Mailman 3 September 2016 - Python-Dev

PEP 448 review
by Guido van Rossum March 30, 2023

March 30, 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

congrats on 3.5! Alas, windows 7 users are having problems installing it
by Laura Creighton Sept. 16, 2019

Sept. 16, 2019

webmaster has already heard from 4 people who cannot install it. I sent them to the bug tracker or to python-list but they seem not to have gone either place. Is there some guide I should be sending them to, 'how to debug installation problems'? Laura

5 6

OpenIndiana and Solaris support
by Victor Stinner March 28, 2017

March 28, 2017

Hi, My question is simple: do we officially support Solaris and/or OpenIndiana? Jesus Cea runs an OpenIndiana buildbot slave: http://buildbot.python.org/all/buildslaves/cea-indiana-x86 "Open Indiana 32 bits" The platform module of Python says "Solaris-2.11", I don't know the exact OpenIndiana version. A lot of unit tests fail on this buildbot with MemoryError. I guess that it's related to Solaris which doesn't allow overcommit (allocating more memory than available memory on the system), or more simply because the slave has not enough memory. There is now an issue which seems specific to OpenIndiana: http://bugs.python.org/issue27847 It might impact Solaris as well, but the Solaris buildbot is offline since "684 builds". Five years ago, I reported a bug because the curses module of Python 3 doesn't build on Solaris nor OpenIndiana anymore. It seems like the bug was not fixed, and the issue is still open: http://bugs.python.org/issue13552 So my question is if we officially support Solaris and/or OpenIndiana. If yes, how can we fix issues when we only have buildbot slave which has memory errors, and no SSH access to this server? Solaris doesn't seem to be officially supported in Python, so I suggest to drop the OpenIndiana buildbot (which is failing since at least 2 years) and close all Solaris issues as "WONTFIX". Victor

6 12

Debugging Python scripts with GDB on OSX
by Alexandru Croitor Oct. 15, 2016

Oct. 15, 2016

Hello, I'm interested to find out if debugging Python scripts with GDB is supported on OSX at all? I'm referring to the functionality described on https://wiki.python.org/moin/DebuggingWithGdb and on http://fedoraproject.org/wiki/Features/EasierPythonDebugging. I've tried so far various combinations of pre-compiled GDB from the homebrew package manager, locally-compiled GDB from homebrew, as well as locally compiled GDB from MacPorts, together with a pre-compiled Python 2.7, homebrew-compiled 2.7, and custom compiled Python 2.7 from the official source tarball. My results so far were not successful. The legacy GDB commands to show a python stack trace or the local variables - do not work. And the new GDB commands (referenced on the Fedora project page) are not present at all in any of the GDB versions. I've checked the python CI build bot tests, and it seems the new GDB commands are only successfully tested on Linux machines, and are skipped on FreeBSD, OS X, and Solaris machines. Are the new python <-> GDB commands specific to Linux? Are there any considerations to take in regards to debug symbols for Python / GDB on OSX? Has anyone attempted what I'm trying to do? I would be grateful for any advice. And I apologize if my choice of the mailing lists is not the best. Regards, Alex.

4 6

C99
by Benjamin Peterson Oct. 9, 2016

Oct. 9, 2016

PEP 7 requires CPython to use C code conforming to the venerable C89 standard. Traditionally, we've been stuck with C89 due to poor C support in MSVC. However, MSVC 2013 and 2015 implement the key features of C99. C99 does not offer anything earth-shattering; here are the features I think we'd find most interesting: - Variable declarations can be on any line: removes possibly the most annoying limitation of C89. - Inline functions: We can make Py_DECREF and Py_INCREF inline functions rather than unpleasant macros. - C++-style line comments: Not an killer feature but commonly used. - Booleans In summary, some niceties that would make CPython hacking a little more fun. So, what say you to updating PEP 7 to allow C99 features for Python 3.6 (in so much as GCC and MSVC support them)? Regards, Benjamin

28 65

IMPORTANT: An extra week until 3.6.0b2, now 2016-10-10
by Ned Deily Oct. 1, 2016

Oct. 1, 2016

