How would this feature be useful?
Hey! First of all thanks for the amazing work 🌈
I'm using pipx to manage multiple Poetry versions on my machine and it works like a charm!
However, I have to remember which version I'm using in each project and add the correct suffix to every command.
Describe the solution you'd like
I'd love to have a way to "bind" a pipx executable to one of the available suffixes when running commands in a certain folder, similar to how PyEnv does with the .python-version file and the pyenv local <python-version> command.
Describe alternatives you've considered
I'm currently solving this by defining a shell function called poetry that checks the current directory, looks for a file called .poetry-version to check the pinned version for the project, and then calls poetry@<version>.
This works kind of OK, but it's shell dependant and does not scale really well to multiple tools.
It would be amazing to have this as a baked-in functionality!
How would this feature be useful?
Hey! First of all thanks for the amazing work 🌈
I'm using
pipxto manage multiple Poetry versions on my machine and it works like a charm!However, I have to remember which version I'm using in each project and add the correct suffix to every command.
Describe the solution you'd like
I'd love to have a way to "bind" a pipx executable to one of the available suffixes when running commands in a certain folder, similar to how PyEnv does with the
.python-versionfile and thepyenv local <python-version>command.Describe alternatives you've considered
I'm currently solving this by defining a shell function called
poetrythat checks the current directory, looks for a file called.poetry-versionto check the pinned version for the project, and then callspoetry@<version>.This works kind of OK, but it's shell dependant and does not scale really well to multiple tools.
It would be amazing to have this as a baked-in functionality!