Am 06.03.2014 12:38, schrieb Martin Zibricky: > > The real solution could be to add folder 'PyInstaller/lib' at the end of > sys.path - pyinstaller would use system packages first and fallback to the > bundled. > > And also remove six.py module since do not use it yet.
Both of which are not solving the problem at it's root: There may be different version of other packages in PyInstaller/lib/, too. And there are both cases: The system-wide one is too old for PyInstaller and the one in PyInstaller/lib may be to old for the packaged application. Two possible solutions come to my mind: 1) Implement out own import mechanism using the system-wide and, if this one is too old, falling back to the one in PyInstaller/lib. Well, this is adding another cludge. 2) Require these dependencies to be installed by the user. What do you think? -- Schönen Gruß Hartmut Goebel Dipl.-Informatiker (univ), CISSP, CSSLP Information Security Management, Security Governance, Secure Software Development Goebel Consult, Landshut http://www.goebel-consult.de Blog: http://www.goebel-consult.de/blog/passwort-richtlinien-bei-dhl-vergratzen-user Kolumne: http://www.cissp-gefluester.de/2011-11-in-troja-nichts-neues Goebel Consult ist Mitglied bei http://www.7-it.de/
smime.p7s
Description: S/MIME Cryptographic Signature
