Minor tweaks to badges and tracking master instructions #118
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
|
Thanks! |
stevengj
added a commit
that referenced
this pull request
Mar 4, 2015
Minor tweaks to badges and tracking master instructions
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.
I thought since PackageEvaluator is working nicely with PyCall, it'd be nice to show PyCall is working great on release.
My next PkgEval project is to start testing the various packages that depend on PyCall, which are mostly excluded right now.
I've also thrown in a tweak to the REQUIRE - PyCall is defacto 0.3 only anyway due to Dates, thought it was better to be explicit.