Re: [Numpy-discussion] [SciPy-Dev] ANN: first release candidate for scipy 0.17.0

Hi, On Wed, Dec 23, 2015 at 12:34 PM, Evgeni Burovski wrote: > Hi, > > I'm pleased to announce the availability of the first release > candidate for Scipy 0.17.0. Please try this rc and report any issues > on Github tracker or scipy-dev mailing list. > Source tarballs

Re: [Numpy-discussion] Proposal: stop providing official win32 downloads (for now)

On Tue, Dec 22, 2015 at 7:22 PM, Chris Barker wrote: > On Tue, Dec 22, 2015 at 11:18 AM, David Cournapeau > wrote: >>> >>> Any way to know how many people are running 32 bit Python on Windows >>> these days?? >> >> >> I don't claim we are representative

Re: [Numpy-discussion] Proposal: stop providing official win32 downloads (for now)

On Tue, Dec 22, 2015 at 7:38 PM, Chris Barker <chris.bar...@noaa.gov> wrote: > On Tue, Dec 22, 2015 at 11:32 AM, Matthew Brett <matthew.br...@gmail.com> > wrote: >> >> The take-home is that about 12 percent of gamers have 32 bit Windows. >> It's easy to believe

Re: [Numpy-discussion] performance solving system of equations in numpy and MATLAB

Hi, On Wed, Dec 16, 2015 at 6:34 PM, Edison Gustavo Muenz wrote: > Sometime ago I saw this: https://software.intel.com/sites/campaigns/nest/ > > I don't know if the "community" license applies in your case though. It is > worth taking a look at. > > On Wed, Dec 16, 2015

Re: [Numpy-discussion] array of random numbers fails to construct

Hi, On Tue, Dec 8, 2015 at 4:40 PM, Stephan Hoyer wrote: > On Sun, Dec 6, 2015 at 3:55 PM, Allan Haldane > wrote: >> >> >> I've also often wanted to generate large datasets of random uint8 and >> uint16. As a workaround, this is something I have used:

Re: [Numpy-discussion] array of random numbers fails to construct

Hi, On Sun, Dec 6, 2015 at 12:39 PM, DAVID SAROFF (RIT Student) wrote: > This works. A big array of eight bit random numbers is constructed: > > import numpy as np > > spectrumArray = np.random.randint(0,255, (2**20,2**12)).astype(np.uint8) > > > > This fails. It eats up all

Re: [Numpy-discussion] Removiing 1.10.0 and 1.10.1 from sourceforge and pypi

Hi, On Fri, Nov 13, 2015 at 10:06 AM, Charles R Harris wrote: > Hi All, > > I think 1.10.0 and 1.10.1 are sufficiently buggy that they should be removed > from circulation as soon as 1.10.2 comes out. The inner product bug for non > contiguous arrays is particularly

Re: [Numpy-discussion] Numpy 1.10.1 released.

Hi, On Mon, Oct 12, 2015 at 9:27 AM, Charles R Harris wrote: > Hi All, > > I'm pleased to announce the release of Numpy 1.10.1. This release fixes some > build problems and serves to reset the release number on pipy to something > usable. As a note for future release

Re: [Numpy-discussion] Oops - maybe post3 numpy file?

On Fri, Oct 9, 2015 at 7:43 AM, Charles R Harris <charlesr.har...@gmail.com> wrote: > > > On Fri, Oct 9, 2015 at 4:28 AM, Ralf Gommers <ralf.gomm...@gmail.com> wrote: >> >> >> >> On Fri, Oct 9, 2015 at 4:45 AM, Matthew Brett <matthew.br...@gmail.

[Numpy-discussion] Oops - maybe post3 numpy file?

Hi, I'm afraid I made a mistake uploading OSX wheels for numpy 1.10.0. Using twine to do the upload generated a new release - 1.10.0.post2 - containing only the wheels. I deleted that new release to avoid confusion, but now, when I try and upload the wheels to the 1.10.0 pypi release via the web

Re: [Numpy-discussion] Oops - maybe post3 numpy file?

gt;> wrote: >> > >> > On Thu, Oct 8, 2015 at 6:30 PM, Matthew Brett <matthew.br...@gmail.com> >> > wrote: >> >> >> >> Hi, >> >> >> >> I'm afraid I made a mistake uploading OSX wheels for numpy 1.10.0. >> &

Re: [Numpy-discussion] [pydata] ANN: pandas v0.17.0rc2 - RELEASE CANDIDATE 2

Hi, On Sat, Oct 3, 2015 at 2:33 PM, Jeff Reback wrote: > Hi, > > I'm pleased to announce the availability of the second release candidate of > Pandas 0.17.0. > Please try this RC and report any issues here: Pandas Issues > We will be releasing officially on October 9. > >

Re: [Numpy-discussion] Tentative numpy tutorial

Hi, On Wed, Sep 23, 2015 at 2:25 AM, Dan Patterson wrote: > Bryan is this the tutorial to which you refer? > http://docs.scipy.org/doc/scipy/reference/tutorial/index.html > ___ I think it is the

Re: [Numpy-discussion] Governance model request

On Wed, Sep 23, 2015 at 3:08 PM, Fernando Perez <fperez@gmail.com> wrote: > > On Wed, Sep 23, 2015 at 2:32 PM, Matthew Brett <matthew.br...@gmail.com> > wrote: >> >> Did you see any remark made by me or Stefan or anyone else that could >> reasona

Re: [Numpy-discussion] Governance model request

Hi, On Wed, Sep 23, 2015 at 1:36 PM, Fernando Perez <fperez@gmail.com> wrote: > On Wed, Sep 23, 2015 at 12:57 PM, Matthew Brett <matthew.br...@gmail.com> > wrote: >> >> I see a severe reaction to perceived 'suspicion and innuendo', but I >> see no 'suspi

Re: [Numpy-discussion] Governance model request

Hi, On Wed, Sep 23, 2015 at 1:02 AM, Fernando Perez wrote: [snip] > 1. I hope the discussion can move past the suspicion and innuendo about > Continuum and Travis I'm glad the discussion has become a little more calm now, but I find it difficult not to be annoyed by this

Re: [Numpy-discussion] Plan for 1.9.4 release

Hi, On Wed, Sep 23, 2015 at 5:30 PM, Fernando Perez wrote: > Chance this will be merged into 1.10? I know there's an rc floating out > there for 1.10, and this sounds like an actual bug... Would be great to > have a solid 1.10 for the 3.5 crowd :) 1.10 already contains

Re: [Numpy-discussion] Governance model request

Hi, On Tue, Sep 22, 2015 at 11:20 AM, Stefan van der Walt wrote: > Hi Travis > > On 2015-09-22 03:44:12, Travis Oliphant wrote: >> I'm actually offended that so many at BIDS seem eager to crucify my >> intentions when I've done nothing but give away my

[Numpy-discussion] ANN: Numpy 1.9.3 bugfix release

ng_double_representation; * `#6141 <https://github.com/numpy/numpy/pull/6141>`__: enable Visual Studio 2015 C99 features; * `#6171 <https://github.com/numpy/numpy/pull/6171>`__: revert C99 complex for MSVC14. Cheers, Matthew Brett - for the numpy developers.

Re: [Numpy-discussion] Governance model request

Hi Travis, and all, You might have seen I was advocating for having someone who takes final responsibility for the project, partly to get discussions unstuck, as you said. I agree with Chris, that at this stage, there is no-one who could be Benevolent Dictator for the project. It seems to me

Re: [Numpy-discussion] OK to upload patched 1.9.2 for Python 3.5?

On Mon, Sep 14, 2015 at 9:42 AM, Matthew Brett <matthew.br...@gmail.com> wrote: > On Mon, Sep 14, 2015 at 3:47 AM, Julian Taylor > <jtaylor.deb...@googlemail.com> wrote: >> as due to the many incompatiblities in 1.10 many will likely not be able >> to update anytim

Re: [Numpy-discussion] OK to upload patched 1.9.2 for Python 3.5?

On Mon, Sep 14, 2015 at 3:47 AM, Julian Taylor wrote: > as due to the many incompatiblities in 1.10 many will likely not be able > to update anytime soon, so I think putting out another 1.9.3 bugfix > release would be a good idea. > I can probably do the release

Re: [Numpy-discussion] First release candidate for the 1.5.0 series

Hi, On Mon, Sep 14, 2015 at 8:59 PM, Thomas Caswell wrote: > Please give it a try! (linux64 conda builds are available on the tacaswell > anaconda.org channel) > > https://github.com/matplotlib/matplotlib/releases/tag/v1.5.0rc1 > > This release contains many new features.

Re: [Numpy-discussion] OK to upload patched 1.9.2 for Python 3.5?

;>> Carlkl >>> >>> 2015-09-14 10:46 GMT+02:00 Robert Kern <robert.k...@gmail.com >>> <mailto:robert.k...@gmail.com>>: >>> >>> On Mon, Sep 14, 2015 at 9:32 AM, Matthew Brett >>> <matthew.br...@gmail.com <mail

[Numpy-discussion] OK to upload patched 1.9.2 for Python 3.5?

Hi, I'm just building numpy 1.9.2 for Python 3.5 (just released). In order to get the tests to pass on Python 3.5, I need to cherry pick commit 7d6aa8c onto the 1.9.2 tag position. Does anyone object to me uploading a wheel built from this patched version to pypi as 1.9.2 for Python 3.5 on OSX?

Re: [Numpy-discussion] OK to upload patched 1.9.2 for Python 3.5?

Hi, On Mon, Sep 14, 2015 at 1:22 AM, David Cournapeau <courn...@gmail.com> wrote: > > > On Mon, Sep 14, 2015 at 9:18 AM, Matthew Brett <matthew.br...@gmail.com> > wrote: >> >> Hi, >> >> I'm just building numpy 1.9.2 for Python 3.5 (just released). &

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

