This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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
Attachment:
signature.asc
Description: Digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |