nidaqmx: Upgrade to Python 3.10 syntax #871
Merged
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
zhindes
approved these changes
Oct 24, 2025
bkeryan
force-pushed
the
users/bkeryan/remove-python-3.9
branch
from
d2396f6 to
0bf42c3
Compare
bkeryan
force-pushed
the
users/bkeryan/pyupgrade-3.10
branch
from
311f5bc to
7ea2b61
Compare
Contributor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've updated CHANGELOG.md if applicable.I've added tests applicable for this pull requestWhat does this Pull Request accomplish?
Use
Get-ChildItem -Recurse "*.py" | ForEach-Object { pyupgrade --py310-plus $_ }to upgrade to Python 3.10+ syntax.For codegen, I ran this on the generated files and manually copied the changes into the Mako templates and other codegen files.
Why should this Pull Request be merged?
Python 3.9 is EOL.
What testing has been done?
Ran nps, mypy, unit tests locally.
PR build