-
Notifications
You must be signed in to change notification settings - Fork 8
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
Support backwards compatibility with mlrose-hiive #7
Comments
- Introduced a new GeomDecay class that inherits from GeometricDecay. - Added a deprecation warning in the GeomDecay class to inform users that it will be removed in a future release. - Updated the GeometricDecay class to include detailed docstrings and type annotations. - Ensured backward compatibility by allowing the use of the old GeomDecay class name with a warning.
Progress towards supporting backward compatibility
|
UpdateI've decided that the classes, methods, properties, and attributes should be renamed back to their original names for the time being. This revision will inherently support backwards compatibility with At this time, only the renamed classes have been documented in the comment above, so we'll start with reverting the class names. The other renamed entities will be more difficult to track down, but they might be just as important as the class names. |
@gitongah want me to leave the last two class names for you to rename, or you want me to do it? |
EXAMPLE COMMENT |
Finished method name check for .decorators.short_name_decorator.py we have different names |
Finished method name check for .gridsearch.grid_search_mixin.py we have different name from the mlrose-hiive |
Finished method name check for .runners._nn_runner_base.py and we have a method that is not on the mlrose-hiive. "dynamic_runner_name" method. |
I'm reasonably satisfied with the level of backwards compatibility at this time, so I'm closing this issue. |
Issue Summary
Refactored code needs to be further revised to ensure backward compatibility with
mlrose-hiive
.The text was updated successfully, but these errors were encountered: