You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having trio support would be nice. I've been slowly moving towards this by first adopting anyio and now migrating to httpx.
What's missing is testing it. The current tests are already based on anyio, so it's just a matter of switching the backend during a test run.
By focusing on AnyIO we should get Trio support and any other backend that AnyIO supports.
Why is this important to you?
Python comes with the asyncio built-in package, but Trio has a friendlier API and we want to include its users. Otherwise people who use Trio can't use the Dagger Python SDK.
I suspect a problem with this since gql uses asyncio specifically. Need to investigate if we can work with that or convince the project to adopt AnyIO.
It's been more than a year since there's any activity to move the core GraphQL library to adopt AnyIO instead of asyncio. Let's revisit this at a later time.
What are you trying to do?
Having trio support would be nice. I've been slowly moving towards this by first adopting anyio and now migrating to httpx.
What's missing is testing it. The current tests are already based on anyio, so it's just a matter of switching the backend during a test run.
By focusing on AnyIO we should get Trio support and any other backend that AnyIO supports.
Why is this important to you?
Python comes with the
asyncio
built-in package, but Trio has a friendlier API and we want to include its users. Otherwise people who use Trio can't use the Dagger Python SDK.Dependencies
The text was updated successfully, but these errors were encountered: