pyx-devel — PyX development

Re: [PyX-devel] Re: Some comments on PyX

[Joerg L. <jo...@us...>]

Hi Michael,

On 16.10.03, Michael Schindler wrote:
> I threw a coin, and it said "Number" -- what now?

Throw again!

> Is there a possibility for the following?
>    "import pyx"        --> access via "pyx.canvas.canvas()", everything
>                            is loaded automatically
>    "from pyx import *" --> say "canvas.canvas()" instead

That's exactly the behaviour that Fernando was requesting, 
so I suppose we are now 3:1 in favour of this solution, if
I'm correct.

        Jörg

-- 
JOERG LEHMANN  | PyX - High quality PostScript figures with Python & TeX
jo...@lu...  | Visit http://pyx.sourceforge.net/

Re: [PyX-devel] Re: Some comments on PyX

[Michael S. <mic...@ph...>]

Hi Jörg and André,

> On 16.10.03, Joerg Lehmann wrote:
> > I'm not sure about that. Of course, at the moment an "import pyx"
> > doesn't do anything (expect providing access to pyx.__version__ and
> > pyx.__all__) and using the code given above it would at least do
> > something reasonable. On the other hand, the behaviour seems to
> > be rather implicit than explicit to me. So, as I said, I don't know.
>
> Well, same for me. Should we play dice now?

I threw a coin, and it said "Number" -- what now?

Some statements about the above:
1. Usually one does not want to say
     pyx.canvas.canvas() instead of canvas.canvas(),
   which is long enough.

2. There might be some conflicts with other module names, and in this
   case it is more work to import the necessary modules one by one
   without these conflicts.

3. Loading everything by default is not a good idea, as can be seen in the
   scipy-project which is too slow for usage.

Is there a possibility for the following?
   "import pyx"        --> access via "pyx.canvas.canvas()", everything
                           is loaded automatically
   "from pyx import *" --> say "canvas.canvas()" instead

Best Greetings,
  Michael

-- 
"A mathematician is a device for turning coffee into theorems"
  Paul Erdös.

Re: [PyX-devel] start from home-directory

[Joerg L. <jo...@us...>]

Hi Arnd,

On 16.10.03, Arnd Baecker wrote:
> > > [ptpl14] ~ $ python hello.py
> > > tmp5f9pw-
> >
> > What's this?
> 
> This seems to be the temporary file-name, created by PyX, I suppose.
> I still see this after correcting my screwed setup.
> 
> Hmm, I haven't seen this with PyX-0.4, as far as I remember
> (the above is with todays CVS).

It was a bogus debugging output which somehow slipped into
CVS... I have removed it now.

        Jörg

-- 
JOERG LEHMANN  | PyX - High quality PostScript figures with Python & TeX
jo...@lu...  | Visit http://pyx.sourceforge.net/

Re: [PyX-devel] start from home-directory

[Arnd B. <arn...@we...>]

Hi Andre,

thanks for the quick response.
The crucial question which helped me was:

> I'm not sure, but it seems to be that TeX is not able to
> start at all. And this looks like some temporary file name. (You can
> say "tex" in both directories, don't you?

I can, but it takes much longer in my home-directory:
time latex t.tex:
  Subdirectory:   0.06s user 0.01s system 140% cpu 0.050 total
  Homedirectory:  7.89s user 1.96s system 69% cpu 14.136 total
And the origin of this was me setting
  TEXINPUTS=:.//:${TEXINPUTS}
I.e. all subdirectories are searched recursively
(which is fine in many situations, but this is not so
good  when starting from the home-directory)
Because of this we hit the <=5s border and pyx fails.
To confirm this I added a
  text.set(waitfortex=30)
and it works fine (though slow ;-).

To summarize: even on a single platform
one can get easily beyong the 5s limit
with a wierd set-up ;-)

So many thanks for your help!!

> > [ptpl14] ~ $ python hello.py
> > tmp5f9pw-
>
> What's this?

This seems to be the temporary file-name, created by PyX, I suppose.
I still see this after correcting my screwed setup.

Hmm, I haven't seen this with PyX-0.4, as far as I remember
(the above is with todays CVS).

Many thanks,

Arnd

Re: [PyX-devel] Re: Some comments on PyX

[Andre W. <wo...@us...>]

Jörg,

On 16.10.03, Joerg Lehmann wrote:
> I'm not sure about that. Of course, at the moment an "import pyx"
> doesn't do anything (expect providing access to pyx.__version__ and
> pyx.__all__) and using the code given above it would at least do
> something reasonable. On the other hand, the behaviour seems to
> be rather implicit than explicit to me. So, as I said, I don't know.

Well, same for me. Should we play dice now?

> > 2) I have to address the share/data_files search path issue.
> 
> Maybe also something for a pyxrc?

That's actually a good idea. By that we could even get rid of the
developer search path (this third path possibility explained in my
previous mail). I kind of like the idea. In principle we might be even
able to use libkpathsea ... it's probably possible to feed it with
some additional path search types we read from our configuration and
use that. But on the other hand we already do have some working code
except that we should feed it with some input from pyxrc. And
libkpathsea is not neccessarily linked as a module.

BTW: Have you ever done a /etc/<xxx>rc and ~/.<xxx>rc file before
(e.g. in pytone)? How about the distribution of that via distutils?


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us...
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/

Re: [PyX-devel] Re: Some comments on PyX

[Joerg L. <jo...@us...>]

Hi André, Fernando, and *,

On 16.10.03, Andre Wobst wrote:
> On 15.10.03, Fernando Perez wrote:
> > 'import pyx' doesn't provide access to pyx's modules.  The examples provided
> > all use 'from pyx import *', which is bad form for larger scripts, where this
> > kind of blanket import is bound to cause nasty name collisions.
> > 
> > FIX: trivial.  In __init__.py, add after __all__ is defined:
> > 
> > # Load __all__ in pyx namespace so that a simple 'import pyx' gives
> > # access to them via pyx.<name>
> > for name in __all__:
> >     __import__(name,globals(),locals(),[])
> 
> Right now you can do the following:
> 
>     wobsta@mbo:~$ python
>     Python 2.3.2 (#1, Oct  6 2003, 16:59:47)
>     [GCC 2.95.4 20011002 (Debian prerelease)] on linux2
>     Type "help", "copyright", "credits" or "license" for more information.
>     >>> import pyx
>     >>> import pyx.canvas
>     >>> c = pyx.canvas.canvas()
>     >>> c.text(0, 0, "Hello, world!")
>     <pyx.text._textbox instance at 0x4030f86c>
>     >>> c.writetofile("hello")
> 
> Yes, you have to do the second import statement. But is that really a
> crucial point? I'm interested in Jörgs response to that as well.

I'm not sure about that. Of course, at the moment an "import pyx"
doesn't do anything (expect providing access to pyx.__version__ and
pyx.__all__) and using the code given above it would at least do
something reasonable. On the other hand, the behaviour seems to
be rather implicit than explicit to me. So, as I said, I don't know.

> I quickly want to summarize my impression (also in order to tell Jörg
> about my point of what we should do):
> 
> 1) We need some runtime configuration possibility (like a pyxrc). We
> had discussed it in terms of the mapping files before already. There
> are two further use-cases: the timeout configuration (suggested above)
> and the TeX --ipc option (I've done some tests working nicely, but now
> I have to work in the direction of a pagewise dvi-reading inside PyX).

Ok.

> 2) I have to address the share/data_files search path issue.

Maybe also something for a pyxrc?

Greetings,

        Jörg

-- 
JOERG LEHMANN  | PyX - High quality PostScript figures with Python & TeX
jo...@lu...  | Visit http://pyx.sourceforge.net/

Re: [PyX-devel] start from home-directory

[Andre W. <wo...@us...>]

Hi Arnd,

On 16.10.03, Arnd Baecker wrote:
> If I execute `python hello.py`
> in my home-directory, I get
>   pyx.text.TexResultError: TeX didn't respond as expected within the
>   timeout period (5 seconds).
> (see below for the full log)
> However, in a subdirectory everything works fine.
> Can someone confirm this behavior ?
> (If not then I will have to check if I screwed up my
> setup at some place ...)

It's hopefully not the case ;-)

> [ptpl14] ~ $ python hello.py
> tmp5f9pw-

What's this? Just in case, it might have something to do with the
problem. I'm not sure, but it seems to be that TeX is not able to
start at all. And this looks like some temporary file name. (You can
say "tex" in both directories, don't you? And you are allowed to write
files in both directories!?)

> Traceback (most recent call last):
>   File "hello.py", line 4, in ?
>     c.text(0, 0, "Hello, world!")
>   File "/python/PYTHON/lib/python2.3/site-packages/pyx/canvas.py",
> line 773, in text
>     return self.insert(self.texrunner.text(x, y, atext, *args))
>   File "/python/PYTHON/lib/python2.3/site-packages/pyx/text.py", line
> 2318, in text
>     return self._text(unit.topt(x), unit.topt(y), expr, *args)
>   File "/python/PYTHON/lib/python2.3/site-packages/pyx/text.py", line
> 2306, in _text
>     self.execute(expr, *helper.getattrs(args, texmessage,
> default=self.texmessagedefaultrun))
>   File "/python/PYTHON/lib/python2.3/site-packages/pyx/text.py", line
> 1969, in execute
>     self.execute("\\scrollmode\n\\raiseerror%\n" # switch to and check
> scrollmode
>   File "/python/PYTHON/lib/python2.3/site-packages/pyx/text.py", line
> 2103, in execute
>     raise TexResultError("TeX didn't respond as expected within the
> timeout period (%i seconds)." % self.waitfortex, self)
> pyx.text.TexResultError: TeX didn't respond as expected within the timeout
> period (5 seconds).
> The expression passed to TeX was:
>   \scrollmode
>   \raiseerror%
>   \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
>   \gdef\PyXHAlign{0}%
>   \newbox\PyXBox%
>   \newbox\PyXBoxHAligned%
>   \newdimen\PyXDimenHAlignLT%
>   \newdimen\PyXDimenHAlignRT%
>   \newbox\PyXBoxVAlign%
>   \newdimen\PyXDimenVAlign%
>   \newbox\PyXBoxVBox%
>   \newdimen\PyXDimenVBox%
>   \long\def\ProcessPyXBox#1#2{%
>   \setbox\PyXBox=\hbox{{#1}}%
>   \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%
>   \PyXDimenHAlignRT=\wd\PyXBox%
>   \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
>   \gdef\PyXHAlign{0}%
> 
> \immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlignRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%
>   \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:}}%
>   \PyXInput{1}%
> After parsing the return message from TeX, the following was left:
>   This is TeX, Version 3.14159 (Web2C 7.4.5)

I've not yet understand, what's going wrong. It might help to get a
more verbose information. Could you first check yourself, that you're
importing the same version of PyX in both cases (start python with the
-v flag and compare the path information of the imported modules). If
they are the same could you insert the following line immediately
after importing pyx in your python script:

        text.set(waitfortex=15, errordebug=2, texdebug="spamneggs")

Run it in both directories and send me both spamneggs.tex files (of
both directories) and the error message you get. It might help in
finding out what's going wrong ...


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us...
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/

[PyX-devel] start from home-directory

[Arnd B. <arn...@we...>]

Hi,

when devising a small example for Fernando last night
I encountered the following strange behavior:

If I execute `python hello.py`
in my home-directory, I get
  pyx.text.TexResultError: TeX didn't respond as expected within the
  timeout period (5 seconds).
(see below for the full log)
However, in a subdirectory everything works fine.
Can someone confirm this behavior ?
(If not then I will have to check if I screwed up my
setup at some place ...)

BTW: thanks for this great tool (which is just getting
some attention among scipy-folks ;-).

Arnd


[ptpl14] ~ $ python hello.py
tmp5f9pw-
Traceback (most recent call last):
  File "hello.py", line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/python/PYTHON/lib/python2.3/site-packages/pyx/canvas.py",
line 773, in text
    return self.insert(self.texrunner.text(x, y, atext, *args))
  File "/python/PYTHON/lib/python2.3/site-packages/pyx/text.py", line
2318, in text
    return self._text(unit.topt(x), unit.topt(y), expr, *args)
  File "/python/PYTHON/lib/python2.3/site-packages/pyx/text.py", line
2306, in _text
    self.execute(expr, *helper.getattrs(args, texmessage,
default=self.texmessagedefaultrun))
  File "/python/PYTHON/lib/python2.3/site-packages/pyx/text.py", line
1969, in execute
    self.execute("\\scrollmode\n\\raiseerror%\n" # switch to and check
scrollmode
  File "/python/PYTHON/lib/python2.3/site-packages/pyx/text.py", line
2103, in execute
    raise TexResultError("TeX didn't respond as expected within the
timeout period (%i seconds)." % self.waitfortex, self)
pyx.text.TexResultError: TeX didn't respond as expected within the timeout
period (5 seconds).
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXHAlign{0}%

\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlignRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%
  \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:}}%
  \PyXInput{1}%
After parsing the return message from TeX, the following was left:
  This is TeX, Version 3.14159 (Web2C 7.4.5)

[PyX-devel] Re: Some comments on PyX

[Andre W. <wo...@us...>]

Fernando,

thanks for your detailed report. There are important issues we surely
want to address. Let me briefly give you some comments right now on
some issues, which are easy to solve.

On 15.10.03, Fernando Perez wrote:
> 'import pyx' doesn't provide access to pyx's modules.  The examples provided
> all use 'from pyx import *', which is bad form for larger scripts, where this
> kind of blanket import is bound to cause nasty name collisions.
> 
> FIX: trivial.  In __init__.py, add after __all__ is defined:
> 
> # Load __all__ in pyx namespace so that a simple 'import pyx' gives
> # access to them via pyx.<name>
> for name in __all__:
>     __import__(name,globals(),locals(),[])

Right now you can do the following:

    wobsta@mbo:~$ python
    Python 2.3.2 (#1, Oct  6 2003, 16:59:47)
    [GCC 2.95.4 20011002 (Debian prerelease)] on linux2
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import pyx
    >>> import pyx.canvas
    >>> c = pyx.canvas.canvas()
    >>> c.text(0, 0, "Hello, world!")
    <pyx.text._textbox instance at 0x4030f86c>
    >>> c.writetofile("hello")

Yes, you have to do the second import statement. But is that really a
crucial point? I'm interested in Jörgs response to that as well.

> - PROBLEM: setup.py doesn't put things in the proper place if --home is given
> different from the default.  I used --home=~/usr/local, and while pyx itself
> went into ~/usr/local/lib/python/pyx, its .lfs files went to
> ~/usr/local/share/pyx.  But the pyx program itself expects to find them
> somewhere else, because trying to run hello.py produces:
> 
> planck[examples]> python hello.py
> Traceback (most recent call last):
>   File "hello.py", line 4, in ?
>     c.text(0, 0, "Hello, world!")
>   File "/home/fperez/usr/local/lib/python/pyx/canvas.py", line 767, in text
>     return self.insert(self.texrunner.text(x, y, atext, *args))
>   File "/home/fperez/usr/local/lib/python/pyx/text.py", line 2283, in text
>     return self._text(unit.topt(x), unit.topt(y), expr, *args)
>   File "/home/fperez/usr/local/lib/python/pyx/text.py", line 2271, in _text
>     self.execute(expr, *helper.getattrs(args, texmessage, default=self.texmessagedefaultrun))
>   File "/home/fperez/usr/local/lib/python/pyx/text.py", line 1994, in execute
>     raise IOError("file '%s' not found. Available latex font sizes: %s" % (lfsname, lfsnames))
> IOError: file '10pt.lfs' not found. Available latex font sizes: []
> 
> This may be a bug in setup.py, or in pyx itself (pyx may need to adjust its
> search paths according to where it got installed).  I don't know for sure.
> 
> Putting some print statements in text.py gave the following:
> 
> *** file 10pt.lfs not found!
> *** file /usr/share/pyx/10pt.lfs not found!
> *** file /home/fperez/usr/local/lib/python/pyx/lfs/10pt.lfs not found!
> 
> So the problem is in how pyx builds its search path (lines 1980-93 in
> text.py).  It needs to pick up the correct installation path, or setup.py
> needs to make sure that the lfs files end up underneath the pyx directory
> (instead of above it, in ../../share).
> 
> FIX: For now I can fix it manually, by moving the .lfs files to a directory
> (which must be created first) called
> /home/fperez/usr/local/lib/python/pyx/lfs.  But this needs to be done
> permanently in the code.  I'm not exactly sure what the correct fix is.

This hole subject is very important to be improved. I may tell you,
why it is the way it is right now: The first search path is just the
local directory in case you're placing own lfs-files there. The second
path is pythons share directory. Since these lfs-files are installed
as data_files by setup.py they automatically come into this share
directory. PyX now asks python for its default share directory ... yes
and this goes wrong when installing PyX to another place. I'll try to
find out how to fix this. It should be a common problem using
data_files and distutils. (Unfortunately those things are kind of
difficult to learn out of the distutils documentation).

However, the third search path is for inplace compilation and usage
(thus basically for development). It uses the path where the modules
are located which is fine, but it seems not to be the correct place to
install data_files to that possition. Thus it is not intended to be
used in a properly installed PyX package.

BTW, for the second search path: We could do a path search like in the
third case and walk towards "../../share" in order to reach the share
directory. But what if you tell the setup.py to install the data_files
at some other place? (I'm not sure if you're allowed to do so.) I have
to really address this correctly since we now know that it is broken.

> PROBLEM
> -------
> 
> After fixing the previous one manually, I still can't run hello.py.
> Note that I've also seen this error on a machine where pyx was 'setup.py
> install'ed to a default directory.
> 
> Here's the traceback:
> 
> planck[examples]> python hello.py
> Traceback (most recent call last):
>   File "hello.py", line 6, in ?
>     c.writetofile("hello")
> 
> ... [snip]
> 
> RuntimeError: no information for font 'cmr10' found in font mapping file, aborting
> 
> This problem is discussed in:
> 
> http://sourceforge.net/mailarchive/forum.php?thread_id=3225190&forum_id=23700
> 
> FIX: change around line 504 of text.py, from:
> 
> fontmap = readfontmap(["psfonts.map"])
> 
> to:
> 
> fontmap = readfontmap(["psfonts.map","psfonts.cmz","psfonts.amz"])
> 
> It might be worth doing this in the mainline sources.  Even if it is not the
> ideal default for some latex-related reasons I don't understand, the truth is
> that distributions as popular as RedHat choke on the current configuration.
> If this simple change makes pyx work out of the box for many users, it is that
> much more likely to become popular.

Its likely that we will have some /etc/pyxrc and ~/.pyxrc for that in
the future (like you can have a .dvipsrc telling dvips to do the same
as PyX regarding the fonts; its the 'p' option in the dvipsrc or the
'u' at the command line). We should provide an example for that file
telling people to possibly include that map files when they are
running a TeX installation not using type1 fonts by default.

> PROBLEM
> -------
> 
> Trying to run the latex.py example:
> 
> planck[examples]> python latex.py
> Traceback (most recent call last):
>    File "latex.py", line 9, in ?
>      c.text(0, 0, r"This is \LaTeX.")
> 
> .... [snip]
> 
> pyx.text.TexResultError: TeX didn't respond as expected within the timeout 
> period (5 seconds).
> The expression passed to TeX was:
>    \documentclass{article}%
>    \PyXInput{3}%
> After parsing the return message from TeX, the following was left:
>    *
> 
> 
> The problem is that on a system where ~ is NFS mounted, a 5 second timeout may 
> be just too short.  We serve /home from an old Solaris box, and latex'ing a 
> file typically is a bit of a slow process with lots of network read/write 
> activity.  I wouldn't be surprised if this was a rather common situation in 
> typical unix shops.
> 
> FIX: I'd advocate for a much longer timeout, perhaps 30 seconds at least.  I
> changed it to 30 (line 1848 of text.py), and it works fine even on our
> sluggish network.  While this timeout is a bit long, it makes pyx a much more
> robust system in the face of 'real world' network environments.

I do not want to make it very long, because people might have to wait
for that timeout if TeX is broken badly (however, once your setup is
fine its not likely that you step into that problem). People are
probably not waiting that long if their script seem to hang. We might
make that an option in the .pyxrc as well ... so that you can adjust
it to your specific needs. You're right that you might want to
increase this value to make PyX more reliable.

BTW: You can always do so by "text.set(waitfortex=30)" for the default
texrunner and in the same way at the constructor when creating own
texrunner instances.

> PROBLEM
> -------
> 
> After fixing the above, I can run most of the included examples.  The only
> remaining issues are:
> 
> - The pattern.eps file looks very different from the one on the website.  The
> global figure is indeed the PyX logo, but instead of being made out of little
> copies of PyX, it's made out of text blocks.  This may or may not be an issue
> with my system, I don't know.

It's likely that you're just observing a problem of ghostscript here.
Try to turn off the anti-aliasing feature of ghostscript (it helps in
quite some cases where ghostscript behaves badly). In ghostview press
"a" for that. You may also send this file to a PostScript 2 aware
printer (IIRC these pattern things are PostScript Level 2 features).

> I've put up what I get (temporarily) in
> http://windom.colorado.edu/~fperez/tmp/pattern.eps
> in case the developers find it useful.

Yes, it works for me with disabled antialiasing in ghostscript.

> - bar.py and minimal.py don't run because the corresponding .dat files are not
> included in the distribution.

I've got this report yesterday from Andrea Riciputi as well and
already fixed the distribution configuration in CVS in that respect.

I quickly want to summarize my impression (also in order to tell Jörg
about my point of what we should do):

1) We need some runtime configuration possibility (like a pyxrc). We
had discussed it in terms of the mapping files before already. There
are two further use-cases: the timeout configuration (suggested above)
and the TeX --ipc option (I've done some tests working nicely, but now
I have to work in the direction of a pagewise dvi-reading inside PyX).

2) I have to address the share/data_files search path issue.

Thanks for all your intensive work in testing our package. You
hopefully will like it so it was worse your effort. You're welcome to
further join the discussion.


André


PS: I'm crossposting this to pyx-devel in order to let other
developers be able to join your discussion.

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us...
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/

Re: [PyX-devel] possible bug installing PyX on Mac OS X

[Andre W. <wo...@us...>]

Eric,

I'm sorry. I've just seen, that this feature of turning on and off
some extention modules by editing setup.cfg is a feature not included
in PyX-0.4.1. (There is not setup.cfg distributed with PyX at all.)
However, everything else said is true, so you just can turn off the
building of the libkpathsea extention module by editing setup.py.
Instead of

ext_modules = [Extension("pyx.t1strip._t1strip",
                         sources=["pyx/t1strip/t1strip.c", "pyx/t1strip/writet1.c"]),
               Extension("pyx.pykpathsea._pykpathsea",
                         sources=["pyx/pykpathsea/pykpathsea.c"],
                         libraries=["kpathsea"])]

you should use:

ext_modules = [Extension("pyx.t1strip._t1strip",
                         sources=["pyx/t1strip/t1strip.c", "pyx/t1strip/writet1.c"])]

I apologize for the confusion.


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us...
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/

Re: [PyX-devel] possible bug installing PyX on Mac OS X

[Andre W. <wo...@us...>]

Eric,

On 15.10.03, Eric Daniel Fraenkel wrote:
> 	i got the following bug when installing PyX on Mac OS X (10.2.6) for 
> Python 2.2. it seems that i miss two include files progname.h and 
> tex-file.h. they should probably be in my 
> /usr/local/teTeX/include/kpathsea directory but they are not. i hope 
> this is usefull.

This means, that your TeX-distribution is not complete (at least in
terms of development). It all depends on the TeX installation you're
using. There might be some install option of your TeX-distribution
where you can enable the installation of development files like these
header files.

Since libkpathsea is specific to the TeX installation (it has a
hard-coded path to texmf.cnf inside), you should not try to just get
libkpathsea compiled and running independend from your TeX
installation. TeX itself will need it as well and you should stick to
that libkpathsea your TeX is compiled to.

But you may run PyX without a linked version of libkpathsea since
there is a tool called kpsewhich for TeX path searchs to be performed
on the command line. You may try to run:
    kpsewhich psfonts.map
    kpsewhich cmr10.pfb
If you get the full paths of those files back you should be able to
run PyX without a linked libkpathsea. Try "build_pykpathsea=0" in
setup.cfg to disable the linked version of libkpathsea. The path
lookups will be a bit slower than (the execution of kpsewhich is
performed for each lookup), but it should still be quite useable.

André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us...
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/

[PyX-devel] possible bug installing PyX on Mac OS X

[Eric D. F. <e.d...@st...>]

hello,

	i got the following bug when installing PyX on Mac OS X (10.2.6) for 
Python 2.2. it seems that i miss two include files progname.h and 
tex-file.h. they should probably be in my 
/usr/local/teTeX/include/kpathsea directory but they are not. i hope 
this is usefull.

Daniel Fraenkel

~/Desktop/PyX-0.4.1 > python setup.py install
running install
running build
running build_py
not copying pyx/__init__.py (output up-to-date)
not copying pyx/attrlist.py (output up-to-date)
not copying pyx/base.py (output up-to-date)
not copying pyx/bbox.py (output up-to-date)
not copying pyx/box.py (output up-to-date)
not copying pyx/canvas.py (output up-to-date)
not copying pyx/color.py (output up-to-date)
not copying pyx/connector.py (output up-to-date)
not copying pyx/data.py (output up-to-date)
not copying pyx/epsfile.py (output up-to-date)
not copying pyx/graph.py (output up-to-date)
not copying pyx/helper.py (output up-to-date)
not copying pyx/mathtree.py (output up-to-date)
not copying pyx/path.py (output up-to-date)
not copying pyx/prolog.py (output up-to-date)
not copying pyx/tex.py (output up-to-date)
not copying pyx/text.py (output up-to-date)
not copying pyx/timeaxis.py (output up-to-date)
not copying pyx/trafo.py (output up-to-date)
not copying pyx/unit.py (output up-to-date)
not copying pyx/version.py (output up-to-date)
not copying pyx/t1strip/__init__.py (output up-to-date)
not copying pyx/pykpathsea/__init__.py (output up-to-date)
running build_ext
skipping 'pyx.t1strip._t1strip' extension (up-to-date)
building 'pyx.pykpathsea._pykpathsea' extension
gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -no-cpp-precomp 
-I/usr/include/python2.2 -c pyx/pykpathsea/pykpathsea.c -o 
build/temp.darwin-6.6-Power Macintosh-2.2/pykpathsea.o
pyx/pykpathsea/pykpathsea.c:20:31: kpathsea/tex-file.h: No such file or 
directory
pyx/pykpathsea/pykpathsea.c:21:31: kpathsea/progname.h: No such file or 
directory
pyx/pykpathsea/pykpathsea.c: In function `py_kpse_find_file':
pyx/pykpathsea/pykpathsea.c:31: warning: implicit declaration of 
function `kpse_find_file'
pyx/pykpathsea/pykpathsea.c:31: `kpse_file_format_type' undeclared 
(first use in this function)
pyx/pykpathsea/pykpathsea.c:31: (Each undeclared identifier is reported 
only once
pyx/pykpathsea/pykpathsea.c:31: for each function it appears in.)
pyx/pykpathsea/pykpathsea.c:31: parse error before "kpse_file_format"
pyx/pykpathsea/pykpathsea.c: In function `init_pykpathsea':
pyx/pykpathsea/pykpathsea.c:55: warning: implicit declaration of 
function `kpse_set_program_name'
pyx/pykpathsea/pykpathsea.c:57: `kpse_gf_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:58: `kpse_pk_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:59: `kpse_any_glyph_format' undeclared 
(first use in this function)
pyx/pykpathsea/pykpathsea.c:60: `kpse_tfm_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:61: `kpse_afm_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:62: `kpse_base_format' undeclared (first 
use in this function)
pyx/pykpathsea/pykpathsea.c:63: `kpse_bib_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:64: `kpse_bst_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:65: `kpse_cnf_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:66: `kpse_db_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:67: `kpse_fmt_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:68: `kpse_fontmap_format' undeclared (first 
use in this function)
pyx/pykpathsea/pykpathsea.c:69: `kpse_mem_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:70: `kpse_mf_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:71: `kpse_mfpool_format' undeclared (first 
use in this function)
pyx/pykpathsea/pykpathsea.c:72: `kpse_mft_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:73: `kpse_mp_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:74: `kpse_mppool_format' undeclared (first 
use in this function)
pyx/pykpathsea/pykpathsea.c:75: `kpse_mpsupport_format' undeclared 
(first use in this function)
pyx/pykpathsea/pykpathsea.c:76: `kpse_ocp_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:77: `kpse_ofm_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:78: `kpse_opl_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:79: `kpse_otp_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:80: `kpse_ovf_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:81: `kpse_ovp_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:82: `kpse_pict_format' undeclared (first 
use in this function)
pyx/pykpathsea/pykpathsea.c:83: `kpse_tex_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:84: `kpse_texdoc_format' undeclared (first 
use in this function)
pyx/pykpathsea/pykpathsea.c:85: `kpse_texpool_format' undeclared (first 
use in this function)
pyx/pykpathsea/pykpathsea.c:86: `kpse_texsource_format' undeclared 
(first use in this function)
pyx/pykpathsea/pykpathsea.c:87: `kpse_tex_ps_header_format' undeclared 
(first use in this function)
pyx/pykpathsea/pykpathsea.c:88: `kpse_troff_font_format' undeclared 
(first use in this function)
pyx/pykpathsea/pykpathsea.c:89: `kpse_type1_format' undeclared (first 
use in this function)
pyx/pykpathsea/pykpathsea.c:90: `kpse_vf_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:91: `kpse_dvips_config_format' undeclared 
(first use in this function)
pyx/pykpathsea/pykpathsea.c:92: `kpse_ist_format' undeclared (first use 
in this function)
pyx/pykpathsea/pykpathsea.c:93: `kpse_truetype_format' undeclared 
(first use in this function)
pyx/pykpathsea/pykpathsea.c:94: `kpse_type42_format' undeclared (first 
use in this function)
pyx/pykpathsea/pykpathsea.c:95: `kpse_web2c_format' undeclared (first 
use in this function)
pyx/pykpathsea/pykpathsea.c:96: `kpse_program_text_format' undeclared 
(first use in this function)
pyx/pykpathsea/pykpathsea.c:97: `kpse_program_binary_format' undeclared 
(first use in this function)
pyx/pykpathsea/pykpathsea.c:98: `kpse_miscfonts_format' undeclared 
(first use in this function)
error: command 'gcc' failed with exit status 1
~/Desktop/PyX-0.4.1 > 

[PyX-devel] [ pyx-Bugs-817717 ] TeX error with PyX-0.4.1

[SourceForge.net <no...@so...>]

Bugs item #817717, was opened at 2003-10-04 16:17
Message generated for change (Comment added) made by wobsta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: TeX error with PyX-0.4.1

Initial Comment:
I run Python 2.1.3, TeX (Web2C 7.3.7) 3.14159 and
kpathsea version 3.3.7 under Debian GNU/Linux 3.0.

If i run any of the examples which output some text I get 
the following error message:sieck@acertm:~$ python
/usr/lib/python2.1/site-packages/PyX/examples/hello.py 
Traceback (most recent call last):
  File
"/usr/lib/python2.1/site-packages/PyX/examples/hello.py",
line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/home/sieck/packages/PyX-0.4.1/pyx/canvas.py",
line 767, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2283, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2271, in _text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 1950, in execute
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2070, in execute
pyx.text.TexResultError: TeX didn't respond as expected
within the timeout period 
(5 seconds).
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXHAlign{0}%
 
\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlig
nRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%
 
\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:}}%
  \PyXInput{1}%
After parsing the return message from TeX, the
following was left:
  This is TeX, Version 3.14159 (Web2C 7.3.7)
  ! I can't find file `@473.0'.
  <*> @473.0
            
  Please type another input file name: ! I can't find
