Closed
Bug 1432331
Opened 7 years ago
Closed 1 year ago
[flake8] Prevent external configuration from being picked up
Categories
(Developer Infrastructure :: Lint and Formatting, enhancement, P3)
Developer Infrastructure
Lint and Formatting
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ahal, Unassigned)
References
()
Details
If there is a global flake8 configuration, |mach lint -l flake8| will pick it up. This is bad because things will pass for developers locally, but potentially fail in CI. We should try to prevent external (outside of mozilla-central) configuration from being used.
Unfortunately flake8 makes this hard to do. There doesn't seem to be a way to provide multiple config files *and* ignore global ones. We can do one or the other, but not both. This leaves us with only two options that I can see:
1. Use a single global config file at the root of mozilla-central
2. Read the relevant configs outside of flake8, merge them, pass them back in as a single file
Option 1 means we can't have directory level config files (ironically, going this route would also allow us to switch flake8 to a blacklist instead of a whitelist). But it is a nice to have.
Option 2 seems like it would be do-able, but would add a decent amount of overhead and complexity.
Updated•7 years ago
|
Version: Version 3 → unspecified
Reporter | ||
Updated•7 years ago
|
Priority: -- → P3
Updated•7 years ago
|
Product: Testing → Firefox Build System
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
Updated•2 years ago
|
Severity: normal → S3
Comment 1•1 year ago
|
||
Flake8 is no longer used.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•