fix(README): replace relative imports with absolute imports in quicks… #1272
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…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".
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Closes
How was this tested:
python run_worker.pyand verified it no longer throwsImportError: attempted relative import with no known parent packageAny docs updates needed?
No docs updates needed.