> On 19 May 2020, at 20:27, Brett Cannon <br...@python.org> wrote: > > I'm going to ask that people please try to keep this thread on-topic to the > question of using Unicode characters directly for things that we currently > use two ASCII characters to represent. Other ideas that spring up from this > question are totally welcome to be done as new threads of discussion.
Thank you for re-focusing the discussion I’d like to express the strong opinion that anything related to a particular IDE is not the right answer I’m not going to switch to jetbrains just to get ligatures or fancy rendering, am I ? would you ? Plus, it’s not only IDE’s, I’m prominently concerned by beginners and students, who start reading code on sources like github, or teaching websites, or notebooks; one cannot expect all these stacks to go this extra mile, that is just not right IMHO back to the point as phrased by Brett: I reckon the languages communities have mostly so far stuck to ASCII, probably for good reasons, but the thing is Unicode has been around for quite some time now, and can be deemed generally available so why not take full advantage of it ? It is my feeling that part of the awkwardness of the typing annotations, rightfully outlined above, is due to the narrow set of characters at our disposal, hence the awkward Iterable[] (this one at least clearly deserves better IMHO), and Dict[,] likewise There has to be nicer and more legible ways to express all these I tend to start the discussion on typing annotations because they are more recent, and clearly more in need of improvement however like Alex Hall pointed out, using dedicated symbols like > quoting ≤ instead of <=, ≥ instead of >=, ≠ instead of !=, would make a lot of sense as well I also reckon it is still cumbersome to simply enter Unicode characters from a keyboard sometimes; I guess if the big players were located in other countries that would maybe be different But that will change over time, no matter the speed, some day that will be for granted So again maybe 2020 is the right time to break that barrier ? === PS. it looks like one reasonable thread to spawn off from the earlier exchanges here is about the definition of an arrow operator for defining function types I’ll leave it to the person who originally extended the discussion in that direction :) _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/U3PAVI4QT7LXJKT2MNP7PJ4T6DO7LUQZ/ Code of Conduct: http://python.org/psf/codeofconduct/
