From: goat <moo...@gm...> - 2013-11-28 18:47:49
|
Ran into the spawn error in an odd way. My frozen exe wouldn't start when called by its relevant URI, regardless of where it was situated on file system. Implementing the SetCurrentDirectory approach fixed it. The issue may be rooted somewhere else. On 11/28/2013 4:37 PM, Thomas Heller wrote: > BTW: Please post the answers to the mailing list! > > Am 28.11.2013 14:47, schrieb goat: >>> Interesting idea. For executables; but this cannot be used for dlls... >> It is possible to retrieve the literal path of a DLL regardless of the >> exe it is attached to. > Sure, but it is at least *not nice* to change the current directory > of an exe from a dll when it is loaded. > >> I have to test the functionality around, not 100% >> of the calls to perform. Would also need to detect whether the code is >> called as an exe or a DLL, nothing too hard either. >> >> I'm going to try and implement these fixes and submit a new patch >> somewhere around tonight or tomorrow morning. >> >> Apparently you can set the environment variable PYTHONIOENCODING before >> calling Py_Initialize(), I'll give it a look as well. >> > Thomas > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk > _______________________________________________ > Py2exe-users mailing list > Py2...@li... > https://lists.sourceforge.net/lists/listinfo/py2exe-users |