Re: [Numpy-discussion] Which Python to use for Mac binaries

2013-01-09 Thread Ralf Gommers
On Thu, Jan 10, 2013 at 3:55 AM, Ondřej Čertík wrote: > On Tue, Jan 8, 2013 at 8:45 AM, Chris Barker - NOAA Federal > wrote: > > On Mon, Jan 7, 2013 at 10:23 PM, Ondřej Čertík > wrote: > >>> > http://www.commandlinefu.com/commands/view/2031/install-an-mpkg-from-the-command-line-on-osx > >> > >>

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

2013-01-09 Thread Mike Anderson
On 9 January 2013 23:09, Alan G Isaac wrote: > On 1/9/2013 9:58 AM, Nathaniel Smith wrote: > > I don't think most happy current numpy users are wishing they > > could switch to writing Lisp on the JVM or vice-versa, so I don't > > think it's surprising that no-one's jumped up to do this work. > >

Re: [Numpy-discussion] Which Python to use for Mac binaries

2013-01-09 Thread Ondřej Čertík
On Tue, Jan 8, 2013 at 8:45 AM, Chris Barker - NOAA Federal wrote: > On Mon, Jan 7, 2013 at 10:23 PM, Ondřej Čertík > wrote: >>> http://www.commandlinefu.com/commands/view/2031/install-an-mpkg-from-the-command-line-on-osx >> >> This requires root access. Without sudo, I get: >> >> $ installer -p

Re: [Numpy-discussion] Remove support for numeric and numarray in 1.8

2013-01-09 Thread Charles R Harris
On Wed, Jan 9, 2013 at 4:21 PM, Christopher Hanley wrote: > After poking around our code base and talking to a few folks I predict > that we at STScI can remove our dependence on the numpy-numarray > compatibility layer by the end of this calendar year. I'm unsure of what > the timeline for numpy

Re: [Numpy-discussion] Remove support for numeric and numarray in 1.8

2013-01-09 Thread Nathaniel Smith
On Wed, Jan 9, 2013 at 11:21 PM, Christopher Hanley wrote: > After poking around our code base and talking to a few folks I predict that > we at STScI can remove our dependence on the numpy-numarray compatibility > layer by the end of this calendar year. I'm unsure of what the timeline for > nump

Re: [Numpy-discussion] Remove support for numeric and numarray in 1.8

2013-01-09 Thread Christopher Hanley
After poking around our code base and talking to a few folks I predict that we at STScI can remove our dependence on the numpy-numarray compatibility layer by the end of this calendar year. I'm unsure of what the timeline for numpy 1.8 is so I don't know if this schedule supports removal of the co

[Numpy-discussion] [SCIPY2013] Feedback on mini-symposia themes

2013-01-09 Thread Jonathan Rocher
Dear community members, We are working hard to organize the SciPy2013 conference (Scientific Computing with Python) , this June 24th-29th in Austin, TX. We would like to probe the community about the themes you would be interested in contributing to or parti

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

2013-01-09 Thread Chris Barker - NOAA Federal
On Wed, Jan 9, 2013 at 2:57 AM, Mike Anderson > I'm hoping the API will be independent of storage format - i.e. the > underlying implementations can store the data any way they like. So the API > will be written in terms of abstractions, and the user will have the choice > of whatever concrete imp

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

2013-01-09 Thread Dag Sverre Seljebotn
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

2013-01-09 Thread Dag Sverre Seljebotn
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] Do we want scalar casting to behave as it does at the moment?

2013-01-09 Thread Andrew Collette
Hi Nathaniel, > Sure. But the only reason this is in 1.6 is that the person who made > the change never mentioned it to anyone else, so it wasn't noticed > until after 1.6 came out. If it had gone through proper review/mailing > list discussion (like we're doing now) then it's very unlikely it > w

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

2013-01-09 Thread Chris Barker - NOAA Federal
On Wed, Jan 9, 2013 at 2:35 AM, Mike Anderson >> First -- is this a "matrix" library, or a general use nd-array >> library? That will drive your design a great deal. > This is very useful context - thanks! I've had opinions in favour of both an > nd-array style library and a matrix library. I gue

[Numpy-discussion] numpydoc for python 3?

2013-01-09 Thread Jaakko Luttinen
Hi! I'm trying to use numpydoc (Sphinx extension) for my project written in Python 3.2. However, installing numpydoc gives errors shown at http://pastebin.com/MPED6v9G and although it says "Successfully installed numpydoc", trying to import numpydoc raises errors.. Could this be fixed or am I doi

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

2013-01-09 Thread Chris Barker - NOAA Federal
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, and you apply a scale and offset to get >> a reading in volts. >

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

