It's been almost a year since 2.7.3, so it's time for another 2.7 bugfix release. 2013-02-02 - 2.7.4 release branch created; rc released 2013-02-16 - 2.7.4 released Does this work for you, Martin and Ned? -- Regards, Benjamin
In article
It's been almost a year since 2.7.3, so it's time for another 2.7 bugfix release.
2013-02-02 - 2.7.4 release branch created; rc released 2013-02-16 - 2.7.4 released
Does this work for you, Martin and Ned?
That works for me. There are also several pending issues that I want to get into 2.7.4 (and 3.2.4). That should be enough time to finish them. -- Ned Deily, nad@acm.org
On Sat, Jan 19, 2013 at 9:30 PM, Benjamin Peterson
It's been almost a year since 2.7.3, so it's time for another 2.7 bugfix release.
2013-02-02 - 2.7.4 release branch created; rc released 2013-02-16 - 2.7.4 released
The Cape Town Python User Group is having a Python Bug Day next weekend (26th & 27th January) [1]. If there any particular 2.7 bugs that need looking at please shout, otherwise we'll just work from the top of the list of 2.7 issues on the bug tracker. [1] http://ctpug.org.za/wiki/Sprint20130126 Schiavo Simon
On Sat, 2013-01-19 at 14:30 -0500, Benjamin Peterson wrote:
It's been almost a year since 2.7.3, so it's time for another 2.7 bugfix release.
2013-02-02 - 2.7.4 release branch created; rc released 2013-02-16 - 2.7.4 released
Does this work for you, Martin and Ned?
I have a pet issue that has a patch that requires application to the 2.7 branch, if anyone would be kind enough to do it: http://bugs.python.org/issue15881 It has already been applied to various 3.X branches. - C
Am 19.01.2013 20:30, schrieb Benjamin Peterson:
It's been almost a year since 2.7.3, so it's time for another 2.7 bugfix release.
2013-02-02 - 2.7.4 release branch created; rc released 2013-02-16 - 2.7.4 released
Does this work for you, Martin and Ned?
I would propose to sync this with 3.2.4 if there's no argument against it. Georg
There are crashers for which patches were proposed but do not reviewed yet: Issue #6083: Reference counting bug in PyArg_ParseTuple and PyArg_ParseTupleAndKeywords. Issue #7358: cStringIO not 64-bit safe. Issue #16137: Using time.asctime() with an array with negative tm_hour causes Python Crash. Issue #16686: audioop overflow issues. #8865 is reviewed but not committed.
2013/2/3 Serhiy Storchaka
There are crashers for which patches were proposed but do not reviewed yet:
Issue #6083: Reference counting bug in PyArg_ParseTuple and PyArg_ParseTupleAndKeywords.
Issue #7358: cStringIO not 64-bit safe.
Issue #16137: Using time.asctime() with an array with negative tm_hour causes Python Crash.
Issue #16686: audioop overflow issues.
#8865 is reviewed but not committed.
Thanks. In the future, this should be raised to "release blocker" priority to get my attention. -- Regards, Benjamin
Just to clarify, the release branch hasn't been created yet, correct?
- Nadeem
On Sun, Feb 3, 2013 at 3:38 PM, Benjamin Peterson
2013/2/3 Serhiy Storchaka
: There are crashers for which patches were proposed but do not reviewed yet:
Issue #6083: Reference counting bug in PyArg_ParseTuple and PyArg_ParseTupleAndKeywords.
Issue #7358: cStringIO not 64-bit safe.
Issue #16137: Using time.asctime() with an array with negative tm_hour causes Python Crash.
Issue #16686: audioop overflow issues.
#8865 is reviewed but not committed.
Thanks. In the future, this should be raised to "release blocker" priority to get my attention.
-- Regards, Benjamin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/nadeem.vawda%40gmail.com
On Sun, Feb 3, 2013 at 6:08 PM, Nadeem Vawda
Just to clarify, the release branch hasn't been created yet, correct?
It's by tag and no: http://hg.python.org/cpython/tags -Brett
- Nadeem
On Sun, Feb 3, 2013 at 3:38 PM, Benjamin Peterson
wrote: 2013/2/3 Serhiy Storchaka
: There are crashers for which patches were proposed but do not reviewed yet:
Issue #6083: Reference counting bug in PyArg_ParseTuple and PyArg_ParseTupleAndKeywords.
Issue #7358: cStringIO not 64-bit safe.
Issue #16137: Using time.asctime() with an array with negative tm_hour causes Python Crash.
Issue #16686: audioop overflow issues.
#8865 is reviewed but not committed.
Thanks. In the future, this should be raised to "release blocker" priority to get my attention.
-- Regards, Benjamin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/nadeem.vawda%40gmail.com
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org
participants (8)
-
Benjamin Peterson
-
Brett Cannon
-
Chris McDonough
-
Georg Brandl
-
Nadeem Vawda
-
Ned Deily
-
Serhiy Storchaka
-
Simon Cross