News for hackers. Stuff that matters.
Re:The Fundamental Problem in Python 3 by kresten on Friday December 20, 2019 @01:22AM (#21842070)
It takes a specific type of personality to remain angry about Python 3 in Dec 2019.

Didn’t that story finish?

Re:The Fundamental Problem in Python 3 by mehrdadn on Friday December 20, 2019 @01:36AM (#21842126)
Why would the stories finish when the pains they refer to are still there like before...?
Re:The Fundamental Problem in Python 3 by jasondclinton on Friday December 20, 2019 @01:38AM (#21842132)
I know if at least a few big tech companies that haven't migrated from 2 yet. So, a lot of folks are discovering Python 3 for the first time.
Re:The Fundamental Problem in Python 3 by philipov on Friday December 20, 2019 @02:20AM (#21842262)
In my experience, companies haven't yet migrated from Python 2 for the same reason they haven't yet migrated from COBOL. It has nothing to do with Python 3's benefits or flaws.
Re:The Fundamental Problem in Python 3 by KaiserPro on Friday December 20, 2019 @02:33AM (#21842301)
its a specific bug in python3.

not just rant, its a specific, well reasoned bug report.

Re:The Fundamental Problem in Python 3 by jnwatson on Friday December 20, 2019 @02:46AM (#21842356)
It is horrible compromise of a bad situation. 99% of the time file name bytes are UTF-8 decodable. What do you do in the other case? You could return a different type, but then that makes dealing with it harder. You could make a new filesystem name type, but that would make simple APIs complicated. Using a new control character is probably the best one could do.