Skip to content
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

Find alternative to dependency-injector framework #71

Open
febus982 opened this issue Nov 22, 2023 · 2 comments
Open

Find alternative to dependency-injector framework #71

febus982 opened this issue Nov 22, 2023 · 2 comments

Comments

@febus982
Copy link
Owner

febus982 commented Nov 22, 2023

The project is not actively maintained except for urgent requirements: ets-labs/python-dependency-injector#742

Once python 3.12 is released it will pin pydantic to v1, making the package incompatible (ets-labs/python-dependency-injector#765 ets-labs/python-dependency-injector#752)

Potential candidates (https://github.com/sfermigier/awesome-dependency-injection-in-python)?

@macieyng
Copy link

ets-labs/python-dependency-injector#752 (comment)
Pydantic v1 will be pinned only for tests. It's not a dependency od dependency-injector. It doesn't mean you can't use it with Python 3.12.

@febus982
Copy link
Owner Author

febus982 commented Nov 24, 2023

Thanks for specifying this @macieyng I updated the issue description in case anyone stumbles on this. (This makes this issue a little less urgent to fix at least)

Unfortunately despite this, it looks like there is not much time to maintain bugs, apart from urgent requirements (from ets-labs/python-dependency-injector#742 (comment)). Before python 3.12 support the last commit was almost a year ago.

A shame, because I truly love the framework (I'm not a C developer or I'd contribute to some of them).

I use only a minimal subset of the functionalities the framework provides, it might be easier to simply rewrite them in python.

febus982 added a commit that referenced this issue Jan 10, 2024
…on-3.11

Run github pages flow using python 3.11 because of issue #71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants