BERJAYA

PEP 448 review
by Guido van Rossum March 29, 2023

March 29, 2023

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 May 18, 2021

May 18, 2021

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

What's New editing
by R. David Murray Sept. 8, 2015

Sept. 8, 2015

Just so people aren't caught unawares, it is very unlikely that I will have time to be the final editor on "What's New for 3.5" they way I was for 3.3 and 3.4. I've tried to encourage people to keep What's New up to date, but *someone* should make a final editing pass. Ideally they'd do at least the research Serhiy did last year on checking that there's a mention for all of the versionadded and versionchanged 3.5's in the docs. Even better would be to review the NEWS and/or commit history...but *that* is a really big job these days.... --David

14 21

tp_finalize vs tp_del sematics
by Valentine Sinitsyn Sept. 4, 2015

Sept. 4, 2015

Hi everybody, I'm trying to get sense of PEP-0442 [1]. Most of the looks clear, however I wasn't able to answer myself one simple question: why it wasn't possible to implement proposed CI disposal scheme on top of tp_del? Common sense suggests that tp_del and tp_finalize have different semantics. For instance, with tp_finalize there is a guarantee that the object will be in a safe state, as documented at [2]. However, tp_del is not documented, and I have only vague idea of its guarantees. Are there any? Thanks for the clarification. 1. https://www.python.org/dev/peps/pep-0442/ 2. https://docs.python.org/3/c-api/typeobj.html -- Best regards, Valentine Sinitsyn

3 11

Building Extensions for Python 3.5 on Windows
by Steve Dower Sept. 2, 2015

Sept. 2, 2015

I've written up a long technical blog post about the compiler and CRT changes in Python 3.5, which will be of interest to those who build and distribute native extensions for Windows. http://stevedower.id.au/blog/building-for-python-3-5/ Hopefully it puts some of the changes we've made into a context where they don't just look like unnecessary pain. Feedback and discussion welcome, either on these lists or on the post itself. Cheers, Steve

5 11

PEP 498: Literal String Interpolation
by Eric V. Smith Aug. 31, 2015

Aug. 31, 2015

PEP 498 adds a new string prefix which allows simpler string formatting by embedding expressions inside string literals. The expressions are evaluated and inserted into the resulting string value: >>> import datetime >>> name = 'Fred' >>> age = 50 >>> anniversary = datetime.date(1991, 10, 12) >>> f'My name is {name}, my age next year is {age+1}, my anniversary is {anniversary:%A, %B %d, %Y}.' 'My name is Fred, my age next year is 51, my anniversary is Saturday, October 12, 1991.' There's been a lot of discussion about this on python-ideas, much of which has been incorporated in to the PEP. Now I feel it's ready for python-dev input. Note there's a companion PEP 501 which extends this idea by delaying converting the expression into a string. This allows for more control over how the expressions are converted in to strings, and allows for non-string conversions as well. I have a complete implementation of PEP 498. I'll shortly create an issue and attach the patch to it. -- Eric.

3 6

Re: [Python-Dev] ZIP File Instead of Installer
by Steve Holden Aug. 31, 2015

Aug. 31, 2015

Hi Alex, Thanks for your email, and the suggestion. A couple of things … First, as webmaster we are simply volunteers who try to accept and process feedback *about the python.org <http://python.org/> web site*. We aren’t (mostly) actively involved in the development of the language, though we are all dedicated users - most of us either don’t have tie to take part in python-dev or feel we have already put our time in. So this isn’t the best channel for the particular inout you’re making. Second, while it’s practical to put *most* of the stdlib in a zip file it may be impractical to put them *all* in there. I did some experiments (admittedly about eight years ago, so things may have changed) to enable an import mechanism that imported code from a relational database. Naturally there were modules that had to be loaded using the standard mechanisms - the ones I needed to import to enable my database imports! It’s a classical bootstrap problem. Third, your idea would need considerable expansion before being actionable: consider the fact that there are millions of downloads of Python every month. Obviously there is huge amount of engineering detail to consider before releasing anything new - if an error only occurs one time in 100,000 that will lead to a substantial number of bug reports, so the dev tend to proceed fairly carefully and with much deliberation. Fourth, I really like it that you are enthusiastic about Python, and would suggest you consider joining the python-dev mailing list. Start as a lurker, just reading what is said, and (since you are obviously thinking a lot as you learn Python) you will be surprised how much you pick up. The people on that list aren’t gods, they are just regular developers who happen to commit a lot of their time to Python’s development, and they rely on a continuous influx of new blood. So as long as you take your time getting to know the personalities involved and how the list works you are likely to find a welcome there. The day will arrive when you realize that rather to your surprise you have something to contribute. There’s also the python-ideas list and, if you are nervous about just diving straight into python-dev, there’s the python-mentor list that was specifically designed to provide a sympathetic and uncritical response to enthusiasm such as you exhibit. The caveat in all this is that as an old fart I haven’t actually been active on any of those lists for quite a while, so I am unsure how active they all are. I hope this response is helpful. I’ve invested a lot of time in trying to make the Python ecosystem one that welcomes enthusiasm and energy, and lot of other people do the same, many of them more effectively than me. It seems to me that you have both enthusiasm and energy, which is why I’ve taken the time to encourage you to put it to use. Good luck in your progress with Python. regards Steve PS: The mailing lists are all detailed on https://mail.python.org/mailman/listinfo <https://mail.python.org/mailman/listinfo> > On Aug 31, 2015, at 9:48 PM, Alex Huffstetler <superdoom1(a)outlook.com> wrote: > > I have an idea. I had a problem with installing Python because I’m not an admin. > My idea is you delete the installer and put all the files in a ZIP folder. It can make download time faster. > Also, I made the Python logo out off underscores and pipes. > If it dosen’t look right, put it somewhere on the Internet and it’ll look right. > _____________ > | . | > _______|_______ |________ > | | | > | _____________| | > | | | > |_______| _______________| > | . | > |_____________| -- Steve Holden steve(a)holdenweb.com / +44 208 289 6308 / @holdenweb

1 0

provisional status for asyncio
by Yury Selivanov Aug. 29, 2015

Aug. 29, 2015

Recently, in an asyncio related issue [1], Guido said that new features for asyncio have to wait till 3.6, since asyncio is no longer a provisional package. Later, in an off-list conversation, he suggested that this topic should be discussed on python-dev, and that it might indeed make sense to either write a new PEP for cases like this or to augment PEP 411. My opinion on this topic is that we must maintain full backwards compatibility for asyncio from 3.5.0, as it is now widely used, and there is quite a big ecosystem around it. However, asyncio is simply not mature enough to be completely feature frozen for about 2 years. For example, there is an issue [2] to add starttls support to asyncio. It is an essential feature, because some protocols start as clear text and upgrade to TLS later, for example PostgreSQL PQ3 protocol. It's very hard to implement starttls on top of asyncio, lots of code will have to be duplicated -- it's a feature that has to implemented in the asyncio core. Aside from adding new APIs, we also have to improve debugging capabilities. One example is using os.fork() from within a running event loop -- it must be avoided by all means. There are safe ways to fork in asyncio applications (and I plan to document them soon), but asyncio should raise an exception in debug mode if this happens (see issue [3]). These are just two immediate issues that I have in mind. In reality, asyncio is quite young compared to frameworks like Twisted, which had years to mature, and accumulate essential features. My proposal is to amend PEP 411 with two levels of provisional packages: Level 1: Backwards incompatible changes might be introduced in point releases. Level 2: Only backwards compatible changes can be introduced in new point releases. With the above amendments, asyncio status should be restated as a level-2 provisional package. I'm CC-ing authors of PEP 411 Nick and Eli. Thank you, Yury [1] http://bugs.python.org/issue23630 [2] http://bugs.python.org/issue23749 [3] http://bugs.python.org/issue21998

