-
Notifications
You must be signed in to change notification settings - Fork 9
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
Update v1.0.0 - Getting ready for publication #44
Conversation
meld/version.py
Outdated
@@ -1,4 +1,3 @@ | |||
# Copyright (C) 2020 Krishnaswamy Lab, Yale University | |||
|
|||
__version__ = "0.3.2" | |||
|
|||
__version__ = "0.4.0" |
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.
If you're going to change the function APIs, you should either (and preferably both) bump a major version number to indicate breaking changes, or use legacy_api_wrap to accept the legacy arguments (see https://github.com/theislab/scanpy/blob/master/scanpy/external/pp/_magic.py#L19 for an example).
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.
Also any functions with changed names ideally you would created a deprecated function mapping from old to new.
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.
Yeah I was wondering about this. I'd rather have the 0.x block reserved for the prepublication beta software and then just break everything for version 1.0 🤣
No description provided.