➜
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.
Created on 2013-07-05 18:55 by brett.cannon, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg192343 - (view) | Author: Brett Cannon (brett.cannon) *  |
Date: 2013-07-05 18:55 | |
Setuptools 0.8 uses a Python 2/3 compatible codebase so it should simplify the instructions for running coverage.py. |
|||
| msg192966 - (view) | Author: Brett Cannon (brett.cannon) * |
Date: 2013-07-12 20:17 | |
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) |
|||
| msg193054 - (view) | Author: Brett Cannon (brett.cannon) * |
Date: 2013-07-14 15:09 | |
Setuptools 0.8 will work fine. See issue #18367 for its planned use. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:47 | admin | set | github: 62566 |
| 2013-07-14 15:09:18 | brett.cannon | set | status: open -> closed resolution: fixed messages: + msg193054 |
| 2013-07-12 20:17:40 | brett.cannon | set | messages: + msg192966 |
| 2013-07-05 18:55:45 | brett.cannon | create | |