On Tue, 26 Feb 2019 at 21:17, Jeroen Demeyer J.Demeyer@ugent.be wrote:
On 2019-02-26 11:46, Nick Coghlan wrote:
A dozen or so entries from the top 100 that include binary extensions:
We really should make a difference between projects using the C API only indirectly through some other tool like Cython and packages using the C API directly. Although the split is not perfect, some Cython projects still use C API calls or implement some functionality in manually-written C extensions.
Indeed, but even doing that level investigation requires picking a set of popular packages to investigate :)
I'll also note that this will only pick up projects using the C API that are themselves distributed using PyPI. It won't pick up:
- Linux projects that are only shipped as distro packages (I'm
squatting solv, rpm, and dnf on PyPI because they're not pip-installable, but it would be potentially disastrous if "sudo pip install solv rpm dnf" actually did anything).
- applications embedding the Python runtime (Blender, Maya, ArcGIS, etc)
- other projects targeting the Python C API via a predefined platform
like https://www.vfxplatform.com/
Cheers, Nick.