#10963: More functorial constructions
-------------------------------------+-------------------------------------
Reporter: nthiery | Owner: stumpc5
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.1
Component: categories | Resolution:
Keywords: days54 | Merged in:
Authors: Nicolas M. Thiéry | Reviewers: Simon King, Frédéric
Report Upstream: N/A | Chapoton
Branch: | Work issues:
public/ticket/10963 | Commit:
Dependencies: #11224, #8327, | 8045aa4a4b7ada735b3eb6055382f9b341a39f1e
#10193, #12895, #14516, #14722, | Stopgaps:
#13589, #14471, #15069, #15094, |
#11688, #13394, #15150, #15506 |
-------------------------------------+-------------------------------------
Comment (by vbraun):
At least implementing a kind of "axiom enum" type leverages some of
Python's code inspection capabilities. But IMHO there is a reason that it
took until Python 3.4 and at least one failed PEP for enums to make it
into Python: there are few compelling use cases in a completely dynamic
language. You can pass anything to a method and store anything as an
attribute, so instead of an enum value you can always use the enumerated
thing. And I don't buy that there is no code or data that we could
possibly attach to axioms. Why not
{{{#!python
class Finite(Axiom):
class ParentMethods:
def is_finite(self): return True
class Groups(Category):
class ParentMethods:
@requires_axiom(Finite())
def is_finite_group(self): return True
}}}
--
Ticket URL: <http://trac.sagemath.org/ticket/10963#comment:394>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
