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 Epic_Wink, SilentGhost, p-ganssle, pitrou, steve.dower, xtreak
Date 2019-04-12.15:51:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555084281.79.0.690581962085.issue36602@roundup.psfhosted.org>
In-reply-to
Content
Having spent more time than I'm proud of recursing through directories, I'd be happy enough with a convenience function that has sensible defaults.

If I want breadth-first recursion (and I often do), I'll write it myself. I have a slight preference for getting all files in a directory before going deeper (which is not what the PR does), and I think that's most consistent with the current behaviour.

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.

If there's an easy and well-known algorithm for detecting infinite symlink recursion (e.g. resolve and check if it's a parent of itself) then do that and skip it, but don't return the targets.
History
Date User Action Args
2019-04-12 15:51:21steve.dowersetrecipients: + steve.dower, pitrou, SilentGhost, p-ganssle, xtreak, Epic_Wink
2019-04-12 15:51:21steve.dowersetmessageid: <1555084281.79.0.690581962085.issue36602@roundup.psfhosted.org>
2019-04-12 15:51:21steve.dowerlinkissue36602 messages
2019-04-12 15:51:21steve.dowercreate