Closed stualden closed 3 years ago
Try updating panel to the latest version with this command conda install panel=0.11 -c pyviz
Thank you! That eliminated the error message. Then to get hvplot to actually work, I needed to create fresh notebooks - any existing notebook that had been run with the old panel was "tainted" (it appears to be this bug).
Just one more question (and then I'll get back to work!) - is it best to use the pyviz channel for anything hvplot related, overriding conda defaults where needed? (For example, in this case, a conda update --all would just move me back to panel 0.10.3.) Thanks again.
Good to hear that it worked.
I use the pyviz channel for all the pyviz packages , e.g. panel
, holoviews
, etc. I have the following setup for my .condarc
file.
ssl_verify: true
channels:
- pyviz
- conda-forge
- defaults
Thank you, I will try that channel priority.
Should I re-report the IPKernelApp No such comm: hv-extension-comm
bug? Looks like that ticket was closed back in April 2019, but the bug appears to still be there (I just triggered it a different way, that's all).
Yes, that's the channel priority I'd use; pyviz is always either equal to or more up to date than conda-forge or defaults.
The "No such comm" warnings are meaningless but very irritating. I've offered $500 USD to anyone who can safely eliminate them, but so far no takers.
Once I'm up to speed on all this, I may just take on your offer :-)
It's not so much the warning that bothers me, it's the accompanying fact that after a notebook has experienced an error like the one I described above, calls to hvplot
don't generate any output in the notebook (and instead just generate those annoying warnings in the console).
Restarting the kernel or reloading the notebook doesn't fix it, even with (in my case) an updated panel
. You have to copy your code to a brand new notebook and run that. That's the bug (at least it seems like a bug) I'd like to report, but I guess I'm not sure where to report it.
@stualden I suspect that's weird incompatible versions sticking around. The procedure to fix that is usually:
I'm still working out an approach that would resolve this properly.
And in any case the "No such comm" messages are generally unrelated to the actual problem; people see them whenever they are experiencing a problem and thus think they are relevant, but they also occur when there is no problem, so they are really just a distraction!
Thank you everyone - I'm grateful for your help, and once again a happy hvplot user.
Complete, minimal, self-contained example code that reproduces the issue
Problem description
When I try the import, I get the following response in a Jupyter Notebook on Chrome or Edge:
With Internet Explorer, I get the following (both messages):
After that, any calls to hvplot produce no output.
Console output
ALL software version info
channels:
dependencies:
Thank you! If this is a bokeh issue rather than an hvplot issue, please advise.