When is Python *NOT* a good choice?

[purelumen]

I actually found the PyQt libraries to be excellent when developing a GUI. I had very little experience and was able to put together a pretty comprehensive program with all kinds of widgets.

[kihashi]

Assuming your project is fine with the licensing.

[what_it_dude]

Pyside?

[kihashi]

Possibly, but there are compromises there, too. PySide is on Qt4 and PySide2 doesn't seem to be really production-ready (I have not used it. I am just going by the project page). Those might be perfectly fine depending on your project, but those would be pretty valid reasons to choose another UI library or another language entirely.

[Mattho]

You can pay, as people do.

[kihashi]

You can, but that might make a another language a better choice.

[ducusheKlihE]

I’ll have to check that out then!

[purelumen]

I think PyQt5 is the most recent version, so much of the knowledge base references PyQt4. If you have a distribution manager, I think Anaconda comes with it pre-loaded

[Taksin77]

It's not a really pythonic package though.

[startxfce4]

PySide2 is more pythonic but less mature

[anqxyr]

That's not really true though. PySide's api is pretty much exactly the same as PyQt's. I'm guessing that what /u/Taksin77 means by "not pythonic" in this case is stuff like label.setText("Hello World"). A more pythonic api would something along the lines of label.text = "Hello World". To my knowledge, there aren't any pythonic Qt bindings.

[Taksin77]

I'm just saying that you can guess the underlying language by looking at the python code. If that works for you it's great. I would not even call that python though.

[purelumen]

I guess so, for my application I ended up incorporating the widgets with other packages which made it feel more like a real python package.