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

Support Jupyter Notebooks Natively in Che via Python Plugin #16723

Open
murphye opened this issue Apr 23, 2020 · 6 comments
Open

Support Jupyter Notebooks Natively in Che via Python Plugin #16723

murphye opened this issue Apr 23, 2020 · 6 comments
Labels
area/plugin-registry kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@murphye
Copy link

murphye commented Apr 23, 2020

Is your enhancement related to a problem? Please describe.

I cannot use Jupyter Notebooks inside of Che. It's possible with VS Code.

I have experimented with the Python plugin for Che, and it does not offer the same features as the Python plugin in VS Code.

Describe the solution you'd like

The Microsoft VS Code plugin for Python provides out of the box, native support for Jupyter, including starting and connecting to a Jupyter server:
https://code.visualstudio.com/docs/python/jupyter-support

You can view and use IPython notebooks directly in VS Code.

Describe alternatives you've considered

Jupyter web interface, but doesn't integrate with Che.

Additional context

Using Jupyter from Che would be a powerful alternative to Jupyter web interface.

@murphye murphye added the kind/enhancement A feature request - must adhere to the feature request template. label Apr 23, 2020
@murphye murphye changed the title Fully Support Jupyter Notebooks in Che via Python Plugin Support Jupyter Notebooks Natively in Che via Python Plugin Apr 23, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Apr 23, 2020
@JPinkney
Copy link
Contributor

We actually use the VSCode Python Plugin but perhaps the version is too old and needs to be updated: https://github.com/eclipse/che-plugin-registry/blob/master/v3/plugins/ms-python/python/2019.5.18875/meta.yaml#L20 to get all of the features

@rhopp rhopp added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Apr 23, 2020
@ericwill
Copy link
Contributor

We actually use the VSCode Python Plugin but perhaps the version is too old and needs to be updated

Yup: #16183

@murphye
Copy link
Author

murphye commented Apr 23, 2020

Can you test Jupyter support when completing that issue? Also this issue may be relevant to test:
#16730

Jupyter needs to be installed into the Python environment to work.

@ericwill
Copy link
Contributor

Can you test Jupyter support when completing that issue? Also this issue may be relevant to test:
#16730

Jupyter needs to be installed into the Python environment to work.

Yes we will, thanks for the feedback.

@murphye
Copy link
Author

murphye commented Aug 28, 2020

Any update on this issue? Was in a Sprint a while back...

@che-bot
Copy link
Contributor

che-bot commented Feb 24, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 24, 2021
@ericwill ericwill added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugin-registry kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants