Mailman 3 September 2012 - Python-Dev

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

18 May '21

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

8 14

Reviving restricted mode?
by Guido van Rossum 14 Aug '14

14 Aug '14

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 05 Jul '13

05 Jul '13

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 16 Feb '13

16 Feb '13

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

Why no venv in existing directory?
by Stefan H. Holek 07 Jan '13

07 Jan '13

Hi All, While trying 3.3 beta I found that I cannot use my favorite virtualenv pattern with pyvenv: $ virtualenv . Installing.....done. $ pyvenv . Error: Directory exists: /Users/stefan/sandbox/foo I appreciate that this behavior is documented and was in the PEP from the start: "If the target directory already exists an error will be raised, unless the --clear or --upgrade option was provided." Still, I am curious what the rationale behind this restriction is. For me, being able to "bless" an existing directory with a virtualenv has always been one of its attractions. Thanks, Stefan -- Stefan H. Holek stefan(a)epy.co.at

7 8

PEP 3145 (With Contents)
by Eric Pruitt 25 Dec '12

25 Dec '12

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 22 Dec '12

22 Dec '12

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

Understanding the buffer API
by Jeff Allen 18 Dec '12

18 Dec '12

I'm implementing the buffer API and some of memoryview for Jython. I have read with interest, and mostly understood, the discussion in Issue #10181 that led to the v3.3 re-implementation of memoryview and much-improved documentation of the buffer API. Although Jython is targeting v2.7 at the moment, and 1-D bytes (there's no Jython NumPy), I'd like to lay a solid foundation that benefits from the recent CPython work. I hope that some of the complexity in memoryview stems from legacy considerations I don't have to deal with in Jython. I am puzzled that PEP 3118 makes some specifications that seem unnecessary and complicate the implementation. Would those who know the API inside out answer a few questions? My understanding is this: When a consumer requests a buffer from the exporter it specifies using flags how it intends to navigate it. If the buffer actually needs more apparatus than the consumer proposes, this raises an exception. If the buffer needs less apparatus than the consumer proposes, the exporter has to supply what was asked for. For example, if the consumer sets PyBUF_STRIDES, and the buffer can only be navigated by using suboffsets (PIL-style) this raises an exception. Alternatively, if the consumer sets PyBUF_STRIDES, and the buffer is just a simple byte array, the exporter has to supply shape and strides arrays (with trivial values), since the consumer is going to use those arrays. Is there any harm is supplying shape and strides when they were not requested? The PEP says: "PyBUF_ND ... If this is not given then shape will be NULL". It doesn't stipulate that strides will be null if PyBUF_STRIDES is not given, but the library documentation says so. suboffsets is different since even when requested, it will be null if not needed. Similar, but simpler, the PEP says "PyBUF_FORMAT ... If format is not explicitly requested then the format must be returned as NULL (which means "B", or unsigned bytes)". What would be the harm in returning "B"? One place where this really matters is in the implementation of memoryview. PyMemoryView requests a buffer with the flags PyBUF_FULL_RO, so even a simple byte buffer export will come with shape, strides and format. A consumer (of the memoryview's buffer API) might specify PyBUF_SIMPLE: according to the PEP I can't simply give it the original buffer since required fields (that the consumer will presumably not access) are not NULL. In practice, I'd like to: what could possibly go wrong? Jeff Allen

4 13

Tru64 support
by Andrew Svetlov 27 Nov '12

27 Nov '12

Unittests for subprocess module has weird comment: We cannot use os.path.realpath to canonicalize the path, since it doesn't expand Tru64 {memb} strings. See bug 1063571. http://hg.python.org/cpython/file/82ae284cd5f1/Lib/test/test_subprocess.py#… is link to comment, http://bugs.python.org/issue1063571 — issue in bugtracker. Is it still up to date? Bug has been created in 2004. I don't see Tru64 in list of available buildbots. Do we need to care about this platform? And how to make sure what existing code works fine for that? Or maybe we can drop support for Tru64 as well as we already does it for, say, VMS? -- Thanks, Andrew Svetlov

10 20

Python Bug Day in October
by Éric Araujo 26 Oct '12

26 Oct '12

Hi all, The Montreal-Python user group would like to host a bug day on October 27 (to be confirmed) at a partner university in Montreal. It would be cool to do a bug day on IRC like we used to (and in other physical locations if people want to!) to get new contributors and close bugs. What do you think? Cheers

10 24

what´s new 3.3
by Kristján Valur Jónsson 05 Oct '12

05 Oct '12

