pyx-user — PyX user

[PyX-user] Help

[. N. <nar...@ut...>]

To whom it may concern,

Would you please help me with how to change the view of a 3D graph? The pyX file is copied below:



import math
from pyx import *
#from pyx.graph import axis
#painter=graph.axis.painter.regular(labelattrs=[color.grey.white])





# colors and symbols to use (alternatingly)
colors = [color.rgb.red, color.rgb.green, color.rgb.blue,color.cmyk.Sepia,color.cmyk.RubineRed, color.cmyk.Yellow,color.cmyk.RedOrange, color.cmyk.Violet, color.cmyk.CornflowerBlue,color.gray.black]
colors1 = [color.gray.black]
symbols = [graph.style._diamondsymbol, graph.style._trianglesymbol, graph.style._circlesymbol, graph.style._squaresymbol]

# create the graph styles to be used below
symbol = graph.style.symbol(symbol=attr.changelist(symbols), size=0.12,
                            symbolattrs=[deco.stroked.clear,
                                         attr.changelist([deco.filled([cc]) for cc in colors])])
line = graph.style.line(lineattrs=[attr.changelist(colors),
                                   attr.changelist([style.linestyle.solid])])

line1 = graph.style.line(lineattrs=[attr.changelist(colors1),
                                   attr.changelist([style.linestyle.dashed])])

myparter1 = graph.axis.parter.linear(["0.25", "2.5"])
myparter2 = graph.axis.parter.linear(["1.25", "1.25"])



g = graph.graphxyz(size=6.5,  key=graph.key.key( pos="tl", columndist=0.1*unit.v_cm, hdist=0.3*unit.v_cm, vdist=0.3*unit.v_cm, symbolspace=0.2*unit.v_cm, columns=1, dist=0.1),


                 x=graph.axis.lin(min= -2.5, max= 2.5, title=r"$\Large{q}$"),
                 y=graph.axis.lin(min= -0.75, max= 0.15, title=r"$\Large{{\rm Re}(s)}$"),
                 z=graph.axis.lin(min= -0.25, max= 0.25, title=r"$\Large{{\rm Im}(s)}$"))




g.plot(graph.data.file("Root1.dat", x=1, y=2, z=3, title= None), styles=[line])
g.plot(graph.data.file("Root2.dat", x=1, y=2, z=3, title= None), styles=[line])
g.plot(graph.data.file("Root3.dat", x=1, y=2, z=3, title= None), styles=[line])
#g.plot(graph.data.file("table3.data", x=1, y=2, title= None), styles=[line])
#g.plot(graph.data.file("table_0.data", x=1, y=2, title= None), styles=[line1])
#g.plot(graph.data.file("fort.3", x=1, y=4, title=r"$k_v = 40$"), styles=[line, symbol])
#g.plot(graph.data.function("y(x)= 0.0", title= None ),styles=[line1])



#g.text(6.0,0.8,0.1,r"\small{$n_C = 1$}")
#g.text(6.0,0.4,r"\small{$\tilde{k}_{+} = 0.01$}")
g.text(-7,4,r"$\Large{r_{BA} = 0.1, \tilde{k}_{+} = 0.01, \tilde{D}_{t}^{\rm eff} = 0.1, n_C = 1}$")
#g.text(1.1,0.4,r"\small{$\tilde{D}_{t}^{\rm eff} = 0.1$}")

#g.text(1.82,2.0,r"\small{$s = -2 k - D q^2$}")










g.writeEPSfile("Stability_Analysis_3D_Reaction")
g.writePDFfile("Stability_Analysis_3D_Reaction")







Best,
Narender

[PyX-user] ANN: PyX 0.16 released

[André W. <co...@wo...>]

Hi,

We're very happy to announce the release of PyX 0.16! This release 
enables a shortcut for accessing graph-component attributes, simplifying 
the modification of default components. Small improvements and several 
bug fixes, especially for the text alignment with TeX Live 2020, are 
included. See the full list of changes below.

Happy PyXing,

          André and Jörg

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

0.16 (2022/10/16):
    - graph module:
      - enable shortcut for passing arguments through graph components
        (axes, painters, etc.) by passing keyword arguments consisting
        of graph components separated by underscores.
    - graph.axis.style:
      - Allow invalid values (e.g. None) in color values of density
        style.
    - text module:
      - make alignment work with texlive 2020 (reported by Thomas
        Bending)
      - fix deprecation warning for isSet
    - dvi module:
      - ignore the l3backend header special for dvips
    - bitmap module:
      - fix bitmap palette data pdf output being bytes
    - canvas module:
       - add clear() method to canvas class (suggested by Camilo Talero)
    - t1 extension module:
       - adjust to int/Py_ssize_t change in python 3.10 (thanks to
         Michael J Gruber)
    - graph.axis.texter:
      - rename multiplication_tex -> multiplicationtex and
        multiplication_unicode -> multiplicationunicode in default texter
    - manual:
      - Remove deprecated code in colorname.py and gradientname.py
        (thanks to grozin for reporting this in bug #37)
    - the gallery has been moved away from sourceforge.net wiki to the
      PyX website. Contributions by pull requests are welcome.

[PyX-user] roadmap?

[S J. S. <swa...@gm...>]

Hello,

PyX really is an excellent little library. I was wondering what sort of
development is planned, and I hope that development can remain active.

*S. Joshua Swamidass M.D. Ph.D.*
http://swami.wustl.edu/

Faculty Lead, Translational Bioinformatics, Institute for Informatics
Associate Professor, Laboratory and Genomic Medicine
Associate Professor, Biomedical Engineering
Washington University in St. Louis

Administrator: Lori Scantlan <*lls...@wu... <lls...@wu...>*>

Re: [PyX-user] Bug(?) in text placement using LaTeX

[Michael J G. <mic...@us...>]

Hi there,

I'm still curious why I'm not seeing this on Fedora 34. Maybe the
l3backend (which I have no idea about) can be disabled or enabled?
2020-03-12 is the in-file version for l3backend-dvips.def.

In any case, l3backend apparently will stop adding to AtBeginDvi again:

https://github.com/latex3/latex3/commit/8e5ab128710c56558b5a48cfa58132494a4ba3c5

It's still worthwhile to deal with the problem for versions between
that and the one Thomas reported on, of course.

I also came across the new option `suppress-backend-headers` which may
help with the warning:

https://github.com/latex3/latex3/commit/d9355f33a9194764bc3255d9f4f59b12e9446bd9

Cheers
Michael

Re: [PyX-user] Bug(?) in text placement using LaTeX

[Thomas B. <tho...@ho...>]

Hi André,

This patch fixes the problem for me (although I still get the warning, as
you say).

Many thanks for your very quick help,

Thomas


On Thu, 24 Jun 2021 at 19:16, André Wobst <co...@wo...> wrote:

> Hi,
>
> I could reproduce it on Debian 11 (not yet released). It seems related
> to the upgrade to TeX Live 2020, which added the l3backend (was not
> present before). This package adds specials by \AtBeginDvi{...}, which
> unboxes the box send to \shipout and re-boxes it. By that the vertical
> alignment, which we set to zero height for the hbox passed to \shipout,
> gets lost at the first box shipped out by PyX.
>
> There is a simple solution in applying this vertical setting at the box
> nested inside, before we also fix the horizontal alignment according to
> the output requirements. This should not introduce any difference for
> regular use, although (as it is TeX/LaTeX) any difference can always be
> utilized (as the l3backend shows). Please try the attached patch. I hope
> it resolves the issue for you. (And we probably should release this soon
> ...)
>
>
> André
>
> PS: The additional special output (warning by PyX) has not yet been
> addressed/silenced. Also, I have not yet checked whether we can continue
> to use the pyx.def output driver as before. There are various open
> questions, which need further investigation ...
>
> Am 22.06.21 um 20:11 schrieb Thomas Bending:
> > I've used PyX happily for years, but I've recently noticed what seems to
> > be a bug in text placement when using LaTeX for text processing. Here's
> > my code:
> >
> > import pyx
> > pyx.text.set(engine = pyx.text.TexEngine)
> > c = pyx.canvas.canvas()
> > c.text(0, 0, 'A')
> > c.text(0, 0, 'B')
> > c.writePDFfile('out.pdf')
> >
> > This produces the file attached as out_tex.pdf, with the A and B
> > superimposed as I'd expect. However, if I change the engine specified in
> > line 2 to pyx.text.LatexEngine then
> >
> >  1. I see the warning /ignoring special 'header=l3backend-dvips.pro
> >     <http://l3backend-dvips.pro>'/
> >  2. The script produces the file attached as out_latex.pdf, with the A
> >     displaced downwards (and hence almost off the page).
> >
> > I'm using PyX 0.15, Python 3.9.5, TeX = TeX 3.14159265 (TeX Live
> > 2020/Debian) and LaTeX = pdfTeX 3.14159265-2.6-1.40.21 (TeX Live
> > 2020/Debian), all running under Ubuntu 21.04. I believe that this issue
> > appeared when I upgraded to Ubuntu 21.04, which may also have involved
> > upgrades to some of these packages.
> >
> > Can anyone suggest what I can do to prevent this displacement of the
> > text when using the LaTeX engine, please? Is this displacement related
> > to the warning? Any advice welcomed,
> >
> > Thomas
> >
> >
> >
> > _______________________________________________
> > PyX-user mailing list
> > PyX...@li...
> > https://lists.sourceforge.net/lists/listinfo/pyx-user
> >
>
> --
> by _ _      _
>    / \ \    / ) Dr. André Wobst, co...@wo..., https://www.wobsta.de
>   / _ \ \/\/ /  wobsta GmbH,  Ulmer Straße 248,  86156 Augsburg,  Germany
> (_/ \_)_/\_/   Office: +49 (0)821 90796043,  Mobile: +49 (0)160 93804217
>

