Brett Cannon added the comment: So this actually works out very nicely. The basic steps are:
1. Download ez_setup.py for setuptools 2. Create a venv 3. Install coverage.py (build actually works as expected which was a pleasant surprise) 4. Run coverage.py with PYTHONPATH set to fullcoverage as if coverage.py was installed 5. Generate coverage report as normal 6. Delete the venv (since coverage/tracer.so will not be built for the user's binary and they will be on a different platform which means the venv won't be linked properly, etc.) 7. Wipe out the built files in the coverage.py checkout (or just blow out the clone and re-clone) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18366> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
