New submission from Alex Regueiro alex...@gmail.com:
Python 2.7 has no knowledge of directory symlinks on Windows 7. Listing a
directory symlink does not work, nor does accessing a file within one. This is
quite a notable missing feature on Windows 7, where symlinks are becoming
increasingly
Alex Regueiro alex...@gmail.com added the comment:
What are you running? This is not what I get on Win7 x64, and I have had
several other users in ##python on FreeNode confirm this inability. As far as
Python is concerned, these dir sym links do not even exist
Alex Regueiro alex...@gmail.com added the comment:
Thanks Bryan, that would be great.
The elevated privs problem could potentially be avoided by creating symlinks
using the Win32 API directly. As long as the appropiate group policy is set,
one does not require admin privs to create symlinks
Alex Regueiro alex...@gmail.com added the comment:
Well, at the very least it's a system-dependent issue, since I've tried out
listdir and also file access on my system and some other Windows users'.
--
___
Python tracker rep...@bugs.python.org
http
Alex Regueiro alex...@gmail.com added the comment:
No error whatsoever. Python just thinks it doesn't exist unfortunately. Same
report from other users...
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13412
Alex Regueiro alex...@gmail.com added the comment:
When listing the parent dir in which a dir symlink resides, the dir symlink
doesn't show up. That's the one I noticed most.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Alex Regueiro alex...@gmail.com added the comment:
Okay, so I figured out where I was originally seeing this issue. (It does
indeed work normally as you said; I'm not sure how I tested otherwise.)
Well, the problem is when you load a module that is a SYMLINKD. If the module
folder is a normal
New submission from Alex Regueiro alex...@gmail.com:
Python 2.7 normally inputs directory-modules fine on Windows 7. The notable
exception however is symbolically-linked directories on the filesystem, which
are ignored (not thought to exist) by the Python `import` statement. (Note
Alex Regueiro alex...@gmail.com added the comment:
Is this bug going to be fixed? I've been experiencing this for some time now,
and it seems the Python team has known about it for a while too... seems like
an easy fix!
--
nosy: +alexreg
___
Python
Alex Regueiro alex...@gmail.com added the comment:
Well, I am making an assumption here. :-)
Might have a look at a patch. Never looked at the Python runtime before. If
it's all written in C, then it's possible. I'm guessing most of the Python
programmers don't know much/anything about Win32
Alex Regueiro alex...@gmail.com added the comment:
Thanks Brian; that's good to know. If we could get it in the next release
(Python 2.8?) that would be awesome.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6727
Alex Regueiro alex...@gmail.com added the comment:
That's great, thanks.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6727
___
___
Python-bugs
Alex Regueiro alex...@gmail.com added the comment:
That's very good news. I suspected MS has written a wrapper over this somewhere
to accommodate for this bug, and it was just a matter of using the right API.
I look forward to seeing this in the next 2.7 release
New submission from Alex Regueiro:
Quotes around hashbangs are not recognised and are considered invalid syntax,
at least on Bash on OS X 10.12. There's really no workaround (that I'm aware
of) for paths containing spaces, except maybe symlinking the directory in the
path the contains
14 matches
Mail list logo