Re: [PyX-user] Bug(?) in text placement using LaTeX

[André W. <co...@wo...>]

Hi,

I could reproduce it on Debian 11 (not yet released). It seems related 
to the upgrade to TeX Live 2020, which added the l3backend (was not 
present before). This package adds specials by \AtBeginDvi{...}, which 
unboxes the box send to \shipout and re-boxes it. By that the vertical 
alignment, which we set to zero height for the hbox passed to \shipout, 
gets lost at the first box shipped out by PyX.

There is a simple solution in applying this vertical setting at the box 
nested inside, before we also fix the horizontal alignment according to 
the output requirements. This should not introduce any difference for 
regular use, although (as it is TeX/LaTeX) any difference can always be 
utilized (as the l3backend shows). Please try the attached patch. I hope 
it resolves the issue for you. (And we probably should release this soon 
...)


André

PS: The additional special output (warning by PyX) has not yet been 
addressed/silenced. Also, I have not yet checked whether we can continue 
to use the pyx.def output driver as before. There are various open 
questions, which need further investigation ...

Am 22.06.21 um 20:11 schrieb Thomas Bending:
> I've used PyX happily for years, but I've recently noticed what seems to 
> be a bug in text placement when using LaTeX for text processing. Here's 
> my code:
> 
> import pyx
> pyx.text.set(engine = pyx.text.TexEngine)
> c = pyx.canvas.canvas()
> c.text(0, 0, 'A')
> c.text(0, 0, 'B')
> c.writePDFfile('out.pdf')
> 
> This produces the file attached as out_tex.pdf, with the A and B 
> superimposed as I'd expect. However, if I change the engine specified in 
> line 2 to pyx.text.LatexEngine then
> 
>  1. I see the warning /ignoring special 'header=l3backend-dvips.pro
>     <http://l3backend-dvips.pro>'/
>  2. The script produces the file attached as out_latex.pdf, with the A
>     displaced downwards (and hence almost off the page).
> 
> I'm using PyX 0.15, Python 3.9.5, TeX = TeX 3.14159265 (TeX Live 
> 2020/Debian) and LaTeX = pdfTeX 3.14159265-2.6-1.40.21 (TeX Live 
> 2020/Debian), all running under Ubuntu 21.04. I believe that this issue 
> appeared when I upgraded to Ubuntu 21.04, which may also have involved 
> upgrades to some of these packages.
> 
> Can anyone suggest what I can do to prevent this displacement of the 
> text when using the LaTeX engine, please? Is this displacement related 
> to the warning? Any advice welcomed,
> 
> Thomas
> 
> 
> 
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user
> 

-- 
by _ _      _
   / \ \    / ) Dr. André Wobst, co...@wo..., https://www.wobsta.de
  / _ \ \/\/ /  wobsta GmbH,  Ulmer Straße 248,  86156 Augsburg,  Germany
(_/ \_)_/\_/   Office: +49 (0)821 90796043,  Mobile: +49 (0)160 93804217

[PyX-user] Bug(?) in text placement using LaTeX

[Thomas B. <tho...@ho...>]

I've used PyX happily for years, but I've recently noticed what seems to be
a bug in text placement when using LaTeX for text processing. Here's my
code:

import pyx
pyx.text.set(engine = pyx.text.TexEngine)
c = pyx.canvas.canvas()
c.text(0, 0, 'A')
c.text(0, 0, 'B')
c.writePDFfile('out.pdf')

This produces the file attached as out_tex.pdf, with the A and B
superimposed as I'd expect. However, if I change the engine specified in
line 2 to pyx.text.LatexEngine then

   1. I see the warning *ignoring special 'header=l3backend-dvips.pro
   <http://l3backend-dvips.pro>'*
   2. The script produces the file attached as out_latex.pdf, with the A
   displaced downwards (and hence almost off the page).

I'm using PyX 0.15, Python 3.9.5, TeX = TeX 3.14159265 (TeX Live
2020/Debian) and LaTeX = pdfTeX 3.14159265-2.6-1.40.21 (TeX Live
2020/Debian), all running under Ubuntu 21.04. I believe that this issue
appeared when I upgraded to Ubuntu 21.04, which may also have involved
upgrades to some of these packages.

Can anyone suggest what I can do to prevent this displacement of the text
when using the LaTeX engine, please? Is this displacement related to the
warning? Any advice welcomed,

Thomas

Re: [PyX-user] Automatic logarithmic partitioner fails for small graph

[André W. <co...@wo...>]

Hi Alexis,

this is the expected behavior. The reason is, that (a) you need more 
then one number at an axis, (b) ranges are fixed if set at the axis, and 
(c) all automatic log axis "partitions" always include a label at value 
1 (i.e. 10^0). While any positive integer can be used as the step for 
the exponents (like 10^0, 10^2, 10^4, ..., or 10^0, 10^3, 10^6, ..., and 
so on) and an arbitrary range might be in use (i.e. not including 10^0), 
the logic remains that same. For your case numbers at 10^0 and 10^2 are 
a valid partition, but 10^1 and 10^3 are not. 10^1, 10^2, 10^3 is fine, 
too, but 10, 100 and 1000 is rejected in your case due to overlapping 
labels. (Changing the texter to write the numbers using exponents could 
help here.)

If you get the range from the data and allow PyX to extend the range (as 
done by default), it probably finds a reasonable solution. Also 
including 10^0 (i.e. 1) will likely help in many situations. However 
note that overlapping labels are always rejected. Hence for tiny graphs 
the automatic axis partitioning might fail and there is no way out 
except reducing the font size, but you already observed that ... :-)

Best,


André

Am 18.03.21 um 14:23 schrieb Alexis Poncet:
> Hi,
> 
> The following code fails with pyx.graph.axis.axis.NoValidPartitionError.
> 
> from pyx import *
> xaxis = graph.axis.log(min=10, max=1000)
> yaxis = graph.axis.log(min=1, max=100)
> g = graph.graphxy(width=1.2, x=xaxis, y=yaxis)
> g.writePDFfile()
> 
> I don't really understand why PyX is not able to find a partition. You 
> can check that the problem disappears with `width=1.3` or with 
> `unit.set(xscale=0.8)`.
> I solved by it by providing explicitely the ticks, but I feel that PyX 
> should be able to find a solution (as it does for the y axis).
> 
> ticks = [graph.axis.tick.tick(x, label=a) for x, a in zip([10, 100, 
> 1000], ["10", "", "1000"])]
> xaxis = graph.axis.log(min=10, max=1000, parter=None, manualticks=ticks)
> 
> I don't know if this qualifies as a bug, or if it is expected behavior.
> 
> Cheers,
> 
> Alexis
> 
> 
> 
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

-- 
by _ _      _
    / \ \    / ) Dr. André Wobst, co...@wo..., https://www.wobsta.de
   / _ \ \/\/ /  wobsta GmbH,  Ulmer Straße 248,  86156 Augsburg,  Germany
(_/ \_)_/\_/   Office: +49 (0)821 90796043,  Mobile: +49 (0)160 93804217

[PyX-user] Automatic logarithmic partitioner fails for small graph

[Alexis P. <ale...@so...>]

Hi,

The following code fails with pyx.graph.axis.axis.NoValidPartitionError.

from pyx import *
xaxis = graph.axis.log(min=10, max=1000)
yaxis = graph.axis.log(min=1, max=100)
g = graph.graphxy(width=1.2, x=xaxis, y=yaxis)
g.writePDFfile()

I don't really understand why PyX is not able to find a partition. You 
can check that the problem disappears with `width=1.3` or with 
`unit.set(xscale=0.8)`.
I solved by it by providing explicitely the ticks, but I feel that PyX 
should be able to find a solution (as it does for the y axis).

ticks = [graph.axis.tick.tick(x, label=a) for x, a in zip([10, 100, 
1000], ["10", "", "1000"])]
xaxis = graph.axis.log(min=10, max=1000, parter=None, manualticks=ticks)

