Update cc API usage #373
Merged
Update cc API usage #373
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
ghost
added
the
|
I'm guessing the tests fail because of the cc version that's not created, hence not on pip |
|
can you also have a look at |
right, they'll pass once cc was updated on pipy and this branch's cc version is bumped
sure! |
added 2 commits
June 10, 2016 16:23
|
otherwise 👍 |
|
if @r-marques approves, then you can merge |
|
👍 |
sbellem
pushed a commit
to sbellem/bigchaindb
that referenced
this pull request
Oct 24, 2016
…ation Update cc API usage
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.
This is the fix related to: bigchaindb/cryptoconditions#15
We can merge as soon as cc was pushed to pipy.