Mailman 3 December 2018 - Python-Dev

PEP 448 review
by Guido van Rossum March 29, 2023

March 29, 2023

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

7 17

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

May 18, 2021

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

8 14

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

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

why is not 64-bit installer the default download link for Windows?
by Cosimo Lupo June 19, 2019

June 19, 2019

If one goes to httWhps://www.python.org/downloads <https://www.python.org/downloads> from a Windows browser, the default download URL is for the 32-bit installer instead of the 64-bit one. I wonder why is this still the case? Shouldn't we encourage new Windows users (who may not even know the distinction between the two architectures) to use the 64-bit version of Python, since most likely they can? If this is not the correct forum for this, please let me know where I can direct my question/feature request, thanks. Cosimo -- Cosimo Lupo

14 22

Summary of Python tracker Issues
by Python tracker Dec. 28, 2018

Dec. 28, 2018

ACTIVITY SUMMARY (2018-12-21 - 2018-12-28) 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 6902 ( +6) closed 40454 (+47) total 47356 (+53) Open issues with patches: 2739 Issues opened (33) ================== #35556: See if frozen modules can use relative imports https://bugs.python.org/issue35556 opened by brett.cannon #35557: Allow lowercase hexadecimal characters in base64.b16decode() https://bugs.python.org/issue35557 opened by djhoulihan #35560: format(float(123), "00") causes segfault in debug builds https://bugs.python.org/issue35560 opened by xtreak #35561: Valgrind reports Syscall param epoll_ctl(event) points to unin https://bugs.python.org/issue35561 opened by nikratio #35563: Doc: warnings.rst - add links to references https://bugs.python.org/issue35563 opened by cheryl.sabella #35568: Expose the C raise() function in the signal module, for use on https://bugs.python.org/issue35568 opened by njs #35569: OSX: Enable IPV6_RECVPKTINFO https://bugs.python.org/issue35569 opened by chrysn #35570: 2to3 creates code using deprecated imp module https://bugs.python.org/issue35570 opened by hanno #35571: Parallel Timeout Class https://bugs.python.org/issue35571 opened by Stefan Volz #35573: is_HDN is returns false positive and false negative value for https://bugs.python.org/issue35573 opened by Divya Rani #35577: side_effect mocked method lose reference to instance https://bugs.python.org/issue35577 opened by Adnan Umer #35578: Add test for Argument Clinic converters https://bugs.python.org/issue35578 opened by serhiy.storchaka #35580: Windows IocpProactor: CreateIoCompletionPort 4th arg 0xfffffff https://bugs.python.org/issue35580 opened by jeffr(a)livedata.com #35581: Document @typing.type_check_only https://bugs.python.org/issue35581 opened by srittau #35582: Argument Clinic: inline parsing code for functions with only p https://bugs.python.org/issue35582 opened by serhiy.storchaka #35583: (glibc2.28/MIPS32EL) python 3.7.x interpreter segmentation fau https://bugs.python.org/issue35583 opened by broly #35584: Wrong statement about ^ in howto/regex.rst https://bugs.python.org/issue35584 opened by mdk #35586: Open pyexpat compilation, Make shows error（missing separator https://bugs.python.org/issue35586 opened by kbengine #35588: Speed up mod/divmod/floordiv for Fraction type https://bugs.python.org/issue35588 opened by scoder #35589: BaseSelectorEventLoop.sock_sendall() performance regression: e https://bugs.python.org/issue35589 opened by Huazuo Gao #35590: logging.handlers.SysLogHandler with STREAM connects in constru https://bugs.python.org/issue35590 opened by jso2460 #35592: Not able to use Python 3.7.2 due to SSL issue https://bugs.python.org/issue35592 opened by Gunasekar Rajendran #35593: Register standard browser: Chrome https://bugs.python.org/issue35593 opened by eamanu #35594: Python script generating Segmentation Fault https://bugs.python.org/issue35594 opened by Daugeras #35595: Add sys flag to always show full paths in stack traces (instea https://bugs.python.org/issue35595 opened by Scott Arciszewski #35596: Fatal Python error: initfsencoding: unable to load the file sy https://bugs.python.org/issue35596 opened by hyu #35598: IDLE: Modernize config_key module https://bugs.python.org/issue35598 opened by cheryl.sabella #35599: asyncio windows_events.py IocpProactor bug https://bugs.python.org/issue35599 opened by jeffr(a)livedata.com #35600: Expose siphash https://bugs.python.org/issue35600 opened by Dima.Tisnek #35601: Race condition in test_signal_handling_args x86-64 High Sierra https://bugs.python.org/issue35601 opened by pablogsal #35602: cleanup code may fail in test_asyncio.test_unix_events.Selecto https://bugs.python.org/issue35602 opened by pablogsal #35603: table header in output of difflib.HtmlDiff.make_table is not e https://bugs.python.org/issue35603 opened by xtreak #35605: backported patch requires new sphinx, minimum sphinx version w https://bugs.python.org/issue35605 opened by Anthony Sottile Most recent 15 issues with no replies (15) ========================================== #35603: table header in output of difflib.HtmlDiff.make_table is not e https://bugs.python.org/issue35603 #35602: cleanup code may fail in test_asyncio.test_unix_events.Selecto https://bugs.python.org/issue35602 #35601: Race condition in test_signal_handling_args x86-64 High Sierra https://bugs.python.org/issue35601 #35599: asyncio windows_events.py IocpProactor bug https://bugs.python.org/issue35599 #35593: Register standard browser: Chrome https://bugs.python.org/issue35593 #35586: Open pyexpat compilation, Make shows error（missing separator https://bugs.python.org/issue35586 #35582: Argument Clinic: inline parsing code for functions with only p https://bugs.python.org/issue35582 #35581: Document @typing.type_check_only https://bugs.python.org/issue35581 #35577: side_effect mocked method lose reference to instance https://bugs.python.org/issue35577 #35571: Parallel Timeout Class https://bugs.python.org/issue35571 #35556: See if frozen modules can use relative imports https://bugs.python.org/issue35556 #35552: Do not read memory past the specified limit in PyUnicode_FromF https://bugs.python.org/issue35552 #35551: Encoding and alias issues https://bugs.python.org/issue35551 #35550: Some define guards for Solaris are wrong https://bugs.python.org/issue35550 #35540: dataclasses.asdict breaks with defaultdict fields https://bugs.python.org/issue35540 Most recent 15 issues waiting for review (15) ============================================= #35603: table header in output of difflib.HtmlDiff.make_table is not e https://bugs.python.org/issue35603 #35602: cleanup code may fail in test_asyncio.test_unix_events.Selecto https://bugs.python.org/issue35602 #35601: Race condition in test_signal_handling_args x86-64 High Sierra https://bugs.python.org/issue35601 #35598: IDLE: Modernize config_key module https://bugs.python.org/issue35598 #35596: Fatal Python error: initfsencoding: unable to load the file sy https://bugs.python.org/issue35596 #35588: Speed up mod/divmod/floordiv for Fraction type https://bugs.python.org/issue35588 #35582: Argument Clinic: inline parsing code for functions with only p https://bugs.python.org/issue35582 #35581: Document @typing.type_check_only https://bugs.python.org/issue35581 #35578: Add test for Argument Clinic converters https://bugs.python.org/issue35578 #35568: Expose the C raise() function in the signal module, for use on https://bugs.python.org/issue35568 #35563: Doc: warnings.rst - add links to references https://bugs.python.org/issue35563 #35560: format(float(123), "00") causes segfault in debug builds https://bugs.python.org/issue35560 #35557: Allow lowercase hexadecimal characters in base64.b16decode() https://bugs.python.org/issue35557 #35552: Do not read memory past the specified limit in PyUnicode_FromF https://bugs.python.org/issue35552 #35550: Some define guards for Solaris are wrong https://bugs.python.org/issue35550 Top 10 most discussed issues (10) ================================= #33830: Error in the output of one example in the httplib docs https://bugs.python.org/issue33830 11 msgs #35596: Fatal Python error: initfsencoding: unable to load the file sy https://bugs.python.org/issue35596 9 msgs #35588: Speed up mod/divmod/floordiv for Fraction type https://bugs.python.org/issue35588 8 msgs #35548: memoryview needlessly (?) requires represented object to be ha https://bugs.python.org/issue35548 7 msgs #35560: format(float(123), "00") causes segfault in debug builds https://bugs.python.org/issue35560 7 msgs #35485: Mac: tkinter windows turn black while resized https://bugs.python.org/issue35485 6 msgs #35563: Doc: warnings.rst - add links to references https://bugs.python.org/issue35563 5 msgs #35568: Expose the C raise() function in the signal module, for use on https://bugs.python.org/issue35568 5 msgs #35573: is_HDN is returns false positive and false negative value for https://bugs.python.org/issue35573 5 msgs #35594: Python script generating Segmentation Fault https://bugs.python.org/issue35594 5 msgs Issues closed (44) ================== #11191: test_search_cpp error on AIX (with xlc) https://bugs.python.org/issue11191 closed by ncoghlan #11192: test_socket error on AIX https://bugs.python.org/issue11192 closed by ncoghlan #21524: Allowing to pass pathlib.Path object in mimetypes.guess_type f https://bugs.python.org/issue21524 closed by cheryl.sabella #22703: Idle Code Context menu entrie(s) https://bugs.python.org/issue22703 closed by terry.reedy #23867: Argument Clinic: inline parsing code for 1-argument functions https://bugs.python.org/issue23867 closed by serhiy.storchaka #24307: [Python 2] pip error on windows whose current user name contai https://bugs.python.org/issue24307 closed by serhiy.storchaka #24390: Python 3.4.3 64 bits is not "high dpi aware" https://bugs.python.org/issue24390 closed by cheryl.sabella #27643: test_ctypes fails on AIX with xlc https://bugs.python.org/issue27643 closed by ncoghlan #29886: links between binascii.{un,}hexlify / bytes.{,to}hex https://bugs.python.org/issue29886 closed by rhettinger #30455: Generate all tokens related code and docs from Grammar/Tokens https://bugs.python.org/issue30455 closed by serhiy.storchaka #30561: sync-up gammavariate and expovariate code https://bugs.python.org/issue30561 closed by rhettinger #31440: wrong default module search path in help message https://bugs.python.org/issue31440 closed by cheryl.sabella #31503: Enhance dir(module) to be informed by __all__ by updating modu https://bugs.python.org/issue31503 closed by cheryl.sabella #32067: Deprecate accepting unrecognized braces in regular expressions https://bugs.python.org/issue32067 closed by serhiy.storchaka #32070: Clarify the behavior of the staticmethod builtin https://bugs.python.org/issue32070 closed by rhettinger #34193: Fix pluralization in TypeError messages in getargs.c https://bugs.python.org/issue34193 closed by serhiy.storchaka #34373: test_time errors on AIX https://bugs.python.org/issue34373 closed by ncoghlan #34711: Lib/http/server.py: Return HTTPStatus.NOT_FOUND if path.endswi https://bugs.python.org/issue34711 closed by ncoghlan #34764: Improve documentation example for using iter() with sentinel v https://bugs.python.org/issue34764 closed by rhettinger #34897: distutils test errors when CXX is not set https://bugs.python.org/issue34897 closed by ncoghlan #35009: argparse throws UnicodeEncodeError for printing help with unic https://bugs.python.org/issue35009 closed by xtreak #35208: IDLE: Squeezed line count ignores wrapping before newline https://bugs.python.org/issue35208 closed by taleinat #35387: Dialogs on IDLE are accompanied by a small black window https://bugs.python.org/issue35387 closed by ned.deily #35402: Upgrade macOS and Windows installers to Tcl 8.6.9 and Tk 8.6.9 https://bugs.python.org/issue35402 closed by ned.deily #35553: Test https://bugs.python.org/issue35553 closed by EWDurbin #35554: Test https://bugs.python.org/issue35554 closed by EWDurbin #35555: IDLE: Gray out Code Context on non-editor windows https://bugs.python.org/issue35555 closed by terry.reedy #35558: venv: running activate.bat gives ' parameter format not correc https://bugs.python.org/issue35558 closed by Nils-Hero #35559: Optimize base64.b16decode to use compiled regex https://bugs.python.org/issue35559 closed by xtreak #35562: Issue in sizeof() function https://bugs.python.org/issue35562 closed by ammar2 #35564: [DOC] Sphinx 2.0 will require master_doc variable set in conf. https://bugs.python.org/issue35564 closed by mdk #35565: Add detail to an assertion failure message in wsgiref https://bugs.python.org/issue35565 closed by rhettinger #35566: DOC: Add links to annotation glossary term https://bugs.python.org/issue35566 closed by rhettinger #35567: Convert membership test from dict-of-constants to a set https://bugs.python.org/issue35567 closed by rhettinger #35572: Logging module cleanup https://bugs.python.org/issue35572 closed by vinay.sajip #35574: Coconut support https://bugs.python.org/issue35574 closed by steven.daprano #35575: Improved range syntax https://bugs.python.org/issue35575 closed by rhettinger #35576: function splitextTest does not return expected value https://bugs.python.org/issue35576 closed by serhiy.storchaka #35579: Typo in in asyncio-task documentation https://bugs.python.org/issue35579 closed by asvetlov #35585: Speedup Enum lookup https://bugs.python.org/issue35585 closed by asvetlov #35587: Python 3.7.2 Embed - zipimport.ZipImportError (Cannot load pyt https://bugs.python.org/issue35587 closed by steve.dower #35591: IDLE: Traceback on Find Selection https://bugs.python.org/issue35591 closed by terry.reedy #35597: Bug in Python's compiler https://bugs.python.org/issue35597 closed by tim.peters #35604: Is python used more than Java Nowadays? https://bugs.python.org/issue35604 closed by steven.daprano

1 0

[RELEASE] Python 3.7.2 and 3.6.8 are now available
by Ned Deily Dec. 24, 2018

Dec. 24, 2018

https://blog.python.org/2018/12/python-372-and-368-are-now-available.html Python 3.7.2 and 3.6.8 are now available. Python 3.7.2 is the next maintenance release of Python 3.7, the latest feature release of Python. You can find Python 3.7.2 here: https://www.python.org/downloads/release/python-372/ See the What’s New In Python 3.7 document for more information about the many new features and optimizations included in the 3.7 series. Detailed information about the changes made in 3.7.2 can be found in its change log. We are also happy to announce the availability of Python 3.6.8: https://www.python.org/downloads/release/python-368/ Python 3.6.8 is planned to be the last bugfix release of Python 3.6. Per our support policy, we plan to provide security fixes for Python 3.6 as needed through 2021, five years following its initial release. Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. https://docs.python.org/3.7/whatsnew/3.7.html https://docs.python.org/3.7/whatsnew/changelog.html#python-3-7-2-final https://docs.python.org/3.6/whatsnew/changelog.html#python-3-6-8-final https://www.python.org/psf/ -- Ned Deily nad(a)python.org -- []

1 0

Summary of Python tracker Issues
by Python tracker Dec. 21, 2018

