Re: [Python-Dev] 2.7.9 schedule redux

2014-11-01 Thread Nick Coghlan
On 1 November 2014 09:59, Donald Stufft  wrote:
>
>> On Oct 31, 2014, at 7:54 PM, Benjamin Peterson  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   |   [email protected]   |   Brisbane, Australia
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] 2.7.9 schedule redux

2014-11-01 Thread Donald Stufft

> On Nov 1, 2014, at 8:05 AM, Nick Coghlan  wrote:
> 
> On 1 November 2014 09:59, Donald Stufft  wrote:
>> 
>>> On Oct 31, 2014, at 7:54 PM, Benjamin Peterson  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

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] problem with hg.python.org?

2014-11-01 Thread Terry Reedy

My normally dependable pull.bat script has 3 times given me this.

F:\Python\dev>hg --repository F:\Python\dev\5\py35 pull --verbose 
--config ui.merge=internal:merge ssh://[email protected]/cpython

pulling from ssh://[email protected]/cpython
searching for changes
all local heads known remotely
adding changesets
adding manifests
adding file changes
transaction abort!
rollback completed
abort: data/Doc/howto/webservers.rst.i@5f4ad429ae9f: unknown parent!
remote: Unable to write to standard output: The pipe is being closed.

Since I have no 'data/Doc/i@5f9f, I am guessing that the problem 
is not local.


--
Terry Jan Reedy

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] problem with hg.python.org?

2014-11-01 Thread Donald Stufft

> On Nov 1, 2014, at 10:37 PM, Terry Reedy  wrote:
> 
> My normally dependable pull.bat script has 3 times given me this.
> 
> F:\Python\dev>hg --repository F:\Python\dev\5\py35 pull --verbose --config 
> ui.merge=internal:merge ssh://[email protected]/cpython
> pulling from ssh://[email protected]/cpython
> searching for changes
> all local heads known remotely
> adding changesets
> adding manifests
> adding file changes
> transaction abort!
> rollback completed
> abort: data/Doc/howto/webservers.rst.i@5f4ad429ae9f: unknown parent!
> remote: Unable to write to standard output: The pipe is being closed.
> 
> Since I have no 'data/Doc/i@5f9f, I am guessing that the problem is 
> not local.
> 
> -- 
> Terry Jan Reedy
> 
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: 
> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io

The internet suggests trying hg verify, does that do anything?

---
Donald Stufft
PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] problem with hg.python.org?

2014-11-01 Thread Terry Reedy

On 11/1/2014 11:03 PM, Donald Stufft wrote:



On Nov 1, 2014, at 10:37 PM, Terry Reedy  wrote:



abort: data/Doc/howto/webservers.rst.i@5f4ad429ae9f: unknown parent!
remote: Unable to write to standard output: The pipe is being closed.



The internet suggests trying hg verify, does that do anything?


I should have though of that.  60+ integrity errors.  I am recloning.

--
Terry Jan Reedy

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com