[Python-Dev] File system path encoding on Windows (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Wed Aug 31 00:58:09 EDT 2016
- Previous message (by thread): [Python-Dev] File system path encoding on Windows
- Next message (by thread): [Python-Dev] socket.setsockopt() with optval=NULL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 31 August 2016 at 10:27, Steve Dower <steve.dower at python.org> wrote:
On 30Aug2016 1702, Victor Stinner wrote:
I can try to run more tests if you know some other major Python applications (modules?) working on Windows/Python 3. The major ones aren't really the concern. I'd be interested to see where numpy and pandas are at, but I suspect they've already encountered and fixed many of these issues due to the size of the user base. (Though skim-reading numpy I see lots of code that would be affected - for better or worse - if the default encoding for open() changed...)
For a case of "Don't break software already trying to do things right", the https://github.com/beetbox/beets example that Daniel linked earlier would be a good one to test.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] File system path encoding on Windows
- Next message (by thread): [Python-Dev] socket.setsockopt() with optval=NULL
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]