mented in
src/sage/rings/finite_rings/element_base.pyx rather than making a
new file such as src/sage/categories/finite_field_elements.pyx and
moving it there?
4. Any other advice/warnings before I look into this further?
--
Vincent Macri (he/him)
--
You received this message because you are subs
Sage asking
Singular to do an unnecessarily complicated computation?
--
Vincent Macri (he/him)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+un
I think just before configure, but I didn't do any testing to verify
that's the only place you need it. I just ran it once then did all the
steps to build from source without closing the terminal.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
As a workaround until GCC 15 is supported, this worked for me:
export CC=$(which gcc-14)
export CPP=$(which cpp-14)
export CXX=$(which g++-14)
export FC=$(which gfortran-14)
these can be installed via the Fedora packages gcc14, gcc14-c++, and
gcc14-gfortran.
Vincent Macri (He/Him)
--
You
open PRs for multiple iterations of the same thing.
Vincent Macri (He/Him)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com
t because it's unlikely to get picked up. Then a
search for the "unresponsive" tag on open PRs would return a list of
abandoned PRs that add/fix something important, and a search for the
"unresponsive" tag on closed PRs would return a list of abandoned PRs
that whi
should start after the PR is tagged with "changes requested". I don't want to
punish contributions where it's our fault for not reviewing them in a timely
manner. Basically we should only be closing PRs where we reviewed them, changes
were requested, and changes were not made
e the PR ideally, if GitHub permissions
allow which I think they do) as soon as they start working on it again.
Ideally any closings of PRs in this way would be accompanied by a link to the
developer guide explaining that all the dev needs to do to reopen the PR is
continue working on it.
V
appropriate) then the PR may be closed
with the tag "r: no response". The PR may be reopened at a later date if
the author responds.
--
Vincent Macri (He/Him)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
I can reproduce in Sage 10.4, and I found some additional weird behaviour.
Doing p // p a second time gives 0.
Doing p / p causes a segmentation fault and crashes Sage.
Vincent Macri (He/Him)
On 2024-11-05 7:50 a.m., 'Martin R' via sage-devel wrote:
[â–³EXTERNAL]
I just stu
10 matches
Mail list logo
