[sage-devel] Re: QQbar(-1)^(1/3) != AA(-1)^(1/3)

Dima Pasechnik wrote: > the function 1/n : AA->AA is 1-1 on all AA, and I don't see why this > property should be broken. Mathematically it makes perfect sense as > is. Because the ** operator is part of the coercion system, and AA coerces into QQbar, CC, etc. > In fact, it should also work like

Re: [sage-devel] Re: Memory leak in |EllipticCurve([n,0]).root_number()| and problem in algebraic geometry

> How do you know that doesn't leak? Do you mean that repeated execution of > those commands in the same session does not swell memory use? I am computing the root number in a loop, collect garbage and measure the used memory using `Process.memory_info().rss` > It may even be the case that 128

Re: [sage-devel] Re: Synchronization of GitHub state and priority labels continues on Tuesday July 11th

On Friday, August 30, 2024 at 9:48:39 AM UTC+9 Matthias Koeppe wrote: Make it a draft PR, then the synchronizer is not active. Confirmed. Thanks. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

Re: [sage-devel] Re: Synchronization of GitHub state and priority labels continues on Tuesday July 11th

Make it a draft PR, then the synchronizer is not active. If it's waiting for something external, I also add the "pending" label. On Thursday, August 29, 2024 at 5:07:20 PM UTC-7 Kwankyu Lee wrote: > OK, I can live without the "needs info" label. > > On the other hand, the PR is not yet for revie

Re: [sage-devel] Re: Synchronization of GitHub state and priority labels continues on Tuesday July 11th

OK, I can live without the "needs info" label. On the other hand, the PR is not yet for review because it intends to fix things in deprecation period. How can I stop the synchronizer from adding "needs review" whenever I push a commit? -- You received this message because you are subscribed to

[sage-devel] Re: Proposal: Demote jupyter-jsmol and tachyon to optional

The following PRs are open for review: - build/pkgs/jupyter_jsmol: Change to optional - Demote jmol to optional On Monday, August 19, 2024 at 5:13:29 PM UTC-7 Matthias Koeppe wrote: > jupyter-jsmol > <

Re: [sage-devel] Re: Memory leak in |EllipticCurve([n,0]).root_number()| and problem in algebraic geometry

It would be good to reproduce this with cypari2 alone. cypari2 is known to have similar kind (?) of problems: https://github.com/sagemath/cypari2/issues/112 On Thu, Aug 29, 2024 at 6:47 PM Nils Bruin wrote: > > On Thursday 29 August 2024 at 09:51:04 UTC-7 Georgi Guninski wrote: > > I observe tha

Re: [sage-devel] Re: Synchronization of GitHub state and priority labels continues on Tuesday July 11th

In this example, the synchronizer has been removing the "needs info" label from the PR on pushes. Perhaps we should just phase out the use of the "needs info" label for PRs. Personally, I do not recall much success in soliciting info from others using the "needs info" label. It may just be too

Re: [sage-devel] Re: Memory leak in |EllipticCurve([n,0]).root_number()| and problem in algebraic geometry

On Thursday 29 August 2024 at 09:51:04 UTC-7 Georgi Guninski wrote: I observe that the following does not leak: E=EllipticCurve([5*13,0]) #no leak rn=E.root_number() How do you know that doesn't leak? Do you mean that repeated execution of those commands in the same session does not swell m

Re: [sage-devel] Re: Memory leak in |EllipticCurve([n,0]).root_number()| and problem in algebraic geometry

I observe that the following does not leak: E=EllipticCurve([5*13,0]) #no leak rn=E.root_number() The size of the leak is suspiciously close to a power of two. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and st

Re: [sage-devel] QQbar(-1)^(1/3) != AA(-1)^(1/3)

On 28 August 2024 16:05:43 BST, Georgi Guninski wrote: >All of the following return the complex branch: >pari/gp, mpmath, maxima > This is just them lacking functionality specifically for real fields, not something to copy. One can always coerse a real field element to an extension containin

[sage-devel] Re: Memory leak in |EllipticCurve([n,0]).root_number()| and problem in algebraic geometry

The leakage does not seem to be happening on the python heap. A next step could be to see if cypari's stack is swelling. On Thursday 29 August 2024 at 02:34:06 UTC-7 Georgi Guninski wrote: > In short: > ``` > for A2 in range(1, 10**5): > E=EllipticCurve([A2,0]) > rn=E.root_number() > ``` > leaks

[sage-devel] Memory leak in |EllipticCurve([n,0]).root_number()| and problem in algebraic geometry

In short: ``` for A2 in range(1, 10**5): E=EllipticCurve([A2,0]) rn=E.root_number() ``` leaks nearly 128MB of memory on sage 10.4 The same code in pari passes with very little memory. This is related to the following problem in algebraic geometry [1] Let $k,k_1,k_2$ be squarefree pairwise