Just to confirm, after I installed sagemath_coxeter3 the computation which
was reported on sage-support as failing, and which produced the traceback
saying that coxeter3 needed to be installed, now works fine:
┌─────────────────────────────────────────────┐
│ SageMath version 10.6.beta4, Release Date: 2025-01-18
│
│ Using Python 3.12.5. Type "help()" for help.
│
└─────────────────────────────────────────────┘
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Warning: this is a prerelease version, and it may be unstable.
┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
sage: R.<v> = LaurentPolynomialRing(ZZ, 'v')
sage: W = CoxeterGroup('A3', implementation='coxeter3')
sage: H = IwahoriHeckeAlgebra(W, v**2); Cp=H.Cp()
sage: Cp.product_on_basis(W([1,2,1]), W([3,1]))
(v^-1+v)*Cp[1,2,1,3]
sage: Cp.product_on_basis(W([1,2,1]), W([3,1,2]))
(v^-1+v)*Cp[1,2,1,3,2] + (v^-1+v)*Cp[1,2,1]
- Marc
On Sunday, January 26, 2025 at 1:03:42 PM UTC-6 Marc Culler wrote:
> Yes, I have a log file for coxeter3 which built fine.
>
> The problem turned out to be that I had to use BOTH ---enable-coxeter3 AND
> -enable-sagemath_coxeter3. With the latter option, the .so file gets build
> and installed as expected.
>
> Why? What is this about? And why does the traceback tell our user to
> install the coxeter3 package when the coxeter3 package is installed already
> and what is really needed is the sagemath_coxeter3 package?
>
> - Marc
> On Sunday, January 26, 2025 at 12:49:02 PM UTC-6 dim...@gmail.com wrote:
>
>> On Sun, Jan 26, 2025 at 11:51 AM Marc Culler <marc....@gmail.com> 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?
>>
>> do you have anything in logs/pkgs/coxeter* ?
>> If not, and if you use the standard make build (not meson-based one) you
>> may try
>>
>> make coxeter3
>>
>> and see how it goes.
>>
>> Dima
>>
>> >
>> > - 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+...@googlegroups.com.
>> > To view this discussion visit
>> https://groups.google.com/d/msgid/sage-devel/0762e04b-33ba-4bfa-8ee4-e145163dd7f7n%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/sage-devel/1a53cabd-1896-4ea9-82aa-7565531af856n%40googlegroups.com.