file `\scrollmode'.
  (cut after 5 lines, increase errordebug for more output)

# end of output

Any ideas?

Alexander Sieck

alexander dot sieck at web dot de


# start of output




----------------------------------------------------------------------

>Comment By: André Wobst (wobsta)
Date: 2003-10-14 07:44

Message:
Logged In: YES 
user_id=405853

Jörg, yes, you're totally right. I mixed it up with the
encoding of the standard TeX fonts as they are included in
recent versions of teTeX (there might still be cases where
the encoding modification becomes important, but it seems to
be not the case in common usage as teTeX didn't had the
reencoding for a long time as well). Thus, Alexander, you
are fine with your updated psfonts.map created by updmap. I
think we're done. Closing.
Andre

----------------------------------------------------------------------

Comment By: Jörg Lehmann (joergl)
Date: 2003-10-13 21:47

Message:
Logged In: YES 
user_id=390410

André, wasn't that the bug in our usage of writet1.c, where we 
haven't reset the value of the global fontencoding variable
before
using the routine for the standard encoded fonts?

----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-13 08:19

Message:
Logged In: YES 
user_id=405853

Fine that its working now. Concerning the encoding files: We
had some problems with some fonts a few weeks ago (shortly
before releasing PyX 0.4). A signature of this problem was
the missing integral glyph in the integral graph example.
However I could produce this example without a font
reencoding now. I'm kind of confused (I've tried to
reproduce our old problem, but I coudn't). Jörg, do you
remember what the problem was and wasn't it solved by some
reencoding?

Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-10 20:18

Message:
Logged In: NO 

Hello,

as described in the header of
  /usr/share/texmf/dvips/config/psfonts.map
the file psfonts.map is created by the script
  /usr/share/texmf/dvips/config/updmap
Changing
  type1_default=false
  #type1_default=true
to
  # type1_default=false
  type1_default=true
in this script and running it added the missing lines like
  cmr10 CMR10 <cmr10.pfb
to psfonts.map .

Now all PyX examples work.
The meaning of the encoding files *.enc
you mentioned and what you mean by
"you should better extract the enclosing font information"
is not clear to me yet.
  
Thanks for your quick response.

Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-09 08:06

Message:
Logged In: YES 
user_id=405853

I see. Point is, that the package installs the fonts but
does not automatically include them in the file psfonts.map
(used by dvips for example). This file contains some
information about the available PostScript-Fonts. When you
request cmr10 for example, there should be such an entry in
the psfonts.map file. (Run "kpsewhich psfonts.map" to find
this mapping file; it should be located at
/usr/share/texmf/dvips/config/psfonts.map.) Although there
are mapping files for the Computer Modern Roman fonts
available in your debian distribution (stable, isn't it),
they do not contain proper encoding information. Instead of
using those information from
/usr/share/texmf/dvips/bluesky/psfonts.cmr, you should
better extract the enclosing font information. You should be
able to run test.py in the test directory after extraction.
You can then install this psfonts.map and *.enc files in the
appropriate texmf directory to make it globally available.
You can either install it into something like
/usr/local/share/texmf/dvips/psfonts or in your home
directory ~/texmf/dvips/psfonts. See "kpsewhich texmf.cnf"
about your TeX related search path configuration.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-08 22:19

Message:
Logged In: NO 

Hello,

it still doesn't work. I have installed tetex-extra:
sieck@acertm:~/packages/PyX-0.4.1/examples$ find
/usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf
sieck@acertm:~/packages/PyX-0.4.1/examples$ ls
/usr/share/texmf/fonts/type1/
adobe  bitstrea  bluesky  hoekwater  public  urw

But for all examples with text-output, e.g. hello.py,
I still get the error:

RuntimeError: no information for font 'cmr10' found in font
mapping file

When I did run make in /PyX-0.4.1/manual/ the first time,
there was a message about some files that couldn't be
created, a request to rerun it and finally the same error
as above.
After the rerun it finished without this error message
and manual.dvi was created.

Are there any environment variables I have to set or does
one need to initialize the Type1 fonts?
I rebooted after installing tetex-extra, to initialize tetex or
kpathsea, but this didn't help.
In the docu I only found a hint to mktexls-r, but this is only
to speed kpathsea up, right?

Regards
               Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-08 08:48

Message:
Logged In: YES 
user_id=405853

It's nice to see that you could get distutils working. You
are totally right about the python-dev package you need to
install for that.

It's quite likely that you are missing just one last point
now: You need the TeX-Fonts in Type1 format (a scalable font
format from Adobe available in a direct PostScript version
(called *.pfa) and a packed version of it (called *.pfb) --
the later are usually distributed and PyX needs it). This is
nice to have for tex&dvips as well, since you are not stick
to the metafont pk-version of the fonts anymore (which has
some advantages, e.g. in pdf creation and other things). The
type1-Fonts are available in the debian package tetex-extra.
Just install this package to get the files like cmr10.pfb
... then try again.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-07 23:35

Message:
Logged In: NO 

Hello,

since I couldn't find the distutils for Python2.1 
"python setup.py install" failed with
"No module distutils.core". Therefore, I extracted
PyX-0.4.1.tar directly to ../lib/python2.1/site-packages.
With this I could produce the example box.eps, but the
examples with text-output produced the message given
above.
In the meantime I learned that since Python1.6 the
distutils module is in python2.x-dev and installed
it. Then I run "python setup.py install" and removed
the PyX directory in site-packages. This solved the
problem mentioned above.

Unfortunately, now something is wrong with the TeX fonts:
=== start of output ===
sieck@acertm:~/packages/PyX-0.4.1/examples$ python hello.py
Traceback (most recent call last):
  File "hello.py", line 6, in ?
    c.writetofile("hello")
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 936, in writetofile
    for pritem in self.prolog():
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 661, in prolog
    result.extend(cmd.prolog())
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1780, in prolog
    return result + self.texrunner.prolog(self.dvinumber,
self.page)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2086, in prolog
    self.getdvi()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2080, in getdvi
    self.dvifiles.append(DVIFile(dvifilename,
debug=self.dvidebug))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
685, in __init__
    self.readfile()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1087, in readfile
    state = self._read_page()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1045, in _read_page
    file.read(file.readuchar()+file.readuchar()))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
773, in definefont
    self.fonts[num] =  Font(fontname, c, q, d, self.tfmconv,
self.debug > 1)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
516, in __init__
    raise RuntimeError("no information for font '%s' found
in font mapping file, aborting" % name)
  RuntimeError: no information for font 'cmr10' found in
font mapping file, aborting
=== end of output ===

"libkpathsea-dev - kpathsea.a and include files for teTeX"
is installed.
The environment variables in /etc/texmf/texmf.cnf seem to be
in agreement
with the documentation.
A file cmr10.tfm does exist:
sieck@acertm:~$ find /usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf

I can use LaTeX separately without problems, e.g. article.cls
and german.sty and the fonts are found.

I am not sure whether the problem is caused by my environment
or by PyX.

Regards 
             Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-06 17:46

Message:
Logged In: YES 
user_id=405853

I could not yet reproduce your problem. It would be really
nice if you could do some tests in order to better trace
down the problem.

First of all, I'm wondering that you've installed the
examples systemwide (this would not be the case when you run
"python setup.py install" in the pyx directory --- which is
the suggested way to install pyx). The PyX directory in
/usr/lib/pythonx.x/site-packages should not contain
uppercase characters. You can already see some strange
behavior that pyx in taken not from
/usr/lib/pythonx.x/site-packages/pyx but from somewhere in
your home directory. I expect this to be due to your way of
installing pyx. Could you first of all try to fix this and
the tell me, if the problem remains ...

By the way, I should note that pyx indeed tries to create a
temporary file handed over to TeX. This file has a temporary
name and is removed after TeX should have read it. The file
is created in the local directory (all these things are
build in order to come over some TeX limitations). However,
since the creation of the file should have been done at that
point your problem occures (otherwise you should have got
some exception earlier), you might be able to see that file
(you might need to turn off the atexit call to cleen the
temporary files in text.py). On the other hand, TeX said in
the example above, that it could not read that very file.
Still, very strange ...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

[PyX-devel] [ pyx-Bugs-817717 ] TeX error with PyX-0.4.1

[SourceForge.net <no...@so...>]

Bugs item #817717, was opened at 2003-10-04 16:17
Message generated for change (Comment added) made by joergl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: TeX error with PyX-0.4.1

Initial Comment:
I run Python 2.1.3, TeX (Web2C 7.3.7) 3.14159 and
kpathsea version 3.3.7 under Debian GNU/Linux 3.0.

If i run any of the examples which output some text I get 
the following error message:sieck@acertm:~$ python
/usr/lib/python2.1/site-packages/PyX/examples/hello.py 
Traceback (most recent call last):
  File
"/usr/lib/python2.1/site-packages/PyX/examples/hello.py",
line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/home/sieck/packages/PyX-0.4.1/pyx/canvas.py",
line 767, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2283, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2271, in _text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 1950, in execute
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2070, in execute
pyx.text.TexResultError: TeX didn't respond as expected
within the timeout period 
(5 seconds).
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXHAlign{0}%
 
\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlig
nRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%
 
\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:}}%
  \PyXInput{1}%
After parsing the return message from TeX, the
following was left:
  This is TeX, Version 3.14159 (Web2C 7.3.7)
  ! I can't find file `@473.0'.
  <*> @473.0
            
  Please type another input file name: ! I can't find
