Python below 3.6 is failing various tests, and I don't see a compelling reason to keep supporting that in the next release. Python 2 was sunset over a year ago ( https://www.python.org/doc/sunset-python-2/ ). Thanks @RJTK for the suggestion.

Things we need to change to be able to do this

• Remove the tests below 3.5 from github workflow testing matrix
• Remove mentions of anything below python 3.6 in various metadata files (setup.py, etc)
• Remove the part of the publishing process that builds a python 2.x distribution

Things this will unlock

• Our CI will pass again
• We can use black to format the whole codebase once over chore(build): apply black formatting + CI step to main codebase #663
• We can add black to the CI process so people don't need to be manually checking/editing their code style chore(build): apply black formatting + CI step to main codebase #663

Users who are unable to migrate past python 2 can continue to use the current release of Tiingo (0.13.0). If this becomes an issue for anyone, please leave a note in this thread and we'll see if we can recommend an alternate solution.

Notes on the ecosystem moving along

• Our readthedocs build started failing recently, it's because the websockets client wasn't installable on Python 2. Upgrading to python 3 ( see https://readthedocs.org/projects/tiingo-python/builds/14476185/ )