Skip to content

Improve typing with structured ASGI scopes and WSGI environment TypedDicts#2642

Open
MustafaNazir11 wants to merge 1 commit into
falconry:masterfrom
MustafaNazir11:master
Open

Improve typing with structured ASGI scopes and WSGI environment TypedDicts#2642
MustafaNazir11 wants to merge 1 commit into
falconry:masterfrom
MustafaNazir11:master

Conversation

@MustafaNazir11
Copy link
Copy Markdown

@MustafaNazir11 MustafaNazir11 commented May 4, 2026

Summary of Changes

This PR modernizes and significantly strengthens Falcon’s typing by replacing loosely typed dict[str, Any] usages with well-defined TypedDict structures for both ASGI scopes and WSGI environment objects.

It also updates legacy typing syntax (Union, Optional) to modern Python 3.10+ style and improves internal type safety across multiple modules.

Related Issues

Relates to #2628

Pull Request Checklist

This is just a reminder about the most common mistakes. Please make sure that you tick all appropriate boxes. Reading our contribution guide at least once will save you a few review cycles!

If an item doesn't apply to your pull request, check it anyway to make it apparent that there's nothing to do.

  • Applied changes to both WSGI and ASGI code paths and interfaces (where applicable).
  • Added tests for changed code.
  • Performed automated tests and code quality checks by running tox.
  • Prefixed code comments with GitHub nick and an appropriate prefix.
  • Coding style is consistent with the rest of the framework.
  • Updated documentation for changed code.
    • Added docstrings for any new classes, functions, or modules.
    • Updated docstrings for any modifications to existing code.
    • Updated both WSGI and ASGI docs (where applicable).
    • Added references to new classes, functions, or modules to the relevant RST file under docs/.
    • Updated all relevant supporting documentation files under docs/.
    • A copyright notice is included at the top of any new modules (using your own name or the name of your organization).
    • Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives.
  • Changes (and possible deprecations) have towncrier news fragments under docs/_newsfragments/, with the file name format {issue_number}.{fragment_type}.rst. (Run tox -e towncrier, and inspect docs/_build/html/changes/ in the browser to ensure it renders correctly.)
  • LLM output, if any, has been carefully reviewed and tested by a human developer. (See also: Use of LLMs ("AI").)

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!

PR template inspired by the attrs project.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 4, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (b1b683a) to head (4489964).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #2642   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           64        64           
  Lines         7976      7983    +7     
  Branches      1102      1103    +1     
=========================================
+ Hits          7976      7983    +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown
Member

@vytas7 vytas7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR, @MustafaNazir11!

Unfortunately, it requires a major overhaul before we could consider it.

If you are improving typing, please don't alter the code's behaviour itself, especially not in performance-critical code paths!

Also, the main goal of the TypedDicts was to get rid of type-ignores related to using too generic types. Unfortunately, it seems we got a slew of new ignores instead!

Comment thread falcon/asgi/app.py
asgi_info: dict[str, str] = scope['asgi']
raw = scope['asgi']
except KeyError:
# NOTE(kgriffs): According to the ASGI spec, "2.0" is
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't remove the notes or make unrelated changes to code.

Comment thread falcon/asgi/app.py
spec_version: str | None = asgi_info['spec_version']
except KeyError:
spec_version = None
# Normalize into proper _ASGIVersions shape
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't make changes that can affect performance in this performance-critical path.

Comment thread falcon/asgi/app.py
# first (in contrast to one-shot lifespan events).
if scope_type == 'websocket':
await self._handle_websocket(spec_version, scope, receive, send)
await self._handle_websocket(spec_version, scope, receive, send) # type: ignore[arg-type]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The whole point was to get rid of type-ignores, not to add new ones!

Comment thread falcon/asgi/app.py

req = self._request_type(
scope, receive, first_event=first_event, options=self.req_options
scope, # type: ignore[arg-type]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, no new ignores!

Comment thread falcon/_typing.py
if sys.version_info >= (3, 11):
from typing import NotRequired
from wsgiref.types import StartResponse as StartResponse
from wsgiref.types import WSGIEnvironment as WSGIEnvironment
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you remove WSGIEnvironment from here?

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

Successfully merging this pull request may close these issues.

2 participants