Cython errors when building p_group_cohomology

77 views
Skip to first unread message

Marc Culler

unread,
Nov 15, 2023, 6:49:04 PM11/15/23
to sage-devel
I am not able to build the optional package p_group_cohomology in 10.2.rc2 due to cython errors.

The first error looks like:

[p_group_cohomology-3.3.3.p1]   Error compiling Cython file:
[p_group_cohomology-3.3.3.p1]   -------------------------------------------
-----------------
[p_group_cohomology-3.3.3.p1]   ...
[p_group_cohomology-3.3.3.p1]   from sage.structure.element cimport Element
[p_group_cohomology-3.3.3.p1]   from .map cimport Map
[p_group_cohomology-3.3.3.p1]   ^
[p_group_cohomology-3.3.3.p1]   -------------------------------------------
-----------------
[p_group_cohomology-3.3.3.p1]
[p_group_cohomology-3.3.3.p1]   /XXX/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/sage/categories/morphism.pxd:2:0: 'sage/categories/map.pxd' not found

In fact, the file map.pxd does exist in the same directory as morphism.pxd, which is the file containing the failing cimport line.  But the missing path reported by cython is not an absolute path: sage/categories/map.pxd.  I don't know to which base directory that relative path is meant to be applied, but evidently it is wrong.

I will attach the log file.

- Marc
p_group_cohomology-3.3.3.p1.log

Matthias Koeppe

unread,
Nov 15, 2023, 6:57:07 PM11/15/23
to sage-devel
This will need an adjustment for namespace packages, see

Dima Pasechnik

unread,
Nov 15, 2023, 7:51:20 PM11/15/23
to sage-...@googlegroups.com
This package produces mathematically incorrect results, as was shown on a trac ticket a couple of years ago, and no movement then. Demote to experimental?

Michael Orlitzky

unread,
Nov 15, 2023, 8:04:11 PM11/15/23
to sage-...@googlegroups.com
On 2023-11-16 00:51:12, Dima Pasechnik wrote:
> This package produces mathematically incorrect results, as was shown
> on a trac ticket a couple of years ago, and no movement then. Demote
> to experimental?

There's not much distinction at this point, but if we're going by the
"builds on supported platforms" criteria, then it makes sense.

What would make even more sense is to give it a meson.build file (to
locate singular and gap), stick it on pypi, and then delete it from
the sage repo because at that point it could be installed with pip.

Edgar Costa

unread,
Nov 15, 2023, 8:15:45 PM11/15/23
to sage-...@googlegroups.com

--
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 sage-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/b0293496-5e25-49d5-bd11-78928bb3ecb6n%40googlegroups.com.

Marc Culler

unread,
Nov 16, 2023, 12:03:27 PM11/16/23
to sage-devel
Thank you, Edgar!  That worked.

- Marc
Reply all
Reply to author
Forward
0 new messages