On 2016-05-18 22:49, François Bissey wrote:
On 05/19/16 02:28, John Cremona wrote:
Two similar machines running ubuntu 14.04 and gcc-4.8.4. On one 7.2
built fine but on the other ipython ran into difficulties. This was
an upgrade from 7.1 in the git sense, i.e. I have the source repo,
which wa
On 05/19/16 02:28, John Cremona wrote:
Two similar machines running ubuntu 14.04 and gcc-4.8.4. On one 7.2
built fine but on the other ipython ran into difficulties. This was
an upgrade from 7.1 in the git sense, i.e. I have the source repo,
which was probably at 7.0 and first did git pull trac
A number of buildbot machines are now failing tests, probably due to a
recent git update? In any case, I propose to remove sage.dev. Of course
feel free to fix the failures if you want to keep it ;-)
sage -t --long src/sage/dev/git_interface.py
the (py)zmq installation is the problem. Whats the output of
ldd local/lib/python/site-packages/zmq/backend/cython/_device.so
On Wednesday, May 18, 2016 at 4:29:18 PM UTC+2, John Cremona wrote:
>
> Two similar machines running ubuntu 14.04 and gcc-4.8.4. On one 7.2
> built fine but on the othe
On Wednesday, May 18, 2016, Brian Beavers wrote:
> Looks like there's more going on than just a lack of pty. Here's the
> result:
>
>
Well that is just another test of pty...
> sage: gp.eval('2+2')
> ---
> OSError
Looks like there's more going on than just a lack of pty. Here's the result:
sage: gp.eval('2+2')
---
OSError Traceback (most recent call last)
in ()
> 1 gp.eval('2+2')
/usr/lib/sagemath
On Wednesday, May 18, 2016, Brian Beavers wrote:
> I've discovered why the notebook server (and administrative pages within)
> loads but notebooks do not load: WSL does not yet suppot pty. When I try to
> create a worksheet, back in the terminal Sage throws an error that it is
> out of pty instan
I've discovered why the notebook server (and administrative pages within)
loads but notebooks do not load: WSL does not yet suppot pty. When I try to
create a worksheet, back in the terminal Sage throws an error that it is
out of pty instances.
Brian Beavers, Ph.D., Associate Professor
Departmen
What you did gets discussed/advertised at the beginning of this podcast:
https://talkpython.fm/episodes/show/59/sagemath-open-source-is-ready-to-compete-in-the-classroom
On Tue, May 10, 2016 at 4:36 PM, Brian Beavers wrote:
> I don't know if any of you are Windows Insiders and are following th
https://talkpython.fm/episodes/show/59/sagemath-open-source-is-ready-to-compete-in-the-classroom
--
William (http://wstein.org)
--
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, sen
I also vote for 3: command/method names should be as meaningful as
possible, especially since tab-completion means that no one ever needs to
type long names. (Short-hands such as and `gens` for generators drive me
nuts:)
The name `content` doesn't meet this aim but `content_ideal` does.
On Wed
this is still Sage 7.1, so http://trac.sagemath.org/ticket/20381 is not
there yet.
Anyhow, this is being built with gcc 6.1.1, and leads to an obscure C++
error...
Could you perhaps downgrade your compiler to gcc 5 (or 4.9.3 ?)
On Wednesday, May 18, 2016 at 11:40:07 AM UTC+1, Antonio Rojas wr
Antonio Rojas wrote:
> Adetokunbo Arogbonlo wrote:
>
>> Cleaning out old PolyBoRi and BRiAl installations
>> patching file Makefile.am
>> patching file Makefile.in
>> patching file groebner/src/Makefile.am
>> patching file groebner/src/Makefile.in
>> checking for a BSD-compatible install...
Adetokunbo Arogbonlo wrote:
> Cleaning out old PolyBoRi and BRiAl installations
> patching file Makefile.am
> patching file Makefile.in
> patching file groebner/src/Makefile.am
> patching file groebner/src/Makefile.in
> checking for a BSD-compatible install... /usr/bin/install -c
The patch c
I vote for 3
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.
I had completely forgotten this old discussion. Thanks for bringing
it up again; I assume that it has not been resolved in the meantime.
[I do not promise to be consistent today with anything I have said
before on the subject.]
Consistency with existing code and with Magma et al is surely
impor
Dear Dima!
Thank you for your interest! (I was away for the weekend...)
remove_constraint takes as input the index of the constraint to be
>> removed! It is unlikely, that add_constraint(variable==0) creates an
>> indexed constraint, but perhaps I am mistaken.
>>
>
> Somewhat naively, I'd
On May 18, 2016 2:50 AM, "Dima Pasechnik" wrote:
>
>
>
> On Wednesday, May 18, 2016 at 7:44:03 AM UTC+1, Adetokunbo Arogbonlo
wrote:
>>
>> Hi Sage Dev Team,
>>
>> Making sage from source fails on my machine.
>>
>> Sage version: sage-7.1
>>
>> Machine details:
>> Arch linux installed on a Macbook P
18 matches
Mail list logo
