bpo-37552 strptime/strftime return invalid results with UCRT version 17763.615#14460
bpo-37552 strptime/strftime return invalid results with UCRT version 17763.615#14460pganssle merged 8 commits into
Conversation
|
These issues ought to be fixed in the next Windows update (end of year, about the time that 3.8 releases), though we may get a redistributable ucrtbase.dll sooner. |
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
|
I have made the requested changes; please review again. |
Sorry, something went wrong.
|
Thanks for making the requested changes! @pganssle: please review the changes made to this pull request. |
Sorry, something went wrong.
|
I believe this has been sufficiently handled, but I'll let @pganssle retract his review when he's ready. (And I'll poke him in person today to make sure he's ready ;) ) |
Sorry, something went wrong.
|
If the Azure Pipelines PR check passes, I think this is ready for additional feedback and/or merging. |
Sorry, something went wrong.
zware
left a comment
There was a problem hiding this comment.
LGTM.
Sorry, something went wrong.
|
@pganssle: Please replace |
Sorry, something went wrong.
…17763.615 (pythonGH-14460) A bug in MSVC UCRT version 17763.615 (which has been fixed in newer versions) is causing test failures in some strptime/strftime tests when the default code page is c65001. This change selectively skips the tests affected by this. (cherry picked from commit 9cd39b1) Co-authored-by: Paul Monson <paulmon@users.noreply.github.com>
Noooo, I forgot I left that in the PR title. Serves me right for not using automerge. |
Sorry, something went wrong.
|
Thanks for the PR and for promptly addressing comments, @paulmon! |
Sorry, something went wrong.
…17763.615 (GH-14460) A bug in MSVC UCRT version 17763.615 (which has been fixed in newer versions) is causing test failures in some strptime/strftime tests when the default code page is c65001. This change selectively skips the tests affected by this. (cherry picked from commit 9cd39b1) Co-authored-by: Paul Monson <paulmon@users.noreply.github.com>
|
Thanks! all of the buildbot tests for Windows ARM32 have passed passed with only warnings since this was merged. |
Sorry, something went wrong.
…17763.615 (python#14460) A bug in MSVC UCRT version 17763.615 (which has been fixed in newer versions) is causing test failures in some strptime/strftime tests when the default code page is c65001. This change selectively skips the tests affected by this.
…17763.615 (python#14460) A bug in MSVC UCRT version 17763.615 (which has been fixed in newer versions) is causing test failures in some strptime/strftime tests when the default code page is c65001. This change selectively skips the tests affected by this.
…17763.615 (python#14460) A bug in MSVC UCRT version 17763.615 (which has been fixed in newer versions) is causing test failures in some strptime/strftime tests when the default code page is c65001. This change selectively skips the tests affected by this.
Skip tests that fail because of bug in MSVC UCRT failure when the default code page is cp65001.
@zooba
https://bugs.python.org/issue36511