-
Notifications
You must be signed in to change notification settings - Fork 112
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
Deprecate the wrappers of the array iterator API. #280
Conversation
452e6a9
to
7dc83be
Compare
I also noticed that the implementations of |
7dc83be
to
2e1ec9a
Compare
With apologies just saying that I've seen this and the other PRs but haven't had enough time to dedicate a read of these and form any opinion. Might be able to do so tomorrow evening, depending on how long you want to delay the 0.16 numpy release. |
Please take your time. I think delaying the release until you or @kngwyu had time to look into the two PR related to the I think I should merge the already prepared #259 after you make the 0.16 release of PyO3, so people can upgrade using a Git dependency against our |
2e1ec9a
to
8caea5d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 I think the rationale here makes a lot of sense, let's proceed with this.
One thing I'm unsure on, does using ndarray
iteration require unsafe? (At least until #274 or similar.) It might be nice to have an example to point users at so that they know what to replace the deprecated code with.
Only under the same circumstances that the |
8caea5d
to
3363c8b
Compare
…erator the NumPy iterator wrappers.
3363c8b
to
b3be43a
Compare
Follow-up to #279, deprecating the
npyiter
module with a short explanation of why ndarray's facilities are preferable.