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

Modifying existing environment still attempts to reinstall existing packages #1568

Closed
FriedrichFroebel opened this issue Nov 5, 2024 · 2 comments

Comments

@FriedrichFroebel
Copy link

Describe the bug

Trying to install the ocrodjvu with the --force option attempts to build a dependency which is already installed in the virtual environment.

How to reproduce

Running pipx install ocrodjvu fails due to some incompatibilities for python-djvulibre (the PyPI package is broken and I am waiting for a maintainer transfer). Thus I am trying to work with an existing environment:

  • /usr/bin/python3 -m venv /home/user/.local/share/pipx/venvs/ocrodjvu
  • /home/user/.local/share/pipx/venvs/ocrodjvu/bin/python -m pip --no-input install 'git+https://github.com/FriedrichFroebel/python-djvulibre.git'
  • /home/user/.local/share/pipx/venvs/ocrodjvu/bin/python -m pip show python-djvulibre
  • pipx install --force --verbose ocrodjvu

This attempts to re-build python-djvulibre (from PyPI) and fails due to known incompatibilities.

Expected behavior

pipx install --force should re-use the existing virtual environment and not attempt to re-install python-djvulibre as stated in the help:

  --force, -f           Modify existing virtual environment and files in PIPX_BIN_DIR and PIPX_MAN_DIR
@huxuan
Copy link
Member

huxuan commented Jan 30, 2025

Sorry for the misleading, but as described in the help message, --force will Modify existing virtual environment and files. So I think the behavior is expected. Anyway, feel free to reopen the issue if necessary.

@huxuan huxuan closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2025
@FriedrichFroebel
Copy link
Author

Thanks for the explanation. In the meantime, the actual upstream issue has been fixed, thus I do not need the workaround I tried here anymore.

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

No branches or pull requests

2 participants