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

native-notebooks-update #4692

Merged
merged 1 commit into from
Jul 22, 2021
Merged

native-notebooks-update #4692

merged 1 commit into from
Jul 22, 2021

Conversation

claudiaregio
Copy link
Contributor

No description provided.

@@ -21,53 +21,51 @@ MetaSocialImage: images/tutorial/social.png

## Setting up your environment

To work with Jupyter notebooks, you must activate an Anaconda environment in VS Code, or another Python environment in which you've installed the [Jupyter package](https://pypi.org/project/jupyter/). To select an environment, use the **Python: Select Interpreter** command from the Command Palette (`kb(workbench.action.showCommands)`).
To work with Python in Jupyter notebooks, you must activate an Anaconda environment in VS Code, or another Python environment in which you've installed the [Jupyter package](https://pypi.org/project/jupyter/). To select an environment, use the **Python: Select Interpreter** command from the Command Palette (`kb(workbench.action.showCommands)`).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you actually need the Jupyter package? I thought ipykernel was sufficient?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Depends. We need jupyter if the user is on a Mac M1 or an ubuntu machine that ZMQ binaries aren't available for.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm would it be worth it to add a note for Ubuntu and Mac M1 users? Or maybe we can detect which system they're on and show install Jupyter package depending on what machine they're on? @gregvanl is that possible?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would have to be pretty sophisticated. Mac M1 only. Mac older processors work fine. Ubuntu with specific glib libraries missing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah okay so it's just simpler to have everyone install the Jupyter package

Copy link
Contributor

@DonJayamanne DonJayamanne Jul 21, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm would it be worth it to add a note for Ubuntu and Mac M1 users? Or maybe we can detect which system

I think we should just build the zmq binaries instead of documenting work arounds.
For instance we know what OS & linux distros VS Code supporst, so why not setup a CI to build zmq binaries for those particular OS/linux distros, its basically a one time job.
Here's the issue, microsoft/vscode-jupyter#5206

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah okay so it's just simpler to have everyone install the Jupyter package

I'd say its much simpler for us to build zmq & ship that, than having to deal with the issues users have when installing Jupyter & other packages (confusions around which interpreter/where it is installed, issues with users running pip install in conda environments , etc).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the easiest thing for the docs to say now is that you install jupyter. Instead of having complicated logic for how the user determines what to install. We can change the docs when we fix the implementation problem.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can change the docs when we fix the implementation problem.

Oh yes, I agree

@gregvanl gregvanl self-assigned this Jul 21, 2021
@gregvanl gregvanl merged commit fee4702 into main Jul 22, 2021
@claudiaregio claudiaregio deleted the clregio/native-update branch July 26, 2021 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants