Skip to content

fix: correct spelling errors in docstrings and test docs - #2093

Open
RoomWithOutRoof (Jah-yee) wants to merge 1 commit into
microsoft:mainfrom
Jah-yee:fix/spelling-typos-2026-11-06
Open

RoomWithOutRoof (Jah-yee) wants to merge 1 commit into
microsoft:mainfrom
Jah-yee:fix/spelling-typos-2026-11-06

Conversation

@Jah-yee

Copy link
Copy Markdown

Description

Fixes four spelling errors in debugpy's own (non-vendored) sources and test docs.

  • src/debugpy/common/messaging.py (line 1062): occured -> occurred, in the docstring that describes the message-handling error context
  • tests/timeline.md (line 104): succesful -> successful, in the note about the response body of a successful request
  • tests/timeline.md (line 115): sucessful -> successful, in the description of what request() returns on success
  • tests/pytest_fixtures.py (line 199): writen -> written, in the get_marked_line_numbers() docstring

All four occurrences are in comments and docstrings, so no runtime behaviour changes. The vendored src/debugpy/_vendored/pydevd/ tree is deliberately left untouched, since it is synced from upstream pydevd.

Changes

  • 3 files changed, 4 insertions(+), 4 deletions(-)

How to test

  • python -m py_compile src/debugpy/common/messaging.py tests/pytest_fixtures.py (passes)
  • pytest tests/test_timeline.py exercises the tests/timeline.md snippets; the change there is textual only

Fix four misspellings outside the vendored pydevd tree: 'occured' -> 'occurred' in src/debugpy/common/messaging.py, 'succesful'/'sucessful' -> 'successful' in tests/timeline.md, and 'writen' -> 'written' in tests/pytest_fixtures.py.
@Jah-yee
RoomWithOutRoof (Jah-yee) requested a review from a team as a code owner November 6, 2026 05:14
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

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.

1 participant