[issue13412] No knowledge of symlinks on Windows
New submission from Alex Regueiro : 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 prevalent. -- components: IO messages: 147715 nosy: alexreg priority: normal severity: normal status: open title: No knowledge of symlinks on Windows versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue13412> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13412] No knowledge of symlinks on Windows
Alex Regueiro 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. -- ___ Python tracker <http://bugs.python.org/issue13412> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13412] No knowledge of symlinks on Windows
Alex Regueiro 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. Perhaps symlink creation/deletion on Windows could even be integrated into the Python class library? -- ___ Python tracker <http://bugs.python.org/issue13412> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13412] No knowledge of symlinks on Windows
Alex Regueiro 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 <http://bugs.python.org/issue13412> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13412] No knowledge of symlinks on Windows
Alex Regueiro added the comment: No error whatsoever. Python just thinks it doesn't exist unfortunately. Same report from other users... -- ___ Python tracker <http://bugs.python.org/issue13412> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13412] No knowledge of symlinks on Windows
Alex Regueiro 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 <http://bugs.python.org/issue13412> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13412] Symbolic links omitted by os.listdir on some systems
Alex Regueiro 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 directory, all works fine, otherwise it can't be found. Hopefully you can verify this. -- ___ Python tracker <http://bugs.python.org/issue13412> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13419] import does not recognise SYMLINKDs on Windows 7
New submission from Alex Regueiro : 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 that the Python interpreter normally has no problem with symlinks on Win7 with its file I/O features.) -- messages: 147789 nosy: alexreg priority: normal severity: normal status: open title: import does not recognise SYMLINKDs on Windows 7 type: feature request versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue13419> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6727] ImportError when package is symlinked on Windows
Alex Regueiro 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 tracker <http://bugs.python.org/issue6727> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6727] ImportError when package is symlinked on Windows
Alex Regueiro 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 programming, so that probably explains the delay. -- ___ Python tracker <http://bugs.python.org/issue6727> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6727] ImportError when package is symlinked on Windows
Alex Regueiro 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 <http://bugs.python.org/issue6727> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6727] ImportError when package is symlinked on Windows
Alex Regueiro added the comment: That's great, thanks. -- ___ Python tracker <http://bugs.python.org/issue6727> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6727] ImportError when package is symlinked on Windows
Alex Regueiro 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. -- ___ Python tracker <http://bugs.python.org/issue6727> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28446] pyvenv generates malformed hashbangs for scripts
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 the space. Maybe a warning message about this would be best. To reproduce this issue, simply run the following from an empty directory that has a space in its path: ``` pyenv venv/ source ./venv/bin/activate pip ``` The result should be something like: ``` -bash: /Users/me/dir with space/foo/venv/bin/pip: "/Users/me/dir: bad interpreter: No such file or directory ``` -- messages: 278676 nosy: alexreg priority: normal severity: normal status: open title: pyvenv generates malformed hashbangs for scripts type: behavior versions: Python 3.5 ___ Python tracker <http://bugs.python.org/issue28446> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
