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

rhead of vectorize). > > Numba already has guvectorize (and it's own version of vectorize as well), > which already does exactly this. > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > https://mail.scipy.org/mailman/li

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

to work on this. Best, -Travis > Chuck > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > https://mail.scipy.org/mailman/listinfo/numpy-discussion > > -- *Travis Oliphant, PhD* *Co-founder and CEO* @teoliphant 512-222-5440 http://www.continuum.io ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Changing FFT cache to a bounded LRU cache

idea how maintainable their patches are, since I haven't seen > them -- this is just from taking to people here at pycon. > > -n > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > https://mail.scipy.org/mailma

[Numpy-discussion] Blog-post that explains what Blaze actually is and where Pluribus project now lives.

, a discussion of additional projects that will hopefully benefit some of you as well, and for which your feedback and assistance is welcome. Best, -Travis -- *Travis Oliphant, PhD* *Co-founder and CEO* @teoliphant 512-222-5440 http://www.continuum.io

Re: [Numpy-discussion] Changes to generalized ufunc core dimension checking

On Wed, Mar 16, 2016 at 3:07 PM, Charles R Harris <charlesr.har...@gmail.com > wrote: > > > On Wed, Mar 16, 2016 at 1:48 PM, Travis Oliphant <tra...@continuum.io> > wrote: > >> >> >> On Wed, Mar 16, 2016 at 12:55 PM, Nathaniel Smith <n...@pobox

[Numpy-discussion] Changes to generalized ufunc core dimension checking

rr2. It no longer works with 1.10.0 but I don't see why that is an improvement. Thoughts? Is there a work-around that doesn't involve creating a 1-d array the same size as arr2 and filling it with scalar2? Thanks. -Travis -- *Travis Oliphant, PhD* *Co-founder and CEO* @teoliphant 512-

Re: [Numpy-discussion] Changes to generalized ufunc core dimension checking

On Wed, Mar 16, 2016 at 12:55 PM, Nathaniel Smith <n...@pobox.com> wrote: > Hi Travis, > > On Mar 16, 2016 9:52 AM, "Travis Oliphant" <tra...@continuum.io> wrote: > > > > Hi everyone, > > > > Can you help me understand why the stricter

Re: [Numpy-discussion] Changes to generalized ufunc core dimension checking

On Thu, Mar 17, 2016 at 4:41 PM, Stephan Hoyer <sho...@gmail.com> wrote: > On Thu, Mar 17, 2016 at 1:04 AM, Travis Oliphant <tra...@continuum.io> > wrote: > >> I think that is a good idea.Let the user decide if scalar >> broadcasting is acceptable for their

Re: [Numpy-discussion] 1.11.0 release notes.

; NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > https://mail.scipy.org/mailman/listinfo/numpy-discussion > > -- *Travis Oliphant* *Co-founder and CEO* @teoliphant 512-222-5440 http://www.continuum.io ___ NumPy-Discu

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

ere is a good infrastructure for > > third parties to build and distribute the binaries -- e.g. > > Anaconda.org. > > I thought that Anaconda.org allows pypi channels as well? > It does: http://pypi.anaconda.org/ -Travis > > Matthew >

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

millions more with other companies and organizations hosting conda packages and indexes. The conda user-base is already very large. A great benefit to the Python ecosystem would be to allow pip users and conda users to share each other's work --- rather than to spend time reproducing work that

Re: [Numpy-discussion] Fast Access to Container of Numpy Arrays on Disk?

emory mapping, but there is a restriction >>> that the numpy arrays in each “column” must be of fixed and same size. >>> > - I looked at PyTables, which may be a solution, but seems to >>> have a very steep learning curve. >>> > - I haven’t tried SQLite3, but I am worried about the time it >>> takes to query the DB for a sequential ID, and then translate byte arrays. >>> > >>> > Any ideas? I greatly appreciate any guidance you can provide. >>> > >>> > Thanks, >>> > Ryan >>> > ___ >>> > NumPy-Discussion mailing list >>> > NumPy-Discussion@scipy.org >>> > https://mail.scipy.org/mailman/listinfo/numpy-discussion >>> >>> >>> >>> -- >>> Nathaniel J. Smith -- http://vorpus.org >>> ___ >>> NumPy-Discussion mailing list >>> NumPy-Discussion@scipy.org >>> https://mail.scipy.org/mailman/listinfo/numpy-discussion >>> >> >> >> >> -- >> Francesc Alted >> >> ___ >> NumPy-Discussion mailing list >> NumPy-Discussion@scipy.org >> https://mail.scipy.org/mailman/listinfo/numpy-discussion >> >> > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > https://mail.scipy.org/mailman/listinfo/numpy-discussion > > -- *Travis Oliphant* *Co-founder and CEO* @teoliphant 512-222-5440 http://www.continuum.io ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion

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

> cover > all of the external > dependencies used by the latest Anaconda release, but earlier releases and > other > conda-installable packages from the default channel are not so strict. > > -Robert > > ___ > N

Re: [Numpy-discussion] isfortran compatibility in numpy 1.10.

reWarning and later > move to 1, which it my preferred solution. See gh-6590 > <https://github.com/numpy/numpy/issues/6590> for the issue. > > Thoughts? > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.or

Re: [Numpy-discussion] Numpy Generalized Ufuncs: Pointer Arithmetic and Segmentation Faults (Debugging?)

ce > implementations of generalised numpy ufuncs? > > I would greatly appreciate some insight into properly developing > generalised ufuncs. > > Best, > Eleanore > > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.o

[Numpy-discussion] Let's move forward with the current governance document.

Hi everyone, After some further thought and spending quite a bit of time re-reading the discussion on a few threads, I now believe that my request to be on the steering council might be creating more trouble than it's worth. Nothing matters to me more than seeing NumPy continue to grow and

Re: [Numpy-discussion] composition of the steering council (was Re: Governance model request)

point. > > -n > > -- > Nathaniel J. Smith -- http://vorpus.org > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > https://mail.scipy.org/mailman/listinfo/numpy-discussion > -- *Travis Oliphant* *Co-founde

Re: [Numpy-discussion] composition of the steering council (was Re: Governance model request)

NumPy-Discussion mailing list > > NumPy-Discussion@scipy.org > > https://mail.scipy.org/mailman/listinfo/numpy-discussion > > > _______ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > https://mail.scipy.org/mailman/listinfo/numpy-discussion > > -- *Tra

Re: [Numpy-discussion] Governance model request

r project; we were just now writing up a blog post to acknowledge > this, but in light of this discussion, I feel that I should say this up > front so folks can gauge any potential bias accordingly. > > > On Tue, Sep 22, 2015 at 3:44 AM, Travis Oliphant <tra...@continuum.io> > wro

Re: [Numpy-discussion] Steering Committee Size

On Wed, Sep 23, 2015 at 3:25 AM, Sebastian Berg wrote: > Hi, > > Trying to figure out at least a bit from the discussions. While I am > happy with the draft, I wonder if someone has some insights about some > questions: > > 1. How large crowds have examples of

Re: [Numpy-discussion] Governance model request

> > > One last time, it was *not* a personal reference to you: the only reason I > mentioned your names was because of the Berkeley clarification regarding > BIDS that I asked of Travis, that's all. If that comment hadn't been made, > I would not have made any mention whatsoever of anyone in

Re: [Numpy-discussion] interpretation of the draft governance document (was Re: Governance model request)

3:08 AM, Travis Oliphant <tra...@continuum.io> > wrote: > > > > > > On Tue, Sep 22, 2015 at 4:33 AM, Nathaniel Smith <n...@pobox.com> wrote: > >> > >> On Tue, Sep 22, 2015 at 1:24 AM, Travis Oliphant <tra...@continuum.io> > >> wrote

Re: [Numpy-discussion] composition of the steering council (was Re: Governance model request)

> > Regarding the seed council, I just tried to pick an objective > criterion and an arbitrary date that seemed generally in keeping with > idea of "should be active in the last 1-to-2-years-ish". Fiddling with > the exact date in particular makes very little difference -- between > pushing it

Re: [Numpy-discussion] interpretation of the draft governance document (was Re: Governance model request)

ial > Council Members are nominated by existing Council members and voted upon by > the existing Council after asking if the potential Member is interested and > willing to serve in that capacity. The Council will be initially formed > from the set of existing Core Develop

Re: [Numpy-discussion] composition of the steering council (was Re: Governance model request)

On Wed, Sep 23, 2015 at 6:19 PM, Charles R Harris <charlesr.har...@gmail.com > wrote: > > > On Wed, Sep 23, 2015 at 3:42 PM, Chris Barker <chris.bar...@noaa.gov> > wrote: > >> On Wed, Sep 23, 2015 at 2:21 PM, Travis Oliphant <tra...@continuum.io> >

Re: [Numpy-discussion] Governance model request

model, mixed with some concern about being "automatically disqualified" from a council that can decide the future of NumPy if things don't move forward. -Travis On Tue, Sep 22, 2015 at 12:57 AM, Stefan van der Walt <stef...@berkeley.edu> wrote: > On 2015-09-20 11:20:28, T

Re: [Numpy-discussion] 1.10.0rc1 coming tomorrow, 22 Sept.

Just a heads up. The lack of reported problems in 1.10.0b1 has been > stunning. > > Chuck > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > https://mail.scipy.org/mailman/listinfo/numpy-discussion > >

Re: [Numpy-discussion] Commit rights for Allan Haldane

__ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > https://mail.scipy.org/mailman/listinfo/numpy-discussion > > -- *Travis Oliphant* *Co-founder and CEO* @teoliphant 512-222-5440 http://www.continuum.io __

Re: [Numpy-discussion] Governance model request

On Tue, Sep 22, 2015 at 1:20 PM, Stefan van der Walt wrote: > > > I guess we've gone off the rails pretty far at this point, so let me at > least take a step back, and make sure that you know that: > > - I have never doubted that your intensions for NumPy are anything but >

Re: [Numpy-discussion] Governance model request

gt; wrote: > > Hi Travis > > > > On 2015-09-22 03:44:12, Travis Oliphant <tra...@continuum.io> 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 time, my energy, my > >>

Re: [Numpy-discussion] Governance model request

On Tue, Sep 22, 2015 at 2:16 AM, Stefan van der Walt <stef...@berkeley.edu> wrote: > Hi Travis > > On 2015-09-21 23:29:12, Travis Oliphant <tra...@continuum.io> wrote: > > 1) nobody believes that the community should be forced to adopt numba > as > > part

Re: [Numpy-discussion] Governance model request

haniel Smith <n...@pobox.com> wrote: > On Mon, Sep 21, 2015 at 9:20 AM, Travis Oliphant <tra...@continuum.io> > wrote: > > > > I wrote my recommendations quickly before heading on a plane.I hope > the spirit of them was caught correctly.I also want

Re: [Numpy-discussion] Governance model request

sts of array computing in Python at heart? The only thing that is different between me today and me 18 years ago is that 1) I have more resources now, 2) I have more knowledge about computer science and software architecture and 3) I have more experience with how NumPy gets used.All I can

Re: [Numpy-discussion] Governance model request

re you really arguing that they shouldn't because there are other projects Continuum is working on that have some overlap with NumPy.I really hope you don't actually believe that. -Travis > Stéfan > ___ > NumPy-Discussion mailing list >

Re: [Numpy-discussion] 1.10.0rc1 coming tomorrow, 22 Sept.

in the next few months on anaconda.org that will make this easier -- but no promises at this point. -Travis On Tue, Sep 22, 2015 at 2:19 AM, Nathaniel Smith <n...@pobox.com> wrote: > On Sep 21, 2015 11:51 PM, "Travis Oliphant" <tra...@continuum.io> wrote: > >

Re: [Numpy-discussion] Governance model request

