On Fri, May 18, 2012 at 04:07:02AM -0700, Mike Zabrocki wrote:
> I also found the same behavior (I don't know why it worked before).
>Thanks Nicolas for identifying the real problem. That doctest failure
>with .nabla() would have been a mystery forever.
That's my job :-)
I am sur
On Fri, May 18, 2012 at 01:43:27AM -0700, Anne Schilling wrote:
> I opened a ticket
> http://trac.sagemath.org/sage_trac/ticket/12969
>
> For the record, this problem also occurs in plain sage-5.0 without the new
> symmetric function patch in the sage-combinat queue applied that Mike
> and I have
Hi Anne,
I also found the same behavior (I don't know why it worked before).
Thanks Nicolas for identifying the real problem. That doctest failure
with .nabla() would have been a mystery forever.
-Mike
On Friday, 18 May 2012 04:43:27 UTC-4, Anne Schilling wrote:
>
> Nicolas, thanks so much
Nicolas, thanks so much for figuring out where the problem is!
I opened a ticket
http://trac.sagemath.org/sage_trac/ticket/12969
For the record, this problem also occurs in plain sage-5.0 without the new
symmetric function patch in the sage-combinat queue applied that Mike
and I have been working
On Thu, May 17, 2012 at 07:27:31PM -0400, Mike Zabrocki wrote:
> It is the test for the function .nabla() that was failing (I think like 836).
>
> sage: Sym = SymmetricFunctions(FractionField(QQ['q','t']))
> sage: P = Sym.macdonald().P()
> sage: P([1,