2013-01-09 Thread Frédéric Bastien
Hi, Congratulation for the release and a big thanks for the hard work. I tested it with our software and all work fine. thanks! Frédéric On Sun, Dec 30, 2012 at 7:17 PM, Sandro Tosi wrote: > Hi Ondrej & al, > > On Sat, Dec 29, 2012 at 1:02 AM, Ondřej Čertík > wrote: >> I'm pleased to announ

Re: [Numpy-discussion] Linear least squares

2013-01-09 Thread Charles R Harris
On Wed, Jan 9, 2013 at 1:29 AM, Till Stensitz wrote: > Nathaniel Smith pobox.com> writes: > > > > > > An obvious thing is that it always computes residuals, which could be > > costly; if your pinv code isn't doing that then it's not really > > comparable. (Though might still be well-suited for y

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

2013-01-09 Thread Benjamin Root
On Wed, Jan 9, 2013 at 9:58 AM, Nathaniel Smith wrote: > On Wed, Jan 9, 2013 at 2:53 PM, Alan G Isaac wrote: > > I'm just a Python+NumPy user and not a CS type. > > May I ask a naive question on this thread? > > > > Given the work that has (as I understand it) gone into > > making NumPy usable a

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

2013-01-09 Thread Alan G Isaac
On 1/9/2013 9:58 AM, Nathaniel Smith wrote: > I don't think most happy current numpy users are wishing they > could switch to writing Lisp on the JVM or vice-versa, so I don't > think it's surprising that no-one's jumped up to do this work. Sure. I'm trying to look at this more from the Clojure

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

2013-01-09 Thread Nathaniel Smith
On Tue, Jan 8, 2013 at 9:14 PM, Andrew Collette wrote: > Hi Nathaniel, > > (Responding to both your emails) > >> The problem is that rule for arrays - and for every other party of >> numpy in general - are that we *don't* pick types based on values. >> Numpy always uses input types to determine ou

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

2013-01-09 Thread Nathaniel Smith
On Wed, Jan 9, 2013 at 2:53 PM, Alan G Isaac wrote: > I'm just a Python+NumPy user and not a CS type. > May I ask a naive question on this thread? > > Given the work that has (as I understand it) gone into > making NumPy usable as a C library, why is the discussion not > going in a direction like

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

2013-01-09 Thread Alan G Isaac
I'm just a Python+NumPy user and not a CS type. May I ask a naive question on this thread? Given the work that has (as I understand it) gone into making NumPy usable as a C library, why is the discussion not going in a direction like the following: What changes to the NumPy code base would be requ

[Numpy-discussion] natural alignment

2013-01-09 Thread Henry Gomersall
Further to my previous emails about getting SIMD aligned arrays, I've noticed that numpy arrays aren't always naturally aligned either. For example, numpy.float96 arrays are not always aligned on 12-byte boundaries under 32-bit linux/gcc. Indeed, .alignment on the array always seems to return 4 (

Re: [Numpy-discussion] Bug with ufuncs made with frompyfunc

2013-01-09 Thread Nathaniel Smith
On Wed, Jan 9, 2013 at 7:23 AM, OKB (not okblacke) wrote: > A bug causing errors with using methods of ufuncs created with > frompyfunc was mentioned on the list over a year ago: > http://mail.scipy.org/pipermail/numpy-discussion/2011- > September/058501.html > > Is there any word

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

2013-01-09 Thread Daπid
On Jan 9, 2013 11:35 AM, "Mike Anderson" wrote: > But I'm curious: what is the main use case for the alternative data types in NumPy? Is it for columns of data of heterogeneous types? or something else? In my case, I have used 32 bit (or lower) arrays due to memory limitations and some significant

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

2013-01-09 Thread Dag Sverre Seljebotn
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 there has been some discussion about > cr

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

2013-01-09 Thread Mike Anderson
On 4 January 2013 16:13, Dag Sverre Seljebotn wrote: > On 01/04/2013 09:00 AM, Dag Sverre Seljebotn wrote: > > On 01/04/2013 07:29 AM, Mike Anderson wrote: > > > Oh: Depending on your amibitions, it's worth thinking hard about i) > storage format, and ii) lazy evaluation. > > Storage format: The

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

2013-01-09 Thread Mike Anderson
On 4 January 2013 16:00, 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 > > fledgeling matrix libra

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

2013-01-09 Thread Mike Anderson
On 8 January 2013 02:08, Chris Barker - NOAA Federal wrote: > On Thu, Jan 3, 2013 at 10:29 PM, Mike Anderson > wrote: > > 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 libra

Re: [Numpy-discussion] Linear least squares

2013-01-09 Thread Till Stensitz
Nathaniel Smith pobox.com> writes: > > An obvious thing is that it always computes residuals, which could be > costly; if your pinv code isn't doing that then it's not really > comparable. (Though might still be well-suited for your actual > problem.) > > Depending on how well-conditioned your