-
-
Notifications
You must be signed in to change notification settings - Fork 49.6k
Description
Also related to #309
There are a lot of files that try to support both Python 2 and Python 3, with mixed results. Then there are some files using explicit Python 3.6 features (such as f-strings), which makes running all files under both Python 2 and Python 3 a bit yanky.
While we can probably make most of this work using backporting libraries (such as future-fstrings), we could start going through all of your files and drop Python 2 support entirely. As Python 2 reaches end of life January 1st 2020, this should be done at some point, sooner rather than later. Do you want us to, at least start, to do it while refactoring the test suite? If so, which versions of Python should be supported?
For this whole project to be tested in a unified manner, it must require certain versions of Python. We can do this job for you, when the test suites have been set up.