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 gvanrossum
Recipients benhoyt, ethan.furman, gvanrossum, pitrou, serhiy.storchaka, vstinner
Date 2016-01-07.01:29:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJJPFGD--1D48KJGMNUMEbBwi+SSzxj6eBrBadcx_C+0GQ@mail.gmail.com>
In-reply-to <1452128813.43.0.0294991548565.issue26032@psf.upfronthosting.co.za>
Content
Ben, I think it's worth calling out what the rules are around symlinks. I'm
guessing the info that is initially present is a subset of lstat(), so if
that indicates it's a symlink, is_dir() and is_file() will need a stat()
call, *unless* follow_symlinks is False.

Another question: for symlinks, there are two different possible stat
results: one for stat() and one for lstat(). Are these both cached
separately? Or is only one of them? (Experimentally, they are either both
cached or the cache remembers the follow_symlinks flag and re-fetches the
other result.)

Related, "this method always requires a system call", that remark seems to
disregard the cache.

I'd be happy to review a doc update patch if you make one.
History
Date User Action Args
2016-01-07 01:29:30gvanrossumsetrecipients: + gvanrossum, pitrou, vstinner, benhoyt, ethan.furman, serhiy.storchaka
2016-01-07 01:29:30gvanrossumlinkissue26032 messages
2016-01-07 01:29:29gvanrossumcreate