The coxeter3 package is not the only one. The optional packages meataxe and sirocco also have .pyx files with no associated .so file. Those three are the only optional packages which appear in venv/lib/python3.12/site-packages/sage/libs even though many other optional packages are enabled by my configure command. I have no idea what would cause an optional package to be there. But whatever the mechanism may be, it also seems to cause the extension module for such an optional package not to get built.
- Marc On Sunday, January 26, 2025 at 11:50:57 AM UTC-6 Marc Culler wrote: > In the venv of my recently built SageMath-10.6beta4 I find: > % ls lib/python3.12/site-packages/sage/libs/coxeter3 > __init__.py coxeter.pxd decl.pxd __pycache__ coxeter.pyx > all__sagemath_coxeter3.py coxeter_group.py > > In other subdirectories of sage/libs, such as flint, one finds that every > .pyx file has an associated .so file in the same subdirectory. So I would > expect to find > lib/python3.12/site-packages/sage/libs/coxeter3/coxeter-cpython-312-darwin.so, > > but it is not there. > That seems to suggest that coxeter.pyx is not being compiled by cython, > and therefore that the extension module sage.libs.coxeter3.coxeter is not > being built and hence is not installed. > > So it looks to me like the sagelib build process is skipping the step of > cythonizing and compiling cython extension modules that are part of an > optional package. > > Am I missing some step which is needed for this to happen? I have used > the --enable-coxeter3 flag in the configure command. Do I need to do > something else? > > - 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 sage-devel+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/8b30dece-d842-401b-bf72-c012f9e57757n%40googlegroups.com.
