Hi Andrew,
On Tue, May 17, 2011 at 07:58:34PM -0700, Andrew Mathas wrote:
> 1. Currently the shape of a tableau must be a partition, however, to
> me it seems more natural to allow the shapes to be arbitrary
> compositions -- and certainly I need this sometimes"). I am not sure
> if this
Salut,
I just pushed a rebase of 10335, as I needed it after updating to
4.7.rc2.
On the way, I saw that sage doesn't start properly after 8703 is
applied (right before 10335).
Best, Christian
--
You received this message because you are subscribed to the Google Groups
"sage-combinat-devel" g
On Thu, May 19, 2011 at 08:33:03AM -0700, Christian Stump wrote:
> I just pushed a rebase of 10335, as I needed it after updating to
> 4.7.rc2.
Thanks. Please put back the guards appropriately for those still using
4.6.2.
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil"
On Tue, May 17, 2011 at 03:49:49PM -0700, Simon King wrote:
> I agree that it is not an issue. But for the record: It is in sage/
> categories/primer.py and is as follows.
> sage: p = 6*x^2 + 12*x + 6
> sage: R. = PolynomialRing(QQ, sparse=True)
> sage: pQ = R ( p )
> sage: pQ._pow_
> Thanks. Please put back the guards appropriately for those still using
> 4.6.2.
the guards were
#+4_7 #-4_6_1 # needs rebase
I just deleted #+4.7. It applies properly 4.6.2, so I don't understand
what I should do for 4.6.2.
Thanks, Christian
--
You received this message because you are subs
Hi Nicolas,
> We definitely want a feature of this sort. In MuPAD, we had something
> like T.getxy(i,j) which was doing just that. I think it was discussed
> to allow for T[i,j] or T.get_cell(x,y); T(i,j) could make sense too.
> And we also want T.set_cell(x,y,value) allowing for changing the valu
