Repository navigation
gh-161194: fix timezone constants when timezone rules change mid-year - #161230
NotorandXor256 wants to merge 4 commits into
Conversation
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
|
during regeneration the configuration |
|
Please revert all unrelated changes. |
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
|
@StanFromIreland I have removed unrelated changes. |
|
Please fix the CI, many jobs are failing. |
Detect the declaration of tzname during configuration so that CPython uses libc's timezone globals instead of relying on January and July samples.
This avoids reporting stale timezone constants when a timezone's rules change during the year.