[sage-devel] Re: Package upgrade PRs waiting for review

2024-09-05 Thread 'tobia...@gmx.de' via sage-devel
@Kwankyu, replying here to your comments. The cython constraint in scipy is for build-time. Sagelib only cares about the fact that scipy is installed in the same venv, not how you install or build it. In fact, pip uses build isolation by default, or you may install scipy using the prebuilt whee

Re: [sage-devel] Re: Memory leak in `NumberField().class_group().order()`

2024-09-05 Thread Marc Culler
Caching uses memory intentionally, for the purpose of speeding up computations. Leaks use memory unintentionally, for no purpose. I don't know where the caching happens. I only deduce that it exists because, when running the same computation twice, the second time is faster. However, the cachi

[sage-devel] Bug report 2nd try

2024-09-05 Thread 'OHappyDay' via sage-devel
I recently stumbled upon something that looks like a bug: Try to integrate the following function: f(x)=log(1+4*cos(x)+4) integrate(f,x,0,pi) According to the following video (https://www.youtube.com/watch?v=nscSDYApAjM) the result should be 2*pi*log(2) But my local Sage as well as online I g

Re: [sage-devel] Re: Memory leak in `NumberField().class_group().order()`

2024-09-05 Thread Georgi Guninski
On Wed, Sep 4, 2024 at 11:13 PM Marc Culler wrote: > > I think that here you are seeing caching taking place, rather than a memory > leak. This is what I tried: > > You call this caching, I call it leak, it can be both ways. It is natural to compute the class numbers of QQ[sqrt(-n)] and it shoul