file `\scrollmode'.
  (cut after 5 lines, increase errordebug for more output)

# end of output

Any ideas?

Alexander Sieck

alexander dot sieck at web dot de


# start of output




----------------------------------------------------------------------

>Comment By: Jörg Lehmann (joergl)
Date: 2003-10-13 21:47

Message:
Logged In: YES 
user_id=390410

André, wasn't that the bug in our usage of writet1.c, where we 
haven't reset the value of the global fontencoding variable
before
using the routine for the standard encoded fonts?

----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-13 08:19

Message:
Logged In: YES 
user_id=405853

Fine that its working now. Concerning the encoding files: We
had some problems with some fonts a few weeks ago (shortly
before releasing PyX 0.4). A signature of this problem was
the missing integral glyph in the integral graph example.
However I could produce this example without a font
reencoding now. I'm kind of confused (I've tried to
reproduce our old problem, but I coudn't). Jörg, do you
remember what the problem was and wasn't it solved by some
reencoding?

Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-10 20:18

Message:
Logged In: NO 

Hello,

as described in the header of
  /usr/share/texmf/dvips/config/psfonts.map
the file psfonts.map is created by the script
  /usr/share/texmf/dvips/config/updmap
Changing
  type1_default=false
  #type1_default=true
to
  # type1_default=false
  type1_default=true
in this script and running it added the missing lines like
  cmr10 CMR10 <cmr10.pfb
to psfonts.map .

Now all PyX examples work.
The meaning of the encoding files *.enc
you mentioned and what you mean by
"you should better extract the enclosing font information"
is not clear to me yet.
  
Thanks for your quick response.

Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-09 08:06

Message:
Logged In: YES 
user_id=405853

I see. Point is, that the package installs the fonts but
does not automatically include them in the file psfonts.map
(used by dvips for example). This file contains some
information about the available PostScript-Fonts. When you
request cmr10 for example, there should be such an entry in
the psfonts.map file. (Run "kpsewhich psfonts.map" to find
this mapping file; it should be located at
/usr/share/texmf/dvips/config/psfonts.map.) Although there
are mapping files for the Computer Modern Roman fonts
available in your debian distribution (stable, isn't it),
they do not contain proper encoding information. Instead of
using those information from
/usr/share/texmf/dvips/bluesky/psfonts.cmr, you should
better extract the enclosing font information. You should be
able to run test.py in the test directory after extraction.
You can then install this psfonts.map and *.enc files in the
appropriate texmf directory to make it globally available.
You can either install it into something like
/usr/local/share/texmf/dvips/psfonts or in your home
directory ~/texmf/dvips/psfonts. See "kpsewhich texmf.cnf"
about your TeX related search path configuration.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-08 22:19

Message:
Logged In: NO 

Hello,

it still doesn't work. I have installed tetex-extra:
sieck@acertm:~/packages/PyX-0.4.1/examples$ find
/usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf
sieck@acertm:~/packages/PyX-0.4.1/examples$ ls
/usr/share/texmf/fonts/type1/
adobe  bitstrea  bluesky  hoekwater  public  urw

But for all examples with text-output, e.g. hello.py,
I still get the error:

RuntimeError: no information for font 'cmr10' found in font
mapping file

When I did run make in /PyX-0.4.1/manual/ the first time,
there was a message about some files that couldn't be
created, a request to rerun it and finally the same error
as above.
After the rerun it finished without this error message
and manual.dvi was created.

Are there any environment variables I have to set or does
one need to initialize the Type1 fonts?
I rebooted after installing tetex-extra, to initialize tetex or
kpathsea, but this didn't help.
In the docu I only found a hint to mktexls-r, but this is only
to speed kpathsea up, right?

Regards
               Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-08 08:48

Message:
Logged In: YES 
user_id=405853

It's nice to see that you could get distutils working. You
are totally right about the python-dev package you need to
install for that.

It's quite likely that you are missing just one last point
now: You need the TeX-Fonts in Type1 format (a scalable font
format from Adobe available in a direct PostScript version
(called *.pfa) and a packed version of it (called *.pfb) --
the later are usually distributed and PyX needs it). This is
nice to have for tex&dvips as well, since you are not stick
to the metafont pk-version of the fonts anymore (which has
some advantages, e.g. in pdf creation and other things). The
type1-Fonts are available in the debian package tetex-extra.
Just install this package to get the files like cmr10.pfb
... then try again.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-07 23:35

Message:
Logged In: NO 

Hello,

since I couldn't find the distutils for Python2.1 
"python setup.py install" failed with
"No module distutils.core". Therefore, I extracted
PyX-0.4.1.tar directly to ../lib/python2.1/site-packages.
With this I could produce the example box.eps, but the
examples with text-output produced the message given
above.
In the meantime I learned that since Python1.6 the
distutils module is in python2.x-dev and installed
it. Then I run "python setup.py install" and removed
the PyX directory in site-packages. This solved the
problem mentioned above.

Unfortunately, now something is wrong with the TeX fonts:
=== start of output ===
sieck@acertm:~/packages/PyX-0.4.1/examples$ python hello.py
Traceback (most recent call last):
  File "hello.py", line 6, in ?
    c.writetofile("hello")
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 936, in writetofile
    for pritem in self.prolog():
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 661, in prolog
    result.extend(cmd.prolog())
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1780, in prolog
    return result + self.texrunner.prolog(self.dvinumber,
self.page)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2086, in prolog
    self.getdvi()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2080, in getdvi
    self.dvifiles.append(DVIFile(dvifilename,
debug=self.dvidebug))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
685, in __init__
    self.readfile()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1087, in readfile
    state = self._read_page()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1045, in _read_page
    file.read(file.readuchar()+file.readuchar()))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
773, in definefont
    self.fonts[num] =  Font(fontname, c, q, d, self.tfmconv,
self.debug > 1)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
516, in __init__
    raise RuntimeError("no information for font '%s' found
in font mapping file, aborting" % name)
  RuntimeError: no information for font 'cmr10' found in
font mapping file, aborting
=== end of output ===

"libkpathsea-dev - kpathsea.a and include files for teTeX"
is installed.
The environment variables in /etc/texmf/texmf.cnf seem to be
in agreement
with the documentation.
A file cmr10.tfm does exist:
sieck@acertm:~$ find /usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf

I can use LaTeX separately without problems, e.g. article.cls
and german.sty and the fonts are found.

I am not sure whether the problem is caused by my environment
or by PyX.

Regards 
             Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-06 17:46

Message:
Logged In: YES 
user_id=405853

I could not yet reproduce your problem. It would be really
nice if you could do some tests in order to better trace
down the problem.

First of all, I'm wondering that you've installed the
examples systemwide (this would not be the case when you run
"python setup.py install" in the pyx directory --- which is
the suggested way to install pyx). The PyX directory in
/usr/lib/pythonx.x/site-packages should not contain
uppercase characters. You can already see some strange
behavior that pyx in taken not from
/usr/lib/pythonx.x/site-packages/pyx but from somewhere in
your home directory. I expect this to be due to your way of
installing pyx. Could you first of all try to fix this and
the tell me, if the problem remains ...

By the way, I should note that pyx indeed tries to create a
temporary file handed over to TeX. This file has a temporary
name and is removed after TeX should have read it. The file
is created in the local directory (all these things are
build in order to come over some TeX limitations). However,
since the creation of the file should have been done at that
point your problem occures (otherwise you should have got
some exception earlier), you might be able to see that file
(you might need to turn off the atexit call to cleen the
temporary files in text.py). On the other hand, TeX said in
the example above, that it could not read that very file.
Still, very strange ...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

[PyX-devel] [ pyx-Bugs-779129 ] SyntaxError on Linux: PyX-0.3.1.tar.gz

[SourceForge.net <no...@so...>]

Bugs item #779129, was opened at 2003-07-28 22:05
Message generated for change (Settings changed) made by wobsta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=779129&group_id=45430

Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: SyntaxError on Linux: PyX-0.3.1.tar.gz

Initial Comment:
I was trying to install the latest version of PyX in
Linux (Red Hat) using the Python 2.2.3.   Here is the
message I got:

python setup.py build_ext -i
  File "setup.py", line 66
    **addargs)
     ^
SyntaxError: invalid syntax



----------------------------------------------------------------------

Comment By: Jörg Lehmann (joergl)
Date: 2003-07-29 09:53

Message:
Logged In: YES 
user_id=390410

I would suggest running the setup.py script via

python2.2 setup.py build_ext -i 

HTH,
     Jörg

----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-07-29 08:46

Message:
Logged In: YES 
user_id=405853

Just to get sure: could you please run "python -V" in your
environment to get sure that you do not pick some old flavor
of python by accident. (The keyword argument syntax the
interpreter complains about was introduced in python 2.0.
For newer versions of python this message just doesn't make
any sense to me right now.)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=779129&group_id=45430

[PyX-devel] [ pyx-Bugs-817717 ] TeX error with PyX-0.4.1

[SourceForge.net <no...@so...>]

Bugs item #817717, was opened at 2003-10-04 16:17
Message generated for change (Comment added) made by wobsta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: TeX error with PyX-0.4.1

Initial Comment:
I run Python 2.1.3, TeX (Web2C 7.3.7) 3.14159 and
kpathsea version 3.3.7 under Debian GNU/Linux 3.0.

If i run any of the examples which output some text I get 
the following error message:sieck@acertm:~$ python
/usr/lib/python2.1/site-packages/PyX/examples/hello.py 
Traceback (most recent call last):
  File
"/usr/lib/python2.1/site-packages/PyX/examples/hello.py",
line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/home/sieck/packages/PyX-0.4.1/pyx/canvas.py",
line 767, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2283, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2271, in _text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 1950, in execute
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2070, in execute
pyx.text.TexResultError: TeX didn't respond as expected
within the timeout period 
(5 seconds).
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXHAlign{0}%
 
\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlig
nRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%
 
\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:}}%
  \PyXInput{1}%
After parsing the return message from TeX, the
following was left:
  This is TeX, Version 3.14159 (Web2C 7.3.7)
  ! I can't find file `@473.0'.
  <*> @473.0
            
  Please type another input file name: ! I can't find