Continuum simultaneously is bad, on > principle? That's fine, as such, but let's make that position explicit if > that's all it is. > > > > Bryan > > ___ > > NumPy-Discussion mailing list > > NumPy-Discussion@scipy.org >

Re: [Numpy-discussion] Governance model request

On Tue, Sep 22, 2015 at 4:33 AM, Nathaniel Smith <n...@pobox.com> wrote: > On Tue, Sep 22, 2015 at 1:24 AM, Travis Oliphant <tra...@continuum.io> > wrote: > >> I actually do agree with your view of the steering council as being >> usually not really being needed

Re: [Numpy-discussion] Governance model request

maller and that people who have a right to vote on things like the make-up of the steering committee be comprised of people who have been significantly involved in the past 3 years (not just the past one year). -Travis > > Cheers, > > Matthew > > > [1] http://www.bbc.com/ne

Re: [Numpy-discussion] Governance model request

utors. In that case, I would define active as having a time-window of 5 years instead of just 1). Thanks, -Travis On Mon, Sep 21, 2015 at 2:39 AM, Sebastian Berg <sebast...@sipsolutions.net> wrote: > On Mo, 2015-09-21 at 11:32 +0200, Sebastian Berg wrote: > > On So, 201

[Numpy-discussion] Governance model request

After long conversations at BIDS this weekend and after reading the entire governance document, I realized that the steering council is very large and I don't agree with the mechanism by which it is chosen. A one year time frame is pretty short on the context of a two decades old project and I

