➜

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 belopolsky
Recipients belopolsky, eric.araujo, ezio.melotti, jcea, lemburg, sdaoden, vstinner
Date 2011-02-24.15:40:45
SpamBayes Score 1.2140761e-06
Marked as misclassified No
Message-id <AANLkTi=kY1s-ScxjhKSAB9HWyTCdEGJxnMVuBYbso9X2@mail.gmail.com>
In-reply-to <1298561454.43.0.304649761025.issue11303@psf.upfronthosting.co.za>
Content 
On Thu, Feb 24, 2011 at 10:30 AM, Ezio Melotti <report@bugs.python.org> wrote:
..
> See also discussion on #5902.

Mark has closed #5902 and indeed the discussion of how to efficiently
normalize encoding names (without changing what is accepted) is beyond
the scope of that or the current issue.  Can someone open a separate
issue to see if we can improve the current situation?  I don't think
having three slightly different normalize functions is optimal.  See
msg129248.
History
Date User Action Args
2011-02-24 15:40:46belopolskysetrecipients: + belopolsky, lemburg, jcea, vstinner, ezio.melotti, eric.araujo, sdaoden
2011-02-24 15:40:45belopolskylinkissue11303 messages
2011-02-24 15:40:45belopolskycreate