This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients brett.cannon
Date 2013-07-12.20:17:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1373660260.04.0.67024518657.issue18366@psf.upfronthosting.co.za>
In-reply-to
Content
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)
History
Date User Action Args
2013-07-12 20:17:40brett.cannonsetrecipients: + brett.cannon
2013-07-12 20:17:40brett.cannonsetmessageid: <1373660260.04.0.67024518657.issue18366@psf.upfronthosting.co.za>
2013-07-12 20:17:40brett.cannonlinkissue18366 messages
2013-07-12 20:17:39brett.cannoncreate