Can't autocomplete methods for `ProactorEventLoop`

[NewUserHa]

Environment data

• Pylance version: 2026.2.1
• OS and version: win10
• Python version: 3.13.11

Code Snippet

import asyncio
asyncio.get_running_loop().create_pipe_connection

Repro Steps

Expected behavior

the language server lists out all possible candidates for autocomplete in pop-up

Actual behavior

the asyncio.get_running_loop().create_pipe_connection exists, but pylance doesn't show it up.
it only showed inrrelative results.

Additional

Another issue: when follow definition of the asyncio.get_running_loop().connect_read_pipe, it jumped into the AbstractEventLoop.connect_read_pipe rather than the real BaseEventLoop.connect_read_pipe. This issue has existed for long time.
It seems pylance doesn't work really well for the asyncio standard library for some time.

[rchiodo]

I believe this is by design. The get_running_loop is actually implemented in C code so Pylance uses the typeshed for get_running_loop to get the type.

And AsyncEventLoop does not have create_pipe_connection. This would be an issue for the typeshed stubs to address. Pylance is doing the correct thing here.

[rchiodo]

You'd have to typecast the running loop to a ProactorEventLoop.

Like this:

[NewUserHa]

But none will use cast when asking for autocomplete in reality.
Since the actual type of the object is ProactorEventLoop in memory space, it could have use the that to calculate the autocomplete list,
rather than a Abstract Class.

[rchiodo]

Since the actual type of the object is ProactorEventLoop in memory space, it could have use the that to calculate the autocomplete list, rather than a Abstract Class.

Unfortunately, that isn't possible. Pylance is a static analyzer. It doesn't run any Python code. It only analyzes the python code to figure out types.