[sage-devel] GitHub finally adds something resembling workflow

(Forgive me if I'm late to the party--been on vacation for the last ~2 weeks) https://help.github.com/articles/about-pull-request-reviews/ I still think this falls far short of what Trac can do (nevermind the lack of customization), but at least it's a step in the right direction. Erik -- You

Re: [sage-devel] Re: National Science Foundation support for Sage

Super exciting - Congratulations! And please keep us updated when the web page comes up. Best, Johan -- 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] Re: Sage's references: new policy?

Hi John, Le mercredi 21 septembre 2016 01:03:27 UTC+2, John H Palmieri a écrit : > > As discussed in another thread [1]_ on sage-devel recently, I propose > changing our policy toward references: > > - all references should be put into a master bibliography file, and > What about the pdf

[sage-devel] sage -rst2ipynb

Hi all, after the live documentation (which was resolved by #20690), one of the important features that are missing to switch from sagenb to jupyter is the possibility to work with source documents, e.g. to prepare and version tutorials (.iypnb files are not easily editable by a human from a text

[sage-devel] Re: Sage's references: new policy?

On Wednesday, September 21, 2016 at 1:03:27 AM UTC+2, John H Palmieri wrote: > > - all references should be, insofar as possible, in a standard form > There is one standard form for everything, even old papers, the Google Scholar cluster link. Guess which one will survive longer: Google or all

[sage-devel] Re: Issues with meataxe on 32bit systems (Cannot select field GF(9) in file matcore.c)

Hi Thierry, On 2016-09-21, Thierry wrote: > while trying to build and test Sage Debian Live 7.3, i notice some issue > with meataxe package. Thanks for trying! > While doctests pass on the VM is was built on > (Pentium3 kvm-emulated), the doctests give a lot of

Re: [sage-devel] Sage contributor in AAUP journal

On Tue, Sep 20, 2016 at 6:48 PM, William Stein wrote: > > > On Mon, Sep 19, 2016 at 6:37 PM, kcrisman wrote: >> >> Some of you may be interested in this article by Paul-Olivier Dehaye: >> https://www.aaup.org/article/mooc-platforms-surveillance-and-control >

Re: [sage-devel] Re: Importing sage.libs.gap.assigned_names take a very long time

On Fri, Sep 16, 2016 at 10:55 PM, Volker Braun wrote: > For tab completion and so on we want a list of "useful" GAP functions, > excluding internal functions that are not meant for end users. > Unfortunately, there isn't really a good way to get that from GAP. The best >

Re: [sage-devel] Sage and pylint

On Fri, Sep 16, 2016 at 1:12 PM, VulK wrote: > Hi, > I thought this was a question for sage-devel because it is about tickets I > am currently working on (#21254 specifically). Sorry for the wrong > assumption. > > I did try sage -pip install pylint before posting but the

Re: [sage-devel] Sage and pylint

Hi Erik, no options. As an example of the errors I get let's consider the ticket I am working on (#21254). I installed pylint via $ sage -pip install pylint my sage install is in /opt/sage so $ /opt/sage/local/bin/pylint /opt/sage/src/sage/algebras/cluster_algebra.py | grep E: |

[sage-devel] Re: macos sierra

On Wednesday, September 21, 2016 at 7:14:55 AM UTC-7, John H Palmieri wrote: > > I tried building Sage with macos sierrra (OS X 10.12, Darwin 16.0.0), and > it failed: Python claims to build successfully, but says > > Failed to build these modules: > _scproxy

Re: [sage-devel] Re: PYTHONUSERBASE?

I would benefit a lot from having Sage be part of the system Python. The reason is that I am using a distribution and my distribution comes with many Python modules that I am using. For some of them they are either broken on Sage or just does not compile at all (eg matplotlib graphics, pygtk). I

[sage-devel] Re: Error building sage 7.3 on Fedora 24 x86_64

The easiest solution would be to install the dependencies so that Sage doesn't attempt to compile its own toolchain: http://doc.sagemath.org/html/en/installation/source.html#linux-prerequisite-installation On Thursday, September 22, 2016 at 8:45:34 PM UTC+2, Lennart Jern wrote: > > Hello, > >

[sage-devel] pre-built buildbot docker images?

Hi, Is there a Sage buildbot docker image, e.g, something so "any idiot" can just go docker run blah blah sagemath-buildbot-ubuntu or docker run blah blah sagemath-buildbot-centos and have a build bot running... and when they want to clean up, just delete the docker container? --

Re: [sage-devel] Re: PYTHONUSERBASE?

On Thu, Sep 22, 2016 at 12:49 PM, Vincent Delecroix < 20100.delecr...@gmail.com> wrote: > I would benefit a lot from having Sage be part of the system Python. > The reason is that I am using a distribution and my distribution comes > with many Python modules that I am using. For some of them they

Re: [sage-devel] Re: PYTHONUSERBASE?

On Sat, Sep 10, 2016 at 4:55 PM, William Stein wrote: > On Sat, Sep 10, 2016 at 3:30 AM, Volker Braun wrote: >> I think this idea of installing stuff globally (either system-wide or in >> ~/.local) is outdated. Really its always better to make a venv if

Re: [sage-devel] Re: PYTHONUSERBASE?

On Sat, Sep 10, 2016 at 12:30 PM, Volker Braun wrote: > I think this idea of installing stuff globally (either system-wide or in > ~/.local) is outdated. Really its always better to make a venv if you need > some sort of specialist package. Its just an all-around better

[sage-devel] Make some fun

I just tried `make -B` inside a source install. I recommend it :) Luca P.S.: Seriously, I am not a Makefile expert, I don't know what's happening here, but infinite recursion feels bad. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Re: Issues with meataxe on 32bit systems (Cannot select field GF(9) in file matcore.c)

Hi, On Thu, Sep 22, 2016 at 01:00:57PM +, Simon King wrote: [...] > A part of #20136 is related with finding the correct path to the > multiplication tables. So, perhaps it does fix it. Can you please try? I will have a try (but it might take some time). > Just to make sure: Both systems