-
Notifications
You must be signed in to change notification settings - Fork 225
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
Add model version separate from package version #448
Conversation
This was already too low - previously was 3.3.1. With update of doubleclick we now need to require 3.4
An alternative approach that would make things simpler going forward would be to declare the current state as being model version |
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.
Thanks a lot for doing this!
ipympl/_version.py
Outdated
# These should not be changed unless we introduce changes to communication between | ||
# frontend and backend. | ||
__TOOLBAR_MODEL_VERSION__ = "^0.10.5" | ||
__CANVAS_MODEL_VERSION__ = "^0.10.5" |
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.
It might be easier to track if we have one same version for all models?
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 that's probably a good call. One isn't really functional without the other so no need to have them separate.
README.md
Outdated
@@ -64,6 +64,7 @@ Versions lookup table: | |||
|
|||
| `ipympl` | `jupyter-matplotlib` | `JupyterLab` | `Matplotlib` | | |||
|----------|----------------------|--------------|--------------| | |||
| 0.8.9 | 0.10.x | 3 or 2 | 3.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.
I would prefer if we do version bumps separately, if you don't mind
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.
👍
package.json
Outdated
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "jupyter-matplotlib", | |||
"version": "0.10.5", | |||
"version": "0.10.6", |
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.
Same comment here for the version bump
Concerning the version bump, what I did until now was to push release commits to master (see this for example), that keeps the release commit clean in the history and far from any merge commit. |
|
any idea what's causing this new error?
|
@@ -32,6 +32,6 @@ function activateWidgetExtension( | |||
registry.registerWidget({ | |||
name: MODULE_NAME, | |||
version: MODULE_VERSION, | |||
exports: () => import('./index'), | |||
exports: (): any => import('./index'), |
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.
this gets rid of the typescript error, but is probably not the best way to do that.
Thank goodness for those galata tests. they catch that this actually does break things :/ |
ipympl/_version.py
Outdated
# how to speak. See counterpart in the src/version.ts file. | ||
# These should not be changed unless we introduce changes to communication between | ||
# frontend and backend. | ||
__MODEL_VERSION__ = "^1.0.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.
in ipywidgets there is no ^
maybe we should remove also?
I don't have any strong opinion on declaring the current state as being model version |
I actually believe this could go smoothly for users. They will hopefully just see a version bump on ipympl and jupyter-matplotlib, as for any release. Then it will hopefully be easier for them to update one without the other from now on :) |
to allow compatibility between patch releases.
@@ -12,8 +12,8 @@ export class ToolbarModel extends DOMWidgetModel { | |||
_view_name: 'ToolbarView', | |||
_model_module: 'jupyter-matplotlib', | |||
_view_module: 'jupyter-matplotlib', | |||
_model_module_version: '^' + MODULE_VERSION, | |||
_view_module_version: '^' + MODULE_VERSION, | |||
_model_module_version: MODEL_VERSION, |
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.
I'm not sure having the ^
does anything - and ipywidgets doesn't do this, so I removed it to be more similar to ipywidgets.
I think this is ready now (supposing tests pass) |
Hopefully fixes #416
Adds a model version version that is not tied to the npm release version so that we can (hopefully) have compatibility across patch versions.
Bumps the version for release of the double click fixes