#9107: Nested class name mangling can be wrong in case of double nesting
------------------------------+--------------------------------------------
Reporter: hivert | Owner: nthiery
Type: defect | Status: needs_work
Priority: major | Milestone: sage-5.12
Component: categories | Resolution:
Keywords: | Merged in:
Authors: Simon King | Reviewers: Volker Braun, Florent Hivert
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: #12808 | Stopgaps:
------------------------------+--------------------------------------------
Comment (by tscrim):
Hey Nicolas and Simon,
The problem comes from the fact that there is a 4 level deep class nesting
with a method (which is 5 levels deep) in the
`Sets.WithRealizations.ParentMethods.Realizations.super_categories`. I've
tried moving this subclass into a separate class, and this solves the pdf
build issue but introduces some doctesting errors. I don't think there is
a way to extend the nesting level since that is a latex thing, nor do I
think we should try since 4 nested classes is a lot IMO. I'm guessing
beforehand because of the improper naming, latex did the environments
differently...?
Anyways the fix for the pdf build is to remove a level (or two) of class
nesting.
Best,[[BR]]
Travis
--
Ticket URL: <http://trac.sagemath.org/ticket/9107#comment:39>
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.
