On Tue, Dec 16, 2008 at 10:29 PM, Joshua Kantor
wrote:
> I attached a patch that fixes the segfault.
Thanks for attaching a patch to
http://trac.sagemath.org/sage_trac/ticket/4752
I commented that it needs a doctest illustrating that the segfault
doesn't happen. Then it's ready to go in.
I
Hi Harald,
I like it. tex4ht can translate LaTeX into XHTML, so if the right
configuration files were written for tex4ht it would be possible to
have SageTeX commands migrate into the XHTML in a format that your
tool would then convert into the final form (with Sage output and
PNG's of plots, et
This is one of the very few things I really miss since I abandoned
Mathematica for Sage. Holding down the control key and moving your
mouse over a plot would display the coordinates nearby. Or something
like that.
Similar functionality would be a great addition that would be very
useful in educ
> what exactly did you set those env variables to? What is the content
> of the directories, i.e. the exact name of libgfortran?
I set
SAGE_FORTRAN=/usr/bin/gfortran
and
SAGE_FORTRAN_LIB=/usr/lib/gcc/powerpc-linux.gnu/4.3/libgfortran.so
Contents are as follows:
$ ls /usr/bin | grep fortran
Jaap Spies wrote:
> mabshoff wrote:
>>
>> Please build, test and report issues. DSage still has some failures,
>> so we will probably disable some doctests before 3.2.2.final.
>>
>
On Fedora 10, 32 bits:
The following tests failed:
sage -t "devel/sage/sage/dsage/interface/dsage_inte
By the way, that's a nice exercise. While I was looking at it I
noticed a fix for the determinant calculation you were doing - a
version that works is:
z=var('z')
(xA, yA, zA)=(1,1,0)
(xB, yB, zB)=(0,1/2,1)
(xC, yC, zC)=(0,0,z)
MZ = matrix(3,3,[xA, xB, xC, yA, yB, yC, 1, 1, 1])
MX = matrix(3,3,[
I thought perhaps the Polyhedron class in polyhedra.py could handle
this sort of thing, but at the moment the render_solid() method
crashes on 2-d polyhedra in 3-d. I will work on fixing that too.
-M. Hampton
On Dec 16, 12:47 pm, Robert Bradshaw
wrote:
> On Dec 16, 2008, at 8:28 AM, philt wrot
On Dec 16, 2008, at 8:28 AM, philt wrote:
>
> Hello,
>
> I got some trouble trying to draw polygons in JMol because the
> function looks not available easily.
> Sage is featuring the following:
> point() -> try point2d else point3d
> line() -> try line2d else line3d
> polygon() -> only 2d
> but m
On Dec 16, 10:38 am, C wrote:
> Hi again,
>
> Thanks for pointing out the relevant part of the readme. I set these
> and tried again. The build fails in exactly the same way. Do you
> have any other ideas?
>
> best,
> Chris
Hi Chris,
what exactly did you set those env variables to? What is
Hi again,
Thanks for pointing out the relevant part of the readme. I set these
and tried again. The build fails in exactly the same way. Do you
have any other ideas?
best,
Chris
On Dec 15, 12:27 pm, mabshoff wrote:
> On Dec 15, 10:05 am, C wrote:
>
> > Hi Michael,
>
> Hi C,
>
> > > The log
On Dec 16, 2008, at 10:12 , mabshoff wrote:
> On Dec 16, 9:46 am, "Justin C. Walker" wrote:
>
>>
>> In case I am missing something obvious :-} any reason why this one
>> file is causing grief? As John noted, Nicolas's name crops up in a
>> number of files.
>
> Only one instance has an accent o
> Very nice. It's a clear description of the details of what needs to
> be done, and can probably be easily automated. I've made this trac
> #4817:
>
> http://trac.sagemath.org/sage_trac/ticket/4817
Great! I should point out that the only reason for the script being
long is to allow for doin
On Dec 16, 9:46 am, "Justin C. Walker" wrote:
>
> In case I am missing something obvious :-} any reason why this one
> file is causing grief? As John noted, Nicolas's name crops up in a
> number of files.
Only one instance has an accent over the e, the other ones do not.
> Justin
By th
On Dec 16, 2008, at 09:39 , mabshoff wrote:
>
>
>
> On Dec 16, 9:37 am, "John Cremona" wrote:
>> This still leaves with the task of patching that one file for
>> 3.2.2, right?
>
> Absolutely. But since that file seems to be the only one that causes
> trouble I want to avoid monkeying with the
On Dec 16, 9:37 am, "John Cremona" wrote:
> This still leaves with the task of patching that one file for 3.2.2, right?
Absolutely. But since that file seems to be the only one that causes
trouble I want to avoid monkeying with the files where it works :)
> John
Cheers,
Michael
--~--~--
This still leaves with the task of patching that one file for 3.2.2, right?
John
2008/12/16 mabshoff :
>
>
>
> On Dec 16, 9:33 am, "John Cremona" wrote:
>> It may just be a coincidence but one of the few files which uses the
>> coding mechanism is this:
>>
>> rings/polynomial/multi_polynomial_i
On Dec 16, 9:33 am, "John Cremona" wrote:
> It may just be a coincidence but one of the few files which uses the
> coding mechanism is this:
>
> rings/polynomial/multi_polynomial_ideal.py:# -*- coding: utf-8 -*-
>
> and that happens to be another file where tests are failing on some
> machines!
It may just be a coincidence but one of the few files which uses the
coding mechanism is this:
rings/polynomial/multi_polynomial_ideal.py:# -*- coding: utf-8 -*-
and that happens to be another file where tests are failing on some
machines! My guess is that it's there because some of the
contrib
On Dec 16, 2008, at 09:28 , mabshoff wrote:
> On Dec 16, 9:25 am, "John Cremona" wrote:
>> It looks like Nicolas will have to lose his accent, unless he wants
>> to
>> find out about encoding and change all these:
>>
>
> Yep, that change that character in the patch and I patch it out
> locally
On Tue, Dec 16, 2008 at 9:15 AM, kcrisman wrote:
>
> Hi sage-devel,
>
> Thanks to some assistance from Dan and my chair/sysadmin, and a lot of
> time trying to figure out vagaries of the not-for-the-faint-of-heart
> documentation of Mac shell and Mac app property lists, I have the
> following ste
On Dec 16, 9:25 am, "John Cremona" wrote:
> It looks like Nicolas will have to lose his accent, unless he wants to
> find out about encoding and change all these:
>
Yep, that change that character in the patch and I patch it out
locally before importing the patch.
We should have a rule to onl
On Dec 16, 2008, at 09:13 , John Cremona wrote:
> 2008/12/16 Justin C. Walker :
>>
>> On Dec 16, 2008, at 09:01 , John Cremona wrote:
>>> Patch attached at #4816 but in testing I turned up a strange problem
>>> when cloning my new 64-bit 3.2.2.rc0 build.
>>
>> Have you identified the errant chara
It looks like Nicolas will have to lose his accent, unless he wants to
find out about encoding and change all these:
sage: search_src("Nicolas M. Thi")
--
| Sage Version 3.2.2.rc0, Release Date: 2008-12-15 |
| T
On Dec 16, 7:04 am, Dan Christensen wrote:
> John H Palmieri writes:
>
> > class AlgebraIdeal(object):
> > def __init__(self, A, gens = []):
> > if not isinstance(A, Algebra): raise TypeError, "Argument A
> > must be an algebra."
> > self.__algebra = A
> > self.__gens
On Dec 16, 2008, at 09:07 , Justin C. Walker wrote:
>
>
> On Dec 16, 2008, at 09:01 , John Cremona wrote:
>
>>
>> Patch attached at #4816 but in testing I turned up a strange problem
>> when cloning my new 64-bit 3.2.2.rc0 build.
>
> Have you identified the errant character? Nicolas's name, on
Hi sage-devel,
Thanks to some assistance from Dan and my chair/sysadmin, and a lot of
time trying to figure out vagaries of the not-for-the-faint-of-heart
documentation of Mac shell and Mac app property lists, I have the
following steps to make a Sage app clickable from anywhere which can
be easi
2008/12/16 Justin C. Walker :
>
>
> On Dec 16, 2008, at 09:01 , John Cremona wrote:
>
>>
>> Patch attached at #4816 but in testing I turned up a strange problem
>> when cloning my new 64-bit 3.2.2.rc0 build.
>
> Have you identified the errant character? Nicolas's name, on line 2,
> has extended b
On Dec 16, 2008, at 09:01 , John Cremona wrote:
>
> Patch attached at #4816 but in testing I turned up a strange problem
> when cloning my new 64-bit 3.2.2.rc0 build.
Have you identified the errant character? Nicolas's name, on line 2,
has extended bit in it, but I don't see the problem you
We cannot redefine range() as that's Python. There is Sage's own
srange which returns Integers, and it is probably best to use that.
John
2008/12/16 philt :
>
> Hi all,
>
> I stumbled across a hard-to-find bug in my code because of the way
> Sage redefines integers.
> Usually int is mapped to I
Patch attached at #4816 but in testing I turned up a strange problem
when cloning my new 64-bit 3.2.2.rc0 build.
John
2008/12/16 Justin C. Walker :
>
>
> On Dec 16, 2008, at 08:35 , John Cremona wrote:
>
>>
>> 2008/12/16 mabshoff :
>>>
>>>
>>>
>>> On Dec 16, 8:19 am, "Justin C. Walker" wrote:
>
Hi all,
I stumbled across a hard-to-find bug in my code because of the way
Sage redefines integers.
Usually int is mapped to Integer more or less transparently:
N=3
for i in range(1, N):
print "i=%s N=%s i/N=%s" % (str(i), str(N), str(i/N))
i=1 N=3 i/N=1/3
i=2 N=3 i/N=2/3
Actually N is Inte
On Dec 16, 2008, at 08:35 , John Cremona wrote:
>
> 2008/12/16 mabshoff :
>>
>>
>>
>> On Dec 16, 8:19 am, "Justin C. Walker" wrote:
>>
>>
>>
>>> Built w/o problems on Mac OS X, 10.5.5 (Dual Quad Xeon) as an
>>> upgrade
>>> from 3.2.2.alpha2 (which was built from scratch).
>>>
>>> Testing sho
On Dec 16, 8:35 am, "John Cremona" wrote:
> >> Testing showed one failure, in
> >> devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py
>
> Is there a ticket for this yet?
Justin just opened #4816 for this.
Cheers,
Michael
--~--~-~--~~~---~--~-
2008/12/16 mabshoff :
>
>
>
> On Dec 16, 8:19 am, "Justin C. Walker" wrote:
>
>
>
>> Built w/o problems on Mac OS X, 10.5.5 (Dual Quad Xeon) as an upgrade
>> from 3.2.2.alpha2 (which was built from scratch).
>>
>> Testing showed one failure, in
>> devel/sage/sage/schemes/elliptic_curves/
Hello,
I got some trouble trying to draw polygons in JMol because the
function looks not available easily.
Sage is featuring the following:
point() -> try point2d else point3d
line() -> try line2d else line3d
polygon() -> only 2d
but many fancy volumes are available in 3D...
I think it'd be more
On Dec 16, 8:19 am, "Justin C. Walker" wrote:
> Built w/o problems on Mac OS X, 10.5.5 (Dual Quad Xeon) as an upgrade
> from 3.2.2.alpha2 (which was built from scratch).
>
> Testing showed one failure, in
> devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py
>
> The log f
On Dec 15, 2008, at 23:50 , mabshoff wrote:
>
> Hi,
>
> here goes 3.2.2.rc0. The S-integral point counting code is in, the
> Sage Words library is not, but it will likely be in 3.2.2.rc1. The
> main issue with the Sage Words library are pickle jar failures which
> need to be resolved one way or
This would be awesome!
On Tue, Dec 16, 2008 at 9:45 AM, Jason Grout
wrote:
>
> This is just some brainstorming based on a recent networkx-discussion
> post. Recently there has been some discussion on the networkx mailing
> list about adding mouseovers using an html imagemap. This stemmed from
mabshoff wrote:
> Hi,
>
> here goes 3.2.2.rc0. The S-integral point counting code is in, the
> Sage Words library is not, but it will likely be in 3.2.2.rc1. The
> main issue with the Sage Words library are pickle jar failures which
> need to be resolved one way or the other, but more about that
Built fine and all tests pass on 64-bit Suse.
Built fine and all but one tests pass on 32-bit Suse, the exception
being the known thing in multi_polynomial_ideal.py:
Failed example:
S = R.quotient((x**Integer(2) + y**Integer(2),
Integer(17)),names=('a', 'b')); (a, b,) =
S._first_ngens(Intege
John H Palmieri writes:
> class AlgebraIdeal(object):
> def __init__(self, A, gens = []):
> if not isinstance(A, Algebra): raise TypeError, "Argument A
> must be an algebra."
> self.__algebra = A
> self.__gens = gens
[...]
> sage: J = AlgebraIdeal(R, [y^2])
>
> Then
This is just some brainstorming based on a recent networkx-discussion
post. Recently there has been some discussion on the networkx mailing
list about adding mouseovers using an html imagemap. This stemmed from
this blog entry:
http://hackmap.blogspot.com/2008/06/pylab-matplotlib-imagemap.ht
On Dec 16, 3:59 am, "David Joyner" wrote:
> Hi:
Hi,
> Is there a command, say called packages(method="standard"), which simply
> returns the list of strings of the packages (standard ones only, if the
> "standard" option is given), along perhaps with their version number?
> I don't think so,
On Tue, Dec 16, 2008 at 12:27 AM, Martin Rubey
wrote:
>
> Martin Rubey writes:
>
>> I wanted to install qepcad-1.50, but failed.
>
> just for the record: installing tcsh makes the problem go away. This hint was
> buried in a longer mail on this list, so I repeat it here...
Thank you Martin. I
Hello,
On Tue, Dec 16, 2008 at 3:59 AM, David Joyner wrote:
>
> Hi:
>
> Is there a command, say called packages(method="standard"), which simply
> returns the list of strings of the packages (standard ones only, if the
> "standard" option is given), along perhaps with their version number?
> I d
Hi:
Is there a command, say called packages(method="standard"), which simply
returns the list of strings of the packages (standard ones only, if the
"standard" option is given), along perhaps with their version number?
I don't think so, but progress moves so fast, I could have missed it.
This cou
Hi Dan,
On Mon, Dec 15, 2008 at 7:55 PM, Dan Drake wrote:
> I know this used to work, because the example distributed with SageTeX
> has it! See example.{tex,pdf} from
> http://tug.ctan.org/tex-archive/macros/latex/contrib/sagetex/. Is the
> above code still considered correct, or is there now a
I built rc0 and did a "sage -ba" to re-do the Cython stuff. "make ptest"
went fine, but "make ptestlong" had some dsage errors, which passed when
I re-ran them manually.
Test log is at http://mathsci.kaist.ac.kr/~drake/logs/ptestlong.log.
Dan
--
--- Dan Drake
- KAIST Department of Mathem
On Dec 16, 1:17 am, daveloeffler wrote:
Hi David,
> Installs fine on my machine, but why does doc-3.2.2.spkg contain a pre-
> compiled version of the old 3.2.1 reference manual? The build process
> doesn't (IIRC) automatically rebuild the docs, so we risk leaving
> users with outdated documenta
Installs fine on my machine, but why does doc-3.2.2.spkg contain a pre-
compiled version of the old 3.2.1 reference manual? The build process
doesn't (IIRC) automatically rebuild the docs, so we risk leaving
users with outdated documentation, and it's highly likely that many
won't even realise thi
50 matches
Mail list logo
