No description
Find a file
Marc Cataford 5e245f11cc
refactor: url.JoinPath and state path.Join abstraction instead of fmt… (#5)
* refactor: url.JoinPath and state path.Join abstraction instead of fmt.Sprintf

* refactor: version composition with fmt.Sprintf
2023-11-05 10:19:53 -05:00
scripts refactor: simplify project structure (#2) 2023-11-04 21:28:11 -04:00
.gitignore feat: basic use,install,list,help,init functionality (#1) 2023-11-03 00:41:05 -04:00
cli.go feat: use cached archive if available, allow skip using --no-cache (#3) 2023-11-04 21:54:58 -04:00
commands.go refactor: url.JoinPath and state path.Join abstraction instead of fmt… (#5) 2023-11-05 10:19:53 -05:00
go.mod feat: basic use,install,list,help,init functionality (#1) 2023-11-03 00:41:05 -04:00
install_python.go refactor: url.JoinPath and state path.Join abstraction instead of fmt… (#5) 2023-11-05 10:19:53 -05:00
LICENSE Initial commit 2023-10-30 23:30:00 -04:00
README.md feat: basic use,install,list,help,init functionality (#1) 2023-11-03 00:41:05 -04:00
state.go refactor: url.JoinPath and state path.Join abstraction instead of fmt… (#5) 2023-11-05 10:19:53 -05:00
util.go refactor: simplify project structure (#2) 2023-11-04 21:28:11 -04:00
v.go fix: shim should use v executable from $PATH (#4) 2023-11-05 09:44:56 -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) and add ~/.v/shims to your $PATH as well.

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.