Mailman 3 March 2014 - Python-Dev

Treating tokenize.Untokenizer as private
by Terry Reedy 31 Mar '14

31 Mar '14

I am working through the multiple bugs afflicting tokenize.untokenize, which is described in the tokenize doc and has an even longer docstring. While the function could be implemented as one 70-line function, it happens to be implemented as a 4-line wrapper for a completely undocumented (Untokenizer class with 4 methods. (It is unmentioned in the doc and there are currently no docstrings.) I view the class as a private implementation detail and would like to treat it as such, and perhaps even rename it _Untokenizer to make that clear. The issue arises in #9974. It appears that a fix may require the addition of an instance attribute or .add_whitespace parameter. If there is objection to treating the whole class as private, I would at least like to treat add_whitespace as the private helper that it is. There is no reason to call it directly except for testing. Otherwise, it could just as well have been left inline at the one call site. -- Terry Jan Reedy

3 4

collections.sortedtree
by Marko Rauhamaa 31 Mar '14

31 Mar '14

I have made a full implementation of a balanced tree and would like to know what the process is to have it considered for inclusion in Python 3. To summarize, the implementation closely parallels dict() features and resides in _collectionsmodule.c under the name collections.sortedtree. It uses solely the "<" operator to compare keys. I have chosen the AVL tree as an implementation technique. The views support a number of optional arguments: sorteddict.keys(reversed=False, start=unspecified, inclusive=True) The primary objective of having a balanced tree in the standard library is to support ordered access in an efficient manner. The typical applications would include timers (networking), aging (cache) and prefix patterns (routing). Marko

24 74

Making proxy types easier to write and maintain
by Antoine Pitrou 31 Mar '14

31 Mar '14

Hello, It is known to be cumbersome to write a proxy type that will correctly proxy all special methods (this has to be done manually on the type, since special methods are not looked up on the instance: a __getattr__ method would not work). Recently we've had reports of two stdlib types that forgot to implement some special methods: - weakref.proxy doesn't implement __reversed__: http://bugs.python.org/issue19359 - mock.MagicMock doesn't implement __truediv__: http://bugs.python.org/issue20968 In http://bugs.python.org/issue19359#msg213530 I proposed to introduce a "proxy protocol" (__proxy__ / tp_proxy) that would be used as a fallback by _PyObject_LookupSpecial to fetch the lookup target, i.e.: def _PyObject_LookupSpecial(obj, name): tp = type(obj) try: return getattr(tp, name) except AttributeError: return getattr(tp.tp_proxy(), name) What do you think? Regards Antoine.

8 14

freeze build slave
by "Martin v. Löwis" 31 Mar '14

31 Mar '14

I have created a buildbot configuration to test freeze. At the moment, it has only one builder: http://buildbot.python.org/all/waterfall?show=AMD64%20Ubuntu%20LTS%20Freeze… which currently fails as freeze doesn't actually work. The test itself works by first building Python in release mode, then installing it, then running freeze on a test program, then building the test programm (and ultimately running it). The question then is: how should that integrate with the rest of the builders? I can see three alternatives: A. (status quo) run the test on a selected subset of the Unix builders B. run the test on all Unix builders. C. integrate the test with the Unix regular Unix builder Evaluating these alternatives: B: pro: wider testing con: each such build takes the slave lock, so slaves will have to do one additional full build per commit (or two if the fix gets checked into 3.4 as well). In addition, each slave will need disk space for one additional build tree plus one Python installation, per branch. C: pro: compared to B, build time is reduced (need only to build once per branch); disk space is also reduced con: it would test a debug build, not a release build Regards, Martin

4 3

PyErr_ Fetch | Restore & friends
by Ethan Furman 29 Mar '14

29 Mar '14

I'm working on issue 1615 [1] and came up with this tidbit, which works [2], but not well enough: slot_tp_getattr_hook(PyObject *self, PyObject *name) { ... + PyObject *error_type, *error_value, *error_traceback; ... + /* if an AttributeError is set, save it and call getattr; if getattr + sets an AttributeError, discard it and return the original + AttributeError */ if (res == NULL && PyErr_ExceptionMatches(PyExc_AttributeError)) { + PyErr_Fetch(&error_type, &error_value, &error_traceback); res = call_attribute(self, getattr, name); + if (res == NULL && PyErr_ExceptionMatches(PyExc_AttributeError)) + PyErr_Restore(error_type, error_value, error_traceback); } So I tried adding in a second call to PyErr_Fetch and adding the original error as context, like so: if (res == NULL && PyErr_ExceptionMatches(PyExc_AttributeError)) { PyErr_Fetch(&ctx_error_type, &ctx_error_value, &ctx_error_traceback); res = call_attribute(self, getattr, name); if (res == NULL && PyErr_ExceptionMatches(PyExc_AttributeError)) { PyErr_Fetch(&error_type, &error_value, &error_traceback); PyException_SetContext(error_value, ctx_error_value); PyErr_Restore(error_type, error_value, error_traceback); } else { Py_DECREF(ctx_error_value); } Py_DECREF(ctx_error_type); Py_DECREF(ctx_error_traceback); } This bit of code won't even finish compiling. I am not sure if my understanding of references (and how these functions create/consume them) or my understanding of when and where to call PyErr_Fetch|Restore or PyException_SetContext is at fault, but I would greatly appreciate somebody correcting my understanding. :) -- ~Ethan~ [1] http://http://bugs.python.org/issue1615 [2] works as in everything compiles, but the resulting behavior introduces a new bug (the message of a 'raise AttributeError' in a __getattr__ is ignored).

