apify 2.7.1b4__tar.gz → 3.0.5b2__tar.gz

{apify-2.7.1b4 → apify-3.0.5b2}/.github/workflows/build_and_deploy_docs.yaml

@@ -22,12 +22,12 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           token: ${{ secrets.APIFY_SERVICE_ACCOUNT_GITHUB_TOKEN }}
 
       - name: Set up Node
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version: ${{ env.NODE_VERSION }}
           cache: npm
@@ -50,12 +50,12 @@ jobs:
           git push
 
       - name: Set up Python
-        uses: actions/setup-python@v5
+        uses: actions/setup-python@v6
         with:
           python-version: ${{ env.PYTHON_VERSION }}
 
       - name: Set up uv package manager
-        uses: astral-sh/setup-uv@v6
+        uses: astral-sh/setup-uv@v7
         with:
           python-version: ${{ env.PYTHON_VERSION }}
 
@@ -72,7 +72,7 @@ jobs:
         uses: actions/configure-pages@v5
 
       - name: Upload GitHub Pages artifact
-        uses: actions/upload-pages-artifact@v3
+        uses: actions/upload-pages-artifact@v4
         with:
           path: ./website/build
 

{apify-2.7.1b4 → apify-3.0.5b2}/.github/workflows/pre_release.yaml

@@ -11,6 +11,10 @@ on:
   # Or it can be triggered manually.
   workflow_dispatch:
 
+concurrency:
+  group: release
+  cancel-in-progress: false
+
 jobs:
   release_metadata:
     if: "!startsWith(github.event.head_commit.message, 'docs') && !startsWith(github.event.head_commit.message, 'ci') && startsWith(github.repository, 'apify/')"

{apify-2.7.1b4 → apify-3.0.5b2}/.github/workflows/release.yaml

@@ -21,6 +21,10 @@ on:
         type: string
         default: ""
 
+concurrency:
+  group: release
+  cancel-in-progress: false
+
 jobs:
   release_metadata:
     name: Prepare release metadata
@@ -57,16 +61,9 @@ jobs:
     with:
       python-versions: '["3.10", "3.11", "3.12", "3.13"]'
 
-  integration_tests:
-    name: Integration tests
-    uses: apify/workflows/.github/workflows/python_integration_tests.yaml@main
-    secrets: inherit
-    with:
-      python-versions: '["3.10", "3.13"]'
-
   update_changelog:
     name: Update changelog
-    needs: [release_metadata, lint_check, type_check, unit_tests, integration_tests]
+    needs: [release_metadata, lint_check, type_check, unit_tests]
     uses: apify/workflows/.github/workflows/python_bump_and_update_changelog.yaml@main
     with:
       version_number: ${{ needs.release_metadata.outputs.version_number }}

{apify-2.7.1b4 → apify-3.0.5b2}/.github/workflows/run_code_checks.yaml

@@ -6,12 +6,7 @@ on:
   # step required for PRs from forks. This prevents their potential exposure.
   pull_request:
 
-  # Pushing to the master branch triggers code checks
-  push:
-    branches:
-      - master
-    tags-ignore:
-      - "**" # Ignore all tags to prevent duplicate checks when tags are pushed.
+  # Trigger for pushing to the master branch is handled by the pre-release workflow.
 
   # It should also be possible to trigger checks manually
   workflow_dispatch:
@@ -41,7 +36,6 @@ jobs:
 
   integration_tests:
     name: Integration tests
-    needs: [lint_check, type_check, unit_tests]
     uses: apify/workflows/.github/workflows/python_integration_tests.yaml@main
     secrets: inherit
     with:

{apify-2.7.1b4 → apify-3.0.5b2}/.github/workflows/update_new_issue.yaml

@@ -14,7 +14,7 @@ jobs:
 
     steps:
       # Add the "t-tooling" label to all new issues
