Skip to content

Python: docs: fix 'rather then' typo in CODING_STANDARD #8323

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mrchatam wants to merge 2 commits into
base: main
Choose a base branch
from
+1 −1
Open

Python: docs: fix 'rather then' typo in CODING_STANDARD #8323

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0a8a18d
Python: docs: fix 'rather then' typo in CODING_STANDARD
mrchatam Sep 11, 2026
817fb02
Merge branch 'main' into docs/fix-rather-than-coding-standard
mrchatam Sep 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion python/CODING_STANDARD.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ We use typing as a helper, it is not a goal in and of itself, so be pragmatic ab
In general, the public interfaces of our classes, are important to get right, internally it is okay to have loosely typed code, as long as tests cover the code itself.
This includes making a conscious choice when to program defensively, you can always do `getattr(item, 'attribute')` but that might end up causing you issues down the road
because the type of `item` in this case, should have that attribute and if it doesn't it points to a larger issue, so if the type is expected to have that attribute, you should
use `item.attribute` to ensure it fails at that point, rather then somewhere downstream where a value is expected but none was found.
use `item.attribute` to ensure it fails at that point, rather than somewhere downstream where a value is expected but none was found.

### Future Annotations

Expand Down
Loading