[issue26031] Add stat caching option to pathlib

Guido van Rossum added the comment: Okay, I am giving up on this. -- resolution: -> out of date stage: test needed -> resolved status: open -> closed ___ Python tracker ___

[issue26031] Add stat caching option to pathlib

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26031] Add stat caching option to pathlib

Changes by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue26031] Add stat caching option to pathlib

Antoine Pitrou added the comment: Let me first mention the stat caching question was asked during the PEP discussion and ultimately it was decided it's not a good idea to meld it in the Path design :-) Early versions of pathlib were more complex as they were able to keep some file

[issue26031] Add stat caching option to pathlib

New submission from Guido van Rossum: There are concerns that pathlib is inefficient because it doesn't cache stat() operations. Thus, for example this code calls stat() for each result twice (once internal to the glob, a second time to answer the is_symlink() question): p =

[issue26031] Add stat caching option to pathlib

Guido van Rossum added the comment: That's fair, though I don't know what kind of caching design was considered (until Ram's suggestion on python-ideas I had thought the cache would simply use a slot on the Path instance to hold the stat() result). If we want pathlib to become pervasive we may