Hi there. Not having kept up, I realized I failed to contribute to the What's new thingie. Here's stuff I remember working on and putting in: 1. pickling support for built in iterators (#14288) 2. inter process socket duplication for windows (#14310) 3. Progress callback for gc module (#10576) 4. Faster locking on windows (#15038) DiSome of this should probably be mentioned in the What's new document, even if only in its online version. K

3 2

Stdlib and timezones, again
by Lennart Regebro 04 Oct '12

04 Oct '12

With 3.3 out, it's time to bring up something for 3.4. And it's about pytz and stdlib, basically. And we have been over that again, but I have a proposal anyway. The problem with including pytz in the stdlib is that it contains the tz/zoneinfo/Olson database, and it updates much more often than Python does. I propose to solve this problem in the following way: 1. Merge the functionality of pytz into the stdlib datetime module. That means extending datetime.tzinfo with the localize() function and and adding a top-level datetime.timezone() function. any other extra functionality pytz has. 2. The datetime.timezone() function will work as the pytz.timezone() function, ie return a tzinfo object from the tz database. 3. However, Python will not include the database. Instead it will use the one that the OS provides, if it provides one (ie Unices, including OS X if I remember correctly). 4. On any other OS, datetime.timezone() will return an error explaining that no tz database can be found, but that it is available in the module 'pytzdata' which then will need to be created. If this module is installed, the datetime.timezone() function will prefer that database before the OS database. 5. We can also consider implementing something like the get_localzone() function of my module tzlocal. This solves two problems. i. We have real, useful timezone support in Python. For Unix, it's included, for all other systems, it's just an extra module. The extra module can also be installed to give Python up to date tz information even when the operating system is outdated and unsupported and no longer receiving updates. ii. pytz is_dst flag becomes included in stdlib, solving one of the few imperfections in the current library. What do you say? Is this a path worth pursuing? //Lennart

23 77

experimental: Misc/NEWS included in docs
by Georg Brandl 02 Oct '12

02 Oct '12

Hi, at http://docs.python.org/3.3/whatsnew/news.html, there is now a rendering of Misc/NEWS with tracker links and a crude filtering capability. I thought that this will complement the "whatsnew" documents nicely for people looking for more detail. Please let me know if it's useful, or what could be done to make it *more* useful. cheers, Georg

6 6

[RELEASED] Python 3.3.0
by Georg Brandl 02 Oct '12

02 Oct '12

On behalf of the Python development team, I'm delighted to announce the Python 3.3.0 final release. Python 3.3 includes a range of improvements of the 3.x series, as well as easier porting between 2.x and 3.x. Major new features and changes in the 3.3 release series are: * PEP 380, syntax for delegating to a subgenerator ("yield from") * PEP 393, flexible string representation (doing away with the distinction between "wide" and "narrow" Unicode builds) * A C implementation of the "decimal" module, with up to 120x speedup for decimal-heavy applications * The import system (__import__) now based on importlib by default * The new "lzma" module with LZMA/XZ support * PEP 397, a Python launcher for Windows * PEP 405, virtual environment support in core * PEP 420, namespace package support * PEP 3151, reworking the OS and IO exception hierarchy * PEP 3155, qualified name for classes and functions * PEP 409, suppressing exception context * PEP 414, explicit Unicode literals to help with porting * PEP 418, extended platform-independent clocks in the "time" module * PEP 412, a new key-sharing dictionary implementation that significantly saves memory for object-oriented code * PEP 362, the function-signature object * The new "faulthandler" module that helps diagnosing crashes * The new "unittest.mock" module * The new "ipaddress" module * The "sys.implementation" attribute * A policy framework for the email package, with a provisional (see PEP 411) policy that adds much improved unicode support for email header parsing * A "collections.ChainMap" class for linking mappings to a single unit * Wrappers for many more POSIX functions in the "os" and "signal" modules, as well as other useful functions such as "sendfile()" * Hash randomization, introduced in earlier bugfix releases, is now switched on by default In total, almost 500 API items are new or improved in Python 3.3. For a more extensive list of changes in 3.3.0, see http://docs.python.org/3.3/whatsnew/3.3.html To download Python 3.3.0 visit: http://www.python.org/download/releases/3.3.0/ This is a production release, please report any bugs to http://bugs.python.org/ Enjoy! -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.3's contributors)

13 15

Benchmarking Python 3.3 against Python 2.7 (wide build)
by Brett Cannon 01 Oct '12

01 Oct '12

