“I'm basically giving myself a permanent vacation from being BDFL”

Re:“I'm basically giving myself a permanent vacation from be... by jacquesm on Thursday July 12, 2018 @02:18PM (#17517212)

> Python 3 breakage and async turned out to be prescient, fantastic decisions.

Python 3 implementation was a step in the right direction, but the decision to allow the old language co co-exist with the new one and to break backwards compatibility between the two (for instance 'print') in places where it didn't need to break makes no sense to me.

A lot of goodwill got burned with that.

[ Parent | on HN ]

Re:“I'm basically giving myself a permanent vacation from be... by JetSpiegel on Thursday July 12, 2018 @07:08PM (#17519364)

I think this was important. The class of bugs it would have created if it had been compatible with the unicode/ascii split would be hideous.

Fail fast. It's better to break right away than having false senses of security. There is always __future__ too.

[ Parent | on HN ]