shell wrong path

[Andreas Roehler]

Am 01.11.2011 12:33, schrieb Andrea Crotti:
> While trying to run a script and there is already another *Python*
> buffer open
> for another directory, running the script normally fails if there are some
> relative file paths.
>
> Apparently the CWD in the *Python* buffer remains the old one, and thus it
> makes sense that Python can't resolve relative paths.
>
> I tried to add this line in py-execute-buffer but without success,
> any help?
>
> (cd (file-name-directory (buffer-file-name py-master-file)))
>

[Andreas Roehler (a-roehler)]

Am 01.11.2011 22:50, schrieb Andrea Crotti:
[ ... ]
> > And anyway, I think is quite a bug, because if I run a python script I
> > should expect that it runs in the same current directory...
I quite agree.

Georg

[Andreas Roehler (a-roehler)]

better now?

[Andrea Crotti (andrea-crotti-0)]

I did a bzr pull, deleted the "elc", reloaded python-mode,
then I created a simple file

import os
print("hello from %s" % os.getcwd())

and run it, I still see the CWD from the previously running python, not
the CWD of the current script..

[Andreas Roehler (a-roehler)]

whats the precise command you used as "run"

M-x py-execute-buffer here yields in buffer

*Python*

>>> ## executing temporary file /tmp/Python3442A4R.py...
hello from MY-USERDIR

;;;;;;;

C-h v default-directory
-->
default-directory is a variable defined in `C source code'.
Its value is
"PATH-WHERE-SKRIPT-RESIDES/"

;;;;;;;;;;;

i.e. getcwd()

returns $HOME

[Andreas Roehler (a-roehler)]

could you try again?

[Andrea Crotti (andrea-crotti-0)]

Now it seems to work :)
I tried two different scripts running on the same *Python* and they run in the right CWD...

Thanks