Dear Andre,

I am also very curious what's going on. Here is what I get after
commenting out this line (I've also added text.set(errordebug=3) to
hello.py:

Traceback (most recent call last):
  File 
"C:\aaaaa\bbbbbb\cccccccc\ddd\eeeeeee\fffffff\gggggggggggggggggggg\hello.py",
line 4, in <module>
    c.text(0, 0, "Hello, world!")
  File "C:\Python26\lib\site-packages\pyx\canvas.py", line 268, in text
    return self.insert(self.texrunner.text(x, y, atext, *args, **kwargs))
  File "C:\Python26\lib\site-packages\pyx\text.py", line 1205, in text
    self.execute(expr, self.defaulttexmessagesdefaultrun +
self.texmessagesdefaultrun + texmessages)
  File "C:\Python26\lib\site-packages\pyx\text.py", line 935, in execute
    self.defaulttexmessagesstart + self.texmessagesstart)
  File "C:\Python26\lib\site-packages\pyx\text.py", line 1040, in execute
    t.check(self)
  File "C:\Python26\lib\site-packages\pyx\text.py", line 108, in check
    raise TexResultError("TeX running startup file failed", texrunner)
pyx.text.TexResultError: TeX running startup file failed
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXBoxHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \gdef\PyXFlushHAlign{0}%
  \def\PyXragged{%
  \leftskip=0pt plus \PyXFlushHAlign fil%
  \rightskip=0pt plus 1fil%
  \advance\rightskip0pt plus -\PyXFlushHAlign fil%
  \parfillskip=0pt%
  \pretolerance=9999%
  \tolerance=9999%
  \parindent=0pt%
  \hyphenpenalty=9999%
  \exhyphenpenalty=9999}%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newdimen\PyXDimenVShift%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXBoxHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXBoxHAlign{0}%
  
\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlignRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBo
x:}%
  \setbox\PyXBoxHAligned=\hbox{\kern-\PyXDimenHAlignLT\box\PyXBox}%
  \ht\PyXBoxHAligned0pt%
  {\count0=80\count1=121\count2=88\count3=#2\shipout\box\PyXBoxHAligned}}%
  \def\PyXInput#1{\immediate\write16{PyXInputMarker:executeid=#1:}}%
  \def\PyXMarker#1{\hskip0pt\special{PyX:marker #1}}%%
  \PyXInput{1}%
After parsing the return message from TeX, the following was left:
  , Version 3.1415926 (MiKTeX 2.8)

  
(c:\aaaaa\bbbbbb\cccccccc\ddd\eeeeeee\fffffff\gggggggggggggggggggg\tmpr3iamv.te
  x)
  *
  (cut after 5 lines, increase errordebug for more output)

c:\aaaaa\bbbbbb\cccccccc\ddd\eeeeeee\fffffff\gggggggggggggggggggg>hello.py
Traceback (most recent call last):
  File 
"C:\aaaaa\bbbbbb\cccccccc\ddd\eeeeeee\fffffff\gggggggggggggggggggg\hello.py",
line 6, in <module>
    c.text(0, 0, "Hello, world!")
  File "C:\Python26\lib\site-packages\pyx\canvas.py", line 268, in text
    return self.insert(self.texrunner.text(x, y, atext, *args, **kwargs))
  File "C:\Python26\lib\site-packages\pyx\text.py", line 1205, in text
    self.execute(expr, self.defaulttexmessagesdefaultrun +
self.texmessagesdefaultrun + texmessages)
  File "C:\Python26\lib\site-packages\pyx\text.py", line 935, in execute
    self.defaulttexmessagesstart + self.texmessagesstart)
  File "C:\Python26\lib\site-packages\pyx\text.py", line 1040, in execute
    t.check(self)
  File "C:\Python26\lib\site-packages\pyx\text.py", line 108, in check
    raise TexResultError("TeX running startup file failed", texrunner)
pyx.text.TexResultError: TeX running startup file failed
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXBoxHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \gdef\PyXFlushHAlign{0}%
  \def\PyXragged{%
  \leftskip=0pt plus \PyXFlushHAlign fil%
  \rightskip=0pt plus 1fil%
  \advance\rightskip0pt plus -\PyXFlushHAlign fil%
  \parfillskip=0pt%
  \pretolerance=9999%
  \tolerance=9999%
  \parindent=0pt%
  \hyphenpenalty=9999%
  \exhyphenpenalty=9999}%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newdimen\PyXDimenVShift%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXBoxHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXBoxHAlign{0}%
  
