4 ms·

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.

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/ https://pypi.org/project/ninja/ [1] https://github.com/scikit-build/ninja-python-distributions/issues/308 https://github.com/scikit-build/ninja-python-distributions/i...

endgame 7mo ago
Why is a C++ project being distributed on PyPi at all?
- grim_io 7mo ago
  Probably for the same reason other binaries are distributed by npm: lack of cross platform general package managers and registries
  - mikepurvis 7mo ago
    Also for cases where a python project needs to depend on it.
    - Ferret7446 7mo ago
      Kinda weird to have the language toolchain wrap the build system, should be the other way around.
      - mikepurvis 7mo ago
        Yes, but I mean... this is Python we're talking about. There are several build systems / coordinators written in Python (scons, colcon, etc) not to mention Python packages that themselves contain compiled bits written in other languages. I know nowadays we have formalized, cross-platform ways to build bindings (scikit-build-core, etc), but that is a relatively recent development; for a long ass time it was pretty common place to have a setup.py full of shell-outs to native toolchains and build tools. It's not hard to imagine a person in that headspace feeling like being able to pull that stuff directly from pypi would be an upgrade over trying to detect it missing and instruct the user to install it before trying again.
  - verdverm 7mo ago
    Or lack of a tool like Goreleaser in the language ecosystem that handles that
- zahlman 7mo ago
  You may be interested in this discussion: https://discuss.python.org/t/use-of-pypi-as-a-generic-storage-platform-for-binaries/106044 https://discuss.python.org/t/use-of-pypi-as-a-generic-storag...
- tadfisher 7mo ago
  Because the development world either hasn't heard of nix or has collectively decided to not use nix.
- hulitu 7mo ago
  You need to bundle a supply chain attack with it. /s
j1elo 7mo ago
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.

endgame 7mo ago

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

grim_io 7mo ago
Probably for the same reason other binaries are distributed by npm: lack of cross platform general package managers and registries
- mikepurvis 7mo ago
  Also for cases where a python project needs to depend on it.
  - Ferret7446 7mo ago
    Kinda weird to have the language toolchain wrap the build system, should be the other way around.
    - mikepurvis 7mo ago
      Yes, but I mean... this is Python we're talking about. There are several build systems / coordinators written in Python (scons, colcon, etc) not to mention Python packages that themselves contain compiled bits written in other languages. I know nowadays we have formalized, cross-platform ways to build bindings (scikit-build-core, etc), but that is a relatively recent development; for a long ass time it was pretty common place to have a setup.py full of shell-outs to native toolchains and build tools. It's not hard to imagine a person in that headspace feeling like being able to pull that stuff directly from pypi would be an upgrade over trying to detect it missing and instruct the user to install it before trying again.
- verdverm 7mo ago
  Or lack of a tool like Goreleaser in the language ecosystem that handles that
zahlman 7mo ago
You may be interested in this discussion: https://discuss.python.org/t/use-of-pypi-as-a-generic-storage-platform-for-binaries/106044 https://discuss.python.org/t/use-of-pypi-as-a-generic-storag...
tadfisher 7mo ago
Because the development world either hasn't heard of nix or has collectively decided to not use nix.
hulitu 7mo ago
You need to bundle a supply chain attack with it. /s

j1elo 7mo ago

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.