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 loewis
Recipients belopolsky, ezio.melotti, lemburg, loewis
Date 2010-11-29.19:48:38
SpamBayes Score 0.00010245
Marked as misclassified No
Message-id <4CF40395.70000@v.loewis.de>
In-reply-to <AANLkTina_o7yahC9_70VeJfu=08NdUoJqZfyE1siH4YC@mail.gmail.com>
Content
> These changes don't affect gencodec.py, but it may be inconvenient to
> run makeunicodedata.py and gencodec.py using different versions of
> Python.

As MAL explains: these are completely unrelated, independent tools,
and gencodec isn't run more than once per decade (or so). I only ever
run makeunicodedata, and I have been using Python 3 to run it.

The mappings are not supposed to ever change once produced. In
particular, new versions of Unicode cannot affect them, since the
existing characters all map fine to existing code points, which will
not change their meaning per Unicode stability criteria.
History
Date User Action Args
2010-11-29 19:48:39loewissetrecipients: + loewis, lemburg, belopolsky, ezio.melotti
2010-11-29 19:48:38loewislinkissue10552 messages
2010-11-29 19:48:38loewiscreate