Ethan Furman stoneleaf.us> writes:
> Do we allow bytes to be returned from os.fspath()? If yes, then do we
> allow bytes from __fspath__()?
De-lurking. Especially since the ultimate goal is better interoperability, I
feel like an implementation that people can play with would help guide the
Brett Cannon python.org> writes:
> https://gist.github.com/brettcannon/b3719f54715787d54a206bc011869aa1 has
the four potential approaches implemented (although it doesn't follow the
"separate functions" approach some are proposing and instead goes with the
allow_bytes approach I originally
Donald Stufft stufft.io> writes:
> > On Apr 14, 2016, at 11:59 AM, Michael Mysinger via Python-Dev python.org> wrote:
> >
> > In essence, you will force me to pre-
> > wrap all RichPath objects in either os.fsencode(os.fspath(path)) or
> > os.fsdecode(os
Ethan Furman stoneleaf.us> writes:
> On 04/14/2016 12:03 AM, Michael Mysinger via Python-Dev wrote:
> > In particular, one RichPath
> > class might return bytes and another str, or even worse the same class
might
> > sometimes return bytes and sometimes str. When will o
