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

+1 for Github (personally I still prefer Trac, but the bus factor argument and recruitment of new contributors are more important) emanuel.c...@gmail.com schrieb am Freitag, 23. September 2022 um 08:37:26 UTC+2: > +1 for Github > > Also wishing for contingency plan for re-migrating to self-ho

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

+1 for Github Also wishing for contingency plan for re-migrating to self-hosted Gitlab. Le mercredi 21 septembre 2022 à 19:23:36 UTC+2, David Roe a écrit : > Dear Sage developers, > Following extensive discussion, both recently >

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

+1 for Github as I'm new to open source,it would be easy for me to learn and contribute through github as ik some of it it would be awesome On Wednesday, September 21, 2022 at 10:53:36 PM UTC+5:30 David Roe wrote: > Dear Sage developers, > Following extensive discussion, both recently >

[sage-devel] Re: Invitation: Weekly 30-minute Sage developer calls on Jitsi

Starting now On Monday, September 19, 2022 at 9:02:39 PM UTC-7 Matthias Koeppe wrote: > Dear all, > Our first Sage developer calls last Thursday/Friday on Zoom were very > successful! > > We are switching to video conferencing on Jitsi from now on. It is open > source software; see https://jit

Re: [sage-devel] Re: is it intentional that prod does not stop when it hits 0?

Note also that prod(range(1,n)) does *NOT* just multiple 1 times 2 times 3 in order. Instead, it uses a tree approach so that the multiplications involve objects with more balanced sizes, which is much faster, e.g., for large integers multiplyling n*m with n and m having similar sizes can overall

[sage-devel] Re: is it intentional that prod does not stop when it hits 0?

as kcrisman mentions, prod first gathers all the factors before it multiplies them together. It does so for a reason: it takes the product in a balanced fasion; not just going through the factors iteratively. I don't know if it does an early exit if any zeros are encountered, but the strategy o

[sage-devel] Re: is it intentional that prod does not stop when it hits 0?

I'm not sure what you were expecting. It does return 0, but it does so after all the print statements are done. Remember, your "test" function just returns the input, so the map function just returns a list (well, a map object, but ...) and then we prod everything in the list. But that happe

Re: [sage-devel] Re: PARI/GP upgrade to 2.15

On Thu, 22 Sept 2022, 19:21 Antonio Rojas, wrote: > Specifically, help is needed from someone who understands genus2reduction > code in order to solve the (almost) last remaining issue. > I'll take a look tomorrow. John > El jueves, 15 de septiembre de 2022 a las 20:58:19 UTC+2, vdelecroix >

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

+1 for GitHub El jueves, 22 de septiembre de 2022 a las 18:43:02 UTC+2, martinr...@googlemail.com escribió: > +1 for GitHub > > On Wed, Sep 21 2022, David Roe wrote: > > Dear Sage developers, > > Following extensive discussion, both recently > >

[sage-devel] Re: PARI/GP upgrade to 2.15

Specifically, help is needed from someone who understands genus2reduction code in order to solve the (almost) last remaining issue. El jueves, 15 de septiembre de 2022 a las 20:58:19 UTC+2, vdelecroix escribió: > Dear all, > > The PARI/GP team is about to release a new version. I opened a ticke

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

+1 for GitHub On Wed, Sep 21 2022, David Roe wrote: > Dear Sage developers, > Following extensive discussion, both recently > > (prompted > by issues upgrading the trac server) and over >

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

+1 for GitHub Clemens Heuberger Am 21.09.22 um 19:23 schrieb David Roe: Dear Sage developers, Following extensive discussion, both recently  (prompted by issues upgrading the trac server) and over

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

I did not chime in in the long thread leading to the vote, but I am quite used to working with Gitlab (hosted at my university) and would be more comfortable with a Gitlab solution because I have the impression that it gives us more freedom (we currently run our own patchbots, so running our o

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

0(I like trac, but I am unable and unwilling to contribute to it) On Thursday, 22 September 2022 at 16:38:59 UTC+2 tobias...@gmail.com wrote: > +1 for Github > > On Thursday, 22 September 2022 at 14:19:57 UTC+2 Jonathan wrote: > >> +1 for Github >> >> On Thursday, September 22, 2022 at 5:06:0

[sage-devel] is it intentional that prod does not stop when it hits 0?

sage: def test(n): : print("n:", n) : return n : sage: l = [2,3,5,0,7,11,17,19] sage: prod(map(test, l)) n: 2 n: 3 n: 5 n: 0 n: 7 n: 11 n: 17 n: 19 0 I expected that it would return 0 once we multiply with 0. Martin -- You received this message because you are subscribed to

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

+1 for Github On Thursday, 22 September 2022 at 14:19:57 UTC+2 Jonathan wrote: > +1 for Github > > On Thursday, September 22, 2022 at 5:06:02 AM UTC-5 antoine@gmail.com > wrote: > >> +1 for Github >> >> Le jeudi 22 septembre 2022 à 11:38:17 UTC+2, chris wuthrich a écrit : >> >>> >>> 0(No

[sage-devel] Re: Is this a bug?

On Thursday, September 22, 2022 at 5:29:41 AM UTC+2 Travis Scrimshaw wrote: > No, it is not. The generic fraction field can only reduce something up to > a unit since the gcd is defined up to a unit. I agree it looks funny, but I > don't see a sensible way to code to get a negative sign in the n

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

Sage has a tradition of public voting, but I'm fine if people want to email me separately with their vote and I can forward it along. David On Thu, Sep 22, 2022 at 3:22 AM Dima Pasechnik wrote: > Do we require everyone willing to vote to do so on sage-devel, or it > could be done elsewhere (not

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

+1 for Github On Thursday, September 22, 2022 at 5:06:02 AM UTC-5 antoine@gmail.com wrote: > +1 for Github > > Le jeudi 22 septembre 2022 à 11:38:17 UTC+2, chris wuthrich a écrit : > >> >> 0(No real preference and too little understanding of the matter, but >> very happy that we have a

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

+1 for Github Le jeudi 22 septembre 2022 à 11:38:17 UTC+2, chris wuthrich a écrit : > > 0(No real preference and too little understanding of the matter, but > very happy that we have a meaningful vote on things like this.) -- You received this message because you are subscribed to the Goog

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

0(No real preference and too little understanding of the matter, but very happy that we have a meaningful vote on things like this.) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails fro

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

+1 for GitHub On Wednesday, September 21, 2022 at 9:35:07 PM UTC-7 idealpr...@gmail.com wrote: > +1 for GitHub. Mirroring to GitLab can be considered later. > > On Thursday, September 22, 2022 at 8:45:22 AM UTC+5:30 Nathan Dunfield > wrote: > >> +1 for GitHub > > -- You received this message

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

+1 for GitHub, and GitLab mirror later On Wednesday, September 21, 2022 at 7:23:36 PM UTC+2 David Roe wrote: > Dear Sage developers, > Following extensive discussion, both recently > > (prompted > by issues upgrading the tr

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

+1 for GitHub -- 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.goo

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

Do we require everyone willing to vote to do so on sage-devel, or it could be done elsewhere (not every contributor to Sage or its dependencies/packages is there) ? On Wed, Sep 21, 2022 at 6:23 PM David Roe wrote: > > Dear Sage developers, > As announced in a parallel thread, we are voting to mov