Open kpeez opened 8 months ago
I had the same issue, as a workaround I used poetry to make a PEP517 compliant whl.
git clone --depth 1 https://github.com/mattloper/chumpy.git && \
cd chumpy && \
poetry init \
--name "chumpy" \
--description "chumpy (poetry build)" \
--author "Matthew Loper" \
--license "MIT" \
--no-interaction && \
poetry version $(python -c 'import runpy;print(runpy.run_path("./chumpy/version.py")["version"])') && \
poetry add numpy@* scipy@* six@* && \
poetry build
This generates a PEP 517 compliant pyproject.toml which could be used to update this package by the author.
This makes installation with pixi
failed, too
Issue Description
The
chumpy
package'ssetup.py
file currently attempts to importpip
during the installation process, as shown in the following lines:There are a couple of problems with this approach:
--use-pep517
flag withpip
(which will become the default behavior in the future), or when using other PEP 517-compliant build tools, the installation process fails with a ModuleNotFoundError: No module named 'pip' error. This is because pip is not guaranteed to be available during the installation process when PEP 517 is used.pip
availability: Even without using PEP 517, the assumption thatpip
is installed and available during the package installation process is incorrect. Some package managers or environments may not includepip
by default, leading to the sameModuleNotFoundError
.Steps to reproduce
chumpy
usingpip
with the--use-pep517
flag: