Mailman 3 September 2015 - Python-Dev

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

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

Sept. 15, 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

VS 2010 compiler
by Chris Barker - NOAA Federal Oct. 2, 2015

Oct. 2, 2015

As I understand it, the MS VS2010 compiler is required (or at least best practice) for compiling Python extensions for the python.org Windows builds of py 3.4 and ?[1] However, MS now makes it very hard (impossible?) to download VS2010 Express ( or Community, or whatever the free as in beer version is called). I realize that this is not python-dev's responsibility, but if there is any way to either document where it can be found, or put a bit of pressure on MS to make it available, as they have for VS2008 and py2.7, that would be great. Sorry to bug this list, I didn't know where else to reach out to. -Chris [1] it's actually prefer hard to find out which compiler version is used for which python version. And has been for years. Would a patch to the docs, probably here: https://docs.python.org/3.4/using/windows.html#compiling-python-on-windows Be considered?

14 31

Washington DC Python sprint report
by Barry Warsaw Sept. 29, 2015

Sept. 29, 2015

Yesterday (27-Sep-2015), four Washington DC area Python developers got together for a local Python hacking sprint. Andrew, Eric, Jason, and I were joined remotely by the esteemed R. David Murray. We did stuff and had fun! We hope to do stuff and have fun again! If you want to join us for stuff and fun next time, please get in touch. Here's a write-up of the sprint: https://gitlab.com/python-smtpd-hackers/aiosmtpd/wikis/2015-09-27-hackfest Special thanks to the PSF and Brian Curtin for sponsoring the sprint. Cheers, -Barry

4 7

Committing a bug fix
by Alexander Belopolsky Sept. 29, 2015

Sept. 29, 2015

Can someone remind me which branches regular (non-security) bug fixes go to these days? See <http://bugs.python.org/issue23600> for context.

7 12

xunit unittest.TestSuite
by vijayram Sept. 26, 2015

Sept. 26, 2015

Hi All, I am facing this same issue described here: https://github.com/nose-devs/nose/issues/542 <https://github.com/nose-devs/nose/issues/542> any alternative or solution to this issue that anyone is aware of... please kindly suggest... Thank you, VJ

2 1

Summary of Python tracker Issues
by Python tracker Sept. 25, 2015

Sept. 25, 2015

