Ned Batchelder

In https://github.com/python/cpython/pull/117005#discussion_r1532502844, @AlexWaygood suggests using ``` :meth:`!__init__` ``` instead of ``` :meth:`~!object.__init__` ``` because it renders the same, but is less clutter in the .rst file. Semantically, it's a link-suppressed...

> Thoughts? Never mind: I am now seeing that this has been discussed above, and CI fails with `~!`, so I will switch to the shorter form.

And then I read more about conflicts of interest later on.... So perhaps all is fine?

An idea for the emoji: a gratitude gesture like this: https://www.google.com/search?q=gratitude+gesture,+hand+on+chest&tbm=isch Eyes closed, smiling, hand on chest.

After typing this up, I tried creating a hashtag column with `generativeart typography -aiart -stablediffusion` as the hashtags, but that didn't work either.

Thanks for doing this. I would like to include the "coverage combine" message only if there are combinable data files. I've included other comments in the diff.

> Coverage report shows a lot of files with 0 lines which give 100% of coverage, or no lines covered (0%) You can exclude empty files ([skip_empty](https://coverage.readthedocs.io/en/7.4.4/config.html#html-skip-empty)), and 100% files...

There are a few things I still don't understand: - Why do you want to measure the coverage of numpy? Are you testing numpy? - How should coverage know which...

Huh, this is a great idea :) I wonder if we'd need to give the user some control over how many cores to use? The HTML report is many files...

Some exploration reveals there is a bunch of refactoring that would need to be done. During reporting, we have a graph of objects that is not picklable: HtmlReport -> HtmlDataGeneration...