EST invalid IANA timezone #1554
Conversation
With 'EST' `discover` consistently failed with ```Raised error: 'No time zone found with key EST'```
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1554 +/- ##
=======================================
Coverage 92.66% 92.66%
=======================================
Files 150 150
Lines 9538 9538
Branches 974 974
=======================================
Hits 8838 8838
Misses 499 499
Partials 201 201 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
To be honest, it sounds like your installation is broken. tzdata should have it and I just tested that I can initialize it on python3.13 just fine: You could try if installing tzdata using pip helps. If so, python cannot find the OS-wide installation for some reason. |
|
@BrianRossmajer Can you try checking out my PR [#1583] and see if that resolved the time module issue? I have implemented a more aggressive failover and deterministic time zone capture for older IOT devices. If that resolves your issues, we can close this out and implement the more robust failover. |
3 participants
With 'EST'
kasa discoveron Debian consistently failed withRaised error: 'No time zone found with key EST'I couldn't confirm "EST" was a valid IANA timezone, where America/Toronto definitely is... but it's "Eastern Time" not "Eastern Standard Time" which I think is what folks would expect in any case.