Le vendredi 2 mai 2014 05:50:40 UTC+2, Michael Torrie a écrit : > Can't help but feed the troll... forgive me. > > > > On 04/28/2014 02:57 AM, wxjmfa...@gmail.com wrote: > > > Python 2.7 + cp1252: > > > - Solid and coherent system (nothing to do with the Euro). > > > > Except that cp1252 is not unicode. Perhaps some subset of unicode can > > be encoded into bytes using cp1252. But if it works for you keep using > > it, and stop spreading nonsense about FSR. > > > > > Python 3: > > > - Flexible String Representation (a problem per se), > > > a mathematical absurditiy which does the opposite of > > > the coding schemes endorsed by Unicord.org (sheet of > > > paper and pencil!) > > > - Very deeply buggy (quadrature of the circle problem). > > > > Maybe it's the language barrier, but whatever it is you are talking > > about, I certainly can't make out. > > > > You've been ranting about FSR for years without being able to clearly > > say what's wrong with it. Please quote unicode specifications that you > > feel Python does not implement. What unicode characters cannot be > > represented? Does Python choke on certain unicode strings or expose > > entities it should not (like Javascript does)? > > > > Why would you think that the unicode consortium's list of byte encodings > > are the only possible valid ways of encoding unicode to a byte stream? > > > > If you're going to continue to write this sort of stuff, please have the > > decency to answer these questions at least. > > > > > Positive side: > > > - A very nice tool to teach the coding of characters > > > and unicode. > > > > Indeed.
======== - -- https://mail.python.org/mailman/listinfo/python-list