Mailman 3 May 2020 - Python-Dev

Mixed Python/C debugging
by Skip Montanaro 26 Apr '23

26 Apr '23

Having tried comp.lang.python with no response, I turn here... After at least ten years away from Python's run-time interpreter & byte code compiler, I'm getting set to familiarize myself with that again. This will, I think, entail debugging a mixed Python/C environment. I'm an Emacs user and am aware that GDB since 7.0 has support for debugging at the Python code level. Is Emacs+GDB my best bet? Are there any Python IDEs which support C-level breakpoints and debugging? Thanks, Skip

5 6

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

Boundaries between numbers and identifiers
by Serhiy Storchaka 15 Apr '21

15 Apr '21

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

pathlib.Path: inconsistent symlink_to() and link_to()
by Barney Gale 22 Jan '21

22 Jan '21

Hi, Pathlib's symlink_to() and link_to() methods have different argument orders, so: a.symlink_to(b) # Creates a symlink from A to B a.link_to(b) # Creates a hard link from B to A I don't think link_to() was intended to be implemented this way, as the docs say "Create a hard link pointing to a path named target.". It's also inconsistent with everything else in pathlib, most obviously symlink_to(). Bug report here: https://bugs.python.org/issue39291 This /really/ irks me. Apparently it's too late to fix link_to(), so I'd like to suggest we add a new hardlink_to() method that matches the symlink_to() argument order. link_to() then becomes deprecated/undocumented. Any thoughts? Barney

4 5

Summary of Python tracker Issues
by Python tracker 05 Jun '20

05 Jun '20

