[issue2403] Add figleaf coverage metrics

Changes by Berker Peksag : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue2403] Add figleaf coverage metrics

Mark Lawrence added the comment: As there have been no replies to msg213358 can someone close this please. -- nosy: +BreamoreBoy status: pending -> open versions: +Python 3.5 -Python 3.3 ___ Python tracker _

[issue2403] Add figleaf coverage metrics

Éric Araujo added the comment: Indeed, the devguide documents how to use coverage.py, and there is even a pure-stdlib solution with regrtest. I recommend closing this. -- resolution: -> rejected stage: test needed -> committed/rejected status: open -> pending

[issue2403] Add figleaf coverage metrics

Sandro Tosi added the comment: The devguide reports a long section about code convering cpython: http://docs.python.org/devguide/coverage.html . It uses Ned's coverege.py and has a lot of details about how to use it and how to generate nice reports out of it. do we need an internal tool for c

[issue2403] Add figleaf coverage metrics

Éric Araujo added the comment: Adding people interested in code coverage to nosy. -- nosy: +giampaolo.rodola, ncoghlan versions: +Python 3.3 -Python 2.7, Python 3.1 ___ Python tracker __

[issue2403] Add figleaf coverage metrics

Éric Araujo added the comment: the Python API of figleaf* -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue2403] Add figleaf coverage metrics

Éric Araujo added the comment: IIUC, using runpy (either from Python or in a subprocess i.e. python -m test.regrtest) would allow running from build dir. Coverage reports are nice, but I personally dislike the idea of code downloading something via HTTP and running it. I’d prefer just having

[issue2403] Add figleaf coverage metrics

Changes by Skip Montanaro : -- nosy: -skip.montanaro ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue2403] Add figleaf coverage metrics

Daniel Diniz added the comment: Re-attaching the coverage bootstrapping file as plain/text. -- nosy: +ajaksu2 stage: -> test needed type: -> feature request versions: +Python 2.7, Python 3.1 -Python 2.6 Added file: http://bugs.python.org/file13788/coverage.py

[issue2403] Add figleaf coverage metrics

Skip Montanaro <[EMAIL PROTECTED]> added the comment: I gave this a try. It seems to not report on many files. For example, test_csv was run and passed, but there is no html file in the coverage directory with "csv" in its name after figleaf2html is run. Nor is there a key in the pickled dicti

[issue2403] Add figleaf coverage metrics

Skip Montanaro <[EMAIL PROTECTED]> added the comment: How will this work if I use a build directory? For example, my source is in ~/src/python/trunk. In there I create a build directory. When I run it I get % pwd /Users/skip/src/python/trunk/build % ./python.exe ../Tools/coverage/coverage.py

[issue2403] Add figleaf coverage metrics

Neal Norwitz <[EMAIL PROTECTED]> added the comment: > * ../../python.exe changed to sys.executable. > * Figleaf is 69kb. It seems to work fine doing it all in one read() > call. Should it be chunked? At 69kb, nah. It should be good enough for the first cut. > * Optparse isn't used, pa

[issue2403] Add figleaf coverage metrics

Jerry Seutter <[EMAIL PROTECTED]> added the comment: Thanks for the input. * ../../python.exe changed to sys.executable. * Figleaf is 69kb. It seems to work fine doing it all in one read() call. Should it be chunked? * Optparse isn't used, partially because I'm lazy and partly because I'm n

[issue2403] Add figleaf coverage metrics

Neal Norwitz <[EMAIL PROTECTED]> added the comment: Thanks for the patch. It would be nice to get more instrumentation like coverage, performance, etc. Here are some things I noticed while reviewing the patch: * This won't work on unix other than OSX. Can you change ../../python.exe to sys.e

[issue2403] Add figleaf coverage metrics

Jerry Seutter <[EMAIL PROTECTED]> added the comment: To test: 1. Unzip the zipfile in the base python directory. The zipfile will create Tools/coverage*. 2. cd Tools; patch -p0 README.patch 3. cd coverage 4. ../../python.exe coverage.py The script will download figleaf, then run regrtest.py.

[issue2403] Add figleaf coverage metrics

Changes by Jerry Seutter <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file9738/coverage.zip __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs

[issue2403] Add figleaf coverage metrics

New submission from Jerry Seutter <[EMAIL PROTECTED]>: This issue adds support for figleaf unit test coverage information. The diffs apply against trunk -- components: Tests files: README.patch keywords: patch, patch messages: 63975 nosy: jseutter priority: low severity: normal status: