Mailman 3 June 2017 - Python-Dev

PEP 448 review
by Guido van Rossum 29 Mar '23

29 Mar '23

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 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

congrats on 3.5! Alas, windows 7 users are having problems installing it
by Laura Creighton 15 Sep '19

15 Sep '19

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

Help requested with Python 2.7 performance regression
by Barry Warsaw 17 Aug '17

17 Aug '17

Hello all, Over in Ubuntu, we've gotten reports about some performance regressions in Python 2.7 when moving from Trusty (14.04 LTS) to Xenial (16.04 LTS). Trusty's version is based on 2.7.6 while Xenial's version is based on 2.7.12 with bits of .13 cherry picked. We've not been able to identify any change in Python itself (or the Debian/Ubuntu deltas) which could account for this, so the investigation has led to various gcc compiler options and version differences. In particular disabling LTO (link-time optimization) seems to have a positive impact, but doesn't completely regain the loss. Louis (Cc'd here) has done a ton of work to measure and analyze the problem, but we've more or less hit a roadblock, so we're taking the issue public to see if anybody on this mailing list has further ideas. A detailed analysis is available in this Google doc: https://docs.google.com/document/d/1zrV3OIRSo99fd2Ty4YdGk_scmTRDmVauBprKL8e… The document should be public for comments and editing. If you have any thoughts, or other lines of investigation you think are worthwhile pursuing, please add your comments to the document. Cheers, -Barry

11 21

Star the CPython GitHub project if you like Python!
by Victor Stinner 04 Jul '17

04 Jul '17

Hi, GitHub has a showcase page of hosted programming languages: https://github.com/showcases/programming-languages Python is only #11 with 8,539 stars, behind PHP and Ruby! Hey, you should "like" ("star"?) the CPython project if you like Python! https://github.com/python/cpython/ Click on "Star" at the top right. Thank you! Victor

4 4

New work-in-progress bisection tool for the Python test suite (in regrtest)
by Victor Stinner 04 Jul '17

04 Jul '17

Hi, Last weeks, I worked on a new tool to bisect failing tests because it's painful to bisect manually reference leaks (I remove as much code as possible until the code is small enough to be reviewable manually). See the bisect_test.py script attached to this issue: http://bugs.python.org/issue29512 With the help of Louie Lu, I added new --list-cases option to "python -m test", so you can now list all test cases and write it into a text file: ./python -m test --list-cases test_os > tests I also added a new --matchfile option, to filter tests using a text file which contains one pattern per line: ./python -m test --matchfile=tests test_os fnmatch is used to match test names, so "*" joker character can be used in test names. My bisection tool takes a text file with the --matchfile format (one pattern per line) and creates a random subset of tests with half of the tests. If tests still fail, use the subset. Otherwise, create a new random subset. Loop until the subset contains a single test (configurable threshold, -n command line option). The long term plan is to integrate the bisection feature directly into regrtest. Right now, my script is hardcoded to bisect reference leak bugs, but it should be easy to modify it to bisect other test issues like test creating files without removing it ("ENV_CHANGED" failure in regrtest). For example, a core file is dumped when running test_subprocess on FreeBSD buildbots: http://bugs.python.org/issue30448 But I'm unable to reproduce the issue on my FreeBSD. It would be nice to be able to automate the bisection on the buildbot directly. --list-cases and --matchfile options are now available in 2.7, 3.5, 3.6 and master (3.7) branches. TODO: doctest tests are only partially supported, see: http://bugs.python.org/issue30683 Victor

8 20

Buildbot report (almost July)
by Victor Stinner 04 Jul '17

04 Jul '17

Hi, Our buildbots are now even more stable than in my previous buildbot report. Many random failures have been fixed, even if there are still many rare random failures (most of them are related to multiprocessing). Search for issues created by "haypo" (me!) with the Component "Tests" to see all remaining issues. I'm trying to open an issue for *each* buildbot failure! So yeah, we have a long list of 44 open issues! Correct me if I'm wrong, but, for the first time, *all reference leaks* have been fixed on *all branches* (2.7, 3.5, 3.6 and master), on *Linux and Windows*! Before, we mostly focused on the master branch (called "default" in Mercurial) on Linux. I also started to fix a few "memory block" leaks, most (or all?) of them should also be fixed (on all branches, on Linux and Windows). A new policy has been decided (on python-committers): if a commit breaks too many buildbots and cannot fixed easily nor quickly, the commit will be reverted, just to keep our buildbots "green". It doesn't mean that the commit will be rejected forever. It's a practical solution to give more time to write a proper fix, take time to review it, and not have to be stressed to fix buildbots "ASAP". Moreover, keeping green buildbots all the time allows to catch regressions more quickly, which ease debug in many ways. You have be warned! Now I will not hesitate to revert your change if you break my little buildbots ;-) I mostly care of Linux, Windows, macOS and FreeBSD (10 and CURRENT). Breaking other platforms is less important, since other platforms already have issues, but not enough developers interested to fix them. Obviously, I'm interested in keeping more buildbots green, if someone shows up and help me to fix remaining issues! Victor

4 8

Summary of Python tracker Issues
by Python tracker 01 Jul '17

01 Jul '17

