Hi.
How can I say, from the cmd line, that python should take my CWD as my
CWD, and not the directory where the script actually is?
I have a python script that works fine when it sits in directory WC,
but if I move it out of WC to H and put a symlink from H/script to WC,
it doesn't find the
On 2013.05.16 02:48, Charles Smith wrote:
Hi.
How can I say, from the cmd line, that python should take my CWD as my
CWD, and not the directory where the script actually is?
I have a python script that works fine when it sits in directory WC,
but if I move it out of WC to H and put a
On 05/16/2013 03:48 AM, Charles Smith wrote:
Hi.
How can I say, from the cmd line, that python should take my CWD as my
CWD, and not the directory where the script actually is?
I have a python script that works fine when it sits in directory WC,
but if I move it out of WC to H and put a
On 16 Mai, 10:18, Dave Angel da...@davea.name wrote:
On 05/16/2013 03:48 AM, Charles Smith wrote:
Hi.
How can I say, from the cmd line, that python should take my CWD as my
CWD, and not the directory where the script actually is?
I have a python script that works fine when it sits in
On Thu, 16 May 2013 00:48:45 -0700, Charles Smith wrote:
Hi.
How can I say, from the cmd line, that python should take my CWD as my
CWD, and not the directory where the script actually is?
*scratches head*
Python does use your current working directory as your current working
directory. I
On 16 Mai, 11:04, Steven D'Aprano steve
+comp.lang.pyt...@pearwood.info wrote:
Python does use your current working directory as your current working
directory. I think you are misdiagnosing the problem.
That's usually how it ends up ...
Here's a demonstration:
steve@runes:~$ cat
On 05/16/2013 04:29 AM, Charles Smith wrote:
On 16 Mai, 10:18, Dave Angel da...@davea.name wrote:
On 05/16/2013 03:48 AM, Charles Smith wrote:
Hi.
How can I say, from the cmd line, that python should take my CWD as my
CWD, and not the directory where the script actually is?
I have a
