NumPy 1.16 is the last release to support Python 2.7 • Hacker News Board

Re: NumPy 1.16 is the last release to support Python 2.7

#111

Post by geofft » Tue, Jan 22, 2019, 3:42 AM UTC

explainplease wrote: post #47

geofft wrote: post #14

Earlier quoted context omitted.

Sorry, I mean that the volunteer maintainer of the latexmk package in Debian hasn't updated it since 2015. Arch probably has a newer version from the latexmk authors (and I think Arch does not have the same culture of individual package maintainers, in general).

The Debian LaTeX maintainer was essentially harassed out of the project by the Anti-Harassment Team.

This is 1) irrelevant, he was not the maintainer for latexmk (in fact he did some non-maintainer uploads very recently for it to update it to the latest version), and 2) not true, he was not "harassed out of the project," he was removed by formal action. I read "harassed out" as "pressured into quitting" or something. He didn't quit under pressure; his account was removed. (And he's still a Debian Maintainer, same status as me.)

Re: NumPy 1.16 is the last release to support Python 2.7

#112

Post by geofft » Tue, Jan 22, 2019, 3:44 AM UTC

gammateam wrote: post #102

geofft wrote: post #10

Earlier quoted context omitted.

Debian stable (Stretch aka Debian 9, released summer 2017, regular support through ~summer 2020) has Python 3.5. Debian oldstable (Jessie aka Debian 8, released summer 2015, regular support through summer 2018) had Python 3.4. If you're on oldstable it's time to think about upgrading.... The next stable release (Buster aka Debian 10) is just starting the freeze process now and expected to come out this summer - Debia…

wow 3.5 I already have apps that won't install unless 3.6 is there

Sure, and those apps didn't exist in late 2016/early 2017 when Debian stable was being finalized. It's called stable for a reason. If you want a faster-moving distro with correspondingly higher risk, there are multiple excellent choices, but in general you'll have to keep up with a much faster upgrade cycle. (My personal preferences would be Ubuntu non-LTS or even Debian testing, which goes through pretty good QA these days and is a fine choice for non-production-critical machines.) Alternatively, wait a few months and the next stable release will have you covered.

Re: NumPy 1.16 is the last release to support Python 2.7

#113

Post by chupasaurus » Tue, Jan 22, 2019, 10:49 AM UTC

mehrdadn wrote: post #85

raxxorrax wrote: post #84

Earlier quoted context omitted.

No idea. I use mainly Debian but I think Ubuntu has a more aggressive update policy and is based on Debian. Not sure about RH since I don't know a lot about their package managers. But CentOS and Fedora are probably also quite up to date.

Oh Ubuntu is like Debian to me... in fact when I was taking about Debian this whole time I was actually talking about Ubuntu. Its latexmk is the one that's old.

Most of the big maintaining teams (programming languages and DEs) are the same for both distributions.

Re: NumPy 1.16 is the last release to support Python 2.7

#114

Post by hencoappel » Tue, Jan 22, 2019, 12:34 PM UTC

VWWHFSfQ wrote: post #96

josteink wrote: post #79

Earlier quoted context omitted.

> Our old servers are on SLES 11 which has Python 2.6 and even our new boxes have RHEL 7 which has Python 2.7 only by default. Not to sound condescending... But why does this single default matter that much? I'm sure you install lot of things onto these machines which isn't there by default, right? Why is installing Python 3 on top of all those other non-default packages such a problem?

I prefer to install as few 3rd party packages as possible. In RHEL7 until recently Python 3 was only available via 3rd party repos, until EPEL added it. So now it's not that big of a deal to install python3, but before that why would I go about adding ius or something to get a modern python when there's a perfectly fine Python 2.7 built into the system for running sysadmin jobs?

> perfectly fine Python 2.7

Not sure how you see a system being deprecated in 2020 as perfectly fine.

Re: NumPy 1.16 is the last release to support Python 2.7

#115

Post by explainplease » Tue, Jan 22, 2019, 8:55 PM UTC

geofft wrote: post #111

explainplease wrote: post #47

Earlier quoted context omitted.

The Debian LaTeX maintainer was essentially harassed out of the project by the Anti-Harassment Team.

This is 1) irrelevant, he was not the maintainer for latexmk (in fact he did some non-maintainer uploads very recently for it to update it to the latest version), and 2) not true, he was not "harassed out of the project," he was removed by formal action. I read "harassed out" as "pressured into quitting" or something. He didn't quit under pressure; his account was removed. (And he's still a Debian Maintainer, same st…

> he was not "harassed out of the project," he was removed by formal action.

Ah, yes, the standard bureaucratic cover for abuse: retroactively justify it with formal committee action, by asking people to submit examples of badthink and badspeak from years ago:

		2012: 1 email
		2013: 7 emails
		2014: 5 emails
		2015: 1 email
		2016: 0 emails
		2017: 2 emails
		2018: 2 emails

Nothing wrong with that at all. Nothing to see here! Debian's a perfectly healthy project. Continue on your way.