setup.cfg: more_itertools dropped support for python 2.7 with release 6.0

[dankegel]

Fixes #10

Verified that with python 2.7 and 3.6.7, pip install --user -e . installed the expected compatible version of more-itertools.

[dankegel]

The failures are because the existing code isn't indented properly, and you can see the proper version of more-itertools getting installed now, so the failures are spurious with respect to this merge request.

[jaraco]

The failures are because the existing code isn't indented properly

Actually, tabs are allowed. The issue is with PyCQA/pycodestyle#836. I've merged the workaround and I'll close and re-open the PR to test against latest master.

[jaraco]

I think the proper fix is to use installers that recognize valid Python versions. Accepting this change implies that every other project that depends on more_itertools would need to do the same, and moreover every package that depends on every other package would need to do the same when the other package drops support for Python 3. Instead, the packaging infrastructure has put in place a means to declare and solicit packages associated with the correct Python versions. That's probably the best approach. Otherwise, there's a combinatorial explosion of these sorts of workarounds.

So I'm disinclined to accept it. Thoughts?

[jaraco]

As you can see, tests pass without this PR.

[jaraco]

After further consideration in the parent ticket, the change here and the changes that would imply if extended to the ecosystem are simply unsustainable. A more systemic approach is going to be needed, so let's avoid adding this band-aid here.

[dankegel]

Thanks for the review.