Gonzalo Tornaría

This looks better to me than #49606 in that it avoids the vendored zstd.

> > Cython's namespace package support has bugs. So what's the problem with not using it (for now, until it's ready)? > > Once again, Sage is not affected by...

> This is incompatible with the modularization work and cannot be merged. At the very least I systematically need to `touch src/sage/__init__.py` because sagemath is broken without this file.

> > I systematically need to `touch src/sage/__init__.py` because sagemath is broken without this file. > > Because of a system install of Sage components as discussed previously? Yes, and...

> > Could we please have as major goal to stop using "customization" of standard tools? > > Of course, that's a major goal. > > * [Meta-ticket: Eliminate use...

> @tornaria Of course your feedback is always appreciated. > > But some "implementation details" matter very much -- because of external constraints, namely the Python "ecosystem". Implicit namespace packages...

> > but activate the "sagemath-pari" part only if pari is available, etc. IOW, keep sage the library as a whole, but make it more "dynamic" on what software it...

> > > but activate the "sagemath-pari" part only if pari is available, etc. IOW, keep sage the library as a whole, but make it more "dynamic" on what software...

I realized the same thing happens in subsequent pages: if a state update is done _after a `pagebreak`_ and before `#set page()`. Change the snippet above to: ```typst #let var...

And this also affects polylux as in: ```typst #import "@preview/polylux:0.3.1": * #import themes.clean: * #show: clean-theme.with( footer: [Author, institution], short-title: [Short title], ) #slide[#lorem(20)] #slide[#lorem(20)] #utils.register-section("Introduction") #slide[#lorem(20)] #slide[#lorem(20)] ``` The...