Sorry, I do not understand the answer. Something in the upgrade of 
setuptools provoke that after any small change (or even none), sagelib is 
completely rebuilt.

El viernes, 29 de agosto de 2025 a las 18:00:48 UTC+2, Dima Pasechnik 
escribió:

> Sticking to the old half-btoken tools while the world moves on is not a 
> solution.
>
> We have a bunch of 10-year old code (SageKernelSpec class etc) meant to do 
> what nowadays can be done with one call to "jupyter kernelspec".
>
>
>
> On August 29, 2025 9:41:15 AM CDT, Enrique Artal <[email protected]> 
> wrote:
>
>> There was another (worse) way to solve it, to downgrade setuptools; 
>> actually this downgrading also solved another issue, namely the complete 
>> building of sagelib for any run of make.
>>
>> El jueves, 28 de agosto de 2025 a las 18:42:16 UTC+2, Dima Pasechnik 
>> escribió:
>>
>>>
>>>
>>> On August 28, 2025 11:15:17 AM CDT, Eric Gourgoulhon <
>>> [email protected]> wrote: 
>>> >Hi, 
>>> > 
>>> >I've just built Sage 10.8.beta1 from a fresh git clone, after having 
>>> >removed by hand the dead https://ftp.rediris.es/mirror/sagemath/ 
>>> ><
>>> https://ftp.rediris.es/mirror/sagemath/spkg/upstream/cython/cython-3.1.3.tar.gz>
>>>  
>>> from 
>>> >upstream/mirror_list, following this advice: 
>>> >https://groups.google.com/g/sage-release/c/CqAD2Y1f_5E/m/lHBJEgEPAAAJ 
>>> >The build finished successively and Sage works in console mode, but the 
>>> >command 
>>> > 
>>> >sage -n jupyterlab 
>>> > 
>>> >fails to find any SageMath kernel... 
>>> >This issue seems to have reported already for Sage 10.8.beta0: 
>>> > https://groups.google.com/g/sage-release/c/CqAD2Y1f_5E/m/oUgrS1S3AAAJ 
>>>
>>> a fix for this is attempted in #40700 
>>>
>>> > 
>>> >Eric. 
>>> > 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" 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-release/08bdae2c-030b-4c54-890e-39393cae30fdn%40googlegroups.com.

Reply via email to