forked from jcrobak/parquet-python
-
-
Notifications
You must be signed in to change notification settings - Fork 178
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
np.datetime64 vs pd.Timestamp #12
Comments
Can we make a test for this? |
martindurant
pushed a commit
to martindurant/fastparquet
that referenced
this issue
Nov 14, 2016
Merged
martindurant
added a commit
that referenced
this issue
Nov 14, 2016
martindurant
added a commit
that referenced
this issue
Nov 15, 2016
* Warn on timestamp coersion Fixes #12 * Flesh out details and a little dev doc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that we convert to datetime64s. Is this intentional? Do we roundtrip cleanly to pandas timestamps with timezones?
The text was updated successfully, but these errors were encountered: