connexion VS Dependency Injector

I do like to use their SQLAlchemy ModelView for CRUD operations and expose a OpenAPI to it using flask based connexion project for front-end or other integration points.

but maybe because i decided to use connexion(api) or flask-admin(mvc) i had a better user experience while still feeling i have control over my requirements.txt.

Connexion is a framework on top of Flask that automagically handles HTTP requests defined using OpenAPI

https://github.com/zalando/connexion (spec-first framework on top of Flask)

I'm using the Connexion framework for Flask to build a microservice. I would like to write tests for my application using py.test.

I'm a bit late to this thread, but I'd also recommend Zalando's connexion library for OpenAPI declarative API specs (built on top of Flask).

Connexion for OpenAPI spec first REST APIs: https://github.com/zalando/connexion

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.