[sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report
On Friday, June 12, 2015 at 6:27:28 PM UTC-5, William Stein wrote: > > On Fri, Jun 12, 2015 at 1:28 PM, Franco Saliola > wrote: > > > > Here is a mini report on Sage Day 65. I'm not an organizer so this is > not > > official. > > Thanks to Anne Schilling for helping to prepare this. > > > > - 24 tickets on trac are tagged with `sagedays65` or `sd65`. Some of > these > > have > > been positively reviewed and marked as fixed. Some are waiting for > review > > (hint, hint). Several of these tickets include contributions from new > > users. > > > > - Installation troubles: > > > > - several people had a hard difficult time installing Sage on their > > machines (8-10 people) > > > > - there were people who did not have a working development version > on > > their > > machines by the end of the week (4-5 people); two of these people > were > > the organizers of the Sage Days > > This is a bummer. It gives me even more motivation to make > SageMathCloud Sage-developer friendly.I'm also curious if anybody > has any -- possibly *radical* -- suggestions about how to address this > problem using new ideas. > Most of these problems were related to installing on Macs: various different OS versions (10.10, 10.9, 10.8, ...); XCode versions; command line tools out of date; Perhaps an enhanced build test system might help. Some ideas (mostly questions): (1) Would it be possible to maintain a list of known compilation errors? The build process could check online if the error message matches one of the known issues and then return links to a page with information (possible workarounds, appropriate trac tickets)? (2) Could we release bundles or dmgs or whatever they are called for the *developer* version for OS X? (3) A computer scientist who participated in part of the Sage Days said that perhaps using Travis CI could help with some of this. I don't know anything about this, but maybe someone with Travis experience could say whether this might help? Franco -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report
> If you are asking for ideas, I'm wondering: how hard would it be to > give the user better information and better options in the case when a > Sage install fails due to a package? > I'll add a +1 for this idea. I helped Stephen Doty install the development version of Sage on his machine while we were there and the process involved asking for help at sage-devel. https://groups.google.com/forum/?fromgroups#!topic/sage-devel/_jY4yj9NcZc There was a simple fix and a quick response, but I had to know who and where to ask. -Mike -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report
On Friday, June 12, 2015, Anne Schilling wrote: > Actually, Peter Tingley's Sage was not working due to some git problems > (committing on top of the develop branch)! That has been fixed. So it was > not really an install problem. > > The SageMathCloud was great for those who had trouble installing Sage on > their own computer. Sometimes we had connection issues to the SMC (the > wheel was just spinning). Franco gave a nice talk on how A fixed a bug that causes this today. Email me if you see it > to copy the latest version onto one's own Sage developer project. That > saves to actually run the install (so Darij, your "complaints" are not > really valid since copying only takes a few minutes). > > Best, > > Anne > > > > > On Jun 12, 2015, at 18:26, William Stein > wrote: > > > >> On Fri, Jun 12, 2015 at 1:28 PM, Franco Saliola > wrote: > >> > >> Here is a mini report on Sage Day 65. I'm not an organizer so this is > not > >> official. > >> Thanks to Anne Schilling for helping to prepare this. > >> > >> - 24 tickets on trac are tagged with `sagedays65` or `sd65`. Some of > these > >> have > >> been positively reviewed and marked as fixed. Some are waiting for > review > >> (hint, hint). Several of these tickets include contributions from new > >> users. > >> > >> - Installation troubles: > >> > >>- several people had a hard difficult time installing Sage on their > >> machines (8-10 people) > >> > >>- there were people who did not have a working development version on > >> their > >> machines by the end of the week (4-5 people); two of these people > were > >> the organizers of the Sage Days > > > > This is a bummer. It gives me even more motivation to make > > SageMathCloud Sage-developer friendly.I'm also curious if anybody > > has any -- possibly *radical* -- suggestions about how to address this > > problem using new ideas. > > > > > >> > >>- number of participants: 40 > >> > >>- some thing that really helped was the Sage Development Images > project > >> > >> - A possible warning to future organizers of Sage Days: We had good > internet > >> access, but the university network blocked all ssh connections! This > was > >> mainly resolved on the first day, but there were still some issues with > >> pulling/pushing through the `git trac` command. > >> > >> Franco > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "sage-combinat-devel" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an > >> email to sage-combinat-devel+unsubscr...@googlegroups.com > . > >> To post to this group, send email to > sage-combinat-de...@googlegroups.com . > >> Visit this group at http://groups.google.com/group/sage-combinat-devel. > >> For more options, visit https://groups.google.com/d/optout. > > > > > > > > -- > > William (http://wstein.org) > > > > -- > > You received this message because you are subscribed to the Google > Groups "sage-combinat-devel" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to sage-combinat-devel+unsubscr...@googlegroups.com > . > > To post to this group, send email to > sage-combinat-de...@googlegroups.com . > > Visit this group at http://groups.google.com/group/sage-combinat-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 http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- Sent from my massive iPhone 6 plus. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report
Actually, Peter Tingley's Sage was not working due to some git problems (committing on top of the develop branch)! That has been fixed. So it was not really an install problem. The SageMathCloud was great for those who had trouble installing Sage on their own computer. Sometimes we had connection issues to the SMC (the wheel was just spinning). Franco gave a nice talk on how to copy the latest version onto one's own Sage developer project. That saves to actually run the install (so Darij, your "complaints" are not really valid since copying only takes a few minutes). Best, Anne > On Jun 12, 2015, at 18:26, William Stein wrote: > >> On Fri, Jun 12, 2015 at 1:28 PM, Franco Saliola wrote: >> >> Here is a mini report on Sage Day 65. I'm not an organizer so this is not >> official. >> Thanks to Anne Schilling for helping to prepare this. >> >> - 24 tickets on trac are tagged with `sagedays65` or `sd65`. Some of these >> have >> been positively reviewed and marked as fixed. Some are waiting for review >> (hint, hint). Several of these tickets include contributions from new >> users. >> >> - Installation troubles: >> >>- several people had a hard difficult time installing Sage on their >> machines (8-10 people) >> >>- there were people who did not have a working development version on >> their >> machines by the end of the week (4-5 people); two of these people were >> the organizers of the Sage Days > > This is a bummer. It gives me even more motivation to make > SageMathCloud Sage-developer friendly.I'm also curious if anybody > has any -- possibly *radical* -- suggestions about how to address this > problem using new ideas. > > >> >>- number of participants: 40 >> >>- some thing that really helped was the Sage Development Images project >> >> - A possible warning to future organizers of Sage Days: We had good internet >> access, but the university network blocked all ssh connections! This was >> mainly resolved on the first day, but there were still some issues with >> pulling/pushing through the `git trac` command. >> >> Franco >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-combinat-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-combinat-devel+unsubscr...@googlegroups.com. >> To post to this group, send email to sage-combinat-de...@googlegroups.com. >> Visit this group at http://groups.google.com/group/sage-combinat-devel. >> For more options, visit https://groups.google.com/d/optout. > > > > -- > William (http://wstein.org) > > -- > You received this message because you are subscribed to the Google Groups > "sage-combinat-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-combinat-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-combinat-de...@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-combinat-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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Sage Days 65 mini report
- Installation troubles: > > - several people had a hard difficult time installing Sage on their > machines (8-10 people) > > - there were people who did not have a working development version on > their > machines by the end of the week (4-5 people); two of these people > were > the organizers of the Sage Days > That's troubling - we've usually been able to get everyone set up, even with very strange proxy settings at Sage Days 60 (which I was not the one who figured out how to fix). Can you specify exactly what sort of problems you had, on which platforms, etc.? -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: revisions to sandpiles needs review
I have two bright former students who would probably be willing to help. One is in currently in the CS program at UW and the other will start the PhD program in math at Berkeley next fall. Both know sandpile theory well (the former is a co-author), and both have experience using the Sage, especially the sandpile functionality. The former student helped develop the hyperplanes code in Sage. What if they would be willing to systematically review my revisions according to the usual conventions (e.g., http://doc.sagemath.org/html/en/developer/reviewer_checklist.html#chapter-review)? Does this seem like a reasonable way to proceed? On Friday, June 12, 2015 at 10:24:46 AM UTC-7, kcrisman wrote: > > >> The guideline is not a rule, but it has not been put there for no >> reason either. I have had to do *very* long reviews of a diff that >> wasn't half as long as yours. I certainly would not start another one >> when, from the look of your diff file, the changes are so unrelated >> that you could have split it in 5 different tickets easily. Though >> Karl-Dieter is more optimistic, and may have more time for it. >> >> > I don't know anything about sandpiles except the ones at our beach. But > in this case I would not be surprised if there were people who cared enough > about it - and about accurate code - that this could get reviewed. > > David (P.), one thing you could do to help that is to make a comment on > your ticket (or edit the description) to make it clear which line numbers > etc. would be self-contained review units. Then someone could review a > piece at a time, at least mentally. > > There is also "git add -p" which apparently allows you to decide which > hunks (in the patch sense) you want to add to a commit, and you could break > your branch up into smaller "bite-sized" chunks that way. See > https://cbx33.github.io/gitt/afterhours5-1.html for a pretty informative > post that continues to affirm my contention that git does way too many > things with way too few commands :) But I am not a git expert and have > never tried this, so I can't say how annoying that might be. Still, it > could be a way to at least break this ticket into more easily reviewable > commits without actually making separate branches. > > - kcrisman > -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report
On Sat, Jun 13, 2015 at 1:26 AM, William Stein wrote: > This is a bummer. It gives me even more motivation to make > SageMathCloud Sage-developer friendly.I'm also curious if anybody > has any -- possibly *radical* -- suggestions about how to address this > problem using new ideas. +1 for a friendlier SMC; I definitely wouldn't mind it not falling asleep on compile :) If you are asking for ideas, I'm wondering: how hard would it be to give the user better information and better options in the case when a Sage install fails due to a package? In many cases the actual errors are laughable and the packages far from crucial; particularly optional packages shouldn't be causing a build to break! I don't know how flexible makefiles are, but I would love it to wrap the installation of a package in a way like this: - If the package installs fine, do nothing extra. - If it does not, add a clear error at the end of the log, naming the package and the version. Name the other packages which depend on the one that didn't install. Tell the user how to sidestep the installation of the package (at their own risk). Mention the email addresses of the people that should care about the problem (package maintainer, build manager, sagedevel?) and what to send them. - Allow the user to pull an older version of the package. Would this be difficult? Best regards, Darij -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: [sage-combinat-devel] Sage Days 65 mini report
On Fri, Jun 12, 2015 at 1:28 PM, Franco Saliola wrote: > > Here is a mini report on Sage Day 65. I'm not an organizer so this is not > official. > Thanks to Anne Schilling for helping to prepare this. > > - 24 tickets on trac are tagged with `sagedays65` or `sd65`. Some of these > have > been positively reviewed and marked as fixed. Some are waiting for review > (hint, hint). Several of these tickets include contributions from new > users. > > - Installation troubles: > > - several people had a hard difficult time installing Sage on their > machines (8-10 people) > > - there were people who did not have a working development version on > their > machines by the end of the week (4-5 people); two of these people were > the organizers of the Sage Days This is a bummer. It gives me even more motivation to make SageMathCloud Sage-developer friendly.I'm also curious if anybody has any -- possibly *radical* -- suggestions about how to address this problem using new ideas. > > - number of participants: 40 > > - some thing that really helped was the Sage Development Images project > > - A possible warning to future organizers of Sage Days: We had good internet > access, but the university network blocked all ssh connections! This was > mainly resolved on the first day, but there were still some issues with > pulling/pushing through the `git trac` command. > > Franco > > -- > You received this message because you are subscribed to the Google Groups > "sage-combinat-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-combinat-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-combinat-de...@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-combinat-devel. > For more options, visit https://groups.google.com/d/optout. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] The future of polybori
On Fri, Jun 12, 2015 at 5:34 AM, 'Martin Albrecht' via sage-devel < sage-devel@googlegroups.com> wrote: > Hi, > > so, the Singular team *wants* to keep PolyBoRi alive, but it's currently > not > clear if and when they *can* devote resources to it. This will be clarified > over the next few months it seems. > What about this: Now: We work on making polybori an optional package in sage. * At least going by this thread, the number of people who use polybori in Sage is small enough for it to make sense to have polybori as an optional package. * (I looked into this before I did the autotoolization) It shouldn't take too much work to optionalize polybori -- the main effort will be its uses in the crypto code. * Polybori is the sole dependency of Sage that doesn't at least build against python 3 -- getting past this last major hurdle will make it much easier to work on porting the actual sage library to python 3. Future: The Singular team or whoever dedicates the time to maintain a sequel to polybori. * This will be required once we stop supporting python 2 in the very distant future (at least after 2020, which is the EOL for python 2). > > Cheers, > Martin > > On Friday 12 Jun 2015 10:14:53 Martin Albrecht wrote: > > I started talking to some people from the symbolic computation community > to > > discuss options (e.g. if someone wants to take over maintenance). Hence, > > don't rush to a conclusion please, I'd really like to keep PolyBoRi > around > > somehow but don't want to be (sole) maintainer. > > > > Cheers, > > Martin > > > > On Thursday 11 Jun 2015 20:45:41 William Stein wrote: > > > On Thursday, June 11, 2015, Ralf Stephan wrote: > > > > So folks, be careful when you fork---you might end up as maintainer. > > > > > > Good point. I think we should either > > > > > > 1. Remove polybori or > > > > > > 2. Have a specific person (or persons) step up to be maintainer. > > > > > > I'm fine with either option. > > > > > > > -- > > > > 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 http://groups.google.com/group/sage-devel. > > > > For more options, visit https://groups.google.com/d/optout. > -- > .www: https://martinralbrecht.wordpress.com > .pgp: 40BC 7F0D 724B 4AB1 CC98 4014 A040 043C 6532 AFB4 > .xmpp: martinralbre...@jabber.ccc.de > .twitter: https://twitter.com/martinralbrecht > .keybase: https://keybase.io/martinralbrecht > > -- > 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 http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- Andrew -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] The future of polybori
On Thu, Jun 11, 2015 at 2:42 PM, Alexander Dreyer < jan.alexander.dre...@gmail.com> wrote: > From my point of view a fork - or better call it sequel - would be the > best. > > Unfortunately, all original developers like me went to industrial > positions, which are completely unrelated to PolyBoRi or any kind of > algebraic software. > Meanwhile, family and the new jobs don't leave us time to work on pet > projects. So, the real active branch is the ohanar github repository. > > At that repository, I already see great work in autotools support. I would > adopt this for sure if I ever get the chance to get back to work on > PolyBoRi. For the unlikely case of sudden freetime I would rather > contribute to the new project than trying to resurrect the old one. ;-) > > However, to avoid confusion, you should rename your fork. Use TOSSFKAP or > BRiAl or whatever you like to distinuish the projects. > Yes, I agree, I just didn't have a good name. Do you have a particular favorite (and we could just use that). > Also, I have to note, that in the autotools branch some headers from > original Cudd were reintroduced. Which ones exactly? I exported the mercurial repository into git and double checked the files, but didn't notice any new headers. > This might be a problem since some were intentionally left out due to > unclear licenses. This had been suggested by the debian people some time > ago. > > Best regards and good luck, > Alexander > > -- > 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 http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- Andrew -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Sage Days 65 mini report
Here is a mini report on Sage Day 65. I'm not an organizer so this is not official. Thanks to Anne Schilling for helping to prepare this. - 24 tickets on trac are tagged with `sagedays65` or `sd65`. Some of these have been positively reviewed and marked as fixed. Some are waiting for review (hint, hint). Several of these tickets include contributions from new users. - Installation troubles: - several people had a hard difficult time installing Sage on their machines (8-10 people) - there were people who did not have a working development version on their machines by the end of the week (4-5 people); two of these people were the organizers of the Sage Days - number of participants: 40 - some thing that really helped was the Sage Development Images project - A possible warning to future organizers of Sage Days: We had good internet access, but the university network blocked all ssh connections! This was mainly resolved on the first day, but there were still some issues with pulling/pushing through the `git trac` command. Franco -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Packaging rant
2015-06-12 6:18 GMT-03:00 Jeroen Demeyer : > On 2015-06-11 10:31, Julien Puydt wrote: >> >> Open software is about cooperation. > > Of course. The question is: what should we do if upstream does not want to > cooperate? I don't want to call names in this thread, but I have proposed > patches to many upstream projects which are part of Sage (usually they are > small bugfixes). The chances of actually getting a patch accepted by > upstream are unfortunately much smaller than I would wish. I understand your frustration. I understand that sage needs to bundle all it needs because otherwise it would be pretty much impossible to install sage on old, or too new systems. But keeping as close as possible to upstream is really desirable. For example, I have some patches in a few packages in Fedora, to satisfy sage, but for others it is not easy... Right now, Fedora has sagemath 6.5 packaged, and I need to find some time to see if reasonable, and how I would patch sage to use a non released and patched pari, to update to 6.7 (skipping 6.6). > Some people think that Sage should only add patches to upstream packages if > they are accepted by upstream. This is frustrating, because it really slows > down Sage development. > > Jeroen. Thaks, Paulo -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: revisions to sandpiles needs review
The following two should succeed: make ptestlong make doc-pdf On Friday, June 12, 2015 at 8:36:39 PM UTC+2, David Perkinson wrote: > > One constructive thing I can do, at least, is revise the code to the point > that patchbot is happy. Up to this point, I have only known of the test > "sage -t". All tests passed for my revised code. The problems patchbot > is flagging all seem to be issues with building documentation: indentation > errors, etc. How can I test these issues locally. It would be great to > be able to run a command analogous to "sage -t" (and preferably have errors > referred to by line number). > > On Friday, June 12, 2015 at 10:24:46 AM UTC-7, kcrisman wrote: >> >> >>> The guideline is not a rule, but it has not been put there for no >>> reason either. I have had to do *very* long reviews of a diff that >>> wasn't half as long as yours. I certainly would not start another one >>> when, from the look of your diff file, the changes are so unrelated >>> that you could have split it in 5 different tickets easily. Though >>> Karl-Dieter is more optimistic, and may have more time for it. >>> >>> >> I don't know anything about sandpiles except the ones at our beach. But >> in this case I would not be surprised if there were people who cared enough >> about it - and about accurate code - that this could get reviewed. >> >> David (P.), one thing you could do to help that is to make a comment on >> your ticket (or edit the description) to make it clear which line numbers >> etc. would be self-contained review units. Then someone could review a >> piece at a time, at least mentally. >> >> There is also "git add -p" which apparently allows you to decide which >> hunks (in the patch sense) you want to add to a commit, and you could break >> your branch up into smaller "bite-sized" chunks that way. See >> https://cbx33.github.io/gitt/afterhours5-1.html for a pretty informative >> post that continues to affirm my contention that git does way too many >> things with way too few commands :) But I am not a git expert and have >> never tried this, so I can't say how annoying that might be. Still, it >> could be a way to at least break this ticket into more easily reviewable >> commits without actually making separate branches. >> >> - kcrisman >> > -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: revisions to sandpiles needs review
One constructive thing I can do, at least, is revise the code to the point that patchbot is happy. Up to this point, I have only known of the test "sage -t". All tests passed for my revised code. The problems patchbot is flagging all seem to be issues with building documentation: indentation errors, etc. How can I test these issues locally. It would be great to be able to run a command analogous to "sage -t" (and preferably have errors referred to by line number). On Friday, June 12, 2015 at 10:24:46 AM UTC-7, kcrisman wrote: > > >> The guideline is not a rule, but it has not been put there for no >> reason either. I have had to do *very* long reviews of a diff that >> wasn't half as long as yours. I certainly would not start another one >> when, from the look of your diff file, the changes are so unrelated >> that you could have split it in 5 different tickets easily. Though >> Karl-Dieter is more optimistic, and may have more time for it. >> >> > I don't know anything about sandpiles except the ones at our beach. But > in this case I would not be surprised if there were people who cared enough > about it - and about accurate code - that this could get reviewed. > > David (P.), one thing you could do to help that is to make a comment on > your ticket (or edit the description) to make it clear which line numbers > etc. would be self-contained review units. Then someone could review a > piece at a time, at least mentally. > > There is also "git add -p" which apparently allows you to decide which > hunks (in the patch sense) you want to add to a commit, and you could break > your branch up into smaller "bite-sized" chunks that way. See > https://cbx33.github.io/gitt/afterhours5-1.html for a pretty informative > post that continues to affirm my contention that git does way too many > things with way too few commands :) But I am not a git expert and have > never tried this, so I can't say how annoying that might be. Still, it > could be a way to at least break this ticket into more easily reviewable > commits without actually making separate branches. > > - kcrisman > -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: (off topic) Re: [sage-devel] The future of polybori
On Thursday, June 11, 2015 at 12:11:34 PM UTC-7, William wrote: > > On Thu, Jun 11, 2015 at 11:55 AM, Francesco Biscani > > wrote: > > On 11 June 2015 at 20:13, Travis Scrimshaw > wrote: > >> > >>Difficult-to-dechiper can be considered a pro by bigger businesses > with > >> proprietry software to help prevent reverse-engineering (although from > what > >> I've been told, they typically run it through a scrambler before > compiling > >> the code for release). > > > > > > Not sure what you mean by that. I have worked in the past for a > > multinational company (>100k employees) on software which costs hundreds > of > > thousands of dollars per license, and never heard of that. I am not an > > assembly guy but I would think that the binary of a non-trivial software > is > > already scrambled well enough (especially in release mode where the > compiler > > is gonna pull all sorts of tricks for optimisation). > I think it's now something the compilers do automatically, in particular in release mode, because, as you said, it does all sorts of crazy optimizations. It was something my (old school) C++ programmer professor told me once. > It's officially called "The Wolfram Language" [1] beating out [2] many > other options such as "Wolframese, Wolframic, Wolframian, Wolframish > or Wolframaic, perhaps Wolfese, Wolfic or Wolfish, Wolfian or Wolfan > or Wolfatic, ,the exotic Wolfari or Wolfala? Wolvese or Wolvic? > WolframCode or WolframScript—or Wolfcode or Wolfscript—but these sound > either too obscure or too lightweight. Then there’s the somewhat > inelegantWolframLang, or it shorter forms WolfLang and WolfLan, which > sound too much like Wolfgang. Then there are names like WolframX and > WolfX, but it’s not clear the “X” adds much. > Adding "X" makes it look cool. Same with a "Z". Oh, should we change our name to SageX, SageZ, Zage, Sag3, S4ge 54g3, S4g3, Z4g3, Sag3M4th, or (really FTW and the 1337): 54g3|\/|4+|-| Then, Stephen and Al Gore can fight over who invented what. > Wouldn't that be an inconvienent truth.. Best, 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: revisions to sandpiles needs review
> > > The guideline is not a rule, but it has not been put there for no > reason either. I have had to do *very* long reviews of a diff that > wasn't half as long as yours. I certainly would not start another one > when, from the look of your diff file, the changes are so unrelated > that you could have split it in 5 different tickets easily. Though > Karl-Dieter is more optimistic, and may have more time for it. > > I don't know anything about sandpiles except the ones at our beach. But in this case I would not be surprised if there were people who cared enough about it - and about accurate code - that this could get reviewed. David (P.), one thing you could do to help that is to make a comment on your ticket (or edit the description) to make it clear which line numbers etc. would be self-contained review units. Then someone could review a piece at a time, at least mentally. There is also "git add -p" which apparently allows you to decide which hunks (in the patch sense) you want to add to a commit, and you could break your branch up into smaller "bite-sized" chunks that way. See https://cbx33.github.io/gitt/afterhours5-1.html for a pretty informative post that continues to affirm my contention that git does way too many things with way too few commands :) But I am not a git expert and have never tried this, so I can't say how annoying that might be. Still, it could be a way to at least break this ticket into more easily reviewable commits without actually making separate branches. - kcrisman -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: parents and elements and categories
Dear Categurus! I would somehow like to move on, so it would be good to know 1) is my question very difficult to answer (and I should go for something less ambitious) (i.e., takes even a category guru more than 15min to think about), or 2) is my question hard to understand or silly (and I should clarify), or 3) something else I didn't think of. thank you for your patience, Martin -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: SageManifolds Install Issue
Also, to revert in the meantime, do wget https://launchpad.net/~aims/+archive/ubuntu/sagemath/+build/7499250/+files/sagemath-upstream-binary_6.7ppa10revert6.6.aims6-2_amd64.deb sudo dpkg -i sagemath-upstream-binary_6.7ppa10revert6.6.aims6-2_amd64.deb sudo apt-mark hold sagemath-upstream-binary Regards, Jan On 12 June 2015 at 17:53, Jan Groenewald wrote: > Hi > > The more important drop is the whole src folder, which I think is needed > for rebuilds. We did it to save space and bandwidth, and most importantly > you should not be compiling as root which is necessary to install optional > packages, which we intentially dropped now.. Perhaps a poll on this is > necessary. > > In principle the PPA supports easy install and upgrades, and I am not sure > how to safely install, except perhaps to have all files owned by a new > sagemath user we'd have to create and incorporate, and also the deb is > built from prebuilt binaries, see a recent thread about sagemath binaries > unsuitable for development. > > > https://groups.google.com/forum/#!searchin/sage-devel/binaries$20development/sage-devel/QdwdT8J8q50/TyLCIeAF37cJ > > At the moment we don't want to immediately revert. We could have a package > sagemath-source which installs the latest source, but you are probably > better of with a source tree of your own. How big is the need for optional > packages via the PPA? We have a need for gap_packages at our institution, > and a few others. > > Regards, > Jan > > On 12 June 2015 at 17:13, Gérard JASTRZEB wrote: > >> First of all, I let me thank you for maintaining a PPA for SAGEMATH. >> But since v6.7 there is a problem for those who want to install >> SAGEMANIFOLDS as well. >> You dropped Makefile and .git from /usr/lib/sagemath (system install), >> which are mandatory for SAGEMANIFOLDS, as the install script (stable >> version) triggers a re-build of sage and the development version >> installs via git. Here is the link for it : >> http://sagemanifolds.obspm.fr/download.html >> >> Thank you for having a look at it. >> Gérard JASTRZEB >> gerard,jastr...@free.fr >> -- >> This message was sent from Launchpad by >> =?utf-8?q?G=C3=A9rard_JASTRZEB?= (https://launchpad.net/~gerard-jastrzeb) >> using the "Contact this team's admins" link on the AIMS team page >> (https://launchpad.net/~aims). >> For more information see >> https://help.launchpad.net/YourAccount/ContactingPeople >> > > -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: SageManifolds Install Issue
Hi The more important drop is the whole src folder, which I think is needed for rebuilds. We did it to save space and bandwidth, and most importantly you should not be compiling as root which is necessary to install optional packages, which we intentially dropped now.. Perhaps a poll on this is necessary. In principle the PPA supports easy install and upgrades, and I am not sure how to safely install, except perhaps to have all files owned by a new sagemath user we'd have to create and incorporate, and also the deb is built from prebuilt binaries, see a recent thread about sagemath binaries unsuitable for development. https://groups.google.com/forum/#!searchin/sage-devel/binaries$20development/sage-devel/QdwdT8J8q50/TyLCIeAF37cJ At the moment we don't want to immediately revert. We could have a package sagemath-source which installs the latest source, but you are probably better of with a source tree of your own. How big is the need for optional packages via the PPA? We have a need for gap_packages at our institution, and a few others. Regards, Jan On 12 June 2015 at 17:13, Gérard JASTRZEB wrote: > First of all, I let me thank you for maintaining a PPA for SAGEMATH. > But since v6.7 there is a problem for those who want to install > SAGEMANIFOLDS as well. > You dropped Makefile and .git from /usr/lib/sagemath (system install), > which are mandatory for SAGEMANIFOLDS, as the install script (stable > version) triggers a re-build of sage and the development version > installs via git. Here is the link for it : > http://sagemanifolds.obspm.fr/download.html > > Thank you for having a look at it. > Gérard JASTRZEB > gerard,jastr...@free.fr > -- > This message was sent from Launchpad by > =?utf-8?q?G=C3=A9rard_JASTRZEB?= (https://launchpad.net/~gerard-jastrzeb) > using the "Contact this team's admins" link on the AIMS team page > (https://launchpad.net/~aims). > For more information see > https://help.launchpad.net/YourAccount/ContactingPeople > -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Fwd: [GAP] GAP 4.7.8 release
GAP 4.7.8 is out. I opened http://trac.sagemath.org/ticket/18689 -- Forwarded message -- From: Alexander Konovalov Date: 2015-06-12 12:00 GMT+02:00 Subject: [GAP] GAP 4.7.8 release To: gap-dev , GAP Support , g...@gap-system.org Dear all, The 4.7.8 release just happened - the files are now publicly available: ftp://ftp.gap-system.org/pub/gap/gap47/ I will announce this in the GAP Forum as soon as I will update the website. Alexander ___ Gap mailing list g...@gap-system.org https://mail.gap-system.org/mailman/listinfo/gap -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Packaging rant
On 2015-06-12 14:32, Julien Puydt wrote: Nothing will slow development down like dozens of forked packages to maintain, especially if upstreams consider you hostile. If you mean "forking" in the serious sense, you're probably right. If you mean "forking" as in "add a few patches", then you're surely wrong: Sage has always added many patches to various upstream project and that was never a burden to development. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] The future of polybori
On 2015-06-12 14:34, 'Martin Albrecht' via sage-devel wrote: Hi, so, the Singular team *wants* to keep PolyBoRi alive, but it's currently not clear if and when they *can* devote resources to it. This will be clarified over the next few months it seems. Doesn't OpenDreamKit help with 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 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] The future of polybori
Hi, so, the Singular team *wants* to keep PolyBoRi alive, but it's currently not clear if and when they *can* devote resources to it. This will be clarified over the next few months it seems. Cheers, Martin On Friday 12 Jun 2015 10:14:53 Martin Albrecht wrote: > I started talking to some people from the symbolic computation community to > discuss options (e.g. if someone wants to take over maintenance). Hence, > don't rush to a conclusion please, I'd really like to keep PolyBoRi around > somehow but don't want to be (sole) maintainer. > > Cheers, > Martin > > On Thursday 11 Jun 2015 20:45:41 William Stein wrote: > > On Thursday, June 11, 2015, Ralf Stephan wrote: > > > So folks, be careful when you fork---you might end up as maintainer. > > > > Good point. I think we should either > > > > 1. Remove polybori or > > > > 2. Have a specific person (or persons) step up to be maintainer. > > > > I'm fine with either option. > > > > > -- > > > 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 http://groups.google.com/group/sage-devel. > > > For more options, visit https://groups.google.com/d/optout. -- .www: https://martinralbrecht.wordpress.com .pgp: 40BC 7F0D 724B 4AB1 CC98 4014 A040 043C 6532 AFB4 .xmpp: martinralbre...@jabber.ccc.de .twitter: https://twitter.com/martinralbrecht .keybase: https://keybase.io/martinralbrecht -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Packaging rant
Hi, Le 12/06/2015 11:18, Jeroen Demeyer a écrit : On 2015-06-11 10:31, Julien Puydt wrote: Open software is about cooperation. Of course. The question is: what should we do if upstream does not want to cooperate? I don't want to call names in this thread, but I have proposed patches to many upstream projects which are part of Sage (usually they are small bugfixes). The chances of actually getting a patch accepted by upstream are unfortunately much smaller than I would wish. Some people think that Sage should only add patches to upstream packages if they are accepted by upstream. This is frustrating, because it really slows down Sage development. Nothing will slow development down like dozens of forked packages to maintain, especially if upstreams consider you hostile. There's a joke around here which one could translate as "The fastest and shortest way down is off the cliff -- I prefer hiking!" Snark on #sagemath -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Packaging rant
> On 12/06/2015, at 21:18, Jeroen Demeyer wrote: > > On 2015-06-11 10:31, Julien Puydt wrote: >> Open software is about cooperation. > Of course. The question is: what should we do if upstream does not want to > cooperate? I don't want to call names in this thread, but I have proposed > patches to many upstream projects which are part of Sage (usually they are > small bugfixes). The chances of actually getting a patch accepted by upstream > are unfortunately much smaller than I would wish. > That’s very unfortunate, you expect some rejections but your report of low number is still annoying. > Some people think that Sage should only add patches to upstream packages if > they are accepted by upstream. This is frustrating, because it really slows > down Sage development. > Having been around sage since 2007, I have accepted the fact that not all of the patches in sage will be upstreamed. Even at a linux distro level that’s a pipe dream - have you seen the list of patches that go into your distro? How many of these will be accepted upstream? Probably less than you would imagine. Nevertheless, it is uncomfortable, I am sure that I have been one the people that prompted that remark, it is even written somewhere on trac. There are weighted decisions and I do not want to be painted all black or white. I am the sage-on-gentoo maintainer and anything that is not accepted in the main Gentoo tree, I carry it in my tree and the maintenance is mine to do. If the package is only in my tree, I won’t be fussy adding sage patches. If the package is in the main tree and widely used, well the barrier for entry of the patch to the main tree has just dramatically increased, even more so if 1) it is not accepted upstream 2) it adds a “feature” rather than fix something that will break for many people (the line between feature and bug may sometimes be blurry). In that case, I will carry a fork of the distro package with all the burden that implies when trying to maintain coherence with the distro and steal the main tree own various fixes (it’s been a while since sage-on-gentoo has relied on maxima from the main tree…). So I am looking at sage trac and I see one of those major, widely used, package and upstream reject the patch. Do I want to review the inclusion? Well it is a bit like asking if I am a masochist (considering how long I have been doing sage-on-gentoo it is a really good question). So on that principle I won’t review it. Someone else may review it positively, I am not the only reviewer available after all, and then I’ll have to do my masochistic bit anyway. May be Jeroen is right, may be I should cut the middle man and do the review anyway. François -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] The future of polybori
On Friday, June 12, 2015, 'Martin Albrecht' via sage-devel < sage-devel@googlegroups.com> wrote: > I started talking to some people from the symbolic computation community to > discuss options (e.g. if someone wants to take over maintenance). Hence, > don't > rush to a conclusion please, I'd really like to keep PolyBoRi around > somehow > but don't want to be (sole) maintainer. Thanks!! > > Cheers, > Martin > > On Thursday 11 Jun 2015 20:45:41 William Stein wrote: > > On Thursday, June 11, 2015, Ralf Stephan > wrote: > > > So folks, be careful when you fork---you might end up as maintainer. > > > > Good point. I think we should either > > > > 1. Remove polybori or > > > > 2. Have a specific person (or persons) step up to be maintainer. > > > > I'm fine with either option. > > > > > -- > > > 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 http://groups.google.com/group/sage-devel. > > > For more options, visit https://groups.google.com/d/optout. > -- > .www: https://martinralbrecht.wordpress.com > .pgp: 40BC 7F0D 724B 4AB1 CC98 4014 A040 043C 6532 AFB4 > .xmpp: martinralbre...@jabber.ccc.de > .twitter: https://twitter.com/martinralbrecht > .keybase: https://keybase.io/martinralbrecht > > -- > 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 http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- Sent from my massive iPhone 6 plus. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Packaging rant
On 2015-06-11 10:31, Julien Puydt wrote: Open software is about cooperation. Of course. The question is: what should we do if upstream does not want to cooperate? I don't want to call names in this thread, but I have proposed patches to many upstream projects which are part of Sage (usually they are small bugfixes). The chances of actually getting a patch accepted by upstream are unfortunately much smaller than I would wish. Some people think that Sage should only add patches to upstream packages if they are accepted by upstream. This is frustrating, because it really slows down Sage development. Jeroen. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] The future of polybori
I started talking to some people from the symbolic computation community to discuss options (e.g. if someone wants to take over maintenance). Hence, don't rush to a conclusion please, I'd really like to keep PolyBoRi around somehow but don't want to be (sole) maintainer. Cheers, Martin On Thursday 11 Jun 2015 20:45:41 William Stein wrote: > On Thursday, June 11, 2015, Ralf Stephan wrote: > > So folks, be careful when you fork---you might end up as maintainer. > > Good point. I think we should either > > 1. Remove polybori or > > 2. Have a specific person (or persons) step up to be maintainer. > > I'm fine with either option. > > > -- > > 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 http://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. -- .www: https://martinralbrecht.wordpress.com .pgp: 40BC 7F0D 724B 4AB1 CC98 4014 A040 043C 6532 AFB4 .xmpp: martinralbre...@jabber.ccc.de .twitter: https://twitter.com/martinralbrecht .keybase: https://keybase.io/martinralbrecht -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
