-
Notifications
You must be signed in to change notification settings - Fork 50
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 to jupyter-packaging v0.10 #145
Conversation
Yes I think so. There used to be a similar one in |
@@ -1,19 +1,23 @@ | |||
include LICENSE | |||
include README.md | |||
include CHANGELOG.md |
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.
We can even combine this line with the one above with *.md
.
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.
Yes, but I wanted to add both separately to know exactly what we need.
Is the RELEASE.md necessary?
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.
Ah right. Then I guess it's fine to leave it like it is now.
It's done, but I would like to create a symlink to the nbconvert folder for gridstack, when running Lines 69 to 97 in 99c1b35
Could we create and script or something and run it with |
setup.py
Outdated
version=pkg_json["version"], | ||
url=pkg_json["homepage"], | ||
author=pkg_json["author"], | ||
description=pkg_json["description"], |
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.
Maybe we still want to keep the metadata for the Python package separate from the JupyterLab extension?
So we don't use this description for the template:
"description": "A JupyterLab extension to create Voila dashboards using GridStack", |
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.
That's right, I'll change. I'll use the setup.cfg
to add the metadata for the python package then.
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.
And we can even move most of this to setup.cfg
, similar to: https://github.com/voila-dashboards/voila/blob/main/setup.cfg
This comment has been minimized.
This comment has been minimized.
I'm setting the version in the |
Sounds good 👍 We'll want to version the Python package and the lab extension separately anyway. Later when we do the releaser PR, we can move the Python version to |
pyproject.toml
Outdated
@@ -1,3 +1,17 @@ | |||
[build-system] | |||
requires = ["jupyter_packaging~=0.7.9", "jupyterlab~=3.0", "setuptools>=40.8.0", "wheel", "jupyter_core"] | |||
build-backend = "setuptools.build_meta" | |||
requires = ["jupyter_packaging~=0.10,<2", "jupyterlab~=3.1", "jupyterlab_widgets~=1.0", "voila>=0.2.0,<0.3.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.
This could also be:
requires = ["jupyter_packaging~=0.10,<2", "jupyterlab~=3.1", "jupyterlab_widgets~=1.0", "voila>=0.2.0,<0.3.0"] | |
requires = ["jupyter_packaging~=0.10,<2", "jupyterlab~=3.1", "jupyterlab_widgets~=1.0", "voila~=0.2.0"] |
Remove useless line Co-authored-by: Jeremy Tuloup <jeremy.tuloup@gmail.com>
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!
This should be good to merge, and we can iterate afterwards as part of #147 |
Thank you so much Jeremy! |
@jtpio Can we simplify the development build?
voila-gridstack/setup.py
Lines 69 to 97 in 99c1b35