Claudiu Popa
Claudiu Popa
Yeah, this could be a fix for now, until we will have a proper one for pylint.
@tuukkamustonen We probably won't need to indicate that we're ignoring a _pylint_ or say a _flake8_ error. We can recognise our errors and hopefully other tools don't have an overlap...
@edran I don't understand what you mean. Are you referring to add a `pylint-` or `flake8-` prefix to the error codes? That unfortunately doesn't seem like a big of change...
Thanks @JulienPalard This hasn't been fixed yet but we'll get to it.
This looks like an issue that could be solved with better control flow inference, so that `pylint` could know that `all` could be either `None` or some other iterable value.
Thanks for that report @ncoghlan It's probably a separate issue which we can resolve easier with a brain transform https://github.com/PyCQA/astroid/tree/master/astroid/brain so it's probably better to move the report to a...
Thanks for the report folks!
Thanks for the report! I can reproduce it using your example. The issue stems from the fact that `using-constant-test` does not check that the result of the inference could have...
Thanks for the report.
I believe this is in issue with type comments parsing on Python 3.8: ``` In [3]: ast.parse(open('a.py').read(), type_comments=True) Traceback (most recent call last): File "/Users/claudiu/.pyenv/versions/3.8.1/lib/python3.8/site-packages/IPython/core/interactiveshell.py", line 3331, in run_code exec(code_obj,...