Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
warns about "return" and "return None" statements at the end of functions/methods. These statements are useless because None is the default return type if they are missing.
Please comment on this feature because there are 20+ existing test cases that break with it. I'd like to know how to "fix" the failing tests before updating documentation, etc.
however that leaves out the case where there is only one return statement at the end of the function body and it is either "return" or "return None". I am currently working with a legacy codebase which has many of these. For example
IMO this checker can still be beneficial to people, but probably needs to be better integrated with the