fix: initialize a_tex to prevent UnboundLocalError in PolarPlane #4557
+1
−0
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
chopan050
approved these changes
Feb 2, 2026
Contributor
chopan050
left a comment
chopan050
left a comment
There was a problem hiding this comment.
LGTM! Thanks for this change!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 noticed a potential 'UnboundLocalError' in 'PolarPlane.get_coordinate_labels'. The variable 'a_tex' is defined within multiple 'if/elif' blocks but lacks a default initialization or an 'else' catch-all. If 'self.azimuth_units' were to contain an unexpected value (e.g. through manual modification after initialization), the subsequent 'VGroup(*a_tex)' call would crash. This change ensures 'a_tex' is always defined.