Fix compatibility with Trio 0.15.0

pquentin · pquentin · commit 9572aaff6010 · 2020-05-19T21:06:34.000+04:00
diff --git a/pytest_trio/_tests/test_fixture_names.py b/pytest_trio/_tests/test_fixture_names.py
@@ -12,7 +12,7 @@ def fixture_with_unique_name(nursery):
 async def test_fixture_names(fixture_with_unique_name):
     # This might be a bit fragile ... if we rearrange the nursery hierarchy
     # somehow so it breaks, then we can make it more robust.
-    task = trio.hazmat.current_task()
+    task = trio.lowlevel.current_task()
     assert task.name == "<test 'test_fixture_names'>"
     sibling_names = {task.name for task in task.parent_nursery.child_tasks}
     assert "<fixture 'fixture_with_unique_name'>" in sibling_names
diff --git a/pytest_trio/plugin.py b/pytest_trio/plugin.py
@@ -208,7 +208,7 @@ async def run(self, test_ctx, contextvars_ctx):
 
         # This is a gross hack. I guess Trio should provide a context=
         # argument to start_soon/start?
-        task = trio.hazmat.current_task()
+        task = trio.lowlevel.current_task()
         assert canary not in task.context
         task.context = contextvars_ctx
         # Force a yield so we pick up the new context
diff --git a/setup.py b/setup.py
@@ -16,7 +16,7 @@
     packages=find_packages(),
     entry_points={'pytest11': ['trio = pytest_trio.plugin']},
     install_requires=[
-        "trio >= 0.11",
+        "trio >= 0.15.0",
         "async_generator >= 1.9",
         "outcome",
         # For node.get_closest_marker
