pip install chumpy------> ERROR mesage

[flydragon2018]

ModuleNotFoundError: No module named 'pip'
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

[flydragon2018]

I need to install chumpy again recently.
so I delete pip first from the site-packages,
then

python -m ensurepip --upgrade

the pip version is 20.0.2

chumpy 0.69 was installed early,

pip install chumpy==0.70 --ignore-installed requests

[Mwni]

pip install wheel

solves this

[matthewfranglen]

I have this issue when installing chumpy in a poetry virtual environment. It occurs for versions 0.70, 0.69, 0.68, 0.67.7. I was able to install 0.66.

➜ PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring poetry add 'chumpy<0.68'

Updating dependencies
Resolving dependencies... (6.3s)

Package operations: 1 install, 0 updates, 0 removals

  • Installing chumpy (0.67.7): Failed

  ChefBuildError

  Backend subprocess exited when trying to invoke get_requires_for_build_wheel

  Traceback (most recent call last):
    File "<string>", line 9, in <module>
  ModuleNotFoundError: No module named 'pip'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/home/matthew/.local/pipx/venvs/poetry/lib/python3.10/site-packages/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
      main()
    File "/home/matthew/.local/pipx/venvs/poetry/lib/python3.10/site-packages/pyproject_hooks/_in_process/_in_process.py", line 335, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
    File "/home/matthew/.local/pipx/venvs/poetry/lib/python3.10/site-packages/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
      return hook(config_settings)
    File "/tmp/tmpj1kw8j7d/.venv/lib/python3.10/site-packages/setuptools/build_meta.py", line 355, in get_requires_for_build_wheel
      return self._get_build_requires(config_settings, requirements=['wheel'])
    File "/tmp/tmpj1kw8j7d/.venv/lib/python3.10/site-packages/setuptools/build_meta.py", line 325, in _get_build_requires
      self.run_setup()
    File "/tmp/tmpj1kw8j7d/.venv/lib/python3.10/site-packages/setuptools/build_meta.py", line 507, in run_setup
      super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)
    File "/tmp/tmpj1kw8j7d/.venv/lib/python3.10/site-packages/setuptools/build_meta.py", line 341, in run_setup
      exec(code, locals())
    File "<string>", line 11, in <module>
  ModuleNotFoundError: No module named 'pip'


  at ~/.local/pipx/venvs/poetry/lib/python3.10/site-packages/poetry/installation/chef.py:147 in _prepare
      143│
      144│                 error = ChefBuildError("\n\n".join(message_parts))
      145│
      146│             if error is not None:
    → 147│                 raise error from None
      148│
      149│             return path
      150│
      151│     def _prepare_sdist(self, archive: Path, destination: Path | None = None) -> Path:

Note: This error originates from the build backend, and is likely not a problem with poetry but with chumpy (0.67.7) not supporting PEP 517 builds. You can verify this by running 'pip wheel --use-pep517 "chumpy (==0.67.7)"'.

[4d30]

Would be nice to add wheel to requirements

[elisa-aleman]

I have this issue when installing chumpy in a poetry virtual environment. It occurs for versions 0.70, 0.69, 0.68, 0.67.7. I was able to install 0.66.

➜ PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring poetry add 'chumpy<0.68'



Updating dependencies

Resolving dependencies... (6.3s)



Package operations: 1 install, 0 updates, 0 removals



  • Installing chumpy (0.67.7): Failed



  ChefBuildError



  Backend subprocess exited when trying to invoke get_requires_for_build_wheel



  Traceback (most recent call last):

    File "<string>", line 9, in <module>

  ModuleNotFoundError: No module named 'pip'



  During handling of the above exception, another exception occurred:



  Traceback (most recent call last):

    File "/home/matthew/.local/pipx/venvs/poetry/lib/python3.10/site-packages/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>

      main()

    File "/home/matthew/.local/pipx/venvs/poetry/lib/python3.10/site-packages/pyproject_hooks/_in_process/_in_process.py", line 335, in main

      json_out['return_val'] = hook(**hook_input['kwargs'])

    File "/home/matthew/.local/pipx/venvs/poetry/lib/python3.10/site-packages/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel

      return hook(config_settings)

    File "/tmp/tmpj1kw8j7d/.venv/lib/python3.10/site-packages/setuptools/build_meta.py", line 355, in get_requires_for_build_wheel

      return self._get_build_requires(config_settings, requirements=['wheel'])

    File "/tmp/tmpj1kw8j7d/.venv/lib/python3.10/site-packages/setuptools/build_meta.py", line 325, in _get_build_requires

      self.run_setup()

    File "/tmp/tmpj1kw8j7d/.venv/lib/python3.10/site-packages/setuptools/build_meta.py", line 507, in run_setup

      super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)

    File "/tmp/tmpj1kw8j7d/.venv/lib/python3.10/site-packages/setuptools/build_meta.py", line 341, in run_setup

      exec(code, locals())

    File "<string>", line 11, in <module>

  ModuleNotFoundError: No module named 'pip'





  at ~/.local/pipx/venvs/poetry/lib/python3.10/site-packages/poetry/installation/chef.py:147 in _prepare

      143│

      144│                 error = ChefBuildError("\n\n".join(message_parts))

      145│

      146│             if error is not None:

    → 147│                 raise error from None

      148│

      149│             return path

      150│

      151│     def _prepare_sdist(self, archive: Path, destination: Path | None = None) -> Path:



Note: This error originates from the build backend, and is likely not a problem with poetry but with chumpy (0.67.7) not supporting PEP 517 builds. You can verify this by running 'pip wheel --use-pep517 "chumpy (==0.67.7)"'.

I also had this issue and this this as a workaround #56 (comment)