Nathaniel J. Smith

@lordi No, `trio_asyncio.run` is just a confusing shorthand for doing `trio.run` and then `trio_asyncio.open_loop`. So you don't need it; you can just do `open_loop` yourself. I'm not sure why we...

Looks like there's some socket that's not getting closed properly, and it's causing spurious failures in the test suite. Not really anything to worry about, but we should still fix...

I guess this has the same cause as #123 -- we're not properly querying pytest to figure out the list of fixtures. I would guess fixing one would also fix...

I think the way forward here is probably to: - add some kind of "helper task" support to trio: https://github.com/python-trio/trio/issues/1521 - deprecate the `nursery` fixture, since it's not needed if...

If you put the nursery into a fixture, then you're scoping the entire test to run inside that nursery. So your test isn't just cancelling your `Foo`'s background worker; you're...

You could certainly make a fixture that implemented that nested nursery logic I mentioned. I'm not sure how if it would be very popular in general, though? I've never found...

Huh, that's weird. I get the same thing. I've definitely been able to run the tests locally in the past. It might have been something like `PYTHONPATH=. pytest pytest_trio`, but...

Hmm, it looks like a workaround is to do: ``` virtualenv -ppython3 venv . venv/bin/activate git clone git://github.com/python-trio/pytest-trio cd pytest-trio pip install -r test-requirements.txt pip install -e . pytest --pyargs...

@Alessandro-Barbieri What trouble is it causing for you? Are you trying to make changes to pytest-trio?

@Alessandro-Barbieri If you know how to fix it then we would love to merge a patch, but I don't know how to fix it. Can you somehow install the package...