Hi there,

I've been chasing the following bug for quite a long time...

sage: p1 = Posets(6)[85]; p2 = Posets(6)[35]
sage: p1.cover_relations()
[[0, 1], [0, 2], [3, 5], [4, 5]]
sage: p2.cover_relations()
[[0, 1], [0, 2], [1, 3], [1, 4], [2, 3], [2, 4], [3, 5], [4, 5]]
sage: p1 == p2
True
sage: p1.__eq__
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)

/home/averell/.sage/temp/tomahawk/21813/_home_averell_recherche_00SVN_FRG_Articles_Hivert_Schilling_Thiery_HeckeMonoid_main_sage_4.py
 in <module>()

AttributeError: 'FinitePoset' object has no attribute '__eq__'

I tried to fix it in trac_7538_poset_equal_fix-fh.patch but this is  not quite
good:

sage: p1, p2 = Posets(2).list()
sage: p2 < p1
True

sage: [[p1.__cmp__(p2) for p1 in Posets(2)] for p2 in Posets(2)]
[[0, 1], [1, 0]]
sage: [[p2.__cmp__(p1) for p1 in Posets(2)] for p2 in Posets(2)]
[[0, 1], [-1, 0]]
sage: p2 < p1
False

!!!

Is there any reason to define cmp and not only __eq__ ? What is the intended
semantic of this comparison ? 

Cheers,

Florent

--

You received this message because you are subscribed to the Google Groups 
"sage-combinat-devel" group.
To post to this group, send email to sage-combinat-de...@googlegroups.com.
To unsubscribe from this group, send email to 
sage-combinat-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sage-combinat-devel?hl=en.


Reply via email to