Skip to content
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

EOS deprecations #360

Merged
merged 2 commits into from
Aug 16, 2024
Merged

EOS deprecations #360

merged 2 commits into from
Aug 16, 2024

Conversation

JostMigenda
Copy link
Member

Working on #356 I noticed that there were a few more SN model classes that had only a single option for the eos argument but where it wasn’t marked as @deprecated. This PR adds deprecation markers to those models; in line with the docstring of the GarchingArchiveModel class (which these four models all inherit from).

For the Fischer_2020 model, which was just added in #347, I’m also moving the eos argument to a metadata field. (No deprecation necessary here, because this was never in a published release.)

Since there’s only a single option for either, those shouldn’t be initialisation parameters.
The model has not yet appeared in a public release, so this doesn’t require a deprecation.
…e value

Was already marked as deprecated in the GarchingArchiveModel docstring, but let’s make it more explicit here.
@sybenzvi sybenzvi merged commit 25aecf2 into main Aug 16, 2024
14 checks passed
@sybenzvi sybenzvi deleted the JostMigenda/EOSDeprecations branch August 16, 2024 04:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants