Skip to content
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

Datashader import error. #26

Open
mrazomej opened this issue May 1, 2020 · 2 comments
Open

Datashader import error. #26

mrazomej opened this issue May 1, 2020 · 2 comments

Comments

@mrazomej
Copy link
Contributor

mrazomej commented May 1, 2020

Every time I import the module I always get the following warning:

bebi103-0.0.55-py3.7.egg/bebi103/viz.py:37: UserWarning: DataShader import failed with error 
"cannot import name 'encode_utf8' from 'bokeh.embed.notebook' 
(/Users/mrazomej/anaconda3/lib/python3.7/site-packages/bokeh/embed/notebook.py)".
Features requiring DataShader will not work and you will get exceptions.

The error seems to be in import datashader.bokeh_ext.

When I use corner plots with datashade=True I get the following error:

~/anaconda3/lib/python3.7/site-packages/bebi103-0.0.55-py3.7.egg/bebi103/viz.py in corner(samples, pars, labels, datashade, plot_width, plot_ecdf, cmap, color_by_chain, palette, divergence_color, alpha, single_param_color, bins, show_contours, contour_color, bins_2d, levels, weights, smooth, extend_contour_domain, plot_width_correction, plot_height_correction, xtick_label_orientation)

NameError: name 'datashader' is not defined

Any ideas on why this is happening?

Computational environment:

CPython 3.7.7
IPython 7.13.0

bebi103 0.0.55
bokeh 2.0.1
datashader 0.10.0

compiler   : Clang 4.0.1 (tags/RELEASE_401/final)
system     : Darwin
release    : 18.7.0
machine    : x86_64
processor  : i386
CPU cores  : 8
interpreter: 64bit
@mrazomej
Copy link
Contributor Author

mrazomej commented May 2, 2020

It seems to be an incompatibility issue with bokeh 2.0. Allegedly this has been already fixed as shown in 888. The datashade option will then hopefully work with the next version of datashader.

@justinbois
Copy link
Owner

I think what needs to happen is to update how DataShader is used. This issue should stay open until that is done, since the update to DataShader will also involve a deprecation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants