Python 2 will be replaced with Python 3 in the next RHEL major release

Re:Python 2 will be replaced with Python 3 in the next RHEL ... by UncleEntity on Wednesday April 11, 2018 @11:34AM (#16812185)

They did break all C extensions in py3k -- not so bad you can't work around it with some preprocessor magic but break it they did.

And they continued to break them within the py3k lifetime, mostly unicode related stuff from what I can remember. Probably still break stuff but I haven't had time for my toy python projects in a while so haven't been messing with the C-API lately.

[ Parent | on HN ]

Re:Python 2 will be replaced with Python 3 in the next RHEL ... by oblio on Wednesday April 11, 2018 @11:48AM (#16812312)

We're actually agreeing here, I think.

I wished they had broken everything harder and once and for all, in order to fix the issue.

If there's going to be breakage anyway, people adjust their expectations. The scale is basically:

a lot of breakage > a bit of breakage >>>>>> no breakage.

Once you do break backwards compatibility, you might as well do it in a big way, provided you:

* don't offer vaporware for a decade (hello Perl 6!)

* try to offer some mitigations for the migration pain (auto-conversions, support libraries, top-notch docs, etc.)

* offer a great carrot at the end of the tunnel (good performance would be such a carrot)

[ Parent | on HN ]