On 1 Apr 2008, at 16:22, Ronald Oussoren wrote: >> 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.
Yep, this is what I meant - the goal being to put responsibility for this behaviour where it really belongs: with the modules that require it. Of course, it'll mean that any existing modules that expect a GUI connection by default will need updated to call TransformProcessType themselves. But given that such modules will almost certainly contain Mac-specific code anyway, it shouldn't be a big deal to add the extra call during their Python 3 upgrade. has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
