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 Garen, eric.smith, jaraco
Date 2011-10-10.13:50:12
SpamBayes Score 8.715395e-11
Marked as misclassified No
Message-id <1318254613.19.0.284459177103.issue13143@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks Garen for the detailed analysis and writeup. The short answer to your question is "supported by the Python runtime". Allow me to provide a bit of history.

Symlink awareness under Windows was added to Python in Python 3.2, so the behavior you see in Python 2.7 is somewhat historical - in particular, islink was implemented to always return False. In hindsight, this decision was probably a poor one, because it doesn't allow for forward compatibility.

Unfortunately, due to the compatibility rules of Python versions, this cannot change. The semantic meaning of ntpath.islink (and thus os.path.islink on Windows) cannot change.

The suggestion to update the documentation to reflect this behavior is  a good one. I will extend the Python 3.1 and earlier docs to clarify this detail.

One suggestion for the client: to accurately determine if the Python runtime supports symlinks, check hasattr(os, 'symlink'), whereafter you'll know if the runtime supports symlinks and whether os.link will return anything other than False.
History
Date User Action Args
2011-10-10 13:50:13jaracosetrecipients: + jaraco, eric.smith, Garen
2011-10-10 13:50:13jaracosetmessageid: <1318254613.19.0.284459177103.issue13143@psf.upfronthosting.co.za>
2011-10-10 13:50:12jaracolinkissue13143 messages
2011-10-10 13:50:12jaracocreate