Repository navigation
[tooling] Fix tool invocations with older system Python versions - #1856
Merged
Merged
Conversation
BenjaminPelletier
marked this pull request as ready for review
October 28, 2026 07:17
the-glu
approved these changes
Oct 28, 2026
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
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.
#1852 upgraded to Python 3.14 and changed many particular syntax instances to ones that work exclusively with 3.14 and not certain earlier versions of Python. This is fine for all code that will be executed from a controlled environment like a docker image or via uv, but a few Python scripts in the repo are intended to be run directly from a user's system. To maximize compatibility, these scripts should keep the older syntax so every user isn't forced to update their system Python installation before starting to use InterUSS tools (like many of the
maketargets). This PR attempts to ensure that compatibility.We may consider switching all scripts from using Python to using uv and require uv as a single additional tool other than docker for a user to install before interacting with our products, but that is a much larger PR than this one.