On Friday, January 05, 2007, at 02:30PM, "Fredrik Lundh" <[EMAIL PROTECTED]> 
wrote:
>Talin wrote:
>
>> Rather than fixing on a standard markup, I would like to see support for
>> a __markup__ module variable which specifies the specific markup
>> language that is used in that module. Doc processors could inspect that
>> variable and then load the appropriate markup translator.
>
>Ideally, a module should be able to specify what *documentation provider*
>to use.  Not everyone wants to stuff everything into docstrings, and, 
>especially
>if you're building larger components, automatic introspection simply doesn't
>work very well.

+lots on that. This is not only true for larger components but projects like 
wxpython, pyqt and pyobjc could also use these hooks to add links to the C 
version of those libraries (I don't know about pyqt but wxpython and pyobjc 
both have choosen to document the differences with the C library instead of 
trying to duplicate their work).

Ronald
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to