Remember how #PyYAML ignored #Cython 3 compatibility problems for a year and a half? Well, Cython 3 got released today and now the related bug exploded when tons of pipelines suddenly started failing.
Remember how #PyYAML ignored #Cython 3 compatibility problems for a year and a half? Well, Cython 3 got released today and now the related bug exploded when tons of pipelines suddenly started failing. 1 comment
|
The #PyYAML problem is only getting better. People are trying really hard to make their things work again. Apparently there's a way to force constraints on pip but it's not a perfect solution either.
I have two thoughts about this:
1. *Finally*, it's not just us in #Gentoo being hit by constraint conflicts (i.e. two packages in depgraph requiring different #Cython versions).
2. Given that PyYAML knew about the problem for a year and a half and did nothing to avoid it… do you think it's a good idea to continue using that package? Or #YAML in particular, Norway?
https://discuss.python.org/t/no-way-to-pin-build-dependencies/29833
#Python
The #PyYAML problem is only getting better. People are trying really hard to make their things work again. Apparently there's a way to force constraints on pip but it's not a perfect solution either.
I have two thoughts about this:
1. *Finally*, it's not just us in #Gentoo being hit by constraint conflicts (i.e. two packages in depgraph requiring different #Cython versions).