[Python-Dev] Import and unicode: part two (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Thu Jan 20 14:16:51 CET 2011
- Previous message: [Python-Dev] Import and unicode: part two
- Next message: [Python-Dev] Import and unicode: part two
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Jan 20, 2011 at 10:08 PM, Simon Cross <hodgestar+pythondev at gmail.com> wrote:
I'm changing my vote on this to a +1 for two reasons:
* Initially I thought this wasn't supported by Python at all but I see that currently it is supported but that support is broken (or at least limited to UTF-8 filesystem encodings). Since support is there, might as well make it better (especially if it tidies up the code base at the same time). * I still don't think it's a good idea to give modules non-ASCII names but the "consenting adults" approach suggests we should let people shoot themselves in the foot if they believe they have good reason to do so.
I'm also +1 on this for the reasons Simon gives.
I should have a chance to look at the patch this weekend.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] Import and unicode: part two
- Next message: [Python-Dev] Import and unicode: part two
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]