On Thursday, October 2, 2025 at 1:50:37 PM UTC-5 [email protected] wrote:
By the way, to give you an example of careless, in my book, reviewing:
#40877.
(it wasn't actually even reviewed, the release manager just pushed it
through, over our protests).
It reverted #40765, which in particular made sure that there is a way to
find
Sage's cython directories, via sage.config. Now for instance
sage_numerical_backends_* (coin, etc) cannot be built because the old way
to find cython
directories is gone, and the new way got reverted.
So now, there is a request to revive sage_numerical_backends_coin, and one
has to dig through the branch of #40765 to fish out the necessary bits.
I don't know what this about I was able to build
sage_numerical_backends_coin with no problems by doing what I suggested in
my email. Namely:
replace the symlink
sage/build/pkgs/sage_numerical_backends_coin/package-versiion.txt ->
../../../VERSION.txt by a file containing one line: 10.4
With the symlink the upstream url is for a tatball with version number
10.8beta5 which of course does not exist since the latest version on pypi
is 10.4.
Once the tarball is downloaded the package builds fine and can be inported
into sage.
- Marc
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/sage-devel/b67337ba-e9b4-4345-a9bd-c5697295fd92n%40googlegroups.com.
