Thoughts,

• some version of setuptools/pip have added support to restrict installations by python version, https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/#python-requires
• and so we should be able to safely drop support for these minority languages
• are the last releases of pip+setuptools for py2.7 able to honor this variable?
• if we drop 2.7, we should also drop 3.5, from this graph from https://pypistats.org/packages/wcwidth

I am a strong believer in backporting and so on, having worked in many restrictive environments, I can sympathize with the small number of the tens of thousands of wcwidth downloads performed every day by python 2.7. And, though they should be version-pinning when working with such legacy software versions, there are cases where they are not.

The reason I held onto python 2 support so long was because it wasn't too difficult, we had found simple 2/3 switches that work in the codebase and the tests have provided nearly 100% coverage.

However I think a majority of the bugs of wcswidth calculations have been resolved, and python 2.7 users can now benefit from this. And that I cannot expect any python 2.7 users will want to make use of any new API's that are discussed in open issues. And for that reason, I am a proponent of dropping support of older python releases.