Thanks for all of your efforts in getting us to the beta phase of 3.6.0! A large number of important features and a huge amount of code were committed just prior to the b1 feature freeze 3 weekends ago. Not surprisingly, there were a number of bugs found and loose ends identified and, as a result, we've negotiated some extensions to get things in before b2. Under the current schedule there were only 3 weeks between b1 and b2 and then 4 weeks between b2 and b3; that was mainly because we pushed b1 back a week due to the development sprint. I would *really* like for us to get those remaining pieces which were granted extensions into b2 as planned. The longer they are delayed, the more risk it puts on the final steps of the release and it's really important to have a stable base for our testing efforts and those of our downstream users, like third-party developers and distributors. So I think it makes sense to move b2 back a week, giving us all an extra week to get things in for b2. Without changing the date for b3, we will now have 4 weeks between b1 and b2 and 3 weeks between b2 and b3. That gives us about 10 days from now until b2. It would be great if you can update the issue tracker for any exempted items you have. I will try to followup with you, as needed, over the next few days on their status. Please contact me if you have any questions about the 3.6.0 schedule or about whether a change is appropriate for the beta phase. To recap, the remaining milestones for 3.6.0: 2016-10-10, 1200 UTC: 3.6.0 beta 2 (was 10-03, remaining exempted features, bug and doc fixes) 2016-10-31: 3.6.0 beta 3 (bug and doc fixes) 2016-11-21: 3.6.0 beta 4 (important bug fixes and doc fixes) 2016-12-05 3.6.0 release candidate 1 (3.6.0 code freeze, critical bug fixes, doc fixes) 2016-12-16 3.6.0 release (3.6.0rc1 plus any necessary emergency fixes) Thank you all again for your great efforts so far on 3.6! --Ned https://www.python.org/dev/peps/pep-0494/ -- Ned Deily nad(a)python.org -- []

1 0

Summary of Python tracker Issues
by Python tracker Oct. 1, 2016

Oct. 1, 2016

ACTIVITY SUMMARY (2016-09-23 - 2016-09-30) 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 5519 (-11) closed 34555 (+70) total 40074 (+59) Open issues with patches: 2381 Issues opened (39) ================== #18235: _sysconfigdata.py wrong on AIX installations http://bugs.python.org/issue18235 reopened by martin.panter #19795: Formatting of True/False/None in docs http://bugs.python.org/issue19795 reopened by serhiy.storchaka #27665: Make create_server able to listen on several ports http://bugs.python.org/issue27665 reopened by bayandin #28259: Ctypes bug windows http://bugs.python.org/issue28259 opened by PlatonAdCo #28261: wrong error messages when using PyArg_ParseTuple to parse norm http://bugs.python.org/issue28261 opened by Oren Milman #28262: Header folder folds incorrectly causing MissingHeaderBodySepar http://bugs.python.org/issue28262 opened by vincenttc #28264: Python 3.4.4 Turtle library - Turtle.onclick events blocked by http://bugs.python.org/issue28264 opened by George Fagin #28267: [MinGW] Crash at start when compiled by MinGW for 64-bit Windo http://bugs.python.org/issue28267 opened by vmurashev #28269: [MinGW] Can't compile Python/dynload_win.c due to static strca http://bugs.python.org/issue28269 opened by vmurashev #28270: [MinGW] Can't compile Modules/posixmodule.c by MinGW - several http://bugs.python.org/issue28270 opened by vmurashev #28271: [MinGW] Can't compile _ctypes/callproc.c - SEH not supported b http://bugs.python.org/issue28271 opened by vmurashev #28272: a redundant check in maybe_small_long http://bugs.python.org/issue28272 opened by Oren Milman #28273: Make os.waitpid() option parameter optional. http://bugs.python.org/issue28273 opened by StyXman #28275: LZMADecompressor.decompress Use After Free http://bugs.python.org/issue28275 opened by JohnLeitch #28276: test_loading.py - false positive result for "def test_find" wh http://bugs.python.org/issue28276 opened by Michael.Felt #28277: ./Modules/_io/_iomodule.c build failure on AIX (beta1) while ( http://bugs.python.org/issue28277 opened by Michael.Felt #28278: Make `weakref.WeakKeyDictionary.__repr__` meaningful http://bugs.python.org/issue28278 opened by cool-RR #28279: setuptools failing to read from setup.cfg only in Python 3.6 http://bugs.python.org/issue28279 opened by Roy Williams #28280: Always return a list from PyMapping_Keys/PyMapping_Values/PyMa http://bugs.python.org/issue28280 opened by serhiy.storchaka #28281: Remove year limits from calendar http://bugs.python.org/issue28281 opened by belopolsky #28282: find_library("c") defers to find_msvcrt() http://bugs.python.org/issue28282 opened by martin.panter #28286: gzip guessing of mode is ambiguilous http://bugs.python.org/issue28286 opened by serhiy.storchaka #28287: Refactor subprocess.Popen to let a subclass handle IO asynchro http://bugs.python.org/issue28287 opened by martius #28288: Expose environment variable for Py_Py3kWarningFlag http://bugs.python.org/issue28288 opened by Roy Williams #28290: BETA report: Python-3.6 build messages to stderr: AIX and "not http://bugs.python.org/issue28290 opened by Michael.Felt #28291: urllib/urllib2 AbstractDigestAuthHandler locked to retried cou http://bugs.python.org/issue28291 opened by secynic #28292: Make Calendar.itermonthdates() behave consistently in edge cas http://bugs.python.org/issue28292 opened by belopolsky #28293: Don't completely dump the regex cache when full http://bugs.python.org/issue28293 opened by rhettinger #28294: HTTPServer server.py assumes sys.stderr != None http://bugs.python.org/issue28294 opened by grismar #28295: PyUnicode_AsUCS4 doc and impl conflict on exception http://bugs.python.org/issue28295 opened by xiang.zhang #28298: can't set big int-like objects to items in array 'Q', 'L' and http://bugs.python.org/issue28298 opened by Oren Milman #28301: python3.4-config --extension-suffix reports '.cpython-34m.so' http://bugs.python.org/issue28301 opened by DrLou #28307: Accelerate 'string' % (value, ...) by using formatted string l http://bugs.python.org/issue28307 opened by serhiy.storchaka #28308: Accelerate 'string'.format(value, ...) by using formatted stri http://bugs.python.org/issue28308 opened by serhiy.storchaka #28309: Accelerate string.Template by using formatted string literals http://bugs.python.org/issue28309 opened by serhiy.storchaka #28312: Minor change - more direct hint re: multiple machine sizes and http://bugs.python.org/issue28312 opened by Michael.Felt #28314: ElementTree: Element.getiterator(tag) broken in 3.6 http://bugs.python.org/issue28314 opened by mitya57 #28315: incorrect "in ?" output in 'divide' example at "Defining Clean http://bugs.python.org/issue28315 opened by viorel #28317: Improve support of FORMAT_VALUE in dis http://bugs.python.org/issue28317 opened by serhiy.storchaka Most recent 15 issues with no replies (15) ========================================== #28317: Improve support of FORMAT_VALUE in dis http://bugs.python.org/issue28317 #28312: Minor change - more direct hint re: multiple machine sizes and http://bugs.python.org/issue28312 #28309: Accelerate string.Template by using formatted string literals http://bugs.python.org/issue28309 #28287: Refactor subprocess.Popen to let a subclass handle IO asynchro http://bugs.python.org/issue28287 #28286: gzip guessing of mode is ambiguilous http://bugs.python.org/issue28286 #28282: find_library("c") defers to find_msvcrt() http://bugs.python.org/issue28282 #28280: Always return a list from PyMapping_Keys/PyMapping_Values/PyMa http://bugs.python.org/issue28280 #28279: setuptools failing to read from setup.cfg only in Python 3.6 http://bugs.python.org/issue28279 #28273: Make os.waitpid() option parameter optional. http://bugs.python.org/issue28273 #28271: [MinGW] Can't compile _ctypes/callproc.c - SEH not supported b http://bugs.python.org/issue28271 #28269: [MinGW] Can't compile Python/dynload_win.c due to static strca http://bugs.python.org/issue28269 #28264: Python 3.4.4 Turtle library - Turtle.onclick events blocked by http://bugs.python.org/issue28264 #28261: wrong error messages when using PyArg_ParseTuple to parse norm http://bugs.python.org/issue28261 #28259: Ctypes bug windows http://bugs.python.org/issue28259 #28249: doctest.DocTestFinder reports incorrect line numbers with excl http://bugs.python.org/issue28249 Most recent 15 issues waiting for review (15) ============================================= #28317: Improve support of FORMAT_VALUE in dis http://bugs.python.org/issue28317 #28315: incorrect "in ?" output in 'divide' example at "Defining Clean http://bugs.python.org/issue28315 #28314: ElementTree: Element.getiterator(tag) broken in 3.6 http://bugs.python.org/issue28314 #28309: Accelerate string.Template by using formatted string literals http://bugs.python.org/issue28309 #28298: can't set big int-like objects to items in array 'Q', 'L' and http://bugs.python.org/issue28298 #28295: PyUnicode_AsUCS4 doc and impl conflict on exception http://bugs.python.org/issue28295 #28294: HTTPServer server.py assumes sys.stderr != None http://bugs.python.org/issue28294 #28293: Don't completely dump the regex cache when full http://bugs.python.org/issue28293 #28291: urllib/urllib2 AbstractDigestAuthHandler locked to retried cou http://bugs.python.org/issue28291 #28287: Refactor subprocess.Popen to let a subclass handle IO asynchro http://bugs.python.org/issue28287 #28286: gzip guessing of mode is ambiguilous http://bugs.python.org/issue28286 #28275: LZMADecompressor.decompress Use After Free http://bugs.python.org/issue28275 #28273: Make os.waitpid() option parameter optional. http://bugs.python.org/issue28273 #28272: a redundant check in maybe_small_long http://bugs.python.org/issue28272 #28271: [MinGW] Can't compile _ctypes/callproc.c - SEH not supported b http://bugs.python.org/issue28271 Top 10 most discussed issues (10) ================================= #28293: Don't completely dump the regex cache when full http://bugs.python.org/issue28293 13 msgs #28207: Use pkg-config to find dependencies http://bugs.python.org/issue28207 12 msgs #28183: Clean up and speed up dict iteration http://bugs.python.org/issue28183 11 msgs #27873: multiprocessing.pool.Pool.map should take more than one iterab http://bugs.python.org/issue27873 7 msgs #28281: Remove year limits from calendar http://bugs.python.org/issue28281 7 msgs #28275: LZMADecompressor.decompress Use After Free http://bugs.python.org/issue28275 6 msgs #28314: ElementTree: Element.getiterator(tag) broken in 3.6 http://bugs.python.org/issue28314 6 msgs #27386: Asyncio server hang when clients connect and immediately disco http://bugs.python.org/issue27386 5 msgs #28199: Compact dict resizing is doing too much work http://bugs.python.org/issue28199 5 msgs #28267: [MinGW] Crash at start when compiled by MinGW for 64-bit Windo http://bugs.python.org/issue28267 5 msgs Issues closed (66) ================== #5895: socketmodule.c on HPUX ia64 without _XOPEN_SOURCE_EXTENDED com http://bugs.python.org/issue5895 closed by christian.heimes #10673: multiprocess.Process join method - timeout indistinguishable f http://bugs.python.org/issue10673 closed by berker.peksag #18893: invalid exception handling in Lib/ctypes/macholib/dyld.py http://bugs.python.org/issue18893 closed by berker.peksag #20100: epoll docs are not clear with regards to CLOEXEC. http://bugs.python.org/issue20100 closed by berker.peksag #20754: distutils should use SafeConfigParser http://bugs.python.org/issue20754 closed by berker.peksag #20947: -Wstrict-overflow findings http://bugs.python.org/issue20947 closed by christian.heimes #21578: Misleading error message when ImportError called with invalid http://bugs.python.org/issue21578 closed by serhiy.storchaka #21903: ctypes documentation MessageBoxA example produces error http://bugs.python.org/issue21903 closed by berker.peksag #22969: Compile fails with --without-signal-module http://bugs.python.org/issue22969 closed by berker.peksag #23155: unittest: object has no attribute '_removed_tests' http://bugs.python.org/issue23155 closed by berker.peksag #23520: test_os failed (python-3.4.3, Linux SuSE) http://bugs.python.org/issue23520 closed by berker.peksag #23701: Drop extraneous comment from winreg.QueryValue's docstring http://bugs.python.org/issue23701 closed by berker.peksag #24201: _winreg PyHKEY Type Confusion http://bugs.python.org/issue24201 closed by steve.dower #25830: _TypeAlias: Discrepancy between docstring and behavior http://bugs.python.org/issue25830 closed by gvanrossum #26075: typing.Union unifies types too broadly http://bugs.python.org/issue26075 closed by gvanrossum #26148: String literals are not interned if in a tuple http://bugs.python.org/issue26148 closed by serhiy.storchaka #26224: Add "version added" for documentation of asyncio.timeout for d http://bugs.python.org/issue26224 closed by berker.peksag #26477: typing forward references and module attributes http://bugs.python.org/issue26477 closed by gvanrossum #26550: documentation minor issue : "Step back: WSGI" section from "HO http://bugs.python.org/issue26550 closed by berker.peksag #26650: calendar: OverflowErrors for year == 1 and firstweekday > 0 http://bugs.python.org/issue26650 closed by belopolsky #27322: test_compile_path fails when python has been installed http://bugs.python.org/issue27322 closed by berker.peksag #27565: Offer error context manager for code.interact http://bugs.python.org/issue27565 closed by berker.peksag #27703: Replace two Py_XDECREFs with Py_DECREFs in do_raise http://bugs.python.org/issue27703 closed by serhiy.storchaka #27740: Fix doc of Py_CompileStringExFlags http://bugs.python.org/issue27740 closed by berker.peksag #27766: Add ChaCha20 Poly1305 to SSL ciphers http://bugs.python.org/issue27766 closed by christian.heimes #27845: Optimize update_keyword_args() function http://bugs.python.org/issue27845 closed by serhiy.storchaka #27897: Avoid possible crash in pysqlite_connection_create_collation http://bugs.python.org/issue27897 closed by serhiy.storchaka #27914: Incorrect comment in PyModule_ExcDef http://bugs.python.org/issue27914 closed by serhiy.storchaka #27942: Default value identity regression http://bugs.python.org/issue27942 closed by serhiy.storchaka #27963: null poiter dereference in set_conversion_mode due uncheck _ct http://bugs.python.org/issue27963 closed by serhiy.storchaka #27995: Upgrade Python 3.4 to OpenSSL 1.0.2h on Windows http://bugs.python.org/issue27995 closed by christian.heimes #28144: Decrease empty_keys_struct's dk_refcnt http://bugs.python.org/issue28144 closed by serhiy.storchaka #28148: [Patch] Also stop using localtime() in timemodule http://bugs.python.org/issue28148 closed by belopolsky #28194: Clean up some checks in dict implementation http://bugs.python.org/issue28194 closed by serhiy.storchaka #28203: complex() gives wrong error when the second argument has an in http://bugs.python.org/issue28203 closed by mark.dickinson #28211: Wrong return value type in the doc of PyMapping_Keys/Values/It http://bugs.python.org/issue28211 closed by serhiy.storchaka #28221: Unused indata in test_ssl.ThreadedTests.test_asyncore_server http://bugs.python.org/issue28221 closed by martin.panter #28250: typing.NamedTuple instances are not picklable Two http://bugs.python.org/issue28250 closed by mark.dickinson #28252: Tuples used before introduction to tuple in tutorial http://bugs.python.org/issue28252 closed by rhettinger #28253: calendar.prcal(9999) output has a problem http://bugs.python.org/issue28253 closed by belopolsky #28254: Add C API for gc.enable, gc.disable, and gc.isenabled http://bugs.python.org/issue28254 closed by rhettinger #28258: Broken python-config generated with Estonian locale http://bugs.python.org/issue28258 closed by serhiy.storchaka #28260: mock._Any and mock._Call implement __eq__ but not __hash__ http://bugs.python.org/issue28260 closed by berker.peksag #28263: Python 2.7's `-3` flag warns about __eq__ being implemented wi http://bugs.python.org/issue28263 closed by christian.heimes #28265: builtin_function_or_method's __getattribute__ not applicable t http://bugs.python.org/issue28265 closed by eric.snow #28266: setup.py uses build Python's configuration when cross-compilin http://bugs.python.org/issue28266 closed by Rouslan Korneychuk #28268: bz2.open does not use __fspath__ (PEP 519) http://bugs.python.org/issue28268 closed by serhiy.storchaka #28274: asyncio does not call exception handler if task stored http://bugs.python.org/issue28274 closed by r.david.murray #28283: test_sock_connect_sock_write_race() of test.test_asyncio.test_ http://bugs.python.org/issue28283 closed by berker.peksag #28284: Memory corruption due to size expansion (overflow) in _json.en http://bugs.python.org/issue28284 closed by python-dev #28285: 35.5 - 29.58 = 5.920000000000002 (it's false !) http://bugs.python.org/issue28285 closed by serhiy.storchaka #28289: ImportError.__init__ doesn't reset not specified exception att http://bugs.python.org/issue28289 closed by serhiy.storchaka #28296: Add __le__ and __ge__ to collections.Counter http://bugs.python.org/issue28296 closed by r.david.murray #28297: sched module example has wrong output http://bugs.python.org/issue28297 closed by xiang.zhang #28299: DirEntry.is_dir() evaluates True for a file on Windows http://bugs.python.org/issue28299 closed by paul.moore #28300: [PATCH] Fix misspelled "implemented" word http://bugs.python.org/issue28300 closed by berker.peksag #28302: Unpacking numpy array give list http://bugs.python.org/issue28302 closed by SilentGhost #28303: [PATCH] Fix broken grammar in "pydoc3 unittest" http://bugs.python.org/issue28303 closed by berker.peksag #28304: Condition.wait() doesn't raise KeyboardInterrupt http://bugs.python.org/issue28304 closed by berker.peksag #28305: Make error for Python3.6 on Cygwin http://bugs.python.org/issue28305 closed by r.david.murray #28306: incorrect output "int division or modulo by zero" in Handling http://bugs.python.org/issue28306 closed by berker.peksag #28310: Mixing yield and return with value is allowed http://bugs.python.org/issue28310 closed by xiang.zhang #28311: AIX shared library extension modules installation broken - Pyt http://bugs.python.org/issue28311 closed by martin.panter #28313: ttk Style().configure() overwrites Tk().option_add() Button bu http://bugs.python.org/issue28313 closed by serhiy.storchaka #28316: descriptor and repr get into conflict http://bugs.python.org/issue28316 closed by benjamin.peterson #1175984: Make subprocess.Popen support file-like objects (win) http://bugs.python.org/issue1175984 closed by christian.heimes

1 0

Re: [Python-Dev] [Python-checkins] cpython (merge 3.5 -> default): Null merge.
by Martin Panter Sept. 29, 2016

Sept. 29, 2016

On 29 September 2016 at 04:26, Zachary Ware <zachary.ware+pydev(a)gmail.com> wrote: > On Wed, Sep 28, 2016 at 10:04 PM, Terry Reedy <tjreedy(a)udel.edu> wrote: >> On 9/28/2016 9:57 PM, terry.reedy wrote: >>> https://hg.python.org/cpython/rev/02eb35b79af0 >> >> >> (2nd try) I mistakenly null merged from 3.5 to default. >> Should a now do a proper null merge from 3.5 to 3.6 to default? >> Should I revert this null merge? FYI I committed some merges (04060fa4428d and ae0c983d3c65) which should have fixed this all up. > You aren't the only one who's missed 3.6 since it was branched :). If > there are changes in 3.5 that should not be in 3.6, you should go > ahead and do a null merge from 3.5 -> 3.6 -> default. If the changes > in 3.5 are already in 3.6, I'd just leave it as is; it will clear up > when somebody next merges something. In this case, my automatic merge process gave conflicts and spooky “ambiguous merge” warnings, so in this case I think it was good to deal with it sooner rather than later.

1 0

Re: [Python-Dev] [Python-checkins] cpython (merge 3.5 -> default): Null merge.
by Martin Panter Sept. 29, 2016

Sept. 29, 2016

On 29 September 2016 at 03:04, Terry Reedy <tjreedy(a)udel.edu> wrote: > On 9/28/2016 9:57 PM, terry.reedy wrote: >> https://hg.python.org/cpython/rev/02eb35b79af0 > > (2nd try) I mistakenly null merged from 3.5 to default. > Should a now do a proper null merge from 3.5 to 3.6 to default? Yes, I think 3.5 needs to be merged into 3.6, and the result needs to be merged into default. I guess they are null merges because the entries were already present in 3.6b1. > Should I revert this null merge? I don’t think there is much point in reverting a null merge, if there are no actual changes to revert.

1 0