I'm going to be on Zulip and working on reviewing some Python 3 tickets. Feel free to join me! David
On Sun, Oct 29, 2017 at 5:33 AM, David Roe <roed.m...@gmail.com> wrote: > Sorry for dropping the ball on organizing these. Based on the results of > the survey, I'm going to propose Monday, November 6 starting at 4pm EST, > 10pm CET. The first topic will be the Python 3 transition: what needs to > be done and how we can get more people involved in the effort. > > If you'd like to participate but don't like the time, please add your > preferences to the survey I sent out earlier. > David > > On Fri, Oct 27, 2017 at 11:53 AM, William Stein <wst...@gmail.com> wrote: > >> On Fri, Oct 27, 2017 at 7:46 AM Emmanuel Charpentier < >> emanuel.charpent...@gmail.com> wrote: >> >>> I used to do a lot of work for Sage - in fact I was at one point in the >>>> top 10% of some list William produced. But now the switch from mercurial to >>>> git, and I'm out of it. There are other reasons in my case - I worked >>>> mainly on the port to Solaris, completed that, but Solaris is no longer >>>> tested or working. >>>> >>> >>> Should it be rekindled ? Or should we stop to claim to support Solaris ? >>> >> >> I personally no longer care about Solaris support for Sage. We used to >> support Solaris before mainly because a paying customer paid us something >> (which made it possible for Michael Abshoff to work on Sage). They are no >> longer paying us, and haven't for many, many year. >> >> >>> >>>> * A DECENT interface to Mathematica, with a proper API, not using >>>> pexpect, which seems to be rather a poor alternative, which is always >>>> breaking. >>>> >>> >>> A good interface to "the competition" is always useful. However, I >>> wouldn't disdain pexpect, which turns out to be surpisingly useful. The >>> current (non-negligible) problems with Mathematica interface seem more >>> related to the lack of proper dictionaries and support functions in Sage >>> (where there are in fact functions to *guess* (!) a translation) than a >>> fundamental interface type problem. A real pair of parsers for what we >>> send to Mathematica and what it returns could be a useful first step... >>> >> >> Emmanuel, you really understand Sage... >> >> William >> -- >> -- William Stein >> >> -- >> 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 post to this group, send email to sage-devel@googlegroups.com. >> Visit this group at https://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.