py-pip, py-virtualenv: drop EOL pythons >= 3.4?

[jmroot (Joshua Root)]

Our current policy says:

The setuptools, pip and virtualenv modules should continue to be provided even for EOL Python versions, so that users who need them can still install modules.

However, Python 3.4 and later ship with both venv and ensurepip, which should be sufficient for this purpose. So while the 26 through 33 subports will remain necessary, I think it's probably OK to drop the later EOL versions as normal provided the subports have no dependents, i.e. 34, 35, 36, and 37 currently; and continue to do so for future versions as they go EOL.

Thoughts?

[reneeotten (Renee Otten)]

I am okay with dropping the subports for the EOL Python versions you mention as I agree one would still be able to install packages with the included libraries. In fact, I would be perfectly fine with also dropping them for Python 2.6 - 3.3 as really nobody should be using these Python versions anymore...

[jmroot (Joshua Root)]

The utility might be debatable for some of those versions, but 2.7 at least will, for better or worse, continue to be relevant for some time. All of these older ports are not there because you should use them, but because you might have to.

[jmroot (Joshua Root)]

In 589940a25e572afed166456d51a75ad169675f72/macports-ports (master):

py32-setuptools: restore as per policy

See: #68130

[jmroot (Joshua Root)]

In ba9ad22dcbc341db1f2acabafc635d8def1fe9a1/macports-ports (master):

py34-pip: delete subport

See: #68130

[jmroot (Joshua Root)]

In 4191425cd9b69fdc9015387ce1ca854450f6ec25/macports-ports (master):

py3{4,5,6}-virtualenv: delete, no dependents

See: #68130

[jmroot (Joshua Root)]

OK, I've updated the wiki. Technically as per the policy we should have py{26,32,33}-virtualenv, but it looks like a lot of deps would need to be (re)added, so let's just call this sufficiently fixed for the time being.