Re: [Numpy-discussion] replacing the mechanism for dispatching ufuncs

What is the status of this proposal? On Wed, Jun 22, 2011 at 6:56 PM, Mark Wiebe wrote: > On Wed, Jun 22, 2011 at 4:57 PM, Darren Dale wrote: >> >> On Wed, Jun 22, 2011 at 1:31 PM, Mark Wiebe wrote: >> > On Wed, Jun 22, 2011 at 7:34 AM, Lluís wrote: >&g

Re: [Numpy-discussion] X11 system info

On Wed, Jul 20, 2011 at 4:58 AM, Pauli Virtanen wrote: > Tue, 19 Jul 2011 21:55:28 +0200, Ralf Gommers wrote: >> On Sun, Jul 17, 2011 at 11:48 PM, Darren Dale >> wrote: >>> In numpy.distutils.system info: >>> >>>    default_x11_lib_dirs

[Numpy-discussion] X11 system info

In numpy.distutils.system info: default_x11_lib_dirs = libpaths(['/usr/X11R6/lib','/usr/X11/lib', '/usr/lib'], platform_bits) default_x11_include_dirs = ['/usr/X11R6/include','/usr/X11/include', '/usr/include'] These def

Re: [Numpy-discussion] replacing the mechanism for dispatching ufuncs

On Wed, Jun 22, 2011 at 1:31 PM, Mark Wiebe wrote: > On Wed, Jun 22, 2011 at 7:34 AM, Lluís wrote: >> >> Darren Dale writes: >> >> > On Tue, Jun 21, 2011 at 1:57 PM, Mark Wiebe wrote: >> >> On Tue, Jun 21, 2011 at 12:36 PM, Charles R Harris >> &g

Re: [Numpy-discussion] replacing the mechanism for dispatching ufuncs

On Tue, Jun 21, 2011 at 1:57 PM, Mark Wiebe wrote: > On Tue, Jun 21, 2011 at 12:36 PM, Charles R Harris > wrote: >> How does the ufunc get called so it doesn't get caught in an endless loop? [...] > The function being called needs to ensure this, either by extracting a raw > ndarray from instan

Re: [Numpy-discussion] replacing the mechanism for dispatching ufuncs

On Tue, Jun 21, 2011 at 2:28 PM, Charles R Harris wrote: > > > On Tue, Jun 21, 2011 at 11:57 AM, Mark Wiebe wrote: >> >> On Tue, Jun 21, 2011 at 12:36 PM, Charles R Harris >> wrote: >>> >>> >>> On Mon, Jun 20, 2011 at 12:32 PM, Mark Wiebe wrote: NumPy has a mechanism built in to allow

Re: [Numpy-discussion] python3 setup.py install fails with git maint/1.6.x

On Mon, Apr 4, 2011 at 3:31 PM, Ralf Gommers wrote: > On Mon, Apr 4, 2011 at 9:15 PM, Darren Dale wrote: >> I just checkout out the 1.6 branch, attempted to install with python3: > > I hope you mean the 1.6.0b1 tarball, not the current branch head? This > problem is (or shoul

[Numpy-discussion] python3 setup.py install fails with git maint/1.6.x

I just checkout out the 1.6 branch, attempted to install with python3: RefactoringTool: Line 695: You should use a for loop here Running from numpy source directory.Traceback (most recent call last): File "setup.py", line 196, in setup_package() File "setup.py", line 170, in setup_package

Re: [Numpy-discussion] nearing a milestone

On Fri, Apr 1, 2011 at 4:08 PM, Benjamin Root wrote: > Whoosh! > > Ben Root > > P.S. -- In case it is needed to be said, that is 1e6 downloads from > sourceforge only.  NumPy is now on github... The releases are still distributed through sourceforge. Maybe the SciPy2011 Program Committee could p

[Numpy-discussion] nearing a milestone

Numpy is nearing a milestone: http://sourceforge.net/projects/numpy/files/NumPy/stats/timeline?dates=2007-09-25+to+2011-04-01 ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] When was the ddof kwarg added to std()?

On Wed, Mar 16, 2011 at 9:10 AM, Scott Sinclair wrote: > On 16 March 2011 14:52, Darren Dale wrote: >> Does anyone know when the ddof kwarg was added to std()? Has it always >> been there? > > Does 'git log --grep=ddof' he

[Numpy-discussion] When was the ddof kwarg added to std()?

Does anyone know when the ddof kwarg was added to std()? Has it always been there? Thanks, Darren ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] core library structure

