Drop support for python 3.2

[nichochar]

Our build tool has automatically updated pip and virtualenv, and these new versions have dropped support for python 3.2.

Googling around, I have found that a lot of people have dropped support of python 3.0, 3.1 and 3.2. This seems to be a common trend. Here are a few examples:

• Soco
• pip discussion about dropping support
• python3.2 lifecycle is up february 2017

I vote we drop support, but wanted to get a global view.
@jparise @cgordon any opinions here?

[jparise]

I agree. Let's drop it.

[nichochar]

Unfortunately, I misunderstood the problem. The question is actually whether we should (temporarily probably) drop support for pypy3. Indeed pypy3 is using a python version of 3.2, and virtualenv and pip have dropped support for it, breaking the CI of pymemcache.

It's a bit of a head scratcher. Ideally I could bump the python pypy3 is using to python 3.3 but I believe support for that isn't yet live. I have asked the pypy folks in IRC about this, and they said a pypy3 with python 3.3 is already in alpha.

I have a hard time knowing how many people are using the pypy3 version. Maybe we simply remove the test in CI for now, and add it back when the python 3.3 is supported?

I think this pip ticket is related

[nichochar]

Chatting with a guy on the IRC #pypy channel who is having the same issue (I think this may be common), a few notes:

• we suspect very little people are using both python 3.2 and pypy3(.2)
• the best solution is to figure out how to get travis to install the alpha pypy3(.3). Apparently there is a solution using tox-travis here at jsonschema

[nichochar]

Relevant travic-ci ticket, pasting the explanation of the bug:

tox tries to execute pypy3 if it exists (via factor pypy3) or fall back to using python.
Travis image for pypy3.3-5.2 has a pypy3 in the PATH, but it is pypy3-2.4.
If the wrong pypy3 is removed from the PATH, all works well.
If a correct pypy3 is put in the PATH ahead of the incorrect one, all works well.

[nichochar]

After looking into how different people solve this, it seems like the travis folks don't care about supporting pypy3 on different python interpreters. For now, I will deactivate the pypy3 integration testing, following influx-db-python and others.