Pierre Sassoulas

The problem with the json score is fixed in pylint dev branch, but we can't put it in a 2.X version in order to not break compatibility. We might release...

We released [3.0.0a0 with the fix](https://pypi.org/project/pylint/3.0.0a0/), let me know if there is any problem.

I don't know what to look for in your stacktrace, what was the uncaught exception in pylint ? (By the way we released 3.0.0a1 because of a [problem with disabling...

Ok, let's debug it together then :) Can you open a pylint issue with the pylint command launched just before the crash and the code on which it was launched...

This issue is blocked by the json specification in pylint and the lack of progress on it (https://github.com/PyCQA/pylint/issues/4741). We need to implement that new json specification, and release a new...

Yeah, sorry I was not very clear. If it's a crash inside pylint the issue could be opened in https://github.com/PyCQA/pylint/issues. I would need the actual pylint command launched by `pylint-pycharm`...

The thing is we did not release this in 2.x version because having `--score=yes` would not output score. So breaking thing is expected when suddenly pylint output the score. It's...

Full disclosure I'm biased because I'm maintaining it, but ``astroid`` permits to infer values: ```python >>> import astroid >>> a = astroid.extract_node(''' ... import argparse ... ... parser = argparse.ArgumentParser()...

Hello, we already spent hundred of hours in this, as @DanielNoord can corroborate :smile: We're close to being able to activate mypy, probably not with ``--strict`` but astroid was not...

Reopening because I did not understand that the merge request was only illustrative