file `\scrollmode'.
  (cut after 5 lines, increase errordebug for more output)

# end of output

Any ideas?

Alexander Sieck

alexander dot sieck at web dot de


# start of output




----------------------------------------------------------------------

>Comment By: André Wobst (wobsta)
Date: 2003-10-13 08:19

Message:
Logged In: YES 
user_id=405853

Fine that its working now. Concerning the encoding files: We
had some problems with some fonts a few weeks ago (shortly
before releasing PyX 0.4). A signature of this problem was
the missing integral glyph in the integral graph example.
However I could produce this example without a font
reencoding now. I'm kind of confused (I've tried to
reproduce our old problem, but I coudn't). Jörg, do you
remember what the problem was and wasn't it solved by some
reencoding?

Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-10 20:18

Message:
Logged In: NO 

Hello,

as described in the header of
  /usr/share/texmf/dvips/config/psfonts.map
the file psfonts.map is created by the script
  /usr/share/texmf/dvips/config/updmap
Changing
  type1_default=false
  #type1_default=true
to
  # type1_default=false
  type1_default=true
in this script and running it added the missing lines like
  cmr10 CMR10 <cmr10.pfb
to psfonts.map .

Now all PyX examples work.
The meaning of the encoding files *.enc
you mentioned and what you mean by
"you should better extract the enclosing font information"
is not clear to me yet.
  
Thanks for your quick response.

Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-09 08:06

Message:
Logged In: YES 
user_id=405853

I see. Point is, that the package installs the fonts but
does not automatically include them in the file psfonts.map
(used by dvips for example). This file contains some
information about the available PostScript-Fonts. When you
request cmr10 for example, there should be such an entry in
the psfonts.map file. (Run "kpsewhich psfonts.map" to find
this mapping file; it should be located at
/usr/share/texmf/dvips/config/psfonts.map.) Although there
are mapping files for the Computer Modern Roman fonts
available in your debian distribution (stable, isn't it),
they do not contain proper encoding information. Instead of
using those information from
/usr/share/texmf/dvips/bluesky/psfonts.cmr, you should
better extract the enclosing font information. You should be
able to run test.py in the test directory after extraction.
You can then install this psfonts.map and *.enc files in the
appropriate texmf directory to make it globally available.
You can either install it into something like
/usr/local/share/texmf/dvips/psfonts or in your home
directory ~/texmf/dvips/psfonts. See "kpsewhich texmf.cnf"
about your TeX related search path configuration.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-08 22:19

Message:
Logged In: NO 

Hello,

it still doesn't work. I have installed tetex-extra:
sieck@acertm:~/packages/PyX-0.4.1/examples$ find
/usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf
sieck@acertm:~/packages/PyX-0.4.1/examples$ ls
/usr/share/texmf/fonts/type1/
adobe  bitstrea  bluesky  hoekwater  public  urw

But for all examples with text-output, e.g. hello.py,
I still get the error:

RuntimeError: no information for font 'cmr10' found in font
mapping file

When I did run make in /PyX-0.4.1/manual/ the first time,
there was a message about some files that couldn't be
created, a request to rerun it and finally the same error
as above.
After the rerun it finished without this error message
and manual.dvi was created.

Are there any environment variables I have to set or does
one need to initialize the Type1 fonts?
I rebooted after installing tetex-extra, to initialize tetex or
kpathsea, but this didn't help.
In the docu I only found a hint to mktexls-r, but this is only
to speed kpathsea up, right?

Regards
               Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-08 08:48

Message:
Logged In: YES 
user_id=405853

It's nice to see that you could get distutils working. You
are totally right about the python-dev package you need to
install for that.

It's quite likely that you are missing just one last point
now: You need the TeX-Fonts in Type1 format (a scalable font
format from Adobe available in a direct PostScript version
(called *.pfa) and a packed version of it (called *.pfb) --
the later are usually distributed and PyX needs it). This is
nice to have for tex&dvips as well, since you are not stick
to the metafont pk-version of the fonts anymore (which has
some advantages, e.g. in pdf creation and other things). The
type1-Fonts are available in the debian package tetex-extra.
Just install this package to get the files like cmr10.pfb
... then try again.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-07 23:35

Message:
Logged In: NO 

Hello,

since I couldn't find the distutils for Python2.1 
"python setup.py install" failed with
"No module distutils.core". Therefore, I extracted
PyX-0.4.1.tar directly to ../lib/python2.1/site-packages.
With this I could produce the example box.eps, but the
examples with text-output produced the message given
above.
In the meantime I learned that since Python1.6 the
distutils module is in python2.x-dev and installed
it. Then I run "python setup.py install" and removed
the PyX directory in site-packages. This solved the
problem mentioned above.

Unfortunately, now something is wrong with the TeX fonts:
=== start of output ===
sieck@acertm:~/packages/PyX-0.4.1/examples$ python hello.py
Traceback (most recent call last):
  File "hello.py", line 6, in ?
    c.writetofile("hello")
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 936, in writetofile
    for pritem in self.prolog():
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 661, in prolog
    result.extend(cmd.prolog())
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1780, in prolog
    return result + self.texrunner.prolog(self.dvinumber,
self.page)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2086, in prolog
    self.getdvi()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2080, in getdvi
    self.dvifiles.append(DVIFile(dvifilename,
debug=self.dvidebug))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
685, in __init__
    self.readfile()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1087, in readfile
    state = self._read_page()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1045, in _read_page
    file.read(file.readuchar()+file.readuchar()))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
773, in definefont
    self.fonts[num] =  Font(fontname, c, q, d, self.tfmconv,
self.debug > 1)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
516, in __init__
    raise RuntimeError("no information for font '%s' found
in font mapping file, aborting" % name)
  RuntimeError: no information for font 'cmr10' found in
font mapping file, aborting
=== end of output ===

"libkpathsea-dev - kpathsea.a and include files for teTeX"
is installed.
The environment variables in /etc/texmf/texmf.cnf seem to be
in agreement
with the documentation.
A file cmr10.tfm does exist:
sieck@acertm:~$ find /usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf

I can use LaTeX separately without problems, e.g. article.cls
and german.sty and the fonts are found.

I am not sure whether the problem is caused by my environment
or by PyX.

Regards 
             Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-06 17:46

Message:
Logged In: YES 
user_id=405853

I could not yet reproduce your problem. It would be really
nice if you could do some tests in order to better trace
down the problem.

First of all, I'm wondering that you've installed the
examples systemwide (this would not be the case when you run
"python setup.py install" in the pyx directory --- which is
the suggested way to install pyx). The PyX directory in
/usr/lib/pythonx.x/site-packages should not contain
uppercase characters. You can already see some strange
behavior that pyx in taken not from
/usr/lib/pythonx.x/site-packages/pyx but from somewhere in
your home directory. I expect this to be due to your way of
installing pyx. Could you first of all try to fix this and
the tell me, if the problem remains ...

By the way, I should note that pyx indeed tries to create a
temporary file handed over to TeX. This file has a temporary
name and is removed after TeX should have read it. The file
is created in the local directory (all these things are
build in order to come over some TeX limitations). However,
since the creation of the file should have been done at that
point your problem occures (otherwise you should have got
some exception earlier), you might be able to see that file
(you might need to turn off the atexit call to cleen the
temporary files in text.py). On the other hand, TeX said in
the example above, that it could not read that very file.
Still, very strange ...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

[PyX-devel] [ pyx-Bugs-821284 ] problem in key with title=None

[SourceForge.net <no...@so...>]

Bugs item #821284, was opened at 2003-10-10 17:29
Message generated for change (Comment added) made by wobsta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=821284&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Gert Ingold (gertingold)
Assigned to: Nobody/Anonymous (nobody)
Summary: problem in key with title=None

Initial Comment:
The task was to plot data and to produce a key for only
some of the data files. Omitting the title for these
data files obviously does not help as key entries with
label (unknown) are produced. However, one would expect
title=None to work. Unfortunately, this results in a
TeX error (see attached file fss.err). Shouldn't this
be implemented in such a way that title=None simply
ignores the corresponding data set while generating the
key?

----------------------------------------------------------------------

>Comment By: André Wobst (wobsta)
Date: 2003-10-13 07:31

Message:
Logged In: YES 
user_id=405853

You are right. It's just missing in the implementation right
now. But I already added this missing feature to the TODO
list in the CHANGELOG quite some time ago. In the meantime
you may use the graphs addkey method to manually add a key
providing a list of plotinfo instances. By that you can
select the plotinfo instances you want to add to the key by
yourself.

Andre

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=821284&group_id=45430

[PyX-devel] [ pyx-Bugs-817717 ] TeX error with PyX-0.4.1

[SourceForge.net <no...@so...>]

Bugs item #817717, was opened at 2003-10-04 07:17
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: TeX error with PyX-0.4.1

Initial Comment:
I run Python 2.1.3, TeX (Web2C 7.3.7) 3.14159 and
kpathsea version 3.3.7 under Debian GNU/Linux 3.0.

If i run any of the examples which output some text I get 
the following error message:sieck@acertm:~$ python
/usr/lib/python2.1/site-packages/PyX/examples/hello.py 
Traceback (most recent call last):
  File
"/usr/lib/python2.1/site-packages/PyX/examples/hello.py",
line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/home/sieck/packages/PyX-0.4.1/pyx/canvas.py",
line 767, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2283, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2271, in _text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 1950, in execute
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2070, in execute
pyx.text.TexResultError: TeX didn't respond as expected
within the timeout period 
(5 seconds).
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXHAlign{0}%
 
\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlig
nRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%
 
\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:}}%
  \PyXInput{1}%
After parsing the return message from TeX, the
following was left:
  This is TeX, Version 3.14159 (Web2C 7.3.7)
  ! I can't find file `@473.0'.
  <*> @473.0
            
  Please type another input file name: ! I can't find
