It's really great to see data being gathered on the impact of changes.
As we've already seen in this thread, there are many suggestions for how to
gather more data and thoughts on how the methodology might be enhanced --
and these suggestions are great -- but just having a means to gather some
imp
Hi Steve,
I completely agree with all you said ;-)
I will not debate here if incompatible changes are worth it or not,
this topic was discussed recently in another thread.
On Fri, Dec 3, 2021 at 2:56 PM Steve Dower wrote:
> FTR, I don't consider the top projects on PyPI to be representative of
FTR, I don't consider the top projects on PyPI to be representative of
our user base, and *especially* not representative of people compiling
native modules.
This is not a good way to evaluate the impact of breaking changes.
It would be far safer to assume that every change is going to break
Hi,
You're correct that the download_pypi_top.py script only downloads the
latest version. I'm looking for projects impacted by incompatible
changes. If the latest version is fine, a project just has to update
its dependencies. If the latest version has an issue, it's very likely
that old versions
On Fri, 2021-12-03 at 00:44 +0100, Victor Stinner wrote:
> I wrote two scripts based on the work of INADA-san's work to (1)
> download the source code of the PyPI top 5000 projects (2) search for
> a regex in these projects (compressed source archives).
>
> You can use these tools if you work on a
