moving to unicode (was re: PEP)
Robin Becker
robin at jessikat.fsnet.co.uk
Wed Aug 9 11:10:25 EDT 2000
More information about the Python-list mailing list
Wed Aug 9 11:10:25 EDT 2000
- Previous message (by thread): [PEP draft 2] Adding new math operators
- Next message (by thread): [PEP draft 2] Adding new math operators
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In article <4jek5.3550$Z2.65461 at nnrp1.uunet.ca>, Warren Postma <embed at NOSPAM.geocities.com> writes > >> Another thing that should be borne in mind is that we'll be moving to >> unicode so that other operator notations may in fact be more feasible in >> future eg the symbol character set may have an existence in unicode. >> That would make the symbology easier, but not how to associate such >> symbols with python code. > >This scares me more than polluting a nice clean language like Python with >two sets of binary operators. > >If someone wants to write their Python code and write their comments and >string literals in Hebrew, then I can see how handy this would be for them, >but I wonder how much complexity it's going to throw on the backs of the >other 90% of the world's developers who are already used to writing and >reading ASCII files exclusively. > >Warren Postma > > We're the ones complaining about the lack of operator symbols. Unicode will happen whether we like it or not; whether we take advantage of it is up to us. -mumblingly-ýrs- Robin Becker
- Previous message (by thread): [PEP draft 2] Adding new math operators
- Next message (by thread): [PEP draft 2] Adding new math operators
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list