Skip to content

Transition FutureWarnings older than X versions to Deprecations? #524

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.

Sign up for GitHub

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

Jump to bottom
Closed
effigies opened this issue Mar 29, 2017 · 1 comment · Fixed by #755
Closed

Transition FutureWarnings older than X versions to Deprecations? #524

effigies opened this issue Mar 29, 2017 · 1 comment · Fixed by #755
Milestone
2.5.0

Comments

@effigies
Copy link
Member

Continuing on from the ArrayProxy.header deprecation in #521, it'd probably be good to move FutureWarnings from <=2.0 (2.1?) to DeprecationWarnings, more generally.

Not sure how to use the versioned deprecation machinery to deprecate modules (looking at nibabel.minc).
@effigies
Copy link
Member Author

effigies commented Sep 7, 2017

@matthew-brett Good to transition FutureWarnings to DeprecationWarnings?

Also there are some behavior changes that we've been warning about since v1.1.0:

@effigies effigies mentioned this issue Sep 27, 2017
Merged
28 tasks
@effigies effigies added this to the 2.5.0 milestone Apr 25, 2019
@effigies effigies mentioned this issue Apr 26, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.5.0
Development

Successfully merging a pull request may close this issue.

MAINT: Effect FutureWarnings, including deprecations effigies/nibabel
1 participant
@effigies