-
Notifications
You must be signed in to change notification settings - Fork 673
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
Deprecate encore in favour of mdaencore #4274
Comments
Are we going to remove the code and replace with mdaencore until 3.0 (as we did for hole2, psa, etc)? |
Probably? I think we're still missing a set of wheels that are fully compatible with the current status of MDA though, might need to get that done first. |
Deprecation should be added for 2.8.0, given that we keep sending people over to mdaencore when they open issues here. |
(Even if we don't replace it with the kit.) |
I think we're just missing the CF migration, I'll add it to my to-do list for later in the month. |
I started working on this assuming we can go the replace code with the mdakit route, but checking first @IAlibay were you able to the CF stuff? (otherwise I can just stick to adding deprecation messages for now) |
Following some discussion, given that mdaencore is a bit more complicated and that it would be nice to get something in before the upcoming 2.8.0 release, I'll go with adding warnings for now. |
The encore code has been turned into a separate mdakit. We should deprecate it from core with the aim of removing in 3.0.
The text was updated successfully, but these errors were encountered: