fix: remove upper pin on vyper dependency #115
Closed
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
|
After some discussion, going to look into actually ensuring we can flatten on 0.4...
|
I haven't looked at the vyper changelog or anything, but my primary concern is vyper modules. Right now imports are just treated as interfaces and transpiled accordingly. Which is probably not what we want for modules. But most of what I'm saying is guesswork. Needs investigation. |
antazoey
commented
Jun 13, 2024
|
closing in favor of #118 |
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.
What I did
trying to assist in envs where vyper is installed in 0.4
fixes: #114
fixes APE-1762
How I did it
How to verify it
Checklist