This repository was archived by the owner on May 23, 2023. It is now read-only.
Add Vyper as a test option as well. #854
Merged
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
https://github.com/ethereum/vyper was renamed from 'Viper' to 'Vyper'. We are in the process of doing the full renaming of the vyper module as well.
Just patching the tester like so - will for the interim allow both viper & vyper support - if someone is using an older checkout from master. Alternatively I can also create the full patch for 'vyper' in the other parts of of the develop branch - and once viper is fully renamed it just merges.
Let me know what's easiest ;)