BERJAYA

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

Reviving restricted mode?
by Guido van Rossum Aug. 14, 2014

Aug. 14, 2014

I've received some enthusiastic emails from someone who wants to revive restricted mode. He started out with a bunch of patches to the CPython runtime using ctypes, which he attached to an App Engine bug: http://code.google.com/p/googleappengine/issues/detail?id=671 Based on his code (the file secure.py is all you need, included in secure.tar.gz) it seems he believes the only security leaks are __subclasses__, gi_frame and gi_code. (I have since convinced him that if we add "restricted" guards to these attributes, he doesn't need the functions added to sys.) I don't recall the exploits that Samuele once posted that caused the death of rexec.py -- does anyone recall, or have a pointer to the threads? -- --Guido van Rossum (home page: http://www.python.org/~guido/)

19 35

PEP 423 : naming conventions and recipes related to packaging
by Benoît Bryon July 5, 2013

July 5, 2013

Hi, Here is an informational PEP proposal: http://hg.python.org/peps/file/52767ab7e140/pep-0423.txt Could you review it for style, consistency and content? Additional notes: * Original discussion posted to distutils-sig(a)python.org * started on May 2012 at http://mail.python.org/pipermail/distutils-sig/2012-May/018551.html * continues in June 2012 at http://mail.python.org/pipermail/distutils-sig/2012-June/018641.html * that's why I set "Discussion-To:<distutils-sig(a)python.org>" header. * Original document was edited as a contrib to cpython documentation: * http://bugs.python.org/issue14899 * file history at https://bitbucket.org/benoitbryon/cpython/history/Doc/packaging/packagename… * but it looked like a PEP, so posted to peps(a)python.org... Regards, Benoit (benoitbb on irc.freenode.net)

11 20

Point of building without threads?
by Antoine Pitrou Feb. 16, 2013

Feb. 16, 2013

Hello, I guess a long time ago, threading support in operating systems wasn't very widespread, but these days all our supported platforms have it. Is it still useful for production purposes to configure --without-threads? Do people use this option for something else than curiosity of mind? Regards Antoine.

10 22

PEP 3145 (With Contents)
by Eric Pruitt Dec. 25, 2012

Dec. 25, 2012

