-
Notifications
You must be signed in to change notification settings - Fork 9
Version 1.10.2 requires Python 3.8 again #39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I just ran into this error too!
|
Yes, this was completely deliberate: #38. What platform are you on that's still using Python 3.7? So are you asking us to add [project]
...
requires-python = ">= 3.8" A PR would be fine. |
I'm on a Beaglebone black, it's at 3.7.13.
That would be a solution, at least then it would error out during install. Everything seemed fine until I ran the code. |
If I add that to what would be 1.10.3, then the install would try 1.10.2, and that would fail, I think? So I just have to get rid of 1.10.2 altogether? |
I didn't specify a version, just grabbing the latest. So I don't think it will matter to me. |
Debian bullseye is available for BeagleBone Black from https://www.beagleboard.org/distros. That has Python 3.9. Python 3.7 has been EOL since June, 2023. Can you upgrade your Debian version? |
I'm working on that now. I will see if I can downgrade the requirement until then. |
just |
Yup, that's what I did for now. |
We use a PocketBeagle with Debian Buster; whilst we hope to use the images for Bullseye or Bookworm in the future we cannot guarantee it for all devices, and so any older ones that may be updated for whatever reason are at risk of becoming unusable for our purposes. (Patching to force a particular install version worked on our first affected device, and I did so before writing this ticket.)
Hmm, yeah I can see the issue there. |
I am going to clean this up by making a 1.10.3 that requires 3.8, and removing 1.10.2. Then anyone installing this with 3.7 with get 1.10.1. |
I think this is all set now, right @dhalbert? I see the 1.10.2 version yanked on PyPI. |
Right, I think it is all set. So 1.10.1 is fine for 3.7, and 1.10.3 is the first to require 3.8. I will close this. Fixed by #40 |
Following in the footsteps of issue #3, the use of
/
notation has been reintroduced as of1.10.2
and in doing so requires the use of Python 3.8. This is not a thing that can be guaranteed, especially when multiple devices are being built in a commercial capacity on limited hardware.Rather than removing the
/
notation again, one option would be to restrict1.10.2
to Python 3.8, and leave the current python requirements for older versions of the module.The text was updated successfully, but these errors were encountered: