No description
Find a file
2024-01-25 23:25:10 -05:00
.github/workflows test: partial coverage state (#9) 2023-11-08 00:23:44 -05:00
cli refactor(cli): move cli+logger to own module 2024-01-25 23:22:47 -05:00
exec refactor(python): move python-specific logic to own module 2024-01-25 23:22:54 -05:00
integration ci: add basic integration test, pipeline step (#7) 2023-11-05 11:47:24 -05:00
logger refactor(python): move python-specific logic to own module 2024-01-25 23:22:54 -05:00
python refactor(python): move python commands under python module 2024-01-25 23:23:01 -05:00
scripts refactor(python): move python commands under python module 2024-01-25 23:23:01 -05:00
state refactor(state-mgmt): move state management code to own module 2024-01-25 23:21:06 -05:00
testutils refactor(python): move python-specific logic to own module 2024-01-25 23:22:54 -05:00
.gitignore feat: basic use,install,list,help,init functionality (#1) 2023-11-03 00:41:05 -04:00
commands.go refactor(python): move python commands under python module 2024-01-25 23:23:01 -05:00
go.mod test: partial coverage state (#9) 2023-11-08 00:23:44 -05:00
go.sum test: partial coverage state (#9) 2023-11-08 00:23:44 -05:00
LICENSE Initial commit 2023-10-30 23:30:00 -04:00
README.md feat: easier path setup through init --add-path (#6) 2023-11-05 10:41:43 -05:00
v.go refactor(python): move python commands under python module 2024-01-25 23:23:01 -05:00

v

A version manager you might not want to use.

Overview

v is a simple version manager inspired from other tools like asdf, pyenv, n and nvm. At it's core, it's a reinvention of the wheel with some extras.

  • First and foremost, while the first version is about Python version management, the plan is to expand to support a bunch more runtime (with an emphasis on simplifying adding more runtimes to manage);
  • A lot of those tools are written as shellscript, which I find somewhat inscrutable. Go is a bit easier to read;
  • ...? It's a reason to write some Go. :)

Roadmap

While the plan for the first release is to only support Python runtimes, expanding to others will be next so that v can just handle all/most version management needs.

Usage

Building your own and setting up

Pre-built binaries are not currently available. You can clone the repository and build your own via . scripts/build.

You should find a suitable place for the binary (/usr/local/bin is a good location) and if not already included, add its location to $PATH.

Finally, run v init to create directories to store artifacts and state (under ~/.v unless override using the V_ROOT environment variable). The following should also be added to your shell's configuration (i.e. .zshrc, .bashrc, ...):

export PATH=<path-to-v-executable>:$PATH
eval "$(v init --add-path)"

This will handle adding shim paths to your shell without hassle.

Usage

v will print a helpful list of available commands.

The most important things to know include v install <version> to install new versions and v use <installed version> to use a specific version of Python.

Contributing

The project isn't currently accepting contributions because it's not yet set up to do so. Stay tuned.