asdf-python VS asdf

Point of clarification: asdf uses python-build which is from pyenv.

https://github.com/asdf-community/asdf-python?tab=readme-ov-...

[env] # supports arbitrary env vars so mise can be used like direnv/dotenv NODE_ENV = 'production' [tools] # specify single or multiple versions terraform = '1.0.0' erlang = ['23.3', '24.0'] # supports everything you can do with .tool-versions currently node = ['16', 'prefix:20', 'ref:master', 'path:~/.nodes/14'] # send arbitrary options to the plugin, passed as: # MISE_TOOL_OPTS\_\_VENV=.venv python = {version='3.10', virtualenv='.venv'} [plugins] # specify a custom repo url # note this will only be used if the plugin does not already exist python = 'https://github.com/asdf-community/asdf-python' [alias.node] # project-local aliases my_custom_node = '20'

Yeah, I should've been more precise. The asdf plugins use parts of existing systems. For example (python/ruby/node)-build which mostly come from other version managers. Asdf does provide extras, but the plugin-specific code is tiny: https://github.com/asdf-community/asdf-python/blob/master/bi...

❯ asdf plugin-list --urls --refs act https://github.com/grimoh/asdf-act.git master 8729029 aws-vault https://github.com/beardix/asdf-aws-vault.git master 937a1db awscli https://github.com/MetricMike/asdf-awscli.git main b9ba4c7 docker-slim https://github.com/everpeace/asdf-docker-slim.git master 4ee75a3 golang https://github.com/kennyp/asdf-golang.git master 1f388f1 helm https://github.com/Antiarchitect/asdf-helm.git master 87eef5a java https://github.com/halcyon/asdf-java.git master f0c702f jq https://github.com/ryodocx/asdf-jq.git master 3144577 kubectl https://github.com/asdf-community/asdf-kubectl.git master da7bb0b minikube https://github.com/alvarobp/asdf-minikube.git master 8ca7b8d mysql https://github.com/iroddis/asdf-mysql.git master 3aaf756 nodejs https://github.com/asdf-vm/asdf-nodejs.git master cb61e3d perl https://github.com/ouest/asdf-perl.git master 31bb799 php https://github.com/asdf-community/asdf-php.git master 759843b postgres https://github.com/smashedtoatoms/asdf-postgres.git master 4f8b356 python https://github.com/danhper/asdf-python.git master 8ab052f redis https://github.com/smashedtoatoms/asdf-redis.git master bf1276e ruby https://github.com/asdf-vm/asdf-ruby.git master f134c2d sbt https://github.com/bram2000/asdf-sbt.git master 33f9637 scala https://github.com/asdf-community/asdf-scala.git master 1206055 skaffold https://github.com/virtualstaticvoid/asdf-skaffold.git master c942ecf spark https://github.com/joshuaballoch/asdf-spark.git master 6fe49de

You could look at what a new $PATH file looks like by spinning up a new VM or google around for default path examples. As for your dependency issues, I like to use poetry and asdf to keep things straight.

I use asdf and its Python plugin [1] to install Python interpreter versions.

For managing virtual environments on my preferred shell (Fish), I use (and maintain) VirtualFish [2].

For managing project dependencies, I activate environments via VirtualFish and then use Poetry [3] to update the dependencies within the environments.

[1]: https://github.com/danhper/asdf-python

[2]: http://github.com/justinmayer/virtualfish

[3]: http://python-poetry.org

The main issue most people have with asdf is that it’s annoyingly slow. Not unusably so, but just enough that it’s irritating.

I identified [0] the source for much of it (sub-shells and pipes) and began a PR [1], but became bogged down with BATS testing, and then found mise / rtx, so kind of lost interest. Sorry. You can always implement these if you’d like.

[0]: https://github.com/asdf-vm/asdf/issues/290#issuecomment-1383...

[1]: https://github.com/asdf-vm/asdf/pull/1441

Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions

https://asdf-vm.com/

Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?

These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…

We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).

(asdf)[https://asdf-vm.com/] fully supports Python and almost any other language. I've been using it for Ruby, Python, Elixir, and other languages for years and never looked back.

Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).

There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:

I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.