3 ms·

Isn't it better staying out? It seems like it shares similar properties to pytz - new codecs need to be added semi-regularly. What was it Kenneth Reitz said? S

• maxerickson 9y ago
  Presumably the way to do it would be to add the individual encodings as modules in https://github.com/python/cpython/tree/master/Lib/encodings https://github.com/python/cpython/tree/master/Lib/encodings so the risk of stagnation would be low. I guess the bigger issue would be bikeshedding the names and aliases...
• rspeer 9y ago
  Yeah, I know the saying. My observation here is that the number of text encodings is generally decreasing, due to the fact that UTF-8 is obviously good. I want wacky encodings to die. But this is just a class of encodings that have existed for decades and that Python missed. Perhaps on the basis that they were non-standard nonsense, but now they're standardized. It could be argued that web-windows-1252 is the third most common encoding in the world. If I'm giving directions for how to decode text in this encoding, it currently only works if you've imported ftfy first, even if you don't need ftfy.
  • crdoconnor 9y ago
    If they're all 10 years old and on their way out then yeah, I suppose it would make sense to include them in python - whether or not they're nonsense.
  • simonw 9y ago
    Sounds to me like you've argued yourself around to pitching them for inclusion! I find the argument that web-windows-1252 is supported by modern browsers very convincing.