Mailman 3 May 2012 - Python-Dev

Re: [Python-Dev] cpython: #12586: add provisional email policy with new header parsing and folding.
by Georg Brandl 26 May '12

26 May '12

Am 26.05.2012 00:44, schrieb r.david.murray: > http://hg.python.org/cpython/rev/0189b9d2d6bc > changeset: 77148:0189b9d2d6bc > user: R David Murray <rdmurray(a)bitdance.com> > date: Fri May 25 18:42:14 2012 -0400 > summary: > #12586: add provisional email policy with new header parsing and folding. > > When the new policies are used (and only when the new policies are explicitly > used) headers turn into objects that have attributes based on their parsed > values, and can be set using objects that encapsulate the values, as well as > set directly from unicode strings. The folding algorithm then takes care of > encoding unicode where needed, and folding according to the highest level > syntactic objects. > > With this patch only date and time headers are parsed as anything other than > unstructured, but that is all the helper methods in the existing API handle. > I do plan to add more parsers, and complete the set specified in the RFC > before the package becomes stable. > > files: > Doc/library/email.policy.rst | 323 + > Lib/email/_encoded_words.py | 211 + > Lib/email/_header_value_parser.py | 2145 ++++++++ > Lib/email/_headerregistry.py | 456 + > Lib/email/_policybase.py | 12 +- > Lib/email/errors.py | 43 +- > Lib/email/generator.py | 11 +- > Lib/email/policy.py | 173 +- > Lib/email/utils.py | 7 + > Lib/test/test_email/__init__.py | 6 + > Lib/test/test_email/test__encoded_words.py | 187 + > Lib/test/test_email/test__header_value_parser.py | 2466 ++++++++++ > Lib/test/test_email/test__headerregistry.py | 717 ++ > Lib/test/test_email/test_generator.py | 170 +- > Lib/test/test_email/test_pickleable.py | 57 + > Lib/test/test_email/test_policy.py | 126 +- > 16 files changed, 6994 insertions(+), 116 deletions(-) > > > diff --git a/Doc/library/email.policy.rst b/Doc/library/email.policy.rst > --- a/Doc/library/email.policy.rst > +++ b/Doc/library/email.policy.rst > @@ -306,3 +306,326 @@ > ``7bit``, non-ascii binary data is CTE encoded using the ``unknown-8bit`` > charset. Otherwise the original source header is used, with its existing > line breaks and and any (RFC invalid) binary data it may contain. > + > + > +.. note:: > + > + The remainder of the classes documented below are included in the standard > + library on a :term:`provisional basis <provisional package>`. Backwards > + incompatible changes (up to and including removal of the feature) may occur > + if deemed necessary by the core developers. > + > + > +.. class:: EmailPolicy(**kw) > + > + This concrete :class:`Policy` provides behavior that is intended to be fully > + compliant with the current email RFCs. These include (but are not limited > + to) :rfc:`5322`, :rfc:`2047`, and the current MIME RFCs. > + > + This policy adds new header parsing and folding algorithms. Instead of > + simple strings, headers are custom objects with custom attributes depending > + on the type of the field. The parsing and folding algorithm fully implement > + :rfc:`2047` and :rfc:`5322`. > + > + In addition to the settable attributes listed above that apply to all > + policies, this policy adds the following additional attributes: > + > + .. attribute:: refold_source > + > + If the value for a header in the ``Message`` object originated from a > + :mod:`~email.parser` (as opposed to being set by a program), this > + attribute indicates whether or not a generator should refold that value > + when transforming the message back into stream form. The possible values > + are: > + > + ======== =============================================================== > + ``none`` all source values use original folding > + > + ``long`` source values that have any line that is longer than > + ``max_line_length`` will be refolded > + > + ``all`` all values are refolded. > + ======== =============================================================== > + > + The default is ``long``. > + > + .. attribute:: header_factory > + > + A callable that takes two arguments, ``name`` and ``value``, where > + ``name`` is a header field name and ``value`` is an unfolded header field > + value, and returns a string-like object that represents that header. A > + default ``header_factory`` is provided that understands some of the > + :RFC:`5322` header field types. (Currently address fields and date > + fields have special treatment, while all other fields are treated as > + unstructured. This list will be completed before the extension is marked > + stable.) > + > + The class provides the following concrete implementations of the abstract > + methods of :class:`Policy`: > + > + .. method:: header_source_parse(sourcelines) > + > + The implementation of this method is the same as that for the > + :class:`Compat32` policy. > + > + .. method:: header_store_parse(name, value) > + > + The name is returned unchanged. If the input value has a ``name`` > + attribute and it matches *name* ignoring case, the value is returned > + unchanged. Otherwise the *name* and *value* are passed to > + ``header_factory``, and the resulting custom header object is returned as > + the value. In this case a ``ValueError`` is raised if the input value > + contains CR or LF characters. > + > + .. method:: header_fetch_parse(name, value) > + > + If the value has a ``name`` attribute, it is returned to unmodified. > + Otherwise the *name*, and the *value* with any CR or LF characters > + removed, are passed to the ``header_factory``, and the resulting custom > + header object is returned. Any surrogateescaped bytes get turned into > + the unicode unknown-character glyph. > + > + .. method:: fold(name, value) > + > + Header folding is controlled by the :attr:`refold_source` policy setting. > + A value is considered to be a 'source value' if and only if it does not > + have a ``name`` attribute (having a ``name`` attribute means it is a > + header object of some sort). If a source value needs to be refolded > + according to the policy, it is converted into a custom header object by > + passing the *name* and the *value* with any CR and LF characters removed > + to the ``header_factory``. Folding of a custom header object is done by > + calling its ``fold`` method with the current policy. > + > + Source values are split into lines using :meth:`~str.splitlines`. If > + the value is not to be refolded, the lines are rejoined using the > + ``linesep`` from the policy and returned. The exception is lines > + containing non-ascii binary data. In that case the value is refolded > + regardless of the ``refold_source`` setting, which causes the binary data > + to be CTE encoded using the ``unknown-8bit`` charset. > + > + .. method:: fold_binary(name, value) > + > + The same as :meth:`fold` if :attr:`cte_type` is ``7bit``, except that > + the returned value is bytes. > + > + If :attr:`cte_type` is ``8bit``, non-ASCII binary data is converted back > + into bytes. Headers with binary data are not refolded, regardless of the > + ``refold_header`` setting, since there is no way to know whether the > + binary data consists of single byte characters or multibyte characters. > + > +The following instances of :class:`EmailPolicy` provide defaults suitable for > +specific application domains. Note that in the future the behavior of these > +instances (in particular the ``HTTP` instance) may be adjusted to conform even > +more closely to the RFCs relevant to their domains. > + > +.. data:: default > + > + An instance of ``EmailPolicy`` with all defaults unchanged. This policy > + uses the standard Python ``\n`` line endings rather than the RFC-correct > + ``\r\n``. > + > +.. data:: SMTP > + > + Suitable for serializing messages in conformance with the email RFCs. > + Like ``default``, but with ``linesep`` set to ``\r\n``, which is RFC > + compliant. > + > +.. data:: HTTP > + > + Suitable for serializing headers with for use in HTTP traffic. Like > + ``SMTP`` except that ``max_line_length`` is set to ``None`` (unlimited). > + > +.. data:: strict > + > + Convenience instance. The same as ``default`` except that > + ``raise_on_defect`` is set to ``True``. This allows any policy to be made > + strict by writing:: > + > + somepolicy + policy.strict > + > +With all of these :class:`EmailPolicies <.EmailPolicy>`, the effective API of > +the email package is changed from the Python 3.2 API in the following ways: > + > + * Setting a header on a :class:`~email.message.Message` results in that > + header being parsed and a custom header object created. > + > + * Fetching a header value from a :class:`~email.message.Message` results > + in that header being parsed and a custom header object created and > + returned. > + > + * Any custom header object, or any header that is refolded due to the > + policy settings, is folded using an algorithm that fully implements the > + RFC folding algorithms, including knowing where encoded words are required > + and allowed. > + > +From the application view, this means that any header obtained through the > +:class:`~email.message.Message` is a custom header object with custom > +attributes, whose string value is the fully decoded unicode value of the > +header. Likewise, a header may be assigned a new value, or a new header > +created, using a unicode string, and the policy will take care of converting > +the unicode string into the correct RFC encoded form. > + > +The custom header objects and their attributes are described below. All custom > +header objects are string subclasses, and their string value is the fully > +decoded value of the header field (the part of the field after the ``:``) > + > + > +.. class:: BaseHeader > + > + This is the base class for all custom header objects. It provides the > + following attributes: > + > + .. attribute:: name > + > + The header field name (the portion of the field before the ':'). > + > + .. attribute:: defects > + > + A possibly empty list of :class:`~email.errors.MessageDefect` objects > + that record any RFC violations found while parsing the header field. > + > + .. method:: fold(*, policy) > + > + Return a string containing :attr:`~email.policy.Policy.linesep` > + characters as required to correctly fold the header according > + to *policy*. A :attr:`~email.policy.Policy.cte_type` of > + ``8bit`` will be treated as if it were ``7bit``, since strings > + may not contain binary data. > + > + > +.. class:: UnstructuredHeader > + > + The class used for any header that does not have a more specific > + type. (The :mailheader:`Subject` header is an example of an > + unstructured header.) It does not have any additional attributes. > + > + > +.. class:: DateHeader > + > + The value of this type of header is a single date and time value. The > + primary example of this type of header is the :mailheader:`Date` header. > + > + .. attribute:: datetime > + > + A :class:`~datetime.datetime` encoding the date and time from the > + header value. > + > + The ``datetime`` will be a naive ``datetime`` if the value either does > + not have a specified timezone (which would be a violation of the RFC) or > + if the timezone is specified as ``-0000``. This timezone value indicates > + that the date and time is to be considered to be in UTC, but with no > + indication of the local timezone in which it was generated. (This > + contrasts to ``+0000``, which indicates a date and time that really is in > + the UTC ``0000`` timezone.) > + > + If the header value contains a valid timezone that is not ``-0000``, the > + ``datetime`` will be an aware ``datetime`` having a > + :class:`~datetime.tzinfo` set to the :class:`~datetime.timezone` > + indicated by the header value. > + > + A ``datetime`` may also be assigned to a :mailheader:`Date` type header. > + The resulting string value will use a timezone of ``-0000`` if the > + ``datetime`` is naive, and the appropriate UTC offset if the ``datetime`` is > + aware. > + > + > +.. class:: AddressHeader > + > + This class is used for all headers that can contain addresses, whether they > + are supposed to be singleton addresses or a list. > + > + .. attribute:: addresses > + > + A list of :class:`.Address` objects listing all of the addresses that > + could be parsed out of the field value. > + > + .. attribute:: groups > + > + A list of :class:`.Group` objects. Every address in :attr:`.addresses` > + appears in one of the group objects in the tuple. Addresses that are not > + syntactically part of a group are represented by ``Group`` objects whose > + ``name`` is ``None``. > + > + In addition to addresses in string form, any combination of > + :class:`.Address` and :class:`.Group` objects, singly or in a list, may be > + assigned to an address header. > + > + > +.. class:: Address(display_name='', username='', domain='', addr_spec=None): > + > + The class used to represent an email address. The general form of an > + address is:: > + > + [display_name] <username@domain> > + > + or:: > + > + username@domain > + > + where each part must conform to specific syntax rules spelled out in > + :rfc:`5322`. > + > + As a convenience *addr_spec* can be specified instead of *username* and > + *domain*, in which case *username* and *domain* will be parsed from the > + *addr_spec*. An *addr_spec* must be a properly RFC quoted string; if it is > + not ``Address`` will raise an error. Unicode characters are allowed and > + will be property encoded when serialized. However, per the RFCs, unicode is > + *not* allowed in the username portion of the address. > + > + .. attribute:: display_name > + > + The display name portion of the address, if any, with all quoting > + removed. If the address does not have a display name, this attribute > + will be an empty string. > + > + .. attribute:: username > + > + The ``username`` portion of the address, with all quoting removed. > + > + .. attribute:: domain > + > + The ``domain`` portion of the address. > + > + .. attribute:: addr_spec > + > + The ``username@domain`` portion of the address, correctly quoted > + for use as a bare address (the second form shown above). This > + attribute is not mutable. > + > + .. method:: __str__() > + > + The ``str`` value of the object is the address quoted according to > + :rfc:`5322` rules, but with no Content Transfer Encoding of any non-ASCII > + characters. > + > + > +.. class:: Group(display_name=None, addresses=None) > + > + The class used to represent an address group. The general form of an > + address group is:: > + > + display_name: [address-list]; > + > + As a convenience for processing lists of addresses that consist of a mixture > + of groups and single addresses, a ``Group`` may also be used to represent > + single addresses that are not part of a group by setting *display_name* to > + ``None`` and providing a list of the single address as *addresses*. > + > + .. attribute:: display_name > + > + The ``display_name`` of the group. If it is ``None`` and there is > + exactly one ``Address`` in ``addresses``, then the ``Group`` represents a > + single address that is not in a group. > + > + .. attribute:: addresses > + > + A possibly empty tuple of :class:`.Address` objects representing the > + addresses in the group. > + > + .. method:: __str__() > + > + The ``str`` value of a ``Group`` is formatted according to :rfc:`5322`, > + but with no Content Transfer Encoding of any non-ASCII characters. If > + ``display_name`` is none and there is a single ``Address`` in the > + ``addresses` list, the ``str`` value will be the same as the ``str`` of > + that single ``Address``. There's a lot of new stuff here: should have a versionadded? (Or do we need new markup for "provisional" stuff?) Georg

