Fix bug preventing local install of vyper package from working.
How I did it
Two things had to be done:
Checks to make sure we don't attempt to download the package if we detect we are using the version we have in our site-packages. (detected using the pragma spec).
Specify the path to the binary. This is needed so we can still use the vvm method.
How to verify it
Two cases needed for testing (that I have tried myself too):
Case 1:
Install vyper from source (either a local clone or via git)
Compile a contract using the next bumped version. Right now, the latest tag on vyper is 0.3.1, so set your pragma to 0.3.2. It should work now!
Case 2 (regression test):
Make sure you do not have vyper installed locally.
Specify a pragma from a released tag, such as 0.3.1.
Notice you can compile
Checklist
[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)
What I did
Fix bug preventing local install of
vyperpackage from working.How I did it
Two things had to be done:
vvmmethod.How to verify it
Two cases needed for testing (that I have tried myself too):
Case 1:
vyperfrom source (either a local clone or viagit)vyperis0.3.1, so set your pragma to0.3.2. It should work now!Case 2 (regression test):
0.3.1.Checklist