[issue31948] [EASY] Broken MSDN links in msilib docs

Mariatta Wijaya added the comment: This couldn't be backported by miss-islington, so someone needs to do it manually. -- stage: patch review -> backport needed ___ Python tracker

[issue31948] [EASY] Broken MSDN links in msilib docs

Mariatta Wijaya added the comment: New changeset 3bda0aa3783bf85fc3ff8bc042aefd9c4fd3 by Mariatta (Jesse-Bakker) in branch 'master': bpo-31948: Fix broken links in msilib docs (GH-4397)

[issue31948] [EASY] Broken MSDN links in msilib docs

Change by Roundup Robot : -- keywords: +patch pull_requests: +4345 stage: needs patch -> patch review ___ Python tracker

[issue31997] SSL lib does not handle trailing dot (period) in hostname or certificate

Christian Heimes added the comment: As I explained before, the ssl module is the wrong place to address the issue. You *must* keep SNI TLS extension, HTTP Host header, and hostname for SAN matching in sync. Python uses the server_hostname argument for both SNI and hostname

[issue31963] AMD64 Debian PGO 3.x buildbot: compilation failed with an internal compiler error in create_edge

Neil Schemenauer added the comment: I'm willing to put some time into trying to fix this, in the case that it is caused by my Makefile changes. However, it would be very helpful if I could login to the build-bot and try running with the Makefile change backed out. Is

[issue31997] SSL lib does not handle trailing dot (period) in hostname or certificate

Sam Napolitano added the comment: Sorry I wasn't able to get back to you sooner. If having a trailing dot in the cert is an RFC violation, then case 2 can be left alone. As for case 3, we can be more explicit: if hostname ends in a dot AND cert does not end in a

[issue32021] Brotli encoding is not recognized by mimetypes

R. David Murray added the comment: Hmm. OK, the docs do say that value should be usable as a content-encoding header. However, absent any sort of program that actually does brotli encoding/decoding to and from files, this would be essentially useless based on the

[issue32030] PEP 432: Rewrite Py_Main()

Change by STINNER Victor : -- title: Rewrite Py_Main() -> PEP 432: Rewrite Py_Main() ___ Python tracker ___

[issue31948] [EASY] Broken MSDN links in msilib docs

Change by Mariatta Wijaya : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue32025] Add time.thread_time()

STINNER Victor added the comment: > On other platforms, it can simply raise NotImplementedError. Would it be possible to not provide the function if it's not supported by a platform? Do you know platforms which don't support time.thread_time()? Do you want to add

[issue31948] [EASY] Broken MSDN links in msilib docs

Mariatta Wijaya added the comment: New changeset 42336def77f53861284336b3335098a1b9b8cab2 by Mariatta (Jesse-Bakker) in branch '3.6': bpo-31948: Fix broken links in msilib docs (GH-4397). (GH-4398)

[issue32030] PEP 432: Rewrite Py_Main()

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list

[issue32029] cgi: TypeError when no argument string is found

Berker Peksag added the comment: Thank you for your report. This looks like a duplicate of issue 2. You might workaround this by passing ``headers={"Content-Disposition": "inline"}`` to cgi.FieldStorage() (untested) -- nosy: +berker.peksag resolution: ->

[issue32025] Add time.thread_time()

STINNER Victor added the comment: It seems like macOS doesn't implement CLOCK_THREAD_CPUTIME_ID but provides thread_info() which can be used by suming user and system times. -- ___ Python tracker

[issue32029] cgi: TypeError

New submission from Sebastian Rittau : Consider the following code: import cgi from io import BytesIO cgi.FieldStorage(BytesIO(b"{}"), environ={ "REQUEST_METHOD": "POST", "CONTENT_TYPE": "application/json", "CONTENT_LENGTH": "14", })

[issue27777] cgi.FieldStorage can't parse simple body with Content-Length and no Content-Disposition

Change by Sebastian Rittau : -- nosy: +srittau ___ Python tracker ___ ___

[issue32030] PEP 432: Rewrite Py_Main()

Nick Coghlan added the comment: While it doesn't necessarily need to be in this patch, something else I recently realised (by breaking it *cough* [1]) is that the interaction between our command line options and our environment variables isn't really clearly defined

[issue31948] [EASY] Broken MSDN links in msilib docs

