If someone sees this: The ninja package on PyPI [0] currently stays at version 1.13.0 . There is an issue in 1.13.0 preventing it building projects on Windows. The issue is already fixed in 1.13.1 almost a year ago, but the PyPI package hasn't got an update, see [1], and many downstream projects have to stay at 1.11 . I hope it could update soon.

[0] https://pypi.org/project/ninja/

[1] https://github.com/scikit-build/ninja-python-distributions/i...

▲

endgame 12 hours ago | parent | next [-]

Why is a C++ project being distributed on PyPi at all?

▲

grim_io 12 hours ago | parent | next [-]

Probably for the same reason other binaries are distributed by npm: lack of cross platform general package managers and registries

	▲	mikepurvis 11 hours ago \| parent \| next [-]
		Also for cases where a python project needs to depend on it.
	▲	verdverm 9 hours ago \| parent \| prev [-]
		Or lack of a tool like Goreleaser in the language ecosystem that handles that

▲

zahlman 8 hours ago | parent | prev | next [-]

You may be interested in this discussion: https://discuss.python.org/t/use-of-pypi-as-a-generic-storag...

▲

tadfisher 7 hours ago | parent | prev [-]

Because the development world either hasn't heard of nix or has collectively decided to not use nix.

▲

j1elo 11 hours ago | parent | prev [-]

What a messy and frankly, absurd situation to be left in. To fork a project in order to provide a tool through Pypi, only to then stop updating it on a broken version. That's more a disservice than a service for the community... If you're going to stay stuck, better to drop the broken release and stay stuck on the previous working one.