Am 26.07.2011 12:04, schrieb Giovanni Bajo:
Well, regarding the replacement of os.system() with subprocess module: There are many bug related to os.system, os.popen, etc. For example if the path contains spaces, it needs to be quoted -- and it needs to be quoted correctly.I oppose any drop in compatibility that it is not backed by a strong showstopper. If it's needed for Python3, we can still make it conditional so that it only gets triggered for newer Python versions.
So the question is: Should we keep compatibility only for compatibilities sake? Keep compatible with something nobody uses anymore?
Python 2.3 was released on July 29, 2003, this is eight years ago. The last release of Python 2.2 (2.2.3) was on May 30, 2003. Not even the security fix for SimpleXMLRPCServer was put into a newer release (see http://www.python.org/download/releases/2.2.3/).
On the other hand, Python 2.3 brings a lot of improvements which would enhance the software quality of PyInstaller, of we are using it or solve problem. E.g. Unicode file names, source code encoding, or the logging package.
IMHO, there is no real need for keeping compatible for < 2.3. New projects should be written at least in Python 2.6 and existing project can still use PyInstaller 1.5.
just my 5 cent. ** -- Schönen Gruß - Regards Hartmut Goebel Dipl.-Informatiker (univ.), CISSP, CSSLP Goebel Consult Spezialist für IT-Sicherheit in komplexen Umgebungen http://www.goebel-consult.de Monatliche Kolumne: http://www.cissp-gefluester.de/ Goebel Consult mit Mitglied bei http://www.7-it.de
smime.p7s
Description: S/MIME Cryptographic Signature
