Jason R. Coombs

> it's only possible for them to pay out to a single individual It is possible (though maybe not widely publicized) to set up multiple recipients for a project (I...

I believe it is not. The procedures herein rely on virtualbox, which doesn't support Apple Silicon. It's possible it could be made to work with VMWare or Parallels or UTM,...

Today I learned that UTM is backed by qemu, which has a [vagrant provider](https://github.com/ppggff/vagrant-qemu). I tried spinning up the box using qemu, but without success (reasonably, because the images haven't...

I suspect that DLL has some dependency on a service running and that if the miner is started before that dependency is ready, the error will occur.

That technique does not seem to be having the desired effect. See the referenced PR on Setuptools, where the PyPy tests take ~17 minutes to run, whereas with coverage disabled,...

In pypa/setuptools#2254, I learned that `cov.cov_controller.pause()` was necessary, but it's working now! Thank you so much.

Just to confirm - I run with `--doctest-modules` as a matter of course to _get_ this coverage. That is, even if no doctests are run, if the module is executed,...

I notice this issue when I'm testing a project that's used by pytest (or a plugin). For example, the [zipp project](/jaraco/zipp) was reporting no coverage on the lines the execute...

I notice that the warnings go away if I run with `-p no:checkdocs`. It seems the [act of loading the project metadata](https://github.com/jaraco/pytest-checkdocs/blob/0548d2615e5d5a6e3663f649943f84df4187ebca/pytest_checkdocs/__init__.py#L72) in a pytest plugin is tripping up file...

By design, a distribution package and its metadata are loosely-coupled from the Python package(s), for better or for worse. That is, when you `import numpy`, that's a different numpy than...