bpo-34482: Add tests for proper handling of non-UTF-8-encodable strin…#8878
bpo-34482: Add tests for proper handling of non-UTF-8-encodable strin…#8878taleinat merged 7 commits into
Conversation
…gs in datetime classes A follow-up of bpo-34454.
|
II think rather than doing Alternatively, maybe use |
Sorry, something went wrong.
|
I think this also needs tests for |
Sorry, something went wrong.
|
I made a PR against @izbyshev's branch that fixes this bug as part of adding the test suite. I can move that to a separate PR against master if preferred. |
Sorry, something went wrong.
|
IMO a NEWS entry isn't needed here, since this only affects tests. |
Sorry, something went wrong.
|
By the way, in light of the fact that I have a PR to fix this, I withdraw my comments about expectedFailure and such. The whole point of expectedFailure is to make it clear that you are testing known-pathological behavior so it's not misinterpreted (and so that you can check in an automated way whether your expectations are false). Since it will be fixed almost immediately it's a pointless bit of formalism to explicitly mark them as failing just to have them switched over to succeeding immediately. |
Sorry, something went wrong.
My tests are in |
Sorry, something went wrong.
|
@taleinat Per discussion on izbyshev#1, I think it might be good to just do these as two separate PRs, if this one is ready to merge. It would be inconvenient for me to update my PR in response to review comments if it has to go through PRs to Alexey's fork first, and it's probably better to centralize the review comments on the main fork. |
Sorry, something went wrong.
|
@pganssle And I've eventually decided to add a separate test for |
Sorry, something went wrong.
Its behavior across platforms is inconsistent and hard to test.
|
I've removed |
Sorry, something went wrong.
|
I just merged the PR #8959: you may have to update/rebase this PR (that I didn't review it). |
Sorry, something went wrong.
|
Thanks, @vstinner, but this PR doesn't need rebasing right now. BTW, I don't know why Travis is unhappy. Could anybody tell it to try again? |
Sorry, something went wrong.
Restarted. Two runs, one of the a "docs" run, ran out of memory. I hope it's just transient. |
Sorry, something went wrong.
The test run succeeded. The "docs" run fails due to recent changes having left it a broken state in master for a short while; this just needs a merge/rebase. I'm on it. |
Sorry, something went wrong.
taleinat
left a comment
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
vstinner
left a comment
There was a problem hiding this comment.
LGTM. I love to see more tests on edge cases!
Sorry, something went wrong.
Sorry, something went wrong.
…ings (pythonGH-8878) (cherry picked from commit 3b0047d) Co-authored-by: Alexey Izbyshev <izbyshev@ispras.ru>
…gs in datetime classes
A follow-up of [bpo-34454](https://www.bugs.python.org/issue34454).
https://bugs.python.org/issue34482