[Python-Dev] Re: interlocking dependencies on the path to a release

["Martin v. Löwis"]

Phillip J. Eby wrote:
>> How do you create a module index and a "global" index in reST?
> 
> 
> By adding directives, or using interpreted text, as long as the feature 
> is supported by a given output writer.

Ah, so you would make use of extensions; i.e. we would essentially
clone reST.

>> How do you express document inclusion (in the spirit of \input)?
> 
> 
> There's an "include" directive.  I don't know what you mean by the 
> "spirit of \input".

If include means literal inclusion, it is in the spirit of \input.

> The difference is merely that the meaning of reST's equivalents to 
> macros and environments (i.e. "interpreted text roles" and "directives") 
> are defined using Python code rather than Latex.  Of course, a latex 
> writer could still be used to generate latex output, if that is the 
> preferred format for printing.

I did not understand that, in order to use reST in a complex
application, you have to write your own markup extensions, and
then support those in all the backends you care about.

If that is typical, then yes, reST should be able to represent
everything we have in the documentation right now. It just means
that we cannot expect reST to work *out-of-the-box*. Instead, we
first need to implement the missing formatting elements for the
backends we care for. That sounds like a significant project of
its own.

Regards,
Martin