ACTIVITY SUMMARY (2017-06-23 - 2017-06-30) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 6006 (-20) closed 36565 (+95) total 42571 (+75) Open issues with patches: 2344 Issues opened (53) ================== #14094: ntpath.realpath() should use GetFinalPathNameByHandle() http://bugs.python.org/issue14094 reopened by eryksun #30744: Local variable assignment is broken when combined with threads http://bugs.python.org/issue30744 opened by njs #30747: _Py_atomic_* not actually atomic on Windows with MSVC http://bugs.python.org/issue30747 opened by Paxxi #30748: Upgrade tuples in socket to named tuple like http://bugs.python.org/issue30748 opened by Ben Lewis #30751: IDLE: Display entry errors for key sequence entry in entry box http://bugs.python.org/issue30751 opened by terry.reedy #30754: textwrap.dedent mishandles empty lines http://bugs.python.org/issue30754 opened by Julian #30755: locale.normalize() and getdefaultlocale() convert C.UTF-8 to e http://bugs.python.org/issue30755 opened by mattheww #30756: ttk: GUI tests fail on Ubuntu http://bugs.python.org/issue30756 opened by csabella #30757: pyinstaller can be added to docs, py2exe ref can be updated http://bugs.python.org/issue30757 opened by denfromufa #30758: regrtest hangs sometimes on the master branch (test_pydoc? tes http://bugs.python.org/issue30758 opened by haypo #30759: [2.7] Fix python2 -m test --list-cases test_multibytecodec_sup http://bugs.python.org/issue30759 opened by haypo #30760: configparse module in python3 can not write '%' to config file http://bugs.python.org/issue30760 opened by quanyechavshuo #30761: pdb: Add step / next count arguments http://bugs.python.org/issue30761 opened by louielu #30762: Misleading message “can't concat bytes to str” http://bugs.python.org/issue30762 opened by antoine.pietri #30766: Make CHECK_STATUS_PTHREAD signal-safe http://bugs.python.org/issue30766 opened by pitrou #30767: logging must check exc_info correctly http://bugs.python.org/issue30767 opened by krivushinme #30768: PyThread_acquire_lock_timed() should recompute the timeout whe http://bugs.python.org/issue30768 opened by haypo #30772: Normalise non-ASCII variable names in __all__ http://bugs.python.org/issue30772 opened by Nate Soares #30773: async generator receives wrong value when shared between corou http://bugs.python.org/issue30773 opened by Dima.Tisnek #30774: list_repr not safe against concurrent mutation http://bugs.python.org/issue30774 opened by pitrou #30777: IDLE: configdialog -- add docstrings and improve comments http://bugs.python.org/issue30777 opened by terry.reedy #30778: test_bsddb3 crash on x86 Windows XP 2.7 http://bugs.python.org/issue30778 opened by haypo #30779: IDLE: configdialog -- factor out Changes class http://bugs.python.org/issue30779 opened by terry.reedy #30780: IDLE: configdialog - add tests for ConfigDialog GUI. http://bugs.python.org/issue30780 opened by terry.reedy #30781: IDLE: configdialog -- switch to ttk widgets. http://bugs.python.org/issue30781 opened by terry.reedy #30782: Allow limiting the number of concurrent tasks in asyncio.as_co http://bugs.python.org/issue30782 opened by andybalaam #30784: IDLE: separate editor window and text http://bugs.python.org/issue30784 opened by louielu #30786: getaddrinfo emulation does not support AI_NUMERICSERV http://bugs.python.org/issue30786 opened by smejkar #30788: email.policy.SMTP.fold() issue for long filenames with spaces http://bugs.python.org/issue30788 opened by jhillacre #30789: Redesign PyCodeObject.co_extras to use a single memory block, http://bugs.python.org/issue30789 opened by haypo #30790: Can't use proxy to connect internet on windows http://bugs.python.org/issue30790 opened by Cordius #30791: tkinter.Tk() adds suffix to window class name when launching m http://bugs.python.org/issue30791 opened by hakonhagland #30792: Add contextlib.convert_exception manager http://bugs.python.org/issue30792 opened by steven.daprano #30793: Parsing error on f-string-expressions containing strings with http://bugs.python.org/issue30793 opened by Anselm Kiefner #30794: Add multiprocessing.Process.kill() http://bugs.python.org/issue30794 opened by pitrou #30795: OS X failures in test_site http://bugs.python.org/issue30795 opened by pitrou #30797: ./pyconfig.h:1438:0: warning: "_GNU_SOURCE" redefined [enabled http://bugs.python.org/issue30797 opened by Segev Finer #30798: Document that subprocess.Popen does not set PWD http://bugs.python.org/issue30798 opened by jamesdlin #30799: Improved test coverage Lib/_osx_support.py 99% http://bugs.python.org/issue30799 opened by chexex #30800: zlib.compressobj took too much memory on window http://bugs.python.org/issue30800 opened by dennisding #30801: shoutdown process error with python 3.4 and pyqt/PySide http://bugs.python.org/issue30801 opened by alberfontan1 #30802: datetime.datetime.strptime('200722', '%Y%U') http://bugs.python.org/issue30802 opened by winton #30803: Truth value of sets not properly documented http://bugs.python.org/issue30803 opened by thomassen #30804: bolen-dmg-3.x build-installer.py failed http://bugs.python.org/issue30804 opened by haypo #30805: asyncio: race condition with debug and subprocess http://bugs.python.org/issue30805 opened by wg #30806: netrc.__repr__() is broken for writing to file http://bugs.python.org/issue30806 opened by Bezier89 #30808: Use _Py_atomic API for concurrency-sensitive signal state http://bugs.python.org/issue30808 opened by pitrou #30809: IDLE parenmatch - highlighting options http://bugs.python.org/issue30809 opened by wohlganger #30811: A venv created and activated from within a virtualenv uses the http://bugs.python.org/issue30811 opened by Antony.Lee #30814: Import dotted name as alias breaks with concurrency http://bugs.python.org/issue30814 opened by Samuele Santi2 #30816: test_open() of test_eintr timeout after 10 min on "x86-64 El C http://bugs.python.org/issue30816 opened by haypo #30817: Abort in PyErr_PrintEx() when no memory http://bugs.python.org/issue30817 opened by xdegaye #30818: Warning -- asyncore.socket_map was modified by test_ftplib on http://bugs.python.org/issue30818 opened by haypo Most recent 15 issues with no replies (15) ========================================== #30816: test_open() of test_eintr timeout after 10 min on "x86-64 El C http://bugs.python.org/issue30816 #30814: Import dotted name as alias breaks with concurrency http://bugs.python.org/issue30814 #30811: A venv created and activated from within a virtualenv uses the http://bugs.python.org/issue30811 #30806: netrc.__repr__() is broken for writing to file http://bugs.python.org/issue30806 #30805: asyncio: race condition with debug and subprocess http://bugs.python.org/issue30805 #30804: bolen-dmg-3.x build-installer.py failed http://bugs.python.org/issue30804 #30801: shoutdown process error with python 3.4 and pyqt/PySide http://bugs.python.org/issue30801 #30800: zlib.compressobj took too much memory on window http://bugs.python.org/issue30800 #30799: Improved test coverage Lib/_osx_support.py 99% http://bugs.python.org/issue30799 #30798: Document that subprocess.Popen does not set PWD http://bugs.python.org/issue30798 #30797: ./pyconfig.h:1438:0: warning: "_GNU_SOURCE" redefined [enabled http://bugs.python.org/issue30797 #30794: Add multiprocessing.Process.kill() http://bugs.python.org/issue30794 #30791: tkinter.Tk() adds suffix to window class name when launching m http://bugs.python.org/issue30791 #30790: Can't use proxy to connect internet on windows http://bugs.python.org/issue30790 #30789: Redesign PyCodeObject.co_extras to use a single memory block, http://bugs.python.org/issue30789 Most recent 15 issues waiting for review (15) ============================================= #30817: Abort in PyErr_PrintEx() when no memory http://bugs.python.org/issue30817 #30808: Use _Py_atomic API for concurrency-sensitive signal state http://bugs.python.org/issue30808 #30747: _Py_atomic_* not actually atomic on Windows with MSVC http://bugs.python.org/issue30747 #30714: test_ssl fails with openssl 1.1.0f http://bugs.python.org/issue30714 #30711: getaddrinfo invalid port number http://bugs.python.org/issue30711 #30710: getaddrinfo raises OverflowError http://bugs.python.org/issue30710 #30696: infinite loop in PyRun_InteractiveLoopFlags() http://bugs.python.org/issue30696 #30695: add a nomemory_allocator to the _testcapi module http://bugs.python.org/issue30695 #30693: tarfile add uses random order http://bugs.python.org/issue30693 #30688: support named Unicode escapes (\N{name}) in re http://bugs.python.org/issue30688 #30680: textwrap should treat Unicode em-dash like ASCII em-dash http://bugs.python.org/issue30680 #30665: pass big values for arg to fcntl.ioctl http://bugs.python.org/issue30665 #30593: sqlite3 executescript does not respect isolation_level? http://bugs.python.org/issue30593 #30560: Py_SetFatalErrorAbortFunc: Allow embedding program to handle f http://bugs.python.org/issue30560 #30541: Add restricted mocks to the python unittest mocking framework http://bugs.python.org/issue30541 Top 10 most discussed issues (10) ================================= #24813: Redesign Help => About IDLE, make it non-modal http://bugs.python.org/issue24813 21 msgs #30703: Non-reentrant signal handler (test_multiprocessing_forkserver http://bugs.python.org/issue30703 18 msgs #29926: IDLE: in shell, time.sleep ignores _thread.interrupt_main() http://bugs.python.org/issue29926 16 msgs #30744: Local variable assignment is broken when combined with threads http://bugs.python.org/issue30744 13 msgs #30422: Add roadmap.txt section to idlelib http://bugs.python.org/issue30422 11 msgs #21998: asyncio: support fork http://bugs.python.org/issue21998 9 msgs #30730: [security] Injecting environment variable in subprocess on Win http://bugs.python.org/issue30730 9 msgs #29988: (async) with blocks and try/finally are not as KeyboardInterru http://bugs.python.org/issue29988 8 msgs #30302: Improve .__repr__ implementation for datetime.timedelta http://bugs.python.org/issue30302 7 msgs #30726: [Windows] Warnings in elementtree due to new expat http://bugs.python.org/issue30726 7 msgs Issues closed (87) ================== #10909: IDLE: thread hang, possibly related to print http://bugs.python.org/issue10909 closed by terry.reedy #10972: zipfile: add "unicode" option to the force the filename encodi http://bugs.python.org/issue10972 closed by haypo #12215: TextIOWrapper: issues with interlaced read-write http://bugs.python.org/issue12215 closed by haypo #12512: codecs: StreamWriter issues with stateful codecs after a seek http://bugs.python.org/issue12512 closed by haypo #12513: codec.StreamReaderWriter: issues with interlaced read-write http://bugs.python.org/issue12513 closed by haypo #13552: Compilation issues of the curses module on Solaris and OpenInd http://bugs.python.org/issue13552 closed by haypo #13617: Reject embedded null characters in wchar* strings http://bugs.python.org/issue13617 closed by serhiy.storchaka #19150: IDLE shell fails: "ModifiedInterpreter instance has no attribu http://bugs.python.org/issue19150 closed by terry.reedy #20615: Replace PyDict_GetItem() with PyDict_GetItemWithError() http://bugs.python.org/issue20615 closed by haypo #20718: OpenBSD/AIX: tests passing a file descriptor with sendmsg/recv http://bugs.python.org/issue20718 closed by haypo #21080: asyncio.subprocess: connect pipes of two programs http://bugs.python.org/issue21080 closed by haypo #21519: IDLE : Bug in keybinding validity check http://bugs.python.org/issue21519 closed by terry.reedy #22207: Test for integer overflow on Py_ssize_t: explicitly cast to si http://bugs.python.org/issue22207 closed by haypo #22271: Deprecate PyUnicode_AsUnicode(): emit a DeprecationWarning http://bugs.python.org/issue22271 closed by haypo #23587: asyncio: use the new traceback.TracebackException class http://bugs.python.org/issue23587 closed by haypo #23763: Chain exceptions in C http://bugs.python.org/issue23763 closed by haypo #24598: asyncio: add background task detecting reference cycles http://bugs.python.org/issue24598 closed by haypo #24999: Segfault in test_re.test_sre_character_class_literals() when P http://bugs.python.org/issue24999 closed by haypo #25606: asyncio doc: 'socket' transport extra info is not mandatory http://bugs.python.org/issue25606 closed by haypo #25796: Running test_multiprocessing_spawn is slow (more than 8 minute http://bugs.python.org/issue25796 closed by haypo #25868: test_eintr.test_sigwaitinfo() hangs on "AMD64 FreeBSD CURRENT http://bugs.python.org/issue25868 closed by haypo #26373: asyncio: add support for async context manager on streams? http://bugs.python.org/issue26373 closed by haypo #26643: regrtest: rework libregrtest.save_env submodule http://bugs.python.org/issue26643 closed by haypo #26757: test_urllib2net.test_http_basic() timeout after 15 min on http://bugs.python.org/issue26757 closed by haypo #27103: regrtest: capture stdout (-W) option is incompatible with refl http://bugs.python.org/issue27103 closed by haypo #27847: os.set_inheritable() looks to be broken on OpenIndiana, regres http://bugs.python.org/issue27847 closed by haypo #27940: xml.etree: Avoid XML declaration for the "ascii" encoding http://bugs.python.org/issue27940 closed by haypo #28223: test_tools fails with timeout on AMD64 Snow Leop 3.x buildbot http://bugs.python.org/issue28223 closed by haypo #28224: Compilation warnings on Windows: export 'PyInit_xx' specified http://bugs.python.org/issue28224 closed by haypo #28232: asyncio: wrap_future() doesn't handle cancellation correctly http://bugs.python.org/issue28232 closed by haypo #28554: Windows: _socket module fails to compile on "AMD64 Windows7 SP http://bugs.python.org/issue28554 closed by haypo #28572: IDLE: add tests for config dialog. http://bugs.python.org/issue28572 closed by terry.reedy #28711: IDLE doesn't open http://bugs.python.org/issue28711 closed by terry.reedy #29461: Experiment usage of likely/unlikely in CPython core http://bugs.python.org/issue29461 closed by haypo #29512: regrtest refleak: implement bisection feature http://bugs.python.org/issue29512 closed by haypo #29530: Windows buildbots broken by the migration to GitHub (meta issu http://bugs.python.org/issue29530 closed by haypo #29585: site.py imports relatively large `sysconfig` module. http://bugs.python.org/issue29585 closed by inada.naoki #29910: Ctrl-D eats a character on IDLE http://bugs.python.org/issue29910 closed by terry.reedy #30038: Race condition in how trip_signal writes to wakeup fd http://bugs.python.org/issue30038 closed by njs #30062: datetime in Python 3.6+ no longer respects 'TZ' environment va http://bugs.python.org/issue30062 closed by ammar2 #30172: test_tools takes longer than 5 minutes on some buildbots http://bugs.python.org/issue30172 closed by haypo #30263: regrtest: log the system load? http://bugs.python.org/issue30263 closed by haypo #30280: Warning -- threading._dangling was modified by test_asyncio on http://bugs.python.org/issue30280 closed by haypo #30314: Buildbots: 15 min is too low for test_tools on x86 Tiger 3.6 b http://bugs.python.org/issue30314 closed by haypo #30329: poplib and imaplib should catch "OSError: [WinError 10022] An http://bugs.python.org/issue30329 closed by haypo #30362: Launcher add list and list with paths options http://bugs.python.org/issue30362 closed by steve.dower #30368: [2.7] OpenSSL compilation fails on AMD64 Windows7 SP1 VS9.0 2. http://bugs.python.org/issue30368 closed by haypo #30523: regrtest: add --list-cases option to only display test case id http://bugs.python.org/issue30523 closed by haypo #30542: test_files() of test_tools.test_unparse.DirectoryTestCase leak http://bugs.python.org/issue30542 closed by haypo #30596: Add close() to multiprocessing.Process http://bugs.python.org/issue30596 closed by pitrou #30599: test_threaded_import leaks references http://bugs.python.org/issue30599 closed by haypo #30645: imp.py: load_package() appends to its own loop variable http://bugs.python.org/issue30645 closed by brett.cannon #30647: CODESET error on AMD64 FreeBSD 10.x Shared 3.x caused by the P http://bugs.python.org/issue30647 closed by ncoghlan #30664: Change unittest's _SubTest to not sort its params when printin http://bugs.python.org/issue30664 closed by serhiy.storchaka #30673: Add -t option (timeout) to Tools/buildbot/test.bat for "AMD64 http://bugs.python.org/issue30673 closed by haypo #30674: IDLE: add docstrings to grep.py http://bugs.python.org/issue30674 closed by terry.reedy #30675: test_zipfile leaks references on Python 3.5 on the wo Refleaks http://bugs.python.org/issue30675 closed by haypo #30704: test_free_different_thread() of test_code leaks references on http://bugs.python.org/issue30704 closed by haypo #30705: python2.7 -m test -R 3:3 hangs on Refleaks 2.7 buildbots http://bugs.python.org/issue30705 closed by haypo #30706: EmailMessage Object Creation http://bugs.python.org/issue30706 closed by r.david.murray #30708: Ensure that the result of PyUnicode_AsWideCharString() doesn't http://bugs.python.org/issue30708 closed by serhiy.storchaka #30723: IDLE parenmatch - left and right highlighting, independent fla http://bugs.python.org/issue30723 closed by terry.reedy #30733: Typo in Document What's New: Calendar http://bugs.python.org/issue30733 closed by doerwalter #30734: 200000 indexes crashes eval and python (without eval) http://bugs.python.org/issue30734 closed by serhiy.storchaka #30742: VS2015 support for 2.7 branch http://bugs.python.org/issue30742 closed by steve.dower #30743: unittest discover does not mention module file must be named w http://bugs.python.org/issue30743 closed by alex.75 #30745: Warnings in Modules/_winapi.c http://bugs.python.org/issue30745 closed by serhiy.storchaka #30746: Reject environment variable names containing '=' http://bugs.python.org/issue30746 closed by serhiy.storchaka #30749: Non-atomic and unusual (wrong) rename behavior under OS X http://bugs.python.org/issue30749 closed by Alex Groce #30750: Update `make patchcheck` to understand Misc/NEWS.d http://bugs.python.org/issue30750 closed by brett.cannon #30752: Basic subtraction is wrong ( 1.83 - 1.52 == 0.3100000000000000 http://bugs.python.org/issue30752 closed by mark.dickinson #30753: not able to execute print command on page 16 of documentation http://bugs.python.org/issue30753 closed by steven.daprano #30763: There is functionality bug in linecache library. http://bugs.python.org/issue30763 closed by gvanrossum #30764: regrtest: Add --fail-env-changed option http://bugs.python.org/issue30764 closed by haypo #30765: PyThread_acquire_lock can block even when asked not ot http://bugs.python.org/issue30765 closed by pitrou #30769: [EASY (C)] test_execve_invalid_env() of test_os leaks referenc http://bugs.python.org/issue30769 closed by haypo #30775: test_multiprocessing_forkserver leaks references on Python 3 http://bugs.python.org/issue30775 closed by pitrou #30776: regrtest: change -R/--huntrleaks rule to decide if a test leak http://bugs.python.org/issue30776 closed by haypo #30783: Spawned subprocesses don't respect environment http://bugs.python.org/issue30783 closed by eryksun #30785: ast.c duplicates STR(CHILD) http://bugs.python.org/issue30785 closed by emilyemorehouse #30787: Please add a comprehensive index of decorators to the document http://bugs.python.org/issue30787 closed by brett.cannon #30796: Failures/crashes in test_signal on some buildbots http://bugs.python.org/issue30796 closed by pitrou #30807: setitimer() can disable timer by mistake http://bugs.python.org/issue30807 closed by pitrou #30810: Germany made the upper case ß official. 'ß'.upper() should n http://bugs.python.org/issue30810 closed by haypo #30812: Running test_warnings twice fails http://bugs.python.org/issue30812 closed by haypo #30813: test_unittest fails when hunting reference leaks http://bugs.python.org/issue30813 closed by haypo #30815: StringIO uses inefficient PyUnicode_AsUCS4 http://bugs.python.org/issue30815 closed by inada.naoki