I don't know if this qualifies as a bug, or if it is expected behavior.

Cheers,

Alexis

[PyX-user] pyx for python 3.9.1

[<rba...@mu...>]

2021.02.17

Salut,

The problem:

rbc@v320:~/Python/PyX-0.15$ python3 setup.py install
/usr/local/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution option: 'python_requires'
  warnings.warn(msg)
/usr/local/lib/python3.9/distutils/dist.py:274: UserWarning: Unknown distribution option: 'extras_require'
  warnings.warn(msg)
running install
running build
running build_py
running build_ext
building 'pyx.pykpathsea' extension
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/usr/local/include/python3.9 -c pyx/pykpathsea.c -o build/temp.linux-x86_64-3.9/pyx/pykpathsea.o
pyx/pykpathsea.c:21:31: fatal error: kpathsea/tex-file.h: Aucun fichier ou dossier de ce type
 #include <kpathsea/tex-file.h>
                               ^
compilation terminated.
error: command '/usr/bin/gcc' failed with exit code 1

Is there a solution?

René Bastian

Re: [PyX-user] Changing text font using preamble gives RuntimeError: missing font information for 'ecrm1000'; check fontmapping file(s)

[Michael J G. <mic...@us...>]

Hi Tony,

first of all sorry for misdirecting my first answer. I didn't mean to
steer you away from the list.

The issue is a misunderstanding of the ascii package, it seems. It is
a package for typesetting special ascii symbols. That's why it uses a
special encoding and has glyphs only in specific positions of that
encoding. In particular, you cannot use it as a textfont in T1. The
doc tells you to either use the commands which it supplies, or use the
glyph number as in \textascii{\char"16}. So:

\documentclass{article}
\usepackage{ascii}
\begin{document}
\SO
\end{document}

(when run through pdflatex) produces a PDF which uses the ascii font
for the musical score (plus the standard text font for the page number
which I did not turn off).

from pyx import *
text.set(cls=text.LatexRunner)
text.preamble(r"\usepackage{ascii}")
c = canvas.canvas()
c.text(0,0,r"\SO")
c.writePDFfile("test.pdf")

(when run through python) produces that same symbol. If your PyX is
quite new you'll get a warning to follow the switch from runner to
engine, which does not matter for the font issue.

Cheers
Michael

Am Di., 14. Juli 2020 um 10:56 Uhr schrieb jumbophut <jum...@gm...>:
>
> Thanks Michael.
>
> The output of kpsewhich sfrm1000.pfb was blank.  I fixed this with
> sudo apt-get install cm-super-minimal.  This fixed the error I was
> getting before, but I still wasn't getting font I wanted.  The PDF was
> still just computer modern.
>
> I then created the following LaTeX file and compiled with pdflatex test.tex:
> \documentclass{article}
> \usepackage{ascii}
> \usepackage[T1]{fontenc}
> \begin{document}
> {\fontfamily{ascii}\selectfont Testing}
> Testing
> \end{document}
>
> This produced only CM output and the warning "Font shape
> `T1/ascii/m/n' undefined".  So I edited
> /usr/share/texlive/texmf-dist/tex/latex/ascii-font/ascii.sty, which
> had the encoding as 'U', and changed all the 'U's to 'T1's (seems like
> an unwise thing but I couldn't work out what else to do).  Recompiling
> the .tex file gave ascii font for the first occurrence of testing and
> CM for the second.
>
> So, the ascii font is there and usable from pdflatex directly.
>
> However, it is not usable if I instead compile the file with "latex
> test.tex && dvips tex.dvi". In that case I get CM output in the
> postscript and the warning "Font shape `T1/ascii/m/n' undefined".
>
> Next I tried to run my PyX file:
> from pyx import *
> text.set(cls=text.LatexRunner)
> text.preamble(r"\usepackage{ascii} \usepackage[T1]{fontenc} ")
> c = canvas.canvas()
> c.text(0,0,"Testing")
> c.writePDFfile("test.pdf")
>
> The output PDF was just CM, and I got warnings about extracting font
> information from 'SFRM1000' being slow.
>
> Then I changed c.text(0,0,"Testing") to:
> c.text(0,0,r"{\fontfamily{ascii}\selectfont Testing}")
>
> That didn't fix the problem and I additionally got the warnings:
> "ignoring font substitutions of NFSS" and "Font shape `T1/ascii/m/n'
> undefined".
>
> Any suggestions about where to go from here?  I wonder if PyX is using
> latex + dvips to initially set the text (the combination which didn't
> work directly with my test .tex file) rather than pdflatex (which did
> work directly).  If so, one solution would be to make latex + dvips --
> like pdflatex -- see the fonts correctly, but I'm unsure how to do
> that.   (I realise that at this point it is starting to look more like
> a bigger texlive/Ubuntu problem than a PyX problem but hoping there
> might still be a straightforward solution).
>
> Cheers
> Tony
>
>
> On 7/14/20, Michael J Gruber <mic...@gm...> wrote:
> > Hi there,
> >
> > what does
> >
> > kpsewhich sfrm1000.pfb
> >
> > say? If your distro does like mine then the map files in /var are
> > recreated on the fly, taking into account which fonts are present. A
> > good test is also to compile a small LaTeX file using pdflatex: Can
> > you use the intended fonts this way? The error message indicates that
> > LaTeX does not find them.
> >
> > Cheers
> > Michael
> >
> > Am Mo., 13. Juli 2020 um 13:08 Uhr schrieb jumbophut <jum...@gm...>:
> >>
> >> I am trying to use a different font (not Computer Modern) in PyX, with
> >> standard Ubuntu 18.04 installs of PyX and texlive, but it is not
> >> working.  I have tried to resolve this but got lost in the minutiae of
> >> TeX font management.  Can anybody help?
> >>
> >> Running the following example:
> >>
> >> from pyx import *
> >> text.set(cls=text.LatexRunner)
> >> text.preamble(r"\usepackage{ascii} \normalfont \usepackage[T1]{fontenc}
> >> ")
> >> c = canvas.canvas()
> >> c.text(0,0,"Testing")
> >> c.writePDFfile("test.pdf")
> >>
> >> gives this error:
> >>
> >> RuntimeError: missing font information for 'ecrm1000'; check fontmapping
> >> file(s)
> >>
> >> I have found a mapping for ecrm1000 in
> >> /usr/share/texlive/texmf-dist/fonts/map/dvips/updmap/psfonts_t1.map
> >> (file A):
> >> ecrm1000 SFRM1000 " T1Encoding ReEncodeFont " <cm-super-t1.enc
> >> <sfrm1000.pfb
> >>
> >> I tried adding the following to .pyxrc, but it does not resolve the
> >> error:
> >> [text]
> >> fontmaps = psfonts.map psfonts_T1.map psfonts.cmz psfonts.amz
> >>
> >> There is no similar map in the other psfonts*.map files on my system.
> >> In particular, there is no entry in
> >> /var/lib/texmf/fonts/map/dvips/updmap/psfonts_t1.map (file B).  I
> >> tried copying file A over file B but it does not fix the error.
> >>
> >> If have also tried changing the preamble to:
> >> text.preamble(r"\usepackage{ascii} \usepackage[T1]{fontenc} ")
> >> (error is the same)
> >>
> >> and to
> >> text.preamble(r"\usepackage{ascii}")
> >> (no error but also no new font, just Computer Modern).
> >>
> >> Stack trace for the PyX error follows:
> >>
> >> Ignoring line 16630 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibBol'
> >> Ignoring line 16631 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibBol'
> >> Ignoring line 16632 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibBol'
> >> Ignoring line 16633 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibBolIta'
> >> Ignoring line 16634 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibBolIta'
> >> Ignoring line 16635 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibBolIta'
> >> Ignoring line 16636 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibIta'
> >> Ignoring line 16637 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibIta'
> >> Ignoring line 16638 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibIta'
> >> Ignoring line 16639 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibReg'
> >> Ignoring line 16640 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibReg'
> >> Ignoring line 16641 in mapping file 'pdftex.map': Unknown token
> >> '<MinLibReg'
> >> Traceback (most recent call last):
> >>   File "test.py", line 6, in <module>
> >>     c.writePDFfile("test.pdf")
> >>   File "/usr/lib/python3/dist-packages/pyx/canvas.py", line 50, in
> >> wrappedindocument
> >>     return method(d, file, **write_kwargs)
> >>   File "/usr/lib/python3/dist-packages/pyx/document.py", line 193, in
> >> writePDFfile
> >>     pdfwriter.PDFwriter(self, f, **kwargs)
> >>   File "/usr/lib/python3/dist-packages/pyx/pdfwriter.py", line 322, in
> >> __init__
> >>     catalog = PDFcatalog(document, self, registry)
> >>   File "/usr/lib/python3/dist-packages/pyx/pdfwriter.py", line 143, in
> >> __init__
> >>     self.PDFpages = PDFpages(document, writer, registry)
> >>   File "/usr/lib/python3/dist-packages/pyx/pdfwriter.py", line 208, in
> >> __init__
> >>     page = PDFpage(page, pageno, self, writer, registry)
> >>   File "/usr/lib/python3/dist-packages/pyx/pdfwriter.py", line 242, in
> >> __init__
> >>     self.PDFcontent = PDFcontent(page, writer, self.pageregistry)
> >>   File "/usr/lib/python3/dist-packages/pyx/pdfwriter.py", line 274, in
> >> __init__
> >>     page.processPDF(contentfile, awriter, acontext, registry, self.bbox)
> >>   File "/usr/lib/python3/dist-packages/pyx/document.py", line 135, in
> >> processPDF
> >>     self._process("processPDF", *args)
> >>   File "/usr/lib/python3/dist-packages/pyx/document.py", line 129, in
> >> _process
> >>     getattr(cc, processMethod)(contentfile, writer, context, registry,
> >> bbox)
> >>   File "/usr/lib/python3/dist-packages/pyx/canvas.py", line 238, in
> >> processPDF
> >>     item.processPDF(file, writer, context, registry, nbbox)
> >>   File "/usr/lib/python3/dist-packages/pyx/text.py", line 887, in
> >> processPDF
> >>     self.dvicanvas.processPDF(file, writer, context, registry, abbox)
> >>   File "/usr/lib/python3/dist-packages/pyx/canvas.py", line 238, in
> >> processPDF
> >>     item.processPDF(file, writer, context, registry, nbbox)
> >>   File "/usr/lib/python3/dist-packages/pyx/dvi/texfont.py", line 193,
> >> in processPDF
> >>     self._text(writer).processPDF(file, writer, context, registry, bbox)
> >>   File "/usr/lib/python3/dist-packages/pyx/dvi/texfont.py", line 179, in
> >> _text
> >>     mapline = self.font.getMAPline(writer.getfontmap())
> >>   File "/usr/lib/python3/dist-packages/pyx/dvi/texfont.py", line 134,
> >> in getMAPline
> >>     raise RuntimeError("missing font information for '%s'; check
> >> fontmapping file(s)" % self.name)
> >> RuntimeError: missing font information for 'ecrm1000'; check fontmapping
> >> file(s)
> >>
> >> Selected output from dpkg -l | grep ii texlive:
> >>
> >> ii  texlive-base                               2017.20180305-1
> >>                          all          TeX Live: Essential programs and
> >> files
> >> [...]
> >> ii  texlive-fonts-extra                        2017.20180305-2
> >>                          all          TeX Live: Additional fonts
> >> [...]
> >> ii  texlive-fonts-recommended                  2017.20180305-1
> >>                          all          TeX Live: Recommended fonts
> >> [...]
> >>
> >> Output of locate ecrm1000:
> >> /usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/ecrm1000.mf
> >> /usr/share/texlive/texmf-dist/fonts/tfm/jknappen/ec/ecrm1000.tfm
> >>
> >> Output of cat /etc/lsb-release:
> >> DISTRIB_ID=Ubuntu
> >> DISTRIB_RELEASE=18.04
> >> DISTRIB_CODENAME=bionic
> >> DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
> >>
> >> I read the PyX FAQ, which has an entry about cmr10 in it.  This error
> >> looks different, but just in case...
> >>
> >> Output of kpsewhich cmr10.pfb
> >> /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb
> >>
> >> --
> >> Tony (echo 'spend!,pocket awide' | sed 'y/acdeikospntw!,
> >> /l...@om...i/')
> >>
> >>
> >> _______________________________________________
> >> PyX-user mailing list
> >> PyX...@li...
> >> https://lists.sourceforge.net/lists/listinfo/pyx-user
> >
>
>
> --
> Tony (echo 'spend!,pocket awide' | sed 'y/acdeikospntw!, /l...@om...i/')

[PyX-user] Changing text font using preamble gives RuntimeError: missing font information for 'ecrm1000'; check fontmapping file(s)

[jumbophut <jum...@gm...>]

I am trying to use a different font (not Computer Modern) in PyX, with
standard Ubuntu 18.04 installs of PyX and texlive, but it is not
working.  I have tried to resolve this but got lost in the minutiae of
TeX font management.  Can anybody help?

Running the following example:

from pyx import *
text.set(cls=text.LatexRunner)
text.preamble(r"\usepackage{ascii} \normalfont \usepackage[T1]{fontenc} ")
c = canvas.canvas()
c.text(0,0,"Testing")
c.writePDFfile("test.pdf")

gives this error:

RuntimeError: missing font information for 'ecrm1000'; check fontmapping file(s)

I have found a mapping for ecrm1000 in
/usr/share/texlive/texmf-dist/fonts/map/dvips/updmap/psfonts_t1.map
(file A):
ecrm1000 SFRM1000 " T1Encoding ReEncodeFont " <cm-super-t1.enc <sfrm1000.pfb

I tried adding the following to .pyxrc, but it does not resolve the error:
[text]
fontmaps = psfonts.map psfonts_T1.map psfonts.cmz psfonts.amz

There is no similar map in the other psfonts*.map files on my system.
In particular, there is no entry in
/var/lib/texmf/fonts/map/dvips/updmap/psfonts_t1.map (file B).  I
tried copying file A over file B but it does not fix the error.

If have also tried changing the preamble to:
text.preamble(r"\usepackage{ascii} \usepackage[T1]{fontenc} ")
(error is the same)

and to
text.preamble(r"\usepackage{ascii}")
(no error but also no new font, just Computer Modern).

Stack trace for the PyX error follows:

Ignoring line 16630 in mapping file 'pdftex.map': Unknown token '<MinLibBol'
Ignoring line 16631 in mapping file 'pdftex.map': Unknown token '<MinLibBol'
Ignoring line 16632 in mapping file 'pdftex.map': Unknown token '<MinLibBol'
Ignoring line 16633 in mapping file 'pdftex.map': Unknown token '<MinLibBolIta'
Ignoring line 16634 in mapping file 'pdftex.map': Unknown token '<MinLibBolIta'
Ignoring line 16635 in mapping file 'pdftex.map': Unknown token '<MinLibBolIta'
Ignoring line 16636 in mapping file 'pdftex.map': Unknown token '<MinLibIta'
Ignoring line 16637 in mapping file 'pdftex.map': Unknown token '<MinLibIta'
Ignoring line 16638 in mapping file 'pdftex.map': Unknown token '<MinLibIta'
Ignoring line 16639 in mapping file 'pdftex.map': Unknown token '<MinLibReg'
Ignoring line 16640 in mapping file 'pdftex.map': Unknown token '<MinLibReg'
Ignoring line 16641 in mapping file 'pdftex.map': Unknown token '<MinLibReg'
Traceback (most recent call last):
  File "test.py", line 6, in <module>
    c.writePDFfile("test.pdf")
  File "/usr/lib/python3/dist-packages/pyx/canvas.py", line 50, in
wrappedindocument
    return method(d, file, **write_kwargs)
  File "/usr/lib/python3/dist-packages/pyx/document.py", line 193, in
writePDFfile
    pdfwriter.PDFwriter(self, f, **kwargs)
  File "/usr/lib/python3/dist-packages/pyx/pdfwriter.py", line 322, in __init__
    catalog = PDFcatalog(document, self, registry)
  File "/usr/lib/python3/dist-packages/pyx/pdfwriter.py", line 143, in __init__
    self.PDFpages = PDFpages(document, writer, registry)
  File "/usr/lib/python3/dist-packages/pyx/pdfwriter.py", line 208, in __init__
    page = PDFpage(page, pageno, self, writer, registry)
  File "/usr/lib/python3/dist-packages/pyx/pdfwriter.py", line 242, in __init__
    self.PDFcontent = PDFcontent(page, writer, self.pageregistry)
  File "/usr/lib/python3/dist-packages/pyx/pdfwriter.py", line 274, in __init__
    page.processPDF(contentfile, awriter, acontext, registry, self.bbox)
  File "/usr/lib/python3/dist-packages/pyx/document.py", line 135, in processPDF
    self._process("processPDF", *args)
  File "/usr/lib/python3/dist-packages/pyx/document.py", line 129, in _process
    getattr(cc, processMethod)(contentfile, writer, context, registry, bbox)
  File "/usr/lib/python3/dist-packages/pyx/canvas.py", line 238, in processPDF
    item.processPDF(file, writer, context, registry, nbbox)
  File "/usr/lib/python3/dist-packages/pyx/text.py", line 887, in processPDF
    self.dvicanvas.processPDF(file, writer, context, registry, abbox)
  File "/usr/lib/python3/dist-packages/pyx/canvas.py", line 238, in processPDF
    item.processPDF(file, writer, context, registry, nbbox)
  File "/usr/lib/python3/dist-packages/pyx/dvi/texfont.py", line 193,
in processPDF
    self._text(writer).processPDF(file, writer, context, registry, bbox)
  File "/usr/lib/python3/dist-packages/pyx/dvi/texfont.py", line 179, in _text
    mapline = self.font.getMAPline(writer.getfontmap())
  File "/usr/lib/python3/dist-packages/pyx/dvi/texfont.py", line 134,
in getMAPline
    raise RuntimeError("missing font information for '%s'; check
fontmapping file(s)" % self.name)
RuntimeError: missing font information for 'ecrm1000'; check fontmapping file(s)

Selected output from dpkg -l | grep ii texlive:

ii  texlive-base                               2017.20180305-1
                         all          TeX Live: Essential programs and
files
[...]
ii  texlive-fonts-extra                        2017.20180305-2
                         all          TeX Live: Additional fonts
[...]
ii  texlive-fonts-recommended                  2017.20180305-1
                         all          TeX Live: Recommended fonts
[...]

Output of locate ecrm1000:
/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/ecrm1000.mf
/usr/share/texlive/texmf-dist/fonts/tfm/jknappen/ec/ecrm1000.tfm

Output of cat /etc/lsb-release:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"

I read the PyX FAQ, which has an entry about cmr10 in it.  This error
looks different, but just in case...

Output of kpsewhich cmr10.pfb
/usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb

-- 
Tony (echo 'spend!,pocket awide' | sed 'y/acdeikospntw!, /l...@om...i/')

Re: [PyX-user] (no subject)

[André W. <co...@wo...>]

Hi,

PyX 0.14.1 or PyX 0.15 ... should not make any difference. The problem 
is, that PyX has no support for time, date, or datetime axes. (It should 
be possible to change that, but for now ... sorry.)

Using xnames requires a bar axis. This has major drawbacks, like being 
positioned equal distant in the order as provided. But heck, yes, it is 
possible with just a very few changes:

1. You need a tuple, with a position on the subaxis for the "bar" value.

2. You need to set a range for the subaxes, like 0 to 1, as you do not 
have a bar style in use. (The bar would automatically request this range 
and thus work without the hustle.)

This means, the following works:

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

ts=['13:00','13:15','13:30','13:45','14:00','14:15','14:30']
tsm=[(x, 0.5) for x in ts]

waittime = [560, 580, 540, 800, 1000, 600, 560]

attrs = [color.gradient.RedBlue]

g = graph.graphxy(width=10, 
x=graph.axis.bar(defaultsubaxis=graph.axis.lin(min=0, max=1, 
painter=None, linkpainter=None, parter=None)), key=graph.key.key())

g.plot(graph.data.values(x=tsm, y=waittime),
        [graph.style.line(attrs),
         graph.style.symbol(graph.style.symbol.changesquare, 
symbolattrs=attrs, size=0.1)])

g.writeEPSfile("waittime")
g.writePDFfile("waittime")

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

However, I am not confident, that this a solution to go for. It might 
be, depending on your use case.

Otherwise, well, you need to convert to numbers (and back for the 
labels) yourself. :-(

Best,


André

Am 09.06.20 um 15:38 schrieb Martín Marqués:
> Hi,
> 
> 
>     and welcome to the PyX club :)
> 
> 
> Not the best way to join the club by forgetting to add a subject. :(
> 
>     The current version of PyX is 0.15 for the Fedora rpm, by the way.
>     Independent of that:
> 
> 
> Maybe because I'm still on Fedora 30. I installed the packages 
> yesterday, so seems that the last available version here. Plans to move 
> to F32 are on my TODO
> 
>     Presumably, your ts is not a list of numbers but strings (labels). You
>     probably want to convert them or use them as labels by using
>     `xname=ts` instead of `x=ts`.
> 
> 
> Oh my! Didn't have that. And yes, ts is a list of str with the time of 
> the occurrence that is stored in fulldata["waittime"]
> Now it fails in a completely different way. :-D
> 
> Code snippet with actual data to test:
> 
> ```
> ts=['13:00','13:15','13:30','13:45','14:00','14:15','14:30']
> 
> waittime = [560, 580, 540, 800, 1000, 600, 560]
> 
> attrs = [color.gradient.RedBlue]
> 
> g = graph.graphxy(width=600, key=graph.key.key())
> 
> g.plot(graph.data.values(xname=ts, y=waittime),
>         [graph.style.line(attrs),
>          graph.style.symbol(graph.style.symbol.changesquare, 
> symbolattrs=attrs, size=0.1)])
> 
> g.writeEPSfile("waittime")
> g.writePDFfile("waittime")
> ```
> 
> ```
> Traceback (most recent call last):
>    File "build_graf.py", line 61, in <module>
>      graph.style.symbol(graph.style.symbol.changesquare, 
> symbolattrs=attrs, size=0.1)])
>    File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 
> 215, in plot
>      plotitems.append(plotitem(self, d, styles))
>    File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 
> 93, in __init__
>      self.usedcolumnnames.update(set(s.columnnames(privatedata, 
> self.sharedata, graph, self.data.columnnames, self.dataaxisnames)))
>    File "/usr/lib64/python3.7/site-packages/pyx/graph/style.py", line 
> 440, in columnnames
>      raise ValueError("incomplete position information")
> ValueError: incomplete position information
> ```
> 
> Regards, Martín
> 
> -- 
> Martín Marqués
> It’s not that I have something to hide,
> it’s that I have nothing I want you to see
> 
> 
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user
> 

-- 
by _ _      _
   / \ \    / ) Dr. André Wobst, co...@wo..., https://www.wobsta.de
  / _ \ \/\/ /  wobsta GmbH, Amselweg 22, 85716 Unterschleißheim, Germany
(_/ \_)_/\_/   Office: +49 (0)89 5480 3394, Mobile: +49 (0)160 9380 4217

Re: [PyX-user] (no subject)

[Martín M. <mar...@gm...>]

Hi,


and welcome to the PyX club :)
>

Not the best way to join the club by forgetting to add a subject. :(


> The current version of PyX is 0.15 for the Fedora rpm, by the way.
> Independent of that:
>

Maybe because I'm still on Fedora 30. I installed the packages yesterday,
so seems that the last available version here. Plans to move to F32 are on
my TODO


> Presumably, your ts is not a list of numbers but strings (labels). You
> probably want to convert them or use them as labels by using
> `xname=ts` instead of `x=ts`.
>

Oh my! Didn't have that. And yes, ts is a list of str with the time of the
occurrence that is stored in fulldata["waittime"]

Now it fails in a completely different way. :-D

Code snippet with actual data to test:

```
ts=['13:00','13:15','13:30','13:45','14:00','14:15','14:30']

waittime = [560, 580, 540, 800, 1000, 600, 560]

attrs = [color.gradient.RedBlue]

g = graph.graphxy(width=600, key=graph.key.key())

g.plot(graph.data.values(xname=ts, y=waittime),
       [graph.style.line(attrs),
        graph.style.symbol(graph.style.symbol.changesquare,
symbolattrs=attrs, size=0.1)])

g.writeEPSfile("waittime")
g.writePDFfile("waittime")
```

```
Traceback (most recent call last):
  File "build_graf.py", line 61, in <module>
    graph.style.symbol(graph.style.symbol.changesquare, symbolattrs=attrs,
size=0.1)])
  File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 215,
in plot
    plotitems.append(plotitem(self, d, styles))
  File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 93, in
__init__
    self.usedcolumnnames.update(set(s.columnnames(privatedata,
self.sharedata, graph, self.data.columnnames, self.dataaxisnames)))
  File "/usr/lib64/python3.7/site-packages/pyx/graph/style.py", line 440,
in columnnames
    raise ValueError("incomplete position information")
ValueError: incomplete position information
```

Regards, Martín

-- 
Martín Marqués
It’s not that I have something to hide,
it’s that I have nothing I want you to see

Re: [PyX-user] (no subject)

[Michael J G. <mic...@us...>]

Hi there,

and welcome to the PyX club :)

The current version of PyX is 0.15 for the Fedora rpm, by the way.
Independent of that:

Presumably, your ts is not a list of numbers but strings (labels). You
probably want to convert them or use them as labels by using
`xname=ts` instead of `x=ts`.

Cheers
Michael

Am Di., 9. Juni 2020 um 14:35 Uhr schrieb Martín Marqués
<mar...@gm...>:
>
> Hi,
>
> I'm building my first scripts with PyX trying to replace my old bash + gnuplot scripts. Most of my work moves around plotting output from log files that are sent to me so I can get a graphical idea of what's happening.
>
> I want to plot graphs with time span on the x axis and numerical values (number of transactions, number of connections, etc.) on the y axis.
>
> This is what I have so far. Each entry from the fulldata dictionary and the ts list have exactly the same len() and are all lists. This is an example with the 'waittime' entry, but same thing happens with any entry of the dictionary:
>
> ```
> attrs = [color.gradient.RedBlue]
>
> g = graph.graphxy(width=600, key=graph.key.key())
>
> g.plot(graph.data.values(x=ts, y=fulldata["waittime"]),
>        [graph.style.line(attrs),
>         graph.style.symbol(graph.style.symbol.changesquare, symbolattrs=attrs, size=0.1)])
>
> g.writeEPSfile("waittime")
> g.writePDFfile("waittime")
> ```
>
> On running this I get the following error:
>
> ```
> Traceback (most recent call last):
>   File "build_graf.py", line 59, in <module>
>     g.writeEPSfile("waittime")
>   File "/usr/lib64/python3.7/site-packages/pyx/canvas.py", line 50, in wrappedindocument
>     return method(d, file, **write_kwargs)
>   File "/usr/lib64/python3.7/site-packages/pyx/document.py", line 185, in writeEPSfile
>     pswriter.EPSwriter(self, f, **kwargs)
>   File "/usr/lib64/python3.7/site-packages/pyx/pswriter.py", line 142, in __init__
>     page.processPS(pagefile, self, acontext, registry, pagebbox)
>   File "/usr/lib64/python3.7/site-packages/pyx/document.py", line 132, in processPS
>     self._process("processPS", *args)
>   File "/usr/lib64/python3.7/site-packages/pyx/document.py", line 78, in _process
>     bbox.set(self.canvas.bbox()) # this bbox is not accurate
>   File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 181, in bbox
>     self.finish()
>   File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 303, in finish
>     self.doaxes()
>   File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 580, in doaxes
>     self.dolayout()
>   File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 564, in dolayout
>     self.doaxiscreate(axisname)
>   File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 240, in doaxiscreate
>     self.axes[axisname].create()
>   File "/usr/lib64/python3.7/site-packages/pyx/graph/axis/axis.py", line 591, in create
>     self.canvas = self.axis.create(self.data, self.positioner, self.graphtexrunner, self.errorname)
>   File "/usr/lib64/python3.7/site-packages/pyx/graph/axis/axis.py", line 250, in create
>     return _regularaxis._create(self, data, positioner, graphtexrunner, self.parter, self.rater, errorname)
>   File "/usr/lib64/python3.7/site-packages/pyx/graph/axis/axis.py", line 116, in _create
>     raise RuntimeError("incomplete axis range %s" % errorname)
> RuntimeError: incomplete axis range for axis x
> ```
>
> BTW, I had to fix the formatting in axis.py as there was a mistake which made the `raise` not work. Where can I send patches? I'm using rpm packages, version 0.14.1.
>
> Any help on how to fix the error from above, or better ways to build my graphs would be much appreciated. :-)
>
> Kind regards, Martín
> --
> Martín Marqués
> It’s not that I have something to hide,
> it’s that I have nothing I want you to see
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

[PyX-user] (no subject)

[Martín M. <mar...@gm...>]

Hi,

I'm building my first scripts with PyX trying to replace my old bash +
gnuplot scripts. Most of my work moves around plotting output from log
files that are sent to me so I can get a graphical idea of what's happening.

I want to plot graphs with time span on the x axis and numerical values
(number of transactions, number of connections, etc.) on the y axis.

This is what I have so far. Each entry from the fulldata dictionary and the
ts list have exactly the same len() and are all lists. This is an example
with the 'waittime' entry, but same thing happens with any entry of the
dictionary:

```
attrs = [color.gradient.RedBlue]

g = graph.graphxy(width=600, key=graph.key.key())

g.plot(graph.data.values(x=ts, y=fulldata["waittime"]),
       [graph.style.line(attrs),
        graph.style.symbol(graph.style.symbol.changesquare,
symbolattrs=attrs, size=0.1)])

g.writeEPSfile("waittime")
g.writePDFfile("waittime")
```

On running this I get the following error:

```
Traceback (most recent call last):
  File "build_graf.py", line 59, in <module>
    g.writeEPSfile("waittime")
  File "/usr/lib64/python3.7/site-packages/pyx/canvas.py", line 50, in
wrappedindocument
    return method(d, file, **write_kwargs)
  File "/usr/lib64/python3.7/site-packages/pyx/document.py", line 185, in
writeEPSfile
    pswriter.EPSwriter(self, f, **kwargs)
  File "/usr/lib64/python3.7/site-packages/pyx/pswriter.py", line 142, in
__init__
    page.processPS(pagefile, self, acontext, registry, pagebbox)
  File "/usr/lib64/python3.7/site-packages/pyx/document.py", line 132, in
processPS
    self._process("processPS", *args)
  File "/usr/lib64/python3.7/site-packages/pyx/document.py", line 78, in
_process
    bbox.set(self.canvas.bbox()) # this bbox is not accurate
  File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 181,
in bbox
    self.finish()
  File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 303,
in finish
    self.doaxes()
  File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 580,
in doaxes
    self.dolayout()
  File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 564,
in dolayout
    self.doaxiscreate(axisname)
  File "/usr/lib64/python3.7/site-packages/pyx/graph/graph.py", line 240,
in doaxiscreate
    self.axes[axisname].create()
  File "/usr/lib64/python3.7/site-packages/pyx/graph/axis/axis.py", line
591, in create
    self.canvas = self.axis.create(self.data, self.positioner,
self.graphtexrunner, self.errorname)
  File "/usr/lib64/python3.7/site-packages/pyx/graph/axis/axis.py", line
250, in create
    return _regularaxis._create(self, data, positioner, graphtexrunner,
self.parter, self.rater, errorname)
  File "/usr/lib64/python3.7/site-packages/pyx/graph/axis/axis.py", line
116, in _create
    raise RuntimeError("incomplete axis range %s" % errorname)
RuntimeError: incomplete axis range for axis x
```

BTW, I had to fix the formatting in axis.py as there was a mistake which
made the `raise` not work. Where can I send patches? I'm using rpm
packages, version 0.14.1.

Any help on how to fix the error from above, or better ways to build my
graphs would be much appreciated. :-)

Kind regards, Martín
-- 
Martín Marqués
It’s not that I have something to hide,
it’s that I have nothing I want you to see

Re: [PyX-user] Hello World blows out

[Donald T. <do...@ti...>]

André,

No, I wasn't aware that I need a TeX installation.

Ah, that fixes the issue.  Thanks.

  -- Don
--
Donald Tillman, Palo Alto, California
http://www.till.com


> On May 24, 2020, at 11:42 PM, André Wobst <co...@wo...> wrote:
> 
> Dear Donald,
> 
> are you aware that you need a TeX installation? Like texlive (https://www.tug.org/texlive/)
> 
> Trying to simulate what happens without TeX being available, I just changed the name of the tex executable in my .pyxrc. The result looks a bit different, but still ... I think this could be the source of your problem.
> 
> Best,
> 
> 
> André
> 
> 
> wobsta@x1:~/pyx/dev$ python hello.py
> Platform name is: posix
> Python executable: /home/wobsta/.pyenv/versions/pyxdev/bin/python
> Python version: 3.6.9 (default, Sep  4 2019, 18:32:29)
> [GCC 8.3.0]
> PyX comes from: /home/wobsta/pyx/dev/pyx/__init__.py
> PyX version: 0.15
> pyxrc is loaded from: /home/wobsta/.pyxrc
> pykpathsea: not available
> file locators in use: local, internal, recursivedir, ls_R
> PyX executes tex_not_installed with args ['--output-directory', '/tmp/pyx1apacx7z', '--ipc'] located at None
> Traceback (most recent call last):
>  File "hello.py", line 9, in <module>
>    c.text(0, 0, r"Hello, world!")
>  File "/home/wobsta/pyx/dev/pyx/canvas.py", line 409, in text
>    return self.insert(self.textengine.text(x, y, atext, *args, **kwargs))
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1454, in wrapped
>    return f(self, *args, **kwargs)
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1490, in text
>    return self.instance.text(*args, **kwargs)
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1330, in text
>    return self.text_pt(unit.topt(x), unit.topt(y), *args, **kwargs)
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1304, in text_pt
>    left_pt, right_pt, height_pt, depth_pt = self.do_typeset(expr, self.texmessages_run_default + self.texmessages_run + texmessages)
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1221, in do_typeset
>    self.do_start()
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1370, in do_start
>    super().do_start()
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1176, in do_start
>    self.popen = config.Popen(cmd, stdin=config.PIPE, stdout=config.PIPE, stderr=config.STDOUT, bufsize=0)
>  File "/home/wobsta/pyx/dev/pyx/config.py", line 218, in Popen
>    return subprocess.Popen(cmd, *args, **kwargs)
>  File "/home/wobsta/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 729, in __init__
>    restore_signals, start_new_session)
>  File "/home/wobsta/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 1364, in _execute_child
>    raise child_exception_type(errno_num, err_msg, err_filename)
> FileNotFoundError: [Errno 2] No such file or directory: 'tex_not_installed': 'tex_not_installed'
> Error in atexit._run_exitfuncs:
> Traceback (most recent call last):
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1035, in _cleanup
>    self.do_finish(cleanup=False)
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1235, in do_finish
>    self.go_finish()
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1364, in go_finish
>    self._execute("\\end%\n", self.texmessages_end_default + self.texmessages_end, STATE_TYPESET, STATE_DONE)
>  File "/home/wobsta/pyx/dev/pyx/text.py", line 1078, in _execute
>    self.texoutput.expect(None)
> AttributeError: 'SingleTexEngine' object has no attribute 'texoutput'
> 
> 
> Am 25.05.20 um 01:22 schrieb Donald Tillman:
>> Hi folks,
>> I'm trying PyX for the first time.  This is on an iMac, High Sierra, 10.13.6.
>> The third line of the Hello World demo blows out with this error:
>>>>> c.text(0, 0, "Hello, world!")
>> Traceback (most recent call last):
>>   File "<stdin>", line 1, in <module>
>>   File "/anaconda3/lib/python3.7/site-packages/pyx/canvas.py", line 409, in text
>>     return self.insert(self.textengine.text(x, y, atext, *args, **kwargs))
>>   File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1454, in wrapped
>>     return f(self, *args, **kwargs)
>>   File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1490, in text
>>     return self.instance.text(*args, **kwargs)
>>   File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1330, in text
>>     return self.text_pt(unit.topt(x), unit.topt(y), *args, **kwargs)
>>   File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1304, in text_pt
>>     left_pt, right_pt, height_pt, depth_pt = self.do_typeset(expr, self.texmessages_run_default + self.texmessages_run + texmessages)
>>   File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1224, in do_typeset
>>     return self._execute(expr, texmessages, STATE_TYPESET, STATE_TYPESET)
>>   File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1091, in _execute
>>     self.texoutput.expect("PyXInputMarker:executeid=%i:" % self.executeid)
>> AttributeError: 'SingleTexEngine' object has no attribute 'texoutput'
>> Perhaps there's some secret step I've missed?
>> Thanks!
>>>>> pyxinfo()
>> Platform name is: posix
>> Python executable: /anaconda3/bin/python
>> Python version: 3.7.3 (default, Mar 27 2019, 16:54:48)
>> [Clang 4.0.1 (tags/RELEASE_401/final)]
>> PyX comes from: /anaconda3/lib/python3.7/site-packages/pyx/__init__.py
>> PyX version: 0.15
>> pyxrc would be loaded from: /Users/till/.pyxrc
>> pykpathsea: not available
>> file locators in use: local, internal, pykpathsea, kpsewhich
>>   -- Don
> -- 
> by _ _      _
>  / \ \    / ) Dr. André Wobst, co...@wo..., https://www.wobsta.de
> / _ \ \/\/ /  wobsta GmbH, Amselweg 22, 85716 Unterschleißheim, Germany
> (_/ \_)_/\_/   Office: +49 (0)89 5480 3394, Mobile: +49 (0)160 9380 4217
> 

Re: [PyX-user] Hello World blows out

[André W. <co...@wo...>]

Dear Donald,

are you aware that you need a TeX installation? Like texlive 
(https://www.tug.org/texlive/)

Trying to simulate what happens without TeX being available, I just 
changed the name of the tex executable in my .pyxrc. The result looks a 
bit different, but still ... I think this could be the source of your 
problem.

Best,


André


wobsta@x1:~/pyx/dev$ python hello.py
Platform name is: posix
Python executable: /home/wobsta/.pyenv/versions/pyxdev/bin/python
Python version: 3.6.9 (default, Sep  4 2019, 18:32:29)
[GCC 8.3.0]
PyX comes from: /home/wobsta/pyx/dev/pyx/__init__.py
PyX version: 0.15
pyxrc is loaded from: /home/wobsta/.pyxrc
pykpathsea: not available
file locators in use: local, internal, recursivedir, ls_R
PyX executes tex_not_installed with args ['--output-directory', 
'/tmp/pyx1apacx7z', '--ipc'] located at None
Traceback (most recent call last):
   File "hello.py", line 9, in <module>
     c.text(0, 0, r"Hello, world!")
   File "/home/wobsta/pyx/dev/pyx/canvas.py", line 409, in text
     return self.insert(self.textengine.text(x, y, atext, *args, **kwargs))
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1454, in wrapped
     return f(self, *args, **kwargs)
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1490, in text
     return self.instance.text(*args, **kwargs)
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1330, in text
     return self.text_pt(unit.topt(x), unit.topt(y), *args, **kwargs)
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1304, in text_pt
     left_pt, right_pt, height_pt, depth_pt = self.do_typeset(expr, 
self.texmessages_run_default + self.texmessages_run + texmessages)
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1221, in do_typeset
     self.do_start()
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1370, in do_start
     super().do_start()
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1176, in do_start
     self.popen = config.Popen(cmd, stdin=config.PIPE, 
stdout=config.PIPE, stderr=config.STDOUT, bufsize=0)
   File "/home/wobsta/pyx/dev/pyx/config.py", line 218, in Popen
     return subprocess.Popen(cmd, *args, **kwargs)
   File 
"/home/wobsta/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 
729, in __init__
     restore_signals, start_new_session)
   File 
"/home/wobsta/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 
1364, in _execute_child
     raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 
'tex_not_installed': 'tex_not_installed'
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1035, in _cleanup
     self.do_finish(cleanup=False)
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1235, in do_finish
     self.go_finish()
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1364, in go_finish
     self._execute("\\end%\n", self.texmessages_end_default + 
self.texmessages_end, STATE_TYPESET, STATE_DONE)
   File "/home/wobsta/pyx/dev/pyx/text.py", line 1078, in _execute
     self.texoutput.expect(None)
AttributeError: 'SingleTexEngine' object has no attribute 'texoutput'


Am 25.05.20 um 01:22 schrieb Donald Tillman:
> Hi folks,
> 
> I'm trying PyX for the first time.  This is on an iMac, High Sierra, 10.13.6.
> 
> The third line of the Hello World demo blows out with this error:
> 
>>>> c.text(0, 0, "Hello, world!")
> Traceback (most recent call last):
>    File "<stdin>", line 1, in <module>
>    File "/anaconda3/lib/python3.7/site-packages/pyx/canvas.py", line 409, in text
>      return self.insert(self.textengine.text(x, y, atext, *args, **kwargs))
>    File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1454, in wrapped
>      return f(self, *args, **kwargs)
>    File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1490, in text
>      return self.instance.text(*args, **kwargs)
>    File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1330, in text
>      return self.text_pt(unit.topt(x), unit.topt(y), *args, **kwargs)
>    File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1304, in text_pt
>      left_pt, right_pt, height_pt, depth_pt = self.do_typeset(expr, self.texmessages_run_default + self.texmessages_run + texmessages)
>    File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1224, in do_typeset
>      return self._execute(expr, texmessages, STATE_TYPESET, STATE_TYPESET)
>    File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1091, in _execute
>      self.texoutput.expect("PyXInputMarker:executeid=%i:" % self.executeid)
> AttributeError: 'SingleTexEngine' object has no attribute 'texoutput'
> 
> Perhaps there's some secret step I've missed?
> 
> Thanks!
> 
>>>> pyxinfo()
> Platform name is: posix
> Python executable: /anaconda3/bin/python
> Python version: 3.7.3 (default, Mar 27 2019, 16:54:48)
> [Clang 4.0.1 (tags/RELEASE_401/final)]
> PyX comes from: /anaconda3/lib/python3.7/site-packages/pyx/__init__.py
> PyX version: 0.15
> pyxrc would be loaded from: /Users/till/.pyxrc
> pykpathsea: not available
> file locators in use: local, internal, pykpathsea, kpsewhich
> 
>    -- Don
> --
> Donald Tillman, Palo Alto, California
> http://www.till.com
> 
> 
> 
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user
> 

-- 
by _ _      _
   / \ \    / ) Dr. André Wobst, co...@wo..., https://www.wobsta.de
  / _ \ \/\/ /  wobsta GmbH, Amselweg 22, 85716 Unterschleißheim, Germany
(_/ \_)_/\_/   Office: +49 (0)89 5480 3394, Mobile: +49 (0)160 9380 4217

[PyX-user] Hello World blows out

[Donald T. <do...@ti...>]

Hi folks,

I'm trying PyX for the first time.  This is on an iMac, High Sierra, 10.13.6.

The third line of the Hello World demo blows out with this error:

>>> c.text(0, 0, "Hello, world!")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/anaconda3/lib/python3.7/site-packages/pyx/canvas.py", line 409, in text
    return self.insert(self.textengine.text(x, y, atext, *args, **kwargs))
  File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1454, in wrapped
    return f(self, *args, **kwargs)
  File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1490, in text
    return self.instance.text(*args, **kwargs)
  File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1330, in text
    return self.text_pt(unit.topt(x), unit.topt(y), *args, **kwargs)
  File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1304, in text_pt
    left_pt, right_pt, height_pt, depth_pt = self.do_typeset(expr, self.texmessages_run_default + self.texmessages_run + texmessages)
  File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1224, in do_typeset
    return self._execute(expr, texmessages, STATE_TYPESET, STATE_TYPESET)
  File "/anaconda3/lib/python3.7/site-packages/pyx/text.py", line 1091, in _execute
    self.texoutput.expect("PyXInputMarker:executeid=%i:" % self.executeid)
