Skip to content

docs(operations): use typed 2.x errors and add StepContext.attempt for Python - #277

Open
ayushiahjolia wants to merge 1 commit into
mainfrom
fix/typed-operation-errors-v2
Open

docs(operations): use typed 2.x errors and add StepContext.attempt for Python#277
ayushiahjolia wants to merge 1 commit into
mainfrom
fix/typed-operation-errors-v2

Conversation

@ayushiahjolia

Copy link
Copy Markdown
Contributor

Issue #, if available: aws/aws-durable-execution-sdk-python#663

Description of changes:
Updates the Python tabs in step.md, invoke.md, and child-context.md to match the 2.x SDK error hierarchy, and documents the attempt field on the Python StepContext.

mdformat --check docs/, codespell docs/, check_example_refs.py (529 files), and zensical build --clean all pass.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@ayushiahjolia
ayushiahjolia deployed to ai-pr-review-runtime August 31, 2026 23:11 — with GitHub Actions Active
@ayushiahjolia
ayushiahjolia force-pushed the fix/typed-operation-errors-v2 branch from 7d14286 to 11cf0f7 Compare August 31, 2026 23:17
@ayushiahjolia
ayushiahjolia force-pushed the fix/typed-operation-errors-v2 branch from 11cf0f7 to 40c7e00 Compare August 31, 2026 23:49

The Python SDK uses synchronous methods and does not support `await`.

## 2.x Upgrade

@yaythomas yaythomas Sep 1, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of tucking this away here, I wonder if would help adding a News/Announcements section called:

Label / slug: "What's New" / whats-new
Placement: last top-level tab in the docs nav
Structure: folders per SDK

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this PR I'm intentionally following the same pattern the Java language page already uses for its 2.x migration (a link-out to the SDK's migration guide from the language reference), so Python stays consistent with the existing convention here.

The "What's New" hub is a great fit for the news/announcements space we talked about in the team meetings - a place to post whenever we ship new features. I'll take that on separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants