On 1 Apr, 2008, at 14:23, has wrote:
On 1 Apr 2008, at 13:19, has wrote:The command line python interpreter automatically upgrades to a full GUI process whenever OS APIs linked to the Window Manager are called. [...]As an addendum: Note that this isn't an issue with Ruby as the ruby interpreter only upgrades to a GUI process if you call TransformProcessType yourself. e.g. This is what rb-appscript's OSAX module does whenever it needs to display a dialog, and it works fine. With the general de-Macification of Python 3.0 being planned, I wonder if the python3.0 interpreter should take the same approach, leaving it up to individual modules to decide if and when they want a GUI connection? Anyone any thoughts?
My preference would be to have have modules "just work", that is I shouldn't have to call TransformProcessType myself but appscript and/ or the Carbon libraries should do that for me when necessary.
Ronald
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
