[issue18367] See if a venv setup can be used for devinabox for coverage

Changes by Brett Cannon : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue18367] See if a venv setup can be used for devinabox for coverage

Brett Cannon added the comment: I think getting set up for coverage.py is going to change to: 1. Download the latest setuptools 2. Download the latest coverage -- full_coverage.py build -- 3. Create a venv 4. Extract setuptools and coverage into a src/ directory in the venv 5. Install setuptools

[issue18367] See if a venv setup can be used for devinabox for coverage

Brett Cannon added the comment: So first thing is that you can't relocate a venv. The --upgrade option is only for when you upgrade a Python installation in-place (e.g. go from 3.3 to 3.4 but otherwise all other details stay the same). The --clear option empties out the directories so nothing

[issue18367] See if a venv setup can be used for devinabox for coverage

New submission from Brett Cannon: Right now there is a bunch of contorting with setuptools and coverage.py's checkout to get things in reasonable places, etc. Might be easiest to create a venv from the built checkout and then install both setuptools and the coverage.py checkout into the venv f