Daniel Harding added the comment:
@Zach - thanks for the review. Sorry that it has taken a few months to pick
this issue back up. Anyway, here is an updated patch. It is pretty different
than the previous patch, to the point that I would consider it a completely new
patch.
Anyway, here
Daniel Harding added the comment:
The previous version of this patch did not handle bytes arguments correctly and
could fail in conjunction with a non-ASCII compatible encoding. Also, if the
result was a UNC path, it was not being handled correctly (the returned value
would have started
Daniel Harding added the comment:
Uploading a new series of patches - they are all the same as the first set,
except for 0006-Make-realpath-follow-symbolic-links-on-Windows.patch. I
realized that I could use os.readlink to handle broken symbolic links, so I
changed the logic of
Daniel Harding added the comment:
I have attached a series of patches with (hopefully) provide more robust fix
for this issue, against the Python 3.3 branch. It handles both bytes and str
objects, paths that do not actually exist on the filesystem, and removal of the
'\\?\' prefi
Daniel Harding added the comment:
I have created a script that does essentially what Mark Tolonen
suggests. When it is provided a script to run, it looks for a #! line
and if it exists, attempts to use that to determine which version of
python.exe to use. It also has the ability to install
Changes by Daniel Harding :
--
nosy: +dharding
___
Python tracker
<http://bugs.python.org/issue4485>
___
___
Python-bugs-list mailing list
Unsubscribe: