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

Maybe this is just me, I tried to build the tarball I got from sourceforge in a fresh virtualenv on my mac and received the following error: clang: numpy/core/src/multiarray/buffer.c clang: src/multiarray/cblasfuncs.c clang: error: no such file or directory: 'src/multiarray/cblasfuncs.c' clang: er

[Numpy-discussion] Changes to np.digitize since NumPy 1.9?

Hi all, I've been testing the package I spend most of my time on, yt, under numpy 1.10b1 since the announcement went out. I think I've narrowed down and fixed all of the test failures that cropped up except for one last issue. It seems that the behavior of np.digitize with respect to ndarray subc

Re: [Numpy-discussion] Changes to np.digitize since NumPy 1.9?

On Thu, Aug 13, 2015 at 9:44 AM, Charles R Harris wrote: > > > On Thu, Aug 13, 2015 at 12:09 AM, Jaime Fernández del Río < > jaime.f...@gmail.com> wrote: > >> On Wed, Aug 12, 2015 at 2:03 PM, Nathan Goldbaum >> wrote: >> >>> Hi all, >>>

Re: [Numpy-discussion] Notes from the numpy dev meeting at scipy 2015

On Tue, Aug 25, 2015 at 5:03 AM, Nathaniel Smith wrote: > Hi all, > > These are the notes from the NumPy dev meeting held July 7, 2015, at > the SciPy conference in Austin, presented here so the list can keep up > with what happens, and so you can give feedback. Please do give > feedback, none of

Re: [Numpy-discussion] "Become an Open Source Contributor" workshop

If you are going to do work at a terminal, I'd suggest using a library like doitlive (http://doitlive.readthedocs.org/en/latest/) so you can't make mistakes while still making it look like you are actually typing everything at a terminal. You will also be able to share your exact terminal sessions

Re: [Numpy-discussion] Cython-based OpenMP-accelerated quartic polynomial solver

subprocess. If that succeeds, then great, we can add -fopenmp as a compilation flag. If not, don't do that. This was implemented when Apple switched from GCC 4.2 to LLVM/Clang in OS X 10.7. We've had exactly one bug report about this, and it wasn'

Re: [Numpy-discussion] Behavior of numpy.copy with sub-classes

On Mon, Oct 19, 2015 at 7:23 PM, Jonathan Helmus wrote: > In GitHub issue #3474, a number of us have started a conversation on how > NumPy's copy function should behave when passed an instance which is a > sub-class of the array class. Specifically, the issue began by noting that > when a Masked

Re: [Numpy-discussion] Proposal: stop supporting 'setup.py install'; start requiring 'pip install .' instead

Interestingly, conda actually does "setup.py install" in the recipe for numpy: https://github.com/conda/conda-recipes/blob/master/numpy-openblas/build.sh I'm not sure if this is the one they use to build the anaconda package, I think they have internal versions of most of the recipes on conda-reci

Re: [Numpy-discussion] Proposal: stop supporting 'setup.py install'; start requiring 'pip install .' instead

Would this happen at the level of numpy's setup.py script or would it be implemented in numpy.distutils? I'm asking as the developer of a package that uses numpy.distutils to manage C extensions. On Tue, Oct 27, 2015 at 10:28 AM, wrote: > > > On Tue, Oct 27, 2015 at 10:59 AM, Nathaniel Smith wr

Re: [Numpy-discussion] New behavior of allclose

I actually brought this up before 1.10 came out: https://github.com/numpy/numpy/issues/6196 The behavior change brought out a bug in our use of allclose, so while it was annoying in the sense that our test suite started failing in a new way, it was good in that our tests are now more correct. On

Re: [Numpy-discussion] New behavior of allclose

Oh oops, this is about np.allcose, not np.assert_allclose. Sorry for the noise... On Wed, Nov 4, 2015 at 1:36 PM, Nathan Goldbaum wrote: > I actually brought this up before 1.10 came out: > https://github.com/numpy/numpy/issues/6196 > > The behavior change brought out a bug i

Re: [Numpy-discussion] New behavior of allclose

Yup, https://github.com/numpy/numpy/issues/6196 On Wed, Nov 4, 2015 at 1:45 PM, Charles R Harris wrote: > > > On Wed, Nov 4, 2015 at 12:42 PM, Nathan Goldbaum > wrote: > >> Oh oops, this is about np.allcose, not np.assert_allclose. Sorry for the >> noise... >>

