Drop support for Python 3.2

[dstufft]

Pending discussion on pypa-dev.

[xavfernandez]

https://github.com/pypa/pip/blob/develop/.travis/run.sh#L57-L60 could probably go also

[xavfernandez]

This information seems useful.

[dstufft]

We weren't keeping it up to date (for instance, it didn't include Python 3.1 being dropped) and it's sort of a pain (for instance, right now I'd say "Python 3.2 was supported through 7.1.2", but if we release 7.1.3 then this needs updated). It also duplicates information that is already available in the change log.

[pfmoore]

Agreed. I'd prefer to keep this, and add that 3.2 was supported through v7. That way we have a record of what version people on older Pythons should use.

[dstufft]

@pfmoore Any reason that the record in CHANGES.txt is not sufficient?

[pfmoore]

@dstufft your comment came in while mine was being typed. That's a fair point. Maybe we just modify it to be a list of "support for Python X.Y was dropped in version Z"?

But agreed it's a bit of a pain. Happy for you to simply drop it and if I get the time I can trawl the changelogs and add back in a simpler summary.

[pfmoore]

Any reason that the record in CHANGES.txt is not sufficient?

Stop typing while I am! :-) Simply that here is a little more visible.

[dstufft]

Stop typing while I am! :-)

NO U

:D

[dstufft]

Good catch on missing the reference to 3.2 in .travis/run.sh.

[dstufft]

Gonna merge this, if anyone has complaints we can revert.

[yan12125]

An question: is there a chance to apply this commit in progress into _vendor, so that pip works on Python 3.2 again? Or I have to stick with pip < 8 for Python 3.2 support?

[RonnyPfannschmidt]

python 3.2 is not only end of life, but also has a considerable maintenance burden

pip intensely wants to avoid patching vendored libs, we want them unmodified

[yan12125]

pip works on Python 3.2 again?

So the answer is no?

python 3.2 is not only end of life

The 3.2 branch on CPython HG is not closed yet, and the 3.2 version tag is available on bugs.python.org, too. In fact I have posted a question to python-dev but got no response yet.

[pfmoore]

Correct, the answer is no.

Python 3.2 was in security fix mode until February 2016, but is now end of life. See https://docs.python.org/devguide/devcycle.html#summary - we don't remove old tags, so the fact that a tag is present means nothing.

[pfmoore]

You do of course have the option of applying the patch you mention to a local copy of pip, and maintaining that for yourself for however long you wish. It's just that pip itself won't apply that patch.

[yan12125]

Thanks. Existing Python 3.2 stuff as well as the delayed (or cancelled?) 3.2.7 release is quite confusing on deciding whether to support Python 3.2 or not.

[Ivoz]

@yan12125 if that commit is present in a future ( / current) pypi release of the progress package, then pip will likely eventually incorporate it when we update vendor libraries to their latest stable releases. What we don't do is manually include patches to the libraries under _vendor.

So you may find a future >=8.x release of pip works on python 3.2, purely incidentally (if this was the only 3.2 incompatability) - however absolutely no expectations should be made.

[yan12125]

Thanks for the detailed explanation and never mind. I've proposed to drop Python 3.2 support in our application.