Hi All,
On 10 Jun., 23:29, "Nicolas M. Thiery"
wrote:
> Note that we also have quite some tutorial material on development on
> the Sage-Combinat queue, and should go into Sage at some point.
Better sooner than later, I'd say. Why is it not in the thematic
tutorials yet? Is a review missing?
If
Hi Niles,
On Sat, Jun 11, 2011 at 3:16 AM, Niles wrote:
> Thanks; I just tried it out. Here are some minor comments:
>
> * The phrase "bleeding edge" still appears in the download directory
> [1], and also in the readme file.
>
> * The large warning says the directory contains "builds", which lea
What about calling them "development snapshots"?
-Keshav
Join us in #sagemath on irc.freenode.net !
--
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
Dear Simon, dear all,
+1 on Simon extending his notes to a full tutorial!
Note that we also have quite some tutorial material on development on
the Sage-Combinat queue, and should go into Sage at some point. We
should think about their respective perimeter. In any cases, please
feel free
Thanks; I just tried it out. Here are some minor comments:
* The phrase "bleeding edge" still appears in the download directory
[1], and also in the readme file.
* The large warning says the directory contains "builds", which lead
me to think that I was downloading a binary for my system (even
th
On 6/10/11 11:22 AM, Robert Bradshaw wrote:
Maybe pending? Is this for positively reviewed tickets? Is
"needs-info" insufficient.
What about new tickets? Should they be on the current release milestone
still?
Jason
--
To post to this group, send an email to sage-devel@googlegroups.com
To
Maybe pending? Is this for positively reviewed tickets? Is
"needs-info" insufficient.
On Fri, Jun 10, 2011 at 1:38 AM, Jeroen Demeyer wrote:
> Hello,
>
> I have created a new milestone on Trac: "sage-wait" meant for tickets
> which are not ready to be merged, for example because they depend on a
On Fri, Jun 10, 2011 at 3:23 AM, Maarten Derickx
wrote:
> To solve this problem you can offcourse put your generator matrix in
> echelon form and remove the nonzero rows. He check might not be in the
> code for performance reasons but I didn't wrote the code so I'm not
> sure.
>
> Maybe the best w
On 10 June 2011 10:36, Burcin Erocal wrote:
> Hi,
>
> On Fri, 10 Jun 2011 09:27:47 +0100
> Martin Albrecht wrote:
>
>> I'm wondering whether we should do a Sage-FLINT days thingy/coding
>> sprint (either somewhere in the big blue room or online) to make use
>> of all the cool new features in FLIN
On 10 June 2011 13:59, Bill Hart wrote:
> On 10 June 2011 10:36, Burcin Erocal wrote:
>> Hi,
>>
>> On Fri, 10 Jun 2011 09:27:47 +0100
>> Martin Albrecht wrote:
>>
>>> I'm wondering whether we should do a Sage-FLINT days thingy/coding
>>> sprint (either somewhere in the big blue room or online) t
Hi,
On Fri, 10 Jun 2011 09:27:47 +0100
Martin Albrecht wrote:
> I'm wondering whether we should do a Sage-FLINT days thingy/coding
> sprint (either somewhere in the big blue room or online) to make use
> of all the cool new features in FLINT 2.x?
>
> Or should we wait until everything from 1.5
Hello,
I have created a new milestone on Trac: "sage-wait" meant for tickets
which are not ready to be merged, for example because they depend on a
non-trivial ticket or because there is some discussion about the ticket.
Better naming suggestions are always welcome.
Jeroen.
--
To post to this
Hi,
I'm wondering whether we should do a Sage-FLINT days thingy/coding sprint
(either somewhere in the big blue room or online) to make use of all the cool
new features in FLINT 2.x?
Or should we wait until everything from 1.5 are in 2.x?
Cheers,
Martin
--
name: Martin Albrecht
_pgp: http://
To solve this problem you can offcourse put your generator matrix in
echelon form and remove the nonzero rows. He check might not be in the
code for performance reasons but I didn't wrote the code so I'm not
sure.
Maybe the best way to solve this problem is to standardly check for
full rank and ha
14 matches
Mail list logo