2 2

Re: [Python-Dev] cpython: inspect.Signature: Add 'Signature.from_callable' classmethod. Closes #17373
by Antoine Pitrou 29 Mar '14

29 Mar '14

On Thu, 27 Mar 2014 17:12:02 +0100 (CET) yury.selivanov <python-checkins(a)python.org> wrote: > > + .. classmethod:: Signature.from_callable(obj) > + > + Return a :class:`Signature` (or its subclass) object for a given callable > + ``obj``. This method simplifies subclassing of :class:`Signature`: > + > + :: > + > + class MySignature(Signature): > + pass > + sig = MySignature.from_callable(min) > + assert isinstance(sig, MySignature) > + This needs a "versionadded" tag. Regards Antoine.

3 2

Fwd: shutdown concurrent.futures.ProcessPoolExecutor
by Giampaolo Rodola' 28 Mar '14

28 Mar '14

This is a follow up of: https://groups.google.com/forum/#!topic/python-tulip/91NCCqV4SFs According to the information I collected so far it seems it's not possible (or at least very hard) to cleanly shutdown a process pool and all its workers in case of KeyboardInterrupt / SIGINT. Literally, what I would like to do is this: - intercept SIGINT form the main process and/or from each worker process - send SIGINT to all workers - wait for them to finish with a timeout - finally exit Whereas it exists a solution based on multiprocessing: http://noswap.com/blog/python-multiprocessing-keyboardinterrupt ...concurrent.futures.ProcessPoolExecutor does not expose all the necessary bits to emulate it. By opening this thread I hope either to find a solution and document it or if it turns out that it is simply not possible to do this via concurrent.futures then discuss whether it's the case to expose more ProcessPoolExecutor APIs, because right now the interface it offers is pretty limited compared to multiprocessing.Pool: http://docs.python.org/3.5/library/multiprocessing.html#multiprocessing.poo… In particular, it won't let you pass an initializer function to pass to multiprocessing.Pool nor terminate() the process pool (only wait() for it). ---------- Forwarded message ---------- From: Guido van Rossum <guido(a)python.org> Date: Sat, Mar 29, 2014 at 12:05 AM Subject: Re: [python-tulip] How to cleanly shutdown the IO loop when using run_in_executor()? To: Giampaolo Rodola' <g.rodola(a)gmail.com> Cc: python-tulip <python-tulip(a)googlegroups.com> You're going to have to move the discussion to python-dev or the python issue tracker then. On Fri, Mar 28, 2014 at 4:02 PM, Giampaolo Rodola' <g.rodola(a)gmail.com>wrote: > > On Wed, Mar 26, 2014 at 7:35 PM, Guido van Rossum <guido(a)python.org>wrote: > >> Another thing to investigate might be how the executor creates the >> processes, and if anything happens to signals there. > > > After some further digging this seems to be related with the problem at > hand. > According to this: > http://noswap.com/blog/python-multiprocessing-keyboardinterrupt > ...it appears a feasible solution is to prevent workers to ever receive > KeyboardInterrupt and have the main process shutdown the pool via > pool.terminate() and finally pool.join(). > Unfortunately concurrent.futures.ProcessPoolExecutor does not expose all > the necessary bits to do that (multiprocessing.Pool(initializer=...) > argument and terminate() method). > > I also suspect that in order to emulate the suggested solution the > underlying Process instance should be daemonized, similarly to what > multiprocessing.Pool does: > > http://hg.python.org/cpython/file/3567d7ebd382/Lib/multiprocessing/pool.py#… > > I wonder whether concurrent.futures.ProcessPoolExecutor would be better > off exposing more APIs in order to facilitate tasks like these. > > > -- > Giampaolo - http://grodola.blogspot.com > > -- --Guido van Rossum (python.org/~guido) -- Giampaolo - http://grodola.blogspot.com

