BTW we do have build/tox.ini to automatically test our build-time scripts
against multiple Python versions. But only if you add testcases to
build/test/.
On Tuesday, March 22, 2016 at 11:49:44 PM UTC+1, John H Palmieri wrote:
>
>
>
> On Tuesday, March 22, 2016 at 3:24:13 PM UTC-7, David Roe
On Tuesday, March 22, 2016 at 3:49:44 PM UTC-7, John H Palmieri wrote:
>
>
>
> On Tuesday, March 22, 2016 at 3:24:13 PM UTC-7, David Roe wrote:
>>
>>
>>
>> On Tue, Mar 22, 2016 at 10:13 PM, Dima Pasechnik
>> wrote:
>>
>>> we now decompress tarfiles with python
>>>
>>>
On Tuesday, March 22, 2016 at 3:24:13 PM UTC-7, David Roe wrote:
>
>
>
> On Tue, Mar 22, 2016 at 10:13 PM, Dima Pasechnik > wrote:
>
>> we now decompress tarfiles with python
>>
>> https://docs.python.org/2/library/tarfile.html
>>
>> and all the features of it are only in
we now decompress tarfiles with python
https://docs.python.org/2/library/tarfile.html
and all the features of it are only in Python 2.7. Hmm...
On Tuesday, March 22, 2016 at 9:35:24 PM UTC, Travis Scrimshaw wrote:
>
> Is that the entire log? If not, could you please post it? Although it
>
We changed to using Python to uncompress tarballs, so an out-of-date
version of Python could cause this. What does "python --version" say?
(Should we check the Python version in ./configure?)
John
On Tuesday, March 22, 2016 at 2:35:24 PM UTC-7, Travis Scrimshaw wrote:
>
> Is that the
Is that the entire log? If not, could you please post it? Although it looks
like you have an issue with not having a high enough version of python
(IIRC, this is needed for the bootstrapping) or something is wrong with
your tar.
Best,
Travis
On Tuesday, March 22, 2016 at 4:25:35 PM UTC-5,
I just failed to build Sage 7.1 on my work server, on which I have built
many previous versions. Any ideas?
patch-2.7.5
Setting up build directory for patch-2.7.5
Traceback (most recent call last):
File
done for librae
Vincent
On 22/03/16 17:17, Frédéric Chapoton wrote:
@ all patchbot owners, could you please set
"max_behind_commits" to 0 in your json config file ?
This may prevent the bots to go on misbehaving until the next beta..
Frederic
Le mardi 22 mars 2016 08:37:12 UTC+1, Frédéric
@ all patchbot owners, could you please set
"max_behind_commits" to 0 in your json config file ?
This may prevent the bots to go on misbehaving until the next beta..
Frederic
Le mardi 22 mars 2016 08:37:12 UTC+1, Frédéric Chapoton a écrit :
>
> Hello,
>
> the patchbots seem to be very confused
facepalm:
found an example in thematic tutorials; it turns out one can just do
:ref:`sage.bla.foo` everywhere in the docs, not only in the reference
manual/library code.
On Tuesday, March 22, 2016 at 11:47:57 AM UTC, Dima Pasechnik wrote:
>
> How can this be done? I understand how to use :ref:
Ah! Thank's for checking this out.
I don't really know how that came there, maybe an error by me. But for
example I have no idea about the DKIM key.
However, now this is txt and spf is gone:
$ dig +short sagemath.org txt
"v=spf1 a:trac.sagemath.org ?all"
and the site verification ...
I hope
On 03/22/2016 05:43 AM, Harald Schilly wrote:
>
> Seems like it works better now? However, we could add a SPF TXT line to
> the DNS of sagemath.org? I.e. my idea is, that by including the sender
> explicitly in this "v=spf1 include: ?all" entry, the
> score would get pushed higher (no longer
I'm going to bet this is http://trac.sagemath.org/ticket/11160
or http://trac.sagemath.org/ticket/10657 appearing as a surprise even when
there aren't any explicit options set?
Actually maybe it's http://trac.sagemath.org/ticket/12591
On Tuesday, March 22, 2016 at 5:00:04 AM UTC-4, Samuel
How can this be done? I understand how to use :ref: within a document, e.g.
across the tutorial, but how about referencing something.
Say, just something that can be referred to by a label, e.g. a section
title
r""
.. blah:
Blah blah
==
foo
""
somewhere...
Thanks,
Dima
--
You
On Tuesday, March 22, 2016 at 9:53:42 AM UTC, Eric Gourgoulhon wrote:
>
>
>
> Le mardi 22 mars 2016 10:38:43 UTC+1, Harald Schilly a écrit :
>>
>>
>>
>> On Tuesday, March 22, 2016 at 9:49:29 AM UTC+1, Samuel Lelievre wrote:
>>>
>>>
>>> Shouldn't the "long time" stuff appear anyway in the online
Le mardi 22 mars 2016 10:38:43 UTC+1, Harald Schilly a écrit :
>
>
>
> On Tuesday, March 22, 2016 at 9:49:29 AM UTC+1, Samuel Lelievre wrote:
>>
>>
>> Shouldn't the "long time" stuff appear anyway in the online
>> documentation?
>>
>
> Well, do you have any idea how to do that?
>
> It's easy:
On Friday, March 18, 2016 at 3:39:47 PM UTC+1, Daniel Krenn wrote:
>
> On 2016-03-18 14:55, Harald Schilly wrote:
> > I have no idea about trac's email setup, can you forward me the source
> > code of one of such emails? My guess is, that it doesn't properly sign
> > the email, etc.
>
> The
On Tuesday, March 22, 2016 at 9:49:29 AM UTC+1, Samuel Lelievre wrote:
>
>
> Shouldn't the "long time" stuff appear anyway in the online documentation?
>
Well, do you have any idea how to do that?
-- harald
--
You received this message because you are subscribed to the Google Groups
On the documentation page for plotting
http://doc.sagemath.org/html/en/reference/plotting/sage/plot/plot.html
there is the following example:
Here we give only one row:
sage: p1 = plot(sin,(-4,4))
sage: p2 = plot(cos,(-4,4))
sage: g = graphics_array([p1, p2]);
The page
http://doc.sagemath.org/html/en/reference/plotting/sage/plot/plot.html
has this:
Pi Axis
sage: g1 = plot(sin(x), 0, 2*pi)
sage: g2 = plot(cos(x), 0, 2*pi, linestyle = "--")
sage: (g1+g2).show(ticks=pi/6, tick_formatter=pi) # long time
# show their sum,
Hello,
the patchbots seem to be very confused by the 7.1 release.
It may come from a bug in the patchbot code. Maybe the situation will go
back to
normal with the first beta of 7.2. I remember patchbots being troubled by
exact release,
but not as severely as this time.
Could somebody please
21 matches
Mail list logo