10 33

Summary of Python tracker Issues
by Python tracker Aug. 28, 2015

Aug. 28, 2015

ACTIVITY SUMMARY (2015-08-21 - 2015-08-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 5042 (+29) closed 31671 (+15) total 36713 (+44) Open issues with patches: 2251 Issues opened (39) ================== #24909: Windows: subprocess.Popen: race condition for leaking inherita http://bugs.python.org/issue24909 opened by Adam Meily #24910: Windows MSIs don't have unique display names http://bugs.python.org/issue24910 opened by steve.dower #24911: Context manager of socket.socket is not documented http://bugs.python.org/issue24911 opened by zodalahtathi #24912: The type of cached objects is mutable http://bugs.python.org/issue24912 opened by serhiy.storchaka #24913: deque.index() overruns deque boundary http://bugs.python.org/issue24913 opened by JohnLeitch #24914: Python: Not just OO style but this is not mentioned on python. http://bugs.python.org/issue24914 opened by Paddy McCarthy #24915: Profile Guided Optimization improvements (better training, llv http://bugs.python.org/issue24915 opened by alecsandru.patrascu #24916: In sysconfig, don't rely on sys.version format http://bugs.python.org/issue24916 opened by takluyver #24917: time_strftime() Buffer Over-read http://bugs.python.org/issue24917 opened by JohnLeitch #24918: Docs layout bug http://bugs.python.org/issue24918 opened by reag #24920: shutil.get_terminal_size throws AttributeError http://bugs.python.org/issue24920 opened by Isaac Levy #24921: Operator precedence table in 5.15 should be highest to lowest http://bugs.python.org/issue24921 opened by Joseph Schachner #24922: assertWarnsRegex doesn't allow multiple warning messages http://bugs.python.org/issue24922 opened by sleepycal #24923: Append system paths in setup.py instead of prepending http://bugs.python.org/issue24923 opened by christopher.hogan #24924: _posixsubprocess.c: sysconf() might not be async-signal-safe http://bugs.python.org/issue24924 opened by jwilk #24925: Allow doctest to find line number of __test__ strings if forma http://bugs.python.org/issue24925 opened by r.david.murray #24927: multiprocessing.Pool hangs forever on segfault http://bugs.python.org/issue24927 opened by Jonas Obrist #24928: mock.patch.dict spoils order of items in collections.OrderedDi http://bugs.python.org/issue24928 opened by Alexander Oblovatniy #24929: _strptime.TimeRE should not enforce range in regex http://bugs.python.org/issue24929 opened by Steve Yeung #24930: test_ssl broker was fixed http://bugs.python.org/issue24930 opened by marcosptf #24931: _asdict breaks when inheriting from a namedtuple http://bugs.python.org/issue24931 opened by Samuel Isaacson #24932: Migrate _testembed to a C unit testing library http://bugs.python.org/issue24932 opened by ncoghlan #24933: socket.recv(size, MSG_TRUNC) returns more than size bytes http://bugs.python.org/issue24933 opened by Andrey Wagin #24934: django_v2 benchmark not working in Python 3.6 http://bugs.python.org/issue24934 opened by florin.papa #24935: LDSHARED is not set according when CC is set. http://bugs.python.org/issue24935 opened by yunlian #24936: Idle: handle 'raise' properly when running with subprocess (2. http://bugs.python.org/issue24936 opened by terry.reedy #24937: Multiple problems in getters & setters in capsulethunk.h http://bugs.python.org/issue24937 opened by encukou #24938: Measure if _warnings.c is still worth having http://bugs.python.org/issue24938 opened by brett.cannon #24939: Remove unicode_format.h from stringlib http://bugs.python.org/issue24939 opened by eric.smith #24940: RotatingFileHandler uses tell in non-binary mode to determine http://bugs.python.org/issue24940 opened by Ilya.Kulakov #24941: Add classproperty as builtin class http://bugs.python.org/issue24941 opened by guettli #24942: Remove domain from ipaddress.reverse_pointer property and add http://bugs.python.org/issue24942 opened by leeclemens #24945: Expose Py_TPFLAGS_ values from Python http://bugs.python.org/issue24945 opened by erik.bray #24946: Tkinter tests that fail on linux in tiling window manager http://bugs.python.org/issue24946 opened by terry.reedy #24948: Multiprocessing not timely flushing stack trace to stderr http://bugs.python.org/issue24948 opened by memeplex #24949: Identifier lookup in a multi-level package is flakey http://bugs.python.org/issue24949 opened by SegundoBob #24950: FAIL: test_expanduser when $HOME=/ http://bugs.python.org/issue24950 opened by felixonmars #24951: Idle test_configdialog fails on Fedora 23, 3.6 http://bugs.python.org/issue24951 opened by terry.reedy #24952: stack_size([size]) is actually stack_size(size=0) http://bugs.python.org/issue24952 opened by mattip Most recent 15 issues with no replies (15) ========================================== #24946: Tkinter tests that fail on linux in tiling window manager http://bugs.python.org/issue24946 #24942: Remove domain from ipaddress.reverse_pointer property and add http://bugs.python.org/issue24942 #24940: RotatingFileHandler uses tell in non-binary mode to determine http://bugs.python.org/issue24940 #24936: Idle: handle 'raise' properly when running with subprocess (2. http://bugs.python.org/issue24936 #24925: Allow doctest to find line number of __test__ strings if forma http://bugs.python.org/issue24925 #24924: _posixsubprocess.c: sysconf() might not be async-signal-safe http://bugs.python.org/issue24924 #24923: Append system paths in setup.py instead of prepending http://bugs.python.org/issue24923 #24922: assertWarnsRegex doesn't allow multiple warning messages http://bugs.python.org/issue24922 #24917: time_strftime() Buffer Over-read http://bugs.python.org/issue24917 #24916: In sysconfig, don't rely on sys.version format http://bugs.python.org/issue24916 #24910: Windows MSIs don't have unique display names http://bugs.python.org/issue24910 #24906: asyncore asynchat hanging on ssl http://bugs.python.org/issue24906 #24905: Allow incremental I/O to blobs in sqlite3 http://bugs.python.org/issue24905 #24899: Add an os.path <=> pathlib equivalence table in pathlib docs http://bugs.python.org/issue24899 #24894: iso-8859-11 missing from codecs table http://bugs.python.org/issue24894 Most recent 15 issues waiting for review (15) ============================================= #24952: stack_size([size]) is actually stack_size(size=0) http://bugs.python.org/issue24952 #24938: Measure if _warnings.c is still worth having http://bugs.python.org/issue24938 #24937: Multiple problems in getters & setters in capsulethunk.h http://bugs.python.org/issue24937 #24934: django_v2 benchmark not working in Python 3.6 http://bugs.python.org/issue24934 #24931: _asdict breaks when inheriting from a namedtuple http://bugs.python.org/issue24931 #24930: test_ssl broker was fixed http://bugs.python.org/issue24930 #24927: multiprocessing.Pool hangs forever on segfault http://bugs.python.org/issue24927 #24925: Allow doctest to find line number of __test__ strings if forma http://bugs.python.org/issue24925 #24923: Append system paths in setup.py instead of prepending http://bugs.python.org/issue24923 #24917: time_strftime() Buffer Over-read http://bugs.python.org/issue24917 #24916: In sysconfig, don't rely on sys.version format http://bugs.python.org/issue24916 #24915: Profile Guided Optimization improvements (better training, llv http://bugs.python.org/issue24915 #24913: deque.index() overruns deque boundary http://bugs.python.org/issue24913 #24909: Windows: subprocess.Popen: race condition for leaking inherita http://bugs.python.org/issue24909 #24904: Patch: add timeout to difflib SequenceMatcher ratio() and quic http://bugs.python.org/issue24904 Top 10 most discussed issues (10) ================================= #24915: Profile Guided Optimization improvements (better training, llv http://bugs.python.org/issue24915 21 msgs #23630: support multiple hosts in create_server/start_server http://bugs.python.org/issue23630 15 msgs #2786: Names in function call exception should have class names, if t http://bugs.python.org/issue2786 13 msgs #23496: Steps for Android Native Build of Python 3.4.2 http://bugs.python.org/issue23496 8 msgs #24294: DeprecationWarnings should be visible by default in the intera http://bugs.python.org/issue24294 8 msgs #24829: Use interactive input even if stdout is redirected http://bugs.python.org/issue24829 8 msgs #24913: deque.index() overruns deque boundary http://bugs.python.org/issue24913 8 msgs #24934: django_v2 benchmark not working in Python 3.6 http://bugs.python.org/issue24934 8 msgs #3548: subprocess.pipe function http://bugs.python.org/issue3548 7 msgs #24305: The new import system makes it inconvenient to correctly issue http://bugs.python.org/issue24305 7 msgs Issues closed (14) ================== #21112: 3.4 regression: unittest.expectedFailure no longer works on Te http://bugs.python.org/issue21112 closed by rbcollins #22812: Documentation of unittest -p usage wrong on windows. http://bugs.python.org/issue22812 closed by rbcollins #22936: traceback module has no way to show locals http://bugs.python.org/issue22936 closed by rbcollins #23552: Have timeit warn about runs that are not independent of each o http://bugs.python.org/issue23552 closed by rbcollins #24633: README file installed into site-packages conflicts with packag http://bugs.python.org/issue24633 closed by rbcollins #24769: Interpreter doesn't start when dynamic loading is disabled http://bugs.python.org/issue24769 closed by larry #24808: PyTypeObject fields have incorrectly documented types http://bugs.python.org/issue24808 closed by martin.panter #24847: Can't import tkinter in Python 3.5.0rc1 http://bugs.python.org/issue24847 closed by larry #24850: syslog.syslog() does not return error when unable to send the http://bugs.python.org/issue24850 closed by r.david.murray #24919: Use user shell in subprocess http://bugs.python.org/issue24919 closed by r.david.murray #24926: Incorrect Example in HTMLParser.handle_comment(data) http://bugs.python.org/issue24926 closed by r.david.murray #24943: Simplifying os.exec* http://bugs.python.org/issue24943 closed by r.david.murray #24944: traceback when using tempfile module on windows http://bugs.python.org/issue24944 closed by haypo #24947: asyncio-eventloop documentation grammar (minor) http://bugs.python.org/issue24947 closed by python-dev

1 0

Testing tkinter on Linux
by Terry Reedy Aug. 28, 2015

Aug. 28, 2015

None of the linux buildbots run with X enabled. Consequently none of the tkinter (or tkinter user) gui tests are run on Linux. It was thus pointed out to me, during discussion of using ttk widgets in Idle, that we do not really know if ttk works on the variety of Linux systems (beyond the one Serhiy uses) and that I should look into this. I asked on python-list for help, by linux users running python3 -m test -ugui test_tk test_ttk_guionly test_idle Seven people did so with Debian Jessie, Debian Wheezy, Gentoo, Mint, openSUSE, and Ubuntu (x2). One machine failed once with the ttk test, and then passed. Another failed the tk test until a mis-configuration was fixed. So tkinter, and ttk in particular, seems to be working on linux. Do any of the core devs who run the test suite on Linux do so with -uall or -ugui? The gui tests above take about 10 seconds (mostly the tk test) on my machine, with some flashing boxes near the end. -- Terry Jan Reedy

5 6

Python-Dev

August 2015