Assuming #504 is true and a major release is needed, deprecation warnings are needed. I think Material.material_components should raise a DeprecationWarning pointing to #504 with release 0.4.1.
Also I think with the next major release a lot of the DeprecationWarnings from Montepy 0.2.0 can be removed now. Just as: montepy.data_cards. I think at least the ones that are raised as an Error because changing a DeprecationWarning for an AttributeError won't be too bad.
I'm not sure if these new Deprecations should occur before or after a migration plan is in place. The migration plan would need to have the new interface pretty well pinned down, so I'm hesitant to wait. Maybe we could at least make a landing page in the documentation that we can explain the issues, and possible migration, alpha testing etc.
Assuming #504 is true and a major release is needed, deprecation warnings are needed. I think
Material.material_components
should raise aDeprecationWarning
pointing to #504 with release 0.4.1.Also I think with the next major release a lot of the DeprecationWarnings from Montepy 0.2.0 can be removed now. Just as:
montepy.data_cards
. I think at least the ones that are raised as an Error because changing aDeprecationWarning
for anAttributeError
won't be too bad.I'm not sure if these new Deprecations should occur before or after a migration plan is in place. The migration plan would need to have the new interface pretty well pinned down, so I'm hesitant to wait. Maybe we could at least make a landing page in the documentation that we can explain the issues, and possible migration, alpha testing etc.