-
Notifications
You must be signed in to change notification settings - Fork 121
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
nbextensions_configurator validating problems found #37
Comments
Your analysis is pretty much spot-on, I think.
This approach arose because i wanted to simplify the installation process, and ensure that it would never be possible to be missing the JavaScript but have the python for the serverextension, or vice versa. However, again as you pointed out, it brings with it its own problem of spurious validation warnings, which are confusing for end-users.
No, there are no obvious optimizations to the approach, other than reinforcing the link between the js & python sides, as i mentioned. It's not a recommended approach. I would not do this if starting again from scratch, but have stuck with it for now to avoid the pain of issues switching to the standard approach. I think your best course of action depends on use-case. If your serverextension is rendering its own page, then you can add your own handler for js, or just embed it into the page. If on the other hand you have a js extension to an existing notebook page, which will make calls to your serverextension at another URL, then you should use the existing nbextension installation and activation methods. However, to simplify things for the user, you can create a jupyter subcommand to simplify the process with a wrapper script, as seen for example at jupyter_contrib_nbextensions/install.py and jupyter_contrib_nbextensions/application.py. So then, you can simplify to something like
Does that make sense? |
many thanks for your patient and practical advice! @jcb91 thanks. |
you're welcome! 😄 |
For my Centos 6.5 system, I also suffer this problems:
|
@chrinide it appears that you've used |
Hello, I am getting the same validation issue when I am working with Google Datalab notebook. In my case, I am not able to see the extension viz. It is google code that works find on colab notebook. My code is the following: ` !jupyter nbextension list !jupyter nbextension install --py --symlink tensorflow_model_analysis --sys-prefix /usr/local/envs/py2env/lib/python2.7/site-packages/h5py/init.py:36: FutureWarning: Conversion of the second argument of issubdtype from
!jupyter nbextension list !jupyter nbextension enable tensorflow_model_analysis --py --sys-prefix /usr/local/envs/py2env/lib/python2.7/site-packages/h5py/init.py:36: FutureWarning: Conversion of the second argument of issubdtype from !jupyter nbextension list Known nbextensions: Show data sliced along feature column trip_start_hour.tfma.view.render_slicing_metrics(tfma_result_1, slicing_column='trip_start_hour') U2xpY2luZ01ldHJpY3NWaWV3ZXIoY29uZmlnPXsnd2VpZ2h0ZWRFeGFtcGxlc0NvbHVtbic6ICdwb3N0X2V4cG9ydF9tZXRyaWNzL2V4YW1wbGVfY291bnQnfSwgZGF0YT1beydtZXRyaWNzJzrigKY= ` What looks wrong to you? do you have any recommendation how to fix that. thanks for any advice, |
@OrielResearchCure: If you still have problems, please try to install the extensions you are using without installing the nbextensions_configurator. If this works well, install the configurator afterwards. If you know run into problems, please open a new issue on this. |
when executing
jupyter nbextension list
, some problem information occurs:After checking the problem, I found that the nbextension static file are not copied to
<jupyter-data-dir>/nbextensions
, but the server extension directly adds the static path tonbextension
handler, thus it works well. Although it doesn't affect the functionalities, it is still confusing to newcomers.Currently I'm developing an server extension, and also, a js nbextension. A server extension usually need a cooperational js sextension. The installation flow of the extension for a user is
There are too many steps for users to install an extension.
In this repository, it give an approach to patch nbextensions static resource directly to jupyter application.
There's no need to copy resources, enable nbextensions. But, the validating problem will occur by using this approach.
is it recommended to use this approach
are there some optimization for server extensions development
The text was updated successfully, but these errors were encountered: