Merge ~paride/curtin:pylint-explicit-generated-members into curtin:master
Status: | Merged |
---|---|
Approved by: | Michael Hudson-Doyle |
Approved revision: | 101acb8c274c2de0e4f0a6758aa38bcc4813dca7 |
Merge reported by: | Server Team CI bot |
Merged at revision: | not available |
Proposed branch: | ~paride/curtin:pylint-explicit-generated-members |
Merge into: | curtin:master |
Diff against target: |
13 lines (+1/-1) 1 file modified
pylintrc (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Server Team CI bot | continuous-integration | Approve | |
Dan Bungert | Approve | ||
Review via email: mp+402652@code.launchpad.net |
Commit message
pylintrc: explicitly list the DISTROS generated-members
For some obscure reason setting
generated-
in pylintrc makes the pylint run flaky, causing failures like:
curtin/
E1101: Instance of 'Distros' has no 'debian' member (no-member)
curtin/
E1101: Instance of 'Distros' has no 'redhat' member (no-member)
These failures:
- happen on about 15% of the time, at least on Bionic
- also happen with the latest stable version of pylint (2.8.2)
- only happen on install_grub.py (which only refers to debian and redhat)
- do not seem to happen on Impish.
- possibly related: https:/
But the truth is I don't understand why generated-
even works some of the time for some generated members. Let's replace
it with the explicit list of the (non auto-detected) generated members,
so it will always work, and we'll know why it does.
See the commit message for rationale and reasoning.
I'd be very happy to amend the last paragraph if anybody can explain why
generated- members= DISTROS\ .
kind of works.