Install & Compatibility
Where this runs
tested against v0.6.1 · 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
muslpy 3.10–3.920 runs
installs and imports cleanly · install 0.0s · import 0.000s · 17.8MB
glibcpy 3.10–3.920 runs
installs and imports cleanly · install 1.5s · import 0.000s · 18MB
16MB installed
● package 16MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
ChainMap
✓ from aiotask_context import ChainMap
✗ from aiotask_context import context
get
✓ from aiotask_context import get
set
✓ from aiotask_context import set
This quickstart demonstrates how `aiotask-context` allows setting context variables that are isolated to the current `asyncio.Task`. Sub-tasks inherit a copy of their parent's context, and modifications within a sub-task do not affect the parent or sibling tasks, ensuring task-local storage.
import asyncio
from aiotask_context import context
async def nested_task(task_id: str):
"""A sub-task that accesses and modifies context."""
request_id = context.get("request_id")
print(f"Task {task_id}: Retrieved request_id: {request_id}")
# Set a task-specific value; this does not affect other tasks' contexts
# nor the parent task's context once the child task's context is copied.
context.set("task_data", f"Data from {task_id}")
await asyncio.sleep(0.01) # Simulate async work
print(f"Task {task_id}: Set task_data: {context.get('task_data')}")
async def main():
print("--- aiotask-context Quickstart ---")
# Set context in the main task
context.set("request_id", "req-xyz-123")
print(f"Main task: Initial request_id: {context.get('request_id')}")
# Create and run sub-tasks. Each sub-task inherits a *copy* of the parent's context.
task1 = asyncio.create_task(nested_task("A"))
task2 = asyncio.create_task(nested_task("B"))
await task1
await task2
# The main task's context remains unchanged by sub-tasks' modifications
print(f"Main task: Final request_id: {context.get('request_id')}") # Should be 'req-xyz-123'
# Task-specific data set in sub-tasks is not accessible here in the main task
print(f"Main task: task_data: {context.get('task_data')}") # Should be None
print("This demonstrates task-local context isolation in asyncio.")
if __name__ == "__main__":
asyncio.run(main())
Debug
Known issues
breakingThe package underwent a significant change in version 0.4.0. Prior to 0.4.0, `Context` was a class that needed to be instantiated (e.g., `c = Context()`). Since 0.4.0, `context` is a pre-instantiated singleton object directly imported (`from aiotask_context import context`).fixUpdate your import statement from `from aiotask_context import Context` and remove any instantiation, using `context` directly instead.
affects: < 0.4.0
breakingThe project's GitHub repository and primary maintainership transitioned from `vimeo/aiotask-context` to `python-aiotask-context/aiotask-context`. While the package name on PyPI remains the same, older documentation or references might point to the outdated repository.fixAlways refer to the official repository at `https://github.com/python-aiotask-context/aiotask-context` for the most up-to-date information, issues, and contributions.
affects: All versions
gotchaContext in `aiotask-context` is strictly task-local. When `asyncio.create_task` is used, the child task inherits a *copy* of the parent's context. Any modifications made by the child task to its context will not reflect in the parent task's context or sibling tasks' contexts.fixUnderstand that `aiotask-context` provides task-local storage, not global or shared state across tasks. If you need to communicate state *back* to a parent task, use standard asyncio mechanisms like `asyncio.Queue` or return values.
affects: All versions
gotcha`aiotask-context` is designed for task-scoped data and should not be confused with `contextvars` (PEP 567) introduced in Python 3.7. While both provide context management, `aiotask-context` predates `contextvars` and relies on direct manipulation of `asyncio.Task` internals. `contextvars` offers a more robust and officially supported way for context propagation.fixFor new projects on Python 3.7+, consider evaluating `contextvars` from the standard library. If using `aiotask-context`, be aware of its specific implementation and ensure it meets your requirements.
affects: All versions, especially Python 3.7+
Upgrade
Version history
0.6.1latest on PyPI · released Jan 21, 2020
Audit
Dependencies
No dependency data recorded yet.