Coverage remained the same at ?% when pulling 7b09005 on twm:py2-setup-metadata into c7f0a80 on hamcrest:master.

Coverage remained the same at ?% when pulling fe00696 on twm:py2-setup-metadata into c7f0a80 on hamcrest:master.

Not quite the point; the 1.x series should support Python 2, not the other way around.

Not quite the point; the 1.x series should support Python 2, not the other way around.

python_requires corresponds to PEP 345's Requires-Python field:

This field specifies the Python version(s) that the distribution is guaranteed to be compatible with.
https://www.python.org/dev/peps/pep-0345/#requires-python

@twm's usage is correct.

Oh, I see: #130 (comment)

So should I retarget this at some other branch?

@markrwilliams I know their usage is correct, but it's not the right change.

@twm arguably yes, but honestly that needs to end up in the ball of commits that's gonna get yanked out and re-inserted into the 2.0 line. I'm inclined to let @brunns sort that stuff out and then see if this is still necessary then. If so, definitely re-target it there.

Okay, I'll leave it as-is for now. Let me know if there is anything I need to do. If it's obsolete feel free to close — I won't be offended. Thanks for PyHamcrest!

I'm pretty sure we want this on master, at least, so I'll merge it. We wouldn't want it on any Python 2 compatible releases, but any such release would have to be cut from a much older commit.