Alright, I will re-submit with the contents pasted. I never use double backquotes as I think them rather ugly; that is the work of an editor or some automated program in the chain. Plus, it also messed up my line formatting and now I have lines with one word on them... Anyway, the contents of PEP 3145: PEP: 3145 Title: Asynchronous I/O For subprocess.Popen Author: (James) Eric Pruitt, Charles R. McCreary, Josiah Carlson Type: Standards Track Content-Type: text/plain Created: 04-Aug-2009 Python-Version: 3.2 Abstract: In its present form, the subprocess.Popen implementation is prone to dead-locking and blocking of the parent Python script while waiting on data from the child process. Motivation: A search for "python asynchronous subprocess" will turn up numerous accounts of people wanting to execute a child process and communicate with it from time to time reading only the data that is available instead of blocking to wait for the program to produce data [1] [2] [3]. The current behavior of the subprocess module is that when a user sends or receives data via the stdin, stderr and stdout file objects, dead locks are common and documented [4] [5]. While communicate can be used to alleviate some of the buffering issues, it will still cause the parent process to block while attempting to read data when none is available to be read from the child process. Rationale: There is a documented need for asynchronous, non-blocking functionality in subprocess.Popen [6] [7] [2] [3]. Inclusion of the code would improve the utility of the Python standard library that can be used on Unix based and Windows builds of Python. Practically every I/O object in Python has a file-like wrapper of some sort. Sockets already act as such and for strings there is StringIO. Popen can be made to act like a file by simply using the methods attached the the subprocess.Popen.stderr, stdout and stdin file-like objects. But when using the read and write methods of those options, you do not have the benefit of asynchronous I/O. In the proposed solution the wrapper wraps the asynchronous methods to mimic a file object. Reference Implementation: I have been maintaining a Google Code repository that contains all of my changes including tests and documentation [9] as well as blog detailing the problems I have come across in the development process [10]. I have been working on implementing non-blocking asynchronous I/O in the subprocess.Popen module as well as a wrapper class for subprocess.Popen that makes it so that an executed process can take the place of a file by duplicating all of the methods and attributes that file objects have. There are two base functions that have been added to the subprocess.Popen class: Popen.send and Popen._recv, each with two separate implementations, one for Windows and one for Unix based systems. The Windows implementation uses ctypes to access the functions needed to control pipes in the kernel 32 DLL in an asynchronous manner. On Unix based systems, the Python interface for file control serves the same purpose. The different implementations of Popen.send and Popen._recv have identical arguments to make code that uses these functions work across multiple platforms. When calling the Popen._recv function, it requires the pipe name be passed as an argument so there exists the Popen.recv function that passes selects stdout as the pipe for Popen._recv by default. Popen.recv_err selects stderr as the pipe by default. "Popen.recv" and "Popen.recv_err" are much easier to read and understand than "Popen._recv('stdout' ..." and "Popen._recv('stderr' ..." respectively. Since the Popen._recv function does not wait on data to be produced before returning a value, it may return empty bytes. Popen.asyncread handles this issue by returning all data read over a given time interval. The ProcessIOWrapper class uses the asyncread and asyncwrite functions to allow a process to act like a file so that there are no blocking issues that can arise from using the stdout and stdin file objects produced from a subprocess.Popen call. References: [1] [ python-Feature Requests-1191964 ] asynchronous Subprocess http://mail.python.org/pipermail/python-bugs-list/2006-December/ 036524.html [2] Daily Life in an Ivory Basement : /feb-07/problems-with-subprocess http://ivory.idyll.org/blog/feb-07/problems-with-subprocess [3] How can I run an external command asynchronously from Python? - Stack Overflow http://stackoverflow.com/questions/636561/how-can-i-run-an-external- command-asynchronously-from-python [4] 18.1. subprocess - Subprocess management - Python v2.6.2 documentation http://docs.python.org/library/subprocess.html#subprocess.Popen.wait [5] 18.1. subprocess - Subprocess management - Python v2.6.2 documentation http://docs.python.org/library/subprocess.html#subprocess.Popen.kill [6] Issue 1191964: asynchronous Subprocess - Python tracker http://bugs.python.org/issue1191964 [7] Module to allow Asynchronous subprocess use on Windows and Posix platforms - ActiveState Code http://code.activestate.com/recipes/440554/ [8] subprocess.rst - subprocdev - Project Hosting on Google Code http://code.google.com/p/subprocdev/source/browse/doc/subprocess.rst?spec=s… [9] subprocdev - Project Hosting on Google Code http://code.google.com/p/subprocdev [10] Python Subprocess Dev http://subdev.blogspot.com/ Copyright: This P.E.P. is licensed under the Open Publication License; http://www.opencontent.org/openpub/. On Tue, Sep 8, 2009 at 22:56, Benjamin Peterson <benjamin(a)python.org> wrote: > 2009/9/7 Eric Pruitt <eric.pruitt(a)gmail.com>: >> Hello all, >> >> I have been working on adding asynchronous I/O to the Python >> subprocess module as part of my Google Summer of Code project. Now >> that I have finished documenting and pruning the code, I present PEP >> 3145 for its inclusion into the Python core code. Any and all feedback >> on the PEP (http://www.python.org/dev/peps/pep-3145/) is appreciated. > > Hi Eric, > One of the reasons you're not getting many response is that you've not > pasted the contents of the PEP in this message. That makes it really > easy for people to comment on various sections. > > BTW, it seems like you were trying to use reST formatting with the > text PEP layout. Double backquotes only mean something in reST. > > > -- > Regards, > Benjamin >

10 26

Testing the tests by modifying the ordering of dict items.
by Mark Shannon Dec. 22, 2012

Dec. 22, 2012

Hi, Python code should not depend upon the ordering of items in a dict. Unfortunately it seems that a number of tests in the standard library do just that. Changing PyDict_MINSIZE from 8 to either 4 or 16 causes the following tests to fail: test_dis test_email test_inspect test_nntplib test_packaging test_plistlib test_pprint test_symtable test_trace test_sys also fails, but this is a legitimate failure in sys.getsizeof() Changing the collision resolution function from f(n) = 5n + 1 to f(n) = n + 1 results in the same failures, except for test_packaging and test_symtable which pass. Finally, changing the seed in unicode_hash() from (implicit) 0 to an arbitrary value (12345678) causes the above tests to fail plus: test_json test_set test_ttk_textonly test_urllib test_urlparse I think this is a real issue as the unicode_hash() function is likely to change soon due to http://bugs.python.org/issue13703. Should I: 1. Submit one big bug report? 2. Submit a bug report for each "failing" test separately? 3. Ignore it, since the tests only fail when I start messing about? Cheers, Mark.