1 0

PEP 461: Adding % formatting to bytes and bytearray -- Request for Pronouncement
by Ethan Furman 28 Mar '14

28 Mar '14

Requesting pronouncement on PEP 461. Full text below. =============================================================================== PEP: 461 Title: Adding % formatting to bytes and bytearray Version: $Revision$ Last-Modified: $Date$ Author: Ethan Furman <ethan(a)stoneleaf.us> Status: Draft Type: Standards Track Content-Type: text/x-rst Created: 2014-01-13 Python-Version: 3.5 Post-History: 2014-01-14, 2014-01-15, 2014-01-17, 2014-02-22, 2014-03-25, 2014-03-27 Resolution: Abstract ======== This PEP proposes adding % formatting operations similar to Python 2's ``str`` type to ``bytes`` and ``bytearray`` [1]_ [2]_. Rationale ========= While interpolation is usually thought of as a string operation, there are cases where interpolation on ``bytes`` or ``bytearrays`` make sense, and the work needed to make up for this missing functionality detracts from the overall readability of the code. Motivation ========== With Python 3 and the split between ``str`` and ``bytes``, one small but important area of programming became slightly more difficult, and much more painful -- wire format protocols [3]_. This area of programming is characterized by a mixture of binary data and ASCII compatible segments of text (aka ASCII-encoded text). Bringing back a restricted %-interpolation for ``bytes`` and ``bytearray`` will aid both in writing new wire format code, and in porting Python 2 wire format code. Common use-cases include ``dbf`` and ``pdf`` file formats, ``email`` formats, and ``FTP`` and ``HTTP`` communications, among many others. Proposed semantics for ``bytes`` and ``bytearray`` formatting ============================================================= %-interpolation --------------- All the numeric formatting codes (``d``, ``i``, ``o``, ``u``, ``x``, ``X``, ``e``, ``E``, ``f``, ``F``, ``g``, ``G``, and any that are subsequently added to Python 3) will be supported, and will work as they do for str, including the padding, justification and other related modifiers (currently ``#``, ``0``, ``-``, `` `` (space), and ``+`` (plus any added to Python 3)). The only non-numeric codes allowed are ``c``, ``b``, ``a``, and ``s`` (which is a synonym for b). For the numeric codes, the only difference between ``str`` and ``bytes`` (or ``bytearray``) interpolation is that the results from these codes will be ASCII-encoded text, not unicode. In other words, for any numeric formatting code `%x`:: b"%x" % val is equivalent to:: ("%x" % val).encode("ascii") Examples:: >>> b'%4x' % 10 b' a' >>> b'%#4x' % 10 ' 0xa' >>> b'%04X' % 10 '000A' ``%c`` will insert a single byte, either from an ``int`` in range(256), or from a ``bytes`` argument of length 1, not from a ``str``. Examples:: >>> b'%c' % 48 b'0' >>> b'%c' % b'a' b'a' ``%b`` will insert a series of bytes. These bytes are collected in one of two ways: - input type supports ``Py_buffer`` [4]_? use it to collect the necessary bytes - input type is something else? use its ``__bytes__`` method [5]_ ; if there isn't one, raise a ``TypeError`` In particular, ``%b`` will not accept numbers nor ``str``. ``str`` is rejected as the string to bytes conversion requires an encoding, and we are refusing to guess; numbers are rejected because: - what makes a number is fuzzy (float? Decimal? Fraction? some user type?) - allowing numbers would lead to ambiguity between numbers and textual representations of numbers (3.14 vs '3.14') - given the nature of wire formats, explicit is definitely better than implicit ``%s`` is included as a synonym for ``%b`` for the sole purpose of making 2/3 code bases easier to maintain. Python 3 only code should use ``%b``. Examples:: >>> b'%b' % b'abc' b'abc' >>> b'%b' % 'some string'.encode('utf8') b'some string' >>> b'%b' % 3.14 Traceback (most recent call last): ... TypeError: b'%b' does not accept 'float' >>> b'%b' % 'hello world!' Traceback (most recent call last): ... TypeError: b'%b' does not accept 'str' ``%a`` will give the equivalent of ``repr(some_obj).encode('ascii', 'backslashreplace')`` on the interpolated value. Use cases include developing a new protocol and writing landmarks into the stream; debugging data going into an existing protocol to see if the problem is the protocol itself or bad data; a fall-back for a serialization format; or any situation where defining ``__bytes__`` would not be appropriate but a readable/informative representation is needed [6]_. Examples:: >>> b'%a' % 3.14 b'3.14' >>> b'%a' % b'abc' b"b'abc'" >>> b'%a' % 'def' b"'def'" Unsupported codes ----------------- ``%r`` (which calls ``__repr__`` and returns a ``str``) is not supported. Compatibility with Python 2 =========================== As noted above, ``%s`` is being included solely to help ease migration from, and/or have a single code base with, Python 2. This is important as there are modules both in the wild and behind closed doors that currently use the Python 2 ``str`` type as a ``bytes`` container, and hence are using ``%s`` as a bytes interpolator. However, ``%b`` should be used in new, Python 3 only code, so ``%s`` will immediately be deprecated, but not removed until the next major Python release. Proposed variations =================== It has been proposed to automatically use ``.encode('ascii','strict')`` for ``str`` arguments to ``%b``. - Rejected as this would lead to intermittent failures. Better to have the operation always fail so the trouble-spot can be correctly fixed. It has been proposed to have ``%b`` return the ascii-encoded repr when the value is a ``str`` (b'%b' % 'abc' --> b"'abc'"). - Rejected as this would lead to hard to debug failures far from the problem site. Better to have the operation always fail so the trouble-spot can be easily fixed. Originally this PEP also proposed adding format-style formatting, but it was decided that format and its related machinery were all strictly text (aka ``str``) based, and it was dropped. Various new special methods were proposed, such as ``__ascii__``, ``__format_bytes__``, etc.; such methods are not needed at this time, but can be visited again later if real-world use shows deficiencies with this solution. A competing PEP, ``PEP 460 Add binary interpolation and formatting`` [7]_, also exists. Objections ========== The objections raised against this PEP were mainly variations on two themes: - the ``bytes`` and ``bytearray`` types are for pure binary data, with no assumptions about encodings - offering %-interpolation that assumes an ASCII encoding will be an attractive nuisance and lead us back to the problems of the Python 2 ``str``/``unicode`` text model As was seen during the discussion, ``bytes`` and ``bytearray`` are also used for mixed binary data and ASCII-compatible segments: file formats such as ``dbf`` and ``pdf``, network protocols such as ``ftp`` and ``email``, etc. ``bytes`` and ``bytearray`` already have several methods which assume an ASCII compatible encoding. ``upper()``, ``isalpha()``, and ``expandtabs()`` to name just a few. %-interpolation, with its very restricted mini-language, will not be any more of a nuisance than the already existing methods. Some have objected to allowing the full range of numeric formatting codes with the claim that decimal alone would be sufficient. However, at least two formats (dbf and pdf) make use of non-decimal numbers. Footnotes ========= .. [1] http://docs.python.org/2/library/stdtypes.html#string-formatting .. [2] neither string.Template, format, nor str.format are under consideration .. [3] https://mail.python.org/pipermail/python-dev/2014-January/131518.html .. [4] http://docs.python.org/3/c-api/buffer.html examples: ``memoryview``, ``array.array``, ``bytearray``, ``bytes`` .. [5] http://docs.python.org/3/reference/datamodel.html#object.__bytes__ .. [6] https://mail.python.org/pipermail/python-dev/2014-February/132750.html .. [7] http://python.org/dev/peps/pep-0460/ Copyright ========= This document has been placed in the public domain. .. Local Variables: mode: indented-text indent-tabs-mode: nil sentence-end-double-space: t fill-column: 70 coding: utf-8 End:

