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
I have stub pyi files and pylint doesn't seem to be using them.
I have tried renaming them to py and deleting the pyd files and this mostly works. One specific problem with this technique though is that I see the error "assignment-from-no-return" on functions.
As an example, if my .pyi file - renamed to .py has the following: def getPlatform() -> str: ...
I see errors for "assignment-from-no-return" in other places for code like this: platform = infoModule.getPlatform()
Is there a better way of using stub pyi files?
Documentation for future user
I expected to see a section heading about using stubs in the help - or for the stubs to just be used and work.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Look like this one has better SEO but was created later. I'm going to close as duplicate and change the title of the other one. Thank you @DetachHead (Just curious are you participating in closember ?) !
Question
I have stub pyi files and pylint doesn't seem to be using them.
I have tried renaming them to py and deleting the pyd files and this mostly works. One specific problem with this technique though is that I see the error "assignment-from-no-return" on functions.
As an example, if my .pyi file - renamed to .py has the following:
def getPlatform() -> str: ...
I see errors for "assignment-from-no-return" in other places for code like this:
platform = infoModule.getPlatform()
Is there a better way of using stub pyi files?
Documentation for future user
I expected to see a section heading about using stubs in the help - or for the stubs to just be used and work.
Additional context
No response
The text was updated successfully, but these errors were encountered: