Re: [Numpy-discussion] [help needed] associativity and precedence of '@'

On 03/20/2014 02:26 PM, Dag Sverre Seljebotn wrote: > On 03/19/2014 08:45 PM, josef.p...@gmail.com wrote: >> >> >> >> On Wed, Mar 19, 2014 at 2:24 PM, Nathaniel Smith > <mailto:n...@pobox.com>> wrote: >> >> On Tue, Mar 18, 2014 at 9:14 A

Re: [Numpy-discussion] [help needed] associativity and precedence of '@'

On 03/19/2014 08:45 PM, josef.p...@gmail.com wrote: > > > > On Wed, Mar 19, 2014 at 2:24 PM, Nathaniel Smith > wrote: > > On Tue, Mar 18, 2014 at 9:14 AM, Robert Kern > wrote: > > On Tue, Mar 18, 2014 at 12:54 AM, Nathaniel Smith

Re: [Numpy-discussion] openblas?

On 09/23/2013 02:27 PM, Neal Becker wrote: > Does numpy/scipy support building with openblas for blas,lapack instead of > atlas? I have that working myself. I think it was simply a matter of using the configuration below; NumPy will think it is ATLAS, but that doesn't matter. Once NumPy is built

Re: [Numpy-discussion] add .H attribute?

On 07/23/2013 07:53 PM, Alan G Isaac wrote: > I'm trying to understand the state of this discussion. > I believe that propoents of adding a .H attribute have > primarily emphasized > > - readability (and general ease of use) > - consistency with matrix and masked array > - forward looking (to a fut

Re: [Numpy-discussion] add .H attribute?

On 07/23/2013 10:35 AM, Dag Sverre Seljebotn wrote: > On 07/23/2013 09:35 AM, Dave Hirschfeld wrote: >> Alan G Isaac gmail.com> writes: >> >>> >>> On 7/22/2013 3:10 PM, Nathaniel Smith wrote: >>>> Having .T but not .H is an ex

Re: [Numpy-discussion] add .H attribute?

On 07/23/2013 09:35 AM, Dave Hirschfeld wrote: > Alan G Isaac gmail.com> writes: > >> >> On 7/22/2013 3:10 PM, Nathaniel Smith wrote: >>> Having .T but not .H is an example of this split. >> >> Hate to do this but ... >> >>Readability counts. > > +10! > > A.conjugate().transpose() is unspeakab

Re: [Numpy-discussion] low level optimization in NumPy and minivect

On 06/25/2013 04:21 PM, Frédéric Bastien wrote: > Hi, > > I wasn't able to attend this year Scipy Conference. My tutorial proposal > was rejected and other deadline intefered with this conference date. > > Will the presentation be recorded? If not, can you make the slide available? > > What is your

Re: [Numpy-discussion] low level optimization in NumPy and minivect

On 06/17/2013 11:03 PM, Julian Taylor wrote: > On 17.06.2013 17:11, Frédéric Bastien wrote: >> Hi, >> >> I saw that recently Julian Taylor is doing many low level optimization >> like using SSE instruction. I think it is great. >> >> Last year, Mark Florisson released the minivect[1] project that h

Re: [Numpy-discussion] Please stop bottom posting!!

On 04/04/2013 12:00 AM, Chris Barker - NOAA Federal wrote: > OK, OK, I know the fashion is to blast people with "please don't top > post" messages -- it seems to have invaded all the mailing lists I'm > on. > > But I don't get it. > > Most of us have threaded mail readers these days, so is it so ha

Re: [Numpy-discussion] Windows, blas, atlas and dlls

On 02/22/2013 05:52 PM, Chris Barker - NOAA Federal wrote: > On Thu, Feb 21, 2013 at 4:16 AM, Matyáš Novák wrote: >>> You could also look into OpenBLAS, which is easier to build and >>> generally faster than ATLAS. (But alas, not supported by NumPy/SciPY AFAIK.) > > It look slike OpenBLAS is BSD-l

Re: [Numpy-discussion] Windows, blas, atlas and dlls

On 02/20/2013 10:18 AM, Sergio wrote: > Dag Sverre Seljebotn astro.uio.no> writes: > >> >> On 02/18/2013 05:26 PM, rif wrote: >>> I have no answer to the question, but I was curious as to why directly >>> calling the cblas would be 10x-20x slower in the

Re: [Numpy-discussion] Windows, blas, atlas and dlls

On 02/18/2013 09:23 PM, Pauli Virtanen wrote: > 18.02.2013 20:41, Dag Sverre Seljebotn kirjoitti: > [clip] >> I think there should be a new project, pylapack or similar, for this, >> outside of NumPy and SciPy. NumPy and SciPy could try to import it, and >> if found, fetch

Re: [Numpy-discussion] Windows, blas, atlas and dlls

On 02/18/2013 06:48 PM, Pauli Virtanen wrote: > 18.02.2013 19:20, Dag Sverre Seljebotn kirjoitti: >> On 02/18/2013 05:29 PM, rif wrote: >>> But I'd hope that the overhead for going through the wrappers is >>> constant, rather than dependent on the size, so that

Re: [Numpy-discussion] Windows, blas, atlas and dlls

S matters much less in this situation. But if you have a code that is used with either many small or fewer large matrices, then a compiled loop over a good BLAS is a good compromise without splitting up the code paths. DS > > > On Mon, Feb 18, 2013 at 8:28 AM, Dag Sverre S

Re: [Numpy-discussion] Windows, blas, atlas and dlls

On 02/18/2013 05:28 PM, Dag Sverre Seljebotn wrote: > On 02/18/2013 05:26 PM, rif wrote: >> I have no answer to the question, but I was curious as to why directly >> calling the cblas would be 10x-20x slower in The statement was that directly (on the Cython level) calling cblas is

Re: [Numpy-discussion] Windows, blas, atlas and dlls

On 02/18/2013 05:26 PM, rif wrote: > I have no answer to the question, but I was curious as to why directly > calling the cblas would be 10x-20x slower in the first place. That > seems surprising, although I'm just learning about python numerics. The statement was that directly (on the Cython lev

Re: [Numpy-discussion] ANN: NumPy 1.7.0 release

On 02/10/2013 11:58 AM, Dag Sverre Seljebotn wrote: > On 02/10/2013 03:36 AM, Neal Becker wrote: >> Is there a way to add '-march=native' flag to gcc for the build? > > I think something along these lines should work (untested): > > CFLAGS="$(python-config --cf

Re: [Numpy-discussion] ANN: NumPy 1.7.0 release

On 02/10/2013 03:36 AM, Neal Becker wrote: > Is there a way to add '-march=native' flag to gcc for the build? I think something along these lines should work (untested): CFLAGS="$(python-config --cflags) -march=native" python setup.py install Dag Sverre __

Re: [Numpy-discussion] Any plans for windows 64-bit installer for 1.7?

On 02/07/2013 12:16 AM, Matthew Brett wrote: > Hi, > > On Wed, Feb 6, 2013 at 1:36 PM, Ralf Gommers wrote: >> >> >> >> On Wed, Feb 6, 2013 at 8:46 PM, Matthew Brett >> wrote: >>> >>> Hi, >>> >>> On Wed, Feb 6, 2013 at 10:48 AM, Ralf Gommers >>> wrote: On Wed, Feb 6, 2013 at 1

Re: [Numpy-discussion] Issues to fix for 1.7.0rc2.

On 02/06/2013 08:41 AM, Charles R Harris wrote: > > > On Tue, Feb 5, 2013 at 11:50 PM, Jason Grout > mailto:jason-s...@creativetrax.com>> wrote: > > On 2/6/13 12:46 AM, Charles R Harris wrote: > > if we decide to do so > > I should mention that we don't really depend on either behavior

Re: [Numpy-discussion] Shouldn't all in-place operations simply return self?

On 01/17/2013 05:33 PM, Nathaniel Smith wrote: > On Thu, Jan 17, 2013 at 2:32 PM, Alan G Isaac wrote: >> Is it really better to have `permute` and `permuted` >> than to add a keyword? (Note that these are actually >> still ambiguous, except by convention.) > > The convention in question, though,

Re: [Numpy-discussion] Casting Bug or a "Feature"?

On 01/17/2013 01:27 PM, josef.p...@gmail.com wrote: > On Thu, Jan 17, 2013 at 2:34 AM, Matthieu Brucher > wrote: >> Hi, >> >> Actually, this behavior is already present in other languages, so I'm -1 on >> additional verbosity. >> Of course a += b is not the same as a = a + b. The first one modifie

Re: [Numpy-discussion] Do we want scalar casting to behave as it does at the moment?

On 01/09/2013 06:22 PM, Chris Barker - NOAA Federal wrote: > On Wed, Jan 9, 2013 at 7:09 AM, Nathaniel Smith wrote: >>> This is a general issue applying to data which is read from real-world >>> external sources. For example, digitizers routinely represent their >>> samples as int8's or int16's,

Re: [Numpy-discussion] Insights / lessons learned from NumPy design

On 01/09/2013 04:41 PM, Benjamin Root wrote: > > > 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

Re: [Numpy-discussion] Insights / lessons learned from NumPy design

On 01/09/2013 11:49 AM, Mike Anderson wrote: > On 4 January 2013 16:00, Dag Sverre Seljebotn > mailto:d.s.seljeb...@astro.uio.no>> wrote: > > On 01/04/2013 07:29 AM, Mike Anderson wrote: > > Hello all, > > > > In the Clojure community

Re: [Numpy-discussion] Do we want scalar casting to behave as it does at the moment?

