Hi all, I am using numpy.in1d in the merger tree, which is new in numpy 1.4. http://docs.scipy.org/doc/numpy/reference/generated/numpy.in1d.html Do we think that this will be a problem, kinda sorta forcing users to upgrade when we do the next point release? I think as long as we say 'numpy 1.4 required' it's ok. _______________________________________________________ sskory@physics.ucsd.edu o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_\(_)_______________
Hi Stephen,
Feel free to use it, but actually Numpy-1.4 has been causing problems
as it break the ABI. So all of our extension modules will have to be
re-compiled (not a big deal) and we *may* have to re-generate the
Cython extensions -- I believe Cython 0.13.1 has support for changing
struct sizes, but that might only be in pre-release.
So I think we should upgrade people but even as of right now (I've
been following the thread tonight, actually!) it's not clear whether
or not ABI breakage will occur in the final 1.4 release. If it does,
there might be some headaches, but all in all it'll be a good upgrade,
I'm sure.
-Matt
On Tue, Feb 2, 2010 at 8:28 PM, Stephen Skory
Hi all,
I am using numpy.in1d in the merger tree, which is new in numpy 1.4.
http://docs.scipy.org/doc/numpy/reference/generated/numpy.in1d.html
Do we think that this will be a problem, kinda sorta forcing users to upgrade when we do the next point release? I think as long as we say 'numpy 1.4 required' it's ok. _______________________________________________________ sskory@physics.ucsd.edu o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_\(_)_______________
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (2)
-
Matthew Turk
-
Stephen Skory