-      - uses: actions/github-script@v7
+      - uses: actions/github-script@v8
         with:
           script: |
             github.rest.issues.addLabels({

{apify-2.7.1b4 → apify-3.0.5b2}/CHANGELOG.md

@@ -3,24 +3,90 @@
 All notable changes to this project will be documented in this file.
 
 <!-- git-cliff-unreleased-start -->
-## 2.7.1 - **not yet released**
+## 3.0.5 - **not yet released**
+
+
+<!-- git-cliff-unreleased-end -->
+## [3.0.4](https://github.com/apify/apify-sdk-python/releases/tag/v3.0.4) (2025-11-03)
 
 ### 🐛 Bug Fixes
 
-- Restrict apify-shared and apify-client versions ([#523](https://github.com/apify/apify-sdk-python/pull/523)) ([b3ae5a9](https://github.com/apify/apify-sdk-python/commit/b3ae5a972a65454a4998eda59c9fcc3f6b7e8579)) by [@vdusek](https://github.com/vdusek)
+- Fix type of `cloud_storage_client` in `SmartApifyStorageClient` ([#642](https://github.com/apify/apify-sdk-python/pull/642)) ([3bf285d](https://github.com/apify/apify-sdk-python/commit/3bf285d60f507730954986a80c19ed2e27a38f9c)) by [@vdusek](https://github.com/vdusek)
+- Fix local charging log dataset name ([#649](https://github.com/apify/apify-sdk-python/pull/649)) ([fdb1276](https://github.com/apify/apify-sdk-python/commit/fdb1276264aee2687596d87c96d19033fe915823)) by [@vdusek](https://github.com/vdusek), closes [#648](https://github.com/apify/apify-sdk-python/issues/648)
 
+### ⚡ Performance
+
+- Use Apify-provided environment variables to obtain PPE pricing information ([#644](https://github.com/apify/apify-sdk-python/pull/644)) ([0c32f29](https://github.com/apify/apify-sdk-python/commit/0c32f29d6a316f5bacc931595d694f262c925b2b)) by [@Mantisus](https://github.com/Mantisus), closes [#614](https://github.com/apify/apify-sdk-python/issues/614)
+
+
+## [3.0.3](https://github.com/apify/apify-sdk-python/releases/tag/v3.0.3) (2025-10-21)
+
+### 🐛 Bug Fixes
+
+- Cache requests in RQ implementations by `id` ([#633](https://github.com/apify/apify-sdk-python/pull/633)) ([76886ce](https://github.com/apify/apify-sdk-python/commit/76886ce496165346a01f67e018547287c211ea54)) by [@Pijukatel](https://github.com/Pijukatel), closes [#630](https://github.com/apify/apify-sdk-python/issues/630)
+
+
+## [3.0.2](https://github.com/apify/apify-sdk-python/releases/tag/v3.0.2) (2025-10-17)
+
+### 🐛 Bug Fixes
+
+- Handle None result in single consumer request queue client ([#623](https://github.com/apify/apify-sdk-python/pull/623)) ([451284a](https://github.com/apify/apify-sdk-python/commit/451284a5c633bc5613bd1e9060df286a1c20b259)) by [@janbuchar](https://github.com/janbuchar), closes [#1472](https://github.com/apify/apify-sdk-python/issues/1472)
+- Unify Actor context manager with init &amp; exit methods ([#600](https://github.com/apify/apify-sdk-python/pull/600)) ([6b0d084](https://github.com/apify/apify-sdk-python/commit/6b0d0842ae66a3a206bbb682a3e5f81ad552f029)) by [@vdusek](https://github.com/vdusek), closes [#598](https://github.com/apify/apify-sdk-python/issues/598)
+- Handle truncated `unique_key` in `list_head` by fetching full request data ([#631](https://github.com/apify/apify-sdk-python/pull/631)) ([4238086](https://github.com/apify/apify-sdk-python/commit/423808678d9155a84a266bf50bb09f1a56466174)) by [@vdusek](https://github.com/vdusek), closes [#627](https://github.com/apify/apify-sdk-python/issues/627)
+
+
+## [3.0.1](https://github.com/apify/apify-sdk-python/releases/tag/v3.0.1) (2025-10-08)
+
+### 🐛 Bug Fixes
+
+- Also load input from a file with a .json extension in file system storage ([#617](https://github.com/apify/apify-sdk-python/pull/617)) ([b62804c](https://github.com/apify/apify-sdk-python/commit/b62804c170069cd7aa77572bb9682a156581cbac)) by [@janbuchar](https://github.com/janbuchar)
 
-<!-- git-cliff-unreleased-end -->
-## [2.7.0](https://github.com/apify/apify-sdk-python/releases/tag/v2.7.0) (2025-07-14)
+
+## [3.0.0](https://github.com/apify/apify-sdk-python/releases/tag/v3.0.0) (2025-09-29)
+
+- Check out the [Upgrading guide](https://docs.apify.com/sdk/python/docs/upgrading/upgrading-to-v3) to ensure a smooth update.
 
 ### 🚀 Features
 
-- **crypto:** Decrypt secret objects ([#482](https://github.com/apify/apify-sdk-python/pull/482)) ([ce9daf7](https://github.com/apify/apify-sdk-python/commit/ce9daf7381212b8dc194e8a643e5ca0dedbc0078)) by [@MFori](https://github.com/MFori)
+- Add deduplication to `add_batch_of_requests` ([#534](https://github.com/apify/apify-sdk-python/pull/534)) ([dd03c4d](https://github.com/apify/apify-sdk-python/commit/dd03c4d446f611492adf35f1b5738648ee5a66f7)) by [@Pijukatel](https://github.com/Pijukatel), closes [#514](https://github.com/apify/apify-sdk-python/issues/514)
+- Add new methods to ChargingManager ([#580](https://github.com/apify/apify-sdk-python/pull/580)) ([54f7f8b](https://github.com/apify/apify-sdk-python/commit/54f7f8b29c5982be98b595dac11eceff915035c9)) by [@vdusek](https://github.com/vdusek)
+- Add support for NDU storages ([#594](https://github.com/apify/apify-sdk-python/pull/594)) ([8721ef5](https://github.com/apify/apify-sdk-python/commit/8721ef5731bcb1a04ad63c930089bf83be29f308)) by [@vdusek](https://github.com/vdusek), closes [#1175](https://github.com/apify/apify-sdk-python/issues/1175)
+- Add stats to `ApifyRequestQueueClient` ([#574](https://github.com/apify/apify-sdk-python/pull/574)) ([21f6782](https://github.com/apify/apify-sdk-python/commit/21f6782b444f623aba986b4922cf67bafafd4b2c)) by [@Pijukatel](https://github.com/Pijukatel), closes [#1344](https://github.com/apify/apify-sdk-python/issues/1344)
+- Add specialized ApifyRequestQueue clients ([#573](https://github.com/apify/apify-sdk-python/pull/573)) ([f830ab0](https://github.com/apify/apify-sdk-python/commit/f830ab09b1fa12189c9d3297d5cf18a4f2da62fa)) by [@Pijukatel](https://github.com/Pijukatel)
 
 ### 🐛 Bug Fixes
 
-- Sync `@docusaurus` theme version [internal] ([#500](https://github.com/apify/apify-sdk-python/pull/500)) ([a7485e7](https://github.com/apify/apify-sdk-python/commit/a7485e7d2276fde464ce862573d5b95e7d4d836a)) by [@katzino](https://github.com/katzino)
-- Tagline overlap ([#501](https://github.com/apify/apify-sdk-python/pull/501)) ([bae8340](https://github.com/apify/apify-sdk-python/commit/bae8340c46fea756ea35ea4d591da84c09d478e2)) by [@katzino](https://github.com/katzino)
+- Restrict apify-shared and apify-client versions ([#523](https://github.com/apify/apify-sdk-python/pull/523)) ([b3ae5a9](https://github.com/apify/apify-sdk-python/commit/b3ae5a972a65454a4998eda59c9fcc3f6b7e8579)) by [@vdusek](https://github.com/vdusek)
+- Expose `APIFY_USER_IS_PAYING` env var to the configuration ([#507](https://github.com/apify/apify-sdk-python/pull/507)) ([0801e54](https://github.com/apify/apify-sdk-python/commit/0801e54887317c1280cc6828ecd3f2cc53287e76)) by [@stepskop](https://github.com/stepskop)
+- Resolve DeprecationWarning in ApifyEventManager ([#555](https://github.com/apify/apify-sdk-python/pull/555)) ([0c5111d](https://github.com/apify/apify-sdk-python/commit/0c5111dafe19796ec1fb9652a44c031bed9758df)) by [@vdusek](https://github.com/vdusek), closes [#343](https://github.com/apify/apify-sdk-python/issues/343)
+- Use same `client_key` for `Actor` created `request_queue` and improve its metadata estimation ([#552](https://github.com/apify/apify-sdk-python/pull/552)) ([7e4e5da](https://github.com/apify/apify-sdk-python/commit/7e4e5da81dd87e84ebeef2bd336c6c1d422cb9a7)) by [@Pijukatel](https://github.com/Pijukatel), closes [#536](https://github.com/apify/apify-sdk-python/issues/536)
+- Properly process pre-existing Actor input file ([#591](https://github.com/apify/apify-sdk-python/pull/591)) ([cc5075f](https://github.com/apify/apify-sdk-python/commit/cc5075fab8c72ca5711cfd97932037b34e6997cd)) by [@Pijukatel](https://github.com/Pijukatel), closes [#590](https://github.com/apify/apify-sdk-python/issues/590)
+
+### Chore
+
+- [**breaking**] Update apify-client and apify-shared to v2.0 ([#548](https://github.com/apify/apify-sdk-python/pull/548)) ([8ba084d](https://github.com/apify/apify-sdk-python/commit/8ba084ded6cd018111343f2219260b481c8d4e35)) by [@vdusek](https://github.com/vdusek)
+
+### Refactor
+
+- [**breaking**] Adapt to the Crawlee v1.0 ([#470](https://github.com/apify/apify-sdk-python/pull/470)) ([f7e3320](https://github.com/apify/apify-sdk-python/commit/f7e33206cf3e4767faacbdc43511b45b6785f929)) by [@vdusek](https://github.com/vdusek), closes [#469](https://github.com/apify/apify-sdk-python/issues/469), [#540](https://github.com/apify/apify-sdk-python/issues/540)
+- [**breaking**] Replace `httpx` with `impit` ([#560](https://github.com/apify/apify-sdk-python/pull/560)) ([cca3869](https://github.com/apify/apify-sdk-python/commit/cca3869e85968865e56aafcdcb36fbccba27aef0)) by [@Mantisus](https://github.com/Mantisus), closes [#558](https://github.com/apify/apify-sdk-python/issues/558)
+- [**breaking**] Remove `Request.id` field ([#553](https://github.com/apify/apify-sdk-python/pull/553)) ([445ab5d](https://github.com/apify/apify-sdk-python/commit/445ab5d752b785fc2018b35c8adbe779253d7acd)) by [@Pijukatel](https://github.com/Pijukatel)
+- [**breaking**] Make `Actor` initialization stricter and more predictable ([#576](https://github.com/apify/apify-sdk-python/pull/576)) ([912222a](https://github.com/apify/apify-sdk-python/commit/912222a7a8123be66c94c50a2e461276fbfc50c4)) by [@Pijukatel](https://github.com/Pijukatel)
+- [**breaking**] Make default Apify storages use alias mechanism ([#606](https://github.com/apify/apify-sdk-python/pull/606)) ([dbea7d9](https://github.com/apify/apify-sdk-python/commit/dbea7d97fe7f25aa8658a32c5bb46a3800561df5)) by [@Pijukatel](https://github.com/Pijukatel), closes [#599](https://github.com/apify/apify-sdk-python/issues/599)
+
+
+## [2.7.3](https://github.com/apify/apify-sdk-python/releases/tag/v2.7.3) (2025-08-11)
+
+### 🐛 Bug Fixes
+
+- Expose `APIFY_USER_IS_PAYING` env var to the configuration (#507) ([0de022c](https://github.com/apify/apify-sdk-python/commit/0de022c3435f24c821053c771e7b659433e3fb6e))
+
+
+## [2.7.2](https://github.com/apify/apify-sdk-python/releases/tag/v2.7.2) (2025-07-30)
+
+### 🐛 Bug Fixes
+
+- Restrict apify-shared and apify-client versions ([#523](https://github.com/apify/apify-sdk-python/pull/523)) ([581ebae](https://github.com/apify/apify-sdk-python/commit/581ebae5752a984a34cbabc02c49945ae392db00)) by [@vdusek](https://github.com/vdusek)
 
 
 ## [2.7.1](https://github.com/apify/apify-sdk-python/releases/tag/v2.7.1) (2025-07-24)
@@ -148,6 +214,8 @@ All notable changes to this project will be documented in this file.
 
 ## [2.0.0](https://github.com/apify/apify-sdk-python/releases/tag/v2.0.0) (2024-09-10)
 
+- Check out the [Upgrading guide](https://docs.apify.com/sdk/python/docs/upgrading/upgrading-to-v2) to ensure a smooth update.
+
 ### 🚀 Features
 
 - Better Actor API typing ([#256](https://github.com/apify/apify-sdk-python/pull/256)) ([abb87e7](https://github.com/apify/apify-sdk-python/commit/abb87e7f3c272f88a9a76292d8394fe93b98428a)) by [@janbuchar](https://github.com/janbuchar), closes [#243](https://github.com/apify/apify-sdk-python/issues/243)

{apify-2.7.1b4 → apify-3.0.5b2}/Makefile

@@ -26,13 +26,13 @@ type-check:
 	uv run mypy
 
 unit-tests:
-	uv run pytest --numprocesses=auto --verbose --cov=src/apify tests/unit
+	uv run pytest --numprocesses=auto -vv --cov=src/apify tests/unit
 
 unit-tests-cov:
-	uv run pytest --numprocesses=auto --verbose --cov=src/apify --cov-report=html tests/unit
+	uv run pytest --numprocesses=auto -vv --cov=src/apify --cov-report=html tests/unit
 
 integration-tests:
-	uv run pytest --numprocesses=$(INTEGRATION_TESTS_CONCURRENCY) --verbose tests/integration
+	uv run pytest --numprocesses=$(INTEGRATION_TESTS_CONCURRENCY) -vv tests/integration
 
 format:
 	uv run ruff check --fix

{apify-2.7.1b4 → apify-3.0.5b2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: apify
-Version: 2.7.1b4
+Version: 3.0.5b2
 Summary: Apify SDK for Python
 Project-URL: Apify Homepage, https://apify.com
 Project-URL: Changelog, https://docs.apify.com/sdk/python/docs/changelog
@@ -225,20 +225,37 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Software Development :: Libraries
 Requires-Python: >=3.10
-Requires-Dist: apify-client<2.0.0
-Requires-Dist: apify-shared<2.0.0
-Requires-Dist: crawlee~=0.6.0
+Requires-Dist: apify-client<3.0.0,>=2.2.0
+Requires-Dist: apify-shared<3.0.0,>=2.0.0
+Requires-Dist: cachetools>=5.5.0
+Requires-Dist: crawlee<2.0.0,>=1.0.4
 Requires-Dist: cryptography>=42.0.0
-Requires-Dist: httpx>=0.27.0
-Requires-Dist: lazy-object-proxy<1.11.0
+Requires-Dist: impit>=0.6.1
+Requires-Dist: lazy-object-proxy>=1.11.0
 Requires-Dist: more-itertools>=10.2.0
 Requires-Dist: typing-extensions>=4.1.0
 Requires-Dist: websockets>=14.0
+Requires-Dist: yarl>=1.18.0
 Provides-Extra: scrapy
 Requires-Dist: scrapy>=2.11.0; extra == 'scrapy'
 Description-Content-Type: text/markdown
 
-# Apify SDK for Python
+<h1 align=center>Apify SDK for Python</h1>
+
+<p align=center>
+    <a href="https://badge.fury.io/py/apify" rel="nofollow">
+        <img src="https://badge.fury.io/py/apify.svg" alt="PyPI version" style="max-width: 100%;">
+    </a>
+    <a href="https://pypi.org/project/apify/" rel="nofollow">
+        <img src="https://img.shields.io/pypi/dm/apify" alt="PyPI - Downloads" style="max-width: 100%;">
+    </a>
+    <a href="https://pypi.org/project/apify/" rel="nofollow">
+        <img src="https://img.shields.io/pypi/pyversions/apify" alt="PyPI - Python Version" style="max-width: 100%;">
+    </a>
+    <a href="https://discord.gg/jyEM2PRvMU" rel="nofollow">
+        <img src="https://img.shields.io/discord/801163717915574323?label=discord" alt="Chat on discord" style="max-width: 100%;">
+    </a>
+</p>
 
 The Apify SDK for Python is the official library to create [Apify Actors](https://docs.apify.com/platform/actors)
 in Python. It provides useful features like Actor lifecycle management, local storage emulation, and Actor

{apify-2.7.1b4 → apify-3.0.5b2}/README.md

@@ -1,4 +1,19 @@
-# Apify SDK for Python
+<h1 align=center>Apify SDK for Python</h1>
+
+<p align=center>
+    <a href="https://badge.fury.io/py/apify" rel="nofollow">
+        <img src="https://badge.fury.io/py/apify.svg" alt="PyPI version" style="max-width: 100%;">
+    </a>
+    <a href="https://pypi.org/project/apify/" rel="nofollow">
+        <img src="https://img.shields.io/pypi/dm/apify" alt="PyPI - Downloads" style="max-width: 100%;">
+    </a>
+    <a href="https://pypi.org/project/apify/" rel="nofollow">
+        <img src="https://img.shields.io/pypi/pyversions/apify" alt="PyPI - Python Version" style="max-width: 100%;">
+    </a>
+    <a href="https://discord.gg/jyEM2PRvMU" rel="nofollow">
+        <img src="https://img.shields.io/discord/801163717915574323?label=discord" alt="Chat on discord" style="max-width: 100%;">
+    </a>
+</p>
 
 The Apify SDK for Python is the official library to create [Apify Actors](https://docs.apify.com/platform/actors)
 in Python. It provides useful features like Actor lifecycle management, local storage emulation, and Actor

apify-3.0.5b2/docs/02_concepts/01_actor_lifecycle.mdx

@@ -0,0 +1,101 @@
+---
+id: actor-lifecycle
+title: Actor lifecycle
+---
+
+import CodeBlock from '@theme/CodeBlock';
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+import ClassContextExample from '!!raw-loader!./code/01_class_context.py';
+import ClassManualExample from '!!raw-loader!./code/01_class_manual.py';
+import InstanceContextExample from '!!raw-loader!./code/01_instance_context.py';
+import InstanceManualExample from '!!raw-loader!./code/01_instance_manual.py';
+
+import ErrorHandlingContextExample from '!!raw-loader!./code/01_error_handling_context.py';
+import ErrorHandlingManualExample from '!!raw-loader!./code/01_error_handling_manual.py';
+
+import RebootExample from '!!raw-loader!./code/01_reboot.py';
+
+import StatusMessageExample from '!!raw-loader!./code/01_status_message.py';
+
+This guide explains how an **Apify Actor** starts, runs, and shuts down, describing the complete Actor lifecycle. For information about the core concepts such as Actors, the Apify Console, storages, and events, check out the [Apify platform documentation](https://docs.apify.com/platform).
+
+## Actor initialization
+
+During initialization, the SDK prepares all the components required to integrate with the Apify platform. It loads configuration from environment variables, initializes access to platform storages such as the [key-value store, dataset, and request queue](https://docs.apify.com/platform/storage), sets up event handling for [platform events](https://docs.apify.com/platform/integrations/webhooks/events), and configures logging.
+
+The recommended approach in Python is to use the global [`Actor`](https://docs.apify.com/sdk/python/reference/class/Actor) class as an asynchronous context manager. This approach automatically manages setup and teardown and keeps your code concise. When entering the context, the SDK loads configuration and initializes clients lazily—for example, a dataset is opened only when it is first accessed. If the Actor runs on the Apify platform, it also begins listening for platform events.
+
+When the Actor exits, either normally or due to an exception, the SDK performs a graceful shutdown. It persists the final Actor state, stops event handling, and sets the terminal exit code together with the [status message](https://docs.apify.com/platform/actors/development/programming-interface/status-messages).
+
+<Tabs groupId="request_queue">
+    <TabItem value="actor_class_with_context_manager" label="Actor class with context manager" default>
+        <CodeBlock className="language-python">
+            {ClassContextExample}
+        </CodeBlock>
+    </TabItem>
+    <TabItem value="actor_class_with_manual_init_exit" label="Actor class with manual init/exit">
+        <CodeBlock className="language-python">
+            {ClassManualExample}
+        </CodeBlock>
+    </TabItem>
+</Tabs>
+
+You can also create an [`Actor`](https://docs.apify.com/sdk/python/reference/class/Actor) instance directly. This does not change its capabilities but allows you to specify optional parameters during initialization, such as disabling automatic `sys.exit()` calls or customizing timeouts. The choice between using a context manager or manual initialization depends on how much control you require over the Actor's startup and shutdown sequence.
+
+<Tabs groupId="request_queue">
+    <TabItem value="actor_instance_with_context_manager" label="Actor instance with context manager" default>
+        <CodeBlock className="language-python">
+            {InstanceContextExample}
+        </CodeBlock>
+    </TabItem>
+    <TabItem value="actor_instance_with_manual_init_exit" label="Actor instance with manual init/exit">
+        <CodeBlock className="language-python">
+            {InstanceManualExample}
+        </CodeBlock>
+    </TabItem>
+</Tabs>
+
+## Error handling
+
+Good error handling lets your Actor fail fast on critical errors, retry transient issues safely, and keep data consistent. Normally you rely on the `async with Actor:` block—if it finishes, the run succeeds (exit code 0); if an unhandled exception occurs, the run fails (exit code 1).
+
+The SDK provides helper methods for explicit control:
+
+- [`Actor.exit`](https://docs.apify.com/sdk/python/reference/class/Actor#exit) -  terminates the run successfully (default exit code 0).
+- [`Actor.fail`](https://docs.apify.com/sdk/python/reference/class/Actor#fail) -  marks the run as failed (default exit code 1).
+
+Any non-zero exit code is treated as a `FAILED` run. You rarely need to call these methods directly unless you want to perform a controlled shutdown or customize the exit behavior.
+
+Catch exceptions only when necessary - for example, to retry network timeouts or map specific errors to exit codes. Keep retry loops bounded with backoff and re-raise once exhausted. Make your processing idempotent so that restarts don't corrupt results. Both [`Actor.exit`](https://docs.apify.com/sdk/python/reference/class/Actor#exit) and [`Actor.fail`](https://docs.apify.com/sdk/python/reference/class/Actor#fail) perform the same cleanup, so complete any long-running persistence before calling them.
+
+Below is a minimal context-manager example where an unhandled exception automatically fails the run, followed by a manual pattern giving you more control.
+
+<CodeBlock className="language-python">{ErrorHandlingContextExample}</CodeBlock>
+
+If you need explicit control over exit codes or status messages, you can manage the Actor manually using [`Actor.init`](https://docs.apify.com/sdk/python/reference/class/Actor#init), [`Actor.exit`](https://docs.apify.com/sdk/python/reference/class/Actor#exit), and [`Actor.fail`](https://docs.apify.com/sdk/python/reference/class/Actor#fail).
+
+<CodeBlock className="language-python">{ErrorHandlingManualExample}</CodeBlock>
+
+## Reboot
+
+Rebooting (available on the Apify platform only) instructs the platform worker to restart your Actor from the beginning of its execution. Use this mechanism only for transient conditions that are likely to resolve after a fresh start — for example, rotating a blocked proxy pool or recovering from a stuck browser environment.
+
+Before triggering a reboot, persist any essential state externally (e.g., to the key-value store or dataset), as all in-memory data is lost after reboot. The example below tracks a reboot counter in the default key-value store and allows at most three restarts before exiting normally.
+
+<CodeBlock className="language-python">{RebootExample}</CodeBlock>
+
+## Status message
+
+[Status messages](https://docs.apify.com/platform/actors/development/programming-interface/status-messages) are lightweight, human-readable progress indicators displayed with the Actor run on the Apify platform (separate from logs). Use them to communicate high-level phases or milestones, such as "Fetching list", "Processed 120/500 pages", or "Uploading results".
+
+Update the status only when the user's understanding of progress changes - avoid frequent updates for every processed item. Detailed information should go to logs or storages (dataset, key-value store) instead.
+
+The SDK optimizes updates by sending an API request only when the message text changes, so repeating the same message incurs no additional cost.
+
+<CodeBlock className="language-python">{StatusMessageExample}</CodeBlock>
+
+## Conclusion
+
+This page has presented the full Actor lifecycle: initialization, execution, error handling, rebooting, shutdown and status messages. You've seen how the SDK supports both context-based and manual control patterns. For deeper dives, explore the [reference docs](https://docs.apify.com/sdk/python/reference), [guides](https://docs.apify.com/sdk/python/docs/guides/beautifulsoup-httpx), and [platform documentation](https://docs.apify.com/platform).

{apify-2.7.1b4/docs/03_concepts → apify-3.0.5b2/docs/02_concepts}/09_running_webserver.mdx

@@ -13,9 +13,9 @@ The URL is available in the following places:
 
 - In Apify Console, on the Actor run details page as the **Container URL** field.
 - In the API as the `container_url` property of the [Run object](https://docs.apify.com/api/v2#/reference/actors/run-object/get-run).
-- In the Actor as the `Actor.config.container_url` property.
+- In the Actor as the `Actor.configuration.container_url` property.
 
-The web server running inside the container must listen at the port defined by the `Actor.config.container_port` property. When running Actors locally, the port defaults to `4321`, so the web server will be accessible at `http://localhost:4321`.
+The web server running inside the container must listen at the port defined by the `Actor.configuration.container_port` property. When running Actors locally, the port defaults to `4321`, so the web server will be accessible at `http://localhost:4321`.
 
 ## Example
 

{apify-2.7.1b4/docs/03_concepts → apify-3.0.5b2/docs/02_concepts}/12_pay_per_event.mdx

@@ -13,6 +13,12 @@ Apify provides several [pricing models](https://docs.apify.com/platform/actors/p
 
 To use the pay-per-event pricing model, you first need to [set it up](https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event) for your Actor in the Apify console. After that, you're free to start charging for events.
 
+:::info How pay-per-event pricing works
+
+If you want more details about PPE pricing, please refer to our [PPE documentation](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event).
+
+:::
+
 ## Charging for events
 
 After monetization is set in the Apify console, you can add <ApiLink to="class/Actor#charge">`Actor.charge`</ApiLink> calls to your code and start monetizing!
@@ -41,6 +47,6 @@ It is encouraged to test your monetization code on your machine before releasing
 ACTOR_TEST_PAY_PER_EVENT=true python -m youractor
 ```
 
-If you also wish to see a log of all the events charged throughout the run, the Apify SDK keeps a log of charged events in a so called charging dataset. Your charging dataset can be found under the `charging_log` name (unless you change your storage settings, this dataset is stored in `storage/datasets/charging_log/`). Please note that this log is not available when running the Actor in production on the Apify platform.
+If you also wish to see a log of all the events charged throughout the run, the Apify SDK keeps a log of charged events in a so called charging dataset. Your charging dataset can be found under the `charging-log` name (unless you change your storage settings, this dataset is stored in `storage/datasets/charging-log/`). Please note that this log is not available when running the Actor in production on the Apify platform.
 
 Because pricing configuration is stored by the Apify platform, all events will have a default price of $1.

apify-3.0.5b2/docs/02_concepts/code/01_class_context.py

@@ -0,0 +1,21 @@
+import asyncio
+
+from apify import Actor
+
+
+async def main() -> None:
+    async with Actor:
+        # Get input
+        actor_input = await Actor.get_input()
+        Actor.log.info('Actor input: %s', actor_input)
+
+        # Your Actor logic here
+        data = {'message': 'Hello from Actor!', 'input': actor_input}
+        await Actor.push_data(data)
+
+        # Set status message
+        await Actor.set_status_message('Actor completed successfully')
+
+
+if __name__ == '__main__':
+    asyncio.run(main())

apify-3.0.5b2/docs/02_concepts/code/01_class_manual.py

@@ -0,0 +1,26 @@
+import asyncio
+
+from apify import Actor
+
+
+async def main() -> None:
+    await Actor.init()
+
+    try:
+        # Get input
+        actor_input = await Actor.get_input()
+        Actor.log.info('Actor input: %s', actor_input)
+
+        # Your Actor logic here
+        data = {'message': 'Hello from Actor!', 'input': actor_input}
+        await Actor.push_data(data)
+
+        # Set status message
+        await Actor.set_status_message('Actor completed successfully')
+
+    finally:
+        await Actor.exit()
+
+
+if __name__ == '__main__':
+    asyncio.run(main())

{apify-2.7.1b4/docs/03_concepts → apify-3.0.5b2/docs/02_concepts}/code/01_context_manager.py

@@ -1,3 +1,5 @@
+import asyncio
+
 from apify import Actor
 
 
@@ -7,3 +9,7 @@ async def main() -> None:
         Actor.log.info('Actor input: %s', actor_input)
         await Actor.set_value('OUTPUT', 'Hello, world!')
         raise RuntimeError('Ouch!')
+
+
+if __name__ == '__main__':
+    asyncio.run(main())

apify-3.0.5b2/docs/02_concepts/code/01_error_handling_context.py

@@ -0,0 +1,13 @@
+import asyncio
+
+from apify import Actor
+
+
+async def main() -> None:
+    async with Actor:
+        # Any unhandled exception triggers Actor.fail() automatically
+        raise RuntimeError('Boom')
+
+
+if __name__ == '__main__':
+    asyncio.run(main())

apify-3.0.5b2/docs/02_concepts/code/01_error_handling_manual.py

@@ -0,0 +1,33 @@
+import asyncio
+import random
+
+from apify import Actor
+
+
+async def do_work() -> None:
+    # Simulate random outcomes: success or one of two exception types.
+    outcome = random.random()
+
+    if outcome < 0.33:
+        raise ValueError('Invalid input data encountered')
+    if outcome < 0.66:
+        raise RuntimeError('Unexpected runtime failure')
+
+    # Simulate successful work
+    Actor.log.info('Work completed successfully')
+
+
+async def main() -> None:
+    await Actor.init()
+    try:
+        await do_work()
+    except ValueError as exc:  # Specific error mapping example
+        await Actor.fail(exit_code=10, exception=exc)
+    except Exception as exc:  # Catch-all for unexpected errors
+        await Actor.fail(exit_code=91, exception=exc)
+    else:
+        await Actor.exit(status_message='Actor completed successfully')
+
+
+if __name__ == '__main__':
+    asyncio.run(main())

{apify-2.7.1b4/docs/03_concepts → apify-3.0.5b2/docs/02_concepts}/code/01_init_exit.py

@@ -1,3 +1,5 @@
+import asyncio
+
 from apify import Actor
 
 
@@ -14,3 +16,7 @@ async def main() -> None:
         await Actor.fail(exit_code=91, exception=exc)
 
     await Actor.exit()
+
+
+if __name__ == '__main__':
+    asyncio.run(main())

apify-3.0.5b2/docs/02_concepts/code/01_instance_context.py

@@ -0,0 +1,27 @@
+import asyncio
+from datetime import timedelta
+
+from apify import Actor
+
+
+async def main() -> None:
+    actor = Actor(
+        event_listeners_timeout=timedelta(seconds=30),
+        cleanup_timeout=timedelta(seconds=30),
+    )
+
+    async with actor:
+        # Get input
+        actor_input = await actor.get_input()
+        actor.log.info('Actor input: %s', actor_input)
+
+        # Your Actor logic here
+        data = {'message': 'Hello from Actor instance!', 'input': actor_input}
+        await actor.push_data(data)
+
+        # Set status message
+        await actor.set_status_message('Actor completed successfully')
+
+
+if __name__ == '__main__':
+    asyncio.run(main())