[Python-Dev] When should pathlib stop being provisional? (original) (raw)
Ethan Furman ethan at stoneleaf.us
Wed Apr 6 17:03:55 EDT 2016
- Previous message (by thread): [Python-Dev] When should pathlib stop being provisional?
- Next message (by thread): [Python-Dev] When should pathlib stop being provisional?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 04/06/2016 01:47 PM, Sven R. Kunze wrote:
I still cannot remember what the concrete issue was why we dropped pathlib the same day we gave it a try. It was something really stupid and although I hoped to reduce the size of the code, it was less readable. But it was not the path->str issue but something more mundane. It was something that forced us to use os[.path] as Path didn't provide something equivalent. Cannot remember.....
I'm willing to guess that if you had been able to just call
os.whatever(your_path_obj)
it would have been at most a minor annoyance.
--
Ethan
- Previous message (by thread): [Python-Dev] When should pathlib stop being provisional?
- Next message (by thread): [Python-Dev] When should pathlib stop being provisional?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]