This release is a pre-release and may not be stable for production use.
Getting Started
See Installing Vyper to install vyper. See Tools and Resources for an additional list of framework and tools with vyper support. See Documentation for the documentation and overall design goals of the Vyper language.
See learn.vyperlang.org for learning Vyper by building a Pokémon game. See try.vyperlang.org to use Vyper in a hosted jupyter environment!
Note: Vyper is beta software, use with care
Installation
See the Vyper documentation for build instructions.
Compiling a contract
To compile a contract, use:
vyper your_file_name.vy
generate bytecode
vyper -f bytecode file-name.vy > file-name.bin
generate abi
vyper -f abi file-name.vy > file-name.abi
There is also an online compiler available you can use to experiment with
the language and compile to bytecode and/or IR.
Note: While the vyper version of the online compiler is updated on a regular basis it might be a bit behind the latest version found in the master branch of this repository.
Testing (using pytest)
(Complete installation steps first.)
make dev-init
python setup.py test
Developing (working on the compiler)
A useful script to have in your PATH is something like the following:
$ cat ~/.local/bin/vyc
#!/usr/bin/env bash
PYTHONPATH=. python vyper/cli/vyper_compile.py "$@"
To run a python performance profile (to find compiler perf hotspots):
PYTHONPATH=. python -m cProfile -s tottime vyper/cli/vyper_compile.py "$@"
To get a call graph from a python profile, https://stackoverflow.com/a/23164271/ is helpful.
Contributing
- See Issues tab, and feel free to submit your own issues
- Add PRs if you discover a solution to an existing issue
- For further discussions and questions, post in Discussions or talk to us on Discord
- For more information, see Contributing
2 maintainers
Metadata
2 maintainers
Release files for vyper 0.4.1b3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vyper-0.4.1b3.tar.gz | 693.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vyper-0.4.1b3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / vyper-0.4.1b3.tar.gz
| Download URL | vyper-0.4.1b3.tar.gz |
|---|---|
| Size | 693.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe9176b1c1e4bc75938b95c0e319b6015059fd62dbc19bbb0351cf1d2a18876c
|
|
BLAKE2b-256 checksum How to use checksums |
3b8f26a2341e5f11330b9ffde9d202b51fe434bfe51aae0949c13ce6f46ba4c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 15, 2024.
Transparency logRelease files / vyper-0.4.1b3-py3-none-any.whl
| Download URL | vyper-0.4.1b3-py3-none-any.whl |
|---|---|
| Size | 352.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34610e13a5ed142b0e94c81d3b986d37e709f0a82a204e04a5c257d747c3652e
|
|
BLAKE2b-256 checksum How to use checksums |
a7ce858d2e43ef3d7f1f0655fd345267a15a305b7f17a88a53f0b62a8a6a608d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 15, 2024.
Transparency log
