I'm updating the 2.7 release PEP with the following release dates 2.7.9rc1 Nov 22 2.7.9 final December 5 I expect PEPs 476 and 477 can be done by then? Given that 2.7.9 has had some large changes, having multiple rcs is not unlikely. Hopefully, we can get a final out by 2015, though.
On Oct 31, 2014, at 7:54 PM, Benjamin Peterson <benjamin@python.org> wrote:
I'm updating the 2.7 release PEP with the following release dates
2.7.9rc1 Nov 22 2.7.9 final December 5
I expect PEPs 476 and 477 can be done by then?
Given that 2.7.9 has had some large changes, having multiple rcs is not unlikely. Hopefully, we can get a final out by 2015, though.
Yes on PEP 477, the actual back porting is done, I’m just slacking on doing the tests because we used unittest.mock in 3.4. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
On 1 November 2014 09:59, Donald Stufft <donald@stufft.io> wrote:
On Oct 31, 2014, at 7:54 PM, Benjamin Peterson <benjamin@python.org> wrote:
I'm updating the 2.7 release PEP with the following release dates
2.7.9rc1 Nov 22 2.7.9 final December 5
I expect PEPs 476 and 477 can be done by then?
Given that 2.7.9 has had some large changes, having multiple rcs is not unlikely. Hopefully, we can get a final out by 2015, though.
Yes on PEP 477, the actual back porting is done, I’m just slacking on doing the tests because we used unittest.mock in 3.4.
mock is only a single file, so making it available to the Python 2.7 regression test suite as something like test._mock_backport sounds tolerable to me. Another challenge is that the functional tests (i.e. the ones that actually run pip from the bundled wheel file, rather than mocking it out) are in test_venv, since they rely on venv to provide a degree of isolation from the Python instance running the test suite. However, given that pip's own tests cover compatibility with the 2.x series, the Python 3 test suite covers the functional integration with ensurepip, and the mock-based tests for ensurepip cover the 2.7 backport itself, I think we still have an acceptable level of regression testing coverage, even without being able to backport the venv based functional tests. Regards, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Nov 1, 2014, at 8:05 AM, Nick Coghlan <ncoghlan@gmail.com> wrote:
On 1 November 2014 09:59, Donald Stufft <donald@stufft.io> wrote:
On Oct 31, 2014, at 7:54 PM, Benjamin Peterson <benjamin@python.org> wrote:
I'm updating the 2.7 release PEP with the following release dates
2.7.9rc1 Nov 22 2.7.9 final December 5
I expect PEPs 476 and 477 can be done by then?
Given that 2.7.9 has had some large changes, having multiple rcs is not unlikely. Hopefully, we can get a final out by 2015, though.
Yes on PEP 477, the actual back porting is done, I’m just slacking on doing the tests because we used unittest.mock in 3.4.
mock is only a single file, so making it available to the Python 2.7 regression test suite as something like test._mock_backport sounds tolerable to me.
Another challenge is that the functional tests (i.e. the ones that actually run pip from the bundled wheel file, rather than mocking it out) are in test_venv, since they rely on venv to provide a degree of isolation from the Python instance running the test suite.
However, given that pip's own tests cover compatibility with the 2.x series, the Python 3 test suite covers the functional integration with ensurepip, and the mock-based tests for ensurepip cover the 2.7 backport itself, I think we still have an acceptable level of regression testing coverage, even without being able to backport the venv based functional tests.
Ok. The actual delta between ensurepip in 3.4 and in 2.7.9 is quite small too. It’s really just removing things like def foo(*, bar=None) and tempfile.TemporaryDirectory. No logic changes, just syntax/helper stuff. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
participants (3)
-
Benjamin Peterson -
Donald Stufft -
Nick Coghlan