problem with the PS-backend in matplotlib 0.64

Hello, I am very sorry about this, but I messed up the PS

    > backend shortly before the release :frowning: While trying to
    > move a block of code I duplicated it instead. The
    > consequence is, that PostScript files generated with
    > matplotlib 0.64 draw every bit of the figure twice. The
    > output is still ok, but it is generated in an inefficient
    > way.

    > Luckily at least the huge PostScript fonts are only
    > included once.

    > Again, I am very sorry about this, Jochen --

No worries, we're used to doing bug fix releases around here. Better
that you caught it than some irate gnuplot user who comes around here
complaining about matplotlib's PS file sizes :slight_smile:

Just commit the patch and in a few days as we iron out any remaining
bugs that are discovered I'll post a bug fix release.

JDH

Hello John,

No worries, we're used to doing bug fix releases around here. Better
that you caught it than some irate gnuplot user who comes around here
complaining about matplotlib's PS file sizes :slight_smile:

Well, everything is of course still dominated by the huge included
fonts, so they will probably not notice :wink: Maybe I can start doing
something about this during the week-end. Let's see ...

Just commit the patch and in a few days as we iron out any remaining
bugs that are discovered I'll post a bug fix release.

The patch is already in CVS.

I have another (more intrusive) patch ready, which strips down the
PostScript file size even more by removing about 20 million
gsave/grestore pairs per figure. I tried the backend_driver script
and the patch seems to work. Can I also check this in, or should I be
stabilising the PostScript backend at the moment?

All the best,
Jochen

···

On Thu, Nov 11, 2004 at 08:12:00AM -0600, John Hunter wrote:
--

John Hunter wrote:

"Jochen" == Jochen Voss <voss@...7...> writes:

    > Hello, I am very sorry about this, but I messed up the PS
    > backend shortly before the release :frowning: While trying to

[...]

No worries, we're used to doing bug fix releases around here. Better
that you caught it than some irate gnuplot user who comes around here
complaining about matplotlib's PS file sizes :slight_smile:

hey! I was nice when I asked! :wink:

Best,

f