that kind of debate. That brings us to my next comment: On Fri, Sep 4, 2015 at 8:35 PM, Nathaniel Smith <n...@pobox.com> wrote: > On Fri, Aug 28, 2015 at 1:46 AM, Matthew Brett <matthew.br...@gmail.com> > wrote: >> Hi, >> >> On Fri, Aug 28, 2015 at 5:59 AM, Jaime F

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

On Sat, Sep 5, 2015 at 7:14 PM, Nathaniel Smith <n...@pobox.com> wrote: > On Sat, Sep 5, 2015 at 4:20 PM, Matthew Brett <matthew.br...@gmail.com> wrote: >> Hi, >> >> Thanks for replying, that is helpful. >> >> I'm going to write carefully, beca

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

On Fri, Sep 4, 2015 at 2:33 AM, Matthew Brett <matthew.br...@gmail.com> wrote: > Hi, > > On Wed, Sep 2, 2015 at 5:41 PM, Chris Barker <chris.bar...@noaa.gov> wrote: >> 1) I very much agree that governance can make or break a project. However, >> the actual governa

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

On Sat, Sep 5, 2015 at 12:04 AM, <josef.p...@gmail.com> wrote: > > > On Fri, Sep 4, 2015 at 5:55 PM, Matthew Brett <matthew.br...@gmail.com> > wrote: >> >> Hi, >> >> On Fri, Sep 4, 2015 at 10:22 PM, Eric Firing <efir...@hawaii.edu> w

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi, On Fri, Sep 4, 2015 at 10:22 PM, Eric Firing <efir...@hawaii.edu> wrote: > On 2015/09/04 10:53 AM, Matthew Brett wrote: >> On Fri, Sep 4, 2015 at 2:33 AM, Matthew Brett <matthew.br...@gmail.com> >> wrote: >>> Hi, >>> >>> On Wed, Sep 2

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

On Sat, Sep 5, 2015 at 12:47 AM, <josef.p...@gmail.com> wrote: > > > On Fri, Sep 4, 2015 at 7:19 PM, Matthew Brett <matthew.br...@gmail.com> > wrote: >> >> On Sat, Sep 5, 2015 at 12:04 AM, <josef.p...@gmail.com> wrote: >> > >> > &g

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi, On Wed, Sep 2, 2015 at 5:41 PM, Chris Barker wrote: > 1) I very much agree that governance can make or break a project. However, > the actual governance approach often ends up making less difference than the > people involved. > > 2) While the FreeBSD and XFree

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi, On Thu, Aug 27, 2015 at 12:11 PM, Sebastian Berg sebast...@sipsolutions.net wrote: On Do, 2015-08-27 at 10:45 +0100, Matthew Brett wrote: Hi, On Thu, Aug 27, 2015 at 10:35 AM, Bryan Van de Ven bry...@continuum.io wrote: On Aug 27, 2015, at 10:22 AM, Matthew Brett matthew.br

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi On Thu, Aug 27, 2015 at 5:11 PM, josef.p...@gmail.com wrote: On Thu, Aug 27, 2015 at 11:04 AM, Matthew Brett matthew.br...@gmail.com wrote: Hi, On Thu, Aug 27, 2015 at 3:34 PM, josef.p...@gmail.com wrote: [snip] I don't really see a problem with codifying the status quo. That's

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi, On Thu, Aug 27, 2015 at 3:34 PM, josef.p...@gmail.com wrote: [snip] I don't really see a problem with codifying the status quo. That's an excellent point.If we believe that the current situation is the best possible, both now and in the future, then codifying the status quo is an

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi, On Thu, Aug 27, 2015 at 3:43 PM, Bryan Van de Ven bry...@continuum.io wrote: On Aug 27, 2015, at 1:57 PM, Matthew Brett matthew.br...@gmail.com wrote: The 'president' idea ...seems to be predicated on a steady stream of people who: actually want job, don't mind campaigning

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi, On Thu, Aug 27, 2015 at 10:35 AM, Bryan Van de Ven bry...@continuum.io wrote: On Aug 27, 2015, at 10:22 AM, Matthew Brett matthew.br...@gmail.com wrote: In the case of the 'core' model, we have some compelling testimony from someone with a great deal of experience: Much of this early

Re: [Numpy-discussion] [DRAFT] numpy governance document

Hi, On Thu, Aug 27, 2015 at 11:10 AM, Nathaniel Smith n...@pobox.com wrote: On Thu, Aug 27, 2015 at 1:44 AM, Matthew Brett matthew.br...@gmail.com wrote: Hi, On Thu, Aug 27, 2015 at 7:33 AM, Nathaniel Smith n...@pobox.com wrote: Hi all, Here's a first draft of a governance document

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi, On Thu, Aug 27, 2015 at 11:05 AM, Nathaniel Smith n...@pobox.com wrote: On Thu, Aug 27, 2015 at 2:16 AM, Matthew Brett matthew.br...@gmail.com wrote: So, I speculate, that a good governance model would have: * one 'president' who has to take final responsibility for all decisions

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

