Windows installer needs to be better documented, and preferably more self-contained #18
Comments
|
Removing version: 3.0.1 (automated comment) |
|
Added to the docs in <<changeset d6fe28e481fe (bb)>>. |
agronholm
added a commit
to agronholm/coveragepy
that referenced
this issue
Aug 16, 2020
These two backends have their own exception reporting which will print unnecessary messages to the console. This was now fixed with a wrapper that bypasses such invasive error handling. Fixes nedbat#18.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally reported by Geoff Bache (Bitbucket: geoffbache, GitHub: Unknown)
I tried to install the latest coverage on Windows using the Windows installer, but on running it just got a stack trace saying "No module named pkg_resources". I happened to know that that meant I needed to install setuptools, mostly because I'd already been through this process on Linux, but I guess many people wouldn't.
Even then it wasn't trivial either because there is still no Windows installer for setuptools with Python 2.6. A bit of googling got me there in the end, but maybe some notes on your website explaining this would save future Windows users some time.
The text was updated successfully, but these errors were encountered: