#sphinx-doc

[02sphinx] 07birkenfeld pushed 032 commits to 03master [+0/-0/±6] 13http://git.io/5vBuxg

[02sphinx] 07EricFromCanada 035d96523 - Fix LaTeX writer's handling of multirow table cells Originally the LaTeX writer could only handle one multirow cell per row. This commit fixes that and adds support for cells spanning both rows and columns.

[02sphinx] 07birkenfeld 03a53e105 - Merge pull request #1667 from EricFromCanada/latex-multirow Fix LaTeX writer's handling of multirow table cells

Has anyone attempted to programmatically rewrite epydoc docstrings to reST when using autodoc? My understanding is that they're less expressive (more of a presentation language than markup) so I'm guessing it would be hard or impossible.

Having spent a lot of time writing epytext markup, I can't think of any major problems you'd run in to.

There really isn't much difference between "@param foo:" and ":param foo" or "C{foo}" and "``foo``".

Yep. The issue I have is that I'd like to rewrite "Foo bar C{SomeClass}" to "Foo bar :py:class`SomeClass`", rather than "Foo bar ``SomeClass``"

You can look up what `SomeClass` is and emit the right kind of markup, if you want.

Since you *can* look up what kind of object most identifiers like that refer to (statically, even) I think `:py:class:...` is silly.

Why make the person write that if the tool could figure it out itself?

What would you write instead?

Something without "class" in it.

Right, right.

(sorry, I'm still a little new to this)

in our domain for the Dylan language, we have separate roles for various constructs, but we store them all and look them all up in the same mapping ... so it doesn't actually matter which of the roles you use.

Do you think that's a good thing or a bad thing or it doesn't matter?

anyway, I did get it resolved.. :)

now on to more time wasting

!

Any chance there's a better answer to this question? http://stackoverflow.com/questions/11716781/ope...

[02sphinx] 07shimizukawa pushed 032 commits to 03master [+0/-0/±2] 13http://git.io/JqONng

[02sphinx] 07shimizukawa 03a9c1ab9 - Merge branch 'stable' Conflicts: setup.py

[02sphinx] 07shimizukawa pushed 031 commit to 03stable [+0/-0/±1] 13http://git.io/4lV3hw

exarkun: I don't think it has mattered much for us either way.

[02sphinx] 07birkenfeld pushed 034 commits to 03master [+0/-0/±16] 13http://git.io/O3TO3Q

[02sphinx] 07EricFromCanada 03a63e494 - Add highlight_options configuration value This changeset adds the `highlight_options` configuration value, which specifies a dict of key-value pairs to pass to the Pygments highlighter specified with `highlight_language`. For example, specifying `highlight_options = {'funcnamehighlighting' : False}` for the 'php' lexer will disable function name highlighting. Both the HTML and LaTeX writers have been upd

[02sphinx] 07EricFromCanada 033111f7b - rewording of `highlight_options` description

[02sphinx] 07EricFromCanada 030f0ffbb - revised pygments_style description

[02sphinx] ... and 1 more commits.

[02sphinx] 07birkenfeld pushed 031 commit to 03master [+0/-0/±1] 13http://git.io/_8YnBA

[02sphinx] 07birkenfeld 03b9fe829 - highlighting: fix potential TypeError

[02sphinx] 07birkenfeld pushed 031 commit to 03master [+0/-0/±2] 13http://git.io/IG_4NA

[02sphinx] 07lsaffre 0321b8384 - autodoc: use sourcename also for content generated by autodoc itself Fixes #1061 Fixes #1656