Author vbr
Recipients akitada, amaury.forgeotdarc, collinwinter, ezio.melotti, georg.brandl, giampaolo.rodola, gregory.p.smith, jacques, jaylogan, jhalcrow, jimjjewett, loewis, mark, moreati, mrabarnett, nneonneo, pitrou, r.david.murray, rsc, sjmachin, timehorse, vbr
Date 2010-11-13.13:47:27
SpamBayes Score 1.41695e-05
Marked as misclassified No
Message-id <1289656049.29.0.161510973132.issue2636@psf.upfronthosting.co.za>
In-reply-to
Content
I'd have liked to suggest updating the underlying unicode data to the latest standard 6.0, but it turns out, it might be problematic with the cross-version compatibility;
according to the clarification in 
http://bugs.python.org/issue10400
the 3... versions are going to be updated, while it is not allowed in the 2.x series.
I guess it would cause maintainance problems (as the needed properties are not available via unicodedata).
Anyway, while I'd like the recent unicode data to be supported (new characters, ranges, scripts, and corrected individual properties...),
I'm much happier, that there is support for the 2 series in regex...
vbr
History
Date User Action Args
2010-11-13 13:47:29vbrsetrecipients: + vbr, loewis, georg.brandl, collinwinter, gregory.p.smith, jimjjewett, sjmachin, amaury.forgeotdarc, pitrou, nneonneo, giampaolo.rodola, rsc, timehorse, mark, ezio.melotti, mrabarnett, jaylogan, akitada, moreati, r.david.murray, jacques, jhalcrow
2010-11-13 13:47:29vbrsetmessageid: <1289656049.29.0.161510973132.issue2636@psf.upfronthosting.co.za>
2010-11-13 13:47:27vbrlinkissue2636 messages
2010-11-13 13:47:27vbrcreate