Skip to content

Conversation

@Lujeni
Copy link

@Lujeni Lujeni commented Jan 12, 2026

The quickstart examples used relative imports (e.g., from .activities) which fail when scripts are run directly with the error "attempted relative import with no known parent package".

What was changed

Changed relative imports to absolute imports README

Why?

Relative imports fail when Python scripts are executed directly (e.g., python run_worker.py) because Python doesn't recognize the script as part of a package. Using absolute imports allows the scripts to be run directly without import errors.

Checklist

  1. Closes

  2. How was this tested:

    • Ran python run_worker.py and verified it no longer throws ImportError: attempted relative import with no known parent package
    • Verified imports work correctly when running the script directly
  3. Any docs updates needed?
    No docs updates needed.

@Lujeni Lujeni requested a review from a team as a code owner January 12, 2026 19:31
@CLAassistant
Copy link

CLAassistant commented Jan 12, 2026

CLA assistant check
All committers have signed the CLA.

@Lujeni Lujeni force-pushed the docs/quick-start-relative-import branch from c69550c to 82bbbc9 Compare January 21, 2026 20:44
…tart

The quickstart examples used relative imports (e.g., `from .activities`)
which fail when scripts are run directly with the error "attempted
relative import with no known parent package".
@Lujeni Lujeni force-pushed the docs/quick-start-relative-import branch from 82bbbc9 to f15e213 Compare January 21, 2026 20:45
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.

3 participants