aioauth VS Dependency Injector

aioauth is a library, the server in this context means that it implements the oauth2 protocol itself (rfc6749). there are few libraries for Python: authlib and oauthlib that also implement the oauth2 protocol, but unfortunately their implementation is not asynchronous, thus you cannot use these libraries in fastapi or aiohttp. aioauth solves this problem

Hello folks.

I'm happy to introduce aioauth - asynchronous oauth2 framework / server for Python 3.

For now it's implements 3 RFC's: rfc6749, rfc7662, rfc7636

It is easy to use and can be easily integrated into fastapi or aiohttp (FastAPI example was described in README).

Project homepage: https://github.com/aliev/aioauth

Nothing to do with the nature of the language, but with the nature of the program.

If you're writing a few line script, you don't need a DI container. Once your program gets large, it becomes extremely messy without one. It's no surprise projects like [1] exist.

[1] https://github.com/ets-labs/python-dependency-injector

Totally agree with this. And I’ve found this pattern pairs really well with https://python-dependency-injector.ets-labs.org/

dependency_injector: https://github.com/ets-labs/python-dependency-injector

As projects continue to grow, its recommended to utilise a dependency injection framework to “inject” these dependencies, such as Dependency Injector, to inject dependency arguments automatically ✨.

One approach is to pass this config as a variable to every class it is required, which I dont prefer. Another option is to annotate the config class as singleton and create the config object at every place where I need them. I also came across this library called Dependency_Injector. https://python-dependency-injector.ets-labs.org/ This seems a bit heavy weight for my use case though. I am looking forward to know how other solve this problem

Dependency Injector

dependency-injector (docs) is python library that provides a framework which enables you to implement DI and IoC in Python.