AttributeError: 'SingleTexEngine' object has no attribute 'texoutput'

Perhaps there's some secret step I've missed?

Thanks!

>>> pyxinfo()
Platform name is: posix
Python executable: /anaconda3/bin/python
Python version: 3.7.3 (default, Mar 27 2019, 16:54:48) 
[Clang 4.0.1 (tags/RELEASE_401/final)]
PyX comes from: /anaconda3/lib/python3.7/site-packages/pyx/__init__.py
PyX version: 0.15
pyxrc would be loaded from: /Users/till/.pyxrc
pykpathsea: not available
file locators in use: local, internal, pykpathsea, kpsewhich

  -- Don
--
Donald Tillman, Palo Alto, California
http://www.till.com

Re: [PyX-user] Fonts: how to use Helvetica from the default PDF library?

[Gert-Ludwig I. <ger...@ph...>]

Dear Maarten,

>         Pyx.text.set(Pyx.text.LatexEngine, texenc='utf-8')
>         Pyx.text.preamble(r"\usepackage{helvetica}”)

Give \usepackage{helvet} a try.

> _And another question_,… /how can I use the diameter symbol from LaTex?/
> \times and \cdot work, føreing chåracters too, but the \diameter symbol
> yields:

Take a look at
http://tug.ctan.org/info/symbols/comprehensive/symbols-a4.pdf . There
exist various fonts providing the diameter symbol in slightly different
form.

Best regards,
Gert

-- 
 Gert-Ludwig Ingold     email: Gert.Ingold@Physik.Uni-Augsburg.DE
 Institut für Physik    Phone: +49-821-598-3234
 Universität Augsburg   Fax  : +49-821-598-3222
 D-86135 Augsburg       WWW  : www.physik.uni-augsburg.de/theo1/ingold
 Germany                PGP  : 86FF5A93, key available from homepage

[PyX-user] Fonts: how to use Helvetica from the default PDF library?

[Maarten v. d. V. <m.h...@gm...>]

Dear people,

I would like to ask your help again for another issue I can’t seem to solve using the documentation and the newsletter archives. I must admit that I have practically no experience with LaTex.

Use case:
I intend to use PyX as a replacement for pyFPD, handcrafted SVG and the PIL(LOW) library. My goal is to serve custom made, free, on demand graphics.

Because of that, the font in the document should be one of the 14 Adobe standard postscript fonts, so the downloaded document can be edited in, say, Illustrator. 

Problem:
I can find out how I should do this. How can use Helvetica as the standard font for my documents?

What I tried:

        Pyx.text.set(Pyx.text.LatexEngine, texenc='utf-8')
        Pyx.text.preamble(r"\usepackage{helvetica}”)

This makes, seemingly, crash LaTex. Flask says: "Still waiting for LaTeX after 5 (of 60) seconds…”.

And another question,… how can I use the diameter symbol from LaTex? \times and \cdot work, føreing chåracters too, but the \diameter symbol yields:

  *! Undefined control sequence.

Thanks again in advance,

Maarten

Re: [PyX-user] Multi Page documents

[Maarten v. d. V. <m.h...@gm...>]

Dear Gert, Michael,

_Vielen Dank_ for your help. Both your suggestions worked!

Maarten


> On 7 May 2020, at 15:44, Michael J Gruber <mic...@us...> wrote:
> 
> Hi Marten,
> 
> I guess you did not quite follow through the thread you cited. the
> following should be as close to your code as possible but working :)
> 
> from pyx import *
> c = canvas.canvas()
> c.text(0, 0, "Hello, world!")
> c.stroke(path.line(0, 0, 2, 0))
> page = document.page(c, paperformat = document.paperformat.Letter)
> result = document.document([page,])
> result.writePSfile("Whatever")
> 
> Cheers
> Michael
> 
> Am Do., 7. Mai 2020 um 15:02 Uhr schrieb Maarten van der Velde
> <m.h...@gm...>:
>> 
>> Dear all,
>> 
>> I wonder if you can help me.
>> 
>> I would like to create multi page documents in Pyx. I am browsing through the documentation and the mailing list archive, but I am not able to connect all the pieces of information.
>> 
>> I have tried following along:
>> 
>> https://sourceforge.net/p/pyx/mailman/message/6193313/
>> 
>> c = canvas.canvas()
>> c.text(0, 0, "Hello, world!")
>> c.stroke(path.line(0, 0, 2, 0))
>> 
>> page = document.page(c, paperformat=paperformat.Letter)
>> 
>> result = canvas.document(c)
>> result.writePSfile("Whatever")
>> 
>> But this gives me the error:
>> 
>> AttributeError: 'Document' object has no attribute ‘page'
>> 
>> Did the package change since this thread? (2007…) Is there a working example somewhere that I could use instead?
>> 
>> Thanks,
>> 
>> Maarten
>> _______________________________________________
>> PyX-user mailing list
>> PyX...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyx-user

Re: [PyX-user] Multi Page documents

[Michael J G. <mic...@us...>]

Hi Marten,

I guess you did not quite follow through the thread you cited. the
following should be as close to your code as possible but working :)