file `\scrollmode'.
  (cut after 5 lines, increase errordebug for more output)

# end of output

Any ideas?

Alexander Sieck

alexander dot sieck at web dot de


# start of output




----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-10 11:18

Message:
Logged In: NO 

Hello,

as described in the header of
  /usr/share/texmf/dvips/config/psfonts.map
the file psfonts.map is created by the script
  /usr/share/texmf/dvips/config/updmap
Changing
  type1_default=false
  #type1_default=true
to
  # type1_default=false
  type1_default=true
in this script and running it added the missing lines like
  cmr10 CMR10 <cmr10.pfb
to psfonts.map .

Now all PyX examples work.
The meaning of the encoding files *.enc
you mentioned and what you mean by
"you should better extract the enclosing font information"
is not clear to me yet.
  
Thanks for your quick response.

Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-08 23:06

Message:
Logged In: YES 
user_id=405853

I see. Point is, that the package installs the fonts but
does not automatically include them in the file psfonts.map
(used by dvips for example). This file contains some
information about the available PostScript-Fonts. When you
request cmr10 for example, there should be such an entry in
the psfonts.map file. (Run "kpsewhich psfonts.map" to find
this mapping file; it should be located at
/usr/share/texmf/dvips/config/psfonts.map.) Although there
are mapping files for the Computer Modern Roman fonts
available in your debian distribution (stable, isn't it),
they do not contain proper encoding information. Instead of
using those information from
/usr/share/texmf/dvips/bluesky/psfonts.cmr, you should
better extract the enclosing font information. You should be
able to run test.py in the test directory after extraction.
You can then install this psfonts.map and *.enc files in the
appropriate texmf directory to make it globally available.
You can either install it into something like
/usr/local/share/texmf/dvips/psfonts or in your home
directory ~/texmf/dvips/psfonts. See "kpsewhich texmf.cnf"
about your TeX related search path configuration.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-08 13:19

Message:
Logged In: NO 

Hello,

it still doesn't work. I have installed tetex-extra:
sieck@acertm:~/packages/PyX-0.4.1/examples$ find
/usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf
sieck@acertm:~/packages/PyX-0.4.1/examples$ ls
/usr/share/texmf/fonts/type1/
adobe  bitstrea  bluesky  hoekwater  public  urw

But for all examples with text-output, e.g. hello.py,
I still get the error:

RuntimeError: no information for font 'cmr10' found in font
mapping file

When I did run make in /PyX-0.4.1/manual/ the first time,
there was a message about some files that couldn't be
created, a request to rerun it and finally the same error
as above.
After the rerun it finished without this error message
and manual.dvi was created.

Are there any environment variables I have to set or does
one need to initialize the Type1 fonts?
I rebooted after installing tetex-extra, to initialize tetex or
kpathsea, but this didn't help.
In the docu I only found a hint to mktexls-r, but this is only
to speed kpathsea up, right?

Regards
               Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-07 23:48

Message:
Logged In: YES 
user_id=405853

It's nice to see that you could get distutils working. You
are totally right about the python-dev package you need to
install for that.

It's quite likely that you are missing just one last point
now: You need the TeX-Fonts in Type1 format (a scalable font
format from Adobe available in a direct PostScript version
(called *.pfa) and a packed version of it (called *.pfb) --
the later are usually distributed and PyX needs it). This is
nice to have for tex&dvips as well, since you are not stick
to the metafont pk-version of the fonts anymore (which has
some advantages, e.g. in pdf creation and other things). The
type1-Fonts are available in the debian package tetex-extra.
Just install this package to get the files like cmr10.pfb
... then try again.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-07 14:35

Message:
Logged In: NO 

Hello,

since I couldn't find the distutils for Python2.1 
"python setup.py install" failed with
"No module distutils.core". Therefore, I extracted
PyX-0.4.1.tar directly to ../lib/python2.1/site-packages.
With this I could produce the example box.eps, but the
examples with text-output produced the message given
above.
In the meantime I learned that since Python1.6 the
distutils module is in python2.x-dev and installed
it. Then I run "python setup.py install" and removed
the PyX directory in site-packages. This solved the
problem mentioned above.

Unfortunately, now something is wrong with the TeX fonts:
=== start of output ===
sieck@acertm:~/packages/PyX-0.4.1/examples$ python hello.py
Traceback (most recent call last):
  File "hello.py", line 6, in ?
    c.writetofile("hello")
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 936, in writetofile
    for pritem in self.prolog():
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 661, in prolog
    result.extend(cmd.prolog())
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1780, in prolog
    return result + self.texrunner.prolog(self.dvinumber,
self.page)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2086, in prolog
    self.getdvi()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2080, in getdvi
    self.dvifiles.append(DVIFile(dvifilename,
debug=self.dvidebug))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
685, in __init__
    self.readfile()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1087, in readfile
    state = self._read_page()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1045, in _read_page
    file.read(file.readuchar()+file.readuchar()))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
773, in definefont
    self.fonts[num] =  Font(fontname, c, q, d, self.tfmconv,
self.debug > 1)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
516, in __init__
    raise RuntimeError("no information for font '%s' found
in font mapping file, aborting" % name)
  RuntimeError: no information for font 'cmr10' found in
font mapping file, aborting
=== end of output ===

"libkpathsea-dev - kpathsea.a and include files for teTeX"
is installed.
The environment variables in /etc/texmf/texmf.cnf seem to be
in agreement
with the documentation.
A file cmr10.tfm does exist:
sieck@acertm:~$ find /usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf

I can use LaTeX separately without problems, e.g. article.cls
and german.sty and the fonts are found.

I am not sure whether the problem is caused by my environment
or by PyX.

Regards 
             Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-06 08:46

Message:
Logged In: YES 
user_id=405853

I could not yet reproduce your problem. It would be really
nice if you could do some tests in order to better trace
down the problem.

First of all, I'm wondering that you've installed the
examples systemwide (this would not be the case when you run
"python setup.py install" in the pyx directory --- which is
the suggested way to install pyx). The PyX directory in
/usr/lib/pythonx.x/site-packages should not contain
uppercase characters. You can already see some strange
behavior that pyx in taken not from
/usr/lib/pythonx.x/site-packages/pyx but from somewhere in
your home directory. I expect this to be due to your way of
installing pyx. Could you first of all try to fix this and
the tell me, if the problem remains ...

By the way, I should note that pyx indeed tries to create a
temporary file handed over to TeX. This file has a temporary
name and is removed after TeX should have read it. The file
is created in the local directory (all these things are
build in order to come over some TeX limitations). However,
since the creation of the file should have been done at that
point your problem occures (otherwise you should have got
some exception earlier), you might be able to see that file
(you might need to turn off the atexit call to cleen the
temporary files in text.py). On the other hand, TeX said in
the example above, that it could not read that very file.
Still, very strange ...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

[PyX-devel] [ pyx-Bugs-821284 ] problem in key with title=None

[SourceForge.net <no...@so...>]

Bugs item #821284, was opened at 2003-10-10 15:29
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=821284&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Gert Ingold (gertingold)
Assigned to: Nobody/Anonymous (nobody)
Summary: problem in key with title=None

Initial Comment:
The task was to plot data and to produce a key for only
some of the data files. Omitting the title for these
data files obviously does not help as key entries with
label (unknown) are produced. However, one would expect
title=None to work. Unfortunately, this results in a
TeX error (see attached file fss.err). Shouldn't this
be implemented in such a way that title=None simply
ignores the corresponding data set while generating the
key?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=821284&group_id=45430

[PyX-devel] [ pyx-Bugs-817717 ] TeX error with PyX-0.4.1

[SourceForge.net <no...@so...>]

Bugs item #817717, was opened at 2003-10-04 16:17
Message generated for change (Comment added) made by wobsta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: TeX error with PyX-0.4.1

Initial Comment:
I run Python 2.1.3, TeX (Web2C 7.3.7) 3.14159 and
kpathsea version 3.3.7 under Debian GNU/Linux 3.0.

If i run any of the examples which output some text I get 
the following error message:sieck@acertm:~$ python
/usr/lib/python2.1/site-packages/PyX/examples/hello.py 
Traceback (most recent call last):
  File
"/usr/lib/python2.1/site-packages/PyX/examples/hello.py",
line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/home/sieck/packages/PyX-0.4.1/pyx/canvas.py",
line 767, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2283, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2271, in _text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 1950, in execute
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2070, in execute
pyx.text.TexResultError: TeX didn't respond as expected
within the timeout period 
(5 seconds).
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXHAlign{0}%
 
\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlig
nRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%
 
\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:}}%
  \PyXInput{1}%
After parsing the return message from TeX, the
following was left:
  This is TeX, Version 3.14159 (Web2C 7.3.7)
  ! I can't find file `@473.0'.
  <*> @473.0
            
  Please type another input file name: ! I can't find
file `\scrollmode'.
  (cut after 5 lines, increase errordebug for more output)

# end of output

Any ideas?

Alexander Sieck

alexander dot sieck at web dot de


# start of output




----------------------------------------------------------------------

>Comment By: André Wobst (wobsta)
Date: 2003-10-09 08:06

Message:
Logged In: YES 
user_id=405853

I see. Point is, that the package installs the fonts but
does not automatically include them in the file psfonts.map
(used by dvips for example). This file contains some
information about the available PostScript-Fonts. When you
request cmr10 for example, there should be such an entry in
the psfonts.map file. (Run "kpsewhich psfonts.map" to find
this mapping file; it should be located at
/usr/share/texmf/dvips/config/psfonts.map.) Although there
are mapping files for the Computer Modern Roman fonts
available in your debian distribution (stable, isn't it),
they do not contain proper encoding information. Instead of
using those information from
/usr/share/texmf/dvips/bluesky/psfonts.cmr, you should
better extract the enclosing font information. You should be
able to run test.py in the test directory after extraction.
You can then install this psfonts.map and *.enc files in the
appropriate texmf directory to make it globally available.
You can either install it into something like
/usr/local/share/texmf/dvips/psfonts or in your home
directory ~/texmf/dvips/psfonts. See "kpsewhich texmf.cnf"
about your TeX related search path configuration.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-08 22:19

Message:
Logged In: NO 

Hello,

it still doesn't work. I have installed tetex-extra:
sieck@acertm:~/packages/PyX-0.4.1/examples$ find
/usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf
sieck@acertm:~/packages/PyX-0.4.1/examples$ ls
/usr/share/texmf/fonts/type1/
adobe  bitstrea  bluesky  hoekwater  public  urw

But for all examples with text-output, e.g. hello.py,
I still get the error:

RuntimeError: no information for font 'cmr10' found in font
mapping file

When I did run make in /PyX-0.4.1/manual/ the first time,
there was a message about some files that couldn't be
created, a request to rerun it and finally the same error
as above.
After the rerun it finished without this error message
and manual.dvi was created.

Are there any environment variables I have to set or does
one need to initialize the Type1 fonts?
I rebooted after installing tetex-extra, to initialize tetex or
kpathsea, but this didn't help.
In the docu I only found a hint to mktexls-r, but this is only
to speed kpathsea up, right?

Regards
               Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-08 08:48

Message:
Logged In: YES 
user_id=405853

It's nice to see that you could get distutils working. You
are totally right about the python-dev package you need to
install for that.

It's quite likely that you are missing just one last point
now: You need the TeX-Fonts in Type1 format (a scalable font
format from Adobe available in a direct PostScript version
(called *.pfa) and a packed version of it (called *.pfb) --
the later are usually distributed and PyX needs it). This is
nice to have for tex&dvips as well, since you are not stick
to the metafont pk-version of the fonts anymore (which has
some advantages, e.g. in pdf creation and other things). The
type1-Fonts are available in the debian package tetex-extra.
Just install this package to get the files like cmr10.pfb
... then try again.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-07 23:35

Message:
Logged In: NO 

Hello,

since I couldn't find the distutils for Python2.1 
"python setup.py install" failed with
"No module distutils.core". Therefore, I extracted
PyX-0.4.1.tar directly to ../lib/python2.1/site-packages.
With this I could produce the example box.eps, but the
examples with text-output produced the message given
above.
In the meantime I learned that since Python1.6 the
distutils module is in python2.x-dev and installed
it. Then I run "python setup.py install" and removed
the PyX directory in site-packages. This solved the
problem mentioned above.

Unfortunately, now something is wrong with the TeX fonts:
=== start of output ===
sieck@acertm:~/packages/PyX-0.4.1/examples$ python hello.py
Traceback (most recent call last):
  File "hello.py", line 6, in ?
    c.writetofile("hello")
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 936, in writetofile
    for pritem in self.prolog():
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 661, in prolog
    result.extend(cmd.prolog())
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1780, in prolog
    return result + self.texrunner.prolog(self.dvinumber,
self.page)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2086, in prolog
    self.getdvi()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2080, in getdvi
    self.dvifiles.append(DVIFile(dvifilename,
debug=self.dvidebug))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
685, in __init__
    self.readfile()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1087, in readfile
    state = self._read_page()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1045, in _read_page
    file.read(file.readuchar()+file.readuchar()))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
773, in definefont
    self.fonts[num] =  Font(fontname, c, q, d, self.tfmconv,
self.debug > 1)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
516, in __init__
    raise RuntimeError("no information for font '%s' found
in font mapping file, aborting" % name)
  RuntimeError: no information for font 'cmr10' found in
font mapping file, aborting
=== end of output ===

"libkpathsea-dev - kpathsea.a and include files for teTeX"
is installed.
The environment variables in /etc/texmf/texmf.cnf seem to be
in agreement
with the documentation.
A file cmr10.tfm does exist:
sieck@acertm:~$ find /usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf

I can use LaTeX separately without problems, e.g. article.cls
and german.sty and the fonts are found.

I am not sure whether the problem is caused by my environment
or by PyX.

Regards 
             Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-06 17:46

Message:
Logged In: YES 
user_id=405853

I could not yet reproduce your problem. It would be really
nice if you could do some tests in order to better trace
down the problem.

First of all, I'm wondering that you've installed the
examples systemwide (this would not be the case when you run
"python setup.py install" in the pyx directory --- which is
the suggested way to install pyx). The PyX directory in
/usr/lib/pythonx.x/site-packages should not contain
uppercase characters. You can already see some strange
behavior that pyx in taken not from
/usr/lib/pythonx.x/site-packages/pyx but from somewhere in
your home directory. I expect this to be due to your way of
installing pyx. Could you first of all try to fix this and
the tell me, if the problem remains ...

By the way, I should note that pyx indeed tries to create a
temporary file handed over to TeX. This file has a temporary
name and is removed after TeX should have read it. The file
is created in the local directory (all these things are
build in order to come over some TeX limitations). However,
since the creation of the file should have been done at that
point your problem occures (otherwise you should have got
some exception earlier), you might be able to see that file
(you might need to turn off the atexit call to cleen the
temporary files in text.py). On the other hand, TeX said in
the example above, that it could not read that very file.
Still, very strange ...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

[PyX-devel] [ pyx-Bugs-817717 ] TeX error with PyX-0.4.1

[SourceForge.net <no...@so...>]

Bugs item #817717, was opened at 2003-10-04 07:17
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: TeX error with PyX-0.4.1

Initial Comment:
I run Python 2.1.3, TeX (Web2C 7.3.7) 3.14159 and
kpathsea version 3.3.7 under Debian GNU/Linux 3.0.

If i run any of the examples which output some text I get 
the following error message:sieck@acertm:~$ python
/usr/lib/python2.1/site-packages/PyX/examples/hello.py 
Traceback (most recent call last):
  File
"/usr/lib/python2.1/site-packages/PyX/examples/hello.py",
line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/home/sieck/packages/PyX-0.4.1/pyx/canvas.py",
line 767, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2283, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2271, in _text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 1950, in execute
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2070, in execute
pyx.text.TexResultError: TeX didn't respond as expected
within the timeout period 
(5 seconds).
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXHAlign{0}%
 
\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlig
nRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%
 
\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:}}%
  \PyXInput{1}%
After parsing the return message from TeX, the
following was left:
  This is TeX, Version 3.14159 (Web2C 7.3.7)
  ! I can't find file `@473.0'.
  <*> @473.0
            
  Please type another input file name: ! I can't find
file `\scrollmode'.
  (cut after 5 lines, increase errordebug for more output)

# end of output

Any ideas?

Alexander Sieck

alexander dot sieck at web dot de


# start of output




----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-08 13:19

Message:
Logged In: NO 

Hello,

it still doesn't work. I have installed tetex-extra:
sieck@acertm:~/packages/PyX-0.4.1/examples$ find
/usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf
sieck@acertm:~/packages/PyX-0.4.1/examples$ ls
/usr/share/texmf/fonts/type1/
adobe  bitstrea  bluesky  hoekwater  public  urw

But for all examples with text-output, e.g. hello.py,
I still get the error:

RuntimeError: no information for font 'cmr10' found in font
mapping file

When I did run make in /PyX-0.4.1/manual/ the first time,
there was a message about some files that couldn't be
created, a request to rerun it and finally the same error
as above.
After the rerun it finished without this error message
and manual.dvi was created.

Are there any environment variables I have to set or does
one need to initialize the Type1 fonts?
I rebooted after installing tetex-extra, to initialize tetex or
kpathsea, but this didn't help.
In the docu I only found a hint to mktexls-r, but this is only
to speed kpathsea up, right?

Regards
               Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-07 23:48

Message:
Logged In: YES 
user_id=405853

It's nice to see that you could get distutils working. You
are totally right about the python-dev package you need to
install for that.

It's quite likely that you are missing just one last point
now: You need the TeX-Fonts in Type1 format (a scalable font
format from Adobe available in a direct PostScript version
(called *.pfa) and a packed version of it (called *.pfb) --
the later are usually distributed and PyX needs it). This is
nice to have for tex&dvips as well, since you are not stick
to the metafont pk-version of the fonts anymore (which has
some advantages, e.g. in pdf creation and other things). The
type1-Fonts are available in the debian package tetex-extra.
Just install this package to get the files like cmr10.pfb
... then try again.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-07 14:35

Message:
Logged In: NO 

Hello,

since I couldn't find the distutils for Python2.1 
"python setup.py install" failed with
"No module distutils.core". Therefore, I extracted
PyX-0.4.1.tar directly to ../lib/python2.1/site-packages.
With this I could produce the example box.eps, but the
examples with text-output produced the message given
above.
In the meantime I learned that since Python1.6 the
distutils module is in python2.x-dev and installed
it. Then I run "python setup.py install" and removed
the PyX directory in site-packages. This solved the
problem mentioned above.

Unfortunately, now something is wrong with the TeX fonts:
=== start of output ===
sieck@acertm:~/packages/PyX-0.4.1/examples$ python hello.py
Traceback (most recent call last):
  File "hello.py", line 6, in ?
    c.writetofile("hello")
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 936, in writetofile
    for pritem in self.prolog():
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 661, in prolog
    result.extend(cmd.prolog())
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1780, in prolog
    return result + self.texrunner.prolog(self.dvinumber,
self.page)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2086, in prolog
    self.getdvi()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2080, in getdvi
    self.dvifiles.append(DVIFile(dvifilename,
debug=self.dvidebug))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
685, in __init__
    self.readfile()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1087, in readfile
    state = self._read_page()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1045, in _read_page
    file.read(file.readuchar()+file.readuchar()))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
773, in definefont
    self.fonts[num] =  Font(fontname, c, q, d, self.tfmconv,
self.debug > 1)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
516, in __init__
    raise RuntimeError("no information for font '%s' found
in font mapping file, aborting" % name)
  RuntimeError: no information for font 'cmr10' found in
font mapping file, aborting
=== end of output ===

"libkpathsea-dev - kpathsea.a and include files for teTeX"
is installed.
The environment variables in /etc/texmf/texmf.cnf seem to be
in agreement
with the documentation.
A file cmr10.tfm does exist:
sieck@acertm:~$ find /usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf

I can use LaTeX separately without problems, e.g. article.cls
and german.sty and the fonts are found.

I am not sure whether the problem is caused by my environment
or by PyX.

Regards 
             Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-06 08:46

Message:
Logged In: YES 
user_id=405853

I could not yet reproduce your problem. It would be really
nice if you could do some tests in order to better trace
down the problem.

First of all, I'm wondering that you've installed the
examples systemwide (this would not be the case when you run
"python setup.py install" in the pyx directory --- which is
the suggested way to install pyx). The PyX directory in
/usr/lib/pythonx.x/site-packages should not contain
uppercase characters. You can already see some strange
behavior that pyx in taken not from
/usr/lib/pythonx.x/site-packages/pyx but from somewhere in
your home directory. I expect this to be due to your way of
installing pyx. Could you first of all try to fix this and
the tell me, if the problem remains ...

By the way, I should note that pyx indeed tries to create a
temporary file handed over to TeX. This file has a temporary
name and is removed after TeX should have read it. The file
is created in the local directory (all these things are
build in order to come over some TeX limitations). However,
since the creation of the file should have been done at that
point your problem occures (otherwise you should have got
some exception earlier), you might be able to see that file
(you might need to turn off the atexit call to cleen the
temporary files in text.py). On the other hand, TeX said in
the example above, that it could not read that very file.
Still, very strange ...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

[PyX-devel] [ pyx-Bugs-817717 ] TeX error with PyX-0.4.1

[SourceForge.net <no...@so...>]

Bugs item #817717, was opened at 2003-10-04 16:17
Message generated for change (Comment added) made by wobsta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: TeX error with PyX-0.4.1

Initial Comment:
I run Python 2.1.3, TeX (Web2C 7.3.7) 3.14159 and
kpathsea version 3.3.7 under Debian GNU/Linux 3.0.

If i run any of the examples which output some text I get 
the following error message:sieck@acertm:~$ python
/usr/lib/python2.1/site-packages/PyX/examples/hello.py 
Traceback (most recent call last):
  File
"/usr/lib/python2.1/site-packages/PyX/examples/hello.py",
line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/home/sieck/packages/PyX-0.4.1/pyx/canvas.py",
line 767, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2283, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2271, in _text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 1950, in execute
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2070, in execute
pyx.text.TexResultError: TeX didn't respond as expected
within the timeout period 
(5 seconds).
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXHAlign{0}%
 
\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlig
nRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%
 
\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:}}%
  \PyXInput{1}%
After parsing the return message from TeX, the
following was left:
  This is TeX, Version 3.14159 (Web2C 7.3.7)
  ! I can't find file `@473.0'.
  <*> @473.0
            
  Please type another input file name: ! I can't find
file `\scrollmode'.
  (cut after 5 lines, increase errordebug for more output)

# end of output

Any ideas?

Alexander Sieck

alexander dot sieck at web dot de


# start of output




----------------------------------------------------------------------

>Comment By: André Wobst (wobsta)
Date: 2003-10-08 08:48

Message:
Logged In: YES 
user_id=405853

It's nice to see that you could get distutils working. You
are totally right about the python-dev package you need to
install for that.

It's quite likely that you are missing just one last point
now: You need the TeX-Fonts in Type1 format (a scalable font
format from Adobe available in a direct PostScript version
(called *.pfa) and a packed version of it (called *.pfb) --
the later are usually distributed and PyX needs it). This is
nice to have for tex&dvips as well, since you are not stick
to the metafont pk-version of the fonts anymore (which has
some advantages, e.g. in pdf creation and other things). The
type1-Fonts are available in the debian package tetex-extra.
Just install this package to get the files like cmr10.pfb
... then try again.

HTH, Andre

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-07 23:35

Message:
Logged In: NO 

Hello,

since I couldn't find the distutils for Python2.1 
"python setup.py install" failed with
"No module distutils.core". Therefore, I extracted
PyX-0.4.1.tar directly to ../lib/python2.1/site-packages.
With this I could produce the example box.eps, but the
examples with text-output produced the message given
above.
In the meantime I learned that since Python1.6 the
distutils module is in python2.x-dev and installed
it. Then I run "python setup.py install" and removed
the PyX directory in site-packages. This solved the
problem mentioned above.

Unfortunately, now something is wrong with the TeX fonts:
=== start of output ===
sieck@acertm:~/packages/PyX-0.4.1/examples$ python hello.py
Traceback (most recent call last):
  File "hello.py", line 6, in ?
    c.writetofile("hello")
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 936, in writetofile
    for pritem in self.prolog():
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 661, in prolog
    result.extend(cmd.prolog())
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1780, in prolog
    return result + self.texrunner.prolog(self.dvinumber,
self.page)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2086, in prolog
    self.getdvi()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2080, in getdvi
    self.dvifiles.append(DVIFile(dvifilename,
debug=self.dvidebug))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
685, in __init__
    self.readfile()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1087, in readfile
    state = self._read_page()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1045, in _read_page
    file.read(file.readuchar()+file.readuchar()))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
773, in definefont
    self.fonts[num] =  Font(fontname, c, q, d, self.tfmconv,
self.debug > 1)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
516, in __init__
    raise RuntimeError("no information for font '%s' found
in font mapping file, aborting" % name)
  RuntimeError: no information for font 'cmr10' found in
font mapping file, aborting
=== end of output ===

"libkpathsea-dev - kpathsea.a and include files for teTeX"
is installed.
The environment variables in /etc/texmf/texmf.cnf seem to be
in agreement
with the documentation.
A file cmr10.tfm does exist:
sieck@acertm:~$ find /usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf

I can use LaTeX separately without problems, e.g. article.cls
and german.sty and the fonts are found.

I am not sure whether the problem is caused by my environment
or by PyX.

Regards 
             Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-06 17:46

Message:
Logged In: YES 
user_id=405853

I could not yet reproduce your problem. It would be really
nice if you could do some tests in order to better trace
down the problem.

First of all, I'm wondering that you've installed the
examples systemwide (this would not be the case when you run
"python setup.py install" in the pyx directory --- which is
the suggested way to install pyx). The PyX directory in
/usr/lib/pythonx.x/site-packages should not contain
uppercase characters. You can already see some strange
behavior that pyx in taken not from
/usr/lib/pythonx.x/site-packages/pyx but from somewhere in
your home directory. I expect this to be due to your way of
installing pyx. Could you first of all try to fix this and
the tell me, if the problem remains ...

By the way, I should note that pyx indeed tries to create a
temporary file handed over to TeX. This file has a temporary
name and is removed after TeX should have read it. The file
is created in the local directory (all these things are
build in order to come over some TeX limitations). However,
since the creation of the file should have been done at that
point your problem occures (otherwise you should have got
some exception earlier), you might be able to see that file
(you might need to turn off the atexit call to cleen the
temporary files in text.py). On the other hand, TeX said in
the example above, that it could not read that very file.
Still, very strange ...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

[PyX-devel] [ pyx-Bugs-817717 ] TeX error with PyX-0.4.1

[SourceForge.net <no...@so...>]

Bugs item #817717, was opened at 2003-10-04 07:17
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: TeX error with PyX-0.4.1

Initial Comment:
I run Python 2.1.3, TeX (Web2C 7.3.7) 3.14159 and
kpathsea version 3.3.7 under Debian GNU/Linux 3.0.

If i run any of the examples which output some text I get 
the following error message:sieck@acertm:~$ python
/usr/lib/python2.1/site-packages/PyX/examples/hello.py 
Traceback (most recent call last):
  File
"/usr/lib/python2.1/site-packages/PyX/examples/hello.py",
line 4, in ?
    c.text(0, 0, "Hello, world!")
  File "/home/sieck/packages/PyX-0.4.1/pyx/canvas.py",
line 767, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2283, in text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2271, in _text
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 1950, in execute
  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",
line 2070, in execute
pyx.text.TexResultError: TeX didn't respond as expected
within the timeout period 
(5 seconds).
The expression passed to TeX was:
  \scrollmode
  \raiseerror%
  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%
  \gdef\PyXHAlign{0}%
  \newbox\PyXBox%
  \newbox\PyXBoxHAligned%
  \newdimen\PyXDimenHAlignLT%
  \newdimen\PyXDimenHAlignRT%
  \newbox\PyXBoxVAlign%
  \newdimen\PyXDimenVAlign%
  \newbox\PyXBoxVBox%
  \newdimen\PyXDimenVBox%
  \long\def\ProcessPyXBox#1#2{%
  \setbox\PyXBox=\hbox{{#1}}%
  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%
  \PyXDimenHAlignRT=\wd\PyXBox%
  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%
  \gdef\PyXHAlign{0}%
 
\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlig
nRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%
 
\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:}}%
  \PyXInput{1}%
After parsing the return message from TeX, the
following was left:
  This is TeX, Version 3.14159 (Web2C 7.3.7)
  ! I can't find file `@473.0'.
  <*> @473.0
            
  Please type another input file name: ! I can't find
