Closed strogdon closed 1 year ago
I was going to ask why you still are on pandas-1.5.2 instead of 2.0.3-r1, but it looks like 2.0.3-r1 is still cython<3 only. It is from 2.1.0 that it supports cython-3. I did not notice because my pandas is ~arch, since I needed fixes for sqlalchemy-2.0.0 early on.
Either, I can keyword pandas or it should be stabilised shortly. Still, what is holding pandas back for you?
As far as I know I can use any pandas. But since I'm not ~arch maybe it should be keyworded.
Or I can just keyword it locally. But others may have an issue.
The issue will hardy be unique to sage. I imagine some other people will get caught in that kind of stuff so long as there is not a cython 3 version of all the packages in the tree - or even at least an ~arch version. I can imagine some relatively dead package will never make the move without a distro patch. It will take time.
It appears that https://bugs.gentoo.org/915281 has been fixed.
Indeed. I do hope sage 10.2 comes out very soon. It is currently impossible to emerge 10.1 because there is no cython<3 numpy left in the tree.
Unless I'm missing something there is the above conflict. I built Sage with the above cython
And then after
emerge -puDN world
I havewhich appears to be due to
pandas