Changes between Initial Version and Version 4 of Ticket #11935


Ignore:
Timestamp:
10/18/11 09:57:28 (8 years ago)
Author:
SimonKing
Comment:

Replying to SimonKing:

I suggest that I create patches for both 2. and 3., and then people can tell what they think about it. The method resolution will then be taken care of by another patch.

I just argued myself into splitting the ticket: This here will be for the base ring independent parent/element classes, and another one will be for method resolution order.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11935

    • Property Summary changed from Make parent/element classes independent of base rings and the category graph consistent with method resolution to Make parent/element classes independent of base rings
  • Ticket #11935 – Description

    initial v4  
    1 At #11900 and [http://groups.google.com/group/sage-combinat-devel/browse_thread/thread/99c74827d704e677 sage-combinat-devel], as well as in some comments in sage/categories/category.py, the idea was discussed to make
    2 
    3  * `C.all_super_categories()` consistent with `C.parent_class.mro()` and `C.element_class.mro()`.
    4  * `Algebras(GF(3)).parent_class==Algebras(GF(5)).parent_class` - hence, make the parent/element classes as independent from the base of a category as possible.
    5 
    6 I think it should be fine to have both in one ticket.
     1At #11900 and [http://groups.google.com/group/sage-combinat-devel/browse_thread/thread/99c74827d704e677 sage-combinat-devel], as well as in some comments in sage/categories/category.py, the idea was discussed to make, for example, `Algebras(GF(3)).parent_class==Algebras(GF(5)).parent_class` - hence, make the parent/element classes as independent from the base of a category as possible.