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
Originally reported by: Andrew Pennebaker (BitBucket: mcandre, GitHub: @mcandre?)
Most linters offer CLI syntax of linter
meaning lint all relevant files in a directory. Typically, users run linter ., to lint the current directory.
pylint rejects this for directories with no init.py, such as collections of standalone, one-off scripts. As a mitigation, we can use pylint *.py, but it would be nice to type pylint ., in keeping with conventional linter syntax.
Originally reported by: Andrew Pennebaker (BitBucket: mcandre, GitHub: @mcandre?)
Most linters offer CLI syntax of linter
meaning lint all relevant files in a directory. Typically, users run linter ., to lint the current directory.pylint rejects this for directories with no init.py, such as collections of standalone, one-off scripts. As a mitigation, we can use pylint *.py, but it would be nice to type pylint ., in keeping with conventional linter syntax.
The text was updated successfully, but these errors were encountered: