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

Consider adding support for tracking subclass method invocations #142

Open
kgryte opened this issue Dec 7, 2020 · 0 comments
Open

Consider adding support for tracking subclass method invocations #142

kgryte opened this issue Dec 7, 2020 · 0 comments

Comments

@kgryte
Copy link
Contributor

kgryte commented Dec 7, 2020

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).

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

No branches or pull requests

1 participant