2 1

How to build a browser in Paython. cannot import webkit & object.
by Mr.T Beppu 26 May '12

26 May '12

I think that I will make a browser in Official Python (not MacPorts Python). What should I do in order to install Webkit for Official Python (not MacPorts Python) ? from tokyo Japan.

2 1

Re: [Python-Dev] [Python-checkins] peps: PEP 421 is implemented.
by Nick Coghlan 26 May '12

26 May '12

On Sat, May 26, 2012 at 5:14 PM, georg.brandl <python-checkins(a)python.org> wrote: > http://hg.python.org/peps/rev/cba34504163d > changeset: 4441:cba34504163d > user: Georg Brandl <georg(a)python.org> > date: Sat May 26 09:15:01 2012 +0200 > summary: > PEP 421 is implemented. Did you mean to move 405 instead? 421 is accepted, but not implemented yet. Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

1 0

Re: [Python-Dev] cpython: Implemented PEP 405 (Python virtual environments).
by Antoine Pitrou 26 May '12

26 May '12

On Sat, 26 May 2012 04:48:49 +0200 vinay.sajip <python-checkins(a)python.org> wrote: > +_sys_home = getattr(sys, '_home', None) > +if _sys_home and os.name == 'nt' and _sys_home.lower().endswith('pcbuild'): > + _sys_home = os.path.dirname(_sys_home) What about pcbuild/amd64? Does this work on 64-bit builds? > +_sys_home = getattr(sys, '_home', None) > +if _sys_home and os.name == 'nt' and _sys_home.lower().endswith('pcbuild'): > + _sys_home = os.path.dirname(_sys_home) Same question here. > +#!/usr/bin/env python I don't think there should be a shebang line in a test file. > +# > +# Copyright 2011 by Vinay Sajip. All Rights Reserved. > +# > +# Permission to use, copy, modify, and distribute this software and its > +# documentation for any purpose and without fee is hereby granted, > +# provided that the above copyright notice appear in all copies and that > +# both that copyright notice and this permission notice appear in > +# supporting documentation, and that the name of Vinay Sajip > +# not be used in advertising or publicity pertaining to distribution > +# of the software without specific, written prior permission. > +# VINAY SAJIP DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING > +# ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL > +# VINAY SAJIP BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR > +# ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER > +# IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT > +# OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Why the copyright boilerplate? > +# Use with a Python executable built from the Python fork at > +# > +# https://bitbucket.org/vinay.sajip/pythonv/ as follows: This needs to be updated. > +# You'll need an Internet connection (needed to download distribute_setup.py). > +# > +# The script will change to the environment's binary directory and run > +# > +# ./python distribute_setup.py [...] > +# This class will not be included in Python core; it's here for now to Well... either the comment should be fixed or the class removed. > + # XXX This option will be removed. > + # XXX This will be changed to EnvBuilder Same here. > diff --git a/Lib/venv/scripts/nt/pysetup3.exe b/Lib/venv/scripts/nt/pysetup3.exe > new file mode 100644 > index 0000000000000000000000000000000000000000..3f3c09ebc8e55f4ac3379041753cb34daef71892 > GIT binary patch What's this file and how was it compiled? Regards Antoine.