Re: [Numpy-discussion] The process I intend to follow for any proposed changes to NumPy

ponse Division > NOAA/NOS/OR(206) 526-6959 voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 main reception > > chris.bar...@noaa.gov > > _______ > NumPy-Discussion maili

[Numpy-discussion] The process I intend to follow for any proposed changes to NumPy

Hey all, I just wanted to clarify, that I am very excited about a few ideas I have --- but I don't have time myself to engage in the community process to get these changes into NumPy. However, those are real processes --- I've been coaching a few people in those processes for the past several

[Numpy-discussion] Just to this list --- more details of the approach

oach. There is more to it, but that is the basic idea.Please forgive me if I can't respond to any feedback from the list in a timely way. I will as I can. -Travis -- *Travis Oliphant* *Co-founder and CEO* @teoliphant 512-222-5440 http://www.continuum.io ___ NumPy-Dis

[Numpy-discussion] Looking for a developer who will work with me for at least 6 months to fix NumPy's dtype system.

if I can't find someone I will publish the ideas --- but that also takes time and effort that is in short supply for me right now. If there is someone willing to fund this work, please let me know as well -- that could free up more of my time. Best, -Travis -- *Travis Oliphant* *Co-found

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

specifically what I think is a better approach to array- and table-computing in Python that keeps the stability of NumPy and adds new features using different approaches. -Travis On Tue, Aug 25, 2015 at 12:00 PM, Travis Oliphant tra...@continuum.io wrote: Thanks for the write-up Nathaniel

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

On Tue, Aug 25, 2015 at 3:58 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Tue, Aug 25, 2015 at 1:00 PM, Travis Oliphant tra...@continuum.io wrote: Thanks for the write-up Nathaniel. There is a lot of great detail and interesting ideas here. snip I think that summarizes

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

On Tue, Aug 25, 2015 at 3:58 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Tue, Aug 25, 2015 at 1:00 PM, Travis Oliphant tra...@continuum.io wrote: Thanks for the write-up Nathaniel. There is a lot of great detail and interesting ideas here. snip There are at least 3

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

that function an array with a special dtype and get out both f(x) and f'(x)) - probably others I'm forgetting right now I should also note that there was one substantial objection to this plan, from Travis Oliphant (in discussions later in the conference). I'm not confident I

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

