[PyQt] PyQt/PyCharm/PEP problem with PyQt types

Phil Thompson phil at riverbankcomputing.com
Wed Nov 22 10:18:16 GMT 2017

On 22 Nov 2017, at 10:13 am, J Barchan <jnbarchan at gmail.com> wrote:
> @Florian & @Phil,
> Your posts crossed with my last one above.
> Technically as I wrote there, one does not have to "go through Qt reading whether a "QObject *" does or does not accept NULL/None, because it automatically does.  As I wrote, if it does not, the correct Qt C++ declaration would have been "QObject &", and that was up to the Qt people, not PyQt to guess.
> Having said that, I realise we are where we are.  (Unless PyQt wants to change the declarations at the next release.)  I am concerned about what I can do moving on.  You guys have clarified to me that I am not "missing something" which would have solved this neatly.  I now can declare my own function parameters/returns with Union; I am stuck with where a PyQt function does not do so and so I will get a warning on my calling code, but at least I know where I am.  So thank you all.

I'm happy to change things so they work better. I don't use them myself so other people need to come to a consensus about any changes. When I added support I tried to get the PyCharm people to comment and/or verify the decisions I took but they were completely unresponsive.


More information about the PyQt mailing list