News for hackers. Stuff that matters.

A comment on The Python Steering Council intent to approve PEP 703: making the GIL optional. Parent comment

Re:The Python Steering Council intent to approve PEP 703: ma... by a_nop on Friday July 28, 2023 @09:28PM (#36915807)
They kind of burned a breaking major version transition for no good reason with 2-to-3, now they are prefacing a major change with "it won't be like 2-to-3". It sounds like they may be maintaining two operating modes in CPython 3 instead of going forward with another major transition, just because of that history.
[ Parent | on HN ]
Re:The Python Steering Council intent to approve PEP 703: ma... by jborean93 on Saturday July 29, 2023 @03:22AM (#36917760)
> They kind of burned a breaking major version transition for no good reason with 2-to-3

The unicode/text changes alone were a pretty good reason. Division producing floats are also a nice change IMO. I don’t want to discount the challenges with the transition but saying there was no good reason isn’t right to me.

[ Parent | on HN ]
Re:The Python Steering Council intent to approve PEP 703: ma... by rightbyte on Saturday July 29, 2023 @04:27AM (#36918137)
Not good enough reason then?
[ Parent | on HN ]
Re:The Python Steering Council intent to approve PEP 703: ma... by lozenge on Saturday July 29, 2023 @04:45AM (#36918234)
There were a lot of bad reasons as well. The removal of the u string prefix in versions 3.0-3.2 was unnecessary and made the transition much more difficult. It kind of gave Python 3 a bad reputation.
[ Parent | on HN ]
Re:The Python Steering Council intent to approve PEP 703: ma... by a_nop on Sunday July 30, 2023 @01:09AM (#36928024)
Unicode was absolutely a good change, the burn was the execution
[ Parent | on HN ]