Registry / http-networking / apify-shared

apify-shared

JSON →
library2.3.0pypypi✓ verified 23d ago

The `apify-shared-python` library (current version 2.2.0) provides constants and utilities shared internally across Apify's other Python projects, such as `apify-client-python` and `apify-sdk-python`. It is not intended for direct public consumption, and its internal API is subject to change without deprecation warnings. The library maintains an active development status as it supports other core Apify libraries.

pip install apify-shared
INSTALL
IMPORT
SIG · APIFY-SHARED
A
apify-shared
http-networkingpythonv2.3.0
Install
1.6s avg
Import
114ms
Disk
16MB
Pass rate
10/ 10
Env Coverage10 / 10
glibc
3.93.13
musl
3.93.13
Install & Compatibility
Where this runs
tested against v2.3.0 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
py 3.103.95 runs
installs and imports cleanly · install 0.0s · import 0.118s · 17.8MB
glibc
py 3.103.95 runs
installs and imports cleanly · install 1.6s · import 0.110s · 18MB
16MB installed
● package 16MB
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

ActorExitCodes
from apify_shared.consts import ActorExitCodes
This is an example of importing a constant. Users are strongly advised against directly importing from `apify_shared` as it is an internal library with no stable public API.

This quickstart demonstrates a minimal import from `apify-shared`. However, this library is strictly for internal Apify use. Direct consumption is discouraged, and users should typically use `apify-sdk` or `apify-client` for developing Apify Actors or interacting with the Apify API.

from apify_shared.consts import ActorExitCodes # Accessing an internal constant (example) print(f"Actor OK exit code: {ActorExitCodes.SUCCESS}")
Debug
Known issues
breakingThis library is for internal use by Apify projects only. Its public API is not stable and may introduce breaking changes at any time without prior deprecation warnings. Users should avoid direct usage.
fix
Use `apify-sdk` for developing Apify Actors or `apify-client` for interacting with the Apify API, which provide stable public APIs. Only use `apify-shared` if explicitly instructed by Apify for development within their ecosystem.
affects: All versions
gotchaThere is no guaranteed backward compatibility for `apify-shared`. Functions, classes, and constants may be renamed, moved, or removed without notice, leading to unexpected errors or behavior in applications directly dependent on it.
fix
As advised, refrain from building applications directly on `apify-shared`. Rely on the stable APIs provided by `apify-sdk` or `apify-client` which manage their internal dependencies on `apify-shared` appropriately.
affects: All versions
Errors
Common errors & fixes
ModuleNotFoundError: No module named 'apify_shared'
The 'apify-shared' package is not installed in the Python environment.
fix
Install the package using 'pip install apify-shared'.
ImportError: cannot import name 'Actor' from 'apify_shared'
The 'Actor' class is not part of the 'apify-shared' package; it belongs to the 'apify' package.
fix
Use 'from apify import Actor' instead.
TypeError: 'NoneType' object is not iterable
Attempting to iterate over a 'None' object, possibly due to a failed API call returning 'None'.
fix
Check the API response for errors and handle cases where the response is 'None'.
Upgrade
Version history
2.3.0latest on PyPI · released Aug 3, 2026
Audit
Dependencies
pythonrequiredRequired runtime environment.
Agent activity
21 hits · last 30 days
node
18
OpenAI (training)
1
Resources
apify-shared — pip install apify-shared · libregistry