belinda thom wrote:
[...]
Here's more info (redundant?) regarding what I've tried, in case it
clarifies. (Ultimately, I will obviously need to upgrade to 0.9, at
which point I can report back on if this fixed the problem on my
machine, but I can't do that until after the semester is
belinda thom wrote:
Thanks Eric!
I'm kind of afraid to upgrade to the SVN version b/c I fear something
else might break (I've yet to install matplotlib from source b/c of a
few nagging Mac OS X issues).
What would you recommend?
I don't know; I see from your earlier message that Tim
belinda thom wrote:
Me neither :-). I will try and get permission to upgrade axis.py w/my
quick fix commenting out the kwargs in line 2131 of axes.py, as this is
the quick option and I need something ASAP. You seem to know quite a bit
about matplotlib. If you have any idea what this hack
Hi,
I'm replying to this older thread
http://www.mail-archive.com/matplotlib-users@lists.sourceforge.net/
msg02100.html
because it relates very much to my recent problem, posted at http://
www.mail-archive.com/matplotlib-users@lists.sourceforge.net/
msg03037.html. This problem seems more
On Apr 11, 2007, at 4:47 PM, belinda thom wrote:
Hi,
I'm replying to this older thread
http://www.mail-archive.com/matplotlib-users@lists.sourceforge.net/
msg02100.html
because it relates very much to my recent problem, posted at http://
Belinda,
John has checked in some fixes for axes3d recently, and your test code
now runs with the version in svn--except for the problem that you should
use P.show() only once in a given script. (I think there is some
backend for which you can get away with using it more than once, but
this
Thanks Eric!
I'm kind of afraid to upgrade to the SVN version b/c I fear something
else might break (I've yet to install matplotlib from source b/c of a
few nagging Mac OS X issues).
What would you recommend?
There's also the issue of having to upgrade student machines for
which I'm not
Hi,
the same problem occurred, when I also tried to plot some chaos systems
the solution I found (and works just fine) is to comment axes.py:2131
I didn't send a patch, 'cos I'm not sure that it wasn't really an
common bug (I played with my overall python distribution)
some OT:
1) trajectories -