1 0

Accepting PEP 405 (Python Virtual Environments)
by Nick Coghlan 25 May '12

25 May '12

As the latest round of updates that Carl and Vinay pushed to the PEPs repo have addressed my few remaining questions, I am accepting PEP 405 for inclusion in Python 3.3. Thanks to all involved in working out the spec for what to model directly on virtualenv, and areas where cleaner solutions could be found given the power to tweak the behaviour of the core interpreter and the standard library. Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

3 3

doc change for weakref
by Ethan Furman 25 May '12

25 May '12

I'd like to make a slight doc change for weakref to state (more or less): weakrefs are not invalidated when the strong refs are gone, but rather when garbage collection reclaims the object Should this be accurate for all implementations, or should it be more along the lines of: weakrefs may be invalidated as soon as the strong refs are gone, but may last until garbage collection reclaims the object ~Ethan~

5 4

Re: [Python-Dev] sys.implementation
by Eric Snow 25 May '12

25 May '12

PEP 421 has reached a good place and I'd like to ask for pronouncement. Thanks! -eric

2 2

Volunteering to be PEP czar for PEP 421, sys.implementation
by Barry Warsaw 25 May '12

25 May '12

I've mentioned this in private to a few folks, with generally positive feedback. I am formally volunteering to be PEP czar for PEP 421, sys.implementation. If there are no objections in the next few days, I'll make it official. Cheers, -Barry

