Oleg Höfling

Here's my humble suggestion: a Travis job configuration that builds fat Linux/MacOS wheels with `libev` included, installs them and runs unit tests, with additional releasing on tag push. Examples: *...

As noted in #121, I have started porting scripts under `tests/` to automated unit tests, but am not quite happy with the result yet. Right now I am unsure about...

I'm not sure if I can use threads - I can only send signals to the main thread, not to spawned ones. As for the suggestion with piping data between...

> One thing we have to think about is that some of the tests are useful only when called 1000s of times, for example the exception tests, which are used...

This PR (and the other one I have started working at for #121) were parts of making `bjoern` pass the requirements of our internal QA & security team. Since then,...

@bluetech > Hmm just noticed a regression of sorts - now sphinx shows a bunch of private constructors (e.g. [here](https://pytest--9248.org.readthedocs.build/en/9248/reference/reference.html#pytest.Cache) - search for `_ispytest` in the API Reference) where previously...

Same is with fixtures, e.g. if I create an incomplete info field list for `capsys` via ```diff --- a/src/_pytest/capture.py +++ b/src/_pytest/capture.py @@ -906,6 +906,9 @@ def capsys(request: SubRequest) -> Generator[CaptureFixture[str],...

> Seems like we're going to have to do this. It would take some work -- often we omit `:param:` for "obvious" parameters/short functions. This is something I could tackle,...

At least when it comes to the CI, the failures are not related to Django bump and should be amended with the next release of `sphinx-celery` that includes https://github.com/celery/sphinx_celery/pull/40.

@diegocastrum are you still on it or is the task up for grabs?