Re: [Numpy-discussion] ANN: XDress v0.4

2014-02-26 Thread Eelco Hoogendoorn
Thanks for the heads up, I wasn't aware of this project. While boost.python is a very nice package, its distributability is nothing short of nonexistent, so its great to have a pure python binding generator. One thing which I have often found frustrating is natural ndarray interop between python a

[Numpy-discussion] ANN: XDress v0.4

2014-02-26 Thread Anthony Scopatz
Hello All, I am *extremely *pleased to be able to announce the version 0.4 release of xdress. This version contains much anticipated full support for Clang as a parser! This is almost entirely due to the efforts of Geoffrey Irving. Please thank him the next time you get a chance :) This releas

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Matthew Brett
Hi, On Wed, Feb 26, 2014 at 3:10 PM, Tom Augspurger wrote: > Thanks Chris, > > > Chris Barker - NOAA Federal wrote >> What python are you using? apparently not a Universal 32+64 bit build. The >> one Apple delivers? > > I'm using homebrew python, so the platform difference seems to have come > fr

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Tom Augspurger
Thanks Chris, Chris Barker - NOAA Federal wrote > What python are you using? apparently not a Universal 32+64 bit build. The > one Apple delivers? I'm using homebrew python, so the platform difference seems to have come from there. I agree about renaming the file as not being a real solution. I'

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Matthew Brett
Hi, On Wed, Feb 26, 2014 at 2:33 PM, Chris Barker wrote: > On Wed, Feb 26, 2014 at 11:34 AM, Matthew Brett > wrote: > >> >> > - convention is the other option: >> > - use binary wheel for in-house deplyment to similar systems >> > - use binary wheels for a well-defined python build: >>

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Chris Barker
On Wed, Feb 26, 2014 at 11:34 AM, Matthew Brett wrote: > > - convention is the other option: > > - use binary wheel for in-house deplyment to similar systems > > - use binary wheels for a well-defined python build: > >- for PyPi, that's the python.org builds for Windows and OS-

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Matthew Brett
Hi, On Wed, Feb 26, 2014 at 11:02 AM, Chris Barker wrote: > On Wed, Feb 26, 2014 at 8:27 AM, Tom Augspurger > wrote: >> >> Thanks for posting those wheels Matthew. >> >> I'm on a Mac (10.9.2) and I had trouble installing numpy from your wheel >> in >> a fresh virtualenv with the latests pip, set

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Frédéric Bastien
Hi, Arnaud finished that in a different way then we had discussed in the PR. https://github.com/numpy/numpy/pull/4081 Fred On Wed, Feb 26, 2014 at 10:07 AM, Frédéric Bastien wrote: > Hi, > > I have a PR that fix way too much printing to stdout when finding the > blas linking information: > > h

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Chris Barker
On Wed, Feb 26, 2014 at 8:27 AM, Tom Augspurger wrote: > Thanks for posting those wheels Matthew. > > I'm on a Mac (10.9.2) and I had trouble installing numpy from your wheel in > a fresh virtualenv with the latests pip, setuptools, and wheel. > > ``` > $pip install > ~/Downloads/numpy-1.8.0.dev_a

Re: [Numpy-discussion] Help Understanding Indexing Behavior

2014-02-26 Thread Chris Barker
On Wed, Feb 26, 2014 at 5:32 AM, Slavin, Jonathan wrote: > This behavior is a property of python slicing. It takes some getting used > to, but has its advantages. > quite a few, actually! They key with slicing is to think of the index as pointing to the space between the elements: 0 1 2 3

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Tom Augspurger
Thanks for posting those wheels Matthew. I'm on a Mac (10.9.2) and I had trouble installing numpy from your wheel in a fresh virtualenv with the latests pip, setuptools, and wheel. ``` $pip install ~/Downloads/numpy-1.8.0.dev_a89a36e-cp27-none-macosx_10_9_intel.whl numpy-1.8.0.dev_a89a36e-cp27-n

Re: [Numpy-discussion] Help Understanding Indexing Behavior

2014-02-26 Thread Sturla Molden
JB wrote: > > x = np.array([1,2,3,4,5,6,7,8,9,10]) > > If I want the first 5 elements, what do I do? x[:5] ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] 1.8.1 release

2014-02-26 Thread Frédéric Bastien
Hi, I have a PR that fix way too much printing to stdout when finding the blas linking information: https://github.com/numpy/numpy/pull/4081 This was created by change in NumPy. I was requested as a comment to put the removed information in the dict that we return to the user. I won't have the

Re: [Numpy-discussion] Help Understanding Indexing Behavior

2014-02-26 Thread Slavin, Jonathan
JB, This behavior is a property of python slicing. It takes some getting used to, but has its advantages. In general in a slice [i:j] the indices go from i to j-1. In the case that i is 0 it's easy to think of it as j giving the number of elements (by the way you can also do a[:j] -- i.e. leavi

Re: [Numpy-discussion] Custom floating point representation to IEEE 754 double

2014-02-26 Thread Oscar Benjamin
On 26 February 2014 00:35, Daniele Nicolodi wrote: > > "simpler" in my original email has to be read as involving less > operations and thus more efficient, not simpler to understand, indeed it > is already a simple implementation of the definition. What I would like > to know is if there are some

Re: [Numpy-discussion] Custom floating point representation to IEEE 754 double

2014-02-26 Thread Gregor Thalhammer
Am 25.02.2014 um 12:08 schrieb Daniele Nicolodi : > Hello, > > I'm dealing with an instrument that transfers numerical values through > an RS232 port in a custom (?) floating point representation (56 bits, 4 > bits exponent and 52 bits significand). > > Of course I need to convert this format t