ACTIVITY SUMMARY (2020-05-22 - 2020-05-29) 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 7487 ( +9) closed 45080 (+80) total 52567 (+89) Open issues with patches: 3011 Issues opened (58) ================== #39343: Travis CI: documentation job fails in library/nntplib.rst with https://bugs.python.org/issue39343 reopened by chris.jerdonek #40133: Provide additional matchers for unittest.mock https://bugs.python.org/issue40133 reopened by gregory.p.smith #40733: Make IDLE doc more visible, mention in main python docs page https://bugs.python.org/issue40733 opened by phr #40734: /usr/bin surprisingly in sys.path under IDLE https://bugs.python.org/issue40734 opened by phr #40735: test_nntplib: sporadic failures, NetworkedNNTP_SSLTests.test_w https://bugs.python.org/issue40735 opened by chris.jerdonek #40736: better message for re.search TypeError ("expected string or by https://bugs.python.org/issue40736 opened by chris.jerdonek #40739: find_library broken for binutils >= 2.32 / 2.34 https://bugs.python.org/issue40739 opened by Frederik Rietdijk #40741: Upgrade to SQLite v3.32.1 in Windows and macOS builds https://bugs.python.org/issue40741 opened by erlendaasland #40742: Doc: Parallel build break audit table https://bugs.python.org/issue40742 opened by mdk #40743: [CMake] It's 2020, where is CMake? https://bugs.python.org/issue40743 opened by TheUltimatePineapple #40744: Explicitly drop support for SQLite version < 3.7.3 https://bugs.python.org/issue40744 opened by erlendaasland #40745: Typo in library/typing https://bugs.python.org/issue40745 opened by hectorcanto #40746: test_gdb failing on Raspbian on 3.9, regression from 3.8 https://bugs.python.org/issue40746 opened by gregory.p.smith #40747: sysconfig.get_config_var("py_version_nodot") should return 3_1 https://bugs.python.org/issue40747 opened by mattip #40748: Tutorial 4.7 More on Defining Functions missing screen prompts https://bugs.python.org/issue40748 opened by Chas Belov #40749: Consider adding decorator for required inner class https://bugs.python.org/issue40749 opened by Elijah Rippeth #40754: ModuleNotFoundError: No module named '_testinternalcapi' under https://bugs.python.org/issue40754 opened by honglei.jiang #40756: Second argument of LoggerAdapter.__init__ should default to No https://bugs.python.org/issue40756 opened by arturoescaip #40757: tarfile: ignore_zeros = True won't raise exception even on inv https://bugs.python.org/issue40757 opened by mxmlnkn #40758: For 7.2.7. Code Examples, distinguish between the Tutorial and https://bugs.python.org/issue40758 opened by Chas Belov #40759: Deprecate the symbol module https://bugs.python.org/issue40759 opened by BTaskaya #40762: Writing bytes using CSV module results in b prefixed strings https://bugs.python.org/issue40762 opened by sidhant #40763: zipfile.extractall is safe by now https://bugs.python.org/issue40763 opened by VA #40766: Add support for SQLITE_DIRECTONLY and SQLITE_INNOCUOUS for use https://bugs.python.org/issue40766 opened by erlendaasland #40767: Allow pure Wayland to get default XDG webbrowser https://bugs.python.org/issue40767 opened by Jeremy Attali #40769: Pegen: cover extra surrounding parentheses for invalid annotat https://bugs.python.org/issue40769 opened by BTaskaya #40770: RFE: Run linkchecker on documentation on the CI https://bugs.python.org/issue40770 opened by hroncok #40771: python3 fromtimestamp generates OSError https://bugs.python.org/issue40771 opened by jamercee #40772: module 'resource' has no attribute 'RLIMIT_VMEM' https://bugs.python.org/issue40772 opened by Titusz Ban #40773: DOC: Fix rendering for 'retval' on the pdb page https://bugs.python.org/issue40773 opened by cheryl.sabella #40775: Fix missing dot in sqlite3 Node type name https://bugs.python.org/issue40775 opened by erlendaasland #40777: _datetimemodule.c:3328:16: error: initializer element is not c https://bugs.python.org/issue40777 opened by smani #40782: AbstactEventLoop.run_in_executor is listed as an async method, https://bugs.python.org/issue40782 opened by jamesba #40785: `mmap.mmap(..., 0)` doesn't work as advertised in docs (fails https://bugs.python.org/issue40785 opened by ngie #40786: madvise should be accessible outside of mmap instance https://bugs.python.org/issue40786 opened by ngie #40788: Build issue Solaris 10 Sparc https://bugs.python.org/issue40788 opened by munocat #40791: hmac.compare_digest could try harder to be constant-time. https://bugs.python.org/issue40791 opened by Devin Jeanpierre #40794: dataclass signatures and docstrings w/future-annotations https://bugs.python.org/issue40794 opened by BTaskaya #40797: multiprocessing.Semaphore has undocumented get_value() method https://bugs.python.org/issue40797 opened by remi.lapeyre #40798: The deprecated-removed Sphinx extension need to change the err https://bugs.python.org/issue40798 opened by remi.lapeyre #40799: Create Lib/_pydatetime.py file to optimize "import datetime" w https://bugs.python.org/issue40799 opened by vstinner #40800: asyncio.sleep(0) should "yield" back to the event loop, but it https://bugs.python.org/issue40800 opened by Davy Durham #40801: Expose PyFloat_AsDouble at Python level: operator.as_float? https://bugs.python.org/issue40801 opened by mark.dickinson #40802: AbstractEventLoop.shutdown_default_executor breaks backwards c https://bugs.python.org/issue40802 opened by petr.viktorin #40804: Bug report in python3.6.8 using argparse module https://bugs.python.org/issue40804 opened by amansi26 #40805: Can no longer patch flask.g https://bugs.python.org/issue40805 opened by Rob Taft #40807: CODEOP: Show warnings once during _maybe_compile https://bugs.python.org/issue40807 opened by cheryl.sabella #40808: test_venv fails with HOME=/ on AMD64 FreeBSD Non-Debug 3.x https://bugs.python.org/issue40808 opened by vstinner #40810: sqlite3 test CheckTraceCallbackContent fails for sqlite v3.7.3 https://bugs.python.org/issue40810 opened by erlendaasland #40811: Allow to create new Event Loops on Threads https://bugs.python.org/issue40811 opened by Christian Exposito #40813: Output SyntaxError is not defective https://bugs.python.org/issue40813 opened by timofej #40814: Update typing module documentation based on PEP 585 https://bugs.python.org/issue40814 opened by Matúš Valo #40815: Multiprocessing docs don't describe thread-safety https://bugs.python.org/issue40815 opened by bjs #40816: Add missed AsyncContextDecorator to contextlib https://bugs.python.org/issue40816 opened by heckad #40817: Document the asyncio shell https://bugs.python.org/issue40817 opened by remi.lapeyre #40818: Run sys.__interactivehook__ for asyncio REPLs https://bugs.python.org/issue40818 opened by remi.lapeyre #40819: Idle Context Menu Copy/Cut Grayed Out https://bugs.python.org/issue40819 opened by BevInTX #40820: Mock Call attributes args and kwargs have no changeversion https://bugs.python.org/issue40820 opened by Andrius Gobis Most recent 15 issues with no replies (15) ========================================== #40820: Mock Call attributes args and kwargs have no changeversion https://bugs.python.org/issue40820 #40819: Idle Context Menu Copy/Cut Grayed Out https://bugs.python.org/issue40819 #40818: Run sys.__interactivehook__ for asyncio REPLs https://bugs.python.org/issue40818 #40816: Add missed AsyncContextDecorator to contextlib https://bugs.python.org/issue40816 #40815: Multiprocessing docs don't describe thread-safety https://bugs.python.org/issue40815 #40814: Update typing module documentation based on PEP 585 https://bugs.python.org/issue40814 #40808: test_venv fails with HOME=/ on AMD64 FreeBSD Non-Debug 3.x https://bugs.python.org/issue40808 #40807: CODEOP: Show warnings once during _maybe_compile https://bugs.python.org/issue40807 #40805: Can no longer patch flask.g https://bugs.python.org/issue40805 #40802: AbstractEventLoop.shutdown_default_executor breaks backwards c https://bugs.python.org/issue40802 #40800: asyncio.sleep(0) should "yield" back to the event loop, but it https://bugs.python.org/issue40800 #40797: multiprocessing.Semaphore has undocumented get_value() method https://bugs.python.org/issue40797 #40788: Build issue Solaris 10 Sparc https://bugs.python.org/issue40788 #40786: madvise should be accessible outside of mmap instance https://bugs.python.org/issue40786 #40775: Fix missing dot in sqlite3 Node type name https://bugs.python.org/issue40775 Most recent 15 issues waiting for review (15) ============================================= #40818: Run sys.__interactivehook__ for asyncio REPLs https://bugs.python.org/issue40818 #40816: Add missed AsyncContextDecorator to contextlib https://bugs.python.org/issue40816 #40811: Allow to create new Event Loops on Threads https://bugs.python.org/issue40811 #40810: sqlite3 test CheckTraceCallbackContent fails for sqlite v3.7.3 https://bugs.python.org/issue40810 #40807: CODEOP: Show warnings once during _maybe_compile https://bugs.python.org/issue40807 #40801: Expose PyFloat_AsDouble at Python level: operator.as_float? https://bugs.python.org/issue40801 #40799: Create Lib/_pydatetime.py file to optimize "import datetime" w https://bugs.python.org/issue40799 #40798: The deprecated-removed Sphinx extension need to change the err https://bugs.python.org/issue40798 #40791: hmac.compare_digest could try harder to be constant-time. https://bugs.python.org/issue40791 #40777: _datetimemodule.c:3328:16: error: initializer element is not c https://bugs.python.org/issue40777 #40775: Fix missing dot in sqlite3 Node type name https://bugs.python.org/issue40775 #40769: Pegen: cover extra surrounding parentheses for invalid annotat https://bugs.python.org/issue40769 #40767: Allow pure Wayland to get default XDG webbrowser https://bugs.python.org/issue40767 #40766: Add support for SQLITE_DIRECTONLY and SQLITE_INNOCUOUS for use https://bugs.python.org/issue40766 #40762: Writing bytes using CSV module results in b prefixed strings https://bugs.python.org/issue40762 Top 10 most discussed issues (10) ================================= #40762: Writing bytes using CSV module results in b prefixed strings https://bugs.python.org/issue40762 15 msgs #30064: BaseSelectorEventLoop.sock_{recv,sendall}() don't remove their https://bugs.python.org/issue30064 13 msgs #40794: dataclass signatures and docstrings w/future-annotations https://bugs.python.org/issue40794 11 msgs #38605: [typing] PEP 563: Postponed evaluation of annotations: enable https://bugs.python.org/issue38605 10 msgs #40701: tempfile mixes str and bytes in an inconsistent manner https://bugs.python.org/issue40701 10 msgs #40801: Expose PyFloat_AsDouble at Python level: operator.as_float? https://bugs.python.org/issue40801 9 msgs #40217: The garbage collector doesn't take in account that objects of https://bugs.python.org/issue40217 8 msgs #40748: Tutorial 4.7 More on Defining Functions missing screen prompts https://bugs.python.org/issue40748 8 msgs #2897: PyMemberDef missing in limited API / Deprecate structmember.h https://bugs.python.org/issue2897 7 msgs #40275: test.support has way too many imports https://bugs.python.org/issue40275 7 msgs Issues closed (78) ================== #13097: [easy C issue] ctypes: segfault with large number of callback https://bugs.python.org/issue13097 closed by vstinner #14562: urllib2 maybe blocks too long with small chunks https://bugs.python.org/issue14562 closed by benjamin.peterson #17050: argparse.REMAINDER doesn't work as first argument https://bugs.python.org/issue17050 closed by rhettinger #23082: pathlib relative_to() can give confusing error message https://bugs.python.org/issue23082 closed by steve.dower #23721: Set up a daily test coverage run https://bugs.python.org/issue23721 closed by brett.cannon #25247: Tkinter modules built successfully but removed because they co https://bugs.python.org/issue25247 closed by ned.deily #25920: PyOS_AfterFork should reset socketmodule's lock https://bugs.python.org/issue25920 closed by vstinner #26415: Excessive peak memory consumption by the Python parser https://bugs.python.org/issue26415 closed by pablogsal #29882: Add an efficient popcount method for integers https://bugs.python.org/issue29882 closed by mark.dickinson #30986: Add --include-py argument to Tools/msi/make_zip.py https://bugs.python.org/issue30986 closed by cheryl.sabella #32398: OSX C++ linking workaround in distutils breaks other packages https://bugs.python.org/issue32398 closed by cheryl.sabella #33111: Merely importing tkinter breaks parallel code (multiprocessing https://bugs.python.org/issue33111 closed by ned.deily #33388: Support PEP 566 metadata in distutils https://bugs.python.org/issue33388 closed by eric.araujo #34397: remove redundant overflow checks in tuple and list implementat https://bugs.python.org/issue34397 closed by cheryl.sabella #35545: asyncio.base_events.create_connection doesn't handle scoped IP https://bugs.python.org/issue35545 closed by cheryl.sabella #36290: _ast.ast_type_init does not handle args and kwargs correctly. https://bugs.python.org/issue36290 closed by pablogsal #37129: Add os.RWF_APPEND flag for os.pwritev https://bugs.python.org/issue37129 closed by vstinner #37218: Default hmac.new() digestmod has not been removed from documen https://bugs.python.org/issue37218 closed by cheryl.sabella #37973: improve docstrings of sys.float_info https://bugs.python.org/issue37973 closed by mark.dickinson #37999: No longer use implicit convertion to int with loss https://bugs.python.org/issue37999 closed by serhiy.storchaka #38580: select()'s documentation claims only sequences are accepted, b https://bugs.python.org/issue38580 closed by taleinat #39244: multiprocessing.get_all_start_methods() wrong default on macOS https://bugs.python.org/issue39244 closed by taleinat #39685: Python 3.8 regression Socket operation on non-socket https://bugs.python.org/issue39685 closed by christian.heimes #39686: add dump_json to ast module https://bugs.python.org/issue39686 closed by cheryl.sabella #40160: documentation example of os.walk should be less destructive https://bugs.python.org/issue40160 closed by serhiy.storchaka #40327: list(sys.modules.items()) can throw RuntimeError: dictionary c https://bugs.python.org/issue40327 closed by rhettinger #40367: ImportError: libffi.so.6 https://bugs.python.org/issue40367 closed by YoSTEALTH #40373: urlunparse does not escape slash (/) for http+unix:// in netlo https://bugs.python.org/issue40373 closed by taleinat #40439: Error in an external reference https://bugs.python.org/issue40439 closed by cheryl.sabella #40474: Code coverage report not entirely accurate https://bugs.python.org/issue40474 closed by brett.cannon #40552: Enhance for loop and copy example in tutorial https://bugs.python.org/issue40552 closed by nanjekyejoannah #40558: update CONTRIBUTING.rst docs https://bugs.python.org/issue40558 closed by zach.ware #40586: Pydoc should support https for hyperlinks. https://bugs.python.org/issue40586 closed by cheryl.sabella #40611: Add MAP_POPULATE to the mmap library https://bugs.python.org/issue40611 closed by vstinner #40646: Builtins in doc show signature in documentation https://bugs.python.org/issue40646 closed by terry.reedy #40654: shutil.copyfile mutates symlink for absolute path https://bugs.python.org/issue40654 closed by steve.dower #40663: Wrong generated annotation on subscripting https://bugs.python.org/issue40663 closed by pablogsal #40667: [Windows] Add global python and python3 commands https://bugs.python.org/issue40667 closed by steve.dower #40678: Full list of Python lexical rules https://bugs.python.org/issue40678 closed by cool-RR #40679: show class name in method invocation TypeError https://bugs.python.org/issue40679 closed by chris.jerdonek #40688: PEG Generator: Fix scripts to always use the correct parser https://bugs.python.org/issue40688 closed by lys.nikolaou #40719: Add pt-br to the language switcher at the Python 3.6 and 2.7 d https://bugs.python.org/issue40719 closed by rffontenelle #40722: test_ttk_guionly times out on Ubuntu CI https://bugs.python.org/issue40722 closed by terry.reedy #40730: Odd sentence in 3.9 What's New https://bugs.python.org/issue40730 closed by eric.smith #40731: CWI url's protocol on LICENSE file from http to https https://bugs.python.org/issue40731 closed by gvanrossum #40732: New realpath breaks setuptools_scm https://bugs.python.org/issue40732 closed by jaraco #40737: Fix possible reference leak for sqlite3 initialization https://bugs.python.org/issue40737 closed by corona10 #40738: backspace character \b not processed by IDLE https://bugs.python.org/issue40738 closed by terry.reedy #40740: Missing api-ms-win-core-path-l1-1.0.dll for python-3.9.0b1-amd https://bugs.python.org/issue40740 closed by steve.dower #40750: Support -d flag in the new parser https://bugs.python.org/issue40750 closed by pablogsal #40751: command 'elif' does not work https://bugs.python.org/issue40751 closed by terry.reedy #40752: Implement PurePath.__len__ https://bugs.python.org/issue40752 closed by serhiy.storchaka #40753: Remove Python 2 compatibility code from pathlib https://bugs.python.org/issue40753 closed by brett.cannon #40755: Add missing multiset predicates to collections.Counter https://bugs.python.org/issue40755 closed by rhettinger #40760: Dictionary comprehension using older division behavior https://bugs.python.org/issue40760 closed by Amol Sharma #40761: unittest.TestCase.assertTrue return True even if the expr is F https://bugs.python.org/issue40761 closed by zach.ware #40764: Conflation of Counter with Multiset https://bugs.python.org/issue40764 closed by rhettinger #40765: clear screen in idle https://bugs.python.org/issue40765 closed by terry.reedy #40768: pyaudio https://bugs.python.org/issue40768 closed by SilentGhost #40774: "Important" block in documentation of asyncio.create_subproces https://bugs.python.org/issue40774 closed by benjamin.peterson #40776: Python 3.7.6 installation issue on mac os x 10.6.8 https://bugs.python.org/issue40776 closed by ned.deily #40778: Updating Py_REFCNT and Py_SIZE to use _PyObject_CAST_CONS https://bugs.python.org/issue40778 closed by corona10 #40779: incorrect end column for single argument generator function ca https://bugs.python.org/issue40779 closed by pablogsal #40780: float.__format__() handles trailing zeros inconsistently in � https://bugs.python.org/issue40780 closed by mark.dickinson #40781: Remove sys._debugmallocstats() function and PYTHONMALLOCSTATS https://bugs.python.org/issue40781 closed by vstinner #40783: test_interpreters test_interpreters leaked [216, 216, 216] ref https://bugs.python.org/issue40783 closed by pablogsal #40784: test_sqlite: CheckFuncDeterministic() fails with SQLite 3.32 https://bugs.python.org/issue40784 closed by berker.peksag #40787: Mysql + unittest crash https://bugs.python.org/issue40787 closed by lgerosa #40789: C-level destructor in PySide2 breaks gen_send_ex, which assume https://bugs.python.org/issue40789 closed by njs #40790: Python should enable computed gotos on Mac by default https://bugs.python.org/issue40790 closed by benjamin.peterson #40792: Make PyNumber_Index() always returning an exact int instance https://bugs.python.org/issue40792 closed by serhiy.storchaka #40793: print() performance problem with very large numbers https://bugs.python.org/issue40793 closed by mark.dickinson #40795: ctypes: PyErr_WriteUnraisable() called with no exception set o https://bugs.python.org/issue40795 closed by vstinner #40796: dataclasses.make_dataclass: Exception when called with differe https://bugs.python.org/issue40796 closed by Darrick Yee #40803: Unable to execute python.exe from zip in wine https://bugs.python.org/issue40803 closed by clanmills #40806: itertools.product not lazy https://bugs.python.org/issue40806 closed by rhettinger #40809: list.Count() isn't working as expected for the series of same https://bugs.python.org/issue40809 closed by steven.daprano #40812: _tkinter build failed when install Python-3.6.10 https://bugs.python.org/issue40812 closed by ned.deily

