chrysle
chrysle
I think this could be a useful feature. But I don't see another way than passing the attribute's name by hand. It should of course be possible to configure the...
Thanks for raising this! Apparently the `package_name_from_spec` function is run over the packages to preinstall, which shouldn't be: https://github.com/pypa/pipx/blob/c44d210649b8cad08f5368d6f01bc870fb34115b/src/pipx/commands/install.py#L94 Would you like to submit a quick fix?
I must admit I also wasn't aware of that entry point. Thanks for raising this issue!
> `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...
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.
Python 3.8 & 3.9 are now supported on MacOS 14.
> unless you specifically would like to have an old Intel runner job too, but they will probably go away at some point. Probably that would be a good idea?...
Thanks for the PR nontheless, then! (It'd be appreciated if you could have a look at #1246, BTW; probably I'm doing something fundamentally wrong).
I think it would be good to enable configuring standard `pip` args via an environment variable, thanks for raising this issue! I'll have a look today.
For me, with 1.5.0 `pipx`-managed `pip` _can_ access the configuration. Have you set it globally? Also, if you run `pip` in one of your venvs and list the config, it...