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 neologix
Recipients hynek, jcea, ncoghlan, neologix, pitrou, python-dev, rosslagerwall, tarek
Date 2012-02-05.15:19:30
SpamBayes Score 1.6431652e-07
Marked as misclassified No
Message-id <1328455171.45.0.939299812533.issue13734@psf.upfronthosting.co.za>
In-reply-to
Content
Committed, thanks for the comments.

Note to myself (and others that might be interested in the O(1)) version):
we can't simply call openat(dirfd, "..", O_RDONLY) to re-open the current directory's file descriptor after having walked a into one of its subdirectories because if this subdirectory is actually a link, we'll open the parent directory of the target directory, instead of the current (toppath) directory. OTOH, if the user passes followlinks=True, then we don't have to bother with openat() and friends in which case we don't have to bother passing FDs between calls to fwalk().
History
Date User Action Args
2012-02-05 15:19:31neologixsetrecipients: + neologix, jcea, ncoghlan, pitrou, tarek, rosslagerwall, python-dev, hynek
2012-02-05 15:19:31neologixsetmessageid: <1328455171.45.0.939299812533.issue13734@psf.upfronthosting.co.za>
2012-02-05 15:19:30neologixlinkissue13734 messages
2012-02-05 15:19:30neologixcreate