Change by Jesse Bakker : -- pull_requests: +4346 stage: backport needed -> patch review ___ Python tracker ___

[issue32029] cgi: TypeError when no argument string is found

Change by Sebastian Rittau : -- components: +Library (Lib) title: cgi: TypeError -> cgi: TypeError when no argument string is found ___ Python tracker

[issue32030] PEP 432: Rewrite Py_Main()

Change by STINNER Victor : -- nosy: +eric.snow, ncoghlan ___ Python tracker ___

[issue32030] PEP 432: Rewrite Py_Main()

STINNER Victor added the comment: I rewrote Py_Main() to prepare the code to be able to implement my "-X dev" idea: https://mail.python.org/pipermail/python-dev//2017-November/150514.html The problem is that currently the code parsing command line options and the

[issue32028] Syntactically wrong suggestions by the new custom print statement error message

Nick Coghlan added the comment: Given the symptoms (stripping 4 spaces + "pr" from the start of the line, leaving "int " behind), it looks like we're not stripping the leading whitespace when determining the text to include in the suggested print() call. To reproduce this

[issue32028] Syntactically wrong suggestions by the new custom print statement error message

Sanyam Khurana added the comment: Sure, let me have a look at it and work on fix. -- ___ Python tracker ___

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Change by Serhiy Storchaka : -- pull_requests: +4348 ___ Python tracker ___ ___

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Serhiy Storchaka added the comment: New changeset 9165f77d5f93a2c12aa0e90853e3ae7212800d3c by Serhiy Storchaka in branch 'master': bpo-32012: Disallow trailing comma after genexpr without parenthesis. (#4382)

[issue32021] Brotli encoding is not recognized by mimetypes

Andrey added the comment: NodeJS: https://www.npmjs.com/package/brotli Python: https://pypi.python.org/pypi/brotlipy https://pypi.python.org/pypi/Brotli Ubuntu: https://launchpad.net/ubuntu/+source/brotli That said I don't expect an average user to compress their files as

[issue32026] Memory leaks in Python on Windows

Nick Coghlan added the comment: I think it's reasonable to keep this open if the problems can be reproduced with the current 3.7 dev branch - while we've refactored a lot of things, we haven't specifically gone memory leak hunting for the embedded case, and I'm pretty

[issue32022] Python problem - == RESTART: Shell =====

Shimon Malachi Cohen added the comment: Not really... Did you see the "restart" ? On Nov 14, 2017 2:38 PM, "Eric V. Smith" wrote: > > Eric V. Smith added the comment: > > Can you reproduce this with a much smaller example? > >

[issue32021] Brotli encoding is not recognized by mimetypes

R. David Murray added the comment: It looks like Brotli is a de-facto standard (RFC 7932 is an informational RFC), and it says the IANA registry has been updated. However, this appears to be http-only, with no corresponding program used for compression of files, and

[issue32024] Nominal decorator function call syntax is inconsistent with regular function calls

New submission from Nick Coghlan : Function calls in decorators are implemented as regular function calls, and hence permit the use of generator expressions as their sole argument without a second pair of parentheses. However,

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Stefan Krah added the comment: I would prefer to do nothing about the subject of this issue. I still don't see any ambiguity, except in a very broad colloquial sense. Why introduce another special case? -- ___ Python tracker

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Stefan Krah added the comment: On Tue, Nov 14, 2017 at 01:31:52PM +, Nick Coghlan wrote: > If limited to the original scope, this isn't a new special case, it's fixing > a bug in the implementation of the existing special case (where it's ignoring > the trailing comma

[issue32022] Python problem - == RESTART: Shell =====

Eric V. Smith added the comment: Can you reproduce this with a much smaller example? -- nosy: +eric.smith ___ Python tracker ___

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Nick Coghlan added the comment: OK, I've filed https://bugs.python.org/issue32024 to cover the decorator syntax discrepancy. So I'd still prefer to restrict the patch for *this* issue to just the genuinely ambiguous case, and leave the

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Nick Coghlan added the comment: If limited to the original scope, this isn't a new special case, it's fixing a bug in the implementation of the existing special case (where it's ignoring the trailing comma when it shouldn't be). If it hadn't been for the scope creep to

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Stefan Krah added the comment: I think "ambiguous" is not the right word. If a single argument can be a non-parenthesized generator and all arguments can be followed by a trailing comma, it's clear. The language spec is often behind in my experience. -- nosy:

[issue32025] Add time.thread_time()

New submission from Antoine Pitrou : Currently, the time module has time.process_time(), a cross-platform function for getting per-process elapsed CPU time. Similarly, we could expose time.thread_time(), to get per-thread elapsed CPU time. On a modern POSIX platform, it can

[issue32022] Python problem - == RESTART: Shell =====

New submission from Shimon Malachi Cohen : Dear Friends, It seems that I manage to find a problem with Python ... version 3.6.3 Attached is a PY file designed to solve a puzzle: see function makeGame1 To find a solution run: doFind() >>> doFind() > counter: 11735841

[issue32022] Python problem - == RESTART: Shell =====

Shimon Malachi Cohen added the comment: lines 209 <==> 210 -- ___ Python tracker ___

[issue32021] Brotli encoding is not recognized by mimetypes

Christian Heimes added the comment: You can just add the encoding to mimetypes.encodings_map: mimetypes.encodings_map['.br'] = 'brotli' -- nosy: +christian.heimes versions: -Python 3.4, Python 3.5, Python 3.8 ___ Python tracker

[issue32015] Asyncio looping during simultaneously socket read/write and reconnection

Andrew Svetlov added the comment: New changeset e1d62e0b7cc842d6b75b4d480391f4a94e503255 by Andrew Svetlov (Andrey Egorov) in branch 'master': bpo-32015: Asyncio looping during simultaneously socket read/write an… (#4386)

[issue32015] Asyncio looping during simultaneously socket read/write and reconnection

Change by Andrew Svetlov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.5, Python 3.8 ___ Python tracker

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Henk-Jaap Wagenaar added the comment: I think this showcases how difficult it is to get this right, requires carefully reading the EBNF language spec, not just the text, and the behaviour is unexpected. -- ___ Python

[issue32021] Brotli encoding is not recognized by mimetypes

Andrey added the comment: Yes, however would it make sense to add it, so mimetypes recognizes it by default? I will make a PR if it makes sense. -- ___ Python tracker

[issue32015] Asyncio looping during simultaneously socket read/write and reconnection

Change by Andrew Svetlov : -- pull_requests: +4341 ___ Python tracker ___ ___

[issue32015] Asyncio looping during simultaneously socket read/write and reconnection

Andrew Svetlov added the comment: New changeset cc0961c517c31578f6a40a4dc7ea177d62c256b7 by Andrew Svetlov in branch '3.6': [3.6] bpo-32015: Asyncio looping during simultaneously socket read/write an… (GH-4386) (#4393)

[issue32023] Always require parentheses for genexps in base class lists

New submission from Nick Coghlan : The compiler currently allows parentheses to be omitted if a generator expression is the sole entry in a base class list: >>> class C(x for x in []): pass ... Traceback (most recent call last): File "", line 1, in

[issue16055] incorrect error text for int(base=1000, x='1')

STINNER Victor added the comment: New changeset 58cbae22930486814cc01cf9f981d9fe5e0c68f9 by Victor Stinner (Miss Islington (bot)) in branch '3.6': bpo-16055: Fixes incorrect error text for int('1', base=1000) (GH-4376) (#4389)

[issue16055] incorrect error text for int(base=1000, x='1')

STINNER Victor added the comment: Thank you Sanyam Khurana, I merged your PR and backported the fix automaticalled to Python 3.6. Can you please try to backport the fix to Python 2.7 and create a new PR? -- ___ Python

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Nick Coghlan added the comment: I created https://bugs.python.org/issue32023 to explicitly cover the base class list case, and after checking the language spec, I agree that case should be a syntax error. However, `@deco(x for x in [])` should *not* be a syntax error, as:

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Serhiy Storchaka added the comment: No, it doesn't match the "@dotted_name(arg_list)" pattern. decorator: "@" `dotted_name` ["(" [`argument_list` [","]] ")"] NEWLINE call: `primary` "(" [`argument_list` [","] | `comprehension`] ")" argument_list:

[issue32022] Python problem - == RESTART: Shell =====

Shimon Malachi Cohen added the comment: Here is another simple example - Simple? the game board ==> is small see attached PY file run ==> doFind() -- Added file: https://bugs.python.org/file47264/KAKURU.py ___ Python tracker

[issue32021] Brotli encoding is not recognized by mimetypes

R. David Murray added the comment: OK, so there are "real" filenames that have .br on the end? That wasn't clear from the RFC and discussions I found. Based on the documentation, br is for use in the Content-Encoding header. What does aiohttp do when it gets a brotli

[issue32026] Memory leaks in Python on Windows

New submission from PJ Naughter : I would like to report memory leaks in Python 3.6.3 when embedded in a C++ Windows app. I have download the Python 3.6.3 code and compiled a debug version of Python with my copy of Visual Studio 2017 Professional (have also confirmed the

[issue32021] Brotli encoding is not recognized by mimetypes

R. David Murray added the comment: Note, I'm not saying we shouldn't do this, I'd just like to get good documentation of why linked to this issue. -- ___ Python tracker

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Change by Stefan Krah : -- nosy: -skrah ___ Python tracker ___ ___ Python-bugs-list

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Change by Yury Selivanov : -- nosy: -yselivanov ___ Python tracker ___ ___

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Change by Stefan Krah : -- nosy: -skrah ___ Python tracker ___ ___ Python-bugs-list

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Stefan Krah added the comment: Yes Sir! -- nosy: +skrah ___ Python tracker ___ ___

[issue32022] Python problem - == RESTART: Shell =====

Eric V. Smith added the comment: That's too much code for me to run without analyzing it first. If I have time, I'll look at it. -- ___ Python tracker

[issue15606] re.VERBOSE whitespace behavior not completely documented

Change by Roundup Robot : -- pull_requests: +4343 ___ Python tracker ___

[issue15606] re.VERBOSE whitespace behavior not completely documented

Change by Roundup Robot : -- pull_requests: +4342 ___ Python tracker ___

[issue15606] re.VERBOSE whitespace behavior not completely documented

Serhiy Storchaka added the comment: New changeset 14c1fe682f0086ec28f24fee9bf1c85d80507ee5 by Serhiy Storchaka (Miss Islington (bot)) in branch '3.6': bpo-15606: Improve the re.VERBOSE documentation. (GH-4366) (#4394)

[issue15606] re.VERBOSE whitespace behavior not completely documented

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Serhiy Storchaka added the comment: I would prefer to fix all related cases in one issue, for having all examples in one place and having only one reference. All this cases are caused by the limitation of the parser used in CPython, and using different grammar

[issue15606] re.VERBOSE whitespace behavior not completely documented

Serhiy Storchaka added the comment: New changeset b0b44b4b3337297007f5ef87220a75df204399f8 by Serhiy Storchaka in branch 'master': bpo-15606: Improve the re.VERBOSE documentation. (#4366)

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Serhiy Storchaka added the comment: Stefan, `[1,2,3]` is an expression, but `x for x in [1,2,3]` is not. If you want to change the Python language specification, please open a topic on Python-Dev and provide the rationale. --

[issue32021] Brotli encoding is not recognized by mimetypes

Andrey added the comment: When "type, encoding = mimetypes.guess_type('file.js.br')" is used not only the "encoding" is not set to "brotli", but the type is also not recognized. Such code is used in aiohttp for example. My proposal is to add 'br' to

[issue15606] re.VERBOSE whitespace behavior not completely documented

Serhiy Storchaka added the comment: New changeset a2f1be0b5ba2bed49b7f94c026b541ff07e52518 by Serhiy Storchaka (Miss Islington (bot)) in branch '2.7': bpo-15606: Improve the re.VERBOSE documentation. (GH-4366) (#4395)

[issue31415] Add -X option to show import time

Barry A. Warsaw added the comment: I think there is nothing left to do for this issue, so I'm closing it. -- status: open -> closed ___ Python tracker

[issue31388] Provide a way to defer SIGINT handling in the current thread

Jeroen Demeyer added the comment: It's not only about ensuring that cleanup code gets run, but also about ensuring that the interrupt is actually seen. Currently, if you press CTRL-C at the "wrong" moment (during __del__), it will just get ignored. -- nosy:

[issue32026] Memory leaks in Python on Windows

Steve Dower added the comment: Not sure how much we can do about this, but you may want to try with Python 3.7. Eric and Nick have been working on streamlining startup, which includes a lot of work (thanks Eric!) to remove static variables. Don't expect a fix in

[issue29406] asyncio SSL contexts leak sockets after calling close with certain Apache servers

Andrew Svetlov added the comment: I'm picking up the issue. Will provide an updated PR soon. -- assignee: yselivanov -> asvetlov nosy: +asvetlov ___ Python tracker

[issue32027] argparse allow_abbrev option also controls short flag combinations

New submission from Jörn Hees : The allow_abbrev option (default True) currently is documented like this (https://docs.python.org/3/library/argparse.html#allow-abbrev): > Normally, when you pass an argument list to the parse_args() method of an > ArgumentParser, it

[issue29406] asyncio SSL contexts leak sockets after calling close with certain Apache servers

Andrew Svetlov added the comment: I'm skeptical about `critical` priority. The bugfix could be backported to Python 3.6 but I very not sure about the need for 3.5. It is a desirable fix but not secure. Yury Selivanov please confirm. --

[issue32024] Nominal decorator function call syntax is inconsistent with regular function calls

Guido van Rossum added the comment: The implementation is as intended and the language spec needs an update. -- ___ Python tracker

[issue32021] Brotli encoding is not recognized by mimetypes

Andrey added the comment: Currently aiohttp doesn't support Brotli. (I'm here because I would like to get that support) When it gets (as a server) a request for file.html it checks if file.html.gz exists (and accept-encoding contains 'gzip'). It then send file.html.gz to

[issue29406] asyncio SSL contexts leak sockets after calling close with certain Apache servers

Yury Selivanov added the comment: > The bugfix could be backported to Python 3.6 but I very not sure about the > need for 3.5. > It is a desirable fix but not secure. The attached script looks very innocent, and it's worrisome that it's that easy to make an asyncio SSL

[issue32027] argparse allow_abbrev option also controls short flag combinations

Change by Jörn Hees : -- keywords: +patch pull_requests: +4344 stage: -> patch review ___ Python tracker ___

[issue32026] Memory leaks in Python on Windows

PJ Naughter added the comment: OK, Thanks for the quick reply. I have just migrated my application from Python 3.3 to Python 3.6.3 and would not expect you to backport changes from the 3.7 development stream to the released stream. What I will do when I get a chance is

[issue32028] Syntactically wrong suggestions by the new custom print statement error message

New submission from Martin Drawitsch : I think I found a bug in the new print syntax suggestion introduced by https://bugs.python.org/issue30597. When the following code is executed by Python 3.6.3 inside of a .py file: def f(): print '%d' % 2 , then

[issue32012] Disallow ambiguous syntax f(x for x in [1],)

Guido van Rossum added the comment: It's a (small) mistake that we didn't make the syntax for argument lists in decorators the same as argument lists everywhere else, and that should be fixed to allow exactly what's allowed in regular calls. (That syntax is weird because we

[issue27923] PEP 467 -- Minor API improvements for binary sequences

Elias Zamaria added the comment: Can someone here merge my pull request? If not, then what else needs to be done for my change to be included in 3.7? -- ___ Python tracker

[issue32030] Rewrite Py_Main()

Change by STINNER Victor : -- keywords: +patch pull_requests: +4347 stage: -> patch review ___ Python tracker ___

[issue32030] Rewrite Py_Main()

New submission from STINNER Victor : Python has a lot of code for its initialization. It's very hard to touch this code without risking to break something. It's hard to move code since many parts of the code are interdepent. The code rely on global "Py_xxx"

[issue32024] Nominal decorator function call syntax is inconsistent with regular function calls

Change by Serhiy Storchaka : -- dependencies: +Disallow ambiguous syntax f(x for x in [1],) type: behavior -> enhancement versions: +Python 3.7 ___ Python tracker

[issue32023] Always require parentheses for genexps in base class lists

Change by Serhiy Storchaka : -- dependencies: +Disallow ambiguous syntax f(x for x in [1],) ___ Python tracker ___

[issue27923] PEP 467 -- Minor API improvements for binary sequences

Serhiy Storchaka added the comment: I don't think these changes should be merged. For bytes.zeros(N), you can use b'\0' * N. For iterbytes() methods, I think that the general function which works with any sequence that support slicing would be more useful.