On 2017-01-24 13:09, John Cremona wrote:
OK, I am doing that and then make and make ptestlong, and we'll see
what happens no, same errors.
Minor comment: if you are going to run "make ptestlong" anyway, there is
no point in running "make" separately. In other words, "make && make
On 24 January 2017 at 10:02, Jeroen Demeyer wrote:
> On 2017-01-24 10:54, John Cremona wrote:
>>
>> Quite possibly. If I use pip to install something and it tells me
>> that my pip os out of date I usually obey instructions and update it.
>> Should I not have done?
>
>
>
On 2017-01-24 10:54, John Cremona wrote:
Quite possibly. If I use pip to install something and it tells me
that my pip os out of date I usually obey instructions and update it.
Should I not have done?
Depends. If you want all doctests to pass: no, you should not have done
that.
And what
This is 3 doctest runs concatenated. I will just look at the last one
(if you remember for next time: better just post the log of one run).
Those issues are because of pip. Did you manually upgrade pip in that
installation?
--
You received this message because you are subscribed to the
On Tuesday, January 24, 2017 at 3:55:57 AM UTC, kcrisman wrote:
>
>
>
>
> On two systems I built this beta I had to remove ~/.sage/,
>> as with it present Sage just dies. (unless started with ---nodotsage).
>>
>> People with stuff in ~/.sage/ will not be happy.
>>
>>
>>>
> Like, say, the
On two systems I built this beta I had to remove ~/.sage/,
> as with it present Sage just dies. (unless started with ---nodotsage).
>
> People with stuff in ~/.sage/ will not be happy.
>
>
>>
Like, say, the sagenb?
--
You received this message because you are subscribed to the Google Groups
On 2017-01-23 17:50, John Cremona wrote:
ptestlong.log available on request.
Yes please.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
+1 for the fact that "git pull trac develop; make" completed without
the usual "make doc-clean", but -1 for:
sage -t --long src/sage/doctest/test.py # 16 doctests failed
sage -t --long src/sage/tests/cmdline.py # 2 doctests failed
sage -t --long src/sage/misc/package.py # 9 doctests failed
On two systems I built this beta I had to remove ~/.sage/,
as with it present Sage just dies. (unless started with ---nodotsage).
People with stuff in ~/.sage/ will not be happy.
On Saturday, January 21, 2017 at 5:57:13 PM UTC, Volker Braun wrote:
>
> As always, you can get the latest beta