Fix trio 0.15 warnings

[smurfix]

No description provided.

[njsmith]

Diff looks plausible to me. You have test failures though, and GitHub isn't letting me see the logs on my phone, so maybe everything is broken, I dunno :-)

I'm curious why anyio needs to subclass trio.Condition instead of just using it.

[agronholm]

I'm curious why anyio needs to subclass trio.Condition instead of just using it.

Because the notify and notify_all methods are coroutine methods in anyio and regular methods in trio.

[agronholm]

Diff looks plausible to me. You have test failures though, and GitHub isn't letting me see the logs on my phone, so maybe everything is broken, I dunno :-)

./anyio/_backends/_trio.py:250:1: W293 blank line contains whitespace

[agronholm]

This module does not exist in trio before v0.15. It would be better to use a conditional import for now.

[smurfix]

Done. (For some values of "done" …)

[smurfix]

OK, the Lock argument was missing. No longer testing against Py3.5 with Trio 0.15 should probably be fixed by somebody more familiar with the test setup.

[smurfix]

/opt/hostedtoolcache/Python/3.8.2/x64/lib/python3.8/site-packages/curio/pytest_plugin.py:60: PytestDeprecationWarning: direct construction of Function has been deprecated, please use Function.from_parent

Not my problem either, I'm afraid …

[agronholm]

Almost there!

[pquentin]

Trio 0.15.0 no longer supports Python 3.5, what is AnyIO's policy here?

[agronholm]

AnyIO 1.x still supports py3.5 but AnyIO 2.0 (in development) has dropped support. I will look at modifying the test suite to skip trio testing on py3.5.

[agronholm]

Thanks!