Migrate from Flask to Quart for ASGI async support #94
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.
Converts BlockPy server from Flask (WSGI) to Quart (ASGI) to enable async/await patterns and improved concurrency. Quart maintains Flask's API, requiring minimal code changes.
Core Changes
CustomFlask→CustomQuartasgi.pyfor ASGI deploymentImport Updates
Updated 30+ files from
from flask importtofrom quart import:Context Handling
Removed synchronous app context from setup in
main.py:Tasks System
Removed
@current_app.huey.task()decorators fromtasks/tasks.pyto avoid import-time app context access. Tasks remain as regular functions, can be decorated post-initialization if needed.Test Fixtures
Updated
tests/conftest.pyto handle Quart's async context using asyncio event loop for synchronous test compatibility.Compatibility
All Flask extensions work unchanged:
Routes and existing patterns remain identical. Optional async route handlers now supported:
Deployment
Deploy with Hypercorn instead of Gunicorn:
Procfile and Docker entrypoint updated accordingly.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.