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

> 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()`

As I said above this does not happen with either cypari or cypari2 when using getno. This is not a cypari issue. The issue is that Sage creates a "unique" object for each new number field, where new means that the input parameters for the NumberField function have not been used before. The number

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

sage: pari.getheap() [201, 4265] sage: On Sunday, September 8, 2024 at 9:12:14 AM UTC-6 Marc Culler wrote: > I agree that this is a bug. I do not think it is the same issue as the > leak you reported involving elliptic curves. The reason I don't think so > is that it is possibl

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

I agree that this is a bug. I do not think it is the same issue as the leak you reported involving elliptic curves. The reason I don't think so is that it is possible to compute class numbers with no memory leak using the PARI getno function in either cypari or cypari 2. There are many thing

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

i Guninski wrote: 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 n

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

On Monday, September 2, 2024 at 11:13:43 AM UTC-6 dima wrote: It appears that all these gunclone_deep() etc aren't documented in any proper way (and this is a root cause of this; same applies to memleaks we have in libsingular interface). Can you post a link to docs you are reading? I can only f

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

I think that here you are seeing caching taking place, rather than a memory leak. This is what I tried: sage: import cypari2 sage: pari = cypari2.Pari() sage: def test(N): : for a in range(1, N): : K = NumberField(x^2+a, 'w') : m = K.class_group().order :

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

Georgi, sorry for misspelling your name. - Marc On Tuesday, September 3, 2024 at 12:56:49 PM UTC-5 Marc Culler wrote: > That is a pretty interesting exchange, it indicates that this memory leak > has been known to exist for 6 years, and the remedy is also discussed > there. De

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

o explicitly call a destructor [ e.g. > obj_free ] any time a function such as 'ellinit' was used > > > It's not easy if the list of functions "such as 'ellinit'" is not known. > > <https://pari.math.u-bordeaux.fr/archives/pari-dev-1808/msg

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

s. prev_size in fastbins". I won't force this list to participate in the full debugging experience. The basic problem has been identified. The remedy is far from clear. - Marc On Sun, Sep 1, 2024, 5:37 PM Marc Culler wrote: > This is now fixed in cypari. The fix consisted of replacing

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

ext of the peculiar memory model used by cypari and cypari2. I tested the cypari fix on linux ubuntu using the test function described earlier in this thread. With 10**8 iterations it never used over 8.4MB of memory. - Marc On Sunday, September 1, 2024 at 12:07:26 PM UTC-6 Marc Culler wr

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

the call to ellrootno and is not uncloning all of those GENs. But it only does that with a newly created curve. - Marc On Sunday, September 1, 2024 at 10:24:33 AM UTC-6 Marc Culler wrote: > I would say that the getheap behavior is a symptom of the same memory > management bug(s). Also,

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

...@gmail.com wrote: > 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 si

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

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 garbage-collected after being destroyed. I am sure that is a big pa

Re: [sage-devel] Re: (I’m failing to build a working binary) Please provide a snapcraft package/container as now all but one Linux distributions no longer package Sagemath.

Dear Laël, On Sunday, August 25, 2024 at 2:29:44 AM UTC-5 "Dima" wrote: CertIainly Sage does build and run on all sorts of Linux systems. But it's getting more and more bloated to support macOS, and this gets in the way of Linux. It is true that Sage builds on linux, of course. It is false t

[sage-support] Re: MacOS 14.5 on M2 fails to build at gmp

I suggest installing the Sage_macOS app on the university's machine and building from source on a machine which you are allowed to configure. The binary installation is completely self-contained, so will not be affected by anything the IT administrators may have installed. - Marc On Thursday,

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

On Wed, Aug 21, 2024 at 12:35 PM Dima Pasechnik wrote: > what if you have a version mismatch between the toolchain used to build > the shipped binary, > and XCode you installed locally? I'd expect trouble, in particular with > C++. > When I tested the %%cython magic command I was running a beta

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

, users of Sage, building from source is a bad idea. - Marc On Wednesday, August 21, 2024 at 12:03:29 PM UTC-5 Marc Culler wrote: > Using cython within Sage via the %%cython magic command definitely does* > not *require building Sage from source. That magic command works fine in &g

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

Using cython within Sage via the %%cython magic command definitely does* not *require building Sage from source. That magic command works fine in the Sage_macOS binary distribution of SageMath. The cython pip package is included in that binary distribution, because it gets built and installed

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

On Tuesday, August 20, 2024 at 8:22:35 PM UTC-5 Kwankyu Lee wrote: it is not a bad idea for a non-developer user to install sage from source. I disagree. It *is* a bad idea, for so many reasons: * It requires a lot of time and work which is completely unrelated to using Sage. * It will almos

Re: [sage-devel] Proposal: Policy for standard packages from binary wheelsall

tions being IPython and its dependencies. - Marc PS I am also delegating the choice of version for many image processing libraries to the Pillow project, and trusting them to compile the libraries. On Sat, Aug 10, 2024 at 10:40 PM Matthias Koeppe wrote: > On Friday, August 9, 2024 at 7:37:34 AM

Re: [sage-devel] Proposal: Policy for standard packages from binary wheelsall

x27;t know if this scheme will end up being simpler than installing Rust in the Sage build directory (which involves very little more than downloading and running rustup.sh). I hope it will. - Marc On Friday, August 9, 2024 at 8:54:48 AM UTC-5 Nathan Dunfield wrote: > On Thursday, August

Re: [sage-devel] Proposal: Policy for standard packages from binary wheels

I think it would be possible to use a single spkg for all of the additional binary wheels, where the main content of that spkg is a requirements.txt file listing versions and hashes. I also think that would be easier to maintain than many spkg directories, one for each binary wheel. The only

[sage-release] Re: Sage 10.4.rc4 released

I hope that #38360 can also be merged before the release of 10.4, because the current reversion to the naive bounds for the complex interval inverse operator breaks many of the verified computations in the SnapPy test suite, and makes it harder to do

Re: [sage-devel] Re: ask.sagemath.org issues - do we need it?

Thank you Sébastien for standing up for users, for distinguishing between users and developers, and for recognizing that those two groups have different needs. May your Karma increase exponentially! - Marc On Monday, July 1, 2024 at 8:18:36 AM UTC-5 Sébastien Labbé wrote: > I don't visit ask.

[sage-devel] Misleading message from sage

I think it would be good to replace misleading messages in sage by accurate messages. I offer as an example the following message which occurs if I run sage after first running: export DOT_SAGE="~/Library/Application Support/SageMath-10-4"" The message I got was: Your home directory has a

Re: [sage-support] Errors building Sage 10.4.beta6 in Sonoma 14.5

The issue with the --disable-editable has now been fixed by Matthias Koeppe in PR #38304. It was not specific to macOS. - Marc On Thursday, May 30, 2024 at 11:35:07 AM UTC-5 Jon Higa wrote: > > Jon Higa > May 21, 2024, 12:41:48 PM (9 days ago) > to sage-support > > Jon Higa > Mar 25, 2024, 4:

Re: [sage-release] Sage 10.4.beta6 released

I see the same failure od fflas_ffpack on macOS 14.1. - Marc On Monday, May 13, 2024 at 5:53:22 AM UTC-5 david@gmail.com wrote: > I’m unable to compile on macOS 12.7.4 on a fresh clone (and fresh shell). > > The compilation of fflas_ffpack-2.5.0 is failing. See attached log. > > -- You rec

[sage-devel] Re: command not found errors from configure

Oh. And I think the default value should probably be set with: PYTHON_FOR_VENV=/usr/bin/false - Marc On Saturday, May 4, 2024 at 5:54:55 PM UTC-5 Marc Culler wrote: > It is disturbing when one sees "command not found" errors in a configure > script. That is what happens

[sage-devel] command not found errors from configure

It is disturbing when one sees "command not found" errors in a configure script. That is what happens with 10.4.beta5. After tracing it down I found that they are coming from lines like: *if "${PYTHON_FOR_VENV}" -c "import sys; sys.exit(sys.version_info.minor < 11)"* *then :* The variab

[sage-devel] testing optional packages

I don't know what the expectations are for testing optional packages, but in 10.4.beta4 when I run: ./sage -t venv/lib/python3.11/site-packages/symengine I get the exception: NameError: name 'test_sage_conversions' is not defined - Marc -- You received this message because you are subscribed

Re: [sage-devel] Re: help menu in jupyter notebook

Yes, I was only talking about really just running Sage locally. - Marc. On Friday, April 26, 2024 at 7:54:38 PM UTC-5 Nils Bruin wrote: > On Friday 26 April 2024 at 15:44:22 UTC-7 marc@gmail.com wrote: > > I don't see what difference the choice of port makes to a user. It is not > possible

Re: [sage-devel] Re: help menu in jupyter notebook

The jupyter server operates on the loopback interface which has IP address 127.0.0.1 and IP name localhost. The cocoserver uses that same interface. Jupyter tries to get port and if that is busy it hunts for a nearby port that is not in use. The cocoserver uses an arbitrary system-assig

Re: [sage-devel] Re: help menu in jupyter notebook

Yes, I meant MB. Thanks. There are other issues with viewing local documentation files in a browser. On Ubuntu, Chrome and Firefox are packaged as snaps. A snap is not allowed to read a file:// url which is not in the user's home directory. As long as sage is installed in the user's home direc

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

variable is not used in those cases, but I don't know why not. - Marc On Thursday, April 25, 2024 at 11:30:52 PM UTC-5 Marc Culler wrote: > This looks pretty complicated. > > I used XCode 15.0.1 to build the macOS SageMath-10-3 app for Arm and XCode > 13.4 for Intel. I got "

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Fri, Apr 26, 2024 at 8:02 AM Dima Pasechnik wrote: > On Thu, Apr 25, 2024 at 4:36 PM wrote: > > you might also like to know that in 2000 I asked whether we can have > libgap :P > > https://www.gap-system.org/ForumArchive/Pasechni.1/Dmitrii.1/using_GA.1/1.html > It > Thank you! It is a strug

[sage-devel] Re: help menu in jupyter notebook

Another drawback of linking to online documentation is that the online documentation is always for the current release version of Sage, not the Sage that the user happens to be running,. I have a suggestion to improve the situation, which is to do what the Sage_macOS app does. The app provides

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

oying and/or >>>> alarming to someone with no plans to do anything involving compilation of >>>> C >>>> code. >>>> >>>> The calls to xcode-select were added in PR#36599 >>>> <https://github.com/sagemath/sage/pull/36599>

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

s not open the dialog. The error message appears in >>>>> the terminal when running sage in a command line, which is annoying >>>>> and/or >>>>> alarming to someone with no plans to do anything involving compilation of >>>>> C >>>&

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

ker instead of ld when their new version of ld >> was totally broken. This is done by adding -ld_classic to LDFLAGS. >> >> *Note to people who worked on PR #36599* (@jhpalmieri and @mkoeppe): I >> think Apple's new linker is working now, so it is probably no longer >>

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

April 25, 2024 at 9:17:35 AM UTC-5 Marc Culler wrote: > Another amusing quote, this time from the sbrk man page on macOS: > > > The brk and sbrk functions are historical curiosities left over from > > earlier days before the advent of virtual memory management. > > That s

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

systems). - Marc On Thursday, April 25, 2024 at 9:03:30 AM UTC-5 Marc Culler wrote: > On Thursday, April 25, 2024 at 8:28:48 AM UTC-5 Dima Pasechnik wrote: > > Essential components of sagelib such as GAP, Singular, don't run on > native Windows > > > I was amused to find the

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Thursday, April 25, 2024 at 8:28:48 AM UTC-5 Dima Pasechnik wrote: Essential components of sagelib such as GAP, Singular, don't run on native Windows I was amused to find the following statement on the GAP forum from 2005: > W

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Thu, Apr 25, 2024 at 8:28 AM Dima Pasechnik wrote: > On Thu, Apr 25, 2024 at 1:28 PM Nathan Dunfield > wrote: > > > > On Wednesday, April 24, 2024 at 10:14:09 PM UTC-5 Matthias Koeppe wrote: > > > > Yes, native Windows would clearly be a very important target. > > > > > > As a data point, dow

[sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

to LDFLAGS. *Note to people who worked on PR #36599* (@jhpalmieri and @mkoeppe): I think Apple's new linker is working now, so it is probably no longer necessary and not a good idea to force use of ld_classic. - Marc On Tuesday, April 23, 2024 at 10:45:54 PM UTC-5 Marc Culler wrote: Tha

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Wed, Apr 24, 2024 at 2:26 PM Oscar Benjamin wrote: > Presumably though a hypothetical person who wants CyPari2 but not all of > Sage can already just use CyPari so that person is already well served. > That hypothetical person could also use CyPari2 if they didn't care about memory leaks and

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

e, 23 Apr 2024 at 15:27, Marc Culler wrote: > > > > The projects that will really benefit from modularization will be those > that provide their own limited mathematical context. Developers of such > projects will be able to choose which parts of Sage are relevant to their > s

Re: [sage-support] Jupyter Notebook crashes, then get connection refused error and cannot relaunch on mac

ocalc and it got her able to submit her assignment tonight, at > least! > > Thank you again!!! > > On Tuesday, April 23, 2024 at 6:58:30 PM UTC-4 Marc Culler wrote: > >> The 10.3 version of the app uses the standard location for Jupyter >> runtime files: ~/Library/Jupyt

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

On Wednesday, April 24, 2024 at 8:05:15 AM UTC-5 Dima Pasechnik wrote: running Cython in sage prompt or in Sage Jupyter notebook has nothing to do with -i option. I realize that. But it looked to me like those variables are being set in the sage-env script *primarily* to support sage -i. Per

Re: [sage-devel] Question: why does /usr/bin/gcc get called during Sage startup?

On Tuesday, April 23, 2024 at 11:17:49 PM UTC-5 Marc Culler wrote: I wonder if the Sage community would be willing to reconsider the idea of having one entry point for every function provided by SageMath, I won't speak for the community, but I reconsidered this and I decided that it wou

Re: [sage-devel] Question: why does /usr/bin/gcc get called during Sage startup?

On Tuesday, April 23, 2024 at 8:58:58 PM UTC-5 Dima Pasechnik wrot It's not quite correct to say that a C, or other, compiler is not required to run Sage. Sage allows you to define, build, load, and run Cython extensions without leaving Sage, thus, it needs to call a compiler after cythonisati

[sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

ub.com/sagemath/sage/commit/69213d74ead4e93687cf61f214b0d96dd3f9885a > > Maybe you can workaround this by setting AS=as and LD=ld in > sage-env-config. > > HTH, > Gonzalo > > > On Tuesday, April 23, 2024 at 3:48:18 PM UTC-3 Marc Culler wrote: > >> I discover

Re: [sage-support] Jupyter Notebook crashes, then get connection refused error and cannot relaunch on mac

The 10.3 version of the app uses the standard location for Jupyter runtime files: ~/Library/Jupyter - Marc On Tuesday, April 23, 2024 at 5:08:43 PM UTC-5 Dima Pasechnik wrote: > PS. From what I see on https://github.com/3-manifolds/Sage_macOS/issues/28 > I gather you might try to remove (or bet

[sage-support] Re: Jupyter Notebook crashes, then get connection refused error and cannot relaunch on mac

Please ask her to try removing the two directories ~/Library/Jupyter and ~/.sage: rm -rf ~/Library/Jupyter rm -rf ~/.sage If that does not fix it, please open an issue at our github site: https://github.com/3-manifolds/Sage_macOS/issues We will work through it with you and figure out what is goin

[sage-devel] Question: why does /usr/bin/gcc get called during Sage startup?

I discovered, by installing the Sage_macOS app on a pristine macOS system, that somehow, somewhere, in Sage's startup sequence there is a call to gcc. This is true whether Sage is being started from a command line or a notebook. On such a macOS system /usr/bin/gcc exists, but calling it causes

[sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Tuesday, April 23, 2024 at 4:07:37 AM UTC-5 Tobias wrote: In reply to the comment ( https://github.com/sagemath/sage/pull/36676#issuecomment-2067371677) once the modularization is in place, it will impose wide-ranging constraints on what functions from other modules you are able to use. C

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Sunday, April 21, 2024 at 9:42:24 AM UTC-5 Nathan Dunfield wrote: For the statements in this thread, I don't see any contradictions about the definition of the "normal Python way of doing things". My understanding of that term is to post *self-contained* binary wheels to PyPI for all suppo

Re: [sage-devel] Re: VOTE: Revert merged PR with unreviewed dependencies

On Thursday, April 18, 2024 at 12:47:36 PM UTC-5 David Roe wrote: On Thu, Apr 18, 2024 at 1:43 PM Matthias Koeppe wrote: I will first note that the title of this post is misleading. Everything that was merged has been reviewed -- as noted, many months ago. I agree that everything was reviewed

[sage-devel] Re: Proposal (redo): Make python_build (and its dependency pyproject_hooks) a standard package

+1 on making python_build a standard package. - Marc On Tuesday, April 9, 2024 at 10:44:36 PM UTC-5 Matthias Koeppe wrote: > We added python_build as an optional "pip" package (see > https://deploy-livedoc--sagemath.netlify.app/html/en/developer/packaging#package-types > for > the terminology

Re: [sage-devel] Re: Proposal (redo): Make python_build (and its dependency pyproject_hooks) a standard package

On Monday, April 15, 2024 at 7:03:27 AM UTC-5 Michael Orlitzky wrote: The solution for users is pretty simple. You should be able to install a sage that works and will remain working with one command using homebrew, conda, guix, etc. The reason you can't is ... I would just mention that macOS

[sage-support] Re: Is there a way to use Sage's Jupyter outside the sage shell ?

If I understand your question correctly, the answer is yes. All that you need to do is to copy the sage kernel spec directory into /usr/local/share/jupyter/kernels. If you have installed jupyter in a python venv then the jupyter command in the venv will always check for kernels in that direct

[sage-support] Re: Successful plots (without notebook) on Windows?

Evidently it is possible to install Firefox on Ubuntu 22.04 from the Mozilla PPA instead of using the snap. https://askubuntu.com/questions/1399383/how-to-install-firefox-as-a-traditional-deb-package-without-snap-in-ubuntu-22 - Marc On Tuesday, April 2, 2024 at 7:14:47 AM UTC-5 Marc Culler

[sage-support] Re: Successful plots (without notebook) on Windows?

Actually the firefox snap can access files on the local disk, but only if they are in the user's home directory. It cannot access files in /tmp. Does the plot viewer use the ubuntu system's /tmp? - Marc On Monday, April 1, 2024 at 2:31:44 PM UTC-5 Emmanuel Charpentier wrote: > I just had to

Re: [sage-devel] Mysterious .sage behavior

t; > > I must say I don't know what kind of problems these versioned names are > meant to solve. > > > > >On 31 March 2024 15:23:24 CEST, Marc Culler <https://groups.google.com/>> wrote : > > >if [ -z "$IPYTHONDIR" ]; then > > # W

[sage-devel] Mysterious .sage behavior

This is a follow-up to a user's query in a Sage_macOS issue. The current sage-env script contains the excerpt below. It seems pretty confusing that Sage would create a directory named .sage/ipython-5.0.0 when Sage is shipping IPython 8.18.1. What would be wrong with calling the directory .s

Re: [sage-devel] Re: xz/liblzma has been compromised

n general, just ssh on certain linux distros. I would NOT suggest that "for your security" Sage should stop supporting linux. - Marc On Saturday, March 30, 2024 at 9:08:45 AM UTC-5 Marc Culler wrote: > > Potentially, any tarfile we host may contain an exploit. > > Poten

Re: [sage-devel] Re: xz/liblzma has been compromised

> Potentially, any tarfile we host may contain an exploit. Potentially, any file may contain an exploit. This hack specifically targeted ssh. When used by ssh to verify keys, the hacked liblzma would validate certain invalid keys, allowing a "back door" for a particular bad actor to login to

[sage-devel] Downloads

In case anyone is interested ... The SageMath 10.3 app for macOS has been downloaded 684 times since it was released on Sunday. The SageMath 10.2 app was downloaded 8685 times since its release about 4 months ago. For both versions, Arm downloads outnumber Intel by about 2 to 1. Source: https

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

rt is writing? Is there a reason why he is writing a kernel when one already exists? Obviously I have no idea what I am talking about and am publicly revealing my ignorance. - Marc On Friday, March 22, 2024 at 12:29:56 PM UTC-5 Marc Culler wrote: > I wasn't advocating anyth

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

I wasn't advocating anything like that. Certainly I don't think that pari-jupyter should be "killed". I am assuming that pari-jupyter is or will be a package that can be installed with pip. And I am also assuming that it has no direct interaction with Sage. Are those assumptions wrong? If

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

If one has Sage installed with the pari-jupyter package installed in Sage and one wants to run pari-jupyter, what does one do? Is it equivalent to just installing pari-jupyter with pip and starting it up in the normal way? Does pari-jupyter use any components of Sage? If the answers are "yes

[sage-devel] Re: Vote: changes to Sage's Code of Conduct

+1 On Thursday, March 21, 2024 at 11:51:40 AM UTC-5 John H Palmieri wrote: > Dear Sage community, > > As announced at > https://groups.google.com/g/sage-devel/c/Xf6dbPLmKPY/m/p88auKlBAwAJ, I > propose some changes to the Code of Conduct. Those changes have been > discussed and modified based o

[sage-devel] Re: Jupyter Lab Sage menu

It would also be a good idea to open the javascript console and see if there are errors being reported around the time when the menu disappears. - Marc On Wednesday, March 6, 2024 at 8:20:00 PM UTC-6 Marc Culler wrote: > Viviane, > > If you do a shift-reload (or whatever makes you

[sage-devel] Re: Jupyter Lab Sage menu

Viviane, If you do a shift-reload (or whatever makes your browser clear its cache) does that make the menu come back? - Marc On Wednesday, March 6, 2024 at 8:11:45 AM UTC-6 Viviane Pons wrote: > Dear all, > > I am working on a conda distribution of sage with jupyter lab. My conda > environnem

Re: [sage-devel] Re: VOTE: use "blocker" label only for PRs; use "critical" label for Issues

I see. Thanks. - Marc On Wed, Feb 28, 2024 at 6:49 PM Kwankyu Lee wrote: > > > On Thursday, February 29, 2024 at 8:35:24 AM UTC+9 Marc Culler wrote: > > I have a proposal: It should be forbidden to call for a vote on a proposal > before there has been a discussion. > &g

[sage-devel] Re: VOTE: use "blocker" label only for PRs; use "critical" label for Issues

I have a proposal: It should be forbidden to call for a vote on a proposal before there has been a discussion. Without a chair, it would be impossible for this group to follow Robert's Rules of Order, even approximately. But the basic process should still be the same. The rules are designed to

[sage-devel] Re: Question about the sage venv.

On Thursday, December 7, 2023 at 5:04:25 PM UTC-6 Matthias Koeppe wrote: Sure, but that would preclude using the same SAGE_LOCAL for an installation with venv over a system python and an installation of SPKG python. I don't understand. The bash script sage/venv/bin/sage calls sage/venv/bin/

[sage-devel] Re: Question about the sage venv.

On Thursday, December 7, 2023 at 2:31:24 PM UTC-6 Matthias Koeppe wrote: > The venv would always contain a pyvenv.cfg file. Could you explain why this matters for what you have in mind? It is not essential. It is just cleaner and more uniform. I think it is misleading to have something calle

[sage-devel] Re: Question about the sage venv.

ptions because they already set the rpaths, to a subdirectory of the python package named .dylibs. - Marc On Thursday, December 7, 2023 at 12:17:00 PM UTC-6 Matthias Koeppe wrote: > On Thursday, December 7, 2023 at 10:04:14 AM UTC-8 Marc Culler wrote: > > I have a very narrow techical

[sage-devel] Question about the sage venv.

I have a very narrow techical question. I am hoping for a narrow technical answer, preferably from someone who was involved in designing the Sage venv. QUESTION: Why doesn't the Sage venv contain a pyvenv.cfg file? When you read PEP 405 you learn that the py

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

I should also have mentioned that macOS is an example of a system which does not come with libjpeg. On Fri, Nov 17, 2023 at 12:53 PM Marc Culler wrote: > No, I meant both "normal" and "standard". I am sure I will master this > terminology sooner or later. > > On

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

No, I meant both "normal" and "standard". I am sure I will master this terminology sooner or later. On Friday, November 17, 2023 at 12:51:48 PM UTC-6 Marc Culler wrote: > I meant "normal" when I said "standard". > > On Friday, November 17, 20

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

I meant "normal" when I said "standard". On Friday, November 17, 2023 at 12:49:18 PM UTC-6 Marc Culler wrote: > I expect to receive lots of flak for saying this, but I support making > libjpeg be a standard spkg using the source code from > https://libjpeg.s

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

I expect to receive lots of flak for saying this, but I support making libjpeg be a standard spkg using the source code from https://libjpeg.sourceforge.net. I just built version jpeg-9e on Ubuntu 18.04 and macOS 10.13. The standard ./configure ; make install method works flawlessly - not eve

Re: [sage-devel] Cython errors when building p_group_cohomology

Thank you, Edgar! That worked. - Marc On Wednesday, November 15, 2023 at 7:15:45 PM UTC-6 Edgar Costa wrote: > Marc, you should try something like this: > https://github.com/edgarcosta/pyfib/commit/f30cd702f5b8610a284b1b1f425ef22b2a2a11fa > > On Wed, Nov 15, 2023 at 6:49 PM Marc C

[sage-devel] Cython errors when building p_group_cohomology

I am not able to build the optional package p_group_cohomology in 10.2.rc2 due to cython errors. The first error looks like: [p_group_cohomology-3.3.3.p1] Error compiling Cython file: [p_group_cohomology-3.3.3.p1] --- - [p_group_cohomol

Re: [sage-devel] Symengine package fails to build in 10.2rc2

I see your unanswered message "ping" on issue #456 from 5 days ago. But in the Releases section I see that v0.11.0 was released 2 days ago. - Marc On Tuesday, November 14, 2023 at 11:50:55 AM UTC-6 Dima Pasechnik wrote: > On Tue, Nov 14, 2023 at 5:18 PM Marc Culler wrote

Re: [sage-devel] Re: Question about make dependencies

sage/installed. > > On Tuesday, November 14, 2023 at 9:37:09 AM UTC-8 Marc Culler wrote: > >> For me, one of the most frustrating parts of building sage is that, >> whenever a build fails, the make system decides that gmp is out of date and >> hence I have to wa

Re: [sage-devel] Re: Question about make dependencies

I was hesitant to send that message because I didn't want to have to go through this again. On Tue, Nov 14, 2023 at 11:58 AM Dima Pasechnik wrote: > > Does ./configure say why the system copy is unsuitable? > There is no system copy. I imagine it might be an artifact of the design of Sage on M

[sage-devel] Re: Question about make dependencies

Tuesday, November 14, 2023 at 11:37:09 AM UTC-6 Marc Culler wrote: > For me, one of the most frustrating parts of building sage is that, > whenever a build fails, the make system decides that gmp is out of date and > hence I have to wait for it to recompile gmp and all of its dependencies. &g

[sage-devel] Question about make dependencies

For me, one of the most frustrating parts of building sage is that, whenever a build fails, the make system decides that gmp is out of date and hence I have to wait for it to recompile gmp and all of its dependencies. Is this intentional? Does anyone know why it happens? Is it avoidable? Or a

[sage-devel] Symengine package fails to build in 10.2rc2

The symengine package has apparently not been updated to be compatible with cython 3. This is what I see in the log (full log attached): performance hint: /private/var/tmp/sage-10.2-current/local/var/lib/sage/venv-python3.11.1/var/tmp/sage/build/symengine_py-0.10.0/src/symengine/lib/symengine

Re: Build failure on macOS Sonoma 14.0 beta

at 2:50 AM Hans Åberg wrote: > > > On 20 Sep 2023, at 22:45, Marc Culler wrote: > > > > I learned by reading the release notes for XCode 15 that Apple rewrote > the linker for XCode 15. They also made the old linker available by using > -ld64 as a linker option. >

Re: Build failure on macOS Sonoma 14.0 beta

This message is just to make sure that the situation is clear.: 1. Building gmp with -enable-fat fails with the XCode 15 compiler and the new XCode 15 linker. The error reported by the linker is impossible. It is reporting an out of range branch instruction in a function which is written in asse

Re: Build failure on macOS Sonoma 14.0 beta

On Wed, Sep 20, 2023 at 3:44 PM Torbjörn Granlund wrote: > Marc Culler writes: > > It is not possible for the GMP maintainers to analyse the effects of > various options which we do not know about. As I wrote before, please > just use --enable-fat. > If you read my earlier

Re: Build failure on macOS Sonoma 14.0 beta

mmands, even in functions which are written in assembly language and which contain no branch commands whatsoever. I hope that the GMP project will try and succeed at getting Apple to fix this bug. (I have given up trying to get Apple to fix bugs. They just ignore me.) - Marc On Wed, Sep 20, 202

Re: Build failure on macOS Sonoma 14.0 beta

n Wed, Sep 20, 2023 at 12:01 PM Marc Culler wrote: > One more data point -- I do get a successful build if I omit the > --enable-fat option. That means no CFLAGS and configuring with: > > $ ./configure --with-pic --prefix=XX > > In this case the compiler options incl

Re: Build failure on macOS Sonoma 14.0 beta

gt; On Wed, Sep 20, 2023 at 11:25 AM Hans Åberg wrote: > >> >> >> > On 20 Sep 2023, at 16:36, Marc Culler wrote: >> > >> > …macOS Sonoma beta… >> … >> > …using: "Apple clang version 15.0.0 >> > (

Re: Build failure on macOS Sonoma 14.0 beta

> > On 20 Sep 2023, at 16:36, Marc Culler wrote: > > > > …macOS Sonoma beta… > … > > …using: "Apple clang version 15.0.0 > > (clang-1500.0.40.1)" > > The same compiler version is now available on MacOS 13, together with > Xcode 15. > > _

Re: Build failure on macOS Sonoma 14.0 beta

I get exactly the same error with: export CFLAGS="-arch x86_64 -mmacosx-version-min=10.9" I will also try removing those options. - Marc On Wed, Sep 20, 2023 at 10:48 AM Marc Culler wrote: > Thanks for replying! > > The reason for the options "-mno-avx -mno-avx2

  1   2   3   >