Cleanup in the thematic tutorials

[ncohen]

This branch reorders the index of thematic tutorials.

http://www.sagemath.org/doc/thematic_tutorials/

Currently, the hierarchy is not very clear between section/subsections, and very big titles have one or two entries (like "geometry").

This branch flattens it a bit, and reorders it:

• "Programming and Design" is renamed to "Introduction to Sage" (right after 'Introduction to Python')

• 'coding theory' is moved to 'combinatorics' (it had a section of its own before)

• 'Modeling mathematics on a computer' is renamed to '!Parents/!Elements, Categories and algebraic structures' (the whole of Sage is about modelling mathematics, from symbolics to graph theory)

• A short table of contents is added in the "categories primer" http://www.sagemath.org/doc/reference/categories/sage/categories/primer.html

• Same for "group theory" http://www.sagemath.org/doc/thematic_tutorials/group_theory.html#group-theory

• Importantly, all doctests of the "coding theory" tutorial were disabled for they began with "Sage :". I changed that, but there are many broken doctests that I cannot fix myself. This is ticket #17617.

Nathann

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​4645442	trac #17614: Move numerical_sage to thematic_tutorials (and only that)
​612c3cf	trac #17614: Update the links
​c07c428	trac #17615: Move bordeaux_2008 into thematic_tutorials/explicit_methods_in_number_theory/ (and only that)
​3c4d499	trac #17615: Update the links
​89bd621	trac #17616: Cleanup in the thematic tutorials

[mmezzarobba]

This mostly looks good to me, but

• what is the reason for changing "new algebraic structures" to "new algebraic structure" in coercion_and_categories.rst?
• perhaps it would be worth linking to your follow-up ticket in the broken doctests that you marked with not tested

[ncohen]

Yooooooooo !

This mostly looks good to me, but

• what is the reason for changing "new algebraic structures" to "new algebraic structure" in coercion_and_categories.rst?

Adding typos make it easier for newcomers to make their first contributions.

• perhaps it would be worth linking to your follow-up ticket in the broken doctests that you marked with not tested

I do not understand what change you request.

Nathann

(I will push a commit in a second to add this 's')

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​d121ef2

trac #17616: Typo

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​6f74cb9

#17616: link to #17617 in temporarily disabled doctests

[mmezzarobba]

Replying to ncohen:

I do not understand what change you request.

Sorry if I wasn't clear. I committed the change I had in mind.

[ncohen]

Sorry if I wasn't clear. I committed the change I had in mind.

Oh I see. Well, I don't see anything wrong with that.

Nathann

[ncohen]

Thaaaaaaaanks !

[vbraun]

Conflicts, probably with #17614

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​c949950	trac #17615: Merged with 6.5.beta6
​cf7b89a	trac #17615: Broken doctest
​90a576a	trac #17616: Merged with updated #17615

[git]

Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. This was a forced push. New commits:

​21dbfd8	trac #17615: Merged with 6.5.beta6
​e4f3206	trac #17615: Broken doctest
​e1f7d37	trac #17616: Merged with updated #17615

[vbraun]

sage -t --long --warn-long 40.6 src/doc/en/thematic_tutorials/coding_theory.rst
**********************************************************************
File "src/doc/en/thematic_tutorials/coding_theory.rst", line 87, in doc.en.thematic_tutorials.coding_theory
Failed example:
    C = best_known_linear_code(6,3,GF(2))
Exception raised:
    Traceback (most recent call last):
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/doctest/forker.py", line 488, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/doctest/forker.py", line 850, in compile_and_execute
        exec(compiled, globs)
      File "<doctest doc.en.thematic_tutorials.coding_theory[2]>", line 1, in <module>
        C = best_known_linear_code(Integer(6),Integer(3),GF(Integer(2)))
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/coding/linear_code.py", line 437, in best_known_linear_code
        C = gap("BestKnownLinearCode(%s,%s,GF(%s))"%(n,k,q))
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/interfaces/interface.py", line 199, in __call__
        return cls(self, x, name=name)
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/interfaces/expect.py", line 1307, in __init__
        self._name = parent._create(value, name=name)
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/interfaces/interface.py", line 389, in _create
        self.set(name, value)
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/interfaces/gap.py", line 1305, in set
        out = self._eval_line(cmd, allow_use_file=True)
      File "/mnt/disk/home/release/Sage/local/lib/python2.7/site-packages/sage/interfaces/gap.py", line 771, in _eval_line
        raise RuntimeError(message)
    TypeError: Gap produced error output
    Error, Variable: 'BestKnownLinearCode' must have a value

       executing $sage4:=BestKnownLinearCode(6,3,GF(2));;

[git]

Branch pushed to git repo; I updated commit sha1. New commits:

​d780d12

trac #17616: Broken doctest

[ncohen]

Sorry :-/

Nathann