-
Notifications
You must be signed in to change notification settings - Fork 303
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
Drop support for Python 3.7 #8025
Comments
python 3.8 is still supported whatever you understand. |
You mean supported by PSF, or in Haiku? I asked on IRC if we should move away from both 3.7 and 3.8, and @pulkomandy, at least, said yes, I understand that lots of stuff still depend on Py 3.7 and 3.8 (thus the lists), and my intention was start moving forward the packages with low impact. I wasn't planning to remove Python 3.7 and Python 3.8 right away (breaking things), if that's the concern. In any case, I'll wait for confirmation on how to proceed. |
You wrote "Python versions 3.7 and 3.8 are in "Source-only security fix releases" mode" as a reason for this issue. But only 3.7 is soon EOL. We switched to 3.9 only three months ago, please give users some time before removing anything. |
Alright. Guess moving low impact packages from 3.7 to 3.9 would still be OK? Or would you rather prefer to see PRs that only add 3.9/3.10 support if missing? |
Sure, moving away from 3.7 when upgrading versions is OK. |
My reasoning for saying it's ok to remove 3.7 and 3.8:
As a result, Python 3.8 does not need to be supported in the long term. And PYthon 3.7 is replaced by 3.9 so there is no need to support it anymore. Is this moving too fast? If so, what is the correct timelin for this? Should we keep Python 3.7 as "deprecated" until the next beta release of Haiku? Or is it just "wait a few months"? Are there reasons to keep Python 3.8 a little longer? |
IMO it's irrelevant when Beta 4 switched to Python 3.9 as the new default. If users use Python 3.8 and vendor packages for their own python scripts, they should be given some time to upgrade (6 months seem reasonable). Python 3.7 won't be supported long upstream, so that's another case. |
Recipes with only 3.7 are left alone. Help with #8025.
@threedeyes most of the qt packages are still using python3.7, did a few already (see list above), any reason why python is involved in them? (haven't seen any mention in the configure/build process?) For qmdnsengine I can't find any reference to python aside from some doxygen references? |
libcec (removed python dependency): #8302 |
Recipes with only 3.7 are left alone. Help with haikuports#8025.
All the qt6* ones are off the list today... thanks a lot @threedeyes!!! |
@pulkomandy: Tried to run a build for u-boot (trying to see if it builds OK after changing
Tried manually installing all the available "mpfr" packages, and verifying the lib is where it is supposed to... same result. Questions: Besides this libmpfr.so.4 issue that might be a new issue with the arm-none-eabi-gcc package... Is the recipe a WIP, or it should be buildable? If the later, do you think we can just switch to TIA. |
It seems I just forgot the PATCHES in the recipe and that should be added, rather than ignoring the patch? I had this working when I pushed it, otherwise I would have marked the recipe as broken. I have used the resulting uboot binaries on an ARM system and managed to get haiku_loader running with it. The first problem appears to be a missing dependency of arm-none-eabi-gcc to lib:libmpfr$secondaryArchSuffix. Also I'm a bit confused why you ask this in a thread about Python 3.7? |
Because the u-boot recipe has the mentioned dependency on setuptools_python3 (besides the one for cmd:python3, that one's ok, but the setuptools_python3 is 3.7). And because we're trying to switch away from 3.7 in this thread. (u-boot being one of the few remaining on the list above, and the one I was trying to work on). |
From the list in the initial post I think "only" scribus and libreoffice are still on Python 3.7? Is there anything else? |
Noup, you're right. Only Scribus and LO 6.4 remain using Python 3.7. The rest are all Python 2.x |
Just in case... I'm attempting to re-build Scribus with Python 3.10 on 64 bits right now (edit: build seems fine... will open PR). After many network-related issues, managed to get all the necessary dependencies. I'm affraid Scribus is as big as a project as I can tackle with my slow PC/network. Some other kind soul will have to try with LibreOffice 6.4 :-) |
I think this can be closed, yielding with "inrecipe ..." doesn't show up anything for python3.7, cmd:python3 is only used in BUILD_PREREQUIRES so installing those packages shouldn't be a problem, rebuilding them for a newer version will use python3.10 at this moment. |
Closing. Remaining 2.7 cleanup tasks either have active PRs, or could be handled individually when the time comes to update each particular package. Thanks, everyone! With most the recipes in good shape now, dropping 3.8 next should be far less work. |
As beta4 uses Python 3.9 as default, and as Python versions 3.7 and 3.8 are in "Source-only security fix releases" mode (with even less than 3 months of that for 3.7), we should drop support for the older ones (adding support for Python 3.10 where possible).Edit: scope for this issue has changed following discussion on comments below.As beta4 uses Python 3.9 as default, and as Python versions 3.7 is nearing EOL, we'll be dropping support for it (and also for Python 2.7 package that might still remain), while adding support for Python 3.10 where possible.
To help keep track of the progress on this regard, I'll add some tasks list:
Regular packages (recipes not under
dev-python/
):List of *. recipes that contain either of:
(and for Python 2.x:
_python$
,cmd:python$
andlibpython2
)Python packages (recipes under
dev-python/
):List of
*.recipe
files for Python packages that contain either of:(and for Python 2.x: _python$ and cmd:python$)
The text was updated successfully, but these errors were encountered: