Wed, 10 Dec 2008 07:42:05 +0100, Gael Varoquaux wrote:
> On Tue, Dec 09, 2008 at 07:23:41PM +0100, Georg Brandl wrote:
>> I agree. That code wasn't written by me, but by a contributor who liked
>> to have background-color and border-color for code boxes.
>
> Ha, that's me I guess. I was sleeping
On Tue, Dec 09, 2008 at 07:23:41PM +0100, Georg Brandl wrote:
> I agree. That code wasn't written by me, but by a contributor who liked
> to have background-color and border-color for code boxes.
Ha, that's me I guess. I was sleeping throught that conversation;
Can you remind me what the problem
On Dec 9, 1:23 pm, Georg Brandl <[EMAIL PROTECTED]> wrote:
> I agree. That code wasn't written by me, but by a contributor who liked
> to have background-color and border-color for code boxes.
>
> What you can try is to not overwrite Verbatim at all, i.e.
>
> \let\Verbatim=\OriginalVerbatim
> \l
Michael Bayer schrieb:
[...]
> I'm still not understanding LaTex enough to figure out how to make the
> \MakeFramed box a little smaller, but a new way of doing this needs to
> be discovered, since anyone who tries to put a code example under a
> method :param: is going to have this issue.
I ag
So I have looked into it, and the problem will occur with any method-
level docstring that uses a code example underneath a :param:. The
reason it doesn't occur with one of my other docstrings is because
that particular docstring is at the class level.
Code like this that's already nested inside
It's basically the list inside of Verbatim:
\renewcommand{\Verbatim}[1][1]{%
% The list environement is needed to control perfectly the vertical
% space.
\list{}{%
\setlength\parskip{0pt}%
\setlength\itemsep{0ex}%
\setlength\topsep{0ex}%
\setlength\partopsep{0pt}%
\setlength\leftm
Thanks go out to Alex Brasetvik on IRC for narrowing this one way
down. We have PDF output entirely working for the whole SQLA tree.
But only if we don't include this one docstring:
"""Translate url attributes into a dictionary of connection
arguments.
Returns attributes of thi
