On Thu, Jul 29, 2010 at 6:17 PM, Benjamin Root ben.r...@ou.edu wrote:
As a side-note, it looks like various files that have been changed due to
svnmerge.py are still showing themselves as having their properties
modified. Is this ok?
Yes, for some reason some of the files, like axes3d
On Sun, Jul 25, 2010 at 3:51 PM, Benjamin Root ben.r...@ou.edu wrote:
On Tue, Jul 20, 2010 at 9:21 AM, Jeff Klukas klu...@wisc.edu wrote:
Hello,
The documentation for hist seems to indicate that you should be able
to send a list of values through the 'weights' parameter in axes.hist,
and
On 07/29/2010 09:31 AM, Benjamin Root wrote:
[...]
Good catch, Jeff. Looking over the code, looks like both the input
data, x, and the weights get similar pre-processing done to ready it
for histogramming. It appears that a fix was made to how x was being
processed, but the
On Thu, Jul 29, 2010 at 3:39 PM, Eric Firing efir...@hawaii.edu wrote:
On 07/29/2010 09:31 AM, Benjamin Root wrote:
[...]
Good catch, Jeff. Looking over the code, looks like both the input
data, x, and the weights get similar pre-processing done to ready it
for
On 07/29/2010 01:17 PM, Benjamin Root wrote:
On Thu, Jul 29, 2010 at 3:39 PM, Eric Firing efir...@hawaii.edu
mailto:efir...@hawaii.edu wrote:
On 07/29/2010 09:31 AM, Benjamin Root wrote:
[...]
Good catch, Jeff. Looking over the code, looks like both the
input
On Tue, Jul 20, 2010 at 9:21 AM, Jeff Klukas klu...@wisc.edu wrote:
Hello,
The documentation for hist seems to indicate that you should be able
to send a list of values through the 'weights' parameter in axes.hist,
and this worked in previous versions. In 1.0, however, this produces
an
Hello,
The documentation for hist seems to indicate that you should be able
to send a list of values through the 'weights' parameter in axes.hist,
and this worked in previous versions. In 1.0, however, this produces
an error. I've attached a diff (also pasted below) that I believe
produces the
