Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
AmbiguousTimeError: Cannot infer dst time from Timestamp('2015-11-01 01:00:03'), try using the 'ambiguous' argument #14402
Comments
|
can you show a copy-pastable example. e.g. construct a frame exactly like what you need. Then apply operations to show an error. |
jorisvandenbossche
added the
Timezones
label
Oct 12, 2016
|
|
adamschultz
commented
Oct 12, 2016
|
Thanks for the quick reply. Here's the traceback from a minimal, reproducible example with a one-row data frame.
|
jreback
added the
Bug
label
Oct 12, 2016
jreback
added this to the
0.19.1
milestone
Oct 12, 2016
jreback
added a commit
to jreback/pandas
that referenced
this issue
Oct 12, 2016
|
|
jreback |
eeb3478
|
jreback
referenced
this issue
Oct 12, 2016
Closed
BUG: Bug in localizing an ambiguous timezone when a boolean is passed #14405
|
@adamschultz ok fixed in #14405 ; this was a bug in interpreting a passed boolean. Note that you still MUST pass the ambiguous argument, as this fundamentally IS an ambiguous time. |
jreback
added a commit
to jreback/pandas
that referenced
this issue
Oct 13, 2016
|
|
jreback |
d47ed55
|
jreback
closed this
in a40e185
Oct 13, 2016
tworec
added a commit
to RTBHOUSE/pandas
that referenced
this issue
Oct 21, 2016
|
|
jreback + tworec |
839fd99
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
adamschultz commentedOct 12, 2016
In Pandas 0.19.0, there seems to be an error when setting the timezone for times close to the dst cutoff.
This issue appears very similar to #11619 and #11626, both of which have been closed. The traceback is below.
Here is some relevant information on the data frame.
I also had this same issue in Pandas 0.18.0 before upgrading to 0.19.0.