Re: [sage-devel] source code comments: doctesting instructions

On Thu, 29 Oct 2015, John H Palmieri wrote: Since we can already detect doctests, and among those we can already detect the various doctest flags, we should be able to hide those flags. The TESTS blocks are a different situation. If we insist that TESTS blocks are always the last thing in the

[sage-devel] Error installing package mpir-2.7.0 on arch linux

Hello, I just got an error trying to compile sage 6.9 from source, on a just updated archlinux with kernel 4.2.3. A couple of days ago I could upgrade my working installation, and it worked, but it failed at building the documentation. Regards libtool: compile: gcc -DHAVE_CONFIG_H -I. -I..

Re: [sage-devel] source code comments: doctesting instructions

On Thu, 29 Oct 2015, Nathann Cohen wrote: Now, to give a testable example of this kind of function one must put sorted() to output or do someting like (1 in result, 2 in result) --> True. Should we show them to user? I think that this could be argued to both directions. In those cases I'd

[sage-devel] sage compiling fails at the pyzmq-14.3.0 package

Hello, I'm trying to compile sage on a cluster with openmpi (distro: slackware-current) and I'm getting the error below when trying to compile pyzmq. It seems that a '-R' option is passed to gcc, which makes the compiling process fail. I tried a simple 'python setup.py build' in the

Re: [sage-devel] Sage on OS X: El Capitan

On Sun, Oct 25, 2015 at 6:49 PM, David Joyner wrote: > On Sun, Oct 25, 2015 at 5:10 PM, David Joyner wrote: >> On Sun, Oct 25, 2015 at 3:46 PM, Volker Braun wrote: >>> Are those the new binaries that I built with

[sage-devel] compile on ubuntu 16.04

Hi, Yesterday I upgraded one partition to 16.04 (xenial), sage-10 beta 2 compiles good with compilateur 5.2.1. At the moment I see no difference, tough a lot of recent files. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

[sage-devel] Re: sage compiling fails at the pyzmq-14.3.0 package

Just found out more about this bug: if I set the PYTHONPATH var to /usr/local/src/Math/sage-6.9/local/lib/python/site_packages then the code compiles fine, since rather than the '-R' option it is used the correct '-Wl,-R'. If, instead, I set it, as sage does, to

[sage-devel] Re: sage compiling fails at the pyzmq-14.3.0 package

Solved! For some reason the file /usr/local/src/Math/sage-6.9/local/lib/python2.7/distutils/unixccompiler.py is not behaving fine and it passes the '-R' option to mpicc instead of '-Wl,-R'. When /usr/local/src/Math/sage-6.9/local/lib/python was not in the PYTHONPATH, then python was using the

[sage-devel] git on xkcd

Reasons we should have stuck with hg: http://xkcd.com/1597/ sage: xkcd(1597) Githttp://imgs.xkcd.com/comics/git.png; title="If that doesn't fix it, git.txt contains the phone number of a friend of mine who understands git. Just wait through a few minutes of 'It's really pretty simple, just

[sage-devel] Re: Definition of multifactorial #5415

On Friday, 30 October 2015 05:38:56 UTC, prateek sharma wrote: > > > It should be like > a=42 > k=3 > sage: a.multifactorial(k) > I told you to display the source code for this function, as this is what you asked, no? > > On Wednesday, October 28, 2015 at 2:50:01 PM UTC+5:30, Dima

[sage-devel] Re: Definition of multifactorial #5415

On Friday, October 30, 2015 at 8:50:42 AM UTC-7, Dima Pasechnik wrote: > > > > On Friday, 30 October 2015 05:38:56 UTC, prateek sharma wrote: >> >> >> It should be like >> a=42 >> k=3 >> sage: a.multifactorial(k) >> > > I told you to display the source code for this function, as this is what >