3 3

ISO 8601 durations and datetime.timedelta
by Skip Montanaro 28 Mar '14

28 Mar '14

Andrew wrote: > I meant ISO 8601 syntax for "durations" [1]. That's exactly what I was referring to. Consider this session: >>> now = datetime.datetime.now() >>> now datetime.datetime(2014, 3, 28, 12, 4, 38, 517110) >>> then = now - datetime.timedelta(days=57, hours=12, minutes=12, seconds=12) >>> now datetime.datetime(2014, 3, 28, 12, 4, 38, 517110) >>> then datetime.datetime(2014, 1, 29, 23, 52, 26, 517110) so, the difference is: >>> now - then datetime.timedelta(57, 43932) Given that the timedelta has more than "a month's" worth of days, how would you describe it using the ISO8601 duration notation without referencing a specific point in time? Conversely, given your example, "P3Y6M4DT12H30M5S", how would you convert that into a timedelta without knowing which exact years and months this duration refers to? Timedelta objects are very precise beasts, which is almost certainly why they don't support "years" and "months" args in their constructors. This is why I said this deserved a separate topic. Probably on python-ideas. Skip

2 1

Summary of Python tracker Issues
by Python tracker 28 Mar '14

28 Mar '14

ACTIVITY SUMMARY (2014-03-21 - 2014-03-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: open 4534 (+23) closed 28324 (+51) total 32858 (+74) Open issues with patches: 2090 Issues opened (61) ================== #15968: Incorporate Tcl/Tk/Tix into the Windows build process http://bugs.python.org/issue15968 reopened by haypo #16047: Tools/freeze no longer works in Python 3 http://bugs.python.org/issue16047 reopened by lemburg #21013: server-specific SSL context configuration http://bugs.python.org/issue21013 opened by pitrou #21014: `1` => `True`; for tutorial docs http://bugs.python.org/issue21014 opened by SamuelMarks #21016: trace: $prefix and $exec_prefix improperly replaced on Fedora http://bugs.python.org/issue21016 opened by mathstuf #21018: [patch] added missing documentation about escaping characters http://bugs.python.org/issue21018 opened by Arun.Persaud #21019: PyMethodDef ml_name is char* instead of const char* http://bugs.python.org/issue21019 opened by h.venev #21020: PyMethodDef ml_doc is char* instead of const char* http://bugs.python.org/issue21020 opened by h.venev #21021: PyMemberDef name is char* instead of const char* http://bugs.python.org/issue21021 opened by h.venev #21022: PyMemberDef doc is char* instead of const char* http://bugs.python.org/issue21022 opened by h.venev #21023: PyTypeObject tp_name is char* instead of const char* http://bugs.python.org/issue21023 opened by h.venev #21024: PyTypeObject tp_doc is char* instead of const char* http://bugs.python.org/issue21024 opened by h.venev #21025: if check_hostname is true, context can't be used for server pu http://bugs.python.org/issue21025 opened by pitrou #21026: Document sitecustomize.py problems with pythonw http://bugs.python.org/issue21026 opened by terry.reedy #21027: difflib new cli interface http://bugs.python.org/issue21027 opened by Claudiu.Popa #21028: ElementTree objects should support all the same methods as Ele http://bugs.python.org/issue21028 opened by rhettinger #21029: IDLE mis-coloring "print" http://bugs.python.org/issue21029 opened by rhettinger #21030: pip usable only by administrators on Windows http://bugs.python.org/issue21030 opened by Christian.Ullrich #21031: [patch] Add AlpineLinux to the platform module's supported dis http://bugs.python.org/issue21031 opened by Elizacat #21032: Socket leak if HTTPConnection.getresponse() fails http://bugs.python.org/issue21032 opened by vadmium #21033: previous trace function still invoked after sys.settrace() http://bugs.python.org/issue21033 opened by xdegaye #21034: Python docs reference the Distribute package which has been de http://bugs.python.org/issue21034 opened by Jurko.Gospodnetić #21035: Python's HTTP server implementations hangs after 16.343 reques http://bugs.python.org/issue21035 opened by chobeiry #21037: add an AddressSanitizer build option http://bugs.python.org/issue21037 opened by neologix #21040: socketserver: use selectors module http://bugs.python.org/issue21040 opened by neologix #21041: pathlib.PurePath.parents rejects negative indexes http://bugs.python.org/issue21041 opened by akira #21042: ctypes.util.find_library() should return full pathname instead http://bugs.python.org/issue21042 opened by Hernan.Grecco #21044: tarfile does not handle file .name being an int http://bugs.python.org/issue21044 opened by seirl #21046: Document formulas used in statistics http://bugs.python.org/issue21046 opened by zach.ware #21047: html.parser.HTMLParser: convert_charrefs should become True by http://bugs.python.org/issue21047 opened by Arfrever #21048: Index 'as' in import and with statements http://bugs.python.org/issue21048 opened by terry.reedy #21052: Consider dropping ImportWarning for empty sys.path_hooks and s http://bugs.python.org/issue21052 opened by brett.cannon #21054: Improve indexing of syntax symbols http://bugs.python.org/issue21054 opened by terry.reedy #21055: Index (augmented) assignment symbols http://bugs.python.org/issue21055 opened by terry.reedy #21056: csv documentation is incorrect http://bugs.python.org/issue21056 opened by NRGunby #21057: TextIOWrapper does not support reading bytearrays or memoryvie http://bugs.python.org/issue21057 opened by nikratio #21059: idle_test.test_warning failure http://bugs.python.org/issue21059 opened by neologix #21060: Better error message for setup.py upload command without sdist http://bugs.python.org/issue21060 opened by eric.araujo #21061: Is contextlib.redirect_stdout reentrant or not? http://bugs.python.org/issue21061 opened by perey #21062: Evalute all import-related modules for best practices http://bugs.python.org/issue21062 opened by brett.cannon #21063: Touch up one-line descriptions of modules for module index http://bugs.python.org/issue21063 opened by brett.cannon #21066: The separate download version for the documentation doesn't wo http://bugs.python.org/issue21066 opened by Cristian.Baboi #21068: Make ssl.PROTOCOL_* an enum http://bugs.python.org/issue21068 opened by pitrou #21069: test_fileno of test_urllibnet intermittently fails when using http://bugs.python.org/issue21069 opened by dfarrell07 #21070: test_xmlrpc waits forever instead of reporting failure http://bugs.python.org/issue21070 opened by matejcik #21071: struct.Struct.format is bytes, but should be str http://bugs.python.org/issue21071 opened by zbysz #21072: Python docs and downloads not available for Egypt http://bugs.python.org/issue21072 opened by Leo.Butcher #21073: Py_ReprEnter potentially misbehaves during malformed thread st http://bugs.python.org/issue21073 opened by itaibn #21074: Too aggressive constant folding http://bugs.python.org/issue21074 opened by naoki #21075: fileinput should use stdin.buffer for "rb" mode http://bugs.python.org/issue21075 opened by brandon-rhodes #21076: Turn signal.SIG* constants into enums http://bugs.python.org/issue21076 opened by giampaolo.rodola #21077: Turtle Circle Speed 0 http://bugs.python.org/issue21077 opened by Garrett.Grimsley #21078: multiprocessing.managers.BaseManager.__init__'s "serializer" a http://bugs.python.org/issue21078 opened by yorik.sar #21079: EmailMessage.is_attachment == False if filename is present http://bugs.python.org/issue21079 opened by brandon-rhodes #21080: asyncio.subprocess: connect pipes of two programs http://bugs.python.org/issue21080 opened by haypo #21081: missing vietnamese codec TCVN 5712:1993 in Python http://bugs.python.org/issue21081 opened by progfou #21082: os.makedirs(exist_ok=True) is not thread-safe: umask is set te http://bugs.python.org/issue21082 opened by desrt #21083: Add get_content_disposition() to email.message.Message http://bugs.python.org/issue21083 opened by brandon-rhodes #21084: IDLE can't deal with characters above the range (U+0000-U+FFFF http://bugs.python.org/issue21084 opened by wjssz #21085: compile error Python3.3 on Cygwin http://bugs.python.org/issue21085 opened by dellair.jie #21086: Source with "# -*- coding: ASCII -*-" and UNIX EOL (\n) result http://bugs.python.org/issue21086 opened by Morten.Z Most recent 15 issues with no replies (15) ========================================== #21083: Add get_content_disposition() to email.message.Message http://bugs.python.org/issue21083 #21077: Turtle Circle Speed 0 http://bugs.python.org/issue21077 #21066: The separate download version for the documentation doesn't wo http://bugs.python.org/issue21066 #21062: Evalute all import-related modules for best practices http://bugs.python.org/issue21062 #21060: Better error message for setup.py upload command without sdist http://bugs.python.org/issue21060 #21055: Index (augmented) assignment symbols http://bugs.python.org/issue21055 #21054: Improve indexing of syntax symbols http://bugs.python.org/issue21054 #21048: Index 'as' in import and with statements http://bugs.python.org/issue21048 #21047: html.parser.HTMLParser: convert_charrefs should become True by http://bugs.python.org/issue21047 #21042: ctypes.util.find_library() should return full pathname instead http://bugs.python.org/issue21042 #21034: Python docs reference the Distribute package which has been de http://bugs.python.org/issue21034 #21033: previous trace function still invoked after sys.settrace() http://bugs.python.org/issue21033 #21032: Socket leak if HTTPConnection.getresponse() fails http://bugs.python.org/issue21032 #21031: [patch] Add AlpineLinux to the platform module's supported dis http://bugs.python.org/issue21031 #21029: IDLE mis-coloring "print" http://bugs.python.org/issue21029 Most recent 15 issues waiting for review (15) ============================================= #21082: os.makedirs(exist_ok=True) is not thread-safe: umask is set te http://bugs.python.org/issue21082 #21079: EmailMessage.is_attachment == False if filename is present http://bugs.python.org/issue21079 #21076: Turn signal.SIG* constants into enums http://bugs.python.org/issue21076 #21069: test_fileno of test_urllibnet intermittently fails when using http://bugs.python.org/issue21069 #21068: Make ssl.PROTOCOL_* an enum http://bugs.python.org/issue21068 #21063: Touch up one-line descriptions of modules for module index http://bugs.python.org/issue21063 #21057: TextIOWrapper does not support reading bytearrays or memoryvie http://bugs.python.org/issue21057 #21055: Index (augmented) assignment symbols http://bugs.python.org/issue21055 #21048: Index 'as' in import and with statements http://bugs.python.org/issue21048 #21044: tarfile does not handle file .name being an int http://bugs.python.org/issue21044 #21041: pathlib.PurePath.parents rejects negative indexes http://bugs.python.org/issue21041 #21040: socketserver: use selectors module http://bugs.python.org/issue21040 #21037: add an AddressSanitizer build option http://bugs.python.org/issue21037 #21034: Python docs reference the Distribute package which has been de http://bugs.python.org/issue21034 #21032: Socket leak if HTTPConnection.getresponse() fails http://bugs.python.org/issue21032 Top 10 most discussed issues (10) ================================= #20904: HAVE_PY_SET_53BIT_PRECISION for m68k http://bugs.python.org/issue20904 41 msgs #16047: Tools/freeze no longer works in Python 3 http://bugs.python.org/issue16047 24 msgs #21013: server-specific SSL context configuration http://bugs.python.org/issue21013 16 msgs #20210: Provide configure options to enable/disable Python modules and http://bugs.python.org/issue20210 15 msgs #21035: Python's HTTP server implementations hangs after 16.343 reques http://bugs.python.org/issue21035 14 msgs #21057: TextIOWrapper does not support reading bytearrays or memoryvie http://bugs.python.org/issue21057 11 msgs #21069: test_fileno of test_urllibnet intermittently fails when using http://bugs.python.org/issue21069 11 msgs #21079: EmailMessage.is_attachment == False if filename is present http://bugs.python.org/issue21079 11 msgs #20951: SSLSocket.send() returns 0 for non-blocking socket http://bugs.python.org/issue20951 8 msgs #21044: tarfile does not handle file .name being an int http://bugs.python.org/issue21044 8 msgs Issues closed (44) ================== #6676: expat parser throws Memory Error when parsing multiple files http://bugs.python.org/issue6676 closed by ned.deily #12209: Minor edits to faulthandler doc http://bugs.python.org/issue12209 closed by haypo #15971: Sporadic failure in test_dump_tracebacks_later_file (test_faul http://bugs.python.org/issue15971 closed by haypo #17373: Add inspect.Signature.from_callable() http://bugs.python.org/issue17373 closed by python-dev #17654: IDLE only customizes correctly for OS X when using framework b http://bugs.python.org/issue17654 closed by ned.deily #18456: Documentation for PyDict_Update is incorrect http://bugs.python.org/issue18456 closed by python-dev #19264: subprocess.Popen doesn't support unicode on Windows http://bugs.python.org/issue19264 closed by terry.reedy #19537: Fix misalignment in fastsearch_memchr_1char http://bugs.python.org/issue19537 closed by pitrou #19573: Fix the docstring of inspect.Parameter and the implementation http://bugs.python.org/issue19573 closed by python-dev #19818: tracemalloc: comments on the doc http://bugs.python.org/issue19818 closed by haypo #19995: %c, %o, %x, %X accept non-integer values instead of raising an http://bugs.python.org/issue19995 closed by ethan.furman #20145: unittest.assert*Regex functions should verify that expected_re http://bugs.python.org/issue20145 closed by r.david.murray #20163: ValueError: time data does not match format http://bugs.python.org/issue20163 closed by dellair.jie #20378: Implement `Signature.__repr__` http://bugs.python.org/issue20378 closed by python-dev #20633: SystemError: Parent module 'multiprocessing' not loaded, canno http://bugs.python.org/issue20633 closed by sbt #20668: Remove dependency on tests.txt when running test_asyncio suite http://bugs.python.org/issue20668 closed by python-dev #20726: inspect: Make Signature instances picklable http://bugs.python.org/issue20726 closed by python-dev #20816: inspect.getcallargs() attempts to iterate over None http://bugs.python.org/issue20816 closed by python-dev #20817: inspect.getcallargs() raises the wrong error if 3+ arguments a http://bugs.python.org/issue20817 closed by python-dev #20913: Standard Library documentation needs SSL security best practic http://bugs.python.org/issue20913 closed by pitrou #20935: Support building Python with Clang sanitizer rules http://bugs.python.org/issue20935 closed by neologix #20953: heap-buffer-overflow in obmalloc.c:987 http://bugs.python.org/issue20953 closed by neologix #20975: Python 3.4 build info wrong in code snippet http://bugs.python.org/issue20975 closed by python-dev #20980: In multiprocessing.pool, ExceptionWithTraceback should derive http://bugs.python.org/issue20980 closed by sbt #20990: pyflakes: undefined names, get_context() and main(), in multip http://bugs.python.org/issue20990 closed by sbt #20992: reading individual bytes of multiple binary files using the Py http://bugs.python.org/issue20992 closed by Tommy.Carstensen #20995: Use Better Default Ciphers for the SSL Module http://bugs.python.org/issue20995 closed by dstufft #21000: json.tool ought to have a help flag http://bugs.python.org/issue21000 closed by python-dev #21006: asyncio.docs : create_subprocess_exec example does not work on http://bugs.python.org/issue21006 closed by haypo #21015: support SSL_CTX_set_ecdh_auto on newer OpenSSLs http://bugs.python.org/issue21015 closed by pitrou #21017: Enable Debug Tix build on Windows http://bugs.python.org/issue21017 closed by zach.ware #21036: typo in hashtable API: _PY_HASHTABLE_ENTRY_DATA -> _Py_HASHTAB http://bugs.python.org/issue21036 closed by haypo #21038: test_epoll.TestEPoll.test_control_and_wait: remove extra asser http://bugs.python.org/issue21038 closed by haypo #21039: pathlib strips trailing slash http://bugs.python.org/issue21039 closed by pitrou #21043: Stop recommending CACert.org in the SSL documentation http://bugs.python.org/issue21043 closed by dstufft #21045: fix layout to generate documentation for Qt Assistant http://bugs.python.org/issue21045 closed by python-dev #21049: Flood of “ImportWarning: sys.meta_path is empty” after exc http://bugs.python.org/issue21049 closed by brett.cannon #21050: Failure to import win32api (from pywin32) http://bugs.python.org/issue21050 closed by theller #21051: incorrect utf-8 conversion with c api http://bugs.python.org/issue21051 closed by mark.dickinson #21053: Idle Crash with the ^ button http://bugs.python.org/issue21053 closed by ned.deily #21058: tempfile.NamedTemporaryFile leaks file descriptor when fdopen http://bugs.python.org/issue21058 closed by haypo #21064: Simple segfault http://bugs.python.org/issue21064 closed by ned.deily #21065: spam http://bugs.python.org/issue21065 closed by r.david.murray #21067: Support Multiple finally clauses. http://bugs.python.org/issue21067 closed by rhettinger

1 0