On Feb 11, 2010, at 6:56 PM, Dr. David Kirkby wrote:
Robert Bradshaw wrote:
To see what would happen, I went and grabbed the OpenSolaris image
at http://virtualbox.wordpress.com/images/opensolaris/ , installed
gcc, moved the openssl directory out of /usr/include, and built
Python 2.6.4 fr
Hi folks,
I have built Sage 4.3.0.1 on t2.math. The binary tarball can be found at
http://sage.math.washington.edu/home/mvngu/t2.math-bin/sage-4.3.0.1.tar.gz
--
Regards
Minh Van Nguyen
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send
Robert Bradshaw wrote:
To see what would happen, I went and grabbed the OpenSolaris image at
http://virtualbox.wordpress.com/images/opensolaris/ , installed gcc,
moved the openssl directory out of /usr/include, and built Python 2.6.4
from source. The result:
op...@opensolaris:~/Python-2.6.4$
Dr. David Kirkby wrote:
I've tried to build sage-4.3.2 on Solaris 10 using gcc 4.4.3 (the latest
version).
I should have made it clear, this is a 32-bit build on SPARC.
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
I've tried to build sage-4.3.2 on Solaris 10 using gcc 4.4.3 (the latest
version). It is complaining about some code in NTL, specicially the use of 'if'
and 'define' include/NTL/config.h.
I'm not a C++ programmer. It is normal to put 'if' and 'define' on two lines
like this below?
#if /*
On Feb 11, 8:06 pm, rjf wrote:
> You might check out the syntax and semantics for part() and inpart()
> in Maxima,
> and be sure to note the difference. The notation for selecting parts
> in Mathematica
> is something like x[[1]].
>
> note in particular that in Maxima, x/y internally looks
Hi folks,
I'm just re-posting mhampton's question here with the above subject,
so it would be picked up by the relevant maintainers of GLPK.
On Fri, Feb 12, 2010 at 11:55 AM, mhampton wrote:
> I haven't seen it matter with 4ti2 or your sandpiles stuff, but there
> is a much more recent glpk pack
You might check out the syntax and semantics for part() and inpart()
in Maxima,
and be sure to note the difference. The notation for selecting parts
in Mathematica
is something like x[[1]].
note in particular that in Maxima, x/y internally looks more like x
* y^(-1), so
the main operator is
I haven't seen it matter with 4ti2 or your sandpiles stuff, but there
is a much more recent glpk package, glpk-4.38.p4, which is probably
better to use.
General question: is there any reason that the experimental glpk-4.9
spkg still exists at all? If not it should be removed.
-Marshall
On Feb 1
Hi,
I'm forwarding this to the Macaulay2 list, since at Sage Days 14 (?),
Dan Grayson's project was to embed Sage into Macaulay2. He was
extremely successful at doing this, and showed us some cool demos as a
result. Maybe he can make some comments.
William
On Thu, Feb 11, 2010 at 4:28 PM, Bur
Hi,
I'm in Kaiserslautern, at a workshop on connecting mathematical
software for polyhedral geometry with software packages for Gröbner
basis (polymake, gfan, singular).
I tried to code a small example demonstrating how to call Sage from
other C programs. I have a Cython module with the following
Excellent. This worked, both on my laptop and on my desktop.
Thank you.
Dave
>
> Try rebuilding mpir, then try installing 4ti2.p0 again.
>
> sage -f mpir-1.2.2.p0
>
> William
>
> --
> William Stein
> Associate Professor of Mathematics
> University of Washingtonhttp://wstein.org
--
To post
Dear Sage
Lenka Viskotova found a bug in evaluating limits in Sage. Evaluating
limits via Maxima may return complex infinity or real ininity. Sage
does not distinguish between them. As a consequence, limit(1/x,x=0) is
wrong.
I was not able to find report on this and thus reported this as
http://t
On Wed, Feb 10, 2010 at 9:48 AM, Dima Pasechnik wrote:
> Dear all,
> I have just created track ticket #8229, that completes the task of
> upgrading
> gap.spkg (ticket #8076) and patching the relevant parts of devel/sage/
> (ticket #8150)
> by also upgrading gap_packages.spkg
>
> Please test. Let's
Hi Rob and Pat,
Thanks for your feedback!
I posted your two comments on trac for the reviewer.
On Wed, Feb 10, 2010 at 10:01:39PM -0800, Rob Beezer wrote:
> On Feb 9, 3:53 pm, "Nicolas M. Thiery"
> wrote:
> > * Implement the various options for both latex constructions (tikz or
> > do
Dear Nils,
That's great, thanks! For some reason, I overlooked the utility of
operands() when I was trying things out. This seems perfectly adequate
for my purposes. The suggested extension of operands() to take a syntax
like operands([0,1]) would be nice, too! +1 from me if this counts.
You
On 02/09/2010 03:53 PM, Nicolas M. Thiery wrote:
> * graph_editor was using iterations=1000 as default. Was there a
>reason? If yes, do we want to set this up as default value for all
>layouts?
Feel free to change this --- there's definitely no deep reason.
It was an attempt to avoid giv
17 matches
Mail list logo
