logoalt Hacker News

yoyohello13today at 2:58 PM2 repliesview on HN

Most Python developers these days weren't even programming when the 2 -> 3 split happened. Unless you're referencing something else.


Replies

zahlmantoday at 5:48 PM

There are quite a few old hands among Python core devs. Certainly the culture of that burnout is in place, if you look at the responses that proposals for new standard library additions get these days. There also seems to be a lot of trauma from the loud complaints about backward compatibility breaks.

I still hear people complain about how such and such removal between "minor versions" of Python 3 (you really should be thinking of them as major versions nowadays — "Python 3 is the brand", the saying goes now), where they were warned like two years in advance about individual functions, supposedly caused a huge problem for them. It's hard for me to reconcile with the rhetoric I've heard in internal discussions; they're so worried in general about possible theoretical compatibility breaks that it seems impossible to change anything.

denimnerd42today at 3:05 PM

the batteries included approach is the stdlib that can do everything. turns out it’s hard to maintain and make good.

show 1 reply