Both of these issues seem to be resolved by the latest fink packages.
-gideon
On Nov 7, 2008, at 10:13 AM, Gideon Simpson wrote:
> 1. I find that the eps's generated, for whatever reason, do not
> automatically conform to something that Preview.app can open. it
> generates the error:
>
> PostSc
Gideon Simpson <[EMAIL PROTECTED]> writes:
>> It looks like it is happening in dviread. Just to make sure this is
>> the culprit, could you temporarily disable usetex in your
>> matplotlibrc file and see if the error goes away?
>
> yes that seems to work. there are no errors when i don't use the
yes that seems to work. there are no errors when i don't use the tex.
-gideon
On Nov 7, 2008, at 1:59 PM, Jouni K. Seppänen wrote:
> Gideon Simpson <[EMAIL PROTECTED]> writes:
>
>> Verbose output attached:
>
> It looks like it is happening in dviread. Just to make sure this is
> the
> culprit,
Gideon Simpson <[EMAIL PROTECTED]> writes:
> Verbose output attached:
It looks like it is happening in dviread. Just to make sure this is the
culprit, could you temporarily disable usetex in your matplotlibrc file
and see if the error goes away?
--
Jouni K. Seppänen
http://www.iki.fi/jks
Verbose output attached:
debug.out
Description: Binary data
-gideon
On Nov 7, 2008, at 1:30 PM, Jouni K. Seppänen wrote:
Gideon Simpson <[EMAIL PROTECTED]> writes:
1. I find that the eps's generated, for whatever reason, do not
automatically conform to something that Preview.app can op
Gideon Simpson <[EMAIL PROTECTED]> writes:
> 1. I find that the eps's generated, for whatever reason, do not
> automatically conform to something that Preview.app can open. it
> generates the error:
>
> PostScript Conversion Error
> The PostScript file "test.eps" could not be converted to a
1. I find that the eps's generated, for whatever reason, do not
automatically conform to something that Preview.app can open. it
generates the error:
PostScript Conversion Error
The PostScript file "test.eps" could not be converted to a PDF file.
However, the eps's are fundamentally there.
On Nov 20, 2007 10:43 AM, Jordan Atlas <[EMAIL PROTECTED]> wrote:
> Can someone recomend a way to save the data in such a way that the
> columns (or rows) are labeled? In otherwords, it would be nice to be
> able to open the saved data and know what each row is without having to
> refer to the sc
Can someone recomend a way to save the data in such a way that the
columns (or rows) are labeled? In otherwords, it would be nice to be
able to open the saved data and know what each row is without having to
refer to the script that created it. (referring to the creating script
feels error p
On Nov 16, 2007 2:54 PM, Mark Bakker <[EMAIL PROTECTED]> wrote:
> Erik -
>
> You write that adding a 'save' is difficult.
> I can see it is involved, but don't quite see how it is specifically
> difficult.
> The way I see it, every item that is added to a figure needs a method
> to write itself to
Erik -
You write that adding a 'save' is difficult.
I can see it is involved, but don't quite see how it is specifically difficult.
The way I see it, every item that is added to a figure needs a method
to write itself to a file. So you loop through all lines, polygons,
and such, and write them to
Jordan Atlas wrote:
> Hello,
>
> Is it possible to 'save' a matplotlib figure object using something
> like the python pickle module? Basically, I'd like to save the 'figure'
> as a file so that I can open it and manipulate it if something is
> wrong. Alternative suggestions are welcome.
Hello,
Is it possible to 'save' a matplotlib figure object using something
like the python pickle module? Basically, I'd like to save the 'figure'
as a file so that I can open it and manipulate it if something is
wrong. Alternative suggestions are welcome.
Thank you,
--Jordan Atlas
---
13 matches
Mail list logo
