-
Notifications
You must be signed in to change notification settings - Fork 25
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
remove deprecated models #171
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #171 +/- ##
==========================================
- Coverage 64.84% 64.81% -0.03%
==========================================
Files 103 102 -1
Lines 5694 5690 -4
==========================================
- Hits 3692 3688 -4
Misses 2002 2002 ☔ View full report in Codecov by Sentry. |
c097728
to
06fa4c3
Compare
|
06fa4c3
to
10a1d98
Compare
It appears Removing this will require updating crds and jwst so leaving this PR as draft. |
10a1d98
to
2e27431
Compare
2e27431
to
ae7a85f
Compare
The current jwst downstream errors I believe will be addressed in: |
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.
Looks good to me - presumably 1.6.1 will be released shortly, and separately from 2.0.0, leading to the two unreleased headers in the changelog?
Thanks for taking a look! Yeah I wasn't quite sure the best way to handle that. The existing changes in the 1.6.1 heading presumably weren't enough to trigger a 2.0.0. I think some options are:
Given the timing of a JWST release (which doesn't require this PR but might require the other changes in 1.6.1) I'm inclined to go for option '1' and hold off on merging this PR (I can convert it to draft if that's easiest). |
7e72a52
to
14d0bb8
Compare
Making this a draft until after the next jwst release. |
5c49b94
to
37649c2
Compare
83bbf67
to
3e78421
Compare
Removed -> use this instead DrizProductModel -> ImageModel DataModel -> JwstDataModel MultiProductModel -> MultiSlitModel MIRIRampModel -> RampModel bump crds minimum version
3e78421
to
2f1b9d1
Compare
This would resolve ticket JP-3585; please ensure this is closed when the PR is merged |
I'd say let's start the 2.0.0 process. We have a milestone started: |
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.
LGTM
@@ -49,7 +49,7 @@ test = [ | |||
"psutil", | |||
"pytest>=4.6.0", | |||
"pytest-doctestplus", | |||
"crds>=11.16.14", | |||
"crds>=11.17.1", |
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.
why the bump in CRDS version?
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.
Thanks for giving this a look.
Earlier version of crds use DataModel
. See:
https://github.com/spacetelescope/crds/releases/tag/11.17.1
and:
spacetelescope/crds#938
As this is removing deprecated features this should technically trigger a 2.0 release. As I believe the removal is only to remove warnings from test suite runs I don't imagine this is urgent. However I don't see any reason not to move to 2.0.
Removed -> use this instead
DrizProductModel -> ImageModel
DataModel -> JwstDataModel
MultiProductModel -> MultiSlitModel
MIRIRampModel -> RampModel
See comment below for cross references to jwst and crds.
jwst: #171 (comment)
crds: #171 (comment)
Dropping these models required updating the minimum crds to 11.17.1:
https://github.com/spacetelescope/crds/releases/tag/11.17.1
Checklist
CHANGES.rst
(either inBug Fixes
orChanges to API
)