|
Title: PPSMP as a standalone executable Post by: zadio on January 18, 2007, 09:12:02 PM Hello,
Let me first say thank for creating such a nice python module. It seems to work wonders so far. However, I have ran into a little problem. I'm trying to take my application (*.py files, and the ppsmp.pyc file) and turn them into a standalone executable to give to users who do not have python loaded on their computers. The compilation (either by 'freeze' or 'pyinstaller') appears to go ok without any noticeable errors. When I run the resulting executable, it simply sits there - appearing "hung". Yet, when I do a process listing, I see that it is spawning hundreds of copies of itself with no end in sight until the operating system runs out of resources. My goal is to create this executable for Linux 2.4/2.6 and Windows 2000/XP operating systems. Please advise on how best I will be able to create my standalone executable. Thanks -Lee Title: Re: PPSMP as a standalone executable Post by: Vitalii on January 19, 2007, 03:56:54 PM Hello, Welcome to the Parallel Python forums,Let me first say thank for creating such a nice python module. It seems to work wonders so far. However, I have ran into a little problem. I'm trying to take my application (*.py files, and the ppsmp.pyc file) and turn them into a standalone executable to give to users who do not have python loaded on their computers. The compilation (either by 'freeze' or 'pyinstaller') appears to go ok without any noticeable errors. When I run the resulting executable, it simply sits there - appearing "hung". Yet, when I do a process listing, I see that it is spawning hundreds of copies of itself with no end in sight until the operating system runs out of resources. My goal is to create this executable for Linux 2.4/2.6 and Windows 2000/XP operating systems. Please advise on how best I will be able to create my standalone executable. Thanks -Lee Most probably current version (1.1 beta) of ppsmp will not work inside of the standalone executable because the way it starts worker processes will interfere with how python code is packed in that binary. I'll take a closer look at this problem soon and it might be fixed in one of the following releases. Thank you for the feedback. Best regards, Vitalii |