ACTIVITY SUMMARY (2015-09-18 - 2015-09-25) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 5142 (+12) closed 31849 (+51) total 36991 (+63) Open issues with patches: 2286 Issues opened (47) ================== #23329: _ssl cannot be compiled with LibreSSL anymore (on OpenBSD 5.5) http://bugs.python.org/issue23329 reopened by haypo #24915: Profile Guided Optimization improvements (better training, llv http://bugs.python.org/issue24915 reopened by haypo #25170: 3.5.0 documentation archives missing http://bugs.python.org/issue25170 opened by Arfrever #25171: does not build on OpenBSD with no value defined for PY_GETENTR http://bugs.python.org/issue25171 opened by rpointel #25172: Unix-only crypt should not be present on Windows. http://bugs.python.org/issue25172 opened by terry.reedy #25173: IDLE - several common dialogs don't have correct parent set http://bugs.python.org/issue25173 opened by markroseman #25175: Documentation-Tkinter Clarify module spelling change in Python http://bugs.python.org/issue25175 opened by Rishit Bansal #25177: OverflowError in statistics.mean when summing large floats http://bugs.python.org/issue25177 opened by David MacIver #25178: IDLE: search regex errors should be in/attached to search dial http://bugs.python.org/issue25178 opened by markroseman #25179: PEP 498 f-strings need to be documented http://bugs.python.org/issue25179 opened by eric.smith #25181: Tests failed in nondecodable directory http://bugs.python.org/issue25181 opened by serhiy.storchaka #25182: python -v crashes in nonencodable directory http://bugs.python.org/issue25182 opened by serhiy.storchaka #25183: python -m inspect --details fails in nondecodable directory http://bugs.python.org/issue25183 opened by serhiy.storchaka #25184: "python -m pydoc -w" fails in nondecodable directory http://bugs.python.org/issue25184 opened by serhiy.storchaka #25185: Inconsistency between venv and site http://bugs.python.org/issue25185 opened by serhiy.storchaka #25186: Don't duplicate _verbose_message in importlib._bootstrap and _ http://bugs.python.org/issue25186 opened by brett.cannon #25187: bdist_rpm fails due to wrong hardcoded assumption about RPM fi http://bugs.python.org/issue25187 opened by dpward #25188: regrtest.py improvement for Profile Guided Optimization builds http://bugs.python.org/issue25188 opened by alecsandru.patrascu #25190: Define StringIO seek offset as code point offset http://bugs.python.org/issue25190 opened by martin.panter #25191: test_getsetlocale_issue1813 failed on OpenBSD http://bugs.python.org/issue25191 opened by rpointel #25193: itertools.accumulate should have an optional initializer argum http://bugs.python.org/issue25193 opened by Alun Champion #25194: Register of Financial Interests for core contributors http://bugs.python.org/issue25194 opened by ncoghlan #25195: mock.ANY doesn't match mock.MagicMock() object http://bugs.python.org/issue25195 opened by felixonmars #25196: Installer>Install in user folder by default when you check: fo http://bugs.python.org/issue25196 opened by Abdullah Hilson #25197: Allow documentation switcher to change url to /3/ and /dev/ http://bugs.python.org/issue25197 opened by mbussonn #25198: Idle: improve idle.html help viewer. http://bugs.python.org/issue25198 opened by terry.reedy #25203: Incorrect handling MemoryError in readline.set_completer_delim http://bugs.python.org/issue25203 opened by serhiy.storchaka #25204: Confusing (?) warning when run deprecated module as script http://bugs.python.org/issue25204 opened by serhiy.storchaka #25205: setattr accepts invalid identifiers http://bugs.python.org/issue25205 opened by W deW #25207: ICC compiler warnings http://bugs.python.org/issue25207 opened by haypo #25209: Append space after completed keywords http://bugs.python.org/issue25209 opened by serhiy.storchaka #25210: Special-case NoneType() in do_richcompare() http://bugs.python.org/issue25210 opened by ezio.melotti #25211: Error message formatting errors in int object unit-test script http://bugs.python.org/issue25211 opened by s-wakaba #25216: Warnings stacklevel frames to skip http://bugs.python.org/issue25216 opened by Jim.Jewett #25217: Method cache can crash at shutdown in _PyType_Lookup http://bugs.python.org/issue25217 opened by pitrou #25218: Automate creation of idlelib/help.html from Doc/.../idle.html http://bugs.python.org/issue25218 opened by terry.reedy #25219: Update doc for Idle command line options. http://bugs.python.org/issue25219 opened by terry.reedy #25220: Enhance and refactor test.regrtest (convert regrtest.py to a p http://bugs.python.org/issue25220 opened by haypo #25221: PyLong_FromLong() potentially returns irregular object when sm http://bugs.python.org/issue25221 opened by s-wakaba #25222: 3.5.0 regression - Fatal Python error: Cannot recover from sta http://bugs.python.org/issue25222 opened by behackett #25224: Replace Idle's README.txt with annotated file list http://bugs.python.org/issue25224 opened by terry.reedy #25226: "suffix" attribute not documented in logging.TimedRotatingFile http://bugs.python.org/issue25226 opened by NobilisVir #25227: Optimize ASCII/latin1 encoder with surrogateescape error handl http://bugs.python.org/issue25227 opened by haypo #25228: Regression in cookie parsing with brackets and quotes http://bugs.python.org/issue25228 opened by Tim.Graham #25229: distutils doesn't add "-Wl," prefix to "-R" on Linux if the C http://bugs.python.org/issue25229 opened by Calvin Walton #25230: Unix datagram sockets not supported http://bugs.python.org/issue25230 opened by rb #25232: CGIRequestHandler behave incorrectly with query component cons http://bugs.python.org/issue25232 opened by xiang.zhang Most recent 15 issues with no replies (15) ========================================== #25232: CGIRequestHandler behave incorrectly with query component cons http://bugs.python.org/issue25232 #25229: distutils doesn't add "-Wl," prefix to "-R" on Linux if the C http://bugs.python.org/issue25229 #25228: Regression in cookie parsing with brackets and quotes http://bugs.python.org/issue25228 #25226: "suffix" attribute not documented in logging.TimedRotatingFile http://bugs.python.org/issue25226 #25221: PyLong_FromLong() potentially returns irregular object when sm http://bugs.python.org/issue25221 #25218: Automate creation of idlelib/help.html from Doc/.../idle.html http://bugs.python.org/issue25218 #25217: Method cache can crash at shutdown in _PyType_Lookup http://bugs.python.org/issue25217 #25216: Warnings stacklevel frames to skip http://bugs.python.org/issue25216 #25204: Confusing (?) warning when run deprecated module as script http://bugs.python.org/issue25204 #25203: Incorrect handling MemoryError in readline.set_completer_delim http://bugs.python.org/issue25203 #25197: Allow documentation switcher to change url to /3/ and /dev/ http://bugs.python.org/issue25197 #25195: mock.ANY doesn't match mock.MagicMock() object http://bugs.python.org/issue25195 #25191: test_getsetlocale_issue1813 failed on OpenBSD http://bugs.python.org/issue25191 #25187: bdist_rpm fails due to wrong hardcoded assumption about RPM fi http://bugs.python.org/issue25187 #25183: python -m inspect --details fails in nondecodable directory http://bugs.python.org/issue25183 Most recent 15 issues waiting for review (15) ============================================= #25232: CGIRequestHandler behave incorrectly with query component cons http://bugs.python.org/issue25232 #25229: distutils doesn't add "-Wl," prefix to "-R" on Linux if the C http://bugs.python.org/issue25229 #25228: Regression in cookie parsing with brackets and quotes http://bugs.python.org/issue25228 #25227: Optimize ASCII/latin1 encoder with surrogateescape error handl http://bugs.python.org/issue25227 #25221: PyLong_FromLong() potentially returns irregular object when sm http://bugs.python.org/issue25221 #25220: Enhance and refactor test.regrtest (convert regrtest.py to a p http://bugs.python.org/issue25220 #25211: Error message formatting errors in int object unit-test script http://bugs.python.org/issue25211 #25209: Append space after completed keywords http://bugs.python.org/issue25209 #25204: Confusing (?) warning when run deprecated module as script http://bugs.python.org/issue25204 #25203: Incorrect handling MemoryError in readline.set_completer_delim http://bugs.python.org/issue25203 #25198: Idle: improve idle.html help viewer. http://bugs.python.org/issue25198 #25197: Allow documentation switcher to change url to /3/ and /dev/ http://bugs.python.org/issue25197 #25194: Register of Financial Interests for core contributors http://bugs.python.org/issue25194 #25188: regrtest.py improvement for Profile Guided Optimization builds http://bugs.python.org/issue25188 #25187: bdist_rpm fails due to wrong hardcoded assumption about RPM fi http://bugs.python.org/issue25187 Top 10 most discussed issues (10) ================================= #25210: Special-case NoneType() in do_richcompare() http://bugs.python.org/issue25210 17 msgs #24915: Profile Guided Optimization improvements (better training, llv http://bugs.python.org/issue24915 15 msgs #18967: Find a less conflict prone approach to Misc/NEWS http://bugs.python.org/issue18967 12 msgs #25194: Register of Financial Interests for core contributors http://bugs.python.org/issue25194 12 msgs #25220: Enhance and refactor test.regrtest (convert regrtest.py to a p http://bugs.python.org/issue25220 12 msgs #25222: 3.5.0 regression - Fatal Python error: Cannot recover from sta http://bugs.python.org/issue25222 12 msgs #24870: Optimize ascii and latin1 decoder with surrogateescape and sur http://bugs.python.org/issue24870 10 msgs #25205: setattr accepts invalid identifiers http://bugs.python.org/issue25205 10 msgs #16701: Docs missing the behavior of += (in-place add) for lists. http://bugs.python.org/issue16701 8 msgs #25177: OverflowError in statistics.mean when summing large floats http://bugs.python.org/issue25177 8 msgs Issues closed (50) ================== #4918: Windows installer created with Python X.Y does not work with P http://bugs.python.org/issue4918 closed by eryksun #16893: Generate Idle help from Doc/library/idle.rst http://bugs.python.org/issue16893 closed by terry.reedy #19143: Finding the Windows version getting messier (detect windows 8. http://bugs.python.org/issue19143 closed by steve.dower #22820: RESTART line with no output http://bugs.python.org/issue22820 closed by terry.reedy #23484: SemLock acquire() keyword arg 'blocking' is invalid http://bugs.python.org/issue23484 closed by berker.peksag #23630: support multiple hosts in create_server/start_server http://bugs.python.org/issue23630 closed by haypo #23979: Multiprocessing Pool.map pickles arguments passed to workers http://bugs.python.org/issue23979 closed by davin #24779: Python/ast.c: decode_unicode is never called with rawmode=True http://bugs.python.org/issue24779 closed by eric.smith #24801: right-mouse click in IDLE on Mac doesn't work http://bugs.python.org/issue24801 closed by terry.reedy #24861: deprecate importing components of IDLE http://bugs.python.org/issue24861 closed by terry.reedy #24894: iso-8859-11 missing from codecs table http://bugs.python.org/issue24894 closed by ezio.melotti #24965: Implement PEP 498: Literal String Formatting http://bugs.python.org/issue24965 closed by eric.smith #25047: xml.etree.ElementTree encoding declaration should be capital ( http://bugs.python.org/issue25047 closed by martin.panter #25057: Make parameter of io.base to be positional and keyword http://bugs.python.org/issue25057 closed by martin.panter #25081: Windows installer Upgrade->Customize->Back goes to Install pag http://bugs.python.org/issue25081 closed by steve.dower #25084: remove semi-busy loop in py2.7 threading.Condition.wait(timeou http://bugs.python.org/issue25084 closed by pitrou #25085: Windows x86-64 embeddable zip file contains test directorys http://bugs.python.org/issue25085 closed by python-dev #25086: Windows x86-64 embeddable zip file, lot of big EXE files in di http://bugs.python.org/issue25086 closed by steve.dower #25092: Regression: test_datetime fails on 3.5, Win 7, works on 3.4 http://bugs.python.org/issue25092 closed by steve.dower #25101: test_zipfile failure when run by unprivileged user with instal http://bugs.python.org/issue25101 closed by serhiy.storchaka #25102: Windows installer: 'precompile standard library' option should http://bugs.python.org/issue25102 closed by steve.dower #25103: 3.5.0 installed standard library on Windows has LF line ending http://bugs.python.org/issue25103 closed by steve.dower #25112: Windows installer assigns non-existent icons to Python file ty http://bugs.python.org/issue25112 closed by steve.dower #25114: asyncio: add ssl_object extra info http://bugs.python.org/issue25114 closed by haypo #25124: No single .msi available for 3.5 release http://bugs.python.org/issue25124 closed by steve.dower #25126: Non-web installer fails without a connection when doing debug http://bugs.python.org/issue25126 closed by steve.dower #25133: Clarify that the constants in selectors are module-level http://bugs.python.org/issue25133 closed by brett.cannon #25138: test_socket: socket.EAI_NODATA doesn't exist on FreeBSD http://bugs.python.org/issue25138 closed by haypo #25145: urllib how-to should be updated to remove PyGoogle http://bugs.python.org/issue25145 closed by benjamin.peterson #25148: Windows registry PythonCore key changed inconsistent with othe http://bugs.python.org/issue25148 closed by steve.dower #25162: Windows installation does not appear in list of installed appl http://bugs.python.org/issue25162 closed by steve.dower #25169: multiprocessing docs example still refs os.getppid as unix-onl http://bugs.python.org/issue25169 closed by berker.peksag #25174: Backspace Escape Character at End of String http://bugs.python.org/issue25174 closed by martin.panter #25176: Link to urllib.parse.parse_qsl, not parse_qs, from cgi.parse_q http://bugs.python.org/issue25176 closed by martin.panter #25180: Tools/parser/unparse.py needs to be updated for f-strings http://bugs.python.org/issue25180 closed by eric.smith #25189: An issue about os.access http://bugs.python.org/issue25189 closed by serhiy.storchaka #25192: deque append and appendleft should return value if maxlen set http://bugs.python.org/issue25192 closed by rhettinger #25199: Idle: add cross-references from and to macosxSupport http://bugs.python.org/issue25199 closed by terry.reedy #25200: bug on re.search using the char ,-: http://bugs.python.org/issue25200 closed by serhiy.storchaka #25201: lock of multiprocessing.Value is not a keyword-only argument http://bugs.python.org/issue25201 closed by berker.peksag #25202: Windows: with-statement doesn't release file handle after exce http://bugs.python.org/issue25202 closed by eryksun #25206: PEP 498: Minor mistakes/outdateness http://bugs.python.org/issue25206 closed by eric.smith #25208: improvements to the asyncio documentation http://bugs.python.org/issue25208 closed by asvetlov #25212: Remove the double spaces in the C-API Intro http://bugs.python.org/issue25212 closed by ezio.melotti #25213: Regression: Python 3.5.0 shutil.copy2 doesn't raise Permission http://bugs.python.org/issue25213 closed by steve.dower #25214: asyncio ssl transport regression http://bugs.python.org/issue25214 closed by haypo #25215: Simple extension to iter(): iter() returns empty generator http://bugs.python.org/issue25215 closed by brett.cannon #25223: Statically or dynamically linked to the VC++runtime ? or how http://bugs.python.org/issue25223 closed by acx01bc #25225: Idle doc: redo Syntax Colors section http://bugs.python.org/issue25225 closed by terry.reedy #25231: Argparse module and escape sequence (special symbols) in argum http://bugs.python.org/issue25231 closed by martin.panter

