Hi, so pip 8 is going to drop support for Python 3.2; setuptools 19 will drop support for it too.
This implies either pinning pip and setuptools in CI, or dropping support for 3.2 in things where CI depends on those tools. I know we don't specifically test or support 3.2 in OpenStack things ... but since we're a fairly big community of users of things I (help) maintain, I thought I'd check and see whether folk here have a need for 3.2 support - in higher level things. So... I'm sending this email to poll for folk that *need* support for 3.2, to see how widespread the impact of dropping support would be. (Obviously users can pin versions of the libraries that drop 3.2 - the older releases will still be on PyPI... ) If there isn't a hue and cry about this then I think it will make sense to drop support for Python 3.2 in mock, testtools, fixtures, testrepository, testscenarios, testresources, unittest2, traceback2 and linecache2 - generally everything :) -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
