The official policy is that we want them to go away, but reality so far has not budged. We will continue to hold our breath though. :-) On Tue, Aug 19, 2014 at 1:37 AM, Serhiy Storchaka <storchaka at gmail.com> wrote: > Builting open(), io classes, os and os.path functions and some other > functions in the stdlib support bytes paths as well as str paths. But many > functions doesn't. There are requests about adding this support ([1], [2]) > in some modules. It is easy (just call os.fsdecode() on argument) but I'm > not sure it is worth to do. Pathlib doesn't support bytes path and it looks > intentional. What is general policy about support of bytes path in the > stdlib? > > [1] http://bugs.python.org/issue19997 > [2] http://bugs.python.org/issue20797 > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/ > guido%40python.org > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140819/6890db8b/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4