Re: [PyX-user] Error generating manual (\file command) and workaround

[Michael S. <m-s...@us...>]

Salut André,

On 15.10.07, Andre Wobst wrote:
> without detailed investigations either, my observation was that it
> depends on the python version! IIRC the manual can be build with the
> mkhowto from python2.3, which is of course a bit old style.

I tried it with python 2.5: The self-compiled version on a SuSE does
not work, while a debian python 2.5 works. But the following has to be
taken into account:

First, a link to a valid 
  mkhowto
has to be generated. I guess that you refer to the creation of this
link when you say:

> There was a hack (?!) by Michael Schindler, which I
> guess addressed this problem (it can be found in svn), but it broke
> the build for me when I was trying to release 0.10. I just reverted
> the change and it worked for me again.



> > I had a problem while generating the manual. I have docutils and
> > latex2html installed. I followed the instructions in INSTALL about
> > making a link to the mkhowto command and ran make, and got this LaTeX
> > error:
> > 
> > ! Undefined control sequence.
> > \filenq #1->{\py@smallsize \textsf {\let \e
> >                                             =\textbackslash #1}}
> > l.45 ... for the data from file \file{graph.dat}.}

This is an error in manual.cls that comes from the python
documentation class (I would call it a bug in manual.cls). I do not
fully understand why it occurs, but it seems to be the case that a
"let" command does not work if the command is not yet "defined" -- at
least not inside a command or inner vertial mode or horizontal mode or
whatever!

The solution is to define \e before using it: Say
  \def\e{}
somewhere in the header of manual.tex. That cures the problem.

I then encounter a buffer overflow in makeindex (on opensuse 10.3). It
does not occur in Debian Etch.

Michael.