Route Rust logs through Python logging via pyo3-log

Cargo.toml

@@ -24,7 +24,7 @@ hypersync-client = "1.4.1"
 anyhow = "1"
 arrow = { version = "57", features = ["ffi"] }
 prefix-hex = "0.7"
-env_logger = "0.11"
+pyo3-log = "0.13"
 faster-hex = "0.9"
 ruint = "1"
 num-bigint = "0.4"

README.md

@@ -111,6 +111,19 @@ export ENVIO_API_TOKEN="your-token-here"
 python examples/simple_logs_of_event.py
 ```
 
+## Logging
+
+The Rust core emits its logs through Python's `logging` module, so the usual handlers, formatters and levels apply. Records from the client arrive under the `hypersync_client` logger (HTTP internals arrive under `reqwest`):
+
+```python
+import logging
+
+logging.basicConfig(level=logging.INFO)
+logging.getLogger("hypersync_client").setLevel(logging.DEBUG)
+```
+
+Configure logging before the first client call. Log levels are cached on the Rust side once a record has been emitted, so changes made later may not take effect.
+
 ## What you can build
 
 The Python client is a natural fit for data science workflows, analytics pipelines, and any application that needs fast access to blockchain data from Python:

src/lib.rs

@@ -29,6 +29,9 @@ use types::RateLimitInfo;
 
 #[pymodule]
 fn hypersync(m: &Bound<'_, PyModule>) -> PyResult<()> {
+    // Forward Rust `log` records to Python's `logging` module.
+    pyo3_log::try_init().ok();
+
     m.add_class::<HypersyncClient>()?;
     m.add_class::<Decoder>()?;
     m.add_class::<CallDecoder>()?;
@@ -51,8 +54,6 @@ impl HypersyncClient {
     /// Create a new client with given config
     #[new]
     fn new(config: ClientConfig) -> Result<HypersyncClient> {
-        env_logger::try_init().ok();
-
         let config = config.try_convert().context("parse config")?;
 
         // Identify this client (and its version) to the server. `hscp` =