This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ideasman42
Recipients SilentGhost, benhoyt, ideasman42, mont29, paul.moore, serhiy.storchaka, steve.dower, tim.golden, vstinner, zach.ware
Date 2015-12-21.07:37:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450683432.54.0.674779823461.issue25911@psf.upfronthosting.co.za>
In-reply-to
Content
@haypo, I checked available info online and couldn't find any reference to byte file-paths were deprecated since Python3.2.

On the contrary, the 3.2 release notes [0] state:

 "countless fixes regarding bytes/string issues; among them full support for a bytes environment (filenames, environment variables)"

----
Also docs for open 3.2 [1] and 3.5 [2] say that byte filenames are supported with no mention of deprecation.

Since this is already working properly in 3.5 for other systems besides ms-windows, and worked in 3.4x.
Dropping support on a single platform seems a rather problematic regression.

----

[0]: https://www.python.org/download/releases/3.2/
[1]: https://docs.python.org/3.2/library/functions.html#open
[2]: https://docs.python.org/3.5/library/functions.html#open
History
Date User Action Args
2015-12-21 07:37:12ideasman42setrecipients: + ideasman42, paul.moore, vstinner, tim.golden, SilentGhost, benhoyt, zach.ware, serhiy.storchaka, steve.dower, mont29
2015-12-21 07:37:12ideasman42setmessageid: <1450683432.54.0.674779823461.issue25911@psf.upfronthosting.co.za>
2015-12-21 07:37:12ideasman42linkissue25911 messages
2015-12-21 07:37:12ideasman42create