#15475: Reenable broken doctests in #15473 and #15476 when #10963 is merged
-------------------------------------+-------------------------------------
Reporter: darij | Owner:
Type: defect | Status: needs_work
Priority: minor | Milestone: sage-6.3
Component: categories | Resolution:
Keywords: 10963, | Merged in:
categories, c3, coercion, | Reviewers:
transitivity, descent algebras, | Work issues:
symmetric functions | Commit:
Authors: | ef918e33132d7bf77dd999696a0efd891d831377
Report Upstream: N/A | Stopgaps:
Branch: |
public/categories/15475 |
Dependencies: #10963, #15473, |
#15476 |
-------------------------------------+-------------------------------------
Comment (by SimonKing):
Replying to [comment:15 darij]:
> EDIT: On the other hand, commenting out `self._coercions_used = True` in
parent.pyx does not fix the error. But why do we have this kind of flag
anyway? How on earth do we want to know if all coercions from/to a given
objects are already known? Why on earth do we want this information?
If I understand correctly, this flag is only relevant if we want to
explicitly set a new coercion via `register_coerce_map_from` or something
of that kind (can't look into the code right now). The idea is that the
explicit registrations happens during initialisation, whereas the
automatic discovery of coerce maps by backtracking happens later and is
not hampered by `self._coercions_used`.
--
Ticket URL: <http://trac.sagemath.org/ticket/15475#comment:16>
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/d/optout.