\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlignRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBo
x:}%
  \setbox\PyXBoxHAligned=\hbox{\kern-\PyXDimenHAlignLT\box\PyXBox}%
  \ht\PyXBoxHAligned0pt%
  {\count0=80\count1=121\count2=88\count3=#2\shipout\box\PyXBoxHAligned}}%
  \def\PyXInput#1{\immediate\write16{PyXInputMarker:executeid=#1:}}%
  \def\PyXMarker#1{\hskip0pt\special{PyX:marker #1}}%%
  \PyXInput{1}%
The return message from TeX was:
  This is TeX, Version 3.1415926 (MiKTeX 2.8)

  
(c:\aaaaa\bbbbbb\cccccccc\ddd\eeeeeee\fffffff\gggggggggggggggggggg\tmp5xrttd.te
  x)
  *

  *! Undefined control sequence.
  <*> \raiseerror
                 %

  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *PyXInputMarker:executeid=1:
After parsing this message, the following was left:
  , Version 3.1415926 (MiKTeX 2.8)

  
(c:\aaaaa\bbbbbb\cccccccc\ddd\eeeeeee\fffffff\gggggggggggggggggggg\tmp5xrttd.te
  x)
  *

  *! Undefined control sequence.
  <*> \raiseerror
                 %

  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *
  *

On Mon, Dec 14, 2009 at 9:52 AM, André Wobst
<[email protected]> wrote:
> Dear Wojciech,
>
> that's weird. (La)TeX adds linebreaks in its output to not overfill the 
> terminal. This creates various trouble when reading the console output. But I 
> don't see how this problem here is generated. It would be of great value to 
> learn it.
>
> It seems that a TexResultError is generated in the first place, which is 
> caught in line 1206. While clearing up (by line 1207) another problem is 
> found (that no dvi file was created). Unfortunately, by that we don't see 
> error caught in line 1206 anymore. Could you please comment out line 1207 for 
> a try and send the other traceback, which probably includes some information 
> about the original problem. Thanks!
>
>
> André
>
>
> Am 12.12.2009 um 14:56 schrieb Wojciech Jaskowski:
>
>> Hello,
>>
>> Recently I have come across a very weird error. I do not know if its
>> connected with latex or PyX, but I can only produce it using PyX.
>>
>> I use just examples/hello.py. If I run it in the directory:
>>
>> c:\aaaaa\bbbbbb\cccccccc\ddd\eeeeeee\fffffff\ggggggggggggggggggg\
>>
>> everything is ok (this is the real name of my directory - not just an
>> place-holder), but when I try the same in
>>
>> c:\aaaaa\bbbbbb\cccccccc\ddd\eeeeeee\fffffff\gggggggggggggggggggg\
>>
>> (one 'g' more), I get:
>>
>> Traceback (most recent call last):
>>  File 
>> "C:\aaaaa\bbbbbb\cccccccc\ddd\eeeeeee\fffffff\gggggggggggggggggggg\hello.
>> py", line 4, in <module>
>>    c.text(0, 0, "Hello, world!")
>>  File "C:\Python26\lib\site-packages\pyx\canvas.py", line 268, in text
>>    return self.insert(self.texrunner.text(x, y, atext, *args, **kwargs))
>>  File "C:\Python26\lib\site-packages\pyx\text.py", line 1207, in text
>>    self.finishdvi(ignoretail=1)
>>  File "C:\Python26\lib\site-packages\pyx\text.py", line 1056, in finishdvi
>>    self.dvifile = dvifile.DVIfile(dvifilename, debug=self.dvidebug)
>>  File "C:\Python26\lib\site-packages\pyx\dvi\dvifile.py", line 135, in 
>> __init__
>>
>>    self.file = reader.reader(self.filename)
>>  File "C:\Python26\lib\site-packages\pyx\reader.py", line 7, in __init__
>>    self.file = open(filename, "rb")
>> IOError: [Errno 2] No such file or directory: 'tmpvs897p.dvi'
>>
>> It took me a bit to understand that this is connected with the place,
>> when I run the script ;-). I used PyX rev3010, MikTex 2.8, python
>> 2.6.4.8
>>
>> Best regards,
>> Wojciech Jaskowski
>>
>> ------------------------------------------------------------------------------
>> Return on Information:
>> Google Enterprise Search pays you back
>> Get the facts.
>> http://p.sf.net/sfu/google-dev2dev
>> _______________________________________________
>> PyX-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/pyx-user
>
> --
> by  _ _      _    Dr. André Wobst, Amselweg 22, 85716 Unterschleißheim
>   / \ \    / )   [email protected], http://www.wobsta.de/
>  / _ \ \/\/ /    PyX - High quality PostScript and PDF figures
>  (_/ \_)_/\_/     with Python & TeX: visit http://pyx.sourceforge.net/
>
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
>
> _______________________________________________
> PyX-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pyx-user
>
>



-- 
Wojciech Jaskowski
Laboratory of Intelligent Decision Support Systems
Institute of Computing Science
Poznan University of Technology
Piotrowo 2, 60-965 Poznan, Poland
E-mail: [email protected]
www.cs.put.poznan.pl/wjaskowski

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
PyX-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyx-user

Reply via email to