Repository navigation
test: use canonical IANA timezone names (fix CI on runners without legacy tz aliases) - #177
Merged
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
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.
Since 2026-10-26 the
test (3.12)andtest (3.13)jobs fail on main and on every PR (including #176) with one failure:test_get_bars_since_with_pytz_timezone_objectraisesZoneInfoNotFoundError: 'No time zone found with key US/Eastern'. The runner's tz database no longer resolves the legacyUS/*aliases through zoneinfo. A rerun of the last green main CI (8dfb561) now fails the same way, so it's environmental, not a dependency change.This swaps the legacy names in tests (and one docstring example) for canonical IANA names:
US/EasterntoAmerica/New_York,US/CentraltoAmerica/Chicago,US/PacifictoAmerica/Los_Angeles. No runtime behavior change, no new dependency, no release needed.