Version-Release number of selected component: pylint-2.3.1-1.fc30 Additional info: reporter: libreport-2.10.1 cmdline: /usr/bin/python3 /usr/bin/pylint -f text '--msg-template={path}:{line}:{column}:{C}: [{symbol}] {msg}' -r n '' crash_function: add_one_message exception_type: KeyError executable: /usr/bin/pylint interpreter: python3-3.7.3-3.fc30.x86_64 kernel: 5.1.16-300.fc30.x86_64 runlevel: N 5 type: Python3 uid: 1001 Truncated backtrace: utils.py:547:add_one_message:KeyError: None Traceback (most recent call last): File "/usr/bin/pylint", line 11, in <module> load_entry_point('pylint==2.3.1', 'console_scripts', 'pylint')() File "/usr/lib/python3.7/site-packages/pylint/__init__.py", line 20, in run_pylint Run(sys.argv[1:]) File "/usr/lib/python3.7/site-packages/pylint/lint.py", line 1628, in __init__ linter.check(args) File "/usr/lib/python3.7/site-packages/pylint/lint.py", line 943, in check self._do_check(files_or_modules) File "/usr/lib/python3.7/site-packages/pylint/lint.py", line 1057, in _do_check for descr in self.expand_files(files_or_modules): File "/usr/lib/python3.7/site-packages/pylint/lint.py", line 1099, in expand_files self.add_message(key, args=message) File "/usr/lib/python3.7/site-packages/pylint/utils.py", line 496, in add_message message_definition, line, node, args, confidence, col_offset File "/usr/lib/python3.7/site-packages/pylint/utils.py", line 547, in add_one_message self.stats["by_module"][self.current_name][msg_cat] += 1 KeyError: None Local variables in innermost frame: self: <pylint.lint.PyLinter object at 0x7fe34b4d54a8> message_definition: MessageDefinition:{'checker': <pylint.lint.PyLinter object at 0x7fe34b4d54a8>, 'msgid': 'F0001', 'msg': '%s', 'descr': 'Used when an error occurred preventing the analysis of a module (unable to find it for instance).', 'symbol': 'fatal', 'scope': 'line-based-msg', 'minversion': None, 'maxversion': None, 'old_names': []} line: None node: None args: 'No module named ' confidence: Confidence(name='UNDEFINED', description='Warning without any associated confidence level.') col_offset: None msgid: 'F0001' symbol: 'fatal' msg_cat: 'fatal'
Created attachment 1594092 [details] File: backtrace
Created attachment 1594093 [details] File: cgroup
Created attachment 1594094 [details] File: cpuinfo
Created attachment 1594095 [details] File: environ
Created attachment 1594096 [details] File: mountinfo
Created attachment 1594097 [details] File: namespaces
Created attachment 1594098 [details] File: open_fds
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.