[sphinx-dev] Autodoc munging \n in function signatures

2010-03-20 Thread Jeff Forcier
Hi, and thanks for Sphinx! It's great. I've encountered what seems like an odd problem with the autodoc plugin: a function signature with \n in a default value has the '\' stripped away, and thus any generated autodocs appear to claim that the string instead just reads n. This happens regardless

[sphinx-dev] Location of sphinx-quickstart etc scripts?

2010-03-20 Thread Nick Edwards
Hi, Sphinx looks really cool and I'm keen to try it out! I'm having some problems getting it working though... I'm on a multiuser system to which I don't have root / sudo access so cannot use easy install. I can quite happily install python packages in my user area though. I installed sphinx by

[sphinx-dev] :class: followed by :ref: corrupts text

2010-03-20 Thread Michael Bayer
With 0.6.5 (and 0.6.2, others) I'm seeing lines like this: All about how to define :class:`~sqlalchemy.schema.Table` objects, as well as how to create them from an existing database automatically, is described in :ref:`metadata_toplevel`. become collapsed in the output, producing this: All

[sphinx-dev] Re: :class: followed by :ref: corrupts text

2010-03-20 Thread Michael Bayer
the workaround is to put :ref: on a newline: All about how to define :class:`~sqlalchemy.schema.Table` objects, as well as how to create them from an existing database automatically, is described in :ref:`metadata_toplevel`. so the issue is not as screamingly urgent. and yes we're looking

[sphinx-dev] Re: :class: followed by :ref: corrupts text - **nevermind**

2010-03-20 Thread Michael Bayer
nevermind, it's a regexp in our build that's been wrong for a long time and only revealed this issue after people help annotate tons of docs for us. On Mar 20, 1:28 pm, Michael Bayer zzz...@gmail.com wrote: the workaround is to put :ref: on a newline: All about how to define