Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 11:00 PM, David Cournapeau wrote: > Charles R Harris wrote: > > > > > > > > Just to be clear, there are *already* macros in the ndarrayobject.h file > > that aren't py3k compatible. How do you propose to fix those? > > I don't understand the connection with the public vs pr

Re: [Numpy-discussion] numpy 2.0, what else to do?

Charles R Harris wrote: > > > > Just to be clear, there are *already* macros in the ndarrayobject.h file > that aren't py3k compatible. How do you propose to fix those? I don't understand the connection with the public vs private issue. If the py3k compatibility header is to be shared by seve

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 10:35 PM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Mon, Feb 15, 2010 at 10:19 PM, David Cournapeau > wrote: > >> Charles R Harris wrote: >> > >> > >> > On Mon, Feb 15, 2010 at 8:13 PM, David Cournapeau < >> da...@silveregg.co.jp >> >

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 10:19 PM, David Cournapeau wrote: > Charles R Harris wrote: > > > > > > On Mon, Feb 15, 2010 at 8:13 PM, David Cournapeau > > wrote: > > > > Charles R Harris wrote: > > > > > > > > > On Mon, Feb 15, 2010 at 3:58 PM, Charles

Re: [Numpy-discussion] numpy 2.0, what else to do?

Charles R Harris wrote: > > > On Mon, Feb 15, 2010 at 8:13 PM, David Cournapeau > wrote: > > Charles R Harris wrote: > > > > > > On Mon, Feb 15, 2010 at 3:58 PM, Charles R Harris > > mailto:charlesr.har...@gmail.com> >

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 8:13 PM, David Cournapeau wrote: > Charles R Harris wrote: > > > > > > On Mon, Feb 15, 2010 at 3:58 PM, Charles R Harris > > mailto:charlesr.har...@gmail.com>> wrote: > > > > > > > > On Mon, Feb 15, 2010 at 3:34 PM, David Cournapeau > > mailto:courn...@gmail.com>> w

Re: [Numpy-discussion] numpy 2.0, what else to do?

Charles R Harris wrote: > > > On Mon, Feb 15, 2010 at 3:58 PM, Charles R Harris > mailto:charlesr.har...@gmail.com>> wrote: > > > > On Mon, Feb 15, 2010 at 3:34 PM, David Cournapeau > mailto:courn...@gmail.com>> wrote: > > On Tue, Feb 16, 2010 at 7:04 AM, Charles R Harris >

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 3:58 PM, Charles R Harris wrote: > > > On Mon, Feb 15, 2010 at 3:34 PM, David Cournapeau wrote: > >> On Tue, Feb 16, 2010 at 7:04 AM, Charles R Harris >> wrote: >> > >> > >> > On Mon, Feb 15, 2010 at 2:46 PM, David Cournapeau >> > wrote: >> >> >> >> On Tue, Feb 16, 2010

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 3:34 PM, David Cournapeau wrote: > On Tue, Feb 16, 2010 at 7:04 AM, Charles R Harris > wrote: > > > > > > On Mon, Feb 15, 2010 at 2:46 PM, David Cournapeau > > wrote: > >> > >> On Tue, Feb 16, 2010 at 4:08 AM, Charles R Harris > >> wrote: > >> > >> > > >> > I was wonderi

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Tue, Feb 16, 2010 at 7:04 AM, Charles R Harris wrote: > > > On Mon, Feb 15, 2010 at 2:46 PM, David Cournapeau > wrote: >> >> On Tue, Feb 16, 2010 at 4:08 AM, Charles R Harris >> wrote: >> >> > >> > I was wondering about that. Why do we have a private include directory? >> > Would it make more

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 2:46 PM, David Cournapeau wrote: > On Tue, Feb 16, 2010 at 4:08 AM, Charles R Harris > wrote: > > > > > I was wondering about that. Why do we have a private include directory? > > Would it make more sense to move it to core/include/numpy/private. > > No, the whole point is

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Tue, Feb 16, 2010 at 4:08 AM, Charles R Harris wrote: > > I was wondering about that. Why do we have a private include directory? > Would it make more sense to move it to core/include/numpy/private. No, the whole point is to avoid other packages to include that by mistake, to avoid namespace

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 12:03 PM, Pauli Virtanen wrote: > su, 2010-02-14 kello 11:51 -0700, Charles R Harris kirjoitti: > [clip] > > There are more - grep -r ob_type numpy/* - how do you want to go about > > fixing these things? > > self->ob_type is fine if `self` is a plain PyObject* and not a s

Re: [Numpy-discussion] numpy 2.0, what else to do?

su, 2010-02-14 kello 11:51 -0700, Charles R Harris kirjoitti: [clip] > There are more - grep -r ob_type numpy/* - how do you want to go about > fixing these things? self->ob_type is fine if `self` is a plain PyObject* and not a subclass pointer. The issue in changing all of them to Py_TYPE is tha

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 10:04 AM, David Huard wrote: > In the list of things to do, I suggest deleting completely the old > histogram behaviour and the `new` keyword. +1 ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/

Re: [Numpy-discussion] numpy 2.0, what else to do?

In the list of things to do, I suggest deleting completely the old histogram behaviour and the `new` keyword. The `new` keyword argument has raised a deprecation warning since 1.3 and was set for removal in 1.4. David H. On Mon, Feb 15, 2010 at 9:21 AM, Robert Kern wrote: > On Mon, Feb 15, 2010

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 05:24, David Cournapeau wrote: > David Cournapeau wrote: > >> >> It is always an ABI change, but is mostly backward compatible (which is >> neither the case of matplotlib or scipy AFAIK). > > This sentence does not make any sense: I meant that it is backward > compatible fr

Re: [Numpy-discussion] numpy 2.0, what else to do?

David Cournapeau wrote: > > It is always an ABI change, but is mostly backward compatible (which is > neither the case of matplotlib or scipy AFAIK). This sentence does not make any sense: I meant that it is backward compatible from an ABI POV, unless the structure PyArray_Array itself is inc

Re: [Numpy-discussion] numpy 2.0, what else to do?

Sebastian Haase wrote: > On Mon, Feb 15, 2010 at 11:17 AM, Francesc Alted wrote: >> A Sunday 14 February 2010 13:40:17 Stéfan van der Walt escrigué: >>> On 14 February 2010 01:23, David Cournapeau wrote: I think that there should be absolutely no change whatsoever, for two reasons: - th

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Mon, Feb 15, 2010 at 11:17 AM, Francesc Alted wrote: > A Sunday 14 February 2010 13:40:17 Stéfan van der Walt escrigué: >> On 14 February 2010 01:23, David Cournapeau wrote: >> > I think that there should be absolutely no change whatsoever, for two >> > reasons: - the release is in a few weeks

Re: [Numpy-discussion] numpy 2.0, what else to do?

A Sunday 14 February 2010 13:40:17 Stéfan van der Walt escrigué: > On 14 February 2010 01:23, David Cournapeau wrote: > > I think that there should be absolutely no change whatsoever, for two > > reasons: - the release is in a few weeks, it is too late to change much. > > The whole datetime issue

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Sun, Feb 14, 2010 at 17:38, Xavier Gnata wrote: > BTW, is there a better place to discuss these "python3 only" related issues? I suggest starting a new thread, but numpy-discussion is the right place. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigm

Re: [Numpy-discussion] numpy 2.0, what else to do?

Ok! git clone git://github.com/pv/numpy-work.git git checkout origin/py3k NPY_SEPARATE_BUILD=1 python3.1 setup.py build but now it fails during the build: n file included from numpy/core/src/multiarray/buffer.c:14, from numpy/core/src/multiarray/multiarraymodule_onefile.c:36: numpy/core/src/multi

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Sun, Feb 14, 2010 at 11:38 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Sun, Feb 14, 2010 at 11:32 AM, Pauli Virtanen wrote: > >> Charles R Harris gmail.com> writes: >> > - if (ap1->ob_type != ap2->ob_type) { >> > + if (Py_TYPE(ap1) != Py_TYPE(ap2)) { >> > >> > Pauli fix

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Sun, Feb 14, 2010 at 11:32 AM, Pauli Virtanen wrote: > Charles R Harris gmail.com> writes: > > - if (ap1->ob_type != ap2->ob_type) { > > + if (Py_TYPE(ap1) != Py_TYPE(ap2)) { > > > > Pauli fixed a lot of those. Did you remove the old build directory and > all > that stuff? > > I thought I fi

Re: [Numpy-discussion] numpy 2.0, what else to do?

Charles R Harris gmail.com> writes: > -  if (ap1->ob_type != ap2->ob_type) { > + if (Py_TYPE(ap1) != Py_TYPE(ap2)) { > > Pauli fixed a lot of those. Did you remove the old build directory and all that stuff? I thought I fixed all of those, but apparently missed that one. Builds fine for me, but

Re: [Numpy-discussion] numpy 2.0, what else to do?

Xavier Gnata gmail.com> writes: > Well I ran git clone git://github.com/pv/numpy-work.git an hour ago (in > an empty directory) That will give you the master branch, which indeed does not contain any Py3 stuff. You need also to switch to the py3k branch: git co origin/py3k To see all availa

Re: [Numpy-discussion] numpy 2.0, what else to do?

On 14 February 2010 01:23, David Cournapeau wrote: > I think that there should be absolutely no change whatsoever, for two reasons: >  - the release is in a few weeks, it is too late to change much. The > whole datetime issue happened because the change came too late, I > would hope that we avoid

Re: [Numpy-discussion] numpy 2.0, what else to do?

Dag Sverre Seljebotn wrote: > Pauli Virtanen wrote: >> We will most likely have experimental py3 support in 2.0. >> >> If you, or someone else wishes to help bringing 2.0 to fully work >> with Py3, now is a very good time to step up. >> > ... >> Finally, try to write some PEP 3118 using code, a

Re: [Numpy-discussion] numpy 2.0, what else to do?

Pauli Virtanen wrote: > We will most likely have experimental py3 support in 2.0. > > If you, or someone else wishes to help bringing 2.0 to fully work with Py3, > now is a very good time to step up. > ... > Finally, try to write some PEP 3118 using code, and check how it works. (You > can use

Re: [Numpy-discussion] numpy 2.0, what else to do?

On 02/13/2010 09:28 PM, Pauli Virtanen wrote: > We will most likely have experimental py3 support in 2.0. > > If you, or someone else wishes to help bringing 2.0 to fully work with Py3, > now is a very good time to step up. > > How to give a hand: > > 1. Get my latest py3 branch from http://github

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Sat, Feb 13, 2010 at 11:13 PM, Matthew Brett wrote: > Hi, > > > Sounds to me like you don't fully agree w/ Travis - he said "This is > exactly > > what I was worried about with calling the next release 2.0." Seems that > > Travis understands that the larger community, whether we want them to o

Re: [Numpy-discussion] numpy 2.0, what else to do?

Hi, > Sounds to me like you don't fully agree w/ Travis - he said "This is exactly > what I was worried about with calling the next release 2.0."  Seems that > Travis understands that the larger community, whether we want them to or > not, _does_ "attach...much importance to [a] big number change"

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Sat, Feb 13, 2010 at 11:59 AM, Matthew Brett wrote: > Hi, > > On Sat, Feb 13, 2010 at 11:53 AM, Xavier Gnata > wrote: > > IMHO 2.0 should support python3. > > That would be a major step and a good reason to call it 2.0. > > I agree with Travis, I think we should try not to attach too much > im

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Sun, Feb 14, 2010 at 1:24 AM, Charles R Harris wrote: > Hi All, > > Since there has been talk of deprecating the numarray and numeric > compatibility parts of numpy for the upcoming 2.0 release I thought maybe we > could consider a few other changes. First, numpy imports a ton of stuff by > def

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Feb 13, 2010, at 11:24 AM, Charles R Harris wrote: > Hi All, > > Since there has been talk of deprecating the numarray and numeric > compatibility Can someone be explicit about what is mean by this deprecation? > parts of numpy for the upcoming 2.0 release I thought maybe we could > cons

Re: [Numpy-discussion] numpy 2.0, what else to do?

I clarified my vote on these topics in a follow up email to Jared's separating the ideas. -- (mobile phone of) Travis Oliphant Enthought, Inc. 1-512-536-1057 http://www.enthought.com On Feb 13, 2010, at 1:44 PM, Travis Oliphant wrote: > -1 > > -- > (mobile phone of) > Travis Oliphant > Enth

Re: [Numpy-discussion] numpy 2.0, what else to do?

Yes such changes could be done in the 2.x series with appropriate transition aids like deprecation warnings. Travis -- (mobile phone of) Travis Oliphant Enthought, Inc. 1-512-536-1057 http://www.enthought.com On Feb 13, 2010, at 2:01 PM, Charles R Harris wrote: On Sat, Feb 13, 2010 at

Re: [Numpy-discussion] numpy 2.0, what else to do?

-- (mobile phone of) Travis Oliphant Enthought, Inc. 1-512-536-1057 http://www.enthought.com On Feb 13, 2010, at 2:34 PM, Jarrod Millman wrote: > On Sat, Feb 13, 2010 at 1:49 PM, Travis Oliphant > wrote: >> This is exactly what I was worried about with calling the next >> release >> 2.0.

Re: [Numpy-discussion] numpy 2.0, what else to do?

On 02/13/2010 10:15 PM, Charles R Harris wrote: > > > On Sat, Feb 13, 2010 at 2:07 PM, Xavier Gnata > wrote: > > On 02/13/2010 09:28 PM, Pauli Virtanen wrote: > > We will most likely have experimental py3 support in 2.0. > > > > If you, or someone els

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Sat, Feb 13, 2010 at 2:07 PM, Xavier Gnata wrote: > On 02/13/2010 09:28 PM, Pauli Virtanen wrote: > > We will most likely have experimental py3 support in 2.0. > > > > If you, or someone else wishes to help bringing 2.0 to fully work with > Py3, now is a very good time to step up. > > > > How t

Re: [Numpy-discussion] numpy 2.0, what else to do?

On 02/13/2010 09:28 PM, Pauli Virtanen wrote: > We will most likely have experimental py3 support in 2.0. > > If you, or someone else wishes to help bringing 2.0 to fully work with Py3, > now is a very good time to step up. > > How to give a hand: > > 1. Get my latest py3 branch from http://github

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Sat, Feb 13, 2010 at 1:49 PM, Travis Oliphant wrote: > This is exactly what I was worried about with calling the next release > 2.0. > > This is not the time to change all the things we wish were done > differently. > > The release is scheduled for 3 weeks. Hey Travis, I agree with your gener

Re: [Numpy-discussion] numpy 2.0, what else to do?

We will most likely have experimental py3 support in 2.0. If you, or someone else wishes to help bringing 2.0 to fully work with Py3, now is a very good time to step up. How to give a hand: 1. Get my latest py3 branch from http://github.com/pv/numpy-work/tree/py3k Read doc/py3k.txt 2. Get py3

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Sat, Feb 13, 2010 at 12:49 PM, Travis Oliphant wrote: > This is exactly what I was worried about with calling the next release > 2.0. > > This is not the time to change all the things we wish were done > differently. > > Do you think it would be reasonable to make such changes in 2.x? They woul

Re: [Numpy-discussion] numpy 2.0, what else to do?

Hi, On Sat, Feb 13, 2010 at 11:53 AM, Xavier Gnata wrote: > IMHO 2.0 should support python3. > That would be a major step and a good reason to call it 2.0. I agree with Travis, I think we should try not to attach too much importance to the big number change, release 2.0 just taking care of the A

Re: [Numpy-discussion] numpy 2.0, what else to do?

IMHO 2.0 should support python3. That would be a major step and a good reason to call it 2.0. Xavier > This is exactly what I was worried about with calling the next release > 2.0. > > This is not the time to change all the things we wish were done > differently. > > The release is scheduled

Re: [Numpy-discussion] numpy 2.0, what else to do?

On 02/13/2010 07:31 PM, Charles R Harris wrote: > > > On Sat, Feb 13, 2010 at 11:23 AM, Joe Harrington > wrote: > > Chuck Harris writes (on numpy-discussion): > > > Since there has been talk of deprecating the numarray and numeric > > compatibility parts of

Re: [Numpy-discussion] numpy 2.0, what else to do?

This is exactly what I was worried about with calling the next release 2.0. This is not the time to change all the things we wish were done differently. The release is scheduled for 3 weeks. Travis -- (mobile phone of) Travis Oliphant Enthought, Inc. 1-512-536-1057 http://www.enthought.com

Re: [Numpy-discussion] numpy 2.0, what else to do?

-1 -- (mobile phone of) Travis Oliphant Enthought, Inc. 1-512-536-1057 http://www.enthought.com On Feb 13, 2010, at 10:24 AM, Charles R Harris wrote: > Hi All, > > Since there has been talk of deprecating the numarray and numeric > compatibility parts of numpy for the upcoming 2.0 release I t

Re: [Numpy-discussion] numpy 2.0, what else to do?

On Sat, Feb 13, 2010 at 11:23 AM, Joe Harrington wrote: > Chuck Harris writes (on numpy-discussion): > > > Since there has been talk of deprecating the numarray and numeric > > compatibility parts of numpy for the upcoming 2.0 release I thought maybe > we > > could consider a few other changes. F

Re: [Numpy-discussion] numpy 2.0, what else to do?

Chuck Harris writes (on numpy-discussion): > Since there has been talk of deprecating the numarray and numeric > compatibility parts of numpy for the upcoming 2.0 release I thought maybe we > could consider a few other changes. First, numpy imports a ton of stuff by > default and this is maintaine

Re: [Numpy-discussion] numpy 2.0, what else to do?

Charles R Harris wrote: > numpy imports a ton > of stuff by default and this is maintained for backward compatibility. > Would this be a reasonable time to change that and require explicit > imports for things like fft? absolutely! I'd love far more minimalist imports. This is particularly an

[Numpy-discussion] numpy 2.0, what else to do?

Hi All, Since there has been talk of deprecating the numarray and numeric compatibility parts of numpy for the upcoming 2.0 release I thought maybe we could consider a few other changes. First, numpy imports a ton of stuff by default and this is maintained for backward compatibility. Would this be