Add mapping for 'sage' to 'sagemath'
📝 Summary
Adds the correct upstream Python package for the sage import.
🔍 Description of Changes
Alternative to https://github.com/marimo-team/marimo/pull/7151. Here we use the official upstream package as the target of the mapping, and not an unofficial fork.
📋 Checklist
- [x] I have read the contributor guidelines.
- [ ] For large changes, or changes that affect the public API: this change was discussed or approved through an issue, on Discord, or the community discussions (Please provide a link if applicable).
- [ ] I have added tests for the changes made.
- [ ] I have run the code and verified that it works as expected.
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| marimo-docs | Preview | Comment | Nov 12, 2025 3:13am |
All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.
I have read the CLA Document and I hereby sign the CLA
@dmadisetti I cannot comment on https://github.com/marimo-team/marimo/pull/7151, so let me respond here:
Ah, ok. We can also pre-package the bins for molab, but I think the official sage distribution is what most users would expect
Let me know if I can help with the pre-building of sagemath (which is indeed the recommended Python package to install). It can be installed using pip / uv / ... as documented at https://doc-develop--sagemath.netlify.app/html/en/installation/source (you have to ensure though that all required system packages are available). We are working on providing binary wheels.
Thanks for opening this @tobiasdiez - but I was under the impression sagemath-standard was the general package for distribution
I can't speaking for everyone, but objectively
- sagemath-standard released has indeed stopped since 10.8.b1, and nobody has gotten around to fix it yet
- I'm not working on any packaging aspect.
So, if you can get sagemath to work, great, problems solved. If not, I don't mind providing an unofficial fork (*) for 10 years (**) until sage finally provide binary packages.
(*) if you are scared of malwares, just pin to a particular version. But I doubt... Also that you're stuck on the equivalent of 10.6 or so. You can give a warning to the user if you want.
(**) maybe exaggeration, maybe not.
Thanks for opening this @tobiasdiez - but I was under the impression sagemath-standard was the general package for distribution
sagemath-standard refers to the old setuptools-based distribution, which by now is discontinued and no longer present in the sagemath git repo. sagemath is the new meson-based distribution that should be used now (it was introduced in https://github.com/sagemath/sage/pull/39548, at that point still in parallel to sagemath-standard).