[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] how does qApp work in Python? (was Re: from PyQt5.Qt import *)
From:       Christian Tismer <tismer () stackless ! com>
Date:       2018-06-28 15:23:22
Message-ID: 35d24cbf-1a05-7595-884c-a5415a6d4cc3 () stackless ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]

[Attachment #4 (multipart/mixed)]


On 28.06.18 15:42, Christian Tismer wrote:
> On 28.06.18 14:52, Kyle Altendorf wrote:
>> On 2018-06-28 08:37, Christian Tismer wrote:
>>> There is just a single exception that I built explicitly
>>> into our new PySide2 version:
>>>
>>> It allows to write "from PySide2 import *".
>>
>> Since this just came up recently in #pyqt, how do you handle qApp?   Same
>> question for PyQt actually.   It didn't seem to be working as expected.  
>> I also wouldn't expect it to work with the * imports in any case.

Addendum:
Yes, it works with (and without) "from PySide2 import *" because that
is unrelated:
Things which are added to __builtins__ are always found without
any extra import. It is sufficient to import any PySide2 module.

Cheers -- Chris
-- 
Christian Tismer-Sperling    :^)   tismer@stackless.com
Software Consulting          :     http://www.stackless.com/
Karl-Liebknecht-Str. 121     :     http://pyside.org
14482 Potsdam                :     GPG key -> 0xE7301150FB7BEE0E
phone +49 173 24 18 776  fax +49 (30) 700143-0023


["signature.asc" (application/pgp-signature)]
[Attachment #8 (text/plain)]

_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
https://www.riverbankcomputing.com/mailman/listinfo/pyqt

[prev in list] [next in list] [prev in thread] [next in thread]