Am 08.04.2014 07:54, schrieb Burak Nehbit: >> Have you bundled it using PyInstaller, too? Are you using MERGE? > > No, I haven’t. I haven’t had taken a look at Merge—up until now my > belief was that multiprocessing did not need such tools. I can run > Twisted’s own spawnProcess without bundling the subprocess or without > merge, so I would think Ampoule would not change anything. It’s > nothing but a wrapper over spawnProcess. >
Did I understand right? You haven't bundled the second program using PyInstaller at all? If you second program is a Python-Program, and you are *not* shipping the Python interpreter and you are *not* bundling that program, how should this program run? >> Well, I'd prefer having a requirements.txt and a PyInstaller >> .spec-file, so I can immediately start looking into the problem. :-) > > My apologies, here’s the last working spec file I had. > > https://dl.dropboxusercontent.com/u/5815330/aether.spec This should be something like: a1 = Analysis(['/Volumes/Sky/Repos/aether/Code/aether/main.py']) pyz1 = PYZ(a1.pure) exe1 = EXE(pyz1, a1.scripts, ...) a2 = Analysis(['/Volumes/Sky/Repos/aether/second-program.py']) pyz2 = PYZ(a2.pure) exe2 = EXE(pyz2, a2.scripts, ...) coll = COLLECT(exe1, exe2 a1.binaries, a1.zipfiles, a1.datas, a2.binaries, a2.zipfiles, a2.datas, strip=None, upx=True, name='Aether' ) I strongly suggest testing this with two very simple applications, both of which only printing some text. > Should I be packaging the second process on its own? Can Merge handle > this? Yes. No, Merge is the advanced usage. You should first get an simple app running, then your app, them you may try merge. -- 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/sag-nein-zum-routerzwang Kolumne: http://www.cissp-gefluester.de/2010-09-mut-zur-beschraenkung Goebel Consult ist Mitglied bei http://www.7-it.de/
smime.p7s
Description: S/MIME Cryptographic Signature
