Giovanni Bajo píše v St 27. 07. 2011 v 12:26 +0200: > Generically updating to subprocess for the sake of doing it is not > something that we should waste time on. If there are compelling > reasons > (eg: preparation for 3.0) then we keeping two code-paths don't sound > like too much effort.
Then let's wrap os.system and subprocess in own function in PyInstaller/compat.py. Other python projects, when they decided to support python 3, their minimum requirement is mostly python 2.4. I'm not sure what other reasons they have. The module Six, which we could use to wrap different module names in python2 and python3 claims python 2.4+. -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
