× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [1593 lines of output]
Error compiling Cython file:
------------------------------------------------------------
...
# Distributed under the terms of the GNU General Public License (GPL) either
# version 2, or (at your option) any later version
#
# http://www.gnu.org/licenses/
from sage.libs.arb.types cimport *
^
------------------------------------------------------------
src/ore_algebra/analytic/binary_splitting_arb.pyx:17:0: 'sage/libs/arb/types.pxd' not found
Both of the above commands work correctly with Sage 10.7.
--
Marc
Marc Mezzarobba
unread,
Aug 29, 2025, 4:58:58 AM (7 days ago) Aug 29
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to sage-...@googlegroups.com
Marc Mezzarobba wrote:
> It looks like Sage 10.8.beta0 broke the installation of external
> packages that include Cython modules.
Update: I just noticed that 10.8.beta1 is out. The issue is still
present.
--
Marc
Dima Pasechnik
unread,
Aug 29, 2025, 8:29:04 PM (6 days ago) Aug 29
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to sage-...@googlegroups.com
yes, it appears as if sage.env.sage_include_directories() got broken.
Not the least due to its test being too weak.
In a macOS setup I tried, I'm getting, as output,
['/Users/dima/software/sage/local/var/lib/sage/venv-python3.13/lib/python3.13/site-packages/_sagemath_editable_loader.py',
'/Users/dima/software/sage/local/var/lib/sage/venv-python3.13/lib/python3.13/site-packages/numpy/_core/include',
'/Library/Frameworks/Python.framework/Versions/3.13/include/python3.13']
and it's obvious that these are not locations where one can hope to
find Sage's .pxd files
(from a Sage installation in ~/software/sage).
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to sage-...@googlegroups.com
On Fri, Aug 29, 2025 at 6:47 PM Dima Pasechnik <dim...@gmail.com> wrote:
>
> yes, it appears as if sage.env.sage_include_directories() got broken.
> Not the least due to its test being too weak.
> In a macOS setup I tried, I'm getting, as output,
> ['/Users/dima/software/sage/local/var/lib/sage/venv-python3.13/lib/python3.13/site-packages/_sagemath_editable_loader.py',
> '/Users/dima/software/sage/local/var/lib/sage/venv-python3.13/lib/python3.13/site-packages/numpy/_core/include',
> '/Library/Frameworks/Python.framework/Versions/3.13/include/python3.13']
>
> and it's obvious that these are not locations where one can hope to
> find Sage's .pxd files
> (from a Sage installation in ~/software/sage).