-
Notifications
You must be signed in to change notification settings - Fork 343
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
Warnings on Installation Regarding Deprecated setuptools #5754
Comments
Given that, after the release of 103.0 LTS, we're now on track for bigger chances, let's start by dropping Python 3.7 support. There are a number of features that are available on Python 3.8 and later only. One example is the availibility of importlib.metadata stardand library, which we intend to use to replace pkg_resources (and then setuptools as a whole). As for Avocado users and important platforms, we're on a good position such as QEMU already requiring Python 3.8, and CentOS Stream 9 shipping Python 3.9.18. Reference: avocado-framework#5754 Signed-off-by: Cleber Rosa <[email protected]>
Given that, after the release of 103.0 LTS, we're now on track for bigger chances, let's start by dropping Python 3.7 support. There are a number of features that are available on Python 3.8 and later only. One example is the availibility of importlib.metadata stardand library, which we intend to use to replace pkg_resources (and then setuptools as a whole). As for Avocado users and important platforms, we're on a good position such as QEMU already requiring Python 3.8, and CentOS Stream 9 shipping Python 3.9.18. Reference: avocado-framework#5754 Signed-off-by: Cleber Rosa <[email protected]>
Given that, after the release of 103.0 LTS, we're now on track for bigger chances, let's start by dropping Python 3.7 support. There are a number of features that are available on Python 3.8 and later only. One example is the availibility of importlib.metadata stardand library, which we intend to use to replace pkg_resources (and then setuptools as a whole). As for Avocado users and important platforms, we're on a good position such as QEMU already requiring Python 3.8, and CentOS Stream 9 shipping Python 3.9.18. For RPM builds, EL8 (in all its forms) are not going to be built anymore on CI. This may change if the SPEC file is updated to support a conditional build using Python 3.8 for EL8, but that depends on the existence of all dependencies on that build, including python3-aexpect, which is not currently available. Reference: avocado-framework#5754 Signed-off-by: Cleber Rosa <[email protected]>
Hello! I am Nyuydine Bill an applicant for outreachy internship, I wish to know if this issue is still relevant so I can start working on it |
Hi @NyuydineBill, thanks for reaching out. Yes, this issue still is relevant. As a matter of fact, it's being addressed right now, but you may also be able to help. There may be a simple fix to each of the warnings being produced, and if you are able to come up with these fixes, they'd be more than welcome. But, I've chosen to take on this issue from a different angle: removing the setuptools dependency from Avocado. The reason is that Python 3.12 and later standard installations do not come with setuptools, and having an Avocado installation that depends only on Python itself is very attractive. The first part of the work is removing Avocado's dependency on But, with the removal of setuptools, we must change the way we describe and perform Avocado's packaging. Converting Avocado's If you want to experient with that, it'd be greatly appreciated. |
From the python 3.12 the setuptools are not part of python and needs to be installed separately. Let's update the release workflow to handle this issue until avocado-framework#5754 will be fixed. Signed-off-by: Jan Richter <[email protected]>
From the python 3.12 the setuptools are not part of python and needs to be installed separately. Let's update the release workflow to handle this issue until avocado-framework#5754 will be fixed. Signed-off-by: Jan Richter <[email protected]>
From the python 3.12 the setuptools are not part of python and needs to be installed separately. Let's update the release workflow to handle this issue until avocado-framework#5754 will be fixed. Signed-off-by: Jan Richter <[email protected]>
From the python 3.12 the setuptools are not part of python and needs to be installed separately. Let's update the release workflow to handle this issue until avocado-framework#5754 will be fixed. Signed-off-by: Jan Richter <[email protected]>
From the python 3.12 the setuptools are not part of python and needs to be installed separately. Let's update the release workflow to handle this issue until avocado-framework#5754 will be fixed. Signed-off-by: Jan Richter <[email protected]>
From the python 3.12 the setuptools are not part of python and needs to be installed separately. Let's update the release workflow to handle this issue until avocado-framework#5754 will be fixed. Signed-off-by: Jan Richter <[email protected]>
Describe the bug
When attempting to install Avocado from source using the
./setup.py install --user
command, I encountered several deprecation warnings. These warnings seem to be related to the use of deprecated setuptools features.Steps to reproduce
git clone https://github.com/avocado-framework/avocado.git
)cd avocado
)./setup.py build
./setup.py install --user
Expected behavior
The installation process should complete without any deprecation warnings.
Current behavior
The installation process emits multiple deprecation warnings related to setuptools. These warnings relate to:
setup.py install
being deprecatedavocado.etc.avocado.scripts.job
,avocado.etc.avocado.sysinfo
, andavocado.libexec
being installed as data, which is deprecatedSystem information
Additional information
Despite the warnings, the package appears to install successfully, but I am concerned that these warnings indicate potential future compatibility issues.
Here's a snippet of the warnings:
The text was updated successfully, but these errors were encountered: