@fabiosantoscode@mastodon.social
Post #2198717
2025-12-15 11:50 UTC
@millie@infosec.exchange especially true for programming languages and core libraries. python2 vs python3 was so exhausting and took so long, and what did we win from it, as a species?
Replies (3)
-
@millie@infosec.exchange 2025-12-15 13:36
@fabiosantoscode@mastodon.social Had they kept the print keyword as opposed to migrating entirely to it being a built-in function and also kept the binascii library working with unicode string types, then like 90% if the python2-python3 compatibility issues would nonexistent. Most of the language remained completely the same but those two changes made it so the vast majority of python2 scripts straight up were not compatible with a python3 interpreter.
-
@art_codesmith@toot.cafe 2025-12-15 13:55
@fabiosantoscode@mastodon.social @millie@infosec.exchange Better Unicode support?
-
@SvenGeier@mathstodon.xyz 2025-12-15 17:18
@fabiosantoscode@mastodon.social We invalidated an xkcd comic (353)! Take that, Randall Munroe... @millie@infosec.exchange