[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2016-10-21 - 2016-10-28)
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:
open5525 ( +1)
closed 34779 (+51)
total 40304 (+52)
Open issues with patches: 2398
Issues opened (36)
==
#5830: heapq item comparison problematic with sched's events
http://bugs.python.org/issue5830 reopened by serhiy.storchaka
#5996: abstract class instantiable when subclassing dict
http://bugs.python.org/issue5996 reopened by gvanrossum
#25002: Deprecate asyncore/asynchat
http://bugs.python.org/issue25002 reopened by serhiy.storchaka
#25152: venv documentation doesn't tell you how to specify a particula
http://bugs.python.org/issue25152 reopened by serhiy.storchaka
#28498: tk busy command
http://bugs.python.org/issue28498 opened by tkinter
#28499: Logging module documentation needs a rework.
http://bugs.python.org/issue28499 opened by Pierre Bousquie
#28501: [Patch] Make os.umask() optional
http://bugs.python.org/issue28501 opened by EdSchouten
#28502: [Patch] Make os.chdir() optional
http://bugs.python.org/issue28502 opened by EdSchouten
#28503: [Patch] '_crypt' module: fix implicit declaration of crypt(),
http://bugs.python.org/issue28503 opened by EdSchouten
#28506: Multiprocessing Pool starmap - struct.error: 'i' format requir
http://bugs.python.org/issue28506 opened by Justin Ting
#28512: PyErr_SyntaxLocationEx() and PyErr_SyntaxLocationObject() alwa
http://bugs.python.org/issue28512 opened by serhiy.storchaka
#28513: Document zipfile CLI
http://bugs.python.org/issue28513 opened by serhiy.storchaka
#28516: contextlib.ExitStack.__enter__ has trivial but undocumented be
http://bugs.python.org/issue28516 opened by walker.hale.iv
#28518: execute("begin immediate") throwing OperationalError
http://bugs.python.org/issue28518 opened by fschulze
#28519: Update pydoc tool to support generic types
http://bugs.python.org/issue28519 opened by levkivskyi
#28521: _PyEval_RequestCodeExtraIndex should return a globally valid i
http://bugs.python.org/issue28521 opened by jpe
#28522: can't make IDLEX work with python._pth and python-3.6.0b2
http://bugs.python.org/issue28522 opened by Big Stone
#28523: Idlelib.configdialog: use 'color' insteadof 'colour'
http://bugs.python.org/issue28523 opened by terry.reedy
#28524: Set default argument of logging.disable() to logging.CRITICAL
http://bugs.python.org/issue28524 opened by Al.Sweigart
#28528: Pdb.checkline()
http://bugs.python.org/issue28528 opened by takluyver
#28530: Howto detect if an object is of type os.DirEntry
http://bugs.python.org/issue28530 opened by stephan
#28531: Improve utf7 encoder memory usage
http://bugs.python.org/issue28531 opened by xiang.zhang
#28532: Show sys.version when -V option is supplied twice.
http://bugs.python.org/issue28532 opened by inada.naoki
#28533: Replace asyncore
http://bugs.python.org/issue28533 opened by Mariatta
#28534: Replace asynchat
http://bugs.python.org/issue28534 opened by Mariatta
#28536: Show the qualified name when a call fails
http://bugs.python.org/issue28536 opened by Ryan.Gonzalez
#28538: _socket module cross-compilation error on android-24
http://bugs.python.org/issue28538 opened by xdegaye
#28539: httplib/http.client HTTPConnection._set_hostport() regression
http://bugs.python.org/issue28539 opened by cfs-pure
#28540: math.degrees(sys.float_info.max) should throw an OverflowError
http://bugs.python.org/issue28540 opened by franciscouzo
#28541: Improve test coverage for json library - loading bytes
http://bugs.python.org/issue28541 opened by Eric Appelt
#28542: document cross compilation
http://bugs.python.org/issue28542 opened by xdegaye
#28543: Incomplete fast path codecs aliases in codecs doc
http://bugs.python.org/issue28543 opened by xiang.zhang
#28544: Implement asyncio.Task in C
http://bugs.python.org/issue28544 opened by yselivanov
#28546: Better explain setting pdb breakpoints
http://bugs.python.org/issue28546 opened by iank
#28547: Python to use Windows Certificate Store
http://bugs.python.org/issue28547 opened by Jean-Philippe Landry
#28548: http.server parse_request() bug and error reporting
http://bugs.python.org/issue28548 opened by barry
Most recent 15 issues with no replies (15)
==
#28548: http.server parse_request() bug and error reporting
http://bugs.python.org/issue28548
#28546: Better explain setting pdb breakpoints
http://bugs.python.org/issue28546
#28543: Incomplete fast path codecs aliases in codecs doc
http://bugs.python.org/issue28543
#28542: document cross compilation
http://bugs.python.org/issue28542
#28538: _socket module cross-compilation error on android-24
http://bugs.python.org/issue28538
#28534: Replace asynchat
http://bugs.python.org/issue28534
#28533: Replace asyncore
http://bugs.python.org/issue28533
#28532: Sh
[Python-Dev] Clarification for concurrent.futures.Future
The docs for this class state: "Future instances are created by Executor.submit() and should not be created directly except for testing." https://docs.python.org/3/library/concurrent.futures.html#future-objects We have a need for a thread-safe future type in our extension but this statement makes us hesitate to use it. We don't need the executor functionality. We can write our own future class easily enough, we're just wondering what the justification was for the limitations mentioned in the docs. Thanks, Mark Spruiell ZeroC, Inc. ___ 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
Re: [Python-Dev] Clarification for concurrent.futures.Future
It means that the API for setting results/exceptions is essentially private and may change. So if you use this you risk that your code will break randomly at some point in the future when you upgrade Python. ___ 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
[Python-Dev] Reminder: 3.6.0b3 snapshot 2016-10-31 12:00 UTC
The third, and next-to-last, beta snapshot planned for the 3.6 release cycle is coming up in a few days. With fewer than 7 weeks remaining until the 3.6.0 release, it is very important that we all focus on stability and correctness. Please try to make sure that all remaining non-doc issues associated with new features are addressed in b3. Any remaining 3.6 feature-related issues still open after b3 should be marked in the issue tracker as "release blocker" and *must* be addressed one way or another by b4, 11-21. All other non-critical bug fixes should also be checked in by b4. Only release critical and doc fixes will be allowed once we exit the beta phase. Please plan accordingly. Please contact me if you have any questions about the 3.6.0 schedule or about whether a change is appropriate at this point in the 3.6.0 cycle. To recap, the remaining milestones for 3.6.0: 2016-10-31, 1200 UTC: 3.6.0 beta 3 (feature fixes, bug fixes, 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, release 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 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
