pep8 1.4 now supports reading configuration parameters from a 'pep8' section in tox.ini. That would let us get rid of the .pep8 files in the repositories and have all the tools configured in a single file.
Description
Description
Details
Details
- Reference
- bz53353
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | hashar | T114360 Remove packages pep8 / pylint and pyflakes from CI slaves | |||
Resolved | hashar | T55354 JJB: replace pyflakes / pep8 jobs with tox-jessie job | |||
Declined | hashar | T55353 migrate all .pep8 files content to setup.cfg / tox.ini | |||
Resolved | None | T46443 Jenkins: install tox on Precise labs instances | |||
Resolved | hashar | T106799 Pin tox to a specific version | |||
Resolved | None | T55352 upgrade pep8 from v1.3.3 to v1.4.5 | |||
Resolved | akosiaris | T54239 [OPS] backport pep8 v1.4+ from Saucy to Precise | |||
Resolved | awight | T114218 wikimedia/fundraising/tools should pass python lint checks (flake8) |
Event Timeline
Comment Actions
From a discussion we had with Bryan Davis, the flake8/pep8 configuration should be in setup.cfg.
Comment Actions
(In reply to Antoine "hashar" Musso from comment #2)
From a discussion we had with Bryan Davis, the flake8/pep8 configuration
should be in setup.cfg.
It was my understanding that flake8 and pep8 will not consider setup.cfg if there is a tox.ini file. Or will they?
Comment Actions
(In reply to Jean-Fred from comment #3)
It was my understanding that flake8 and pep8 will not consider setup.cfg if
there is a tox.ini file. Or will they?
Was apparently a bug in pep8 which got fixed with pep8 1.4.6. From its change log at https://pypi.python.org/pypi/pep8:
When both a tox.ini and a setup.cfg are present in the project directory, merge their contents. The tox.ini file takes precedence (same as before). (Issue #182)
Comment Actions
We are moving to tox/flake8 so most repos have the configuration done either in setup.cfg or tox.ini.