file `\scrollmode'.
  (cut after 5 lines, increase errordebug for more output)

# end of output

Any ideas?

Alexander Sieck

alexander dot sieck at web dot de


# start of output




----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2003-10-07 14:35

Message:
Logged In: NO 

Hello,

since I couldn't find the distutils for Python2.1 
"python setup.py install" failed with
"No module distutils.core". Therefore, I extracted
PyX-0.4.1.tar directly to ../lib/python2.1/site-packages.
With this I could produce the example box.eps, but the
examples with text-output produced the message given
above.
In the meantime I learned that since Python1.6 the
distutils module is in python2.x-dev and installed
it. Then I run "python setup.py install" and removed
the PyX directory in site-packages. This solved the
problem mentioned above.

Unfortunately, now something is wrong with the TeX fonts:
=== start of output ===
sieck@acertm:~/packages/PyX-0.4.1/examples$ python hello.py
Traceback (most recent call last):
  File "hello.py", line 6, in ?
    c.writetofile("hello")
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 936, in writetofile
    for pritem in self.prolog():
  File "/usr/lib/python2.1/site-packages/pyx/canvas.py",
line 661, in prolog
    result.extend(cmd.prolog())
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1780, in prolog
    return result + self.texrunner.prolog(self.dvinumber,
self.page)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2086, in prolog
    self.getdvi()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
2080, in getdvi
    self.dvifiles.append(DVIFile(dvifilename,
debug=self.dvidebug))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
685, in __init__
    self.readfile()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1087, in readfile
    state = self._read_page()
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
1045, in _read_page
    file.read(file.readuchar()+file.readuchar()))
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
773, in definefont
    self.fonts[num] =  Font(fontname, c, q, d, self.tfmconv,
self.debug > 1)
  File "/usr/lib/python2.1/site-packages/pyx/text.py", line
516, in __init__
    raise RuntimeError("no information for font '%s' found
in font mapping file, aborting" % name)
  RuntimeError: no information for font 'cmr10' found in
font mapping file, aborting
=== end of output ===

"libkpathsea-dev - kpathsea.a and include files for teTeX"
is installed.
The environment variables in /etc/texmf/texmf.cnf seem to be
in agreement
with the documentation.
A file cmr10.tfm does exist:
sieck@acertm:~$ find /usr/share/texmf -name cmr10*
/usr/share/texmf/fonts/tfm/public/cm/cmr10.tfm
/usr/share/texmf/fonts/source/public/cm/cmr10.mf

I can use LaTeX separately without problems, e.g. article.cls
and german.sty and the fonts are found.

I am not sure whether the problem is caused by my environment
or by PyX.

Regards 
             Alexander


----------------------------------------------------------------------

Comment By: André Wobst (wobsta)
Date: 2003-10-06 08:46

Message:
Logged In: YES 
user_id=405853

I could not yet reproduce your problem. It would be really
nice if you could do some tests in order to better trace
down the problem.

First of all, I'm wondering that you've installed the
examples systemwide (this would not be the case when you run
"python setup.py install" in the pyx directory --- which is
the suggested way to install pyx). The PyX directory in
/usr/lib/pythonx.x/site-packages should not contain
uppercase characters. You can already see some strange
behavior that pyx in taken not from
/usr/lib/pythonx.x/site-packages/pyx but from somewhere in
your home directory. I expect this to be due to your way of
installing pyx. Could you first of all try to fix this and
the tell me, if the problem remains ...

By the way, I should note that pyx indeed tries to create a
temporary file handed over to TeX. This file has a temporary
name and is removed after TeX should have read it. The file
is created in the local directory (all these things are
build in order to come over some TeX limitations). However,
since the creation of the file should have been done at that
point your problem occures (otherwise you should have got
some exception earlier), you might be able to see that file
(you might need to turn off the atexit call to cleen the
temporary files in text.py). On the other hand, TeX said in
the example above, that it could not read that very file.
Still, very strange ...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

[PyX-devel] [ pyx-Bugs-817717 ] TeX error with PyX-0.4.1

[SourceForge.net <no...@so...>]

Bugs item #817717, was opened at 2003-10-04 16:17
Message generated for change (Comment added) made by wobsta
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: TeX error with PyX-0.4.1

Initial Comment:
I run Python 2.1.3, TeX (Web2C 7.3.7) 3.14159 and

kpathsea version 3.3.7 under Debian GNU/Linux 3.0.



If i run any of the examples which output some text I get 

the following error message:sieck@acertm:~$ python

/usr/lib/python2.1/site-packages/PyX/examples/hello.py 

Traceback (most recent call last):

  File

"/usr/lib/python2.1/site-packages/PyX/examples/hello.py",

line 4, in ?

    c.text(0, 0, "Hello, world!")

  File "/home/sieck/packages/PyX-0.4.1/pyx/canvas.py",

line 767, in text

  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",

line 2283, in text

  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",

line 2271, in _text

  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",

line 1950, in execute

  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",

line 2070, in execute

pyx.text.TexResultError: TeX didn't respond as expected

within the timeout period 

(5 seconds).

The expression passed to TeX was:

  \scrollmode

  \raiseerror%

  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%

  \gdef\PyXHAlign{0}%

  \newbox\PyXBox%

  \newbox\PyXBoxHAligned%

  \newdimen\PyXDimenHAlignLT%

  \newdimen\PyXDimenHAlignRT%

  \newbox\PyXBoxVAlign%

  \newdimen\PyXDimenVAlign%

  \newbox\PyXBoxVBox%

  \newdimen\PyXDimenVBox%

  \long\def\ProcessPyXBox#1#2{%

  \setbox\PyXBox=\hbox{{#1}}%

  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%

  \PyXDimenHAlignRT=\wd\PyXBox%

  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%

  \gdef\PyXHAlign{0}%

 

\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlig

nRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%

 

\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:}}%

  \PyXInput{1}%

After parsing the return message from TeX, the

following was left:

  This is TeX, Version 3.14159 (Web2C 7.3.7)

  ! I can't find file `@473.0'.

  <*> @473.0

            

  Please type another input file name: ! I can't find

file `\scrollmode'.

  (cut after 5 lines, increase errordebug for more output)



# end of output



Any ideas?



Alexander Sieck



alexander dot sieck at web dot de





# start of output







----------------------------------------------------------------------

>Comment By: André Wobst (wobsta)
Date: 2003-10-06 17:46

Message:
Logged In: YES 
user_id=405853

I could not yet reproduce your problem. It would be really

nice if you could do some tests in order to better trace

down the problem.



First of all, I'm wondering that you've installed the

examples systemwide (this would not be the case when you run

"python setup.py install" in the pyx directory --- which is

the suggested way to install pyx). The PyX directory in

/usr/lib/pythonx.x/site-packages should not contain

uppercase characters. You can already see some strange

behavior that pyx in taken not from

/usr/lib/pythonx.x/site-packages/pyx but from somewhere in

your home directory. I expect this to be due to your way of

installing pyx. Could you first of all try to fix this and

the tell me, if the problem remains ...



By the way, I should note that pyx indeed tries to create a

temporary file handed over to TeX. This file has a temporary

name and is removed after TeX should have read it. The file

is created in the local directory (all these things are

build in order to come over some TeX limitations). However,

since the creation of the file should have been done at that

point your problem occures (otherwise you should have got

some exception earlier), you might be able to see that file

(you might need to turn off the atexit call to cleen the

temporary files in text.py). On the other hand, TeX said in

the example above, that it could not read that very file.

Still, very strange ...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

[PyX-devel] [ pyx-Bugs-817717 ] TeX error with PyX-0.4.1

[SourceForge.net <no...@so...>]

Bugs item #817717, was opened at 2003-10-04 07:17
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: TeX error with PyX-0.4.1

Initial Comment:
I run Python 2.1.3, TeX (Web2C 7.3.7) 3.14159 and

kpathsea version 3.3.7 under Debian GNU/Linux 3.0.



If i run any of the examples which output some text I get 

the following error message:sieck@acertm:~$ python

/usr/lib/python2.1/site-packages/PyX/examples/hello.py 

Traceback (most recent call last):

  File

"/usr/lib/python2.1/site-packages/PyX/examples/hello.py",

line 4, in ?

    c.text(0, 0, "Hello, world!")

  File "/home/sieck/packages/PyX-0.4.1/pyx/canvas.py",

line 767, in text

  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",

line 2283, in text

  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",

line 2271, in _text

  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",

line 1950, in execute

  File "/home/sieck/packages/PyX-0.4.1/pyx/text.py",

line 2070, in execute

pyx.text.TexResultError: TeX didn't respond as expected

within the timeout period 

(5 seconds).

The expression passed to TeX was:

  \scrollmode

  \raiseerror%

  \def\PyX{P\kern-.3em\lower.5ex\hbox{Y}\kern-.18em X}%

  \gdef\PyXHAlign{0}%

  \newbox\PyXBox%

  \newbox\PyXBoxHAligned%

  \newdimen\PyXDimenHAlignLT%

  \newdimen\PyXDimenHAlignRT%

  \newbox\PyXBoxVAlign%

  \newdimen\PyXDimenVAlign%

  \newbox\PyXBoxVBox%

  \newdimen\PyXDimenVBox%

  \long\def\ProcessPyXBox#1#2{%

  \setbox\PyXBox=\hbox{{#1}}%

  \PyXDimenHAlignLT=\PyXHAlign\wd\PyXBox%

  \PyXDimenHAlignRT=\wd\PyXBox%

  \advance\PyXDimenHAlignRT by -\PyXDimenHAlignLT%

  \gdef\PyXHAlign{0}%

 

\immediate\write16{PyXBox:page=#2,lt=\the\PyXDimenHAlignLT,rt=\the\PyXDimenHAlig

nRT,ht=\the\ht\PyXBox,dp=\the\dp\PyXBox:}%

 

\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:}}%

  \PyXInput{1}%

After parsing the return message from TeX, the

following was left:

  This is TeX, Version 3.14159 (Web2C 7.3.7)

  ! I can't find file `@473.0'.

  <*> @473.0

            

  Please type another input file name: ! I can't find

file `\scrollmode'.

  (cut after 5 lines, increase errordebug for more output)



# end of output



Any ideas?



Alexander Sieck



alexander dot sieck at web dot de





# start of output







----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442886&aid=817717&group_id=45430