I am presenting the talk "Python 3.3: Trust Me, It's Better Than 2.7" as PyCon Argentina and Brasil (and US if they accept the talk). As part of that talk I need to be able to benchmark Python 3.3 against 2.7 (both from tip) using the unladen benchmarks (which now include benchmarks from PyPy that can be relatively easily ported to Python 3). To make sure the unladen benchmarks run fine against Python 3.3, I did a fast run of the benchmarks. I figured people might be interested in the quick-and-dirty results on my 2 GHz Intel Core i7 MacBook Pro w/ 8 GB RAM and no attempt to control for performance beyond not actively browsing the web. As I said, quick-and-dirty and not authoritative; all done just to make sure all the benchmarks could run to completion (including the django, html5lib, and genshi benchmarks which are only on my laptop ATM until those projects cut a release with official Python 3 support). One thing to keep in mind is that many benchmarks use a raw str for things, so the benchmarks often compare Python 2.7 str vs. Python 3.3 str (i.e. str vs. unicode). While this might seem unfair, this is what real-world comparisons in performance will be from users so it's an (somewhat unfair) comparison that we just have to live with. I might take the time to try to make some tests run under both raw strings and unicode so both comparisons are available. If you care about helping out with the benchmarks (e.g. helping spot where the iteration counts should be higher, etc.) then head over to the speed@mailing list. > python3 perf.py -T --basedir ../benchmarks -f -b py3k ../cpython/builds/2.7-wide/bin/python ../cpython/builds/3.3/bin/python3.3 ... output about the command line for the benchmarks ... ### 2to3 ### 0.785234 -> 0.722169: 1.09x faster ### call_method ### Min: 0.491433 -> 0.414841: 1.18x faster Avg: 0.493640 -> 0.416564: 1.19x faster Significant (t=127.21) Stddev: 0.00170 -> 0.00162: 1.0513x smaller ### call_method_slots ### Min: 0.492749 -> 0.416280: 1.18x faster Avg: 0.497888 -> 0.419275: 1.19x faster Significant (t=61.72) Stddev: 0.00433 -> 0.00237: 1.8304x smaller ### call_method_unknown ### Min: 0.575536 -> 0.427234: 1.35x faster Avg: 0.577286 -> 0.433428: 1.33x faster Significant (t=66.09) Stddev: 0.00117 -> 0.00835: 7.1621x larger ### call_simple ### Min: 0.413011 -> 0.338923: 1.22x faster Avg: 0.415862 -> 0.340699: 1.22x faster Significant (t=111.94) Stddev: 0.00223 -> 0.00134: 1.6616x smaller ### chaos ### Min: 0.375286 -> 0.435456: 1.16x slower Avg: 0.382798 -> 0.459515: 1.20x slower Significant (t=-5.01) Stddev: 0.01116 -> 0.03234: 2.8980x larger ### fastpickle ### Min: 0.853560 -> 0.770580: 1.11x faster Avg: 0.879498 -> 0.776249: 1.13x faster Significant (t=8.24) Stddev: 0.02771 -> 0.00407: 6.7995x smaller ### float ### Min: 0.476596 -> 0.391101: 1.22x faster Avg: 0.486164 -> 0.411553: 1.18x faster Significant (t=9.07) Stddev: 0.01049 -> 0.01511: 1.4411x larger ### formatted_logging ### Min: 0.346703 -> 0.451643: 1.30x slower Avg: 0.351218 -> 0.454626: 1.29x slower Significant (t=-51.50) Stddev: 0.00376 -> 0.00246: 1.5265x smaller ### genshi ### Min: 0.275107 -> 0.294309: 1.07x slower Avg: 0.287433 -> 0.299026: 1.04x slower Significant (t=-3.82) Stddev: 0.01077 -> 0.00467: 2.3044x smaller ### go ### Min: 0.719160 -> 0.781042: 1.09x slower Avg: 0.729322 -> 0.798135: 1.09x slower Significant (t=-8.54) Stddev: 0.01300 -> 0.01248: 1.0415x smaller ### hexiom2 ### 203.842661 -> 187.107363: 1.09x faster ### iterative_count ### Min: 0.145088 -> 0.153285: 1.06x slower Avg: 0.146369 -> 0.154425: 1.06x slower Significant (t=-9.21) Stddev: 0.00134 -> 0.00142: 1.0569x larger ### json_dump_v2 ### Min: 3.512367 -> 4.040813: 1.15x slower Avg: 3.521879 -> 4.057966: 1.15x slower Significant (t=-64.29) Stddev: 0.01071 -> 0.01526: 1.4247x larger ### json_load ### Min: 1.024560 -> 0.642353: 1.60x faster Avg: 1.025255 -> 0.644000: 1.59x faster Significant (t=426.59) Stddev: 0.00049 -> 0.00194: 3.9240x larger ### mako_v2 ### Min: 0.137584 -> 0.287701: 2.09x slower Avg: 0.140620 -> 0.293204: 2.09x slower Significant (t=-296.14) Stddev: 0.00243 -> 0.00272: 1.1195x larger ### meteor_contest ### Min: 0.284739 -> 0.254285: 1.12x faster Avg: 0.286174 -> 0.255323: 1.12x faster Significant (t=38.02) Stddev: 0.00124 -> 0.00133: 1.0725x larger ### nbody ### Min: 0.491416 -> 0.336127: 1.46x faster Avg: 0.493339 -> 0.337467: 1.46x faster Significant (t=185.50) Stddev: 0.00164 -> 0.00092: 1.7927x smaller ### normal_startup ### Min: 0.639285 -> 0.898157: 1.40x slower Avg: 0.645513 -> 0.901586: 1.40x slower Significant (t=-90.10) Stddev: 0.00575 -> 0.00270: 2.1309x smaller ### nqueens ### Min: 0.399351 -> 0.429575: 1.08x slower Avg: 0.403643 -> 0.430284: 1.07x slower Significant (t=-9.83) Stddev: 0.00603 -> 0.00053: 11.3092x smaller ### pathlib ### Min: 0.137462 -> 0.170506: 1.24x slower Avg: 0.145370 -> 0.172849: 1.19x slower Significant (t=-11.09) Stddev: 0.01232 -> 0.00128: 9.6403x smaller ### pidigits ### Min: 0.400265 -> 0.379307: 1.06x faster Avg: 0.401755 -> 0.381171: 1.05x faster Significant (t=14.65) Stddev: 0.00259 -> 0.00178: 1.4496x smaller ### raytrace ### Min: 1.770596 -> 1.958350: 1.11x slower Avg: 1.773719 -> 1.968401: 1.11x slower Significant (t=-44.19) Stddev: 0.00439 -> 0.00882: 2.0099x larger ### regex_effbot ### Min: 0.076566 -> 0.098124: 1.28x slower Avg: 0.077491 -> 0.098696: 1.27x slower Significant (t=-54.47) Stddev: 0.00052 -> 0.00069: 1.3227x larger ### regex_v8 ### Min: 0.091530 -> 0.109116: 1.19x slower Avg: 0.092308 -> 0.113627: 1.23x slower Significant (t=-5.72) Stddev: 0.00088 -> 0.00829: 9.4271x larger ### richards ### Min: 0.257974 -> 0.232134: 1.11x faster Avg: 0.259248 -> 0.234325: 1.11x faster Significant (t=23.80) Stddev: 0.00144 -> 0.00185: 1.2823x larger ### simple_logging ### Min: 0.326569 -> 0.416797: 1.28x slower Avg: 0.331694 -> 0.418844: 1.26x slower Significant (t=-36.32) Stddev: 0.00523 -> 0.00122: 4.3004x smaller ### spectral_norm ### Min: 0.483011 -> 0.741558: 1.54x slower Avg: 0.487128 -> 0.749741: 1.54x slower Significant (t=-57.40) Stddev: 0.00512 -> 0.00886: 1.7299x larger ### startup_nosite ### Min: 0.220444 -> 0.374521: 1.70x slower Avg: 0.222773 -> 0.376785: 1.69x slower Significant (t=-176.17) Stddev: 0.00166 -> 0.00221: 1.3331x larger ### threaded_count ### Min: 0.171352 -> 0.151892: 1.13x faster Avg: 0.183180 -> 0.153634: 1.19x faster Significant (t=8.12) Stddev: 0.00801 -> 0.00140: 5.7241x smaller ### unpack_sequence ### Min: 0.000075 -> 0.000061: 1.23x faster Avg: 0.000101 -> 0.000065: 1.54x faster Significant (t=206.90) Stddev: 0.00001 -> 0.00000: 3.2374x smaller The following not significant results are hidden, use -v to show them: chameleon, fannkuch, fastunpickle, regex_compile, silent_logging ### django ### Min: 0.868956 -> 0.894571: 1.03x slower Avg: 0.873620 -> 0.905274: 1.04x slower Significant (t=-6.97) Stddev: 0.00313 -> 0.00966: 3.0912x larger ### genshi ### Min: 0.269615 -> 0.286348: 1.06x slower Avg: 0.272206 -> 0.290708: 1.07x slower Significant (t=-12.29) Stddev: 0.00253 -> 0.00526: 2.0793x larger ### html5lib ### 12.279808 -> 11.862586: 1.04x faster

