On 2 April 2011 18:08, Robert Bradshaw wrote:
> I think the key point is that there are several metrics for judging
> code. Some judge code by how many compiler warnings it produces, or
> how standard-abiding it is. Others judge code by clarity of the
> expressed algorithm(s).
It's hard for me t
On 4 Apr., 08:26, Simon King wrote:
> 1) cdef classes inheriting from Parent or Element can be provided with
> cached methods, even if they do not allow attribute assignment.
To be precise: They can not be defined in the Cython code, but it will
be possible to provide them via cached parent metho
Hi!
I am just looking at doc/common/sage_autodoc.py, and I notice that the
documentation is obtained by simply taking the __doc__ attribute, if
it exists. That is a problem with method decorators that are written
in Cython, because __doc__ would always provide the documentation of
the decorator, n
On Apr 4, 1:13 pm, William Stein wrote:
> Great idea! Post a ticket.
This is now #11121 and awaits review :)
-Keshav
--
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 option
Is the problem reproducible?
If so, a valgrind log would be useful to debug the problem. It should
find the source of any segfault. zn_poly would need to be compiled
with the -g option to GCC. It could of course be a compiler bug.
Possibly compilation with a lower optimisation level would make it
On 4/3/11 11:08 PM, Rob Beezer wrote:
A friend of mine, Nicole Allen, runs the Student Public Interest
Research Group's "Affordable Textbook Campaign." Her job title is
"Textbook Advocate" - how cool is that?
Part of her job is promoting open source textbooks (how much more
affordable can you g
Currently we have legendre_symbol and kronecker_symbol in the global
namespace. Anyone mind having jacobi_symbol as an alias for
kronecker_symbol but raising an error for 'wrong' input?
Thanks,
- kcrisman
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from
Lots of videos/screencasts using Sage...
-- Forwarded message --
From: Raazesh Sainudiin
Date: Mon, Apr 4, 2011 at 12:07 PM
Subject: Monte Carlo Methods in Sage Lectures in YouTube PlayList
To: William Stein
Dear William,
Due to the earthquake in Christchurch several courses
On 04/ 4/11 01:01 PM, Bill Hart wrote:
Is the problem reproducible?
I'll have to check how reproducible it is by building znpoly repeatedly. But
it's the first failure I've known in what must be more than 100 compete builds
of Sage on this machine.
znpoly is only taking 39 s to build and r
Just a note: the Sage versions rely on the Python random module.
--
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/sa
On Sun, Apr 3, 2011 at 7:01 PM, D. M. Monarres wrote:
> Was working on some code that required the random shuffling of the order of
> a list and noticed that there was both a random() function implemented in
> the sage library and a random module in the python standard library.
> Importing the lat
On Mon, Apr 4, 2011 at 5:01 AM, Bill Hart wrote:
> Is the problem reproducible?
>
> If so, a valgrind log would be useful to debug the problem. It should
> find the source of any segfault. zn_poly would need to be compiled
> with the -g option to GCC. It could of course be a compiler bug.
> Possib
12 matches
Mail list logo
