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 in the venv 6. Install coverage in the venv -- full_coverage.py run -- 7. Run coverage -- full_coverage.py html -- 8. Create coverage report *outside of venv* -- 9. Delete venv *but leave the setuptools and coverage tarballs for users* This removes the need for the coverage clone and a lot of the crazy tweaking required to execute Python for fullcoverage; this setup will only require setting PYTHONPATH to src/coverage/fullcoverage (or something like that) in the venv. ---------- assignee: -> brett.cannon _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18367> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
