-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Updated to 5.0.0 #3
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
Before merging this, it would be helpful to get some oversight from the @jdfreder. Is there an additional dependency which we should be pulling in (e.g. was the JS pulled out of this package and into widgetsnbextension). |
@pelson yeah, part of the Javascript was published to npm. The widgetsnbextension package installs that part and adds to it. The built (combined) static assets are a resource of the widgetsnbextension package (you can see this is the contents uploaded to pypi). Installing ipywidgets should automatically install widgetsnbextension. In order for the widgets to work in the notebook (only compatible with the newly released 4.2), |
So, let me try to reduce this. Please correct me if I'm wrong.
|
Yes to 1 and 3, no to 2. |
Hmm...I thought that |
FWIW, AppVeyor already passed, but the status didn't update for some reason. |
widgetsnbextension is new to ipywidgets 5.0. It is a dependency of ipywidgets, maybe that's what you mean by included. |
We need a new conda-forge feedstock called widgetsnbextension, and to add that as a dependency here AFAICT. It would also be nice if we had a test in this feedstock which failed without that dependency. |
I have a PR almost ready for that. I was just waiting for the CircleCI issues to be resolved. I am sending it soon. |
Feel free to send it when you are ready. I don't know what timescale these CircleCI API issues will be resolved. If we need it really badly, we can just restart Travis loads of times until it works. Not optimal, but that is sort of the situation until CircleCI gets back to us. |
NVM guess you just did. |
This needs to be re-rendered with |
There is now a feedstock for widgetsnbextension and packages have been released for all OSes, Python versions, and architectures. |
|
||
test: | ||
imports: | ||
- ipywidgets | ||
|
||
about: | ||
home: http://github.com/jakevdp/ipywidgets |
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.
😆 - how did that happen! 😄
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.
Well, he did have something like that once. ( http://github.com/jakevdp/ipywidgets-static )
ipywidgets is now at version 5.1.2 to fix some bugs an API incompatibilities. And widgetsnbextension is at 1.2.1. Does it make sense to go to 5.0.0 first and then bump again or just update this PR? |
Nice to see you over here, @parente. At this point, I'm thinking conda-forge is the only way to keep up with Jupyter's rapid releases in any realistic way. I wonder if it would be worthwhile to start adding conda-forge as a channel in the docker images so that we can ensure we are getting the newest packages available. Sure, that's fine. Right now I think we are waiting for some feedback from, @jdfreder. There was some concern that |
@minrk added it yesterday to docker-stacks and @willingc merged. I don't think a build was kicked off though.
Understood. Just a friendly FYI on the versions. |
I would just update the PR. Oh wait! I am the author of the PR 😳 Let me get to it... |
Awesome! Sorry, I may have missed it. My notifications are literally swamped with stuff from here. Still trying to figure out how best to handle that better.
Sure and we appreciate the FYI. |
We will probably make minor bug-fix releases of ipywidgets and IMO there are only benefits to updating the PR. @minrk https://github.com/minrk added it yesterday to docker-stacks and Awesome! Sorry, I may have missed it. My notifications are literally swamped with Understood. Just a friendly FYI on the versions. Sure and we appreciate the FYI. — |
Done! Welcome to conda-forge!! |
@@ -59,10 +59,15 @@ install: | |||
- cmd: set PATH=%CONDA_INSTALL_LOCN%;%CONDA_INSTALL_LOCN%\scripts;%PATH% | |||
- cmd: set PYTHONUNBUFFERED=1 | |||
|
|||
- cmd: conda config --set show_channel_urls true | |||
- cmd: conda install -c http://conda.binstar.org/pelson/channel/development --yes --quiet obvious-ci | |||
- cmd: conda config --add channels http://conda.binstar.org/conda-forge | |||
- cmd: conda info | |||
- cmd: conda install -n root --quiet --yes conda-build anaconda-client jinja2 setuptools |
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 pin the version of conda-build, as in .travis.yml
?
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, I see the line below!
@jakirkham what are you looking for in particular? I reviewed and didn't see anything out of place, other than my failure to read re: pinning Raised a question over here about the installation procedure for the user: |
@ocefpaf said:
I'm not an ipywidgets expert by any means, so I think you're better off keeping me on the list of people who send PRs instead of people with the ability to merge and break master. 🙈 |
If you ( @parente ) are interested in helping maintain the docker image though, we would be more than happy to have you on board there. Though it is substantially simpler than the ones at docker-stacks. Mainly this determines how builds are done on the Linux side of things here. |
@parente is totally an ipywidgets expert. |
Ah so he's being humble here. 😉 |
Well @bollwyvl, I remember you had mentioned spending a fair bit of time trying to get these to install properly and I wanted to make sure that the installation we are doing here and with |
@@ -1,17 +1,17 @@ | |||
{% set version = "4.1.1" %} | |||
{% set version = "5.1.2" %} |
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.
Can you point to 5.1.3, I just made a patch release?
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.
Done! Thanks @SylvainCorlay!
This looks good to me. Should we get this in? |
Yeah, that's the rub! On many of our extensions, I am using the somewhat-creaky PhantomJS/CasperJS test stuff that the 4.x notebook uses. It looks like widgets is now on the karma side of things, which I haven't been able to use, as anaconda.org doesn't have native browsers (coming soon, I'm promised)... and if using phantom (even 2.x), would inherit all the same old nasty problems. But it does seem the way of justice. Assuming we don't have browsers, I guess the best one could do would be to see if the extensions actually installed correctly (i.e. check the output of
At the Jupyter Dev meeting, we talked about extracting the good bits of jupyter-js-notebook's tests into something that a developer could use at test time to easily employ best practices for testing extension-related functionality in as close to a representative environment as possible. Since this will inevitably use node stuff, conda is a great target, as you can now just pull It should be possible for a dev to specify:
|
|
||
test: | ||
imports: | ||
- ipywidgets | ||
|
||
about: | ||
home: http://github.com/jakevdp/ipywidgets | ||
home: https://github.com/ipython/ipywidgets | ||
license: BSD 3-clause | ||
summary: IPython Static Widgets |
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.
Should this rather be Jupyter interactive widgets
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.
The GitHub pages has: IPython widgets for the Jupyter Notebook
I am changing here to Widgets for the Jupyter Notebook
, sounds good?
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.
As long as they aren't "static" and it's referring to "Jupyter", I'm happy. @SylvainCorlay comments?
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.
The front-end is now kernel-language agnostic and we are working hard to make it work outside of the notebook....
I am 👍 on merging this and iterating from there... |
(I will depend on this for the recipes on ipyleaflet, bqplot, pythreejs...) |
I see @bollwyvl. Thanks for the useful feedback. Can we maybe add an issue wrt to testing and we will table it for now? If people are happy with this as is, I'm eager to see it go in ASAP. |
There was a failure downloading miniconda in one of the Travis CI builds. As this is unrelated to the content here, I went ahead and restarted it. |
Merge? |
Agreed. |
Thanks everyone. If we have new issues, let's iterate. Sound good? |
This is an excellent suggestion, I'd love to see this in the recipe! Great to have you guys on board with this recipe - welcome! There are details here that only somebody in the thick of development can know so it is awesome to be able to pull on that knowledge to package ipywidgets (& friends) to give conda users the best possible experience. |
Changed from PyPI to GitHub and using
sha256
instead ofmd5
.