Closed agjohnson closed 1 year ago
When we talked about this one, @humitos raised issues about .tool-versions
changing suddenly. This could be a problem, though with a repository configuration that uses NPM and Poetry, the system dependencies can change underneath without affecting the installed dependencies.
Yeah, I wish there was some concept of version selection like that in asdf. There are a few issues, like https://github.com/asdf-vm/asdf/issues/352, that discuss some maybe options, but seems this feature was specifically ruled out.
At least with poetry abstracting the Python version a little, it's mostly just wasting the space for each Python core installation, but even a bare installation is about 250MB per install :/
We've talked about checking in the
asdf
configuration file for explicit version management of system dependencies in the past. This is a lightweight version of that that gives an explicit way to get started. Usingasdf
locally is out of the scope of documentation here, it's a system level dependency.:books: Documentation preview :books:: https://read-the-docs-site-community--173.com.readthedocs.build/en/173/