[sphinx-dev] Re: TypeError: unsupported operand type(s) for -: 'str' and 'int'

010/9/7 Fernando Gómez : > Hi, > > Can you give some advice regarding this exception? This is what the > console shows: > > - > Running Sphinx v1.0.3 > loading pickled environment... not yet created > building [html]: targets for 56 source files

[sphinx-dev] TypeError: unsupported operand type(s) for -: 'str' and 'int'

quot;, line 779, in interpreted_or_phrase_ref 'without end-string.', line=lineno) File "/usr/local/lib/python2.6/dist-packages/docutils/utils.py", line 230, in warning return self.system_message(self.WARNING_LEVEL, *args, **kwargs) File "/usr/local/lib/pyt

Re: [sphinx-dev] Re: Adding stuff to doctree in a convenient way

*before* the rst is parsed. -- Fernando Gómez Biblioteca "Antonio Monteiro" INMABB (Conicet / Universidad Nacional del Sur) Av. Alem 1253 B8000CPB Bahía Blanca, Argentina Tel. +54 (291) 459 5116 http://inmabb.criba.edu.ar/ -- You received this message because you are subscribed to the

Re: [sphinx-dev] Adding stuff to doctree in a convenient way

le before the rst markup is parsed is an adequate solution, then the "source-read" event may be what you need: http://sphinx.pocoo.org/ext/appapi.html#event-source-read -- Fernando Gómez Biblioteca "Antonio Monteiro" INMABB (Conicet / Universidad Nacional del Sur) Av. Al

[sphinx-dev] Re: Handling css for a reusable extension

By the way, it's reasonable to assume that this style sheet would eventually have more than one version, each associated with a different Sphinx theme. 2010/3/2 Fernando Gómez : > Hi, > > I'm developing a Sphinx extension which won't be tied to any > particular project

[sphinx-dev] Handling css for a reusable extension

that it is findable by all such projects, i.e. somewhere in sys.path. I'd like to know what's the recommended approach to solve the same issue for the .css file. Thanks in advance. [1] http://sphinx.pocoo.org/extensions.html -- Fernando Gómez Biblioteca "Antonio Monteiro"

[sphinx-dev] Suggestion: absolute paths vs relative paths

ion be included in both places, as well as in any other directive where the same concept is applicable. Regards, Fernando [1] http://sphinx.pocoo.org/rest.html#images [2] http://sphinx.pocoo.org/concepts.html#the-toc-tree -- Fernando Gómez Biblioteca "Antonio Monteiro" INMABB

Re: [sphinx-dev] Literate programming with noweb and sphinx -- Single vs multiple files

ult looks promising. I'll keep posting on this subject, and probably ask for some help too :-) BTW, I've already solved the file splitting issue, in a way that is satisfactory at least in the context of my project. Regards, Fernando -- Fernando Gómez Biblioteca "Antonio Monteiro&q

Re: [sphinx-dev] Simple Extension Help

nd Django uses a couple of those. Regards, Fernando -- Fernando Gómez Biblioteca "Antonio Monteiro" INMABB (Conicet / Universidad Nacional del Sur) Av. Alem 1253 B8000CPB Bahía Blanca, Argentina Tel. +54 (291) 459 5116 http://inmabb.criba.edu.ar/ -- You received this message becau

[sphinx-dev] parsed-literal conflicts with code highlighting

a way to make Pygments see the clean, unescaped code so that its parser is not bothered by the escape sequences. Of course, even without the "unintended markup" issue, the code blocks that do contain :ref: links still would be a problem for the highlighter... Any hints? Your help w

[sphinx-dev] Literate programming with noweb and sphinx -- Single vs multiple files

Hi, This is the "how to split a single reST document into multiple files" issue again, within a particular context which might be of interest for someone else. :-) I'm using literate programming [1] for my current project, which is a web app written in Python. I chose noweb [2] as the tool for t