I see.
I only checked that the code in hist() hadn't changed. I guess it pays
to be thorough. Hope this didn't waste too much time.
Cheers,
Scott
>>> Eric Firing <[EMAIL PROTECTED]> 4/30/2007 20:02 >>>
Scott,
In svn, barh does accept the 'log' kwarg via **kwargs, and your example
works corr
In http://matplotlib.sourceforge.net/tutorial.html
the following link is brocken :
http://matplotlib.sourceforge.net/pylab.html#-rc
(in "Customizing matplotlib" part)
therefore, it is difficult to get information about rc...
What does one have to install from the command line to fix this? I'm getting
the same error running the basemap examples, after installing matplotlib
0.90 via egg and basemap via installer, and numpy via source.
Traceback (most recent call last):
File "simpletest.py", line 1, in
from matpl
Darren Dale wrote:
> On Monday 30 April 2007 02:31:59 pm Eric Firing wrote:
>> One way this could happen is if the .matplotlib directory exists but is
>> not writable; such a case would give the error traceback you see with
>> little clue as to what and where the problem really is. So, __init__.py
Hi Eric,
Thanks for your response.
> One way this could happen is if the .matplotlib directory exists
> but is not writable; such a case would give the error traceback you
> see with little clue as to what and where the problem really is.
> So, __init__.py certainly could be improved.
On Monday 30 April 2007 02:31:59 pm Eric Firing wrote:
> One way this could happen is if the .matplotlib directory exists but is
> not writable; such a case would give the error traceback you see with
> little clue as to what and where the problem really is. So, __init__.py
> certainly could be im
Try building it with g++. Generally you should be able to set
the env variable CC to g++ but I think distutils in python 2.3
does not look at the environment variables and you may need to tweak
python2.3/config/Makefile to use g++ instead of Sun's cc.
I may be wrong.
Later versions of python respec
One way this could happen is if the .matplotlib directory exists but is
not writable; such a case would give the error traceback you see with
little clue as to what and where the problem really is. So, __init__.py
certainly could be improved. (Offhand, I don't even know why the
existence of s
Scott,
In svn, barh does accept the 'log' kwarg via **kwargs, and your example
works correctly. Here is the relevant CHANGELOG entry, after 0.90 was
released:
2007-03-03 Change barh to take a kwargs dict and pass it to bar.
Fixes sf bug #1669506.
I think it was just a matter of c
Hi all,
I recently run into a problem with the .matplotlib directory. I run a
script as a daemon, that in its turn runs several scripts to create
graphs (often the same script with different input parameters),
dependent on an outside trigger. Recently, I found that these script
crashed
Hi,
The following code fails for me with matplotlib-0.90.0 --
---
import pylab as pl
x = pl.randn(1000)
pl.hist(x, orientation='horizontal')
pl.show()
---
This is because Axes.barh() [called
On 4/30/07, Gonzalo A. de la Vega <[EMAIL PROTECTED]> wrote:
> Hi all,
> I'm trying to embed a polar plot into a glade gui. I modified the
> mpl_with_glade.py example script to have something to start with. No
> problems with normal plot, but when I try to do polar plot, it fails with
> the followi
Claudio <[EMAIL PROTECTED]> writes:
> Is there any way i can handle the size (without having to actually
> modify the whole system through config file)?
Yes, the size keyword:
> xticks(ind, colors.keys())
xticks(ind, colors.keys(), size='smaller')
The possible values of size are listed at
http
Hello.
I'm writing for a question about the bar() object. My problem is that I
have to write long labels to the ticks to indicate the bins' meaning but
they are overlapping one onto another. Is there any way i can handle the
size (without having to actually modify the whole system through config
fi
14 matches
Mail list logo
