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 steve.dower
Recipients Christian Åkerström, eric.smith, eryksun, ethan smith, ishimoto, jaraco, living180, ncdave4life, paul.moore, pitrou, steve.dower, stutzbach, takluyver, tim.golden, zach.ware, Étienne Dupuis
Date 2019-08-16.18:34:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1565980479.49.0.796151556703.issue9949@roundup.psfhosted.org>
In-reply-to
Content
Another minor change worth calling out - I added a note to the docs that when a symlink cycle is detected, realpath() could return any member of the cycle, but does not guarantee which one.

For our test cases it's generally stable enough, but if you change the starting point (e.g. from absolute to relative path) then it can change the result. It seemed easier all round just to not guarantee anything about which member of the cycle will be returned, rather than determining the exact rules, reproducing them across all platforms, and documenting them.
History
Date User Action Args
2019-08-16 18:34:39steve.dowersetrecipients: + steve.dower, paul.moore, ishimoto, jaraco, pitrou, eric.smith, tim.golden, stutzbach, living180, takluyver, zach.ware, ncdave4life, eryksun, Christian Åkerström, ethan smith, Étienne Dupuis
2019-08-16 18:34:39steve.dowersetmessageid: <1565980479.49.0.796151556703.issue9949@roundup.psfhosted.org>
2019-08-16 18:34:39steve.dowerlinkissue9949 messages
2019-08-16 18:34:39steve.dowercreate