-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Remove support for installed .egg
distributions when using the importlib.metadata
backend
#12330
Comments
- removed old and unused directories - added the new project manager according to [PEP621](https://peps.python.org/pep-0621/), (pypa/pip#12330)
@hanivianka have you tried the recommended action mentioned in the top post of this page? |
@sbidoul has pip 24.3 been released? im tired of seeing the bright message pop up on an otherwise dark screen |
@tahayparker 24.3 is planned for October 2024. It is important that affected users resolve the warning by applying the recommendation in the first post of this page. |
The problem is based on PIP updating. update to 23.3.2, rebuild the build. first, delete the build and the dist plus the .egg.info folder. build build:
then, the twine:
view document here: Packaging Python Projects |
$ pip install --upgrade --force-reinstall pipes
Defaulting to user installation because normal site-packages is not writeable
DEPRECATION: Loading egg at /usr/lib/python3.13/site-packages/gpg-1.23.2-py3.13-linux-x86_64.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at https://github.com/pypa/pip/issues/12330
ERROR: Could not find a version that satisfies the requirement pipes (from versions: none)
ERROR: No matching distribution found for pipes
$ pip3 install --upgrade --force-reinstall pipes
Defaulting to user installation because normal site-packages is not writeable
DEPRECATION: Loading egg at /usr/lib/python3.13/site-packages/gpg-1.23.2-py3.13-linux-x86_64.egg is deprecated. pip 25.1 will enforce this behaviour change. A possible replacement is to use pip for package installation. Discussion can be found at https://github.com/pypa/pip/issues/12330
ERROR: Could not find a version that satisfies the requirement pipes (from versions: none)
ERROR: No matching distribution found for pipes What should I do? Please Help someone |
@jdu211171 at first glance it seems like a distro level install is broken Please report this to your distro |
mamba run pip install -U smp build twine |
Nice to see that NGC containers e.g. https://catalog.ngc.nvidia.com/orgs/nvidia/containers/pytorch/tags have this problem still.
😭 |
Before this PR different versions of `triton-kernels-benchmark` can coexist, which is an unexpected/incorrect behavior. And it is possible that the old version has a hash that is lexicographically higher in the sort, which causes the old version to be unexpectedly used. More details can be found here: pypa/pip#12330 Signed-off-by: Whitney Tsang <[email protected]>
@sbidoul We do not have .egg-info dirs in the .zip file, if that's what you mean. The .zip file is on sys.path. The warning we're seeing is this:
|
Followup: the zip file does contain these kinds of entries:
If I remove the .dist-info folder, the warning goes away. |
Hmm, I’m not even sure loading .dist-info from a zip is even an intended feature, or if we want to continue support it or not. The warning (and the wholde deprecation) is supposed to only apply to loading .egg-info from a zip. We should have a separate issue to discuss this. |
pip has dropped support for installing
.egg
distributions when it stopped invokingsetup.py install
.At some point pip will abandon support for detecting and uninstalling legacy
.egg
distributions too.If you reach this issue from the pip deprecation message, it is likely that your Python environment has distributions that have been installed with
setup.py install
,easy_install
, or an older pip version.The recommended action is to uninstall the distribution and reinstall it with a recent pip.
The text was updated successfully, but these errors were encountered: