| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | test_py2_compat: Ignore error message positions | toonn | 2022-05-26 | 1 | -0/+6 |
| | | |||||
| * | test_py2_compat: Test f-string detection | toonn | 2022-02-05 | 1 | -0/+25 |
| | | |||||
| * | Trying to ban f-strings | toonn | 2022-02-05 | 1 | -0/+8 |
| | | |||||
| * | test_py2_compat: Message was renamed to MessageTest | toonn | 2022-02-05 | 1 | -7/+7 |
| | | |||||
| * | test_py2_compat: Test the new with-statement check | toonn | 2021-08-08 | 1 | -0/+26 |
| | | |||||
| * | py2_compat: Fix formatting for PEP8 | toonn | 2021-08-08 | 1 | -3/+3 |
| | | |||||
| * | py2_compat: Added check for with Popen | toonn | 2021-08-08 | 1 | -1/+19 |
| | | | | | | Popen objects became context managers after Python 3.2 so we can't use them as such without a wrapper. | ||||
| * | Fix test_py2_compat formatting | toonn | 2020-11-11 | 1 | -0/+1 |
| | | |||||
| * | Shortcut py2 incompatible pytest tests | toonn | 2020-11-11 | 1 | -0/+11 |
| | | | | | | | Three of our pytest tests aren't compatible with python 2 by returning early from these testcases and always making them pass, we avoid false negatives in CI results. | ||||
| * | Apply some PEP8 love to the pylint module and tests | toonn | 2020-07-05 | 2 | -20/+17 |
| | | |||||
| * | Implement python 2 compatibility checks | toonn | 2020-07-05 | 2 | -0/+286 |
| We have been stuck on pylint <2 for a long time now because it dropped some of the python 2 lints we rely on. We maintain compatibility with python 2.6+ and 3.5+ and a lack of lints makes especially the former much harder. Incompatibilities had already snuck in in the form of implicit format specs. By implementing a custom checker we can make sure this doesn't happen again. | |||||