7 15

Re: [Python-Dev] benchmarks: Force map to a list to guarantee the calculations are performed under
by Antoine Pitrou 30 Sep '12

30 Sep '12

On Mon, 1 Oct 2012 01:00:42 +0200 (CEST) brett.cannon <python-checkins(a)python.org> wrote: > http://hg.python.org/benchmarks/rev/e9f911fd9bd3 > changeset: 184:e9f911fd9bd3 > user: Brett Cannon <brett(a)python.org> > date: Sun Sep 30 19:00:32 2012 -0400 > summary: > Force map to a list to guarantee the calculations are performed under > Python 3. [...] > def eval_times_u(func, u): > - return map(func, ((i,u) for i in xrange(len(list(u))))) > + return list(imap(func, ((i,u) for i in xrange(len(list(u)))))) Ugh, can't you use a list comprehension instead? The code would be much more idiomatic. Regards Antoine. -- Software development and contracting: http://pro.pitrou.net

2 1

Failed issue tracker submission
by Python tracker 30 Sep '12

30 Sep '12

The node specified by the designator in the subject of your message ("16304") does not exist. Subject was: "[issue16304]" Mail Gateway Help ================= Incoming messages are examined for multiple parts: . In a multipart/mixed message or part, each subpart is extracted and examined. The text/plain subparts are assembled to form the textual body of the message, to be stored in the file associated with a "msg" class node. Any parts of other types are each stored in separate files and given "file" class nodes that are linked to the "msg" node. . In a multipart/alternative message or part, we look for a text/plain subpart and ignore the other parts. . A message/rfc822 is treated similar tomultipart/mixed (except for special handling of the first text part) if unpack_rfc822 is set in the mailgw config section. Summary ------- The "summary" property on message nodes is taken from the first non-quoting section in the message body. The message body is divided into sections by blank lines. Sections where the second and all subsequent lines begin with a ">" or "|" character are considered "quoting sections". The first line of the first non-quoting section becomes the summary of the message. Addresses --------- All of the addresses in the To: and Cc: headers of the incoming message are looked up among the user nodes, and the corresponding users are placed in the "recipients" property on the new "msg" node. The address in the From: header similarly determines the "author" property of the new "msg" node. The default handling for addresses that don't have corresponding users is to create new users with no passwords and a username equal to the address. (The web interface does not permit logins for users with no passwords.) If we prefer to reject mail from outside sources, we can simply register an auditor on the "user" class that prevents the creation of user nodes with no passwords. Actions ------- The subject line of the incoming message is examined to determine whether the message is an attempt to create a new item or to discuss an existing item. A designator enclosed in square brackets is sought as the first thing on the subject line (after skipping any "Fwd:" or "Re:" prefixes). If an item designator (class name and id number) is found there, the newly created "msg" node is added to the "messages" property for that item, and any new "file" nodes are added to the "files" property for the item. If just an item class name is found there, we attempt to create a new item of that class with its "messages" property initialized to contain the new "msg" node and its "files" property initialized to contain any new "file" nodes. Triggers -------- Both cases may trigger detectors (in the first case we are calling the set() method to add the message to the item's spool; in the second case we are calling the create() method to create a new node). If an auditor raises an exception, the original message is bounced back to the sender with the explanatory message given in the exception. Return-Path: <python-dev(a)python.org> X-Original-To: report(a)bugs.python.org Delivered-To: roundup+tracker(a)psf.upfronthosting.co.za Received: from mail.python.org (mail.python.org [82.94.164.166]) by psf.upfronthosting.co.za (Postfix) with ESMTPS id C96C81CA8C for <report(a)bugs.python.org>; Mon, 1 Oct 2012 00:05:31 +0200 (CEST) Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3XVLKR40JNzNYF for <report(a)bugs.python.org>; Mon, 1 Oct 2012 00:05:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1349042731; bh=VvsXcY86pi/c+BeJIZc+70zwVxaiJ7YyKuEt7uYQ3Tc=; h=MIME-Version:Content-Type:Content-Transfer-Encoding:From:To: Subject:Message-Id:Date; b=JIb9A8mKbs/8mEf6lMLk3yCyEqivXstaCqDmc1Bx/B8VveRxdmlBnXCIdktlJpDXA e+ffB/whCObLiza0eN0IM8SVH012oUCUHsjGyE/9KMYXzgDLjqGhVQl65OD7lZ0did Go+K7962YIYqsKcJFoEDsTBu0OKNroH9FqedZq1M= Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 01 Oct 2012 00:05:31 +0200 Received: from virt-7yvsjn.psf.osuosl.org (virt-7yvsjn.psf.osuosl.org [140.211.10.72]) by mail.python.org (Postfix) with ESMTP for <report(a)bugs.python.org>; Mon, 1 Oct 2012 00:05:30 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 From: python-dev(a)python.org To: report(a)bugs.python.org Subject: [issue16304] Message-Id: <3XVLKR40JNzNYF(a)mail.python.org> Date: Mon, 1 Oct 2012 00:05:31 +0200 (CEST) TmV3IGNoYW5nZXNldCA0MjU4MjQ4YTQ0YzcgYnkgTmFkZWVtIFZhd2RhIGluIGJyYW5jaCAnMy4z JzoKSXNzdWUgIzE2MzA0OiBGdXJ0aGVyIHBlcmZvcm1hbmNlIGltcHJvdmVtZW50cyBmb3IgQloy RmlsZS4KaHR0cDovL2hnLnB5dGhvbi5vcmcvY3B5dGhvbi9yZXYvNDI1ODI0OGE0NGM3CgoKTmV3 IGNoYW5nZXNldCBhYmI1YzViZGU4NzIgYnkgTmFkZWVtIFZhd2RhIGluIGJyYW5jaCAnZGVmYXVs dCc6Ck1lcmdlOiAjMTYzMDQ6IEZ1cnRoZXIgcGVyZm9ybWFuY2UgaW1wcm92ZW1lbnRzIGZvciBC WjJGaWxlLgpodHRwOi8vaGcucHl0aG9uLm9yZy9jcHl0aG9uL3Jldi9hYmI1YzViZGU4NzIK

1 0

Re: [Python-Dev] [Python-checkins] cpython (3.3): Change libmpdec to use ANSI code in strict ansi mode as inline asm isn't
by Stefan Krah 30 Sep '12

30 Sep '12

christian.heimes <python-checkins(a)python.org> wrote: > +/* ASM isn't available in strict ansi C mode */ > +#if defined(ASM) && defined(__STRICT_ANSI__) > + #undef ASM > + #define ANSI > +#endif I'm not too fond of this solution: the libmpdec build output should always be accurate. Now you have ... -ansi -DCONFIG_64=1 -DASM=1 ... but the build is silently non-asm. Like for pymath.c, __asm__ is tested for and selected in ./configure. So I'll replace asm with __asm__, same as in pymath.c and ceval.c. Stefan Krah

1 1

buildbot with -O
by Benjamin Peterson 30 Sep '12

30 Sep '12

In light of issue #16046, I think it would be helpful to have a buildbot running the testsuite with -O enabled. -- Regards, Benjamin

4 5

[RELEASED] Python 3.3.0 release candidate 3
by Georg Brandl 30 Sep '12

30 Sep '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On behalf of the Python development team, I'm delighted to announce the third release candidate of Python 3.3.0. This is a preview release, and its use is not recommended in production settings. Python 3.3 includes a range of improvements of the 3.x series, as well as easier porting between 2.x and 3.x. Major new features and changes in the 3.3 release series are: * PEP 380, syntax for delegating to a subgenerator ("yield from") * PEP 393, flexible string representation (doing away with the distinction between "wide" and "narrow" Unicode builds) * A C implementation of the "decimal" module, with up to 80x speedup for decimal-heavy applications * The import system (__import__) now based on importlib by default * The new "lzma" module with LZMA/XZ support * PEP 397, a Python launcher for Windows * PEP 405, virtual environment support in core * PEP 420, namespace package support * PEP 3151, reworking the OS and IO exception hierarchy * PEP 3155, qualified name for classes and functions * PEP 409, suppressing exception context * PEP 414, explicit Unicode literals to help with porting * PEP 418, extended platform-independent clocks in the "time" module * PEP 412, a new key-sharing dictionary implementation that significantly saves memory for object-oriented code * PEP 362, the function-signature object * The new "faulthandler" module that helps diagnosing crashes * The new "unittest.mock" module * The new "ipaddress" module * The "sys.implementation" attribute * A policy framework for the email package, with a provisional (see PEP 411) policy that adds much improved unicode support for email header parsing * A "collections.ChainMap" class for linking mappings to a single unit * Wrappers for many more POSIX functions in the "os" and "signal" modules, as well as other useful functions such as "sendfile()" * Hash randomization, introduced in earlier bugfix releases, is now switched on by default In total, almost 500 API items are new or improved in Python 3.3. For a more extensive list of changes in 3.3.0, see http://docs.python.org/3.3/whatsnew/3.3.html To download Python 3.3.0 visit: http://www.python.org/download/releases/3.3.0/ Please consider trying Python 3.3.0 with your code and reporting any bugs you may notice to: http://bugs.python.org/ Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.3's contributors) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlBf+0cACgkQN9GcIYhpnLBqfgCglbN63XUr2m4Ya4ff8Hza1Axl SgMAniQZRJi8uYfeqltf5/G4QV/+SdWT =KXTo -----END PGP SIGNATURE-----

14 23

"Decimal(2) != float(2)"???
by Jan Kaliszewski 30 Sep '12

30 Sep '12

Hello, In http://docs.python.org/release/3.2.3/reference/expressions.html#in we read: "[...] This can create the illusion of non-transitivity between supported cross-type comparisons and unsupported comparisons. For example, Decimal(2) == 2 and 2 == float(2) but Decimal(2) != float(2)." (The same is in the 3.3 docs). But: Python 3.2.3 (default, Sep 10 2012, 18:14:40) [GCC 4.6.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import decimal >>> decimal.Decimal(2) == float(2) True Is it a bug in the docs or in Python itself? (I checked that in 3.2, but it may be true for 3.3 as well) Regards. *j

4 3

Re: [Python-Dev] make decimal the default non-integer instead of float?
by Gregory P. Smith 29 Sep '12

29 Sep '12

-cc: python-dev +cc: python-ideas On Sat, Sep 29, 2012 at 11:39 AM, Chris Angelico <rosuav(a)gmail.com> wrote: > On Sun, Sep 30, 2012 at 4:26 AM, Brett Cannon <brett(a)python.org> wrote: > > Does this mean we want to re-open the discussion about decimal constants? > > Last time this came up I think we decided that we wanted to wait for > > cdecimal (which is obviously here) and work out how to handle contexts, > the > > syntax, etc. > > Just to throw a crazy idea out: How bad a change would it be to make > decimal actually the default? > > (Caveat: I've not worked with decimal/cdecimal to any real extent and > don't know its limitations etc.) > Painful for existing code, unittests and extension modules. Definitely python-ideas territory (thread moved there with an appropriate subject). I'm not surprised at all that a decimal type can be "fast" in an interpreted language due to the already dominant interpreter overhead. I wish all spreadsheets had used decimals from day one rather than binary floating point (blame Lotus?). Think of the trouble that would have saved the world. -gps

1 0

str.format bug again
by Ben Wolfson 29 Sep '12

29 Sep '12

