On 2017-02-04 10:34, Jean-Philippe Labbé wrote:
Before that it was building the doc, and before that installing the
jupyter client.
Logs please... ignore the "python" thing, it's most likely not the
reason for the failure.
--
You received this message because you are subscribed to the
On Saturday, February 4, 2017 at 11:55:00 AM UTC+1, Samuel Lelievre wrote:
>
> Should 'make ptestlong' ignore the content of 'init.sage'?
>
Yes.
>
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop
Indeed... Sorry for the answering delay (NI...).
--
Emmanuel Charpentier
Le jeudi 2 février 2017 14:45:43 UTC+1, Volker Braun a écrit :
>
> Presumably this one: https://trac.sagemath.org/ticket/15585
>
>
> On Thursday, February 2, 2017 at 1:30:04 PM UTC+1, Emmanuel Charpentier
> wrote:
>>
>> On
Hi,
I get:
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all'):
* package: python
log file: /sage/logs/pkgs/python.log
build directory: /sage/local/var/tmp/sage/build/python
=
On 2017-02-04 11:54, Samuel Lelièvre wrote:
> You are right Volker!
>
> I followed the hint in fidbc's answer at [0]
>
> [0] https://ask.sagemath.org/question/10060/sage-terminal-colors/
>
> and I have the following 'init.sage':
>
> $ cat $HOME/.sage/init.sage
> %colors Linux
I have
2017-02-04 11:32 GMT+01:00 Volker Braun:
> I think its likely that you have some local configuration, probably
> ipython,
>
that is being picked up accidentally. The failures all come from switching
> on
>
ascii colors even though they shoudn't be for doctests.
>
In any case I can't reproduce it.
Hi!
On 2017-02-04, Daniel Krenn wrote:
>> Should 'make ptestlong' ignore the content of 'init.sage'?
>
> +1, I think (without having thought too much about it...)
+1. IIRC, init.sage is about the user's personal configuration
for interactive sessions, and s/he might want to use,