RetroSearch Browse

Thu May 12 08:40:21 EDT 2016 · https://mail.python.org/pipermail/python-dev/2016-May/144546.html

On Thu, May 12, 2016 at 3:04 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>
> I'd still like to see this exposed to Python code as os._raw_fspath()
> (with the leading underscore just meaning "this probably isn't the API
> you want" rather than indicating a private or unstable API), and then
> fspath() defined as a wrapper around it which disallows bytes as
> output.
>

I don't remember (should probably check) if you previously proposed
implementing exactly that in C, but I indeed agree with what you write
above, except that I don't like the "_raw_" prefix in the name. I
would be willing to call that simply fspath though, since as mentioned
before in this thread (I think by Brett and me), the reasons for
rejecting bytes in fspath are really quite minor.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-May/144546.html below:

[Python-Dev] file system path protocol PEP