You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately the situation is unsatisfactory despite having PEP561 support. There are multiple unfixed issues involving underscored attributes and methods:
Underscored class names like _Element, _ElementTree are building blocks of lxml, which can't be lived without. Annotation of many function arguments become impossible without using them. But the degree of inconvenience introduced by bugs above seriously hinder UX of developers using lxml. It even induced well-intended yet unnecessary PR on types-lxml.
For now, putting to extreme, PyCharm should be avoided like plague until relevant bugs are fixed.
Vendor
JetBrains
OS
Windows, MacOS, Linux
PEP561 support
Yes
The text was updated successfully, but these errors were encountered:
Pyre-check
The support for PEP561 is new, so the current situation is still not fully evaluated. However some problems are immediately notable:
logging.LoggerAdapter
is a non-generic classcssselect
annotationPyType
Although not officially supported,
typeshed
has already been successfully using PyType in test suite by importingpytype.io.parse_pyi
.PyCharm
Unfortunately the situation is unsatisfactory despite having PEP561 support. There are multiple unfixed issues involving underscored attributes and methods:
Underscored class names like
_Element
,_ElementTree
are building blocks oflxml
, which can't be lived without. Annotation of many function arguments become impossible without using them. But the degree of inconvenience introduced by bugs above seriously hinder UX of developers usinglxml
. It even induced well-intended yet unnecessary PR ontypes-lxml
.For now, putting to extreme, PyCharm should be avoided like plague until relevant bugs are fixed.
The text was updated successfully, but these errors were encountered: