Hi Jason, What's the current status of your tableaux patch? I seem to remember that there may be some refactoring issues with 4.6.2 so I thought I should ask first before diving in. I'm currently reinstalling from source to try and get my missing patch queues back...
If it hasn't been reviewed yet then I'd be happy to do it as I need to understand what you have done so that I can sup it up and make corresponding TableauxTuple classes, which I need. I've looked quickly over the patch and have two questions. 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 would break anything apart from the partition checks, but it might. 2. Secondly, what do people think about adding a __call__ method to the Tableaux() class: def __call__(self,cell): """ Return the entry in `cell` of the tableau EXAMPLES:: sage: Tableau([[1,2,3,4],[3,4,2,5]])(0,0) 1 sage: Tableau([[1,2,3,4],[3,4,2,5]])(1,3) 5 """ row=cell[0] col=cell[1] assert row<len(self.shape()) and col<self.shape()[row], 'cell not in diagram' return self[row][col] Of course, currently you can use Tableau([[1,2,3,4],[3,4,2,5]])[0][0] but this would be useful (for me) in writing code which could apply to elements of the classes Tableaux or TableauxTuples. Cheers, Andrew -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
