-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
New iterator #36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New iterator #36
Conversation
I'd rather not edit the history too much if I can get away with it - I cleaned up the early commits when it was clear the iterator worked well. I could possibly separate out the ufunc conversion and the backwards compatibility changes, but they have to go at the end since they depend on the code for the iterator buffering subsystem. Also, as it is now, pretty much every commit will build and run, whereas if I edit the history there's no way I can spend the time to ensure that holds anymore. |
Well, it was worth a try ;) I still think it worth separating out the backward compatibility part if it isn't too much trouble. |
With this patch, the latest scipy trunk (7087), built against NumPy 1.5.1, passes all tests when run against the numpy trunk. The single failing test, test_imresize, fails because it tests all float types, and the new 'half' type lacks the precision to pass that test.
Now in methods.c each argument gets its own line, so its easier to validate.
This function implements the numpy.empty_like semantics, but supports the new NPY_KEEPORDER enumeration value as well as switching to a different data type.
Merge in ~STEPAN.SINDELAR_ORACLE.COM/numpy-hpy from mq/findarrayprep to labs-hpy-port * commit '50a763b10a3f7541806cf6dc2ae262cfe80e7a54': Migrate function _find_array_prepare to HPy
feat: Add vext_s8
All the NumPy and SciPy tests pass now (with a small scipy patch) on my machine. I think there's no a way to get the buildbot to pull from my branch without changing its configuration, so maybe merging the branch now is a good idea.