In article <3Ykxmg1NdXzSKN@mail.python.org>, giampaolo.rodola <python-checkins@python.org> wrote:

http://hg.python.org/cpython/rev/88fadc0d7b20 changeset: 81498:88fadc0d7b20 branch: 3.3 parent: 81495:e1c81ab5ad97 user: Giampaolo Rodola' <g.rodola@gmail.com> date: Mon Jan 14 02:24:25 2013 +0100 summary: fix for previous commit related to issue 10527 which didn't have the intended effect as per http://bugs.python.org/issue10527#msg179895

In article <3YkxmM0JwNzSJb@mail.python.org>, giampaolo.rodola <python-checkins@python.org> wrote:

http://hg.python.org/cpython/rev/831f49cc00fc changeset: 81497:831f49cc00fc user: Giampaolo Rodola' <g.rodola@gmail.com> date: Mon Jan 14 02:24:05 2013 +0100 summary: fix for previous commit related to issue 10527 which didn't have the intended effect as per http://bugs.python.org/issue10527#msg179895

files: Lib/multiprocessing/connection.py | 48 +++++++++--------- Lib/test/test_multiprocessing.py | 2 +- 2 files changed, 26 insertions(+), 24 deletions(-)

It appears these two changesets were checked in independently rather than merging from branch 3.3 to default. As a result, the 3.3 branch is currently "open"; you'll see this as a +1 heads when doing a hg pull -u. A null merge needs to happen from 3.3 to default to close the 3.3 branch again. Giampaolo, can you take care of this? -- Ned Deily, nad@acm.org