Re: [Numpy-discussion] Should I use pip install numpy in linux?

Doesn't building on CentOS 5 also mean using a quite old version of gcc? I've never tested this, but I've seen claims on the anaconda mailing list of ~25% slowdowns compared to building from source or using system packages, which was attributed to building using an older gcc that doesn't optimize

Re: [Numpy-discussion] NumPy 1.11.0b3 released.

https://github.com/numpy/numpy/blob/master/doc/release/1.11.0-notes.rst On Fri, Feb 12, 2016 at 3:17 PM, Andreas Mueller wrote: > Hi. > Where can I find the changelog? > It would be good for us to know which changes are done one purpos without > hunting through the issue tracker. > > Thanks, > A

Re: [Numpy-discussion] Is this a known error in Ipython with numpy?

On Wed, Apr 27, 2016 at 8:49 PM, Alexander Griffing wrote: > On Wed, Apr 27, 2016 at 7:48 PM, Elliot Hallmark > wrote: > > Hello, > > > > I haven't worked hard yet to create a minimal runnable (reproduce-able) > > example but I wanted to check if this sounds familiar to anyone. > > > > I have a

Re: [Numpy-discussion] Custom Dtype/Units discussion

Hi Ryan, As a maintainer of a unit-aware ndarray subclass, I'm also interested in sitting in. Maybe this can be an informal BOF session? Nathan On Sunday, July 10, 2016, Ryan May wrote: > Hi Nathaniel, > > Thursday works for me; anyone else interested is welcome to join. > > Ryan > > On Sun,

Re: [Numpy-discussion] Custom Dtype/Units discussion

for me too. >> On Jul 13, 2016 7:46 PM, "Charles R Harris" >> wrote: >> >>> Evening would work for me. Dinner? >>> On Jul 13, 2016 2:43 PM, "Ryan May" wrote: >>> >>>> On Mon, Jul 11, 2016 at 12:39 PM, Chris Barker

Re: [Numpy-discussion] Custom Dtype/Units discussion

t. > > On Jul 14, 2016 10:52, "Nathan Goldbaum" wrote: > >> Fine with me as well. Meet in the downstairs lobby after the lightning >> talks? >> >> On Thu, Jul 14, 2016 at 10:49 AM, Ryan May wrote: >> >>> Fine with me. >>> >&g

Re: [Numpy-discussion] Custom Dtype/Units discussion

We are in room 203 On Thursday, July 14, 2016, Nathan Goldbaum wrote: > > > On Thu, Jul 14, 2016 at 11:05 AM, Nathaniel Smith > wrote: > >> Where is "the downstairs lobby"? I can think of 4 places that I might >> describe that way depending on contex

Re: [Numpy-discussion] New Indexing Methods Revival #N (subclasses!)

On Monday, September 5, 2016, Marten van Kerkwijk wrote: > Hi Sebastian, > > It would seem to me that any subclass has to keep up to date with new > features in ndarray, and while I think ndarray has a responsibility > not to break backward compatibility, I do not think it has to protect > agains

Re: [Numpy-discussion] New Indexing Methods Revival #N (subclasses!)

On Tuesday, September 6, 2016, Stephan Hoyer wrote: > On Mon, Sep 5, 2016 at 6:02 PM, Marten van Kerkwijk < > m.h.vankerkw...@gmail.com > > wrote: > >> p.s. Just to be clear: personally, I think we should have neither >> `__numpy_getitem__` nor a mixin; we should just get the quite >> wonderful n

Re: [Numpy-discussion] gmane

Hi Chuck, Since that blog post, Gmane is under new management and will continue to be available: http://home.gmane.org Nathan On Friday, September 9, 2016, Charles R Harris wrote: > Hi All, > > Looks like gmane is going down > . Does

Re: [Numpy-discussion] guvectorize, a helper for writing generalized ufuncs