4 4

cross-compiling patches
by Antoine Pitrou July 1, 2012

July 1, 2012

Hello, I think these patches are premature (they break compilation on OS X, and they break ctypes configure on my Linux box). Furthermore, they were committed post-beta, which means they should probably have waited for after the 3.3 release. So I propose for these commits to be reverted. (to be clear, I'm talking about all configure / Makefile / setup.py / libffi changes since and including http://hg.python.org/cpython/rev/e6e99d449bdc876fa57111e7e534c44ecbc3bcbd ) Regards Antoine.

4 4

Issue 1677 - please advise
by Tim Golden June 29, 2012

June 29, 2012

I've been working on issue 1677 which concerns a race condition in the interactive interpreter on Windows where a Ctrl-C can in some circumstances cause the interpreter to exit as though a Ctrl-Z had been pressed. I've added patches to the issue for 2.7, 3.2 & default. I can't see any realistic way to add a test for this. Unsurprisingly there don't appear to be any tests in the test suite for the interactive interpreter and even if there were, this is an inconsistent race condition I'm fixing. So... should I go ahead and push anyway, or is there anything else I should be doing as part of the change? Thanks TJG

2 1

Summary of Python tracker Issues
by Python tracker June 29, 2012

June 29, 2012

ACTIVITY SUMMARY (2012-06-22 - 2012-06-29) 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 3485 ( +3) closed 23515 (+80) total 27000 (+83) Open issues with patches: 1456 Issues opened (54) ================== #11728: mbox parser incorrect behaviour http://bugs.python.org/issue11728 reopened by petri.lehtinen #15034: Devguide should document best practices for stdlib exceptions http://bugs.python.org/issue15034 reopened by r.david.murray #15140: PEP 384 inconsistent with implementation http://bugs.python.org/issue15140 opened by pitrou #15141: IDLE horizontal scroll bar missing (Win-XPsp3) http://bugs.python.org/issue15141 opened by NyteHawk #15144: Possible integer overflow in operations with addresses and siz http://bugs.python.org/issue15144 opened by storchaka #15145: Faster *_find_max_char http://bugs.python.org/issue15145 opened by storchaka #15147: Remove packaging from the stdlib http://bugs.python.org/issue15147 opened by pitrou #15148: shutil.which() docstring could be clearer http://bugs.python.org/issue15148 opened by tshepang #15151: Documentation for Signature, Parameter and signature in inspec http://bugs.python.org/issue15151 opened by ncoghlan #15152: test_subprocess fqailures on awfully slow builtbots http://bugs.python.org/issue15152 opened by neologix #15158: Add support for multi-character delimiters in csv http://bugs.python.org/issue15158 opened by ramchandra.apte #15163: pydoc displays __loader__ as module data http://bugs.python.org/issue15163 opened by pitrou #15165: test_email: failure on Windows http://bugs.python.org/issue15165 opened by skrah #15166: Implement imp.get_tag() using sys.implementation http://bugs.python.org/issue15166 opened by brett.cannon #15167: Re-implement imp.get_magic() in pure Python http://bugs.python.org/issue15167 opened by brett.cannon #15168: Move importlib.test to test.importlib http://bugs.python.org/issue15168 opened by brett.cannon #15169: Clear C code under PyImport_ExecCodeModuleObject() http://bugs.python.org/issue15169 opened by brett.cannon #15170: Fix 64-bit building for buildbot scripts (2.7) http://bugs.python.org/issue15170 opened by skrah #15171: Fix 64-bit building for buildbot scripts (3.2) http://bugs.python.org/issue15171 opened by skrah #15172: Document nasm-2.10.01 as required version for openssl http://bugs.python.org/issue15172 opened by skrah #15174: amd64\python_d.exe -m test fails http://bugs.python.org/issue15174 opened by skrah #15175: pydoc -k zip throws segmentation fault http://bugs.python.org/issue15175 opened by shank #15178: Doctest should handle situations when test files are not reada http://bugs.python.org/issue15178 opened by bkabrda #15180: Cryptic traceback from os.path.join when mixing str & bytes http://bugs.python.org/issue15180 opened by ncoghlan #15182: find_library_file() should try to link http://bugs.python.org/issue15182 opened by jdemeyer #15183: it should be made clear that the statement in the --setup opti http://bugs.python.org/issue15183 opened by tshepang #15184: Test failure in test_sysconfig_module http://bugs.python.org/issue15184 opened by georg.brandl #15185: Validate callbacks in 'contextlib.ExitStack.callback()' http://bugs.python.org/issue15185 opened by Yury.Selivanov #15186: Support os.walk(dir_fd=) http://bugs.python.org/issue15186 opened by larry #15188: test_ldshared_value failure on OS X using python.org Pythons http://bugs.python.org/issue15188 opened by ned.deily #15189: tkinter.messagebox does not use the application's icon http://bugs.python.org/issue15189 opened by mark #15191: tkinter convenience dialogs don't use themed widgets http://bugs.python.org/issue15191 opened by mark #15192: test_bufio failures on Win64 buildbot http://bugs.python.org/issue15192 opened by pitrou #15194: libffi-3.0.11 update http://bugs.python.org/issue15194 opened by doko #15195: test_distutils fails when ARCHFLAGS is set on a Mac http://bugs.python.org/issue15195 opened by Marc.Abramowitz #15197: test_gettext failure on Win64 buildbot http://bugs.python.org/issue15197 opened by pitrou #15198: multiprocessing Pipe send of non-picklable objects doesn't rai http://bugs.python.org/issue15198 opened by Ian.Bell #15199: Default mimetype for javascript should be application/javascri http://bugs.python.org/issue15199 opened by bkabrda #15200: Faster os.walk http://bugs.python.org/issue15200 opened by storchaka #15201: C argument errors and Python arguments error are different http://bugs.python.org/issue15201 opened by ramchandra.apte #15202: followlinks/follow_symlinks/symlinks flags unification http://bugs.python.org/issue15202 opened by storchaka #15204: Deprecate the 'U' open mode http://bugs.python.org/issue15204 opened by storchaka #15205: distutils dereferences symlinks on Mac OS X but not on Linux http://bugs.python.org/issue15205 opened by olliewalsh #15206: uuid module falls back to unsuitable RNG http://bugs.python.org/issue15206 opened by christian.heimes #15207: mimetypes.read_windows_registry() uses the wrong regkey, creat http://bugs.python.org/issue15207 opened by dlchambers #15209: Re-raising exceptions from an expression http://bugs.python.org/issue15209 opened by Tyler.Crompton #15210: importlib.__init__ checks for the wrong exception when looking http://bugs.python.org/issue15210 opened by brett.cannon #15212: Rename SC_GLOBAL_EXPLICT to SC_GLOBAL_EXPLICIT in compiler mod http://bugs.python.org/issue15212 opened by Arfrever #15213: _PyOS_URandom documentation http://bugs.python.org/issue15213 opened by christian.heimes #15216: Support setting the encoding on a text stream after creation http://bugs.python.org/issue15216 opened by ncoghlan #15220: Reduce parsing overhead in email.feedparser.BufferedSubFile http://bugs.python.org/issue15220 opened by r.david.murray #15221: os.path.is*() may return False if path can't be accessed http://bugs.python.org/issue15221 opened by giampaolo.rodola #15222: mailbox.mbox writes without end-of-line at the file end. http://bugs.python.org/issue15222 opened by lilydjwg #665194: datetime-RFC2822 roundtripping http://bugs.python.org/issue665194 reopened by belopolsky Most recent 15 issues with no replies (15) ========================================== #15212: Rename SC_GLOBAL_EXPLICT to SC_GLOBAL_EXPLICIT in compiler mod http://bugs.python.org/issue15212 #15210: importlib.__init__ checks for the wrong exception when looking http://bugs.python.org/issue15210 #15205: distutils dereferences symlinks on Mac OS X but not on Linux http://bugs.python.org/issue15205 #15201: C argument errors and Python arguments error are different http://bugs.python.org/issue15201 #15199: Default mimetype for javascript should be application/javascri http://bugs.python.org/issue15199 #15198: multiprocessing Pipe send of non-picklable objects doesn't rai http://bugs.python.org/issue15198 #15195: test_distutils fails when ARCHFLAGS is set on a Mac http://bugs.python.org/issue15195 #15191: tkinter convenience dialogs don't use themed widgets http://bugs.python.org/issue15191 #15189: tkinter.messagebox does not use the application's icon http://bugs.python.org/issue15189 #15188: test_ldshared_value failure on OS X using python.org Pythons http://bugs.python.org/issue15188 #15182: find_library_file() should try to link http://bugs.python.org/issue15182 #15174: amd64\python_d.exe -m test fails http://bugs.python.org/issue15174 #15168: Move importlib.test to test.importlib http://bugs.python.org/issue15168 #15167: Re-implement imp.get_magic() in pure Python http://bugs.python.org/issue15167 #15163: pydoc displays __loader__ as module data http://bugs.python.org/issue15163 Most recent 15 issues waiting for review (15) ============================================= #15220: Reduce parsing overhead in email.feedparser.BufferedSubFile http://bugs.python.org/issue15220 #15212: Rename SC_GLOBAL_EXPLICT to SC_GLOBAL_EXPLICIT in compiler mod http://bugs.python.org/issue15212 #15209: Re-raising exceptions from an expression http://bugs.python.org/issue15209 #15207: mimetypes.read_windows_registry() uses the wrong regkey, creat http://bugs.python.org/issue15207 #15206: uuid module falls back to unsuitable RNG http://bugs.python.org/issue15206 #15204: Deprecate the 'U' open mode http://bugs.python.org/issue15204 #15202: followlinks/follow_symlinks/symlinks flags unification http://bugs.python.org/issue15202 #15200: Faster os.walk http://bugs.python.org/issue15200 #15199: Default mimetype for javascript should be application/javascri http://bugs.python.org/issue15199 #15194: libffi-3.0.11 update http://bugs.python.org/issue15194 #15186: Support os.walk(dir_fd=) http://bugs.python.org/issue15186 #15185: Validate callbacks in 'contextlib.ExitStack.callback()' http://bugs.python.org/issue15185 #15184: Test failure in test_sysconfig_module http://bugs.python.org/issue15184 #15180: Cryptic traceback from os.path.join when mixing str & bytes http://bugs.python.org/issue15180 #15178: Doctest should handle situations when test files are not reada http://bugs.python.org/issue15178 Top 10 most discussed issues (10) ================================= #1677: Ctrl-C will exit out of Python interpreter in Windows http://bugs.python.org/issue1677 18 msgs #10142: Support for SEEK_HOLE/SEEK_DATA http://bugs.python.org/issue10142 16 msgs #15030: PyPycLoader can't read cached .pyc files http://bugs.python.org/issue15030 16 msgs #444582: Finding programs in PATH, adding shutil.which http://bugs.python.org/issue444582 16 msgs #15147: Remove packaging from the stdlib http://bugs.python.org/issue15147 12 msgs #15209: Re-raising exceptions from an expression http://bugs.python.org/issue15209 12 msgs #15202: followlinks/follow_symlinks/symlinks flags unification http://bugs.python.org/issue15202 11 msgs #15206: uuid module falls back to unsuitable RNG http://bugs.python.org/issue15206 11 msgs #15133: tkinter.BooleanVar.get() behavior and docstring disagree http://bugs.python.org/issue15133 10 msgs #15139: Speed up threading.Condition wakeup http://bugs.python.org/issue15139 10 msgs Issues closed (80) ================== #3665: Support \u and \U escapes in regexes http://bugs.python.org/issue3665 closed by pitrou #4489: shutil.rmtree is vulnerable to a symlink attack http://bugs.python.org/issue4489 closed by hynek #5067: Error msg from using wrong quotes in JSON is unhelpful http://bugs.python.org/issue5067 closed by pitrou #5346: mailbox._singlefileMailbox.flush doesn't preserve file rights http://bugs.python.org/issue5346 closed by petri.lehtinen #5441: Convenience API for timeit.main http://bugs.python.org/issue5441 closed by ncoghlan #7360: [mailbox] race: mbox may lose data with concurrent access http://bugs.python.org/issue7360 closed by petri.lehtinen #7582: Use ISO timestamp in diff.py http://bugs.python.org/issue7582 closed by belopolsky #8916: Move PEP 362 (function signature objects) into inspect http://bugs.python.org/issue8916 closed by eric.araujo #9527: Add aware local time support to datetime module http://bugs.python.org/issue9527 closed by belopolsky #9559: mailbox.mbox creates new file when adding message to mbox http://bugs.python.org/issue9559 closed by petri.lehtinen #10376: ZipFile unzip is unbuffered http://bugs.python.org/issue10376 closed by pitrou #10571: "setup.py upload --sign" broken: TypeError: 'str' does not sup http://bugs.python.org/issue10571 closed by pitrou #11113: html.entities mapping dicts need updating? http://bugs.python.org/issue11113 closed by ezio.melotti #11626: Py_LIMITED_API on windows: unresolved symbol __imp___PyArg_Par http://bugs.python.org/issue11626 closed by loewis #11678: Add support for Arch Linux to platform.linux_distributions() http://bugs.python.org/issue11678 closed by python-dev #12559: gzip.open() needs an optional encoding argument http://bugs.python.org/issue12559 closed by nadeem.vawda #13062: Introspection generator and function closure state http://bugs.python.org/issue13062 closed by python-dev #13556: When tzinfo.utcoffset is out-of-bounds, the exception message http://bugs.python.org/issue13556 closed by belopolsky #13666: datetime documentation typos http://bugs.python.org/issue13666 closed by orsenthil #13685: argparse update help msg for % signs http://bugs.python.org/issue13685 closed by orsenthil #14127: add st_*time_ns fields to os.stat(), add ns keyword to os.*uti http://bugs.python.org/issue14127 closed by larry #14226: Expose dict_proxy type from descrobject.c http://bugs.python.org/issue14226 closed by eric.snow #14286: xxlimited.obj: unresolved external symbol __imp__PyObject_New http://bugs.python.org/issue14286 closed by loewis #14327: replace use of uname in the configury with macros set by AC_CA http://bugs.python.org/issue14327 closed by doko #14469: Python 3 documentation links http://bugs.python.org/issue14469 closed by orsenthil #14626: os module: use keyword-only arguments for dir_fd and nofollow http://bugs.python.org/issue14626 closed by georg.brandl #14698: test_posix failures - getpwduid()/initgroups()/getgroups() http://bugs.python.org/issue14698 closed by neologix #14742: test_tools very slow http://bugs.python.org/issue14742 closed by mark.dickinson #14785: Add sys._debugmallocstats() http://bugs.python.org/issue14785 closed by dmalcolm #14815: random_seed uses only 32-bits of hash on Win64 http://bugs.python.org/issue14815 closed by larry #14837: Better SSL errors http://bugs.python.org/issue14837 closed by pitrou #14906: rotatingHandler WindowsError http://bugs.python.org/issue14906 closed by vinay.sajip #14917: Make os.symlink on Win32 detect if target is directory http://bugs.python.org/issue14917 closed by larry #14923: Even faster UTF-8 decoding http://bugs.python.org/issue14923 closed by mark.dickinson #15008: PEP 362 "Signature Objects" reference implementation http://bugs.python.org/issue15008 closed by Yury.Selivanov #15042: Implemented PyState_AddModule, PyState_RemoveModule http://bugs.python.org/issue15042 closed by loewis #15055: dictnotes.txt is out of date http://bugs.python.org/issue15055 closed by pitrou #15061: hmac.secure_compare() leaks information about length of string http://bugs.python.org/issue15061 closed by christian.heimes #15079: pickle: Possibly misplaced test http://bugs.python.org/issue15079 closed by pitrou #15080: Cookie library doesn't parse date properly http://bugs.python.org/issue15080 closed by terry.reedy #15102: Fix 64-bit building for buildbot scripts (3.3) http://bugs.python.org/issue15102 closed by skrah #15118: uname and other os functions should return a struct sequence i http://bugs.python.org/issue15118 closed by larry #15124: _thread.LockType: Optimize lock deletion, acquisition of uncon http://bugs.python.org/issue15124 closed by pitrou #15135: HOWTOs doesn't link to "Idioms and Anti-Idioms" article http://bugs.python.org/issue15135 closed by terry.reedy #15137: Cleaned source of `cmd` module http://bugs.python.org/issue15137 closed by terry.reedy #15138: base64.urlsafe_b64**code are too slow http://bugs.python.org/issue15138 closed by gvanrossum #15142: Fix reference leak with types created using PyType_FromSpec http://bugs.python.org/issue15142 closed by pitrou #15143: Windows compile errors http://bugs.python.org/issue15143 closed by georg.brandl #15146: Implemented PyType_FromSpecWithBases http://bugs.python.org/issue15146 closed by loewis #15149: Release Schedule needs updating http://bugs.python.org/issue15149 closed by georg.brandl #15150: Windows build does not link http://bugs.python.org/issue15150 closed by loewis #15153: Add inspect.getgeneratorlocals http://bugs.python.org/issue15153 closed by python-dev #15154: remove "rmdir" argument from os.unlink, add "dir_fd" to os.rmd http://bugs.python.org/issue15154 closed by larry #15155: sporadic failure in RecvmsgSCTPStreamTest http://bugs.python.org/issue15155 closed by neologix #15156: Refactor HTMLParser.unescape to use html.entities.html5 http://bugs.python.org/issue15156 closed by ezio.melotti #15157: venvs should include pydoc http://bugs.python.org/issue15157 closed by python-dev #15159: Add failover for follow_symlinks and effective_ids where possi http://bugs.python.org/issue15159 closed by larry #15160: Add support for MIME header parsing to the new provisional ema http://bugs.python.org/issue15160 closed by r.david.murray #15161: add new-style os API to two missing functions http://bugs.python.org/issue15161 closed by python-dev #15162: help() says "This is the online help utility." even though it http://bugs.python.org/issue15162 closed by python-dev #15164: add platform.uname() namedtuple interface? http://bugs.python.org/issue15164 closed by larry #15173: Copyright/licensing statement in new venv module http://bugs.python.org/issue15173 closed by python-dev #15176: Clarify the behavior of listdir(fd) in both code and documenta http://bugs.python.org/issue15176 closed by larry #15177: Support os.fwalk(dir_fd=) http://bugs.python.org/issue15177 closed by larry #15179: An infinite loop happens when we use SysLogHandler with eventl http://bugs.python.org/issue15179 closed by python-dev #15181: importlib.h: suncc warnings http://bugs.python.org/issue15181 closed by pitrou #15187: test_shutil does not clean up after itself http://bugs.python.org/issue15187 closed by larry #15190: Allow whitespace and comments after line continuation characte http://bugs.python.org/issue15190 closed by eric.smith #15193: Exception AttributeError: "'NoneType' object has no attribute http://bugs.python.org/issue15193 closed by mark.dickinson #15196: os.path.realpath gets confused when symlinks include '..' http://bugs.python.org/issue15196 closed by o11c #15203: Accepting of os functions of (path, dir_fd) pair as argument http://bugs.python.org/issue15203 closed by ncoghlan #15208: Uparrow doesn't show previously typed variable or character http://bugs.python.org/issue15208 closed by ned.deily #15211: Test http://bugs.python.org/issue15211 closed by r.david.murray #15214: list.startswith() and list.remove() fails to catch consecutive http://bugs.python.org/issue15214 closed by petri.lehtinen #15215: socket module setblocking and settimeout problem http://bugs.python.org/issue15215 closed by pitrou #15217: os.listdir is missing in os.supports_dir_fd http://bugs.python.org/issue15217 closed by larry #15218: Check for all necessary dir_fd and follow_symlinks functions http://bugs.python.org/issue15218 closed by python-dev #15219: Leak in "_hashlib.new()" if argument is not a string http://bugs.python.org/issue15219 closed by amaury.forgeotdarc #415492: Compiler generates relative filenames http://bugs.python.org/issue415492 closed by brett.cannon #1644987: ./configure --prefix=/ breaks, won't build C modules http://bugs.python.org/issue1644987 closed by jcea

1 0

Bitbucket mirror?
by Tim Golden June 29, 2012

June 29, 2012

Just recently I'm sure I saw a post saying that the main Python repo was mirrored on bitbucket.org for the convenience of developers who could then fork to their own accounts. For the life of me I can't find it now. Can someone confirm and/or nudge me in the right direction, please? TJG

5 6

Python-Dev

June 2012