hi,
i observed a similar problem that persists in matplotlib 0.90.1 (python 2.5,
numpy 1.0.1, ipython 0.7.3).
the problem occurs when a window is closed and it seems to be specific to
the non-interactive mode using the GTK or GTKAgg backend. the following
short script runs ok once, but when i
Hi,
I've been using matplotlib for a little while and am finding it very
useful. Yesterday, though, I hit a problem:
Because I didn't read the docs properly, I tried to use
matplotlib.transforms.scale_transform
like this:
t = scale_transform(1.0, 2.0)
but then I got a core-dump when
Thanks for tracking this down, Ben. Applied in svn as r3547.
Ben North wrote:
I've been using matplotlib for a little while and am finding it very
useful. Yesterday, though, I hit a problem:
-
This SF.net email is
Hi everyone,
I'm running Suse10.2 and installing packages using Yast (after much pain
trying to install Numpy and Scipy without it!). After installing (and
re-installing) Matplotlib in this way, I get the error,
ImportError: matplotlib/ft2font.so: undefined symbol: PyUnicodeUCS4_GetSize
when I
Hi,
The normal rectangular Axes class and the derived PolarAxes class both
have set_xlim() and set_ylim() functions, but the rectangular Axes class
has a default value of False for the 'emit' argument, whereas the
PolarAxes version has True. I had a figure containing three Axes
instances,
I recently ran into a similar problem myself building stuff from source,
but I'm not sure of the specifics with SuSE and their packages etc.
Python can be configured in two ways -- with two-byte (UCS2) or
four-byte (UCS4) Unicode characters. Apparently the default for a
source installation of
On 7/17/07, Ben North [EMAIL PROTECTED] wrote:
Hi,
The normal rectangular Axes class and the derived PolarAxes class both
have set_xlim() and set_ylim() functions, but the rectangular Axes class
has a default value of False for the 'emit' argument, whereas the
PolarAxes version has True.
Hi,
There is a difference in the behaviour of Axes.hlines() vs
Axes.vlines(), in that vlines() lets you supply scalars for ymin and
ymax, whereas hlines() doesn't (for xmin and xmax). The patch below
fixes that, and also what looks like a separate bug in vlines. There
are also other
For some reason, builds from SVN dont install either pytz
or dateutil (at least not in the right place). Importing pylab
from these builds results in an import error.
How can I build these so as to convince these modules to
install correctly?
Thanks.
Hello,
I wrote a message some weeks ago about a problem I have with pylab,
but I think I probably did not explained it very well.
I am witting a small application that use tkFileDialog to prompt user
to select a file.
Then reads it and plot the data.
I want that the user could be able to press a
On 7/17/07, Ben North [EMAIL PROTECTED] wrote:
There is a difference in the behaviour of Axes.hlines() vs
Axes.vlines(), in that vlines() lets you supply scalars for ymin and
ymax, whereas hlines() doesn't (for xmin and xmax). The patch below
fixes that, and also what looks like a separate
On Tuesday 17 July 2007 12:04:54 pm John Hunter wrote:
I was wondering, though, whether there'd be any support for some work
which tidied up the near-duplicate code in axes.py. I've been playing
Certainly, but probably not using meta-classes.
around with an approach using python's
On 7/17/07, Chris Fonnesbeck [EMAIL PROTECTED] wrote:
For some reason, builds from SVN dont install either pytz
or dateutil (at least not in the right place). Importing pylab
from these builds results in an import error.
How can I build these so as to convince these modules to
install
13 matches
Mail list logo
