Algorand Python
Algorand Python is a partial implementation of the Python programming language that runs on the AVM. It includes a statically typed framework for development of Algorand smart contracts and logic signatures, with Pythonic interfaces to underlying AVM functionality that works with standard Python tooling.
Algorand Python is compiled for execution on the AVM by PuyaPy, an optimising compiler that ensures the resulting AVM bytecode execution semantics that match the given Python code. PuyaPy produces output that is directly compatible with AlgoKit typed clients to make deployment and calling easy.
Documentation | Language guide
Installation
Recommended method
The easiest way to use Algorand Python is to instantiate a template with AlgoKit via:
algokit init -t python
This will give you a full development environment with intellisense, linting, automatic formatting, breakpoint debugging, deployment and CI/CD.
A sample smart contract will be placed under PROJECT_NAME/projects/PROJECT_NAME/smart_contracts/SMART_CONTRACT_NAME/contract.py (replacing PROJECT_NAME and SMART_CONTRACT_NAME with the values you chose during the template wizard.)
Manual Alternative
Alternatively, if you want to start from scratch you can do the following:
- Ensure you have Python 3.12+
- Install AlgoKit CLI
- Check you can run the compiler:
algokit compile py -h
- Install Algorand Python into your project
poetry add algorand-python - Create a contract in a (e.g.)
contract.pyfile:from algopy import ARC4Contract, arc4 class HelloWorldContract(ARC4Contract): @arc4.abimethod def hello(self, name: arc4.String) -> arc4.String: return "Hello, " + name
Usage
- Navigate to your contract and compile it:
algokit compile py contract.py
- You should now have
HelloWorldContract.approval.tealandHelloWorldContract.clear.tealon the file system! - We generally recommend using ARC-56 and generated typed clients to have the most optimal deployment and consumption experience; PuyaPy produces an ARC-56 compatible app spec file by default:
algokit compile py contract.py --no-output-teal
- You should now have
HelloWorldContract.arc56.json, which can be generated into a client e.g. using AlgoKit CLI:algokit generate client HelloWorldContract.arc56.json --output client.py
- From here you can dive into the examples or look at the documentation.
Examples
There are many examples in this repo, here are some of the more useful ones that showcase what is possible.
The compiled output is available under the out/ directory alongside these, e.g. the approval
TEAL for voting is available at examples/voting/out/VotingRoundApp.approval.teal.
Metadata
Release files for puyapy 5.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| puyapy-5.10.1-py3-none-any.whl | Python 3 | none | any | Details for puyapy-5.10.1-py3-none-any.whl |
Release files / puyapy-5.10.1-py3-none-any.whl
| Download URL | puyapy-5.10.1-py3-none-any.whl |
|---|---|
| Size | 772.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
317aa257c4ba9f2dec8c9dc7af68a3fed1020a4bcf986c004c0ed5c9ca76ced0
|
|
BLAKE2b-256 checksum How to use checksums |
f52d554b748c443d7ed87216c93e75fab6790a5b7663153fe79f3aa23a175647
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 24, 2026.
Transparency logSecurity for puyapy 5.10.1
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.
Full provenance
1 file in this release has been uploaded with provenance metadata.
Attestation for puyapy-5.10.1-py3-none-any.whl
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 Aug 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.