On Saturday, February 18, 2012, Sturla Molden wrote:
>
>
> Den 18. feb. 2012 kl. 17:12 skrev Alan G Isaac
>
> >:
>
> >
> >
> > How does "stream-lined" code written for maintainability
> > (i.e., with helpful comments and tests) become *less*
> > accessible to amateurs??
>
>
> I think you missed
On Sat, Feb 18, 2012 at 2:45 PM, Charles R Harris wrote:
>
>
> On Sat, Feb 18, 2012 at 1:39 PM, Matthew Brett wrote:
>
>> Hi,
>>
>> On Sat, Feb 18, 2012 at 12:35 PM, Charles R Harris
>> wrote:
>> >
>> >
>> > On Sat, Feb 18, 2012 at 12:21 PM, Matthew Brett <
>> matthew.br...@gmail.com>
>> > wrote
On Saturday, February 18, 2012, Matthew Brett wrote:
> Hi,
>
> On Sat, Feb 18, 2012 at 8:38 PM, Travis Oliphant
> >
> wrote:
>
> > We will need to see examples of what Mark is talking about and clarify
> some
> > of the compiler issues. Certainly there is some risk that once code is
> > written
On Thu, Feb 23, 2012 at 3:14 PM, Robert Kern wrote:
> On Thu, Feb 23, 2012 at 21:09, Gael Varoquaux
> wrote:
> > On Thu, Feb 23, 2012 at 04:07:04PM -0500, Wes McKinney wrote:
> >> In this last case for example, around 500 MB of RAM is taken up for an
> >> array that should only be about 80-90MB.
On Saturday, February 25, 2012, Alan G Isaac wrote:
> On 2/25/2012 4:44 PM, James Bergstra wrote:
> > bincount([]) makes no sense,
>
> I disagree:
> http://permalink.gmane.org/gmane.comp.python.numeric.general/42041
>
>
> > but if a minlength argument is provided,
> > then the routine should succe
On Saturday, March 3, 2012, Robert Kern wrote:
> On Sat, Mar 3, 2012 at 14:31, Ralf Gommers
wrote:
>>
>>
>> On Sat, Mar 3, 2012 at 3:05 PM, Robert Kern
wrote:
>>>
>>> On Sat, Mar 3, 2012 at 13:59, Ralf Gommers
>>> wrote:
>>> >
>>> >
>>> > On Thu, Mar 1, 2012 at 11:44 PM, Joe Kington
wrote:
>>>
On Mon, Mar 5, 2012 at 1:44 PM, Keith Goodman wrote:
> On Mon, Mar 5, 2012 at 11:36 AM, wrote:
> > How about numpy.ptp, to follow this line? I would expect it's single
> > pass, but wouldn't short circuit compared to cython of Keith
>
> I[1] a = np.ones(10)
> I[2] timeit (a == a[0]).all()
>
On Wed, Mar 7, 2012 at 1:26 PM, Nathaniel Smith wrote:
> On Wed, Mar 7, 2012 at 5:17 PM, Charles R Harris
> wrote:
> > On Wed, Mar 7, 2012 at 9:35 AM, Pierre Haessig >
> >> Coming back to Travis proposition "bit-pattern approaches to missing
> >> data (*at least* for float64 and int32) need to
On Wednesday, March 7, 2012, Neal Becker wrote:
> Charles R Harris wrote:
>
>> On Wed, Mar 7, 2012 at 1:05 PM, Neal Becker wrote:
>>
>>> I'm wondering what is the use for the ignored data feature?
>>>
>>> I can use:
>>>
>>> A[valid_A_indexes] = whatever
>>>
>>> to process only the 'non-ignored' p
On Wednesday, March 7, 2012, Nathaniel Smith wrote:
> On Wed, Mar 7, 2012 at 8:05 PM, Neal Becker wrote:
>> I'm wondering what is the use for the ignored data feature?
>>
>> I can use:
>>
>> A[valid_A_indexes] = whatever
>>
>> to process only the 'non-ignored' portions of A. So at least some
sim
On Thursday, March 15, 2012, Nathaniel Smith wrote:
> On Wed, Mar 14, 2012 at 1:44 AM, Mark Wiebe wrote:
>> On Fri, Mar 9, 2012 at 8:55 AM, Bryan Van de Ven
>> wrote:
>>>
>>> Hi all,
>>>
>>> I have started working on a NEP for adding an enumerated type to NumPy.
>>> It is on my GitHub:
>>>
>>>
On Thursday, March 15, 2012, Charles R Harris
wrote:
>
>
> On Thu, Mar 15, 2012 at 10:17 PM, David Cournapeau
wrote:
>>
>>
>> On Thu, Mar 15, 2012 at 11:10 PM, Matthew Brett
wrote:
>>>
>>> Hi,
>>>
>>> Am I right in thinking that float96 on windows 32 bit is a float64
>>> padded to 96 bits?
>>
>>
On Sunday, March 18, 2012, wrote:
> Dear list,
> I am having problems installing matplotlib (from source) and fipy.
> I had installed numpy from source and it is running well:
> :~$ python -c "import numpy; print numpy.__version__"
> 1.6.1
> After being trying to solve this problem on matplotlib
On Friday, April 6, 2012, Val Kalatsky wrote:
>
> The only slicing short-cut I can think of is the Ellipsis object, but it's
> not going to help you much here.
> The alternatives that come to my mind are (1) manipulation of shape
> directly and (2) building a string and running eval on it.
> Your
On Mon, Apr 9, 2012 at 12:14 PM, Jonathan T. Niehof wrote:
> On 04/06/2012 06:54 AM, Benjamin Root wrote:
>
> > Take a peek at how np.gradient() does it. It creates a list of None with
> > a length equal to the number of dimensions, and then inserts a slice
> > object in
On Tue, Apr 10, 2012 at 12:57 PM, Francesc Alted wrote:
> On 4/10/12 9:55 AM, Henry Gomersall wrote:
> > On 10/04/2012 16:36, Francesc Alted wrote:
> >> In [10]: timeit c = numpy.complex64(numpy.abs(numpy.complex128(b)))
> >> 100 loops, best of 3: 12.3 ms per loop
> >>
> >> In [11]: timeit c = num
On Tue, Apr 10, 2012 at 12:52 PM, Jonathan T. Niehof wrote:
> On 04/09/2012 09:11 PM, Tony Yu wrote:
>
> > I guess I wasn't reading very carefully and assumed that you meant a
> > list of `slice(None)` instead of a list of `None`.
>
> My apologies to Ben...I wasn't being pedantic to be a jerk, I w
On Wed, Apr 11, 2012 at 11:38 PM, santhu kumar wrote:
> Hello all,
>
> I am trying to optimise a code and want your suggestions.
> A : - NX3 matrix (coordinates of N points)
>
> After performing pairwise distance computations(called pdist) between
> these points, depending upon a condition that t
On Tue, Apr 24, 2012 at 2:12 PM, Charles R Harris wrote:
>
>
> On Tue, Apr 24, 2012 at 9:25 AM, wrote:
>
>> On Tue, Apr 24, 2012 at 9:43 AM, Pierre Haessig
>> wrote:
>> > Hi,
>> >
>> > Le 24/04/2012 15:14, Charles R Harris a écrit :
>> >>
>> >> a) All arrays should be implicitly masked, even if
On Tue, Apr 24, 2012 at 3:23 PM, Stéfan van der Walt wrote:
> On Tue, Apr 24, 2012 at 11:12 AM, Charles R Harris
> wrote:
> > The advantage of nans, I suppose, is that they are in the hardware and so
>
> Why are we having a discussion on NAN's in a thread on consensus?
> This is a strong indicato
On Tuesday, April 24, 2012, Matthew Brett wrote:
> Hi,
>
> On Tue, Apr 24, 2012 at 2:25 PM, Charles R Harris
> > wrote:
> >
> >
> > 2012/4/24 Stéfan van der Walt >
> >>
> >> On Tue, Apr 24, 2012 at 11:12 AM, Charles R Harris
> >> > wrote:
> >> > The advantage of nans, I suppose, is that they are i
On Wednesday, April 25, 2012, Matthew Brett wrote:
> Hi,
>
> On Wed, Apr 25, 2012 at 2:35 PM, Travis Oliphant
> >
> wrote:
> >>
> >> Do you agree that Numpy has not been very successful in recruiting and
> >> maintaining new developers compared to its large user-base?
> >>
> >> Compared to - say
On Wednesday, April 25, 2012, Travis Oliphant wrote:
>
> On Apr 25, 2012, at 7:18 PM, josef.p...@gmail.com wrote:
>
> >
> > Except for the big changes like NA and datetime, I think the debate is
> > pretty boring.
> > The main problem that I see for discussing technical issues is whether
> > ther
On Fri, Apr 27, 2012 at 6:32 AM, Richard Hattersley
wrote:
> I know used a somewhat jokey tone in my original posting, but
> fundamentally it was a serious question concerning a live topic. So I'm
> curious about the lack of response. Has this all been covered before?
>
> Sorry if I'm being too im
On Monday, April 30, 2012, Travis Oliphant wrote:
> Hey all,
>
> We have been doing some investigation of various approaches to issue
> tracking. The last time the conversation left this list was with
> Ralf's current list of preferences as:
>
> 1) Redmine
> 2) Trac
> 3) Github
>
> Since that
On Wednesday, May 2, 2012, Stéfan van der Walt wrote:
> On Wed, May 2, 2012 at 4:46 PM, Kevin Jacobs
>
> >
> > wrote:
> > A FLANN implementation should be even faster--perhaps by as much as
> another
> > factor of two.
>
> I guess it depends on whether you care about the "Approximate" in
> "Fast
On Saturday, May 5, 2012, Pauli Virtanen wrote:
> 05.05.2012 22:53, Ralf Gommers kirjoitti:
> [clip]
> > would be great to get it done by end of June.To Charles' list
> > and Ralf's suggestions, I would add setting up a server that can
> > relay pull requests to the mailing list.
>
On Saturday, May 5, 2012, Charles R Harris wrote:
>
>
> On Sat, May 5, 2012 at 8:50 PM, Benjamin Root
>
> > wrote:
>
>>
>>
>> On Saturday, May 5, 2012, Pauli Virtanen wrote:
>>
>>> 05.05.2012 22:53, Ralf Gommers kirjoitti:
>>> [clip
On Wednesday, May 9, 2012, Nathaniel Smith wrote:
>
>
> My only objection to this proposal is that committing to this approach
> seems premature. The existing masked array objects act quite
> differently from numpy.ma, so why do you believe that they're a good
> foundation for numpy.ma, and why wi
Just noticed this in the output from printing some numpy record arrays:
[[('2008081712', -24, -78.0, 20.10381469727, 45.0, -999.0, 0.0)]
[ ('2008081718', -18, -79.584741211, 20.70762939453, 45.0, -999.0,
0.0)]
[ ('2008081800', -12, -80.3305175781, 21.10381469727, 45.0,
-999.0
On Sat, May 5, 2012 at 2:15 PM, Ralf Gommers wrote:
> Hi,
>
> I'm pleased to announce the availability of the first release candidate of
> NumPy 1.6.2. This is a maintenance release. Due to the delay of the NumPy
> 1.7.0, this release contains far more fixes than a regular NumPy bugfix
> release.
Hello all,
I need to sort a structured array in a stable manner. I am also sorting
only by one of the keys, so I don't think lexsort() is stable in that
respect. np.sort() allows for choosing 'mergesort', but it appears to not
be implemented for structured arrays. Am I going to have to create a
On Fri, May 11, 2012 at 12:00 PM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
>
>
> On Fri, May 11, 2012 at 9:01 AM, Benjamin Root wrote:
>
>> Hello all,
>>
>> I need to sort a structured array in a stable manner. I am also sorting
>> only by
On Saturday, May 12, 2012, Travis Oliphant wrote:
> Another approach would be to introduce a method:
>
> a.diag(copy=False)
>
> and leave a.diagonal() alone. Then, a.diagonal() could be deprecated over
> 2-3 releases.
>
> -Travis
>
+1
Ben Root
>
___
On Wed, May 16, 2012 at 9:55 AM, Nathaniel Smith wrote:
> On Tue, May 15, 2012 at 2:49 PM, Frédéric Bastien wrote:
> > Hi,
> >
> > In fact, I would arg to never change the current behavior, but add the
> > flag for people that want to use it.
> >
> > Why?
> >
> > 1) There is probably >10k script
On Friday, May 18, 2012, Chao YUE wrote:
> Dear all,
>
> This is only a small python import question. I think I'm right but just
> want some confirmation.
>
> Previously I have installed numpy 1.5.1. and then I used pip install
> --upgrade numpy
> to install numpy 1.6.1
>
> But when I try to impor
On Thu, May 24, 2012 at 10:56 AM, Jonathan T. Niehof wrote:
> On 05/23/2012 05:31 PM, T J wrote:
>
> > It seems that there are a number of ways to check if an array is a view.
> > Do we have a preferred way in the API that is guaranteed to stay
> > available? Or are all of the various methods "her
On Fri, May 25, 2012 at 11:17 AM, Chris Withers wrote:
> Hi All,
>
> I have an array:
>
> arrrgh = numpy.zeros(1)
>
> A sparse collection of elements will have values greater than zero:
>
> arrrgh[] = 2
> arrrgh[3453453] =42
>
> The *wrong* way to do this is:
>
> for i in xrange(len(ar
On Sunday, May 27, 2012, Chao YUE wrote:
> for me, np.nonzero() and np.where() both work. It seems they have same
> function.
>
> chao
They are not identical. Nonzeros is for indices. The where function is
really meant for a different purpose, but special-cases for this call
signature.
Ben Root
On Fri, Jun 1, 2012 at 9:14 AM, Nathaniel Smith wrote:
> On Fri, Jun 1, 2012 at 10:46 AM, Chris Withers
> wrote:
> > Hi All,
> >
> > Any reason why this:
> >
> > >>> import numpy
> > >>> numpy.zeros(10)[-123]
> > Traceback (most recent call last):
> > File "", line 1, in
> > IndexError: ind
On Sunday, June 3, 2012, Ralf Gommers wrote:
>
>
> On Sun, Jun 3, 2012 at 4:49 PM, Nathaniel Smith
>
> > wrote:
>
>> On Sun, Jun 3, 2012 at 3:28 PM, Ralf Gommers
>> > 'ralf.gomm...@googlemail.com');>> wrote:
>> > Hi,
>> >
>> > Just ran into this:
>> >
>> np.__version__
>> > '1.5.1'
>>
On Monday, June 4, 2012, Chris Barker wrote:
> On Mon, Jun 4, 2012 at 11:10 AM, Patrick Redmond
> >
> wrote:
> > Here's how I sorted primarily by field 'a' descending and secondarily by
> > field 'b' ascending:
>
> could you multiply the numeric field by -1, sort, then put it back --
> somethign
On Tue, Jun 5, 2012 at 10:49 AM, Nathaniel Smith wrote:
> On Tue, Jun 5, 2012 at 1:17 AM, Benjamin Root wrote:
> >
> >
> > On Monday, June 4, 2012, Chris Barker wrote:
> >>
> >> On Mon, Jun 4, 2012 at 11:10 AM, Patrick Redmond
> >> wrote:
On Tue, Jun 5, 2012 at 10:37 AM, Robert Kern wrote:
> On Tue, Jun 5, 2012 at 2:54 PM, Neal Becker wrote:
> > I think it's unfortunate that functions like logical_or are limited to
> binary.
> >
> > As a workaround, I've been using this:
> >
> > def apply_binary (func, *args):
> >if len (args
Not sure if this is a bug or not. I am using a fairly recent master branch.
>>> # Setting up...
>>> import numpy as np
>>> a = np.zeros((10, 1), dtype=[('foo', 'f4'), ('bar', 'f4'), ('spam',
'f4')])
>>> a['foo'] = np.random.random((10, 1))
>>> a['bar'] = np.random.random((10, 1))
>>> a['spam'] =
On Thursday, June 21, 2012, Robert Kern wrote:
> On Thu, Jun 21, 2012 at 7:33 PM, eat >
> wrote:
> > Heh,
> >
> > On Thu, Jun 21, 2012 at 6:03 PM, Robert Kern
> > >
> wrote:
> >>
> >> On Thu, Jun 21, 2012 at 3:59 PM, bob tnur
> >> >
> wrote:
> >> > Hi all numpy fun;)
> >> > This question is alre
On Fri, Jun 22, 2012 at 9:42 AM, eat wrote:
> Hi,
>
> On Fri, Jun 22, 2012 at 7:51 AM, Gael Varoquaux <
> gael.varoqu...@normalesup.org> wrote:
>
>> On Thu, Jun 21, 2012 at 08:59:09PM -0400, Benjamin Root wrote:
>> > > munkres seems to be a pure pytho
On Fri, Jun 22, 2012 at 10:25 AM, Travis Oliphant wrote:
> Accessing individual elements of NumPy arrays is slower than accessing
> individual elements of lists --- around 2.5x-3x slower.NumPy has to do
> more work to figure out what kind of indexing you are trying to do because
> of its flexi
On Mon, Jun 25, 2012 at 1:41 PM, Travis Oliphant wrote:
>
>> C was famous for bugs due to the lack of function prototypes. This was
>> fixed with C99 and the stricter typing was a great help.
>>
>>
>> Bugs are not "due to lack of function prototypes". Bugs are due to
>> mistakes that programmers
On Tue, Jun 26, 2012 at 12:48 PM, David Cournapeau wrote:
> On Tue, Jun 26, 2012 at 5:24 PM, Travis Oliphant
> wrote:
> >
> >> Let us note that that problem was due to Travis convincing David to
> >> include the Datetime work in the release against David's own best
> judgement.
> >> The result wa
On Tuesday, June 26, 2012, Charles R Harris wrote:
>
>
> On Tue, Jun 26, 2012 at 3:42 PM, Matthew Brett wrote:
>
> Hi,
>
> On Mon, Jun 18, 2012 at 3:50 PM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Sun, Jun 17, 2012 at 7:22 PM, Charles R Harris
> > wrote:
> >>
> >>
> >> On Sat, Jun 16, 2012 at 2
On Tuesday, June 26, 2012, Thouis (Ray) Jones wrote:
> On Tue, Jun 26, 2012 at 10:11 PM, Jason Grout
> > wrote:
> > On 6/26/12 3:06 PM, Dag Sverre Seljebotn wrote:
> >> Something the Sage project does very well is meeting often in person
> >
> > Another thing we have that has improved the mailing
On Mon, Jul 2, 2012 at 4:34 PM, Nathaniel Smith wrote:
> On Mon, Jul 2, 2012 at 8:17 PM, Andrew Dalke
> wrote:
> > In this email I propose a few changes which I think are minor
> > and which don't really affect the external NumPy API but which
> > I think could improve the "import numpy" perform
On Tue, Jul 10, 2012 at 3:37 AM, Robert Kern wrote:
> On Tue, Jul 10, 2012 at 4:32 AM, Charles R Harris
> wrote:
> > Hi All,
> >
> > I've been adding type specific sorts for object and structured arrays. It
> > seems that datetime64 and timedelta64 are also not supported. Is there
> any
> > reas
On Tue, Jul 10, 2012 at 6:07 AM, Ralf Gommers
wrote:
>
>
> On Tue, Jul 10, 2012 at 11:36 AM, Ralf Gommers <
> ralf.gomm...@googlemail.com> wrote:
>
>>
>>
>> On Tue, Jul 10, 2012 at 4:20 AM, Six Silberman
>> wrote:
>>
>>> Hi all,
>>>
>>> Some colleagues and I are interested in contributing to nump
On Tue, Jul 10, 2012 at 2:45 PM, Prakash Joshi wrote:
> Hi All,
>
> I built numpy 1.6.2 on linux 64 bit and installed numpy in
> site-packages, It pass all the test cases of numpy, but I am not sure if
> this is good build; As I did not specified any fortran compiler while
> setup, also I do n
Prakash,
On Tue, Jul 10, 2012 at 3:26 PM, Prakash Joshi wrote:
> Thanks Ben.
>
> Also I did not specified any of BLAS, LAPACK, ATLAS libraries, do we
> need these libraries for numpy?
>
"Need", no, you do not "need" them in the sense that NumPy does not require
them to work. NumPy will work
On Thursday, July 12, 2012, Thouis (Ray) Jones wrote:
> On Thu, Jul 12, 2012 at 1:28 AM, Charles R Harris
> > wrote:
> > Hi All,
> >
> > Travis and I agree that it would be appropriate to remove the current
> 1.7.x
> > branch and branch again after a code freeze. That way we can avoid the
> pain
>
On Thursday, July 12, 2012, Nathaniel Smith wrote:
> On Thu, Jul 12, 2012 at 12:48 PM, Benjamin Root
> >
> wrote:
> >
> >
> > On Thursday, July 12, 2012, Thouis (Ray) Jones wrote:
> >>
> >> On Thu, Jul 12, 2012 at 1:28 AM, Charles R Harris
> &g
On Thu, Jul 12, 2012 at 3:38 PM, Chao YUE wrote:
> Dear all,
>
> I want to create a function and I would like one of the arguments of the
> function to determine what slicing of numpy array I want to use.
> a simple example:
>
> a=np.arange(100).reshape(10,10)
>
> suppose I want to have a imaging
ery similar to the
arguments for range() (with some exceptions/differences).
Cheers!
Ben Root
> 2012/7/12 Benjamin Root
>
>>
>>
>> On Thu, Jul 12, 2012 at 3:38 PM, Chao YUE wrote:
>>
>>> Dear all,
>>>
>>> I want to create a function and
On Thursday, July 12, 2012, Chao YUE wrote:
> Thanks all for the discussion. Actually I am trying to use something like
> numpy ndarray indexing in the function. Like when I call:
>
> func(a,'1:3,:,2:4'), it knows I want to retrieve a[1:3,:,2:4], and
> func(a,'1:3,:,4') for a[1:3,:,4] ect.
> I am
On Monday, July 23, 2012, OC wrote:
> > It's unPythonic just in the sense that it is unlike every other type
> > constructor in Python. int(x) returns an int, list(x) returns a list,
> > but np.complex64(x) sometimes returns a np.complex64, and sometimes it
> > returns a np.ndarray, depending
On Thu, Jul 26, 2012 at 4:45 PM, Colin J. Williams wrote:
> It seems that these standards have been adopted, which is good:
>
> The following import conventions are used throughout the NumPy source and
> documentation:
>
> import numpy as np
> import matplotlib as mpl
> import matplotlib.pyplot
On Thu, Jul 26, 2012 at 7:12 PM, Robert Kern wrote:
> On Fri, Jul 27, 2012 at 12:05 AM, Colin J. Williams
> wrote:
> > On 26/07/2012 4:57 PM, Benjamin Root wrote:
> >
> >
> > On Thu, Jul 26, 2012 at 4:45 PM, Colin J. Williams wrote:
> >>
> >>
On Thu, Jul 26, 2012 at 2:33 PM, Phil Hodge wrote:
> On a Linux machine:
>
> > uname -srvop
> Linux 2.6.18-308.8.2.el5 #1 SMP Tue May 29 11:54:17 EDT 2012 x86_64
> GNU/Linux
>
> this example shows an apparent problem with the where function:
>
> Python 2.7.1 (r271:86832, Dec 21 2010, 11:19:43)
>
On Fri, Jul 27, 2012 at 3:58 PM, Andreas Mueller
wrote:
> Hi Everybody.
> The bug is that no error is raised, right?
> The docs say
>
> where(condition, [x, y])
>
> x, y : array_like, optional
> Values from which to choose. `x` and `y` need to have the same
> shape as `condition`
>
> In
On Tue, Aug 21, 2012 at 12:24 PM, Ondřej Čertík wrote:
> Hi,
>
> I'm pleased to announce the availability of the first beta release of
> NumPy 1.7.0b1.
>
> Sources and binary installers can be found at
> https://sourceforge.net/projects/numpy/files/NumPy/1.7.0b1/
>
> Please test this release and r
On Thursday, August 30, 2012, Neal Becker wrote:
> I think this should be simple, but I'm drawing a blank
>
> I have 2 2d matrixes
>
> Matrix A has indexes (i, symbol)
> Matrix B has indexes (state, symbol)
>
> I combined them into a 3d matrix:
>
> C = A[:,newaxis,:] + B[newaxis,:,:]
> where C has
An issue just reported on the matplotlib-users list involved a user who ran
out of memory while attempting to do an imshow() on a large array. While
this wouldn't be totally unexpected, the user's traceback shows that they
ran out of memory before any actual building of the image occurred. Memory
Consider the following code:
import numpy as np
a = np.array([1, 2, 3, 4, 5], dtype=np.int16)
a *= float(255) / 15
In v1.6.x, this yields:
array([17, 34, 51, 68, 85], dtype=int16)
But in master, this throws an exception about failing to cast via same_kind.
Note that numpy was smart about this o
On Mon, Sep 17, 2012 at 9:33 PM, Charles R Harris wrote:
>
>
> On Mon, Sep 17, 2012 at 3:40 PM, Travis Oliphant wrote:
>
>>
>> On Sep 17, 2012, at 8:42 AM, Benjamin Root wrote:
>>
>> > Consider the following code:
>> >
>> > import nump
On Fri, Sep 7, 2012 at 12:05 PM, Nathaniel Smith wrote:
> On 7 Sep 2012 14:38, "Benjamin Root" wrote:
> >
> > An issue just reported on the matplotlib-users list involved a user who
> ran out of memory while attempting to do an imshow() on a large array.
>
On Tue, Sep 18, 2012 at 2:47 PM, Charles R Harris wrote:
>
>
> On Tue, Sep 18, 2012 at 11:39 AM, Benjamin Root wrote:
>
>>
>>
>> On Mon, Sep 17, 2012 at 9:33 PM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>>
>>>
>&
On Tue, Sep 18, 2012 at 3:19 PM, Ralf Gommers wrote:
>
>
> On Tue, Sep 18, 2012 at 9:13 PM, Benjamin Root wrote:
>
>>
>>
>> On Tue, Sep 18, 2012 at 2:47 PM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>>
>>>
>&
On Tue, Sep 18, 2012 at 3:25 PM, Charles R Harris wrote:
>
>
> On Tue, Sep 18, 2012 at 1:13 PM, Benjamin Root wrote:
>
>>
>>
>> On Tue, Sep 18, 2012 at 2:47 PM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>>
>>>
>&
On Tue, Sep 18, 2012 at 4:42 PM, Charles R Harris wrote:
>
>
> On Tue, Sep 18, 2012 at 2:33 PM, Travis Oliphant wrote:
>
>>
>> On Sep 18, 2012, at 2:44 PM, Charles R Harris wrote:
>>
>>
>>
>> On Tue, Sep 18, 2012 at 1:35 PM, Benjamin Root wrote
On Fri, Sep 21, 2012 at 4:19 PM, Travis Oliphant wrote:
>
> On Sep 21, 2012, at 3:13 PM, Ralf Gommers wrote:
>
> Hi,
>
> An issue I keep running into is that packages use:
> install_requires = ["numpy"]
> or
> install_requires = ['numpy >= 1.6']
>
> in their setup.py. This simply doesn't w
On Wed, Oct 24, 2012 at 3:00 PM, Michael Aye wrote:
> As numpy.fromfile seems to require full file object functionalities
> like seek, I can not use it with the sys.stdin pipe.
> So how could I stream a binary pipe directly into numpy?
> I can imagine storing the data in a string and use StringIO
This error started showing up in the test suite for mpl when using numpy
master.
AttributeError: incompatible shape for a non-contiguous array
The tracebacks all point back to various code points where we are trying to
set the shape of an array, e.g.,
offsets.shape = (-1, 2)
Those lines haven't
On Mon, Oct 29, 2012 at 10:33 AM, Sebastian Berg wrote:
> Hey,
>
> On Mon, 2012-10-29 at 09:54 -0400, Benjamin Root wrote:
> > This error started showing up in the test suite for mpl when using
> > numpy master.
> >
> > AttributeError: incompatible shape for a
gt; ---
> Patrick Marsh
> Ph.D. Candidate / Liaison to the HWT
> School of Meteorology / University of Oklahoma
> Cooperative Institute for Mesoscale Meteorological Studies
> National Severe Storms Laboratory
> http://www.patricktmarsh.com
>
>
>
> On Mon, Oct 29, 2012 at
On Wednesday, October 31, 2012, wrote:
> On Wed, Oct 31, 2012 at 8:59 PM, klo uo >
> wrote:
> > Thanks for your reply
> >
> > I suppose, variable length signals are split on equal parts and dominant
> > harmonic is extracted. Then scatter plot shows this pattern, which has
> some
> > low correlati
On Monday, November 12, 2012, Olivier Delalleau wrote:
> 2012/11/12 Nathaniel Smith 'n...@pobox.com');>>
>
>> On Mon, Nov 12, 2012 at 8:54 PM, Matthew Brett
>> > 'matthew.br...@gmail.com');>>
>> wrote:
>> > Hi,
>> >
>> > I wanted to check that everyone knows about and is happy with the
>> > scal
On Monday, November 12, 2012, Benjamin Root wrote:
>
>
> On Monday, November 12, 2012, Olivier Delalleau wrote:
>
>> 2012/11/12 Nathaniel Smith
>>
>>> On Mon, Nov 12, 2012 at 8:54 PM, Matthew Brett
>>> wrote:
>>> > Hi,
>>> >
&
On Monday, November 12, 2012, Matthew Brett wrote:
> Hi,
>
> On Mon, Nov 12, 2012 at 8:15 PM, Benjamin Root wrote:
> >
> >
> > On Monday, November 12, 2012, Olivier Delalleau wrote:
> >>
> >> 2012/11/12 Nathaniel Smith
> >>>
> >&
On Saturday, November 17, 2012, Chao YUE wrote:
> Dear all,
>
> I need to make a linear contrast of the 2D numpy array "data" from an
> interval to another, the approach is:
> I have another two list: "base" & "target", then I check for each ndarray
> element "data[i,j]",
> if base[m] =< data[i,
On Saturday, November 17, 2012, Charles R Harris wrote:
>
>
> On Sat, Nov 17, 2012 at 1:00 PM, Olivier Delalleau
>
> > wrote:
>
>> 2012/11/17 Gökhan Sever > 'cvml', 'gokhanse...@gmail.com');>>
>>
>>>
>>>
>>> On Sat, Nov 17, 2012 at 9:47 AM, Nathaniel Smith
>>>
>>> > wrote:
>>>
On Fri, Nov
On Tue, Dec 4, 2012 at 8:57 AM, Sebastian Berg
wrote:
> Hey,
>
> Maybe someone has an opinion about this (since in fact it is new
> behavior, so it is undefined). `np.take` used to not allow 0-d/scalar
> input but did allow any other dimensions for the indices. Thinking about
> changing this, mean
As a point of reference, python 2.4 is on RH5/CentOS5. While RH6 is the
current version, there are still enterprises that are using version 5. Of
course, at this point, one really should be working on a migration plan and
shouldn't be doing new development on those machines...
Ben Root
_
On Thu, Dec 13, 2012 at 12:38 PM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
> The previous proposal to drop python 2.4 support garnered no opposition.
> How about dropping support for python 2.5 also?
>
> Chuck
>
>
matplotlib 1.2 supports py2.5. I haven't seen any plan to move off of t
My apologies... we support 2.6 and above. +1 on dropping 2.5 support.
Ben
On Thu, Dec 13, 2012 at 1:12 PM, Benjamin Root wrote:
> On Thu, Dec 13, 2012 at 12:38 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>> The previous proposal to drop python 2.
On Wed, Jan 9, 2013 at 9:58 AM, Nathaniel Smith wrote:
> On Wed, Jan 9, 2013 at 2:53 PM, Alan G Isaac wrote:
> > I'm just a Python+NumPy user and not a CS type.
> > May I ask a naive question on this thread?
> >
> > Given the work that has (as I understand it) gone into
> > making NumPy usable a
On Mon, Jan 14, 2013 at 7:38 AM, Pierre Haessig wrote:
> Hi,
>
> Le 14/01/2013 00:39, Nathaniel Smith a écrit :
> > (The nice thing about np.filled() is that it makes np.zeros() and
> > np.ones() feel like clutter, rather than the reverse... not that I'm
> > suggesting ever getting rid of them, bu
On Mon, Jan 14, 2013 at 12:27 PM, Eric Firing wrote:
> On 2013/01/14 6:15 AM, Olivier Delalleau wrote:
> > - I agree the name collision with np.ma.filled is a problem. I have no
> > better suggestion though at this point.
>
> How about "initialized()"?
>
A verb! +1 from me!
For those wondering,
On Mon, Jan 14, 2013 at 1:56 PM, David Warde-Farley <
d.warde.far...@gmail.com> wrote:
> On Mon, Jan 14, 2013 at 1:12 PM, Pierre Haessig
> wrote:
> > In [8]: tile(nan, (3,3)) # (it's a verb ! )
>
> tile, in my opinion, is useful in some cases (for people who think in
> terms of repmat()) but not
On Thu, Jan 17, 2013 at 8:54 AM, Jim Vickroy wrote:
> On 1/16/2013 11:41 PM, Nathaniel Smith wrote:
>
> On 16 Jan 2013 17:54, wrote:
> > >>> a = np.random.random_integers(0, 5, size=5)
> > >>> b = a.sort()
> > >>> b
> > >>> a
> > array([0, 1, 2, 5, 5])
> >
> > >>> b = np.random.shuffle(a)
> > >
On Thu, Jan 17, 2013 at 5:04 PM, Eric Firing wrote:
> On 2013/01/17 4:13 AM, Pierre Haessig wrote:
> > Hi,
> >
> > Le 14/01/2013 20:05, Benjamin Root a écrit :
> >> I do like the way you are thinking in terms of the broadcasting
> >> semantics, but I wonder
On Fri, Jan 18, 2013 at 3:44 AM, Daniele Nicolodi wrote:
> On 17/01/2013 23:27, Mark Wiebe wrote:
> > Would it be too weird or clumsy to extend the empty and empty_like
> > functions to do the filling?
> >
> > np.empty((10, 10), fill=np.nan)
> > np.empty_like(my_arr, fill=np.nan)
>
> Wouldn't it b
On Fri, Jan 18, 2013 at 11:36 AM, Daniele Nicolodi wrote:
> On 18/01/2013 15:19, Benjamin Root wrote:
> >
> >
> > On Fri, Jan 18, 2013 at 3:44 AM, Daniele Nicolodi > <mailto:dani...@grinta.net>> wrote:
> >
> > On 17/01/2013 23:27, Mark Wiebe wro
1 - 100 of 617 matches
Mail list logo
