This has been a very interesting discussion...
There are pros and cons to modularity, and it's worth noting that this can
be done at various different levels. For example, where I work we have a
single, monolithic codebase (very convenient) but at the same time have
fairly strict, explicit depende
On Tue, 26 Apr 2016, Kiran Kedlaya wrote:
Yes, but the docstring itself still needs to be corrected: it says 'for
example "Matrix.random(GF(3), 2)" never generates "[[2,0],[0,2]]".' without
the flag.
OK, I added that to http://trac.sagemath.org/ticket/20465 .
--
Jori Mäntysalo
On Sunday, April 24, 2016 at 4:13:44 AM UTC-7, Jori Mäntysalo wrote:
>
> On Sun, 24 Apr 2016, Volker Braun wrote:
>
> >Warning: Matrices generated are not uniformly distributed. For
> > unimodular matrices over finite field this function does not even
> >
> > At least its not THAT pr
Hi,
On Tue, Apr 26, 2016 at 09:53:27AM -0700, William Stein wrote:
> Hi,
>
> A few years ago Keith Clawson worked for me/UW partly on maintaining
> sage development infrastructure. He bought the domain sagedev.org
> somewhere, and set it up for some purposes. I have access to the
> route 53 DN
Hi,
A few years ago Keith Clawson worked for me/UW partly on maintaining
sage development infrastructure. He bought the domain sagedev.org
somewhere, and set it up for some purposes. I have access to the
route 53 DNS entries for the domain, and was going to delete it, since
he has long stopped
On Tuesday, April 26, 2016 at 1:53:41 AM UTC-7, Johan S. R. Nielsen wrote:
>
> Basically, I don't understand why this def should be a property, and it
> seems to me to be problematic. Specifically:
>
> 1) This is a property that can throw an exception. Isn't that a problem?
>
> 2) This is a prop
So I finally figured out a way to get NTL to work in thread-safe mode
on a much broader range of platforms, including Mac OSX (10.10 and above)
and Linux with somewhat older gcc's (gcc version 4.8 and above).
This new version of NTL still requires many C++11 features in
thread-safe mode, but it do
Hi
I came across the following in sage/matrix/matrix2.pyx:14367:
@property
def I(self):
r"""
Returns the inverse of the matrix, if it exists.
"""
return ~self
Basically, I don't understand why this def should be a property, and it
seems to me to b
Sage documentation contains nice indexes of for example graph functions.
It has for example subheaders "Graph products", "Paths and cycles" etc.
Another example is static finite posets, that have most functions listed
at
http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/posets/po
