You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload
8000
a> to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
plotly/tests/test_optional/test_px/test_px_hover.py contains a test test_date_in_hover that currently marks the PyArrow case xfail because of problems with the constructor. We need to fix that test.
My understanding is that you would like to build the table directly with a "date" being datetime type.
Not sure which kind of conversions are possible in the initialization - especially, what we use from string to datetime (pyarrow.compute.strptime) requires an explicit format, so I would be surprised if only during initialization this is inferred.
Hey @gvwilson , thanks for the ping.
I might be missing something but the test is not marked to xfail for pyarrow at the moment and I don't see it failing either in your CI (at least for pyarrow).
Similarly, locally I don't get any issue.
plotly/tests/test_optional/test_px/test_px_hover.py
contains a testtest_date_in_hover
that currently marks the PyArrow casexfail
because of problems with the constructor. We need to fix that test.@FBruzzesi writes:
My understanding is that you would like to build the table directly with a "date" being datetime type.
Not sure which kind of conversions are possible in the initialization - especially, what we use from string to datetime (pyarrow.compute.strptime) requires an explicit format, so I would be surprised if only during initialization this is inferred.
What you can do is to pass a datetime object:
In narwhals you could do the same:
The text was updated successfully, but these errors were encountered: