Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs modern-python/modern-di#579.
Summary
modern-di>=3,<5. The lower bound stays, since the integration uses no 4.0-only API.modern-di3.x had a mandatory-open lifecycle. Only 3.0 raised on a resolve from a closed container; 3.1 to 3.6 warned and reopened it, and 4.0 raises again. The paragraph now says that.ContainerClosedWarning,use_lock, the registries,finalizer_errors, optional context, overrides cleared on close). Nothing else needed changing. TheContainerClosedErrorcomments inmain.pyandtests/test_lifespan.pyalready match 4.0.Verification
uv syncresolved modern-di 3.6.0. eof-fixer, ruff format/check and ty pass; pytest 17 passed, coverage 100%.This PR stays a draft until modern-di 4.0.0 is on PyPI.