On Fri, Feb 4, 2011 at 2:23 PM, Lluís wrote: > Darren Dale writes: > >> With generic functions, you wouldn't have to remember to use the ufunc >> provided by masked array for one type, or the default numpy for >> another type. > > Sorry, but I don't see

Re: [Numpy-discussion] core library structure

On Thu, Feb 3, 2011 at 2:07 PM, Mark Wiebe wrote: > Moving this to a new thread. > On Thu, Feb 3, 2011 at 10:50 AM, Charles R > Harris  wrote: >> >> On Thu, Feb 3, 2011 at 11:07 AM, Mark Wiebe  wrote: [...] >>> Yeah, I understand it's the result of organic growth and merging from >>> many differen

Re: [Numpy-discussion] Strange problem with h5py and numpy

On Mon, Dec 27, 2010 at 12:58 PM, Johannes Korn wrote: > Hi, > > I have a strange problem with h5py or with numpy. I think this question belongs on the h5py mailing list. > I try to read a bunch of hdf files in a loop. The problem is that I get > an error at the second file because the file hand

[Numpy-discussion] problem with numpy/cython on python3, ok with python2

I just installed numpy for both python2 and 3 from an up-to-date checkout of the 1.5.x branch. I am attempting to cythonize the following code with cython-0.13: --- cimport numpy as np import numpy as np def test(): cdef np.ndarray[np.float64_t, ndim=1] ret ret_arr = np.zeros((20,), dtype=

[Numpy-discussion] seeking advice on a fast string->array conversion

I am wrapping up a small package to parse a particular ascii-encoded file format generated by a program we use heavily here at the lab. (In the unlikely event that you work at a synchrotron, and use Certified Scientific's "spec" program, and are actually interested, the code is currently available

Re: [Numpy-discussion] seeking advice on a fast string->array conversion

Apologies, I accidentally hit send... On Tue, Nov 16, 2010 at 9:20 AM, Darren Dale wrote: > I am wrapping up a small package to parse a particular ascii-encoded > file format generated by a program we use heavily here at the lab. (In > the unlikely event that you work at a synchrotron

Re: [Numpy-discussion] seeking advice on a fast string->array conversion

On Tue, Nov 16, 2010 at 10:31 AM, Darren Dale wrote: > On Tue, Nov 16, 2010 at 9:55 AM, Pauli Virtanen wrote: >> Tue, 16 Nov 2010 09:41:04 -0500, Darren Dale wrote: >> [clip] >>> That loop takes 0.33 seconds to execute, which is a good start. I need >>> som

Re: [Numpy-discussion] seeking advice on a fast string->array conversion

ut why are your files so > large? > > On Nov 16, 2010 9:20 AM, "Darren Dale" wrote: >> I am wrapping up a small package to parse a particular ascii-encoded >> file format generated by a program we use heavily here at the lab. (In >> the unlikely event that y

Re: [Numpy-discussion] seeking advice on a fast string->array conversion

On Tue, Nov 16, 2010 at 11:46 AM, Christopher Barker wrote: > On 11/16/10 7:31 AM, Darren Dale wrote: >> On Tue, Nov 16, 2010 at 9:55 AM, Pauli Virtanen  wrote: >>> Tue, 16 Nov 2010 09:41:04 -0500, Darren Dale wrote: >>> [clip] >>>> That loop takes 0.33 se

Re: [Numpy-discussion] seeking advice on a fast string->array conversion

On Tue, Nov 16, 2010 at 9:55 AM, Pauli Virtanen wrote: > Tue, 16 Nov 2010 09:41:04 -0500, Darren Dale wrote: > [clip] >> That loop takes 0.33 seconds to execute, which is a good start. I need >> some help converting this example to return an actual numpy array. Could >&g

Re: [Numpy-discussion] bzr mirror

On Sat, Nov 13, 2010 at 7:27 AM, Darren Dale wrote: > On Fri, Nov 12, 2010 at 9:42 PM, Ralf Gommers > wrote: >> Hi, >> >> While cleaning up the numpy wiki start page I came across a bzr mirror >> that still pointed to svn, https://launchpad.net/numpy, originally >

Re: [Numpy-discussion] bzr mirror

On Fri, Nov 12, 2010 at 9:42 PM, Ralf Gommers wrote: > Hi, > > While cleaning up the numpy wiki start page I came across a bzr mirror > that still pointed to svn, https://launchpad.net/numpy, originally > registered by Jarrod. It would be good to either point that to git or > delete it. I couldn't

Re: [Numpy-discussion] whitespace in git repo

On Thu, Oct 28, 2010 at 12:11 PM, Charles R Harris wrote: > > > On Thu, Oct 28, 2010 at 9:23 AM, Darren Dale wrote: >> >> Hi Chuck, >> >> On Wed, Oct 27, 2010 at 1:30 PM, Charles R Harris >> wrote: >> > >> > I'd like to do something

Re: [Numpy-discussion] whitespace in git repo

On Thu, Oct 28, 2010 at 3:23 PM, wrote: > On Thu, Oct 28, 2010 at 2:40 PM, Darren Dale wrote: >> On Thu, Oct 28, 2010 at 12:23 PM,   wrote: >>> On Thu, Oct 28, 2010 at 12:11 PM, Charles R Harris >>>> On Thu, Oct 28, 2010 at 9:23 AM, Darren Dale wrote: >>

Re: [Numpy-discussion] whitespace in git repo

On Thu, Oct 28, 2010 at 12:23 PM, wrote: > On Thu, Oct 28, 2010 at 12:11 PM, Charles R Harris >> On Thu, Oct 28, 2010 at 9:23 AM, Darren Dale wrote: >>> And now the bad news: I have not been able to verify that Git respects >>> the autocrlf setting or the eol sett

Re: [Numpy-discussion] whitespace in git repo

Hi Chuck, On Wed, Oct 27, 2010 at 1:30 PM, Charles R Harris wrote: > > I'd like to do something here, but I'm waiting for a consensus and for > someone to test things out, maybe with a test repo, to make sure things > operate correctly. The documentation isn't that clear... I am getting ready to

Re: [Numpy-discussion] whitespace in git repo

On Wed, Oct 27, 2010 at 11:31 AM, Friedrich Romstedt wrote: > Hi Darren, > > 2010/10/27 Darren Dale : >>> So the svg changes must come from the 'fix' value for the whitespace action. >>> >>> I don't think it is a good idea to let whitespace be

Re: [Numpy-discussion] whitespace in git repo

On Wed, Oct 27, 2010 at 8:36 AM, Friedrich Romstedt wrote: > Hi Darren, > > 2010/10/19 Darren Dale : >> I have the following set in my ~/.gitconfig file: >> >>    [apply] >>        whitespace = fix >> >>    [core] >>        autocrlf = input &

Re: [Numpy-discussion] ANN: NumPy 1.5.1 release candidate 1

On Sun, Oct 24, 2010 at 11:29 AM, Charles R Harris wrote: > > > On Sun, Oct 24, 2010 at 9:22 AM, Darren Dale wrote: >> >> On Sun, Oct 17, 2010 at 7:35 AM, Ralf Gommers >> wrote: >> > Hi, >> > >> > I am pleased to announce the availability of

Re: [Numpy-discussion] ANN: NumPy 1.5.1 release candidate 1

On Sun, Oct 17, 2010 at 7:35 AM, Ralf Gommers wrote: > Hi, > > I am pleased to announce the availability of the first release > candidate of NumPy 1.5.1. This is a bug-fix release with no new > features compared to 1.5.0. [...] > Please report any other issues on the Numpy-discussion mailing list.

Re: [Numpy-discussion] whitespace in git repo

On Thu, Oct 21, 2010 at 4:48 PM, Friedrich Romstedt wrote: > 2010/10/21 Darren Dale : >> I filed a new pull request, http://github.com/numpy/numpy/pull/7 . >> This should enforce LF on all text files, with the current exception >> of the nsi.in file, which is CRLF. The svgs h

Re: [Numpy-discussion] whitespace in git repo

On Thu, Oct 21, 2010 at 9:26 AM, David Cournapeau wrote: > On Thu, Oct 21, 2010 at 8:47 PM, Friedrich Romstedt > wrote: >> 2010/10/21 David Cournapeau : >>> On Thu, Oct 21, 2010 at 12:56 AM, Friedrich Romstedt >>> wrote: >>>> 2010/10/20 Darren Da

Re: [Numpy-discussion] whitespace in git repo

On Wed, Oct 20, 2010 at 11:56 AM, Friedrich Romstedt wrote: > 2010/10/20 Darren Dale : >> On Wed, Oct 20, 2010 at 6:12 AM, Friedrich Romstedt >> wrote: >>> Due to Darren's config file the .nsi.in file made it with CRLF into the >>> repo. >> >>

Re: [Numpy-discussion] whitespace in git repo

On Wed, Oct 20, 2010 at 6:12 AM, Friedrich Romstedt wrote: > Due to Darren's config file the .nsi.in file made it with CRLF into the repo. Uh, no. ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-

[Numpy-discussion] whitespace in git repo

We have been discussing whitespace and line endings at the following pull request: http://github.com/numpy/numpy/pull/4 . Chuck suggested we discuss it here on the list. I have the following set in my ~/.gitconfig file: [apply] whitespace = fix [core] autocrlf = input wh

Re: [Numpy-discussion] test errors in the trunk

On Sat, Jul 31, 2010 at 7:22 AM, Ralf Gommers wrote: > > > On Sat, Jul 31, 2010 at 4:55 AM, Robert Kern wrote: >> >> On Fri, Jul 30, 2010 at 13:22, Darren Dale wrote: >> > I just upgraded my svn checkout and did a fresh install. When I try to >> > ru

[Numpy-discussion] test errors in the trunk

I just upgraded my svn checkout and did a fresh install. When I try to run the test suite, I get a ton of errors: np.test() Running unit tests for numpy NumPy version 2.0.0.dev8550 NumPy is installed in /Users/darren/.local/lib/python2.6/site-packages/numpy Python version 2.6.5 (r265:79063, Jul 1

Re: [Numpy-discussion] question about creating numpy arrays

On Thu, May 20, 2010 at 12:07 PM, Bruce Southey wrote: > np.array is an array creating function that numpy.array takes a > array_like input and it *will* try to convert that input into an array. > (This also occurs when you give np.array a masked array as an input.) > This a 'feature' especially w

Re: [Numpy-discussion] question about creating numpy arrays

[sorry, my last got cut off] On Thu, May 20, 2010 at 11:37 AM, Darren Dale wrote: > On Thu, May 20, 2010 at 10:44 AM, Benjamin Root wrote: >>> I gave two counterexamples of why. >> >> The examples you gave aren't counterexamples.  See below... > > I'm

Re: [Numpy-discussion] question about creating numpy arrays

ts that derive from ndarray, and am concerned about the implications for classes that extend ndarray. > On Wed, May 19, 2010 at 7:06 PM, Darren Dale wrote: >> >> On Wed, May 19, 2010 at 4:19 PM,   wrote: >> > On Wed, May 19, 2010 at 4:08 PM, Darren Dale wrote: >> &

Re: [Numpy-discussion] question about creating numpy arrays

On Wed, May 19, 2010 at 4:19 PM, wrote: > On Wed, May 19, 2010 at 4:08 PM, Darren Dale wrote: >> I have a question about creation of numpy arrays from a list of >> objects, which bears on the Quantities project and also on masked >> arrays: >> >>>>> imp

[Numpy-discussion] question about creating numpy arrays

I have a question about creation of numpy arrays from a list of objects, which bears on the Quantities project and also on masked arrays: >>> import quantities as pq >>> import numpy as np >>> a, b = 2*pq.m,1*pq.s >>> np.array([a, b]) array([ 12., 1.]) Why doesn't that create an object array? S

Re: [Numpy-discussion] Bug in numpy.fix(): broken for scalar arguments

On Sun, Apr 18, 2010 at 9:28 AM, Darren Dale wrote: > On Sun, Apr 18, 2010 at 9:08 AM, Darren Dale wrote: >> On Sat, Apr 17, 2010 at 4:16 PM, Charles R Harris >> wrote: >>> >>> >>> On Sat, Apr 17, 2010 at 2:01 PM, Eric Firing wrote: >>>&

Re: [Numpy-discussion] Bug in numpy.fix(): broken for scalar arguments

On Sun, Apr 18, 2010 at 9:08 AM, Darren Dale wrote: > On Sat, Apr 17, 2010 at 4:16 PM, Charles R Harris > wrote: >> >> >> On Sat, Apr 17, 2010 at 2:01 PM, Eric Firing wrote: >>> >>> np.fix() no longer works for scalar arguments: >>&

Re: [Numpy-discussion] Bug in numpy.fix(): broken for scalar arguments

On Sat, Apr 17, 2010 at 4:16 PM, Charles R Harris wrote: > > > On Sat, Apr 17, 2010 at 2:01 PM, Eric Firing wrote: >> >> np.fix() no longer works for scalar arguments: >> >> >> In [1]:import numpy as np >> >> In [2]:np.version.version >> Out[2]:'2.0.0.dev8334' >> >> In [3]:np.fix(3.14) >> >>

Re: [Numpy-discussion] ufunc improvements [Was: Warnings in numpy.ma.test()]

asked arrays or masked arrays not dealing well with trapz. There is an additional bit at the end that was not discussed elsewhere. On Thu, Mar 18, 2010 at 8:14 AM, Darren Dale wrote: > On Wed, Mar 17, 2010 at 10:16 PM, Charles R Harris > wrote: >> Just *one* function to rule them all a

Re: [Numpy-discussion] numpy.trapz() doesn't respect subclass

On Sat, Mar 27, 2010 at 10:23 PM, wrote: > subclasses of ndarray, like masked_arrays and quantities, and classes > that delegate to array calculations, like pandas, can redefine > anything. So there is not much that can be relied on if any subclass > is allowed to be used inside a function > > e.

[Numpy-discussion] should ndarray implement __round__ for py3k?

A simple test in python 3: >>> import numpy as np >>> round(np.arange(10)) Traceback (most recent call last): File "", line 1, in TypeError: type numpy.ndarray doesn't define __round__ method Here is some additional context: http://bugs.python.org/issue7261 Darren

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 10:16 PM, Charles R Harris wrote: > On Wed, Mar 17, 2010 at 7:39 PM, Darren Dale wrote: >> On Wed, Mar 17, 2010 at 8:22 PM, Charles R Harris >> > What bothers me here is the opposing desire to separate ufuncs from >> > their >> > ndarra

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Thu, Mar 18, 2010 at 5:12 PM, Eric Firing wrote: > Ryan May wrote: >> On Thu, Mar 18, 2010 at 2:46 PM, Christopher Barker >> wrote: >>> Gael Varoquaux wrote: On Thu, Mar 18, 2010 at 12:12:10PM -0700, Christopher Barker wrote: > sure -- that's kind of my point -- if EVERY numpy array w

[Numpy-discussion] ufunc improvements [Was: Warnings in numpy.ma.test()]

On Wed, Mar 17, 2010 at 10:16 PM, Charles R Harris wrote: > > > On Wed, Mar 17, 2010 at 7:39 PM, Darren Dale wrote: >> >> On Wed, Mar 17, 2010 at 8:22 PM, Charles R Harris >> wrote: >> > >> > >> > On Wed, Mar 17, 2010 at 5:26 PM, Darren Da

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 8:22 PM, Charles R Harris wrote: > > > On Wed, Mar 17, 2010 at 5:26 PM, Darren Dale wrote: >> >> On Wed, Mar 17, 2010 at 5:43 PM, Charles R Harris >> wrote: >> > On Wed, Mar 17, 2010 at 3:13 PM, Darren Dale wrote: >> >

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 5:43 PM, Charles R Harris wrote: > On Wed, Mar 17, 2010 at 3:13 PM, Darren Dale wrote: >> On Wed, Mar 17, 2010 at 4:48 PM, Pierre GM wrote: >> > On Mar 17, 2010, at 8:19 AM, Darren Dale wrote: >> >> >> >> I started thinking abo

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 4:48 PM, Pierre GM wrote: > On Mar 17, 2010, at 8:19 AM, Darren Dale wrote: >> >> I started thinking about a third method called __input_prepare__ that >> would be called on the way into the ufunc, which would allow you to >> intercept the input

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 10:45 AM, Charles R Harris wrote: > > > On Wed, Mar 17, 2010 at 6:19 AM, Darren Dale wrote: >> >> On Wed, Mar 17, 2010 at 2:07 AM, Pierre GM wrote: >> > All, >> > As you're probably aware, the current test suite for numpy.

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 10:11 AM, Ryan May wrote: > On Wed, Mar 17, 2010 at 7:19 AM, Darren Dale wrote: >> Is this general enough for your use case? I haven't tried to think >> about how to change some global state at one point and change it back >> at another, that

Re: [Numpy-discussion] Warnings in numpy.ma.test()

On Wed, Mar 17, 2010 at 2:07 AM, Pierre GM wrote: > All, > As you're probably aware, the current test suite for numpy.ma raises some > nagging warnings such as "invalid value in ...". These warnings are only > issued when a standard numpy ufunc (eg., np.sqrt) is called on a MaskedArray, > inste

Re: [Numpy-discussion] subclassing ndarray in python3

Hi Pauli, On Thu, Mar 11, 2010 at 3:38 PM, Pauli Virtanen wrote: > Thanks for testing. I wish the test suite was more complete (hint! > hint! :) I'll be happy to contribute, but lately I get a few 15-30 minute blocks a week for this kind of work (hence the short attempt to work on Quantities thi

[Numpy-discussion] subclassing ndarray in python3

Now that the trunk has some support for python3, I am working on making Quantities work with python3 as well. I'm running into some problems related to subclassing ndarray that can be illustrated with a simple script, reproduced below. It looks like there is a problem with the reflected operations,

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Fri, Feb 12, 2010 at 12:16 AM, David Cournapeau wrote: > Charles R Harris wrote: > >> >> >> I don't see any struct definitions there, it looks clean. > > Any struct defined outside numpy/core/include is fine to change at will > as far as ABI is concerned anyway, so no need to check anything :)

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 11, 2010 at 11:57 PM, Charles R Harris wrote: > > > On Thu, Feb 11, 2010 at 9:39 PM, Darren Dale wrote: >> >> On Thu, Feb 11, 2010 at 11:22 PM, Charles R Harris >> wrote: >> > >> > >> > On Thu, Feb 11, 2010 at 8:12 PM, David Cou

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 11, 2010 at 11:22 PM, Charles R Harris wrote: > > > On Thu, Feb 11, 2010 at 8:12 PM, David Cournapeau > wrote: >> >> Charles R Harris wrote: >> > >> > >> > On Thu, Feb 11, 2010 at 7:00 PM, David Cournapeau > > > wrote: >> > >> >     josef.p...@gmail.com <

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

2010/2/11 Stéfan van der Walt : > On 11 February 2010 09:52, Charles R Harris wrote: >> Simple, eh. The version should be 2.0. > > I'm going with the element of least surprise: no one will be surprised > when 1.5 is released with ABI changes I'll buy you a doughnut if that turns out to be correct

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Wed, Feb 10, 2010 at 3:31 PM, Travis Oliphant wrote: > On Feb 8, 2010, at 4:08 PM, Darren Dale wrote: >> I definitely should have counted to 100 before sending that. It wasn't >> helpful and I apologize. > > I actually found this quite funny.    I need to apolog

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Mon, Feb 8, 2010 at 10:53 PM, Charles R Harris wrote: > > > On Mon, Feb 8, 2010 at 8:40 PM, Darren Dale wrote: >> >> On Mon, Feb 8, 2010 at 10:35 PM, Charles R Harris >> wrote: >> > >> > >> > On Mon, Feb 8, 2010 at 8:27 PM, Darren Da

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Mon, Feb 8, 2010 at 10:35 PM, Charles R Harris wrote: > > > On Mon, Feb 8, 2010 at 8:27 PM, Darren Dale wrote: >> >> On Mon, Feb 8, 2010 at 10:24 PM, Robert Kern >> wrote: >> > On Mon, Feb 8, 2010 at 21:23, Darren Dale wrote: >> >> On Mon, F

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Mon, Feb 8, 2010 at 10:24 PM, Robert Kern wrote: > On Mon, Feb 8, 2010 at 21:23, Darren Dale wrote: >> On Mon, Feb 8, 2010 at 10:10 PM, Robert Kern wrote: >>> On Mon, Feb 8, 2010 at 20:50, Darren Dale wrote: >>>> On Mon, Feb 8, 2010 at 7:52 PM, Robert Kern wr

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Mon, Feb 8, 2010 at 10:10 PM, Robert Kern wrote: > On Mon, Feb 8, 2010 at 20:50, Darren Dale wrote: >> On Mon, Feb 8, 2010 at 7:52 PM, Robert Kern wrote: >>> On Mon, Feb 8, 2010 at 18:43, Darren Dale wrote: >>>> On Mon, Feb 8, 2010 at 7:25 PM, Robert Kern w

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Mon, Feb 8, 2010 at 7:52 PM, Robert Kern wrote: > On Mon, Feb 8, 2010 at 18:43, Darren Dale wrote: >> On Mon, Feb 8, 2010 at 7:25 PM, Robert Kern wrote: >>> Here's the problem that I don't think many people appreciate: logical >>> arguments suck j

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Mon, Feb 8, 2010 at 7:25 PM, Robert Kern wrote: > Here's the problem that I don't think many people appreciate: logical > arguments suck just as much as personal experience in answering these > questions. You can make perfectly structured arguments until you are > blue in the face, but without

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Mon, Feb 8, 2010 at 5:05 PM, Darren Dale wrote: > On Mon, Feb 8, 2010 at 5:05 PM, Jarrod Millman wrote: >> On Mon, Feb 8, 2010 at 1:57 PM, Charles R Harris >> wrote: >>> Should the release containing the datetime/hasobject changes be called >>> >>> a

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Mon, Feb 8, 2010 at 5:05 PM, Jarrod Millman wrote: > On Mon, Feb 8, 2010 at 1:57 PM, Charles R Harris > wrote: >> Should the release containing the datetime/hasobject changes be called >> >> a) 1.5.0 >> b) 2.0.0 > > My vote goes to b. You don't matter. Nor do I. __

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

I'm breaking my promise, after people wrote me offlist encouraging me to keep pushing my point of view. On Sun, Feb 7, 2010 at 8:23 PM, David Cournapeau wrote: > Jarrod Millman wrote: >>  Just >> to be clear, I would prefer to see the ABI-breaking release be called >> 2.0.  I don't see why we hav

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Sat, Feb 6, 2010 at 10:16 PM, Travis Oliphant wrote: > I will just work on trunk and assume that the next release will be ABI > incompatible.   At this point I would rather call the next version 1.5 > than 2.0, though.  When the date-time work is completed, then we could > release an ABI-compat

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Sat, Feb 6, 2010 at 8:39 AM, David Cournapeau wrote: > On Sat, Feb 6, 2010 at 10:36 PM, Darren Dale wrote: >> >> I don't understand why there is any debate about what to call a >> release that breaks ABI compatibility. > > Because it means datetime support wil

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Sat, Feb 6, 2010 at 8:29 AM, wrote: > On Sat, Feb 6, 2010 at 8:07 AM, Francesc Alted wrote: >> A Saturday 06 February 2010 13:17:22 David Cournapeau escrigué: >>> On Sat, Feb 6, 2010 at 4:07 PM, Travis Oliphant >> wrote: >>> > I think this plan is the least disruptive and satisfies the conce

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Fri, Feb 5, 2010 at 10:25 PM, Travis Oliphant wrote: > > On Feb 5, 2010, at 2:32 PM, Christopher Barker wrote: > >> Hi folks, >> >> It sounds like a consensus has been reached to put out a 1.4.1 that is >> ABI compatible with 1.3.* > > This is not true.   Consensus has not been reached. How ma

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Thu, Feb 4, 2010 at 3:21 AM, Francesc Alted wrote: > A Thursday 04 February 2010 08:46:01 Charles R Harris escrigué: >> > Perhaps one way to articulate my perspective is the following: >> > >> > There are currently 2 groups of NumPy users: >> > >> >  1)  those who have re-compiled all of their

[Numpy-discussion] numpy.test(): invalid value encountered in {isinf, divide, power, ...}

I haven't been following development on the trunk closely, so I apologize if this is a known issue. I didn't see anything relevant when I searched the list. I just updated my checkout of the trunk, cleaned out the old installation and build/, and reinstalled. When I run the test suite (without spe

Re: [Numpy-discussion] [SciPy-dev] Announcing toydist, improving distribution and packaging situation

On Wed, Dec 30, 2009 at 11:16 AM, David Cournapeau wrote: > On Wed, Dec 30, 2009 at 11:26 PM, Darren Dale wrote: >> Hi David, >> >> On Mon, Dec 28, 2009 at 9:03 AM, David Cournapeau wrote: >>> Executable: grin >>>    module: grin >>>

Re: [Numpy-discussion] Announcing toydist, improving distribution and packaging situation

On Wed, Dec 30, 2009 at 9:26 AM, Ravi wrote: > On Wednesday 30 December 2009 06:15:45 René Dudfield wrote: > >> I agree with many things in that post.  Except your conclusion on >> multiple versions of packages in isolation.  Package isolation is like >> processes, and package sharing is like thre

Re: [Numpy-discussion] Announcing toydist, improving distribution and packaging situation

Hi David, On Mon, Dec 28, 2009 at 9:03 AM, David Cournapeau wrote: > Executable: grin >    module: grin >    function: grin_main > > Executable: grind >    module: grin >    function: grind_main Have you thought at all about operations that are currently performed by post-installation scripts? F

Re: [Numpy-discussion] Cython issues w/ 1.4.0

On Tue, Dec 8, 2009 at 12:02 PM, Pauli Virtanen wrote: > Sun, 06 Dec 2009 14:53:58 +0100, Gael Varoquaux wrote: >> I have a lot of code that has stopped working with my latest SVN pull to >> numpy. >> >> * Some compiled code yields an error looking like (from memory): >> >>     "incorrect type 'nu

Re: [Numpy-discussion] Py3 merge

On Sat, Dec 5, 2009 at 10:54 PM, David Cournapeau wrote: > On Sun, Dec 6, 2009 at 9:41 AM, Pauli Virtanen wrote: >> Hi, >> >> I'd like to commit my Py3 Numpy branch to SVN trunk soon: >> >>        http://github.com/pv/numpy-work/commits/py3k > > Awesome - I think we should merge this ASAP. In par

Re: [Numpy-discussion] REMINDER: trunk is about to be frozen for 1.4.0

On Tue, Nov 17, 2009 at 8:55 PM, David Cournapeau wrote: > already done  in r7743 :) Did you report it as a bug on trac, so that > I close it as well, Oh, thanks! No, I forgot to report it on trac, I'll try to remember that in the future. ___ NumPy-Disc

Re: [Numpy-discussion] REMINDER: trunk is about to be frozen for 1.4.0

Please consider applying this patch before freezing, or you can't do "python setup.py develop" with Distribute (at least not with Enthought's Enable): ndex: numpy/distutils/command/build_ext.py === --- numpy/distutils/command/build_ex

Re: [Numpy-discussion] numpy distutils and distribute

On Sat, Nov 14, 2009 at 10:42 AM, Gökhan Sever wrote: > On Sat, Nov 14, 2009 at 9:29 AM, Darren Dale wrote: >> >> Please excuse the cross-post. I have installed distribute-0.6.8 and >> numpy-svn into my ~/.local/lib/python2.6/site-packages (using "python >> set

[Numpy-discussion] numpy distutils and distribute

Please excuse the cross-post. I have installed distribute-0.6.8 and numpy-svn into my ~/.local/lib/python2.6/site-packages (using "python setup.py install --user"). I am now trying to install Enthought's Enable from a fresh svn checkout on ubuntu karmic: $ python setup.py develop --user [...] buil

Re: [Numpy-discussion] 1.4.0: Setting a firm release date for 1st december.

On Mon, Nov 2, 2009 at 3:29 AM, David Cournapeau wrote: > Hi, > > I think it is about time to release 1.4.0. Instead of proposing a > release date, I am setting a firm date for 1st December, and 16th > november to freeze the trunk. If someone wants a different date, you > have to speak now. > > Th

Re: [Numpy-discussion] numpy and C99

On Fri, Oct 23, 2009 at 9:29 AM, Pauli Virtanen wrote: > Fri, 23 Oct 2009 09:21:17 -0400, Darren Dale wrote: >> Can we use features of C99 in numpy? For example, can we use "//" style >> comments, and C99 for statements "for (int i=0, ...) "? > > It would

[Numpy-discussion] numpy and C99

Can we use features of C99 in numpy? For example, can we use "//" style comments, and C99 for statements "for (int i=0, ...) "? Darren ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Another suggestion for making numpy's functions generic

Hi Travis, On Mon, Oct 19, 2009 at 6:29 PM, Travis Oliphant wrote: > > On Oct 17, 2009, at 7:49 AM, Darren Dale wrote: [...] >> When calling numpy functions: >> >> 1) __input_prepare__ provides an opportunity to operate on the inputs >> to yield versions that are

Re: [Numpy-discussion] Another suggestion for making numpy's functions generic

On Tue, Oct 20, 2009 at 5:24 AM, Sebastian Walter wrote: > I'm not very familiar with the underlying C-API of numpy, so this has > to be taken with a grain of salt. > > The reason why I'm curious about the genericity is that it would be > awesome to have: > 1) ufuncs like sin, cos, exp... to work

