On 19 December 2012 03:16, P Purkayastha wrote:
>
> It is consistent with whatever A.ambient_vector_space() is doing. There is
> even a doctest:
>
> sage: M = ZZ^3;
> sage: V = M.ambient_vector_space(); V
> Vector space of dimension 3 over Rational Field
>
> Since th
I am refering to the package
http://www.sagemath.org/packages/experimental/python-unladen-2009Q2.spkg
I assume this is Python Unladen Swallow (even though SPKG.txt doesn't
mention this), which is a dead project since 3 years. So I propose to
remove this package, please reply any objections.
In an
Just when I thought the #715 + #11521 issues were fixed in sage-5.5.rc1...
Apparently, sage-5.6.beta0 has uncovered a new problem: with the current
sage-5.6.beta0, I get the following reproducible segfault on hawk
(OpenSolaris i386):
> sage -t --long -force_lib devel/sage/sage/modules/module.pyx
On Dec 19, 2012, at 4:16 AM, P Purkayastha wrote:
> On 12/19/2012 12:28 AM, Charles Bouillaguet wrote:
>> Hi all,
>>
>> There seems to be an inconsistency between the docstrings and the actual
>> behavior of some module-related methods. For instance, I am surprised by the
>> behavior of the coo
2012/12/18 kcrisman
> if [ -a "/standard/path/to/Cygwin/lib/or/program.dll" ] ; then
>
> with a whole bunch of "ands"? Or is there some better way to do this?
>
Wouldn't it be a lot better to use e.g. "which make" and see if you get a
path, then do e.g. "make -v" to read the version number?
Be
On 19 December 2012 10:49, Charles Bouillaguet
wrote:
> On Dec 19, 2012, at 4:16 AM, P Purkayastha wrote:
>
>> On 12/19/2012 12:28 AM, Charles Bouillaguet wrote:
>>> Hi all,
>>>
>>> There seems to be an inconsistency between the docstrings and the actual
>>> behavior of some module-related method
* OpenSolaris has been dead for many years now
* No such machine on Skynet, many developers don't have access (I don't)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscrib
On Wednesday, December 19, 2012 11:16:50 AM UTC+1, Jeroen Demeyer wrote:
>
> Just when I thought the #715 + #11521 issues were fixed in sage-5.5.rc1...
>
> Apparently, sage-5.6.beta0 has uncovered a new problem: with the current
> sage-5.6.beta0, I get the following reproducible segfault on haw
On 12/19/2012 07:44 PM, John Cremona wrote:
On 19 December 2012 10:49, Charles Bouillaguet
wrote:
On Dec 19, 2012, at 4:16 AM, P Purkayastha wrote:
On 12/19/2012 12:28 AM, Charles Bouillaguet wrote:
Hi all,
There seems to be an inconsistency between the docstrings and the actual
behavior o
Is there anyone in the Sage community who uses OpenSolaris, or any other
variant?
On Wednesday, December 19, 2012 8:44:58 PM UTC+8, Volker Braun wrote:
>
> * OpenSolaris has been dead for many years now
> * No such machine on Skynet, many developers don't have access (I don't)
>
>
--
You receiv
On 19 December 2012 17:39, P Purkayastha wrote:
> Is there anyone in the Sage community who uses OpenSolaris, or any other
> variant?
Yes, I do.
Many Sage developers have access to my OpenSolaris machine - if anyone
else wants one, they can have it.
The buildbot uses OpenSolaris, so I personall
On 19 December 2012 12:44, Volker Braun wrote:
> * OpenSolaris has been dead for many years now
> * No such machine on Skynet, many developers don't have access (I don't)
Open Indiana is based on the OpenSolaris source, and there is a stong
simularity between Solaris and OpenSolaris.
If you want
On Wednesday, December 19, 2012 5:51:25 PM UTC, Dr. David Kirkby wrote:
> Open Indiana is based on the OpenSolaris source, and there is a stong
> simularity between Solaris and OpenSolaris.
I don't mind OpenIndiana, in fact I'm compiling Sage on it right now. We
definitely need better instructio
On 2012-12-19, P Purkayastha wrote:
> --=_Part_764_937810.1355938788856
> Content-Type: text/plain; charset=ISO-8859-1
>
> Is there anyone in the Sage community who uses OpenSolaris, or any other
> variant?
there are two people that I can think of as OpenSolaris Sage users: Jaap
Spies and Da
On 2012-12-19, Volker Braun wrote:
> --=_Part_747_12972659.1355940087469
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
>
> On Wednesday, December 19, 2012 5:51:25 PM UTC, Dr. David Kirkby wrote:
>> Open Indiana is based on the OpenSolaris source,
On 19 December 2012 18:07, Dima Pasechnik wrote:
> Volker,
> Right, it would be good if you look at it, as I often can't even connect
> to David's machine - too far from Singapore...
>
> Dima
The reason you could not connect an hour or so ago could be due to the
fact there was a power failure.
Another reason to support as much platforms as possible (even dead
platforms) is that it helps porting in general. If you support 10 quite
different systems, it is quite likely that the 11th system also works.
It's happened several times before that doctest failures on obscure
systems were caused b
Hey, yo;
I'm experimenting with building Sage on the Raspberry Pi. It apparently
has an ARM6 processor, so I'm running from scratch. I ran into problems
building libm4rie as well (and also on building conversion.c); it would
start running and then after about 20 minutes the device would freez
Le 19/12/2012 21:52, tom d a écrit :
I'm experimenting with building Sage on the Raspberry Pi. It apparently
has an ARM6 processor, so I'm running from scratch. I ran into problems
building libm4rie as well (and also on building conversion.c); it would
start running and then after about 20 minute
I fail to see what we can learn from a platform that ships a gcc version
that is too old to compile libz, for example. Except that its frustrating
to manually bring up a toolchain and the importance of a working package
management system to keep your unix flavor alive.
Dead platforms are, at th
And while I'm venting, who decided to install libgfortran in a directory
that is not searched by gfortran by default. I'm looking at you, Open
Indiana. You don't compile fortran code much?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post
On 2012-12-19 22:52, Volker Braun wrote:
> Most issues will just be braindamage that goes to show why the
> dead platform was abandoned in the first place.
Sometimes yes, but these issues are usual trivial to fix. But as I said
in my previous post, sometimes we do find true bugs by testing on
diffe
On Dec 19, 2012, at 12:44 PM, John Cremona wrote:
---
Charles Bouillaguet
http://www.lifl.fr/~bouillaguet/
> I suggest adding to the documentation of A.coordinates() that it works
> also if the given element is in the ambient space, with an example of
> that. In concrete terms you need the el
On Wednesday, December 19, 2012 10:47:51 PM UTC, Jeroen Demeyer wrote:
> For example, I'm not convinced that the GAP problem
> is OpenSolaris braindamage.
>
If its not then its quite certain that it would also appear on OpenIndiana.
Which has some developer community and updates and source cod
On 12/20/2012 08:33 AM, Volker Braun wrote:
On Wednesday, December 19, 2012 10:47:51 PM UTC, Jeroen Demeyer wrote:
For example, I'm not convinced that the GAP problem
is OpenSolaris braindamage.
If its not then its quite certain that it would also appear on
OpenIndiana. Which has some
25 matches
Mail list logo
