Re: Problem calling python
"Luke Dunstan" <[email protected]>
| Newsgroups | gmane.comp.python.windows-ce |
|---|---|
| Message-ID | <[email protected]> |
----- Original Message ----- From: "Ed Blake" <[email protected]> To: <[email protected]> Sent: Thursday, April 13, 2006 12:19 AM Subject: Re: [PythonCE] Problem calling python > > I've been wondering about that. Don't you get the full path to a script > when > it is run? Otherwise how would Python know where to find the file it's > supposed to execute? How can you open a file without knowing where it is? > And if you do know where a script is being run from - shouldn't that be > the > scripts initial working directory? Your suggestion has been implemented in the latest release. Luke > > --- Luke Dunstan <[email protected]> wrote: > >> >> While you are debugging this, please be aware that unlike most operating >> systems, Windows CE has no concept of a "current directory" at all. The >> command prompt gives the illusion of a current directory for convenience >> but >> once you start another program it will have no way of knowing what the >> command prompt current directory was. PythonCE also emulates a current >> directory for compatibility with other Python platforms but it is always >> "\Temp" when you start PythonCE. You can see what the current (emulated) >> directory is using os.getcwd(). >> >> Luke >> > > _______________________________________________ > PythonCE mailing list > [email protected] > http://mail.python.org/mailman/listinfo/pythonce >