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 ezio.melotti
Recipients belopolsky, eric.araujo, ezio.melotti, jcea, lemburg, pitrou, rhettinger, sdaoden, vstinner
Date 2011-02-26.01:39:05
SpamBayes Score 1.088895e-07
Marked as misclassified No
Message-id <1298684345.88.0.568485988805.issue11303@psf.upfronthosting.co.za>
In-reply-to
Content
> For other spellings like "utf8" or "latin1", I wonder if it would be
> useful to emit a warning/suggestion to use the standard spelling.

It would prefer to see the note added by Alexander in the doc mention *only* the preferred spellings (i.e. 'utf-8' and 'iso-8859-1') rather than all the variants that are actually optimized. One of the reasons that lead me to open #5902 is that I didn't like the inconsistencies in the encoding names (utf-8 vs utf8 vs UTF8 etc). Suggesting only one spelling per encoding will fix the problem.

FWIW, the correct spelling is 'latin1', not 'latin-1', but I still prefer 'iso-8859-1' over the two.

(The note could also use some more ``'markup'`` for the encoding names.)
History
Date User Action Args
2011-02-26 01:39:05ezio.melottisetrecipients: + ezio.melotti, lemburg, rhettinger, jcea, belopolsky, pitrou, vstinner, eric.araujo, sdaoden
2011-02-26 01:39:05ezio.melottisetmessageid: <1298684345.88.0.568485988805.issue11303@psf.upfronthosting.co.za>
2011-02-26 01:39:05ezio.melottilinkissue11303 messages
2011-02-26 01:39:05ezio.melotticreate