Brandon Craig Rhodes bran...@rhodesmill.org added the comment:
Brett, yes, you are welcome to close this issue — Ned quite handily convinced
me that coverage code belongs in the coverage distribution, not languishing
about in the CPython source tree. That solution also quite beautifully solves
Thomas Wouters tho...@python.org added the comment:
For what it's worth, the need for a bootstrap-module has also come up within
Google, where we have... somewhat different requirements than most. In order
to fix import paths in a way that works even when using python -S, I had a
need to
Brett Cannon br...@python.org added the comment:
Brandon, can I go ahead and close this and consider the script you and Ned have
in the coverage.py repo to be the canonical script to use?
--
status: open - pending
___
Python tracker
Nick Coghlan ncogh...@gmail.com added the comment:
Do we really want to enshrine shadowing the encodings module as the one true
way to do this kind of thing?
Although I guess defining a way to do it properly would be a fairly major
undertaking, so perhaps blessing the encodings hack is the
Nick Coghlan ncogh...@gmail.com added the comment:
Added Ned to the nosy list.
For Python core, we should also keep in mind that we do have the option of
adding a -X coverage option to avoid the need for the encodings module hack.
--
nosy: +nedbat
Ned Batchelder n...@nedbatchelder.com added the comment:
The tip of the coverage.py repo (https://bitbucket.org/ned/coveragepy) has a
new implementation of the encodings hack which seems to work well.
Of course, an option to run a module before anything else in the interpreter
would make the
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11561
___
___
Changes by Éric Araujo mer...@netwok.org:
Removed file: http://bugs.python.org/file22622/unnamed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11561
___
Éric Araujo mer...@netwok.org added the comment:
I think your suggestions are all good ones, and I have incorporated
them into the file.
Great :) You left some commented-out debugging prints.
(But do note that the departures we are now making from Ned's own
copy of the tracer code —
Brandon Craig Rhodes bran...@rhodesmill.org added the comment:
Éric, I think your suggestions are all good ones, and I have incorporated them
into the file. (But do note that the departures we are now making from Ned's
own copy of the tracer code — removing the commented-out debugging
Éric Araujo mer...@netwok.org added the comment:
Thanks for your work on this. I made some minor comments on Rietveld (you
should get an email), waiting for the real import experts to comment on the
meat of the patch.
--
nosy: +eric.araujo
___
Changes by Eric Snow ericsnowcurren...@gmail.com:
--
nosy: +ericsnow
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11561
___
___
Python-bugs-list
Brett Cannon br...@python.org added the comment:
Which I have not forgotten about. Just waiting until I have the time to get
to this.
On Mon, Jul 11, 2011 at 08:50, Ãric Araujo rep...@bugs.python.org wrote:
Ãric Araujo mer...@netwok.org added the comment:
Thanks for your work on this. I
Changes by Sandro Tosi sandro.t...@gmail.com:
--
nosy: +sandro.tosi
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11561
___
___
Python-bugs-list
Changes by Brett Cannon br...@python.org:
--
assignee: - brett.cannon
components: +Demos and Tools
stage: - patch review
versions: +Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11561
New submission from Brandon Craig Rhodes bran...@rhodesmill.org:
When running the Python regression tests in coverage, the initial outer level
of interpreted code in several standard library modules shows as not having
been covered by the tests, because they were imported during the Python
Brandon Craig Rhodes bran...@rhodesmill.org added the comment:
Here is a module that solves this problem if the tests are run with the
fullcoverage directory at the front of the PYTHONPATH, like this:
PYTHONPATH=Tools/fullcoverage ./python -m coverage run --pylib
Lib/test/regrtest.py
Changes by Nick Coghlan ncogh...@gmail.com:
--
nosy: +brett.cannon, ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11561
___
___
18 matches
Mail list logo
