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

Support built-in “venv” #173

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open

Support built-in “venv” #173

wants to merge 8 commits into from

Commits on Jan 10, 2018

  1. Configuration menu
    Copy the full SHA
    8ed7afb View commit details
    Browse the repository at this point in the history

Commits on Jan 18, 2018

  1. Beefing up tests so Tox works for 3.5+ on macOS

    Need a newer Virtualenv for 3.6, and newer Pytest for 3.5+, so the
    requirements.txt are modified to allow newer versions.
    
    Path of tmpdir on macOS is a symlink and need to be resolved explicitly
    to prevent the check from failing.
    
    Some tests are beefed up to help pinpoint the problem more accurately.
    uranusjr committed Jan 18, 2018
    Configuration menu
    Copy the full SHA
    e72ece5 View commit details
    Browse the repository at this point in the history
  2. Refactor some run-time constants to _utils

    So we can use it in the venv backend implementation.
    uranusjr committed Jan 18, 2018
    Configuration menu
    Copy the full SHA
    79ae559 View commit details
    Browse the repository at this point in the history
  3. Implement venv backend

    The venv backend is used by default when "venv" and "ensurepip" are
    available (i.e. Python 3.4+). This can be disabled with the
    PEW_USE_VIRTUALENV environ.
    
    Certain tests are skipped:
    
    @skip_venv
    Test makes assumptions that do not fit venv's structure. The
    functionality is implemented, but the check is logically incompatible
    with how venv does things.
    
    @skip_venv_site_packages
    Same as above, but specifically this has something to do with venv's
    central configuration file, and can be fixed by implementing a parallel
    test.
    
    @skip_venv_cp
    This uses the "pew cp" command, which is not implemented yet. I will try
    to eliminate them if possible.
    uranusjr committed Jan 18, 2018
    Configuration menu
    Copy the full SHA
    e961bec View commit details
    Browse the repository at this point in the history

Commits on Jan 22, 2018

  1. Configuration menu
    Copy the full SHA
    e0b7cf0 View commit details
    Browse the repository at this point in the history
  2. Try harder to find Python for venv in a virtualenv

    This provide a more hard-nose effort to find a real Python in all places
    possible. Should work if you install Python from the standard CPython
    distribution. If not, I don't know what will.
    uranusjr committed Jan 22, 2018
    Configuration menu
    Copy the full SHA
    c1943cf View commit details
    Browse the repository at this point in the history

Commits on Jan 27, 2018

  1. Configuration menu
    Copy the full SHA
    dba8b36 View commit details
    Browse the repository at this point in the history
  2. Ugly hack to work around activate script perms

    Add the write permission to all activate scripts before copying the
    venv if needed, and restore all modified files after cloning.
    
    Why this is needed:
    #173 (comment)
    uranusjr committed Jan 27, 2018
    Configuration menu
    Copy the full SHA
    c25f19e View commit details
    Browse the repository at this point in the history