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
An issue arose when analyzing GeoPandas and its consumption of Pandas APIs.
GeoPandas subclasses Pandas (see here), so, in principle, a subclassed method should correspond to an equivalent Pandas DataFrame method. However, this is not the case.
Based on analysis, GeoPandas appears to only consume 3 Pandas APIs, but this is, presumably, not a fair representation, given that many a GeoPandas DataFrame method is a Pandas DataFrame method.
Accordingly, may be worth investigating whether we can track subclass method invocations.
In conversation with @saulshanabrook, he suggested updating the Tracer to look at method resolution order (MRO).
The text was updated successfully, but these errors were encountered:
An issue arose when analyzing GeoPandas and its consumption of Pandas APIs.
GeoPandas subclasses Pandas (see here), so, in principle, a subclassed method should correspond to an equivalent Pandas DataFrame method. However, this is not the case.
Based on analysis, GeoPandas appears to only consume 3 Pandas APIs, but this is, presumably, not a fair representation, given that many a GeoPandas DataFrame method is a Pandas DataFrame method.
Accordingly, may be worth investigating whether we can track subclass method invocations.
In conversation with @saulshanabrook, he suggested updating the
Tracer
to look at method resolution order (MRO).The text was updated successfully, but these errors were encountered: