Mailman 3 June 2015 - Python-Dev

PEP 448 review
by Guido van Rossum 29 Mar '23

29 Mar '23

I'm back, I've re-read the PEP, and I've re-read the long thread with "(no subject)". I think Georg Brandl nailed it: """ *I like the "sequence and dict flattening" part of the PEP, mostly because itis consistent and should be easy to understand, but the comprehension syntaxenhancements seem to be bad for readability and "comprehending" what the codedoes.The call syntax part is a mixed bag on the one hand it is nice to be consistent with the extended possibilities in literals (flattening), but on the other hand there would be small but annoying inconsistencies anyways (e.g. the duplicate kwarg case above).* """ Greg Ewing followed up explaining that the inconsistency between dict flattening and call syntax is inherent in the pre-existing different rules for dicts vs. keyword args: {'a':1, 'a':2} results in {'a':2}, while f(a=1, a=2) is an error. (This form is a SyntaxError; the dynamic case f(a=1, **{'a': 1}) is a TypeError.) For me, allowing f(*a, *b) and f(**d, **e) and all the other combinations for function calls proposed by the PEP is an easy +1 -- it's a straightforward extension of the existing pattern, and anybody who knows what f(x, *a) does will understand f(x, *a, y, *b). Guessing what f(**d, **e) means shouldn't be hard either. Understanding the edge case for duplicate keys with f(**d, **e) is a little harder, but the error messages are pretty clear, and it is not a new edge case. The sequence and dict flattening syntax proposals are also clean and logical -- we already have *-unpacking on the receiving side, so allowing *x in tuple expressions reads pretty naturally (and the similarity with *a in argument lists certainly helps). From here, having [a, *x, b, *y] is also natural, and then the extension to other displays is natural: {a, *x, b, *y} and {a:1, **d, b:2, **e}. This, too, gets a +1 from me. So that leaves comprehensions. IIRC, during the development of the patch we realized that f(*x for x in xs) is sufficiently ambiguous that we decided to disallow it -- note that f(x for x in xs) is already somewhat of a special case because an argument can only be a "bare" generator expression if it is the only argument. The same reasoning doesn't apply (in that form) to list, set and dict comprehensions -- while f(x for x in xs) is identical in meaning to f((x for x in xs)), [x for x in xs] is NOT the same as [(x for x in xs)] (that's a list of one element, and the element is a generator expression). The basic premise of this part of the proposal is that if you have a few iterables, the new proposal (without comprehensions) lets you create a list or generator expression that iterates over all of them, essentially flattening them: >>> xs = [1, 2, 3] >>> ys = ['abc', 'def'] >>> zs = [99] >>> [*xs, *ys, *zs] [1, 2, 3, 'abc', 'def', 99] >>> But now suppose you have a list of iterables: >>> xss = [[1, 2, 3], ['abc', 'def'], [99]] >>> [*xss[0], *xss[1], *xss[2]] [1, 2, 3, 'abc', 'def', 99] >>> Wouldn't it be nice if you could write the latter using a comprehension? >>> xss = [[1, 2, 3], ['abc', 'def'], [99]] >>> [*xs for xs in xss] [1, 2, 3, 'abc', 'def', 99] >>> This is somewhat seductive, and the following is even nicer: the *xs position may be an expression, e.g.: >>> xss = [[1, 2, 3], ['abc', 'def'], [99]] >>> [*xs[:2] for xs in xss] [1, 2, 'abc', 'def', 99] >>> On the other hand, I had to explore the possibilities here by experimenting in the interpreter, and I discovered some odd edge cases (e.g. you can parenthesize the starred expression, but that seems a syntactic accident). All in all I am personally +0 on the comprehension part of the PEP, and I like that it provides a way to "flatten" a sequence of sequences, but I think very few people in the thread have supported this part. Therefore I would like to ask Neil to update the PEP and the patch to take out the comprehension part, so that the two "easy wins" can make it into Python 3.5 (basically, I am accepting two-thirds of the PEP :-). There is some time yet until alpha 2. I would also like code reviewers (Benjamin?) to start reviewing the patch <http://bugs.python.org/issue2292>, taking into account that the comprehension part needs to be removed. -- --Guido van Rossum (python.org/~guido)

7 17

PEP 1, PEP Purpose and Guidelines
by barry＠zope.com 18 May '21

18 May '21

It has been a while since I posted a copy of PEP 1 to the mailing lists and newsgroups. I've recently done some updating of a few sections, so in the interest of gaining wider community participation in the Python development process, I'm posting the latest revision of PEP 1 here. A version of the PEP is always available on-line at http://www.python.org/peps/pep-0001.html Enjoy, -Barry -------------------- snip snip -------------------- PEP: 1 Title: PEP Purpose and Guidelines Version: $Revision: 1.36 $ Last-Modified: $Date: 2002/07/29 18:34:59 $ Author: Barry A. Warsaw, Jeremy Hylton Status: Active Type: Informational Created: 13-Jun-2000 Post-History: 21-Mar-2001, 29-Jul-2002 What is a PEP? PEP stands for Python Enhancement Proposal. A PEP is a design document providing information to the Python community, or describing a new feature for Python. The PEP should provide a concise technical specification of the feature and a rationale for the feature. We intend PEPs to be the primary mechanisms for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Python. The PEP author is responsible for building consensus within the community and documenting dissenting opinions. Because the PEPs are maintained as plain text files under CVS control, their revision history is the historical record of the feature proposal[1]. Kinds of PEPs There are two kinds of PEPs. A standards track PEP describes a new feature or implementation for Python. An informational PEP describes a Python design issue, or provides general guidelines or information to the Python community, but does not propose a new feature. Informational PEPs do not necessarily represent a Python community consensus or recommendation, so users and implementors are free to ignore informational PEPs or follow their advice. PEP Work Flow The PEP editor, Barry Warsaw <peps(a)python.org>, assigns numbers for each PEP and changes its status. The PEP process begins with a new idea for Python. It is highly recommended that a single PEP contain a single key proposal or new idea. The more focussed the PEP, the more successfully it tends to be. The PEP editor reserves the right to reject PEP proposals if they appear too unfocussed or too broad. If in doubt, split your PEP into several well-focussed ones. Each PEP must have a champion -- someone who writes the PEP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The PEP champion (a.k.a. Author) should first attempt to ascertain whether the idea is PEP-able. Small enhancements or patches often don't need a PEP and can be injected into the Python development work flow with a patch submission to the SourceForge patch manager[2] or feature request tracker[3]. The PEP champion then emails the PEP editor <peps(a)python.org> with a proposed title and a rough, but fleshed out, draft of the PEP. This draft must be written in PEP style as described below. If the PEP editor approves, he will assign the PEP a number, label it as standards track or informational, give it status 'draft', and create and check-in the initial draft of the PEP. The PEP editor will not unreasonably deny a PEP. Reasons for denying PEP status include duplication of effort, being technically unsound, not providing proper motivation or addressing backwards compatibility, or not in keeping with the Python philosophy. The BDFL (Benevolent Dictator for Life, Guido van Rossum) can be consulted during the approval phase, and is the final arbitrator of the draft's PEP-ability. If a pre-PEP is rejected, the author may elect to take the pre-PEP to the comp.lang.python newsgroup (a.k.a. python-list(a)python.org mailing list) to help flesh it out, gain feedback and consensus from the community at large, and improve the PEP for re-submission. The author of the PEP is then responsible for posting the PEP to the community forums, and marshaling community support for it. As updates are necessary, the PEP author can check in new versions if they have CVS commit permissions, or can email new PEP versions to the PEP editor for committing. Standards track PEPs consists of two parts, a design document and a reference implementation. The PEP should be reviewed and accepted before a reference implementation is begun, unless a reference implementation will aid people in studying the PEP. Standards Track PEPs must include an implementation - in the form of code, patch, or URL to same - before it can be considered Final. PEP authors are responsible for collecting community feedback on a PEP before submitting it for review. A PEP that has not been discussed on python-list(a)python.org and/or python-dev(a)python.org will not be accepted. However, wherever possible, long open-ended discussions on public mailing lists should be avoided. Strategies to keep the discussions efficient include, setting up a separate SIG mailing list for the topic, having the PEP author accept private comments in the early design phases, etc. PEP authors should use their discretion here. Once the authors have completed a PEP, they must inform the PEP editor that it is ready for review. PEPs are reviewed by the BDFL and his chosen consultants, who may accept or reject a PEP or send it back to the author(s) for revision. Once a PEP has been accepted, the reference implementation must be completed. When the reference implementation is complete and accepted by the BDFL, the status will be changed to `Final.' A PEP can also be assigned status `Deferred.' The PEP author or editor can assign the PEP this status when no progress is being made on the PEP. Once a PEP is deferred, the PEP editor can re-assign it to draft status. A PEP can also be `Rejected'. Perhaps after all is said and done it was not a good idea. It is still important to have a record of this fact. PEPs can also be replaced by a different PEP, rendering the original obsolete. This is intended for Informational PEPs, where version 2 of an API can replace version 1. PEP work flow is as follows: Draft -> Accepted -> Final -> Replaced ^ +----> Rejected v Deferred Some informational PEPs may also have a status of `Active' if they are never meant to be completed. E.g. PEP 1. What belongs in a successful PEP? Each PEP should have the following parts: 1. Preamble -- RFC822 style headers containing meta-data about the PEP, including the PEP number, a short descriptive title (limited to a maximum of 44 characters), the names, and optionally the contact info for each author, etc. 2. Abstract -- a short (~200 word) description of the technical issue being addressed. 3. Copyright/public domain -- Each PEP must either be explicitly labelled as placed in the public domain (see this PEP as an example) or licensed under the Open Publication License[4]. 4. Specification -- The technical specification should describe the syntax and semantics of any new language feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current Python platforms (CPython, JPython, Python .NET). 5. Motivation -- The motivation is critical for PEPs that want to change the Python language. It should clearly explain why the existing language specification is inadequate to address the problem that the PEP solves. PEP submissions without sufficient motivation may be rejected outright. 6. Rationale -- The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion. 7. Backwards Compatibility -- All PEPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The PEP must explain how the author proposes to deal with these incompatibilities. PEP submissions without a sufficient backwards compatibility treatise may be rejected outright. 8. Reference Implementation -- The reference implementation must be completed before any PEP is given status 'Final,' but it need not be completed before the PEP is accepted. It is better to finish the specification and rationale first and reach consensus on it before writing code. The final implementation must include test code and documentation appropriate for either the Python language reference or the standard library reference. PEP Template PEPs are written in plain ASCII text, and should adhere to a rigid style. There is a Python script that parses this style and converts the plain text PEP to HTML for viewing on the web[5]. PEP 9 contains a boilerplate[7] template you can use to get started writing your PEP. Each PEP must begin with an RFC822 style header preamble. The headers must appear in the following order. Headers marked with `*' are optional and are described below. All other headers are required. PEP: <pep number> Title: <pep title> Version: <cvs version string> Last-Modified: <cvs date string> Author: <list of authors' real names and optionally, email addrs> * Discussions-To: <email address> Status: <Draft | Active | Accepted | Deferred | Final | Replaced> Type: <Informational | Standards Track> * Requires: <pep numbers> Created: <date created on, in dd-mmm-yyyy format> * Python-Version: <version number> Post-History: <dates of postings to python-list and python-dev> * Replaces: <pep number> * Replaced-By: <pep number> The Author: header lists the names and optionally, the email addresses of all the authors/owners of the PEP. The format of the author entry should be address(a)dom.ain (Random J. User) if the email address is included, and just Random J. User if the address is not given. If there are multiple authors, each should be on a separate line following RFC 822 continuation line conventions. Note that personal email addresses in PEPs will be obscured as a defense against spam harvesters. Standards track PEPs must have a Python-Version: header which indicates the version of Python that the feature will be released with. Informational PEPs do not need a Python-Version: header. While a PEP is in private discussions (usually during the initial Draft phase), a Discussions-To: header will indicate the mailing list or URL where the PEP is being discussed. No Discussions-To: header is necessary if the PEP is being discussed privately with the author, or on the python-list or python-dev email mailing lists. Note that email addresses in the Discussions-To: header will not be obscured. Created: records the date that the PEP was assigned a number, while Post-History: is used to record the dates of when new versions of the PEP are posted to python-list and/or python-dev. Both headers should be in dd-mmm-yyyy format, e.g. 14-Aug-2001. PEPs may have a Requires: header, indicating the PEP numbers that this PEP depends on. PEPs may also have a Replaced-By: header indicating that a PEP has been rendered obsolete by a later document; the value is the number of the PEP that replaces the current document. The newer PEP must have a Replaces: header containing the number of the PEP that it rendered obsolete. PEP Formatting Requirements PEP headings must begin in column zero and the initial letter of each word must be capitalized as in book titles. Acronyms should be in all capitals. The body of each section must be indented 4 spaces. Code samples inside body sections should be indented a further 4 spaces, and other indentation can be used as required to make the text readable. You must use two blank lines between the last line of a section's body and the next section heading. You must adhere to the Emacs convention of adding two spaces at the end of every sentence. You should fill your paragraphs to column 70, but under no circumstances should your lines extend past column 79. If your code samples spill over column 79, you should rewrite them. Tab characters must never appear in the document at all. A PEP should include the standard Emacs stanza included by example at the bottom of this PEP. A PEP must contain a Copyright section, and it is strongly recommended to put the PEP in the public domain. When referencing an external web page in the body of a PEP, you should include the title of the page in the text, with a footnote reference to the URL. Do not include the URL in the body text of the PEP. E.g. Refer to the Python Language web site [1] for more details. ... [1] http://www.python.org When referring to another PEP, include the PEP number in the body text, such as "PEP 1". The title may optionally appear. Add a footnote reference that includes the PEP's title and author. It may optionally include the explicit URL on a separate line, but only in the References section. Note that the pep2html.py script will calculate URLs automatically, e.g.: ... Refer to PEP 1 [7] for more information about PEP style ... References [7] PEP 1, PEP Purpose and Guidelines, Warsaw, Hylton http://www.python.org/peps/pep-0001.html If you decide to provide an explicit URL for a PEP, please use this as the URL template: http://www.python.org/peps/pep-xxxx.html PEP numbers in URLs must be padded with zeros from the left, so as to be exactly 4 characters wide, however PEP numbers in text are never padded. Reporting PEP Bugs, or Submitting PEP Updates How you report a bug, or submit a PEP update depends on several factors, such as the maturity of the PEP, the preferences of the PEP author, and the nature of your comments. For the early draft stages of the PEP, it's probably best to send your comments and changes directly to the PEP author. For more mature, or finished PEPs you may want to submit corrections to the SourceForge bug manager[6] or better yet, the SourceForge patch manager[2] so that your changes don't get lost. If the PEP author is a SF developer, assign the bug/patch to him, otherwise assign it to the PEP editor. When in doubt about where to send your changes, please check first with the PEP author and/or PEP editor. PEP authors who are also SF committers, can update the PEPs themselves by using "cvs commit" to commit their changes. Remember to also push the formatted PEP text out to the web by doing the following: % python pep2html.py -i NUM where NUM is the number of the PEP you want to push out. See % python pep2html.py --help for details. Transferring PEP Ownership It occasionally becomes necessary to transfer ownership of PEPs to a new champion. In general, we'd like to retain the original author as a co-author of the transferred PEP, but that's really up to the original author. A good reason to transfer ownership is because the original author no longer has the time or interest in updating it or following through with the PEP process, or has fallen off the face of the 'net (i.e. is unreachable or not responding to email). A bad reason to transfer ownership is because you don't agree with the direction of the PEP. We try to build consensus around a PEP, but if that's not possible, you can always submit a competing PEP. If you are interested assuming ownership of a PEP, send a message asking to take over, addressed to both the original author and the PEP editor <peps(a)python.org>. If the original author doesn't respond to email in a timely manner, the PEP editor will make a unilateral decision (it's not like such decisions can be reversed. :). References and Footnotes [1] This historical record is available by the normal CVS commands for retrieving older revisions. For those without direct access to the CVS tree, you can browse the current and past PEP revisions via the SourceForge web site at http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/python/nondist/peps/?cvsroot=… [2] http://sourceforge.net/tracker/?group_id=5470&atid=305470 [3] http://sourceforge.net/tracker/?atid=355470&group_id=5470&func=browse [4] http://www.opencontent.org/openpub/ [5] The script referred to here is pep2html.py, which lives in the same directory in the CVS tree as the PEPs themselves. Try "pep2html.py --help" for details. The URL for viewing PEPs on the web is http://www.python.org/peps/ [6] http://sourceforge.net/tracker/?group_id=5470&atid=305470 [7] PEP 9, Sample PEP Template http://www.python.org/peps/pep-0009.html 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 End:

8 14

Re: [Python-Dev] Status on PEP-431 Timezones
by Isaac Schwabacher 29 Jul '15

29 Jul '15

On 15-04-15, Akira Li <4kir4.1i(a)gmail.com> wrote: > Isaac Schwabacher <ischwabacher(a)wisc.edu> writes: > > > On 15-04-15, Akira Li <4kir4.1i(a)gmail.com> wrote: > >> Isaac Schwabacher <ischwabacher(a)wisc.edu> writes: > >> > ... > >> > > >> > I know that you can do datetime.now(tz), and you can do datetime(2013, > >> > 11, 3, 1, 30, tzinfo=zoneinfo('America/Chicago')), but not being able > >> > to add a time zone to an existing naive datetime is painful (and > >> > strptime doesn't even let you pass in a time zone). > >> > >> `.now(tz)` is correct. `datetime(..., tzinfo=tz)`) is wrong: if tz is a > >> pytz timezone then you may get a wrong tzinfo (LMT), you should use > >> `tz.localize(naive_dt, is_dst=False|True|None)` instead. > > > > The whole point of this thread is to finalize PEP 431, which fixes the > > problem for which `localize()` and `normalize()` are workarounds. When > > this is done, `datetime(..., tzinfo=tz)` will be correct. > > > > ijs > > The input time is ambiguous. Even if we assume PEP 431 is implemented in > some form, your code is still missing isdst parameter (or the > analog). PEP 431 won't fix it; it can't resolve the ambiguity by > itself. Notice is_dst paramter in the `tz.localize()` call (current > API). ...yeah, I forgot to throw that in there. It was supposed to be there all along. Nothing to see here, move along. > .now(tz) works even during end-of-DST transitions (current API) when the > local time is ambiguous. I know that. That's what I was complaining about-- I was trying to talk about how astimezone() was going to be inadequate even after the PEP was implemented because it couldn't turn naive datetimes into aware ones, and people were giving examples that started with aware datetimes generated by now(tz), which completely went around the point I was trying to make. But it looks like astimezone() is going to grow an is_dst parameter, and everything will be OK. ijs

28 142

Importance of "async" keyword
by Sven R. Kunze 07 Jul '15

07 Jul '15

Hi everybody, recently, I stumbled over the new 3.5 release and in doing so over PEP 0492. After careful consideration and after reading many blog posts of various coders, I first would like to thank Yury Selivanov and everybody else who brought PEP 0492 to its final state. I therefore considered usage within our projects, however, still find hazy items in PEP 0492. So, I would like to contribute my thoughts on this in order to either increase my understanding or even improve Python's async capability. In order to do this, I need a clarification regarding the rationale behind the async keyword. The PEP rationalizes its introduction with: "If useful() [...] would become a regular python function, [...] important() would be broken." What bothers me is, why should important() be broken in that case? Regards, Sven R. Kunze

13 38

Capturing PyRun_String stdout
by Chris Moller 30 Jun '15

30 Jun '15

I expect this has been asked before, but I can't find out much about it... I'm trying to embed Python as a scripting language and I need to capture the output of PyRun_String(), PyEval_EvalCode(), or whatever as a char * (or wchar_t * or whatever) rather than have it go to stdout. Python 3.3.2 under plain C, not C++ And, while I'm interrupting everyone's afternoon, another question: if I pass Py_single_input to PyRun_String() or Py_CompileString()/PyEval_EvalCode(), it accepts statements like "a=10" and can then properly do stuff like "print(a)". If I use Py_eval_input instead, I get error messages. In both cases, I'm using the same global_dict and local_dict, if that makes any difference. What am I doing wrong? Thanks, Chris Moller

2 1

Not getting mail from the issue tracker
by Robert Collins 29 Jun '15

29 Jun '15

Firstly, a big sorry to all those unittest issues I haven't commented on. Turns out I simply don't get mail from the issue tracker. :(. Who should I speak to to try and debug this? In the interim, if you want me to look at an issue please ping me on IRC (lifeless) or mail me directly. -Rob -- Robert Collins <rbtcollins(a)hp.com> Distinguished Technologist HP Converged Cloud

2 1

Re: [Python-Dev] cpython: Minor refactoring. Move reference count logic into function that adds entry.
by Serhiy Storchaka 28 Jun '15

28 Jun '15

On 28.06.15 08:03, raymond.hettinger wrote: > https://hg.python.org/cpython/rev/637e197be547 > changeset: 96697:637e197be547 > user: Raymond Hettinger <python(a)rcn.com> > date: Sat Jun 27 22:03:35 2015 -0700 > summary: > Minor refactoring. Move reference count logic into function that adds entry. This looks not correct. key should be increfed before calling PyObject_RichCompareBool() for the same reason as startkey.

1 0

Unicode 8.0 and 3.5
by Terry Reedy 27 Jun '15

27 Jun '15

Unicode 8.0 was just released. Can we have unicodedata updated to match in 3.5? -- Terry Jan Reedy

7 11

Summary of Python tracker Issues
by Python tracker 26 Jun '15

26 Jun '15

ACTIVITY SUMMARY (2015-06-19 - 2015-06-26) 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 4908 (+16) closed 31369 (+27) total 36277 (+43) Open issues with patches: 2254 Issues opened (29) ================== #15014: smtplib: add support for arbitrary auth methods http://bugs.python.org/issue15014 reopened by barry #24475: The docs never define what a pool "task" is http://bugs.python.org/issue24475 opened by Zahari.Dim #24477: In argparse subparser's option goes to parent parser http://bugs.python.org/issue24477 opened by py.user #24479: Support LMMS project files in mimetypes.guess_type http://bugs.python.org/issue24479 opened by Andreas Nilsson #24481: hotshot pack_string Heap Buffer Overflow http://bugs.python.org/issue24481 opened by JohnLeitch #24482: itertools.tee causes segfault in a multithreading environment, http://bugs.python.org/issue24482 opened by Dmitry Odzerikho #24483: Avoid repeated hash calculation in C implementation of functoo http://bugs.python.org/issue24483 opened by serhiy.storchaka #24484: multiprocessing cleanup occasionally throws exception http://bugs.python.org/issue24484 opened by Jorge Herskovic #24485: Function source inspection fails on closures http://bugs.python.org/issue24485 opened by malthe #24488: ConfigParser.getboolean fails on boolean options http://bugs.python.org/issue24488 opened by andreas-h #24492: using custom objects as modules: AttributeErrors new in 3.5 http://bugs.python.org/issue24492 opened by arigo #24493: subprocess with env=os.environ doesn't preserve environment va http://bugs.python.org/issue24493 opened by The Compiler #24494: Can't specify encoding with fileinput and inplace=True http://bugs.python.org/issue24494 opened by lilydjwg #24498: Shoudl ptags and eptags be removed from repo? http://bugs.python.org/issue24498 opened by r.david.murray #24499: Python Installer text piles up during installation process http://bugs.python.org/issue24499 opened by Zach “The Quantum Mechanic” W #24500: provide context manager to redirect C output http://bugs.python.org/issue24500 opened by Zahari.Dim #24501: configure does not find (n)curses in /usr/local/libs http://bugs.python.org/issue24501 opened by petepdx #24502: OS X 2.7 package has zeros for version numbers in sub-packages http://bugs.python.org/issue24502 opened by Jim Zajkowski #24503: csv.writer fails when within csv.reader http://bugs.python.org/issue24503 opened by ezzieyguywuf #24505: shutil.which wrong result on Windows http://bugs.python.org/issue24505 opened by bobjalex #24506: make fails with gcc 4.9 due to fatal warning of unused variabl http://bugs.python.org/issue24506 opened by krichter #24507: CRLF issues http://bugs.python.org/issue24507 opened by RusiMody #24508: Backport 3.5's Windows build project files to 2.7 http://bugs.python.org/issue24508 opened by zach.ware #24510: Make _PyCoro_GetAwaitableIter a public API http://bugs.python.org/issue24510 opened by yselivanov #24511: Add methods for async protocols http://bugs.python.org/issue24511 opened by yselivanov #24512: multiprocessing should log a warning when forking multithreade http://bugs.python.org/issue24512 opened by trcarden #24514: tarfile fails to extract archive (handled fine by gnu tar and http://bugs.python.org/issue24514 opened by pombreda #24515: docstring of isinstance http://bugs.python.org/issue24515 opened by Luc Saffre #24516: SSL create_default_socket purpose insufficiently documented http://bugs.python.org/issue24516 opened by messa Most recent 15 issues with no replies (15) ========================================== #24512: multiprocessing should log a warning when forking multithreade http://bugs.python.org/issue24512 #24499: Python Installer text piles up during installation process http://bugs.python.org/issue24499 #24498: Shoudl ptags and eptags be removed from repo? http://bugs.python.org/issue24498 #24481: hotshot pack_string Heap Buffer Overflow http://bugs.python.org/issue24481 #24477: In argparse subparser's option goes to parent parser http://bugs.python.org/issue24477 #24475: The docs never define what a pool "task" is http://bugs.python.org/issue24475 #24466: extend_path explanation in documentation is ambiguous http://bugs.python.org/issue24466 #24424: xml.dom.minidom: performance issue with Node.insertBefore() http://bugs.python.org/issue24424 #24417: Type-specific documentation for __format__ methods http://bugs.python.org/issue24417 #24415: SIGINT always reset to SIG_DFL by Py_Finalize() http://bugs.python.org/issue24415 #24414: MACOSX_DEPLOYMENT_TARGET set incorrectly by configure http://bugs.python.org/issue24414 #24407: Use after free in PyDict_merge http://bugs.python.org/issue24407 #24381: Got warning when compiling ffi.c on Mac http://bugs.python.org/issue24381 #24364: Not all defects pass through email policy http://bugs.python.org/issue24364 #24352: Provide a way for assertLogs to optionally not hide the loggin http://bugs.python.org/issue24352 Most recent 15 issues waiting for review (15) ============================================= #24514: tarfile fails to extract archive (handled fine by gnu tar and http://bugs.python.org/issue24514 #24508: Backport 3.5's Windows build project files to 2.7 http://bugs.python.org/issue24508 #24506: make fails with gcc 4.9 due to fatal warning of unused variabl http://bugs.python.org/issue24506 #24483: Avoid repeated hash calculation in C implementation of functoo http://bugs.python.org/issue24483 #24468: Expose C level compiler flag constants to Python code http://bugs.python.org/issue24468 #24467: bytearray pop and remove Buffer Over-read http://bugs.python.org/issue24467 #24465: Make tarfile have deterministic sorting http://bugs.python.org/issue24465 #24464: Got warning when compiling sqlite3 module on Mac OS X http://bugs.python.org/issue24464 #24462: bytearray.find Buffer Over-read http://bugs.python.org/issue24462 #24458: Documentation for PEP 489 http://bugs.python.org/issue24458 #24456: audioop.adpcm2lin Buffer Over-read http://bugs.python.org/issue24456 #24452: Make webbrowser support Chrome on Mac OS X http://bugs.python.org/issue24452 #24451: Add metrics to future objects (concurrent or asyncio?) http://bugs.python.org/issue24451 #24450: Add cr_await calculated property to coroutine object http://bugs.python.org/issue24450 #24440: Move the buildslave setup information from the wiki to the dev http://bugs.python.org/issue24440 Top 10 most discussed issues (10) ================================= #24483: Avoid repeated hash calculation in C implementation of functoo http://bugs.python.org/issue24483 15 msgs #24129: Incorrect (misleading) statement in the execution model docume http://bugs.python.org/issue24129 11 msgs #24484: multiprocessing cleanup occasionally throws exception http://bugs.python.org/issue24484 10 msgs #20387: tokenize/untokenize roundtrip fails with tabs http://bugs.python.org/issue20387 8 msgs #24263: unittest cannot load module whose name starts with Unicode http://bugs.python.org/issue24263 8 msgs #23883: __all__ lists are incomplete http://bugs.python.org/issue23883 7 msgs #15014: smtplib: add support for arbitrary auth methods http://bugs.python.org/issue15014 6 msgs #24325: Speedup types.coroutine() http://bugs.python.org/issue24325 6 msgs #24514: tarfile fails to extract archive (handled fine by gnu tar and http://bugs.python.org/issue24514 6 msgs #12210: test_smtplib: intermittent failures on FreeBSD http://bugs.python.org/issue12210 5 msgs Issues closed (27) ================== #13213: generator.throw() behavior http://bugs.python.org/issue13213 closed by vadmium #23246: distutils fails to locate vcvarsall with Visual C++ Compiler f http://bugs.python.org/issue23246 closed by steve.dower #23684: urlparse() documentation does not account for default scheme http://bugs.python.org/issue23684 closed by berker.peksag #24244: Python exception on strftime with %f on Python 3 and Python 2 http://bugs.python.org/issue24244 closed by python-dev #24309: string.Template should be using str.format and/or deprecated http://bugs.python.org/issue24309 closed by wau #24400: Awaitable ABC incompatible with functools.singledispatch http://bugs.python.org/issue24400 closed by yselivanov #24426: re.split performance degraded significantly by capturing group http://bugs.python.org/issue24426 closed by serhiy.storchaka #24436: _PyTraceback_Add has no const qualifier for its char * argumen http://bugs.python.org/issue24436 closed by serhiy.storchaka #24439: Feedback for awaitable coroutine documentation http://bugs.python.org/issue24439 closed by yselivanov #24447: tab indentation breaks in tokenize.untokenize http://bugs.python.org/issue24447 closed by terry.reedy #24448: Syntax highlighting marks multiline comments as strings http://bugs.python.org/issue24448 closed by terry.reedy #24457: audioop.lin2adpcm Buffer Over-read http://bugs.python.org/issue24457 closed by serhiy.storchaka #24474: Accidental exception chaining in inspect.Signature.bind() http://bugs.python.org/issue24474 closed by ncoghlan #24476: Statically link vcruntime140.dll http://bugs.python.org/issue24476 closed by steve.dower #24478: asyncio: segfault in test_env_var_debug() on non-debug Windows http://bugs.python.org/issue24478 closed by zach.ware #24480: Python 2.7.10 http://bugs.python.org/issue24480 closed by yliu120 #24486: http/client.py block indefinitely on line 308 in _read_status http://bugs.python.org/issue24486 closed by Julien.Palard #24487: Change asyncio.async() → ensure_future() http://bugs.python.org/issue24487 closed by yselivanov #24489: cmath.polar() can raise due to pre-existing errno http://bugs.python.org/issue24489 closed by pitrou #24490: DeprecationWarning hidden even after warnings.filterwarnings(' http://bugs.python.org/issue24490 closed by ned.deily #24491: inspect.getsource can't get source code if provided function i http://bugs.python.org/issue24491 closed by ned.deily #24495: asyncio.ensure_future() AttributeError with “async def” co http://bugs.python.org/issue24495 closed by yselivanov #24496: Non-idiomatic examples in gzip docs http://bugs.python.org/issue24496 closed by berker.peksag #24497: test_decimal.py contains a dead link http://bugs.python.org/issue24497 closed by ned.deily #24504: os.listdir() error if the last folder starts not with the capi http://bugs.python.org/issue24504 closed by Djarbore #24509: Undocumented features of asyncio: call_at, call_later http://bugs.python.org/issue24509 closed by yselivanov #24513: decimal test version mismatch http://bugs.python.org/issue24513 closed by skrah

1 0

Adding c-api async protocol support
by Arc Riley 25 Jun '15

25 Jun '15

A type slot for tp_as_async has already been added (which is good!) but we do not currently seem to have protocol functions for awaitable types. I would expect to find an Awaitable Protocol listed under Abstract Objects Layer, with functions like PyAwait_Check, PyAwaitIter_Check, and PyAwaitIter_Next, etc. Specifically its currently difficult to test whether an object is awaitable or an awaitable iterable, or use said objects from the c-api without relying on method testing/calling mechanisms.

6 7