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

Include Content that Uses Broken Extensions? #10

Closed
jzf2101 opened this issue Jun 27, 2017 · 4 comments
Closed

Include Content that Uses Broken Extensions? #10

jzf2101 opened this issue Jun 27, 2017 · 4 comments

Comments

@jzf2101
Copy link
Contributor

jzf2101 commented Jun 27, 2017

@jasongrout Since a number of the Lab extensions aren't working eg widgets and geojson, should we bother with including content that relies on those extensions? For example the geojson of the museums in DC

@jzf2101 jzf2101 changed the title Include Content that Uses Broken Extension Include Content that Uses Broken Extensions? Jun 27, 2017
@jasongrout
Copy link
Contributor

I think we should pin the demo to versions that work, but make the demo flexible enough so that that content can be skipped if needed. This means the demo won't be updated as often as JLab (at least right now), but I think that's okay.

Widgets should work with JLab 0.24. I'm not sure about geojson.

@blink1073
Copy link
Member

Geojson is not yet updated. Agreed that ipywidgets and google-drive are the only two known extensions that are compatible with JupyterLab 0.24.

@jzf2101
Copy link
Contributor Author

jzf2101 commented Jun 28, 2017

@jasongrout so should we keep the Geojson, bqplot, dask, and pythreejs content?

@blink1073
Copy link
Member

I'd say keep the content, so that when they become compatible we have the files in place.

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

3 participants