Remove deprecated stuff for v3.0
See original GitHub issueThis is a follow-up of
- #5761 – Completely remove the deprecated “clobber” keyword for v3, as discussed. Users must switch to “overwrite” keyword now.
- #6191 – Completely remove
analytic_functions
sub-package. Users must switch to modeling for blackbody. - #6200 – Completely remove
GaussianAbsorption1D
model. Users can construct such a thing by subtractingGaussian1D
from desired continuum model (e.g.,Const1D
).
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Python 3.12.0 is to remove long-deprecated items
It seems to me that if the Python community continues in this direction, nothing will work more than 3 months after it's last...
Read more >Remove deprecated `Message` method · Issue #8883 ...
Removed the method from the codebase. Added a changelog entry for 3.0 saying we've removed the previously deprecated method. All reactions.
Read more >[META] Remove deprecated classes, methods, procedural ...
This plan issue is to deal with all the rest of the deprecated code to be removed that are outside of deprecated modules:...
Read more >How long to wait before deleting a deprecated method? [closed]
Major version releases are a good time to remove deprecated methods. Minor releases should typically not contain breaking changes.
Read more >Will deprecated items in Java be removed - Stack Overflow
Quite frankly, what the Java team usually do, is to deprecate the method and remove its implementation to the suggested method instead.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@bsipocz , looks like @astrofrog added the milestone (thanks, Tom!).
Also, I added “Last-before-release” tags here and in #5773. Is that correct?
@pllim @eteq - What about creating the 3.0 milestone now? There are already a few issues out there that will be relevant for that only, and I think it would be very helpful to milestone the asap to lower the chance of getting lost in the noise of open issues.