On Thu, Aug 27, 2015 at 9:36 AM, Matthew Brett matthew.br...@gmail.com wrote: Hi, On Wed, Aug 26, 2015 at 11:46 PM, Stefan van der Walt stef...@berkeley.edu wrote: Hi Matthew On 2015-08-26 10:50:47, Matthew Brett matthew.br...@gmail.com wrote: In short, the core structure seems

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi, On Thu, Aug 27, 2015 at 10:15 AM, Bryan Van de Ven bry...@continuum.io wrote: On Aug 27, 2015, at 9:36 AM, Matthew Brett matthew.br...@gmail.com wrote: So, in answer to your question, it's difficult to know if a particular governance model is successful. It isn't enough that a project

Re: [Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi, On Wed, Aug 26, 2015 at 11:46 PM, Stefan van der Walt stef...@berkeley.edu wrote: Hi Matthew On 2015-08-26 10:50:47, Matthew Brett matthew.br...@gmail.com wrote: In short, the core structure seems to be characteristically associated with a conservatism and lack of vision that causes

Re: [Numpy-discussion] [DRAFT] numpy governance document

Hi, On Thu, Aug 27, 2015 at 7:33 AM, Nathaniel Smith n...@pobox.com wrote: Hi all, Here's a first draft of a governance document for NumPy. Thanks for this. I wasn't sure from your email whether you were asking for feedback as to whether this was the right governance model? I mean that -

[Numpy-discussion] Comments on governance proposal (was: Notes from the numpy dev meeting at scipy 2015)

Hi, Splitting this one off too because it's a rather different discussion, although related. On Tue, Aug 25, 2015 at 11:03 AM, Nathaniel Smith n...@pobox.com wrote: [snip] Formalizing our governance/decision making == This was a major focus of

Re: [Numpy-discussion] testing numpy with downstream testsuites (was: Re: Notes from the numpy dev meeting at scipy 2015)

less often in the future ;-). One simple way to get going would be for the release manager to trigger a build from this repo: https://github.com/matthew-brett/travis-wheel-builder This build would then upload a wheel to: http://travis-wheels.scikit-image.org/ The upstream packages would have

Re: [Numpy-discussion] [SciPy-Dev] ANN: Numpy 1.10.0b1 release

Hi, On Wed, Aug 12, 2015 at 12:23 PM, Sebastian Berg sebast...@sipsolutions.net wrote: On Mi, 2015-08-12 at 01:07 -0700, Nathaniel Smith wrote: On Wed, Aug 12, 2015 at 12:51 AM, Sebastian Berg sebast...@sipsolutions.net wrote: On Mi, 2015-08-12 at 09:41 +0200, Jens Jørgen Mortensen wrote:

Re: [Numpy-discussion] [SciPy-Dev] ANN: Numpy 1.10.0b1 release

On Thu, Aug 13, 2015 at 1:04 PM, Matthew Brett matthew.br...@gmail.com wrote: Hi, On Wed, Aug 12, 2015 at 12:23 PM, Sebastian Berg sebast...@sipsolutions.net wrote: On Mi, 2015-08-12 at 01:07 -0700, Nathaniel Smith wrote: On Wed, Aug 12, 2015 at 12:51 AM, Sebastian Berg sebast

Re: [Numpy-discussion] Change default order to Fortran order

Hi, On Mon, Aug 3, 2015 at 3:13 PM, Gregory Lee grle...@gmail.com wrote: I agree that often you don't need to worry about the memory order. However, it is not uncommon in medical imaging to go back and forth between a 2D or 3D image representation and a 1D array representation (e.g. as often

Re: [Numpy-discussion] Change default order to Fortran order

On Mon, Aug 3, 2015 at 5:01 PM, Sturla Molden sturla.mol...@gmail.com wrote: Matthew Brett matthew.br...@gmail.com wrote: Sure, but to avoid confusion, maybe move the discussion of image indexing order to another thread? I think this thread is about memory layout, which is a different issue

Re: [Numpy-discussion] Change default order to Fortran order

