Skip to content

Conversation

@tconley1428
Copy link
Contributor

@tconley1428 tconley1428 commented Dec 3, 2025

What was changed

Used pyupgrade to update to >=3.10 conventions.

Why?

Checklist

  1. Closes

  2. How was this tested:

  1. Any docs updates needed?

@tconley1428 tconley1428 marked this pull request as ready for review December 3, 2025 23:08
@tconley1428 tconley1428 requested a review from a team as a code owner December 3, 2025 23:08
@tconley1428 tconley1428 changed the title WIP pyupgrade Update for 3.10 best practices Dec 3, 2025
Copy link
Contributor

@VegetarianOrc VegetarianOrc left a comment

Choose a reason for hiding this comment

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

I looks like we might have a bunch of the unused imports (like Optional) left throughout but that should probably get cleaned up separately.

@tconley1428 tconley1428 merged commit 4439675 into main Dec 8, 2025
15 checks passed
@tconley1428 tconley1428 deleted the pyupgrade branch December 8, 2025 22:33
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.

3 participants