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 p-ganssle
Recipients Epic_Wink, SilentGhost, p-ganssle, pitrou, steve.dower, xtreak
Date 2019-04-13.00:13:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555114389.64.0.969219216591.issue36602@roundup.psfhosted.org>
In-reply-to
Content
> I don't spend enough time dealing with symlinks to have strong opinions there, but given we have ways to resolve symlinks but not to get back to the original name (and I *have* had to deal with issues where I've needed to find the original name from the target :roll-eyes:) I'd say don't resolve anything eagerly.

You mean treating symlinks to directories like files? I suppose that's a possibility, but I do think it will end up being a source of bugs around symlinking.

Admittedly, it *is* apparently what rglob('*') does (just tested it - apparently it won't follow symlinks to directories), though I think it might be a better interface to try to break cycles rather than not follow symlinks (particularly since `iterdir` currently treats symlinks to directories as directories).
History
Date User Action Args
2019-04-13 00:13:09p-gansslesetrecipients: + p-ganssle, pitrou, SilentGhost, steve.dower, xtreak, Epic_Wink
2019-04-13 00:13:09p-gansslesetmessageid: <1555114389.64.0.969219216591.issue36602@roundup.psfhosted.org>
2019-04-13 00:13:09p-gansslelinkissue36602 messages
2019-04-13 00:13:09p-gansslecreate