Hi Michael,
I've created sage-giac <https://github.com/sagemath/sage-giac> and added
you as an admin. Let me know if you need anything else. Thanks for
working on this!
David
On Thu, Feb 13, 2025 at 12:39 PM Michael Orlitzky
wrote:
> Hi, this is a friendly reminder that I am
The first thing I would try would be to use `make build` rather than sage
-br. The error you're seeing is related to missing flint, and sage -br
only helps with changes to Cython code within the Sage library, not
packages that Sage depends on.
David
On Sun, Feb 2, 2025 at 9:11 AM Pawani Ag
10:55 GMT-06:00, David Einstein
> wrote:
>
>> Macosx 15.1.1 M1 laptop
>>
>> I probably messed something up with my python setup but I cannot figure
>> out what.
>>
>> It is looking for python 3.11 which I have removed.
>>
>> Thank you fo
Macosx 15.1.1 M1 laptop
I probably messed something up with my python setup but I cannot figure out
what.
It is looking for python 3.11 which I have removed.
Thank you for any assistance. This is almost certainly my fault, but I'm
not sure how to fix it.
--
You received this message beca
On Wed, Jan 1, 2025 at 3:18 AM Georgi Guninski wrote:
> Happy New smooth square year 3^4 * 5^2!
>
sage: (20 + 25)*(20 + 25)
2025
Happy New Year to you too!
> Let happiness be with you!
>
> --
> joro
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-de
se
> sage: isinstance(c, FieldElement)
> True
>
It's not ideal, but OrderElement_quadratic inherits from
NumberFieldElement_quadratic because there's a lot of common functionality,
which eventually inherits from FieldElement. It's basically a consequence
of Cython not suppor
Yep, that should work. To find the right import statements, you can do
sage: import_statements(libgap)
from sage.libs.gap.libgap import libgap
David
On Thu, Dec 5, 2024 at 5:37 PM Jackson Walters
wrote:
> Perhaps I can just use
>
> from sage.libs.gap.libgap import libgap
>
&
What is your github username?
David
On Tue, Dec 3, 2024 at 2:56 PM Jackson Walters
wrote:
> It seems I am not able to add comments to issues or PRs on GitHub. Is this
> a GitHub issue or something specifically with Sage?
>
> --
> You received this message because you are su
Here's a functional link to join the group:
https://groups.google.com/g/sage-government. Sorry for the broken link!
David
On Fri, Nov 29, 2024 at 2:09 PM David Roe wrote:
> Dear Sage developers,
>
> One of the common themes that came out of the Community Survey
> <https:/
vote. The
creation of this list does not change anything about how decisions are made
for the project.
I plan to send some initial emails to the new list in about a week, though
the history in the group will be visible if you don't end up joining until
later.
David
--
You received this mes
Thanks for the suggestion. Is there a PR when cypari2 started using
pointers on the PARI stack? I'm just trying to figure out how to make such
a change.
David
On Thu, Nov 14, 2024 at 2:44 AM Vincent Delecroix <20100.delecr...@gmail.com>
wrote:
> Hi David,
>
> I think that
/databases-of-elliptic-curves-ordered-by-height-and-distributions-of-selmer-groups-and-ranks/E245E7A5300FEA32E48E89A71C746930>
elliptic curve databases to the LMFDB, since the files they contain are too
large to host with a non-threaded 30 second timeout.
Help resolving the bug or suggesting worka
On 22:35 Mon 07 Oct 2024, Dima Pasechnik wrote:
Indeed, Flint is dual licensed under GPL and LGPL - so why don't we
re-license sagelib under LGPL then.
...[SNIP]...
I don't know whether it'd need a lot of individual approvals, but
GPL->LGPL is certainly done quite often. E.g. GMP was relicenced u
not solve the problem, I believe.
>
If you have suggestions, I encourage you to reach out to us on
sage-cond...@googlegroups.com.
David
> Doris
>
> > On 7. Sep 2024, at 09:36, Dima Pasechnik wrote:
> >
> >
> >
> > On 6 September 2024 22:29:35 BST, Matthi
n the CoC should
be involved anyway.
If there is a sense that extreme misconduct has occurred then any developer
can ask the CoCC to block them.
However, if a developer who is not on the CoCC blocks a user then the CoCC
should block that developer's github privileges for a small length of time,
of the contributors file
<https://github.com/sagemath/website/blob/master/conf/contributors.xml>.
David
--
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-d
sage-edu: wdjoy...@gmail.com, kcris...@gmail.com
On Fri, Aug 23, 2024 at 6:35 AM John Cremona wrote:
> sage-nt: John Cremona
> sage-algebra: David Kohel, Harald Schilly, Mike Hansen, William Stein
> Sage Days 6: John Cremona, William Stein
> sagedays35, sage-flint-days: Bill Hart
3Aowner> of the
sage-devel group is the same as the current membership of the Code of
Conduct Committee: myself, Julian Rüth, John Palmieri, Nils Bruin, Viviane
Pons and JP Labbe.
David
> Thanks!
> Matthias
>
> --
> You received this message because you are subscribed to the
others, which is why we asked for discussion rather than a vote.
David
On Thu, Aug 22, 2024 at 2:32 PM Matthias Koeppe
wrote:
> On Thursday, August 22, 2024 at 11:08:48 AM UTC-7 John H Palmieri wrote:
>
> This message comes from the Code of Conduct Committee, in response to a
> quest
e not.
Thanks,
David.
On Friday, July 12, 2024 at 6:31:54 PM UTC+2 enriqu...@gmail.com wrote:
> Thanks. Is it documented somewhere?
>
> El viernes, 12 de julio de 2024 a las 15:01:19 UTC+2, Dima Pasechnik
> escribió:
>
>> Yes, this is a recent change.
>> It's time to ret
nd did
not just use the public API. I was not involved in that aspect of the
migration, so I'll let others speak to exactly what was involved.
David
On Thu, Jul 11, 2024 at 12:50 PM Oscar Benjamin
wrote:
> Hi all,
>
> There have been some discussions and tentative attempts to m
Could you explain more why you want to italicize something inside a literal
block?
David
On Sat, Jun 22, 2024 at 10:39 PM Janmenjaya Panda <
janmenjaya.panda...@gmail.com> wrote:
> Could someone please mention, how to italicize a particular term inside a
> literal block?
> Use of
x + 1)
sage: Kquo(x^2)
-xbar - 1
David
On Mon, Jun 17, 2024 at 10:05 AM Georgi Guninski
wrote:
> This hurts me, so workaround is welcome.
>
>
> n=13*random_prime(2**20);Kyx.=Integers(n)[];f=x^2+x+1;Kquo.=Kyx.quotient(f);Kquo
> #pass
>
>
> n=13*random_prime(2**50);Kyx.
made in awareness of the limitations
> of "pip" packages.
>
I see the policy you refer to here
<https://doc.sagemath.org/html/en/developer/packaging.html>, but what
limitations of pip packages prevent them from being standard?
David
> --
> You received this message bec
n in Sage ? No, obviously not.
> Are you going to demote pytest back to optional,
> and throw away work done on using pytest more? No. Have another fight
> over the ways Sage should be packaged? Yes, sure.
>
I don't find it plausible that a package whose purpose is to test Python
cod
R.
I personally think the three options are fine.
Le mercredi 15 mai 2024 à 02:46:52 UTC-4, Dima Pasechnik a écrit :
>
>
> On 15 May 2024 02:14:05 BST, David Roe wrote:
> >On Tue, May 14, 2024 at 9:13 PM Dima Pasechnik wrote:
> >
> >>
> >>
> >> On 1
such permissions are automatic for the members of triage team.
>
That's incorrect. Triage is a lower permission level than Write; see here
<https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organ
For another data point, on an ubuntu laptop:
sage: time [f(0.1*i) for i in range(1,10)]
CPU times: user 136 ms, sys: 0 ns, total: 136 ms
Wall time: 99.1 ms
[1, 1, 1, 1, 1, 1, 1, 1, 1]
sage: time f(0.1)
CPU times: user 13.6 ms, sys: 0 ns, total: 13.6 ms
Wall time: 13.5 ms
1
sage: version()
'SageMat
cope you want to support in terms of
degree (and, to a lesser extent, size of coefficients), as well as whether
you want to allow non-monic polynomials.
Good luck!
David
After some research I have the impression that there are some proofs of
> concept, but there is nothing actively developed?
The vote was 8-4. I'm setting the PR back to positive review.
David
On Sat, Apr 20, 2024 at 5:04 AM Volker Braun wrote:
> It was merged because it was positively reviewed.
>
> Neither I nor the merge script reads every ticket description and looks
> through the text whether
On Thu, Apr 18, 2024 at 1:51 PM Matthias Koeppe
wrote:
> David, none of this explains the misleading use of the word "unreviewed".
I believe that it does. If there was confusion, hopefully this exchange
can help clarify it for others.
David
> On Thursday, April 18, 2024 at 1
efinition, #36951 and #36676 did not have
positive review at the time that #36964 was merged.
David
On Thursday, April 18, 2024 at 8:54:26 AM UTC-7 David Roe wrote:
>
>> Hi all,
>> Sage has had a review process for over 15 years, but a combination of
>> recent changes has l
On Thu, Apr 18, 2024 at 11:54 AM David Roe wrote:
>
> Hi all,
> Sage has had a review process for over 15 years, but a combination of recent
> changes has led to the merging of a PR into sage-10.4.beta3 of a change
> (#36964) that I believe should not (yet) have been merge
you have broader changes to raise about sage
development.
- Broader discussion of technical differences or philosophy: start a new
thread.
I suggest a deadline of Sunday April 21 at 23:59 US/Pacific for this vote.
Finally, many of these PRs have been plagued by conflict and inappropriate
language
disputed.
>>
>> It floods my inbox and makes my heart sink.
>>
>
> Well, on the latest disputed PR
> https://github.com/sagemath/sage/pull/37796 I proposed
> to stop with this all and go back to getting the PRs approved by consensus.
>
> Should we call an urgent gener
community is currently falling short, even if you do not
have specific solutions.
The Sage Code of Conduct Committee
David Roe
J-P Labbe
John Palmieri
Julian Rüth
Nils Bruin
Viviane Pons
On Fri, Apr 12, 2024 at 4:11 PM Matthias Koeppe
wrote:
> Trigger Warning: In this post, I will discuss top
/pkgs/sage_docbuild-10.4.beta3.time: No such
file or directory
make[2]: Leaving directory '/home/davidayotte/sage/build/make'
Sage build/upgrade complete!
cat: logs/install.time: No such file or directory
OS: Ubuntu 22.04.4 LTS via WSL2 on Windows 11
Best,
David A.
--
You received this mess
-devel. We are sad in taking this step, and are
continuing to work privately with both Dima and Matthias to resolve this
conflict.
David
for the sage-conduct committee
On Wed, Apr 10, 2024 at 7:30 PM Matthias Koeppe
wrote:
> Reported.
>
> On Wednesday, April 10, 2024 at 3:39:56 PM U
+1
On Thu, Mar 21, 2024 at 12:51 PM 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 on feedback from se
+1.
On Thu, Mar 21, 2024 at 4:09 PM 'Martin R' via sage-devel <
sage-devel@googlegroups.com> wrote:
> +1
>
> I just re-read the whole thing, and I'm quite impressed! Thank you!
>
> On Thursday 21 March 2024 at 19:03:34 UTC+1 Matthias Koeppe wrote:
>
>> +1.
>>
>> On Thursday, March 21, 2024 at 9:
This vote has passed, and I've added a "CI Fix" label
<https://github.com/sagemath/sage/labels/p%3A%20CI%20Fix> on github. I am
not going to have time to implement changes to our CI infrastructure in the
near future, but others are welcome to do so.
David
On Sun, Mar 10
proval
voting had a different result.
The anonymized votes are here
<https://docs.google.com/spreadsheets/d/12kbJepIKLpLKwLDum70FsSkqTto2St5gbspf3DyrPIc/edit?usp=sharing>,
in case anyone wants to do further analysis.
David
--
You received this message because you are subscribed to the
voting as well.
David
On Fri, Mar 15, 2024 at 10:42 PM Matthias Koeppe
wrote:
> Dear all:
> Please take the time to participate in the voting process for the
> "disputed" PRs.
>
>
> https://github.com/sagemath/sage/pulls?q=is%3Aopen+label%3Adisputed+is%3Apr+label%3A%22s%
(vivianep...@gmail.com, VivianePons on github)
David Roe (roed.m...@gmail.com, roed314 on github)
Julian Rüth (julian.ru...@fsfe.org, saraedum on github)
Thank you to everyone for voting!
I also want to thank Vincent Delecroix, David Joyner, Harald Schilly, and
William Stein for their service on
changes made by others be in a positive direction.
David
On Thu, Mar 14, 2024 at 7:29 PM Kwankyu Lee wrote:
> ... if there is any difference in process between the PRs currently set to
> "positive review" and those currently set to "needs review"?
>
>
> In my opinion
e to do so and I'd be happy
to offer a review.
David
On Mon, Mar 11, 2024 at 1:44 PM kcrisman wrote:
>
> It would be helpful for anyone explicitly voting +/-1 to either link to a
> previous comment or make a new actual comment (beyond the vote) to
> clarify. This is particularl
There is also this old trac ticket
<https://github.com/sagemath/sage/issues/23154> about implementing fast
arithmetic in genus 2 Jacobians, which never made it into Sage. I've CCed
Mike Jabobson, who worked on it.
David
On Tue, Mar 12, 2024 at 12:10 PM Giacomo Pope wrote:
>
meone
else volunteers to write them.
David
On Sun, Mar 10, 2024 at 6:18 PM Matthias Koeppe
wrote:
> Yes, we could prepare several proposals for separate projects.
> One can see in the lists of past funded projects that some organizations
> have received funding for two simultaneous pr
1987309496> that
these kinds of guidelines are better put in our reviewing code rather than
the Code of Conduct, since they feel more like details than guiding
principles.
David
> David Roe schrieb am Sonntag, 10. März 2024 um 16:44:06 UTC+1:
>
>> I agree with both Tobias and Matthia
date the code of conduct in #37501
<https://github.com/sagemath/sage/pull/37501>, we should update the dates
when the code of conduct was last modified.
There is also discussion at the bottom about Sage's governance structure,
but I don't think that's required for an affiliate
In the interest of moving forward, I'm planning on giving the PR positive
review on Thursday. Of course, additional changes are always possible
through a discussion here if we find that there are more that we want to
add.
David
On Tue, Mar 5, 2024 at 2:45 PM Matthias Koeppe
wrote:
> I thin
I can't take the lead.
David
On Sat, Mar 9, 2024 at 5:13 PM Matthias Koeppe
wrote:
> SageMath could benefit from hiring a technical writer for a project to
> improve the Sage documentation. Google Season of Docs is a program that
> supports such projects. Some key facts:
> - total p
+1
- DLD
On 03:43 Mon 04 Mar 2024, David Roe wrote:
The following proposal has been made several times the last few weeks: in
PR #37428 <https://github.com/sagemath/sage/issues/37428>, in this thread
<https://groups.google.com/g/sage-devel/c/uWHaWK7b6H4> and then in this
t
+1
- DLD
On 03:23 Mon 04 Mar 2024, David Roe wrote:
With no further discussion on this thread
<https://groups.google.com/g/sage-devel/c/XDvKkMRoDk4>, I'm calling a vote
on a new process for resolving disagreements on a PR.
*Proposal*
It is now allowed to vote on disputed PRs
nstructively resolve the current blocks individually and voluntarily.
We will continue to work toward addressing the underlying reasons
(revisions to the code of conduct, recruiting new members, new policies on
labels and reviewing, additional actions on github and in private).
Thanks,
David
for the
ase was actually one of the reasons that I suggested a 2 to 1
threshold. I think that if a single objector thinks that a PR should not
proceed and the author and reviewer both think it should, the onus should
be on the objector to find other developers who share their objections.
David
On Wed, Fe
ippela...@gmail.com, jplab on github)
John Palmieri (jhpalmier...@gmail.com, jhpalmieri on github)
Viviane Pons (vivianep...@gmail.com, VivianePons on github)
David Roe (roed.m...@gmail.com, roed314 on github)
Julian Rüth (julian.ru...@fsfe.org, saraedum on github)
William Stein (wst...@gmail.com, willia
We've received several nominations, but if you have been on the fence about
suggesting someone I encourage you to write to us. The nomination period
will close tomorrow night.
David
On Wed, Feb 28, 2024 at 10:52 AM David Roe wrote:
>
>
> On Wed, Feb 28, 2024 at 10:51 AM Dima Pa
cket.
b. If a PR becomes disputed (as described in this proposal
<https://groups.google.com/g/sage-devel/c/IgBYUJl33SQ>), the "CI Fix"
status can be voted on separately upon request; otherwise it should be
applied if and only if positive review is applied.
Voting will be open until Wedn
courage the release manager to give enough time for
everyone to express an opinion.
Voting will be open until Wednesday, March 13.
David
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving em
el free to
either email me at roed.m...@gmail.com or contact me on Zulip
<http://sagemath.zulipchat.com>). In the long term, we should figure out a
better process and document it.
David
On Fri, Mar 1, 2024 at 11:53 AM 'Martin R' via sage-devel <
sage-devel@googlegroups.com> wro
hat it shouldn't be merged, and there
> hasn't been a vote.
>
Once we settle on a process for managing disagreement about PRs (as we're
discussing in this thread
<https://groups.google.com/g/sage-devel/c/XDvKkMRoDk4/m/0yrtdKkGAwAJ>), I
think adding something like
mittee at any point.
>>
>
> b. sounds way too broad to me. Should it say in addition something like
> "The complaint in question only qualifies if it was ruled valid by the
> committee." Note that these complaints were misused in the past.
>
Sure, that seems reasona
On Wed, Feb 28, 2024 at 1:01 AM Kwankyu Lee wrote:
> Thank you for making progress on these urgent issues. I suggest the
> following:
>
> 1. Open two other new threads, each of which is for voting on each
> proposal.
> 2. On a proposal, it should be clear that *a positive vote (+1) is for
> the w
tely upon
request; otherwise it will just follow the same process described above.
I'm sorry for abandoning this thread
<https://groups.google.com/g/sage-devel/c/XON6NTJa33o> for the last few
months, but hope that we can make some progress now.
David
--
You received this message because
ge-ab...@googlegroups.com. I
announced the membership of this committee a few days ago in another
thread; since then one member has resigned and another has expressed
willingness to be replaced. The current membership is
William Stein
John Palmieri
David Roe
Vincent Delecroix
David Joyner
As a group, we believe
https://doc.sagemath.org/html/en/developer/review.html.
>
I also agree that usage (2) should get a new name. How about "CIFix?"
David
> On Monday, February 26, 2024 at 4:21:58 PM UTC-8 Kwankyu Lee wrote:
>
>> On Tuesday, February 27, 2024 at 2:43:18 AM UTC+9 Vincent
to EE though in order to get the
generators in terms of coordinates for your original curve.
David
On Mon, Feb 26, 2024 at 12:41 PM William Paulsen
wrote:
> I ran the following code in SageMath 10.2:
>
> sage: K. = QuadraticField(2)
> sage: E = EllipticCurve([0, 60/49*a - 135/49, 0, -57
can confirm that the google group list does receive messages.
> And if so, may we know who's on the committee?
>
> Asking on behalf of the community.
>
The members of the committee are:
* William Stein
* Vincent Delecroix
* David Joyner
* Harald Schilly
* John Palmieri
* David Roe
On 22:42 Sun 11 Feb 2024, Matthias Koeppe wrote:
*2. Is our community aware of the sagemath/sage GitHub wiki?*
https://github.com/sagemath/sage/wiki
- Are the contents of the wiki front page useful?
I think the existence of two wikis (i.e. the github wiki and
https://wiki.sagemath.org/) is con
lly makes it the opposite of a catchall error.
>
The main scenario when I use a RuntimeError is when an assumption that I
never expected to be violated fails. I agree with Travis that catchall is
not the right description for this error type.
David
--
You received this message because you ar
o +1 from me, with a manual check that the change seems appropriate.
David
On Mon, Feb 5, 2024 at 7:54 PM Dave Morris
wrote:
> -1 from me.
>
> Looking at just a few uncovered some that I think are definitely not
> ArithmeticError.
>
> Examples:
> There is an occur
ant is in a different Python class.
Instead of "fixing" the quotient function, you can simply implement another
quotient function, call it quotient_to_cosets or something like that.
> On Saturday, February 3, 2024 at 10:24:54 PM UTC+5:30 David Roe wrote:
>
>> You can lift elem
reimages
[(), (2,4,6)(3,5,7), (2,6,4)(3,7,5)]
David
On Sat, Feb 3, 2024 at 10:58 AM 'Ruchit Jagodara' via sage-devel <
sage-devel@googlegroups.com> wrote:
> I think this is giving a group isomorphic to the actual quotient group but
> I need the actual quotient group. Therefor,
I agree with Dima that 2 days is not enough time to gather feedback. Is
there any reason for the quick turnaround time?
David
P.S. I'm sorry about disappearing from the other thread about disputed
PRs. I will try to summarize the discussion on that thread and call for a
vote shortly.
O
Dear all,
I observe some doctest warnings that I don't know how to fix. This is
certainly a side effect of the modularization.
File "src/sage/plot/plot.py", line 569, in sage.plot.plot
Warning: Variable 'sig_on_count' referenced here was set only in doctest
marked '# needs sage.symbolic'
s
On Wed, Nov 29, 2023 at 10:12 AM tobia...@gmx.de wrote:
> At first I was very enthusiastic about this proposed policy, but after
> thinking about this for a bit I'm no longer convinced this is a good idea.
>
> First of all, the policy sets out to solve the case "where there is a
> general consens
's better put off to another thread.
David
On Tue, Nov 28, 2023 at 4:48 PM Dima Pasechnik wrote:
> On Tue, Nov 28, 2023 at 9:25 PM Kwankyu Lee wrote:
> >
> > Meanwhile, Matthias and Dima spent lots of mental energy to produce a
> prime example showing why we need the polic
everyone to keep the discussion positive and civil. I plan to call a vote
on whatever proposal comes out of our discussion.
David
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving em
Thank you Matthias; clearing out /usr/local/include/flint* and
/usr/local/flint* solved the problem.
David
On Mon, Nov 20, 2023 at 5:51 PM Matthias Koeppe
wrote:
> The real error from your log:
>
> sage/algebras/quatalg/quaternion_algebra_element.cpp:22735
ipy
<https://math.mit.edu/~roed/scipy-1.11.3.log>
../meson.build:82:0: ERROR: Compiler gfortran cannot compile programs.
I noticed that this is the first g++ call after a bunch of gcc calls, but
it doesn't seem to be the first g++ call overall. Any ideas?
David
--
You received this
I'm not aware of why we were suppressing jpeg support before, but this
sounds like a good idea to me.
David
On Thu, Nov 16, 2023 at 9:48 AM Eric Gourgoulhon
wrote:
> Hi All,
>
> Pillow provides the Python Imaging Library (PIL)
> https://pillow.readthedocs.io/en/stable/
&g
ortran instead:
>
> make gfortran
> make
>
> the one from Homebrew is currently broken.
>
>
> On Mon, Oct 2, 2023 at 1:25 PM David Einstein wrote:
> >
> > I just upgraded an M1 macbook pro to osx 14.0, upgraded homebrew and
> tried rebuilding sage. It fail
On Wed, Sep 27, 2023 at 2:32 PM John H Palmieri
wrote:
> The github issue #36060 (https://github.com/sagemath/sage/issues/36060)
> proposes adding a backslash operator for Sage integers, so that "2 \ 3"
> will return the same as "3 / 2". Do you support this?
>
>
I'm not for or against. However, I
If you want the order generated by a, you can do
sage: K.=NumberField(x^2-10)
sage: OK=K.maximal_order()
sage: O = K.order(a)
sage: O.index_in(OK)
1
Note that this correctly fails in Nils' example:
sage: K.order(a^2)
...
ValueError: the rank of the span of gens is wrong
David
On Thu,
a this function
in expression.pyx:
cpdef _latex_Expression(x):
return char_to_str(GEx_to_str_latex(&(x)._gobj))
I think it would be reasonable for Sage to do what the original poster
suggested, and turn integrals into \int in latex rather than trying to
evaluate them.
David
On Wed, Jul
to review,
help is more than welcome).
Best,
David.
On Thursday, July 6, 2023 at 6:01:23 PM UTC+2 Nils Bruin wrote:
> On Wednesday, 5 July 2023 at 21:54:03 UTC-7 David Coudert wrote:
>
> The current design choice in `EdgesView` is to sort only when asking for
> the list of edges
and
> ''>
>
> I think that either E is broken from start and an error should have
> been raised in the first stage or everything is fine and we should
> have a proper string representation.
>
> On Wed, 5 Jul 2023 at 08:33, David Coudert wrote:
> >
> > T
I have opened https://github.com/sagemath/sage/issues/35902 to collect such
kind of issues.
Please use it to share new cases.
On Wednesday, July 5, 2023 at 9:38:28 AM UTC+2 Georgi Guninski wrote:
> Hi sage devs, your daily dose of incomparable objects,
> fix 'em while they are free ;)
>
> G=Grap
Most of these calls are done on purpose and safe, but some may raise an
error.
> ./base/static_sparse_backend.pyx:512: vertices.sort()
It's inside a try ... except... statement. We may certainly remove it in
the future.
> ./base/static_sparse_graph.pxd:10: void qsort(void *base, int nmemb, i
There is an active deprecation warning in method edges(). Parameter sort
will be set to False in the future. I'm surprised you don't see it.
sage: Graph([('A','B'),(1,2)]).edges()
:1: DeprecationWarning: parameter 'sort' will
be set to False by default in the future See https://github.com/sagema
Thanks for reporting this issue. I have opened an issue
(https://github.com/sagemath/sage/issues/35889) and will propose a fix asap.
On Sunday, July 2, 2023 at 6:37:45 PM UTC+2 Georgi Guninski wrote:
> You definitely can construct graph with incomparable vertices
> and they worked as expected in
I vote for (A)
On Friday, June 30, 2023 at 2:59:53 PM UTC+2 David Ayotte wrote:
> I vote for (A)
>
> Le jeudi 29 juin 2023 à 18:47:42 UTC-4, Edgar Costa a écrit :
>
>> I vote for (A)
>>
>> On Thu, Jun 29, 2023 at 6:27 PM Marc Culler wrote:
>>
>>>
I vote for (A)
Le jeudi 29 juin 2023 à 18:47:42 UTC-4, Edgar Costa a écrit :
> I vote for (A)
>
> On Thu, Jun 29, 2023 at 6:27 PM Marc Culler wrote:
>
>> I vote for (C).
>>
>> On Wednesday, June 28, 2023 at 9:40:07 PM UTC-5 Kwankyu Lee wrote:
>>
>>> Hi,
>>>
>>> We spent six days for the prelimin
I vote for (A)
On Thu, Jun 29, 2023 at 5:13 AM Eric Gourgoulhon
wrote:
> I vote for (A)
>
> --
> 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+unsub
while work goes forward on a summarizing wiki page, I'd like to
hear suggestions from others about how to make the process better. Feel
free to email the list or write to me directly.
We made it through the github discussion, and we can make it through this.
Stay positive.
David
On T
How do you handle files that depend on multiple libraries (like both FLINT
and NTL for example)? Are these only included in sagemath-standard?
David
On Fri, Jun 16, 2023 at 2:19 PM Matthias Koeppe
wrote:
> On Friday, June 16, 2023 at 11:07:36 AM UTC-7 David Roe wrote:
>
> I assume
every file
part of exactly one package (aside from sagemath-standard, which is the
union of all of them?). From the quick glance I've taken so far, the
division looks pretty reasonable.
David
On Fri, Jun 16, 2023 at 1:58 PM Matthias Koeppe
wrote:
> (index of previous posts: https://github
ent. As a workaround you
can either use pari (as you discovered), or use an integer matrix and
occasionally reduce the coefficients.
David
On Wed, Jun 14, 2023 at 9:18 AM Georgi Guninski wrote:
> pari/gp appears significantly faster:
>
> sage: time M31=M3**n
> CPU times: user 11.2 s, sys
I will delete any messages to this thread in the next week. I encourage
people who have not yet engaged to think about the issue and see if they
have a compromise to suggest.
David
On Wed, May 31, 2023 at 5:24 PM G. M.-S. wrote:
>
> Hi all.
>
> I would like to ask for a moratorium
1 - 100 of 6360 matches
Mail list logo
