On 05/16/2013 04:29 AM, Charles Smith wrote:
On 16 Mai, 10:18, Dave Angel 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 w
On 16 Mai, 11:04, Steven D'Aprano 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 test.py
> import os
> print os.getcwd(
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
On 16 Mai, 10:18, Dave Angel 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 direct
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 symlin
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 p
