Am 10.10.2014 15:58, schrieb Gelonida N: > Have a project with 2 executables both sharing the same pkg.file. > - one executable with console=True > - another for exactly the same code with console=False
Yes, but this would require some more work (at least on non-Unix file-systems), because the file of the .pkg is derived from the .exe. And this derivation is hard-coded in the boot-loader. Nevertheless it should not be to hard implementing this. > Other use case could be an alternative implementation of merge > by collecting all modules into a single .pyz/.pkg file, that will be > used by all the executables. Yes, absolutely. This would be a more elegant solution than the current MERGE(). The only problem is, that the scripts are part of the .pkg, too. But MERGE() has the same problem, so the solution should not be that hard to implement. > Other use case (see thread "patching a pyinstaller release") > - having an external patch script reading, modifying, rewriting a > pyz/pkg file for a project. If you would implement such a tool, I vote for including it into the PyInstaller distribution. -- 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/install-cyanogenmod-on-s3-mini-using-linux Kolumne: http://www.cissp-gefluester.de/2010-07-passwoerter-lieben-lernen Goebel Consult ist Mitglied bei http://www.7-it.de/
smime.p7s
Description: S/MIME Cryptographic Signature
