A new update is now available for icp-py-core, the community maintained Python agent designed for building on the Internet Computer.
Version 2.3.0 introduces a range of improvements aimed at making development smoother, faster, and more flexible, particularly for teams working with canisters and Candid interfaces in Python.
One of the headline additions is configurable timeouts, allowing developers to set custom limits for query requests and update polling. This gives more control over how applications behave under different network conditions, which can be especially useful when building production-grade services.
The release also adds auto-Candid fetching, meaning the canister wrapper can now retrieve interfaces directly from the Internet Computer. This reduces manual steps and helps developers stay aligned with the latest canister definitions.
Another key change is the introduction of native async support. With async methods now available across all canister functions, Python developers can build more responsive applications and better integrate with modern asynchronous workflows.
Security and verification also receive attention in this version. The update includes optional query signature verification, allowing replica-signed query responses to be checked for authenticity, which may appeal to developers prioritising trust and validation.
Support has also been added for composite queries, extending compatibility with newer Candid query types and broadening the range of canister interactions available through the library.
Alongside new features, the maintainers note that v2.3.0 includes important bug fixes, particularly around read-state handling and v4 call polling, areas that can affect reliability when interacting with the network.
Overall, the update reflects ongoing efforts by the community to strengthen Python tooling within the Internet Computer ecosystem, offering developers more capability while continuing to refine core functionality.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion