Feature request: add skip argument to upgrade-all command
See original GitHub issueHi! I’ve recently discovered that running pipx upgrade
on a particular package breaks the symlink. To reproduce:
- Install
unimatrix
with
pipx install unimatrix --spec git+https://github.com/will8211/unimatrix --verbose
- Check that
unimatrix
binary is correctly symlinked (for instance withwhich unimatrix
) - Run
pipx upgrade unimatrix
-> for some reason pipx this upgradesunimatrix
to 0.1 which isn’t a tagged release - Now try running
unimatrix
orwhich unimatrix
: it doesn’t work since the symlink seems to be broken.
Please let me know if you can reproduce. Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:17
Top Results From Across the Web
Add an upgrade-all command · Issue #4551 · pypa/pip - GitHub
This feature request is purely a pip-specific feature, about "I have a bunch of packages in an environment, and I want to bump...
Read more >AutoUpgrade Command-Line Parameters and Options
Review the AutoUpgrade parameters and select the parameters and options for your Oracle Database upgrade use case.
Read more >Upgrade - Chocolatey Software Docs
NOTE all is a special package keyword that will allow you to upgrade all currently installed packages. Skip upgrading certain packages with choco...
Read more >How to upgrade all Python packages with pip? - Stack Overflow
The grep is to skip editable ("-e") package definitions, as suggested by @jawache. (Yes, you could replace grep + cut with sed or...
Read more >pacman - ArchWiki
Use the #Querying package databases command to view the optional dependencies of a package. When installing a package which you require only as ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yup that is the fix. (An alternate fix is to store a mapping of
--spec
to pipx-installed packages, but I am hesitant to add that)Fixed in my previous comment; still the same output
Running
./pip install -U unimatrix
from within the venv also updates the package so it seems to be a problem with pip then which believe the 0.1 to supersede the 0.1.dev version.Anyways I can leave the issue open and change the title if you are willing to add the ignore flag to the upgrade-all command