Re: [Numpy-discussion] Another suggestion for making numpy's functions generic

On Mon, Oct 19, 2009 at 3:10 AM, Sebastian Walter wrote: > On Sat, Oct 17, 2009 at 2:49 PM, Darren Dale wrote: >> numpy's functions, especially ufuncs, have had some ability to support >> subclasses through the ndarray.__array_wrap__ method, which provides >> masked

Re: [Numpy-discussion] Subclassing record array

: >> >>   - I can't access data through indexing >> In [563]: bloc['Price'] >> /home/loic/Python/numpy/test.py in ((r,)) >>     50 >>     51     def __repr__(self): >> ---> 52         return self._head + ''.join(self._fmt % tuple(r)

Re: [Numpy-discussion] Another suggestion for making numpy's functions generic

On Sat, Oct 17, 2009 at 6:45 PM, Charles R Harris wrote: > > > On Sat, Oct 17, 2009 at 6:49 AM, Darren Dale wrote: [...] >> I think it will be not too difficult to document this overall scheme: >> >> When calling numpy functions: >> >> 1) __input_prepare_

[Numpy-discussion] Another suggestion for making numpy's functions generic

numpy's functions, especially ufuncs, have had some ability to support subclasses through the ndarray.__array_wrap__ method, which provides masked arrays or quantities (for example) with an opportunity to set the class and metadata of the output array at the end of an operation. An example is q1 =

Re: [Numpy-discussion] __array_wrap__

On Wed, Sep 30, 2009 at 2:57 AM, Pauli Virtanen wrote: > Tue, 29 Sep 2009 14:55:44 -0400, Neal Becker wrote: > >> This seems to work now, but I'm wondering if Charles is correct, that >> inheritance isn't such a great idea here. >> >> The advantage of inheritance is I don't have to implement forwa

  1   2   3   >