feat(python-sdk): add logger option for request/debug logging

[mishushakov]

Adds a logger option (a standard library logging.Logger) to Sandbox.create/AsyncSandbox.create and the static Sandbox.connect(sandbox_id, ...), wired into the API client, the envd client, the volume content client, and the RPC (ConnectRPC) path. The logger is stored on the sandbox and propagates to all of its later operations — including control-plane calls like kill/pause/set_timeout/get_info (via get_api_params) — so logging keeps working after construction; mirroring the JS SDK, logger is a construction-time option and not a public per-request parameter those methods accept from the caller, and nothing is logged unless a logger is supplied. The stdlib logging.Logger is used directly as the adapter (no ported JS Logger interface), and log levels match JS: requests at INFO, successful API and unary RPC responses at INFO, streamed RPC messages at DEBUG, failed API responses (status >= 400) at ERROR. The always-on module-level (e2b.*) request logging at the transport layer was removed in favor of this opt-in client-layer logging, and volume content operations continue to accept logger per call via VolumeApiParams to match the JS Volume API. Includes a changeset and unit tests in tests/test_logging_option.py.

Usage

import logging
from e2b import Sandbox

logging.basicConfig(level=logging.DEBUG)
logger = logging.getLogger("my-app.e2b")

sbx = Sandbox.create(logger=logger)
sbx.commands.run("echo hello")   # RPC logged via `logger`
sbx.set_timeout(60)              # control-plane call also logged via `logger`

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: f75d99d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@e2b/python-sdk	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[cursor]

PR Summary

Medium Risk
Wide touch across HTTP/RPC clients with a default logging behavior change (silent unless opt-in), which can break operators who depended on implicit SDK logs without changing application code.

Overview
Adds optional stdlib logging.Logger on sandbox create/connect (and volume per-call), wired through API httpx event hooks, envd HTTP clients, ConnectRPC, and get_api_params so control-plane calls keep the same logger.

Without logger=, the SDK no longer emits the request/response lines that used to come from module loggers on HTTP transports and ApiClient hooks, so existing setups that relied on default e2b.* logging will go quiet unless they pass a logger (behavior change vs prior releases).

TransportWithLogger / AsyncTransportWithLogger (and volume equivalents) still exist but no longer perform logging; only httpx event_hooks log when a logger is supplied, so the transport class names are misleading.

CI runs Windows pytest without --numprocesses=4. Unit coverage is in tests/test_logging_option.py; changeset documents the feature.

^{Reviewed by Cursor Bugbot for commit f75d99d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Package Artifacts

Built from 856c219. Download artifacts from this workflow run.

JS SDK (e2b@2.30.3-mishushakov-python-logger-connection-option.0):

npm install ./e2b-2.30.3-mishushakov-python-logger-connection-option.0.tgz

CLI (@e2b/cli@2.12.1-mishushakov-python-logger-connection-option.0):

npm install ./e2b-cli-2.12.1-mishushakov-python-logger-connection-option.0.tgz

Python SDK (e2b==2.29.2+mishushakov-python-logger-connection-option):

pip install ./e2b-2.29.2+mishushakov.python.logger.connection.option-py3-none-any.whl

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 25416ed3cc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 96c1322. Configure here.}

[mishushakov]

@matthewlouisbrockman was the two commits added on purpose? if it's not related to the PR, i'd move that