TypeError: dtype '<class 'datetime.datetime'>' not understood
See original GitHub issuedf
valuation_date
0 2018-06-08
1 2018-06-11
2 2018-06-12
3 2018-06-13
4 2018-06-14
5 2018-06-15
type(valuation_dates_df)
Out[16]: pandas.core.frame.DataFrame
type(valuation_dates_df['valuation_date'])
Out[15]: pandas.core.series.Series
To reproduce the error:
dict= {'valuation_date': {0: Timestamp('2018-06-08 00:00:00'),
1: Timestamp('2018-06-11 00:00:00'),
2: Timestamp('2018-06-12 00:00:00'),
3: Timestamp('2018-06-13 00:00:00'),
4: Timestamp('2018-06-14 00:00:00'),
5: Timestamp('2018-06-15 00:00:00')}}
pd.DataFrame.from_records(dict)['valuation_date'].astype(datetime.datetime)
valuation_dates_df['valuation_date'].astype(datetime.datetime)
File "C:\git\mre_x\_tcp\work\win-na-x64-release\py3\mre_venv3\lib\site-packages\pandas\core\dtypes\common.py", line 2029, in pandas_dtype
raise TypeError("dtype '{}' not understood".format(dtype))
TypeError: dtype '<class 'datetime.datetime'>' not understood
The issue occurs with pandas 0.24.1 and did not occur in 0.23.4.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (6 by maintainers)
Top Results From Across the Web
TypeError: dtype '<class 'datetime.timedelta'>' not understood
I have two dates where the difference of the dates determine how many days the user has been active. df['days_active'] = df['last_login'] - ......
Read more >Rossman_data_clean.ipynb got TypeError: dtype '<class ' ...
I was running rossman_data_clean.ipynb and got TypeError: dtype '<class 'datetime.datetime'>' not understood. I guess it's something with ...
Read more >[Code]-TypeError: dtype '<class 'datetime.date'>' not understood
I am working on below code, takes the data from yahoo finance and plotting the data for the technical analysis of the stock....
Read more >datetime dtypes in pandas read_csv - Intellipaat Community
The pandas.read_csv() function has a keyword parameter called parse_dates. Using this you can on the fly convert strings, floats or integers ...
Read more >pandas.to_datetime — pandas 0.21.1 documentation
list-like: DatetimeIndex; Series: Series of datetime64 dtype; scalar: Timestamp. In case when it is not possible to return designated types (e.g. when any ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jreback
By that logic neither should python
int
orfloat
be allowed, but they currently are (int
seems to default toint32
).So I don’t see why we can’t put practicality over purity here and let users have their shorthand conveniences.
I’d also like to point out that the alternative way to perform this operation:
df['some_col'] = pd.to_datetime(df['some_col'])
also doesn’t specify any units. So I’m not sure that’s a strong argument here.
EDIT:
On re-reading this comment I’m realizing it maybe comes off as a bit combative, particularly since text doesn’t convey tone. I’m sorry if so. I really appreciate what you and the rest of the pandas maintainer team do for so many people. I just figured I’d raise something that has been a repeated annoyance to me in the past, but I respect that not everyone may agree and perhaps with good reason. There might be implementation details I’m unaware of that could make a change like this messier than it at first appears. In terms of the actual reasoning for why I think
datetime.datetime
should be a legal argument forastype
, I hope I’ve made a decent case :pI changed from this:
to this:
where ‘date’ is a pandas series of dates in string type before the casting.