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

Pin Python version used on mybinder.org #5

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

betatim
Copy link

@betatim betatim commented Apr 29, 2019

When pinning versions of the packages like you do in requirements.txt it makes sense to also pin the version of Python. This is more an investment in the future, for example when repo2docker (the tool we use to build the repo) switches the default version of Python again.


Switching the default version of Python and the very specific pinning of versions is what caused the build to break this time. (We have an issue or forum post on making a guide of best practices but I can't find it :-/). Min's advice in that post goes something like: for "living" repos pin lightly so you can "go with the flow" and get upgrades. Sometimes things will break but as you are using the repo you can fix it then and then. For "archive" repos pin everything. Package versions, their dependencies, and the version of Python. I will try and find the post/issue and link it here.

@betatim
Copy link
Author

betatim commented Apr 30, 2019

jupyterhub/mybinder.org-user-guide#161 is the issue I was thinking of.

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.

1 participant