top | item 40113998

(no title)

eclipsetheworld | 1 year ago

This looks really cool! Working on multiple projects with different versions before tools like pyenv or nvm existed was a real challenge. As someone working with different programming languages as well, this tool looks like the next logical step.

discuss

order

rjzzleep|1 year ago

asdf works great for that purpose. And you can either use a single .tool-versions file or enable legacy support for compatibility with pyenv rbenv etc.

Plus is supports many more tools than just the language vms

https://asdf-vm.com/

magnio|1 year ago

I wanted to like asdf but 1. it's slow, and 2. not available on Windows proper (non-WSL). Same with mise (https://github.com/jdx/mise) which builds on asdf.

Volta exists but alas, it's only for JavaScript.

aooohan|1 year ago

But it does nothing for Windows.

devmor|1 year ago

pyenv is still the best solution to this problem I have yet to see - wish it existed for everything

tyingq|1 year ago

It does have upsides. Though the python runtime version management story suffers from being fragmented. It gets complex if you add poetry, IDEs, different types of shells (gitbash, power shell, zsh, etc), things that have their own ideas of environments (Jupyter as one example).

aooohan|1 year ago

Honestly, the python plugin is a bit problematic on Windows at the moment, the next plugin version should fix that.

But on unix it is also built using python-build. For me, a light python user, there is no difference between using vfox and using pyenv.