On 01/08/2013 10:32 PM, Dag Sverre Seljebotn wrote: > On 01/08/2013 06:20 PM, Andrew Collette wrote: >> Hi, >> >>> I think you are voting strongly for the current casting rules, because >>> they make it less obvious to the user that scalars are different from &g

Re: [Numpy-discussion] Do we want scalar casting to behave as it does at the moment?

On 01/08/2013 06:20 PM, Andrew Collette wrote: > Hi, > >> I think you are voting strongly for the current casting rules, because >> they make it less obvious to the user that scalars are different from >> arrays. > > Maybe this is the source of my confusion... why should scalars be > different from

Re: [Numpy-discussion] Do we want scalar casting to behave as it does at the moment?

On 2013-01-07 21:50, Andrew Collette wrote: > Hi Matthew, > >> Just to be clear, you mean you might have something like this? >> >> def my_func('array_name', some_offset): >> arr = load_somehow('array_name') # dtype hitherto unknown >> return arr + some_offset >> >> ? And the problem is th

Re: [Numpy-discussion] Rank-0 arrays - reprise

On 01/06/2013 05:52 PM, Nathaniel Smith wrote: > On Sun, Jan 6, 2013 at 10:35 AM, Dag Sverre Seljebotn > wrote: >> I should have been more precise: I like the proposal, but also believe >> the additional complexity introduced have significant costs that must be >> consid

Re: [Numpy-discussion] Rank-0 arrays - reprise

On 01/06/2013 11:16 AM, Nathaniel Smith wrote: > On 6 Jan 2013 07:59, "Dag Sverre Seljebotn" <mailto:d.s.seljeb...@astro.uio.no>> wrote: > > Try to enumerate all the fundamentally different things (if you count > > memory use/running time) that can happen for n

Re: [Numpy-discussion] Rank-0 arrays - reprise

On 01/06/2013 10:41 AM, Sebastian Berg wrote: > On Sun, 2013-01-06 at 08:58 +0100, Dag Sverre Seljebotn wrote: >> On 01/05/2013 10:31 PM, Nathaniel Smith wrote: >>> On 5 Jan 2013 12:16, "Matthew Brett" wrote: >>>> >>>> Hi, >>>> >&

Re: [Numpy-discussion] Rank-0 arrays - reprise

On 01/05/2013 10:31 PM, Nathaniel Smith wrote: > On 5 Jan 2013 12:16, "Matthew Brett" wrote: >> >> Hi, >> >> Following on from Nathaniel's explorations of the scalar - array >> casting rules, some resources on rank-0 arrays. >> >> The discussion that Nathaniel tracked down on "rank-0 arrays"; it a

Re: [Numpy-discussion] Scalar casting rules use-case reprise

On 01/04/2013 02:46 PM, Nathaniel Smith wrote: > On Fri, Jan 4, 2013 at 11:09 AM, Matthew Brett > wrote: >> Hi, >> >> Reading the discussion on the scalar casting rule change I realized I >> was hazy on the use-cases that led to the rule that scalars cast >> differently from arrays. >> >> My impr

Re: [Numpy-discussion] Insights / lessons learned from NumPy design

On 01/04/2013 09:00 AM, Dag Sverre Seljebotn wrote: > On 01/04/2013 07:29 AM, Mike Anderson wrote: >> Hello all, >> >> In the Clojure community there has been some discussion about creating a >> common matrix maths library / API. Currently there are a few different >

Re: [Numpy-discussion] Insights / lessons learned from NumPy design

On 01/04/2013 07:29 AM, Mike Anderson wrote: > Hello all, > > In the Clojure community there has been some discussion about creating a > common matrix maths library / API. Currently there are a few different > fledgeling matrix libraries in Clojure, so it seemed like a worthwhile > effort to unify

Re: [Numpy-discussion] Do we want scalar casting to behave as it does at the moment?

On 01/04/2013 12:39 AM, Andrew Collette wrote: >> Consensus in that bug report seems to be that for array/scalar operations >> like: >>np.array([1], dtype=np.int8) + 1000 # can't be represented as an int8! >> we should raise an error, rather than either silently upcasting the >> result (as in

Re: [Numpy-discussion] Future of numpy (was: DARPA funding for Blaze and passing the NumPy torch)

On 12/22/2012 06:36 PM, Matthew Brett wrote: > Hi, > > On Thu, Dec 20, 2012 at 5:39 PM, Nathaniel Smith wrote: >> On Thu, Dec 20, 2012 at 11:46 PM, Matthew Brett >> wrote: >>> Travis - I think you are suggesting that there should be no one >>> person in charge of numpy, and I think this is very

Re: [Numpy-discussion] NaN (Not a Number) occurs in calculation of complex number for Bessel functions

On 12/21/2012 02:30 PM, Happyman wrote: > I have everything in C or Fortran...According to my friends > recommendations I started learning Python for my research... > > Do you mean the functions which gave Nan result has not been developed > properly yet in Python, Don't you The way most of Nu

