clarify async view incompatibility with gevent monkey patching #5885
+56
−0
Conversation
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
2 participants
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.
@davidism Please Check
Closes #5881
This PR adds documentation clarifying the limitations and unsupported nature of using Flask async views together with gevent monkey patching.
While simple async views may appear to work for individual requests, concurrent requests can fail due to conflicts between asyncio’s event loop assumptions and gevent’s greenlet-based threading model. The documentation explains why this behavior occurs, highlights failure modes that typically only appear under concurrency, and outlines recommended alternatives and advanced override considerations.
This change is documentation-only and is based on the investigation and conclusions discussed in the linked issue.