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.

Sign up for GitHub

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

Jump to bottom

Use 'python3 -m venv' instead of virtualenv #15754

Merged
merged 4 commits into from
Jan 24, 2020
Merged

Use 'python3 -m venv' instead of virtualenv #15754

merged 4 commits into from
Jan 24, 2020

Commits on Jan 23, 2020

  1. Use 'python3 -m venv' instead of virtualenv 

    Switch over to `python3 -m venv` instead of `virtualenv`. It's the recommended way to create virtual Python environments in 3.4 and above.

https://docs.python.org/3/library/venv.html
    @andrewkroh
    andrewkroh committed Jan 23, 2020
    Configuration menu
    Copy the full SHA
    f0fde9a View commit details
    Browse the repository at this point in the history

  2. Update references to 'python' to $pythonExe 

    Remove any direct references to python to always allow
a specific python binary or version to be used.
    @andrewkroh
    andrewkroh committed Jan 23, 2020
    Configuration menu
    Copy the full SHA
    7d505d9 View commit details
    Browse the repository at this point in the history

  3. Update Dockerfiles to use python3

    @andrewkroh
    andrewkroh committed Jan 23, 2020
    Configuration menu
    Copy the full SHA
    06153c3 View commit details
    Browse the repository at this point in the history

  4. Update Travis and Vagrantfile

    @andrewkroh
    andrewkroh committed Jan 23, 2020
    Configuration menu
    Copy the full SHA
    75b9e8b View commit details
    Browse the repository at this point in the history