Am 2015-01-12 um 22:07 schrieb David Roe:
I would say that, ideally, the kind of functionality that
you're moving from Group to Monoid should go in the categories. Then we
don't need an intermediate class in the Python inheritance tree.
Does this also mean, that (ideally) there shouldn't even
Am 2015-01-12 um 22:07 schrieb David Roe:
This is a circular import error. If you look at the chain of imports,
you'll see that earlier you're in the file sage/rings/all.py, and the
error occurs when you later try to import sage.rings.all.
A brief glance at your code doesn't reveal the
This is a circular import error. If you look at the chain of imports,
you'll see that earlier you're in the file sage/rings/all.py, and the
error occurs when you later try to import sage.rings.all.
A brief glance at your code doesn't reveal the cause of the problem for me,
though it could be
In
http://trac.sagemath.org/ticket/17626
the group class should have a newly created monoid class as a base. At
the moment the group and the monoid parent do not have much in common
(but their elements have).
I've started implementing this, but have a rather strange problem. See
below the
