4 ms·
This broke a lot of stuff for us at work today. Building the wheels or something I can’t remember. The fix was forcing pip to use not the 3.x and use something
by gigatexal 3y ago
This broke a lot of stuff for us at work today. Building the wheels or something I can’t remember. The fix was forcing pip to use not the 3.x and use something older I think.
- gyrovagueGeist 3y agoJust so anyone who reads this has the version: cython<=0.29.36 is the most recent non 3.0.0 version.
- esafak 3y agoAs always: pin your dependencies.
- unpythonic 3y agoSadly, it's not always that simple. If one of your well-pinned packages has a build dependency which is not correctly pinned, then you're subject to the problem.
- physicsguy 3y agoCython did everything right here since it used a major version number to signify the change. Other projets not pinning their dependencies is not their fault!
- lazka 3y agoThey don't use pinning in their examples: https://cython.readthedocs.io/en/latest/src/userguide/source_files_and_compilation.html#basic-setup-py https://cython.readthedocs.io/en/latest/src/userguide/source... and https://cython.readthedocs.io/en/latest/src/userguide/source_files_and_compilation.html#distributing-cython-modules https://cython.readthedocs.io/en/latest/src/userguide/source...
- physicsguy 3y agoPinning depends on the requirements you as the consumer have, and the specific package manager (pip, conda, poetry, etc.) so it's hard to give guidance that's helpful when you're a library maintainer. Generally when consuming any dependency you should pin though...