ASKSAGE: Sage Q&A Forum - Individual question feedhttps://ask.sagemath.org/questions/Q&A Forum for SageenCopyright Sage, 2010. Some rights reserved under creative commons license.Fri, 27 Feb 2015 10:01:05 -0600Incorrect parsing of docstring of sage.structure.indexed_generators.IndexedGeneratorshttps://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/[This is more of a bug report, but I'm not sure how to report bugs.]
I'm running 'Sage Version 6.5.rc0, Release Date: 2015-01-29' and when I display the help for `sage.structure.indexed_generators.IndexedGenerators` I get some weird formatting error. It's coming from line 103 of the file `$SAGE_ROOT/local/lib/python2.7/site-packages/sage/structure/indexed_generators.py` where a \left is displayed as `<=ft`. It seems that `\le` in `\left` gets replaced by `<=`.
Sat, 07 Feb 2015 03:28:31 -0600https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/Answer by kcrisman for <p>[This is more of a bug report, but I'm not sure how to report bugs.]</p>
<p>I'm running 'Sage Version 6.5.rc0, Release Date: 2015-01-29' and when I display the help for <code>sage.structure.indexed_generators.IndexedGenerators</code> I get some weird formatting error. It's coming from line 103 of the file <code>$SAGE_ROOT/local/lib/python2.7/site-packages/sage/structure/indexed_generators.py</code> where a \left is displayed as <code><=ft</code>. It seems that <code>\le</code> in <code>\left</code> gets replaced by <code><=</code>.</p>
https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?answer=25768#post-id-25768I'm surprised this was never noticed before. See http://trac.sagemath.org/ticket/17745. Sat, 07 Feb 2015 20:44:07 -0600https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?answer=25768#post-id-25768Comment by kcrisman for <p>I'm surprised this was never noticed before. See <a href="http://trac.sagemath.org/ticket/17745">http://trac.sagemath.org/ticket/17745</a>. </p>
https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?comment=25889#post-id-25889If you find any more, please consider posting them at the ticket directly - hopefully it will all be fixed, anyway the infrastructure will exist once this ticket gets in.Sat, 21 Feb 2015 15:52:58 -0600https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?comment=25889#post-id-25889Comment by SL for <p>I'm surprised this was never noticed before. See <a href="http://trac.sagemath.org/ticket/17745">http://trac.sagemath.org/ticket/17745</a>. </p>
https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?comment=25872#post-id-25872Another such issues appear for `dirac_delta`, `heaviside`, `unit_step`. A `\left` gets replaced by `<=ft`.Thu, 19 Feb 2015 03:34:08 -0600https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?comment=25872#post-id-25872Comment by kcrisman for <p>I'm surprised this was never noticed before. See <a href="http://trac.sagemath.org/ticket/17745">http://trac.sagemath.org/ticket/17745</a>. </p>
https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?comment=25952#post-id-25952Yeah, this just isn't a great venue for continuing reports, nor is it efficient. I've opened http://trac.sagemath.org/ticket/17870 for more such issues. We definitely value such diligent work, it makes things look much more professional.Fri, 27 Feb 2015 10:01:05 -0600https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?comment=25952#post-id-25952Comment by SL for <p>I'm surprised this was never noticed before. See <a href="http://trac.sagemath.org/ticket/17745">http://trac.sagemath.org/ticket/17745</a>. </p>
https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?comment=25937#post-id-25937@kcrisman, I don't have a Trac account yet, I should probably get one. I did find another instance of this problem in the documentation of `dodecahedron`.Wed, 25 Feb 2015 23:37:16 -0600https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?comment=25937#post-id-25937Comment by SL for <p>I'm surprised this was never noticed before. See <a href="http://trac.sagemath.org/ticket/17745">http://trac.sagemath.org/ticket/17745</a>. </p>
https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?comment=25826#post-id-25826I noticed another similar (related?) issue in the help for the `timeit` command. The help contains
sage: timeit("a = 2nb=131nfactor(a^b-1)", number=25)
25 loops, best of 3: ... per loop
where some `\n` have been replaced by `n`.Sat, 14 Feb 2015 07:54:41 -0600https://ask.sagemath.org/question/25763/incorrect-parsing-of-docstring-of-sagestructureindexed_generatorsindexedgenerators/?comment=25826#post-id-25826