There's a patch for this bug: http://bugs.python.org/issue12014 that needs reviewed. Petri Lehtinen made some (very minor) comments back in May; otherwise it's been neglected. I've brought this up occasionally here in the past; it would be great if someone could just give it a thumbs up or down (or say what needs to be changed, or whatever). -- Ben Wolfson "Human kind has used its intelligence to vary the flavour of drinks, which may be sweet, aromatic, fermented or spirit-based. ... Family and social life also offer numerous other occasions to consume drinks for pleasure." [Larousse, "Drink" entry]

3 3

Deprecating "U" open mode
by Serhiy Storchaka 28 Sep '12

28 Sep '12

Since Python 2.3 many open-like functions supports "Universal line mode" (PEP 278 [1]). Since 3.0 (and 2.6) PEP 3116 [2] suggests better alternative -- io.TextWrapper. In issue15204 [3] proposed to deprecate "U" mode in open-like functions. In fact I found only three places where "U" mode is mentioned in the standard library: * builtin open (io.open) (almost ignored); * fileinput (transparently passed to open); * zipfile (inefficient and inconsistent implementation). Is someone uses "U" mode and has objections? [1] http://www.python.org/dev/peps/pep-0278/ [2] http://www.python.org/dev/peps/pep-3116/ [3] http://bugs.python.org/issue15204

2 1

Summary of Python tracker Issues
by Python tracker 28 Sep '12

28 Sep '12

