Brett Cannon added the comment:
Thanks for the path, Senko! Tweaked the wording a bit as the current
directory part was accurate for when you're in the REPL.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
Roundup Robot added the comment:
New changeset 47c31e7d3779 by Brett Cannon in branch 'default':
Issue #6386: When executing a script that's a symlink, the directory
http://hg.python.org/cpython/rev/47c31e7d3779
--
nosy: +python-dev
___
Python
Changes by Brett Cannon br...@python.org:
--
assignee: - brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6386
___
___
Python-bugs-list
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6386
___
Senko Rasic added the comment:
Yep, signed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6386
___
___
Python-bugs-list mailing list
Senko Rasic added the comment:
Patch for modifying the modules part of tutorial with the changes suggested by
jamadagni (reworded slightly so the note is outside the itemized list).
--
keywords: +patch
nosy: +senko
Added file:
Brett Cannon added the comment:
Senko, could you sign the contributor agreement
(http://python.org/psf/contrib/contrib-form/) so we can use your patch?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6386
Shriramana Sharma added the comment:
I'm sorry but I don't get why this is a WONTFIX. I reported what is (now)
apparently a dup: issue 18067. Just like the OP of this bug, I feel that in
doing testing and such, one would naturally symlink and expect the library in
the *current* directory to
R. David Murray added the comment:
When a script is executed by python, it does *not* import from the CWD, it
imports from the *location of the script*. From this, then, you can see that
there are two possible interpretations of the location of the script when the
script is a symlink, and we
Nick Coghlan added the comment:
The current behaviour is also needed to sanely support Python scripts
symlinked from Linux /bin directories.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6386
Shriramana Sharma added the comment:
The current behaviour is also needed to sanely support Python
scripts symlinked from Linux /bin directories.
OK that clinched it for me -- I can't argue against that! And obviously it is
not meaningful to copy/symlink *all* the current-directory modules
Nick Coghlan added the comment:
That's fair - reopening this as a docs bug.
--
assignee: brett.cannon -
components: +Documentation
resolution: wont fix -
stage: test needed - needs patch
status: closed - open
type: behavior - enhancement
versions: -Python 3.2
Mark Lawrence added the comment:
It will be difficult to take this forward owing to the problem description in
msg89914 being limited to importing from normal files in the same directory
does not work. Plus any problems back then may well have been fixed due to
the reworking of the import
Brett Cannon added the comment:
In case someone wants to reproduce:
mkdir pkg
echo import tester pkg/symlinked.py
ln -s pkg/symlinked.py linked.py
echo print('HIT') tester.py
That fails because Python assumes you are in the pkg directory, not the
directory you started execution.
Changes by Eric Snow ericsnowcurren...@gmail.com:
--
nosy: +eric.snow
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6386
___
___
Python-bugs-list
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +brett.cannon, ncoghlan
versions: +Python 3.3, Python 3.4 -Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6386
___
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
stage: - unit test needed
versions: +Python 3.2 -Python 2.4, Python 2.5, Python 2.6, Python 3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6386
New submission from jbeulich jbeul...@novell.com:
Due to the way PySys_SetArgv() works, when the initial script is a
symbolic link, importing from normal files in the same directory does
not work. This is particularly surprising when the work tree is a
symlinked clone (cp -s) of an original
Changes by jan matejek jmate...@suse.cz:
--
nosy: +matejcik
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6386
___
___
Python-bugs-list mailing
19 matches
Mail list logo
