Mikhail Golubev 63461fb262 PY-53671 Don't treat methods qualified with a module as unbound ...

While resolving an aliased method exported from a module, we might lose
the context that it was referenced via instance and hence its first "self"
parameter is already bound and doesn't need to be passed explicitly.
The reason is PyResolveUtil#doResolveQualifiedNameInScope (called in
PyTargetExpressionImpl.multiResolveAssignedValue) performs resolve
over qualified names saved in PSI stubs and returns plain PsiElements
(end results) that don't retain such information about their qualifiers.
QualifiedResolveResult can't be used there either because we don't keep
PyExpressions in PSI stubs. What's more, when later such function is referenced
via some module we consider it definitely unbound, even though a module cannot
possibly have a method as its immediate attribute. I changed the logic so that
we no longer consider referencing a method through a module as somehow affecting
its bound/unbound state.

GitOrigin-RevId: 17a6c3e5d43c088d0663ba54651004c8370d5eca

2022-07-19 15:06:06 +00:00

..

gen/com/jetbrains/python

PY-47974 Extracted isConsole() check

2021-04-07 22:34:57 +00:00

resources

PY-53611 Add support of Required and NotRequired TypedDict type specifications (PEP-655)

2022-06-21 20:29:34 +00:00

src/com/jetbrains

PY-53671 Don't treat methods qualified with a module as unbound

2022-07-19 15:06:06 +00:00

intellij.python.psi.impl.iml

add jdom to source code to modify and strip to our needs

2022-03-27 18:52:47 +00:00