Ape Ethereum Framework
Project description
Quick Start
Prerequisite
In the latest release, Ape requires:
- Linux or macOS
- Python 3.7.X or later
Windows:
- Install Windows Subsystem Linux (WSL)
- Choose Ubuntu 20.04 OR Any other Linux Distribution with Python 3.7.X or later
Please make sure you are using Python 3.7.X or later.
Check your python command by entering
python3 --version
Installation
Suggestion: Create a virtual environment using virtualenv or venv.
You may skip this creating a virtual environment if you know you don't require one for your use case.
Create your virtual environment folder
python3 -m venv /path/to/new/environment
source <venv_folder>/bin/activate
You should see (name_of_venv) DESKTOP_NAME:~/path:$.
To deactivate the virtual environment, do:
deactivate
Now that your Python version is later than 3.7.X and you have created a
virtual environment. Let's install Ape! There are 3 ways to install
ape: pip, setuptools, or Docker.
via pip
You can install the latest release via pip:
pip install -U pip
pip install eth-ape
via setuptools
You can clone the repository and use setuptools for the most up-to-date version:
git clone https://github.com/ApeWorX/ape.git
cd ape
python3 setup.py install
via docker
Please visit our Dockerhub for more details on using Ape with Docker.
docker run \
--volume $HOME/.ape:/root/.ape \
--volume $HOME/.vvm:/root/.vvm \
--volume $HOME/.solcx:/root/.solcx \
--volume $PWD:/root/project \
--workdir /root/project \
apeworx/ape compile
Docker Uninstall Process: You will need to remove files generated by docker
sudo rm -rf **\~/.solcx**
sudo rm -rf **\~/.vvm**
Overview
For more in-depth information about the project please look at the projects It explains the purpose of each folder and how to use them effectively.
Use ape init to initialize your ape project folders. Visit userguide project for more information.
ape init
Environment Variables:
Environment Variables are used to help connect you to your files or ecosystems outside of ApeWorX.
Please setup environment variables (where applicable) and follow the latest instructions from the 3rd party:
Example use case:
# Used by the `ape-infura` plugin
export WEB3_INFURA_PROJECT_ID=<YOUR_INFURA_PROJECT_ID>
# Used by the `ape-alchemy` plugin
export WEB3_ALCHEMY_API_KEY=<YOUR_ALCHEMY_KEY>
Visit ape-alchemy
Visit ape-infura
Ape Console
Ape provides an IPython interactive console with useful pre-defined locals to interact with your project. To interact with a deployed contract in a local environment, start by opening the console:
ape console --network :mainnet-fork:hardhat
Visit Ape Console to learn how to use Ape Console.
Quick Usage
Use -h to list all the commands.
ape -h
You can import or generate accounts.
ape accounts import acc0 # Will prompt for a private key
ape accounts generate acc1
List all your accounts with the list command.
ape accounts list
Add any plugins you may need, such as vyper.
ape plugins list -a
ape plugins install vyper
ape plugins list -a
NOTE: If a plugin does not originate from the
ApeWorX GitHub organization, you will get a warning about installing
3rd-class plugins. Any plugin that is not an official plugin has the chance of not being trustworthy. Thus, you should
be mindful about which plugins you install. Additionally, plugins that come bundled with ape in the core installation
cannot be removed and are considered part of the ape core software.
You can interact and compile contracts. Here is an example of a project with a contract you interact with:
git clone https://github.com/brownie-mix/vyper-token-mix.git
cd vyper-token-mix/
You can compile contracts within the contracts/ directory of your project.
The --size option will display you the size of the contract.
ape compile --size
Provide the same arguments to pytest as you would to the ape test command.
ape test -k test_only_one_thing --coverage
Connect an IPython session through your favorite provider.
ape console --network ethereum:mainnet:infura
If you want to run specific files in a scripts/ directory, you can do it using the ape run command.
# This command will run a file named deploy in the scripts/ directory
$ ape run deploy
Logging
To enable debug logging, run your command with the --verbosity flag using DEBUG as the value:
ape run --verbosity DEBUG
You can use ape as a package outside of scripts for the ape run command as well.
You can work with registered networks, providers, and blockchain ecosystems (like Ethereum):
from ape import networks
with networks.ethereum.mainnet.use_provider("infura"):
... # Work with the infura provider here
You can work with test accounts, local accounts, and (WIP) popular hardware wallets:
from ape import accounts
a = accounts[0] # Load by index
a = accounts["example.eth"] # or load by ENS/address
a = accounts.load("alias") # or load by alias
You can also work with contract types:
from ape import project
c = a.deploy(project.MyContract, ...)
c.viewThis() # Make Web3 calls
c.doThat(sender=a) # Make Web3 transactions
assert c.MyEvent[-1].caller == a # Search through Web3 events
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file eth-ape-0.2.2.tar.gz.
File metadata
- Download URL: eth-ape-0.2.2.tar.gz
- Upload date:
- Size: 199.1 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.8.0 pkginfo/1.8.2 readme-renderer/35.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.9 tqdm/4.64.0 importlib-metadata/4.11.3 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 6693e9ea6a48523a82b156437752adce316cfe04c5a6105e09bdbb533cb9e81e |
|
| MD5 | 57818e5b968338b76a41e056eebeb48f |
|
| BLAKE2b-256 | 3f156bd27e9c50de01f9c8d6711bfef4c6da6d766286352833282e3bdb2cffd8 |
File details
Details for the file eth_ape-0.2.2-py3-none-any.whl.
File metadata
- Download URL: eth_ape-0.2.2-py3-none-any.whl
- Upload date:
- Size: 142.3 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/3.8.0 pkginfo/1.8.2 readme-renderer/35.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.9 tqdm/4.64.0 importlib-metadata/4.11.3 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 67bad68dfdcccd5215ba82fa1f6111f623dce73c95dfd580d0488aaebf83beaf |
|
| MD5 | f2a73a16133a3a4a3cd47246c3e7bf03 |
|
| BLAKE2b-256 | f4de0f82f9e7e3d139a72845fcddccf7bd473d377e9604db9a66df3cac5f2915 |
