➜

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, ezio.melotti, lemburg, loewis, terry.reedy, vstinner
Date 2013-06-23.23:34:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372030470.42.0.563940518339.issue18236@psf.upfronthosting.co.za>
In-reply-to
Content 
I would like someone review this change:

https://bitbucket.org/alexander_belopolsky/cpython/commits/92c187025d0a8a989d9f81f2cb4c96f4eecb81cb?at=issue-18236

The patch can go in without this optimization, but I think this is the right first step towards removing _Py_ascii_whitespace.

I don't think there is a need to generate ASCII optimization in makeunicodedata.  While technically Unicode stability policy only guarantees that White_Space property will not be removed from code point s that have it, I think there is little chance that they will ever add White_Space property to another code point in the ASCII range and if they do, I am not sure Python will have to follow.
History
Date User Action Args
2013-06-23 23:34:30belopolskysetrecipients: + belopolsky, lemburg, loewis, terry.reedy, vstinner, ezio.melotti
2013-06-23 23:34:30belopolskysetmessageid: <1372030470.42.0.563940518339.issue18236@psf.upfronthosting.co.za>
2013-06-23 23:34:30belopolskylinkissue18236 messages
2013-06-23 23:34:30belopolskycreate