Hi folks,
reposting... has anyone a clue that might help in the right direction??
was my question too hard or would it help better if I rephrased it ?
thanks so much
maser
maser rati <[EMAIL PROTECTED]> wrote: Hi Folks,
I was wondering how to set the Matplotlib classic To
Self follow-up:
Rolled back to visual 0.3.2.9 and the segfault with pylab is not present
there; both the visual object and pylab graph are rendered correctly.
Sorry vpython, looks like the bug is due to your new beta.
-Mark
Mark Heslep wrote:
> Version information:
> ---
Version information:
---
Vpython visual-4.beta14
In [2]: visual.__version__
Out[2]: '1.0.1'
Python 2.4.4, Fedora Core 6 updated.
python-matplotlib-0.87.7-3.fc6
Description:
A segfault is reliably produced when running vpython along with pylab /
matplotlib functions:
cut--
Christopher Barker wrote:
> Gary Ruben wrote:
>> I just picked up a problem posted over on the numpy list. I noticed that
>> from pylab import * is importing the oldnumeric-wrapper versions of
>> zeros(), ones() and empty(), and presumably other things too, into the
>> interactive namespace. S
Well, the old trusted email [EMAIL PROTECTED] is being
retired today. It served me well for 12 years migrating from old Sun
boxes through countless linux boxes but since I'm no longer at
uchicago and the box it is running on is dying, I figured it is
finally time to give it up. That and the fact
Hi,
I'm using matplotlib in a GTK gui canvas with the GTKAgg backend. I'm
connecting a mouse click 'button_press_event' to the click function. If
I choose print event.x everything works fine. However I'm after the x
value in terms of the x-axis not pixels. When I try print event.xdata I
ge
On 1/31/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
Chris Fonnesbeck wrote:
> I have built a
> matplotlib installer for OS X,
Sorry I can't help with your problem, but:
Which Python are you building against?
Which num* are you including
Which wxPython?
Which other back-ends.
Active
Chris Fonnesbeck wrote:
> I have built a
> matplotlib installer for OS X,
Sorry I can't help with your problem, but:
Which Python are you building against?
Which num* are you including
Which wxPython?
Which other back-ends.
I'd really love to see a workable installer that we can post on python
This may not be the appropriate place to post this, but I have built a
matplotlib installer for OS X, using setupegg.py:
python setupegg.py config -L../staticlibs build bdist_mpkg
However, when I import pylab, I get the follwing:
ImportError: No module named matplotlib.pylab
The problem appears
Chris,
My guess is that you have some combination of 0.87.7 and svn; the
traceback says 0.87.7, and the KeyError is because of an addition to
rcParams since 0.87.7.
Try this:
In [1]:import matplotlib
In [2]:matplotlib.rcParams
Out[2]:
{'axes.axisbelow': False,
'axes.edgecolor': 'k',
'axes
On 1/31/07, John Hunter <[EMAIL PROTECTED]> wrote:
> "Chris" == Chris Fonnesbeck <[EMAIL PROTECTED]> writes:
Chris> The thing is, I deleted my entire ~/.matplotlib directory,
Chris> hoping to start clean. Where does matplotlib get its info
Chris> when a .matplotlibrc is not present
On 1/31/07, Chris Fonnesbeck <[EMAIL PROTECTED]> wrote:
> I am still getting this problem. Here is an ipython traceback of a very
> simple plot:
>
> In [1]: from pylab import *
Chris, try
xmode verbose
in ipython right before running your code. This will make the
traceback dump even more deta
> "Chris" == Chris Fonnesbeck <[EMAIL PROTECTED]> writes:
Chris> The thing is, I deleted my entire ~/.matplotlib directory,
Chris> hoping to start clean. Where does matplotlib get its info
Chris> when a .matplotlibrc is not present in my home directory?
It first looks in the curre
Gary Ruben wrote:
> I just picked up a problem posted over on the numpy list. I noticed that
> from pylab import * is importing the oldnumeric-wrapper versions of
> zeros(), ones() and empty(), and presumably other things too, into the
> interactive namespace. Shouldn't it be picking up the version
On 1/6/07, Eric Firing <[EMAIL PROTECTED]> wrote:
Chris,
I suspect it is a problem with your matplotlibrc file; you could try
stripping it down to bare minimum, as in the svn root directory.
Another possibility is that your update is somehow incomplete or
scrambled with an earlier installation.
I just picked up a problem posted over on the numpy list. I noticed that
from pylab import * is importing the oldnumeric-wrapper versions of
zeros(), ones() and empty(), and presumably other things too, into the
interactive namespace. Shouldn't it be picking up the versions from
numpy's main namesp
16 matches
Mail list logo
