Re: [sage-combinat-devel] comments/questions on poset code

2012-02-18 Thread Anne Schilling
> In part. But more importantly because LinearExtensionsOfPoset accepts > a list as input, and lists are not hashable. So class call needs to > transform it into a tuple before passing it down to > UniqueRepresentation. See the documentation of UniqueRepresentation > for details. Ok, thank you! >

Re: [sage-combinat-devel] comments/questions on poset code

2012-02-18 Thread Florent Hivert
Hi Anne, > Thanks! The only problem is that when it is not yet imported one gets the > same error and hence it is hard to locate: You should use "search_src": sage: search_src("ClonableInt") sets/finite_set_map_cy.pxd:14:from sage.structure.list_clone cimport ClonableIntArray sets/finite_

Re: [sage-combinat-devel] comments/questions on poset code

2012-02-18 Thread Anne Schilling
On 2/18/12 9:40 AM, Nicolas Borie wrote: > Le samedi 18 février 2012 à 09:29 -0800, Anne Schilling a écrit : >> Which patch is ClonableIntArray in? For me it is not defined (and I am >> hesitant to base my >> code on something not yet in sage): >> >> sage: class toto(ClonableIntArray): >> :

Re: [sage-combinat-devel] comments/questions on poset code

2012-02-18 Thread Anne Schilling
I have some other problems with the view command: sage: P = Poset(([1,2], [[1,2]]), cover_relations = True) sage: H = P.hasse_diagram() sage: H._latex_() == P._latex_() True sage: view(H) works, but sage: view(P) blows up An error occurred. This is pdfTeXk, Version 3.1415926-1.40.9 (Web2C 7.5.

Re: [sage-combinat-devel] comments/questions on poset code

2012-02-18 Thread Anne Schilling
Great, thanks! I now added a _latex_ method to FinitePosets. However, without my patch applied I get doc test failures in /combinat/posets/posets.py which did not happen before. Did something substantial change that causes these failures? Cheers, Anne posets anne$ hg qtop trac_9280-graded-alg

Re: [sage-combinat-devel] comments/questions on poset code

2012-02-18 Thread Florent Hivert
On Sat, Feb 18, 2012 at 06:40:17PM +0100, Nicolas Borie wrote: > Le samedi 18 février 2012 à 09:29 -0800, Anne Schilling a écrit : > > Which patch is ClonableIntArray in? For me it is not defined (and I am > > hesitant to base my > > code on something not yet in sage): > > > > sage: class toto(Cl

Re: [sage-combinat-devel] comments/questions on poset code

2012-02-18 Thread Nicolas Borie
Le samedi 18 février 2012 à 09:29 -0800, Anne Schilling a écrit : > Which patch is ClonableIntArray in? For me it is not defined (and I am > hesitant to base my > code on something not yet in sage): > > sage: class toto(ClonableIntArray): > : def check(self): pass > : > --

Re: [sage-combinat-devel] comments/questions on poset code

2012-02-18 Thread Anne Schilling
On 2/17/12 12:13 AM, Florent Hivert wrote: >>> By the way: changing P.linear_extensions() to return an enumerated set >>> rather than a plain list could make sense, assuming there is no speed >>> loss. This might require a bit of cythonification; maybe using >>> ClonableArray will be enough. It's s

Re: [sage-combinat-devel] Sage-Combinat on Sage 5.0.beta4 and updated sage-combinat script

2012-02-18 Thread Vincent Delecroix
2012/2/18, Nicolas M. Thiery : > Hi Florent, Vincent, > > All my edits in the series file to carefully craft guards on the > patches that are already merged in 5.0 got discarded in one of the > recent merge! > > I reinstated them, so the queue should work again ... That should be me! I made

Re: [sage-combinat-devel] Sage-Combinat on Sage 5.0.beta4 and updated sage-combinat script

2012-02-18 Thread Nicolas M. Thiery
Hi Florent, Vincent, All my edits in the series file to carefully craft guards on the patches that are already merged in 5.0 got discarded in one of the recent merge! I reinstated them, so the queue should work again ... Cheers, Nicolas -- Nicolas M. Thiér

Re: [sage-combinat-devel] lazy enumerated set

2012-02-18 Thread Vincent Delecroix
Finally I implemented two decorators : one for functions and one for methods and everything seems to work. The last version is in sage-combinat queue. I have to write down documentation but the ticket should be finalized today. If you have any remark on naming convention, architecture, possible i