Josiah Carlson wrote: > "Martin v. Löwis" <martin at v.loewis.de> wrote: > >>Fredrik Lundh wrote: >> >>>however, for Python 3000, it would be nice if the source-code encoding applied >>>to the *entire* file (XML-style), rather than just unicode string literals and (hope- >>>fully) comments and docstrings. >> >>As MAL explains, the encoding currently does apply to the entire file. >>However, because of the Python syntax, you are restricted to ASCII >>in many places, such as keywords, number literals, and (unfortunately) >>identifiers. Lifting the restriction on identifiers is on my agenda. > > > It seems that removing this restriction may cause serious issues, at > least in the case when using cyrillic characters in names. See recent > security issues in regards to web addresses in web browsers for the > confusion (and/or name errors) that could result in their use. > > While I agree in principle that people should be able to use the > entirety of one's own natural language in writing software in > programming languages, I think that it is an ugly can of worms that > perhaps shouldn't be opened. I agree with Josiah. A few years ago we had a discussion about this on python-dev and agreed to stick with ASCII identifiers for Python. I still think that's the right way to go. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Oct 25 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4