-
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trio
support broken: unexpected keyword argument 'auth_manager'
#138
Comments
Hi @burnpanck , It’s likely that support for Trio & Curio got broken. I’ve been only approving PRs and not actively maintaining the repo. Also, I didn’t feel like there’s much demand for loops outside asyncio. That’s why I wasn’t investing much in testing them. But I’d say the changes since I last personally tested these 2 loop providers were minimal. So should be easy to patch. It would be amazing if you can help me with that! And I’ll do my best to approve and deploy your changes. Thanks! |
People don't realise what they miss! With trio, I don't have a single exception that accidentally ends up on stderr. With asnycio, that happens all the time. Anyway, I'm happy to help in this regard. What exactly is that |
Yup, it’s not too complicated. But auth manager is important, it’s the object responsible for authenticating the requests being sent. @burnpanck |
It appears that
trio
support is currently broken. The following basic example fails:->
It looks like
auth_manager
is somethingrequests
-specific which potentially was just implemented recently?This was tested under python 3.12.2 with the following versions:
trio
: 0.24.0aiogoogle
: 5.7.0asks
: 3.0.0The text was updated successfully, but these errors were encountered: