I have the same sort of issues with an old laptop with Pentium M CPU
(banias 1.1GHz, http://ark.intel.com/Product.aspx?id=27600)
Actually, I think the idea of re-running Altas install from scratch,
many times, as the spkg does, makes not too much sense. Googling that
issues shows that one should r
oops, Trac has eaten up my last update. Or I forgot to hit "submit"...
Done now, at last.
Dima
On Dec 18, 6:32 am, John H Palmieri wrote:
> On Dec 16, 8:57 pm, Dima Pasechnik wrote:
>
> > I've given it positive review.
>
> Can you please update the ticket to reflect that?
>
> Thanks,
> John
On 12/17/10 6:27 PM, Eviatar wrote:
Sure. Here it is:
http://www.mediafire.com/?wml7036fymeb30w
I believe this is just an issue with the aspect ratio of the matrix plot
in Sage. I notice in my copy of Sage, the patch at #2100 [1] applied, I
get the attached figure. There still are some su
Sure. Here it is:
http://www.mediafire.com/?wml7036fymeb30w
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-d
On Dec 16, 8:57 pm, Dima Pasechnik wrote:
> I've given it positive review.
Can you please update the ticket to reflect that?
Thanks,
John
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegro
On 12/17/10 4:20 PM, Eviatar wrote:
Hello all,
matrix_plot seems to have problems making accurate graphics.
For example, this is a plot of the Sierpinski triangle, and you can
see some rectangular points:
http://tinyurl.com/24nfbuz
This also occurs when saving a matrix plot as an svg:
matrix_
Hello all,
matrix_plot seems to have problems making accurate graphics.
For example, this is a plot of the Sierpinski triangle, and you can
see some rectangular points:
http://tinyurl.com/24nfbuz
This also occurs when saving a matrix plot as an svg:
matrix_plot(a).save('/home/username/Desktop/p
On Dec 17, 2010, at 11:54 , John H Palmieri wrote:
> On Dec 17, 9:56 am, "Justin C. Walker" wrote:
>> Thanks for all the comments...
> Well, I just put this in a file and doctested it. It passed:
>
> TESTS::
>
>sage: print "hello, hello"
>hello, hello
>sage: print "hello, he
On Dec 17, 9:56 am, "Justin C. Walker" wrote:
> Thanks for all the comments...
>
> On Dec 16, 2010, at 23:57 , Dan Drake wrote:
>
> > On Thu, 16 Dec 2010 at 09:12PM -0800, Justin C. Walker wrote:
> >> I have a doctest that results in a long (400-byte) string of output.
> >> Is there a simple way t
Thanks for all the comments...
On Dec 16, 2010, at 23:57 , Dan Drake wrote:
> On Thu, 16 Dec 2010 at 09:12PM -0800, Justin C. Walker wrote:
>> I have a doctest that results in a long (400-byte) string of output.
>> Is there a simple way to tell the doctest code to ignore whitespace
>> (in particu
Hi folks,
The situation with weighted() is even more bizarre:
sage: version()
'Sage Version 4.6.1.alpha3, Release Date: 2010-12-05'
sage: G = Graph({1:{2:3}})
sage: G.weighted()
False
sage: G.weighted('a')
sage: G.weighted()
'a'
sage: G.weighted(True)
sage: G.weighted()
True
Python recognizes a
On Fri, Dec 17, 2010 at 9:16 AM, Jeroen Demeyer wrote:
> Blocker ticket #9163 has a patch and needs review. It fixes a doctest
> failure in sage/interfaces/expect.py. The ticket claims the error
> happens on Cygwin and OS X. I have tested the fix only on OS X 10.6.
I cannot test this on Cygwin
Blocker ticket #9163 has a patch and needs review. It fixes a doctest
failure in sage/interfaces/expect.py. The ticket claims the error
happens on Cygwin and OS X. I have tested the fix only on OS X 10.6.
Jeroen.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubs
you can linebreak the output, for example the following is valid:
sage: set([1,2,3])
set([1,
2,
3])
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For m
On 2010-12-17 06:12, Justin C. Walker wrote:
> Hi, all,
>
> I have a doctest that results in a long (400-byte) string of output. Is
> there a simple way to tell the doctest code to ignore whitespace (in
> particular, newlines) when comparing output? I don't think putting that
> output in the
Hi
On Dec 17, 11:52 am, Karen Bindash
wrote:
> Did you really mean Sage 3.6 or was you intending to write 4.6?
Woops. Yes, 4.6.
regards,
Jan
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegr
Did you really mean Sage 3.6 or was you intending to write 4.6?
If you did mean 3.6, then the ATLAS package would have changed a lot
since Sage 3.6.
Dave
On 12/16/10, Jan Groenewald wrote:
> Hi
>
> I had ATLAS fail to build from sage-3.6 running Ubuntu 10.04.1
> on an HP Probook 4515s with and
Sorry, the above was me logged into the wrong email account. Please
disregard. :)
Here's an example of the kind of test you can write:
sage: for x in range(10):
... print x
...
0
...
9
You may notice that the line continuations in the above example are
prefixed with "..
I believe you can represent output by the first line, a line
containing only "..." (appropriately indented of course), and then the
last line. There are other arrangements by which you can use this
elision arrangement - see the python doctest documentation for more
about this. Best practice is to p
19 matches
Mail list logo