Dec. 21, 2018

ACTIVITY SUMMARY (2018-12-14 - 2018-12-21) 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 6896 (-13) closed 40407 (+67) total 47303 (+54) Open issues with patches: 2737 Issues opened (31) ================== #35500: Align expected and actual calls on mock.assert_called_with err https://bugs.python.org/issue35500 opened by xtreak #35501: "make coverage" should not leak coverage compiler flags to thi https://bugs.python.org/issue35501 opened by vstinner #35502: Memory leak in xml.etree.ElementTree.iterparse https://bugs.python.org/issue35502 opened by jess.j #35503: os.path.islink() works with cygwin installation but not python https://bugs.python.org/issue35503 opened by bward #35505: Test test_imaplib fail in test_imap4_host_default_value https://bugs.python.org/issue35505 opened by Petr Stupka #35507: multiprocessing: seg fault when creating RawArray from numpy c https://bugs.python.org/issue35507 opened by sh37211 #35512: patch.dict resolves in_dict eagerly (should be late resolved) https://bugs.python.org/issue35512 opened by jason.coombs #35514: Docs on reference count detail. enhancement. https://bugs.python.org/issue35514 opened by bombs-kim #35517: selector.EpollSelector: add new parameter to support EPOLLEXCL https://bugs.python.org/issue35517 opened by Manjusaka #35518: test_timeout uses blackhole.snakebite.net domain which doesn't https://bugs.python.org/issue35518 opened by vstinner #35520: Python won't build with dtrace enabled on some systems. https://bugs.python.org/issue35520 opened by kulikjak #35524: using/windows launcher image might be deprecated https://bugs.python.org/issue35524 opened by seluj78 #35525: Incorrect keyword name in NNTP.starttls() documentation https://bugs.python.org/issue35525 opened by cmcp22 #35527: Make fields selectively immutable in dataclasses https://bugs.python.org/issue35527 opened by rhettinger #35528: [DOC] [LaTeX] Sphinx 2.0 uses GNU FreeFont as default for xela https://bugs.python.org/issue35528 opened by jfbu #35530: Counter-intuitive logging API https://bugs.python.org/issue35530 opened by porton #35533: argparse standard error usage for exit / error https://bugs.python.org/issue35533 opened by philiprowlands #35534: SIGSEGV in stackdepth_walk https://bugs.python.org/issue35534 opened by gozdal #35535: time.strptime() unexpectedly gives the same result for %U and https://bugs.python.org/issue35535 opened by Paul Keating #35536: Calling built-in locals() and globals() in C++ leads to System https://bugs.python.org/issue35536 opened by Никита Сиргиенко #35537: use os.posix_spawn in subprocess https://bugs.python.org/issue35537 opened by nanjekyejoannah #35539: Cannot properly close terminated process https://bugs.python.org/issue35539 opened by hniksic #35540: dataclasses.asdict breaks with defaultdict fields https://bugs.python.org/issue35540 opened by wrmsr #35545: asyncio.base_events.create_connection doesn't handle scoped IP https://bugs.python.org/issue35545 opened by maxifree #35546: String formatting produces incorrect result with left-aligned https://bugs.python.org/issue35546 opened by serhiy.storchaka #35547: email.parser / email.policy does not correctly handle multiple https://bugs.python.org/issue35547 opened by mjpieters #35548: memoryview needlessly (?) requires represented object to be ha https://bugs.python.org/issue35548 opened by Kentzo #35549: Add partial_match: bool = False argument to unicodedata.lookup https://bugs.python.org/issue35549 opened by rominf #35550: Some define guards for Solaris are wrong https://bugs.python.org/issue35550 opened by kulikjak #35551: Encoding and alias issues https://bugs.python.org/issue35551 opened by blkserene #35552: Do not read memory past the specified limit in PyUnicode_FromF https://bugs.python.org/issue35552 opened by serhiy.storchaka Most recent 15 issues with no replies (15) ========================================== #35552: Do not read memory past the specified limit in PyUnicode_FromF https://bugs.python.org/issue35552 #35551: Encoding and alias issues https://bugs.python.org/issue35551 #35550: Some define guards for Solaris are wrong https://bugs.python.org/issue35550 #35549: Add partial_match: bool = False argument to unicodedata.lookup https://bugs.python.org/issue35549 #35548: memoryview needlessly (?) requires represented object to be ha https://bugs.python.org/issue35548 #35540: dataclasses.asdict breaks with defaultdict fields https://bugs.python.org/issue35540 #35539: Cannot properly close terminated process https://bugs.python.org/issue35539 #35533: argparse standard error usage for exit / error https://bugs.python.org/issue35533 #35528: [DOC] [LaTeX] Sphinx 2.0 uses GNU FreeFont as default for xela https://bugs.python.org/issue35528 #35525: Incorrect keyword name in NNTP.starttls() documentation https://bugs.python.org/issue35525 #35520: Python won't build with dtrace enabled on some systems. https://bugs.python.org/issue35520 #35514: Docs on reference count detail. enhancement. https://bugs.python.org/issue35514 #35512: patch.dict resolves in_dict eagerly (should be late resolved) https://bugs.python.org/issue35512 #35505: Test test_imaplib fail in test_imap4_host_default_value https://bugs.python.org/issue35505 #35501: "make coverage" should not leak coverage compiler flags to thi https://bugs.python.org/issue35501 Most recent 15 issues waiting for review (15) ============================================= #35552: Do not read memory past the specified limit in PyUnicode_FromF https://bugs.python.org/issue35552 #35550: Some define guards for Solaris are wrong https://bugs.python.org/issue35550 #35545: asyncio.base_events.create_connection doesn't handle scoped IP https://bugs.python.org/issue35545 #35520: Python won't build with dtrace enabled on some systems. https://bugs.python.org/issue35520 #35517: selector.EpollSelector: add new parameter to support EPOLLEXCL https://bugs.python.org/issue35517 #35502: Memory leak in xml.etree.ElementTree.iterparse https://bugs.python.org/issue35502 #35498: Parents objects in pathlib.Path don't support slices as __geti https://bugs.python.org/issue35498 #35494: Inaccurate error message for f-string https://bugs.python.org/issue35494 #35488: pathlib Path.match does not behave as described https://bugs.python.org/issue35488 #35479: multiprocessing.Pool.join() always takes at least 100 ms https://bugs.python.org/issue35479 #35478: multiprocessing: ApplyResult.get() hangs if the pool is termin https://bugs.python.org/issue35478 #35470: A deadly decref in _PyImport_FindExtensionObjectEx() https://bugs.python.org/issue35470 #35466: Use a linked list for the ceval pending calls. https://bugs.python.org/issue35466 #35459: Use PyDict_GetItemWithError() instead of PyDict_GetItem() https://bugs.python.org/issue35459 #35455: Solaris thread_time doesn't work with current implementation https://bugs.python.org/issue35455 Top 10 most discussed issues (10) ================================= #35517: selector.EpollSelector: add new parameter to support EPOLLEXCL https://bugs.python.org/issue35517 18 msgs #35537: use os.posix_spawn in subprocess https://bugs.python.org/issue35537 17 msgs #35530: Counter-intuitive logging API https://bugs.python.org/issue35530 9 msgs #35502: Memory leak in xml.etree.ElementTree.iterparse https://bugs.python.org/issue35502 7 msgs #35485: Mac: tkinter windows turn black while resized https://bugs.python.org/issue35485 5 msgs #35524: using/windows launcher image might be deprecated https://bugs.python.org/issue35524 5 msgs #29707: os.path.ismount() always returns false for mount --bind on sam https://bugs.python.org/issue29707 4 msgs #35518: test_timeout uses blackhole.snakebite.net domain which doesn't https://bugs.python.org/issue35518 4 msgs #35547: email.parser / email.policy does not correctly handle multiple https://bugs.python.org/issue35547 4 msgs #19974: tarfile doesn't overwrite symlink by directory https://bugs.python.org/issue19974 3 msgs Issues closed (63) ================== #10320: printf %qd is nonstandard https://bugs.python.org/issue10320 closed by serhiy.storchaka #10496: Python startup should not require passwd entry https://bugs.python.org/issue10496 closed by vstinner #16516: argparse types (and actions) must be hashable https://bugs.python.org/issue16516 closed by gvanrossum #18085: Verifying refcounts.dat https://bugs.python.org/issue18085 closed by serhiy.storchaka #18799: Resurrect and fix test_404 in Lib/test/test_xmlrpc.py https://bugs.python.org/issue18799 closed by serhiy.storchaka #20164: Undocumented KeyError from os.path.expanduser https://bugs.python.org/issue20164 closed by serhiy.storchaka #23057: [Windows] asyncio: support signal handlers on Windows (feature https://bugs.python.org/issue23057 closed by asvetlov #32077: Documentation: Some Unicode object functions don't indicate wh https://bugs.python.org/issue32077 closed by serhiy.storchaka #32706: test_check_hostname() of test_ftplib started to fail randomly https://bugs.python.org/issue32706 closed by vstinner #33306: Improving SyntaxError for unmatched parentheses https://bugs.python.org/issue33306 closed by serhiy.storchaka #34238: When BROWSER is set on Mac webbrowser.register_standard_browse https://bugs.python.org/issue34238 closed by serhiy.storchaka #34589: Py_Initialize() and Py_Main() should not enable C locale coerc https://bugs.python.org/issue34589 closed by ncoghlan #34686: Add `-r`, as opposed to `-R` to Python core interpreter https://bugs.python.org/issue34686 closed by lepaperwan #34833: [CI] Azure Pipeline: Initialize Agent failed https://bugs.python.org/issue34833 closed by vstinner #35012: [3.7] test_multiprocessing_spawn hangs randomly on AppVeyor https://bugs.python.org/issue35012 closed by vstinner #35238: Alleviate memory reservation of fork_exec in subprocess.Popen https://bugs.python.org/issue35238 closed by oesteban #35257: Avoid leaking linker flags into distutils: add PY_LDFLAGS_NODI https://bugs.python.org/issue35257 closed by ned.deily #35259: Py_FinalizeEx unconditionally exists in Py_LIMITED_API https://bugs.python.org/issue35259 closed by serhiy.storchaka #35266: Add _PyPreConfig and rework _PyCoreConfig and _PyMainInterpret https://bugs.python.org/issue35266 closed by vstinner #35268: Windows 10 asyncio reading continously stdin and stdout Stockf https://bugs.python.org/issue35268 closed by cheryl.sabella #35337: Check index in PyTuple_GET_ITEM/PyTuple_SET_ITEM in debug mode https://bugs.python.org/issue35337 closed by vstinner #35348: Problems with handling the file command output in platform.arc https://bugs.python.org/issue35348 closed by vstinner #35368: [2.7] Make PyMem_Malloc() thread-safe in debug mode https://bugs.python.org/issue35368 closed by vstinner #35394: Add __slots__ = () to asyncio protocols https://bugs.python.org/issue35394 closed by asvetlov #35412: test_future4 ran no test https://bugs.python.org/issue35412 closed by vstinner #35415: fileno argument to socket.socket is not validated https://bugs.python.org/issue35415 closed by asvetlov #35424: multiprocessing.Pool: emit ResourceWarning https://bugs.python.org/issue35424 closed by vstinner #35441: Dead (and buggy) code due to mishandling of PyList_SetItem() e https://bugs.python.org/issue35441 closed by serhiy.storchaka #35450: venv module doesn't create a copy of python binary by default https://bugs.python.org/issue35450 closed by cheryl.sabella #35461: Document C API functions which swallow exceptions https://bugs.python.org/issue35461 closed by serhiy.storchaka #35465: [asyncio] Document loop.add_signal_handler https://bugs.python.org/issue35465 closed by yselivanov #35469: [2.7] time.asctime() regression https://bugs.python.org/issue35469 closed by vstinner #35472: python 3.7.2 rc1 bumped sphinx requirements a bit too much https://bugs.python.org/issue35472 closed by mdk #35475: Docs do not show PyImport_AddModuleObject() returns a borrowed https://bugs.python.org/issue35475 closed by serhiy.storchaka #35480: argparse: add a full fledged parser as a subparser https://bugs.python.org/issue35480 closed by terry.reedy #35482: can't open python368rc1.chm and python372rc1.chm https://bugs.python.org/issue35482 closed by steve.dower #35490: Remove the DecodeFSDefault return converter in Argument Clinic https://bugs.python.org/issue35490 closed by serhiy.storchaka #35492: Missing colon on func statement in library/sys doc https://bugs.python.org/issue35492 closed by terry.reedy #35496: left-to-right violation in match order https://bugs.python.org/issue35496 closed by steve.newcomb #35497: Libary select docs enhance https://bugs.python.org/issue35497 closed by xiang.zhang #35499: "make profile-opt" overrides CFLAGS_NODIST https://bugs.python.org/issue35499 closed by vstinner #35504: `del OSError().characters_written` raises `SystemError` https://bugs.python.org/issue35504 closed by serhiy.storchaka #35506: Doc: fix keyword `as` link from `import` and `try` https://bugs.python.org/issue35506 closed by serhiy.storchaka #35508: array.index should take optional start and stop indices like f https://bugs.python.org/issue35508 closed by kyuupichan #35509: Unable to inherit from logging.Formatter https://bugs.python.org/issue35509 closed by yan12125 #35510: pickling derived dataclasses https://bugs.python.org/issue35510 closed by satra #35511: Some methods of profile.Profile are not supported but the docs https://bugs.python.org/issue35511 closed by asvetlov #35513: Lib/test/lock_tests.py should not use time.time(), but time.mo https://bugs.python.org/issue35513 closed by vstinner #35515: Matrix operator star creates a false matrix https://bugs.python.org/issue35515 closed by christian.heimes #35516: platform.system_alias(): add macOS support https://bugs.python.org/issue35516 closed by vstinner #35519: Can not run test without test module for tests which import ra https://bugs.python.org/issue35519 closed by vstinner #35521: IDLE: Add doc section for Code Context and ref links. https://bugs.python.org/issue35521 closed by terry.reedy #35522: os.stat().st_ctime and time.time() mismatch https://bugs.python.org/issue35522 closed by rbiswas143 #35523: Remove old ctypes callback workaround: creating the first inst https://bugs.python.org/issue35523 closed by vstinner #35526: __future__.barry_as_FLUFL documented as mandatory for Python 3 https://bugs.python.org/issue35526 closed by barry #35529: A reference counting bug in ctypes https://bugs.python.org/issue35529 closed by serhiy.storchaka #35531: xml.etree.ElementTree Elment.find bug, fails to find tag https://bugs.python.org/issue35531 closed by spacether #35532: numpy-stl library problem, class stl.base.BaseMesh lacks funct https://bugs.python.org/issue35532 closed by serhiy.storchaka #35538: splitext does not seems to handle filepath ending in . https://bugs.python.org/issue35538 closed by mrabarnett #35541: CLI error when .python_history contains unicode characters https://bugs.python.org/issue35541 closed by eryksun #35542: stack exhaustion in 3.6.7 https://bugs.python.org/issue35542 closed by shuoz #35543: re.sub is only replacing max. of 2 string found by regexp. https://bugs.python.org/issue35543 closed by serhiy.storchaka #35544: unicode.encode docstring says return value can be unicode https://bugs.python.org/issue35544 closed by serhiy.storchaka

1 0

Windows porting: request to review PR #880
by Jeroen Demeyer Dec. 21, 2018

Dec. 21, 2018

Can somebody please review https://github.com/python/cpython/pull/880 That addresses a severe problem on Windows making it impossible to build any C++ extension module with some compilers.

2 1