Mailman 3 December 2015 - Python-Dev

PEP 448 review
by Guido van Rossum March 29, 2023

March 29, 2023

I'm back, I've re-read the PEP, and I've re-read the long thread with "(no subject)". I think Georg Brandl nailed it: """ *I like the "sequence and dict flattening" part of the PEP, mostly because itis consistent and should be easy to understand, but the comprehension syntaxenhancements seem to be bad for readability and "comprehending" what the codedoes.The call syntax part is a mixed bag on the one hand it is nice to be consistent with the extended possibilities in literals (flattening), but on the other hand there would be small but annoying inconsistencies anyways (e.g. the duplicate kwarg case above).* """ Greg Ewing followed up explaining that the inconsistency between dict flattening and call syntax is inherent in the pre-existing different rules for dicts vs. keyword args: {'a':1, 'a':2} results in {'a':2}, while f(a=1, a=2) is an error. (This form is a SyntaxError; the dynamic case f(a=1, **{'a': 1}) is a TypeError.) For me, allowing f(*a, *b) and f(**d, **e) and all the other combinations for function calls proposed by the PEP is an easy +1 -- it's a straightforward extension of the existing pattern, and anybody who knows what f(x, *a) does will understand f(x, *a, y, *b). Guessing what f(**d, **e) means shouldn't be hard either. Understanding the edge case for duplicate keys with f(**d, **e) is a little harder, but the error messages are pretty clear, and it is not a new edge case. The sequence and dict flattening syntax proposals are also clean and logical -- we already have *-unpacking on the receiving side, so allowing *x in tuple expressions reads pretty naturally (and the similarity with *a in argument lists certainly helps). From here, having [a, *x, b, *y] is also natural, and then the extension to other displays is natural: {a, *x, b, *y} and {a:1, **d, b:2, **e}. This, too, gets a +1 from me. So that leaves comprehensions. IIRC, during the development of the patch we realized that f(*x for x in xs) is sufficiently ambiguous that we decided to disallow it -- note that f(x for x in xs) is already somewhat of a special case because an argument can only be a "bare" generator expression if it is the only argument. The same reasoning doesn't apply (in that form) to list, set and dict comprehensions -- while f(x for x in xs) is identical in meaning to f((x for x in xs)), [x for x in xs] is NOT the same as [(x for x in xs)] (that's a list of one element, and the element is a generator expression). The basic premise of this part of the proposal is that if you have a few iterables, the new proposal (without comprehensions) lets you create a list or generator expression that iterates over all of them, essentially flattening them: >>> xs = [1, 2, 3] >>> ys = ['abc', 'def'] >>> zs = [99] >>> [*xs, *ys, *zs] [1, 2, 3, 'abc', 'def', 99] >>> But now suppose you have a list of iterables: >>> xss = [[1, 2, 3], ['abc', 'def'], [99]] >>> [*xss[0], *xss[1], *xss[2]] [1, 2, 3, 'abc', 'def', 99] >>> Wouldn't it be nice if you could write the latter using a comprehension? >>> xss = [[1, 2, 3], ['abc', 'def'], [99]] >>> [*xs for xs in xss] [1, 2, 3, 'abc', 'def', 99] >>> This is somewhat seductive, and the following is even nicer: the *xs position may be an expression, e.g.: >>> xss = [[1, 2, 3], ['abc', 'def'], [99]] >>> [*xs[:2] for xs in xss] [1, 2, 'abc', 'def', 99] >>> On the other hand, I had to explore the possibilities here by experimenting in the interpreter, and I discovered some odd edge cases (e.g. you can parenthesize the starred expression, but that seems a syntactic accident). All in all I am personally +0 on the comprehension part of the PEP, and I like that it provides a way to "flatten" a sequence of sequences, but I think very few people in the thread have supported this part. Therefore I would like to ask Neil to update the PEP and the patch to take out the comprehension part, so that the two "easy wins" can make it into Python 3.5 (basically, I am accepting two-thirds of the PEP :-). There is some time yet until alpha 2. I would also like code reviewers (Benjamin?) to start reviewing the patch <http://bugs.python.org/issue2292>, taking into account that the comprehension part needs to be removed. -- --Guido van Rossum (python.org/~guido)

7 17

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

May 18, 2021

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

8 14

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

Sept. 15, 2019

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

5 6

PEP 506 secrets module
by Steven D'Aprano April 15, 2016

April 15, 2016

Hi, As extensively discussed on Python-Ideas, the secrets module and PEP 506 is (I hope) ready for pronouncement. https://www.python.org/dev/peps/pep-0506/ There is code and tests here: https://bitbucket.org/sdaprano/secrets or you can run hg clone https://sdaprano@bitbucket.org/sdaprano/secrets The code is written for and tested on Python 2.6, 2.7, 3.1 - 3.4. -- Steve

13 28

PEP 257 and __init__
by Facundo Batista Jan. 4, 2016

Jan. 4, 2016

Hola! (I was doubting in sending this mail to this list or to the normal one, but as it affects a "style recommendation" we propose for the whole community, I finally sent it here) I was reading PEP 257 and it says that all public methods from a class (including __init__) should have a docstring. Why __init__? It's behaviour is well defined (inits the instance), and the initialization parameters should be described in the class' docstring itself, right? Or I am missing something? Should we remove "__init__" (the class method, *not* the package file) as to require docstrings in the PEP? Thanks! -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ Twitter: @facundobatista

7 11

subprocess check_output
by Carlos Barera Dec. 30, 2015

Dec. 30, 2015

Hi, Trying to run a specific command (ibstat) installed in /usr/sbin on an Ubuntu 15.04 machine, using subprocess.check_output and getting "/bin/sh: /usr/sbin/ibstat: No such file or directory" I tried the following: - running the command providing full path - running with executable=bash - running with (['/bin/bash', '-c' , "/usr/sbin/ibstat"]) Nothing worked ... Any idea? -carlos

2 1

Re: [Python-Dev] Is there a reference manual for Python bytecode?
by Wes Turner Dec. 29, 2015

Dec. 29, 2015

numba * http://numba.pydata.org/numba-doc/0.16.0/modules/numba.html#module-numba.by… * https://github.com/numba/numba/blob/master/numba/bytecode.py pypy * http://doc.pypy.org/en/latest/interpreter.html * http://aosabook.org/en/pypy.html ... http://compilers.pydata.org/ #Bytecode Utilities On Dec 28, 2015 1:33 PM, "Sturla Molden" <sturla.molden(a)gmail.com> wrote: Brett Cannon <brett(a)python.org> wrote: > Ned also neglected to mention his byterun project which is a pure Python > implementation of the CPython eval loop: <a > href="https://github.com/nedbat/byterun">https://github.com/nedbat/byterun </a> I would also encourage you to take a look at Numba. It is an LLVM based JIT compiler for Python bytecode, written for hardcore numerical algorithms in Python. It can often achieve the same performance as -O2 in C after a short burn-in while inferring the types of the arguments and variables. Using it is mostly as easy as adding an @numba.jit decorator to the function we want to accelerate. Numba is rapidly becoming what Google's long dead swallow should have been. :-) Sturla _______________________________________________ Python-Dev mailing list Python-Dev(a)python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/wes.turner%40gmail.com

1 0

Is there a reference manual for Python bytecode?
by Erik Dec. 29, 2015

Dec. 29, 2015

Hi. Looking at ceval.c and peephole.c, there is - of course - lots of specific hard-coded knowledge of the bytecode (e.g., number of operands and other attributes). I'd like to experiment at this level, but I can't seem to find a reference for the bytecode. Is there the equivalent of something like the ARM ARM(*) for Python bytecode? I can read Python or C code if it's encoded that way, but I'm looking for something that's a bit more immediate than deciphering what an interpreter or optimizer is trying to do (i.e., some sort of table layout or per-opcode set of attributes). BR, E. (*) http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0406c/index.…

8 17

Thanks for your hard work and my New Years resolutions
by Brett Cannon Dec. 26, 2015

Dec. 26, 2015

I just wanted to quickly thank everyone for the work they put into this project. I realize most of us either get only a little bit of paid time to work on Python or none at all, so contributing easily ends up using personal time which I know is a precious thing. So thank you for caring enough about this project to put in your valuable time and effort while trying to keep it enjoyable for everyone else. As we go into 2016, I hope to do my part to indirectly thank everyone by making our developer workflow easier to work with so that not only the lives of the core developers become easier but we once again become a project that is viewed as welcoming to outside contribution (instead of our current reputation as having patches sit in the issue tracker, languishing; join core-workflow if you want to help out with that). I also hope to see zipimport rewritten -- either by someone else or me if necessary -- so that my importlib.resources idea can land in time for Python 3.6 (join the import-sig if that interests you). Otherwise I plan to keep promoting Python 3 as we get ever closer to 2020. :)

2 1

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

Dec. 25, 2015

ACTIVITY SUMMARY (2015-12-18 - 2015-12-25) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 5345 (+21) closed 32365 (+24) total 37710 (+45) Open issues with patches: 2351 Issues opened (38) ================== #24840: implement bool conversion for enums to prevent odd edge case http://bugs.python.org/issue24840 reopened by gregory.p.smith #25908: ProcessPoolExecutor deadlock on KeyboardInterrupt http://bugs.python.org/issue25908 opened by jacksontj #25909: Incorrect documentation for PyMapping_Items and like http://bugs.python.org/issue25909 opened by serhiy.storchaka #25910: Fixing links in documentation http://bugs.python.org/issue25910 opened by SilentGhost #25911: Regression: os.walk now using os.scandir() breaks bytes filena http://bugs.python.org/issue25911 opened by mont29 #25912: Use __spec__.__name__ instead of __name__ in the docs where ap http://bugs.python.org/issue25912 opened by Antony.Lee #25913: base64.a85decode adobe flag incorrectly utilizes <~ as a marke http://bugs.python.org/issue25913 opened by Soren Solari #25916: wave module readframes now returns bytes not str http://bugs.python.org/issue25916 opened by Iber Parodi Siri #25917: Fixing howto links in docs http://bugs.python.org/issue25917 opened by SilentGhost #25918: AssertionError in lib2to3 on 2.7.11 Windows http://bugs.python.org/issue25918 opened by schlamar #25919: htp.client PUT method ignores error responses sent immediatly http://bugs.python.org/issue25919 opened by Wiktor Niesiobedzki #25920: PyOS_AfterFork should reset socketmodule's lock http://bugs.python.org/issue25920 opened by emptysquare #25922: canceling a repair install breaks the ability to uninstall, re http://bugs.python.org/issue25922 opened by Kyle S (MrStonedOne) #25923: More const char http://bugs.python.org/issue25923 opened by serhiy.storchaka #25924: investigate if getaddrinfo(3) on OSX is thread-safe http://bugs.python.org/issue25924 opened by ronaldoussoren #25925: Coverage support for CPython 2 http://bugs.python.org/issue25925 opened by alecsandru.patrascu #25926: problems with "times" keyword in itertools.repeat http://bugs.python.org/issue25926 opened by Thomas Feldmann #25927: add dir_fd for mkstemp, and also maybe to all tempfile.* http://bugs.python.org/issue25927 opened by mmarkk #25928: Add Decimal.as_integer_ratio() http://bugs.python.org/issue25928 opened by johnwalker #25930: Document that os.remove is semantically identical to os.unlink http://bugs.python.org/issue25930 opened by Anthony Sottile #25931: os.fork() command distributed in windows Python27 (in SocketSe http://bugs.python.org/issue25931 opened by Sam Lobel #25933: Unhandled exception (TypeError) with ftplib in function retrbi http://bugs.python.org/issue25933 opened by Sam Adams #25934: ICC compiler: ICC treats denormal floating point numbers as 0. http://bugs.python.org/issue25934 opened by skrah #25935: OrderedDict prevents garbage collection if a circulary referen http://bugs.python.org/issue25935 opened by charettes #25936: Improve FastChildWatcher with WNOWAIT? http://bugs.python.org/issue25936 opened by WGH #25937: DIfference between utf8 and utf-8 when i define python source http://bugs.python.org/issue25937 opened by 王杰 #25939: _ssl.enum_certificates() fails with ERROR_ACCESS_DENIED if pyt http://bugs.python.org/issue25939 opened by Chi Hsuan Yen #25940: SSL tests failed due to expired svn.python.org SSL certificate http://bugs.python.org/issue25940 opened by Chi Hsuan Yen #25941: Add 'How to Review a Patch' section to devguide http://bugs.python.org/issue25941 opened by Winterflower #25942: subprocess.call SIGKILLs too liberally http://bugs.python.org/issue25942 opened by Mike Pomraning #25943: Integer overflow in _bsddb leads to heap corruption http://bugs.python.org/issue25943 opened by Ned Williamson #25945: Type confusion in partial_setstate and partial_call leads to m http://bugs.python.org/issue25945 opened by Ned Williamson #25946: configure should pick /usr/bin/g++ automatically if present http://bugs.python.org/issue25946 opened by krichter #25947: Installation problem http://bugs.python.org/issue25947 opened by camilleri.jon(a)gmail.com #25948: Invalid MIME encoding generated by email.mime (line too long) http://bugs.python.org/issue25948 opened by vog #25949: Lazy creation of __dict__ in OrderedDict http://bugs.python.org/issue25949 opened by serhiy.storchaka #25951: SSLSocket.sendall() does not return None on success like socke http://bugs.python.org/issue25951 opened by ProgVal #25952: code_context not available in exec() http://bugs.python.org/issue25952 opened by Grzegorz Krasoń Most recent 15 issues with no replies (15) ========================================== #25952: code_context not available in exec() http://bugs.python.org/issue25952 #25951: SSLSocket.sendall() does not return None on success like socke http://bugs.python.org/issue25951 #25949: Lazy creation of __dict__ in OrderedDict http://bugs.python.org/issue25949 #25948: Invalid MIME encoding generated by email.mime (line too long) http://bugs.python.org/issue25948 #25946: configure should pick /usr/bin/g++ automatically if present http://bugs.python.org/issue25946 #25943: Integer overflow in _bsddb leads to heap corruption http://bugs.python.org/issue25943 #25942: subprocess.call SIGKILLs too liberally http://bugs.python.org/issue25942 #25937: DIfference between utf8 and utf-8 when i define python source http://bugs.python.org/issue25937 #25936: Improve FastChildWatcher with WNOWAIT? http://bugs.python.org/issue25936 #25935: OrderedDict prevents garbage collection if a circulary referen http://bugs.python.org/issue25935 #25934: ICC compiler: ICC treats denormal floating point numbers as 0. http://bugs.python.org/issue25934 #25924: investigate if getaddrinfo(3) on OSX is thread-safe http://bugs.python.org/issue25924 #25923: More const char http://bugs.python.org/issue25923 #25917: Fixing howto links in docs http://bugs.python.org/issue25917 #25910: Fixing links in documentation http://bugs.python.org/issue25910 Most recent 15 issues waiting for review (15) ============================================= #25949: Lazy creation of __dict__ in OrderedDict http://bugs.python.org/issue25949 #25945: Type confusion in partial_setstate and partial_call leads to m http://bugs.python.org/issue25945 #25942: subprocess.call SIGKILLs too liberally http://bugs.python.org/issue25942 #25941: Add 'How to Review a Patch' section to devguide http://bugs.python.org/issue25941 #25939: _ssl.enum_certificates() fails with ERROR_ACCESS_DENIED if pyt http://bugs.python.org/issue25939 #25933: Unhandled exception (TypeError) with ftplib in function retrbi http://bugs.python.org/issue25933 #25925: Coverage support for CPython 2 http://bugs.python.org/issue25925 #25923: More const char http://bugs.python.org/issue25923 #25919: htp.client PUT method ignores error responses sent immediatly http://bugs.python.org/issue25919 #25917: Fixing howto links in docs http://bugs.python.org/issue25917 #25916: wave module readframes now returns bytes not str http://bugs.python.org/issue25916 #25913: base64.a85decode adobe flag incorrectly utilizes <~ as a marke http://bugs.python.org/issue25913 #25911: Regression: os.walk now using os.scandir() breaks bytes filena http://bugs.python.org/issue25911 #25910: Fixing links in documentation http://bugs.python.org/issue25910 #25909: Incorrect documentation for PyMapping_Items and like http://bugs.python.org/issue25909 Top 10 most discussed issues (10) ================================= #4709: Mingw-w64 and python on windows x64 http://bugs.python.org/issue4709 13 msgs #25911: Regression: os.walk now using os.scandir() breaks bytes filena http://bugs.python.org/issue25911 12 msgs #25928: Add Decimal.as_integer_ratio() http://bugs.python.org/issue25928 10 msgs #19475: Add timespec optional flag to datetime isoformat() to choose t http://bugs.python.org/issue19475 7 msgs #21579: Python 3.4: tempfile.close attribute does not work http://bugs.python.org/issue21579 7 msgs #25848: Tkinter tests failed on Windows buildbots http://bugs.python.org/issue25848 7 msgs #25919: htp.client PUT method ignores error responses sent immediatly http://bugs.python.org/issue25919 6 msgs #25930: Document that os.remove is semantically identical to os.unlink http://bugs.python.org/issue25930 6 msgs #12484: The Py_InitModule functions no longer exist, but remain in the http://bugs.python.org/issue12484 5 msgs #25933: Unhandled exception (TypeError) with ftplib in function retrbi http://bugs.python.org/issue25933 5 msgs Issues closed (23) ================== #17868: pprint long non-printable bytes as hexdump http://bugs.python.org/issue17868 closed by serhiy.storchaka #20782: base64 module docs do not use the terms 'bytes' and 'string' c http://bugs.python.org/issue20782 closed by r.david.murray #22227: Simplify tarfile iterator http://bugs.python.org/issue22227 closed by serhiy.storchaka #24103: Use after free in xmlparser_setevents (1) http://bugs.python.org/issue24103 closed by serhiy.storchaka #24580: Wrong or missing exception when compiling regexes with recursi http://bugs.python.org/issue24580 closed by serhiy.storchaka #25421: Make __sizeof__ for builtin types more subclass friendly http://bugs.python.org/issue25421 closed by serhiy.storchaka #25766: __bytes__ doesn't work for str subclasses http://bugs.python.org/issue25766 closed by serhiy.storchaka #25827: Support ICC in configure http://bugs.python.org/issue25827 closed by zach.ware #25844: Pylauncher, launcher.c: Assigning NULL to a pointer instead of http://bugs.python.org/issue25844 closed by serhiy.storchaka #25860: os.fwalk() silently skips remaining directories when error occ http://bugs.python.org/issue25860 closed by serhiy.storchaka #25869: Faster ElementTree deepcopying http://bugs.python.org/issue25869 closed by serhiy.storchaka #25873: Faster ElementTree iterating http://bugs.python.org/issue25873 closed by serhiy.storchaka #25902: Fixed various refcount issues in ElementTree iteration http://bugs.python.org/issue25902 closed by serhiy.storchaka #25905: IDLE fails to display the README file http://bugs.python.org/issue25905 closed by terry.reedy #25914: Fix OrderedDict.__sizeof__ http://bugs.python.org/issue25914 closed by serhiy.storchaka #25915: file.write() after file.read() adds text to the end of the fil http://bugs.python.org/issue25915 closed by Adam Wasik #25921: project files for wininst-14.0*.exe don't exist http://bugs.python.org/issue25921 closed by zach.ware #25929: When doing string.replace, it uses the entire 'find' string an http://bugs.python.org/issue25929 closed by r.david.murray #25932: Windows installer ships an outdated and insecure curl.exe http://bugs.python.org/issue25932 closed by zach.ware #25938: if sentence doesn't work with input() http://bugs.python.org/issue25938 closed by benjamin.peterson #25944: Type confusion in partial_setstate and partial_repr leads to c http://bugs.python.org/issue25944 closed by serhiy.storchaka #25950: svn.python.org SSL certificate expired, causing test failures http://bugs.python.org/issue25950 closed by berker.peksag #1753718: base64 "legacy" functions violate RFC 3548 http://bugs.python.org/issue1753718 closed by r.david.murray

1 0