with the development of a dedicated mingw-w64 based compiler toolchain to support OpenBLAS / ATLAS based binaries on windows. Cheers, carlkl 2014-10-08 1:32 GMT+02:00 Travis Oliphant tra...@continuum.io: Hey Andrew, You can use any of the binaries from Anaconda and redistribute them

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

flavors). It should be straightforward to take those binaries and make conda (or wheel) packages out of them. A good mingw64 stack for Windows would be great and benefits many communities. On Wed, Oct 8, 2014 at 4:46 PM, Sturla Molden sturla.mol...@gmail.com wrote: Travis Oliphant tra

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

NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- Travis Oliphant CEO Continuum Analytics, Inc. http://www.continuum.io ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman

Re: [Numpy-discussion] Custom dtypes without C -- or, a standard ndarray-like type

-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- Travis Oliphant CEO Continuum Analytics, Inc. http://www.continuum.io ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http

Re: [Numpy-discussion] Custom dtypes without C -- or, a standard ndarray-like type

On Sun, Sep 21, 2014 at 6:50 PM, Stephan Hoyer sho...@gmail.com wrote: pandas has some hacks to support custom types of data for which numpy can't handle well enough or at all. Examples include datetime and Categorical [1], and others like GeoArray [2] that haven't make it into pandas yet.

Re: [Numpy-discussion] SciPy 2014 BoF NumPy Participation

) ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- Travis Oliphant CEO Continuum Analytics, Inc. http://www.continuum.io ___ NumPy-Discussion mailing

Re: [Numpy-discussion] big-bangs versus incremental improvements (was: Re: SciPy 2014 BoF NumPy Participation)

Believe me, I'm all for incremental changes if it is actually possible and doesn't actually cost more. It's also why I've been silent until now about anything we are doing being a candidate for a NumPy 2.0. I understand the challenges of getting people to change. But, features and solid

Re: [Numpy-discussion] PEP 465 has been accepted / volunteers needed

Congratulations! This is definitely a big step for array-computing with Python. Working with the Python devs to implement a PEP can be a tremendous opportunity to increase your programming awareness and ability --- as well as make some good friends. This is a great way to get involved with both

Re: [Numpy-discussion] It looks like Py 3.5 will include a dedicated infix matrix multiply operator

Congratulations Nathaniel! This is great news! Well done on starting the process and taking things forward. Travis On Mar 14, 2014 7:51 PM, Nathaniel Smith n...@pobox.com wrote: Well, that was fast. Guido says he'll accept the addition of '@' as an infix operator for matrix multiplication,

Re: [Numpy-discussion] Indexing changes in 1.9

code paths. Is their a roadmap for 1.9? Travis On Feb 3, 2014 1:26 PM, Sebastian Berg sebast...@sipsolutions.net wrote: On Sun, 2014-02-02 at 13:11 -0600, Travis Oliphant wrote: This sounds like a great and welcome work and improvements. Does it make sense to also do something about

Re: [Numpy-discussion] Indexing changes in 1.9

This sounds like a great and welcome work and improvements. Does it make sense to also do something about the behavior of advanced indexing when slices are interleaved between lists and integers. I know that jay borque has some preliminary work to fix this. There are a some straightforward

Re: [Numpy-discussion] ufunc overrides

___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- Travis Oliphant Continuum Analytics, Inc. http://www.continuum.io ___ NumPy-Discussion

Re: [Numpy-discussion] timezones and datetime64

___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion -- --- Travis Oliphant Continuum Analytics, Inc. http://www.continuum.io ___ NumPy

Re: [Numpy-discussion] A new webpage promoting Compiler technology for CPython

answered to. On Feb 16, 2013, at 9:59 AM, Ronan Lamy wrote: Le 15/02/2013 07:11, Travis Oliphant a écrit : This page is specifically for Compiler projects that either integrate with or work directly with the CPython run-time which is why PyPy is not presently listed. The PyPy project

Re: [Numpy-discussion] A new webpage promoting Compiler technology for CPython

...@googlegroups.com until a more specific list is created. On Sat, Feb 16, 2013 at 6:14 PM, Fernando Perez fperez@gmail.comwrote: On Sat, Feb 16, 2013 at 3:56 PM, Travis Oliphant tra...@continuum.io wrote: We should take this discussion off list. Just as a bystander interested in this: why? It seems

[Numpy-discussion] A new webpage promoting Compiler technology for CPython

spreading, and so we welcome any and all contributions. Thank you, Travis Oliphant ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

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

Fantastic job everyone! Hats of to you Ondrej! -Travis On Dec 28, 2012, at 6:02 PM, Ondřej Čertík wrote: Hi, I'm pleased to announce the availability of the first release candidate of NumPy 1.7.0rc1. Sources and binary installers can be found at

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

On Dec 20, 2012, at 7:39 PM, Nathaniel Smith wrote: On Thu, Dec 20, 2012 at 11:46 PM, Matthew Brett matthew.br...@gmail.com wrote: Travis - I think you are suggesting that there should be no one person in charge of numpy, and I think this is very unlikely to work well. Perhaps there are

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

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 on this list that Continuum Analytics has received DARPA funding (to the tune of at least $3

[Numpy-discussion] www.numpy.org home page

For people interested in the www.numpy.org home page: Jon Turner has officially transferred the www.numpy.org domain to NumFOCUS. Thank you, Jon for this donation and for being a care-taker of the domain-name. We have setup the domain registration to point to numpy.github.com and I've

Re: [Numpy-discussion] Proposal to drop python 2.4 support in numpy 1.8

A big +1 from me --- but I don't have anyone I know using 2.4 anymore -Travis On Dec 13, 2012, at 10:34 AM, Charles R Harris wrote: Time to raise this topic again. Opinions welcome. Chuck ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] Speed bottlenecks on simple tasks - suggested improvement

Raul, This is *fantastic work*. While many optimizations were done 6 years ago as people started to convert their code, that kind of report has trailed off in the last few years. I have not seen this kind of speed-comparison for some time --- but I think it's definitely beneficial.

Re: [Numpy-discussion] Z-ordering (Morton ordering) for numpy

This is pretty cool.Something like this would be interesting to play with. There are some algorithms that are faster with z-order arrays.The code is simple enough and small enough that I could see putting it in NumPy. What do others think? -Travis On Nov 24, 2012, at 1:03 PM,

[Numpy-discussion] NumFOCUS has received 501(c)3 status

Hello all, I'm really happy to report that NumFOCUS has received it's 501(c)3 status from the IRS. You can now make tax-deductible donations to NumFOCUS for the support of NumPy. We will put a NumPy-specific button on the home-page of NumPy soon so you can specifically direct your funds.

[Numpy-discussion] 1.7.0 release

Hey all, Ondrej has been tied up finishing his PhD for the past several weeks. He is defending his work shortly and should be available to continue to help with the 1.7.0 release around the first of December.He and I have been in contact during this process, and I've been helping where I

Re: [Numpy-discussion] ticket 2228: Scientific package seeing ABI change in 1.6.x

On Nov 4, 2012, at 1:31 PM, Ralf Gommers wrote: On Wed, Oct 31, 2012 at 1:05 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Tue, Oct 30, 2012 at 9:26 PM, Travis Oliphant tra...@continuum.io wrote: The NPY_CHAR is not a real type. There are no type-coercion functions

Re: [Numpy-discussion] ticket 2228: Scientific package seeing ABI change in 1.6.x

The NPY_CHAR is not a real type. There are no type-coercion functions attached to it nor ufuncs nor a full dtype object. However, it is used to mimic old Numeric character arrays (especially for copying a string). It should have been deprecated before changing the ABI. I don't think

Re: [Numpy-discussion] Issue tracking

On Oct 23, 2012, at 9:58 AM, David Cournapeau wrote: On Tue, Oct 23, 2012 at 5:05 AM, Thouis (Ray) Jones tho...@gmail.com wrote: On Fri, Oct 19, 2012 at 9:34 PM, Thouis (Ray) Jones tho...@gmail.com wrote: On Fri, Oct 19, 2012 at 4:46 PM, Thouis (Ray) Jones tho...@gmail.com wrote: On Fri,

Re: [Numpy-discussion] Issue tracking

Kudos! Ray. Very impressive and useful work. -Travis On Oct 19, 2012, at 10:20 AM, Thouis (Ray) Jones wrote: I started the import with the oldest 75 and newest 125 Trac issues, and will wait a few hours to do the rest to allow feedback, just in case something is broken that I haven't

[Numpy-discussion] Announcing Anaconda version 1.1

I just wanted to let everyone know about our new release of Anaconda which now has Spyder and Matplotlib working for Mac OS X and Windows. Right now, it's the best way to get the pre-requisites for Numba --- though I recommend getting the latest Numba from github as Numba is still under active

[Numpy-discussion] A change with minor compatibility questions

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 array. Currently their hash function just hashes the

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

On Oct 17, 2012, at 12:48 PM, Dag Sverre Seljebotn wrote: 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

Re: [Numpy-discussion] Behavior of .base

On Oct 1, 2012, at 9:11 AM, Jim Bosch wrote: On 09/30/2012 03:59 PM, Travis Oliphant wrote: Hey all, In a github-discussion with Gael and Nathaniel, we came up with a proposal for .base that we should put before this list.Traditionally, .base has always pointed to None for arrays

[Numpy-discussion] Behavior of .base

Hey all, In a github-discussion with Gael and Nathaniel, we came up with a proposal for .base that we should put before this list.Traditionally, .base has always pointed to None for arrays that owned their own memory and to the most immediate array object parent for arrays that did not

Re: [Numpy-discussion] Behavior of .base

We are not talking about changing it back. The change in 1.6 caused problems that need to be addressed. Can you clarify your concerns? The proposal is not a major change to the behavior on master, but it does fix a real issue. -- Travis Oliphant (on a mobile) 512-826-7480 On Sep 30, 2012

Re: [Numpy-discussion] Behavior of .base

to an unexpected mmap object. -- Travis Oliphant (on a mobile) 512-826-7480 On Sep 30, 2012, at 3:50 PM, Han Genuit hangen...@gmail.com wrote: On Sun, Sep 30, 2012 at 10:35 PM, Travis Oliphant tra...@continuum.io wrote: We are not talking about changing it back. The change in 1.6 caused

Re: [Numpy-discussion] Behavior of .base

-- Travis Oliphant (on a mobile) 512-826-7480 On Sep 30, 2012, at 4:00 PM, Han Genuit hangen...@gmail.com wrote: On Sun, Sep 30, 2012 at 10:55 PM, Travis Oliphant tra...@continuum.io wrote: I think you are misunderstanding the proposal. The proposal is to traverse the views as far

Re: [Numpy-discussion] Behavior of .base

It sounds like there are no objections and this has a strong chance to fix the problems.We will put it on the TODO list for 1.7.0 release. -Travis On Sep 30, 2012, at 9:30 PM, Charles R Harris wrote: On Sun, Sep 30, 2012 at 1:59 PM, Travis Oliphant tra...@continuum.io wrote: Hey

Re: [Numpy-discussion] Making numpy sensible: backward compatibility please

Thank you for expressing this voice, Gael.It is an important perspective. The main reason that 1.7 has taken so long to get released is because I'm concerned about these kinds of changes and really want to either remove them or put in adequate warnings prior to moving forward. It's a

Re: [Numpy-discussion] Making numpy sensible: backward compatibility please

On Sep 28, 2012, at 4:53 PM, Henry Gomersall wrote: On Fri, 2012-09-28 at 16:43 -0500, Travis Oliphant wrote: I agree that we should be much more cautious about semantic changes in the 1.X series of NumPy.How we handle situations where 1.6 changed things from 1.5 and wasn't reported

Re: [Numpy-discussion] Making numpy sensible: backward compatibility please

From a practical standpoint, I believe that people implementing large changes to the numpy codebase, or any other core scipy package, should think really hard about their impact. I do realise that the changes are discussed on the mailing lists, but there is a lot of activity to follow

Re: [Numpy-discussion] np.array execution path

Check to see if this expression is true no is o In the first case no and o are the same object Travis -- Travis Oliphant (on a mobile) 512-826-7480 On Sep 22, 2012, at 1:01 PM, Sebastian Berg sebast...@sipsolutions.net wrote: Hi, I have a bit of trouble figuring this out. I would have

Re: [Numpy-discussion] specifying numpy as dependency in your project, install_requires

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 work a lot of the time. I actually filed a bug against patsy for

Re: [Numpy-discussion] tests for casting table? (was: Numpy 1.7b1 API change cause big trouble)

Here are a couple of scripts that might help (I used them to compare casting tables between various versions of NumPy): Casting Table Creation Script import numpy as np operators = np.set_numeric_ops().values() types = '?bhilqpBHILQPfdgFDGO' to_check = ['add',

Re: [Numpy-discussion] Regression: in-place operations (possibly intentional)

On Sep 18, 2012, at 1:47 PM, Charles R Harris wrote: On Tue, Sep 18, 2012 at 11:39 AM, Benjamin Root ben.r...@ou.edu wrote: On Mon, Sep 17, 2012 at 9:33 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 17, 2012 at 3:40 PM, Travis Oliphant tra...@continuum.io

Re: [Numpy-discussion] Regression: in-place operations (possibly intentional)

: On Tue, Sep 18, 2012 at 2:47 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Tue, Sep 18, 2012 at 11:39 AM, Benjamin Root ben.r...@ou.edu wrote: On Mon, Sep 17, 2012 at 9:33 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 17, 2012 at 3:40 PM, Travis

Re: [Numpy-discussion] Regression: in-place operations (possibly intentional)

That is sort of the point of all this. We are using 16 bit integers because we wanted to be as efficient as possible and didn't need anything larger. Note, that is what we changed the code to, I am just wondering if we are being too cautious. The casting kwarg looks to be what I

Re: [Numpy-discussion] Regression: in-place operations (possibly intentional)

On Sep 17, 2012, at 8:42 AM, Benjamin Root wrote: 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

Re: [Numpy-discussion] Change in behavior of np.concatenate for upcoming release

I was working on the same fix and so I saw your code was similar and merged it. It needs to be back-ported to 1.7.0 Thanks, -Travis On Sep 15, 2012, at 11:06 AM, Han Genuit wrote: Okay, sent in a pull request: https://github.com/numpy/numpy/pull/443.

Re: [Numpy-discussion] Change in behavior of np.concatenate for upcoming release

It's very nice to get your help.I hope I haven't inappropriately set expectations :-) -Travis On Sep 15, 2012, at 3:14 PM, Han Genuit wrote: Yeah, that merge was fast. :-) Regards, Han ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] Obscure code in concatenate code path?

On Sep 13, 2012, at 8:40 AM, Nathaniel Smith wrote: On Thu, Sep 13, 2012 at 11:12 AM, Matthew Brett matthew.br...@gmail.com wrote: Hi, While writing some tests for np.concatenate, I ran foul of this code: if (axis = NPY_MAXDIMS) { ret =

Re: [Numpy-discussion] Obscure code in concatenate code path?

This is expected behavior. It's how the concatenate Python function manages to handle axis=None to flatten the arrays before concatenation. This has been in NumPy since 1.0 and should not be changed without deprecation warnings which I am -0 on. Now, it is true that the C-API

  1   2   3   4   5   6   7   >