News for hackers. Stuff that matters.

A comment on Python 2 will be replaced with Python 3 in the next RHEL major release. Parent comment

Re:Python 2 will be replaced with Python 3 in the next RHEL ... by AnIdiotOnTheNet on Wednesday April 11, 2018 @09:56AM (#16811077)
Whenever this comes up I feel it is worth pointing out that Linux's "Things break" approach is a problem exclusive to the userland tooling built up around the kernel. Linus takes a very hardline stance against breaking kernel ABI compatibility (except for drivers), but pretty much every piece of software outside of that, including GLIBC, thinks it's totally ok to break things all the time.

It's really very sad that the Linux community never adopted Linus's view.

[ Parent | on HN ]
Re:Python 2 will be replaced with Python 3 in the next RHEL ... by jhall1468 on Wednesday April 11, 2018 @11:14AM (#16811921)
Because they are entirely different things. Breaking the kernel ABI doesn't just break a few packages for a popular language, it breaks the entire ecosystem. More importantly there's literally no reason to break compatibility in the kernel. There are perfectly valid reasons to break compatibility in programming languages.

Apples and oranges comparison.

[ Parent | on HN ]
Re:Python 2 will be replaced with Python 3 in the next RHEL ... by jgalar on Wednesday April 11, 2018 @12:27PM (#16812742)
Even the kernel occasionally breaks interfaces. Case in point, FUTEX_FD was introduced in 2.6.0 and retired in 2.6.26 [1].

I don't think anyone working on glibc is intent on breaking user space. Sometimes it's just the most pragmatic solution.

[1] http://man7.org/linux/man-pages/man2/futex.2.html

[ Parent | on HN ]