Message362919
> Decorating __new__ with lru_cache would likely run into memory leakage problems?
I think the LRU cache would be for returning the same instance when called with the same string. I don't think it would be needed to return the same instance when called with a Path instance.
> From a quick look it appears to only be settable by using the path (not the actual file) as a context manager, and only serves to block further filesystem methods, but I'm not even sure why?
This came up in bpo-39682 recently, I'm not sure what this flag is supposed to mean and I could not find it in the documentation.
Since it's uncorrelated to the file object and the physical file, I think it may actually be dangerous to rely on this flag. I don't know why is the purpose of using Path as a context manager. |
|
Date |
User |
Action |
Args |
2020-02-28 21:41:52 | remi.lapeyre | set | recipients:
+ remi.lapeyre, brett.cannon, rhettinger, pitrou, Antony.Lee |
2020-02-28 21:41:52 | remi.lapeyre | set | messageid: <1582926112.94.0.890494554536.issue39783@roundup.psfhosted.org> |
2020-02-28 21:41:52 | remi.lapeyre | link | issue39783 messages |
2020-02-28 21:41:52 | remi.lapeyre | create | |
|