Skip to content

Develop better tooling for static and dynamic analysis #44

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

Closed
gvanrossum opened this issue Apr 12, 2021 · 2 comments
Closed

Develop better tooling for static and dynamic analysis #44

gvanrossum opened this issue Apr 12, 2021 · 2 comments

Comments

@gvanrossum
Copy link
Collaborator

When we have an idea for rewriting some byte code (e.g. ADD_INT) we should be able to assess the relevance to a large body of code quickly. For example, static analysis could pull down the 1000 most popular Python packages from PyPI or GitHub and count opcodes for all .py files found there.

Dynamic analysis requires running code, which makes things more complicated, and moreover running it with a modified CPython interpreter. But we should at least have some standard way to do this, rather dan doing it ad-hoc each time a question turns up.

@gvanrossum
Copy link
Collaborator Author

A list of popular PyPI packages is published monthly here: https://hugovk.github.io/top-pypi-packages/

There are docs for accessing PyPI via API here: https://warehouse.pypa.io/api-reference/json.html

Is it worth it to separately also download popular GitHub projects? If they contain Python code they should be on PyPI, right? (Assuming they are popular.)

@gvanrossum
Copy link
Collaborator Author

I'm done with this (for the time being), the results are posted in https://github.com/faster-cpython/tools/

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

No branches or pull requests

1 participant