MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/Python/comments/26irie/python_3_is_killing_python/chrmjsf/?context=3
r/Python • u/upofadown • May 26 '14
147 comments sorted by
View all comments
6
The alternative is dealing with those warts that built up. This is a necessary evil!
0 u/[deleted] May 26 '14 [deleted] 2 u/flying-sheep May 26 '14 It has no way to use undecodable bytes as filenames on Unix (which should be possible)But that's it AFAIK. 5 u/mitsuhiko Flask Creator May 26 '14 Surrogate escapes are a terrible wart. Way worse than bytes vs unicode in python 2. There is still no good way to deal with surrogate escapes as far as i know.
0
[deleted]
2 u/flying-sheep May 26 '14 It has no way to use undecodable bytes as filenames on Unix (which should be possible)But that's it AFAIK. 5 u/mitsuhiko Flask Creator May 26 '14 Surrogate escapes are a terrible wart. Way worse than bytes vs unicode in python 2. There is still no good way to deal with surrogate escapes as far as i know.
2
It has no way to use undecodable bytes as filenames on Unix (which should be possible)
But that's it AFAIK.
5 u/mitsuhiko Flask Creator May 26 '14 Surrogate escapes are a terrible wart. Way worse than bytes vs unicode in python 2. There is still no good way to deal with surrogate escapes as far as i know.
5
Surrogate escapes are a terrible wart. Way worse than bytes vs unicode in python 2. There is still no good way to deal with surrogate escapes as far as i know.
6
u/TankorSmash May 26 '14
The alternative is dealing with those warts that built up. This is a necessary evil!