2 1

PEP 618: Add Optional Length-Checking To zip
by Brandt Bucher 02 Jun '20

02 Jun '20

I have pushed a second draft of PEP 618: https://www.python.org/dev/peps/pep-0618 Please let me know what you think – I'd love to hear any new feedback that hasn't yet been addressed in the PEP! Brandt

23 60

Repr: where to place the address and additional info?
by Serhiy Storchaka 01 Jun '20

01 Jun '20

The default repr of Python object is formatted using the following pattern: <{typename} object at {address:#x}> And many custom reprs use similar patterns, but add some additional type specific information. The type name first, followed by details and address. All is surrounded by angle quotes. The question is in what order to show address and other details? Should the address be at rear or in the middle? <{typename} {details} at {address:#x}> <{typename} at {address:#x} {details}> There are examples of both ways in the stdlib. I am going to add new custom reprs [1] and need to know what pattern looks better. Also, is "object" mandatory after the type name? <{typename} object {details} at {address:#x}> <{typename} object at {address:#x} {details}> [1] https://bugs.python.org/issue24391

5 4

PEG parser and raw strings
by Vito De Tullio 29 May '20

29 May '20

Hi. Just a question about the new PEG parser: will it support lone slash in raw strings? the fact that r'\' doesn't work as expected it's a strange exception to remember.

5 4

Map errno==ETIME to TimeoutError
by Eric V. Smith 26 May '20

26 May '20

Does anyone have an opinion on https://bugs.python.org/issue39673? It maps ETIME to TimeoutError, in addition to the already existing ETIMEDOUT. http://man7.org/linux/man-pages/man3/errno.3.html says: *ETIME *Timer expired (POSIX.1 (XSI STREAMS option)). (POSIX.1 says "STREAMioctl(2) <http://man7.org/linux/man-pages/man2/ioctl.2.html> timeout".) *ETIMEDOUT *Connection timed out (POSIX.1-2001). It seems like a reasonable change to me, but I'm not a subject matter expert on STREAMS, or what other affect this might have. And if added to 3.10, should it be backported? I'd tend to say "no", because of unknown impacts on existing code. Eric

8 12