from pyx import *
c = canvas.canvas()
c.text(0, 0, "Hello, world!")
c.stroke(path.line(0, 0, 2, 0))
page = document.page(c, paperformat = document.paperformat.Letter)
result = document.document([page,])
result.writePSfile("Whatever")

Cheers
Michael

Am Do., 7. Mai 2020 um 15:02 Uhr schrieb Maarten van der Velde
<m.h...@gm...>:
>
> Dear all,
>
> I wonder if you can help me.
>
> I would like to create multi page documents in Pyx. I am browsing through the documentation and the mailing list archive, but I am not able to connect all the pieces of information.
>
> I have tried following along:
>
> https://sourceforge.net/p/pyx/mailman/message/6193313/
>
> c = canvas.canvas()
> c.text(0, 0, "Hello, world!")
> c.stroke(path.line(0, 0, 2, 0))
>
> page = document.page(c, paperformat=paperformat.Letter)
>
> result = canvas.document(c)
> result.writePSfile("Whatever")
>
> But this gives me the error:
>
> AttributeError: 'Document' object has no attribute ‘page'
>
> Did the package change since this thread? (2007…) Is there a working example somewhere that I could use instead?
>
> Thanks,
>
> Maarten
> _______________________________________________
> PyX-user mailing list
> PyX...@li...
> https://lists.sourceforge.net/lists/listinfo/pyx-user

