Bug 1613466

Summary: pylint tracebacks on code importing the dmidecode module
Product: [Fedora] Fedora Reporter: Ondřej Lysoněk <olysonek>
Component: pylintAssignee: Christian Dersch <lupinix.fedora>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 28CC: chad.schroeder, lupinix.fedora, orion
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:41:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
traceback none

Description Ondřej Lysoněk 2018-08-07 15:33:41 UTC 
Created attachment 1474033 [details]
traceback

Description of problem:
When running pylint on code which imports the dmidecode module, pylint crashes with a traceback.

Version-Release number of selected component (if applicable):
python3-pylint-1.7.5-1.fc28.noarch
python3-dmidecode-3.12.2-11.fc28.x86_64

How reproducible:
always

Steps to Reproduce:
1. yum install -y python3-dmidecode
2. cat > a.py << EOF
> import dmidecode
> EOF
3. pylint-3 a

Actual results:
pylint crashes with a traceback, see the attachment.

Expected results:
pylint does not crash

Additional info:
The dmidecode module as such seems to work fine.
Comment 1 Ondřej Lysoněk 2018-08-13 14:26:16 UTC 
This is rather unpleasant, as I'm now unable to check the module in our project that imports dmidecode with pylint.
Comment 2 Chad 2018-10-18 14:17:36 UTC 
I'm experiencing the same issue.
Comment 3 Ondřej Lysoněk 2019-02-19 14:31:18 UTC 
It appears to work now with python3-pylint-2.1.1-2.fc29.noarch and I don't need it in F28, so from my POV, we can close this.
Comment 4 Ben Cotton 2019-05-02 19:53:15 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.
Comment 5 Ben Cotton 2019-05-28 23:41:29 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.