ACTIVITY SUMMARY (2012-09-21 - 2012-09-28) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 3754 (+23) closed 24106 (+61) total 27860 (+84) Open issues with patches: 1662 Issues opened (52) ================== #16000: test_curses should use unittest http://bugs.python.org/issue16000 opened by chris.jerdonek #16001: small ints: cache string representation http://bugs.python.org/issue16001 opened by haypo #16003: thread_PyThread_start_new_thread fails with a generic error http://bugs.python.org/issue16003 opened by kristjan.jonsson #16004: Add `make touch` to 2.7 Makefile http://bugs.python.org/issue16004 opened by chris.jerdonek #16005: smtplib.SMTP().sendmail() and rset() http://bugs.python.org/issue16005 opened by DDarko #16007: Improved Error message for failing re expressions http://bugs.python.org/issue16007 opened by lingster #16009: Json error messages could provide more information about the e http://bugs.python.org/issue16009 opened by Luka.Rahne #16011: "in" should be consistent with return value of __contains__ http://bugs.python.org/issue16011 opened by nparikh #16013: small csv reader bug http://bugs.python.org/issue16013 opened by arigo #16023: IDLE freezes on ^5 or ^6 (Un-)Tabify Region with OS X Cocoa Tk http://bugs.python.org/issue16023 opened by szellmeyer #16024: Doc cleanup regarding path=fd, dir_fd, follow_symlinks, etc http://bugs.python.org/issue16024 opened by larry #16025: Minor corrections to the zipfile documentation http://bugs.python.org/issue16025 opened by storchaka #16026: csv.DictReader argument names documented incorrectly http://bugs.python.org/issue16026 opened by petere #16027: pkgutil doesn't support frozen modules http://bugs.python.org/issue16027 opened by lemburg #16029: pickle.dumps(xrange(sys.maxsize)) produces xrange(0) http://bugs.python.org/issue16029 opened by akira #16030: xrange repr broken for large arguments http://bugs.python.org/issue16030 opened by mark.dickinson #16034: bz2 module appears slower in Python 3.x versus Python 2.x http://bugs.python.org/issue16034 opened by victorhooi #16036: simplify int() signature docs http://bugs.python.org/issue16036 opened by chris.jerdonek #16037: httplib: header parsing is not delimited http://bugs.python.org/issue16037 opened by christian.heimes #16038: ftplib: unlimited readline() from connection http://bugs.python.org/issue16038 opened by christian.heimes #16039: imaplib: unlimited readline() from connection http://bugs.python.org/issue16039 opened by christian.heimes #16040: nntplib: unlimited readline() from connection http://bugs.python.org/issue16040 opened by christian.heimes #16041: poplib: unlimited readline() from connection http://bugs.python.org/issue16041 opened by christian.heimes #16042: smtplib: unlimited readline() from connection http://bugs.python.org/issue16042 opened by christian.heimes #16043: xmlrpc: gzip_decode has unlimited read() http://bugs.python.org/issue16043 opened by christian.heimes #16044: xml.etree.ElementTree.Element: append method iterator param is http://bugs.python.org/issue16044 opened by kirpit #16045: add more unit tests for built-in int() http://bugs.python.org/issue16045 opened by chris.jerdonek #16047: Tools/freeze no longer works in Python 3 http://bugs.python.org/issue16047 opened by lemburg #16048: Tutorial-classes-remarks: replace paragragh http://bugs.python.org/issue16048 opened by terry.reedy #16049: Create abstract base classes by inheritance rather than a dire http://bugs.python.org/issue16049 opened by rhettinger #16050: ctypes: callback from C++ to Python fails with Illegal Instruc http://bugs.python.org/issue16050 opened by Opilki_Inside #16053: "strict" parameter is not documented in csv module http://bugs.python.org/issue16053 opened by storchaka #16055: incorrect error text for int(base=1000, x='1') http://bugs.python.org/issue16055 opened by chris.jerdonek #16056: shadowed test names in std lib regression tests http://bugs.python.org/issue16056 opened by xdegaye #16057: Subclasses of JSONEncoder should not be insturcted to call JSO http://bugs.python.org/issue16057 opened by Justin.Lebar #16058: ConfigParser no longer deepcopy compatible in 2.7 http://bugs.python.org/issue16058 opened by rbcollins #16059: Serialize MD5 computation-state and resume later http://bugs.python.org/issue16059 opened by Ye.Yuan #16061: performance regression in string replace for 3.3 http://bugs.python.org/issue16061 opened by BreamoreBoy #16062: Socket closed prematurely in httplib for https http://bugs.python.org/issue16062 opened by ABR #16063: HMAC trans_5C is a string, causing a TypeError http://bugs.python.org/issue16063 opened by Adam.Glenn #16065: Python/distutils setup.py: passing --prefix / makes --root ign http://bugs.python.org/issue16065 opened by arschficker #16066: Truncated POST data in CGI script on Windows 7 http://bugs.python.org/issue16066 opened by Alexander.Martin #16067: UAC prompt for installation shows temporary file name http://bugs.python.org/issue16067 opened by breyed #16070: Structure and native Structure (LittleEndianStructure on Windo http://bugs.python.org/issue16070 opened by hct #16071: fix link to email.message.Message in mailbox docs http://bugs.python.org/issue16071 opened by chris.jerdonek #16074: bad error in rename http://bugs.python.org/issue16074 opened by v+python #16076: xml.etree.ElementTree.Element is no longer pickleable http://bugs.python.org/issue16076 opened by einarfd #16077: fix code example in docs for built-in reduce() http://bugs.python.org/issue16077 opened by chris.jerdonek #16079: list duplicate test names with patchcheck http://bugs.python.org/issue16079 opened by xdegaye #16081: Fix compile warnings in thread_pthread.h http://bugs.python.org/issue16081 opened by bbrazil #16082: xml.etree.ElementTree.tostringlist does conform to it's docume http://bugs.python.org/issue16082 opened by einarfd #16083: HTTPServer does not correctly handle bad headers http://bugs.python.org/issue16083 opened by maker Most recent 15 issues with no replies (15) ========================================== #16081: Fix compile warnings in thread_pthread.h http://bugs.python.org/issue16081 #16079: list duplicate test names with patchcheck http://bugs.python.org/issue16079 #16076: xml.etree.ElementTree.Element is no longer pickleable http://bugs.python.org/issue16076 #16074: bad error in rename http://bugs.python.org/issue16074 #16071: fix link to email.message.Message in mailbox docs http://bugs.python.org/issue16071 #16070: Structure and native Structure (LittleEndianStructure on Windo http://bugs.python.org/issue16070 #16067: UAC prompt for installation shows temporary file name http://bugs.python.org/issue16067 #16063: HMAC trans_5C is a string, causing a TypeError http://bugs.python.org/issue16063 #16058: ConfigParser no longer deepcopy compatible in 2.7 http://bugs.python.org/issue16058 #16057: Subclasses of JSONEncoder should not be insturcted to call JSO http://bugs.python.org/issue16057 #16053: "strict" parameter is not documented in csv module http://bugs.python.org/issue16053 #16047: Tools/freeze no longer works in Python 3 http://bugs.python.org/issue16047 #16041: poplib: unlimited readline() from connection http://bugs.python.org/issue16041 #16040: nntplib: unlimited readline() from connection http://bugs.python.org/issue16040 #16039: imaplib: unlimited readline() from connection http://bugs.python.org/issue16039 Most recent 15 issues waiting for review (15) ============================================= #16083: HTTPServer does not correctly handle bad headers http://bugs.python.org/issue16083 #16081: Fix compile warnings in thread_pthread.h http://bugs.python.org/issue16081 #16079: list duplicate test names with patchcheck http://bugs.python.org/issue16079 #16056: shadowed test names in std lib regression tests http://bugs.python.org/issue16056 #16055: incorrect error text for int(base=1000, x='1') http://bugs.python.org/issue16055 #16050: ctypes: callback from C++ to Python fails with Illegal Instruc http://bugs.python.org/issue16050 #16042: smtplib: unlimited readline() from connection http://bugs.python.org/issue16042 #16036: simplify int() signature docs http://bugs.python.org/issue16036 #16034: bz2 module appears slower in Python 3.x versus Python 2.x http://bugs.python.org/issue16034 #16029: pickle.dumps(xrange(sys.maxsize)) produces xrange(0) http://bugs.python.org/issue16029 #16025: Minor corrections to the zipfile documentation http://bugs.python.org/issue16025 #16024: Doc cleanup regarding path=fd, dir_fd, follow_symlinks, etc http://bugs.python.org/issue16024 #16013: small csv reader bug http://bugs.python.org/issue16013 #16004: Add `make touch` to 2.7 Makefile http://bugs.python.org/issue16004 #16001: small ints: cache string representation http://bugs.python.org/issue16001 Top 10 most discussed issues (10) ================================= #8425: a -= b should be fast if a is a small set and b is a large set http://bugs.python.org/issue8425 14 msgs #10044: small int optimization http://bugs.python.org/issue10044 10 msgs #15958: bytes.join() should allow arbitrary buffer objects http://bugs.python.org/issue15958 9 msgs #15964: SyntaxError in asdl when building 2.7 with system Python 3 http://bugs.python.org/issue15964 9 msgs #16029: pickle.dumps(xrange(sys.maxsize)) produces xrange(0) http://bugs.python.org/issue16029 9 msgs #16036: simplify int() signature docs http://bugs.python.org/issue16036 9 msgs #16055: incorrect error text for int(base=1000, x='1') http://bugs.python.org/issue16055 8 msgs #16056: shadowed test names in std lib regression tests http://bugs.python.org/issue16056 8 msgs #16001: small ints: cache string representation http://bugs.python.org/issue16001 7 msgs #16005: smtplib.SMTP().sendmail() and rset() http://bugs.python.org/issue16005 7 msgs Issues closed (58) ================== #2126: BaseHTTPServer.py fails long POST from IE http://bugs.python.org/issue2126 closed by pitrou #2600: BindingHTTPConnectionWithTimeout and BindingHTTPHandlerWithTim http://bugs.python.org/issue2600 closed by pitrou #6027: test_xmlrpc_net fails when the ISP returns "302 Found" http://bugs.python.org/issue6027 closed by ezio.melotti #7844: Add -3 warning for absolute imports. http://bugs.python.org/issue7844 closed by mark.dickinson #10980: http.server Header Unicode Bug http://bugs.python.org/issue10980 closed by pitrou #11103: Python 3.2 installer doesn't register file extensions on Windo http://bugs.python.org/issue11103 closed by serwy #12376: unittest.TextTestResult.__init__ does not pass on its init arg http://bugs.python.org/issue12376 closed by michael.foord #13263: Group some os functions in submodules http://bugs.python.org/issue13263 closed by ezio.melotti #14295: PEP 417: adding mock module http://bugs.python.org/issue14295 closed by michael.foord #15270: "Economy of Expression" section outdated http://bugs.python.org/issue15270 closed by rhettinger #15323: Provide target name in output message when Mock.assert_called_ http://bugs.python.org/issue15323 closed by python-dev #15379: Charmap decoding of no-BMP characters http://bugs.python.org/issue15379 closed by pitrou #15593: urlparse.parse_qs documentation wrong re: urlencode http://bugs.python.org/issue15593 closed by python-dev #15815: Add numerator to ZeroDivisionError messages http://bugs.python.org/issue15815 closed by terry.reedy #15882: _decimal.Decimal constructed from tuple http://bugs.python.org/issue15882 closed by georg.brandl #15895: PyRun_SimpleFileExFlags() can leak a FILE pointer http://bugs.python.org/issue15895 closed by georg.brandl #15900: Memory leak in PyUnicode_TranslateCharmap() http://bugs.python.org/issue15900 closed by georg.brandl #15925: email.utils.parsedate() and email.utils.parsedate_tz() should http://bugs.python.org/issue15925 closed by georg.brandl #15926: Segmentation fault after multiple reinitializations http://bugs.python.org/issue15926 closed by georg.brandl #15935: clarify argparse docs re: add_argument() type and default argu http://bugs.python.org/issue15935 closed by barry #15949: docs.python.org not getting updated http://bugs.python.org/issue15949 closed by ezio.melotti #15953: Incorrect some fields declaration in the PyTypeObject document http://bugs.python.org/issue15953 closed by python-dev #15969: faulthandler: drop S from dump_tracebacks_later() function nam http://bugs.python.org/issue15969 closed by georg.brandl #15973: Segmentation fault on timezone comparison http://bugs.python.org/issue15973 closed by georg.brandl #15978: asyncore: included batteries don't fit http://bugs.python.org/issue15978 closed by benjamin.peterson #15993: Windows: 3.3.0-rc2.msi: test_buffer fails http://bugs.python.org/issue15993 closed by loewis #16002: AIX buildbot compile errors http://bugs.python.org/issue16002 closed by skrah #16006: Spelling mistake in PEP 213 http://bugs.python.org/issue16006 closed by ezio.melotti #16008: [OS bug] DragonFly buildbot locale failures http://bugs.python.org/issue16008 closed by skrah #16010: Some Unicode in identifiers improperly rejected http://bugs.python.org/issue16010 closed by r.david.murray #16012: pyexpat: Argument for UseForeignDTD should be optional http://bugs.python.org/issue16012 closed by christian.heimes #16014: Incomplete link in docs http://bugs.python.org/issue16014 closed by ezio.melotti #16015: Incorrect startup header in tutorial http://bugs.python.org/issue16015 closed by chris.jerdonek #16016: Maybe make one author in ipaddress HOWTO http://bugs.python.org/issue16016 closed by ezio.melotti #16017: "urls" should be capital in tutorial http://bugs.python.org/issue16017 closed by ezio.melotti #16018: Impossible ... line in tutorial http://bugs.python.org/issue16018 closed by ezio.melotti #16019: Python highlighting in tutorial;should be text highlighting http://bugs.python.org/issue16019 closed by ezio.melotti #16020: Missing >>> in Python code example http://bugs.python.org/issue16020 closed by ezio.melotti #16021: In a table in PEP 235, brrrrrrrr should be N/A http://bugs.python.org/issue16021 closed by mark.dickinson #16022: Mistake in "What's New in Python 3.3" http://bugs.python.org/issue16022 closed by python-dev #16028: break in finally discards exception http://bugs.python.org/issue16028 closed by mark.dickinson #16031: relative import headaches http://bugs.python.org/issue16031 closed by ncoghlan #16032: IDLE 3.2 is crashing multiple times http://bugs.python.org/issue16032 closed by ned.deily #16033: IDLE crashes when debugging and saving http://bugs.python.org/issue16033 closed by serwy #16035: Segmentation fault in test suite of apsw http://bugs.python.org/issue16035 closed by georg.brandl #16046: python -O does not find *.pyo files http://bugs.python.org/issue16046 closed by georg.brandl #16051: Documentation missing pipes.quote() http://bugs.python.org/issue16051 closed by r.david.murray #16052: Typo in "What's new in 3.3" http://bugs.python.org/issue16052 closed by python-dev #16054: IDLE Preferences Crashes on click http://bugs.python.org/issue16054 closed by ned.deily #16060: Double decref and dereferencing after decref in int() http://bugs.python.org/issue16060 closed by georg.brandl #16064: unittest -m claims executable is "python", not "python3" http://bugs.python.org/issue16064 closed by python-dev #16068: with statement executes type(obj).__exit__ rather than getattr http://bugs.python.org/issue16068 closed by Paul.Wiseman #16069: packaging shows up on docs.python.org/dev http://bugs.python.org/issue16069 closed by georg.brandl #16072: fix documentation of string.replace() signature http://bugs.python.org/issue16072 closed by asvetlov #16073: fix map() statement in list comprehension example http://bugs.python.org/issue16073 closed by chris.jerdonek #16075: incoming.cia hook error when pushing commits http://bugs.python.org/issue16075 closed by georg.brandl #16078: Calendar.leapdays(y1,y2) bug http://bugs.python.org/issue16078 closed by larry #16080: test_decimal causes other tests to fail with LC_ALL=fr_FR http://bugs.python.org/issue16080 closed by skrah

1 0