Skip to content
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

pipx does not find dependencies from extras #534

Closed
itsayellow opened this issue Oct 24, 2020 · 0 comments · Fixed by #593
Closed

pipx does not find dependencies from extras #534

itsayellow opened this issue Oct 24, 2020 · 0 comments · Fixed by #593

Comments

@itsayellow
Copy link
Contributor

Describe the bug

pipx accurately installs from a package spec with extras, but it does not keep track of the dependencies from extras in its metadata.

Consequently, using the argument --include-deps with install will not install the apps of the dependencies from extras.

The problem is that we only supply the name of the main package to venv_metadata_inspector.py and not its extras.

Is there a way to determine the extras used to install a package from the venv? I was unable to find any.

How to reproduce

> pipx install 'nox[tox_to_nox]' --include-deps
⚠️  Note: register-python-argcomplete was already on your PATH at /usr/local/bin/register-python-argcomplete
  installed package nox 2020.8.22, Python 3.9.0
  These apps are now globally available
    - activate-global-python-argcomplete
    - nox
    - python-argcomplete-check-easy-install-script
    - python-argcomplete-tcsh
    - register-python-argcomplete
    - tox-to-nox
    - virtualenv
done! ✨ 🌟 ✨

Expected behavior

Since tox is installed to the venv with extra tox_to_nox, the app tox should have been exposed.

Also, viewing pipx_metadata.json in the nox venv shows no mention of the extra packages in app_paths_of_dependencies or apps_of_dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant