MAINT: remove binder launches #191
Closed
+0
−14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bsipocz
force-pushed
the
MAINT_remove_binder
branch
from
6d92958 to
c13d245
Compare
bsipocz
force-pushed
the
MAINT_remove_binder
branch
from
c13d245 to
475b9bb
Compare
bsipocz
added
the
infrastructure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Binder feels to be unreliable these days, none of us could launch it during the latest Python WG meeting, so I opened this PR for its removal. However in recent days I had good experience of actually launching it. So if we decide to keep it around for e.g. async learn, #193 provides a fix for launching markdowns as notebooks.
Merge either this one or #193
(closes #193)