python3.4 compatiblity

[spaceone]

python3.4 compatiblity

[spaceone]

Quoting you

By making the code exclusively Python 3.5+, I'm able to focus on the quality of the checks and re-use all the nice features of the new releases (check out pathlib) instead of wasting cycles on Unicode compatiblity, etc.

Unfortionately this makes your code not being usable by me. (I have no python 2.5 in the next X years when debian doesn't support this). Would you consider adding 3.4 compatibility?

[ambv]

I'm sorry but no. I don't have any spare cycles to support legacy versions of the language and test that they work. The async/await syntax introduced in 3.5 is a big deal to me. More importantly, bugbear requires Python 3.5 to be able to parse source code that uses 3.5+ syntax.

Would you consider building a 3.5 to use for your linting needs? It would literally take you less time to do that than to file this bug.

[spaceone]

Okay.

[spaceone]

(We are still on 2.7 and this will probably not change in the next 2 years). But okay, I think I will just check our code manually once when I set up a 3.5 environment.

[ambv]

flake8 is an external tool, you can keep it in an external virtual environment and just have it on PATH.