#15279: RootSystem __init__ builds the dual twice, breaking initialization of 
non-
crystallographic root systems
----------------------------+----------------------------------------------
   Reporter:  darij         |            Owner:
       Type:  defect        |           Status:  new
   Priority:  major         |        Milestone:  sage-5.13
  Component:  PLEASE        |         Keywords:  root-system, sage-combinat
  CHANGE                    |          Authors:  Darij Grinberg
  Merged in:                |  Report Upstream:  N/A
  Reviewers:                |           Branch:
Work issues:                |     Dependencies:
     Commit:                |
   Stopgaps:                |
----------------------------+----------------------------------------------
 Relevant piece of the code:
 {{{
         if as_dual_of is None:
             self.dual_side = False
             self.dual = RootSystem(self._cartan_type.dual(),
 as_dual_of=self);
             # still fails for CartanType G2xA1
             try:
                 self.dual = RootSystem(self._cartan_type.dual(),
 as_dual_of=self);
             except StandardError:
                 pass
 }}}
 The definition of {{{self.dual}}} is done twice, one time in a try clause,
 one time outside. I don't know if the breaking of non-crystallographic
 root systems is intentional or not (might be it is because there doesn't
 seem to be much functionality implemented for that), but it certainly
 slows down things.

--
Ticket URL: <http://trac.sagemath.org/ticket/15279>
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.

Reply via email to