Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correctly handle producing multiple Venvs for the same python version #32

Merged
merged 1 commit into from
Mar 19, 2024

Commits on Mar 19, 2024

  1. Correctly handle producing multiple Venvs for the same python version

    I had about 80% of the approach implemented from day one - we already
    checked a map to see if we'd already seen that version. The problem was
    we never set anything in it so it was always empty.
    
    This also tidies up the tests a bit, and removes the needless link to
    `/usr/local/include/python3.7m` for >=Py3.8 (which doesn't need it)
    
    I used `coreos/go-semver` for Semver parsing as that was already in our
    dep tree
    ashb committed Mar 19, 2024
    Configuration menu
    Copy the full SHA
    00a2a8e View commit details
    Browse the repository at this point in the history