jaraco
commented
1 month ago I've confirmed the issue can be replicated simply:
draft 🐚 pip download setuptools
Collecting setuptools
Using cached setuptools-74.1.2-py3-none-any.whl.metadata (6.7 kB)
Using cached setuptools-74.1.2-py3-none-any.whl (1.3 MB)
Saved ./setuptools-74.1.2-py3-none-any.whl
Successfully downloaded setuptools
draft 🐚 py -c 'import setuptools'
Traceback (most recent call last):
File "<string>", line 1, in <module>
import setuptools
ModuleNotFoundError: No module named 'setuptools'
draft [1] 🐚 env PYTHONPATH=./setuptools-74.1.2-py3-none-any.whl py -c 'import setuptools'
Traceback (most recent call last):
File "<string>", line 1, in <module>
import setuptools
File "/Users/jaraco/draft/setuptools-74.1.2-py3-none-any.whl/setuptools/__init__.py", line 27, in <module>
from .dist import Distribution
File "/Users/jaraco/draft/setuptools-74.1.2-py3-none-any.whl/setuptools/dist.py", line 18, in <module>
from . import (
...<3 lines>...
)
File "/Users/jaraco/draft/setuptools-74.1.2-py3-none-any.whl/setuptools/_entry_points.py", line 5, in <module>
from jaraco.functools import pass_none
ModuleNotFoundError: No module named 'jaraco'
gaborbernat
In https://github.com/pypa/setuptools/pull/4457#discussion_r1748703788_, @gaborbernat reported that the simplified vendoring strategy means vendored dependencies are no longer working for zipimporter archives.
Although the best recommended solution is for downstream integrators to incorporate the dependencies (
setuptools[core]) naturally, it would be nice if the vendoring could continue to work until dependencies can be fully declared naturally (e.g. undersetuptools).