[Python-Dev] Summary of Python tracker Issues

2016-09-30 Thread Python tracker

ACTIVITY SUMMARY (2016-09-23 - 2016-09-30)
Python tracker at http://bugs.python.org/

To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.

Issues counts and deltas:
  open5519 (-11)
  closed 34555 (+70)
  total  40074 (+59)

Open issues with patches: 2381 


Issues opened (39)
==

#18235: _sysconfigdata.py wrong on AIX installations
http://bugs.python.org/issue18235  reopened by martin.panter

#19795: Formatting of True/False/None in docs
http://bugs.python.org/issue19795  reopened by serhiy.storchaka

#27665: Make create_server able to listen on several ports
http://bugs.python.org/issue27665  reopened by bayandin

#28259: Ctypes bug windows
http://bugs.python.org/issue28259  opened by PlatonAdCo

#28261: wrong error messages when using PyArg_ParseTuple to parse norm
http://bugs.python.org/issue28261  opened by Oren Milman

#28262: Header folder folds incorrectly causing MissingHeaderBodySepar
http://bugs.python.org/issue28262  opened by vincenttc

#28264: Python 3.4.4 Turtle library - Turtle.onclick events blocked by
http://bugs.python.org/issue28264  opened by George Fagin

#28267: [MinGW] Crash at start when compiled by MinGW for 64-bit Windo
http://bugs.python.org/issue28267  opened by vmurashev

#28269: [MinGW] Can't compile Python/dynload_win.c due to static strca
http://bugs.python.org/issue28269  opened by vmurashev

#28270: [MinGW] Can't compile Modules/posixmodule.c by MinGW - several
http://bugs.python.org/issue28270  opened by vmurashev

#28271: [MinGW] Can't compile _ctypes/callproc.c - SEH not supported b
http://bugs.python.org/issue28271  opened by vmurashev

#28272: a redundant check in maybe_small_long
http://bugs.python.org/issue28272  opened by Oren Milman

#28273: Make os.waitpid() option parameter optional.
http://bugs.python.org/issue28273  opened by StyXman

#28275: LZMADecompressor.decompress Use After Free
http://bugs.python.org/issue28275  opened by JohnLeitch

#28276: test_loading.py - false positive result for "def test_find" wh
http://bugs.python.org/issue28276  opened by Michael.Felt

#28277: ./Modules/_io/_iomodule.c build failure on AIX (beta1) while (
http://bugs.python.org/issue28277  opened by Michael.Felt

#28278: Make `weakref.WeakKeyDictionary.__repr__` meaningful
http://bugs.python.org/issue28278  opened by cool-RR

#28279: setuptools failing to read from setup.cfg only in Python 3.6
http://bugs.python.org/issue28279  opened by Roy Williams

#28280: Always return a list from PyMapping_Keys/PyMapping_Values/PyMa
http://bugs.python.org/issue28280  opened by serhiy.storchaka

#28281: Remove year limits from calendar
http://bugs.python.org/issue28281  opened by belopolsky

#28282: find_library("c") defers to find_msvcrt()
http://bugs.python.org/issue28282  opened by martin.panter

#28286: gzip guessing of mode is ambiguilous
http://bugs.python.org/issue28286  opened by serhiy.storchaka

#28287: Refactor subprocess.Popen to let a subclass handle IO asynchro
http://bugs.python.org/issue28287  opened by martius

#28288: Expose environment variable for Py_Py3kWarningFlag
http://bugs.python.org/issue28288  opened by Roy Williams

#28290: BETA report: Python-3.6 build messages to stderr: AIX and "not
http://bugs.python.org/issue28290  opened by Michael.Felt

#28291: urllib/urllib2 AbstractDigestAuthHandler locked to retried cou
http://bugs.python.org/issue28291  opened by secynic

#28292: Make Calendar.itermonthdates() behave consistently in edge cas
http://bugs.python.org/issue28292  opened by belopolsky

#28293: Don't completely dump the regex cache when full
http://bugs.python.org/issue28293  opened by rhettinger

#28294: HTTPServer server.py assumes sys.stderr != None
http://bugs.python.org/issue28294  opened by grismar

#28295: PyUnicode_AsUCS4 doc and impl conflict on exception
http://bugs.python.org/issue28295  opened by xiang.zhang

#28298: can't set big int-like objects to items in array 'Q', 'L' and 
http://bugs.python.org/issue28298  opened by Oren Milman

#28301: python3.4-config --extension-suffix reports '.cpython-34m.so'
http://bugs.python.org/issue28301  opened by DrLou

#28307: Accelerate 'string' % (value, ...) by using formatted string l
http://bugs.python.org/issue28307  opened by serhiy.storchaka

#28308: Accelerate 'string'.format(value, ...) by using formatted stri
http://bugs.python.org/issue28308  opened by serhiy.storchaka

#28309: Accelerate string.Template by using formatted string literals
http://bugs.python.org/issue28309  opened by serhiy.storchaka

#28312: Minor change - more direct hint re: multiple machine sizes and
http://bugs.python.org/issue28312  opened by Michael.Felt

#28314: ElementTree: Element.getiterator(tag) broken in 3.6
http://bugs.python.org/issue28314  opened by mitya57

#28315: incorrect "in ?" output in 'divide' example at "Defining Clean
http://bugs.python.org/issue28315  opened by viorel

#28317: Improve support of FORMAT_VALUE in dis
http://bugs.pyth

[Python-Dev] IMPORTANT: An extra week until 3.6.0b2, now 2016-10-10

2016-09-30 Thread Ned Deily
Thanks for all of your efforts in getting us to the beta phase of 3.6.0!  A 
large number of important features and a huge amount of code were committed 
just prior to the b1 feature freeze 3 weekends ago.  Not surprisingly, there 
were a number of bugs found and loose ends identified and, as a result, we've 
negotiated some extensions to get things in before b2.  Under the current 
schedule there were only 3 weeks between b1 and b2 and then 4 weeks between b2 
and b3; that was mainly because we pushed b1 back a week due to the development 
sprint.  I would *really* like for us to get those remaining pieces which were 
granted extensions into b2 as planned.  The longer they are delayed, the more 
risk it puts on the final steps of the release and it's really important to 
have a stable base for our testing efforts and those of our downstream users, 
like third-party developers and distributors.  So I think it makes sense to 
move b2 back a week, giving us all an extra week to get things in for b
 2.  Without changing the date for b3, we will now have 4 weeks between b1 and 
b2 and 3 weeks between b2 and b3.  That gives us about 10 days from now until 
b2.

It would be great if you can update the issue tracker for any exempted items 
you have.  I will try to followup with you, as needed, over the next few days 
on their status.  Please contact me if you have any questions about the 3.6.0 
schedule or about whether a change is appropriate for the beta phase.

To recap, the remaining milestones for 3.6.0:

2016-10-10, 1200 UTC: 3.6.0 beta 2 (was 10-03, remaining exempted features, bug 
and doc fixes)

2016-10-31: 3.6.0 beta 3 (bug and doc fixes)

2016-11-21: 3.6.0 beta 4 (important bug fixes and doc fixes)

2016-12-05 3.6.0 release candidate 1 (3.6.0 code freeze, critical bug fixes, 
doc fixes)

2016-12-16 3.6.0 release (3.6.0rc1 plus any necessary emergency fixes)


Thank you all again for your great efforts so far on 3.6!

--Ned

https://www.python.org/dev/peps/pep-0494/

--
  Ned Deily
  n...@python.org -- []

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