Sagemath installation via Ubuntu 22.04 on Windows presents an error due to missing package #2204 #sagemath
@sagemath 10.6 has been released on April 1, 2025. SageMath now supports RISC-V systems.
A total of 75 people contributed to this release. Of those, 24 made their first contribution to Sage.
More info about this release on https://github.com/sagemath/sage/wiki/Sage-10.6-Release-Tour
The source code can be found on https://github.com/sagemath/sage/releases/tag/10.6
I saw today that my CoCalc (https://cocalc.com/) license was about to renew. I've been meaning to move to a more #SelfHosting or #P2P paradigm, so this was good timing for me to cancel. I left this message when doing so:
"I want to support Sage, and I like using CoCalc, but I don't want to put money towards a service that supports Microsoft, Amazon, or OpenAI in any way. I didn't care so much about this before, and I even log in to CoCalc with a GitHub account, but I'm tired of having my work scraped for profit by people who donate to fascists who are destroying my nation. I would consider returning if all ties to these corporations were cut and cloud computing services came from responsible companies, perhaps in the EU."
I'm pretty sure I already have backups of everything I want from GitHub, so I can be done with them too. I should have quit when Microsoft first arrived. My plan is to switch to Radicle (https://radicle.xyz/) rather than another centralized service. I'll be sure to post about how that goes.
I recently read a paper by Kleshnina and others and used it to teach myself some evolutionary game theory techniques.
This is a little obscure, so I'll thread below about why this topic matters for humans and the environment 
#Switch to #OpenSource solutions in #Linux
Photoshop: #Photopea
Illustrator: #Inkscape
PremierePro: #Kdenlive #Shotcut #OBStudio
Office: #FreeOffice #LibreOffice
Maya: #Blender
Media: #VLC
Unity: #Godot
ToonBoom: #SynfigStudio #Pencil2D
InDesign: #Scribus
Nuke: #Natron
Procreate: #Krita
After Effects: #Friction
Mathematica: #SageMath #SymPy
MatLab: #GnuOctave
Audition: #Audacity
Autocad: #FreeCAD #QCad
Ableton: #Ardour #LMMS (daily build)
Lightroom: #DarkTable, #RawTherapee
And more...
#Switch to #opensource solutions:
Windows: #Linux
Photoshop: #Gimp 3.0-rc
Illustrator: #Inkscape
PremierePro: #Kdenlive, #Shotcut
Office/Acrobat: #OnlyOffice, #LibreOffice
Maya: #Blender
Media: #VLC
Unity: #Godot
ToonBoom: #SynfigStudio, #Pencil2D
InDesign: #Scribus
Nuke: #Natron
Procreate: #Krita
After Effects: #Friction
Mathematica: #SageMath, #SymPy
MatLab: #GnuOctave
Audition: #Audacity
Autocad: #FreeCAD, #QCad
Ableton: #Ardour, #LMMS (daily build)
Lightroom: #DarkTable, #RawTherapee
I've been a fan of Sage (https://www.sagemath.org/) and CoCalc (https://cocalc.com/) for some time, and I would now like to complain.
Sage is an open source computer algebra system which is written in Python, but for technical reasons comes with its own version of the Python interpreter. The first IDE I used regularly was Eclipse, and I used to know the arcane steps needed to make it use the Sage Python binary on various systems.
I switched to PyCharm some years ago, but I have only been using it to write pure Python. Now I want to use Sage, so I tried doing the same gymnastics I used to do with Eclipse and was annoyed.
I decided that being forced to work online wasn't a big deal, so I'd use CoCalc instead. Even though CoCalc was made with Sage in mind, there does not seem to be direct support for running Python modules with Sage, only the notebook style is promoted. It seems absurd to me that after all these years it is still so much work to simply use Sage in a Python project with an IDE.
In addition to this, Sage's support for the kinds of calculations I want to do at the moment is quite immature, with TODO in many, many places.
I want to use Sage since it combines many useful (and fast) libraries that I need, but I think I need to just accept that I should start building my own solution that works for my purposes.
I know that I could contribute to Sage, but I feel like the weight of changing what I need to change is so much, and that I would get my calculation done faster by just doing it myself.
I have also written an finicky to setup xdg-desktop-portal that let one choose #files using #emacs https://codeberg.org/rahguzar/filechooser , an Emacs interface to #hoogle https://codeberg.org/rahguzar/consult-hoogle
There is a (kind of in progress) major mode for #sagemath https://codeberg.org/rahguzar/sage-mode which hasn't seen much progress in a while because it is usable for its only user i.e. me.
Recently I managed to make produce a (humongous) #texinfo manual for Sage so that I can read it from Emacs https://github.com/sagemath/sage/issues/21734
@ssmns
نمونههای مناسب هستن (مثل #Sagemath و #Octave) درمورد سرعت و ... قبول دارم بعضی جاها. ولی اون مسئله که گفتم رو نمیشه با آزمون پسدادن حل کرد!
یکی از اصلهای پایهای کار علمی، بازتولیدپذیری (Reproducibility) باید باشه. 
حداقلش نیاز به پرداخت هزینههای بالا برای رسیدن به اون نتیجهٔ قبلیه. تازه اگه مطمئن باشیم واقعا همون نتیجهٔ قبلیه و اگه از اون وجود خطاهای احتمالی چشمپوشی کنیم!
@mariatta, I think I would have enjoyed PyConUS. My attitude toward #python has been evolving rapidly. My first encounter was in the 90s looking at the mailman code, but never touched it or looked at it until a couple of years ago.
My reintroduction was via #SageMath. I liked using Python for teaching about other things, including #cryptography. I could write things that would be readable to many people and I didn’t have to use a bigint library. So I have largely shifted to #jupyter from #RMarkdown for my own notes on things and for exposition.
But (putting it mildly) I am not a fan of dynamic typing, and I was coding against the grain. But a very wise friend, @averagesecurityguy said, “Let Python be Python”.
The work of the Python typing community has helped me enormously. If I broaden my notion of “compile time” to include #mypy checks, then I have decent compile time type checking, while letting Python be Python.
Sometimes it takes more time to refute a `gcc` bug than confirm it. This week I spent most time on https://gcc.gnu.org/PR114872 where `sagemath` `SIGSEGV`ed on some simple inputs.
Bug updates are a bit hard to read and are missing a bit of compiler-unrelated context. I wrote something more coherent in https://trofi.github.io/posts/312-the-sagemath-saga.html
I discovered today that #ChatGPT and #CoCalc (which already has AI integration) make it extremely easy to perform any #sagemath computation that can be described to GPT; I used this to perform enough numerics to arrive at the solution to a problem in https://mathoverflow.net/a/454051/766 . (The GPT provided code did contain some minor syntax errors, but CoCalc’s native AI could easily fix them.) I did not feel proficient enough in the past to use Sage on a regular basis, but now I think I will.
@ai @Hyolobrika @jeffcliff here is another example where #maxima and #sagemath fail to simplify a summation . Wolframalpha.com also fails to find the pi/16 value but gives different closed forms and a numerical value compatible with pi/16
sum(1.0*sin(n*pi/3)^3*cos(n*pi/3)/n,n,1,Infinity)
### sage false result
S= 2.4150948914066888
## exact value
S_exact= 1/16*pi = 0.19634954084936207
## partial sum agree with exact value
S_num= 0.11348739774386768*sqrt(3) = 0.1965659389111564
@ai I don't think so. I proved the formulas above using the Dirichlet theorem applied to the Fourier series expansion of the 2*pi periodic function :
f(x)= cos(x) for x in [0,pi[
f(x)=0 for x in [-pi,0[
my post was about the bug appearing when I want to verify the formula with in maxima (and also with #sagemath) see http://rouxph.blogspot.com/2020/04/calcul-de-series-et-bug-dans-wxmaxima.html
An #introduction: I'm a senior research scientist at #ICERM working in theoretical and computation number theory. I also contribute to the #LMFDB (L-function and modular form database), to #sagemath, and to a variety of other projects in open source math software. I typically write either #python or #cpp and I'm happy to talk about #math or #code.
I like #cooking, #cycling, #crosswords, and even things that don't begin with 'c'.
visiblement ils ont un gros problème de compatibilité avec 
