Skip to content

BUG: explicit tz=None ignored in Timestamp constructor #48688

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.

Sign up for GitHub

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

Jump to bottom
Closed
jbrockmendel opened this issue Sep 21, 2022 · 1 comment · Fixed by #58226
Closed

BUG: explicit tz=None ignored in Timestamp constructor #48688

jbrockmendel opened this issue Sep 21, 2022 · 1 comment · Fixed by #58226
Assignees
@tqa236
Labels
Bug Datetime Datetime data dtype Timezones Timezone data dtype

Comments

@jbrockmendel
Copy link
Member

jbrockmendel commented Sep 21, 2022 •
edited
Loading 

In [14]: Timestamp(datetime(2022, 1, 1, tzinfo=timezone.utc), tz=None)
Out[14]: Timestamp('2022-01-01 00:00:00+0000', tz='UTC')

If a user explicitly passes tz=None and a tzaware string or datetime object, we should raise. This was fixed for DatetimeIndex in GH#48659
@jbrockmendel jbrockmendel added Bug Needs Triage Issue that has not been reviewed by a pandas team member labels Sep 21, 2022
@mroeschke mroeschke added Datetime Datetime data dtype Timezones Timezone data dtype and removed Needs Triage Issue that has not been reviewed by a pandas team member labels Sep 21, 2022
@tqa236
Copy link
Contributor

tqa236 commented Apr 11, 2024

take

@tqa236 tqa236 mentioned this issue Apr 11, 2024
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tqa236 tqa236

Labels
Bug Datetime Datetime data dtype Timezones Timezone data dtype
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

BUG: Timestamp ignoring explicit tz=None tqa236/pandas
3 participants
@jbrockmendel @mroeschke @tqa236