On Mon, Sep 28, 2009 at 01:42:05PM +0100, Daniel P. Berrange wrote:
> On Fri, Sep 25, 2009 at 03:58:34PM +0200, Daniel Veillard wrote:
> > On Fri, Sep 25, 2009 at 02:42:47PM +0100, Daniel P. Berrange wrote:
> > > On Fri, Sep 25, 2009 at 03:33:41PM +0200, Daniel Veillard wrote:
> > > > On Fri, Sep 2
On Fri, Sep 25, 2009 at 03:58:34PM +0200, Daniel Veillard wrote:
> On Fri, Sep 25, 2009 at 02:42:47PM +0100, Daniel P. Berrange wrote:
> > On Fri, Sep 25, 2009 at 03:33:41PM +0200, Daniel Veillard wrote:
> > > On Fri, Sep 25, 2009 at 01:28:51PM +0100, Daniel P. Berrange wrote:
> > > I'm still waiti
On Fri, Sep 25, 2009 at 02:42:47PM +0100, Daniel P. Berrange wrote:
> On Fri, Sep 25, 2009 at 03:33:41PM +0200, Daniel Veillard wrote:
> > On Fri, Sep 25, 2009 at 01:28:51PM +0100, Daniel P. Berrange wrote:
> > I'm still waiting to see what this gives in the HTML docs :-)
>
> Hmm, I didn't check t
On Fri, Sep 25, 2009 at 03:33:41PM +0200, Daniel Veillard wrote:
> On Fri, Sep 25, 2009 at 01:28:51PM +0100, Daniel P. Berrange wrote:
> > The python method help docs are copied across from the C
> > funtion comments, but in the process all line breaks and
> > indentation was being lost. This made
On Fri, Sep 25, 2009 at 01:28:51PM +0100, Daniel P. Berrange wrote:
> The python method help docs are copied across from the C
> funtion comments, but in the process all line breaks and
> indentation was being lost. This made the resulting text
> and code examples completely unreadable. Both the AP
The python method help docs are copied across from the C
funtion comments, but in the process all line breaks and
indentation was being lost. This made the resulting text
and code examples completely unreadable. Both the API
doc extractor and the python generator were destroying
whitespace & this f
