You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current system for naming types is overly complex: each type has an internal name (e.g. "integer") and an associated PFSM. We then separately have a map (twice – see #68) between internal names and Pandas names. This is confusing and leads to weirdness like show_schema showing the inferred type as “integer” but df.types showing Int64.
Schema.transform suggests that date-iso-8601, date-eu and date-non-std can all be converted automatically to datatime64 by Series.astype – is this correct?
ptype_pandas_mapping is defined more than once
The text was updated successfully, but these errors were encountered:
The current system for naming types is overly complex: each type has an internal name (e.g.
"integer"
) and an associated PFSM. We then separately have a map (twice – see #68) between internal names and Pandas names. This is confusing and leads to weirdness likeshow_schema
showing the inferred type as “integer” butdf.types
showingInt64
.Schema.transform
suggests thatdate-iso-8601
,date-eu
anddate-non-std
can all be converted automatically todatatime64
bySeries.astype
– is this correct?ptype_pandas_mapping
is defined more than onceThe text was updated successfully, but these errors were encountered: