[Python-Dev] We now have C code coverage!
Oh whoops, sorry about that. I haven't really used mailing lists
before and so I assumed hitting reply in gmail would send it to
python-dev, not just your personal email. Just so the config file
locations are publicly documented, here's what I responded with:
> For IDLE's test suite, I use a customized .coveragerc. I strongly prefer to not abandon that and litter the code with # pragmas.
Yup, I agree completely. Having pragmas everywhere is really annoying,
its really only useful for small one-off stuff.
> In order to make sense of the coverage report and have it be truthful, one needs to know what options are being used.
> Is the --branch flag set?
> Is .coveragerc or some other configuration file in use?
> If so, what is the content?
> Do we have any control over the use and content of exclusion settings?
To answer all these questions at once, yeah, we have complete control
over all the coverage parameters. Currently we aren't building with
`--branch` and don't have a coveragrc file. We could put one in the
root of CPython (which would get picked up automatically) but
personally I think CI related crud should go into its own folder.
Luckily we do have a ".github" folder, so I'd suggest putting the
coveragerc file in there and then adding the parameter
All the parameters to coverage.py can be configured here
If you wanna send over your IDLE coveragerc file, I can experiment and
try to get it working for Travis, or you can explore it yourself if
On Fri, Jun 29, 2018 at 9:14 AM, Terry Reedy <tjreedy at udel.edu> wrote:
> On 6/29/2018 9:25 AM, Brett Cannon wrote:
>> On Thu, Jun 28, 2018, 21:28 Terry Reedy, <tjreedy at udel.edu
>> <mailto:tjreedy at udel.edu>> wrote:
> [question about our coverage bot]
>> Everything is either covered by the Travis or codecov configuration files
>> which are both checked into the cpython repo. (I'm on vacation or else I
>> would provide links to the files themselves.)
> Ammar Askar privately asked for my coveragerc file so he could experiment
> with the configuration.
> Terry Jan Reedy
> Python-Dev mailing list
> Python-Dev at python.org