-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Avoid dependence on NdElement and add deprecation warning #1191
Conversation
If you are trying to deprecate |
That is the idea yes, the problem is pickle compatibility which would be a real pain. |
Agreed. For this reason if you do get pickle compatibility working, make sure to add a deprecation warning so that when the time comes, we are less likely to forget to strip out the (inevitably!) horrible pickling hacks. |
c82a1db
to
59924e7
Compare
As outlined in #1146, this PR now stops NdElement being used by default under any circumstances, with an additional deprecation warning issued when it an NdElement is instantiated for an unforeseen reason. In v2.0 NdElements will be removed and I'd even support dropping pickle support. |
Agreed. Version 2.0 is also there to allow us to clean up things like this and make a break with the 1.x series. We should consider backporting fixes from 2.0 into 1.7.x and if we find there is demand for continued 1.0 support, we should consider backporting key features from 2.0 into a 1.8 release (after 2.0). |
Ready to merge. |
The title should still be updated as I think it is now more general than what is suggested. I assume I'm not seeing any |
In discussion we decided that there would be plenty of warnings when working with Merging. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Seemingly straightforward, needs further testing though.
Ended up reviving the NdElement deprecation PR here.