Install & Compatibility
Where this runs
tested against v0.5.19 · 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
py 3.10
✕ build_error
✕ build_error
py 3.9
✕ build_error
✕ build_error
32MB installed
● package 32MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
UiPathError
✓ from uipath.core.exceptions import UiPathError
✗ from uipath.exceptions import UiPathError
UiPathError is located within the core sub-package.
This example demonstrates how to import and handle a foundational exception from `uipath-core`, showcasing its role in providing core abstractions for custom components.
from uipath.core.exceptions import UiPathError
class CustomUiPathComponent:
def __init__(self, name):
self.name = name
def execute(self, should_fail: bool):
if should_fail:
raise UiPathError(f"Component '{self.name}' failed to execute.")
return f"Component '{self.name}' executed successfully."
try:
component = CustomUiPathComponent("MyProcessor")
print(component.execute(False))
print(component.execute(True))
except UiPathError as e:
print(f"Caught expected UiPathError: {e}")
Debug
Known issues
breakingThe `platform` module, which previously provided core functionalities, was extracted into a separate `uipath-platform` library starting with `uipath-python` SDK v2.9.0. If your application or custom `uipath-core` extensions relied on direct imports from `uipath.platform`, these imports will now fail unless `uipath-platform` is explicitly installed and imports are updated.fixExplicitly install `uipath-platform` (`pip install uipath-platform`) and update any direct `uipath.platform` imports to reflect its new package structure if necessary. Review the `uipath-python` SDK v2.9.0 migration guide for full details.
affects: uipath-python SDK v2.9.0+
breakingCore 'context grounding' contracts underwent significant changes in `uipath-python` SDK v2.9.0. Specific fields like `PreProcessing` and `Fields` were removed, while `extraction_strategy`, `embeddings_enabled`, and `is_encrypted` were added. This impacts any code that interacts with or extends UiPath's context grounding mechanisms, potentially including custom components built using `uipath-core` abstractions.fixReview the `uipath-python` SDK v2.9.0 migration guide for updated context grounding contract details and adapt your code accordingly. Ensure any custom data structures or interfaces align with the new contract.
affects: uipath-python SDK v2.9.0+
gotcha`uipath-core` provides low-level abstractions and foundational components. It is not intended for direct interaction with high-level UiPath SDK functionalities such as orchestrator communication, AI functions, or RPA process execution. Attempting to find or use such features directly from `uipath-core` will result in `AttributeError` or `ImportError`.fixFor high-level SDK operations, use the main `uipath` package (e.g., `pip install uipath`) and refer to its documentation for specific modules like `uipath.functions` or `uipath.orchestrator`.
affects: All versions
Upgrade
Version history
0.5.19latest on PyPI · released Jun 17, 2026
Audit
Dependencies
No dependency data recorded yet.