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

Drop support for python 3.5 #296

Merged
merged 2 commits into from
Sep 1, 2020

Conversation

blink1073
Copy link
Collaborator

JupyterLab is dropping support for Python 3.5 in 3.0, see also https://numpy.org/neps/nep-0029-deprecation_policy.html

@jasongrout
Copy link
Contributor

JupyterLab is dropping support for Python 3.5 in 3.0

When was this decided?

@jasongrout
Copy link
Contributor

Duh: jupyterlab/jupyterlab#8903

Sometimes I don't know where my head is :)

@blink1073
Copy link
Collaborator Author

😄

@jasongrout
Copy link
Contributor

Oh, I think the reason I didn't push that change down to this level is that Notebook 6 supports python 3.5, and I thought we wanted nbclassic to be a drop-in replacement. So I thought that supporting python 3.5 was deliberate for jupyter_server to make sure people could migrate off notebook.

@Zsailer
Copy link
Member

Zsailer commented Aug 31, 2020

I think since Python 3.5 reaches end-of-life on 9/13, we can ask that people move off in jupyter_server and Notebook at this point. I'm planning to submit a PR to remove Python 3.5 from Notebook too.

@blink1073 blink1073 merged commit 99bfb41 into jupyter-server:master Sep 1, 2020
@blink1073 blink1073 added this to the 1.0 Release milestone Sep 17, 2020
hMED22 pushed a commit to hMED22/jupyter_server that referenced this pull request Jan 23, 2023
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

Successfully merging this pull request may close these issues.

None yet

3 participants