Re: [sage-devel] Re: Demote brial (= polybori) from standard to experimental

[Vincent Delecroix]

+1 for me too

On Mon, 10 Jun 2024 at 18:41, Nathan Dunfield  wrote:
>
> This makes sense to me.
>
> Nathan
>
> On Sunday, October 1, 2023 at 2:29:55 PM UTC-5 Matthias Koeppe wrote:
>
> I propose to demote this package to experimental.
> - It has been declared dead at least once -  
> https://martinralbrecht.wordpress.com/2015/06/13/polybori-is-dead-it-needs-your-help/
> - It has no upstream maintainer (except for ermergency fixes by Francois 
> Bissey) - https://github.com/BRiAl/BRiAl/graphs/contributors, 
> https://sourceforge.net/projects/polybori/
> - It has been dropped from Debian testing, where it seems to block SageMath 
> upgrades (Sage is stuck at 9.5 in Debian/Ubuntu)
> - The conda and homebrew packages of brial lead to segfaults 
> (https://github.com/sagemath/sage/issues/35595, 
> https://github.com/sagemath/sage/issues/34780)
> - It is disconnected from the advances in SMT (satisfiability modulo 
> theories) over the past decade (representative paper: 
> https://arxiv.org/abs/2305.00028v2)
>
>
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/427f1f70-7cc7-4f5e-8466-ad28bb81ae87n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAnrB_9oTfDeYfSAu%2BVzGU-9cKe8Rrdp2kCNB7LnPs1_xA%40mail.gmail.com.

Re: [sage-devel] Re: New labels v: mimimal, v: small ... on pull requests

[Vincent Delecroix]

I fully agree with Travis. I do not see the added value of these
additional tags.

On Thu, 9 May 2024 at 23:46, Travis Scrimshaw  wrote:
>
> I am *very* strongly opposed to these tags. Their cutoffs are arbitrary nor 
> they serve no useful purpose as far as I can tell. To this point, they do not 
> reflect the difficulty of a review; in fact, they are at best 
> counterproductive to finding reviewers because it might deter people from 
> reviewing "large" or "huge" changes as they can include lots of trivial 
> doctest changes. At best it is just additional clutter in all of the 
> information for PRs.
>
> From a community perspective, I feel such changes should have been brought to 
> the attention of sage-devel once the PR was at a positive review. 
> Specifically, before the PR was merged. Not everyone has time to read every 
> PR, and a small consensus of developers might not reflect the development 
> community at-large when making changes like this.
>
> Best,
> Travis
>
>
> On Tuesday, May 7, 2024 at 3:12:27 PM UTC+9 seb@gmail.com wrote:
>>
>> Dear Sage developers,
>>
>> You may have noticed that since yesterday a new type of labels with the `v:` 
>> prefix has appeared on our PRs. These are automatically set to classify PRs 
>> based on their size. For more information, see #37262.
>>
>> Sebastian
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/a1904934-a31f-4ce0-83c2-76cf2d1a70f1n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3DBaLG%2B4BfJ-qw9cJKY5x_4zKc1%2B76yF%2BNQ6MJLVV3CMw%40mail.gmail.com.

Re: [sage-devel] Re: Matrices over QQbar

[Vincent Delecroix]

The fix was easy. Much harder was to find the root of the problem!

If you are interested in intensive computations over QQbar I strongly
advise you to look towards https://flintlib.org/ maintained by Fredrik
Johansson. This library has *two* implementations of QQbar which are
way more performant (and probably more reliable) than what is in
SageMath. The more or less short term goal is to use flint
implementations to replace the current QQbar implementation in
SageMath.You could give it a try inside SageMath via
https://github.com/mezzarobba/flint_gr_sage (feel free to open an
issue there asking for installation help or describing the things you
want to compute).

I do intend to make my commit part of SageMath QQbar, but it is not on
the top priority list.

Best
Vincent

On Mon, 6 May 2024 at 09:27, Hakan Granath  wrote:
>
> Great, thanks for working out and fixing the (quite non-trivial, it seems) 
> root cause of this issue!
>
> Just a curious question: would it be useful to add the functionality of your 
> commit 8de6ba5 to potentially simplify QQbar objects? Especially doing linear 
> algebra over QQbar I guess you get many trivial operations (like adding 0) 
> and optimizing them away might maybe improve performance? Just an idea, I 
> haven't done any benchmarking to support that hypothesis.
>
> Best regards,
>
> Håkan
>
> On Mon, May 6, 2024 at 12:15 AM Vincent Delecroix <20100.delecr...@gmail.com> 
> wrote:
>>
>> Turns out to be a serious bug in complex interval fields. The problem
>> is hopefully fixed by https://github.com/sagemath/sage/pull/37941
>> which should make its way to the next sage release.
>>
>> Thanks again for your report.
>> Vincent
>>
>> On Fri, 3 May 2024 at 18:13, vdelecroix <20100.delecr...@gmail.com> wrote:
>> >
>> > Thanks for your report! I simplified a bit your example and posted an 
>> > issue https://github.com/sagemath/sage/issues/37927.
>> >
>> > Vincent
>> >
>> > Le vendredi 3 mai 2024 à 15:05:03 UTC+2, Hakan Granath a écrit :
>> >>
>> >> Hi,
>> >>
>> >> I think sometimes matrices over QQbar give erroneous results (sorry for 
>> >> the messy example, if I try to simplify it the problem disappears):
>> >>
>> >> R. = QQ[]
>> >> v1 = QQbar.polynomial_root(AA.common_polynomial(y^2 + 1), CIF(RIF(RR(0)), 
>> >> RIF(-RR(1
>> >> v2 = QQbar.polynomial_root(AA.common_polynomial(y^2 + 1), CIF(RIF(RR(0)), 
>> >> RIF(RR(1
>> >> v3 = 4*v2
>> >> v4 = AA.polynomial_root(AA.common_polynomial(y^2 - 2), 
>> >> RIF(-RR(1.4142135623730951), -RR(1.4142135623730949)))
>> >> v5 = AA.polynomial_root(AA.common_polynomial(y^2 - 2), 
>> >> RIF(RR(1.4142135623730949), RR(1.4142135623730951)))
>> >> v6 = QQbar.polynomial_root(AA.common_polynomial(y^2 + 16), 
>> >> CIF(RIF(RR(0)), RIF(-RR(4
>> >> v7 = v6*v6
>> >> v8 = QQbar.polynomial_root(AA.common_polynomial(y^2 + 1), CIF(RIF(RR(0)), 
>> >> RIF(RR(1
>> >>
>> >> M = matrix(QQbar, [[0, 0, 1, 0, 0, 0, 0, 0, 0, 0], [0, 1, 0, 0, 0, 0, 0, 
>> >> 0, 0, 0], [-4, 2*v1, 1, 64, -32*v1, -16, 8*v1, 4, -2*v1, -1], [4*v1, 1, 
>> >> 0, -192*v1, -80, 32*v1, 12, -4*v1, -1, 0], [2, 0, 0, -480, 160*v1, 48, 
>> >> -12*v1, -2, 0, 0], [-4, 2*v2, 1, 64, -32*v2, -16, 8*v2, 4, -2*v2, -1], 
>> >> [v3, 1, 0, -192*v2, -80, 32*v2, 12, -v3, -1, 0], [2, 0, 0, -480, 160*v2, 
>> >> 48, -12*v2, -2, 0, 0], [0, 0, 0, 8, QQbar(4*v4), 4, QQbar(2*v4), 2, 
>> >> QQbar(AA.polynomial_root(AA.common_polynomial(y^2 - 2), 
>> >> RIF(-RR(1.4142135623730951), -RR(1.4142135623730949, 1], [0, 0, 0, 
>> >> QQbar(24*v4), 20, QQbar(8*v4), 6, QQbar(2*v4), 1, 0], [0, 0, 0, 8, 
>> >> QQbar(4*v5), 4, QQbar(2*v5), 2, 
>> >> QQbar(AA.polynomial_root(AA.common_polynomial(y^2 - 2), 
>> >> RIF(RR(1.4142135623730949), RR(1.4142135623730951, 1], [0, 0, 0, 
>> >> QQbar(24*v5), 20, QQbar(8*v5), 6, QQbar(2*v5), 1, 0], [0, 0, 0, v7*v7*v7, 
>> >> v7*v7*v6, v7*v7, v6*v6*v6, v6*v6, v6, 1], [0, 0, 0, -4096, 1024*v8, 256, 
>> >> -64*v8, -16, 4*v8, 1]])
>> >>
>> >> With this matrix I get:
>> >>
>> >>   sage: M.right_kernel_matrix()
>> >>   []
>> >>
>> >> but in fact the right kernel is generated by:
>> >>
>> >>   sage: v = Matrix(QQbar, 10, 1, [-108, 0, 0, 1, 0, 12, 0, -60, 0, 64])
>> >>   sage: M * v == 0
>> >>   True
>> >>
>> >&

Re: [sage-devel] Re: Matrices over QQbar

[Vincent Delecroix]

Turns out to be a serious bug in complex interval fields. The problem
is hopefully fixed by https://github.com/sagemath/sage/pull/37941
which should make its way to the next sage release.

Thanks again for your report.
Vincent

On Fri, 3 May 2024 at 18:13, vdelecroix <20100.delecr...@gmail.com> wrote:
>
> Thanks for your report! I simplified a bit your example and posted an issue 
> https://github.com/sagemath/sage/issues/37927.
>
> Vincent
>
> Le vendredi 3 mai 2024 à 15:05:03 UTC+2, Hakan Granath a écrit :
>>
>> Hi,
>>
>> I think sometimes matrices over QQbar give erroneous results (sorry for the 
>> messy example, if I try to simplify it the problem disappears):
>>
>> R. = QQ[]
>> v1 = QQbar.polynomial_root(AA.common_polynomial(y^2 + 1), CIF(RIF(RR(0)), 
>> RIF(-RR(1
>> v2 = QQbar.polynomial_root(AA.common_polynomial(y^2 + 1), CIF(RIF(RR(0)), 
>> RIF(RR(1
>> v3 = 4*v2
>> v4 = AA.polynomial_root(AA.common_polynomial(y^2 - 2), 
>> RIF(-RR(1.4142135623730951), -RR(1.4142135623730949)))
>> v5 = AA.polynomial_root(AA.common_polynomial(y^2 - 2), 
>> RIF(RR(1.4142135623730949), RR(1.4142135623730951)))
>> v6 = QQbar.polynomial_root(AA.common_polynomial(y^2 + 16), CIF(RIF(RR(0)), 
>> RIF(-RR(4
>> v7 = v6*v6
>> v8 = QQbar.polynomial_root(AA.common_polynomial(y^2 + 1), CIF(RIF(RR(0)), 
>> RIF(RR(1
>>
>> M = matrix(QQbar, [[0, 0, 1, 0, 0, 0, 0, 0, 0, 0], [0, 1, 0, 0, 0, 0, 0, 0, 
>> 0, 0], [-4, 2*v1, 1, 64, -32*v1, -16, 8*v1, 4, -2*v1, -1], [4*v1, 1, 0, 
>> -192*v1, -80, 32*v1, 12, -4*v1, -1, 0], [2, 0, 0, -480, 160*v1, 48, -12*v1, 
>> -2, 0, 0], [-4, 2*v2, 1, 64, -32*v2, -16, 8*v2, 4, -2*v2, -1], [v3, 1, 0, 
>> -192*v2, -80, 32*v2, 12, -v3, -1, 0], [2, 0, 0, -480, 160*v2, 48, -12*v2, 
>> -2, 0, 0], [0, 0, 0, 8, QQbar(4*v4), 4, QQbar(2*v4), 2, 
>> QQbar(AA.polynomial_root(AA.common_polynomial(y^2 - 2), 
>> RIF(-RR(1.4142135623730951), -RR(1.4142135623730949, 1], [0, 0, 0, 
>> QQbar(24*v4), 20, QQbar(8*v4), 6, QQbar(2*v4), 1, 0], [0, 0, 0, 8, 
>> QQbar(4*v5), 4, QQbar(2*v5), 2, 
>> QQbar(AA.polynomial_root(AA.common_polynomial(y^2 - 2), 
>> RIF(RR(1.4142135623730949), RR(1.4142135623730951, 1], [0, 0, 0, 
>> QQbar(24*v5), 20, QQbar(8*v5), 6, QQbar(2*v5), 1, 0], [0, 0, 0, v7*v7*v7, 
>> v7*v7*v6, v7*v7, v6*v6*v6, v6*v6, v6, 1], [0, 0, 0, -4096, 1024*v8, 256, 
>> -64*v8, -16, 4*v8, 1]])
>>
>> With this matrix I get:
>>
>>   sage: M.right_kernel_matrix()
>>   []
>>
>> but in fact the right kernel is generated by:
>>
>>   sage: v = Matrix(QQbar, 10, 1, [-108, 0, 0, 1, 0, 12, 0, -60, 0, 64])
>>   sage: M * v == 0
>>   True
>>
>> This is with SageMath version 10.3 using Python 3.11.1 on Ubuntu 22.04.4.
>>
>> Best regards,
>>
>> Håkan Granath
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/1c927686-bada-4943-8000-a6fdf6e71029n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkgsAcFmt-6NKWvuh0va_UVy-jdSJVnPrSrjGE_CA3Nog%40mail.gmail.com.

Re: [sage-devel] SEGV caused by CTL-C in C/C++ code probably related to signals

[Vincent Delecroix]

I do not remember anything specific about solve_mod. Though, there are
many places in Cython source code where sig_on/sig_off is not handled
carefully enough (and many that were fixed).

The fact that it is not reproducible is not necessarily a huge problem. However,
- Could you share the code (as minimal as possible) that provokes this
on your machine?
- Do you have the complete (C) trace of the crash? You might need to
install gdb depending on your setup.

Vincent

On Wed, 10 Apr 2024 at 16:18, Georgi Guninski  wrote:
>
> I don't have reproducible testcase, but my pain is that sometimes if I
> press CTL-C e.g. when solve_mod() is called in a loop, I get SEGV and
> abort.
> I suspect besides signals, it is hitting race condition.
> Is this a known issue?
>
> Very long ago there was vulnerability in sendmail, where it did
> printf() or similar in signal handler and this was documented in the
> literature.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAGUWgD_7t9OTNdo6Ovrt%3DJdNqmGJLPGsZHVoJK0mNPQhuz1CKQ%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkUS4secJzvZJfSVivuqoKwnUUGSjPxi2aUAuTY2MinBw%40mail.gmail.com.

Re: [sage-devel] Re: stopping cypari2, pari-jupyter and pplpy maintenance

[Vincent Delecroix]

Thanks Matthias. You are now an owner on PyPI.

On Tue, 12 Mar 2024 at 22:59, Matthias Koeppe  wrote:
>
> Thanks, Vincent, for all your work on these projects in the past, and for 
> letting us know about your decision.
> As https://github.com/sagemath/cypari2/issues/131 indicates (and previously 
> raised in 
> https://groups.google.com/g/sage-devel/c/JBFbtUNhqNU/m/2PvzZbS8AQAJ), we will 
> need to document development workflow, governance, release management process 
> for these projects (and others in the sagemath org).
>
> You can add me on PyPI for these projects, then I'll use the same deployment 
> key that the other sagemath projects use for pushing releases to PyPI.
> https://github.com/sagemath/cypari2/pull/141 is already prepared for this, 
> and I can add the same for the other projects.
>
> Matthias
>
> On Tuesday, March 12, 2024 at 10:44:08 AM UTC-7 Vincent Delecroix wrote:
>>
>> Dear all,
>>
>> I used to be the maintainer of cypari2, pari-jupyter and pplpy. I will
>> not work anymore on any of them from now on. The three projects are
>> under the sagemath organization on github so that any administrator
>> can take over. Concerning the access to PyPI to push releases I can
>> promote anybody who wants access (do we have a policy for this?).
>>
>> Best
>> Vincent
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/f174964b-692c-498a-be21-45a0b192e2f4n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3Dd3ZL4-gStcg7%3DmHSpPxY%2BhABBtaXDFB4SZXORuT0F_Q%40mail.gmail.com.

Re: [sage-devel] stopping cypari2, pari-jupyter and pplpy maintenance

[Vincent Delecroix]

Hi William,

Mostly time. Some choices had to be made on where to concentrate my
energy. I do not find it particularly rewarding to work on these
projects. The lack of support, good atmosphere and appreciation did
not help me trying to find more time working on them.

Best
Vincent

On Tue, 12 Mar 2024 at 18:51, William Stein  wrote:
>
> Hi Vincent,
>
> To help whoever takes over, do you have any comments about *why* you
> will not work on any of these projects?  Is it just lack of time and you need
> to focus on something else, or is there something fundamentally annoying
> about the direction of these projects?  Thanks for any insight to help guide
> whoever takes over.
>
>  -- William
>
> On Tue, Mar 12, 2024 at 10:44 AM Vincent Delecroix 
> <20100.delecr...@gmail.com> wrote:
>>
>> Dear all,
>>
>> I used to be the maintainer of cypari2, pari-jupyter and pplpy. I will
>> not work anymore on any of them from now on. The three projects are
>> under the sagemath organization on github so that any administrator
>> can take over. Concerning the access to PyPI to push releases I can
>> promote anybody who wants access (do we have a policy for this?).
>>
>> Best
>> Vincent
>>
>> --
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3DBxVFYEore941XQfF%3DLVV3cf7d-nJ1YUAADC3sYsKjFw%40mail.gmail.com.
>
>
>
> --
> William (http://wstein.org)
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CACLE5GAHLRU0e3cTQBx1WVxs_KrsbpMVzv0zyX_pOog1_JiOpw%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3DQwt_Q%3D0coaCPcmwwCwsdk5eUm%3DPvbNWbkAAFiXAzQsw%40mail.gmail.com.

[sage-devel] stopping cypari2, pari-jupyter and pplpy maintenance

[Vincent Delecroix]

Dear all,

I used to be the maintainer of cypari2, pari-jupyter and pplpy. I will
not work anymore on any of them from now on. The three projects are
under the sagemath organization on github so that any administrator
can take over. Concerning the access to PyPI to push releases I can
promote anybody who wants access (do we have a policy for this?).

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3DBxVFYEore941XQfF%3DLVV3cf7d-nJ1YUAADC3sYsKjFw%40mail.gmail.com.

Re: [sage-devel] VOTE: Use "CI Fix" label for merging into continuous integration runs

[Vincent Delecroix]

+1

On Mon, 4 Mar 2024 at 20:21, G. M.-S.  wrote:
>
>
> +1
>
> Guillermo
>
> On Mon, 4 Mar 2024 at 09:43, David Roe  wrote:
>>
>> The following proposal has been made several times the last few weeks: in PR 
>> #37428, in this thread and then in this thread.  It is orthogonal to the 
>> ongoing vote in this thread.  With no further discussion, I'm calling a vote.
>>
>> Background
>>
>> Starting in Sage 10.2, PRs with the Blocker label have been merged into all 
>> other PRs before running CI; see the changelog and this post for more 
>> details.  This has led to disagreements about whether this label should be 
>> applied.
>>
>> Proposal
>> We use "CI Fix" rather than Blocker to determine whether an open PR should 
>> be merged before running CI.  Blocker will retain its previous meaning of a 
>> PR that should be merged before the next release is finished.  The process 
>> below describes how to resolve disagreements about whether the "CI Fix" 
>> label should be applied.
>> a. Only PRs with positive review should be marked with the "CI Fix" label.  
>> This should be done if both author and reviewer agree that it is 
>> appropriate, and a rationale should be given in a comment on the ticket.
>> b. If a PR becomes disputed (as described in this proposal), 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 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 emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CANnG189Rx%3DfXHDCQvDiTS0f_qHwRG9LbfiKKqph6DXuF%3Dd1zcw%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAm6wy1c4mDnvfwT5Ow%2BCEYvheqKDyzOpTfjJZUd_Ur%3DNQ%40mail.gmail.com.

Re: [sage-devel] VOTE: disputed PRs

[Vincent Delecroix]

+1

On Mon, 4 Mar 2024 at 20:20, G. M.-S.  wrote:
>
>
> +1
>
> Guillermo
>
> On Mon, 4 Mar 2024 at 09:23, David Roe  wrote:
>>
>> With no further discussion on this thread, 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 directly on Github rather than 
>> bringing them to sage-devel.  Working things out amicably is preferable, and 
>> anyone is welcome to ask on sage-devel for more eyes on a PR.  If you notice 
>> a serious issue with a PR, it is acceptable to change it to Needs Work (and 
>> make a comment!) as an initial step, but if the author or reviewer do not 
>> agree then process below should be followed instead. This process is 
>> intended as a lower-intensity method for resolving disagreements, and full 
>> votes on sage-devel override the process described below.
>> a. When there is disagreement about whether a PR should be merged, anyone 
>> may mark a PR as disputed.
>> b. There is no scheduled vote, but rather an ongoing poll based on opinions 
>> expressed by developers on the PR (these opinions can be expressed via 
>> previous positive reviews or explicit comments giving approval).  The PR 
>> author is presumed to vote in favor; if they give up or no longer favor the 
>> PR they have the right to close the PR overall without any further voting.
>> c. If the total number of positive votes is at least twice the number of 
>> negative votes, anyone involved may set the status to positive review; if 
>> the total number of positive votes is less than twice the number of negative 
>> votes, anyone involved may set the status to needs review.  When either of 
>> these actions is taken, the person changing the status must list the people 
>> they are counting as positive and negative votes in a comment using @ 
>> mentions.
>> d. The final decision on merging a disputed PR remains with the release 
>> manager, and we encourage 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 emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CANnG189YucyTQqiSYM7%2BBbgDHSauYdzsP9G%3DDP5gXYhgp15KTQ%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmCE2QRbey4%2B42mXhA%3D8e7gz1zJO1%2BcF5fgYEpARMt1vQ%40mail.gmail.com.

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

[Vincent Delecroix]

On Thu, 29 Feb 2024 at 01:49, 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.
>
>
> Sorry if it was not clear to you, but the discussion before this vote is here:
>
> https://groups.google.com/g/sage-devel/c/uWHaWK7b6H4

>From my point of view, the discussion that happened in the linked
thread has few to do from (1)+(2)+(3) of Marc's proposal (that I
approve very much!). It contains a lot of controversy and you did
write "Anyway, as there are only objections here, I give up.". You
then launched this vote thread 2 days after while the discussion was
still going on in the first one. Notice that the discussion that
happened in the linked thread has very few to do with the vote
proposal that you made here. Your proposal was never introduced as a
proposal open to amendment but only as a vote.

To me this call to vote is premature and for this reason I vote negatively (-1).

Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAnNd1%3DVLQfYHBGrQeMCHJ__4XnX1usujiX3dCQHK5%3DvLA%40mail.gmail.com.

Re: [sage-devel] Re: Unload "blocker" label

[Vincent Delecroix]

In that case, let me do a proposal.

Introduce a new label distinct from "blocker" for

usage 2: PRs that should be merged temporarily before CI tests run

(even though I think that "merged temporarily" would better be clarified)

Vincent

On Mon, 26 Feb 2024 at 18:35, Matthias Koeppe  wrote:
>
> On Monday, February 26, 2024 at 5:31:47 AM UTC-8 Kwankyu Lee wrote:
>
> Anyway, as there are only objections here, I give up.
>
> Thanks for opinions.
>
>
> On Monday, February 26, 2024 at 6:02:41 AM UTC-8 Vincent Delecroix wrote:
>
> Dear Kwankyu,
> Either you give up because people disagree with you (which is a
> problem about yourself) or you feel like your proposal was not given
> the credit it should have been (which is a problem with the tone of
> the "commenters" e-mails). Or maybe something else. But sending an
> e-mail saying that you give up because of objections is neither
> helping the discussion nor the technical problem that you pointed out
> in your initial e-mail.
>
>
> Vincent, I think both are unnecessarily harsh readings of "I give up."
>
> I read Kwankyu's post simply as "I am withdrawing my proposal".
>
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/0857b65d-3e62-49c2-a622-d692d836bce2n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAnDbu71CoyQeb%3D%2BGBJY4ak7mFpGLUqgUYUZSGQF4uaGLQ%40mail.gmail.com.

Re: [sage-devel] Re: Unload "blocker" label

[Vincent Delecroix]

Dear Kwankyu,

Note that everybody who kindly took the time to consider your proposal
responded the same : it seems more consistent to have only two
categories {1, 3} and {2} rather than three (following your
numbering).

Either you give up because people disagree with you (which is a
problem about yourself) or you feel like your proposal was not given
the credit it should have been (which is a problem with the tone of
the "commenters" e-mails). Or maybe something else. But sending an
e-mail saying that you give up because of objections is neither
helping the discussion nor the technical problem that you pointed out
in your initial e-mail.

Best
Vincent


On Mon, 26 Feb 2024 at 14:31, Kwankyu Lee  wrote:
>
> Anyway, as there are only objections here, I give up.
>
> Thanks for opinions.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/6b53b2d5-7d52-479b-8886-50c8f1100637n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkb5PkO7CxwZT8xBJcS3fV9mK4HJiWkdSC5GDd%2BiyPSCA%40mail.gmail.com.

Re: [sage-devel] Re: Unload "blocker" label

[Vincent Delecroix]

Hi Kwankyu,

I do not agree with

usage 3: Issues that should be fixed as fast as possible

To me it is rather "issues that should be fixed before the next
release" (or at least it was the way it was supposed to work when we
had trac). This looks better to me as that there is no reason to
release a broken sage.

Best
Vincent

On Mon, 26 Feb 2024 at 09:17, Kwankyu Lee  wrote:
>
>
>
> On Monday, February 26, 2024 at 4:46:36 PM UTC+9 tobia...@gmx.de wrote:
>
> Just move "usage 2" to a new label. Would be more intuitive and explicit in 
> my opinion.
>
>
> I am a bit inclined to your opinion, but not sure. Others may argue that 
> "usage 1" and " usage 2" are better to be combined under one label.
>
> Anyway, here I am focusing on the (easy) issue of separating "usage 3" from 
> the "blocker" label.
>
>
>
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/609bd8c5-92dd-4c64-8204-a4956517558an%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAnLWEi%2BLJJ51tHJUARrykpe_AiwkMyU3NY_TTt_j07C4A%40mail.gmail.com.

Re: [sage-devel] One year of Sage development on GitHub

[Vincent Delecroix]

I fully second the observation of Michael though it might have few to
do with the github switch. Sage development nowadays does not seem to
be anymore about math research and efficient computations but mostly
about "dependencies", "infrastructure" and "maintenance". I am always
depressed by reading the change logs. It might have been a reasonable
thing if sage was a "stable core Computer Algebra System" on which
further specialized math research libraries would depend on. But the
latter is not the official nor advised way of doing things.

On Thu, 8 Feb 2024 at 14:02, Michael Orlitzky  wrote:
>
> On Thu, 2024-02-08 at 11:30 +, Dima Pasechnik wrote:
> >
> > We should not try to compete, in effect, with Conda etc, yet we do. This is
> > the primary reason for slowness.
> >
>
> My personal stats for the year 2023-02-08 through 2024-02-08:
>
>   Commits: 423
>   Reviews: 38
>
> Zero of those have anything to do with mathematics.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/665f0fd945ca6301e75489e1922fb03462cda021.camel%40orlitzky.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmCkF%2Bj1XUQEuAK2B%3DD6WDT8Ejk9qrVBZ6fVvxg8H19EQ%40mail.gmail.com.

Re: [sage-devel] Re: Exception in floor(tanh(91))

[Vincent Delecroix]

The following is the proper way to extract digits

sage: tanh(91).numerical_approx(digits=10)
1.0
sage: tanh(91).numerical_approx(digits=100)
0.998182667935304138503930

On Fri, 9 Feb 2024 at 17:16, Georgi Guninski  wrote:
>
> When I try to extract digits of tanh(91) via floor, I still get error
>
> sage: floor(10^4*tanh(91))
> ValueError
>
> sage: gp('floor(10^4*tanh(91))')
> 1
>
>
> gp computes it both ways :)
>
> sage: gp.default('realprecision',10^5)
> 0
> sage: gp('floor(tanh(91))')
> 0
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAGUWgD9_cAc%2B_WCMh%3D2hCuvMy2GO-tgcNnrARh2q7K%3D8CErrfQ%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAks%2BkJU61cDTC1vD911YRzVjMG67A-u4Jz%2BNU82WgYd0Q%40mail.gmail.com.

Re: [sage-devel] Unable to `load` or `import/cimport` Cython files into Sage while developing

[Vincent Delecroix]

Dear Jing,

Not being able to use Cython from this sage app is indeed problematic.
However as Dima said this is more a problem of the app rather than a
problem with sage itself. You would better open an issue at
https://github.com/3-manifolds/Sage_macOS. If you do, please post the
link of the issue in this thread.

Best
Vincent

On Wed, 27 Dec 2023 at 13:43, Dima Pasechnik  wrote:
>
> On Wed, Dec 27, 2023 at 12:23 PM Jing Guo  wrote:
> >
> > I just did. The following is the new error.
> >
> > ➜  local-hom-count git:(main) ✗ sage
> > ┌┐
> > │ SageMath version 10.2, Release Date: 2023-12-03│
> > │ Using Python 3.11.1. Type "help()" for help.   │
> > └┘
> > sage: load("helper_functions.pyx")
> > Compiling ./helper_functions.pyx...
> > ---
> > DistutilsExecErrorTraceback (most recent call last)
> > File 
> > /private/var/tmp/sage-10.2-current/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/setuptools/_distutils/unixccompiler.py:266,
> >  in UnixCCompiler.link(self, target_desc, objects, output_filename, 
> > output_dir, libraries, library_dirs, runtime_library_dirs, export_symbols, 
> > debug, extra_preargs, extra_postargs, build_temp, target_lang)
> > 264 linker = compiler_fixup(linker, ld_args)
> > --> 266 self.spawn(linker + ld_args)
> > 267 except DistutilsExecError as msg:
> >
> > File 
> > /private/var/tmp/sage-10.2-current/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/setuptools/_distutils/ccompiler.py:1041,
> >  in CCompiler.spawn(self, cmd, **kwargs)
> >1040 def spawn(self, cmd, **kwargs):
> > -> 1041 spawn(cmd, dry_run=self.dry_run, **kwargs)
> >
> > File 
> > /private/var/tmp/sage-10.2-current/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/setuptools/_distutils/spawn.py:70,
> >  in spawn(cmd, search_path, verbose, dry_run, env)
> >  69 cmd = cmd[0]
> > ---> 70 raise DistutilsExecError(
> >  71 "command {!r} failed with exit code {}".format(cmd, exitcode)
> >  72 )
> >
> > DistutilsExecError: command '/usr/bin/gcc' failed with exit code 1
>
> Please check https://doc.sagemath.org/html/en/installation/index.html#macos
> and note that you re doing development. I.e.
> you are trying to do Sage development in an unsupported environment.
> The app you are using does not come with all the tools needed to
> create Python extensions from Cython (this needs Apple software, which
> one cannot just bundle for copyright reasons).
>
> Having said that, your errors probably indicate that you have an
> outdated XCode/command line tools installed. But I don't know whether
> this can be made to work at all, or you really need a different
> install of Sage for your tasks.
>
>
>
>
> >
> > During handling of the above exception, another exception occurred:
> >
> > LinkError Traceback (most recent call last)
> > File 
> > /private/var/tmp/sage-10.2-current/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/sage/misc/cython.py:454,
> >  in cython(filename, verbose, compile_message, use_cache, 
> > create_local_c_file, annotate, sage_namespace, create_local_so_file)
> > 453 with redirection(2, errfile, close=False):
> > --> 454 dist.run_command("build")
> > 455 finally:
> >
> > File 
> > /private/var/tmp/sage-10.2-current/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/setuptools/dist.py:989,
> >  in Distribution.run_command(self, command)
> > 986 # Postpone defaults until all explicit configuration is considered
> > 987 # (setup() args, config files, command line and plugins)
> > --> 989 super().run_command(command)
> >
> > File 
> > /private/var/tmp/sage-10.2-current/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/setuptools/_distutils/dist.py:988,
> >  in Distribution.run_command(self, command)
> > 987 cmd_obj.ensure_finalized()
> > --> 988 cmd_obj.run()
> > 989 self.have_run[command] = 1
> >
> > File 
> > /private/var/tmp/sage-10.2-current/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/setuptools/_distutils/command/build.py:131,
> >  in build.run(self)
> > 130 for cmd_name in self.get_sub_commands():
> > --> 131 self.run_command(cmd_name)
> >
> > File 
> > /private/var/tmp/sage-10.2-current/local/var/lib/sage/venv-python3.11.1/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:318,
> >  in Command.run_command(self, command)
> > 314 """Run some other command: uses the 'run_command()' method of
> > 315 Distribution, which creates and finalizes the command object if
> > 316 necessary and then invokes its 'run()' method.
> > 317 """
> > --> 318 self.distribution.run_command(command)
> >
> > 

Re: [sage-devel] What's the point of GF(2, impl='ntl')?

[Vincent Delecroix]

I definitely agree about tests! There should be a generic "test suite"
that should systematically be run with these all different
implementations. It is a bit ridiculous that your example was not
caught.

On Fri, 29 Sept 2023 at 17:53, John H Palmieri  wrote:
>
> First, an error in the original message: it should have been 
> "identity_matrix(F, 1)". That doesn't make any difference in the behavior. A 
> little exploration suggests that the problem goes away if you make the 
> identity matrix sparse: the problem may be with multiplying a dense matrix 
> with a vector. I'm not sure about this, though.
>
> This is with the most recent beta, built from scratch on several different OS 
> X machines. It also happens on Sagecell. I have not yet opened an issue, 
> because there are deeper existential questions: if linear algebra over this 
> field is broken, and if there are no doctests to detect that it's broken, how 
> viable is this implementation? How long has it been broken? Why has no one 
> noticed? What is it used for? Should we keep it?
>
> I think that if someone wanted to add a new implementation of a field to Sage 
> today, we would insist on doctests verifying that it worked as a drop-in 
> replacement for the existing implementations everywhere in Sage where fields 
> get used. GF(2, impl='ntl') does not meet this standard. Someone can 
> presumably fix this one bug, but is someone willing to add all of the 
> doctests that should really be added?
>
> On Friday, September 29, 2023 at 12:32:14 AM UTC-7 Vincent Delecroix wrote:
>>
>> What is your sage version? How did you install it? Did you open an
>> issue on github?
>>
>> Best
>> Vincent
>>
>> On Tue, 26 Sept 2023 at 07:00, John H Palmieri  wrote:
>> >
>> > Setup:
>> >
>> > sage: F = GF(2, impl='ntl')
>> > sage: m_ntl = identity_matrix(1, F)
>> > sage: v_ntl = vector(F, (1,))
>> >
>> > Now consider
>> >
>> > sage: m_ntl * v_ntl
>> > sage: v_ntl * m_ntl
>> >
>> > I'm trying to multiply a 1x1 matrix by a 1-dimensional vector, in one 
>> > order or the other. Here's what happens: the first line fails with a 
>> > SignalError, and the second actually crashes Sage. If we are defining a 
>> > field that can't do linear algebra, shouldn't there be big warnings posted 
>> > somewhere? If we are defining a field like this, are there any 
>> > expectations that it should work broadly with Sage types and 
>> > constructions? I just discovered that cup products in mod 2 cohomology 
>> > don't work when "mod 2" means coefficients in GF(2, impl='ntl'), and I 
>> > don't know if I should bother trying to fix this.
>> >
>> > For what it's worth, I get the same with `GF(2, impl='givaro')`. Also for 
>> > what it's worth, explicitly converting `v_ntl` to a matrix allows the 
>> > matrix multiplication to work.
>> >
>> > I see this on two different OS X machines, one Intel and one Apple Silicon.
>> >
>> > --
>> > John
>> >
>> > --
>> > 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+...@googlegroups.com.
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/sage-devel/faeffb72-3b16-4f37-90c4-f969e4d5c017n%40googlegroups.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/378f06a5-2008-42fb-8642-32019a3a4976n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3DumacWP1W0CbyT40a9oPO6B_ejDcqc7HbZkck2Y_5kBg%40mail.gmail.com.

Re: [sage-devel] What's the point of GF(2, impl='ntl')?

[Vincent Delecroix]

What is your sage version? How did you install it? Did you open an
issue on github?

Best
Vincent

On Tue, 26 Sept 2023 at 07:00, John H Palmieri  wrote:
>
> Setup:
>
> sage: F = GF(2, impl='ntl')
> sage: m_ntl = identity_matrix(1, F)
> sage: v_ntl = vector(F, (1,))
>
> Now consider
>
> sage: m_ntl * v_ntl
> sage: v_ntl * m_ntl
>
> I'm trying to multiply a 1x1 matrix by a 1-dimensional vector, in one order 
> or the other. Here's what happens: the first line fails with a SignalError, 
> and the second actually crashes Sage. If we are defining a field that can't 
> do linear algebra, shouldn't there be big warnings posted somewhere? If we 
> are defining a field like this, are there any expectations that it should 
> work broadly with Sage types and constructions? I just discovered that cup 
> products in mod 2 cohomology don't work when "mod 2" means coefficients in 
> GF(2, impl='ntl'), and I don't know if I should bother trying to fix this.
>
> For what it's worth, I get the same with `GF(2, impl='givaro')`. Also for 
> what it's worth, explicitly converting `v_ntl` to a matrix allows the matrix 
> multiplication to work.
>
> I see this on two different OS X machines, one Intel and one Apple Silicon.
>
> --
> John
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/faeffb72-3b16-4f37-90c4-f969e4d5c017n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAm37d_yY%2B7AYbUV2dtVwXBGwE412yLGjcPi1wSCO%2BjfvA%40mail.gmail.com.

Re: [sage-devel] opinions requested on x + y behaviour for polynomials

[Vincent Delecroix]

Hi Frederic,

My opinion is that if there is a single non-ambiguous canonical
parent, then yes. In the case of polynomial rings I think that the
priority is to fix the following kind of non-commutativity in coercion
```
sage: cm = get_coercion_model()
sage: cm.common_parent(QQ['x,y'], QQ['y,x'])
Multivariate Polynomial Ring in x, y over Rational Field
sage: cm.common_parent(QQ['y,x'], QQ['x,y'])
Multivariate Polynomial Ring in y, x over Rational Field
```
This concerns also your use case,in what order will you put variables
in the resulting polynomial ring?

Best
Vincent

PS: one also need to pay attention to monomial ordering

On Sat, 26 Aug 2023 at 09:22, Frédéric Chapoton  wrote:
>
> Dear all,
>
> currently, if x and y are in two different polynomial rings, one cannot add 
> them.
>
> I propose in https://github.com/sagemath/sage/pull/36138 a sketch of changes 
> that would build a common polynomial ring by taking the union of variables. 
> This does not break too many things. Instead many doctests checking for 
> coercion failure now report coercion success. There are still a few 
> problematic things to solve, in particular about infinite polynomials rings.
>
> Please express your opinion about that change of behaviour.
>
> Frederic
>
> Question: what does magma do ?
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/130fadf1-6308-4d6b-8607-a0f6ca22d76bn%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAk0ML2SkYjKWYftdWdm27h-hzcmp4kqWR7t%2BT4Wvv6hsw%40mail.gmail.com.

Re: [sage-devel] Graph([('A','B'),(1,2)]).edges() raises weird traceback

[Vincent Delecroix]

I do not like a solution involving a m log(m) cost at initialization.
EdgesView is supposed to be O(1) at construction right?

On Thu, 6 Jul 2023 at 06:54, David Coudert  wrote:
>
> The current design choice in `EdgesView` is to sort only when asking for the 
> list of edges, that is when calling `__repr__` if `sort=True`.
> The alternative is to sort at the initialization of the object and to cache 
> the sorted list of edges in the object.
> Should we go for this alternative implementation ?
>
> On Wednesday, July 5, 2023 at 8:48:05 AM UTC+2 Vincent Delecroix wrote:
>>
>> To my mind, this is not the problem. The first command does generate a
>> warning (fine)
>>
>> sage: E = Graph([('A','B'),(1,2)]).edges()
>> :1: DeprecationWarning: parameter 'sort'
>> will be set to False by default in the future
>> See https://github.com/sagemath/sage/issues/27408 for details.
>>
>> But the EdgesView.__repr__ is buggy (bad)
>>
>> sage: E
>> ) failed:
>> TypeError: unsupported operand parent(s) for <: 'Integer Ring' 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:
>> >
>> > 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/sagemath/sage/issues/27408 for details.
>> > Graph([('A','B'),(Integer(1),Integer(2))]).edges() 
>> > ) failed: TypeError: 
>> > unsupported operand parent(s) for <: 'Integer Ring' and ''>
>> >
>> >
>> > On Tuesday, July 4, 2023 at 4:29:21 PM UTC+2 Vincent Delecroix wrote:
>> >>
>> >> https://github.com/sagemath/sage/issues/35897
>> >>
>> >> On Tue, 4 Jul 2023 at 16:25, Vincent Delecroix
>> >> <20100.d...@gmail.com> wrote:
>> >> >
>> >> > This is a bug in the __repr__ method of EdgesView. Thanks for your 
>> >> > report.
>> >> >
>> >> > On Tue, 4 Jul 2023 at 10:52, Georgi Guninski  wrote:
>> >> > >
>> >> > > Graph([('A','B'),(1,2)]).edges()
>> >> > > ) failed:
>> >> > > TypeError: unsupported operand parent(s) for <: 'Integer Ring' and
>> >> > > ''>
>> >> > >
>> >> > > I think this is related to sorting the edges.
>> >> > >
>> >> > > The following works:
>> >> > > sage: Graph([("A",1),("B",2)]).edges()
>> >> > > [(1, 'A', None), (2, 'B', None)]
>> >> > >
>> >> > > --
>> >> > > 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+...@googlegroups.com.
>> >> > > To view this discussion on the web visit 
>> >> > > https://groups.google.com/d/msgid/sage-devel/CAGUWgD9zHPdu2ifxaMOc%3DEaUN5B9A_v6RmDXMLkFLCvc-Etc0w%40mail.gmail.com.
>> >
>> > --
>> > 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+...@googlegroups.com.
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/sage-devel/1ec8c4cf-c0d5-4682-8d10-8e74d0779dfdn%40googlegroups.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/af6e1bb0-9662-4994-ba14-28ffe010e68fn%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmFM9OEo%3DC2_qv%2BCX7wuBBoJKdhzJLwwPkoeeR_w7JVAQ%40mail.gmail.com.

Re: [sage-devel] Re: Exception in `G=Graph([("A",1)]);G.faces()`

[Vincent Delecroix]

On Wed, 5 Jul 2023 at 17:51, Georgi Guninski  wrote:
>
> On Wed, Jul 5, 2023 at 4:05 PM David Coudert  wrote:
> >
> > I have opened https://github.com/sagemath/sage/issues/35902 to collect such 
> > kind of issues.
> > Please use it to share new cases.
> >
> I just reported a bug on github, though I don't like microsoft services at 
> all.

Is google any better?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3D5K22ZxY7Ea7Sjn5-udvdQD-C_4atABZxVdp75UEXvkQ%40mail.gmail.com.

Re: [sage-devel] Graph([('A','B'),(1,2)]).edges() raises weird traceback

[Vincent Delecroix]

To my mind, this is not the problem. The first command does generate a
warning (fine)

sage: E = Graph([('A','B'),(1,2)]).edges()
:1: DeprecationWarning: parameter 'sort'
will be set to False by default in the future
See https://github.com/sagemath/sage/issues/27408 for details.

But the EdgesView.__repr__ is buggy (bad)

sage: E
) failed:
TypeError: unsupported operand parent(s) for <: 'Integer Ring' 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:
>
> 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/sagemath/sage/issues/27408 for details.
> Graph([('A','B'),(Integer(1),Integer(2))]).edges() 
> ) failed: TypeError: 
> unsupported operand parent(s) for <: 'Integer Ring' and ''>
>
>
> On Tuesday, July 4, 2023 at 4:29:21 PM UTC+2 Vincent Delecroix wrote:
>>
>> https://github.com/sagemath/sage/issues/35897
>>
>> On Tue, 4 Jul 2023 at 16:25, Vincent Delecroix
>> <20100.d...@gmail.com> wrote:
>> >
>> > This is a bug in the __repr__ method of EdgesView. Thanks for your report.
>> >
>> > On Tue, 4 Jul 2023 at 10:52, Georgi Guninski  wrote:
>> > >
>> > > Graph([('A','B'),(1,2)]).edges()
>> > > ) failed:
>> > > TypeError: unsupported operand parent(s) for <: 'Integer Ring' and
>> > > ''>
>> > >
>> > > I think this is related to sorting the edges.
>> > >
>> > > The following works:
>> > > sage: Graph([("A",1),("B",2)]).edges()
>> > > [(1, 'A', None), (2, 'B', None)]
>> > >
>> > > --
>> > > 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+...@googlegroups.com.
>> > > To view this discussion on the web visit 
>> > > https://groups.google.com/d/msgid/sage-devel/CAGUWgD9zHPdu2ifxaMOc%3DEaUN5B9A_v6RmDXMLkFLCvc-Etc0w%40mail.gmail.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/1ec8c4cf-c0d5-4682-8d10-8e74d0779dfdn%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkSVhbSP7-_HT13NmkNJRdOrp%2B5Zq00p4RH9XQQ1A1Gwg%40mail.gmail.com.

Re: [sage-devel] Graph([('A','B'),(1,2)]).edges() raises weird traceback

[Vincent Delecroix]

https://github.com/sagemath/sage/issues/35897

On Tue, 4 Jul 2023 at 16:25, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> This is a bug in the __repr__ method of EdgesView. Thanks for your report.
>
> On Tue, 4 Jul 2023 at 10:52, Georgi Guninski  wrote:
> >
> > Graph([('A','B'),(1,2)]).edges()
> > ) failed:
> > TypeError: unsupported operand parent(s) for <: 'Integer Ring' and
> > ''>
> >
> > I think this is related to sorting the edges.
> >
> > The following works:
> > sage: Graph([("A",1),("B",2)]).edges()
> > [(1, 'A', None), (2, 'B', None)]
> >
> > --
> > 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.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-devel/CAGUWgD9zHPdu2ifxaMOc%3DEaUN5B9A_v6RmDXMLkFLCvc-Etc0w%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3D2hNRdkCZq%3DwmZL1cfAR2NikEquagmZTZVf2ZN%2BoPFjA%40mail.gmail.com.

Re: [sage-devel] Graph([('A','B'),(1,2)]).edges() raises weird traceback

[Vincent Delecroix]

This is a bug in the __repr__ method of EdgesView. Thanks for your report.

On Tue, 4 Jul 2023 at 10:52, Georgi Guninski  wrote:
>
> Graph([('A','B'),(1,2)]).edges()
> ) failed:
> TypeError: unsupported operand parent(s) for <: 'Integer Ring' and
> ''>
>
> I think this is related to sorting the edges.
>
> The following works:
> sage: Graph([("A",1),("B",2)]).edges()
> [(1, 'A', None), (2, 'B', None)]
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAGUWgD9zHPdu2ifxaMOc%3DEaUN5B9A_v6RmDXMLkFLCvc-Etc0w%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmFrFoNy3Q6omb6NfS%3D6UBaQpk7u3tGqL%2BYz0aExUgpbQ%40mail.gmail.com.

Re: [sage-devel] Isomorphic multi digraphs have distinct number of spanning trees, bug?

[Vincent Delecroix]

You could also check equality for all vertices with

sage: ans, isom = G1.is_isomorphic(G2, certificate=True)
sage: all(G1.spanning_trees_count(u) ==
G2.spanning_trees_count(isom[u]) for u in G1.vertices(sort=False))
True

On Sun, 18 Jun 2023 at 10:09, Dima Pasechnik  wrote:
>
> It could be an integer overflow somewhere in the determinant
> computation, as the numbers are very, very big.
>
> By default, determinants are computed by flint, so it can be a bug there.
> You can modify the code of spanning_trees_count() to allow passing of
> the algorithm to compute determinant, and see if you can get it right.
>
> HTH
> Dima
>
> On Sun, Jun 18, 2023 at 8:49 AM Georgi Guninski  wrote:
> >
> > On Sun, Jun 18, 2023 at 10:16 AM Emmanuel Briand
> >  wrote:
> > >
> > > Have you taken into account the following?
> > >
> > > ignature:  G1.spanning_trees_count(root_vertex=None)
> > > Docstring:
> > >Return the number of spanning trees in a graph.
> > >
> > >In the case of a digraph, counts the number of spanning out-trees
> > >rooted in "root_vertex".  Default is to set first vertex as root.
> > >
> > >
> >
> > Thanks, I should have RTFM.
> >
> > This still doesn't work for me:
> >
> > sage: 
> > G1.spanning_trees_count(root_vertex=None),G2.spanning_trees_count(root_ver
> > : tex=None)
> > (27202601182632270746156805986464038912000,
> >  40803901773948406119235208979696058368000)
> >
> >
> > Is it rigorous to set c1=G1.spanning_trees_count()
> > and then do:
> >
> > sage: c1=G1.spanning_trees_count()
> > sage: for i in range(G1.order()):
> > : c2=G2.spanning_trees_count(i)
> > : if c2==c1:  print(i)
> > :
> > 6
> >
> > I expect for isomorphic multi digraphs the loop to find equal c1,c2?
> >
> > --
> > 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.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-devel/CAGUWgD_Zkf7g2py2PxWkYA4PqBOW6Ws%2BW31JtsQF2nmO6JE9tg%40mail.gmail.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq2%2B_eejUwRr9M5%3DB%3Ddn36XMvU1hRbEQ_wwGu2obdWf2Kw%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmK1t%3DHrcRG4QeeitLsU88XMuuRsY_w0sMG-iC6zQFC3g%40mail.gmail.com.

Re: [sage-devel] Isomorphic multi digraphs have distinct number of spanning trees, bug?

[Vincent Delecroix]

sage: G1.spanning_trees_count(root_vertex=0)
27202601182632270746156805986464038912000
sage: G2.spanning_trees_count(root_vertex=6)
27202601182632270746156805986464038912000

On Sun, 18 Jun 2023 at 09:49, Georgi Guninski  wrote:
>
> On Sun, Jun 18, 2023 at 10:16 AM Emmanuel Briand
>  wrote:
> >
> > Have you taken into account the following?
> >
> > ignature:  G1.spanning_trees_count(root_vertex=None)
> > Docstring:
> >Return the number of spanning trees in a graph.
> >
> >In the case of a digraph, counts the number of spanning out-trees
> >rooted in "root_vertex".  Default is to set first vertex as root.
> >
> >
>
> Thanks, I should have RTFM.
>
> This still doesn't work for me:
>
> sage: 
> G1.spanning_trees_count(root_vertex=None),G2.spanning_trees_count(root_ver
> : tex=None)
> (27202601182632270746156805986464038912000,
>  40803901773948406119235208979696058368000)
>
>
> Is it rigorous to set c1=G1.spanning_trees_count()
> and then do:
>
> sage: c1=G1.spanning_trees_count()
> sage: for i in range(G1.order()):
> : c2=G2.spanning_trees_count(i)
> : if c2==c1:  print(i)
> :
> 6
>
> I expect for isomorphic multi digraphs the loop to find equal c1,c2?
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAGUWgD_Zkf7g2py2PxWkYA4PqBOW6Ws%2BW31JtsQF2nmO6JE9tg%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAntJP%3DXemn%2BAmnYt6BfRfq8GujWQYZSpAjPyA81oOHxEw%40mail.gmail.com.

Re: [sage-devel] compiling sage without documentation

[Vincent Delecroix]

Thanks Dima. Is there a way I can figure out by myself which info is up to date?

On Thu, 16 Mar 2023 at 11:30, Dima Pasechnik  wrote:
>
> On Thu, Mar 16, 2023 at 10:00 AM Vincent Delecroix
> <20100.delecr...@gmail.com> wrote:
> >
> > Dear all,
> >
> > I would like to compile sage without the documentation. According to
> > ./configure --help I supposed the following would just work
> >
> > ./configure --with-sage_docbuild=no --with-pplpy_doc=no
> > --with-sagemath_doc_html=no --with-sagemath_doc_pdf=no
>
> this is outdated: have a look at
> % ./configure -h | grep doc
>   --infodir=DIR   info documentation [DATAROOTDIR/info]
>   --mandir=DIRman documentation [DATAROOTDIR/man]
>   --docdir=DIRdocumentation root [DATAROOTDIR/doc/sage]
>   --htmldir=DIR   html documentation [DOCDIR]
>   --dvidir=DIRdvi documentation [DOCDIR]
>   --pdfdir=DIRpdf documentation [DOCDIR]
>   --psdir=DIR ps documentation [DOCDIR]
>   --disable-doc   disable build of the Sage documentation and packages
>   for manipulating documents based on data
>   documentation reader
>   --enable-pandoc_attributes={no|if_installed (default)|yes}
>   enable build and use of the optional package
> pandoc_attributes: A parser
>   and generator for pandoc block attributes
>   * package info: ./sage -info pandoc_attributes
>   --disable-pandoc_attributes
>   same as --enable-pandoc_attributes=no
>   --enable-sagemath_doc_pdf={no|if_installed (default)|yes}
>   enable build and use of the optional package
> sagemath_doc_pdf: SageMath
>   documentation in PDF format
>   * package info: ./sage -info sagemath_doc_pdf
>   --disable-sagemath_doc_pdf
>   same as --enable-sagemath_doc_pdf=no
>   Mathematics Software: IPython kernel, Sage
> preparser, doctester
>   --with-system-pandoc={no|yes (default)|force (exit with an error if
> no usable version is found)}
>   detect and use an existing system pandoc
>
> So it seems that you'd like  --disable-doc  option.
>
> >
> > But I got
> >
> > configure: WARNING: unrecognized options: --with-sage-docbuild,
> > --with-pplpy-doc, --with-sagemath-doc-html, --with-sagemath-doc-pdf
> >
> > Best
> > Vincent
> >
> > --
> > 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.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-devel/CAGEwAAnwvcG%3D4Ntk4%3DMrA2G3rj4xhfCOL24pHC%3DMjJJPJ7_w%3DQ%40mail.gmail.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq2Ce2O_k9MhfxCA_DTBDoJ%2BPojAUps8L%2BqifEHY7HjJng%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkKOK3juDU%3D5OM607ehr2-wZX%3DEzdVWfwrWJ5s_rWwNNw%40mail.gmail.com.

[sage-devel] compiling sage without documentation

[Vincent Delecroix]

Dear all,

I would like to compile sage without the documentation. According to
./configure --help I supposed the following would just work

./configure --with-sage_docbuild=no --with-pplpy_doc=no
--with-sagemath_doc_html=no --with-sagemath_doc_pdf=no

But I got

configure: WARNING: unrecognized options: --with-sage-docbuild,
--with-pplpy-doc, --with-sagemath-doc-html, --with-sagemath-doc-pdf

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAnwvcG%3D4Ntk4%3DMrA2G3rj4xhfCOL24pHC%3DMjJJPJ7_w%3DQ%40mail.gmail.com.

Re: [sage-devel] weird commits on top of develop

[Vincent Delecroix]

In other words, everytime you got confused we will have a develop
branch not aligned with the most recent tag and a bunch of extra
commits cancelling each other?

On Sun, 26 Feb 2023 at 16:46, Dima Pasechnik  wrote:
>
> sometimes Volker misses things which make CI break, and such a release is 
> pretty much useless, in the sense that you can't gauge anything from the CI 
> results on PRs made on top of it. Or an important CI or other infrastructure 
> improvement doesn't make it into the release.
>
> In previous release cycles we few times pushed necessary changes in develop 
> to fix such things.
> We do have OK from Volker for these fixes.
>
> This time I got confused and pushed a totally irrelevant change (which did 
> not break develop, it just had no effect on anything at all).
>
> Dima
>
>
>
>
> On Sun, 26 Feb 2023, 10:19 Vincent Delecroix, <20100.delecr...@gmail.com> 
> wrote:
>>
>> I do not understand why develop isn't protected against anybody but
>> the release manager pushes.
>>
>> On Sun, 26 Feb 2023 at 11:16, Dima Pasechnik  wrote:
>> >
>> > it was a mistake on my side - I thought develop branch was broken, but it 
>> > was not.
>> >
>> > On Sun, 26 Feb 2023, 10:13 Vincent Delecroix, <20100.delecr...@gmail.com> 
>> > wrote:
>> >>
>> >> Hello,
>> >>
>> >> Why do we have commits on top of develop after the release commits? Namely
>> >>
>> >> commit 52a81cbd161ef4d5895325657c88a68590ea1d3b
>> >> Author: Dima Pasechnik 
>> >> Date:   Fri Feb 24 21:15:42 2023 +
>> >>
>> >> Revert "add missing # optional - gap3"
>> >>
>> >> This reverts commit c017a6a3d68f0aca8cb63ceba52fe451a64881a3.
>> >>
>> >> commit c017a6a3d68f0aca8cb63ceba52fe451a64881a3
>> >> Author: Dima Pasechnik 
>> >> Date:   Fri Feb 24 11:57:32 2023 +
>> >>
>> >> add missing # optional - gap3
>> >>
>> >> to let CI pass
>> >>
>> >> Best
>> >> Vincent
>> >>
>> >> --
>> >> 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.
>> >> To view this discussion on the web visit 
>> >> https://groups.google.com/d/msgid/sage-devel/CAGEwAAkF50jNxVth6io%2BCErWu9mWFW4L2D%2BERqQVcNf7aPjp1A%40mail.gmail.com.
>> >
>> > --
>> > 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.
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/sage-devel/CAAWYfq0XTpPcxuKuE11ChKpx0jcAjsxGRVsrD%2BLDeQO-X4RxnQ%40mail.gmail.com.
>>
>> --
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3Dv8cvjs8wz172f3KtwkeYubB4BEx9NKLWS_XD7d28jJg%40mail.gmail.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0U9GvqhM6qy8katYmoXE-xeGW3z41moGcicSucVzHwpw%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAk-ork4G3BXoC%3DkVOQSSQ%3D0Hb86sxeMw7cB2vbN%2BJ3x6g%40mail.gmail.com.

Re: [sage-devel] weird commits on top of develop

[Vincent Delecroix]

I do not understand why develop isn't protected against anybody but
the release manager pushes.

On Sun, 26 Feb 2023 at 11:16, Dima Pasechnik  wrote:
>
> it was a mistake on my side - I thought develop branch was broken, but it was 
> not.
>
> On Sun, 26 Feb 2023, 10:13 Vincent Delecroix, <20100.delecr...@gmail.com> 
> wrote:
>>
>> Hello,
>>
>> Why do we have commits on top of develop after the release commits? Namely
>>
>> commit 52a81cbd161ef4d5895325657c88a68590ea1d3b
>> Author: Dima Pasechnik 
>> Date:   Fri Feb 24 21:15:42 2023 +
>>
>> Revert "add missing # optional - gap3"
>>
>> This reverts commit c017a6a3d68f0aca8cb63ceba52fe451a64881a3.
>>
>> commit c017a6a3d68f0aca8cb63ceba52fe451a64881a3
>> Author: Dima Pasechnik 
>> Date:   Fri Feb 24 11:57:32 2023 +
>>
>> add missing # optional - gap3
>>
>> to let CI pass
>>
>> Best
>> Vincent
>>
>> --
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/CAGEwAAkF50jNxVth6io%2BCErWu9mWFW4L2D%2BERqQVcNf7aPjp1A%40mail.gmail.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0XTpPcxuKuE11ChKpx0jcAjsxGRVsrD%2BLDeQO-X4RxnQ%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3Dv8cvjs8wz172f3KtwkeYubB4BEx9NKLWS_XD7d28jJg%40mail.gmail.com.

[sage-devel] weird commits on top of develop

[Vincent Delecroix]

Hello,

Why do we have commits on top of develop after the release commits? Namely

commit 52a81cbd161ef4d5895325657c88a68590ea1d3b
Author: Dima Pasechnik 
Date:   Fri Feb 24 21:15:42 2023 +

Revert "add missing # optional - gap3"

This reverts commit c017a6a3d68f0aca8cb63ceba52fe451a64881a3.

commit c017a6a3d68f0aca8cb63ceba52fe451a64881a3
Author: Dima Pasechnik 
Date:   Fri Feb 24 11:57:32 2023 +

add missing # optional - gap3

to let CI pass

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkF50jNxVth6io%2BCErWu9mWFW4L2D%2BERqQVcNf7aPjp1A%40mail.gmail.com.

Re: [sage-devel] Procedure to be a member of sage github organization

[Vincent Delecroix]

I think that the needs_review positive_review tags do not fit well in
the github workflow. These have been kept to mimic the trac workflow
but are annoying. I support Edgar suggestion that the "needs review
tag" should be replaced by "not a draft" status. Similarly, the
"positive review tag" would better be replaced by something like
"approved by a developer".

On Sat, 25 Feb 2023 at 20:38, Edgar Costa  wrote:
>
> Most likely not the status quo at the moment, but if a PR is not ready to be 
> reviewed should be marked as a draft, which the author can do without any 
> special permissions.
> Otherwise, I would assume the PR is ready to be reviewed.
>
> On Fri, Feb 24, 2023 at 9:43 PM Trevor Karn  wrote:
>>
>> How do new developers tag their PR as "needs review" without having triage 
>> access?
>>
>> On Thursday, February 23, 2023 at 1:37:07 AM UTC-6 David Roe wrote:
>>>
>>> As a first proposal: once you have a PR accepted then you're added to the 
>>> sagemath organization.  I'm not sure exactly what the cutoff should be for 
>>> being added to triage (which gives the capability of changing labels, 
>>> closing and assigning issues and PRs, requesting PR reviews, applying 
>>> milestones and marking as duplicate.  I'm fine with giving these 
>>> permissions to people after their first PR is merged, but some might argue 
>>> for more of a history with contributors.
>>>
>>> Julian and I had talked about writing a bot to handle these permissions, 
>>> but haven't gotten around to it yet.
>>> David
>>>
>>> On Thu, Feb 23, 2023 at 5:33 AM Kwankyu Lee  wrote:

 Hi,

 We are getting PRs from non-member contributors.

 What is the procedure or the condition to be invited for membership?

 --
 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+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/sage-devel/9eae5420-6b43-440e-b36d-d30c3b23421bn%40googlegroups.com.
>>
>> --
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/1ee1ac47-44bb-4c0d-a8df-132fc4cdc86an%40googlegroups.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x7fGhOaaHwy3DEyfC%3DomQYV1c8JWCkanEcCRUdo7bFCHw%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmV%3DSuknLWzjkKTKyihS2exrrd-87vsMKrFChD5N7W4oQ%40mail.gmail.com.

Re: [sage-devel] online talk about the github workflow

[Vincent Delecroix]

The video should be available at
https://webconf.u-bordeaux.fr/b/vin-g33-6qy at the bottom of the page.

Vincent

https://visio.u-bordeaux.fr/playback/presentation/2.0/playback.html?meetingId=887e0bfc02a9a556a1ea79a2c1d59e3cb7717460-1675700189259

On 06/02/2023, Matthias Koeppe  wrote:
> The notes of my talk are available at https://hackmd.io/@mkoeppe/HyibcDT2j
>
>
> On Friday, February 3, 2023 at 8:00:29 AM UTC-8 GMS wrote:
>
>>
>> As I have said to Vincent, I can take care of making the video.
>> I shall submit it to Matthias before making it available for publication.
>>
>> Guillermo
>>
>> On Fri, 3 Feb 2023 at 15:53, Matthias Koeppe 
>> wrote:
>>
>>> Recording my talk is, of course, fine with me.
>>>
>>> On Friday, February 3, 2023 at 1:38:33 AM UTC-8 vdelecroix wrote:
>>>
 This could be recorded (if Matthias agree) and available on the BBB
 website. I do not know how to make a proper video out of the BBB
 recording and will not spend anytime on it. Anybody with this
 knowledge is welcome to make that happen.

 Best
 Vincent

 On Thu, 2 Feb 2023 at 22:36, François Bissey 
 wrote:
 >
 > On 3/02/23 10:30, David Joyner wrote:
 > > Hi Vincent:
 > > Will this be recorded and posted on youtube,
 > > or something like that?
 > > - David
 >
 > I am seconding that request. That time is 5:30am in my time zone.
 >
 > François (NZST=UTC+13 at this time of the year)

>>>
>>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/3c2bacc4-d717-484f-845a-1735b5977d9en%40googlegroups.com.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3DkuvScMQ-GG_LZ6W5i-j%3D6yBgFKwyD-4yGB%3DtjafDLTw%40mail.gmail.com.

Re: [sage-devel] online talk about the github workflow

[Vincent Delecroix]

Talk will start in about 10min from now at

 https://webconf.u-bordeaux.fr/b/vin-g33-6qy

On 03/02/2023, Matthias Koeppe  wrote:
> Recording my talk is, of course, fine with me.
>
> On Friday, February 3, 2023 at 1:38:33 AM UTC-8 vdelecroix wrote:
>
>> This could be recorded (if Matthias agree) and available on the BBB
>> website. I do not know how to make a proper video out of the BBB
>> recording and will not spend anytime on it. Anybody with this
>> knowledge is welcome to make that happen.
>>
>> Best
>> Vincent
>>
>> On Thu, 2 Feb 2023 at 22:36, François Bissey  wrote:
>> >
>> > On 3/02/23 10:30, David Joyner wrote:
>> > > Hi Vincent:
>> > > Will this be recorded and posted on youtube,
>> > > or something like that?
>> > > - David
>> > >
>> >
>> > I am seconding that request. That time is 5:30am in my time zone.
>> >
>> > François (NZST=UTC+13 at this time of the year)
>> >
>> > --
>> > 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+...@googlegroups.com.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/31ef3b4b-4183-4de8-dc0e-c02d9939dce8%40gmail.com
>> .
>>
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/de74d772-30b0-4e0a-8941-acfe142859dbn%40googlegroups.com.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3DNQyv_4ijU%2BRTdFHhX1p%3DN2kzf-8iEi2q1DM-SP6Z%2BaA%40mail.gmail.com.

Re: [sage-devel] online talk about the github workflow

[Vincent Delecroix]

This could be recorded (if Matthias agree) and available on the BBB
website. I do not know how to make a proper video out of the BBB
recording and will not spend anytime on it. Anybody with this
knowledge is welcome to make that happen.

Best
Vincent

On Thu, 2 Feb 2023 at 22:36, François Bissey  wrote:
>
> On 3/02/23 10:30, David Joyner wrote:
> > Hi Vincent:
> > Will this be recorded and posted on youtube,
> > or something like that?
> > - David
> >
>
> I am seconding that request. That time is 5:30am in my time zone.
>
> François (NZST=UTC+13 at this time of the year)
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/31ef3b4b-4183-4de8-dc0e-c02d9939dce8%40gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAnM_J%3DAXeB6iFsODr7FnB4NEeo88aABY7GEdHyBy%2Bf-YQ%40mail.gmail.com.

[sage-devel] wiki access

[Vincent Delecroix]

Dear all,

It seems that it is not possible anymore to log in for editing the
SageMath wiki at https://wiki.sagemath.org/. This is the tool we were
planning to use for sage days 117 starting on Monday. Does anyone know
what happened?

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkijkiGjsBaGrAbPOwJ8_BOzf7dfG2zW-c8gScD-7rQow%40mail.gmail.com.

[sage-devel] online talk about the github workflow

[Vincent Delecroix]

Dear all,

As part of the sage days 117 (https://wiki.sagemath.org/days117)
Matthias Köppe will give on online talk about the new github workflow
for SageMath development. It will happen on Monday Feb 6th at 17:30
CET (= UTC+1). For those who want to join, it will happen on

https://webconf.u-bordeaux.fr/b/vin-g33-6qy

Best wishes,
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmfW7JCxos%3DO7-Ds_pnd7Z9e_o22qsShqiBOMFhu8ngOw%40mail.gmail.com.

[sage-devel] Is R on the system needed to compile sage?

[Vincent Delecroix]

Hello,

In a fresh cloned environment (9.8.beta7) I tried to build sage and it
ended with the failure of r-none (as it is a dummy package). It
appears that r is not installed on my system. Though is it a
requirement? Nothing in configure warned me so.

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3Dr3z1gLacLkR9%3DbKPn93TMnqdnFeue7Sm4Q83xM2FO%3Dg%40mail.gmail.com.

Re: [sage-devel] sage is slowding down PARI/GP by factor x2 (roughly)

[Vincent Delecroix]

On Thu, 15 Dec 2022 at 01:42, Dima Pasechnik  wrote:
>
>
>
> On Wed, 14 Dec 2022, 21:06 Vincent Delecroix, <20100.delecr...@gmail.com> 
> wrote:
>>
>> Note that in #34850 I execute the very same command, namely
>> pari("quadclassunit(1 - 2^100)"), once in a fresh python session and
>> once preceeded by "import sage.all". So whatever linking and whatever
>> threading option has been used to compile pari these are the same for
>> both executions.
>
>
>
> oops, sorry, I was too quick. I guess here it is a change in memory layout 
> that causes the slowdown.

I don't quite believe it. The PARI/GP stack is allocated before the
`import sage.all` and is not affected by this call. What kind of
change in memory could cause the slowdown here?

> You also mention that it might be ipython - can this be tested by building 
> Sage without it?

I meant the base kernel from ipython that would be responsible for the
slowdown in pari_jupyter. That is just a supposition.

>> In particular, I do not see any relations between
>> #31572 (which tests two pari versions) and #34850 (which tests a
>> single pari version). Could you either read carefully the description
>> of #34850 or explain the link between #31572 and #34850 if any?
>>
>> On Wed, 14 Dec 2022 at 21:58, Dima Pasechnik  wrote:
>> >
>> > Does #31572 actually mean that pari threads are more harmful than useful?
>> > If so, perhaps, we can create a special multithreaded, differerently
>> > named, libpari for giac, and
>> > build our "main" libpari single-threaded?
>> >
>> > Dima
>> >
>> > On Wed, Dec 14, 2022 at 8:38 PM David Roe  wrote:
>> > >
>> > > It could be related to #31572, which notes a dramatic speed regression 
>> > > based on pari being compiled with pthread.
>> > > David
>> > >
>> > > On Wed, Dec 14, 2022 at 3:30 PM Dima Pasechnik  wrote:
>> > >>
>> > >> I vaguely recall something about the way gp is built, without linking 
>> > >> libpari dynamically, and something about gp getting slower if built 
>> > >> with threads.
>> > >>
>> > >> So, probably, more info is needed on how exactly your comparisons are 
>> > >> done, in regard of using, or not, threads, and dynamic linking.
>> > >>
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> On Wed, 14 Dec 2022, 20:23 Vincent Delecroix, 
>> > >> <20100.delecr...@gmail.com> wrote:
>> > >>>
>> > >>> Dear all,
>> > >>>
>> > >>> Some strange phenomenon makes execution of PARI/GP up to twice slower
>> > >>> when ran inside a Python process compared to its execution in GP.
>> > >>> Though this is not systematic, in a fresh python environment timing
>> > >>> are comparable with GP.
>> > >>>
>> > >>> The slowdown has been first observed in the context of pari_jupyter
>> > >>> [1] and then with cypari2 when sage.all is loaded [2]. There is a
>> > >>> short code snippet in the description of [2] that you can try on your
>> > >>> own sage version (must be ran with "sage -python" and not "sage").
>> > >>>
>> > >>> Any idea on what could be the source of the slowdown or some profiling
>> > >>> advices would be very welcome.
>> > >>>
>> > >>> [1] https://github.com/sagemath/pari-jupyter/issues/27
>> > >>> [2] https://trac.sagemath.org/ticket/34850
>> > >>>
>> > >>> Best
>> > >>> Vincent
>> > >>>
>> > >>> --
>> > >>> 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.
>> > >>> To view this discussion on the web visit 
>> > >>> https://groups.google.com/d/msgid/sage-devel/CAGEwAAm_%2BVfg%3D6po8-7B4eb7kW2UT%3DHjvXaR7yfUOxL930HhQQ%40mail.gmail.com.
>> > >>
>> > >> --
>> > >> You received this message because you are subscribed to the Google 
>> > >> Groups "sage-devel" group.
>> > >> To unsubscribe from this group and 

Re: [sage-devel] sage is slowding down PARI/GP by factor x2 (roughly)

[Vincent Delecroix]

Note that in #34850 I execute the very same command, namely
pari("quadclassunit(1 - 2^100)"), once in a fresh python session and
once preceeded by "import sage.all". So whatever linking and whatever
threading option has been used to compile pari these are the same for
both executions. In particular, I do not see any relations between
#31572 (which tests two pari versions) and #34850 (which tests a
single pari version). Could you either read carefully the description
of #34850 or explain the link between #31572 and #34850 if any?

On Wed, 14 Dec 2022 at 21:58, Dima Pasechnik  wrote:
>
> Does #31572 actually mean that pari threads are more harmful than useful?
> If so, perhaps, we can create a special multithreaded, differerently
> named, libpari for giac, and
> build our "main" libpari single-threaded?
>
> Dima
>
> On Wed, Dec 14, 2022 at 8:38 PM David Roe  wrote:
> >
> > It could be related to #31572, which notes a dramatic speed regression 
> > based on pari being compiled with pthread.
> > David
> >
> > On Wed, Dec 14, 2022 at 3:30 PM Dima Pasechnik  wrote:
> >>
> >> I vaguely recall something about the way gp is built, without linking 
> >> libpari dynamically, and something about gp getting slower if built with 
> >> threads.
> >>
> >> So, probably, more info is needed on how exactly your comparisons are 
> >> done, in regard of using, or not, threads, and dynamic linking.
> >>
> >>
> >>
> >>
> >>
> >> On Wed, 14 Dec 2022, 20:23 Vincent Delecroix, <20100.delecr...@gmail.com> 
> >> wrote:
> >>>
> >>> Dear all,
> >>>
> >>> Some strange phenomenon makes execution of PARI/GP up to twice slower
> >>> when ran inside a Python process compared to its execution in GP.
> >>> Though this is not systematic, in a fresh python environment timing
> >>> are comparable with GP.
> >>>
> >>> The slowdown has been first observed in the context of pari_jupyter
> >>> [1] and then with cypari2 when sage.all is loaded [2]. There is a
> >>> short code snippet in the description of [2] that you can try on your
> >>> own sage version (must be ran with "sage -python" and not "sage").
> >>>
> >>> Any idea on what could be the source of the slowdown or some profiling
> >>> advices would be very welcome.
> >>>
> >>> [1] https://github.com/sagemath/pari-jupyter/issues/27
> >>> [2] https://trac.sagemath.org/ticket/34850
> >>>
> >>> Best
> >>> Vincent
> >>>
> >>> --
> >>> 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.
> >>> To view this discussion on the web visit 
> >>> https://groups.google.com/d/msgid/sage-devel/CAGEwAAm_%2BVfg%3D6po8-7B4eb7kW2UT%3DHjvXaR7yfUOxL930HhQQ%40mail.gmail.com.
> >>
> >> --
> >> 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.
> >> To view this discussion on the web visit 
> >> https://groups.google.com/d/msgid/sage-devel/CAAWYfq2yJEvXbRa8znksXtDm%2B-hkXN_EVpwN09X4tb8EY-0-kA%40mail.gmail.com.
> >
> > --
> > 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.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-devel/CAChs6_mqWOpnHAe4-cYTxg63y5ri4vFuJxZRasMUzsEMYzTNAQ%40mail.gmail.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq0dH8%3DTp1z_owfAbCw-ED_W%3DHjuh0NQp%2B9MUatapfxKXw%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmj4FkYzJC07v80S%3DqU%3DVOH8vtysU%3Dg5tOs10-qV8Sqxg%40mail.gmail.com.

[sage-devel] sage is slowding down PARI/GP by factor x2 (roughly)

[Vincent Delecroix]

Dear all,

Some strange phenomenon makes execution of PARI/GP up to twice slower
when ran inside a Python process compared to its execution in GP.
Though this is not systematic, in a fresh python environment timing
are comparable with GP.

The slowdown has been first observed in the context of pari_jupyter
[1] and then with cypari2 when sage.all is loaded [2]. There is a
short code snippet in the description of [2] that you can try on your
own sage version (must be ran with "sage -python" and not "sage").

Any idea on what could be the source of the slowdown or some profiling
advices would be very welcome.

[1] https://github.com/sagemath/pari-jupyter/issues/27
[2] https://trac.sagemath.org/ticket/34850

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAm_%2BVfg%3D6po8-7B4eb7kW2UT%3DHjvXaR7yfUOxL930HhQQ%40mail.gmail.com.

Re: [sage-devel] Re: sagelib fails to build (9.8.beta5)

[Vincent Delecroix]

I managed to build (though doc-build failed). Thanks.

On Wed, 14 Dec 2022 at 19:53, Matthias Koeppe  wrote:
>
> No, you need to apply it to the source tree using "patch -p1"
>
> On Wednesday, December 14, 2022 at 5:55:04 AM UTC-8 vdelecroix wrote:
>>
>> In order to build, is it fine to just add this patch to
>> `SAGE_DIR/build/pkg/sagelib/patches/`?
>>
>> On Wed, 14 Dec 2022 at 14:50, Antonio Rojas  wrote:
>> >
>> > That's the singular 4.3.1.p3 update. The patch [1] fixes the build, but 
>> > there are some regressions in the asymptotics ring that need looked into.
>> >
>> > [1] 
>> > https://github.com/archlinux/svntogit-community/blob/packages/sagemath/trunk/sagemath-singular-4.3.1.p3.patch
>> >
>> > El miércoles, 14 de diciembre de 2022 a las 14:11:05 UTC+1, vdelecroix 
>> > escribió:
>> >>
>> >> Hello,
>> >>
>> >> Building sage 9.8.beta5 on archlinux went fine up to sagelib which
>> >> complains that setuptools is not there (see attached config and logs).
>> >> Dependency issue?
>> >>
>> >> Best
>> >> Vincent
>> >
>> > --
>> > 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+...@googlegroups.com.
>> > To view this discussion on the web visit 
>> > https://groups.google.com/d/msgid/sage-devel/71eb3f31-0b42-4945-bff9-38bb3279d5f9n%40googlegroups.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/13d77057-bd65-4c7e-96c0-4c6af75b7156n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3DOgyx2V6g_mV7Rh7kLfM3hDyHRB7exK0ZVo1UnAZ1Hig%40mail.gmail.com.

Re: [sage-devel] Re: sagelib fails to build (9.8.beta5)

[Vincent Delecroix]

In order to build, is it fine to just add this patch to
`SAGE_DIR/build/pkg/sagelib/patches/`?

On Wed, 14 Dec 2022 at 14:50, Antonio Rojas  wrote:
>
> That's the singular 4.3.1.p3 update. The patch [1] fixes the build, but there 
> are some regressions in the asymptotics ring that need looked into.
>
> [1]  
> https://github.com/archlinux/svntogit-community/blob/packages/sagemath/trunk/sagemath-singular-4.3.1.p3.patch
>
> El miércoles, 14 de diciembre de 2022 a las 14:11:05 UTC+1, vdelecroix 
> escribió:
>>
>> Hello,
>>
>> Building sage 9.8.beta5 on archlinux went fine up to sagelib which
>> complains that setuptools is not there (see attached config and logs).
>> Dependency issue?
>>
>> Best
>> Vincent
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/71eb3f31-0b42-4945-bff9-38bb3279d5f9n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3D_kmc6XvwM42RuKKJd07Pwd3Z1bPm%3DeMfEoz51-Lcj%2Bg%40mail.gmail.com.

[sage-devel] about cypari2 development amd maintenance on github

[Vincent Delecroix]

Dear all,

I am one of the maintainer of cypari2. Contrarily to Jeroen and Luca
who left, I am not a number theorist and not a specialist of PARI/GP.
I took over the maintainance responsability because it felt like a
good thing for the math community and because PARI development happens
in a nearby lab and Bill Allombert is constantly helping.

I had other tasks to do these days and was not very pro-active. Some
members of sagemath, though not registered as sagemath/cypari2 admin,
decided to start integrating merge requests even though these merge
requests were not adequate (eg version bump inside a merge request and
code that depended on a development branch of cysignals). It took me a
lot of headache to rewrite git history and end up with a clean
release. I am very frustrated that it took me a full day rather than
an hour to finalize this release. Moreover, the forced push to the
master branch is not nice to the contributors of cypari2.

Do you have suggestion on how such things could be avoided with
cypari2 being on github under the sagemath group?

Best regards,
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmW647Lt_83dH_0bA82no663O%3DzU_rdZ9vi8sox_4q8Ew%40mail.gmail.com.

[sage-devel] cypari2 release 2.1.3

[Vincent Delecroix]

Dear all,

There is a new release of cypari2 now on PyPI

https://pypi.org/project/cypari2/2.1.3/

Thanks to the help of Isuru Fernando, Jerry James, Jonathan Kliem and
Gonzalo Tornaría cypari2 supports the most recent Python and PARI
versions.

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmt4wsVi1yThW7XUcr5QnSr6dh3HM2yyBG2S1ZKUPzYVA%40mail.gmail.com.

Re: [sage-devel] Re: Democratic issue: rushing decisions

[Vincent Delecroix]

Dear all,

I do not interpret Thierry message as an attempt to change the issue
of the vote. Most of the answers focused on this particular point and
hence look completely off topic to me. More dramatically they are also
very rude in that they try to discredit what Thierry attempted to
share. I also felt a lot of violence during the discussion that
preceded the vote and it does continue right now. The problem is about
the form and not about the issue of the decision.

Best,
Vincent

On Wed, 5 Oct 2022 at 19:19, David Roe  wrote:
>
> I will also note that the final vote in favor of moving to github was 46 to 8 
> in favor.  Another few weeks of discussion, on top of the substantial amount 
> of time spent over the last few months (in fact, over the last decade), is 
> unlikely to have changed the outcome.
> David
>
> On Wed, Oct 5, 2022 at 12:51 PM Matthias Koeppe  
> wrote:
>>
>> On Wednesday, October 5, 2022 at 3:11:12 AM UTC-7 Thierry 
>> (sage-googlesucks@xxx) wrote:
>>>
>>> several developers asked for delays [...]
>>> [1,2,3,4,5,6].
>>
>>
>> This is a misrepresentation of most of the 6 cited messages. I'll just point 
>> out one specifically:
>>
>>>
>>>
>>> [3] Vincent : "For me the discussion in this thread is very premature"
>>> https://groups.google.com/g/sage-devel/c/ayOL8_bzOfk/m/ZTXx_speBwAJ
>>
>>
>> This message from Vincent dates Sep 10, which *prompted* our efforts to 
>> write the detailed
>> transition guide, work out many details etc. over the following week.
>>
>>
>>
>> --
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/6ffb834f-3300-43c6-be46-db35ec4000a6n%40googlegroups.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAChs6_nBRxsymmF4t8aL2ebpyNjU7WfS7F3%3DBTCTjco%2B815rQA%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3Duph8RtToae1gnO2Or5BJ1AO%2Bod%2B5z0hyYpGBO4HO38g%40mail.gmail.com.

Re: [sage-devel] is there a convention for _bool_ was: is it intentional that prod does not stop when it hits 0?

[Vincent Delecroix]

You are right of course (my bad): bool(expr) could be considered as
being True according to these specifications (and anyway "True" is
always a good answer). Though these are specifications for SR and does
not apply to the entire library. It is not clear to me what global
specification we could have for bool(algebraic expression).

On Tue, 27 Sept 2022 at 12:49, 'Martin R' via sage-devel
 wrote:
>
> I am reading this differently, but that may be my lack of knowledge of 
> English.
>
> I thought "Return True, unless provably zero" would give true, if something 
> cannot be shown to be zero.
>
> Martin
>
> On Tuesday, 27 September 2022 at 12:21:12 UTC+2 vdelecroix wrote:
>>
>> On Tue, 27 Sept 2022 at 11:58, 'Martin R' via sage-devel
>>  wrote:
>> >
>> >
>> >
>> > On Friday, 23 September 2022 at 20:09:55 UTC+2 Nils Bruin wrote:
>> >>
>> >> On Friday, 23 September 2022 at 10:37:01 UTC-7 axio...@yahoo.de wrote:
>> >>>
>> >>> OK, this is off topic, but: shouldn't it be this convention? At least: 
>> >>> shouldn't there be some convention? Maybe it would be good to discuss 
>> >>> this in a separate thread. Thus, I repeat the question:
>> >>>
>> >>> Is there, or should there be a convention about x._bool_ returning False 
>> >>> only when x is provably False?
>> >>>
>> >> No, quite the opposite. Certainly in SR, equalities that can't be proven 
>> >> correct (for "proof" used in the loose sense of what the various symbolic 
>> >> engines are willing to confirm), will return "False" when converted to 
>> >> "bool" value. The key is: _bool_ cannot really error out (that would 
>> >> break too much in python) and does not allow for "unknown" outcomes, so 
>> >> some choice must be made.
>> >
>> >
>> > The doc of Expression.__bool__ says:
>> >
>> > Return True unless this symbolic expression can be shown by Sage
>> > to be zero. Note that deciding if an expression is zero is
>> > undecidable in general.
>> >
>> > which seems to be in agreement with what I thought. Or am I missing 
>> > something?
>> >
>> > It seems really strange to me that "not O(x^7)" should be True.
>>
>> According to this symbolic specification,O(x^7) is not provably an
>> exact zero so it is reasonable to evaluate it to False. Which means
>> that "not O(x^7)" ought to be True.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/a4a00641-0b8d-4fd4-8690-7e75bb860c74n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3DQ0ZEP82hSKFq7Sx4r7qraO7aZ5L005xzabr19QJSp%3Dw%40mail.gmail.com.

Re: [sage-devel] is there a convention for _bool_ was: is it intentional that prod does not stop when it hits 0?

[Vincent Delecroix]

On Tue, 27 Sept 2022 at 11:58, 'Martin R' via sage-devel
 wrote:
>
>
>
> On Friday, 23 September 2022 at 20:09:55 UTC+2 Nils Bruin wrote:
>>
>> On Friday, 23 September 2022 at 10:37:01 UTC-7 axio...@yahoo.de wrote:
>>>
>>> OK, this is off topic, but: shouldn't it be this convention?  At least: 
>>> shouldn't there be some convention?  Maybe it would be good to discuss this 
>>> in a separate thread.  Thus, I repeat the question:
>>>
>>> Is there, or should there be a convention about x._bool_ returning False 
>>> only when x is provably False?
>>>
>> No, quite the opposite. Certainly in SR, equalities that can't be proven 
>> correct (for "proof" used in the loose sense of what the various symbolic 
>> engines are willing to confirm), will return "False" when converted to 
>> "bool" value. The key is: _bool_ cannot really error out (that would break 
>> too much in python) and does not allow for "unknown" outcomes, so some 
>> choice must be made.
>
>
> The doc of Expression.__bool__ says:
>
> Return True unless this symbolic expression can be shown by Sage
> to be zero.  Note that deciding if an expression is zero is
> undecidable in general.
>
> which seems to be in agreement with what I thought.  Or am I missing 
> something?
>
> It seems really strange to me that "not O(x^7)" should be True.

According to this symbolic specification,O(x^7) is not provably an
exact zero so it is reasonable to evaluate it to False. Which means
that "not O(x^7)" ought to be True.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAk_-fXfQpvj4YUnemJu3T3%3DJ%2BGJUuVrKa6whBHfqZAQOw%40mail.gmail.com.

Re: [sage-devel] Re: VOTE: move Sage development to Github

[Vincent Delecroix]

-1

On Fri, 23 Sept 2022 at 12:43, Marc Mezzarobba  wrote:
>
> Emmanuel Charpentier wrote:
> > +1 for Github
> >
> > Also wishing for contingency plan for re-migrating to self-hosted
> > Gitlab.
>
> Same here.
>
> --
> Marc
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/tgk2jf%24nm6%241%40ciao.gmane.io.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmy6gDkBdkw_iiUZGuFwygWGpF-eN9-BLc2-1q3vyWPzQ%40mail.gmail.com.

[sage-devel] PARI/GP upgrade to 2.15

[Vincent Delecroix]

Dear all,

The PARI/GP team is about to release a new version. I opened a ticket
for that purpose at https://trac.sagemath.org/ticket/34537. It went
relatively smoothly with respect to building. However there are a lot
of doctest failures in a lot of different files that I am not familiar
about. Some of them involves the fact that they introduced a new LLL
implementation. The list of failures appears in comment:5 on the
ticket. Any help on understanding/fixing them would be appreciated.

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmB7Msin%3DpP1KO4SoooMoC1%2BqE6YDANi8JvMpK%3DPyP6nA%40mail.gmail.com.

Re: [sage-devel] A list of file with deprecation

[Vincent Delecroix]

> I have a question: given a trac ticket number, is there a way of recover the 
> "Merge In" field of the ticket with the command line? I'd like to 
> automatically add this info to the list.

For that purpose, the git trac command line tool is very helpful
```
$ git trac find 1aeab526b544f3559028767fb8e79e3a4690b476
Commit has been merged in Updated SageMath version to 8.6.beta0.
commit 68e69a31793d44e5a537ee23ff36fbb304fd3cb1
Merge: b17d624e3e 714417176c
Author: Release Manager 
Date:   Sun Dec 23 00:56:30 2018 +0100

Trac #26846: py3: fix sparse graph isomorphism

URL: https://trac.sagemath.org/26846
Reported by: chapoton
Ticket author(s): Frédéric Chapoton
Reviewer(s): David Coudert
```

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAnmD1Y7JZ9g__bxqo7%3D8-KESdvHE_Cq8fKA1hx4qBuOPQ%40mail.gmail.com.

Re: [sage-devel] Re: On changing Bernoulli(1) to +½

[Vincent Delecroix]

PARI/GP actually has a better convention : only even Bernoulli numbers exist

? bernvec(5)
%1 = [1, 1/6, -1/30, 1/42, -1/30, 5/66]

And the two conventions can be recovered as evaluations of Bernoulli
polynomials at 0 and 1 respectively

? [subst(bernpol(n), x, 0) | n <- [1..6]]
%2 = [-1/2, 1/6, 0, -1/30, 0, 1/42]
? [subst(bernpol(n), x, 1) | n <- [1..6]]
%3 = [1/2, 1/6, 0, -1/30, 0, 1/42]

I second Edgar that I don't see much of the point on doing this
change. If we had to do any change I would suggest to raise an error
when bernoulli(n) is called with n=1 so that nobody could complain
about sage convention choices.

Vincent

On Tue, 13 Sept 2022 at 04:00, edgardi...@gmail.com
 wrote:
>
> The choice of the sign is arbitrary. So why make this change? What is the 
> benefit?
> Most recent papers, algebra systems (Maple/Mathematica/Magma/Matlab/Oscar), 
> and libraries (Pari/Flint/Mpmath/ARB) seemed to have picked B_1 = -1/2.
> Thus why put work into changing the default value and go against the current 
> norm?
> By doing this you will generate a lot of unnecessary work to go from one 
> arbitrary choice (that most people use) to another that few seem to use.
> On Monday, September 12, 2022 at 5:09:24 PM UTC-4 Fredrik Johansson wrote:
>>
>> I'm pretty neutral about this change, but I've received PRs for FLINT and 
>> mpmath (presumably there will be one for Arb as well) so I suppose I will 
>> need to make a decision about merging or closing them sooner or later :-)
>>
>> The sign convention for B_1 is fairly arbitrary, and the downside of 
>> changing it is that this introduces ambiguity and inconsistency where there 
>> was none before. On the other hand, you can make the case that "patching" 
>> deficient conventions is better in the long run... at least if the new 
>> convention eventually sees near-universal adoption (which is not at all 
>> guaranteed here).
>>
>> An advantage of B+ is that it would agree with the definition used in Sage 
>> for generalized Bernoulli numbers when restricted to the trivial character; 
>> see 
>> https://doc.sagemath.org/html/en/reference/modmisc/sage/modular/dirichlet.html#sage.modular.dirichlet.DirichletCharacter.bernoulli
>>
>> The claim "bernoulli_plus admits a natural generalisation to real and 
>> complex numbers but bernoulli_minus does not" (made elsewhere in this 
>> thread) seems a bit hyperbolic. For B+ this natural generalization is 
>> -n*zeta(1-n); for B- one can just use -n*zeta(1-n)*cos(pi*n). OK, one is a 
>> bit simpler than the other, but both are perfectly fine entire functions.
>>
>> For Sage and mpmath, I suppose the least intrusive option is to introduce a 
>> keyword argument to select the plus/minus convention, with B- as default 
>> until there is community consensus to change it. There is not really a 
>> strong need to change low-level libraries like FLINT at this point since 
>> it's trivial to handle both conventions in a wrapper.
>>
>> Fredrik
>>
>>
>> On Saturday, September 10, 2022 at 4:17:08 PM UTC+2 redde...@gmail.com wrote:
>>>
>>> My name is Jeremy Tan, or Parcly Taxel in the furry/MLP art scene. As of 
>>> this post I am a recent graduate from the National University of Singapore 
>>> with two degrees in maths and computer science.
>>>
>>> Over the past month I had a good read of Peter Luschny's Bernoulli 
>>> Manifesto (http://luschny.de/math/zeta/The-Bernoulli-Manifesto.html) and 
>>> was thoroughly convinced that B_1 (the first Bernoulli number) has to be 
>>> +½, not -½. (Much of Luschny's argument centres on being able to (1) 
>>> interpolate the Bernoulli numbers when B_1 = +½ with an entire function 
>>> intimately related to the zeta function, and (2) extend the range of 
>>> validity of or simplify several important equations like the 
>>> Euler–Maclaurin formula. Have a read yourself though – it is close to 
>>> divine truth.)
>>>
>>> So I went to SymPy – one of SageMath's dependencies, and where a discussion 
>>> on this topic was open (https://github.com/sympy/sympy/issues/23866) – and 
>>> successfully merged several PRs there 
>>> (https://github.com/sympy/sympy/pull/23926) implementing both that change 
>>> and some functions in Luschny's "An introduction to the Bernoulli function" 
>>> (https://arxiv.org/abs/2009.06743).
>>>
>>> I thought I was also done with changing B_1 = +½ for SageMath, but then 
>>> someone pointed out that the latter currently uses other libraries that all 
>>> have B_1 = -½. I have already opened a PR for one such library, FLINT, to 
>>> change B_1 = +½ there (https://github.com/wbhart/flint2/pull/1179). However 
>>> Fredrik Johansson has advised me that I take the discussion right here, to 
>>> sage-devel, because (in his words)
>>>
>>> > if FLINT and Arb change their definitions but the Sage developers decide 
>>> > that they don't like it, they will just treat the new behavior as a bug 
>>> > and add a special case in the wrapper to return B_1 = -½.
>>>
>>> So my proposal is to 

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

[Vincent Delecroix]

Hello,

I am in the same mood as Travis : if I was to consider a move to
github I would like to have a clear and complete overview of the
changes in the workflow (how do we set ticket dependencies? how
reviews will work? management of releases? etc). For me the discussion
in this thread is very premature as there is no proposal of this sort.
The "moving to github" does not specify how things will work.

I see clear advantages of moving to github. The first being trac
maintenance and a second example that William mentioned is that it
might lower the barrier for newcomers. But there are also plenty of
reasons not to migrate. The first one I think is that we might loose
active developers. Let me recall that the move from mercurial to git
some 10 years ago made many active developers quit.

So I would like to propose that ticket #30363 instead of being
technical (ie how do we do the move) explains
- a concrete proposal for a github workflow (there might be several of them)
- list the pros
- list the cons
Then we could proceed with a reasonable discussion on whether we will
do such move.

Ideally (if we had illimited developer time) I would like to encourage
the possibility of having both trac and github. If I recall correctly,
it was possible to authenticate to trac with github account and make
PR on github that automatically transformed into a ticket on trac.

Best
Vincent

On Sat, 10 Sept 2022 at 09:54, Dima Pasechnik  wrote:
>
>
>
> On Sat, 10 Sep 2022, 05:48 Matthias Koeppe,  wrote:
>>
>> On Friday, September 9, 2022 at 9:34:16 PM UTC-7 Travis Scrimshaw wrote:
>>>
>>> I really dislike Github's decentralized approach with PR and having to have 
>>> separate clones of the repo within each user. My understanding is if two 
>>> people have different fixes, then they individually submit PRs that are not 
>>> explicitly linked with each other, much less with a specific bug report 
>>> issue.
>>
>>
>> In the PR you would include a comment such as "Fixes #1234", which links it 
>> to an Issue (bug report).
>
>
> and this Issue will then automatically get a comment/mention linking to the 
> PR, no manual intervention in the Issue is needed.
>
>
>> Yes, there can be multiple competing PRs in order solve one ticket. Better 
>> than edit wars on a Trac ticket.
>>
>>
>> --
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/2548301a-19d8-4ab5-ab1c-84f3fdcf5bbcn%40googlegroups.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq3rdAfkj%3DkDLJa0TxMPxLHz4O2_stffO8F-PyiGsO0ZqQ%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkYpD4fh%3D_QvuwmZoRSgrF6AgUeg1WWvbXMhX-DJ5hanA%40mail.gmail.com.

Re: [sage-devel] abort() in __gmpz_realloc of symbolic expression with `gmp: overflow in mpz type`

[Vincent Delecroix]

Indeed, there is something wrong with the error handling of exponents

{{{
sage: a = 2 ** (2**63)
Traceback (most recent call last):
...
.../sage/rings/integer.pyx in sage.rings.integer.Integer._pow_
   2229 r = smallInteger(1)
   2230 else:
-> 2231 raise OverflowError(f"exponent must be at most {LONG_MAX}")
   2232 if mpz_sgn(exp) >= 0:
   2233 return r

OverflowError: exponent must be at most 9223372036854775807
}}}
but
{{{
sage: a = 2 ** (2**62)
Traceback (most recent call last):
...
.../sage/rings/integer.pyx in sage.rings.integer.Integer.__pow__
   2149
   2150 if type(left) is type(right):
-> 2151 return (left)._pow_(right)
   2152 elif isinstance(left, Element):
   2153 return coercion_model.bin_op(left, right, operator.pow)

.../sage/rings/integer.pyx in sage.rings.integer.Integer._pow_
   2213
   2214 if mpz_fits_slong_p(exp):
-> 2215 return self._pow_long(mpz_get_si(exp))
   2216
   2217 # Raising to an exponent which doesn't fit in a long overflows

.../sage/rings/integer.pyx in sage.rings.integer.Integer._pow_long
   2245 if n > 0:
   2246 x = PY_NEW(Integer)
-> 2247 sig_on()
   2248 mpz_pow_ui(x.value, self.value, n)
   2249 sig_off()

RuntimeError: Aborted
}}}

On Sun, 4 Sept 2022 at 11:58, Georgi Guninski  wrote:
>
> sage 9.0 on ubuntu 20.
>
> When raising symbolic expression to large integer power
> i get abort() with stack:
>
> gmp: overflow in mpz type
>
> /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f26d1c7a859]
> /lib/x86_64-linux-gnu/libgmp.so.10(__gmpz_realloc+0xad)[0x7f26d048edcd]
> /lib/x86_64-linux-gnu/libgmp.so.10(__gmpz_n_pow_ui+0x7e7)[0x7f26d048ba97]
> /lib/x86_64-linux-gnu/libpynac.so.18(_ZNK5GiNaC7numeric5powerEl+0x114)[0x7f26683b1c14]
>
> The non-minimal testcase
> ===
> def binnk3u(n,k):  return ( (n/k)**(k))
> n1=(2*10**3);d0=29004853178239;n0=SR(log(n1));tt=binnk3u(n0+d0-1,(d0))
> print("passed :(")
> ===
>
> on sagecell i get no output, just an animated rotating circle.
>
> if possible please don't regress the following, which works:
>
> sage: log(pi)**(2**80)
> log(pi)^1208925819614629174706176
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CAGUWgD_Un568rw_RfAUmS3YaGiwV4sGh49oVsUkGEC3gvbV1rA%40mail.gmail.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkH6kzYXKibDmY23Y6ZhKCQ3UPt2Rwo6iHSvqvttz77qA%40mail.gmail.com.

Re: [sage-devel] Trac #34152 needs you (to vote)!

[Vincent Delecroix]

hybrid > copy files > sage pseudo package

Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmZi5Noq2FWqigeN4VWJVAswiZS1T9kQzAYpGdztQhveg%40mail.gmail.com.

[sage-devel] Re: 9.7.beta8 build error jupyter_jsmol

[Vincent Delecroix]

Note that this looks like a network failure... but this is happening
inside the jupyter_jsmol build which tries to install some javascript
via npm. I thought that the package tarballs were supposed to contain
everything to build by themselves.

On Tue, 23 Aug 2022 at 18:27, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> Dear all,
>
> A fresh build on archlinux stopped at jupyter_jsmol. See attached logs.
>
> Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAA%3Dkg%3D1RpeY0SqawZPo9Yp1-6K1%3DtE1YLWXd_FanUx0g9A%40mail.gmail.com.

Re: [sage-devel] Re: LazyPowerSeriesRing Replacement

[Vincent Delecroix]

On Mon, 15 Aug 2022 at 09:50, John Cremona  wrote:
>
> On Mon, 15 Aug 2022 at 08:21, Kwankyu Lee  wrote:
> >
> > If LazyTaylorSeriesRing could be a complete replacement of 
> > LazyPowerSeriesRing, then I think we should remove the old 
> > LazyPowerSeriesRing
> > and rename LazyTaylorSeriesRing to LazyPowerSeriesRing. Do you mean this?
> >
> > Mathematically, Taylor series means power series derived from a function. 
> > So aTaylor series is always attached to a function. The name 
> > LazyTaylorSeriesRing seems a misnomer.
>
> I agree with all these points!

Me too.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmdxyJHiXnniu_9KJFPV8pOR4A2Km2GDvazPWRvrH-uHQ%40mail.gmail.com.

Re: [sage-devel] Re: fractions of symmetric functions

[Vincent Delecroix]

On Tue, 9 Aug 2022 at 21:14, 'Martin R' via sage-devel
 wrote:
>
> I am guessing that part of the problem is
>
> sage: SymmetricFunctions(ZZ) in IntegralDomains()
> False

Though the following looks fine

sage: SymmetricFunctions(ZZ).e() in IntegralDomains()
True

> The other problem is that fraction_field is not a parent method of 
> IntegralDomains.

Indeed, it is only implemented in sage/rings/ring.pyx which is a
historic left over. Moreover, the implementation uses a custom cache
with double underscore where cached_method would do the job. I think
it would be a good time to try to move the implementation to
categories.

Could you open a ticket and cc me?

> I'd be grateful for input / corrections.

As Trevor implicitly suggested, I think you want a custom fraction
field here so that you can change basis. Typically, you would like a
coherent interface as follows

sage: S = SymmetricFunctions(ZZ)
sage: S.fraction_field().e() is S.e().fraction_field()
True
sage: Ke = S.fraction_field().e()
sage: Kp = S.fraction_field().p()
sage: Kp(Ke([3,2,1]) / Ke([2,1])) == Kp(Ke([3,2,1])) / Kp(Ke([2,1]))
True

But to my mind this is another layer of complexity and would require
an other iteration of tickets.

Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAna8k295yZrX9CMjVaXFjqvadPvuLBJX2-iTu2LeveW5w%40mail.gmail.com.

Re: [sage-devel] Proposal: make Furo a standard package

[Vincent Delecroix]

On Thu, 4 Aug 2022 at 08:16, Kwankyu Lee  wrote:
>
>
>
> On Thursday, August 4, 2022 at 2:07:56 PM UTC+9 vdelecroix wrote:
>>
>> Let me add a note that I don't like so much the code blocks (ie
>> EXAMPLES/TESTS). Namely,
>> * the brackets and parenthesis are weirdly bold (maybe because of the
>> fonts on my computer)
>> * numbers appear in bold blue and we basically see only this from far away
>> * I dislike the output part being in italic
>> * The "sage:" prompt has the same color as comments "# this is a
>> comment" which is not nice
>> * The symbols +, *, / have too close color to prompt and commands
>
>
> The style of code blocks is dictated by the Pygments style in Sphinx. What 
> you see is the "tango" style, which seems best from my experiments.
>
> Here are the choices: https://pygments.org/styles/ You may like other style 
> But it would be hard to pick one style agreeable to us all.

Is it your personal decision to use tango for the (future) sage
documentation? As a very personal opinion, I prefer better the default
style. Note that tango is a style with lower contrast which is another
argument against it.

Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAmrTGQG%2Bh%3D_beZwS5W21CDiRPbJ7F7KmUQAXgqF3qSrXg%40mail.gmail.com.

Re: [sage-devel] Proposal: make Furo a standard package

[Vincent Delecroix]

Thanks for working on this. +1 for making Furo standard.

Let me add a note that I don't like so much the code blocks (ie
EXAMPLES/TESTS). Namely,
* the brackets and parenthesis are weirdly bold (maybe because of the
fonts on my computer)
* numbers appear in bold blue and we basically see only this from far away
* I dislike the output part being in italic
* The "sage:" prompt has the same color as comments "# this is a
comment" which is not nice
* The symbols +, *, / have too close color to prompt and commands

Best
Vincent

On Thu, 4 Aug 2022 at 03:29, Kwankyu Lee  wrote:
>
> Dear Sage developers,
>
> Furo is a clean customisable Sphinx documentation theme. It has been an 
> optional pip package since  Sage 9.7.beta2.
>
> Meanwhile we made efforts to make Furo a new theme for our documentation 
> through
>
> https://trac.sagemath.org/ticket/33601
> https://trac.sagemath.org/ticket/34252
> https://trac.sagemath.org/ticket/33833
>
> Now it is ready to replace the current Sage classic theme that makes our 
> documentation look awfully outdated. You can check the documentation with new 
> look and feel in
>
> https://2505ea042169d8a179d4b1f28a0c0baeabdd421a--sagemath-tobias.netlify.app/
>
> It would be great that Sage 9.7 will be released with the lifted-up 
> documentation.
>
> So we propose here to upgrade the Furo package to a standard package. Please 
> vote.
>
>
>
>
>
>
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/f0478d5c-6005-4a30-b96e-5b9b2e37b213n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkLFuEGnWqACa70hS_HTpu6L4Sd0SFrggipe9sPu9H95g%40mail.gmail.com.

[sage-devel] pplpy

[Vincent Delecroix]

Hello,

Unless anyone disagrees, I will move the development of pplpy from
gitlab (https://gitlab.com/videlec/pplpy) to github under the sagemath
group. It will simplify the maintenance on my side.

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkH4YQ_8D-UB-yxh30yTzxLaywj548v78T8odeump3_XA%40mail.gmail.com.

Re: [sage-devel] Error in matrix reduction

[Vincent Delecroix]

Indeed, calling previous_prime(p) with p=2 does not sound like a good
idea :-) The following is very suspicious to me

~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/matrix/misc.pyx
in sage.matrix.misc.matrix_rational_echelon_form_multimodular
(build/cythonized/sage/matrix/misc.c:7147)()

375 verbose("Excluding this prime (bad pivots).",
caller_name="multimod echelon")

376 t = verbose("time for pivot compare", t, level=2,
caller_name="multimod echelon")

--> 377 p = previous_prime(p)

Vincent

On Fri, 29 Jul 2022 at 16:07, Trevor Karn  wrote:
>
> Hi all,
>
> I'm working on trac ticket https://trac.sagemath.org/ticket/34138 and during 
> some testing on commit b3ef1f7 got an error that I don't understand. In 
> implementing the F4 algorithm there is a computation of matrix RREF. During 
> that step, on the "gametwo7" example of 
> https://web.archive.org/web/20181129231728/http://www.cecm.sfu.ca/~rpearcea/polsys.txt,
>  I get the error below. It looks like the error is occurring in the matrix 
> row reduction. Does this seem like a bug with the Groebner basis code or with 
> the matrix code?
>
> Thanks so much!
>
> Best,
> Trevor
>
>  ---
>
> ValueErrorTraceback (most recent call last)
>
>  in 
>
> > 1 cProfile.runctx('I.groebner_basis()', globals(), locals(), 
> 'profile.prof')
>
>
> /usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/cProfile.py
>  in runctx(statement, globals, locals, filename, sort)
>
>  17
>
>  18 def runctx(statement, globals, locals, filename=None, sort=-1):
>
> ---> 19 return _pyprofile._Utils(Profile).runctx(statement, globals, 
> locals,
>
>  20  filename, sort)
>
>  21
>
>
> /usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/profile.py
>  in runctx(self, statement, globals, locals, filename, sort)
>
>  60 prof = self.profiler()
>
>  61 try:
>
> ---> 62 prof.runctx(statement, globals, locals)
>
>  63 except SystemExit:
>
>  64 pass
>
>
> /usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/cProfile.py
>  in runctx(self, cmd, globals, locals)
>
>  98 self.enable()
>
>  99 try:
>
> --> 100 exec(cmd, globals, locals)
>
> 101 finally:
>
> 102 self.disable()
>
>
>  in 
>
>
> ~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/algebras/clifford_algebra.py
>  in groebner_basis(self, term_order)
>
>2755 return self._groebner_strategy.groebner_basis
>
>2756 self._groebner_strategy = strategy(self)
>
> -> 2757 self._groebner_strategy.compute_groebner()
>
>2758 return self._groebner_strategy.groebner_basis
>
>2759
>
>
> ~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/algebras/exterior_algebra_groebner.pyx
>  in sage.algebras.exterior_algebra_groebner.GroebnerStrategy.compute_groebner 
> (build/cythonized/sage/algebras/exterior_algebra_groebner.c:8678)()
>
> 221 while P:
>
> 222 Pp = P.pop(min(P))  # The selection: lowest lcm degree
>
> --> 223 Gp = self.reduction(Pp, G)
>
> 224 G.extend(Gp)
>
> 225 for j in range(n, len(G)):
>
>
> ~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/algebras/exterior_algebra_groebner.pyx
>  in sage.algebras.exterior_algebra_groebner.GroebnerStrategy.reduction 
> (build/cythonized/sage/algebras/exterior_algebra_groebner.c:7581)()
>
> 178 for m,c in ( 
> f)._monomial_coefficients.items()},
>
> 179sparse=True)
>
> --> 180 M.echelonize()  # Do this in place
>
> 181 lead_supports = 
> set(self.leading_supp( f) for f in L)
>
> 182 return [self.E.element_class(self.E, {self.int_to_bitset(r - 
> Integer(j)): c for j,c in M[i].iteritems()})
>
>
> ~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/matrix/matrix_rational_sparse.pyx
>  in sage.matrix.matrix_rational_sparse.Matrix_rational_sparse.echelonize 
> (build/cythonized/sage/matrix/matrix_rational_sparse.c:7063)()
>
> 524 self.check_mutability()
>
> 525
>
> --> 526 pivots = self._echelonize_multimodular(height_guess, proof, 
> **kwds)
>
> 527
>
> 528 self.cache('in_echelon_form', True)
>
>
> ~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/matrix/matrix_rational_sparse.pyx
>  in 
> sage.matrix.matrix_rational_sparse.Matrix_rational_sparse._echelonize_multimodular
>  

Re: [sage-devel] sage -i normaliz fails on cygwin due to e-antic

[Vincent Delecroix]

Your compilation problem comes from the fact that antic
(https://github.com/wbhart/antic) is not available. You should install
it first. If you are familiar with (or curious about)
compilation/installation in the sage environment you can install the
full normaliz stack manually. Otherwise you might just want to wait
for the upgrade ticket to be ready.

On Fri, 29 Jul 2022 at 14:09, Max Kölbl  wrote:
>
> @Vincent thank you very much!
> I opened the subshell by typing
>
> $ cd '/home/Ray/sage/sage/local/var/tmp/sage/build/e_antic-1.2.1' && 
> '/home/Ray/sage/sage/sage' --buildsh
>
> and then I ran your suggestions, but I got an error again. These are the last 
> lines in the shell:
>
> > checking for antic/nf.h... no
> > configure: error: antic headers not found
> > configure: error: ./configure failed for libeantic
>
> Is that the correct setting in the first place?
>
> After that, I tried installing antic in the sage environment directly, but 
> the compilation also failed.
>
> Should I still open an issue on
> https://github.com/flatsurf/e-antic ?
>
> Thank you very much in advance!
>
> @Matthias thank you! That's good to know!
>
>
> Matthias Koeppe schrieb am Freitag, 29. Juli 2022 um 03:34:34 UTC+9:
>>
>> That would be the upgrade ticket https://trac.sagemath.org/ticket/31588
>>
>> On Thursday, July 28, 2022 at 7:06:45 AM UTC-7 vdelecroix wrote:
>>>
>>> Hi Max,
>>>
>>> Could you try to build the last version of e-antic (1.2.1) in the sage
>>> environment ? In the sage shell, this is achieved with
>>>
>>> $ wget 
>>> https://github.com/flatsurf/e-antic/releases/download/1.2.1/e-antic-1.2.1.tar.gz
>>> $ tar xf e-antic-1.2.1.tar.gz
>>> $ cd e-antic-1.2.1
>>> $ ./configure --without-byexample --without-pytest --without-doc
>>> $ make
>>>
>>> In case it fails, reply to this message or open an issue at
>>> https://github.com/flatsurf/e-antic
>>>
>>> Best
>>> Vincent
>>>
>>> On Thu, 28 Jul 2022 at 14:53, Max Kölbl  wrote:
>>> >
>>> > Dear everyone,
>>> >
>>> > It is me again with a different problem.
>>> >
>>> > While trying to run `sage -i normaliz`, an error occured due to e-antic.
>>> > The log is attached.
>>> >
>>> > I also tried as a workaround to build normaliz directly, but the 
>>> > `install_normaliz_with_eantic.sh`-script failed too (but I don't know 
>>> > where to ask about this).
>>> >
>>> > Thank you very much in advance!
>>> > Max
>>> >
>>> > --
>>> > 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+...@googlegroups.com.
>>> > To view this discussion on the web visit 
>>> > https://groups.google.com/d/msgid/sage-devel/ed4afc25-7402-4226-be26-32226de91bd7n%40googlegroups.com.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/8d72c0f9-630d-4f5a-96fd-f0a4462c0998n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAnETXA0f5Ff1yDQQNNX6nYNjs0e01NJpG4vf_MYYPgZOQ%40mail.gmail.com.

[sage-devel] docker image sagemath/sagemath-dev:develop performs full compilation

[Vincent Delecroix]

Dear all,

When running

$ docker run -it sagemath/sagemath-dev:develop

the machine launches and starts compiling all of sage! Not sure when
such behaviour started but something is definitely broken.

Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAnR4ohxb-GX9vOqASCvtdkMbaDrvDg_U6DJMhDOWcnf%2Bw%40mail.gmail.com.

Re: [sage-devel] sage -i normaliz fails on cygwin due to e-antic

[Vincent Delecroix]

Hi Max,

Could you try to build the last version of e-antic (1.2.1) in the sage
environment ? In the sage shell, this is achieved with

$ wget 
https://github.com/flatsurf/e-antic/releases/download/1.2.1/e-antic-1.2.1.tar.gz
$ tar xf e-antic-1.2.1.tar.gz
$ cd e-antic-1.2.1
$ ./configure --without-byexample --without-pytest --without-doc
$ make

In case it fails, reply to this message or open an issue at
https://github.com/flatsurf/e-antic

Best
Vincent

On Thu, 28 Jul 2022 at 14:53, Max Kölbl  wrote:
>
> Dear everyone,
>
> It is me again with a different problem.
>
> While trying to run `sage -i normaliz`, an error occured due to e-antic.
> The log is attached.
>
> I also tried as a workaround to build normaliz directly, but the 
> `install_normaliz_with_eantic.sh`-script failed too (but I don't know where 
> to ask about this).
>
> Thank you very much in advance!
> Max
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/ed4afc25-7402-4226-be26-32226de91bd7n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAk6qVp0mrGVsLUaV-4E9JMwn%3DmXtZqc0X_LJqhdkX9tfg%40mail.gmail.com.

Re: [sage-devel] Adding a C or C++ Code to The SageMath

[Vincent Delecroix]

Autotools is convenient but definitely not mandatory. cmake does a
similar job. Some projects (eg flint, PARI/GP) have a home made build
system that works fine.

What is required is:
* a configuration step that let us specify the build directory,
install directory, compilers, static versus dynamic library, etc. This
is typically done via a configure script.
* a build step, typically a target of the Makefile, eg "make build"
* an installation step, typically a target of the Makefile, eg "make install"

On Sat, 9 Jul 2022 at 16:24, friedri...@gmail.com
 wrote:
>
> Hi all,
>
> I just stumbled across this thread :) and am curious, what the best way would 
> be to add ESPRESSO to sage.
> Judging the package type for ESPRESSO from the sage packaging doc referenced 
> by Matthias, I'd say its definitly not a pip package ;) however I'm not sure 
> I understand the difference between a "normal" and a "script" package. It 
> says, a normal package comes from a tarball, so we'd need a source of that 
> for ESPRESSO, i.e. a tar archive containing the source code as well as a 
> build environment - should this be based on autotools? But I assume an 
> equivalent build environment needs to be available for a script package, too?
>
> So far I'm not aware of any ESPRESSO distribution that would provide, e.g., 
> an autotools based build (https://github.com/Gigantua/Espresso/tree/main/src 
> gives for example only a Visual Studio project which will not help for 
> including it in sage, I assume?).
>
> Thus, first step would be to write an autotools build for ESPRESSO, is that 
> right?
>
> Matthias Koeppe schrieb am Sonntag, 14. Juni 2020 um 02:50:00 UTC+2:
>>
>> https://doc.sagemath.org/html/en/developer/packaging.html
>>
>> On Saturday, June 13, 2020 at 11:17:51 AM UTC-7 hsn.ha...@gmail.com wrote:
>>>
>>> Hello all!
>>>
>>> I would be most grateful if someone let me know how I should start. It 
>>> would be fine if you introduced to me, a simple example which has been 
>>> already implented in Sage, so thst I could review it. Thanks for your time.
>>>
>>> Cheers,
>>> Hosein
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/447c823c-80ec-4613-9568-1185d4b9b0b0n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAki%2BV%2BcUjVWpPc6gkLu%3D%3DhfA516RiScP9f5YZW8rC5QVw%40mail.gmail.com.

Re: [sage-devel] Re: Length of vectors in `plot_vector_field3d()`

[Vincent Delecroix]

On Mon, 20 Jun 2022 at 18:01, Niranjana K M  wrote:
>
> @Vincent
>
> On Sun, Jun 19, 2022 at 5:52 PM Vincent Delecroix <20100.delecr...@gmail.com> 
> wrote:
>>
>> Nice catch indeed. I am not sure that "scaled=True/False" is the most
>> flexible design. You might just want to apply *some* scale, not
>> necessarily the one making the max length being one. I imagine that it
>> would be nice to allow "scaled" to be a positive floating point
>> number. In other words
>>
>> if scaled is True: # boolean
>> scaled_vectors = [v/max_len for v in vectors]
>> elif scaled is False: # boolean
>> scaled_vectors = vectors
>> else: # assume that scaled is a ratio
>> scaled = float(scaled)
>> assert scaled > 0
>> scaled_vectors = [v / scaled for v in vectors]
>>
>> What do you think?
>
>
> Nice. It will implement scaling as available in vector_field().plot(). Let 
> the scaling be a factor multiplication (it will avoid dividing by 0 if 
> scaled=0) and let it be positive or negative (for which the arrows reverse in 
> direction).
> Is it necessary to convert scaled into a float? Any real number is fine to 
> multiply.
> A slight modified version:
>
> if scaled is True: # boolean
> scaled_vectors = [v/max_len for v in vectors]
> elif scaled is False: # boolean
> scaled_vectors = vectors
> else: # assume that scaled is a real number
> #scaled = float(scaled)
> assert scaled in RR
> scaled_vectors = [v*scaled for v in vectors]

I think it is desirable to use the same argument conventions as the
method VectorField.plot(). In particular use `scale` and not `scaled`.
I don't know whether VectorField.plot() supports a default rescaling
as you proposed.

>> Do you know how to open a ticket on https://trac.sagemath.org? Details
>> are in the developer guide
>> (https://doc.sagemath.org/html/en/developer/index.html).
>>
>
> I read the guide. Shall I open a ticket?

Sure. You can go on. Don't forget to mention the ticket number you
open in this e-mail discussion.

Best
Vincent

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkZoWf91bzjT-EUC%3DCg0w8jLBnVgEdzVhRXtHrgQ8YpYA%40mail.gmail.com.

Re: [sage-devel] Re: Length of vectors in `plot_vector_field3d()`

[Vincent Delecroix]

Nice catch indeed. I am not sure that "scaled=True/False" is the most
flexible design. You might just want to apply *some* scale, not
necessarily the one making the max length being one. I imagine that it
would be nice to allow "scaled" to be a positive floating point
number. In other words

if scaled is True: # boolean
scaled_vectors = [v/max_len for v in vectors]
elif scaled is False: # boolean
scaled_vectors = vectors
else: # assume that scaled is a ratio
scaled = float(scaled)
assert scaled > 0
scaled_vectors = [v / scaled for v in vectors]

What do you think?

Do you know how to open a ticket on https://trac.sagemath.org? Details
are in the developer guide
(https://doc.sagemath.org/html/en/developer/index.html).

Best
Vincent

On Sun, 19 Jun 2022 at 13:38, Niranjana K M  wrote:
>
> Dear all,
> I figured it out. It  has to do with
> scaled_vectors = [v/max_len for v in vectors]
> line 141 of  
> $SAGE_ROOT/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/plot/plot3d/plot_field3d.py
> Can we have scaling optional in sage? I just propose it, with a new keyword 
> argument default with `scaled=True`.
> if scaled:
> scaled_vectors = [v/max_len for v in vectors]
> else:
> scaled_vectors = vectors
> I can sense the consequences, when `scaled=False` and when the vector field 
> is such that the vector lengths are too large to over print on the vectors 
> ahead of them. At user's  risk, if he really wants them not to be scaled and 
> can play with range and plot_points to avoid overprinting.
>
> PS 1: I was trying to demonstrate and calculate electric flux through a 
> hemisphere with constant field. While plotting the constant field i felt them 
> not to be scaled.
> PS 2: I thank and appreciate sage community for bringing out such a wonderful 
> software. I have been following it since last 10+ years, since version 3.  I 
> am really excited while exploring the section Differential Geometry of 
> Parametrized Surfaces and sections on Manifolds, to see how Sage grew from 
> missing functions to manifolds. I just loved it.
>
> with regards,
> Niranjana
> On Sunday, June 19, 2022 at 3:56:55 PM UTC+5:30 Niranjana K M wrote:
>>
>> Dear all,
>> I tried to plot constant vector fields.
>> plot_vector_field3d((1,0,0), (x,-2,2), (y,-2,2), (z,-2,2))
>> and
>> plot_vector_field3d((2,0,0), (x,-2,2), (y,-2,2), (z,-2,2))
>> Length of the arrows of first one are equal to the second one. I expect 
>> that the length of arrows in second to be double that of the first. Also 
>> their lengths are not equal to their magnitudes.
>> Is it a bug? If it is the normal behavior, then any work around to have 
>> length of the arrows to be equal to that of the magnitudes of the vectors in 
>> the field.
>>
>> PS : The following shows vectors in the filed have their lengths equal to 
>> their magnitudes. As expected.
>> plot_vector_field3d((x,0,0), (x,-2,2), (y,-2,2), (z,-2,2))
>>
>> With regards
>> Niranjana
>>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/facb394b-bd32-40fc-9c59-60eff0deaa02n%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAkenrdUx-YDrZhKF8ekj0f4EeeGV%2B6VwG1X-kXt-N-63Q%40mail.gmail.com.

Re: [sage-devel] Sign issue in special values of Legendre Polynomials

[Vincent Delecroix]

There is indeed a problem

sage: legendre_P(2, 0)
1/2
sage: legendre_P(2.0, 0.0)
-0.500

On Mon, 6 Jun 2022 at 20:38, Dan Cross  wrote:
>
> Hi,
> It seems the special values of the Legendre Polynomials evaluated at zero are 
> hard coded to be positive, but the sign should alternate.  So, while 
> legendre_P(0,0) correctly gives 1 and legendre_P(4,0) correctly gives 3/8, 
> legendre_P(2,0) gives +1/2 instead of -1/2.  Evaluating legendre_P(2,x) for 
> any x close to zero gives a value close to -1/2 as it should.  This problem 
> is even evident on the documentation page 
> (https://paulmasson.github.io/sagemath-docs/functions/legendre_P.html) which 
> shows the graph of P_2 passing through -1/2 but tabulates the special value 
> at zero as +1/2.
>
> Thanks.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/9745505a-d332-4b63-9acd-770123e0291dn%40googlegroups.com.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAGEwAAndOc_J5r8AJSE4BuikdsiMv5Mt%3DpjGvPNc1Bjn32tdcQ%40mail.gmail.com.

Re: [sage-devel] --patchbot

[Vincent Delecroix]

I guess this is

https://wiki.sagemath.org/patchbot

which has moved to

https://trac.sagemath.org/wiki/patchbot

Le 30/05/2022 à 14:37, ph h a écrit :

Dear All,

Is this link correct: https://wiki.sagemath.org/buildbot ?
*This page does not exist yet. You can create a new empty page, or use one
of the page templates.*

Thank you for your help.

phiho

~/sage-9.7/b1.3$ root.beta1 -patchbot
Traceback (most recent call last):
   File "", line 1, in 
ModuleNotFoundError: No module named 'sage_patchbot'
Error: cannot find installation path for sage_patchbot
See https://wiki.sagemath.org/buildbot for instructions
~/sage-9.7/b1.3$



--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/430f9403-7ba1-02bf-612e-a168f6c4e456%40gmail.com.

Re: [sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

[Vincent Delecroix]

Le 16/05/2022 à 12:35, Dima Pasechnik a écrit :

On Mon, May 16, 2022 at 8:03 AM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:


I would say that code with parallel computations + cypari2 should not
be merged (as cypari2 does not support it).


is it parallel multiprocessing, or parallel multithreading?


True : multiprocessing is not a problem with cypari2. Only
multithreading must be avoided.


If you need parallel + PARI then use the C library directly with the
appropriate threads locks.

If the problem comes from somewhere else, then it would better be sorted
out.

Best
Vincent

Le 16/05/2022 à 06:42, 'Travis Scrimshaw' via sage-devel a écrit :

That sure seems like it. So what should we do about the ticket? Would there
be opposition to merging this piece of code, as there doesn't seem like
there is a fix coming for the likely underlying cypari bug anytime soon?

Best,
Travis


On Sunday, May 15, 2022 at 4:14:31 PM UTC+9 vdelecroix wrote:


Probably related to https://github.com/sagemath/cypari2/issues/107 ?

Le 15/05/2022 à 05:06, 'Travis Scrimshaw' via sage-devel a écrit :

Hi everyone,
On ticket #30423 <https://trac.sagemath.org/ticket/30423>, Dan, Willie,
and I have been working on a parallel-computation based implementation

for

computing F-matrices that are used in math physics. However, we have been
seeing some doctest failures sporadically that involve segfaults and
linked-list corruption from (cy)PARI. Here are the logs from testing with
the first and the last having full tracebacks.

http://sporadic.stanford.edu/badlog-match
http://sporadic.stanford.edu/badlog
http://sporadic.stanford.edu/badlog1
http://sporadic.stanford.edu/badlog2
http://sporadic.stanford.edu/badlog3

The first question would be if anyone has an idea about what is causing
this. I have this impression that PARI is thread-safe, but I am wondering
if cypari is also thread/parallel-safe or if there are any specific

things

that we should be careful about. (We’ve already had to work around a
pickling issue with polynomials IIRC.)

Second question is that because this is a Heisenbug and I suspect it is
something upstream (and so far, nobody has been able to reproducing it
during an interactive version of Sage), I was wondering what the policy
would be for merging the ticket. I recall in the past that we have merged
tickets with Heisenbugs with followup tickets noting the behavior, but I

am

not 100% sure about that (and I wouldn’t necessarily know how to find any
explicit examples). I was wondering if we could merge the ticket in an
early beta version so that many people/systems can test it to see if it
becomes more reproducible; of course this is assuming that the build bots
are not consistent in reproducing this. Should we just mark any offending
test(s) as “# known bug” and is there some general policy about this?

Thanks,
Travis








--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fd05e9f5-52b2-f2f8-bc02-c968c0a70e79%40gmail.com.




--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/8a34b501-51b9-595a-b5d3-c81d63c55ced%40gmail.com.

Re: [sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

[Vincent Delecroix]

I would say that code with parallel computations + cypari2 should not
be merged (as cypari2 does not support it).

If you need parallel + PARI then use the C library directly with the
appropriate threads locks.

If the problem comes from somewhere else, then it would better be sorted
out.

Best
Vincent

Le 16/05/2022 à 06:42, 'Travis Scrimshaw' via sage-devel a écrit :

That sure seems like it. So what should we do about the ticket? Would there
be opposition to merging this piece of code, as there doesn't seem like
there is a fix coming for the likely underlying cypari bug anytime soon?

Best,
Travis


On Sunday, May 15, 2022 at 4:14:31 PM UTC+9 vdelecroix wrote:


Probably related to https://github.com/sagemath/cypari2/issues/107 ?

Le 15/05/2022 à 05:06, 'Travis Scrimshaw' via sage-devel a écrit :

Hi everyone,
On ticket #30423 , Dan, Willie,
and I have been working on a parallel-computation based implementation

for

computing F-matrices that are used in math physics. However, we have been
seeing some doctest failures sporadically that involve segfaults and
linked-list corruption from (cy)PARI. Here are the logs from testing with
the first and the last having full tracebacks.

http://sporadic.stanford.edu/badlog-match
http://sporadic.stanford.edu/badlog
http://sporadic.stanford.edu/badlog1
http://sporadic.stanford.edu/badlog2
http://sporadic.stanford.edu/badlog3

The first question would be if anyone has an idea about what is causing
this. I have this impression that PARI is thread-safe, but I am wondering
if cypari is also thread/parallel-safe or if there are any specific

things

that we should be careful about. (We’ve already had to work around a
pickling issue with polynomials IIRC.)

Second question is that because this is a Heisenbug and I suspect it is
something upstream (and so far, nobody has been able to reproducing it
during an interactive version of Sage), I was wondering what the policy
would be for merging the ticket. I recall in the past that we have merged
tickets with Heisenbugs with followup tickets noting the behavior, but I

am

not 100% sure about that (and I wouldn’t necessarily know how to find any
explicit examples). I was wondering if we could merge the ticket in an
early beta version so that many people/systems can test it to see if it
becomes more reproducible; of course this is assuming that the build bots
are not consistent in reproducing this. Should we just mark any offending
test(s) as “# known bug” and is there some general policy about this?

Thanks,
Travis








--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fd05e9f5-52b2-f2f8-bc02-c968c0a70e79%40gmail.com.

Re: [sage-devel] (cy)PARI in Parallel, Heisenbugs, and Merging Policy

[Vincent Delecroix]

Probably related to https://github.com/sagemath/cypari2/issues/107 ?

Le 15/05/2022 à 05:06, 'Travis Scrimshaw' via sage-devel a écrit :

Hi everyone,
On ticket #30423 , Dan, Willie,
and I have been working on a parallel-computation based implementation for
computing F-matrices that are used in math physics. However, we have been
seeing some doctest failures sporadically that involve segfaults and
linked-list corruption from (cy)PARI. Here are the logs from testing with
the first and the last having full tracebacks.

http://sporadic.stanford.edu/badlog-match
http://sporadic.stanford.edu/badlog
http://sporadic.stanford.edu/badlog1
http://sporadic.stanford.edu/badlog2
http://sporadic.stanford.edu/badlog3

The first question would be if anyone has an idea about what is causing
this. I have this impression that PARI is thread-safe, but I am wondering
if cypari is also thread/parallel-safe or if there are any specific things
that we should be careful about. (We’ve already had to work around a
pickling issue with polynomials IIRC.)

Second question is that because this is a Heisenbug and I suspect it is
something upstream (and so far, nobody has been able to reproducing it
during an interactive version of Sage), I was wondering what the policy
would be for merging the ticket. I recall in the past that we have merged
tickets with Heisenbugs with followup tickets noting the behavior, but I am
not 100% sure about that (and I wouldn’t necessarily know how to find any
explicit examples). I was wondering if we could merge the ticket in an
early beta version so that many people/systems can test it to see if it
becomes more reproducible; of course this is assuming that the build bots
are not consistent in reproducing this. Should we just mark any offending
test(s) as “# known bug” and is there some general policy about this?

Thanks,
Travis




--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c6f8db11-1f7d-2ce3-5550-1cd3a776a8ce%40gmail.com.

Re: [sage-devel] Jupyter Notebook requires Javascript

[Vincent Delecroix]

Dear Phiho,

Please post your question on sage-support mailing list or the
forum  https://ask.sagemath.org/questions/. The sage-devel
mailing list is, as its name suggests, about sage development.

Best
Vincent

Le 10/05/2022 à 07:28, ph h a écrit :

Dear All,

This does not seem to work with IE on Windows Server 2019 Version 1809?

These steps were followed:

1.

Click Tools > Internet Options.

2.

Click the Security tab > Custom Level.

3.

In the Scripting section, click Enable for Active Scripting.

4.

In the dialog box that displays, click Yes.

How can Chrome be used by Jupyter Notebook at start up?


Thank you for your help.

Regards,

phiho

[image: JupyterNotebookRequiresJavaScript.jpg]



--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f898e5b4-13ca-f6ad-9301-f3bc49202ca3%40gmail.com.

Re: [sage-devel] The SageMath developer map needs your (updated) information

[Vincent Delecroix]

It would be cool to have map locators for the quadruple

   (person, time, affiliation, trac id)

(no affiliation being an option). That way we could make many
maps out of one. And in particular visualize the evolution of
sage development.

Vincent

Le 09/05/2022 à 09:59, David Roe a écrit :

For former contributors who are no longer active, do we have a policy about
saying their current institution/company versus where they were when they
were contributing to Sage?
David

On Mon, May 9, 2022 at 3:51 AM Dima Pasechnik  wrote:


On Sun, May 8, 2022 at 9:51 PM Matthias Koeppe 
wrote:


https://www.sagemath.org/development-map.html

To add yourself or to update your information: edit

https://github.com/sagemath/website/blob/master/conf/contributors.xml and
send a pull request

there are lots of  `http:` URLs there which should become `https:`
Also, some contributors don't have their trac logins mentioned.





--
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.

To view this discussion on the web visit

https://groups.google.com/d/msgid/sage-devel/019ca0a8-5d4c-45d2-8505-1a548bbe98een%40googlegroups.com
.

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CAAWYfq1b0j6t-Z0cR8bBzv7CDK8bGwvXooSeqe7SLjTSZdu_NQ%40mail.gmail.com
.





--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b044b5a2-c564-5db4-1e5b-4c851313b4ed%40gmail.com.

Re: [sage-devel] Closing the old Sage wiki

[Vincent Delecroix]

On the other hand, it was not clear to me that we would
keep trac forever (eg moving to gitlab or github was
mentioned several times). Migrating the wiki as you propose
will make it harder to leave trac.

1) If it is just a problem of "login with github", why can't we
provide github login to the wiki?

2) I don't understand why outdated content is a reason to move
the wiki. Just delete or update the content seems a more
reasonable option to me.

3) Regarding history : the trac wiki appeared *after* the
wiki.sagemath.org.

Unless there is a good reason to do so, let us not migrate the
original Sage wiki.

Vincent

Le 18/04/2022 à 20:45, Matthias Koeppe a écrit :

Let's get rid of the old Sage wiki (https://wiki.sagemath.org/SageWiki).

1) It excludes new and newish developers who do not have the required
legacy trac account but log in to Trac using their GitHub accounts.
2) It has very little non-outdated content (see below) -- it reflects
poorly on the project.
3) We already have another Wiki as part of the Trac
server. https://trac.sagemath.org/wiki/WikiStart

Steps done:
a) I went through in the last few weeks and reviewed and then deleted many
wildly outdated pages and pages that only duplicated information that is
available in our
manuals. https://wiki.sagemath.org/RecentChanges?max_days=90
b) I have migrated https://wiki.sagemath.org/ReleaseTours/sage-9.6
and https://wiki.sagemath.org/patchbot (and subpages) to the Trac wiki.

To do:
c) Migrate some info to our documentation
- see for example https://trac.sagemath.org/ticket/30500 on IDE & text
editor configuration
d) Migrate the rest of the pages to the Trac wiki -
https://trac.sagemath.org/ticket/33725
- for example the archive of SageDays activities




--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1afbc590-80f9-2b2a-cfc0-60ddd3dc2126%40gmail.com.

Re: [sage-devel] question on Python version when installing 9.6 beta 7

[Vincent Delecroix]

You could install the python3-dev Ubuntu package to fix the issue.

Le 08/04/2022 à 05:32, 'Nasser M. Abbasi' via sage-devel a écrit :

looking at config.log, it rejected the python version Python 3.10.4 I had
because of this

##  ##
## Checking whether SageMath should install SPKG python3... ##
##  ##
configure:31945: checking whether any of bzip2 liblzma libffi is installed
as or will be installed as SPKG
configure:31954: result: no
configure:31958: checking for python3 >= 3.7.0, < 3.11.0 with modules
sqlite3, ctypes, math, hashlib, crypt, socket, zlib, distutils.core, ssl
configure:32625: result:
configure:32649: checking ... whether /bin/python3 is good
CC=gcc CXX=g++ -std=gnu++11 conftest_venv/bin/python3 conftest.py --verbose
build --build-base=conftest.dir
/mnt/g/nabbasi/data/CDROM/sagemath/sage-9.6.beta7/conftest.py:1:
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
from distutils.core import setup
running build
running build_ext
building 'config_check_distutils' extension
creating conftest.dir
creating conftest.dir/temp.linux-x86_64-3.10
gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
-fstack-protector-strong -Wformat -Werror=format-security -g
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/mnt/g/nabbasi/data/CDROM/sagemath/sage-9.6.beta7/conftest_venv/include
-I/usr/include/python3.10 -c conftest.c -o
conftest.dir/temp.linux-x86_64-3.10/conftest.o
conftest.c:75:10: fatal error: Python.h: No such file or directory
75 | #include 
| ^~
compilation terminated.
error: command '/bin/gcc' failed with exit code 1
configure:33213: result: no, the version is in the supported range, and the
modules can be imported, but distutils cannot build a C extension
configure:32649: checking ... whether /usr/bin/python3 is good
CC=gcc CXX=g++ -std=gnu++11 conftest_venv/bin/python3 conftest.py --verbose
build --build-base=conftest.dir
/mnt/g/nabbasi/data/CDROM/sagemath/sage-9.6.beta7/conftest.py:1:
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
from distutils.core import setup
running build
running build_ext
building 'config_check_distutils' extension
creating conftest.dir
creating conftest.dir/temp.linux-x86_64-3.10
gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
-fstack-protector-strong -Wformat -Werror=format-security -g
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/mnt/g/nabbasi/data/CDROM/sagemath/sage-9.6.beta7/conftest_venv/include
-I/usr/include/python3.10 -c conftest.c -o
conftest.dir/temp.linux-x86_64-3.10/conftest.o
conftest.c:75:10: fatal error: Python.h: No such file or directory
75 | #include 
| ^~
compilation terminated.
error: command '/bin/gcc' failed with exit code 1
configure:33213: result: no, the version is in the supported range, and the
modules can be imported, but distutils cannot build a C extension
configure:33271: result:
configure:33275: to try to use a different system python, use ./configure
--with-python=/path/to/python
configure:33302: no suitable system package found for SPKG python3



On Thursday, April 7, 2022 at 11:18:56 AM UTC-5 dim...@gmail.com wrote:


On Thu, Apr 7, 2022 at 4:41 PM 'Nasser M. Abbasi' via sage-devel
 wrote:


Here is the information you asked for


which python3

/bin/python3


python3 --version

Python 3.10.4


which python

/bin/python


python --version

Python 3.10.4





Thanks.
How about config.log?
I suppose your python3 is rejected as it does not have all the
required by Sage modules
installed. (Or its other dependencies are not fully installed)

At the end of the run of ./configure there is a message printed with
recommendations
what you should install system-wide.
In particular, you should run

sudo apt-get libffi-dev libbz2-dev bzip2 xz-utils liblzma-dev






On Thursday, April 7, 2022 at 3:39:03 AM UTC-5 dim...@gmail.com wrote:


On Thu, Apr 7, 2022 at 9:01 AM Dima Pasechnik  wrote:


On Thu, Apr 7, 2022 at 6:17 AM 'Nasser M. Abbasi' via sage-devel
 wrote:


Basic question:

I Downloaded beta 7 source code. When I do ./configure, it tells me

that it wants to install Python 3-3.1.0.3 since no suitable one found.


However, I have Python 3.10.4 installed.
So why is it building [python3-3.10.3] ?


which python

/bin/python

python --version

Python 3.10.4


the tests in ./configure are for python3, not python

What's the output of

which python3

?


also, check

python3 --version


In any case, if you're still stuck, please post the top-level config.log











I am on Ubuntu 20.04

I hope this Python it is building will not interfere with my own

Python after installation of sagemath when it is done building?


--Nasser

Re: [sage-devel] ERROR In function "is_prime"

[Vincent Delecroix]

Which version of sage are you using?

In a console I get

sage: k=ZZ(18878585599102049192211644417)
sage: k.is_prime()
True
sage: GF(k)
Finite Field of size 18878585599102049192211644417


Le 02/04/2022 à 02:30, carlos ortiz a écrit :

The number:

18878585599102049192211644417 = 61*2^88+1

but in sage:

k=ZZ(18878585599102049192211644417)

k.is_prime()

True

k.factor()

18878585599102049192211644417

F = FiniteField(18)

raise ValueError("the order of a finite field must be a prime power")


Howeve,

F=FiniteField(18878585599102049192211644417)

F

Finite Field of size 18878585599102049192211644417

The above functions generate error for this number

















--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/802c6049-64ed-6f71-2617-389f169cfb8d%40gmail.com.

[sage-devel] conventions about X.Graded() categories

[Vincent Delecroix]

Dear all,

While fixing #33499 I wanted to implement a generic version at the level
of categories (namely inside graded algebras). However, I did not find a
place with the specifications of the Graded axiom... In particular
- how do we specify the grading semi-ring on parents?
- how do we access the homogenous components on elements?

Best
Vincent

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/329a0c0c-70e7-ef2c-7456-cbc1074073fd%40gmail.com.

[sage-devel] %lsmagic broken in sage interpreter

[Vincent Delecroix]

Dear all,

The IPython magic %lsmagic is supposed to list the available
magic functions. However, this does not seem to work within
the sage interpreter

$ sage -ipython
[1]: %lsmagic
Available line magics:
%alias  %alias_magic  %autoawait ...

But

$ sage
sage: %lsmagic


Any idea on what is going wrong?

Vincent

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d80e565a-b835-be04-12ea-5affcb1b3a6d%40gmail.com.

Re: [sage-devel] Can we restore `mean`?

[Vincent Delecroix]

Le 13/02/2022 à 22:21, Matthias Koeppe a écrit :

On Sunday, February 13, 2022 at 12:58:41 PM UTC-8 David Roe wrote:


The documentation of Python's statistics module notes that "Unless
explicitly noted, these functions support int, float, Decimal and Fraction.
Behaviour with other types (whether in the numeric tower or not) is
currently unsupported. Collections with a mix of types are also undefined
and implementation-dependent."



Yes, they need the Sage community's input to develop this further.


Please review #33453 that does restore a mean and median into the global
namespace.

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ccaf3ecf-a116-f533-4d79-18f344719c4c%40gmail.com.

[sage-devel] documentation build complains about database Cremona (9.6.beta3)

[Vincent Delecroix]

Dear all,

On a Ubuntu 20.04, documentation builds stops with

[sagemath_doc_html-none] [plotting ]   File 
"/home/debian/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/features/__init__.py", 
line 559, in absolute_path

[sagemath_doc_html-none] [plotting ] raise FeatureNotPresentError(self,
[sagemath_doc_html-none] [plotting ] 
sage.features.FeatureNotPresentError: database_cremona_mini_ellcurve is 
not available.
[sagemath_doc_html-none] [plotting ] 'cremona_mini.db' not found in any 
of ['/home/debian/sage/local/share/cremona']
[sagemath_doc_html-none] [plotting ] No equivalent system packages for 
debian are known to Sage.
[sagemath_doc_html-none] [plotting ] To install 
database_cremona_mini_ellcurve using the Sage package manager, you can 
try to run:

[sagemath_doc_html-none] [plotting ]   !sage -i database_cremona_ellcurve
[sagemath_doc_html-none] [plotting ] No equivalent system packages for 
pip are known to Sage.
[sagemath_doc_html-none] [plotting ] Further installation instructions 
might be available at https://github.com/JohnCremona/ecdata.
[sagemath_doc_html-none] [plotting ] The inventory files are in 
local/share/doc/sage/inventory/en/reference/plotting.

[sagemath_doc_html-none] Error building the documentation.

See also attached log. Any hint about what happened?

Best
Vincent

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/53c54ac4-dfed-dbbc-1e07-f217b6f8fb6a%40gmail.com.

Re: [sage-devel] Possible bug: specifying category messes up coercion?

[Vincent Delecroix]

There is an explanation and a "solution" on the ticket.

Best
Vincent

Le 03/02/2022 à 23:48, Akos M a écrit :

Replacing 0 with self.zero() works perfectly, thank you!

Best,
Akos

On Thursday, February 3, 2022 at 11:34:43 PM UTC+1 Akos M wrote:


Thanks for the feedback.

Indeed, defined as such, C is a broken object - this was just the smallest
example where I could reproduce the error.

I was hoping that it should be possible to access the module elements
without referring to 1, or multiplication.
I would like to define multiplication later in the definition of some
algebraic structure, but still inherit the methods from the category.
(Similarly to
https://doc.sagemath.org/html/en/thematic_tutorials/coercion_and_categories.html
)

In particular, the error originally appeared in the form of
"if x == 0:"
where x is an element of the module, as should be 0 (now coerced..).

Best,
Akos
On Thursday, February 3, 2022 at 10:10:29 PM UTC+1 vdelecroix wrote:


Now I am thinking about it, I am not sure it is a bug. You did
not defined any algebra structure (neither the unit nor the
product on the basis). C is definitely a broken object.

However, it would make sense for C(0) not to call C(1).

Vincent

Le 03/02/2022 à 21:49, Akos M a écrit :

Thanks, I created - my first - ticket.
https://trac.sagemath.org/ticket/33285#ticket

Once the ticket is (eventually) resolved, how do I update sage to

involve

the resolution?

Thanks,
Akos

On Thursday, February 3, 2022 at 1:39:10 PM UTC+1 vdelecroix wrote:


It is definitely a bug. Do you know how to open
a ticket on the trac server ?

The infinite loop comes from C.one() calling C(1)
calling C.one()... When you specify a category
the inheritance is different and this explains
the difference of behaviour.

Best
Vincent

Le 03/02/2022 à 11:29, Akos M a écrit :



Hi,

The snippet
D = CombinatorialFreeModule(ZZ, [1,2]) D(0)

works fine, however
C = CombinatorialFreeModule(ZZ, [1,2],

category=AlgebrasWithBasis(ZZ))

C(0)


gets into an infinite loop:
File




"/opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/categories/magmas.py",


line 488, in one return self(1) File "sage/structure/parent.pyx",

line

900,

in sage.structure.parent.Parent.__call__
(build/cythonized/sage/structure/parent.c:9218) return mor._call_(x)

File

"sage/categories/map.pyx", line 1694, in
sage.categories.map.FormalCompositeMap._call_
(build/cythonized/sage/categories/map.c:11607) x = f._call_(x) File
"sage/categories/morphism.pyx", line 549, in
sage.categories.morphism.SetMorphism._call_
(build/cythonized/sage/categories/morphism.c:8489) cpdef Element
_call_(self, x): File "sage/categories/morphism.pyx", line 568, in
sage.categories.morphism.SetMorphism._call_
(build/cythonized/sage/categories/morphism.c:8439) return

self._function(x)

File




"/opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/categories/unital_algebras.py",


line 70, in from_base_ring return self.one()._lmul_(r) File
"sage/misc/cachefunc.pyx", line 2310, in
sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__
(build/cythonized/sage/misc/cachefunc.c:12712) self.cache =
f(self._instance)

Why is this? Is this expected behaviour?
(Also asked on:




https://ask.sagemath.org/question/60903/possible-bug-specifying-category-messes-up-coercion/

)


Thanks,
Akos













--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/bd089958-fbd3-056a-72c9-1f3fa0bfb1e3%40gmail.com.

Re: [sage-devel] Possible bug: specifying category messes up coercion?

[Vincent Delecroix]

Now I am thinking about it, I am not sure it is a bug. You did
not defined any algebra structure (neither the unit nor the
product on the basis). C is definitely a broken object.

However, it would make sense for C(0) not to call C(1).

Vincent

Le 03/02/2022 à 21:49, Akos M a écrit :

Thanks, I created - my first - ticket.
https://trac.sagemath.org/ticket/33285#ticket

Once the ticket is (eventually) resolved, how do I update sage to involve
the resolution?

Thanks,
Akos

On Thursday, February 3, 2022 at 1:39:10 PM UTC+1 vdelecroix wrote:


It is definitely a bug. Do you know how to open
a ticket on the trac server ?

The infinite loop comes from C.one() calling C(1)
calling C.one()... When you specify a category
the inheritance is different and this explains
the difference of behaviour.

Best
Vincent

Le 03/02/2022 à 11:29, Akos M a écrit :



Hi,

The snippet
D = CombinatorialFreeModule(ZZ, [1,2]) D(0)

works fine, however
C = CombinatorialFreeModule(ZZ, [1,2], category=AlgebrasWithBasis(ZZ))

C(0)


gets into an infinite loop:
File


"/opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/categories/magmas.py",

line 488, in one return self(1) File "sage/structure/parent.pyx", line

900,

in sage.structure.parent.Parent.__call__
(build/cythonized/sage/structure/parent.c:9218) return mor._call_(x) File
"sage/categories/map.pyx", line 1694, in
sage.categories.map.FormalCompositeMap._call_
(build/cythonized/sage/categories/map.c:11607) x = f._call_(x) File
"sage/categories/morphism.pyx", line 549, in
sage.categories.morphism.SetMorphism._call_
(build/cythonized/sage/categories/morphism.c:8489) cpdef Element
_call_(self, x): File "sage/categories/morphism.pyx", line 568, in
sage.categories.morphism.SetMorphism._call_
(build/cythonized/sage/categories/morphism.c:8439) return

self._function(x)

File


"/opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/categories/unital_algebras.py",

line 70, in from_base_ring return self.one()._lmul_(r) File
"sage/misc/cachefunc.pyx", line 2310, in
sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__
(build/cythonized/sage/misc/cachefunc.c:12712) self.cache =
f(self._instance)

Why is this? Is this expected behaviour?
(Also asked on:


https://ask.sagemath.org/question/60903/possible-bug-specifying-category-messes-up-coercion/
)


Thanks,
Akos







--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a88b1d6a-5632-df2d-8b47-06d6badaf67f%40gmail.com.

Re: [sage-devel] Possible bug: specifying category messes up coercion?

[Vincent Delecroix]

Thanks for creating the ticket.

Once the ticket is solved there are two routes to obtain a
version of SageMath including the fix.

* Either you obtain the corresponding git branch that will be
  attached to the ticket and compile this version of the source
  code

* Or wait for a release of SageMath that will include the fix

But first things first : the issue has to be solved!

Best
Vincent

Le 03/02/2022 à 21:49, Akos M a écrit :

Thanks, I created - my first - ticket.
https://trac.sagemath.org/ticket/33285#ticket

Once the ticket is (eventually) resolved, how do I update sage to involve
the resolution?

Thanks,
Akos

On Thursday, February 3, 2022 at 1:39:10 PM UTC+1 vdelecroix wrote:


It is definitely a bug. Do you know how to open
a ticket on the trac server ?

The infinite loop comes from C.one() calling C(1)
calling C.one()... When you specify a category
the inheritance is different and this explains
the difference of behaviour.

Best
Vincent

Le 03/02/2022 à 11:29, Akos M a écrit :



Hi,

The snippet
D = CombinatorialFreeModule(ZZ, [1,2]) D(0)

works fine, however
C = CombinatorialFreeModule(ZZ, [1,2], category=AlgebrasWithBasis(ZZ))

C(0)


gets into an infinite loop:
File


"/opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/categories/magmas.py",

line 488, in one return self(1) File "sage/structure/parent.pyx", line

900,

in sage.structure.parent.Parent.__call__
(build/cythonized/sage/structure/parent.c:9218) return mor._call_(x) File
"sage/categories/map.pyx", line 1694, in
sage.categories.map.FormalCompositeMap._call_
(build/cythonized/sage/categories/map.c:11607) x = f._call_(x) File
"sage/categories/morphism.pyx", line 549, in
sage.categories.morphism.SetMorphism._call_
(build/cythonized/sage/categories/morphism.c:8489) cpdef Element
_call_(self, x): File "sage/categories/morphism.pyx", line 568, in
sage.categories.morphism.SetMorphism._call_
(build/cythonized/sage/categories/morphism.c:8439) return

self._function(x)

File


"/opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/categories/unital_algebras.py",

line 70, in from_base_ring return self.one()._lmul_(r) File
"sage/misc/cachefunc.pyx", line 2310, in
sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__
(build/cythonized/sage/misc/cachefunc.c:12712) self.cache =
f(self._instance)

Why is this? Is this expected behaviour?
(Also asked on:


https://ask.sagemath.org/question/60903/possible-bug-specifying-category-messes-up-coercion/
)


Thanks,
Akos







--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6dde336c-2c69-3e56-be9d-3ac485bf983e%40gmail.com.

Re: [sage-devel] Possible bug: specifying category messes up coercion?

[Vincent Delecroix]

It is definitely a bug. Do you know how to open
a ticket on the trac server ?

The infinite loop comes from C.one() calling C(1)
calling C.one()... When you specify a category
the inheritance is different and this explains
the difference of behaviour.

Best
Vincent

Le 03/02/2022 à 11:29, Akos M a écrit :



Hi,

The snippet
D = CombinatorialFreeModule(ZZ, [1,2]) D(0)

works fine, however
C = CombinatorialFreeModule(ZZ, [1,2], category=AlgebrasWithBasis(ZZ)) C(0)

gets into an infinite loop:
File
"/opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/categories/magmas.py",
line 488, in one return self(1) File "sage/structure/parent.pyx", line 900,
in sage.structure.parent.Parent.__call__
(build/cythonized/sage/structure/parent.c:9218) return mor._call_(x) File
"sage/categories/map.pyx", line 1694, in
sage.categories.map.FormalCompositeMap._call_
(build/cythonized/sage/categories/map.c:11607) x = f._call_(x) File
"sage/categories/morphism.pyx", line 549, in
sage.categories.morphism.SetMorphism._call_
(build/cythonized/sage/categories/morphism.c:8489) cpdef Element
_call_(self, x): File "sage/categories/morphism.pyx", line 568, in
sage.categories.morphism.SetMorphism._call_
(build/cythonized/sage/categories/morphism.c:8439) return self._function(x)
File
"/opt/sagemath-9.0/local/lib/python3.7/site-packages/sage/categories/unital_algebras.py",
line 70, in from_base_ring return self.one()._lmul_(r) File
"sage/misc/cachefunc.pyx", line 2310, in
sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__
(build/cythonized/sage/misc/cachefunc.c:12712) self.cache =
f(self._instance)

Why is this? Is this expected behaviour?
(Also asked on:
https://ask.sagemath.org/question/60903/possible-bug-specifying-category-messes-up-coercion/)

Thanks,
Akos



--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3ae00851-5b8b-b24f-f771-8624e903a18d%40gmail.com.

Re: [sage-devel] Patchbot/CI improvements

[Vincent Delecroix]

Le 23/01/2022 à 18:35, Matthias Koeppe a écrit :

Patchbot experts:
1) Currently the patchbot does not run on certain tickets that make changes
to build/pkgs, so we do not have automatic testing for these tickets. Is
this something that can be changed?


I would say that this is doable (since if I remember correctly, packages
can be downloaded from their upstream urls). Please open an issue on
sage-patchbot.


2) Can "make doc-pdf" please be added?


It is (sort of) already there

https://github.com/sagemath/sage-patchbot/blob/master/sage_patchbot/plugins.py#L179

That could be activated by default if the experimental status of
this plugin is removed. You can also open an issue.


I don't know if Volker's integration scripts look at the patchbot status at
all, but nevertheless these two changes could improve our workflow.



--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/fbf28c85-4992-a381-f942-204ca6b59217%40gmail.com.

Re: [sage-devel] not easily reproducible QQbar bug

[Vincent Delecroix]

I am not able to reproduce. I ran 1000 times the same code snippet
you provided on all the sage that I have around me. Do you have the
bug in a fresh session  or after some hours of other unrelated
computations? In the first case, you can try to reproduce with

1. In an instance where you have the bug (at the start of a
   fresh session), get the initial random seed with initial_seed()

2. Start a fresh session, set the initial seed with
   set_random_seed(value_from_point_1_above) and rerun
   the code snippet

Best
Vincent

Le 13/01/2022 à 15:16, 'Martin R' via sage-devel a écrit :

ubuntu 21.04
'SageMath version 9.5.beta7, Release Date: 2021-11-18'

On Thursday, 13 January 2022 at 15:09:57 UTC+1 vdelecroix wrote:


Could you be more specific : Which sage version ? which setup ?

Vincent

Le 13/01/2022 à 15:05, 'Martin R' via sage-devel a écrit :

I have some very strange behaviour of a substitution, which I don't know
how to reproduce, but it happens from time to time, and is REALLY
disturbing. I don't even know what to write into a ticket, so I'm asking
here first. The definition of CSP is at the end of the mail.

sage: R. = ZZ[]
sage: p = q^21 + q^20 + q^19 + q^18 + q^17 + q^16 + q^15 + q^14 + q^13 +
q^12 + q^11 + 2*q^10 + 2*q^9 + 2*q^8 + 2*q^7 + 2*q^6 + 2*q^5 + 2*q^4 +
2*q^3 + 2*q^2 + 3*q + 4
sage: p == CSP(22)
True
sage: CSP(22).subs({q:QQbar.zeta(2)})
-28
sage: CSP(22).subs({q:QQbar.zeta(2)})
2
sage: CSP(22).parent()
Univariate Polynomial Ring in q over Integer Ring

Sometimes I also get a complex number.

Martin

###
def cycle_power(g, e):
"""
Return k such that g^k = e
"""
if e.is_one():
return 0
k = 1
p = g
while True:
if e == p:
return k
p *= g
k += 1

@cached_function
def CSP(n):
C = groups.permutation.Cyclic(n)
g = C.gen()
R. = ZZ[]
return sum(q^min(cycle_power(g, e) for e in coset) for H in
C.subgroups() for coset in C.cosets(H))







--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/57c62fad-c645-9883-50c5-3605cb557b5a%40gmail.com.

Re: [sage-devel] not easily reproducible QQbar bug

[Vincent Delecroix]

Could you be more specific : Which sage version ? which setup ?

Vincent

Le 13/01/2022 à 15:05, 'Martin R' via sage-devel a écrit :

I have some very strange behaviour of a substitution, which I don't know
how to reproduce, but it happens from time to time, and is REALLY
disturbing.  I don't even know what to write into a ticket, so I'm asking
here first.  The definition of CSP is at the end of the mail.

sage: R. = ZZ[]
sage: p = q^21 + q^20 + q^19 + q^18 + q^17 + q^16 + q^15 + q^14 + q^13 +
q^12 + q^11 + 2*q^10 + 2*q^9 + 2*q^8 + 2*q^7 + 2*q^6 + 2*q^5 + 2*q^4 +
2*q^3 + 2*q^2 + 3*q + 4
sage: p == CSP(22)
True
sage: CSP(22).subs({q:QQbar.zeta(2)})
-28
sage: CSP(22).subs({q:QQbar.zeta(2)})
2
sage: CSP(22).parent()
Univariate Polynomial Ring in q over Integer Ring

Sometimes I also get a complex number.

Martin

###
def cycle_power(g, e):
 """
 Return k such that g^k = e
 """
 if e.is_one():
 return 0
 k = 1
 p = g
 while True:
 if e == p:
 return k
 p *= g
 k += 1

@cached_function
def CSP(n):
 C = groups.permutation.Cyclic(n)
 g = C.gen()
 R. = ZZ[]
 return sum(q^min(cycle_power(g, e) for e in coset) for H in
C.subgroups() for coset in C.cosets(H))



--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a05289f9-3b44-b4fa-e119-3c8b07c54a39%40gmail.com.

[sage-devel] random doctest failure in BinaryQF.solve_integer

[Vincent Delecroix]

Dear all,

In the following patchbot report

https://patchbot.sagemath.org/log/32553/Linux/1_SMP_Debian_5.10.84-1_(2021-12-08)/x86_64/5.10.0-10-amd64/tmonteil-lxc3/2022-01-04%2017:18:22

one can see

sage -t --long --random-seed=147150541496621216702880946653671608515 
src/sage/quadratic_forms/binary_qf.py

**
File "src/sage/quadratic_forms/binary_qf.py", line 1498, in 
sage.quadratic_forms.binary_qf.BinaryQF.solve_integer

Failed example:
xy is None or Q(*xy) == 0
Expected:
True
Got:
False
**
1 item had failures:
   1 of  12 in sage.quadratic_forms.binary_qf.BinaryQF.solve_integer
[282 tests, 1 failure, 0.41 s]

However this is not reproducible on my machine.

Best
Vincent

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/9c8fa879-5204-43c8-afe3-ed62c20a6bff%40gmail.com.

Re: [sage-devel] settings in github/sagemath

[Vincent Delecroix]

Le 26/12/2021 à 11:28, Dima Pasechnik a écrit :

On Sun, Dec 26, 2021 at 9:42 AM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:


Dear all,

Jeroen kindly transfered pari_jupyter under the sagemath
umbrella at

https://github.com/sagemath/pari_jupyter

However, I do not have enough the administrator rights for
this repo.

* Is there any administrator for the whole github/sagemath
project that can grant me admistrator rights to
pari_jupyter ?

* Would it be possible to become an administrator of the
whole github/sagemath ?


Hi Vincent,
you're now an admin there.


That worked !

Thanks Dima
Vincent

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/82bc51f1-6839-f84f-0ec4-88a115983559%40gmail.com.

[sage-devel] settings in github/sagemath

[Vincent Delecroix]

Dear all,

Jeroen kindly transfered pari_jupyter under the sagemath
umbrella at

  https://github.com/sagemath/pari_jupyter

However, I do not have enough the administrator rights for
this repo.

* Is there any administrator for the whole github/sagemath
  project that can grant me admistrator rights to
  pari_jupyter ?

* Would it be possible to become an administrator of the
  whole github/sagemath ?

Best
Vincent

PS: The up to date version is currently under my
own github at https://github.com/videlec/pari-jupyter

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/83115262-9aa5-ea04-422a-cb7398f6ca8c%40gmail.com.

Re: [sage-devel] patchbots open maxima threads and don't close them

[Vincent Delecroix]

More precisely I had 3 x 3 groups of processes (each time, killing
one of them killed the other 2 in the same group).

Vincent

Le 13/12/2021 à 15:52, Vincent Delecroix a écrit :

Are these really threads? I think they are independent
processes (otherwise they would be closed at the time sage
terminates its test). I observe the same invasion on my
patchbot. But they not only eat memory but also CPU.

Vincent

Le 13/12/2021 à 10:53, 'jonatha...@googlemail.com' via sage-devel a écrit :

Hi there,

I run a patchbot (panke), which completely slowed down because of maxima
threads that ate away my memory. There were like 10 of them. Is this a 
bug?


Killing those threads the patchbot keeps on running just fine. So
apparently, they were really lost.

Jonathan



--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/0afc1d7a-4299-69fc-9c7d-9710feaedc82%40gmail.com.

Re: [sage-devel] patchbots open maxima threads and don't close them

[Vincent Delecroix]

Are these really threads? I think they are independent
processes (otherwise they would be closed at the time sage
terminates its test). I observe the same invasion on my
patchbot. But they not only eat memory but also CPU.

Vincent

Le 13/12/2021 à 10:53, 'jonatha...@googlemail.com' via sage-devel a écrit :

Hi there,

I run a patchbot (panke), which completely slowed down because of maxima
threads that ate away my memory. There were like 10 of them. Is this a bug?

Killing those threads the patchbot keeps on running just fine. So
apparently, they were really lost.

Jonathan



--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/da432d3b-3d88-f40b-2daf-f0796d0aabbd%40gmail.com.

[sage-devel] pari-jupyter is back

[Vincent Delecroix]

Dear all,

The jupyter kernel for PARI/GP developed by Jeroen Demeyer was
not maintained since he left sage development. Together with
the PARI/GP team in Bordeaux I took over the maintainance and
we now have a pari-jupyter 1.4.0 that is compatible with
python 3.9 and PARI 2.13. See

https://pypi.org/project/pari-jupyter/

Best
Vincent

PS: For the time being, the sources are at
https://github.com/videlec/pari-jupyter but it might change in
the near future.

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a4d30ff2-fd66-ca47-edca-851d1170c94c%40gmail.com.

Re: [sage-devel] permission denied on git.trac

[Vincent Delecroix]

All my keys were ssh-rsa. It appears that some server
thinks it is not secure enough. Maybe it is the case
for our git.trac. At least, I generated a ed25519 key
and it now works.

Vincent

Le 25/11/2021 à 19:05, Vincent Delecroix a écrit :



Le 25/11/2021 à 12:18, Dima Pasechnik a écrit :

On Thu, Nov 25, 2021 at 11:08 AM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:


Hello,

Trying to fetch or push to the git server I today get

$ git fetch
g...@trac.sagemath.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


I did not change any ssh key on my computer. Though,
I did reupload them to the trac server user interface
in case something was lost somewhere. But the problem
persists.


recently discussed here:
https://groups.google.com/g/sage-devel/c/7rGuosozeO0/m/8HKnDAi1AgAJ

TL;DR: Either you have very a very old key, of type no longer accepted
by sshd (and so you need to upload a better key), or there is
blacklisting.
I'll reboot the trac server soon, this seems to help with blacklisting.


What is a "very old key"? A ssh key is not supposed to become obsolete.

I did upload a new ssh key and nothing changed as far as "git fetch"
is concerned.

Best
Vincent


--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/153a7967-8349-37ee-c24f-b3c0186bd1ee%40gmail.com.

Re: [sage-devel] permission denied on git.trac

[Vincent Delecroix]

Le 25/11/2021 à 12:18, Dima Pasechnik a écrit :

On Thu, Nov 25, 2021 at 11:08 AM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:


Hello,

Trying to fetch or push to the git server I today get

$ git fetch
g...@trac.sagemath.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


I did not change any ssh key on my computer. Though,
I did reupload them to the trac server user interface
in case something was lost somewhere. But the problem
persists.


recently discussed here:
https://groups.google.com/g/sage-devel/c/7rGuosozeO0/m/8HKnDAi1AgAJ

TL;DR: Either you have very a very old key, of type no longer accepted
by sshd (and so you need to upload a better key), or there is
blacklisting.
I'll reboot the trac server soon, this seems to help with blacklisting.


What is a "very old key"? A ssh key is not supposed to become obsolete.

I did upload a new ssh key and nothing changed as far as "git fetch"
is concerned.

Best
Vincent

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e9c33161-b5d2-d96c-f053-461f1965c948%40gmail.com.

[sage-devel] permission denied on git.trac

[Vincent Delecroix]

Hello,

Trying to fetch or push to the git server I today get

$ git fetch
g...@trac.sagemath.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


I did not change any ssh key on my computer. Though,
I did reupload them to the trac server user interface
in case something was lost somewhere. But the problem
persists.

Any idea?

Best
Vincent

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/935d0579-787f-6f6f-ede4-d09c3eb5034b%40gmail.com.

Re: [sage-devel] making primecount (and its dependency primesieve) standard

[Vincent Delecroix]

+1 for using standard and efficient libraries instead of slow and
buggy sage implementations :-)

Thanks
Vincent

Le 23/11/2021 à 11:26, Dima Pasechnik a écrit :

primecount is a popular C++ library  of efficient procedures to
compute prime_pi(x), i.e. π(x),
number of prime numbers  <=x, and related functions.
It's an optional package now. The repo is
https://github.com/kimwalisch/primecount

The default Sage implementation of prime_pi is buggy, and a very tricky and old
Cython code - see https://trac.sagemath.org/ticket/24960
Replacing it with the primecount implementation is the most direct way
to fix it, and it also
gives huge speedups. For this, primecount should be promoted from
optional to standard.
Primecount has a (vendored by default) dependency, a C++ library primesieve,
even more popular.
Many distros have primesieve as a separate package, so we'd like to split
primesieve off primecount, see https://trac.sagemath.org/ticket/25009

Any objections to this ?
  (any objector volunteers to fix Sage's buggy prime_pi :-))

Thanks,
Dima

PS. in the modularization effort, the Cython interface to primecount will become
a separate PyPI package, work in progress on this is on
https://github.com/dimpase/primecountpy




.



--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2f33258e-3cc6-538c-3044-2b4b40a9111d%40gmail.com.