On Nov 6, 12:45 pm, IRLStephen <[EMAIL PROTECTED]> wrote: > Hi, > > I have a python application which I am compiling to exe with > pyinstaller. The application has a facility that allows the user to > execute other python scripts from a gui. The app uses the > subprocess.Popen() function to execute the python files in a new > process. > > My problem is that on one winPC, if I run a .py file which prints out > os.name, I see 'nt'. However, if I run my application on another winPC > (which does not have any installation of python) and then run the > same .py file, the os.name is 'posix' > > Can someone explain why this might be. Its causing me a big issues, > because python scripts that try to import non-system modules can't > find them on the second PC, but they work fine on the first PC. (the > modules are in the same directory as the application) > > This seems to be down to the sys.path being incorrect on the PC thats > reporting its platform as 'posix'. i.e. the sys.path includes /path/to/ > application, but because its posix, it should be /cygwin/c/path/to/ > application > > Any help/pointers would be greatly appreciated > > Thanks, > Stephen
I should probably mention that I'm using python 2.5 and pyinstaller 1.3 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en -~----------~----~----~----~------~----~------~--~---
