On 09. 09. 21 23:36, Antonio Cuni wrote:
On Thu, Sep 9, 2021 at 5:06 PM Marc-Andre Lemburg <mal@egenix.com> wrote:
Analyze the top PyPI packages, identify the ones which would break and send the maintainers an email explaining the change.
for this particular issue, I have a repository which contains the C code in the top 4000 PyPI packages: https://github.com/hpyproject/top4000-pypi-packages
the repo is imperfect: to keep the size small it contains only the C code (thus you can't build the packages from there), I manually removed some duplicated/vendored/autogenerated files and it's just a snapshot of a certain point in time. However, it is very useful in combination with grep to have some idea of how often a certain API and/or pattern is used in the real world.
Sadly, "top 4000 PyPI packages" is very biased towards widely-used projects and the public projects -- ones least likely to have issues, because the community (of widely-used projects) or the author of the CPython change (for public projects) can submit fixes early.
It would be sad if CPython focused only on successful, public projects; but I fear that's where we'll end up if we use this heuristic when evaluating changes.