This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients amaury.forgeotdarc, brian.curtin, jaraco, pitrou, python-dev, santoso.wijaya, tim.golden
Date 2013-05-28.02:07:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369706848.19.0.252644002885.issue13772@psf.upfronthosting.co.za>
In-reply-to
Content
Ugh. So it seems the 3.3 implementation of win_symlink, which is now been renamed to posix_symlink, is now much more complicated. Not only does it handle symlink arguments on Unix platforms, providing abstraction for a couple of underlying system calls, but the Windows implementation also supports once again wide and narrow characters for the path, which means that the directory detection functions I created are no longer suitable as they also need wide and narrow versions.
History
Date User Action Args
2013-05-28 02:07:28jaracosetrecipients: + jaraco, amaury.forgeotdarc, pitrou, tim.golden, brian.curtin, santoso.wijaya, python-dev
2013-05-28 02:07:28jaracosetmessageid: <1369706848.19.0.252644002885.issue13772@psf.upfronthosting.co.za>
2013-05-28 02:07:28jaracolinkissue13772 messages
2013-05-28 02:07:27jaracocreate