>As well, with cypari, a call to pari.getheap() adds 1 object there, a
bug, I guess.
>(this does not happen with cypari2)
>In [14]: pari.getheap()
>Out[14]: [334, 163655741]
>In [15]: pari.getheap()
>Out[15]: [335, 163655758]
I can't reproduce this on 10.4:
sage: s=pari.getheap()
sage: fo
On Sat, Aug 31, 2024 at 4:35 AM Marc Culler wrote:
>
> As Dima says, and as the issue he mentions supports, the current cypari2 code
> which attempts to keep Pari Gens on the Pari stack as much as possible is
> badly broken. There are many situations where Python Gen objects cannot be
> garbag
On Fri, 2024-08-30 at 20:26 -0700, Kwankyu Lee wrote:
>
> What do you think?
Why not do what everyone else does, and let developers merge PRs into
the "develop" branch when they're approved? Waiting only causes merge
conflicts. The release manager could still cherry-pick commits for
betas, relea
