Sandbox::https://mail.python.org/archives/list/python-dev@python.org/2019/8/

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

Boundaries between numbers and identifiers
by Serhiy Storchaka April 15, 2021

April 15, 2021

In Python 2.5 `0or[]` was accepted by the Python parser. It became an error in 2.6 because "0o" became recognizing as an incomplete octal number. `1or[]` still is accepted. On other hand, `1if 2else 3` is accepted despites the fact that "2e" can be recognized as an incomplete floating point number. In this case the tokenizer pushes "e" back and returns "2". Shouldn't it do the same with "0o"? It is possible to make `0or[]` be parseable again. Python implementation is able to tokenize this example: $ echo '0or[]' | ./python -m tokenize 1,0-1,1: NUMBER '0' 1,1-1,3: NAME 'or' 1,3-1,4: OP '[' 1,4-1,5: OP ']' 1,5-1,6: NEWLINE '\n' 2,0-2,0: ENDMARKER '' On other hand, all these examples look weird. There is an assymmetry: `1or 2` is a valid syntax, but `1 or2` is not. It is hard to recognize visually the boundary between a number and the following identifier or keyword, especially if numbers can contain letters ("b", "e", "j", "o", "x") and underscores, and identifiers can contain digits. On both sides of the boundary can be letters, digits, and underscores. I propose to change the Python syntax by adding a requirement that there should be a whitespace or delimiter between a numeric literal and the following keyword.

8 10

About "python-porting" mail list
by Facundo Batista Jan. 20, 2020

Jan. 20, 2020

Hello! This list (which I co-admin, with Georg) is getting less and less traffic as months pass by. See: https://mail.python.org/pipermail/python-porting/ The interwebs has been collecting ton of resources about porting py2 to 3 during these years. Any not-yet-answered question surely can be done in a list with more participants. Can we kill this list? Thanks! Regards, -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org.ar/ Twitter: @facundobatista

4 7

Adding a toml module to the standard lib?
by Bastian Venthur Dec. 16, 2019

Dec. 16, 2019

Hi, I'd like to discuss the idea to add a module to parse TOML [toml-lang] to Python's standard library. PEP-0518 -- Specifying Minimum Build System Requirements for Python Projects [pep] suggests to store build system dependencies in `pyproject.toml`, yet Python itself does not support this format. Various packaging related projects like pip and pipenv already support PEP-0518 and vendored one of the existing TOML libraries in order to read `pyproject.toml` files. Besides that, TOML seems a better alternative to .cfg/.ini, .json -- both of which are already supported by Python's standard lib and parsing/dumping TOML properly is tricky enough to solve it properly [requirements]. There are a couple of TOML implementations out there [toml, pytoml, tomlkit] and one would have to find out which one to prefer and migrate into the stdlib. If the result of this discussion is leaning towards adding TOML, I'd volunteer to do it. This includes: coordinating with the maintainer of the chosen library, writing the PEP (hopefully with some help) and maintain the module for at least two years. Cheers, Bastian [toml-lang]: https://github.com/toml-lang/toml [pep]: https://www.python.org/dev/peps/pep-0518 [pip]: https://github.com/pypa/pip [pipenv]: https://github.com/pypa/pipenv [toml]: https://github.com/uiri/toml [pytoml]: https://github.com/avakar/pytoml [tomlkit]: https://github.com/sdispater/tomlkit [requirements]: https://devguide.python.org/stdlibchanges/#requirements -- Dr. Bastian Venthur http://venthur.de Debian Developer venthur at debian org

8 9

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

python3 -bb and hash collisions
by Daniel Holth Sept. 13, 2019

Sept. 13, 2019

