You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running topgrade, pipx is the slowest step when there are no upgrades
Describe the solution you'd like
pipx upgrade-all should check if upgrades are available in parallel. It’s fine if they’re upgraded in sequence, but taking 2 seconds to check if 3 tools have upgrades pending is a bit slow.
Maybe using a connection pool with limited size if we want to overengineer things. I assume for most users, starting x requests, where x is the number of installed tools would be fine.
Describe alternatives you've considered
none
The text was updated successfully, but these errors were encountered:
pipx upgrade-all should check if upgrades are available in parallel. It’s fine if they’re upgraded in parallel, but taking 2 seconds to check if 3 tools have upgrades pending is a bit slow.
I think this would best be tackled after #149 has been addressed, as then we'll be able to handle requests to the simple API for newer versions in parallel.
How would this feature be useful?
When running
topgrade
, pipx is the slowest step when there are no upgradesDescribe the solution you'd like
pipx upgrade-all
should check if upgrades are available in parallel. It’s fine if they’re upgraded in sequence, but taking 2 seconds to check if 3 tools have upgrades pending is a bit slow.Maybe using a connection pool with limited size if we want to overengineer things. I assume for most users, starting x requests, where x is the number of installed tools would be fine.
Describe alternatives you've considered
none
The text was updated successfully, but these errors were encountered: