3 ms·
This has been explained over and over. Those boundaries in python2 are very easy to get wrong and the runtime will not warn you, which means you won't know abou
by toyg 10y ago
This has been explained over and over. Those boundaries in python2 are very easy to get wrong and the runtime will not warn you, which means you won't know about them until some crap data comes down the wire and code chokes or (worse) silently corrupts data. In py3 you are forced to explicitly Do The Right Thing, so entire classes of bugs are just Not Possible.
It shouldn't take 8 years to understand this issue, and I'm positive you do understand it because you're an intelligent person, so please don't troll about it.
- Radim 10y ago"With dynamic typing, the runtime will not warn you, which means you won't know until some crap data comes and your code chokes. With static typing, you are forced to explicitly Do The Right Thing, so entire classes of bugs are just Not Possible." See what I did there? toyg, I found your comment unbearably rude, condescending and arrogant, and downvoted it for that reason.
- toyg 10y ago> See what I did there? Confused your terminology? With static typing, the compiler will warn you, not the runtime. Regardless, the difference is that in practice, file-handling boundary calls don't need to be as flexible as internal interfaces, and it's obviously much more difficult to figure out what The Right Thing To Do is in the latter case (or whether there is a Right Thing at all, in a lot of cases). How many times do you need to change the encoding you use for writing files? How many times do you change an internal class or type? They are totally different ballgames. > I found your comment unbearably rude, condescending and arrogant Apologies, but after 8 years and countless hours of bickering on this point, patience can wear really, really thin.
- Radim 10y agoHave you considered that if you find yourself debating for 8 years without success, you're debating the wrong side? :) Yes, Python 3 is an improvement over Python 2. I like Python 3. No, Python 2's unicode support was fine, contrary to OP's claim.