This was the only other problem package besides gfortran. The issue seems
to be that one of the e_antic files includes a boost header which triggers
a warning about assigning out-of-range values to an enum. That warning was
promoted to an error in clang 16. Boost actually already has a
worka
We are observing disadvantage of a long thread.
At some point, other participants forget the context in which a participant
write a comment.
Dima and I were talking about a fictional sagemath-number-theory
distribution package.
I imagined a user/developer who installed sagemath-number-theory, a
On Thu, Oct 3, 2024 at 11:15 PM Marc Culler wrote:
>
> According to https://formulae.brew.sh/formula/gcc, the homebrew gcc supports
> Sequoia on Arm but not on Intel yet. The patch referenced in the ticket
> appears to work. It is not entirely trivial to apply that patch, however,
> because i
On Thu, Oct 3, 2024 at 11:01 PM Matthias Koeppe
wrote:
>
> On Thursday, October 3, 2024 at 1:18:44 PM UTC-7 Dima Pasechnik wrote:
>
> Why is it quicker than running ./sage -t src/sage/lfunctions src/sage/rings/
> (perhaps few other should be added) on a full sagelib install?
>
>
> You are missing
According to https://formulae.brew.sh/formula/gcc, the homebrew gcc
supports Sequoia on Arm but not on Intel yet. The patch referenced in the
ticket appears to work. It is not entirely trivial to apply that patch,
however, because it changes some of the same files as the existing patches.
- M
On Thursday, October 3, 2024 at 1:18:44 PM UTC-7 Dima Pasechnik wrote:
Why is it quicker than running ./sage -t src/sage/lfunctions
src/sage/rings/
(perhaps few other should be added) on a full sagelib install?
You are missing the point.
The main point of testing a modularized distribution i
On Thursday, October 3, 2024 at 1:16:12 PM UTC-7 Dima Pasechnik wrote:
what's so special about an updated sagemath-categories distribution so that
you absolutely must base the brial update on them?
Distributions are just wrappers for code, after all.
"Wrappers"? No.
Instead of using -distri
Hi Marc,
does Homebrew's gfortran work for you?
Dima
On 3 October 2024 19:02:49 BST, Marc Culler wrote:
>... as I learned the hard way, after updating my build system to macOS 15.
>
>The cause is this bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116809
>for which a patch exists.
>
>- Marc
>
On Thursday, October 3, 2024 at 2:47:20 AM UTC-7 axio...@yahoo.de wrote:
> There's a simple and important principle of Open Source: Trust those who
are doing the work.
I cannot quite pin it down,
I think it's worth to engage in a bit more of reflection.
but this sounds fishy to me. Maybe bec
On Thursday, October 3, 2024 at 5:26:09 AM UTC-7 axio...@yahoo.de wrote:
It seems to me that one of the main innovations of sage (among other CAS)
was to make writing doctests really easy *and* keep them together with the
code *and* make testing them *while developing* very straightforward.
Ye
On Thursday, October 3, 2024 at 6:11:48 AM UTC-7 Kwankyu Lee wrote:
It seems to me that one of the main innovations of sage (among other CAS)
was to make writing doctests really easy *and* keep them together with the
code *and* make testing them *while developing* very straightforward.
True!
On Thu, Oct 3, 2024 at 2:11 PM Kwankyu Lee wrote:
>
> It seems to me that one of the main innovations of sage (among other CAS) was
> to make writing doctests really easy *and* keep them together with the code
> *and* make testing them *while developing* very straightforward.
>
>
> True!
>
>
> T
On 3 October 2024 11:30:38 BST, Kwankyu Lee wrote:
>I can imagine this:
>
>sagemath-number-theory won't have the coding theory portion of the sage
>library. Hence developers for sagemath-number-theory could test their
>favorite distribution package quicker.
However, they'd need to test all p
All: We elected a Code of Conduct Committee earlier this year.
The committee, ostensibly, is following the manual at
https://github.com/sagemath/sage/blob/develop/CODE_OF_CONDUCT_COMMITTEE.md
I have severe concerns, at the core of which are:
1. the complete and willful refusal by the committee to
On Wednesday, October 2, 2024 at 2:48:10 PM UTC-7 oscar.j@gmail.com
wrote:
In my mind it could make sense for there to be a sagemath-minimal
package which from a user perspective represents a "minimal
installation of Sage" in comparison to say a package called
sagemath-full. The implicatio
On Wednesday, October 2, 2024 at 1:08:37 AM UTC-7 axio...@yahoo.de wrote:
the description given by Matthias, reproduced below, makes no sense to me
at all.
> The other contents of *sagemath-categories* are provided in similar
spirit. For example, there are the Function objects from sage.functi
And I have repeatedly explained that no matter how brial and
sagemath-categories are related, one can perfectly either
have a completely independent PR for brial, or
base the brial one on a PR that deals with updates to sagemath-whatever
distribution(s).
If X depends on Y, make a PR for Y, an
... as I learned the hard way, after updating my build system to macOS 15.
The cause is this bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116809
for which a patch exists.
- Marc
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
I am already using ./configure --enable-download-from-upstream-url
Deleting the tar.gz from upstream does not fix the issue.
Now trying make after make distclean.
Thank you for yours ideas.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsub
I think I experienced the same phenomenon (getting stuck) once before.
Later it disappeared perhaps after "make distclean" or something.
I don't know why.
You may try again after removing all files in
/home/slabbe/GitBox/sage/upstream/
--
You received this message because you are subscribed
On Thu, 2024-10-03 at 06:13 -0700, Sébastien Labbé wrote:
> After a long period using an old version of Sage, I tried to update my
> version of Sage yesterday to the latest development version, but the `make`
> gets stuck while trying to download cython and maxima. See excerpt of log
> below. I
After a long period using an old version of Sage, I tried to update my
version of Sage yesterday to the latest development version, but the `make`
gets stuck while trying to download cython and maxima. See excerpt of log
below. I have never seen such a problem before, so I post my issue here.
A
It seems to me that one of the main innovations of sage (among other CAS)
was to make writing doctests really easy *and* keep them together with the
code *and* make testing them *while developing* very straightforward.
True!
The final of these three points would be broken *by encouraging d
I think that this would be a major step backwards. Currently, if I make
changes in one part of sage (right now: polynomials), I am sometimes a bit
surprised where I am breaking code (in the case at hand: braid groups). Of
course, this is rarely surprising once I look at the code, but I don't h
I can imagine this:
sagemath-number-theory won't have the coding theory portion of the sage
library. Hence developers for sagemath-number-theory could test their
favorite distribution package quicker.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" gr
> It may provide a "sage" with elementary mathematics that all advanced
mathematics depend
There is no boundary between "elementary" and "advanced" mathematics.
Also, there is no boundary between "discrete mathematics" and "complex
analysis" or "numerics".
> There's a simple and important pri
26 matches
Mail list logo
