Skip to content
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

BUG: Bug in DataFrame construction with recarray and non-ns datetime dtype (GH6140) #6142

Merged
merged 1 commit into from
Jan 28, 2014

Conversation

jreback
Copy link
Contributor

@jreback jreback commented Jan 28, 2014

closes #6140

jreback added a commit that referenced this pull request Jan 28, 2014
BUG: Bug in DataFrame construction with recarray and non-ns datetime dtype (GH6140)
@jreback jreback merged commit 1ed5c3e into pandas-dev:master Jan 28, 2014
@ghost
Copy link

ghost commented Jan 28, 2014

===============================================================================
ERROR: test_from_records_with_datetimes (pandas.tests.test_frame.TestDataFrame)
-------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/buildslave/nd-bb-slave-sparc-wheezy/pandas-py3_x-wheezy-sparc/build/venv/lib/python3.2/site-packages/pandas-0.13.0_420_ga67c3cd-py3.2-linux-sparc64.egg/pandas/tests/test_frame.py", line 3970, in test_from_records_with_datetimes
    recarray = np.core.records.fromarrays(arrdata, dtype=dtypes)
  File "/usr/lib/python3/dist-packages/numpy/core/records.py", line 566, in fromarrays
    _array[_names[i]] = arrayList[i]
ValueError: Must be a datetime.date or datetime.datetime object

@ghost
Copy link

ghost commented Jan 28, 2014

Best thing I ever did.

@jreback
Copy link
Contributor Author

jreback commented Jan 28, 2014

funny thing when I was doing this was thinking that their is a bug that caused all of the other sparc issues

namely that for some reason dtype comparisons don't work on date time types (but u can compare then as strings) - weird because it works on Linux in general

but getting off topic !

and I put in that exact comparison

ok 1.5 hrs to compile / test

@ghost
Copy link

ghost commented Jan 28, 2014

2.5h average delay +1.5 run actually. But at least you know there's a problem the same day
you commited, not 3 weeks after.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DataFrame.from_records doesn't handle missing dates (None)
1 participant