[PATCH] [BZ 17588 13064] Update UTF-8 charmap and width to Unicode 7.0.0

Mike Frysinger vapier@gentoo.org
Tue Feb 17 11:41:00 GMT 2015


On 22 Dec 2014 20:52, Alexandre Oliva wrote:
> <snip>

+1 to pretty much all the tenets Alexandre laid out here.

> One issue that springs to mind is the requirement for python2.7
> compatibility.  I'm pretty sure we have used python3-only features, and
> I hope we don't have to rewrite them into less readable variants just
> for python2.7 compatibility, for scripts that would only have to be
> rerun at Unicode version updates.  I'm assuming we'll keep on holding
> the generated ctype and utf8 files in the source repository.

i'm used to py2.7, but i don't have a problem with requiring py3.3+.  i think we 
should pick one for all files and stick with it though ... having a mix across 
modules would be awful for cognitive load.  should be easy to enforce though:

#!/usr/bin/python3
...
import sys
...
if sys.hexversion < 0x3030000:
    raise RuntimeError('python-3.3+ required')
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20150217/26bd606b/attachment.sig>


More information about the Libc-alpha mailing list