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

2024-09-15 Thread Nils Bruin
On Sunday 15 September 2024 at 10:46:06 UTC-7 marc@gmail.com wrote: > You can grab one of those objects on the heap and look at its backreference graph How does one do that? You can grab one of the objects: next(a for a in gc.get_objects() if id(a) not in pre and str(type(a)) == "") (

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

2024-09-15 Thread Marc Culler
> You can grab one of those objects on the heap and look at its backreference > graph How does one do that? - Marc On Sun, Sep 15, 2024 at 11:17 AM Nils Bruin wrote: > > On Sunday 15 September 2024 at 10:08:18 UTC-7 dim...@gmail.com wrote: > > For me this code is rather unpredictable, as ipyth

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

2024-09-15 Thread Nils Bruin
On Sunday 15 September 2024 at 10:08:18 UTC-7 dim...@gmail.com wrote: For me this code is rather unpredictable, as ipython and prompt_toolkit kick in and produce extra objects. For consistency (at least them the output values are reproducible) it looks better to experiment with Sage's python

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

2024-09-15 Thread Dima Pasechnik
For me this code is rather unpredictable, as ipython and prompt_toolkit kick in and produce extra objects. For consistency (at least them the output values are reproducible) it looks better to experiment with Sage's python (./sage --python) for which the code needs to be adjusted, with "^" replace

Re: [sage-devel] Unable to build sagelib on macOS arm64

2024-09-15 Thread Dima Pasechnik
it appears that m4ri was not successfully built. Please post the corresponding log file, logs/pkgs/m4ri*.log On Sun, Sep 15, 2024 at 5:37 AM Mavin Hellman wrote: > > Attempting to build Sage 10.5 beta on macOS Version 14.2.1 (23C71) > > ``` > [sagelib-10.5.beta3] [spkg-install] ld: illegal t