-
Notifications
You must be signed in to change notification settings - Fork 17
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
an asynchronous version of the v2 API wrapper #44
Comments
yep, this has been on my mind for a while now. I'll write an async version at some point (or someone is free to beat me to it, as always) |
possibly separate them into folders so imports become like |
I'd prefer if the async version was called I did start working on this, and you can see my (extremely rough and currently erroring) progress on the async branch, namely commit b420040. It turned out to be a pain to extract out the async portions of the code cleanly. The async version of the requests oauthlib is also broken (weibeu/Async-OAuthlib#3) so I would need to either fix that or roll my own implementation. In short, don't expect this anytime soon. |
I've implemented this in v3.1.0. You can import it as |
it would be quite useful for website backends, with logins and discord bots, that also want to authenticate users in a way
https://async-oauthlib.readthedocs.io/en/latest/ there's an async oauth module, that seems to fit the features needed for it
and for requests themself,
aiohttp
would be niceit could be named something like
AsyncOssapiV2
which would be used the same as the synchronous one, except that all endpoints would need to beawait
edThe text was updated successfully, but these errors were encountered: