[Python-Dev] Pathlib enhancements - acceptable inputs and outputs for __fspath__ and os.fspath()
Ethan Furman
ethan at stoneleaf.us
Fri Apr 15 00:22:07 EDT 2016
More information about the Python-Dev mailing list
Fri Apr 15 00:22:07 EDT 2016
- Previous message (by thread): [Python-Dev] Pathlib enhancements - acceptable inputs and outputs for __fspath__ and os.fspath()
- Next message (by thread): [Python-Dev] Pathlib enhancements - acceptable inputs and outputs for __fspath__ and os.fspath()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 04/14/2016 06:01 PM, Ethan Furman wrote: > On 04/14/2016 05:20 PM, Stephen J. Turnbull wrote: >> you'll have to impose it on me. > > Hmm. Well, the good news is you have convinced me that letting bytes > through willy-nilly is akin to loosing the hounds of hell on our code. > The bad news is I was never in that camp. ;) Actually, in retrospect, I was in that camp at the beginning. But Brett's code (and your arguments, amongst others) convinced me of that <one function with a flag> or <a pair of functions> would be better/safer. -- ~Ethan~
- Previous message (by thread): [Python-Dev] Pathlib enhancements - acceptable inputs and outputs for __fspath__ and os.fspath()
- Next message (by thread): [Python-Dev] Pathlib enhancements - acceptable inputs and outputs for __fspath__ and os.fspath()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list