Re: Couldn't install numpy on Python 2.7

On 6/12/2024 1:59 PM, Chris Angelico via Python-list wrote:

On Thu, 13 Jun 2024 at 03:41, AVI GROSS via Python-list
<python-list@python.org> wrote:

>
Change is hard even when it may be necessary.
>
The argument often is about whether some things are necessary or not.
>
Python made a decision but clearly not a unanimous one.

 What decision? To not release any new versions of Python 2? That isn't
actually the OP's problem here - the Python interpreter runs just
fine. But there's no numpy build for the OP's hardware and Python 2.7.
 So if you want to complain about Python 2.7 being dead, all you have
to do is go through all of the popular packages and build binaries for
all modern computers. If that sounds easy, go ahead and do it; if it
sounds hard, realise that open source is not a democracy, and you
can't demand that other people do more and more and more unpaid work
just because you can't be bothered upgrading your code.

I support a Tomcat project that has some java code and most of the code is for Jython 2.7.  Jython 2.7 is approximately on a par with Python 2.7.  Any Python-only code from the standard library will probably run, but of course any C extensions cannot.  The nice thing about using Jython in a java environment is that it can call any java object, and java code can call Jython objects and their methods.
The project cannot move to a Python-3 compatible version because Jython 3.xx doesn't exist and may never exist.  The saving grace is that my project doesn't have to use packages like numpy, scipy, and so forth. Also, the project is very mature and almost certainly won't need to create functionality such packages would enable.  It would be nice to be able to use some newer parts of the standard library, but there it is. Jython does support "from __future__ import" and I make use of that for the print function and the like.

My current PC was not upgradable because of the new hardware requirement
Microsoft decided was needed for Windows 11.

 Yes, and that's a good reason to switch to Linux for the older computer.

I have a 2012-vintage laptop that in modern terms has a very small supply of RAM and a very slow hard drive. When my newer Windows 10 computer was going to be out of service for a while, I put a Linux distro on an external SSD and copied things I needed to work on to it, including my Thunderbird email profile directory.
Thunderbird and everything else worked perfectly for me during that week.  True, there were a few Windows-only programs I missed, but I used other similar programs even if I didn't like them as much.  It's amazing how little resources Linux installs need, even with a GUI.  Of course, 4GB RAM is limiting whether you are on Linux or Windows - you can't avoid shuffling all those GUI bits around - but with a little care it worked great.  And with the external SSD the laptop was a lot snappier than it ever was when it was new.

I mention this in the context of examples of why even people who are fairly
knowledgeable do not feel much need to fix what does not feel broken.

 It doesn't feel broken, right up until it does. The OP has discovered
that it *IS* broken. Whining that it doesn't "feel broken" is nonsense
when it is, in fact, not working.
 

When is Python 4 coming?

 Is this just another content-free whine, or are you actually curious
about the planned future of Python? If the latter, there is **PLENTY**
of information out there and I don't need to repeat it here.
 Please don't FUD.
 ChrisA