Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Refactor asyncio tools tests to use structures from_remote_debugging directly #143955

Open
Assignees
johnslavik
Labels
testsTests in the Lib/test dirtype-refactorCode refactoring (with no changes in behavior)
@johnslavik

Description

@johnslavik

The asyncio tools use structures from the_remote_debugging module.

In tests we currently reimplement these structures:

FrameInfo=namedtuple('FrameInfo', ['funcname','filename','lineno'])
CoroInfo=namedtuple('CoroInfo', ['call_stack','task_name'])
TaskInfo=namedtuple('TaskInfo', ['task_id','task_name','coroutine_stack','awaited_by'])
AwaitedInfo=namedtuple('AwaitedInfo', ['thread_id','awaited_by'])

InGH-142394, the upstream structures from_remote_debugging were changed, but the reimplementations in the tests were not updated to match. This caused a regression fromGH-143952 to sneak in.

Let's use structures from_remote_debugging directly, as it is currently done intest_external_inspection, to prevent any further unnoticed discrepancies.

cc@pablogsal

Metadata

Metadata

Assignees

Labels

testsTests in the Lib/test dirtype-refactorCode refactoring (with no changes in behavior)

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2026 Movatter.jp