Bug 1483869 - false-positive report of the "stat" module move
Summary: false-positive report of the "stat" module move
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: pylint
Version: 26
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-22 07:37 UTC by Standa Laznicka
Modified: 2018-05-03 10:47 UTC (History)
4 users (show)

Fixed In Version: pylint-1.7.2-2.fc26
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-03 10:47:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Standa Laznicka 2017-08-22 07:37:23 UTC
Description of problem:
python2 pylint throws "bad-python3-import" warning on `import stat` lines in source codes

Version-Release number of selected component (if applicable):
python2-pylint-1.7.2-1.fc26.noarch

How reproducible:
Always

Steps to Reproduce:
1. Have a python source code with `import stat` line
2. Run pylint2 on it

Actual results (example):
ipaserver/install/dsinstance.py:30: [W1648(bad-python3-import), ] Module moved in Python 3)

Expected results:
No warning.

Additional info:
Fixed upstream: https://github.com/PyCQA/pylint/issues/1565

Comment 1 Standa Laznicka 2017-08-28 10:56:12 UTC
Added a few labels, this is blocking our CI in Fedora 26 and the fix is simple.

Comment 2 Fedora Update System 2017-08-31 20:50:42 UTC
pylint-1.7.2-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-d64f60d3bc

Comment 3 Fedora Update System 2017-08-31 20:53:16 UTC
pylint-1.7.2-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-2b69c91ef9

Comment 4 Fedora Update System 2017-09-02 22:25:34 UTC
pylint-1.7.2-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2017-09-03 19:53:03 UTC
pylint-1.7.2-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-d64f60d3bc

Comment 6 Fedora Update System 2017-09-30 06:10:28 UTC
pylint-1.7.2-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Christian Heimes 2017-10-19 13:13:50 UTC
For the record, the issue hasn't been fixed in upstreams' 1.7 branch yet. I requested a backport to have the issue fixed in 1.7.5. https://github.com/PyCQA/pylint/issues/1708

Comment 8 Fedora End Of Life 2018-05-03 08:32:38 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 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 '26'.

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 26 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 9 Christian Heimes 2018-05-03 10:47:56 UTC
Problem has been fixed in F27 and F28.


Note You need to log in before you can comment on or make changes to this bug.