On Tue, Sep 13, 2016 at 11:47 AM, Stephan Hoyer wrote: > NumPy has the handy np.vectorize for turning Python code that operates on > scalars into a function that vectorizes works like a ufunc, but no helper > function for creating generalized ufuncs (http://docs.scipy.org/doc/ > numpy/reference/c

Re: [Numpy-discussion] assert_allclose equal_nan default value.

Agreed, especially given the prevalence of using this function in downstream test suites: https://github.com/search?utf8=%E2%9C%93&q=numpy+assert_allclose&type=Code&ref=searchresults On Thu, Oct 20, 2016 at 12:16 PM, Charles R Harris < charlesr.har...@gmail.com> wrote: > Hi All, > > Just a heads

Re: [Numpy-discussion] __numpy_ufunc__

I'm interested in this, but was never able to dive in to the lengthy discussions on this. I'm curious if there is a summary of the current state of things somewhere that I could read to catch up. On Sunday, November 6, 2016, Charles R Harris wrote: > > > On Sun, Nov 6, 2016 at 11:44 AM, Charles

Re: [Numpy-discussion] subclassing ndarray and keeping same ufunc behavior

You might also want to consider writing a wrapper object that contains an ndarray as a (possibly private) attribute and then presents different views or interpretations of that array. Subclassing ndarray is a pit of snakes, it's best to avoid it if you can (I say as the author and maintainer of an

Re: [Numpy-discussion] NumPy 1.12.0b1 released

Since the NumPy API is forwards compatible, you should use the oldest version of NumPy you would like to support to build your wheels with. The wheels will then work with any future NumPy versions. On Fri, Nov 18, 2016 at 9:30 AM Peter Cock wrote: > I have a related question to Matti's, > > Do y

Re: [Numpy-discussion] Wheel files for PPC64

Hi Leonardo, Matthew Brett replied to you on Nov 23: https://mail.scipy.org/pipermail/numpy-discussion/2016-November/076290.html It seems you will need to take this up with the upstream python packaging community to come up with an alternate to manylinux1 that will work on ppc architectures. -N

Re: [Numpy-discussion] Does numpy.bincount support numpy.float128 type weights?

I think this is a deficiency in the current implementation of bincount, which always casts the weights to float64. This WIP pull request should probably fix it: https://github.com/numpy/numpy/pull/7464 On Wed, Nov 30, 2016 at 3:54 PM, Wei, Huayi wrote: > Hi, There, > > Here is a sample code usi

Re: [Numpy-discussion] Possible to pickle new state in NDArray subclasses?

I'm able to do this in my ndarrary subclass using __reduce__ and __setstate__: https://bitbucket.org/yt_analysis/yt/src/yt/yt/units/yt_array.py#yt_array.py-1250 Here it's being used to save the unit information into the pickle for a unit-aware ndarray subclass. On Wed, Dec 14, 2016 at 1:45 PM, S

Re: [Numpy-discussion] NumPy 1.12.0 release

I've seen reports on the anaconda mailing list of people seeing similar speed ups when they compile e.g. Numpy with a recent gcc. Anaconda has the same issue as manylinux in that they need to use versions of GCC available on CentOS 5. Given the upcoming official EOL for CentOS5, it might make sens

Re: [Numpy-discussion] Proposal to support __format__

On Wed, Feb 15, 2017 at 4:05 PM, Ilhan Polat wrote: > On the last item, do we really have to follow that strange, `d`,`g` and so > on conventions on formatting? With all respect to the humongous historical > baggage, I think that notation is pretty archaic and terminal like. If > being pythonic i

Re: [Numpy-discussion] Arrays and format()

See this issue: https://github.com/numpy/numpy/issues/5543 There was also a very thorough discussion of this recently on this mailing list: http://numpy-discussion.10968.n7.nabble.com/Proposal-to-support-format-td43931.html On Tue, Feb 28, 2017 at 11:32 AM Ryan May wrote: > Hi, > > Can someon

Re: [Numpy-discussion] migration of all scipy.org mailing lists

Are you sure about astropy? They recently moved to google groups. On Wednesday, March 22, 2017, Ralf Gommers wrote: > Hi all, > > The server for the scipy.org mailing list is in very bad shape, so we > (led by Didrik Pinte) are planning to complete the migration of active > mailing lists to the

Re: [Numpy-discussion] migration of all scipy.org mailing lists

The switchover happened on almost the same day, see: https://mail.scipy.org/pipermail/astropy/2017-March/004498.html On Thu, Mar 23, 2017 at 5:09 AM Ralf Gommers wrote: > On Thu, Mar 23, 2017 at 3:11 AM, Nathan Goldbaum > wrote: > > Are you sure about astropy? They recently mov