On Saturday, August 30, 2025 at 1:00:48 AM UTC+9 Dima Pasechnik wrote: 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". Are you sure that SageKernelSpec class was created due to lack of "jupyter kernelspec" 10 years ago? It is not sound that some code is regarded half-broken because it is 10 years old. It worked well just before something (setuptools or build system) has changed recently in our codebase. The missing sagemath kernel issue is a way more serious problem than sticking to the old tools. If we don't have a good solution, sticking to the old tools is a reasonable solution. -- 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/f2cea524-dcf8-42c9-a38e-d25902392f05n%40googlegroups.com.
