Codecov Report

Merging #190 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #190   +/-   ##
=====================================
  Coverage       0%     0%           
=====================================
  Files           1      1           
  Lines           1      1           
=====================================
  Misses          1      1

@0xInfection, would love to know the reasoning behind the confusion

@thomasrockhu, there are still many projects which run on Legacy Python. I wonder why you removed support for 2.x versions as unsupported.

@0xInfection, the reason for removing 2.6 testing support is based on pinning coverage and pytest. Given that 2.6.9 was released in October 2013 and has been officially retired, I felt that it wasn't worth continuing to support. Note of course, that 2.7 will still be tested.

However, you bring up a good point that we should be more transparent and communicative about these sort of changes. What would make this an easier transition for you?

Here's the pip installs for codecov from PyPI for February 2019:

Source: pypistats python_minor codecov --last-month # pip install pypistats

https://hugovk.github.io/drop-python/2.6/ shows that currently 255/360 of the most downloaded PyPI packages have already dropped Python 2.6

If you add python_requires='>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*', as an argument to setup() in setup.py, then pip will install the correct version for the user's running Python.

Make sure to use recent pip, setuptools and wheel when releasing to include the metadata in the package.