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
In this code above pylint on python 3.7 complains about not finding members:
##########Linting Output - pylint##########
************* Module issue
10,15,error,E1101:Module 'trio' has no 'open_nursery' member
17,4,error,E1101:Module 'trio' has no 'run' member
------------------------------------------------------------------
Your code has been rated at 1.67/10 (previous run: 1.67/10, +0.00)
The issue can obviously worked around by ignoring.
ipython finds both functions with code completion.
Also reported against pylint.
The text was updated successfully, but these errors were encountered:
Yes, this has come up a few times, and it's kind of both trio and pylint's fault: pylint is using imperfect heuristics to try to guess what members are exported from a module, and trio's exports are put together in a complicated way that pylint's heuristics don't work on. There are similar issues with other tools that try to analyze trio statically (like mypy, pycharm, etc.), rather than at runtime (like ipython).
Unfortunately we can't really fix all those tools, so we should change how trio does exports. We have an open issue for that: #542. No-one's started working on it yet, but I'm sure it will happen sometime... or if it's something you wanted to work on then speak up there or in chat and we can help you figure out how to get started.
This might not be a trio problem, I am aware of this:
In this code above pylint on python 3.7 complains about not finding members:
The issue can obviously worked around by ignoring.
ipython finds both functions with code completion.
Also reported against pylint.
The text was updated successfully, but these errors were encountered: