On Thu, Jul 19, 2012 at 02:21:52AM -0700, Simon King wrote:
>Thus, it seems to me that this is an ideal application of parents with
>multiple realisations. Nicolas, perhaps you can comment on the sage-devel
>thread?
Thanks Simon for the heads up! I am in vacations right now so won't be
On Sun, Jul 22, 2012 at 10:44:36AM +0200, Martin Rubey wrote:
> I am not completely sure I see your point: do you mean, that it is often
> the case that a doctest fails because of a *different* patch? And once
> that one is fixed, the patch owner would modify his own?
My typical use case: I work
Andrew Mathas writes:
> Thanks for posting the errors showing up in partition.py. It seems
> that you have an older version of the patch (which should have still
> passed the doc tests), or possibly a misapplied one. It should go away
> when you merge, but Anne says that my patch is not applying
FYI, the next glitch is a trivial rebase of 12215_segfault_fixes.patch over
trac_5457-symmetric_functions-mz.patch. 12215 is needed in order to get a
bunch of the category patches to apply.
cheers,
Hugh
On Sunday, July 22, 2012 5:46:40 PM UTC+9, Martin wrote:
>
> I just compiled successful
2. We currently have a nested series of classes for tableaux, one branch of
which is
> Tableaux > SemistandardTableaux > StandardTableaux > StandardTableaux_n >
> StandardTableaux_partition
>
> My question is, does there exist an efficient way of making use of the
> class hierarchy to construct
Hi Everyone,
I have a few questions about people's thoughts and the sage-combinat
philosophy on the best way of implementing some things. I'll start with the
more general ones and then specialise to those which just concerning
tableaux and partitions. Sorry, this has turned into a rather long e
On Sun, Jul 22, 2012 at 10:46:40AM +0200, Martin Rubey wrote:
> I just compiled successfully sage 5.2.rc0 (with an install of the
> openssl pkg in the middle).
>
> However, the queue doesn't apply:
>
> trac_13169-permgroup_doctests-nt.patch
This patch has been merged in 5.2.rc0. I just updated t
On Fri, Jul 20, 2012 at 07:47:33AM -0700, Anne Schilling wrote:
> > We could modify the Sage Patchbot ( http://patchbot.sagemath.org/ ) to
> > test the Combinat queue automatically.
>
> That sounds like a good idea. I would also like to have a computer set-up
> (like the new upcoming combinat.sage
I just compiled successfully sage 5.2.rc0 (with an install of the
openssl pkg in the middle).
However, the queue doesn't apply:
patching file sage/groups/perm_gps/permgroup.py
Hunk #1 FAILED at 279
1 out of 1 hunks FAILED -- saving rejects to file
sage/groups/perm_gps/permgroup.py.rej
patching fi
"Nicolas M. Thiery" writes:
> On Thu, Jul 19, 2012 at 11:45:09PM +0200, Martin Rubey wrote:
>> two things turned out to be very useful:
>>
>> 1) being able to mark tests as "expected to fail"
>
> That's certainly a nice too, but I would not advocate this in our
> situation, or at least not for
Hi Martin!
On Thu, Jul 19, 2012 at 11:45:09PM +0200, Martin Rubey wrote:
> Although I am now relieved that I didn't break anything, let me add one
> other idea: in the unittesting package for fricas, two things turned out
> to be very useful:
>
> 1) being able to mark tests as "expected t
11 matches
Mail list logo
