Remove unused/misleading utcdelta#191
Merged
akrherz merged 4 commits intopython-metar:mainfrom Apr 15, 2025
Merged
Conversation
akrherz
reviewed
Apr 10, 2025
akrherz
approved these changes
Apr 10, 2025
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
3 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.
This PR removes the unused
utcdelta, which leads to confusion around whether timezones are handled naively or not.Even though code-wise this is a small change, I'd suggest a major semver bump to 2.0.0 as it's a breaking change to the Metar constructor.
This has some overlap with #186; however, that PR suggests broader changes to how timezones are handled, and the utcdelta arg is misleading enough that I believe it should be removed regardless of the decision on how to handle zulu time.