Re: [Numpy-discussion] Byte aligned arrays

On 12/20/2012 03:23 PM, Francesc Alted wrote: > On 12/20/12 9:53 AM, Henry Gomersall wrote: >> On Wed, 2012-12-19 at 19:03 +0100, Francesc Alted wrote: >>> The only scenario that I see that this would create unaligned arrays >>> is >>> for machines having AVX. But provided that the Intel architect

Re: [Numpy-discussion] === I REALLY NEED YOUR HELP OUR PYTHON USERS ====

On 12/20/2012 07:32 PM, Happyman wrote: > Hi Python users, > > First of all, Marry coming Cristmas!!! ALL THE BEST TO YOU AND YOUR FAMILY > > I need solution of integration under trapz() rule: > There are following functions: > > def F1 (const1, x): >"""several calculations depending on

Re: [Numpy-discussion] DARPA funding for Blaze and passing the NumPy torch

On 12/18/2012 08:06 AM, Dag Sverre Seljebotn wrote: > On 12/18/2012 03:10 AM, Jason Grout wrote: >> On 12/16/12 11:07 PM, Travis Oliphant wrote: >>> Hello all, >>> >>> There is a lot happening in my life right now and I am spread quite >>> thin among th

Re: [Numpy-discussion] DARPA funding for Blaze and passing the NumPy torch

On 12/18/2012 03:10 AM, Jason Grout wrote: > On 12/16/12 11:07 PM, Travis Oliphant wrote: >> Hello all, >> >> There is a lot happening in my life right now and I am spread quite >> thin among the various projects that I take an interest in. In >> particular, I am thrilled to publicly announce o

Re: [Numpy-discussion] site.cfg: Custom BLAS / LAPACK configuration

On 12/13/2012 07:59 PM, David Cournapeau wrote: > On Fri, Dec 7, 2012 at 7:58 PM, Dag Sverre Seljebotn > wrote: >> One way of fixing this I'm sort of itching to do is to create a >> "pylapack" project which can iterate quickly on these build issues, >> run-

Re: [Numpy-discussion] site.cfg: Custom BLAS / LAPACK configuration

On 12/07/2012 07:58 PM, Dag Sverre Seljebotn wrote: > One way of fixing this I'm sort of itching to do is to create a > "pylapack" project which can iterate quickly on these build issues, > run-time selection of LAPACK backend and so on. (With some templates > gen

Re: [Numpy-discussion] Numpy Trac migration

On 12/06/2012 01:45 AM, Pauli Virtanen wrote: > Hi, > > For those whom it may concern: Since the Numpy Trac -> Github migration > is complete, I went ahead and added redirects > > projects.scipy.org/numpy/register -> github.com/numpy/numpy/issues > projects.scipy.org/numpy/newticket -> github.com/n

Re: [Numpy-discussion] site.cfg: Custom BLAS / LAPACK configuration

One way of fixing this I'm sort of itching to do is to create a "pylapack" project which can iterate quickly on these build issues, run-time selection of LAPACK backend and so on. (With some templates generating some Cython code it shouldn't be more than a few days for an MVP.) Then patch NumP

Re: [Numpy-discussion] Use OpenBLAS for the binary releases?

On 11/20/2012 08:35 PM, Dag Sverre Seljebotn wrote: > On 11/20/2012 06:22 PM, David Cournapeau wrote: >> On Tue, Nov 20, 2012 at 5:03 PM, Sturla Molden wrote: >>> On 20.11.2012 15:38, David Cournapeau wrote: >>> >>>> I support this as well in principle fo

Re: [Numpy-discussion] Use OpenBLAS for the binary releases?

On 11/20/2012 06:22 PM, David Cournapeau wrote: > On Tue, Nov 20, 2012 at 5:03 PM, Sturla Molden wrote: >> On 20.11.2012 15:38, David Cournapeau wrote: >> >>> I support this as well in principle for our binary release: one issue >>> is that we don't have the infrastructure on mac to build an insta

Re: [Numpy-discussion] Use OpenBLAS for the binary releases?

On 11/19/2012 06:12 PM, Sturla Molden wrote: > I think NumPy and SciPy should consider to use OpenBLAS (a fork of > GotoBLAS2) instead of ATLAS or f2c'd Netlib BLAS for the binary releases. > > Here are its virtues: > > * Very easy to build: Just a makefile, no configuration script or > special bui

Re: [Numpy-discussion] Scipy dot

On 11/09/2012 11:57 PM, Matthieu Brucher wrote: > Hi, > > A.A slower than A.A' is not a surprise for me. The latter is far more > cache friendly that the former. Everything follows cache lines, so it is > faster than something that will use one element from each cache line. In > fact it is exactly

Re: [Numpy-discussion] testing with amd libm/acml

On 11/08/2012 07:55 PM, Dag Sverre Seljebotn wrote: > On 11/08/2012 06:59 PM, Francesc Alted wrote: >> On 11/8/12 6:38 PM, Dag Sverre Seljebotn wrote: >>> On 11/08/2012 06:06 PM, Francesc Alted wrote: >>>> On 11/8/12 1:41 PM, Dag Sverre Seljebotn wrote: >>>

Re: [Numpy-discussion] testing with amd libm/acml

On 11/08/2012 06:59 PM, Francesc Alted wrote: > On 11/8/12 6:38 PM, Dag Sverre Seljebotn wrote: >> On 11/08/2012 06:06 PM, Francesc Alted wrote: >>> On 11/8/12 1:41 PM, Dag Sverre Seljebotn wrote: >>>> On 11/07/2012 08:41 PM, Neal Becker wrote: >>>>> W

Re: [Numpy-discussion] testing with amd libm/acml

On 11/08/2012 06:06 PM, Francesc Alted wrote: > On 11/8/12 1:41 PM, Dag Sverre Seljebotn wrote: >> On 11/07/2012 08:41 PM, Neal Becker wrote: >>> Would you expect numexpr without MKL to give a significant boost? >> If you need higher performance than what numexpr can give w

Re: [Numpy-discussion] testing with amd libm/acml

On 11/07/2012 08:41 PM, Neal Becker wrote: > Would you expect numexpr without MKL to give a significant boost? If you need higher performance than what numexpr can give without using MKL, you could look at code such as this: https://github.com/herumi/fmath/blob/master/fmath.hpp#L480 But that me

Re: [Numpy-discussion] Scipy dot

On 11/08/2012 01:07 PM, Gael Varoquaux wrote: > On Thu, Nov 08, 2012 at 11:28:21AM +, Nathaniel Smith wrote: >> I think everyone would be very happy to see numpy.dot modified to do >> this automatically. But adding a scipy.dot IMHO would be fixing things >> in the wrong place and just create ex

Re: [Numpy-discussion] testing with amd libm/acml

On 11/07/2012 03:30 PM, Neal Becker wrote: > David Cournapeau wrote: > >> On Wed, Nov 7, 2012 at 1:56 PM, Neal Becker wrote: >>> David Cournapeau wrote: >>> On Wed, Nov 7, 2012 at 12:35 PM, Neal Becker wrote: > I'm trying to do a bit of benchmarking to see if amd libm/acml will help

Re: [Numpy-discussion] how to pipe into numpy arrays?

On 10/25/2012 08:17 AM, Dag Sverre Seljebotn wrote: > On 10/24/2012 09: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

Re: [Numpy-discussion] how to pipe into numpy arrays?

On 10/24/2012 09: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 but the >

Re: [Numpy-discussion] A change with minor compatibility questions

On 10/17/2012 06:56 PM, Dag Sverre Seljebotn wrote: > On 10/17/2012 05:22 PM, Travis Oliphant wrote: >> Hey all, >> >> https://github.com/numpy/numpy/pull/482 >> >> is a pull request that changes the hash function for numpy void >> scalars. These are the

Re: [Numpy-discussion] A change with minor compatibility questions

On 10/17/2012 05:22 PM, Travis Oliphant wrote: > Hey all, > > https://github.com/numpy/numpy/pull/482 > > is a pull request that changes the hash function for numpy void > scalars. These are the objects returned from fully indexing a > structured array: array[i] if array is a 1-d structured arr

Re: [Numpy-discussion] How to copy data from a C array to a numpy array efficiently?

On 10/07/2012 08:48 AM, Dag Sverre Seljebotn wrote: > On 10/07/2012 08:41 AM, Jianbao Tao wrote: >> Hi, >> >> I am developing a Python wrapper of the NASA CDF C library in Cython. I >> have got a working version of it now, but it is slower than the >> counterpart

Re: [Numpy-discussion] How to copy data from a C array to a numpy array efficiently?

On 10/07/2012 08:41 AM, Jianbao Tao wrote: > Hi, > > I am developing a Python wrapper of the NASA CDF C library in Cython. I > have got a working version of it now, but it is slower than the > counterpart in IDL. For loading the same file, mine takes about 400 ms, > whereas the IDL version takes ab

Re: [Numpy-discussion] Behavior of .base

On 10/01/2012 04:56 PM, Charles R Harris wrote: > > > On Mon, Oct 1, 2012 at 8:40 AM, Thouis (Ray) Jones > wrote: > > On Mon, Oct 1, 2012 at 8:20 AM, Nathaniel Smith > wrote: > > [...] > > How can we discourage people from doing th

Re: [Numpy-discussion] How to debug reference counting errors

On 08/31/2012 09:03 AM, Ondřej Čertík wrote: > Hi, > > There is segfault reported here: > > http://projects.scipy.org/numpy/ticket/1588 > > I've managed to isolate the problem and even provide a simple patch, > that fixes it here: > > https://github.com/numpy/numpy/issues/398 > > however the patch

[Numpy-discussion] Mark Florisson's GSoC, minivect, and NumPy

I just wanted to draw the attention of NumPy devs to Mark Florisson's GSoC work. It is 'minivect', a tool to use for compiling array expressions (think (as a concept) a shared backend between Cython, Theano, numba, though it's only used in Cython currently). His M. Sc. thesis, "Techniques for

Re: [Numpy-discussion] how to use numpy-vendor

On 08/14/2012 06:34 AM, Ondřej Čertík wrote: > Hi, > > How should one use the "vendor" repository (https://github.com/numpy/vendor) > in Wine? Should I put the binaries into .wine/drive_c/Python25/libs/, > or somewhere else? > I've search all mailinglists and I didn't find any information on it. >

Re: [Numpy-discussion] Moving away from using accelerate framework on mac os x ?

On 08/04/2012 01:14 PM, Aron Ahmadia wrote: > Hi David, > > Apple's response here is somewhat confusing, but I will add that on the > supercomputing side of things we rarely fork, as this is not > well-supported from the vendors or the hardware (it's hard enough to > performantly spawn 500,000 proc

Re: [Numpy-discussion] Licensing question

On 08/02/2012 10:44 PM, Damon McDougall wrote: > Hi, > > I have a question about the licence for NumPy's codebase. I am currently > writing a library and I'd like to release under some BSD-type licence. > Unfortunately, my choice to link against MIT's FFTW library (released > under the GPL) means t

Re: [Numpy-discussion] Extracting sub-fields from an array as a view (PR 350)

On 07/15/2012 12:31 AM, Travis Oliphant wrote: > > In https://github.com/numpy/numpy/pull/350/files , > > javius provides a patch to allow field extraction from a structured > array to return a view instead of a copy. Generally, this is consistent > with the desire to have NumPy return views whenev

Re: [Numpy-discussion] SSE Optimization

Some more context over what Francesc said: If you mean using SSE for simple things like addition and multiplication, then you must be aware that NumPy's way of working means that it lends itself very badly to such optimizations. For small arrays, the Python interpreter overhead tends to dominat

Re: [Numpy-discussion] Meta: help, devel and stackoverflow

On 06/30/2012 09:37 PM, Matthew Brett wrote: > Hi, > > On Sat, Jun 30, 2012 at 12:29 PM, John Hunter wrote: >> >> >> On Fri, Jun 29, 2012 at 2:20 PM, Jim Vickroy wrote: >>> >>> As a lurker and user, I too wish for a distinct numpy-users list. -- jv >>> >> >> This thread is a perfect example of w

Re: [Numpy-discussion] Meta: help, devel and stackoverflow

On 06/30/2012 08:44 PM, Fernando Perez wrote: > On Sat, Jun 30, 2012 at 11:36 AM, Dag Sverre Seljebotn > wrote: >> It is rumored that a problem with some stackexchange sites is the host >> of nay-sayers saying that a question doesn't belong here but in this >> other

Re: [Numpy-discussion] Meta: help, devel and stackoverflow

On 06/30/2012 07:31 PM, Fernando Perez wrote: > On Sat, Jun 30, 2012 at 10:13 AM, Jason Grout > wrote: >> >> I'm curious: do you mean using stackexchange.com itself, or using >> http://scicomp.stackexchange.com/ specifically? > > I meant the latter, which seems like it would be the best suited fo

Re: [Numpy-discussion] Meta: help, devel and stackoverflow

+1 on scicomp.stackexchange.com For it to work, one would need to actively push users towards it though...so it would require a very clear pronouncement. Matthew: I'm happy with the split we did with Cython. It leaves me free to mostly ignore cython-users, and it saves users from thos 100+ post

Re: [Numpy-discussion] Combined versus separate build

On 06/27/2012 09:53 PM, Nathaniel Smith wrote: > On Wed, Jun 27, 2012 at 8:29 PM, David Cournapeau wrote: >> On Wed, Jun 27, 2012 at 8:07 PM, Nathaniel Smith wrote: >>> On Wed, Jun 27, 2012 at 7:50 PM, David Cournapeau >>> wrote: On Wed, Jun 27, 2012 at 7:17 PM, Nathaniel Smith wrote: >>>

Re: [Numpy-discussion] moving forward around ABI/API compatibilities (was numpy 1.7.x branch)

On 06/26/2012 10:35 PM, Dag Sverre Seljebotn wrote: > On 06/26/2012 05:02 PM, Travis Oliphant wrote: >>>> >>>> (I have not read the whole cython discussion yet) >>> >>> So here's the summary. It's rather complicated but also incredibly ne

Re: [Numpy-discussion] moving forward around ABI/API compatibilities (was numpy 1.7.x branch)

On 06/26/2012 05:02 PM, Travis Oliphant wrote: >>> >>> (I have not read the whole cython discussion yet) >> >> So here's the summary. It's rather complicated but also incredibly neat >> :-) And technical details can be hidden behind a tight API. > > Could you provide a bit more context for this lis

Re: [Numpy-discussion] Created NumPy 1.7.x branch

On 06/26/2012 09:51 PM, Travis Oliphant wrote: >> >> Exactly. >> >> I don't >> feel responsible for this issue (except I maybe should have pushed >> more strongly about datetime being included), >> >> >> I think you left out a 'not'. I don't mean to imply that you were in >> anyway the

Re: [Numpy-discussion] moving forward around ABI/API compatibilities (was numpy 1.7.x branch)

On 06/26/2012 04:08 PM, Dag Sverre Seljebotn wrote: > On 06/26/2012 01:48 PM, David Cournapeau wrote: >> Hi, >> >> I am just continuing the discussion around ABI/API, the technical side >> of things that is, as this is unrelated to 1.7.x. release. >> >> On Tu

Re: [Numpy-discussion] moving forward around ABI/API compatibilities (was numpy 1.7.x branch)

On 06/26/2012 01:48 PM, David Cournapeau wrote: > Hi, > > I am just continuing the discussion around ABI/API, the technical side > of things that is, as this is unrelated to 1.7.x. release. > > On Tue, Jun 26, 2012 at 11:41 AM, Dag Sverre Seljebotn > wrote: >> On

Re: [Numpy-discussion] moving forward around ABI/API compatibilities (was numpy 1.7.x branch)

On 06/26/2012 01:48 PM, David Cournapeau wrote: > Hi, > > I am just continuing the discussion around ABI/API, the technical side > of things that is, as this is unrelated to 1.7.x. release. > > On Tue, Jun 26, 2012 at 11:41 AM, Dag Sverre Seljebotn > wrote: >> On

Re: [Numpy-discussion] Created NumPy 1.7.x branch

On 06/26/2012 11:58 AM, David Cournapeau wrote: > On Tue, Jun 26, 2012 at 10:27 AM, Dag Sverre Seljebotn > wrote: >> On 06/26/2012 05:35 AM, David Cournapeau wrote: >>> On Tue, Jun 26, 2012 at 4:10 AM, Ondřej Čertík >>> wrote: >>> >>>> >&

Re: [Numpy-discussion] Created NumPy 1.7.x branch

On 06/26/2012 05:35 AM, David Cournapeau wrote: > On Tue, Jun 26, 2012 at 4:10 AM, Ondřej Čertík > wrote: > >> >> My understanding is that Travis is simply trying to stress "We have to >> think about the implications of our changes on existing users." and >> also that little changes (with the bes

Re: [Numpy-discussion] Created NumPy 1.7.x branch

On 06/23/2012 09:32 AM, Dag Sverre Seljebotn wrote: > On 06/23/2012 05:14 AM, Charles R Harris wrote: >> >> >> On Fri, Jun 22, 2012 at 2:42 PM, Travis Oliphant> <mailto:tra...@continuum.io>> wrote: >> >>> >>> The usual practice is to

Re: [Numpy-discussion] Created NumPy 1.7.x branch

On 06/23/2012 05:14 AM, Charles R Harris wrote: > > > On Fri, Jun 22, 2012 at 2:42 PM, Travis Oliphant > wrote: > >> >> The usual practice is to announce a schedule first. > > I just did announce the schedule. > > > What has been done in the past is that an inte

Re: [Numpy-discussion] numpy allocation event hooks

On 06/18/2012 12:14 PM, Thouis (Ray) Jones wrote: > Based on some previous discussion on the numpy list [1] and in > now-cancelled PRs [2,3], I'd like to solicit opinions on adding an > interface for numpy memory allocation event tracking, as implemented > in this PR: > > https://github.com/numpy/n

Re: [Numpy-discussion] Enum/Factor NEP (now with code)

On 06/14/2012 12:06 AM, Bryan Van de Ven wrote: > On 6/13/12 1:12 PM, Nathaniel Smith wrote: >> your-branch's-base-master but not in your-repo's-master are new stuff >> that you did on your branch. Solution is just to do >> git push master > > Fixed, thanks. > >> Yes, of course we *could* wri

Re: [Numpy-discussion] Enum/Factor NEP (now with code)

Nathaniel Smith wrote: >On Wed, Jun 13, 2012 at 5:04 PM, Dag Sverre Seljebotn > wrote: >> On 06/13/2012 03:33 PM, Nathaniel Smith wrote: >>> I'm inclined to say therefore that we should just drop the "open >type" >>> idea, since it adds co

Re: [Numpy-discussion] Enum/Factor NEP (now with code)

On 06/13/2012 03:33 PM, Nathaniel Smith wrote: > On Tue, Jun 12, 2012 at 10:27 PM, Bryan Van de Ven > wrote: >> Hi all, >> >> It has been some time, but I do have an update regarding this proposed >> feature. I thought it would be helpful to flesh out some parts of a >> possible implementation to

Re: [Numpy-discussion] lazy evaluation

On 06/06/2012 12:06 AM, mark florisson wrote: > On 5 June 2012 22:36, Dag Sverre Seljebotn wrote: >> On 06/05/2012 10:47 PM, mark florisson wrote: >>> On 5 June 2012 20:17, Nathaniel Smithwrote: >>>> On Tue, Jun 5, 2012 at 7:08 PM, mark florisson >>>

Re: [Numpy-discussion] lazy evaluation

On 06/05/2012 10:47 PM, mark florisson wrote: > On 5 June 2012 20:17, Nathaniel Smith wrote: >> On Tue, Jun 5, 2012 at 7:08 PM, mark florisson >> wrote: >>> On 5 June 2012 17:38, Nathaniel Smith wrote: On Tue, Jun 5, 2012 at 4:12 PM, mark florisson wrote: > On 5 June 2012 14:58,

Re: [Numpy-discussion] Changes in PyArray_FromAny between 1.5.x and 1.6.x

On 06/04/2012 09:06 PM, Mike Hansen wrote: > On Mon, May 28, 2012 at 3:15 AM, Mike Hansen wrote: >> In trying to upgrade NumPy within Sage, we notices some differences in >> behavior between 1.5 and 1.6. In particular, in 1.5, we have >> >> sage: f = 0.5 >> sage: f.__array_interface__ >> {'typest

Re: [Numpy-discussion] pre-PEP for making creative forking of NumPy less destructive

On 05/18/2012 01:48 PM, mark florisson wrote: > On 17 May 2012 23:53, Dag Sverre Seljebotn wrote: >> I'm repeating myself a bit, but my previous thread of this ended up >> being about something else, and also since then I've been on an >> expedition to the hostile

Re: [Numpy-discussion] Checking for views

On 05/25/2012 03:17 PM, Robert Kern wrote: > On Thu, May 24, 2012 at 5:52 PM, Robert Kern wrote: > >> (Hmm, now that I think about it, the edge cases are when the strides >> are 0 or negative. 0-stride axes can simply be removed, and I think we >> should be able to work back to a first item and fl

Re: [Numpy-discussion] Should arr.diagonal() return a copy or a view? (1.7 compatibility issue)

On 05/23/2012 10:00 PM, Dag Sverre Seljebotn wrote: > On 05/23/2012 07:29 PM, Travis Oliphant wrote: >> >> On May 23, 2012, at 8:02 AM, Olivier Delalleau wrote: >> >>> 2012/5/23 Nathaniel Smithmailto:n...@pobox.com>> >>> >>> On Wed, May 23

Re: [Numpy-discussion] Should arr.diagonal() return a copy or a view? (1.7 compatibility issue)

On 05/23/2012 07:29 PM, Travis Oliphant wrote: > > On May 23, 2012, at 8:02 AM, Olivier Delalleau wrote: > >> 2012/5/23 Nathaniel Smith mailto:n...@pobox.com>> >> >> On Wed, May 23, 2012 at 6:06 AM, Travis Oliphant >> mailto:tra...@continuum.io>> wrote: >> > I just realized that the pul

Re: [Numpy-discussion] question about in-place operations

On 05/22/2012 04:54 PM, Massimo DiPierro wrote: > For now I will be doing this: > > import numpy > import time > > a=numpy.zeros(200) > b=numpy.zeros(200) > c=1.0 > > # naive solution > t0 = time.time() > for i in xrange(len(a)): > a[i] += c*b[i] > print time.time()-t0 > > # possible s

Re: [Numpy-discussion] question about in-place operations

On 05/22/2012 04:25 PM, Massimo DiPierro wrote: > hello everybody, > > first of all thanks to the developed for bumpy which is very useful. I am > building a software that uses numpy+pyopencl for lattice qcd computations. > One problem that I am facing is that I need to perform most operations on

Re: [Numpy-discussion] un-silencing Numpy's deprecation warnings

On 05/22/2012 12:06 PM, Robert Kern wrote: > On Tue, May 22, 2012 at 9:27 AM, Nathaniel Smith wrote: >> So starting in Python 2.7 and 3.2, the Python developers have made >> DeprecationWarnings invisible by default: >> http://docs.python.org/whatsnew/2.7.html#the-future-for-python-2-x >> http:

Re: [Numpy-discussion] Masked Array for NumPy 1.7

Travis Oliphant wrote: >Hey all, > >After reading all the discussion around masked arrays and getting input >from as many people as possible, it is clear that there is still >disagreement about what to do, but there have been some fruitful >discussions that ensued. > >This isn't really new as

  1   2   3   4   5   >