This exception seems to occur if you build the documentation with Python 2 and
Python 3 without cleaning in between.
It is a not a packaging problem and I consider it to be a bug.
--
You received this message because you are subscribed to the Google Groups
sphinx-dev group.
To post to this
A colon has to follow the hash like #: so in order for Sphinx to pick it up as
a doc string for that attribute.
Am 16.03.2012 um 11:11 schrieb Andrea Crotti andrea.crott...@gmail.com:
I tried all the possible options I found but none of them worked yet.
Given something like:
a.py:
#
On Tue, 2010-10-12 at 15:58 +0300, Viktoras wrote:
default resource access could be current file-based, but through some
extension mechanism users could add their own resource types, like your
suggested Git one or my SVN one. This could very well extend into
http-get and similar stuff.
If
There is no way at the moment to use a Wiki as a platform to create
documentation. We are working on a websupport library as part of Sphinx
which will be in the next version along with several other new major
features which have been developed during GSoC (don't hold your breath
just yet.)
It
It works as expected with a recent docutils version.
--
You received this message because you are subscribed to the Google Groups
sphinx-dev group.
To post to this group, send email to sphinx-...@googlegroups.com.
To unsubscribe from this group, send email to
But, what if I *really* wanted to remove that space? Is there some
rule against doing that?
Yeah there is, inline markup can't be used in words like *foo*bar. Try
escaping the opening bracket like :ref:`foo bar`\baz.
However this shouldn't raise an exception like this but that is a
problem with
No, I believe it should, to remain consistent with the aforementioned
case (*foo*bar) and several other examples besides that one (which
docutils, for instance, lumps under the name character-level inline
markup).
Well obviously there should be an exception, however it should be clear
by
Which brings me to the main point of my post. I tried looking at some
of the default domains to figure out how domains worked, but I'm
having trouble understanding it, since there's a lot going on in all
the domains. (The internal workings of docutils have always been
opaque to me.) I think
