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 josh.r
Recipients gvanrossum, josh.r, pitrou
Date 2016-01-05.05:25:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1451971517.7.0.288043575894.issue26012@psf.upfronthosting.co.za>
In-reply-to
Content
So would the goal of a fix be something like dev/inode memoization to prevent traversing the same link twice? To provide an argument to prevent following symlinks at all (as in stuff like os.walk), possibly defaulting to followlinks=False? It looks like languages like Ruby never follow symlinks when performing recursive globs to avoid this issue ( https://stackoverflow.com/questions/357754/can-i-traverse-symlinked-directories-in-ruby-with-a-glob ). It's probably easiest to just block recursing through symlinks (at least by default); memoizing risks unbounded memory overhead for large directory trees.
History
Date User Action Args
2016-01-05 05:25:17josh.rsetrecipients: + josh.r, gvanrossum, pitrou
2016-01-05 05:25:17josh.rsetmessageid: <1451971517.7.0.288043575894.issue26012@psf.upfronthosting.co.za>
2016-01-05 05:25:17josh.rlinkissue26012 messages
2016-01-05 05:25:16josh.rcreate