1 1

Rietveld update
by martin＠v.loewis.de 25 May '12

25 May '12

As some have probably noticed: I updated the Rietveld version that we use to the current code base. There have been a few incompatible changes (schema, GAE API) which I hope I resolved. If you find new problems, please report them to the meta tracker. Regards, Martin

1 0

Summary of Python tracker Issues
by Python tracker 25 May '12

25 May '12

ACTIVITY SUMMARY (2012-05-18 - 2012-05-25) 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 3440 ( +8) closed 23254 (+58) total 26694 (+66) Open issues with patches: 1455 Issues opened (44) ================== #11804: expat parser not xml 1.1 (breaks xmlrpclib) http://bugs.python.org/issue11804 reopened by xrg #14852: json and ElementTree parsers misbehave on streams containing m http://bugs.python.org/issue14852 opened by Frederick.Ross #14853: test_file.py depends on sys.stdin being unseekable http://bugs.python.org/issue14853 opened by gregory.p.smith #14854: faulthandler: fatal error with "SystemError: null argument to http://bugs.python.org/issue14854 opened by zbysz #14855: IPv6 support for logging.handlers http://bugs.python.org/issue14855 opened by cblp #14856: argparse: creating an already defined subparsers does not rais http://bugs.python.org/issue14856 opened by eacb #14857: Direct access to lexically scoped __class__ is broken in 3.3 http://bugs.python.org/issue14857 opened by ncoghlan #14858: 'pysetup create' off-by-one when choosing classification matur http://bugs.python.org/issue14858 opened by todddeluca #14869: imaplib erronously quotes atoms such as flags http://bugs.python.org/issue14869 opened by brightbyte #14870: Descriptions of os.utime() and os.utimensat() use wrong notati http://bugs.python.org/issue14870 opened by hynek #14871: Rewrite the command line parsers and actions system used in di http://bugs.python.org/issue14871 opened by eric.araujo #14873: Windows devguide: clarification for build errors due to missin http://bugs.python.org/issue14873 opened by valhallasw #14874: Faster charmap decoding http://bugs.python.org/issue14874 opened by storchaka #14876: IDLE highlighting theme does not preview with user-selected fo http://bugs.python.org/issue14876 opened by andrew.m #14877: No option to run bdist_wininst against newer msvc versions on http://bugs.python.org/issue14877 opened by Aaron.Staley #14878: send statement from PEP342 is poorly documented. http://bugs.python.org/issue14878 opened by Stephen.Lacy #14879: invalid docs for subprocess exceptions with shell=True http://bugs.python.org/issue14879 opened by techtonik #14880: csv.reader and .writer use wrong kwargs notation in 2.7 docs http://bugs.python.org/issue14880 opened by hynek #14881: multiprocessing.dummy craches when self._parent._children does http://bugs.python.org/issue14881 opened by Itay.Brandes #14882: Link/Compile Error on Sun Sparc Solaris10 with gcc3.4.3----pyt http://bugs.python.org/issue14882 opened by seeker77 #14886: json C vs pure-python implementation difference http://bugs.python.org/issue14886 opened by mmarkk #14892: 'import readline' hangs when launching with '&' on BSD and OS http://bugs.python.org/issue14892 opened by olivier-mattelaer #14893: Tutorial: Add function annotation example to function tutorial http://bugs.python.org/issue14893 opened by zach.ware #14894: distutils.LooseVersion fails to compare number and a word http://bugs.python.org/issue14894 opened by Natalia #14895: test_warnings.py EnvironmentVariableTests is a bad test http://bugs.python.org/issue14895 opened by tebeka #14897: struct.pack raises unexpected error message http://bugs.python.org/issue14897 opened by mesheb82 #14899: Naming conventions and guidelines for packages and namespace p http://bugs.python.org/issue14899 opened by benoitbryon #14900: cProfile does not take its result headers as sort arguments http://bugs.python.org/issue14900 opened by ArneBab #14901: Python Windows FAQ is Very Outdated http://bugs.python.org/issue14901 opened by michael.driscoll #14902: test_logging failed http://bugs.python.org/issue14902 opened by cblp #14903: dictobject infinite loop on 2.6.5 on 32-bit x86 http://bugs.python.org/issue14903 opened by Daniel.Farina #14904: test_unicode_repr_oflw (in test_bigmem) crashes http://bugs.python.org/issue14904 opened by pitrou #14905: zipimport.c needs to support namespace packages when no 'direc http://bugs.python.org/issue14905 opened by eric.smith #14906: rotatingHandler WindowsError http://bugs.python.org/issue14906 opened by jacuro #14907: SSL module cannot handle unicode filenames http://bugs.python.org/issue14907 opened by ms4py #14908: datetime.datetime should have a timestamp() method http://bugs.python.org/issue14908 opened by djc #14909: Fix incorrect use of *Realloc() and *Resize() http://bugs.python.org/issue14909 opened by kristjan.jonsson #14910: argparse: disable abbreviation http://bugs.python.org/issue14910 opened by jens.jaehrig #14911: generator.throw() documentation inaccurate http://bugs.python.org/issue14911 opened by kristjan.jonsson #14912: Pdb does not stop at a breakpoint after a restart command and http://bugs.python.org/issue14912 opened by xdegaye #14913: tokenize the source to manage Pdb breakpoints http://bugs.python.org/issue14913 opened by xdegaye #14914: pysetup installed distribute despite dry run option being spec http://bugs.python.org/issue14914 opened by ncoghlan #14915: pysetup may leave a package in a half-installed state http://bugs.python.org/issue14915 opened by ncoghlan #14916: PyRun_InteractiveLoop fails to run interactively when using a http://bugs.python.org/issue14916 opened by Kevin.Barry Most recent 15 issues with no replies (15) ========================================== #14916: PyRun_InteractiveLoop fails to run interactively when using a http://bugs.python.org/issue14916 #14915: pysetup may leave a package in a half-installed state http://bugs.python.org/issue14915 #14914: pysetup installed distribute despite dry run option being spec http://bugs.python.org/issue14914 #14913: tokenize the source to manage Pdb breakpoints http://bugs.python.org/issue14913 #14911: generator.throw() documentation inaccurate http://bugs.python.org/issue14911 #14910: argparse: disable abbreviation http://bugs.python.org/issue14910 #14909: Fix incorrect use of *Realloc() and *Resize() http://bugs.python.org/issue14909 #14906: rotatingHandler WindowsError http://bugs.python.org/issue14906 #14904: test_unicode_repr_oflw (in test_bigmem) crashes http://bugs.python.org/issue14904 #14900: cProfile does not take its result headers as sort arguments http://bugs.python.org/issue14900 #14874: Faster charmap decoding http://bugs.python.org/issue14874 #14871: Rewrite the command line parsers and actions system used in di http://bugs.python.org/issue14871 #14858: 'pysetup create' off-by-one when choosing classification matur http://bugs.python.org/issue14858 #14853: test_file.py depends on sys.stdin being unseekable http://bugs.python.org/issue14853 #14852: json and ElementTree parsers misbehave on streams containing m http://bugs.python.org/issue14852 Most recent 15 issues waiting for review (15) ============================================= #14913: tokenize the source to manage Pdb breakpoints http://bugs.python.org/issue14913 #14909: Fix incorrect use of *Realloc() and *Resize() http://bugs.python.org/issue14909 #14900: cProfile does not take its result headers as sort arguments http://bugs.python.org/issue14900 #14899: Naming conventions and guidelines for packages and namespace p http://bugs.python.org/issue14899 #14895: test_warnings.py EnvironmentVariableTests is a bad test http://bugs.python.org/issue14895 #14893: Tutorial: Add function annotation example to function tutorial http://bugs.python.org/issue14893 #14876: IDLE highlighting theme does not preview with user-selected fo http://bugs.python.org/issue14876 #14874: Faster charmap decoding http://bugs.python.org/issue14874 #14873: Windows devguide: clarification for build errors due to missin http://bugs.python.org/issue14873 #14856: argparse: creating an already defined subparsers does not rais http://bugs.python.org/issue14856 #14855: IPv6 support for logging.handlers http://bugs.python.org/issue14855 #14854: faulthandler: fatal error with "SystemError: null argument to http://bugs.python.org/issue14854 #14843: support define_macros / undef_macros in setup.cfg http://bugs.python.org/issue14843 #14840: Tutorial: Add a bit on the difference between tuples and lists http://bugs.python.org/issue14840 #14837: Better SSL errors http://bugs.python.org/issue14837 Top 10 most discussed issues (10) ================================= #14814: Implement PEP 3144 (the ipaddress module) http://bugs.python.org/issue14814 15 msgs #14775: Dict untracking can result in quadratic dict build-up http://bugs.python.org/issue14775 12 msgs #14855: IPv6 support for logging.handlers http://bugs.python.org/issue14855 11 msgs #11804: expat parser not xml 1.1 (breaks xmlrpclib) http://bugs.python.org/issue11804 7 msgs #12014: str.format parses replacement field incorrectly http://bugs.python.org/issue12014 7 msgs #14744: Use _PyUnicodeWriter API in str.format() internals http://bugs.python.org/issue14744 7 msgs #14854: faulthandler: fatal error with "SystemError: null argument to http://bugs.python.org/issue14854 7 msgs #14886: json C vs pure-python implementation difference http://bugs.python.org/issue14886 6 msgs #14894: distutils.LooseVersion fails to compare number and a word http://bugs.python.org/issue14894 6 msgs #1191964: asynchronous Subprocess http://bugs.python.org/issue1191964 6 msgs Issues closed (54) ================== #4033: python search path - .pth recursion http://bugs.python.org/issue4033 closed by brett.cannon #9374: urlparse should parse query and fragment for arbitrary schemes http://bugs.python.org/issue9374 closed by orsenthil #9400: multiprocessing.pool.AsyncResult.get() messes up exceptions http://bugs.python.org/issue9400 closed by sbt #11647: function decorated with a context manager can only be invoked http://bugs.python.org/issue11647 closed by ncoghlan #12098: Child process running as debug on Windows http://bugs.python.org/issue12098 closed by sbt #13152: textwrap: support custom tabsize http://bugs.python.org/issue13152 closed by hynek #13208: Problems with urllib on windows http://bugs.python.org/issue13208 closed by holdenweb #13210: Support Visual Studio 2010 http://bugs.python.org/issue13210 closed by loewis #13445: Enable linking the module pysqlite with Berkeley DB SQL instea http://bugs.python.org/issue13445 closed by petri.lehtinen #13585: Add contextlib.ExitStack http://bugs.python.org/issue13585 closed by python-dev #13682: Documentation of os.fdopen() refers to non-existing bufsize ar http://bugs.python.org/issue13682 closed by petri.lehtinen #14072: urlparse on tel: URI-s misses the scheme in some cases http://bugs.python.org/issue14072 closed by ezio.melotti #14075: argparse: unused method? http://bugs.python.org/issue14075 closed by petri.lehtinen #14136: Simplify PEP 409 command line test and move it to test_cmd_lin http://bugs.python.org/issue14136 closed by python-dev #14426: date format problem in Cookie/http.cookies http://bugs.python.org/issue14426 closed by orsenthil #14472: .gitignore is outdated http://bugs.python.org/issue14472 closed by petri.lehtinen #14494: __future__.py and its documentation claim absolute imports bec http://bugs.python.org/issue14494 closed by petri.lehtinen #14572: 2.7.3: sqlite module does not build on centos 5 and Mac OS X 1 http://bugs.python.org/issue14572 closed by ned.deily #14588: PEP 3115 compliant dynamic class creation http://bugs.python.org/issue14588 closed by python-dev #14660: Implement PEP 420: Implicit Namespace Packages http://bugs.python.org/issue14660 closed by eric.smith #14721: httplib doesn't specify content-length header for POST request http://bugs.python.org/issue14721 closed by orsenthil #14798: pyclbr raises KeyError when the prefix of a dotted name is not http://bugs.python.org/issue14798 closed by petri.lehtinen #14804: Wrong defaults args notation in docs http://bugs.python.org/issue14804 closed by hynek #14821: _ctypes and other modules not built with msbuild on vs2010 sol http://bugs.python.org/issue14821 closed by jason.coombs #14822: Build unusable when compiled for Win 64-bit release http://bugs.python.org/issue14822 closed by jason.coombs #14831: make r argument on itertools.combinations() optional http://bugs.python.org/issue14831 closed by terry.reedy #14833: Copyright date in footer of /pypi says 2011 http://bugs.python.org/issue14833 closed by terry.reedy #14836: Add next(iter(o)) to set.pop, dict.popitem entries. http://bugs.python.org/issue14836 closed by rhettinger #14838: IDLE Will not load on reinstall http://bugs.python.org/issue14838 closed by loewis #14842: Link to function time() in the docs point to the time module http://bugs.python.org/issue14842 closed by python-dev #14849: C implementation of ElementTree: Inheriting from Element break http://bugs.python.org/issue14849 closed by eli.bendersky #14851: Python-2.6.8 install fails due to missing files http://bugs.python.org/issue14851 closed by ned.deily #14859: Patch to make IDLE window rise to top in OS X on launch http://bugs.python.org/issue14859 closed by ned.deily #14860: devguide: Clarify how to run cpython test suite - esp. on 2.7 http://bugs.python.org/issue14860 closed by ezio.melotti #14861: Make ./python -m test work to run test suite in Python 2.7 http://bugs.python.org/issue14861 closed by loewis #14862: os.__all__ is missing some names http://bugs.python.org/issue14862 closed by petri.lehtinen #14863: Update docs of os.fdopen() http://bugs.python.org/issue14863 closed by petri.lehtinen #14864: Mention logging.disable(logging.NOTSET) to reset the command i http://bugs.python.org/issue14864 closed by python-dev #14865: #doctest: directives removed from doctest chapter examples http://bugs.python.org/issue14865 closed by terry.reedy #14866: 2.x,3.x iOS static build: Fatal Python error: exceptions boots http://bugs.python.org/issue14866 closed by amaury.forgeotdarc #14867: chm link missing from 2.7.3 download page http://bugs.python.org/issue14867 closed by ned.deily #14868: Allow log calls to return True for code optimization. http://bugs.python.org/issue14868 closed by Lluís #14872: subprocess is not safe from deadlocks http://bugs.python.org/issue14872 closed by rosslagerwall #14875: Unusual way of doing 'Inf' in json library http://bugs.python.org/issue14875 closed by ezio.melotti #14883: html documentation does not show comments in code blocks http://bugs.python.org/issue14883 closed by ezio.melotti #14884: Windows Build instruction typo http://bugs.python.org/issue14884 closed by eli.bendersky #14885: shutil tests, test_copy2_xattr and test_copyxattr, fail http://bugs.python.org/issue14885 closed by hynek #14887: pysetup: unfriendly error message for unknown commands http://bugs.python.org/issue14887 closed by eric.araujo #14888: _md5 module crashes on large data http://bugs.python.org/issue14888 closed by pitrou #14889: PyBytes_FromObject(bytes_object) creates a new object http://bugs.python.org/issue14889 closed by larry #14890: typo in difflib http://bugs.python.org/issue14890 closed by ninsen #14891: An error in bindings of closures http://bugs.python.org/issue14891 closed by amaury.forgeotdarc #14896: plistlib handling of real datatype http://bugs.python.org/issue14896 closed by ned.deily #14898: Dict collision on boolean and integer values http://bugs.python.org/issue14898 closed by mark.dickinson

1 0