3 ms·

Python 3 also allows for non-ASCII identifiers.

• filmor 7y ago
  Just to be clear, this comment was just a clarification on what goatinaboat might have been getting at, I was in no way suggesting that the snappy claim > While I agree that everything should be ASCII the Python community believes everything should be Unicode, since Python 3. had any substance. It's just important to know IMHO that not only string handling changed in Python 3, but that you can indeed Unicode-ify your identifiers now as well to a certain extend (see https://www.python.org/dev/peps/pep-3131/ https://www.python.org/dev/peps/pep-3131/). I still don't do it for interoperability reasons.
• goatinaboat 7y ago
  Indeed it’s right here https://www.python.org/dev/peps/pep-3131/ https://www.python.org/dev/peps/pep-3131/ Seems a few people on this thread don’t know Python as well as they think they do
  • oefrha 7y ago
    Plenty of mainstream languages allow non-ASCII characters in identifiers. Pretty much none of them (at least not one that I've worked with) have non-ASCII delimiters/operators/keywords/reserved words. Knowing non-ASCII characters is supported in identifiers has nothing to do with objecting to non-ASCII symbols in the language syntax. (Btw plenty of languages tell you non-ASCII characters are supported in identifier names in the first pages of official tutorials, e.g. golang and Swift off the top of my head, so knowing this kind of stuff doesn't make you a language expert.)
    • goatinaboat 7y ago
      knowing this kind of stuff doesn't make you a language expert Never said it did. But I will say for a fact that those who don’t know it are not language experts.
  • geofft 7y ago
    Nobody in this thread disputed that Python 3 allows for non-ASCII identifiers.