3 2

Summary of Python tracker Issues
by Python tracker 01 Jul '17

01 Jul '17

ACTIVITY SUMMARY (2017-06-16 - 2017-06-23) 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 6026 ( -8) closed 36470 (+65) total 42496 (+57) Open issues with patches: 2361 Issues opened (49) ================== #27425: Tests fail because of git's newline preferences on Windows http://bugs.python.org/issue27425 reopened by haypo #30383: [3.5] Backport regrtest features from master to Python 3.5 http://bugs.python.org/issue30383 reopened by haypo #30597: Show expected input in custom "print" error message http://bugs.python.org/issue30597 reopened by ncoghlan #30685: Multiprocessing Send to Manager Fails for Large Payload http://bugs.python.org/issue30685 opened by maxehr #30686: make `make install` faster http://bugs.python.org/issue30686 opened by inada.naoki #30688: support named Unicode escapes (\N{name}) in re http://bugs.python.org/issue30688 opened by jonathaneunice #30691: WeakSet is not pickleable http://bugs.python.org/issue30691 opened by serhiy.storchaka #30692: Automatic upcast does not occur for custom classes http://bugs.python.org/issue30692 opened by rharke #30693: tarfile add uses random order http://bugs.python.org/issue30693 opened by bmwiedemann #30694: Update embedded copy of expat to 2.2.1 http://bugs.python.org/issue30694 opened by ned.deily #30695: add a nomemory_allocator to the _testcapi module http://bugs.python.org/issue30695 opened by xdegaye #30696: infinite loop in PyRun_InteractiveLoopFlags() http://bugs.python.org/issue30696 opened by xdegaye #30697: segfault in PyErr_NormalizeException() after memory exhaustion http://bugs.python.org/issue30697 opened by xdegaye #30698: asyncio sslproto do not shutdown ssl layer cleanly http://bugs.python.org/issue30698 opened by grzgrzgrz3 #30699: Misleading class names in datetime.tzinfo usage examples http://bugs.python.org/issue30699 opened by Robert.Tasarz #30700: fileinput inplace clobbers file without leaving backup on deco http://bugs.python.org/issue30700 opened by switchnode #30701: Exception parsing certain invalid email address headers http://bugs.python.org/issue30701 opened by timb07 #30703: test_multiprocessing_forkserver hangs on the master branch http://bugs.python.org/issue30703 opened by haypo #30704: test_free_different_thread() of test_code leaks references on http://bugs.python.org/issue30704 opened by haypo #30705: python2.7 -m test -R 3:3 hangs on Refleaks 2.7 buildbots http://bugs.python.org/issue30705 opened by haypo #30706: EmailMessage Object Creation http://bugs.python.org/issue30706 opened by Michael Salsone #30707: Incorrect description of "async with" in PEP492 and documentat http://bugs.python.org/issue30707 opened by Damien George #30708: Ensure that the result of PyUnicode_AsWideCharString() doesn't http://bugs.python.org/issue30708 opened by serhiy.storchaka #30710: getaddrinfo raises OverflowError http://bugs.python.org/issue30710 opened by smejkar #30711: getaddrinfo invalid port number http://bugs.python.org/issue30711 opened by smejkar #30713: Reject newline character (U+000A) in URLs in urllib.parse http://bugs.python.org/issue30713 opened by haypo #30714: test_ssl fails with openssl 1.1.0f http://bugs.python.org/issue30714 opened by cstratak #30715: Test_winreg, test_dynamic_key hangs on my Win 10 http://bugs.python.org/issue30715 opened by terry.reedy #30716: Failing tests with installed 3.6.2rc1 on Win 10-64 http://bugs.python.org/issue30716 opened by terry.reedy #30717: str.center() is not unicode aware http://bugs.python.org/issue30717 opened by Guillaume Sanchez #30718: open builtin function: specifying the size of buffer has no ef http://bugs.python.org/issue30718 opened by direprobs #30719: IDLE: Make PyShell visible upon error. http://bugs.python.org/issue30719 opened by terry.reedy #30721: Show expected input for right shift operator usage in custom " http://bugs.python.org/issue30721 opened by CuriousLearner #30722: Tools/demo/redemo.py broken http://bugs.python.org/issue30722 opened by Christoph Sarnowski2 #30723: IDLE parenmatch - left and right highlighting, independent fla http://bugs.python.org/issue30723 opened by wohlganger #30724: ZipFile.open treats directory path as empty file http://bugs.python.org/issue30724 opened by Kit Yan Choi #30725: Windows installer for 2.7.13 doesn't install pip when installi http://bugs.python.org/issue30725 opened by KevKeating #30726: [Windows] Warnings in elementtree due to new expat http://bugs.python.org/issue30726 opened by Segev Finer #30728: IDLE: Modernize configdialog code. http://bugs.python.org/issue30728 opened by terry.reedy #30730: Injecting environment variable in subprocess on Windows http://bugs.python.org/issue30730 opened by serhiy.storchaka #30731: Use correct executable manifest for windows http://bugs.python.org/issue30731 opened by tumagonx #30732: json.dumps() lacks information about RecursionError related to http://bugs.python.org/issue30732 opened by Krzysztof Nazarewski #30733: Typo in Document What's New: Calendar http://bugs.python.org/issue30733 opened by Jonathon Vandezande #30734: 200000 indexes crashes eval and python (without eval) http://bugs.python.org/issue30734 opened by george-shuklin #30735: Python 3.6.1 test_asyncio fails on Solaris 11 http://bugs.python.org/issue30735 opened by petriborg #30737: Update devguide link to the new URL http://bugs.python.org/issue30737 opened by Mariatta #30739: pypi ssl errors [CERTIFICATE_VERIFY_FAILED] http://bugs.python.org/issue30739 opened by Luc Zimmermann #30740: SSLError when cancelling an SSL connection http://bugs.python.org/issue30740 opened by mehaase #30741: https://www.pypi-mirrors.org/ error 503 http://bugs.python.org/issue30741 opened by Luc Zimmermann Most recent 15 issues with no replies (15) ========================================== #30740: SSLError when cancelling an SSL connection http://bugs.python.org/issue30740 #30739: pypi ssl errors [CERTIFICATE_VERIFY_FAILED] http://bugs.python.org/issue30739 #30735: Python 3.6.1 test_asyncio fails on Solaris 11 http://bugs.python.org/issue30735 #30734: 200000 indexes crashes eval and python (without eval) http://bugs.python.org/issue30734 #30733: Typo in Document What's New: Calendar http://bugs.python.org/issue30733 #30732: json.dumps() lacks information about RecursionError related to http://bugs.python.org/issue30732 #30730: Injecting environment variable in subprocess on Windows http://bugs.python.org/issue30730 #30724: ZipFile.open treats directory path as empty file http://bugs.python.org/issue30724 #30718: open builtin function: specifying the size of buffer has no ef http://bugs.python.org/issue30718 #30715: Test_winreg, test_dynamic_key hangs on my Win 10 http://bugs.python.org/issue30715 #30711: getaddrinfo invalid port number http://bugs.python.org/issue30711 #30705: python2.7 -m test -R 3:3 hangs on Refleaks 2.7 buildbots http://bugs.python.org/issue30705 #30704: test_free_different_thread() of test_code leaks references on http://bugs.python.org/issue30704 #30700: fileinput inplace clobbers file without leaving backup on deco http://bugs.python.org/issue30700 #30699: Misleading class names in datetime.tzinfo usage examples http://bugs.python.org/issue30699 Most recent 15 issues waiting for review (15) ============================================= #30730: Injecting environment variable in subprocess on Windows http://bugs.python.org/issue30730 #30714: test_ssl fails with openssl 1.1.0f http://bugs.python.org/issue30714 #30711: getaddrinfo invalid port number http://bugs.python.org/issue30711 #30710: getaddrinfo raises OverflowError http://bugs.python.org/issue30710 #30708: Ensure that the result of PyUnicode_AsWideCharString() doesn't http://bugs.python.org/issue30708 #30696: infinite loop in PyRun_InteractiveLoopFlags() http://bugs.python.org/issue30696 #30695: add a nomemory_allocator to the _testcapi module http://bugs.python.org/issue30695 #30693: tarfile add uses random order http://bugs.python.org/issue30693 #30688: support named Unicode escapes (\N{name}) in re http://bugs.python.org/issue30688 #30680: textwrap should treat Unicode em-dash like ASCII em-dash http://bugs.python.org/issue30680 #30665: pass big values for arg to fcntl.ioctl http://bugs.python.org/issue30665 #30593: sqlite3 executescript does not respect isolation_level? http://bugs.python.org/issue30593 #30560: Py_SetFatalErrorAbortFunc: Allow embedding program to handle f http://bugs.python.org/issue30560 #30541: Add restricted mocks to the python unittest mocking framework http://bugs.python.org/issue30541 #30519: Add daemon argument to Timer http://bugs.python.org/issue30519 Top 10 most discussed issues (10) ================================= #30500: [security] urllib connects to a wrong host http://bugs.python.org/issue30500 13 msgs #30695: add a nomemory_allocator to the _testcapi module http://bugs.python.org/issue30695 10 msgs #29591: expat 2.2.0: Various security vulnerabilities in bundled expat http://bugs.python.org/issue29591 9 msgs #30725: Windows installer for 2.7.13 doesn't install pip when installi http://bugs.python.org/issue30725 9 msgs #16258: test_local.TestEnUSCollection failures on Solaris 10 http://bugs.python.org/issue16258 8 msgs #30368: [2.7] OpenSSL compilation fails on AMD64 Windows7 SP1 VS9.0 2. http://bugs.python.org/issue30368 8 msgs #30694: Update embedded copy of expat to 2.2.1 http://bugs.python.org/issue30694 8 msgs #30710: getaddrinfo raises OverflowError http://bugs.python.org/issue30710 8 msgs #30726: [Windows] Warnings in elementtree due to new expat http://bugs.python.org/issue30726 8 msgs #30263: regrtest: log the system load? http://bugs.python.org/issue30263 7 msgs Issues closed (63) ================== #4765: IDLE fails to "Delete Custom Key Set" properly http://bugs.python.org/issue4765 closed by terry.reedy #10079: idlelib for Python 3 with Guilherme Polo GSoC enhancements http://bugs.python.org/issue10079 closed by terry.reedy #12420: distutils tests fail if PATH is not defined http://bugs.python.org/issue12420 closed by terry.reedy #14326: IDLE - allow shell to support different locales http://bugs.python.org/issue14326 closed by terry.reedy #15308: IDLE - add an "Interrupt Execution" to shell menu http://bugs.python.org/issue15308 closed by terry.reedy #17060: IDLE -- jump to home should not go past the PS1 and PS2 prompt http://bugs.python.org/issue17060 closed by terry.reedy #17187: Python segfaults from improperly formed and called function http://bugs.python.org/issue17187 closed by serhiy.storchaka #17773: test_pydoc fails with the installed testsuite (2.7) http://bugs.python.org/issue17773 closed by terry.reedy #18152: Idle: add 2.7 backport script http://bugs.python.org/issue18152 closed by terry.reedy #18316: Idle 2.7: update to simplify cross-version patches http://bugs.python.org/issue18316 closed by terry.reedy #18967: Find a less conflict prone approach to Misc/NEWS http://bugs.python.org/issue18967 closed by brett.cannon #20663: Introduce exception argument to iter http://bugs.python.org/issue20663 closed by terry.reedy #21071: struct.Struct.format is bytes, but should be str http://bugs.python.org/issue21071 closed by haypo #21632: Idle: sychronize text files across versions as appropriate. http://bugs.python.org/issue21632 closed by terry.reedy #22028: Python 3.4.1 Installer ended prematurely (Windows msi) http://bugs.python.org/issue22028 closed by tim.golden #22897: IDLE hangs on OS X with Cocoa Tk if encoding dialog is require http://bugs.python.org/issue22897 closed by terry.reedy #23337: [IDLE/Windows] Run python with restricted rights http://bugs.python.org/issue23337 closed by terry.reedy #23431: Idle Application Not Responding http://bugs.python.org/issue23431 closed by terry.reedy #24212: Idle, 2.7, backport idlelib.__main__, enable py -m idlelib http://bugs.python.org/issue24212 closed by terry.reedy #24718: Specify interpreter when running in IDLE http://bugs.python.org/issue24718 closed by terry.reedy #24936: Idle: handle 'raise' properly when running with subprocess (2. http://bugs.python.org/issue24936 closed by terry.reedy #25020: IDLE - centralize ui policies and small utilities http://bugs.python.org/issue25020 closed by terry.reedy #25125: "Edit with IDLE" does not work for shortcuts http://bugs.python.org/issue25125 closed by terry.reedy #25224: Replace Idle's README.txt with annotated file list http://bugs.python.org/issue25224 closed by terry.reedy #25303: Add option to py_compile to compile for syntax checking withou http://bugs.python.org/issue25303 closed by terry.reedy #26627: IDLE incorrectly labeling error as internal http://bugs.python.org/issue26627 closed by terry.reedy #26993: Copy idlelib *.py files with new names http://bugs.python.org/issue26993 closed by terry.reedy #27162: Add idlelib.interface module http://bugs.python.org/issue27162 closed by terry.reedy #28889: IDLE needs the ability to pass in command-line arguments http://bugs.python.org/issue28889 closed by terry.reedy #29366: os.listdir has inconsistent behavior when run on a non-directo http://bugs.python.org/issue29366 closed by terry.reedy #29523: latest setuptools breaks virtualenvs due to unbundling depende http://bugs.python.org/issue29523 closed by cstratak #29702: Error 0x80070003: Failed to launch elevated child process http://bugs.python.org/issue29702 closed by eryksun #29755: python3 gettext.lgettext sometimes returns bytes, not string http://bugs.python.org/issue29755 closed by serhiy.storchaka #30016: No sideways scrolling in IDLE http://bugs.python.org/issue30016 closed by terry.reedy #30054: Expose tracemalloc C API to track/untrack memory blocks http://bugs.python.org/issue30054 closed by haypo #30176: curses attribute constants list is incomplete http://bugs.python.org/issue30176 closed by xiang.zhang #30303: IDLE: Add _utest to textview and add textview tests http://bugs.python.org/issue30303 closed by terry.reedy #30360: getpass.getpass() does not accept stdin from an Expect script http://bugs.python.org/issue30360 closed by terry.reedy #30473: defaultdict raises SystemError, __missing__ returned NULL in t http://bugs.python.org/issue30473 closed by haypo #30565: PEP 538: silence locale coercion and compatibility warnings by http://bugs.python.org/issue30565 closed by ncoghlan #30598: Py_NewInterpreter() leaks a reference on warnoptions in _PySys http://bugs.python.org/issue30598 closed by ncoghlan #30602: [Windows] os.spawn*() tests of test_os leak references on Wind http://bugs.python.org/issue30602 closed by haypo #30604: co_extra_freefuncs is stored thread locally and can lead to cr http://bugs.python.org/issue30604 closed by yselivanov #30619: typing.Union doc incoherence in case a class and its subclass http://bugs.python.org/issue30619 closed by Mariatta #30629: lower() is called twice http://bugs.python.org/issue30629 closed by terry.reedy #30630: Missing MSI files http://bugs.python.org/issue30630 closed by terry.reedy #30657: Unsafe arithmetic in PyString_DecodeEscape http://bugs.python.org/issue30657 closed by serhiy.storchaka #30670: pprint for dict in sorted order or insert order? http://bugs.python.org/issue30670 closed by terry.reedy #30671: dict: improve lookup function http://bugs.python.org/issue30671 closed by tim.peters #30682: f-string assert is too restrictive http://bugs.python.org/issue30682 closed by eric.smith #30684: datetime.fromtimestamp raises OSError on first day after epoch http://bugs.python.org/issue30684 closed by r.david.murray #30687: build.bat should locate msbuild.exe rather than vcvarsall.bat http://bugs.python.org/issue30687 closed by steve.dower #30689: len() and iter() of ChainMap don't work with unhashable keys http://bugs.python.org/issue30689 closed by rhettinger #30690: ChainMap doesn't preserve the order of ordered mappings http://bugs.python.org/issue30690 closed by rhettinger #30702: pickle uses getattr(obj, '__reduce__') instead of getattr(type http://bugs.python.org/issue30702 closed by serhiy.storchaka #30709: Bad getter from Descriptor#Properties example http://bugs.python.org/issue30709 closed by Mariatta #30712: struct.unpack generates wrong error in certain conditions http://bugs.python.org/issue30712 closed by serhiy.storchaka #30720: re.sub substitution match group contains wrong value after unm http://bugs.python.org/issue30720 closed by serhiy.storchaka #30727: [2.7] test_threading.ConditionTests.test_notify() hangs random http://bugs.python.org/issue30727 closed by serhiy.storchaka #30729: Swap doesn't work in some circumstances http://bugs.python.org/issue30729 closed by rhettinger #30736: Support Unicode 10.0 http://bugs.python.org/issue30736 closed by benjamin.peterson #30738: __next__() method in iterators 9.9 http://bugs.python.org/issue30738 closed by eryksun #1080387: Making IDLE Themes and Keys Config more Robust http://bugs.python.org/issue1080387 closed by terry.reedy

2 1

Re: [Python-Dev] Star the CPython GitHub project if you like Python!
by rymg19＠gmail.com 30 Jun '17

30 Jun '17

I had tried to get people to star it after the GitHub migration, but I don't think too many did... FWIW Python's doing pretty well on GitHub considering it's only been there a couple of months. Only other project that did so well was Swift, and that was partly because it was previously closed-source. -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone elsehttp://refi64.com On Jun 30, 2017 at 9:01 AM, <Victor Stinner <victor.stinner(a)gmail.com>> wrote: Hi, GitHub has a showcase page of hosted programming languages: https://github.com/showcases/programming-languages Python is only #11 with 8,539 stars, behind PHP and Ruby! Hey, you should "like" ("star"?) the CPython project if you like Python! https://github.com/python/cpython/ Click on "Star" at the top right. Thank you! Victor _______________________________________________ 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/rymg19%40gmail.com

1 0