My $0.02 on the NumPy 2.0 schedule:
NumPy 2.0 is for ABI-incompatible changes like datetime support, and .NET support. It would be ideal, if at the same time we could future-proof the ABI some-what so that future changes can be made in an ABI-compatible way. I also think it would be a good idea to incorporate Mark's small-array improvements into the C-structure of NumPy arrays. If Mark has time to work on this, I have some hope we can get there.
I have been wanting to propose a "generator array" for some time now, but have not had time to write it up. I have the outline of a design that overlaps but I think generalizes Mark's deferred arrays. Mark's deferred arrays would be a particular realization of the generator array, but other realizations are possible as well.
There is much that has to be fleshed out for it to really work, and I think it will have to be in NumPy 2.0 because it will create ABI changes. I don't have the time to personally implement the design. If there are others out there that have the time, I would love to talk with them about it. However, I don't want to distract from this scheduling thread to discuss the ideas (I will post something else for that).
The reason for a NumPy 1.6 suggestion, is that Mark (and others it would seem) have additional work and features that do not need to wait for the NumPy 2.0 ABI design to finalize in order to get out there.
If someone is willing to manage the release of NumPy 1.6, then it sounds like a great idea to me.
-Travis
Basically the reason for
On Jan 27, 2011, at 11:56 AM, Mark Wiebe wrote:
On Thu, Jan 27, 2011 at 9:36 AM, Charles R Harris
<charlesr.harris@gmail.com> wrote:
All tests pass for me now, maybe it's a good time to merge the branch into the trunk so we can run it on the buildbot?
Might be better to merge your unadulterated stuff into master, make a 1.6 branch, and add the compatibility fixes in the branch. You can test branches on the buildbot I think, at least that worked for svn, I haven't tried it with github.
I'm inclined to put the ABI fixes in trunk as well for the time being. The two changes of note, moving the 'cast' array to the end of PyArray_ArrFuncs and making 'flags' in PyArray_Descr bigger, can be reapplied if the 2.0 refactor ends up needing them. I think for 2.0, more extensive future-proofing will be desirable anyway, so trunk may as well be ABI compatible until it's clear what changes are necessary.
-Mark
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
---
Travis Oliphant
Enthought, Inc.
1-512-536-1057