Ticket #13801 (closed defect: fixed)
Fix facade set category initialisation
|Reported by:||vdelecroix||Owned by:||vdelecroix|
|Component:||categories||Keywords:||category, facade, days45|
|Report Upstream:||N/A||Reviewers:||Travis Scrimshaw|
|Authors:||Vincent Delecroix||Merged in:||sage-5.8.beta0|
Description (last modified by vdelecroix) (diff)
Facade sets are used in many places but there are two small errors that prevent from using it everywhere...
The first error concerns multiple categories initialisation. Here is a minimal example
class A(Parent): def __init__(self): Parent.__init__(self, category=((FiniteEnumeratedSets(),Monoids()), facade=True)
for which we get
sage: A() Traceback (most recent call last): ... AttributeError: 'tuple' object has no attribute 'is_subcategory'
The second problem concerns the behavior of .facade_for() which is better explained with a minimal example
class B(Parent): def __init__(self): Parent.__init__(self, category=Sets(), facade=True)
for which we get
sage: b = B() sage: b.facade_for() Traceback (most recent call last): ... AttributeError: 'B_with_category' object has no attribute '_facade_for'
The ticket provides the (trivial) corrections for both problems and add two doctests.
- Status changed from new to needs_review
- Description modified (diff)
- Keywords facade, days45 added; facade removed
- Reviewers set to Travis Scrimshaw
- Status changed from needs_review to positive_review
- Status changed from positive_review to closed
- Resolution set to fixed
- Milestone changed from sage-5.7 to sage-5.8
comment:10 Changed 3 months ago by jdemeyer
- Status changed from closed to new
- Resolution fixed deleted