Re: [Numpy-discussion] Upcoming 1.8 release.

2013-08-17 Thread Pauli Virtanen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 17.08.2013 21:20, Charles R Harris kirjoitti: [clip] > Experimental would be OK if it would help you with Scipy 0.13.0. > But if it does go in and is used in 0.13, won't that effectively > lock it in until the next scipy/numpy release? That seems a bit

Re: [Numpy-discussion] Upcoming 1.8 release.

2013-08-17 Thread Charles R Harris
On Sat, Aug 17, 2013 at 11:43 AM, Pauli Virtanen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > 15.08.2013 19:52, Charles R Harris kirjoitti: > > On Thu, Aug 15, 2013 at 10:48 AM, Blake Griffith > > >> wrote: I would like to have the ufunc overrides in 1.8 if it is > >> possible. >

Re: [Numpy-discussion] Upcoming 1.8 release.

2013-08-17 Thread Pauli Virtanen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 15.08.2013 19:52, Charles R Harris kirjoitti: > On Thu, Aug 15, 2013 at 10:48 AM, Blake Griffith > > wrote: I would like to have the ufunc overrides in 1.8 if it is >> possible. [clip] > What is the status of that? I've been leaving that commit up the

[Numpy-discussion] Test cases for integer behvaiour

2013-08-17 Thread Arink Verma
Hi All, For scalar operations Numpy first try to extract the underlying C value from a Python Integers. It causes bottleneck because it first converts the Python scalar into its matching NumPy scalar (e.g. PyLong -> int32) and then it extracts the C value from the NumPy scalar. Its quicker to jus