Skip to content

bpo-10381: Test that new_timezone can return the UTC singleton #5318

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 22, 2018

Conversation

pganssle
Copy link
Member

@pganssle pganssle commented Jan 25, 2018

While I was fixing #5317, I realized that we are currently not testing the behavior that new_timezone will return the UTC singleton if provided a zero offset and no name.

I'm referring this to the original issue, since this is really more of an oversight in the original test suite than a new issue. Since it has no behavior change and only affects an unreleased feature, I have not added news.

CC: @abalkin

https://bugs.python.org/issue10381

@abalkin
Copy link
Member

abalkin commented Feb 22, 2018

@ned-deily - as a tests-only change, I think this can go in 3.7.

@ned-deily
Copy link
Member

@abalkin Sure, as a feature fix, go ahead and merge to master and allow backport to 3.7.

@abalkin abalkin merged commit a049f57 into python:master Feb 22, 2018
@miss-islington
Copy link
Contributor

Thanks @pganssle for the PR, and @abalkin for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Feb 22, 2018
@bedevere-bot
Copy link

GH-5819 is a backport of this pull request to the 3.7 branch.

abalkin pushed a commit that referenced this pull request Feb 22, 2018
@pganssle pganssle deleted the utc_singleton_api_test branch October 25, 2018 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants