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

Update version of notebook package #7

Merged
merged 1 commit into from
Apr 8, 2022
Merged

Update version of notebook package #7

merged 1 commit into from
Apr 8, 2022

Conversation

yuvipanda
Copy link
Member

@github-actions
Copy link

github-actions bot commented Apr 8, 2022

Binder 👈 Test this PR on Binder

Copy link
Member

@choldgraf choldgraf left a comment

Choose a reason for hiding this comment

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

This looks good to me!

Though I am confused why we aren't installing the "latest" version of the Jupyter Notebook with this environment.yml file anyway. Here is my thinking:

  • If no dependency pins the notebook package, I assume that conda would install the latest released version. In which case specifying this shouldn't make a difference.
  • If a dependency does pin the notebook package, then us setting a minimum should create a version conflict, right?

@yuvipanda
Copy link
Member Author

@choldgraf repo2docker was pinning notebook to 6.3.0 for python 3.6 compatibility reasons. Just opened jupyterhub/repo2docker#1149 to fix it

@yuvipanda yuvipanda merged commit c4e586f into main Apr 8, 2022
@damianavila damianavila deleted the yuvipanda-patch-1 branch April 11, 2022 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants