py-call-osafterfork isn't needed in python 3.13+ #2736
Draft
+12
−7
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.
fixes #2710
in 3.13, there's a new mutex type that now cares if the mutex is unlocked while not currently locked
A warning should be emitted to advise to use
py-call-uwsgi-fork-hooksif running against 3.13 (+ a doc update that suggests to usepy-call-uwsgi-fork-hooksoverpy-call-osafterforksince maintainers want to support py-call-osafterfork for LTS reasons, my suggestion would be to just remove
py-call-osafterforkentirely otherwise