Hi, On Mon, Aug 3, 2015 at 8:09 AM, Nathaniel Smith n...@pobox.com wrote: On Aug 2, 2015 11:06 PM, Kang Wang kwan...@wisc.edu wrote: This is very good discussion. Thank you all for replying. I can see the fundamental difference is that I always think/talk/read/write a 3D image as I(x, y,

Re: [Numpy-discussion] np.nonzero - order guarantees?

On Tue, Jul 28, 2015 at 4:45 PM, Sebastian Berg sebast...@sipsolutions.net wrote: Yes, I think it is guaranteed C order in the results. On Mon Jul 27 14:05:01 2015 GMT+0200, Matthew Brett wrote: Hi, `np.nonzero` for a 2D array `A` returns: row_inds, col_inds = np.nonzero(A) I notice

[Numpy-discussion] np.nonzero - order guarantees?

Hi, `np.nonzero` for a 2D array `A` returns: row_inds, col_inds = np.nonzero(A) I notice that `row_inds` appears to be sorted by value, and `col_inds` appears to be sorted by value, within each row. Is this a guarantee of the `np.nonzero` function? If not, does this function guarantee any

Re: [Numpy-discussion] Rationale for integer promotion rules

On Thu, Jul 16, 2015 at 7:14 PM, Nathaniel Smith n...@pobox.com wrote: On Thu, Jul 16, 2015 at 9:18 AM, Antoine Pitrou solip...@pitrou.net wrote: Hi, We were discussion integer promotion rules amongst the Numba team, and we were wondering about the rationale for Numpy's rules. For example,

Re: [Numpy-discussion] Numpy V1.4.1 software license

Hi, On Wed, Jul 8, 2015 at 4:53 PM, Nguyen, Theresa X theresa.x.ngu...@lmco.com wrote: Dear Sir/Madam, Currently, I have a chance to review the software Numpy V1.4.1, I found some software that they had the Copyright but *no License* show as below: 1. File:

Re: [Numpy-discussion] webinterface down

Hi, On Mon, Jul 6, 2015 at 7:35 PM, Valentin Haenel valen...@haenel.co wrote: Hi, the webinterface at: http://mail.scipy.org/mailman/listinfo/numpy-discussion seems down for me. For anyone else too? Works for me now - but we had enough troubles with the mailman interface for

Re: [Numpy-discussion] Strategy for OpenBLAS

Hi, On 5/27/15, Nathaniel Smith n...@pobox.com wrote: On Tue, May 26, 2015 at 7:56 AM, Matthew Brett matthew.br...@gmail.com wrote: Hi, This morning I was wondering whether we ought to plan to devote some resources to collaborating with the OpenBLAS team. Sounds like a great idea to me

Re: [Numpy-discussion] Strategy for OpenBLAS

Hi, On Tue, May 26, 2015 at 12:53 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote: On 05/26/2015 04:56 PM, Matthew Brett wrote: Hi, This morning I was wondering whether we ought to plan to devote some resources to collaborating with the OpenBLAS team. It is relatively easy to add

[Numpy-discussion] Strategy for OpenBLAS

Hi, This morning I was wondering whether we ought to plan to devote some resources to collaborating with the OpenBLAS team. Summary: we should explore ways of setting up numpy as a test engine for OpenBLAS development. Detail: I am getting the impression that OpenBLAS is looking like the most

Re: [Numpy-discussion] binary wheels for numpy?

On Sun, May 17, 2015 at 9:14 PM, Chris Barker chris.bar...@noaa.gov wrote: On Sun, May 17, 2015 at 3:06 AM, Ralf Gommers ralf.gomm...@gmail.com wrote: Binaries which crash for ~1% of users (which ATLAS-SSE2 would result in) are still not acceptable I think. what instruction set would an

Re: [Numpy-discussion] binary wheels for numpy?

On Sun, May 17, 2015 at 9:27 PM, Nathaniel Smith n...@pobox.com wrote: On Sun, May 17, 2015 at 9:09 PM, Chris Barker chris.bar...@noaa.gov wrote: On Sun, May 17, 2015 at 12:11 PM, Robert Kern robert.k...@gmail.com wrote: I don't think permission from Intel is the blocking issue for putting

Re: [Numpy-discussion] binary wheels for numpy?

On Sun, May 17, 2015 at 8:22 AM, Sturla Molden sturla.mol...@gmail.com wrote: Matthew Brett matthew.br...@gmail.com wrote: Yes, unfortunately we can't put MKL binaries on pypi because of the MKL license - see I believe we can, because we asked Intel for permission. From what I heard

Re: [Numpy-discussion] binary wheels for numpy?

Hi, On Fri, May 15, 2015 at 1:07 PM, Chris Barker chris.bar...@noaa.gov wrote: Hi folks., I did a little intro to scipy session as part of a larger Python class the other day, and was dismayed to find that pip install numpy still dosn't work on Windows. Thanks mostly to Matthew Brett's

Re: [Numpy-discussion] Consider improving numpy.outer's behavior with zero-dimensional vectors

Hi, On Thu, Apr 16, 2015 at 3:19 PM, Neil Girdhar mistersh...@gmail.com wrote: Actually, looking at the docs, numpy.outer is *only* defined for 1-d vectors. Should anyone who used it with multi-dimensional arrays have an expectation that it will keep working in the same way? On Thu, Apr 16,

Re: [Numpy-discussion] OS X wheels: speed versus multiprocessing

Hi, On Mon, Apr 6, 2015 at 5:13 PM, Sturla Molden sturla.mol...@gmail.com wrote: On 07/04/15 01:49, Nathaniel Smith wrote: Any opinions, objections? Accelerate does not break multiprocessing, quite the opposite. The bug is in multiprocessing and has been fixed in Python 3.4. My vote would

Re: [Numpy-discussion] Advanced indexing: fancy vs. orthogonal

Hi, On Thu, Apr 2, 2015 at 8:20 PM, Jaime Fernández del Río jaime.f...@gmail.com wrote: On Thu, Apr 2, 2015 at 7:30 PM, Matthew Brett matthew.br...@gmail.com wrote: Hi, On Thu, Apr 2, 2015 at 6:09 PM, josef.p...@gmail.com wrote: On Thu, Apr 2, 2015 at 8:02 PM, Eric Firing efir

Re: [Numpy-discussion] Advanced indexing: fancy vs. orthogonal

Hi, On Thu, Apr 2, 2015 at 6:09 PM, josef.p...@gmail.com wrote: On Thu, Apr 2, 2015 at 8:02 PM, Eric Firing efir...@hawaii.edu wrote: On 2015/04/02 1:14 PM, Hanno Klemm wrote: Well, I have written quite a bit of code that relies on fancy indexing, and I think the question, if the behaviour

Re: [Numpy-discussion] Silent Broadcasting considered harmful

Hi, On Sun, Feb 8, 2015 at 1:24 PM, Stefan Reiterer dom...@gmx.net wrote: I don't think this is a good comparison, especially since broadcasting is a feature not a necessity ... It's more like turning off/on driving assistance. And as already mentioned: other matrix languages also allow it,

Re: [Numpy-discussion] Silent Broadcasting considered harmful

Hi, On Sun, Feb 8, 2015 at 1:39 PM, Simon Wood sgwoo...@gmail.com wrote: On Sun, Feb 8, 2015 at 4:24 PM, Stefan Reiterer dom...@gmx.net wrote: I don't think this is a good comparison, especially since broadcasting is a feature not a necessity ... It's more like turning off/on driving

Re: [Numpy-discussion] new mingw-w64 based numpy and scipy wheel (still experimental)

Hi, On Tue, Jan 27, 2015 at 1:37 PM, Carl Kleffner cmkleff...@gmail.com wrote: 2015-01-27 22:13 GMT+01:00 Nathaniel Smith n...@pobox.com: On Tue, Jan 27, 2015 at 8:53 PM, Ralf Gommers ralf.gomm...@gmail.com wrote: On Mon, Jan 26, 2015 at 4:30 PM, Carl Kleffner cmkleff...@gmail.com

Re: [Numpy-discussion] new mingw-w64 based numpy and scipy wheel (still experimental)

Hi, On Sun, Jan 25, 2015 at 12:23 PM, Nathaniel Smith n...@pobox.com wrote: On 25 Jan 2015 18:46, Carl Kleffner cmkleff...@gmail.com wrote: 2015-01-25 16:46 GMT+01:00 Nathaniel Smith n...@pobox.com: On Sat, Jan 24, 2015 at 5:29 PM, Carl Kleffner cmkleff...@gmail.com wrote: 2015-01-23

Re: [Numpy-discussion] ANN: Scipy 0.15.0 release

Hi, On Mon, Jan 12, 2015 at 7:13 AM, Ralf Gommers ralf.gomm...@gmail.com wrote: On Mon, Jan 12, 2015 at 4:50 AM, cjw c...@ncf.ca wrote: Paul, Wot, no AMD64? Colin, this is well known from previous scipy and numpy releases. It's due to not having a freely available 64-bit compiler chain

Re: [Numpy-discussion] The future of ndarray.diagonal()

Hi, On Sun, Jan 4, 2015 at 4:22 PM, Konrad Hinsen konrad.hin...@fastmail.net wrote: 2) Changes that yield to different results for unmodified legacy code should never be allowed. I think this is a very reasonable rule. Case in point - I have some fairly old code in https://github.com/matthew