set([u"foo", b"foo]) will error because the two kinds of string have the same hash, and this causes a comparison. Is that correct?

11 18

Python for Windows (python-3.7.4.exe) location confusing
by Armen Michaeli Sept. 10, 2019

Sept. 10, 2019

Hi all, The installer dialog mentions Python will be installed in something like $USERPROFILE\AppData\Local\Programs\Python\Python37-32 while at the same time suggesting it will be made available for all users through the "Install launcher for all users (recommended)". This is confusing -- if the package is to be made available for everybody, it shouldn't be installed somewhere under the profile folder of whomever is installing it, normally other people can't even access this folder at all. It should be installed in %Program Files(x86)%, unless it is a private installation indeed (the "Install launcher for all users" is unchecked). Is this an omission of sorts? Is one expected to correct this themselves, during installation -- I don't see where one would even specify the installation folder? [image: image.png]

7 10

PEP 581/588 RFC: Collecting feedback about GitHub Issues
by Mariatta Aug. 30, 2019

Aug. 30, 2019

(cross posting to python-committers, python-dev, core-workflow) PEP 581: Using GitHub Issues has been accepted by the steering council, but PEP 588: GitHub Issues Migration plan is still in progress. I'd like to hear from core developers as well as heavy b.p.o users, the following: 1. what features do they find lacking from GitHub issues, or 2. what are the things you can do in b.p.o but not in GitHub, or 3. Other workflow that will be blocked if we were to switch to GitHub today By understanding your needs, we can be better prepared for the migration, and we can start looking for solutions. In addition, I received tip that the GitHub team is very motivated to help us, and if we can give them some of our most wanted features, they *might* be able to accommodate us. But first we need to tell them what we need. They're not promising anything, but I'd like to at least try and give them these suggestions. Action items: 1. Please leave your comment in this issue: https://github.com/python/core-workflow/issues/359 2. Leave your +1 by reacting 👍 to suggested feature by others 3. Please do this before October 1, 2019 (not a hard deadline) Thanks ᐧ

2 2

Summary of Python tracker Issues
by Python tracker Aug. 30, 2019

Aug. 30, 2019

ACTIVITY SUMMARY (2019-08-23 - 2019-08-30) Python tracker at https://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 7114 (-39) closed 42626 (+97) total 49740 (+58) Open issues with patches: 2864 Issues opened (36) ================== #34410: itertools.tee not thread-safe; can segfault interpreter when w https://bugs.python.org/issue34410 reopened by serhiy.storchaka #37834: readlink on Windows cannot read app exec links https://bugs.python.org/issue37834 reopened by lukasz.langa #37932: ConfigParser.items(section) with allow_no_value returns empty https://bugs.python.org/issue37932 opened by Sean Robertson #37935: Improve performance of pathlib.scandir() https://bugs.python.org/issue37935 opened by Shai #37936: gitignore file is too broad https://bugs.python.org/issue37936 opened by Greg Price #37937: Mention ``frame.f_trace`` in :func:`sys.settrace` docs. https://bugs.python.org/issue37937 opened by cool-RR #37938: refactor PyLong_As*() functions https://bugs.python.org/issue37938 opened by sir-sigurd #37939: os.path.normpath change some characters of a path into kinda ' https://bugs.python.org/issue37939 opened by Yugi #37940: Add xml.tool to pretty print XML like json.tool https://bugs.python.org/issue37940 opened by xtreak #37941: python -m and runpy.run_module set different __name__ by defau https://bugs.python.org/issue37941 opened by Julian #37943: mimetypes.guess_extension() doesn’t get JPG right https://bugs.python.org/issue37943 opened by _savage #37945: test_locale failing https://bugs.python.org/issue37945 opened by tim.golden #37948: get_type_hints fails if there are un-annotated fields in a dat https://bugs.python.org/issue37948 opened by arne #37951: Disallow fork in a subinterpreter broke subprocesses in mod_ws https://bugs.python.org/issue37951 opened by christian.heimes #37952: Add support for export_keying_material to SSL library https://bugs.python.org/issue37952 opened by wingel71 #37953: Fix ForwardRef equality checks https://bugs.python.org/issue37953 opened by plokmijnuhby #37955: mock.patch incorrect reference to Mock https://bugs.python.org/issue37955 opened by phsilva #37956: UUID authorize version 6+ with variant RFC 4122 https://bugs.python.org/issue37956 opened by Erawpalassalg #37957: Allow regrtest to receive a file with test (and subtests) to i https://bugs.python.org/issue37957 opened by pablogsal #37958: Adding get_profile_dict to pstats https://bugs.python.org/issue37958 opened by Daniel Olshansky #37961: Tracemalloc traces do not include original stack trace length https://bugs.python.org/issue37961 opened by jd #37963: No URL for docs of pth files https://bugs.python.org/issue37963 opened by Thomas Güttler #37966: is_normalized is much slower at "no" than the standard's algor https://bugs.python.org/issue37966 opened by Greg Price #37967: release candidate is not gpg signed (and missing release workf https://bugs.python.org/issue37967 opened by mattip #37969: urllib.parse functions reporting false equivalent URIs https://bugs.python.org/issue37969 opened by maggyero #37970: urllib.parse docstrings incomplete https://bugs.python.org/issue37970 opened by zach.ware #37971: Wrong trace with multiple decorators (linenumber wrong in fram https://bugs.python.org/issue37971 opened by control-k #37972: unittest.mock.call does not chain __getitem__ to another _Call https://bugs.python.org/issue37972 opened by blhsing #37973: improve docstrings of sys.float_info https://bugs.python.org/issue37973 opened by sir-sigurd #37977: Big red pickle security warning should stress the point even m https://bugs.python.org/issue37977 opened by lordmauve #37980: regression when passing numpy bools to sorted(..., reverse=r) https://bugs.python.org/issue37980 opened by tcaswell #37981: Can't install Python 3.7.4 x64 on Win 8.1 https://bugs.python.org/issue37981 opened by Alexander Podgórski #37985: WFERR_UNMARSHALLABLE breaks recursion limit https://bugs.python.org/issue37985 opened by herring #37986: Improve perfomance of PyLong_FromDouble() https://bugs.python.org/issue37986 opened by sir-sigurd #37988: Issue found during language name processing in a list https://bugs.python.org/issue37988 opened by AjaySyam #37989: documentation format error in Chinese version https://bugs.python.org/issue37989 opened by 刘俨晖 Most recent 15 issues with no replies (15) ========================================== #37989: documentation format error in Chinese version https://bugs.python.org/issue37989 #37986: Improve perfomance of PyLong_FromDouble() https://bugs.python.org/issue37986 #37981: Can't install Python 3.7.4 x64 on Win 8.1 https://bugs.python.org/issue37981 #37977: Big red pickle security warning should stress the point even m https://bugs.python.org/issue37977 #37972: unittest.mock.call does not chain __getitem__ to another _Call https://bugs.python.org/issue37972 #37963: No URL for docs of pth files https://bugs.python.org/issue37963 #37958: Adding get_profile_dict to pstats https://bugs.python.org/issue37958 #37956: UUID authorize version 6+ with variant RFC 4122 https://bugs.python.org/issue37956 #37955: mock.patch incorrect reference to Mock https://bugs.python.org/issue37955 #37953: Fix ForwardRef equality checks https://bugs.python.org/issue37953 #37948: get_type_hints fails if there are un-annotated fields in a dat https://bugs.python.org/issue37948 #37941: python -m and runpy.run_module set different __name__ by defau https://bugs.python.org/issue37941 #37938: refactor PyLong_As*() functions https://bugs.python.org/issue37938 #37937: Mention ``frame.f_trace`` in :func:`sys.settrace` docs. https://bugs.python.org/issue37937 #37932: ConfigParser.items(section) with allow_no_value returns empty https://bugs.python.org/issue37932 Most recent 15 issues waiting for review (15) ============================================= #37977: Big red pickle security warning should stress the point even m https://bugs.python.org/issue37977 #37972: unittest.mock.call does not chain __getitem__ to another _Call https://bugs.python.org/issue37972 #37971: Wrong trace with multiple decorators (linenumber wrong in fram https://bugs.python.org/issue37971 #37966: is_normalized is much slower at "no" than the standard's algor https://bugs.python.org/issue37966 #37961: Tracemalloc traces do not include original stack trace length https://bugs.python.org/issue37961 #37955: mock.patch incorrect reference to Mock https://bugs.python.org/issue37955 #37953: Fix ForwardRef equality checks https://bugs.python.org/issue37953 #37951: Disallow fork in a subinterpreter broke subprocesses in mod_ws https://bugs.python.org/issue37951 #37938: refactor PyLong_As*() functions https://bugs.python.org/issue37938 #37936: gitignore file is too broad https://bugs.python.org/issue37936 #37935: Improve performance of pathlib.scandir() https://bugs.python.org/issue37935 #37931: crash reimporting posix after Py_Finalize on mac https://bugs.python.org/issue37931 #37921: Improve zipfile: add support for symlinks https://bugs.python.org/issue37921 #37916: distutils: allow overriding of the RANLIB command on macOS (da https://bugs.python.org/issue37916 #37913: Document that __length_hint__ may return NotImplemented https://bugs.python.org/issue37913 Top 10 most discussed issues (10) ================================= #37945: test_locale failing https://bugs.python.org/issue37945 16 msgs #37980: regression when passing numpy bools to sorted(..., reverse=r) https://bugs.python.org/issue37980 10 msgs #37951: Disallow fork in a subinterpreter broke subprocesses in mod_ws https://bugs.python.org/issue37951 8 msgs #37837: add internal _PyLong_FromUnsignedChar() function https://bugs.python.org/issue37837 7 msgs #20806: os.times document points to wrong section of non-Linux manual https://bugs.python.org/issue20806 5 msgs #37935: Improve performance of pathlib.scandir() https://bugs.python.org/issue37935 5 msgs #37940: Add xml.tool to pretty print XML like json.tool https://bugs.python.org/issue37940 5 msgs #37957: Allow regrtest to receive a file with test (and subtests) to i https://bugs.python.org/issue37957 5 msgs #37961: Tracemalloc traces do not include original stack trace length https://bugs.python.org/issue37961 5 msgs #37971: Wrong trace with multiple decorators (linenumber wrong in fram https://bugs.python.org/issue37971 5 msgs Issues closed (93) ================== #8425: a -= b should be fast if a is a small set and b is a large set https://bugs.python.org/issue8425 closed by rhettinger #9985: difflib.SequenceMatcher has slightly buggy and undocumented ca https://bugs.python.org/issue9985 closed by rhettinger #10190: Can argparse._AttributeHolder._get_kwargs become a public API? https://bugs.python.org/issue10190 closed by rhettinger #10978: Add optional argument to Semaphore.release for releasing multi https://bugs.python.org/issue10978 closed by rhettinger #12077: Harmonizing descriptor protocol documentation https://bugs.python.org/issue12077 closed by rhettinger #13653: reorder set.intersection parameters for better performance https://bugs.python.org/issue13653 closed by rhettinger #14010: deeply nested itertools objects segfault https://bugs.python.org/issue14010 closed by rhettinger #14112: tutorial intro talks of "shallow copy" concept without explana https://bugs.python.org/issue14112 closed by rhettinger #14619: Enhanced variable substitution for databases https://bugs.python.org/issue14619 closed by rhettinger #15542: Documentation incorrectly suggests __init__ called after direc https://bugs.python.org/issue15542 closed by rhettinger #16468: argparse only supports iterable choices https://bugs.python.org/issue16468 closed by rhettinger #17794: Add a key parameter to PriorityQueue https://bugs.python.org/issue17794 closed by rhettinger #18078: threading.Condition to allow notify on a specific waiter https://bugs.python.org/issue18078 closed by rhettinger #18378: locale.getdefaultlocale() fails on Mac OS X with default langu https://bugs.python.org/issue18378 closed by ned.deily #19072: classmethod doesn't honour descriptor protocol of wrapped call https://bugs.python.org/issue19072 closed by rhettinger #19119: duplicate test name in Lib/test/test_heapq.py https://bugs.python.org/issue19119 closed by rhettinger #19419: Use abc.ABC in the collections ABC https://bugs.python.org/issue19419 closed by rhettinger #22001: containers "same" does not always mean "__eq__". https://bugs.python.org/issue22001 closed by rhettinger #23061: Update pep8 to specify explicitly 'module level' imports at to https://bugs.python.org/issue23061 closed by rhettinger #23423: XPath Support in ElementTree doc omission https://bugs.python.org/issue23423 closed by scoder #23674: super() documentation isn't very clear https://bugs.python.org/issue23674 closed by rhettinger #23878: Missing sanity checks for various C library function calls... https://bugs.python.org/issue23878 closed by vstinner #24726: OrderedDict has strange behaviour when dict.__setitem__ is use https://bugs.python.org/issue24726 closed by rhettinger #25061: Add native enum support for argparse https://bugs.python.org/issue25061 closed by rhettinger #25435: Wrong function calls and referring to not removed concepts in https://bugs.python.org/issue25435 closed by rhettinger #25777: Misleading descriptions in docs about invoking descriptors. https://bugs.python.org/issue25777 closed by rhettinger #27260: Missing equality check for super objects https://bugs.python.org/issue27260 closed by rhettinger #27575: dict viewkeys intersection slow for large dicts https://bugs.python.org/issue27575 closed by rhettinger #28269: [MinGW] Can't compile Python/dynload_win.c due to static strca https://bugs.python.org/issue28269 closed by serhiy.storchaka #29352: provide the authorative source for s[i:j] negative slice indic https://bugs.python.org/issue29352 closed by rhettinger #29535: datetime hash is deterministic in some cases https://bugs.python.org/issue29535 closed by serhiy.storchaka #30162: Add _PyTuple_Empty and make PyTuple_New(0) never failing https://bugs.python.org/issue30162 closed by serhiy.storchaka #32118: Doc for comparison of sequences with non-orderable elements https://bugs.python.org/issue32118 closed by rhettinger #34259: Improve docstring of list.sort https://bugs.python.org/issue34259 closed by rhettinger #34679: asyncio.add_signal_handler call fails if not on main thread https://bugs.python.org/issue34679 closed by asvetlov #34775: pathlib.PurePath division raises TypeError instead of returnin https://bugs.python.org/issue34775 closed by ned.deily #35028: Off by one error in cgi.FieldStorage(max_num_fields) https://bugs.python.org/issue35028 closed by benjamin.peterson #35737: crypt AuthenticationError introduced with new Linux kernel https://bugs.python.org/issue35737 closed by icycle #35946: Ambiguous documentation for assert_called_with() https://bugs.python.org/issue35946 closed by ned.deily #36167: DOC: Incorrect capitalization in Programming FAQ https://bugs.python.org/issue36167 closed by ned.deily #36205: Python 3.7 and 3.8 process_time is not reported correctly when https://bugs.python.org/issue36205 closed by ned.deily #36582: collections.UserString encode method returns a string https://bugs.python.org/issue36582 closed by rhettinger #36743: Docs: Descript __get__ signature defined differently across th https://bugs.python.org/issue36743 closed by rhettinger #36763: Implementation of the PEP 587 https://bugs.python.org/issue36763 closed by vstinner #36833: Add tests for Datetime C API Macros https://bugs.python.org/issue36833 closed by vstinner #36871: Misleading error from unittest.mock's assert_has_calls https://bugs.python.org/issue36871 closed by xtreak #36917: ast.NodeVisitor no longer calls visit_Str https://bugs.python.org/issue36917 closed by serhiy.storchaka #37034: Argument Clinic omits name of keyword-only parameter on _PyArg https://bugs.python.org/issue37034 closed by serhiy.storchaka #37055: Numerous warnings with blake2 module https://bugs.python.org/issue37055 closed by christian.heimes #37140: ctypes change made clang fail to build https://bugs.python.org/issue37140 closed by vstinner #37176: super() docs don't say what super() does https://bugs.python.org/issue37176 closed by rhettinger #37328: remove deprecated HTMLParser.unescape https://bugs.python.org/issue37328 closed by inada.naoki #37372: datetime.time unpickling fails in case of python2 pickle with https://bugs.python.org/issue37372 closed by serhiy.storchaka #37385: test_multiprocessing fails on AMD64 FreeBSD CURRENT Shared 2.7 https://bugs.python.org/issue37385 closed by vstinner #37482: Email address display name fails with both encoded words and s https://bugs.python.org/issue37482 closed by bsiem #37549: os.dup() fails for standard streams on Windows 7 https://bugs.python.org/issue37549 closed by steve.dower #37664: Update bundled pip and setuptools https://bugs.python.org/issue37664 closed by steve.dower #37757: TargetScopeError not raised for comprehension scope conflict https://bugs.python.org/issue37757 closed by ncoghlan #37772: zipfile.Path.iterdir() outputs sub directories many times or n https://bugs.python.org/issue37772 closed by jaraco #37798: Add C fastpath for statistics.NormalDist.inv_cdf() https://bugs.python.org/issue37798 closed by rhettinger #37805: json.dump(..., skipkeys=True) has no unit tests https://bugs.python.org/issue37805 closed by inada.naoki #37812: Make implicit returns explicit in longobject.c (in CHECK_SMALL https://bugs.python.org/issue37812 closed by rhettinger #37830: continue and break in finally with return in try results with https://bugs.python.org/issue37830 closed by serhiy.storchaka #37905: Improve docs for NormalDist https://bugs.python.org/issue37905 closed by rhettinger #37914: class timedelta, support the method hours and minutes in field https://bugs.python.org/issue37914 closed by elinaldosoft #37918: What about an enum for open() modes? https://bugs.python.org/issue37918 closed by vstinner #37925: --embed not included in python3.8-config usage/--help https://bugs.python.org/issue37925 closed by vstinner #37929: IDLE: OK sometimes fails to close configdialog https://bugs.python.org/issue37929 closed by taleinat #37930: make fails when compiling Python 2.6 from source (posixmodule. https://bugs.python.org/issue37930 closed by ned.deily #37933: faulthandler causes segfaults https://bugs.python.org/issue37933 closed by vstinner #37934: Docs: Clarify NotImplemented use cases https://bugs.python.org/issue37934 closed by rhettinger #37942: Generate correct error check for PyFloat_AsDouble https://bugs.python.org/issue37942 closed by rhettinger #37944: Adjacent escape character in json.load() https://bugs.python.org/issue37944 closed by serhiy.storchaka #37946: Add the Bessel functions of the first and second kind to the m https://bugs.python.org/issue37946 closed by pablogsal #37947: symtable_handle_namedexpr does not adjust correctly the recurs https://bugs.python.org/issue37947 closed by pablogsal #37949: Create empty __annotations__ dictionaries lazily https://bugs.python.org/issue37949 closed by rhettinger #37950: ast.dump() with incomplete node https://bugs.python.org/issue37950 closed by serhiy.storchaka #37954: Multiple tests are leaking references in AMD64 Windows8.1 Refl https://bugs.python.org/issue37954 closed by pablogsal #37959: test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBS https://bugs.python.org/issue37959 closed by vstinner #37960: repr() of buffered and text streams silences too many exceptio https://bugs.python.org/issue37960 closed by serhiy.storchaka #37962: Improve ISO 8601 timezone support in the datetime.fromisoforma https://bugs.python.org/issue37962 closed by p-ganssle #37964: F_GETPATH is not available in fcntl.fcntl https://bugs.python.org/issue37964 closed by miss-islington #37965: CCompiler has_function displays warning https://bugs.python.org/issue37965 closed by miss-islington #37968: Add a turtle module function to draw a circle centered at the https://bugs.python.org/issue37968 closed by rhettinger #37974: zip() docstring should say 'iterator' instead of 'object with https://bugs.python.org/issue37974 closed by rhettinger #37975: Typo in the documentation by C-API DateTime Objects¶ https://bugs.python.org/issue37975 closed by xtreak #37976: zip() shadows TypeError raised in __iter__() of source iterabl https://bugs.python.org/issue37976 closed by rhettinger #37978: Importing an unused package causes the function of another pac https://bugs.python.org/issue37978 closed by christian.heimes #37979: Document an alternative to ISO 8601 parsing https://bugs.python.org/issue37979 closed by pitrou #37982: Add a --minify argument to json.tool https://bugs.python.org/issue37982 closed by rhettinger #37983: macOS: os.lchmod() incorrectly removed by 2.7.16 https://bugs.python.org/issue37983 closed by ned.deily #37984: Unable parse csv on latin iso or binary mode https://bugs.python.org/issue37984 closed by rhettinger #37987: retrun collection item in for cycle with finally continue https://bugs.python.org/issue37987 closed by serhiy.storchaka

1 0

Python-Dev

August 2019