Re: [PyX-user] Multi Page documents

[Gert-Ludwig I. <ger...@ph...>]

Dear Maarten,

You might want to take a look at
https://pyx-project.org/pyxfaq/general_aspects_plotting.html#how-do-i-generate-multipage-output
.

I just verified that it is still running with an up-to-date PyX
installation (provided you remove the backslash in unit.t\_cm which
should never have been there).

Best regards,
Gert

-- 
 Gert-Ludwig Ingold     email: Gert.Ingold@Physik.Uni-Augsburg.DE
 Institut für Physik    Phone: +49-821-598-3234
 Universität Augsburg   Fax  : +49-821-598-3222
 D-86135 Augsburg       WWW  : www.physik.uni-augsburg.de/theo1/ingold
 Germany                PGP  : 86FF5A93, key available from homepage

[PyX-user] Multi Page documents

[Maarten v. d. V. <m.h...@gm...>]

Dear all,

I wonder if you can help me.

I would like to create multi page documents in Pyx. I am browsing through the documentation and the mailing list archive, but I am not able to connect all the pieces of information. 

I have tried following along:

https://sourceforge.net/p/pyx/mailman/message/6193313/ <https://sourceforge.net/p/pyx/mailman/message/6193313/>

c = canvas.canvas()
c.text(0, 0, "Hello, world!")
c.stroke(path.line(0, 0, 2, 0))

page = document.page(c, paperformat=paperformat.Letter)

result = canvas.document(c)
result.writePSfile("Whatever")
But this gives me the error:

AttributeError: 'Document' object has no attribute ‘page'

Did the package change since this thread? (2007…) Is there a working example somewhere that I could use instead?

Thanks,

Maarten