Re: [Numpy-discussion] The future of ndarray.diagonal()

Hi, On Thu, Jan 1, 2015 at 9:35 PM, Alexander Belopolsky ndar...@mac.com wrote: A discussion [1] is currently underway at GitHub which will benefit from a larger forum. In version 1.9, the diagonal() method was changed to return a read-only (non-contiguous) view into the original array

Re: [Numpy-discussion] npymath on Windows

Hi, On Sun, Dec 28, 2014 at 4:17 PM, David Cournapeau courn...@gmail.com wrote: On Sun, Dec 28, 2014 at 1:59 AM, Matthew Brett matthew.br...@gmail.com wrote: Hi, Sorry for this ignorant email, but we got confused trying to use 'libnpymath.a' from the mingw builds of numpy: We were

[Numpy-discussion] npymath on Windows

Hi, Sorry for this ignorant email, but we got confused trying to use 'libnpymath.a' from the mingw builds of numpy: We were trying to link against the mingw numpy 'libnpymath.a' using Visual Studio C, but this give undefined symbols from 'libnpymath.a' like this: npymath.lib(npy_math.o) : error

Re: [Numpy-discussion] [SciPy-Dev] ANN: Scipy 0.15.0 release candidate 1

Hi, On Mon, Dec 15, 2014 at 2:47 PM, Pauli Virtanen p...@iki.fi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear all, Scipy 0.15.0 release candidate 1 is now available. If no surprises turn up, the final release is planned within two weeks. Source tarballs, full release notes

Re: [Numpy-discussion] Add a function to broadcast arrays to a given shape to numpy's stride_tricks?

On Sunday, December 7, 2014, Stephan Hoyer sho...@gmail.com wrote: I recently wrote function to manually broadcast an ndarray to a given shape according to numpy's broadcasting rules (using strides): https://github.com/xray/xray/commit/7aee4a3ed2dfd3b9aff7f3c5c6c68d51df2e3ff3 The same

Re: [Numpy-discussion] Add a function to broadcast arrays to a given shape to numpy's stride_tricks?

Hi, On Monday, December 8, 2014, Pierre Haessig pierre.haes...@crans.org wrote: Hi, Le 07/12/2014 08:10, Stephan Hoyer a écrit : In [5]: %timeit xray.core.utils.as_shape(x, y.shape) 10 loops, best of 3: 17 µs per loop Would this be a welcome addition to numpy's lib.stride_tricks?

[Numpy-discussion] Uint64 casting bug for MSVC builds

Hi, I just noticed this using Christophe Gohlke's MKL builds of numpy: import numpy as np val = 2**63 + 2**62 np.float64(val) 1.3835058055282164e+19 np.float64(val).astype(np.uint64) 9223372036854775808 In general it seems that floats get clipped at 2**63 when casting to uint64. This

Re: [Numpy-discussion] ANN: Scipy 0.15.0 beta 1 release

Hi, On Sun, Nov 23, 2014 at 3:13 PM, Pauli Virtanen p...@iki.fi wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear all, We have finally finished preparing the Scipy 0.15.0 beta 1 release. Please try it and report any issues on the scipy-dev mailing list, and/or on Github. If no

Re: [Numpy-discussion] ANN: NumPy 1.9.1 bugfix release

Hi, On Mon, Nov 3, 2014 at 8:13 AM, Charles R Harris charlesr.har...@gmail.com wrote: Hi Julian, On Sun, Nov 2, 2014 at 6:33 AM, Julian Taylor jtaylor.deb...@googlemail.com wrote: Hello, We am pleased to announce the release of NumPy 1.9.1, a bugfix only release for the 1.9.x series.

Re: [Numpy-discussion] FFTS for numpy's FFTs (was: Re: Choosing between NumPy and SciPy functions)

On Thu, Oct 30, 2014 at 4:28 AM, Nathaniel Smith n...@pobox.com wrote: On 30 Oct 2014 11:12, Sturla Molden sturla.mol...@gmail.com wrote: Nathaniel Smith n...@pobox.com wrote: [*] Actually, we could, but the binaries would be tainted with a viral license. And binaries linked with MKL

Re: [Numpy-discussion] FFTS for numpy's FFTs (was: Re: Choosing between NumPy and SciPy functions)

On Thu, Oct 30, 2014 at 10:24 AM, Matthew Brett matthew.br...@gmail.com wrote: On Thu, Oct 30, 2014 at 4:28 AM, Nathaniel Smith n...@pobox.com wrote: On 30 Oct 2014 11:12, Sturla Molden sturla.mol...@gmail.com wrote: Nathaniel Smith n...@pobox.com wrote: [*] Actually, we could

Re: [Numpy-discussion] Choosing between NumPy and SciPy functions

Hi, On Mon, Oct 27, 2014 at 8:07 PM, Sturla Molden sturla.mol...@gmail.com wrote: Sturla Molden sturla.mol...@gmail.com wrote: If we really need a kick-ass fast FFT we need to go to libraries like FFTW, Intel MKL or Apple's Accelerate Framework, I should perhaps also mention FFTS here,

Re: [Numpy-discussion] npy_log2 undefined on Linux

On Fri, Oct 24, 2014 at 6:04 PM, Matthew Brett matthew.br...@gmail.com wrote: Hi, We (dipy developers) have a hit a new problem trying to use the ``npy_log`` C function in our code. Specifically, on Linux, but not on Mac or Windows, we are getting errors of form: ImportError: /path

Re: [Numpy-discussion] npy_log2 undefined on Linux

On Sat, Oct 25, 2014 at 2:15 PM, Matthew Brett matthew.br...@gmail.com wrote: On Fri, Oct 24, 2014 at 6:04 PM, Matthew Brett matthew.br...@gmail.com wrote: Hi, We (dipy developers) have a hit a new problem trying to use the ``npy_log`` C function in our code. Specifically, on Linux

[Numpy-discussion] npy_log2 undefined on Linux