1 0

PEP 495 accepted
by Guido van Rossum Sept. 24, 2015

Sept. 24, 2015

Just so people know, over at the datetime-sig I've accepted PEP 495, which adds a fold flag to datetime objects to distinguish ambiguous times. This enables roundripping of conversions for those times where the local clock is moved backward (creating ambiguous times that could not be distinguished before). I would like to thank Alexander and Tim for their unrelenting work on this. The idea seems simple, but the details were excruciatingly hard to get right, given the strict backwards compatibility requirements. There may well be additional beneficial changes to the datetime module. The datetime-sig is now open for their discussion. However, proposals that break backwards compatibility are a waste of everybody's time, so be prepared to explain how your proposal does not break existing code that works under Python 3.5. -- --Guido van Rossum (python.org/~guido)

7 29

Make stacklevel=2 by default in warnings.warn()
by Serhiy Storchaka Sept. 22, 2015

Sept. 22, 2015

For now the default value of the stacklevel parameter in warnings.warn() is 1. But in most cases stacklevel=2 is required, sometimes >2, and I don't know cases that need stacklevel=1. I propose to make the default value of stacklevel to be 2. I think that unlikely this will break existing code. But rather can fix existing bugs. If stacklevel=1 is required (I don't know cases), it can be explicitly specified.

8 17