{{ message }}
-
Notifications
You must be signed in to change notification settings - Fork 231
fix: make Signal.fire keyword-only to type the dispatch contract #1784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
bluetoothbot
wants to merge
9
commits into
python-zeroconf:master
Choose a base branch
from
bluetoothbot:koan/fix-issue-1779
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
769d9e5
fix: type Signal dispatch contract with Protocol
bluetoothbot 77c8c08
fix: make Signal.fire keyword-only to type the dispatch contract
bluetoothbot 6d21163
test: silence mypy arg-type on positional Signal.fire call
bluetoothbot 255510b
fix: resolve CI failures on #1784 (attempt 1)
bluetoothbot 7193b54
chore: drop out-of-scope cython version cap from build requires
bluetoothbot 4f16168
fix: resolve CI failures on #1784 (attempt 1)
bluetoothbot aed6b41
chore: drop out-of-scope cython cap and ci release-dry-run change
bluetoothbot b127121
test: pin unknown-kwarg rejection in Signal.fire test
bluetoothbot c789ca9
fix: accept and discard extra kwargs in Signal.fire for back compat
bluetoothbot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
You can’t perform that action at this time.

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need a **kwargs: Any throw away as well for back compat?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important
Depends on how much compat you want.
**kwargs: Anythrowaway costs little and keeps most of this PR's value: typo protection survives, becausenmae=gets absorbed by kwargs whilenamestays required, so mypy still flags a missing argument. Only loss: extra keys pass through to handlers again — same as pre-change behaviour.Full back-compat needs defaults too. A caller firing only its own keys still breaks on four required params, and defaults would kill the missing-argument check entirely.
Only in-tree caller:
browser.py:743. Adopting**kwargsmeans rewritingtest_signal_fire_rejects_unknown_kwarg(tests/test_services.py:306) to assert forwarding, not rejection.Which way do you want it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably just accept **kwargs and throw them away in case someone passes garbage it doesn't break