something like: eg_log.pyx import numpy as np cimport numpy as cnp cdef extern from numpy/npy_math.h nogil: double npy_log(double x) def use_log(double val): return npy_log(val) /eg_log.pyx See : https://github.com/matthew-brett/mincy/tree/npy_log_example for a self-contained example

Re: [Numpy-discussion] np.gradient

Hi, On Sat, Oct 18, 2014 at 6:17 PM, Nathaniel Smith n...@pobox.com wrote: Okay! I think I now actually understand what was going on with np.gradient! The discussion has been pretty confused, and I'm worried that what's in master right now is not the right solution, which is a problem because

Re: [Numpy-discussion] Changed behavior of np.gradient

Hi, On Thu, Oct 16, 2014 at 6:38 PM, Benjamin Root ben.r...@ou.edu wrote: That isn't what I meant. Higher order doesn't necessarily mean more accurate. The results simply have different properties. The user needs to choose the differentiation order that they need. One interesting effect in

Re: [Numpy-discussion] Copyright status of NumPy binaries on Windows/OS X

Hi, On Tue, Oct 7, 2014 at 5:13 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote: On 06.10.2014 18:54, Andrew Collette wrote: Hi all, I am working with the HDF Group on a new open-source viewer program for HDF5 files, powered by NumPy, h5py, and wxPython. On Windows, since people

[Numpy-discussion] Fwd: We need help working on code coverage for Cython code

Hi, Sorry for those of you also on the scikit-image mailing list - but here again I'm asking for help to get coverage working for Cython code. Over on another mailing list, we've hit a big problem trying to work out coverage on a large amount of Cython code. As y'all probably know, there's no

Re: [Numpy-discussion] Fwd: We need help working on code coverage for Cython code

Hi, On Tue, Aug 12, 2014 at 12:43 PM, Stéfan van der Walt ste...@sun.ac.za wrote: Hi Matthew On Tue, Aug 12, 2014 at 9:24 PM, Matthew Brett matthew.br...@gmail.com wrote: The Cython developers have done some work on this [1] but it is currently stalled for lack of developer time to work

Re: [Numpy-discussion] Fwd: We need help working on code coverage for Cython code

Hi, On Tue, Aug 12, 2014 at 12:52 PM, Stéfan van der Walt ste...@sun.ac.za wrote: Hi Matthew On Tue, Aug 12, 2014 at 9:49 PM, Matthew Brett matthew.br...@gmail.com wrote: My very vague impression is that Stefan B thinks of the lnotab PR as part of the process of getting the work done, so

Re: [Numpy-discussion] Help - numpy / scipy binary compatibility

Hi, On Sun, Aug 10, 2014 at 11:41 PM, Ralf Gommers ralf.gomm...@gmail.com wrote: On Mon, Aug 11, 2014 at 8:39 AM, Ralf Gommers ralf.gomm...@gmail.com wrote: On Sat, Aug 9, 2014 at 5:04 AM, David Cournapeau courn...@gmail.com wrote: On Sat, Aug 9, 2014 at 10:41 AM, Matthew Brett

Re: [Numpy-discussion] ANN: NumPy 1.8.2 bugfix release

On Sat, Aug 9, 2014 at 5:38 AM, Julian Taylor jtaylor.deb...@googlemail.com wrote: Hello, I am pleased to announce the release of NumPy 1.8.2, a pure bugfix release for the 1.8.x series. https://sourceforge.net/projects/numpy/files/NumPy/1.8.2/ The upgrade is recommended for all users of the

[Numpy-discussion] Help - numpy / scipy binary compatibility

Hi, I would be very happy of some help trying to work out a numpy package binary incompatibility. I'm trying to work out what's happening for this ticket: https://github.com/scipy/scipy/issues/3863 which I summarized at the end: https://github.com/scipy/scipy/issues/3863#issuecomment-51669861

Re: [Numpy-discussion] ANN: NumPy 1.8.2 release candidate

string to object https://github.com/numpy/numpy/pull/4722 thanks, I missed that one, pretty simple, I'll add it to the final release. OSX wheels built and tested and uploaded OK : http://wheels.scikit-image.org https://travis-ci.org/matthew-brett/numpy-atlas-binaries/builds/31747958 Will test

Re: [Numpy-discussion] ANN: NumPy 1.8.2 release candidate

Hi, On Tue, Aug 5, 2014 at 2:27 PM, Matthew Brett matthew.br...@gmail.com wrote: Hi, On Tue, Aug 5, 2014 at 1:57 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote: On 05.08.2014 22:32, Christoph Gohlke wrote: On 8/5/2014 12:45 PM, Julian Taylor wrote: Hello, I am pleased to announce

Re: [Numpy-discussion] last call for numpy 1.8.2 bugfixes

Hi, On Mon, Aug 4, 2014 at 3:05 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote: hi, as numpy 1.9 is going to be a relative hard upgrade as indexing changes expose a couple bugs in third party packages and the large amount of small little incompatibilities I will create a numpy 1.8.2

<    1   2   3   4   5   6   7   8   9   10   >