From report at bugs.python.org  Tue Oct  1 00:16:48 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 01 Oct 2019 04:16:48 +0000
Subject: [issue38319] shutil.copyfile(): os.sendfile() fails with
 OverflowError on 32-bit system
In-Reply-To: <1569829071.99.0.925566441615.issue38319@roundup.psfhosted.org>
Message-ID: <1569903408.96.0.801801113573.issue38319@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16093
pull_request: https://github.com/python/cpython/pull/16506

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38319>
_______________________________________

From report at bugs.python.org  Tue Oct  1 00:21:40 2019
From: report at bugs.python.org (paul rubin)
Date: Tue, 01 Oct 2019 04:21:40 +0000
Subject: [issue38333] add type signatures to library function docs
Message-ID: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>


New submission from paul rubin <phr-pythonbugs at nightsong.com>:

It would be nice if the library reference manual had type signatures for all the stdlib functions at some point.  It might be possible to extract a lot of them automatically from typeshed and semi-automatically paste them into the doc files.  It might also be ok to do this gradually.  I can help with this but wouldn't want to take on the entire task.

----------
assignee: docs at python
components: Documentation
messages: 353634
nosy: docs at python, phr
priority: normal
severity: normal
status: open
title: add type signatures to library function docs
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Tue Oct  1 00:55:18 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 01 Oct 2019 04:55:18 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1569905718.8.0.775834127327.issue38333@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I believe there was an explicit decision not to do this.  For the time being, optional typing is still optional.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Tue Oct  1 00:55:46 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 01 Oct 2019 04:55:46 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1569905746.75.0.538174304136.issue38333@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee: docs at python -> gvanrossum
nosy: +gvanrossum

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Tue Oct  1 01:00:06 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 01 Oct 2019 05:00:06 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1569906006.63.0.929293197798.issue38333@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

Even if this not desirable for the source code, it still makes sense to add the types to the docs, at least when they are simple and compact. The proposed notation from PEP 604 ('|' for unions) might help with compactness. Many docs are unnecessarily vague about types.

----------
assignee: gvanrossum -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Tue Oct  1 01:01:12 2019
From: report at bugs.python.org (Giampaolo Rodola')
Date: Tue, 01 Oct 2019 05:01:12 +0000
Subject: [issue38319] shutil.copyfile(): os.sendfile() fails with
 OverflowError on 32-bit system
In-Reply-To: <1569829071.99.0.925566441615.issue38319@roundup.psfhosted.org>
Message-ID: <1569906072.17.0.53514203129.issue38319@roundup.psfhosted.org>


Giampaolo Rodola' <g.rodola at gmail.com> added the comment:

Looks like it worked:
https://buildbot.python.org/all/#/builders/176/builds/1383

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38319>
_______________________________________

From report at bugs.python.org  Tue Oct  1 01:01:18 2019
From: report at bugs.python.org (Giampaolo Rodola')
Date: Tue, 01 Oct 2019 05:01:18 +0000
Subject: [issue38319] shutil.copyfile(): os.sendfile() fails with
 OverflowError on 32-bit system
In-Reply-To: <1569829071.99.0.925566441615.issue38319@roundup.psfhosted.org>
Message-ID: <1569906078.71.0.894916668359.issue38319@roundup.psfhosted.org>


Change by Giampaolo Rodola' <g.rodola at gmail.com>:


----------
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38319>
_______________________________________

From report at bugs.python.org  Tue Oct  1 02:42:23 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Tue, 01 Oct 2019 06:42:23 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1569912143.0.0.669955016968.issue38333@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

> Many docs are ... vague about types.

... and I consider that a feature. At least if you do that, make an explicit decision not to introduce TypeErrors for "disagreeing with the documented signature".

For example, I'd be ok with sum being documented as taking an iterable of numbers and returning a number, but it would be a catastrophe if as a consequence of that, sum of a list of lists would stop working.

----------
nosy: +veky

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:26:19 2019
From: report at bugs.python.org (Andrei Troie)
Date: Tue, 01 Oct 2019 07:26:19 +0000
Subject: [issue38332] invalid content-transfer-encoding in encoded-word causes
 KeyError
In-Reply-To: <1569877053.41.0.568400002445.issue38332@roundup.psfhosted.org>
Message-ID: <1569914779.14.0.247969687488.issue38332@roundup.psfhosted.org>


Change by Andrei Troie <andreitroie90 at gmail.com>:


----------
keywords: +patch
pull_requests: +16094
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16503

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38332>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:37:55 2019
From: report at bugs.python.org (Neil Schemenauer)
Date: Tue, 01 Oct 2019 07:37:55 +0000
Subject: [issue33418] Memory leaks in functions
In-Reply-To: <1525370063.61.0.682650639539.issue33418@psf.upfronthosting.co.za>
Message-ID: <1569915475.31.0.771833207968.issue33418@roundup.psfhosted.org>


Change by Neil Schemenauer <nas-python at arctrix.com>:


----------
pull_requests: +16095
pull_request: https://github.com/python/cpython/pull/16502

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33418>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:43:53 2019
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 01 Oct 2019 07:43:53 +0000
Subject: [issue22377] %Z in strptime doesn't match EST and others
In-Reply-To: <1410301455.57.0.912701656833.issue22377@psf.upfronthosting.co.za>
Message-ID: <1569915833.85.0.599867867774.issue22377@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
pull_requests: +16096
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16507

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22377>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:46:08 2019
From: report at bugs.python.org (karl)
Date: Tue, 01 Oct 2019 07:46:08 +0000
Subject: [issue22377] %Z in strptime doesn't match EST and others
In-Reply-To: <1410301455.57.0.912701656833.issue22377@psf.upfronthosting.co.za>
Message-ID: <1569915968.53.0.508324877698.issue22377@roundup.psfhosted.org>


karl <karl+pythonbugs at la-grange.net> added the comment:

I created a PR following the recommendations of p-ganssle
https://github.com/python/cpython/pull/16507

----------
nosy: +karlcow

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22377>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:46:11 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Tue, 01 Oct 2019 07:46:11 +0000
Subject: [issue38326] Concerns with the last minute changes to the PEP 587 API
In-Reply-To: <1569852491.15.0.285571416668.issue38326@roundup.psfhosted.org>
Message-ID: <1569915971.64.0.598156185474.issue38326@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:

I suggest closing this and following up in BPO-38304 about a possible graceful error message during invalid embedding.

----------
priority: release blocker -> normal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38326>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:47:20 2019
From: report at bugs.python.org (Andrei Troie)
Date: Tue, 01 Oct 2019 07:47:20 +0000
Subject: [issue38332] invalid content-transfer-encoding in encoded-word causes
 KeyError
In-Reply-To: <1569877053.41.0.568400002445.issue38332@roundup.psfhosted.org>
Message-ID: <1569916040.5.0.982646977495.issue38332@roundup.psfhosted.org>


Andrei Troie <andreitroie90 at gmail.com> added the comment:

I agree with you that according to the RFC, the cte can of course only be "B" or "Q". My point is that, in my example, if you try to do that you get a KeyError propagating all the way down to email.message.get(), which I believe is incorrect. 

Consider an encoded word which is syntactically incorrect in a different way, like  if for instance it's missing the terminating '?=':

'=?UTF-8?Q?somevalue'

Currently, this case will cause _encoded_words.py to throw a ValueError on this line:

_, charset, cte, cte_string, _ = ew.split('?')

Which is then caught by _header_value_parser.get_encoded_word() and handled appropriately.

To me this is the same kind of thing. I agree that an exception should be thrown, I just don't think it should propagate all the way back to the caller of email.message.get().

On a separate note, I agree with you that perhaps _encoded_words.decode() should throw more specific exceptions instead of ValueError and KeyError but that's a separate thing. I can fix that if you prefer.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38332>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:49:41 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Tue, 01 Oct 2019 07:49:41 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1569916181.1.0.450350315102.issue38006@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:


New changeset b3612070b746f799901443b65725008bc035872b by ?ukasz Langa (Neil Schemenauer) in branch '3.8':
Restore tp_clear for function object. (#16502)
https://github.com/python/cpython/commit/b3612070b746f799901443b65725008bc035872b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:51:09 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Tue, 01 Oct 2019 07:51:09 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1569916268.99.0.989208419549.issue38006@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:

Thanks a million everyone, this is now hopefully solved. I'm leaving it open for Neil to experiment with his unit test (which would be amazing to have!).

----------
priority: release blocker -> normal
versions:  -Python 2.7, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:52:28 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Tue, 01 Oct 2019 07:52:28 +0000
Subject: [issue38304] PEP 587 implementation is not ABI forward compatible
In-Reply-To: <1569630765.03.0.323163871576.issue38304@roundup.psfhosted.org>
Message-ID: <1569916348.87.0.938493956738.issue38304@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:

Will you forward port your change to master, Victor?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38304>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:55:07 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Tue, 01 Oct 2019 07:55:07 +0000
Subject: [issue38319] shutil.copyfile(): os.sendfile() fails with
 OverflowError on 32-bit system
In-Reply-To: <1569829071.99.0.925566441615.issue38319@roundup.psfhosted.org>
Message-ID: <1569916507.12.0.937070940612.issue38319@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:


New changeset 938c00ca9e4207a2531041edff2e82490b02047f by ?ukasz Langa (Miss Islington (bot)) in branch '3.8':
bpo-38319: Fix shutil._fastcopy_sendfile(): set sendfile() max block size (GH-16491) (#16506)
https://github.com/python/cpython/commit/938c00ca9e4207a2531041edff2e82490b02047f


----------
nosy: +lukasz.langa

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38319>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:59:20 2019
From: report at bugs.python.org (=?utf-8?q?Ricardo_B=C3=A1nffy?=)
Date: Tue, 01 Oct 2019 07:59:20 +0000
Subject: [issue38294] Documentation on 3.6->3.7 re.escape no longer escaping
 "/" or ":" should be obvious
In-Reply-To: <1569603997.59.0.0237297108404.issue38294@roundup.psfhosted.org>
Message-ID: <1569916760.85.0.77544200194.issue38294@roundup.psfhosted.org>


Change by Ricardo B?nffy <rbanffy at gmail.com>:


----------
title: re.escape no longer escapes "/" or ":" -> Documentation on 3.6->3.7 re.escape no longer escaping "/" or ":" should be obvious

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38294>
_______________________________________

From report at bugs.python.org  Tue Oct  1 03:59:39 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Tue, 01 Oct 2019 07:59:39 +0000
Subject: [issue38242] Revert the new asyncio Streams API
In-Reply-To: <1569020325.08.0.390897413838.issue38242@roundup.psfhosted.org>
Message-ID: <1569916779.92.0.983602243547.issue38242@roundup.psfhosted.org>


Change by ?ukasz Langa <lukasz at langa.pl>:


----------
priority: release blocker -> normal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38242>
_______________________________________

From report at bugs.python.org  Tue Oct  1 04:17:22 2019
From: report at bugs.python.org (Daniel Hillier)
Date: Tue, 01 Oct 2019 08:17:22 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
Message-ID: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>


New submission from Daniel Hillier <daniel.hillier at gmail.com>:

Seeking back beyond the decrypted / unzipped buffer doesn't reset the decrypter's crc key values. All data read after seeking back beyond the buffer is garbled.

----------
components: Library (Lib)
messages: 353646
nosy: dhillier
priority: normal
severity: normal
status: open
title: zipfile: Seeking encrypted file breaks after seeking backwards
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Tue Oct  1 04:22:25 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 08:22:25 +0000
Subject: [issue38321] Compiler warnings when building Python 3.8
In-Reply-To: <1569838124.87.0.490940014864.issue38321@roundup.psfhosted.org>
Message-ID: <1569918145.33.0.100789632925.issue38321@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> d:\dev\cpython\modules\expat\xmltok.c

This file is copied directly from https://github.com/libexpat/libexpat/ project. Would you mind to propose your patch there?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38321>
_______________________________________

From report at bugs.python.org  Tue Oct  1 04:26:27 2019
From: report at bugs.python.org (Antoine Pietri)
Date: Tue, 01 Oct 2019 08:26:27 +0000
Subject: [issue38306] High level API for loop.run_in_executor(None, ...)?
In-Reply-To: <1569681785.01.0.799144749415.issue38306@roundup.psfhosted.org>
Message-ID: <1569918387.1.0.0130524081601.issue38306@roundup.psfhosted.org>


Antoine Pietri <antoine.pietri1 at gmail.com> added the comment:

> run_in_executor doesn't necessarily create a new thread each time so create_thread would be misleading. run_in_thread might be better.

Right, the idea was to have an analogy with create_task, because the run_in_executor would be wrapped in a Task. I'm okay with run_thread() too.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38306>
_______________________________________

From report at bugs.python.org  Tue Oct  1 04:28:10 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 08:28:10 +0000
Subject: [issue38326] Concerns with the last minute changes to the PEP 587 API
In-Reply-To: <1569852491.15.0.285571416668.issue38326@roundup.psfhosted.org>
Message-ID: <1569918490.48.0.700132161239.issue38326@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Nick merged my two PRS, so the initial concern is gone :-) I close the issue. Thanks for the feedback, it was an interesting talk. Sorry for the bad timing. I dislike working under pressure of a deadline :-(

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38326>
_______________________________________

From report at bugs.python.org  Tue Oct  1 04:28:24 2019
From: report at bugs.python.org (Ma Lin)
Date: Tue, 01 Oct 2019 08:28:24 +0000
Subject: [issue38321] Compiler warnings when building Python 3.8
In-Reply-To: <1569838124.87.0.490940014864.issue38321@roundup.psfhosted.org>
Message-ID: <1569918504.72.0.62677816137.issue38321@roundup.psfhosted.org>


Ma Lin <malincns at 163.com> added the comment:

> This file is copied directly from https://github.com/libexpat/libexpat/ > project. Would you mind to propose your patch there?

ok, I will report to there.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38321>
_______________________________________

From report at bugs.python.org  Tue Oct  1 04:30:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 08:30:00 +0000
Subject: [issue38304] PEP 587 implementation is not ABI forward compatible
In-Reply-To: <1569630765.03.0.323163871576.issue38304@roundup.psfhosted.org>
Message-ID: <1569918600.7.0.185207532938.issue38304@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16098
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/16508

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38304>
_______________________________________

From report at bugs.python.org  Tue Oct  1 04:31:22 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 08:31:22 +0000
Subject: [issue38304] PEP 587 implementation is not ABI forward compatible
In-Reply-To: <1569630765.03.0.323163871576.issue38304@roundup.psfhosted.org>
Message-ID: <1569918682.13.0.54110464011.issue38304@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Will you forward port your change to master, Victor?

Sure, it was my plan: PR 16508. I chose to fix 3.8 first to unblock the 3.8.0rc1 release.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38304>
_______________________________________

From report at bugs.python.org  Tue Oct  1 04:56:41 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 08:56:41 +0000
Subject: [issue38304] PEP 587 implementation is not ABI forward compatible
In-Reply-To: <1569630765.03.0.323163871576.issue38304@roundup.psfhosted.org>
Message-ID: <1569920201.45.0.765947132029.issue38304@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 3c30a76f3d3c0dcc1fb4de097fa4a3a4c92c0b0b by Victor Stinner in branch 'master':
bpo-38304: Remove PyConfig.struct_size (GH-16500) (GH-16508)
https://github.com/python/cpython/commit/3c30a76f3d3c0dcc1fb4de097fa4a3a4c92c0b0b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38304>
_______________________________________

From report at bugs.python.org  Tue Oct  1 05:03:08 2019
From: report at bugs.python.org (Dominic Littlewood)
Date: Tue, 01 Oct 2019 09:03:08 +0000
Subject: [issue38297] Imports at top of module is often not used
In-Reply-To: <1569608194.16.0.811329598218.issue38297@roundup.psfhosted.org>
Message-ID: <1569920588.67.0.674204917104.issue38297@roundup.psfhosted.org>


Dominic Littlewood <11dlittlewood at gmail.com> added the comment:

With all due respect, I disagree with what you're saying here.

"It's a bit misleading to use the stdlib as a guideline"
... when looking at the style guide for the stdlib? I appreciate that PEP 8 is used for other purposes, but its main purpose is clear from its very first line.

"There are reasons we do this in certain spots"
Yes, there are. And given that there are so many of these different spots where it would give better performance to ignore the rule, PEP 8 should reflect that.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38297>
_______________________________________

From report at bugs.python.org  Tue Oct  1 05:11:22 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 09:11:22 +0000
Subject: [issue38304] PEP 587 implementation is not ABI forward compatible
In-Reply-To: <1569630765.03.0.323163871576.issue38304@roundup.psfhosted.org>
Message-ID: <1569921082.38.0.580774020176.issue38304@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16099
pull_request: https://github.com/python/cpython/pull/16509

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38304>
_______________________________________

From report at bugs.python.org  Tue Oct  1 05:16:22 2019
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 01 Oct 2019 09:16:22 +0000
Subject: [issue38297] Imports at top of module is often not used
In-Reply-To: <1569608194.16.0.811329598218.issue38297@roundup.psfhosted.org>
Message-ID: <1569921382.76.0.795105560819.issue38297@roundup.psfhosted.org>


Christian Heimes <lists at cheimes.de> added the comment:

A considerable amount of code is a lot older than PEP 8, some even over a decade older. Even newer code in the stdlib does not conform to PEP 8 for multiple reasons, e.g. external modules was incorporated into the stdlib.

PEP 8 sections "Introduction" and "A Foolish Consistency is the Hobgoblin of Little Minds" explain why parts stdlib do not follow PEP 8.

----------
nosy: +christian.heimes

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38297>
_______________________________________

From report at bugs.python.org  Tue Oct  1 05:22:30 2019
From: report at bugs.python.org (Matteo Dell'Amico)
Date: Tue, 01 Oct 2019 09:22:30 +0000
Subject: [issue38200] Adding itertools.pairwise to the standard library?
In-Reply-To: <1568736008.51.0.85414927582.issue38200@roundup.psfhosted.org>
Message-ID: <1569921750.08.0.872872683154.issue38200@roundup.psfhosted.org>


Matteo Dell'Amico <della at linux.it> added the comment:

Sorry for taking so long to answer, I didn't see notifications somehow.

Raymond, my use case is in general something that happens when I'm doing analytics on sequences of events (e.g., URLs visited by a browser) or paths in a graph. I look at pairs and do something based on the pair of events (e.g., did the user likely clicked an advertising link? did they go to a potentially risky webpage, possibly by clicking a link?)

I see the argument for generalizing to a sliding window, although that may lead people to choosing inefficient algorithms for sliding average or median.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38200>
_______________________________________

From report at bugs.python.org  Tue Oct  1 05:53:30 2019
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 01 Oct 2019 09:53:30 +0000
Subject: [issue38270] Tests: Avoid MD5 or check for MD5 availablity
In-Reply-To: <1569406198.76.0.145895264341.issue38270@roundup.psfhosted.org>
Message-ID: <1569923610.06.0.242148466382.issue38270@roundup.psfhosted.org>


Change by Christian Heimes <lists at cheimes.de>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38270>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:06:19 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:06:19 +0000
Subject: [issue38304] PEP 587 implementation is not ABI forward compatible
In-Reply-To: <1569630765.03.0.323163871576.issue38304@roundup.psfhosted.org>
Message-ID: <1569924379.75.0.72466411036.issue38304@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 8462a4936b3a551dc546a6adea04a70b0a07ca67 by Victor Stinner in branch 'master':
bpo-38304: PyConfig_InitPythonConfig() cannot fail anymore (GH-16509)
https://github.com/python/cpython/commit/8462a4936b3a551dc546a6adea04a70b0a07ca67


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38304>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:06:35 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 01 Oct 2019 10:06:35 +0000
Subject: [issue38304] PEP 587 implementation is not ABI forward compatible
In-Reply-To: <1569630765.03.0.323163871576.issue38304@roundup.psfhosted.org>
Message-ID: <1569924395.22.0.860413153076.issue38304@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16100
pull_request: https://github.com/python/cpython/pull/16510

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38304>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:09:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:09:30 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1569924570.51.0.107104928901.issue36670@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16101
pull_request: https://github.com/python/cpython/pull/16511

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:20:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:20:59 +0000
Subject: [issue38321] Compiler warnings when building Python 3.8
In-Reply-To: <1569838124.87.0.490940014864.issue38321@roundup.psfhosted.org>
Message-ID: <1569925259.11.0.635813343666.issue38321@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16102
pull_request: https://github.com/python/cpython/pull/16512

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38321>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:26:07 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 01 Oct 2019 10:26:07 +0000
Subject: [issue38304] PEP 587 implementation is not ABI forward compatible
In-Reply-To: <1569630765.03.0.323163871576.issue38304@roundup.psfhosted.org>
Message-ID: <1569925567.48.0.784630395252.issue38304@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset d49f096cc41f57155efe71cd089c29b38c218488 by Miss Islington (bot) in branch '3.8':
bpo-38304: PyConfig_InitPythonConfig() cannot fail anymore (GH-16509)
https://github.com/python/cpython/commit/d49f096cc41f57155efe71cd089c29b38c218488


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38304>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:27:28 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:27:28 +0000
Subject: [issue38304] PEP 587 implementation is not ABI forward compatible
In-Reply-To: <1569630765.03.0.323163871576.issue38304@roundup.psfhosted.org>
Message-ID: <1569925648.41.0.0321917364169.issue38304@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It was decided to abandon the idea of stable ABI for PyConfig: see bpo-38326. I now close this issue.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38304>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:28:14 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:28:14 +0000
Subject: [issue38205] Py_UNREACHABLE() no longer behaves as a function call
In-Reply-To: <1568758355.81.0.764131668398.issue38205@roundup.psfhosted.org>
Message-ID: <1569925694.97.0.254708537512.issue38205@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The initial issue has been fixed in 3.8 and master. I close the issue.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38205>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:29:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:29:39 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1569925779.36.0.741263568911.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 982bfa4da07b2e5749a0f4e68f99e972bcc3a549 by Victor Stinner in branch 'master':
bpo-36670: Multiple regrtest bugfixes (GH-16511)
https://github.com/python/cpython/commit/982bfa4da07b2e5749a0f4e68f99e972bcc3a549


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:29:47 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 01 Oct 2019 10:29:47 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1569925787.68.0.0643292072308.issue36670@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16103
pull_request: https://github.com/python/cpython/pull/16513

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:30:23 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:30:23 +0000
Subject: [issue38190] regrtest: test suite completes but Tests Result is not
 displayed and the process hangs
In-Reply-To: <1568662315.14.0.520273367874.issue38190@roundup.psfhosted.org>
Message-ID: <1569925823.18.0.678679946039.issue38190@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I pushed different regrtest bugfixes. The situation should now be less worse. I close the issue.

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38190>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:33:10 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:33:10 +0000
Subject: [issue37507] multiprocessing: Add a stop() method to ForkServer
In-Reply-To: <1562336538.11.0.898279442139.issue37507@roundup.psfhosted.org>
Message-ID: <1569925990.14.0.7438088258.issue37507@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

_test_multiprocessing.py calls:

        # Stop the ForkServer process if it's running
        from multiprocessing import forkserver
        forkserver._forkserver._stop()

It seems like multiprocessing tests are the main consumer of this method. So let's keep it private for now.

----------
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37507>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:40:38 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 01 Oct 2019 10:40:38 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1569926438.5.0.289297297311.issue36670@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16104
pull_request: https://github.com/python/cpython/pull/16514

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:45:17 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:45:17 +0000
Subject: [issue37474] Should Py_Initialize() control the floating point mode?
In-Reply-To: <1562002743.95.0.49076601863.issue37474@roundup.psfhosted.org>
Message-ID: <1569926717.86.0.615228131552.issue37474@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16105
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16515

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37474>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:45:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:45:55 +0000
Subject: [issue38321] Compiler warnings when building Python 3.8
In-Reply-To: <1569838124.87.0.490940014864.issue38321@roundup.psfhosted.org>
Message-ID: <1569926755.47.0.245087949414.issue38321@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 2f90261280e36a179831d72ce794115be31c88bb by Victor Stinner in branch 'master':
bpo-38321: Fix compiler warning in _randommodule.c (GH-16512)
https://github.com/python/cpython/commit/2f90261280e36a179831d72ce794115be31c88bb


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38321>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:47:55 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 01 Oct 2019 10:47:55 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1569926875.14.0.558492108677.issue36670@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 6b4c70abcaa348c84a2c1bb6f5a46596cf358e36 by Miss Islington (bot) in branch '3.8':
bpo-36670: Multiple regrtest bugfixes (GH-16511)
https://github.com/python/cpython/commit/6b4c70abcaa348c84a2c1bb6f5a46596cf358e36


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:48:44 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:48:44 +0000
Subject: [issue37245] Azure Pipeline 3.8 CI: multiple tests hung and timed out
 on macOS 10.13
In-Reply-To: <1560340622.3.0.842050597369.issue37245@roundup.psfhosted.org>
Message-ID: <1569926924.93.0.359010763168.issue37245@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It seems like macOS job pass again on Azure Pipelines. I close the issue.

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37245>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:50:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:50:13 +0000
Subject: [issue37146] opcode cache for LOAD_GLOBAL emits false alarm in memory
 leak hunting
In-Reply-To: <1559594083.93.0.475089830437.issue37146@roundup.psfhosted.org>
Message-ID: <1569927013.48.0.293589682811.issue37146@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It seems like nobody came up with a solution for the debug mode since June. I close the issue. Reopen it if you would like to propose a solution.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37146>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:56:16 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:56:16 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1569927376.84.0.973360919639.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Thanks Lorenz Mende for the nice bug report, investigating the issue and proposing fix. I wrote a PR based on your work with some minor changes. I included it in a large regrtest change to fix other bugs.

regrtest should work again with locales other than English.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:58:04 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:58:04 +0000
Subject: [issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py
In-Reply-To: <1569032250.18.0.545337961077.issue38243@roundup.psfhosted.org>
Message-ID: <1569927484.08.0.824304034772.issue38243@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 8eb64155ff26823542ccf0225b3d57b6ae36ea89 by Victor Stinner (Dong-hee Na) in branch '2.7':
[2.7] bpo-38243: Escape the server title of DocXMLRPCServer (GH-16447)
https://github.com/python/cpython/commit/8eb64155ff26823542ccf0225b3d57b6ae36ea89


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38243>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:58:56 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 01 Oct 2019 10:58:56 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1569927536.2.0.0142502599123.issue36670@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset d6a92b55944bf1ef4992e4375f02a7132717bf53 by Miss Islington (bot) in branch '3.7':
bpo-36670: Multiple regrtest bugfixes (GH-16511)
https://github.com/python/cpython/commit/d6a92b55944bf1ef4992e4375f02a7132717bf53


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Tue Oct  1 06:59:41 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 10:59:41 +0000
Subject: [issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py
In-Reply-To: <1569032250.18.0.545337961077.issue38243@roundup.psfhosted.org>
Message-ID: <1569927581.17.0.665081231442.issue38243@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16106
pull_request: https://github.com/python/cpython/pull/16516

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38243>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:01:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:01:42 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1569927702.09.0.296537916024.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> We could avoid typeperf command by accessing directly performance counters: (...)

Honestly, it sounds very complicated. I don't think that it's worth it. With Lorenz's fix, regrtest now "just works". So I think that it's good enough.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:09:51 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:09:51 +0000
Subject: [issue37802] micro-optimization of PyLong_FromSize_t()
In-Reply-To: <1565357260.71.0.37857302813.issue37802@roundup.psfhosted.org>
Message-ID: <1569928191.21.0.566152488689.issue37802@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16107
pull_request: https://github.com/python/cpython/pull/16517

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37802>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:09:51 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:09:51 +0000
Subject: [issue38321] Compiler warnings when building Python 3.8
In-Reply-To: <1569838124.87.0.490940014864.issue38321@roundup.psfhosted.org>
Message-ID: <1569928191.31.0.669379657429.issue38321@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16108
pull_request: https://github.com/python/cpython/pull/16517

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38321>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:12:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:12:32 +0000
Subject: [issue37474] Should Py_Initialize() control the floating point mode?
In-Reply-To: <1562002743.95.0.49076601863.issue37474@roundup.psfhosted.org>
Message-ID: <1569928352.08.0.877426088631.issue37474@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 5e0ea7540f577c9684e272000fdfc80d29bb78a2 by Victor Stinner in branch 'master':
bpo-37474: Don't call fedisableexcept() on FreeBSD (GH-16515)
https://github.com/python/cpython/commit/5e0ea7540f577c9684e272000fdfc80d29bb78a2


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37474>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:14:10 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:14:10 +0000
Subject: [issue37474] Should Py_Initialize() control the floating point mode?
In-Reply-To: <1562002743.95.0.49076601863.issue37474@roundup.psfhosted.org>
Message-ID: <1569928450.84.0.635900697582.issue37474@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Sorry, I failed to find time to convert attached tests to tests in the Python test suite. But I understood that existing tests should be enough to control the rounding mode.

I removed the call. If something goes wrong, we can add it back.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37474>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:27:09 2019
From: report at bugs.python.org (Krishna Oza)
Date: Tue, 01 Oct 2019 11:27:09 +0000
Subject: [issue38331] Exec not recognizing global variables inside function
In-Reply-To: <1569875978.41.0.850227388561.issue38331@roundup.psfhosted.org>
Message-ID: <1569929229.23.0.4039025182.issue38331@roundup.psfhosted.org>


Krishna Oza <krishoza15sep at gmail.com> added the comment:

adding self to nosy list.

----------
nosy: +Krishna Oza

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38331>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:28:39 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Tue, 01 Oct 2019 11:28:39 +0000
Subject: [issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py
In-Reply-To: <1569032250.18.0.545337961077.issue38243@roundup.psfhosted.org>
Message-ID: <1569929319.16.0.418304954403.issue38243@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38243>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:29:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:29:56 +0000
Subject: [issue38321] Compiler warnings when building Python 3.8
In-Reply-To: <1569838124.87.0.490940014864.issue38321@roundup.psfhosted.org>
Message-ID: <1569929396.23.0.272438865162.issue38321@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 6314abcc08f5d0f3d3a915dc9455ea223fa65517 by Victor Stinner in branch 'master':
bpo-37802: Fix a compiler warning in longobject.c (GH-16517)
https://github.com/python/cpython/commit/6314abcc08f5d0f3d3a915dc9455ea223fa65517


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38321>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:29:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:29:56 +0000
Subject: [issue37802] micro-optimization of PyLong_FromSize_t()
In-Reply-To: <1565357260.71.0.37857302813.issue37802@roundup.psfhosted.org>
Message-ID: <1569929396.29.0.744470488001.issue37802@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 6314abcc08f5d0f3d3a915dc9455ea223fa65517 by Victor Stinner in branch 'master':
bpo-37802: Fix a compiler warning in longobject.c (GH-16517)
https://github.com/python/cpython/commit/6314abcc08f5d0f3d3a915dc9455ea223fa65517


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37802>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:32:48 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:32:48 +0000
Subject: [issue38321] Compiler warnings when building Python 3.8
In-Reply-To: <1569838124.87.0.490940014864.issue38321@roundup.psfhosted.org>
Message-ID: <1569929568.82.0.940973052816.issue38321@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16109
pull_request: https://github.com/python/cpython/pull/16518

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38321>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:43:43 2019
From: report at bugs.python.org (Sanjay)
Date: Tue, 01 Oct 2019 11:43:43 +0000
Subject: [issue38335] simplify overlaps function in ipaddress.py
Message-ID: <1569930223.76.0.865877463422.issue38335@roundup.psfhosted.org>


New submission from Sanjay <sanjay537 at gmail.com>:

the current implementation of overlaps function tests either network or broadcast address is in other but
we can skip checking broadcast address is in other because we anyway check if other.network_address in self 

without loss of generality if we assume self has smaller prefixlen than other then when self.broadcast_address in other then other.network_address *SHOULD* be in self but the reverse is not true

so my first patch was to make the function logic simply do
`self.network_address in other or other.network_address in self`

but the current PR does a different change. We have introduced two new functions subnet_of and supernet_of

for two networks A, B there are only three possibilities 
1. they don't overlap
2. A is subnet of B
3. B is subnet of A

so we can reuse the existing function and just do
`return self.subnet_of(other) or self.supernet_of(other)`
the only thing is while overlaps() function returns false when we try to compare with a network or with diff version the other throws exception so I added a typecheck in the beginning.

P.S the docstring is slightly convoluted for newcomers, based on the three possibilities it should say "Tell if self is supernet or subnet of other" because "partly contained" can also mean two ranges intersect which can never happen to network prefixes. I have not made that change but can make it.

There are also some other issues I want to address but I want to do one at a time.

----------
components: Library (Lib)
files: skip_broadcast_in.patch
keywords: patch
messages: 353676
nosy: Sanjay
priority: normal
severity: normal
status: open
title: simplify overlaps function in ipaddress.py
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9
Added file: https://bugs.python.org/file48634/skip_broadcast_in.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38335>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:45:26 2019
From: report at bugs.python.org (Sanjay)
Date: Tue, 01 Oct 2019 11:45:26 +0000
Subject: [issue38335] simplify overlaps function in ipaddress.py
In-Reply-To: <1569930223.76.0.865877463422.issue38335@roundup.psfhosted.org>
Message-ID: <1569930326.32.0.891740945099.issue38335@roundup.psfhosted.org>


Change by Sanjay <sanjay537 at gmail.com>:


----------
pull_requests: +16110
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16519

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38335>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:50:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:50:02 +0000
Subject: [issue3832] add force_shared Library option to create shared lib even
 with use_stub=False
In-Reply-To: <1221100214.51.0.623800325069.issue3832@psf.upfronthosting.co.za>
Message-ID: <1569930602.14.0.330203352452.issue3832@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16111
pull_request: https://github.com/python/cpython/pull/16518

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue3832>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:51:17 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:51:17 +0000
Subject: [issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py
In-Reply-To: <1569032250.18.0.545337961077.issue38243@roundup.psfhosted.org>
Message-ID: <1569930677.33.0.230185451528.issue38243@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I prefer to keep it open until the 3.5 backport is merged.

----------
resolution: fixed -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38243>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:52:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:52:03 +0000
Subject: [issue3832] add force_shared Library option to create shared lib even
 with use_stub=False
In-Reply-To: <1221100214.51.0.623800325069.issue3832@psf.upfronthosting.co.za>
Message-ID: <1569930723.79.0.214019169711.issue3832@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset bfe1f74e39d0049a829962050e86a6a2d2a2781e by Victor Stinner in branch '3.8':
[3.8] bpo-3832: Fix compiler warnings (GH-16518)
https://github.com/python/cpython/commit/bfe1f74e39d0049a829962050e86a6a2d2a2781e


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue3832>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:52:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:52:03 +0000
Subject: [issue22273] abort when passing certain structs by value using ctypes
In-Reply-To: <1408988002.99.0.886549500758.issue22273@psf.upfronthosting.co.za>
Message-ID: <1569930723.58.0.371051240161.issue22273@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset bfe1f74e39d0049a829962050e86a6a2d2a2781e by Victor Stinner in branch '3.8':
[3.8] bpo-3832: Fix compiler warnings (GH-16518)
https://github.com/python/cpython/commit/bfe1f74e39d0049a829962050e86a6a2d2a2781e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22273>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:52:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:52:03 +0000
Subject: [issue38321] Compiler warnings when building Python 3.8
In-Reply-To: <1569838124.87.0.490940014864.issue38321@roundup.psfhosted.org>
Message-ID: <1569930723.72.0.257967922986.issue38321@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset bfe1f74e39d0049a829962050e86a6a2d2a2781e by Victor Stinner in branch '3.8':
[3.8] bpo-3832: Fix compiler warnings (GH-16518)
https://github.com/python/cpython/commit/bfe1f74e39d0049a829962050e86a6a2d2a2781e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38321>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:52:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:52:03 +0000
Subject: [issue38248] inconsistency in asyncio.Task between cancellation while
 running vs. cancellation immediately after it finishes
In-Reply-To: <1569141924.07.0.413373545347.issue38248@roundup.psfhosted.org>
Message-ID: <1569930723.49.0.428281658687.issue38248@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset bfe1f74e39d0049a829962050e86a6a2d2a2781e by Victor Stinner in branch '3.8':
[3.8] bpo-3832: Fix compiler warnings (GH-16518)
https://github.com/python/cpython/commit/bfe1f74e39d0049a829962050e86a6a2d2a2781e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38248>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:54:21 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:54:21 +0000
Subject: [issue3832] add force_shared Library option to create shared lib even
 with use_stub=False
In-Reply-To: <1221100214.51.0.623800325069.issue3832@psf.upfronthosting.co.za>
Message-ID: <1569930861.65.0.13454206187.issue3832@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Oops, the previous comment should be for bpo-38321.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue3832>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:54:45 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:54:45 +0000
Subject: [issue38321] Compiler warnings when building Python 3.8
In-Reply-To: <1569838124.87.0.490940014864.issue38321@roundup.psfhosted.org>
Message-ID: <1569930885.21.0.199220735345.issue38321@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

New changeset bfe1f74e39d0049a829962050e86a6a2d2a2781e by Victor Stinner in branch '3.8':
[3.8] bpo-3832: Fix compiler warnings (GH-16518)
https://github.com/python/cpython/commit/bfe1f74e39d0049a829962050e86a6a2d2a2781e

(oops, I made a typo in the bpo number in the commit title.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38321>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:55:21 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:55:21 +0000
Subject: [issue38321] Compiler warnings when building Python 3.8
In-Reply-To: <1569838124.87.0.490940014864.issue38321@roundup.psfhosted.org>
Message-ID: <1569930921.31.0.3134155889.issue38321@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Ok, most warnings have been fixed in 3.8 and master. I close the issue.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38321>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:56:31 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Tue, 01 Oct 2019 11:56:31 +0000
Subject: [issue38336] Remove the __set__ method restriction on data
 descriptors for attribute lookup precedence
Message-ID: <1569930991.59.0.212656372364.issue38336@roundup.psfhosted.org>


New submission from G?ry <gery.ogam at gmail.com>:

The [language documentation](https://docs.python.org/3/reference/datamodel.html#invoking-descriptors) states:

> Data descriptors with __set__() and __get__() defined always override a redefinition in an instance dictionary. In contrast, non-data descriptors can be overridden by instances.

This override is not limited to data descriptors defining `__set__()` (and `__get__()`). It is also true for data descriptors defining `__delete__()` (and `__get__()`) and data descriptors defining both `__set__()` and `__delete__()` (and `__get__()`).

In other words, _any_ data descriptors (objects defining either `__set__()` or `__delete__()` or both) defining `__get__()` override an attribute redefinition in an instance dictionary.

----------
assignee: docs at python
components: Documentation
messages: 353685
nosy: docs at python, maggyero
priority: normal
severity: normal
status: open
title: Remove the __set__ method restriction on data descriptors for attribute lookup precedence
type: enhancement
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38336>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:56:33 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 11:56:33 +0000
Subject: [issue38248] inconsistency in asyncio.Task between cancellation while
 running vs. cancellation immediately after it finishes
In-Reply-To: <1569141924.07.0.413373545347.issue38248@roundup.psfhosted.org>
Message-ID: <1569930993.64.0.636070358387.issue38248@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Can this issue be closed now?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38248>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:57:03 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Tue, 01 Oct 2019 11:57:03 +0000
Subject: [issue38336] Remove the __set__ method restriction on data
 descriptors for attribute lookup precedence
In-Reply-To: <1569930991.59.0.212656372364.issue38336@roundup.psfhosted.org>
Message-ID: <1569931023.13.0.160076223279.issue38336@roundup.psfhosted.org>


Change by G?ry <gery.ogam at gmail.com>:


----------
keywords: +patch
pull_requests: +16112
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16520

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38336>
_______________________________________

From report at bugs.python.org  Tue Oct  1 07:58:11 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Tue, 01 Oct 2019 11:58:11 +0000
Subject: [issue38336] Remove the __set__ method restriction on data
 descriptors for attribute lookup precedence
In-Reply-To: <1569930991.59.0.212656372364.issue38336@roundup.psfhosted.org>
Message-ID: <1569931091.38.0.746062223849.issue38336@roundup.psfhosted.org>


G?ry <gery.ogam at gmail.com> added the comment:

I have opened a PR here: https://github.com/python/cpython/pull/16520

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38336>
_______________________________________

From report at bugs.python.org  Tue Oct  1 08:00:44 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Tue, 01 Oct 2019 12:00:44 +0000
Subject: [issue38336] Remove the __set__ method restriction on data
 descriptors for attribute lookup precedence
In-Reply-To: <1569930991.59.0.212656372364.issue38336@roundup.psfhosted.org>
Message-ID: <1569931244.42.0.671682756924.issue38336@roundup.psfhosted.org>


Change by G?ry <gery.ogam at gmail.com>:


----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38336>
_______________________________________

From report at bugs.python.org  Tue Oct  1 08:01:59 2019
From: report at bugs.python.org (Jonas Drotleff)
Date: Tue, 01 Oct 2019 12:01:59 +0000
Subject: [issue38337] inspect: getmembers calls properties
Message-ID: <1569931319.11.0.161787180553.issue38337@roundup.psfhosted.org>


New submission from Jonas Drotleff <jonas.drotleff at gmail.com>:

When calling inspect.getmembers on a class that has a property (@property), the property will be called by the getattr call in getmembers.

Example:

import inspect

class Example:
    def __init__(self, var):
        self._var = var
        print('__init__')

    def foo(self, bar):
        print(bar)
        print('foo')

    @property
    def var(self):
        print('Access property')
        return self._var


if __name__ == '__main__':
    ex = Example('Hello')
    print('--- getmembers from instance ---')
    print(inspect.getmembers(ex))
    print('--- getmembers from class    ---')
    print(inspect.getmembers(Example))


Result:

__init__
--- getmembers from instance ---
Access property
[('__class__', <attribute '__class__' of 'object' objects>), ..., ('var', 'Hello')]
--- getmembers from class    ---
[('__class__', <attribute '__class__' of 'object' objects>), ..., ('var', <property object at 0x...>)]


Expected:

__init__
--- getmembers from instance ---
[('__class__', <attribute '__class__' of 'object' objects>), ..., ('var', <property object at 0x...>)]
--- getmembers from class    ---
[('__class__', <attribute '__class__' of 'object' objects>), ..., ('var', <property object at 0x...>)]

----------
components: Library (Lib)
messages: 353688
nosy: jnsdrtlf
priority: normal
severity: normal
status: open
title: inspect: getmembers calls properties
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38337>
_______________________________________

From report at bugs.python.org  Tue Oct  1 08:07:43 2019
From: report at bugs.python.org (Jonas Drotleff)
Date: Tue, 01 Oct 2019 12:07:43 +0000
Subject: [issue38337] inspect: getmembers calls properties
In-Reply-To: <1569931319.11.0.161787180553.issue38337@roundup.psfhosted.org>
Message-ID: <1569931663.61.0.986732735918.issue38337@roundup.psfhosted.org>


Change by Jonas Drotleff <jonas.drotleff at gmail.com>:


----------
keywords: +patch
pull_requests: +16113
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16521

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38337>
_______________________________________

From report at bugs.python.org  Tue Oct  1 08:21:52 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Tue, 01 Oct 2019 12:21:52 +0000
Subject: [issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py
In-Reply-To: <1569032250.18.0.545337961077.issue38243@roundup.psfhosted.org>
Message-ID: <1569932512.79.0.674126476138.issue38243@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> I prefer to keep it open until the 3.5 backport is merged.
Sorry, I didn't find it.
Yes, we should let it open until the PR is merged.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38243>
_______________________________________

From report at bugs.python.org  Tue Oct  1 08:46:23 2019
From: report at bugs.python.org (Mike)
Date: Tue, 01 Oct 2019 12:46:23 +0000
Subject: [issue36054] Way to detect CPU count inside docker container
In-Reply-To: <1550681782.39.0.211832814896.issue36054@roundup.psfhosted.org>
Message-ID: <1569933983.49.0.940090301415.issue36054@roundup.psfhosted.org>


Mike <mcnelson.phd at gmail.com> added the comment:

Is this issue still being worked on as a core feature? I needed a solution for this using 2.7.11 to enable some old code to work properly/nicely in a container environment on AWS Batch and was forced to figure out what OpenJDK was doing and came up with a solution. The process in OpenJDK seems to be, find where the cgroups for docker are located in the file system, then depending on the values in different files you can determine the number of CPUs available. 

The inelegant code below is what worked for me:

def query_cpu():
	if os.path.isfile('/sys/fs/cgroup/cpu/cpu.cfs_quota_us'):
		cpu_quota = int(open('/sys/fs/cgroup/cpu/cpu.cfs_quota_us').read().rstrip())
		#print(cpu_quota) # Not useful for AWS Batch based jobs as result is -1, but works on local linux systems
	if cpu_quota != -1 and os.path.isfile('/sys/fs/cgroup/cpu/cpu.cfs_period_us'):
		cpu_period = int(open('/sys/fs/cgroup/cpu/cpu.cfs_period_us').read().rstrip())
		#print(cpu_period)
		avail_cpu = int(cpu_quota / cpu_period) # Divide quota by period and you should get num of allotted CPU to the container, rounded down if fractional.
	elif os.path.isfile('/sys/fs/cgroup/cpu/cpu.shares'):
		cpu_shares = int(open('/sys/fs/cgroup/cpu/cpu.shares').read().rstrip())
		#print(cpu_shares) # For AWS, gives correct value * 1024.
		avail_cpu = int(cpu_shares / 1024)
	return avail_cpu


This solution makes several assumptions about the cgroup locations within the container vs dynamically finding where those files are located as OpenJDK does. I also haven't included the more robust method in case cpu.quota and cpu.shares are -1.

Hopefully this is a start for getting this implemented.

----------
nosy: +mcnelsonphd

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36054>
_______________________________________

From report at bugs.python.org  Tue Oct  1 08:51:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 12:51:30 +0000
Subject: [issue36054] On Linux,
 os.count() should read cgroup cpu.shares and cpu.cfs (CPU count
 inside docker container)
In-Reply-To: <1550681782.39.0.211832814896.issue36054@roundup.psfhosted.org>
Message-ID: <1569934290.41.0.329471556743.issue36054@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: Way to detect CPU count inside docker container -> On Linux, os.count() should read cgroup cpu.shares and cpu.cfs (CPU count inside docker container)

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36054>
_______________________________________

From report at bugs.python.org  Tue Oct  1 08:55:54 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 12:55:54 +0000
Subject: [issue38338] [2.7] test_ssl fails
Message-ID: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

SSLv23 and TLS v1.0 are disabled by RHEL8 crypto policy.

AMD64 RHEL8 2.7:
https://buildbot.python.org/all/#/builders/245/builds/5

test_protocol_sslv23 (test.test_ssl.ThreadedTests)
Connecting to an SSLv23 server with various client options ... 
 Could not scan /etc/ssl/openssl.cnf for MinProtocol: [Errno 2] No such file or directory: '/etc/ssl/openssl.cnf'

 PROTOCOL_TLS->PROTOCOL_TLS CERT_NONE
 PROTOCOL_TLSv1->PROTOCOL_TLS CERT_NONE
ERROR

======================================================================
ERROR: test_protocol_sslv23 (test.test_ssl.ThreadedTests)
Connecting to an SSLv23 server with various client options
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/test/test_ssl.py", line 189, in f
    return func(*args, **kwargs)
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/test/test_ssl.py", line 2402, in test_protocol_sslv23
    try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_TLSv1, 'TLSv1')
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/test/test_ssl.py", line 2134, in try_protocol_combo
    chatty=False, connectionchatty=False)
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/test/test_ssl.py", line 2062, in server_params_test
    s.connect((HOST, server.port))
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/ssl.py", line 864, in connect
    self._real_connect(addr, False)
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/ssl.py", line 855, in _real_connect
    self.do_handshake()
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/ssl.py", line 828, in do_handshake
    self._sslobj.do_handshake()
SSLError: [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:727)

and

test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests)
Connecting to a TLSv1.1 server with various client options. ... 
 Could not scan /etc/ssl/openssl.cnf for MinProtocol: [Errno 2] No such file or directory: '/etc/ssl/openssl.cnf'

 PROTOCOL_TLSv1_1->PROTOCOL_TLSv1_1 CERT_NONE
 {PROTOCOL_TLS->PROTOCOL_TLSv1_1} CERT_NONE
 PROTOCOL_TLSv1_1->PROTOCOL_TLS CERT_NONE
ERROR

======================================================================
ERROR: test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests)
Connecting to a TLSv1.1 server with various client options.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/test/test_ssl.py", line 189, in f
    return func(*args, **kwargs)
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/test/test_ssl.py", line 2477, in test_protocol_tlsv1_1
    try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_TLSv1_1, 'TLSv1.1')
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/test/test_ssl.py", line 2134, in try_protocol_combo
    chatty=False, connectionchatty=False)
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/test/test_ssl.py", line 2062, in server_params_test
    s.connect((HOST, server.port))
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/ssl.py", line 864, in connect
    self._real_connect(addr, False)
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/ssl.py", line 855, in _real_connect
    self.do_handshake()
  File "/home/buildbot/buildarea/2.7.cstratak-RHEL8-x86_64/build/Lib/ssl.py", line 828, in do_handshake
    self._sslobj.do_handshake()
SSLError: [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:727)

----------
assignee: christian.heimes
components: SSL, Tests
messages: 353691
nosy: christian.heimes, vstinner
priority: normal
severity: normal
status: open
title: [2.7] test_ssl fails
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Tue Oct  1 08:56:28 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 12:56:28 +0000
Subject: [issue38338] [2.7] test_ssl fails
In-Reply-To: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>
Message-ID: <1569934588.38.0.102157039478.issue38338@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +cstratak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Tue Oct  1 08:57:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 12:57:07 +0000
Subject: [issue38338] [2.7] test_ssl fails on RHEL8
In-Reply-To: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>
Message-ID: <1569934627.77.0.108167120218.issue38338@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: [2.7] test_ssl fails -> [2.7] test_ssl fails on RHEL8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Tue Oct  1 09:20:50 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 13:20:50 +0000
Subject: [issue38339] [3.5] The doc job of Travis CI fails on Python 3.5:
 needs at least Sphinx v1.8
Message-ID: <1569936050.09.0.437024380138.issue38339@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

Example:
https://travis-ci.org/python/cpython/jobs/590339147

$ python --version

Python 3.6.3

$ pip --version

pip 9.0.1 from /home/travis/virtualenv/python3.6.3/lib/python3.6/site-packages (python 3.6)

Could not locate requirements.txt. Override the install: key in your .travis.yml to install dependencies.
before_script.1

0.00s$ cd Doc
before_script.2

8.58s$ python -m pip install sphinx~=1.6.1 blurb

1.88s$ make check suspicious html SPHINXOPTS="-q -W -j4"

python3 tools/rstlint.py -i tools -i ./venv -i README.rst

No problems found.

make[1]: Entering directory `/home/travis/build/python/cpython/Doc'

mkdir -p build

Building NEWS from Misc/NEWS.d with blurb

PATH=./venv/bin:$PATH sphinx-build -b suspicious -d build/doctrees -D latex_elements.papersize= -q -W -j4 . build/suspicious 

Sphinx version error:

This project needs at least Sphinx v1.8 and therefore cannot be built with this version.

make[1]: *** [build] Error 1

make[1]: Leaving directory `/home/travis/build/python/cpython/Doc'

Suspicious check complete; look for any errors in the above output or in build/suspicious/suspicious.csv.  If all issues are false positives, append that file to tools/susp-ignored.csv.

make: *** [suspicious] Error 1

The command "make check suspicious html SPHINXOPTS="-q -W -j4"" exited with 2.
cache.2

store build cache

----------
assignee: docs at python
components: Documentation
messages: 353692
nosy: docs at python, mdk, vstinner
priority: normal
severity: normal
status: open
title: [3.5] The doc job of Travis CI fails on Python 3.5: needs at least Sphinx v1.8
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38339>
_______________________________________

From report at bugs.python.org  Tue Oct  1 09:23:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 13:23:42 +0000
Subject: [issue38339] [3.5] The doc job of Travis CI fails on Python 3.5:
 needs at least Sphinx v1.8
In-Reply-To: <1569936050.09.0.437024380138.issue38339@roundup.psfhosted.org>
Message-ID: <1569936222.18.0.971372503731.issue38339@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

This issue prevents to merge the following 3.5 pull requests:
https://github.com/python/cpython/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+base%3A3.5+

----------
nosy: +larry

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38339>
_______________________________________

From report at bugs.python.org  Tue Oct  1 09:24:11 2019
From: report at bugs.python.org (ECAS India)
Date: Tue, 01 Oct 2019 13:24:11 +0000
Subject: [issue38340] ERROR WHILE BUILDING pyworld for x86_64-linux-gnu-gcc
Message-ID: <1569936251.44.0.0859719635079.issue38340@roundup.psfhosted.org>


New submission from ECAS India <erpuneetbawa at gmail.com>:

creating build/temp.linux-x86_64-3.7/lib/World
  creating build/temp.linux-x86_64-3.7/lib/World/src
  x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ilib/World/src -I/usr/include/python3.7m -I/usr/local/lib/python3.7/dist-packages/numpy/core/include -c pyworld/pyworld.cpp -o build/temp.linux-x86_64-3.7/pyworld/pyworld.o
  x86_64-linux-gnu-gcc: error: pyworld/pyworld.cpp: No such file or directory
  x86_64-linux-gnu-gcc: fatal error: no input files
  compilation terminated.
  error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
  
  ----------------------------------------
  Failed building wheel for pyworld
  Running setup.py clean for pyworld
Failed to build pyworld

----------
files: Screenshot from 2019-10-01 18-53-25.png
messages: 353694
nosy: ECAS India
priority: normal
severity: normal
status: open
title: ERROR WHILE BUILDING pyworld for x86_64-linux-gnu-gcc
type: compile error
versions: Python 3.7
Added file: https://bugs.python.org/file48635/Screenshot from 2019-10-01 18-53-25.png

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38340>
_______________________________________

From report at bugs.python.org  Tue Oct  1 09:25:28 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 13:25:28 +0000
Subject: [issue38339] [3.5] The doc job of Travis CI fails on Python 3.5:
 needs at least Sphinx v1.8
In-Reply-To: <1569936050.09.0.437024380138.issue38339@roundup.psfhosted.org>
Message-ID: <1569936328.19.0.690529231769.issue38339@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I suggest to backport https://github.com/python/cpython/pull/10676 to 3.5: use Sphinx 1.8.2 in .travis.yml. Commit in the 3.6 branch:

commit 23a98abd4256f931ed89b65ec6babd4f06dbff97
Author: Miss Islington (bot) <31488909+miss-islington at users.noreply.github.com>
Date:   Sat Dec 8 21:34:30 2018 -0800

    [3.7] Doc: Bump sphinx. (GH-10676) (GH-10803)
    
    (cherry picked from commit 2db96ae7444880d66d4ef65abab8a5e6ff328711)
    
    Co-authored-by: Julien Palard <julien at palard.fr>

diff --git a/.travis.yml b/.travis.yml
index ed4e46c782..8250fd91b3 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -43,7 +43,7 @@ matrix:
         - cd Doc
         # Sphinx is pinned so that new versions that introduce new warnings won't suddenly cause build failures.
         # (Updating the version is fine as long as no warnings are raised by doing so.)
-        - python -m pip install sphinx~=1.6.1 blurb
+        - python -m pip install sphinx==1.8.2 blurb
       script:
         - make check suspicious html SPHINXOPTS="-q -W -j4"
     - os: linux

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38339>
_______________________________________

From report at bugs.python.org  Tue Oct  1 09:27:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 13:27:13 +0000
Subject: [issue38339] [3.5] The doc job of Travis CI fails on Python 3.5:
 needs at least Sphinx v1.8
In-Reply-To: <1569936050.09.0.437024380138.issue38339@roundup.psfhosted.org>
Message-ID: <1569936433.1.0.6913943827.issue38339@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16115
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16522

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38339>
_______________________________________

From report at bugs.python.org  Tue Oct  1 09:28:07 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 01 Oct 2019 13:28:07 +0000
Subject: [issue38340] ERROR WHILE BUILDING pyworld for x86_64-linux-gnu-gcc
In-Reply-To: <1569936251.44.0.0859719635079.issue38340@roundup.psfhosted.org>
Message-ID: <1569936487.73.0.0121065283684.issue38340@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

This is an issue tracker for CPython. The build log seems like an issue with pyworld package. I would suggest creating an issue in their tracker.

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38340>
_______________________________________

From report at bugs.python.org  Tue Oct  1 09:28:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 13:28:55 +0000
Subject: [issue38339] [3.5] The doc job of Travis CI fails on Python 3.5:
 needs at least Sphinx v1.8
In-Reply-To: <1569936050.09.0.437024380138.issue38339@roundup.psfhosted.org>
Message-ID: <1569936535.38.0.510129404962.issue38339@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I proposed PR 16522 to update Sphinx from version 1.6.1 to 1.8.2.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38339>
_______________________________________

From report at bugs.python.org  Tue Oct  1 10:03:07 2019
From: report at bugs.python.org (Sanjay)
Date: Tue, 01 Oct 2019 14:03:07 +0000
Subject: [issue38337] inspect: getmembers calls properties
In-Reply-To: <1569931319.11.0.161787180553.issue38337@roundup.psfhosted.org>
Message-ID: <1569938587.96.0.742008377806.issue38337@roundup.psfhosted.org>


Sanjay <sanjay537 at gmail.com> added the comment:

the issue happens in 2.7 as well

----------
nosy: +Sanjay
versions: +Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38337>
_______________________________________

From report at bugs.python.org  Tue Oct  1 11:35:07 2019
From: report at bugs.python.org (Charalampos Stratakis)
Date: Tue, 01 Oct 2019 15:35:07 +0000
Subject: [issue37096] Add large-file tests for modules using sendfile(2)
In-Reply-To: <1559200699.13.0.758657145229.issue37096@roundup.psfhosted.org>
Message-ID: <1569944107.21.0.496609356315.issue37096@roundup.psfhosted.org>


Charalampos Stratakis <cstratak at redhat.com> added the comment:

After this change I get some disk space issues on the Fedora rawhide buildbot for the clang installed build only (and strangely enough not for the other jobs). There are currently around 9GB of free space there:

https://buildbot.python.org/all/#/builders/188/builds/1110

======================================================================
ERROR: test_tofromfile (test.test_array.DoubleTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-rawhide-x86_64.clang-installed/build/target/lib/python3.9/test/test_array.py",
line 374, in test_tofromfile
    f.close()
OSError: [Errno 28] No space left on device

----------
nosy: +cstratak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37096>
_______________________________________

From report at bugs.python.org  Tue Oct  1 12:01:15 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 01 Oct 2019 16:01:15 +0000
Subject: [issue38248] inconsistency in asyncio.Task between cancellation while
 running vs. cancellation immediately after it finishes
In-Reply-To: <1569141924.07.0.413373545347.issue38248@roundup.psfhosted.org>
Message-ID: <1569945675.38.0.0693245872436.issue38248@roundup.psfhosted.org>


Change by Yury Selivanov <yselivanov at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38248>
_______________________________________

From report at bugs.python.org  Tue Oct  1 12:02:56 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 01 Oct 2019 16:02:56 +0000
Subject: [issue37146] opcode cache for LOAD_GLOBAL emits false alarm in memory
 leak hunting
In-Reply-To: <1559594083.93.0.475089830437.issue37146@roundup.psfhosted.org>
Message-ID: <1569945776.09.0.772960370073.issue37146@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

> It seems like nobody came up with a solution for the debug mode since June. I close the issue. Reopen it if you would like to propose a solution.

I think the only solution is to have a flag to disable optimizations, inlcluding this one.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37146>
_______________________________________

From report at bugs.python.org  Tue Oct  1 12:42:10 2019
From: report at bugs.python.org (Giampaolo Rodola')
Date: Tue, 01 Oct 2019 16:42:10 +0000
Subject: [issue37096] Add large-file tests for modules using sendfile(2)
In-Reply-To: <1559200699.13.0.758657145229.issue37096@roundup.psfhosted.org>
Message-ID: <1569948130.86.0.427985570941.issue37096@roundup.psfhosted.org>


Giampaolo Rodola' <g.rodola at gmail.com> added the comment:

Sorry about that. I'm attaching a patch which skips those tests if there's not enough free disk space. If you confirm it works I'll make a PR.

----------
Added file: https://bugs.python.org/file48636/disk-space.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37096>
_______________________________________

From report at bugs.python.org  Tue Oct  1 13:06:05 2019
From: report at bugs.python.org (Zachary Ware)
Date: Tue, 01 Oct 2019 17:06:05 +0000
Subject: [issue38313] Crash/No start
In-Reply-To: <1569726233.14.0.289073858967.issue38313@roundup.psfhosted.org>
Message-ID: <1569949565.52.0.735762960417.issue38313@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:

Feel free to reopen if you can answer the questions in my previous message.

----------
resolution:  -> works for me
stage:  -> resolved
status: pending -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38313>
_______________________________________

From report at bugs.python.org  Tue Oct  1 13:08:29 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 17:08:29 +0000
Subject: [issue37096] Add large-file tests for modules using sendfile(2)
In-Reply-To: <1559200699.13.0.758657145229.issue37096@roundup.psfhosted.org>
Message-ID: <1569949709.1.0.359192808466.issue37096@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Should we decorate the new files with @requires('largefile', '...')? Documentation:

    largefile - It is okay to run some test that may create huge
                files.  These tests can take a long time and may
                consume >2 GiB of disk space temporarily.

It may be interesting to add an option to regrtest to specify how much space can be used by tests, an option similar to -M/--memlimit which is for memory.

I don't recall if largefile is enabled by default on buildbots or not :-p

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37096>
_______________________________________

From report at bugs.python.org  Tue Oct  1 13:19:53 2019
From: report at bugs.python.org (Charalampos Stratakis)
Date: Tue, 01 Oct 2019 17:19:53 +0000
Subject: [issue37096] Add large-file tests for modules using sendfile(2)
In-Reply-To: <1559200699.13.0.758657145229.issue37096@roundup.psfhosted.org>
Message-ID: <1569950393.87.0.470105470541.issue37096@roundup.psfhosted.org>


Charalampos Stratakis <cstratak at redhat.com> added the comment:

It seems that the -uall argument is passed to regrtest invocation for the buildbot run [0] which invokes the largefile tests (including all the resource intensive tests). However when configure is run you can see: checking whether to enable large file support... no

[0] https://github.com/python/cpython/blob/master/Lib/test/libregrtest/cmdline.py#L81

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37096>
_______________________________________

From report at bugs.python.org  Tue Oct  1 13:43:04 2019
From: report at bugs.python.org (Tony Cappellini)
Date: Tue, 01 Oct 2019 17:43:04 +0000
Subject: [issue37424] subprocess.run timeout does not function if shell=True
 and capture_output=True
In-Reply-To: <1561618790.88.0.611701645761.issue37424@roundup.psfhosted.org>
Message-ID: <1569951784.27.0.891099265896.issue37424@roundup.psfhosted.org>


Tony Cappellini <cappy2112 at gmail.com> added the comment:

I'm still seeing hangs with subprocess.run() in Python 3.7.4
Unfortunately, it involves talking to an NVME SSD on Linux, so I cannot
easily submit code to duplicate it.

----------
nosy: +cappy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37424>
_______________________________________

From report at bugs.python.org  Tue Oct  1 13:55:25 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 01 Oct 2019 17:55:25 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569912143.0.0.669955016968.issue38333@roundup.psfhosted.org>
Message-ID: <CAP7+vJKeRzoVH9eTpmgdFGYac=RHwCNyCGD431SFWAp68RjBeg@mail.gmail.com>


Guido van Rossum <guido at python.org> added the comment:

I'm sorry, but that's unacceptable.

On Mon, Sep 30, 2019 at 23:42 Vedran ?a?i? <report at bugs.python.org> wrote:

>
> Vedran ?a?i? <vedgar at gmail.com> added the comment:
>
> > Many docs are ... vague about types.
>
> ... and I consider that a feature. At least if you do that, make an
> explicit decision not to introduce TypeErrors for "disagreeing with the
> documented signature".
>
> For example, I'd be ok with sum being documented as taking an iterable of
> numbers and returning a number, but it would be a catastrophe if as a
> consequence of that, sum of a list of lists would stop working.
>
> ----------
> nosy: +veky
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue38333>
> _______________________________________
>
-- 
--Guido (mobile)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Tue Oct  1 14:00:22 2019
From: report at bugs.python.org (Tony Cappellini)
Date: Tue, 01 Oct 2019 18:00:22 +0000
Subject: [issue37424] subprocess.run timeout does not function if shell=True
 and capture_output=True
In-Reply-To: <1561618790.88.0.611701645761.issue37424@roundup.psfhosted.org>
Message-ID: <1569952822.43.0.274093840921.issue37424@roundup.psfhosted.org>


Tony Cappellini <cappy2112 at gmail.com> added the comment:

Using Python 3.7.4, I'm calling subprocess.run() with the following arguments. .run() still hangs even though a timeout is being passed in.

subprocess.run(cmd_list,                                            stdout=subprocess.PIPE,                                           stderr=subprocess.STDOUT,                                           shell=False,                                           timeout=timeout_val,                                           check=True,                                           universal_newlines=True)



cmd_list contains the name of the bash script below, which is
./rescan.sh

------------------------------------------------------------------
#!/usr/bin/bash

echo Rescanning system for PCIe devices

echo "Rescan device"
echo 1 > /sys/bus/pci/rescan

sleep 5

if [ `lspci | grep -ic "Non-Volatile memory controller"` -gt 0 ]
then
	echo "Device Detected after Rescan"
else 
	echo "Device NOT detected after Rescan"
	exit 1
fi 

echo Rescan Done


This script is scanning for NVME SSDs, so duplicating the issue is not as straightforward as submitting a python script.

The OS is CentOS 7. 

uname  -a shows
 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I know the Kernel is old, but we have a restriction against updating it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37424>
_______________________________________

From report at bugs.python.org  Tue Oct  1 14:29:30 2019
From: report at bugs.python.org (Tim Peters)
Date: Tue, 01 Oct 2019 18:29:30 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1569954570.37.0.419140675844.issue38006@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

Neil, about this comment:

#   - ct is not yet trash (it actually is but the GC doesn't know because of
#     the missing tp_traverse method).

I believe gc should know ct is trash.  ct is in the cf list, and the latter does have tp_traverse.

What gc won't know is that `a` is trash, because `a` is attached to ct, and ct doesn't have tp_traverse.

It should blow up anyway :-)

Maybe with a simpler structure it would be easier to rearrange code to nudge the callback into getting cleared before use?

Z <- Y <- A <-> B -> WZ -> C

where WZ is a weakref to Z with callback C, and Y doesn't implement tp_traverse.  The only cycle is between A and B, which could just as well be the same object.  All the other stuff hangs off that cycle.

It's all trash, but we won't know in advance that Z is part of it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Tue Oct  1 16:23:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 20:23:56 +0000
Subject: [issue37096] Add large-file tests for modules using sendfile(2)
In-Reply-To: <1559200699.13.0.758657145229.issue37096@roundup.psfhosted.org>
Message-ID: <1569961436.78.0.737885895101.issue37096@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> checking whether to enable large file support... no

That's only at the C level to decide how to pass a file position.

It's unrelated to the regrtest "largefile" resource.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37096>
_______________________________________

From report at bugs.python.org  Tue Oct  1 16:26:06 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 01 Oct 2019 20:26:06 +0000
Subject: [issue37424] subprocess.run timeout does not function if shell=True
 and capture_output=True
In-Reply-To: <1561618790.88.0.611701645761.issue37424@roundup.psfhosted.org>
Message-ID: <1569961566.08.0.0211341598222.issue37424@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> I'm still seeing hangs with subprocess.run() in Python 3.7.4

That's not surprising, the fix has been pushed at 2019-09-11. Python 3.7.5 will include the fix and it will be released soon:
https://www.python.org/dev/peps/pep-0537/

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37424>
_______________________________________

From report at bugs.python.org  Tue Oct  1 16:28:42 2019
From: report at bugs.python.org (Ronald Oussoren)
Date: Tue, 01 Oct 2019 20:28:42 +0000
Subject: [issue38331] Exec not recognizing global variables inside function
In-Reply-To: <1569875978.41.0.850227388561.issue38331@roundup.psfhosted.org>
Message-ID: <1569961722.92.0.434496977098.issue38331@roundup.psfhosted.org>


Ronald Oussoren <ronaldoussoren at mac.com> added the comment:

I don't think this is a bug.

def func():
   print(var)

This captures the globals at the time of definition, that is "global" references are resolved using the func.__globals__ attribute which is the globals dictionary at the time the function is created

exec("func()", globals=my_globals;locals=my_globals)

This runs code with a different globals dictionary, but that doesn't affect the already defined function because it resolves names with the previously captured globals dictionary.

This is basically the mechanism that ensures that functions defined in a module use that modules global namespace, and not the globals from where they are called.

----------
nosy: +ronaldoussoren

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38331>
_______________________________________

From report at bugs.python.org  Tue Oct  1 16:40:45 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 01 Oct 2019 20:40:45 +0000
Subject: [issue36470] dataclasses.replace raises an exception if InitVar with
 default argument is not provided.
In-Reply-To: <1553860338.68.0.823118501948.issue36470@roundup.psfhosted.org>
Message-ID: <1569962445.5.0.543113062189.issue36470@roundup.psfhosted.org>


Change by Eric V. Smith <eric at trueblade.com>:


----------
assignee:  -> eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36470>
_______________________________________

From report at bugs.python.org  Tue Oct  1 16:50:47 2019
From: report at bugs.python.org (Norman Denayer)
Date: Tue, 01 Oct 2019 20:50:47 +0000
Subject: [issue38341] Add SMTPNotSupportedError in the exports of smtplib
Message-ID: <1569963046.98.0.477841717728.issue38341@roundup.psfhosted.org>


New submission from Norman Denayer <denayer.norman at gmail.com>:

Long story short:
smtplib.SMTPNotSupportedError seems the only exception not present in __all__ variable exposed by smtplib.py

Context:
I currently face an issue running mypy on one of my module:
...tools/email.py:46: error: Module has no attribute "SMTPNotSupportedError"
            except smtplib.SMTPNotSupportedError:

Digging into the context of this error, I note this exception is not exposed in the list __all__.

Regards,
Norman

----------
components: email
messages: 353712
nosy: Norman.Denayer, barry, r.david.murray
priority: normal
severity: normal
status: open
title: Add SMTPNotSupportedError in the exports of smtplib
type: enhancement
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38341>
_______________________________________

From report at bugs.python.org  Tue Oct  1 16:52:28 2019
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 01 Oct 2019 20:52:28 +0000
Subject: [issue38341] Add SMTPNotSupportedError in the exports of smtplib
In-Reply-To: <1569963046.98.0.477841717728.issue38341@roundup.psfhosted.org>
Message-ID: <1569963147.99.0.96003009692.issue38341@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +16116
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16525

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38341>
_______________________________________

From report at bugs.python.org  Tue Oct  1 16:55:23 2019
From: report at bugs.python.org (Neil Schemenauer)
Date: Tue, 01 Oct 2019 20:55:23 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1569963323.42.0.838084079366.issue38006@roundup.psfhosted.org>


Neil Schemenauer <nas-python at arctrix.com> added the comment:

?ukasz, is there some reason you removed old versions (2.7, 3.6, etc)?  The bug is present on those versions of Python and it should be trivial to backport the fix.  If those branches are maintained, I think we should fix it.

Attached is a small test program (gc_weakref_bug_demo2.py) that causes the same crash as in this bug report (SEGV inside _PyFunction_Vectorcall).  Setting things up is quite tricky and it depends on the order that things are cleared in delete_garbage().  Maybe still worth making a unit test for it?

Instead of using the 'dummy' function, you can also use types.SimpleNamespace().  Calling repr() on it after tp_clear will result in a crash or an assert failure.  Those two crashes are not needed to confirm the bug.  Just the fact that 'callback' runs is proof enough.  So, in a unit test, the callback to just set a global to indicate failure.

----------
Added file: https://bugs.python.org/file48637/gc_weakref_bug_demo2.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Tue Oct  1 18:22:11 2019
From: report at bugs.python.org (Anthony Tuininga)
Date: Tue, 01 Oct 2019 22:22:11 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
Message-ID: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>


New submission from Anthony Tuininga <anthony.tuininga at gmail.com>:

Running the suggested code found at https://docs.python.org/3.8/whatsnew/3.8.html regarding the new importlib.metadata module

from importlib.metadata import version, requires, files
version('requests')

yields the error

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.8/importlib/metadata/__init__.py", line 365, in version
    return distribution(package).version
  File "/usr/local/lib/python3.8/importlib/metadata/__init__.py", line 338, in distribution
    return Distribution.from_name(package)
  File "/usr/local/lib/python3.8/importlib/metadata/__init__.py", line 159, in from_name
    dists = resolver(name)
  File "<frozen importlib._bootstrap_external>", line 1381, in find_distributions
ImportError: cannot import name 'MetadataPathFinder' from 'importlib.metadata' (/usr/local/lib/python3.8/importlib/metadata/__init__.py)

----------
components: Library (Lib)
messages: 353714
nosy: atuining
priority: normal
severity: normal
status: open
title: ImportError: cannot import name 'MetadataPathFinder' from 'importlib.metadata'
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Tue Oct  1 18:27:41 2019
From: report at bugs.python.org (=?utf-8?q?Ionel_Cristian_M=C4=83rie=C8=99?=)
Date: Tue, 01 Oct 2019 22:27:41 +0000
Subject: [issue38227] Setting a signal handler gets multiprocessing.Pool stuck
In-Reply-To: <1568929295.79.0.555392640133.issue38227@roundup.psfhosted.org>
Message-ID: <1569968861.72.0.715706456082.issue38227@roundup.psfhosted.org>


Change by Ionel Cristian M?rie? <contact at ionelmc.ro>:


----------
components: +Library (Lib)

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38227>
_______________________________________

From report at bugs.python.org  Tue Oct  1 19:01:39 2019
From: report at bugs.python.org (Steve Dower)
Date: Tue, 01 Oct 2019 23:01:39 +0000
Subject: [issue38343] Version name in PC/layout read incorrectly for RC
Message-ID: <1569970899.08.0.367684181352.issue38343@roundup.psfhosted.org>


New submission from Steve Dower <steve.dower at python.org>:

I noticed that when the nuget.org packages published for 3.8.0rc1, they were given the version "3.8.0".

3.7.5rc1 was okay because it's still using the old approach to setting the version.

This needs to be fixed before any more RCs are released. I'll see if I can get the incorrectly versioned files removed from nuget and replace them with RCs.

----------
assignee: steve.dower
components: Windows
keywords: 3.8regression
messages: 353715
nosy: paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title: Version name in PC/layout read incorrectly for RC
type: behavior
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38343>
_______________________________________

From report at bugs.python.org  Tue Oct  1 19:04:16 2019
From: report at bugs.python.org (Steve Dower)
Date: Tue, 01 Oct 2019 23:04:16 +0000
Subject: [issue38343] Version name in PC/layout read incorrectly for RC
In-Reply-To: <1569970899.08.0.367684181352.issue38343@roundup.psfhosted.org>
Message-ID: <1569971056.4.0.651959130234.issue38343@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
nosy: +lukasz.langa

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38343>
_______________________________________

From report at bugs.python.org  Tue Oct  1 19:09:37 2019
From: report at bugs.python.org (Steve Dower)
Date: Tue, 01 Oct 2019 23:09:37 +0000
Subject: [issue38343] Version name in PC/layout read incorrectly for RC
In-Reply-To: <1569970899.08.0.367684181352.issue38343@roundup.psfhosted.org>
Message-ID: <1569971377.85.0.287739570608.issue38343@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords: +patch
pull_requests: +16118
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16527

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38343>
_______________________________________

From report at bugs.python.org  Tue Oct  1 19:42:31 2019
From: report at bugs.python.org (Steve Dower)
Date: Tue, 01 Oct 2019 23:42:31 +0000
Subject: [issue38343] Version name in PC/layout read incorrectly for RC
In-Reply-To: <1569970899.08.0.367684181352.issue38343@roundup.psfhosted.org>
Message-ID: <1569973351.42.0.875855357477.issue38343@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset b9a8b8296cd7be22f8b5bf92af686a788c47c7bf by Steve Dower in branch 'master':
bpo-38343: Fixes version handling for nuget packages (GH-16527)
https://github.com/python/cpython/commit/b9a8b8296cd7be22f8b5bf92af686a788c47c7bf


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38343>
_______________________________________

From report at bugs.python.org  Tue Oct  1 19:42:37 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 01 Oct 2019 23:42:37 +0000
Subject: [issue38343] Version name in PC/layout read incorrectly for RC
In-Reply-To: <1569970899.08.0.367684181352.issue38343@roundup.psfhosted.org>
Message-ID: <1569973357.41.0.860097275668.issue38343@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16119
pull_request: https://github.com/python/cpython/pull/16528

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38343>
_______________________________________

From report at bugs.python.org  Tue Oct  1 19:46:06 2019
From: report at bugs.python.org (Steve Dower)
Date: Tue, 01 Oct 2019 23:46:06 +0000
Subject: [issue38343] Version name in PC/layout read incorrectly for RC
In-Reply-To: <1569970899.08.0.367684181352.issue38343@roundup.psfhosted.org>
Message-ID: <1569973566.32.0.0294159949871.issue38343@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

I already republished correctly-versioned files and unlisted the wrong ones (as well as contacting support to see whether they can delete them completely so they don't impact the final release).

The change above fixes the issue. It will need cherry-picking for the v3.8.0 tag (or the v3.8.0rc2 tag...).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38343>
_______________________________________

From report at bugs.python.org  Tue Oct  1 20:00:52 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Oct 2019 00:00:52 +0000
Subject: [issue38343] Version name in PC/layout read incorrectly for RC
In-Reply-To: <1569970899.08.0.367684181352.issue38343@roundup.psfhosted.org>
Message-ID: <1569974452.54.0.829167363038.issue38343@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset a11df75269b5d47248be617ed02e96c1d1938fd1 by Miss Islington (bot) in branch '3.8':
bpo-38343: Fixes version handling for nuget packages (GH-16527)
https://github.com/python/cpython/commit/a11df75269b5d47248be617ed02e96c1d1938fd1


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38343>
_______________________________________

From report at bugs.python.org  Tue Oct  1 20:01:20 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 02 Oct 2019 00:01:20 +0000
Subject: [issue38343] Version name in PC/layout read incorrectly for RC
In-Reply-To: <1569970899.08.0.367684181352.issue38343@roundup.psfhosted.org>
Message-ID: <1569974480.55.0.206654581075.issue38343@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38343>
_______________________________________

From report at bugs.python.org  Tue Oct  1 20:09:47 2019
From: report at bugs.python.org (Eric Snow)
Date: Wed, 02 Oct 2019 00:09:47 +0000
Subject: [issue38187] test.test_tools.test_c_analyzer fails in refleak mode
In-Reply-To: <1568646466.84.0.78149770012.issue38187@roundup.psfhosted.org>
Message-ID: <1569974987.22.0.875268949192.issue38187@roundup.psfhosted.org>


Change by Eric Snow <ericsnowcurrently at gmail.com>:


----------
status: pending -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38187>
_______________________________________

From report at bugs.python.org  Tue Oct  1 20:23:55 2019
From: report at bugs.python.org (Daniel Hillier)
Date: Wed, 02 Oct 2019 00:23:55 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1569975835.93.0.854000276183.issue38334@roundup.psfhosted.org>


Change by Daniel Hillier <daniel.hillier at gmail.com>:


----------
keywords: +patch
pull_requests: +16120
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16529

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Tue Oct  1 20:39:03 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Wed, 02 Oct 2019 00:39:03 +0000
Subject: [issue38332] invalid content-transfer-encoding in encoded-word causes
 KeyError
In-Reply-To: <1569877053.41.0.568400002445.issue38332@roundup.psfhosted.org>
Message-ID: <1569976743.53.0.730994697804.issue38332@roundup.psfhosted.org>


Emmanuel Arias <emmanuelarias30 at gmail.com> added the comment:

Hi Andrei sorry for my last message. Now I understand perfectly your idea and your PR. IMO this is a correct patch.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38332>
_______________________________________

From report at bugs.python.org  Tue Oct  1 21:47:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 01:47:56 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1569980876.62.0.959315717695.issue36670@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16121
pull_request: https://github.com/python/cpython/pull/16530

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 01:47:38 2019
From: report at bugs.python.org (=?utf-8?q?Mathias_Fr=C3=B6hlich?=)
Date: Wed, 02 Oct 2019 05:47:38 +0000
Subject: [issue18309] Make python slightly more relocatable
In-Reply-To: <1372262450.0.0.792872111515.issue18309@psf.upfronthosting.co.za>
Message-ID: <1569995258.77.0.195009160545.issue18309@roundup.psfhosted.org>


Mathias Fr?hlich <Mathias.Froehlich at web.de> added the comment:

Ok, so far.
But what shall I do now?
It would be nice that python is a bit smarter in finding its increasing important module files when being embedded into an application.
Anybody out there who wants to look at that contribution?
best
Mathias

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue18309>
_______________________________________

From report at bugs.python.org  Wed Oct  2 02:01:56 2019
From: report at bugs.python.org (=?utf-8?b?0JDQu9C10LrRgdCw0L3QtNGAINCh0LXQvNC10L3QvtCy?=)
Date: Wed, 02 Oct 2019 06:01:56 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
In-Reply-To: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>
Message-ID: <1569996116.13.0.873484254785.issue38342@roundup.psfhosted.org>


????????? ??????? <iamsav at gmail.com> added the comment:

on windows
```C:\>py -c "import sys;from importlib.metadata import version, requires, files;print(sys.version);print(version('requests'))"
3.8.0b4 (tags/v3.8.0b4:d93605d, Aug 29 2019, 23:21:28) [MSC v.1916 64 bit (AMD64)]
2.22.0
```

----------
nosy: +iamsav

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Wed Oct  2 02:30:23 2019
From: report at bugs.python.org (James Abel)
Date: Wed, 02 Oct 2019 06:30:23 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
Message-ID: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>


New submission from James Abel <jamescabel at gmail.com>:

In activate.bat, the else needs to be on the same line as the if

----------
components: Windows
messages: 353722
nosy: James Abel, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: activate.bat else needs to be on the same line as the if
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Wed Oct  2 02:30:42 2019
From: report at bugs.python.org (Robert Kearns)
Date: Wed, 02 Oct 2019 06:30:42 +0000
Subject: [issue38345] Add end lines to pyclbr objects
Message-ID: <1569997842.45.0.505629355226.issue38345@roundup.psfhosted.org>


Change by Robert Kearns <rxk0914 at hotmail.com>:


----------
components: Library (Lib)
nosy: RobertKearns
priority: normal
severity: normal
status: open
title: Add end lines to pyclbr objects
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38345>
_______________________________________

From report at bugs.python.org  Wed Oct  2 02:31:55 2019
From: report at bugs.python.org (James Abel)
Date: Wed, 02 Oct 2019 06:31:55 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1569997915.71.0.279899009029.issue38344@roundup.psfhosted.org>


Change by James Abel <j at abel.co>:


----------
keywords: +patch
pull_requests: +16122
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16533

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Wed Oct  2 02:40:26 2019
From: report at bugs.python.org (Robert Kearns)
Date: Wed, 02 Oct 2019 06:40:26 +0000
Subject: [issue38345] Add end lines to pyclbr objects
Message-ID: <1569998426.95.0.986811491718.issue38345@roundup.psfhosted.org>


Change by Robert Kearns <rxk0914 at hotmail.com>:


----------
keywords: +patch
pull_requests: +16124
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16534

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38345>
_______________________________________

From report at bugs.python.org  Wed Oct  2 02:41:31 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 02 Oct 2019 06:41:31 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
In-Reply-To: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>
Message-ID: <1569998491.81.0.219120400316.issue38342@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +jaraco

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Wed Oct  2 03:20:26 2019
From: report at bugs.python.org (Mariusz Wawrzonkowski)
Date: Wed, 02 Oct 2019 07:20:26 +0000
Subject: [issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead
 to memory corruption and deadlock
In-Reply-To: <1568200653.3.0.865964137512.issue38106@roundup.psfhosted.org>
Message-ID: <1570000826.57.0.693507387503.issue38106@roundup.psfhosted.org>


Mariusz Wawrzonkowski <x9a at wp.pl> added the comment:

I can confirm that I have the deadlock because of the reason described above. When I change the PyThread_release_lock source locally to signal before releasing the mutex, then my deadlock does not occur anymore. I have tested it on a heave multithreading model.

----------
nosy: +mariosoft

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38106>
_______________________________________

From report at bugs.python.org  Wed Oct  2 03:51:17 2019
From: report at bugs.python.org (Florimond Manca)
Date: Wed, 02 Oct 2019 07:51:17 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
In-Reply-To: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>
Message-ID: <1570002677.93.0.802089440934.issue38342@roundup.psfhosted.org>


Florimond Manca <florimond.manca2 at gmail.com> added the comment:

Can confirm this on 3.8.0rc1+ / macOS Mojave:

```console
$ python -c "import importlib.metadata; print(list(importlib.metadata.distributions()))"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/florimond/.pyenv/versions/3.8-dev/lib/python3.8/importlib/metadata/__init__.py", line 175, in <genexpr>
    resolver()
  File "<frozen importlib._bootstrap_external>", line 1381, in find_distributions
ImportError: cannot import name 'MetadataPathFinder' from 'importlib.metadata' (/Users/florimond/.pyenv/versions/3.8-dev/lib/python3.8/importlib/metadata/__init__.py)
```

I discovered this pytest started failing on 3.8-dev because it uses `importlib.metadata.distributions()` internally.

3.8.0b4+ used to be fine I believe. I'd assume this is a rather critical bug?

----------
nosy: +Florimond Manca

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Wed Oct  2 04:08:36 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 02 Oct 2019 08:08:36 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
In-Reply-To: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>
Message-ID: <1570003716.97.0.394730637077.issue38342@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

The library was synced with https://bugs.python.org/issue38121 which seems to be related to this.

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Wed Oct  2 04:23:36 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 08:23:36 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1570004616.02.0.257993237306.issue38006@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Oh, Neil missed "bpo-38006: " prefix in his commit. Here it is:

commit bcda460baf25062ab68622b3f043f52b9db4d21d
Author: Neil Schemenauer <nas-github at arctrix.com>
Date:   Mon Sep 30 10:06:45 2019 -0700

    Clear weakrefs in garbage found by the GC (#16495)
    
    Fix a bug due to the interaction of weakrefs and the cyclic garbage
    collector. We must clear any weakrefs in garbage in order to prevent
    their callbacks from executing and causing a crash.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Wed Oct  2 04:52:49 2019
From: report at bugs.python.org (Jim Jeon)
Date: Wed, 02 Oct 2019 08:52:49 +0000
Subject: [issue38346] Wrong behavior when using `assert_called_with` with
 mutable object
Message-ID: <1570006369.69.0.450054962888.issue38346@roundup.psfhosted.org>


New submission from Jim Jeon <jimjeon.me at gmail.com>:

When `assert_called_with` is used with mutable object, test fails if the object has changed. I think this is not what it meant to do.

https://docs.python.org/dev/library/unittest.mock-examples.html#coping-with-mutable-arguments

The same situation is explained in this document. But I don't understand why they did not fix and just are proposing some solutions to the users.

----------
components: Tests
files: Screen Shot 2019-10-02 at 5.22.05 PM.png
messages: 353727
nosy: Jim Jeon
priority: normal
severity: normal
status: open
title: Wrong behavior when using `assert_called_with` with mutable object
type: enhancement
versions: Python 3.7
Added file: https://bugs.python.org/file48638/Screen Shot 2019-10-02 at 5.22.05 PM.png

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38346>
_______________________________________

From report at bugs.python.org  Wed Oct  2 05:15:35 2019
From: report at bugs.python.org (=?utf-8?b?UsO8ZGlnZXIgUGzDvG0=?=)
Date: Wed, 02 Oct 2019 09:15:35 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
Message-ID: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>


New submission from R?diger Pl?m <r.pluem at gmx.de>:

Tools/scripts/pathfix.py does not find Python scripts that contain a '-' in their filename when working recursively.
This is caused by the regular expression used to detect whether a filename is a Python script:

r'^[a-zA-Z0-9_]+\.py$'

r'^[a-zA-Z0-9_-]+\.py$'

fixes this. I am not sure if you want to allow further characters in script names like spaces or other special characters. The pull request I will create will only fix the '-' issue.

----------
components: Demos and Tools
messages: 353728
nosy: rpluem
priority: normal
severity: normal
status: open
title: pathfix.py does not find Python scripts that have '-' in its filename
type: behavior
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Wed Oct  2 05:42:07 2019
From: report at bugs.python.org (=?utf-8?b?UsO8ZGlnZXIgUGzDvG0=?=)
Date: Wed, 02 Oct 2019 09:42:07 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1570009327.48.0.143161828105.issue38347@roundup.psfhosted.org>


Change by R?diger Pl?m <r.pluem at gmx.de>:


----------
keywords: +patch
pull_requests: +16125
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16536

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Wed Oct  2 06:00:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 10:00:39 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1570010439.28.0.301310672244.issue38347@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Wed Oct  2 06:21:06 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Wed, 02 Oct 2019 10:21:06 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1570011666.3.0.547333736424.issue38006@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:

> ?ukasz, is there some reason you removed old versions (2.7, 3.6, etc)?  The bug is present on those versions of Python and it should be trivial to backport the fix.  If those branches are maintained, I think we should fix it.

Sorry, I did that by mistake.

----------
versions: +Python 2.7, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Wed Oct  2 06:47:14 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 10:47:14 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570013234.35.0.697595922647.issue36670@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16126
pull_request: https://github.com/python/cpython/pull/16537

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 07:21:40 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Wed, 02 Oct 2019 11:21:40 +0000
Subject: [issue38346] Wrong behavior when using `assert_called_with` with
 mutable object
In-Reply-To: <1570006369.69.0.450054962888.issue38346@roundup.psfhosted.org>
Message-ID: <1570015300.14.0.274328027503.issue38346@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

I don't see what the "fix" should be. Python doesn't have value semantics. Functions are called with objects, not with their values.

Imagine a was global variable, and then you say:
    a = mutable_object()
    f(a)
    a.mutate()
    f.assert_called_with(a)

In your view of the world, this should raise??

----------
nosy: +veky

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38346>
_______________________________________

From report at bugs.python.org  Wed Oct  2 07:35:27 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 11:35:27 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570016127.56.0.101538831278.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 2ea71a07d0a720707094ee55f78fd232c40724bc by Victor Stinner in branch 'master':
bpo-36670: regrtest bug fixes (GH-16537)
https://github.com/python/cpython/commit/2ea71a07d0a720707094ee55f78fd232c40724bc


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 07:35:36 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Oct 2019 11:35:36 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570016136.08.0.115257088278.issue36670@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16127
pull_request: https://github.com/python/cpython/pull/16538

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 07:54:22 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Oct 2019 11:54:22 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570017262.19.0.0264495672583.issue36670@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset a72de9338882b8013a4bb8adb930fe3308682e28 by Miss Islington (bot) in branch '3.8':
bpo-36670: regrtest bug fixes (GH-16537)
https://github.com/python/cpython/commit/a72de9338882b8013a4bb8adb930fe3308682e28


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 08:03:41 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 02 Oct 2019 12:03:41 +0000
Subject: [issue38346] Wrong behavior when using `assert_called_with` with
 mutable object
In-Reply-To: <1570006369.69.0.450054962888.issue38346@roundup.psfhosted.org>
Message-ID: <1570017821.84.0.243687275528.issue38346@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

As explained copy would cause backwards incompatible change on objects that depend on identity comparison. I am not sure if this can be fixed in a backwards compatible manner.

> One possibility would be for mock to copy the arguments you pass in. This could then cause problems if you do assertions that rely on object identity for equality.

----------
nosy: +cjw296, lisroach, mariocj89, michael.foord, xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38346>
_______________________________________

From report at bugs.python.org  Wed Oct  2 08:09:15 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 02 Oct 2019 12:09:15 +0000
Subject: [issue38346] Wrong behavior when using `assert_called_with` with
 mutable object
In-Reply-To: <1570006369.69.0.450054962888.issue38346@roundup.psfhosted.org>
Message-ID: <1570018155.37.0.973988015451.issue38346@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

See also https://bugs.python.org/issue28848

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38346>
_______________________________________

From report at bugs.python.org  Wed Oct  2 08:35:13 2019
From: report at bugs.python.org (Jason R. Coombs)
Date: Wed, 02 Oct 2019 12:35:13 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
In-Reply-To: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>
Message-ID: <1570019713.05.0.549058175543.issue38342@roundup.psfhosted.org>


Jason R. Coombs <jaraco at jaraco.com> added the comment:

I believe importlib/metadata/__init__ was moved to importlib.metadata. I?ll inspect the repo for correctness, but there may be another issue with the old files lingering.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Wed Oct  2 10:09:30 2019
From: report at bugs.python.org (Jason R. Coombs)
Date: Wed, 02 Oct 2019 14:09:30 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
In-Reply-To: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>
Message-ID: <1570025370.76.0.129600307073.issue38342@roundup.psfhosted.org>


Jason R. Coombs <jaraco at jaraco.com> added the comment:

I've confirmed that the `metadata` directory doesn't exist in the repo. It also doesn't appear on my Python 3.8.0b4 installation on macOS:

```
cpython master $ ls /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/importlib/                                               
__init__.py            _bootstrap.py          abc.py                 metadata.py            util.py
__pycache__            _bootstrap_external.py machinery.py           resources.py
cpython master $ python3.8 -V                                                                                                                
Python 3.8.0b4
```

I installed b4 clean. I also installed 3.8.0rc1 over 3.8.0b4 and everything is fine.

It's possible that installing 3.8.0b4 over 3.8.0b3 would leave the old package lingering. Can you confirm that's how 3.8.0rc1 was installed?

I've crafted this command which should correct the situation in such an environment::

python -c "import importlib.metadata, shutil, pathlib; file = pathlib.Path(importlib.metadata.__file__); str(file).endswith('__init__.py') and shutil.rmtree(file.parent) and print('removed', file.parent)"

Please give that a try and see if it corrects the condition.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Wed Oct  2 10:38:28 2019
From: report at bugs.python.org (Huyston)
Date: Wed, 02 Oct 2019 14:38:28 +0000
Subject: [issue38331] Exec not recognizing global variables inside function
In-Reply-To: <1569875978.41.0.850227388561.issue38331@roundup.psfhosted.org>
Message-ID: <1570027108.21.0.576932208055.issue38331@roundup.psfhosted.org>


Huyston <prajogaosu at gmail.com> added the comment:

Ronald Oussoren, I understand your comment and it makes sense in the module perspective.

However, when using 'exec', we are explicitly passing a globals dict (and locals) that the target code should consider.

As the documentation states:
"If globals and locals are given, they are used for the global and local variables, respectively."

In my point of view, the function is not considering the given globals and locals dict.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38331>
_______________________________________

From report at bugs.python.org  Wed Oct  2 10:39:28 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 14:39:28 +0000
Subject: [issue38319] shutil.copyfile(): os.sendfile() fails with
 OverflowError on 32-bit system
In-Reply-To: <1569829071.99.0.925566441615.issue38319@roundup.psfhosted.org>
Message-ID: <1570027168.14.0.747549270211.issue38319@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

32-bit buildbots are back to green. Thanks for the fix!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38319>
_______________________________________

From report at bugs.python.org  Wed Oct  2 10:54:08 2019
From: report at bugs.python.org (Anthony Tuininga)
Date: Wed, 02 Oct 2019 14:54:08 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
In-Reply-To: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>
Message-ID: <1570028048.88.0.232648858384.issue38342@roundup.psfhosted.org>


Anthony Tuininga <anthony.tuininga at gmail.com> added the comment:

Yes. I had tried b3 earlier, installed b4 over b3 and then rc1 over b4. Removing the cruft using the command you specified caused the problem to go away.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Wed Oct  2 10:59:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 14:59:02 +0000
Subject: [issue38338] [2.7] test_ssl fails on RHEL8
In-Reply-To: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>
Message-ID: <1570028342.03.0.0765004439207.issue38338@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16128
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16539

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Wed Oct  2 11:02:36 2019
From: report at bugs.python.org (Batuhan)
Date: Wed, 02 Oct 2019 15:02:36 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
In-Reply-To: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>
Message-ID: <1570028556.33.0.769542164168.issue38342@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

https://gitlab.com/python-devs/importlib_metadata/issues/92

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Wed Oct  2 11:14:59 2019
From: report at bugs.python.org (Batuhan)
Date: Wed, 02 Oct 2019 15:14:59 +0000
Subject: [issue38348] Make python -m ast more configurable
Message-ID: <1570029299.56.0.0303865742584.issue38348@roundup.psfhosted.org>


New submission from Batuhan <batuhanosmantaskaya at gmail.com>:

Allow user to set indent level and parsing status of type comments

----------
components: Library (Lib)
messages: 353741
nosy: BTaskaya, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Make python -m ast more configurable
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38348>
_______________________________________

From report at bugs.python.org  Wed Oct  2 11:30:45 2019
From: report at bugs.python.org (Batuhan)
Date: Wed, 02 Oct 2019 15:30:45 +0000
Subject: [issue38348] Make python -m ast more configurable
In-Reply-To: <1570029299.56.0.0303865742584.issue38348@roundup.psfhosted.org>
Message-ID: <1570030245.87.0.0171098991935.issue38348@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


----------
keywords: +patch
pull_requests: +16129
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16540

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38348>
_______________________________________

From report at bugs.python.org  Wed Oct  2 11:52:50 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 15:52:50 +0000
Subject: [issue38338] [2.7] test_ssl fails on RHEL8
In-Reply-To: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>
Message-ID: <1570031570.51.0.127577763255.issue38338@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset b3e7045f8314e7b62cd95861d207fe2f97e47198 by Victor Stinner in branch 'master':
bpo-38338, test.pythoninfo: add more ssl infos (GH-16539)
https://github.com/python/cpython/commit/b3e7045f8314e7b62cd95861d207fe2f97e47198


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Wed Oct  2 11:57:14 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Oct 2019 15:57:14 +0000
Subject: [issue38338] [2.7] test_ssl fails on RHEL8
In-Reply-To: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>
Message-ID: <1570031834.26.0.858927935342.issue38338@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16130
pull_request: https://github.com/python/cpython/pull/16541

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Wed Oct  2 11:57:24 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Oct 2019 15:57:24 +0000
Subject: [issue38338] [2.7] test_ssl fails on RHEL8
In-Reply-To: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>
Message-ID: <1570031844.15.0.458901193387.issue38338@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16131
pull_request: https://github.com/python/cpython/pull/16542

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:10:03 2019
From: report at bugs.python.org (jackotonye)
Date: Wed, 02 Oct 2019 16:10:03 +0000
Subject: [issue38349] Email example using imaginary library installation
 error. The install shows that it only supports python 2.x but is listed for
 python 3.6+
Message-ID: <1570032603.68.0.429442517445.issue38349@roundup.psfhosted.org>


New submission from jackotonye <tonyejck at gmail.com>:

https://docs.python.org/3.7/library/email.examples.html

----------
assignee: docs at python
components: Documentation
messages: 353743
nosy: docs at python, jackotonye
priority: normal
severity: normal
status: open
title: Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed for python 3.6+
type: resource usage
versions: Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38349>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:10:48 2019
From: report at bugs.python.org (jackotonye)
Date: Wed, 02 Oct 2019 16:10:48 +0000
Subject: [issue38349] Email example using imaginary library installation
 error. The install shows that it only supports python 2.x but is listed under
 python 3.6+ docs.
In-Reply-To: <1570032603.68.0.429442517445.issue38349@roundup.psfhosted.org>
Message-ID: <1570032648.53.0.366017505181.issue38349@roundup.psfhosted.org>


Change by jackotonye <tonyejck at gmail.com>:


----------
title: Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed for python 3.6+ -> Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed under python 3.6+ docs.

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38349>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:13:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 16:13:30 +0000
Subject: [issue38338] [2.7] test_ssl fails on RHEL8
In-Reply-To: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>
Message-ID: <1570032810.05.0.348309466913.issue38338@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16132
pull_request: https://github.com/python/cpython/pull/16543

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:15:00 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Oct 2019 16:15:00 +0000
Subject: [issue38338] [2.7] test_ssl fails on RHEL8
In-Reply-To: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>
Message-ID: <1570032900.29.0.723946070211.issue38338@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset ab98cd8aee5a5a7222b82ff13d61f0d33e72a889 by Miss Islington (bot) in branch '3.7':
bpo-38338, test.pythoninfo: add more ssl infos (GH-16539)
https://github.com/python/cpython/commit/ab98cd8aee5a5a7222b82ff13d61f0d33e72a889


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:20:48 2019
From: report at bugs.python.org (SilentGhost)
Date: Wed, 02 Oct 2019 16:20:48 +0000
Subject: [issue38349] Email example using imaginary library installation
 error. The install shows that it only supports python 2.x but is listed under
 python 3.6+ docs.
In-Reply-To: <1570032603.68.0.429442517445.issue38349@roundup.psfhosted.org>
Message-ID: <1570033248.3.0.655431547559.issue38349@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

imaginary in the example is not meant to refer to https://pypi.org/project/Imaginary/ it's meant to refer to a module that you could write that would do all the dirty work. Perhaps, it's not the best name to use provided there is an actual module on pypi, alternatively half-baked outdated modules could be remove.

----------
nosy: +SilentGhost

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38349>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:35:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 16:35:07 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
Message-ID: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

In Python 2.7, when using ./configure --with-pydebug, Python is built using -O0 compiler optimization level: disable all optimizations. The comment is quite explicit: "Optimization messes up debuggers, so turn it off for debug builds".

if test "$Py_DEBUG" = 'true' ; then
    # Optimization messes up debuggers, so turn it off for
    # debug builds.
    OPT="-g -O0 -Wall $STRICT_PROTO"
else
    OPT="-g $WRAP -O3 -Wall $STRICT_PROTO"
fi

In Python 3, -Og is preferred over -O0 for pydebug, if -Og is available:

if test "$Py_DEBUG" = 'true' ; then
    # Optimization messes up debuggers, so turn it off for
    # debug builds.
    if "$CC" -v --help 2>/dev/null |grep -- -Og > /dev/null; then
        OPT="-g -Og -Wall"
    else
        OPT="-g -O0 -Wall"
    fi
else
    OPT="-g $WRAP -O3 -Wall"
fi

Problem: in my experience, gdb traceback doesn't make sense sometimes, and gdb fails to inspect some function arguments and some variables which are displayed as <optimized out>.

See a very concrete example with a test_gdb failure on x86-64 when Python is compiled using gcc -Og:
https://bugzilla.redhat.com/show_bug.cgi?id=1734327#c22

My colleague who is working on gdb suggests to use -O0:
https://bugzilla.redhat.com/show_bug.cgi?id=1734327#c27

Since I started contributing to Python, I always forced gcc -O0 because any other optimization level caused me many issues in gdb. I'm using -O0 for 10 years with sucess.

The GCC documentation says "It is a better choice than -O0 for producing debuggable code because some compiler passes that collect debug information are disabled at -O0." But my experience says the opposite.

Note: instead of -g, we could use -g3 to include debug information for macros and defines.

--

I'm proposing to change the *default* compiler flags from -Og to -O0. Obviously, Linux distributions and developers are free to override the compiler optimization level. For example: ./configure --with-pydebug CFLAGS="-Og" ensures that Python is always built using -Og.

I propose to modify 3.7, 3.8 and master branches.

----------
components: Build
messages: 353746
nosy: vstinner
priority: normal
severity: normal
status: open
title: ./configure --with-pydebug should use -O0 rather than -Og
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:36:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 16:36:39 +0000
Subject: [issue38338] [2.7] test_ssl fails on RHEL8
In-Reply-To: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>
Message-ID: <1570034199.61.0.592881572984.issue38338@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 403ca7ea70232e520af18511fbfb89b58ef2a046 by Victor Stinner in branch '2.7':
[2.7] bpo-38338, test.pythoninfo: add more ssl infos (GH-16543)
https://github.com/python/cpython/commit/403ca7ea70232e520af18511fbfb89b58ef2a046


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:44:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 16:44:00 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570034640.37.0.940081739879.issue38350@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I basically propose to revert bpo-23445 change:

commit 3d6c784371bccc2407048652bce50c5bccf9b1af
Author: Antoine Pitrou <solipsis at pitrou.net>
Date:   Wed Feb 11 19:39:16 2015 +0100

    Issue #23445: pydebug builds now use "gcc -Og" where possible, to make the resulting executable faster.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:45:36 2019
From: report at bugs.python.org (Mariatta)
Date: Wed, 02 Oct 2019 16:45:36 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
Message-ID: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>


New submission from Mariatta <mariatta at python.org>:

A string was formatted with %s in the code example 

https://github.com/python/cpython/blob/b3e7045f8314e7b62cd95861d207fe2f97e47198/Doc/includes/email-simple.py#L15 

```
msg['Subject'] = 'The contents of %s' % textfile
```

It would be great to modernize that into fstring.

Doc can be read at: https://docs.python.org/3.7/library/email.examples.html

----------
assignee: docs at python
components: Documentation
keywords: easy, newcomer friendly
messages: 353749
nosy: Mariatta, docs at python
priority: normal
severity: normal
stage: needs patch
status: open
title: Modernize email example from %-formatting to f-string
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:50:41 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 16:50:41 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570035041.0.0.311026541522.issue38350@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

test_gdb is failing in different architectures and different operating systems:

* Fedora, Python 3.8, x86-64:
  https://bugzilla.redhat.com/show_bug.cgi?id=1734327

* RHEL8, Python 3.6, s390x
  https://bugzilla.redhat.com/show_bug.cgi?id=1712977

* RHEL 8, Python 3.6, ppc64le
  https://bugzilla.redhat.com/show_bug.cgi?id=1714733

I'm quite sure that most issues are caused by the compiler optimization level which is not -O0.

See also bpo-37631: the debug build of the RHEL8 package is supposed to be compiled using -O0 using EXTRA_CFLAGS variable, but -O0 in EXTRA_CFLAGS variable is overriden by -02 in CFLAGS_NODIST.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:52:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 16:52:39 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570035159.04.0.113054220447.issue38350@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16133
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16544

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:52:53 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Oct 2019 16:52:53 +0000
Subject: [issue38338] [2.7] test_ssl fails on RHEL8
In-Reply-To: <1569934554.24.0.56143952582.issue38338@roundup.psfhosted.org>
Message-ID: <1570035173.8.0.445469704288.issue38338@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 183733dfb6b4779d1a5e47f41a2fb86c6be08dda by Miss Islington (bot) in branch '3.8':
bpo-38338, test.pythoninfo: add more ssl infos (GH-16539)
https://github.com/python/cpython/commit/183733dfb6b4779d1a5e47f41a2fb86c6be08dda


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38338>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:56:27 2019
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 02 Oct 2019 16:56:27 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
In-Reply-To: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>
Message-ID: <1570035387.86.0.966292679854.issue38342@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

Closing as not a bug as this seems to be an issue from installing over a b3 or earlier build where the importlib/metadata/ directory gets left behind and thus take priority in import over importlib/metadata.py.

----------
nosy: +brett.cannon
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:56:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 16:56:56 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570035416.22.0.207101919996.issue38350@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

My use case is to debug a crash using a Python compiled in debug module, like python3-debug program in Fedora. Since the debug ABI is now compatible with the release build, the idea is to attempt to reproduce a crash in gdb using python3-debug instead of python3, and then use gdb to see what's going on.

With -Og, the call stack is wrong sometimes, and some function arguments and local variables cannot be read (displayed as <optimized out>).

On Travis CI, a few months ago, Python was built in debug mode using -O3. But it was a side effect of OpenSSL flags if I recall correctly.

With my PR 16544, Travis CI now uses -O0.

----------
nosy: +pablogsal, pitrou, serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Wed Oct  2 12:57:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 16:57:46 +0000
Subject: [issue23445] Use -Og for debug builds
In-Reply-To: <1423672122.39.0.391181135666.issue23445@psf.upfronthosting.co.za>
Message-ID: <1570035466.44.0.0435784036698.issue23445@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I created bpo-38350 to propose to revert this change.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23445>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:01:04 2019
From: report at bugs.python.org (jackotonye)
Date: Wed, 02 Oct 2019 17:01:04 +0000
Subject: [issue38349] Email example using imaginary library installation
 error. The install shows that it only supports python 2.x but is listed under
 python 3.6+ docs.
In-Reply-To: <1570033248.3.0.655431547559.issue38349@roundup.psfhosted.org>
Message-ID: <CA+O3LwAmJysjECQ-b-r6wTrOeZZw7229gHFrYF1_jRuwwB3-tQ@mail.gmail.com>


jackotonye <tonyejck at gmail.com> added the comment:

Might be best to make it a little more obvious since most examples are
considered executable code. That would require little modification.

On Wed, Oct 2, 2019 at 12:20 PM SilentGhost <report at bugs.python.org> wrote:

>
> SilentGhost <ghost.adh at runbox.com> added the comment:
>
> imaginary in the example is not meant to refer to
> https://pypi.org/project/Imaginary/ it's meant to refer to a module that
> you could write that would do all the dirty work. Perhaps, it's not the
> best name to use provided there is an actual module on pypi, alternatively
> half-baked outdated modules could be remove.
>
> ----------
> nosy: +SilentGhost
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue38349>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38349>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:21:58 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 02 Oct 2019 17:21:58 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1570036918.11.0.562301326934.issue38344@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Should be a straightforward fix (replace the "else" with "if not defined..."), but since it slipped through testing we probably want a regression test in test_venv as well.

(+RM for the 3.8 regression)

----------
keywords: +3.8regression
nosy: +lukasz.langa
priority: normal -> release blocker
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:25:51 2019
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Wed, 02 Oct 2019 17:25:51 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570037151.33.0.751619941683.issue38351@roundup.psfhosted.org>


Fred L. Drake, Jr. <fdrake at gmail.com> added the comment:

Does it make sense to change just one example?

I'm not sure what the long-term stance is on whether %-formatting should be replaced at this point, but shouldn't this be a matter of which string formatting approach we want overall, rather than adjusting only specific examples?

----------
nosy: +fdrake

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:33:10 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 02 Oct 2019 17:33:10 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1570037589.99.0.672362950548.issue38344@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Adding this to the end of test_unicode_in_batch_file seems to be sufficient to cause the test to fail:

        self.assertEqual(err.strip(), '')

Potentially we should add that additional check throughout this test module, but I don't think that's needed for a post-RC fix.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:42:26 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Oct 2019 17:42:26 +0000
Subject: [issue22214] Tkinter: Don't stringify callback arguments
In-Reply-To: <1408285449.26.0.836464630135.issue22214@psf.upfronthosting.co.za>
Message-ID: <1570038146.5.0.215528016276.issue22214@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16134
pull_request: https://github.com/python/cpython/pull/16545

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22214>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:46:24 2019
From: report at bugs.python.org (Sanjay)
Date: Wed, 02 Oct 2019 17:46:24 +0000
Subject: [issue38335] simplify overlaps function in ipaddress.py
In-Reply-To: <1569930223.76.0.865877463422.issue38335@roundup.psfhosted.org>
Message-ID: <1570038384.95.0.284111190914.issue38335@roundup.psfhosted.org>


Change by Sanjay <sanjay537 at gmail.com>:


----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38335>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:52:38 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Oct 2019 17:52:38 +0000
Subject: [issue22214] Tkinter: Don't stringify callback arguments
In-Reply-To: <1408285449.26.0.836464630135.issue22214@psf.upfronthosting.co.za>
Message-ID: <1570038758.46.0.805351426298.issue22214@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

PR 16545 solves the problem by using OS specific methods for converting between Python and Tcl strings. It is not ideal, but is good enough for most real cases.

Now you can paste, copy and print non-BMP characters. The code containing them can be displayed weird, but the result of print looks OK.

>>> '\N{PERSONAL COMPUTER}'
'?'
>>> print('?')
?

As a side effect, printing '\udcf0\udc9f\udc90\udc8d' on Linux and '\ud83d\udcbb' on Windows should have the same effect as printing '\U0001f4bb'.

I do not know about macOS, but expect the same behavior as on Linux. Could anybody test please?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22214>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:52:50 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Oct 2019 17:52:50 +0000
Subject: [issue22214] Tkinter: Don't stringify callback arguments
In-Reply-To: <1408285449.26.0.836464630135.issue22214@psf.upfronthosting.co.za>
Message-ID: <1570038769.99.0.158704123262.issue22214@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
versions: +Python 3.7, Python 3.8, Python 3.9 -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22214>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:54:03 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Oct 2019 17:54:03 +0000
Subject: [issue22214] Tkinter: Don't stringify callback arguments
In-Reply-To: <1408285449.26.0.836464630135.issue22214@psf.upfronthosting.co.za>
Message-ID: <1570038843.97.0.0389369664172.issue22214@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Oops, it is better to attach it to issue13153.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22214>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:56:02 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Oct 2019 17:56:02 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570038962.59.0.941567054335.issue13153@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

PR 16545 solves the problem by using OS specific methods for converting between Python and Tcl strings. It is not ideal, but is good enough for most real cases.

Now you can paste, copy and print non-BMP characters. The code containing them can be displayed weird, but the result of print looks OK.

>>> '\N{PERSONAL COMPUTER}'
'?'
>>> print('?')
?

As a side effect, printing '\udcf0\udc9f\udc90\udc8d' on Linux and '\ud83d\udcbb' on Windows should have the same effect as printing '\U0001f4bb'.

I do not know about macOS, but expect the same behavior as on Linux. Could anybody test please?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:56:20 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Oct 2019 17:56:20 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570038980.64.0.849130134086.issue13153@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16135
pull_request: https://github.com/python/cpython/pull/16545

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:57:21 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Oct 2019 17:57:21 +0000
Subject: [issue22214] Tkinter: Don't stringify callback arguments
In-Reply-To: <1408285449.26.0.836464630135.issue22214@psf.upfronthosting.co.za>
Message-ID: <1570039041.61.0.67305059139.issue22214@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
Removed message: https://bugs.python.org/msg353759

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22214>
_______________________________________

From report at bugs.python.org  Wed Oct  2 13:57:31 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Oct 2019 17:57:31 +0000
Subject: [issue22214] Tkinter: Don't stringify callback arguments
In-Reply-To: <1408285449.26.0.836464630135.issue22214@psf.upfronthosting.co.za>
Message-ID: <1570039051.82.0.795977732951.issue22214@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
Removed message: https://bugs.python.org/msg353760

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22214>
_______________________________________

From report at bugs.python.org  Wed Oct  2 14:16:12 2019
From: report at bugs.python.org (Mariatta)
Date: Wed, 02 Oct 2019 18:16:12 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570040172.91.0.275441813932.issue38351@roundup.psfhosted.org>


Mariatta <mariatta at python.org> added the comment:

I think updating one isolated code example is less invasive and easier to review, instead of one big PR to change everything from "%s" to str.format or f-string.

I brought up this example code merely because I happen to be reading this page.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 14:31:17 2019
From: report at bugs.python.org (Karl Kornel)
Date: Wed, 02 Oct 2019 18:31:17 +0000
Subject: [issue38352] In typing docs,
 note explicit import needed for IO and Pattern/Match
Message-ID: <1570041077.58.0.399304866649.issue38352@roundup.psfhosted.org>


New submission from Karl Kornel <karl at kornel.us>:

Hello!

In https://github.com/python/cpython/blob/master/Lib/typing.py#L115-L117, there is a note about the io and re classes not being included in typing.__all__.  I am a relatively new user of typing, and I did `from typing import *` in my code.  I ran the code through mypy first, which reported no problems, but then running Python 3.6 failed with a NameError (name 'IO' is not defined).

Reading through the typing source, it's clear that this was an intentional decision.  So, instead of reporting a bug, I'd like to request a documentation enhancement!

The docs for typing make no mention of typing.io or typing.re.  So, my request is: In the sections for the IO/TextIO/BinaryIO and Pattern/Match classes, include text warning the user that these types are not imported when you do `from typing import *`.

----------
assignee: docs at python
components: Documentation
messages: 353763
nosy: Karl Kornel, docs at python
priority: normal
severity: normal
status: open
title: In typing docs, note explicit import needed for IO and Pattern/Match
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38352>
_______________________________________

From report at bugs.python.org  Wed Oct  2 14:42:40 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 02 Oct 2019 18:42:40 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1570041760.75.0.0138449473932.issue38344@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Also adding Ned - this made it into 3.7 as well.

----------
nosy: +ned.deily
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Wed Oct  2 14:52:54 2019
From: report at bugs.python.org (Tal Einat)
Date: Wed, 02 Oct 2019 18:52:54 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570042374.73.0.610315182816.issue13153@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

Serhiy, this looks like a great step in the right direction!

Tested on Win10 with PR GH-16545 (commit f4db0e7e00). Here is a copy/paste from an IDLE shell session:

>>> '\N{PERSONAL COMPUTER}'
'????'
>>> print('?')
SyntaxError: 'utf-8' codec can't encode characters in position 7-12: surrogates not allowed

Note that in the first output, the second and third chars in the string aren't visible in IDLE; i.e. what is actually displayed is '??'.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Wed Oct  2 16:04:04 2019
From: report at bugs.python.org (Tal Einat)
Date: Wed, 02 Oct 2019 20:04:04 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570046644.21.0.616309770175.issue13153@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

Not sure if this helps, but a bit of experimentation brought this up:

>>> '\N{PERSONAL COMPUTER}'.encode('utf-8')
b'\xf0\x9f\x92\xbb'
>>> '????'.encode('utf-16le')
b'\xf0\x00\x9f\x00\x92\x00\xbb\x00'
>>> '????'.encode('utf-16')
b'\xff\xfe\xf0\x00\x9f\x00\x92\x00\xbb\x00'

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Wed Oct  2 16:18:16 2019
From: report at bugs.python.org (Tal Einat)
Date: Wed, 02 Oct 2019 20:18:16 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570047496.92.0.067338209661.issue13153@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

More info:

>>> '\N{PERSONAL COMPUTER}'.encode('utf-8').decode('latin-1') == '????'
True

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Wed Oct  2 16:33:50 2019
From: report at bugs.python.org (David Bolen)
Date: Wed, 02 Oct 2019 20:33:50 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570048430.18.0.746810899129.issue36670@roundup.psfhosted.org>


David Bolen <db3l.net at gmail.com> added the comment:

Just an FYI that this change is generating warnings on my Windows 10 buildbot with some regularity about a failure to parse testperf output, such as:

Warning -- Failed to parse typeperf output: '"10/01/2019 07:58:50.056"'

from https://buildbot.python.org/all/#/builders/217/builds/487

Now, clearly there's no queue length in that output so the parsing warning is accurate, but does the overall build have to reflect a warning in such cases, given that it's just a test harness issue, and not anything going wrong with the actual tests?  Previously any such cases would be ignored silently, so this probably isn't a new issue but just one that is now shows up as an overall build warning.

I don't know why both fields aren't present although it seems plausible that it's just a partial line from the I/O (I don't think it guarantees it receives full lines), and the queue length field would appear on the following read.

----------
nosy: +db3l

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 16:51:07 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Oct 2019 20:51:07 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570049467.15.0.751933405772.issue13153@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Sorry, I did not test the last version on Windows. There was a bug which caused using the Linux version on Windows. Now it should be fixed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Wed Oct  2 16:54:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 20:54:00 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570049640.15.0.65277481426.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Just an FYI that this change is generating warnings on my Windows 10 buildbot with some regularity about a failure to parse testperf output, such as:

Warning -- Failed to parse typeperf output: '"10/01/2019 07:58:50.056"'

Aha, interesting. I added a warning to debug the code.

> Now, clearly there's no queue length in that output so the parsing warning is accurate, but does the overall build have to reflect a warning in such cases, given that it's just a test harness issue, and not anything going wrong with the actual tests?

The build is marked as "warning" (orange) which is different than "fail" (red). Warnings are used to detect bugs or interesting issues, but not considered as a regression.

> I don't know why both fields aren't present although it seems plausible that it's just a partial line from the I/O (I don't think it guarantees it receives full lines), and the queue length field would appear on the following read.

Right, the code doesn't ensure that a line ends with a newline character. Could you try to run manually the following command to check its output?

   typeperf "\System\Processor Queue Length" -si 1

Maybe uncomplete lines should be buffered in read_output().

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 17:04:37 2019
From: report at bugs.python.org (Matej Cepl)
Date: Wed, 02 Oct 2019 21:04:37 +0000
Subject: [issue38014] Python 3.7 does not compile
In-Reply-To: <1567477987.66.0.578307493025.issue38014@roundup.psfhosted.org>
Message-ID: <1570050277.02.0.990512930834.issue38014@roundup.psfhosted.org>


Matej Cepl <mcepl at cepl.eu> added the comment:

Isn?t https://bugzilla.suse.com/1152793 (removal of stropts.h from glibc) cause of this?

----------
nosy: +mcepl

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38014>
_______________________________________

From report at bugs.python.org  Wed Oct  2 17:05:46 2019
From: report at bugs.python.org (David Bolen)
Date: Wed, 02 Oct 2019 21:05:46 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570050346.04.0.29744272019.issue36670@roundup.psfhosted.org>


David Bolen <db3l.net at gmail.com> added the comment:

Oh, I agree it's just a warning, and I suspect few people look into warnings, but since it's not from an actual test, I'm not sure the overall build should be flagged.

The manual typeperf looks fine, but there's no way I could tell visually how the I/O is being done under the covers.  My bet is typeperf is probably issuing multiple output calls, one for the leading timestamp and then one for each value.  So regrtest just happens to interleave its own read in between the two.  The subsequent read would then get the trailing ",####" which the current code would parse normally as it only cares about the second field.  In which case it's not even affecting the load monitoring, other than the warning message.

I suspect it's happening on the Windows 10 buildbot as the machine is reasonably fast.  But to your earlier comment about things just working previously, I'm not sure there's that much value in adding code to deal with this case.

I'd probably just remove the warning to restore the earlier behavior.  The current code still ignores other issues like an actual read failure in read_output.  Or, if there's a way to generate the message without it being considered an overall test build warning, that would work too.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 17:06:23 2019
From: report at bugs.python.org (Matej Cepl)
Date: Wed, 02 Oct 2019 21:06:23 +0000
Subject: [issue38014] Python 3.7 does not compile
In-Reply-To: <1567477987.66.0.578307493025.issue38014@roundup.psfhosted.org>
Message-ID: <1570050383.23.0.655027073827.issue38014@roundup.psfhosted.org>


Matej Cepl <mcepl at cepl.eu> added the comment:

Sorry, got confused. My openSUSE bug has nothing to do with it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38014>
_______________________________________

From report at bugs.python.org  Wed Oct  2 17:12:43 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 21:12:43 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
Message-ID: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

Place holder issue for changes related to path configuration cleanup changes (Modules/getpath.c).

----------
components: Interpreter Core
messages: 353774
nosy: vstinner
priority: normal
severity: normal
status: open
title: Cleanup the path configuration implementation code (getpath.c)
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Wed Oct  2 17:13:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 21:13:00 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570050780.81.0.805395298563.issue38353@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16136
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16548

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Wed Oct  2 17:32:12 2019
From: report at bugs.python.org (Enji Cooper)
Date: Wed, 02 Oct 2019 21:32:12 +0000
Subject: [issue38354] Fix for bug 30378 regressed SysLogHandler
Message-ID: <1570051932.55.0.313239800858.issue38354@roundup.psfhosted.org>


New submission from Enji Cooper <yaneurabeya at gmail.com>:

The change made for bug 30378 caused a regression in our code by making
lookups for SysLogHandler addresses at init time, instead of making them more lazy. Example:

>>> import logging.handlers
>>> LOGGER = logging.getLogger("logger")
>>> LOGGER.addHandler(logging.handlers.SysLogHandler(address=('resolvessometimesbutnotthefirsttime.com', logging.handlers.SYSLOG_UDP_PORT)))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python2.7/logging/handlers.py", line 767, in __init__
    ress = socket.getaddrinfo(host, port, 0, socktype)
socket.gaierror: [Errno -2] Name or service not known

This is exacerbated by the fact that a lot of code the organization I work for (and to be honest, I have written in the past) initializes global loggers once at import time. If the SysLogHandler is added to the global logger and the DNS resolution isn't possible (/etc/hosts is empty on Unix or does not contain the entry, and DNS out is to lunch), it will fall on its face at initialization time.

There needs to be a more graceful way of initializing loggers like this, or a way of delaying the host resolution, so it fails gracefully and doesn't crash the entire program (restoring the previous behavior).

Example: SMTPHandler doesn't do name resolution until it calls emit, which seems like a much more logical place to do the operation (especially since DNS records can change or become invalid).

----------
components: Library (Lib)
messages: 353775
nosy: calcheng, ngie
priority: normal
severity: normal
status: open
title: Fix for bug 30378 regressed SysLogHandler
type: crash
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38354>
_______________________________________

From report at bugs.python.org  Wed Oct  2 17:32:35 2019
From: report at bugs.python.org (Enji Cooper)
Date: Wed, 02 Oct 2019 21:32:35 +0000
Subject: [issue38354] Fix for bug 30378 regressed SysLogHandler by making it
 resolve addresses at initialization instead of in `.emit()`
In-Reply-To: <1570051932.55.0.313239800858.issue38354@roundup.psfhosted.org>
Message-ID: <1570051955.97.0.939565525109.issue38354@roundup.psfhosted.org>


Change by Enji Cooper <yaneurabeya at gmail.com>:


----------
title: Fix for bug 30378 regressed SysLogHandler -> Fix for bug 30378 regressed SysLogHandler by making it resolve addresses at initialization instead of in `.emit()`

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38354>
_______________________________________

From report at bugs.python.org  Wed Oct  2 17:42:35 2019
From: report at bugs.python.org (paul rubin)
Date: Wed, 02 Oct 2019 21:42:35 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570052555.9.0.591966850606.issue38333@roundup.psfhosted.org>


paul rubin <phr-pythonbugs at nightsong.com> added the comment:

Yes, the suggestion was just for the docs, and since those are intended for human rather than machine consumption, it's fine if there are some blurry cases where there is no signature.  Ideally in those cases, the issue should be explained in the doc text.

I actually don't see what's wrong with including signatures in the source code as well, as long as doing so doesn't break anyone's existing code.  I agree with Veky that one should be very hesitant about breaking existing working code, even if that code relies on undocumented behavior.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Wed Oct  2 17:51:29 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 21:51:29 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570053089.15.0.317455607901.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 61691d833631fed42b86605b09e1535e3e8d40e5 by Victor Stinner in branch 'master':
bpo-38353: Cleanup includes in the internal C API (GH-16548)
https://github.com/python/cpython/commit/61691d833631fed42b86605b09e1535e3e8d40e5


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Wed Oct  2 17:53:10 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 21:53:10 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570053190.89.0.417433331426.issue38353@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16137
pull_request: https://github.com/python/cpython/pull/16549

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:13:00 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 02 Oct 2019 22:13:00 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570054380.69.0.49203887201.issue38333@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

@phr

To be clear, I agree that there's nothing wrong with adding signatures to docs. We just need to find a way to do it. There will definitely be some cases where it's better not to have a type rather than trying to spell out the actual type in the docs.

My "unacceptable" comment was meant in response to Vedran's suggestion that it would be okay to lie in the docs about the signature for sum(). If the truth is too subtle to use a specific type signature we should keep the words. (The words for sum() are actually pretty clear.)

FWIW: My objection against vague docs was specifically about situations where the word "string" is used without clarifying if this allows bytes. I've also seen docs that were even more vague, e.g. "a name" or "a filename".

Signatures in the code won't "break" the code (they are ignored at runtime) but if present they should nevertheless be precise since they will be used by type checkers. Signatures in code are *not* just documentation. Only in very limited situations would I be okay with lies in signatures -- this would have to be done on a case by case basis.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:14:19 2019
From: report at bugs.python.org (David Bolen)
Date: Wed, 02 Oct 2019 22:14:19 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570054459.13.0.0669928774781.issue36670@roundup.psfhosted.org>


David Bolen <db3l.net at gmail.com> added the comment:

I've confirmed the partial read with some local modifications, and the failures are always split between time stamp and value:

Warning -- Failed to parse typeperf output: '"10/02/2019 17:42:26.229"'
0.0
Warning -- Missing first field: ,"0.000000"
0.0

Adding multiple variables to the typeperf command can vary the split position, but I've only seen it at a variable boundary (starting with the comma).  So I'm guessing with the current implementation the above is probably the only point where the I/Os can be interleaved.

Also, CRLF seems to only appear at the start of each read, never at the end.  You can see that behavior interactively too where the cursor waits at the end of the line between samples.  So changes to wait for a complete line to be read would also delay load values by one sample interval.

So I'm thinking just reverting to silently ignoring this case is probably simplest.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:15:33 2019
From: report at bugs.python.org (Enji Cooper)
Date: Wed, 02 Oct 2019 22:15:33 +0000
Subject: [issue38354] Fix for bug 30378 regressed SysLogHandler by making it
 resolve addresses at initialization instead of in `.emit()`
In-Reply-To: <1570051932.55.0.313239800858.issue38354@roundup.psfhosted.org>
Message-ID: <1570054533.82.0.719604100062.issue38354@roundup.psfhosted.org>


Enji Cooper <yaneurabeya at gmail.com> added the comment:

Capturing more context here, based on internal discussion: other handlers are doing address resolution in `emit()` (HTTPHandler, SMTPHandler), which is expensive. In order for SysLogHandler to not regress behavior and not become expensive, performance-wise, it would probably be best to use `functools.lru_cache()`, using the address and a timeout as the key when resolving the addresses to avoid always doing address resolutions, e.g., DNS lookups: https://docs.python.org/3/library/functools.html#functools.lru_cache .

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38354>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:24:47 2019
From: report at bugs.python.org (Charalampos Stratakis)
Date: Wed, 02 Oct 2019 22:24:47 +0000
Subject: [issue37631] EXTRA_CFLAGS get overrided by CFLAGS_NODIST
In-Reply-To: <1563536952.58.0.764226132067.issue37631@roundup.psfhosted.org>
Message-ID: <1570055087.82.0.0469581998003.issue37631@roundup.psfhosted.org>


Charalampos Stratakis <cstratak at redhat.com> added the comment:

Dug a bit further here.

The issue is that CFLAGS_NODIST will always come after normal CFLAGS (which are subsets of PY_CFLAGS and PY_CFLAGS_NODIST) [0][1].

The EXTRA_CFLAGS variable is appended at the end of PY_CFLAGS [2], hence as reported here, whatever compiler flag comes after, embedded within PY_CFLAGS_NODIST, will override the previous flags if they contradict each other.

So basically EXTRA_CFLAGS can be used only for flags that can't be overwritten by PY_CFLAGS_NODIST, which in my opinion, is not very useful in the context of just adding extra flags.

Commit adding the variable to Python 2.5: https://github.com/python/cpython/commit/08cd598c2145d00f1517c93cabf80a5d7d2a4bc0

"EXTRA_CFLAGS has been introduced as an environment variable to hold compiler flags that change binary compatibility"

Apparently it was added in order to avoid using the OPT variable for the various debug builds described in https://github.com/python/cpython/blob/master/Misc/SpecialBuilds.txt

On another note this flag will get passed down to distutils, so if it was used for building the interpreter, C extensions compiled by users will also inherit it.

Honestly I am not sure what the best solution would be here. If the various sub-debug special builds are still relevant and they stack, by doing for example $ make CFLAGS_NODIST="-DPy_TRACE_REFS" EXTRA_CFLAGS="-DPy_REF_DEBUG" then the issue can be closed, and the documentation can be more explicit that the EXTRA_CFLAGS is to be used only for the special builds.

If the EXTRA_CFLAGS can also be used for adding our own flags, then the flag handling needs to change to take this into account.

[0] https://github.com/python/cpython/blob/master/setup.py#L85
[1] https://github.com/python/cpython/blob/master/Makefile.pre.in#L115
[2] https://github.com/python/cpython/blob/master/Makefile.pre.in#L97

----------
nosy: +brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37631>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:37:37 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 02 Oct 2019 22:37:37 +0000
Subject: [issue38355] ntpath.realpath() fails on sys.executable
Message-ID: <1570055857.28.0.434394542652.issue38355@roundup.psfhosted.org>


New submission from Steve Dower <steve.dower at python.org>:

The change to error handling did not include ERROR_CANT_ACCESS_FILE, but this error occurs in the Store package install.

After suppressing this error, it then occurs again when stripping the prefix - we should just check for the same error here to determine whether it's safe to remove the prefix of a file we can't access.

----------
assignee: steve.dower
components: Windows
keywords: 3.8regression
messages: 353782
nosy: lukasz.langa, paul.moore, steve.dower, tim.golden, zach.ware
priority: release blocker
severity: normal
status: open
title: ntpath.realpath() fails on sys.executable
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38355>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:40:41 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 22:40:41 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570056041.18.0.773812445806.issue36670@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16138
pull_request: https://github.com/python/cpython/pull/16550

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:41:37 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 02 Oct 2019 22:41:37 +0000
Subject: [issue38355] ntpath.realpath() fails on sys.executable
In-Reply-To: <1570055857.28.0.434394542652.issue38355@roundup.psfhosted.org>
Message-ID: <1570056097.18.0.93662176026.issue38355@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords: +patch
pull_requests: +16139
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16551

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38355>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:41:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 22:41:56 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570056116.84.0.389273045594.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Ok, I managed to reproduce the bug using this change:

diff --git a/Lib/test/libregrtest/win_utils.py b/Lib/test/libregrtest/win_utils.py
index f0c17b906f..78429faa89 100644
--- a/Lib/test/libregrtest/win_utils.py
+++ b/Lib/test/libregrtest/win_utils.py
@@ -14,7 +14,7 @@ BUFSIZE = 8192
 LOAD_FACTOR_1 = 0.9200444146293232478931553241
 
 # Seconds per measurement
-SAMPLING_INTERVAL = 5
+SAMPLING_INTERVAL = 0
 # Windows registry subkey of HKEY_LOCAL_MACHINE where the counter names
 # of typeperf are registered
 COUNTER_REGISTRY_KEY = (r"SOFTWARE\Microsoft\Windows NT\CurrentVersion"


I wrote PR 16550 to handle partial lines.

----------
resolution: fixed -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:53:01 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 22:53:01 +0000
Subject: [issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks
 threads
Message-ID: <1570056781.39.0.894014377654.issue38356@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

Warning seen o AMD64 Ubuntu Shared 3.x buildbot:
https://buildbot.python.org/all/#/builders/141/builds/2593

test_devnull_output (test.test_a=syncio.test_subprocess.SubprocessThreadedWatcherTests) ...
Warning -- threading_cleanup() failed to cleanup 1 threads (count: 1, dangling: 2)

The ThreadedChildWatcher class of asyncio.unix_events doesn't seem to have a method to join all threads. It should be done in tests to prevent "leaking" threads which can have side effects on following tests.

----------
components: Tests, asyncio
messages: 353784
nosy: asvetlov, vstinner, yselivanov
priority: normal
severity: normal
status: open
title: test_asyncio: SubprocessThreadedWatcherTests leaks threads
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38356>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:53:10 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 22:53:10 +0000
Subject: [issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks
 threads
In-Reply-To: <1570056781.39.0.894014377654.issue38356@roundup.psfhosted.org>
Message-ID: <1570056790.56.0.0964253285658.issue38356@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38356>
_______________________________________

From report at bugs.python.org  Wed Oct  2 18:53:55 2019
From: report at bugs.python.org (Charalampos Stratakis)
Date: Wed, 02 Oct 2019 22:53:55 +0000
Subject: [issue37631] EXTRA_CFLAGS get overrided by CFLAGS_NODIST
In-Reply-To: <1563536952.58.0.764226132067.issue37631@roundup.psfhosted.org>
Message-ID: <1570056835.9.0.615417971958.issue37631@roundup.psfhosted.org>


Charalampos Stratakis <cstratak at redhat.com> added the comment:

Also this is due to an expected behaviour from gcc. From the documentation:

"If you use multiple -O options, with or without level numbers, the last such option is the one that is effective. "

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37631>
_______________________________________

From report at bugs.python.org  Wed Oct  2 19:04:12 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 02 Oct 2019 23:04:12 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570057452.74.0.0879032904856.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 3e04cd268ee9a57f95dc78d8974b21a6fac3f666 by Victor Stinner in branch 'master':
bpo-36670, regrtest: Fix WindowsLoadTracker() for partial line (GH-16550)
https://github.com/python/cpython/commit/3e04cd268ee9a57f95dc78d8974b21a6fac3f666


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Wed Oct  2 19:17:19 2019
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Wed, 02 Oct 2019 23:17:19 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570058239.75.0.52131467203.issue38351@roundup.psfhosted.org>


Fred L. Drake, Jr. <fdrake at gmail.com> added the comment:

I agree that it's less invasive and easier to review.

My question (and it's just that) is whether we've made a decision to prefer one formatting syntax over others (outside of examples discussing the formatting approaches themselves).

If a decision is made to prefer one over others, it's worth making that decision separately, and then using separate PRs to deal with updates to different parts of the docs.

Added Julien Palard to the issue; I'd value input on this.

----------
nosy: +JulienPalard

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 19:56:23 2019
From: report at bugs.python.org (Michael Everitt)
Date: Wed, 02 Oct 2019 23:56:23 +0000
Subject: [issue38318] Issues linking with ncurses and tinfo (cannot resolve
 symbols)
In-Reply-To: <1569809156.07.0.948937719189.issue38318@roundup.psfhosted.org>
Message-ID: <1570060583.69.0.680364522951.issue38318@roundup.psfhosted.org>


Michael Everitt <michael at 2e0cer.net> added the comment:

Attached patch seems to fix build failure for python2.7 with uclibc-ng.

----------
keywords: +patch
Added file: https://bugs.python.org/file48639/fix-tinfo-probably-python-2_7.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38318>
_______________________________________

From report at bugs.python.org  Wed Oct  2 19:57:38 2019
From: report at bugs.python.org (Michael Everitt)
Date: Wed, 02 Oct 2019 23:57:38 +0000
Subject: [issue38318] Issues linking with ncurses and tinfo (cannot resolve
 symbols)
In-Reply-To: <1569809156.07.0.948937719189.issue38318@roundup.psfhosted.org>
Message-ID: <1570060658.64.0.971295342456.issue38318@roundup.psfhosted.org>


Michael Everitt <michael at 2e0cer.net> added the comment:

Attached patch seems to fix build with python3.6 withh uclibc-ng.

Tested on x86_64 and ARMv6zk.

----------
Added file: https://bugs.python.org/file48640/fix-tinfo-probably-python-3_6.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38318>
_______________________________________

From report at bugs.python.org  Wed Oct  2 20:06:08 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 03 Oct 2019 00:06:08 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570061168.19.0.184707835611.issue38351@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

Welcome back from the OOOS break Mariatta!

> My question (and it's just that) is whether we've made a decision to prefer one formatting syntax over others (outside of examples discussing the formatting approaches themselves).

I agree that we should reach a consensus on the preferred string formatting style. However, there seems to be two separate questions here:

1) Should the code examples in the docs be updated to use f-strings?

2) Should ALL instances of the old string formatting be updated to use f-strings? This would affect every *.py; potentially leading to additional code churn, which adds clutter to the commit logs and git blame.

The first one is far less costly and has very minimal risk of breakage. The cost of updating every *.py to use f-strings is worth considering, but is significantly higher and has more potential consequences, especially for the regression tests. I'm personally in favor of updating the code examples first and discussing the second question in a python-dev thread due to the wide impact.

> If a decision is made to prefer one over others, it's worth making that decision separately, and then using separate PRs to deal with updates to different parts of the docs.

Once we reach a decision on the matter, I think this particular issue could serve as a great first PR for a new contributor to become familiar with the workflow, so it would be a good candidate for the "newcomer friendly" label. Most python users are well acquainted with string formatting. I wouldn't mind opening a PR to fix it myself, but I think that leaving it open for a new contributor to work on as an intro to the workflow would be far more beneficial.

Although there may be a benefit to use f-strings instead here, there's certainly no rush to have it completed in a short period of time. I would be in favor of having each PR address a single documentation file. This would help accelerate the review process and provide a valuable learning experience to a greater number of new contributors, in comparison to a single PR that updates every single code example in the docs.

----------
nosy: +aeros167

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 20:10:47 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 03 Oct 2019 00:10:47 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570061447.61.0.464026766837.issue38351@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> so it would be a good candidate for the "newcomer friendly" label

Never mind, just noticed this was already labeled as newcomer friendly. I only saw the "easy" label at first. (:

If consensus is reached for this, we can open a separate issue for addressing the other doc files, something along the lines of "Update code examples to use f-strings". As mentioned earlier I think it would be worth having each new contributor update all of the instances in a single *.rst in a PR, but it can be a single issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 20:12:54 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 03 Oct 2019 00:12:54 +0000
Subject: [issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks
 threads
In-Reply-To: <1570056781.39.0.894014377654.issue38356@roundup.psfhosted.org>
Message-ID: <1570061574.38.0.922265425663.issue38356@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

I can try to work on fixing this.

----------
nosy: +aeros167

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38356>
_______________________________________

From report at bugs.python.org  Wed Oct  2 20:47:56 2019
From: report at bugs.python.org (karl)
Date: Thu, 03 Oct 2019 00:47:56 +0000
Subject: [issue19683] test_minidom has many empty tests
In-Reply-To: <1385047059.66.0.790496754317.issue19683@psf.upfronthosting.co.za>
Message-ID: <1570063676.44.0.221790770593.issue19683@roundup.psfhosted.org>


karl <karl+pythonbugs at la-grange.net> added the comment:

@zach.ware
@r.david.murray


So I was looking at that issue. There is a lot of work. 

I had a couple of questions, because there are different categories


# Empty tests for existing functions.

This seems to be straightforward as they would complete the module.

Example:
```python
def testGetAttributeNode(self): pass
```
https://github.com/python/cpython/blob/3e04cd268ee9a57f95dc78d8974b21a6fac3f666/Lib/test/test_minidom.py#L412

which refers to: `GetAttributeNode`
https://github.com/python/cpython/blob/3e04cd268ee9a57f95dc78d8974b21a6fac3f666/Lib/xml/dom/minidom.py#L765-L768
https://github.com/python/cpython/blob/3e04cd268ee9a57f95dc78d8974b21a6fac3f666/Lib/test/test_minidom.py#L285-L294



# Tests without any logical reference in the module.

This is puzzling because I'm not sure which DOM feature they should be testing.

For example:

```
    def testGetAttrList(self):
        pass
```

https://github.com/python/cpython/blob/3e04cd268ee9a57f95dc78d8974b21a6fac3f666/Lib/test/test_minidom.py#L383-L384


Or maybe this is just supposed to test Element.attributes returning a list of attributes, such as 
`NamedNodeMap [ def="ghi", jkl="mno"]` returned by a browser.


```
>>> import xml.dom.minidom
>>> from xml.dom.minidom import parse, Node, Document, parseString
>>> from xml.dom.minidom import getDOMImplementation
>>> dom = parseString("<abc/>")
>>> el = dom.documentElement
>>> el.setAttribute("def", "ghi")
>>> el.setAttribute("jkl", "mno")
>>> el.attributes
<xml.dom.minidom.NamedNodeMap object at 0x10b6d6780>
```

or is it supposed to test something like 

```
>>> el.attributes.items()
[('def', 'ghi'), ('jkl', 'mno')]
```

This is slightly confusing. And the missing docstrings are not making it easier.



# Tests which do not really test the module(?)

I think for example about this, which is testing that `del` is working, but it doesn't have anything to do with the DOM. 

```
    def testDeleteAttr(self):
        dom = Document()
        child = dom.appendChild(dom.createElement("abc"))

        self.confirm(len(child.attributes) == 0)
        child.setAttribute("def", "ghi")
        self.confirm(len(child.attributes) == 1)
        del child.attributes["def"]
        self.confirm(len(child.attributes) == 0)
        dom.unlink()
```

https://github.com/python/cpython/blob/3e04cd268ee9a57f95dc78d8974b21a6fac3f666/Lib/test/test_minidom.py#L285-L294

Specifically when there is a function for it: `removeAttribute`
https://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-6D6AC0F9 

which is tested just below that test.
https://github.com/python/cpython/blob/3e04cd268ee9a57f95dc78d8974b21a6fac3f666/Lib/test/test_minidom.py#L296-L305

so I guess these should be removed or do I miss something in the testing logic?




# Missing docstrings.

Both the testing module and the module lack a lot of docstrings.
Would it be good to fix this too, probably in a separate commit.



# DOM Level 2

So the module intent is to implement DOM Level 2.
but does that make sense in the light of 
https://dom.spec.whatwg.org/

Should minidom tries to follow the current DOM spec?

----------
nosy: +karlcow

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue19683>
_______________________________________

From report at bugs.python.org  Wed Oct  2 20:49:56 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 03 Oct 2019 00:49:56 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570063796.68.0.583659482227.issue38351@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

I definitely think we should not modify any code in the stdlib just to switch to f-strings.

I think the code examples in the docs would benefit from a consistent style, and since f-strings are the least verbose way to format strings, I'd endorse using them except where .format or %-formatting is the point of the example.

I agree with Fred that hearing from Julien would be helpful.

----------
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:13:22 2019
From: report at bugs.python.org (Dima Tisnek)
Date: Thu, 03 Oct 2019 01:13:22 +0000
Subject: [issue38342] ImportError: cannot import name 'MetadataPathFinder'
 from 'importlib.metadata'
In-Reply-To: <1569968531.94.0.379845933414.issue38342@roundup.psfhosted.org>
Message-ID: <1570065202.67.0.421680792214.issue38342@roundup.psfhosted.org>


Change by Dima Tisnek <dimaqq at gmail.com>:


----------
nosy: +Dima.Tisnek

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38342>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:18:28 2019
From: report at bugs.python.org (Charalampos Stratakis)
Date: Thu, 03 Oct 2019 01:18:28 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570065508.19.0.826028467143.issue38350@roundup.psfhosted.org>


Charalampos Stratakis <cstratak at redhat.com> added the comment:

Do note though that if the -D_FORTIFY_SOURCE=2 hardening flag is used, the compilation will fail with an optimization level less than -Og.

Haven't tried yet with -D_FORTIFY_SOURCE=1 to see if it works with -O0.

----------
nosy: +cstratak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:34:08 2019
From: report at bugs.python.org (Artificial)
Date: Thu, 03 Oct 2019 01:34:08 +0000
Subject: [issue38357] print adding extra bytes in hex above x7F
Message-ID: <1570066448.41.0.0345074372849.issue38357@roundup.psfhosted.org>


New submission from Artificial <me at artificialamateur.xyz>:

Any hex str of value above \x7F causes an extra byte to printed.

----------
files: Screenshot from 2019-10-02 20-31-50.png
messages: 353796
nosy: Artificial
priority: normal
severity: normal
status: open
title: print adding extra bytes in hex above x7F
type: behavior
versions: Python 3.7
Added file: https://bugs.python.org/file48641/Screenshot from 2019-10-02 20-31-50.png

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38357>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:35:44 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 03 Oct 2019 01:35:44 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570066544.09.0.167907923987.issue38351@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> I definitely think we should not modify any code in the stdlib just to switch to f-strings.

Does this also apply to updating code to use f-strings in an area that's already being modified for a functional purpose? 

I agree that that we shouldn't update stdlib code for the sole purpose of switching to f-strings, but if a function or method is already being changed for another purpose, I don't think updating the formatting to use f-strings is an issue. This would probably have to be decided on a case-by-case basis though.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:36:33 2019
From: report at bugs.python.org (Charalampos Stratakis)
Date: Thu, 03 Oct 2019 01:36:33 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570066593.14.0.746245857514.issue38350@roundup.psfhosted.org>


Charalampos Stratakis <cstratak at redhat.com> added the comment:

Correction, not fail, just a ton of warnings. The same is true for -D_FORTIFY_SOURCE=1

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:37:41 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 03 Oct 2019 01:37:41 +0000
Subject: [issue38354] Fix for bug 30378 regressed SysLogHandler by making it
 resolve addresses at initialization instead of in `.emit()`
In-Reply-To: <1570051932.55.0.313239800858.issue38354@roundup.psfhosted.org>
Message-ID: <1570066661.9.0.708343242321.issue38354@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +vinay.sajip

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38354>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:37:47 2019
From: report at bugs.python.org (Artificial)
Date: Thu, 03 Oct 2019 01:37:47 +0000
Subject: [issue38357] print adding extra bytes in hex above x7F
In-Reply-To: <1570066448.41.0.0345074372849.issue38357@roundup.psfhosted.org>
Message-ID: <1570066667.99.0.68750646925.issue38357@roundup.psfhosted.org>


Artificial <me at artificialamateur.xyz> added the comment:

python3 -c "print('\x7F')" > test.txt && xxd test.txt
00000000: 7f0a                                     ..                               

python3 -c "print('\x80')" > test.txt && xxd test.txt
00000000: c280 0a                                  ...

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38357>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:40:36 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 03 Oct 2019 01:40:36 +0000
Subject: [issue38352] In typing docs,
 note explicit import needed for IO and Pattern/Match
In-Reply-To: <1570041077.58.0.399304866649.issue38352@roundup.psfhosted.org>
Message-ID: <1570066836.93.0.566849358122.issue38352@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +gvanrossum, levkivskyi

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38352>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:42:31 2019
From: report at bugs.python.org (Ammar Askar)
Date: Thu, 03 Oct 2019 01:42:31 +0000
Subject: [issue38357] print adding extra bytes in hex above x7F
In-Reply-To: <1570066448.41.0.0345074372849.issue38357@roundup.psfhosted.org>
Message-ID: <1570066951.44.0.251089054198.issue38357@roundup.psfhosted.org>


Ammar Askar <ammar at ammaraskar.com> added the comment:

If you're trying to get raw bytes, you need to use

    print(b'\x80')

what's happening right now is that the '\x80' is treated as a unicode code point (see https://docs.python.org/3/howto/unicode.html#the-string-type), and when Python goes to print it, it gets encoded to the raw underlying bytes. Which, in the default encoding of utf-8 requires the extra byte.

>>> '\x80'.encode()
b'\xc2\x80'

----------
nosy: +ammar2
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38357>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:44:40 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 03 Oct 2019 01:44:40 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570067080.54.0.3826899637.issue38351@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

>> I definitely think we should not modify any code in the stdlib just to switch to f-strings.

> Does this also apply to updating code to use f-strings in an area that's already being modified for a functional purpose? 

No. As I said, not just to switch to f-strings. If other changes are also being made, discretion is advised. Just like any other cleanup.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:50:35 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Thu, 03 Oct 2019 01:50:35 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570067435.94.0.350801268744.issue38350@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:

If -Og is breaking debugging, isn't that a compiler bug? The GCC manpage claims " -Og enables optimizations that do not interfere with debugging."

----------
nosy: +benjamin.peterson

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:53:47 2019
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Thu, 03 Oct 2019 01:53:47 +0000
Subject: [issue38357] print adding extra bytes in hex above x7F
In-Reply-To: <1570066448.41.0.0345074372849.issue38357@roundup.psfhosted.org>
Message-ID: <1570067627.38.0.114305911034.issue38357@roundup.psfhosted.org>


Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com> added the comment:

However print() called with non-str argument would firstly call str() on it, which is most likely not what reporter wanted:

>>> print(b'\x80')
b'\x80'
>>> str(b"\x80")
"b'\\x80'"
>>> print(str(b"\x80"))
b'\x80'

$ python -c "print(b'\x80')" > test.txt
$ xxd test.txt
00000000: 6227 5c78 3830 270a                      b'\x80'.


Proper solution is to write to files opened in binary mode, which in case of stdout and stderr means to use sys.stdout.buffer and sys.stderr.buffer:

>>> sys.stdout.buffer.write(b"\x80")
?1

$ python -c "import sys; sys.stdout.buffer.write(b'\x80')" > test.txt
$ xxd test.txt
00000000: 80                                       .

----------
nosy: +Arfrever

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38357>
_______________________________________

From report at bugs.python.org  Wed Oct  2 21:55:29 2019
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Thu, 03 Oct 2019 01:55:29 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570067729.07.0.991230580307.issue38351@roundup.psfhosted.org>


Fred L. Drake, Jr. <fdrake at gmail.com> added the comment:

Definitely agree with Eric on this; code modernization is definitely on the risky side, so judicious updates are important. (Of course, not updating is also a risk, eventually. But not much of one in this case.)

This issue is really about whether the docs should be updated to use the newer syntax. In general, I think we should update the docs, and we've delayed long enough for the general application of f-strings.

There will be cases to be wary of, certainly. I'm thinking especially of calls to the logging methods, or anywhere else doing delayed formatting. (Not that I can think of others off the top of my head.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 22:05:25 2019
From: report at bugs.python.org (Artificial)
Date: Thu, 03 Oct 2019 02:05:25 +0000
Subject: [issue38357] print adding extra bytes in hex above x7F
In-Reply-To: <1570066448.41.0.0345074372849.issue38357@roundup.psfhosted.org>
Message-ID: <1570068325.89.0.710341636113.issue38357@roundup.psfhosted.org>


Artificial <me at artificialamateur.xyz> added the comment:

Thanks, Arfrever

Seems unnecessarily complicated for what worked in Python2.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38357>
_______________________________________

From report at bugs.python.org  Wed Oct  2 22:22:48 2019
From: report at bugs.python.org (Charalampos Stratakis)
Date: Thu, 03 Oct 2019 02:22:48 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570069368.95.0.597139547812.issue38350@roundup.psfhosted.org>


Charalampos Stratakis <cstratak at redhat.com> added the comment:

It seems that it's still being worked on from gcc's side:

https://gcc.gnu.org/bugzilla//show_bug.cgi?id=78685

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Wed Oct  2 23:02:46 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Thu, 03 Oct 2019 03:02:46 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570071766.26.0.828187149069.issue38333@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

In that case, I'm pretty sure you'd never be able to document almost _any_ function signature. Python is simply not a statically typed language, and we love it because of that.

Ok, go to the list of builtins, and start alphabetically. First is abs. What type does it take, and what type does it return? Again, I'd be completely ok with saying it takes an int, a float, or a complex, and returns either an int or a float. The same as the words in the docs already say. But according to Guido, that's "unacceptable", since abs can also take (and return) a datetime.timedelta, for example.

I am very afraid that if we start doing this, we will lose _many_ useful features that make Python the language it is. It's really not worth it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Wed Oct  2 23:06:28 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 03 Oct 2019 03:06:28 +0000
Subject: [issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks
 threads
In-Reply-To: <1570056781.39.0.894014377654.issue38356@roundup.psfhosted.org>
Message-ID: <1570071988.46.0.595629214932.issue38356@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

First I'll work on adding a new method. Here's a few potential names, ordered roughly by my preferences:

1) join_threads()

2) shutdown_threads()

3) shutdown_threadpool()

The first and second options are roughly equal, but I think join_threads() is a bit more specific to what this is doing.

The third option is because a group of threads could be considered a "threadpool", but ThreadedChildWatcher doesn't utilize a dedicated threadpool class of any form, it just uses an internal dict named `_threads` that maps process IDs to threads. So this name might be potentially misleading.

I'm also wondering whether or not this method should have a timeout parameter that defaults to None. I'm thinking we can probably leave it out for now, but I wanted to hear some other opinions on this.

For now, I'll be implementing this as a regular method, but I could make it a coroutine if that's desired. Admittedly, I don't enough have knowledge of the realistic use cases for ThreadedChildWatcher to know if it would be particularly useful to have an awaitable method to join the threads.

Another consideration is if we want this method to join the threads to be called in `ThreadedChildWatcher.close()`. I think it makes sense from a design perspective to join all of the threads when the close method is used. 

Plus, it would allow the method to be integrated with the tests better. Currently, the test uses the same `setUp()` and `tearDown()` for each of the different subprocess watchers. If it weren't called in the `close()` method, we'd have to add an `if isinstance(watcher, ThreadedChildWatcher)` conditional in `tearDown()`. So, I would prefer to have the method called from `close()`.

Finally, should this method be part of the public API, or just a private method? As mentioned earlier, I'm not overly aware of the realistic use cases for ThreadedChildWatcher. As a result, I don't know if it would be especially useful for users to call this method independently, especially if this were called from `close()` as I was suggesting earlier. 

After we reach a consensus on the implementation details and API design for the new method, I'll work on adding an entry in the documentation (if it should be public) and updating test_subprocess.SubprocessThreadedWatcherTests to utilize it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38356>
_______________________________________

From report at bugs.python.org  Wed Oct  2 23:19:00 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 03 Oct 2019 03:19:00 +0000
Subject: [issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks
 threads
In-Reply-To: <1570056781.39.0.894014377654.issue38356@roundup.psfhosted.org>
Message-ID: <1570072740.84.0.044932513183.issue38356@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> Another consideration is if we want this method to join the threads to be called in `ThreadedChildWatcher.close()`.

An additional benefit of having the method called from `close()` is that it means we don't have to modify the tests directly. Also, ThreadedChildWatcher's implementation of `close()` does nothing at the moment.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38356>
_______________________________________

From report at bugs.python.org  Wed Oct  2 23:35:39 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 03 Oct 2019 03:35:39 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570073739.25.0.503609582079.issue38351@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

>  (Not that I can think of others off the top of my head.)

For the most part, templating examples can be switched to the .format() style but shouldn't be switched to f-strings.  The former technique is still necessary if someone wants to move templates to an external file or if they need to use gettext() i18n, f-strings don't work well in the latter case.

Also note, there are no plans to completely remove old-style formatting.  AFAICT, it will be around forever, so people still need to see some examples of each.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  2 23:38:34 2019
From: report at bugs.python.org (paul rubin)
Date: Thu, 03 Oct 2019 03:38:34 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570073914.88.0.362848840236.issue38333@roundup.psfhosted.org>


paul rubin <phr-pythonbugs at nightsong.com> added the comment:

abs takes any value that understands the __abs__ method and returns something of the same type.  In fact there is already a type protocol for it:

https://mypy.readthedocs.io/en/stable/protocols.html#supportsabs-t

So abs's signature would be (x : Abs[T]) -> T where T is a type parameter.  

I'm sure there are some examples where no good signature is possible, but lots of others are fine.  Someone did a Smalltalk study long ago and found that most functions were monomorphic in practice even though Smalltalk is dynamically typed like Python.  As a matter of style, Python code tends to be typed even when it doesn't have to be.  Not all the time of course.

I'm still getting used to types and mypy (I was a py2 holdout til quite recently, and mypy has been a more attractive reason to change than any of the other stuff) and I do keep noticing cases that don't work as I hoped, but it's still a good move in general.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Wed Oct  2 23:55:02 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 03 Oct 2019 03:55:02 +0000
Subject: [issue38356] test_asyncio: SubprocessThreadedWatcherTests leaks
 threads
In-Reply-To: <1570056781.39.0.894014377654.issue38356@roundup.psfhosted.org>
Message-ID: <1570074902.4.0.336399104449.issue38356@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
keywords: +patch
pull_requests: +16140
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16552

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38356>
_______________________________________

From report at bugs.python.org  Thu Oct  3 01:03:30 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 03 Oct 2019 05:03:30 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570079010.09.0.536921503659.issue13153@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

The revised PR appears to fix this and other issues, although the presence of astral chars in code being edited messes up tk's cursor positioning.  Assuming that this cannot be changed, we could add the the ability to replace astral chars with \U escapes.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Thu Oct  3 01:06:25 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 03 Oct 2019 05:06:25 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570079185.77.0.375767337715.issue38351@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> For the most part, templating examples can be switched to the .format() style but shouldn't be switched to f-strings.

Is there no specific use case for the older "%s" % sub template that .format() doesn't have?

> The former technique is still necessary if someone wants to move templates to an external file

Interesting, I wasn't aware of that. This seems like it might be worth a brief mention in https://docs.python.org/3.9/library/stdtypes.html#str.format. 

> AFAICT, it will be around forever, so people still need to see some examples of each.

To allow users to see examples of each, would you suggest that we should leave the existing .format() examples as is and have more recently created examples use f-strings? I'd be okay with this, as long as there's a balance of both everywhere (particularly in the tutorial).

Personally, I think that the f-string examples should be used more commonly used since they're generally more concise and readable. But, I can definitely understand the purpose of leaving the older ones around as long as they have a specific use case and are still utilized.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Thu Oct  3 01:45:58 2019
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Thu, 03 Oct 2019 05:45:58 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570081558.91.0.640037403641.issue38351@roundup.psfhosted.org>


Fred L. Drake, Jr. <fdrake at gmail.com> added the comment:

I'd like to see consistent usage by default, with specific examples using the older forms as appropriate.  The use cases Raymond identified are worth discussing (and the tutorial may be a good place for this), and well as mentioned in the reference docs for the '%s' % x and ''.format() operations (and string.Template(), of course).

I would not like to see different syntaxes randomly applied to different examples that happen to involve formatting, but where that's not the emphasis.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Thu Oct  3 02:20:42 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Thu, 03 Oct 2019 06:20:42 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570083642.45.0.770722397423.issue38333@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

Well, yes, if you're going to invent a special typeclass for every protocol, then you can document any signature. But what purpose does it serve? Abs to me seems like a hack, not something we really wanted to capture with the type system.

Do you find (x : Abs[T]) -> T in any way clearer than what's currently written in the docs? Do we really want to move in that direction? And not to mention that "... returns something of the same type" is _still_ incorrect -- for example, for complex it returns float.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Thu Oct  3 02:31:28 2019
From: report at bugs.python.org (Aivar Annamaa)
Date: Thu, 03 Oct 2019 06:31:28 +0000
Subject: [issue34455] Tkinter crashing when pressing Command + ^  (OSX)
In-Reply-To: <1534890010.44.0.56676864532.issue34455@psf.upfronthosting.co.za>
Message-ID: <1570084288.95.0.666441901404.issue34455@roundup.psfhosted.org>


Aivar Annamaa <aivar.annamaa at gmail.com> added the comment:

I created the ticket: https://core.tcl-lang.org/tk/tktview/5849df7852c48cb763b11a11d848a68482b0f828

----------
nosy: +Aivar.Annamaa

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34455>
_______________________________________

From report at bugs.python.org  Thu Oct  3 02:41:52 2019
From: report at bugs.python.org (paul rubin)
Date: Thu, 03 Oct 2019 06:41:52 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570084912.15.0.809646963988.issue38333@roundup.psfhosted.org>


paul rubin <phr-pythonbugs at nightsong.com> added the comment:

At first glance, having a typeclass for each protocol (at least the widely used ones) seems fine.  It's inherent in Haskell and a lot of libraries are organized around a common set of typeclasses--look up "Typeclassopedia" for descriptions of them.  Certainly the case of abs (which you asked about by name), the typeclass is already there in the typing module.

You're right about abs(complex) returning float.  Haskell's type signature for abs is "Num a => a -> a" which means the input type is the same as the output.  That is a little bit peculiar since the abs of a complex number is complex, but we usually think of abs as a mathematical norm, which is conventionally a real.

Anyway, "abs(x: Abs[T]) -> Any"  is a better-than-nothing signature for abs, and the docs can comment a little further, and maybe someday it could even do a type-level lookup at typechecking time, i.e. have something like Haskell's "type families".

I like to think it's possible to supply reasonable signatures for most functions.  I just fixed a bug in something today because bs4 (beautiful soup 4) has no typeshed stub so mypy uses Any for functions like soup.find, instead of Optional[tag].  So the program worked fine as long as find kept returning a tag, but then crashed because it hit a document without a tag and my code didn't check for None.  That's something more precise types would have caught at mypy time.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Thu Oct  3 02:48:43 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Thu, 03 Oct 2019 06:48:43 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570085323.0.0.761777128097.issue38333@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

Your arguments in my view boil down to "Haskell is a nice language" and "Static typing is useful". It still doesn't change my argument that Python is genetically neither of these. And we will cripple it greatly if we try to push it in that direction.

[Your problem with bs4 is just a facet of a billion dollar mistake (treating null as an object), that's present in many statically typed languages even today. Optional is great for explaining to humans, but very hard to get right when talking to computers.]

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Thu Oct  3 02:58:07 2019
From: report at bugs.python.org (paul rubin)
Date: Thu, 03 Oct 2019 06:58:07 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570085887.1.0.54412728298.issue38333@roundup.psfhosted.org>


paul rubin <phr-pythonbugs at nightsong.com> added the comment:

I don't think we're going to accomplish anything continuing the eternal static-vs-dynamic debate, which in Python's case has already been resolved by adding optional static typing.  It's a done deal, and the issue here is just how to document it.  Erlang (via the Erlang Dialyzer), Clojure, and Racket have all been down a similar road and gained some value from it.

Haskell's Maybe type (its version of Option) works fine.  In Python the convention of returning None for a missing value is not great, but we are stuck with it and Option[whatever] is helpful.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Thu Oct  3 03:06:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 07:06:57 +0000
Subject: [issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead
 to memory corruption and deadlock
In-Reply-To: <1568200653.3.0.865964137512.issue38106@roundup.psfhosted.org>
Message-ID: <1570086417.72.0.353329180504.issue38106@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset c5abd63e94fcea10bdfa7a20842c6af3248bbd74 by Victor Stinner (Kirill Smelkov) in branch '2.7':
bpo-38106: Fix race in pthread PyThread_release_lock() (GH-16047)
https://github.com/python/cpython/commit/c5abd63e94fcea10bdfa7a20842c6af3248bbd74


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38106>
_______________________________________

From report at bugs.python.org  Thu Oct  3 03:10:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 07:10:00 +0000
Subject: [issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead
 to memory corruption and deadlock
In-Reply-To: <1568200653.3.0.865964137512.issue38106@roundup.psfhosted.org>
Message-ID: <1570086600.73.0.478316809964.issue38106@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I merged Kirill Smelkov's fix. Thanks. I close the issue.

I'm surprised that we still find new bugs in this code which is supposed to be battle tested! Maybe recent Darwin changed made the bug more likely.

PyPy: it's now your turn to fix it ;-)

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38106>
_______________________________________

From report at bugs.python.org  Thu Oct  3 03:11:14 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 07:11:14 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570086674.02.0.708342364417.issue38350@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Do note though that if the -D_FORTIFY_SOURCE=2 hardening flag is used, the compilation will fail with an optimization level less than -Og.

Does it make any sense to use a debug build in production? Does it make sense to enable hardening on a debug buil?d

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Thu Oct  3 03:16:24 2019
From: report at bugs.python.org (Nathaniel Smith)
Date: Thu, 03 Oct 2019 07:16:24 +0000
Subject: [issue37373] Configuration of windows event loop for libraries
In-Reply-To: <1561228405.39.0.674272094682.issue37373@roundup.psfhosted.org>
Message-ID: <1570086984.11.0.830577712617.issue37373@roundup.psfhosted.org>


Nathaniel Smith <njs at pobox.com> added the comment:

It's also possible to implement 'select' on top of IOCP using undocumented private APIs. That's what libuv does (and how 'select' works internally). There's a bunch of information on this collected here: https://github.com/python-trio/trio/issues/52

----------
nosy: +njs

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37373>
_______________________________________

From report at bugs.python.org  Thu Oct  3 03:50:25 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 07:50:25 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570089025.19.0.635558580933.issue36670@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16141
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/16553

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 03:56:11 2019
From: report at bugs.python.org (Kirill Smelkov)
Date: Thu, 03 Oct 2019 07:56:11 +0000
Subject: [issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead
 to memory corruption and deadlock
In-Reply-To: <1568200653.3.0.865964137512.issue38106@roundup.psfhosted.org>
Message-ID: <1570089371.99.0.107614941299.issue38106@roundup.psfhosted.org>


Kirill Smelkov <kirr at nexedi.com> added the comment:

Victor, thanks for merging.

> I'm surprised that we still find new bugs in this code which is supposed to
> be battle tested! Maybe recent Darwin changed made the bug more likely.

As discussed above (https://bugs.python.org/issue38106#msg351917,
https://bugs.python.org/issue38106#msg351970), due to the GIL, the bug is not
possible to trigger from pure-python code, and it can be hit only via using CAPI
directly. I indeed started to observe the problem after moving locks and
other code that implement channels in Pygolang from Python to C level (see
"0.0.3" in https://pypi.org/project/pygolang/#pygolang-change-history)

The bug was there since 1994 and, from my point of view, it was not discovered
because locking functionality was not enough hammer-tested. The bug was also
not possible to explain without taking lock lifetime into account, as, without
create/destroy, just lock/unlock sequence was race free. 
https://bugs.python.org/issue433625 confirms that.

I cannot say about whether recent macOS changes are relevant. My primary
platform is Linux and I only recently started to use macOS under QEMU for
testing. However from my brief study of https://github.com/apple/darwin-libpthread
I believe the difference in scheduling related to pthread condition variable
signalling under macOS and Linux is there already for a long time.

> PyPy: it's now your turn to fix it ;-)

PyPy people fixed the bug the same day it was reported:

https://bitbucket.org/pypy/pypy/issues/3072

:)

Kirill

P.S. Mariusz, thanks also for your feedback.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38106>
_______________________________________

From report at bugs.python.org  Thu Oct  3 04:02:19 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 08:02:19 +0000
Subject: [issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead
 to memory corruption and deadlock
In-Reply-To: <1568200653.3.0.865964137512.issue38106@roundup.psfhosted.org>
Message-ID: <1570089739.42.0.951837660945.issue38106@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> PyPy people fixed the bug the same day it was reported: ...

Oh ok, so the CPython commit message is already outdated :-)

"PyPy has the same bug for both pypy2 and pypy3 (...)"

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38106>
_______________________________________

From report at bugs.python.org  Thu Oct  3 04:06:54 2019
From: report at bugs.python.org (Kirill Smelkov)
Date: Thu, 03 Oct 2019 08:06:54 +0000
Subject: [issue38106] [2.7] Race in PyThread_release_lock on macOS - can lead
 to memory corruption and deadlock
In-Reply-To: <1568200653.3.0.865964137512.issue38106@roundup.psfhosted.org>
Message-ID: <1570090014.13.0.501800047711.issue38106@roundup.psfhosted.org>


Kirill Smelkov <kirr at nexedi.com> added the comment:

:) Yes and no. PyPy did not make a new release with the fix yet.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38106>
_______________________________________

From report at bugs.python.org  Thu Oct  3 04:31:46 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 03 Oct 2019 08:31:46 +0000
Subject: [issue34455] Tkinter crashing when pressing Command + ^  (OSX)
In-Reply-To: <1534890010.44.0.56676864532.issue34455@psf.upfronthosting.co.za>
Message-ID: <1570091506.0.0.901027848632.issue34455@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Aivar, thank you for opening the issue.

I believe what I meant about tkinter bind calls would be to conditionallly bind '<Command+^>' to a function that returns 'break', thus claiming that the key combination has been handled and that tk should ignore it.  The function could do nothing or it could display a message.

I don't know if this would work until it were tested.  And it would be a real kludgy workaround and until disabled would block the key combo from working when the tcl people did fix it.  So not to be done lightly.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34455>
_______________________________________

From report at bugs.python.org  Thu Oct  3 04:32:54 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 03 Oct 2019 08:32:54 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570091574.84.0.455591358174.issue38350@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

The purpose of using -Og is that it significantly speeds up tests. You can always pass CFLAGS="-O0" if you debug particular debugger issues, but in normal cases -Og looks more beneficial. It saves hours of time of common developers.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Thu Oct  3 04:39:18 2019
From: report at bugs.python.org (Aivar Annamaa)
Date: Thu, 03 Oct 2019 08:39:18 +0000
Subject: [issue34455] Tkinter crashing when pressing Command + ^  (OSX)
In-Reply-To: <1534890010.44.0.56676864532.issue34455@psf.upfronthosting.co.za>
Message-ID: <1570091958.15.0.733574698604.issue34455@roundup.psfhosted.org>


Aivar Annamaa <aivar.annamaa at gmail.com> added the comment:

> to conditionallly bind '<Command+^>' to a function that returns 'break'

I tried capturing all <Key> events. The handler was called for Cmd press,  but the crash occurred before the handler was called for the other key.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34455>
_______________________________________

From report at bugs.python.org  Thu Oct  3 04:45:37 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 03 Oct 2019 08:45:37 +0000
Subject: [issue38348] Make python -m ast more configurable
In-Reply-To: <1570029299.56.0.0303865742584.issue38348@roundup.psfhosted.org>
Message-ID: <1570092337.6.0.477882387951.issue38348@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Why do you need this feature?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38348>
_______________________________________

From report at bugs.python.org  Thu Oct  3 04:53:38 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 08:53:38 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570092818.07.0.519103079434.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset c65119d5bfded03f80a9805889391b66fa7bf551 by Victor Stinner in branch 'master':
bpo-36670: Enhance regrtest WindowsLoadTracker (GH-16553)
https://github.com/python/cpython/commit/c65119d5bfded03f80a9805889391b66fa7bf551


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 04:55:18 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 08:55:18 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570092918.42.0.932548534524.issue36670@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16142
pull_request: https://github.com/python/cpython/pull/16554

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 05:03:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 09:03:56 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570093436.64.0.695345745491.issue36670@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16143
pull_request: https://github.com/python/cpython/pull/16555

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 05:10:09 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 03 Oct 2019 09:10:09 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570093809.64.0.127343709998.issue13153@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

>From the point of view of Tk, the astral character "?" looks like either two invisible characters "\ud83d\udcbb" or as four characters "?\x9f\x92?" (two of them are invisible). Thus this breaks editing the physical line past the astral character. We cannot do anything with this.

It also breaks syntax highlighting up to 100 lines past the astral character. We can add a workaround for this, but I am not sure it is worth. The solution could be complex and slow down the common case. In any case it is a different issue.

File names with astral characters now are shown correctly in most cases. Astral characters are not shown in the title of the window, perhaps it is font depending.

Opening a file name with astral characters works in the command line, but it does not work via the file open dialog. This looks like a bug in Tk, we cannot workaround it (or at least the possible workaround would be ugly and partial).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Thu Oct  3 05:12:37 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 03 Oct 2019 09:12:37 +0000
Subject: [issue38358] ASSERTION ERROR WHILE USING TENSORFLOW
In-Reply-To: <1570092612.13.0.03397983919.issue38358@roundup.psfhosted.org>
Message-ID: <1570093957.25.0.816873815495.issue38358@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

This is a tracker for bugs in Python itself. Tensorflow is a third-party library. Please use an appropriate bug tracker for reporting issues with tensorflow.

----------
nosy: +serhiy.storchaka
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38358>
_______________________________________

From report at bugs.python.org  Thu Oct  3 05:29:12 2019
From: report at bugs.python.org (karl)
Date: Thu, 03 Oct 2019 09:29:12 +0000
Subject: [issue19683] test_minidom has many empty tests
In-Reply-To: <1385047059.66.0.790496754317.issue19683@psf.upfronthosting.co.za>
Message-ID: <1570094952.11.0.554903241685.issue19683@roundup.psfhosted.org>


karl <karl+pythonbugs at la-grange.net> added the comment:

err? Errata on my previous comment.

"""
Simple implementation of the Level 1 DOM.

Namespaces and other minor Level 2 features are also supported.
"""
https://github.com/python/cpython/blob/c65119d5bfded03f80a9805889391b66fa7bf551/Lib/xml/dom/minidom.py#L1-L3


https://www.w3.org/TR/REC-DOM-Level-1/

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue19683>
_______________________________________

From report at bugs.python.org  Thu Oct  3 05:32:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 09:32:53 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570095173.74.0.125913863176.issue36670@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16144
pull_request: https://github.com/python/cpython/pull/16556

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 05:53:25 2019
From: report at bugs.python.org (Andrew Ushakov)
Date: Thu, 03 Oct 2019 09:53:25 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
Message-ID: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>


New submission from Andrew Ushakov <andrew.ushakov at gmail.com>:

pyw.exe (Python Launcher for Windows Version 3.8.121.1013) opens a console window at startup. To reproduce, run command below from the console:

D:>pyw -c "import time; time.sleep(10)"

By the way command:

D:>pythomw -c "import time; time.sleep(10)"

works as expected, silently.

----------
components: Windows
messages: 353836
nosy: Andrew Ushakov, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: pyw.exe opens console window in Windows 10
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Thu Oct  3 05:54:22 2019
From: report at bugs.python.org (karl)
Date: Thu, 03 Oct 2019 09:54:22 +0000
Subject: [issue9004] datetime.utctimetuple() should not set tm_isdst flag to 0
In-Reply-To: <1276659404.06.0.425467293989.issue9004@psf.upfronthosting.co.za>
Message-ID: <1570096462.61.0.798445428352.issue9004@roundup.psfhosted.org>


karl <karl+pythonbugs at la-grange.net> added the comment:

@gaurav The pull request 
https://github.com/python/cpython/pull/10870
has been closed in favor of 
https://github.com/python/cpython/pull/15773
which has already been merged.

So we can probably close here.

----------
message_count: 7.0 -> 8.0
nosy: +karlcow
nosy_count: 7.0 -> 8.0
pull_requests: +16145
pull_request: https://github.com/python/cpython/pull/15773

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue9004>
_______________________________________

From report at bugs.python.org  Thu Oct  3 07:20:54 2019
From: report at bugs.python.org (Joshua Root)
Date: Thu, 03 Oct 2019 11:20:54 +0000
Subject: [issue38360] single-argument form of -isysroot should be supported
Message-ID: <1570101654.53.0.395218631906.issue38360@roundup.psfhosted.org>


New submission from Joshua Root <josh+python at root.id.au>:

The path associated with the -isysroot compiler flag can be supplied either as a separate argument or in the same argument as -isysroot itself. The places in library code that do special handling of this flag should support both forms, but currently only support the two separate arguments form. This means that the flag may not be removed when pointing to a nonexistent SDK or when a different SDK is specified in the user's CFLAGS, and at worst a ValueError is raised in compiler_fixup.

----------
components: Distutils, macOS
messages: 353838
nosy: dstufft, eric.araujo, jmr, ned.deily, ronaldoussoren
priority: normal
pull_requests: 16146
severity: normal
status: open
title: single-argument form of -isysroot should be supported
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38360>
_______________________________________

From report at bugs.python.org  Thu Oct  3 07:38:59 2019
From: report at bugs.python.org (Vaclav Bartos)
Date: Thu, 03 Oct 2019 11:38:59 +0000
Subject: [issue38361] syslog: Default "ident" in syslog.openlog() shouldn't
 contain slash
Message-ID: <1570102738.99.0.163183464343.issue38361@roundup.psfhosted.org>


New submission from Vaclav Bartos <bartos at cesnet.cz>:

When `syslog.openlog()` is called without parameters (or `syslog.syslog()` is called directly), the `ident` parameter should be set to "sys.argv[0] with leading path components stripped" (citation from docs).

I suppose this means that when sys.argv[0] is "/some/path/to/script", the ident should be set to "script" (this is the behavior in Python 2.7)

However, in Python 3.x, it gets set to "/script", i.e. the last slash is included in the string. I suppose this is not intended, it is just a "one-off" error in parsing the string.

The fix is trivial, see the linked GitHub PR.


To reproduce the bug:

$ python3
>>> import sys
>>> import syslog
>>> sys.argv[0] = "/some/path/to/script"
>>> syslog.syslog("TEST MESSAGE")
>>> 
$ tail -n 1 /var/log/messages
Oct  3 11:11:46 localhost /script: TEST MESSAGE

----------
components: Extension Modules
messages: 353839
nosy: vaclavbartos
priority: normal
pull_requests: 16147
severity: normal
status: open
title: syslog: Default "ident" in syslog.openlog() shouldn't contain slash
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38361>
_______________________________________

From report at bugs.python.org  Thu Oct  3 07:44:52 2019
From: report at bugs.python.org (=?utf-8?b?0KHQstC10YLQu9C+0LzQuNGAINCR0LDQu9C10LLRgdC60Lg=?=)
Date: Thu, 03 Oct 2019 11:44:52 +0000
Subject: [issue38362] platform.system() comparison problem
Message-ID: <1570103092.18.0.780844249271.issue38362@roundup.psfhosted.org>


New submission from ????????? ???????? <s.balevski at gmail.com>:

Hi, I am using platform.system(). On linux I am using python3.6. 
>>> platform.system()
'Linux'
>>> platform.system() is 'Linux'
False 
>>> platform.system() == 'Linux'
True 

On Windows with python 3.7:
[?10/?3/?2019 2:42 PM]  
>>> platform.system()
'Windows'
>>> platform.system() is 'Windows'
True
>>> platform.system() == 'Windows'
True 

Is this a known problem?

----------
components: Library (Lib)
messages: 353840
nosy: ????????? ????????
priority: normal
severity: normal
status: open
title: platform.system() comparison problem
type: behavior
versions: Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38362>
_______________________________________

From report at bugs.python.org  Thu Oct  3 08:10:17 2019
From: report at bugs.python.org (Stephen Tucker)
Date: Thu, 03 Oct 2019 12:10:17 +0000
Subject: [issue38363] No Module named ..." and UTF-8 Byte Order Marks
Message-ID: <CAP=-cKWPrnrc7WpYcbLG99UVhTp0hC3bJbkJ3F8qiwqTuLR0aA@mail.gmail.com>


New submission from Stephen Tucker <stephen_tucker at sil.org>:

Hi,

I am running Python 2.7.10 on Windows 10.

I have discovered that if a .py source text file (that is, a Module text
file) starts with a UTF-8 Byte Order Mark, the module does not get "found"
by the  import  statement.

I have just spent an inordinate amount of time reaching this conclusion.

I realise that 2.7.10 is probably not being supported any more, however,
please let me ask the questions anyway:

Could ...
   Either:   ... the error message please be more helpful? (Like, for
example,  "Module begins with a Byte Order Mark")
   Or:    ... the BOM be allowed at the start of a Module?

Thanks.

Stephen Tucker.

----------
messages: 353841
nosy: Stephen_Tucker
priority: normal
severity: normal
status: open
title: No Module named ..." and UTF-8 Byte Order Marks

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38363>
_______________________________________

From report at bugs.python.org  Thu Oct  3 08:25:49 2019
From: report at bugs.python.org (Batuhan)
Date: Thu, 03 Oct 2019 12:25:49 +0000
Subject: [issue38348] Make python -m ast more configurable
In-Reply-To: <1570092337.6.0.477882387951.issue38348@roundup.psfhosted.org>
Message-ID: <CANDBV66MNZiUGYzT+PJfdhyGEhVjyPWFrvFOsfRXrGgzp3nVvg@mail.gmail.com>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

I was checking typed_ast and i wanted to know which parts changed and
implement that parts to astor. But there was no flags for --type-comments
False.

Also it can be handy to have an indention option to change it for fitting
tree into the terminal width.

On Thu, Oct 3, 2019, 11:45 AM Serhiy Storchaka <report at bugs.python.org>
wrote:

>
> Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:
>
> Why do you need this feature?
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue38348>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38348>
_______________________________________

From report at bugs.python.org  Thu Oct  3 08:44:09 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 03 Oct 2019 12:44:09 +0000
Subject: [issue38362] platform.system() comparison problem
In-Reply-To: <1570103092.18.0.780844249271.issue38362@roundup.psfhosted.org>
Message-ID: <1570106649.3.0.462215838462.issue38362@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Using "is" could be dependent on how the string is interned to refer to the same string during comparison for identity. Using == is more reliable and correct.

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38362>
_______________________________________

From report at bugs.python.org  Thu Oct  3 08:51:19 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Thu, 03 Oct 2019 12:51:19 +0000
Subject: [issue38362] platform.system() comparison problem
In-Reply-To: <1570103092.18.0.780844249271.issue38362@roundup.psfhosted.org>
Message-ID: <1570107079.14.0.955782891773.issue38362@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

This is nothing to do with platform.system. You can see the same behaviour with any string comparison, or ints.

The `is` operator is not a cute way of spelling `==`, it tests for object identity, not equality. It tests whether the two arguments are the same object. The Python interpreter caches some strings, and some ints, to save memory, so the result of ``expression is "somestring"`` will depend on the operating system, the version of Python, what happens to be in the cache, and whatever memory optimization tricks are being used by the interpreter.

Never use ``is`` for testing whether two things are equal. Only use it for testing object identity, like ``obj is None``.

By the way, this question about ``is`` has been asked many, many times on places like Stackoverflow. If you have any further questions about this, you should check the answers there.

----------
nosy: +steven.daprano
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38362>
_______________________________________

From report at bugs.python.org  Thu Oct  3 08:52:29 2019
From: report at bugs.python.org (karl)
Date: Thu, 03 Oct 2019 12:52:29 +0000
Subject: [issue1375011] http.cookies,
 Cookie.py: Improper handling of duplicate cookies
Message-ID: <1570107149.58.0.181991050581.issue1375011@roundup.psfhosted.org>


karl <karl+pythonbugs at la-grange.net> added the comment:

Relevant spec
https://tools.ietf.org/html/rfc6265

----------
nosy: +karlcow

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1375011>
_______________________________________

From report at bugs.python.org  Thu Oct  3 08:52:18 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Thu, 03 Oct 2019 12:52:18 +0000
Subject: [issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent()
 Internal
In-Reply-To: <1569352841.72.0.766028949986.issue38266@roundup.psfhosted.org>
Message-ID: <1570107138.9.0.937941647512.issue38266@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


----------
keywords: +patch
pull_requests: +16148
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16558

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38266>
_______________________________________

From report at bugs.python.org  Thu Oct  3 08:52:18 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Thu, 03 Oct 2019 12:52:18 +0000
Subject: [issue37878] Sub-Interpreters : Document PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1570107138.99.0.514294940305.issue37878@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


----------
pull_requests: +16149
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16558

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37878>
_______________________________________

From report at bugs.python.org  Thu Oct  3 08:54:57 2019
From: report at bugs.python.org (Kevin Walzer)
Date: Thu, 03 Oct 2019 12:54:57 +0000
Subject: [issue34455] Tkinter crashing when pressing Command + ^  (OSX)
In-Reply-To: <1534890010.44.0.56676864532.issue34455@psf.upfronthosting.co.za>
Message-ID: <1570107297.68.0.049737053999.issue34455@roundup.psfhosted.org>


Kevin Walzer <wordtech at users.sourceforge.net> added the comment:

We have committed some fixes to the keyboard code in the past year that seem to have fixed this issue. I do not see it in 8.6.10, now as a RC. I believe this bug is obsolete at this point.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34455>
_______________________________________

From report at bugs.python.org  Thu Oct  3 09:20:11 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Thu, 03 Oct 2019 13:20:11 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570108811.29.0.551786544999.issue38333@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

https://www.python.org/dev/peps/pep-0484/#non-goals

I really have nothing more to say.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Thu Oct  3 09:21:58 2019
From: report at bugs.python.org (Ma Lin)
Date: Thu, 03 Oct 2019 13:21:58 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570108918.61.0.837349451.issue13153@roundup.psfhosted.org>


Ma Lin <malincns at 163.com> added the comment:

> Thus this breaks editing the physical line past the astral character. We cannot do anything with this.

I tried, it's sad the experience is not very good.

----------
nosy: +Ma Lin

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Thu Oct  3 09:28:44 2019
From: report at bugs.python.org (Martijn Pieters)
Date: Thu, 03 Oct 2019 13:28:44 +0000
Subject: [issue38364] inspect.iscoroutinefunction / isgeneratorfunction /
 isasyncgenfunction can't handle partialmethod objects
Message-ID: <1570109324.07.0.792957059658.issue38364@roundup.psfhosted.org>


New submission from Martijn Pieters <mj at python.org>:

This is a follow-up to #33261, which added general support for detecting generator / coroutine / async generator functions wrapped in partials. It appears that partialmethod objects were missed out.

While a partialmethod object will produce a functools.partial() object on binding to an instance, the .func attribute of that partial is a bound method, not a function, and the current _has_code_flag implementation unwraps methods *before* it unwraps partials.

Next, binding to a class produces a partialmethod._make_unbound_method.<locals>._method wrapper function. _unwrap_partial can't unwrap this, as it doesn't handle this case; it could look for the `_partialmethod` attribute and follow that to find the `.func` attribute.

Test case:

import inspect
import functools

class Foo:
    async def bar(self, a): return a
    ham = partialmethod(bar, "spam")

print(inspect.iscoroutinefunction(Foo.bar)  # True
print(inspect.iscoroutinefunction(Foo.ham)  # False
instance = Foo()
print(inspect.iscoroutinefunction(instance.bar)  # True
print(inspect.iscoroutinefunction(instance.ham)  # False

----------
components: Library (Lib)
messages: 353849
nosy: mjpieters
priority: normal
severity: normal
status: open
title: inspect.iscoroutinefunction / isgeneratorfunction / isasyncgenfunction can't handle  partialmethod objects
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38364>
_______________________________________

From report at bugs.python.org  Thu Oct  3 09:38:56 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 03 Oct 2019 13:38:56 +0000
Subject: [issue38364] inspect.iscoroutinefunction / isgeneratorfunction /
 isasyncgenfunction can't handle partialmethod objects
In-Reply-To: <1570109324.07.0.792957059658.issue38364@roundup.psfhosted.org>
Message-ID: <1570109936.31.0.383849926036.issue38364@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +asvetlov, yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38364>
_______________________________________

From report at bugs.python.org  Thu Oct  3 10:15:34 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 14:15:34 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570112134.52.0.462047450189.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 098e25672f1c3578855d5ded4f5147795c9ed956 by Victor Stinner in branch 'master':
bpo-36670: Enhance regrtest (GH-16556)
https://github.com/python/cpython/commit/098e25672f1c3578855d5ded4f5147795c9ed956


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 10:18:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 14:18:53 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570112333.33.0.29995287471.issue36670@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16150
pull_request: https://github.com/python/cpython/pull/16559

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 10:20:34 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 14:20:34 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570112434.33.0.672205405223.issue36670@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16151
pull_request: https://github.com/python/cpython/pull/16560

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 10:40:28 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 03 Oct 2019 14:40:28 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570113628.44.0.370738502846.issue38333@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

Since this discussion went down in flames quickly, I'm closing it. Another issue can be opened once someone has a concrete design of what this should look like in the formatted docs, an example that does this for a few libraries, and a prototype of a tool that extracts signatures from typeshed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Thu Oct  3 10:40:44 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 03 Oct 2019 14:40:44 +0000
Subject: [issue38333] add type signatures to library function docs
In-Reply-To: <1569903700.63.0.276076850828.issue38333@roundup.psfhosted.org>
Message-ID: <1570113644.71.0.136358399603.issue38333@roundup.psfhosted.org>


Change by Guido van Rossum <guido at python.org>:


----------
resolution:  -> postponed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38333>
_______________________________________

From report at bugs.python.org  Thu Oct  3 10:50:51 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 03 Oct 2019 14:50:51 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
In-Reply-To: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>
Message-ID: <1570114251.1.0.806496922095.issue38359@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

I know what this is - in issue38133 I added support for the PEP 514 ExecutablePath key, but didn't add a check for WindowedExecutablePath for the pyw.exe case.

I'll add it.

----------
assignee:  -> steve.dower
keywords: +3.8regression
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Thu Oct  3 10:56:38 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 03 Oct 2019 14:56:38 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
In-Reply-To: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>
Message-ID: <1570114598.01.0.4065493471.issue38359@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
nosy: +lukasz.langa
priority: normal -> release blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:09:12 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 03 Oct 2019 15:09:12 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
In-Reply-To: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>
Message-ID: <1570115352.35.0.930324422878.issue38359@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords: +patch
pull_requests: +16152
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16561

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:26:40 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 15:26:40 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570116400.28.0.439687875288.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset de3195c937d5fca0d79cc93dbafa76c0f89ca5b8 by Victor Stinner in branch '3.8':
[3.8] bpo-36670, regrtest: Fix WindowsLoadTracker() for partial line (GH-16550) (GH-16560)
https://github.com/python/cpython/commit/de3195c937d5fca0d79cc93dbafa76c0f89ca5b8


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:27:22 2019
From: report at bugs.python.org (Stephen Tucker)
Date: Thu, 03 Oct 2019 15:27:22 +0000
Subject: [issue38365] Issue 38363 - False Alarm - Sorry!
Message-ID: <CAP=-cKXE9rZEAA_OG_KrVObV-2VkTC4cDBHDNp67y54ru5P29w@mail.gmail.com>


New submission from Stephen Tucker <stephen_tucker at sil.org>:

Hi,

Issue 38363 is a false alarm - I am sorry to have wasted your time.

My mistake was that the file that had the BOM in it also had a space at the
end of the filename. I removed the space and the module was found OK.

Sorry again.

Stephen Tucker.

----------
messages: 353854
nosy: Stephen_Tucker
priority: normal
severity: normal
status: open
title: Issue 38363 - False Alarm - Sorry!

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38365>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:27:42 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 03 Oct 2019 15:27:42 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570116462.47.0.914893743545.issue36670@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16153
pull_request: https://github.com/python/cpython/pull/16562

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:31:09 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 03 Oct 2019 15:31:09 +0000
Subject: [issue38355] ntpath.realpath() fails on sys.executable
In-Reply-To: <1570055857.28.0.434394542652.issue38355@roundup.psfhosted.org>
Message-ID: <1570116669.42.0.0651030879537.issue38355@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset a0e3d27e4e3cb5b67e325df080fb18b70c2910cf by Steve Dower in branch 'master':
bpo-38355: Fix ntpath.realpath failing on sys.executable (GH-16551)
https://github.com/python/cpython/commit/a0e3d27e4e3cb5b67e325df080fb18b70c2910cf


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38355>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:31:23 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 03 Oct 2019 15:31:23 +0000
Subject: [issue38355] ntpath.realpath() fails on sys.executable
In-Reply-To: <1570055857.28.0.434394542652.issue38355@roundup.psfhosted.org>
Message-ID: <1570116683.34.0.968965388608.issue38355@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16154
pull_request: https://github.com/python/cpython/pull/16563

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38355>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:31:24 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 03 Oct 2019 15:31:24 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
In-Reply-To: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>
Message-ID: <1570116684.23.0.458482173691.issue38359@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 353fb1ecbfd58752dabae115c4964095e1e35e5f by Steve Dower in branch 'master':
bpo-38359: Ensures pyw.exe launcher reads correct registry key (GH-16561)
https://github.com/python/cpython/commit/353fb1ecbfd58752dabae115c4964095e1e35e5f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:31:37 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 15:31:37 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570116697.46.0.897926515603.issue36670@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Thanks for the bug report. I was impacted by the bug with my French locale as well.

I pushed a fix based on Lorenz Mende's work, with minor changes. I also enhanced WindowsLoadTracker to handle partial write and report parsing errors as warnings rather than exception.

I pushed other changes to enhance regrtest in general.

The load average is not updated every second and it's value is initialized from the arithmetic mean of the first 5 values of the Processor Queue Length.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:31:38 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 03 Oct 2019 15:31:38 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
In-Reply-To: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>
Message-ID: <1570116698.93.0.389132919631.issue38359@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16155
pull_request: https://github.com/python/cpython/pull/16564

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:38:49 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Thu, 03 Oct 2019 15:38:49 +0000
Subject: [issue38365] Issue 38363 - False Alarm - Sorry!
In-Reply-To: <CAP=-cKXE9rZEAA_OG_KrVObV-2VkTC4cDBHDNp67y54ru5P29w@mail.gmail.com>
Message-ID: <1570117129.23.0.0470257051156.issue38365@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Please don't create a *second* bug report to say that your previous bug report was erroneous. Just go and close the first one.

----------
nosy: +steven.daprano
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38365>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:41:03 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Thu, 03 Oct 2019 15:41:03 +0000
Subject: [issue38363] No Module named ..." and UTF-8 Byte Order Marks
In-Reply-To: <CAP=-cKWPrnrc7WpYcbLG99UVhTp0hC3bJbkJ3F8qiwqTuLR0aA@mail.gmail.com>
Message-ID: <1570117263.37.0.833183547386.issue38363@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

False alarm, see Stephen Tucker's message here

https://bugs.python.org/issue38365#msg353854

File name has a trailing space which is why it wasn't found.

----------
nosy: +steven.daprano
resolution:  -> works for me
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38363>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:44:56 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 03 Oct 2019 15:44:56 +0000
Subject: [issue36670] regrtest: win_utils decodes typeperf output from the
 wrong encoding (test suite broken due to cpu usage feature on win 10/ german)
In-Reply-To: <1555689157.38.0.435665423105.issue36670@roundup.psfhosted.org>
Message-ID: <1570117496.01.0.960185169767.issue36670@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset f9016e5fc9424d41c8e53de84f8699e78769a14a by Miss Islington (bot) in branch '3.7':
[3.8] bpo-36670, regrtest: Fix WindowsLoadTracker() for partial line (GH-16550) (GH-16560)
https://github.com/python/cpython/commit/f9016e5fc9424d41c8e53de84f8699e78769a14a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36670>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:49:59 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 03 Oct 2019 15:49:59 +0000
Subject: [issue38355] ntpath.realpath() fails on sys.executable
In-Reply-To: <1570055857.28.0.434394542652.issue38355@roundup.psfhosted.org>
Message-ID: <1570117799.63.0.174409735616.issue38355@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 6067e1d2bebccc2e73dd729d25c98df7bc9e2d59 by Miss Islington (bot) in branch '3.8':
bpo-38355: Fix ntpath.realpath failing on sys.executable (GH-16551)
https://github.com/python/cpython/commit/6067e1d2bebccc2e73dd729d25c98df7bc9e2d59


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38355>
_______________________________________

From report at bugs.python.org  Thu Oct  3 11:51:16 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 03 Oct 2019 15:51:16 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
In-Reply-To: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>
Message-ID: <1570117876.08.0.0861101739405.issue38359@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset e74fa70bcc379de1ce956273c5386fc8a7b9c5e6 by Miss Islington (bot) in branch '3.8':
bpo-38359: Ensures pyw.exe launcher reads correct registry key (GH-16561)
https://github.com/python/cpython/commit/e74fa70bcc379de1ce956273c5386fc8a7b9c5e6


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Thu Oct  3 12:11:43 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 03 Oct 2019 16:11:43 +0000
Subject: [issue38355] ntpath.realpath() fails on sys.executable
In-Reply-To: <1570055857.28.0.434394542652.issue38355@roundup.psfhosted.org>
Message-ID: <1570119103.82.0.890753840328.issue38355@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

This is resolved as far as I'm concerned - leaving open for ?ukasz to cherrypick and close.

----------
stage: patch review -> backport needed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38355>
_______________________________________

From report at bugs.python.org  Thu Oct  3 12:12:02 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 03 Oct 2019 16:12:02 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
In-Reply-To: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>
Message-ID: <1570119122.05.0.108169785157.issue38359@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

This is resolved as far as I'm concerned - leaving open for ?ukasz to cherrypick and close.

----------
stage: patch review -> backport needed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Thu Oct  3 12:19:59 2019
From: report at bugs.python.org (=?utf-8?q?Jonas_Sch=C3=A4fer?=)
Date: Thu, 03 Oct 2019 16:19:59 +0000
Subject: [issue14364] Argparse incorrectly handles '--' as argument to option
In-Reply-To: <1332080953.55.0.495639573781.issue14364@psf.upfronthosting.co.za>
Message-ID: <1570119599.38.0.907555341763.issue14364@roundup.psfhosted.org>


Jonas Sch?fer <jonas at zombofant.net> added the comment:

Since I have been adversely affected by this bug ([1]), I looked at the patches.

I combined issue14364.test.patch (which adds test cases for --foo=--) and dbldash.patch in my local working tree and that seems to resolve the issue (tests pass if and only if I apply dbldash.patch and my reproducer from [1]) passes too).

The patches do not contain any type of metainformation, so I?m not comfortable with submitting this as a PR. I am also not at all familiar with the process of managing the changelog etc.

This should serve as a confirmation that this issue can be resolved with the patches. Someone more familiar than me with the process could take up the task to get this merged.

Note: As you can see in [1], this issue has already caused data loss.

   [1]: https://github.com/borgbackup/borg/issues/4769

----------
nosy: +jssfr

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue14364>
_______________________________________

From report at bugs.python.org  Thu Oct  3 12:55:48 2019
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 03 Oct 2019 16:55:48 +0000
Subject: [issue38357] print adding extra bytes in hex above x7F
In-Reply-To: <1570066448.41.0.0345074372849.issue38357@roundup.psfhosted.org>
Message-ID: <1570121748.01.0.097256315748.issue38357@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

@Artificial please see the various blog posts and explanations about why the clear separation between bytes and text came to be and thus this change isn't "unnecessarily complicated".

----------
nosy: +brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38357>
_______________________________________

From report at bugs.python.org  Thu Oct  3 12:57:32 2019
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 03 Oct 2019 16:57:32 +0000
Subject: [issue37631] EXTRA_CFLAGS get overrided by CFLAGS_NODIST
In-Reply-To: <1563536952.58.0.764226132067.issue37631@roundup.psfhosted.org>
Message-ID: <1570121852.9.0.573408578008.issue37631@roundup.psfhosted.org>


Change by Brett Cannon <brett at python.org>:


----------
nosy:  -brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37631>
_______________________________________

From report at bugs.python.org  Thu Oct  3 13:55:56 2019
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 03 Oct 2019 17:55:56 +0000
Subject: [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1570125356.07.0.592113329314.issue32758@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +16156
pull_request: https://github.com/python/cpython/pull/16565

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32758>
_______________________________________

From report at bugs.python.org  Thu Oct  3 13:57:54 2019
From: report at bugs.python.org (Tim Peters)
Date: Thu, 03 Oct 2019 17:57:54 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1570125474.42.0.560324672845.issue38006@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

Loose ends.  Telegraphic because typing is hard.

1. Docs should be changed to encourage implementing the full gc protocol for "all" containers.  Spell out what can go wrong if they don't.  Be upfront about that history has, at times, proved us too optimistic about that ever since weakrefs were added.

2. Surprise finalizers (SF).  All weakrefs to trash objects were already cleared.  So if a SF can access trash, it must be via a chain of strong refs.  But in that case, they wouldn't be trash to begin with (since they're reachable from the SF, which is a S because we believed it wasn't trash).

So best optimistic guess is that only this can go wrong:  we promise that a finalizer will run at most once (even if the object is resurrected), but a SF neither records that it has been run nor recognizes that (if so) it's already been run.  IOW, a finalizer will be run at most once when it's not a surprise, but will run every time it is a SF.

3. get_objects() exposing invalid objects.  That's no good.  Not due to missing tp_traverse, but that the aggregate of trash objects revealed by tp_traverses exceed the aggregate of those reclaimed by tp_clears and subsequent refcounting.

Must not move invalids to older generation.  Move to new internal (to delete_garbage) list instead.  That list should be empty at delete_garbage's end.  If not, I'd be happy to die with a fatal runtime error.  Else, e.g.,

- add to count of trash objects that could not be collected

- append them to gc.garbage, each as the sole attribute of a new (say) `_GCInvalid` container, whose repr/str only shows the address of the invalid object.  So the top-level objects in gc.garbage remain valid, but the daring can access the invalid objects indirectly.  At least their type pointers should be intact.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Thu Oct  3 14:01:47 2019
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 03 Oct 2019 18:01:47 +0000
Subject: [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1570125707.07.0.949811390614.issue32758@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
pull_requests: +16157
pull_request: https://github.com/python/cpython/pull/16566

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32758>
_______________________________________

From report at bugs.python.org  Thu Oct  3 14:10:36 2019
From: report at bugs.python.org (Ned Deily)
Date: Thu, 03 Oct 2019 18:10:36 +0000
Subject: [issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent()
 Internal
In-Reply-To: <1569352841.72.0.766028949986.issue38266@roundup.psfhosted.org>
Message-ID: <1570126236.01.0.517695592249.issue38266@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Since this sounds like a regression being introduced by 3.8.0, should the reversion be included in 3.8.0 final or can it wait for 3.8.1?

----------
keywords: +3.8regression
nosy: +lukasz.langa, ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38266>
_______________________________________

From report at bugs.python.org  Thu Oct  3 14:11:15 2019
From: report at bugs.python.org (Paul Ganssle)
Date: Thu, 03 Oct 2019 18:11:15 +0000
Subject: [issue7980] time.strptime not thread safe
In-Reply-To: <1266835598.13.0.361031999331.issue7980@psf.upfronthosting.co.za>
Message-ID: <1570126275.39.0.663563198066.issue7980@roundup.psfhosted.org>


Paul Ganssle <p.ganssle at gmail.com> added the comment:

>From what I can tell, this is a Python 2.7-only bug, and it's not a security issue, so I think we can close the issue as either "wontfix" (because we won't fix it in Python 2) or "fixed" (because it is already fixed in Python 3), depending on your perspective.

----------
nosy: +p-ganssle

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue7980>
_______________________________________

From report at bugs.python.org  Thu Oct  3 14:12:30 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 03 Oct 2019 18:12:30 +0000
Subject: [issue26093] __qualname__ different when calling generator object w/
 functions.partial
In-Reply-To: <1452638028.1.0.595104762218.issue26093@psf.upfronthosting.co.za>
Message-ID: <1570126350.03.0.187910448544.issue26093@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

Python 3.9.0a0 (heads/bpo-31722:fc4a044a3c, Oct  4 2019, 03:10:14)
[Clang 11.0.0 (clang-1100.0.33.8)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import functools
>>> def f():
...     def g():
...         yield 1
...     return g
...
>>> functools.partial(f())().__qualname__ == f()().__qualname__
True
>>> functools.partial(f())().__qualname__
'f.<locals>.g'
>>> f()().__qualname__
'f.<locals>.g'

Looks like that this issue is fixed

----------
nosy: +corona10
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26093>
_______________________________________

From report at bugs.python.org  Thu Oct  3 14:30:19 2019
From: report at bugs.python.org (hongweipeng)
Date: Thu, 03 Oct 2019 18:30:19 +0000
Subject: [issue38337] inspect: getmembers calls properties
In-Reply-To: <1569931319.11.0.161787180553.issue38337@roundup.psfhosted.org>
Message-ID: <1570127419.08.0.976410524922.issue38337@roundup.psfhosted.org>


hongweipeng <hongweichen8888 at sina.com> added the comment:

The results of this example are different from mine(version 3.7.4).
```
__init__
--- getmembers from instance ---
Access property
[('__class__', <class '__main__.Example'>), ... ('var', 'Hello')]
--- getmembers from class    ---
[('__class__', <class 'type'>),'var', <property object at 0x>)]
```

----------
nosy: +hongweipeng

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38337>
_______________________________________

From report at bugs.python.org  Thu Oct  3 14:48:46 2019
From: report at bugs.python.org (Jonas Drotleff)
Date: Thu, 03 Oct 2019 18:48:46 +0000
Subject: [issue38337] inspect: getmembers calls properties
In-Reply-To: <1569931319.11.0.161787180553.issue38337@roundup.psfhosted.org>
Message-ID: <1570128526.43.0.183492827764.issue38337@roundup.psfhosted.org>


Jonas Drotleff <jonas.drotleff at gmail.com> added the comment:

> The results of this example are different from mine(version 3.7.4)

I do not really see any difference. What do you mean?

----------
nosy:  -Sanjay

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38337>
_______________________________________

From report at bugs.python.org  Thu Oct  3 14:50:59 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Thu, 03 Oct 2019 18:50:59 +0000
Subject: [issue36225] Lingering subinterpreters should be implicitly cleared
 on shutdown
In-Reply-To: <1551964663.69.0.686712846789.issue36225@roundup.psfhosted.org>
Message-ID: <1570128659.66.0.0113414519623.issue36225@roundup.psfhosted.org>


Joannah Nanjekye <nanjekyejoannah at gmail.com> added the comment:

I remember julien wanting to check this out during a discussion we had at the sprints hence the loop in.

----------
nosy: +mdk

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36225>
_______________________________________

From report at bugs.python.org  Thu Oct  3 15:37:10 2019
From: report at bugs.python.org (AWhetter)
Date: Thu, 03 Oct 2019 19:37:10 +0000
Subject: [issue34938] Fix mimetype.init() to account for from import
In-Reply-To: <1539036789.21.0.545547206417.issue34938@psf.upfronthosting.co.za>
Message-ID: <1570131430.13.0.14257265062.issue34938@roundup.psfhosted.org>


Change by AWhetter <ashley at awhetter.co.uk>:


----------
keywords: +patch
pull_requests: +16158
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16567

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34938>
_______________________________________

From report at bugs.python.org  Thu Oct  3 15:37:12 2019
From: report at bugs.python.org (Mario Corchero)
Date: Thu, 03 Oct 2019 19:37:12 +0000
Subject: [issue38346] Wrong behavior when using `assert_called_with` with
 mutable object
In-Reply-To: <1570006369.69.0.450054962888.issue38346@roundup.psfhosted.org>
Message-ID: <1570131432.92.0.908430559237.issue38346@roundup.psfhosted.org>


Mario Corchero <mariocj89 at gmail.com> added the comment:

This might be painful in certain scenarios, like when using wraps on functions that modify the arguments:

```
def func(d):
  return d.pop("key")
>>> def func(d):
...   return d.pop("key")
...
>>> m = Mock(wraps=func)
>>> m({"key": 1})
1
>>> m.assert_called_with({"key": 1})
#raises
```

But I think "not fixing" this through copy is reasonable, especially when doing copy can also break assertions on objects that cannot be copied, which can happen if they implement their own __copy__ and some other situations. Additionally, copy does not fully capture "the value of the object when it was passed" for custom types.

A copying mock was published under pypi in https://github.com/wimglenn/copyingmock but doesn't seem to get a lot of attention, if this was interesting by users it could be added as a new type of Mock, or maybe just a mixin that users could add to any existing mock if they wished.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38346>
_______________________________________

From report at bugs.python.org  Thu Oct  3 16:52:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 20:52:20 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1570135940.06.0.102419940344.issue38006@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> 1. Docs should be changed to encourage implementing the full gc protocol for "all" containers.  Spell out what can go wrong if they don't.  Be upfront about that history has, at times, proved us too optimistic about that ever since weakrefs were added.

Would it make any sense to add an opt-in option to emit a warning when a new type is created with Py_TPFLAGS_HAVE_GC but it doesn't implement tp_traverse? Maybe also emit a warning if it doesn't implement tp_clear?

Maybe it could be a ResourceWarning emitted in development mode, when -X dev is used on the command line.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Thu Oct  3 16:58:15 2019
From: report at bugs.python.org (Eddie Elizondo)
Date: Thu, 03 Oct 2019 20:58:15 +0000
Subject: [issue38140] Py_tp_dictoffset / Py_tp_finalize are unsettable in
 stable API
In-Reply-To: <1568297060.68.0.400472303762.issue38140@roundup.psfhosted.org>
Message-ID: <1570136295.17.0.679814357012.issue38140@roundup.psfhosted.org>


Eddie Elizondo <eduardo.elizondorueda at gmail.com> added the comment:

Woops, just realized that you already documented this, thanks! Btw, Victor already merged a fix for the windows compiler warning. This issue can be closed now

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38140>
_______________________________________

From report at bugs.python.org  Thu Oct  3 17:02:12 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 21:02:12 +0000
Subject: [issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent()
 Internal
In-Reply-To: <1569352841.72.0.766028949986.issue38266@roundup.psfhosted.org>
Message-ID: <1570136532.12.0.431200883698.issue38266@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Since this sounds like a regression being introduced by 3.8.0, should the reversion be included in 3.8.0 final or can it wait for 3.8.1?

IMHO PR 16558 is safe: it adds code which already existed in Python 2.7, and likely previously. For me it's a low risk of regression between rc1 and final.

I set the priority to release blocker, but Lukasz is the last one to take the final decision on including the fix or not.

Well, right now, I don't consider that PR 16558 is ready to be merged.

----------
priority: normal -> release blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38266>
_______________________________________

From report at bugs.python.org  Thu Oct  3 17:08:34 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Thu, 03 Oct 2019 21:08:34 +0000
Subject: [issue34344] Fix the docstring for
 AbstractEventLoopPolicy.get_event_loop
In-Reply-To: <1533549887.39.0.56676864532.issue34344@psf.upfronthosting.co.za>
Message-ID: <1570136914.7.0.286310021312.issue34344@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:


New changeset b23a8423a923077e4f83d3f328bb7542b4c940ed by Yury Selivanov (idomic) in branch 'master':
bpo-34344 Fix AbstractEventLoopPolicy.get_event_loop docstring (GH-16463)
https://github.com/python/cpython/commit/b23a8423a923077e4f83d3f328bb7542b4c940ed


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34344>
_______________________________________

From report at bugs.python.org  Thu Oct  3 17:09:03 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 03 Oct 2019 21:09:03 +0000
Subject: [issue34344] Fix the docstring for
 AbstractEventLoopPolicy.get_event_loop
In-Reply-To: <1533549887.39.0.56676864532.issue34344@psf.upfronthosting.co.za>
Message-ID: <1570136943.62.0.912979664572.issue34344@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16159
pull_request: https://github.com/python/cpython/pull/16568

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34344>
_______________________________________

From report at bugs.python.org  Thu Oct  3 17:09:10 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 03 Oct 2019 21:09:10 +0000
Subject: [issue34344] Fix the docstring for
 AbstractEventLoopPolicy.get_event_loop
In-Reply-To: <1533549887.39.0.56676864532.issue34344@psf.upfronthosting.co.za>
Message-ID: <1570136950.56.0.0231489820159.issue34344@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16160
pull_request: https://github.com/python/cpython/pull/16569

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34344>
_______________________________________

From report at bugs.python.org  Thu Oct  3 17:17:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 21:17:03 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570137423.21.0.650416398047.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 86ec5c65fe04ece16f3aada5292cc62726062ad0 by Victor Stinner in branch 'master':
bpo-38353: Fix calculate_argv0_path() for symlinks (GH-16549)
https://github.com/python/cpython/commit/86ec5c65fe04ece16f3aada5292cc62726062ad0


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct  3 17:19:12 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 21:19:12 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570137552.46.0.218130973595.issue38353@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16161
pull_request: https://github.com/python/cpython/pull/16570

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct  3 17:27:00 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 03 Oct 2019 21:27:00 +0000
Subject: [issue34344] Fix the docstring for
 AbstractEventLoopPolicy.get_event_loop
In-Reply-To: <1533549887.39.0.56676864532.issue34344@psf.upfronthosting.co.za>
Message-ID: <1570138020.25.0.814073214411.issue34344@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 8edde5caabc611c6320fd104244abe3a409cf0b6 by Miss Islington (bot) in branch '3.8':
bpo-34344 Fix AbstractEventLoopPolicy.get_event_loop docstring (GH-16463)
https://github.com/python/cpython/commit/8edde5caabc611c6320fd104244abe3a409cf0b6


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34344>
_______________________________________

From report at bugs.python.org  Thu Oct  3 17:27:38 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 03 Oct 2019 21:27:38 +0000
Subject: [issue34344] Fix the docstring for
 AbstractEventLoopPolicy.get_event_loop
In-Reply-To: <1533549887.39.0.56676864532.issue34344@psf.upfronthosting.co.za>
Message-ID: <1570138058.75.0.771520296468.issue34344@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 4de3fbe27f672dcd9c24d3e99258f39b12c365a5 by Miss Islington (bot) in branch '3.7':
bpo-34344 Fix AbstractEventLoopPolicy.get_event_loop docstring (GH-16463)
https://github.com/python/cpython/commit/4de3fbe27f672dcd9c24d3e99258f39b12c365a5


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34344>
_______________________________________

From report at bugs.python.org  Thu Oct  3 17:59:26 2019
From: report at bugs.python.org (jacksmait)
Date: Thu, 03 Oct 2019 21:59:26 +0000
Subject: [issue32545] Unable to install Python 3.7.0a4 on Windows 10 - Error
 0x80070643: Failed to install MSI package.
In-Reply-To: <1515875653.34.0.467229070634.issue32545@psf.upfronthosting.co.za>
Message-ID: <1570139966.7.0.465469203294.issue32545@roundup.psfhosted.org>


jacksmait <jacksmait005 at gmail.com> added the comment:

if you are facing problem with printer problems then click on http://www.printertechsupportphonenumbers.com/printer-driver-support/ and get solution of windows 10 printer driver is unavailable, printer driver is unavailable and etc or free contact us at +1-866-760-2639

----------
nosy: +jacksmait

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32545>
_______________________________________

From report at bugs.python.org  Thu Oct  3 18:34:54 2019
From: report at bugs.python.org (AWhetter)
Date: Thu, 03 Oct 2019 22:34:54 +0000
Subject: [issue38235] Docs of logging module says argument is named "lvl".
 TypeError.
In-Reply-To: <1568996817.83.0.32795106699.issue38235@roundup.psfhosted.org>
Message-ID: <1570142094.64.0.382601182001.issue38235@roundup.psfhosted.org>


Change by AWhetter <ashley at awhetter.co.uk>:


----------
keywords: +patch
pull_requests: +16162
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16571

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38235>
_______________________________________

From report at bugs.python.org  Thu Oct  3 18:35:15 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 03 Oct 2019 22:35:15 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1570142115.13.0.0788178125664.issue38006@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:

> Would it make any sense to add an opt-in option to emit a warning when a new type is created with Py_TPFLAGS_HAVE_GC but it doesn't implement tp_traverse?

Or even fatal error out?  There's no reason to have Py_TPFLAGS_HAVE_GC but not implement tp_traverse, AFAIR.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Thu Oct  3 18:41:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 22:41:55 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1570142515.57.0.762510366253.issue38006@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Or even fatal error out?  There's no reason to have Py_TPFLAGS_HAVE_GC but not implement tp_traverse, AFAIR.

Well... It would prefer a smooth transition.

Such sanity checks which mostly concerns developers perfectly fit the -X dev mode.

I mean, calling Py_FatalError() only in development mode would be acceptable, rather than blocking the usage of C extensions which are working "perfectly well" on Python 3.7.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Thu Oct  3 18:43:14 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 22:43:14 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570142594.78.0.276896692933.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset c515b573af1189fc46ddcd3323c53ed073b84848 by Victor Stinner in branch 'master':
bpo-38353: Fix compiler warning in pycore_initconfig.h (GH-16570)
https://github.com/python/cpython/commit/c515b573af1189fc46ddcd3323c53ed073b84848


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct  3 18:46:03 2019
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 03 Oct 2019 22:46:03 +0000
Subject: [issue32545] Unable to install Python 3.7.0a4 on Windows 10 - Error
 0x80070643: Failed to install MSI package.
In-Reply-To: <1515875653.34.0.467229070634.issue32545@psf.upfronthosting.co.za>
Message-ID: <1570142763.66.0.384200634823.issue32545@roundup.psfhosted.org>


Change by Zachary Ware <zachary.ware at gmail.com>:


----------
Removed message: https://bugs.python.org/msg353882

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32545>
_______________________________________

From report at bugs.python.org  Thu Oct  3 18:48:54 2019
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 03 Oct 2019 22:48:54 +0000
Subject: [issue32545] Unable to install Python 3.7.0a4 on Windows 10 - Error
 0x80070643: Failed to install MSI package.
In-Reply-To: <1515875653.34.0.467229070634.issue32545@psf.upfronthosting.co.za>
Message-ID: <1570142934.19.0.381293424566.issue32545@roundup.psfhosted.org>


Change by Zachary Ware <zachary.ware at gmail.com>:


----------
hgrepos:  -383

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32545>
_______________________________________

From report at bugs.python.org  Thu Oct  3 18:50:33 2019
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 03 Oct 2019 22:50:33 +0000
Subject: [issue32545] Unable to install Python 3.7.0a4 on Windows 10 - Error
 0x80070643: Failed to install MSI package.
In-Reply-To: <1515875653.34.0.467229070634.issue32545@psf.upfronthosting.co.za>
Message-ID: <1570143033.48.0.38042962506.issue32545@roundup.psfhosted.org>


Change by Zachary Ware <zachary.ware at gmail.com>:


----------
Removed message: https://bugs.python.org/msg345856

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32545>
_______________________________________

From report at bugs.python.org  Thu Oct  3 18:52:26 2019
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 03 Oct 2019 22:52:26 +0000
Subject: [issue32545] Unable to install Python 3.7.0a4 on Windows 10 - Error
 0x80070643: Failed to install MSI package.
In-Reply-To: <1515875653.34.0.467229070634.issue32545@psf.upfronthosting.co.za>
Message-ID: <1570143146.51.0.591533216813.issue32545@roundup.psfhosted.org>


Change by Zachary Ware <zachary.ware at gmail.com>:


----------
nosy:  -Printer Setup, jacksmait, prince_parker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32545>
_______________________________________

From report at bugs.python.org  Thu Oct  3 18:52:36 2019
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 03 Oct 2019 22:52:36 +0000
Subject: [issue32545] Unable to install Python 3.7.0a4 on Windows 10 - Error
 0x80070643: Failed to install MSI package.
In-Reply-To: <1515875653.34.0.467229070634.issue32545@psf.upfronthosting.co.za>
Message-ID: <1570143156.53.0.719895785497.issue32545@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:

This issue seems to have become a spam magnet, so I'm clearing the nosy list to keep it out of our inboxes.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32545>
_______________________________________

From report at bugs.python.org  Thu Oct  3 18:52:43 2019
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 03 Oct 2019 22:52:43 +0000
Subject: [issue32545] Unable to install Python 3.7.0a4 on Windows 10 - Error
 0x80070643: Failed to install MSI package.
In-Reply-To: <1515875653.34.0.467229070634.issue32545@psf.upfronthosting.co.za>
Message-ID: <1570143163.26.0.149042597062.issue32545@roundup.psfhosted.org>


Change by Zachary Ware <zachary.ware at gmail.com>:


----------
nosy:  -Amin Radjabov, chipstuff, emniclap, mwr256, paul.moore, steve.dower, taleinat, terry.reedy, tim.golden, zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32545>
_______________________________________

From report at bugs.python.org  Thu Oct  3 19:04:49 2019
From: report at bugs.python.org (Io Mintz)
Date: Thu, 03 Oct 2019 23:04:49 +0000
Subject: [issue38366] dataclasses: generate the _hash_action table from the
 if-else tree
Message-ID: <1570143889.18.0.0994959118678.issue38366@roundup.psfhosted.org>


New submission from Io Mintz <benjabean1 at gmail.com>:

The dataclasses._hash_action table is currently a bit hard to read. It could be generated once from the if-else tree written in https://bugs.python.org/issue32929#msg312829 instead, which would both be easier to read and easier to maintain, while still maintaining the efficiency of the current dictionary.

----------
components: Library (Lib)
messages: 353887
nosy: iomintz
priority: normal
pull_requests: 16163
severity: normal
status: open
title: dataclasses: generate the _hash_action table from the if-else tree
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38366>
_______________________________________

From report at bugs.python.org  Thu Oct  3 19:12:27 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 23:12:27 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570144347.16.0.786762456783.issue38353@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16164
pull_request: https://github.com/python/cpython/pull/16572

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct  3 19:35:27 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 03 Oct 2019 23:35:27 +0000
Subject: [issue38366] dataclasses: generate the _hash_action table from the
 if-else tree
In-Reply-To: <1570143889.18.0.0994959118678.issue38366@roundup.psfhosted.org>
Message-ID: <1570145727.66.0.823375627429.issue38366@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

I don't see that as an improvement, especially when the goal is to not change any functionality.

But maybe I'm just used to truth tables. To me, the truth table makes it clear that each case is handled correctly.

----------
assignee:  -> eric.smith
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38366>
_______________________________________

From report at bugs.python.org  Thu Oct  3 19:55:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 03 Oct 2019 23:55:53 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570146953.57.0.721987121588.issue38353@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16165
pull_request: https://github.com/python/cpython/pull/16573

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct  3 20:10:22 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 00:10:22 +0000
Subject: [issue38367] test_regrtest hanged on AMD64 Windows10 3.x
Message-ID: <1570147821.98.0.530432590053.issue38367@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

https://buildbot.python.org/all/#/builders/3/builds/3617

...
0:25:50 load avg: 0.00 running: test_regrtest (13 min 48 sec)
0:26:20 load avg: 0.00 running: test_regrtest (14 min 18 sec)
0:26:50 load avg: 0.00 running: test_regrtest (14 min 48 sec)
0:27:02 load avg: 0.00 [419/419/1] test_regrtest crashed (Exit code 1)

(...)

0:27:02 load avg: 0.00 Re-running failed tests in verbose mode
0:27:02 load avg: 0.00 Re-running test_regrtest in verbose mode

Timeout (0:15:00)!
Thread 0x00002ee0 (most recent call first):
  File "D:\buildarea\3.x.bolen-windows10\build\lib\subprocess.py", line 1457 in _readerthread
  File "D:\buildarea\3.x.bolen-windows10\build\lib\threading.py", line 882 in run
  File "D:\buildarea\3.x.bolen-windows10\build\lib\threading.py", line 944 in _bootstrap_inner
  File "D:\buildarea\3.x.bolen-windows10\build\lib\threading.py", line 902 in _bootstrap

Thread 0x00002140 (most recent call first):
  File "D:\buildarea\3.x.bolen-windows10\build\lib\threading.py", line 1039 in _wait_for_tstate_lock
  File "D:\buildarea\3.x.bolen-windows10\build\lib\threading.py", line 1023 in join
  File "D:\buildarea\3.x.bolen-windows10\build\lib\subprocess.py", line 1486 in _communicate
  File "D:\buildarea\3.x.bolen-windows10\build\lib\subprocess.py", line 1113 in communicate
  File "D:\buildarea\3.x.bolen-windows10\build\lib\subprocess.py", line 499 in run
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\test_regrtest.py", line 504 in run_command
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\test_regrtest.py", line 529 in run_python
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\test_regrtest.py", line 584 in run_tests
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\test_regrtest.py", line 610 in test_module_autotest
  File "D:\buildarea\3.x.bolen-windows10\build\lib\unittest\case.py", line 616 in _callTestMethod
  File "D:\buildarea\3.x.bolen-windows10\build\lib\unittest\case.py", line 659 in run
  File "D:\buildarea\3.x.bolen-windows10\build\lib\unittest\case.py", line 719 in __call__
  File "D:\buildarea\3.x.bolen-windows10\build\lib\unittest\suite.py", line 122 in run
  File "D:\buildarea\3.x.bolen-windows10\build\lib\unittest\suite.py", line 84 in __call__
  File "D:\buildarea\3.x.bolen-windows10\build\lib\unittest\suite.py", line 122 in run
  File "D:\buildarea\3.x.bolen-windows10\build\lib\unittest\suite.py", line 84 in __call__
  File "D:\buildarea\3.x.bolen-windows10\build\lib\unittest\suite.py", line 122 in run
  File "D:\buildarea\3.x.bolen-windows10\build\lib\unittest\suite.py", line 84 in __call__
  File "D:\buildarea\3.x.bolen-windows10\build\lib\unittest\runner.py", line 176 in run
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\support\__init__.py", line 2032 in _run_suite
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\support\__init__.py", line 2128 in run_unittest
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\runtest.py", line 209 in _test_module
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\runtest.py", line 234 in _runtest_inner2
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\runtest.py", line 270 in _runtest_inner
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\runtest.py", line 140 in _runtest
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\runtest.py", line 193 in runtest
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\runtest_mp.py", line 67 in run_tests_worker
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\main.py", line 654 in _main
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\main.py", line 634 in main
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\main.py", line 712 in main
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\regrtest.py", line 43 in _main
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\regrtest.py", line 47 in <module>
  File "D:\buildarea\3.x.bolen-windows10\build\lib\runpy.py", line 85 in _run_code
  File "D:\buildarea\3.x.bolen-windows10\build\lib\runpy.py", line 192 in _run_module_as_main

(...)

1 re-run test:
    test_regrtest

Total duration: 27 min 35 sec
Tests result: FAILURE then SUCCESS


Traceback (most recent call last):
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\support\__init__.py", line 1049, in temp_dir
    yield path
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\support\__init__.py", line 1101, in temp_cwd
    yield cwd_dir
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\main.py", line 634, in main
    self._main(tests, kwargs)
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\libregrtest\main.py", line 707, in _main
    sys.exit(0)
SystemExit: 0

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\buildarea\3.x.bolen-windows10\build\lib\test\support\__init__.py", line 336, in _force_run
    return func(*args)
PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'D:\\buildarea\\3.x.bolen-windows10\\build\\build\\test_python_9260\\test_python_worker_11168'

----------
components: Tests
messages: 353889
nosy: vstinner
priority: normal
severity: normal
status: open
title: test_regrtest hanged on AMD64 Windows10 3.x
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38367>
_______________________________________

From report at bugs.python.org  Thu Oct  3 20:20:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 00:20:42 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570148442.05.0.425648053264.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

On my Fedora 30, GCC doesn't complain on "typedef struct pyruntimestate _PyRuntimeState;". But clang on macOS emits a warning, saying that it's C11-only feature. So I modified the internal header files to use "struct pyruntimestate" instead, to avoid any compilation issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct  3 20:21:10 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 00:21:10 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570148470.87.0.919112704148.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset e982d8b64f5d358c578bfca5cdfe4524dbc74000 by Victor Stinner in branch 'master':
bpo-38353: Fix compiler warning in internal headers (GH-16573)
https://github.com/python/cpython/commit/e982d8b64f5d358c578bfca5cdfe4524dbc74000


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct  3 20:22:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 00:22:42 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570148562.13.0.309688512976.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 03a8a56faca0c1851051269e3517d70cbce830b7 by Victor Stinner in branch 'master':
bpo-38353: Add subfunctions to getpath.c (GH-16572)
https://github.com/python/cpython/commit/03a8a56faca0c1851051269e3517d70cbce830b7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct  3 20:50:01 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 00:50:01 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570150201.12.0.521027844749.issue38353@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16166
pull_request: https://github.com/python/cpython/pull/16574

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct  3 20:50:33 2019
From: report at bugs.python.org (AWhetter)
Date: Fri, 04 Oct 2019 00:50:33 +0000
Subject: [issue37700] shutil.copyfile does not raise SpecialFileError for
 socket files
In-Reply-To: <1564374136.89.0.594392746042.issue37700@roundup.psfhosted.org>
Message-ID: <1570150233.7.0.845334329595.issue37700@roundup.psfhosted.org>


Change by AWhetter <ashley at awhetter.co.uk>:


----------
keywords: +patch
pull_requests: +16167
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16575

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37700>
_______________________________________

From report at bugs.python.org  Thu Oct  3 21:53:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 01:53:32 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570154012.12.0.846389463558.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset f0c85793d2a087974969f7eea6ca24bbd1178d53 by Victor Stinner in branch 'master':
bpo-38353: Rework ismodule() in getpath.c (GH-16574)
https://github.com/python/cpython/commit/f0c85793d2a087974969f7eea6ca24bbd1178d53


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct  3 22:02:00 2019
From: report at bugs.python.org (Jim Jeon)
Date: Fri, 04 Oct 2019 02:02:00 +0000
Subject: [issue38346] Wrong behavior when using `assert_called_with` with
 mutable object
In-Reply-To: <1570006369.69.0.450054962888.issue38346@roundup.psfhosted.org>
Message-ID: <1570154520.98.0.545459767686.issue38346@roundup.psfhosted.org>


Jim Jeon <jimjeon.me at gmail.com> added the comment:

Thank you all for the kind answers.
I didn't know copying could cause so many problems.

@veky
Thank you for the example.
But it seems that the example will actually raise and I think it should.
I am talking f.assert_called_with(b) when `b` has same values of `a` before it is mutated. I thought the function's purpose is to check values of the exact moment the function is called.

@xtreak
Thanks for the related issue. I didn't consider `identity comparison` situations. Definitely that could cause problems.

@mariocj89
> copy does not fully capture "the value of the object when it was passed" for custom types.
Thank you for the kind answer, it was really helpful to me. Now I understand why copying is so dangerous.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38346>
_______________________________________

From report at bugs.python.org  Thu Oct  3 22:35:35 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 04 Oct 2019 02:35:35 +0000
Subject: [issue38350] ./configure --with-pydebug should use -O0 rather than -Og
In-Reply-To: <1570034107.68.0.232468214894.issue38350@roundup.psfhosted.org>
Message-ID: <1570156535.93.0.432570068268.issue38350@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
versions:  -Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38350>
_______________________________________

From report at bugs.python.org  Thu Oct  3 23:16:04 2019
From: report at bugs.python.org (hongweipeng)
Date: Fri, 04 Oct 2019 03:16:04 +0000
Subject: [issue38337] inspect: getmembers calls properties
In-Reply-To: <1569931319.11.0.161787180553.issue38337@roundup.psfhosted.org>
Message-ID: <1570158964.2.0.923258276009.issue38337@roundup.psfhosted.org>


hongweipeng <hongweichen8888 at sina.com> added the comment:

I mean why member `__class__` is expected to be `<attribute '__class__'...>)`. I check PR16521,for __class__, it always gets `<attribute '__class__'...>)`.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38337>
_______________________________________

From report at bugs.python.org  Thu Oct  3 23:40:38 2019
From: report at bugs.python.org (Tim Peters)
Date: Fri, 04 Oct 2019 03:40:38 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1570160438.43.0.957480685974.issue38006@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

My understanding is that the CFFI types at issue don't even have Py_TPFLAGS_HAVE_GC.  They're completely invisible to gc.  As Armin says in the CFFI issue report (linked to earlier), he never got the impression from the docs that he needed to implement anything related to cyclic gc.

Since Armin is extremely capable, conscientious, and reasonable, that tells me our docs are lacking.

It was intended at the start that the worst that could happen if a type ignored the gc protocols was that memory may leak.  That story changed radically when weakrefs with callbacks were added - but nobody knew it at the time because the weakref design gave no thought to cyclic gc.  It's been driven by segfaults ever since ;-)

We're doing all we can to keep non-cooperating code "working", and will continue to do so.  But who knows?  The next segfault may be one we can't hack around.  It's fundamentally insane to expect any gc to work perfectly when it may be blind to what the object graph _is_.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Fri Oct  4 01:02:50 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Oct 2019 05:02:50 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570165370.43.0.773212039953.issue13153@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

A week ago, I thought that the astral solution was to always replace with the \U escape.  With this patch, we can and should send them to read-only text windows, and let the OS and font display it or a substitute.  On Windows, at least, the emoji which beginners most often want to use get displayed.

Elsewhere, we will have to check and do some follow-up patches.  For using file names with astral chars results, on Windows, in six large boxes, and when the file is saved, it is saved in a new file with the boxes, not the original file.  Such file names are not added to the recent files list, or maybe list boxes cannot handle them.

Code is another issue.  Astral chars in files could be replaced when read.  Unfortunately, I believe some are legal identifier chars.  On the clipboard, on Windows, astral chars become sequences of 6 surrogates.

>>> r.clipboard_clear()
>>> r.clipboard_append('?')
>>> r.clipboard_get()
'\udced\udca0\udcbd\udced\udcba\udc80'

Perhaps we should try to intercept paste and replace such sequences with the \U escape.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 01:50:36 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 05:50:36 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570168236.69.0.242533073381.issue13153@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Thank you for your example Terry. There was one dubious place which I did not change because I did not know how to trigger the execution of it. Now the clipboard is fixed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 02:39:44 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 04 Oct 2019 06:39:44 +0000
Subject: [issue38366] dataclasses: generate the _hash_action table from the
 if-else tree
In-Reply-To: <1570143889.18.0.0994959118678.issue38366@roundup.psfhosted.org>
Message-ID: <1570171184.63.0.040148741343.issue38366@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I concur with Eric.  The original code is preferable.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38366>
_______________________________________

From report at bugs.python.org  Fri Oct  4 02:40:32 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 04 Oct 2019 06:40:32 +0000
Subject: [issue38235] Docs of logging module says argument is named "lvl".
 TypeError.
In-Reply-To: <1568996817.83.0.32795106699.issue38235@roundup.psfhosted.org>
Message-ID: <1570171232.36.0.0921803457276.issue38235@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee: rhettinger -> vinay.sajip

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38235>
_______________________________________

From report at bugs.python.org  Fri Oct  4 02:49:31 2019
From: report at bugs.python.org (Jonas Drotleff)
Date: Fri, 04 Oct 2019 06:49:31 +0000
Subject: [issue38337] inspect: getmembers calls properties
In-Reply-To: <1569931319.11.0.161787180553.issue38337@roundup.psfhosted.org>
Message-ID: <1570171771.67.0.0518759124881.issue38337@roundup.psfhosted.org>


Jonas Drotleff <jonas.drotleff at gmail.com> added the comment:

Oh, yes I see what you mean. That's my fault, it seems like I copied the wrong line. Sorry.

But the important piece is the 'var' attribute. Sorry for the confusion.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38337>
_______________________________________

From report at bugs.python.org  Fri Oct  4 03:42:28 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Oct 2019 07:42:28 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570174948.44.0.481490988073.issue13153@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

What do you mean by fixed?  After deleting and remaking a pr_16545 branch, I see the same result for clipboard_get.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 03:55:19 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 04 Oct 2019 07:55:19 +0000
Subject: [issue38235] Docs of logging module says argument is named "lvl".
 TypeError.
In-Reply-To: <1568996817.83.0.32795106699.issue38235@roundup.psfhosted.org>
Message-ID: <1570175719.46.0.265645187671.issue38235@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset 3142c667b50254daaa28f22c79bdda177136bd03 by Vinay Sajip (Ashley Whetter) in branch 'master':
bpo-38235: Correct some arguments names in logging documentation (GH-16571)
https://github.com/python/cpython/commit/3142c667b50254daaa28f22c79bdda177136bd03


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38235>
_______________________________________

From report at bugs.python.org  Fri Oct  4 04:00:07 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Oct 2019 08:00:07 +0000
Subject: [issue38235] Docs of logging module says argument is named "lvl".
 TypeError.
In-Reply-To: <1568996817.83.0.32795106699.issue38235@roundup.psfhosted.org>
Message-ID: <1570176007.43.0.973683982715.issue38235@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16168
pull_request: https://github.com/python/cpython/pull/16576

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38235>
_______________________________________

From report at bugs.python.org  Fri Oct  4 04:00:21 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Oct 2019 08:00:21 +0000
Subject: [issue38235] Docs of logging module says argument is named "lvl".
 TypeError.
In-Reply-To: <1568996817.83.0.32795106699.issue38235@roundup.psfhosted.org>
Message-ID: <1570176021.28.0.415220179102.issue38235@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16169
pull_request: https://github.com/python/cpython/pull/16577

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38235>
_______________________________________

From report at bugs.python.org  Fri Oct  4 04:08:55 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 08:08:55 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570176535.2.0.499987015581.issue13153@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

What is the result of new tests?

    python.bat -m test -v -uall test_tk -m test_clipboard*

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 04:14:04 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 04 Oct 2019 08:14:04 +0000
Subject: [issue38235] Docs of logging module says argument is named "lvl".
 TypeError.
In-Reply-To: <1568996817.83.0.32795106699.issue38235@roundup.psfhosted.org>
Message-ID: <1570176844.18.0.771397643736.issue38235@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset 3af2733a8265a2685b2c0466a58a66e544a81c64 by Vinay Sajip (Miss Islington (bot)) in branch '3.8':
bpo-38235: Correct some arguments names in logging documentation (GH-16571) (GH-16576)
https://github.com/python/cpython/commit/3af2733a8265a2685b2c0466a58a66e544a81c64


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38235>
_______________________________________

From report at bugs.python.org  Fri Oct  4 04:14:31 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 04 Oct 2019 08:14:31 +0000
Subject: [issue38235] Docs of logging module says argument is named "lvl".
 TypeError.
In-Reply-To: <1568996817.83.0.32795106699.issue38235@roundup.psfhosted.org>
Message-ID: <1570176871.39.0.164527643491.issue38235@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset 4f82a53c5d34df00bf2d563c2417f5e2638d1004 by Vinay Sajip (Miss Islington (bot)) in branch '3.7':
bpo-38235: Correct some arguments names in logging documentation (GH-16571) (GH-16577)
https://github.com/python/cpython/commit/4f82a53c5d34df00bf2d563c2417f5e2638d1004


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38235>
_______________________________________

From report at bugs.python.org  Fri Oct  4 04:15:04 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 04 Oct 2019 08:15:04 +0000
Subject: [issue38235] Docs of logging module says argument is named "lvl".
 TypeError.
In-Reply-To: <1568996817.83.0.32795106699.issue38235@roundup.psfhosted.org>
Message-ID: <1570176904.2.0.462157104658.issue38235@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions:  -Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38235>
_______________________________________

From report at bugs.python.org  Fri Oct  4 04:36:01 2019
From: report at bugs.python.org (Doug O'Riordan)
Date: Fri, 04 Oct 2019 08:36:01 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
Message-ID: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>


New submission from Doug O'Riordan <oriordan at biztosan.hu>:

Ran into Segfaults while trying to use pysnmp with 3.8.0rc1.
The code is running fine on 3.8.0b04.

$ python3.8
Python 3.8.0rc1 (default, Oct  2 2019, 14:15:18)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ctypes
>>> class in6_addr_U(ctypes.Union):
...     _fields_ = [
...         ('__u6_addr8', ctypes.c_uint8 * 16),
...         ('__u6_addr16', ctypes.c_uint16 * 8),
...         ('__u6_addr32', ctypes.c_uint32 * 4),
...     ]
...
Segmentation fault

$ docker run -it python:3.8.0rc1-slim
Python 3.8.0rc1 (default, Oct  2 2019, 23:38:42)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ctypes
>>> class in6_addr_U(ctypes.Union):
...     _fields_ = [
...         ('__u6_addr8', ctypes.c_uint8 * 16),
...         ('__u6_addr16', ctypes.c_uint16 * 8),
...         ('__u6_addr32', ctypes.c_uint32 * 4),
...     ]
...
$

The code is from here: https://github.com/etingof/pysnmp/blob/master/pysnmp/carrier/sockmsg.py#L47-L52

----------
components: ctypes
messages: 353906
nosy: oriordan
priority: normal
severity: normal
status: open
title: Crash when subclassing ctypes.Union
type: crash
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Fri Oct  4 04:40:20 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 04 Oct 2019 08:40:20 +0000
Subject: [issue38354] Fix for bug 30378 regressed SysLogHandler by making it
 resolve addresses at initialization instead of in `.emit()`
In-Reply-To: <1570051932.55.0.313239800858.issue38354@roundup.psfhosted.org>
Message-ID: <1570178420.22.0.603813885681.issue38354@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

This could perhaps be handled by just swallowing errors in the constructor (as is done for Unix sockets, for example) and trying to connect in emit() if there is no connection.

Not sure I want to go down the caching route - it complicates things for what is a rare use case, plus raises the question of allowing configurable timeouts for the cache, etc.

This seems a rare use case, so I have things that have a higher priority on my list of things to do, but I'll certainly review a patch to address this.

----------
versions:  -Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38354>
_______________________________________

From report at bugs.python.org  Fri Oct  4 04:53:26 2019
From: report at bugs.python.org (Arminius)
Date: Fri, 04 Oct 2019 08:53:26 +0000
Subject: [issue35212] Expressions with format specifiers in f-strings give
 wrong code position in AST
In-Reply-To: <1541939640.9.0.788709270274.issue35212@psf.upfronthosting.co.za>
Message-ID: <1570179206.67.0.660570991885.issue35212@roundup.psfhosted.org>


Arminius <numirias at gmail.com> added the comment:

There is another instance of incorrectly reported offsets in f-strings, in this case affecting multi-line strings.

Example:

(
    f'aaa{foo}bbb'
    f'ccc{bar}ddd'
    f'eee{baz}fff'
)

Relevant part of the syntax tree:

JoinedStr(
    lineno=2,
    col_offset=4,
    values=[
        Str(lineno=2, col_offset=4, s='aaa'),
        FormattedValue(
            lineno=2,
            col_offset=4,
            value=Name(lineno=2, col_offset=10, id='foo', ctx=Load()),
            conversion=-1,
            format_spec=None,
        ),
        Str(lineno=2, col_offset=4, s='bbbccc'),
        FormattedValue(
            lineno=2,
            col_offset=4,
            value=Name(lineno=2, col_offset=5, id='bar', ctx=Load()),
            conversion=-1,
            format_spec=None,
        ),
        Str(lineno=2, col_offset=4, s='dddcccaaaaaaaaaaaaaa'),
        FormattedValue(
            lineno=2,
            col_offset=4,
            value=Name(lineno=2, col_offset=5, id='baz', ctx=Load()),
            conversion=-1,
            format_spec=None,
        ),
        Str(lineno=2, col_offset=4, s='ddd'),
    ],
),

The reported code position for "foo" is correct (2,10), but not for "bar" (2,5) and "baz" (2,5).


Could you give an estimate as to whether this issue will be looked at any time soon?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35212>
_______________________________________

From report at bugs.python.org  Fri Oct  4 04:55:46 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 04 Oct 2019 08:55:46 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570179346.49.0.00476232707067.issue38368@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

I am adding 3.8 regression since the report says 3.8.0b4 works and segfaults with 3.8.0RC1.

----------
keywords: +3.8regression
nosy: +lukasz.langa, xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Fri Oct  4 05:00:35 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Oct 2019 09:00:35 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570179635.54.0.187240981669.issue13153@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

After remembering to recompile (sorry), the test passes and clipgoard_get returns the rocket.  Very nice, thank you.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 05:18:54 2019
From: report at bugs.python.org (Paul Moore)
Date: Fri, 04 Oct 2019 09:18:54 +0000
Subject: [issue38369] Python 3.7.4 venv command does not install pip
Message-ID: <1570180734.57.0.0824297518984.issue38369@roundup.psfhosted.org>


New submission from Paul Moore <p.f.moore at gmail.com>:

The venv module with Python 3.4 on Windows doesn't install pip - even though the --without-pip flag is not specified. This appears to be a regression since pip is installed when using 3.7:

>C:\Utils\PythonVersions\Python-3.7.3\python.exe -m venv ve-373
>dir .\ve-373\Scripts\pip.exe


    Directory: C:\Work\Scratch\vv\ve-373\Scripts


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----       04/10/2019     10:08         102765 pip.exe


>py -m venv ve-374
>dir .\ve-374\Scripts\pip.exe
dir : Cannot find path 'C:\Work\Scratch\vv\ve-374\Scripts\pip.exe' because it does not exist.
At line:1 char:1
+ dir .\ve-374\Scripts\pip.exe
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\Work\Scratch...Scripts\pip.exe:String) [Get-ChildItem], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand
>py -V
Python 3.7.4

----------
assignee: steve.dower
components: Library (Lib)
messages: 353911
nosy: paul.moore, steve.dower
priority: normal
severity: normal
status: open
title: Python 3.7.4 venv command does not install pip
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38369>
_______________________________________

From report at bugs.python.org  Fri Oct  4 05:37:27 2019
From: report at bugs.python.org (Paul Moore)
Date: Fri, 04 Oct 2019 09:37:27 +0000
Subject: [issue38369] Python 3.7.4 venv command does not install pip
In-Reply-To: <1570180734.57.0.0824297518984.issue38369@roundup.psfhosted.org>
Message-ID: <1570181847.97.0.421572324708.issue38369@roundup.psfhosted.org>


Paul Moore <p.f.moore at gmail.com> added the comment:

This appears to be somehow caused by running Python 3.7.4 from an active virtualenv (which I'd forgotten I had active when I did the test).

Regardless, I'd have expected that the command would either correctly create a venv containing pip, or fail to create the venv at all. Creating an incomplete venv is extremely confusing for the user, if nothing else.

It looks like this is *not* a regression - it's been like this since 3.6.8 at least.

Actually, the created venv looks pretty broken to me - it has the *parent* environment in `sys.path`, but does not have its *own* environment there:

>.\ve-368a\Scripts\python.exe
Python 3.6.8 (tags/v3.6.8:3c6b436a57, Dec 24 2018, 00:16:47) [MSC v.1916 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['', 'C:\\Work\\Scratch\\vv\\ve-368a\\Scripts\\python36.zip', 'C:\\Users\\UK03306\\.virtualenvs\\f1980c81dac32d4\\DLLs', 'C:\\Users\\UK03306\\.virtualenvs\\f1980c81dac32d4\\lib', 'C:\\Users\\UK03306\\.virtualenvs\\f1980c81dac32d4\\Scripts', 'C:\\Utils\\PythonVersions\\Python-3.6.8\\Lib', 'C:\\Utils\\PythonVersions\\Python-3.6.8\\DLLs', 'C:\\Users\\UK03306\\.virtualenvs\\f1980c81dac32d4', 'C:\\Users\\UK03306\\.virtualenvs\\f1980c81dac32d4\\lib\\site-packages']

Note the lack of ve-368a directories, and the presence of a lot of directories from .virtualenvs (the parent environment).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38369>
_______________________________________

From report at bugs.python.org  Fri Oct  4 05:48:36 2019
From: report at bugs.python.org (Paul Moore)
Date: Fri, 04 Oct 2019 09:48:36 +0000
Subject: [issue38369] Python 3.7.4 venv command does not install pip
In-Reply-To: <1570180734.57.0.0824297518984.issue38369@roundup.psfhosted.org>
Message-ID: <1570182516.86.0.98494159581.issue38369@roundup.psfhosted.org>


Paul Moore <p.f.moore at gmail.com> added the comment:

Further update - this appears to also happen on Ubuntu (at least the version available through the Windows Linux subsystem), so it's not a Windows-specific issue.

----------
assignee: steve.dower -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38369>
_______________________________________

From report at bugs.python.org  Fri Oct  4 05:50:51 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Fri, 04 Oct 2019 09:50:51 +0000
Subject: [issue37025] Misleading error message "Python failed to load the
 default activation context"
In-Reply-To: <1558646019.4.0.18611977167.issue37025@roundup.psfhosted.org>
Message-ID: <1570182651.52.0.791822940635.issue37025@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
keywords: +patch
pull_requests: +16170
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16579

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37025>
_______________________________________

From report at bugs.python.org  Fri Oct  4 05:53:36 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Fri, 04 Oct 2019 09:53:36 +0000
Subject: [issue37025] Misleading error message "Python failed to load the
 default activation context"
In-Reply-To: <1558646019.4.0.18611977167.issue37025@roundup.psfhosted.org>
Message-ID: <1570182816.59.0.912302008444.issue37025@roundup.psfhosted.org>


Zackery Spytz <zspytz at gmail.com> added the comment:

Thank you for the report. I've created a pull request to fix this issue.

----------
nosy: +ZackerySpytz
versions: +Python 2.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37025>
_______________________________________

From report at bugs.python.org  Fri Oct  4 06:02:24 2019
From: report at bugs.python.org (Paul Moore)
Date: Fri, 04 Oct 2019 10:02:24 +0000
Subject: [issue38369] Python 3.7.4 venv command does not install pip
In-Reply-To: <1570180734.57.0.0824297518984.issue38369@roundup.psfhosted.org>
Message-ID: <1570183344.99.0.612739970388.issue38369@roundup.psfhosted.org>


Paul Moore <p.f.moore at gmail.com> added the comment:

Sigh. Never mind, this appears to be because virtualenv uses its own hacked copy of site.py which is missing a lot of the venv support code.

I'll report this over on virtualenv.

----------
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38369>
_______________________________________

From report at bugs.python.org  Fri Oct  4 06:09:55 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 10:09:55 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570183795.12.0.262973008261.issue13153@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 06cb94bc8419b9a24df6b0d724fcd8e40c6971d6 by Serhiy Storchaka in branch 'master':
bpo-13153: Use OS native encoding for converting between Python and Tcl. (GH-16545)
https://github.com/python/cpython/commit/06cb94bc8419b9a24df6b0d724fcd8e40c6971d6


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 06:10:07 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Oct 2019 10:10:07 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570183807.25.0.418966458365.issue13153@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16171
pull_request: https://github.com/python/cpython/pull/16580

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 06:10:14 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Oct 2019 10:10:14 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570183814.76.0.437396486861.issue13153@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16172
pull_request: https://github.com/python/cpython/pull/16581

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 06:24:29 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 04 Oct 2019 10:24:29 +0000
Subject: [issue38352] In typing docs,
 note explicit import needed for IO and Pattern/Match
In-Reply-To: <1570041077.58.0.399304866649.issue38352@roundup.psfhosted.org>
Message-ID: <1570184669.1.0.663951521838.issue38352@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

> So, my request is: In the sections for the IO/TextIO/BinaryIO and Pattern/Match classes, include text warning the user that these types are not imported when you do `from typing import *`.

I don't think this should really be a warning, probably just a note, but otherwise I totally agree. Would you like to make a PR?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38352>
_______________________________________

From report at bugs.python.org  Fri Oct  4 06:28:56 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Oct 2019 10:28:56 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570184936.89.0.877572405889.issue13153@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 6c3fbbc177f5e1867ab09a315dbf58554a80accd by Miss Islington (bot) in branch '3.7':
bpo-13153: Use OS native encoding for converting between Python and Tcl. (GH-16545)
https://github.com/python/cpython/commit/6c3fbbc177f5e1867ab09a315dbf58554a80accd


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 06:28:59 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Oct 2019 10:28:59 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570184939.51.0.904795581251.issue13153@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset dc191245d8f63f5ab41afff0468b7463a07e7b00 by Miss Islington (bot) in branch '3.8':
bpo-13153: Use OS native encoding for converting between Python and Tcl. (GH-16545)
https://github.com/python/cpython/commit/dc191245d8f63f5ab41afff0468b7463a07e7b00


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:24:32 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 04 Oct 2019 11:24:32 +0000
Subject: [issue38366] dataclasses: generate the _hash_action table from the
 if-else tree
In-Reply-To: <1570143889.18.0.0994959118678.issue38366@roundup.psfhosted.org>
Message-ID: <1570188272.13.0.192125557261.issue38366@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Thank you for your contribution, @iomintz, but I'm not going to accept this change. I don't think it improves the clarity of the code. And I realize this is wholly a subjective decision, and others may disagree. But to me, looking at the table it's clear that each case is handled correctly, while looking through the code I'd need to reason about it for each case.

----------
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38366>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:27:18 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 11:27:18 +0000
Subject: [issue36632] test_multiprocessing_forkserver: test_rapid_restart()
 leaked a dangling process on AMD64 FreeBSD 10-STABLE Non-Debug 3.x
In-Reply-To: <1555326100.12.0.0433329524894.issue36632@roundup.psfhosted.org>
Message-ID: <1570188438.99.0.0395702582792.issue36632@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Warning on AMD64 Debian root 3.x:
https://buildbot.python.org/all/#/builders/27/builds/3853

test_enable_logging (test.test_multiprocessing_spawn.WithProcessesTestLogging) ... ok
test_level (test.test_multiprocessing_spawn.WithProcessesTestLogging) ... ok
test_rapid_restart (test.test_multiprocessing_spawn.WithProcessesTestManagerRestart) ... ok
Warning -- Dangling processes: {<SpawnProcess name='QueueManager-212' pid=2551 parent=31308 stopped exitcode=-SIGTERM>}
test_access (test.test_multiprocessing_spawn.WithProcessesTestPicklingConnections) ... ok

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36632>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:35:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 11:35:53 +0000
Subject: [issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent()
 Internal
In-Reply-To: <1569352841.72.0.766028949986.issue38266@roundup.psfhosted.org>
Message-ID: <1570188953.57.0.194953970317.issue38266@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 8855e47d09d4db1206c65b24efc8ad0df585ac46 by Victor Stinner (Joannah Nanjekye) in branch 'master':
bpo-38266: Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal (GH-16558)
https://github.com/python/cpython/commit/8855e47d09d4db1206c65b24efc8ad0df585ac46


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38266>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:35:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 11:35:53 +0000
Subject: [issue37878] Sub-Interpreters : Document PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1570188953.71.0.0348530717838.issue37878@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 8855e47d09d4db1206c65b24efc8ad0df585ac46 by Victor Stinner (Joannah Nanjekye) in branch 'master':
bpo-38266: Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal (GH-16558)
https://github.com/python/cpython/commit/8855e47d09d4db1206c65b24efc8ad0df585ac46


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37878>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:40:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 11:40:02 +0000
Subject: [issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent()
 Internal
In-Reply-To: <1569352841.72.0.766028949986.issue38266@roundup.psfhosted.org>
Message-ID: <1570189202.58.0.868453646459.issue38266@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Since this sounds like a regression being introduced by 3.8.0, should the reversion be included in 3.8.0 final or can it wait for 3.8.1?

Oh, in fact, the change was only made in the master branch: after the 3.8 branch was created. The 3.8 branch still contains PyThreadState_DeleteCurrent() ;-) There is no regression in 3.8, only in master, and the regression in master has been fixed.

----------
priority: release blocker -> 
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38266>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:44:01 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 11:44:01 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570189441.52.0.0990611998718.issue13153@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:45:51 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 11:45:51 +0000
Subject: [issue37878] Sub-Interpreters : Document PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1570189551.04.0.546330647651.issue37878@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> bpo-38266: Revert bpo-37878: Make PyThreadState_DeleteCurrent() Internal (GH-16558)

Oh, I didn't notice something in the review: the revert moved PyThreadState_DeleteCurrent() definition from Include/pystate.h to Include/cpython/pystate.h. Previously, it was defined in Include/pystate.h, see the commit removing it:
https://github.com/python/cpython/commit/2bc43cdc015eda4f1a651bb2b308a17a83c38e14

Joannah: can you please move the definition back to Include/pystate.h, at the same place it was before the removal, please?

The revert excluded PyThreadState_DeleteCurrent() from the stable API (Py_LIMITED_API).

----------
versions:  -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37878>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:46:09 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 11:46:09 +0000
Subject: [issue22742] IDLE shows traceback when printing non-BMP character
In-Reply-To: <1414426704.85.0.168243800807.issue22742@psf.upfronthosting.co.za>
Message-ID: <1570189569.66.0.260272789275.issue22742@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Fixed by PR 16545 (see issue13153).

----------
nosy: +serhiy.storchaka
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22742>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:46:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 11:46:39 +0000
Subject: [issue37878] Sub-Interpreters : Document PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1570189599.28.0.603130324837.issue37878@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

To be clear: this issue only impacts Python 3.8. The function was only removed from the master branch. It was still in the 3.8 branch.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37878>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:47:21 2019
From: report at bugs.python.org (plugin nieulq)
Date: Fri, 04 Oct 2019 11:47:21 +0000
Subject: [issue38370] An array as attribute of an object is shared between
 instances
Message-ID: <1570189641.68.0.415571181009.issue38370@roundup.psfhosted.org>


New submission from plugin nieulq <plu9in at gmail.com>:

I am using this version on Windows :
Python 3.7.4 (tags/v3.7.4:e09359112e, Jul  8 2019, 20:34:20) [MSC v.1916 64 bit (AMD64)].
When an attribute of an object is an array, the array is shared between instances as shown in my example.
When executed, the output generated by the script is:
Value1
Value2
Value3
Value4
--------------------------------
Value1
Value2
Value3
Value4

It should be :

Value1
Value2
--------------------------------
Value3
Value4

----------
components: Windows
messages: 353928
nosy: paul.moore, plugin nieulq, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: An array as attribute of an object is shared between instances
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38370>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:50:09 2019
From: report at bugs.python.org (plugin nieulq)
Date: Fri, 04 Oct 2019 11:50:09 +0000
Subject: [issue38370] An array as attribute of an object is shared between
 instances
In-Reply-To: <1570189641.68.0.415571181009.issue38370@roundup.psfhosted.org>
Message-ID: <1570189809.01.0.687444337933.issue38370@roundup.psfhosted.org>


plugin nieulq <plu9in at gmail.com> added the comment:

I am using this version on Windows :
Python 3.7.4 (tags/v3.7.4:e09359112e, Jul  8 2019, 20:34:20) [MSC v.1916 64 bit (AMD64)].
When an attribute of an object is an array, the array is shared between instances as shown in my example.

class AClass(object):
    def __init__(self, val=[]):
        self.contents = val

    def add_content(self, newcontent):
        self.contents.append(newcontent)
        return self

    def print(self):
        for val in self.contents:
            print(str(val))


if __name__ == '__main__':
    sc = AClass()
    sc = sc.add_content("Value1").add_content("Value2")

    sb = AClass()
    sb = sb.add_content("Value3").add_content("Value4")

    sc.print()
    print("--------------------------------")
    sb.print()


When executed, the output generated by the script is:
Value1
Value2
Value3
Value4
--------------------------------
Value1
Value2
Value3
Value4

It should be :

Value1
Value2
--------------------------------
Value3
Value4

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38370>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:56:58 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Fri, 04 Oct 2019 11:56:58 +0000
Subject: [issue38370] An array as attribute of an object is shared between
 instances
In-Reply-To: <1570189641.68.0.415571181009.issue38370@roundup.psfhosted.org>
Message-ID: <1570190218.42.0.715938873473.issue38370@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

This is a common gotcha. Take a look at: https://docs.python.org/3/faq/programming.html#why-are-default-values-shared-between-objects

----------
nosy: +mark.dickinson
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38370>
_______________________________________

From report at bugs.python.org  Fri Oct  4 07:59:57 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 11:59:57 +0000
Subject: [issue22742] IDLE shows traceback when printing non-BMP character
In-Reply-To: <1414426704.85.0.168243800807.issue22742@psf.upfronthosting.co.za>
Message-ID: <1570190397.59.0.363957471919.issue22742@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

It was fixed for all valid Unicode characters, you can still get an error when print a surrogate character to the stderr on Linux:

>>> import sys
>>> print('\ud800', file=sys.stderr)
Traceback (most recent call last):
  File "<pyshell#4>", line 1, in <module>
    print('\ud800', file=sys.stderr)
UnicodeEncodeError: 'utf-8' codec can't encode character '\ud800' in position 0: surrogates not allowed

In the Python REPL you get an escaped sequence.

>>> import sys
>>> print('\ud800', file=sys.stderr)
\ud800

----------
resolution: fixed -> 
stage: resolved -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22742>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:00:21 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 12:00:21 +0000
Subject: [issue36698] Shell restart when error message contains non-BMP
 characters
In-Reply-To: <1555953357.75.0.808052597637.issue36698@roundup.psfhosted.org>
Message-ID: <1570190420.99.0.258940205621.issue36698@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Mostly fixed by PR 16545 (see issue13153). The original example is now passed.

>>> raise Exception('\U0001f603')
Traceback (most recent call last):
  File "<pyshell#1>", line 1, in <module>
    raise Exception('\U0001f603')
Exception: ?
>>> 

But you can still cause a restart of the shell by using surrogate characters:

>>> raise Exception('\ud800')
Traceback (most recent call last):
  File "<pyshell#0>", line 1, in <module>
    raise Exception('\ud800')
Traceback (most recent call last):
  File "<pyshell#0>", line 1, in <module>
    raise Exception('\ud800')

================================ RESTART: Shell ================================
>>>

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36698>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:03:40 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 12:03:40 +0000
Subject: [issue21084] IDLE can't deal with characters above the range
 (U+0000-U+FFFF)
In-Reply-To: <1396008065.84.0.00802001667749.issue21084@psf.upfronthosting.co.za>
Message-ID: <1570190620.49.0.215064150717.issue21084@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Fixed by PR 16545 (see issue13153).

----------
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21084>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:07:50 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 12:07:50 +0000
Subject: [issue30019] IDLE freezes when opening a file with astral characters
In-Reply-To: <1491596146.33.0.970912299828.issue30019@psf.upfronthosting.co.za>
Message-ID: <1570190870.65.0.0291057980917.issue30019@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

This looks like a duplicate of issue21084. Fixed by PR 16545 (see issue13153). It is virtually Eryk's workaround, but at the Tkinter level.

----------
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30019>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:08:41 2019
From: report at bugs.python.org (plugin nieulq)
Date: Fri, 04 Oct 2019 12:08:41 +0000
Subject: [issue38370] An array as attribute of an object is shared between
 instances
In-Reply-To: <1570189641.68.0.415571181009.issue38370@roundup.psfhosted.org>
Message-ID: <1570190921.24.0.652525795485.issue38370@roundup.psfhosted.org>


plugin nieulq <plu9in at gmail.com> added the comment:

Ah ... Ok. My bad.
Thank you for pointing this out to me, Mark.
This is definitely a strange behavior.

----------
nosy:  -mark.dickinson
resolution: not a bug -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38370>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:13:03 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 04 Oct 2019 12:13:03 +0000
Subject: [issue37878] Sub-Interpreters : Document PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1570191183.22.0.375626418982.issue37878@roundup.psfhosted.org>


Joannah Nanjekye <nanjekyejoannah at gmail.com> added the comment:

> Oh, I didn't notice something in the review: the revert moved >PyThreadState_DeleteCurrent() definition from Include/pystate.h to >Include/cpython/pystate.h. Previously, it was defined in > Include/pystate.h, see the commit removing it:

I made this change as it was requested by Eric snow in issue38266.

"when we un-revert we should be sure to move PyThreadState_DeleteCurrent() from Include/pystate.h to Include/cpython/pystate.h."

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37878>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:26:06 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 12:26:06 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570191966.66.0.463726577597.issue13153@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> bpo-13153: Use OS native encoding for converting between Python and Tcl. (GH-16545)

WOW. That's huge. The issue with non-BMP characters has been fixed? Finally? The issue was haunting the bug tracker for at least 8 years!!!

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:30:38 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 12:30:38 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570192238.08.0.260670829054.issue38353@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16173
pull_request: https://github.com/python/cpython/pull/16582

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:34:51 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 04 Oct 2019 12:34:51 +0000
Subject: [issue38227] Setting a signal handler gets multiprocessing.Pool stuck
In-Reply-To: <1568929295.79.0.555392640133.issue38227@roundup.psfhosted.org>
Message-ID: <1570192491.68.0.998101165482.issue38227@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:

Several things here:

- you can perform critical cleanup with the atexit module; using a signal handler for that is extremely low-level and error-prone

- you can also try to switch to the "forkserver" method of multiprocessing, perhaps that will fix your issue

----------
nosy: +pitrou

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38227>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:43:51 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 04 Oct 2019 12:43:51 +0000
Subject: [issue38284] signal.sigwait* do not intercept certain signals
In-Reply-To: <1569496743.5.0.75731685223.issue38284@roundup.psfhosted.org>
Message-ID: <1570193031.64.0.105866218895.issue38284@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:

Python just exposes thin wrappers around the underlying libc calls, so you have to understand how those work.

On Linux, the sigwaitinfo() man page says:

NOTES
       In normal usage, the calling program blocks the signals  in
       set via a prior call to sigprocmask(2) (so that the default
       disposition for these signals does not occur if they become
       pending  between  successive calls to sigwaitinfo() or sig?
       timedwait()) and does not establish handlers for these sig?
       nals.

So you need to block the given signal with pthread_sigmask() before waiting on it.  For example:

>>> import signal
>>> signal.pthread_sigmask(signal.SIG_BLOCK, [signal.SIGHUP])
set()
>>> signal.sigwait([signal.SIGHUP])
<Signals.SIGHUP: 1>

----------
nosy: +pitrou

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38284>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:44:55 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 04 Oct 2019 12:44:55 +0000
Subject: [issue38284] signal.sigwait* do not intercept certain signals
In-Reply-To: <1569496743.5.0.75731685223.issue38284@roundup.psfhosted.org>
Message-ID: <1570193095.04.0.626268709775.issue38284@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:

Closing as not a Python bug.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38284>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:48:23 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 04 Oct 2019 12:48:23 +0000
Subject: [issue38249] Optimize out Py_UNREACHABLE in the release mode
In-Reply-To: <1569145626.92.0.408422678201.issue38249@roundup.psfhosted.org>
Message-ID: <1570193303.27.0.656208925366.issue38249@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:

I agree with Serhiy.  If you hit a rare situation that you don't want to handle, use Py_FatalError(), not Py_UNREACHABLE().

Py_UNREACHABLE() is for situations which are *logically* impossible, not just uncommon.

----------
nosy: +pitrou

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38249>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:53:06 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 04 Oct 2019 12:53:06 +0000
Subject: [issue38167] O_DIRECT read fails with 4K mmap buffer
In-Reply-To: <1568417320.49.0.42295605579.issue38167@roundup.psfhosted.org>
Message-ID: <1570193586.01.0.882535143135.issue38167@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:

I agree with Josh. If you want to use O_DIRECT, use an unbuffered file object and be sure to issue reads of the right size.

----------
nosy: +pitrou

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38167>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:55:41 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 04 Oct 2019 12:55:41 +0000
Subject: [issue38167] O_DIRECT read fails with 4K mmap buffer
In-Reply-To: <1568417320.49.0.42295605579.issue38167@roundup.psfhosted.org>
Message-ID: <1570193741.7.0.0828144215231.issue38167@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:

Also I'm curious: why are you using O_DIRECT, and furthermore, why are you using it to read into mmap'ed memory?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38167>
_______________________________________

From report at bugs.python.org  Fri Oct  4 08:56:47 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 04 Oct 2019 12:56:47 +0000
Subject: [issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent()
 Internal
In-Reply-To: <1569352841.72.0.766028949986.issue38266@roundup.psfhosted.org>
Message-ID: <1570193807.02.0.141855637474.issue38266@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
keywords:  -3.8regression
versions:  -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38266>
_______________________________________

From report at bugs.python.org  Fri Oct  4 09:00:08 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Fri, 04 Oct 2019 13:00:08 +0000
Subject: [issue38346] Wrong behavior when using `assert_called_with` with
 mutable object
In-Reply-To: <1570006369.69.0.450054962888.issue38346@roundup.psfhosted.org>
Message-ID: <1570194008.92.0.0481192798278.issue38346@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

> when `b` has same values of `a` before it is mutated.

There might be no such object. Or it might exist, but you still wouldn't want it.

Consider the case when a is a coroutine that has just started (a=coro()). You call f with a, and then advance a to the next yielding point. Is f called with a? You say no. Ok. But imagine you call coro again, and call that b (b=coro()). Is f called with b? Do you really want to say yes to that?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38346>
_______________________________________

From report at bugs.python.org  Fri Oct  4 09:22:43 2019
From: report at bugs.python.org (Tal Einat)
Date: Fri, 04 Oct 2019 13:22:43 +0000
Subject: [issue13153] IDLE 3.x on Windows exits when pasting non-BMP unicode
In-Reply-To: <1318363292.9.0.682519731008.issue13153@psf.upfronthosting.co.za>
Message-ID: <1570195363.15.0.830681132573.issue13153@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

Indeed, Serhiy, you've done an amazing job with this change and it will greatly benefit many people.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13153>
_______________________________________

From report at bugs.python.org  Fri Oct  4 09:26:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 13:26:02 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570195562.77.0.294362630148.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset abd7cd856ba326bd7574135c7d034e98492ab695 by Victor Stinner in branch 'master':
bpo-38353: getpath.c uses dynamically allocated strings (GH-16582)
https://github.com/python/cpython/commit/abd7cd856ba326bd7574135c7d034e98492ab695


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Fri Oct  4 10:53:50 2019
From: report at bugs.python.org (=?utf-8?q?Ionel_Cristian_M=C4=83rie=C8=99?=)
Date: Fri, 04 Oct 2019 14:53:50 +0000
Subject: [issue38227] Setting a signal handler gets multiprocessing.Pool stuck
In-Reply-To: <1568929295.79.0.555392640133.issue38227@roundup.psfhosted.org>
Message-ID: <1570200830.33.0.657316228323.issue38227@roundup.psfhosted.org>


Ionel Cristian M?rie? <contact at ionelmc.ro> added the comment:

atexit proved time and time again to be unreliable, not really an option. Not all programs shutdown nicely enough for atexit. 

Should I tell users "use forkserver on 3.8 because broken stuff"?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38227>
_______________________________________

From report at bugs.python.org  Fri Oct  4 11:09:07 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 15:09:07 +0000
Subject: [issue36698] Shell restart when error message contains non-BMP
 characters
In-Reply-To: <1555953357.75.0.808052597637.issue36698@roundup.psfhosted.org>
Message-ID: <1570201746.99.0.624904196614.issue36698@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16174
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16583

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36698>
_______________________________________

From report at bugs.python.org  Fri Oct  4 11:33:41 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 15:33:41 +0000
Subject: [issue38371] Tkinter: deprecate the split() method
Message-ID: <1570203221.73.0.664458057352.issue38371@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

The tkapp.split() method has weird behavior. It splits a string recursively, so the type of items and the depth of nesting depends on spaces in string values. For example:

>>> import tkinter
>>> root = tkinter.Tcl()
>>> root.tk.split('Hi')
'Hi'
>>> root.tk.split('Hello "Good bye"')
('Hello', ('Good', 'bye'))

It may work as you meant in some cases (if items at the same level either all have spaces or all do not have spaces), but return unexpected  result for untested cases. It is more robust to use the tkapp.splitlist() method, which split exactly one level and always returns a tuple of strings. It can be used recursively if you need nested lists.

>>> root.tk.splitlist('Hi')
('Hi',)
>>> root.tk.splitlist('Hello "Good bye"')
('Hello', 'Good bye')
>>> [root.tk.splitlist(x) for x in root.tk.splitlist('Hello "Good bye"')]
[('Hello',), ('Good', 'bye')]

----------
components: Tkinter
messages: 353948
nosy: serhiy.storchaka
priority: normal
severity: normal
status: open
title: Tkinter: deprecate the split() method
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38371>
_______________________________________

From report at bugs.python.org  Fri Oct  4 11:45:22 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 15:45:22 +0000
Subject: [issue38371] Tkinter: deprecate the split() method
In-Reply-To: <1570203221.73.0.664458057352.issue38371@roundup.psfhosted.org>
Message-ID: <1570203922.22.0.9350011877.issue38371@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16175
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16584

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38371>
_______________________________________

From report at bugs.python.org  Fri Oct  4 12:01:16 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 16:01:16 +0000
Subject: [issue37878] Sub-Interpreters : Document PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1570204876.83.0.932706029342.issue37878@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> "when we un-revert we should be sure to move PyThreadState_DeleteCurrent() from Include/pystate.h to Include/cpython/pystate.h."

Ah, I didn't see this comment. If Eric endorses this change, I'm fine with it :-)

I close the issue.

If someone wants to modify PyThreadState_DeleteCurrent() to automatically call PyThreadState_Clear(), please open a new issue for that.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37878>
_______________________________________

From report at bugs.python.org  Fri Oct  4 12:01:29 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 16:01:29 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570204889.01.0.710380251659.issue38353@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16176
pull_request: https://github.com/python/cpython/pull/16585

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Fri Oct  4 12:02:21 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 16:02:21 +0000
Subject: [issue38249] Optimize out Py_UNREACHABLE in the release mode
In-Reply-To: <1569145626.92.0.408422678201.issue38249@roundup.psfhosted.org>
Message-ID: <1570204941.9.0.497106055483.issue38249@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Py_UNREACHABLE() is for situations which are *logically* impossible, not just uncommon.

I suggest to clarify/enhance Py_UNREACHABLE() documentation to make it more explicit in that case.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38249>
_______________________________________

From report at bugs.python.org  Fri Oct  4 12:04:57 2019
From: report at bugs.python.org (AWhetter)
Date: Fri, 04 Oct 2019 16:04:57 +0000
Subject: [issue38235] Docs of logging module says argument is named "lvl".
 TypeError.
In-Reply-To: <1568996817.83.0.32795106699.issue38235@roundup.psfhosted.org>
Message-ID: <1570205097.96.0.718508583621.issue38235@roundup.psfhosted.org>


Change by AWhetter <ashley at awhetter.co.uk>:


----------
pull_requests: +16177
pull_request: https://github.com/python/cpython/pull/16586

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38235>
_______________________________________

From report at bugs.python.org  Fri Oct  4 12:25:47 2019
From: report at bugs.python.org (Paul)
Date: Fri, 04 Oct 2019 16:25:47 +0000
Subject: [issue38167] O_DIRECT read fails with 4K mmap buffer
In-Reply-To: <1568417320.49.0.42295605579.issue38167@roundup.psfhosted.org>
Message-ID: <1570206347.21.0.566924645914.issue38167@roundup.psfhosted.org>


Paul <paul.carlisle at gmail.com> added the comment:

> I agree with Josh. If you want to use O_DIRECT, use an unbuffered file object and be sure to issue reads of the right size.

I do not believe an unbuffered file uses O_DIRECT.  This is why I use os.open(fpath, os.O_DIRECT).

> Also I'm curious: why are you using O_DIRECT, and furthermore, why are you using it to read into mmap'ed memory?

I am testing a storage device and must use O_DIRECT to avoid the kernel's cache.  I am using mmap because it was the simplest way to get a page-aligned memory buffer, which is required for direct IO.

I believe that this is a bug regardless of the use of mmap, especially considering that this worked in Python 2.  I believe the fix I have sent out for review addresses it adequately.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38167>
_______________________________________

From report at bugs.python.org  Fri Oct  4 12:27:17 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 04 Oct 2019 16:27:17 +0000
Subject: [issue37025] Misleading error message "Python failed to load the
 default activation context"
In-Reply-To: <1558646019.4.0.18611977167.issue37025@roundup.psfhosted.org>
Message-ID: <1570206437.35.0.707325664908.issue37025@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

This doesn't apply since Python 3.5, as the HAVE_SXS preprocessor variable is not defined.

We should just delete this code entirely in 3.9, and patch the message in 2.7.

----------
versions:  -Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37025>
_______________________________________

From report at bugs.python.org  Fri Oct  4 12:39:41 2019
From: report at bugs.python.org (Barry A. Warsaw)
Date: Fri, 04 Oct 2019 16:39:41 +0000
Subject: [issue38249] Optimize out Py_UNREACHABLE in the release mode
In-Reply-To: <1569145626.92.0.408422678201.issue38249@roundup.psfhosted.org>
Message-ID: <1570207181.12.0.67924654032.issue38249@roundup.psfhosted.org>


Barry A. Warsaw <barry at python.org> added the comment:

+1 Serhiy.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38249>
_______________________________________

From report at bugs.python.org  Fri Oct  4 12:54:45 2019
From: report at bugs.python.org (=?utf-8?b?0JHQtdCw0YLRgNC40YEg0JHQvtC90LXQstCw?=)
Date: Fri, 04 Oct 2019 16:54:45 +0000
Subject: [issue38372] Undefined behavior when changing dict while iterating it
Message-ID: <1570208085.28.0.0436589933875.issue38372@roundup.psfhosted.org>


New submission from ??????? ?????? <beatrisvboneva at gmail.com>:

When changing a dict while iterating through it by removing one key and inserting other which is calculated based on the old one, the dict is changed unexpectedly.

The following function:

```
def test(d: dict): 
     for i in d: 
         d[i+1] = d.pop(i)
```

when called with input dict `{1: 'test'}` transforms the dict to:
- `{6: 'test'}` in Python3.7.4;
- `{8: 'test'}` in Python3.5.3 and Python2.7.

If I change the function to add 2 to the key ( `d[i+2] = d.pop(i)` ) and use the same input `{1: 'test'}` the dict is changed to:
- `{11: 'test'}` in Python3.7;
- `{9: 'test'}` in Python3.5.

Similar thing happens with strings:

```
def test(d: dict): 
     for i in d: 
         d[i+'x'] = d.pop(i)
```

When called with input dict `{'a': 'test'}` it transforms it to:
- `{'axxxxx': 'test'}` in Python3.7.4;
- `{'axx': 'test'}` in Python3.5.3.

----------
components: Library (Lib)
messages: 353954
nosy: ??????? ??????
priority: normal
severity: normal
status: open
title: Undefined behavior when changing dict while iterating it
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38372>
_______________________________________

From report at bugs.python.org  Fri Oct  4 12:54:52 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 04 Oct 2019 16:54:52 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570208092.39.0.209811460415.issue38368@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Also crashes on Windows (x64 and x86), and on 3.7.5rc1, so this is likely in our code.

----------
nosy: +ned.deily, steve.dower
priority: normal -> release blocker
stage:  -> test needed
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Fri Oct  4 12:57:51 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 04 Oct 2019 16:57:51 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570208271.01.0.985395555845.issue38368@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

I get this assertion in a debug build:

Assertion failed: actual_type_index <= MAX_ELEMENTS, file c:\projects\cpython\modules\_ctypes\stgdict.c, line 718

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Fri Oct  4 13:05:50 2019
From: report at bugs.python.org (AWhetter)
Date: Fri, 04 Oct 2019 17:05:50 +0000
Subject: [issue16974] when "python -c command" does a traceback,
 it open the file "<string>"
In-Reply-To: <1358286006.48.0.232332339533.issue16974@psf.upfronthosting.co.za>
Message-ID: <1570208750.07.0.585902826142.issue16974@roundup.psfhosted.org>


AWhetter <ashley at awhetter.co.uk> added the comment:

If we were to add a new attribute to indicate whether a file is real or not, there would need to be a way for users to indicate whether a file is real or not to functions such as `compile()` (there's lots more!) that take a filename. Without enforcing this being set and introducing backward incompatible changes, it would need a default value. To be backwards compatible we could default to True and the existing behaviour persists.

It's also worth mentioning that there's a few places (there might be more!) where Python already assumes that a file in angle brackets is not a real file:
* https://github.com/python/cpython/blob/abd7cd856ba326bd7574135c7d034e98492ab695/Lib/bdb.py#L45
* https://github.com/python/cpython/blob/abd7cd856ba326bd7574135c7d034e98492ab695/Lib/pdb.py#L694
* https://github.com/python/cpython/blob/abd7cd856ba326bd7574135c7d034e98492ab695/Lib/pickle.py#L324

Nothing major though and easily changeable so it's definitely possible but it would be a lot of work to make sure that everything is setting the new attribute properly.

Is there a preference on what the name of this attribute should be? Maybe `__is_real_file__`. It's clear but long.

----------
nosy: +AWhetter

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16974>
_______________________________________

From report at bugs.python.org  Fri Oct  4 13:07:01 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 04 Oct 2019 17:07:01 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570208821.43.0.726010768079.issue38368@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Increasing MAX_ELEMENTS fixes it, but I'm not sure what other impacts there are from doing that.

+Vinay who added the array handling that's hitting the limit.

----------
nosy: +vinay.sajip
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Fri Oct  4 13:08:46 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 04 Oct 2019 17:08:46 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570208926.22.0.745708691166.issue38368@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Given this limit can easily be hit by user code, I'd like to see it turned into a proper check with an exception (or a dynamic array) rather than just an assertion. We should not segfault here.

while (length > 0) {
    actual_types[actual_type_index++] = &edict->ffi_type_pointer;
    assert(actual_type_index <= MAX_ELEMENTS);
    length--;
}

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Fri Oct  4 13:10:57 2019
From: report at bugs.python.org (Beatris Boneva)
Date: Fri, 04 Oct 2019 17:10:57 +0000
Subject: [issue38372] Undefined behavior when changing dict while iterating it
In-Reply-To: <1570208085.28.0.0436589933875.issue38372@roundup.psfhosted.org>
Message-ID: <1570209057.41.0.932775372547.issue38372@roundup.psfhosted.org>


Beatris Boneva <beatrisvboneva at gmail.com> added the comment:

Now I see it is duplicate of https://bugs.python.org/issue19332. Closing it.

----------
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38372>
_______________________________________

From report at bugs.python.org  Fri Oct  4 13:51:10 2019
From: report at bugs.python.org (Tim Peters)
Date: Fri, 04 Oct 2019 17:51:10 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1570211470.07.0.0299885544467.issue38006@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

BTW, the phrase "missing tp_traverse" is misleading.  If an object with a NULL tp_traverse appears in a gc generation, gc will blow up the next time that generation is collected.  That's always been so - gc doesn't check whether tp_traverse is NULL, it just calls it.  It's tp_clear that it checks, because that one is optional.

I don't recall any problem we've had with extensions implementing the gc protocol incorrectly or incompletely.  It's this issue's problem:  containers not participating in gc _at all_.

If we had a traditional mark-sweep collector, that would be massively catastrophic.  Miss a pointer and you can conclude a live object is actually trash, and tear it down while it's still in use.

Our problem is the opposite:  miss a pointer and we can conclude a trash object is actually live.  At the start, the worst that _could_ do is leak memory.  It's the later introduction of time-to-die finalizers (weakref callbacks at first) that created the opportunity for segfaults:  the only 100% clearly safe way to run finalizers in cyclic trash is to force them to run _before_ anything at all is torn down by force (tp_clear).  But to run them in advance, we have to know the relevant objects _are_ trash.  Which we can't always know if containers don't always participate.

While Neil & I haven't thought of ways that can go wrong now beyond that a "surprise finalizer" may get run any number of times, that doesn't mean far worse things can't happen - just that they'll surprise us when they do :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Fri Oct  4 13:54:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Oct 2019 17:54:00 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570211640.93.0.0564142050289.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset c02b41b1fb115c87693530ea6a480b2e15460424 by Victor Stinner in branch 'master':
bpo-38353: getpath.c: allocates strings on the heap (GH-16585)
https://github.com/python/cpython/commit/c02b41b1fb115c87693530ea6a480b2e15460424


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Fri Oct  4 13:55:38 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Oct 2019 17:55:38 +0000
Subject: [issue22742] IDLE shows traceback when printing non-BMP character
In-Reply-To: <1414426704.85.0.168243800807.issue22742@psf.upfronthosting.co.za>
Message-ID: <1570211738.79.0.664655820922.issue22742@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Printing the unquoted escape representation rather than a replacement char is a bit strange and not what I expect from the python docs.  I could see it as a bug.  In any case, on Windows, it is the Python REPL that raises, but only for sys.stdout.

>>> import sys
>>> print('\ud800', file=sys.stderr)
\ud800
>>> print('\ud800', file=sys.stdout)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeEncodeError: 'utf-8' codec can't encode character '\ud800' in position 0: surrogates not allowed

whereas on Windows the surrogate is displayed as a box with diagonal lines ([X] compressed in one char) in both cases.  When copied and pasted into FireFox, the pasted surrogate shows as a square box containing mini D 8 0 0 chars.
>>> print('\ud800', file=sys.stdout)
?
>>> print('\ud800', file=sys.stderr)
?

I consider putting the undisplayable codepoint, rather than a replacement character, into the editor buffer (however tcl encodes it) so that IDLE can retrieve it without loss of information the proper thing for tk to do. IDLE can then potentially identify the character to the user.
===

An oddity though.  With

>>> import tkinter as tk
>>> r = tk.Tk()
>>> t = tk.Text(r)
>>> t.pack()
>>> t.insert('insert', 'a\ud800b')

the box is an empty square, not crossed.  But when I copy-paste 'a?b' into the font sample (Serhiy, making this editable was a great idea), it is crossed for every font I tried, even for Courier, which is what is being used in text t.

----------
stage:  -> needs patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22742>
_______________________________________

From report at bugs.python.org  Fri Oct  4 13:56:00 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 17:56:00 +0000
Subject: [issue38328] Speed up the creation time of constant list literals.
In-Reply-To: <1569862645.36.0.924344090693.issue38328@roundup.psfhosted.org>
Message-ID: <1570211760.62.0.315810100386.issue38328@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Great! I withdrew the original proposition in issue33325 because the part of the optimization was not so good as I expected. But this part is good.

$ ./python -m timeit "[$(seq -s, 10)]"
5000000 loops, best of 5: 75.5 nsec per loop
$ ./python -m timeit "[*($(seq -s, 10))]"
5000000 loops, best of 5: 57.2 nsec per loop

Would you consider to optimize also creating a set of constants?

$ ./python -m timeit "{$(seq -s, 10)}"
2000000 loops, best of 5: 186 nsec per loop
$ ./python -m timeit -s "a = frozenset(($(seq -s, 10)))"  "{*a}"
2000000 loops, best of 5: 116 nsec per loop

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38328>
_______________________________________

From report at bugs.python.org  Fri Oct  4 14:17:07 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 04 Oct 2019 18:17:07 +0000
Subject: [issue38328] Speed up the creation time of constant list literals.
In-Reply-To: <1569862645.36.0.924344090693.issue38328@roundup.psfhosted.org>
Message-ID: <1570213027.25.0.908161465771.issue38328@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

Yes, I was thinking about that (and BUILD_CONST_KEY_MAP as well). I'll open another PR with those as soon as this one is in.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38328>
_______________________________________

From report at bugs.python.org  Fri Oct  4 14:18:00 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 04 Oct 2019 18:18:00 +0000
Subject: [issue34938] Fix mimetype.init() to account for from import
In-Reply-To: <1539036789.21.0.545547206417.issue34938@psf.upfronthosting.co.za>
Message-ID: <1570213080.26.0.8871571263.issue34938@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Adding email team here, since you were pinged on the PR.

PR 16567 doesn't fix the `inited` member, which is considerably more difficult to do, unfortunately, but it does mean that it's out of sync with the values you hold. Arguably this is a better state to be in though.

Unfortunately, the "internal" data structures referred to in the docs[1] are all documented public API, which means we can't just ignore this issue :( We ought to at least update the docs to mention that `inited` won't be updated if you've `from ... import`ed it (which would normally be obvious, except that now some other values _will_ be updated).

Also, the `init` docs say that it will only be completely rebuilt when `files` is `None` (and specifically calls out passing an empty list as a way to avoid this happening). I'm pretty sure we don't respect this now.

All up, I think we have more work to do here to get the behaviour right. Alternatively, we can make changes in 3.9 to specify better usage (such as explicitly discouraging direct use of the dictionaries and adding more helper functions if necessary).

[1]: https://docs.python.org/3/library/mimetypes.html#mimetypes.init

----------
nosy: +barry, maxking, r.david.murray, steve.dower
versions: +Python 3.9 -Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34938>
_______________________________________

From report at bugs.python.org  Fri Oct  4 14:25:27 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 04 Oct 2019 18:25:27 +0000
Subject: [issue34938] Fix mimetype.init() to account for from import
In-Reply-To: <1539036789.21.0.545547206417.issue34938@psf.upfronthosting.co.za>
Message-ID: <1570213527.7.0.0483766961831.issue34938@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
nosy: +brandtbucher

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34938>
_______________________________________

From report at bugs.python.org  Fri Oct  4 14:26:45 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 04 Oct 2019 18:26:45 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570213605.14.0.155837269204.issue38368@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

> We should not segfault here.

Agreed, MAX_ELEMENTS was set to be an upper bound which shouldn't be hit. I'll investigate with OP's example data and see where the bug is.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Fri Oct  4 14:28:33 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Oct 2019 18:28:33 +0000
Subject: [issue36698] Shell restart when error message contains non-BMP
 characters
In-Reply-To: <1555953357.75.0.808052597637.issue36698@roundup.psfhosted.org>
Message-ID: <1570213713.32.0.781669416695.issue36698@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

As with #22742, the problem, without PR 16583, only occurs with *nix.  On Windows, the traceback ends with "Exception: ?" and a prompt is printed.

----------
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36698>
_______________________________________

From report at bugs.python.org  Fri Oct  4 14:30:23 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 04 Oct 2019 18:30:23 +0000
Subject: [issue38348] Make python -m ast more configurable
In-Reply-To: <1570029299.56.0.0303865742584.issue38348@roundup.psfhosted.org>
Message-ID: <1570213823.68.0.762192621797.issue38348@roundup.psfhosted.org>


Change by Ivan Levkivskyi <levkivskyi at gmail.com>:


----------
nosy: +levkivskyi

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38348>
_______________________________________

From report at bugs.python.org  Fri Oct  4 14:50:19 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Oct 2019 18:50:19 +0000
Subject: [issue21084] IDLE can't deal with characters above the range
 (U+0000-U+FFFF)
In-Reply-To: <1396008065.84.0.00802001667749.issue21084@psf.upfronthosting.co.za>
Message-ID: <1570215019.35.0.418829716893.issue21084@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

As noted on #13153, files with astral chars can now be read without an exception, but the presence of astral chars messes up editing text that follows at least on the same line by misplacing the cursor.  I will open a new issue about replacing such with \U escapes.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21084>
_______________________________________

From report at bugs.python.org  Fri Oct  4 14:52:14 2019
From: report at bugs.python.org (Ali Rizvi-Santiago)
Date: Fri, 04 Oct 2019 18:52:14 +0000
Subject: [issue35173] Re-use already existing functionality to allow Python
 2.7.x (both embedded and standalone) to locate the module path according to
 the shared library
In-Reply-To: <1569459597.01.0.435639543665.issue35173@roundup.psfhosted.org>
Message-ID: <CAAOSh+YmSWTj4bB8xS0PruiS4zp1NY21B6L46=NpHK5efMiYcQ@mail.gmail.com>


Ali Rizvi-Santiago <arizvisa at gmail.com> added the comment:

Sure. It was for Python2 anyways.

-Ali

On Wed, Sep 25, 2019 at 8:00 PM STINNER Victor <report at bugs.python.org>
wrote:

>
> STINNER Victor <vstinner at python.org> added the comment:
>
> Modules/getpath.c and PC/getpathp.c have been deeply reworked with the
> implementation of the PEP 587 in Python 3.8. Parameters which are already
> set (ex: Py_SetProgramName() or using the new PyConfig API) are no longer
> overriden. I added some tests on the "path configuration".
>
> The most reliable way to configure the path configuration is now to use
> the new initialization API using PyConfig.
> https://docs.python.org/dev/c-api/init_config.html
>
> ----------
> nosy: +vstinner
> resolution:  -> fixed
> stage:  -> resolved
> status: open -> closed
> versions: +Python 3.8, Python 3.9 -Python 2.7
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue35173>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35173>
_______________________________________

From report at bugs.python.org  Fri Oct  4 16:41:49 2019
From: report at bugs.python.org (Ashley Whetter)
Date: Fri, 04 Oct 2019 20:41:49 +0000
Subject: [issue33714] module can set an exception in tp_clear
In-Reply-To: <1527769305.39.0.682650639539.issue33714@psf.upfronthosting.co.za>
Message-ID: <1570221709.51.0.649293827496.issue33714@roundup.psfhosted.org>


Ashley Whetter <ashley at awhetter.co.uk> added the comment:

I've attached a reproduction case. Here's the setup.py that I used:

```
from distutils.core import Extension, setup

extension = Extension("breaky", ["breaky.c"])

setup(
    name="tp_clear",
    version="0.1.0",
    ext_modules=[extension],
)
```

which I built and ran with:
```
python setup.py build_ext --inplace
python -c "import breaky, gc; a = breaky.Breaky(); a = 1"
```

----------
nosy: +AWhetter
Added file: https://bugs.python.org/file48642/breaky.c

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33714>
_______________________________________

From report at bugs.python.org  Fri Oct  4 16:43:30 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 20:43:30 +0000
Subject: [issue38348] Make python -m ast more configurable
In-Reply-To: <1570029299.56.0.0303865742584.issue38348@roundup.psfhosted.org>
Message-ID: <1570221810.48.0.597675649618.issue38348@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Sorry, I do not understand you. typed_ast does not have such features as multiline dump() and CLI. What relation is this have with the --type-comments flag?

As for fitting tree into the terminal width, the current indentation is 3 spaces. Changing it to 2 spaces will not save much horisontal space, and 1-space indentation is not particularly readable.

I do not want to complicate this tiny feature. If you want more control on the output, you can write a small Python script which calls ast.dump() programmatically.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38348>
_______________________________________

From report at bugs.python.org  Fri Oct  4 16:57:03 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 04 Oct 2019 20:57:03 +0000
Subject: [issue38328] Speed up the creation time of constant list literals.
In-Reply-To: <1569862645.36.0.924344090693.issue38328@roundup.psfhosted.org>
Message-ID: <1570222623.67.0.716088555942.issue38328@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

...unless you'd prefer that I add them to this PR. But I think it's a better idea to add and review them separately.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38328>
_______________________________________

From report at bugs.python.org  Fri Oct  4 16:58:02 2019
From: report at bugs.python.org (Adam Stewart)
Date: Fri, 04 Oct 2019 20:58:02 +0000
Subject: [issue26510] [argparse] Add required argument to add_subparsers
In-Reply-To: <1457445361.5.0.530669445668.issue26510@psf.upfronthosting.co.za>
Message-ID: <1570222682.36.0.933925936981.issue26510@roundup.psfhosted.org>


Change by Adam Stewart <ajstewart426 at gmail.com>:


----------
pull_requests: +16178
pull_request: https://github.com/python/cpython/pull/16588

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26510>
_______________________________________

From report at bugs.python.org  Fri Oct  4 18:03:38 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 22:03:38 +0000
Subject: [issue38328] Speed up the creation time of constant list literals.
In-Reply-To: <1569862645.36.0.924344090693.issue38328@roundup.psfhosted.org>
Message-ID: <1570226618.94.0.692457078052.issue38328@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Okay, but first I want to solve an issue with list overallocation.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38328>
_______________________________________

From report at bugs.python.org  Fri Oct  4 18:18:26 2019
From: report at bugs.python.org (Wenzel Jakob)
Date: Fri, 04 Oct 2019 22:18:26 +0000
Subject: [issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent()
 Internal
In-Reply-To: <1569352841.72.0.766028949986.issue38266@roundup.psfhosted.org>
Message-ID: <1570227506.19.0.852009018242.issue38266@roundup.psfhosted.org>


Wenzel Jakob <wenzel at inf.ethz.ch> added the comment:

This is great -- thank you for handling this so quickly.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38266>
_______________________________________

From report at bugs.python.org  Fri Oct  4 18:43:43 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 22:43:43 +0000
Subject: [issue38373] List overallocation strategy
Message-ID: <1570229023.08.0.986734049649.issue38373@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

Currently list uses the following formula for allocating an array for items (if size != 0):

    allocated = size + (size >> 3) + (3 if size < 9 else 6)

If add items by 1 the growth pattern is:  0, 4, 8, 16, 25, 35, 46, 58, 72, 88, ...

I think this strategy can be improved.

1. There is no much sense in allocating the space for 25 items. The standard Python allocator returns addresses aligned to 16 bytes on 64-bit platform. It will allocate a space for 26 items. It is more efficient if the starting address is a multiple of some power of two, and perhaps larger than the pointer size.

So it may be better to allocate a multiple of two or four items. Few first sizes are multiple of four, so this is good multiplier. I suggest to use the following expression:

    allocated = (size + (size >> 3) + 6) & ~3

It adds bits AND, but removes conditional value.

2. It is common enough case if the list is created from a sequence of a known size and do not adds items anymore. Or if it is created by concatenating of few sequences. In such cases the list can overallocate a space which will never be used. For example:

>>> import sys
>>> sys.getsizeof([1, 2, 3])
80
>>> sys.getsizeof([*(1, 2, 3)])
104

List display allocates a space for exactly 3 items. But a list created from a tuple allocates a space for 6 items.

Other example. Let extend a list by 10 items at a time.

size allocated
 10     17
 20     28
 30     39
 40     51
 50     51
 60     73
 70     73
 80     96
 90     96
100    118

We need to reallocate an array after first four steps. 17 is too small for 20, 28 is too small for 30, 39 is too small for 40. So overallocating does not help, it just spends a space.

My idea, that if we adds several items at a time and need to reallocate an array, we check if the overallocated size is enough for adding the same amount of items next time. If it is not enough, we do not overallocate.

The final algorithm is:

    allocated = (size + (size >> 3) + 6) & ~3
    if size - old_size > allocated - size:
        allocated = (size + 3) & ~3

It will save a space if extend a list by many items few times.

----------
components: Interpreter Core
messages: 353976
nosy: rhettinger, serhiy.storchaka, tim.peters
priority: normal
severity: normal
status: open
title: List overallocation strategy
type: resource usage
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38373>
_______________________________________

From report at bugs.python.org  Fri Oct  4 18:55:09 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 04 Oct 2019 22:55:09 +0000
Subject: [issue38373] List overallocation strategy
In-Reply-To: <1570229023.08.0.986734049649.issue38373@roundup.psfhosted.org>
Message-ID: <1570229709.29.0.852665449103.issue38373@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
nosy: +brandtbucher

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38373>
_______________________________________

From report at bugs.python.org  Fri Oct  4 18:55:21 2019
From: report at bugs.python.org (Martijn Pieters)
Date: Fri, 04 Oct 2019 22:55:21 +0000
Subject: [issue38374] Remove weakref.ReferenceError entry from documentation
Message-ID: <1570229721.54.0.2203597595.issue38374@roundup.psfhosted.org>


New submission from Martijn Pieters <mj at python.org>:

The weakref documentation still mentions weakref.ReferenceError:

https://docs.python.org/3/library/weakref.html#weakref.ReferenceError

But this alias for the built-in ReferenceError exception was removed in the 3.0 development cycle (https://github.com/python/cpython/commit/2633c69fae7e413b2b64b01d8c0c901ae649a225#diff-b7975e9ef5a6be5f64e9bb391de03057), the last version where `weakref.ReferenceError` still exists is Python 2.7.

Please remove it, it's just confusing now.

----------
assignee: docs at python
components: Documentation
messages: 353977
nosy: docs at python, mjpieters
priority: normal
severity: normal
status: open
title: Remove weakref.ReferenceError entry from documentation
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38374>
_______________________________________

From report at bugs.python.org  Fri Oct  4 19:08:21 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 04 Oct 2019 23:08:21 +0000
Subject: [issue38373] List overallocation strategy
In-Reply-To: <1570229023.08.0.986734049649.issue38373@roundup.psfhosted.org>
Message-ID: <1570230501.37.0.54198702565.issue38373@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

We should definitely revisit the over-allocation strategy.  I last worked on the existing strategy back in 2004.  Since then, the weighting of the speed/space trade-off considerations have changed.   

We need to keep the amortized O(1) append() behavior, but possibly we would benefit from more over-allocation and fewer resizes.  Also, we should look at the interaction with the small object allocator to see if its design is causing realloc() to frequently have to move data rather than extending in place.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38373>
_______________________________________

From report at bugs.python.org  Fri Oct  4 19:17:52 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Oct 2019 23:17:52 +0000
Subject: [issue38373] List overallocation strategy
In-Reply-To: <1570229023.08.0.986734049649.issue38373@roundup.psfhosted.org>
Message-ID: <1570231072.71.0.86719155235.issue38373@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Here is some data. step is the number of items added at a time, the first row is the size, the second row is the currently allocated size, the third row is the proposed allocated size.

for step in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10):
    sizes0 = range(step, step*31, step)
    sizes1 = []
    sizes2 = []
    old_size = allocated1 = allocated2 = 0
    for size in sizes0:
        if size > allocated1:
            allocated1 = size + (size >> 3) + (3 if size < 9 else 6)
        sizes1.append(allocated1)
        if size > allocated2:
            allocated2 = (size + (size >> 3) + 6) & ~3
            if size - old_size > allocated2 - size:
                allocated2 = (size + 3) & ~3
        sizes2.append(allocated2)
        old_size = size
    print('\nstep =', step)
    print(' '.join(f'{x:3}' for x in sizes0))
    print(' '.join(f'{x:3}' for x in sizes1))
    print(' '.join(f'{x:3}' for x in sizes2))

step = 1
  1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30
  4   4   4   4   8   8   8   8  16  16  16  16  16  16  16  16  25  25  25  25  25  25  25  25  25  35  35  35  35  35
  4   4   4   4   8   8   8   8  16  16  16  16  16  16  16  16  24  24  24  24  24  24  24  24  32  32  32  32  32  32

step = 2
  2   4   6   8  10  12  14  16  18  20  22  24  26  28  30  32  34  36  38  40  42  44  46  48  50  52  54  56  58  60
  5   5   9   9  17  17  17  17  26  26  26  26  26  37  37  37  37  37  48  48  48  48  48  48  62  62  62  62  62  62
  8   8   8   8  16  16  16  16  24  24  24  24  32  32  32  32  44  44  44  44  44  44  56  56  56  56  56  56  68  68

step = 3
  3   6   9  12  15  18  21  24  27  30  33  36  39  42  45  48  51  54  57  60  63  66  69  72  75  78  81  84  87  90
  6   6  16  16  16  26  26  26  36  36  36  36  49  49  49  49  63  63  63  63  63  80  80  80  80  80  97  97  97  97
  8   8  16  16  16  24  24  24  36  36  36  36  48  48  48  48  60  60  60  60  76  76  76  76  76  92  92  92  92  92

step = 4
  4   8  12  16  20  24  28  32  36  40  44  48  52  56  60  64  68  72  76  80  84  88  92  96 100 104 108 112 116 120
  7  12  12  24  24  24  37  37  37  51  51  51  64  64  64  64  82  82  82  82 100 100 100 100 100 123 123 123 123 123
  8   8  16  16  28  28  28  40  40  40  52  52  52  68  68  68  68  84  84  84  84 104 104 104 104 104 124 124 124 124

step = 5
  5  10  15  20  25  30  35  40  45  50  55  60  65  70  75  80  85  90  95 100 105 110 115 120 125 130 135 140 145 150
  8  17  17  28  28  39  39  51  51  51  67  67  67  84  84  84 101 101 101 101 124 124 124 124 146 146 146 146 146 174
  8  16  16  28  28  36  36  48  48  60  60  60  76  76  76  96  96  96  96 116 116 116 116 140 140 140 140 140 168 168

step = 6
  6  12  18  24  30  36  42  48  54  60  66  72  78  84  90  96 102 108 114 120 126 132 138 144 150 156 162 168 174 180
  9  19  19  33  33  46  46  60  60  60  80  80  80 100 100 100 120 120 120 120 147 147 147 147 174 174 174 174 174 208
 12  12  24  24  36  36  52  52  64  64  80  80  80 100 100 100 120 120 120 120 144 144 144 144 172 172 172 172 200 200

step = 7
  7  14  21  28  35  42  49  56  63  70  77  84  91  98 105 112 119 126 133 140 147 154 161 168 175 182 189 196 203 210
 10  21  21  37  37  53  53  69  69  84  84  84 108 108 108 132 132 132 155 155 155 155 187 187 187 187 218 218 218 218
  8  16  28  28  44  44  60  60  76  76  92  92  92 116 116 116 136 136 136 160 160 160 184 184 184 184 216 216 216 216

step = 8
  8  16  24  32  40  48  56  64  72  80  88  96 104 112 120 128 136 144 152 160 168 176 184 192 200 208 216 224 232 240
 12  24  24  42  42  60  60  78  78  96  96  96 123 123 123 150 150 150 177 177 177 177 213 213 213 213 249 249 249 249
  8  24  24  40  40  60  60  76  76  96  96  96 120 120 120 148 148 148 176 176 176 176 212 212 212 212 248 248 248 248

step = 9
  9  18  27  36  45  54  63  72  81  90  99 108 117 126 135 144 153 162 171 180 189 198 207 216 225 234 243 252 261 270
 16  26  36  36  56  56  76  76  97  97 117 117 117 147 147 147 178 178 178 208 208 208 208 249 249 249 249 289 289 289
 12  20  36  36  56  56  76  76  96  96 116 116 136 136 136 168 168 168 196 196 196 228 228 228 228 268 268 268 268 308

step = 10
 10  20  30  40  50  60  70  80  90 100 110 120 130 140 150 160 170 180 190 200 210 220 230 240 250 260 270 280 290 300
 17  28  39  51  51  73  73  96  96 118 118 141 141 141 174 174 174 208 208 208 242 242 242 242 287 287 287 287 332 332
 12  20  32  40  60  60  84  84 104 104 128 128 152 152 152 184 184 184 216 216 216 252 252 252 252 296 296 296 296 340

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38373>
_______________________________________

From report at bugs.python.org  Fri Oct  4 19:43:22 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 04 Oct 2019 23:43:22 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570232602.86.0.578042023447.issue38368@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
keywords: +patch
pull_requests: +16179
stage: test needed -> patch review
pull_request: https://github.com/python/cpython/pull/16589

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Fri Oct  4 20:00:27 2019
From: report at bugs.python.org (Ashley Whetter)
Date: Sat, 05 Oct 2019 00:00:27 +0000
Subject: [issue33714] module can set an exception in tp_clear
In-Reply-To: <1527769305.39.0.682650639539.issue33714@psf.upfronthosting.co.za>
Message-ID: <1570233627.28.0.854774362137.issue33714@roundup.psfhosted.org>


Ashley Whetter <ashley at awhetter.co.uk> added the comment:

I've just realised that this issue was specific to tp_clear on a module and not on objects. tp_clear on modules has already been fixed in https://bugs.python.org/issue33622.
I think this is closable.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33714>
_______________________________________

From report at bugs.python.org  Fri Oct  4 20:29:40 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 05 Oct 2019 00:29:40 +0000
Subject: [issue38341] Add SMTPNotSupportedError in the exports of smtplib
In-Reply-To: <1569963046.98.0.477841717728.issue38341@roundup.psfhosted.org>
Message-ID: <1570235380.04.0.156078552872.issue38341@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

It seems that SMTPNotSupportedError is publicly documented, it should be a part of __all__.

----------
nosy: +maxking

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38341>
_______________________________________

From report at bugs.python.org  Fri Oct  4 20:31:02 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 05 Oct 2019 00:31:02 +0000
Subject: [issue38341] Add SMTPNotSupportedError in the exports of smtplib
In-Reply-To: <1569963046.98.0.477841717728.issue38341@roundup.psfhosted.org>
Message-ID: <1570235462.01.0.361995511597.issue38341@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:


New changeset 3faf826e5879536d2272f1a51c58965a16827f81 by Abhilash Raj (nde) in branch 'master':
bpo-38341: Add SMTPNotSupportedError in the exports of smtplib (#16525)
https://github.com/python/cpython/commit/3faf826e5879536d2272f1a51c58965a16827f81


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38341>
_______________________________________

From report at bugs.python.org  Fri Oct  4 20:31:19 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 05 Oct 2019 00:31:19 +0000
Subject: [issue38341] Add SMTPNotSupportedError in the exports of smtplib
In-Reply-To: <1569963046.98.0.477841717728.issue38341@roundup.psfhosted.org>
Message-ID: <1570235479.01.0.690333754313.issue38341@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16180
pull_request: https://github.com/python/cpython/pull/16590

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38341>
_______________________________________

From report at bugs.python.org  Fri Oct  4 21:18:00 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 05 Oct 2019 01:18:00 +0000
Subject: [issue38232] empty local-part in addr_spec displayed incorrectly
In-Reply-To: <1568990050.48.0.808924350002.issue38232@roundup.psfhosted.org>
Message-ID: <1570238280.35.0.656906236806.issue38232@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

It is actually parsed correctly and serialized back when you try to convert it to a string representation:

from email.parser import BytesFeedParser
import email.policy

def main():
    eml_string = 'From: Nobody <""@example.org>'
    parser = BytesFeedParser(policy = email.policy.default)
    parser.feed(eml_string.encode())
    msg = parser.close()
    print(msg.get('From').addresses[0].addr_spec)
    print(repr(msg.get('From')._parse_tree))
    print(msg.as_string())

Running this gives me:


@example.org
AddressList([Address([Mailbox([NameAddr([DisplayName([Atom([ValueTerminal('Nobody'), CFWSList([WhiteSpaceTerminal(' ')])])]), AngleAddr([ValueTerminal('<'), AddrSpec([LocalPart([QuotedString([BareQuotedString([ValueTerminal('')])])]), ValueTerminal('@'), Domain([DotAtom([DotAtomText([ValueTerminal('example'), ValueTerminal('.'), ValueTerminal('org')])])])]), ValueTerminal('>')])])])])])
From: Nobody <""@example.org>


Notice the : AddrSpec([LocalPart([QuotedString([BareQuotedString([ValueTerminal('')])])])

print() converts the addr-spec into a string, which omits the quotes. This is true for any non-none string too:


hello at example.org
AddressList([Address([Mailbox([NameAddr([DisplayName([Atom([ValueTerminal('Nobody'), CFWSList([WhiteSpaceTerminal(' ')])])]), AngleAddr([ValueTerminal('<'), AddrSpec([LocalPart([QuotedString([BareQuotedString([ValueTerminal('hello')])])]), ValueTerminal('@'), Domain([DotAtom([DotAtomText([ValueTerminal('example'), ValueTerminal('.'), ValueTerminal('org')])])])]), ValueTerminal('>')])])])])])
From: Nobody <"hello"@example.org>


If you prefer the string representation of the header's parsed value, you can try:

    print(msg.get('From').fold(policy=email.policy.default))

Which prints:

    From: Nobody <""@example.org>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38232>
_______________________________________

From report at bugs.python.org  Fri Oct  4 22:07:41 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Sat, 05 Oct 2019 02:07:41 +0000
Subject: [issue38167] O_DIRECT read fails with 4K mmap buffer
In-Reply-To: <1568417320.49.0.42295605579.issue38167@roundup.psfhosted.org>
Message-ID: <1570241261.29.0.0638980409879.issue38167@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

> I do not believe an unbuffered file uses O_DIRECT.  This is why I use os.open(fpath, os.O_DIRECT).

Problem is you follow it with:

fo = os.fdopen(fd, 'rb+')

which introduces a Python level of buffering around the kernel unbuffered file descriptor. You'd need to pass buffering=0 to make os.fdopen avoid returning a buffered file object, making it:

fo = os.fdopen(fd, 'rb+', buffering=0)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38167>
_______________________________________

From report at bugs.python.org  Fri Oct  4 22:50:54 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 05 Oct 2019 02:50:54 +0000
Subject: [issue38308] Add optional weighting to statistics.harmonic_mean()
In-Reply-To: <1569695295.83.0.838130885601.issue38308@roundup.psfhosted.org>
Message-ID: <1570243854.77.0.571190393326.issue38308@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

@rhettinger
If you are okay, Can I process with this issue with your guide?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38308>
_______________________________________

From report at bugs.python.org  Fri Oct  4 23:24:43 2019
From: report at bugs.python.org (Tim Peters)
Date: Sat, 05 Oct 2019 03:24:43 +0000
Subject: [issue38373] List overallocation strategy
In-Reply-To: <1570229023.08.0.986734049649.issue38373@roundup.psfhosted.org>
Message-ID: <1570245883.54.0.886767259366.issue38373@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

WRT pymalloc, it will always copy on growing resize in this context.  A pymalloc pool is dedicated to blocks of the same size class, so if the size class increases (they're 16 bytes apart now), the data must be copied to a different pool (dedicated to blocks of the larger size class).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38373>
_______________________________________

From report at bugs.python.org  Fri Oct  4 23:43:23 2019
From: report at bugs.python.org (Samuel Marks)
Date: Sat, 05 Oct 2019 03:43:23 +0000
Subject: [issue22240] argparse support for "python -m module" in help
In-Reply-To: <1408564751.42.0.897410433728.issue22240@psf.upfronthosting.co.za>
Message-ID: <1570247003.46.0.220957585643.issue22240@roundup.psfhosted.org>


Samuel Marks <samuelmarks at gmail.com> added the comment:

Until this is accepted, I've modified my codebase:
```
from argparse import ArgumentParser

ArgumentParser(
  prog=None if globals().get('__spec__') is None else 'python -m {}'.format(__spec__.name.partition('.')[0])
)
```

----------
nosy: +samuelmarks

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22240>
_______________________________________

From report at bugs.python.org  Sat Oct  5 00:01:50 2019
From: report at bugs.python.org (Paul)
Date: Sat, 05 Oct 2019 04:01:50 +0000
Subject: [issue38167] O_DIRECT read fails with 4K mmap buffer
In-Reply-To: <1568417320.49.0.42295605579.issue38167@roundup.psfhosted.org>
Message-ID: <1570248110.82.0.448551480219.issue38167@roundup.psfhosted.org>


Paul <paul.carlisle at gmail.com> added the comment:

> Problem is you follow it with:
>
> fo = os.fdopen(fd, 'rb+')

> which introduces a Python level of buffering around the kernel unbuffered file descriptor. You'd need to pass buffering=0 to make os.fdopen avoid returning a buffered file object, making it:

> fo = os.fdopen(fd, 'rb+', buffering=0)

You are absolutely right!  This fixed the issue.  So... is this not a bug, then?  Should I discard my patch?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38167>
_______________________________________

From report at bugs.python.org  Sat Oct  5 00:05:03 2019
From: report at bugs.python.org (Samuel Marks)
Date: Sat, 05 Oct 2019 04:05:03 +0000
Subject: [issue22240] argparse support for "python -m module" in help
In-Reply-To: <1408564751.42.0.897410433728.issue22240@psf.upfronthosting.co.za>
Message-ID: <1570248303.76.0.527936524934.issue22240@roundup.psfhosted.org>


Samuel Marks <samuelmarks at gmail.com> added the comment:

See https://bugs.python.org/msg353987 for manual test

----------
Added file: https://bugs.python.org/file48643/prog-module-name-handler.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22240>
_______________________________________

From report at bugs.python.org  Sat Oct  5 00:43:16 2019
From: report at bugs.python.org (Batuhan)
Date: Sat, 05 Oct 2019 04:43:16 +0000
Subject: [issue38348] Make python -m ast more configurable
In-Reply-To: <1570029299.56.0.0303865742584.issue38348@roundup.psfhosted.org>
Message-ID: <1570250596.25.0.160159494372.issue38348@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

> I do not want to complicate this tiny feature.
Making more configurable isn't making it complicated. It is just improving users control over it by indentation and parsing option.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38348>
_______________________________________

From report at bugs.python.org  Sat Oct  5 01:14:21 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 05 Oct 2019 05:14:21 +0000
Subject: [issue38373] List overallocation strategy
In-Reply-To: <1570229023.08.0.986734049649.issue38373@roundup.psfhosted.org>
Message-ID: <1570252461.76.0.933268757289.issue38373@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

> WRT pymalloc, it will always copy on growing resize in this context

That sounds like an excellent reason NOT to use pymalloc ;-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38373>
_______________________________________

From report at bugs.python.org  Sat Oct  5 01:16:48 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 05 Oct 2019 05:16:48 +0000
Subject: [issue38308] Add optional weighting to statistics.harmonic_mean()
In-Reply-To: <1569695295.83.0.838130885601.issue38308@roundup.psfhosted.org>
Message-ID: <1570252608.82.0.48222765669.issue38308@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

> Can I process with this issue with your guide?

Thank you, but this is one I would like to do myself.  I've already done work on it and would like to wrap it up (also, it's more complicated than it seems because the supporting functions are a bit awkward to use in this context).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38308>
_______________________________________

From report at bugs.python.org  Sat Oct  5 01:32:19 2019
From: report at bugs.python.org (Tim Peters)
Date: Sat, 05 Oct 2019 05:32:19 +0000
Subject: [issue38373] List overallocation strategy
In-Reply-To: <1570229023.08.0.986734049649.issue38373@roundup.psfhosted.org>
Message-ID: <1570253539.93.0.621590103007.issue38373@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

Don't know.  Define "the problem" ;-)  As soon as the allocation is over 512 bytes (64 pointers), it's punted to the system malloc family.  Before then, do a relative handful of relatively small memcpy's really matter?

pymalloc is faster than system mallocs, and probably uses space more efficiently.  There are no pure wins here :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38373>
_______________________________________

From report at bugs.python.org  Sat Oct  5 01:52:51 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 05 Oct 2019 05:52:51 +0000
Subject: [issue38316] docs: Code object's "co_stacksize" field is described
 with mistake
In-Reply-To: <1569789294.48.0.284805020981.issue38316@roundup.psfhosted.org>
Message-ID: <1570254771.04.0.651373431069.issue38316@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
versions:  -Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38316>
_______________________________________

From report at bugs.python.org  Sat Oct  5 02:04:24 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 05 Oct 2019 06:04:24 +0000
Subject: [issue38324] [Windows] test_locale and test__locale failures on
 Windows
In-Reply-To: <1569849277.36.0.00648751871696.issue38324@roundup.psfhosted.org>
Message-ID: <1570255464.42.0.0896609467688.issue38324@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

I started a report on failures on my machine a few days ago, but never finished editing.  I am pasting in what I wrote so far. The same 4 tests fail today with a rebuild 12 hours ago.
---

I ran the test suite on my 64-bit Win10 machine with fresh debug 32 builds in freshly updated repository.
3.9 - tests failed for _locale, locale, and winconsoleio and import
3.8 - tests failed for _locale, locale, and winconsoleio
3.7 - tests failed for _locale, locale, and winconsoleio

=====================================================================================
f:\dev\3x>python -m test -j0 -ugui
Running Debug|Win32 interpreter...
== CPython 3.9.0a0 (heads/master:c5a7e0ce19, Sep 28 2019, 13:58:57) [MSC v.1900 32 bit (Intel)]
== Windows-10-10.0.18362-SP0 little-endian
== cwd: F:\dev\3x\build\test_python_12736
== CPU count: 12
== encodings: locale=cp1252, FS=utf-8
Run tests in parallel using 14 child processes
____________________________________________________________________________________
Failure 1.
test test__locale failed -- Traceback (most recent call last):
  File "F:\dev\3x\lib\test\test__locale.py", line 133, in test_lc_numeric_localeconv
    if self.numeric_tester('localeconv', formatting[lc], lc, loc):
  File "F:\dev\3x\lib\test\test__locale.py", line 97, in numeric_tester
    self.assertEqual(calc_value, known_value,
AssertionError: ',' != '\u066b'
- ,
+ \u066b
 : , != \u066b (localeconv for decimal_point; set to ps_AF, using ps_AF)
___________________________________________________________________________

Failure 2:
test_importlib failed -- running: test_concurrent_futures (1 min 6 sec)
Failed to import test module: test.test_importlib.import_.test_fromlist
Traceback (most recent call last):
  File "F:\dev\3x\lib\unittest\loader.py", line 436, in _find_test_path
    module = self._get_module_from_name(name)
  File "F:\dev\3x\lib\unittest\loader.py", line 377, in _get_module_from_name
    __import__(name)
ValueError: source code string cannot contain null bytes

test test_importlib crashed -- Traceback (most recent call last):
  File "F:\dev\3x\lib\test\libregrtest\runtest.py", line 270, in _runtest_inner
    refleak = _runtest_inner2(ns, test_name)
  File "F:\dev\3x\lib\test\libregrtest\runtest.py", line 234, in _runtest_inner2
    test_runner()
  File "F:\dev\3x\lib\test\libregrtest\runtest.py", line 208, in _test_module
    raise Exception("errors while loading tests")
Exception: errors while loading tests
_____________________________________________________________________________________

Failure 3.
test test_locale failed -- Traceback (most recent call last):
  File "F:\dev\3x\lib\test\test_locale.py", line 567, in test_getsetlocale_issue1813
    locale.setlocale(locale.LC_CTYPE, loc)
  File "F:\dev\3x\lib\locale.py", line 608, in setlocale
    return _setlocale(category, locale)
locale.Error: unsupported locale setting
_____________________________________________________________________________________

Failure 4. test_winconsoleio

ERROR: test_input (test.test_winconsoleio.WindowsConsoleIOTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "F:\dev\3x\lib\test\test_winconsoleio.py", line 148, in test_input
    self.assertStdinRoundTrip('\U00100000\U0010ffff\U0010fffd')
  File "F:\dev\3x\lib\test\test_winconsoleio.py", line 135, in assertStdinRoundTrip
    actual = input()
OSError: [WinError 87] The parameter is incorrect

======================================================================
ERROR: test_partial_reads (test.test_winconsoleio.WindowsConsoleIOTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "F:\dev\3x\lib\test\test_winconsoleio.py", line 161, in test_partial_reads
    b = stdin.read(read_count)
OSError: [WinError 87] The parameter is incorrect

======================================================================
ERROR: test_partial_surrogate_reads (test.test_winconsoleio.WindowsConsoleIOTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "F:\dev\3x\lib\test\test_winconsoleio.py", line 178, in test_partial_surrogate_reads
    b = stdin.read(read_count)
OSError: [WinError 87] The parameter is incorrect
______________________________________________________________________________________

5. Non-failure tracebacks displayed passing test_concurrent_futures

Cancelling an overlapped future failed
future: <_OverlappedFuture pending overlapped=<pending, 0x432ab70> cb=[BaseProactorEventLoop._loop_self_reading()]>
Traceback (most recent call last):
  File "F:\dev\3x\lib\asyncio\windows_events.py", line 66, in _cancel_overlapped
    self._ov.cancel()
OSError: [WinError 6] The handle is invalid
Cancelling an overlapped future failed
future: <_OverlappedFuture pending overlapped=<pending, 0x432ab70> cb=[BaseProactorEventLoop._loop_self_reading()]>
Traceback (most recent call last):
  File "F:\dev\3x\lib\asyncio\windows_events.py", line 66, in _cancel_overlapped
    self._ov.cancel()
OSError: [WinError 6] The handle is invalid
Error on reading from the event loop self pipe
loop: <ProactorEventLoop running=True closed=False debug=False>
Traceback (most recent call last):
  File "F:\dev\3x\lib\asyncio\windows_events.py", line 453, in finish_recv
    return ov.getresult()
OSError: [WinError 995] The I/O operation has been aborted because of either a thread exit or an application request
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "F:\dev\3x\lib\asyncio\proactor_events.py", line 768, in _loop_self_reading
    f.result()  # may raise
  File "F:\dev\3x\lib\asyncio\windows_events.py", line 808, in _poll
    value = callback(transferred, key, ov)
  File "F:\dev\3x\lib\asyncio\windows_events.py", line 457, in finish_recv
    raise ConnectionResetError(*exc.args)
ConnectionResetError: [WinError 995] The I/O operation has been aborted because of either a thread exit or an application request
F:\dev\3x\lib\asyncio\base_events.py:673: ResourceWarning: unclosed event loop <ProactorEventLoop running=False closed=False debug=False>
  _warn(f"unclosed event loop {self!r}", ResourceWarning, source=self)
ResourceWarning: Enable tracemalloc to get the object allocation traceback
=========================================================================================

3.8 CPython 3.8.0b4+ (heads/3.8:36c6fa9680, Sep 28 2019, 14:00:28) [MSC v.1900 32 bit (Intel)]

test_locale, locale, and winconsoleio failed as before, test_import ok.

3.7 CPython 3.7.4+ (heads/3.7:80dd66ac27, Sep 28 2019, 14:01:04)

test_locale, locale, and winconsoleio failed as before
test_compileall, tools also failed temporarily due to local issues with ntpath.*.pyc and scripts/reindent.py, which I fixed.
========================================================================================
Looking at some of the other failures.

3. def test_getsetlocale_issue1813(self):
       # Issue #1813: setting and getting the locale under a Turkish locale
       https://bugs.python.org/issue1813 (closed 2011, 2012)

>>> locale.setlocale(locale.LC_CTYPE, 'tr_TR')
'tr_TR'
>>> loc = locale.getlocale(locale.LC_CTYPE)
>>> loc
('tr_TR', 'ISO8859-9')
>>> locale.setlocale(locale.LC_CTYPE, loc)
Traceback (most recent call last):
  File "<pyshell#6>", line 1, in <module>
    locale.setlocale(locale.LC_CTYPE, loc)
  File "C:\Programs\Python38\lib\locale.py", line 608, in setlocale
    return _setlocale(category, locale)
locale.Error: unsupported locale setting

Some change made this fail again, after being fixed on my local machine, even if it continues to work on buildbots.

----------
nosy: +terry.reedy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38324>
_______________________________________

From report at bugs.python.org  Sat Oct  5 02:23:39 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 05 Oct 2019 06:23:39 +0000
Subject: [issue38331] Exec not recognizing global variables inside function
In-Reply-To: <1569875978.41.0.850227388561.issue38331@roundup.psfhosted.org>
Message-ID: <1570256619.96.0.83896826246.issue38331@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Ronald is correct, and for the reason given.  Python functions are lexically scoped, not dynamically scoped, and you are expecting the latter.  The exec global and local namespaces are used to resolve identifier in the code you pass.  Your first example passes 'func' and that is resolved to the *pre-compiled* function object which uses is lexicographical globals.  It does not contain the func-local 'var'.  You second example contains a def statement to be compiled in the exec namespaces.  Please post to python-list if you want further discussion.

----------
nosy: +terry.reedy
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38331>
_______________________________________

From report at bugs.python.org  Sat Oct  5 02:44:43 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 05 Oct 2019 06:44:43 +0000
Subject: [issue38345] Add end lines to pyclbr objects
Message-ID: <1570257883.59.0.504869825391.issue38345@roundup.psfhosted.org>


New submission from Terry J. Reedy <tjreedy at udel.edu>:

I am closing this for now because there is no information upon which to proceed, and because you closed your PR (without explanation).  The nested dicts returned by pyclbr already constitute a tree of nesting relationships between the functions and classes defined in a module.  IDLE, for instance, uses this for its module browser.  (The obsolete name 'pyclbr' comes from when it only returned, I believe, a dict of top-level classes.)

----------
nosy: +terry.reedy
resolution:  -> postponed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38345>
_______________________________________

From report at bugs.python.org  Sat Oct  5 03:20:01 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 05 Oct 2019 07:20:01 +0000
Subject: [issue38349] Email example using imaginary library installation error.
In-Reply-To: <1570032603.68.0.429442517445.issue38349@roundup.psfhosted.org>
Message-ID: <1570260001.52.0.952140751848.issue38349@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

The rest of the overly long title was "The install shows that it only supports python 2.x but is listed under python 3.6+ docs."

The lines in question are from the 2nd to last example.

  # An imaginary module that would make this work and be safe.
  from imaginary import magic_html_parser

The comment plus the names 'imaginary' and 'magic_html_parser' should make it pretty clear that 'imaginary' is meant to be an imaginary, hypothetical module with an imaginary, hypothetical method, not an actual module named 'imaginary' with an actual 'magic_html_parser' method.

jackotonye, do you have a concrete suggestion?  I am tempted to close this, but will wait for suggestion and let the email people see this.

Also, when responding by email, please remove the quoted previous post and it is redundant on the web page.

----------
nosy: +barry, maxking, r.david.murray, terry.reedy
title: Email example using imaginary library installation error. The install shows that it only supports python 2.x but is listed under python 3.6+ docs. -> Email example using imaginary library installation error.
versions:  -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38349>
_______________________________________

From report at bugs.python.org  Sat Oct  5 04:09:38 2019
From: report at bugs.python.org (SilentGhost)
Date: Sat, 05 Oct 2019 08:09:38 +0000
Subject: [issue38349] Email example using imaginary library installation error.
In-Reply-To: <1570032603.68.0.429442517445.issue38349@roundup.psfhosted.org>
Message-ID: <1570262978.27.0.110210532946.issue38349@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

One fairly naive solution would be to define a magic_html_parser directly in the example and move explanatory comment there. In order not to break the code it could return an empty string.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38349>
_______________________________________

From report at bugs.python.org  Sat Oct  5 04:22:34 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 05 Oct 2019 08:22:34 +0000
Subject: [issue33714] module can set an exception in tp_clear
In-Reply-To: <1527769305.39.0.682650639539.issue33714@psf.upfronthosting.co.za>
Message-ID: <1570263754.9.0.95003805912.issue33714@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16181
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16592

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33714>
_______________________________________

From report at bugs.python.org  Sat Oct  5 04:58:13 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 05 Oct 2019 08:58:13 +0000
Subject: [issue38308] Add optional weighting to statistics.harmonic_mean()
In-Reply-To: <1569695295.83.0.838130885601.issue38308@roundup.psfhosted.org>
Message-ID: <1570265893.91.0.352083511089.issue38308@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

Oh.. Thank you for letting me know

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38308>
_______________________________________

From report at bugs.python.org  Sat Oct  5 05:57:50 2019
From: report at bugs.python.org (STINNER Victor)
Date: Sat, 05 Oct 2019 09:57:50 +0000
Subject: [issue38266] Revert bpo-37878: Make PyThreadState_DeleteCurrent()
 Internal
In-Reply-To: <1569352841.72.0.766028949986.issue38266@roundup.psfhosted.org>
Message-ID: <1570269470.85.0.36322125948.issue38266@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> This is great -- thank you for handling this so quickly.

Thanks for testing the master branch and reporting regressions quickly as well ;-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38266>
_______________________________________

From report at bugs.python.org  Sat Oct  5 06:43:35 2019
From: report at bugs.python.org (hai shi)
Date: Sat, 05 Oct 2019 10:43:35 +0000
Subject: [issue14364] Argparse incorrectly handles '--' as argument to option
In-Reply-To: <1332080953.55.0.495639573781.issue14364@psf.upfronthosting.co.za>
Message-ID: <1570272215.5.0.458255108897.issue14364@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

Hi, Jonas. Thanks for your report.
Let us wait core team's discuss;)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue14364>
_______________________________________

From report at bugs.python.org  Sat Oct  5 07:38:34 2019
From: report at bugs.python.org (Mario Corchero)
Date: Sat, 05 Oct 2019 11:38:34 +0000
Subject: [issue38346] Wrong behavior when using `assert_called_with` with
 mutable object
In-Reply-To: <1570006369.69.0.450054962888.issue38346@roundup.psfhosted.org>
Message-ID: <1570275514.92.0.746149907259.issue38346@roundup.psfhosted.org>


Mario Corchero <mariocj89 at gmail.com> added the comment:

Thanks! We can look at adding a copying mock if we see people needing it, but yeah, adding copy by default would be quite complex if we don't want to break existing users.

----------
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38346>
_______________________________________

From report at bugs.python.org  Sat Oct  5 07:56:36 2019
From: report at bugs.python.org (Massimo)
Date: Sat, 05 Oct 2019 11:56:36 +0000
Subject: [issue38375] Enum lookup fails for callable values
Message-ID: <1570276596.73.0.237929240562.issue38375@roundup.psfhosted.org>


New submission from Massimo <massimo at typish.io>:

```
from enum import Enum

class T(Enum):
  TEST = 1

print(T["TEST"])

class S(Enum):
  TEST = lambda a: a

print(S["TEST"])
```
fails with `KeyError: 'TEST'` on the last line.

----------
components: Interpreter Core
messages: 354003
nosy: typish
priority: normal
severity: normal
status: open
title: Enum lookup fails for callable values
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38375>
_______________________________________

From report at bugs.python.org  Sat Oct  5 08:01:00 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 05 Oct 2019 12:01:00 +0000
Subject: [issue38375] Enum lookup fails for callable values
In-Reply-To: <1570276596.73.0.237929240562.issue38375@roundup.psfhosted.org>
Message-ID: <1570276860.16.0.29007046906.issue38375@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +ethan.furman

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38375>
_______________________________________

From report at bugs.python.org  Sat Oct  5 08:16:13 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 05 Oct 2019 12:16:13 +0000
Subject: [issue38335] simplify overlaps function in ipaddress.py
In-Reply-To: <1569930223.76.0.865877463422.issue38335@roundup.psfhosted.org>
Message-ID: <1570277773.98.0.0249119503699.issue38335@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

What is the benefit of your version?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38335>
_______________________________________

From report at bugs.python.org  Sat Oct  5 08:25:55 2019
From: report at bugs.python.org (Sanjay)
Date: Sat, 05 Oct 2019 12:25:55 +0000
Subject: [issue38335] simplify overlaps function in ipaddress.py
In-Reply-To: <1569930223.76.0.865877463422.issue38335@roundup.psfhosted.org>
Message-ID: <1570278355.21.0.518525591835.issue38335@roundup.psfhosted.org>


Sanjay <sanjay537 at gmail.com> added the comment:

the version in the patch is less code a or b or c or d becomes a or d

the version in PR is using the subnet_of, supernet_of function because overlap means either a is subnet_of or supernet_of b. So was trying to consolidate the implementation of overlap from 2 to 1.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38335>
_______________________________________

From report at bugs.python.org  Sat Oct  5 08:43:51 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Sat, 05 Oct 2019 12:43:51 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
Message-ID: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>


New submission from Vinay Sajip <vinay_sajip at yahoo.co.uk>:

Following

./configure --prefix=$HOME/.local --with-assertions

and then running make leads to an error:

$ make
gcc -pthread -c -Wno-unused-result -Wsign-compare -g -fwrapv -O3 -Wall    -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration  -I./Include/internal  -I. -I./Include    -DPy_BUILD_CORE -o Objects/codeobject.o Objects/codeobject.c
gcc -pthread -c -Wno-unused-result -Wsign-compare -g -fwrapv -O3 -Wall    -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration  -I./Include/internal  -I. -I./Include    -DPy_BUILD_CORE -o Objects/complexobject.o Objects/complexobject.c
gcc -pthread -c -Wno-unused-result -Wsign-compare -g -fwrapv -O3 -Wall    -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration  -I./Include/internal  -I. -I./Include    -DPy_BUILD_CORE -o Objects/descrobject.o Objects/descrobject.c
In file included from ./Include/object.h:746:0,
                 from ./Include/pytime.h:6,
                 from ./Include/Python.h:85,
                 from Objects/descrobject.c:3:
./Include/object.h:111:38: error: expected ?)? before ?*? token
 #define _PyObject_CAST(op) ((PyObject*)(op))
                                      ^
./Include/cpython/object.h:337:36: note: in definition of macro ?PyType_HasFeature?
 #define PyType_HasFeature(t,f)  (((t)->tp_flags & (f)) != 0)
                                    ^
./Include/unicodeobject.h:115:18: note: in expansion of macro ?PyType_FastSubclass?
                  PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_UNICODE_SUBCLASS)
                  ^
./Include/object.h:122:34: note: in expansion of macro ?_PyObject_CAST?
 #define Py_TYPE(ob)             (_PyObject_CAST(ob)->ob_type)
                                  ^
./Include/unicodeobject.h:115:38: note: in expansion of macro ?Py_TYPE?
                  PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_UNICODE_SUBCLASS)
                                      ^
./Include/unicodeobject.h:1042:56: note: in expansion of macro ?PyUnicode_Check?
 #define _PyUnicode_CheckConsistency(op, check_content) PyUnicode_Check(op)
                                                        ^
./Include/internal/pycore_object.h:14:17: note: in expansion of macro ?_PyUnicode_CheckConsistency?
 PyAPI_FUNC(int) _PyUnicode_CheckConsistency(PyObject *op, int check_content);
                 ^
./Include/object.h:111:40: error: expected ?)? before ?(? token
 #define _PyObject_CAST(op) ((PyObject*)(op))
                                        ^
./Include/cpython/object.h:337:36: note: in definition of macro ?PyType_HasFeature?
 #define PyType_HasFeature(t,f)  (((t)->tp_flags & (f)) != 0)
                                    ^
./Include/unicodeobject.h:115:18: note: in expansion of macro ?PyType_FastSubclass?
                  PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_UNICODE_SUBCLASS)
                  ^
./Include/object.h:122:34: note: in expansion of macro ?_PyObject_CAST?
 #define Py_TYPE(ob)             (_PyObject_CAST(ob)->ob_type)
                                  ^
./Include/unicodeobject.h:115:38: note: in expansion of macro ?Py_TYPE?
                  PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_UNICODE_SUBCLASS)
                                      ^
./Include/unicodeobject.h:1042:56: note: in expansion of macro ?PyUnicode_Check?
 #define _PyUnicode_CheckConsistency(op, check_content) PyUnicode_Check(op)
                                                        ^
./Include/internal/pycore_object.h:14:17: note: in expansion of macro ?_PyUnicode_CheckConsistency?
 PyAPI_FUNC(int) _PyUnicode_CheckConsistency(PyObject *op, int check_content);
                 ^
./Include/object.h:122:52: error: expected ?)? before ?->? token
 #define Py_TYPE(ob)             (_PyObject_CAST(ob)->ob_type)
                                                    ^
./Include/cpython/object.h:337:36: note: in definition of macro ?PyType_HasFeature?
 #define PyType_HasFeature(t,f)  (((t)->tp_flags & (f)) != 0)
                                    ^
./Include/unicodeobject.h:115:18: note: in expansion of macro ?PyType_FastSubclass?
                  PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_UNICODE_SUBCLASS)
                  ^
./Include/unicodeobject.h:115:38: note: in expansion of macro ?Py_TYPE?
                  PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_UNICODE_SUBCLASS)
                                      ^
./Include/unicodeobject.h:1042:56: note: in expansion of macro ?PyUnicode_Check?
 #define _PyUnicode_CheckConsistency(op, check_content) PyUnicode_Check(op)
                                                        ^
./Include/internal/pycore_object.h:14:17: note: in expansion of macro ?_PyUnicode_CheckConsistency?
 PyAPI_FUNC(int) _PyUnicode_CheckConsistency(PyObject *op, int check_content);
                 ^
./Include/cpython/object.h:337:38: error: expected ?)? before ?->? token
 #define PyType_HasFeature(t,f)  (((t)->tp_flags & (f)) != 0)
                                      ^
./Include/object.h:351:35: note: in expansion of macro ?PyType_HasFeature?
 #define PyType_FastSubclass(t,f)  PyType_HasFeature(t,f)
                                   ^
./Include/unicodeobject.h:115:18: note: in expansion of macro ?PyType_FastSubclass?
                  PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_UNICODE_SUBCLASS)
                  ^
./Include/unicodeobject.h:1042:56: note: in expansion of macro ?PyUnicode_Check?
 #define _PyUnicode_CheckConsistency(op, check_content) PyUnicode_Check(op)
                                                        ^
./Include/internal/pycore_object.h:14:17: note: in expansion of macro ?_PyUnicode_CheckConsistency?
 PyAPI_FUNC(int) _PyUnicode_CheckConsistency(PyObject *op, int check_content);
                 ^
./Include/cpython/object.h:337:56: error: expected ?)? before ?!=? token
 #define PyType_HasFeature(t,f)  (((t)->tp_flags & (f)) != 0)
                                                        ^
./Include/object.h:351:35: note: in expansion of macro ?PyType_HasFeature?
 #define PyType_FastSubclass(t,f)  PyType_HasFeature(t,f)
                                   ^
./Include/unicodeobject.h:115:18: note: in expansion of macro ?PyType_FastSubclass?
                  PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_UNICODE_SUBCLASS)
                  ^
./Include/unicodeobject.h:1042:56: note: in expansion of macro ?PyUnicode_Check?
 #define _PyUnicode_CheckConsistency(op, check_content) PyUnicode_Check(op)
                                                        ^
./Include/internal/pycore_object.h:14:17: note: in expansion of macro ?_PyUnicode_CheckConsistency?
 PyAPI_FUNC(int) _PyUnicode_CheckConsistency(PyObject *op, int check_content);
                 ^
Makefile:1711: recipe for target 'Objects/descrobject.o' failed
make: *** [Objects/descrobject.o] Error 1

BTW, this happens even if Py_DEBUG=true is defined. System where the failure occurred: Ubuntu 16.04, 64-bit.

----------
components: Build
messages: 354006
nosy: vinay.sajip
priority: normal
severity: normal
status: open
title: ./configure --with-assertions generates a broken build
type: behavior
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Sat Oct  5 08:47:02 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Sat, 05 Oct 2019 12:47:02 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570279622.41.0.326754793973.issue38376@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

BTW it also seems to fail when just Py_DEBUG is specified (no --with-assertions).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Sat Oct  5 09:36:58 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 05 Oct 2019 13:36:58 +0000
Subject: [issue38375] Enum lookup fails for callable values
In-Reply-To: <1570276596.73.0.237929240562.issue38375@roundup.psfhosted.org>
Message-ID: <1570282618.83.0.839171762738.issue38375@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

https://docs.python.org/3/library/enum.html#allowed-members-and-attributes-of-enumerations

> The rules for what is allowed are as follows: names that start and end with a single underscore are reserved by enum and cannot be used; all other attributes defined within an enumeration will become members of this enumeration, with the exception of special methods (__str__(), __add__(), etc.), descriptors (methods are also descriptors), and variable names listed in _ignore_.

Looking at the code _member_names has the list of member names internally that stores the members. I guess with a callable assigned to TEST it becomes a method and is not added as a member as per the above doc to skip descriptor as method.

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38375>
_______________________________________

From report at bugs.python.org  Sat Oct  5 09:40:25 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 05 Oct 2019 13:40:25 +0000
Subject: [issue38375] Enum lookup fails for callable values
In-Reply-To: <1570276596.73.0.237929240562.issue38375@roundup.psfhosted.org>
Message-ID: <1570282825.62.0.0663685129771.issue38375@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Some relevant threads

* https://stackoverflow.com/questions/40338652/how-to-define-enum-values-that-are-functions
* https://mail.python.org/pipermail/python-ideas/2017-April/045428.html

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38375>
_______________________________________

From report at bugs.python.org  Sat Oct  5 09:47:18 2019
From: report at bugs.python.org (Matej Cepl)
Date: Sat, 05 Oct 2019 13:47:18 +0000
Subject: [issue38377]
 test_asyncio.test_events.GetEventLoopTestsMixin.test_get_event_loop_new_process
 mixin breaks in the Unix environment without working /dev/shm
Message-ID: <1570283238.14.0.402660591178.issue38377@roundup.psfhosted.org>


New submission from Matej Cepl <mcepl at cepl.eu>:

======================================================================
ERROR: test_get_event_loop_new_process (test.test_asyncio.test_events.TestCGetEventLoop)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/test/test_asyncio/test_events.py", line 2647, in test_get_event_loop_new_process
    self.loop.run_until_complete(main()),
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/asyncio/base_events.py", line 608, in run_until_complete
    return future.result()
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/test/test_asyncio/test_events.py", line 2640, in main
    pool = concurrent.futures.ProcessPoolExecutor()
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/concurrent/futures/process.py", line 555, in __init__
    self._call_queue = _SafeQueue(
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/concurrent/futures/process.py", line 165, in __init__
    super().__init__(max_size, ctx=ctx)
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/multiprocessing/queues.py", line 42, in __init__
    self._rlock = ctx.Lock()
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/multiprocessing/context.py", line 68, in Lock
    return Lock(ctx=self.get_context())
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/multiprocessing/synchronize.py", line 162, in __init__
    SemLock.__init__(self, SEMAPHORE, 1, 1, ctx=ctx)
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/multiprocessing/synchronize.py", line 57, in __init__
    sl = self._semlock = _multiprocessing.SemLock(
OSError: [Errno 38] Function not implemented

======================================================================
ERROR: test_get_event_loop_new_process (test.test_asyncio.test_events.TestPyGetEventLoop)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/test/test_asyncio/test_events.py", line 2647, in test_get_event_loop_new_process
    self.loop.run_until_complete(main()),
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/asyncio/base_events.py", line 608, in run_until_complete
    return future.result()
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/test/test_asyncio/test_events.py", line 2640, in main
    pool = concurrent.futures.ProcessPoolExecutor()
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/concurrent/futures/process.py", line 555, in __init__
    self._call_queue = _SafeQueue(
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/concurrent/futures/process.py", line 165, in __init__
    super().__init__(max_size, ctx=ctx)
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/multiprocessing/queues.py", line 42, in __init__
    self._rlock = ctx.Lock()
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/multiprocessing/context.py", line 68, in Lock
    return Lock(ctx=self.get_context())
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/multiprocessing/synchronize.py", line 162, in __init__
    SemLock.__init__(self, SEMAPHORE, 1, 1, ctx=ctx)
  File "/home/abuild/rpmbuild/BUILD/Python-3.8.0rc1/Lib/multiprocessing/synchronize.py", line 57, in __init__
    sl = self._semlock = _multiprocessing.SemLock(
OSError: [Errno 38] Function not implemented

----------------------------------------------------------------------

The problem is that in the OpenBuildService (the build system of SUSE distributions) /dev/shm is limited to:

abuild at milic:~/rpmbuild/BUILD/Python-3.8.0rc1> ls -ld /dev/shm
drwxr-xr-x 1 root root 0 Oct  5 13:23 /dev/shm
abuild at milic:~/rpmbuild/BUILD/Python-3.8.0rc1>

Provided PR will skip test if /dev/shm doesn?t exist or it doesn?t sufficient permissions.

----------
components: asyncio
messages: 354010
nosy: asvetlov, mcepl, yselivanov
priority: normal
severity: normal
status: open
title: test_asyncio.test_events.GetEventLoopTestsMixin.test_get_event_loop_new_process mixin breaks in the Unix environment without working /dev/shm
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38377>
_______________________________________

From report at bugs.python.org  Sat Oct  5 09:48:15 2019
From: report at bugs.python.org (Matej Cepl)
Date: Sat, 05 Oct 2019 13:48:15 +0000
Subject: [issue38377]
 test_asyncio.test_events.GetEventLoopTestsMixin.test_get_event_loop_new_process
 mixin breaks in the Unix environment without working /dev/shm
In-Reply-To: <1570283238.14.0.402660591178.issue38377@roundup.psfhosted.org>
Message-ID: <1570283295.86.0.335235616498.issue38377@roundup.psfhosted.org>


Change by Matej Cepl <mcepl at cepl.eu>:


----------
keywords: +patch
pull_requests: +16182
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16593

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38377>
_______________________________________

From report at bugs.python.org  Sat Oct  5 10:06:35 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Sat, 05 Oct 2019 14:06:35 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570284395.77.0.166268323523.issue38376@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

Adding Thomas and Victor based on git blame on some of the source lines concerned.

----------
nosy: +twouters, vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Sat Oct  5 11:04:03 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 05 Oct 2019 15:04:03 +0000
Subject: [issue38378] os.sendfile() has improperly named parameter
Message-ID: <1570287843.24.0.0727618245068.issue38378@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

os.sendfile() has a keyword-or-positional parameter named "in". Since it is a keyword in Python, it is not possible to pass it as a keyword argument. You can only pass it as a positional argument or using a var-keyword argument (unlikely anybody uses the latter). The preceding parameter, "out", also can not be passed by keyword because of this.

It is weird, but usually does not cause a problem. You cannot use a keyword argument, period. But it prevents os.sendfile() from converting to Argument Clinic, because Argument Clinic does not allow using Python keywords as parameter names (I already created a patch for conversion, but in needs to solve this issue first).

There are two ways to solve this issue.

1. Rename parameter "in" (and maybe "out" for consistency). "out_fd" and "in_fd" look good names (they are use in Linux manpage).

2. Make "out" and "in" positional-only parameters.

----------
components: Extension Modules
messages: 354012
nosy: serhiy.storchaka
priority: normal
severity: normal
status: open
title: os.sendfile() has improperly named parameter
type: behavior
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38378>
_______________________________________

From report at bugs.python.org  Sat Oct  5 11:11:16 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Sat, 05 Oct 2019 15:11:16 +0000
Subject: [issue38378] os.sendfile() has improperly named parameter
In-Reply-To: <1570287843.24.0.0727618245068.issue38378@roundup.psfhosted.org>
Message-ID: <1570288276.4.0.413334551841.issue38378@roundup.psfhosted.org>


Zackery Spytz <zspytz at gmail.com> added the comment:

See also bpo-15078.

----------
nosy: +ZackerySpytz

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38378>
_______________________________________

From report at bugs.python.org  Sat Oct  5 11:15:24 2019
From: report at bugs.python.org (Thomas Wouters)
Date: Sat, 05 Oct 2019 15:15:24 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570288524.89.0.838145872255.issue38376@roundup.psfhosted.org>


Change by Thomas Wouters <thomas at python.org>:


----------
keywords: +patch
pull_requests: +16183
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16594

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Sat Oct  5 11:16:13 2019
From: report at bugs.python.org (Thomas Wouters)
Date: Sat, 05 Oct 2019 15:16:13 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570288573.09.0.957200771425.issue38376@roundup.psfhosted.org>


Thomas Wouters <thomas at python.org> added the comment:

The problem is _PyUnicode_CheckConsistency switched from being only defined when Py_DEBUG is set, to being defined unconditionally. That was a good change, but it made the API-compatibility hack of #defining _PyUnicode_CheckConsistency in Include/unicodeobject.h do the wrong thing. PR #16594.

----------
stage: patch review -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Sat Oct  5 11:46:08 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 05 Oct 2019 15:46:08 +0000
Subject: [issue38349] Email example using imaginary library installation error.
In-Reply-To: <1570032603.68.0.429442517445.issue38349@roundup.psfhosted.org>
Message-ID: <1570290368.06.0.493577730632.issue38349@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

The function of this imaginary method is described below:

    # The magic_html_parser has to rewrite the href="cid:...." attributes to
    # point to the filenames in partfiles.  It also has to do a safety-sanitize
    # of the html.  It could be written using html.parser.

This implementation is going to be non-trivial (more than just a wrapper around html.parser) I think, and I would like to not make the example related to email even longer due to that implementation.

And I agree with Terry, the comment should make it pretty clear, there aren't any dependencies in the examples outside of standard library.

Any other synonym that we'd choose could end up being a package in pypi someday :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38349>
_______________________________________

From report at bugs.python.org  Sat Oct  5 11:48:06 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 05 Oct 2019 15:48:06 +0000
Subject: [issue38349] Email example using imaginary library installation error.
In-Reply-To: <1570032603.68.0.429442517445.issue38349@roundup.psfhosted.org>
Message-ID: <1570290486.43.0.695592581472.issue38349@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

The comment should make it clear that it is an made up imaginary module. The no dependencies outside of standard library is not written, I guess?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38349>
_______________________________________

From report at bugs.python.org  Sat Oct  5 12:07:49 2019
From: report at bugs.python.org (jackotonye)
Date: Sat, 05 Oct 2019 16:07:49 +0000
Subject: [issue38349] Email example using imaginary library installation error.
In-Reply-To: <1570290486.43.0.695592581472.issue38349@roundup.psfhosted.org>
Message-ID: <749E708A-2F88-4EDC-A9E4-1BCE60091EE0@gmail.com>


jackotonye <tonyejck at gmail.com> added the comment:

I?m fine with closing the issue. 

Seems trivial now after reading the comments but noting that most developers take examples as running code and spend less time going over the comments and a dependency that had similar names makes it even harder to make the point. 

If the comment was at the usage rather than at import it would be more obvious that it needs to be a custom implementation.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38349>
_______________________________________

From report at bugs.python.org  Sat Oct  5 12:15:18 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 05 Oct 2019 16:15:18 +0000
Subject: [issue38349] Email example using imaginary library installation error.
In-Reply-To: <1570032603.68.0.429442517445.issue38349@roundup.psfhosted.org>
Message-ID: <1570292118.64.0.914875201531.issue38349@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

We could move that comment to the top near the import, I am totally fine with that.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38349>
_______________________________________

From report at bugs.python.org  Sat Oct  5 12:19:21 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 05 Oct 2019 16:19:21 +0000
Subject: [issue38332] invalid content-transfer-encoding in encoded-word causes
 KeyError
In-Reply-To: <1569877053.41.0.568400002445.issue38332@roundup.psfhosted.org>
Message-ID: <1570292361.19.0.867487396675.issue38332@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:


New changeset 65dcc8a8dc41d3453fd6b987073a5f1b30c5c0fd by Abhilash Raj (Andrei Troie) in branch 'master':
bpo-38332: Catch KeyError from unknown cte in encoded-word. (GH-16503)
https://github.com/python/cpython/commit/65dcc8a8dc41d3453fd6b987073a5f1b30c5c0fd


----------
nosy: +maxking

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38332>
_______________________________________

From report at bugs.python.org  Sat Oct  5 12:19:39 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 05 Oct 2019 16:19:39 +0000
Subject: [issue38332] invalid content-transfer-encoding in encoded-word causes
 KeyError
In-Reply-To: <1569877053.41.0.568400002445.issue38332@roundup.psfhosted.org>
Message-ID: <1570292379.84.0.0274977624281.issue38332@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16184
pull_request: https://github.com/python/cpython/pull/16596

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38332>
_______________________________________

From report at bugs.python.org  Sat Oct  5 12:19:45 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 05 Oct 2019 16:19:45 +0000
Subject: [issue38332] invalid content-transfer-encoding in encoded-word causes
 KeyError
In-Reply-To: <1569877053.41.0.568400002445.issue38332@roundup.psfhosted.org>
Message-ID: <1570292385.47.0.0114547588782.issue38332@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16185
pull_request: https://github.com/python/cpython/pull/16597

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38332>
_______________________________________

From report at bugs.python.org  Sat Oct  5 13:31:26 2019
From: report at bugs.python.org (Tim Peters)
Date: Sat, 05 Oct 2019 17:31:26 +0000
Subject: [issue38379] finalizer resurrection in gc
Message-ID: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>


New submission from Tim Peters <tim at python.org>:

While people are thinking about gc, zleak.py shows a small bug, and a possible opportunity for improvement, in the way gc treats finalizers that resurrect objects.

The bug:  the stats keep claiming gc is collecting an enormous number of objects, but in fact it's not collecting any.  Objects in the unreachable set shouldn't add to the "collected" count unless they _are_ collected.

Output:

resurrecting
collect 2000002
gen 2 stats {'collections': 2, 'collected': 2000002, 'uncollectable': 0}
resurrecting
collect 4000004
gen 2 stats {'collections': 3, 'collected': 6000006, 'uncollectable': 0}
resurrecting
collect 6000006
gen 2 stats {'collections': 4, 'collected': 12000012, 'uncollectable': 0}
resurrecting
collect 8000008
gen 2 stats {'collections': 5, 'collected': 20000020, 'uncollectable': 0}
resurrecting
collect 10000010
gen 2 stats {'collections': 6, 'collected': 30000030, 'uncollectable': 0}
...

Memory use grows without bound, and collections take ever longer.

The opportunity:  if any finalizer resurrects anything, gc gives up.  But the process of computing whether anything was resurrected also determines which initially-trash objects are reachable from the risen dead.  Offhand I don't see why we couldn't proceed collecting what remains trash.  Then zleak.py would reclaim everything instead of nothing.

Sketch:  rather than just set a flag, check_garbage() could move now-reachable objects to the old generation (and, for each one moved, decrement the count of collected objects).  Then delete_garbage() could proceed on what remains in the unreachable list.

----------
components: Interpreter Core
files: zleak.py
messages: 354020
nosy: nascheme, pitrou, tim.peters
priority: normal
severity: normal
stage: needs patch
status: open
title: finalizer resurrection in gc
type: behavior
versions: Python 3.9
Added file: https://bugs.python.org/file48644/zleak.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Sat Oct  5 13:44:59 2019
From: report at bugs.python.org (Ben Harper)
Date: Sat, 05 Oct 2019 17:44:59 +0000
Subject: [issue36356] Failure to build with address sanitizer
In-Reply-To: <1552967277.69.0.646647509224.issue36356@roundup.psfhosted.org>
Message-ID: <1570297499.08.0.992266548864.issue36356@roundup.psfhosted.org>


Change by Ben Harper <btharper1221 at gmail.com>:


----------
pull_requests: +16186
pull_request: https://github.com/python/cpython/pull/16598

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36356>
_______________________________________

From report at bugs.python.org  Sat Oct  5 14:28:18 2019
From: report at bugs.python.org (Eryk Sun)
Date: Sat, 05 Oct 2019 18:28:18 +0000
Subject: [issue38324] [Windows] test_locale and test__locale failures on
 Windows
In-Reply-To: <1569849277.36.0.00648751871696.issue38324@roundup.psfhosted.org>
Message-ID: <1570300098.52.0.314074342888.issue38324@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

Terry, the test_winconsoleio problem is issue 38325. Test cases with surrogate pairs that are known to fail in recent builds of Windows 10 have to be split out.

For the "ps_AF" locale failure that you noted, in my case with Windows 10 18362, I have to first modify the tests in Lib/test/test__locale.py to set LC_CTYPE before setting LC_NUMERIC. Otherwise the lconv result in C has the wrong encoding, and PyUnicode_DecodeLocale fails. 

After making this change, I can reproduce the noted failure. The "ps_AF" (Pashto, Afghanistan) case will have to be skipped in Windows because the system NLS data does not agree with the assumed Arabic decimal and thousands separator, U+066B and U+066C, but instead uses "," and ".". This can be verified directly via WINAPI GetLocaleInfoEx:

    >>> n = kernel32.GetLocaleInfoEx('ps-AF', LOCALE_SSCRIPTS, buf, len(buf))
    >>> buf.value
    'Arab;'
    >>> n = kernel32.GetLocaleInfoEx('ps-AF', LOCALE_SDECIMAL, buf, len(buf))
    >>> buf.value
    ','
    >>> n = kernel32.GetLocaleInfoEx('ps-AF', LOCALE_STHOUSAND, buf, len(buf))
    >>> buf.value
    '.'

In case this was a quirk in the NLS data for languages that use a Perso-Arabic script, such as Pashto, I also checked Saudi Arabia ("ar-SA"), which uses a standard Arabic script, but the result was the same.

----------
nosy: +eryksun

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38324>
_______________________________________

From report at bugs.python.org  Sat Oct  5 15:34:39 2019
From: report at bugs.python.org (Antonio Gutierrez)
Date: Sat, 05 Oct 2019 19:34:39 +0000
Subject: [issue36161] Use thread-safe functions instead of unsafe ones (crypt, 
 ttyname)
In-Reply-To: <1551475826.18.0.295115684796.issue36161@roundup.psfhosted.org>
Message-ID: <1570304079.57.0.733360072364.issue36161@roundup.psfhosted.org>


Change by Antonio Gutierrez <chibby0ne at gmail.com>:


----------
pull_requests: +16187
pull_request: https://github.com/python/cpython/pull/16599

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36161>
_______________________________________

From report at bugs.python.org  Sat Oct  5 17:25:52 2019
From: report at bugs.python.org (Ned Deily)
Date: Sat, 05 Oct 2019 21:25:52 +0000
Subject: [issue38295] test_relative_path of test_py_compile fails on macOS
 10.15 Catalina
In-Reply-To: <1569605043.98.0.657218273343.issue38295@roundup.psfhosted.org>
Message-ID: <1570310752.59.0.230523880811.issue38295@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Also the similar single test in 2.7.x fails on 10.15 (pre-release):

======================================================================
ERROR: test_relative_path (test.test_py_compile.PyCompileTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/test/test_py_compile.py", line 45, in test_relative_path
    os.path.relpath(self.pyc_path))
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/py_compile.py", line 123, in compile
    with open(cfile, 'wb') as fc:
IOError: [Errno 2] No such file or directory: '../../../../../../../var/folders/n6/q3475zjd38bc3q197d77wjc80000gn/T/tmpLPxkJN/_test.pyc'

----------
title: macOS Catalina test failures -> test_relative_path of test_py_compile fails on macOS 10.15 Catalina
versions: +Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38295>
_______________________________________

From report at bugs.python.org  Sat Oct  5 18:12:20 2019
From: report at bugs.python.org (Big Stone)
Date: Sat, 05 Oct 2019 22:12:20 +0000
Subject: [issue38380] Update SQLite to 3.30 in Windows and macOS installer
 builds
Message-ID: <1570313540.41.0.0224198940573.issue38380@roundup.psfhosted.org>


New submission from Big Stone <stonebig34 at gmail.com>:

there is a security fix in sqlite-3.30

https://nvd.nist.gov/vuln/detail/CVE-2019-16168#VulnChangeHistorySection

https://www.sqlite.org/releaselog/3_30_0.html

----------
messages: 354023
nosy: Big Stone
priority: normal
severity: normal
status: open
title: Update SQLite to 3.30 in Windows and macOS installer builds

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38380>
_______________________________________

From report at bugs.python.org  Sat Oct  5 18:23:55 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 05 Oct 2019 22:23:55 +0000
Subject: [issue38381] Possible wordcode optimization for STORE/LOAD pairs
Message-ID: <1570314235.55.0.575306260981.issue38381@roundup.psfhosted.org>


New submission from Raymond Hettinger <raymond.hettinger at gmail.com>:

In the show code below, the STORE_FAST x is FOLLOWED by LOAD_FAST x.   This is a common word code pairing.  Perhaps a new combined opcode would help:

        case TARGET(LOAD_AND_STORE_FAST): {
            PyObject *value = GETLOCAL(oparg);
            if (value == NULL) {
                format_exc_check_arg(tstate, PyExc_UnboundLocalError,
                                     UNBOUNDLOCAL_ERROR_MSG,
                                     PyTuple_GetItem(co->co_varnames, oparg));
                goto error;
            }
            Py_INCREF(value);
            SETLOCAL(oparg, value);
            FAST_DISPATCH();
        }

The combined opcode saves one one trip around the eval-loop and it saves
unnecessary stack manipulations (a PUSH() immediately followed by a POP()).

The code generation would likely need to be a compiler or AST step because it crosses basic block boundaries.  Care would need to be taken to not adversely affect tracing the code in a debugger.

Note in the following code, the "x" is never used after the STORE/LOAD pair.  In theory, the two opcodes could be dropped entirely; however, would affect a call to "locals()".

-------- Code disassembly ------

>>> def f(s):
	for x in g:
		yield x**2

		
>>> dis(f)
  2           0 LOAD_GLOBAL              0 (g)
              2 GET_ITER
        >>    4 FOR_ITER                14 (to 20)
              6 STORE_FAST               1 (x)

  3           8 LOAD_FAST                1 (x)
             10 LOAD_CONST               1 (2)
             12 BINARY_POWER
             14 YIELD_VALUE
             16 POP_TOP
             18 JUMP_ABSOLUTE            4
        >>   20 LOAD_CONST               0 (None)
             22 RETURN_VALUE

----------
components: Interpreter Core
messages: 354024
nosy: rhettinger
priority: normal
severity: normal
status: open
title: Possible wordcode optimization for STORE/LOAD pairs
type: performance
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38381>
_______________________________________

From report at bugs.python.org  Sat Oct  5 18:35:11 2019
From: report at bugs.python.org (Ned Deily)
Date: Sat, 05 Oct 2019 22:35:11 +0000
Subject: [issue38380] Update SQLite to 3.30 in Windows and macOS installer
 builds
In-Reply-To: <1570313540.41.0.0224198940573.issue38380@roundup.psfhosted.org>
Message-ID: <1570314911.9.0.370346092261.issue38380@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

I verified it is exploitable via the sqlite3 module by adapting the test case from the SQLite ticket (https://www.sqlite.org/src/info/e4598ecbdd18bd82).  But since it requires the exploiter to be able to specify raw SQL statements, it doesn't sound like it needs to be treated as a Python security issue.  We should plan to to update to the latest SQLite but it doesn't need to be a release blocker.

----------
components: +Build, Windows, macOS
nosy: +ned.deily, paul.moore, ronaldoussoren, steve.dower, tim.golden, zach.ware
stage:  -> needs patch
versions: +Python 2.7, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38380>
_______________________________________

From report at bugs.python.org  Sat Oct  5 18:51:55 2019
From: report at bugs.python.org (Martijn Pieters)
Date: Sat, 05 Oct 2019 22:51:55 +0000
Subject: [issue38364] inspect.iscoroutinefunction / isgeneratorfunction /
 isasyncgenfunction can't handle partialmethod objects
In-Reply-To: <1570109324.07.0.792957059658.issue38364@roundup.psfhosted.org>
Message-ID: <1570315915.9.0.744620287446.issue38364@roundup.psfhosted.org>


Change by Martijn Pieters <mj at python.org>:


----------
keywords: +patch
pull_requests: +16188
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16600

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38364>
_______________________________________

From report at bugs.python.org  Sat Oct  5 19:59:00 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 05 Oct 2019 23:59:00 +0000
Subject: [issue18578] Rename and document test.bytecode_helper as
 test.support.bytecode_helper
In-Reply-To: <1375014946.89.0.0130176350727.issue18578@psf.upfronthosting.co.za>
Message-ID: <1570319940.44.0.425703665577.issue18578@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Just noting for the record that the reason a new warning wasn't needed here is because there is already a general "No compatibility guarantees" warning for the entire test package: https://docs.python.org/3/library/test.html

Thanks for getting this resolved!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue18578>
_______________________________________

From report at bugs.python.org  Sat Oct  5 20:07:28 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 06 Oct 2019 00:07:28 +0000
Subject: [issue22257] PEP 432 (PEP 587): Redesign the interpreter startup
 sequence
In-Reply-To: <1408789351.84.0.0171822343712.issue22257@psf.upfronthosting.co.za>
Message-ID: <1570320448.6.0.120486908371.issue22257@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Agreed. I've also added PEP 587 to the issue title to make the connection to that PEP more obvious.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
title: PEP 432: Redesign the interpreter startup sequence -> PEP 432 (PEP 587): Redesign the interpreter startup sequence

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22257>
_______________________________________

From report at bugs.python.org  Sat Oct  5 21:46:18 2019
From: report at bugs.python.org (Warren Weckesser)
Date: Sun, 06 Oct 2019 01:46:18 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
Message-ID: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>


New submission from Warren Weckesser <warren.weckesser at gmail.com>:

The function statistics.harmonic_mean is supposed to raise a StatisticsError if any element in the input is negative.  It fails to do so if the negative element is preceded by a zero.  When there is a zero before the negative element, the function returns 0:

>>> from statistics import harmonic_mean
>>> harmonic_mean([0, -1, 3])
0

If the zero occurs after the negative value, the StatisticsError exception is correctly raised:

>>> harmonic_mean([-1, 0, 3])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/warren/repos/git/forks/cpython/Lib/statistics.py", line 406, in harmonic_mean
    T, total, count = _sum(1/x for x in _fail_neg(data, errmsg))
  File "/Users/warren/repos/git/forks/cpython/Lib/statistics.py", line 164, in _sum
    for typ, values in groupby(data, type):
  File "/Users/warren/repos/git/forks/cpython/Lib/statistics.py", line 406, in <genexpr>
    T, total, count = _sum(1/x for x in _fail_neg(data, errmsg))
  File "/Users/warren/repos/git/forks/cpython/Lib/statistics.py", line 289, in _fail_neg
    raise StatisticsError(errmsg)
statistics.StatisticsError: harmonic mean does not support negative values
>>> 

The problem is in this code in the function harmonic_mean:

    try:
        T, total, count = _sum(1/x for x in _fail_neg(data, errmsg))
    except ZeroDivisionError:
        return 0

When the zero occurs before the negative value, the ZeroDivisionError is raised before the negative value has been seen by the generator _fail_neg, and the function returns 0.

----------
components: Library (Lib)
messages: 354028
nosy: WarrenWeckesser
priority: normal
severity: normal
status: open
title: statistics.harmonic_mean fails to raise error with negative input that follows a 0
type: behavior
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Sat Oct  5 22:20:15 2019
From: report at bugs.python.org (Caleb Hattingh)
Date: Sun, 06 Oct 2019 02:20:15 +0000
Subject: [issue37736] asyncio.wait_for is still confusing
In-Reply-To: <1564651501.71.0.316479365632.issue37736@roundup.psfhosted.org>
Message-ID: <1570328415.07.0.111293787972.issue37736@roundup.psfhosted.org>


Caleb Hattingh <caleb.hattingh at gmail.com> added the comment:

> asyncio.wait_for is still confusing

Perhaps the confusion can be fixed with improvements to the docs? To me, these specific docs seem pretty clear now, but I might not be a good judge of that.

> However, we still have the case where a misbehaving Task can cause wait_for to hang indefinitely.

The key word here is "misbehaving". Cooperative concurrency does require cooperation. There are many ways in which coroutines can misbehave, the popular one being calling blocking functions when they shouldn't. I would be very uncomfortable with my coroutine being killable (e.g. by wait_for) by some other means besides CancelledError (which I can intercept and manage cleanup).  

The contract is: if my coroutine has a CancelledError raised, I take that to mean that I need to clean up whatever resources need cleanup, in a timely manner and then exit. If my coro refuses to exit, it is my coroutine that is wrong, not wait_for being unable to kill the coroutine.

I definitely agree with Yury that the previous behaviour, the one where wait_for could raise TimeoutError *before* the inner coro has exited, was buggy and needed to be fixed.

----------
nosy: +cjrh

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37736>
_______________________________________

From report at bugs.python.org  Sat Oct  5 22:40:20 2019
From: report at bugs.python.org (Warren Weckesser)
Date: Sun, 06 Oct 2019 02:40:20 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570329620.36.0.696849357019.issue38382@roundup.psfhosted.org>


Warren Weckesser <warren.weckesser at gmail.com> added the comment:

The premature return on ZeroDivisionError also causes an inconsistency in how types are handled.  For example,

>>> harmonic_mean([1, 0, "foo"])
0

We get an error as expected if "foo" occurs before 0:

>>> harmonic_mean([1, "foo", 0])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/warren/repos/git/forks/cpython/Lib/statistics.py", line 406, in harmonic_mean
    T, total, count = _sum(1/x for x in _fail_neg(data, errmsg))
  File "/Users/warren/repos/git/forks/cpython/Lib/statistics.py", line 166, in _sum
    for n,d in map(_exact_ratio, values):
  File "/Users/warren/repos/git/forks/cpython/Lib/statistics.py", line 406, in <genexpr>
    T, total, count = _sum(1/x for x in _fail_neg(data, errmsg))
  File "/Users/warren/repos/git/forks/cpython/Lib/statistics.py", line 288, in _fail_neg
    if x < 0:
TypeError: '<' not supported between instances of 'str' and 'int'

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Sat Oct  5 23:12:28 2019
From: report at bugs.python.org (Warren Weckesser)
Date: Sun, 06 Oct 2019 03:12:28 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570331548.74.0.550779792525.issue38382@roundup.psfhosted.org>


Change by Warren Weckesser <warren.weckesser at gmail.com>:


----------
keywords: +patch
pull_requests: +16189
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16601

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Sun Oct  6 02:21:50 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sun, 06 Oct 2019 06:21:50 +0000
Subject: [issue38210] Intersection of dict view with iterator returns empty set
In-Reply-To: <1568790606.98.0.898790756289.issue38210@roundup.psfhosted.org>
Message-ID: <1570342910.77.0.554401568996.issue38210@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
keywords: +patch
pull_requests: +16190
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16602

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38210>
_______________________________________

From report at bugs.python.org  Sun Oct  6 03:01:27 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 06 Oct 2019 07:01:27 +0000
Subject: [issue38381] Possible wordcode optimization for STORE/LOAD pairs
In-Reply-To: <1570314235.55.0.575306260981.issue38381@roundup.psfhosted.org>
Message-ID: <1570345287.28.0.647854050328.issue38381@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I thought about this. But STORE_FAST x is followed by LOAD_FAST x just by accident. If you change the expression (1+x**2 or f(x**2)) they no longer be neighbors. I am not sure this pattern is common enough. There are more common pairs.

Also, note that LOAD_FAST belong to the different line of code. It should be preserved for debugging purpose. Otherwise you could not set a breakpoint on the first line of the loop body.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38381>
_______________________________________

From report at bugs.python.org  Sun Oct  6 05:21:20 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sun, 06 Oct 2019 09:21:20 +0000
Subject: [issue38210] Intersection of dict view with iterator returns empty set
In-Reply-To: <1568790606.98.0.898790756289.issue38210@roundup.psfhosted.org>
Message-ID: <1570353680.74.0.232756040179.issue38210@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
nosy: +corona10

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38210>
_______________________________________

From report at bugs.python.org  Sun Oct  6 06:51:34 2019
From: report at bugs.python.org (hai shi)
Date: Sun, 06 Oct 2019 10:51:34 +0000
Subject: [issue38383] undefined behavior in tailmatch() of bytes_methods.c
Message-ID: <1570359094.2.0.728788628974.issue38383@roundup.psfhosted.org>


New submission from hai shi <shihai1991 at 126.com>:

`if (start + slen > len)` would cause undefined behavior?
such as: start=PY_SSIZE_T_MAX, slen=1

REFS:
[1] https://github.com/python/cpython/blob/master/Objects/bytes_methods.c#L746

----------
components: Interpreter Core
messages: 354032
nosy: shihai1991
priority: normal
severity: normal
status: open
title: undefined behavior in tailmatch() of bytes_methods.c
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38383>
_______________________________________

From report at bugs.python.org  Sun Oct  6 06:53:12 2019
From: report at bugs.python.org (hai shi)
Date: Sun, 06 Oct 2019 10:53:12 +0000
Subject: [issue38383] undefined behavior in tailmatch() of bytes_methods.c
In-Reply-To: <1570359094.2.0.728788628974.issue38383@roundup.psfhosted.org>
Message-ID: <1570359192.67.0.0671974819738.issue38383@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
keywords: +patch
pull_requests: +16191
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16603

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38383>
_______________________________________

From report at bugs.python.org  Sun Oct  6 07:28:39 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 06 Oct 2019 11:28:39 +0000
Subject: [issue38210] Intersection of dict view with iterator returns empty set
In-Reply-To: <1568790606.98.0.898790756289.issue38210@roundup.psfhosted.org>
Message-ID: <1570361319.2.0.973613132755.issue38210@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset c38e725d17537b20ff090b1b5ec7db1820ff9b63 by Serhiy Storchaka (Dong-hee Na) in branch 'master':
bpo-38210: Fix intersection operation with dict view and iterator. (GH-16602)
https://github.com/python/cpython/commit/c38e725d17537b20ff090b1b5ec7db1820ff9b63


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38210>
_______________________________________

From report at bugs.python.org  Sun Oct  6 07:29:41 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 06 Oct 2019 11:29:41 +0000
Subject: [issue38210] Intersection of dict view with iterator returns empty set
In-Reply-To: <1568790606.98.0.898790756289.issue38210@roundup.psfhosted.org>
Message-ID: <1570361381.78.0.13113493602.issue38210@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Thank you Dong-hee for your fix!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38210>
_______________________________________

From report at bugs.python.org  Sun Oct  6 08:17:22 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 06 Oct 2019 12:17:22 +0000
Subject: [issue38383] undefined behavior in tailmatch() of bytes_methods.c
In-Reply-To: <1570359094.2.0.728788628974.issue38383@roundup.psfhosted.org>
Message-ID: <1570364242.07.0.073288765594.issue38383@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 24ddd9c2d6ab61cbce7e68d6de36d4df9bd2c3fb by Serhiy Storchaka (Hai Shi) in branch 'master':
bpo-38383: Fix possible integer overflow in startswith() of bytes and bytearray. (GH-16603)
https://github.com/python/cpython/commit/24ddd9c2d6ab61cbce7e68d6de36d4df9bd2c3fb


----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38383>
_______________________________________

From report at bugs.python.org  Sun Oct  6 08:18:51 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 06 Oct 2019 12:18:51 +0000
Subject: [issue38383] undefined behavior in tailmatch() of bytes_methods.c
In-Reply-To: <1570359094.2.0.728788628974.issue38383@roundup.psfhosted.org>
Message-ID: <1570364331.36.0.722681867902.issue38383@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16192
pull_request: https://github.com/python/cpython/pull/16604

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38383>
_______________________________________

From report at bugs.python.org  Sun Oct  6 08:18:58 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 06 Oct 2019 12:18:58 +0000
Subject: [issue38383] undefined behavior in tailmatch() of bytes_methods.c
In-Reply-To: <1570359094.2.0.728788628974.issue38383@roundup.psfhosted.org>
Message-ID: <1570364338.62.0.253727395805.issue38383@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16193
pull_request: https://github.com/python/cpython/pull/16605

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38383>
_______________________________________

From report at bugs.python.org  Sun Oct  6 08:20:04 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 06 Oct 2019 12:20:04 +0000
Subject: [issue38383] undefined behavior in tailmatch() of bytes_methods.c
In-Reply-To: <1570359094.2.0.728788628974.issue38383@roundup.psfhosted.org>
Message-ID: <1570364404.67.0.417306849365.issue38383@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38383>
_______________________________________

From report at bugs.python.org  Sun Oct  6 08:36:47 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 06 Oct 2019 12:36:47 +0000
Subject: [issue38383] undefined behavior in tailmatch() of bytes_methods.c
In-Reply-To: <1570359094.2.0.728788628974.issue38383@roundup.psfhosted.org>
Message-ID: <1570365407.65.0.127135680743.issue38383@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset b40442ba88fec5e64ab1802ce37df0afec59fa53 by Miss Islington (bot) in branch '3.7':
bpo-38383: Fix possible integer overflow in startswith() of bytes and bytearray. (GH-16603)
https://github.com/python/cpython/commit/b40442ba88fec5e64ab1802ce37df0afec59fa53


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38383>
_______________________________________

From report at bugs.python.org  Sun Oct  6 08:37:22 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 06 Oct 2019 12:37:22 +0000
Subject: [issue38383] undefined behavior in tailmatch() of bytes_methods.c
In-Reply-To: <1570359094.2.0.728788628974.issue38383@roundup.psfhosted.org>
Message-ID: <1570365442.94.0.324120483073.issue38383@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset ce3c913909746aa1d782ed8bca5076a656422931 by Miss Islington (bot) in branch '3.8':
bpo-38383: Fix possible integer overflow in startswith() of bytes and bytearray. (GH-16603)
https://github.com/python/cpython/commit/ce3c913909746aa1d782ed8bca5076a656422931


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38383>
_______________________________________

From report at bugs.python.org  Sun Oct  6 09:39:09 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Sun, 06 Oct 2019 13:39:09 +0000
Subject: [issue38384] An assertion failure in test_pickle
Message-ID: <1570369149.47.0.841206648458.issue38384@roundup.psfhosted.org>


New submission from Zackery Spytz <zspytz at gmail.com>:

When running test_pickle, I sometimes see an assertion failure.

./python -m test test_pickle
0:00:00 load avg: 1.04 Run tests sequentially
0:00:00 load avg: 1.04 [1/1] test_pickle
python: Objects/typeobject.c:3151: _PyType_Lookup: Assertion `!PyErr_Occurred()' failed.
Fatal Python error: Aborted

Current thread 0x00007f8158632140 (most recent call first):
  File "/home/lubuntu2/cpython/Lib/test/pickletester.py", line 3400 in test_unpickling_buffering_readline
  File "/home/lubuntu2/cpython/Lib/unittest/case.py", line 617 in _callTestMethod
  File "/home/lubuntu2/cpython/Lib/unittest/case.py", line 663 in run
  File "/home/lubuntu2/cpython/Lib/unittest/case.py", line 725 in __call__
  File "/home/lubuntu2/cpython/Lib/unittest/suite.py", line 122 in run
  File "/home/lubuntu2/cpython/Lib/unittest/suite.py", line 84 in __call__
  File "/home/lubuntu2/cpython/Lib/unittest/suite.py", line 122 in run
  File "/home/lubuntu2/cpython/Lib/unittest/suite.py", line 84 in __call__
  File "/home/lubuntu2/cpython/Lib/test/support/testresult.py", line 162 in run
  File "/home/lubuntu2/cpython/Lib/test/support/__init__.py", line 2032 in _run_suite
  File "/home/lubuntu2/cpython/Lib/test/support/__init__.py", line 2128 in run_unittest
  File "/home/lubuntu2/cpython/Lib/test/test_pickle.py", line 525 in test_main
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/runtest.py", line 234 in _runtest_inner2
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/runtest.py", line 270 in _runtest_inner
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/runtest.py", line 153 in _runtest
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/runtest.py", line 193 in runtest
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/main.py", line 417 in run_tests_sequential
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/main.py", line 515 in run_tests
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/main.py", line 687 in _main
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/main.py", line 634 in main
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/main.py", line 712 in main
  File "/home/lubuntu2/cpython/Lib/test/__main__.py", line 2 in <module>
  File "/home/lubuntu2/cpython/Lib/runpy.py", line 85 in _run_code
  File "/home/lubuntu2/cpython/Lib/runpy.py", line 192 in _run_module_as_main
Aborted (core dumped)


In _Unpickler_SetInputStream(), _PyObject_LookupAttrId() is called three times in a row without any error handling.
If an exception occurs during the first or second call, _PyObject_LookupAttrId() will be called with a live exception.

----------
components: Extension Modules
messages: 354038
nosy: ZackerySpytz
priority: normal
severity: normal
status: open
title: An assertion failure in test_pickle
type: crash
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38384>
_______________________________________

From report at bugs.python.org  Sun Oct  6 09:41:58 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Sun, 06 Oct 2019 13:41:58 +0000
Subject: [issue38384] An assertion failure in test_pickle
In-Reply-To: <1570369149.47.0.841206648458.issue38384@roundup.psfhosted.org>
Message-ID: <1570369318.59.0.34577548961.issue38384@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
keywords: +patch
pull_requests: +16194
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16606

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38384>
_______________________________________

From report at bugs.python.org  Sun Oct  6 11:39:36 2019
From: report at bugs.python.org (Mauricio Villegas)
Date: Sun, 06 Oct 2019 15:39:36 +0000
Subject: [issue35005] argparse should accept json and yaml argument types
In-Reply-To: <1539735338.04.0.788709270274.issue35005@psf.upfronthosting.co.za>
Message-ID: <1570376376.15.0.819437258286.issue35005@roundup.psfhosted.org>


Mauricio Villegas <mauricio_ville at yahoo.com> added the comment:

FYI there is a new python package that extends argparse with the enhancements proposed here and more.

https://pypi.org/project/jsonargparse/

----------
nosy: +mauvilsa

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35005>
_______________________________________

From report at bugs.python.org  Sun Oct  6 12:34:54 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 06 Oct 2019 16:34:54 +0000
Subject: [issue38384] An assertion failure in test_pickle
In-Reply-To: <1570369149.47.0.841206648458.issue38384@roundup.psfhosted.org>
Message-ID: <1570379694.61.0.390188065548.issue38384@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I do not understand how you got an assertion failure. Did you interrupt tests with Ctrl-C?

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38384>
_______________________________________

From report at bugs.python.org  Sun Oct  6 14:33:41 2019
From: report at bugs.python.org (Tim Peters)
Date: Sun, 06 Oct 2019 18:33:41 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570386821.26.0.936975116344.issue38379@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

Just noting that check_garbage() currently only determines which trash objects are now directly reachable from outside.  To be usable for the intended purpose, it would need to go on to compute which trash objects are reachable from those too.

Maybe a new function

static void
deduce_unreachable(PyGC_Head *base, PyGC_Head *unreachable)

that packaged the steps through move_unreachable().  The main function would use that on `young`, and check_garbage() on `unreachable` to find the _still_ unreachable objects.

I don't care about the expense.  Outside of zleak.py, the number of unreachable objects is usually small, so it's usually cheap to make another pass over just them.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Sun Oct  6 14:33:52 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 06 Oct 2019 18:33:52 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570386832.8.0.6083295823.issue38382@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee:  -> rhettinger
nosy: +rhettinger, steven.daprano
versions: +Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Sun Oct  6 15:06:06 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 06 Oct 2019 19:06:06 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570388766.52.0.229148224466.issue38382@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Normally early-out behaviors are allowed to skip any checks for subsequent inputs (for example, the any() and all() builtins stop consuming inputs one a final value is found).

However, that reasoning might not apply to a zero input for harmonic_mean().  Technically, the definition of harmonic mean doesn't allow for a zero input value at all (accordingly, MS Excel gives an error for a zero input).  Presumably, the reason that Python's harmonic_mean() returns zero is so that the function degrades gracefully as one of the inputs gets closer to zero.

Options at this point:

* Just document that there is an early-out for zero.

* Stick with the strategy of treating zero as if it were just a very, very small positive input.  The would imply that all of the inputs should be considered and that TypeErrors or StatisticErrors should be raised for later data points (though I'm unclear what this world view implies when the inputs have both a zero and a positive infinity).

* Treat a zero input as an error.  This matches the usual specification of harmonic mean being defined only for non-negative real inputs.

----------
nosy: +mark.dickinson, tim.peters

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Sun Oct  6 15:10:16 2019
From: report at bugs.python.org (Eric O. LEBIGOT)
Date: Sun, 06 Oct 2019 19:10:16 +0000
Subject: [issue38385] statistics: incorrect documentation
Message-ID: <1570389016.13.0.165369947537.issue38385@roundup.psfhosted.org>


New submission from Eric O. LEBIGOT <eric.lebigot at normalesup.org>:

The documentation for the statistics package indicates that many of its functions (like median()) accept iterators. They seem to actually accept something more convenient, namely iterables.

Thus, iterator could probably be  usefully replaced by iterable on many of the functions (when applicable, which I would expect is everywhere).

----------
assignee: docs at python
components: Documentation
messages: 354043
nosy: docs at python, lebigot
priority: normal
severity: normal
status: open
title: statistics: incorrect documentation
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38385>
_______________________________________

From report at bugs.python.org  Sun Oct  6 15:20:19 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 06 Oct 2019 19:20:19 +0000
Subject: [issue38385] statistics: incorrect documentation
In-Reply-To: <1570389016.13.0.165369947537.issue38385@roundup.psfhosted.org>
Message-ID: <1570389619.13.0.628082346797.issue38385@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

This is a reasonable suggestion (all iterators are iterable, but not all iterables are iterators).  I'll work on it shortly (in conjunction with some other minor doc fixups).

----------
assignee: docs at python -> rhettinger
nosy: +rhettinger, steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38385>
_______________________________________

From report at bugs.python.org  Sun Oct  6 15:37:20 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 06 Oct 2019 19:37:20 +0000
Subject: [issue38210] Intersection of dict view with iterator returns empty set
In-Reply-To: <1568790606.98.0.898790756289.issue38210@roundup.psfhosted.org>
Message-ID: <1570390640.05.0.0195993924988.issue38210@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Please add a test for this regression.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38210>
_______________________________________

From report at bugs.python.org  Sun Oct  6 15:49:27 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sun, 06 Oct 2019 19:49:27 +0000
Subject: [issue21360] mailbox.Maildir should ignore files named with a leading
 dot
In-Reply-To: <1398550003.67.0.360972625113.issue21360@psf.upfronthosting.co.za>
Message-ID: <1570391367.47.0.688945700593.issue21360@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

David: How do you propose we move forward on this? 

Should we provide a switch to keep the original behaviour (which is off by default) so if there is someone depending on this bug, they could still continue to do it with relatively small change?

It is a change of behaviour, so probably isn't going to be back ported if it gets merged in 3.9 window.

----------
nosy: +maxking

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21360>
_______________________________________

From report at bugs.python.org  Sun Oct  6 15:51:25 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 06 Oct 2019 19:51:25 +0000
Subject: [issue38210] Intersection of dict view with iterator returns empty set
In-Reply-To: <1568790606.98.0.898790756289.issue38210@roundup.psfhosted.org>
Message-ID: <1570391485.77.0.963362726575.issue38210@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

It was added. Do you mean any special?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38210>
_______________________________________

From report at bugs.python.org  Sun Oct  6 16:54:47 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 06 Oct 2019 20:54:47 +0000
Subject: [issue35005] argparse should accept json and yaml argument types
In-Reply-To: <1539735338.04.0.788709270274.issue35005@psf.upfronthosting.co.za>
Message-ID: <1570395287.57.0.199354236021.issue35005@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I am going to decline this feature request on the principle of keeping our modules loosely coupled and orthogonal to one another.  

As paul.j3 pointed out, the "type" option seems to work best with simple conversions like "int".  As pointed-out by another respondent, FileType hasn't aged well and it may have been a mistake to include it all.  Likewise other converters like DateTime have been previously discussed and rejected.

There is a gray area between where argument parsing stops and application logic begins.   Since this is a standard library module, we should draw the line at simple converters/validators like "int", leaving anything more complex for downstream logic.  That will afford users greater flexibility and control than supported by the add_argument() API which intentionally only handles common cases.

[Braden Groom]
> I agree with Paul. This is probably simple enough for applications
> to implement. It also doesn't make sense to add either of these
> if the precedent was set by rejecting DateTime previously.

I concur as well.

[Mauricio Villegas]
> FYI there is a new python package that extends argparse 
> with the enhancements proposed here and more.

Thank you for the link. It will likely prove to be a valuable resource for people finding this issue in the future.  The referenced project shows the value of external projects being able to go in directions that are well beyond the scope of our standard library module: "Not exclusively intended for parsing command line arguments. The main focus is parsing yaml or jsonnet configuration files and not necessarily from a command line tool."

----------
assignee: bob.ippolito -> rhettinger
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35005>
_______________________________________

From report at bugs.python.org  Sun Oct  6 17:22:36 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 06 Oct 2019 21:22:36 +0000
Subject: [issue14364] Argparse incorrectly handles '--' as argument to option
In-Reply-To: <1332080953.55.0.495639573781.issue14364@psf.upfronthosting.co.za>
Message-ID: <1570396956.36.0.159045593867.issue14364@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Paul and David, is the current PR complete in your opinion?  Are there known cases where the PR would break existing, working code?

Also there needs to be doc entry that is clear on both new and old strategy for distinguishing options from arguments when a dash or dashdash is present.  The PR's Misc/NEWS entry, "Fix behavior of argparse when '--' as argument to option", is insufficient.

----------
assignee:  -> rhettinger
versions: +Python 3.8, Python 3.9 -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue14364>
_______________________________________

From report at bugs.python.org  Sun Oct  6 17:31:16 2019
From: report at bugs.python.org (Warren Weckesser)
Date: Sun, 06 Oct 2019 21:31:16 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570397476.34.0.15631730776.issue38382@roundup.psfhosted.org>


Warren Weckesser <warren.weckesser at gmail.com> added the comment:

I find it hard to accept the first option.  It seems to let a detail of the current implementation take precedence over API design.  I don't see why we would want an API in which harmonic_mean([1, 0, -1]) returns 0 but harmonic_mean([-1, 0, 1]) raises an error.  The harmonic mean should be invariant to permutations of the input (well, at least to within normal floating point precision when the input is floating point).  I wouldn't expect such a radical change in behavior based on how I ordered my input to harmonic_mean.

The second option appears to be the API that was intended when the function was implemented.  Returning 0 when one or more inputs are 0 (and the rest are positive numbers) is justified by taking a limit.  Just like we *define* the sinc function (https://en.wikipedia.org/wiki/Sinc_function) to be 1 at x=0 and sin(x)/x when x != 0 (because the limit as x approaches 0 of sin(x)/x is 1), we can define the value of the harmonic mean with zeros in the input as the limiting value as one (or more) positive values goes to 0.  That limit is 0.  (Also note that, in the case where just one input is 0, the expression for the harmonic mean can be manipulated into a form that gives 0 without requiring a limit. E.g. for three values, 1/(1/x0 + 1/x1 + 1/x2) = x0*x1*x2/(x1*x2 + x0*x2 + x0*x1).  If just one of those values is 0, the denominator is nonzero, so the result is simply 0.)

There is a nice analogy from electrical circuit theory.  Given, say, three resistances R1, R2 and R3 wired in parallel, the total resistance R is

   R = 1/(1/R1 + 1/R2 + 1/R3) = harmonic_mean([R1, R2, R3])/3

(https://en.wikipedia.org/wiki/Series_and_parallel_circuits#Resistance_units_2). Intuitively, we know that if any of those resistances is 0 (i.e. there is a short circuit), the total resistance is also 0.

The resistance analogy also gives the correct interpretation for the case where the input includes both 0 and +inf.  An infinite resistance is an open circuit (i.e. no connection), so putting that in parallel with a short circuit still results in a total resistance of 0.

The third option, in which any zero in the input is treated as an error, is a change in behavior. Given the justification for returning 0, and given that currently a call such as harmonic_mean([1, 0, 2]) *does* return 0, making that an error seems like an undesirable change.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Sun Oct  6 18:29:52 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 06 Oct 2019 22:29:52 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570400992.58.0.993041590681.issue38382@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

The resistor example is persuasive :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Sun Oct  6 19:03:41 2019
From: report at bugs.python.org (yangzongwu)
Date: Sun, 06 Oct 2019 23:03:41 +0000
Subject: [issue38386] ModuleNotFoundError: No module named '_ctypes'
Message-ID: <1570403021.12.0.499983378492.issue38386@roundup.psfhosted.org>


New submission from yangzongwu <yangzong5 at gmail.com>:

I have try the following, but it is no useful
sudo apt install libffi-dev
 
but when i import _ctypes under python,it is OK
yzw at yzw-virtual-machine:~/Desktop/Test$ python3
Python 3.6.8 (default, Aug 20 2019, 17:12:48) 
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import _ctypes
>>>


logs:
yzw at yzw-virtual-machine:~/Desktop/Test$ buildozer android clean

# Ensure build layout
No buildozer.spec found in the current directory. Abandon.
yzw at yzw-virtual-machine:~/Desktop/Test$ 
yzw at yzw-virtual-machine:~/Desktop/Test$ buildozer android clean
# Ensure build layout
No buildozer.spec found in the current directory. Abandon.
yzw at yzw-virtual-machine:~/Desktop/Test$ buildozer init
File buildozer.spec created, ready to customize!
yzw at yzw-virtual-machine:~/Desktop/Test$ buildozer -v android debug
# Check configuration tokens
# Ensure build layout
# Create directory /home/yzw/Desktop/Test/bin
# Check configuration tokens
# Preparing build
# Check requirements for android
# Run 'dpkg --version'
# Cwd None
Debian 'dpkg' package management program version 1.19.0.5 (amd64).
This is free software; see the GNU General Public License version 2 or
later for copying conditions. There is NO warranty.
# Search for Git (git)
#  -> found at /usr/bin/git
# Search for Cython (cython)
#  -> found at /home/yzw/.local/bin/cython
# Search for Java compiler (javac)
#  -> found at /usr/lib/jvm/java-8-openjdk-amd64/bin/javac
# Search for Java keytool (keytool)
#  -> found at /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/keytool
# Install platform
# Run '/usr/bin/python3 -m pip install -q --user \'appdirs\' \'colorama>=0.3.3\' \'jinja2\' \'six\' \'enum34; python_version<"3.4"\' \'sh>=1.10; sys_platform!="nt"\' \'pep517\' \'pytoml\' \'virtualenv\''
# Cwd None
# Apache ANT found at /home/yzw/.buildozer/android/platform/apache-ant-1.9.4
# Android SDK found at /home/yzw/.buildozer/android/platform/android-sdk
# Android NDK found at /home/yzw/.buildozer/android/platform/android-ndk-r17c
# Check application requirements
# Check garden requirements
# Compile platform
# Run '/usr/bin/python3 -m pythonforandroid.toolchain create --dist_name=myapp --bootstrap=sdl2 --requirements=python3,kivy --arch armeabi-v7a --copy-libs --color=always --storage-dir="/home/yzw/Desktop/Test/.buildozer/android/platform/build" --ndk-api=21'
# Cwd /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Will compile for the following archs: armeabi-v7a
[INFO]:    Found Android API target in $ANDROIDAPI: 27
[INFO]:    Available Android APIs are (27)
[INFO]:    Requested API target 27 is available, continuing.
[INFO]:    Found NDK dir in $ANDROIDNDK: /home/yzw/.buildozer/android/platform/android-ndk-r17c
[INFO]:    Found NDK version 17c
[INFO]:    Getting NDK API version (i.e. minimum supported API) from user argument
[INFO]:    Found virtualenv at /home/yzw/.local/bin/virtualenv
[INFO]:    ccache is missing, the build will not be optimized in the future.
[INFO]:    Found the following toolchain versions: ['4.9']
[INFO]:    Picking the latest gcc toolchain, here 4.9
[INFO]:    No existing dists meet the given requirements!
[INFO]:    No dist exists that meets your requirements, so one will be built.
[INFO]:    Found a single valid recipe set: ['hostpython3', 'libffi', 'openssl', 'sdl2_image', 'sdl2_mixer', 'sdl2_ttf', 'sqlite3', 'python3', 'sdl2', 'setuptools', 'six', 'pyjnius', 'android', 'kivy']
[INFO]:    The selected bootstrap is sdl2
[INFO]:    # Creating dist with sdl2 bootstrap
[INFO]:    Dist will have name myapp and requirements (python3, kivy)
[INFO]:    Dist contains the following requirements as recipes: ['hostpython3', 'libffi', 'openssl', 'sdl2_image', 'sdl2_mixer', 'sdl2_ttf', 'sqlite3', 'python3', 'sdl2', 'setuptools', 'six', 'pyjnius', 'android', 'kivy']
[INFO]:    Dist will also contain modules () installed from pip
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/bootstrap_builds/sdl2-python3
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Recipe build order is ['hostpython3', 'libffi', 'openssl', 'sdl2_image', 'sdl2_mixer', 'sdl2_ttf', 'sqlite3', 'python3', 'sdl2', 'setuptools', 'six', 'pyjnius', 'android', 'kivy']
[INFO]:    # Downloading recipes 
[INFO]:    Downloading hostpython3
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Te...(and 57 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/hostpython3
[INFO]:    -> running basename https://www.python.or...(and 35 more)
[INFO]:    hostpython3 download already cached, skipping                      
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading libffi
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Te...(and 52 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/libffi
[INFO]:    -> running basename https://github.com/li...(and 33 more)
[INFO]:    libffi download already cached, skipping                           
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading openssl
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Te...(and 53 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/openssl
[INFO]:    -> running basename https://www.openssl.o...(and 30 more)
[INFO]:    openssl download already cached, skipping                          
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading sdl2_image
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Te...(and 56 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/sdl2_image
[INFO]:    -> running basename https://www.libsdl.o...(and 53 more)
[INFO]:    sdl2_image download already cached, skipping                       
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading sdl2_mixer
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Te...(and 56 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/sdl2_mixer
[INFO]:    -> running basename https://www.libsdl.o...(and 53 more)
[INFO]:    sdl2_mixer download already cached, skipping                       
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading sdl2_ttf
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Te...(and 54 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/sdl2_ttf
[INFO]:    -> running basename https://www.libsdl.or...(and 49 more)
[INFO]:    sdl2_ttf download already cached, skipping                         
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading sqlite3
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Te...(and 53 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/sqlite3
[INFO]:    -> running basename https://www.sqlite.or...(and 38 more)
[INFO]:    sqlite3 download already cached, skipping                          
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading python3
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Te...(and 53 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/python3
[INFO]:    -> running basename https://www.python.or...(and 35 more)
[INFO]:    python3 download already cached, skipping                          
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading sdl2
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Tes...(and 49 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/sdl2
[INFO]:    -> running basename https://www.libsdl.or...(and 27 more)
[INFO]:    sdl2 download already cached, skipping                             
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading setuptools
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Te...(and 56 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/setuptools
[INFO]:    -> running basename https://pypi.python....(and 54 more)
[INFO]:    setuptools download already cached, skipping                       
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading six
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Tes...(and 48 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/six
[INFO]:    -> running basename https://pypi.python.o...(and 42 more)
[INFO]:    six download already cached, skipping                              
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading pyjnius
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Te...(and 53 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/pyjnius
[INFO]:    -> running basename https://github.com/ki...(and 30 more)
[INFO]:    pyjnius download already cached, skipping                          
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Downloading android
[INFO]:    Skipping android download as no URL is set
[INFO]:    Downloading kivy
[INFO]:    -> running mkdir -p /home/yzw/Desktop/Tes...(and 49 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/packages/kivy
[INFO]:    -> running basename https://github.com/ki...(and 26 more)
[INFO]:    kivy download already cached, skipping                             
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    # Building all recipes for arch armeabi-v7a
[INFO]:    # Unpacking recipes
[INFO]:    Unpacking hostpython3 for armeabi-v7a
[INFO]:    -> running basename https://www.python.or...(and 35 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/hostpython3/desktop
[INFO]:    hostpython3 is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking libffi for armeabi-v7a
[INFO]:    -> running basename https://github.com/li...(and 33 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/libffi/armeabi-v7a__ndk_target_21
[INFO]:    libffi is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking openssl for armeabi-v7a
[INFO]:    -> running basename https://www.openssl.o...(and 30 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/openssl/armeabi-v7a__ndk_target_21
[INFO]:    openssl is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking sdl2_image for armeabi-v7a
[INFO]:    -> running basename https://www.libsdl.o...(and 53 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/bootstrap_builds/sdl2-python3/jni
[INFO]:    sdl2_image is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking sdl2_mixer for armeabi-v7a
[INFO]:    -> running basename https://www.libsdl.o...(and 53 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/bootstrap_builds/sdl2-python3/jni
[INFO]:    sdl2_mixer is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking sdl2_ttf for armeabi-v7a
[INFO]:    -> running basename https://www.libsdl.or...(and 49 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/bootstrap_builds/sdl2-python3/jni
[INFO]:    sdl2_ttf is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking sqlite3 for armeabi-v7a
[INFO]:    -> running basename https://www.sqlite.or...(and 38 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/sqlite3/armeabi-v7a__ndk_target_21
[INFO]:    sqlite3 is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking python3 for armeabi-v7a
[INFO]:    -> running basename https://www.python.or...(and 35 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/python3-libffi-openssl-sqlite3/armeabi-v7a__ndk_target_21
[INFO]:    python3 is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking sdl2 for armeabi-v7a
[INFO]:    -> running basename https://www.libsdl.or...(and 27 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/bootstrap_builds/sdl2-python3/jni
[INFO]:    sdl2 is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking setuptools for armeabi-v7a
[INFO]:    -> running basename https://pypi.python....(and 54 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/setuptools-python3/armeabi-v7a__ndk_target_21
[INFO]:    setuptools is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking six for armeabi-v7a
[INFO]:    -> running basename https://pypi.python.o...(and 42 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/six-python3/armeabi-v7a__ndk_target_21
[INFO]:    six is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Unpacking pyjnius for armeabi-v7a
[INFO]:    -> running basename https://github.com/ki...(and 30 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/pyjnius-python3-sdl2/armeabi-v7a__ndk_target_21
[INFO]:    pyjnius is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    -> running rm -rf /home/yzw/Desktop/Test...(and 109 more)
[INFO]:    -> running cp -a /home/yzw/Desktop/Test/...(and 215 more)
[INFO]:    Unpacking kivy for armeabi-v7a
[INFO]:    -> running basename https://github.com/ki...(and 26 more)
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/kivy-python3/armeabi-v7a__ndk_target_21
[INFO]:    kivy is already unpacked, skipping
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    # Prebuilding recipes
[INFO]:    Prebuilding hostpython3 for armeabi-v7a
[INFO]:    hostpython3 has no prebuild_armeabi_v7a, skipping
[INFO]:    Prebuilding libffi for armeabi-v7a
[INFO]:    libffi has no prebuild_armeabi_v7a, skipping
[INFO]:    Applying patches for libffi[armeabi-v7a]
[INFO]:    libffi already patched, skipping
[INFO]:    Prebuilding openssl for armeabi-v7a
[INFO]:    openssl has no prebuild_armeabi_v7a, skipping
[INFO]:    Prebuilding sdl2_image for armeabi-v7a
[INFO]:    sdl2_image has no prebuild_armeabi_v7a, skipping
[INFO]:    Applying patches for sdl2_image[armeabi-v7a]
[INFO]:    sdl2_image already patched, skipping
[INFO]:    Prebuilding sdl2_mixer for armeabi-v7a
[INFO]:    sdl2_mixer has no prebuild_armeabi_v7a, skipping
[INFO]:    Applying patches for sdl2_mixer[armeabi-v7a]
[INFO]:    sdl2_mixer already patched, skipping
[INFO]:    Prebuilding sdl2_ttf for armeabi-v7a
[INFO]:    sdl2_ttf has no prebuild_armeabi_v7a, skipping
[INFO]:    Prebuilding sqlite3 for armeabi-v7a
[INFO]:    sqlite3 has no prebuild_armeabi_v7a, skipping
[INFO]:    Prebuilding python3 for armeabi-v7a
[INFO]:    python3 has no prebuild_armeabi_v7a, skipping
[INFO]:    Applying patches for python3[armeabi-v7a]
[INFO]:    python3 already patched, skipping
[INFO]:    Prebuilding sdl2 for armeabi-v7a
[INFO]:    sdl2 has no prebuild_armeabi_v7a, skipping
[INFO]:    Prebuilding setuptools for armeabi-v7a
[INFO]:    setuptools has no prebuild_armeabi_v7a, skipping
[INFO]:    Prebuilding six for armeabi-v7a
[INFO]:    six has no prebuild_armeabi_v7a, skipping
[INFO]:    Prebuilding pyjnius for armeabi-v7a
[INFO]:    pyjnius has no prebuild_armeabi_v7a, skipping
[INFO]:    Applying patches for pyjnius[armeabi-v7a]
[INFO]:    pyjnius already patched, skipping
[INFO]:    Prebuilding android for armeabi-v7a
[INFO]:    android has no prebuild_armeabi_v7a, skipping
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/android-python3-sdl2/armeabi-v7a__ndk_target_21/android
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Prebuilding kivy for armeabi-v7a
[INFO]:    kivy has no prebuild_armeabi_v7a, skipping
[INFO]:    # Building recipes
[INFO]:    Building hostpython3 for armeabi-v7a
[INFO]:    Skipping hostpython3 (3.7.1) build, as it has already been completed
[INFO]:    Building libffi for armeabi-v7a
[INFO]:    libffi said it is already built, skipping
[INFO]:    Building openssl for armeabi-v7a
[INFO]:    openssl said it is already built, skipping
[INFO]:    Building sdl2_image for armeabi-v7a
[INFO]:    Building sdl2_mixer for armeabi-v7a
[INFO]:    Building sdl2_ttf for armeabi-v7a
[INFO]:    Building sqlite3 for armeabi-v7a
[INFO]:    sqlite3 said it is already built, skipping
[INFO]:    Building python3 for armeabi-v7a
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/python3-libffi-openssl-sqlite3/armeabi-v7a__ndk_target_21/python3/android-build
[WARNING]: Doing some hacky stuff to link properly
[INFO]:    -> running cp /home/yzw/.buildozer/andro...(and 83 more)
[INFO]:    -> running cp /home/yzw/.buildozer/andro...(and 81 more)
[WARNING]: lld not found, linking without it. Consider installing lld if linker errors occur.
[INFO]:    Activating flags for sqlite3
[INFO]:    Activating flags for libffi
[INFO]:    Activating flags for openssl
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Building sdl2 for armeabi-v7a
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/bootstrap_builds/sdl2-python3/jni
[INFO]:    -> running ndk-build V=1
[INFO]:    <- directory context /home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android
[INFO]:    Building setuptools for armeabi-v7a
[INFO]:    setuptools apparently isn't already in site-packages
[INFO]:    Installing setuptools into site-packages
[INFO]:    -> directory context /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/setuptools-python3/armeabi-v7a__ndk_target_21/setuptools
[INFO]:    -> running python setup.py install -O2 -...(and 106 more)
Exception in thread background thread for pid 57350:                          
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/home/yzw/.local/lib/python3.6/site-packages/sh.py", line 1540, in wrap
    fn(*args, **kwargs)
  File "/home/yzw/.local/lib/python3.6/site-packages/sh.py", line 2459, in background_thread
    handle_exit_code(exit_code)
  File "/home/yzw/.local/lib/python3.6/site-packages/sh.py", line 2157, in fn
    return self.command.handle_command_exit_code(exit_code)
  File "/home/yzw/.local/lib/python3.6/site-packages/sh.py", line 815, in handle_command_exit_code
    raise exc
sh.ErrorReturnCode_1: 

  RAN: /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/hostpython3/desktop/hostpython3/native-build/python setup.py install -O2 --root=/home/yzw/Desktop/Test/.buildozer/android/platform/build/build/python-installs/myapp --install-lib=.

  STDOUT:
Traceback (most recent call last):
  File "setup.py", line 11, in <module>
    import setuptools
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/setuptools-python3/armeabi-v7a__ndk_target_21/setuptools/setuptools/__init__.py", line 20, in <module>
    from setuptools.dist import Distribution, Feature
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/setuptools-python3/armeabi-v7a__ndk_target_21/setuptools/setuptools/dist.py", line 36, in <module>
    from setuptools import windows_support
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/setuptools-python3/armeabi-v7a__ndk_target_21/setuptools/setuptools/windows_support.py", line 2, in <module>
    import ctypes
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/hostpython3/desktop/hostpython3/Lib/ctypes/__init__.py", line 7, in <module>
    from _ctypes import Union, Structure, Array
ModuleNotFoundError: No module named '_ctypes'


  STDERR:


Traceback (most recent call last):
  File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 1192, in <module>
    main()
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android/pythonforandroid/entrypoints.py", line 18, in main
    ToolchainCL()
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 668, in __init__
    getattr(self, args.subparser_name.replace('-', '_'))(args)
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 153, in wrapper_func
    build_dist_from_args(ctx, dist, args)
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 206, in build_dist_from_args
    args, "ignore_setup_py", False
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android/pythonforandroid/build.py", line 577, in build_recipes
    recipe.build_arch(arch)
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android/pythonforandroid/recipe.py", line 844, in build_arch
    self.install_python_package(arch)
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android/pythonforandroid/recipe.py", line 863, in install_python_package
    _env=hpenv, *self.setup_extra_args)
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/python-for-android/pythonforandroid/logger.py", line 180, in shprint
    for line in output:
  File "/home/yzw/.local/lib/python3.6/site-packages/sh.py", line 863, in next
    self.wait()
  File "/home/yzw/.local/lib/python3.6/site-packages/sh.py", line 792, in wait
    self.handle_command_exit_code(exit_code)
  File "/home/yzw/.local/lib/python3.6/site-packages/sh.py", line 815, in handle_command_exit_code
    raise exc
sh.ErrorReturnCode_1: 

  RAN: /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/hostpython3/desktop/hostpython3/native-build/python setup.py install -O2 --root=/home/yzw/Desktop/Test/.buildozer/android/platform/build/build/python-installs/myapp --install-lib=.

  STDOUT:
Traceback (most recent call last):
  File "setup.py", line 11, in <module>
    import setuptools
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/setuptools-python3/armeabi-v7a__ndk_target_21/setuptools/setuptools/__init__.py", line 20, in <module>
    from setuptools.dist import Distribution, Feature
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/setuptools-python3/armeabi-v7a__ndk_target_21/setuptools/setuptools/dist.py", line 36, in <module>
    from setuptools import windows_support
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/setuptools-python3/armeabi-v7a__ndk_target_21/setuptools/setuptools/windows_support.py", line 2, in <module>
    import ctypes
  File "/home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/hostpython3/desktop/hostpython3/Lib/ctypes/__init__.py", line 7, in <module>
    from _ctypes import Union, Structure, Array
ModuleNotFoundError: No module named '_ctypes'


  STDERR:

# Command failed: /usr/bin/python3 -m pythonforandroid.toolchain create --dist_name=myapp --bootstrap=sdl2 --requirements=python3,kivy --arch armeabi-v7a --copy-libs --color=always --storage-dir="/home/yzw/Desktop/Test/.buildozer/android/platform/build" --ndk-api=21
# 
# Buildozer failed to execute the last command
# The error might be hidden in the log above this error
# Please read the full log, and search for it before
# raising an issue with buildozer itself.
# In case of a bug report, please add a full log with log_level = 2

----------
components: Build
messages: 354052
nosy: yangzongwu
priority: normal
severity: normal
status: open
title: ModuleNotFoundError: No module named '_ctypes'
type: compile error
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38386>
_______________________________________

From report at bugs.python.org  Sun Oct  6 19:43:50 2019
From: report at bugs.python.org (Brad Solomon)
Date: Sun, 06 Oct 2019 23:43:50 +0000
Subject: [issue38387] Document PyDoc_STRVAR
Message-ID: <1570405430.86.0.169338229908.issue38387@roundup.psfhosted.org>


New submission from Brad Solomon <brad.solomon.1124 at gmail.com>:

The C-API reference would benefit from a short mention of PyDoc_STRVAR usage, since it is used so frequently within Modules/.

----------
assignee: docs at python
components: Documentation
messages: 354053
nosy: bsolomon1124, docs at python
priority: normal
pull_requests: 16195
severity: normal
status: open
title: Document PyDoc_STRVAR
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38387>
_______________________________________

From report at bugs.python.org  Sun Oct  6 19:51:13 2019
From: report at bugs.python.org (Dima Tisnek)
Date: Sun, 06 Oct 2019 23:51:13 +0000
Subject: [issue38388] Pickle protocol v 5 needs to be documented
Message-ID: <1570405873.92.0.178526679084.issue38388@roundup.psfhosted.org>


New submission from Dima Tisnek <dimaqq at gmail.com>:

Python 3.8 brings new pickle protocol, version 5.
It's not documented.

```
(venv) ? ~/m/proj> python
Python 3.7.4 (v3.7.4:e09359112e, Jul  8 2019, 14:54:52)
[Clang 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import pickle
>>> pickle.HIGHEST_PROTOCOL
4
>>> ^D
(venv) ? ~/m/proj> python3.8
Python 3.8.0rc1 (v3.8.0rc1:34214de6ab, Oct  1 2019, 12:56:49)
[Clang 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import pickle
>>> pickle.HIGHEST_PROTOCOL
5
>>> ^D
```

Yet there's no mention of "protocol version 5" at:

https://github.com/python/cpython/blob/master/Doc/library/pickle.rst
https://docs.python.org/3.9/library/pickle.html#data-stream-format
https://docs.python.org/3.8/library/pickle.html#data-stream-format

----------
assignee: docs at python
components: Documentation
messages: 354054
nosy: Dima.Tisnek, docs at python
priority: normal
severity: normal
status: open
title: Pickle protocol v 5 needs to be documented
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38388>
_______________________________________

From report at bugs.python.org  Sun Oct  6 19:56:22 2019
From: report at bugs.python.org (Ned Deily)
Date: Sun, 06 Oct 2019 23:56:22 +0000
Subject: [issue38386] ModuleNotFoundError: No module named '_ctypes'
In-Reply-To: <1570403021.12.0.499983378492.issue38386@roundup.psfhosted.org>
Message-ID: <1570406182.98.0.0980799601725.issue38386@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Sorry, you appear to be using a third-party packaging system that provides Python for Android platforms.  It's not something we provide or support.  You should ask your question of that project (python-for-android perhaps?) or on a forum like StackOverflow.  Good luck!

----------
nosy: +ned.deily
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38386>
_______________________________________

From report at bugs.python.org  Sun Oct  6 20:22:37 2019
From: report at bugs.python.org (Tim Peters)
Date: Mon, 07 Oct 2019 00:22:37 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570407757.53.0.0213078586289.issue38382@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

I don't have a problem with the current behavior (early out on zero, even if later arguments are senseless).  So:

> * Just document that there is an early-out for zero.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Sun Oct  6 20:26:31 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Mon, 07 Oct 2019 00:26:31 +0000
Subject: [issue38386] ModuleNotFoundError: No module named '_ctypes'
In-Reply-To: <1570403021.12.0.499983378492.issue38386@roundup.psfhosted.org>
Message-ID: <1570407991.7.0.262149170855.issue38386@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

I agree with Ned closing this issue, but just glancing at the logs, it looks to me like buildozer has shadowed your Python's ctypes with a broken ctypes in /home/yzw/Desktop/Test/.buildozer/android/platform/build/build/other_builds/hostpython3/desktop/hostpython3/Lib

If that's the case, this is definitely not a Python bug and should be reported to buildozer.

But one thing you should check first:

run ``which python3`` and make sure that the Python you are running (which has ctypes installed) is the same as the /usr/bin/python3 that buildozer is running.

Or run ``/usr/bin/python3 -c "import ctypes"`` and see what happens.

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38386>
_______________________________________

From report at bugs.python.org  Sun Oct  6 20:42:25 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 07 Oct 2019 00:42:25 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570408945.86.0.254324340399.issue38382@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

> I don't have a problem with the current behavior (early out on zero,
> even if later arguments are senseless).  So:
>
> > * Just document that there is an early-out for zero.

That make the most sense to me as well (even though the OP thinks otherwise).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Sun Oct  6 21:41:18 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Mon, 07 Oct 2019 01:41:18 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570412478.93.0.113956276178.issue38382@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Thanks Warren, the resistance example is excellent, would you like to write up a PR to add it to the docs?

In the original design, I prohibited negative numbers because that seems to be what everyone says you should do, but as far as I can tell it is mathematically well defined so long as the sum of positive values doesn't equal the sum of negative values. And in that case, we could return a NAN.

I don't know that there's any physical meaning to the harmonic mean of negative values (circuits with negative resistances?), but I'm almost tempted to make this "consenting adults" and remove the restriction altogether. That would simplify the implementation and remove any arguments about early-out on zero.

I acknowledge Warren's point about permutations of data, but that applies to anything with an early-out. I don't think that's quite persuasive enough to justify losing the early exit on zero.

Warren, if you feel really strongly about this, feel free to try to change my mind. But for now, I think that documenting that zero triggers an early-out is the right solution.

By the way, I've just noticed that harmonic_mean([INF, INF]) raises. Should it return INF instead?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Sun Oct  6 22:08:55 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 02:08:55 +0000
Subject: [issue26510] [argparse] Add required argument to add_subparsers
In-Reply-To: <1457445361.5.0.530669445668.issue26510@psf.upfronthosting.co.za>
Message-ID: <1570414135.04.0.998053447857.issue26510@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 9e71917e0290972f65711f75510078f799cf0b59 by Miss Islington (bot) (Adam J. Stewart) in branch 'master':
 bpo-26510: Add versionchanged for required arg of add_subparsers (GH-16588)
https://github.com/python/cpython/commit/9e71917e0290972f65711f75510078f799cf0b59


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26510>
_______________________________________

From report at bugs.python.org  Sun Oct  6 22:09:17 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 02:09:17 +0000
Subject: [issue26510] [argparse] Add required argument to add_subparsers
In-Reply-To: <1457445361.5.0.530669445668.issue26510@psf.upfronthosting.co.za>
Message-ID: <1570414157.83.0.390395565314.issue26510@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16196
pull_request: https://github.com/python/cpython/pull/16608

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26510>
_______________________________________

From report at bugs.python.org  Sun Oct  6 22:09:26 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 02:09:26 +0000
Subject: [issue26510] [argparse] Add required argument to add_subparsers
In-Reply-To: <1457445361.5.0.530669445668.issue26510@psf.upfronthosting.co.za>
Message-ID: <1570414166.52.0.242530319055.issue26510@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16197
pull_request: https://github.com/python/cpython/pull/16609

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26510>
_______________________________________

From report at bugs.python.org  Sun Oct  6 22:14:53 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 02:14:53 +0000
Subject: [issue26510] [argparse] Add required argument to add_subparsers
In-Reply-To: <1457445361.5.0.530669445668.issue26510@psf.upfronthosting.co.za>
Message-ID: <1570414493.26.0.92758606156.issue26510@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 50b8d579421e621130806e62d6108f5f83d4be7f by Miss Islington (bot) in branch '3.7':
bpo-26510: Add versionchanged for required arg of add_subparsers (GH-16588)
https://github.com/python/cpython/commit/50b8d579421e621130806e62d6108f5f83d4be7f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26510>
_______________________________________

From report at bugs.python.org  Sun Oct  6 22:15:47 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 02:15:47 +0000
Subject: [issue26510] [argparse] Add required argument to add_subparsers
In-Reply-To: <1457445361.5.0.530669445668.issue26510@psf.upfronthosting.co.za>
Message-ID: <1570414547.8.0.555380066044.issue26510@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset f19b4d7474973236e63d3d8260bfb8072acfff9d by Miss Islington (bot) in branch '3.8':
bpo-26510: Add versionchanged for required arg of add_subparsers (GH-16588)
https://github.com/python/cpython/commit/f19b4d7474973236e63d3d8260bfb8072acfff9d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26510>
_______________________________________

From report at bugs.python.org  Mon Oct  7 00:29:16 2019
From: report at bugs.python.org (Tamirys Pino)
Date: Mon, 07 Oct 2019 04:29:16 +0000
Subject: [issue38389] Bug on sorted with count key
Message-ID: <1570422556.48.0.0127805381731.issue38389@roundup.psfhosted.org>


New submission from Tamirys Pino <taamypino at gmail.com>:

>>> data=[2, 3, 2, 4, 5, 12, 2, 3, 3, 3, 12, 5]
>>> data
[2, 3, 2, 4, 5, 12, 2, 3, 3, 3, 12, 5]
>>> sorted(data)
[2, 2, 2, 3, 3, 3, 3, 4, 5, 5, 12, 12]
>>> sorted(data, key=data.count)
[4, 5, 12, 12, 5, 2, 2, 2, 3, 3, 3, 3]

[4, 5, 12, 12, 5, 2, 2, 2, 3, 3, 3, 3] should be [4, 5, 5, 12, 12, 2, 2, 2, 3, 3, 3, 3]

----------
messages: 354063
nosy: Tamirys Pino
priority: normal
severity: normal
status: open
title: Bug on sorted with count key
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38389>
_______________________________________

From report at bugs.python.org  Mon Oct  7 00:32:59 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Mon, 07 Oct 2019 04:32:59 +0000
Subject: [issue38389] Bug on sorted with count key
In-Reply-To: <1570422556.48.0.0127805381731.issue38389@roundup.psfhosted.org>
Message-ID: <1570422779.7.0.313568488573.issue38389@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:

5 and 12 both appear twice in the list, so as far as the key function is concerned, they're equal.

----------
nosy: +benjamin.peterson
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38389>
_______________________________________

From report at bugs.python.org  Mon Oct  7 03:25:36 2019
From: report at bugs.python.org (Warren Weckesser)
Date: Mon, 07 Oct 2019 07:25:36 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570433136.38.0.469668233183.issue38382@roundup.psfhosted.org>


Warren Weckesser <warren.weckesser at gmail.com> added the comment:

I really don't like the current inconsistent behavior.  I can't help but see it as a bug, and I am surprised that folks think it is OK that harmonic_mean([0, "foo"]) returns 0.  This is the *statistics* module, and the first line of https://docs.python.org/3/library/statistics.html says "This module provides functions for calculating mathematical statistics of numeric (Real-valued) data".  I understand the desire to maintain the performance benefit of the early exit, but I would rather disallow values that are zero than accept the nonsensical result of harmonic_mean([0, "foo"]) and the inconsistency between that and the result of harmonic_mean(["foo", 0]).  I spend most of my time working on numerical-ish code, so my world view might be different than that of y'all.

Here's a new proposal.  To continue to accept zero values, and disallow negative values consistently (as the function is documented to do), *and* preserve the early exit, I propose that the try/except statement in harmonic_mean in master be changed to

    try:
        T, total, count = _sum(1/x for x in _fail_neg(data, errmsg))
    except ZeroDivisionError:
        if any(x < 0 for x in data):
            raise StatisticsError(errmsg) from None
        return 0

The change adds just the two lines in the except block.  This doesn't change the "happy path" that is followed when all the values are strictly greater than 0.  The cost of the additional check for any negative values in the input only occurs in the (presumably uncommon) case where an input value is 0.  (This means, however, that any values before the first 0 are checked twice.)

> In the original design, I prohibited negative numbers because that seems to be what everyone says you should do, but as far as I can tell it is mathematically well defined so long as the sum of positive values doesn't equal the sum of negative values. And in that case, we could return a NAN.

Allowing negative values introduces some mathematical issues.  Most importantly, the limit of the harmonic mean as two or more values approach zero (in the multivariable limit sense) no longer exists.  Even in the simple case of computing the harmonic mean H(x, y) of two values, the limit of H(x, y) as (x, y) -> (0, 0) does not exist. H(x, y) is one of those funky functions where there are different paths to the origin in the second and fourth quadrants that lead to different values of the limit.  Of course, practicality beats purity, so the harmonic mean could simply be defined to be 0 whenever any one of the inputs is 0.  Then the only issue is the one you mentioned: the handling of the case where the denominator of the harmonic mean formula is zero.  In that case, the code would return NAN as you suggested, or raise an exception.  Overall, I don't think handling negative values is very important, and I'm not sure such a change to the function is worthwhile.  On the other hand, I think it would be better than the current behavior.

> By the way, I've just noticed that harmonic_mean([INF, INF]) raises. Should it return INF instead?

Yes, I expect INF in that case.  Currently it only raises when all the inputs are INF.  Include one finite value, and there is no error:

In [67]: harmonic_mean([math.inf, math.inf, 5])
Out[67]: 15.0

The exception could be fixed by checking if total is zero before computing n/total (currently computed in the return statement of the function).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Mon Oct  7 04:54:41 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 07 Oct 2019 08:54:41 +0000
Subject: [issue14364] Argparse incorrectly handles '--' as argument to option
In-Reply-To: <1332080953.55.0.495639573781.issue14364@psf.upfronthosting.co.za>
Message-ID: <1570438481.6.0.060166702542.issue14364@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

> The PR's Misc/NEWS entry, "Fix behavior of argparse when '--' as argument to option", is insufficient.

Thanks for your comment, Raymond. I would continue update the desc.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue14364>
_______________________________________

From report at bugs.python.org  Mon Oct  7 05:10:21 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 09:10:21 +0000
Subject: [issue25988] collections.abc.Indexable
In-Reply-To: <1451686739.56.0.219134772531.issue25988@psf.upfronthosting.co.za>
Message-ID: <1570439421.65.0.100599777936.issue25988@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset ef092fe9905f61ca27889092ca1248a11aa74498 by Serhiy Storchaka in branch 'master':
bpo-25988: Do not expose abstract collection classes in the collections module. (GH-10596)
https://github.com/python/cpython/commit/ef092fe9905f61ca27889092ca1248a11aa74498


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue25988>
_______________________________________

From report at bugs.python.org  Mon Oct  7 05:14:51 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 07 Oct 2019 09:14:51 +0000
Subject: [issue38390] Got an compile warning in dictobject.c
Message-ID: <1570439691.81.0.591764842739.issue38390@roundup.psfhosted.org>


New submission from hai shi <shihai1991 at 126.com>:

The warning detail:

Objects/dictobject.c: In function ?_PyDictView_Intersect?:
Objects/dictobject.c:4189:15: warning: unused variable ?tmp? [-Wunused-variable]
     PyObject *tmp;
               ^

----------
components: Build
messages: 354068
nosy: shihai1991
priority: normal
severity: normal
status: open
title: Got an compile warning in dictobject.c
type: compile error
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38390>
_______________________________________

From report at bugs.python.org  Mon Oct  7 05:15:59 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 07 Oct 2019 09:15:59 +0000
Subject: [issue38390] Got a compile warning in dictobject.c
In-Reply-To: <1570439691.81.0.591764842739.issue38390@roundup.psfhosted.org>
Message-ID: <1570439759.87.0.797134504569.issue38390@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
title: Got an compile warning in dictobject.c -> Got a compile warning in dictobject.c

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38390>
_______________________________________

From report at bugs.python.org  Mon Oct  7 05:16:38 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 09:16:38 +0000
Subject: [issue38215] Do not import modules in star-import when __all__ is not
 defined.
In-Reply-To: <1568822213.45.0.69943350833.issue38215@roundup.psfhosted.org>
Message-ID: <1570439798.74.0.927048250804.issue38215@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38215>
_______________________________________

From report at bugs.python.org  Mon Oct  7 05:17:05 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 07 Oct 2019 09:17:05 +0000
Subject: [issue38390] Got a compile warning in dictobject.c
In-Reply-To: <1570439691.81.0.591764842739.issue38390@roundup.psfhosted.org>
Message-ID: <1570439825.61.0.970439098079.issue38390@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
keywords: +patch
pull_requests: +16198
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16610

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38390>
_______________________________________

From report at bugs.python.org  Mon Oct  7 05:36:21 2019
From: report at bugs.python.org (=?utf-8?q?Lo=C3=AFc_Etienne?=)
Date: Mon, 07 Oct 2019 09:36:21 +0000
Subject: [issue38391] Typo in tutorial code (does not compile)
Message-ID: <1570440981.11.0.0420917562712.issue38391@roundup.psfhosted.org>


New submission from Lo?c Etienne <loic.jonas.etienne at gmail.com>:

https://docs.python.org/3.7/extending/newtypes_tutorial.html

Is: PY_DECREF(m);
Should be: Py_DECREF(m);

----------
components: Demos and Tools
messages: 354069
nosy: Lo?c Etienne
priority: normal
severity: normal
status: open
title: Typo in tutorial code (does not compile)
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38391>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:05:29 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:05:29 +0000
Subject: [issue38210] Intersection of dict view with iterator returns empty set
In-Reply-To: <1568790606.98.0.898790756289.issue38210@roundup.psfhosted.org>
Message-ID: <1570442729.5.0.667011761711.issue38210@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16199
pull_request: https://github.com/python/cpython/pull/16611

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38210>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:14:01 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:14:01 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1570443241.29.0.603236906832.issue36389@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16200
pull_request: https://github.com/python/cpython/pull/16612

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:14:01 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:14:01 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570443241.43.0.350894484691.issue38376@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16201
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16612

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:14:55 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 10:14:55 +0000
Subject: [issue28869] __module__ attribute is not set correctly for a class
 created by direct metaclass call
In-Reply-To: <1480885774.84.0.670239959771.issue28869@psf.upfronthosting.co.za>
Message-ID: <1570443295.32.0.723207676877.issue28869@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16202
pull_request: https://github.com/python/cpython/pull/16613

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28869>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:15:22 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:15:22 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570443322.78.0.624434474757.issue38376@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

My intent in bpo-36389 was to also provide _PyObject_CheckConsistency() in release mode to help debugging GC crash, especially in visit_decref(). I wrote PR 16612 to fix my implementation.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:18:35 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 10:18:35 +0000
Subject: [issue28869] __module__ attribute is not set correctly for a class
 created by direct metaclass call
In-Reply-To: <1480885774.84.0.670239959771.issue28869@psf.upfronthosting.co.za>
Message-ID: <1570443515.49.0.686434781206.issue28869@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

There is a simpler way to fix this issue. Instead of hacking __new__, the inheritance registry can be set up in ABCMeta.__init__. There are no reasons of making this in __new__.

----------
versions: +Python 3.7, Python 3.8, Python 3.9 -Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28869>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:20:31 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 10:20:31 +0000
Subject: [issue38390] Got a compile warning in dictobject.c
In-Reply-To: <1570439691.81.0.591764842739.issue38390@roundup.psfhosted.org>
Message-ID: <1570443631.21.0.129375554669.issue38390@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38390>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:21:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:21:20 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570443680.09.0.8477910249.issue38353@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16203
pull_request: https://github.com/python/cpython/pull/16614

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:22:42 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 10:22:42 +0000
Subject: [issue25988] collections.abc.Indexable
In-Reply-To: <1451686739.56.0.219134772531.issue25988@psf.upfronthosting.co.za>
Message-ID: <1570443762.82.0.214802904716.issue25988@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.9 -Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue25988>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:28:19 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:28:19 +0000
Subject: [issue38210] Intersection of dict view with iterator returns empty set
In-Reply-To: <1568790606.98.0.898790756289.issue38210@roundup.psfhosted.org>
Message-ID: <1570444099.4.0.165218898717.issue38210@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset d97f1ce6dba6c4aa5614adc06ad2e0948709845c by Victor Stinner in branch 'master':
bpo-38210: Fix compiler warning in dictobject.c (GH-16611)
https://github.com/python/cpython/commit/d97f1ce6dba6c4aa5614adc06ad2e0948709845c


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38210>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:29:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:29:26 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1570444166.7.0.908163938998.issue36389@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Update: I added an assertion which should help to detect some kind of bugs in debug mode:

commit d91d4de31745fc1ed4c7e6c208917827c9c472b6
Author: Victor Stinner <vstinner at redhat.com>
Date:   Mon Sep 9 17:44:59 2019 +0200

    bpo-38070: visit_decref() calls _PyObject_IsFreed() (GH-15782)
    
    In debug mode, visit_decref() now calls _PyObject_IsFreed() to ensure
    that the object is not freed. If it's freed, the program fails with
    an assertion error and Python dumps informations about the freed
    object.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:48:58 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:48:58 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
Message-ID: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

A bug in Python/hamt.c was only discovered 4 months after the code was added to Python:
* https://mail.python.org/pipermail/python-dev/2018-June/153857.html
* https://bugs.python.org/issue33803

The problem was that an object was tracked by the GC, whereas calling its traverse method crashed Python... depending when the traverse method is called exactly.

Pseudo-code:

  PyObject_GC_Track(<partially initialized object>);
  ...
  obj2 = PyObject_GC_NewVar(...);
  ...
  <finish to initialize the first object>

The problem is that PyObject_GC_NewVar() can trigger a GC collection which uses the partially initialized object, and then we get a cryptic crash in the GC (usually seen in visit_decref()).

I propose to make PyObject_GC_Track() stricter: validate that the object seems to be "valid" or "fully initialized". From the GC point of view, it means that calling tp_traverse must not crash.

Attached PR is a concrete implementation.

This issue is a follow-up of my previously failed attempt bpo-36389 "Add gc.enable_object_debugger(): detect corrupted Python objects in the GC". While bpo-36389 attempts to discoverd corrupted objects once a GC collection is triggered, this issue is restricted to objects entering the GC.

First problem: my PR breaks Modules/pyexpat.c whereas the code is not strictly a bug: in Python 3.8, it's ok to put a partially initialized object into the GC if no GC collection can be triggered before the object is fully initialized. In Modules/pyexpat.c case, the code looks safe from that point of view.

It means that such change is a backward incompatible change. IMHO it's a good step forward, since it is likely to discovered hidden bugs.

----------
components: Interpreter Core
messages: 354074
nosy: vstinner
priority: normal
severity: normal
status: open
title: Ensure that objects entering the GC are valid
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:54:28 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:54:28 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570445668.54.0.261064782393.issue38392@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16204
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16615

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:55:45 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:55:45 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570445745.22.0.942154058501.issue38392@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Pablo, Tim, Neal: what do you think of this idea?

----------
nosy: +nnorwitz, pablogsal, tim.peters
stage: patch review -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:56:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:56:20 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1570445780.68.0.599167411867.issue36389@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I created bpo-38392 "Ensure that objects entering the GC are valid".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Mon Oct  7 06:57:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 10:57:02 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570445821.99.0.58482677778.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset b96145a6b5d89599ebccd2111d93f5670ddae840 by Victor Stinner in branch 'master':
bpo-38353: Simplify calculate_pybuilddir() (GH-16614)
https://github.com/python/cpython/commit/b96145a6b5d89599ebccd2111d93f5670ddae840


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Mon Oct  7 07:02:41 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 11:02:41 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1570446161.63.0.349206528839.issue37531@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Oh, regrtest main process was killed by faulthandler watchdog: it was blocked in _get_result() for longer than 1 minute.

Extract of _get_result():

        use_faulthandler = (self.ns.timeout is not None)
        timeout = PROGRESS_UPDATE
        while True:
            if use_faulthandler:
                faulthandler.dump_traceback_later(timeout * 2.0, exit=True)

            # wait for a thread
            try:
                return self.output.get(timeout=timeout)
            except queue.Empty:
                pass

            # display progress
            running = get_running(self.workers)
            if running and not self.ns.pgo:
                self.log('running: %s' % ', '.join(running))

self.ns.timeout is supposed to be 1500.

I don't understand why regrtest got a timeout of 60 seconds?

https://buildbot.python.org/all/#/builders/168/builds/1583

LD_LIBRARY_PATH=/usr/home/buildbot/python/3.x.koobs-freebsd-current/build ./python  ./Tools/scripts/run_tests.py -j 1 -u all -W --slowest --fail-env-changed --timeout=1500 -j2 -j4 
== CPython 3.9.0a0 (heads/master:ed8efd8e2c, Oct 7 2019, 21:38:27) [Clang 8.0.1 (tags/RELEASE_801/final 366581)]
== FreeBSD-13.0-CURRENT-amd64-64bit-ELF little-endian
== cwd: /usr/home/buildbot/python/3.x.koobs-freebsd-current/build/build/test_python_67537
== CPU count: 4
== encodings: locale=UTF-8, FS=utf-8
Using random seed 1307598
0:00:00 load avg: 3.41 Run tests in parallel using 4 child processes
(...)
0:00:11 load avg: 3.55 [ 12/419] test_extcall passed
0:00:13 load avg: 3.55 [ 13/419] test_pydoc passed
0:00:14 load avg: 3.55 [ 14/419] test_devpoll skipped
test_devpoll skipped -- test works only on Solaris OS family
0:00:15 load avg: 3.55 [ 15/419] test_class passed
0:00:17 load avg: 3.50 [ 16/419] test_ntpath passed
Timeout (0:01:00)!
Thread 0x0000000802d30c00 (most recent call first):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/selectors.py", line 415 in select
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/subprocess.py", line 1964 in _communicate
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/subprocess.py", line 1113 in communicate
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 199 in _run_process
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 228 in _runtest
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 265 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/threading.py", line 944 in _bootstrap_inner
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/threading.py", line 902 in _bootstrap

Thread 0x0000000802d2fd00 (most recent call first):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/selectors.py", line 415 in select
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/subprocess.py", line 1964 in _communicate
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/subprocess.py", line 1113 in communicate
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 199 in _run_process
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 228 in _runtest
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 265 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/threading.py", line 944 in _bootstrap_inner
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/threading.py", line 902 in _bootstrap

Thread 0x0000000802d2f800 (most recent call first):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/selectors.py", line 415 in select
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/subprocess.py", line 1964 in _communicate
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/subprocess.py", line 1113 in communicate
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 199 in _run_process
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 228 in _runtest
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 265 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/threading.py", line 944 in _bootstrap_inner
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/threading.py", line 902 in _bootstrap

Thread 0x0000000802d30200 (most recent call first):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/selectors.py", line 415 in select
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/subprocess.py", line 1964 in _communicate
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/subprocess.py", line 1113 in communicate
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 199 in _run_process
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 228 in _runtest
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 265 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/threading.py", line 944 in _bootstrap_inner
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/threading.py", line 902 in _bootstrap

Thread 0x0000000800acc000 (most recent call first):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/threading.py", line 307 in wait
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/queue.py", line 179 in get
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 362 in _get_result
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 413 in run_tests
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 434 in run_tests_multiprocess
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/main.py", line 513 in run_tests
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/main.py", line 687 in _main
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/main.py", line 634 in main
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/libregrtest/main.py", line 712 in main
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/test/__main__.py", line 2 in <module>
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/runpy.py", line 85 in _run_code
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-current/build/Lib/runpy.py", line 192 in _run_module_as_main
*** Error code 1

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Mon Oct  7 07:04:35 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 11:04:35 +0000
Subject: [issue38323] test_ayncio: test_close_kill_running() hangs on AMD64
 RHEL7 Refleaks 3.x
In-Reply-To: <1569848255.08.0.155489980043.issue38323@roundup.psfhosted.org>
Message-ID: <1570446275.3.0.434598582171.issue38323@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Fail on x86 Gentoo Refleaks 3.x:
https://buildbot.python.org/all/#/builders/1/builds/737

(...)
Loop <_UnixSelectorEventLoop running=False closed=True debug=False> that handles pid 8654 is closed
.Timeout (3:15:00)!
Thread 0xb7b92700 (most recent call first):
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/selectors.py", line 468 in select
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/asyncio/base_events.py", line 1837 in _run_once
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/asyncio/base_events.py", line 589 in run_forever
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/asyncio/base_events.py", line 621 in run_until_complete
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/test_asyncio/test_subprocess.py", line 484 in test_close_kill_running
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/case.py", line 616 in _callTestMethod
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/case.py", line 659 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/case.py", line 719 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 122 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 84 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 122 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 84 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 122 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 84 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 122 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 84 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 122 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 84 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/support/testresult.py", line 162 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/support/__init__.py", line 2032 in _run_suite
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/support/__init__.py", line 2128 in run_unittest
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest.py", line 209 in _test_module
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/refleak.py", line 87 in dash_R
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest.py", line 232 in _runtest_inner2
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest.py", line 270 in _runtest_inner
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest.py", line 153 in _runtest
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest.py", line 193 in runtest
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest_mp.py", line 67 in run_tests_worker
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/main.py", line 654 in _main
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/main.py", line 634 in main
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/main.py", line 712 in main
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/regrtest.py", line 43 in _main
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/regrtest.py", line 47 in <module>
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/runpy.py", line 85 in _run_code
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/runpy.py", line 192 in _run_module_as_main

== Tests result: FAILURE ==

410 tests OK.

10 slowest tests:
- test_concurrent_futures: 23 min 2 sec
- test_multiprocessing_spawn: 22 min 6 sec
- test_multiprocessing_forkserver: 15 min 51 sec
- test_multiprocessing_fork: 10 min 15 sec
- test_regrtest: 10 min 10 sec
- test_gdb: 8 min 26 sec
- test_lib2to3: 7 min 31 sec
- test_pickle: 7 min
- test_io: 6 min 50 sec
- test_subprocess: 6 min 37 sec

1 test failed:
    test_asyncio

8 tests skipped:
    test_devpoll test_kqueue test_msilib test_startfile
    test_winconsoleio test_winreg test_winsound test_zipfile64
4:25:59 load avg: 1.55
4:25:59 load avg: 1.55 Re-running failed tests in verbose mode
4:25:59 load avg: 1.55 Re-running test_asyncio in verbose mode
(...)
test_close_kill_running (test.test_asyncio.test_subprocess.SubprocessMultiLoopWatcherTests) ... Timeout (3:15:00)!
Thread 0xb7c51700 (most recent call first):
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/selectors.py", line 468 in select
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/asyncio/base_events.py", line 1837 in _run_once
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/asyncio/base_events.py", line 589 in run_forever
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/asyncio/base_events.py", line 621 in run_until_complete
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/test_asyncio/test_subprocess.py", line 484 in test_close_kill_running
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/case.py", line 616 in _callTestMethod
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/case.py", line 659 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/case.py", line 719 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 122 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 84 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 122 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 84 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 122 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 84 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 122 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 84 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 122 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/suite.py", line 84 in __call__
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/unittest/runner.py", line 176 in run
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/support/__init__.py", line 2032 in _run_suite
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/support/__init__.py", line 2128 in run_unittest
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest.py", line 209 in _test_module
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/refleak.py", line 87 in dash_R
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest.py", line 232 in _runtest_inner2
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest.py", line 270 in _runtest_inner
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest.py", line 153 in _runtest
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/runtest.py", line 193 in runtest
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/main.py", line 318 in rerun_failed_tests
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/main.py", line 691 in _main
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/main.py", line 634 in main
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/libregrtest/main.py", line 712 in main
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/__main__.py", line 2 in <module>
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/runpy.py", line 85 in _run_code
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/runpy.py", line 192 in _run_module_as_main
make: *** [Makefile:1163: buildbottest] Error 1

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38323>
_______________________________________

From report at bugs.python.org  Mon Oct  7 07:09:08 2019
From: report at bugs.python.org (Krishna Oza)
Date: Mon, 07 Oct 2019 11:09:08 +0000
Subject: [issue38391] Typo in tutorial code (does not compile)
In-Reply-To: <1570440981.11.0.0420917562712.issue38391@roundup.psfhosted.org>
Message-ID: <1570446548.98.0.862800676733.issue38391@roundup.psfhosted.org>


Change by Krishna Oza <krishoza15sep at gmail.com>:


----------
keywords: +patch
pull_requests: +16205
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16616

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38391>
_______________________________________

From report at bugs.python.org  Mon Oct  7 07:21:36 2019
From: report at bugs.python.org (Thomas Wouters)
Date: Mon, 07 Oct 2019 11:21:36 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570447296.89.0.606155747918.issue38392@roundup.psfhosted.org>


Thomas Wouters <thomas at python.org> added the comment:

I'm pretty sure you meant nascheme, not nnorwitz.

----------
nosy: +nascheme, twouters -nnorwitz

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Mon Oct  7 07:35:15 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 11:35:15 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570448115.29.0.148318211025.issue38392@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

It could be possible to do this in backward compatible way. PyObject_GC_Track() could add the object to the list of new objects (all objects are already linked in bi-linked list, so it would need to just move the object to the specified list), and PyObject_GC_NewVar() could check all new objects and clear the list of new objects (just move the head).

I am not sure it is worth to do such complication.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Mon Oct  7 07:42:08 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 11:42:08 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570448528.2.0.416187203627.issue38392@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

>From documentation:

.. c:function:: void PyObject_GC_Track(PyObject *op)

   Adds the object *op* to the set of container objects tracked by the
   collector.  The collector can run at unexpected times so objects must be
   valid while being tracked.  This should be called once all the fields
   followed by the :c:member:`~PyTypeObject.tp_traverse` handler become valid, usually near the
   end of the constructor.

So there was a bug in Modules/pyexpat.c.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Mon Oct  7 07:57:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 11:57:20 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570449440.96.0.389160059094.issue38392@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> I'm pretty sure you meant nascheme, not nnorwitz.

Oops, right :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Mon Oct  7 07:57:53 2019
From: report at bugs.python.org (Xiang Zhang)
Date: Mon, 07 Oct 2019 11:57:53 +0000
Subject: [issue38391] Typo in tutorial code (does not compile)
In-Reply-To: <1570440981.11.0.0420917562712.issue38391@roundup.psfhosted.org>
Message-ID: <1570449473.89.0.701089964586.issue38391@roundup.psfhosted.org>


Xiang Zhang <angwerzx at 126.com> added the comment:


New changeset 038503e08ac5b10601b95d5adc2c2cab7be10163 by Xiang Zhang (Krishna Oza) in branch 'master':
bpo-38391: Fixing a typo for Py_DECREF (GH-16616)
https://github.com/python/cpython/commit/038503e08ac5b10601b95d5adc2c2cab7be10163


----------
nosy: +xiang.zhang

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38391>
_______________________________________

From report at bugs.python.org  Mon Oct  7 07:58:09 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 11:58:09 +0000
Subject: [issue38391] Typo in tutorial code (does not compile)
In-Reply-To: <1570440981.11.0.0420917562712.issue38391@roundup.psfhosted.org>
Message-ID: <1570449489.38.0.133326904574.issue38391@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16206
pull_request: https://github.com/python/cpython/pull/16618

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38391>
_______________________________________

From report at bugs.python.org  Mon Oct  7 07:58:15 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 11:58:15 +0000
Subject: [issue38391] Typo in tutorial code (does not compile)
In-Reply-To: <1570440981.11.0.0420917562712.issue38391@roundup.psfhosted.org>
Message-ID: <1570449495.79.0.00883093935011.issue38391@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16207
pull_request: https://github.com/python/cpython/pull/16619

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38391>
_______________________________________

From report at bugs.python.org  Mon Oct  7 08:04:12 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 12:04:12 +0000
Subject: [issue38391] Typo in tutorial code (does not compile)
In-Reply-To: <1570440981.11.0.0420917562712.issue38391@roundup.psfhosted.org>
Message-ID: <1570449852.4.0.926150882278.issue38391@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 77b4a659b60536caf11c547332d30677f3e8f02e by Miss Islington (bot) in branch '3.7':
bpo-38391: Fixing a typo for Py_DECREF (GH-16616)
https://github.com/python/cpython/commit/77b4a659b60536caf11c547332d30677f3e8f02e


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38391>
_______________________________________

From report at bugs.python.org  Mon Oct  7 08:05:12 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 12:05:12 +0000
Subject: [issue38391] Typo in tutorial code (does not compile)
In-Reply-To: <1570440981.11.0.0420917562712.issue38391@roundup.psfhosted.org>
Message-ID: <1570449912.49.0.0396620237618.issue38391@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 985ec986e864b670687b900a4d6ca977b4e9694d by Miss Islington (bot) in branch '3.8':
bpo-38391: Fixing a typo for Py_DECREF (GH-16616)
https://github.com/python/cpython/commit/985ec986e864b670687b900a4d6ca977b4e9694d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38391>
_______________________________________

From report at bugs.python.org  Mon Oct  7 08:06:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 12:06:07 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570449967.12.0.263946945781.issue38392@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> It could be possible to do this in backward compatible way. PyObject_GC_Track() could add the object to the list of new objects (all objects are already linked in bi-linked list, so it would need to just move the object to the specified list), and PyObject_GC_NewVar() could check all new objects and clear the list of new objects (just move the head).

That's different than what I'm proposing here. Checking "later" is more on the bpo-36389 side: my bpo-36389 PR modified PyObject_GC_NewVar() to check that young object are valid.

Moreover, my bpo-36389 PR required threshold: checking all young objects at each PyObject_GC_NewVar() simply killed performance which made the whole approach unusable in practice. Because of the threshold, my implementation failed to detect the hamt.c bug bpo-33803: the partially initialized was already fully initialized when my "object debugger" ran. PR 16615 detects immediately the hamt.c bug bpo-33803.

I designed bpo-36389 to attempt to detect when an object is corrupted after its creation, corrupted by code running "later".

We had a customer with a bug in OpenStack Nova. Nova crashed in visit_decref() but I failed to debug the issue. It motivated me to modify the debug ABI in Python 3.8, so later it will become possible to switch from release to debug mode to attempt to debug a program using additional checks added by the debug build.

Here my intent is to ensure that objects entering the GC are valid to help to keep the GC list consistent and valid. But it doesn't prevent an object from being corrupted after its creation. We should try to find a different approach for that (maybe revisit bpo-36389).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Mon Oct  7 08:11:05 2019
From: report at bugs.python.org (Xiang Zhang)
Date: Mon, 07 Oct 2019 12:11:05 +0000
Subject: [issue38391] Typo in tutorial code (does not compile)
In-Reply-To: <1570440981.11.0.0420917562712.issue38391@roundup.psfhosted.org>
Message-ID: <1570450265.75.0.397714416111.issue38391@roundup.psfhosted.org>


Change by Xiang Zhang <angwerzx at 126.com>:


----------
assignee:  -> docs at python
components: +Documentation -Demos and Tools
nosy: +docs at python
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38391>
_______________________________________

From report at bugs.python.org  Mon Oct  7 08:13:12 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 12:13:12 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1570450392.69.0.067136924725.issue37531@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> I don't understand why regrtest got a timeout of 60 seconds?

Oh, that comes from "timeout = PROGRESS_UPDATE" with "PROGRESS_UPDATE = 30.0".

But it means that the main process was stuck for longer than 60 seconds!?

The main process is supposed to write an update "running: ..." every 30 seconds.

This buildbot is very slow. Maybe 30 and 60 seconds limits are too low?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Mon Oct  7 08:25:18 2019
From: report at bugs.python.org (Mark Shannon)
Date: Mon, 07 Oct 2019 12:25:18 +0000
Subject: [issue26219] implement per-opcode cache in ceval
In-Reply-To: <1453918500.26.0.0886095278127.issue26219@psf.upfronthosting.co.za>
Message-ID: <1570451118.04.0.185026669888.issue26219@roundup.psfhosted.org>


Mark Shannon <mark at hotpy.org> added the comment:

"What's new in Python 3.8" says that this change speeds up the LOAD_GLOBAL opcode by 40%.
That seems meaningless as a program cannot have LOAD_GLOBAL in isolation so any test would have other bytecodes as well.

What's the evidence for the claimed speedup?
What's the speedup on the benchmark suite?

----------
nosy: +Mark.Shannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26219>
_______________________________________

From report at bugs.python.org  Mon Oct  7 08:28:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 12:28:07 +0000
Subject: [issue26219] implement per-opcode cache in ceval
In-Reply-To: <1453918500.26.0.0886095278127.issue26219@psf.upfronthosting.co.za>
Message-ID: <1570451287.0.0.918003641485.issue26219@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> What's the evidence for the claimed speedup?
> What's the speedup on the benchmark suite?

https://github.com/python/cpython/pull/12884#issuecomment-485091040
points to:
https://github.com/methane/sandbox/tree/master/2019/opcache_load_global#opcache-for-load_global

== Microbenchmark ==

$ master/python -m perf timeit -s 'def foo(): int; str; bytes; float; int; str; bytes; float' -- 'foo()'
.....................
Mean +- std dev: 213 ns +- 5 ns

$ opcache/python -m perf timeit -s 'def foo(): int; str; bytes; float; int; str; bytes; float' -- 'foo()'
.....................
Mean +- std dev: 120 ns +- 2 ns

== pyperformance ==

$ ./cpython/python -m perf compare_to master.json opcache_load_global.json -G  --min-speed=2
Slower (2):
- pickle: 19.1 us +- 0.2 us -> 19.7 us +- 0.8 us: 1.03x slower (+3%)
- unpickle_list: 8.66 us +- 0.04 us -> 8.85 us +- 0.06 us: 1.02x slower (+2%)

Faster (23):
- scimark_lu: 424 ms +- 22 ms -> 384 ms +- 4 ms: 1.10x faster (-9%)
- regex_compile: 359 ms +- 4 ms -> 330 ms +- 1 ms: 1.09x faster (-8%)
- django_template: 250 ms +- 3 ms -> 231 ms +- 2 ms: 1.08x faster (-8%)
- unpickle_pure_python: 802 us +- 12 us -> 754 us +- 9 us: 1.06x faster (-6%)
- pickle_pure_python: 1.04 ms +- 0.01 ms -> 991 us +- 15 us: 1.05x faster (-5%)
- hexiom: 20.8 ms +- 0.2 ms -> 19.8 ms +- 0.1 ms: 1.05x faster (-5%)
- logging_simple: 18.4 us +- 0.2 us -> 17.6 us +- 0.2 us: 1.05x faster (-4%)
- sympy_expand: 774 ms +- 5 ms -> 741 ms +- 3 ms: 1.04x faster (-4%)
- json_dumps: 28.1 ms +- 0.2 ms -> 27.0 ms +- 0.2 ms: 1.04x faster (-4%)
- logging_format: 20.4 us +- 0.2 us -> 19.6 us +- 0.3 us: 1.04x faster (-4%)
- richards: 147 ms +- 2 ms -> 141 ms +- 1 ms: 1.04x faster (-4%)
- meteor_contest: 189 ms +- 1 ms -> 182 ms +- 1 ms: 1.04x faster (-4%)
- xml_etree_iterparse: 226 ms +- 2 ms -> 217 ms +- 2 ms: 1.04x faster (-4%)
- sympy_str: 358 ms +- 3 ms -> 345 ms +- 4 ms: 1.04x faster (-4%)
- sqlalchemy_imperative: 44.0 ms +- 1.2 ms -> 42.4 ms +- 1.2 ms: 1.04x faster (-4%)
- sympy_sum: 167 ms +- 1 ms -> 161 ms +- 1 ms: 1.04x faster (-4%)
- nqueens: 217 ms +- 1 ms -> 211 ms +- 1 ms: 1.03x faster (-3%)
- fannkuch: 1.09 sec +- 0.01 sec -> 1.07 sec +- 0.00 sec: 1.03x faster (-3%)
- raytrace: 1.11 sec +- 0.02 sec -> 1.08 sec +- 0.01 sec: 1.03x faster (-3%)
- dulwich_log: 122 ms +- 1 ms -> 119 ms +- 1 ms: 1.03x faster (-3%)
- logging_silent: 419 ns +- 5 ns -> 410 ns +- 5 ns: 1.02x faster (-2%)
- sympy_integrate: 33.5 ms +- 0.1 ms -> 32.8 ms +- 0.2 ms: 1.02x faster (-2%)
- pathlib: 40.8 ms +- 0.4 ms -> 40.0 ms +- 0.5 ms: 1.02x faster (-2%)

Benchmark hidden because not significant (32): (...)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26219>
_______________________________________

From report at bugs.python.org  Mon Oct  7 08:41:00 2019
From: report at bugs.python.org (Mark Shannon)
Date: Mon, 07 Oct 2019 12:41:00 +0000
Subject: [issue26219] implement per-opcode cache in ceval
In-Reply-To: <1453918500.26.0.0886095278127.issue26219@psf.upfronthosting.co.za>
Message-ID: <1570452060.66.0.886326993478.issue26219@roundup.psfhosted.org>


Mark Shannon <mark at hotpy.org> added the comment:

Given that
def foo(): int; str; bytes; float; int; str; bytes; float
can be trivially be rewritten as
def foo(): pass
I think that benchmark is meaningless.

I really don't think we should be making claims like "40% speedup" for such contrived examples.

It looks like the speedup is real, but only about 2% speedup overall.
The "what's new" should reflect that, IMO.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26219>
_______________________________________

From report at bugs.python.org  Mon Oct  7 09:12:36 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 07 Oct 2019 13:12:36 +0000
Subject: [issue37324] collections: remove deprecated aliases to ABC classes
In-Reply-To: <1560803912.16.0.0813723259969.issue37324@roundup.psfhosted.org>
Message-ID: <1570453956.49.0.0597133205545.issue37324@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

I think this can be closed since https://bugs.python.org/issue25988 has the PR merged.

----------
nosy: +serhiy.storchaka, xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37324>
_______________________________________

From report at bugs.python.org  Mon Oct  7 09:14:45 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 07 Oct 2019 13:14:45 +0000
Subject: [issue36953] Remove collections ABCs?
In-Reply-To: <1558140764.46.0.049733618419.issue36953@roundup.psfhosted.org>
Message-ID: <1570454085.16.0.0517423511793.issue36953@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

The removal was done in https://bugs.python.org/issue25988 . Given that the version in warning message was updated I guess this can be closed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36953>
_______________________________________

From report at bugs.python.org  Mon Oct  7 09:20:44 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 13:20:44 +0000
Subject: [issue37324] collections: remove deprecated aliases to ABC classes
In-Reply-To: <1560803912.16.0.0813723259969.issue37324@roundup.psfhosted.org>
Message-ID: <1570454444.09.0.596948676476.issue37324@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> collections.abc.Indexable

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37324>
_______________________________________

From report at bugs.python.org  Mon Oct  7 09:21:47 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 13:21:47 +0000
Subject: [issue36953] Remove collections ABCs?
In-Reply-To: <1558140764.46.0.049733618419.issue36953@roundup.psfhosted.org>
Message-ID: <1570454507.87.0.98593679987.issue36953@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36953>
_______________________________________

From report at bugs.python.org  Mon Oct  7 09:24:31 2019
From: report at bugs.python.org (Chih-Hsuan Yen)
Date: Mon, 07 Oct 2019 13:24:31 +0000
Subject: [issue36953] Remove collections ABCs?
In-Reply-To: <1558140764.46.0.049733618419.issue36953@roundup.psfhosted.org>
Message-ID: <1570454671.63.0.875492061985.issue36953@roundup.psfhosted.org>


Chih-Hsuan Yen <yan12125 at gmail.com> added the comment:

Lib/collections/__init__.py on branch 3.7 still states:

> Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working

I think it should also be updated (hopefully before 3.7.5?) as the actual removal turns out to be in 3.9.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36953>
_______________________________________

From report at bugs.python.org  Mon Oct  7 09:27:24 2019
From: report at bugs.python.org (pmp-p)
Date: Mon, 07 Oct 2019 13:27:24 +0000
Subject: [issue38393] building modules from 3.8.0rc1 fails in a venv when
 system 3.8 is present
Message-ID: <1570454844.33.0.763324170679.issue38393@roundup.psfhosted.org>


New submission from pmp-p <pmpp.pub at gmail.com>:

when trying to build rc1 from a b4 venv to prepare a python host for cross compilation on ubuntu xenial flavour x64

i got :


cd /tmp
python3.7 -m venv testenv
cd testenv/
. bin/activate
(testenv) /tmp/testenv $ tar xf /tmp/Python-3.8.0rc1.tar.xz && cd Python-3.8.0rc1

CC=clang ./configure --prefix=/tmp/python3.host --with-system-ffi --disable-ipv6 --without-ensurepip --with-c-locale-coercion --disable-shared && make

./python -E ./setup.py  build
step will fail for the reason i suspect is srcdir is taken from system python3.8 if installed ( /usr/local in that case )

$ ./python -E 
Python 3.8.0rc1 (default, Oct  7 2019, 15:16:07) 
[Clang 6.0.0 (tags/RELEASE_600/final)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('srcdir')
'/usr/local/lib/python3.8/config-3.8-x86_64-linux-gnu'
>>>

----------
messages: 354095
nosy: pmpp, vstinner
priority: normal
severity: normal
status: open
title: building modules from 3.8.0rc1 fails in a venv when system 3.8 is present
type: compile error
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38393>
_______________________________________

From report at bugs.python.org  Mon Oct  7 09:40:51 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 13:40:51 +0000
Subject: [issue38393] building modules from 3.8.0rc1 fails in a venv when
 system 3.8 is present
In-Reply-To: <1570454844.33.0.763324170679.issue38393@roundup.psfhosted.org>
Message-ID: <1570455651.67.0.930942074982.issue38393@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It's not a Python 3.8 regression. Python 3.7 has the same behavior.


cd $HOME
python3.7 -m venv testenv
cd testenv/
. bin/activate

wget https://www.python.org/ftp/python/3.8.0/Python-3.8.0rc1.tar.xz
tar -xf Python-3.8.0rc1.tar.xz && cd Python-3.8.0rc1
CC=clang ./configure --prefix=/tmp/python3.host --with-system-ffi --disable-ipv6 --without-ensurepip --with-c-locale-coercion --disable-shared && make

Python 3.8 error:

"""
$ make
./python -E -S -m sysconfig --generate-posix-vars ;\
if test $? -ne 0 ; then \
	echo "generate-posix-vars failed" ; \
	rm -f ./pybuilddir.txt ; \
	exit 1 ; \
fi
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Python path configuration:
  PYTHONHOME = (not set)
  PYTHONPATH = (not set)
  program name = './python'
  isolated = 0
  environment = 0
  user site = 1
  import site = 0
  sys._base_executable = '/home/vstinner/testenv/Python-3.8.0rc1/python'
  sys.base_prefix = '/tmp/python3.host'
  sys.base_exec_prefix = '/tmp/python3.host'
  sys.executable = '/home/vstinner/testenv/Python-3.8.0rc1/python'
  sys.prefix = '/tmp/python3.host'
  sys.exec_prefix = '/tmp/python3.host'
  sys.path = [
    '/tmp/python3.host/lib/python38.zip',
    '/tmp/python3.host/lib/python3.8',
    '/tmp/python3.host/lib/lib-dynload',
  ]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007ff6a75f6740 (most recent call first):
<no Python frame>
generate-posix-vars failed
make: *** [Makefile:592: pybuilddir.txt] Error 1
"""


cd ..
wget https://www.python.org/ftp/python/3.7.4/Python-3.7.4.tar.xz
tar -xf Python-3.7.4.tar.xz 
cd Python-3.7.4/
CC=clang ./configure --prefix=/tmp/python3.host --with-system-ffi --disable-ipv6 --without-ensurepip --with-c-locale-coercion --disable-shared

Python 3.7 error:

"""
$ make
./python -E -S -m sysconfig --generate-posix-vars ;\
if test $? -ne 0 ; then \
	echo "generate-posix-vars failed" ; \
	rm -f ./pybuilddir.txt ; \
	exit 1 ; \
fi
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Fatal Python error: initfsencoding: Unable to get the locale encoding
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007f5a77f5a740 (most recent call first):
/bin/sh : ligne 5 : 19592 Aborted                 (core dumped)./python -E -S -m sysconfig --generate-posix-vars
generate-posix-vars failed
make: *** [Makefile:606: pybuilddir.txt] Error 1
"""

----------
components: +Build

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38393>
_______________________________________

From report at bugs.python.org  Mon Oct  7 09:41:40 2019
From: report at bugs.python.org (pmp-p)
Date: Mon, 07 Oct 2019 13:41:40 +0000
Subject: [issue38393] building modules from 3.8.0rc1 fails in a venv when
 system 3.8 is present
In-Reply-To: <1570454844.33.0.763324170679.issue38393@roundup.psfhosted.org>
Message-ID: <1570455700.45.0.477736315602.issue38393@roundup.psfhosted.org>


Change by pmp-p <pmpp.pub at gmail.com>:


----------
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38393>
_______________________________________

From report at bugs.python.org  Mon Oct  7 10:01:54 2019
From: report at bugs.python.org (Florian Krause)
Date: Mon, 07 Oct 2019 14:01:54 +0000
Subject: [issue38394] time.get_clock_info reports "adjustable=False" for
 implementation="CLOCK_MONOTONIC"
Message-ID: <1570456914.26.0.677053488358.issue38394@roundup.psfhosted.org>


New submission from Florian Krause <siebenhundertzehn at gmail.com>:

clock_gettime(CLOCK_MONOTONIC) is adjustable via NTP, as described here: https://linux.die.net/man/2/clock_gettime

(and also mentioned in PEP 418).

Yet, time.get_clock_info reports it as "adjustable=False" (this even seems to be hardcoded for all clocks on Linux).

----------
components: Library (Lib)
messages: 354097
nosy: Florian Krause
priority: normal
severity: normal
status: open
title: time.get_clock_info reports "adjustable=False" for implementation="CLOCK_MONOTONIC"
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38394>
_______________________________________

From report at bugs.python.org  Mon Oct  7 10:04:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 14:04:56 +0000
Subject: [issue38393] building modules from 3.8.0rc1 fails in a venv when
 system 3.8 is present
In-Reply-To: <1570454844.33.0.763324170679.issue38393@roundup.psfhosted.org>
Message-ID: <1570457096.9.0.122987841003.issue38393@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The problem is that Python looks for pyvenv.cfg in the program directory or in its parent directory. For example:

/tmp/testenv/Python-3.8.0rc1/python looks for /tmp/testenv/Python-3.8.0rc1/pyvenv.cfg (doesn't exist) and 
/tmp/testenv/Python-3.8.0rc1/pyvenv.cfg (exists). On my system, pyvenv.cfg contains:
---
home = /usr/bin
include-system-site-packages = false
version = 3.7.4
---

We should add an option to ignore pyvenv.cfg, or modify an existing option like -I to ignore pyvenv.cfg.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38393>
_______________________________________

From report at bugs.python.org  Mon Oct  7 10:11:43 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 14:11:43 +0000
Subject: [issue38394] time.get_clock_info reports "adjustable=False" for
 implementation="CLOCK_MONOTONIC"
In-Reply-To: <1570456914.26.0.677053488358.issue38394@roundup.psfhosted.org>
Message-ID: <1570457503.63.0.240215694287.issue38394@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Well, that's more a documentation issue than a bug.

"adjustable=False" in the context of Python means that the clock cannot jump a day forward or one day backwards.

For example, on my Fedora 30, I cannot set CLOCK_MONOTONIC clock as root:

$ sudo python3
>>> import time
>>> time.clock_settime(time.CLOCK_MONOTONIC, time.clock_gettime(time.CLOCK_MONOTONIC))
OSError: [Errno 22] Invalid argument

In the Linux kernel, NTP adjusts CLOCK_MONOTONIC so it really measures time in *seconds*, rather something faster or slower than one second :-)

Python time.monotonic() documentation clearly states that it uses the unit of one second:
https://docs.python.org/dev/library/time.html#time.monotonic
"Return the value (in fractional seconds) of a monotonic clock, i.e. a clock that cannot go backwards. (...)"

CLOCK_MONOTONIC_RAW must not be used for time.monotonic() because it doesn't use an unit of 1 second.

Feel free to propose a documentation enhancement :-)

https://docs.python.org/dev/library/time.html#time.get_clock_info

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38394>
_______________________________________

From report at bugs.python.org  Mon Oct  7 10:21:55 2019
From: report at bugs.python.org (Maarten ter Huurne)
Date: Mon, 07 Oct 2019 14:21:55 +0000
Subject: [issue21970] Broken code for handling file://host in
 urllib.request.FileHandler.file_open
In-Reply-To: <1405216161.05.0.3363234179.issue21970@psf.upfronthosting.co.za>
Message-ID: <1570458115.82.0.10636396093.issue21970@roundup.psfhosted.org>


Maarten ter Huurne <maarten at treewalker.org> added the comment:

Another problem with the current code is that when passed a URL with a host name that is not empty or "localhost", but is one of the alternative names for localhost returned by get_names(), file_open() returns None implicitly instead of opening the file.

I think this issue would be fixed by the proposed patch. So it would be good if the patch could be reviewed and adopted.

----------
nosy: +mthuurne
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21970>
_______________________________________

From report at bugs.python.org  Mon Oct  7 10:34:58 2019
From: report at bugs.python.org (Maarten ter Huurne)
Date: Mon, 07 Oct 2019 14:34:58 +0000
Subject: [issue17088] ElementTree incorrectly refuses to write attributes
 without namespaces when default_namespace is used
In-Reply-To: <1359599707.26.0.771342463799.issue17088@psf.upfronthosting.co.za>
Message-ID: <1570458898.85.0.309576548191.issue17088@roundup.psfhosted.org>


Maarten ter Huurne <maarten at treewalker.org> added the comment:

Can I please get a review of the pull request?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17088>
_______________________________________

From report at bugs.python.org  Mon Oct  7 10:49:09 2019
From: report at bugs.python.org (Sam Gross)
Date: Mon, 07 Oct 2019 14:49:09 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
Message-ID: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>


New submission from Sam Gross <colesbury at gmail.com>:

The implementation of weakref.proxy's methods call back into the Python API using a "borrowed reference" of the weakly referenced object (acquired via PyWeakref_GET_OBJECT). This API call may delete the last reference to the object (either directly or via GC), leaving a dangling pointer, which can be subsequently dereferenced.

Tested with Python 3.8.0b4 (debug build)

The following code crashes with a debug build of Python 3.8.0b4 on Linux.

import weakref

obj = None

class MyObj:
    def __iter__(self):
        global obj
        del obj
        return NotImplemented

obj = MyObj()
p = weakref.proxy(obj)
print(5 in p)


This particular test case does not crash with a release build (on Linux).

The implementation of `in` on a proxy object calls proxy_contains:

   return PySequence_Contains(PyWeakref_GET_OBJECT(proxy), value);

https://github.com/python/cpython/blob/v3.8.0b4/Objects/weakrefobject.c#L556


This eventually calls _PySequence_IterSearch. The call to PyObject_GetIter can call arbitrary code, which can lead to seq (the proxy's referent) being deleted. The subsequent call to type_error dereferences a dead object. 

    it = PyObject_GetIter(seq);
    if (it == NULL) {
        type_error("argument of type '%.200s' is not iterable", seq);
        return -1;
    }

https://github.com/python/cpython/blob/v3.8.0b4/Objects/abstract.c#L2003-L2007

I believe some functions, like proxy_length, may be immune to this problem because they do not access the borrowed referent after calling into user code. However, this is hard to verify from reading the code and may be fragile -- small changes to PyObject_Length/Size, for example, might .

See also https://bugs.python.org/issue16602

----------
components: Interpreter Core
messages: 354102
nosy: colesbury
priority: normal
severity: normal
status: open
title: proxy_contains (weakref.proxy) can access an object with 0 refcount
type: crash
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Mon Oct  7 10:56:08 2019
From: report at bugs.python.org (Sascha Silbe)
Date: Mon, 07 Oct 2019 14:56:08 +0000
Subject: [issue34271] Please support logging of SSL master secret by env
 variable SSLKEYLOGFILE
In-Reply-To: <1532867889.16.0.56676864532.issue34271@psf.upfronthosting.co.za>
Message-ID: <1570460168.63.0.399578745851.issue34271@roundup.psfhosted.org>


Change by Sascha Silbe <sascha-web-bugs.python.org at silbe.org>:


----------
nosy: +sascha_silbe

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34271>
_______________________________________

From report at bugs.python.org  Mon Oct  7 11:55:56 2019
From: report at bugs.python.org (Batuhan)
Date: Mon, 07 Oct 2019 15:55:56 +0000
Subject: [issue38396] ast.literal_eval doesn't give information about node
 except the type of it
Message-ID: <1570463756.86.0.131436803473.issue38396@roundup.psfhosted.org>


New submission from Batuhan <batuhanosmantaskaya at gmail.com>:

def _convert_num(node):
        if isinstance(node, Constant):
            if type(node.value) in (int, float, complex):
                return node.value
>       raise ValueError('malformed node or string: ' + repr(node))
E       ValueError: malformed node or string: <_ast.Name object at 0x7f0e7ebab320>

When a malformed node passes into literal_eval, it raises ValueError with repr of node (which is just a memory address and type). I think using dump(node) at there is a better option, like

node = <_ast.Name object at 0x7fa8279847d0>

    def _convert_num(node):
        if isinstance(node, Constant):
            if type(node.value) in (int, float, complex):
                return node.value
>       raise ValueError('malformed node or string: ' + dump(node))
E       ValueError: malformed node or string: Name(id='a', ctx=Load())

----------
components: Library (Lib)
messages: 354103
nosy: BTaskaya
priority: normal
severity: normal
status: open
title: ast.literal_eval doesn't give information about node except the type of it
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38396>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:02:35 2019
From: report at bugs.python.org (Batuhan)
Date: Mon, 07 Oct 2019 16:02:35 +0000
Subject: [issue38396] ast.literal_eval doesn't give information about node
 except the type of it
In-Reply-To: <1570463756.86.0.131436803473.issue38396@roundup.psfhosted.org>
Message-ID: <1570464155.92.0.276411231825.issue38396@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


----------
keywords: +patch
pull_requests: +16208
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16620

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38396>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:03:10 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 07 Oct 2019 16:03:10 +0000
Subject: [issue38396] ast.literal_eval doesn't give information about node
 except the type of it
In-Reply-To: <1570463756.86.0.131436803473.issue38396@roundup.psfhosted.org>
Message-ID: <1570464190.6.0.0745658231706.issue38396@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +levkivskyi

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38396>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:06:40 2019
From: report at bugs.python.org (retnikt)
Date: Mon, 07 Oct 2019 16:06:40 +0000
Subject: [issue38397] __init_subclass__ causes TypeError when used with more
 standard library metaclasses (such as EnumMeta)
Message-ID: <1570464400.89.0.0085195281122.issue38397@roundup.psfhosted.org>


New submission from retnikt <retnikt at gmail.com>:

Essentially the same as https://bugs.python.org/issue29581 (more detail is there), but for the additional meta-classes enum.EnumMeta and probably typing.NamedTupleMeta (discussion needed - is there a use-case for this?)

The __new__ method on these metaclasses should include **kwargs at the end of the method definition and pass them on to the super call in order to allow the special method __init_subclass__ to be defined with custom parameters on classes using the metaclass.

(also, perhaps the issue for typing should be reported separately on github python/typing instead)

----------
components: Library (Lib)
messages: 354104
nosy: retnikt
priority: normal
severity: normal
status: open
title: __init_subclass__ causes TypeError when used with more standard library metaclasses (such as EnumMeta)
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38397>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:09:58 2019
From: report at bugs.python.org (PyScripter)
Date: Mon, 07 Oct 2019 16:09:58 +0000
Subject: [issue38398] PyUnicode functions are not exported by python 2 in
 Ubuntu
Message-ID: <1570464598.55.0.274340335252.issue38398@roundup.psfhosted.org>


New submission from PyScripter <pyscripter at gmail.com>:

As per title PyUnicode functions, such as PyUnicode_FromWideChar, are not exported on Ubuntu and possibly other Linux systems.  This is a show stopper for embedded Python.

To confirm:

>>> import ctypes
>>> hasattr(ctypes.pythonapi, "PyUnicode_FromWideChar")

It should return True, but it returns False. ?

I have tested with the default Ubuntu python 2.7.15 and with compiled python 2.7.16.

Note that the problem does not exist in python3 and also python 2.7 and 3.x in Windows.  So it is only python 2.7 in Ubuntu.

----------
components: Library (Lib)
messages: 354105
nosy: pyscripter
priority: normal
severity: normal
status: open
title: PyUnicode functions are not exported by python 2 in Ubuntu
type: crash
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38398>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:14:17 2019
From: report at bugs.python.org (Zachary Ware)
Date: Mon, 07 Oct 2019 16:14:17 +0000
Subject: [issue38398] PyUnicode functions are not exported by python 2 in
 Ubuntu
In-Reply-To: <1570464598.55.0.274340335252.issue38398@roundup.psfhosted.org>
Message-ID: <1570464857.5.0.237923157764.issue38398@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:

Given that 2.7 is reaching end-of-life in a single-digit number of months, I doubt anything will be changed here.  I'll leave it up to Benjamin to make that determination, though.

----------
nosy: +benjamin.peterson, zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38398>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:20:01 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Mon, 07 Oct 2019 16:20:01 +0000
Subject: [issue36356] Failure to build with address sanitizer
In-Reply-To: <1552967277.69.0.646647509224.issue36356@roundup.psfhosted.org>
Message-ID: <1570465201.45.0.645657797843.issue36356@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:


New changeset 321def805abc5b7c92c7e90ca90cb2434fdab855 by Yury Selivanov (Ben Harper) in branch 'master':
bpo-36356: Fix memory leak in _asynciomodule.c (GH-16598)
https://github.com/python/cpython/commit/321def805abc5b7c92c7e90ca90cb2434fdab855


----------
nosy: +yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36356>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:20:12 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 16:20:12 +0000
Subject: [issue36356] Failure to build with address sanitizer
In-Reply-To: <1552967277.69.0.646647509224.issue36356@roundup.psfhosted.org>
Message-ID: <1570465212.79.0.509223700103.issue36356@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16209
pull_request: https://github.com/python/cpython/pull/16622

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36356>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:20:43 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 16:20:43 +0000
Subject: [issue38398] PyUnicode functions are not exported by python 2 in
 Ubuntu
In-Reply-To: <1570464598.55.0.274340335252.issue38398@roundup.psfhosted.org>
Message-ID: <1570465243.4.0.225402087012.issue38398@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> hasattr(ctypes.pythonapi, "PyUnicode_FromWideChar")

Python 2 has a surprising ABI. The function names depending on the Unicode implementation:

PyUnicodeUCS2_FromWideChar on Windows, PyUnicodeUCS4_FromWideChar on other platforms.

Enjoy the ugly https://github.com/python/cpython/blob/2.7/Include/unicodeobject.h

And say hello to the new compact Unicode strings, PEP 393, implemented in Python 3.3, which unified that!
https://www.python.org/dev/peps/pep-0393/

----------
nosy: +vstinner
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38398>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:24:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 16:24:26 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570465466.27.0.819591822491.issue38376@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16210
pull_request: https://github.com/python/cpython/pull/16623

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:29:07 2019
From: report at bugs.python.org (PyScripter)
Date: Mon, 07 Oct 2019 16:29:07 +0000
Subject: [issue38398] PyUnicode functions are not exported by python 2 in
 Ubuntu
In-Reply-To: <1570464598.55.0.274340335252.issue38398@roundup.psfhosted.org>
Message-ID: <1570465747.29.0.374906822242.issue38398@roundup.psfhosted.org>


PyScripter <pyscripter at gmail.com> added the comment:

To Victor:

Neither of PyUnicodeUCS2_FromWideChar or PyUnicodeUCS4_FromWideChar is exported.

>>> import ctypes
>>> hasattr(ctypes.pythonapi, "PyUnicode_FromWideChar")
>>> hasattr(ctypes.pythonapi, "PyUnicodeUSC4_FromWideChar")
>>> hasattr(ctypes.pythonapi, "PyUnicodeUSC2_FromWideChar")

all return false on Ubuntu.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38398>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:29:26 2019
From: report at bugs.python.org (retnikt)
Date: Mon, 07 Oct 2019 16:29:26 +0000
Subject: [issue38397] __init_subclass__ causes TypeError when used with more
 standard library metaclasses (such as EnumMeta)
In-Reply-To: <1570464400.89.0.0085195281122.issue38397@roundup.psfhosted.org>
Message-ID: <1570465766.34.0.401559715747.issue38397@roundup.psfhosted.org>


retnikt <retnikt at gmail.com> added the comment:

I can (and will) submit a PR for this, by the way.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38397>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:31:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 16:31:32 +0000
Subject: [issue38398] PyUnicode functions are not exported by python 2 in
 Ubuntu
In-Reply-To: <1570464598.55.0.274340335252.issue38398@roundup.psfhosted.org>
Message-ID: <1570465892.15.0.320187666123.issue38398@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

ctypes.pythonapi is kind of magic. I'm not sure if hasattr() is supposed to work on it. But that works for me:

$ python2
Python 2.7.16 (default, Apr 30 2019, 15:54:43) 
>>> import ctypes
>>> ctypes.pythonapi.PyUnicodeUCS4_FromWideChar
<_FuncPtr object at 0x7f1b9c155ef0>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38398>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:32:13 2019
From: report at bugs.python.org (PyScripter)
Date: Mon, 07 Oct 2019 16:32:13 +0000
Subject: [issue38398] PyUnicode functions are not exported by python 2 in
 Ubuntu
In-Reply-To: <1570464598.55.0.274340335252.issue38398@roundup.psfhosted.org>
Message-ID: <1570465933.78.0.184508007621.issue38398@roundup.psfhosted.org>


PyScripter <pyscripter at gmail.com> added the comment:

I meant PyUnicodeUCS4_FromWideChar PyUnicodeUCS2_FromWideChar.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38398>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:33:03 2019
From: report at bugs.python.org (PyScripter)
Date: Mon, 07 Oct 2019 16:33:03 +0000
Subject: [issue38398] PyUnicode functions are not exported by python 2 in
 Ubuntu
In-Reply-To: <1570464598.55.0.274340335252.issue38398@roundup.psfhosted.org>
Message-ID: <1570465983.62.0.867325300134.issue38398@roundup.psfhosted.org>


PyScripter <pyscripter at gmail.com> added the comment:

Is this on Ubuntu?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38398>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:33:43 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 16:33:43 +0000
Subject: [issue38398] PyUnicode functions are not exported by python 2 in
 Ubuntu
In-Reply-To: <1570464598.55.0.274340335252.issue38398@roundup.psfhosted.org>
Message-ID: <1570466023.61.0.309533615332.issue38398@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Is this on Ubuntu?

No, only Fedora. If the issue is specific to Ubuntu, report it to the Ubuntu bug tracker.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38398>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:36:31 2019
From: report at bugs.python.org (PyScripter)
Date: Mon, 07 Oct 2019 16:36:31 +0000
Subject: [issue38398] PyUnicode functions are not exported by python 2 in
 Ubuntu
In-Reply-To: <1570464598.55.0.274340335252.issue38398@roundup.psfhosted.org>
Message-ID: <1570466191.0.0.22134720563.issue38398@roundup.psfhosted.org>


PyScripter <pyscripter at gmail.com> added the comment:

>>> sys.version
'2.7.16 (default, Oct  7 2019, 17:16:30) \n[GCC 7.4.0]'
>>> ctypes.pythonapi.PyUnicodeUCS4_FromWideChar
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/ctypes/__init__.py", line 379, in __getattr__
    func = self.__getitem__(name)
  File "/usr/local/lib/python2.7/ctypes/__init__.py", line 384, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: python2.7: undefined symbol: PyUnicodeUCS4_FromWideChar
>>>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38398>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:38:04 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 16:38:04 +0000
Subject: [issue36356] Failure to build with address sanitizer
In-Reply-To: <1552967277.69.0.646647509224.issue36356@roundup.psfhosted.org>
Message-ID: <1570466283.99.0.0956640256543.issue36356@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 13915a3100608f011b29da2f3716c990f523b631 by Miss Islington (bot) in branch '3.8':
bpo-36356: Fix memory leak in _asynciomodule.c (GH-16598)
https://github.com/python/cpython/commit/13915a3100608f011b29da2f3716c990f523b631


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36356>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:42:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 16:42:03 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1570466523.86.0.0600958193708.issue36389@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 6876257eaabdb30f27ebcbd7d2557278ce2e5705 by Victor Stinner in branch 'master':
bpo-36389: _PyObject_CheckConsistency() available in release mode (GH-16612)
https://github.com/python/cpython/commit/6876257eaabdb30f27ebcbd7d2557278ce2e5705


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:42:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 16:42:03 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570466523.93.0.689182025332.issue38376@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 6876257eaabdb30f27ebcbd7d2557278ce2e5705 by Victor Stinner in branch 'master':
bpo-36389: _PyObject_CheckConsistency() available in release mode (GH-16612)
https://github.com/python/cpython/commit/6876257eaabdb30f27ebcbd7d2557278ce2e5705


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:46:05 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 16:46:05 +0000
Subject: [issue36356] Failure to build with address sanitizer
In-Reply-To: <1552967277.69.0.646647509224.issue36356@roundup.psfhosted.org>
Message-ID: <1570466765.17.0.827150251294.issue36356@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Can we close this issue, or is there a remaining known bug?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36356>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:51:31 2019
From: report at bugs.python.org (AwesomeCronk)
Date: Mon, 07 Oct 2019 16:51:31 +0000
Subject: [issue38399] Error message persists when reimporting library
Message-ID: <1570467091.43.0.986668758934.issue38399@roundup.psfhosted.org>


New submission from AwesomeCronk <awesomecronk at gmail.com>:

I am working on a hexdump library in Python 3.7.4.
Whenever an issue is triggered, the error message shows up. I can usually edit and correct the file(library), but when I reimport the library and rerun the function, it throws the same error on the same line number, even if the line was removed or commented out.

----------
components: Interpreter Core
files: pythonerror.png
messages: 354120
nosy: AwesomeCronk
priority: normal
severity: normal
status: open
title: Error message persists when reimporting library
type: behavior
versions: Python 3.7
Added file: https://bugs.python.org/file48645/pythonerror.png

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38399>
_______________________________________

From report at bugs.python.org  Mon Oct  7 12:58:59 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 07 Oct 2019 16:58:59 +0000
Subject: [issue38399] Error message persists when reimporting library
In-Reply-To: <1570467091.43.0.986668758934.issue38399@roundup.psfhosted.org>
Message-ID: <1570467539.06.0.149428216975.issue38399@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

I think this is due to str bytes concatenation error on line number 19. Editing and reimporting doesn't give you new code in repl. Try the changes in new repl after changing it in file. Python will just use unchanged code and will use line number 19 in traceback to show error which is different as file was edited.

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38399>
_______________________________________

From report at bugs.python.org  Mon Oct  7 13:14:46 2019
From: report at bugs.python.org (Brett Cannon)
Date: Mon, 07 Oct 2019 17:14:46 +0000
Subject: [issue26219] implement per-opcode cache in ceval
In-Reply-To: <1453918500.26.0.0886095278127.issue26219@psf.upfronthosting.co.za>
Message-ID: <1570468486.03.0.313843402226.issue26219@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

I personally think it would be fine to change the wording to say "measurable speed-up" and not attribute a specific number.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26219>
_______________________________________

From report at bugs.python.org  Mon Oct  7 13:23:48 2019
From: report at bugs.python.org (Ned Deily)
Date: Mon, 07 Oct 2019 17:23:48 +0000
Subject: [issue36356] Failure to build with address sanitizer
In-Reply-To: <1552967277.69.0.646647509224.issue36356@roundup.psfhosted.org>
Message-ID: <1570469028.87.0.688021246887.issue36356@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

FWIW, the assertion error on macOS reported above in msg338774 does not seem to occur anymore with current HEAD of master and with recent system clang (Apple clang version 11.0.0 (clang-1100.0.33.8)) on macOS 10.14.6.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36356>
_______________________________________

From report at bugs.python.org  Mon Oct  7 13:54:19 2019
From: report at bugs.python.org (Ethan Furman)
Date: Mon, 07 Oct 2019 17:54:19 +0000
Subject: [issue38375] Enum lookup fails for callable values
In-Reply-To: <1570276596.73.0.237929240562.issue38375@roundup.psfhosted.org>
Message-ID: <1570470859.31.0.86869722416.issue38375@roundup.psfhosted.org>


Ethan Furman <ethan at stoneleaf.us> added the comment:

This is the intended, and documented, behavior.

----------
assignee:  -> ethan.furman
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38375>
_______________________________________

From report at bugs.python.org  Mon Oct  7 13:58:48 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Mon, 07 Oct 2019 17:58:48 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570471128.54.0.21884254002.issue38379@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


----------
nosy: +nanjekyejoannah

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Mon Oct  7 14:04:19 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Mon, 07 Oct 2019 18:04:19 +0000
Subject: [issue38388] Pickle protocol v 5 needs to be documented
In-Reply-To: <1570405873.92.0.178526679084.issue38388@roundup.psfhosted.org>
Message-ID: <1570471459.35.0.593129144568.issue38388@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


----------
nosy: +nanjekyejoannah

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38388>
_______________________________________

From report at bugs.python.org  Mon Oct  7 14:40:51 2019
From: report at bugs.python.org (Isaac Turner)
Date: Mon, 07 Oct 2019 18:40:51 +0000
Subject: [issue37591] test_concurrent_future failed
In-Reply-To: <1563106770.47.0.449024295444.issue37591@roundup.psfhosted.org>
Message-ID: <1570473651.66.0.87731087606.issue37591@roundup.psfhosted.org>


Isaac Turner <turner.isaac at gmail.com> added the comment:

I'm seeing the same error on Ubuntu LTS 16.04.6 on an ARM64 platform.

$ make && make test

...

0:09:18 load avg: 2.09 [ 78/416] test_complex
0:09:20 load avg: 2.08 [ 79/416] test_concurrent_futures

Traceback:
 Thread 0x0000007f6ffff1f0 (most recent call first):
  File "/home/minit/Python-3.7.4/Lib/threading.py", line 296 in wait
  File "/home/minit/Python-3.7.4/Lib/multiprocessing/queues.py", line 224 in _feed
  File "/home/minit/Python-3.7.4/Lib/threading.py", line 870 in run
  File "/home/minit/Python-3.7.4/Lib/threading.py", line 926 in _bootstrap_inner
  File "/home/minit/Python-3.7.4/Lib/threading.py", line 890 in _bootstrap

Thread 0x0000007f93fff1f0 (most recent call first):
  File "/home/minit/Python-3.7.4/Lib/selectors.py", line 415 in select
  File "/home/minit/Python-3.7.4/Lib/multiprocessing/connection.py", line 920 in wait
  File "/home/minit/Python-3.7.4/Lib/concurrent/futures/process.py", line 361 in _queue_management_worker
  File "/home/minit/Python-3.7.4/Lib/threading.py", line 870 in run
  File "/home/minit/Python-3.7.4/Lib/threading.py", line 926 in _bootstrap_inner
  File "/home/minit/Python-3.7.4/Lib/threading.py", line 890 in _bootstrap

Current thread 0x0000007fa6296000 (most recent call first):
  File "/home/minit/Python-3.7.4/Lib/test/test_concurrent_futures.py", line 917 in _fail_on_deadlock
  File "/home/minit/Python-3.7.4/Lib/test/test_concurrent_futures.py", line 978 in test_crash
  File "/home/minit/Python-3.7.4/Lib/unittest/case.py", line 628 in run
  File "/home/minit/Python-3.7.4/Lib/unittest/case.py", line 676 in __call__
  File "/home/minit/Python-3.7.4/Lib/unittest/suite.py", line 122 in run
  File "/home/minit/Python-3.7.4/Lib/unittest/suite.py", line 84 in __call__
  File "/home/minit/Python-3.7.4/Lib/unittest/suite.py", line 122 in run
  File "/home/minit/Python-3.7.4/Lib/unittest/suite.py", line 84 in __call__
  File "/home/minit/Python-3.7.4/Lib/unittest/suite.py", line 122 in run
  File "/home/minit/Python-3.7.4/Lib/unittest/suite.py", line 84 in __call__
  File "/home/minit/Python-3.7.4/Lib/test/support/testresult.py", line 162 in run
  File "/home/minit/Python-3.7.4/Lib/test/support/__init__.py", line 1915 in _run_suite
  File "/home/minit/Python-3.7.4/Lib/test/support/__init__.py", line 2011 in run_unittest
  File "/home/minit/Python-3.7.4/Lib/test/test_concurrent_futures.py", line 1245 in test_main
  File "/home/minit/Python-3.7.4/Lib/test/support/__init__.py", line 2143 in decorator
  File "/home/minit/Python-3.7.4/Lib/test/libregrtest/runtest.py", line 228 in _runtest_inner2
  File "/home/minit/Python-3.7.4/Lib/test/libregrtest/runtest.py", line 264 in _runtest_inner
  File "/home/minit/Python-3.7.4/Lib/test/libregrtest/runtest.py", line 149 in _runtest
  File "/home/minit/Python-3.7.4/Lib/test/libregrtest/runtest.py", line 187 in runtest
  File "/home/minit/Python-3.7.4/Lib/test/libregrtest/main.py", line 390 in run_tests_sequential
  File "/home/minit/Python-3.7.4/Lib/test/libregrtest/main.py", line 488 in run_tests
  File "/home/minit/Python-3.7.4/Lib/test/libregrtest/main.py", line 642 in _main
  File "/home/minit/Python-3.7.4/Lib/test/libregrtest/main.py", line 588 in main
  File "/home/minit/Python-3.7.4/Lib/test/libregrtest/main.py", line 663 in main
  File "/home/minit/Python-3.7.4/Lib/test/regrtest.py", line 46 in _main
  File "/home/minit/Python-3.7.4/Lib/test/regrtest.py", line 50 in <module>
  File "/home/minit/Python-3.7.4/Lib/runpy.py", line 85 in _run_code
  File "/home/minit/Python-3.7.4/Lib/runpy.py", line 193 in _run_module_as_main

test test_concurrent_futures failed

----------
nosy: +Isaac Turner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37591>
_______________________________________

From report at bugs.python.org  Mon Oct  7 14:47:52 2019
From: report at bugs.python.org (Adam Williamson)
Date: Mon, 07 Oct 2019 18:47:52 +0000
Subject: [issue37951] Disallow fork in a subinterpreter broke subprocesses in
 mod_wsgi daemon mode
In-Reply-To: <1566808952.7.0.710040972846.issue37951@roundup.psfhosted.org>
Message-ID: <1570474072.5.0.443371081638.issue37951@roundup.psfhosted.org>


Adam Williamson <awilliam at redhat.com> added the comment:

Well, now our (Fedora QA's) automated testing of FreeIPA is showing what looks like a problem with preexec_fn (rather than fork) being disallowed:

https://bugzilla.redhat.com/show_bug.cgi?id=1759290

Login to the FreeIPA webUI is failing, and at the time it fails we see this error message on the server end:

[Mon Oct 07 09:22:19.521604 2019] [wsgi:error] [pid 32989:tid 139746234119936] [remote 10.0.2.102:56054] ipa: DEBUG: args=['/usr/bin/kinit', 'admin', '-c', '/run/ipa/ccaches/kinit_32989', '-E']
[Mon Oct 07 09:22:19.521996 2019] [wsgi:error] [pid 32989:tid 139746234119936] [remote 10.0.2.102:56054] ipa: DEBUG: Process execution failed
[Mon Oct 07 09:22:19.522189 2019] [wsgi:error] [pid 32989:tid 139746234119936] [remote 10.0.2.102:56054] ipa: INFO: 401 Unauthorized: preexec_fn not supported within subinterpreters

----------
nosy: +adamwill
status: pending -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37951>
_______________________________________

From report at bugs.python.org  Mon Oct  7 14:59:24 2019
From: report at bugs.python.org (Massimo)
Date: Mon, 07 Oct 2019 18:59:24 +0000
Subject: [issue38375] Enum lookup fails for callable values
In-Reply-To: <1570276596.73.0.237929240562.issue38375@roundup.psfhosted.org>
Message-ID: <1570474764.18.0.20037910271.issue38375@roundup.psfhosted.org>


Massimo <massimo at typish.io> added the comment:

Where is this documented? Sorry, I couldn't find it.

In any case, I'd say this behaviour is quite unexpected, and unless technical reasons are overwhelming, would be nice to change it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38375>
_______________________________________

From report at bugs.python.org  Mon Oct  7 15:07:31 2019
From: report at bugs.python.org (Daniel Debrunner)
Date: Mon, 07 Oct 2019 19:07:31 +0000
Subject: [issue36697] inspect.getclosurevars returns wrong globals dict
In-Reply-To: <1555922969.45.0.450842121898.issue36697@roundup.psfhosted.org>
Message-ID: <1570475251.34.0.527321620539.issue36697@roundup.psfhosted.org>


Daniel Debrunner <djd at debrunners.com> added the comment:

Another case:

model="Hello"
class M(object):
    def __init__(self):
        pass
    def __call__(self):
        print(self.model)

cvs = inspect.getclosurevars(M.__call__)

ClosureVars(nonlocals={}, globals={'model': 'Hello'}, builtins={'print': <built-in function print>}, unbound=set())

Of course self.model does not refer to the global model
M()()
AttributeError: 'M' object has no attribute 'model'

----------
nosy: +Daniel Debrunner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36697>
_______________________________________

From report at bugs.python.org  Mon Oct  7 15:12:19 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 19:12:19 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570475539.22.0.401305549717.issue38376@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 435b2eeb7bc5b8ec264e900b38bcb3d76552d777 by Victor Stinner in branch '3.8':
bpo-38376: Fix _PyUnicode_CheckConsistency() definition (GH-16623)
https://github.com/python/cpython/commit/435b2eeb7bc5b8ec264e900b38bcb3d76552d777


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Mon Oct  7 15:15:15 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Mon, 07 Oct 2019 19:15:15 +0000
Subject: [issue37951] Disallow fork in a subinterpreter broke subprocesses in
 mod_wsgi daemon mode
In-Reply-To: <1566808952.7.0.710040972846.issue37951@roundup.psfhosted.org>
Message-ID: <1570475715.42.0.836443658221.issue37951@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

preexec_fn is fundamentally unsupportable.

what code is using it, there should be a way not to rely on that.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37951>
_______________________________________

From report at bugs.python.org  Mon Oct  7 15:21:19 2019
From: report at bugs.python.org (Adam Williamson)
Date: Mon, 07 Oct 2019 19:21:19 +0000
Subject: [issue37951] Disallow fork in a subinterpreter broke subprocesses in
 mod_wsgi daemon mode
In-Reply-To: <1566808952.7.0.710040972846.issue37951@roundup.psfhosted.org>
Message-ID: <1570476079.24.0.764543844725.issue37951@roundup.psfhosted.org>


Adam Williamson <awilliam at redhat.com> added the comment:

It's this function:

https://github.com/freeipa/freeipa/blob/master/ipalib/install/kinit.py#L66

The function `run` is imported from `ipapython.ipautil`, it's defined here:

https://github.com/freeipa/freeipa/blob/master/ipapython/ipautil.py#L391

all of this is being run inside a WSGI.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37951>
_______________________________________

From report at bugs.python.org  Mon Oct  7 15:34:50 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Mon, 07 Oct 2019 19:34:50 +0000
Subject: [issue38396] ast.literal_eval doesn't give information about node
 except the type of it
In-Reply-To: <1570463756.86.0.131436803473.issue38396@roundup.psfhosted.org>
Message-ID: <1570476890.88.0.759531475652.issue38396@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

The downside however is that exception messages can become very long. So I am not sure we should change this.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38396>
_______________________________________

From report at bugs.python.org  Mon Oct  7 15:47:55 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 19:47:55 +0000
Subject: [issue38396] ast.literal_eval doesn't give information about node
 except the type of it
In-Reply-To: <1570463756.86.0.131436803473.issue38396@roundup.psfhosted.org>
Message-ID: <1570477675.67.0.212235447471.issue38396@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I have same doubts.

See also issue32888.

----------
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> Improve exception message in ast.literal_eval

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38396>
_______________________________________

From report at bugs.python.org  Mon Oct  7 15:50:44 2019
From: report at bugs.python.org (Eric Meyer)
Date: Mon, 07 Oct 2019 19:50:44 +0000
Subject: [issue32879] Race condition in multiprocessing Queue
In-Reply-To: <1519091702.0.0.467229070634.issue32879@psf.upfronthosting.co.za>
Message-ID: <1570477844.92.0.159873146509.issue32879@roundup.psfhosted.org>


Eric Meyer <ericallenmeyer at gmail.com> added the comment:

multiprocessing.SimpleQueue is another workaround to this issue.

I agree the docs should be clearer about this. Additionally, it would be helpful if there was a way to optionally put an item on a multiprocessing.Queue and block until the item has been written to the pipe (or block until it is safe to mutate,garbage collect,etc the item in the calling thread).

----------
nosy: +highvelcty

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32879>
_______________________________________

From report at bugs.python.org  Mon Oct  7 15:55:39 2019
From: report at bugs.python.org (Christian Heimes)
Date: Mon, 07 Oct 2019 19:55:39 +0000
Subject: [issue37951] Disallow fork in a subinterpreter broke subprocesses in
 mod_wsgi daemon mode
In-Reply-To: <1566808952.7.0.710040972846.issue37951@roundup.psfhosted.org>
Message-ID: <1570478139.04.0.280222280586.issue37951@roundup.psfhosted.org>


Christian Heimes <lists at cheimes.de> added the comment:

I'll address the issue in FreeIPA.

The ipautil.run() function is a helper around subprocess.Popen. The function always installs a preexec_fn in case it needs to change umask or drop priviliges. The WSGI server does not need these features.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37951>
_______________________________________

From report at bugs.python.org  Mon Oct  7 15:57:16 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 19:57:16 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1570478236.66.0.861295044188.issue36389@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16211
pull_request: https://github.com/python/cpython/pull/16624

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Mon Oct  7 16:01:21 2019
From: report at bugs.python.org (Christian Heimes)
Date: Mon, 07 Oct 2019 20:01:21 +0000
Subject: [issue37951] Disallow fork in a subinterpreter broke subprocesses in
 mod_wsgi daemon mode
In-Reply-To: <1566808952.7.0.710040972846.issue37951@roundup.psfhosted.org>
Message-ID: <1570478481.38.0.231052632613.issue37951@roundup.psfhosted.org>


Christian Heimes <lists at cheimes.de> added the comment:

https://github.com/freeipa/freeipa/pull/3769 should address the issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37951>
_______________________________________

From report at bugs.python.org  Mon Oct  7 16:28:18 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Mon, 07 Oct 2019 20:28:18 +0000
Subject: [issue36953] Remove collections ABCs?
In-Reply-To: <1558140764.46.0.049733618419.issue36953@roundup.psfhosted.org>
Message-ID: <1570480098.06.0.456892792409.issue36953@roundup.psfhosted.org>


Emmanuel Arias <emmanuelarias30 at gmail.com> added the comment:

Now was remove from 3.7

https://github.com/python/cpython/commit/ef092fe9905f61ca27889092ca1248a11aa74498

This issue should be closed, isn't?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36953>
_______________________________________

From report at bugs.python.org  Mon Oct  7 16:31:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 20:31:46 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1570480306.37.0.972100614483.issue36389@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 60ec6efd96d95476fe5e38c491491add04f026e5 by Victor Stinner in branch 'master':
bpo-36389: Fix _PyBytesWriter in release mode (GH-16624)
https://github.com/python/cpython/commit/60ec6efd96d95476fe5e38c491491add04f026e5


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Mon Oct  7 16:34:50 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 20:34:50 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570480490.43.0.135607332403.issue38376@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I pushed one more fix in https://bugs.python.org/issue36389#msg354138

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Mon Oct  7 16:39:08 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 20:39:08 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1570480748.61.0.765475661192.issue38376@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

After pushing some fixes to 3.8 and master branches, I tested the following commands in 3.7, 3.8 and master branches:

make distclean
./configure --prefix=$HOME/.local --with-assertions
make
./python -m test -j0 test_bytes test_gc test_capi

These commands now work in the 3 branches. I close the issue.

Thanks Vinay Sajip for the bug report! Thanks T. Wouters for previous fixes.

@T. Wouters: I took the liberty of closing your PR 16594 in favor of my PR 16623. I may backport PR 16612 enhancements to 3.8 later, but not jus before a 3.8.0 final release to no stress our release manager ;-)

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Mon Oct  7 16:54:41 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2019 20:54:41 +0000
Subject: [issue38294] Documentation on 3.6->3.7 re.escape no longer escaping
 "/" or ":" should be obvious
In-Reply-To: <1569603997.59.0.0237297108404.issue38294@roundup.psfhosted.org>
Message-ID: <1570481681.81.0.87939079294.issue38294@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 15ae75d660befe643ed42eb2707a557cea97256c by Serhiy Storchaka (Ricardo B?nffy) in branch 'master':
bpo-38294: Add list of no-longer-escaped chars to re.escape documentation. (GH-16442)
https://github.com/python/cpython/commit/15ae75d660befe643ed42eb2707a557cea97256c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38294>
_______________________________________

From report at bugs.python.org  Mon Oct  7 17:00:58 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 21:00:58 +0000
Subject: [issue38294] Documentation on 3.6->3.7 re.escape no longer escaping
 "/" or ":" should be obvious
In-Reply-To: <1569603997.59.0.0237297108404.issue38294@roundup.psfhosted.org>
Message-ID: <1570482058.38.0.250284399986.issue38294@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16212
pull_request: https://github.com/python/cpython/pull/16626

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38294>
_______________________________________

From report at bugs.python.org  Mon Oct  7 17:07:23 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 07 Oct 2019 21:07:23 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1570482443.24.0.731238074995.issue38344@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset e310af9e2941c2fbb7370e003276cc37eb230f16 by Steve Dower (James Abel) in branch 'master':
bpo-38344: Fix syntax in activate.bat (GH-16533)
https://github.com/python/cpython/commit/e310af9e2941c2fbb7370e003276cc37eb230f16


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Mon Oct  7 17:07:36 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 21:07:36 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1570482456.16.0.608306041213.issue38344@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16213
pull_request: https://github.com/python/cpython/pull/16627

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Mon Oct  7 17:07:49 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 21:07:49 +0000
Subject: [issue38294] Documentation on 3.6->3.7 re.escape no longer escaping
 "/" or ":" should be obvious
In-Reply-To: <1569603997.59.0.0237297108404.issue38294@roundup.psfhosted.org>
Message-ID: <1570482469.47.0.824690976522.issue38294@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset b731fc521cf78e53268e35777d836ca80e7ab305 by Miss Islington (bot) in branch '3.8':
bpo-38294: Add list of no-longer-escaped chars to re.escape documentation. (GH-16442)
https://github.com/python/cpython/commit/b731fc521cf78e53268e35777d836ca80e7ab305


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38294>
_______________________________________

From report at bugs.python.org  Mon Oct  7 17:08:36 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 21:08:36 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1570482516.92.0.687860646132.issue38344@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16214
pull_request: https://github.com/python/cpython/pull/16628

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Mon Oct  7 17:10:14 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 07 Oct 2019 21:10:14 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1570482614.96.0.0898615528729.issue38344@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

I've merged the fix so that it can be cherry-picked for the upcoming releases.

I'd still like to see the tests enhanced to be able to detect error output in the scripts, but those don't need to necessarily make it into the upcoming releases.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Mon Oct  7 17:18:36 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 21:18:36 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1570483116.22.0.339997869857.issue36389@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16215
pull_request: https://github.com/python/cpython/pull/16629

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Mon Oct  7 17:25:09 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 21:25:09 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1570483509.8.0.514230920735.issue38344@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset bfb5f9a66cc348c9cf25c857ad9910479e587517 by Miss Islington (bot) in branch '3.7':
bpo-38344: Fix syntax in activate.bat (GH-16533)
https://github.com/python/cpython/commit/bfb5f9a66cc348c9cf25c857ad9910479e587517


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Mon Oct  7 17:27:00 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 07 Oct 2019 21:27:00 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1570483620.43.0.517958930077.issue38344@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 4880e5a1b66d9175fcc402cb0288bc1898356831 by Miss Islington (bot) in branch '3.8':
bpo-38344: Fix syntax in activate.bat (GH-16533)
https://github.com/python/cpython/commit/4880e5a1b66d9175fcc402cb0288bc1898356831


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Mon Oct  7 17:44:08 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 21:44:08 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1570484648.33.0.0788344647986.issue36389@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 7775349895088a7ae68cecf0c74cf817f15e2c74 by Victor Stinner in branch 'master':
bpo-36389: Add newline to _PyObject_AssertFailed() (GH-16629)
https://github.com/python/cpython/commit/7775349895088a7ae68cecf0c74cf817f15e2c74


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Mon Oct  7 18:09:34 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 22:09:34 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570486174.42.0.56993669901.issue38392@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 1b1845569539db5c1a6948a5d32daea381f1e35f by Victor Stinner in branch 'master':
bpo-38392: PyObject_GC_Track() validates object in debug mode (GH-16615)
https://github.com/python/cpython/commit/1b1845569539db5c1a6948a5d32daea381f1e35f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Mon Oct  7 18:26:18 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 22:26:18 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570487178.54.0.341230502255.issue38392@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Ok, I pushed a change. Let's see how third party projects like it :-) We still have time to revert it if it causes too many damage.

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Mon Oct  7 18:49:49 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Mon, 07 Oct 2019 22:49:49 +0000
Subject: [issue38399] Error message persists when reimporting library
In-Reply-To: <1570467091.43.0.986668758934.issue38399@roundup.psfhosted.org>
Message-ID: <1570488589.31.0.557810266872.issue38399@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Importing the second and subsequent times reloads the module from the system cache. Instead, you can:

- run ``del sys.modules['hexdump']`` and then ``import hexdump``;

- call ``importlib.reload(hexdump)``; or

- restart the REPL.

Remember that reloading the module won't redefine any existing classes or instances you created from the old module, they will continue to reference the old module code until they are destroyed and recreated. So the last option (restarting the REPL) is usually the most effective. But with care, reload(hexdump) should do the trick.

----------
nosy: +steven.daprano
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38399>
_______________________________________

From report at bugs.python.org  Mon Oct  7 19:01:37 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 07 Oct 2019 23:01:37 +0000
Subject: [issue38400] Python segfaults when configured with --with-pydebug
 --with-trace-refs
Message-ID: <1570489297.7.0.2347429078.issue38400@roundup.psfhosted.org>


New submission from Pablo Galindo Salgado <pablogsal at gmail.com>:

configure --with-pydebug --with-trace-refs && make

Modules/gcmodule.c:378: visit_decref: Assertion "!_PyObject_IsFreed(op)" failed
<object at 0x5557629ca260 is freed>
Fatal Python error: _PyObject_AssertFailed
Python runtime state: preinitialized

Current thread 0x00007f6e2863e740 (most recent call first):
<no Python frame>
/bin/sh: line 5: 28078 Aborted                 (core dumped) ./python -E -S -m sysconfig --generate-posix-vars
generate-posix-vars failed
make: * [Makefile:592: pybuilddir.txt] Error 1

----------
components: Interpreter Core
messages: 354151
nosy: pablogsal, vstinner
priority: normal
severity: normal
status: open
title: Python segfaults when configured with --with-pydebug --with-trace-refs
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38400>
_______________________________________

From report at bugs.python.org  Mon Oct  7 19:01:53 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 07 Oct 2019 23:01:53 +0000
Subject: [issue38400] Python segfaults when configured with --with-pydebug
 --with-trace-refs
In-Reply-To: <1570489297.7.0.2347429078.issue38400@roundup.psfhosted.org>
Message-ID: <1570489313.83.0.707786642982.issue38400@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

This is a regression introduced by:

commit 6876257eaabdb30f27ebcbd7d2557278ce2e5705
Author: Victor Stinner <vstinner at python.org>
Date:   Mon Oct 7 18:42:01 2019 +0200

    bpo-36389: _PyObject_CheckConsistency() available in release mode (GH-16612)
    
    bpo-36389, bpo-38376: The _PyObject_CheckConsistency() function is
    now also available in release mode. For example, it can be used to
    debug a crash in the visit_decref() function of the GC.
    
    Modify the following functions to also work in release mode:
    
    * _PyDict_CheckConsistency()
    * _PyObject_CheckConsistency()
    * _PyType_CheckConsistency()
    * _PyUnicode_CheckConsistency()
    
    Other changes:
    
    * _PyMem_IsPtrFreed(ptr) now also returns 1 if ptr is NULL
      (equals to 0).
    * _PyBytesWriter_CheckConsistency() now returns 1 and is only used
      with assert().
    * Reorder _PyObject_Dump() to write safe fields first, and only
      attempt to render repr() at the end.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38400>
_______________________________________

From report at bugs.python.org  Mon Oct  7 19:21:09 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 07 Oct 2019 23:21:09 +0000
Subject: [issue38400] Python segfaults when configured with --with-pydebug
 --with-trace-refs
In-Reply-To: <1570489297.7.0.2347429078.issue38400@roundup.psfhosted.org>
Message-ID: <1570490469.36.0.444603800523.issue38400@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +patch
pull_requests: +16216
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16630

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38400>
_______________________________________

From report at bugs.python.org  Mon Oct  7 19:43:17 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 07 Oct 2019 23:43:17 +0000
Subject: [issue38400] Python segfaults when configured with --with-pydebug
 --with-trace-refs
In-Reply-To: <1570489297.7.0.2347429078.issue38400@roundup.psfhosted.org>
Message-ID: <1570491797.87.0.598328349212.issue38400@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 36e33c360ed7716a2b5ab2b53210da81f8ce1295 by Pablo Galindo in branch 'master':
bpo-38400 Don't check for NULL linked list pointers in _PyObject_IsFreed (GH-16630)
https://github.com/python/cpython/commit/36e33c360ed7716a2b5ab2b53210da81f8ce1295


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38400>
_______________________________________

From report at bugs.python.org  Mon Oct  7 19:43:22 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 07 Oct 2019 23:43:22 +0000
Subject: [issue38400] Python segfaults when configured with --with-pydebug
 --with-trace-refs
In-Reply-To: <1570489297.7.0.2347429078.issue38400@roundup.psfhosted.org>
Message-ID: <1570491802.41.0.640735094957.issue38400@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38400>
_______________________________________

From report at bugs.python.org  Mon Oct  7 19:53:15 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 07 Oct 2019 23:53:15 +0000
Subject: [issue38070] visit_decref(): add an assertion to check that the
 object is not freed
In-Reply-To: <1568037936.88.0.10373402622.issue38070@roundup.psfhosted.org>
Message-ID: <1570492395.58.0.112366417858.issue38070@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16217
pull_request: https://github.com/python/cpython/pull/16631

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38070>
_______________________________________

From report at bugs.python.org  Mon Oct  7 20:23:44 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 00:23:44 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570494224.12.0.98432232832.issue38395@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +patch
pull_requests: +16218
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16632

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Mon Oct  7 20:24:53 2019
From: report at bugs.python.org (John Parejko)
Date: Tue, 08 Oct 2019 00:24:53 +0000
Subject: [issue38401] Make dataclass attribute docstrings accessible
Message-ID: <1570494293.05.0.934356434949.issue38401@roundup.psfhosted.org>


New submission from John Parejko <parejkoj at uw.edu>:

Dataclasses provide a very straightforward way to specify structured data. One can trivally document a dataclass's attributes via triple-quoted attribute docstrings per PEP 257. However, those docstrings are not accessible to pydoc, so they are lost to users of the dataclass.

For example, the attribute docstrings in the below dataclass should be available when looking at `help(SpectralData)`, but that help command does not show the docstrings.

```
@dataclasses.dataclass
class SpectralData:
    """Class to hold data and metadata from a fiber spectrograph."""
    wavelength: astropy.units.Quantity
    """The wavelength array produced by the instrument."""
    spectrum: np.ndarray
    """The flux array in instrumental units."""
    duration: float
    """The duration of the exposure in seconds."""
```

----------
assignee: docs at python
components: Documentation
messages: 354154
nosy: John Parejko2, docs at python
priority: normal
severity: normal
status: open
title: Make dataclass attribute docstrings accessible
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38401>
_______________________________________

From report at bugs.python.org  Mon Oct  7 20:26:53 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 00:26:53 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570494413.9.0.931882924401.issue38395@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
versions: +Python 3.7, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Mon Oct  7 20:33:14 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 00:33:14 +0000
Subject: [issue27542] Segfault in gcmodule.c:360 visit_decref
In-Reply-To: <1468755086.8.0.27245311458.issue27542@psf.upfronthosting.co.za>
Message-ID: <1570494794.96.0.246947296025.issue27542@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Julien: I'm working on enhancement of debug traces on visit_decref(). Are you still able to reproduce the crash in 2019?

I failed to reproduce the bug in a virtual environment with:

* Python 2.7.14
* pip 8.1.2
* cffi 1.7.0

$ virtualenv -p python2 venv
Running virtualenv with interpreter /usr/bin/python2
New python executable in /home/haypo/venv/bin/python2
Also creating executable in /home/haypo/venv/bin/python
Installing setuptools, pkg_resources, pip, wheel...done.

$ venv/bin/python -m pip install pip==8.1.2
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Collecting pip==8.1.2
  Using cached https://files.pythonhosted.org/packages/9c/32/004ce0852e0a127f07f358b715015763273799bd798956fa930814b60f39/pip-8.1.2-py2.py3-none-any.whl
Installing collected packages: pip
  Found existing installation: pip 19.2.3
    Uninstalling pip-19.2.3:
      Successfully uninstalled pip-19.2.3
Successfully installed pip-8.1.2

$ venv/bin/python -m pip install cffi==1.7.0
Collecting cffi==1.7.0
  Using cached https://files.pythonhosted.org/packages/46/26/2413bf923b1de47d9e9cf48f248dec1a16027a7773452315f34746253c35/cffi-1.7.0-cp27-cp27mu-manylinux1_x86_64.whl
Collecting pycparser (from cffi==1.7.0)
Installing collected packages: pycparser, cffi
Successfully installed cffi-1.7.0 pycparser-2.19
You are using pip version 8.1.2, however version 19.2.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27542>
_______________________________________

From report at bugs.python.org  Mon Oct  7 20:35:11 2019
From: report at bugs.python.org (Kubilay Kocak)
Date: Tue, 08 Oct 2019 00:35:11 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1570494911.2.0.776761129182.issue37531@roundup.psfhosted.org>


Change by Kubilay Kocak <koobs.freebsd at gmail.com>:


----------
nosy: +koobs

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Mon Oct  7 20:35:20 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 00:35:20 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570494920.61.0.567927260015.issue38395@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
versions: +Python 2.7, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Mon Oct  7 20:36:12 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 00:36:12 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570494972.87.0.0455789715201.issue38395@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy: +benjamin.peterson, lukasz.langa, ned.deily
priority: normal -> release blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Mon Oct  7 20:37:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 00:37:42 +0000
Subject: [issue38070] visit_decref(): add an assertion to check that the
 object is not freed
In-Reply-To: <1568037936.88.0.10373402622.issue38070@roundup.psfhosted.org>
Message-ID: <1570495062.54.0.716202594374.issue38070@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 4d5f94b8cd20f804c7868c5395a15aa6032f874c by Victor Stinner in branch 'master':
bpo-38070: Enhance visit_decref() debug trace (GH-16631)
https://github.com/python/cpython/commit/4d5f94b8cd20f804c7868c5395a15aa6032f874c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38070>
_______________________________________

From report at bugs.python.org  Mon Oct  7 20:38:56 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 00:38:56 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570495136.46.0.540085270118.issue38395@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I'm marking this as release blocker for the 3.8 incoming release so we don't forget about fixing this.

----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Mon Oct  7 20:42:49 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 08 Oct 2019 00:42:49 +0000
Subject: [issue38388] Pickle protocol v 5 needs to be documented
In-Reply-To: <1570405873.92.0.178526679084.issue38388@roundup.psfhosted.org>
Message-ID: <1570495369.88.0.480998011115.issue38388@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +pitrou

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38388>
_______________________________________

From report at bugs.python.org  Mon Oct  7 21:42:35 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Tue, 08 Oct 2019 01:42:35 +0000
Subject: [issue37664] Update bundled pip and setuptools
In-Reply-To: <1563918687.03.0.591223674737.issue37664@roundup.psfhosted.org>
Message-ID: <1570498955.14.0.869057122699.issue37664@roundup.psfhosted.org>


Change by Benjamin Peterson <benjamin at python.org>:


----------
pull_requests: +16219
pull_request: https://github.com/python/cpython/pull/16633

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37664>
_______________________________________

From report at bugs.python.org  Mon Oct  7 21:54:08 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Tue, 08 Oct 2019 01:54:08 +0000
Subject: [issue37664] Update bundled pip and setuptools
In-Reply-To: <1563918687.03.0.591223674737.issue37664@roundup.psfhosted.org>
Message-ID: <1570499648.76.0.748793935956.issue37664@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset e7e58fe03175adc660c192e724b91ae7ccba9cb6 by Benjamin Peterson in branch '2.7':
[2.7] bpo-37664: Update ensurepip bundled wheels, again (GH-16633)
https://github.com/python/cpython/commit/e7e58fe03175adc660c192e724b91ae7ccba9cb6


----------
nosy: +benjamin.peterson

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37664>
_______________________________________

From report at bugs.python.org  Mon Oct  7 22:00:05 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Tue, 08 Oct 2019 02:00:05 +0000
Subject: [issue36274] http.client cannot send non-ASCII request lines
In-Reply-To: <1552422803.93.0.420596825145.issue36274@roundup.psfhosted.org>
Message-ID: <1570500005.19.0.149889623864.issue36274@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset f5b1abbb3b0083381925dcd5898ae6d019224826 by Benjamin Peterson (Jason R. Coombs) in branch '2.7':
[2.7] bpo-38216, bpo-36274: Allow subclasses to separately override validation and encoding behavior (GH-16476)
https://github.com/python/cpython/commit/f5b1abbb3b0083381925dcd5898ae6d019224826


----------
nosy: +benjamin.peterson

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36274>
_______________________________________

From report at bugs.python.org  Mon Oct  7 22:00:05 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Tue, 08 Oct 2019 02:00:05 +0000
Subject: [issue38216] Fix for issue30458 (HTTP Header Injection) prevents
 crafting invalid requests
In-Reply-To: <1568823270.72.0.1365123921.issue38216@roundup.psfhosted.org>
Message-ID: <1570500005.03.0.19896145954.issue38216@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset f5b1abbb3b0083381925dcd5898ae6d019224826 by Benjamin Peterson (Jason R. Coombs) in branch '2.7':
[2.7] bpo-38216, bpo-36274: Allow subclasses to separately override validation and encoding behavior (GH-16476)
https://github.com/python/cpython/commit/f5b1abbb3b0083381925dcd5898ae6d019224826


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38216>
_______________________________________

From report at bugs.python.org  Mon Oct  7 22:05:29 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Tue, 08 Oct 2019 02:05:29 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570500329.85.0.321840069257.issue38395@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:

Note I'm going to ignore this for the purposes of 2.7.17 because it doesn't look like a new regression.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Mon Oct  7 23:38:40 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 03:38:40 +0000
Subject: [issue31589] Links for French documentation PDF is broken: LaTeX
 issue with non-ASCII characters?
In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za>
Message-ID: <1570505920.17.0.0171154459807.issue31589@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16220
pull_request: https://github.com/python/cpython/pull/16636

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31589>
_______________________________________

From report at bugs.python.org  Mon Oct  7 23:38:40 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 03:38:40 +0000
Subject: [issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15
In-Reply-To: <1512228356.9.0.213398074469.issue32200@psf.upfronthosting.co.za>
Message-ID: <1570505920.3.0.598009074707.issue32200@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16221
pull_request: https://github.com/python/cpython/pull/16636

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32200>
_______________________________________

From report at bugs.python.org  Mon Oct  7 23:39:40 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 03:39:40 +0000
Subject: [issue35036] logger failure in suspicious.py
In-Reply-To: <1540105005.86.0.788709270274.issue35036@psf.upfronthosting.co.za>
Message-ID: <1570505980.85.0.76069526547.issue35036@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16222
pull_request: https://github.com/python/cpython/pull/16637

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35036>
_______________________________________

From report at bugs.python.org  Mon Oct  7 23:41:04 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 08 Oct 2019 03:41:04 +0000
Subject: [issue38401] Make dataclass attribute docstrings accessible
In-Reply-To: <1570494293.05.0.934356434949.issue38401@roundup.psfhosted.org>
Message-ID: <1570506064.51.0.815366155639.issue38401@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38401>
_______________________________________

From report at bugs.python.org  Mon Oct  7 23:42:55 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 03:42:55 +0000
Subject: [issue31589] Links for French documentation PDF is broken: LaTeX
 issue with non-ASCII characters?
In-Reply-To: <1506416349.22.0.925737411431.issue31589@psf.upfronthosting.co.za>
Message-ID: <1570506175.3.0.369945825776.issue31589@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset d9b321692b6770c0fe7cb7ba05f9bd5c6082a880 by Miss Islington (bot) in branch '2.7':
bpo-31589 : Build PDF using xelatex for better UTF8 support. (GH-3940)
https://github.com/python/cpython/commit/d9b321692b6770c0fe7cb7ba05f9bd5c6082a880


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31589>
_______________________________________

From report at bugs.python.org  Mon Oct  7 23:42:55 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 03:42:55 +0000
Subject: [issue32200] Full docs build of 3.6 and 3.7 failing since 2017-10-15
In-Reply-To: <1512228356.9.0.213398074469.issue32200@psf.upfronthosting.co.za>
Message-ID: <1570506175.43.0.618521516389.issue32200@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset d9b321692b6770c0fe7cb7ba05f9bd5c6082a880 by Miss Islington (bot) in branch '2.7':
bpo-31589 : Build PDF using xelatex for better UTF8 support. (GH-3940)
https://github.com/python/cpython/commit/d9b321692b6770c0fe7cb7ba05f9bd5c6082a880


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32200>
_______________________________________

From report at bugs.python.org  Mon Oct  7 23:43:56 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 03:43:56 +0000
Subject: [issue35036] logger failure in suspicious.py
In-Reply-To: <1540105005.86.0.788709270274.issue35036@psf.upfronthosting.co.za>
Message-ID: <1570506236.28.0.732395464328.issue35036@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset e78d79c15cc53bdf8161d41c627cbfb551d8ee96 by Miss Islington (bot) in branch '2.7':
bpo-35036: Remove empty log line in the suspicious.py tool (GH-10024)
https://github.com/python/cpython/commit/e78d79c15cc53bdf8161d41c627cbfb551d8ee96


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35036>
_______________________________________

From report at bugs.python.org  Mon Oct  7 23:46:48 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Tue, 08 Oct 2019 03:46:48 +0000
Subject: [issue31036] building the python docs requires the blurb module
In-Reply-To: <1500995634.2.0.614160562868.issue31036@psf.upfronthosting.co.za>
Message-ID: <1570506408.46.0.378884869679.issue31036@roundup.psfhosted.org>


Change by Benjamin Peterson <benjamin at python.org>:


----------
pull_requests: +16223
pull_request: https://github.com/python/cpython/pull/16638

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31036>
_______________________________________

From report at bugs.python.org  Mon Oct  7 23:57:08 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Tue, 08 Oct 2019 03:57:08 +0000
Subject: [issue31036] building the python docs requires the blurb module
In-Reply-To: <1500995634.2.0.614160562868.issue31036@psf.upfronthosting.co.za>
Message-ID: <1570507028.73.0.212365018335.issue31036@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset 0bd59d655280ad4c4aff2d327789815b89caee18 by Benjamin Peterson in branch '2.7':
[2.7] bpo-31036: Allow sphinx and blurb to be found automatically (GH-16638)
https://github.com/python/cpython/commit/0bd59d655280ad4c4aff2d327789815b89caee18


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31036>
_______________________________________

From report at bugs.python.org  Tue Oct  8 00:01:58 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Tue, 08 Oct 2019 04:01:58 +0000
Subject: [issue38402] crypt: check error from library call
Message-ID: <1570507318.72.0.325157356882.issue38402@roundup.psfhosted.org>


New submission from Benjamin Peterson <benjamin at python.org>:

(split off from #36161)

The crypt module currently doesn't check for errors from crypt or crypt_r. It should.

----------
messages: 354166
nosy: benjamin.peterson
priority: normal
severity: normal
status: open
title: crypt: check error from library call
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38402>
_______________________________________

From report at bugs.python.org  Tue Oct  8 00:02:41 2019
From: report at bugs.python.org (Antonio Gutierrez)
Date: Tue, 08 Oct 2019 04:02:41 +0000
Subject: [issue38402] crypt: check error from library call
In-Reply-To: <1570507318.72.0.325157356882.issue38402@roundup.psfhosted.org>
Message-ID: <1570507361.49.0.073340342777.issue38402@roundup.psfhosted.org>


Change by Antonio Gutierrez <chibby0ne at gmail.com>:


----------
keywords: +patch
pull_requests: +16224
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16599

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38402>
_______________________________________

From report at bugs.python.org  Tue Oct  8 00:21:41 2019
From: report at bugs.python.org (Steve Dower)
Date: Tue, 08 Oct 2019 04:21:41 +0000
Subject: [issue38403] nuspec iconUrl field is deprecated
Message-ID: <1570508501.54.0.80221217734.issue38403@roundup.psfhosted.org>


New submission from Steve Dower <steve.dower at python.org>:

The iconUrl field has to be replaced with an icon field, and we need to include the file in the package now.

Details at https://docs.microsoft.com/en-us/nuget/reference/nuspec#icon

----------
assignee: steve.dower
components: Windows
messages: 354167
nosy: paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title: nuspec iconUrl field is deprecated
type: behavior
versions: Python 2.7, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38403>
_______________________________________

From report at bugs.python.org  Tue Oct  8 00:22:22 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Tue, 08 Oct 2019 04:22:22 +0000
Subject: [issue38402] crypt: check error from library call
In-Reply-To: <1570507318.72.0.325157356882.issue38402@roundup.psfhosted.org>
Message-ID: <1570508542.16.0.363685603243.issue38402@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset 0d3fe8ae4961bf551e7d5e42559e2ede1a08fd7c by Benjamin Peterson (Antonio Gutierrez) in branch 'master':
closes bpo-38402: Check error of primitive crypt/crypt_r. (GH-16599)
https://github.com/python/cpython/commit/0d3fe8ae4961bf551e7d5e42559e2ede1a08fd7c


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38402>
_______________________________________

From report at bugs.python.org  Tue Oct  8 00:44:33 2019
From: report at bugs.python.org (Poker Online Jakarta)
Date: Tue, 08 Oct 2019 04:44:33 +0000
Subject: [issue38404] Poker Online
Message-ID: <1570509873.23.0.248422964885.issue38404@roundup.psfhosted.org>


New submission from Poker Online Jakarta <jayadiliuss at gmail.com>:

<a href="https://www.jakartapoker.net/">poker online</a>

[url=https://www.jakartapoker.net/]poker online[/url]

----------
components: Argument Clinic
messages: 354169
nosy: larry, pokeronlinejakarta
priority: normal
severity: normal
status: open
title: Poker Online
type: crash
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38404>
_______________________________________

From report at bugs.python.org  Tue Oct  8 00:46:00 2019
From: report at bugs.python.org (Poker Online Jakarta)
Date: Tue, 08 Oct 2019 04:46:00 +0000
Subject: [issue38404] Poker Online
In-Reply-To: <1570509873.23.0.248422964885.issue38404@roundup.psfhosted.org>
Message-ID: <1570509960.93.0.565237354328.issue38404@roundup.psfhosted.org>


Poker Online Jakarta <jayadiliuss at gmail.com> added the comment:

Situs https://www.jakartapoker.net/ adalah situs judi poker online terpercaya dan terbaik di Indonesia

----------
Added file: https://bugs.python.org/file48646/2.jpg

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38404>
_______________________________________

From report at bugs.python.org  Tue Oct  8 01:11:41 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 08 Oct 2019 05:11:41 +0000
Subject: [issue38404] Poker Online
In-Reply-To: <1570509873.23.0.248422964885.issue38404@roundup.psfhosted.org>
Message-ID: <1570511501.84.0.0597178267211.issue38404@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


Removed file: https://bugs.python.org/file48646/2.jpg

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38404>
_______________________________________

From report at bugs.python.org  Tue Oct  8 01:12:02 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 08 Oct 2019 05:12:02 +0000
Subject: [issue38404] Poker Online
In-Reply-To: <1570509873.23.0.248422964885.issue38404@roundup.psfhosted.org>
Message-ID: <1570511522.62.0.351381803838.issue38404@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
Removed message: https://bugs.python.org/msg354170

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38404>
_______________________________________

From report at bugs.python.org  Tue Oct  8 01:12:13 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 08 Oct 2019 05:12:13 +0000
Subject: [issue38404] Poker Online
Message-ID: <1570511533.31.0.727110168001.issue38404@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
Removed message: https://bugs.python.org/msg354169

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38404>
_______________________________________

From report at bugs.python.org  Tue Oct  8 01:13:17 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 08 Oct 2019 05:13:17 +0000
Subject: [issue38404] spam
Message-ID: <1570511597.15.0.6957757108.issue38404@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
nosy:  -larry, pokeronlinejakarta
resolution:  -> rejected
stage:  -> resolved
status: open -> closed
title: Poker Online -> spam
type: crash -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38404>
_______________________________________

From report at bugs.python.org  Tue Oct  8 02:46:40 2019
From: report at bugs.python.org (Dima Tisnek)
Date: Tue, 08 Oct 2019 06:46:40 +0000
Subject: [issue38388] Pickle protocol v 5 needs to be documented
In-Reply-To: <1570405873.92.0.178526679084.issue38388@roundup.psfhosted.org>
Message-ID: <1570517200.2.0.408209358896.issue38388@roundup.psfhosted.org>


Change by Dima Tisnek <dimaqq at gmail.com>:


----------
keywords: +patch
pull_requests: +16225
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16639

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38388>
_______________________________________

From report at bugs.python.org  Tue Oct  8 03:06:54 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 07:06:54 +0000
Subject: [issue38400] Python segfaults when configured with --with-pydebug
 --with-trace-refs
In-Reply-To: <1570489297.7.0.2347429078.issue38400@roundup.psfhosted.org>
Message-ID: <1570518414.44.0.696061621389.issue38400@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Notes for myself.

the visit_decref() has been updated to display repr() of the parent object, rather than display the "freed" object.

Before:
---
Modules/gcmodule.c:378: visit_decref: Assertion "!_PyObject_IsFreed(op)" failed
<object at 0x5557629ca260 is freed>
Fatal Python error: _PyObject_AssertFailed
Python runtime state: preinitialized

Current thread 0x00007f6e2863e740 (most recent call first):
<no Python frame>
---

After:
---
Modules/gcmodule.c:378: visit_decref: Assertion "!_PyObject_IsFreed(op)" failed
Enable tracemalloc to get the memory block allocation traceback

object address  : 0x7fe2d1a52b40
object refcount : 1
object type     : 0x740be0
object type name: dict
object repr     : {'__repr__': <slot wrapper '__repr__' of 'weakref' objects>, '__hash__': <slot wrapper '__hash__' of 'weakref' objects>, '__call__': <slot wrapper '__call__' of 'weakref' objects>, '__lt__': <slot wrapper '__lt__' of 'weakref' objects>, '__le__': <slot wrapper '__le__' of 'weakref' objects>, '__eq__': <slot wrapper '__eq__' of 'weakref' objects>, '__ne__': <slot wrapper '__ne__' of 'weakref' objects>, '__gt__': <slot wrapper '__gt__' of 'weakref' objects>, '__ge__': <slot wrapper '__ge__' of 'weakref' objects>, '__init__': <slot wrapper '__init__' of 'weakref' objects>, '__new__': <built-in method __new__ of type object at 0x749500>, '__callback__': <member '__callback__' of 'weakref' objects>, '__doc__': None}

Fatal Python error: _PyObject_AssertFailed
Python runtime state: preinitialized

Current thread 0x00007fe2dea35740 (most recent call first):
<no Python frame>
---

The problem was that the None object was seen as "freed" because _ob_prev=_ob_next=NULL. This object doesn't seem to be part of the list of all objects, sys.getobjects(). I fixed Py_None, but then I got the same assertion error on a different (moduledef) object. I gave up, and Pablo and me fixed _PyObject_IsFreed() instead.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38400>
_______________________________________

From report at bugs.python.org  Tue Oct  8 03:09:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 07:09:47 +0000
Subject: [issue33803] contextvars: hamt_alloc() must initialize h_root and
 h_count fields
In-Reply-To: <1528415094.5.0.592728768989.issue33803@psf.upfronthosting.co.za>
Message-ID: <1570518587.37.0.14508720594.issue33803@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Notes for myself.

In bpo-38392, I modified PyObject_GC_Track() in debug mode to detect this bug.

For example, this bug can be reproduced with this change:
---
diff --git a/Python/hamt.c b/Python/hamt.c
index 28b4e1ef6c..d7dd555d15 100644
--- a/Python/hamt.c
+++ b/Python/hamt.c
@@ -2478,8 +2478,6 @@ hamt_alloc(void)
     if (o == NULL) {
         return NULL;
     }
-    o->h_count = 0;
-    o->h_root = NULL;
     o->h_weakreflist = NULL;
     PyObject_GC_Track(o);
     return o;
---

Python now detects the bug in debug mode:
---
$ ./python -m test -v test_context
(...)
test_context_copy_1 (test.test_context.ContextTest) ...
Modules/gcmodule.c:1931: visit_validate: Assertion failed: PyObject_GC_Track() object is not valid
Enable tracemalloc to get the memory block allocation traceback

object address  : 0x7f2b17408d70
object refcount : 1
object type     : 0x76bc20
object type name: hamt
object repr     : <hamt object at 0x7f2b17408d70>

Fatal Python error: _PyObject_AssertFailed
Python runtime state: initialized

Current thread 0x00007f2b25590740 (most recent call first):
  File "/home/vstinner/python/master/Lib/test/test_context.py", line 322 in test_context_copy_1
  File "/home/vstinner/python/master/Lib/unittest/case.py", line 616 in _callTestMethod
  File "/home/vstinner/python/master/Lib/unittest/case.py", line 659 in run
  (...)
  File "/home/vstinner/python/master/Lib/runpy.py", line 192 in _run_module_as_main
Aborted (core dumped)
---

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33803>
_______________________________________

From report at bugs.python.org  Tue Oct  8 03:10:02 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 07:10:02 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570518602.07.0.328230113207.issue38392@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I am sure this will break third-party projects. But I thing that we should not revert this change, as it completely matches the documentation. It is good that it was applied so early at development cycle.

Stefan, could you please test Cython and lxml with this?

----------
nosy: +scoder

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Tue Oct  8 03:54:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 07:54:13 +0000
Subject: [issue27542] Segfault in gcmodule.c:360 visit_decref
In-Reply-To: <1468755086.8.0.27245311458.issue27542@psf.upfronthosting.co.za>
Message-ID: <1570521253.21.0.956232301429.issue27542@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Julien: I'm working on enhancement of debug traces on visit_decref(). Are you still able to reproduce the crash in 2019?

I asked him on IRC. No, he cannot reproduce the bug anymore.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27542>
_______________________________________

From report at bugs.python.org  Tue Oct  8 04:06:51 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 08 Oct 2019 08:06:51 +0000
Subject: [issue27542] Segfault in gcmodule.c:360 visit_decref
In-Reply-To: <1468755086.8.0.27245311458.issue27542@psf.upfronthosting.co.za>
Message-ID: <1570522011.88.0.152823947502.issue27542@roundup.psfhosted.org>


Julien Palard <julien+python at palard.fr> added the comment:

I tried again with the same version of pip and cffi on cpython 2.7.16 (no 13, I have no VM atm to compile a 2.7.13) but no segfault this time.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27542>
_______________________________________

From report at bugs.python.org  Tue Oct  8 04:18:02 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 08:18:02 +0000
Subject: [issue38405] Nested subclasses of typing.NamedTuple are not pickleable
Message-ID: <1570522682.37.0.234893155024.issue38405@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

Example:

>>> from typing import NamedTuple
>>> import pickle
>>> class A:
...     class B(NamedTuple):
...         x: int
... 
>>> pickle.dumps(A.B)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
_pickle.PicklingError: Can't pickle <class '__main__.B'>: attribute lookup B on __main__ failed

----------
components: Library (Lib)
messages: 354176
nosy: gvanrossum, levkivskyi, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Nested subclasses of typing.NamedTuple are not pickleable
type: behavior
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38405>
_______________________________________

From report at bugs.python.org  Tue Oct  8 04:20:34 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 08:20:34 +0000
Subject: [issue38405] Nested subclasses of typing.NamedTuple are not pickleable
In-Reply-To: <1570522682.37.0.234893155024.issue38405@roundup.psfhosted.org>
Message-ID: <1570522834.29.0.736279203066.issue38405@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16226
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16641

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38405>
_______________________________________

From report at bugs.python.org  Tue Oct  8 04:36:22 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 08:36:22 +0000
Subject: [issue38406] Missed some public names in help(typing)
Message-ID: <1570523782.74.0.0305216426842.issue38406@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

Special forms NoReturn, Final, Literal and class ForwardRef are not shown in the help() output.

----------
components: Library (Lib)
messages: 354177
nosy: gvanrossum, levkivskyi, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Missed some public names in help(typing)
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38406>
_______________________________________

From report at bugs.python.org  Tue Oct  8 04:44:08 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 08:44:08 +0000
Subject: [issue38406] Missed some public names in help(typing)
In-Reply-To: <1570523782.74.0.0305216426842.issue38406@roundup.psfhosted.org>
Message-ID: <1570524248.53.0.525564883885.issue38406@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Sorry, I looked at wrong Python version.

----------
resolution:  -> works for me
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38406>
_______________________________________

From report at bugs.python.org  Tue Oct  8 04:59:44 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 08:59:44 +0000
Subject: [issue38407] Add docstrings for typing.SupportsXXX classes
Message-ID: <1570525184.08.0.803412577085.issue38407@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

typing.SupportsXXX classes do not have docstrings and help() shows the docstring of the parent class instead, which is wrong ("Base class for protocol classes...").

----------
components: Library (Lib)
messages: 354179
nosy: gvanrossum, levkivskyi, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Add docstrings for typing.SupportsXXX classes
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38407>
_______________________________________

From report at bugs.python.org  Tue Oct  8 05:01:56 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 09:01:56 +0000
Subject: [issue38407] Add docstrings for typing.SupportsXXX classes
In-Reply-To: <1570525184.08.0.803412577085.issue38407@roundup.psfhosted.org>
Message-ID: <1570525316.11.0.70862216919.issue38407@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16227
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16644

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38407>
_______________________________________

From report at bugs.python.org  Tue Oct  8 05:19:31 2019
From: report at bugs.python.org (hongweipeng)
Date: Tue, 08 Oct 2019 09:19:31 +0000
Subject: [issue26103] Contradiction in definition of "data descriptor" between
 (dotted lookup behavior/datamodel documentation) and (inspect
 lib/descriptor how-to)
In-Reply-To: <1452718612.1.0.925403449689.issue26103@psf.upfronthosting.co.za>
Message-ID: <1570526371.13.0.0515719894316.issue26103@roundup.psfhosted.org>


Change by hongweipeng <hongweichen8888 at sina.com>:


----------
pull_requests: +16228
pull_request: https://github.com/python/cpython/pull/16645

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26103>
_______________________________________

From report at bugs.python.org  Tue Oct  8 05:51:03 2019
From: report at bugs.python.org (James Allsopp)
Date: Tue, 08 Oct 2019 09:51:03 +0000
Subject: [issue38408] urlparse gives no method to build a url with a port
Message-ID: <1570528263.82.0.631134670905.issue38408@roundup.psfhosted.org>


New submission from James Allsopp <jamesaallsopp at googlemail.com>:

Hi,
I like to build my Url's using url unparse, e.g.
site_to_test = urllib.parse.urlunparse((scheme, host, page, '', '', ''))
r = requests.get(site_to_test)

However, we reach a lot of sites through SSH tunnels, as our network is heavily locked down, and need to specify a port. Unfortunately, we can parse a url with a port, and get site_to_test.port = '9097' we can't run it the other way, e.g. this fails.
site_to_test = urllib.parse.urlunparse((scheme, host, page, '', '', '',port=9097))

This should be easy to fix and there's a use case for it.
Thanks

----------
components: Library (Lib)
messages: 354180
nosy: James Allsopp
priority: normal
severity: normal
status: open
title: urlparse gives no method to build a url with a port
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38408>
_______________________________________

From report at bugs.python.org  Tue Oct  8 05:51:06 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 08 Oct 2019 09:51:06 +0000
Subject: [issue26219] implement per-opcode cache in ceval
In-Reply-To: <1570452060.66.0.886326993478.issue26219@roundup.psfhosted.org>
Message-ID: <CAEfz+TwwP6msvO+t4rKOgA3Pbwvq9FFvBjb73nBWj0YT74DkHw@mail.gmail.com>


Inada Naoki <songofacandy at gmail.com> added the comment:

On Mon, Oct 7, 2019 at 9:41 PM Mark Shannon <report at bugs.python.org> wrote:
>
> Mark Shannon <mark at hotpy.org> added the comment:
>
> Given that
> def foo(): int; str; bytes; float; int; str; bytes; float
> can be trivially be rewritten as
> def foo(): pass
> I think that benchmark is meaningless.
>

Do you mean every microbenchmark measuring single feature is meaningless?

I think it is worth enough for readers who understand what
`LOAD_GLOBAL` instruction means.
(e.g. People who using techniques like `int_ = int` before a loop.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26219>
_______________________________________

From report at bugs.python.org  Tue Oct  8 06:02:00 2019
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 08 Oct 2019 10:02:00 +0000
Subject: [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1570528920.75.0.040752402381.issue32996@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
pull_requests: +16229
pull_request: https://github.com/python/cpython/pull/16646

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Tue Oct  8 06:29:06 2019
From: report at bugs.python.org (=?utf-8?q?Ricardo_B=C3=A1nffy?=)
Date: Tue, 08 Oct 2019 10:29:06 +0000
Subject: [issue38294] Documentation on 3.6->3.7 re.escape no longer escaping
 "/" or ":" should be obvious
In-Reply-To: <1569603997.59.0.0237297108404.issue38294@roundup.psfhosted.org>
Message-ID: <1570530546.01.0.303969868226.issue38294@roundup.psfhosted.org>


Change by Ricardo B?nffy <rbanffy at gmail.com>:


----------
pull_requests: +16230
pull_request: https://github.com/python/cpython/pull/16647

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38294>
_______________________________________

From report at bugs.python.org  Tue Oct  8 06:34:50 2019
From: report at bugs.python.org (M. Eric Irrgang)
Date: Tue, 08 Oct 2019 10:34:50 +0000
Subject: [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1570530890.05.0.390338975009.issue32996@roundup.psfhosted.org>


Change by M. Eric Irrgang <ericirrgang at gmail.com>:


----------
pull_requests: +16231
pull_request: https://github.com/python/cpython/pull/16648

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Tue Oct  8 06:46:20 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 10:46:20 +0000
Subject: [issue33714] module can set an exception in tp_clear
In-Reply-To: <1527769305.39.0.682650639539.issue33714@psf.upfronthosting.co.za>
Message-ID: <1570531580.87.0.10390479039.issue33714@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset d7c387384a27f37e4e3fa7890c859212c56b45b2 by Miss Islington (bot) (Serhiy Storchaka) in branch 'master':
bpo-33714: Output an exception raised in module's m_clear(). (GH-16592)
https://github.com/python/cpython/commit/d7c387384a27f37e4e3fa7890c859212c56b45b2


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33714>
_______________________________________

From report at bugs.python.org  Tue Oct  8 06:47:11 2019
From: report at bugs.python.org (Petr Viktorin)
Date: Tue, 08 Oct 2019 10:47:11 +0000
Subject: [issue33714] module can set an exception in tp_clear
In-Reply-To: <1527769305.39.0.682650639539.issue33714@psf.upfronthosting.co.za>
Message-ID: <1570531631.11.0.646348998905.issue33714@roundup.psfhosted.org>


Petr Viktorin <encukou at gmail.com> added the comment:

Indeed, it can be closed.
Thanks Serhiy for the better error message!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33714>
_______________________________________

From report at bugs.python.org  Tue Oct  8 06:46:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 10:46:47 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570531607.39.0.341324466056.issue38118@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> ==6832==    at 0x4D87E9: PyUnicode_Decode (unicodeobject.c:3395)

This warning is a false alarm: the GCC builtin strcmp() function seems to read past the NUL byte. When recompiling Python with -fno-builtin GCC option, the warning is gone.

The valgrind warning can be reproduced using attached valgrind_strcmp_warn.c:

On Fedora 30 with:

* gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1)
* valgrind-3.15.0

GCC builtin strcmp() emits a false alarm in valgrind: it reads past the NUL
byte.

$ gcc -O3 valgrind_strcmp_warn.c -o valgrind_strcmp_warn -D NDEBUG=1 -g && valgrind ./valgrind_strcmp_warn
(...)
==29173== Conditional jump or move depends on uninitialised value(s)
==29173==    at 0x4011CB: PyUnicode_Decode.part.0 (valgrind_strcmp_warn.c:276)
==29173==    by 0x4898F42: (below main) (in /usr/lib64/libc-2.29.so)
==29173==
==29173== Conditional jump or move depends on uninitialised value(s)
==29173==    at 0x4011EE: PyUnicode_Decode.part.0 (valgrind_strcmp_warn.c:280)
==29173==    by 0x4898F42: (below main) (in /usr/lib64/libc-2.29.so)
==29173==
==29173== Conditional jump or move depends on uninitialised value(s)
==29173==    at 0x401221: PyUnicode_Decode.part.0 (valgrind_strcmp_warn.c:282)
==29173==    by 0x4898F42: (below main) (in /usr/lib64/libc-2.29.so)
(...)
==29173== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)

versus

$ gcc -O3 valgrind_strcmp_warn.c -o valgrind_strcmp_warn -D NDEBUG=1 -fno-builtin -g && valgrind ./valgrind_strcmp_warn
==29217== Memcheck, a memory error detector
(...)
==29217== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

----------
title: Valgrind warnings when running tokenize.py -> Valgrind warning in PyUnicode_Decode: false alarm with GCC builtin strcmp()
Added file: https://bugs.python.org/file48647/valgrind_strcmp_warn.c

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:04:03 2019
From: report at bugs.python.org (Matthias Klose)
Date: Tue, 08 Oct 2019 11:04:03 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570532643.77.0.852325441945.issue38368@roundup.psfhosted.org>


Change by Matthias Klose <doko at debian.org>:


----------
keywords: +3.7regression -patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:23:57 2019
From: report at bugs.python.org (Amir Mohamadi)
Date: Tue, 08 Oct 2019 11:23:57 +0000
Subject: [issue38408] urlparse gives no method to build a url with a port
In-Reply-To: <1570528263.82.0.631134670905.issue38408@roundup.psfhosted.org>
Message-ID: <1570533837.25.0.623021877753.issue38408@roundup.psfhosted.org>


Amir Mohamadi <amiremohamadi at yahoo.com> added the comment:

Hi!
I'm a newbie but I'd like to work on this issue
can I work on it???

----------
nosy: +Amir

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38408>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:31:44 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 11:31:44 +0000
Subject: [issue38371] Tkinter: deprecate the split() method
In-Reply-To: <1570203221.73.0.664458057352.issue38371@roundup.psfhosted.org>
Message-ID: <1570534304.15.0.753400463776.issue38371@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset d05b000c6bcd39dba4f4b2656e45954802649562 by Serhiy Storchaka in branch 'master':
bpo-38371: Tkinter: deprecate the split() method. (GH-16584)
https://github.com/python/cpython/commit/d05b000c6bcd39dba4f4b2656e45954802649562


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38371>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:32:28 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 11:32:28 +0000
Subject: [issue36698] Shell restart when error message contains non-BMP
 characters
In-Reply-To: <1555953357.75.0.808052597637.issue36698@roundup.psfhosted.org>
Message-ID: <1570534348.87.0.527093202384.issue36698@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset b690a2759e62d9ee0b6ea1b20e8f7e4b2cdbf8bb by Serhiy Storchaka in branch 'master':
bpo-36698: IDLE no longer fails when write non-encodable characters to stderr. (GH-16583)
https://github.com/python/cpython/commit/b690a2759e62d9ee0b6ea1b20e8f7e4b2cdbf8bb


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36698>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:32:39 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 11:32:39 +0000
Subject: [issue36698] Shell restart when error message contains non-BMP
 characters
In-Reply-To: <1555953357.75.0.808052597637.issue36698@roundup.psfhosted.org>
Message-ID: <1570534359.35.0.948661955757.issue36698@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16232
pull_request: https://github.com/python/cpython/pull/16649

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36698>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:32:46 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 11:32:46 +0000
Subject: [issue36698] Shell restart when error message contains non-BMP
 characters
In-Reply-To: <1555953357.75.0.808052597637.issue36698@roundup.psfhosted.org>
Message-ID: <1570534366.04.0.623647247694.issue36698@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16233
pull_request: https://github.com/python/cpython/pull/16650

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36698>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:37:58 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 11:37:58 +0000
Subject: [issue38371] Tkinter: deprecate the split() method
In-Reply-To: <1570203221.73.0.664458057352.issue38371@roundup.psfhosted.org>
Message-ID: <1570534678.86.0.56465986531.issue38371@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38371>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:49:22 2019
From: report at bugs.python.org (hai shi)
Date: Tue, 08 Oct 2019 11:49:22 +0000
Subject: [issue16623] argparse help formatter does not honor non-breaking space
In-Reply-To: <1354745001.59.0.580615965604.issue16623@psf.upfronthosting.co.za>
Message-ID: <1570535362.33.0.848081883932.issue16623@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

I checked the help format.
the help_lines' width in python2.7 is different python3.

The width is more likely a hardcode in 
https://github.com/python/cpython/blob/2.7/Lib/argparse.py#L165.
, so the help_lines = [u'This is a very long help string. ex: "--s3', u's3://my.bucket/dir1/dir2"'](when joining this help_lines it will add a '\n' in the middle)

Since python 3.3, the width is a dynamic value in 
https://github.com/python/cpython/blob/master/Lib/argparse.py#L170
, so the help_lines = ['This is a very long help string. ex: "--s3\xa0s3://my.bucket/dir1/dir2"']

----------
nosy: +shihai1991

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16623>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:51:19 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 11:51:19 +0000
Subject: [issue36698] Shell restart when error message contains non-BMP
 characters
In-Reply-To: <1555953357.75.0.808052597637.issue36698@roundup.psfhosted.org>
Message-ID: <1570535479.89.0.793645003152.issue36698@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset a1f45008f190b0d340ec0eac623f05ef98e6b4c9 by Miss Islington (bot) in branch '3.8':
bpo-36698: IDLE no longer fails when write non-encodable characters to stderr. (GH-16583)
https://github.com/python/cpython/commit/a1f45008f190b0d340ec0eac623f05ef98e6b4c9


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36698>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:52:00 2019
From: report at bugs.python.org (hai shi)
Date: Tue, 08 Oct 2019 11:52:00 +0000
Subject: [issue16623] argparse help formatter does not honor non-breaking space
In-Reply-To: <1354745001.59.0.580615965604.issue16623@psf.upfronthosting.co.za>
Message-ID: <1570535520.64.0.322988835953.issue16623@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

oh, typo error. the help_lines' width in python2.7 is different python3.-->the help_lines' width in python2.7 is different with python3.x

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16623>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:52:52 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 11:52:52 +0000
Subject: [issue36698] Shell restart when error message contains non-BMP
 characters
In-Reply-To: <1555953357.75.0.808052597637.issue36698@roundup.psfhosted.org>
Message-ID: <1570535572.05.0.147162705897.issue36698@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 4f962ecfa1aadc45facc250841208f6dd2ce690f by Miss Islington (bot) in branch '3.7':
bpo-36698: IDLE no longer fails when write non-encodable characters to stderr. (GH-16583)
https://github.com/python/cpython/commit/4f962ecfa1aadc45facc250841208f6dd2ce690f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36698>
_______________________________________

From report at bugs.python.org  Tue Oct  8 07:56:49 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 08 Oct 2019 11:56:49 +0000
Subject: [issue38401] Make dataclass attribute docstrings accessible
In-Reply-To: <1570494293.05.0.934356434949.issue38401@roundup.psfhosted.org>
Message-ID: <1570535809.61.0.275195380836.issue38401@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Note that those strings are not docstrings, per se. They're just strings, and aren't available in the class definition for the dataclass decorator to see. It's really no different from:

class X:
    x: int
    3

That 3 just gets evaluated and thrown away, like the strings in your example. To change this is beyond the scope of dataclasses, and would need to be a language change. I can't think of a good way to attach the string to the annotation before it (I'm assuming this would only work with annotations, but maybe you have other ideas). You might want to bring this up on python-ideas to get some more feedback.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38401>
_______________________________________

From report at bugs.python.org  Tue Oct  8 08:03:42 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 12:03:42 +0000
Subject: [issue36698] Shell restart when error message contains non-BMP
 characters
In-Reply-To: <1555953357.75.0.808052597637.issue36698@roundup.psfhosted.org>
Message-ID: <1570536222.47.0.18846383732.issue36698@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36698>
_______________________________________

From report at bugs.python.org  Tue Oct  8 08:05:45 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 12:05:45 +0000
Subject: [issue22742] IDLE shows traceback when printing non-BMP character
In-Reply-To: <1414426704.85.0.168243800807.issue22742@psf.upfronthosting.co.za>
Message-ID: <1570536345.26.0.715511866085.issue22742@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

And with PR 16583 it is now completely fixed. I.e. it can only fail in cases when the regular interactive interpreter fails too.

----------
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22742>
_______________________________________

From report at bugs.python.org  Tue Oct  8 08:15:19 2019
From: report at bugs.python.org (Petr Viktorin)
Date: Tue, 08 Oct 2019 12:15:19 +0000
Subject: [issue37879] Segfaults in C heap type subclasses
In-Reply-To: <1566074851.0.0.451710928537.issue37879@roundup.psfhosted.org>
Message-ID: <1570536919.21.0.24289434681.issue37879@roundup.psfhosted.org>


Petr Viktorin <encukou at gmail.com> added the comment:

Thanks to St?phane and Eddie for fixing the refleak!

----------
resolution:  -> fixed
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37879>
_______________________________________

From report at bugs.python.org  Tue Oct  8 08:18:12 2019
From: report at bugs.python.org (Petr Viktorin)
Date: Tue, 08 Oct 2019 12:18:12 +0000
Subject: [issue38140] Py_tp_dictoffset / Py_tp_finalize are unsettable in
 stable API
In-Reply-To: <1568297060.68.0.400472303762.issue38140@roundup.psfhosted.org>
Message-ID: <1570537092.32.0.178105798381.issue38140@roundup.psfhosted.org>


Petr Viktorin <encukou at gmail.com> added the comment:

Thank you all!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38140>
_______________________________________

From report at bugs.python.org  Tue Oct  8 08:34:38 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 08 Oct 2019 12:34:38 +0000
Subject: [issue38408] urlparse gives no method to build a url with a port
In-Reply-To: <1570528263.82.0.631134670905.issue38408@roundup.psfhosted.org>
Message-ID: <1570538078.47.0.890268307934.issue38408@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

One way I can think of doing this in a backward compatible way is to add keyword parameters to urlunparse, like:

def urlunparse(components, *, username=None, password=None, hostname=None, port=None):

Which would make your call:
site_to_test = urllib.parse.urlunparse((scheme, host, page, '', '', ''), port=9097)

I think that's a horrible interface, but it is backward compatible.

A better interface would be have all 10 URL parameters passed in as keyword arguments, with reasonable defaults. If you want to keep this named "urlunparse", you'd need to say you can't pass in both "components" and any other named parameter (other than maybe the 4  parameters that are unnamed in ParseResult).

Something like:
def urlunparse(components=None, scheme=None, netloc=None, path=None, params=None, query=None, fragment=None, *, username=None, password=None, hostname=None, port=None):

Then error if components is set and any of scheme, netloc, path, params, query, or fragment is also set.

We could bikeshed about which would be keyword-only, if any, all, or only some as I've shown here.

Another option would be to leave urlunparse alone, and add a new function entirely, which wouldn't have to worry about backward compatibility.

It might be worthwhile to raise this on python-ideas.

----------
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38408>
_______________________________________

From report at bugs.python.org  Tue Oct  8 08:45:06 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 12:45:06 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570538706.79.0.833665135802.issue38118@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The valgrind false alarm on GCC builtin strcmp() has been reported to the Valgrind bug tracker in 2011, with an update in 2012 and... nothing :-(
https://bugs.kde.org/show_bug.cgi?id=264936

curl worked around the issue by disabling valgrind on the impacted test:
https://lists.fedoraproject.org/pipermail/scm-commits/2011-February/567665.html

Passing "--partial-loads-ok=yes" to Valgrind has no effect... It became the default:
http://valgrind.org/docs/manual/mc-manual.html#opt.partial-loads-ok

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 08:45:52 2019
From: report at bugs.python.org (Ben Harper)
Date: Tue, 08 Oct 2019 12:45:52 +0000
Subject: [issue36253] Use after free in ctypes test suite
In-Reply-To: <1552176520.99.0.273814604607.issue36253@roundup.psfhosted.org>
Message-ID: <1570538752.17.0.879238281581.issue36253@roundup.psfhosted.org>


Ben Harper <btharper1221 at gmail.com> added the comment:

Changes merged

----------
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36253>
_______________________________________

From report at bugs.python.org  Tue Oct  8 08:47:13 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 08 Oct 2019 12:47:13 +0000
Subject: [issue33803] contextvars: hamt_alloc() must initialize h_root and
 h_count fields
In-Reply-To: <1528415094.5.0.592728768989.issue33803@psf.upfronthosting.co.za>
Message-ID: <1570538833.37.0.118563625323.issue33803@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

> In bpo-38392, I modified PyObject_GC_Track() in debug mode to detect this bug.

Awesome!!!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33803>
_______________________________________

From report at bugs.python.org  Tue Oct  8 08:55:35 2019
From: report at bugs.python.org (Ben Harper)
Date: Tue, 08 Oct 2019 12:55:35 +0000
Subject: [issue36356] Failure to build with address sanitizer
In-Reply-To: <1552967277.69.0.646647509224.issue36356@roundup.psfhosted.org>
Message-ID: <1570539335.52.0.115613780875.issue36356@roundup.psfhosted.org>


Ben Harper <btharper1221 at gmail.com> added the comment:

The default build of python with ASAN builds successfully. Test suite and PGO build are currently blocked, but that can be separated if it makes more sense to handle them individually.

Would it make sense to add an ASAN build to the CI pipeline to make detection automatic going forward?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36356>
_______________________________________

From report at bugs.python.org  Tue Oct  8 08:56:32 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 08 Oct 2019 12:56:32 +0000
Subject: [issue36356] Failure to build with address sanitizer
In-Reply-To: <1552967277.69.0.646647509224.issue36356@roundup.psfhosted.org>
Message-ID: <1570539392.58.0.756300746535.issue36356@roundup.psfhosted.org>


Change by Yury Selivanov <yselivanov at gmail.com>:


----------
nosy:  -yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36356>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:03:16 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 13:03:16 +0000
Subject: [issue36356] Failure to build with address sanitizer
In-Reply-To: <1552967277.69.0.646647509224.issue36356@roundup.psfhosted.org>
Message-ID: <1570539796.06.0.883588951918.issue36356@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> The default build of python with ASAN builds successfully. Test suite and PGO build are currently blocked, but that can be separated if it makes more sense to handle them individually.

Yeah, please open one issue per ASAN issue (try to group similar warnings in the same Python issue?).


> Would it make sense to add an ASAN build to the CI pipeline to make detection automatic going forward?

Gregory maintains a clang UBSan buildbot:
https://buildbot.python.org/all/#/builders/135

Usually I prefer to setup a buildbot when most issues are fixed.

I close this issue.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36356>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:08:22 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 13:08:22 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570540102.84.0.79298705839.issue38118@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16234
stage: resolved -> patch review
pull_request: https://github.com/python/cpython/pull/16651

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:19:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 13:19:24 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570540764.31.0.508358838071.issue38118@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It seems like Python 2.7 is not affected.

----------
versions: +Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:29:57 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 13:29:57 +0000
Subject: [issue38405] Nested subclasses of typing.NamedTuple are not pickleable
In-Reply-To: <1570522682.37.0.234893155024.issue38405@roundup.psfhosted.org>
Message-ID: <1570541397.06.0.195489271616.issue38405@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 13abda41003daf599587991d8291f0dacf6e9519 by Serhiy Storchaka in branch 'master':
bpo-38405: Make nested subclasses of typing.NamedTuple pickleable. (GH-16641)
https://github.com/python/cpython/commit/13abda41003daf599587991d8291f0dacf6e9519


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38405>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:30:20 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 13:30:20 +0000
Subject: [issue38407] Add docstrings for typing.SupportsXXX classes
In-Reply-To: <1570525184.08.0.803412577085.issue38407@roundup.psfhosted.org>
Message-ID: <1570541420.05.0.856004186365.issue38407@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 8252c52e57283515ace5d4251584255dc5c60eb5 by Serhiy Storchaka in branch 'master':
bpo-38407: Add docstrings for typing.SupportsXXX classes. (GH-16644)
https://github.com/python/cpython/commit/8252c52e57283515ace5d4251584255dc5c60eb5


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38407>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:42:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 13:42:24 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570542144.39.0.554984782854.issue38118@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 03ab6b4fc6f59a4452756e7a3a46310ce30ec4b2 by Victor Stinner in branch 'master':
bpo-38118: Ignore Valgrind false alarm in PyUnicode_Decode() (GH-16651)
https://github.com/python/cpython/commit/03ab6b4fc6f59a4452756e7a3a46310ce30ec4b2


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:42:30 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 13:42:30 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570542150.74.0.488052561864.issue38118@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16235
pull_request: https://github.com/python/cpython/pull/16652

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:42:38 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 13:42:38 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570542158.4.0.519289532135.issue38118@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16236
pull_request: https://github.com/python/cpython/pull/16653

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:49:15 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 13:49:15 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570542555.02.0.445016913722.issue38118@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 364532fb4962991d278da6470c3aec4e443e533d by Miss Islington (bot) in branch '3.8':
bpo-38118: Ignore Valgrind false alarm in PyUnicode_Decode() (GH-16651)
https://github.com/python/cpython/commit/364532fb4962991d278da6470c3aec4e443e533d


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:50:14 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 13:50:14 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570542614.0.0.747747113985.issue38118@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16237
pull_request: https://github.com/python/cpython/pull/16654

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:53:51 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 13:53:51 +0000
Subject: [issue38405] Nested subclasses of typing.NamedTuple are not pickleable
In-Reply-To: <1570522682.37.0.234893155024.issue38405@roundup.psfhosted.org>
Message-ID: <1570542831.53.0.491205528608.issue38405@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16238
pull_request: https://github.com/python/cpython/pull/16655

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38405>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:54:25 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 13:54:25 +0000
Subject: [issue38407] Add docstrings for typing.SupportsXXX classes
In-Reply-To: <1570525184.08.0.803412577085.issue38407@roundup.psfhosted.org>
Message-ID: <1570542865.4.0.609225955654.issue38407@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16239
pull_request: https://github.com/python/cpython/pull/16656

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38407>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:56:11 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 13:56:11 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570542971.36.0.125303518777.issue38118@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 98043b4fcd80bdfa8cc2be1730fa2a4cf4950958 by Miss Islington (bot) in branch '3.7':
bpo-38118: Ignore Valgrind false alarm in PyUnicode_Decode() (GH-16651)
https://github.com/python/cpython/commit/98043b4fcd80bdfa8cc2be1730fa2a4cf4950958


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:58:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 13:58:13 +0000
Subject: [issue38118] Valgrind warning in PyUnicode_Decode: false alarm with
 GCC builtin strcmp()
In-Reply-To: <1568215737.14.0.192001407155.issue38118@roundup.psfhosted.org>
Message-ID: <1570543093.07.0.200165263542.issue38118@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Ok, the issue has been fixed in 3.7, 3.8 and master branches.

Ensure that you use Valgrind with Misc/valgrind.supp. Example:

$ echo|PYTHONMALLOC=malloc valgrind --suppressions=Misc/valgrind-python.supp ./python Lib/tokenize.py
(...)
==12923== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)

I close the issue.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38118>
_______________________________________

From report at bugs.python.org  Tue Oct  8 09:59:54 2019
From: report at bugs.python.org (Bob Dowling)
Date: Tue, 08 Oct 2019 13:59:54 +0000
Subject: [issue38409] Typo in doc string for str.strip
Message-ID: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>


New submission from Bob Dowling <bob.dowling.64 at gmail.com>:

The doc string for str.strip() has a typo: the "d" at the end of "removed" is missing.

help(str.strip)

Currently:
Return a copy of the string with leading and trailing whitespace remove.

Should be:
Return a copy of the string with leading and trailing whitespace removed.

I have attached an offered patch.

----------
components: Library (Lib)
files: str_strip.patch
keywords: patch
messages: 354209
nosy: Bob Dowling
priority: normal
severity: normal
status: open
title: Typo in doc string for str.strip
type: behavior
versions: Python 3.7
Added file: https://bugs.python.org/file48648/str_strip.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:03:35 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 14:03:35 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570543415.11.0.916029767299.issue38409@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +newcomer friendly

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:06:15 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Tue, 08 Oct 2019 14:06:15 +0000
Subject: [issue38410] Possible fatal errors due to
 _PyEval_SetAsyncGen{Finalizer, Firstiter}()
Message-ID: <1570543574.99.0.942798410146.issue38410@roundup.psfhosted.org>


New submission from Zackery Spytz <zspytz at gmail.com>:

_PyEval_SetAsyncGenFinalizer() and _PyEval_SetAsyncGenFirstiter() don't include proper error handling for their PySys_Audit() calls. This could lead to leaked exceptions and fatal errors.

----------
components: Interpreter Core
messages: 354210
nosy: ZackerySpytz
priority: normal
severity: normal
status: open
title: Possible fatal errors due to _PyEval_SetAsyncGen{Finalizer,Firstiter}()
type: crash
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38410>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:08:56 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Tue, 08 Oct 2019 14:08:56 +0000
Subject: [issue38410] Possible fatal errors due to
 _PyEval_SetAsyncGen{Finalizer, Firstiter}()
In-Reply-To: <1570543574.99.0.942798410146.issue38410@roundup.psfhosted.org>
Message-ID: <1570543736.46.0.62298193918.issue38410@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
keywords: +patch
pull_requests: +16240
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16657

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38410>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:12:45 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 14:12:45 +0000
Subject: [issue38405] Nested subclasses of typing.NamedTuple are not pickleable
In-Reply-To: <1570522682.37.0.234893155024.issue38405@roundup.psfhosted.org>
Message-ID: <1570543965.55.0.19138367918.issue38405@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 10b475a151dc35c8ca4047331d591130973e914d by Miss Islington (bot) in branch '3.8':
bpo-38405: Make nested subclasses of typing.NamedTuple pickleable. (GH-16641)
https://github.com/python/cpython/commit/10b475a151dc35c8ca4047331d591130973e914d


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38405>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:15:02 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Oct 2019 14:15:02 +0000
Subject: [issue38407] Add docstrings for typing.SupportsXXX classes
In-Reply-To: <1570525184.08.0.803412577085.issue38407@roundup.psfhosted.org>
Message-ID: <1570544102.0.0.934032868773.issue38407@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 7162440a7247f77d22cd937143f358fd5ac85af4 by Miss Islington (bot) in branch '3.8':
bpo-38407: Add docstrings for typing.SupportsXXX classes. (GH-16644)
https://github.com/python/cpython/commit/7162440a7247f77d22cd937143f358fd5ac85af4


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38407>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:27:02 2019
From: report at bugs.python.org (Tim Peters)
Date: Tue, 08 Oct 2019 14:27:02 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570544822.12.0.800361055336.issue38379@roundup.psfhosted.org>


Change by Tim Peters <tim at python.org>:


----------
keywords: +patch
pull_requests: +16241
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16658

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:28:52 2019
From: report at bugs.python.org (Tim Peters)
Date: Tue, 08 Oct 2019 14:28:52 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570544932.05.0.354419655603.issue38379@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

PR 16658 aims to repair the stats reported.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:35:36 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Tue, 08 Oct 2019 14:35:36 +0000
Subject: [issue36075] python 2to3 conversion tool is generating file with
 extra line for every input line
In-Reply-To: <1550828319.37.0.854628356141.issue36075@roundup.psfhosted.org>
Message-ID: <1570545336.02.0.763716610772.issue36075@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

Looks like a duplicate of #34108

----------
nosy: +mark.dickinson

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36075>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:38:52 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 08 Oct 2019 14:38:52 +0000
Subject: [issue38410] Possible fatal errors due to
 _PyEval_SetAsyncGen{Finalizer, Firstiter}()
In-Reply-To: <1570543574.99.0.942798410146.issue38410@roundup.psfhosted.org>
Message-ID: <1570545532.66.0.372638944009.issue38410@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +steve.dower

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38410>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:40:38 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 08 Oct 2019 14:40:38 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570545638.47.0.952841579256.issue38409@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Thanks for the patch and report. CPython now accepts GitHub pull requests https://devguide.python.org/pullrequest/

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:44:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 14:44:39 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1570545879.69.0.025328431416.issue37531@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16242
pull_request: https://github.com/python/cpython/pull/16659

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:44:40 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 14:44:40 +0000
Subject: [issue38207] subprocess: On Windows,
 Popen.kill() + Popen.communicate() is blocking until all processes
 using the pipe close the pipe
In-Reply-To: <1568763048.2.0.765446302919.issue38207@roundup.psfhosted.org>
Message-ID: <1570545880.06.0.961916659054.issue38207@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16243
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16659

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38207>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:53:47 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Tue, 08 Oct 2019 14:53:47 +0000
Subject: [issue38202] A fatal error in test_dictviews
In-Reply-To: <1568748421.29.0.795591630213.issue38202@roundup.psfhosted.org>
Message-ID: <1570546427.68.0.863523650374.issue38202@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

Can you finalize the PR 16241 by adding the unit test which @serhiy.storchaka suggested?

----------
nosy: +corona10

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38202>
_______________________________________

From report at bugs.python.org  Tue Oct  8 10:54:16 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Tue, 08 Oct 2019 14:54:16 +0000
Subject: [issue36075] python 2to3 conversion tool is generating file with
 extra line for every input line
In-Reply-To: <1550828319.37.0.854628356141.issue36075@roundup.psfhosted.org>
Message-ID: <1570546456.72.0.215650390696.issue36075@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

Closing as duplicate.

@sabakauser: if you update to a recent Python 3.7 (anything more recent than 3.7.1 should be enough), you should find that this is fixed.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> 2to3 munges new lines on Windows

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36075>
_______________________________________

From report at bugs.python.org  Tue Oct  8 11:15:47 2019
From: report at bugs.python.org (Jack Robison)
Date: Tue, 08 Oct 2019 15:15:47 +0000
Subject: [issue38411] SQLITE_MISUSE race condition in sqlite3 is misleadingly
 raised as a binding error
Message-ID: <1570547747.91.0.842919846552.issue38411@roundup.psfhosted.org>


New submission from Jack Robison <jackrobison at lbry.com>:

There is a race condition in the sqlite3 module that is misleadingly raised as sqlite3.InterfaceError('Error binding parameter 0 - probably unsupported type.')

There are two issues here, one is the incorrectly raise error (https://bugs.python.org/issue16379), the other is the underlying SQLITE_MISUSE caused by the race condition. I believe this is a race between sqlite3 vs python garbage collection due to the releasing of the GIL. If the GIL releasing is removed from sqlite3, I cannot reproduce the race.

Here is a script to reproduce the error, as the number of runners or queries_per_executemany is increased the error happens more frequently. The minimal test case only needs two executemanys where each has two queries to run.





import asyncio
import sqlite3
from concurrent.futures.thread import ThreadPoolExecutor


async def misuse_sqlite(runners=2, queries_per_executemany=2):
    loop = asyncio.get_event_loop()

    expected_error = 'Error binding parameter 0 - probably unsupported type.'
    exceptions = []
    executor = ThreadPoolExecutor(1)
    db = executor.submit(sqlite3.connect, ':memory:', isolation_level=None).result()
    executor.submit(db.executescript, "create table test (id text primary key);")

    def query_in_executor():
        return asyncio.wrap_future(executor.submit(executemany))

    def executemany():
        try:
            return db.executemany("select * from test where id=?", ((str(i),) for i in range(queries_per_executemany)))
        except Exception as err:
            exceptions.append(err)

    for _ in range(runners):
        loop.call_soon(query_in_executor)
    await asyncio.sleep(0.01)

    assert all(str(err) == expected_error and isinstance(err, sqlite3.InterfaceError) for err in exceptions)

    executor.submit(db.close).result()
    executor.shutdown()

    return len(exceptions) > 0


attempts = 0

while True:
    attempts += 1
    if asyncio.run(misuse_sqlite()):
        print('error hit on attempt', attempts)
        break

----------
components: Library (Lib)
messages: 354218
nosy: Jack Robison
priority: normal
severity: normal
status: open
title: SQLITE_MISUSE race condition in sqlite3 is misleadingly raised as a binding error
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38411>
_______________________________________

From report at bugs.python.org  Tue Oct  8 11:30:56 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 15:30:56 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570548656.36.0.541013064642.issue38395@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 10cd00a9e3c22af37c748ea5a417f6fb66601e21 by Pablo Galindo in branch 'master':
bpo-38395: Fix ownership in weakref.proxy methods (GH-16632)
https://github.com/python/cpython/commit/10cd00a9e3c22af37c748ea5a417f6fb66601e21


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Tue Oct  8 11:47:53 2019
From: report at bugs.python.org (Steve Dower)
Date: Tue, 08 Oct 2019 15:47:53 +0000
Subject: [issue38410] Possible fatal errors due to
 _PyEval_SetAsyncGen{Finalizer, Firstiter}()
In-Reply-To: <1570543574.99.0.942798410146.issue38410@roundup.psfhosted.org>
Message-ID: <1570549673.69.0.954284840542.issue38410@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

You're right, they need either your patch or PyErr_WriteUnraisable(NULL) before returning.

?ukasz - this needs a fix in 3.8, but we don't have to necessarily change the (internal, but exposed) ABI. For 3.9, we'll fix it properly, but for 3.8 I'll let you make the call whether we can also add a return value to these functions.

-PyAPI_FUNC(void) _PyEval_SetAsyncGenFirstiter(PyObject *);
+PyAPI_FUNC(int) _PyEval_SetAsyncGenFirstiter(PyObject *);
 PyAPI_FUNC(PyObject *) _PyEval_GetAsyncGenFirstiter(void);
-PyAPI_FUNC(void) _PyEval_SetAsyncGenFinalizer(PyObject *);
+PyAPI_FUNC(int) _PyEval_SetAsyncGenFinalizer(PyObject *);

----------
keywords: +newcomer friendly
nosy: +lukasz.langa
priority: normal -> release blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38410>
_______________________________________

From report at bugs.python.org  Tue Oct  8 11:54:27 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 15:54:27 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570550067.58.0.05557216346.issue38395@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16244
pull_request: https://github.com/python/cpython/pull/16661

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Tue Oct  8 11:55:31 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 15:55:31 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570550131.71.0.17685216432.issue38395@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16245
pull_request: https://github.com/python/cpython/pull/16662

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Tue Oct  8 11:57:33 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 15:57:33 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570550253.14.0.545801757558.issue38395@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16246
pull_request: https://github.com/python/cpython/pull/16663

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Tue Oct  8 12:08:32 2019
From: report at bugs.python.org (Jack Robison)
Date: Tue, 08 Oct 2019 16:08:32 +0000
Subject: [issue38411] SQLITE_MISUSE race condition in sqlite3 is misleadingly
 raised as a binding error
In-Reply-To: <1570547747.91.0.842919846552.issue38411@roundup.psfhosted.org>
Message-ID: <1570550912.88.0.401306658285.issue38411@roundup.psfhosted.org>


Change by Jack Robison <jackrobison at lbry.com>:


----------
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38411>
_______________________________________

From report at bugs.python.org  Tue Oct  8 12:41:04 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2019 16:41:04 +0000
Subject: [issue38294] Documentation on 3.6->3.7 re.escape no longer escaping
 "/" or ":" should be obvious
In-Reply-To: <1569603997.59.0.0237297108404.issue38294@roundup.psfhosted.org>
Message-ID: <1570552864.55.0.701987667886.issue38294@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 43f5c0c4d0a608c04c3978adb45117f3943203b7 by Serhiy Storchaka (Ricardo B?nffy) in branch '3.7':
[3.7] bpo-38294: Add list of no-longer-escaped chars to re.escape documentation. (GH-16442) (GH-16647)
https://github.com/python/cpython/commit/43f5c0c4d0a608c04c3978adb45117f3943203b7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38294>
_______________________________________

From report at bugs.python.org  Tue Oct  8 12:45:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 16:45:53 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1570553153.73.0.585933176308.issue37531@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 0ec618af98ac250a91ee9c91f8569e6df6772758 by Victor Stinner in branch 'master':
bpo-37531: regrtest ignores output on timeout (GH-16659)
https://github.com/python/cpython/commit/0ec618af98ac250a91ee9c91f8569e6df6772758


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Tue Oct  8 12:45:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 16:45:53 +0000
Subject: [issue38207] subprocess: On Windows,
 Popen.kill() + Popen.communicate() is blocking until all processes
 using the pipe close the pipe
In-Reply-To: <1568763048.2.0.765446302919.issue38207@roundup.psfhosted.org>
Message-ID: <1570553153.65.0.825243791179.issue38207@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 0ec618af98ac250a91ee9c91f8569e6df6772758 by Victor Stinner in branch 'master':
bpo-37531: regrtest ignores output on timeout (GH-16659)
https://github.com/python/cpython/commit/0ec618af98ac250a91ee9c91f8569e6df6772758


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38207>
_______________________________________

From report at bugs.python.org  Tue Oct  8 13:32:00 2019
From: report at bugs.python.org (belegnar)
Date: Tue, 08 Oct 2019 17:32:00 +0000
Subject: [issue38412] csv.reader failed to split string with spaces and quoted
 delimiter
Message-ID: <1570555920.82.0.491270320818.issue38412@roundup.psfhosted.org>


New submission from belegnar <admin at zilantkon.ru>:

```
>>> list(csv.reader(['param1,"param21,param22",param3']))
[['param1', 'param21,param22', 'param3']]
>>> list(csv.reader(['param1, "param21,param22", param3']))
[['param1', ' "param21', 'param22"', ' param3']]
```

version 3.7.4 on linux

----------
components: Library (Lib)
messages: 354224
nosy: belegnar
priority: normal
severity: normal
status: open
title: csv.reader failed to split string with spaces and quoted delimiter
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38412>
_______________________________________

From report at bugs.python.org  Tue Oct  8 13:36:56 2019
From: report at bugs.python.org (Larry Hastings)
Date: Tue, 08 Oct 2019 17:36:56 +0000
Subject: [issue38216] Fix for issue30458 (HTTP Header Injection) prevents
 crafting invalid requests
In-Reply-To: <1568823270.72.0.1365123921.issue38216@roundup.psfhosted.org>
Message-ID: <1570556216.94.0.33019580289.issue38216@roundup.psfhosted.org>


Larry Hastings <larry at hastings.org> added the comment:


New changeset 2784e78dc3445c6dd59e915d86c336374c1fa09a by larryhastings (Jason R. Coombs) in branch '3.5':
[3.5] bpo-38216, bpo-36274: Allow subclasses to separately override validation and encoding behavior (GH-16448) (#16475)
https://github.com/python/cpython/commit/2784e78dc3445c6dd59e915d86c336374c1fa09a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38216>
_______________________________________

From report at bugs.python.org  Tue Oct  8 13:36:57 2019
From: report at bugs.python.org (Larry Hastings)
Date: Tue, 08 Oct 2019 17:36:57 +0000
Subject: [issue36274] http.client cannot send non-ASCII request lines
In-Reply-To: <1552422803.93.0.420596825145.issue36274@roundup.psfhosted.org>
Message-ID: <1570556217.12.0.953053993671.issue36274@roundup.psfhosted.org>


Larry Hastings <larry at hastings.org> added the comment:


New changeset 2784e78dc3445c6dd59e915d86c336374c1fa09a by larryhastings (Jason R. Coombs) in branch '3.5':
[3.5] bpo-38216, bpo-36274: Allow subclasses to separately override validation and encoding behavior (GH-16448) (#16475)
https://github.com/python/cpython/commit/2784e78dc3445c6dd59e915d86c336374c1fa09a


----------
nosy: +larry

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36274>
_______________________________________

From report at bugs.python.org  Tue Oct  8 13:37:30 2019
From: report at bugs.python.org (Larry Hastings)
Date: Tue, 08 Oct 2019 17:37:30 +0000
Subject: [issue38216] Fix for issue30458 (HTTP Header Injection) prevents
 crafting invalid requests
In-Reply-To: <1568823270.72.0.1365123921.issue38216@roundup.psfhosted.org>
Message-ID: <1570556250.56.0.973799147062.issue38216@roundup.psfhosted.org>


Change by Larry Hastings <larry at hastings.org>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38216>
_______________________________________

From report at bugs.python.org  Tue Oct  8 13:47:27 2019
From: report at bugs.python.org (Eli Schwartz)
Date: Tue, 08 Oct 2019 17:47:27 +0000
Subject: [issue1724822] provide a shlex.split alternative for Windows shell
 syntax
Message-ID: <1570556847.62.0.715349478609.issue1724822@roundup.psfhosted.org>


Change by Eli Schwartz <eschwartz93 at gmail.com>:


----------
nosy: +eschwartz

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1724822>
_______________________________________

From report at bugs.python.org  Tue Oct  8 14:13:05 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Tue, 08 Oct 2019 18:13:05 +0000
Subject: [issue31722] _io.IncrementalNewlineDecoder doesn't inherit
 codecs.IncrementalDecoder
In-Reply-To: <1507386401.5.0.213398074469.issue31722@psf.upfronthosting.co.za>
Message-ID: <1570558385.51.0.526208294829.issue31722@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
pull_requests: +16247
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16664

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31722>
_______________________________________

From report at bugs.python.org  Tue Oct  8 14:46:56 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Tue, 08 Oct 2019 18:46:56 +0000
Subject: [issue31722] _io.IncrementalNewlineDecoder doesn't inherit
 codecs.IncrementalDecoder
In-Reply-To: <1507386401.5.0.213398074469.issue31722@psf.upfronthosting.co.za>
Message-ID: <1570560416.97.0.454249409365.issue31722@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
nosy: +corona10

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31722>
_______________________________________

From report at bugs.python.org  Tue Oct  8 15:01:21 2019
From: report at bugs.python.org (Ronan Lamy)
Date: Tue, 08 Oct 2019 19:01:21 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570561281.62.0.713782954572.issue38109@roundup.psfhosted.org>


Change by Ronan Lamy <ronan.lamy at gmail.com>:


----------
keywords: +patch
pull_requests: +16248
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16665

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Tue Oct  8 15:24:03 2019
From: report at bugs.python.org (Aviral)
Date: Tue, 08 Oct 2019 19:24:03 +0000
Subject: [issue38307] Provide Class' end line in readmodule module
In-Reply-To: <1569691590.29.0.185701662636.issue38307@roundup.psfhosted.org>
Message-ID: <1570562643.88.0.19773826804.issue38307@roundup.psfhosted.org>


Change by Aviral <hi at aviralsrivastava.com>:


----------
keywords: +patch
pull_requests: +16249
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16466

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38307>
_______________________________________

From report at bugs.python.org  Tue Oct  8 15:30:42 2019
From: report at bugs.python.org (Vladimir Ryabtsev)
Date: Tue, 08 Oct 2019 19:30:42 +0000
Subject: [issue38413] Remove or change "Multithreading" section
Message-ID: <1570563042.6.0.0902531064636.issue38413@roundup.psfhosted.org>


New submission from Vladimir Ryabtsev <greatvovan at gmail.com>:

This is regarding the page https://docs.python.org/3.7/library/sqlite3.html.

I believe this section on the very bottom of the page has been kept here for pretty long time, during that both SQLite and the sqlite3 module evolved and improved. Now the content contradicts to the description of function "connect()" in the part describing "check_same_thread" parameter. The function description says that using connections from multiple threads is allowed with serialization handled by the user (and it is true), while the bottom "Mutithreading" section says sharing connections is not allowed.

I think we can remove "Mutithreading" section entirely unless there is something important to add to what already mentioned.

----------
assignee: docs at python
components: Documentation
messages: 354227
nosy: Vladimir Ryabtsev, docs at python
priority: normal
severity: normal
status: open
title: Remove or change "Multithreading" section
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38413>
_______________________________________

From report at bugs.python.org  Tue Oct  8 15:51:36 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Tue, 08 Oct 2019 19:51:36 +0000
Subject: [issue38307] Provide Class' end line in readmodule module
In-Reply-To: <1569691590.29.0.185701662636.issue38307@roundup.psfhosted.org>
Message-ID: <1570564296.8.0.0891052811631.issue38307@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
nosy: +brandtbucher

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38307>
_______________________________________

From report at bugs.python.org  Tue Oct  8 15:57:40 2019
From: report at bugs.python.org (Umar Asghar)
Date: Tue, 08 Oct 2019 19:57:40 +0000
Subject: [issue38414] Ordering a nested dictionary in python with json format
Message-ID: <1570564660.13.0.727592441748.issue38414@roundup.psfhosted.org>


New submission from Umar Asghar <mrumarasghar at gmail.com>:

Python does not preserve ordering in JSON format. I have tested it out but it's not working. Here is my code.

# Python3 code to demonstrate 
# Sort nested dictionary by key 
# using OrderedDict() + sorted() 
from collections import OrderedDict 
from operator import getitem 
import json

# initializing dictionary 
test_dict = {'Nikhil' : { 'roll' : 24, 'marks' : 17}, 
            'Akshat' : {'roll' : 54, 'marks' : 12}, 
            'Akash' : { 'roll' : 12, 'marks' : 15}} 

# printing original dict 
print("The original dictionary : " + str(test_dict)) 

# using OrderedDict() + sorted() 
# Sort nested dictionary by key 
res = OrderedDict(sorted(test_dict.items(), 
    key = lambda x: getitem(x[1], 'marks'))) 

print("The sorted dictionary by marks is : " + str(res))
# Output
# The sorted dictionary by marks is : OrderedDict([('Akshat', {'marks': 12, 'roll': 54}), ('Akash', {'marks': 15, 'roll': 12}), ('Nikhil', {'marks': 17, 'roll': 24})])

res = json.dumps(res)

# print result 
print("The sorted dictionary by marks is : (json)")
print(json.loads(res)) 
# Output
# The sorted dictionary by marks is : 
# {'Akash': {'marks': 15, 'roll': 12}, 'Akshat': {'marks': 12, 'roll': 54}, 'Nikhil': {'marks': 17, 'roll': 24}}
Does anyone suggest any solution for it?

It's different than a simple dictionary. It only targets the nested dictionary ordering. Please don't mark it a duplication of simple dictionary ordering with JSON. thanks

----------
messages: 354228
nosy: Umar Asghar
priority: normal
severity: normal
status: open
title: Ordering a nested dictionary in python with json format

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38414>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:00:18 2019
From: report at bugs.python.org (Umar Asghar)
Date: Tue, 08 Oct 2019 20:00:18 +0000
Subject: [issue38414] Ordering a nested dictionary in python with json format
In-Reply-To: <1570564660.13.0.727592441748.issue38414@roundup.psfhosted.org>
Message-ID: <1570564818.23.0.676198758798.issue38414@roundup.psfhosted.org>


Umar Asghar <mrumarasghar at gmail.com> added the comment:

I guess it exists in all Python versions. I have tested in both Python 2 and Python 3.

Python 2.7.15+ (default, Jul  9 2019, 16:51:35) 
[GCC 7.4.0] on linux2

Python 3.6.8 (default, Aug 20 2019, 17:12:48) 
[GCC 8.3.0] on linux

----------
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38414>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:03:24 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Tue, 08 Oct 2019 20:03:24 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570565004.02.0.00552834220564.issue38109@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
nosy: +brandtbucher

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:17:27 2019
From: report at bugs.python.org (Umar Asghar)
Date: Tue, 08 Oct 2019 20:17:27 +0000
Subject: [issue38414] Ordering a nested dictionary in python with json format
In-Reply-To: <1570564660.13.0.727592441748.issue38414@roundup.psfhosted.org>
Message-ID: <1570565847.11.0.667042423587.issue38414@roundup.psfhosted.org>


Change by Umar Asghar <mrumarasghar at gmail.com>:


Added file: https://bugs.python.org/file48649/test.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38414>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:25:48 2019
From: report at bugs.python.org (Umar Asghar)
Date: Tue, 08 Oct 2019 20:25:48 +0000
Subject: [issue38414] Ordering a nested dictionary in python with json format
In-Reply-To: <1570564660.13.0.727592441748.issue38414@roundup.psfhosted.org>
Message-ID: <1570566348.6.0.908214448004.issue38414@roundup.psfhosted.org>


Umar Asghar <mrumarasghar at gmail.com> added the comment:

I have recently attached the file, please review it as a code reference.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38414>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:26:07 2019
From: report at bugs.python.org (Hansraj Das)
Date: Tue, 08 Oct 2019 20:26:07 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570566367.23.0.683681624357.issue38409@roundup.psfhosted.org>


Change by Hansraj Das <raj.das.136 at gmail.com>:


----------
nosy: +hansrajdas

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:26:47 2019
From: report at bugs.python.org (Umar Asghar)
Date: Tue, 08 Oct 2019 20:26:47 +0000
Subject: [issue38414] Ordering a nested dictionary in python with json format
In-Reply-To: <1570564660.13.0.727592441748.issue38414@roundup.psfhosted.org>
Message-ID: <1570566407.56.0.234342185184.issue38414@roundup.psfhosted.org>


Change by Umar Asghar <mrumarasghar at gmail.com>:


----------
versions: +Python 2.7 -Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38414>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:38:14 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 20:38:14 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570567094.6.0.679240789079.issue38395@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 526ef856dd598fd3cefdfadeb18ede7a8e57aa41 by Pablo Galindo in branch '3.8':
[3.8] bpo-38395: Fix ownership in weakref.proxy methods (GH-16632) (GH-16662)
https://github.com/python/cpython/commit/526ef856dd598fd3cefdfadeb18ede7a8e57aa41


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:38:32 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 20:38:32 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570567112.06.0.801778720372.issue38395@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
priority: release blocker -> normal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:45:49 2019
From: report at bugs.python.org (Jason Fried)
Date: Tue, 08 Oct 2019 20:45:49 +0000
Subject: [issue38415] @asynccontextmanager decorated functions are not
 callable like @contextmanager
Message-ID: <1570567549.28.0.993731185011.issue38415@roundup.psfhosted.org>


New submission from Jason Fried <me at jasonfried.info>:

The standard contextmanager decorator produces a wrapper that itself can be used as a decorator

```
@contextmanager
def some_context():
    ...
    yield

@some_context()
def some_function():
    # we are inside a with some_context() now. 
    ...


```

When I created a version of asynccontextmanager internally before it was available in the  stdLib I copied this behavior and I have people internally to facebook using this behavior,  Was there a reason this behavior was not replicated to asynccontextmanager?  

I have a diff an tests to add

----------
components: Library (Lib)
messages: 354232
nosy: fried, yselivanov
priority: normal
severity: normal
status: open
title: @asynccontextmanager decorated functions are not callable like @contextmanager
type: enhancement
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38415>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:57:33 2019
From: report at bugs.python.org (Jason Fried)
Date: Tue, 08 Oct 2019 20:57:33 +0000
Subject: [issue38415] @asynccontextmanager decorated functions are not
 callable like @contextmanager
In-Reply-To: <1570567549.28.0.993731185011.issue38415@roundup.psfhosted.org>
Message-ID: <1570568253.64.0.335862852666.issue38415@roundup.psfhosted.org>


Change by Jason Fried <me at jasonfried.info>:


----------
keywords: +patch
pull_requests: +16250
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16667

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38415>
_______________________________________

From report at bugs.python.org  Tue Oct  8 16:59:08 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Tue, 08 Oct 2019 20:59:08 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570568348.98.0.361156871394.issue38368@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset e8bedbddadaa86be6bd86dc32dbdbd53933a4988 by Vinay Sajip in branch 'master':
bpo-38368: Added fix for ctypes crash when handling arrays in structs? (GH-16589)
https://github.com/python/cpython/commit/e8bedbddadaa86be6bd86dc32dbdbd53933a4988


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Tue Oct  8 17:03:43 2019
From: report at bugs.python.org (Zachary Ware)
Date: Tue, 08 Oct 2019 21:03:43 +0000
Subject: [issue34957] Segementation faults on ARM and ARM64
In-Reply-To: <1539251006.2.0.788709270274.issue34957@psf.upfronthosting.co.za>
Message-ID: <1570568623.69.0.794119252513.issue34957@roundup.psfhosted.org>


Change by Zachary Ware <zachary.ware at gmail.com>:


----------
resolution: works for me -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34957>
_______________________________________

From report at bugs.python.org  Tue Oct  8 17:14:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 21:14:26 +0000
Subject: [issue38416] test_largefile.TestSocketSendfile.test_it() failed with
 15 min timeout on AMD64 FreeBSD 10-STABLE Non-Debug 3.x
Message-ID: <1570569266.33.0.0795173642593.issue38416@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

It seems like the 15 min timeout for the overall test_largefile is too short for the very slow AMD64 FreeBSD 10-STABLE Non-Debug 3.x buildbot.

The test creates two files of 2.5 GB on the disk.

One solution is to skip the test on this buildbot worker. For example, using a test resource like "largefile","cpu" resource, or another one. Maybe only skip TestSocketSendfile.test_it(), or even skip for the whole file. Currently, the whole file requires the "largefile" resource, but only on Windows and macOS.

Right now, the buildbot worker runs the test suite using:

   ./python  ./Tools/scripts/run_tests.py -j 1 -u all -W --slowest --fail-env-changed --timeout=900 -j2 -j4 

So all resources are enabled.

--

https://buildbot.python.org/all/#/builders/167/builds/1695

test_it (test.test_largefile.TestCopyfile) ... ok
Timeout (0:15:00)!
Thread 0x0000000806c95400 (most recent call first):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/test_largefile.py", line 193 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/threading.py", line 882 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/threading.py", line 944 in _bootstrap_inner
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/threading.py", line 902 in _bootstrap

Thread 0x0000000801c06400 (most recent call first):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/socket.py", line 386 in _sendfile_use_sendfile
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/socket.py", line 483 in sendfile
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/test_largefile.py", line 207 in test_it
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/unittest/case.py", line 616 in _callTestMethod
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/unittest/case.py", line 659 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/unittest/case.py", line 719 in __call__
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/unittest/suite.py", line 122 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/unittest/suite.py", line 84 in __call__
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/unittest/suite.py", line 122 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/unittest/suite.py", line 84 in __call__
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/unittest/suite.py", line 122 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/unittest/suite.py", line 84 in __call__
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/unittest/runner.py", line 176 in run
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/support/__init__.py", line 2032 in _run_suite
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/support/__init__.py", line 2128 in run_unittest
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/libregrtest/runtest.py", line 209 in _test_module
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/libregrtest/runtest.py", line 234 in _runtest_inner2
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/libregrtest/runtest.py", line 270 in _runtest_inner
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/libregrtest/runtest.py", line 153 in _runtest
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/libregrtest/runtest.py", line 193 in runtest
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/libregrtest/main.py", line 318 in rerun_failed_tests
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/libregrtest/main.py", line 691 in _main
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/libregrtest/main.py", line 634 in main
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/libregrtest/main.py", line 712 in main
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/test/__main__.py", line 2 in <module>
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/runpy.py", line 85 in _run_code
  File "/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Lib/runpy.py", line 192 in _run_module_as_main
test_it (test.test_largefile.TestSocketSendfile) ... *** Error code 1

----------
components: Tests
messages: 354234
nosy: giampaolo.rodola, pablogsal, vstinner
priority: normal
severity: normal
status: open
title: test_largefile.TestSocketSendfile.test_it() failed with 15 min timeout on AMD64 FreeBSD 10-STABLE Non-Debug 3.x
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38416>
_______________________________________

From report at bugs.python.org  Tue Oct  8 17:15:28 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 21:15:28 +0000
Subject: [issue38416] test_largefile.TestSocketSendfile.test_it() failed with
 15 min timeout on AMD64 FreeBSD 10-STABLE Non-Debug 3.x
In-Reply-To: <1570569266.33.0.0795173642593.issue38416@roundup.psfhosted.org>
Message-ID: <1570569328.54.0.801359123196.issue38416@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

On the previous build, the test failed with timeout while other tests were running in parallel, and then the test passed ... in 14 min 43 seconds... which is very close to the limit of 15 minutes :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38416>
_______________________________________

From report at bugs.python.org  Tue Oct  8 17:16:19 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 21:16:19 +0000
Subject: [issue38416] test_largefile.TestSocketSendfile.test_it() failed with
 15 min timeout on AMD64 FreeBSD 10-STABLE Non-Debug 3.x
In-Reply-To: <1570569266.33.0.0795173642593.issue38416@roundup.psfhosted.org>
Message-ID: <1570569379.36.0.325466957366.issue38416@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Another approach is to change the timeout of 15 min for this super slow buildbot. For example, set it to 20 min or 30 min.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38416>
_______________________________________

From report at bugs.python.org  Tue Oct  8 18:00:15 2019
From: report at bugs.python.org (Umar Asghar)
Date: Tue, 08 Oct 2019 22:00:15 +0000
Subject: [issue38414] Ordering a nested dictionary in python with json format
In-Reply-To: <1570564660.13.0.727592441748.issue38414@roundup.psfhosted.org>
Message-ID: <1570572015.41.0.707558807656.issue38414@roundup.psfhosted.org>


Umar Asghar <mrumarasghar at gmail.com> added the comment:

Please ignore the above shared sample data in the above code and consider this one.

this is the exact code that is misbehaving in python 2.7


# Sort nested dictionary by key
# using OrderedDict() + sorted()
from collections import OrderedDict
from operator import getitem
import json

# initializing dictionary
test_dict = {'3' : { 'roll' : 24, 'marks' : 17},
            '2' : {'roll' : 54, 'marks' : 12},
            '1' : { 'roll' : 12, 'marks' : 15}}

# printing original dict
print("The original dictionary : " + str(test_dict))

# using OrderedDict() + sorted()
# Sort nested dictionary by key
res = OrderedDict(sorted(test_dict.items(),
    key = lambda x: getitem(x[1], 'marks')))

print("The sorted dictionary by marks is : " + str(res))
# Output
# The sorted dictionary by marks is : OrderedDict([('2', {'roll': 54, 'marks': 12}), ('1', {'roll': 12, 'marks': 15}), ('3', {'roll': 24, 'marks': 17})])

res1 = json.dumps(res)

# print result
print("The sorted dictionary by marks is : (json)")
print(json.loads(res1))
# Output
# The sorted dictionary by marks is : (json)
# {u'1': {u'roll': 12, u'marks': 15}, u'3': {u'roll': 24, u'marks': 17}, u'2': {u'roll': 54, u'marks': 12}}

----------
Added file: https://bugs.python.org/file48650/bug.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38414>
_______________________________________

From report at bugs.python.org  Tue Oct  8 18:02:34 2019
From: report at bugs.python.org (Umar Asghar)
Date: Tue, 08 Oct 2019 22:02:34 +0000
Subject: [issue38414] Ordering a nested dictionary in python with json format
In-Reply-To: <1570564660.13.0.727592441748.issue38414@roundup.psfhosted.org>
Message-ID: <1570572154.98.0.3883011043.issue38414@roundup.psfhosted.org>


Change by Umar Asghar <mrumarasghar at gmail.com>:


----------
type:  -> enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38414>
_______________________________________

From report at bugs.python.org  Tue Oct  8 18:55:39 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 08 Oct 2019 22:55:39 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
Message-ID: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>


New submission from Gregory P. Smith <greg at krypto.org>:

Another use of the deprecated unsafe preexec_fn was to call os.umask in the child prior to exec.

As seen in https://github.com/freeipa/freeipa/pull/3769 (see the code in there).

We should add an explicit feature for this to avoid people's desire for preexec_fn or for the heavyweight workaround of an intermediate shell calling umask before doing another exec.

Any common preexec_fn uses that we can encode into supported parameters will help our ability to remove the ill fated preexec_fn misfeature in the future.

----------
messages: 354238
nosy: gregory.p.smith
priority: high
severity: normal
stage: needs patch
status: open
title: Add support for settting umask in subprocess children
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Tue Oct  8 19:00:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 08 Oct 2019 23:00:46 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570575646.06.0.969902087971.issue38417@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> We should add an explicit feature for this

If we need to write a wrapper program for that, I would say that no, we don't "have to" provide something in the stdlib.

In OpenStack, I wrote prlimit.py which is a preexec-like wrapper program to apply resource limits when calling a program. It's just a pure Python implementation of the Unix prlimit program. The Python implementation is used when the prlimit progrma is not available.

https://github.com/openstack/oslo.concurrency/blob/master/oslo_concurrency/prlimit.py

IMHO it's perfectly fine to explain that a wrapper program is needed to implement preexec-like features.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Tue Oct  8 19:05:28 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 08 Oct 2019 23:05:28 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570575928.32.0.65473180024.issue38379@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Tue Oct  8 19:06:10 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 08 Oct 2019 23:06:10 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570575970.2.0.0641925650757.issue38417@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

We don't have to for all possible things, doing this just reduced friction for existing uses.  In this case, calling umask in our child ourselves would be easy to support.  (easier than the more important setuid/sid/gid/groups-ish stuff that recently went in)

I'm trying to make sure we track what is blocking people from getting rid of preexec_fn in their existing code so that we can actually deprecate and get rid of the API entirely.

----------
priority: high -> normal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Tue Oct  8 20:32:44 2019
From: report at bugs.python.org (Warren Weckesser)
Date: Wed, 09 Oct 2019 00:32:44 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570581164.97.0.236739462384.issue38382@roundup.psfhosted.org>


Warren Weckesser <warren.weckesser at gmail.com> added the comment:

One more case where the "early out" produces a result that seems wrong:

In [20]: harmonic_mean([math.nan, 0])                                           
Out[20]: 0

Anyone who didn't know about the "early out" behavior would probably expect the result to be NAN.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Tue Oct  8 20:51:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 09 Oct 2019 00:51:47 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570582307.02.0.720758850098.issue38417@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> I'm trying to make sure we track what is blocking people from getting rid of preexec_fn in their existing code so that we can actually deprecate and get rid of the API entirely.

If you consider posix_spawn(), I think that a convenient replacement for preexec_fn function would be a wrapper process which would execute *arbitrary Python code* before spawning the program.

It would not only cover umask case, but also prlimit, and another other custom code.

Pseudo-code of the wrapper:

  import sys
  code = sys.argv[1]
  argv = sys.argv[2:]
  eval(code)
  os.execv(argv[0], argv)

The main risk is that the arbitrary code could create an inheritable file descriptor (not all C extensions respect the PEP 446) which would survive after replacing the process memory with the new program.

Such design would allow to implement it in a third party package (on PyPI) for older Python versions as well.

--

Currently, preexec_fn is a direct reference to a callable Python object in the current process. preexec_fn calls it just after fork().

Here I'm talking about running arbitrary Python code in a freshly spawned Python process. It's different.

--

The new problems are:

* How to ensure that Python is configured as expected? Use -I command line option? Use -S to not import the site module? 
* How to report a Python exception from the child to the parent process? Build a pipe between the two processes and serialize the exception, as we are already doing for preexec_fn?
* How to report os.execv() failure to the parent? Just something like sys.exit(OSErrno.errno)?
* Should close_fds be implemented in the wrapper as well? If yes, can the parent avoid closing file descriptors?

> https://github.com/openstack/oslo.concurrency/blob/master/oslo_concurrency/prlimit.py

This wrapper uses os.execv().

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Tue Oct  8 22:09:42 2019
From: report at bugs.python.org (Timothy Stonis)
Date: Wed, 09 Oct 2019 02:09:42 +0000
Subject: [issue37677] Seg Fault on OSX when multiprocessing
In-Reply-To: <1564042021.53.0.0155934240157.issue37677@roundup.psfhosted.org>
Message-ID: <1570586982.4.0.353036050893.issue37677@roundup.psfhosted.org>


Timothy Stonis <tim at opoet.com> added the comment:

Hi, I have the exact same issue and same stack trace from getaddrinfo (except Python 2.7). Same as original poster, it only happens every couple of weeks and I don't know how to reproduce. For me it's in an Odoo instance that spawns multiple workers with connections to a postgres database. I think this is a MacOS bug, since the issue does not happen on High Sierra (10.13).

----------
nosy: +timstonis
versions: +Python 2.7 -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37677>
_______________________________________

From report at bugs.python.org  Tue Oct  8 22:19:56 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Wed, 09 Oct 2019 02:19:56 +0000
Subject: [issue36161] Use thread-safe functions instead of unsafe ones (crypt, 
 ttyname)
In-Reply-To: <1551475826.18.0.295115684796.issue36161@roundup.psfhosted.org>
Message-ID: <1570587596.31.0.923812474496.issue36161@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset 594e2edfb5e0d24e03469d035d8f39ff29a64d99 by Benjamin Peterson (Antonio Gutierrez) in branch 'master':
closes bpo-36161: Use thread-safe ttyname_r instead of ttyname. (GH-14868)
https://github.com/python/cpython/commit/594e2edfb5e0d24e03469d035d8f39ff29a64d99


----------
nosy: +benjamin.peterson
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36161>
_______________________________________

From report at bugs.python.org  Tue Oct  8 22:28:04 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 09 Oct 2019 02:28:04 +0000
Subject: [issue38418] Audit event for os.system is incorrect
Message-ID: <1570588084.56.0.375267797277.issue38418@roundup.psfhosted.org>


New submission from Steve Dower <steve.dower at python.org>:

It's documented as "os.system" but implemented as just "system".

----------
assignee: steve.dower
messages: 354245
nosy: lukasz.langa, steve.dower
priority: normal
severity: normal
status: open
title: Audit event for os.system is incorrect
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38418>
_______________________________________

From report at bugs.python.org  Tue Oct  8 22:30:43 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 09 Oct 2019 02:30:43 +0000
Subject: [issue38418] Audit event for os.system is incorrect
In-Reply-To: <1570588084.56.0.375267797277.issue38418@roundup.psfhosted.org>
Message-ID: <1570588243.87.0.845051006283.issue38418@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords: +patch
pull_requests: +16251
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16670

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38418>
_______________________________________

From report at bugs.python.org  Tue Oct  8 22:45:31 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 09 Oct 2019 02:45:31 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570589131.16.0.0666006868712.issue38382@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee: rhettinger -> steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Tue Oct  8 23:48:05 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 09 Oct 2019 03:48:05 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
Message-ID: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>


New submission from Dong-hee Na <donghee.na92 at gmail.com>:

See https://github.com/python/cpython/blob/01171ebd966b0cd6352057799ad876dd1e07942e/Tools/c-analyzer/README#L37

----------
keywords: newcomer friendly
messages: 354246
nosy: corona10
priority: normal
severity: normal
status: open
title: The path of check-c-globals.py on README is wrong

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Tue Oct  8 23:49:06 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 09 Oct 2019 03:49:06 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
In-Reply-To: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>
Message-ID: <1570592946.0.0.924917514591.issue38419@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

This is newcomer friendly issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Wed Oct  9 01:17:20 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 09 Oct 2019 05:17:20 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570598240.45.0.0470432340366.issue38368@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
keywords: +patch
pull_requests: +16252
pull_request: https://github.com/python/cpython/pull/16671

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Wed Oct  9 01:31:00 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 09 Oct 2019 05:31:00 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570599060.07.0.517980805361.issue38368@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests: +16253
pull_request: https://github.com/python/cpython/pull/16672

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Wed Oct  9 01:34:30 2019
From: report at bugs.python.org (Larry Hastings)
Date: Wed, 09 Oct 2019 05:34:30 +0000
Subject: [issue38174] Security vulnerability in bundled expat CVE-2019-15903
 (fix available in expat 2.2.8)
In-Reply-To: <1568491807.22.0.03411253388.issue38174@roundup.psfhosted.org>
Message-ID: <1570599270.69.0.579864086327.issue38174@roundup.psfhosted.org>


Larry Hastings <larry at hastings.org> added the comment:


New changeset c386c8b06c6e92786f083ef6aba27b37087fdd20 by larryhastings (Victor Stinner) in branch '3.5':
closes bpo-38174: Update vendored expat library to 2.2.8. (GH-16346) (#16434)
https://github.com/python/cpython/commit/c386c8b06c6e92786f083ef6aba27b37087fdd20


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38174>
_______________________________________

From report at bugs.python.org  Wed Oct  9 01:48:01 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 09 Oct 2019 05:48:01 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570600081.87.0.270405982787.issue38368@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset d004a5b082d0770682e6efbf03105a67469d4820 by Vinay Sajip in branch '3.8':
bpo-38368: Added fix for ctypes crash when handling arrays in structs/unions. (GH-16589) (GH-16671)
https://github.com/python/cpython/commit/d004a5b082d0770682e6efbf03105a67469d4820


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Wed Oct  9 01:48:50 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 09 Oct 2019 05:48:50 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570600130.72.0.544997300332.issue38368@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset 129c2b3d44a962fc5964ef8fd4e6b22dbb691a6c by Vinay Sajip in branch '3.7':
bpo-38368: Added fix for ctypes crash when handling arrays in structs/unions. (GH-16589) (GH-16672)
https://github.com/python/cpython/commit/129c2b3d44a962fc5964ef8fd4e6b22dbb691a6c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Wed Oct  9 01:53:37 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 09 Oct 2019 05:53:37 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1570600416.99.0.882867962538.issue38368@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Wed Oct  9 02:18:06 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2019 06:18:06 +0000
Subject: [issue38414] Ordering a nested dictionary in python with json format
In-Reply-To: <1570564660.13.0.727592441748.issue38414@roundup.psfhosted.org>
Message-ID: <1570601886.41.0.0890141795428.issue38414@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Dictionary preserve the insertion order starting from Python 3.7 (actually from 3.6, but it was not guarantied). I am surprised that you got different result in 3.6. I cannot reproduce it.

In older Python versions you can pass object_pairs_hook=OrderedDict to json.loads() to preserve the insertion order. The regular dictionary cannot preserve it, by its structure.

----------
nosy: +serhiy.storchaka
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38414>
_______________________________________

From report at bugs.python.org  Wed Oct  9 03:32:22 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 09 Oct 2019 07:32:22 +0000
Subject: [issue38412] csv.reader failed to split string with spaces and quoted
 delimiter
In-Reply-To: <1570555920.82.0.491270320818.issue38412@roundup.psfhosted.org>
Message-ID: <1570606342.0.0.509527497744.issue38412@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Can you please add a description of the expected behavior? Does skipinitialspace help with the second input?

https://docs.python.org/3/library/csv.html#csv.Dialect.skipinitialspace

>>> import csv
>>> list(csv.reader(['param1,"param21,param22",param3']))
[['param1', 'param21,param22', 'param3']]
>>> list(csv.reader(['param1, "param21,param22", param3']))
[['param1', ' "param21', 'param22"', ' param3']]
>>> list(csv.reader(['param1, "param21,param22", param3'], skipinitialspace=True))
[['param1', 'param21,param22', 'param3']]
>>> list(csv.reader(['param1,"param21,param22",param3'])) == list(csv.reader(['param1, "param21,param22", param3'], skipinitialspace=True))
True

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38412>
_______________________________________

From report at bugs.python.org  Wed Oct  9 03:58:06 2019
From: report at bugs.python.org (belegnar)
Date: Wed, 09 Oct 2019 07:58:06 +0000
Subject: [issue38412] csv.reader failed to split string with spaces and quoted
 delimiter
In-Reply-To: <1570555920.82.0.491270320818.issue38412@roundup.psfhosted.org>
Message-ID: <1570607886.59.0.788994747467.issue38412@roundup.psfhosted.org>


belegnar <admin at zilantkon.ru> added the comment:

Yes, https://docs.python.org/3/library/csv.html#csv.Dialect.skipinitialspace helps
Sorry

----------
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38412>
_______________________________________

From report at bugs.python.org  Wed Oct  9 04:21:15 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 09 Oct 2019 08:21:15 +0000
Subject: [issue38412] csv.reader failed to split string with spaces and quoted
 delimiter
In-Reply-To: <1570555920.82.0.491270320818.issue38412@roundup.psfhosted.org>
Message-ID: <1570609275.2.0.159716051009.issue38412@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

No problem, happy it helped :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38412>
_______________________________________

From report at bugs.python.org  Wed Oct  9 04:21:25 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 09 Oct 2019 08:21:25 +0000
Subject: [issue38412] csv.reader failed to split string with spaces and quoted
 delimiter
In-Reply-To: <1570555920.82.0.491270320818.issue38412@roundup.psfhosted.org>
Message-ID: <1570609285.04.0.547861783027.issue38412@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
resolution:  -> not a bug

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38412>
_______________________________________

From report at bugs.python.org  Wed Oct  9 04:22:42 2019
From: report at bugs.python.org (wang xuancong)
Date: Wed, 09 Oct 2019 08:22:42 +0000
Subject: [issue38420] defaultdict does not support parametric lambda
Message-ID: <1570609362.26.0.380213879875.issue38420@roundup.psfhosted.org>


New submission from wang xuancong <xuancong84 at gmail.com>:

A very common use of defaultdict is that if the key exist, use the corresponding mapped target, if the key does not exist, use the key itself. However, current Python 2/3 defaultdict does not support parametric lambda function:

>>> from collections import *
>>> aa=defaultdict(lambda t:t)
>>> aa
defaultdict(<function <lambda> at 0x10a55c950>, {})
>>> aa[0]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: <lambda>() missing 1 required positional argument: 't'
>>>

I would like to suggest that use the dict's query key as the first argument in the default lambda function. And use the dict itself as the 2nd argument in the default lambda function (e.g., if the key exist, use the mapped target, otherwise, use the size of the current defaultdict). I think that will make Python much more powerful than any other programming language. Anyone can think of any additional information for the default lambda function? Thanks!

----------
messages: 354255
nosy: xuancong84
priority: normal
severity: normal
status: open
title: defaultdict does not support parametric lambda
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38420>
_______________________________________

From report at bugs.python.org  Wed Oct  9 04:42:27 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Wed, 09 Oct 2019 08:42:27 +0000
Subject: [issue38420] defaultdict does not support parametric lambda
In-Reply-To: <1570609362.26.0.380213879875.issue38420@roundup.psfhosted.org>
Message-ID: <1570610547.43.0.196938338691.issue38420@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

All versions below 3.9 are in feature freeze, so they cannot get new features.

This requested feature is already supported by subclassing ``dict`` and giving it a ``__missing__`` method. See issue #38315

----------
nosy: +steven.daprano
resolution:  -> rejected
stage:  -> resolved
status: open -> closed
versions:  -Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38420>
_______________________________________

From report at bugs.python.org  Wed Oct  9 04:49:23 2019
From: report at bugs.python.org (wang xuancong)
Date: Wed, 09 Oct 2019 08:49:23 +0000
Subject: [issue38315] Provide defaultdict variant that passes key to
 default_factory
In-Reply-To: <1569773559.86.0.293665151535.issue38315@roundup.psfhosted.org>
Message-ID: <1570610963.29.0.345406566651.issue38315@roundup.psfhosted.org>


wang xuancong <xuancong84 at gmail.com> added the comment:

I agree with Mark Amery.
The reason why defaultdict still exists given that everything can be achieved by subclassing the built-in dict is because of convenience. I suggest maybe Python developer can put it into low priority instead.

----------
nosy: +xuancong84

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38315>
_______________________________________

From report at bugs.python.org  Wed Oct  9 05:02:35 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2019 09:02:35 +0000
Subject: [issue38407] Add docstrings for typing.SupportsXXX classes
In-Reply-To: <1570525184.08.0.803412577085.issue38407@roundup.psfhosted.org>
Message-ID: <1570611755.3.0.766652113514.issue38407@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16254
pull_request: https://github.com/python/cpython/pull/16673

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38407>
_______________________________________

From report at bugs.python.org  Wed Oct  9 05:06:43 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2019 09:06:43 +0000
Subject: [issue38405] Nested subclasses of typing.NamedTuple are not pickleable
In-Reply-To: <1570522682.37.0.234893155024.issue38405@roundup.psfhosted.org>
Message-ID: <1570612003.51.0.707056855339.issue38405@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16255
pull_request: https://github.com/python/cpython/pull/16674

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38405>
_______________________________________

From report at bugs.python.org  Wed Oct  9 05:07:52 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2019 09:07:52 +0000
Subject: [issue38294] Documentation on 3.6->3.7 re.escape no longer escaping
 "/" or ":" should be obvious
In-Reply-To: <1569603997.59.0.0237297108404.issue38294@roundup.psfhosted.org>
Message-ID: <1570612072.04.0.994362637129.issue38294@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Thank you for your contribution Ricardo!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38294>
_______________________________________

From report at bugs.python.org  Wed Oct  9 05:11:52 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 09:11:52 +0000
Subject: [issue36953] Remove collections ABCs?
In-Reply-To: <1558140764.46.0.049733618419.issue36953@roundup.psfhosted.org>
Message-ID: <1570612312.73.0.04660459376.issue36953@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16256
pull_request: https://github.com/python/cpython/pull/16675

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36953>
_______________________________________

From report at bugs.python.org  Wed Oct  9 05:29:38 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 09:29:38 +0000
Subject: [issue36953] Remove collections ABCs?
In-Reply-To: <1558140764.46.0.049733618419.issue36953@roundup.psfhosted.org>
Message-ID: <1570613378.08.0.526977351205.issue36953@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 056fa7f52a49a758b1ed5f5a81d8b7ce5c71cec4 by Miss Islington (bot) in branch '3.7':
bpo-36953: Delay removal of ABCs from collections. (GH-13409)
https://github.com/python/cpython/commit/056fa7f52a49a758b1ed5f5a81d8b7ce5c71cec4


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36953>
_______________________________________

From report at bugs.python.org  Wed Oct  9 05:56:52 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2019 09:56:52 +0000
Subject: [issue38405] Nested subclasses of typing.NamedTuple are not pickleable
In-Reply-To: <1570522682.37.0.234893155024.issue38405@roundup.psfhosted.org>
Message-ID: <1570615012.76.0.814338926861.issue38405@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 87db4d343c9609137f6e62aa3595db610a33842c by Serhiy Storchaka in branch '3.7':
[3.7] bpo-38405: Make nested subclasses of typing.NamedTuple pickleable. (GH-16641). (GH-16674)
https://github.com/python/cpython/commit/87db4d343c9609137f6e62aa3595db610a33842c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38405>
_______________________________________

From report at bugs.python.org  Wed Oct  9 05:57:18 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2019 09:57:18 +0000
Subject: [issue38407] Add docstrings for typing.SupportsXXX classes
In-Reply-To: <1570525184.08.0.803412577085.issue38407@roundup.psfhosted.org>
Message-ID: <1570615038.57.0.0897451785525.issue38407@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 0b354fc2bfe1a4624551907df396ed36ea8bf4ca by Serhiy Storchaka in branch '3.7':
[3.7] bpo-38407: Add docstrings for typing.SupportsXXX classes. (GH-16644). (GH-16673)
https://github.com/python/cpython/commit/0b354fc2bfe1a4624551907df396ed36ea8bf4ca


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38407>
_______________________________________

From report at bugs.python.org  Wed Oct  9 05:58:31 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2019 09:58:31 +0000
Subject: [issue38407] Add docstrings for typing.SupportsXXX classes
In-Reply-To: <1570525184.08.0.803412577085.issue38407@roundup.psfhosted.org>
Message-ID: <1570615111.27.0.279416435836.issue38407@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38407>
_______________________________________

From report at bugs.python.org  Wed Oct  9 05:58:47 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2019 09:58:47 +0000
Subject: [issue38405] Nested subclasses of typing.NamedTuple are not pickleable
In-Reply-To: <1570522682.37.0.234893155024.issue38405@roundup.psfhosted.org>
Message-ID: <1570615127.34.0.338894055606.issue38405@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38405>
_______________________________________

From report at bugs.python.org  Wed Oct  9 06:27:20 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Wed, 09 Oct 2019 10:27:20 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570616840.88.0.350995647145.issue38382@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

> In [20]: harmonic_mean([math.nan, 0])                                           
> Out[20]: 0

That one seems excusable, for the same sort of reasons that IEEE 754 specifies that hypot(nan, inf) is inf rather than nan. Similarly, sumSquare and sumAbs from IEEE 754-2008 specify that infinities take precedence over NaNs, on the basis that the result doesn't change if the nan is replaced with any non-nan value.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Wed Oct  9 06:38:58 2019
From: report at bugs.python.org (hongweipeng)
Date: Wed, 09 Oct 2019 10:38:58 +0000
Subject: [issue28869] __module__ attribute is not set correctly for a class
 created by direct metaclass call
In-Reply-To: <1480885774.84.0.670239959771.issue28869@psf.upfronthosting.co.za>
Message-ID: <1570617538.93.0.324270320766.issue28869@roundup.psfhosted.org>


hongweipeng <hongweichen8888 at sina.com> added the comment:

I think we can refer to typing.py, it does not have this issue.

>>> from typing import NamedTuple
>>> A = NamedTuple('A', [('name', str), ('id', int)])
>>> class B(NamedTuple):
...   name: str
...   id: int
... 
>>> A.__module__
'__main__'
>>> B.__module__
'__main__'


It uses `nm_tpl.__module__ = sys._getframe(2).f_globals.get('__name__', '__main__')`.

----------
nosy: +hongweipeng

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28869>
_______________________________________

From report at bugs.python.org  Wed Oct  9 08:07:22 2019
From: report at bugs.python.org (hai shi)
Date: Wed, 09 Oct 2019 12:07:22 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
In-Reply-To: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>
Message-ID: <1570622842.14.0.204595671506.issue38419@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

Maybe the keyword need add the `easy` wrod? (i don't know the internals)
newcomer need find it in `Easy issues` ;)

----------
nosy: +shihai1991

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Wed Oct  9 08:45:03 2019
From: report at bugs.python.org (David Kernan)
Date: Wed, 09 Oct 2019 12:45:03 +0000
Subject: [issue38421] email.utils.parsetime_tz does not return "None"
Message-ID: <1570625103.37.0.0601159046628.issue38421@roundup.psfhosted.org>


New submission from David Kernan <davidsmurf at gmail.com>:

email.utils.parsetime_tz() is a function which attempts to parse a date, and returns a 10-item tuple.
The first 9 items represents a time, and the last item represents the timezone offset from UTC.

In Python 2, the original behavior was to return the date, and a "None" value when there was no timezone - this is documented here:
https://docs.python.org/3/library/email.utils.html#email.utils.parsedate_tz

In Python 3 however, the code specifically prevents "None" from being returned in place of a UTC offset:
https://github.com/python/cpython/blob/3.7/Lib/email/_parseaddr.py#L53-#L54

The Python 3 documentation for email.utils.parsetime_tz() - is still the same as the 2.7 documentation, and specifically mentions that should a timezone be missing from the string, the last item will be "None"

This isn't the case:

Python 3.6.8:
>>> import email.utils
>>> date_string = 'Wed, 09 Oct 2019 08:32:37'
>>> email.utils.parsedate_tz(date_string)
(2019, 10, 9, 8, 32, 37, 0, 1, -1, 0)
----

Python 2.7.16:
>>> import email.utils
>>> date_string = 'Wed, 09 Oct 2019 08:32:37'
>>> email.utils.parsedate_tz(date_string)
(2019, 10, 9, 8, 32, 37, 0, 1, -1, None)

---

Is this an error in code, or is it a mistake in the documentation?

----------
components: email
messages: 354265
nosy: David Kernan, barry, r.david.murray
priority: normal
severity: normal
status: open
title: email.utils.parsetime_tz does not return "None"
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38421>
_______________________________________

From report at bugs.python.org  Wed Oct  9 08:45:09 2019
From: report at bugs.python.org (David Kernan)
Date: Wed, 09 Oct 2019 12:45:09 +0000
Subject: [issue38421] email.utils.parsetime_tz does not return "None"
In-Reply-To: <1570625103.37.0.0601159046628.issue38421@roundup.psfhosted.org>
Message-ID: <1570625109.73.0.249839458138.issue38421@roundup.psfhosted.org>


Change by David Kernan <davidsmurf at gmail.com>:


----------
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38421>
_______________________________________

From report at bugs.python.org  Wed Oct  9 08:46:31 2019
From: report at bugs.python.org (David Kernan)
Date: Wed, 09 Oct 2019 12:46:31 +0000
Subject: [issue38421] email.utils.parsetime_tz does not return "None" as the
 tz offset
In-Reply-To: <1570625103.37.0.0601159046628.issue38421@roundup.psfhosted.org>
Message-ID: <1570625191.7.0.786053128462.issue38421@roundup.psfhosted.org>


Change by David Kernan <davidsmurf at gmail.com>:


----------
title: email.utils.parsetime_tz does not return "None" -> email.utils.parsetime_tz does not return "None" as the tz offset

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38421>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:02:36 2019
From: report at bugs.python.org (Ido Michael)
Date: Wed, 09 Oct 2019 13:02:36 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570626156.33.0.978516441446.issue38351@roundup.psfhosted.org>


Ido Michael <michael.ido at gmail.com> added the comment:

So what was decided?

I can fix this issue and I can wait for a final conclusion as it wasn't clear from the thread.

----------
nosy: +Ido Michael

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:14:52 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 09 Oct 2019 13:14:52 +0000
Subject: [issue38421] email.utils.parsetime_tz does not return "None" as the
 tz offset
In-Reply-To: <1570625103.37.0.0601159046628.issue38421@roundup.psfhosted.org>
Message-ID: <1570626892.19.0.198295303099.issue38421@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +maxking

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38421>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:20:33 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 09 Oct 2019 13:20:33 +0000
Subject: [issue38421] email.utils.parsetime_tz does not return "None" as the
 tz offset
In-Reply-To: <1570625103.37.0.0601159046628.issue38421@roundup.psfhosted.org>
Message-ID: <1570627233.68.0.764295005249.issue38421@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

It looks like a documentation issue to me given the change and tests made in https://github.com/python/cpython/commit/875048bd4c95ae90c3e541cad681b11436ce1f3f

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38421>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:21:20 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 09 Oct 2019 13:21:20 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
In-Reply-To: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>
Message-ID: <1570627280.89.0.970092748856.issue38419@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
keywords: +easy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:25:23 2019
From: report at bugs.python.org (David Kernan)
Date: Wed, 09 Oct 2019 13:25:23 +0000
Subject: [issue38421] email.utils.parsetime_tz does not return "None" as the
 tz offset
In-Reply-To: <1570625103.37.0.0601159046628.issue38421@roundup.psfhosted.org>
Message-ID: <1570627523.55.0.646908229654.issue38421@roundup.psfhosted.org>


David Kernan <davidsmurf at gmail.com> added the comment:

Ah yes, thanks, this does seem pretty intentional.

I'll submit a PR for the documentation for this method for the affected version.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38421>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:33:55 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 13:33:55 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1570628035.18.0.262965252652.issue37531@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16257
pull_request: https://github.com/python/cpython/pull/16676

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:33:55 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 13:33:55 +0000
Subject: [issue38207] subprocess: On Windows,
 Popen.kill() + Popen.communicate() is blocking until all processes
 using the pipe close the pipe
In-Reply-To: <1568763048.2.0.765446302919.issue38207@roundup.psfhosted.org>
Message-ID: <1570628035.31.0.409762478303.issue38207@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16258
pull_request: https://github.com/python/cpython/pull/16676

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38207>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:34:02 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 13:34:02 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1570628042.42.0.696759751306.issue37531@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16259
pull_request: https://github.com/python/cpython/pull/16677

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:34:02 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 13:34:02 +0000
Subject: [issue38207] subprocess: On Windows,
 Popen.kill() + Popen.communicate() is blocking until all processes
 using the pipe close the pipe
In-Reply-To: <1568763048.2.0.765446302919.issue38207@roundup.psfhosted.org>
Message-ID: <1570628042.53.0.287264872399.issue38207@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16260
pull_request: https://github.com/python/cpython/pull/16677

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38207>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:35:59 2019
From: report at bugs.python.org (David Kernan)
Date: Wed, 09 Oct 2019 13:35:59 +0000
Subject: [issue38421] email.utils.parsetime_tz does not return "None" as the
 tz offset
In-Reply-To: <1570625103.37.0.0601159046628.issue38421@roundup.psfhosted.org>
Message-ID: <1570628159.85.0.321286938167.issue38421@roundup.psfhosted.org>


Change by David Kernan <davidsmurf at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation -email
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38421>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:36:40 2019
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 09 Oct 2019 13:36:40 +0000
Subject: [issue38421] email.utils.parsetime_tz does not return "None" as the
 tz offset
In-Reply-To: <1570625103.37.0.0601159046628.issue38421@roundup.psfhosted.org>
Message-ID: <1570628200.15.0.145793522646.issue38421@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +16261
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16678

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38421>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:36:58 2019
From: report at bugs.python.org (David Kernan)
Date: Wed, 09 Oct 2019 13:36:58 +0000
Subject: [issue38413] Remove or change "Multithreading" section
In-Reply-To: <1570563042.6.0.0902531064636.issue38413@roundup.psfhosted.org>
Message-ID: <1570628218.73.0.475649885304.issue38413@roundup.psfhosted.org>


Change by David Kernan <davidsmurf at gmail.com>:


----------
keywords: +patch
pull_requests: +16262
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16678

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38413>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:37:21 2019
From: report at bugs.python.org (David Kernan)
Date: Wed, 09 Oct 2019 13:37:21 +0000
Subject: [issue38413] Remove or change "Multithreading" section
In-Reply-To: <1570563042.6.0.0902531064636.issue38413@roundup.psfhosted.org>
Message-ID: <1570628241.63.0.254397345417.issue38413@roundup.psfhosted.org>


Change by David Kernan <davidsmurf at gmail.com>:


----------
pull_requests:  -16262

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38413>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:52:38 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 13:52:38 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1570629158.38.0.211077365295.issue37531@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 598bfa4d457d61431142ad99ecbb9bd10cf314e6 by Miss Islington (bot) in branch '3.7':
bpo-37531: regrtest ignores output on timeout (GH-16659)
https://github.com/python/cpython/commit/598bfa4d457d61431142ad99ecbb9bd10cf314e6


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Wed Oct  9 09:52:38 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 13:52:38 +0000
Subject: [issue38207] subprocess: On Windows,
 Popen.kill() + Popen.communicate() is blocking until all processes
 using the pipe close the pipe
In-Reply-To: <1568763048.2.0.765446302919.issue38207@roundup.psfhosted.org>
Message-ID: <1570629158.1.0.179471608183.issue38207@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 598bfa4d457d61431142ad99ecbb9bd10cf314e6 by Miss Islington (bot) in branch '3.7':
bpo-37531: regrtest ignores output on timeout (GH-16659)
https://github.com/python/cpython/commit/598bfa4d457d61431142ad99ecbb9bd10cf314e6


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38207>
_______________________________________

From report at bugs.python.org  Wed Oct  9 10:02:18 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 14:02:18 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1570629738.59.0.212864318331.issue37531@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 359a1975cbca488ccd5ea13bd7268d7e88664078 by Miss Islington (bot) in branch '3.8':
bpo-37531: regrtest ignores output on timeout (GH-16659)
https://github.com/python/cpython/commit/359a1975cbca488ccd5ea13bd7268d7e88664078


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Wed Oct  9 10:02:18 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 14:02:18 +0000
Subject: [issue38207] subprocess: On Windows,
 Popen.kill() + Popen.communicate() is blocking until all processes
 using the pipe close the pipe
In-Reply-To: <1568763048.2.0.765446302919.issue38207@roundup.psfhosted.org>
Message-ID: <1570629738.47.0.724845605163.issue38207@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 359a1975cbca488ccd5ea13bd7268d7e88664078 by Miss Islington (bot) in branch '3.8':
bpo-37531: regrtest ignores output on timeout (GH-16659)
https://github.com/python/cpython/commit/359a1975cbca488ccd5ea13bd7268d7e88664078


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38207>
_______________________________________

From report at bugs.python.org  Wed Oct  9 10:09:01 2019
From: report at bugs.python.org (Mariatta)
Date: Wed, 09 Oct 2019 14:09:01 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1570630141.49.0.171375844526.issue38351@roundup.psfhosted.org>


Mariatta <mariatta at python.org> added the comment:

No decision yet. We're waiting for Julien's input. Thanks.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Wed Oct  9 10:35:36 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 09 Oct 2019 14:35:36 +0000
Subject: [issue38408] urlparse gives no method to build a url with a port
In-Reply-To: <1570528263.82.0.631134670905.issue38408@roundup.psfhosted.org>
Message-ID: <1570631736.09.0.724380412175.issue38408@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

Does it work if you pass a string of the form "host:port" as the host field?

I'd rather not change this antiquated interface too much, and I don't like proliferating additional functions.

----------
nosy: +gvanrossum

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38408>
_______________________________________

From report at bugs.python.org  Wed Oct  9 10:44:33 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 09 Oct 2019 14:44:33 +0000
Subject: [issue38408] urlparse gives no method to build a url with a port
In-Reply-To: <1570528263.82.0.631134670905.issue38408@roundup.psfhosted.org>
Message-ID: <1570632273.14.0.431057112609.issue38408@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Yes, that does work:

>>> urllib.parse.urlunparse(("http", f"{host}:{port}", "/", "", "", ""))
'http://hostname:1234/'



The only problem is that your code now needs to look like

>>> port=None
>>> urllib.parse.urlunparse(("http", f"{host}{(':' + str(port)) if port else ''}", "/", "", "", ""))
'http://hostname/'

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38408>
_______________________________________

From report at bugs.python.org  Wed Oct  9 11:01:34 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 09 Oct 2019 15:01:34 +0000
Subject: [issue38408] urlparse gives no method to build a url with a port
In-Reply-To: <1570632273.14.0.431057112609.issue38408@roundup.psfhosted.org>
Message-ID: <CAP7+vJJpM_4ZLoVdtDLiOXCOjAVQ9tF7heVieZv02mjL_B_akg@mail.gmail.com>


Guido van Rossum <guido at python.org> added the comment:

Then I find insufficient reason to change the API. Users who need this
frequently can make their own wrapper.
-- 
--Guido (mobile)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38408>
_______________________________________

From report at bugs.python.org  Wed Oct  9 11:06:10 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 09 Oct 2019 15:06:10 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1570633570.66.0.264924839656.issue37531@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The initial issue has been fixed in branches 3.7, 3.8 and master. I close the issue. Thanks to everybody who help to make these changes possible and helped to debug regressions.

It's not perfect, regrtest has to workaround bpo-38207 bug, but at least regrtest should no longer runs for several hours or days.



> regrtest should kill a worker process if it runs longer than --timeout seconds.

The main regrtest process now kills a worker process running longer than timeout seconds. In practice, it's timeout x 1.5, to give time to the faulthandler watchdog to kill the process.

If regrtest hits bpo-38207 bug, regrtest takes 2 min 30 sec to exit in the worst case.


> But it means that the main process was stuck for longer than 60 seconds!? The main process is supposed to write an update "running: ..." every 30 seconds. This buildbot is very slow. Maybe 30 and 60 seconds limits are too low?

I changed this timeout from 1 minute to 5 minutes.


> Calling popen.kill() + popen.stdout.close() + popen.stderr.close() from a thread B does not always interrupt popen.communicate() in thread A.

I propose to continue the discussion in bpo-38207 "subprocess: On Windows, Popen.kill() + Popen.communicate() is blocking until all processes using the pipe close the pipe".

I implemented workarounds in regrtest so regrtest doesn't block *forever*: it only waits 30 seconds until a worker thread completes, and I added a timeout of 2 minutes on Python exit of the main regrtest process to prevent blocking in threading._shutdown(), because of the blocked threads.


> I don't understand why you get 2 typeperf.exe process: only the main process should spawn one. Worker processes don't need it and should not spawn it.

I didn't check on my Windows VM if I have the issue. If someone sees more than one typeperf.exe process, please open a separated issue.

Note: typeperf.exe is the correct spelling (typepref.exe is a typo ;-)).

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Wed Oct  9 11:06:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 09 Oct 2019 15:06:57 +0000
Subject: [issue38207] subprocess: On Windows,
 Popen.kill() + Popen.communicate() is blocking until all processes
 using the pipe close the pipe
In-Reply-To: <1568763048.2.0.765446302919.issue38207@roundup.psfhosted.org>
Message-ID: <1570633617.71.0.567427914777.issue38207@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

regrtest now workarounds this issue using timeouts on subprocess.Popen.wait() and threading.Thread.join() operations: see bpo-37531.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38207>
_______________________________________

From report at bugs.python.org  Wed Oct  9 11:15:39 2019
From: report at bugs.python.org (Ram Rachum)
Date: Wed, 09 Oct 2019 15:15:39 +0000
Subject: [issue38422] Clarify docstrings of pathlib suffix(es)
Message-ID: <1570634139.23.0.159522926495.issue38422@roundup.psfhosted.org>


New submission from Ram Rachum <ram at rachum.com>:

I'm writing a PR for this right now.

----------
components: Library (Lib)
messages: 354279
nosy: cool-RR
priority: normal
severity: normal
status: open
title: Clarify docstrings of pathlib suffix(es)
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38422>
_______________________________________

From report at bugs.python.org  Wed Oct  9 11:22:43 2019
From: report at bugs.python.org (Erlend Egeberg Aasland)
Date: Wed, 09 Oct 2019 15:22:43 +0000
Subject: [issue38380] Update SQLite to 3.30 in Windows and macOS installer
 builds
In-Reply-To: <1570313540.41.0.0224198940573.issue38380@roundup.psfhosted.org>
Message-ID: <1570634563.95.0.608023864791.issue38380@roundup.psfhosted.org>


Erlend Egeberg Aasland <erlend.aasland at innova.no> added the comment:

I've prepared a PR for https://github.com/python/cpython-source-deps at https://github.com/erlend-aasland/cpython-source-deps/tree/upgrade-sqlite. 

Patches for Windows and macOS installer builds on 3.9 prepared at https://github.com/erlend-aasland/cpython/tree/fix-issue-38380.

If it looks ok, I'll create PR's for CPython and cpython-source-deps. I guess this should be backported to 3.8, 3.7 and 2.7.

----------
nosy: +erlendaasland

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38380>
_______________________________________

From report at bugs.python.org  Wed Oct  9 11:24:08 2019
From: report at bugs.python.org (Ram Rachum)
Date: Wed, 09 Oct 2019 15:24:08 +0000
Subject: [issue38422] Clarify docstrings of pathlib suffix(es)
In-Reply-To: <1570634139.23.0.159522926495.issue38422@roundup.psfhosted.org>
Message-ID: <1570634648.4.0.515734435788.issue38422@roundup.psfhosted.org>


Change by Ram Rachum <ram at rachum.com>:


----------
keywords: +patch
pull_requests: +16264
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16679

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38422>
_______________________________________

From report at bugs.python.org  Wed Oct  9 11:24:50 2019
From: report at bugs.python.org (Erlend Egeberg Aasland)
Date: Wed, 09 Oct 2019 15:24:50 +0000
Subject: [issue38380] Update SQLite to 3.30 in Windows and macOS installer
 builds
In-Reply-To: <1570313540.41.0.0224198940573.issue38380@roundup.psfhosted.org>
Message-ID: <1570634690.8.0.731710514452.issue38380@roundup.psfhosted.org>


Erlend Egeberg Aasland <erlend.aasland at innova.no> added the comment:

bpo-38380: Update macOS installer to use SQLite 3.30.0
https://github.com/erlend-aasland/cpython/commit/aa7d7b1a3bed9a6a73f0611d0542a3442e85b0b6

----------
keywords: +patch
Added file: https://bugs.python.org/file48651/0001-bpo-38380-Update-macOS-installer-to-use-SQLite-3.30..patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38380>
_______________________________________

From report at bugs.python.org  Wed Oct  9 11:25:42 2019
From: report at bugs.python.org (Erlend Egeberg Aasland)
Date: Wed, 09 Oct 2019 15:25:42 +0000
Subject: [issue38380] Update SQLite to 3.30 in Windows and macOS installer
 builds
In-Reply-To: <1570313540.41.0.0224198940573.issue38380@roundup.psfhosted.org>
Message-ID: <1570634742.45.0.504173860498.issue38380@roundup.psfhosted.org>


Erlend Egeberg Aasland <erlend.aasland at innova.no> added the comment:

bpo-38380: Update Windows builds to use SQLite 3.30.0
https://github.com/erlend-aasland/cpython/commit/e25214e6fa7a64353d9c3e16b139c41f5d62eb31

----------
Added file: https://bugs.python.org/file48652/0002-bpo-38380-Update-Windows-builds-to-use-SQLite-3.30.0.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38380>
_______________________________________

From report at bugs.python.org  Wed Oct  9 11:30:59 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 09 Oct 2019 15:30:59 +0000
Subject: [issue38408] urlparse gives no method to build a url with a port
In-Reply-To: <1570528263.82.0.631134670905.issue38408@roundup.psfhosted.org>
Message-ID: <1570635059.68.0.509409934832.issue38408@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Okay, then I'll close this.

----------
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38408>
_______________________________________

From report at bugs.python.org  Wed Oct  9 11:56:36 2019
From: report at bugs.python.org (Erlend Egeberg Aasland)
Date: Wed, 09 Oct 2019 15:56:36 +0000
Subject: [issue38380] Update SQLite to 3.30 in Windows and macOS installer
 builds
In-Reply-To: <1570313540.41.0.0224198940573.issue38380@roundup.psfhosted.org>
Message-ID: <1570636596.65.0.409891670589.issue38380@roundup.psfhosted.org>


Erlend Egeberg Aasland <erlend.aasland at innova.no> added the comment:

FYI: Compiled cpython 3.9 with sqlite-3.30 on macOS 10.14.6. Make test completes without errors.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38380>
_______________________________________

From report at bugs.python.org  Wed Oct  9 12:16:17 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Wed, 09 Oct 2019 16:16:17 +0000
Subject: [issue38408] urlparse gives no method to build a url with a port
In-Reply-To: <1570528263.82.0.631134670905.issue38408@roundup.psfhosted.org>
Message-ID: <1570637777.38.0.50552232852.issue38408@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

@Amir maybe you can update the docs to add an example of how to do this (if there isn't already one there).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38408>
_______________________________________

From report at bugs.python.org  Wed Oct  9 12:51:42 2019
From: report at bugs.python.org (Benjamin Wood)
Date: Wed, 09 Oct 2019 16:51:42 +0000
Subject: [issue17254] add thai encoding aliases to encodings.aliases
In-Reply-To: <1361360924.27.0.663240022367.issue17254@psf.upfronthosting.co.za>
Message-ID: <1570639902.76.0.246476885111.issue17254@roundup.psfhosted.org>


Benjamin Wood <ben.bt.wood at gmail.com> added the comment:

I've created the codepage alias 874.

This is only pending is a merge into the mainline.

Thanks.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17254>
_______________________________________

From report at bugs.python.org  Wed Oct  9 13:14:39 2019
From: report at bugs.python.org (=?utf-8?b?SHJ2b2plIE5pa8WhacSH?=)
Date: Wed, 09 Oct 2019 17:14:39 +0000
Subject: [issue38423] Event loop implementation docs advertise set_event_loop
Message-ID: <1570641279.2.0.929881138502.issue38423@roundup.psfhosted.org>


New submission from Hrvoje Nik?i? <hniksic at gmail.com>:

The docs of SelectorEventLoop and ProactorEventLoop contain examples that call asyncio.set_event_loop:

      selector = selectors.SelectSelector()
      loop = asyncio.SelectorEventLoop(selector)
      asyncio.set_event_loop(loop)

But this won't have any effect on code that uses asyncio.run(), because asyncio.run() creates a fresh event loop. Since asyncio.run() is the recommended way to execute async code and is used consistently throughout the documentation, this might be confusing to someone who tries to e.g. use the proactor loop on Windows.

I propose the following:

* add a disclaimer that instantiating the event loop won't affect calls to asyncio.run(), and that loop.run_until_complete() must be used; and

* link to asyncio.set_event_loop_policy(), which does work with asyncio.run(), but doesn't allow fine-tuning the details, such as which selector to use for the SelectorEventLoop.

----------
assignee: docs at python
components: Documentation, asyncio
messages: 354288
nosy: asvetlov, docs at python, hniksic, yselivanov
priority: normal
severity: normal
status: open
title: Event loop implementation docs advertise set_event_loop
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38423>
_______________________________________

From report at bugs.python.org  Wed Oct  9 13:15:18 2019
From: report at bugs.python.org (=?utf-8?b?SHJ2b2plIE5pa8WhacSH?=)
Date: Wed, 09 Oct 2019 17:15:18 +0000
Subject: [issue38423] Event loop implementation docs advertise set_event_loop
 which doesn't work with asyncio.run
In-Reply-To: <1570641279.2.0.929881138502.issue38423@roundup.psfhosted.org>
Message-ID: <1570641318.29.0.932893304527.issue38423@roundup.psfhosted.org>


Change by Hrvoje Nik?i? <hniksic at gmail.com>:


----------
title: Event loop implementation docs advertise set_event_loop -> Event loop implementation docs advertise set_event_loop which doesn't work with asyncio.run

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38423>
_______________________________________

From report at bugs.python.org  Wed Oct  9 13:19:40 2019
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 09 Oct 2019 17:19:40 +0000
Subject: [issue38413] Remove or change "Multithreading" section
In-Reply-To: <1570563042.6.0.0902531064636.issue38413@roundup.psfhosted.org>
Message-ID: <1570641580.49.0.770568272099.issue38413@roundup.psfhosted.org>


Change by Brett Cannon <brett at python.org>:


----------
nosy: +ghaering

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38413>
_______________________________________

From report at bugs.python.org  Wed Oct  9 13:21:58 2019
From: report at bugs.python.org (Amir Mohamadi)
Date: Wed, 09 Oct 2019 17:21:58 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
In-Reply-To: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>
Message-ID: <1570641718.29.0.719997502135.issue38419@roundup.psfhosted.org>


Change by Amir Mohamadi <amiremohamadi at yahoo.com>:


----------
keywords: +patch
pull_requests: +16266
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16680

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Wed Oct  9 13:36:13 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 09 Oct 2019 17:36:13 +0000
Subject: [issue38423] Event loop implementation docs advertise set_event_loop
 which doesn't work with asyncio.run
In-Reply-To: <1570641279.2.0.929881138502.issue38423@roundup.psfhosted.org>
Message-ID: <1570642573.68.0.0669682076496.issue38423@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

Yes, docs updates sound good.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38423>
_______________________________________

From report at bugs.python.org  Wed Oct  9 13:37:41 2019
From: report at bugs.python.org (Tim Peters)
Date: Wed, 09 Oct 2019 17:37:41 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570642661.43.0.449542093855.issue38379@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:


New changeset ecbf35f9335b0420cb8adfda6f299d6747a16515 by Tim Peters in branch 'master':
bpo-38379:  don't claim objects are collected when they aren't (#16658)
https://github.com/python/cpython/commit/ecbf35f9335b0420cb8adfda6f299d6747a16515


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Wed Oct  9 14:08:59 2019
From: report at bugs.python.org (Tim Peters)
Date: Wed, 09 Oct 2019 18:08:59 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570644539.0.0.125549917569.issue38379@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

I checked the stat fix into master, but GH failed to backport to 3.7 or 3.8 and I'm clueless.  More info in the PR.  Does someone else here know how to get a backport done?

----------
stage: patch review -> backport needed
versions: +Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Wed Oct  9 14:33:48 2019
From: report at bugs.python.org (Daniel Kahn Gillmor)
Date: Wed, 09 Oct 2019 18:33:48 +0000
Subject: [issue17123] Add OCSP support to ssl module
In-Reply-To: <1359994472.8.0.804183286731.issue17123@psf.upfronthosting.co.za>
Message-ID: <1570646028.91.0.799431814838.issue17123@roundup.psfhosted.org>


Daniel Kahn Gillmor <dkg at fifthhorseman.net> added the comment:

It would be great to see at least minimal OCSP stapling support (in the form of callbacks on the client and server sides) availabl in the ssl module, similar to the way that pyopenssl has added such callbacks:

    https://github.com/pyca/pyopenssl/pull/580

If that was present in the ssl module, then it would let other implementations supply reasonable callback functionality for fetching and relaying stapled OCSP responses (on the server side) and validating in-band OCSP responses (on the client side).

----------
nosy: +dkg

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17123>
_______________________________________

From report at bugs.python.org  Wed Oct  9 14:55:59 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 09 Oct 2019 18:55:59 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570647359.67.0.0345389639499.issue38417@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

We should not provide such an "run arbitrary python code before execing the ultimate child" feature in the standard library.

It is complicated, and assumes you have an ability to execute a new interpreter with its own slow startup time as an intermediate in the child in the first place.  (embedded pythons do not have that ability)

Leave that to someone to implement on top of subprocess as a thing on PyPI.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Wed Oct  9 15:46:46 2019
From: report at bugs.python.org (Hansraj Das)
Date: Wed, 09 Oct 2019 19:46:46 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570650406.66.0.61151699859.issue38409@roundup.psfhosted.org>


Change by Hansraj Das <raj.das.136 at gmail.com>:


----------
pull_requests: +16267
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16681

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Wed Oct  9 15:59:07 2019
From: report at bugs.python.org (Dema Abu Adas)
Date: Wed, 09 Oct 2019 19:59:07 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
In-Reply-To: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>
Message-ID: <1570651147.96.0.706298570107.issue38419@roundup.psfhosted.org>


Dema Abu Adas <dabuadas at uoguelph.ca> added the comment:

Hey, Can I take on this issue? :-)

----------
nosy: +de-ma

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Wed Oct  9 16:20:03 2019
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 09 Oct 2019 20:20:03 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570652403.58.0.443573618995.issue38409@roundup.psfhosted.org>


Change by Zachary Ware <zachary.ware at gmail.com>:


----------
pull_requests: +16268
pull_request: https://github.com/python/cpython/pull/16682

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:07:10 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Wed, 09 Oct 2019 21:07:10 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570655230.5.0.144479219431.issue38379@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16269
stage: backport needed -> patch review
pull_request: https://github.com/python/cpython/pull/16683

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:09:03 2019
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 09 Oct 2019 21:09:03 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570655343.64.0.122283342338.issue38409@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:


New changeset 09895c27cd8ff60563a794016e8c099bc897cc74 by Zachary Ware in branch 'master':
bpo-38409: Fix grammar in str.strip() docstring (GH-16682)
https://github.com/python/cpython/commit/09895c27cd8ff60563a794016e8c099bc897cc74


----------
nosy: +zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:09:14 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 21:09:14 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570655354.08.0.200300859117.issue38409@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16270
pull_request: https://github.com/python/cpython/pull/16684

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:11:56 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Wed, 09 Oct 2019 21:11:56 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570655516.75.0.481999407547.issue38379@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16271
pull_request: https://github.com/python/cpython/pull/16685

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:12:29 2019
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 09 Oct 2019 21:12:29 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570655549.59.0.164315547793.issue38409@roundup.psfhosted.org>


Change by Zachary Ware <zachary.ware at gmail.com>:


----------
pull_requests: +16272
pull_request: https://github.com/python/cpython/pull/16686

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:14:53 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Wed, 09 Oct 2019 21:14:53 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570655693.91.0.51380245488.issue38379@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Tim, I have created backports for 3.8 and 3.7 (PR 16683, PR 16685). In my case cherry_picker ecbf35f9335b0420cb8adfda6f299d6747a16515 3.7 and cherry_picker ecbf35f9335b0420cb8adfda6f299d6747a16515 3.8 works after fixing merge conflicts. Maybe there is something going on in your git repo (maybe you didn't fetch from master first and that is why git log fails?).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:25:09 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 21:25:09 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570656309.38.0.246642150786.issue38379@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 0bd9fac7a866ec886ae8f93f9c24dcda6d436929 by Miss Islington (bot) (Pablo Galindo) in branch '3.8':
[3.8] bpo-38379:  don't claim objects are collected when they aren't  (GH-16658) (GH-16683)
https://github.com/python/cpython/commit/0bd9fac7a866ec886ae8f93f9c24dcda6d436929


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:33:54 2019
From: report at bugs.python.org (Fritz Reese)
Date: Wed, 09 Oct 2019 21:33:54 +0000
Subject: [issue24560] codecs.StreamReader doesn't work with nonblocking
 streams: TypeError: can't concat bytes to NoneType
In-Reply-To: <1435936324.39.0.622709208254.issue24560@psf.upfronthosting.co.za>
Message-ID: <1570656834.89.0.44105752454.issue24560@roundup.psfhosted.org>


Fritz Reese <fritzoreese at gmail.com> added the comment:

This is still an issue on Linux in both 3.4 and 3.7 even when using io.open() as suggested by @vstinner:

>>> import io, os, fcntl
>>> r, w = os.pipe()
>>> fcntl(r, fcntl.F_SETFL, os.O_NONBLOCK)
0
>>> stream = io.open(r, 'rt')
>>> stream
<_io.TextIOWrapper name=X mode='rt' encoding='UTF-8'>
>>> stream.buffer
<_io.BufferedReader name=X>
>>> print(repr(stream.buffer.read()))
None
>>> stream.read()
Traceback (most recent call last):
  ...
  File ".../python3.7/codecs.py"..., in decode
    data = self.buffer + input
TypeError: can't concat NoneType to bytes

The error is present in at least 3.4 up to 3.7 where the underlying buffer.read() returns None which is not handled by the TextIOStream.

----------
nosy: +Fritz Reese
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24560>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:42:57 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 09 Oct 2019 21:42:57 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570657377.67.0.563297773301.issue38379@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset a081e931505f190b5ccdff9a781e59b3f13fcc31 by Miss Islington (bot) (Pablo Galindo) in branch '3.7':
[3.7] bpo-38379:  don't claim objects are collected when they aren't (GH-16658) (GH-16685)
https://github.com/python/cpython/commit/a081e931505f190b5ccdff9a781e59b3f13fcc31


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:53:22 2019
From: report at bugs.python.org (Erlend Egeberg Aasland)
Date: Wed, 09 Oct 2019 21:53:22 +0000
Subject: [issue38380] Update SQLite to 3.30 in Windows and macOS installer
 builds
In-Reply-To: <1570313540.41.0.0224198940573.issue38380@roundup.psfhosted.org>
Message-ID: <1570658002.26.0.256828139897.issue38380@roundup.psfhosted.org>


Erlend Egeberg Aasland <erlend.aasland at innova.no> added the comment:

Update: Tested on macOS 10.14.6 with make test on 2.7.17rc1, 3.7.5rc1+, 3.8.0rc1+.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38380>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:55:42 2019
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 09 Oct 2019 21:55:42 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570658142.17.0.134738890045.issue38409@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:


New changeset 0baa6b3c7d9ef1d96f10939c40f8ff95aba9155b by Zachary Ware (Miss Islington (bot)) in branch '3.8':
bpo-38409: Fix grammar in str.strip() docstring (GH-16682) (GH-16684)
https://github.com/python/cpython/commit/0baa6b3c7d9ef1d96f10939c40f8ff95aba9155b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:56:10 2019
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 09 Oct 2019 21:56:10 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570658170.77.0.111726116988.issue38409@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:


New changeset a774ac6637e8f155a28b7733a0a93d4a680584d4 by Zachary Ware in branch '3.7':
[3.7] bpo-38409: Fix grammar in str.strip() docstring (GH-16682) (GH-16686)
https://github.com/python/cpython/commit/a774ac6637e8f155a28b7733a0a93d4a680584d4


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Wed Oct  9 17:57:24 2019
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 09 Oct 2019 21:57:24 +0000
Subject: [issue38409] Typo in doc string for str.strip
In-Reply-To: <1570543194.25.0.196797196101.issue38409@roundup.psfhosted.org>
Message-ID: <1570658244.9.0.8320393194.issue38409@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:

Thanks for the report, Bob!

----------
keywords:  -newcomer friendly
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38409>
_______________________________________

From report at bugs.python.org  Wed Oct  9 20:34:42 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 10 Oct 2019 00:34:42 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570667682.16.0.714560454382.issue38379@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16273
pull_request: https://github.com/python/cpython/pull/16687

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Wed Oct  9 21:10:51 2019
From: report at bugs.python.org (Ammar Askar)
Date: Thu, 10 Oct 2019 01:10:51 +0000
Subject: [issue17894] Edits to descriptor howto
In-Reply-To: <1367547112.04.0.920947702161.issue17894@psf.upfronthosting.co.za>
Message-ID: <1570669851.6.0.0213153774232.issue17894@roundup.psfhosted.org>


Ammar Askar <ammar at ammaraskar.com> added the comment:

Any updates on this? Some of the re-organization and simplifications here look pretty good overall and make the guide way more approachable.

Seeing as how this has been sitting a while and Github has an option allow maintainers to make edits to PRs. Raymond, would you be fine with Ned making a PR out of these changes to solicit your feedback and incorporate it the way you want?

----------
nosy: +ammar2

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17894>
_______________________________________

From report at bugs.python.org  Wed Oct  9 21:34:39 2019
From: report at bugs.python.org (Dima Tisnek)
Date: Thu, 10 Oct 2019 01:34:39 +0000
Subject: [issue38413] Remove or change "Multithreading" section
In-Reply-To: <1570563042.6.0.0902531064636.issue38413@roundup.psfhosted.org>
Message-ID: <1570671279.79.0.812096867454.issue38413@roundup.psfhosted.org>


Dima Tisnek <dimaqq at gmail.com> added the comment:

That would be nice; someone needs to figure out what exact sqlite version allows safe passing of connection between threads. Ideally other caveats would be covered (is passing open cursors to another thread allowed?, etc...)

----------
nosy: +Dima.Tisnek

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38413>
_______________________________________

From report at bugs.python.org  Wed Oct  9 21:38:42 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Thu, 10 Oct 2019 01:38:42 +0000
Subject: [issue17123] Add OCSP support to ssl module
In-Reply-To: <1359994472.8.0.804183286731.issue17123@psf.upfronthosting.co.za>
Message-ID: <1570671522.21.0.151508418003.issue17123@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:

Considering OSCP has fallen out of favor relative to CT in recent years, may be should simply reject this feature request.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17123>
_______________________________________

From report at bugs.python.org  Wed Oct  9 21:39:01 2019
From: report at bugs.python.org (Dima Tisnek)
Date: Thu, 10 Oct 2019 01:39:01 +0000
Subject: [issue38424] typing.Generator shorthand
Message-ID: <1570671541.73.0.307162838122.issue38424@roundup.psfhosted.org>


New submission from Dima Tisnek <dimaqq at gmail.com>:

Currently to annotate a generator, something like `Generator[str, None, None]` is required. Which is a bit confusing and verbose.

Can we allow shorthand, like `Generator[str]` for simple cases?

I'm not entirely certain what the semantics ought to be...
Maybe Generator[t1, t2=Any, t3=None] ?

----------
components: Library (Lib)
messages: 354307
nosy: Dima.Tisnek
priority: normal
severity: normal
status: open
title: typing.Generator shorthand
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38424>
_______________________________________

From report at bugs.python.org  Wed Oct  9 21:41:48 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Thu, 10 Oct 2019 01:41:48 +0000
Subject: [issue38424] typing.Generator shorthand
In-Reply-To: <1570671541.73.0.307162838122.issue38424@roundup.psfhosted.org>
Message-ID: <1570671708.55.0.414859810396.issue38424@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:

Is Iterator[Whatever] not sufficient for you?

----------
nosy: +benjamin.peterson

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38424>
_______________________________________

From report at bugs.python.org  Wed Oct  9 22:29:57 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 10 Oct 2019 02:29:57 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
In-Reply-To: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>
Message-ID: <1570674597.79.0.831657474465.issue38419@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> Hey, Can I take on this issue? :-)

Unfortunately, Amir already sent a patch for this.
Please take a look at another issue :)

Thank you

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Wed Oct  9 22:40:05 2019
From: report at bugs.python.org (Dima Tisnek)
Date: Thu, 10 Oct 2019 02:40:05 +0000
Subject: [issue38424] typing.Generator shorthand
In-Reply-To: <1570671541.73.0.307162838122.issue38424@roundup.psfhosted.org>
Message-ID: <1570675205.05.0.236033975548.issue38424@roundup.psfhosted.org>


Dima Tisnek <dimaqq at gmail.com> added the comment:

Actually yes it is sufficient.

I don't know why I didn't think of that!
Perhaps some note in the docs could help other lost children of Python :P

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38424>
_______________________________________

From report at bugs.python.org  Wed Oct  9 23:24:33 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 10 Oct 2019 03:24:33 +0000
Subject: [issue17894] Edits to descriptor howto
In-Reply-To: <1367547112.04.0.920947702161.issue17894@psf.upfronthosting.co.za>
Message-ID: <1570677873.24.0.193201552934.issue17894@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I've been working on some updates to the descriptor how-to and will likely post next month or so (there have been other priorities for 3.8 and I had had some limitations regarding posting my training material).  I'm going in a different direction than the patches proposed here and am going to mark this tracker issue as closed.  

FWIW, this entry is unique in that it is a work of individual authorship, originally posted on my own website.  When the analysis became a popular, I was asked to post it on python.org.  I will continue to maintain and improve it but am not open to a substantial stylistic rewrite changing it into someone else's style (people can use their own blog posts for that purpose).

----------
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17894>
_______________________________________

From report at bugs.python.org  Thu Oct 10 01:02:14 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 10 Oct 2019 05:02:14 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0MjVdIFJlbW92ZSB3YXJuaW5nOiDigJhyZXPigJkgbWF5IGJl?=
 =?utf-8?q?_used_uninitialized_in_this_function?=
Message-ID: <1570683734.97.0.750890713695.issue38425@roundup.psfhosted.org>


New submission from Dong-hee Na <donghee.na92 at gmail.com>:

Python/Python-ast.c: In function ?PyAST_obj2mod?:
Python/Python-ast.c:10253:12: warning: ?res? may be used uninitialized in this function [-Wmaybe-uninitialized]

CentOS Linux release 7.6.1810
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)

----------
assignee: corona10
messages: 354312
nosy: corona10
priority: normal
severity: normal
status: open
title: Remove warning: ?res? may be used uninitialized in this function
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38425>
_______________________________________

From report at bugs.python.org  Thu Oct 10 01:05:46 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 10 Oct 2019 05:05:46 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0MjVdIFJlbW92ZSB3YXJuaW5nOiDigJhyZXPigJkgbWF5IGJl?=
 =?utf-8?q?_used_uninitialized_in_this_function?=
In-Reply-To: <1570683734.97.0.750890713695.issue38425@roundup.psfhosted.org>
Message-ID: <1570683946.36.0.135014154402.issue38425@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
keywords: +patch
pull_requests: +16274
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16688

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38425>
_______________________________________

From report at bugs.python.org  Thu Oct 10 01:19:25 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 10 Oct 2019 05:19:25 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0MjVdIFJlbW92ZSB3YXJuaW5nOiDigJhyZXPigJkgbWF5IGJl?=
 =?utf-8?q?_used_uninitialized_in_this_function?=
In-Reply-To: <1570683734.97.0.750890713695.issue38425@roundup.psfhosted.org>
Message-ID: <1570684765.35.0.106023499865.issue38425@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
stage: patch review -> 
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38425>
_______________________________________

From report at bugs.python.org  Thu Oct 10 01:31:15 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 10 Oct 2019 05:31:15 +0000
Subject: [issue38426] declare visit_validate in Py_DEBUG macro
Message-ID: <1570685475.13.0.949767572532.issue38426@roundup.psfhosted.org>


New submission from Dong-hee Na <donghee.na92 at gmail.com>:

I've got the warining like this.

Modules/gcmodule.c:1925:1: warning: ?visit_validate? defined but not used [-Wunused-function]
 visit_validate(PyObject *op, void *parent_raw)

This looks like only used in pydebug.
I'd like to propose declaring this function only in #ifdef Py_DEBUG.

My environment is 
CentOS Linux release 7.6.1810
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)

----------
assignee: corona10
components: Interpreter Core
messages: 354313
nosy: corona10, serhiy.storchaka, vstinner
priority: normal
severity: normal
status: open
title: declare visit_validate in Py_DEBUG macro
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38426>
_______________________________________

From report at bugs.python.org  Thu Oct 10 02:00:23 2019
From: report at bugs.python.org (Shengjing Zhu)
Date: Thu, 10 Oct 2019 06:00:23 +0000
Subject: [issue38427] Issue URL on translated Python docs site is always
 pointed to English version
Message-ID: <1570687223.02.0.730833049002.issue38427@roundup.psfhosted.org>


New submission from Shengjing Zhu <zsj950618 at gmail.com>:

On footer of https://docs.python.org/fr/3.8, "Found a bug?" links to https://docs.python.org/3/bugs.html

It should be https://docs.python.org/fr/3.8/bugs.html as 3.7 version.

----------
assignee: docs at python
components: Documentation
messages: 354314
nosy: docs at python, zhsj
priority: normal
severity: normal
status: open
title: Issue URL on translated Python docs site is always pointed to English version
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38427>
_______________________________________

From report at bugs.python.org  Thu Oct 10 02:50:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 06:50:59 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570690259.2.0.472666679067.issue38392@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16275
pull_request: https://github.com/python/cpython/pull/16689

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Thu Oct 10 02:50:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 06:50:59 +0000
Subject: [issue38426] declare visit_validate in Py_DEBUG macro
In-Reply-To: <1570685475.13.0.949767572532.issue38426@roundup.psfhosted.org>
Message-ID: <1570690259.34.0.41555183993.issue38426@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16276
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16689

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38426>
_______________________________________

From report at bugs.python.org  Thu Oct 10 02:53:34 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 06:53:34 +0000
Subject: [issue38426] declare visit_validate in Py_DEBUG macro
In-Reply-To: <1570685475.13.0.949767572532.issue38426@roundup.psfhosted.org>
Message-ID: <1570690414.24.0.65949074444.issue38426@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I wrote PR 16689 to fix the warning. I added the function in bpo-38392.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38426>
_______________________________________

From report at bugs.python.org  Thu Oct 10 02:59:18 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 10 Oct 2019 06:59:18 +0000
Subject: [issue38427] Issue URL on translated Python docs site is always
 pointed to English version
In-Reply-To: <1570687223.02.0.730833049002.issue38427@roundup.psfhosted.org>
Message-ID: <1570690758.88.0.529413443068.issue38427@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

There are occasional reports of typo in translations that are opened in bugs.python.org and it would make sense to redirect to respective GitHub repos for the translations.

----------
nosy: +mdk, xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38427>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:18:07 2019
From: report at bugs.python.org (Shengjing Zhu)
Date: Thu, 10 Oct 2019 07:18:07 +0000
Subject: [issue38427] Issue URL on translated Python docs site is always
 pointed to English version
In-Reply-To: <1570687223.02.0.730833049002.issue38427@roundup.psfhosted.org>
Message-ID: <1570691887.29.0.375892839805.issue38427@roundup.psfhosted.org>


Shengjing Zhu <zsj950618 at gmail.com> added the comment:

On https://docs.python.org/zh-cn/3/bugs.html we emphasis that translation bugs should be reported at GitHub. So that's why I want the footer link same as previous (link to translated bugs.html).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38427>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:32:19 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 07:32:19 +0000
Subject: [issue38392] Ensure that objects entering the GC are valid
In-Reply-To: <1570445338.58.0.651902608854.issue38392@roundup.psfhosted.org>
Message-ID: <1570692739.62.0.0839708357576.issue38392@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset a5447735c334a041ee2ffdeb5c7e13d7d4502ea2 by Victor Stinner in branch 'master':
bpo-38392: Only declare visit_validate() if Py_DEBUG is defined (GH-16689)
https://github.com/python/cpython/commit/a5447735c334a041ee2ffdeb5c7e13d7d4502ea2


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38392>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:32:19 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 07:32:19 +0000
Subject: [issue38426] declare visit_validate in Py_DEBUG macro
In-Reply-To: <1570685475.13.0.949767572532.issue38426@roundup.psfhosted.org>
Message-ID: <1570692739.77.0.628848298608.issue38426@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset a5447735c334a041ee2ffdeb5c7e13d7d4502ea2 by Victor Stinner in branch 'master':
bpo-38392: Only declare visit_validate() if Py_DEBUG is defined (GH-16689)
https://github.com/python/cpython/commit/a5447735c334a041ee2ffdeb5c7e13d7d4502ea2


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38426>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:34:49 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 07:34:49 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570692889.39.0.739249199396.issue38109@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 7bb14316b8ceddb813f31040a299af94a57ab339 by Victor Stinner (Ronan Lamy) in branch 'master':
bpo-38109: Add missing constants to Lib/stat.py (GH-16665)
https://github.com/python/cpython/commit/7bb14316b8ceddb813f31040a299af94a57ab339


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:35:02 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 07:35:02 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570692902.39.0.40194337881.issue38109@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16277
pull_request: https://github.com/python/cpython/pull/16690

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:35:08 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 07:35:08 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570692908.01.0.594612663767.issue38109@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16278
pull_request: https://github.com/python/cpython/pull/16691

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:37:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 07:37:02 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570693022.96.0.6606466822.issue38109@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Ronan Lamy: Hum, do you really need this change to land in Python 3.7 and 3.8? If not, I will close PR 16690 and PR 16691 backports.

I don't think that it's worth it, since _stat should be always present in CPython.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:39:23 2019
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 10 Oct 2019 07:39:23 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570693163.4.0.188092843017.issue38417@roundup.psfhosted.org>


Change by Christian Heimes <lists at cheimes.de>:


----------
nosy: +christian.heimes

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:41:29 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 07:41:29 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0MjVdIFJlbW92ZSB3YXJuaW5nOiDigJhyZXPigJkgbWF5IGJl?=
 =?utf-8?q?_used_uninitialized_in_this_function?=
In-Reply-To: <1570683734.97.0.750890713695.issue38425@roundup.psfhosted.org>
Message-ID: <1570693289.7.0.891344403965.issue38425@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset a05fcd3c7adf6e3a0944da8cf80a3346882e9b3b by Victor Stinner (Dong-hee Na) in branch 'master':
bpo-38425: Fix ?res? may be used uninitialized warning (GH-16688)
https://github.com/python/cpython/commit/a05fcd3c7adf6e3a0944da8cf80a3346882e9b3b


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38425>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:41:37 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 07:41:37 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0MjVdIFJlbW92ZSB3YXJuaW5nOiDigJhyZXPigJkgbWF5IGJl?=
 =?utf-8?q?_used_uninitialized_in_this_function?=
In-Reply-To: <1570683734.97.0.750890713695.issue38425@roundup.psfhosted.org>
Message-ID: <1570693297.57.0.28139157754.issue38425@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16279
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16693

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38425>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:41:43 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 07:41:43 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0MjVdIFJlbW92ZSB3YXJuaW5nOiDigJhyZXPigJkgbWF5IGJl?=
 =?utf-8?q?_used_uninitialized_in_this_function?=
In-Reply-To: <1570683734.97.0.750890713695.issue38425@roundup.psfhosted.org>
Message-ID: <1570693303.25.0.562620984106.issue38425@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16280
pull_request: https://github.com/python/cpython/pull/16694

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38425>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:47:04 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 07:47:04 +0000
Subject: [issue36339] test_ttk_guionly: test_traversal() fails randomly on
 AMD64 Windows8.1 Refleaks 2.7
In-Reply-To: <1552899428.95.0.891639199681.issue36339@roundup.psfhosted.org>
Message-ID: <1570693624.31.0.868910525964.issue36339@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Recent failure:

The Buildbot has detected a failed build on builder AMD64 Windows8.1 Refleaks 2.7 while building Python.
Full details are available at:
    https://buildbot.python.org/all/#builders/33/builds/726

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36339>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:47:29 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 07:47:29 +0000
Subject: [issue38426] declare visit_validate in Py_DEBUG macro
In-Reply-To: <1570685475.13.0.949767572532.issue38426@roundup.psfhosted.org>
Message-ID: <1570693649.71.0.457507190774.issue38426@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Thanks for the report. It's now fixed.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38426>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:49:23 2019
From: report at bugs.python.org (Ronald Oussoren)
Date: Thu, 10 Oct 2019 07:49:23 +0000
Subject: [issue37677] Seg Fault on OSX when multiprocessing
In-Reply-To: <1564042021.53.0.0155934240157.issue37677@roundup.psfhosted.org>
Message-ID: <1570693763.38.0.0313372965067.issue37677@roundup.psfhosted.org>


Ronald Oussoren <ronaldoussoren at mac.com> added the comment:

Looking at the stack trace this is a similar issue as the "no_proxy" one, but in some sense worse because it happens when just calling a regular unix API (not an Apple framework API).

The first few lines of the stack trace are for code in the "Network" framework which is new in macOS 10.14 and is based on lib dispatch and  hence uses threads. That results in the same problem as the "no_proxy" one: code that causes problems when called after os.fork().

That's a bug in macOS.

In Python 3.8 the multiprocessing module switched to "spawn" mode instead of "fork" mode because of this.  You can do this manually for earlier versions (https://docs.python.org/3.7/library/multiprocessing.html#contexts-and-start-methods)

P.S. A reproducer would still be nice as that would make it easier to raise and issue with Apple about this.

----------
components: +macOS
nosy: +ned.deily, ronaldoussoren
versions: +Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37677>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:52:58 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 07:52:58 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570693978.69.0.558573114205.issue38417@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Another use of the deprecated unsafe preexec_fn was to call os.umask in the child prior to exec.

What do you mean by "deprecated"? The parameter doesn't seem to be deprecated in the documentation:
https://docs.python.org/dev/library/subprocess.html#subprocess.Popen

And when I use it, it doesn't emit any warning:
---
import os, subprocess, sys
def func(): print(f"func called in {os.getpid()}")
argv = [sys.executable, "-c", "pass"]
print(f"parent: {os.getpid()}")
subprocess.run(argv, preexec_fn=func)
---

Output:
---
$ ./python -Werror x.py 
parent: 22264
func called in 22265
---

If you want to deprecate it, it should be documented as deprecated and emit a DeprecatedWarning, no?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:53:19 2019
From: report at bugs.python.org (Giampaolo Rodola')
Date: Thu, 10 Oct 2019 07:53:19 +0000
Subject: [issue38416] test_largefile.TestSocketSendfile.test_it() failed with
 15 min timeout on AMD64 FreeBSD 10-STABLE Non-Debug 3.x
In-Reply-To: <1570569266.33.0.0795173642593.issue38416@roundup.psfhosted.org>
Message-ID: <1570693999.85.0.886379528558.issue38416@roundup.psfhosted.org>


Giampaolo Rodola' <g.rodola at gmail.com> added the comment:

> Another approach is to change the timeout of 15 min for this super slow buildbot. For example, set it to 20 min or 30 min.

I think this makes more sense (set timeout to 25 min).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38416>
_______________________________________

From report at bugs.python.org  Thu Oct 10 03:57:08 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 07:57:08 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570694228.58.0.589566081811.issue38417@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

pylint emits a warning on subprocess.Popen(preexec_fn=func):

   W1509: Using preexec_fn keyword which may be unsafe in
   the presence of threads (subprocess-popen-preexec-fn)

But not when using subprocess.run(preexec_fn=func). Maybe a check is missing in pylint.

Note: pyflakes doesn't complain about preexec_fn.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:00:30 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 08:00:30 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0MjVdIFJlbW92ZSB3YXJuaW5nOiDigJhyZXPigJkgbWF5IGJl?=
 =?utf-8?q?_used_uninitialized_in_this_function?=
In-Reply-To: <1570683734.97.0.750890713695.issue38425@roundup.psfhosted.org>
Message-ID: <1570694430.04.0.457154666764.issue38425@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 6b6935e563562c427d5bb1b2864d6a2fed0e74fa by Miss Islington (bot) in branch '3.8':
bpo-38425: Fix ?res? may be used uninitialized warning (GH-16688)
https://github.com/python/cpython/commit/6b6935e563562c427d5bb1b2864d6a2fed0e74fa


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38425>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:00:44 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 08:00:44 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0MjVdIFJlbW92ZSB3YXJuaW5nOiDigJhyZXPigJkgbWF5IGJl?=
 =?utf-8?q?_used_uninitialized_in_this_function?=
In-Reply-To: <1570683734.97.0.750890713695.issue38425@roundup.psfhosted.org>
Message-ID: <1570694444.65.0.746266963229.issue38425@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset d27a9b1695a1b46c81b3a83a7a35034791265d89 by Miss Islington (bot) in branch '3.7':
bpo-38425: Fix ?res? may be used uninitialized warning (GH-16688)
https://github.com/python/cpython/commit/d27a9b1695a1b46c81b3a83a7a35034791265d89


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38425>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:00:58 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:00:58 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570694458.06.0.497019293333.issue38417@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> We should not provide such an "run arbitrary python code before execing the ultimate child" feature in the standard library.

Do you want to modify _posixsubprocess to call umask() between fork() and exec()? As it has been done for uid, gid and groups: call setreuid(), setregid() and setgroups()?

If so, it means that posix_spawn() couldn't be used when the new umask parameter would be used, right?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:01:19 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 10 Oct 2019 08:01:19 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0MjVdIFJlbW92ZSB3YXJuaW5nOiDigJhyZXPigJkgbWF5IGJl?=
 =?utf-8?q?_used_uninitialized_in_this_function?=
In-Reply-To: <1570683734.97.0.750890713695.issue38425@roundup.psfhosted.org>
Message-ID: <1570694479.53.0.510031105939.issue38425@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38425>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:10:52 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:10:52 +0000
Subject: [issue38416] test_largefile.TestSocketSendfile.test_it() failed with
 15 min timeout on AMD64 FreeBSD 10-STABLE Non-Debug 3.x
In-Reply-To: <1570569266.33.0.0795173642593.issue38416@roundup.psfhosted.org>
Message-ID: <1570695052.55.0.768754620697.issue38416@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I changed AMD64 FreeBSD 10-STABLE timeout from 15 to 30 minutes.

https://github.com/python/buildmaster-config/commit/c3fe0b1b65d94c115bbbb0521dda4daba02775dc

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38416>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:13:40 2019
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 10 Oct 2019 08:13:40 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570695220.11.0.188099946813.issue38417@roundup.psfhosted.org>


Christian Heimes <lists at cheimes.de> added the comment:

preexec_fn does not work in subinterpreters, which (amongst others) affects mod_wsgi and similar WSGI implementations. Therefore portable software must not use preexec_fn at all.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:14:42 2019
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 10 Oct 2019 08:14:42 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570695282.25.0.278204097357.issue38417@roundup.psfhosted.org>


Christian Heimes <lists at cheimes.de> added the comment:

Changed in version 3.8: The preexec_fn parameter is no longer supported in subinterpreters. The use of the parameter in a subinterpreter raises RuntimeError. The new restriction may affect applications that are deployed in mod_wsgi, uWSGI, and other embedded environments.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:18:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:18:30 +0000
Subject: [issue14307] Make subclassing SocketServer simpler for non-blocking
 frameworks
In-Reply-To: <1331767378.71.0.470789063251.issue14307@psf.upfronthosting.co.za>
Message-ID: <1570695510.36.0.69983319105.issue14307@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Antoine Pitrou: "...  I'm against this change ..."

Martin Panter: "... But this seems unreasonable to me. ..."

I close the issue. You can use asyncio for non-blocking networking code. Or have a look at Twisted, Tornado, eventlet, etc.

If you really want to hack socketserver, I suggest you to copy the whole socketserver.py file. But asynchronous programming is a hard problem which requires more than modiying a single function. Slowly, you will built something similar the the project that I cited.

----------
nosy: +vstinner
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue14307>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:26:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:26:26 +0000
Subject: [issue35762] subprocess.Popen with universal_newlines and nonblocking
 streams fails with "can't concat NoneType to bytes"
In-Reply-To: <1547738568.37.0.865745194211.issue35762@roundup.psfhosted.org>
Message-ID: <1570695986.74.0.7604967461.issue35762@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I close this issue as a duplicate of bpo-13322 which is older and has a longer history.

----------
nosy: +vstinner
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> buffered read() and write() does not raise BlockingIOError

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35762>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:26:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:26:59 +0000
Subject: [issue13322] buffered read() and write() does not raise
 BlockingIOError
In-Reply-To: <1320246535.71.0.465783773129.issue13322@psf.upfronthosting.co.za>
Message-ID: <1570696019.38.0.603622413712.issue13322@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I closed bpo-35762 as a duplicate of this issue: subprocess.Popen with universal_newlines and nonblocking streams fails with "can't concat NoneType to bytes".

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13322>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:27:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:27:39 +0000
Subject: [issue26292] Raw I/O writelines() broken for non-blocking I/O
In-Reply-To: <1454661860.28.0.473572264835.issue26292@psf.upfronthosting.co.za>
Message-ID: <1570696059.18.0.0724102779005.issue26292@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I close this issue as duplicate of bpo-13322 which is older and has a longer history.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> buffered read() and write() does not raise BlockingIOError

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26292>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:27:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:27:57 +0000
Subject: [issue13322] buffered read() and write() does not raise
 BlockingIOError
In-Reply-To: <1320246535.71.0.465783773129.issue13322@psf.upfronthosting.co.za>
Message-ID: <1570696077.83.0.0891581690408.issue13322@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I closed bpo-26292 as a duplicate of this issue: Raw I/O writelines() broken for non-blocking I/O.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13322>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:29:35 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:29:35 +0000
Subject: [issue24560] codecs.StreamReader doesn't work with nonblocking
 streams: TypeError: can't concat bytes to NoneType
In-Reply-To: <1435936324.39.0.622709208254.issue24560@psf.upfronthosting.co.za>
Message-ID: <1570696175.45.0.0601537592957.issue24560@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I close this issue as a duplicate of bpo-13322.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> buffered read() and write() does not raise BlockingIOError

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24560>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:29:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:29:53 +0000
Subject: [issue13322] buffered read() and write() does not raise
 BlockingIOError
In-Reply-To: <1320246535.71.0.465783773129.issue13322@psf.upfronthosting.co.za>
Message-ID: <1570696193.72.0.966624003992.issue13322@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I closed bpo-24560 as a duplicate of this issue: codecs.StreamReader doesn't work with nonblocking streams: TypeError: can't concat bytes to NoneType.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13322>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:30:27 2019
From: report at bugs.python.org (Jakub Stasiak)
Date: Thu, 10 Oct 2019 08:30:27 +0000
Subject: [issue13322] buffered read() and write() does not raise
 BlockingIOError
In-Reply-To: <1320246535.71.0.465783773129.issue13322@psf.upfronthosting.co.za>
Message-ID: <1570696227.54.0.359837656958.issue13322@roundup.psfhosted.org>


Change by Jakub Stasiak <jakub+python.org at stasiak.at>:


----------
nosy: +jstasiak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13322>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:31:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:31:13 +0000
Subject: [issue13322] buffered read() and write() does not raise
 BlockingIOError
In-Reply-To: <1320246535.71.0.465783773129.issue13322@psf.upfronthosting.co.za>
Message-ID: <1570696273.75.0.609441035951.issue13322@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

See also bpo-32561: Add API to io objects for non-blocking reads/writes.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13322>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:32:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:32:02 +0000
Subject: [issue13322] The io module doesn't support non-blocking files
In-Reply-To: <1320246535.71.0.465783773129.issue13322@psf.upfronthosting.co.za>
Message-ID: <1570696322.57.0.987642919285.issue13322@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
components:  -Documentation, IO
title: buffered read() and write() does not raise BlockingIOError -> The io module doesn't support non-blocking files
versions: +Python 3.9 -Python 2.7, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13322>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:34:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:34:56 +0000
Subject: [issue32561] Add API to io objects for non-blocking reads/writes
In-Reply-To: <1516068442.29.0.467229070634.issue32561@psf.upfronthosting.co.za>
Message-ID: <1570696496.93.0.216127922464.issue32561@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Background: Doing I/O to files on disk has a hugely bimodal latency. If the I/O happens to be in or going to cache (either user-space cache, like in io.BufferedIOBase, or the OS's page cache), then the operation returns instantly (~1 ?s) without blocking. OTOH if the I/O isn't cached (for reads) or cacheable (for writes), then the operation may block for 10 ms or more.

On Linux 4.14 and newer, Python 3.8 now provides os.preadv(os.RWF_NOWAIT):

"Do not wait for data which is not immediately available. If this flag is specified, the system call will return instantly if it would have to read data from the backing storage or wait for a lock. If some data was successfully read, it will return the number of bytes read. If no bytes were read, it will return -1 and set errno to errno.EAGAIN."

At least on recent Linux, it became possible to write a different code path for uncached data.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32561>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:35:51 2019
From: report at bugs.python.org (Rebecca Fair)
Date: Thu, 10 Oct 2019 08:35:51 +0000
Subject: [issue38428] Can't gracefully ctrl+C multiprocessing pool on Python3
 & Windows
Message-ID: <1570696551.92.0.213022823921.issue38428@roundup.psfhosted.org>


New submission from Rebecca Fair <rebecca.fair at stfc.ac.uk>:

I want to be able to Ctrl+C to exit a multiprocessing Pool.map gracefully, and have made a solution based on this Stack Overflow answer: https://stackoverflow.com/questions/11312525/catch-ctrlc-sigint-and-exit-multiprocesses-gracefully-in-python

However, this solution works on Linux, and on Windows 10 with Python 2.7, but not on Windows 10 with Python 3.7. The Ctrl+C is just ignored and I have to kill the processes manually. I've attached the minimum code required to reproduce the problem.

Is this a bug, expected, or is there a workaround? I believe it might be caused by the behaviour of threading.Condition.wait() being changed in commit 7c3e577 but I don't know enough about signalling to say any more than that

----------
components: Windows
files: bug.py
messages: 354344
nosy: paul.moore, rebeccafair, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Can't gracefully ctrl+C multiprocessing pool on Python3 & Windows
versions: Python 3.7
Added file: https://bugs.python.org/file48653/bug.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38428>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:37:08 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:37:08 +0000
Subject: [issue13322] The io module doesn't support non-blocking files
In-Reply-To: <1320246535.71.0.465783773129.issue13322@psf.upfronthosting.co.za>
Message-ID: <1570696628.03.0.0305576828155.issue13322@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

TextIOWrapper, and maybe also BufferedRead, may raise an exception if the underlying file descriptor is configured in non-blocking mode. It may require an additional syscall() to query the FD properties, which may slowdown the creation of file objects in Python :-/

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13322>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:39:50 2019
From: report at bugs.python.org (Rebecca Fair)
Date: Thu, 10 Oct 2019 08:39:50 +0000
Subject: [issue38428] Can't gracefully ctrl+C multiprocessing pool on Python3
 & Windows
In-Reply-To: <1570696551.92.0.213022823921.issue38428@roundup.psfhosted.org>
Message-ID: <1570696790.98.0.901451616211.issue38428@roundup.psfhosted.org>


Rebecca Fair <rebecca.fair at stfc.ac.uk> added the comment:

Sorry, I didn't realise it wouldn't link to a commit automatically, the commit is here: https://github.com/python/cpython/commit/7c3e5773954009d65520eb063621cf7724da88e3

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38428>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:42:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:42:30 +0000
Subject: [issue32561] Add API to io objects for non-blocking reads/writes
In-Reply-To: <1516068442.29.0.467229070634.issue32561@psf.upfronthosting.co.za>
Message-ID: <1570696950.82.0.952626335803.issue32561@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The Linux kernel 5.1 also got a new "io_uring" for asynchronous I/O:

"Ringing in a new asynchronous I/O API"
https://lwn.net/Articles/776703/

Linux 5.2: "The io_uring mechanism has a new operation, IORING_OP_SYNC_FILE_RANGE, which performs the equivalent of a sync_file_range() system call. It is also now possible to register an eventfd with an io_uring and get notifications when operations complete."

Linux 5.3: "The io_uring mechanism has gained support for asynchronous sendmsg() and recvmsg() operations."

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32561>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:47:11 2019
From: report at bugs.python.org (Haruka Ma)
Date: Thu, 10 Oct 2019 08:47:11 +0000
Subject: [issue38429] Failed to compile with --enable-framework on macOS on
 master
Message-ID: <1570697231.32.0.587121640762.issue38429@roundup.psfhosted.org>


New submission from Haruka Ma <mrx at hcc.im>:

Since commit https://github.com/python/cpython/commit/c02b41b1fb115c87693530ea6a480b2e15460424 , some syntax errors are preventing cpython from compiling with --enable-framework on. 

Specifically, the errors are in Modules/getpath.c on line 1134 and 1165.

I've made some inline comments on github as well.

----------
components: macOS
messages: 354348
nosy: Haruka Ma, ned.deily, ronaldoussoren
priority: normal
severity: normal
status: open
title: Failed to compile with --enable-framework on macOS on master
type: compile error
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38429>
_______________________________________

From report at bugs.python.org  Thu Oct 10 04:51:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 08:51:47 +0000
Subject: [issue32561] Add API to io objects for non-blocking reads/writes
In-Reply-To: <1516068442.29.0.467229070634.issue32561@psf.upfronthosting.co.za>
Message-ID: <1570697507.84.0.658685541605.issue32561@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I suggest to close the issue and move the discussion to a place to discuss asynchronous ideas.


I'm sorry, but I don't understand what it is proposed here. I understand that Nathaniel wants to add something like a new "asynchronous" mode in the io module which would make FileIO, BufferedReader and TextIOWrapper behave differently.

IMHO it's a bad idea. The io module is designed for blocking I/O syscalls. Not only the implementation, but also the API.

Non-blocking I/O requires a platform specific implementation for best performances, but that requires something like an event loop, and so unusual programming style like asyncio "await ...".

I dislike the idea of having a single module for synchronous (blocking) and asynchronous (non-blocking) operations. IMHO asynchronous programming is so complex that it requires to develop a whole new module.

Maybe new module could reuse io code. Like implement an asynchronous using io.TextIOWrapper, but its underlying buffer would be feeded and controlled by asynchronous code.

The Python bug tracker is usually used for bugs or to implement a concrete proposal. Here I understand that it's more an idea at the design stage. I don't think that it's the best place to discuss it. I suggest to open a discussion on python-ideas list or a list about asynchronous programming (I looked for "async-sig", but it seems like the list is gone?).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32561>
_______________________________________

From report at bugs.python.org  Thu Oct 10 05:19:52 2019
From: report at bugs.python.org (Giampaolo Rodola')
Date: Thu, 10 Oct 2019 09:19:52 +0000
Subject: [issue38416] test_largefile.TestSocketSendfile.test_it() failed with
 15 min timeout on AMD64 FreeBSD 10-STABLE Non-Debug 3.x
In-Reply-To: <1570569266.33.0.0795173642593.issue38416@roundup.psfhosted.org>
Message-ID: <1570699192.85.0.805493478415.issue38416@roundup.psfhosted.org>


Giampaolo Rodola' <g.rodola at gmail.com> added the comment:

Thanks.

----------
resolution: fixed -> 
stage: resolved -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38416>
_______________________________________

From report at bugs.python.org  Thu Oct 10 05:21:05 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 09:21:05 +0000
Subject: [issue38416] test_largefile.TestSocketSendfile.test_it() failed with
 15 min timeout on AMD64 FreeBSD 10-STABLE Non-Debug 3.x
In-Reply-To: <1570569266.33.0.0795173642593.issue38416@roundup.psfhosted.org>
Message-ID: <1570699265.65.0.654849900025.issue38416@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38416>
_______________________________________

From report at bugs.python.org  Thu Oct 10 05:31:05 2019
From: report at bugs.python.org (Ned Deily)
Date: Thu, 10 Oct 2019 09:31:05 +0000
Subject: [issue38429] Failed to compile with --enable-framework on macOS on
 master
In-Reply-To: <1570697231.32.0.587121640762.issue38429@roundup.psfhosted.org>
Message-ID: <1570699865.75.0.334403774696.issue38429@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38429>
_______________________________________

From report at bugs.python.org  Thu Oct 10 05:41:34 2019
From: report at bugs.python.org (Evgeny Nizhibitsky)
Date: Thu, 10 Oct 2019 09:41:34 +0000
Subject: [issue38430] Memory leak in ThreadPoolExecutor + run_in_executor
Message-ID: <1570700494.14.0.073826419802.issue38430@roundup.psfhosted.org>


New submission from Evgeny Nizhibitsky <nizhibitsky at gmail.com>:

I have run into a memory leak caused by using run_in_executor + ThreadPoolExecutor while running some stability tests with custom web services.

It was 1 MB leaked for 1k requests made for my case and I've extracted the root cause and converted it into minimal script with both mentioned parts + just NOP function to "run".

The script can easily eat up to 1 GB of memory in less then 1 minute now. It uses external psutil library to report the memory allocated but it can be easily commented out and the leak will stay anyway.

One can found that script attached + Dockerfile/Makefile for reproducibility. I've also reproduced it in my own conda-based 3.7 environment as well as the master branch of cpython.

----------
components: asyncio
files: python-leak.zip
messages: 354351
nosy: Evgeny Nizhibitsky, asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: Memory leak in ThreadPoolExecutor + run_in_executor
type: resource usage
versions: Python 3.6, Python 3.7, Python 3.9
Added file: https://bugs.python.org/file48654/python-leak.zip

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38430>
_______________________________________

From report at bugs.python.org  Thu Oct 10 05:52:38 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 09:52:38 +0000
Subject: [issue38430] Memory leak in ThreadPoolExecutor + run_in_executor
In-Reply-To: <1570700494.14.0.073826419802.issue38430@roundup.psfhosted.org>
Message-ID: <1570701158.11.0.627231041645.issue38430@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Well, that's a common issue when using asyncio: you forgot await.

async def main(_loop):
    while True:
        with futures.ThreadPoolExecutor() as pool:
            _loop.run_in_executor(pool, nop)
        sys.stdout.write(f'\r{get_mem():0.3f}MB')

It should be: "await _loop.run_in_executor(pool, nop)" ;-)

Sadly, PYTHONASYNCIODEBUG=1 env var doesn't complain on this bug.

See: https://docs.python.org/dev/library/asyncio-dev.html#debug-mode

----------
nosy: +vstinner
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38430>
_______________________________________

From report at bugs.python.org  Thu Oct 10 05:54:09 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Thu, 10 Oct 2019 09:54:09 +0000
Subject: [issue38430] Memory leak in ThreadPoolExecutor + run_in_executor
In-Reply-To: <1570700494.14.0.073826419802.issue38430@roundup.psfhosted.org>
Message-ID: <1570701249.18.0.705081241042.issue38430@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

You MUST await a future returned from `loop.run_in_executor()` to avoid the leak.

Yuri, what should we do with the issue? I see the second similar report in the last half of the year.
Sure, we can add weakrefs somewhere in futures._chain_future() but I pretty sure that the proper fix is just enforcing `await` here, e.g.

1. rename existing run_in_executor() into a private _run_in_executor() function.

2. write async trampoline:
async def run_in_executor(self, executor, func, *args):
    return await self._run_in_executor(executor, func, *args)

----------
nosy:  -vstinner
resolution: not a bug -> 
stage: resolved -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38430>
_______________________________________

From report at bugs.python.org  Thu Oct 10 05:54:51 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Thu, 10 Oct 2019 09:54:51 +0000
Subject: [issue38430] Memory leak in ThreadPoolExecutor + run_in_executor
In-Reply-To: <1570700494.14.0.073826419802.issue38430@roundup.psfhosted.org>
Message-ID: <1570701291.32.0.526656344521.issue38430@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

Victor answered the first :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38430>
_______________________________________

From report at bugs.python.org  Thu Oct 10 05:55:34 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 09:55:34 +0000
Subject: [issue38430] Memory leak in ThreadPoolExecutor + run_in_executor
In-Reply-To: <1570700494.14.0.073826419802.issue38430@roundup.psfhosted.org>
Message-ID: <1570701334.61.0.0467263739299.issue38430@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Yuri, what should we do with the issue?

A Task emits a warning when it's not awaited. Can a Task be used instead of a Future in run_in_executor()?

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38430>
_______________________________________

From report at bugs.python.org  Thu Oct 10 06:00:52 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Thu, 10 Oct 2019 10:00:52 +0000
Subject: [issue38430] Memory leak in ThreadPoolExecutor + run_in_executor
In-Reply-To: <1570700494.14.0.073826419802.issue38430@roundup.psfhosted.org>
Message-ID: <1570701652.38.0.598253925459.issue38430@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

> Can a Task be used instead of a Future in run_in_executor()?

I don't think that the task is required here. The problem is that run_in_executor is a function that returns asyncio future; that is in turn a wrapper around concurrent future object.

If we convert run_in_executor() into async function we'll get a warning about unawaited coroutine even without asyncio debug mode.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38430>
_______________________________________

From report at bugs.python.org  Thu Oct 10 06:02:05 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 10:02:05 +0000
Subject: [issue38430] Memory leak in ThreadPoolExecutor + run_in_executor
In-Reply-To: <1570700494.14.0.073826419802.issue38430@roundup.psfhosted.org>
Message-ID: <1570701725.36.0.847856028622.issue38430@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> If we convert run_in_executor() into async function we'll get a warning about unawaited coroutine even without asyncio debug mode.

That sounds like a good solution :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38430>
_______________________________________

From report at bugs.python.org  Thu Oct 10 06:02:49 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Thu, 10 Oct 2019 10:02:49 +0000
Subject: [issue38430] Memory leak in ThreadPoolExecutor + run_in_executor
In-Reply-To: <1570700494.14.0.073826419802.issue38430@roundup.psfhosted.org>
Message-ID: <1570701769.25.0.00433262406968.issue38430@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

The change is slightly not backward compatible but
1. It's pretty visible. In the worst-case instead of the memory leak people see a RuntimeWarning
2. We did it already for a part of API, e.g. loop.sock_read() and family

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38430>
_______________________________________

From report at bugs.python.org  Thu Oct 10 06:10:48 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 10:10:48 +0000
Subject: [issue38429] Failed to compile with --enable-framework on macOS on
 master
In-Reply-To: <1570697231.32.0.587121640762.issue38429@roundup.psfhosted.org>
Message-ID: <1570702248.92.0.089603851473.issue38429@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16282
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16695

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38429>
_______________________________________

From report at bugs.python.org  Thu Oct 10 06:10:48 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 10:10:48 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570702248.83.0.524216205925.issue38353@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16281
pull_request: https://github.com/python/cpython/pull/16695

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct 10 06:11:35 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 10:11:35 +0000
Subject: [issue38429] Failed to compile with --enable-framework on macOS on
 master
In-Reply-To: <1570697231.32.0.587121640762.issue38429@roundup.psfhosted.org>
Message-ID: <1570702295.42.0.0164506535942.issue38429@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Oh, I expected that we had macOS buildbots building Python with --enable-framework. Thanks for the reporting the issue.

I wrote PR 16695 which should fix the issue, but I cannot test my fix right now.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38429>
_______________________________________

From report at bugs.python.org  Thu Oct 10 06:38:17 2019
From: report at bugs.python.org (Evgeny Nizhibitsky)
Date: Thu, 10 Oct 2019 10:38:17 +0000
Subject: [issue38430] Memory leak in ThreadPoolExecutor + run_in_executor
In-Reply-To: <1570700494.14.0.073826419802.issue38430@roundup.psfhosted.org>
Message-ID: <1570703897.35.0.779664640715.issue38430@roundup.psfhosted.org>


Evgeny Nizhibitsky <nizhibitsky at gmail.com> added the comment:

Oh, I see that in the initial code with leakage (it was heavy ThreadPoolExecutor + xgboost thing) there was an await but I must have lost it somewhere while reducing it to the minimal example and finished in the wrong direction.

Glad too see that it raised a discussion to prevent others from getting into this silent trap.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38430>
_______________________________________

From report at bugs.python.org  Thu Oct 10 06:54:58 2019
From: report at bugs.python.org (Haruka Ma)
Date: Thu, 10 Oct 2019 10:54:58 +0000
Subject: [issue38429] Failed to compile with --enable-framework on macOS on
 master
In-Reply-To: <1570697231.32.0.587121640762.issue38429@roundup.psfhosted.org>
Message-ID: <1570704898.71.0.339555461112.issue38429@roundup.psfhosted.org>


Haruka Ma <mrx at hcc.im> added the comment:

I'm now getting double free on the same function:

https://pastebin.com/zHWCtTuV (with debug on)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38429>
_______________________________________

From report at bugs.python.org  Thu Oct 10 06:56:30 2019
From: report at bugs.python.org (Nathaniel Smith)
Date: Thu, 10 Oct 2019 10:56:30 +0000
Subject: [issue32561] Add API to io objects for non-blocking reads/writes
In-Reply-To: <1516068442.29.0.467229070634.issue32561@psf.upfronthosting.co.za>
Message-ID: <1570704990.48.0.0102633260734.issue32561@roundup.psfhosted.org>


Nathaniel Smith <njs at pobox.com> added the comment:

The proposal is to be able to run io module operations in two modes: the regular one, and one where performing actual I/O is forbidden ? so if they go down the stack and can fulfill the operation from some in-memory buffer, great, they do that, and if not, they raise an error.

It turns out that this is actually the right primitive to enable async disk access. That's the only target use case, and there's no IO loop involved. If you wanted to keep async disk access separate from the io module, then what we'd have to do is to create a fork of all the code in the io module, and add this feature to it. Which doesn't seem like a good design :-).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32561>
_______________________________________

From report at bugs.python.org  Thu Oct 10 07:11:41 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Thu, 10 Oct 2019 11:11:41 +0000
Subject: [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1570705901.4.0.735562124778.issue32996@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:


New changeset d47f0dd2e85ce032aebfedbde18cdb2e728fa79f by Ivan Levkivskyi (M. Eric Irrgang) in branch 'master':
bpo-32996: Documentation fix-up. (GH-16646)
https://github.com/python/cpython/commit/d47f0dd2e85ce032aebfedbde18cdb2e728fa79f


----------
nosy: +levkivskyi

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Thu Oct 10 07:11:46 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 11:11:46 +0000
Subject: [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1570705906.66.0.351071178059.issue32996@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16283
pull_request: https://github.com/python/cpython/pull/16696

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Thu Oct 10 07:12:19 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 11:12:19 +0000
Subject: [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1570705939.61.0.31480137351.issue32996@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16284
pull_request: https://github.com/python/cpython/pull/16697

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Thu Oct 10 07:17:08 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 11:17:08 +0000
Subject: [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1570706228.16.0.583275081055.issue32996@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset ca012360b103f2ab1acfa506aed032b0ed9b105c by Miss Islington (bot) in branch '3.7':
bpo-32996: Documentation fix-up. (GH-16646)
https://github.com/python/cpython/commit/ca012360b103f2ab1acfa506aed032b0ed9b105c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Thu Oct 10 07:19:06 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 11:19:06 +0000
Subject: [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1570706346.9.0.747852945711.issue32996@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset baf8a9b03a56ce1ee2284763b267ff56ab4507fe by Miss Islington (bot) in branch '3.8':
bpo-32996: Documentation fix-up. (GH-16646)
https://github.com/python/cpython/commit/baf8a9b03a56ce1ee2284763b267ff56ab4507fe


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Thu Oct 10 07:41:49 2019
From: report at bugs.python.org (Ned Batchelder)
Date: Thu, 10 Oct 2019 11:41:49 +0000
Subject: [issue17894] Edits to descriptor howto
In-Reply-To: <1367547112.04.0.920947702161.issue17894@psf.upfronthosting.co.za>
Message-ID: <1570707709.62.0.828657352808.issue17894@roundup.psfhosted.org>


Ned Batchelder <ned at nedbatchelder.com> added the comment:

I think it's a bad precedent to have pages in the official docs that belong to a single author.  If you want to maintain that kind of control, it should go on your blog.  Part of the agreement for having material added to the official docs should be the understanding that they are fair game for community contributions.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17894>
_______________________________________

From report at bugs.python.org  Thu Oct 10 07:59:52 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 11:59:52 +0000
Subject: [issue38429] Failed to compile with --enable-framework on macOS on
 master
In-Reply-To: <1570697231.32.0.587121640762.issue38429@roundup.psfhosted.org>
Message-ID: <1570708792.48.0.285949257744.issue38429@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Hum, getpath.c seems to use deprecated APIs:

./Modules/getpath.c:1098:20: warning: 'NSModuleForSymbol' is deprecated: first deprecated in macOS 10.5 - dladdr() [-Wdeprecated-declarations]
    pythonModule = NSModuleForSymbol(NSLookupAndBindSymbol("_Py_Initialize"));
                   ^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/mach-o/dyld.h:193:21: note: 'NSModuleForSymbol' has been explicitly marked deprecated here
extern NSModule     NSModuleForSymbol(NSSymbol symbol) __API_UNAVAILABLE(ios, tvos, watchos)  __OSX_DEPRECATED(10.1, 10.5, "dladdr()");
                    ^
./Modules/getpath.c:1098:38: warning: 'NSLookupAndBindSymbol' is deprecated: first deprecated in macOS 10.4 - dlsym() [-Wdeprecated-declarations]
    pythonModule = NSModuleForSymbol(NSLookupAndBindSymbol("_Py_Initialize"));
                                     ^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/mach-o/dyld.h:183:17: note: 'NSLookupAndBindSymbol' has been explicitly marked deprecated here
extern NSSymbol NSLookupAndBindSymbol(const char* symbolName)                                                    __API_UNAVAILABLE(ios, tvos, watchos)  __OSX_DEPRECATED(10...
                ^
./Modules/getpath.c:1101:27: warning: 'NSLibraryNameForModule' is deprecated: first deprecated in macOS 10.5 [-Wdeprecated-declarations]
    const char* modPath = NSLibraryNameForModule(pythonModule);
                          ^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include/mach-o/dyld.h:163:21: note: 'NSLibraryNameForModule' has been explicitly marked deprecated here
extern const char*  NSLibraryNameForModule(NSModule m) __API_UNAVAILABLE(ios, tvos, watchos)  __OSX_DEPRECATED(10.1, 10.5, "");
                    ^
3 warnings generated.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38429>
_______________________________________

From report at bugs.python.org  Thu Oct 10 08:06:26 2019
From: report at bugs.python.org (=?utf-8?q?Kristj=C3=A1n_Valur_J=C3=B3nsson?=)
Date: Thu, 10 Oct 2019 12:06:26 +0000
Subject: [issue14307] Make subclassing SocketServer simpler for non-blocking
 frameworks
In-Reply-To: <1331767378.71.0.470789063251.issue14307@psf.upfronthosting.co.za>
Message-ID: <1570709186.31.0.676925733301.issue14307@roundup.psfhosted.org>


Kristj?n Valur J?nsson <sweskman at gmail.com> added the comment:

Nice necro :)
Socketserver is already subclassable and overridable for so many things.  Hard to understand the reluctancy to _allow_ for a different way to handle accept timeouts.  But this is also why I stopped contributing to core, because it turned out to be more about lobbying than anything else.  Anyway this is already implemented in PythonClassic, so no need for me to push it upstream :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue14307>
_______________________________________

From report at bugs.python.org  Thu Oct 10 09:42:36 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 13:42:36 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570714956.07.0.638906888976.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset b6e0fc74265db96fdd0e0b8151c768c583ad80f0 by Victor Stinner in branch 'master':
bpo-38353: Fix typos in calculate_argv0_path_framework() (GH-16695)
https://github.com/python/cpython/commit/b6e0fc74265db96fdd0e0b8151c768c583ad80f0


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct 10 09:42:36 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 13:42:36 +0000
Subject: [issue38429] Failed to compile with --enable-framework on macOS on
 master
In-Reply-To: <1570697231.32.0.587121640762.issue38429@roundup.psfhosted.org>
Message-ID: <1570714956.15.0.791322014207.issue38429@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset b6e0fc74265db96fdd0e0b8151c768c583ad80f0 by Victor Stinner in branch 'master':
bpo-38353: Fix typos in calculate_argv0_path_framework() (GH-16695)
https://github.com/python/cpython/commit/b6e0fc74265db96fdd0e0b8151c768c583ad80f0


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38429>
_______________________________________

From report at bugs.python.org  Thu Oct 10 09:43:11 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 13:43:11 +0000
Subject: [issue38429] Failed to compile with --enable-framework on macOS on
 master
In-Reply-To: <1570697231.32.0.587121640762.issue38429@roundup.psfhosted.org>
Message-ID: <1570714991.02.0.605798082084.issue38429@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Thanks for the bug report Haruka Ma, it should now be fixed.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38429>
_______________________________________

From report at bugs.python.org  Thu Oct 10 09:47:27 2019
From: report at bugs.python.org (Ronan Lamy)
Date: Thu, 10 Oct 2019 13:47:27 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570715247.07.0.933768048108.issue38109@roundup.psfhosted.org>


Ronan Lamy <ronan.lamy at gmail.com> added the comment:

Well, my interest in this is to reduce the divergence between PyPy and CPython, and, potentially, to help other implementations. So I actually care more about 3.7 than about 3.9, which I probably won't look at before 2021.

That said, I don't *need* anything: the fix is already in PyPy and we'll carry it forward regardless of what CPython does.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Thu Oct 10 09:49:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 13:49:55 +0000
Subject: [issue14307] Make subclassing SocketServer simpler for non-blocking
 frameworks
In-Reply-To: <1331767378.71.0.470789063251.issue14307@psf.upfronthosting.co.za>
Message-ID: <1570715395.21.0.90719005641.issue14307@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Hard to understand the reluctancy to _allow_ for a different way to handle accept timeouts.  But this is also why I stopped contributing to core, because it turned out to be more about lobbying than anything else.

To get a change merged into Python, you need to find someone who wants to be responsible for it: not only merge the change, but also maintain the code later. I touched socketserver recently for my work on making the Python CI more reliable. It was not easy to get a review. I ended to merge the changes with no review (if I recall properly).

I dislike socketserver design: it tries to be too generic. Like supporting TCP and UDP, support threading and forking models, etc.

To be honest, I didn't look at your issue. I only close it for bug triage, since there was no activity since 2016 and 2 core devs were against the change.

And you want to revisit the change, please reopen the issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue14307>
_______________________________________

From report at bugs.python.org  Thu Oct 10 09:50:37 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 13:50:37 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570715437.02.0.0453614153848.issue38109@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 8ab11c433a81b6c7ef84a66e36fbe199915e2ff6 by Victor Stinner (Miss Islington (bot)) in branch '3.8':
bpo-38109: Add missing constants to Lib/stat.py (GH-16665) (GH-16690)
https://github.com/python/cpython/commit/8ab11c433a81b6c7ef84a66e36fbe199915e2ff6


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Thu Oct 10 09:50:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 13:50:42 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570715442.01.0.230371972347.issue38109@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset f5ed41c1ae9a575e965d55c6a5e86fb59181eee8 by Victor Stinner (Miss Islington (bot)) in branch '3.7':
bpo-38109: Add missing constants to Lib/stat.py (GH-16665) (GH-16691)
https://github.com/python/cpython/commit/f5ed41c1ae9a575e965d55c6a5e86fb59181eee8


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Thu Oct 10 09:52:05 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 13:52:05 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570715525.74.0.00107539595109.issue38109@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I understand that backporting the change up to 3.7 makes your life easier, so I merged it. The change is safe and should not affect the regular use case (when the C extension _stat is used).

Thanks Ronan for this nice enhancement. It's good to see the stat module respect the PEP 399 ;-)

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Thu Oct 10 09:59:51 2019
From: report at bugs.python.org (Ronald Oussoren)
Date: Thu, 10 Oct 2019 13:59:51 +0000
Subject: [issue38429] Failed to compile with --enable-framework on macOS on
 master
In-Reply-To: <1570697231.32.0.587121640762.issue38429@roundup.psfhosted.org>
Message-ID: <1570715991.26.0.938454954917.issue38429@roundup.psfhosted.org>


Ronald Oussoren <ronaldoussoren at mac.com> added the comment:

W.r.t. the deprecated APIs in getpath.c: Issue15498

That issue contains an ancient patch to switch to non-deprecated APIs, but we haven't had time yet to fully test these. The issue also mentions that Apple's install of Python already switched away from the deprecated APIs, but had some issues at the time.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38429>
_______________________________________

From report at bugs.python.org  Thu Oct 10 10:02:14 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 14:02:14 +0000
Subject: [issue15498] Eliminate the use of deprecated OS X APIs in getpath.c
In-Reply-To: <1343633664.98.0.256476653975.issue15498@psf.upfronthosting.co.za>
Message-ID: <1570716134.29.0.00372303149194.issue15498@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The deprecation warnings are not fixed yet. They were quickly mentioned at:
https://bugs.python.org/issue38429#msg354367

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue15498>
_______________________________________

From report at bugs.python.org  Thu Oct 10 10:07:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 14:07:02 +0000
Subject: [issue38353] Cleanup the path configuration implementation code
 (getpath.c)
In-Reply-To: <1570050763.22.0.787922067096.issue38353@roundup.psfhosted.org>
Message-ID: <1570716422.3.0.137811254357.issue38353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I created this issue to attempt to modify _PyPathConfig to use PyWideStringList for module_search_paths, to support ":" character in a path. It would fix bpo-31210.

See also bpo-12989.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38353>
_______________________________________

From report at bugs.python.org  Thu Oct 10 10:08:22 2019
From: report at bugs.python.org (Ronan Lamy)
Date: Thu, 10 Oct 2019 14:08:22 +0000
Subject: [issue38109] Missing constants in Lib/stat.py
In-Reply-To: <1568208959.37.0.605416078815.issue38109@roundup.psfhosted.org>
Message-ID: <1570716502.71.0.0180284005663.issue38109@roundup.psfhosted.org>


Ronan Lamy <ronan.lamy at gmail.com> added the comment:

Thanks Victor!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38109>
_______________________________________

From report at bugs.python.org  Thu Oct 10 10:11:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 14:11:53 +0000
Subject: [issue38367] test_regrtest hanged on AMD64 Windows10 3.x
In-Reply-To: <1570147821.98.0.530432590053.issue38367@roundup.psfhosted.org>
Message-ID: <1570716713.04.0.0484335998381.issue38367@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I hope that this bug has been fixed by my latest fix for bpo-37531.

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38367>
_______________________________________

From report at bugs.python.org  Thu Oct 10 10:12:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 14:12:47 +0000
Subject: [issue38339] [3.5] The doc job of Travis CI fails on Python 3.5:
 needs at least Sphinx v1.8
In-Reply-To: <1569936050.09.0.437024380138.issue38339@roundup.psfhosted.org>
Message-ID: <1570716767.04.0.017558281597.issue38339@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Larry merged my fix:

commit edd9bc9cc99c919bdc87e5955ec8ad93c295fbe2
Author: Victor Stinner <vstinner at redhat.com>
Date:   Tue Oct 8 19:12:21 2019 +0200

    [3.7] Doc: Bump sphinx. (GH-10676) (GH-10803) (#16522)
    
    (cherry picked from commit 2db96ae7444880d66d4ef65abab8a5e6ff328711)
    
    Co-authored-by: Julien Palard <julien at palard.fr>
    (cherry picked from commit 23a98abd4256f931ed89b65ec6babd4f06dbff97)


The doc of job Travis CI is back to green ;-)

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38339>
_______________________________________

From report at bugs.python.org  Thu Oct 10 10:35:33 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 14:35:33 +0000
Subject: [issue38282] socketmodule.c: _FORTIFY_SOURCE=2 warning in AF_ALG case
 of getsockaddrarg()
In-Reply-To: <1569460305.42.0.728817437513.issue38282@roundup.psfhosted.org>
Message-ID: <1570718133.53.0.655159673132.issue38282@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16285
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16698

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38282>
_______________________________________

From report at bugs.python.org  Thu Oct 10 10:40:24 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 10 Oct 2019 14:40:24 +0000
Subject: [issue37972] unittest.mock.call does not chain __getitem__ to another
 _Call object
In-Reply-To: <1567024381.55.0.529292089661.issue37972@roundup.psfhosted.org>
Message-ID: <1570718424.32.0.74419691462.issue37972@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Closing as fixed since PRs were merged. Thanks Ben.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37972>
_______________________________________

From report at bugs.python.org  Thu Oct 10 10:44:01 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 10 Oct 2019 14:44:01 +0000
Subject: [issue38230] A Path Traversal vulnerability in test/ssl_servers.py
In-Reply-To: <1568983665.6.0.164381465993.issue38230@roundup.psfhosted.org>
Message-ID: <1570718641.54.0.162037934108.issue38230@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

I would propose closing since it's meant for tests and not for end users. I am also not sure if one of the tests depend on this behavior. Adding Victor as friendly ping since it's tagged as security.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38230>
_______________________________________

From report at bugs.python.org  Thu Oct 10 10:46:24 2019
From: report at bugs.python.org (Sylvain Marie)
Date: Thu, 10 Oct 2019 14:46:24 +0000
Subject: [issue36553] inspect.is_decorator_call(frame)
In-Reply-To: <1554711715.55.0.758701327001.issue36553@roundup.psfhosted.org>
Message-ID: <1570718784.89.0.760123357386.issue36553@roundup.psfhosted.org>


Sylvain Marie <sylvain.marie at schneider-electric.com> added the comment:

Quick update on this feature: for the following example to work:

from inspect import is_decorator_call

def set_hello_tag(tag='world'):
    if is_decorator_call():
        # called without parenthesis!
        # the decorated object is `tag`
        return set_hello_tag()(tag)   # note that `is_decorator_call` should not return True for this call
    else:
        def decorate(f):
            setattr(f, 'hello', tag)  # set a hello tag on the decorated f
            return f
        return decorate


Then `is_decorator_call` should be callable without arguments (default to current frame) and should return `True` only if the current frame is the one directly following decorator application. In nested frames (such as the one obtained after first recursive call to `set_hello_tag` above, `is_decorator_call` should return `False`.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36553>
_______________________________________

From report at bugs.python.org  Thu Oct 10 10:55:38 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 14:55:38 +0000
Subject: [issue38230] A Path Traversal vulnerability in test/ssl_servers.py
In-Reply-To: <1568983665.6.0.164381465993.issue38230@roundup.psfhosted.org>
Message-ID: <1570719338.01.0.370641047292.issue38230@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Lib/test/ssl_servers.py is an internal test helper and not designed to be used by any end-user. Don't use it ;-)

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38230>
_______________________________________

From report at bugs.python.org  Thu Oct 10 11:23:12 2019
From: report at bugs.python.org (Benoit Hudson)
Date: Thu, 10 Oct 2019 15:23:12 +0000
Subject: [issue37931] crash reimporting posix after Py_Finalize on mac
In-Reply-To: <1566574787.75.0.458129578699.issue37931@roundup.psfhosted.org>
Message-ID: <1570720992.75.0.88984409332.issue37931@roundup.psfhosted.org>


Benoit Hudson <benoit.hudson at imaginary-spaces.com> added the comment:

Ping! The patch has been ready for review for over a month.

If the patch can be backported to 2.7.x before that gets end-of-lifed it would be ideal.

----------
versions: +Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37931>
_______________________________________

From report at bugs.python.org  Thu Oct 10 11:31:02 2019
From: report at bugs.python.org (Samuel Colvin)
Date: Thu, 10 Oct 2019 15:31:02 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
Message-ID: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>


New submission from Samuel Colvin <samcolvin at gmail.com>:

The following code works fine with python 3.7 but breaks with 3.8:

```
import dataclasses
from typing import Optional

@dataclasses.dataclass
class TestingDataclass:
    base_path: dataclasses.InitVar[Optional[str]] = None
```

Exception traceback:

```
Traceback (most recent call last):
  File "test.py", line 6, in <module>
    class TestingDataclass:
  File "/usr/local/lib/python3.8/dataclasses.py", line 995, in dataclass
    return wrap(cls)
  File "/usr/local/lib/python3.8/dataclasses.py", line 987, in wrap
    return _process_class(cls, init, repr, eq, order, unsafe_hash, frozen)
  File "/usr/local/lib/python3.8/dataclasses.py", line 967, in _process_class
    str(inspect.signature(cls)).replace(' -> None', ''))
  File "/usr/local/lib/python3.8/inspect.py", line 3050, in __str__
    formatted = str(param)
  File "/usr/local/lib/python3.8/inspect.py", line 2568, in __str__
    formatannotation(self._annotation))
  File "/usr/local/lib/python3.8/inspect.py", line 1202, in formatannotation
    return repr(annotation)
  File "/usr/local/lib/python3.8/dataclasses.py", line 213, in __repr__
    return f'dataclasses.InitVar[{self.type.__name__}]'
  File "/usr/local/lib/python3.8/typing.py", line 757, in __getattr__
    raise AttributeError(attr)
AttributeError: __name__
```

The code runs fine with `str` instead of `Optional[str]`.

Tested locally with `Python 3.8.0rc1 (tags/v3.8.0rc1:34214de6ab, Oct 10 2019, 16:15:14)`. The same error can be seen (in a more involved context) on travis [here](https://travis-ci.org/samuelcolvin/pydantic/jobs/596131963)

----------
components: Library (Lib)
messages: 354388
nosy: samuelcolvin
priority: normal
severity: normal
status: open
title: dataclasses.InitVar breaks with typing.Optional
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Thu Oct 10 11:46:54 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 10 Oct 2019 15:46:54 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570722414.73.0.316668875895.issue38431@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Thu Oct 10 11:47:32 2019
From: report at bugs.python.org (Samuel Colvin)
Date: Thu, 10 Oct 2019 15:47:32 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570722452.01.0.638313368542.issue38431@roundup.psfhosted.org>


Samuel Colvin <samcolvin at gmail.com> added the comment:

This is a bug with the `__repr__` method on `InitVar`.

I'm working on a PR now.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Thu Oct 10 11:51:50 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 10 Oct 2019 15:51:50 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570722710.92.0.390127145817.issue38431@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

git blame points to https://github.com/python/cpython/commit/01ee12ba35a333e8a6a25c4153c4a21838e9585c . I am tagging this as a 3.8 regression since the commit was not backported and 3.7 works fine. Feel free to remove it if it's a mistake.

----------
keywords: +3.8regression
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Thu Oct 10 12:00:41 2019
From: report at bugs.python.org (Samuel Colvin)
Date: Thu, 10 Oct 2019 16:00:41 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570723241.85.0.40844368587.issue38431@roundup.psfhosted.org>


Change by Samuel Colvin <samcolvin at gmail.com>:


----------
keywords: +patch
pull_requests: +16286
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16700

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Thu Oct 10 12:01:41 2019
From: report at bugs.python.org (Behzad Seyfi)
Date: Thu, 10 Oct 2019 16:01:41 +0000
Subject: [issue38432] ZeroDivisionError when inf is expected
Message-ID: <1570723301.17.0.789552752187.issue38432@roundup.psfhosted.org>


New submission from Behzad Seyfi <seyfibeh at gmail.com>:

>>> 1/1e-323
inf

>>> 1/1e-324
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ZeroDivisionError: float division by zero

in a 1/x fraction, up to x = 1e-324 it is inf but when x = 1e-325 or little it throws ZeroDivisionError. It is not acceptable and accountable behaviour for inf definition.

----------
components: Interpreter Core
messages: 354391
nosy: Behzad Seyfi
priority: normal
severity: normal
status: open
title: ZeroDivisionError when inf is expected
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38432>
_______________________________________

From report at bugs.python.org  Thu Oct 10 12:06:56 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 10 Oct 2019 16:06:56 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570723616.04.0.788465301186.issue38431@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16287
pull_request: https://github.com/python/cpython/pull/16701

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Thu Oct 10 12:08:49 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 10 Oct 2019 16:08:49 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570723729.33.0.299834044495.issue38431@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Oh, Samuel already made a PR. Then I withdraw PR 16701.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Thu Oct 10 12:09:46 2019
From: report at bugs.python.org (Samuel Colvin)
Date: Thu, 10 Oct 2019 16:09:46 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570723786.52.0.344719270564.issue38431@roundup.psfhosted.org>


Change by Samuel Colvin <samcolvin at gmail.com>:


----------
pull_requests: +16288
pull_request: https://github.com/python/cpython/pull/16702

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Thu Oct 10 12:10:15 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 10 Oct 2019 16:10:15 +0000
Subject: [issue38428] Can't gracefully ctrl+C multiprocessing pool on Python3
 & Windows
In-Reply-To: <1570696551.92.0.213022823921.issue38428@roundup.psfhosted.org>
Message-ID: <1570723815.75.0.654181858229.issue38428@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

I think you're right about that change touching the right code, but I'm pretty sure it wasn't working before either. (Python 2.7 had totally different code, IIRC.)

But the good news is that we should be able to use code similar to what's in Modules/timemodule.c#L1878 (the pysleep() function) to also wait on the event we use to emulate signals on Windows. But perhaps there's a reason Antoine (nosied) didn't do that originally?

----------
nosy: +davin, pitrou
stage:  -> test needed
type:  -> behavior
versions: +Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38428>
_______________________________________

From report at bugs.python.org  Thu Oct 10 12:17:42 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 10 Oct 2019 16:17:42 +0000
Subject: [issue38433] 2.7.17rc1 tcl/tk version regression on Windows
Message-ID: <1570724262.85.0.67744981479.issue38433@roundup.psfhosted.org>


New submission from Terry J. Reedy <tjreedy at udel.edu>:

In my current 2.7.16+ Windows 10-64 repository build, and on at least one 8.1-64 buildbot, the tcl/tk version is 8.5.19
>>> tk.Tk().tk.call('info', 'patchlevel')
'8.5.19'

In my installed 2.7.17rc1, it is the older 8.5.15.  It would seem to me that we should install the same latest 8.5 bugfix release that we test with.  (Or test with what we release ;-)  I presume the discrepancy is unintended due to an incomplete final 2.7 tcl/tk update.

----------
components: Build, Tkinter
messages: 354394
nosy: benjamin.peterson, serhiy.storchaka, terry.reedy, zach.ware
priority: release blocker
severity: normal
status: open
title: 2.7.17rc1 tcl/tk version regression on Windows
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38433>
_______________________________________

From report at bugs.python.org  Thu Oct 10 12:19:04 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 16:19:04 +0000
Subject: [issue38432] ZeroDivisionError when inf is expected
In-Reply-To: <1570723301.17.0.789552752187.issue38432@roundup.psfhosted.org>
Message-ID: <1570724344.03.0.528673906499.issue38432@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

That's not a bug: 64-bit float of IEEE 754 rounds 1e-324 to 0.0.

vstinner at apu$ python3
Python 3.7.4 (default, Jul  9 2019, 16:32:37) 
[GCC 9.1.1 20190503 (Red Hat 9.1.1-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> 1e-324
0.0
>>> import sys
>>> sys.float_info
sys.float_info(max=1.7976931348623157e+308, max_exp=1024, max_10_exp=308, min=2.2250738585072014e-308, min_exp=-1021, min_10_exp=-307, dig=15, mant_dig=53, epsilon=2.220446049250313e-16, radix=2, rounds=1)
>>> sys.float_info.min
2.2250738585072014e-308
>>> sys.float_info.min.hex()
'0x1.0000000000000p-1022'

>>> 1/0.0
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ZeroDivisionError: float division by zero
>>> 1/1e-324
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ZeroDivisionError: float division by zero

----------
nosy: +vstinner
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38432>
_______________________________________

From report at bugs.python.org  Thu Oct 10 12:25:03 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 10 Oct 2019 16:25:03 +0000
Subject: [issue38434] sys.addaudithook event is not documented
Message-ID: <1570724703.62.0.219483741722.issue38434@roundup.psfhosted.org>


New submission from Steve Dower <steve.dower at python.org>:

The sys.addaudithook raises an audit event 'sys.addaudithook'.

The docs for the function refer to the event, as it has slightly different semantics than most, but it is not named explicitly and does not appear in the table of events.

----------
assignee: docs at python
components: Documentation
messages: 354396
nosy: docs at python, steve.dower
priority: normal
severity: normal
stage: needs patch
status: open
title: sys.addaudithook event is not documented
type: enhancement
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38434>
_______________________________________

From report at bugs.python.org  Thu Oct 10 13:11:00 2019
From: report at bugs.python.org (Chih-Hsuan Yen)
Date: Thu, 10 Oct 2019 17:11:00 +0000
Subject: [issue38014] Python 3.7 does not compile
In-Reply-To: <1567477987.66.0.578307493025.issue38014@roundup.psfhosted.org>
Message-ID: <1570727460.77.0.824220825634.issue38014@roundup.psfhosted.org>


Change by Chih-Hsuan Yen <yan12125 at gmail.com>:


----------
nosy: +yan12125

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38014>
_______________________________________

From report at bugs.python.org  Thu Oct 10 14:15:32 2019
From: report at bugs.python.org (Ned Batchelder)
Date: Thu, 10 Oct 2019 18:15:32 +0000
Subject: [issue17894] Edits to descriptor howto
In-Reply-To: <1367547112.04.0.920947702161.issue17894@psf.upfronthosting.co.za>
Message-ID: <1570731332.42.0.0256959983324.issue17894@roundup.psfhosted.org>


Change by Ned Batchelder <ned at nedbatchelder.com>:


----------
resolution: rejected -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17894>
_______________________________________

From report at bugs.python.org  Thu Oct 10 14:18:17 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 10 Oct 2019 18:18:17 +0000
Subject: [issue38435] Start the deprecation cycle for subprocess preexec_fn
Message-ID: <1570731497.4.0.313201495913.issue38435@roundup.psfhosted.org>


New submission from Gregory P. Smith <greg at krypto.org>:

subprocess's preexec_fn feature needs to enter PendingDeprecationWarning state in 3.9, to become a DeprecationWarning in 3.10, with a goal of removing it in 3.11.

Rationale: We now live in a world full of threads, it is entirely unsafe to call back into the python interpreter within the forked child before exec per POSIX specification.

We've also already made preexec_fn no longer supported from CPython subinterpreters in 3.8.

If there are not already issues open for desired features of subprocess that do not yet have replacements or workarounds for *specific* actions that preexec_fn is being used for in your application, please open feature requests for those.  (ex: calling umask is https://bugs.python.org/issue38417, and group, uid, gid setting has already landed in 3.9)

----------
assignee: gregory.p.smith
messages: 354397
nosy: gregory.p.smith
priority: normal
severity: normal
stage: needs patch
status: open
title: Start the deprecation cycle for subprocess preexec_fn
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38435>
_______________________________________

From report at bugs.python.org  Thu Oct 10 14:25:51 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 10 Oct 2019 18:25:51 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570731951.3.0.800765251372.issue38417@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

preexec_fn has been mentally and advisability deprecated for years. :) 
I'll mark it officially with pending deprecation in 3.9 destined to be removed in 3.11.  tracking that in its own rollup issue https://bugs.python.org/issue38435

As far as posix_spawn goes, I expect these kinds of between fork+exec features to be something that prevents posix_spawn from being usable.  As are many other things.  People who want to use posix_spawn will need to know that and seek to avoid those.  That's a documentation issue first and foremost.  Our existing POpen API is very old and wasn't designed to make that nice.

A new API could be made that *only* supports posix_spawn available features if you want an entrypoint that encourages the generally lower latency posix_spawn path.  (A subprocess.spawn function similar to subprocess.run perhaps?)  That should be taken up within its own enhancement issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Thu Oct 10 15:16:04 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Thu, 10 Oct 2019 19:16:04 +0000
Subject: [issue38436] Improved performance for list addition.
Message-ID: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>


New submission from Brandt Bucher <brandtbucher at gmail.com>:

The attached PR adds a fast path for BINARY_ADD instructions involving two lists, where the left list has a refcount of exactly 1.

In this case, we instead do a PySequence_InPlaceConcat operation. This has the affect of avoiding quadratic complexity for list summations, by keeping only one intermediate result and extending it in-place.

For (potentially large) lists:

    a + b + c + d ...

Currently executed as:

    tmp = a + b
    tmp = tmp + c
    tmp = tmp + d
    ...

With this change:

    tmp = a + b
    tmp += c
    tmp += d
    ...

Here are the pyperformance results (optimizations enabled):

Slower (6):
- pickle_list: 3.63 us +- 0.08 us -> 3.78 us +- 0.10 us: 1.04x slower (+4%)
- xml_etree_generate: 102 ms +- 2 ms -> 104 ms +- 3 ms: 1.02x slower (+2%)
- xml_etree_parse: 166 ms +- 4 ms -> 169 ms +- 9 ms: 1.02x slower (+2%)
- scimark_sparse_mat_mult: 5.42 ms +- 0.11 ms -> 5.47 ms +- 0.16 ms: 1.01x slower (+1%)
- pickle_dict: 23.6 us +- 0.8 us -> 23.8 us +- 0.4 us: 1.01x slower (+1%)
- scimark_fft: 413 ms +- 6 ms -> 416 ms +- 6 ms: 1.01x slower (+1%)

Faster (25):
- 2to3: 394 ms +- 18 ms -> 381 ms +- 8 ms: 1.03x faster (-3%)
- python_startup_no_site: 12.0 ms +- 0.2 ms -> 11.7 ms +- 0.2 ms: 1.03x faster (-3%)
- nqueens: 121 ms +- 2 ms -> 118 ms +- 3 ms: 1.03x faster (-2%)
- pathlib: 36.0 ms +- 1.3 ms -> 35.1 ms +- 0.9 ms: 1.02x faster (-2%)
- pickle_pure_python: 523 us +- 15 us -> 511 us +- 13 us: 1.02x faster (-2%)
- deltablue: 8.54 ms +- 0.25 ms -> 8.35 ms +- 0.27 ms: 1.02x faster (-2%)
- logging_silent: 220 ns +- 6 ns -> 215 ns +- 8 ns: 1.02x faster (-2%)
- raytrace: 566 ms +- 8 ms -> 554 ms +- 11 ms: 1.02x faster (-2%)
- hexiom: 11.2 ms +- 0.3 ms -> 11.0 ms +- 0.2 ms: 1.02x faster (-2%)
- go: 294 ms +- 6 ms -> 288 ms +- 5 ms: 1.02x faster (-2%)
- python_startup: 15.7 ms +- 0.4 ms -> 15.4 ms +- 0.5 ms: 1.02x faster (-2%)
- float: 136 ms +- 4 ms -> 134 ms +- 6 ms: 1.02x faster (-2%)
- scimark_sor: 232 ms +- 8 ms -> 228 ms +- 5 ms: 1.02x faster (-2%)
- fannkuch: 554 ms +- 8 ms -> 545 ms +- 9 ms: 1.02x faster (-2%)
- meteor_contest: 115 ms +- 2 ms -> 113 ms +- 3 ms: 1.02x faster (-2%)
- telco: 6.58 ms +- 0.22 ms -> 6.48 ms +- 0.15 ms: 1.02x faster (-2%)
- regex_effbot: 3.76 ms +- 0.08 ms -> 3.70 ms +- 0.09 ms: 1.02x faster (-2%)
- chaos: 129 ms +- 3 ms -> 127 ms +- 2 ms: 1.01x faster (-1%)
- regex_v8: 26.3 ms +- 0.4 ms -> 25.9 ms +- 0.6 ms: 1.01x faster (-1%)
- regex_compile: 200 ms +- 5 ms -> 197 ms +- 5 ms: 1.01x faster (-1%)
- logging_simple: 9.78 us +- 0.19 us -> 9.65 us +- 0.26 us: 1.01x faster (-1%)
- sqlite_synth: 3.24 us +- 0.10 us -> 3.20 us +- 0.06 us: 1.01x faster (-1%)
- unpickle: 16.4 us +- 0.5 us -> 16.2 us +- 0.5 us: 1.01x faster (-1%)
- logging_format: 10.8 us +- 0.2 us -> 10.7 us +- 0.3 us: 1.01x faster (-1%)
- json_loads: 30.2 us +- 0.8 us -> 29.9 us +- 0.6 us: 1.01x faster (-1%)

Benchmark hidden because not significant (14): json_dumps, nbody, pickle, pidigits, regex_dna, richards, scimark_lu, scimark_monte_carlo, spectral_norm, unpack_sequence, unpickle_list, unpickle_pure_python, xml_etree_iterparse, xml_etree_process

This is related to my earlier work in bpo-36229, however this is a much less invasive change that's limited to ceval.c, where our knowledge of context is much better.

----------
components: Interpreter Core
messages: 354399
nosy: brandtbucher
priority: normal
severity: normal
status: open
title: Improved performance for list addition.
type: performance
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Thu Oct 10 15:16:24 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Thu, 10 Oct 2019 19:16:24 +0000
Subject: [issue36229] Avoid unnecessary copies for list, set,
 and bytearray ops.
In-Reply-To: <1551994791.27.0.137413280424.issue36229@roundup.psfhosted.org>
Message-ID: <1570734984.79.0.0349460384924.issue36229@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
pull_requests: +16290
pull_request: https://github.com/python/cpython/pull/16705

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36229>
_______________________________________

From report at bugs.python.org  Thu Oct 10 15:16:24 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Thu, 10 Oct 2019 19:16:24 +0000
Subject: [issue38436] Improved performance for list addition.
In-Reply-To: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>
Message-ID: <1570734984.73.0.018510953218.issue38436@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
keywords: +patch
pull_requests: +16289
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16705

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Thu Oct 10 15:21:35 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Thu, 10 Oct 2019 19:21:35 +0000
Subject: [issue36229] Avoid unnecessary copies for list, set,
 and bytearray ops.
In-Reply-To: <1551994791.27.0.137413280424.issue36229@roundup.psfhosted.org>
Message-ID: <1570735295.48.0.417973402266.issue36229@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
pull_requests:  -16290

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36229>
_______________________________________

From report at bugs.python.org  Thu Oct 10 15:30:23 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 19:30:23 +0000
Subject: [issue38282] socketmodule.c: _FORTIFY_SOURCE=2 warning in AF_ALG case
 of getsockaddrarg()
In-Reply-To: <1569460305.42.0.728817437513.issue38282@roundup.psfhosted.org>
Message-ID: <1570735823.67.0.756083096427.issue38282@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset d565fb9828ee9c494bb7a80057a08e4738273e30 by Victor Stinner in branch 'master':
bpo-38282: Rewrite getsockaddrarg() helper function (GH-16698)
https://github.com/python/cpython/commit/d565fb9828ee9c494bb7a80057a08e4738273e30


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38282>
_______________________________________

From report at bugs.python.org  Thu Oct 10 15:30:31 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 10 Oct 2019 19:30:31 +0000
Subject: [issue38282] socketmodule.c: _FORTIFY_SOURCE=2 warning in AF_ALG case
 of getsockaddrarg()
In-Reply-To: <1569460305.42.0.728817437513.issue38282@roundup.psfhosted.org>
Message-ID: <1570735831.44.0.222605818338.issue38282@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16291
pull_request: https://github.com/python/cpython/pull/16706

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38282>
_______________________________________

From report at bugs.python.org  Thu Oct 10 15:39:02 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 10 Oct 2019 19:39:02 +0000
Subject: [issue38437] Set GC_DEBUG for debug builds of the interpreter
Message-ID: <1570736342.37.0.0664122521403.issue38437@roundup.psfhosted.org>


New submission from Pablo Galindo Salgado <pablogsal at gmail.com>:

While working on bpo-38379 I had to manually set the GC_DEBUG macro to 1 to activate the extra checks that 'validate_list' does. These checks are super useful to make sure all the gc lists used are consistent and in the expected state with the expected masks.

For this reason, I propose to always activate GC_DEBUG for debug builds of the interpreter. It will have a performance impact, but the debugging benefits are substantial.

----------
messages: 354401
nosy: pablogsal, vstinner
priority: normal
severity: normal
status: open
title: Set GC_DEBUG for debug builds of the interpreter
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38437>
_______________________________________

From report at bugs.python.org  Thu Oct 10 15:40:44 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 10 Oct 2019 19:40:44 +0000
Subject: [issue38437] Set GC_DEBUG for debug builds of the interpreter
In-Reply-To: <1570736342.37.0.0664122521403.issue38437@roundup.psfhosted.org>
Message-ID: <1570736444.02.0.728323000281.issue38437@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +patch
pull_requests: +16292
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16707

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38437>
_______________________________________

From report at bugs.python.org  Thu Oct 10 15:41:01 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 10 Oct 2019 19:41:01 +0000
Subject: [issue38437] Set GC_DEBUG for debug builds of the interpreter
In-Reply-To: <1570736342.37.0.0664122521403.issue38437@roundup.psfhosted.org>
Message-ID: <1570736461.87.0.287277285621.issue38437@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
stage: patch review -> 
versions:  -Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38437>
_______________________________________

From report at bugs.python.org  Thu Oct 10 16:24:39 2019
From: report at bugs.python.org (Bob Alexander)
Date: Thu, 10 Oct 2019 20:24:39 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
Message-ID: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>


New submission from Bob Alexander <bobjalex at gmail.com>:

This program:

import argparse
ap = argparse.ArgumentParser()
ap.add_argument("arg", nargs="*")
ap.parse_args()

Gives usage message:
usage: help_complexity.py [-h] [arg [arg ...]]

It's correct, but unnecessarily complex and challenging to the user.
If I were manually writing the usage, arg... would do, or maybe [arg ...] to be consistent with other messages??

----------
components: Library (Lib)
messages: 354402
nosy: bobjalex
priority: normal
severity: normal
status: open
title: argparse "usage" overly-complex with nargs="*"
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Thu Oct 10 16:40:37 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 20:40:37 +0000
Subject: [issue38437] Set GC_DEBUG for debug builds of the interpreter
In-Reply-To: <1570736342.37.0.0664122521403.issue38437@roundup.psfhosted.org>
Message-ID: <1570740037.02.0.53988688402.issue38437@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Under which condition can such list be corrupted?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38437>
_______________________________________

From report at bugs.python.org  Thu Oct 10 16:44:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 10 Oct 2019 20:44:47 +0000
Subject: [issue38435] Start the deprecation cycle for subprocess preexec_fn
In-Reply-To: <1570731497.4.0.313201495913.issue38435@roundup.psfhosted.org>
Message-ID: <1570740287.54.0.950174055176.issue38435@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

What is the recommanded way to replace preexec_fn?

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38435>
_______________________________________

From report at bugs.python.org  Thu Oct 10 16:56:23 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 10 Oct 2019 20:56:23 +0000
Subject: [issue38437] Set GC_DEBUG for debug builds of the interpreter
In-Reply-To: <1570736342.37.0.0664122521403.issue38437@roundup.psfhosted.org>
Message-ID: <1570740983.4.0.749612033912.issue38437@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

> Under which condition can such list be corrupted?

If someone is adding/modifiying the gc and calls any of the functions that set the gc flags like (PREV_MASK_COLLECTING).

One example is that after calling move_unreachable(), the unreachable set has NEXT_MASK_UNREACHABLE and therefore is an invalid list (until move_legacy_finalizers removes the flag and makes it valid again). If you mess the order or violate any of the contract, the lists will be invalid. It helps a lot to know that you are not leaving the lists in invalid state by mistake or on the other hand, to check that they are valid when they are supposed to be valid.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38437>
_______________________________________

From report at bugs.python.org  Thu Oct 10 17:24:06 2019
From: report at bugs.python.org (Tim Peters)
Date: Thu, 10 Oct 2019 21:24:06 +0000
Subject: [issue38437] Set GC_DEBUG for debug builds of the interpreter
In-Reply-To: <1570736342.37.0.0664122521403.issue38437@roundup.psfhosted.org>
Message-ID: <1570742646.84.0.43974787224.issue38437@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

+1.  This code got quite brittle when they decided to fit two pointers, a fat integer, and 3 flags into a struct with room for only the two pointers ;-)  It's a mine field now.  Enabling one of the few automated mine detectors is thoroughly sensible.

----------
nosy: +tim.peters

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38437>
_______________________________________

From report at bugs.python.org  Thu Oct 10 17:31:38 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 10 Oct 2019 21:31:38 +0000
Subject: [issue38435] Start the deprecation cycle for subprocess preexec_fn
In-Reply-To: <1570740287.54.0.950174055176.issue38435@roundup.psfhosted.org>
Message-ID: <CAGE7PNJEs1Vi7kwcNXmCLDVO5ApEZLpXNy7Z3KU7QdMGGx0Ptg@mail.gmail.com>


Gregory P. Smith <greg at krypto.org> added the comment:

With task specific arguments.  cwd, start_new_session, group, extra_groups,
user, etc..

We cannot provide a general do everything replacement and should not try.
It not possible.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38435>
_______________________________________

From report at bugs.python.org  Thu Oct 10 17:45:20 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 10 Oct 2019 21:45:20 +0000
Subject: [issue38437] Set GC_DEBUG for debug builds of the interpreter
In-Reply-To: <1570736342.37.0.0664122521403.issue38437@roundup.psfhosted.org>
Message-ID: <1570743920.49.0.599845547607.issue38437@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 320dd504ddf65efe946e6d1e89053ed2d7ebe1e9 by Pablo Galindo in branch 'master':
bpo-38437: Activate GC_DEBUG when PY_DEBUG is set (GH-16707)
https://github.com/python/cpython/commit/320dd504ddf65efe946e6d1e89053ed2d7ebe1e9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38437>
_______________________________________

From report at bugs.python.org  Thu Oct 10 17:49:20 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 10 Oct 2019 21:49:20 +0000
Subject: [issue38437] Set GC_DEBUG for debug builds of the interpreter
In-Reply-To: <1570736342.37.0.0664122521403.issue38437@roundup.psfhosted.org>
Message-ID: <1570744160.92.0.258347410345.issue38437@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38437>
_______________________________________

From report at bugs.python.org  Thu Oct 10 17:49:32 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 10 Oct 2019 21:49:32 +0000
Subject: [issue38437] Set GC_DEBUG for debug builds of the interpreter
In-Reply-To: <1570736342.37.0.0664122521403.issue38437@roundup.psfhosted.org>
Message-ID: <1570744172.35.0.397168903979.issue38437@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Thanks Victor and Tim!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38437>
_______________________________________

From report at bugs.python.org  Thu Oct 10 17:55:33 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 10 Oct 2019 21:55:33 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
In-Reply-To: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>
Message-ID: <1570744533.48.0.52127310983.issue38438@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

I think [arg ...] would make sense.

Removing 3.5 and 3.6, since they're in security only mode. Adding 3.9.

----------
nosy: +eric.smith
versions: +Python 3.9 -Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Thu Oct 10 18:07:13 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 10 Oct 2019 22:07:13 +0000
Subject: [issue38436] Improved performance for list addition.
In-Reply-To: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>
Message-ID: <1570745233.43.0.000687727665718.issue38436@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

>From the PR:

Where the benchmarks executed with CPU isolation? I am a bit suspicious of the

- pickle_list: 3.63 us +- 0.08 us -> 3.78 us +- 0.10 us: 1.04x slower (+4%)
If not, can you repeat them with CPU isolation and affinity? Check this for more info

----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Thu Oct 10 18:10:20 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Thu, 10 Oct 2019 22:10:20 +0000
Subject: [issue36553] inspect.is_decorator_call(frame)
In-Reply-To: <1554711715.55.0.758701327001.issue36553@roundup.psfhosted.org>
Message-ID: <1570745420.08.0.0689161807735.issue36553@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36553>
_______________________________________

From report at bugs.python.org  Thu Oct 10 18:16:10 2019
From: report at bugs.python.org (Nathaniel Smith)
Date: Thu, 10 Oct 2019 22:16:10 +0000
Subject: [issue32561] Add API to io objects for cache-only reads/writes
In-Reply-To: <1516068442.29.0.467229070634.issue32561@psf.upfronthosting.co.za>
Message-ID: <1570745770.56.0.312606268417.issue32561@roundup.psfhosted.org>


Nathaniel Smith <njs at pobox.com> added the comment:

> If you wanted to keep async disk access separate from the io module, then what we'd have to do is to create a fork of all the code in the io module, and add this feature to it.

Thinking about this again today, I realized there *might* be another option.

The tricky thing about supporting async file I/O is that users want the whole io module interface, and we don't want to have to reimplement all the functionality in TextIOWrapper, BufferedReader, BufferedWriter, etc. And we still need the blocking functionality too, for when we fall back to threads.

But, here's a possible hack. We could implement our own version of 'FileIO' that wraps around a real FileIO. Every operation just delegates to the underlying FileIO ? but with a twist. Something like:

def wrapped_op(self, *args):
    if self._cached_op.key == (op, args):
        return self._cached_op.result
    if MAGIC_THREAD_LOCAL.io_is_forbidden:
        def cache_filler():
            MAGIC_THREAD_LOCAL.io_is_forbidden = False
            self._cached_op = self._real_file.op(*args)
        raise IOForbiddenError(cache_filler)
    return self._real_file.op(*args)

And then in order to implement an async operation, we do something like:

async def op(self, *args):
    while True:
        try:
            # First try fulfilling the operation from cache
            MAGIC_THREAD_LOCAL.io_is_forbidden = True
            return self._io_obj.op(*args)
        except IOForbiddenError as exc:
            # We have to actually hit the disk
            # Run the real IO operation in a thread, then try again
            await in_thread(cache_filler)
        finally:
            del MAGIC_THREAD_LOCAL.io_is_forbidden

This is pretty convoluted: we keep trying the operation on the outer "buffered" object, seeing which low-level I/O operation it gets stuck on, doing that I/O operation, and trying again. There's all kinds of tricky non-local state here; like for example, there isn't any formal guarantee that the next time we try the "outer" I/O operation it will end up making exactly the same request to the "inner" RawIO object. If you try performing I/O operations on the same file from multiple tasks concurrently then you'll get all kinds of havoc. But if it works, then it does have two advantages:

First, it doesn't require changes to the io module, which is at least nice for experimentation.

And second, it's potentially compatible with the io_uring style of async disk I/O API. I don't actually know if this matters; if you look at the io_uring docs, the only reason they say they're more efficient than a thread pool is that they can do the equivalent of preadv(RWF_NOWAIT), and it's a lot easier to add preadv(RWF_NOWAIT) to a thread pool than it is to implement io_uring. But still, this approach is potentially more flexible than my original idea.

We'd still have to reimplement open() in order to set up our weird custom IO stacks, but hopefully that's not *too* bad, since it's mostly just a bunch of if statements to decide which wrappers to stick around the raw IO object.

My big concern is, that I'm not actually sure if this works :-).

The thing is, for this to work, we need TextIOWrapper/BufferedReader/BufferedWriter to be very well-behaved when the underlying operation raises an exception. In particular, if they're doing a complex operation that requires multiple calls to the underlying object, and the second call raises an exception, they need to keep the first call's results in their buffer so that next time they can pick up where they left off. And I have no idea if that's true.

I guess if you squint this is kind of like the non-blocking support in the io module ? IOForbiddenError is like NonBlockingError. The big difference is that here, we don't have any "partial success" state at the low-level; either we do the operation immediately, or we punt and do the operation in a thread. Either way it completes as a single indivisible unit. So that might simplify things? From a quick skim of issue13322 it sounds like a lot of the problems with the current "non-blocking" mode come from these partial success states, but I haven't read it in detail.

----------
title: Add API to io objects for non-blocking reads/writes -> Add API to io objects for cache-only reads/writes

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32561>
_______________________________________

From report at bugs.python.org  Thu Oct 10 18:55:20 2019
From: report at bugs.python.org (Eryk Sun)
Date: Thu, 10 Oct 2019 22:55:20 +0000
Subject: [issue38428] Can't gracefully ctrl+C multiprocessing pool on Python3
 & Windows
In-Reply-To: <1570696551.92.0.213022823921.issue38428@roundup.psfhosted.org>
Message-ID: <1570748120.99.0.393079648968.issue38428@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

> Python 2.7 had totally different code, IIRC.

In 2.7 the wait() method of threading._Condition implements the timeout with a loop the calls time.sleep() with an increasing delay from 500 microseconds up to 50 ms, and no more than the remaining time.

> But the good news is that we should be able to use code similar to 
> what's in Modules/timemodule.c#L1878 (the pysleep() function) to also 
> wait on the event we use to emulate signals on Windows. 

If Python continues to use emulated condition variables, then the kernel wait in _PyCOND_WAIT_MS can easily be adapted to include the SIGINT event. However, isn't it planned at some point to remove the emulated condition-variable implementation in favor of native condition variables? If so and PyCOND_WAIT and PyCOND_TIMEDWAIT end up calling SleepConditionVariableSRW, there's no obvious way to interrupt this to support Ctrl+C and Ctrl+Break (given a custom SIGBREAK handler) in the main thread. 

In particular, in Windows 8+, SleepConditionVariableSRW begins by spinning in user mode for a fixed number of cycles. Then it calls NtWaitForAlertByThreadId to block until alerted by NtAlertThreadByThreadId, which gets called internally by Wake[All]ConditionVariable. It wouldn't be kosher to call NtAlertThreadByThreadId directly in order to alert the main thread because it's an undocumented system call, plus it's poking into the internal implementation details of SleepConditionVariableSRW and WakeConditionVariable, which could leave the variable in a bad state.

----------
nosy: +eryksun

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38428>
_______________________________________

From report at bugs.python.org  Thu Oct 10 19:14:29 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Thu, 10 Oct 2019 23:14:29 +0000
Subject: [issue38348] Make python -m ast more configurable
In-Reply-To: <1570029299.56.0.0303865742584.issue38348@roundup.psfhosted.org>
Message-ID: <1570749269.97.0.491398633417.issue38348@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

I don't have any strong opinion either way, so it looks like we need to wait until someone else will ask for this.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38348>
_______________________________________

From report at bugs.python.org  Thu Oct 10 19:14:55 2019
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Thu, 10 Oct 2019 23:14:55 +0000
Subject: [issue38439] IDLE menu icon is blurry on GNOME
Message-ID: <1570749295.67.0.980962290264.issue38439@roundup.psfhosted.org>


New submission from Miro Hron?ok <miro at hroncok.cz>:

See the attached screenshot. All the GNOME apps have scalable icons, only the IDLE icon is scaled up from 48x48 pixels.

I've found similar issue32129, but apparently the accepted resolution was to change a bit of code somewhere, not to provide higher resolution icons.

----------
assignee: terry.reedy
components: IDLE
files: idle.png
messages: 354415
nosy: hroncok, terry.reedy
priority: normal
severity: normal
status: open
title: IDLE menu icon is blurry on GNOME
versions: Python 3.7, Python 3.8, Python 3.9
Added file: https://bugs.python.org/file48655/idle.png

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38439>
_______________________________________

From report at bugs.python.org  Thu Oct 10 19:45:16 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 10 Oct 2019 23:45:16 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1570751116.4.0.133927662779.issue38344@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
stage: patch review -> commit review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Thu Oct 10 19:46:23 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 10 Oct 2019 23:46:23 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
In-Reply-To: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>
Message-ID: <1570751183.18.0.724096636422.issue38359@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
stage: backport needed -> commit review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Thu Oct 10 19:47:03 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 10 Oct 2019 23:47:03 +0000
Subject: [issue38355] ntpath.realpath() fails on sys.executable
In-Reply-To: <1570055857.28.0.434394542652.issue38355@roundup.psfhosted.org>
Message-ID: <1570751223.09.0.771616578857.issue38355@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
stage: backport needed -> commit review

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38355>
_______________________________________

From report at bugs.python.org  Thu Oct 10 20:06:40 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 11 Oct 2019 00:06:40 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
In-Reply-To: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>
Message-ID: <1570752400.73.0.543888060056.issue38438@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
nosy: +brandtbucher

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Thu Oct 10 20:18:53 2019
From: report at bugs.python.org (Teddy Thomas)
Date: Fri, 11 Oct 2019 00:18:53 +0000
Subject: [issue38014] Python 3.7 does not compile
In-Reply-To: <1567477987.66.0.578307493025.issue38014@roundup.psfhosted.org>
Message-ID: <1570753133.71.0.882391577658.issue38014@roundup.psfhosted.org>


Change by Teddy Thomas <tjthomas292 at gmail.com>:


----------
nosy: +tthoma24

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38014>
_______________________________________

From report at bugs.python.org  Thu Oct 10 20:44:07 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 11 Oct 2019 00:44:07 +0000
Subject: [issue38422] Clarify docstrings of pathlib suffix(es)
In-Reply-To: <1570634139.23.0.159522926495.issue38422@roundup.psfhosted.org>
Message-ID: <1570754647.32.0.465431420225.issue38422@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
type:  -> enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38422>
_______________________________________

From report at bugs.python.org  Thu Oct 10 21:00:04 2019
From: report at bugs.python.org (Matt Joiner)
Date: Fri, 11 Oct 2019 01:00:04 +0000
Subject: [issue13322] The io module doesn't support non-blocking files
In-Reply-To: <1320246535.71.0.465783773129.issue13322@psf.upfronthosting.co.za>
Message-ID: <1570755604.97.0.22246207434.issue13322@roundup.psfhosted.org>


Change by Matt Joiner <anacrolix at gmail.com>:


----------
nosy:  -anacrolix

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13322>
_______________________________________

From report at bugs.python.org  Thu Oct 10 21:30:06 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 11 Oct 2019 01:30:06 +0000
Subject: [issue17894] Edits to descriptor howto
In-Reply-To: <1367547112.04.0.920947702161.issue17894@psf.upfronthosting.co.za>
Message-ID: <1570757405.99.0.279864514826.issue17894@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I am actively working on updates.  However, the work on Python 3.8's whatsnew and doc fixes are a more immediate priority.  Cumulatively, I've put an a lot of effort in to this and have made a continuous stream of improvements over the years including this year.  In a way, maintaining this entry is not much different from being a module maintainer who has the principal responsibility and authority over the updates.  This is something that I frequently teach and have battle tested course material that I'm looking forward to including in the entry.

Please give me space and don't shove. IMO some of the past posts on this subject are border-line abusive, leaving me feeling hounded and degraded (especially with respect to my writing style).  Please be kind and let me continue to improve my contribution at my own pace.  

Please don't re-open this issue. I have marked the patch as rejected because it is at odds with the improvements that I already have in progress and because some of it is essentially just a stylistic difference.

----------
resolution:  -> rejected
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17894>
_______________________________________

From report at bugs.python.org  Thu Oct 10 22:02:12 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 11 Oct 2019 02:02:12 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
In-Reply-To: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>
Message-ID: <1570759332.98.0.307308216157.issue38438@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Thu Oct 10 22:40:05 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Fri, 11 Oct 2019 02:40:05 +0000
Subject: [issue38167] O_DIRECT read fails with 4K mmap buffer
In-Reply-To: <1568417320.49.0.42295605579.issue38167@roundup.psfhosted.org>
Message-ID: <1570761605.45.0.783447412785.issue38167@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

Yeah, not a bug. The I/O subsystem was substantially rewritten between Python 2 and Python 3, so you sometimes need to be more explicit about things like buffering, but as you note, once the buffering is correct, the code works; there's nothing to fix.

----------
resolution:  -> not a bug
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38167>
_______________________________________

From report at bugs.python.org  Fri Oct 11 00:27:28 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 11 Oct 2019 04:27:28 +0000
Subject: [issue38440] Possible news issues with IDLE
Message-ID: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>


New submission from Raymond Hettinger <raymond.hettinger at gmail.com>:

I've been exercising the 3.8.0rc1 version of IDLE and noticed two anomalies but have not had a chance to investigate further:

* Periodically in a long shell session, the cursor jumps to the beginning of the cumulative text output.  This necessitates a lot of scrolling to get back down to the active part of the session.

* The pop-up message box for interrupting currently running code will appear several times in succession.  Dismissing the box doesn't clear a queue of events, so the message may occur several times in a row.

----------
assignee: terry.reedy
components: IDLE
messages: 354418
nosy: rhettinger, terry.reedy
priority: normal
severity: normal
status: open
title: Possible news issues with IDLE
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Fri Oct 11 01:11:44 2019
From: report at bugs.python.org (Matej Cepl)
Date: Fri, 11 Oct 2019 05:11:44 +0000
Subject: [issue38014] Python 3.7 does not compile
In-Reply-To: <1567477987.66.0.578307493025.issue38014@roundup.psfhosted.org>
Message-ID: <1570770704.32.0.0787776240946.issue38014@roundup.psfhosted.org>


Change by Matej Cepl <mcepl at cepl.eu>:


----------
nosy:  -mcepl

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38014>
_______________________________________

From report at bugs.python.org  Fri Oct 11 01:19:43 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 11 Oct 2019 05:19:43 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
In-Reply-To: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>
Message-ID: <1570771183.67.0.598950245811.issue38438@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Bob, would like to create a PR?

----------
assignee:  -> rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Fri Oct 11 02:06:52 2019
From: report at bugs.python.org (Mohsin Boruah)
Date: Fri, 11 Oct 2019 06:06:52 +0000
Subject: [issue35058] Unable to Install Python on Windows
In-Reply-To: <1540390509.38.0.788709270274.issue35058@psf.upfronthosting.co.za>
Message-ID: <1570774012.55.0.0767243667404.issue35058@roundup.psfhosted.org>


Mohsin Boruah <gotechnocious at gmail.com> added the comment:

Thats an amazing information.

----------
nosy: +Mohsin Boruah

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35058>
_______________________________________

From report at bugs.python.org  Fri Oct 11 02:08:42 2019
From: report at bugs.python.org (Mohsin Boruah)
Date: Fri, 11 Oct 2019 06:08:42 +0000
Subject: [issue35058] Unable to Install Python on Windows
In-Reply-To: <1540390509.38.0.788709270274.issue35058@psf.upfronthosting.co.za>
Message-ID: <1570774122.22.0.356643575547.issue35058@roundup.psfhosted.org>


Mohsin Boruah <gotechnocious at gmail.com> added the comment:

Also try this article which I believe will help you out.
http://techstuffsarena.com/2019/01/15/how-to-fix-windows-10-update-error-0x8024a105/

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35058>
_______________________________________

From report at bugs.python.org  Fri Oct 11 02:28:46 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 11 Oct 2019 06:28:46 +0000
Subject: [issue38439] Python needs higher resolution app/menu icons
In-Reply-To: <1570749295.67.0.980962290264.issue38439@roundup.psfhosted.org>
Message-ID: <1570775326.59.0.73317234606.issue38439@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

I think you misunderstood #32129.  It was specific to macOS Aqua systems.  On Windows and generally on Linux, window title bars have a little icon on the left end (at least on Windows).  IDLE uses the tcl/tk GUI framework and by default, on these systems, tk windows have a generic tk icon at the left end.  (At least that is the position on Windows.) #20406 replaced the tk icon with versions of the Python app icon.

On mac Aqua, tk window title bars do not have an icon.  Somehow Mac, Aqua, and tk interact so that the replacement icon instead replaced Apple's version of the Python app (menu) icon, which is different from the *nix/Windows python app icon. This was unintended and a bug.  The fix was to not execute the replacement code on Mac Aqua systems.

Your png shows the Python app icon used for IDLE as a Python application.  It is the same one used for Python applications on the Windows taskbar, including but not limited to IDLE.  I agreed on #32129 that it would be good if someone contributed higher resolution versions.  But it is not specifically an IDLE issue.  I will say more tomorrow.

----------
assignee: terry.reedy -> 
nosy: +serhiy.storchaka
stage:  -> needs patch
title: IDLE menu icon is blurry on GNOME -> Python needs higher resolution app/menu icons

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38439>
_______________________________________

From report at bugs.python.org  Fri Oct 11 02:45:40 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 11 Oct 2019 06:45:40 +0000
Subject: [issue38440] Possible news issues with IDLE
In-Reply-To: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>
Message-ID: <1570776340.95.0.911578378305.issue38440@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

I presume this is on macOS, with its finicky tk.  Have you 'upgraded' to Catalina?  I have not, that I know of.  I will try 3.8.0rc1 on my MacBook Air tomorrow.

1. Jumps.  All the way to before the beginning "Python 3.8..." splash line?  How long is long?  I may not do not do long enough sessions on the mac to see this.

2. Do you mean the box with "Your program is still running!\nDo you want to kill it?" resulting from 'quit()' or 'exit()' or occasionally otherwise?  Will test tomorrow.

----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Fri Oct 11 03:13:31 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Oct 2019 07:13:31 +0000
Subject: [issue38436] Improved performance for list addition.
In-Reply-To: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>
Message-ID: <1570778011.42.0.0316610896656.issue38436@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

How often do you need to add three or more lists in comparison with other uses of the "+" operator?

How larger is the benefit of this optimization?

How much it slows down other uses of the "+" operator?

Would be nice if you provide some numbers.

More efficient way of concatenating several lists in single expression is:

    [*a, *b, *c, *d, ...]

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Fri Oct 11 03:26:31 2019
From: report at bugs.python.org (Aurora)
Date: Fri, 11 Oct 2019 07:26:31 +0000
Subject: [issue38441] failing to build the Documentation
Message-ID: <1570778791.42.0.554605100784.issue38441@roundup.psfhosted.org>


New submission from Aurora <auroraofearth at ya.ru>:

I'm failing to build the cpython/Doc dir.

The full build log is as follows:

mkdir -p build
Building NEWS from Misc/NEWS.d with blurb
PATH=./venv/bin:$PATH sphinx-build -b epub -d build/doctrees -D latex_elements.papersize=  -W . build/epub 
Running Sphinx v2.2.0
making output directory... done
building [mo]: targets for 0 po files that are out of date
building [epub]: targets for 476 source files that are out of date
updating environment: [new config] 476 added, 0 changed, 0 removed
reading sources... [100%] whatsnew/index                                                                                                                                 

Warning, treated as error:
/home/aurora/A.Code/Python/Reference/python/cpython/Doc/library/email.message.rst:4:duplicate object description of email.message, other instance in library/email.compat32-message, use :noindex: for one of them
make: *** [Makefile:46: build] Error 2


Running on Debian Experimental kernel v5.3

----------
assignee: docs at python
components: Documentation
messages: 354425
nosy: aurora, docs at python
priority: normal
severity: normal
status: open
title: failing to build the Documentation
type: compile error
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38441>
_______________________________________

From report at bugs.python.org  Fri Oct 11 03:28:14 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 07:28:14 +0000
Subject: [issue38440] Possible new issues with IDLE
In-Reply-To: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>
Message-ID: <1570778894.53.0.121987879871.issue38440@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

(Just FYI: the version of Tcl/Tk, 8.6.8, we are shipping with the python.org installers for macOS is unchanged since 3.7.2 a year ago, 2.7.16 (in March), and has not changed during the 3.8.0 pre-release cycle.  We did try to update to 8.6.9 for 3.7.2rc1 but there were too many new regressions so we reverted to 8.6.8 and have stuck with it awaiting a release of 8.7.10.)

----------
title: Possible news issues with IDLE -> Possible new issues with IDLE

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Fri Oct 11 03:35:46 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 07:35:46 +0000
Subject: [issue38441] failing to build the Documentation
In-Reply-To: <1570778791.42.0.554605100784.issue38441@roundup.psfhosted.org>
Message-ID: <1570779346.88.0.807381643165.issue38441@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Thanks for the report.  That problem was fixed on the master branch by 141da44bb45bc182886303fce92cbbae5631cb4c on 2019-06-03.  Suggest you build from a more recent source release or updated git repo.

----------
nosy: +ned.deily
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38441>
_______________________________________

From report at bugs.python.org  Fri Oct 11 03:38:37 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Oct 2019 07:38:37 +0000
Subject: [issue38442] Doc/whatsnew/3.8.rst has an execution bit
Message-ID: <1570779517.76.0.861587491217.issue38442@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

It likely happened when it was edited on Windows.

----------
assignee: docs at python
components: Documentation
messages: 354428
nosy: docs at python, lukasz.langa, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Doc/whatsnew/3.8.rst has an execution bit
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38442>
_______________________________________

From report at bugs.python.org  Fri Oct 11 03:38:58 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Oct 2019 07:38:58 +0000
Subject: [issue38442] Doc/whatsnew/3.8.rst has an execution bit
In-Reply-To: <1570779517.76.0.861587491217.issue38442@roundup.psfhosted.org>
Message-ID: <1570779538.34.0.909718354875.issue38442@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16293
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16715

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38442>
_______________________________________

From report at bugs.python.org  Fri Oct 11 03:53:54 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 07:53:54 +0000
Subject: [issue38443] unavailable --with-universal-archs= macOS confgure
 options fail cryptically
Message-ID: <1570780434.84.0.507087684939.issue38443@roundup.psfhosted.org>


New submission from Ned Deily <nad at python.org>:

./configure's --with-universal-archs= supports a number of different CPU architecture combinations.  However most of them are no longer supported on current macOS systems.  If you choose an option with archs not available in the build tool chain in use, the configure script fails in various cryptic ways, usually with multiple configure test failures like:

checking dlfcn.h presence... yes
configure: WARNING: dlfcn.h: present but cannot be compiled
configure: WARNING: dlfcn.h:     check for missing prerequisite headers?
configure: WARNING: dlfcn.h: see the Autoconf documentation
configure: WARNING: dlfcn.h:     section "Present But Cannot Be Compiled"
configure: WARNING: dlfcn.h: proceeding with the compiler's result
configure: WARNING:     ## --------------------------------------- ##
configure: WARNING:     ## Report this to https://bugs.python.org/ ##
configure: WARNING:     ## --------------------------------------- ##

./configure should be more user-friendly here.  At a minimum, it should report near the beginning exactly which archs are going to be tested; it already reports the --with-universal-archs value.  Even better it should explicitly test for support of each arch in the build tool chain in use and stop if any of the requested archs are not available.

----------
components: Build, macOS
messages: 354429
nosy: ned.deily, ronaldoussoren
priority: normal
severity: normal
stage: needs patch
status: open
title: unavailable --with-universal-archs= macOS confgure options fail cryptically
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38443>
_______________________________________

From report at bugs.python.org  Fri Oct 11 04:08:33 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 08:08:33 +0000
Subject: [issue38443] unavailable --with-universal-archs= macOS confgure
 options fail cryptically
In-Reply-To: <1570780434.84.0.507087684939.issue38443@roundup.psfhosted.org>
Message-ID: <1570781313.81.0.691188082982.issue38443@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Also note that, on current macOS systems, specifying just --enable-universalsdk to ./configure results in an implicit --with-universal-archs of intel (which implies both x86_64 and i386).

checking for --enable-universalsdk... /
checking for --with-universal-archs... intel

With macOS 10.15 Catalina and Xcode 11, i364 arch is no longer supported and that results in another cryptic ./configure failure:

checking size of size_t... configure: error: in `/Users/sysadmin/cpython':
configure: error: cannot compute sizeof (size_t)
See `config.log' for more details

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38443>
_______________________________________

From report at bugs.python.org  Fri Oct 11 04:20:55 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 08:20:55 +0000
Subject: [issue38014] ./configure on recent macOS versions can fail with
 multiple "present but cannot be compiled" messages
In-Reply-To: <1567477987.66.0.578307493025.issue38014@roundup.psfhosted.org>
Message-ID: <1570782055.35.0.483468652053.issue38014@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Going and back and looking closer at the original failure, I see now that the root cause of the configure failures *is* using --with-universal-archs=64-bit.  As noted in the Mac/README file, "64-bit" means compile for both "ppc64" and "x86_64" architectures; the configure tests fail because the Apple-supplied build tools (via Xcode or the Command Line Tools) have not supported either ppc or ppc64 for many years (since 10.7, I believe).  In more recent releases prior to macOS 10.15 Catalina, macOS still supported running programs in either intel-32 (i386) or intel-64 (x86_64) so there was still some use for --with-universal-archs=intel, which compiles for both x64_64 and i386.  But 10.15 Catalina no longer includes 32-bit libraries and frameworks, so it is not possible to run 32-bit executables natively anymore.  Thus the only architecture option that is of use on 10.15 is the default, x86_64.  So my original suggestion, to remove the --enable-universalsdk and --with-universal-arch options from your ./configure command should solve the problems you are seeing.  I also verified that --enable-optimizations without --wiht-universal-arch and --enable-universalsdk resulted in a successful build (after following the Devguide's recommendations to install missing libraries using Homebrew).

That said, ./configure should be less cryptic about these kinds of problems.  I've opened Issue38443 to suggest that ./configure be enhanced to give better error messages when a CPU arch is not available to build.

I was unable to reproduce the different failure reported by Bill Minasian in msg351312.  If that problem can be reproduced with the stable release of 10.15 and Xcode 11, please open a new issue for it with details on how to reproduce.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed
title: Python 3.7 does not compile -> ./configure on recent macOS versions can fail with multiple "present but cannot be compiled" messages

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38014>
_______________________________________

From report at bugs.python.org  Fri Oct 11 04:21:54 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 08:21:54 +0000
Subject: [issue38014] ./configure on recent macOS versions can fail with
 multiple "present but cannot be compiled" messages
In-Reply-To: <1567477987.66.0.578307493025.issue38014@roundup.psfhosted.org>
Message-ID: <1570782114.14.0.0235457985293.issue38014@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Going back and looking closer at the original failure, I see now that the root cause of the configure failures *is* using --with-universal-archs=64-bit.  As noted in the Mac/README file, "64-bit" means compile for both "ppc64" and "x86_64" architectures; the configure tests fail because the Apple-supplied build tools (via Xcode or the Command Line Tools) have not supported either ppc or ppc64 for many years (since 10.7, I believe).  In more recent releases prior to macOS 10.15 Catalina, macOS still supported running programs in either intel-32 (i386) or intel-64 (x86_64) so there was still some use for --with-universal-archs=intel, which compiles for both x64_64 and i386.  But 10.15 Catalina no longer includes 32-bit libraries and frameworks, so it is not possible to run 32-bit executables natively anymore.  Thus the only architecture option that is of use on 10.15 is the default, x86_64.  So my original suggestion, to remove the --enable-universalsdk and --with-universal-arch options from your ./configure command should solve the problems you are seeing.  I also verified that --enable-optimizations without --wiht-universal-arch and --enable-universalsdk resulted in a successful build (after following the Devguide's recommendations to install missing libraries using Homebrew).

That said, ./configure should be less cryptic about these kinds of problems.  I've opened Issue38443 to suggest that ./configure be enhanced to give better error messages when a CPU arch is not available to build.

I was unable to reproduce the different failure reported by Bill Minasian in msg351312.  If that problem can be reproduced with the stable release of 10.15 and Xcode 11, please open a new issue for it with details on how to reproduce.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38014>
_______________________________________

From report at bugs.python.org  Fri Oct 11 04:22:08 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 08:22:08 +0000
Subject: [issue38014] ./configure on recent macOS versions can fail with
 multiple "present but cannot be compiled" messages
In-Reply-To: <1567477987.66.0.578307493025.issue38014@roundup.psfhosted.org>
Message-ID: <1570782128.0.0.220693243604.issue38014@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
Removed message: https://bugs.python.org/msg354431

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38014>
_______________________________________

From report at bugs.python.org  Fri Oct 11 04:41:09 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 08:41:09 +0000
Subject: [issue38440] Possible new issues with IDLE
In-Reply-To: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>
Message-ID: <1570783269.63.0.202849255307.issue38440@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

(?8.7.10? should be ?8.6.10?)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Fri Oct 11 04:44:47 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Oct 2019 08:44:47 +0000
Subject: [issue38442] Doc/whatsnew/3.8.rst has an execution bit
In-Reply-To: <1570779517.76.0.861587491217.issue38442@roundup.psfhosted.org>
Message-ID: <1570783487.33.0.36002037752.issue38442@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset cbb548130caf24275fa16100bccc537570cb46df by Serhiy Storchaka in branch 'master':
bpo-38442: Remove an execution bit from Doc/whatsnew/3.8.rst. (GH-16715)
https://github.com/python/cpython/commit/cbb548130caf24275fa16100bccc537570cb46df


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38442>
_______________________________________

From report at bugs.python.org  Fri Oct 11 04:49:50 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Oct 2019 08:49:50 +0000
Subject: [issue38442] Doc/whatsnew/3.8.rst has an execution bit
In-Reply-To: <1570779517.76.0.861587491217.issue38442@roundup.psfhosted.org>
Message-ID: <1570783790.13.0.823439545004.issue38442@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Strange, it was only in master.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions:  -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38442>
_______________________________________

From report at bugs.python.org  Fri Oct 11 06:39:29 2019
From: report at bugs.python.org (Fabrice BAUZAC)
Date: Fri, 11 Oct 2019 10:39:29 +0000
Subject: [issue12271] panel.h is not found even if it's installed on various
 flavours of SUSE
In-Reply-To: <1307365298.12.0.602165301483.issue12271@psf.upfronthosting.co.za>
Message-ID: <1570790369.86.0.524146964017.issue12271@roundup.psfhosted.org>


Fabrice BAUZAC <libnoon at gmail.com> added the comment:

I have been hit by the same issue today.
Kenneth's patch seems fine.  Why not integrate it?

----------
nosy: +fbauzac

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12271>
_______________________________________

From report at bugs.python.org  Fri Oct 11 06:39:38 2019
From: report at bugs.python.org (Shmuel H.)
Date: Fri, 11 Oct 2019 10:39:38 +0000
Subject: [issue38444] dataclass: always generate default __init__ on
 __default_init__
Message-ID: <1570790378.12.0.986632197987.issue38444@roundup.psfhosted.org>


New submission from Shmuel H. <shmuelhazan0 at gmail.com>:

Currently, `dataclasses.dataclass` will generate `__init__` only where the user has not defined one. 

However, sometimes, with frozen classes or dataclasses with a lot of members, redefinition of this function is not trivial,
especially if the only purpose is to change the default behaviour for only one member:
```python
from dataclasses import dataclass

@dataclass(frozen=True)
class Dataclass:
    #...big list of members
    member20: int
    
    def __init__(self, member20: str, **kwargs):
        # self.member20 = int(member20)
        object.__setattr__(self, "member20", int(member20))
        # Now we have to trivially initialize 
        # 20 other members like that :[
```
My idea is to generate the default `__init__` into `__default_init__` even, if the user has defined their own version.
That will allow them to use it like that:
 ```python
from dataclasses import dataclass

@dataclass(frozen=True)
class Dataclass:
    #...big list of members
    member20: int
    
    def __init__(self, member20: str, **kwargs):
        # Oh, that's better :)
        self.__default_init__(member20=int(member20), **kwargs)
```

Implementing that is pretty trivial (I can do that if this change will be approved). 
Please let me know what you think about that.

----------
components: Library (Lib)
messages: 354437
nosy: Shmuel H.
priority: normal
severity: normal
status: open
title: dataclass: always generate default __init__ on __default_init__
type: enhancement
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38444>
_______________________________________

From report at bugs.python.org  Fri Oct 11 06:41:31 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 11 Oct 2019 10:41:31 +0000
Subject: [issue38444] dataclass: always generate default __init__ on
 __default_init__
In-Reply-To: <1570790378.12.0.986632197987.issue38444@roundup.psfhosted.org>
Message-ID: <1570790491.23.0.871217415729.issue38444@roundup.psfhosted.org>


Change by Eric V. Smith <eric at trueblade.com>:


----------
assignee:  -> eric.smith
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38444>
_______________________________________

From report at bugs.python.org  Fri Oct 11 06:42:07 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 11 Oct 2019 10:42:07 +0000
Subject: [issue38444] dataclass: always generate default __init__ on
 __default_init__
In-Reply-To: <1570790378.12.0.986632197987.issue38444@roundup.psfhosted.org>
Message-ID: <1570790527.35.0.60576384181.issue38444@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

This would be a 3.9 feature only, so changing the versions.

----------
versions:  -Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38444>
_______________________________________

From report at bugs.python.org  Fri Oct 11 07:00:31 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 11:00:31 +0000
Subject: [issue38435] Start the deprecation cycle for subprocess preexec_fn
In-Reply-To: <1570731497.4.0.313201495913.issue38435@roundup.psfhosted.org>
Message-ID: <1570791631.28.0.626647457704.issue38435@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> We cannot provide a general do everything replacement and should not try. It not possible.

Well, I proposed a solution at:
https://bugs.python.org/issue38417#msg354242

I know that this solution has multiple flaws, but a bad solution may be better than no solution: breaking applications when upgrading to Python 3.11.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38435>
_______________________________________

From report at bugs.python.org  Fri Oct 11 07:16:42 2019
From: report at bugs.python.org (Nika)
Date: Fri, 11 Oct 2019 11:16:42 +0000
Subject: [issue38445] os.path.exists() takes bool as argument and returns True
Message-ID: <1570792602.16.0.709405121857.issue38445@roundup.psfhosted.org>


New submission from Nika <nika.boeblingen at mail.ru>:

os.path.exists() accepts either True or False as argument and returns True.
Reproducible on Windows, e. g.,  in jupyter notebook or in Eclipse, although not in IDLE, which returns False, as expected.

import os
print(os.path.exists(False))

----------
messages: 354440
nosy: Nika
priority: normal
severity: normal
status: open
title: os.path.exists() takes bool as argument and returns True
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38445>
_______________________________________

From report at bugs.python.org  Fri Oct 11 07:18:11 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 11 Oct 2019 11:18:11 +0000
Subject: [issue38444] dataclass: always generate default __init__ on
 __default_init__
In-Reply-To: <1570790378.12.0.986632197987.issue38444@roundup.psfhosted.org>
Message-ID: <1570792691.41.0.608285275887.issue38444@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Doesn't __post_init__ address this use case?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38444>
_______________________________________

From report at bugs.python.org  Fri Oct 11 07:29:11 2019
From: report at bugs.python.org (Dan Snider)
Date: Fri, 11 Oct 2019 11:29:11 +0000
Subject: [issue38446] Ambiguous signature for builtins.__build_class__
Message-ID: <1570793351.47.0.198943437011.issue38446@roundup.psfhosted.org>


New submission from Dan Snider <mr.assume.away at gmail.com>:

The function has the following signature documented:

    __build_class__(func, name, *bases, metaclass=None, **kwds) 

This implies that `func` and `name` are not positional only parameters when in fact, they are. Another problem with that signature is that None is not a valid value for the metaclass parameter.

----------
messages: 354442
nosy: bup
priority: normal
severity: normal
status: open
title: Ambiguous signature for builtins.__build_class__

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38446>
_______________________________________

From report at bugs.python.org  Fri Oct 11 07:47:55 2019
From: report at bugs.python.org (Mariano Anaya)
Date: Fri, 11 Oct 2019 11:47:55 +0000
Subject: [issue38445] os.path.exists() takes bool as argument and returns True
In-Reply-To: <1570792602.16.0.709405121857.issue38445@roundup.psfhosted.org>
Message-ID: <1570794475.33.0.0598430740933.issue38445@roundup.psfhosted.org>


Mariano Anaya <marianoanaya at gmail.com> added the comment:

Hi, I would like to take a look at this issue. Could someone please assign it to me? Thanks

----------
nosy: +Mariano Anaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38445>
_______________________________________

From report at bugs.python.org  Fri Oct 11 08:17:27 2019
From: report at bugs.python.org (Eryk Sun)
Date: Fri, 11 Oct 2019 12:17:27 +0000
Subject: [issue38445] os.path.exists() takes bool as argument and returns True
In-Reply-To: <1570792602.16.0.709405121857.issue38445@roundup.psfhosted.org>
Message-ID: <1570796247.75.0.235295203615.issue38445@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

Note that the underlying stat call supports file descriptors, which are non-negative integers. This is a supported and tested capability for genericpath.exists (see GenericTest.test_exists_fd in Lib/test/test_genericpath.py).

False and True are integers with the values 0 and 1: 

    >>> issubclass(bool, int)
    True
    >>> False + 0
    0
    >>> True + 0
    1

That can be useful, but there may be cases where we don't want to conflate bools and integers. IMO, a bool should not be supported as a file descriptor. It's likely a bug that should be caught early instead of meaninglessly propagated. 

A high-level solution would check for bool instances in genericpath.exists. A low-level solution, to make this policy consistent in general, would be to modify _fd_converter in Modules/posixmodule.c to disallow bool instances.

----------
nosy: +eryksun

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38445>
_______________________________________

From report at bugs.python.org  Fri Oct 11 08:42:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 12:42:55 +0000
Subject: [issue32561] Add API to io objects for cache-only reads/writes
In-Reply-To: <1516068442.29.0.467229070634.issue32561@psf.upfronthosting.co.za>
Message-ID: <1570797775.61.0.0230707707315.issue32561@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Here a proof-of-concept of an asynchronous io module reusing the existing blocking io module: it implements AsyncBufferedReader.readline() using existing _pyio.BufferedReader.readline().

The approach seems to work, but only if bpo-13322 is fixed first: BufferedReader, TextIOWrapper & friends must return None if the underlying object ("raw" and "buffer" objects) return None.

--

My PoC uses 3 classes:

* AsyncFileIO: similar to io.FileIO but uses "async def"
* AsyncBufferedReader: similar to io.BufferedReader but uses "async def"
* FileIOSandwich: glue between asynchronous AsyncFileIO and blocking io.BufferedReader

At the first read, FileIOSandwich.read(n) call returns None, but it stores the request read size (n).

If AsyncBufferedReader gets None, is calls FileIOSandwich._prepare_read() *asynchronously*/

Then FileIOSandwich.read(n) is called again, and this time it no longer blocks, since data has been already read.

--

Since bpo-13322 is not fixed, my PoC uses _pyio since it's easier to fix. It needs the following fix for _pyio.BufferedReader.readline():

diff --git a/Lib/_pyio.py b/Lib/_pyio.py
index c1bdac7913..e90742ec43 100644
--- a/Lib/_pyio.py
+++ b/Lib/_pyio.py
@@ -557,6 +557,8 @@ class IOBase(metaclass=abc.ABCMeta):
         res = bytearray()
         while size < 0 or len(res) < size:
             b = self.read(nreadahead())
+            if b is None and not res:
+                return None
             if not b:
                 break
             res += b


---

Example:

$ ./python poc_aio.py poc_aio.py 
data: b'import asyncio\n'

Internally, _prepare_read() reads 8 KiB.

----------
Added file: https://bugs.python.org/file48656/poc_aio.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32561>
_______________________________________

From report at bugs.python.org  Fri Oct 11 08:47:25 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 12:47:25 +0000
Subject: [issue32561] Add API to io objects for cache-only reads/writes
In-Reply-To: <1516068442.29.0.467229070634.issue32561@psf.upfronthosting.co.za>
Message-ID: <1570798045.41.0.313364157711.issue32561@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I suggest to leave not attempt to put "async or "await" in the io module to keep it a "simple" as possible, but fix bpo-13322 (in io and _pyio modules).

Instead, I suggest to write a new module only providing asynchronous methods, maybe even for open() and close(). But the new module can reuse the existing io module to avoid having to write complex algorithm like read-ahead, buffering, etc.

Well, I'm not 100% sure that it's doable, since io is hiding many implementation details, there are complex issues like multithreading, locks, interlaced read and write operations, etc.

Note: The io module doesn't fully suppored interlaced read and write :-) See bpo-12215 for example.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32561>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:01:44 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 13:01:44 +0000
Subject: [issue38447] test_multiprocessing_spawn: Dangling processes:
 {<SpawnProcess(QueueManager-1576, stopped)>} on AMD64 RHEL7 Refleaks 3.7
Message-ID: <1570798904.01.0.669672054648.issue38447@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

AMD64 RHEL7 Refleaks 3.7:
https://buildbot.python.org/all/#/builders/311/builds/22

0:15:09 load avg: 12.21 [311/416/1] test_multiprocessing_spawn failed (env changed) (14 min 39 sec) -- running: test_shelve (5 min 11 sec), test_sqlite (1 min), test_cmd_line_script (1 min 26 sec), test_asyncio (3 min 13 sec), test_io (8 min 6 sec), test_pickle (53.8 sec), test_concurrent_futures (12 min 52 sec)
beginning 6 repetitions
123456
....Warning -- Dangling processes: {<SpawnProcess(QueueManager-1576, stopped)>}
Warning -- Dangling processes: {<SpawnProcess(QueueManager-1576, stopped)>}
.Warning -- Dangling processes: {<SpawnProcess(QueueManager-1788, started)>}
.

----------
components: Tests
messages: 354447
nosy: vstinner
priority: normal
severity: normal
status: open
title: test_multiprocessing_spawn: Dangling processes: {<SpawnProcess(QueueManager-1576, stopped)>} on AMD64 RHEL7 Refleaks 3.7
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38447>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:08:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 13:08:53 +0000
Subject: [issue38448] test_concurrent_futures: reap_children() reaped child
 process 26487 on AMD64 RHEL8 Refleaks 3.x
Message-ID: <1570799333.75.0.17786723855.issue38448@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

AMD64 RHEL8 Refleaks 3.x:
https://buildbot.python.org/all/#/builders/272/builds/23

0:27:13 load avg: 4.88 [416/419/1] test_concurrent_futures failed (env changed) (17 min 11 sec) -- running: test_capi (7 min 28 sec), test_gdb (8 min 49 sec), test_asyncio (23 min 23 sec)
beginning 6 repetitions
123456
.Warning -- reap_children() reaped child process 26487
.....
Warning -- multiprocessing.process._dangling was modified by test_concurrent_futures
  Before: set()
  After:  {<weakref at 0x7fdc08f44e30; to 'SpawnProcess' at 0x7fdc0a467c30>}

----------
components: Tests
messages: 354448
nosy: vstinner
priority: normal
severity: normal
status: open
title: test_concurrent_futures: reap_children() reaped child process 26487 on AMD64 RHEL8 Refleaks 3.x
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38448>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:10:43 2019
From: report at bugs.python.org (Thomas Caswell)
Date: Fri, 11 Oct 2019 13:10:43 +0000
Subject: [issue37980] regression when passing numpy bools to sorted(...,
 reverse=r)
In-Reply-To: <1567096742.32.0.970581980709.issue37980@roundup.psfhosted.org>
Message-ID: <1570799443.02.0.165681177867.issue37980@roundup.psfhosted.org>


Thomas Caswell <tcaswell at gmail.com> added the comment:

Any update on resolving this?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37980>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:36:50 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 11 Oct 2019 13:36:50 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
In-Reply-To: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>
Message-ID: <1570801010.31.0.947819924337.issue38438@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

I?m happy to write one. This seems like a pretty straightforward fix.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:36:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 13:36:55 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1570801015.94.0.896215228412.issue38347@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 2b7dc40b2af6578181808ba73c1533fc114e55df by Victor Stinner (Ruediger Pluem) in branch 'master':
bpo-38347: find pathfix for Python scripts whose name contain a '-' (GH-16536)
https://github.com/python/cpython/commit/2b7dc40b2af6578181808ba73c1533fc114e55df


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:37:51 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 13:37:51 +0000
Subject: [issue37415] Error build Python with Intel compiler: <stdatomic.h>
 doesn't provide atomic_uintptr_t
In-Reply-To: <1561563167.55.0.111630694926.issue37415@roundup.psfhosted.org>
Message-ID: <1570801071.89.0.657531909904.issue37415@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16294
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16717

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37415>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:37:53 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 11 Oct 2019 13:37:53 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1570801073.51.0.930082244698.issue38347@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16295
pull_request: https://github.com/python/cpython/pull/16718

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:38:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 13:38:46 +0000
Subject: [issue37415] Error build Python with Intel compiler: <stdatomic.h>
 doesn't provide atomic_uintptr_t
In-Reply-To: <1561563167.55.0.111630694926.issue37415@roundup.psfhosted.org>
Message-ID: <1570801126.94.0.264515109941.issue37415@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I wrote PR 16717 which uses a similar approach than python.patch.

----------
components: +Build
versions: +Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37415>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:46:35 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 13:46:35 +0000
Subject: [issue37415] Error build Python with Intel compiler: <stdatomic.h>
 doesn't provide atomic_uintptr_t
In-Reply-To: <1561563167.55.0.111630694926.issue37415@roundup.psfhosted.org>
Message-ID: <1570801595.62.0.91956456722.issue37415@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Can someone please test PR 16717 with ICC?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37415>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:49:25 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 13:49:25 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1570801765.2.0.0206896347261.issue38347@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16296
pull_request: https://github.com/python/cpython/pull/16719

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Fri Oct 11 09:56:51 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 11 Oct 2019 13:56:51 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1570802211.95.0.486028444478.issue38347@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 73665b41470532f873315d5ae39906160192320d by Miss Islington (bot) in branch '3.8':
bpo-38347: find pathfix for Python scripts whose name contain a '-' (GH-16536)
https://github.com/python/cpython/commit/73665b41470532f873315d5ae39906160192320d


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Fri Oct 11 10:06:40 2019
From: report at bugs.python.org (Yaroslav Halchenko)
Date: Fri, 11 Oct 2019 14:06:40 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
Message-ID: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>


New submission from Yaroslav Halchenko <yarikoptic at gmail.com>:

Our tests in DataLad started to fail while building on Debian with Python 3.7.5rc1 whenever they passed just fine previously with 3.7.3rc1. Analysis boiled down to mimetypes

    $> ./python3.9 -c 'import mimetypes; mimedb = mimetypes.MimeTypes(strict=False); print(mimedb.guess_type(";1.tar.gz"))'                           
    (None, None)
    
    $> ./python3.9 -c 'import mimetypes; mimedb = mimetypes.MimeTypes(strict=False); print(mimedb.guess_type("1.tar.gz"))' 
    ('application/x-tar', 'gzip')
    
    $> git describe
    v3.8.0b1-1174-g2b7dc40b2af


Ref: 

- original issue in DataLad: https://github.com/datalad/datalad/issues/3769

----------
components: Library (Lib)
messages: 354455
nosy: Yaroslav.Halchenko
priority: normal
severity: normal
status: open
title: regression - mimetypes guess_type is confused by ; in the filename
type: behavior
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Fri Oct 11 10:08:39 2019
From: report at bugs.python.org (Yaroslav Halchenko)
Date: Fri, 11 Oct 2019 14:08:39 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570802919.66.0.323298390635.issue38449@roundup.psfhosted.org>


Yaroslav Halchenko <yarikoptic at gmail.com> added the comment:

FWIW, our more complete test filename is 

# python3 -c 'import patoolib.util as ut; print(ut.guess_mime(r" \"\`;b&b&c |.tar.gz"))'
(None, None)

which works fine with older versions

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Fri Oct 11 10:18:33 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 11 Oct 2019 14:18:33 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
In-Reply-To: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>
Message-ID: <1570803513.75.0.614873941243.issue38438@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Bob, as OP you get first dibs on a PR.
Brandt, you're next in line :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Fri Oct 11 10:19:47 2019
From: report at bugs.python.org (Shmuel H.)
Date: Fri, 11 Oct 2019 14:19:47 +0000
Subject: [issue38444] dataclass: always generate default __init__ on
 __default_init__
In-Reply-To: <1570790378.12.0.986632197987.issue38444@roundup.psfhosted.org>
Message-ID: <1570803587.36.0.689686996788.issue38444@roundup.psfhosted.org>


Shmuel H. <shmuelhazan0 at gmail.com> added the comment:

I think it was designed to. However, it is not very usable in production for a number of reasons:
1. It won't work with frozen instances (you'll have to call `object.__setattr__` directly).
2. It gets very messy with more than one or two `InitVar`s which makes it very hard to differentiate between "real"
 values, `InitVar`s and the init logic:
```python
from dataclasses import dataclass, InitVar
@dataclass
class DataClass:
    member0_init: InitVar[str] = None
    member1_init: InitVar[list] = None

    member0: int = None
    member1: dict = None

    def __post_init__(self, member0_init: str, member1_init: list):
        if member0_init is not None and self.member0 is None:
            self.member0 = int(member0_init)
        if member1_init is not None and self.member1 is None:
            self.member1 = dict(member1_init)
```
That code should be equivalent to:
```python
from dataclasses import dataclass
from typing import Union
@dataclass
class DataClass:
    member0: int
    member1: dict

    def __init__(self, member0: Union[int, str], member1: Union[dict, list]):
        if isinstance(member0, str):
            member0 = int(member0)
        if isinstance(member1, list):
            member1 = dict(member1)

        self.__default_init__(member0=member0, member1=member1)
```
Which is much closer to regular python code to someone new for dataclasses.

I would be happy to hear if you have a better solution; I just think it is pretty simple and straight-forward.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38444>
_______________________________________

From report at bugs.python.org  Fri Oct 11 10:33:34 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 11 Oct 2019 14:33:34 +0000
Subject: [issue38444] dataclass: always generate default __init__ on
 __default_init__
In-Reply-To: <1570790378.12.0.986632197987.issue38444@roundup.psfhosted.org>
Message-ID: <1570804414.29.0.774993136984.issue38444@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

I'll try and think of something better.

I know I'm guilty of sending to python-ideas all the time, but discussing proposed design decisions like this are what that list is all about.

If you want to bring it up there, I'd focus on making the problem description crystal clear, and not so much on any proposed solution. At least for starters.

And, someone will ask what attrs or other projects do to solve this problem, so you should research that.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38444>
_______________________________________

From report at bugs.python.org  Fri Oct 11 10:59:23 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 14:59:23 +0000
Subject: [issue1294959] Problems with /usr/lib64 builds.
Message-ID: <1570805963.62.0.508023666225.issue1294959@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1294959>
_______________________________________

From report at bugs.python.org  Fri Oct 11 11:16:34 2019
From: report at bugs.python.org (Matej Cepl)
Date: Fri, 11 Oct 2019 15:16:34 +0000
Subject: [issue1294959] Problems with /usr/lib64 builds.
Message-ID: <1570806994.37.0.251238036371.issue1294959@roundup.psfhosted.org>


Change by Matej Cepl <mcepl at cepl.eu>:


----------
nosy: +mcepl

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1294959>
_______________________________________

From report at bugs.python.org  Fri Oct 11 11:16:47 2019
From: report at bugs.python.org (Matej Cepl)
Date: Fri, 11 Oct 2019 15:16:47 +0000
Subject: [issue1294959] Problems with /usr/lib64 builds.
Message-ID: <1570807007.81.0.223183650349.issue1294959@roundup.psfhosted.org>


Change by Matej Cepl <mcepl at cepl.eu>:


----------
versions: +Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1294959>
_______________________________________

From report at bugs.python.org  Fri Oct 11 11:36:12 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 15:36:12 +0000
Subject: [issue37788] fix for bpo-36402 (threading._shutdown() race condition)
 causes reference leak
In-Reply-To: <1565194972.64.0.065323919799.issue37788@roundup.psfhosted.org>
Message-ID: <1570808172.7.0.486906625874.issue37788@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Copy of wmanley's comment:
https://github.com/python/cpython/pull/13948#issuecomment-541076882
"""
This caused a regression for people overriding Thread.join to implement custom thread interruption. See https://stackoverflow.com/questions/50486083/ending-non-daemon-threads-when-shutting-down-an-interactive-python-session
"""

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37788>
_______________________________________

From report at bugs.python.org  Fri Oct 11 11:37:09 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 15:37:09 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1570808229.04.0.202400455495.issue38347@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset ed189ce49423f15ba8774ff174c15d03d12bc807 by Victor Stinner in branch '3.7':
bpo-38347: find pathfix for Python scripts whose name contain a '-' (GH-16536) (GH-16719)
https://github.com/python/cpython/commit/ed189ce49423f15ba8774ff174c15d03d12bc807


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Fri Oct 11 11:37:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 15:37:39 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1570808259.88.0.975853231129.issue38347@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Thanks Ruediger Pluem: I merged your change into master and backported to 3.8 and 3.7. For the 3.7 backport, I skipped tests.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Fri Oct 11 11:42:52 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Fri, 11 Oct 2019 15:42:52 +0000
Subject: [issue37788] fix for bpo-36402 (threading._shutdown() race condition)
 causes reference leak
In-Reply-To: <1565194972.64.0.065323919799.issue37788@roundup.psfhosted.org>
Message-ID: <1570808572.81.0.122611445241.issue37788@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Hummm....is this really a regression? The docs say:

> No other methods (except for the constructor) should be overridden in a subclass. In other words, only override the __init__() and run() methods of this class.

So if someone is overriding join() they are out of contract

----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37788>
_______________________________________

From report at bugs.python.org  Fri Oct 11 12:02:58 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Fri, 11 Oct 2019 16:02:58 +0000
Subject: [issue38450] 3.8 Release Notes: IDLE section dupe
Message-ID: <1570809778.37.0.687630988781.issue38450@roundup.psfhosted.org>


New submission from Sebastian Rittau <srittau at rittau.biz>:

In the 3.8 release notes (https://docs.python.org/3.8/whatsnew/3.8.html), the section "IDLE and idlelib" is duplicated as "idlelib and IDLE". Also, the section "gc" and "gzip" between them are not sorted alphabetically like the rest of the list.

----------
assignee: docs at python
components: Documentation
messages: 354464
nosy: docs at python, srittau
priority: normal
severity: normal
status: open
title: 3.8 Release Notes: IDLE section dupe
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38450>
_______________________________________

From report at bugs.python.org  Fri Oct 11 12:13:34 2019
From: report at bugs.python.org (Kyle Meyer)
Date: Fri, 11 Oct 2019 16:13:34 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570810414.35.0.166038851141.issue38449@roundup.psfhosted.org>


Kyle Meyer <kyle at kyleam.com> added the comment:

I've performed a bisect the issue with the following script:

    #!/bin/sh
    make -j3 || exit 125
    ./python <<\EOF || exit 1
    import sys
    import mimetypes
    res = mimetypes.MimeTypes(strict=False).guess_type(";1.tar.gz")
    if res[0] is None:
        sys.exit(1)
    EOF

That points to 87bd2071c7 (bpo-22347: Update mimetypes.guess_type to allow proper parsing of URLs (GH-15522), 2019-09-05).  That commit was included in 3.7.5rc1 when it was cherry picked by 8873bff287.

----------
nosy: +kyleam

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Fri Oct 11 12:53:36 2019
From: report at bugs.python.org (Arne Recknagel)
Date: Fri, 11 Oct 2019 16:53:36 +0000
Subject: [issue34632] Port importlib_metadata to Python 3.8
In-Reply-To: <1536689803.48.0.0269046726804.issue34632@psf.upfronthosting.co.za>
Message-ID: <1570812816.84.0.229449330975.issue34632@roundup.psfhosted.org>


Arne Recknagel <arne.recknagel at hotmail.com> added the comment:

Is there a reason the object returned by importlib.metadata.metadata is an EmailMessage and not a dict? If it quacks like a duck it should be a duck, no?

----------
nosy: +arne

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34632>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:02:29 2019
From: report at bugs.python.org (Nick Timkovich)
Date: Fri, 11 Oct 2019 17:02:29 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
In-Reply-To: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>
Message-ID: <1570813349.04.0.652926390757.issue38438@roundup.psfhosted.org>


Nick Timkovich <prometheus235 at gmail.com> added the comment:

The `[arg [arg ...]]` feels a bit more formal to me, and I might prefer it in the example shown where the arg name is fairly short. That said, `man mv` shows something like:

    mv [OPTION]... [-T] SOURCE DEST
    mv [OPTION]... SOURCE... DIRECTORY
    mv [OPTION]... -t DIRECTORY SOURCE...

----------
nosy: +nicktimko

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:03:13 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 11 Oct 2019 17:03:13 +0000
Subject: [issue32498] urllib.parse.unquote raises incorrect errormessage when
 string parameter is bytes
In-Reply-To: <1515179710.49.0.467229070634.issue32498@psf.upfronthosting.co.za>
Message-ID: <1570813393.64.0.303847169556.issue32498@roundup.psfhosted.org>


Joannah Nanjekye <nanjekyejoannah at gmail.com> added the comment:

> Should I update the Status and Resolution of the issue here, or wait for some kind of confirmation?

The status is changed after the patch is merged. The person that merges will usually change the status of the issue or If he/she forgets, anyone with developer role can update the status too.

----------
nosy: +nanjekyejoannah

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32498>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:07:27 2019
From: report at bugs.python.org (Arne Recknagel)
Date: Fri, 11 Oct 2019 17:07:27 +0000
Subject: [issue34632] Port importlib_metadata to Python 3.8
In-Reply-To: <1536689803.48.0.0269046726804.issue34632@psf.upfronthosting.co.za>
Message-ID: <1570813647.26.0.14140085788.issue34632@roundup.psfhosted.org>


Arne Recknagel <arne.recknagel at hotmail.com> added the comment:

I just learned that metadata is stored as an email, and changing the format was rejected in PEP 426. Be that as it may, if it isn't too much of an issue it might still be something that should be hidden from users of the module. Noone wants to know that this particular duck is actually powered by fins under the surface, right?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34632>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:17:31 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 17:17:31 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570814251.15.0.834231648282.issue38449@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Marking as regression release blocker for 3.7.5 final and 3.8.0 final.

----------
keywords: +3.7regression
nosy: +lukasz.langa, martin.panter, ned.deily, vstinner
priority: normal -> release blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:18:38 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 17:18:38 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1570814318.03.0.695663535837.issue22347@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

This change introduces a potential 3.7 regression; see Issue38449.

----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:19:23 2019
From: report at bugs.python.org (Shmuel H.)
Date: Fri, 11 Oct 2019 17:19:23 +0000
Subject: [issue38444] dataclass: always generate default __init__ on
 __default_init__
In-Reply-To: <1570790378.12.0.986632197987.issue38444@roundup.psfhosted.org>
Message-ID: <1570814363.12.0.347176845463.issue38444@roundup.psfhosted.org>


Shmuel H. <shmuelhazan0 at gmail.com> added the comment:

The only other solution I could think about was to change setattr's behaviour dynamically so that it would be valid to call it from frozen instance's `__init__`, but I think it is somehow even worst.

However, thanks for your help, I think we can close this one for now and I'll hopefully write that mail in the next day or two.                

As for other projects, I doubt I'll find any big projects that use frozen dataclasses internally, but I'll try my best to come with one.

(Only now I realize that your the one behind python's dataclasses, keep up the good work!).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38444>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:24:08 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 11 Oct 2019 17:24:08 +0000
Subject: [issue35826] Typo in example for async with statement with condition
In-Reply-To: <1548413052.91.0.387178410518.issue35826@roundup.psfhosted.org>
Message-ID: <1570814648.09.0.869784050043.issue35826@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16297
pull_request: https://github.com/python/cpython/pull/16720

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35826>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:25:26 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Fri, 11 Oct 2019 17:25:26 +0000
Subject: [issue38436] Improved performance for list addition.
In-Reply-To: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>
Message-ID: <1570814726.35.0.890454189582.issue38436@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I have repeated the benchmark in the speed.python.org server with CPU isolation + PGO + LTO:

Slower (21):
- xml_etree_iterparse: 127 ms +- 2 ms -> 131 ms +- 2 ms: 1.03x slower (+3%)
- xml_etree_parse: 195 ms +- 1 ms -> 200 ms +- 2 ms: 1.03x slower (+3%)
- pickle_list: 5.62 us +- 0.05 us -> 5.76 us +- 0.06 us: 1.03x slower (+3%)
- pickle: 13.2 us +- 0.1 us -> 13.5 us +- 0.1 us: 1.02x slower (+2%)
- scimark_lu: 185 ms +- 3 ms -> 188 ms +- 5 ms: 1.02x slower (+2%)
- scimark_fft: 427 ms +- 2 ms -> 434 ms +- 2 ms: 1.02x slower (+2%)
- sympy_integrate: 25.0 ms +- 0.2 ms -> 25.3 ms +- 0.2 ms: 1.01x slower (+1%)
- spectral_norm: 166 ms +- 3 ms -> 169 ms +- 1 ms: 1.01x slower (+1%)
- scimark_sor: 246 ms +- 6 ms -> 249 ms +- 4 ms: 1.01x slower (+1%)
- sympy_sum: 203 ms +- 2 ms -> 205 ms +- 2 ms: 1.01x slower (+1%)
- chaos: 138 ms +- 1 ms -> 139 ms +- 1 ms: 1.01x slower (+1%)
- json_loads: 37.2 us +- 1.0 us -> 37.5 us +- 0.3 us: 1.01x slower (+1%)
- xml_etree_process: 91.0 ms +- 1.1 ms -> 91.7 ms +- 1.8 ms: 1.01x slower (+1%)
- sympy_str: 315 ms +- 2 ms -> 317 ms +- 2 ms: 1.01x slower (+1%)
- sqlalchemy_declarative: 210 ms +- 3 ms -> 211 ms +- 3 ms: 1.01x slower (+1%)
- regex_compile: 214 ms +- 1 ms -> 215 ms +- 1 ms: 1.01x slower (+1%)
- regex_dna: 268 ms +- 1 ms -> 270 ms +- 1 ms: 1.01x slower (+1%)
- logging_format: 11.2 us +- 0.1 us -> 11.3 us +- 0.2 us: 1.01x slower (+1%)
- unpickle_pure_python: 392 us +- 4 us -> 394 us +- 4 us: 1.00x slower (+0%)
- sympy_expand: 492 ms +- 2 ms -> 493 ms +- 3 ms: 1.00x slower (+0%)
- pidigits: 236 ms +- 1 ms -> 236 ms +- 1 ms: 1.00x slower (+0%)

Faster (21):
- unpack_sequence: 73.9 ns +- 1.3 ns -> 69.3 ns +- 1.0 ns: 1.07x faster (-6%)
- 2to3: 405 ms +- 2 ms -> 393 ms +- 2 ms: 1.03x faster (-3%)
- float: 146 ms +- 1 ms -> 142 ms +- 2 ms: 1.03x faster (-3%)
- scimark_sparse_mat_mult: 5.46 ms +- 0.02 ms -> 5.34 ms +- 0.06 ms: 1.02x faster (-2%)
- unpickle: 17.1 us +- 0.1 us -> 16.7 us +- 0.2 us: 1.02x faster (-2%)
- regex_effbot: 3.89 ms +- 0.11 ms -> 3.82 ms +- 0.03 ms: 1.02x faster (-2%)
- json_dumps: 15.9 ms +- 0.1 ms -> 15.7 ms +- 0.1 ms: 1.01x faster (-1%)
- python_startup: 12.4 ms +- 0.1 ms -> 12.3 ms +- 0.0 ms: 1.01x faster (-1%)
- go: 320 ms +- 4 ms -> 316 ms +- 3 ms: 1.01x faster (-1%)
- pathlib: 25.4 ms +- 0.4 ms -> 25.1 ms +- 0.3 ms: 1.01x faster (-1%)
- mako: 19.6 ms +- 0.2 ms -> 19.4 ms +- 0.1 ms: 1.01x faster (-1%)
- fannkuch: 598 ms +- 7 ms -> 591 ms +- 4 ms: 1.01x faster (-1%)
- hexiom: 12.2 ms +- 0.2 ms -> 12.1 ms +- 0.1 ms: 1.01x faster (-1%)
- richards: 85.9 ms +- 1.3 ms -> 85.0 ms +- 1.3 ms: 1.01x faster (-1%)
- python_startup_no_site: 9.18 ms +- 0.05 ms -> 9.09 ms +- 0.02 ms: 1.01x faster (-1%)
- genshi_xml: 74.8 ms +- 0.6 ms -> 74.2 ms +- 0.9 ms: 1.01x faster (-1%)
- nbody: 157 ms +- 2 ms -> 155 ms +- 2 ms: 1.01x faster (-1%)
- unpickle_list: 5.89 us +- 0.03 us -> 5.85 us +- 0.04 us: 1.01x faster (-1%)
- genshi_text: 36.7 ms +- 0.4 ms -> 36.5 ms +- 0.3 ms: 1.01x faster (-1%)
- dulwich_log: 80.5 ms +- 0.5 ms -> 80.0 ms +- 0.5 ms: 1.01x faster (-1%)
- regex_v8: 28.9 ms +- 0.1 ms -> 28.9 ms +- 0.1 ms: 1.00x faster (-0%)

Benchmark hidden because not significant (15): chameleon, crypto_pyaes, deltablue, logging_silent, logging_simple, meteor_contest, nqueens, pickle_dict, pickle_pure_python, raytrace, scimark_monte_carlo, sqlalchemy_imperative, sqlite_synth, telco, xml_etree_generate
Ignored benchmarks (3) of json/2019-09-16_14-25-master-89b8933bb537.json.gz: django_template, html5lib, tornado_http

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:26:13 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 11 Oct 2019 17:26:13 +0000
Subject: [issue38444] dataclass: always generate default __init__ on
 __default_init__
In-Reply-To: <1570790378.12.0.986632197987.issue38444@roundup.psfhosted.org>
Message-ID: <1570814773.08.0.405919090572.issue38444@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Thanks. I'm always looking for ways to make dataclasses easier to use, while keeping within the original goals. I'll close this for now.

----------
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38444>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:30:37 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 11 Oct 2019 17:30:37 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
In-Reply-To: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>
Message-ID: <1570815037.94.0.638571991361.issue38438@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

For backward compatibility with 2 metavars, the two-name form should still be possible. Just pass metavar=("FOO", "FOO").

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:31:45 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 11 Oct 2019 17:31:45 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
In-Reply-To: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>
Message-ID: <1570815105.06.0.37668452057.issue38438@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

I don't think it's any more precise. It just seems verbose and confusing to me, while conveying the same information.

`[arg [arg ...]]` to me means "optionally, an arg followed by one or more optional args".

While `[arg ...]` to  me means "optionally, one or more args".

So, I'd vote for the simpler version, especially since we're presumably trying to communicate with people who aren't BNF or regex experts!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:46:13 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 11 Oct 2019 17:46:13 +0000
Subject: [issue38445] os.path.exists() takes bool as argument and returns True
In-Reply-To: <1570792602.16.0.709405121857.issue38445@roundup.psfhosted.org>
Message-ID: <1570815973.46.0.987380530534.issue38445@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38445>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:50:10 2019
From: report at bugs.python.org (Pouria)
Date: Fri, 11 Oct 2019 17:50:10 +0000
Subject: [issue38451] Datetime definition does not work in function definition
 as list definition
Message-ID: <1570816210.41.0.305155920593.issue38451@roundup.psfhosted.org>


Change by Pouria <Pouriaff7171 at gmail.com>:


----------
components: Library (Lib)
nosy: Pouria_ff
priority: normal
severity: normal
status: open
title: Datetime definition does not work in function definition as list definition
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38451>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:57:16 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Oct 2019 17:57:16 +0000
Subject: [issue38432] ZeroDivisionError when inf is expected
In-Reply-To: <1570723301.17.0.789552752187.issue38432@roundup.psfhosted.org>
Message-ID: <1570816636.77.0.214519212711.issue38432@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

See https://en.wikipedia.org/wiki/Denormal_number.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38432>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:00:15 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 11 Oct 2019 18:00:15 +0000
Subject: [issue38451] Datetime definition does not work in function definition
 as list definition
Message-ID: <1570816815.04.0.693882405229.issue38451@roundup.psfhosted.org>


New submission from Karthikeyan Singaravelan <tir.karthi at gmail.com>:

Can you please add an example of the issue and the actual/expected behavior?

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38451>
_______________________________________

From report at bugs.python.org  Fri Oct 11 13:50:10 2019
From: report at bugs.python.org (Pouria)
Date: Fri, 11 Oct 2019 17:50:10 +0000
Subject: [issue38451] Datetime definition does not work in function definition
 as list definition
Message-ID: <1570816210.41.0.305155920593.issue38451@roundup.psfhosted.org>


Change by Pouria <Pouriaff7171 at gmail.com>:


----------
components: Library (Lib)
nosy: Pouria_ff
priority: normal
severity: normal
status: open
title: Datetime definition does not work in function definition as list definition
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38451>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:20:35 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 11 Oct 2019 18:20:35 +0000
Subject: [issue38436] Improved performance for list addition.
In-Reply-To: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>
Message-ID: <1570818035.53.0.99455845507.issue38436@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

Thanks, Pablo, for providing that. So the changes look like mostly a wash on these benchmarks. 

Serhiy:

I do not see any significant change in + operator timing on my machine (again, just a rough test):

$ ./python.exe -m timeit -s z=0 z+0  # master
10000000 loops, best of 5: 21.3 nsec per loop

$ ./python.exe -m timeit -s z=0 z+0  # list-add
10000000 loops, best of 5: 21.2 nsec per loop

I'm aware that unpacking is "better". With that said, adding a list literal (or a slice of any list, or a list comprehension) to another list is a fairly common operation (I count several dozen examples in the stdlib). Even though these cases only have two operands, they will still see the speed-up.

And the speed-up is good, even in these cases. You can compare using the new code:

$ ./python.exe -m timeit -s l=[0,1,2,3] [0,1,2,3]+l  # Hits new branch
5000000 loops, best of 5: 87.9 nsec per loop

$ ./python.exe -m timeit -s l=[0,1,2,3] l+[0,1,2,3]  # Hits old branch
5000000 loops, best of 5: 92.5 nsec per loop

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:23:50 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 11 Oct 2019 18:23:50 +0000
Subject: [issue38424] typing.Generator shorthand
In-Reply-To: <1570671541.73.0.307162838122.issue38424@roundup.psfhosted.org>
Message-ID: <1570818230.42.0.922592428604.issue38424@roundup.psfhosted.org>


Change by Ivan Levkivskyi <levkivskyi at gmail.com>:


----------
nosy: +levkivskyi

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38424>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:24:00 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 11 Oct 2019 18:24:00 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570818240.29.0.733820824907.issue38431@roundup.psfhosted.org>


Change by Ivan Levkivskyi <levkivskyi at gmail.com>:


----------
nosy: +levkivskyi

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:25:13 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 11 Oct 2019 18:25:13 +0000
Subject: [issue38446] Ambiguous signature for builtins.__build_class__
In-Reply-To: <1570793351.47.0.198943437011.issue38446@roundup.psfhosted.org>
Message-ID: <1570818313.37.0.650138750456.issue38446@roundup.psfhosted.org>


Change by Ivan Levkivskyi <levkivskyi at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38446>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:26:12 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 11 Oct 2019 18:26:12 +0000
Subject: [issue38436] Improved performance for list addition.
In-Reply-To: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>
Message-ID: <1570818372.75.0.651389909478.issue38436@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

...and obviously the gains are more pronounced for more/longer lists.

In general I'm not married to this change, though. If the consensus is "not worth it", I get it.

But it seems like too easy of a win to me.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:26:14 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Oct 2019 18:26:14 +0000
Subject: [issue38445] os.path.exists() takes bool as argument and returns True
In-Reply-To: <1570792602.16.0.709405121857.issue38445@roundup.psfhosted.org>
Message-ID: <1570818374.69.0.410773713453.issue38445@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Eryk, I think testing for bool in _fd_converter and issuing a warning is a good idea. Do you want to create a PR?

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38445>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:26:18 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 11 Oct 2019 18:26:18 +0000
Subject: [issue38424] typing.Generator shorthand
In-Reply-To: <1570671541.73.0.307162838122.issue38424@roundup.psfhosted.org>
Message-ID: <1570818378.23.0.431241275361.issue38424@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

If you would like to propose a doc fix, then please go ahead and make a PR.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38424>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:26:28 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 11 Oct 2019 18:26:28 +0000
Subject: [issue38424] typing.Generator shorthand
In-Reply-To: <1570671541.73.0.307162838122.issue38424@roundup.psfhosted.org>
Message-ID: <1570818388.47.0.245768756245.issue38424@roundup.psfhosted.org>


Change by Ivan Levkivskyi <levkivskyi at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38424>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:29:49 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Oct 2019 18:29:49 +0000
Subject: [issue38424] typing.Generator shorthand
In-Reply-To: <1570671541.73.0.307162838122.issue38424@roundup.psfhosted.org>
Message-ID: <1570818589.76.0.696835463626.issue38424@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

It is already documented, with examples. I do not think the documentation can be made better.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38424>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:34:45 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 11 Oct 2019 18:34:45 +0000
Subject: [issue38424] typing.Generator shorthand
In-Reply-To: <1570671541.73.0.307162838122.issue38424@roundup.psfhosted.org>
Message-ID: <1570818885.33.0.0819596516023.issue38424@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

Actually Serhiy is right, I just checked and found this sentence:
```
Alternatively, annotate your generator as having a return type of either Iterable[YieldType] or Iterator[YieldType]
```

----------
resolution:  -> works for me
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38424>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:37:08 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 11 Oct 2019 18:37:08 +0000
Subject: [issue36229] Avoid unnecessary copies for list, set,
 and bytearray ops.
In-Reply-To: <1551994791.27.0.137413280424.issue36229@roundup.psfhosted.org>
Message-ID: <1570819028.34.0.0623587989712.issue36229@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
pull_requests: +16298
pull_request: https://github.com/python/cpython/pull/16705

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36229>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:43:44 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Oct 2019 18:43:44 +0000
Subject: [issue38436] Improved performance for list addition.
In-Reply-To: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>
Message-ID: <1570819424.93.0.770331724126.issue38436@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

> I do not see any significant change in + operator timing on my machine (again, just a rough test):

Because the time includes the time of iterating, which can be significant in comparison with adding two integers. Please use the pyperf module with --duplicate=1000.

> I'm aware that unpacking is "better". With that said, adding a list literal (or a slice of any list, or a list comprehension) to another list is a fairly common operation (I count several dozen examples in the stdlib).

Could you provide any numbers? For example you can patch ceval.c to count these BINARY_ADD for which your optimization works and these for which it does not work and output counts at the exit of Python. Run several Python programs with the modified interpreter. Tests are bad example, but better than nothing. Something like hg would be better. You are free to find programs that would benefit the most from your optimization.

> And the speed-up is good, even in these cases.

5%. It is not impressive for optimizing a single rare operation.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:46:05 2019
From: report at bugs.python.org (Armin Rigo)
Date: Fri, 11 Oct 2019 18:46:05 +0000
Subject: [issue36229] Avoid unnecessary copies for list, set,
 and bytearray ops.
In-Reply-To: <1551994791.27.0.137413280424.issue36229@roundup.psfhosted.org>
Message-ID: <1570819565.17.0.415670681804.issue36229@roundup.psfhosted.org>


Change by Armin Rigo <arigo at users.sourceforge.net>:


----------
nosy:  -arigo

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36229>
_______________________________________

From report at bugs.python.org  Fri Oct 11 14:59:01 2019
From: report at bugs.python.org (=?utf-8?b?UsO8ZGlnZXIgUGzDvG0=?=)
Date: Fri, 11 Oct 2019 18:59:01 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1570820341.47.0.362012464779.issue38347@roundup.psfhosted.org>


R?diger Pl?m <r.pluem at gmx.de> added the comment:

Welcome Victor Stinner. Any chance to get it also backported to 3.6 as I guess this would increase the chance to see it in RedHat 8 where I hit the issue?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Fri Oct 11 15:24:51 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 11 Oct 2019 19:24:51 +0000
Subject: [issue38436] Improved performance for list addition.
In-Reply-To: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>
Message-ID: <1570821891.78.0.986011233513.issue38436@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

Serhiy, here are the better performance measurements:


$ ./python.exe -m pyperf timeit --duplicate=1000 -s z=0 z+0  # list-add
.....................
Mean +- std dev: 17.3 ns +- 0.3 ns

$ ./python.exe -m pyperf timeit --duplicate=1000 -s z=0 z+0  # master
.....................
Mean +- std dev: 17.2 ns +- 0.3 ns

$ ./python.exe -m pyperf timeit --duplicate=1000 -s l=[0,1,2,3] [0,1,2,3]+l  # New branch
.....................
Mean +- std dev: 92.6 ns +- 1.7 ns

$ ./python.exe -m pyperf timeit --duplicate=1000 -s l=[0,1,2,3] l+[0,1,2,3]  # Old branch
.....................
Mean +- std dev: 99.8 ns +- 1.4 ns


Honestly, I'll defer to you here. If you feel like pursuing this is a total waste of time, I'll just close the issue/PR. Otherwise I can explore how often the branch is hit in production code, as you suggested.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Fri Oct 11 16:11:09 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Fri, 11 Oct 2019 20:11:09 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570824669.53.0.427945750391.issue38449@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

I am looking into the issue.

----------
nosy: +maxking

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Fri Oct 11 16:13:43 2019
From: report at bugs.python.org (Caris Moses)
Date: Fri, 11 Oct 2019 20:13:43 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1570824823.97.0.629660389969.issue21478@roundup.psfhosted.org>


Caris Moses <caris.moses at gmail.com> added the comment:

Hello,
I am still running into this issue. I have tested the following code with Python 3.7.4, 3.7.5rc1 , and 3.8.0rc1.

from unittest import TestCase
from unittest.mock import patch, Mock, call

class MyObject:
    def __init__(self):
        self.foo = 0
        self.bar = 0

    def set_foo(self, value):
        self.foo = value

    def set_bar(self, value):
        self.bar = value

def do_something():
    o = MyObject()
    o.set_foo(3)
    o.set_bar(4)
    return 'something unrelated'

class MyObjectTest(TestCase):

    @patch('test_mock.MyObject.set_bar', autospec=True)
    @patch('test_mock.MyObject.set_foo', autospec=True)
    def test_do_something(self, mock_set_foo, mock_set_bar):
        manager = Mock()
        manager.attach_mock(mock_set_foo, 'set_foo_func')
        manager.attach_mock(mock_set_bar, 'set_bar_func')
        do_something()
        assert manager.mock_calls == [call.set_foo_func(3), call.set_bar_func(4)]

----------
nosy: +Caris Moses

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Fri Oct 11 16:29:08 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 11 Oct 2019 20:29:08 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1570825748.77.0.522059723725.issue38395@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 193366e25c4f84a58d2f6c6c577fd9f0143dc6e1 by Miss Islington (bot) (Pablo Galindo) in branch '3.7':
[3.7] bpo-38395: Fix ownership in weakref.proxy methods (GH-16632) (GH-16663)
https://github.com/python/cpython/commit/193366e25c4f84a58d2f6c6c577fd9f0143dc6e1


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Fri Oct 11 16:35:09 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 11 Oct 2019 20:35:09 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1570826109.12.0.536355023799.issue21478@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Oh well :( My initial guess is that the report is for methods. The other reports were for functions. So I am wondering if the check for FunctionType is successful and if I need to handle something more. I haven't tried it yet.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Fri Oct 11 16:42:25 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 11 Oct 2019 20:42:25 +0000
Subject: [issue38341] Add SMTPNotSupportedError in the exports of smtplib
In-Reply-To: <1569963046.98.0.477841717728.issue38341@roundup.psfhosted.org>
Message-ID: <1570826545.42.0.0884915278397.issue38341@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16299
pull_request: https://github.com/python/cpython/pull/16721

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38341>
_______________________________________

From report at bugs.python.org  Fri Oct 11 16:49:18 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 11 Oct 2019 20:49:18 +0000
Subject: [issue38436] Improved performance for list addition.
In-Reply-To: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>
Message-ID: <1570826958.05.0.996283006757.issue38436@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

I went ahead and ran an instrumented build on some random production code (mostly financial data processing), just because I was curious:

BINARY_ADD ops: 3,720,776
BINARY_ADD ops with two lists: 100,452 (2.7% of total)
BINARY_ADD with new fast path: 26,357 (26.2% of list adds, 0.7% of total)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Fri Oct 11 16:51:16 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 20:51:16 +0000
Subject: [issue38450] 3.8 Release Notes: IDLE section dupe
In-Reply-To: <1570809778.37.0.687630988781.issue38450@roundup.psfhosted.org>
Message-ID: <1570827076.13.0.704929265382.issue38450@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Thanks for the report!  Those whatsnew issues are being addressed in PR 16621.

----------
nosy: +ned.deily
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38450>
_______________________________________

From report at bugs.python.org  Fri Oct 11 16:56:34 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 20:56:34 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1570827394.5.0.607338696402.issue38347@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Welcome Victor Stinner. Any chance to get it also backported to 3.6 as I guess this would increase the chance to see it in RedHat 8 where I hit the issue?

Python 3.6 doesn't accept bugfixes upstream.

If you are a Red Hat customer, you can contact the support to request a backport. Or you can copy the file from the master branch :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Fri Oct 11 16:58:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 20:58:46 +0000
Subject: [issue38445] os.path.exists() takes bool as argument and returns True
In-Reply-To: <1570792602.16.0.709405121857.issue38445@roundup.psfhosted.org>
Message-ID: <1570827526.63.0.0245680273186.issue38445@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Maybe os.fspath() can be used:

>>> os.fspath(True)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: expected str, bytes or os.PathLike object, not bool

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38445>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:09:27 2019
From: report at bugs.python.org (Caris Moses)
Date: Fri, 11 Oct 2019 21:09:27 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1570828167.49.0.553181497043.issue21478@roundup.psfhosted.org>


Caris Moses <caris.moses at gmail.com> added the comment:

I tried it with mocked functions instead of methods and got the same result, so I dug into this a little deeper. It seems as though the issue it how the mocked functions are called. If I replace the do_something() line with the following then it works.

#do_something()
manager.set_foo_func(3)
manager.set_bar_func(4)

I am a beginner with unittest so please let me know if I am just using this incorrectly. However in the original code I posted, if I print(manager.set_foo_func.mock_calls, manager.set_bar_func.mock_calls) I get the calls made in do_something(), however print(manager.mock_calls) returns an empty list which leads me to believe something else is wrong.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:10:23 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 21:10:23 +0000
Subject: [issue38270] Tests: Avoid MD5 or check for MD5 availablity
In-Reply-To: <1569406198.76.0.145895264341.issue38270@roundup.psfhosted.org>
Message-ID: <1570828223.52.0.709136411732.issue38270@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

It looks like Christian originally requested autobackports to both 3.8 and 3.7 but both failed due to git checkout errors.  He then manually restarted the 3.8 backport but it looks like the 3.7 one did not get restarted.  Christian, was that intentional or just an oversight?  If the latter, you should try the 3.7 backport again.

----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38270>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:22:31 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 21:22:31 +0000
Subject: [issue28188] os.putenv should support bytes arguments on Windows
In-Reply-To: <1474123387.93.0.730915025745.issue28188@psf.upfronthosting.co.za>
Message-ID: <1570828951.53.0.783840045939.issue28188@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

In the meanwhile, the PEP 540 "UTF-8 Mode" has been implemented.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28188>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:22:50 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 21:22:50 +0000
Subject: [issue28188] os.putenv should support bytes arguments on Windows
In-Reply-To: <1474123387.93.0.730915025745.issue28188@psf.upfronthosting.co.za>
Message-ID: <1570828970.52.0.516411287432.issue28188@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

This issue was referenced from https://bugs.python.org/issue29240#msg285482

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28188>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:26:30 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Fri, 11 Oct 2019 21:26:30 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570829190.29.0.583026963073.issue38449@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

The bug is interesting due to some of the implementation details of "guess_type". The documentation says that it can parse either a URL or a filename.

Switching from urllib.parse._splittype to urllib.parse.urlparse changed what a valid "path" is. _splittype doesn't care about the rest of the URL except the scheme, but urlparse does. Previously, we used to split things like:

   >>> print(urllib.parse._splittype(';1.tar.gz')
   (None, ';1.tar.gz')

Then, we'd just treat the 2nd part as a filesystem path, which would rightfully guess the extension as .tar.gz

However, switching to using parsing via urllib.parse.urlparse, we get:

    >>> print(urllib.parse.urlparse(';1.tar.gz')
    ParseResult(scheme='', netloc='', path='', params='1.tar.gz', query='', fragment='')

And then we get the ".path" attribute for further processing, which being empty, returns (None, None).

The format of all these parts is:

    scheme://netloc/path;parameters?query#fragment

A simple fix would be to just merge path, parameters, query and fragment together (with appropriate delimiters) and the proceed with further processing. That would fix parsing of Filesystem paths but would break (again) parsing of URLs like:

    >>> mimetypes.guess_type('http://example.com/index.html;1.tar.gz')
    ('application/x-tar', 'gzip')

It should return 'text/html' as the type, since this is a URL and everything after the ';' should not be used to determine the mimetype. But, if there is no scheme provided, we should treat it as a filesystem path and in that case 'application/x-tar' is the right type.

I hope I am not confusing everyone here. 

The right fix IMO would be to make "guess_type" not treat URLs and filesytem paths alike.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:28:59 2019
From: report at bugs.python.org (Danylo)
Date: Fri, 11 Oct 2019 21:28:59 +0000
Subject: [issue38452] unittest setUpClass missing 1 required positional
 argument: 'cls'
Message-ID: <1570829339.09.0.69466145285.issue38452@roundup.psfhosted.org>


New submission from Danylo <dizcza at gmail.com>:

Currently, unittest setUpClass and tearDownClass methods are incorrectly called from within its core.

```
class TestUltrasonicEnv(unittest.TestCase):

    def setUpClass(cls):
        pass
    

    def tearDownClass(cls):
        pass
```

Traceback (the same for teadDownClass)
```
  File "/home/dizcza/anaconda3/envs/robotsim/lib/python3.7/unittest/suite.py", line 163, in _handleClassSetUp
    setUpClass()
TypeError: setUpClass() missing 1 required positional argument: 'cls'
```

The traceback is self-descriptive.

----------
components: Tests
messages: 354501
nosy: dizcza
priority: normal
severity: normal
status: open
title: unittest setUpClass missing 1 required positional argument: 'cls'
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38452>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:32:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 21:32:55 +0000
Subject: [issue32238] Handle "POSIX" in the legacy locale detection
In-Reply-To: <1512606515.62.0.213398074469.issue32238@psf.upfronthosting.co.za>
Message-ID: <1570829575.93.0.410995116988.issue32238@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

In Python 3.8, if the LC_CTYPE is "POSIX", the default stdio error handler is now "surrogateescape" instead of "strict", and the UTF-8 is now enabled. In short, LC_CTYPE="POSIX" now behaves as LC_CTYPE="C".

This change impacts at least FreeBSD. If I correctly, if there is no LC_ALL, LC_CTYPE or LANG environment variable on FreeBSD, the LC_CTYPE locale is "POSIX".

See bpo-34485, bpo-19977 and the "POSIX locale on FreeBSD" section of my article:
https://vstinner.github.io/python3-locales-encodings.html

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32238>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:35:15 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Oct 2019 21:35:15 +0000
Subject: [issue30672] PEP 538: Unexpected locale behaviour on *BSD (including
 Mac OS X)
In-Reply-To: <1497518633.36.0.998856107706.issue30672@psf.upfronthosting.co.za>
Message-ID: <1570829715.63.0.560576591098.issue30672@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Since this issue has been created, I deeply reworked the Python Initialization with the PEP 587, and I made many changes related to locales and the UTF-8 Mode (PEP 540). What's the status of this issue?

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30672>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:36:49 2019
From: report at bugs.python.org (Tal Einat)
Date: Fri, 11 Oct 2019 21:36:49 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1570829809.66.0.663005342504.issue38382@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

I'd certainly be surprised to have the order of zero and negative values in the input have such a dramatic effect on the result. It would make debugging these cases unnecessarily confusing and difficult. And I think it is indeed worth fixing, as these edge-cases are likely to come up of time when dealing with large amounts of data.

I'm +1 on Warren's latest suggestion for a fix.

P.S If we agree on this, either Warren should make the fix himself or we should mark it "newcomer friendly" and let a newcomer handle it.

----------
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:38:52 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 11 Oct 2019 21:38:52 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570829932.39.0.798660765805.issue38449@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Thanks for looking into this, @maxking. With both 3.8.0 final and 3.7.5 final scheduled for just a few days away, I wonder if the best thing to do at this point is to revert them and work on a more robust fix targeted for the next maintenance releases since the original issue was not identified as being a security issue or otherwise critical.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Fri Oct 11 17:53:36 2019
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 11 Oct 2019 21:53:36 +0000
Subject: [issue38452] unittest setUpClass missing 1 required positional
 argument: 'cls'
In-Reply-To: <1570829339.09.0.69466145285.issue38452@roundup.psfhosted.org>
Message-ID: <1570830816.62.0.685824711935.issue38452@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:

`setUpClass` and `tearDownClass` are classmethods and must be decorated as such (`@classmethod`).

----------
nosy: +zach.ware
resolution:  -> not a bug
status: open -> pending

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38452>
_______________________________________

From report at bugs.python.org  Fri Oct 11 18:09:28 2019
From: report at bugs.python.org (Tal Einat)
Date: Fri, 11 Oct 2019 22:09:28 +0000
Subject: [issue38401] Make dataclass attribute docstrings accessible
In-Reply-To: <1570494293.05.0.934356434949.issue38401@roundup.psfhosted.org>
Message-ID: <1570831768.84.0.161865175743.issue38401@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

Thanks for this suggestion John!

Unfortunately, only the first string literal in the example is a doc-string, and the rest indeed are not. (PEP-258 suggested adding such doc-strings, but it was rejected.)

There is currently no standard way to attach a doc-string to a field in dataclasses, nor in attrs on which dataclasses was mostly based. However, both libraries support custom field meta-data, using which one could add such per-field documentation. So if one really needs something like this, it is possible to work up a custom solution.

Eric is correct that this is far from a straightforward suggestion, which would require a significant language change to implement. Due to the depth of the change required, it would need to be discussed on Python-ideas mailing list first. Please bring this up there if you'd like to pursue this further.

I'm closing this as "rejected" for now since I believe the likelihood of pursuing this to be very small, but this can be re-opened later if further discussion warrants it.

----------
nosy: +taleinat
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38401>
_______________________________________

From report at bugs.python.org  Fri Oct 11 18:11:34 2019
From: report at bugs.python.org (Tal Einat)
Date: Fri, 11 Oct 2019 22:11:34 +0000
Subject: [issue38422] Clarify docstrings of pathlib suffix(es)
In-Reply-To: <1570634139.23.0.159522926495.issue38422@roundup.psfhosted.org>
Message-ID: <1570831894.26.0.904939799452.issue38422@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

>From the PR, the rationale for this suggestion is:

"Whenever I use path.suffix I have to check again whether it includes the dot or not. I decided to add it to the docstring so I won't have to keep checking."

----------
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38422>
_______________________________________

From report at bugs.python.org  Fri Oct 11 18:27:20 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 11 Oct 2019 22:27:20 +0000
Subject: [issue38453] ntpath.realpath() should make absolute path earlier
Message-ID: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>


New submission from Steve Dower <steve.dower at python.org>:

Because the abspath() call is deferred until the end of the resolution process, if the current working directory is not already a real path, it will not be fully resolved.

By passing it through abspath() at the start of the function, we ensure that the correct path is resolved.

This will help resolve some inconsistencies in the test suite when tests are launched with a short filename (FILENA~1) in the working directory (though some other fixes are probably needed to help here).

----------
components: Windows
messages: 354509
nosy: eryksun, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title: ntpath.realpath() should make absolute path earlier
type: behavior
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Fri Oct 11 18:28:48 2019
From: report at bugs.python.org (Tal Einat)
Date: Fri, 11 Oct 2019 22:28:48 +0000
Subject: [issue38440] Possible new issues with IDLE
In-Reply-To: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>
Message-ID: <1570832928.88.0.141910149787.issue38440@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Fri Oct 11 18:33:37 2019
From: report at bugs.python.org (Tal Einat)
Date: Fri, 11 Oct 2019 22:33:37 +0000
Subject: [issue38445] os.path.exists() takes bool as argument and returns True
In-Reply-To: <1570792602.16.0.709405121857.issue38445@roundup.psfhosted.org>
Message-ID: <1570833217.4.0.145323226534.issue38445@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

Mariano Anaya, you're welcome to work on this and create a PR.

There's no need to have this issue assigned to you: feel free to just begin working. Anyone reading this will know that you intended to work on this.

(FYI, we only assign issues to core developers, and assigning means something slightly different than "who is working on this.")

----------
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38445>
_______________________________________

From report at bugs.python.org  Fri Oct 11 18:35:42 2019
From: report at bugs.python.org (A.M. Kuchling)
Date: Fri, 11 Oct 2019 22:35:42 +0000
Subject: [issue38450] 3.8 Release Notes: IDLE section dupe
In-Reply-To: <1570809778.37.0.687630988781.issue38450@roundup.psfhosted.org>
Message-ID: <1570833342.66.0.742406640246.issue38450@roundup.psfhosted.org>


Change by A.M. Kuchling <amk at amk.ca>:


----------
pull_requests: +16300
pull_request: https://github.com/python/cpython/pull/16621

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38450>
_______________________________________

From report at bugs.python.org  Fri Oct 11 18:42:30 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 11 Oct 2019 22:42:30 +0000
Subject: [issue38453] ntpath.realpath() should make absolute path earlier
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1570833750.17.0.50048470532.issue38453@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Updating change_cwd() in Lib/test/support/__init__.py to call chdir(realpath(path)) also fixes the test issues I was facing, but the realpath() implementation needs fixing.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Fri Oct 11 19:01:47 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 11 Oct 2019 23:01:47 +0000
Subject: [issue38453] ntpath.realpath() should make absolute path earlier
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1570834907.72.0.7600910022.issue38453@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords: +patch
pull_requests: +16301
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16723

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Fri Oct 11 19:03:21 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 11 Oct 2019 23:03:21 +0000
Subject: [issue38453] ntpath.realpath() should make absolute path earlier
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1570835001.84.0.963288087726.issue38453@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

PR 16723 is just for the test fix.

The realpath() fix should get tests that chdir (without change_cwd()) into a symlink and then realpath() on a relative path. Today, that should fail to resolve the sections in the CWD, and with the fix it should resolve the entire path.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Fri Oct 11 20:38:51 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 00:38:51 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570840731.6.0.443857779991.issue38449@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

Yeah, I agree. I'll submit a PR for reverting the commits.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Fri Oct 11 20:42:58 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 00:42:58 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570840978.15.0.68222021928.issue38449@roundup.psfhosted.org>


Change by Abhilash Raj <raj.abhilash1 at gmail.com>:


----------
keywords: +patch
pull_requests: +16302
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16724

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Fri Oct 11 20:42:58 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 00:42:58 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1570840978.29.0.853260303709.issue22347@roundup.psfhosted.org>


Change by Abhilash Raj <raj.abhilash1 at gmail.com>:


----------
pull_requests: +16303
pull_request: https://github.com/python/cpython/pull/16724

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Fri Oct 11 20:50:15 2019
From: report at bugs.python.org (Eryk Sun)
Date: Sat, 12 Oct 2019 00:50:15 +0000
Subject: [issue38445] os.path.exists() takes bool as argument and returns True
In-Reply-To: <1570792602.16.0.709405121857.issue38445@roundup.psfhosted.org>
Message-ID: <1570841415.31.0.436808755077.issue38445@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

> Maybe os.fspath() can be used

I think that would already be the case if genericpath.exists didn't have to support file descriptors. It's documented that the path argument "refers to an existing path or an open file descriptor".

Modifying _fd_converter would provide consistent behavior for all calls that ultimately use argument clinic's path_t(allow_fd=True) and/or dir_fd. Serhiy's suggestion to raise a warning sounds good. 

Here are some examples that currently pass silently in Linux:

    >>> os.chown(False, 1000, 1000)
    >>> os.chmod(False, 0o666)
    >>> os.utime(False, (1500000000, 1500000000))

Probably os.fstat and other "f" functions (e.g. fstatvfs, fchdir, fchown, fchmod, ftruncate, fdatasync, fsync, and fpathconf) should also raise a warning when passed a bool. For example, the following would raise a warning instead of passing silently:

    >>> os.fstat(False).st_size
    0

These cases could be addressed by consistently using an argument clinic type. Some of them already us the fildes type (e.g. fchdir, fsync, fdatasync). However, fildes_converter calls PyObject_AsFileDescriptor, which also supports objects with a fileno() method. That's documented behavior for PyObject_AsFileDescriptor, but nothing in the documentation of fchdir, fsync, and fdatasync suggests to me that they support objects with a fileno() method:

    >>> os.fchdir(sys.stdin)
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
    NotADirectoryError: [Errno 20] Not a directory

If not for this behavior, we could simply change all of the "f" functions to use the fildes type.

PyObject_AsFileDescriptor is used in various other places as well, such as the select module. In the latter case, supporting objects with a fileno() method is clearly documented.

Also consider including open() and os.fdopen by modifying _io_open_impl in Modules/_io/_iomodule.c. For example:

   >>> open(False, closefd=False)
    <_io.TextIOWrapper name=False mode='r' encoding='UTF-8'>

Currently it calls PyNumber_Check(file). If true, a warning could be raised if PyBool_Check(file) is also true.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38445>
_______________________________________

From report at bugs.python.org  Fri Oct 11 21:51:50 2019
From: report at bugs.python.org (Giampaolo Rodola')
Date: Sat, 12 Oct 2019 01:51:50 +0000
Subject: [issue38378] os.sendfile() has improperly named parameter
In-Reply-To: <1570287843.24.0.0727618245068.issue38378@roundup.psfhosted.org>
Message-ID: <1570845110.16.0.616048006376.issue38378@roundup.psfhosted.org>


Giampaolo Rodola' <g.rodola at gmail.com> added the comment:

I?m for renaming both. Since the function is about transmitting or copying (on Linux) files src_fd and dst_fd could also be good candidates.

----------
nosy: +giampaolo.rodola

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38378>
_______________________________________

From report at bugs.python.org  Fri Oct 11 23:15:55 2019
From: report at bugs.python.org (Dima Tisnek)
Date: Sat, 12 Oct 2019 03:15:55 +0000
Subject: [issue38424] typing.Generator shorthand
In-Reply-To: <1570671541.73.0.307162838122.issue38424@roundup.psfhosted.org>
Message-ID: <1570850155.72.0.653488270828.issue38424@roundup.psfhosted.org>


Dima Tisnek <dimaqq at gmail.com> added the comment:

Clearly my attention span does not exceed 5 paragraphs, so sorry!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38424>
_______________________________________

From report at bugs.python.org  Sat Oct 12 00:46:31 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 12 Oct 2019 04:46:31 +0000
Subject: [issue38451] Datetime definition does not work in function definition
 as list definition
In-Reply-To: <1570816815.04.0.693882405229.issue38451@roundup.psfhosted.org>
Message-ID: <1570855591.22.0.786733575382.issue38451@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Without more information, we cannot do anything with this.

----------
nosy: +terry.reedy
status: open -> pending
versions:  -Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38451>
_______________________________________

From report at bugs.python.org  Sat Oct 12 01:06:32 2019
From: report at bugs.python.org (Batuhan)
Date: Sat, 12 Oct 2019 05:06:32 +0000
Subject: [issue38454] test_listdir is failing on ubuntu with WSL
Message-ID: <1570856792.9.0.835565691535.issue38454@roundup.psfhosted.org>


New submission from Batuhan <batuhanosmantaskaya at gmail.com>:

Run tests sequentially
0:00:00 load avg: 0.52 [1/1] test_os
test test_os failed -- Traceback (most recent call last):
  File "/home/isidentical/cpython/Lib/test/test_os.py", line 2059, in test_listdir
    self.assertEqual(found, expected)
AssertionError: Items in the first set but not the second:
'@test_12966_tmp-?'
Items in the second set but not the first:
'@test_12966_tmp-\udcff'

test_os failed

== Tests result: FAILURE ==

1 test failed:
    test_os

Total duration: 2 sec 587 ms
Tests result: FAILURE


System:
 - Ubuntu 18.04 bionic
 - x86_64 Linux 4.4.0-18362-Microsoft

----------
components: Tests
messages: 354518
nosy: BTaskaya, steve.dower
priority: normal
severity: normal
status: open
title: test_listdir is failing on ubuntu with WSL
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38454>
_______________________________________

From report at bugs.python.org  Sat Oct 12 01:06:50 2019
From: report at bugs.python.org (Pouria)
Date: Sat, 12 Oct 2019 05:06:50 +0000
Subject: [issue38451] Datetime definition does not work in function definition
 as list definition
In-Reply-To: <1570855591.22.0.786733575382.issue38451@roundup.psfhosted.org>
Message-ID: <CAC5VVj_Dw3dyjKvUC24x1_z6Mroenhp3zw7k-p23tPXgxorWCA@mail.gmail.com>


Pouria <Pouriaff7171 at gmail.com> added the comment:

For example
Def a(time=datetime.datetime.today()):
     Print(time)
Output:
    The output of each run is equal to the       first time output
     For exaple :
      If you run
      a()
      Sleep(10)
      a()
      Sleep(10)
       a()
      You see one output three time

?? ????? ???? ?? ????? ?????? ?:?? Terry J. Reedy <report at bugs.python.org>
????:

>
> Terry J. Reedy <tjreedy at udel.edu> added the comment:
>
> Without more information, we cannot do anything with this.
>
> ----------
> nosy: +terry.reedy
> status: open -> pending
> versions:  -Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue38451>
> _______________________________________
>

----------
status: pending -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38451>
_______________________________________

From report at bugs.python.org  Sat Oct 12 01:10:36 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 12 Oct 2019 05:10:36 +0000
Subject: [issue38451] Datetime definition does not work in function definition
 as list definition
In-Reply-To: <1570816815.04.0.693882405229.issue38451@roundup.psfhosted.org>
Message-ID: <1570857036.84.0.34129408011.issue38451@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Default arguments are evaluated only once as the function is defined and not per call.

This is a common gotcha : https://stackoverflow.com/questions/1132941/least-astonishment-and-the-mutable-default-argument

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38451>
_______________________________________

From report at bugs.python.org  Sat Oct 12 01:41:50 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 05:41:50 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1570858910.71.0.335374592646.issue22347@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 19a3d873005e5730eeabdc394c961e93f2ec02f0 by Miss Islington (bot) (Abhilash Raj) in branch 'master':
bpo-38449: Revert "bpo-22347: Update mimetypes.guess_type to allow oper parsing of URLs (GH-15522)" (GH-16724)
https://github.com/python/cpython/commit/19a3d873005e5730eeabdc394c961e93f2ec02f0


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Sat Oct 12 01:41:54 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 05:41:54 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1570858914.01.0.296709556077.issue22347@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16305
pull_request: https://github.com/python/cpython/pull/16725

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Sat Oct 12 01:41:50 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 05:41:50 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570858910.87.0.692949868217.issue38449@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 19a3d873005e5730eeabdc394c961e93f2ec02f0 by Miss Islington (bot) (Abhilash Raj) in branch 'master':
bpo-38449: Revert "bpo-22347: Update mimetypes.guess_type to allow oper parsing of URLs (GH-15522)" (GH-16724)
https://github.com/python/cpython/commit/19a3d873005e5730eeabdc394c961e93f2ec02f0


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 01:41:53 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 05:41:53 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570858913.72.0.72407936528.issue38449@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16304
pull_request: https://github.com/python/cpython/pull/16725

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 02:04:23 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 12 Oct 2019 06:04:23 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570860263.87.0.0609286891195.issue38449@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

I'd like to suggest add unit test for the report case.
So that we can detect future regression issue :)

----------
nosy: +corona10

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 02:13:56 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 12 Oct 2019 06:13:56 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570860836.42.0.490998271389.issue38449@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

And I aplogize for my patch which makes regrssion issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 03:12:15 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 12 Oct 2019 07:12:15 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570864335.73.0.370546876786.issue38417@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
assignee:  -> gregory.p.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Sat Oct 12 03:16:24 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 12 Oct 2019 07:16:24 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570864584.47.0.659124840406.issue38417@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
keywords: +patch
pull_requests: +16306
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16726

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Sat Oct 12 04:09:36 2019
From: report at bugs.python.org (Danylo)
Date: Sat, 12 Oct 2019 08:09:36 +0000
Subject: [issue38452] unittest setUpClass missing 1 required positional
 argument: 'cls'
In-Reply-To: <1570829339.09.0.69466145285.issue38452@roundup.psfhosted.org>
Message-ID: <1570867776.31.0.865248900972.issue38452@roundup.psfhosted.org>


Danylo <dizcza at gmail.com> added the comment:

Sorry, true.
You can close the issue.

----------
stage:  -> resolved
status: pending -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38452>
_______________________________________

From report at bugs.python.org  Sat Oct 12 04:49:49 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Sat, 12 Oct 2019 08:49:49 +0000
Subject: [issue38451] Datetime definition does not work in function definition
 as list definition
In-Reply-To: <1570816815.04.0.693882405229.issue38451@roundup.psfhosted.org>
Message-ID: <1570870189.02.0.121820613859.issue38451@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

This is not a bug, this is the design of function default arguments.

Default arguments in Python use *early binding*, which means they are calculated once, when the function is declared, rather than *late binding*, which means they are calculated each time the function is called.

You can get the effect of late binding by testing for None:

    def func(time=None):
        if time is None:
            time = datetime.datetime.today()
        print(time)


Neither choice is right or wrong, they both have advantages and disadvantages. Python chooses early binding for function defaults, and late binding for closures, which have their own, different, gotchas.

----------
nosy: +steven.daprano
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38451>
_______________________________________

From report at bugs.python.org  Sat Oct 12 04:52:39 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Sat, 12 Oct 2019 08:52:39 +0000
Subject: [issue38451] Datetime definition does not work in function definition
 as list definition
In-Reply-To: <1570816815.04.0.693882405229.issue38451@roundup.psfhosted.org>
Message-ID: <1570870359.86.0.656689209626.issue38451@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Oh, I forgot to mention that this is discussed in one of the FAQs:

https://docs.python.org/3/faq/programming.html#why-are-default-values-shared-between-objects

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38451>
_______________________________________

From report at bugs.python.org  Sat Oct 12 06:29:49 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 12 Oct 2019 10:29:49 +0000
Subject: [issue37731] Possible redifinition of _POSIX_C_SOURCE in ./pyconfig.h
In-Reply-To: <1564582479.63.0.743037360682.issue37731@roundup.psfhosted.org>
Message-ID: <1570876189.8.0.817666913756.issue37731@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

This is also reproducible on Ubuntu 18.04 gcc 7.4.0

In file included from /home/corona10/cpython/Modules/expat/expat_config.h:8:0,
                 from /home/corona10/cpython/Modules/expat/xmltok.c:49:
./pyconfig.h:1586:0: warning: "_POSIX_C_SOURCE" redefined
 #define _POSIX_C_SOURCE 200809L

In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33:0,
                 from /usr/include/string.h:26,
                 from /home/corona10/cpython/Modules/expat/xmltok.c:34:
/usr/include/features.h:294:0: note: this is the location of the previous definition
 # define _POSIX_C_SOURCE 199506L

----------
nosy: +corona10

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37731>
_______________________________________

From report at bugs.python.org  Sat Oct 12 07:24:06 2019
From: report at bugs.python.org (Caleb Hattingh)
Date: Sat, 12 Oct 2019 11:24:06 +0000
Subject: [issue38306] High level API for loop.run_in_executor(None, ...)?
In-Reply-To: <1569681785.01.0.799144749415.issue38306@roundup.psfhosted.org>
Message-ID: <1570879446.69.0.504074792483.issue38306@roundup.psfhosted.org>


Caleb Hattingh <caleb.hattingh at gmail.com> added the comment:

Even before task groups land, this API can be easily improved by adding

asyncio.run_in_executor(func, *args, **kwargs)

- Only valid inside a coro or async context (uses get_running_loop internally)
- Analogous to how `loop.create_task` became `asyncio.create_task`
- Drop having to specify `None` for the default executor
- Users already know the `run_in_executor` name
- Allow both positional and kwargs (we can partial internally before calling loop.run_in_executor)

----------
nosy: +cjrh

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38306>
_______________________________________

From report at bugs.python.org  Sat Oct 12 07:39:45 2019
From: report at bugs.python.org (Antoine Pietri)
Date: Sat, 12 Oct 2019 11:39:45 +0000
Subject: [issue38306] High level API for loop.run_in_executor(None, ...)?
In-Reply-To: <1570879446.69.0.504074792483.issue38306@roundup.psfhosted.org>
Message-ID: <CAOMH6m2OqOLiEKMr+RC+Ef-jw5_qVURZpLM6_=1qQu_AuRqrtQ@mail.gmail.com>


Antoine Pietri <antoine.pietri1 at gmail.com> added the comment:

On Sat, Oct 12, 2019 at 1:24 PM Caleb Hattingh <report at bugs.python.org> wrote:
> Even before task groups land, this API can be easily improved by adding
>
> asyncio.run_in_executor(func, *args, **kwargs)
>
> - Only valid inside a coro or async context (uses get_running_loop internally)
> - Analogous to how `loop.create_task` became `asyncio.create_task`
> - Drop having to specify `None` for the default executor
> - Users already know the `run_in_executor` name
> - Allow both positional and kwargs (we can partial internally before calling loop.run_in_executor)

I think it should be run_thread() if it only works for thread.
run_in_executor() should take an executor= parameter, but it wouldn't
be as clear for beginners. I think there's value in having a simple,
explicit way of saying "I want to run this function in a thread"
without having to know what executors are.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38306>
_______________________________________

From report at bugs.python.org  Sat Oct 12 07:53:14 2019
From: report at bugs.python.org (Caleb Hattingh)
Date: Sat, 12 Oct 2019 11:53:14 +0000
Subject: [issue38306] High level API for loop.run_in_executor(None, ...)?
In-Reply-To: <1569681785.01.0.799144749415.issue38306@roundup.psfhosted.org>
Message-ID: <1570881194.39.0.593388289728.issue38306@roundup.psfhosted.org>


Caleb Hattingh <caleb.hattingh at gmail.com> added the comment:

We can't allow both an `executor=` kwarg, as well as **kwargs for the target func, unfortunately. If we do `executor=`, we'll again have to force users to use functools.partial to wrap their functions that take kwargs.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38306>
_______________________________________

From report at bugs.python.org  Sat Oct 12 08:10:23 2019
From: report at bugs.python.org (Larry Hastings)
Date: Sat, 12 Oct 2019 12:10:23 +0000
Subject: [issue36274] http.client cannot send non-ASCII request lines
In-Reply-To: <1552422803.93.0.420596825145.issue36274@roundup.psfhosted.org>
Message-ID: <1570882223.29.0.945645486661.issue36274@roundup.psfhosted.org>


Change by Larry Hastings <larry at hastings.org>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36274>
_______________________________________

From report at bugs.python.org  Sat Oct 12 08:18:20 2019
From: report at bugs.python.org (Antoine Pietri)
Date: Sat, 12 Oct 2019 12:18:20 +0000
Subject: [issue38306] High level API for loop.run_in_executor(None, ...)?
In-Reply-To: <1570881194.39.0.593388289728.issue38306@roundup.psfhosted.org>
Message-ID: <CAOMH6m0ihSSKMCYDtSWqQpbQ_+69pe8cWK8NySGyw4Hbzpbv5g@mail.gmail.com>


Antoine Pietri <antoine.pietri1 at gmail.com> added the comment:

Yes, that's why I'm in favor of calling it run_thread. Because it
fundamentally *isn't* a way to run a function in an executor, it's a
way to run a function in a thread.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38306>
_______________________________________

From report at bugs.python.org  Sat Oct 12 11:52:49 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 15:52:49 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1570895569.53.0.819439290642.issue22347@roundup.psfhosted.org>


Change by Abhilash Raj <raj.abhilash1 at gmail.com>:


----------
pull_requests: +16307
pull_request: https://github.com/python/cpython/pull/16727

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Sat Oct 12 11:56:15 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 15:56:15 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570895775.19.0.250240860671.issue38449@roundup.psfhosted.org>


Change by Abhilash Raj <raj.abhilash1 at gmail.com>:


----------
pull_requests: +16308
pull_request: https://github.com/python/cpython/pull/16727

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 12:04:59 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 16:04:59 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570896299.66.0.929065693785.issue38449@roundup.psfhosted.org>


Change by Abhilash Raj <raj.abhilash1 at gmail.com>:


----------
pull_requests: +16309
pull_request: https://github.com/python/cpython/pull/16728

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 12:04:59 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 16:04:59 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1570896299.88.0.580068529889.issue22347@roundup.psfhosted.org>


Change by Abhilash Raj <raj.abhilash1 at gmail.com>:


----------
pull_requests: +16310
pull_request: https://github.com/python/cpython/pull/16728

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Sat Oct 12 12:08:27 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 16:08:27 +0000
Subject: [issue38341] Add SMTPNotSupportedError in the exports of smtplib
In-Reply-To: <1569963046.98.0.477841717728.issue38341@roundup.psfhosted.org>
Message-ID: <1570896507.63.0.619157703021.issue38341@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 1da648aceb2496c672aff82ba37ee071ac6054ac by Miss Islington (bot) in branch '3.8':
bpo-38341: Add SMTPNotSupportedError in the exports of smtplib (GH-16525)
https://github.com/python/cpython/commit/1da648aceb2496c672aff82ba37ee071ac6054ac


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38341>
_______________________________________

From report at bugs.python.org  Sat Oct 12 12:26:08 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 16:26:08 +0000
Subject: [issue38341] Add SMTPNotSupportedError in the exports of smtplib
In-Reply-To: <1569963046.98.0.477841717728.issue38341@roundup.psfhosted.org>
Message-ID: <1570897568.11.0.535432365457.issue38341@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset cb580d6fa8349acff723a7a044181d896d076871 by Miss Islington (bot) in branch '3.7':
bpo-38341: Add SMTPNotSupportedError in the exports of smtplib (GH-16525)
https://github.com/python/cpython/commit/cb580d6fa8349acff723a7a044181d896d076871


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38341>
_______________________________________

From report at bugs.python.org  Sat Oct 12 12:29:38 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 16:29:38 +0000
Subject: [issue38341] Add SMTPNotSupportedError in the exports of smtplib
In-Reply-To: <1569963046.98.0.477841717728.issue38341@roundup.psfhosted.org>
Message-ID: <1570897778.01.0.238333993645.issue38341@roundup.psfhosted.org>


Change by Abhilash Raj <raj.abhilash1 at gmail.com>:


----------
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38341>
_______________________________________

From report at bugs.python.org  Sat Oct 12 12:30:21 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 16:30:21 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1570897821.94.0.334418608825.issue22347@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

I am going to re-open this since the fixes were reverted in all the branches.

----------
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Sat Oct 12 12:42:59 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 16:42:59 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570898579.59.0.118798211088.issue38449@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

corona10: That's okay, it happens. I missed it too. There was really no way to foresee all the use cases, which is why we have beta and rc period to catch bugs.

Yes, we should add a test case definitely, do you want to work on a PR?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 12:49:08 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 12 Oct 2019 16:49:08 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570898948.77.0.47925813084.issue38449@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> Yes, we should add a test case definitely, do you want to work on a PR?

Sure, I want to finalize this issue :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 12:58:15 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 16:58:15 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1570899495.17.0.138969361547.issue22347@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:


New changeset 5a638a805503131f4a9cc2bbc5944611295c1500 by Abhilash Raj in branch '3.8':
[3.8] bpo-38449: Revert "bpo-22347: Update mimetypes.guess_type to allow oper parsing of URLs" (GH-16724) (GH-16728)
https://github.com/python/cpython/commit/5a638a805503131f4a9cc2bbc5944611295c1500


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Sat Oct 12 12:58:15 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 16:58:15 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570899495.31.0.932197618624.issue38449@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:


New changeset 5a638a805503131f4a9cc2bbc5944611295c1500 by Abhilash Raj in branch '3.8':
[3.8] bpo-38449: Revert "bpo-22347: Update mimetypes.guess_type to allow oper parsing of URLs" (GH-16724) (GH-16728)
https://github.com/python/cpython/commit/5a638a805503131f4a9cc2bbc5944611295c1500


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 13:02:29 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 17:02:29 +0000
Subject: [issue38332] invalid content-transfer-encoding in encoded-word causes
 KeyError
In-Reply-To: <1569877053.41.0.568400002445.issue38332@roundup.psfhosted.org>
Message-ID: <1570899748.99.0.759960095468.issue38332@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset febe359559781019c0c8432a2f768809d00af6af by Miss Islington (bot) in branch '3.7':
bpo-38332: Catch KeyError from unknown cte in encoded-word. (GH-16503)
https://github.com/python/cpython/commit/febe359559781019c0c8432a2f768809d00af6af


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38332>
_______________________________________

From report at bugs.python.org  Sat Oct 12 13:03:27 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 17:03:27 +0000
Subject: [issue38332] invalid content-transfer-encoding in encoded-word causes
 KeyError
In-Reply-To: <1569877053.41.0.568400002445.issue38332@roundup.psfhosted.org>
Message-ID: <1570899807.81.0.106754798982.issue38332@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset e540bb546163f108c7c304f2e6865efaa78cd4c2 by Miss Islington (bot) in branch '3.8':
bpo-38332: Catch KeyError from unknown cte in encoded-word. (GH-16503)
https://github.com/python/cpython/commit/e540bb546163f108c7c304f2e6865efaa78cd4c2


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38332>
_______________________________________

From report at bugs.python.org  Sat Oct 12 13:04:04 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 12 Oct 2019 17:04:04 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570899844.61.0.17346838655.issue38449@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
pull_requests: +16311
pull_request: https://github.com/python/cpython/pull/16729

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 13:04:19 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sat, 12 Oct 2019 17:04:19 +0000
Subject: [issue38332] invalid content-transfer-encoding in encoded-word causes
 KeyError
In-Reply-To: <1569877053.41.0.568400002445.issue38332@roundup.psfhosted.org>
Message-ID: <1570899859.51.0.765147147752.issue38332@roundup.psfhosted.org>


Change by Abhilash Raj <raj.abhilash1 at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions:  -Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38332>
_______________________________________

From report at bugs.python.org  Sat Oct 12 13:24:29 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 17:24:29 +0000
Subject: [issue35800] remove smtpd.MailmanProxy
In-Reply-To: <1548091630.84.0.140233087609.issue35800@roundup.psfhosted.org>
Message-ID: <1570901069.3.0.775421584888.issue35800@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 822922af90f389b20166f0cd6f5b7c76fd6d42d9 by Miss Islington (bot) (Samuel Colvin) in branch 'master':
bpo-35800: Deprecate smtpd.MailmanProxy (GH-11675)
https://github.com/python/cpython/commit/822922af90f389b20166f0cd6f5b7c76fd6d42d9


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35800>
_______________________________________

From report at bugs.python.org  Sat Oct 12 14:32:21 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 12 Oct 2019 18:32:21 +0000
Subject: [issue37731] Possible redifinition of _POSIX_C_SOURCE in ./pyconfig.h
In-Reply-To: <1564582479.63.0.743037360682.issue37731@roundup.psfhosted.org>
Message-ID: <1570905141.52.0.711782224007.issue37731@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +patch
pull_requests: +16312
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16733

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37731>
_______________________________________

From report at bugs.python.org  Sat Oct 12 14:50:07 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 18:50:07 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570906207.15.0.584621401304.issue38449@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 164bee296ab1f87cc05566b39ee8fb9fb64b3e5a by Miss Islington (bot) (Abhilash Raj) in branch '3.7':
[3.7] bpo-38449: Revert "bpo-22347: Update mimetypes.guess_type to allow oper parsing of URLs (GH-15685)" (GH-16724) (GH-16727)
https://github.com/python/cpython/commit/164bee296ab1f87cc05566b39ee8fb9fb64b3e5a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 14:50:06 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 18:50:06 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1570906206.95.0.966105605982.issue22347@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 164bee296ab1f87cc05566b39ee8fb9fb64b3e5a by Miss Islington (bot) (Abhilash Raj) in branch '3.7':
[3.7] bpo-38449: Revert "bpo-22347: Update mimetypes.guess_type to allow oper parsing of URLs (GH-15685)" (GH-16724) (GH-16727)
https://github.com/python/cpython/commit/164bee296ab1f87cc05566b39ee8fb9fb64b3e5a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Sat Oct 12 14:52:00 2019
From: report at bugs.python.org (Ned Deily)
Date: Sat, 12 Oct 2019 18:52:00 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570906320.62.0.524473250957.issue38449@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Thanks everyone for the quick action on this!

----------
priority: release blocker -> normal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 14:52:59 2019
From: report at bugs.python.org (Ned Deily)
Date: Sat, 12 Oct 2019 18:52:59 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1570906379.97.0.660250647266.issue38449@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

(On second thought, I'll leave this open as a release blocker until we've cherry-picked the fixes for 3.8.0 final and 3.7.5 final.)

----------
priority: normal -> release blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Sat Oct 12 15:11:40 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 12 Oct 2019 19:11:40 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0NTVdIOKAmG1lbXNldOKAmSBvZmZzZXQgWzE3LCA4OF0gZnJv?=
 =?utf-8?q?m_the_object_at_=E2=80=98addrbuf=E2=80=99_is_out_of_the_bounds_?=
 =?utf-8?q?of_referenced_subobject?=
Message-ID: <1570907500.34.0.810333858419.issue38455@roundup.psfhosted.org>


New submission from Pablo Galindo Salgado <pablogsal at gmail.com>:

Compiling 3.8 in release mode emits this warning:

In function ?getsockaddrarg?,
    inlined from ?sock_bind? at /home/pablogsal/github/python/3.8/Modules/socketmodule.c:3066:10:
/home/pablogsal/github/python/3.8/Modules/socketmodule.c:2288:9: warning: ?memset? offset [17, 88] from the object at ?addrbuf? is out of the bounds of referenced subobject ?sa? with type ?struct sockaddr? at offset 0 [-Warray-bounds]
 2288 |         memset(sa, 0, sizeof(*sa));
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~

----------
messages: 354547
nosy: lukasz.langa, pablogsal, vstinner
priority: normal
severity: normal
status: open
title: ?memset? offset [17, 88] from the object at ?addrbuf? is out of the bounds of referenced subobject
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38455>
_______________________________________

From report at bugs.python.org  Sat Oct 12 15:14:14 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 12 Oct 2019 19:14:14 +0000
Subject: [issue37731] Possible redifinition of _POSIX_C_SOURCE in ./pyconfig.h
In-Reply-To: <1564582479.63.0.743037360682.issue37731@roundup.psfhosted.org>
Message-ID: <1570907654.16.0.834621505929.issue37731@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 8177404d520e81f16324a900f093adf3856d33f8 by Pablo Galindo in branch 'master':
bpo-37731: Reorder includes in xmltok.c to avoid redefinition of _POSIX_C_SOURCE (GH-16733)
https://github.com/python/cpython/commit/8177404d520e81f16324a900f093adf3856d33f8


----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37731>
_______________________________________

From report at bugs.python.org  Sat Oct 12 15:14:21 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 19:14:21 +0000
Subject: [issue37731] Possible redifinition of _POSIX_C_SOURCE in ./pyconfig.h
In-Reply-To: <1564582479.63.0.743037360682.issue37731@roundup.psfhosted.org>
Message-ID: <1570907661.49.0.358472892741.issue37731@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16313
pull_request: https://github.com/python/cpython/pull/16734

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37731>
_______________________________________

From report at bugs.python.org  Sat Oct 12 15:17:59 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 12 Oct 2019 19:17:59 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0NTVdIOKAmG1lbXNldOKAmSBvZmZzZXQgWzE3LCA4OF0gZnJv?=
 =?utf-8?q?m_the_object_at_=E2=80=98addrbuf=E2=80=99_is_out_of_the_bounds_?=
 =?utf-8?q?of_referenced_subobject?=
In-Reply-To: <1570907500.34.0.810333858419.issue38455@roundup.psfhosted.org>
Message-ID: <1570907879.25.0.72528683453.issue38455@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy: +christian.heimes

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38455>
_______________________________________

From report at bugs.python.org  Sat Oct 12 15:18:52 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 12 Oct 2019 19:18:52 +0000
Subject: =?utf-8?b?W2lzc3VlMzg0NTVdIOKAmG1lbXNldOKAmSBvZmZzZXQgWzE3LCA4OF0gZnJv?=
 =?utf-8?q?m_the_object_at_=E2=80=98addrbuf=E2=80=99_is_out_of_the_bounds_?=
 =?utf-8?q?of_referenced_subobject?=
In-Reply-To: <1570907500.34.0.810333858419.issue38455@roundup.psfhosted.org>
Message-ID: <1570907932.86.0.757332588206.issue38455@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Duplicate of https://bugs.python.org/issue38282

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38455>
_______________________________________

From report at bugs.python.org  Sat Oct 12 15:22:20 2019
From: report at bugs.python.org (Eryk Sun)
Date: Sat, 12 Oct 2019 19:22:20 +0000
Subject: [issue38454] test_listdir is failing on ubuntu with WSL
In-Reply-To: <1570856792.9.0.835565691535.issue38454@roundup.psfhosted.org>
Message-ID: <1570908140.02.0.402337981702.issue38454@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

The test assumes that Unix filesystems store names as arbitrary sequences of bytes, with only ASCII slash and null reserved. Windows NTFS stores names as arbitrary sequences of 16-bit words, with many reserved ASCII characters including \/:*?<>"| and control characters 0x00-0x1F. WSL implements a UTF-8 filesystem encoding over this by transcoding bytes from UTF-8 to UTF-16LE and escaping reserved characters (excepting slash and null) as sequences that begin with "#" (e.g. "<#" -> "#003C#0023"). The latter is only visible from Windows in the distro's "LocalState\rootfs" tree.

This scheme fails for TESTFN_UNDECODABLE. Bytes that can't be transcoded to UTF-16LE are replaced by the replacement character U+FFFD. For example:

    >>> n = b'\xff'
    >>> open(n, 'w').close()
    >>> os.listdir(b'.')
    [b'\xef\xbf\xbd']
    >>> hex(ord(os.listdir('.')[0]))
    '0xfffd'

WSL could address this by abandoning their current "#" escaping approach to instead translate all reserved and undecodable bytes to the U+DC00-U+DCFF surrogate range, like Python's "surrogateescape" error handler. The Windows API could even support this with a new flag for MultiByteToWideChar and WideCharToMultiByte.

----------
nosy: +eryksun

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38454>
_______________________________________

From report at bugs.python.org  Sat Oct 12 15:32:53 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Oct 2019 19:32:53 +0000
Subject: [issue37731] Possible redifinition of _POSIX_C_SOURCE in ./pyconfig.h
In-Reply-To: <1564582479.63.0.743037360682.issue37731@roundup.psfhosted.org>
Message-ID: <1570908773.13.0.782698108549.issue37731@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset ba44ea6ff8be2b7874c4358f89d5b6f4a558f711 by Miss Islington (bot) in branch '3.8':
bpo-37731: Reorder includes in xmltok.c to avoid redefinition of _POSIX_C_SOURCE (GH-16733)
https://github.com/python/cpython/commit/ba44ea6ff8be2b7874c4358f89d5b6f4a558f711


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37731>
_______________________________________

From report at bugs.python.org  Sat Oct 12 15:33:48 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 12 Oct 2019 19:33:48 +0000
Subject: [issue37731] Possible redifinition of _POSIX_C_SOURCE in ./pyconfig.h
In-Reply-To: <1564582479.63.0.743037360682.issue37731@roundup.psfhosted.org>
Message-ID: <1570908828.85.0.390798472737.issue37731@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37731>
_______________________________________

From report at bugs.python.org  Sat Oct 12 16:17:35 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 12 Oct 2019 20:17:35 +0000
Subject: [issue38446] Ambiguous signature for builtins.__build_class__
In-Reply-To: <1570793351.47.0.198943437011.issue38446@roundup.psfhosted.org>
Message-ID: <1570911455.99.0.0410221473626.issue38446@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +patch
pull_requests: +16314
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16735

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38446>
_______________________________________

From report at bugs.python.org  Sat Oct 12 16:24:59 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 12 Oct 2019 20:24:59 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570911899.39.0.102230919371.issue38417@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:


New changeset f3751efb5c8b53b37efbbf75d9422c1d11c01646 by Gregory P. Smith in branch 'master':
bpo-38417: Add umask support to subprocess (GH-16726)
https://github.com/python/cpython/commit/f3751efb5c8b53b37efbbf75d9422c1d11c01646


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Sat Oct 12 16:26:18 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 12 Oct 2019 20:26:18 +0000
Subject: [issue38417] Add support for settting umask in subprocess children
In-Reply-To: <1570575339.67.0.686572067981.issue38417@roundup.psfhosted.org>
Message-ID: <1570911978.62.0.271281571581.issue38417@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

Now to see if the more esoteric config buildbots find any platform issues to address...

----------
resolution:  -> fixed
stage: patch review -> commit review
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38417>
_______________________________________

From report at bugs.python.org  Sat Oct 12 17:27:44 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 12 Oct 2019 21:27:44 +0000
Subject: [issue38456] Reduce the time test_subprocess takes to complete.
Message-ID: <1570915664.41.0.600749429007.issue38456@roundup.psfhosted.org>


New submission from Gregory P. Smith <greg at krypto.org>:

test_subprocess is one of our long running tests, this slows down CI and buildbots.  There is room for improvement in its total execution time.

Use this issue as a rollup issue for any such work.  we need to keep it reliable, just focus on reducing either user/sys cpu time or wall time.

----------
assignee: gregory.p.smith
components: Tests
messages: 354554
nosy: gregory.p.smith
priority: low
severity: normal
status: open
title: Reduce the time test_subprocess takes to complete.
type: performance
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38456>
_______________________________________

From report at bugs.python.org  Sat Oct 12 17:33:54 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 12 Oct 2019 21:33:54 +0000
Subject: [issue38456] Reduce the time test_subprocess takes to complete.
In-Reply-To: <1570915664.41.0.600749429007.issue38456@roundup.psfhosted.org>
Message-ID: <1570916034.08.0.916220242164.issue38456@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
keywords: +patch
pull_requests: +16315
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16736

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38456>
_______________________________________

From report at bugs.python.org  Sat Oct 12 17:48:12 2019
From: report at bugs.python.org (Yuval S)
Date: Sat, 12 Oct 2019 21:48:12 +0000
Subject: [issue38457] __package__ is None in __init__.py until an import is
 used
Message-ID: <1570916892.54.0.164577302417.issue38457@roundup.psfhosted.org>


New submission from Yuval S <sadan.yuval at gmail.com>:

In Python 2.7, the __package__ variable isn't set when __init__.py is run, until an import is done. In Python 3.5, it is set correctly.

e.g.

# mkdir x && echo "print(__package__)" | tee x/__init__.py x/test.py
# python2 x.test
None
x
# python3 x.test
x
x
# echo -e "import os\n$(cat x/__init__.py)" > x/__init__.py
# python2 x.test
x
x

This is very old, as it's there at least since 2010: https://stackoverflow.com/questions/4437394/package-is-none-when-importing-a-python-module 

I would expect Python 2 and 3 to behave the same.

----------
components: Library (Lib)
messages: 354555
nosy: Yuval S
priority: normal
severity: normal
status: open
title: __package__ is None in __init__.py until an import is used
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38457>
_______________________________________

From report at bugs.python.org  Sat Oct 12 19:07:54 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 12 Oct 2019 23:07:54 +0000
Subject: [issue38282] socketmodule.c: _FORTIFY_SOURCE=2 warning in AF_ALG case
 of getsockaddrarg()
In-Reply-To: <1569460305.42.0.728817437513.issue38282@roundup.psfhosted.org>
Message-ID: <1570921674.08.0.325931849761.issue38282@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

The failures on FreeBSD are:

/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Modules/socketmodule.c:1931:50: error: no member named 'bt_l2' in 'union sock_addr'
            struct sockaddr_l2 *addr = &addrbuf->bt_l2;
                                        ~~~~~~~  ^
/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Modules/socketmodule.c:1950:50: error: no member named 'bt_rc' in 'union sock_addr'
            struct sockaddr_rc *addr = &addrbuf->bt_rc;
                                        ~~~~~~~  ^
/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Modules/socketmodule.c:1967:51: error: no member named 'bt_hci' in 'union sock_addr'
            struct sockaddr_hci *addr = &addrbuf->bt_hci;
                                         ~~~~~~~  ^
3 errors generated.

This is likely due to the fact that those fields are protected by:

typedef union sock_addr {
#ifdef HAVE_BLUETOOTH_BLUETOOTH_H
    struct sockaddr_l2 bt_l2;
    struct sockaddr_rc bt_rc;
    struct sockaddr_sco bt_sco;
    struct sockaddr_hci bt_hci;
#elif defined(MS_WINDOWS)
}

and in those machines HAVE_BLUETOOTH_BLUETOOTH_H is absent.

----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38282>
_______________________________________

From report at bugs.python.org  Sat Oct 12 19:35:56 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 12 Oct 2019 23:35:56 +0000
Subject: [issue38456] Reduce the time test_subprocess takes to complete.
In-Reply-To: <1570915664.41.0.600749429007.issue38456@roundup.psfhosted.org>
Message-ID: <1570923356.52.0.858098976782.issue38456@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:


New changeset 67b93f80c764bca01c81c989d74a99df208bea4d by Gregory P. Smith in branch 'master':
bpo-38456: Use /bin/true in test_subprocess (GH-16736)
https://github.com/python/cpython/commit/67b93f80c764bca01c81c989d74a99df208bea4d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38456>
_______________________________________

From report at bugs.python.org  Sat Oct 12 19:42:13 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Sat, 12 Oct 2019 23:42:13 +0000
Subject: [issue38456] Reduce the time test_subprocess takes to complete.
In-Reply-To: <1570915664.41.0.600749429007.issue38456@roundup.psfhosted.org>
Message-ID: <1570923733.01.0.441687350525.issue38456@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
pull_requests: +16316
pull_request: https://github.com/python/cpython/pull/16737

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38456>
_______________________________________

From report at bugs.python.org  Sat Oct 12 19:54:11 2019
From: report at bugs.python.org (DEVOR BLAKE DANIELS)
Date: Sat, 12 Oct 2019 23:54:11 +0000
Subject: [issue38458] lists
Message-ID: <1570924451.06.0.602805161238.issue38458@roundup.psfhosted.org>


New submission from DEVOR BLAKE DANIELS <dev40573 at gmail.com>:

l=[2,3,4]
p=l
p[0]=5
when I change p[0] to 5,l[0] is also changed to 5. I use slicing to get around this ,but when dealing with lists like s[][],slicing does not work

----------
files: three.py
messages: 354558
nosy: dev40573
priority: normal
severity: normal
status: open
title: lists
type: behavior
Added file: https://bugs.python.org/file48657/three.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38458>
_______________________________________

From report at bugs.python.org  Sat Oct 12 20:19:30 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 00:19:30 +0000
Subject: [issue38282] socketmodule.c: _FORTIFY_SOURCE=2 warning in AF_ALG case
 of getsockaddrarg()
In-Reply-To: <1569460305.42.0.728817437513.issue38282@roundup.psfhosted.org>
Message-ID: <1570925970.82.0.793099366495.issue38282@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16317
pull_request: https://github.com/python/cpython/pull/16738

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38282>
_______________________________________

From report at bugs.python.org  Sat Oct 12 20:24:22 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 13 Oct 2019 00:24:22 +0000
Subject: [issue38457] __package__ is None in __init__.py until an import is
 used
In-Reply-To: <1570916892.54.0.164577302417.issue38457@roundup.psfhosted.org>
Message-ID: <1570926262.36.0.887200736776.issue38457@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38457>
_______________________________________

From report at bugs.python.org  Sat Oct 12 20:34:11 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 00:34:11 +0000
Subject: [issue38282] socketmodule.c: _FORTIFY_SOURCE=2 warning in AF_ALG case
 of getsockaddrarg()
In-Reply-To: <1569460305.42.0.728817437513.issue38282@roundup.psfhosted.org>
Message-ID: <1570926851.78.0.768308972376.issue38282@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

PR 16738 fixes the FreeBSD buildbots by correctly handling the Bluetooth L2CAP socket structure in FreeBSD if only bluetooth.h is available. Check out https://man.cx/ng_btsocket(4) for example for more info in the ng_btsocket protocol for FreeBSD.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38282>
_______________________________________

From report at bugs.python.org  Sat Oct 12 20:41:09 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 00:41:09 +0000
Subject: [issue38458] lists
In-Reply-To: <1570924451.06.0.602805161238.issue38458@roundup.psfhosted.org>
Message-ID: <1570927269.34.0.35998456506.issue38458@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Hi Devor,

This is not a bug in Python but indeed documented behavior. When you do

p=l

you are creating a new reference to the same list ([2,3,4]), so changing one changes the other. If you want to make a copy you can do

p = l.copy()

----------
nosy: +pablogsal
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38458>
_______________________________________

From report at bugs.python.org  Sat Oct 12 20:41:44 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 00:41:44 +0000
Subject: [issue38458] lists
In-Reply-To: <1570924451.06.0.602805161238.issue38458@roundup.psfhosted.org>
Message-ID: <1570927304.07.0.9117266007.issue38458@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy:  -pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38458>
_______________________________________

From report at bugs.python.org  Sat Oct 12 20:44:16 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Sun, 13 Oct 2019 00:44:16 +0000
Subject: [issue38458] lists
In-Reply-To: <1570924451.06.0.602805161238.issue38458@roundup.psfhosted.org>
Message-ID: <1570927456.17.0.430647374722.issue38458@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

This is not a bug, it is part of the design of the language. Assignment in Python does not make a copy of lists, or any other object. In your sample code, p and l are two names for the same list, like "Devor Blake Daniels" and "dev40573" are two names for the same person (you).

You can use slicing to make a copy of the list, or the copy module, or the list constructor.

I don't understand your comment "when dealing with lists like s[][],slicing does not work".

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38458>
_______________________________________

From report at bugs.python.org  Sat Oct 12 20:45:55 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Sun, 13 Oct 2019 00:45:55 +0000
Subject: [issue38458] lists
In-Reply-To: <1570924451.06.0.602805161238.issue38458@roundup.psfhosted.org>
Message-ID: <1570927555.88.0.369899520488.issue38458@roundup.psfhosted.org>


Change by Steven D'Aprano <steve+python at pearwood.info>:


----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38458>
_______________________________________

From report at bugs.python.org  Sat Oct 12 21:03:58 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 01:03:58 +0000
Subject: [issue38282] socketmodule.c: _FORTIFY_SOURCE=2 warning in AF_ALG case
 of getsockaddrarg()
In-Reply-To: <1569460305.42.0.728817437513.issue38282@roundup.psfhosted.org>
Message-ID: <1570928638.02.0.740913259591.issue38282@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 27b33fb41a7c64a6211d73d14804aa0cd6defccb by Pablo Galindo in branch 'master':
bpo-38282: Correctly manage the Bluetooth L2CAP socket structure in FreeBSD (GH-16738)
https://github.com/python/cpython/commit/27b33fb41a7c64a6211d73d14804aa0cd6defccb


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38282>
_______________________________________

From report at bugs.python.org  Sat Oct 12 21:09:52 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 01:09:52 +0000
Subject: [issue38456] Reduce the time test_subprocess takes to complete.
In-Reply-To: <1570915664.41.0.600749429007.issue38456@roundup.psfhosted.org>
Message-ID: <1570928992.06.0.524471419963.issue38456@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16318
pull_request: https://github.com/python/cpython/pull/16739

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38456>
_______________________________________

From report at bugs.python.org  Sat Oct 12 21:40:27 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 01:40:27 +0000
Subject: [issue38456] Reduce the time test_subprocess takes to complete.
In-Reply-To: <1570915664.41.0.600749429007.issue38456@roundup.psfhosted.org>
Message-ID: <1570930827.64.0.840487041081.issue38456@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 46113e0cf32748f66cf64cd633984d143b433cd1 by Pablo Galindo in branch 'master':
bpo-38456: Handle the case when there is no 'true' command (GH-16739)
https://github.com/python/cpython/commit/46113e0cf32748f66cf64cd633984d143b433cd1


----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38456>
_______________________________________

From report at bugs.python.org  Sat Oct 12 23:14:27 2019
From: report at bugs.python.org (Ma Lin)
Date: Sun, 13 Oct 2019 03:14:27 +0000
Subject: [issue38056] Overhaul Error Handlers section in codecs documentation
In-Reply-To: <1567952070.11.0.225789110598.issue38056@roundup.psfhosted.org>
Message-ID: <1570936467.87.0.296982793973.issue38056@roundup.psfhosted.org>


Ma Lin <malincns at 163.com> added the comment:

PR 15732 became an overhaul:

- replace/backslashreplace/surrogateescape were wrongly described as encoding only, in fact they can also be used in decoding.
- clarify the description of surrogatepass.
- add more descriptions to each handler.
- add two REPL examples.
- add indexes for Error Handler's name.
- add default parameter values in codecs.rst
- improve term "text encoding".

PR 15732 has a screenshot of the Error Handlers section.

----------
components: +Unicode
nosy: +ezio.melotti, vstinner
title: Add examples for common text encoding Error Handlers -> Overhaul Error Handlers section in codecs documentation

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38056>
_______________________________________

From report at bugs.python.org  Sat Oct 12 23:46:31 2019
From: report at bugs.python.org (Harmon)
Date: Sun, 13 Oct 2019 03:46:31 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
In-Reply-To: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>
Message-ID: <1570938391.11.0.400144605405.issue38359@roundup.psfhosted.org>


Change by Harmon <Harmon758 at gmail.com>:


----------
nosy: +Harmon758

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Sat Oct 12 23:56:22 2019
From: report at bugs.python.org (Harmon)
Date: Sun, 13 Oct 2019 03:56:22 +0000
Subject: [issue37035] Don't log OSError exceptions in asyncio transports
In-Reply-To: <1558708377.15.0.222546736903.issue37035@roundup.psfhosted.org>
Message-ID: <1570938982.66.0.556934215588.issue37035@roundup.psfhosted.org>


Change by Harmon <Harmon758 at gmail.com>:


----------
nosy: +Harmon758

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37035>
_______________________________________

From report at bugs.python.org  Sun Oct 13 03:18:25 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 13 Oct 2019 07:18:25 +0000
Subject: [issue38440] Possible new issues with IDLE
In-Reply-To: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>
Message-ID: <1570951105.45.0.473684879563.issue38440@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

* Am running 3.8.0rc1 on macOS Mojave 10.14.6.

* My Python is the stock mac 64-build from python.org.

* Started IDLE from a terminal with:
  $ python3.8 -m idlelib.idle

* Yes, the box is "Your program is still running!\nDo you want to kill it?"

* I'm running another course this week and see if I can get more specifics and perhaps a reproducer.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Sun Oct 13 03:25:55 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 13 Oct 2019 07:25:55 +0000
Subject: [issue38440] Possible new issues with IDLE
In-Reply-To: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>
Message-ID: <1570951555.16.0.235587008452.issue38440@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

????

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Sun Oct 13 03:26:03 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 13 Oct 2019 07:26:03 +0000
Subject: [issue38440] Possible new issues with IDLE
In-Reply-To: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>
Message-ID: <1570951563.08.0.206905159242.issue38440@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
Removed message: https://bugs.python.org/msg354566

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Sun Oct 13 03:43:25 2019
From: report at bugs.python.org (Yuval S)
Date: Sun, 13 Oct 2019 07:43:25 +0000
Subject: [issue38457] __package__ is None in __init__.py until an import is
 used
In-Reply-To: <1570916892.54.0.164577302417.issue38457@roundup.psfhosted.org>
Message-ID: <1570952605.61.0.23101230568.issue38457@roundup.psfhosted.org>


Yuval S <sadan.yuval at gmail.com> added the comment:

* It should be python[23] -m x.test, of course.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38457>
_______________________________________

From report at bugs.python.org  Sun Oct 13 04:05:46 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2019 08:05:46 +0000
Subject: [issue38378] os.sendfile() has improperly named parameter
In-Reply-To: <1570287843.24.0.0727618245068.issue38378@roundup.psfhosted.org>
Message-ID: <1570953945.99.0.510792501167.issue38378@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16319
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16742

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38378>
_______________________________________

From report at bugs.python.org  Sun Oct 13 04:31:24 2019
From: report at bugs.python.org (John Lennon)
Date: Sun, 13 Oct 2019 08:31:24 +0000
Subject: [issue38459] typing: Classes that inherit `Generic[...]` indirectly
 aren't considered generic.
Message-ID: <1570955483.97.0.910944150391.issue38459@roundup.psfhosted.org>


New submission from John Lennon <enjigglypuffcx at gmail.com>:

Given the file `example.py` with the following contents:


```python

from typing import Generic, TypeVar

KT = TypeVar("KT")
VT = TypeVar("VT")


class GenericMapping(Generic[KT, VT]):
    pass


class SomeImplMapping(GenericMapping):
    pass


a: GenericMapping[int, float]
b: SomeImplMapping[int, float]
```


I would expect `SomeImplMapping` to be generic as well as `GenericMapping`. However, currently this code fails with the following error:

```sh
Traceback (most recent call last):
  File "adt.py", line 18, in <module>
    b: SomeImplMapping[int, float]
  File "/usr/local/lib/python3.7/typing.py", line 254, in inner
    return func(*args, **kwds)
  File "/usr/local/lib/python3.7/typing.py", line 841, in __class_getitem__
    _check_generic(cls, params)
  File "/usr/local/lib/python3.7/typing.py", line 204, in _check_generic
    raise TypeError(f"{cls} is not a generic class")
TypeError: <class '__main__.SomeImplMapping'> is not a generic class
```


If I understand everything correctly, that's because `typing` doesn't check bases of the class to have `__parameters__` attribute:

https://github.com/python/cpython/blob/master/Lib/typing.py#L210

I did not found the restriction that only direct childs of `Generic[..]` class can be generic in the docs, so I think this is a bug.

----------
components: Library (Lib)
messages: 354568
nosy: John Lennon
priority: normal
severity: normal
status: open
title: typing: Classes that inherit `Generic[...]` indirectly aren't considered generic.
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38459>
_______________________________________

From report at bugs.python.org  Sun Oct 13 04:41:51 2019
From: report at bugs.python.org (John Lennon)
Date: Sun, 13 Oct 2019 08:41:51 +0000
Subject: [issue38459] typing: Classes that inherit `Generic[...]` indirectly
 aren't considered generic.
In-Reply-To: <1570955483.97.0.910944150391.issue38459@roundup.psfhosted.org>
Message-ID: <1570956111.83.0.204301552028.issue38459@roundup.psfhosted.org>


John Lennon <enjigglypuffcx at gmail.com> added the comment:

However, if I change the signature to:

```python

class SomeImplMapping(GenericMapping[KT, VT]):

```

Everything works just fine. And that's not really clear for me: we already have declared the generic types, we can not change the amount of those arguments, so why do we have to pass the same generic parameters again?

And even if that's the designed way to do things, I would expect the first example to fail not because of the type substitution, but for deriving the `GenericMapping` without generic type arguments provided (as if I'll try to derive `Generic` instead of `Generic[...]`).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38459>
_______________________________________

From report at bugs.python.org  Sun Oct 13 04:43:44 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 13 Oct 2019 08:43:44 +0000
Subject: [issue38459] typing: Classes that inherit `Generic[...]` indirectly
 aren't considered generic.
In-Reply-To: <1570955483.97.0.910944150391.issue38459@roundup.psfhosted.org>
Message-ID: <1570956224.29.0.402313258646.issue38459@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +gvanrossum, levkivskyi

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38459>
_______________________________________

From report at bugs.python.org  Sun Oct 13 04:58:18 2019
From: report at bugs.python.org (John Lennon)
Date: Sun, 13 Oct 2019 08:58:18 +0000
Subject: [issue38459] typing: Classes that inherit `Generic[...]` indirectly
 aren't considered generic.
In-Reply-To: <1570955483.97.0.910944150391.issue38459@roundup.psfhosted.org>
Message-ID: <1570957098.93.0.92437162077.issue38459@roundup.psfhosted.org>


John Lennon <enjigglypuffcx at gmail.com> added the comment:

BTW I don't mind creating a PR for that issue if there will be an agreement on what is the desired behavior here.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38459>
_______________________________________

From report at bugs.python.org  Sun Oct 13 04:59:36 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2019 08:59:36 +0000
Subject: [issue38378] os.sendfile() has improperly named parameter
In-Reply-To: <1570287843.24.0.0727618245068.issue38378@roundup.psfhosted.org>
Message-ID: <1570957176.72.0.253894067853.issue38378@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 140a7d1f3579e778656a6b6bfad72489e9870a4d by Serhiy Storchaka in branch 'master':
bpo-38378: Rename parameters "out" and "in" of os.sendfile(). (GH-16742)
https://github.com/python/cpython/commit/140a7d1f3579e778656a6b6bfad72489e9870a4d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38378>
_______________________________________

From report at bugs.python.org  Sun Oct 13 05:01:45 2019
From: report at bugs.python.org (retnikt)
Date: Sun, 13 Oct 2019 09:01:45 +0000
Subject: [issue38397] __init_subclass__ causes TypeError when used with more
 standard library metaclasses (such as EnumMeta)
In-Reply-To: <1570464400.89.0.0085195281122.issue38397@roundup.psfhosted.org>
Message-ID: <1570957305.31.0.513111237422.issue38397@roundup.psfhosted.org>


Change by retnikt <retnikt at gmail.com>:


----------
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38397>
_______________________________________

From report at bugs.python.org  Sun Oct 13 05:18:44 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2019 09:18:44 +0000
Subject: [issue38378] os.sendfile() has improperly named parameter
In-Reply-To: <1570287843.24.0.0727618245068.issue38378@roundup.psfhosted.org>
Message-ID: <1570958324.35.0.664748867894.issue38378@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38378>
_______________________________________

From report at bugs.python.org  Sun Oct 13 06:41:30 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sun, 13 Oct 2019 10:41:30 +0000
Subject: [issue28556] typing.py upgrades
In-Reply-To: <1477756009.46.0.442279756181.issue28556@psf.upfronthosting.co.za>
Message-ID: <1570963290.24.0.496804965545.issue28556@roundup.psfhosted.org>


Change by Ivan Levkivskyi <levkivskyi at gmail.com>:


----------
pull_requests: +16320
pull_request: https://github.com/python/cpython/pull/16743

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28556>
_______________________________________

From report at bugs.python.org  Sun Oct 13 06:43:13 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sun, 13 Oct 2019 10:43:13 +0000
Subject: [issue38459] typing: Classes that inherit `Generic[...]` indirectly
 aren't considered generic.
In-Reply-To: <1570955483.97.0.910944150391.issue38459@roundup.psfhosted.org>
Message-ID: <1570963393.51.0.155590410453.issue38459@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

The docs for typing module are clear about this:
```
Using a generic class without specifying type parameters assumes Any for each position.
```
There is also an example involving a base class.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38459>
_______________________________________

From report at bugs.python.org  Sun Oct 13 07:03:48 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2019 11:03:48 +0000
Subject: [issue28869] __module__ attribute is not set correctly for a class
 created by direct metaclass call
In-Reply-To: <1480885774.84.0.670239959771.issue28869@psf.upfronthosting.co.za>
Message-ID: <1570964628.12.0.740608535085.issue28869@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

PR 14166 now fixes the issue in more generic way. It skips one additional frame when type.__new__ is called not directly from type.__call__.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28869>
_______________________________________

From report at bugs.python.org  Sun Oct 13 07:45:39 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2019 11:45:39 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570967139.53.0.555806680032.issue38431@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 793cb85437299a3da3d74fe65480d720af330cbb by Serhiy Storchaka (Samuel Colvin) in branch 'master':
bpo-38431: Fix __repr__ method of InitVar to work with typing objects. (GH-16702)
https://github.com/python/cpython/commit/793cb85437299a3da3d74fe65480d720af330cbb


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Sun Oct 13 07:45:48 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 13 Oct 2019 11:45:48 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570967148.21.0.5205545062.issue38431@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16321
pull_request: https://github.com/python/cpython/pull/16744

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Sun Oct 13 07:49:08 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2019 11:49:08 +0000
Subject: [issue38202] A fatal error in test_dictviews
In-Reply-To: <1568748421.29.0.795591630213.issue38202@roundup.psfhosted.org>
Message-ID: <1570967348.28.0.881656307495.issue38202@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset b16e382c446d76ede22780b15c75f43c5f132e25 by Serhiy Storchaka (Zackery Spytz) in branch 'master':
bpo-38202: Fix a crash in dict_view & non-itearble. (GH-16241)
https://github.com/python/cpython/commit/b16e382c446d76ede22780b15c75f43c5f132e25


----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38202>
_______________________________________

From report at bugs.python.org  Sun Oct 13 07:52:55 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2019 11:52:55 +0000
Subject: [issue38202] A fatal error in test_dictviews
In-Reply-To: <1568748421.29.0.795591630213.issue38202@roundup.psfhosted.org>
Message-ID: <1570967575.76.0.32876109597.issue38202@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38202>
_______________________________________

From report at bugs.python.org  Sun Oct 13 08:04:08 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 13 Oct 2019 12:04:08 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570968248.03.0.445295875495.issue38431@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 6da52ac411947d1a7958bbad831fcf8dfc8c95fe by Miss Islington (bot) in branch '3.8':
bpo-38431: Fix __repr__ method of InitVar to work with typing objects. (GH-16702)
https://github.com/python/cpython/commit/6da52ac411947d1a7958bbad831fcf8dfc8c95fe


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Sun Oct 13 08:20:54 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Sun, 13 Oct 2019 12:20:54 +0000
Subject: [issue38460] 3.8 Release Notes: document asyncio exception changes
Message-ID: <1570969254.43.0.827620904639.issue38460@roundup.psfhosted.org>


New submission from Sebastian Rittau <srittau at rittau.biz>:

In Python 3.8 asyncio exceptions were consolidated into the new module "asyncio.exceptions". Previously they were spread out over several modules. While the documentation always mandated to import the exceptions from top-level "asyncio", code that incorrectly imported directly from the submodules will break.

----------
assignee: docs at python
components: Documentation
messages: 354577
nosy: docs at python, srittau
priority: normal
severity: normal
status: open
title: 3.8 Release Notes: document asyncio exception changes
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38460>
_______________________________________

From report at bugs.python.org  Sun Oct 13 08:50:54 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2019 12:50:54 +0000
Subject: [issue38431] dataclasses.InitVar breaks with typing.Optional
In-Reply-To: <1570721462.15.0.939525387822.issue38431@roundup.psfhosted.org>
Message-ID: <1570971054.2.0.986353837994.issue38431@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Thank you for your contribution Samuel!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38431>
_______________________________________

From report at bugs.python.org  Sun Oct 13 09:06:44 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Sun, 13 Oct 2019 13:06:44 +0000
Subject: [issue38461] 3.8 Release Notes: "curses" misspelled as "ncurses"
Message-ID: <1570972004.47.0.506267753893.issue38461@roundup.psfhosted.org>


New submission from Sebastian Rittau <srittau at rittau.biz>:

The "curses" module is misspelled and sorted as "ncurses" in the release notes.

----------
messages: 354579
nosy: srittau
priority: normal
severity: normal
status: open
title: 3.8 Release Notes: "curses" misspelled as "ncurses"

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38461>
_______________________________________

From report at bugs.python.org  Sun Oct 13 09:09:19 2019
From: report at bugs.python.org (Joshua Root)
Date: Sun, 13 Oct 2019 13:09:19 +0000
Subject: [issue38014] ./configure on recent macOS versions can fail with
 multiple "present but cannot be compiled" messages
In-Reply-To: <1567477987.66.0.578307493025.issue38014@roundup.psfhosted.org>
Message-ID: <1570972159.96.0.539198369114.issue38014@roundup.psfhosted.org>


Joshua Root <josh+python at root.id.au> added the comment:

The crash reported by BMinas is reputedly related to the -fstack-check option, which is said to be on by default when MACOSX_DEPLOYMENT_TARGET=10.15. I've been unable to confirm whether there was just a bug in the beta, or if it's still a problem on the final Catalina release.

----------
nosy: +jmr

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38014>
_______________________________________

From report at bugs.python.org  Sun Oct 13 09:31:35 2019
From: report at bugs.python.org (Roy Smith)
Date: Sun, 13 Oct 2019 13:31:35 +0000
Subject: [issue38462] Typo (nam ing) in import system docs
Message-ID: <1570973495.13.0.272264963981.issue38462@roundup.psfhosted.org>


New submission from Roy Smith <roy at panix.com>:

In https://docs.python.org/3.5/reference/import.html#importsystem, section "5.2 Packages", second sentence, the word "naming" is broken across two lines.

In 3.7.5rc1 as well.  Didn't check any others.

----------
assignee: docs at python
components: Documentation
messages: 354581
nosy: docs at python, roysmith
priority: normal
severity: normal
status: open
title: Typo (nam ing) in import system docs
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38462>
_______________________________________

From report at bugs.python.org  Sun Oct 13 09:47:22 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Sun, 13 Oct 2019 13:47:22 +0000
Subject: [issue38463] 3.8 Release Notes: Link to
 SSLContext.post_handshake_auth missing
Message-ID: <1570974442.94.0.731112598518.issue38463@roundup.psfhosted.org>


New submission from Sebastian Rittau <srittau at rittau.biz>:

The link to SSLContext.post_handshake_auth in the "ssl" section in the release notes is missing.

----------
assignee: docs at python
components: Documentation
messages: 354582
nosy: docs at python, srittau
priority: normal
severity: normal
status: open
title: 3.8 Release Notes: Link to SSLContext.post_handshake_auth missing
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38463>
_______________________________________

From report at bugs.python.org  Sun Oct 13 10:04:29 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Sun, 13 Oct 2019 14:04:29 +0000
Subject: [issue38462] Typo (nam ing) in import system docs
In-Reply-To: <1570973495.13.0.272264963981.issue38462@roundup.psfhosted.org>
Message-ID: <1570975469.79.0.719081189231.issue38462@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

I'm not seeing this in either the master or 3.5 branches. Perhaps this is being done locally by your browser?

Unfortunately I can't find a way for github to link to a specific line in a .rst file, but when I look at the source code and https://github.com/python/cpython/blob/3.5/Doc/reference/import.rst, I don't see any line breaks.

----------
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38462>
_______________________________________

From report at bugs.python.org  Sun Oct 13 10:20:27 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Sun, 13 Oct 2019 14:20:27 +0000
Subject: [issue38464] documentation for NormalDist.quantiles(): missing
 argument
Message-ID: <1570976427.94.0.852447580797.issue38464@roundup.psfhosted.org>


New submission from Sebastian Rittau <srittau at rittau.biz>:

The documentation for NormalDist.quantiles() (https://docs.python.org/3.8/library/statistics.html#statistics.NormalDist) is missing the "n" argument from the definition.

----------
assignee: docs at python
components: Documentation
messages: 354584
nosy: docs at python, rhettinger, srittau
priority: normal
severity: normal
status: open
title: documentation for NormalDist.quantiles(): missing argument
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38464>
_______________________________________

From report at bugs.python.org  Sun Oct 13 10:27:27 2019
From: report at bugs.python.org (Roy Smith)
Date: Sun, 13 Oct 2019 14:27:27 +0000
Subject: [issue38462] Typo (nam ing) in import system docs
In-Reply-To: <1570973495.13.0.272264963981.issue38462@roundup.psfhosted.org>
Message-ID: <1570976847.0.0.380576940846.issue38462@roundup.psfhosted.org>


Roy Smith <roy at panix.com> added the comment:

Yeah, that's weird.  Looks like this may be a Chrome bug.  I'm seeing it in Chrome (Version 77.0.3865.90 (Official Build) (64-bit)), but not Safari.  This is on MacOS (High Sierra).


In the attached screenshot, I narrowed the window a bit.  In the second paragraph, it's mis-broken "modules" and "contain", but hyphenated some other line breaks.  If I diddle with the CSS and disable "hyphens: auto", it stops breaking words completely (which is probably better than breaking them wrong).

I guess close this and I'll open a bug against Chrome.

----------
Added file: https://bugs.python.org/file48658/Screen Shot 2019-10-13 at 10.12.15 AM.jpg

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38462>
_______________________________________

From report at bugs.python.org  Sun Oct 13 10:57:15 2019
From: report at bugs.python.org (hai shi)
Date: Sun, 13 Oct 2019 14:57:15 +0000
Subject: [issue38465] The type of ob_exports in PyByteArrayObject become
 Py_ssize_t.
Message-ID: <1570978635.87.0.596564542888.issue38465@roundup.psfhosted.org>


New submission from hai shi <shihai1991 at 126.com>:

for a code example:
```
v = []
b = bytearray(0xffff)
for i in range(2**31+1)
    # the ob_exports would be overflow in 32 bit machine when i = 2**31.
    v.append(memoryview(b))
```
IMHO, i thought converting the type of ob_exports to Py_ssize_t is fine.

PS: I have no actual user scenario.

----------
components: Interpreter Core
messages: 354586
nosy: shihai1991
priority: normal
severity: normal
status: open
title: The type of ob_exports in PyByteArrayObject become Py_ssize_t.
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38465>
_______________________________________

From report at bugs.python.org  Sun Oct 13 10:59:28 2019
From: report at bugs.python.org (hai shi)
Date: Sun, 13 Oct 2019 14:59:28 +0000
Subject: [issue38465] The type of ob_exports in PyByteArrayObject become
 Py_ssize_t.
In-Reply-To: <1570978635.87.0.596564542888.issue38465@roundup.psfhosted.org>
Message-ID: <1570978768.78.0.525999569944.issue38465@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
keywords: +patch
pull_requests: +16322
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16746

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38465>
_______________________________________

From report at bugs.python.org  Sun Oct 13 11:03:36 2019
From: report at bugs.python.org (hai shi)
Date: Sun, 13 Oct 2019 15:03:36 +0000
Subject: [issue38465] The type of ob_exports in PyByteArrayObject become
 Py_ssize_t.
In-Reply-To: <1570978635.87.0.596564542888.issue38465@roundup.psfhosted.org>
Message-ID: <1570979016.58.0.426038764343.issue38465@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

sorry, typo error.
# the ob_exports would be overflow in 32 bit machine when i = 2**31.
-->
# the ob_exports would be overflow in 64 bit machine when i = 2**31.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38465>
_______________________________________

From report at bugs.python.org  Sun Oct 13 11:40:26 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Sun, 13 Oct 2019 15:40:26 +0000
Subject: [issue38466] threading.excepthook doc talks about "object"
Message-ID: <1570981226.47.0.762418362865.issue38466@roundup.psfhosted.org>


New submission from Sebastian Rittau <srittau at rittau.biz>:

The documentation of threading.excepthook (https://docs.python.org/3.8/library/threading.html#threading.excepthook) talks about "object", when it only has a "thread" attribute:

"Storing object using a custom hook can resurrect it if it is set to an object which is being finalized. Avoid storing object after the custom hook completes to avoid resurrecting objects."

I believe this is a copy and paste error from sys.unraisablehook.

----------
assignee: docs at python
components: Documentation
messages: 354588
nosy: docs at python, srittau, vstinner
priority: normal
severity: normal
status: open
title: threading.excepthook doc talks about "object"
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38466>
_______________________________________

From report at bugs.python.org  Sun Oct 13 11:49:02 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 15:49:02 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1570981742.77.0.81195110295.issue38379@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 466326dcdf038b948d94302c315be407c73e60d1 by Pablo Galindo in branch 'master':
bpo-38379: Don't block collection of unreachable objects when some objects resurrect (GH-16687)
https://github.com/python/cpython/commit/466326dcdf038b948d94302c315be407c73e60d1


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Sun Oct 13 11:55:39 2019
From: report at bugs.python.org (Ned Deily)
Date: Sun, 13 Oct 2019 15:55:39 +0000
Subject: [issue38463] 3.8 Release Notes: Link to
 SSLContext.post_handshake_auth missing
In-Reply-To: <1570974442.94.0.731112598518.issue38463@roundup.psfhosted.org>
Message-ID: <1570982139.36.0.934446876037.issue38463@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
nosy: +akuchling, rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38463>
_______________________________________

From report at bugs.python.org  Sun Oct 13 11:56:21 2019
From: report at bugs.python.org (Ned Deily)
Date: Sun, 13 Oct 2019 15:56:21 +0000
Subject: [issue38461] 3.8 Release Notes: "curses" misspelled as "ncurses"
In-Reply-To: <1570972004.47.0.506267753893.issue38461@roundup.psfhosted.org>
Message-ID: <1570982181.2.0.239547170849.issue38461@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
nosy: +akuchling, rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38461>
_______________________________________

From report at bugs.python.org  Sun Oct 13 11:58:24 2019
From: report at bugs.python.org (Ned Deily)
Date: Sun, 13 Oct 2019 15:58:24 +0000
Subject: [issue38460] 3.8 Release Notes: document asyncio exception changes
In-Reply-To: <1570969254.43.0.827620904639.issue38460@roundup.psfhosted.org>
Message-ID: <1570982304.88.0.946227259285.issue38460@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
nosy: +akuchling, asvetlov, rhettinger, yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38460>
_______________________________________

From report at bugs.python.org  Sun Oct 13 12:04:33 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Sun, 13 Oct 2019 16:04:33 +0000
Subject: [issue38467] Misspelled argument names for typing.get_origin and
 get_args
Message-ID: <1570982673.75.0.804199303932.issue38467@roundup.psfhosted.org>


New submission from Sebastian Rittau <srittau at rittau.biz>:

The arguments for typing.get_origin() and typing.get_args() are named "typ" in the documentation (https://docs.python.org/3.8/library/typing.html#typing.get_origin), while they are named "tp" in the implementation. Important if used as keyword argument.

----------
assignee: docs at python
components: Documentation
messages: 354590
nosy: docs at python, srittau
priority: normal
severity: normal
status: open
title: Misspelled argument names for typing.get_origin and get_args
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38467>
_______________________________________

From report at bugs.python.org  Sun Oct 13 12:11:27 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Sun, 13 Oct 2019 16:11:27 +0000
Subject: [issue38462] Typo (nam ing) in import system docs
In-Reply-To: <1570973495.13.0.272264963981.issue38462@roundup.psfhosted.org>
Message-ID: <1570983087.68.0.82865017336.issue38462@roundup.psfhosted.org>


Change by Eric V. Smith <eric at trueblade.com>:


----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38462>
_______________________________________

From report at bugs.python.org  Sun Oct 13 12:13:45 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 13 Oct 2019 16:13:45 +0000
Subject: [issue38468] Refactor python-config.in - use getvar()
Message-ID: <1570983225.71.0.166757825145.issue38468@roundup.psfhosted.org>


New submission from Joannah Nanjekye <nanjekyejoannah at gmail.com>:

Use getvar for all still existing sysconfig.get_config_var() calls.

----------
messages: 354591
nosy: nanjekyejoannah
priority: normal
severity: normal
status: open
title: Refactor python-config.in - use getvar()
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38468>
_______________________________________

From report at bugs.python.org  Sun Oct 13 12:16:05 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 13 Oct 2019 16:16:05 +0000
Subject: [issue38468] Refactor python-config.in - use getvar()
In-Reply-To: <1570983225.71.0.166757825145.issue38468@roundup.psfhosted.org>
Message-ID: <1570983365.92.0.812812610324.issue38468@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


----------
keywords: +patch
pull_requests: +16323
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16749

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38468>
_______________________________________

From report at bugs.python.org  Sun Oct 13 12:53:11 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 13 Oct 2019 16:53:11 +0000
Subject: [issue28556] typing.py upgrades
In-Reply-To: <1477756009.46.0.442279756181.issue28556@psf.upfronthosting.co.za>
Message-ID: <1570985591.98.0.870640115887.issue28556@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 8144095707f87bdee6f3e1bbb15283ea61381be6 by Miss Islington (bot) (Ivan Levkivskyi) in branch 'master':
bpo-28556: Remove another mention of metaclass of Generic in typing docs (GH-16743)
https://github.com/python/cpython/commit/8144095707f87bdee6f3e1bbb15283ea61381be6


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28556>
_______________________________________

From report at bugs.python.org  Sun Oct 13 12:53:19 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 13 Oct 2019 16:53:19 +0000
Subject: [issue28556] typing.py upgrades
In-Reply-To: <1477756009.46.0.442279756181.issue28556@psf.upfronthosting.co.za>
Message-ID: <1570985599.47.0.800892657245.issue28556@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16324
pull_request: https://github.com/python/cpython/pull/16750

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28556>
_______________________________________

From report at bugs.python.org  Sun Oct 13 12:53:26 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 13 Oct 2019 16:53:26 +0000
Subject: [issue28556] typing.py upgrades
In-Reply-To: <1477756009.46.0.442279756181.issue28556@psf.upfronthosting.co.za>
Message-ID: <1570985606.73.0.392361346982.issue28556@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16325
pull_request: https://github.com/python/cpython/pull/16751

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28556>
_______________________________________

From report at bugs.python.org  Sun Oct 13 12:59:02 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 13 Oct 2019 16:59:02 +0000
Subject: [issue28556] typing.py upgrades
In-Reply-To: <1477756009.46.0.442279756181.issue28556@psf.upfronthosting.co.za>
Message-ID: <1570985942.97.0.0380821161888.issue28556@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 20d1f49a0008e7c306cbe34dcc1b7d6e62dc3d24 by Miss Islington (bot) in branch '3.7':
bpo-28556: Remove another mention of metaclass of Generic in typing docs (GH-16743)
https://github.com/python/cpython/commit/20d1f49a0008e7c306cbe34dcc1b7d6e62dc3d24


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28556>
_______________________________________

From report at bugs.python.org  Sun Oct 13 13:00:22 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 13 Oct 2019 17:00:22 +0000
Subject: [issue28556] typing.py upgrades
In-Reply-To: <1477756009.46.0.442279756181.issue28556@psf.upfronthosting.co.za>
Message-ID: <1570986022.53.0.741810446164.issue28556@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset e742826531d4369cb1eff65337fa95fd67de8d42 by Miss Islington (bot) in branch '3.8':
bpo-28556: Remove another mention of metaclass of Generic in typing docs (GH-16743)
https://github.com/python/cpython/commit/e742826531d4369cb1eff65337fa95fd67de8d42


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28556>
_______________________________________

From report at bugs.python.org  Sun Oct 13 13:02:01 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 13 Oct 2019 17:02:01 +0000
Subject: [issue38463] 3.8 Release Notes: Link to
 SSLContext.post_handshake_auth missing
In-Reply-To: <1570974442.94.0.731112598518.issue38463@roundup.psfhosted.org>
Message-ID: <1570986121.55.0.648947282678.issue38463@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee: docs at python -> rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38463>
_______________________________________

From report at bugs.python.org  Sun Oct 13 13:02:20 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 13 Oct 2019 17:02:20 +0000
Subject: [issue38461] 3.8 Release Notes: "curses" misspelled as "ncurses"
In-Reply-To: <1570972004.47.0.506267753893.issue38461@roundup.psfhosted.org>
Message-ID: <1570986140.76.0.719204637527.issue38461@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee:  -> rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38461>
_______________________________________

From report at bugs.python.org  Sun Oct 13 13:03:32 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 13 Oct 2019 17:03:32 +0000
Subject: [issue38460] 3.8 Release Notes: document asyncio exception changes
In-Reply-To: <1570969254.43.0.827620904639.issue38460@roundup.psfhosted.org>
Message-ID: <1570986212.81.0.934383855769.issue38460@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Please put all suggestions in a single tracker entry.  Having multiple entries is more of a hindrance than a help.

----------
assignee: docs at python -> rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38460>
_______________________________________

From report at bugs.python.org  Sun Oct 13 13:18:19 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 13 Oct 2019 17:18:19 +0000
Subject: [issue38467] Misspelled argument names for typing.get_origin and
 get_args
In-Reply-To: <1570982673.75.0.804199303932.issue38467@roundup.psfhosted.org>
Message-ID: <1570987099.71.0.154716114215.issue38467@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +levkivskyi

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38467>
_______________________________________

From report at bugs.python.org  Sun Oct 13 14:10:26 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sun, 13 Oct 2019 18:10:26 +0000
Subject: [issue38467] Misspelled argument names for typing.get_origin and
 get_args
In-Reply-To: <1570982673.75.0.804199303932.issue38467@roundup.psfhosted.org>
Message-ID: <1570990226.49.0.241127954062.issue38467@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

I think adjusting the docs would be less disruptive than changing implementation. Would you like to make a PR?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38467>
_______________________________________

From report at bugs.python.org  Sun Oct 13 14:19:14 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Sun, 13 Oct 2019 18:19:14 +0000
Subject: [issue38467] Misspelled argument names for typing.get_origin and
 get_args
In-Reply-To: <1570982673.75.0.804199303932.issue38467@roundup.psfhosted.org>
Message-ID: <1570990754.14.0.291991460246.issue38467@roundup.psfhosted.org>


Change by Sebastian Rittau <srittau at rittau.biz>:


----------
keywords: +patch
pull_requests: +16326
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16753

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38467>
_______________________________________

From report at bugs.python.org  Sun Oct 13 14:20:11 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Sun, 13 Oct 2019 18:20:11 +0000
Subject: [issue38467] Misspelled argument names for typing.get_origin and
 get_args
In-Reply-To: <1570982673.75.0.804199303932.issue38467@roundup.psfhosted.org>
Message-ID: <1570990811.62.0.63026664182.issue38467@roundup.psfhosted.org>


Sebastian Rittau <srittau at rittau.biz> added the comment:

https://github.com/python/cpython/pull/16753

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38467>
_______________________________________

From report at bugs.python.org  Sun Oct 13 14:27:47 2019
From: report at bugs.python.org (Ned Deily)
Date: Sun, 13 Oct 2019 18:27:47 +0000
Subject: [issue38014] ./configure on recent macOS versions can fail with
 multiple "present but cannot be compiled" messages
In-Reply-To: <1567477987.66.0.578307493025.issue38014@roundup.psfhosted.org>
Message-ID: <1570991267.49.0.298746832112.issue38014@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Thanks for the input, @jmr!  I realize that what I wrote was ambiguous so to clarify I *have* tested that example with the final release versions of Catalina and Xcode 11.1 and could not reproduce.  Just for fun, I've also tested with the latest developer previews of 10.15.1 and 11.2 with and without adding -fstack-check via 'OPT=' again without failure.  (Not being familiar with the stack-check option, I don't know if just adding it to the compiler command lines is sufficient.)  So if anyone *can* reproduce with current releases, please open a new issue about it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38014>
_______________________________________

From report at bugs.python.org  Sun Oct 13 14:31:39 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sun, 13 Oct 2019 18:31:39 +0000
Subject: [issue38467] Misspelled argument names for typing.get_origin and
 get_args
In-Reply-To: <1570982673.75.0.804199303932.issue38467@roundup.psfhosted.org>
Message-ID: <1570991499.05.0.850295100896.issue38467@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:


New changeset fdfe2833ace93021278fe4c41c40e1d08d70abf9 by Ivan Levkivskyi (Sebastian Rittau) in branch 'master':
bpo-38467: Fix argument name of typing functions (GH-16753)
https://github.com/python/cpython/commit/fdfe2833ace93021278fe4c41c40e1d08d70abf9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38467>
_______________________________________

From report at bugs.python.org  Sun Oct 13 14:31:47 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 13 Oct 2019 18:31:47 +0000
Subject: [issue38467] Misspelled argument names for typing.get_origin and
 get_args
In-Reply-To: <1570982673.75.0.804199303932.issue38467@roundup.psfhosted.org>
Message-ID: <1570991507.2.0.543700425688.issue38467@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16327
pull_request: https://github.com/python/cpython/pull/16754

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38467>
_______________________________________

From report at bugs.python.org  Sun Oct 13 14:38:48 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 13 Oct 2019 18:38:48 +0000
Subject: [issue38467] Misspelled argument names for typing.get_origin and
 get_args
In-Reply-To: <1570982673.75.0.804199303932.issue38467@roundup.psfhosted.org>
Message-ID: <1570991928.32.0.431683459885.issue38467@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset c732660b7b18352ba8524ac78d39975afe4392ef by Miss Islington (bot) in branch '3.8':
bpo-38467: Fix argument name of typing functions (GH-16753)
https://github.com/python/cpython/commit/c732660b7b18352ba8524ac78d39975afe4392ef


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38467>
_______________________________________

From report at bugs.python.org  Sun Oct 13 14:47:25 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sun, 13 Oct 2019 18:47:25 +0000
Subject: [issue38467] Misspelled argument names for typing.get_origin and
 get_args
In-Reply-To: <1570982673.75.0.804199303932.issue38467@roundup.psfhosted.org>
Message-ID: <1570992445.55.0.57113763266.issue38467@roundup.psfhosted.org>


Change by Ivan Levkivskyi <levkivskyi at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38467>
_______________________________________

From report at bugs.python.org  Sun Oct 13 16:54:11 2019
From: report at bugs.python.org (Pierre Quentel)
Date: Sun, 13 Oct 2019 20:54:11 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
Message-ID: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>


New submission from Pierre Quentel <pierre.quentel at gmail.com>:

PEP 572 says that "an assignment expression occurring in a (...) comprehension (...) binds the target in the containing scope, honoring a nonlocal or global declaration for the target in that scope, if one exists."

In Appendix B, the PEP shows this example :

def f():
    global TARGET
    a = [TARGET := EXPR for VAR in ITERABLE]

So I don't understand why this fails:

Python 3.8.0rc1 (tags/v3.8.0rc1:34214de, Oct  1 2019, 18:42:37) [MSC v.1916 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> x = 0
>>> def f():
...     global x
...     [x := i for i in range(5)]
...
  File "<stdin>", line 3
SyntaxError: no binding for nonlocal 'x' found
>>>

Is this a bug or am I missing something ?

----------
components: Interpreter Core
messages: 354601
nosy: quentel
priority: normal
severity: normal
status: open
title: PEP 572 : assignment expression to a global variable in a comprehension
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Sun Oct 13 17:19:17 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Sun, 13 Oct 2019 21:19:17 +0000
Subject: [issue38410] Possible fatal errors due to
 _PyEval_SetAsyncGen{Finalizer, Firstiter}()
In-Reply-To: <1570543574.99.0.942798410146.issue38410@roundup.psfhosted.org>
Message-ID: <1571001557.23.0.601751459163.issue38410@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:

Unfortunately at this point we will have to leave the ABI as is. We are in fact promising to lock it by Beta 3 so quite a long time ago.

----------
versions:  -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38410>
_______________________________________

From report at bugs.python.org  Sun Oct 13 17:30:54 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 21:30:54 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571002254.58.0.557692552221.issue38469@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy: +emilyemorehouse, gvanrossum, ncoghlan, pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Sun Oct 13 17:58:18 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 21:58:18 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571003898.86.0.405989077454.issue38469@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I think this is a bug in the symtable_extend_namedexpr_scope function because when visiting the stack in reverse order and finding a function block is always assigning the scope as DEF_NONLOCAL.

Marking also as a release blocker unless Nick, Guido or Emily confirm otherwise.

----------
nosy: +lukasz.langa
priority: normal -> release blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Sun Oct 13 17:58:22 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 21:58:22 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571003902.57.0.848868285073.issue38469@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Sun Oct 13 18:07:00 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Sun, 13 Oct 2019 22:07:00 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571004420.56.0.513495732966.issue38469@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

It's a bug, but it's honestly such an odd corner case that I don't think this should hold up the 3.8.0 release. Let's fix it in 3.9 and backport it to 3.8.1.

----------
priority: release blocker -> normal
stage:  -> needs patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Sun Oct 13 18:17:33 2019
From: report at bugs.python.org (Tim Peters)
Date: Sun, 13 Oct 2019 22:17:33 +0000
Subject: [issue38379] finalizer resurrection in gc
In-Reply-To: <1570296686.13.0.00730737596554.issue38379@roundup.psfhosted.org>
Message-ID: <1571005053.45.0.316725424517.issue38379@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

Everything here has been addressed, so closing this.  zleak.py can apparently run forever now without leaking a byte :-)

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38379>
_______________________________________

From report at bugs.python.org  Sun Oct 13 18:20:03 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 22:20:03 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571005203.64.0.12040069124.issue38469@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I am working on a fix now, se we can merge it before the final release

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Sun Oct 13 18:27:16 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Sun, 13 Oct 2019 22:27:16 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571005636.9.0.220796121929.issue38469@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

Thanks for working on a fix. But is it really important enough to violate the desired "rc1 == release" invariant? It's up to the release manager.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Sun Oct 13 18:40:12 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 22:40:12 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571006412.02.0.693009620036.issue38469@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +patch
pull_requests: +16328
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16755

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Sun Oct 13 18:44:21 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 13 Oct 2019 22:44:21 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571006661.2.0.401144392905.issue38469@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

> But is it really important enough to violate the desired "rc1 == release" invariant?

I created the fix because many other bug fixes have been merged since rc1 already so apologies if it seemed a bit precipitate. Let's see what the release manager thinks (in case the bugfix is correct) :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Sun Oct 13 20:16:45 2019
From: report at bugs.python.org (Daniel Hillier)
Date: Mon, 14 Oct 2019 00:16:45 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1571012205.91.0.501636465123.issue38334@roundup.psfhosted.org>


Change by Daniel Hillier <daniel.hillier at gmail.com>:


----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sun Oct 13 20:45:36 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 14 Oct 2019 00:45:36 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
Message-ID: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>


New submission from Pablo Galindo Salgado <pablogsal at gmail.com>:

This buildbot has been failing for a long time (example failure https://buildbot.python.org/all/#/builders/40/builds/3291) since https://github.com/python/cpython/commit/4267c989e7fc6cd528e8a1d04a07fac5cca85ec7:

======================================================================
FAIL: test_compile_dir_maxlevels (test.test_compileall.CompileallTestsWithSourceEpoch)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\test_py_compile.py", line 30, in wrapper
    return fxn(*args, **kwargs)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\test_compileall.py", line 257, in test_compile_dir_maxlevels
    self.assertTrue(os.path.isfile(self.bc_path_long))
AssertionError: False is not true
======================================================================
FAIL: test_compile_dir_maxlevels (test.test_compileall.CompileallTestsWithoutSourceEpoch)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\test_py_compile.py", line 20, in wrapper
    return fxn(*args, **kwargs)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\test_compileall.py", line 257, in test_compile_dir_maxlevels
    self.assertTrue(os.path.isfile(self.bc_path_long))
AssertionError: False is not true
----------------------------------------------------------------------


Can someone try to fix the error, otherwise we would  need to revert commit 4267c989e7fc6cd528e8a1d04a07fac5cca85ec7.

----------
components: Tests, Windows
messages: 354609
nosy: hroncok, pablogsal, paul.moore, petr.viktorin, steve.dower, tim.golden, vstinner, zach.ware
priority: normal
severity: normal
status: open
title: test_compileall fails in AMD64 Windows7 SP1 3.x
type: behavior
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Sun Oct 13 20:46:40 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 14 Oct 2019 00:46:40 +0000
Subject: [issue38112] Compileall improvements
In-Reply-To: <1568210479.53.0.901531773072.issue38112@roundup.psfhosted.org>
Message-ID: <1571014000.69.0.685016792013.issue38112@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

The AMD64 Windows7 SP1 3.x buildbot has been failing for a while since commit 4267c989e7fc6cd528e8a1d04a07fac5cca85ec7, please take a look at https://bugs.python.org/issue38470.

----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38112>
_______________________________________

From report at bugs.python.org  Sun Oct 13 20:59:37 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 00:59:37 +0000
Subject: [issue38464] documentation for NormalDist.quantiles(): missing
 argument
In-Reply-To: <1570976427.94.0.852447580797.issue38464@roundup.psfhosted.org>
Message-ID: <1571014777.97.0.270738665362.issue38464@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Thanks for noticing.. Will get that fixed up shortly.

----------
assignee: docs at python -> rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38464>
_______________________________________

From report at bugs.python.org  Sun Oct 13 22:46:02 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 02:46:02 +0000
Subject: [issue38464] documentation for NormalDist.quantiles(): missing
 argument
In-Reply-To: <1570976427.94.0.852447580797.issue38464@roundup.psfhosted.org>
Message-ID: <1571021162.87.0.11169410049.issue38464@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
keywords: +patch
pull_requests: +16329
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16757

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38464>
_______________________________________

From report at bugs.python.org  Sun Oct 13 22:53:33 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 02:53:33 +0000
Subject: [issue38464] documentation for NormalDist.quantiles(): missing
 argument
In-Reply-To: <1570976427.94.0.852447580797.issue38464@roundup.psfhosted.org>
Message-ID: <1571021613.67.0.575047874944.issue38464@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset 8a6cbf8adb68aa2c43a48769af92e50d5ca1539d by Raymond Hettinger in branch 'master':
bpo-38464: Document parameter for NormalDist.quantiles() (GH-16757)
https://github.com/python/cpython/commit/8a6cbf8adb68aa2c43a48769af92e50d5ca1539d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38464>
_______________________________________

From report at bugs.python.org  Sun Oct 13 22:54:13 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 Oct 2019 02:54:13 +0000
Subject: [issue38464] documentation for NormalDist.quantiles(): missing
 argument
In-Reply-To: <1570976427.94.0.852447580797.issue38464@roundup.psfhosted.org>
Message-ID: <1571021653.59.0.463920145291.issue38464@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16330
pull_request: https://github.com/python/cpython/pull/16758

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38464>
_______________________________________

From report at bugs.python.org  Sun Oct 13 23:04:32 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 03:04:32 +0000
Subject: [issue38464] documentation for NormalDist.quantiles(): missing
 argument
In-Reply-To: <1570976427.94.0.852447580797.issue38464@roundup.psfhosted.org>
Message-ID: <1571022272.15.0.0346815774006.issue38464@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset 36f62860f631acefd7988b76901863339ffa26c9 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-38464: Document parameter for NormalDist.quantiles() (GH-16757) (GH-16758)
https://github.com/python/cpython/commit/36f62860f631acefd7988b76901863339ffa26c9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38464>
_______________________________________

From report at bugs.python.org  Sun Oct 13 23:04:57 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 03:04:57 +0000
Subject: [issue38464] documentation for NormalDist.quantiles(): missing
 argument
In-Reply-To: <1570976427.94.0.852447580797.issue38464@roundup.psfhosted.org>
Message-ID: <1571022297.19.0.134151023769.issue38464@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38464>
_______________________________________

From report at bugs.python.org  Sun Oct 13 23:56:13 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 03:56:13 +0000
Subject: [issue38460] 3.8 Release Notes: document asyncio exception changes
In-Reply-To: <1570969254.43.0.827620904639.issue38460@roundup.psfhosted.org>
Message-ID: <1571025373.02.0.619598860133.issue38460@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
Removed message: https://bugs.python.org/msg354595

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38460>
_______________________________________

From report at bugs.python.org  Sun Oct 13 23:57:02 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 03:57:02 +0000
Subject: [issue38460] 3.8 Release Notes: document asyncio exception changes
In-Reply-To: <1570969254.43.0.827620904639.issue38460@roundup.psfhosted.org>
Message-ID: <1571025422.35.0.689453597671.issue38460@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Yuri, would you propose an entry for this?

----------
assignee: rhettinger -> yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38460>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:18:07 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 14 Oct 2019 04:18:07 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571026687.96.0.112117968899.issue38469@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset fd5c414880b2e05720b9cf14ab0b0d7ae2b7d925 by Pablo Galindo in branch 'master':
bpo-38469: Handle named expression scope with global/nonlocal keywords (GH-16755)
https://github.com/python/cpython/commit/fd5c414880b2e05720b9cf14ab0b0d7ae2b7d925


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:18:20 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 Oct 2019 04:18:20 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571026700.04.0.10277313022.issue38469@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16331
pull_request: https://github.com/python/cpython/pull/16760

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:20:05 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 04:20:05 +0000
Subject: [issue38461] 3.8 Release Notes: "curses" misspelled as "ncurses"
In-Reply-To: <1570972004.47.0.506267753893.issue38461@roundup.psfhosted.org>
Message-ID: <1571026805.45.0.918070940347.issue38461@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
keywords: +patch
pull_requests: +16332
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16761

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38461>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:20:05 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 04:20:05 +0000
Subject: [issue38463] 3.8 Release Notes: Link to
 SSLContext.post_handshake_auth missing
In-Reply-To: <1570974442.94.0.731112598518.issue38463@roundup.psfhosted.org>
Message-ID: <1571026805.72.0.44541699377.issue38463@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
keywords: +patch
pull_requests: +16333
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16761

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38463>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:31:15 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 04:31:15 +0000
Subject: [issue38463] 3.8 Release Notes: Link to
 SSLContext.post_handshake_auth missing
In-Reply-To: <1570974442.94.0.731112598518.issue38463@roundup.psfhosted.org>
Message-ID: <1571027475.92.0.303830117631.issue38463@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset 61a6db5e79921b89b9e2a154990f01f5f3150213 by Raymond Hettinger in branch 'master':
bpo-38461 and bpo-38463: Minor fixes to Whatsnew 3.8 (GH-16761)
https://github.com/python/cpython/commit/61a6db5e79921b89b9e2a154990f01f5f3150213


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38463>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:31:15 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 04:31:15 +0000
Subject: [issue38461] 3.8 Release Notes: "curses" misspelled as "ncurses"
In-Reply-To: <1570972004.47.0.506267753893.issue38461@roundup.psfhosted.org>
Message-ID: <1571027475.73.0.340839812806.issue38461@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset 61a6db5e79921b89b9e2a154990f01f5f3150213 by Raymond Hettinger in branch 'master':
bpo-38461 and bpo-38463: Minor fixes to Whatsnew 3.8 (GH-16761)
https://github.com/python/cpython/commit/61a6db5e79921b89b9e2a154990f01f5f3150213


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38461>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:31:24 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 Oct 2019 04:31:24 +0000
Subject: [issue38461] 3.8 Release Notes: "curses" misspelled as "ncurses"
In-Reply-To: <1570972004.47.0.506267753893.issue38461@roundup.psfhosted.org>
Message-ID: <1571027484.0.0.232331853564.issue38461@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16334
pull_request: https://github.com/python/cpython/pull/16762

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38461>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:31:24 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 Oct 2019 04:31:24 +0000
Subject: [issue38463] 3.8 Release Notes: Link to
 SSLContext.post_handshake_auth missing
In-Reply-To: <1570974442.94.0.731112598518.issue38463@roundup.psfhosted.org>
Message-ID: <1571027484.09.0.0120203959769.issue38463@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16335
pull_request: https://github.com/python/cpython/pull/16762

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38463>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:54:12 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 04:54:12 +0000
Subject: [issue38463] 3.8 Release Notes: Link to
 SSLContext.post_handshake_auth missing
In-Reply-To: <1570974442.94.0.731112598518.issue38463@roundup.psfhosted.org>
Message-ID: <1571028852.64.0.884861014414.issue38463@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset c09379bd6ebdd896547008c641e8899a1e36aa42 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-38461 and bpo-38463: Minor fixes to Whatsnew 3.8 (GH-16761) (GH-16762)
https://github.com/python/cpython/commit/c09379bd6ebdd896547008c641e8899a1e36aa42


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38463>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:54:12 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 04:54:12 +0000
Subject: [issue38461] 3.8 Release Notes: "curses" misspelled as "ncurses"
In-Reply-To: <1570972004.47.0.506267753893.issue38461@roundup.psfhosted.org>
Message-ID: <1571028852.51.0.587140381258.issue38461@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset c09379bd6ebdd896547008c641e8899a1e36aa42 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-38461 and bpo-38463: Minor fixes to Whatsnew 3.8 (GH-16761) (GH-16762)
https://github.com/python/cpython/commit/c09379bd6ebdd896547008c641e8899a1e36aa42


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38461>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:54:49 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 04:54:49 +0000
Subject: [issue38463] 3.8 Release Notes: Link to
 SSLContext.post_handshake_auth missing
In-Reply-To: <1570974442.94.0.731112598518.issue38463@roundup.psfhosted.org>
Message-ID: <1571028889.43.0.589464917272.issue38463@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38463>
_______________________________________

From report at bugs.python.org  Mon Oct 14 00:59:25 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 04:59:25 +0000
Subject: [issue38461] 3.8 Release Notes: "curses" misspelled as "ncurses"
In-Reply-To: <1570972004.47.0.506267753893.issue38461@roundup.psfhosted.org>
Message-ID: <1571029165.11.0.256599227512.issue38461@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38461>
_______________________________________

From report at bugs.python.org  Mon Oct 14 02:18:55 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 06:18:55 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571033935.87.0.632800683851.issue37759@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
pull_requests: +16336
pull_request: https://github.com/python/cpython/pull/16763

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 02:32:09 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 06:32:09 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571034729.08.0.090785955562.issue37759@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset a3291531ea51455cfa5989119db496267425323c by Raymond Hettinger in branch 'master':
bpo-37759: Add examples for the new typing features (GH-16763)
https://github.com/python/cpython/commit/a3291531ea51455cfa5989119db496267425323c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 02:32:15 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 Oct 2019 06:32:15 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571034735.97.0.0688970667539.issue37759@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16337
pull_request: https://github.com/python/cpython/pull/16764

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 02:45:50 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 06:45:50 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571035550.48.0.542345846235.issue37759@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset 3ac152948d63f52267d312be33306067d3847e2a by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-37759: Add examples for the new typing features (GH-16763) (GH-16764)
https://github.com/python/cpython/commit/3ac152948d63f52267d312be33306067d3847e2a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 04:34:02 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 14 Oct 2019 08:34:02 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571042042.42.0.395876924776.issue37759@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16338
pull_request: https://github.com/python/cpython/pull/16769

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 05:06:10 2019
From: report at bugs.python.org (Paul Martin)
Date: Mon, 14 Oct 2019 09:06:10 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571043970.02.0.861887251219.issue37759@roundup.psfhosted.org>


Paul Martin <greatestloginnameever at gmail.com> added the comment:

Should singledispatchmethod and cached_property be added?

----------
nosy: +primal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 05:51:29 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 09:51:29 +0000
Subject: [issue38282] socketmodule.c: _FORTIFY_SOURCE=2 warning in AF_ALG case
 of getsockaddrarg()
In-Reply-To: <1569460305.42.0.728817437513.issue38282@roundup.psfhosted.org>
Message-ID: <1571046689.32.0.7932630657.issue38282@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I close the issue.

I planned to backport the change to 3.8, but 3.8.0 final is supposed to be released today. I prefer to avoid putting a last minute regression on some platforms like DragonflyBSD in 3.8. Backporting the change is not strictly required, it's just a compiler warning, it's a false alarm, and it's only when building with _FORTIFY_SOURCE defined.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38282>
_______________________________________

From report at bugs.python.org  Mon Oct 14 06:13:57 2019
From: report at bugs.python.org (Tal Einat)
Date: Mon, 14 Oct 2019 10:13:57 +0000
Subject: [issue32498] urllib.parse.unquote raises incorrect errormessage when
 string parameter is bytes
In-Reply-To: <1515179710.49.0.467229070634.issue32498@psf.upfronthosting.co.za>
Message-ID: <1571048037.48.0.770692722897.issue32498@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
versions: +Python 3.9 -Python 3.4, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32498>
_______________________________________

From report at bugs.python.org  Mon Oct 14 06:27:18 2019
From: report at bugs.python.org (Tal Einat)
Date: Mon, 14 Oct 2019 10:27:18 +0000
Subject: [issue32498] urllib.parse.unquote raises incorrect errormessage when
 string parameter is bytes
In-Reply-To: <1515179710.49.0.467229070634.issue32498@psf.upfronthosting.co.za>
Message-ID: <1571048838.76.0.448675662376.issue32498@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

So urllib.parse.unquote() will accept bytes in addition to str starting with 3.9.

The unclear exception remains in prior versions. Would someone like to add a better exception for 3.7 and 3.8?

(I'm marking this as "newcomer friendly", referring only to improving the exception for 3.7 and 3.8.)

----------
keywords: +newcomer friendly
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32498>
_______________________________________

From report at bugs.python.org  Mon Oct 14 06:36:33 2019
From: report at bugs.python.org (Tal Einat)
Date: Mon, 14 Oct 2019 10:36:33 +0000
Subject: [issue32498] urllib.parse.unquote raises incorrect errormessage when
 string parameter is bytes
In-Reply-To: <1515179710.49.0.467229070634.issue32498@psf.upfronthosting.co.za>
Message-ID: <1571049393.09.0.193250554455.issue32498@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset aad2ee01561f260c69af1951c0d6fcaf75c4d41b by Tal Einat (Stein Karlsen) in branch 'master':
bpo-32498: urllib.parse.unquote also accepts bytes (GH-7768)
https://github.com/python/cpython/commit/aad2ee01561f260c69af1951c0d6fcaf75c4d41b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32498>
_______________________________________

From report at bugs.python.org  Mon Oct 14 06:42:35 2019
From: report at bugs.python.org (Paul Martin)
Date: Mon, 14 Oct 2019 10:42:35 +0000
Subject: [issue38471] _ProactorDatagramTransport: If close() is called when
 write buffer is not empty,
 the remaining data is not sent and connection_lost is not called
Message-ID: <1571049755.46.0.456741846567.issue38471@roundup.psfhosted.org>


New submission from Paul Martin <greatestloginnameever at gmail.com>:

Expected behaviour for DatagramTransport (from_SelectorDatagramTransport):

transport.close() called.
If there is data in the write buffer, don't call connection_lost.
When all data is written and the buffer is empty, check if connection has been lost and if so, call connection_lost

However for _ProactorDatagramTransport, if close is called with data in the buffer, _loop_writing returns immediately, so it never gets to the point of sending the remaining data or calling connection_lost. The code for calling connection_lost inside _loop_writing is completely unreachable, because the method immediately returns if the connection has been lost.

----------
components: Windows, asyncio
messages: 354626
nosy: asvetlov, paul.moore, primal, steve.dower, tim.golden, yselivanov, zach.ware
priority: normal
severity: normal
status: open
title: _ProactorDatagramTransport: If close() is called when write buffer is not empty, the remaining data is not sent and connection_lost is not called
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38471>
_______________________________________

From report at bugs.python.org  Mon Oct 14 06:42:49 2019
From: report at bugs.python.org (Paul Martin)
Date: Mon, 14 Oct 2019 10:42:49 +0000
Subject: [issue38471] _ProactorDatagramTransport: If close() is called when
 write buffer is not empty,
 the remaining data is not sent and connection_lost is not called
In-Reply-To: <1571049755.46.0.456741846567.issue38471@roundup.psfhosted.org>
Message-ID: <1571049769.74.0.758793920138.issue38471@roundup.psfhosted.org>


Change by Paul Martin <greatestloginnameever at gmail.com>:


----------
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38471>
_______________________________________

From report at bugs.python.org  Mon Oct 14 07:32:09 2019
From: report at bugs.python.org (Petr Viktorin)
Date: Mon, 14 Oct 2019 11:32:09 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571052729.12.0.0313162884213.issue38470@roundup.psfhosted.org>


Petr Viktorin <encukou at gmail.com> added the comment:

Oh! Sorry, I thought I saw green bots, and haven't looked since.
I should have time for this tomorrow.
If that's too late, remove/skip test_compile_dir_maxlevels on Windows. (The feature was untested before, and the 3.9 enhancement added test coverage, so I think it's fair to skip the failing test.)
I don't think simply reverting 4267c989e7fc6cd528e8a1d04a07fac5cca85ec7 will fix the bots.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 07:40:18 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Mon, 14 Oct 2019 11:40:18 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571053218.48.0.230004614621.issue38469@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:


New changeset 927f07c816aad9f8ed961d7ace6a367837f7fa8f by ?ukasz Langa (Miss Islington (bot)) in branch '3.8':
bpo-38469: Handle named expression scope with global/nonlocal keywords (GH-16755) (#16760)
https://github.com/python/cpython/commit/927f07c816aad9f8ed961d7ace6a367837f7fa8f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Mon Oct 14 08:28:35 2019
From: report at bugs.python.org (Alex Grund)
Date: Mon, 14 Oct 2019 12:28:35 +0000
Subject: [issue38472] GCC detection in setup.py is broken
Message-ID: <1571056115.0.0.505317698716.issue38472@roundup.psfhosted.org>


New submission from Alex Grund <flamefire89 at gmail.com>:

`setup.py` runs `<CC> -E -v - </dev/null 1>/dev/null` to figure out include and library paths from the compiler in the function `add_gcc_paths`.

However sample output from the compiler is:

Es werden eingebaute Spezifikationen verwendet.
COLLECT_GCC=g++
Ziel: x86_64-pc-linux-gnu
Konfiguriert mit: ../configure --enable-languages=c,c++,fortran --enable-lto --enable-checking=release --disable-multilib --enable-shared=yes --enable-static=yes --enable-threads=posix --enable-plugins --enable-gold=default --enable-ld --with-plugin-ld=ld.gold --prefix=/sw/installed/GCCcore/9.1.0 --with-local-prefix=/sw/installed/GCCcore/9.1.0 --enable-bootstrap --with-isl=/dev/shm/easybuild-build/GCCcore/9.1.0/dummy-/gcc-9.1.0/stage2_stuff
Thread-Modell: posix
gcc-Version 9.1.0 (GCC) 
COLLECT_GCC_OPTIONS='-E' '-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
 /software/haswell/GCCcore/9.1.0/bin/../libexec/gcc/x86_64-pc-linux-gnu/9.1.0/cc1 -E -quiet -v -iprefix /software/haswell/GCCcore/9.1.0/bin/../lib/gcc/x86_64-pc-linux-gnu/9.1.0/ - -mtune=generic -march=x86-64
nicht vorhandenes Verzeichnis ?/software/haswell/GCCcore/9.1.0/bin/../lib/gcc/x86_64-pc-linux-gnu/9.1.0/../../../../x86_64-pc-linux-gnu/include? wird ignoriert
doppeltes Verzeichnis ?/software/haswell/GCCcore/9.1.0/bin/../lib/gcc/../../lib/gcc/x86_64-pc-linux-gnu/9.1.0/include? wird ignoriert
doppeltes Verzeichnis ?/software/haswell/GCCcore/9.1.0/bin/../lib/gcc/../../lib/gcc/x86_64-pc-linux-gnu/9.1.0/include-fixed? wird ignoriert
nicht vorhandenes Verzeichnis ?/software/haswell/GCCcore/9.1.0/bin/../lib/gcc/../../lib/gcc/x86_64-pc-linux-gnu/9.1.0/../../../../x86_64-pc-linux-gnu/include? wird ignoriert
doppeltes Verzeichnis ?/sw/installed/GCCcore/9.1.0/include? wird ignoriert
  da es ein Nicht-Systemverzeichnis ist, das ein Systemverzeichnis dupliziert
Suche f?r ?#include "..."? beginnt hier:
Suche f?r ?#include <...>? beginnt hier:
 /sw/installed/binutils/2.32-GCCcore-9.1.0/include
 /sw/installed/zlib/1.2.11-GCCcore-9.1.0/include
 /software/haswell/GCCcore/9.1.0/bin/../lib/gcc/x86_64-pc-linux-gnu/9.1.0/include
 /software/haswell/GCCcore/9.1.0/bin/../lib/gcc/x86_64-pc-linux-gnu/9.1.0/include-fixed
 /sw/installed/GCCcore/9.1.0/include
 /usr/include
Ende der Suchliste.
COMPILER_PATH=/software/haswell/GCCcore/9.1.0/bin/../libexec/gcc/x86_64-pc-linux-gnu/9.1.0/:/software/haswell/GCCcore/9.1.0/bin/../libexec/gcc/
LIBRARY_PATH=/software/haswell/GCCcore/9.1.0/bin/../lib/gcc/x86_64-pc-linux-gnu/9.1.0/:/software/haswell/GCCcore/9.1.0/bin/../lib/gcc/:/sw/installed/GCCcore/9.1.0/lib64/../lib64/:/sw/installed/GCCcore/9.1.0/lib/../lib64/:/software/haswell/GCCcore/9.1.0/bin/../lib/gcc/x86_64-pc-linux-gnu/9.1.0/../../../../lib64/:/lib/../lib64/:/usr/lib/../lib64/:/sw/installed/binutils/2.32-GCCcore-9.1.0/lib/:/sw/installed/zlib/1.2.11-GCCcore-9.1.0/lib/:/sw/installed/GCCcore/9.1.0/lib64/:/sw/installed/GCCcore/9.1.0/lib/:/software/haswell/GCCcore/9.1.0/bin/../lib/gcc/x86_64-pc-linux-gnu/9.1.0/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-E' '-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'


So the correct matcher would be "gcc-Version", maybe in addition to "gcc version"

Due to this the setup fails to build e.g. bzip2 modules as the include and lib paths are passed in via CPATH and LIBRARY_PATH only (module system on HPC system)

----------
components: Build
messages: 354629
nosy: Alex Grund
priority: normal
severity: normal
status: open
title: GCC detection in setup.py is broken
type: compile error
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38472>
_______________________________________

From report at bugs.python.org  Mon Oct 14 08:30:28 2019
From: report at bugs.python.org (Ned Deily)
Date: Mon, 14 Oct 2019 12:30:28 +0000
Subject: [issue38472] GCC detection in setup.py is broken
In-Reply-To: <1571056115.0.0.505317698716.issue38472@roundup.psfhosted.org>
Message-ID: <1571056228.74.0.188199253293.issue38472@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
nosy: +doko

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38472>
_______________________________________

From report at bugs.python.org  Mon Oct 14 08:43:44 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 12:43:44 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1571057024.08.0.297521586604.issue38449@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy:  -vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Mon Oct 14 08:44:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 12:44:20 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1571057060.08.0.385582003646.issue22347@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy:  -vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Mon Oct 14 09:10:44 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Mon, 14 Oct 2019 13:10:44 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571058644.66.0.00972088084308.issue37759@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:


New changeset 298439ce3fb01de6c3110cc4847e6afe3253ba7a by ?ukasz Langa (Serhiy Storchaka) in branch 'master':
bpo-37759: Polish What's New in Python 3.8. (#16769)
https://github.com/python/cpython/commit/298439ce3fb01de6c3110cc4847e6afe3253ba7a


----------
nosy: +lukasz.langa

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 09:12:14 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 13:12:14 +0000
Subject: [issue38466] [Easy doc] threading.excepthook doc talks about "object"
In-Reply-To: <1570981226.47.0.762418362865.issue38466@roundup.psfhosted.org>
Message-ID: <1571058734.05.0.391869845849.issue38466@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +newcomer friendly
title: threading.excepthook doc talks about "object" -> [Easy doc] threading.excepthook doc talks about "object"

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38466>
_______________________________________

From report at bugs.python.org  Mon Oct 14 09:12:37 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 13:12:37 +0000
Subject: [issue38445] os.path.exists() takes bool as argument and returns True
In-Reply-To: <1570792602.16.0.709405121857.issue38445@roundup.psfhosted.org>
Message-ID: <1571058757.12.0.689098996694.issue38445@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy:  -vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38445>
_______________________________________

From report at bugs.python.org  Mon Oct 14 09:17:51 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Mon, 14 Oct 2019 13:17:51 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571059071.37.0.0682375011723.issue37759@roundup.psfhosted.org>


Change by ?ukasz Langa <lukasz at langa.pl>:


----------
pull_requests: +16339
pull_request: https://github.com/python/cpython/pull/16777

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 09:25:49 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Mon, 14 Oct 2019 13:25:49 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571059549.75.0.420511212104.issue37759@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:


New changeset e498329ebe0d86a5d80471112d766502b144a476 by ?ukasz Langa in branch '3.8':
[3.8] bpo-37759: Polish What's New in Python 3.8. (GH-16769) (#16777)
https://github.com/python/cpython/commit/e498329ebe0d86a5d80471112d766502b144a476


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 09:31:34 2019
From: report at bugs.python.org (Petr Viktorin)
Date: Mon, 14 Oct 2019 13:31:34 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571059894.93.0.820007967829.issue38470@roundup.psfhosted.org>


Change by Petr Viktorin <encukou at gmail.com>:


----------
keywords: +patch
pull_requests: +16340
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16778

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 09:35:58 2019
From: report at bugs.python.org (Petr Viktorin)
Date: Mon, 14 Oct 2019 13:35:58 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571060158.43.0.938884795769.issue38470@roundup.psfhosted.org>


Petr Viktorin <encukou at gmail.com> added the comment:

If someone has access to Windows and can reproduce this (you need a more special setup than "just Windows"), and you want to spend some time debugging, please do. I'm shooting in the dark.

My proposed patch limits the maximum path depth to 20 directories on Windows. That is enough to test compileall's maxlevels option. Still a longer path would be nicer if possible.

----------
stage: patch review -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 09:53:56 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 14 Oct 2019 13:53:56 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571061236.85.0.377796292482.issue38470@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

You can trigger custom buildbot runs by pushing to the 'buildbot-custom' branch in the CPython repo.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 10:01:06 2019
From: report at bugs.python.org (Paul Martin)
Date: Mon, 14 Oct 2019 14:01:06 +0000
Subject: [issue38471] _ProactorDatagramTransport: If close() is called when
 write buffer is not empty,
 the remaining data is not sent and connection_lost is not called
In-Reply-To: <1571049755.46.0.456741846567.issue38471@roundup.psfhosted.org>
Message-ID: <1571061666.3.0.365833146525.issue38471@roundup.psfhosted.org>


Change by Paul Martin <greatestloginnameever at gmail.com>:


----------
keywords: +patch
pull_requests: +16341
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16779

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38471>
_______________________________________

From report at bugs.python.org  Mon Oct 14 10:01:50 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 14:01:50 +0000
Subject: [issue36338] urlparse of urllib returns wrong hostname
In-Reply-To: <1552896371.92.0.122580708995.issue36338@roundup.psfhosted.org>
Message-ID: <1571061710.8.0.667916268026.issue36338@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16342
pull_request: https://github.com/python/cpython/pull/16780

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36338>
_______________________________________

From report at bugs.python.org  Mon Oct 14 10:04:07 2019
From: report at bugs.python.org (Tal Einat)
Date: Mon, 14 Oct 2019 14:04:07 +0000
Subject: [issue38445] os.path.exists() takes bool as argument and returns True
In-Reply-To: <1570792602.16.0.709405121857.issue38445@roundup.psfhosted.org>
Message-ID: <1571061847.79.0.0793681262421.issue38445@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
nosy:  -taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38445>
_______________________________________

From report at bugs.python.org  Mon Oct 14 10:07:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 14:07:13 +0000
Subject: [issue36338] urlparse of urllib returns wrong hostname
In-Reply-To: <1552896371.92.0.122580708995.issue36338@roundup.psfhosted.org>
Message-ID: <1571062033.18.0.93296219562.issue36338@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I proposed PR 16780 which makes the urllib.parse module way more stricter:

* the IPv6 address is validated by ipaddress.IPv6Address() parser
* invalid characters are rejected in the IPv6 zone: "%", "[" and "]"
* the port number is now validated when parsing the URL: must be an integer in the [0; 65535] range

Sadly, validating using ipaddress.IPv6Address() cannot be easily ported to Python 2 which doesn't have this module.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36338>
_______________________________________

From report at bugs.python.org  Mon Oct 14 10:25:09 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 14 Oct 2019 14:25:09 +0000
Subject: [issue38473] AttributeError on asserting autospecced mock object
 added using attach_mock
Message-ID: <1571063109.86.0.136370910863.issue38473@roundup.psfhosted.org>


New submission from Karthikeyan Singaravelan <tir.karthi at gmail.com>:

The following program causes AttributeError while retrieving the spec signature of a call. It seems that not all mocks specced should have _spec_signature where if autospec is used and the mock is attached with attach_mock then the "mock" attribute has the correct object from which _spec_signature has to be derived. On the attribute being not present we can fallback to the sig being None. This can be workaround by disabling autospec but since this is present in 3.7.5RC1 and 3.8.0RC1 I am tagging it as regression. 

I am also attaching a patch with script to reproduce this that should pass with the patch. I will try to make a PR tonight. Sorry for the last minute report I just stumbled upon this while debugging https://bugs.python.org/issue21478#msg354489. This change was introduced as part of https://bugs.python.org/issue36871 by me. I am tagging the nosy list from issue for review of the patch.


import unittest
from unittest.mock import patch, Mock, call, ANY


class Foo:
    def set_foo(self, val): pass


class FooTest(unittest.TestCase):
    @patch(f"{__name__}.Foo.set_foo", autospec=True)
    def test_autospec_attach_mock_assert(self, mock_set_foo):
        manager = Mock()
        manager.attach_mock(mock_set_foo, "set_foo_func")
        obj = Foo()
        obj.set_foo(3)
        manager.assert_has_calls([call.set_foo_func(ANY, 3)])

if __name__ == "__main__":
    unittest.main()


?  Python-3.7.5rc1 ./python autospec_regression.py
E
======================================================================
ERROR: test_autospec_attach_mock_assert (__main__.FooTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/xtreak/Python-3.7.5rc1/Lib/unittest/mock.py", line 1255, in patched
    return func(*args, **keywargs)
  File "autospec_regression.py", line 16, in test_autospec_attach_mock_assert
    manager.assert_has_calls([call.set_foo_func(ANY, 3)])
  File "/home/xtreak/Python-3.7.5rc1/Lib/unittest/mock.py", line 897, in assert_has_calls
    expected = [self._call_matcher(c) for c in calls]
  File "/home/xtreak/Python-3.7.5rc1/Lib/unittest/mock.py", line 897, in <listcomp>
    expected = [self._call_matcher(c) for c in calls]
  File "/home/xtreak/Python-3.7.5rc1/Lib/unittest/mock.py", line 812, in _call_matcher
    sig = self._get_call_signature_from_name(_call[0])
  File "/home/xtreak/Python-3.7.5rc1/Lib/unittest/mock.py", line 798, in _get_call_signature_from_name
    sig = child._spec_signature
AttributeError: 'function' object has no attribute '_spec_signature'

----------------------------------------------------------------------
Ran 1 test in 0.003s

FAILED (errors=1)

Patch : 


?  Python-3.7.5rc1 diff -u Lib/unittest/mock.py Lib/unittest/mock_patched.py
--- Lib/unittest/mock.py	2019-10-01 22:53:17.000000000 +0530
+++ Lib/unittest/mock_patched.py	2019-10-14 19:18:00.038416294 +0530
@@ -795,7 +795,16 @@
                 break
             else:
                 children = child._mock_children
-                sig = child._spec_signature
+                # If an autospecced object is attached using attach_mock the
+                # child would be a function with mock object as attribute from
+                # which signature has to be derived. If there is no signature
+                # attribute then fallback to None to ensure old signature is 
+                # not used.
+                child = _extract_mock(child)
+                try:
+                    sig = child._spec_signature
+                except AttributeError:
+                    sig = None
 
         return sig

----------
components: Library (Lib)
keywords: 3.7regression, 3.8regression
messages: 354635
nosy: cjw296, gregory.p.smith, lisroach, lukasz.langa, mariocj89, michael.foord, ned.deily, xtreak
priority: normal
severity: normal
status: open
title: AttributeError on asserting autospecced mock object added using attach_mock
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38473>
_______________________________________

From report at bugs.python.org  Mon Oct 14 10:50:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 14:50:46 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571064646.01.0.366984880523.issue38470@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

To reproduce the recent on a recent Windows 10, you can opt-out for long path using this change:

diff --git a/PC/python.manifest b/PC/python.manifest
index 8e1bc022ad..524f9b2f6d 100644
--- a/PC/python.manifest
+++ b/PC/python.manifest
@@ -18,7 +18,6 @@
   </compatibility>
   <application xmlns="urn:schemas-microsoft-com:asm.v3">
     <windowsSettings>
-      <longPathAware xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">true</longPathAware>
     </windowsSettings>
   </application>
   <dependency>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 11:41:18 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 14 Oct 2019 15:41:18 +0000
Subject: [issue38410] Possible fatal errors due to
 _PyEval_SetAsyncGen{Finalizer, Firstiter}()
In-Reply-To: <1570543574.99.0.942798410146.issue38410@roundup.psfhosted.org>
Message-ID: <1571067678.31.0.695936481613.issue38410@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

In that case, the fix for 3.8 should be to call PyErr_WriteUnraisable(NULL) when an error occurs. This will report it through the new unraisable hook, and also prevent a fatal error if the exception escapes.

----------
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38410>
_______________________________________

From report at bugs.python.org  Mon Oct 14 11:42:25 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 14 Oct 2019 15:42:25 +0000
Subject: [issue38453] ntpath.realpath() should make absolute path earlier
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1571067745.43.0.605004946694.issue38453@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset d83fc2702951f56a7339aa95d62414ed6e0fb40d by Steve Dower in branch 'master':
bpo-38453: Resolve test directories before chdir to them (GH-16723)
https://github.com/python/cpython/commit/d83fc2702951f56a7339aa95d62414ed6e0fb40d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Mon Oct 14 11:43:02 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 Oct 2019 15:43:02 +0000
Subject: [issue38453] ntpath.realpath() should make absolute path earlier
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1571067782.36.0.610601530004.issue38453@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16343
pull_request: https://github.com/python/cpython/pull/16783

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Mon Oct 14 11:54:00 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 14 Oct 2019 15:54:00 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571068440.24.0.088361045507.issue38470@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

I'm okay with skipping the failing test if we detect sys.getwindowsversion().major < 10

Windows 7 is not supported for Python 3.9, so this buildbot can be disabled/upgraded.

Windows 8.1 will be supported for at least 3.9, so we'll have to keep skipping the test there.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 11:54:14 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 14 Oct 2019 15:54:14 +0000
Subject: [issue38473] AttributeError on asserting autospecced mock object
 added using attach_mock
In-Reply-To: <1571063109.86.0.136370910863.issue38473@roundup.psfhosted.org>
Message-ID: <1571068454.07.0.325863352255.issue38473@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
keywords: +patch
pull_requests: +16344
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16784

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38473>
_______________________________________

From report at bugs.python.org  Mon Oct 14 11:54:28 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 14 Oct 2019 15:54:28 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571068468.71.0.318235506268.issue37759@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
pull_requests: +16345
pull_request: https://github.com/python/cpython/pull/16785

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 12:01:32 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 Oct 2019 16:01:32 +0000
Subject: [issue38453] ntpath.realpath() should make absolute path earlier
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1571068892.93.0.260224309841.issue38453@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset aa909b6b1242b4969b20bb0250ac386f9b4120d7 by Miss Islington (bot) in branch '3.8':
bpo-38453: Resolve test directories before chdir to them (GH-16723)
https://github.com/python/cpython/commit/aa909b6b1242b4969b20bb0250ac386f9b4120d7


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Mon Oct 14 12:03:20 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 Oct 2019 16:03:20 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571069000.02.0.205501829824.issue37759@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16346
pull_request: https://github.com/python/cpython/pull/16786

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Mon Oct 14 12:35:03 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 14 Oct 2019 16:35:03 +0000
Subject: [issue38410] Possible fatal errors due to
 _PyEval_SetAsyncGen{Finalizer, Firstiter}()
In-Reply-To: <1570543574.99.0.942798410146.issue38410@roundup.psfhosted.org>
Message-ID: <1571070903.84.0.971022763413.issue38410@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

But I'm okay to defer it - this is still going to be obscure functionality for the time being, and it's possible to avoid the issue.

----------
priority: release blocker -> deferred blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38410>
_______________________________________

From report at bugs.python.org  Mon Oct 14 12:38:59 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 14 Oct 2019 16:38:59 +0000
Subject: [issue38453] ntpath.realpath() does not fully resolve relative paths
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1571071139.86.0.0895939224597.issue38453@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
title: ntpath.realpath() should make absolute path earlier -> ntpath.realpath() does not fully resolve relative paths

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Mon Oct 14 13:40:46 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 14 Oct 2019 17:40:46 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1571074846.5.0.108200238922.issue21478@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

I tried your example as below using __name__. I received an AttributeError for which issue38473 in 3.7.5RC1 and 3.8.0RC1 and opened issue38473 and I am running my below code under that issue PR. For 3.7.4, I received manager.mock_calls to be an empty list since it doesn't contain the patch for this issue. Can you please confirm my results too.

?  cpython git:(bpo38473) cat ../backups/bpo21478.py
import unittest
from unittest import TestCase
from unittest.mock import patch, Mock, call, ANY


class MyObject:
    def __init__(self):
        self.foo = 0
        self.bar = 0

    def set_foo(self, value):
        self.foo = value

    def set_bar(self, value):
        self.bar = value


def do_something():
    o = MyObject()
    o.set_foo(3)
    o.set_bar(4)
    return "something unrelated"


class MyObjectTest(TestCase):
    @patch(f"{__name__}.MyObject.set_bar", autospec=True)
    @patch(f"{__name__}.MyObject.set_foo", autospec=True)
    def test_do_something(self, mock_set_foo, mock_set_bar):
        manager = Mock()
        manager.attach_mock(mock_set_foo, "set_foo_func")
        manager.attach_mock(mock_set_bar, "set_bar_func")
        do_something()
        assert manager.mock_calls == [
            call.set_foo_func(ANY, 3),
            call.set_bar_func(ANY, 4),
        ]
        manager.assert_has_calls([call.set_foo_func(ANY, 3), call.set_bar_func(ANY, 4)])


if __name__ == "__main__":
    unittest.main()


?  cpython git:(bpo38473) ./python ../backups/bpo21478.py
.
----------------------------------------------------------------------
Ran 1 test in 0.006s

OK

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Mon Oct 14 13:56:10 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Mon, 14 Oct 2019 17:56:10 +0000
Subject: [issue38473] AttributeError on asserting autospecced mock object
 added using attach_mock
In-Reply-To: <1571063109.86.0.136370910863.issue38473@roundup.psfhosted.org>
Message-ID: <1571075770.45.0.727200864162.issue38473@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38473>
_______________________________________

From report at bugs.python.org  Mon Oct 14 14:30:34 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Mon, 14 Oct 2019 18:30:34 +0000
Subject: [issue38474] digit check logic can be replaced by Py_ISDIGIT on
 prepare_s
Message-ID: <1571077834.59.0.937971525821.issue38474@roundup.psfhosted.org>


New submission from Dong-hee Na <donghee.na92 at gmail.com>:

digit check logic can be replaced by Py_ISDIGIT on prepare_s.

----------
assignee: corona10
messages: 354643
nosy: corona10
priority: normal
severity: normal
status: open
title: digit check logic can be replaced by Py_ISDIGIT on prepare_s

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38474>
_______________________________________

From report at bugs.python.org  Mon Oct 14 14:31:49 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Mon, 14 Oct 2019 18:31:49 +0000
Subject: [issue38474] digit check logic can be replaced by Py_ISDIGIT on
 prepare_s
In-Reply-To: <1571077834.59.0.937971525821.issue38474@roundup.psfhosted.org>
Message-ID: <1571077909.95.0.412503297719.issue38474@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
keywords: +patch
pull_requests: +16347
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16787

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38474>
_______________________________________

From report at bugs.python.org  Mon Oct 14 14:34:01 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Mon, 14 Oct 2019 18:34:01 +0000
Subject: [issue38474] digit check logic can be replaced by Py_ISDIGIT on
 prepare_s
In-Reply-To: <1571077834.59.0.937971525821.issue38474@roundup.psfhosted.org>
Message-ID: <1571078041.24.0.254000263742.issue38474@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
versions: +Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38474>
_______________________________________

From report at bugs.python.org  Mon Oct 14 14:34:35 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 14 Oct 2019 18:34:35 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571078075.38.0.894045618361.issue38469@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Mon Oct 14 15:16:10 2019
From: report at bugs.python.org (Pierre Quentel)
Date: Mon, 14 Oct 2019 19:16:10 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571080570.44.0.468024728102.issue38469@roundup.psfhosted.org>


Pierre Quentel <pierre.quentel at gmail.com> added the comment:

That was a quick fix, thanks !

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Mon Oct 14 15:22:30 2019
From: report at bugs.python.org (Neil Schemenauer)
Date: Mon, 14 Oct 2019 19:22:30 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1571080950.08.0.173984022185.issue38006@roundup.psfhosted.org>


Change by Neil Schemenauer <nas-python at arctrix.com>:


----------
pull_requests: +16348
pull_request: https://github.com/python/cpython/pull/16788

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Mon Oct 14 15:31:02 2019
From: report at bugs.python.org (DEVOR BLAKE DANIELS)
Date: Mon, 14 Oct 2019 19:31:02 +0000
Subject: [issue38475] Break Statement
Message-ID: <1571081462.55.0.733459298847.issue38475@roundup.psfhosted.org>


New submission from DEVOR BLAKE DANIELS <dev40573 at gmail.com>:

The break statement in my AiO() function seems to cause my Uinput() function to malfunction.

----------
components: Windows
files: three.py
messages: 354645
nosy: dev40573, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Break Statement
versions: Python 3.8
Added file: https://bugs.python.org/file48659/three.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38475>
_______________________________________

From report at bugs.python.org  Mon Oct 14 15:58:43 2019
From: report at bugs.python.org (Sam Franklin)
Date: Mon, 14 Oct 2019 19:58:43 +0000
Subject: [issue37910] argparse wrapping fails with metavar="" (no metavar)
In-Reply-To: <1566425299.96.0.375120843288.issue37910@roundup.psfhosted.org>
Message-ID: <1571083123.74.0.898608552523.issue37910@roundup.psfhosted.org>


Sam Franklin <sjfranklin24 at gmail.com> added the comment:

Paul, very true. If I find time I may take a look at rewriting it as you suggest.
For the moment, though, there's a relatively simple change that opens up a range of allowable whitespace characters. It's still a bandage, but it covers decent-sized area and should be easily backported. What do you think of the pull request? It's passed a first review.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37910>
_______________________________________

From report at bugs.python.org  Mon Oct 14 16:40:36 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Mon, 14 Oct 2019 20:40:36 +0000
Subject: [issue38456] Reduce the time test_subprocess takes to complete.
In-Reply-To: <1570915664.41.0.600749429007.issue38456@roundup.psfhosted.org>
Message-ID: <1571085636.33.0.775647392173.issue38456@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:


New changeset 4f0587f161786318cdfa22c42459676fa42aacb6 by Gregory P. Smith in branch '3.8':
[3.8] bpo-38456: Use /bin/true in test_subprocess (GH-16737)
https://github.com/python/cpython/commit/4f0587f161786318cdfa22c42459676fa42aacb6


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38456>
_______________________________________

From report at bugs.python.org  Mon Oct 14 16:48:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 20:48:42 +0000
Subject: [issue38456] Reduce the time test_subprocess takes to complete.
In-Reply-To: <1570915664.41.0.600749429007.issue38456@roundup.psfhosted.org>
Message-ID: <1571086122.34.0.754714501255.issue38456@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Nice. Any idea of the speedup on Travis CI and/or on a specific buildbot worker?

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38456>
_______________________________________

From report at bugs.python.org  Mon Oct 14 16:51:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 20:51:24 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571086284.27.0.916418169522.issue38470@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16350
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16789

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 16:56:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 20:56:13 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571086573.35.0.781651098587.issue38470@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The new test was added by bpo-38112: commit 4267c989e7fc6cd528e8a1d04a07fac5cca85ec7.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:00:19 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Mon, 14 Oct 2019 21:00:19 +0000
Subject: [issue38456] Reduce the time test_subprocess takes to complete.
In-Reply-To: <1570915664.41.0.600749429007.issue38456@roundup.psfhosted.org>
Message-ID: <1571086819.76.0.803990234781.issue38456@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

I assume the CI systems are shared and potentially noisy.  It should be easier to look at some logs from slower buildbots.  but sadly test_subprocess has fallen off the list of "10 slowest tests" that timing info is supplied for.  concurrent.futures, multiprocessing, asyncio, tokenize, etc. all take longer.

I still don't expect it to be more than a few seconds.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38456>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:06:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:06:26 +0000
Subject: [issue37431] test_asyncio: test_start_tls_server_1() failed on ARMv7
 Debian buster 3.7
In-Reply-To: <1561654379.48.0.149014452571.issue37431@roundup.psfhosted.org>
Message-ID: <1571087186.09.0.0355326025732.issue37431@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I close this issue as a duplicate of bpo-35998.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> test_asyncio: test_start_tls_server_1() TimeoutError on Fedora 29

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37431>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:06:28 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:06:28 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571087188.45.0.0482483119621.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I closed bpo-37431 as a duplicate of this issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:07:17 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:07:17 +0000
Subject: [issue35031] test_asyncio test_start_tls_server_1 fails in AMD64
 FreeBSD CURRENT buildbots
In-Reply-To: <1540044407.71.0.788709270274.issue35031@psf.upfronthosting.co.za>
Message-ID: <1571087237.13.0.316798353709.issue35031@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It seems like the issue has been fixed.

See also bpo-35998 for a similar issue on other platforms.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35031>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:13:23 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:13:23 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571087603.19.0.556642364956.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I didn't check if it's the same issue than previous failures, but test_start_tls_server_1() just failed on x86 Gentoo Installed with X 3.8 buildbot:

pythoninfo:

ssl.HAS_SNI: True
ssl.OPENSSL_VERSION: OpenSSL 1.1.1d  10 Sep 2019
ssl.OPENSSL_VERSION_INFO: (1, 1, 1, 4, 15)
ssl.OP_ALL: -0x7fffffac
ssl.OP_NO_TLSv1_1: 0x10000000
ssl.SSLContext.maximum_version: TLSVersion.MAXIMUM_SUPPORTED
ssl.SSLContext.minimum_version: TLSVersion.MINIMUM_SUPPORTED
ssl.SSLContext.options: Options.OP_NO_SSLv3|OP_CIPHER_SERVER_PREFERENCE|OP_ENABLE_MIDDLEBOX_COMPAT|OP_NO_COMPRESSION|OP_ALL
ssl.SSLContext.protocol: _SSLMethod.PROTOCOL_TLS
ssl.SSLContext.verify_mode: VerifyMode.CERT_NONE
ssl.default_https_context.maximum_version: TLSVersion.MAXIMUM_SUPPORTED
ssl.default_https_context.minimum_version: TLSVersion.MINIMUM_SUPPORTED
ssl.default_https_context.options: Options.OP_NO_SSLv3|OP_CIPHER_SERVER_PREFERENCE|OP_ENABLE_MIDDLEBOX_COMPAT|OP_NO_COMPRESSION|OP_ALL
ssl.default_https_context.protocol: _SSLMethod.PROTOCOL_TLS
ssl.default_https_context.verify_mode: VerifyMode.CERT_REQUIRED
ssl.stdlib_context.maximum_version: TLSVersion.MAXIMUM_SUPPORTED
ssl.stdlib_context.minimum_version: TLSVersion.MINIMUM_SUPPORTED
ssl.stdlib_context.options: Options.OP_NO_SSLv3|OP_CIPHER_SERVER_PREFERENCE|OP_ENABLE_MIDDLEBOX_COMPAT|OP_NO_COMPRESSION|OP_ALL
ssl.stdlib_context.protocol: _SSLMethod.PROTOCOL_TLS
ssl.stdlib_context.verify_mode: VerifyMode.CERT_NONE


https://buildbot.python.org/all/#/builders/230/builds/435

test_start_tls_server_1 (test.test_asyncio.test_sslproto.SelectorStartTLSTests) ... Exception in thread test-client:
Traceback (most recent call last):
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/functional.py", line 190, in run
    self._prog(TestSocketWrapper(self._sock))
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/test_sslproto.py", line 575, in <lambda>
    with self.tcp_client(lambda sock: client(sock, addr),
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/test_sslproto.py", line 520, in client
    answer = sock.recv_all(len(ANSWER))
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/functional.py", line 130, in recv_all
    data = self.recv(n - len(buf))
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/ssl.py", line 1226, in recv
    return self.read(buflen)
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/ssl.py", line 1101, in read
    return self._sslobj.read(len)
ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:2560)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/functional.py", line 192, in run
    self._test._abort_socket_test(ex)
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/functional.py", line 114, in _abort_socket_test
    self.fail(ex)
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/unittest/case.py", line 753, in fail
    raise self.failureException(msg)
AssertionError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:2560)
/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/threading.py:934: ResourceWarning: unclosed <ssl.SSLSocket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('127.0.0.1', 59752), raddr=('127.0.0.1', 45469)>
  self._invoke_excepthook(self)
ResourceWarning: Enable tracemalloc to get the object allocation traceback
ERROR


Unhandled error in exception handler
context: {'message': 'Task was destroyed but it is pending!', 'task': <Task pending name='Task-1699' coro=<BaseStartTLS.test_start_tls_server_1.<locals>.main() running at /buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/test_sslproto.py:555> wait_for=<Future finished result=None> cb=[_release_waiter(<Future pendi...xb6a27118>()]>)() at /buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/tasks.py:429]>}
Traceback (most recent call last):
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/base_events.py", line 1729, in call_exception_handler
    self._exception_handler(self, context)
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/functional.py", line 22, in loop_exception_handler
    self.loop.default_exception_handler(context)
AttributeError: 'NoneType' object has no attribute 'default_exception_handler'
/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/test_streams.py:40: ResourceWarning: unclosed <socket.socket fd=8, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('127.0.0.1', 45469)>
  gc.collect()
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/selector_events.py:684: ResourceWarning: unclosed transport <_SelectorSocketTransport fd=8>
  _warn(f"unclosed transport {self!r}", ResourceWarning, source=self)
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/sslproto.py:321: ResourceWarning: unclosed transport <asyncio.sslproto._SSLProtocolTransport object at 0xb5c82b38>
  _warn(f"unclosed transport {self!r}", ResourceWarning, source=self)
ResourceWarning: Enable tracemalloc to get the object allocation traceback
Unhandled error in exception handler
context: {'message': 'Fatal error on SSL transport', 'exception': RuntimeError('Event loop is closed'), 'transport': <_SelectorSocketTransport closing fd=8>, 'protocol': <asyncio.sslproto.SSLProtocol object at 0xb6a27448>}
Traceback (most recent call last):
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/selector_events.py", line 898, in write
    n = self._sock.send(data)
OSError: [Errno 9] Bad file descriptor

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/sslproto.py", line 685, in _process_write_backlog
    self._transport.write(chunk)
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/selector_events.py", line 904, in write
    self._fatal_error(exc, 'Fatal write error on socket transport')
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/selector_events.py", line 699, in _fatal_error
    self._force_close(exc)
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/selector_events.py", line 711, in _force_close
    self._loop.call_soon(self._call_connection_lost, exc)
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/base_events.py", line 711, in call_soon
    self._check_closed()
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/base_events.py", line 504, in _check_closed
    raise RuntimeError('Event loop is closed')
RuntimeError: Event loop is closed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/base_events.py", line 1729, in call_exception_handler
    self._exception_handler(self, context)
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/functional.py", line 22, in loop_exception_handler
    self.loop.default_exception_handler(context)
AttributeError: 'NoneType' object has no attribute 'default_exception_handler'
/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/test_streams.py:40: ResourceWarning: unclosed <socket.socket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('127.0.0.1', 45469)>
  gc.collect()
ResourceWarning: Enable tracemalloc to get the object allocation traceback

ERROR: test_start_tls_server_1 (test.test_asyncio.test_sslproto.SelectorStartTLSTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/test/test_asyncio/test_sslproto.py", line 585, in test_start_tls_server_1
    self.loop.run_until_complete(run_main())
  File "/buildbot/buildarea/cpython/3.8.ware-gentoo-x86.installed/build/target/lib/python3.8/asyncio/base_events.py", line 606, in run_until_complete
    raise RuntimeError('Event loop stopped before Future completed.')
RuntimeError: Event loop stopped before Future completed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:15:16 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:15:16 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571087716.86.0.457340967002.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Similar failure on x86 Gentoo Non-Debug with X 3.x:
https://buildbot.python.org/all/#/builders/99/builds/3472

ERROR: test_start_tls_server_1 (test.test_asyncio.test_sslproto.SelectorStartTLSTests)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:23:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:23:30 +0000
Subject: [issue33356] Windows 10 buildbot:
 test__xxsubinterpreters.test_already_running() fails randomly
In-Reply-To: <1524666400.61.0.682650639539.issue33356@psf.upfronthosting.co.za>
Message-ID: <1571088210.71.0.26277300328.issue33356@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I close this issue as a duplicate of bpo-37224.

----------
resolution:  -> duplicate
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33356>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:24:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:24:46 +0000
Subject: [issue37224] test__xxsubinterpreters failed on AMD64 Windows8.1
 Refleaks 3.8
In-Reply-To: <1560214681.61.0.906498246375.issue37224@roundup.psfhosted.org>
Message-ID: <1571088286.06.0.696612485767.issue37224@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I marked bpo-33356 as a duplicate of this issue:

* Windows10 3.x: test_already_running() failed once, but passed when run again: ...
* AMD64 FreeBSD 10-STABLE Non-Debug 3.x: ...

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37224>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:26:18 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:26:18 +0000
Subject: [issue37224] test__xxsubinterpreters failed on AMD64 Windows8.1
 Refleaks 3.8
In-Reply-To: <1560214681.61.0.906498246375.issue37224@roundup.psfhosted.org>
Message-ID: <1571088378.58.0.704067510827.issue37224@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I closed bpo-38154 as a duplicate of this issue:

* AMD64 FreeBSD CURRENT Shared 3.x: ...

Kyle Stanley proposed a fix: PR 16293.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37224>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:26:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:26:24 +0000
Subject: [issue38154] test__xxsubinterpreters: random failures on AMD64
 FreeBSD CURRENT Shared 3.x
In-Reply-To: <1568368239.98.0.217777678278.issue38154@roundup.psfhosted.org>
Message-ID: <1571088384.65.0.758227506409.issue38154@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I close this issue as a duplicate of bpo-37224.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> test__xxsubinterpreters failed on AMD64 Windows8.1 Refleaks 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38154>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:26:37 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:26:37 +0000
Subject: [issue37224] test__xxsubinterpreters fails randomly
In-Reply-To: <1560214681.61.0.906498246375.issue37224@roundup.psfhosted.org>
Message-ID: <1571088396.99.0.111628238532.issue37224@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: test__xxsubinterpreters failed on AMD64 Windows8.1 Refleaks 3.8 -> test__xxsubinterpreters fails randomly

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37224>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:27:17 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:27:17 +0000
Subject: [issue37224] test__xxsubinterpreters fails randomly
In-Reply-To: <1560214681.61.0.906498246375.issue37224@roundup.psfhosted.org>
Message-ID: <1571088437.05.0.403538501454.issue37224@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

AMD64 FreeBSD CURRENT Shared 3.x:
https://buildbot.python.org/all/#/builders/168/builds/1630

FAIL: test_still_running (test.test__xxsubinterpreters.DestroyTests)
1:07:09 load avg: 8.18 Re-running failed tests in verbose mode
1:07:09 load avg: 8.18 Re-running test__xxsubinterpreters in verbose mode
FAIL: test_still_running (test.test__xxsubinterpreters.DestroyTests)
FAIL: test_subinterpreter (test.test__xxsubinterpreters.IsRunningTests)
FAIL: test_already_running (test.test__xxsubinterpreters.RunStringTests)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37224>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:28:12 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:28:12 +0000
Subject: [issue37224] test__xxsubinterpreters fails randomly
In-Reply-To: <1560214681.61.0.906498246375.issue37224@roundup.psfhosted.org>
Message-ID: <1571088492.77.0.470889374099.issue37224@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

AMD64 FreeBSD CURRENT Shared 3.8:
https://buildbot.python.org/all/#/builders/212/builds/310

FAIL: test_still_running (test.test__xxsubinterpreters.DestroyTests)
FAIL: test_run_coroutine_threadsafe_with_timeout (test.test_asyncio.test_tasks.RunCoroutineThreadsafeTests)
1:01:44 load avg: 7.72 Re-running failed tests in verbose mode
1:01:44 load avg: 7.72 Re-running test__xxsubinterpreters in verbose mode
FAIL: test_still_running (test.test__xxsubinterpreters.DestroyTests)
1:02:01 load avg: 7.58 Re-running test_asyncio in verbose mode

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37224>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:28:44 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Mon, 14 Oct 2019 21:28:44 +0000
Subject: [issue38475] Break Statement
In-Reply-To: <1571081462.55.0.733459298847.issue38475@roundup.psfhosted.org>
Message-ID: <1571088524.88.0.00948942129725.issue38475@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Define "malfunction". Are we supposed to know what your code is meant to do, as well as what it actually does?

Please don't use the bug tracker as a help desk for your own scripts. There are many forums where you can ask for help, such as the mailing lists, the Python Discuss forum, Stackoverflow, Reddit's r/learnpython etc.

If you are going to submit something here as a bug, please ensure that:

(1) it actually is a bug in the Python interpreter first, rather than a bug in your own code; and 

(2) you provide a MINIMAL example, with a description of the expected output, a reason why you expect it, and the actual output.

It may help for you to read this: http://sscce.org/

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38475>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:42:18 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Mon, 14 Oct 2019 21:42:18 +0000
Subject: [issue38469] PEP 572 : assignment expression to a global variable in
 a comprehension
In-Reply-To: <1571000051.15.0.611092311064.issue38469@roundup.psfhosted.org>
Message-ID: <1571089338.93.0.878789752347.issue38469@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:

(FTR the fix is part of Python 3.8.0)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38469>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:45:09 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Mon, 14 Oct 2019 21:45:09 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1571089509.43.0.144067168046.issue38449@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:

(3.8.0 is released with this fix)

----------
priority: release blocker -> normal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:45:39 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Mon, 14 Oct 2019 21:45:39 +0000
Subject: [issue38359] pyw.exe opens console window in Windows 10
In-Reply-To: <1570096405.52.0.325874974028.issue38359@roundup.psfhosted.org>
Message-ID: <1571089539.04.0.658882333405.issue38359@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:

(3.8.0 is released with this fix)

----------
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38359>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:45:49 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Mon, 14 Oct 2019 21:45:49 +0000
Subject: [issue38355] ntpath.realpath() fails on sys.executable
In-Reply-To: <1570055857.28.0.434394542652.issue38355@roundup.psfhosted.org>
Message-ID: <1571089549.96.0.52068258994.issue38355@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:

(3.8.0 is released with this fix)

----------
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38355>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:46:14 2019
From: report at bugs.python.org (=?utf-8?q?=C5=81ukasz_Langa?=)
Date: Mon, 14 Oct 2019 21:46:14 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1571089574.59.0.976202024158.issue38344@roundup.psfhosted.org>


?ukasz Langa <lukasz at langa.pl> added the comment:

(3.8.0 is released with this fix)

----------
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:52:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:52:47 +0000
Subject: [issue38476] test_multiprocessing_fork.test_terminate() failed on
 AMD64 Debian PGO 3.x
Message-ID: <1571089967.06.0.895638026997.issue38476@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

test_multiprocessing_fork.test_terminate() failed twice on AMD64 Debian PGO 3.x:

https://buildbot.python.org/all/#/builders/47/builds/3699

0:23:37 load avg: 0.01 [419/419/1] test_multiprocessing_fork crashed (Exit code 1)
Timeout (0:15:00)!
Thread 0x00007f0272748700 (most recent call first):
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/connection.py", line 379 in _recv
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/connection.py", line 414 in _recv_bytes
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/connection.py", line 250 in recv
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/pool.py", line 599 in _handle_results
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/threading.py", line 882 in run
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/threading.py", line 944 in _bootstrap_inner
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/threading.py", line 902 in _bootstrap

Thread 0x00007f027a8a6500 (most recent call first):
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/pool.py", line 674 in _help_stuff_finish
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/pool.py", line 689 in _terminate_pool
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/util.py", line 201 in __call__
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/pool.py", line 656 in terminate
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/test/_test_multiprocessing.py", line 2521 in test_terminate
...
0:23:37 load avg: 0.01 Re-running test_multiprocessing_fork in verbose mode
...
test_starmap (test.test_multiprocessing_fork.WithProcessesTestPool) ... ok
test_starmap_async (test.test_multiprocessing_fork.WithProcessesTestPool) ... ok
Timeout (0:15:00)!
Thread 0x00007f251d553700 (most recent call first):
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/connection.py", line 379 in _recv
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/connection.py", line 414 in _recv_bytes
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/connection.py", line 250 in recv
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/pool.py", line 599 in _handle_results
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/threading.py", line 882 in run
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/threading.py", line 944 in _bootstrap_inner
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/threading.py", line 902 in _bootstrap

Thread 0x00007f2523e76500 (most recent call first):
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/pool.py", line 674 in _help_stuff_finish
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/pool.py", line 689 in _terminate_pool
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/util.py", line 201 in __call__
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/multiprocessing/pool.py", line 656 in terminate
  File "/var/lib/buildbot/slaves/enable-optimizations-bot/3.x.gps-debian-profile-opt.pgo/build/Lib/test/_test_multiprocessing.py", line 2521 in test_terminate

----------
components: Tests
messages: 354669
nosy: vstinner
priority: normal
severity: normal
status: open
title: test_multiprocessing_fork.test_terminate() failed on AMD64 Debian PGO 3.x
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38476>
_______________________________________

From report at bugs.python.org  Mon Oct 14 17:54:33 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 21:54:33 +0000
Subject: [issue38476] test_multiprocessing_fork.test_terminate() failed on
 AMD64 Debian PGO 3.x
In-Reply-To: <1571089967.06.0.895638026997.issue38476@roundup.psfhosted.org>
Message-ID: <1571090073.94.0.897887151835.issue38476@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> https://buildbot.python.org/all/#/builders/47/builds/3699

The 7 following builds are success. But the latest build failed with "no space left on disk":
https://buildbot.python.org/all/#/builders/47/builds/3707

OSError: [Errno 28] No space left on device: '@test_23959_tmp' -> '@test_23959_tmp2'

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38476>
_______________________________________

From report at bugs.python.org  Mon Oct 14 18:00:59 2019
From: report at bugs.python.org (Jeremy Kloth)
Date: Mon, 14 Oct 2019 22:00:59 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571090459.01.0.328321394731.issue38470@roundup.psfhosted.org>


Jeremy Kloth <jeremy.kloth+python-tracker at gmail.com> added the comment:

> Windows 7 is not supported for Python 3.9, so this buildbot can be disabled/upgraded.

As long as 3.7 and 3.8 are being tested through the buildbots, I would think testing on Windows 7 is still advised.

That said, once those versions are no longer tested (or deemed to not need Windows 7 support) I will be upgrading that buildbot.

----------
nosy: +jkloth

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 18:01:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 22:01:47 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571090507.95.0.173432620771.issue38470@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I wrote PR 16789 which fix the issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 18:13:07 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 14 Oct 2019 22:13:07 +0000
Subject: [issue38133] py.exe cannot locate Store package
In-Reply-To: <1568286313.97.0.196410705778.issue38133@roundup.psfhosted.org>
Message-ID: <1571091187.7.0.0630344831254.issue38133@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
pull_requests: +16351
pull_request: https://github.com/python/cpython/pull/16791

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38133>
_______________________________________

From report at bugs.python.org  Mon Oct 14 18:27:11 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Oct 2019 22:27:11 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1571092031.52.0.486502700018.issue36389@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16352
pull_request: https://github.com/python/cpython/pull/16796

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Mon Oct 14 18:32:37 2019
From: report at bugs.python.org (Tahia K)
Date: Mon, 14 Oct 2019 22:32:37 +0000
Subject: [issue38288] shutil.make_archive() should allow setting
 zipfile.ZipFile() 'strict_timestamps'
In-Reply-To: <1569516230.4.0.693896047629.issue38288@roundup.psfhosted.org>
Message-ID: <1571092357.61.0.803116724071.issue38288@roundup.psfhosted.org>


Change by Tahia K <tahia.khan at gmail.com>:


----------
keywords: +patch
pull_requests: +16353
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16797

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38288>
_______________________________________

From report at bugs.python.org  Mon Oct 14 18:34:20 2019
From: report at bugs.python.org (Tahia K)
Date: Mon, 14 Oct 2019 22:34:20 +0000
Subject: [issue38288] shutil.make_archive() should allow setting
 zipfile.ZipFile() 'strict_timestamps'
In-Reply-To: <1569516230.4.0.693896047629.issue38288@roundup.psfhosted.org>
Message-ID: <1571092460.83.0.958255900202.issue38288@roundup.psfhosted.org>


Tahia K <tahia.khan at gmail.com> added the comment:

I went ahead and picked this one up :) PR is posted to github.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38288>
_______________________________________

From report at bugs.python.org  Mon Oct 14 18:44:02 2019
From: report at bugs.python.org (Neil Schemenauer)
Date: Mon, 14 Oct 2019 22:44:02 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1571093042.65.0.827472874937.issue38006@roundup.psfhosted.org>


Neil Schemenauer <nas-python at arctrix.com> added the comment:

> It's fundamentally insane to expect any gc to work perfectly when it may be blind to what the object graph _is_.

I'm often amazed it works at all, let alone perfectly. ;-P

This did trigger me to think of another possible problem.  I setup my unit test as you suggested:

        #   Z <- Y <- A--+--> WZ -> C
        #             ^  |
        #             +--+
        # where:
        #   WZ is a weakref to Z with callback C
        #   Y doesn't implement tp_traverse
        #   A contains a reference to itself, Y and WZ

But what happens if the GC doesn't see that WZ is trash?  Then it will not be cleared.  Hang it off Y so the GC can't find it.  We can set things up so that Z is freed before WZ (e.g. WZ in a second and newer cycle).  Then, the callback might still run.

On further thought, this seems safe (but maybe broken) because of the handle_weakrefs() logic.  The GC will think WZ is going to outlive Z so it will call it before doing any tp_clear calls.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Mon Oct 14 18:45:46 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 14 Oct 2019 22:45:46 +0000
Subject: [issue38133] py.exe cannot locate Store package
In-Reply-To: <1568286313.97.0.196410705778.issue38133@roundup.psfhosted.org>
Message-ID: <1571093146.64.0.886634751866.issue38133@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 4d202281c128e2026e78fc5f4cc752b1dafbf3ad by Steve Dower in branch 'master':
bpo-38133: Update docs to reflect fixes to py.exe launcher (GH-16791)
https://github.com/python/cpython/commit/4d202281c128e2026e78fc5f4cc752b1dafbf3ad


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38133>
_______________________________________

From report at bugs.python.org  Mon Oct 14 18:45:55 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 Oct 2019 22:45:55 +0000
Subject: [issue38133] py.exe cannot locate Store package
In-Reply-To: <1568286313.97.0.196410705778.issue38133@roundup.psfhosted.org>
Message-ID: <1571093155.45.0.186521008281.issue38133@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16354
pull_request: https://github.com/python/cpython/pull/16798

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38133>
_______________________________________

From report at bugs.python.org  Mon Oct 14 18:52:52 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 14 Oct 2019 22:52:52 +0000
Subject: [issue38133] py.exe cannot locate Store package
In-Reply-To: <1568286313.97.0.196410705778.issue38133@roundup.psfhosted.org>
Message-ID: <1571093572.01.0.701040419505.issue38133@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 42308e8b27c8023e3f9d037f5e4a8892f2dcbc48 by Miss Islington (bot) in branch '3.8':
bpo-38133: Update docs to reflect fixes to py.exe launcher (GH-16791)
https://github.com/python/cpython/commit/42308e8b27c8023e3f9d037f5e4a8892f2dcbc48


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38133>
_______________________________________

From report at bugs.python.org  Mon Oct 14 19:00:08 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Mon, 14 Oct 2019 23:00:08 +0000
Subject: [issue37224] test__xxsubinterpreters fails randomly
In-Reply-To: <1560214681.61.0.906498246375.issue37224@roundup.psfhosted.org>
Message-ID: <1571094008.34.0.889886513921.issue37224@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> Kyle Stanley proposed a fix: PR 16293.

Note that I'm not confident about the fix I proposed in GH-16293, it was more of an idea to fix the intermittent failures more than anything. It definitely needs review from someone knowledgeable about sub-interpreters and the PyInterpreterState API. This isn't an area that I'm experienced in, but I am interested in it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37224>
_______________________________________

From report at bugs.python.org  Mon Oct 14 19:11:16 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Mon, 14 Oct 2019 23:11:16 +0000
Subject: [issue31387] asyncio should make it easy to enable cooperative SIGINT
 handling
In-Reply-To: <1504813050.77.0.505378891387.issue31387@psf.upfronthosting.co.za>
Message-ID: <1571094676.73.0.405076774504.issue31387@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
nosy: +aeros

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31387>
_______________________________________

From report at bugs.python.org  Mon Oct 14 19:43:37 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Mon, 14 Oct 2019 23:43:37 +0000
Subject: [issue28533] Replace asyncore
In-Reply-To: <1477420324.44.0.338895938894.issue28533@psf.upfronthosting.co.za>
Message-ID: <1571096617.94.0.854094101149.issue28533@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
nosy: +aeros

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28533>
_______________________________________

From report at bugs.python.org  Mon Oct 14 20:19:05 2019
From: report at bugs.python.org (Tim Peters)
Date: Tue, 15 Oct 2019 00:19:05 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1571098745.91.0.653023783074.issue38006@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

> I'm often amazed it works at all, let alone perfectly. ;-P

Indeed!  Every time I take a break from gc and come back, I burn another hour wondering why it doesn't recycle _everything_ ;-)

> But what happens if the GC doesn't see that WZ is trash?
> Then it will not be cleared.  Hang it off Y so the GC
> can't find it.

In that case it won't think C is trash either (a weakref holds a strong reference to its callback), so C won't be tp_clear'ed - if WZ isn't in the unreachable set, C can't be either.

> We can set things up so that Z is freed before WZ (e.g.
> WZ in a second and newer cycle).  Then, the callback
> might still run.

Since C hasn't been damaged, and nothing reachable from C would have been considered trash either, I don't see a problem.

> On further thought, this seems safe (but maybe broken) because
> of the handle_weakrefs() logic.  The GC will think WZ is going
> to outlive Z so it will call it before doing any tp_clear calls.

Don't think that applies.  As above, WZ isn't in the unreachable set, so gc knows nothing about it.

Z will eventually be reclaimed via refcounting side effect, C _will_ run, and then WZ, and then C, will be reclaimed by refcounting.

Or am I missing something?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Mon Oct 14 21:06:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 01:06:20 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1571101580.98.0.545851655769.issue36389@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset f82ce5b1b12873b65927149a016be6a7c65e979d by Victor Stinner in branch '3.8':
[3.8] bpo-36389: Backport debug enhancements from master (GH-16796)
https://github.com/python/cpython/commit/f82ce5b1b12873b65927149a016be6a7c65e979d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Mon Oct 14 21:06:21 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 01:06:21 +0000
Subject: [issue38376] ./configure --with-assertions generates a broken build
In-Reply-To: <1570279431.23.0.578903771856.issue38376@roundup.psfhosted.org>
Message-ID: <1571101581.09.0.114031990884.issue38376@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset f82ce5b1b12873b65927149a016be6a7c65e979d by Victor Stinner in branch '3.8':
[3.8] bpo-36389: Backport debug enhancements from master (GH-16796)
https://github.com/python/cpython/commit/f82ce5b1b12873b65927149a016be6a7c65e979d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38376>
_______________________________________

From report at bugs.python.org  Mon Oct 14 21:06:21 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 01:06:21 +0000
Subject: [issue38070] visit_decref(): add an assertion to check that the
 object is not freed
In-Reply-To: <1568037936.88.0.10373402622.issue38070@roundup.psfhosted.org>
Message-ID: <1571101581.16.0.978804837319.issue38070@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset f82ce5b1b12873b65927149a016be6a7c65e979d by Victor Stinner in branch '3.8':
[3.8] bpo-36389: Backport debug enhancements from master (GH-16796)
https://github.com/python/cpython/commit/f82ce5b1b12873b65927149a016be6a7c65e979d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38070>
_______________________________________

From report at bugs.python.org  Mon Oct 14 21:42:50 2019
From: report at bugs.python.org (Louis Huemiller)
Date: Tue, 15 Oct 2019 01:42:50 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
Message-ID: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>


New submission from Louis Huemiller <lhuemill at gmail.com>:

Have created a program that by brute force determines all reachable states of a 2-by-2 MagicCube, sometimes referred to as a 2x2 Rubick's cube. On one of my servers, which is described in the attached file 20191011b_configuration, this program takes 19520.03 seconds to execute under Python2.7.15+, while under 3.8.0rc1 it takes 21887.53 seconds. This program is taking 12.13% longer to execute with 3.8.0rc1 versus 2.7.15+. The exact versions of Python as reported by sys.version are:

  2.7.15+ (default, Oct  7 2019, 17:39:04)
  [GCC 7.4.0]

  3.8.0rc1 (default, Oct  1 2019, 21:48:24)
  [GCC 7.4.0]

Used the following script to execute this program under Python 2.7, 3.6, 3.7, and 3.8:

  mkdir -p ./results
  echo "======== git log ========" > ./results/20191011b_configuration
  git log -n4 >> ./results/20191011b_configuration

  echo ""  >> ./results/20191011b_configuration
  echo "======== uname ========" >> ./results/20191011b_configuration
  uname -a >> ./results/20191011b_configuration

  echo ""  >> ./results/20191011b_configuration
  echo "======== lsb_release ========" >> 
  ./results/20191011b_configuration
  lsb_release -a >> ./results/20191011b_configuration

  echo ""  >> ./results/20191011b_configuration
  echo "======== lshw ========" >> ./results/20191011b_configuration
  sudo lshw >> ./results/20191011b_configuration

  make clean
  make
  ./target/permutations2x2 > \
    ./results/20191011b_magiccube2x2_permutations_cxx_unordered_map 2>&1
  python3.8 ./permutations2x2  > \
    ./results/20191011b_magiccube2x2_permutations_python3.8.0rc1 2>&1
  python3.7 ./permutations2x2  > \
    ./results/20191011b_magiccube2x2_permutations_python3.7 2>&1
  python3.6 ./permutations2x2  > \
    ./results/20191011b_magiccube2x2_permutations_python3.6 2>&1
  python2.7 ./permutations2x2  > 
  ./results/20191011b_magiccube2x2_permutations_python2.7 2>&1

Doing egrep "^# Total_Time:" on each of the output files, shows that the various executions took the following amount of time:

  cxx_unordered_map:# Total_Time: 1098.25
  python2.7:# Total_Time: 19520.03
  python3.6:# Total_Time: 19562.28
  python3.7:# Total_Time: 17012.67
  python3.8.0rc1:# Total_Time: 21887.53

Under Python2.7 and Python3.6 the program ran in approximately the same amount of time, while under Python3.7 it ran 12.8% faster than execution with Python2.7. Finally, the python3.8.0rc1 execution is noticeably slower than all the other executions, at 12.1% lower than Python2.7 and 28.6% slower than Python3.7.

The source for the magic_cube2x2 program is available under gist.github.com at:

  https://gist.github.com/lhuemill/f1273291e5f5e85e4b42e5c7614e60ef

This program creates a fairly large dictionary of 88.179840M entries. Each entry has a key of a string of length 29 and a value string of with a maximum length of 22 characters. A quick back-of-the-envelope calculation shows that this dictionary would use approximately 9GB of memory, but for some reason, all of the Python executions use approximately 22.6GB of memory. Even the C++ version is using 20.2GB when the permutations are stored in an unordered_map<string, string> and 20.55GB when stored in a map<string, string>. Quite surprising that the C++ is using over twice the expected amount of memory.

  CAUTION: When executing this program with less than the needed
           amount of physical memory, be careful that swap is not
           backed by a flash device. Doing so will likely cause
           a significant amount of I/O to the flash device and
           likely quickly wear it out.

----------
files: 20191005b_configuration
messages: 354682
nosy: Louis Huemiller
priority: normal
severity: normal
status: open
title: magiccube2x2 permutations 28% slower with Python 3.8.0rc1 vs 3.7
type: performance
versions: Python 3.8
Added file: https://bugs.python.org/file48660/20191005b_configuration

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Mon Oct 14 22:26:32 2019
From: report at bugs.python.org (Brian Shaginaw)
Date: Tue, 15 Oct 2019 02:26:32 +0000
Subject: [issue38478] inspect.signature.bind does not correctly handle keyword
 argument with same name as positional-only parameter
Message-ID: <1571106392.69.0.85003046785.issue38478@roundup.psfhosted.org>


New submission from Brian Shaginaw <bshaginaw120 at gmail.com>:

>>> import inspect
>>> def foo(bar, /, **kwargs):
...   print(bar, kwargs)
...
>>> foo(1, bar=2)
1 {'bar': 2}
>>> inspect.signature(foo).bind(1, bar=2)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/inspect.py", line 3025, in bind
    return self._bind(args, kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/inspect.py", line 2964, in _bind
    raise TypeError(
TypeError: multiple values for argument 'bar'


Python 3.8 introduced positional-only parameters, which allow parameter names to remain available for use in **kwargs. It looks like `inspect.signature.bind` does not recognize this, and thinks the parameter is being passed twice, which causes the above TypeError.

Expected result: <BoundArguments (bar=1, kwargs={'bar': 2})>

----------
components: Library (Lib)
messages: 354683
nosy: brian.shaginaw
priority: normal
severity: normal
status: open
title: inspect.signature.bind does not correctly handle keyword argument with same name as positional-only parameter
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38478>
_______________________________________

From report at bugs.python.org  Mon Oct 14 22:54:53 2019
From: report at bugs.python.org (Eryk Sun)
Date: Tue, 15 Oct 2019 02:54:53 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571108093.22.0.601340157092.issue38470@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

I tested in Windows 10 with long paths disabled, and the FileNotFoundError exception showed that the failing .pyc had a numeric suffix appended to the name.

create_long_path isn't taking into account _write_atomic in Lib/importlib/_bootstrap_external.py. This function appends the id() of the target path string in order to create a temporary unique name, which it renames to the target if the write succeeds. Since the object ID is a memory address, create_long_path would need to append 16 characters to the longer_cache path. That's 1 for the initial "." of the suffix, plus 15 for the x64 address-space limit of 128 TB, i.e. len(str(0x7FFF_FFFF_FFFF)). 

Note that, by default, long-path support is not enabled in Windows 10. At process startup, the system runtime library enables long-path support if "LongPathsEnabled" is set in "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" and the application manifest enables "longPathAware". Both settings are required.

For the buildbots, pythoninfo checks this as "windows.RtlAreLongPathsEnabled". According to this, for example, bolen-windows10 does not have long paths enabled. Yet test_compileall passed. 

bolen-windows10
https://buildbot.python.org/all/#/builders/3/builds/3681/steps/3/logs/stdio

It seems the test passed because the temp directory on this bot is relatively short: "D:\Temp". That's a factor because create_long_path adds directory components in blocks of 10. It uses 20 "dir_X_Y" components because 30 (240 characters) is too much for MAX_PATH no matter what. 

The same applies to the following buildbots for Windows 7 and 8.1:

bolen-windows7
https://buildbot.python.org/all/#/builders/58/builds/3148/steps/3/logs/stdio

ware-win81-release
https://buildbot.python.org/all/#/builders/12/builds/3360/steps/3/logs/stdio

On the other hand, kloth-win64 has a longer path for its temp directory: "C:\Users\Buildbot\AppData\Local\Temp". This costs an additional 29 characters compared to "D:\Temp" and brings the final path very close to MAX_PATH. The suffix appended by _write_atomic is typically 14-16 characters, which then exceeds MAX_PATH.

----------
nosy: +eryksun

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Mon Oct 14 23:01:38 2019
From: report at bugs.python.org (Tim Peters)
Date: Tue, 15 Oct 2019 03:01:38 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1571108498.55.0.505360007306.issue38006@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

> While Neil & I haven't thought of ways that can go wrong now
> beyond that a "surprise finalizer" may get run any number of
> times ...

Speaking of which, I no longer believe that's true.  Thanks to the usual layers of baffling renaming via macro after macro, I missed object.c's PyObject_CallFinalizerFromDealloc(), which both respects and sets the "am I finalized?" flag regardless of how, e.g., an object with a __del__ ends its life (and possibly resurrects).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Mon Oct 14 23:28:50 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 15 Oct 2019 03:28:50 +0000
Subject: [issue38478] inspect.signature.bind does not correctly handle keyword
 argument with same name as positional-only parameter
In-Reply-To: <1571106392.69.0.85003046785.issue38478@roundup.psfhosted.org>
Message-ID: <1571110130.66.0.745379662649.issue38478@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 00:29:02 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 15 Oct 2019 04:29:02 +0000
Subject: [issue38288] shutil.make_archive() should allow setting
 zipfile.ZipFile() 'strict_timestamps'
In-Reply-To: <1569516230.4.0.693896047629.issue38288@roundup.psfhosted.org>
Message-ID: <1571113742.85.0.71577681599.issue38288@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38288>
_______________________________________

From report at bugs.python.org  Tue Oct 15 01:31:30 2019
From: report at bugs.python.org (Young Y)
Date: Tue, 15 Oct 2019 05:31:30 +0000
Subject: [issue38479] Segmentation fault: 11 Python3.6 on Macbook
Message-ID: <1571117490.83.0.0706569063391.issue38479@roundup.psfhosted.org>


New submission from Young Y <honglou2001 at gmail.com>:

Segmentation fault: 11Process:               Python [5343]
Path:                  /Library/Frameworks/Python.framework/Versions/3.6/Resources/Python.app/Contents/MacOS/Python
Identifier:            Python
Version:               3.6.5 (3.6.5)
Code Type:             X86-64 (Native)
Parent Process:        bash [3524]
Responsible:           Python [5343]
User ID:               501

Date/Time:             2019-10-15 13:26:45.395 +0800
OS Version:            Mac OS X 10.14.1 (18B75)
Report Version:        12
Anonymous UUID:        4552DCD6-6528-6E1A-0C86-24A09F7835F8


Time Awake Since Boot: 9600 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000201c49b57
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [5343]

VM Regions Near 0x201c49b57:
    VM_ALLOCATE            0000000181c4a000-0000000181c4b000 [    4K] r-x/rwx SM=PRV  
--> 
    __UNIXSTACK            00007fff5b000000-00007fff5c000000 [ 16.0M] rw-/rwx SM=ALI  /Library/Frameworks/Python.framework/Versions/3.6/Resources/Python.app/Contents/MacOS/Python

Application Specific Information:
dyld: launch, running initializers
/Library/Application Support/Cylance/Desktop/CyMemDef.dylib

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ???                           	0x0000000201c49b57 0 + 8619596631
1   CyMemDef.dylib                	0x0000000100a77737 _vm_protect(unsigned int, unsigned long, unsigned long, unsigned int, int) + 149
2   CyMemDef.dylib                	0x0000000100a73e3e mach_override_setup + 219
3   CyMemDef.dylib                	0x0000000100a79297 injector(inject_s*, unsigned long) + 355
4   CyMemDef.dylib                	0x0000000100a790a5 MemDefMemory_initialize() + 35
5   CyMemDef.dylib                	0x0000000100a77050 memdefosx_initialize + 28
6   dyld                          	0x00007fff5f67dcc8 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 518
7   dyld                          	0x00007fff5f67dec6 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
8   dyld                          	0x00007fff5f6790da ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, char const*, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 358
9   dyld                          	0x00007fff5f67906d ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, char const*, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 249
10  dyld                          	0x00007fff5f678254 ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 134
11  dyld                          	0x00007fff5f6782e8 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 74
12  dyld                          	0x00007fff5f667774 dyld::initializeMainExecutable() + 199
13  dyld                          	0x00007fff5f66c78f dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 6237
14  dyld                          	0x00007fff5f6664f6 dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 1154
15  dyld                          	0x00007fff5f666036 _dyld_start + 54

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000100a94178  rbx: 0x0000000101c4ab3a  rcx: 0x0000000000000000  rdx: 0x0000000000000008
  rdi: 0x0000000000000103  rsi: 0x0000000101c4ab3a  rbp: 0x00007fff5bffdef0  rsp: 0x00007fff5bffdaa8
   r8: 0x0000000000000005   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000246
  r12: 0x0000000000000005  r13: 0x0000000000000103  r14: 0x0000000000000000  r15: 0x0000000000000008
  rip: 0x0000000201c49b57  rfl: 0x0000000000010246  cr2: 0x0000000201c49b57
  
Logical CPU:     1
Error Code:      0x00000014
Trap Number:     14


Binary Images:
       0x100000000 -        0x100000ff7 +org.python.python (3.6.5 - 3.6.5) <C539EB14-B454-D151-7B93-6A12255582B2> /Library/Frameworks/Python.framework/Versions/3.6/Resources/Python.app/Contents/MacOS/Python
       0x100003000 -        0x100450fe7  com.apple.CoreFoundation (6.9 - 1560.12) <B5BDC307-6C89-3DE0-B4B9-4C2C650E4528> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
       0x1006fb000 -        0x100922fef +org.python.python (3.6.5, [c] 2001-2018 Python Software Foundation. - 3.6.5) <EBF198CD-A37E-A0F1-1E7C-19B9F912D34A> /Library/Frameworks/Python.framework/Versions/3.6/Python
       0x100a6b000 -        0x100a6cffb  libSystem.B.dylib (1252.200.5) <D5AFCC78-2AC2-37EB-B0EF-BB00FD38ED00> /usr/lib/libSystem.B.dylib
       0x100a72000 -        0x100a83ff7 +CyMemDef.dylib (0) <7F2E0690-20B4-335A-AE40-D51A0FD1582F> /Library/Application Support/Cylance/*/CyMemDef.dylib
       0x100ab5000 -        0x10123bfe7  libobjc.A.dylib (750.1) <9CE27EC3-3A12-35D1-8F2F-3550B9668259> /usr/lib/libobjc.A.dylib
       0x1013f3000 -        0x1013f4ff7  libDiagnosticMessagesClient.dylib (107) <C542CB3C-AA44-3D7F-B88C-79CC31B481AB> /usr/lib/libDiagnosticMessagesClient.dylib
       0x1013fa000 -        0x10165dffb  libicucore.A.dylib (62108.0.1) <969815D4-A345-31BB-82B7-0C3B58CA7E90> /usr/lib/libicucore.A.dylib
       0x10174b000 -        0x10175dffb  libz.1.dylib (70.200.4) <99A3D725-8388-38B4-B66C-5E9006E6F072> /usr/lib/libz.1.dylib
       0x101763000 -        0x101778fff  libc++abi.dylib (400.17) <BA948A32-9024-3E55-98D4-18E31F6AED25> /usr/lib/libc++abi.dylib
       0x10178f000 -        0x1017e6ff7  libc++.1.dylib (400.9.4) <D4AB366F-48A9-3C7D-91BD-41198F69DD57> /usr/lib/libc++.1.dylib
       0x101847000 -        0x10184bff3  libcache.dylib (81) <FE21A7E9-DBEB-33AC-836B-785AD036ACF4> /usr/lib/system/libcache.dylib
       0x101851000 -        0x10185bff3  libcommonCrypto.dylib (60118.220.1) <1099E427-6E81-3059-87AF-6F5FD81CA998> /usr/lib/system/libcommonCrypto.dylib
       0x101869000 -        0x101870fff  libcompiler_rt.dylib (63.4) <A4D9CF37-D076-3CE9-95F1-DA89DA1601B6> /usr/lib/system/libcompiler_rt.dylib
       0x10187e000 -        0x101887ff3  libcopyfile.dylib (146.200.3) <4BCDADBF-79F5-3829-B47D-64DA0D44BCBF> /usr/lib/system/libcopyfile.dylib
       0x10188e000 -        0x101912fdf  libcorecrypto.dylib (602.220.6) <E1046E01-A2FD-35B4-B018-ACC372F3880E> /usr/lib/system/libcorecrypto.dylib
       0x10192f000 -        0x101969ff7  libdispatch.dylib (1008.220.2) <D8B56783-152A-34A8-94E9-8E6BAE049384> /usr/lib/system/libdispatch.dylib
       0x10199a000 -        0x1019c9fff  libdyld.dylib (635.2) <1B79A5CE-125F-301F-A441-C1869573AED0> /usr/lib/system/libdyld.dylib
       0x1019ec000 -        0x1019ecffb  libkeymgr.dylib (30) <A73AA788-C35C-3284-BFCA-95B1BBDF0CF3> /usr/lib/system/libkeymgr.dylib
       0x1019f1000 -        0x1019f1ff7  liblaunch.dylib (1336.220.5) <95EB6EAF-2DC5-344F-BADB-CA4E35E4E503> /usr/lib/system/liblaunch.dylib
       0x1019f8000 -        0x1019fdfff  libmacho.dylib (921) <ECC4E97C-575E-3A08-8191-BF02D7D4E637> /usr/lib/system/libmacho.dylib
       0x101a04000 -        0x101a06ffb  libquarantine.dylib (86.220.1) <6AE5AEEC-A9FD-3CF8-92DD-12B5AFBE12DE> /usr/lib/system/libquarantine.dylib
       0x101a0d000 -        0x101a0eff3  libremovefile.dylib (45.200.2) <D74A307B-3DC7-3992-B16C-DACB8207BE13> /usr/lib/system/libremovefile.dylib
       0x101a14000 -        0x101a2bff3  libsystem_asl.dylib (356.200.4) <EC9D8AD4-E5CB-3765-804A-9E1E9DC045D2> /usr/lib/system/libsystem_asl.dylib
       0x101a39000 -        0x101a39fff  libsystem_blocks.dylib (73) <26419398-C30C-30F1-B656-A92AFA9560F6> /usr/lib/system/libsystem_blocks.dylib
       0x101a3e000 -        0x101ac6fff  libsystem_c.dylib (1272.200.26) <3DEEE96E-6DF6-35AD-8654-D69AC26B907B> /usr/lib/system/libsystem_c.dylib
       0x101aef000 -        0x101af2ff7  libsystem_configuration.dylib (963.200.27) <02CC3996-B34E-333C-8806-AE2699D34424> /usr/lib/system/libsystem_configuration.dylib
       0x101af9000 -        0x101afcff7  libsystem_coreservices.dylib (66) <254B6849-2C8F-302C-8616-B8324A11AB30> /usr/lib/system/libsystem_coreservices.dylib
       0x101b02000 -        0x101b08ffb  libsystem_darwin.dylib (1272.200.26) <974E9EF7-DE72-34B7-B056-0A81C10DF8EB> /usr/lib/system/libsystem_darwin.dylib
       0x101b13000 -        0x101b19ff7  libsystem_dnssd.dylib (878.200.35) <FFC665AA-B257-35AD-BD8B-32FD42C2EEC1> /usr/lib/system/libsystem_dnssd.dylib
       0x101b1f000 -        0x101b6bff3  libsystem_info.dylib (517.200.9) <0707C387-D7DE-372E-8FF1-3DE5C91932D6> /usr/lib/system/libsystem_info.dylib
       0x101b82000 -        0x101bcdff7  libsystem_m.dylib (3158.200.7) <43D1796B-954F-37D6-B1AC-9D80DF0655A2> /usr/lib/system/libsystem_m.dylib
       0x101bdc000 -        0x101c00ff7  libsystem_malloc.dylib (166.220.1) <3B196122-4E0D-3E3F-AA3E-5115B976DE26> /usr/lib/system/libsystem_malloc.dylib
       0x101c0f000 -        0x101c1aff3  libsystem_networkextension.dylib (767.220.1) <C54EB8F6-F305-3452-8DB1-F7DA6859AF8C> /usr/lib/system/libsystem_networkextension.dylib
       0x101c27000 -        0x101c2efff  libsystem_notify.dylib (172.200.21) <BCCB222F-DC64-3954-A836-DCCE6659CA5A> /usr/lib/system/libsystem_notify.dylib
       0x101c35000 -        0x101c38ff7  libsystem_sandbox.dylib (851.220.9) <4D6433A8-C703-3ED9-82EB-B9E481A0FD2F> /usr/lib/system/libsystem_sandbox.dylib
       0x101c3f000 -        0x101c41ff3  libsystem_secinit.dylib (30.220.1) <6C681113-8C48-3256-BEF6-0C3723DEB926> /usr/lib/system/libsystem_secinit.dylib
       0x101c47000 -        0x101c6eff7  libsystem_kernel.dylib (4903.221.2) <0E882078-7330-3B49-AA5D-3CDB5645A4E5> /usr/lib/system/libsystem_kernel.dylib
       0x101c89000 -        0x101c92fef  libsystem_platform.dylib (177.200.16) <B75B04AD-69FE-3ADE-84D2-C17972FC8F49> /usr/lib/system/libsystem_platform.dylib
       0x101c9b000 -        0x101ca5fff  libsystem_pthread.dylib (330.220.2) <4958273C-4273-3501-8137-E44249E10D9C> /usr/lib/system/libsystem_pthread.dylib
       0x101cb0000 -        0x101cb7ff7  libsystem_symptoms.dylib (820.227.2) <3147D594-F41F-35FD-BF0B-6B8B66A407DE> /usr/lib/system/libsystem_symptoms.dylib
       0x101cbe000 -        0x101cd3ff7  libsystem_trace.dylib (906.220.1) <D5045DC5-A165-3238-A470-1796F12BF84F> /usr/lib/system/libsystem_trace.dylib
       0x101ce3000 -        0x101ce8ffb  libunwind.dylib (35.4) <41222EF6-2233-3CF4-947A-15D48CB8C030> /usr/lib/system/libunwind.dylib
       0x101cf0000 -        0x101d20fff  libxpc.dylib (1336.220.5) <B2137772-E202-3656-A089-F6DD517007D5> /usr/lib/system/libxpc.dylib
    0x7fff5f665000 -     0x7fff5f6e36a7  dyld (635.2) <1780094A-8FE2-3EAA-B4A3-C4CF14BC5196> /usr/lib/dyld

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 26541
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=25.4M resident=0K(0%) swapped_out_or_unallocated=25.4M(100%)
Writable regions: Total=25.5M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=25.5M(100%)
 
                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Kernel Alloc Once                    8K        2 
MALLOC                            9260K        8 
MALLOC guard page                   16K        5 
VM_ALLOCATE                          4K        2 
__DATA                            4316K       59 
__LINKEDIT                        4768K       46 
__TEXT                            20.7M       48 
__UNICODE                          564K        2 
__UNIXSTACK                       16.0M        2 
shared memory                        8K        3 
===========                     =======  ======= 
TOTAL                             55.2M      167 

Model: MacBookPro14,1, BootROM 184.0.0.0.0, 2 processors, Intel Core i5, 2.3 GHz, 16 GB, SMC 2.43f6
Graphics: Intel Iris Plus Graphics 640, Intel Iris Plus Graphics 640, Built-In
Memory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320
Memory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x170), Broadcom BCM43xx 1.0 (7.77.61.1 AirPortDriverBrcmNIC-1305.2)
Bluetooth: Version 6.0.9f2, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.0 Bus
USB Device: USB 2.0 BILLBOARD
Thunderbolt Bus: MacBook Pro, Apple Inc., 39.2

----------
messages: 354686
nosy: Young Y
priority: normal
severity: normal
status: open
title: Segmentation fault: 11 Python3.6 on Macbook
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38479>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:01:13 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:01:13 +0000
Subject: [issue38479] Segmentation fault: 11 Python3.6 on Macbook
In-Reply-To: <1571117490.83.0.0706569063391.issue38479@roundup.psfhosted.org>
Message-ID: <1571122873.58.0.462006129734.issue38479@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Your system appears to be running Cylance, which I gather is some sort of third-party virus protection system; from the system crash trace, the crash ssems to have happened in /Library/Application Support/Cylance/Desktop/CyMemDef.dylib which presumably is part of Cylance.  I suggest you try disabling it or contacting the vendor for support.  Note also that Python 3.6.5 is no longer supported; as of today, 3.8.0 is now available and 3.7.x has been and will be supported for some time.

Good luck!

----------
nosy: +ned.deily
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38479>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:26:20 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Tue, 15 Oct 2019 07:26:20 +0000
Subject: [issue11410] Use GCC visibility attrs in PyAPI_*
In-Reply-To: <1299391945.72.0.037942723875.issue11410@psf.upfronthosting.co.za>
Message-ID: <1571124380.1.0.368573984138.issue11410@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset 0b60f64e4343913b4931dc27379d9808e5b78fe1 by Vinay Sajip in branch 'master':
bpo-11410: Standardize and use symbol visibility attributes across POSIX and Windows. (GH-16347)
https://github.com/python/cpython/commit/0b60f64e4343913b4931dc27379d9808e5b78fe1


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue11410>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:23 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:23 +0000
Subject: [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1571124623.98.0.454507824339.issue32996@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset 49e650b2489da861d4c49b41787160f30d8259bf by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-32996: Documentation fix-up. (GH-16646)
https://github.com/python/cpython/commit/49e650b2489da861d4c49b41787160f30d8259bf


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32996>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:24 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:24 +0000
Subject: [issue36953] Remove collections ABCs?
In-Reply-To: <1558140764.46.0.049733618419.issue36953@roundup.psfhosted.org>
Message-ID: <1571124624.8.0.0301524056913.issue36953@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset 42b16b2a867ad3f6c022476076da3d6ea789021b by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-36953: Delay removal of ABCs from collections. (GH-13409)
https://github.com/python/cpython/commit/42b16b2a867ad3f6c022476076da3d6ea789021b


----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36953>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:24 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:24 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1571124624.59.0.543878878431.issue38368@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset 1c61f2cc7ab44591b1832307a4022c927502d446 by Ned Deily (Vinay Sajip) in branch '3.7':
bpo-38368: Added fix for ctypes crash when handling arrays in structs/unions. (GH-16589) (GH-16672)
https://github.com/python/cpython/commit/1c61f2cc7ab44591b1832307a4022c927502d446


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:25 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:25 +0000
Subject: [issue38294] Documentation on 3.6->3.7 re.escape no longer escaping
 "/" or ":" should be obvious
In-Reply-To: <1569603997.59.0.0237297108404.issue38294@roundup.psfhosted.org>
Message-ID: <1571124625.77.0.923987431526.issue38294@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset ae41f629e187e1f0cf4d62f5a7b181c64da26466 by Ned Deily (Ricardo B?nffy) in branch '3.7':
[3.7] bpo-38294: Add list of no-longer-escaped chars to re.escape documentation. (GH-16442) (GH-16647)
https://github.com/python/cpython/commit/ae41f629e187e1f0cf4d62f5a7b181c64da26466


----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38294>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:24 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:24 +0000
Subject: [issue28556] typing.py upgrades
In-Reply-To: <1477756009.46.0.442279756181.issue28556@psf.upfronthosting.co.za>
Message-ID: <1571124624.26.0.366919524776.issue28556@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset bd9a70c2c177d2f99f63d87b865e6e9c2936ba2e by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-28556: Remove another mention of metaclass of Generic in typing docs (GH-16743)
https://github.com/python/cpython/commit/bd9a70c2c177d2f99f63d87b865e6e9c2936ba2e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28556>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:25 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:25 +0000
Subject: [issue38235] Docs of logging module says argument is named "lvl".
 TypeError.
In-Reply-To: <1568996817.83.0.32795106699.issue38235@roundup.psfhosted.org>
Message-ID: <1571124625.25.0.283359174741.issue38235@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset 6eb554583218cda9a145982a41c30612968a942f by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-38235: Correct some arguments names in logging documentation (GH-16571) (GH-16577)
https://github.com/python/cpython/commit/6eb554583218cda9a145982a41c30612968a942f


----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38235>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:25 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:25 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1571124625.48.0.0505856465433.issue38449@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset 2a405598bbccbc42710dc5ecf3d44c8de4c16582 by Ned Deily (Abhilash Raj) in branch '3.7':
[3.7] bpo-38449: Revert "bpo-22347: Update mimetypes.guess_type to allow oper parsing of URLs (GH-15685)" (GH-16724) (GH-16727)
https://github.com/python/cpython/commit/2a405598bbccbc42710dc5ecf3d44c8de4c16582


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:25 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:25 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1571124625.89.0.376046184361.issue38344@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset ab22c8bc488e822d03c4778b30ec60131ea35c63 by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-38344: Fix syntax in activate.bat (GH-16533)
https://github.com/python/cpython/commit/ab22c8bc488e822d03c4778b30ec60131ea35c63


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:24 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:24 +0000
Subject: [issue34344] Fix the docstring for
 AbstractEventLoopPolicy.get_event_loop
In-Reply-To: <1533549887.39.0.56676864532.issue34344@psf.upfronthosting.co.za>
Message-ID: <1571124624.42.0.843528508782.issue34344@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset 88204a3908663a574919f9c17278bcabed0598fa by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-34344 Fix AbstractEventLoopPolicy.get_event_loop docstring (GH-16463)
https://github.com/python/cpython/commit/88204a3908663a574919f9c17278bcabed0598fa


----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34344>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:25 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:25 +0000
Subject: [issue22347] mimetypes.guess_type("//example.com") misinterprets host
 name as file name
In-Reply-To: <1409971957.28.0.64915967452.issue22347@psf.upfronthosting.co.za>
Message-ID: <1571124625.65.0.978754717156.issue22347@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset 2a405598bbccbc42710dc5ecf3d44c8de4c16582 by Ned Deily (Abhilash Raj) in branch '3.7':
[3.7] bpo-38449: Revert "bpo-22347: Update mimetypes.guess_type to allow oper parsing of URLs (GH-15685)" (GH-16724) (GH-16727)
https://github.com/python/cpython/commit/2a405598bbccbc42710dc5ecf3d44c8de4c16582


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22347>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:26 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:26 +0000
Subject: [issue26510] [argparse] Add required argument to add_subparsers
In-Reply-To: <1457445361.5.0.530669445668.issue26510@psf.upfronthosting.co.za>
Message-ID: <1571124626.28.0.538094229461.issue26510@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset f168c17b075b4103eaf1f619acd3bca3890fbac7 by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-26510: Add versionchanged for required arg of add_subparsers (GH-16588)
https://github.com/python/cpython/commit/f168c17b075b4103eaf1f619acd3bca3890fbac7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26510>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:30:25 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:30:25 +0000
Subject: [issue38391] Typo in tutorial code (does not compile)
In-Reply-To: <1570440981.11.0.0420917562712.issue38391@roundup.psfhosted.org>
Message-ID: <1571124625.09.0.0633399690746.issue38391@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset e9c65b4ae765ccd381eccdfc4617dc46899406e1 by Ned Deily (Miss Islington (bot)) in branch '3.7':
bpo-38391: Fixing a typo for Py_DECREF (GH-16616)
https://github.com/python/cpython/commit/e9c65b4ae765ccd381eccdfc4617dc46899406e1


----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38391>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:34:20 2019
From: report at bugs.python.org (Giampaolo Rodola')
Date: Tue, 15 Oct 2019 07:34:20 +0000
Subject: [issue38480] resource.setrlimit() should raise PermissionError
Message-ID: <1571124860.16.0.598909630124.issue38480@roundup.psfhosted.org>


New submission from Giampaolo Rodola' <g.rodola at gmail.com>:

>>> import resource
    >>> high = 300 * 1024 * 1024
    >>> resource.setrlimit(resource.RLIMIT_MEMLOCK, (high, high))
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
    ValueError: not allowed to raise maximum limit
    >>> 

Internally EPERM is translated into ValueError (should have been PermissionError). resource.prlimit(), on the other hand, is not affected (correctly raises PermissionError):

    >>> resource.prlimit(os.getpid(), resource.RLIMIT_MEMLOCK, (high, high))
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
    PermissionError: [Errno 1] Operation not permitted


It seems 'ValueError' was used in order to provide a more informative error message, but IMO it was a bad call.
Proposal is to change this in 3.9 only, and document it under whatsnew/porting.

----------
components: Library (Lib)
messages: 354701
nosy: giampaolo.rodola
priority: normal
severity: normal
status: open
title: resource.setrlimit() should raise PermissionError
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38480>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:36:40 2019
From: report at bugs.python.org (=?utf-8?b?5qWa6Im6?=)
Date: Tue, 15 Oct 2019 07:36:40 +0000
Subject: [issue38481] Class static property not static
Message-ID: <1571125000.71.0.339898408736.issue38481@roundup.psfhosted.org>


New submission from ?? <1090217062 at qq.com>:

code:
------------------------------------------------------------------
    class D:
        num = 0
        
        def __init__(self):
            self.num += 1
            print('D num', self.num)

    for i in range(5):
        D()
---------------------------------------------------------------
console print:
---------------------------------------------------------------
Connected to pydev debugger (build 183.5429.31)
D num 1
D num 1
D num 1
D num 1
D num 1

Process finished with exit code 0

----------
components: Windows
messages: 354702
nosy: chuyi, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Class static property not static
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38481>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:42:24 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:42:24 +0000
Subject: [issue38344] activate.bat else needs to be on the same line as the if
In-Reply-To: <1569997823.02.0.0977203709428.issue38344@roundup.psfhosted.org>
Message-ID: <1571125344.98.0.758436296342.issue38344@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

(3.7.5 is released with this fix)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38344>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:44:07 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:44:07 +0000
Subject: [issue38368] Crash when subclassing ctypes.Union
In-Reply-To: <1570178161.94.0.1951756088.issue38368@roundup.psfhosted.org>
Message-ID: <1571125447.77.0.242535461479.issue38368@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

(fix released in 3.8.0 and 3.7.5)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38368>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:45:01 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 07:45:01 +0000
Subject: [issue38449] regression - mimetypes guess_type is confused by ;
 in the filename
In-Reply-To: <1570802800.7.0.378651276775.issue38449@roundup.psfhosted.org>
Message-ID: <1571125501.29.0.0320567965733.issue38449@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

(fix also released in 3.7.5)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38449>
_______________________________________

From report at bugs.python.org  Tue Oct 15 03:47:21 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 15 Oct 2019 07:47:21 +0000
Subject: [issue38481] Class static property not static
In-Reply-To: <1571125000.71.0.339898408736.issue38481@roundup.psfhosted.org>
Message-ID: <1571125641.33.0.645728489533.issue38481@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

When you assign to self.num, you're creating an instance variable which hides the class variable. Instead, assign directly to the class variable:

class D:
    num = 0
    def __init__(self):
        D.num += 1
        print('D num', self.num)

for i in range(5):
    D()

D num 1
D num 2
D num 3
D num 4
D num 5

----------
nosy: +eric.smith
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38481>
_______________________________________

From report at bugs.python.org  Tue Oct 15 04:21:30 2019
From: report at bugs.python.org (Jim Carroll)
Date: Tue, 15 Oct 2019 08:21:30 +0000
Subject: [issue38482] BUG in codecs.BufferedIncrementalDecoder
Message-ID: <1571127690.05.0.477916235895.issue38482@roundup.psfhosted.org>


New submission from Jim Carroll <jim at carroll.com>:

While working with codecs.iterdecode(), encountered "can't concat int to bytes". The source of the problem is BufferedIncrementalDecoder stores it's internal buffer as a bytes (ie: b""), but decode() can be passed either a byte string or in the case of iterdecode() an int.  The solution is to test for this in the decode and if passed an int to coerce to bytes (see attach patch)

Platform: Python 3.7.4 (tags/v3.7.4:e09359112e, Jul  8 2019, 20:34:20) [MSC v.1916 64 bit (AMD64)] on win32

Code to demonstrate the issue:

>>> import codecs
>>> source = ''.join([chr(x) for x in range(256)])
>>> enc = b''.join(codecs.iterencode(source, 'utf-8'))
>>> list(''.join(codecs.iterdecode(enc, 'utf-8')))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Python37\lib\codecs.py", line 1048, in iterdecode
    output = decoder.decode(input)
  File "C:\Python37\lib\codecs.py", line 321, in decode
    data = self.buffer + input
TypeError: can't concat int to bytes

----------
components: Library (Lib)
files: codecs.patch
keywords: patch
messages: 354707
nosy: jamercee
priority: normal
severity: normal
status: open
title: BUG in codecs.BufferedIncrementalDecoder
versions: Python 3.7
Added file: https://bugs.python.org/file48661/codecs.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38482>
_______________________________________

From report at bugs.python.org  Tue Oct 15 04:25:03 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 15 Oct 2019 08:25:03 +0000
Subject: [issue38478] inspect.signature.bind does not correctly handle keyword
 argument with same name as positional-only parameter
In-Reply-To: <1571106392.69.0.85003046785.issue38478@roundup.psfhosted.org>
Message-ID: <1571127903.25.0.286805018874.issue38478@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
assignee:  -> pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 04:26:27 2019
From: report at bugs.python.org (Jim Carroll)
Date: Tue, 15 Oct 2019 08:26:27 +0000
Subject: [issue38482] BUG in codecs.BufferedIncrementalDecoder
In-Reply-To: <1571127690.05.0.477916235895.issue38482@roundup.psfhosted.org>
Message-ID: <1571127987.58.0.203234767329.issue38482@roundup.psfhosted.org>


Change by Jim Carroll <jim at carroll.com>:


Removed file: https://bugs.python.org/file48661/codecs.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38482>
_______________________________________

From report at bugs.python.org  Tue Oct 15 04:27:39 2019
From: report at bugs.python.org (Jim Carroll)
Date: Tue, 15 Oct 2019 08:27:39 +0000
Subject: [issue38482] BUG in codecs.BufferedIncrementalDecoder
In-Reply-To: <1571127690.05.0.477916235895.issue38482@roundup.psfhosted.org>
Message-ID: <1571128059.37.0.45527253173.issue38482@roundup.psfhosted.org>


Change by Jim Carroll <jim at carroll.com>:


Added file: https://bugs.python.org/file48662/codecs.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38482>
_______________________________________

From report at bugs.python.org  Tue Oct 15 04:36:48 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Tue, 15 Oct 2019 08:36:48 +0000
Subject: [issue16575] ctypes: unions as arguments
In-Reply-To: <1354163044.21.0.431588472559.issue16575@psf.upfronthosting.co.za>
Message-ID: <1571128608.98.0.022334711095.issue16575@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests: +16355
pull_request: https://github.com/python/cpython/pull/16799

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16575>
_______________________________________

From report at bugs.python.org  Tue Oct 15 05:26:22 2019
From: report at bugs.python.org (Petr Viktorin)
Date: Tue, 15 Oct 2019 09:26:22 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571131582.23.0.460436739469.issue38470@roundup.psfhosted.org>


Petr Viktorin <encukou at gmail.com> added the comment:


New changeset eb1dda2b56f67f09352c303588c28880c471ae87 by Petr Viktorin (Victor Stinner) in branch 'master':
bpo-38470: Fix test_compileall.test_compile_dir_maxlevels() (GH-16789)
https://github.com/python/cpython/commit/eb1dda2b56f67f09352c303588c28880c471ae87


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Tue Oct 15 05:50:00 2019
From: report at bugs.python.org (Arnaud Diederen)
Date: Tue, 15 Oct 2019 09:50:00 +0000
Subject: [issue37633] Py_CompileString and PyParser_SimpleParseString not
 exported in python38.dll
In-Reply-To: <1563568606.34.0.923231546212.issue37633@roundup.psfhosted.org>
Message-ID: <1571133000.39.0.490654278482.issue37633@roundup.psfhosted.org>


Arnaud Diederen <aundro at gmail.com> added the comment:

Python 3.8 was released yesterday, but this issue was unfortunately not addressed, making it as an embedded runtime.

Are there plans to fix this for a minor 3.8 release?

Thanks!

----------
nosy: +Arnaud Diederen

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37633>
_______________________________________

From report at bugs.python.org  Tue Oct 15 06:21:32 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 15 Oct 2019 10:21:32 +0000
Subject: [issue37633] Py_CompileString and PyParser_SimpleParseString not
 exported in python38.dll
In-Reply-To: <1563568606.34.0.923231546212.issue37633@roundup.psfhosted.org>
Message-ID: <1571134892.93.0.268312951372.issue37633@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37633>
_______________________________________

From report at bugs.python.org  Tue Oct 15 06:40:56 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 15 Oct 2019 10:40:56 +0000
Subject: [issue38478] inspect.signature.bind does not correctly handle keyword
 argument with same name as positional-only parameter
In-Reply-To: <1571106392.69.0.85003046785.issue38478@roundup.psfhosted.org>
Message-ID: <1571136056.12.0.893748476053.issue38478@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +patch
pull_requests: +16356
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16800

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 06:42:08 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 15 Oct 2019 10:42:08 +0000
Subject: [issue38478] inspect.signature.bind does not correctly handle keyword
 argument with same name as positional-only parameter
In-Reply-To: <1571106392.69.0.85003046785.issue38478@roundup.psfhosted.org>
Message-ID: <1571136128.19.0.639026895846.issue38478@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Thanks, Brian for the report!

I have a fix ready. When merged, this will be available in the next release.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 06:42:19 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 15 Oct 2019 10:42:19 +0000
Subject: [issue38478] inspect.signature.bind does not correctly handle keyword
 argument with same name as positional-only parameter
In-Reply-To: <1571106392.69.0.85003046785.issue38478@roundup.psfhosted.org>
Message-ID: <1571136139.25.0.623337701885.issue38478@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 06:42:54 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Oct 2019 10:42:54 +0000
Subject: [issue38482] BUG in codecs.BufferedIncrementalDecoder
In-Reply-To: <1571127690.05.0.477916235895.issue38482@roundup.psfhosted.org>
Message-ID: <1571136174.39.0.266149665327.issue38482@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

The first argument of iterdecode() should be an iterable of bytes objects, not a bytes object. Try codecs.iterdecode([enc], 'utf-8')

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38482>
_______________________________________

From report at bugs.python.org  Tue Oct 15 06:51:40 2019
From: report at bugs.python.org (Cooper Lees)
Date: Tue, 15 Oct 2019 10:51:40 +0000
Subject: [issue38483] [venv] Add ~/.venvrc to change module defaults
Message-ID: <1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>


New submission from Cooper Lees <me at cooperlees.com>:

I'd like to propose adding a run commands (.venvrc) file support to the venv library.

File Location: `~/.venvrc`

This file will support all current CLI arguments and override the defaults for each CLI if present in the file. I will also endeavour to add test for POSIX + Windows systems.

I propose using `configparser` and an `.ini` style config for the `.venvrc`.

My main use for this is to allow myself to default to always using `--upgrade-deps` when I create new venvs.

Thoughts? Concerns?

----------
components: Library (Lib)
messages: 354712
nosy: cooperlees
priority: normal
severity: normal
status: open
title: [venv] Add ~/.venvrc to change module defaults
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38483>
_______________________________________

From report at bugs.python.org  Tue Oct 15 07:15:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 11:15:53 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571138153.76.0.572646443902.issue37759@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

What's New in Python 3.8:

* functools.singledispatchmethod is missing
https://docs.python.org/dev/library/functools.html#functools.singledispatchmethod

* About "Added new multiprocessing.shared_memory module. (Contributed by Davin Potts in bpo-35813.)". Comment on Hacker News: "Hard to understand why this is so far down. This is fantastic news!" and "Shared Memory is the star of this release IMHO." I agree with that :-)

* Maybe PYTHONCACHEPREFIX should be better highlighted? "Anyone else most excited about PYTHONCACHEPREFIX? :-P" and "Not sure about most excited, but I am looking forward to setting PYTHONCACHEPREFIX to a location that isn't in a volume mounted into my Docker container for development."

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Tue Oct 15 07:40:18 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 15 Oct 2019 11:40:18 +0000
Subject: [issue38478] inspect.signature.bind does not correctly handle keyword
 argument with same name as positional-only parameter
In-Reply-To: <1571106392.69.0.85003046785.issue38478@roundup.psfhosted.org>
Message-ID: <1571139618.16.0.00890568008243.issue38478@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset f3ef06a7cb347ab7bd3cc2b0b3dcebe4f9ff36f9 by Pablo Galindo in branch 'master':
bpo-38478: Correctly handle keyword argument with same name as positional-only parameter (GH-16800)
https://github.com/python/cpython/commit/f3ef06a7cb347ab7bd3cc2b0b3dcebe4f9ff36f9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 07:40:26 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 15 Oct 2019 11:40:26 +0000
Subject: [issue38478] inspect.signature.bind does not correctly handle keyword
 argument with same name as positional-only parameter
In-Reply-To: <1571106392.69.0.85003046785.issue38478@roundup.psfhosted.org>
Message-ID: <1571139626.33.0.432516257876.issue38478@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16357
pull_request: https://github.com/python/cpython/pull/16801

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 07:58:51 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Oct 2019 11:58:51 +0000
Subject: [issue38474] digit check logic can be replaced by Py_ISDIGIT on
 prepare_s
In-Reply-To: <1571077834.59.0.937971525821.issue38474@roundup.psfhosted.org>
Message-ID: <1571140731.19.0.2699606306.issue38474@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

What is the benefit of such change?

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38474>
_______________________________________

From report at bugs.python.org  Tue Oct 15 07:59:23 2019
From: report at bugs.python.org (Jim Carroll)
Date: Tue, 15 Oct 2019 11:59:23 +0000
Subject: [issue38482] BUG in codecs.BufferedIncrementalDecoder
In-Reply-To: <1571127690.05.0.477916235895.issue38482@roundup.psfhosted.org>
Message-ID: <1571140763.63.0.418366889447.issue38482@roundup.psfhosted.org>


Jim Carroll <jim at carroll.com> added the comment:

According to the documentation (https://docs.python.org/3.7/library/codecs.html#codecs.iterdecode), the first parameter is a bytes object to decode (not an iterable of bytes). Which is also consistent with it's companion iterencode() which accepts a str object, not an iterable of chars.

Seems logical that one should be able to pass the output from iterencode() as the direct input to iterdecode() without having to convert, no?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38482>
_______________________________________

From report at bugs.python.org  Tue Oct 15 08:00:21 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 12:00:21 +0000
Subject: [issue37961] Tracemalloc traces do not include original stack trace
 length
In-Reply-To: <1566894205.32.0.427554502238.issue37961@roundup.psfhosted.org>
Message-ID: <1571140821.56.0.0727223541794.issue37961@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 8d59eb1b66c51b2b918da9881c57d07d08df43b7 by Victor Stinner (Julien Danjou) in branch 'master':
bpo-37961, tracemalloc: add Traceback.total_nframe (GH-15545)
https://github.com/python/cpython/commit/8d59eb1b66c51b2b918da9881c57d07d08df43b7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37961>
_______________________________________

From report at bugs.python.org  Tue Oct 15 08:02:37 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 15 Oct 2019 12:02:37 +0000
Subject: [issue38478] inspect.signature.bind does not correctly handle keyword
 argument with same name as positional-only parameter
In-Reply-To: <1571106392.69.0.85003046785.issue38478@roundup.psfhosted.org>
Message-ID: <1571140957.42.0.942764753911.issue38478@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset f705f8e9b58955d0d9083e98d71ba01b2e69798c by Miss Islington (bot) in branch '3.8':
bpo-38478: Correctly handle keyword argument with same name as positional-only parameter (GH-16800)
https://github.com/python/cpython/commit/f705f8e9b58955d0d9083e98d71ba01b2e69798c


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 08:37:14 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Tue, 15 Oct 2019 12:37:14 +0000
Subject: [issue38484] HTMLParser.handle_starttag should mention that value can
 be None
Message-ID: <1571143034.46.0.408177469405.issue38484@roundup.psfhosted.org>


New submission from Sebastian Rittau <srittau at rittau.biz>:

The documentation for HTMLParser.handle_starttag (https://docs.python.org/3/library/html.parser.html#html.parser.HTMLParser.handle_starttag) should mention that the value of an attribute can be `None` for argument-less attributes. I can submit a PR if wanted.

----------
assignee: docs at python
components: Documentation
messages: 354719
nosy: docs at python, srittau
priority: normal
severity: normal
status: open
title: HTMLParser.handle_starttag should mention that value can be None
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38484>
_______________________________________

From report at bugs.python.org  Tue Oct 15 08:46:36 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 15 Oct 2019 12:46:36 +0000
Subject: [issue38478] inspect.signature.bind does not correctly handle keyword
 argument with same name as positional-only parameter
In-Reply-To: <1571106392.69.0.85003046785.issue38478@roundup.psfhosted.org>
Message-ID: <1571143596.96.0.391610425212.issue38478@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 08:56:13 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Tue, 15 Oct 2019 12:56:13 +0000
Subject: [issue38474] digit check logic can be replaced by Py_ISDIGIT on
 prepare_s
In-Reply-To: <1571077834.59.0.937971525821.issue38474@roundup.psfhosted.org>
Message-ID: <1571144173.6.0.930289138482.issue38474@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> What is the benefit of such change?


I think that if an API is implemented for a specific purpose,
it should be used. This will help us to maintain code quality.

Especially in the case of pointed out logics,
since Py_ISDIGIT is exactly what we want to do, 
By replacing this logic, we can reduce unnecessary mistakes when someone modifies the logic.

This is, of course, my personal opinion.
I think it may be different from the policies of the core developers.

Thank you

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38474>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:00:12 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 15 Oct 2019 13:00:12 +0000
Subject: [issue34688] Segfault in pandas that works fine on 3.7
In-Reply-To: <1536954749.8.0.956365154283.issue34688@psf.upfronthosting.co.za>
Message-ID: <1571144412.68.0.203444435956.issue34688@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

This has an issue in GitHub and pandas is also tested with 3.8 from https://github.com/pandas-dev/pandas/pull/28730. I am closing this as third party.

----------
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34688>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:00:43 2019
From: report at bugs.python.org (Cooper Lees)
Date: Tue, 15 Oct 2019 13:00:43 +0000
Subject: [issue38483] [venv] Add ~/.venvrc to change module defaults
In-Reply-To: <1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>
Message-ID: <1571144443.64.0.9183378196.issue38483@roundup.psfhosted.org>


Change by Cooper Lees <me at cooperlees.com>:


----------
keywords: +patch
pull_requests: +16358
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16802

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38483>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:05:03 2019
From: report at bugs.python.org (Cooper Lees)
Date: Tue, 15 Oct 2019 13:05:03 +0000
Subject: [issue38483] [venv] Add ~/.venvrc to change module defaults
In-Reply-To: <1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>
Message-ID: <1571144703.79.0.84231196145.issue38483@roundup.psfhosted.org>


Change by Cooper Lees <me at cooperlees.com>:


----------
pull_requests: +16359
pull_request: https://github.com/python/cpython/pull/168

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38483>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:10:34 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 13:10:34 +0000
Subject: [issue37961] Tracemalloc traces do not include original stack trace
 length
In-Reply-To: <1566894205.32.0.427554502238.issue37961@roundup.psfhosted.org>
Message-ID: <1571145034.38.0.479528410545.issue37961@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Thanks for your contribution Julien, I merged your PR.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37961>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:13:57 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 15 Oct 2019 13:13:57 +0000
Subject: [issue38483] [venv] Add ~/.venvrc to change module defaults
In-Reply-To: <1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>
Message-ID: <1571145237.05.0.816077068898.issue38483@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +vinay.sajip

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38483>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:14:08 2019
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Tue, 15 Oct 2019 13:14:08 +0000
Subject: [issue17477] update the bsddb module do build with db 5.x versions
In-Reply-To: <1363671295.4.0.641867038298.issue17477@psf.upfronthosting.co.za>
Message-ID: <1571145248.74.0.305988374681.issue17477@roundup.psfhosted.org>


Jes?s Cea Avi?n <jcea at jcea.es> added the comment:

Time to die.

----------
resolution:  -> wont fix
stage: needs patch -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17477>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:14:16 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 15 Oct 2019 13:14:16 +0000
Subject: [issue38483] [venv] Add ~/.venvrc to change module defaults
In-Reply-To: <1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>
Message-ID: <1571145256.86.0.595365016131.issue38483@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
pull_requests:  -16359

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38483>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:15:06 2019
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Tue, 15 Oct 2019 13:15:06 +0000
Subject: [issue18734] Berkeley DB versions 4.4-4.9 are not discovered by
 setup.py
In-Reply-To: <1376450123.08.0.865805118992.issue18734@psf.upfronthosting.co.za>
Message-ID: <1571145306.2.0.298346035536.issue18734@roundup.psfhosted.org>


Jes?s Cea Avi?n <jcea at jcea.es> added the comment:

Time to die.

----------
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue18734>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:17:58 2019
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Tue, 15 Oct 2019 13:17:58 +0000
Subject: [issue6462] bsddb3 intermittent test failures
In-Reply-To: <1247329933.16.0.47150397.issue6462@psf.upfronthosting.co.za>
Message-ID: <1571145478.25.0.211889824435.issue6462@roundup.psfhosted.org>


Jes?s Cea Avi?n <jcea at jcea.es> added the comment:

Time to die.

----------
resolution:  -> wont fix
stage: needs patch -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue6462>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:34:27 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 13:34:27 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571146467.18.0.0398799427872.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Zachary Ware commented the new failures on the x86 Gentoo worker:

"My worker was updated to OpenSSL v1.1.1d with sslv3 disabled today, which seems like a likely source of these failures."

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:36:27 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 13:36:27 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1571146587.5.0.733494502675.issue38006@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy:  -vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:40:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 13:40:03 +0000
Subject: [issue38112] Compileall improvements
In-Reply-To: <1568210479.53.0.901531773072.issue38112@roundup.psfhosted.org>
Message-ID: <1571146803.45.0.319045413708.issue38112@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Should be fixed by:

New changeset eb1dda2b56f67f09352c303588c28880c471ae87 by Petr Viktorin (Victor Stinner) in branch 'master':
bpo-38470: Fix test_compileall.test_compile_dir_maxlevels() (GH-16789)
https://github.com/python/cpython/commit/eb1dda2b56f67f09352c303588c28880c471ae87

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38112>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:42:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 13:42:59 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571146979.49.0.682208456752.issue38470@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> create_long_path isn't taking into account _write_atomic in Lib/importlib/_bootstrap_external.py.

Yeah, I found the same issue:
https://github.com/python/cpython/pull/16778#issuecomment-541764285

I began to write a complex change to take _write_atomic() in account, but the test became super complex. I don't think that it's worth it. So I wrote a much simpler PR.
https://github.com/python/cpython/pull/16789#issuecomment-541918432

Anyway, the issue should now be fixed.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Tue Oct 15 09:44:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 13:44:30 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571147070.78.0.5930631169.issue38470@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It seems like test_compileall now pass on the 4 Windows workers:

* https://buildbot.python.org/all/#/builders/3
* https://buildbot.python.org/all/#/builders/12
* https://buildbot.python.org/all/#/builders/40
* https://buildbot.python.org/all/#/builders/58

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Tue Oct 15 10:04:43 2019
From: report at bugs.python.org (=?utf-8?q?Walter_D=C3=B6rwald?=)
Date: Tue, 15 Oct 2019 14:04:43 +0000
Subject: [issue38482] BUG in codecs.BufferedIncrementalDecoder
In-Reply-To: <1571127690.05.0.477916235895.issue38482@roundup.psfhosted.org>
Message-ID: <1571148283.89.0.752256063936.issue38482@roundup.psfhosted.org>


Walter D?rwald <walter at livinglogic.de> added the comment:

The documentation might be unclear here. But the argument iterator of

   iterdecode(iterator, encoding, errors='strict', **kwargs)

*is* supposed to be an iterable over bytes objects.

In fact iterencode() transforms an iterator over strings into an iterator over bytes and iterdecode() transforms an iterator over bytes into an iterator over strings.

Since iterating over strings iterates over the characters, it's possible to pass a string to iterencode(). However it's not possible to pass a bytes object to iterdecode() since iterating over a bytes object yields integers:

>>> import codecs
>>> list(codecs.iterencode(['spam'], 'utf-8'))
[b'spam']
>>> list(codecs.iterencode('spam', 'utf-8'))
[b's', b'p', b'a', b'm']
>>> list(codecs.iterdecode([b'spam'], 'utf-8'))
['spam']
>>> list(codecs.iterdecode(b'spam', 'utf-8'))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/codecs.py", line 1048, in iterdecode
    output = decoder.decode(input)
  File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/codecs.py", line 321, in decode
    data = self.buffer + input
TypeError: can't concat int to bytes

----------
nosy: +doerwalter

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38482>
_______________________________________

From report at bugs.python.org  Tue Oct 15 10:18:53 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Tue, 15 Oct 2019 14:18:53 +0000
Subject: [issue38468] Refactor python-config.in - use getvar()
In-Reply-To: <1570983225.71.0.166757825145.issue38468@roundup.psfhosted.org>
Message-ID: <1571149133.18.0.0250135539995.issue38468@roundup.psfhosted.org>


Joannah Nanjekye <nanjekyejoannah at gmail.com> added the comment:


New changeset 3cd21aa6a1467723ccc85e6411a6cbe7fa81ef76 by Joannah Nanjekye in branch 'master':
bpo-38468 : Refactor python-config (#16749)
https://github.com/python/cpython/commit/3cd21aa6a1467723ccc85e6411a6cbe7fa81ef76


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38468>
_______________________________________

From report at bugs.python.org  Tue Oct 15 10:22:34 2019
From: report at bugs.python.org (Jim Carroll)
Date: Tue, 15 Oct 2019 14:22:34 +0000
Subject: [issue38485] BUG Modules/_io/texio.c
Message-ID: <1571149354.19.0.486917734419.issue38485@roundup.psfhosted.org>


New submission from Jim Carroll <jim at carroll.com>:

The io.TextIOWrapper class initializes a codec.IncrementalEncoder and uses it to encode str, but it never calls the encoder's encode('', final=True). According to the docs https://docs.python.org/3.5/library/codecs.html#codecs.IncrementalEncoder.encode:  

``If this is the last call to encode() final must be true (the default is false).``

Without a call to encode('', final=True), codecs cannot be created that use codecs.BufferedIncrementalEncoder which depend on being called with final=True to flush any internal buffers.

Platform: Python 3.7.4 (tags/v3.7.4:e09359112e, Jul  8 2019, 20:34:20) [MSC v.1916 64 bit (AMD64)] on win32

----------
messages: 354733
nosy: jamercee
priority: normal
severity: normal
status: open
title: BUG Modules/_io/texio.c
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38485>
_______________________________________

From report at bugs.python.org  Tue Oct 15 10:46:58 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Tue, 15 Oct 2019 14:46:58 +0000
Subject: [issue38468] Refactor python-config.in - use getvar()
In-Reply-To: <1570983225.71.0.166757825145.issue38468@roundup.psfhosted.org>
Message-ID: <1571150818.11.0.199045757278.issue38468@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38468>
_______________________________________

From report at bugs.python.org  Tue Oct 15 11:20:04 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 15 Oct 2019 15:20:04 +0000
Subject: [issue33604] HMAC default to MD5 marked as to be removed in 3.6
In-Reply-To: <1527014760.1.0.682650639539.issue33604@psf.upfronthosting.co.za>
Message-ID: <1571152804.57.0.844723965796.issue33604@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

The docs still make it look like *digestmod* is an optional argument: 
   https://docs.python.org/3/library/hmac.html#hmac.new

The help output does as well:

    >>> help(hmac.new)
    Help on function new in module hmac:

    new(key, msg=None, digestmod=None)
        Create a new hashing object and return it.
        
        key: The starting key for the hash.
        msg: if available, will immediately be hashed into the object's starting
        state.
        
        You can now feed arbitrary strings into the object using its update()
        method, and can ask for the hash value at any time by calling its digest()
        method.

Also, it is well outside the Python norms to have a required argument default to None and having that default value be invalid.

Presumably, the type annotation for this would be, "digestmod: Optional[str]=None".  That would further add to the confusion with a required Optional argument.

Another thought:  The usual exception for a missing argument is a TypeError, not a ValueError

Lastly, I'm curious why another algorithm wasn't used (perhaps sha256) as a default rather than removing the default altogether.  This doesn't seems like good API design.

FWIW, this removal broke the third-party package, Bottle:

    Bottle v0.12.17 server starting up (using WSGIRefServer())...
    Listening on http://localhost:8081/
    Hit Ctrl-C to quit.

    127.0.0.1 - - [15/Oct/2019 07:53:10] "GET / HTTP/1.1" 200 1471
    Traceback (most recent call last):
      File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/bottle.py", line 862, in _handle
        return route.call(**args)
      File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/bottle.py", line 1742, in wrapper
        rv = callback(*a, **ka)
      File "webapp.py", line 32, in check_credentials
        response.set_cookie('token', token, max_age=3600, secret=secret)
      File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/bottle.py", line 1626, in set_cookie
        value = touni(cookie_encode((name, value), secret))
      File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/bottle.py", line 2600, in cookie_encode
        sig = base64.b64encode(hmac.new(tob(key), msg).digest())
      File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/hmac.py", line 146, in new
        return HMAC(key, msg, digestmod)
      File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/hmac.py", line 49, in __init__
        raise ValueError('`digestmod` is required.')
    ValueError: `digestmod` is required.

----------
nosy: +rhettinger
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33604>
_______________________________________

From report at bugs.python.org  Tue Oct 15 11:42:43 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Oct 2019 15:42:43 +0000
Subject: [issue38485] BUG Modules/_io/texio.c
In-Reply-To: <1571149354.19.0.486917734419.issue38485@roundup.psfhosted.org>
Message-ID: <1571154163.71.0.252768730139.issue38485@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
components: +IO
nosy: +benjamin.peterson, stutzbach
type:  -> behavior
versions: +Python 2.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38485>
_______________________________________

From report at bugs.python.org  Tue Oct 15 11:50:02 2019
From: report at bugs.python.org (Caris Moses)
Date: Tue, 15 Oct 2019 15:50:02 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1571154602.76.0.00892690071699.issue21478@roundup.psfhosted.org>


Caris Moses <caris.moses at gmail.com> added the comment:

I am having some trouble figuring out how to use CPython to get the exact PR you tested on since I've never used CPython before. However, when I just install Python 3.7.5RC1 and 3.8.0RC1 from the binaries and run your code I do get the AttributeError. And when I run your code with Python3.7.4 from binaries I get an empty list.

Can you point me to a good source that will tell me how to get the patch for issue38473? I built and ran cpython from source on my Mac successfully. However when I checkout a different branch or version, rebuild, and run ./python.exe I always get the same Python version.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 11:57:47 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Oct 2019 15:57:47 +0000
Subject: [issue38474] digit check logic can be replaced by Py_ISDIGIT on
 prepare_s
In-Reply-To: <1571077834.59.0.937971525821.issue38474@roundup.psfhosted.org>
Message-ID: <1571155067.94.0.880858415894.issue38474@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

It was added as a replacement of locale aware isdigit(). It was initially used only for implementing bytes.isdigit() and in PyOS_ascii_strtod().

isdigit() is not used in Modules/_struct.c, so there is nothing to replace with Py_ISDIGIT(). Currently hardcoded '0' and '9' are used in more places than Py_ISDIGIT(). Rewriting all this code just because we have Py_ISDIGIT() is a code churn.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38474>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:00:48 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 15 Oct 2019 16:00:48 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1571155248.04.0.0238227538583.issue21478@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Thanks for the confirmation. You can download the patch for the PR by appending .diff/.patch to the PR URL. The patch can be applied to your source locally with "git apply patch_file" to run my example. Reverting patch would cause AttributeError

Diff URL : https://github.com/python/cpython/pull/16784.diff

The PR also includes regression test so reverting the patch to mock.py and running below command would cause error in test.

./python -m test test_unittest

Checking out a different branch and doing below command should do a clean rebuild with a different version of python. Also for reference : https://devguide.python.org/

git clean -xdf && ./configure && make -j4

Hope it helps

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:02:16 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 15 Oct 2019 16:02:16 +0000
Subject: [issue38486] Dead links in mailbox doc
Message-ID: <1571155336.35.0.351516835001.issue38486@roundup.psfhosted.org>


New submission from Inada Naoki <songofacandy at gmail.com>:

Reported on mailing list: https://mail.python.org/archives/list/docs at python.org/thread/NIXFQMWFNSNO6RXPINY56CQQ5L7QIRUV/

qmail.org is dead.  The mailbox doc [1] contains two links to man pages in qmail.org.
Can we just remove them?

[1] https://docs.python.org/3/library/mailbox.html

----------
assignee: docs at python
components: Documentation
messages: 354738
nosy: docs at python, inada.naoki
priority: normal
severity: normal
status: open
title: Dead links in mailbox doc
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38486>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:03:55 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Oct 2019 16:03:55 +0000
Subject: [issue38474] digit check logic can be replaced by Py_ISDIGIT on
 prepare_s
In-Reply-To: <1571077834.59.0.937971525821.issue38474@roundup.psfhosted.org>
Message-ID: <1571155435.34.0.367503387734.issue38474@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I left this on to the struct module maintainers.

----------
nosy: +mark.dickinson, meador.inge

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38474>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:11:08 2019
From: report at bugs.python.org (Giampaolo Rodola')
Date: Tue, 15 Oct 2019 16:11:08 +0000
Subject: [issue38480] resource.setrlimit() should raise PermissionError
In-Reply-To: <1571124860.16.0.598909630124.issue38480@roundup.psfhosted.org>
Message-ID: <1571155868.55.0.668252976548.issue38480@roundup.psfhosted.org>


Change by Giampaolo Rodola' <g.rodola at gmail.com>:


----------
keywords: +patch
pull_requests: +16360
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16804

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38480>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:12:16 2019
From: report at bugs.python.org (Giampaolo Rodola')
Date: Tue, 15 Oct 2019 16:12:16 +0000
Subject: [issue38480] resource.setrlimit() should raise PermissionError
In-Reply-To: <1571124860.16.0.598909630124.issue38480@roundup.psfhosted.org>
Message-ID: <1571155936.23.0.177010407059.issue38480@roundup.psfhosted.org>


Giampaolo Rodola' <g.rodola at gmail.com> added the comment:

It turns out there is a similar precedent which was solved in the same way: issue18787.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38480>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:22:16 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 15 Oct 2019 16:22:16 +0000
Subject: [issue38486] Dead links in mailbox doc
In-Reply-To: <1571155336.35.0.351516835001.issue38486@roundup.psfhosted.org>
Message-ID: <1571156536.35.0.796500950889.issue38486@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
components: +email
nosy: +barry, maxking, r.david.murray

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38486>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:24:08 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 15 Oct 2019 16:24:08 +0000
Subject: [issue33342] urllib IPv6 parsing fails with special characters in
 passwords
In-Reply-To: <1524491070.85.0.682650639539.issue33342@psf.upfronthosting.co.za>
Message-ID: <1571156648.63.0.811878372139.issue33342@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33342>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:37:24 2019
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 15 Oct 2019 16:37:24 +0000
Subject: [issue33604] HMAC default to MD5 marked as to be removed in 3.6
In-Reply-To: <1527014760.1.0.682650639539.issue33604@psf.upfronthosting.co.za>
Message-ID: <1571157444.17.0.415165713597.issue33604@roundup.psfhosted.org>


Christian Heimes <lists at cheimes.de> added the comment:

The weird argument style of a required digestmod with None as default is an unfortunate outcome of the old API. The msg and digestmod argument can be passed in as keyword and as positional argument. I studied existing code and have considered to make digestmod a required keyword-only argument, but that would have broken too much code. The current style is backwards compatible with all code except for code that must be changed any way.

Only code that depends on implicit default digestmod="md5" breaks. The code must adjusted for the deprecation no matter the argument style. The required change is fully backwards compatible with Python 2.7 to 3.7. Bottle is such a case that got broken by the deprecation.

It does not make sense to default to another hashing algorithm:
* This would also break software. Applications would suddenly get a different MAC for the same function call and arguments.
* In cryptography the HMAC algorithm is an operation on a key, message, and PRF. Defaulting to MD5 didn't make sense in the first place.
* Cryptographic primitives have a 'best before' date. SHA256 might become broken in a decade -- maybe 9 years and 364 days earlier, maybe 20 years later. I don't want to do another deprecation cycle.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33604>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:38:55 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 15 Oct 2019 16:38:55 +0000
Subject: [issue33604] HMAC default to MD5 marked as to be removed in 3.6
In-Reply-To: <1527014760.1.0.682650639539.issue33604@psf.upfronthosting.co.za>
Message-ID: <1571157535.69.0.288687646809.issue33604@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
pull_requests: +16362
stage: commit review -> patch review
pull_request: https://github.com/python/cpython/pull/16805

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33604>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:43:50 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 15 Oct 2019 16:43:50 +0000
Subject: [issue33604] HMAC default to MD5 marked as to be removed in 3.6
In-Reply-To: <1527014760.1.0.682650639539.issue33604@psf.upfronthosting.co.za>
Message-ID: <1571157830.02.0.572682656765.issue33604@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

Thanks for the feedback.  Better late than never. :)

A default algorithm is a bad thing when it comes to authentication.  Explicit is better than implicit.  A default regularly becomes obsolete as math and cryptanalysis methods move forward and need to be changed every unpredictable N years.  MD5 was _already_ a bad choice of default when hmac was added in 2.2.

That said, we managed this deprecation and API evolution poorly.

As it has shipped this way in 3.8, I'm first going to fix the documentation and the exception type (both suitable for 3.8).  First PR sent.

In 3.9 we could introduce a better named keyword only digest parameter, leaving digestmod supported as a legacy positional & alternate name for backwards incompatibility.  (minor code gymnastics required to do that, but within reason)

i wouldn't want to remove the digestmod positional/name support until after 3.8 is no longer relevant in the world.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33604>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:45:14 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 15 Oct 2019 16:45:14 +0000
Subject: [issue33604] HMAC default to MD5 marked as to be removed in 3.6
In-Reply-To: <1527014760.1.0.682650639539.issue33604@psf.upfronthosting.co.za>
Message-ID: <1571157914.02.0.930389327713.issue33604@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
assignee:  -> gregory.p.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33604>
_______________________________________

From report at bugs.python.org  Tue Oct 15 12:52:23 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 15 Oct 2019 16:52:23 +0000
Subject: [issue33604] HMAC default to MD5 marked as to be removed in 3.6
In-Reply-To: <1527014760.1.0.682650639539.issue33604@psf.upfronthosting.co.za>
Message-ID: <1571158343.93.0.100786510712.issue33604@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

BTW, if you want the type annotation that'd be used for this, 3.8 effectively removes the Optional[] from the one listed in:

https://github.com/python/typeshed/blob/master/stdlib/2and3/hmac.pyi#L16

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33604>
_______________________________________

From report at bugs.python.org  Tue Oct 15 13:08:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 17:08:55 +0000
Subject: [issue33342] urllib IPv6 parsing fails with special characters in
 passwords
In-Reply-To: <1524491070.85.0.682650639539.issue33342@psf.upfronthosting.co.za>
Message-ID: <1571159335.26.0.288738443785.issue33342@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I modified my PR 16780 to also fix this issue, my PR was written for bpo-36338.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33342>
_______________________________________

From report at bugs.python.org  Tue Oct 15 13:08:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 17:08:57 +0000
Subject: [issue36338] urlparse of urllib returns wrong hostname
In-Reply-To: <1552896371.92.0.122580708995.issue36338@roundup.psfhosted.org>
Message-ID: <1571159337.65.0.0445830916076.issue36338@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I modified my PR 16780 to also fix bpo-33342: "urllib IPv6 parsing fails with special characters in passwords".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36338>
_______________________________________

From report at bugs.python.org  Tue Oct 15 13:12:40 2019
From: report at bugs.python.org (Marcos Dione)
Date: Tue, 15 Oct 2019 17:12:40 +0000
Subject: [issue38487] expat infinite loop
Message-ID: <1571159560.58.0.207422547054.issue38487@roundup.psfhosted.org>


New submission from Marcos Dione <mdione at grulic.org.ar>:

I'm trying to add external entities support to xmltodict[1]. For that I extended the handler to have a ExternalEntityRefHandler handler. After reading a couple of files, the script lock in a tight loop.

I ran the script with gdb (!!) and found that expat think that two of the parsers are parent of each other. I setup a breakpoint in XML_ExternalEntityParserCreate() (yes, this is expat, I know) right after the new parser uses the old parser as parent (xmlparse.c:1279 in my system).

Here are the backtraces and values I found:

--- >8 ---
landuse-lowzoom None styles-otm/landuse-lowzoom.xml None

#0  XML_ExternalEntityParserCreate (oldParser=0xadc4d0, context=context at entry=0x7ffff6c871e0 "landuse-lowzoom", encodingName=encodingName at entry=0x0) at ../../src/lib/xmlparse.c:1281
#1  0x000000000044ec90 in pyexpat_xmlparser_ExternalEntityParserCreate_impl (encoding=0x0, context=0x7ffff6c871e0 "landuse-lowzoom", self=0x7ffff6d556e0) at ../Modules/pyexpat.c:943
#2  pyexpat_xmlparser_ExternalEntityParserCreate (self=0x7ffff6d556e0, args=<optimized out>, nargs=<optimized out>) at ../Modules/clinic/pyexpat.c.h:137
[...]
#15 0x000000000044d80d in my_ExternalEntityRefHandler (parser=<optimized out>, context=0xae1d2c "landuse-lowzoom", base=<optimized out>, systemId=<optimized out>, publicId=<optimized out>)
    at ../Modules/pyexpat.c:659
#16 0x00007ffff7d990c8 in doContent (parser=parser at entry=0xadc4d0, startTagLevel=startTagLevel at entry=0, enc=<optimized out>,
    s=s at entry=0xae08dd "<Map background-color=\"#e0e0e0\" srs=\"+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +no_defs +over\" buffer-size=\"256\">\n\t<!-- style definitions "..., end=end at entry=0xae0ce6 '\001' <repeats 200 times>..., nextPtr=nextPtr at entry=0xadc500, haveMore=1 '\001') at ../../src/lib/xmlparse.c:2685
#17 0x00007ffff7d9957c in contentProcessor (parser=parser at entry=0xadc4d0,
    start=start at entry=0xae08dd "<Map background-color=\"#e0e0e0\" srs=\"+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +no_defs +over\" buffer-size=\"256\">\n\t<!-- style definitions "..., end=end at entry=0xae0ce6 '\001' <repeats 200 times>..., endPtr=endPtr at entry=0xadc500) at ../../src/lib/xmlparse.c:2444
#18 0x00007ffff7d96a73 in doProlog (parser=parser at entry=0xadc4d0, enc=0x7ffff7db89e0 <utf8_encoding>,
    s=0xae08dd "<Map background-color=\"#e0e0e0\" srs=\"+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +no_defs +over\" buffer-size=\"256\">\n\t<!-- style definitions "...,
    s at entry=0xae04e4 "text-water-lowzoom SYSTEM \"styles-otm/text-water-lowzoom.xml\">\n\t<!ENTITY text-glacier-lowzoom SYSTEM \"styles-otm/text-glacier-lowzoom.xml\">\n\t<!ENTITY text-natural-poly SYSTEM \"styles-otm/text-natural-"..., end=end at entry=0xae0ce6 '\001' <repeats 200 times>..., tok=29, next=<optimized out>, nextPtr=0xadc500, haveMore=1 '\001', allowClosingDoctype=1 '\001') at ../../src/lib/xmlparse.c:4371
#19 0x00007ffff7d97f3a in prologProcessor (parser=0xadc4d0,
    s=0xae04e4 "text-water-lowzoom SYSTEM \"styles-otm/text-water-lowzoom.xml\">\n\t<!ENTITY text-glacier-lowzoom SYSTEM \"styles-otm/text-glacier-lowzoom.xml\">\n\t<!ENTITY text-natural-poly SYSTEM \"styles-otm/text-natural-"..., end=0xae0ce6 '\001' <repeats 200 times>..., nextPtr=0xadc500) at ../../src/lib/xmlparse.c:4094
#20 0x00007ffff7d9bb1c in XML_ParseBuffer (isFinal=0, len=<optimized out>, parser=0xadc4d0) at ../../src/lib/xmlparse.c:1893
#21 XML_ParseBuffer (parser=0xadc4d0, len=len at entry=2048, isFinal=isFinal at entry=0) at ../../src/lib/xmlparse.c:1863
#22 0x000000000060886d in pyexpat_xmlparser_ParseFile (self=0x7ffff6d556e0, file=<optimized out>) at ../Modules/pyexpat.c:841

(gdb) print oldParser
$33 = (XML_Parser) 0xadc4d0
(gdb) print parser
$32 = (XML_Parser) 0xadecb0

7ffff6d556e0, 7ffff6d55750
<_io.BufferedReader name='styles-otm/landuse-lowzoom.xml'>
<_io.BufferedReader name='styles-otm/landuse-lowzoom.xml'>
landuse None styles-otm/landuse.xml None

#0  XML_ExternalEntityParserCreate (oldParser=0xadecb0, context=context at entry=0x7ffff6c88660 "landuse", encodingName=encodingName at entry=0x0) at ../../src/lib/xmlparse.c:1281
#1  0x000000000044ec90 in pyexpat_xmlparser_ExternalEntityParserCreate_impl (encoding=0x0, context=0x7ffff6c88660 "landuse", self=0x7ffff6d55750) at ../Modules/pyexpat.c:943
#2  pyexpat_xmlparser_ExternalEntityParserCreate (self=0x7ffff6d55750, args=<optimized out>, nargs=<optimized out>) at ../Modules/clinic/pyexpat.c.h:137
[...]
#15 0x000000000044d80d in my_ExternalEntityRefHandler (parser=<optimized out>, context=0xae1d2c "landuse", base=<optimized out>, systemId=<optimized out>, publicId=<optimized out>) at ../Modules/pyexpat.c:659
#16 0x00007ffff7d990c8 in doContent (parser=parser at entry=0xadc4d0, startTagLevel=startTagLevel at entry=0, enc=<optimized out>,
    s=s at entry=0xae08dd "<Map background-color=\"#e0e0e0\" srs=\"+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +no_defs +over\" buffer-size=\"256\">\n\t<!-- style definitions "..., end=end at entry=0xae0ce6 '\001' <repeats 200 times>..., nextPtr=nextPtr at entry=0xadc500, haveMore=1 '\001') at ../../src/lib/xmlparse.c:2685
#17 0x00007ffff7d9957c in contentProcessor (parser=parser at entry=0xadc4d0,
    start=start at entry=0xae08dd "<Map background-color=\"#e0e0e0\" srs=\"+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +no_defs +over\" buffer-size=\"256\">\n\t<!-- style definitions "..., end=end at entry=0xae0ce6 '\001' <repeats 200 times>..., endPtr=endPtr at entry=0xadc500) at ../../src/lib/xmlparse.c:2444
#18 0x00007ffff7d96a73 in doProlog (parser=parser at entry=0xadc4d0, enc=0x7ffff7db89e0 <utf8_encoding>,
    s=0xae08dd "<Map background-color=\"#e0e0e0\" srs=\"+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +no_defs +over\" buffer-size=\"256\">\n\t<!-- style definitions "...,
    s at entry=0xae04e4 "text-water-lowzoom SYSTEM \"styles-otm/text-water-lowzoom.xml\">\n\t<!ENTITY text-glacier-lowzoom SYSTEM \"styles-otm/text-glacier-lowzoom.xml\">\n\t<!ENTITY text-natural-poly SYSTEM \"styles-otm/text-natural-"..., end=end at entry=0xae0ce6 '\001' <repeats 200 times>..., tok=29, next=<optimized out>, nextPtr=0xadc500, haveMore=1 '\001', allowClosingDoctype=1 '\001') at ../../src/lib/xmlparse.c:4371
#19 0x00007ffff7d97f3a in prologProcessor (parser=0xadc4d0,
    s=0xae04e4 "text-water-lowzoom SYSTEM \"styles-otm/text-water-lowzoom.xml\">\n\t<!ENTITY text-glacier-lowzoom SYSTEM \"styles-otm/text-glacier-lowzoom.xml\">\n\t<!ENTITY text-natural-poly SYSTEM \"styles-otm/text-natural-"..., end=0xae0ce6 '\001' <repeats 200 times>..., nextPtr=0xadc500) at ../../src/lib/xmlparse.c:4094
#20 0x00007ffff7d9bb1c in XML_ParseBuffer (isFinal=0, len=<optimized out>, parser=0xadc4d0) at ../../src/lib/xmlparse.c:1893
#21 XML_ParseBuffer (parser=0xadc4d0, len=len at entry=2048, isFinal=isFinal at entry=0) at ../../src/lib/xmlparse.c:1863
#22 0x000000000060886d in pyexpat_xmlparser_ParseFile (self=0x7ffff6d556e0, file=<optimized out>) at ../Modules/pyexpat.c:841

(gdb) print oldParser
$35 = (XML_Parser) 0xadecb0
(gdb) print parser
$34 = (XML_Parser) 0xae5e00

7ffff6d55750, 7ffff6d557c0
<_io.BufferedReader name='styles-otm/landuse.xml'>
<_io.BufferedReader name='styles-otm/landuse.xml'>
landuse-over-hillshade None styles-otm/landuse-over-hillshade.xml None

#0  XML_ExternalEntityParserCreate (oldParser=0xae5e00, context=context at entry=0x7ffff6c81a60 "landuse-over-hillshade", encodingName=encodingName at entry=0x0) at ../../src/lib/xmlparse.c:1281
#1  0x000000000044ec90 in pyexpat_xmlparser_ExternalEntityParserCreate_impl (encoding=0x0, context=0x7ffff6c81a60 "landuse-over-hillshade", self=0x7ffff6d557c0) at ../Modules/pyexpat.c:943
#2  pyexpat_xmlparser_ExternalEntityParserCreate (self=0x7ffff6d557c0, args=<optimized out>, nargs=<optimized out>) at ../Modules/clinic/pyexpat.c.h:137
[...]
#15 0x000000000044d80d in my_ExternalEntityRefHandler (parser=<optimized out>, context=0xae1d2c "landuse-over-hillshade", base=<optimized out>, systemId=<optimized out>, publicId=<optimized out>)
    at ../Modules/pyexpat.c:659
#16 0x00007ffff7d990c8 in doContent (parser=parser at entry=0xadc4d0, startTagLevel=startTagLevel at entry=0, enc=<optimized out>,
    s=s at entry=0xae08dd "<Map background-color=\"#e0e0e0\" srs=\"+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +no_defs +over\" buffer-size=\"256\">\n\t<!-- style definitions "..., end=end at entry=0xae0ce6 '\001' <repeats 200 times>..., nextPtr=nextPtr at entry=0xadc500, haveMore=1 '\001') at ../../src/lib/xmlparse.c:2685
#17 0x00007ffff7d9957c in contentProcessor (parser=parser at entry=0xadc4d0,
    start=start at entry=0xae08dd "<Map background-color=\"#e0e0e0\" srs=\"+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +no_defs +over\" buffer-size=\"256\">\n\t<!-- style definitions "..., end=end at entry=0xae0ce6 '\001' <repeats 200 times>..., endPtr=endPtr at entry=0xadc500) at ../../src/lib/xmlparse.c:2444
#18 0x00007ffff7d96a73 in doProlog (parser=parser at entry=0xadc4d0, enc=0x7ffff7db89e0 <utf8_encoding>,
    s=0xae08dd "<Map background-color=\"#e0e0e0\" srs=\"+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0 +lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +no_defs +over\" buffer-size=\"256\">\n\t<!-- style definitions "...,
    s at entry=0xae04e4 "text-water-lowzoom SYSTEM \"styles-otm/text-water-lowzoom.xml\">\n\t<!ENTITY text-glacier-lowzoom SYSTEM \"styles-otm/text-glacier-lowzoom.xml\">\n\t<!ENTITY text-natural-poly SYSTEM \"styles-otm/text-natural-"..., end=end at entry=0xae0ce6 '\001' <repeats 200 times>..., tok=29, next=<optimized out>, nextPtr=0xadc500, haveMore=1 '\001', allowClosingDoctype=1 '\001') at ../../src/lib/xmlparse.c:4371
#19 0x00007ffff7d97f3a in prologProcessor (parser=0xadc4d0,
    s=0xae04e4 "text-water-lowzoom SYSTEM \"styles-otm/text-water-lowzoom.xml\">\n\t<!ENTITY text-glacier-lowzoom SYSTEM \"styles-otm/text-glacier-lowzoom.xml\">\n\t<!ENTITY text-natural-poly SYSTEM \"styles-otm/text-natural-"..., end=0xae0ce6 '\001' <repeats 200 times>..., nextPtr=0xadc500) at ../../src/lib/xmlparse.c:4094
#20 0x00007ffff7d9bb1c in XML_ParseBuffer (isFinal=0, len=<optimized out>, parser=0xadc4d0) at ../../src/lib/xmlparse.c:1893
#21 XML_ParseBuffer (parser=0xadc4d0, len=len at entry=2048, isFinal=isFinal at entry=0) at ../../src/lib/xmlparse.c:1863
#22 0x000000000060886d in pyexpat_xmlparser_ParseFile (self=0x7ffff6d556e0, file=<optimized out>) at ../Modules/pyexpat.c:841

(gdb) print oldParser
$36 = (XML_Parser) 0xae5e00
(gdb) print parser
$37 = (XML_Parser) 0xadecb0
--- 8< ---

As I hope you can see, the last two values (parent 0xae5e00, new 0xadecb0) are the exact opposite of the previous one (parent 0xadecb0, new 0xae5e00). Later, when get_hash_secret_salt() is called, it enters in a infinite loop climbing up the parent ladder.

Now, this looks like an expat issue ands not pyexpat, but given that pyexpat provides its own allocator, and that the parser addresses are returned by that, I will start opening this issue here. If it can be proven that it's an expat issue, I'll take it to their issue tracker.

-----
[1] https://github.com/martinblech/xmltodict/issues/226

----------
components: XML
files: expat.tar.gz
messages: 354747
nosy: StyXman
priority: normal
severity: normal
status: open
title: expat infinite loop
type: behavior
versions: Python 3.7
Added file: https://bugs.python.org/file48663/expat.tar.gz

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38487>
_______________________________________

From report at bugs.python.org  Tue Oct 15 13:15:58 2019
From: report at bugs.python.org (Caris Moses)
Date: Tue, 15 Oct 2019 17:15:58 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1571159758.66.0.283296081996.issue21478@roundup.psfhosted.org>


Caris Moses <caris.moses at gmail.com> added the comment:

Great, thanks so much. It works with the patch. So will this patch be included in the next released version of Python?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 13:23:00 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 15 Oct 2019 17:23:00 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1571160180.55.0.296322448563.issue21478@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

It needs to approved and merged by a core dev so that it will be available by 3.7.6 and 3.8.1. To clarify the calls are recorded in 3.7.5 and 3.8.0 in mock_calls. It's a problem with assert_has_calls and autospec. As a workaround you can turn off autospec or use mock_calls to assert for calls instead of assert_has_calls. Sorry for the inconvenience.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 13:44:09 2019
From: report at bugs.python.org (Caris Moses)
Date: Tue, 15 Oct 2019 17:44:09 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1571161449.83.0.506676253568.issue21478@roundup.psfhosted.org>


Caris Moses <caris.moses at gmail.com> added the comment:

I see. Thanks for your help!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Tue Oct 15 15:16:32 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 19:16:32 +0000
Subject: [issue37633] Py_CompileString and PyParser_SimpleParseString not
 exported in python38.dll
In-Reply-To: <1563568606.34.0.923231546212.issue37633@roundup.psfhosted.org>
Message-ID: <1571166992.55.0.424302343779.issue37633@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
keywords: +3.8regression
nosy: +lukasz.langa
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37633>
_______________________________________

From report at bugs.python.org  Tue Oct 15 17:19:42 2019
From: report at bugs.python.org (Xavier Fernandez)
Date: Tue, 15 Oct 2019 21:19:42 +0000
Subject: [issue38488] Update bundled pip to 19.3
Message-ID: <1571174382.81.0.982982924079.issue38488@roundup.psfhosted.org>


Change by Xavier Fernandez <xav.fernandez at gmail.com>:


----------
components: Library (Lib)
nosy: Xavier Fernandez
priority: normal
pull_requests: 16363
severity: normal
status: open
title: Update bundled pip to 19.3
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38488>
_______________________________________

From report at bugs.python.org  Tue Oct 15 17:28:44 2019
From: report at bugs.python.org (Daniel Schlomer)
Date: Tue, 15 Oct 2019 21:28:44 +0000
Subject: [issue38489] Python 3.7 documentation is unavailable for download
Message-ID: <1571174924.15.0.531140690105.issue38489@roundup.psfhosted.org>


New submission from Daniel Schlomer <djschlomer at gmail.com>:

All the download links at https://docs.python.org/3.7/download.html return a 404 error.

----------
messages: 354751
nosy: schlomer
priority: normal
severity: normal
status: open
title: Python 3.7 documentation is unavailable for download
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38489>
_______________________________________

From report at bugs.python.org  Tue Oct 15 17:37:35 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 15 Oct 2019 21:37:35 +0000
Subject: [issue38489] Python 3.7 documentation is unavailable for download
In-Reply-To: <1571174924.15.0.531140690105.issue38489@roundup.psfhosted.org>
Message-ID: <1571175455.23.0.576291724226.issue38489@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Thanks for the report.  The full documentation builds of the current state of the docs, including the downloadable packages, occur only once every 24 hours and the 3.7.5 just missed the last iteration.  It looks like they should appear in about 4 or 5 hours.  Try again then and re-open this issue if they are not then available.  Also, you can download the archived copies of the docset that correspond exactly to the 3.7.5 release from the link here:  https://www.python.org/doc/versions/.

----------
nosy: +ned.deily
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38489>
_______________________________________

From report at bugs.python.org  Tue Oct 15 17:39:29 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Oct 2019 21:39:29 +0000
Subject: [issue32856] Optimize the `for y in [x]` idiom in comprehensions
In-Reply-To: <1518770483.24.0.467229070634.issue32856@psf.upfronthosting.co.za>
Message-ID: <1571175569.19.0.128105734525.issue32856@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I just discovered that the assignment operator leaks variables out of comprehensions.

>>> [(j:=i*i)+1/j for i in range(1, 3)]
[2.0, 4.25]
>>> j
4
>>> g = ((j:=i*i*i)+1/j for i in range(1, 3))
>>> list(g)
[2.0, 8.125]
>>> j
8

So it does not supersedes this optimization.

----------
resolution: rejected -> 
stage: resolved -> 
status: closed -> open
versions: +Python 3.9 -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32856>
_______________________________________

From report at bugs.python.org  Tue Oct 15 17:40:09 2019
From: report at bugs.python.org (=?utf-8?q?Tymek_Wo=C5=82od=C5=BAko?=)
Date: Tue, 15 Oct 2019 21:40:09 +0000
Subject: [issue38490] statistics: add covariance and Pearson's correlation
Message-ID: <1571175609.51.0.475949905245.issue38490@roundup.psfhosted.org>


New submission from Tymek Wo?od?ko <twolodzko at gmail.com>:

Covariance and Pearson's correlation are one of the most basic bivariate statistics.

https://en.wikipedia.org/wiki/Covariance
https://en.wikipedia.org/wiki/Pearson_correlation_coefficient

----------
messages: 354754
nosy: Tymek Wo?od?ko
priority: normal
severity: normal
status: open
title: statistics: add covariance and Pearson's correlation
type: enhancement
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38490>
_______________________________________

From report at bugs.python.org  Tue Oct 15 17:46:38 2019
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 15 Oct 2019 21:46:38 +0000
Subject: [issue38490] statistics: add covariance and Pearson's correlation
In-Reply-To: <1571175609.51.0.475949905245.issue38490@roundup.psfhosted.org>
Message-ID: <1571175998.68.0.716345324982.issue38490@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +16364
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16813

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38490>
_______________________________________

From report at bugs.python.org  Tue Oct 15 18:00:16 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Oct 2019 22:00:16 +0000
Subject: [issue32856] Optimize the `for y in [x]` idiom in comprehensions
In-Reply-To: <1518770483.24.0.467229070634.issue32856@psf.upfronthosting.co.za>
Message-ID: <1571176816.23.0.754198065079.issue32856@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16365
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16814

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32856>
_______________________________________

From report at bugs.python.org  Tue Oct 15 19:17:59 2019
From: report at bugs.python.org (Jim Carroll)
Date: Tue, 15 Oct 2019 23:17:59 +0000
Subject: [issue38482] BUG in codecs.BufferedIncrementalDecoder
In-Reply-To: <1571127690.05.0.477916235895.issue38482@roundup.psfhosted.org>
Message-ID: <1571181479.93.0.222195707465.issue38482@roundup.psfhosted.org>


Jim Carroll <jim at carroll.com> added the comment:

I understand.

btw; I did a deep dive on cpython codebase, and the only references to codecs.iterencode()/iterdecode() is in ./Lib/tests/test_codecs.py. I suspect functions are not used by many people.

The patch I proposed was a three line change that would allow passing either an int or bytes...not sure if that sways any opinions on this topic.

If we decide to just stick with existing functionality, a small clarification to the docs might be in order?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38482>
_______________________________________

From report at bugs.python.org  Tue Oct 15 19:24:58 2019
From: report at bugs.python.org (Bernie Hackett)
Date: Tue, 15 Oct 2019 23:24:58 +0000
Subject: [issue17123] Add OCSP support to ssl module
In-Reply-To: <1359994472.8.0.804183286731.issue17123@psf.upfronthosting.co.za>
Message-ID: <1571181898.14.0.148116117299.issue17123@roundup.psfhosted.org>


Bernie Hackett <bernie.hackett at gmail.com> added the comment:

OCSP is the only way Let's Encrypt supports revocation. It would be really useful to have stapling verification supported in the standard library, even just the callback support PyOpenSSL supports.

https://letsencrypt.org/docs/revoking/

----------
nosy: +behackett

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17123>
_______________________________________

From report at bugs.python.org  Tue Oct 15 19:30:24 2019
From: report at bugs.python.org (devlocalca)
Date: Tue, 15 Oct 2019 23:30:24 +0000
Subject: [issue38491] Can not build Python 3.8.0 on Linux - missing
 dependencies
Message-ID: <1571182224.79.0.802019819326.issue38491@roundup.psfhosted.org>


New submission from devlocalca <devlocalca at gmail.com>:

I can not build the 3.8.0 source code on Linux due to missing dependencies that I cannot find.

More information here:

https://www.reddit.com/r/Python/comments/digewe/python_38_not_possible_to_install_on_linux_why/

Can someone please show me how to build/install Python 3.8.0 on Linux from source, as Python 3.8.0 is not available to install from any RHEL 8 / CentOS 8 repo.

Email:  devlocalca at gmail.com

----------
components: Build
messages: 354757
nosy: devlocalca
priority: normal
severity: normal
status: open
title: Can not build Python 3.8.0 on Linux - missing dependencies
type: compile error
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38491>
_______________________________________

From report at bugs.python.org  Tue Oct 15 19:36:26 2019
From: report at bugs.python.org (Shane Harvey)
Date: Tue, 15 Oct 2019 23:36:26 +0000
Subject: [issue17123] Add OCSP support to ssl module
In-Reply-To: <1359994472.8.0.804183286731.issue17123@psf.upfronthosting.co.za>
Message-ID: <1571182586.5.0.51511565982.issue17123@roundup.psfhosted.org>


Change by Shane Harvey <shnhrv at gmail.com>:


----------
nosy: +ShaneHarvey

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17123>
_______________________________________

From report at bugs.python.org  Tue Oct 15 19:37:08 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 23:37:08 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571182628.25.0.516847637136.issue35998@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16366
pull_request: https://github.com/python/cpython/pull/16815

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Tue Oct 15 19:41:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 23:41:07 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571182867.4.0.751201151852.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I can reproduce the bug on my laptop with the command:

./python -u -m test test_asyncio -m test.test_asyncio.test_sslproto.SelectorStartTLSTests.test_start_tls_server_1 -F -j100

It's a race condition in the test itself, not in asyncio. PR 16815 fix it.

I also got access to Zachary Ware's Gentoo buildbot worker where I can also easily reproduce the bug using "... -F -j2".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Tue Oct 15 19:49:25 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Oct 2019 23:49:25 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571183365.56.0.478513104139.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> I also got access to Zachary Ware's Gentoo buildbot worker where I can also easily reproduce the bug using "... -F -j2".

FYI disabling TLSv1.3 works around the issue on this worker. (It doesn't fix the bug, only hides it.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Tue Oct 15 20:02:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 00:02:26 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571184146.15.0.440940377036.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

FYI "test_start_tls_server_1()" is failing since at least 2017-12-30:
https://bugs.python.org/issue32458#msg309244

I hope that my latest fix will be the last to finally make the test stable.

But I always write that, and the bug always strike me in my back. So I'm now hopeless :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Tue Oct 15 20:36:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 00:36:47 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571186207.65.0.516562529693.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset fab4ef2df0857ab0c97f3058ac5ec3280c4eb891 by Victor Stinner in branch 'master':
bpo-35998: Fix test_asyncio.test_start_tls_server_1() (GH-16815)
https://github.com/python/cpython/commit/fab4ef2df0857ab0c97f3058ac5ec3280c4eb891


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Tue Oct 15 20:47:01 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 00:47:01 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571186821.48.0.365021515781.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

This change needs to be backported to 3.7 and 3.8, but I prefer to wait to see if buildbots like this new change, before doing the backport.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Tue Oct 15 20:50:55 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 16 Oct 2019 00:50:55 +0000
Subject: [issue38490] statistics: add covariance and Pearson's correlation
In-Reply-To: <1571175609.51.0.475949905245.issue38490@roundup.psfhosted.org>
Message-ID: <1571187055.14.0.578198877517.issue38490@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

These two functions are right on the boundary edge of what the statistics module is trying to do, """The module is not intended to be a competitor to third-party libraries such as NumPy, SciPy, or proprietary full-featured statistics packages aimed at professional statisticians such as Minitab, SAS and Matlab. It is aimed at the level of graphing and scientific calculators."""

It is debatable which side of the boundary they belong to. MS Excel has both of these functions, but it isn't a given that a scientific calculator would have them.

Also, the current functions require only high-school level knowledge, but these two require more skill to learn, use, and interpret.

----------
assignee:  -> steven.daprano
nosy: +rhettinger, steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38490>
_______________________________________

From report at bugs.python.org  Tue Oct 15 20:53:33 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 16 Oct 2019 00:53:33 +0000
Subject: [issue32856] Optimize the `for y in [x]` idiom in comprehensions
In-Reply-To: <1518770483.24.0.467229070634.issue32856@psf.upfronthosting.co.za>
Message-ID: <1571187213.38.0.430876409492.issue32856@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

> I just discovered that the assignment operator leaks variables
> out of comprehensions.
> ...
> So it does not supersedes this optimization.

That's a real bummer.  IIRC, it was discussion of this proposal that motivated the creation of the walrus operator.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32856>
_______________________________________

From report at bugs.python.org  Tue Oct 15 21:37:51 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 01:37:51 +0000
Subject: [issue36389] Add gc.enable_object_debugger(): detect corrupted Python
 objects in the GC
In-Reply-To: <1553166161.96.0.697085261419.issue36389@roundup.psfhosted.org>
Message-ID: <1571189871.68.0.370681978713.issue36389@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16367
pull_request: https://github.com/python/cpython/pull/16816

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36389>
_______________________________________

From report at bugs.python.org  Tue Oct 15 21:37:51 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 01:37:51 +0000
Subject: [issue38070] visit_decref(): add an assertion to check that the
 object is not freed
In-Reply-To: <1568037936.88.0.10373402622.issue38070@roundup.psfhosted.org>
Message-ID: <1571189871.81.0.00373441138328.issue38070@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16368
pull_request: https://github.com/python/cpython/pull/16816

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38070>
_______________________________________

From report at bugs.python.org  Tue Oct 15 22:03:12 2019
From: report at bugs.python.org (evaldas)
Date: Wed, 16 Oct 2019 02:03:12 +0000
Subject: [issue38492] Microsoft Store app IDLE (Python 3.8) has dependency on
 msvcp140.dll
Message-ID: <1571191392.22.0.935623826778.issue38492@roundup.psfhosted.org>


New submission from evaldas <evaldaz at gmail.com>:

OS: x64 Windows 10 Professional 1903 fresh installation (with latest updates)

Python 3.8 app (final version 3.8.0, not RC) installation from Microsoft Store adds two shortcuts to the Start menu:
- Python 3.8
- IDLE (Python 3.8)

Clicking the "Python 3.8" (python3.8.exe) starts Python interpreter - all fine and good.

Clicking the "IDLE (Python 3.8)" (idle3.8.exe) displays only the error message "MSVCP140.DLL was not found" (I do not remember exact sentence, because eventually I manually installed Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019).

----------
assignee: terry.reedy
components: IDLE, Windows
messages: 354765
nosy: evaldas, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Microsoft Store app IDLE (Python 3.8) has dependency on msvcp140.dll
type: crash
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38492>
_______________________________________

From report at bugs.python.org  Tue Oct 15 23:49:58 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 16 Oct 2019 03:49:58 +0000
Subject: [issue38492] Microsoft Store app IDLE (Python 3.8) needs msvcp140.dll
In-Reply-To: <1571191392.22.0.935623826778.issue38492@roundup.psfhosted.org>
Message-ID: <1571197798.86.0.228282998232.issue38492@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
assignee: terry.reedy -> 
components: +Installation
title: Microsoft Store app IDLE (Python 3.8) has dependency on msvcp140.dll -> Microsoft Store app IDLE (Python 3.8) needs msvcp140.dll
type: crash -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38492>
_______________________________________

From report at bugs.python.org  Tue Oct 15 23:56:53 2019
From: report at bugs.python.org (Neil Schemenauer)
Date: Wed, 16 Oct 2019 03:56:53 +0000
Subject: [issue38006] Crash in remove() weak reference callback of
 weakref.WeakValueDictionary at Python exit
In-Reply-To: <1567417707.23.0.718072799916.issue38006@roundup.psfhosted.org>
Message-ID: <1571198213.47.0.462988959042.issue38006@roundup.psfhosted.org>


Neil Schemenauer <nas-python at arctrix.com> added the comment:


New changeset 392a13bb9346331b087bcd8bb1b37072c126abee by Neil Schemenauer in branch 'master':
bpo-38006: Add unit test for weakref clear bug (GH-16788)
https://github.com/python/cpython/commit/392a13bb9346331b087bcd8bb1b37072c126abee


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38006>
_______________________________________

From report at bugs.python.org  Wed Oct 16 00:20:06 2019
From: report at bugs.python.org (Louis Huemiller)
Date: Wed, 16 Oct 2019 04:20:06 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
In-Reply-To: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>
Message-ID: <1571199606.02.0.290683620668.issue38477@roundup.psfhosted.org>


Louis Huemiller <lhuemill at gmail.com> added the comment:

Attached is a chart, which shows the results from the runs mentioned in the initial post.  This chart was produced through the use of:

  ../permutations2x2_chart_results \
    -f ./20191011b_chart.svg \ 
 C++unordered_map:./20191011b_magiccube2x2_permutations_cxx_unordered_map \
        Python2.7:./20191011b_magiccube2x2_permutations_python2.7 \
        Python3.6:./20191011b_magiccube2x2_permutations_python3.6 \
        Python3.7:./20191011b_magiccube2x2_permutations_python3.7 \
       
  Python3.8.0rc1:./20191011b_magiccube2x2_permutations_python3.8.0rc1

The permutations2x2_chart_results program is present in the gist.github repository mentioned in the initial post.

----------
Added file: https://bugs.python.org/file48664/20191011b_chart.svg

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Wed Oct 16 00:32:13 2019
From: report at bugs.python.org (Louis Huemiller)
Date: Wed, 16 Oct 2019 04:32:13 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
In-Reply-To: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>
Message-ID: <1571200333.38.0.759910288277.issue38477@roundup.psfhosted.org>


Louis Huemiller <lhuemill at gmail.com> added the comment:

Each of the Python runs mentioned in the initial post took around 4 hours to execute. Although not as accurate, the issue can be demonstrated in less than 5 minutes through the use of:

  # If needed use the following to install Python3.8.0rc1
  $ apt-get update
  $ sudo apt-get upgrade
  $ sudo add-apt-repository ppa:deadsnakes/ppa
  $ sudo apt update
  $ sudo apt install python3.8

  # Use Python3.7 to produce baseline.
  $ python3.7 permutations2x2 --max_depth 6 | egrep "^# Total_Time"

  # Perform Python3.8.0rc1 execution
  python3.8 permutations2x2 --max_depth 6 | egrep "^# Total_Time"

When I did this on my server the Python3.7 execution produced:

  # Total_Time: 62.46

While the Python3.8.0rc1 execution produced:

  # Total_Time: 79.72

By running the program with "--max_depth 6" specified, the program only traversed through permutations that are up to 6 moves from the initial position. Although much less than running through an unlimited number of moves, the above run still showed the Python3.8.0rc1 run as 26.7% ((79.72 - 62.46) / 62.46) slower than the Python3.7 execution. Which is close to the 28.6% reduction in performance seen from runs with unlimited depth of moves.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Wed Oct 16 00:36:12 2019
From: report at bugs.python.org (clintolsen)
Date: Wed, 16 Oct 2019 04:36:12 +0000
Subject: [issue38493] os.CLD_KILLED should be implemented
Message-ID: <1571200572.77.0.0960305175101.issue38493@roundup.psfhosted.org>


New submission from clintolsen <clint.olsen at gmail.com>:

I was running some experiments with os.waitid() and noticed that os.CLD_KILLED is not listed in the documentation.

However, if a process is killed by the system this (missing) value is returned from this function. It seems like possible constant values should be covered or at least documented as such? How should we code around unsupported constant values?

----------
messages: 354769
nosy: clintolsen
priority: normal
severity: normal
status: open
title: os.CLD_KILLED should be implemented
type: enhancement
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38493>
_______________________________________

From report at bugs.python.org  Wed Oct 16 01:41:34 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 16 Oct 2019 05:41:34 +0000
Subject: [issue38490] statistics: add covariance and Pearson's correlation
In-Reply-To: <1571175609.51.0.475949905245.issue38490@roundup.psfhosted.org>
Message-ID: <1571204494.05.0.756540524409.issue38490@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
components: +Library (Lib)
versions:  -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38490>
_______________________________________

From report at bugs.python.org  Wed Oct 16 01:47:03 2019
From: report at bugs.python.org (Inada Naoki)
Date: Wed, 16 Oct 2019 05:47:03 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
In-Reply-To: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>
Message-ID: <1571204823.02.0.151695545526.issue38477@roundup.psfhosted.org>


Change by Inada Naoki <songofacandy at gmail.com>:


----------
nosy: +inada.naoki

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Wed Oct 16 02:22:50 2019
From: report at bugs.python.org (valkheim)
Date: Wed, 16 Oct 2019 06:22:50 +0000
Subject: [issue38494] Add assert_not_called_with
Message-ID: <1571206970.26.0.707248566898.issue38494@roundup.psfhosted.org>


New submission from valkheim <valkheim at protonmail.com>:

This would be nice to integrate an assert_not_called_with feature.

I had to implement it to test a publish/subscribe patterns where multiple subscibers got called but not with the same arguments.

Here is my implementation:

```
def assert_not_called_with(self, *args, **kwargs):
    """assert that the mock was never called with the specified arguments.
    """
    try:
        self.assert_called_with(*args, **kwargs)
    except AssertionError:
        return
    raise AssertionError(
        "Expected %s to not have been called."
        % self._format_mock_call_signature(args, kwargs)
    )
```

An alternative would had been to iterate the call_args_list but it wouldn't result in a clean one-line assert

coming from: https://github.com/testing-cabal/mock/issues/473

----------
messages: 354770
nosy: valkheim
priority: normal
severity: normal
status: open
title: Add assert_not_called_with
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38494>
_______________________________________

From report at bugs.python.org  Wed Oct 16 02:28:01 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Wed, 16 Oct 2019 06:28:01 +0000
Subject: [issue38474] digit check logic can be replaced by Py_ISDIGIT on
 prepare_s
In-Reply-To: <1571077834.59.0.937971525821.issue38474@roundup.psfhosted.org>
Message-ID: <1571207281.66.0.68869482538.issue38474@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

> Rewriting all this code just because we have Py_ISDIGIT() is a code churn.

I'm inclined to agree: the current code works and is efficient; there's no strong reason to change it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38474>
_______________________________________

From report at bugs.python.org  Wed Oct 16 02:34:40 2019
From: report at bugs.python.org (Inada Naoki)
Date: Wed, 16 Oct 2019 06:34:40 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
In-Reply-To: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>
Message-ID: <1571207680.02.0.414718143735.issue38477@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

I can not confirm performance regression in 3.8.0.

$ time ~/pyenv/versions/3.7.3/bin/python permutations2x2 --max_depth 6 | egrep "^# Total_Time" ; time ~/pyenv/versions/3.8.0/bin/python permutations2x2 --max_depth 6 | egrep "^# Total_Time"
# Total_Time: 50.24

real    0m50.665s                                                                                                                                                                                                                                                             user    0m49.729s
sys     0m4.354s
# Total_Time: 47.97

real    0m48.502s
user    0m47.380s
sys     0m4.506s

I suspect that this is a binary specific issue.

Would you try "perf record python ..."?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Wed Oct 16 02:35:21 2019
From: report at bugs.python.org (Inada Naoki)
Date: Wed, 16 Oct 2019 06:35:21 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
In-Reply-To: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>
Message-ID: <1571207721.44.0.974766313268.issue38477@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

Ah, my bad.  I meant `perf stat python ...`.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Wed Oct 16 02:47:31 2019
From: report at bugs.python.org (Inada Naoki)
Date: Wed, 16 Oct 2019 06:47:31 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
In-Reply-To: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>
Message-ID: <1571208451.76.0.355976967358.issue38477@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

Deadsneak Python 3.8:

>>> sysconfig.get_config_var('CFLAGS')
'-Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g   -fstack-protector-strong -Wformat -Werror=format-security'

Disco /usr/bin/python3.7:

>>> sysconfig.get_config_var('CFLAGS')
'-Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g   -fstack-protector-strong -Wformat -Werror=format-security  -g -flto -fuse-linker-plugin -ffat-lto-objects'

So the performance difference comes from optimization options.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Wed Oct 16 02:52:17 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 16 Oct 2019 06:52:17 +0000
Subject: [issue38494] Add assert_not_called_with
In-Reply-To: <1571206970.26.0.707248566898.issue38494@roundup.psfhosted.org>
Message-ID: <1571208737.13.0.866217170108.issue38494@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +cjw296, lisroach, mariocj89, michael.foord, xtreak
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38494>
_______________________________________

From report at bugs.python.org  Wed Oct 16 02:56:02 2019
From: report at bugs.python.org (=?utf-8?q?Tymek_Wo=C5=82od=C5=BAko?=)
Date: Wed, 16 Oct 2019 06:56:02 +0000
Subject: [issue38490] statistics: add covariance and Pearson's correlation
In-Reply-To: <1571187055.14.0.578198877517.issue38490@roundup.psfhosted.org>
Message-ID: <CAHa5zCtuwCwztPU0S1Nj=+H37wLwa+DWLorSwF9ZUSKHR5Vj2Q@mail.gmail.com>


Tymek Wo?od?ko <twolodzko at gmail.com> added the comment:

I think I see your point, that the module is intended for the most basic
features, but I would argue that correlation is one of such "most basic"
statistics.

Correlation and covariance can be thought as equivalents for standard
deviation and variance, but when we are talking about pairs of variables.
Moreover it is probably used much more often then things like geometric or
harmonic mean, that are implemented in the package. Covariance is probably
more esoteric for most non-statisticians, but in my PR (
https://github.com/python/cpython/pull/16813 ) I implemented it for
completeness and as a helper function for the correlation coefficient.

TL;DR those are basic statistics. They would make the module much more
helpful, since the basic statistics could be calculated using base python
w/o external libraries. They are also trivial to implemented (done this in
PR) and do not need much more maintenance then the other functionalities in
the module.

Tim

?r., 16 pa? 2019 o 02:50 Raymond Hettinger <report at bugs.python.org>
napisa?(a):

>
> Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:
>
> These two functions are right on the boundary edge of what the statistics
> module is trying to do, """The module is not intended to be a competitor to
> third-party libraries such as NumPy, SciPy, or proprietary full-featured
> statistics packages aimed at professional statisticians such as Minitab,
> SAS and Matlab. It is aimed at the level of graphing and scientific
> calculators."""
>
> It is debatable which side of the boundary they belong to. MS Excel has
> both of these functions, but it isn't a given that a scientific calculator
> would have them.
>
> Also, the current functions require only high-school level knowledge, but
> these two require more skill to learn, use, and interpret.
>
> ----------
> assignee:  -> steven.daprano
> nosy: +rhettinger, steven.daprano
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue38490>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38490>
_______________________________________

From report at bugs.python.org  Wed Oct 16 03:01:40 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 16 Oct 2019 07:01:40 +0000
Subject: [issue38474] digit check logic can be replaced by Py_ISDIGIT on
 prepare_s
In-Reply-To: <1571077834.59.0.937971525821.issue38474@roundup.psfhosted.org>
Message-ID: <1571209300.73.0.102225544904.issue38474@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> I'm inclined to agree: the current code works and is efficient; there's no strong reason to change it.

Okay, then I will close the PR.
I respect core developer's opinions.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38474>
_______________________________________

From report at bugs.python.org  Wed Oct 16 03:07:25 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 16 Oct 2019 07:07:25 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
In-Reply-To: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>
Message-ID: <1571209645.9.0.158467524884.issue38477@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

If I compile my own 3.7.5 and 3.8.0 both with --enable-optimizations, I am unable to reproduce this.

greg at zoonaut:~/sandbox/python/cpython/lh$ ../b37/python permutations2x2 --max_depth 6 | egrep "^# Total_Time"
# Total_Time: 75.92
greg at zoonaut:~/sandbox/python/cpython/lh$ ../b38/python permutations2x2 --max_depth 6 | egrep "^# Total_Time"
# Total_Time: 84.53
greg at zoonaut:~/sandbox/python/cpython/lh$ ../b37/python permutations2x2 --max_depth 6 | egrep "^# Total_Time"
# Total_Time: 79.90
greg at zoonaut:~/sandbox/python/cpython/lh$ ../b38/python permutations2x2 --max_depth 6 | egrep "^# Total_Time"
# Total_Time: 84.19
greg at zoonaut:~/sandbox/python/cpython/lh$ ../b37/python permutations2x2 --max_depth 6 | egrep "^# Total_Time"
# Total_Time: 86.49
greg at zoonaut:~/sandbox/python/cpython/lh$ ../b37/python permutations2x2 --max_depth 6 | egrep "^# Total_Time"
# Total_Time: 83.95
greg at zoonaut:~/sandbox/python/cpython/lh$ ../b38/python permutations2x2 --max_depth 6 | egrep "^# Total_Time"
# Total_Time: 78.85
greg at zoonaut:~/sandbox/python/cpython/lh$ ../b38/python permutations2x2 --max_depth 6 | egrep "^# Total_Time"
# Total_Time: 78.49

which if you add up the 3.7 and 3.8 times over their four runs each, they both come out to ~81 seconds average.  So I don't see a regression.

I'd say that benchmark is unstable.  Also, making sure you're comparing identically prepared builds of cpython rather than something made by different distro package owners.

----------
nosy: +gregory.p.smith -inada.naoki
resolution: not a bug -> 
stage: resolved -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Wed Oct 16 03:14:08 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 16 Oct 2019 07:14:08 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
In-Reply-To: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>
Message-ID: <1571210048.27.0.571757194799.issue38477@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Wed Oct 16 03:16:30 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 16 Oct 2019 07:16:30 +0000
Subject: [issue38474] digit check logic can be replaced by Py_ISDIGIT on
 prepare_s
In-Reply-To: <1571077834.59.0.937971525821.issue38474@roundup.psfhosted.org>
Message-ID: <1571210190.13.0.187774117681.issue38474@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
resolution:  -> wont fix
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38474>
_______________________________________

From report at bugs.python.org  Wed Oct 16 03:36:41 2019
From: report at bugs.python.org (Alex Mashianov)
Date: Wed, 16 Oct 2019 07:36:41 +0000
Subject: [issue38495] print built-in function docs bug
Message-ID: <1571211401.15.0.283514863374.issue38495@roundup.psfhosted.org>


New submission from Alex Mashianov <mashianov at gmail.com>:

Python docs says print() function default sep='': http://joxi.ru/EA44JnfonNwLAb.png

While in reality sep=' ':
http://joxi.ru/n2YXyRsbw6oYm6.png

Probably it's a bug with space not being escaped in html to prevent trimming.

----------
assignee: docs at python
components: Documentation
messages: 354778
nosy: Alex Mashianov, docs at python
priority: normal
severity: normal
status: open
title: print built-in function docs bug
type: enhancement
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38495>
_______________________________________

From report at bugs.python.org  Wed Oct 16 03:38:27 2019
From: report at bugs.python.org (Inada Naoki)
Date: Wed, 16 Oct 2019 07:38:27 +0000
Subject: [issue38373] List overallocation strategy
In-Reply-To: <1570229023.08.0.986734049649.issue38373@roundup.psfhosted.org>
Message-ID: <1571211507.05.0.606985717937.issue38373@roundup.psfhosted.org>


Change by Inada Naoki <songofacandy at gmail.com>:


----------
nosy: +inada.naoki

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38373>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:00:10 2019
From: report at bugs.python.org (Mikko Rantalainen)
Date: Wed, 16 Oct 2019 08:00:10 +0000
Subject: [issue38496] Python3 allows mixture of tabs and spaces for indentation
Message-ID: <1571212810.12.0.63942359908.issue38496@roundup.psfhosted.org>


New submission from Mikko Rantalainen <mikko.rantalainen at peda.net>:

Contrary to PEP-8 (https://www.python.org/dev/peps/pep-0008/#tabs-or-spaces) claiming "Python 3 disallows mixing the use of tabs and spaces for indentation", in reality Python 3 allows mixing tabs and spaces without warnings or errors. For example (with all spaces replaced with middle dot and all spaces replaced with a short arrow):

#!/usr/bin/python3
for?i?in?range(2):
??for?j?in?range(3):
???for?k?in?range(4):
?????print(i,j,k,sep=",")

Either the PEP-8 should be fixed or the parser/compiler should be fixed. 

The current behavior seems a bit unstable because the exact order of spaces and tabs causes "TabError: inconsistent use of tabs and spaces in indentation" to appear more or less random.

I'd prefer python3 to require that *all whitespace* at the start of the all the lines is tabs for the whole file or spaces for the whole file. And first indented line sets the preference for the whole file.

(Personally I'd prefer tabs contrary to PEP-8 language but this bug is not about the preference. This is PEP-8 claiming things that are not true.)

$ python3 --version
Python 3.5.2

----------
components: Interpreter Core
messages: 354779
nosy: Mikko Rantalainen
priority: normal
severity: normal
status: open
title: Python3 allows mixture of tabs and spaces for indentation
versions: Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38496>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:05:23 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 16 Oct 2019 08:05:23 +0000
Subject: [issue38496] Python3 allows mixture of tabs and spaces for indentation
In-Reply-To: <1571212810.12.0.63942359908.issue38496@roundup.psfhosted.org>
Message-ID: <1571213123.06.0.377713951501.issue38496@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

I can verify this on 3.7.4.

----------
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38496>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:13:45 2019
From: report at bugs.python.org (=?utf-8?b?SWxhw68=?=)
Date: Wed, 16 Oct 2019 08:13:45 +0000
Subject: [issue38497] Wrong argument name in documentation for
 pipes.Template.open
Message-ID: <1571213625.11.0.339305647326.issue38497@roundup.psfhosted.org>


New submission from Ila? <ilaideutel at gmail.com>:

Documentation for the pipes module indicates that the second argument of open()
is "mode", but it is actually "rw".

Python 3.7.4 (default, Oct  4 2019, 06:57:26)
[GCC 9.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from pipes import Template; Template().open('/tmp/f', mode='r')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: open() got an unexpected keyword argument 'mode'

Python 2.7.16 (default, Mar 11 2019, 18:59:25)
[GCC 8.2.1 20181127] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from pipes import Template; Template().open('/tmp/f', mode='r')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: open() got an unexpected keyword argument 'mode'

https://docs.python.org/3/library/pipes.html#pipes.Template.open

----------
assignee: docs at python
components: Documentation
messages: 354781
nosy: docs at python, ilai
priority: normal
severity: normal
status: open
title: Wrong argument name in documentation for pipes.Template.open
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38497>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:16:16 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 16 Oct 2019 08:16:16 +0000
Subject: [issue38495] print built-in function docs bug
In-Reply-To: <1571211401.15.0.283514863374.issue38495@roundup.psfhosted.org>
Message-ID: <1571213776.66.0.42640729308.issue38495@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

In the sphinx source it's ' ' so maybe it's a problem with the rendering part.

https://raw.githubusercontent.com/python/cpython/master/Doc/library/functions.rst

.. function:: print(*objects, sep=' ', end='\\n', file=sys.stdout, flush=False)

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38495>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:18:07 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 16 Oct 2019 08:18:07 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571213887.86.0.495121105114.issue35998@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16369
pull_request: https://github.com/python/cpython/pull/16817

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:25:52 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 08:25:52 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571214352.21.0.202532880988.issue35998@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16370
pull_request: https://github.com/python/cpython/pull/16818

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:31:27 2019
From: report at bugs.python.org (Inada Naoki)
Date: Wed, 16 Oct 2019 08:31:27 +0000
Subject: [issue38495] print built-in function docs bug
In-Reply-To: <1571211401.15.0.283514863374.issue38495@roundup.psfhosted.org>
Message-ID: <1571214687.7.0.531272862097.issue38495@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

Space is not trimmed. You can confirm there is a space by copy&paste it from rendered HTML.

  print(*objects, sep=' ', end='\n', file=sys.stdout, flush=False)?

So this is caused by rendering <em>sep=' '</em>.
I don't like <em>, but I'm not sure this can be customized by theme.

----------
nosy: +inada.naoki

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38495>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:37:01 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 16 Oct 2019 08:37:01 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571215021.69.0.155638395872.issue35998@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset afbcd9f26d1bf5390f56f18c9afbf753e48f230d by Miss Islington (bot) in branch '3.8':
bpo-35998: Fix test_asyncio.test_start_tls_server_1() (GH-16815)
https://github.com/python/cpython/commit/afbcd9f26d1bf5390f56f18c9afbf753e48f230d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:39:12 2019
From: report at bugs.python.org (Weiliang Li)
Date: Wed, 16 Oct 2019 08:39:12 +0000
Subject: [issue38498] The expression '' in '' == '' is evaluated as True
Message-ID: <1571215152.37.0.955381336834.issue38498@roundup.psfhosted.org>


Change by Weiliang Li <to.be.impressive at gmail.com>:


----------
nosy: kigawas
priority: normal
severity: normal
status: open
title: The expression '' in '' == '' is evaluated as True
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38498>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:40:14 2019
From: report at bugs.python.org (Weiliang Li)
Date: Wed, 16 Oct 2019 08:40:14 +0000
Subject: [issue38498] The expression '' in '' == '' is evaluated as True
Message-ID: <1571215214.87.0.1528825259.issue38498@roundup.psfhosted.org>


New submission from Weiliang Li <to.be.impressive at gmail.com>:

In [1]: '' in '' == ''                                                                                                
Out[1]: True

In [2]: 'a' in 'a' == 'a'                                                                                             
Out[2]: True

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38498>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:47:09 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Wed, 16 Oct 2019 08:47:09 +0000
Subject: [issue38490] statistics: add covariance and Pearson's correlation
In-Reply-To: <CAHa5zCtuwCwztPU0S1Nj=+H37wLwa+DWLorSwF9ZUSKHR5Vj2Q@mail.gmail.com>
Message-ID: <20191016084701.GD11150@ando.pearwood.info>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

I can't speak for other countries, but in Australia, secondary school 
mathematics teaches correlation coefficient and linear regression from 
Year 11 onwards (typically ages 16 or 17). Covariance is not itself 
taught, and as far as I can tell neither the TI-83 nor NSpire 
provides a built-in covariance command.

On the other hand, other calculators such as the HP-48GX do.

Oddly, Excel provides the population (not sample) covariance:

https://support.office.com/en-us/article/COVARIANCE-P-function-6F0E1E6D-956D-4E4B-9943-CFEF0BF9EDFC

OpenOffice and LibreOffice also provide a covariance function.

I think that supporting correlation coefficient `r` and linear 
regression would be clear wins, from the perspective of secondary school 
maths. But as far as covariance goes, it would help convince me if you 
had either:

- evidence that covariance is taught in secondary schools, or at 
  least first year undergraduate statistics;

- that it has use-cases beyond "helper for calculating r";

- or that there is demand for it from people who want covariance 
  but can't, or don't want to, use numpy/scipy.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38490>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:51:44 2019
From: report at bugs.python.org (Weiliang Li)
Date: Wed, 16 Oct 2019 08:51:44 +0000
Subject: [issue38498] The expression '' in '' == '' is evaluated as True
In-Reply-To: <1571215214.87.0.1528825259.issue38498@roundup.psfhosted.org>
Message-ID: <1571215904.66.0.112045562091.issue38498@roundup.psfhosted.org>


Weiliang Li <to.be.impressive at gmail.com> added the comment:

https://docs.python.org/3/reference/expressions.html#comparisons

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38498>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:51:54 2019
From: report at bugs.python.org (Weiliang Li)
Date: Wed, 16 Oct 2019 08:51:54 +0000
Subject: [issue38498] The expression '' in '' == '' is evaluated as True
In-Reply-To: <1571215214.87.0.1528825259.issue38498@roundup.psfhosted.org>
Message-ID: <1571215914.24.0.204646904106.issue38498@roundup.psfhosted.org>


Change by Weiliang Li <to.be.impressive at gmail.com>:


----------
resolution:  -> works for me

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38498>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:52:08 2019
From: report at bugs.python.org (Weiliang Li)
Date: Wed, 16 Oct 2019 08:52:08 +0000
Subject: [issue38498] The expression '' in '' == '' is evaluated as True
In-Reply-To: <1571215214.87.0.1528825259.issue38498@roundup.psfhosted.org>
Message-ID: <1571215928.38.0.594765550568.issue38498@roundup.psfhosted.org>


Change by Weiliang Li <to.be.impressive at gmail.com>:


----------
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38498>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:57:31 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Wed, 16 Oct 2019 08:57:31 +0000
Subject: [issue38496] Python3 allows mixture of tabs and spaces for indentation
In-Reply-To: <1571212810.12.0.63942359908.issue38496@roundup.psfhosted.org>
Message-ID: <1571216251.77.0.025313567847.issue38496@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

I believe that the interpreter only requires that each block is consistent, not that all blocks in a module are consistent.

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38496>
_______________________________________

From report at bugs.python.org  Wed Oct 16 04:57:55 2019
From: report at bugs.python.org (Inada Naoki)
Date: Wed, 16 Oct 2019 08:57:55 +0000
Subject: [issue38495] print built-in function docs bug
In-Reply-To: <1571211401.15.0.283514863374.issue38495@roundup.psfhosted.org>
Message-ID: <1571216275.54.0.522440084715.issue38495@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

https://github.com/sphinx-doc/sphinx/pull/6401/files

Recent Sphinx uses <em class="sig-paren">.
So we can add style like this:

  .sig-paren {
    font-family: monospace, sans-serif;
    font-style: normal;
  }

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38495>
_______________________________________

From report at bugs.python.org  Wed Oct 16 05:00:01 2019
From: report at bugs.python.org (=?utf-8?q?Juho_V=C3=A4h=C3=A4-Herttua?=)
Date: Wed, 16 Oct 2019 09:00:01 +0000
Subject: [issue38470] test_compileall fails in AMD64 Windows7 SP1 3.x
In-Reply-To: <1571013936.71.0.668005842061.issue38470@roundup.psfhosted.org>
Message-ID: <1571216401.75.0.407856191842.issue38470@roundup.psfhosted.org>


Change by Juho V?h?-Herttua <juhovh at iki.fi>:


----------
pull_requests: +16371
pull_request: https://github.com/python/cpython/pull/16819

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38470>
_______________________________________

From report at bugs.python.org  Wed Oct 16 05:06:32 2019
From: report at bugs.python.org (=?utf-8?q?Juho_V=C3=A4h=C3=A4-Herttua?=)
Date: Wed, 16 Oct 2019 09:06:32 +0000
Subject: [issue36076] ssl.get_server_certificate should use SNI
In-Reply-To: <1550832637.63.0.810742849841.issue36076@roundup.psfhosted.org>
Message-ID: <1571216792.16.0.700197825724.issue36076@roundup.psfhosted.org>


Change by Juho V?h?-Herttua <juhovh at iki.fi>:


----------
keywords: +patch
pull_requests: +16372
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16820

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36076>
_______________________________________

From report at bugs.python.org  Wed Oct 16 05:25:16 2019
From: report at bugs.python.org (=?utf-8?q?Tymek_Wo=C5=82od=C5=BAko?=)
Date: Wed, 16 Oct 2019 09:25:16 +0000
Subject: [issue38490] statistics: add covariance and Pearson's correlation
In-Reply-To: <20191016084701.GD11150@ando.pearwood.info>
Message-ID: <CAHa5zCupjtid=Q0vhbzwyCWrV5MwowN+cW2tvXC0b=1UaknqLw@mail.gmail.com>


Tymek Wo?od?ko <twolodzko at gmail.com> added the comment:

In case there is agreement with Steven, I will add simple linear regression
( https://en.wikipedia.org/wiki/Simple_linear_regression ) in the same PR,
since it is just:

slope = correlation(x, y) * ( stdev(y) / stdev(x) )
intercept = mean(y) - slope * mean(x)

As about covariance, I see your points, but why not keeping it "because we
can"? It can be useful for some users and the functionality still needs to
be implemented to have correlation coefficient.

On Wed, Oct 16, 2019 at 10:47 AM Steven D'Aprano <report at bugs.python.org>
wrote:

>
> Steven D'Aprano <steve+python at pearwood.info> added the comment:
>
> I can't speak for other countries, but in Australia, secondary school
> mathematics teaches correlation coefficient and linear regression from
> Year 11 onwards (typically ages 16 or 17). Covariance is not itself
> taught, and as far as I can tell neither the TI-83 nor NSpire
> provides a built-in covariance command.
>
> On the other hand, other calculators such as the HP-48GX do.
>
> Oddly, Excel provides the population (not sample) covariance:
>
>
> https://support.office.com/en-us/article/COVARIANCE-P-function-6F0E1E6D-956D-4E4B-9943-CFEF0BF9EDFC
>
> OpenOffice and LibreOffice also provide a covariance function.
>
> I think that supporting correlation coefficient `r` and linear
> regression would be clear wins, from the perspective of secondary school
> maths. But as far as covariance goes, it would help convince me if you
> had either:
>
> - evidence that covariance is taught in secondary schools, or at
>   least first year undergraduate statistics;
>
> - that it has use-cases beyond "helper for calculating r";
>
> - or that there is demand for it from people who want covariance
>   but can't, or don't want to, use numpy/scipy.
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue38490>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38490>
_______________________________________

From report at bugs.python.org  Wed Oct 16 05:25:58 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 16 Oct 2019 09:25:58 +0000
Subject: [issue38496] Python3 allows mixture of tabs and spaces for indentation
In-Reply-To: <1571212810.12.0.63942359908.issue38496@roundup.psfhosted.org>
Message-ID: <1571217958.46.0.712541184548.issue38496@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Thank you for your report Mikko. Yes, the heuristic used in Python 3 is unable to catch all inconsistencies in using tabs and spaces.

Such bug was already reported early. There should be an open issue.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38496>
_______________________________________

From report at bugs.python.org  Wed Oct 16 05:40:38 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 16 Oct 2019 09:40:38 +0000
Subject: [issue38495] print built-in function docs bug
In-Reply-To: <1571211401.15.0.283514863374.issue38495@roundup.psfhosted.org>
Message-ID: <1571218838.39.0.702851000492.issue38495@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Maybe just explain defaults in the text?

   Print *objects* to the text stream *file* (the standard output by default), separated by *sep* (a space by default) and followed
   by *end* (a newline by default).

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38495>
_______________________________________

From report at bugs.python.org  Wed Oct 16 05:44:41 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 09:44:41 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571219081.58.0.826349135394.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 1bceb0e58905fd6d241d7d566e19ca78558973dd by Victor Stinner in branch '3.7':
bpo-35998: Fix test_asyncio.test_start_tls_server_1() (GH-16815) (GH-16818)
https://github.com/python/cpython/commit/1bceb0e58905fd6d241d7d566e19ca78558973dd


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Wed Oct 16 05:59:14 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 09:59:14 +0000
Subject: [issue35998] test_asyncio: test_start_tls_server_1() TimeoutError on
 Fedora 29
In-Reply-To: <1550225538.04.0.738886867119.issue35998@roundup.psfhosted.org>
Message-ID: <1571219954.8.0.759788864077.issue35998@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Buildbots are green on the 3.x branch. I backported my fix to 3.7 and 3.8.

I close the issue. I hope that I will not have to reopen it again.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35998>
_______________________________________

From report at bugs.python.org  Wed Oct 16 06:59:36 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 16 Oct 2019 10:59:36 +0000
Subject: [issue38493] os.CLD_KILLED should be implemented
In-Reply-To: <1571200572.77.0.0960305175101.issue38493@roundup.psfhosted.org>
Message-ID: <1571223576.95.0.0308599744647.issue38493@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
keywords: +patch
pull_requests: +16373
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16821

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38493>
_______________________________________

From report at bugs.python.org  Wed Oct 16 07:25:06 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 16 Oct 2019 11:25:06 +0000
Subject: [issue38493] os.CLD_KILLED should be implemented
In-Reply-To: <1571200572.77.0.0960305175101.issue38493@roundup.psfhosted.org>
Message-ID: <1571225106.5.0.646271811339.issue38493@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
nosy: +corona10

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38493>
_______________________________________

From report at bugs.python.org  Wed Oct 16 07:30:15 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 16 Oct 2019 11:30:15 +0000
Subject: [issue38496] Python3 allows mixture of tabs and spaces for indentation
In-Reply-To: <1571212810.12.0.63942359908.issue38496@roundup.psfhosted.org>
Message-ID: <1571225415.16.0.727468300258.issue38496@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Seems related issue24260

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38496>
_______________________________________

From report at bugs.python.org  Wed Oct 16 07:32:00 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 16 Oct 2019 11:32:00 +0000
Subject: [issue38496] Python3 allows mixture of tabs and spaces for indentation
In-Reply-To: <1571212810.12.0.63942359908.issue38496@roundup.psfhosted.org>
Message-ID: <1571225520.66.0.712026045111.issue38496@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Thanks, Serhiy. This has been reported in 24260, so I'm closing this issue.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> TabError behavior doesn't match documentation
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38496>
_______________________________________

From report at bugs.python.org  Wed Oct 16 07:36:14 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 16 Oct 2019 11:36:14 +0000
Subject: [issue38498] The expression '' in '' == '' is evaluated as True
In-Reply-To: <1571215214.87.0.1528825259.issue38498@roundup.psfhosted.org>
Message-ID: <1571225774.48.0.81133721046.issue38498@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

For future reference:

Specifically, note that:
'' in '' == ''
is equivalent to:
('' in '') and ('' == '')

----------
nosy: +eric.smith
resolution: works for me -> not a bug

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38498>
_______________________________________

From report at bugs.python.org  Wed Oct 16 08:48:46 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 16 Oct 2019 12:48:46 +0000
Subject: [issue38493] os.CLD_KILLED should be implemented
In-Reply-To: <1571200572.77.0.0960305175101.issue38493@roundup.psfhosted.org>
Message-ID: <1571230126.1.0.536801236178.issue38493@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

What about CLD_STOPPED?

For reference, other CLD_* constants were added in issue10812.

----------
nosy: +rosslagerwall, serhiy.storchaka
versions: +Python 3.9 -Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38493>
_______________________________________

From report at bugs.python.org  Wed Oct 16 09:55:57 2019
From: report at bugs.python.org (Alori)
Date: Wed, 16 Oct 2019 13:55:57 +0000
Subject: [issue38499] Add rmtree() to pathlib.Path
Message-ID: <1571234157.02.0.903860423187.issue38499@roundup.psfhosted.org>


New submission from Alori <valorien at gmail.com>:

pathlib.Path supports deletion of both files (Path.unlink()) and directories (Path.rmdir()).

Unfortunately, Path.rmdir() does not allow deletion of non-empty directories which means users must use shutil.rmtree() when deleting such paths.

Since pathlib.Path already supports file and (empty) directory deletion, adding Path.rmtree(missing_ok=False) would support both the utility and the completeness of pathlib.

----------
components: Library (Lib)
messages: 354799
nosy: valorien
priority: normal
severity: normal
status: open
title: Add rmtree() to pathlib.Path
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38499>
_______________________________________

From report at bugs.python.org  Wed Oct 16 10:00:58 2019
From: report at bugs.python.org (Alori)
Date: Wed, 16 Oct 2019 14:00:58 +0000
Subject: [issue38194] Consistently add exist_ok / missing_ok parameters to
 directory creation/deletion functions
In-Reply-To: <1568673909.26.0.25333771691.issue38194@roundup.psfhosted.org>
Message-ID: <1571234458.91.0.593211212395.issue38194@roundup.psfhosted.org>


Alori <valorien at gmail.com> added the comment:

+1
Encountered the same issue today working with Path.rmdir().
Also see a somewhat related issue here: (https://bugs.python.org/issue38499)

----------
nosy: +valorien

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38194>
_______________________________________

From report at bugs.python.org  Wed Oct 16 10:35:42 2019
From: report at bugs.python.org (Romuald Brunet)
Date: Wed, 16 Oct 2019 14:35:42 +0000
Subject: [issue17393] stdlib import mistaken for local by import_fixer
In-Reply-To: <1362946974.63.0.419293411414.issue17393@psf.upfronthosting.co.za>
Message-ID: <1571236542.31.0.494646395255.issue17393@roundup.psfhosted.org>


Change by Romuald Brunet <romuald.brunet at gmail.com>:


----------
nosy: +Romuald

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17393>
_______________________________________

From report at bugs.python.org  Wed Oct 16 10:36:34 2019
From: report at bugs.python.org (Romuald Brunet)
Date: Wed, 16 Oct 2019 14:36:34 +0000
Subject: [issue17393] stdlib import mistaken for local by import_fixer
In-Reply-To: <1362946974.63.0.419293411414.issue17393@psf.upfronthosting.co.za>
Message-ID: <1571236594.07.0.922679671811.issue17393@roundup.psfhosted.org>


Romuald Brunet <romuald.brunet at gmail.com> added the comment:

Confirming that this issue is still present on 3.8 (and working on a fix)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17393>
_______________________________________

From report at bugs.python.org  Wed Oct 16 10:48:41 2019
From: report at bugs.python.org (Ned Deily)
Date: Wed, 16 Oct 2019 14:48:41 +0000
Subject: [issue38491] Can not build Python 3.8.0 on Linux - missing
 dependencies
In-Reply-To: <1571182224.79.0.802019819326.issue38491@roundup.psfhosted.org>
Message-ID: <1571237321.83.0.201982151447.issue38491@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

The Python bug tracker is a place to report bugs, not provide user support.  There are many other places to get that kind of help and it appears you have been receiving help elsewhere.  Good luck!

----------
nosy: +ned.deily
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38491>
_______________________________________

From report at bugs.python.org  Wed Oct 16 12:17:06 2019
From: report at bugs.python.org (Fabio Zadrozny)
Date: Wed, 16 Oct 2019 16:17:06 +0000
Subject: [issue38500] Provide a way to get/set PyInterpreterState.frame_eval
 without needing to access interpreter internals
Message-ID: <1571242626.68.0.14615334114.issue38500@roundup.psfhosted.org>


New submission from Fabio Zadrozny <fabioz at users.sourceforge.net>:

In CPython 3.7 it was possible to do:

#include "pystate.h"
...
PyThreadState *ts = PyThreadState_Get();
PyInterpreterState *interp = ts->interp;
interp->eval_frame = my_frame_eval_func;

This is no longer possible because in 3.8 the PyInterpreterState is opaque, so, Py_BUILD_CORE_MODULE needs to be defined defined and "internal/pycore_pystate.h" must be included to set PyInterpreterState.eval_frame.

This works but isn't ideal -- maybe there could be a function to set PyInterpreterState.eval_frame?

----------
components: Interpreter Core
messages: 354803
nosy: fabioz, vstinner
priority: normal
severity: normal
status: open
title: Provide a way to get/set PyInterpreterState.frame_eval without needing to access interpreter internals
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38500>
_______________________________________

From report at bugs.python.org  Wed Oct 16 12:48:31 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 16 Oct 2019 16:48:31 +0000
Subject: [issue38492] Microsoft Store app IDLE (Python 3.8) needs msvcp140.dll
In-Reply-To: <1571191392.22.0.935623826778.issue38492@roundup.psfhosted.org>
Message-ID: <1571244511.82.0.541408451902.issue38492@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

I know what this is - the fix that went into the console executable didn't make it into the windowed executable.

----------
assignee:  -> steve.dower
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38492>
_______________________________________

From report at bugs.python.org  Wed Oct 16 12:57:28 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 16 Oct 2019 16:57:28 +0000
Subject: [issue38492] Microsoft Store app IDLE (Python 3.8) needs msvcp140.dll
In-Reply-To: <1571191392.22.0.935623826778.issue38492@roundup.psfhosted.org>
Message-ID: <1571245048.79.0.156317677116.issue38492@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords: +patch
pull_requests: +16374
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16824

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38492>
_______________________________________

From report at bugs.python.org  Wed Oct 16 13:11:11 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 16 Oct 2019 17:11:11 +0000
Subject: [issue38499] Add rmtree() to pathlib.Path
In-Reply-To: <1571234157.02.0.903860423187.issue38499@roundup.psfhosted.org>
Message-ID: <1571245871.13.0.220297609638.issue38499@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

There is shutil.rmtree that accepts path objects and is more high level. From the previous discussions with respect to expanding API it's recommended to change the functions already present to accept path objects which shutil.rmtree already does and not to expand pathlib API.

Some related discussions : 

* https://mail.python.org/pipermail/python-ideas/2015-June/034236.html
* https://mail.python.org/pipermail/python-dev/2016-April/143866.html

----------
nosy: +pitrou, serhiy.storchaka, xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38499>
_______________________________________

From report at bugs.python.org  Wed Oct 16 13:21:18 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 16 Oct 2019 17:21:18 +0000
Subject: [issue38499] Add rmtree() to pathlib.Path
In-Reply-To: <1571234157.02.0.903860423187.issue38499@roundup.psfhosted.org>
Message-ID: <1571246478.0.0.438162833499.issue38499@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Concur with Karthikeyan.

pathlib.Path provides an object oriented interface to file path operations and to low-level filesystem operations. rmtree() is a high-level and complex operation. Instead of adding more and more complex operations to the Path class we added support of Path (and more generally, path-like objects) in many other functions.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> pathlib.Path wants an rmtree method

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38499>
_______________________________________

From report at bugs.python.org  Wed Oct 16 13:27:23 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 16 Oct 2019 17:27:23 +0000
Subject: [issue38492] Microsoft Store app IDLE (Python 3.8) needs msvcp140.dll
In-Reply-To: <1571191392.22.0.935623826778.issue38492@roundup.psfhosted.org>
Message-ID: <1571246843.38.0.33946308636.issue38492@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 7aebbd1182bc818324656b2fb764679faf51fdff by Steve Dower in branch 'master':
bpo-38492: Remove pythonw.exe dependency on the Microsoft C++ runtime (GH-16824)
https://github.com/python/cpython/commit/7aebbd1182bc818324656b2fb764679faf51fdff


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38492>
_______________________________________

From report at bugs.python.org  Wed Oct 16 13:27:32 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 16 Oct 2019 17:27:32 +0000
Subject: [issue38492] Microsoft Store app IDLE (Python 3.8) needs msvcp140.dll
In-Reply-To: <1571191392.22.0.935623826778.issue38492@roundup.psfhosted.org>
Message-ID: <1571246852.65.0.470644412715.issue38492@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16375
pull_request: https://github.com/python/cpython/pull/16825

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38492>
_______________________________________

From report at bugs.python.org  Wed Oct 16 13:28:39 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 16 Oct 2019 17:28:39 +0000
Subject: [issue38194] Consistently add exist_ok / missing_ok parameters to
 directory creation/deletion functions
In-Reply-To: <1568673909.26.0.25333771691.issue38194@roundup.psfhosted.org>
Message-ID: <1571246919.52.0.977895239756.issue38194@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38194>
_______________________________________

From report at bugs.python.org  Wed Oct 16 13:46:38 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 16 Oct 2019 17:46:38 +0000
Subject: [issue38492] Microsoft Store app IDLE (Python 3.8) needs msvcp140.dll
In-Reply-To: <1571191392.22.0.935623826778.issue38492@roundup.psfhosted.org>
Message-ID: <1571247998.46.0.092213444454.issue38492@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 7773d391f8261a97af502ecfa74a2a588ee05f36 by Miss Islington (bot) in branch '3.8':
bpo-38492: Remove pythonw.exe dependency on the Microsoft C++ runtime (GH-16824)
https://github.com/python/cpython/commit/7773d391f8261a97af502ecfa74a2a588ee05f36


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38492>
_______________________________________

From report at bugs.python.org  Wed Oct 16 13:59:02 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 16 Oct 2019 17:59:02 +0000
Subject: [issue38492] Microsoft Store app IDLE (Python 3.8) needs msvcp140.dll
In-Reply-To: <1571191392.22.0.935623826778.issue38492@roundup.psfhosted.org>
Message-ID: <1571248742.45.0.397752723018.issue38492@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38492>
_______________________________________

From report at bugs.python.org  Wed Oct 16 14:13:23 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 16 Oct 2019 18:13:23 +0000
Subject: [issue38194] Consistently add exist_ok / missing_ok parameters to
 directory creation/deletion functions
In-Reply-To: <1568673909.26.0.25333771691.issue38194@roundup.psfhosted.org>
Message-ID: <1571249603.5.0.228636180913.issue38194@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

os.mkdir() and os.rmdir() are wrappers around corresponding system calls. I do not think they should have additional parameters, especially for functionality which can be easily achieved by wrapping the call with the try/except block.

For shutil.rmtree() see issue29699.

I do not know a good use case for os.removedirs(). Seems it was added for symmetry to os.makedirs(), but it looks dangerous, because it can remove more than was created by os.makedirs(). shutil.rmtree() looks safer and more useful.

Path.rmdir() I left to the maintainers of the pathlib module.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38194>
_______________________________________

From report at bugs.python.org  Wed Oct 16 14:14:21 2019
From: report at bugs.python.org (Daniel Baskal)
Date: Wed, 16 Oct 2019 18:14:21 +0000
Subject: [issue38466] [Easy doc] threading.excepthook doc talks about "object"
In-Reply-To: <1570981226.47.0.762418362865.issue38466@roundup.psfhosted.org>
Message-ID: <1571249661.51.0.812179525811.issue38466@roundup.psfhosted.org>


Daniel Baskal <daniel.baskal at gmail.com> added the comment:

Hi, as a newcomer I'd like to work on this!

Though, I am uncertain about whether these two hooks (threading.excepthook and sys.unraisablehook) have similar behavior and wouldn't it be misleading to simply change mentions of "object" to "thread" in the docs?

Thanks for the guidance!

----------
nosy: +Daniel Baskal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38466>
_______________________________________

From report at bugs.python.org  Wed Oct 16 14:18:52 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 16 Oct 2019 18:18:52 +0000
Subject: [issue38494] Add assert_not_called_with
In-Reply-To: <1571206970.26.0.707248566898.issue38494@roundup.psfhosted.org>
Message-ID: <1571249932.04.0.884934915614.issue38494@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

assert_called_with only checks against the last call. The docs were have been fixed with issue35946. So after multiple calls the you might get an assertion error in your proposed implementation leading to the conclusion that the call never happened but it's just that the last call doesn't match as explained below. mock calls are recorded in mock_calls attribute so you can do a contains check by constructing the call object to see if the calls are present. For multiple calls you can do a list comprehension and use all().

If it's added it would also mean the addition of assert_not_awaited_with for AsyncMock. Given that there is contains check to do it one line I am not sure it's worthy enough to expand the API. I couldn't find any related proposals in the past. assert_not_called is also a shortcut as added in issue21262. I would wait for others opinion on this.

./python
Python 3.9.0a0 (heads/master:392a13bb93, Oct 16 2019, 22:59:54) 
[GCC 4.8.4] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from unittest.mock import Mock, call
>>> m = Mock()
>>> m(1)
<Mock name='mock()' id='140089503302176'>
>>> m(2)
<Mock name='mock()' id='140089503302176'>
>>> m.assert_called_with(1) # Raises AssertionError but the call was actually made.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/xtreak/stuff/python/cpython/Lib/unittest/mock.py", line 902, in assert_called_with
    raise AssertionError(_error_message()) from cause
AssertionError: expected call not found.
Expected: mock(1)
Actual: mock(2)
>>> call(3) not in m.mock_calls # Use contains check instead of iterating through call_args_list
True
>>> call(1) not in m.mock_calls
False

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38494>
_______________________________________

From report at bugs.python.org  Wed Oct 16 14:28:17 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 16 Oct 2019 18:28:17 +0000
Subject: [issue38497] Wrong argument name in documentation for
 pipes.Template.open
In-Reply-To: <1571213625.11.0.339305647326.issue38497@roundup.psfhosted.org>
Message-ID: <1571250497.2.0.20672750305.issue38497@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Semantically mode makes sense to me though rw is correct and Template.open docstring has rw. There are docs like unittest where the keyword arguments are slightly different from the actual keyword arguments in the assert helpers. I guess it's slightly unfortunate that Template.open got rw as keyword argument while open uses mode as keyword argument.

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38497>
_______________________________________

From report at bugs.python.org  Wed Oct 16 14:31:14 2019
From: report at bugs.python.org (Eric Larson)
Date: Wed, 16 Oct 2019 18:31:14 +0000
Subject: [issue38501] multiprocessing.Pool hangs atexit (and garbage
 collection sometimes)
Message-ID: <1571250674.69.0.928369483471.issue38501@roundup.psfhosted.org>


New submission from Eric Larson <larson.eric.d at gmail.com>:

The following code hangs on Python 3.8.0.rc0 on Ubuntu 19.10 when exiting the interpreter:


from multiprocessing import Pool

class A(object):
    def __init__(self):
        self.pool = Pool(processes=2)

solver = A()


When you eventually do ctrl-C, the traceback is:


^CProcess ForkPoolWorker-2:
Error in atexit._run_exitfuncs:
Process ForkPoolWorker-1:
Traceback (most recent call last):
  File "/usr/lib/python3.8/multiprocessing/util.py", line 277, in _run_finalizers
    finalizer()
  File "/usr/lib/python3.8/multiprocessing/util.py", line 201, in __call__
    res = self._callback(*self._args, **self._kwargs)
  File "/usr/lib/python3.8/multiprocessing/pool.py", line 689, in _terminate_pool
    cls._help_stuff_finish(inqueue, task_handler, len(pool))
  File "/usr/lib/python3.8/multiprocessing/pool.py", line 674, in _help_stuff_finish
    inqueue._rlock.acquire()
KeyboardInterrupt
Traceback (most recent call last):
  File "/usr/lib/python3.8/multiprocessing/process.py", line 313, in _bootstrap
    self.run()
  File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3.8/multiprocessing/pool.py", line 114, in worker
    task = get()
  File "/usr/lib/python3.8/multiprocessing/queues.py", line 355, in get
    with self._rlock:
  File "/usr/lib/python3.8/multiprocessing/synchronize.py", line 95, in __enter__
    return self._semlock.__enter__()
KeyboardInterrupt
Traceback (most recent call last):
  File "/usr/lib/python3.8/multiprocessing/process.py", line 313, in _bootstrap
    self.run()
  File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3.8/multiprocessing/pool.py", line 114, in worker
    task = get()
  File "/usr/lib/python3.8/multiprocessing/queues.py", line 356, in get
    res = self._reader.recv_bytes()
  File "/usr/lib/python3.8/multiprocessing/connection.py", line 216, in recv_bytes
    buf = self._recv_bytes(maxlength)
  File "/usr/lib/python3.8/multiprocessing/connection.py", line 414, in _recv_bytes
    buf = self._recv(4)
  File "/usr/lib/python3.8/multiprocessing/connection.py", line 379, in _recv
    chunk = read(handle, remaining)
KeyboardInterrupt


A similar problem seems to occur when garbage collecting when it's part of a class, and that class has not yet called `self.pool.terminate()` and `self.pool.close()`. Hopefully fixing the `atexit` behavior will similarly fix the `gc.collect()` behavior.

Cross-ref is in SciPy, https://github.com/scipy/scipy/issues/10927. It appears to also cause hangs on Travis 3.8-dev builds: https://travis-ci.org/scipy/scipy/jobs/598786785

----------
components: Library (Lib)
messages: 354813
nosy: Eric Larson
priority: normal
severity: normal
status: open
title: multiprocessing.Pool hangs atexit (and garbage collection sometimes)
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38501>
_______________________________________

From report at bugs.python.org  Wed Oct 16 14:33:59 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 16 Oct 2019 18:33:59 +0000
Subject: [issue38494] Add assert_not_called_with
In-Reply-To: <1571206970.26.0.707248566898.issue38494@roundup.psfhosted.org>
Message-ID: <1571250839.94.0.576241433386.issue38494@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Do you know why there is assertRaises(), but there is no assertNotRaises()?

Because assertNotRaises(Exception, callable, *args, **kwargs) would be equivalent to just callable(*args, **kwargs). Call the function, and if is raised an exception, the test will fail.

Similarly, there is no need of assert_not_called_with(). Just define a function which raises an exception when it is called with the specified arguments.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38494>
_______________________________________

From report at bugs.python.org  Wed Oct 16 16:16:21 2019
From: report at bugs.python.org (Caris Moses)
Date: Wed, 16 Oct 2019 20:16:21 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1571256981.74.0.751006853116.issue21478@roundup.psfhosted.org>


Caris Moses <caris.moses at gmail.com> added the comment:

I believe I have found another bug related to this issue. I can start a new issue if necessary. When I use some_mock.attach_mock(...) and make calls, the resulting some_mock.call_args is None while the some_mock.mock_calls list is not empty.

The code below shows this in Python 3.7.5:

from unittest import TestCase
from unittest.mock import patch, Mock

def foo(value):
    return value

class MyObjectTest(TestCase):

    @patch(f'{__name__}.foo')
    def test_do_something(self, mock_foo):
        manager = Mock()
        manager.attach_mock(mock_foo, 'foo_func')
        foo(3)
        print(manager.mock_calls)
        print(manager.call_args)

if __name__ == "__main__":
    unittest.main()

The print statements return:
[call.foo_func(3)]
None

While the code below (without attach_mock) works fine:
from unittest import TestCase
from unittest.mock import patch, Mock

def foo(value):
    return value

class MyObjectTest(TestCase):

    @patch(f'{__name__}.foo')
    def test_do_something(self, mock_foo):
        foo(3)
        print(mock_foo.mock_calls)
        print(mock_foo.call_args)

if __name__ == "__main__":
    unittest.main()

Print statements correctly return:
[call(3)]
call(3)

for completeness the call_args_list also returns [] when using attach_mock. I also tested in Python 3.8.0 and got the same result.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Wed Oct 16 16:26:13 2019
From: report at bugs.python.org (Zachary McCord)
Date: Wed, 16 Oct 2019 20:26:13 +0000
Subject: [issue35297] untokenize documentation is not correct
In-Reply-To: <1542921902.22.0.788709270274.issue35297@psf.upfronthosting.co.za>
Message-ID: <1571257573.8.0.502517277902.issue35297@roundup.psfhosted.org>


Zachary McCord <zack112358 at gmail.com> added the comment:

I think anyone using the tokenize module to programmatically edit python source wants to use and probably does use the undocumented behavior, which should then be documented.

I ran into this issue because for me this manifested as a crash:

$ python3
>>> import tokenize
>>> tokenize.untokenize([(tokenize.STRING, "''", (1, 0), (1, 0), None)])
"''"
>>> tokenize.untokenize([(tokenize.STRING, "''", None, None, None)])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/<snip>/virtualenv/lib/python3.6/tokenize.py", line 338, in untokenize
    out = ut.untokenize(iterable)
  File "/<snip>/virtualenv/lib/python3.6/tokenize.py", line 272, in untokenize
    self.add_whitespace(start)
  File "/<snip>/virtualenv/lib/python3.6/tokenize.py", line 231, in add_whitespace
    row, col = start
TypeError: 'NoneType' object is not iterable

The second call is giving untokenize() input that is documented to be valid, yet which causes a crash.

----------
nosy: +Zachary McCord

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35297>
_______________________________________

From report at bugs.python.org  Wed Oct 16 17:15:07 2019
From: report at bugs.python.org (Romuald Brunet)
Date: Wed, 16 Oct 2019 21:15:07 +0000
Subject: [issue17393] stdlib import mistaken for local by import_fixer
In-Reply-To: <1362946974.63.0.419293411414.issue17393@psf.upfronthosting.co.za>
Message-ID: <1571260507.17.0.931075444593.issue17393@roundup.psfhosted.org>


Change by Romuald Brunet <romuald.brunet at gmail.com>:


----------
keywords: +patch
pull_requests: +16376
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16826

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17393>
_______________________________________

From report at bugs.python.org  Wed Oct 16 18:00:51 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 22:00:51 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1571263251.13.0.261459868016.issue37531@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16377
pull_request: https://github.com/python/cpython/pull/16827

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Wed Oct 16 18:29:18 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 22:29:18 +0000
Subject: [issue37531] Fix regrtest timeout for subprocesses: regrtest -jN
 --timeout=SECONDS
In-Reply-To: <1562700862.92.0.104600612678.issue37531@roundup.psfhosted.org>
Message-ID: <1571264958.83.0.0524734247718.issue37531@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset a661392f8fb5ac4fc095aa1845d1eb7a25c4e9be by Victor Stinner in branch 'master':
bpo-37531: regrtest now catchs ProcessLookupError (GH-16827)
https://github.com/python/cpython/commit/a661392f8fb5ac4fc095aa1845d1eb7a25c4e9be


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37531>
_______________________________________

From report at bugs.python.org  Wed Oct 16 18:46:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 22:46:46 +0000
Subject: [issue38502] regrtest: use process groups
Message-ID: <1571266006.89.0.625453271604.issue38502@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

Problem.

When regrtest is interrupted by CTRL+c and regrtest multiprocessing code (-jN command line option) is used, regrtest randomly fails to stop come TestWorkerProcess threads.

The problem is that only the direct child process is kill by SIGKILL. If the test spawns a grandchild process, this one will not be killed.

Moreover, the grandchild process inherits the child process stdout and stderr. But regrtest mltiprocessing uses pipes for the child process stdout and stderr.

At the end, Popen.communicate() hangs randomly in the main regrtest process (in a TestWorkerProcess thread) until the child process *and* the grandchild process completes. Except that the main regrtest does not directly kill the grandchild process.

=> see bpo-38207


Solution.

I propose to:

(1) use Popen() with start_new_session=True: a worker process calls setsid() to create a new process group.
(2) Don't kill worker processes, but kill the process groups of worker processes.

Attached PR implements this solution.

----------
components: Tests
messages: 354818
nosy: vstinner
priority: normal
severity: normal
status: open
title: regrtest: use process groups
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38502>
_______________________________________

From report at bugs.python.org  Wed Oct 16 18:52:23 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 22:52:23 +0000
Subject: [issue38502] regrtest: use process groups
In-Reply-To: <1571266006.89.0.625453271604.issue38502@roundup.psfhosted.org>
Message-ID: <1571266343.59.0.459133195806.issue38502@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Example of the problem: sometimes, interrupting a multiprocessing test hangs. regrtest fails to interrupt a TestWorkerProcess thread.

$ ./python -m test test_multiprocessing_fork -j10 -F --timeout=60 --slowest
0:00:00 load avg: 1.09 Run tests in parallel using 10 child processes
^C
Kill <TestWorkerProcess #1 running test=test_multiprocessing_fork pid=4504 time=2.3 sec>
Kill <TestWorkerProcess #2 running test=test_multiprocessing_fork pid=4503 time=2.3 sec>
Kill <TestWorkerProcess #3 running test=test_multiprocessing_fork pid=4506 time=2.3 sec>
Kill <TestWorkerProcess #4 running test=test_multiprocessing_fork pid=4505 time=2.3 sec>
Kill <TestWorkerProcess #5 running test=test_multiprocessing_fork pid=4510 time=2.3 sec>
Kill <TestWorkerProcess #6 running test=test_multiprocessing_fork pid=4509 time=2.3 sec>
Kill <TestWorkerProcess #7 running test=test_multiprocessing_fork pid=4513 time=2.3 sec>
Kill <TestWorkerProcess #8 running test=test_multiprocessing_fork pid=4514 time=2.3 sec>
Kill <TestWorkerProcess #9 running test=test_multiprocessing_fork pid=4516 time=2.3 sec>
Kill <TestWorkerProcess #10 running test=test_multiprocessing_fork pid=4517 time=2.3 sec>
0:00:03 load avg: 1.88 Waiting for <TestWorkerProcess #1 running test=test_multiprocessing_fork pid=4504 time=3.3 sec> thread for 1.0 sec
0:00:04 load avg: 1.88 Waiting for <TestWorkerProcess #1 running test=test_multiprocessing_fork pid=4504 time=4.3 sec> thread for 2.0 sec
0:00:05 load avg: 1.73 Waiting for <TestWorkerProcess #1 running test=test_multiprocessing_fork pid=4504 time=5.3 sec> thread for 3.0 sec
(...)


With my PR, I cannot reproduce the "Waiting for ..." issue anymore.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38502>
_______________________________________

From report at bugs.python.org  Wed Oct 16 19:04:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 23:04:46 +0000
Subject: [issue38502] regrtest: use process groups
In-Reply-To: <1571266006.89.0.625453271604.issue38502@roundup.psfhosted.org>
Message-ID: <1571267086.12.0.398484036512.issue38502@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16378
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16829

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38502>
_______________________________________

From report at bugs.python.org  Wed Oct 16 19:06:04 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 23:06:04 +0000
Subject: [issue38207] subprocess: Popen.kill() + Popen.communicate() is
 blocking until all processes using the pipe close the pipe
In-Reply-To: <1568763048.2.0.765446302919.issue38207@roundup.psfhosted.org>
Message-ID: <1571267164.09.0.18358966386.issue38207@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: subprocess: On Windows, Popen.kill() + Popen.communicate() is blocking until all processes using the pipe close the pipe -> subprocess: Popen.kill() + Popen.communicate() is blocking until all processes using the pipe close the pipe

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38207>
_______________________________________

From report at bugs.python.org  Wed Oct 16 19:06:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 23:06:20 +0000
Subject: [issue38207] subprocess: Popen.kill() + Popen.communicate() is
 blocking until all processes using the pipe close the pipe
In-Reply-To: <1568763048.2.0.765446302919.issue38207@roundup.psfhosted.org>
Message-ID: <1571267180.04.0.544141109834.issue38207@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

See also bpo-31447: "proc communicate not exiting on python subprocess timeout using PIPES".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38207>
_______________________________________

From report at bugs.python.org  Wed Oct 16 19:08:15 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 23:08:15 +0000
Subject: [issue38502] regrtest: use process groups
In-Reply-To: <1571266006.89.0.625453271604.issue38502@roundup.psfhosted.org>
Message-ID: <1571267295.41.0.104574157913.issue38502@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

See also bpo-18969: "test suite: enable faulthandler timeout in assert_python". This issue proposes to use killpg() to send a signal to all Python processes spawned by regrtest: trigger faulthandler to dump the Python traceback of all Python threads.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38502>
_______________________________________

From report at bugs.python.org  Wed Oct 16 19:10:25 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 23:10:25 +0000
Subject: [issue38502] regrtest: use process groups
In-Reply-To: <1571266006.89.0.625453271604.issue38502@roundup.psfhosted.org>
Message-ID: <1571267425.38.0.855043397978.issue38502@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

See also bpo-12413 "make faulthandler dump traceback of child processes" which looks like a duplicate of bpo-18969.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38502>
_______________________________________

From report at bugs.python.org  Wed Oct 16 19:11:05 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 23:11:05 +0000
Subject: [issue24302] Dead Code of Handler check in function
 faulthandler_fatal_error()
In-Reply-To: <1432744245.29.0.369253683429.issue24302@psf.upfronthosting.co.za>
Message-ID: <1571267465.87.0.994647647882.issue24302@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24302>
_______________________________________

From report at bugs.python.org  Wed Oct 16 19:43:43 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 16 Oct 2019 23:43:43 +0000
Subject: [issue38207] subprocess: Popen.kill() + Popen.communicate() is
 blocking until all processes using the pipe close the pipe
In-Reply-To: <1568763048.2.0.765446302919.issue38207@roundup.psfhosted.org>
Message-ID: <1571269423.53.0.781670380824.issue38207@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

On Windows, the threads reading pipes continue to run even after the direct child process exited.

Problem: at Python exit (main process), Python hangs on calling threading._shutdown() which waits until all Python threads complete.

One enhancement would be to spawn subprocess.Popen.communicate() internal threads as daemon threads. So threading._shutdown() would not wait for them at Python exit.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38207>
_______________________________________

From report at bugs.python.org  Wed Oct 16 20:22:10 2019
From: report at bugs.python.org (Ryan May)
Date: Thu, 17 Oct 2019 00:22:10 +0000
Subject: [issue33725] Python crashes on macOS after fork with no exec
In-Reply-To: <1527814386.62.0.682650639539.issue33725@psf.upfronthosting.co.za>
Message-ID: <1571271730.22.0.419929656541.issue33725@roundup.psfhosted.org>


Change by Ryan May <rmay31 at gmail.com>:


----------
nosy: +Ryan May

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33725>
_______________________________________

From report at bugs.python.org  Wed Oct 16 21:16:41 2019
From: report at bugs.python.org (Paul Silisteanu)
Date: Thu, 17 Oct 2019 01:16:41 +0000
Subject: [issue38501] multiprocessing.Pool hangs atexit (and garbage
 collection sometimes)
In-Reply-To: <1571250674.69.0.928369483471.issue38501@roundup.psfhosted.org>
Message-ID: <1571275001.53.0.702028064675.issue38501@roundup.psfhosted.org>


Paul Silisteanu <paul.silisteanu at gmail.com> added the comment:

Same issue on Window 10 and macOS Catalina with Python 3.8.0.
Here is the error I get on Windows 10:

C:\Users\x>py -3.8
Python 3.8.0 (tags/v3.8.0:fa919fd, Oct 14 2019, 19:37:50) [MSC v.1916 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> from multiprocessing import get_context
>>>
>>> class A(object):
...     def __init__(self):
...         self.pool = get_context(None).Pool(2)
...
>>> solver=A()
>>> quit()
Process SpawnPoolWorker-2:
Error in atexit._run_exitfuncs:
Process SpawnPoolWorker-1:
Traceback (most recent call last):
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\process.py", line 313, in _bootstrap
    self.run()
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\pool.py", line 114, in worker
    task = get()
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\queues.py", line 355, in get
    with self._rlock:
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\synchronize.py", line 95, in __enter__
    return self._semlock.__enter__()
Traceback (most recent call last):
KeyboardInterrupt
Traceback (most recent call last):
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\util.py", line 277, in _run_finalizers
    finalizer()
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\util.py", line 201, in __call__
    res = self._callback(*self._args, **self._kwargs)
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\pool.py", line 689, in _terminate_pool
    cls._help_stuff_finish(inqueue, task_handler, len(pool))
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\pool.py", line 674, in _help_stuff_finish
    inqueue._rlock.acquire()
KeyboardInterrupt
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\process.py", line 313, in _bootstrap
    self.run()
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\pool.py", line 114, in worker
    task = get()
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\queues.py", line 356, in get
    res = self._reader.recv_bytes()
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\connection.py", line 216, in recv_bytes
    buf = self._recv_bytes(maxlength)
  File "C:\Users\x\AppData\Local\Programs\Python\Python38\lib\multiprocessing\connection.py", line 305, in _recv_bytes
    waitres = _winapi.WaitForMultipleObjects(
KeyboardInterrupt

C:\Users\x>

----------
nosy: +Paul Silisteanu

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38501>
_______________________________________

From report at bugs.python.org  Wed Oct 16 21:46:40 2019
From: report at bugs.python.org (Daniel Kahn Gillmor)
Date: Thu, 17 Oct 2019 01:46:40 +0000
Subject: [issue17123] Add OCSP support to ssl module
In-Reply-To: <1570671522.21.0.151508418003.issue17123@roundup.psfhosted.org>
Message-ID: <87ftjt6j4u.fsf@fifthhorseman.net>


Daniel Kahn Gillmor <dkg at fifthhorseman.net> added the comment:

On Thu 2019-10-10 01:38:42 +0000, Benjamin Peterson wrote:

> Considering OSCP has fallen out of favor relative to CT in recent
> years, may be should simply reject this feature request.

CT provides the possibility of a website operator to *detect* CA
malfeasance.

OCSP provides a live "proof of freshness" of the certificate at a
cadence significantly shorter than the lifetime of most certificates
(even the 90-day certificates offered by ACME-driven CAs like Let's
Encrypt).

These are orthogonal, and mutually-reinforcing mechanisms, not competing
mechanisms.

      --dkg

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17123>
_______________________________________

From report at bugs.python.org  Wed Oct 16 21:49:54 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 17 Oct 2019 01:49:54 +0000
Subject: [issue38493] os.CLD_KILLED should be implemented
In-Reply-To: <1571200572.77.0.0960305175101.issue38493@roundup.psfhosted.org>
Message-ID: <1571276994.51.0.967038196243.issue38493@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> What about CLD_STOPPED?

I think that it should be added also.
I 've added the CLD_STOPPED on PR 16821.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38493>
_______________________________________

From report at bugs.python.org  Wed Oct 16 22:09:03 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 17 Oct 2019 02:09:03 +0000
Subject: [issue21478] mock calls don't propagate to parent (autospec)
In-Reply-To: <1399899394.81.0.714942512868.issue21478@psf.upfronthosting.co.za>
Message-ID: <1571278143.41.0.47055577317.issue21478@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Please open a new issue. It's getting little hard to track on this since it was closed and has 2 PRs merged.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21478>
_______________________________________

From report at bugs.python.org  Wed Oct 16 22:29:26 2019
From: report at bugs.python.org (Louis Huemiller)
Date: Thu, 17 Oct 2019 02:29:26 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
In-Reply-To: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>
Message-ID: <1571279366.93.0.156026205003.issue38477@roundup.psfhosted.org>


Louis Huemiller <lhuemill at gmail.com> added the comment:

Thank you for looking into the potential issue. Instead of getting Python3.8 from ppa:deadsnakes/ppa, I downloaded the source from:

  https://www.python.org/ftp/python/3.8.0/Python-3.8.0rc1.tgz

Then did the following to build and install it:

  $ cd /usr/src
  $ sudo tar xzf ~/Python-3.8.0rc1.tgz
  $ cd Python-3.8.0rc1/
  $ sudo ./configure --enable-optimizations
  $ sudo apt-get install zlib1g-dev
  $ sudo -H make altinstall

Then re-running the magiccube2x2 permutations with a max_depth of 6 I obtained:

  $ python3.7 permutations2x2 --max_depth 6 | egrep "^# Total_Time"
  # Total_Time: 61.90

  $ python3.8 permutations2x2 --max_depth 6 | egrep "^# Total_Time"
  # Total_Time: 82.45

Unfortunately, this still shows the Python3.8 execution as significantly slower, in this case 33.2% slower. Not sure of the cause, but perhaps I wasn't completely successful at removing the prior installation from ppa:deadsnakes/ppa. I removed it through the use of:

  $ sudo apt remove python3.8
  $ sudo add-apt-repository -r ppa:deadsnakes/ppa
  $ shutdown -r now

Next step I will completly re-install this server and then only install Python3.8 from https://www.python.org/ftp/python/3.8.0/Python-3.8.0rc1.tgz.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Thu Oct 17 00:56:41 2019
From: report at bugs.python.org (Ned Deily)
Date: Thu, 17 Oct 2019 04:56:41 +0000
Subject: [issue34864] In Idle, Mac tabs make editor status line disappear.
In-Reply-To: <1538422572.97.0.545547206417.issue34864@psf.upfronthosting.co.za>
Message-ID: <1571288201.48.0.212118550343.issue34864@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

FTR, Raymond reports in a tweet (https://twitter.com/raymondh/status/1184667350953447424) that it is possible to get logged out if you ignore the warning and try to open a file in IDLE when the System Preference is set to always open documents in tabs.  I was able to reproduce with macOS 10.14.6 on real hardware (I didn't see elsewhere).  This is clearly a Tk issue and there has been a lot of work going on in Tk in this area since Tk 8.6.8.  We have been waiting for an official 8.6.10 release to again try to update the python.org built-in Tcl/Tk after the very unsatisfactory experience with 8.6.9; until then still best to heed the warning!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34864>
_______________________________________

From report at bugs.python.org  Thu Oct 17 00:58:11 2019
From: report at bugs.python.org (Ned Deily)
Date: Thu, 17 Oct 2019 04:58:11 +0000
Subject: [issue34864] In Idle, Mac tabs make editor status line disappear.
In-Reply-To: <1538422572.97.0.545547206417.issue34864@psf.upfronthosting.co.za>
Message-ID: <1571288291.22.0.301628442099.issue34864@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Should be: "I did't *try* elsewhere.", not "see elsewhere".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34864>
_______________________________________

From report at bugs.python.org  Thu Oct 17 01:52:07 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Thu, 17 Oct 2019 05:52:07 +0000
Subject: [issue38436] Improved performance for list addition.
In-Reply-To: <1570734964.11.0.75032337331.issue38436@roundup.psfhosted.org>
Message-ID: <1571291527.35.0.729299343949.issue38436@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

I'm going to go ahead and close this, since the payoff doesn't seem to be worth the effort.

Thanks for the benchmarking and feedback!

----------
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38436>
_______________________________________

From report at bugs.python.org  Thu Oct 17 02:33:30 2019
From: report at bugs.python.org (Louis Huemiller)
Date: Thu, 17 Oct 2019 06:33:30 +0000
Subject: [issue38477] magiccube2x2 permutations 28% slower with Python
 3.8.0rc1 vs 3.7
In-Reply-To: <1571103770.08.0.648523147203.issue38477@roundup.psfhosted.org>
Message-ID: <1571294010.69.0.949299591078.issue38477@roundup.psfhosted.org>


Louis Huemiller <lhuemill at gmail.com> added the comment:

Reinstalled the server I'd been using for this issue, with Ubuntu 18.04.3 LTS Server amd64. This installation already came with Python3.6.8.  Downloaded and installed Python3.7.3 and 3.8.0 from:

  https://www.python.org/ftp/python/3.7.3/Python-3.7.3.tgz
  https://www.python.org/ftp/python/3.8.0/Python-3.8.0.tgz

The installation process was somewhat complicated, with several to be discovered prerequisites.  Used "apt install" to install the following needed dependencies:

  build-essential checkinstall libreadline-gplv2-dev libncursesw5-dev libssl-dev libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev zlib1g-dev libffi-dev

Then was able to do the following to build and install the downloaded Python3.7.3 and 3.8.0:

  $ sudo ./configure --enable-optimizations
  $ sudo -H make altinstall

Then downloaded a clone of my magiccube2x2 repository and obtained the following results:

  $ python3.6 ./permutations2x2 --max_depth 6 | egrep "^# Total_Time:"
  # Total_Time: 69.02
  $ python3.7 ./permutations2x2 --max_depth 6 | egrep "^# Total_Time:"
  # Total_Time: 84.52
  $ python3.8 ./permutations2x2 --max_depth 6 | egrep "^# Total_Time:"
  # Total_Time: 83.14

In this case the runtimes under both of the Python versions that I downloaded the source for and built are significantly slower than the run with python3.6, which came already as part of Ubuntu 18.04.3.

Instead of using the version of python3.7.3 that I built, was able to do:

  $ sudo apt install python3.7

to get one that had already been built for Ubuntu.  Doing this allowed the following result:

  $ /usr/bin/python3.7 ./permutations2x2 --max_depth 6 \
    | egrep "^# Total_Time:"
  # Total_Time: 62.39

Which is better than even the Python3.6 result.  Unfortunately, there is not currently a pre-built Ubuntu package for Python3.8 and the one from ppa:deadsnakes/ppa, I already know has the performance issue.

I did some searching on wiki.python.org and I was unable to find any instructions for how to build python from the source.  Perhaps the instructions are already there but I was unable to find them.

Perhaps this issue should be re-opened as a documentation error. I could really use instructions on how to built a performance version of Python and I suspect several others could also use this. For example, I'd like to pass that information to the maintainers of the deadsnakes repository.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38477>
_______________________________________

From report at bugs.python.org  Thu Oct 17 03:12:47 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 17 Oct 2019 07:12:47 +0000
Subject: [issue37587] JSON loads performance improvement for long strings
In-Reply-To: <1563028922.54.0.821649437171.issue37587@roundup.psfhosted.org>
Message-ID: <1571296367.6.0.335554717738.issue37587@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:


New changeset 9c11029bb41caab5576f354fbf808a5e91325bb0 by Inada Naoki in branch 'master':
bpo-37587: json: Use _PyUnicodeWriter when scanning string. (GH-15591)
https://github.com/python/cpython/commit/9c11029bb41caab5576f354fbf808a5e91325bb0


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37587>
_______________________________________

From report at bugs.python.org  Thu Oct 17 04:22:02 2019
From: report at bugs.python.org (wang xuancong)
Date: Thu, 17 Oct 2019 08:22:02 +0000
Subject: [issue38503] bug: string search can find \n, but can NEVER find \r
Message-ID: <1571300522.6.0.320185035424.issue38503@roundup.psfhosted.org>


New submission from wang xuancong <xuancong84 at gmail.com>:

If I load a file which contains "\r" and "\n", I can find "\n", but not "\r". This behaviour is inconsistent in Python 3, but consistent in Python 2.

>>> open('./3cjkxdnw/accessibilityLog/1570181896323.csv', 'rb').read().count(b'\r')
88
>>> open('./3cjkxdnw/accessibilityLog/1570181896323.csv').read().count('\r')
0
>>> type(open('./3cjkxdnw/accessibilityLog/1570181896323.csv').read())
<class 'str'>
>>> type('\r')
<class 'str'>

Thanks!

----------
messages: 354834
nosy: xuancong84
priority: normal
severity: normal
status: open
title: bug: string search can find \n, but can NEVER find \r
type: behavior
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38503>
_______________________________________

From report at bugs.python.org  Thu Oct 17 04:29:47 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 17 Oct 2019 08:29:47 +0000
Subject: [issue38503] bug: string search can find \n, but can NEVER find \r
In-Reply-To: <1571300522.6.0.320185035424.issue38503@roundup.psfhosted.org>
Message-ID: <1571300987.46.0.907225434421.issue38503@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

It is "universal newline".
See
https://docs.python.org/3/library/functions.html#open
and
https://docs.python.org/3/glossary.html#term-universal-newlines

----------
nosy: +inada.naoki
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38503>
_______________________________________

From report at bugs.python.org  Thu Oct 17 04:30:11 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 17 Oct 2019 08:30:11 +0000
Subject: [issue37587] JSON loads performance improvement for long strings
In-Reply-To: <1563028922.54.0.821649437171.issue37587@roundup.psfhosted.org>
Message-ID: <1571301011.45.0.266974032149.issue37587@roundup.psfhosted.org>


Change by Inada Naoki <songofacandy at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37587>
_______________________________________

From report at bugs.python.org  Thu Oct 17 04:59:44 2019
From: report at bugs.python.org (=?utf-8?q?Walter_D=C3=B6rwald?=)
Date: Thu, 17 Oct 2019 08:59:44 +0000
Subject: [issue38482] BUG in codecs.BufferedIncrementalDecoder
In-Reply-To: <1571127690.05.0.477916235895.issue38482@roundup.psfhosted.org>
Message-ID: <1571302784.26.0.117885582017.issue38482@roundup.psfhosted.org>


Walter D?rwald <walter at livinglogic.de> added the comment:

codecs.iterencode()/iterdecode() are just shallow 10-line wrappers around incremental codecs (which are used as the basis of io streams).

Note that the doc string for iterencode() contains:

   Encodes the input strings from the iterator using an IncrementalEncoder.

i.e. "strings" (plural) should give a hint that iterator is an iterator over strings.

But maybe this could be made clearer.

And https://docs.python.org/3/library/codecs.html#codecs.iterencode and https://docs.python.org/3/library/codecs.html#codecs.iterdecode could indead be clearer about what iterator should be. An example might also help.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38482>
_______________________________________

From report at bugs.python.org  Thu Oct 17 05:34:18 2019
From: report at bugs.python.org (=?utf-8?b?5YiY5a625Lic?=)
Date: Thu, 17 Oct 2019 09:34:18 +0000
Subject: [issue38504] Reduce the size of deb package
Message-ID: <1571304858.59.0.51110588392.issue38504@roundup.psfhosted.org>


New submission from ??? <hearing1996 at gmail.com>:

I am not very good at python, but now I have a need, which is how to compile the source code into a deb package, so that the deb is minimal. The obtained deb package only need to meet the function of installing modules through pip and no extra features are needed.

----------
messages: 354837
nosy: ???
priority: normal
severity: normal
status: open
title: Reduce the size of deb package
type: resource usage
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38504>
_______________________________________

From report at bugs.python.org  Thu Oct 17 06:01:19 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 17 Oct 2019 10:01:19 +0000
Subject: [issue38493] os.CLD_KILLED and os.CLD_STOPPED should be implemented
In-Reply-To: <1571200572.77.0.0960305175101.issue38493@roundup.psfhosted.org>
Message-ID: <1571306479.3.0.0719231963041.issue38493@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
title: os.CLD_KILLED should be implemented -> os.CLD_KILLED and os.CLD_STOPPED should be implemented

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38493>
_______________________________________

From report at bugs.python.org  Thu Oct 17 06:41:41 2019
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 17 Oct 2019 10:41:41 +0000
Subject: [issue34953] Implement `mmap.mmap.__repr__`
In-Reply-To: <1539215332.4.0.788709270274.issue34953@psf.upfronthosting.co.za>
Message-ID: <1571308901.19.0.980418704429.issue34953@roundup.psfhosted.org>


Xiang Zhang <angwerzx at 126.com> added the comment:


New changeset d8ca2354ed30c12b9ce37c4535222b700a727b32 by Xiang Zhang (Taine Zhao) in branch 'master':
bpo-34953: Implement `mmap.mmap.__repr__` (GH-9891)
https://github.com/python/cpython/commit/d8ca2354ed30c12b9ce37c4535222b700a727b32


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34953>
_______________________________________

From report at bugs.python.org  Thu Oct 17 06:42:49 2019
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 17 Oct 2019 10:42:49 +0000
Subject: [issue34953] Implement `mmap.mmap.__repr__`
In-Reply-To: <1539215332.4.0.788709270274.issue34953@psf.upfronthosting.co.za>
Message-ID: <1571308969.78.0.605581814201.issue34953@roundup.psfhosted.org>


Change by Xiang Zhang <angwerzx at 126.com>:


----------
components: +Extension Modules -Interpreter Core
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.9 -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34953>
_______________________________________

From report at bugs.python.org  Thu Oct 17 06:47:58 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 17 Oct 2019 10:47:58 +0000
Subject: [issue38504] Reduce the size of deb package
In-Reply-To: <1571304858.59.0.51110588392.issue38504@roundup.psfhosted.org>
Message-ID: <1571309278.42.0.0615536834957.issue38504@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

I think python-dev or other forums would be of good help than the bug tracker given that it involves optimizing deb package.

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38504>
_______________________________________

From report at bugs.python.org  Thu Oct 17 07:07:56 2019
From: report at bugs.python.org (Mikko Rantalainen)
Date: Thu, 17 Oct 2019 11:07:56 +0000
Subject: [issue24260] TabError behavior doesn't match documentation
In-Reply-To: <1432244751.77.0.187754601995.issue24260@psf.upfronthosting.co.za>
Message-ID: <1571310476.74.0.62569218752.issue24260@roundup.psfhosted.org>


Mikko Rantalainen <mikko.rantalainen at peda.net> added the comment:

As I wrote in duplicate issue38496 (with emphasis added):

I'd prefer python3 to require that *all whitespace* at the start of the all the lines is *tabs for the whole file*, or *spaces for the whole file*. And first indented line sets the preference for the whole file.

That way python3 would really disallow mixing spaces and tabs. And the people who like to use tabs for indent (e.g. me) are happy because they can adjust the amount of indent up to their own taste. I'm in the Allman-8 camp for all languages I use.

----------
nosy: +Mikko Rantalainen

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24260>
_______________________________________

From report at bugs.python.org  Thu Oct  3 04:50:12 2019
From: report at bugs.python.org (Puneet Bawa)
Date: Thu, 03 Oct 2019 08:50:12 +0000
Subject: [issue38358] ASSERTION ERROR WHILE USING TENSORFLOW
Message-ID: <1570092612.13.0.03397983919.issue38358@roundup.psfhosted.org>


New submission from Puneet Bawa <puneet.bawa at chitkara.edu.in>:

-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731a52f28>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07319edeb8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07319edeb8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07319cfe48>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07319cfe48>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073196d7f0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073196d7f0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731d361d0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731d361d0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731d361d0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731d361d0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731d361d0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731d361d0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731a743c8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731a743c8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073196bcf8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073196bcf8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731a4e748>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731a4e748>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731959668>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731959668>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073191ec50>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073191ec50>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07319023c8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07319023c8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07318b9400>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07318b9400>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731871a90>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731871a90>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073191d9e8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073191d9e8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073183da90>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073183da90>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731849f98>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731849f98>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07318a6e48>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07318a6e48>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731814470>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731814470>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07318227f0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07318227f0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073183d128>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073183d128>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07317db048>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07317db048>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07317cc048>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07317cc048>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731783e10>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731783e10>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073173ee10>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073173ee10>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073174b908>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073174b908>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07317f7208>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07317f7208>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731715e80>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731715e80>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731721c18>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731721c18>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07316ea588>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07316ea588>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073176fb00>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073176fb00>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731642be0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731642be0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07324fe5f8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07324fe5f8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07324fe5f8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07324fe5f8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07324fe5f8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07324fe5f8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07315f9fd0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07315f9fd0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073161c898>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073161c898>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731652080>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731652080>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07315d34a8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07315d34a8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731747a90>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731747a90>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731616080>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731616080>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073159bbe0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073159bbe0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07315ad898>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07315ad898>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073155d048>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073155d048>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731551358>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731551358>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073161c588>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073161c588>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731514240>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731514240>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314e3d68>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314e3d68>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314b8b70>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314b8b70>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314869b0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314869b0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314a12b0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314a12b0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314e9358>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314e9358>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314529b0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314529b0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731462518>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731462518>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07313fd390>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07313fd390>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07313c2d30>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07313c2d30>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07313f8390>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07313f8390>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07313e87f0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07313e87f0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731333b70>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731333b70>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731340630>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731340630>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073130ceb8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073130ceb8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731b4ee80>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731b4ee80>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731b4ee80>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731b4ee80>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731b4ee80>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731b4ee80>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07312c42e8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07312c42e8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314ce400>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07314ce400>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07312e49e8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07312e49e8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07313b3ba8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07313b3ba8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07312359e8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07312359e8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07312af4e0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07312af4e0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07312e4d30>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07312e4d30>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073197ec50>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073197ec50>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731bf9f28>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731bf9f28>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731227908>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731227908>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073127ccc0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073127ccc0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073116dcf8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073116dcf8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731178e10>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731178e10>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07311301d0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07311301d0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073124db38>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073124db38>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731168390>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731168390>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073115b7b8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073115b7b8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731121978>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731121978>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07310ce748>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07310ce748>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731130358>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731130358>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07310d87b8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07310d87b8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073106deb8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073106deb8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731084b38>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731084b38>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731092ba8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731092ba8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731026780>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731026780>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730fd09e8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730fd09e8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:From /home/puneet/kaldi-workspace/gan/Voice_Converter_CycleGAN/module.py:62: conv2d (from tensorflow.python.layers.convolutional) is deprecated and will be removed in a future version.
Instructions for updating:
Use `tf.keras.layers.Conv2D` instead.
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0731d6cef0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0731d6cef0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0731d6cef0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0731d6cef0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0731d6cef0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0731d6cef0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0731da9cf8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0731da9cf8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730fa3e80>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730fa3e80>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730f072b0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730f072b0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730ed8358>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730ed8358>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730f36978>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730f36978>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:From /home/puneet/kaldi-workspace/gan/Voice_Converter_CycleGAN/module.py:211: dense (from tensorflow.python.layers.core) is deprecated and will be removed in a future version.
Instructions for updating:
Use keras.layers.dense instead.
WARNING:tensorflow:Entity <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f0730dfe400>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f0730dfe400>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07313f8400>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07313f8400>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07313f8400>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07313f8400>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07313f8400>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07313f8400>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730efb860>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730efb860>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730d97400>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730d97400>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730e6e400>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730e6e400>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730d4b908>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730d4b908>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730df0668>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730df0668>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f0730e2d470>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f0730e2d470>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b647f0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b647f0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730cede80>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730cede80>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730df09e8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730df09e8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730d4bbe0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730d4bbe0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730cede80>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730cede80>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b510b8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b510b8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b16208>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b16208>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730c67588>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730c67588>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f0730c42978>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f0730c42978>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b64748>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b64748>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730adf5c0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730adf5c0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730adf5c0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730adf5c0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b646a0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b646a0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730d82898>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730d82898>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b110f0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b110f0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b45860>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730b45860>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a6f8d0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a6f8d0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f0730a8e550>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f0730a8e550>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730bb8710>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730bb8710>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730bb8710>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730bb8710>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730bb8710>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730bb8710>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07309fe128>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07309fe128>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07309faef0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07309faef0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a2fb00>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a2fb00>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07309c2fd0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07309c2fd0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a212b0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a212b0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f0730a76ba8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f0730a76ba8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a1d7f0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a1d7f0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a76ba8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a76ba8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a76ba8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a76ba8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a1d128>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730a1d128>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730d82a58>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f0730d82a58>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f073096c080>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f073096c080>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07309362e8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f07309362e8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f073090e358>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv.call of <tensorflow.python.layers.convolutional.Conv2D object at 0x7f073090e358>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f07308f7518>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Dense.call of <tensorflow.python.layers.core.Dense object at 0x7f07308f7518>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:From /home/puneet/kaldi-workspace/gan/Voice_Converter_CycleGAN/model.py:93: The name tf.trainable_variables is deprecated. Please use tf.compat.v1.trainable_variables instead.

WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730893d68>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730893d68>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730893d68>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730893d68>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730893d68>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730893d68>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073093c710>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073093c710>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073083cb70>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073083cb70>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073087cb70>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073087cb70>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730936128>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730936128>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07308aaeb8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07308aaeb8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07308f7860>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07308f7860>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07307ffbe0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07307ffbe0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07307d33c8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07307d33c8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07307b3898>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07307b3898>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073078af28>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073078af28>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07307aa3c8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07307aa3c8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07307a2630>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07307a2630>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306f09b0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306f09b0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306fd1d0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306fd1d0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306f0080>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306f0080>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306b3c18>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306b3c18>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073070f668>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073070f668>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306cd128>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306cd128>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073069c390>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073069c390>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306a5080>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306a5080>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730684978>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730684978>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073065ef28>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073065ef28>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07305f57b8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07305f57b8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07305c04a8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07305c04a8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07305cecf8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07305cecf8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07327527f0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07327527f0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07305386d8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07305386d8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07308932b0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07308932b0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07308932b0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07308932b0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731207128>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0731207128>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730f58eb8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730f58eb8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073056a160>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073056a160>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730627860>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730627860>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306a5320>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07306a5320>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07304f44e0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07304f44e0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730594588>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730594588>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730d65828>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730d65828>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07304a4320>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07304a4320>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073045d1d0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073045d1d0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07304f4e48>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07304f4e48>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073045dac8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073045dac8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730421b00>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730421b00>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07303cd3c8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07303cd3c8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07303b6630>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07303b6630>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07303779b0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07303779b0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07303915f8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07303915f8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07303779b0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07303779b0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073034cc18>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073034cc18>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730331240>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730331240>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730363128>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f0730363128>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07302af390>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07302af390>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07302ba048>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07302ba048>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073028d0b8>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073028d0b8>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07302aafd0>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f07302aafd0>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:Entity <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073023ea90>> could not be transformed and will be executed as-is. Please report this to the AutgoGraph team. When filing the bug, set the verbosity to 10 (on Linux, `export AUTOGRAPH_VERBOSITY=10`) and attach the full output. Cause: converting <bound method Conv1D.call of <tensorflow.python.layers.convolutional.Conv1D object at 0x7f073023ea90>>: AssertionError: Bad argument number for Name: 3, expecting 4
WARNING:tensorflow:From /home/puneet/kaldi-workspace/gan/Voice_Converter_CycleGAN/model.py:107: The name tf.train.AdamOptimizer is deprecated. Please use tf.compat.v1.train.AdamOptimizer instead.

----------
components: Build
messages: 353831
nosy: Puneet Bawa
priority: normal
severity: normal
status: open
title: ASSERTION ERROR WHILE USING TENSORFLOW
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38358>
_______________________________________

From report at bugs.python.org  Thu Oct 17 08:23:55 2019
From: report at bugs.python.org (Caris Moses)
Date: Thu, 17 Oct 2019 12:23:55 +0000
Subject: [issue38505] Mock.call_args and Mock.call_args_list
Message-ID: <1571315034.98.0.296986686038.issue38505@roundup.psfhosted.org>


New submission from Caris Moses <caris.moses at gmail.com>:

When I use some_mock.attach_mock(...) and make calls, the resulting some_mock.call_args is None while the some_mock.mock_calls list is not empty.

The code below shows this in Python 3.7.5:

from unittest import TestCase
from unittest.mock import patch, Mock

def foo(value):
    return value

class MyObjectTest(TestCase):

    @patch(f'{__name__}.foo')
    def test_do_something(self, mock_foo):
        manager = Mock()
        manager.attach_mock(mock_foo, 'foo_func')
        foo(3)
        print(manager.mock_calls)
        print(manager.call_args)
        print(manager.call_args_list)

if __name__ == "__main__":
    unittest.main()

The print statements return:
[call.foo_func(3)]
None
[]

While the code below (without attach_mock) works fine:

from unittest import TestCase
from unittest.mock import patch, Mock

def foo(value):
    return value

class MyObjectTest(TestCase):

    @patch(f'{__name__}.foo')
    def test_do_something(self, mock_foo):
        foo(3)
        print(mock_foo.mock_calls)
        print(mock_foo.call_args)
        print(mock_foo.call_args_list)

if __name__ == "__main__":
    unittest.main()

Print statements correctly return:
[call(3)]
call(3)
[call(3)]

I also tested in Python 3.8.0 and got the same result.

----------
messages: 354841
nosy: Caris Moses
priority: normal
severity: normal
status: open
title: Mock.call_args and Mock.call_args_list

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38505>
_______________________________________

From report at bugs.python.org  Thu Oct 17 08:24:48 2019
From: report at bugs.python.org (Caris Moses)
Date: Thu, 17 Oct 2019 12:24:48 +0000
Subject: [issue38505] Mock.call_args and Mock.call_args_list not propagated to
 parent Mock
In-Reply-To: <1571315034.98.0.296986686038.issue38505@roundup.psfhosted.org>
Message-ID: <1571315088.32.0.78904635668.issue38505@roundup.psfhosted.org>


Change by Caris Moses <caris.moses at gmail.com>:


----------
title: Mock.call_args and Mock.call_args_list -> Mock.call_args and Mock.call_args_list not propagated to parent Mock

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38505>
_______________________________________

From report at bugs.python.org  Thu Oct 17 08:32:28 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 17 Oct 2019 12:32:28 +0000
Subject: [issue38505] Mock.call_args and Mock.call_args_list not propagated to
 parent Mock
In-Reply-To: <1571315034.98.0.296986686038.issue38505@roundup.psfhosted.org>
Message-ID: <1571315548.42.0.105727095902.issue38505@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38505>
_______________________________________

From report at bugs.python.org  Thu Oct 17 10:13:24 2019
From: report at bugs.python.org (=?utf-8?q?Tymek_Wo=C5=82od=C5=BAko?=)
Date: Thu, 17 Oct 2019 14:13:24 +0000
Subject: [issue38490] statistics: add covariance and Pearson's correlation
In-Reply-To: <CAHa5zCupjtid=Q0vhbzwyCWrV5MwowN+cW2tvXC0b=1UaknqLw@mail.gmail.com>
Message-ID: <CAHa5zCuw0G7LvygCRGGOEWqT_9=gwHxYhKqFF7Hni-SJy9=PWw@mail.gmail.com>


Tymek Wo?od?ko <twolodzko at gmail.com> added the comment:

I expanded my PR to add simple linear regression. I also created
documentation for the new functionalities.

As about covariance, we can simply not expose it to the users, but I'm not
convinced that there is any gain in keeping it hidden from the users.

Tim

On Wed, Oct 16, 2019 at 11:25 AM Tymek Wo?od?ko <report at bugs.python.org>
wrote:

>
> Tymek Wo?od?ko <twolodzko at gmail.com> added the comment:
>
> In case there is agreement with Steven, I will add simple linear regression
> ( https://en.wikipedia.org/wiki/Simple_linear_regression ) in the same PR,
> since it is just:
>
> slope = correlation(x, y) * ( stdev(y) / stdev(x) )
> intercept = mean(y) - slope * mean(x)
>
> As about covariance, I see your points, but why not keeping it "because we
> can"? It can be useful for some users and the functionality still needs to
> be implemented to have correlation coefficient.
>
> On Wed, Oct 16, 2019 at 10:47 AM Steven D'Aprano <report at bugs.python.org>
> wrote:
>
> >
> > Steven D'Aprano <steve+python at pearwood.info> added the comment:
> >
> > I can't speak for other countries, but in Australia, secondary school
> > mathematics teaches correlation coefficient and linear regression from
> > Year 11 onwards (typically ages 16 or 17). Covariance is not itself
> > taught, and as far as I can tell neither the TI-83 nor NSpire
> > provides a built-in covariance command.
> >
> > On the other hand, other calculators such as the HP-48GX do.
> >
> > Oddly, Excel provides the population (not sample) covariance:
> >
> >
> >
> https://support.office.com/en-us/article/COVARIANCE-P-function-6F0E1E6D-956D-4E4B-9943-CFEF0BF9EDFC
> >
> > OpenOffice and LibreOffice also provide a covariance function.
> >
> > I think that supporting correlation coefficient `r` and linear
> > regression would be clear wins, from the perspective of secondary school
> > maths. But as far as covariance goes, it would help convince me if you
> > had either:
> >
> > - evidence that covariance is taught in secondary schools, or at
> >   least first year undergraduate statistics;
> >
> > - that it has use-cases beyond "helper for calculating r";
> >
> > - or that there is demand for it from people who want covariance
> >   but can't, or don't want to, use numpy/scipy.
> >
> > ----------
> >
> > _______________________________________
> > Python tracker <report at bugs.python.org>
> > <https://bugs.python.org/issue38490>
> > _______________________________________
> >
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue38490>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38490>
_______________________________________

From report at bugs.python.org  Thu Oct 17 10:31:04 2019
From: report at bugs.python.org (ynyyn)
Date: Thu, 17 Oct 2019 14:31:04 +0000
Subject: [issue38506] Launcher for Windows (py.exe) may rank Python 3.xx (in
 the future) after 3.x
Message-ID: <1571322664.68.0.257867788049.issue38506@roundup.psfhosted.org>


New submission from ynyyn <ynyyn at vip.qq.com>:

I, for interest, read some of source code of Python launcher, and found it used string comparison function (`wcscmp()`, in function `compare_pythons()`) to sort Python version in descending order.

It works well currently. But if Python 3.10 or Python 3.xx comes up in the future, Python 3.xx will be ranked after 3.x.

I modified the Registry and made a fake version Python 3.10, to check the launcher's behaviour.

```
PS > py -0p
Installed Pythons found by C:\Windows\py.exe Launcher for Windows
 -3.8-64        D:\Program Files\Python38\python.exe *
 -3.7-64        D:\Program Files\Python37\python.exe
 -3.7-32        D:\Program Files (x86)\Python37-32\python.exe
 -3.6-32        C:\Program Files (x86)\Python36-32\python.exe
 -3.10-64       D:\Program Files\Python37\python.exe
 -2.7-64        C:\python27-x64\python.exe
```

The result turned out that Python 3.10 was really ranked after 3.x.

And it seems that Python 3.xx should be a valid (or supported) version according to the comment from function `validate_version()`.


```
static BOOL
validate_version(wchar_t * p)
{
    /*
    Version information should start with the major version,
    Optionally followed by a period and a minor version,
    Optionally followed by a minus and one of 32 or 64.
    Valid examples:
      ...
      2.7-32
      The intent is to add to the valid patterns:
      3.10
      3-32
      ...
    */

I am not sure whether this is a potential defect that had been confirmed before... But I do not see some relevant comments in the source code.

----------
components: Windows
messages: 354843
nosy: paul.moore, steve.dower, tim.golden, ynyyn, zach.ware
priority: normal
severity: normal
status: open
title: Launcher for Windows (py.exe) may rank Python 3.xx (in the future) after 3.x
type: behavior
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38506>
_______________________________________

From report at bugs.python.org  Thu Oct 17 10:45:11 2019
From: report at bugs.python.org (JUN-WEI SONG)
Date: Thu, 17 Oct 2019 14:45:11 +0000
Subject: [issue38507] Improve the documentation of the nested list
 initialization
Message-ID: <1571323511.47.0.548747991495.issue38507@roundup.psfhosted.org>


New submission from JUN-WEI SONG <sungboss2004 at gmail.com>:

When I used the nested list, I need to initialize the nested list, so I used this expression:

>>> nested_list = [[]] * 5

see also: https://stackoverflow.com/questions/12791501/python-initializing-a-list-of-lists

So I later learned that such an expression would make the list inside the list have the same reference, which would cause the problem that you modified one element would lead to all elements changed in the nested list.

For example:

>>> nested_list[0].append(1)
>>> nested_list
[[1], [1], [1], [1], [1]]

Therefore, maybe we could tell users how to initialize the list on the documentation like below:

If you need to initialize the nested list, you could follow the below example, also, be aware of the expression like ``[[]] * 5``, this will cause the five lists in the nested list to have the same reference.

   >>> nested_list = [[] for _ in range(5)]

----------
assignee: docs at python
components: Documentation
messages: 354844
nosy: docs at python, krnick
priority: normal
severity: normal
status: open
title: Improve the documentation of the nested list initialization
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38507>
_______________________________________

From report at bugs.python.org  Thu Oct 17 10:53:28 2019
From: report at bugs.python.org (Fabio Zadrozny)
Date: Thu, 17 Oct 2019 14:53:28 +0000
Subject: [issue38508] Tracing events anomaly when creating a multi-line list
Message-ID: <1571324008.26.0.275213051562.issue38508@roundup.psfhosted.org>


New submission from Fabio Zadrozny <fabioz at users.sourceforge.net>:

When creating a multi-line list it seems that there's an additional line event that goes back to the start of the list.

i.e.: considering the code as:

[
1,
2
]

when stepping through the list, a debugger would get a line event at the `1` then at `2` and then at `['.

I'm attaching a sample code which prints the traced lines, where it's possible to see that there's a line event that goes backward to the list creation there (note that on Python 3.7 there's no line event for the list creation).

----------
components: Interpreter Core
files: snippet33.py
messages: 354845
nosy: fabioz
priority: normal
severity: normal
status: open
title: Tracing events anomaly when creating a multi-line list
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file48665/snippet33.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38508>
_______________________________________

From report at bugs.python.org  Thu Oct 17 11:15:58 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 17 Oct 2019 15:15:58 +0000
Subject: [issue38506] Launcher for Windows (py.exe) may rank Python 3.xx (in
 the future) after 3.x
In-Reply-To: <1571322664.68.0.257867788049.issue38506@roundup.psfhosted.org>
Message-ID: <1571325358.45.0.0943818352711.issue38506@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

You're right that this will need fixing. But we don't really have to fix it any earlier than 3.10 - the launcher is backwards-compatible but not necessarily forwards-compatible. Still, we can take a fix whenever.

Probably it should just change to using CompareStringEx with (at least) the SORT_DIGITSASNUMBERS flag.

https://docs.microsoft.com/windows/win32/api/stringapiset/nf-stringapiset-comparestringex

----------
stage:  -> test needed
versions:  -Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38506>
_______________________________________

From report at bugs.python.org  Thu Oct 17 11:26:05 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 17 Oct 2019 15:26:05 +0000
Subject: [issue38508] Tracing events anomaly when creating a multi-line list
In-Reply-To: <1571324008.26.0.275213051562.issue38508@roundup.psfhosted.org>
Message-ID: <1571325965.86.0.700110684324.issue38508@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Considering the code as:

x = {
1,
2
}

It first gets constant 1.
Then gets constant 2.
Then build a set.
Then assign it to the variable.

Obviously that the variable is assigned at line 1, so you would get a backward line in any case. The set display is multiline, it occupies lines 1 to 4. What line should be reported? In many cases it is more convenient to take a first line of the multiline expression. If the building a set failed (for example if items are not hashable) you will a line "x = {" in the traceback instead of just "}".

This is not a bug, but a feature. In future perhaps tracing and traceback will get a range instead of a single line for multiline expressions, but it requires significant changes in the code.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38508>
_______________________________________

From report at bugs.python.org  Thu Oct 17 11:31:01 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 17 Oct 2019 15:31:01 +0000
Subject: [issue38507] Improve the documentation of the nested list
 initialization
In-Reply-To: <1571323511.47.0.548747991495.issue38507@roundup.psfhosted.org>
Message-ID: <1571326261.71.0.591531296569.issue38507@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

It is already documented. See note 2 at https://docs.python.org/3/library/stdtypes.html#common-sequence-operations.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38507>
_______________________________________

From report at bugs.python.org  Thu Oct 17 11:42:20 2019
From: report at bugs.python.org (JUN-WEI SONG)
Date: Thu, 17 Oct 2019 15:42:20 +0000
Subject: [issue38507] Improve the documentation of the nested list
 initialization
In-Reply-To: <1571323511.47.0.548747991495.issue38507@roundup.psfhosted.org>
Message-ID: <1571326940.5.0.100079846271.issue38507@roundup.psfhosted.org>


JUN-WEI SONG <sungboss2004 at gmail.com> added the comment:

sorry that I did not notice it already documented

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38507>
_______________________________________

From report at bugs.python.org  Thu Oct 17 11:48:01 2019
From: report at bugs.python.org (Fabio Zadrozny)
Date: Thu, 17 Oct 2019 15:48:01 +0000
Subject: [issue38508] Tracing events anomaly when creating a multi-line list
In-Reply-To: <1571324008.26.0.275213051562.issue38508@roundup.psfhosted.org>
Message-ID: <1571327281.88.0.800131709782.issue38508@roundup.psfhosted.org>


Fabio Zadrozny <fabioz at users.sourceforge.net> added the comment:

If it's a feature and not a bug, seems ok to me (I reported mainly because I thought the behavior was odd, but I guess it makes sense).

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38508>
_______________________________________

From report at bugs.python.org  Thu Oct 17 12:38:32 2019
From: report at bugs.python.org (Aniruddha Bhattacharjee)
Date: Thu, 17 Oct 2019 16:38:32 +0000
Subject: [issue38509] Insufficient description of relative imports in
 docs.python.org
Message-ID: <1571330312.31.0.925076175941.issue38509@roundup.psfhosted.org>


New submission from Aniruddha Bhattacharjee <aniruddha97bhatt at gmail.com>:

In the section "relative imports" of the documentation for "import system", the use of relative imports is explained with the use of an example, however if you try the exact same thing it gives an error. This is nicely explained in https://stackoverflow.com/questions/14132789/relative-imports-for-the-billionth-time and https://www.python.org/dev/peps/pep-0395/. This has also been added as an open issue in the documentation . Is this still under consideration, then I would be happy to update the docs. Thanks

----------
assignee: docs at python
components: Documentation
messages: 354851
nosy: Aniruddha Bhattacharjee, docs at python
priority: normal
severity: normal
status: open
title: Insufficient description of relative imports in docs.python.org
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38509>
_______________________________________

From report at bugs.python.org  Thu Oct 17 14:32:23 2019
From: report at bugs.python.org (John Muth)
Date: Thu, 17 Oct 2019 18:32:23 +0000
Subject: [issue37839] makesetup Doesn't Handle Defines with Equal Sign
In-Reply-To: <1565694009.91.0.692452487744.issue37839@roundup.psfhosted.org>
Message-ID: <1571337143.14.0.0255582335561.issue37839@roundup.psfhosted.org>


John Muth <muth at kontain.app> added the comment:

I ran into the same issue. This patch fixed it for me.

diff --git a/Modules/makesetup b/Modules/makesetup
index eac97ad134..0fbac03833 100755
--- a/Modules/makesetup
+++ b/Modules/makesetup
@@ -133,6 +133,7 @@ sed -e 's/[         ]*#.*//' -e '/^[        ]*$/d' |
 
                # Output DEFS in reverse order so first definition overrides
                case $line in
+               *-D*) ;;
                *=*)    DEFS="$line$NL$DEFS"; continue;;
                'include '*)    DEFS="$line$NL$DEFS"; continue;;
                '*noobjects*')

----------
nosy: +John Muth

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37839>
_______________________________________

From report at bugs.python.org  Thu Oct 17 16:49:31 2019
From: report at bugs.python.org (Ned Deily)
Date: Thu, 17 Oct 2019 20:49:31 +0000
Subject: [issue38504] Reduce the size of deb package
In-Reply-To: <1571304858.59.0.51110588392.issue38504@roundup.psfhosted.org>
Message-ID: <1571345371.75.0.962726194805.issue38504@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

You might also want to try on StackOverflow or on an Ubuntu or Debian forum. We don't produce deb packages ourselves.

----------
nosy: +ned.deily
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38504>
_______________________________________

From report at bugs.python.org  Thu Oct 17 16:55:39 2019
From: report at bugs.python.org (Chiu Speq)
Date: Thu, 17 Oct 2019 20:55:39 +0000
Subject: [issue38510] build python with --enable-shared with static linked
 python against libpython*.a
Message-ID: <1571345739.37.0.277931445502.issue38510@roundup.psfhosted.org>


New submission from Chiu Speq <speq.chiu at gmail.com>:

Build python with --enable-shared will create python binary linked against the shared library. You have LD_LIBRARY_PATH before using python binary if it is installed non-system wide. (ex. using gnu modules load).
Changing BLDLIBRARY in configuration could make program work as usual (without setting LD_LIBRARY_PATH) and generating shared-object as well.

----------
components: Build
files: configure.patch
keywords: patch
messages: 354854
nosy: Chiu Speq
priority: normal
severity: normal
status: open
title: build python with --enable-shared with static linked python against libpython*.a
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file48666/configure.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38510>
_______________________________________

From report at bugs.python.org  Thu Oct 17 17:58:33 2019
From: report at bugs.python.org (Ned Deily)
Date: Thu, 17 Oct 2019 21:58:33 +0000
Subject: [issue37195] test_utime fails on MacOS Mojave (Kernel Version 18.6.0:)
In-Reply-To: <1559912694.09.0.24854010798.issue37195@roundup.psfhosted.org>
Message-ID: <1571349513.5.0.612535743881.issue37195@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

@pablogsal, Is this still an issue for you?  AFAIK, there have been no other reports of this behavior.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37195>
_______________________________________

From report at bugs.python.org  Thu Oct 17 18:00:00 2019
From: report at bugs.python.org (PyScripter)
Date: Thu, 17 Oct 2019 22:00:00 +0000
Subject: [issue22213] Make pyvenv style virtual environments easier to
 configure when embedding Python
In-Reply-To: <1408275761.36.0.915361061447.issue22213@psf.upfronthosting.co.za>
Message-ID: <1571349600.3.0.915286547021.issue22213@roundup.psfhosted.org>


PyScripter <pyscripter at gmail.com> added the comment:

Just in case this will be of help to anyone, I found a way to use venvs in embedded python.

- You first need to Initialize python that is referred as home in pyvenv.cfg.
- Then you execute the following script:

import sys
sys.executable = r"Path to the python executable inside the venv"
path = sys.path
for i in range(len(path)-1, -1, -1):
    if path[i].find("site-packages") > 0:
        path.pop(i)
import site
site.main()
del sys, path, i, site

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22213>
_______________________________________

From report at bugs.python.org  Thu Oct 17 18:39:17 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 17 Oct 2019 22:39:17 +0000
Subject: [issue22213] Make pyvenv style virtual environments easier to
 configure when embedding Python
In-Reply-To: <1408275761.36.0.915361061447.issue22213@psf.upfronthosting.co.za>
Message-ID: <1571351957.95.0.516411629466.issue22213@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

If you just want to be able to import modules from the venv, and you know the path to it, it's simpler to just do:

    import sys
    sys.path.append(r"path to venv\Lib\site-packages")

Updating sys.executable is only necessary if you're going to use libraries that try to re-launch itself, but any embedding application is going to have to do that anyway.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22213>
_______________________________________

From report at bugs.python.org  Thu Oct 17 19:01:08 2019
From: report at bugs.python.org (PyScripter)
Date: Thu, 17 Oct 2019 23:01:08 +0000
Subject: [issue22213] Make pyvenv style virtual environments easier to
 configure when embedding Python
In-Reply-To: <1408275761.36.0.915361061447.issue22213@psf.upfronthosting.co.za>
Message-ID: <1571353268.94.0.180616370381.issue22213@roundup.psfhosted.org>


PyScripter <pyscripter at gmail.com> added the comment:

To Steve:

I want the embedded venv to have the same sys.path as if you were running the venv python interpreter.  So my method takes into account for instance the include-system-site-packages option in pyvenv.cfg.  Also my method sets sys.prefix in the same way as the venv python interpreter.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22213>
_______________________________________

From report at bugs.python.org  Thu Oct 17 20:21:36 2019
From: report at bugs.python.org (Alexey Izbyshev)
Date: Fri, 18 Oct 2019 00:21:36 +0000
Subject: [issue34977] Release Windows Store app containing Python
In-Reply-To: <1539470627.18.0.788709270274.issue34977@psf.upfronthosting.co.za>
Message-ID: <1571358096.73.0.772882969853.issue34977@roundup.psfhosted.org>


Change by Alexey Izbyshev <izbyshev at ispras.ru>:


----------
pull_requests: +16379
pull_request: https://github.com/python/cpython/pull/5812

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34977>
_______________________________________

From report at bugs.python.org  Thu Oct 17 21:26:29 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 18 Oct 2019 01:26:29 +0000
Subject: [issue34508] return of non-parenthesized star-unpacking expression a
 SyntaxError
In-Reply-To: <1535293550.9.0.56676864532.issue34508@psf.upfronthosting.co.za>
Message-ID: <1571361989.72.0.0704856491089.issue34508@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
versions: +Python 3.9 -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34508>
_______________________________________

From report at bugs.python.org  Thu Oct 17 23:30:49 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Fri, 18 Oct 2019 03:30:49 +0000
Subject: [issue33604] HMAC default to MD5 marked as to be removed in 3.6
In-Reply-To: <1527014760.1.0.682650639539.issue33604@psf.upfronthosting.co.za>
Message-ID: <1571369449.8.0.445075306119.issue33604@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:


New changeset f33c57d5c780da1500619f548585792bb5b750ee by Gregory P. Smith in branch 'master':
bpo-33604: Raise TypeError on missing hmac arg. (GH-16805)
https://github.com/python/cpython/commit/f33c57d5c780da1500619f548585792bb5b750ee


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33604>
_______________________________________

From report at bugs.python.org  Thu Oct 17 23:31:13 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 03:31:13 +0000
Subject: [issue33604] HMAC default to MD5 marked as to be removed in 3.6
In-Reply-To: <1527014760.1.0.682650639539.issue33604@psf.upfronthosting.co.za>
Message-ID: <1571369473.77.0.986542979013.issue33604@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16380
pull_request: https://github.com/python/cpython/pull/16833

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33604>
_______________________________________

From report at bugs.python.org  Thu Oct 17 23:48:46 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 03:48:46 +0000
Subject: [issue33604] HMAC default to MD5 marked as to be removed in 3.6
In-Reply-To: <1527014760.1.0.682650639539.issue33604@psf.upfronthosting.co.za>
Message-ID: <1571370526.22.0.0385034607265.issue33604@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset c615db608dbb36a5d10188f7d265dcec7bfcc3cf by Miss Islington (bot) in branch '3.8':
bpo-33604: Raise TypeError on missing hmac arg. (GH-16805)
https://github.com/python/cpython/commit/c615db608dbb36a5d10188f7d265dcec7bfcc3cf


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33604>
_______________________________________

From report at bugs.python.org  Fri Oct 18 00:59:30 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 18 Oct 2019 04:59:30 +0000
Subject: [issue34508] return of non-parenthesized star-unpacking expression a
 SyntaxError
In-Reply-To: <1535293550.9.0.56676864532.issue34508@psf.upfronthosting.co.za>
Message-ID: <1571374770.85.0.724263156125.issue34508@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

Why is this still open? That feature appears already implemented.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34508>
_______________________________________

From report at bugs.python.org  Fri Oct 18 01:01:08 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 18 Oct 2019 05:01:08 +0000
Subject: [issue34508] return of non-parenthesized star-unpacking expression a
 SyntaxError
In-Reply-To: <1535293550.9.0.56676864532.issue34508@psf.upfronthosting.co.za>
Message-ID: <1571374868.68.0.136640805872.issue34508@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

See:

commit fd97d1f1af910a6222ea12aec42c456b64f9aee4
Author: David Cuthbert <dacut at kanga.org>
Date:   Fri Sep 21 18:31:15 2018

    bpo-32117: Allow tuple unpacking in return and yield statements (gh-4509)
    
    Iterable unpacking is now allowed without parentheses in yield and return
    statements, e.g. ``yield 1, 2, 3, *rest``. Thanks to David Cuthbert for the
    change and jChapman for added tests.

----------
resolution:  -> out of date
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34508>
_______________________________________

From report at bugs.python.org  Fri Oct 18 01:05:03 2019
From: report at bugs.python.org (Tim Peters)
Date: Fri, 18 Oct 2019 05:05:03 +0000
Subject: [issue38490] statistics: add covariance and Pearson's correlation
In-Reply-To: <1571175609.51.0.475949905245.issue38490@roundup.psfhosted.org>
Message-ID: <1571375103.1.0.82428693649.issue38490@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

I'm in favor of adding all of this (covariance, coefficient, linear regression).  It's still at the level of elementary statistics, and even taught in watered down "business statistics" classes.  It's about the minimum that can be done beyond single-variable stats.

But I also think this defines the limit of what the core "should" include in this area.

----------
nosy: +tim.peters

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38490>
_______________________________________

From report at bugs.python.org  Fri Oct 18 02:54:41 2019
From: report at bugs.python.org (minjeong kim)
Date: Fri, 18 Oct 2019 06:54:41 +0000
Subject: [issue38511] Multiprocessing does not work properly when using the
 trace module.
Message-ID: <1571381681.91.0.0356393028102.issue38511@roundup.psfhosted.org>


New submission from minjeong kim <98nba at naver.com>:

normal result :
$ python test.py
{'p1': 1, 'p2': 1, 'p3': 1, 'p4': 1}

run with tracing :
$ python -mtrace --trackcalls test.py
{}

It seems that the foo and save functions that multiprocess should call are not called.

----------
components: Library (Lib)
files: test.py
messages: 354864
nosy: rls1004
priority: normal
severity: normal
status: open
title: Multiprocessing does not work properly when using the trace module.
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6
Added file: https://bugs.python.org/file48667/test.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38511>
_______________________________________

From report at bugs.python.org  Fri Oct 18 03:35:08 2019
From: report at bugs.python.org (=?utf-8?b?UsO8ZGlnZXIgUGzDvG0=?=)
Date: Fri, 18 Oct 2019 07:35:08 +0000
Subject: [issue38347] pathfix.py does not find Python scripts that have '-' in
 its filename
In-Reply-To: <1570007735.24.0.378926810144.issue38347@roundup.psfhosted.org>
Message-ID: <1571384108.69.0.160312088414.issue38347@roundup.psfhosted.org>


R?diger Pl?m <r.pluem at gmx.de> added the comment:

Thanks for the information. I opened a support request.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38347>
_______________________________________

From report at bugs.python.org  Fri Oct 18 03:39:20 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 18 Oct 2019 07:39:20 +0000
Subject: [issue38465] The type of ob_exports in PyByteArrayObject become
 Py_ssize_t.
In-Reply-To: <1570978635.87.0.596564542888.issue38465@roundup.psfhosted.org>
Message-ID: <1571384360.02.0.307299172463.issue38465@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

See also array and mmap.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38465>
_______________________________________

From report at bugs.python.org  Fri Oct 18 03:52:18 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 07:52:18 +0000
Subject: [issue38418] Audit event for os.system is incorrect
In-Reply-To: <1570588084.56.0.375267797277.issue38418@roundup.psfhosted.org>
Message-ID: <1571385138.87.0.607315375214.issue38418@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset fbe3c76c7ce1eec887d332d801d3784212cc0f73 by Miss Islington (bot) (Steve Dower) in branch 'master':
bpo-38418: Fixes audit event for os.system to be named 'os.system' (GH-16670)
https://github.com/python/cpython/commit/fbe3c76c7ce1eec887d332d801d3784212cc0f73


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38418>
_______________________________________

From report at bugs.python.org  Fri Oct 18 03:52:29 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 07:52:29 +0000
Subject: [issue38418] Audit event for os.system is incorrect
In-Reply-To: <1570588084.56.0.375267797277.issue38418@roundup.psfhosted.org>
Message-ID: <1571385149.66.0.982609070854.issue38418@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16381
pull_request: https://github.com/python/cpython/pull/16836

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38418>
_______________________________________

From report at bugs.python.org  Fri Oct 18 03:58:26 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 18 Oct 2019 07:58:26 +0000
Subject: [issue38410] Possible fatal errors due to
 _PyEval_SetAsyncGen{Finalizer, Firstiter}()
In-Reply-To: <1570543574.99.0.942798410146.issue38410@roundup.psfhosted.org>
Message-ID: <1571385506.38.0.228799136814.issue38410@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Why this ABI is exported at all? These functions are only used in the sys module, why they are defined in ceval.c instead of be static functions in sysmodule.c?

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38410>
_______________________________________

From report at bugs.python.org  Fri Oct 18 04:00:06 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 18 Oct 2019 08:00:06 +0000
Subject: [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1571385606.92.0.990404358447.issue32758@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 8eb27cc35489848596d9fb4b1c91fac00ae75d21 by Serhiy Storchaka (Ashley Whetter) in branch '2.7':
bpo-32758: Warn that compile() can crash when compiling to an AST object (GH-6043) (GH-16566)
https://github.com/python/cpython/commit/8eb27cc35489848596d9fb4b1c91fac00ae75d21


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32758>
_______________________________________

From report at bugs.python.org  Fri Oct 18 04:00:26 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 18 Oct 2019 08:00:26 +0000
Subject: [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1571385626.3.0.184805319023.issue32758@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset dedb99acdb5bbc179872235f975248133d3fb440 by Serhiy Storchaka (Ashley Whetter) in branch '2.7':
bpo-32758: Warn that ast.parse() and ast.literal_eval() can segfault the interpreter (GH-5960) (GH-16565)
https://github.com/python/cpython/commit/dedb99acdb5bbc179872235f975248133d3fb440


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32758>
_______________________________________

From report at bugs.python.org  Fri Oct 18 04:02:07 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 18 Oct 2019 08:02:07 +0000
Subject: [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1571385727.85.0.242082019835.issue32758@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32758>
_______________________________________

From report at bugs.python.org  Fri Oct 18 05:33:13 2019
From: report at bugs.python.org (zr22122)
Date: Fri, 18 Oct 2019 09:33:13 +0000
Subject: [issue38512] bug of the v3.8 api demo case
Message-ID: <1571391193.91.0.262010952347.issue38512@roundup.psfhosted.org>


New submission from zr22122 <2212239597 at qq.com>:

There exists a bug in the python 3.7 API document, as the picture shows below.
When run this code in my python3.7.3 windows7 os, error occurs.

----------
components: Regular Expressions
files: 2.png
messages: 354871
nosy: ezio.melotti, mrabarnett, zr22122
priority: normal
severity: normal
status: open
title: bug of the v3.8 api demo case
versions: Python 3.8
Added file: https://bugs.python.org/file48668/2.png

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38512>
_______________________________________

From report at bugs.python.org  Fri Oct 18 05:33:55 2019
From: report at bugs.python.org (zr22122)
Date: Fri, 18 Oct 2019 09:33:55 +0000
Subject: [issue38512] bug of the v3.7 API document demo case code
In-Reply-To: <1571391193.91.0.262010952347.issue38512@roundup.psfhosted.org>
Message-ID: <1571391235.84.0.579747889557.issue38512@roundup.psfhosted.org>


Change by zr22122 <2212239597 at qq.com>:


----------
title: bug of the v3.8 api demo case -> bug of the v3.7 API document demo case code

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38512>
_______________________________________

From report at bugs.python.org  Fri Oct 18 05:39:55 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Fri, 18 Oct 2019 09:39:55 +0000
Subject: [issue38513] Should we maintain Jython related code?
Message-ID: <1571391594.51.0.774238079811.issue38513@roundup.psfhosted.org>


New submission from Dong-hee Na <donghee.na92 at gmail.com>:

I can read some of Jython related code on the master branch.
ASFIK, this codes are the legacy of Jython2.
Currently, Jython3 stops development since 2017.
https://github.com/jython/jython3

Can we get rid of the Jython related code?
Or is there any reason to maintain those codes?

----------
messages: 354872
nosy: corona10, serhiy.storchaka, vstinner
priority: normal
severity: normal
status: open
title: Should we maintain Jython related code?

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38513>
_______________________________________

From report at bugs.python.org  Fri Oct 18 05:50:54 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Fri, 18 Oct 2019 09:50:54 +0000
Subject: [issue38512] bug of the v3.7 API document demo case code
In-Reply-To: <1571391193.91.0.262010952347.issue38512@roundup.psfhosted.org>
Message-ID: <1571392254.48.0.114203273265.issue38512@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

What is this a screen shot of?

What error occurs? The picture doesn't show any errors that I can see.

Please COPY and PASTE the code you are running, as text, and the FULL EXCEPTION (the traceback and error message), if there is one. We cannot guess what error you are getting, and you should not expect us to re-type code shown in a screen shot.

Thank you.

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38512>
_______________________________________

From report at bugs.python.org  Fri Oct 18 06:00:47 2019
From: report at bugs.python.org (=?utf-8?q?J=C3=A9r=C3=B4me_Laurens?=)
Date: Fri, 18 Oct 2019 10:00:47 +0000
Subject: [issue38514] pathlib's mkdir documentation improvement
Message-ID: <1571392847.0.0.675625809065.issue38514@roundup.psfhosted.org>


New submission from J?r?me Laurens <jerome.laurens at u-bourgogne.fr>:

There are some inconsistencies in the actual documentation of path lib's mkdir doc.

Here is the 3.7 version, annotated and followed by a change proposal

Path.mkdir(mode=0o777, parents=False, exist_ok=False)
Create a new directory at this given path. If mode is given, it is combined with the process? umask value to determine the file mode and access flags. If the path already exists, FileExistsError is raised. <<<<<<<<<<<<<<<<<< NOT ALWAYS due to exist_ok.

If parents is true, any missing parents of this path are created as needed; they are created with the default permissions without taking mode into account (mimicking the POSIX mkdir -p command).

If parents is false (the default), a missing parent raises FileNotFoundError.

If exist_ok is false (the default), FileExistsError is raised if the target directory already exists.

If exist_ok is true, FileExistsError exceptions will be ignored (same behavior as the POSIX mkdir -p command), but only if the last path component is not an existing non-directory file. <<<<<<<<<<<<<<<<<< UNCLEAR: 1) what is an ignored exception ? 2) The reference to POSIX should appear at the end, like above, 3) the last path component is a string 4) usage of a double negation ignore/is not

----- CHANGE ----

Path.mkdir(mode=0o777, parents=False, exist_ok=False)
Create a new directory in the file system at this given path.

If mode is given, it is combined with the process? umask value to determine the file mode and access flags.

If parents is false (the default), a missing parent raises FileNotFoundError.

If parents is true, any missing parents of this path are created as needed; they are created with the default permissions without taking mode into account (mimicking the POSIX mkdir -p command).

If exist_ok is false (the default), FileExistsError is raised if the given path already exists in the file system, whether a directory or not.

If exist_ok is true, FileExistsError is raised only if the given path already exists in the file system and is not a directory (same behavior as the POSIX mkdir -p command).

Thanks for reading

JL

----------
assignee: docs at python
components: Documentation
messages: 354874
nosy: docs at python, jlaurens
priority: normal
severity: normal
status: open
title: pathlib's mkdir documentation improvement
type: enhancement
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38514>
_______________________________________

From report at bugs.python.org  Fri Oct 18 07:04:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 11:04:24 +0000
Subject: [issue38515] regrtest main process timed out after 5 min on AMD64
 FreeBSD CURRENT Shared 3.8
Message-ID: <1571396664.18.0.656974468417.issue38515@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

https://buildbot.python.org/all/#/builders/212/builds/322

=> see the traceback below.

I'm not sure that it's an issue with Python. It seems like the system was way too loaded: system load around 13.29 for 2 CPUs. I know that this buildbot worker is super slow.

The main regrtest process is supposed to write an update every 30 seconds. Timeout after 5 minutes means that the main process was either *very very slow*, or that the _get_result() method was blocked because of a real bug. I'm surprised since the code works well on all other workers. If it's a bug, one explanation would be that it's a race condition which trigger only under very precise timings.

In the main thread of the main process, the code is stuck on:

   self.output.get(timeout=30)

where self.output is a queue.Queue() instance. This line should not take longer than 30 seconds, except if the system is *really* slow.

Maybe that day, the poor AMD64 FreeBSD CURRENT Shared 3.8 was just too slow?

--

It's not the first time that I see this issue. In bpo-37531, it already failed on the same buildbot worker (koobs-freebsd-current):
https://bugs.python.org/issue37531#msg354078

When it failed, the main regrtest process used a timeout of 60 seconds. I changed this timeout to 5 minutes in commit 0ec618af98ac250a91ee9c91f8569e6df6772758.

5 minutes is already quite big. It means that the system failed to give back the CPU to regrtest main process in 5 minutes, whereas it should get the CPU after 30 seconds.

--


https://buildbot.python.org/all/#/builders/212/builds/322

...
== FreeBSD-13.0-CURRENT-amd64-64bit-ELF little-endian
== cwd: /usr/home/buildbot/python/3.8.koobs-freebsd-current/build/build/test_python_4823
== CPU count: 2
== encodings: locale=UTF-8, FS=utf-8
Using random seed 6868206
0:00:00 load avg: 9.98 Run tests in parallel using 4 child processes
0:00:05 load avg: 10.14 [  1/423] test_opcodes passed
...
0:02:12 load avg: 11.82 running: test_capi (2 min 2 sec), test_pickle (1 min 40 sec), test_multiprocessing_spawn (1 min), test_support (2 min 11 sec)
...
0:13:15 load avg: 12.41 [ 80/423] test_rlcompleter passed -- running: test_lib2to3 (1 min 7 sec), test_multiprocessing_spawn (12 min 2 sec)
...
0:13:17 load avg: 12.30 [ 81/423] test_idle skipped -- running: test_lib2to3 (1 min 9 sec), test_multiprocessing_spawn (12 min 4 sec)
...
0:39:19 load avg: 13.70 running: test_concurrent_futures (4 min 23 sec), test_codecmaps_kr (30.0 sec), test_io (5 min 14 sec), test_tokenize (7 min 20 sec)
...
0:40:53 load avg: 13.80 [208/423] test_socketserver passed -- running: test_concurrent_futures (5 min 57 sec), test_tokenize (8 min 53 sec)
0:41:16 load avg: 13.94 [209/423] test_faulthandler passed (38.2 sec) -- running: test_concurrent_futures (6 min 20 sec), test_tokenize (9 min 16 sec)
0:41:29 load avg: 13.29 [210/423] test_glob passed -- running: test_concurrent_futures (6 min 33 sec), test_zipfile (36.3 sec), test_tokenize (9 min 30 sec)
Timeout (0:05:00)!
Thread 0x000000080257c800 (most recent call first):
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/selectors.py", line 415 in select
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/subprocess.py", line 1866 in _communicate
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/subprocess.py", line 1024 in communicate
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 191 in _run_process
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 229 in _runtest
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 264 in run
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/threading.py", line 932 in _bootstrap_inner
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/threading.py", line 890 in _bootstrap

Thread 0x000000080257b900 (most recent call first):
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/selectors.py", line 415 in select
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/subprocess.py", line 1866 in _communicate
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/subprocess.py", line 1024 in communicate
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 191 in _run_process
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 229 in _runtest
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 264 in run
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/threading.py", line 932 in _bootstrap_inner
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/threading.py", line 890 in _bootstrap

Thread 0x000000080257b400 (most recent call first):
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/selectors.py", line 415 in select
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/subprocess.py", line 1866 in _communicate
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/subprocess.py", line 1024 in communicate
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 191 in _run_process
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 229 in _runtest
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 264 in run
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/threading.py", line 932 in _bootstrap_inner
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/threading.py", line 890 in _bootstrap

Thread 0x000000080257be00 (most recent call first):
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/selectors.py", line 415 in select
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/subprocess.py", line 1866 in _communicate
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/subprocess.py", line 1024 in communicate
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 191 in _run_process
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 229 in _runtest
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 264 in run
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/threading.py", line 932 in _bootstrap_inner
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/threading.py", line 890 in _bootstrap

Thread 0x0000000800ac3000 (most recent call first):
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/threading.py", line 306 in wait
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/queue.py", line 179 in get
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 372 in _get_result
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 423 in run_tests
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/runtest_mp.py", line 444 in run_tests_multiprocess
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/main.py", line 513 in run_tests
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/main.py", line 687 in _main
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/main.py", line 634 in main
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/libregrtest/main.py", line 712 in main
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/test/__main__.py", line 2 in <module>
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/runpy.py", line 85 in _run_code
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-current/build/Lib/runpy.py", line 192 in _run_module_as_main
*** Error code 1

Stop.
make: stopped in /usr/home/buildbot/python/3.8.koobs-freebsd-current/build

----------
components: Tests
messages: 354875
nosy: vstinner
priority: normal
severity: normal
status: open
title: regrtest main process timed out after 5 min on AMD64 FreeBSD CURRENT Shared 3.8
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38515>
_______________________________________

From report at bugs.python.org  Fri Oct 18 07:04:33 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 11:04:33 +0000
Subject: [issue38515] regrtest main process timed out after 5 min on AMD64
 FreeBSD CURRENT Shared 3.8
In-Reply-To: <1571396664.18.0.656974468417.issue38515@roundup.psfhosted.org>
Message-ID: <1571396673.99.0.750046170867.issue38515@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +koobs, pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38515>
_______________________________________

From report at bugs.python.org  Fri Oct 18 07:06:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 11:06:24 +0000
Subject: [issue37224] test__xxsubinterpreters fails randomly
In-Reply-To: <1560214681.61.0.906498246375.issue37224@roundup.psfhosted.org>
Message-ID: <1571396784.95.0.224728875529.issue37224@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The race condition can be reproduced on Linux using a lot of parallel test worker processes. For example, I reproduce it on my laptop (8 CPUs) using:

$ ./python -m test test__xxsubinterpreters -F -j30
...
0:00:26 load avg: 17.86 [ 24] test__xxsubinterpreters passed
0:00:26 load avg: 17.86 [ 25] test__xxsubinterpreters passed
0:00:26 load avg: 17.86 [ 26] test__xxsubinterpreters passed
0:00:27 load avg: 17.86 [ 27/1] test__xxsubinterpreters failed
Exception in thread Thread-8:
Traceback (most recent call last):
  File "/home/vstinner/python/master/Lib/threading.py", line 944, in _bootstrap_inner
    self.run()
  File "/home/vstinner/python/master/Lib/threading.py", line 882, in run
    self._target(*self._args, **self._kwargs)
  File "/home/vstinner/python/master/Lib/test/test__xxsubinterpreters.py", line 51, in run
    interpreters.run_string(interp, dedent(f"""
RuntimeError: unrecognized interpreter ID 46
test test__xxsubinterpreters failed -- Traceback (most recent call last):
  File "/home/vstinner/python/master/Lib/test/test__xxsubinterpreters.py", line 492, in test_subinterpreter
    self.assertTrue(interpreters.is_running(interp))
AssertionError: False is not true

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37224>
_______________________________________

From report at bugs.python.org  Fri Oct 18 07:07:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 11:07:46 +0000
Subject: [issue38513] Should we maintain Jython related code?
In-Reply-To: <1571391594.51.0.774238079811.issue38513@roundup.psfhosted.org>
Message-ID: <1571396866.32.0.481248683356.issue38513@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Currently, Jython3 stops development since 2017.

How official is that?

> Or is there any reason to maintain those codes?

Does it cost any maintenance burden? If not, you have your answer :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38513>
_______________________________________

From report at bugs.python.org  Fri Oct 18 07:08:16 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 11:08:16 +0000
Subject: [issue24260] TabError behavior doesn't match documentation
In-Reply-To: <1432244751.77.0.187754601995.issue24260@psf.upfronthosting.co.za>
Message-ID: <1571396896.88.0.252229335763.issue24260@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy:  -vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24260>
_______________________________________

From report at bugs.python.org  Fri Oct 18 07:46:09 2019
From: report at bugs.python.org (=?utf-8?b?2KrYp9i02YrYsdin2Kog2YXYs9in2YbYrw==?=)
Date: Fri, 18 Oct 2019 11:46:09 +0000
Subject: [issue38511] Multiprocessing does not work properly when using the
 trace module.
In-Reply-To: <1571381681.91.0.0356393028102.issue38511@roundup.psfhosted.org>
Message-ID: <1571399169.81.0.521740498235.issue38511@roundup.psfhosted.org>


Change by ??????? ????? <musaned0506 at gmail.com>:


----------
components: +Windows -Library (Lib)
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
versions: +Python 3.9 -Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38511>
_______________________________________

From report at bugs.python.org  Fri Oct 18 07:46:34 2019
From: report at bugs.python.org (=?utf-8?b?2KrYp9i02YrYsdin2Kog2YXYs9in2YbYrw==?=)
Date: Fri, 18 Oct 2019 11:46:34 +0000
Subject: [issue38511] Multiprocessing does not work properly when using the
 trace module.
In-Reply-To: <1571381681.91.0.0356393028102.issue38511@roundup.psfhosted.org>
Message-ID: <1571399194.15.0.443576089177.issue38511@roundup.psfhosted.org>


Change by ??????? ????? <musaned0506 at gmail.com>:


----------
nosy: +??????? ?????

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38511>
_______________________________________

From report at bugs.python.org  Fri Oct 18 07:46:33 2019
From: report at bugs.python.org (Kubilay Kocak)
Date: Fri, 18 Oct 2019 11:46:33 +0000
Subject: [issue38515] regrtest main process timed out after 5 min on AMD64
 FreeBSD CURRENT Shared 3.8
In-Reply-To: <1571396664.18.0.656974468417.issue38515@roundup.psfhosted.org>
Message-ID: <1571399193.03.0.125263868063.issue38515@roundup.psfhosted.org>


Kubilay Kocak <koobs.freebsd at gmail.com> added the comment:

@Victor 

The guest running the worker was:

- running a FreeBSD build world (-j8)concurrently which is what was creating additional load, though I've done this before and it hasn't caused timeouts.
- suspended/resumed (virtualbox save/restore) which may have affected timings

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38515>
_______________________________________

From report at bugs.python.org  Fri Oct 18 07:46:54 2019
From: report at bugs.python.org (=?utf-8?b?2KrYp9i02YrYsdin2Kog2YXYs9in2YbYrw==?=)
Date: Fri, 18 Oct 2019 11:46:54 +0000
Subject: [issue38511] Multiprocessing does not work properly when using the
 trace module.
In-Reply-To: <1571381681.91.0.0356393028102.issue38511@roundup.psfhosted.org>
Message-ID: <1571399214.0.0.504807429611.issue38511@roundup.psfhosted.org>


??????? ????? <musaned0506 at gmail.com> added the comment:

#!/usr/bin/env python
import multiprocessing, sys, trace
from functools import partial

num_list = ['p1', 'p2', 'p3', 'p4']

def foo(name):
    print(name+'\n')
    return name
def save(result, shared):
    print('a\n')
    shared.results[result] = 1

def mm():
    manager = multiprocessing.Manager()
    shared = manager.dict()
    shared.results = dict()

    clbk = partial(save, shared=shared)

    pool = multiprocessing.Pool(processes=2)
    serial_pool = multiprocessing.Pool(1)

    for name in num_list:
        serial_pool.apply_async(foo, args=[name], callback=clbk)

    pool.close()
    pool.join()

    print(shared.results)

mm()

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38511>
_______________________________________

From report at bugs.python.org  Fri Oct 18 07:48:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 11:48:59 +0000
Subject: [issue38515] regrtest main process timed out after 5 min on AMD64
 FreeBSD CURRENT Shared 3.8
In-Reply-To: <1571396664.18.0.656974468417.issue38515@roundup.psfhosted.org>
Message-ID: <1571399339.88.0.355002530404.issue38515@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> running a FreeBSD build world (-j8)concurrently which is what was creating additional load, though I've done this before and it hasn't caused timeouts.

Maybe you should turn off the buidbot job while upgrading the system? Or try to tune process priorities?


> suspended/resumed (virtualbox save/restore) which may have affected timings

That may be another explanation, right. But it doesn't look the ideal guilty.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38515>
_______________________________________

From report at bugs.python.org  Fri Oct 18 08:11:14 2019
From: report at bugs.python.org (Michael Jaquier)
Date: Fri, 18 Oct 2019 12:11:14 +0000
Subject: [issue38516] PEP 3132 -- Extended Iterable Unpacking inconsistent
 assignment of * variable
Message-ID: <1571400674.51.0.246530871643.issue38516@roundup.psfhosted.org>


New submission from Michael Jaquier <mjaquier at me.com>:

x = [1,2,3]

Case (1)
*b, = x 
*b == [1, 2, 3]

Case(2)
*b, _ = x 
b = [1,2]



Is it not more logical for this to give consistent values regardless. 

i.e.,

*b, = [1,2,3] ; b == [1,2]

*b, _ = [1,3,2] ;  b == [1,2] ;  _ == [3]

----------
components: Library (Lib)
messages: 354881
nosy: mjaquier
priority: normal
severity: normal
status: open
title: PEP 3132 -- Extended Iterable Unpacking inconsistent assignment of * variable
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38516>
_______________________________________

From report at bugs.python.org  Fri Oct 18 08:16:50 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Fri, 18 Oct 2019 12:16:50 +0000
Subject: [issue38513] Should we maintain Jython related code?
In-Reply-To: <1571391594.51.0.774238079811.issue38513@roundup.psfhosted.org>
Message-ID: <1571401010.28.0.97674716503.issue38513@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> How official is that?

https://github.com/jythontools/jython
jeff5 is now maintaining Jython2 but I can not find Jython3 under development.

> Does it cost any maintenance burden? If not, you have your answer :-)

Yes, it currently not burdens for maintenance.
But is the policy of CPython to care about alternative interpreter implementation? So if the new alternative implementation request to modify CPython code. Is it okay?
If so I agree with not to remove Jython code on Python3.x

But if not, can we gradually remove about alternative interpreter related code? Should we preserve the area for Jython?
https://github.com/python/cpython/blob/master/Doc/using/cmdline.rst#options-you-shouldnt-use

Okay, I understand that there must be a historical reason for those codes. But can we move a step for deprecating them?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38513>
_______________________________________

From report at bugs.python.org  Fri Oct 18 08:25:28 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 12:25:28 +0000
Subject: [issue38513] Should we maintain Jython related code?
In-Reply-To: <1571391594.51.0.774238079811.issue38513@roundup.psfhosted.org>
Message-ID: <1571401528.59.0.452728256196.issue38513@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> But is the policy of CPython to care about alternative interpreter implementation?

I think that everybody would like to see more working implementations of Python:
https://hub.packtpub.com/lukasz-langa-at-pylondinium19-if-python-stays-synonymous-with-cpython-for-too-long-well-be-in-big-trouble/

That's why many tests are decorated with @support.cpython_only.

That's also why the PEP 399 exists.


> So if the new alternative implementation request to modify CPython code. Is it okay? If so I agree with not to remove Jython code on Python3.x

I'm not sure of which kind of changes do you have in mind.

Ronan Lamy who works on PyPy recently contributed to CPython Lib/stat.py module to respect the PEP 399: bpo-38109. Such contribution is very welcomed :-)

When PEPs are discussed, we also try to keep in mind that it should be possible to implement the change on other implementations. If it's not, it should be clearly mentioned and justified in the PEP.

Examples:

https://www.python.org/dev/peps/pep-0509/#changes

"The choice of increasing or not the version when a dictionary method does not change its content is left to the Python implementation. A Python implementation can decide to not increase the version to avoid dictionary lookups in guards."

https://www.python.org/dev/peps/pep-0445/

"The only implementation required to conform to this PEP is CPython, but other implementations may choose to be compatible, or to re-use a similar scheme."

https://www.python.org/dev/peps/pep-0454/

"The tracemalloc module has been written for CPython. Other implementations of Python may not be able to provide it."

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38513>
_______________________________________

From report at bugs.python.org  Fri Oct 18 08:31:08 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 18 Oct 2019 12:31:08 +0000
Subject: [issue38513] Should we maintain Jython related code?
In-Reply-To: <1571391594.51.0.774238079811.issue38513@roundup.psfhosted.org>
Message-ID: <1571401868.32.0.813145203584.issue38513@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I think such kind of questions should be asked on Python-Dev.

Even the 2.7 stdlib and tests are not completely compatible with Jython.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38513>
_______________________________________

From report at bugs.python.org  Fri Oct 18 08:38:24 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Fri, 18 Oct 2019 12:38:24 +0000
Subject: [issue38513] Should we maintain Jython related code?
In-Reply-To: <1571391594.51.0.774238079811.issue38513@roundup.psfhosted.org>
Message-ID: <1571402304.06.0.754714732956.issue38513@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> I think that everybody would like to see more working implementations of Python:

I definitely agree with it :)

> I'm not sure of which kind of changes do you have in mind.
> Such contribution is very welcomed :-)

I know some of the projects which implementing Python3.x interpreter with non-C languages. (e.g GraalPython, RustPython)
I just want to know there will be a chance to them if they meet the wall to implementing an interpreter due to their language-specific issue.

And it will be good news to them. :)

Thanks for the kind explanation about this sensitive issue.

Is it okay to change the resolution of this issue to won't fix?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38513>
_______________________________________

From report at bugs.python.org  Fri Oct 18 08:41:04 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Fri, 18 Oct 2019 12:41:04 +0000
Subject: [issue38516] PEP 3132 -- Extended Iterable Unpacking inconsistent
 assignment of * variable
In-Reply-To: <1571400674.51.0.246530871643.issue38516@roundup.psfhosted.org>
Message-ID: <1571402464.92.0.989941293655.issue38516@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Why would they give the same result when the code is different?

    #1 assign c, d, e and everything left over goes into b
    *b, c, d, e, = [1, 2, 3, 4]

    #2 assign c, d and everything left over goes into b
    *b, c, d, = [1, 2, 3, 4]

    #3 assign c and everything left over goes into b
    *b, c, = [1, 2, 3, 4]

    #4 assign nothing and everything left over goes into b
    *b, = [1, 2, 3, 4]

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38516>
_______________________________________

From report at bugs.python.org  Fri Oct 18 08:50:03 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Fri, 18 Oct 2019 12:50:03 +0000
Subject: [issue38513] Should we maintain Jython related code?
In-Reply-To: <1571391594.51.0.774238079811.issue38513@roundup.psfhosted.org>
Message-ID: <1571403003.09.0.656453205857.issue38513@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> Even the 2.7 stdlib and tests are not completely compatible with Jython.

Maybe most of the alternative interpreters will meet this issue.
AFAIK, Dropbox pyston project also met same issue.
(https://blog.pyston.org/)

If the master branch code is Python 2.x, I didn't open this issue.
But I just want to know CPython is still willing to supporting interpreter specific APIs
(e.g is_jython)

But I think that I got the answer from Victor :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38513>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:00:37 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 13:00:37 +0000
Subject: [issue38513] Should we maintain Jython related code?
In-Reply-To: <1571391594.51.0.774238079811.issue38513@roundup.psfhosted.org>
Message-ID: <1571403637.04.0.928147020139.issue38513@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> I think such kind of questions should be asked on Python-Dev.

This issue is not really a concrete actionable issue. It sounds more like a general discussion about Python implementations. I agree with Serhiy that it should be moved to python-dev. And it would be nice to have such discussion on python-dev ;-)

I close the issue.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38513>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:03:29 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 13:03:29 +0000
Subject: [issue38510] build python with --enable-shared with static linked
 python against libpython*.a
In-Reply-To: <1571345739.37.0.277931445502.issue38510@roundup.psfhosted.org>
Message-ID: <1571403809.79.0.604529554623.issue38510@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38510>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:07:36 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 13:07:36 +0000
Subject: [issue27657] urlparse fails if the path is numeric
In-Reply-To: <1469908637.82.0.696114480311.issue27657@psf.upfronthosting.co.za>
Message-ID: <1571404056.61.0.522911669069.issue27657@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 5a88d50ff013a64fbdb25b877c87644a9034c969 by Senthil Kumaran (Tim Graham) in branch 'master':
bpo-27657: Fix urlparse() with numeric paths (#661)
https://github.com/python/cpython/commit/5a88d50ff013a64fbdb25b877c87644a9034c969


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27657>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:07:36 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 13:07:36 +0000
Subject: [issue22891] code removal from urllib.parse.urlsplit()
In-Reply-To: <1416220944.83.0.361625539874.issue22891@psf.upfronthosting.co.za>
Message-ID: <1571404056.83.0.44789475294.issue22891@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 5a88d50ff013a64fbdb25b877c87644a9034c969 by Senthil Kumaran (Tim Graham) in branch 'master':
bpo-27657: Fix urlparse() with numeric paths (#661)
https://github.com/python/cpython/commit/5a88d50ff013a64fbdb25b877c87644a9034c969


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22891>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:07:37 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 13:07:37 +0000
Subject: [issue754016] urlparse goes wrong with IP:port without scheme
Message-ID: <1571404057.13.0.730862666138.issue754016@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 5a88d50ff013a64fbdb25b877c87644a9034c969 by Senthil Kumaran (Tim Graham) in branch 'master':
bpo-27657: Fix urlparse() with numeric paths (#661)
https://github.com/python/cpython/commit/5a88d50ff013a64fbdb25b877c87644a9034c969


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue754016>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:07:37 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 13:07:37 +0000
Subject: [issue754016] urlparse goes wrong with IP:port without scheme
Message-ID: <1571404057.4.0.481312755895.issue754016@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16383
pull_request: https://github.com/python/cpython/pull/16837

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue754016>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:07:37 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 13:07:37 +0000
Subject: [issue16932] urlparse fails at parsing "www.python.org:80/"
In-Reply-To: <1357903769.2.0.674766943444.issue16932@psf.upfronthosting.co.za>
Message-ID: <1571404057.58.0.0715350025603.issue16932@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16384
pull_request: https://github.com/python/cpython/pull/16837

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16932>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:07:36 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 13:07:36 +0000
Subject: [issue16932] urlparse fails at parsing "www.python.org:80/"
In-Reply-To: <1357903769.2.0.674766943444.issue16932@psf.upfronthosting.co.za>
Message-ID: <1571404056.96.0.432898749059.issue16932@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 5a88d50ff013a64fbdb25b877c87644a9034c969 by Senthil Kumaran (Tim Graham) in branch 'master':
bpo-27657: Fix urlparse() with numeric paths (#661)
https://github.com/python/cpython/commit/5a88d50ff013a64fbdb25b877c87644a9034c969


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16932>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:07:37 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 13:07:37 +0000
Subject: [issue27657] urlparse fails if the path is numeric
In-Reply-To: <1469908637.82.0.696114480311.issue27657@psf.upfronthosting.co.za>
Message-ID: <1571404056.61.0.522911669069.issue27657@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 5a88d50ff013a64fbdb25b877c87644a9034c969 by Senthil Kumaran (Tim Graham) in branch 'master':
bpo-27657: Fix urlparse() with numeric paths (#661)
https://github.com/python/cpython/commit/5a88d50ff013a64fbdb25b877c87644a9034c969


----------
keywords: +patch
message_count: 8.0 -> 9.0
pull_requests: +16382
pull_request: https://github.com/python/cpython/pull/16837

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27657>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:07:37 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 13:07:37 +0000
Subject: [issue22891] code removal from urllib.parse.urlsplit()
In-Reply-To: <1416220944.83.0.361625539874.issue22891@psf.upfronthosting.co.za>
Message-ID: <1571404057.71.0.903317993416.issue22891@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16385
pull_request: https://github.com/python/cpython/pull/16837

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22891>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:10:07 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Fri, 18 Oct 2019 13:10:07 +0000
Subject: [issue38307] Provide Class' end line in pyclbr module
In-Reply-To: <1569691590.29.0.185701662636.issue38307@roundup.psfhosted.org>
Message-ID: <1571404207.56.0.934043571251.issue38307@roundup.psfhosted.org>


Change by Steven D'Aprano <steve+python at pearwood.info>:


----------
title: Provide Class' end line in readmodule module -> Provide Class' end line in pyclbr module

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38307>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:18:33 2019
From: report at bugs.python.org (Ricardo Branco)
Date: Fri, 18 Oct 2019 13:18:33 +0000
Subject: [issue38517] functools.cached_property should support partial
 functions and partialmethod's
Message-ID: <1571404713.25.0.542654366975.issue38517@roundup.psfhosted.org>


New submission from Ricardo Branco <ricardo.smartmatic at gmail.com>:

functools.cached_property should support partial functions and partialmethod's

This way one can create cached_property's dynamically.

----------
components: Library (Lib)
messages: 354893
nosy: Ricardo Branco
priority: normal
severity: normal
status: open
title: functools.cached_property should support partial functions and partialmethod's
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38517>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:24:32 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 13:24:32 +0000
Subject: [issue27657] urlparse fails if the path is numeric
In-Reply-To: <1469908637.82.0.696114480311.issue27657@psf.upfronthosting.co.za>
Message-ID: <1571405072.01.0.590763260003.issue27657@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 82b5f6b16e051f8a2ac6e87ba86b082fa1c4a77f by Miss Islington (bot) in branch '3.7':
bpo-27657: Fix urlparse() with numeric paths (GH-661)
https://github.com/python/cpython/commit/82b5f6b16e051f8a2ac6e87ba86b082fa1c4a77f


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27657>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:24:32 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 13:24:32 +0000
Subject: [issue16932] urlparse fails at parsing "www.python.org:80/"
In-Reply-To: <1357903769.2.0.674766943444.issue16932@psf.upfronthosting.co.za>
Message-ID: <1571405072.28.0.77006332612.issue16932@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 82b5f6b16e051f8a2ac6e87ba86b082fa1c4a77f by Miss Islington (bot) in branch '3.7':
bpo-27657: Fix urlparse() with numeric paths (GH-661)
https://github.com/python/cpython/commit/82b5f6b16e051f8a2ac6e87ba86b082fa1c4a77f


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16932>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:24:32 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 13:24:32 +0000
Subject: [issue22891] code removal from urllib.parse.urlsplit()
In-Reply-To: <1416220944.83.0.361625539874.issue22891@psf.upfronthosting.co.za>
Message-ID: <1571405072.17.0.649546771655.issue22891@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 82b5f6b16e051f8a2ac6e87ba86b082fa1c4a77f by Miss Islington (bot) in branch '3.7':
bpo-27657: Fix urlparse() with numeric paths (GH-661)
https://github.com/python/cpython/commit/82b5f6b16e051f8a2ac6e87ba86b082fa1c4a77f


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22891>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:24:32 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 13:24:32 +0000
Subject: [issue754016] urlparse goes wrong with IP:port without scheme
Message-ID: <1571405072.51.0.142360889234.issue754016@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 82b5f6b16e051f8a2ac6e87ba86b082fa1c4a77f by Miss Islington (bot) in branch '3.7':
bpo-27657: Fix urlparse() with numeric paths (GH-661)
https://github.com/python/cpython/commit/82b5f6b16e051f8a2ac6e87ba86b082fa1c4a77f


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue754016>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:42:54 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 18 Oct 2019 13:42:54 +0000
Subject: [issue38517] functools.cached_property should support partial
 functions and partialmethod's
In-Reply-To: <1571404713.25.0.542654366975.issue38517@roundup.psfhosted.org>
Message-ID: <1571406174.81.0.617468746707.issue38517@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +carljm

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38517>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:46:33 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Fri, 18 Oct 2019 13:46:33 +0000
Subject: [issue38518] Pickle protocol 5 is not documented in the
 data-stream-format section for the pickle docs
Message-ID: <1571406393.97.0.877250924995.issue38518@roundup.psfhosted.org>


New submission from Pablo Galindo Salgado <pablogsal at gmail.com>:

The Data Stream format section of the pickle docs (https://docs.python.org/3/library/pickle.html#data-stream-format) fails to document protocol 5 in the list of protocols.

----------
assignee: docs at python
components: Documentation
messages: 354898
nosy: docs at python, pablogsal, pitrou
priority: normal
severity: normal
status: open
title: Pickle protocol 5 is not documented in the data-stream-format section for the pickle docs
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38518>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:47:43 2019
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 18 Oct 2019 13:47:43 +0000
Subject: [issue38517] functools.cached_property should support partial
 functions and partialmethod's
In-Reply-To: <1571404713.25.0.542654366975.issue38517@roundup.psfhosted.org>
Message-ID: <1571406463.44.0.391914821101.issue38517@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +16386
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16838

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38517>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:49:11 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 13:49:11 +0000
Subject: [issue38502] regrtest: use process groups
In-Reply-To: <1571266006.89.0.625453271604.issue38502@roundup.psfhosted.org>
Message-ID: <1571406551.88.0.499063950633.issue38502@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset ecb035cd14c11521276343397151929a94018a22 by Victor Stinner in branch 'master':
bpo-38502: regrtest uses process groups if available (GH-16829)
https://github.com/python/cpython/commit/ecb035cd14c11521276343397151929a94018a22


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38502>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:51:49 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 13:51:49 +0000
Subject: [issue27657] urlparse fails if the path is numeric
In-Reply-To: <1469908637.82.0.696114480311.issue27657@psf.upfronthosting.co.za>
Message-ID: <1571406709.02.0.728869789705.issue27657@roundup.psfhosted.org>


Change by Senthil Kumaran <senthil at uthcode.com>:


----------
pull_requests: +16388
pull_request: https://github.com/python/cpython/pull/16839

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27657>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:51:49 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 13:51:49 +0000
Subject: [issue754016] urlparse goes wrong with IP:port without scheme
Message-ID: <1571406709.22.0.806674977308.issue754016@roundup.psfhosted.org>


Change by Senthil Kumaran <senthil at uthcode.com>:


----------
pull_requests: +16389
pull_request: https://github.com/python/cpython/pull/16839

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue754016>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:51:49 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 13:51:49 +0000
Subject: [issue22891] code removal from urllib.parse.urlsplit()
In-Reply-To: <1416220944.83.0.361625539874.issue22891@psf.upfronthosting.co.za>
Message-ID: <1571406709.5.0.871883642232.issue22891@roundup.psfhosted.org>


Change by Senthil Kumaran <senthil at uthcode.com>:


----------
pull_requests: +16391
pull_request: https://github.com/python/cpython/pull/16839

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22891>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:51:49 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 13:51:49 +0000
Subject: [issue16932] urlparse fails at parsing "www.python.org:80/"
In-Reply-To: <1357903769.2.0.674766943444.issue16932@psf.upfronthosting.co.za>
Message-ID: <1571406709.38.0.00100470976581.issue16932@roundup.psfhosted.org>


Change by Senthil Kumaran <senthil at uthcode.com>:


----------
pull_requests: +16390
pull_request: https://github.com/python/cpython/pull/16839

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16932>
_______________________________________

From report at bugs.python.org  Fri Oct 18 09:52:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Oct 2019 13:52:42 +0000
Subject: [issue38502] regrtest: use process groups
In-Reply-To: <1571266006.89.0.625453271604.issue38502@roundup.psfhosted.org>
Message-ID: <1571406762.75.0.973451409195.issue38502@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I will wait at least one day to see how buildbots like this change before backporting it to 3.7 and 3.8.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38502>
_______________________________________

From report at bugs.python.org  Fri Oct 18 10:29:57 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 18 Oct 2019 14:29:57 +0000
Subject: [issue38518] Pickle protocol 5 is not documented in the
 data-stream-format section for the pickle docs
In-Reply-To: <1571406393.97.0.877250924995.issue38518@roundup.psfhosted.org>
Message-ID: <1571408997.84.0.555667743598.issue38518@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

I guess it will be fixed with https://github.com/python/cpython/pull/16639

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38518>
_______________________________________

From report at bugs.python.org  Fri Oct 18 11:13:33 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Fri, 18 Oct 2019 15:13:33 +0000
Subject: [issue38518] Pickle protocol 5 is not documented in the
 data-stream-format section for the pickle docs
In-Reply-To: <1571406393.97.0.877250924995.issue38518@roundup.psfhosted.org>
Message-ID: <1571411613.12.0.646019398649.issue38518@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Thanks for the finding, Karthikeyan! :)

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Pickle protocol v 5 needs to be documented

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38518>
_______________________________________

From report at bugs.python.org  Fri Oct 18 11:23:21 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 15:23:21 +0000
Subject: [issue27657] urlparse fails if the path is numeric
In-Reply-To: <1469908637.82.0.696114480311.issue27657@psf.upfronthosting.co.za>
Message-ID: <1571412201.45.0.60137124847.issue27657@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 0f3187c1ce3b3ace60f6c1691dfa3d4e744f0384 by Senthil Kumaran in branch '3.8':
[3.8] bpo-27657: Fix urlparse() with numeric paths (GH-661) (#16839)
https://github.com/python/cpython/commit/0f3187c1ce3b3ace60f6c1691dfa3d4e744f0384


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27657>
_______________________________________

From report at bugs.python.org  Fri Oct 18 11:23:21 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 15:23:21 +0000
Subject: [issue22891] code removal from urllib.parse.urlsplit()
In-Reply-To: <1416220944.83.0.361625539874.issue22891@psf.upfronthosting.co.za>
Message-ID: <1571412201.7.0.622219833136.issue22891@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 0f3187c1ce3b3ace60f6c1691dfa3d4e744f0384 by Senthil Kumaran in branch '3.8':
[3.8] bpo-27657: Fix urlparse() with numeric paths (GH-661) (#16839)
https://github.com/python/cpython/commit/0f3187c1ce3b3ace60f6c1691dfa3d4e744f0384


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22891>
_______________________________________

From report at bugs.python.org  Fri Oct 18 11:23:21 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 15:23:21 +0000
Subject: [issue754016] urlparse goes wrong with IP:port without scheme
Message-ID: <1571412201.99.0.168773896855.issue754016@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 0f3187c1ce3b3ace60f6c1691dfa3d4e744f0384 by Senthil Kumaran in branch '3.8':
[3.8] bpo-27657: Fix urlparse() with numeric paths (GH-661) (#16839)
https://github.com/python/cpython/commit/0f3187c1ce3b3ace60f6c1691dfa3d4e744f0384


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue754016>
_______________________________________

From report at bugs.python.org  Fri Oct 18 11:23:21 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 18 Oct 2019 15:23:21 +0000
Subject: [issue16932] urlparse fails at parsing "www.python.org:80/"
In-Reply-To: <1357903769.2.0.674766943444.issue16932@psf.upfronthosting.co.za>
Message-ID: <1571412201.83.0.0872218499346.issue16932@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 0f3187c1ce3b3ace60f6c1691dfa3d4e744f0384 by Senthil Kumaran in branch '3.8':
[3.8] bpo-27657: Fix urlparse() with numeric paths (GH-661) (#16839)
https://github.com/python/cpython/commit/0f3187c1ce3b3ace60f6c1691dfa3d4e744f0384


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16932>
_______________________________________

From report at bugs.python.org  Fri Oct 18 12:10:05 2019
From: report at bugs.python.org (Philippe Cloutier)
Date: Fri, 18 Oct 2019 16:10:05 +0000
Subject: [issue28937] str.split(): allow removing empty strings (when sep is
 not None)
In-Reply-To: <1481469102.15.0.255147638686.issue28937@psf.upfronthosting.co.za>
Message-ID: <1571415005.32.0.491284847056.issue28937@roundup.psfhosted.org>


Philippe Cloutier <chealer at gmail.com> added the comment:

I understood the current (only) behavior, but coming from a PHP background, I really didn't expect it. Thank you for this request, I would definitely like the ability to get behavior matching PHP's explode().

----------
nosy: +Philippe Cloutier
title: str.split(): remove empty strings when sep is not None -> str.split(): allow removing empty strings (when sep is not None)

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28937>
_______________________________________

From report at bugs.python.org  Fri Oct 18 12:26:59 2019
From: report at bugs.python.org (Philippe Cloutier)
Date: Fri, 18 Oct 2019 16:26:59 +0000
Subject: [issue28937] str.split(): allow removing empty strings (when sep is
 not None)
In-Reply-To: <1481469102.15.0.255147638686.issue28937@psf.upfronthosting.co.za>
Message-ID: <1571416019.08.0.0620604323315.issue28937@roundup.psfhosted.org>


Philippe Cloutier <chealer at gmail.com> added the comment:

I assume the "workaround" suggested by Raymond in msg282966 is supposed to read...
filter(None, str.split(sep)
... rather than filter(None, sep.split(input)).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28937>
_______________________________________

From report at bugs.python.org  Fri Oct 18 12:32:38 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 16:32:38 +0000
Subject: [issue38418] Audit event for os.system is incorrect
In-Reply-To: <1570588084.56.0.375267797277.issue38418@roundup.psfhosted.org>
Message-ID: <1571416358.6.0.142252076432.issue38418@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 5fb81420d5ad64a900940e908b546cf40f2d6807 by Miss Islington (bot) in branch '3.8':
bpo-38418: Fixes audit event for os.system to be named 'os.system' (GH-16670)
https://github.com/python/cpython/commit/5fb81420d5ad64a900940e908b546cf40f2d6807


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38418>
_______________________________________

From report at bugs.python.org  Fri Oct 18 12:33:04 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 18 Oct 2019 16:33:04 +0000
Subject: [issue38410] Possible fatal errors due to
 _PyEval_SetAsyncGen{Finalizer, Firstiter}()
In-Reply-To: <1570543574.99.0.942798410146.issue38410@roundup.psfhosted.org>
Message-ID: <1571416384.24.0.358210557484.issue38410@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

> Why this ABI is exported at all?

Great question for (probably) Yury, but it is exported and so we're stuck with it for 3.8 at least :(

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38410>
_______________________________________

From report at bugs.python.org  Fri Oct 18 12:33:39 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 18 Oct 2019 16:33:39 +0000
Subject: [issue38418] Audit event for os.system is incorrect
In-Reply-To: <1570588084.56.0.375267797277.issue38418@roundup.psfhosted.org>
Message-ID: <1571416419.67.0.806532625031.issue38418@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38418>
_______________________________________

From report at bugs.python.org  Fri Oct 18 12:46:22 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 18 Oct 2019 16:46:22 +0000
Subject: [issue38433] 2.7.17rc1 tcl/tk version regression on Windows
In-Reply-To: <1570724262.85.0.67744981479.issue38433@roundup.psfhosted.org>
Message-ID: <1571417182.39.0.364657809193.issue38433@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

What's the status of this release blocker?  Is there something that needs to be done for 2.7.17final which is imminent?

----------
nosy: +ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38433>
_______________________________________

From report at bugs.python.org  Fri Oct 18 12:48:37 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Fri, 18 Oct 2019 16:48:37 +0000
Subject: [issue38433] 2.7.17rc1 tcl/tk version regression on Windows
In-Reply-To: <1570724262.85.0.67744981479.issue38433@roundup.psfhosted.org>
Message-ID: <1571417317.43.0.949756118415.issue38433@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:

Unless this actually regresses functionality, it doesn't seem like this needs to block the release.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38433>
_______________________________________

From report at bugs.python.org  Fri Oct 18 13:19:18 2019
From: report at bugs.python.org (hai shi)
Date: Fri, 18 Oct 2019 17:19:18 +0000
Subject: [issue38465] The type of ob_exports in PyByteArrayObject become
 Py_ssize_t.
In-Reply-To: <1570978635.87.0.596564542888.issue38465@roundup.psfhosted.org>
Message-ID: <1571419158.28.0.0761006832128.issue38465@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

Thanks, Serhiy, you are right.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38465>
_______________________________________

From report at bugs.python.org  Fri Oct 18 14:30:38 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 18 Oct 2019 18:30:38 +0000
Subject: [issue38519] Internal include files missing on Windows
Message-ID: <1571423438.26.0.118785392888.issue38519@roundup.psfhosted.org>


New submission from Steve Dower <steve.dower at python.org>:

The include/internal directory is not being included in the packages published to nuget.org or the Microsoft Store.

This prevents some advanced users from being able to compile against these packages.

----------
assignee: steve.dower
components: Windows
messages: 354914
nosy: paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title: Internal include files missing on Windows
type: compile error
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38519>
_______________________________________

From report at bugs.python.org  Fri Oct 18 14:33:26 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 18 Oct 2019 18:33:26 +0000
Subject: [issue38519] Internal include files missing on Windows
In-Reply-To: <1571423438.26.0.118785392888.issue38519@roundup.psfhosted.org>
Message-ID: <1571423606.8.0.387102892222.issue38519@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

If someone wants to fix this before I do, the change goes in PC/layout/main.py to remove the filter for directories named "internal" - we shouldn't need a filter there at all now that we include everything in the distro.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38519>
_______________________________________

From report at bugs.python.org  Fri Oct 18 14:34:00 2019
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 18 Oct 2019 18:34:00 +0000
Subject: [issue38457] __package__ is None in __init__.py until an import is
 used
In-Reply-To: <1570916892.54.0.164577302417.issue38457@roundup.psfhosted.org>
Message-ID: <1571423640.15.0.820350000686.issue38457@roundup.psfhosted.org>


Change by Brett Cannon <brett at python.org>:


----------
nosy:  -brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38457>
_______________________________________

From report at bugs.python.org  Fri Oct 18 14:34:09 2019
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 18 Oct 2019 18:34:09 +0000
Subject: [issue38457] __package__ is None in __init__.py until an import is
 used
In-Reply-To: <1570916892.54.0.164577302417.issue38457@roundup.psfhosted.org>
Message-ID: <1571423649.18.0.840745460691.issue38457@roundup.psfhosted.org>


Change by Brett Cannon <brett at python.org>:


----------
nosy: +brett.cannon, eric.snow, ncoghlan

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38457>
_______________________________________

From report at bugs.python.org  Fri Oct 18 14:34:12 2019
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 18 Oct 2019 18:34:12 +0000
Subject: [issue38457] __package__ is None in __init__.py until an import is
 used
In-Reply-To: <1570916892.54.0.164577302417.issue38457@roundup.psfhosted.org>
Message-ID: <1571423652.25.0.481391829565.issue38457@roundup.psfhosted.org>


Change by Brett Cannon <brett at python.org>:


----------
nosy:  -brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38457>
_______________________________________

From report at bugs.python.org  Fri Oct 18 14:44:19 2019
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 18 Oct 2019 18:44:19 +0000
Subject: [issue38433] 2.7.17rc1 tcl/tk version regression on Windows
In-Reply-To: <1570724262.85.0.67744981479.issue38433@roundup.psfhosted.org>
Message-ID: <1571424259.36.0.823508856483.issue38433@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:

Since 8.5.19 is the version specified in the build config, that really ought to be the version we ship.  I would guess that it just didn't get rebuilt when Steve built the installer for 2.7.17rc1; should just be a matter of making sure it does for the real thing.

----------
components: +Installation, Windows
nosy: +paul.moore, steve.dower, tim.golden

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38433>
_______________________________________

From report at bugs.python.org  Fri Oct 18 15:57:16 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 18 Oct 2019 19:57:16 +0000
Subject: [issue38433] 2.7.17rc1 tcl/tk version regression on Windows
In-Reply-To: <1570724262.85.0.67744981479.issue38433@roundup.psfhosted.org>
Message-ID: <1571428636.31.0.0534755315286.issue38433@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Strange, I definitely cleaned up the externals before building 2.7.17rc1, so not sure how it ended up with the previous one.

I'll double-check later today on my build machine, but there shouldn't have to be any code changes to deal with this.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38433>
_______________________________________

From report at bugs.python.org  Fri Oct 18 16:48:15 2019
From: report at bugs.python.org (Adrien)
Date: Fri, 18 Oct 2019 20:48:15 +0000
Subject: [issue38520] There is no proper way to know if a process is the main
 one
Message-ID: <1571431695.05.0.294533702536.issue38520@roundup.psfhosted.org>


New submission from Adrien <delgan.py at gmail.com>:

Hi.

I noticed that there exists the function "threading.main_thread()", but there is no equivalent for the "multiprocessing" module.

Is there a reason for this absence?

These StackOverflow questions are related to this problem:
- https://stackoverflow.com/questions/42283265/how-to-determine-if-running-current-process-is-parent
- https://stackoverflow.com/questions/30790660/python-multiprocessing-name-of-the-main-process
- https://stackoverflow.com/questions/18216050/is-there-a-way-to-check-if-a-module-is-being-loaded-by-multiprocessing-standard

Current proposed solutions have flaws.
It's suggested to check if "current_process().name == 'MainProcess'" but anyone can re-write the name of a process with "current_process().name = 'foobar'" so this does not seem to be a reliable solution.
Another alternative is to check for the type of the process, which is different for main and child, respectively "mulitprocessing.process._MainProcess" and "multiprocessing.process.Process". This is obviously hacky as it relies on implementation detail.

What are you thoughts on adding a new "multiprocessing.main_process()" function?

----------
components: Library (Lib)
messages: 354918
nosy: Delgan
priority: normal
severity: normal
status: open
title: There is no proper way to know if a process is the main one
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38520>
_______________________________________

From report at bugs.python.org  Fri Oct 18 16:57:18 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 18 Oct 2019 20:57:18 +0000
Subject: [issue38521] Error in NormalDist.__eq__
Message-ID: <1571432238.37.0.27679322592.issue38521@roundup.psfhosted.org>


New submission from Raymond Hettinger <raymond.hettinger at gmail.com>:

The equality comparison has a typo that wasn't caught by the tests.

----------
assignee: rhettinger
components: Library (Lib)
messages: 354919
nosy: rhettinger
priority: normal
severity: normal
status: open
title: Error in NormalDist.__eq__
type: behavior
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38521>
_______________________________________

From report at bugs.python.org  Fri Oct 18 16:59:34 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 18 Oct 2019 20:59:34 +0000
Subject: [issue38521] Error in NormalDist.__eq__
In-Reply-To: <1571432238.37.0.27679322592.issue38521@roundup.psfhosted.org>
Message-ID: <1571432374.75.0.715102487183.issue38521@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
keywords: +patch
pull_requests: +16392
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16840

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38521>
_______________________________________

From report at bugs.python.org  Fri Oct 18 17:07:27 2019
From: report at bugs.python.org (Eric Snow)
Date: Fri, 18 Oct 2019 21:07:27 +0000
Subject: [issue36876] Global C variables are a problem.
In-Reply-To: <1557514902.13.0.853517754348.issue36876@roundup.psfhosted.org>
Message-ID: <1571432847.6.0.817406312671.issue36876@roundup.psfhosted.org>


Change by Eric Snow <ericsnowcurrently at gmail.com>:


----------
pull_requests: +16393
pull_request: https://github.com/python/cpython/pull/16841

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36876>
_______________________________________

From report at bugs.python.org  Fri Oct 18 17:20:40 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 18 Oct 2019 21:20:40 +0000
Subject: [issue38521] Error in NormalDist.__eq__
In-Reply-To: <1571432238.37.0.27679322592.issue38521@roundup.psfhosted.org>
Message-ID: <1571433640.39.0.868617320876.issue38521@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset 5eabec022b9a10734fcf58faad02c4d233592f64 by Raymond Hettinger in branch 'master':
bpo-38521: Fix error in NormalDist.__eq__() (GH-16840)
https://github.com/python/cpython/commit/5eabec022b9a10734fcf58faad02c4d233592f64


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38521>
_______________________________________

From report at bugs.python.org  Fri Oct 18 17:21:00 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Oct 2019 21:21:00 +0000
Subject: [issue38521] Error in NormalDist.__eq__
In-Reply-To: <1571432238.37.0.27679322592.issue38521@roundup.psfhosted.org>
Message-ID: <1571433660.74.0.59890424002.issue38521@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16394
pull_request: https://github.com/python/cpython/pull/16842

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38521>
_______________________________________

From report at bugs.python.org  Fri Oct 18 17:41:22 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 18 Oct 2019 21:41:22 +0000
Subject: [issue38521] Error in NormalDist.__eq__
In-Reply-To: <1571432238.37.0.27679322592.issue38521@roundup.psfhosted.org>
Message-ID: <1571434882.63.0.58275149326.issue38521@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset 652a1cb0e11eb7cf0040acaf121492d2a99768d9 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-38521: Fix error in NormalDist.__eq__() (GH-16840) (GH-16842)
https://github.com/python/cpython/commit/652a1cb0e11eb7cf0040acaf121492d2a99768d9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38521>
_______________________________________

From report at bugs.python.org  Fri Oct 18 17:41:38 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 18 Oct 2019 21:41:38 +0000
Subject: [issue38521] Error in NormalDist.__eq__
In-Reply-To: <1571432238.37.0.27679322592.issue38521@roundup.psfhosted.org>
Message-ID: <1571434898.47.0.0130118086137.issue38521@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38521>
_______________________________________

From report at bugs.python.org  Fri Oct 18 18:01:11 2019
From: report at bugs.python.org (=?utf-8?q?S=C3=BCmer_Cip?=)
Date: Fri, 18 Oct 2019 22:01:11 +0000
Subject: [issue38522] Py_USING_MEMORY_DEBUGGER is referenced in docs but not
 present in code
Message-ID: <1571436071.95.0.156296507321.issue38522@roundup.psfhosted.org>


New submission from S?mer Cip <sumerc at gmail.com>:

Hi all,

While trying to debug Python C extension via valgrind, I was reading the document Misc/README.valgrind and it seems there are some parts not being uptodate. There is comments comments like following:

Uncomment Py_USING_MEMORY_DEBUGGER in Objects/obmalloc.c, then rebuild Python. This define seems to be removed from the obmalloc.c file and also I am not sure if anything is using it at all. When I searched the code, only Python/dtoa.c have a reference to this define. Anyway, I have not specifically investigated the reason behind of the removal of the define but it seems it is removed somewhere between 3.3 and 3.4. I am assuming it might be related with tracemalloc maybe? 

Cheers,

----------
components: Build
messages: 354922
nosy: S?mer.Cip
priority: normal
severity: normal
status: open
title: Py_USING_MEMORY_DEBUGGER is referenced in docs but not present in code
versions: Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38522>
_______________________________________

From report at bugs.python.org  Fri Oct 18 18:01:41 2019
From: report at bugs.python.org (=?utf-8?q?S=C3=BCmer_Cip?=)
Date: Fri, 18 Oct 2019 22:01:41 +0000
Subject: [issue38522] Py_USING_MEMORY_DEBUGGER is referenced in docs but not
 present in code
In-Reply-To: <1571436071.95.0.156296507321.issue38522@roundup.psfhosted.org>
Message-ID: <1571436101.14.0.357443998847.issue38522@roundup.psfhosted.org>


Change by S?mer Cip <sumerc at gmail.com>:


----------
versions: +Python 2.7, Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38522>
_______________________________________

From report at bugs.python.org  Fri Oct 18 18:18:49 2019
From: report at bugs.python.org (David Bolen)
Date: Fri, 18 Oct 2019 22:18:49 +0000
Subject: [issue38502] regrtest: use process groups
In-Reply-To: <1571266006.89.0.625453271604.issue38502@roundup.psfhosted.org>
Message-ID: <1571437129.1.0.725612527256.issue38502@roundup.psfhosted.org>


David Bolen <db3l.net at gmail.com> added the comment:

I don't know for sure that this is the cause but both 3.x builds following this commit on my bolen-ubuntu worker (Ubuntu 18.04.3) have had test_pty crash in the first attempt, with the retry succeeding.  For example https://buildbot.python.org/all/#/builders/141/builds/2679

In spot checking, the same behavior seems to be occurring on many other non-Windows builders as well, presumably those for which it gets used.

There doesn't seem to be anything useful produced by the first crash.  Just an entry for "test_pty crashed (Exit code -1)" in the test log.

----------
nosy: +db3l

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38502>
_______________________________________

From report at bugs.python.org  Fri Oct 18 18:29:15 2019
From: report at bugs.python.org (Rob nelson)
Date: Fri, 18 Oct 2019 22:29:15 +0000
Subject: [issue38523] ignore_dangling_symlinks in shutil.copytree does not
 apply recursively
Message-ID: <1571437755.03.0.462874003253.issue38523@roundup.psfhosted.org>


New submission from Rob nelson <veaviticus at gmail.com>:

The ignore_dangling_symlinks attribute in shutil.copytree is not passed down recursively, resulting in dangling symlinks located anywhere other than the root of the source tree to raise an error.

The line causing the error for 3.9: https://github.com/python/cpython/blob/v3.8.0/Lib/shutil.py#L486

Trivial patches and an improved test case for:
3.7: https://github.com/veaviticus/cpython/commit/a662ae8a3f85380ec76ed3dfbc778aad8c5ac37a

3.8: https://github.com/veaviticus/cpython/commit/64f72c7196243bd3e2cf4136ebbb9f9ffe206750

3.9: https://github.com/veaviticus/cpython/commit/e55dd12e558443c350d241d87bf17dfc322dbfcf

----------
components: Library (Lib)
messages: 354924
nosy: veaviticus
priority: normal
severity: normal
status: open
title: ignore_dangling_symlinks in shutil.copytree does not apply recursively
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38523>
_______________________________________

From report at bugs.python.org  Fri Oct 18 18:29:43 2019
From: report at bugs.python.org (Michel Desmoulin)
Date: Fri, 18 Oct 2019 22:29:43 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571437783.01.0.393507432395.issue20443@roundup.psfhosted.org>


Michel Desmoulin <desmoulinmichel at gmail.com> added the comment:

Isn't that change breaking compat ?

I'm assuming many scripts in the wild sys.argv[0] and play with it assuming it's relative. 

I would expect such a change to be behind a flag or a __future__ import.

----------
nosy: +Michel Desmoulin

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Fri Oct 18 19:01:11 2019
From: report at bugs.python.org (David Bolen)
Date: Fri, 18 Oct 2019 23:01:11 +0000
Subject: [issue38502] regrtest: use process groups
In-Reply-To: <1571266006.89.0.625453271604.issue38502@roundup.psfhosted.org>
Message-ID: <1571439671.31.0.712523400084.issue38502@roundup.psfhosted.org>


David Bolen <db3l.net at gmail.com> added the comment:

I can recreate this manually by running regrtest.py against test_pty.  Crashes with any "-j#" option, but fine when run sequentially.  Removing the process group change avoids the crash.

With the process group change in place, the trigger point appears to be the final "os.close(master_fd)" in PtyTest.test_basic.  Commenting that out avoids the crash.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38502>
_______________________________________

From report at bugs.python.org  Fri Oct 18 19:09:05 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 18 Oct 2019 23:09:05 +0000
Subject: [issue38520] There is no proper way to know if a process is the main
 one
In-Reply-To: <1571431695.05.0.294533702536.issue38520@roundup.psfhosted.org>
Message-ID: <1571440145.75.0.784952045598.issue38520@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
nosy: +davin, pitrou

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38520>
_______________________________________

From report at bugs.python.org  Fri Oct 18 19:21:40 2019
From: report at bugs.python.org (Michael Felt)
Date: Fri, 18 Oct 2019 23:21:40 +0000
Subject: [issue36752] test multiprocessing: test_rapid_restart() crash on AIX
In-Reply-To: <1556543240.21.0.411629530832.issue36752@roundup.psfhosted.org>
Message-ID: <1571440900.55.0.789414543252.issue36752@roundup.psfhosted.org>


Michael Felt <aixtools at felt.demon.nl> added the comment:

Please let me be much more specific.

This specific bot failure is from when I ran the bot using XLC as a compiler. Because I could not solve it on my own, and did not get any hints in time (see issue35828) Since my work schedule intensified I switched the bot to use gcc - and this test failure disappeared.

Considering that the bot no longer uses XLC - it may make better sense to close this one. No AIX bots are using XLC aka vac(pp) compiler.

Should I have time, I'll look into it again as issue35828. Note also, that manually I still build using XLC and the issue rarely occurs. That is part of what makes debugging so difficult.

Michael

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36752>
_______________________________________

From report at bugs.python.org  Fri Oct 18 22:00:07 2019
From: report at bugs.python.org (Eric Snow)
Date: Sat, 19 Oct 2019 02:00:07 +0000
Subject: [issue36876] Global C variables are a problem.
In-Reply-To: <1557514902.13.0.853517754348.issue36876@roundup.psfhosted.org>
Message-ID: <1571450407.25.0.825243777258.issue36876@roundup.psfhosted.org>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:


New changeset e4c431ecf50def40eb93c3969c1e4eeaf7bf32f1 by Eric Snow in branch 'master':
bpo-36876: Re-organize the c-analyzer tool code. (gh-16841)
https://github.com/python/cpython/commit/e4c431ecf50def40eb93c3969c1e4eeaf7bf32f1


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36876>
_______________________________________

From report at bugs.python.org  Sat Oct 19 03:30:51 2019
From: report at bugs.python.org (hongweipeng)
Date: Sat, 19 Oct 2019 07:30:51 +0000
Subject: [issue38524] functools.cached_property is not supported for setattr
Message-ID: <1571470251.68.0.879446650629.issue38524@roundup.psfhosted.org>


New submission from hongweipeng <hongweichen8888 at sina.com>:

```
from functools import cached_property
def age(self):
    return 10
class A:
    def __init__(self):
        setattr(self.__class__, 'age', property(age))
        setattr(self.__class__, 'age3', cached_property(age))

    age2 = cached_property(age)

a = A()
print(a.age)    # 10
print(a.age2)   # 10
print(a.age3)   # TypeError: Cannot use cached_property instance without calling __set_name__
```
Is it expected?

----------
messages: 354929
nosy: hongweipeng
priority: normal
severity: normal
status: open
title: functools.cached_property is not supported for setattr
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38524>
_______________________________________

From report at bugs.python.org  Sat Oct 19 03:53:20 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Sat, 19 Oct 2019 07:53:20 +0000
Subject: [issue38524] functools.cached_property is not supported for setattr
In-Reply-To: <1571470251.68.0.879446650629.issue38524@roundup.psfhosted.org>
Message-ID: <1571471600.82.0.863997888996.issue38524@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

The documentation doesn't mention ``__set_name__``, but it does say that cached_property is useful for properties which are "effectively immutable".

The ``__set_name__`` error message is pretty cryptic, that seems to have something to do with this PEP:

https://www.python.org/dev/peps/pep-0487/

but why it is relevant here, I don't know. I would expect that cached_property should apply only to read-only properties.

So I think that at the very least, this needs better documentation and a better error message.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38524>
_______________________________________

From report at bugs.python.org  Sat Oct 19 04:00:52 2019
From: report at bugs.python.org (Ivan Bykov)
Date: Sat, 19 Oct 2019 08:00:52 +0000
Subject: [issue38525] Strange reversed dict behavior
Message-ID: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>


New submission from Ivan Bykov <ivan.bykov at gmail.com>:

Python 3.8.0 (tags/v3.8.0:fa919fd, Oct 14 2019, 19:37:50) [MSC v.1916 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license()" for more information.
>>> list(reversed({1: 1}))
[1]
>>> list(reversed({}))

================================ RESTART: Shell ================================
>>>

----------
components: Interpreter Core
messages: 354931
nosy: ivb
priority: normal
severity: normal
status: open
title: Strange reversed dict behavior
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 04:14:44 2019
From: report at bugs.python.org (Ned Deily)
Date: Sat, 19 Oct 2019 08:14:44 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571472884.94.0.148126359274.issue38525@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Outside of IDLE, the example causes a segfault.  With debug build of current master HEAD:

Assertion failed: (value != NULL), function dictreviter_iternext, file ../../source/Objects/dictobject.c, line 3834.

    if (d->ma_values) {
        if (i < 0) {
            goto fail;
        }
        key = DK_ENTRIES(k)[i].me_key;
        value = d->ma_values[i];
        assert (value != NULL);
    }

----------
nosy: +inada.naoki, ned.deily
type: behavior -> crash
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 04:17:05 2019
From: report at bugs.python.org (Ned Deily)
Date: Sat, 19 Oct 2019 08:17:05 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571473025.55.0.449465420077.issue38525@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Thanks for the report, by the way!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 05:17:08 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 Oct 2019 09:17:08 +0000
Subject: [issue38524] functools.cached_property is not supported for setattr
In-Reply-To: <1571470251.68.0.879446650629.issue38524@roundup.psfhosted.org>
Message-ID: <1571476628.63.0.774592258512.issue38524@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
nosy: +carljm, ncoghlan

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38524>
_______________________________________

From report at bugs.python.org  Sat Oct 19 05:23:18 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 Oct 2019 09:23:18 +0000
Subject: [issue38524] functools.cached_property is not supported for setattr
In-Reply-To: <1571470251.68.0.879446650629.issue38524@roundup.psfhosted.org>
Message-ID: <1571476998.16.0.149191606526.issue38524@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

You have to call __set_name__() if you create a cached_property dynamically outside of the class namespace.

p = cached_property(age)
p.__set_name__(cls, 'age3')
cls.age3 = p

(And setattr() is not needed here.)

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38524>
_______________________________________

From report at bugs.python.org  Sat Oct 19 05:57:29 2019
From: report at bugs.python.org (Ned Deily)
Date: Sat, 19 Oct 2019 09:57:29 +0000
Subject: [issue37285] Python 2.7 setup.py incorrectly double-joins SDKROOT
In-Reply-To: <1560536997.94.0.77736391692.issue37285@roundup.psfhosted.org>
Message-ID: <1571479049.5.0.360600837545.issue37285@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Thanks for the report and the PR (and sorry for the delay in responding).  There were several problems with building on macOS without installed header files, which is no longer supported in the most recent Xcode / Command Line Tools releases, as well as a problem specific to 2.7 which caused such builds to not find the system zlib.  All of these issues were addressed in the changes for bpo-36231 (c421c66a58a6caae30f0679d7e61411418e67cec) and bpo-19960 (da7f6dbbf52fe7074360a9eae918806da60139c5) which were merged to 2.7 a few months ago and are being released with 2.7.17. With these changes, the double-join problem your PR was correcting no longer occur.

----------
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> Support builds on macOS without installed system header files

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37285>
_______________________________________

From report at bugs.python.org  Sat Oct 19 07:47:18 2019
From: report at bugs.python.org (Alex Walters)
Date: Sat, 19 Oct 2019 11:47:18 +0000
Subject: [issue38526] zipfile.Path has the wrong method name
Message-ID: <1571485638.73.0.512747413003.issue38526@roundup.psfhosted.org>


New submission from Alex Walters <tritium-list at sdamon.com>:

https://docs.python.org/3.8/library/zipfile.html#zipfile.Path.listdir

The docs for zipfile.Path list a method named 'listdir', the closest approximation to the functionality described in the actual code is a method named 'iterdir'

----------
assignee: docs at python
components: Documentation
messages: 354936
nosy: docs at python, tritium
priority: normal
severity: normal
status: open
title: zipfile.Path has the wrong method name
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38526>
_______________________________________

From report at bugs.python.org  Sat Oct 19 08:27:36 2019
From: report at bugs.python.org (Caleb Hattingh)
Date: Sat, 19 Oct 2019 12:27:36 +0000
Subject: [issue38501] multiprocessing.Pool hangs atexit (and garbage
 collection sometimes)
In-Reply-To: <1571250674.69.0.928369483471.issue38501@roundup.psfhosted.org>
Message-ID: <1571488056.35.0.770682033146.issue38501@roundup.psfhosted.org>


Change by Caleb Hattingh <caleb.hattingh at gmail.com>:


----------
nosy: +cjrh

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38501>
_______________________________________

From report at bugs.python.org  Sat Oct 19 08:56:25 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 19 Oct 2019 12:56:25 +0000
Subject: [issue38526] zipfile.Path has the wrong method name
In-Reply-To: <1571485638.73.0.512747413003.issue38526@roundup.psfhosted.org>
Message-ID: <1571489785.45.0.252511409352.issue38526@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

This looks like a valid issue to me. The docs were added with issue36832.

----------
nosy: +jaraco, xtreak
type:  -> behavior
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38526>
_______________________________________

From report at bugs.python.org  Sat Oct 19 09:04:24 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 19 Oct 2019 13:04:24 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571490264.82.0.772354821797.issue38525@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 09:16:26 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 19 Oct 2019 13:16:26 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571490986.73.0.769139772379.issue38525@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

This issue is related to reversed dict iter.

>>> a = reversed({})
>>> next(a)
Assertion failed: (value != NULL), function dictreviter_iternext, file Objects/dictobject.c, line 3834.
[1]    1366 abort      ./python.exe

----------
nosy: +corona10

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 10:03:37 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 19 Oct 2019 14:03:37 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571493817.49.0.67384414602.issue38525@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

>>> reversed({}.items())
<dict_reverseitemiterator object at 0x106a2bc50>
>>> a = reversed({}.items())
>>> next(a)
Assertion failed: (value != NULL), function dictreviter_iternext, file Objects/dictobject.c, line 3834.
[1]    4106 abort      ./python.exe

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 10:08:58 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 19 Oct 2019 14:08:58 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571494138.43.0.921946686535.issue38525@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

Can I take look at this issue?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 10:47:05 2019
From: report at bugs.python.org (Arnon Yaari)
Date: Sat, 19 Oct 2019 14:47:05 +0000
Subject: [issue38527] configure script fails to detect "float word ordering"
 on Solaris
Message-ID: <1571496425.89.0.0695984738868.issue38527@roundup.psfhosted.org>


New submission from Arnon Yaari <wiggin15 at gmail.com>:

When running the configure script on Solaris SPARC (versions 10 and 11), the script fails with the following error:

    checking whether float word ordering is bigendian... unknown
    configure: error:

    Unknown float word ordering. You need to manually preset
    ax_cv_c_float_words_bigendian=no (or yes) according to your system.


The configure script uses "grep" on a compiled binary to see how a float variable is compiled. On Solaris, the regular "grep" command may be an old version that fails to search in a binary file. The correct command should be "ggrep" (the GNU grep).
Luckily, Python's configure script already finds this command in an earlier check:

    checking for grep that handles long lines and -e... /usr/bin/ggrep

All we have to do, then, is use the command that configure finds. i.e. replace "grep" -> "$GREP".

----------
components: Build
messages: 354941
nosy: wiggin15
priority: normal
severity: normal
status: open
title: configure script fails to detect "float word ordering" on Solaris
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38527>
_______________________________________

From report at bugs.python.org  Sat Oct 19 10:52:08 2019
From: report at bugs.python.org (Arnon Yaari)
Date: Sat, 19 Oct 2019 14:52:08 +0000
Subject: [issue38527] configure script fails to detect "float word ordering"
 on Solaris
In-Reply-To: <1571496425.89.0.0695984738868.issue38527@roundup.psfhosted.org>
Message-ID: <1571496728.64.0.626177346845.issue38527@roundup.psfhosted.org>


Change by Arnon Yaari <wiggin15 at gmail.com>:


----------
keywords: +patch
pull_requests: +16395
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16845

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38527>
_______________________________________

From report at bugs.python.org  Sat Oct 19 10:55:55 2019
From: report at bugs.python.org (hongweipeng)
Date: Sat, 19 Oct 2019 14:55:55 +0000
Subject: [issue38524] functools.cached_property is not supported for setattr
In-Reply-To: <1571470251.68.0.879446650629.issue38524@roundup.psfhosted.org>
Message-ID: <1571496955.61.0.348780117119.issue38524@roundup.psfhosted.org>


hongweipeng <hongweichen8888 at sina.com> added the comment:

Is it possible to add an attrname parameter? It is more convenient to use.

class cached_property:
    def __init__(self, func, attrname=None):
        self.attrname = attrname
        ...

cls.age3 = cached_property(age, 'age3')

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38524>
_______________________________________

From report at bugs.python.org  Sat Oct 19 10:58:30 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 Oct 2019 14:58:30 +0000
Subject: [issue38524] functools.cached_property is not supported for setattr
In-Reply-To: <1571470251.68.0.879446650629.issue38524@roundup.psfhosted.org>
Message-ID: <1571497110.4.0.212848173566.issue38524@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

See issue38517.

For now we need to better document the use of __set_name__ with cached_property.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38524>
_______________________________________

From report at bugs.python.org  Sat Oct 19 11:00:32 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 19 Oct 2019 15:00:32 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571497232.62.0.223171339814.issue38525@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
keywords: +patch
pull_requests: +16396
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16846

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 11:00:56 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 15:00:56 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571497256.05.0.841060096406.issue38525@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16397
pull_request: https://github.com/python/cpython/pull/16847

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 11:00:56 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 15:00:56 +0000
Subject: [issue30040] Speedup empty dict creation and reduce its memory usage
In-Reply-To: <1491903560.12.0.959603376514.issue30040@psf.upfronthosting.co.za>
Message-ID: <1571497256.16.0.104251304241.issue30040@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16398
pull_request: https://github.com/python/cpython/pull/16847

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30040>
_______________________________________

From report at bugs.python.org  Sat Oct 19 11:00:56 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 15:00:56 +0000
Subject: [issue33462] reversible dict
In-Reply-To: <1526009418.33.0.682650639539.issue33462@psf.upfronthosting.co.za>
Message-ID: <1571497256.38.0.598662948343.issue33462@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16399
pull_request: https://github.com/python/cpython/pull/16847

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33462>
_______________________________________

From report at bugs.python.org  Sat Oct 19 11:04:11 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 15:04:11 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571497451.52.0.333309666506.issue38525@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy: +pablogsal, remi.lapeyre
priority: normal -> critical

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 11:04:54 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 15:04:54 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571497494.49.0.696174724718.issue38525@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Wops, we made a PR at the same time, Dong-hee Na.

I will close mine :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 11:18:43 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 19 Oct 2019 15:18:43 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571498323.62.0.850759087263.issue38525@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> Wops, we made a PR at the same time, Dong-hee Na.

lol

> I will close mine :)

Oh.. thank you for giving me a chance.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 11:53:16 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 Oct 2019 15:53:16 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571500396.5.0.315458750211.issue38525@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

The proposed fix fixes a crash, but there is other bug in iterating shared dicts.

class A:
    def __init__(self, x, y):
        if x: self.x = x
        if y: self.y = y

a = A(1, 2)
print(list(iter(a.__dict__)))
print(list(reversed(a.__dict__)))
b = A(1, 0)
print(list(iter(b.__dict__)))
print(list(reversed(b.__dict__)))

With PR 16846 the last print outputs [] instead of expected ['x']. It crashes without PR 16846, so this issue is not only about empty dicts.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 12:21:51 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 19 Oct 2019 16:21:51 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571502111.01.0.0542831826838.issue38525@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> The proposed fix fixes a crash, but there is other bug in iterating shared dicts.

Yes, you are right.
But I can not work on this issue today.
(I have to finalize my paperwork by today :-()
since priority is critical if other core developers finalize this issue today. It will be okay for me.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 12:24:19 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sat, 19 Oct 2019 16:24:19 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571502259.79.0.705313164972.issue38525@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

FYI

c = A(0, 1)
print(type(c.__dict__))
print(list(iter(c.__dict__)))
print(list(reversed(c.__dict__)))

works as we expected.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 12:52:11 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 19 Oct 2019 16:52:11 +0000
Subject: [issue38514] pathlib's mkdir documentation improvement
In-Reply-To: <1571392847.0.0.675625809065.issue38514@roundup.psfhosted.org>
Message-ID: <1571503931.65.0.21759109913.issue38514@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +pitrou

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38514>
_______________________________________

From report at bugs.python.org  Sat Oct 19 13:24:54 2019
From: report at bugs.python.org (Inada Naoki)
Date: Sat, 19 Oct 2019 17:24:54 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571505894.56.0.0952972041751.issue38525@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

When dict is empty, di_pos of reverse iterator must be -1, not 0.
Additionally, di_pos must be initialized from ma_used when dict is key sharing dict.

diff --git a/Objects/dictobject.c b/Objects/dictobject.c
index 64876e0519..6c4b41700b 100644
--- a/Objects/dictobject.c
+++ b/Objects/dictobject.c
@@ -3452,10 +3452,15 @@ dictiter_new(PyDictObject *dict, PyTypeObject *itertype)
     di->di_dict = dict;
     di->di_used = dict->ma_used;
     di->len = dict->ma_used;
-    if ((itertype == &PyDictRevIterKey_Type ||
-         itertype == &PyDictRevIterItem_Type ||
-         itertype == &PyDictRevIterValue_Type) && dict->ma_used) {
+    if (itertype == &PyDictRevIterKey_Type ||
+            itertype == &PyDictRevIterItem_Type ||
+            itertype == &PyDictRevIterValue_Type) {
+        if (dict->ma_values) {
+            di->di_pos = dict->ma_used - 1;
+        }
+        else {
             di->di_pos = dict->ma_keys->dk_nentries - 1;
+        }
     }
     else {

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 13:44:21 2019
From: report at bugs.python.org (Julin)
Date: Sat, 19 Oct 2019 17:44:21 +0000
Subject: [issue38528] Docs for 2.7 version switcher still shows 3.8 as pre
Message-ID: <1571507061.36.0.813335494011.issue38528@roundup.psfhosted.org>


New submission from Julin <julinshaji02 at gmail.com>:

The version switcher in the docs for Python2.7 still shows version 3.8 as `pre (3.8)`. Can we change it to `3.8.0` to mirror that in docs of 3.8?

Also, 2.7 docs version switcher at the moment show `dev (3.9)` for 3.9 whereas the 3.8 docs say `3.9.0a0` can it be changed as well?

----------
assignee: docs at python
components: Documentation
messages: 354950
nosy: docs at python, ju-sh
priority: normal
severity: normal
status: open
title: Docs for 2.7 version switcher still shows 3.8 as pre
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38528>
_______________________________________

From report at bugs.python.org  Sat Oct 19 13:52:35 2019
From: report at bugs.python.org (Julin)
Date: Sat, 19 Oct 2019 17:52:35 +0000
Subject: [issue38528] Docs for 2.7 version switcher still shows 3.8 as pre
In-Reply-To: <1571507061.36.0.813335494011.issue38528@roundup.psfhosted.org>
Message-ID: <1571507555.38.0.895318436981.issue38528@roundup.psfhosted.org>


Julin <julinshaji02 at gmail.com> added the comment:

A PR (16848) has been opened now for the change for pre (3.8) to `3.8.0`. Is the same acceptable for `3.9`?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38528>
_______________________________________

From report at bugs.python.org  Sat Oct 19 14:00:19 2019
From: report at bugs.python.org (Ned Deily)
Date: Sat, 19 Oct 2019 18:00:19 +0000
Subject: [issue38528] Docs for 2.7 version switcher still shows 3.8 as pre
In-Reply-To: <1571507061.36.0.813335494011.issue38528@roundup.psfhosted.org>
Message-ID: <1571508019.53.0.646339724968.issue38528@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

Thanks for thre report.  I overlooked 2.7 when updating the version switcher; the change will appear over the next 24 hours or so as the on-line docs get fully rebuilt.

> Also, 2.7 docs version switcher at the moment show `dev (3.9)` for 3.9 whereas the 3.8 docs say `3.9.0a0` can it be changed as well?

That's not quite accurate.  Only the 3.9 version of the documents show 3.9.0a0, not from any of the other versions; just as only the 3.8 version of the docs build shows 3.8.0 etc. That's an artifact of how the docs are built; we don't do anything to update the specific version.  Compare the version switchers for:

https://docs.python.org/3.7/
https://docs.python.org/3.8/
https://docs.python.org/3.9/

I don't that's worth trying to change.

> A PR (16848) has been opened now for the change for pre (3.8) to `3.8.0`.

No, it changes it to "3.8".  As noted above, only the 3.8 version of the docs when built will show the current 3.8.x release number.

----------
nosy: +ned.deily
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38528>
_______________________________________

From report at bugs.python.org  Sat Oct 19 14:40:29 2019
From: report at bugs.python.org (Ron Frederick)
Date: Sat, 19 Oct 2019 18:40:29 +0000
Subject: [issue38529] Python 3.8 improperly warns about closing properly
 closed streams
Message-ID: <1571510429.0.0.996597968813.issue38529@roundup.psfhosted.org>


New submission from Ron Frederick <ronf at timeheart.net>:

In testing AsyncSSH against Python 3.8, I noticed a large number of the following errors, even though I was properly closing streams before the objects holding them were garbage-collected.

    An open stream object is being garbage collected; call "stream.close()" explicitly.

After some investigation, the problem appears to be that closing a stream is not good enough to prevent the error. The check in asyncio doesn't properly handle the case where the stream is closing, but has not fully closed. Here's a simple test program that demonstrates this:

import asyncio

async def tcp_client():
    reader, writer = await asyncio.open_connection('127.0.0.1', 22)

    writer.close()

asyncio.run(tcp_client())

It's possible to avoid this message by awaiting on writer.wait_closed(), but wait_closed() doesn't exist until Python 3.7, making it very difficult to write portable code and still avoid this message.

----------
components: asyncio
messages: 354953
nosy: Ron Frederick, asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: Python 3.8 improperly warns about closing properly closed streams
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38529>
_______________________________________

From report at bugs.python.org  Sat Oct 19 14:57:31 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 18:57:31 +0000
Subject: [issue38530] Offer suggestions on AttributeError
Message-ID: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>


New submission from Pablo Galindo Salgado <pablogsal at gmail.com>:

To improve the debugging experience in both interactive and non-interactive code, I propose to offer suggestions when attribute access fails. For example:

>>> class A: foo = None
... 
>>> A.fou
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: type object 'A' has no attribute 'fou'

Did you mean: foo?

This also applies to imports from modules and other situations:

>>> import collections
>>> collections.NamedTuple
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module 'collections' has no attribute 'NamedTuple'

Did you mean: namedtuple?

----------
components: Interpreter Core
messages: 354954
nosy: pablogsal
priority: normal
severity: normal
status: open
title: Offer suggestions on AttributeError
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 14:58:15 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 18:58:15 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571511495.22.0.181969595953.issue38530@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +patch
pull_requests: +16400
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16850

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 15:00:16 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 19:00:16 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571511616.38.0.0210405110524.issue38530@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy: +serhiy.storchaka, vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 15:00:42 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 19:00:42 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571511642.46.0.353577983627.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

PR 16850 shows an initial prototype for the idea

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 15:01:04 2019
From: report at bugs.python.org (Batuhan)
Date: Sat, 19 Oct 2019 19:01:04 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571511664.67.0.82623236152.issue38530@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

It already exists as a 3rd party module and it would be really cool to have this in core level.

https://github.com/dutc/didyoumean (by James Powell)

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 15:02:27 2019
From: report at bugs.python.org (Batuhan)
Date: Sat, 19 Oct 2019 19:02:27 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571511747.44.0.427760453255.issue38530@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


----------
nosy: +james

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 15:12:59 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 19 Oct 2019 19:12:59 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571512379.9.0.821490155048.issue38530@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 15:22:24 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 19:22:24 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571512944.86.0.960546024076.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I am not super convinced that this is a great idea because it has some performance cost (although somewhat controlled) but I want to open a discussion.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 15:23:19 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 19 Oct 2019 19:23:19 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571512999.43.0.18793829968.issue38530@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Ruby has it integrated into the core : https://bugs.ruby-lang.org/issues/11252 . It was initially a gem that got merged into core.

> methosd
undefined local variable or method `methosd' for main:Object
Did you mean?  methods
               method
(repl):1:in `<main>'

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 15:23:31 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 19:23:31 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571513011.73.0.379109198934.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Idea: we could only do this in interactive mode if we consider that is expensive enough.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 15:25:09 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 19:25:09 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571513109.29.0.532201829994.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I am running pyperformance to check the performance cost of this.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 16:01:11 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 20:01:11 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571515271.63.0.669961761786.issue38525@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 24dc2f8c56697f9ee51a4887cf0814b6600c1815 by Pablo Galindo (Dong-hee Na) in branch 'master':
bpo-38525: Fix a segmentation fault when using reverse iterators of empty dict (GH-16846)
https://github.com/python/cpython/commit/24dc2f8c56697f9ee51a4887cf0814b6600c1815


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 16:01:33 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 19 Oct 2019 20:01:33 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571515293.66.0.053578827089.issue38525@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16401
pull_request: https://github.com/python/cpython/pull/16853

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 16:14:43 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 20:14:43 +0000
Subject: [issue38520] There is no proper way to know if a process is the main
 one
In-Reply-To: <1571431695.05.0.294533702536.issue38520@roundup.psfhosted.org>
Message-ID: <1571516083.72.0.123269334494.issue38520@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38520>
_______________________________________

From report at bugs.python.org  Sat Oct 19 16:20:59 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 19 Oct 2019 20:20:59 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571516459.05.0.451783391576.issue38525@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset d73205d788a32148ba9a2beaa27badbd94ab65ff by Miss Islington (bot) in branch '3.8':
bpo-38525: Fix a segmentation fault when using reverse iterators of empty dict (GH-16846)
https://github.com/python/cpython/commit/d73205d788a32148ba9a2beaa27badbd94ab65ff


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 16:23:30 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 20:23:30 +0000
Subject: [issue38525] Strange reversed dict behavior
In-Reply-To: <1571472052.75.0.136395293008.issue38525@roundup.psfhosted.org>
Message-ID: <1571516610.49.0.209638906703.issue38525@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Closing this.

Thanks, Dong-hee Na and everyone involved in the issue!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38525>
_______________________________________

From report at bugs.python.org  Sat Oct 19 16:45:21 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 20:45:21 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571517921.49.0.0560236424272.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Slower (27):
- pathlib: 25.2 ms +- 0.4 ms -> 105 ms +- 2 ms: 4.18x slower (+318%)
- sympy_str: 315 ms +- 3 ms -> 500 ms +- 3 ms: 1.59x slower (+59%)
- sympy_sum: 203 ms +- 2 ms -> 286 ms +- 2 ms: 1.41x slower (+41%)
- sqlalchemy_imperative: 36.5 ms +- 0.9 ms -> 41.8 ms +- 0.8 ms: 1.14x slower (+14%)
- python_startup: 12.4 ms +- 0.1 ms -> 13.9 ms +- 0.0 ms: 1.12x slower (+12%)
- python_startup_no_site: 9.19 ms +- 0.04 ms -> 10.3 ms +- 0.0 ms: 1.12x slower (+12%)
- sympy_integrate: 24.9 ms +- 0.1 ms -> 27.6 ms +- 0.3 ms: 1.11x slower (+11%)
- scimark_sparse_mat_mult: 5.21 ms +- 0.05 ms -> 5.49 ms +- 0.06 ms: 1.05x slower (+5%)
- unpickle_list: 5.78 us +- 0.07 us -> 6.08 us +- 0.07 us: 1.05x slower (+5%)
- 2to3: 392 ms +- 2 ms -> 411 ms +- 10 ms: 1.05x slower (+5%)
- nbody: 155 ms +- 2 ms -> 160 ms +- 2 ms: 1.03x slower (+3%)
- scimark_fft: 423 ms +- 2 ms -> 432 ms +- 3 ms: 1.02x slower (+2%)
- float: 142 ms +- 2 ms -> 145 ms +- 2 ms: 1.02x slower (+2%)
- unpack_sequence: 68.6 ns +- 2.5 ns -> 69.9 ns +- 2.1 ns: 1.02x slower (+2%)
- pickle_list: 5.65 us +- 0.05 us -> 5.76 us +- 0.07 us: 1.02x slower (+2%)
- fannkuch: 569 ms +- 3 ms -> 579 ms +- 6 ms: 1.02x slower (+2%)
- xml_etree_parse: 196 ms +- 2 ms -> 199 ms +- 2 ms: 1.02x slower (+2%)
- sqlalchemy_declarative: 210 ms +- 2 ms -> 213 ms +- 3 ms: 1.01x slower (+1%)
- unpickle: 16.9 us +- 0.1 us -> 17.2 us +- 0.7 us: 1.01x slower (+1%)
- regex_effbot: 3.93 ms +- 0.12 ms -> 3.97 ms +- 0.04 ms: 1.01x slower (+1%)
- scimark_monte_carlo: 128 ms +- 2 ms -> 129 ms +- 2 ms: 1.01x slower (+1%)
- scimark_lu: 186 ms +- 5 ms -> 188 ms +- 6 ms: 1.01x slower (+1%)
- regex_dna: 272 ms +- 1 ms -> 274 ms +- 1 ms: 1.01x slower (+1%)
- xml_etree_iterparse: 130 ms +- 2 ms -> 131 ms +- 3 ms: 1.01x slower (+1%)
- genshi_xml: 74.3 ms +- 0.8 ms -> 74.8 ms +- 0.8 ms: 1.01x slower (+1%)
- regex_v8: 29.7 ms +- 0.3 ms -> 29.9 ms +- 0.2 ms: 1.01x slower (+1%)
- mako: 19.3 ms +- 0.3 ms -> 19.4 ms +- 0.2 ms: 1.01x slower (+1%)


The current approach is too expensive, so I'm closing PR 16850.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 16:56:01 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 Oct 2019 20:56:01 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571518561.18.0.845747919098.issue38530@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

AFAIK there is existing issue for this idea.

I have doubts about performance. I added _PyObject_LookupAttr in particularly to avoid an overhead of raising and silencing an AttributeError. I believe most performance sensitive code in the core now uses it and will not be affected, but there is other code which silences it (_PyObject_LookupAttr itself silences an AttributeError raised in called functions), third-party code which uses PyObject_HasAttr or PyObject_GetAttr can be affected.

It might be simpler to implement it in sys.excepthook or sys.displayhook, but at that point we do not have attribute name and a reference to the object. There is an issues and a PEP about adding references to AttributeError. It could help to implement this feature.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 16:59:52 2019
From: report at bugs.python.org (Christoph Zwerschke)
Date: Sat, 19 Oct 2019 20:59:52 +0000
Subject: [issue38531] argparse action "extend" not documented as new
Message-ID: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>


New submission from Christoph Zwerschke <cito at online.de>:

A new action "extend" has been added to argparse in https://github.com/python/cpython/commit/aa32a7e1116f7aaaef9fec453db910e90ab7b101

The documentation should specify that this is new in Python 3.8 addition. I wondered why it didn't work in Python 3.7.

----------
assignee: docs at python
components: Documentation
messages: 354966
nosy: cito, docs at python
priority: normal
severity: normal
status: open
title: argparse action "extend" not documented as new
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:04:48 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 Oct 2019 21:04:48 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571519088.78.0.636840302146.issue38530@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I am surprised that it was SO expensive.

Pathlib would largely benefit from cached_property if it be compatible with slots.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:05:20 2019
From: report at bugs.python.org (Steve Dower)
Date: Sat, 19 Oct 2019 21:05:20 +0000
Subject: [issue38433] 2.7.17rc1 tcl/tk version regression on Windows
In-Reply-To: <1570724262.85.0.67744981479.issue38433@roundup.psfhosted.org>
Message-ID: <1571519120.89.0.160713353108.issue38433@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Confirmed that it was a failed clean/rebuild on my build machine. The current build for 2.7.17 has the newer version.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38433>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:10:19 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 21:10:19 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571519419.63.0.326062072487.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Serhiy, do you think we could attach the object and the name to some private fields of the AttributeError and check that in sys.excepthook if they are present?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:15:02 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 21:15:02 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571519702.65.0.699049216286.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I will also repeat the pyperformance results locally just in case something was off on the speed.python.org server.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:16:43 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 Oct 2019 21:16:43 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571519803.05.0.731286545303.issue38530@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Why private? They should be public.

But the problem is that making a reference to the object we can prolong its lifetime and even create a reference loop. There was a proposition to create a weak reference, but not all types support weak reference.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:19:39 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 21:19:39 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571519979.51.0.795243371473.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

> Why private? They should be public.

I was suggesting orivate for now until the/a PEP to modify the exception is approved. In this way we could try to implement the feature that way.

------

On the other hand do you see any way to make the current approach not that slow? Maybe activating it only on interactive mode?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:21:50 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 Oct 2019 21:21:50 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571520110.59.0.147783053153.issue38530@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

See issue18156, issue22716 and PEP 473.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:24:13 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 21:24:13 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571520253.69.0.404134446189.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

> But the problem is that making a reference to the object we can prolong its lifetime and even create a reference loop.

If I'm not mistaken, as long as the traceback is alive, the object is alive beacuse the frames will contain it. The other case is if the exception is not propagated, but in that case it should just die unless explicitly captured. There is a link you can find to previous discussions?

The cycle only happens if the object has a reference to the exception, and that should not happen in the general case.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:24:49 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 21:24:49 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571520289.19.0.185365270487.issue38530@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
Removed message: https://bugs.python.org/msg354974

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:28:04 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 21:28:04 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571520484.72.0.375885027896.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

> But the problem is that making a reference to the object we can prolong its lifetime and even create a reference loop.

If I'm not mistaken, as long as the traceback is alive, the object is alive beacuse the frames will contain it. The other case is if the exception is not propagated, but in that case it should just die unless explicitly captured. 

The cycle only happens if the object has a reference to the exception, and that should not happen in the general case.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:33:44 2019
From: report at bugs.python.org (Steve Dower)
Date: Sat, 19 Oct 2019 21:33:44 +0000
Subject: [issue31202] Windows pathlib.Path.glob(pattern) fixed part of the
 pattern changed to lowercase whereas it should be unchanged.
In-Reply-To: <1502719052.2.0.11123711046.issue31202@psf.upfronthosting.co.za>
Message-ID: <1571520824.23.0.11385819975.issue31202@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Bumping this - it's bitten me a couple of times as one of the build/release scripts relies on Path.glob().

----------
versions: +Python 3.9 -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31202>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:38:43 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 19 Oct 2019 21:38:43 +0000
Subject: [issue12022] AttributeError should report the same details when
 raised by lookup_special() as when raised in the REPL
In-Reply-To: <1304712442.84.0.0469522790948.issue12022@psf.upfronthosting.co.za>
Message-ID: <1571521123.21.0.857276223482.issue12022@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Would not be better to change an AttributeError to TypeError? Seems this is the only place in the core when missing special method causes an AttributeError and not TypeError.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12022>
_______________________________________

From report at bugs.python.org  Sat Oct 19 17:44:14 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 19 Oct 2019 21:44:14 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571521454.04.0.501703105455.issue37759@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
pull_requests: +16402
pull_request: https://github.com/python/cpython/pull/16854

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Sat Oct 19 18:49:35 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Sat, 19 Oct 2019 22:49:35 +0000
Subject: [issue38395] proxy_contains (weakref.proxy) can access an object with
 0 refcount
In-Reply-To: <1570459749.44.0.879317891234.issue38395@roundup.psfhosted.org>
Message-ID: <1571525375.71.0.343059443349.issue38395@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:

All fixed now, right?

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38395>
_______________________________________

From report at bugs.python.org  Sat Oct 19 19:12:53 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 23:12:53 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571526773.77.0.799138274415.issue38530@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
pull_requests: +16403
pull_request: https://github.com/python/cpython/pull/16856

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 19:15:25 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sat, 19 Oct 2019 23:15:25 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571526925.55.0.213277900545.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I have opened PR 16856 adding fields to the AttributeError and implementing the feature in PyErr_Display.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sat Oct 19 20:25:32 2019
From: report at bugs.python.org (Caleb Hattingh)
Date: Sun, 20 Oct 2019 00:25:32 +0000
Subject: [issue38529] Python 3.8 improperly warns about closing properly
 closed streams
In-Reply-To: <1571510429.0.0.996597968813.issue38529@roundup.psfhosted.org>
Message-ID: <1571531132.25.0.0068353396598.issue38529@roundup.psfhosted.org>


Change by Caleb Hattingh <caleb.hattingh at gmail.com>:


----------
nosy: +cjrh

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38529>
_______________________________________

From report at bugs.python.org  Sat Oct 19 22:51:28 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Sun, 20 Oct 2019 02:51:28 +0000
Subject: [issue38532] Missing decrefs in the _ctypes module
Message-ID: <1571539888.18.0.273531379045.issue38532@roundup.psfhosted.org>


New submission from Zackery Spytz <zspytz at gmail.com>:

In PyCFuncPtr_FromDll(), there are two missing calls to Py_DECREF() if PySys_Audit() fails!

----------
components: Extension Modules
messages: 354980
nosy: ZackerySpytz
priority: normal
severity: normal
status: open
title: Missing decrefs in the _ctypes module
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38532>
_______________________________________

From report at bugs.python.org  Sat Oct 19 22:55:04 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Sun, 20 Oct 2019 02:55:04 +0000
Subject: [issue38532] Missing decrefs in the _ctypes module
In-Reply-To: <1571539888.18.0.273531379045.issue38532@roundup.psfhosted.org>
Message-ID: <1571540104.36.0.252562075794.issue38532@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
keywords: +patch
pull_requests: +16404
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16857

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38532>
_______________________________________

From report at bugs.python.org  Sat Oct 19 23:11:46 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 20 Oct 2019 03:11:46 +0000
Subject: [issue38531] argparse action "extend" not documented as new
In-Reply-To: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>
Message-ID: <1571541106.43.0.877763309461.issue38531@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +paul.j3, rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sat Oct 19 23:22:55 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 20 Oct 2019 03:22:55 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1571541775.13.0.854420773033.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

With the new approach, there is no measurable different in performance:

venv ? pyperf compare_to json/2019-10-19_20-01-master-24dc2f8c5669.json.gz json/2019-10-20_01-32-suggestions2-21404456383b.json.gz -G

Slower (3):
- 2to3: 400 ms +- 2 ms -> 405 ms +- 3 ms: 1.01x slower (+1%)
- sqlite_synth: 3.46 us +- 0.08 us -> 3.50 us +- 0.08 us: 1.01x slower (+1%)
- nqueens: 121 ms +- 1 ms -> 121 ms +- 1 ms: 1.01x slower (+1%)

Faster(4):
- hexiom: 11.9 ms +- 0.1 ms -> 11.8 ms +- 0.1 ms: 1.01x faster (-1%)
- xml_etree_generate: 113 ms +- 2 ms -> 113 ms +- 2 ms: 1.01x faster (-1%)
- python_startup_no_site: 9.25 ms +- 0.06 ms -> 9.20 ms +- 0.01 ms: 1.01x faster (-1%)
- go: 317 ms +- 4 ms -> 315 ms +- 3 ms: 1.01x faster (-1%)
- sympy_integrate: 25.1 ms +- 0.2 ms -> 25.0 ms +- 0.1 ms: 1.01x faster (-1%)


Benchmark hidden because not significant (57): chameleon, chaos, crypto_pyaes, deltablue, dulwich_log, fannkuch, float, genshi_text, genshi_xml, json_dumps, json_loads, logging_format, logging_silent, logging_simple, mako, meteor_contest, nbody, pathlib, pickle, pickle_dict, pickle_list, pickle_pure_python, pidigits, python_startup, raytrace, regex_compile, regex_dna, regex_effbot, regex_v8, richards, scimark_fft, scimark_lu, scimark_monte_carlo, scimark_sor, scimark_sparse_mat_mult, spectral_norm, sqlalchemy_declarative, sqlalchemy_imperative, sympy_expand, sympy_sum, sympy_str, telco, unpack_sequence, unpickle, unpickle_list, unpickle_pure_python, xml_etree_parse, xml_etree_iterparse, xml_etree_process

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sun Oct 20 00:31:43 2019
From: report at bugs.python.org (Jon)
Date: Sun, 20 Oct 2019 04:31:43 +0000
Subject: [issue38533] py script runs with python.exe but not pythonw.exe
 (python console)
Message-ID: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>


New submission from Jon <yourbestfriendjax at gmail.com>:

3.7.5.  Any py script that I run with python.exe or py.exe executes just fine.  But if I try to run any py script with pythonW.exe or pyW.exe it will not run.  

I don't know where the logging for the python executable is located.

On the same machine, java.exe and javaW.exe work properly. (jar file runs exactly the same with either executable.  Only the cmd/console window is suppressed with "w" exe.



I am trying to isolate whether or not python 3.7.5 is to blame or this new windows 10 x64 1809 LTSC machine is to blame.

I have tested in both python 3.7.5 x86 and x64 versions.  the "W" console version does not run any py scripts.

On my previous laptop (win 8.1 x64) and (win2012 r2 x64 server, no problems) with 3.7.4 32 bit.

---

How do I have multiple MINOR versions of python together?  e.g. 3.7.3, 3.7.4, 3.7.5?  Can they be placed in separate folders?

----------
components: Windows
messages: 354982
nosy: 4evermaat, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: py script runs with python.exe but not pythonw.exe (python console)
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Sun Oct 20 00:50:36 2019
From: report at bugs.python.org (Jon)
Date: Sun, 20 Oct 2019 04:50:36 +0000
Subject: [issue38533] py script runs with python.exe but not pythonw.exe
 (python console)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571547036.9.0.133682505945.issue38533@roundup.psfhosted.org>


Jon <yourbestfriendjax at gmail.com> added the comment:

by the way, just to be sure, I am actually running the python.exe / py.exe / pythonw.exe / pyw.exe from the full file path just to be sure.  e.g.

%LOCALAPPDATA%\Programs\Python\Launcher\pyw.exe  test.py

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Sun Oct 20 00:53:46 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 04:53:46 +0000
Subject: [issue36321] Fix misspelled attribute name in namedtuple()
In-Reply-To: <1552767663.81.0.27756638002.issue36321@roundup.psfhosted.org>
Message-ID: <1571547226.56.0.792285440487.issue36321@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
pull_requests: +16405
pull_request: https://github.com/python/cpython/pull/16858

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36321>
_______________________________________

From report at bugs.python.org  Sun Oct 20 00:58:01 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 04:58:01 +0000
Subject: [issue38440] Possible new issues with IDLE
In-Reply-To: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>
Message-ID: <1571547481.46.0.440684718802.issue38440@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I've twice observed another bit of flakey behavior.  When editing a line in a shell session, the cursor arrow keys start emitting mac's ? special symbol character.

I'll look to see if I can find a reproducer for this as well.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Sun Oct 20 02:49:47 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 Oct 2019 06:49:47 +0000
Subject: [issue31202] Windows pathlib.Path.glob(pattern) fixed part of the
 pattern changed to lowercase whereas it should be unchanged.
In-Reply-To: <1502719052.2.0.11123711046.issue31202@psf.upfronthosting.co.za>
Message-ID: <1571554187.68.0.610280995322.issue31202@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31202>
_______________________________________

From report at bugs.python.org  Sun Oct 20 03:20:16 2019
From: report at bugs.python.org (Jon)
Date: Sun, 20 Oct 2019 07:20:16 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python console)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571556016.11.0.0781392618885.issue38533@roundup.psfhosted.org>


Jon <yourbestfriendjax at gmail.com> added the comment:

I installed v3.7.4 x86 and scripts work with `pythonw.exe` and `pyw.exe`

I also tested v3.7.4 x64 bit and scripts also work ok.  So that is some good news.

This proves that pythonw (python console) for 3.7.5 is not working for some unknown reasons.

It is not related to Win10 (thankfully, as that would be an entirely different beast)

Will revert to 3.7.4 and stick with it until further notice.

---

That's about 7 hours of my life I will not get back, but I hope it will help someone.

----------
title: py script runs with python.exe but not pythonw.exe (python console) -> v3.7.5 py script run ok with python.exe but not pythonw.exe (python console)

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Sun Oct 20 03:20:55 2019
From: report at bugs.python.org (Jon)
Date: Sun, 20 Oct 2019 07:20:55 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571556055.4.0.270495080539.issue38533@roundup.psfhosted.org>


Change by Jon <yourbestfriendjax at gmail.com>:


----------
title: v3.7.5 py script run ok with python.exe but not pythonw.exe (python console) -> v3.7.5 py script run ok with python.exe but not pythonw.exe (python console not working)

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Sun Oct 20 03:27:35 2019
From: report at bugs.python.org (Jon)
Date: Sun, 20 Oct 2019 07:27:35 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571556455.8.0.328141516576.issue38533@roundup.psfhosted.org>


Change by Jon <yourbestfriendjax at gmail.com>:


----------
title: v3.7.5 py script run ok with python.exe but not pythonw.exe (python console not working) -> v3.7.5 py script run ok with python.exe but not pythonw.exe (python silent console not working)

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Sun Oct 20 03:59:24 2019
From: report at bugs.python.org (Wator Sead)
Date: Sun, 20 Oct 2019 07:59:24 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
Message-ID: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>


New submission from Wator Sead <seahoh at gmail.com>:

https://bugs.python.org/msg347421

Maybe you forgot it, please fix it in next versions.

----------
assignee: docs at python
components: Documentation, Installation, Windows
messages: 354986
nosy: docs at python, paul.moore, seahoh, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Version 3.8.0 has released with a wrong MS KB number reference
type: resource usage
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Sun Oct 20 04:21:37 2019
From: report at bugs.python.org (Alex Hall)
Date: Sun, 20 Oct 2019 08:21:37 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
Message-ID: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>


New submission from Alex Hall <alex.mojaki at gmail.com>:

In a decorator such as `@a()`, the ast.Call node has a col_offset starting from the @ symbol. This doesn't happen for decorators without arguments (e.g. `@a`) or with some arguments (e.g. `@a(x)`).

----------
components: Interpreter Core
files: decorator_python_bug.py
messages: 354987
nosy: alexmojaki
priority: normal
severity: normal
status: open
title: Incorrect col_offset for decorators with zero arguments (empty parentheses)
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8
Added file: https://bugs.python.org/file48669/decorator_python_bug.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sun Oct 20 04:23:14 2019
From: report at bugs.python.org (Alex Hall)
Date: Sun, 20 Oct 2019 08:23:14 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1571559794.2.0.460322632934.issue38535@roundup.psfhosted.org>


Alex Hall <alex.mojaki at gmail.com> added the comment:

I assume this also happens on 3.9, it's just a bit hard for me to test that now.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sun Oct 20 04:58:32 2019
From: report at bugs.python.org (Jonas Aschenbrenner)
Date: Sun, 20 Oct 2019 08:58:32 +0000
Subject: [issue38536] Trailing space in formatted currency with
 international=True and locale de_DE
Message-ID: <1571561912.94.0.419750510226.issue38536@roundup.psfhosted.org>


New submission from Jonas Aschenbrenner <jonas.aschenbrenner at gmail.com>:

>>> import locale
>>> locale.setlocale(locale.LC_ALL, ('de_DE', 'UTF-8'))
'de_DE.UTF-8'
>>> locale.currency(1345345345352.22, international=True)
'1345345345352,22 EUR '

Expected: '1345345345352,22 EUR'

----------
components: Library (Lib)
messages: 354989
nosy: Jonas Aschenbrenner
priority: normal
severity: normal
status: open
title: Trailing space in formatted currency with international=True and locale de_DE
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38536>
_______________________________________

From report at bugs.python.org  Sun Oct 20 04:59:13 2019
From: report at bugs.python.org (Jonas Aschenbrenner)
Date: Sun, 20 Oct 2019 08:59:13 +0000
Subject: [issue38536] Trailing space in formatted currency with
 international=True and locale de_DE
In-Reply-To: <1571561912.94.0.419750510226.issue38536@roundup.psfhosted.org>
Message-ID: <1571561953.33.0.704006711498.issue38536@roundup.psfhosted.org>


Change by Jonas Aschenbrenner <jonas.aschenbrenner at gmail.com>:


----------
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38536>
_______________________________________

From report at bugs.python.org  Sun Oct 20 05:06:11 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 Oct 2019 09:06:11 +0000
Subject: [issue31202] Windows pathlib.Path.glob(pattern) fixed part of the
 pattern changed to lowercase whereas it should be unchanged.
In-Reply-To: <1502719052.2.0.11123711046.issue31202@psf.upfronthosting.co.za>
Message-ID: <1571562371.13.0.601256909717.issue31202@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16406
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16860

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31202>
_______________________________________

From report at bugs.python.org  Sun Oct 20 05:27:59 2019
From: report at bugs.python.org (SilentGhost)
Date: Sun, 20 Oct 2019 09:27:59 +0000
Subject: [issue38536] Trailing space in formatted currency with
 international=True and symbol following value
In-Reply-To: <1571561912.94.0.419750510226.issue38536@roundup.psfhosted.org>
Message-ID: <1571563679.29.0.910251252105.issue38536@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

This isn't just de_DE locale, but any locale that puts currency symbol after the value. This issue is even "acknowledged" in the test. I'd think that appropriate fix would be to .rstrip smb on line Lib/locale.py:282
Alternatively, function return value could be stripped.

----------
nosy: +SilentGhost, lemburg, twouters
stage:  -> needs patch
title: Trailing space in formatted currency with international=True and locale de_DE -> Trailing space in formatted currency with international=True and symbol following value
versions: +Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38536>
_______________________________________

From report at bugs.python.org  Sun Oct 20 05:51:10 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 Oct 2019 09:51:10 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1571565070.22.0.101101031631.issue38535@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16407
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16861

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sun Oct 20 05:52:13 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 Oct 2019 09:52:13 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1571565133.38.0.869705441594.issue38535@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
versions: +Python 3.9 -Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sun Oct 20 06:56:06 2019
From: report at bugs.python.org (Paul Moore)
Date: Sun, 20 Oct 2019 10:56:06 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571568966.27.0.209338814622.issue38533@roundup.psfhosted.org>


Paul Moore <p.f.moore at gmail.com> added the comment:

Can you give an example of a script that fails? If you try to print (or otherwise use the standard IO streams) pythonw will fail, because there are no stdio streams for a GUI executable - and the traceback, which goes to stderr by default, will be lost.

This is my best guess as to your issue here, but without a reproducible example, it's hard to say anything useful.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Sun Oct 20 07:14:25 2019
From: report at bugs.python.org (Amir Mohamadi)
Date: Sun, 20 Oct 2019 11:14:25 +0000
Subject: [issue38536] Trailing space in formatted currency with
 international=True and symbol following value
In-Reply-To: <1571561912.94.0.419750510226.issue38536@roundup.psfhosted.org>
Message-ID: <1571570065.32.0.561373165288.issue38536@roundup.psfhosted.org>


Amir Mohamadi <amiremohamadi at yahoo.com> added the comment:

Hi!
I'm a newbie.
Can I work on it with your help???

----------
nosy: +Amir

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38536>
_______________________________________

From report at bugs.python.org  Sun Oct 20 07:23:40 2019
From: report at bugs.python.org (Jon)
Date: Sun, 20 Oct 2019 11:23:40 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571570620.21.0.144933669766.issue38533@roundup.psfhosted.org>


Jon <yourbestfriendjax at gmail.com> added the comment:

@paul.moore  all scripts failed.  it's like pyw.exe does not run at all (or quits shortly after.  i have about 5 proprietary scripts.

going back to 3.7.4 everything works as before.   I do suspect there is something wrong with the way that 3.7.5 was compiled for pythonW.exe


 python/pw.exe works fine for both 3.7.4 and 3.7.5 (x86 and x64 versions)
pythonW/pyW.exe works fine for 3.7.4 but not 3.7.5 (x86 and x64 versions)

This is the first time i've ever had this issue.  python 3.6.x.

I originally thought it was a win10 issue because I am setting up a new computer and using 3.7.5 for the first time.  (other computer had 3.7.4).

I will ask my programmer to give some sample code.  But really any existing script you have should work for testing 3.7.5 pythonw.exe , particularly if it requires a couple of non-core modules to run.

Let me know if you are unable to reproduce it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Sun Oct 20 08:26:38 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2019 12:26:38 +0000
Subject: [issue30672] PEP 538: Unexpected locale behaviour on *BSD (including
 Mac OS X)
In-Reply-To: <1497518633.36.0.998856107706.issue30672@psf.upfronthosting.co.za>
Message-ID: <1571574398.28.0.7198777961.issue30672@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

There are a couple of cases that the C locale coercion tests skip because I don't (or didn't) know what they *should* do:

* https://github.com/python/cpython/blob/24dc2f8c56697f9ee51a4887cf0814b6600c1815/Lib/test/test_c_locale_coercion.py#L262 (skips the "LANG=UTF-8" test)
* https://github.com/python/cpython/blob/24dc2f8c56697f9ee51a4887cf0814b6600c1815/Lib/test/test_c_locale_coercion.py#L37 (only adds "POSIX" to the expected C locale equivalents list on non-Android Linux systems)

With the interpreter explicitly checking for "POSIX" now, at least the latter special case could potentially be removed, with "POSIX" just always being part of the EXPECTED_C_LOCALE_EQUIVALENTS list. (It was only removed because it used to break on FreeBSD and Mac OS X)

I don't think we ever figured out why the "LANG=UTF-8" case didn't work the way we expected, so I suspect where going to need to keep that skip for now.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30672>
_______________________________________

From report at bugs.python.org  Sun Oct 20 08:27:26 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2019 12:27:26 +0000
Subject: [issue30672] PEP 538: Unexpected locale behaviour on *BSD (including
 Mac OS X)
In-Reply-To: <1497518633.36.0.998856107706.issue30672@psf.upfronthosting.co.za>
Message-ID: <1571574446.35.0.581774299332.issue30672@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

(Removed the patch keyword, as the linked PR was for an old change that didn't cover the remaining test issues)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30672>
_______________________________________

From report at bugs.python.org  Sun Oct 20 08:45:48 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2019 12:45:48 +0000
Subject: [issue32856] Optimize the `for y in [x]` idiom in comprehensions
In-Reply-To: <1518770483.24.0.467229070634.issue32856@psf.upfronthosting.co.za>
Message-ID: <1571575548.97.0.110405470353.issue32856@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

The benefit offered by the parent local scoping was that it made assignment expressions usable as a straightforward way to implement comprehension-based accumulators where you actually do want access to the final value after the comprehension completes (for example, pulling the example or counter-example out of a call to any() or all()).

The downside is that you need an explicit "del j" after the comprehension to ensure prompt cleanup in those cases where you *don't* need the temporary variable after the comprehension has finished running:

    >>> [(j:=i*i)+1/j for i in range(1, 3)]; del j # Clean up temp

However, that's still going to be clearer to most readers than writing:

    [j+1/j for i in range(1, 3) for j in [i*i]]

So even with the parent local scoping semantics, PEP 572 is still enough to make Yury's comment above still hold (i.e. the use case is too obscure to justify the extra code needed to optimise it)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32856>
_______________________________________

From report at bugs.python.org  Sun Oct 20 08:51:18 2019
From: report at bugs.python.org (PEW's Corner)
Date: Sun, 20 Oct 2019 12:51:18 +0000
Subject: [issue38537] Python 2.7.17 reports itself as 2.7.16
Message-ID: <1571575878.44.0.238301674763.issue38537@roundup.psfhosted.org>


New submission from PEW's Corner <pewscorner at gmail.com>:

After upgrading Python 2.7.16 to 2.7.17 using the Windows x86 MSI installer, the new Python still reports itself as version 2.7.16:

D:\Python27>.\python.exe
Python 2.7.16 (v2.7.16:413a49145e, Mar  4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys; sys.version_info
sys.version_info(major=2, minor=7, micro=16, releaselevel='final', serial=0)
>>>

The python.exe file is dated Oct. 19, but the python27.dll is dated Mar. 4, so doesn't seem to have been updated. Repairing or removing and reinstalling doesn't make any difference, so the old dll seems to be part of the new installation.

----------
components: Installation
messages: 354997
nosy: pewscorner
priority: normal
severity: normal
status: open
title: Python 2.7.17 reports itself as 2.7.16
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38537>
_______________________________________

From report at bugs.python.org  Sun Oct 20 08:54:00 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2019 12:54:00 +0000
Subject: [issue38457] __package__ is None in __init__.py until an import is
 used
In-Reply-To: <1570916892.54.0.164577302417.issue38457@roundup.psfhosted.org>
Message-ID: <1571576040.96.0.256382430953.issue38457@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Yes, this is a design flaw in the Python 2 import system - it derives `__package__` from `__name__` the first time it needs the information and `__package__` isn't already set.

The problem was fixed for the Python 3 series by way of PEP 451, which made substantial changes to the way module initialisation works, allowing the import system to instead derive `__package__` from `__spec__` as part of module creation.

Depending on your reasons for being interested in this, the `importlib2` package may be of interest: https://pypi.org/project/importlib2/

(Judging from the version number, Eric last updated that for Python 3.5, which means it will include the PEP 451 behaviour)

----------
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38457>
_______________________________________

From report at bugs.python.org  Sun Oct 20 09:03:55 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 20 Oct 2019 13:03:55 +0000
Subject: [issue32397] textwrap output may change if you wrap a paragraph twice
In-Reply-To: <1513865443.17.0.213398074469.issue32397@psf.upfronthosting.co.za>
Message-ID: <1571576635.83.0.738645333448.issue32397@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
versions: +Python 3.9 -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32397>
_______________________________________

From report at bugs.python.org  Sun Oct 20 09:09:00 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2019 13:09:00 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571576940.67.0.261573597148.issue20443@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

I think that's a valid point regarding sys.argv[0] - it's the import system and code introspection that wants(/needs) absolute paths, whereas sys.argv[0] gets used in situations (e.g. usage messages) where we should retain whatever the OS gave us, since that best reflects what the user entered.

That's straightforward to selectively revert, though: remove the "config->run_filename != NULL" clause at https://github.com/python/cpython/blob/24dc2f8c56697f9ee51a4887cf0814b6600c1815/Python/initconfig.c#L2201 and add a comment with the reason for the deliberate omission.


That way the OS-provided argv entry will continue to be passed through to sys.argv[0], while everywhere else will get the absolute path.

----------
versions: +Python 3.9 -Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Sun Oct 20 09:14:16 2019
From: report at bugs.python.org (PEW's Corner)
Date: Sun, 20 Oct 2019 13:14:16 +0000
Subject: [issue38537] Python 2.7.17 reports itself as 2.7.16
In-Reply-To: <1571575878.44.0.238301674763.issue38537@roundup.psfhosted.org>
Message-ID: <1571577256.71.0.567076655747.issue38537@roundup.psfhosted.org>


PEW's Corner <pewscorner at gmail.com> added the comment:

After experimenting a bit more, I found that the python27.dll is NOT part of the new installation, but is also NOT removed on upgrade or when uninstalling. After I manually deleted this dll, the new installation correctly reports itself as 2.7.17.

So the problem seems to be that the installer forgets to remove the old dll (and there is no new dll to overwrite it).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38537>
_______________________________________

From report at bugs.python.org  Sun Oct 20 09:16:19 2019
From: report at bugs.python.org (Eryk Sun)
Date: Sun, 20 Oct 2019 13:16:19 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571577379.96.0.640606574335.issue38533@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

> Let me know if you are unable to reproduce it.

x64 pythonw.exe and pyw.exe (3.7.5, 2019-10-14) work for me in Windows 10.0.18362. I have them installed for all users, respectively in "C:\Program Files\Python37" and "C:\Windows". 

Try running `pythonw.exe -m idlelib` and `pythonw.exe -m turtle`. If nothing runs, try it with python.exe, just to make sure tcl/tk and IDLE are installed.

> How do I have multiple MINOR versions of python together? 
> e.g. 3.7.3, 3.7.4, 3.7.5?  Can they be placed in separate 
> folders?

The standard distribution supports one major-version installation for the system and another per user. You can use the nuget packages to test against multiple minor versions.

https://docs.python.org/3/using/windows.html#the-nuget-org-packages

It seems that nuget packages can also be installed via PowerShell 6. However, the "Version" parameter of Visual Studio's Install-Package changes to "RequiredVersion" in PowerShell 6.

----------
nosy: +eryksun

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Sun Oct 20 09:28:24 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2019 13:28:24 +0000
Subject: [issue38524] functools.cached_property is not supported for setattr
In-Reply-To: <1571470251.68.0.879446650629.issue38524@roundup.psfhosted.org>
Message-ID: <1571578104.72.0.663959563313.issue38524@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Another interesting question this raises is whether type.__setattr__ should be checking for values that have `__set_name__` methods defined and calling those methods automatically.

Unfortunately, I think the answer to that is "If we'd thought of that when writing PEP 487, then sure, but it's too late now, as too many folks will be calling it explicitly, and implicitly calling it a second time will cause other, potentially harder to find problems".

So +1 for updating the cached_property docs specifically to mention this problem

However, I'm also wondering if there's somewhere else we should be mentioning it as a general problem.

Perhaps in the docs for __set_name__ itself, noting it as something that authors of descriptors *using* __set_name__ should mention in their docs, with suggested wording?

Something like:

===
`__set_name__`` is only called implicitly as part of the ``type`` constructor, so it will need to be called explicitly with the appropriate parameters when a descriptor is added to a class after initial creation::

    descr = custom_descriptor()
    cls.attr = descr
    descr.__set_name__(cls, 'attr')
===

(The normal sequence is for the descriptor to already be part of the class namespace before __set_name__ gets called)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38524>
_______________________________________

From report at bugs.python.org  Sun Oct 20 09:30:33 2019
From: report at bugs.python.org (Jon)
Date: Sun, 20 Oct 2019 13:30:33 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571578233.05.0.620821330062.issue38533@roundup.psfhosted.org>


Jon <yourbestfriendjax at gmail.com> added the comment:

@eryk.  Could I just have separate folder with each python minor version?  I would keep it portable and just reference the python/pythonw.exe filepath directly for each version when I run.

I could just download the 3.7.5 and drop it anywhere.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Sun Oct 20 09:30:54 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2019 13:30:54 +0000
Subject: [issue38524] functools.cached_property is not supported for setattr
In-Reply-To: <1571470251.68.0.879446650629.issue38524@roundup.psfhosted.org>
Message-ID: <1571578254.16.0.165648614697.issue38524@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Regarding the "attrname" property idea: unfortunately, that won't work, as `__set_name__` doesn't just provide the attribute name, it also provides a reference to the class itself.

cached_property needs both pieces of information, not just the attribute name.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38524>
_______________________________________

From report at bugs.python.org  Sun Oct 20 09:33:15 2019
From: report at bugs.python.org (Paul Martin)
Date: Sun, 20 Oct 2019 13:33:15 +0000
Subject: [issue38471] _ProactorDatagramTransport: If close() is called when
 write buffer is not empty,
 the remaining data is not sent and connection_lost is not called
In-Reply-To: <1571049755.46.0.456741846567.issue38471@roundup.psfhosted.org>
Message-ID: <1571578395.32.0.0881480413269.issue38471@roundup.psfhosted.org>


Change by Paul Martin <greatestloginnameever at gmail.com>:


----------
pull_requests: +16408
pull_request: https://github.com/python/cpython/pull/16863

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38471>
_______________________________________

From report at bugs.python.org  Sun Oct 20 09:34:05 2019
From: report at bugs.python.org (Jon)
Date: Sun, 20 Oct 2019 13:34:05 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571578445.08.0.185328137809.issue38533@roundup.psfhosted.org>


Jon <yourbestfriendjax at gmail.com> added the comment:

BTW, I have win10 x64 v 1809 b 17763.720.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Sun Oct 20 09:37:19 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2019 13:37:19 +0000
Subject: [issue38524] functools.cached_property is not supported for setattr
In-Reply-To: <1571470251.68.0.879446650629.issue38524@roundup.psfhosted.org>
Message-ID: <1571578639.58.0.155306074428.issue38524@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

After writing my previous comment, I double-checked the code, and cached_propery is actually one of the cases where a simple "self.attrname = 'age3'" *will* do the right thing, as cached_property never checks the class information.

That won't work in the general case though, and I think it makes more sense for the cached_property documentation to provide advice that will generalise to arbitrary descriptors (i.e. call `descr.__set_name__(target, "attr")`)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38524>
_______________________________________

From report at bugs.python.org  Sun Oct 20 10:52:18 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 20 Oct 2019 14:52:18 +0000
Subject: [issue38536] Trailing space in formatted currency with
 international=True and symbol following value
In-Reply-To: <1571561912.94.0.419750510226.issue38536@roundup.psfhosted.org>
Message-ID: <1571583138.86.0.804711151262.issue38536@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +16409
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16864

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38536>
_______________________________________

From report at bugs.python.org  Sun Oct 20 11:03:11 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 20 Oct 2019 15:03:11 +0000
Subject: [issue38537] Python 2.7.17 reports itself as 2.7.16
In-Reply-To: <1571575878.44.0.238301674763.issue38537@roundup.psfhosted.org>
Message-ID: <1571583791.54.0.758317436613.issue38537@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +benjamin.peterson, steve.dower

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38537>
_______________________________________

From report at bugs.python.org  Sun Oct 20 11:04:49 2019
From: report at bugs.python.org (SilentGhost)
Date: Sun, 20 Oct 2019 15:04:49 +0000
Subject: [issue38537] Python 2.7.17 reports itself as 2.7.16
In-Reply-To: <1571575878.44.0.238301674763.issue38537@roundup.psfhosted.org>
Message-ID: <1571583889.17.0.239514726022.issue38537@roundup.psfhosted.org>


Change by SilentGhost <ghost.adh at runbox.com>:


----------
components: +Windows
nosy: +paul.moore, tim.golden, zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38537>
_______________________________________

From report at bugs.python.org  Sun Oct 20 11:32:28 2019
From: report at bugs.python.org (Julien Palard)
Date: Sun, 20 Oct 2019 15:32:28 +0000
Subject: [issue38538] dictobject dictviews don't return NotImplemented for
 unrecognized types.
Message-ID: <1571585548.13.0.376831813762.issue38538@roundup.psfhosted.org>


New submission from Julien Palard <julien+python at palard.fr>:

In the following snippet:

    >>> class Ror:
    ...     def __ror__(self, other):
    ...         return set()
    ...
    >>> {}.keys() | Ror()
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
    TypeError: 'Ror' object is not iterable

I expect the __or__ implementation of dict_keys to return NotImplemented when given a non-interesting thing, so my __ror__ can run and get an empty set instead of a TypeError.

Strangely enough, it worked in Python 2.7, I'm not fluent enough en 2.7 object nor C implementation to know why, the dictviews_or looks the same for me.

It looks easy to fix without breaking the tests in dictobject.c like:

    --- a/Objects/dictobject.c
    +++ b/Objects/dictobject.c
    @@ -4284,7 +4284,8 @@ dictviews_or(PyObject* self, PyObject *other)
         tmp = _PyObject_CallMethodIdOneArg(result, &PyId_update, other);
         if (tmp == NULL) {
             Py_DECREF(result);
    -        return NULL;
    +        PyErr_Clear();
    +        Py_RETURN_NOTIMPLEMENTED;
         }

the question is more: should we? I think so but am I missing something?

----------
messages: 355007
nosy: mdk
priority: normal
severity: normal
status: open
title: dictobject dictviews don't return NotImplemented for unrecognized types.
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38538>
_______________________________________

From report at bugs.python.org  Sun Oct 20 11:51:51 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 20 Oct 2019 15:51:51 +0000
Subject: [issue38538] dictobject dictviews don't return NotImplemented for
 unrecognized types.
In-Reply-To: <1571585548.13.0.376831813762.issue38538@roundup.psfhosted.org>
Message-ID: <1571586711.16.0.776370995518.issue38538@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +inada.naoki

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38538>
_______________________________________

From report at bugs.python.org  Sun Oct 20 12:46:55 2019
From: report at bugs.python.org (Batuhan)
Date: Sun, 20 Oct 2019 16:46:55 +0000
Subject: [issue38531] argparse action "extend" not documented as new
In-Reply-To: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>
Message-ID: <1571590015.82.0.0711493812498.issue38531@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


----------
keywords: +patch
pull_requests: +16411
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16865

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sun Oct 20 13:06:17 2019
From: report at bugs.python.org (Batuhan)
Date: Sun, 20 Oct 2019 17:06:17 +0000
Subject: [issue38531] argparse action "extend" not documented as new
In-Reply-To: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>
Message-ID: <1571591177.98.0.430903402681.issue38531@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

Sorry for the inconvenience. I'm fixing it

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sun Oct 20 13:19:50 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 17:19:50 +0000
Subject: [issue36321] Fix misspelled attribute name in namedtuple()
In-Reply-To: <1552767663.81.0.27756638002.issue36321@roundup.psfhosted.org>
Message-ID: <1571591990.68.0.278573073903.issue36321@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset 58ccd201fa74287ca9293c03136fcf1e19800ef9 by Raymond Hettinger in branch 'master':
bpo-36321: Fix misspelled attribute name in namedtuple() (GH-16858)
https://github.com/python/cpython/commit/58ccd201fa74287ca9293c03136fcf1e19800ef9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36321>
_______________________________________

From report at bugs.python.org  Sun Oct 20 13:20:29 2019
From: report at bugs.python.org (Batuhan)
Date: Sun, 20 Oct 2019 17:20:29 +0000
Subject: [issue38522] Py_USING_MEMORY_DEBUGGER is referenced in docs but not
 present in code
In-Reply-To: <1571436071.95.0.156296507321.issue38522@roundup.psfhosted.org>
Message-ID: <1571592029.53.0.179401206023.issue38522@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

It looks like benjamin peterson removed remaining references from obmalloc.c in 3924f93794fd740c547b44884f73303196475cd5

----------
nosy: +BTaskaya, benjamin.peterson

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38522>
_______________________________________

From report at bugs.python.org  Sun Oct 20 14:25:25 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 18:25:25 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571595925.78.0.0266647288274.issue37759@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset c93883c6afbd99929516764263fc49c3e996b10a by Raymond Hettinger in branch 'master':
bpo-37759: More updates to Whatsnew 3.8 (GH-16854)
https://github.com/python/cpython/commit/c93883c6afbd99929516764263fc49c3e996b10a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Sun Oct 20 14:25:52 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 20 Oct 2019 18:25:52 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571595952.58.0.0763952729723.issue37759@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16412
pull_request: https://github.com/python/cpython/pull/16867

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Sun Oct 20 14:35:31 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 18:35:31 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571596531.4.0.809525890616.issue37759@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset c39bc5c9e8f96a8197d1ce2b70746b7189135566 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-37759: More updates to Whatsnew 3.8 (GH-16854) (GH-16867)
https://github.com/python/cpython/commit/c39bc5c9e8f96a8197d1ce2b70746b7189135566


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Sun Oct 20 15:17:35 2019
From: report at bugs.python.org (Julin)
Date: Sun, 20 Oct 2019 19:17:35 +0000
Subject: [issue38539] Update demo files
Message-ID: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>


New submission from Julin <julinshaji02 at gmail.com>:

The demo programs inside Tools/demo, which is to guide people new to the language (that's the purpose, right?), makes use of several bad coding practices.

Like
 - `while 1:` being used instead of `while True:`
 - star import
 - function call and an `if` statement being on the same line, etc.

It can easily mislead someone new to the language especially since it is part of the codebase and part of distribution as well.

Can we update these files? Most of these seem have not been updated in some time.

A discussion touching this problem on #python-dev suggested that the demos were written when the docs were yet to be polished and now that we have a fully fledged documentation, maybe the demo files can be dropped.

But since the bpo has an option 'Demos and tools' under 'components', I guess maybe the demos are still considered essential.

What do you all think?

----------
components: Demos and Tools
messages: 355013
nosy: ju-sh
priority: normal
severity: normal
status: open
title: Update demo files
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Sun Oct 20 15:59:51 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 19:59:51 +0000
Subject: [issue38539] Update demo files
In-Reply-To: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>
Message-ID: <1571601591.56.0.966677916069.issue38539@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

The Tools/demo modules are sort of a quaint museum to the past.  That said, most of the code reads fine even by today's standards.

Go ahead with as PR to change "while 1" to "while True".

The star imports should remain (they are the norm for Tkinter) code.

Let's don't reformat the if/action pairs on the same line.  That reflects the author's way of thinking about the problem.  Though it may offend your stylistic sensibilities, it is valid Python and readable enough.

BTW, the scripts are almost never "guide people new to the language".  They are typically only found by experienced programmers exploring the tree of code (like little easter eggs).

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:00:12 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 20:00:12 +0000
Subject: [issue38539] Update demo files
In-Reply-To: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>
Message-ID: <1571601612.23.0.573474518955.issue38539@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee:  -> rhettinger
versions:  -Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:14:03 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 20:14:03 +0000
Subject: [issue38531] argparse action "extend" not documented as new
In-Reply-To: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>
Message-ID: <1571602443.66.0.318433026123.issue38531@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset 74142078b3b78fea7b4cd791e5c577c0c0964eb7 by Raymond Hettinger (Batuhan Ta?kaya) in branch 'master':
bpo-38531: document extend action's added version (GH-16865)
https://github.com/python/cpython/commit/74142078b3b78fea7b4cd791e5c577c0c0964eb7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:14:08 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 20 Oct 2019 20:14:08 +0000
Subject: [issue38531] argparse action "extend" not documented as new
In-Reply-To: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>
Message-ID: <1571602448.77.0.0819840130131.issue38531@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16413
pull_request: https://github.com/python/cpython/pull/16868

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:14:57 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 20:14:57 +0000
Subject: [issue38531] argparse action "extend" not documented as new
In-Reply-To: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>
Message-ID: <1571602497.77.0.979663076746.issue38531@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Christoph, thanks for the report.
Batuhan, thanks for the PR.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:16:53 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 20:16:53 +0000
Subject: [issue38531] argparse action "extend" not documented as new
In-Reply-To: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>
Message-ID: <1571602613.65.0.413425309804.issue38531@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee: docs at python -> rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:20:18 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 20 Oct 2019 20:20:18 +0000
Subject: [issue34014] loop.run_in_executor should propagate current contextvars
In-Reply-To: <1530401184.74.0.56676864532.issue34014@psf.upfronthosting.co.za>
Message-ID: <1571602818.26.0.287692692834.issue34014@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
versions: +Python 3.9 -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34014>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:25:28 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 20:25:28 +0000
Subject: [issue38531] argparse action "extend" not documented as new
In-Reply-To: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>
Message-ID: <1571603128.04.0.874185889005.issue38531@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset db385229645dbaaa9863e259b2fae67b9da873fe by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-38531: document extend action's added version (GH-16865) (GH-16868)
https://github.com/python/cpython/commit/db385229645dbaaa9863e259b2fae67b9da873fe


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:26:08 2019
From: report at bugs.python.org (Batuhan)
Date: Sun, 20 Oct 2019 20:26:08 +0000
Subject: [issue38531] argparse action "extend" not documented as new
In-Reply-To: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>
Message-ID: <1571603168.43.0.869092518945.issue38531@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

@rhettinger, should we mention about it in whats new too?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:28:26 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 20:28:26 +0000
Subject: [issue38531] argparse action "extend" not documented as new
In-Reply-To: <1571518792.2.0.7359491758.issue38531@roundup.psfhosted.org>
Message-ID: <1571603306.62.0.0332982367707.issue38531@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I've added it to my todo list for the next round of updates.  Though I also plan to do some parsing of the more minor feature adds to make the document more readable.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38531>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:32:33 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 20 Oct 2019 20:32:33 +0000
Subject: [issue37759] Polish whatsnew for 3.8
In-Reply-To: <1564971591.59.0.825854790144.issue37759@roundup.psfhosted.org>
Message-ID: <1571603553.61.0.423744740703.issue37759@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Todos for the next round:
* consider an entry for argparse's extend option
* example for multiprocessing shared memory
* Move C major API changes to its own section
* Edit-out very minor changes so that the
  bigger wins are more salient

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37759>
_______________________________________

From report at bugs.python.org  Sun Oct 20 16:49:13 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 20 Oct 2019 20:49:13 +0000
Subject: [issue26389] Expand traceback module API to accept just an exception
 as an argument
In-Reply-To: <1455836350.85.0.0162824201978.issue26389@psf.upfronthosting.co.za>
Message-ID: <1571604553.93.0.522653069802.issue26389@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

@mbussonn, were you interested in continuing with Brett's (and your) suggestion for the API by making the first argument positional-only and the others optional?

----------
versions: +Python 3.9 -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26389>
_______________________________________

From report at bugs.python.org  Sun Oct 20 23:21:09 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Mon, 21 Oct 2019 03:21:09 +0000
Subject: [issue22385] Define a binary output formatting mini-language for
 *.hex()
In-Reply-To: <1410393301.25.0.193851592698.issue22385@psf.upfronthosting.co.za>
Message-ID: <1571628069.38.0.806936679855.issue22385@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
resolution:  -> fixed
stage: patch review -> commit review
status: open -> closed
versions: +Python 3.9 -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22385>
_______________________________________

From report at bugs.python.org  Mon Oct 21 02:20:30 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 06:20:30 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
Message-ID: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

There are possible leaks in PyArg_Parse and similar functions for format units "es#" and "et#". Macros STORE_SIZE and (since 3.8) FETCH_SIZE can leave the function despite there is an own reference to an encoded string (s). The leak is only possible when PY_SSIZE_T_CLEAN is not defined.

----------
components: Interpreter Core
messages: 355022
nosy: inada.naoki, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Possible leaks in PyArg_Parse for "es#" and "et#"
type: resource usage
versions: Python 2.7, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 02:25:00 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 06:25:00 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571639100.41.0.853059278702.issue38540@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16414
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16869

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 02:31:50 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 06:31:50 +0000
Subject: [issue38465] The type of ob_exports in PyByteArrayObject become
 Py_ssize_t.
In-Reply-To: <1570978635.87.0.596564542888.issue38465@roundup.psfhosted.org>
Message-ID: <1571639510.55.0.913749219551.issue38465@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 06cd5b6acd98205adae1a3ea4223e88f38ad55ab by Serhiy Storchaka (Hai Shi) in branch 'master':
bpo-38465: Convert the type of exports counters to Py_ssize_t. (GH-16746)
https://github.com/python/cpython/commit/06cd5b6acd98205adae1a3ea4223e88f38ad55ab


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38465>
_______________________________________

From report at bugs.python.org  Mon Oct 21 02:32:44 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 06:32:44 +0000
Subject: [issue38465] The type of ob_exports in PyByteArrayObject become
 Py_ssize_t.
In-Reply-To: <1570978635.87.0.596564542888.issue38465@roundup.psfhosted.org>
Message-ID: <1571639564.81.0.592325147528.issue38465@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Thank you for your contribution hai shi!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38465>
_______________________________________

From report at bugs.python.org  Mon Oct 21 02:36:24 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 06:36:24 +0000
Subject: [issue38208] Simplify string.Template by using __init_subclass__()
In-Reply-To: <1568787441.71.0.0135329637022.issue38208@roundup.psfhosted.org>
Message-ID: <1571639784.48.0.170129000589.issue38208@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 919f0bc8c904d3aa13eedb2dd1fe9c6b0555a591 by Serhiy Storchaka in branch 'master':
bpo-38208: Simplify string.Template by using __init_subclass__(). (GH-16256)
https://github.com/python/cpython/commit/919f0bc8c904d3aa13eedb2dd1fe9c6b0555a591


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38208>
_______________________________________

From report at bugs.python.org  Mon Oct 21 02:36:40 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 06:36:40 +0000
Subject: [issue38208] Simplify string.Template by using __init_subclass__()
In-Reply-To: <1568787441.71.0.0135329637022.issue38208@roundup.psfhosted.org>
Message-ID: <1571639800.57.0.269846056633.issue38208@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38208>
_______________________________________

From report at bugs.python.org  Mon Oct 21 02:49:53 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 06:49:53 +0000
Subject: [issue27961] remove support for platforms without "long long"
In-Reply-To: <1473119429.61.0.683650779093.issue27961@psf.upfronthosting.co.za>
Message-ID: <1571640593.38.0.359941034804.issue27961@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset a9ed91e6c2f0f1a9960b1382321918448228a801 by Serhiy Storchaka (Sergey Fedoseev) in branch 'master':
bpo-27961: Replace PY_LONG_LONG with long long. (GH-15386)
https://github.com/python/cpython/commit/a9ed91e6c2f0f1a9960b1382321918448228a801


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27961>
_______________________________________

From report at bugs.python.org  Mon Oct 21 03:01:08 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 07:01:08 +0000
Subject: [issue38493] os.CLD_KILLED and os.CLD_STOPPED should be implemented
In-Reply-To: <1571200572.77.0.0960305175101.issue38493@roundup.psfhosted.org>
Message-ID: <1571641268.69.0.884146348346.issue38493@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 2eba6ad7bf3a5beeed54209a0107be8e1ac77767 by Serhiy Storchaka (Dong-hee Na) in branch 'master':
bpo-38493: Add os.CLD_KILLED and os.CLD_STOPPED. (GH-16821)
https://github.com/python/cpython/commit/2eba6ad7bf3a5beeed54209a0107be8e1ac77767


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38493>
_______________________________________

From report at bugs.python.org  Mon Oct 21 03:02:12 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 07:02:12 +0000
Subject: [issue38493] os.CLD_KILLED and os.CLD_STOPPED should be implemented
In-Reply-To: <1571200572.77.0.0960305175101.issue38493@roundup.psfhosted.org>
Message-ID: <1571641332.96.0.434304743414.issue38493@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Thank you for your contribution Dong-hee!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38493>
_______________________________________

From report at bugs.python.org  Mon Oct 21 04:15:44 2019
From: report at bugs.python.org (ttrd)
Date: Mon, 21 Oct 2019 08:15:44 +0000
Subject: [issue38541] Performance degradation of attribute accesses in Python
 3.7.4
Message-ID: <1571645744.43.0.285485842632.issue38541@roundup.psfhosted.org>


New submission from ttrd <randy.doering at tracetronic.de>:

After upgrading from Python 3.7.3 to Python 3.7.4, we noticed an increased runtime of about 50% in some tests of our application.

After some testing we constructed the following hypothesis: Accessing instance attributes of classes that define a custom metaclass take more time in Python 3.7.4. The access takes the more time the more classes are in the MRO of the concerning class (in other words the more base classes the concerning class has got).

We verified the hypothesis by creating a minimal example (file attached) that produced the output at the bottom. (The index defines the number of base classes. The four variants are with/without a metaclass and with simple/multiple inheritance. The kind of inheritance has no influence on the runtime.)

In Python 3.7.4 (in contrast to 3.7.3 and 3.8), you can see that the usage of a metaclass results in a linear increase of the runtime of attribute accesses depending on the number of base classes.

We could also identify the issue/commit that introduced the performance issue:
https://bugs.python.org/issue28866
https://github.com/python/cpython/commit/bfd0b7720196b9ff647cc33dafbd31a04496402c

In the Python 3.8 branch, the performance issue seems to be resolved by:
https://bugs.python.org/issue36922
https://github.com/python/cpython/commit/988fff5d0e7fccecbf776c08ec56695820b3b4a8

Will this performance issue be addressed in a future 3.7 version (e.g. 3.7.6) or is it in your optinion sufficient that the issue seems to be resolved in 3.8?


Python 3.7.3 (constant runtime)

3.668036e-08 noMetaBaseX[1].attr
3.630355e-08 noMetaBaseX[2].attr
3.687350e-08 noMetaBaseX[5].attr
3.827102e-08 noMetaBaseX[10].attr
3.724956e-08 noMetaBaseX[20].attr
3.912778e-08 noMetaBaseX[50].attr
4.072552e-08 noMetaBaseX[100].attr
3.620875e-08 metaBaseX[1].attr
3.640054e-08 metaBaseX[2].attr
3.599339e-08 metaBaseX[5].attr
3.606570e-08 metaBaseX[10].attr
3.946514e-08 metaBaseX[20].attr
3.715085e-08 metaBaseX[50].attr
3.762364e-08 metaBaseX[100].attr
3.667802e-08 noMetaRecBaseX[1].attr
3.579415e-08 noMetaRecBaseX[2].attr
3.647997e-08 noMetaRecBaseX[5].attr
3.577428e-08 noMetaRecBaseX[10].attr
3.686319e-08 noMetaRecBaseX[20].attr
3.832261e-08 noMetaRecBaseX[50].attr
4.087625e-08 noMetaRecBaseX[100].attr
3.654509e-08 noMetaRecBaseX[1].attr
3.617825e-08 noMetaRecBaseX[2].attr
3.573970e-08 noMetaRecBaseX[5].attr
3.664559e-08 noMetaRecBaseX[10].attr
3.702526e-08 noMetaRecBaseX[20].attr
3.774067e-08 noMetaRecBaseX[50].attr
3.836915e-08 noMetaRecBaseX[100].attr

Python 3.7.4 (see lines marked with ->)

4.042378e-08 noMetaBaseX[1].attr
3.704071e-08 noMetaBaseX[2].attr
3.868766e-08 noMetaBaseX[5].attr
3.716869e-08 noMetaBaseX[10].attr
3.693100e-08 noMetaBaseX[20].attr
3.947849e-08 noMetaBaseX[50].attr
3.790146e-08 noMetaBaseX[100].attr
-> 5.010019e-08 metaBaseX[1].attr
-> 5.215336e-08 metaBaseX[2].attr
-> 6.103393e-08 metaBaseX[5].attr
-> 7.947347e-08 metaBaseX[10].attr
-> 1.082155e-07 metaBaseX[20].attr
-> 2.264330e-07 metaBaseX[50].attr
-> 4.951039e-07 metaBaseX[100].attr
3.727378e-08 noMetaRecBaseX[1].attr
3.815971e-08 noMetaRecBaseX[2].attr
3.661390e-08 noMetaRecBaseX[5].attr
3.709824e-08 noMetaRecBaseX[10].attr
3.785757e-08 noMetaRecBaseX[20].attr
3.813983e-08 noMetaRecBaseX[50].attr
3.856352e-08 noMetaRecBaseX[100].attr
-> 5.260115e-08 metaRecBaseX[1].attr
-> 5.661043e-08 metaRecBaseX[2].attr
-> 6.760995e-08 metaRecBaseX[5].attr
-> 8.038124e-08 metaRecBaseX[10].attr
-> 1.100538e-07 metaRecBaseX[20].attr
-> 2.246786e-07 metaRecBaseX[50].attr
-> 4.877147e-07 metaRecBaseX[100].attr
	
?Python 3.8.0rc1 (constant runtime)

?4.045787e-08 noMetaBaseX[1].attr
4.206206e-08 noMetaBaseX[2].attr
4.209608e-08 noMetaBaseX[5].attr
4.049552e-08 noMetaBaseX[10].attr
4.133343e-08 noMetaBaseX[20].attr
4.229599e-08 noMetaBaseX[50].attr
4.259420e-08 noMetaBaseX[100].attr
4.146996e-08 metaBaseX[1].attr
4.140459e-08 metaBaseX[2].attr
4.143048e-08 metaBaseX[5].attr
4.054639e-08 metaBaseX[10].attr
4.219960e-08 metaBaseX[20].attr
4.222810e-08 metaBaseX[50].attr
4.420123e-08 metaBaseX[100].attr
4.044410e-08 noMetaRecBaseX[1].attr
4.043790e-08 noMetaRecBaseX[2].attr
4.209061e-08 noMetaRecBaseX[5].attr
4.042041e-08 noMetaRecBaseX[10].attr
4.048202e-08 noMetaRecBaseX[20].attr
4.260607e-08 noMetaRecBaseX[50].attr
4.267928e-08 noMetaRecBaseX[100].attr
4.037958e-08 metaRecBaseX[1].attr
3.968827e-08 metaRecBaseX[2].attr
4.011758e-08 metaRecBaseX[5].attr
3.954960e-08 metaRecBaseX[10].attr
4.057979e-08 metaRecBaseX[20].attr
4.145640e-08 metaRecBaseX[50].attr
4.148783e-08 metaRecBaseX[100].attr

----------
components: Interpreter Core
files: timeAttrAccess.py
messages: 355029
nosy: ttrd
priority: normal
severity: normal
status: open
title: Performance degradation of attribute accesses in Python 3.7.4
type: performance
versions: Python 3.7
Added file: https://bugs.python.org/file48670/timeAttrAccess.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38541>
_______________________________________

From report at bugs.python.org  Mon Oct 21 04:35:10 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 08:35:10 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571646910.71.0.0570373472039.issue38540@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 5bc6a7c06eda20ba131ecba6752be0506d310181 by Serhiy Storchaka in branch 'master':
bpo-38540: Fix possible leak in PyArg_Parse for "es#" and "et#". (GH-16869)
https://github.com/python/cpython/commit/5bc6a7c06eda20ba131ecba6752be0506d310181


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 04:35:39 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 Oct 2019 08:35:39 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571646939.41.0.0936134150319.issue38540@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16415
pull_request: https://github.com/python/cpython/pull/16870

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 04:35:46 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 Oct 2019 08:35:46 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571646946.4.0.76523482887.issue38540@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16416
pull_request: https://github.com/python/cpython/pull/16871

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 04:56:53 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 Oct 2019 08:56:53 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571648213.12.0.0447112372266.issue38540@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 3dec84f40ef49bab994a1af4e6082bf81021feab by Miss Skeleton (bot) in branch '3.7':
bpo-38540: Fix possible leak in PyArg_Parse for "esGH-" and "etGH-". (GH-16869)
https://github.com/python/cpython/commit/3dec84f40ef49bab994a1af4e6082bf81021feab


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 05:11:04 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 21 Oct 2019 09:11:04 +0000
Subject: [issue38538] dictobject dictviews don't return NotImplemented for
 unrecognized types.
In-Reply-To: <1571585548.13.0.376831813762.issue38538@roundup.psfhosted.org>
Message-ID: <1571649064.86.0.510309634041.issue38538@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

> Strangely enough, it worked in Python 2.7

It is not strange since dict.keys() in Python 2.7 returns list.

>>> {}.viewkeys() | Ror()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: iteration over non-sequence

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38538>
_______________________________________

From report at bugs.python.org  Mon Oct 21 05:12:43 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 Oct 2019 09:12:43 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571649163.03.0.531344972758.issue38540@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset b1fc8c0c8aec7ef8edd119034e076bc48882ffbb by Miss Skeleton (bot) in branch '3.8':
bpo-38540: Fix possible leak in PyArg_Parse for "esGH-" and "etGH-". (GH-16869)
https://github.com/python/cpython/commit/b1fc8c0c8aec7ef8edd119034e076bc48882ffbb


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 05:43:52 2019
From: report at bugs.python.org (egaudry)
Date: Mon, 21 Oct 2019 09:43:52 +0000
Subject: [issue38542] Expose _PyGC_generation0 for allowing internal use
 directly from a CPython extension
Message-ID: <1571651032.85.0.698320385475.issue38542@roundup.psfhosted.org>


New submission from egaudry <eg at fft.be>:

Hi

I would like to be able to get an handle on PyGC_Head*_PyGC_generation0 from a CPython extension.
This is possible when building Python on a Posix host, but not on Windows because of a missing PyAPI_DATA wrapping of the said object in the objimpl.h header.

Having the possibility to inspect the PyGC_Head here can be very useful when customizing the way a garbage-collectable object created from CPython extension would be cleaned/inspected, etc.

Any chance this patch could be added to get the same capabilities on Windows and Posix platforms ?

Thanks for your feedback,
Eloi

----------
components: Interpreter Core
files: gc.diff
keywords: patch
messages: 355034
nosy: egaudry
priority: normal
severity: normal
status: open
title: Expose _PyGC_generation0 for allowing internal use directly from a CPython extension
type: enhancement
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9
Added file: https://bugs.python.org/file48671/gc.diff

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38542>
_______________________________________

From report at bugs.python.org  Mon Oct 21 05:46:20 2019
From: report at bugs.python.org (egaudry)
Date: Mon, 21 Oct 2019 09:46:20 +0000
Subject: [issue38543] Expose Py_TabcheckFlag as other PyAPI_DATA flag
Message-ID: <1571651180.6.0.332450448454.issue38543@roundup.psfhosted.org>


New submission from egaudry <eg at fft.be>:

When looking at the pydebug.h header file, I see that some symbols are not declared as exported.

For instance, I would like to be able to change the value of the Py_TabcheckFlag when running specific codelines.
Any chance this patch could be added ?

----------
components: Interpreter Core
files: tab.diff
keywords: patch
messages: 355035
nosy: egaudry
priority: normal
severity: normal
status: open
title: Expose Py_TabcheckFlag as other PyAPI_DATA flag
type: enhancement
versions: Python 3.7, Python 3.8, Python 3.9
Added file: https://bugs.python.org/file48672/tab.diff

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38543>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:04:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:04:59 +0000
Subject: [issue38542] [2.7] Expose _PyGC_generation0 for allowing internal use
 directly from a CPython extension
In-Reply-To: <1571651032.85.0.698320385475.issue38542@roundup.psfhosted.org>
Message-ID: <1571652299.95.0.644703970668.issue38542@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

This issue comes from a thread on python-ideas:
https://mail.python.org/archives/list/python-ideas at python.org/thread/7FC2NHAOMKBHONFTUKMAHO5F56UU5UUD/

I understand that it's specific to Python 2.7.

--

_PyGC_generation0 variable no longer exists in Python 3.7, it has been moved into _PyRuntime.gc.generation0:

Include/internal/mem.h:146:#define _PyGC_generation0 _PyRuntime.gc.generation0


In the master branch, _PyRuntime is exported with:

Include/internal/pycore_pystate.h: PyAPI_DATA(_PyRuntimeState) _PyRuntime;


In Python 3.7, _PyRuntime is also exported, but in a different header file:

Include/internal/pystate.h: PyAPI_DATA(_PyRuntimeState) _PyRuntime;

--

Python 2.7:

Modules/gcmodule.c:50:PyGC_Head *_PyGC_generation0 = GEN_HEAD(0);

Include/objimpl.h:276:extern PyGC_Head *_PyGC_generation0;

----------
nosy: +vstinner
title: Expose _PyGC_generation0 for allowing internal use directly from a CPython extension -> [2.7] Expose _PyGC_generation0 for allowing internal use directly from a CPython extension
versions: +Python 2.7 -Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38542>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:05:54 2019
From: report at bugs.python.org (xitop)
Date: Mon, 21 Oct 2019 10:05:54 +0000
Subject: [issue38085] Interrupting class creation in __init_subclass__ may
 lead to incorrect isinstance() and issubclass() results
In-Reply-To: <1568106581.16.0.558052842785.issue38085@roundup.psfhosted.org>
Message-ID: <1571652354.28.0.927707113267.issue38085@roundup.psfhosted.org>


xitop <reg.bugs at poti.sk> added the comment:

Same problem also in Python 3.6.8 and the new 3.8.0.

----------
versions: +Python 3.6, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38085>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:06:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:06:02 +0000
Subject: [issue38542] [2.7] Expose _PyGC_generation0 for allowing internal use
 directly from a CPython extension
In-Reply-To: <1571651032.85.0.698320385475.issue38542@roundup.psfhosted.org>
Message-ID: <1571652362.16.0.983507571849.issue38542@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38542>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:07:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:07:24 +0000
Subject: [issue35473] Intel compiler (icc) does not fully support C11 Features, 
 including atomics
In-Reply-To: <1544637027.92.0.788709270274.issue35473@psf.upfronthosting.co.za>
Message-ID: <1571652444.29.0.90581970156.issue35473@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I mark this issue as a duplicate of bpo-37415.

----------
nosy: +vstinner
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Error build Python with Intel compiler: <stdatomic.h> doesn't provide atomic_uintptr_t

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35473>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:07:38 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:07:38 +0000
Subject: [issue37415] Error build Python with Intel compiler: <stdatomic.h>
 doesn't provide atomic_uintptr_t
In-Reply-To: <1561563167.55.0.111630694926.issue37415@roundup.psfhosted.org>
Message-ID: <1571652458.76.0.0373863510575.issue37415@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I marked bpo-35473 as duplicate of this issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37415>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:19:05 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:19:05 +0000
Subject: [issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1
 3.x: directory not empty: Scripts\
Message-ID: <1571653144.99.0.203555280128.issue38544@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

https://buildbot.python.org/all/#/builders/40/builds/3317

test_executable (test.test_venv.BasicTest) ... ok
test_executable_symlinks (test.test_venv.BasicTest) ... skipped 'Needs symlinks'
test_isolation (test.test_venv.BasicTest) ... ERROR
ERROR
test_multiprocessing (test.test_venv.BasicTest) ... ok
test_overwrite_existing (test.test_venv.BasicTest) ... ok

======================================================================
ERROR: test_isolation (test.test_venv.BasicTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\test_venv.py", line 272, in test_isolation
    builder.create(self.env_dir)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\venv\__init__.py", line 65, in create
    context = self.ensure_directories(env_dir)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\venv\__init__.py", line 108, in ensure_directories
    self.clear_directory(env_dir)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\venv\__init__.py", line 91, in clear_directory
    shutil.rmtree(fn)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\shutil.py", line 730, in rmtree
    return _rmtree_unsafe(path, onerror)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\shutil.py", line 612, in _rmtree_unsafe
    onerror(os.rmdir, path, sys.exc_info())
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\shutil.py", line 610, in _rmtree_unsafe
    os.rmdir(path)
OSError: [WinError 145] The directory is not empty: 'C:\\Users\\Buildbot\\AppData\\Local\\Temp\\tmp2y7z3288\\Scripts'

----------
components: Tests
messages: 355040
nosy: vstinner
priority: normal
severity: normal
status: open
title: test_venv: test_isolation() failed on AMD64 Windows7 SP1 3.x: directory not empty: Scripts\
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38544>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:19:48 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:19:48 +0000
Subject: [issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1
 3.x: directory not empty: Scripts\
In-Reply-To: <1571653144.99.0.203555280128.issue38544@roundup.psfhosted.org>
Message-ID: <1571653188.17.0.373536207676.issue38544@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Similar error on the same build when the test was re-run in verbose mode:

0:10:55 load avg: 1.82 Re-running test_venv in verbose mode
test_deactivate_with_strict_bash_opts (test.test_venv.BasicTest) ... skipped 'not relevant on Windows'
test_defaults (test.test_venv.BasicTest) ... ok
test_executable (test.test_venv.BasicTest) ... ok
test_executable_symlinks (test.test_venv.BasicTest) ... skipped 'Needs symlinks'
test_isolation (test.test_venv.BasicTest) ... ok
test_multiprocessing (test.test_venv.BasicTest) ... ok
test_overwrite_existing (test.test_venv.BasicTest) ... ERROR
ERROR
test_prefixes (test.test_venv.BasicTest) ... ok
test_prompt (test.test_venv.BasicTest) ... ok
test_symlinking (test.test_venv.BasicTest) ... skipped 'Needs symlinks'
test_unicode_in_batch_file (test.test_venv.BasicTest) ... ok
test_unoverwritable_fails (test.test_venv.BasicTest) ... ok
test_upgrade (test.test_venv.BasicTest) ... ok
test_upgrade_dependencies (test.test_venv.BasicTest) ... ok
test_devnull (test.test_venv.EnsurePipTest) ... ok
test_explicit_no_pip (test.test_venv.EnsurePipTest) ... ok
test_no_pip_by_default (test.test_venv.EnsurePipTest) ... ok
test_with_pip (test.test_venv.EnsurePipTest) ... ok

======================================================================
ERROR: test_overwrite_existing (test.test_venv.BasicTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\test_venv.py", line 223, in test_overwrite_existing
    builder.create(self.env_dir)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\venv\__init__.py", line 65, in create
    context = self.ensure_directories(env_dir)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\venv\__init__.py", line 108, in ensure_directories
    self.clear_directory(env_dir)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\venv\__init__.py", line 91, in clear_directory
    shutil.rmtree(fn)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\shutil.py", line 730, in rmtree
    return _rmtree_unsafe(path, onerror)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\shutil.py", line 612, in _rmtree_unsafe
    onerror(os.rmdir, path, sys.exc_info())
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\shutil.py", line 610, in _rmtree_unsafe
    os.rmdir(path)
OSError: [WinError 145] The directory is not empty: 'C:\\Users\\Buildbot\\AppData\\Local\\Temp\\tmpvw7zok8k\\Scripts'

======================================================================
ERROR: test_overwrite_existing (test.test_venv.BasicTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\support\__init__.py", line 336, in _force_run
    return func(*args)
PermissionError: [WinError 5] Access is denied: 'C:\\Users\\Buildbot\\AppData\\Local\\Temp\\tmpvw7zok8k\\Scripts\\activate.bat'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\test_venv.py", line 71, in tearDown
    rmtree(self.env_dir)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\support\__init__.py", line 458, in rmtree
    _rmtree(path)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\support\__init__.py", line 399, in _rmtree
    _waitfor(_rmtree_inner, path, waitall=True)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\support\__init__.py", line 347, in _waitfor
    func(pathname)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\support\__init__.py", line 395, in _rmtree_inner
    _waitfor(_rmtree_inner, fullname, waitall=True)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\support\__init__.py", line 347, in _waitfor
    func(pathname)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\support\__init__.py", line 398, in _rmtree_inner
    _force_run(fullname, os.unlink, fullname)
  File "C:\buildbot.python.org\3.x.kloth-win64\build\lib\test\support\__init__.py", line 341, in _force_run
    os.chmod(path, stat.S_IRWXU)
PermissionError: [WinError 5] Access is denied: 'C:\\Users\\Buildbot\\AppData\\Local\\Temp\\tmpvw7zok8k\\Scripts\\activate.bat'

----------------------------------------------------------------------

Ran 18 tests in 45.669s

FAILED (errors=2, skipped=3)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38544>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:21:04 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:21:04 +0000
Subject: [issue36732] Windows: test_asyncio: test_huge_content_recvinto()
 fails randomly with ProactorEventLoop
In-Reply-To: <1556264661.54.0.31283754406.issue36732@roundup.psfhosted.org>
Message-ID: <1571653264.87.0.564792517737.issue36732@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: test_asyncio: test_huge_content_recvinto() fails randomly -> Windows: test_asyncio: test_huge_content_recvinto() fails randomly with ProactorEventLoop
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36732>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:23:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:23:46 +0000
Subject: [issue30735] Python 3.6.1 test_asyncio fails on Solaris 11
In-Reply-To: <1498139102.26.0.319354129691.issue30735@psf.upfronthosting.co.za>
Message-ID: <1571653426.81.0.594464350933.issue30735@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Solaris is not really supported in Python:
https://pythondev.readthedocs.io/platforms.html#best-effort-and-unofficial-platforms

There is no more Solaris buildbot worker for example.

Morevoer, this issue has no activity for 2 years. I close it.

----------
nosy: +vstinner
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30735>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:27:16 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:27:16 +0000
Subject: [issue23819] test_asyncio fails when run under -O
In-Reply-To: <1427808695.9.0.385563565443.issue23819@psf.upfronthosting.co.za>
Message-ID: <1571653636.34.0.506683234509.issue23819@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

This issue is still relevant 4 years later: many test_asyncio tests fail with python3 -O :-(

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23819>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:28:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:28:07 +0000
Subject: [issue28562] test_asyncio fails on Android upon calling getaddrinfo()
In-Reply-To: <1477846363.43.0.193615088108.issue28562@psf.upfronthosting.co.za>
Message-ID: <1571653687.51.0.913764617166.issue28562@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Is the test still failing on the master branch of Python? Is the patch still needed?

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28562>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:31:01 2019
From: report at bugs.python.org (Laurie Opperman)
Date: Mon, 21 Oct 2019 10:31:01 +0000
Subject: [issue38545] Implement setter and deleter on functools.cached_property
Message-ID: <1571653861.42.0.831485996557.issue38545@roundup.psfhosted.org>


New submission from Laurie Opperman <laurie_opperman at hotmail.com>:

Support setting/updating and clearing the cached value of a cached-property (getter implemented by bpo-21145). Pretty straight-forward to implement

The question is whether cached-property updating should be:
a) always allowed
b) enabled with a cached-property instance attribute
c) enabled with the decorated method's class attribute
d) enabled with the decorated method's instance attribute
e) enabled in a separate decorator (eg functools.updatable_cached_property)

Note: options a, b, c, and d will make functools.cached_property a data descriptor.

I prefer option b or c, as the decision to make the property updatable becomes the property's definer's.

Also, should a warning be raised if a cached value is being overwritten? Should a warning be raised if no cached value is to be deleted?

----------
components: Library (Lib)
messages: 355045
nosy: Epic_Wink
priority: normal
severity: normal
status: open
title: Implement setter and deleter on functools.cached_property
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38545>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:34:16 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:34:16 +0000
Subject: [issue36790] [Windows] test_asyncio fails with application verifier!
 _cancel_overlapped() fails with "The handle is invalid"
In-Reply-To: <1556928611.19.0.664021052346.issue36790@roundup.psfhosted.org>
Message-ID: <1571654056.66.0.950732183534.issue36790@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> when running the testsuite under Application Verifier

test_asyncio is quite big. Can you run test_asyncio in verbose mode, and attach the output as a file to the issue? Or try to identify a few examples of tests which fail with "The handle is invalid" errors"?

It seems like "The handle is invalid" errors" error occurs while calling _cancel_overlapped().

----------
nosy: +vstinner
title: test_asyncio fails with application verifier! -> [Windows] test_asyncio fails with application verifier! _cancel_overlapped() fails with "The handle is invalid"
versions: +Python 3.9 -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36790>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:35:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:35:03 +0000
Subject: [issue34316] test_socket and test_asyncio timeouts in AMD64 Windows10
 3.x buildbots
In-Reply-To: <1533204699.35.0.56676864532.issue34316@psf.upfronthosting.co.za>
Message-ID: <1571654103.03.0.65792479407.issue34316@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I didn't see these failures recently, so I simply close the issue as out of date.

----------
nosy: +vstinner
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34316>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:43:58 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:43:58 +0000
Subject: [issue37516] buid error - test_asyncio fails during make
In-Reply-To: <1562446464.35.0.966251927477.issue37516@roundup.psfhosted.org>
Message-ID: <1571654638.85.0.762024063703.issue37516@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The issue title says "test_asyncio fails", but "Unknown child process pid 30234, will report returncode 255" looks more like a warning. Does test_asyncio fail or not?

Please run test_asyncio in verbose mode to identify which test emits the warning.

Without further information, I suggest to just close the issue, since it doesn't sound like a bug, just a warning.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37516>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:44:19 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:44:19 +0000
Subject: [issue37516] test_asyncio logs: Unknown child process
In-Reply-To: <1562446464.35.0.966251927477.issue37516@roundup.psfhosted.org>
Message-ID: <1571654659.41.0.741092182754.issue37516@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: buid error - test_asyncio fails during make -> test_asyncio logs: Unknown child process

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37516>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:45:08 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:45:08 +0000
Subject: [issue37897] test_asyncio hangs on an IPv6-only host
In-Reply-To: <1566325935.2.0.450737551586.issue37897@roundup.psfhosted.org>
Message-ID: <1571654708.79.0.483157257028.issue37897@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I guess that either test_drain_raises should be skipped or modified to listen to ::1 (IPv6 loopback).

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37897>
_______________________________________

From report at bugs.python.org  Mon Oct 21 06:46:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 10:46:03 +0000
Subject: [issue36990] [AIX] test_asyncio.test_create_connection_ipv6_scope
 fails(in mock test?)
In-Reply-To: <1558439793.15.0.664756328285.issue36990@roundup.psfhosted.org>
Message-ID: <1571654763.92.0.27814280441.issue36990@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: test_asyncio.test_create_connection_ipv6_scope fails(in mock test?) -> [AIX] test_asyncio.test_create_connection_ipv6_scope fails(in mock test?)

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36990>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:14:08 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 11:14:08 +0000
Subject: [issue38543] [2.7] Expose Py_TabcheckFlag as other PyAPI_DATA flag
In-Reply-To: <1571651180.6.0.332450448454.issue38543@roundup.psfhosted.org>
Message-ID: <1571656448.9.0.904243704711.issue38543@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Py_TabcheckFlag has been removed from Python 3. This issue is specific to Python 2.7.

----------
components: +Build
nosy: +vstinner
title: Expose Py_TabcheckFlag as other PyAPI_DATA flag -> [2.7] Expose Py_TabcheckFlag as other PyAPI_DATA flag
versions: +Python 2.7 -Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38543>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:15:30 2019
From: report at bugs.python.org (Laurie Opperman)
Date: Mon, 21 Oct 2019 11:15:30 +0000
Subject: [issue38545] Implement setter and deleter on functools.cached_property
In-Reply-To: <1571653861.42.0.831485996557.issue38545@roundup.psfhosted.org>
Message-ID: <1571656530.8.0.5129881609.issue38545@roundup.psfhosted.org>


Change by Laurie Opperman <laurie_opperman at hotmail.com>:


----------
keywords: +patch
pull_requests: +16417
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16872

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38545>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:20:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 11:20:00 +0000
Subject: [issue38546] test_concurrent_futures: test_interpreter_shutdown()
 warning "reap_children() reaped child process" on AMD64 RHEL7 3.x
Message-ID: <1571656800.65.0.31860297071.issue38546@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

https://buildbot.python.org/all/#/builders/254/builds/162

test_no_stale_references (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.56s ok
test_ressources_gced_in_workers (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 1.90s ok
test_shutdown_race_issue12456 (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.54s ok
test_submit (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.52s ok
test_submit_keyword (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.57s ok
test_traceback (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.48s ok
test_context_manager_shutdown (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolShutdownTest) ... 0.03s ok
test_del_shutdown (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolShutdownTest) ... 0.02s ok
test_hang_issue12364 (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolShutdownTest) ... 1.45s ok
test_interpreter_shutdown (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolShutdownTest) ... 1.62s Warning -- reap_children() reaped child process 28936
ok

----------
components: Tests
messages: 355051
nosy: vstinner
priority: normal
severity: normal
status: open
title: test_concurrent_futures: test_interpreter_shutdown() warning "reap_children() reaped child process" on AMD64 RHEL7 3.x
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38546>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:20:12 2019
From: report at bugs.python.org (egaudry)
Date: Mon, 21 Oct 2019 11:20:12 +0000
Subject: [issue38543] [2.7] Expose Py_TabcheckFlag as other PyAPI_DATA flag
In-Reply-To: <1571651180.6.0.332450448454.issue38543@roundup.psfhosted.org>
Message-ID: <1571656812.65.0.970130837865.issue38543@roundup.psfhosted.org>


egaudry <eg at fft.be> added the comment:

closing as this no real point in making something available in an EOL branch.

----------
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38543>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:20:37 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 11:20:37 +0000
Subject: [issue38546] test_concurrent_futures: test_interpreter_shutdown()
 warning "reap_children() reaped child process" on AMD64 RHEL7 3.x
In-Reply-To: <1571656800.65.0.31860297071.issue38546@roundup.psfhosted.org>
Message-ID: <1571656837.51.0.481015950271.issue38546@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It looks similar to bpo-38448: "test_concurrent_futures: reap_children() reaped child process 26487 on AMD64 RHEL8 Refleaks 3.x"

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38546>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:24:18 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 11:24:18 +0000
Subject: [issue38543] [2.7] Expose Py_TabcheckFlag as other PyAPI_DATA flag
In-Reply-To: <1571651180.6.0.332450448454.issue38543@roundup.psfhosted.org>
Message-ID: <1571657058.96.0.497244352197.issue38543@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Right, Python 2.7 support is ending at the end of the year. Python 2.7 got 18 releases without Py_TabcheckFlag, you're the first to request it.

You should consider to upgrade to Python 3 and have a look at my PEP 587 "Python Initialization Configuration" ;-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38543>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:26:11 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 11:26:11 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571657171.34.0.792021334132.issue20443@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

What is the use case for having a relative sys.argv[0]?

> Isn't that change breaking compat ?

Right. It has been made on purpose. The rationale can be found in the first message of this issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:32:35 2019
From: report at bugs.python.org (Laurie Opperman)
Date: Mon, 21 Oct 2019 11:32:35 +0000
Subject: [issue38545] Implement setter and deleter on functools.cached_property
In-Reply-To: <1571653861.42.0.831485996557.issue38545@roundup.psfhosted.org>
Message-ID: <1571657555.74.0.0439676039555.issue38545@roundup.psfhosted.org>


Laurie Opperman <laurie_opperman at hotmail.com> added the comment:

Turns out, that as a non-data descriptor, a cached property already has setting/updating and clearing through the normal mechanisms in Python. This feature request is therefore redundant: perhaps a new issue to document this inherent behaviour?

Unless you explicitly want to make cached property updating not allowed, but that's easily implemented in application code by sub-classing `functools.cached_property` and defining `__set__` and `__delete__` to raise:

    class unupdatable_cached_property(functools.cached_property):
        def __set__(self, instance, value):
            raise AttributeError("can't set attribute")

        def __delete__(self, instance):
            raise AttributeError("can't delete attribute")

----------
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38545>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:33:21 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 11:33:21 +0000
Subject: [issue36752] test multiprocessing: test_rapid_restart() crash on AIX
 when using XLC compiler
In-Reply-To: <1556543240.21.0.411629530832.issue36752@roundup.psfhosted.org>
Message-ID: <1571657601.88.0.494276802582.issue36752@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

According to Michael Felt, the bug is specific to XLC compiler, but the POWER6 AIX buildbot worker switch to GCC.

Michael Felt: Maybe Python documentation or build system should somewhere discourage the usage of the XLC on AIX because of this bug. But that's a different issue.

Since it seems like nobody is available to debug the XLC specific issue and that the buildbot worker worked around the issue, I close the issue.

----------
resolution:  -> out of date
stage:  -> resolved
status: open -> closed
title: test multiprocessing: test_rapid_restart() crash on AIX -> test multiprocessing: test_rapid_restart() crash on AIX when using XLC compiler

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36752>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:34:56 2019
From: report at bugs.python.org (egaudry)
Date: Mon, 21 Oct 2019 11:34:56 +0000
Subject: [issue38542] [2.7] Expose _PyGC_generation0 for allowing internal use
 directly from a CPython extension
In-Reply-To: <1571651032.85.0.698320385475.issue38542@roundup.psfhosted.org>
Message-ID: <1571657696.19.0.0962831907933.issue38542@roundup.psfhosted.org>


egaudry <eg at fft.be> added the comment:

Victor,

extern PyGC_Head *_PyGC_generation0; 
is located at line 374 of Include/objimpl.h (ifndef Py_LIMITED_API).

I used it from a CPython extension we are developing as an handle to the collection of objects being garbage collected.

>From what you explained, I should use the _PyRuntime exported symbol to get the handle this PyGC_Head. I'll do this.

I guess that cleaning the Include/objimpl.h is the only remaining action to do then.

Thanks for your feedback.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38542>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:38:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 11:38:39 +0000
Subject: [issue38547] test_pty fails when using setsid()
Message-ID: <1571657919.98.0.824899649018.issue38547@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

regrtest has been modified in bpo-38502 to use setsid() when using multiprocessing mode (-jN command line option).

Problem: David Bolen identified that test_pty started to fail on his bolen-ubuntu worker (Ubuntu 18.04.3) since my commit ecb035cd14c11521276343397151929a94018a22.

https://buildbot.python.org/all/#/builders/141/builds/2679

0:19:05 load avg: 1.81 [234/419/1] test_pty crashed (Exit code -1) -- running: test_unicodedata (55.5 sec)

I can reproduce the issue locally:

---
$ ./python -m test -j2 test_pty -v
== CPython 3.9.0a0 (heads/urlparse_ipv6:cc733a8cb6, Oct 21 2019, 11:34:36) [GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]
== Linux-5.2.18-200.fc30.x86_64-x86_64-with-glibc2.29 little-endian
== cwd: /home/vstinner/python/master/build/test_python_20242
== CPU count: 8
== encodings: locale=UTF-8, FS=utf-8
0:00:00 load avg: 0.70 Run tests in parallel using 2 child processes
0:00:00 load avg: 0.70 [1/1/1] test_pty crashed (Exit code -1)
test_basic (test.test_pty.PtyTest) ...

== Tests result: FAILURE ==

1 test failed:
    test_pty

Total duration: 383 ms
Tests result: FAILURE
---

It's surprising that there is no output!

I would prefer to keep process groups in regrtest, it's really helpful to be able to kill all processes spawned by a test worker process.

I'm not sure how/why PTY depends is incompatible with setsid().

----------
components: Tests
messages: 355059
nosy: vstinner
priority: normal
severity: normal
status: open
title: test_pty fails when using setsid()
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38547>
_______________________________________

From report at bugs.python.org  Mon Oct 21 07:39:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 11:39:13 +0000
Subject: [issue38502] regrtest: use process groups
In-Reply-To: <1571266006.89.0.625453271604.issue38502@roundup.psfhosted.org>
Message-ID: <1571657953.4.0.165175652934.issue38502@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> I don't know for sure that this is the cause but both 3.x builds following this commit on my bolen-ubuntu worker (Ubuntu 18.04.3) have had test_pty crash in the first attempt, with the retry succeeding.  For example https://buildbot.python.org/all/#/builders/141/builds/2679

I created bpo-38547: "test_pty fails when using setsid()".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38502>
_______________________________________

From report at bugs.python.org  Mon Oct 21 08:01:17 2019
From: report at bugs.python.org (Jeremy Kloth)
Date: Mon, 21 Oct 2019 12:01:17 +0000
Subject: [issue36732] Windows: test_asyncio: test_huge_content_recvinto()
 fails randomly with ProactorEventLoop
In-Reply-To: <1556264661.54.0.31283754406.issue36732@roundup.psfhosted.org>
Message-ID: <1571659277.7.0.781922657438.issue36732@roundup.psfhosted.org>


Change by Jeremy Kloth <jeremy.kloth+python-tracker at gmail.com>:


----------
nosy: +jkloth

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36732>
_______________________________________

From report at bugs.python.org  Mon Oct 21 08:01:29 2019
From: report at bugs.python.org (Jeremy Kloth)
Date: Mon, 21 Oct 2019 12:01:29 +0000
Subject: [issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1
 3.x: directory not empty: Scripts\
In-Reply-To: <1571653144.99.0.203555280128.issue38544@roundup.psfhosted.org>
Message-ID: <1571659289.98.0.00366994954804.issue38544@roundup.psfhosted.org>


Change by Jeremy Kloth <jeremy.kloth+python-tracker at gmail.com>:


----------
nosy: +jkloth

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38544>
_______________________________________

From report at bugs.python.org  Mon Oct 21 08:04:52 2019
From: report at bugs.python.org (Jeremy Kloth)
Date: Mon, 21 Oct 2019 12:04:52 +0000
Subject: [issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1
 3.x: directory not empty: Scripts\
In-Reply-To: <1571653144.99.0.203555280128.issue38544@roundup.psfhosted.org>
Message-ID: <1571659492.17.0.266391955033.issue38544@roundup.psfhosted.org>


Jeremy Kloth <jeremy.kloth+python-tracker at gmail.com> added the comment:

While not getting into the error itself, there seems to be another issue in that the logging that should be happening when the deletion routines from test.support fail:

https://github.com/python/cpython/blob/5bc6a7c06eda20ba131ecba6752be0506d310181/Lib/test/support/__init__.py#L339
https://github.com/python/cpython/blob/5bc6a7c06eda20ba131ecba6752be0506d310181/Lib/test/support/__init__.py#L375

is not showing up when the test is re-run in verbose mode.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38544>
_______________________________________

From report at bugs.python.org  Mon Oct 21 08:12:20 2019
From: report at bugs.python.org (kryptomatrix)
Date: Mon, 21 Oct 2019 12:12:20 +0000
Subject: [issue38548] open() and file.write() without file.close()
Message-ID: <1571659940.93.0.484534204799.issue38548@roundup.psfhosted.org>


New submission from kryptomatrix <volker.weissmann at gmx.de>:

Consider the following program:

f = open("out.txt", "w")
f.write("abc\n")
exit(0)

Please note the absence of f.close().
The documentation 
https://docs.python.org/3/tutorial/inputoutput.html#reading-and-writing-files
says that you should use f.close() or with f = open(), but is not clear whether the program above without f.close() is guaranteed to write. The tutorial says:
"If you don?t explicitly close a file, Python?s garbage collector will eventually destroy the object and close the open file for you, but the file may stay open for a while. Another risk is that different Python implementations will do this clean-up at different times."
For me this sounds like even without f.close() the file is guaranteed to be written. If it is not guaranteed to be written, you should fix the documentation, if it is guaranteed to be written, then I will open another issue because the following program does not write into out.txt on my machine:

from sympy.core import AtomicExpr
class MyWeirdClass(AtomicExpr):
	def __init__(self):
		pass
f = open("out.txt", "w")
f.write("abc\n")
exit(0)

Note: sys.version is: "3.7.3 (default, Oct  7 2019, 12:56:13) \n[GCC 8.3.0]"

----------
assignee: docs at python
components: Documentation
messages: 355062
nosy: docs at python, kryptomatrix
priority: normal
severity: normal
status: open
title: open() and file.write() without file.close()
type: enhancement
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38548>
_______________________________________

From report at bugs.python.org  Mon Oct 21 08:20:44 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 12:20:44 +0000
Subject: [issue38548] open() and file.write() without file.close()
In-Reply-To: <1571659940.93.0.484534204799.issue38548@roundup.psfhosted.org>
Message-ID: <1571660444.1.0.0465525075903.issue38548@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The issue is a duplicate of bpo-17852.

----------
nosy: +vstinner
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Built-in module _io can lose data from buffered files in reference cycles

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38548>
_______________________________________

From report at bugs.python.org  Mon Oct 21 08:21:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 12:21:13 +0000
Subject: [issue17852] Built-in module _io can lose data from buffered files in
 reference cycles
In-Reply-To: <1367048010.96.0.3580561262.issue17852@psf.upfronthosting.co.za>
Message-ID: <1571660473.2.0.161080755421.issue17852@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I marked bpo-38548 as duplicate of this issue. Copy of msg355062:

Consider the following program:

f = open("out.txt", "w")
f.write("abc\n")
exit(0)

Please note the absence of f.close().
The documentation 
https://docs.python.org/3/tutorial/inputoutput.html#reading-and-writing-files
says that you should use f.close() or with f = open(), but is not clear whether the program above without f.close() is guaranteed to write. The tutorial says:
"If you don?t explicitly close a file, Python?s garbage collector will eventually destroy the object and close the open file for you, but the file may stay open for a while. Another risk is that different Python implementations will do this clean-up at different times."
For me this sounds like even without f.close() the file is guaranteed to be written. If it is not guaranteed to be written, you should fix the documentation, if it is guaranteed to be written, then I will open another issue because the following program does not write into out.txt on my machine:

from sympy.core import AtomicExpr
class MyWeirdClass(AtomicExpr):
	def __init__(self):
		pass
f = open("out.txt", "w")
f.write("abc\n")
exit(0)

Note: sys.version is: "3.7.3 (default, Oct  7 2019, 12:56:13) \n[GCC 8.3.0]"

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17852>
_______________________________________

From report at bugs.python.org  Mon Oct 21 09:01:33 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 13:01:33 +0000
Subject: [issue38542] [2.7] Expose _PyGC_generation0 for allowing internal use
 directly from a CPython extension
In-Reply-To: <1571651032.85.0.698320385475.issue38542@roundup.psfhosted.org>
Message-ID: <1571662893.2.0.0613880388416.issue38542@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I think it is too late to add this feature in 2.7. See https://www.python.org/dev/peps/pep-0373/#release-schedule, the feature freeze was 9.5 years ago.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38542>
_______________________________________

From report at bugs.python.org  Mon Oct 21 09:04:08 2019
From: report at bugs.python.org (egaudry)
Date: Mon, 21 Oct 2019 13:04:08 +0000
Subject: [issue38542] [3.7] clean extern PyGC_Head *_PyGC_generation0;
 in Include/objimpl.h
In-Reply-To: <1571651032.85.0.698320385475.issue38542@roundup.psfhosted.org>
Message-ID: <1571663048.85.0.845660878449.issue38542@roundup.psfhosted.org>


egaudry <eg at fft.be> added the comment:

Yes, the only thing that remains to be done is cleaning objimpl.h.

----------
title: [2.7] Expose _PyGC_generation0 for allowing internal use directly from a CPython extension -> [3.7] clean extern PyGC_Head *_PyGC_generation0; in Include/objimpl.h
versions: +Python 3.7 -Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38542>
_______________________________________

From report at bugs.python.org  Mon Oct 21 09:18:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 13:18:13 +0000
Subject: [issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1
 3.x: directory not empty: Scripts\
In-Reply-To: <1571653144.99.0.203555280128.issue38544@roundup.psfhosted.org>
Message-ID: <1571663893.53.0.195079323585.issue38544@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> ... is not showing up when the test is re-run in verbose mode.

_force_run() logs require verbose >= 2. The test suite is run using:

'Tools\\buildbot\\test.bat' '-x64' '-j2' '-j4' '--timeout' '900'

which runs:

C:\buildbot.python.org\3.x.kloth-win64\build>"C:\buildbot.python.org\3.x.kloth-win64\build\PCbuild\amd64\python_d.exe"  -u -Wd -E -bb -m test  -uall -rwW --slowest --timeout 1200 --fail-env-changed -j1 -j2 -j4 --timeout 900 

Using this command, I get: support.verbose=1 in the main regrtest process and in regrtest worker processes.

Maybe _force_run() should always log, or log "if verbose:" (remove ">= 2" restriction).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38544>
_______________________________________

From report at bugs.python.org  Mon Oct 21 09:18:23 2019
From: report at bugs.python.org (Charalampos Stratakis)
Date: Mon, 21 Oct 2019 13:18:23 +0000
Subject: [issue38510] build python with --enable-shared with static linked
 python against libpython*.a
In-Reply-To: <1571345739.37.0.277931445502.issue38510@roundup.psfhosted.org>
Message-ID: <1571663903.15.0.633862589684.issue38510@roundup.psfhosted.org>


Change by Charalampos Stratakis <cstratak at redhat.com>:


----------
nosy: +cstratak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38510>
_______________________________________

From report at bugs.python.org  Mon Oct 21 09:19:58 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 13:19:58 +0000
Subject: [issue38542] [3.7] clean extern PyGC_Head *_PyGC_generation0;
 in Include/objimpl.h
In-Reply-To: <1571651032.85.0.698320385475.issue38542@roundup.psfhosted.org>
Message-ID: <1571663998.55.0.505106925302.issue38542@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The master branch of Python doesn't contain _PyGC_generation0 anymore.

> Yes, the only thing that remains to be done is cleaning objimpl.h.

We don't do cleanup changes in stable branches. Only in the development branch: master. In this case, it's already fixed. So I close the issue.

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38542>
_______________________________________

From report at bugs.python.org  Mon Oct 21 09:35:04 2019
From: report at bugs.python.org (Jeremy Kloth)
Date: Mon, 21 Oct 2019 13:35:04 +0000
Subject: [issue38544] test_venv: test_isolation() failed on AMD64 Windows7 SP1
 3.x: directory not empty: Scripts\
In-Reply-To: <1571653144.99.0.203555280128.issue38544@roundup.psfhosted.org>
Message-ID: <1571664904.71.0.703635648546.issue38544@roundup.psfhosted.org>


Jeremy Kloth <jeremy.kloth+python-tracker at gmail.com> added the comment:

That covers the logging in _force_run(), but the warning.warn() line is also not output, suggesting that the RuntimeWarning is being suppressed somewhere.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38544>
_______________________________________

From report at bugs.python.org  Mon Oct 21 09:42:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 13:42:26 +0000
Subject: [issue38543] [2.7] Expose Py_TabcheckFlag as other PyAPI_DATA flag
In-Reply-To: <1571651180.6.0.332450448454.issue38543@roundup.psfhosted.org>
Message-ID: <1571665346.8.0.0465227172341.issue38543@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Python 2.7 doesn't accept new features anymore. The issue has been closed.

----------
resolution:  -> wont fix

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38543>
_______________________________________

From report at bugs.python.org  Mon Oct 21 10:03:41 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 14:03:41 +0000
Subject: [issue38466] [Easy doc] threading.excepthook doc talks about "object"
In-Reply-To: <1570981226.47.0.762418362865.issue38466@roundup.psfhosted.org>
Message-ID: <1571666621.2.0.179929515168.issue38466@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> https://docs.python.org/3.8/library/threading.html#threading.excepthook

"Storing *object* using a custom hook can resurrect it"
should be
"Storing *thread* using a custom hook can resurrect it"
in Doc/library/threading.rst

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38466>
_______________________________________

From report at bugs.python.org  Mon Oct 21 10:04:04 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 14:04:04 +0000
Subject: [issue38500] Provide a way to get/set PyInterpreterState.frame_eval
 without needing to access interpreter internals
In-Reply-To: <1571242626.68.0.14615334114.issue38500@roundup.psfhosted.org>
Message-ID: <1571666644.7.0.973709711257.issue38500@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +eric.snow

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38500>
_______________________________________

From report at bugs.python.org  Mon Oct 21 10:12:26 2019
From: report at bugs.python.org (Alex Grund)
Date: Mon, 21 Oct 2019 14:12:26 +0000
Subject: [issue38472] GCC detection in setup.py is broken
In-Reply-To: <1571056115.0.0.505317698716.issue38472@roundup.psfhosted.org>
Message-ID: <1571667146.33.0.027524739441.issue38472@roundup.psfhosted.org>


Alex Grund <flamefire89 at gmail.com> added the comment:

This seems to be a locale issue. So a solution would be to use `LC_ALL=C` before invoking the compiler (or the cross-platform equivalent)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38472>
_______________________________________

From report at bugs.python.org  Mon Oct 21 10:21:13 2019
From: report at bugs.python.org (Alex Grund)
Date: Mon, 21 Oct 2019 14:21:13 +0000
Subject: [issue38549] Compiler build paths and related environment variables
 are ignored for native builds
Message-ID: <1571667673.82.0.434242539711.issue38549@roundup.psfhosted.org>


New submission from Alex Grund <flamefire89 at gmail.com>:

In e.g. Linux users can set CPATH and LIBRARY_PATH to a list of paths considered by e.g. GCC, Clang, ... as if they were passed to `-I`, `-L`

These paths show up in the verbose compiler output too.

However in native builds (not cross-compiling) these variables/directories are ignored which leads to failure of e.g. building the BZip2 extension (among others).

Use case: On HPC modules are used, which means e.g. BZip2 is not installed into a system directory but into some other folder and CPATH, LIBRARY_PATH, LD_LIBRARY_PATH, ... are modified so it can be found by compiler and runtime. However the Python build script does not find it as it ignores those "compiler paths".

This did work ages ago, but was broken when it was decided that compiler paths (output of `gcc -E -v`) is no longer used for native builds and that function was later even renamed: https://github.com/python/cpython/commit/32f5fdd7f4213743fe2f6eedd0fe2108f3157021#diff-2eeaed663bd0d25b7e608891384b7298R514

I propose to rename the function back to its original name and use it always.

----------
components: Build
messages: 355073
nosy: Alex Grund
priority: normal
severity: normal
status: open
title: Compiler build paths and related environment variables are ignored for native builds
type: compile error
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38549>
_______________________________________

From report at bugs.python.org  Mon Oct 21 10:27:28 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 14:27:28 +0000
Subject: [issue38472] GCC detection in setup.py is broken
In-Reply-To: <1571056115.0.0.505317698716.issue38472@roundup.psfhosted.org>
Message-ID: <1571668048.86.0.0242952307718.issue38472@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

What are you trying to do? Compile Python? Cross-compile Python?

> `setup.py` runs `<CC> -E -v - </dev/null 1>/dev/null` to figure out include and library paths from the compiler in the function `add_gcc_paths`.

Are you talking about the add_cross_compiling_paths() function which is only called when _PYTHON_HOST_PLATFORM environment variable is set?

So GCC says "gcc-Version 9.1.0 (GCC) " with your locale, but does it write "gcc version 9.1.0 ..." with LC_ALL=C?

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38472>
_______________________________________

From report at bugs.python.org  Mon Oct 21 10:32:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 14:32:13 +0000
Subject: [issue38549] Compiler build paths and related environment variables
 are ignored for native builds
In-Reply-To: <1571667673.82.0.434242539711.issue38549@roundup.psfhosted.org>
Message-ID: <1571668333.53.0.754058916441.issue38549@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> This did work ages ago, but was broken when it was decided that compiler paths (output of `gcc -E -v`) is no longer used for native builds and that function was later even renamed: https://github.com/python/cpython/commit/32f5fdd7f4213743fe2f6eedd0fe2108f3157021#diff-2eeaed663bd0d25b7e608891384b7298R514

Can you please elaborate?

setup.py of Python 2.7:

        if cross_compiling:
            self.add_gcc_paths()

setup.py of Python 3.5:

        # only change this for cross builds for 3.3, issues on Mageia
        if cross_compiling:
            self.add_gcc_paths()

In the 2.7, this code was changed in 2013 to fix bpo-17990:

"For Issue17086, 8ee6d96a1019 backported some cross-build patches to the 2.7 branch.  The changes to setup.py detect_modules differ in the backport from those in default. In particular, in default, changes to the library and include directory lists used to build extensions modules are only made conditionally when cross-compiling.  But the 2.7 backport makes these changes unconditionally."

commit 6166709eec557f52075417b19676dccc9f405fda
Author: Ned Deily <nad at acm.org>
Date:   Wed May 15 18:00:45 2013 -0700

    Issue #17990: Only modify include and library search paths when cross-compiling.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38549>
_______________________________________

From report at bugs.python.org  Mon Oct 21 10:35:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 14:35:20 +0000
Subject: [issue38549] Compiler build paths and related environment variables
 are ignored for native builds
In-Reply-To: <1571667673.82.0.434242539711.issue38549@roundup.psfhosted.org>
Message-ID: <1571668520.19.0.615729517856.issue38549@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> However in native builds (not cross-compiling) these variables/directories are ignored which leads to failure of e.g. building the BZip2 extension (among others).

Python does not explicitly ignore these environment variable, so I'm not sure how setup.py prevent that.

For example, the _bz2 module is built by setup.py by default in the master branch of Python.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38549>
_______________________________________

From report at bugs.python.org  Mon Oct 21 10:48:43 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Mon, 21 Oct 2019 14:48:43 +0000
Subject: [issue38542] [3.7] clean extern PyGC_Head *_PyGC_generation0;
 in Include/objimpl.h
In-Reply-To: <1571651032.85.0.698320385475.issue38542@roundup.psfhosted.org>
Message-ID: <1571669323.9.0.787800490634.issue38542@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

If it's specific to 2.7, why does the Version metadata say 3.7?

----------
nosy: +gvanrossum

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38542>
_______________________________________

From report at bugs.python.org  Mon Oct 21 11:09:20 2019
From: report at bugs.python.org (egaudry)
Date: Mon, 21 Oct 2019 15:09:20 +0000
Subject: [issue38542] [3.7] clean extern PyGC_Head *_PyGC_generation0;
 in Include/objimpl.h
In-Reply-To: <1571651032.85.0.698320385475.issue38542@roundup.psfhosted.org>
Message-ID: <1571670560.56.0.670086272743.issue38542@roundup.psfhosted.org>


egaudry <eg at fft.be> added the comment:

I originally submitted an issue asking for having the symbol exported.

But, as Victor mentioned, this part of the code was changed between 2.7 and 3.x.

I then asked if the part of the code defining the symbol (and not used anymore) in 3.7 could be removed/cleaned. This is why it was tagged back to 3.7.

As it was already removed in newer version (3.8?) and because the policy is not to clean dead-code, this issue is now closed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38542>
_______________________________________

From report at bugs.python.org  Mon Oct 21 11:47:12 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 15:47:12 +0000
Subject: [issue38546] test_concurrent_futures: test_interpreter_shutdown()
 warning "reap_children() reaped child process" on AMD64 RHEL7 3.x
In-Reply-To: <1571656800.65.0.31860297071.issue38546@roundup.psfhosted.org>
Message-ID: <1571672832.03.0.100930575156.issue38546@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I ran "./python -m test --fail-env-changed -w -j50 -F test_concurrent_futures" on my laptop for 5 minutes: system load of 220,57 with a peak of 403 processes... but I failed to reproduce the issue :-(

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38546>
_______________________________________

From report at bugs.python.org  Mon Oct 21 12:00:04 2019
From: report at bugs.python.org (Mike Gilbert)
Date: Mon, 21 Oct 2019 16:00:04 +0000
Subject: [issue38550] hashlib missing algorithms
Message-ID: <1571673604.24.0.668685601916.issue38550@roundup.psfhosted.org>


New submission from Mike Gilbert <floppymaster at gmail.com>:

After upgrading to Python 3.7.5, several algorithms are unavailable in the hashlib module.

This seems to have been caused by the "fix" for https://bugs.python.org/issue33936. I will submit a PR with a more appropriate change shortly.

Python 3.7.4:
>>> hashlib.algorithms_available
{'ripemd160', 'blake2s256', 'sha512', 'sha3-224', 'sha3_224', 'blake2s', 'shake_128', 'sha3-384', 'sha3_384', 'whirlpool', 'md4', 'md5', 'sha512-224', 'sha3-512', 'sha1', 'blake2b', 'sha384', 'md5-sha1', 'sha3-256', 'shake_256', 'mdc2', 'sha224', 'blake2b512', 'shake128', 'sm3', 'sha256', 'shake256', 'sha3_512', 'sha512-256', 'sha3_256'}

Python 3.7.5:
>>> hashlib.algorithms_available
{'sha224', 'sha256', 'sha3_224', 'blake2s', 'md5', 'sha3_256', 'sha384', 'sha3_512', 'sha3_384', 'shake_256', 'blake2b', 'sha512', 'shake_128', 'sha1'}

----------
components: Extension Modules
messages: 355080
nosy: floppymaster
priority: normal
severity: normal
status: open
title: hashlib missing algorithms
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38550>
_______________________________________

From report at bugs.python.org  Mon Oct 21 12:03:35 2019
From: report at bugs.python.org (Mike Gilbert)
Date: Mon, 21 Oct 2019 16:03:35 +0000
Subject: [issue38550] hashlib missing algorithms
In-Reply-To: <1571673604.24.0.668685601916.issue38550@roundup.psfhosted.org>
Message-ID: <1571673815.72.0.623200571413.issue38550@roundup.psfhosted.org>


Change by Mike Gilbert <floppymaster at gmail.com>:


----------
keywords: +patch
pull_requests: +16418
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16873

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38550>
_______________________________________

From report at bugs.python.org  Mon Oct 21 12:38:19 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 21 Oct 2019 16:38:19 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571675899.01.0.953133696998.issue38533@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Can you try installing https://aka.ms/vs/16/release/VC_redist.x64.exe and then see if it makes a difference?

At least one package in 3.8 still contained a dependency on the C++ runtime, which we do not include, and it's possible that 3.7.5 had the same issue. Both will be fixed in the next updates, but the workaround is to install the file above.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Mon Oct 21 12:39:56 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 21 Oct 2019 16:39:56 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1571675996.98.0.843256121429.issue38534@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

> in what's new and the installer, you've referenced KB2533625 instead of KB2533623. Do we have to open a new issue for this minor search and replace fix?

The new issue is opened now, so we can attach a PR to this one.

Contributions welcome - this isn't difficult.

----------
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Mon Oct 21 12:40:06 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 21 Oct 2019 16:40:06 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1571676006.58.0.5070183855.issue38534@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords: +easy, newcomer friendly

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Mon Oct 21 12:43:20 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 21 Oct 2019 16:43:20 +0000
Subject: [issue38537] Python 2.7.17 reports itself as 2.7.16
In-Reply-To: <1571575878.44.0.238301674763.issue38537@roundup.psfhosted.org>
Message-ID: <1571676200.49.0.45106624748.issue38537@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Exactly where were the DLLs installed?

If you had previously done "just for me" and then this time did "all users", the python27.dll for 2.7.17 will be in C:\Windows\SysWow64, which has lower priority than the one in the same directory.

I won't be fixing or even reviewing any issues in the 2.7 installer at this point. If someone else identifies an easy fix, they're welcome to merge it, but if the problem was changing the mode of install then I'd rather leave this as user error (and be thankful that we've reduced the likelihood of that error since 3.5).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38537>
_______________________________________

From report at bugs.python.org  Mon Oct 21 12:48:47 2019
From: report at bugs.python.org (Jon)
Date: Mon, 21 Oct 2019 16:48:47 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571676527.51.0.668544203763.issue38533@roundup.psfhosted.org>


Jon <yourbestfriendjax at gmail.com> added the comment:

When I have some time.  Maybe this weekend.  3.7.4 is working ok right now for production level.  So I didn't bother with anything else yet.

Might help someone else in the meantime though.  Glad to see that someone is taking the complaint seriously :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Mon Oct 21 13:04:40 2019
From: report at bugs.python.org (Michel Desmoulin)
Date: Mon, 21 Oct 2019 17:04:40 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1571657171.34.0.792021334132.issue20443@roundup.psfhosted.org>
Message-ID: <943f2156-b54e-f48b-2eda-9e4a92673f94@gmail.com>


Michel Desmoulin <desmoulinmichel at gmail.com> added the comment:

The relevance of the use case isn't the problem. Even if people had been using it wrong for all this time, the update is still going to break their code if they did use it this way. And if it was possible, of course many people did.

3.7 already broke a few packages by choosing to not do the True/False dance again and make async/await keywords. I took a lot of people by surprise, not because of the issue itself, but because of the change of philosophy compared of what Python had been in the past.

Do we really want to make a habit of breaking a few things at every minor release ?

It's fair to expect, as a user, that any 3.x will be aiming to be forward compatible. This was the case for Python 2.X and was part of the popularity of the language: a reliable tech.

I'm advocating that any breaking change,, even the tiniest, should be behind a __future__ import or a flag, with warnings, and then switched on for good on Python 4.0.

Python is a language, not a simple library. Stability is key. Like Linus Torvald use to say: "do not break user space"

The fact this change is easy to fix and migrate is not a proper reason to ignore this important software rule, IMO. So many people and so much code rely on Python that the tinest glitch may have massive impact down the line.

Not to mention that after a decade of healing from the P2/3 transition, the community needs a rest.

Le 21/10/2019 ? 13:26, STINNER Victor a ?crit?:
>
> STINNER Victor <vstinner at python.org> added the comment:
>
> What is the use case for having a relative sys.argv[0]?
>
> > Isn't that change breaking compat ?
>
> Right. It has been made on purpose. The rationale can be found in the first message of this issue.
>
> ----------
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue20443>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Mon Oct 21 13:18:30 2019
From: report at bugs.python.org (Mariatta)
Date: Mon, 21 Oct 2019 17:18:30 +0000
Subject: [issue38486] Dead links in mailbox doc
In-Reply-To: <1571155336.35.0.351516835001.issue38486@roundup.psfhosted.org>
Message-ID: <1571678310.73.0.242048450972.issue38486@roundup.psfhosted.org>


Mariatta <mariatta at python.org> added the comment:

Seems like we meant to reference to the maildir specification, which used to be hosted in qmail.com

Since qmail is gone, how about we refer to maildir info here? https://wiki2.dovecot.org/MailboxFormat/Maildir

----------
nosy: +Mariatta

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38486>
_______________________________________

From report at bugs.python.org  Mon Oct 21 13:37:22 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 17:37:22 +0000
Subject: [issue31202] Windows pathlib.Path.glob(pattern) fixed part of the
 pattern changed to lowercase whereas it should be unchanged.
In-Reply-To: <1502719052.2.0.11123711046.issue31202@psf.upfronthosting.co.za>
Message-ID: <1571679442.1.0.393866852181.issue31202@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 10ecbadb799ddf3393d1fc80119a3db14724d381 by Serhiy Storchaka in branch 'master':
bpo-31202: Preserve case of literal parts in Path.glob() on Windows. (GH-16860)
https://github.com/python/cpython/commit/10ecbadb799ddf3393d1fc80119a3db14724d381


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31202>
_______________________________________

From report at bugs.python.org  Mon Oct 21 13:37:39 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 Oct 2019 17:37:39 +0000
Subject: [issue31202] Windows pathlib.Path.glob(pattern) fixed part of the
 pattern changed to lowercase whereas it should be unchanged.
In-Reply-To: <1502719052.2.0.11123711046.issue31202@psf.upfronthosting.co.za>
Message-ID: <1571679459.15.0.520332436574.issue31202@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16419
pull_request: https://github.com/python/cpython/pull/16874

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31202>
_______________________________________

From report at bugs.python.org  Mon Oct 21 13:44:21 2019
From: report at bugs.python.org (Ammar Askar)
Date: Mon, 21 Oct 2019 17:44:21 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571679861.38.0.760511700453.issue20443@roundup.psfhosted.org>


Ammar Askar <ammar at ammaraskar.com> added the comment:

I did a quick search to see what code would break from sys.argv[0] going relative

  intext:"sys.argv[0]" ext:py site:github.com
  https://www.google.com/search?q=intext:"sys.argv%5B0%5D"+ext:py+site:github.com

and while most uses of it are to print usage messages. There is potentially code relying on it being a relative path that will break from this change:

* https://github.com/google/python-gflags/blob/4f06c3d0d6cbe9b1fb90ee9fb1c082b3bf9285f6/gflags/flagvalues.py#L868-L869
* https://github.com/HcashOrg/hcOmniEngine/blob/f1acc2ba3640a8e1c651ddc90a86d569d00704fe/msc-cli.py#L12
* https://github.com/vmtk/vmtk/blob/64675f598e31bc6be3d4fba903fb59bf1394f492/PypeS/pyperun.py#L35
* https://github.com/apache/lucene-solr/blob/cfa49401671b5f9958d46c04120df8c7e3f358be/dev-tools/scripts/svnBranchToGit.py#L783

I think Michel and Nick are correct here and the status-quo should be maintained for sys.argv[0]. Michel should not have to enumerate the use cases for a relative sys.argv[0].

----------
nosy: +ammar2

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Mon Oct 21 13:46:30 2019
From: report at bugs.python.org (Christian Heimes)
Date: Mon, 21 Oct 2019 17:46:30 +0000
Subject: [issue38550] hashlib missing algorithms
In-Reply-To: <1571673604.24.0.668685601916.issue38550@roundup.psfhosted.org>
Message-ID: <1571679990.76.0.244162996022.issue38550@roundup.psfhosted.org>


Christian Heimes <lists at cheimes.de> added the comment:

According to OpenSSL documentation it is not necessary to call any init function. All ciphers and all digests are default options.

As of version 1.1.0 OpenSSL will automatically allocate all resources that it needs so no explicit initialisation is required. Similarly it will also automatically deinitialise as required.

OPENSSL_INIT_ADD_ALL_CIPHERS
With this option the library will automatically load and make available all libcrypto ciphers. This option is a default option.

OPENSSL_INIT_ADD_ALL_DIGESTS
With this option the library will automatically load and make available all libcrypto digests. This option is a default option.

https://www.openssl.org/docs/man1.1.0/man3/OPENSSL_init_crypto.html

----------
nosy: +christian.heimes, gregory.p.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38550>
_______________________________________

From report at bugs.python.org  Mon Oct 21 13:50:03 2019
From: report at bugs.python.org (Mike Gilbert)
Date: Mon, 21 Oct 2019 17:50:03 +0000
Subject: [issue38550] hashlib missing algorithms
In-Reply-To: <1571673604.24.0.668685601916.issue38550@roundup.psfhosted.org>
Message-ID: <1571680203.09.0.753780526238.issue38550@roundup.psfhosted.org>


Mike Gilbert <floppymaster at gmail.com> added the comment:

Then the OpenSSL documentation is wrong, or Python is subsequently doing something to disable some algorithms.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38550>
_______________________________________

From report at bugs.python.org  Mon Oct 21 13:57:39 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 Oct 2019 17:57:39 +0000
Subject: [issue31202] Windows pathlib.Path.glob(pattern) fixed part of the
 pattern changed to lowercase whereas it should be unchanged.
In-Reply-To: <1502719052.2.0.11123711046.issue31202@psf.upfronthosting.co.za>
Message-ID: <1571680659.79.0.596554509323.issue31202@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16420
pull_request: https://github.com/python/cpython/pull/16875

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31202>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:02:23 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 18:02:23 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571680943.45.0.852054183749.issue38540@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16421
pull_request: https://github.com/python/cpython/pull/16876

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:10:09 2019
From: report at bugs.python.org (Mike Gilbert)
Date: Mon, 21 Oct 2019 18:10:09 +0000
Subject: [issue38550] hashlib missing algorithms
In-Reply-To: <1571673604.24.0.668685601916.issue38550@roundup.psfhosted.org>
Message-ID: <1571681409.64.0.179188068886.issue38550@roundup.psfhosted.org>


Mike Gilbert <floppymaster at gmail.com> added the comment:

I see that generate_hash_name_list() calls EVP_MD_do_all() which calls  OPENSSL_init_crypto(OPENSSL_INIT_ADD_ALL_DIGESTS, NULL);

I'm not sure why that doesn't do the job here.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38550>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:10:43 2019
From: report at bugs.python.org (Peter Ludemann)
Date: Mon, 21 Oct 2019 18:10:43 +0000
Subject: [issue38551] lib2to3 Grammar.txt doesn't have Python 3.8 grammar
 changes
Message-ID: <1571681443.98.0.927590549429.issue38551@roundup.psfhosted.org>


New submission from Peter Ludemann <peter.ludemann at gmail.com>:

As far as I can tell, the lib2to3/Grammar.txt file in the Python 3.8 release is the same as that of the Python 3.7 release, which means it doesn't have the "walrus" operator and the "/" parameter syntax.

----------
components: 2to3 (2.x to 3.x conversion tool)
messages: 355092
nosy: Peter Ludemann
priority: normal
severity: normal
status: open
title: lib2to3 Grammar.txt doesn't have Python 3.8 grammar changes
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38551>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:10:59 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 18:10:59 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571681459.2.0.672045948479.issue38540@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16422
pull_request: https://github.com/python/cpython/pull/16877

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:12:20 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 Oct 2019 18:12:20 +0000
Subject: [issue31202] Windows pathlib.Path.glob(pattern) fixed part of the
 pattern changed to lowercase whereas it should be unchanged.
In-Reply-To: <1502719052.2.0.11123711046.issue31202@psf.upfronthosting.co.za>
Message-ID: <1571681540.53.0.36847672285.issue31202@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 175abccbbfccb2f6489dc5c73f4630c1b25ce504 by Miss Skeleton (bot) in branch '3.7':
bpo-31202: Preserve case of literal parts in Path.glob() on Windows. (GH-16860)
https://github.com/python/cpython/commit/175abccbbfccb2f6489dc5c73f4630c1b25ce504


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31202>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:14:28 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 21 Oct 2019 18:14:28 +0000
Subject: [issue38551] lib2to3 Grammar.txt doesn't have Python 3.8 grammar
 changes
In-Reply-To: <1571681443.98.0.927590549429.issue38551@roundup.psfhosted.org>
Message-ID: <1571681668.6.0.952220273373.issue38551@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38551>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:16:25 2019
From: report at bugs.python.org (Julin)
Date: Mon, 21 Oct 2019 18:16:25 +0000
Subject: [issue38539] Update demo files
In-Reply-To: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>
Message-ID: <1571681785.28.0.473142985237.issue38539@roundup.psfhosted.org>


Julin <julinshaji02 at gmail.com> added the comment:

Okay. While I'm at it, can I make a few minor change as well? Like

 - Use fstrings
 - change range(0, val) to range(val) as range()'s first argument has default value 0.
 - Change `for i in range(len(groups)):` to enumerated (redemo.py)
 - rename ss1.py to spreadsheet.py (to make its purpose clearer)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:18:05 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 21 Oct 2019 18:18:05 +0000
Subject: [issue31202] Windows pathlib.Path.glob(pattern) fixed part of the
 pattern changed to lowercase whereas it should be unchanged.
In-Reply-To: <1502719052.2.0.11123711046.issue31202@psf.upfronthosting.co.za>
Message-ID: <1571681885.25.0.534547948307.issue31202@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 2f8d4f08e2fa62cd5c3f6f824be3e7513ff87e07 by Miss Skeleton (bot) in branch '3.8':
bpo-31202: Preserve case of literal parts in Path.glob() on Windows. (GH-16860)
https://github.com/python/cpython/commit/2f8d4f08e2fa62cd5c3f6f824be3e7513ff87e07


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31202>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:18:16 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 21 Oct 2019 18:18:16 +0000
Subject: [issue38551] lib2to3 Grammar.txt doesn't have Python 3.8 grammar
 changes
In-Reply-To: <1571681443.98.0.927590549429.issue38551@roundup.psfhosted.org>
Message-ID: <1571681896.68.0.725236421784.issue38551@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

See also https://bugs.python.org/issue36541 which has an open PR to support the walrus operator.

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38551>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:22:57 2019
From: report at bugs.python.org (William Minchin)
Date: Mon, 21 Oct 2019 18:22:57 +0000
Subject: [issue38552] Colored Prompt broken in REPL in Windows in 3.8
Message-ID: <1571682177.17.0.615459893721.issue38552@roundup.psfhosted.org>


New submission from William Minchin <w_minchin at hotmail.com>:

I have a Python startup file that colorizes my prompt. This worked on Python 3.7, but breaks on Python 3.8. I'm on Windows using Powershell 6.2.3, but `cmd` does the same.

Maybe related, but the colorization also failed on Python 3.7 if a virtual environment was active.

I am using `colorama` to provide the ANSI color codes.

The startup files:

```
import sys
import colorama

colorama.init()

_GREEN = colorama.Fore.GREEN
_YELLOW = colorama.Fore.YELLOW
_RESET = colorama.Style.RESET_ALL

print("setting prompt, {}, {}, {}.".format(_GREEN, _YELLOW, _RESET))
sys.ps1 = "{}>>> {}".format(_GREEN, _RESET)
sys.ps2 = "{}... {}".format(_YELLOW, _RESET)
print()
```

----------
components: Windows
files: python_colored_prompt.png
messages: 355097
nosy: MinchinWeb, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Colored Prompt broken in REPL in Windows in 3.8
type: behavior
versions: Python 3.8
Added file: https://bugs.python.org/file48673/python_colored_prompt.png

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38552>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:40:37 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 18:40:37 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571683237.39.0.469039092058.issue38540@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset ccdfeb7e969bf3aafd43dbe6581c30f66f2b0890 by Serhiy Storchaka in branch '2.7':
[2.7] bpo-38540: Fix possible leak in PyArg_Parse for "es#" and "et#". (GH-16869). (GH-16877)
https://github.com/python/cpython/commit/ccdfeb7e969bf3aafd43dbe6581c30f66f2b0890


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 14:41:12 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 18:41:12 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571683272.65.0.532430356834.issue38540@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 928c68eee620cc6b624a195375143c2aa55644a4 by Serhiy Storchaka in branch '3.7':
bpo-38540: Revert a warning if PY_SSIZE_T_CLEAN is not defined. (GH-16876)
https://github.com/python/cpython/commit/928c68eee620cc6b624a195375143c2aa55644a4


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 15:02:08 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Mon, 21 Oct 2019 19:02:08 +0000
Subject: [issue32856] Optimize the `for y in [x]` idiom in comprehensions
In-Reply-To: <1518770483.24.0.467229070634.issue32856@psf.upfronthosting.co.za>
Message-ID: <1571684528.54.0.583922029545.issue32856@roundup.psfhosted.org>


Change by Yury Selivanov <yselivanov at gmail.com>:


----------
nosy:  -yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32856>
_______________________________________

From report at bugs.python.org  Mon Oct 21 15:12:30 2019
From: report at bugs.python.org (Gilles Bardoux)
Date: Mon, 21 Oct 2019 19:12:30 +0000
Subject: [issue37930] make fails when compiling Python 2.6 from source
 (posixmodule.c)
In-Reply-To: <1566568187.35.0.524066802113.issue37930@roundup.psfhosted.org>
Message-ID: <1571685150.46.0.980079307118.issue37930@roundup.psfhosted.org>


Gilles Bardoux <gilles.bardoux at gmail.com> added the comment:

Hi Oguz,
You just need to change one line in Include/objimpl.h: replace "long double dummy" by "double dummy". Enjoy!

--- a/Include/objimpl.h
+++ b/Include/objimpl.h
@@ -248,7 +248,7 @@ typedef union _gc_head {
         union _gc_head *gc_prev;
         Py_ssize_t gc_refs;
     } gc;
-    long double dummy;  /* force worst-case alignment */
+    double dummy;  /* force worst-case alignment */
 } PyGC_Head;
 
 extern PyGC_Head *_PyGC_generation0;

----------
nosy: +gilles.bardoux

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37930>
_______________________________________

From report at bugs.python.org  Mon Oct 21 15:14:40 2019
From: report at bugs.python.org (Eryk Sun)
Date: Mon, 21 Oct 2019 19:14:40 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1571685280.69.0.183589662833.issue38533@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

> At least one package in 3.8 still contained a dependency on the C++ 
> runtime

FWIW, the very first thing that I checked was the dependencies of pythonw.exe, in case maybe I had a dependent DLL that's not distributed with Windows. There's nothing out of the ordinary:

    C:\Program Files\Python37>sigcheck -nobanner pythonw.exe
    C:\Program Files\Python37\pythonw.exe:
            Verified:       Signed
            Signing date:   7:12 PM 10/14/2019
            Publisher:      Python Software Foundation
            Company:        Python Software Foundation
            Description:    Python
            Product:        Python
            Prod version:   3.7.5
            File version:   3.7.5
            MachineType:    64-bit

    C:\Program Files\Python37>dumpbin /nologo /dependents pythonw.exe

    Dump of file pythonw.exe

    File Type: EXECUTABLE IMAGE

      Image has the following dependencies:

        python37.dll
        VCRUNTIME140.dll
        api-ms-win-crt-runtime-l1-1-0.dll
        api-ms-win-crt-math-l1-1-0.dll
        api-ms-win-crt-stdio-l1-1-0.dll
        api-ms-win-crt-locale-l1-1-0.dll
        api-ms-win-crt-heap-l1-1-0.dll
        KERNEL32.dll

      Summary

            1000 .data
            1000 .pdata
            1000 .rdata
            1000 .reloc
           14000 .rsrc
            2000 .text

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Mon Oct 21 15:42:57 2019
From: report at bugs.python.org (PEW's Corner)
Date: Mon, 21 Oct 2019 19:42:57 +0000
Subject: [issue38537] Python 2.7.17 reports itself as 2.7.16
In-Reply-To: <1571575878.44.0.238301674763.issue38537@roundup.psfhosted.org>
Message-ID: <1571686977.95.0.721566160481.issue38537@roundup.psfhosted.org>


PEW's Corner <pewscorner at gmail.com> added the comment:

Yes, the dll now seems to have ended up in c:\windows\syswow64. I have no idea whether I chose "just for me" or "all users" last time (this is a general irritant when having to manually update software on Windows), but I did choose "all users" this time, so your hypothesis is probably correct.

Considering that the user has no easy way to make the correct choice, nor to anticipate the consequences of a wrong choice, the term "user error" doesn't feel right. :-) But I completely understand why you wouldn't want to put much effort into fixing something that is almost dead, and at least *I* now know how to fix the problem when it happens again.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38537>
_______________________________________

From report at bugs.python.org  Mon Oct 21 16:08:39 2019
From: report at bugs.python.org (Mike Gilbert)
Date: Mon, 21 Oct 2019 20:08:39 +0000
Subject: [issue38550] hashlib missing algorithms
In-Reply-To: <1571673604.24.0.668685601916.issue38550@roundup.psfhosted.org>
Message-ID: <1571688519.06.0.346410444658.issue38550@roundup.psfhosted.org>


Mike Gilbert <floppymaster at gmail.com> added the comment:

Ok, so this appears to be working correctly on master. Just the 3.7 branch is broken.

I think this is because we use OBJ_NAME_do_all instead of EVP_MD_do_all in 3.7.

I think backporting https://github.com/python/cpython/pull/16083 to 3.7 would resolve this.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38550>
_______________________________________

From report at bugs.python.org  Mon Oct 21 16:12:38 2019
From: report at bugs.python.org (Zachary Ware)
Date: Mon, 21 Oct 2019 20:12:38 +0000
Subject: [issue38537] 2.7 on Windows: all-users installation does not clear
 previous just-for-me installation
In-Reply-To: <1571575878.44.0.238301674763.issue38537@roundup.psfhosted.org>
Message-ID: <1571688758.92.0.483851953808.issue38537@roundup.psfhosted.org>


Change by Zachary Ware <zachary.ware at gmail.com>:


----------
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed
title: Python 2.7.17 reports itself as 2.7.16 -> 2.7 on Windows: all-users installation does not clear previous just-for-me installation

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38537>
_______________________________________

From report at bugs.python.org  Mon Oct 21 16:52:04 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2019 20:52:04 +0000
Subject: [issue38540] Possible leaks in PyArg_Parse for "es#" and "et#"
In-Reply-To: <1571638830.02.0.0342300206761.issue38540@roundup.psfhosted.org>
Message-ID: <1571691124.71.0.707136063985.issue38540@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38540>
_______________________________________

From report at bugs.python.org  Mon Oct 21 17:29:31 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 21:29:31 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571693371.44.0.959429150107.issue20443@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Nick Coghlan:
> I think that's a valid point regarding sys.argv[0] - it's the import system and code introspection that wants(/needs) absolute paths, whereas sys.argv[0] gets used in situations (e.g. usage messages) where we should retain whatever the OS gave us, since that best reflects what the user entered.

Even before this cases, there were different cases where Python does modify sys.argv:

* "python3 -c code ..." command: Python removes code from sys.argv
* runpy.run_module() and runpy.run_path() replace sys.argv[0] with a filename

At the C level, the Py_GetArgcArgv() function provides the "original" argc and argv: before they are modified.

See open issues:

* bpo-14208 (closed): No way to recover original argv with python -m
* bpo-29857: Provide `sys.executable_argv` for host application's command line arguments
* bpo-26388: Disabling changing sys.argv[0] with runpy.run_module(...alter_sys=True)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Mon Oct 21 17:44:31 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 21:44:31 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571694271.35.0.731718581204.issue20443@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I understand that the discussion is about my commit 3939c321c90283b49eddde762656e4b1940e7150 which changed multiple things:
---
  Python now gets the absolute path of the script filename specified on
  the command line (ex: ``python3 script.py``): the ``__file__`` attribute of
  the ``__main__`` module, ``sys.argv[0]`` and ``sys.path[0]`` become an
  absolute path, rather than a relative path.
---

I understand that the complain is not about sys.modules['__main__'].__file__ nor sys.path[0], but only sys.argv[0].

The sys.argv documentation says:

"The list of command line arguments passed to a Python script. argv[0] is the script name (it is operating system dependent whether this is a full pathname or not)."

https://docs.python.org/dev/library/sys.html#sys.argv

I understand that before my change, sys.argv[0] was sometimes relative, and sometimes absolute. With my change, sys.argv[0] should now always be asolute.

There are cases where an absolute path is preferred. There are cases where a relative path is preferred. I'm trying to understand the scope of the issue.

> https://github.com/google/python-gflags/blob/4f06c3d0d6cbe9b1fb90ee9fb1c082b3bf9285f6/gflags/flagvalues.py#L868-L869

I don't know this code. It seems like sys.argv[0] is used to lookup in a dict, and that dict keys are supposed to be "module names". I don't understand in which cases sys.argv[0] could be a module *name*, since sys.argv[0] seems like a relative or absolute path.

> https://github.com/HcashOrg/hcOmniEngine/blob/f1acc2ba3640a8e1c651ddc90a86d569d00704fe/msc-cli.py#L12

The code starts by sys.argv.pop(0): remove sys.argv[0].

> https://github.com/vmtk/vmtk/blob/64675f598e31bc6be3d4fba903fb59bf1394f492/PypeS/pyperun.py#L35

if sys.argv[0].startswith('pyperun'): ...

I understand that my change broke such test. Did this test work before my change when specifying the absolute path to run the script? Like path/to/pyperun.py rather than pyperun.py? Such code looks fragile: using os.path.basename() would be safer here.

> https://github.com/apache/lucene-solr/blob/cfa49401671b5f9958d46c04120df8c7e3f358be/dev-tools/scripts/svnBranchToGit.py#L783

  home = os.path.expanduser("~")
  svnWorkingCopiesPath = os.path.join(home, "svnwork")
  gitReposPath = os.path.join(home, "gitrepos")
  if sys.argv[0].startswith(svnWorkingCopiesPath) 
     or sys.argv[0].startswith(gitReposPath): ...

On my Linux, os.path.expanduser("~") is an absolute path and so svnWorkingCopiesPath and gitReposPath should be absolute paths, no?

My change made this code more reliable, rather than breaking it, no?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Mon Oct 21 17:54:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 21:54:32 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571694872.77.0.538161686234.issue20443@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Michel Desmoulin: "The relevance of the use case isn't the problem. Even if people had been using it wrong for all this time, the update is still going to break their code if they did use it this way. And if it was possible, of course many people did."

You have to understand that the change has be done to fix some use cases and that Python 3.8.0 has been related with the change.

If we change again the behavior, we will get Python < 3.8.0, Python 3.8.0 and Python > 3.8.0 behaving differently. I would prefer to fully understand all use cases before starting to discuss changing the behavior again.


> 3.7 already broke a few packages by choosing to not do the True/False dance again and make async/await keywords. I took a lot of people by surprise, not because of the issue itself, but because of the change of philosophy compared of what Python had been in the past.

You have to understand that it was known since the start and it was a deliberate choice after balancing advantages and disadvantages.

https://www.python.org/dev/peps/pep-0492/#transition-plan

I'm only aware of a single function in a single project, Twisted. Are you aware of more projects broken by this change? Did it take long to fix them? Balance it with the ability to use async and await in cases which were not possible in Python 3.6 because they were not real keywords. The Python 3.6 grammar was fully of hack to emulate keywords.


> Do we really want to make a habit of breaking a few things at every minor release ?

Usually, incompatible changes are discussed to balance if it's worth it or not.

There is no plan to break all user code just for your pleasure.

For the specific case of argv[0], the discussion occurred here on associated pull requests, and nobody mentioned any risk of backward compatibility.

FYI I'm working on this topic and I just proposed a the PEP 606 "Python Compatibility Version" to propose one possible solution to make incompatible changes less painful to users.


> It's fair to expect, as a user, that any 3.x will be aiming to be forward compatible. This was the case for Python 2.X and was part of the popularity of the language: a reliable tech.

My PEP 606 tries to explain incompatible changes are needed:
https://www.python.org/dev/peps/pep-0606/#the-need-to-evolve-frequently


> Not to mention that after a decade of healing from the P2/3 transition, the community needs a rest.

I understand that but such comment doesn't help the discussion. See my previous comments and please try to help to fill the missing information to help us to take better decisions.

Since Python 3.8.0 has been release, a revert can make things even worse that the current state.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Mon Oct 21 18:33:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2019 22:33:42 +0000
Subject: [issue38546] test_concurrent_futures: test_interpreter_shutdown()
 warning "reap_children() reaped child process" on AMD64 RHEL7 3.x
In-Reply-To: <1571656800.65.0.31860297071.issue38546@roundup.psfhosted.org>
Message-ID: <1571697222.71.0.935830336817.issue38546@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The system load was at 10.02 when the bug occurred:

> https://buildbot.python.org/all/#/builders/254/builds/162

...
0:04:11 load avg: 10.02 [230/419] test_pkgutil passed -- running: test_io (2 min 46 sec), test_capi (1 min 12 sec), test_concurrent_futures (2 min 43 sec), test_mailbox (2 min 40 sec), test_tokenize (30.6 sec)
0:04:12 load avg: 10.02 [231/419] test_getpass passed -- running: test_io (2 min 47 sec), test_capi (1 min 13 sec), test_concurrent_futures (2 min 43 sec), test_mailbox (2 min 41 sec), test_tokenize (31.1 sec)
0:04:12 load avg: 10.02 [232/419] test_sys passed -- running: test_io (2 min 47 sec), test_capi (1 min 13 sec), test_concurrent_futures (2 min 43 sec), test_mailbox (2 min 41 sec), test_tokenize (31.3 sec)
0:04:12 load avg: 10.02 [233/419] test_winconsoleio skipped -- running: test_io (2 min 48 sec), test_capi (1 min 13 sec), test_concurrent_futures (2 min 44 sec), test_mailbox (2 min 41 sec), test_tokenize (31.7 sec)
test_winconsoleio skipped -- test only relevant on win32
0:04:13 load avg: 10.02 [234/419/1] test_concurrent_futures failed (env changed) (2 min 44 sec) -- running: test_io (2 min 48 sec), test_capi (1 min 14 sec), test_mailbox (2 min 42 sec), test_tokenize (32.0 sec)
...
test_crash (test.test_concurrent_futures.ProcessPoolSpawnExecutorDeadlockTest) ... 4.22s ok
test_shutdown_deadlock (test.test_concurrent_futures.ProcessPoolSpawnExecutorDeadlockTest) ... 1.03s ok
test_initializer (test.test_concurrent_futures.ProcessPoolSpawnFailingInitializerTest) ... 0.51s ok
test_initializer (test.test_concurrent_futures.ProcessPoolSpawnInitializerTest) ... 0.54s ok
test_free_reference (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.67s ok
test_killed_child (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.49s ok
test_map (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.56s ok
test_map_chunksize (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.46s ok
test_map_exception (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.46s ok
test_map_timeout (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 6.48s ok
test_max_workers_negative (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.57s ok
test_max_workers_too_large (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... skipped 'Windows-only process limit'
test_no_stale_references (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.56s ok
test_ressources_gced_in_workers (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 1.90s ok
test_shutdown_race_issue12456 (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.54s ok
test_submit (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.52s ok
test_submit_keyword (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.57s ok
test_traceback (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.48s ok
test_context_manager_shutdown (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolShutdownTest) ... 0.03s ok
test_del_shutdown (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolShutdownTest) ... 0.02s ok
test_hang_issue12364 (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolShutdownTest) ... 1.45s ok
test_interpreter_shutdown (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolShutdownTest) ... 1.62s 
Warning -- reap_children() reaped child process 28936
ok
test_processes_terminate (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolShutdownTest) ... 0.47s ok
test_run_after_shutdown (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolShutdownTest) ... 0.00s ok

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38546>
_______________________________________

From report at bugs.python.org  Mon Oct 21 18:34:06 2019
From: report at bugs.python.org (Peter Ludemann)
Date: Mon, 21 Oct 2019 22:34:06 +0000
Subject: [issue36541] Make lib2to3 grammar more closely match Python
In-Reply-To: <1554514880.92.0.277848417721.issue36541@roundup.psfhosted.org>
Message-ID: <1571697246.03.0.476970391452.issue36541@roundup.psfhosted.org>


Peter Ludemann <peter.ludemann at gmail.com> added the comment:

Re: breakage due to changes in structure (https://bugs.python.org/issue36541#msg339669) ... this has already happened in the past (e.g., type annotations and async). 

It's probably a good idea to add some documentation that structure changes can be expected with each release of Python.

----------
nosy: +Peter Ludemann

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36541>
_______________________________________

From report at bugs.python.org  Mon Oct 21 18:39:57 2019
From: report at bugs.python.org (Peter Ludemann)
Date: Mon, 21 Oct 2019 22:39:57 +0000
Subject: [issue38551] lib2to3 Grammar.txt doesn't have Python 3.8 grammar
 changes
In-Reply-To: <1571681443.98.0.927590549429.issue38551@roundup.psfhosted.org>
Message-ID: <1571697597.59.0.943660997894.issue38551@roundup.psfhosted.org>


Peter Ludemann <peter.ludemann at gmail.com> added the comment:

Should I just close this? (I didn't find https://bugs.python.org/issue36541 when I searched, possibly because I used "2to3" instead of "lib2to3" in my search.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38551>
_______________________________________

From report at bugs.python.org  Mon Oct 21 19:53:20 2019
From: report at bugs.python.org (Laurie Opperman)
Date: Mon, 21 Oct 2019 23:53:20 +0000
Subject: [issue38553] Document functools.cached_property supports value
 updating and clearing
Message-ID: <1571702000.84.0.0143851282892.issue38553@roundup.psfhosted.org>


New submission from Laurie Opperman <laurie_opperman at hotmail.com>:

As I discovered during working on bpo-38545, `functools.cached_property` natively supports cached value setting/updating and clearing (via attribute assignment and deletion, respectively) through mechanisms defined in the language for non-data descriptors:

    class A:
        j = 0
    
        @functools.cached_property
        def b(self):
            self.j += 1
            return self.j

    a = A()
    print(a.b)  # 1
    print(a.b)  # 1
    del a.b
    print(a.b)  # 2
    print(a.b)  # 2
    a.b = 42
    print(a.b)  # 42
    print(a.b)  # 42
    del a.b
    print(a.b)  # 3
    print(a.b)  # 3

I propose that this functionality be documented, for two reasons:
1. To notify developers that this functionality is available, and how to access it
2. To notify developers that this functionality needs to be explicitly disabled. This is important as the built-in `property` is the reverse: property setting and deletion needs to be explicitly implemented

Disabling the value can be achieved by subclassing `functools.cached_property` and overriding/implementing `__set__` and `__delete__` to raise:

    class immutable_cached_property(functools.cached_property):
        def __set__(self, instance, value):
            raise AttributeError("can't set attribute")

        def __delete__(self, instance):
            raise AttributeError("can't delete attribute")

Further reading:
- Defining descriptors: https://docs.python.org/3/reference/datamodel.html#implementing-descriptors
- Descriptor how-to: https://docs.python.org/3/howto/descriptor.html
- Class construction: https://docs.python.org/3/reference/datamodel.html#creating-the-class-object

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 355110
nosy: Epic_Wink, docs at python
priority: normal
severity: normal
status: open
title: Document functools.cached_property supports value updating and clearing
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38553>
_______________________________________

From report at bugs.python.org  Mon Oct 21 20:54:22 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Tue, 22 Oct 2019 00:54:22 +0000
Subject: [issue38328] Speed up the creation time of constant list literals.
In-Reply-To: <1569862645.36.0.924344090693.issue38328@roundup.psfhosted.org>
Message-ID: <1571705662.25.0.0114920560835.issue38328@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
pull_requests: +16423
pull_request: https://github.com/python/cpython/pull/16878

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38328>
_______________________________________

From report at bugs.python.org  Mon Oct 21 22:04:59 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 22 Oct 2019 02:04:59 +0000
Subject: [issue38539] Update demo files
In-Reply-To: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>
Message-ID: <1571709899.18.0.0399204572597.issue38539@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Let's just do the rename for ss1.py.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Mon Oct 21 22:20:31 2019
From: report at bugs.python.org (hongweipeng)
Date: Tue, 22 Oct 2019 02:20:31 +0000
Subject: [issue38553] Document functools.cached_property supports value
 updating and clearing
In-Reply-To: <1571702000.84.0.0143851282892.issue38553@roundup.psfhosted.org>
Message-ID: <1571710831.29.0.558996665684.issue38553@roundup.psfhosted.org>


hongweipeng <hongweichen8888 at sina.com> added the comment:

It can be solved by extending propery. `class cached_property(property):` . How about this idea?

----------
nosy: +hongweipeng

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38553>
_______________________________________

From report at bugs.python.org  Mon Oct 21 23:16:04 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Tue, 22 Oct 2019 03:16:04 +0000
Subject: [issue38554] A fatal error in test_descr
Message-ID: <1571714164.19.0.164454938501.issue38554@roundup.psfhosted.org>


New submission from Zackery Spytz <zspytz at gmail.com>:

When running test_descr, I encountered a fatal error!


./python -m test test_descr
0:00:00 load avg: 0.46 Run tests sequentially
0:00:00 load avg: 0.46 [1/1] test_descr
python: Objects/typeobject.c:7318: update_one_slot: Assertion `!PyErr_Occurred()' failed.
Fatal Python error: Aborted

Current thread 0x00007ff22eb72140 (most recent call first):
  File "/home/lubuntu2/cpython/Lib/test/test_descr.py", line 3923 in test_mutable_bases
  File "/home/lubuntu2/cpython/Lib/unittest/case.py", line 617 in _callTestMethod
  File "/home/lubuntu2/cpython/Lib/unittest/case.py", line 663 in run
  File "/home/lubuntu2/cpython/Lib/unittest/case.py", line 725 in __call__
  File "/home/lubuntu2/cpython/Lib/unittest/suite.py", line 122 in run
  File "/home/lubuntu2/cpython/Lib/unittest/suite.py", line 84 in __call__
  File "/home/lubuntu2/cpython/Lib/unittest/suite.py", line 122 in run
  File "/home/lubuntu2/cpython/Lib/unittest/suite.py", line 84 in __call__
  File "/home/lubuntu2/cpython/Lib/test/support/testresult.py", line 162 in run
  File "/home/lubuntu2/cpython/Lib/test/support/__init__.py", line 2032 in _run_suite
  File "/home/lubuntu2/cpython/Lib/test/support/__init__.py", line 2128 in run_unittest
  File "/home/lubuntu2/cpython/Lib/test/test_descr.py", line 5643 in test_main
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/runtest.py", line 234 in _runtest_inner2
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/runtest.py", line 270 in _runtest_inner
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/runtest.py", line 153 in _runtest
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/runtest.py", line 193 in runtest
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/main.py", line 417 in run_tests_sequential
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/main.py", line 515 in run_tests
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/main.py", line 687 in _main
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/main.py", line 634 in main
  File "/home/lubuntu2/cpython/Lib/test/libregrtest/main.py", line 712 in main
  File "/home/lubuntu2/cpython/Lib/test/__main__.py", line 2 in <module>
  File "/home/lubuntu2/cpython/Lib/runpy.py", line 85 in _run_code
  File "/home/lubuntu2/cpython/Lib/runpy.py", line 192 in _run_module_as_main
Aborted (core dumped)

This is because update_all_slots() is called immediately after add_all_subclasses() in type_set_bases(). If an exception occurs in add_all_subclasses() (for example, MemoryError), update_all_slots() will be called with a live exception.

----------
components: Interpreter Core
messages: 355113
nosy: ZackerySpytz
priority: normal
severity: normal
status: open
title: A fatal error in test_descr
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38554>
_______________________________________

From report at bugs.python.org  Mon Oct 21 23:16:10 2019
From: report at bugs.python.org (Laurie Opperman)
Date: Tue, 22 Oct 2019 03:16:10 +0000
Subject: [issue38553] Document functools.cached_property supports value
 updating and clearing
In-Reply-To: <1571702000.84.0.0143851282892.issue38553@roundup.psfhosted.org>
Message-ID: <1571714170.14.0.857174086667.issue38553@roundup.psfhosted.org>


Laurie Opperman <laurie_opperman at hotmail.com> added the comment:

@hongweipeng What can be solved? Do you mean `functools.cached_property` should inherit `property`? First, this would break existing code dependant on the functionality of `functools.cached_property` (admittedly, Python 3.8 was release less than two weeks ago). Second, that seems like arbitrary restriction: I'd prefer just to update the documentation

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38553>
_______________________________________

From report at bugs.python.org  Mon Oct 21 23:20:31 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Tue, 22 Oct 2019 03:20:31 +0000
Subject: [issue38554] A fatal error in test_descr
In-Reply-To: <1571714164.19.0.164454938501.issue38554@roundup.psfhosted.org>
Message-ID: <1571714431.95.0.460227872867.issue38554@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
keywords: +patch
pull_requests: +16424
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16879

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38554>
_______________________________________

From report at bugs.python.org  Mon Oct 21 23:27:33 2019
From: report at bugs.python.org (Laurie Opperman)
Date: Tue, 22 Oct 2019 03:27:33 +0000
Subject: [issue38483] [venv] Add ~/.venvrc to change module defaults
In-Reply-To: <1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>
Message-ID: <1571714853.56.0.554353558963.issue38483@roundup.psfhosted.org>


Laurie Opperman <laurie_opperman at hotmail.com> added the comment:

".xxxxxrc" usually means a file to be run (by a shell) at shell start, and therefore is a script of command to run ("rc" seems to come from "runcom", ie run commands).

INI files usually have a ".ini" or ".cfg" suffix. `virtualenv`, for example, used an INI file similar to your proposal: https://virtualenv.pypa.io/en/stable/reference/#configuration-file.

----------
nosy: +Epic_Wink

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38483>
_______________________________________

From report at bugs.python.org  Mon Oct 21 23:50:22 2019
From: report at bugs.python.org (Cooper Lees)
Date: Tue, 22 Oct 2019 03:50:22 +0000
Subject: [issue38483] [venv] Add ~/.venvrc to change module defaults
In-Reply-To: <1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>
Message-ID: <1571716222.3.0.705568141626.issue38483@roundup.psfhosted.org>


Cooper Lees <me at cooperlees.com> added the comment:

Good point. Happy to match the virtualenv module and use `.ini` if others agree.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38483>
_______________________________________

From report at bugs.python.org  Tue Oct 22 01:03:08 2019
From: report at bugs.python.org (David Bolen)
Date: Tue, 22 Oct 2019 05:03:08 +0000
Subject: [issue38547] test_pty fails when using setsid()
In-Reply-To: <1571657919.98.0.824899649018.issue38547@roundup.psfhosted.org>
Message-ID: <1571720588.9.0.951679173222.issue38547@roundup.psfhosted.org>


Change by David Bolen <db3l.net at gmail.com>:


----------
nosy: +db3l

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38547>
_______________________________________

From report at bugs.python.org  Tue Oct 22 02:02:22 2019
From: report at bugs.python.org (Eryk Sun)
Date: Tue, 22 Oct 2019 06:02:22 +0000
Subject: [issue38483] [venv] Add ~/.venvrc to change module defaults
In-Reply-To: <1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>
Message-ID: <1571724142.55.0.0834160634961.issue38483@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

In Windows, dot files cannot be hidden (i.e. set the hidden file attribute), unlike how they're conventionally hidden in Unix. Doing so breaks normal access. A directory such as ".venv" can be hidden, but that's still going against convention. For Windows, I suggest using "$APPDATA/Python/venv.ini" as the default path. 

Note that, while "$APPDATA/Python" happens to be the base directory for per-user package installations, i.e. site.getuserbase(), I'm not suggesting to use the user base directory as the default in Unix and macOS systems. 

For comparison, pip uses "$APPDATA/pip/pip.ini" in Windows and "$HOME/.config/pip/pip.conf" in Unix. In macOS it prefers "$HOME/Library/Application Support/pip" over "$HOME/.config/pip" if the former exists.

----------
nosy: +eryksun

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38483>
_______________________________________

From report at bugs.python.org  Tue Oct 22 02:09:22 2019
From: report at bugs.python.org (Aldrian Obaja)
Date: Tue, 22 Oct 2019 06:09:22 +0000
Subject: [issue12178] csv writer doesn't escape escapechar
In-Reply-To: <1306348030.98.0.468032848078.issue12178@psf.upfronthosting.co.za>
Message-ID: <1571724562.98.0.0227736991005.issue12178@roundup.psfhosted.org>


Aldrian Obaja <aldrianobaja.m at gmail.com> added the comment:

I think this issue needs to be escalated, as this is clearly a bug that makes it troublesome to use csv.reader and csv.writer with escapechar.

----------
nosy: +Aldrian Obaja

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12178>
_______________________________________

From report at bugs.python.org  Tue Oct 22 02:11:30 2019
From: report at bugs.python.org (Larry Hastings)
Date: Tue, 22 Oct 2019 06:11:30 +0000
Subject: [issue12178] csv writer doesn't escape escapechar
In-Reply-To: <1306348030.98.0.468032848078.issue12178@psf.upfronthosting.co.za>
Message-ID: <1571724690.79.0.411366735495.issue12178@roundup.psfhosted.org>


Change by Larry Hastings <larry at hastings.org>:


----------
versions: +Python 3.8, Python 3.9 -Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12178>
_______________________________________

From report at bugs.python.org  Tue Oct 22 02:12:05 2019
From: report at bugs.python.org (Larry Hastings)
Date: Tue, 22 Oct 2019 06:12:05 +0000
Subject: [issue12178] csv writer doesn't escape escapechar
In-Reply-To: <1306348030.98.0.468032848078.issue12178@psf.upfronthosting.co.za>
Message-ID: <1571724725.32.0.99578589922.issue12178@roundup.psfhosted.org>


Change by Larry Hastings <larry at hastings.org>:


----------
nosy:  -larry

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12178>
_______________________________________

From report at bugs.python.org  Tue Oct 22 03:42:17 2019
From: report at bugs.python.org (Wator Sead)
Date: Tue, 22 Oct 2019 07:42:17 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1571730137.21.0.189742130775.issue38534@roundup.psfhosted.org>


Wator Sead <seahoh at gmail.com> added the comment:

PR16881
I just use the right one to replaced them.

----------
keywords: +patch
message_count: 2.0 -> 3.0
pull_requests: +16425
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16881

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Tue Oct 22 03:57:25 2019
From: report at bugs.python.org (Wator Sead)
Date: Tue, 22 Oct 2019 07:57:25 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1571731045.03.0.349308166486.issue38534@roundup.psfhosted.org>


Wator Sead <seahoh at gmail.com> added the comment:

I can't signe the CLA. Someone will make a new PR.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Tue Oct 22 03:57:47 2019
From: report at bugs.python.org (Wator Sead)
Date: Tue, 22 Oct 2019 07:57:47 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1571731066.99.0.996986554731.issue38534@roundup.psfhosted.org>


Change by Wator Sead <seahoh at gmail.com>:


----------
pull_requests:  -16425

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Tue Oct 22 04:06:56 2019
From: report at bugs.python.org (Sergey Fedoseev)
Date: Tue, 22 Oct 2019 08:06:56 +0000
Subject: [issue38517] functools.cached_property should support partial
 functions and partialmethod's
In-Reply-To: <1571404713.25.0.542654366975.issue38517@roundup.psfhosted.org>
Message-ID: <1571731616.8.0.556863038173.issue38517@roundup.psfhosted.org>


Sergey Fedoseev <fedoseev.sergey at gmail.com> added the comment:

issue38524 is related.

----------
nosy: +sir-sigurd

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38517>
_______________________________________

From report at bugs.python.org  Tue Oct 22 04:13:16 2019
From: report at bugs.python.org (Sergey Fedoseev)
Date: Tue, 22 Oct 2019 08:13:16 +0000
Subject: [issue38524] functools.cached_property is not supported for setattr
In-Reply-To: <1571470251.68.0.879446650629.issue38524@roundup.psfhosted.org>
Message-ID: <1571731996.02.0.938116819316.issue38524@roundup.psfhosted.org>


Change by Sergey Fedoseev <fedoseev.sergey at gmail.com>:


----------
nosy: +sir-sigurd

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38524>
_______________________________________

From report at bugs.python.org  Tue Oct 22 04:23:32 2019
From: report at bugs.python.org (=?utf-8?q?Tymek_Wo=C5=82od=C5=BAko?=)
Date: Tue, 22 Oct 2019 08:23:32 +0000
Subject: [issue38490] statistics: add covariance, Pearson's correlation,
 and simple linear regression
In-Reply-To: <1571175609.51.0.475949905245.issue38490@roundup.psfhosted.org>
Message-ID: <1571732612.06.0.696854663078.issue38490@roundup.psfhosted.org>


Change by Tymek Wo?od?ko <twolodzko at gmail.com>:


----------
title: statistics: add covariance and Pearson's correlation -> statistics: add covariance, Pearson's correlation, and simple linear regression

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38490>
_______________________________________

From report at bugs.python.org  Tue Oct 22 04:35:09 2019
From: report at bugs.python.org (Petr Viktorin)
Date: Tue, 22 Oct 2019 08:35:09 +0000
Subject: [issue38007] Regression: name of PyType_Spec::slots conflicts with Qt
 macro
In-Reply-To: <1567419827.68.0.665093966998.issue38007@roundup.psfhosted.org>
Message-ID: <1571733309.35.0.530201527514.issue38007@roundup.psfhosted.org>


Change by Petr Viktorin <encukou at gmail.com>:


----------
nosy: +petr.viktorin

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38007>
_______________________________________

From report at bugs.python.org  Tue Oct 22 05:31:18 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 22 Oct 2019 09:31:18 +0000
Subject: [issue38555] Undefined behavior in dictreviter_iternext
Message-ID: <1571736678.22.0.114806248729.issue38555@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

&DK_ENTRIES(k)[i] can be evaluated when i is -1. Getting the address before the beginning of the array is an undefined behavior in C.

----------
components: Interpreter Core
messages: 355122
nosy: inada.naoki, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Undefined behavior in dictreviter_iternext
type: behavior
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38555>
_______________________________________

From report at bugs.python.org  Tue Oct 22 05:34:15 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 22 Oct 2019 09:34:15 +0000
Subject: [issue38555] Undefined behavior in dictreviter_iternext
In-Reply-To: <1571736678.22.0.114806248729.issue38555@roundup.psfhosted.org>
Message-ID: <1571736855.25.0.591747041834.issue38555@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

The pointer can also go before the beginning of the array in a loop if i becomes 0.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38555>
_______________________________________

From report at bugs.python.org  Tue Oct 22 05:35:10 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 22 Oct 2019 09:35:10 +0000
Subject: [issue38555] Undefined behavior in dictreviter_iternext
In-Reply-To: <1571736678.22.0.114806248729.issue38555@roundup.psfhosted.org>
Message-ID: <1571736909.99.0.632475120602.issue38555@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16427
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16883

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38555>
_______________________________________

From report at bugs.python.org  Tue Oct 22 08:39:25 2019
From: report at bugs.python.org (EGN)
Date: Tue, 22 Oct 2019 12:39:25 +0000
Subject: [issue38556] Walrus operator in Python 3.8.0 in list comprehensions
Message-ID: <1571747965.17.0.120540707485.issue38556@roundup.psfhosted.org>


New submission from EGN <pilatinum at gmail.com>:

Just tried to use Walrus operator in list comprehensions (for loop) and it is not possible.

Is it a bug?

----------
messages: 355124
nosy: EGN
priority: normal
severity: normal
status: open
title: Walrus operator in Python 3.8.0 in list comprehensions
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38556>
_______________________________________

From report at bugs.python.org  Tue Oct 22 08:40:54 2019
From: report at bugs.python.org (EGN)
Date: Tue, 22 Oct 2019 12:40:54 +0000
Subject: [issue38556] Walrus operator in list comprehensions [Python 3.8.0]
In-Reply-To: <1571747965.17.0.120540707485.issue38556@roundup.psfhosted.org>
Message-ID: <1571748054.22.0.176897336858.issue38556@roundup.psfhosted.org>


Change by EGN <pilatinum at gmail.com>:


----------
title: Walrus operator in Python 3.8.0 in list comprehensions -> Walrus operator in list comprehensions [Python 3.8.0]

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38556>
_______________________________________

From report at bugs.python.org  Tue Oct 22 08:52:58 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 22 Oct 2019 12:52:58 +0000
Subject: [issue38556] Walrus operator in list comprehensions [Python 3.8.0]
In-Reply-To: <1571747965.17.0.120540707485.issue38556@roundup.psfhosted.org>
Message-ID: <1571748778.8.0.764632104774.issue38556@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Can you please post a short snippet of what you are trying to do and the issue you are facing like traceback if any?

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38556>
_______________________________________

From report at bugs.python.org  Tue Oct 22 09:03:41 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Tue, 22 Oct 2019 13:03:41 +0000
Subject: [issue38556] Walrus operator in list comprehensions [Python 3.8.0]
In-Reply-To: <1571747965.17.0.120540707485.issue38556@roundup.psfhosted.org>
Message-ID: <1571749421.26.0.051586084569.issue38556@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

We're not mind-readers, how do you expect us to know what you tried if you don't tell us?

The walrus operator works for me:

    >>> [spam for c in "hello world" if (spam:=c.upper()) in 'AEIOU']
    ['E', 'O', 'O']

    >>> [(spam:=x**2, spam+1) for x in range(5)]
    [(0, 1), (1, 2), (4, 5), (9, 10), (16, 17)]


What did you try, and what happened?

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38556>
_______________________________________

From report at bugs.python.org  Tue Oct 22 09:05:04 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Tue, 22 Oct 2019 13:05:04 +0000
Subject: [issue38556] Walrus operator in list comprehensions [Python 3.8.0]
In-Reply-To: <1571747965.17.0.120540707485.issue38556@roundup.psfhosted.org>
Message-ID: <1571749504.54.0.788369827237.issue38556@roundup.psfhosted.org>


Change by Steven D'Aprano <steve+python at pearwood.info>:


----------
components: +Interpreter Core
type: enhancement -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38556>
_______________________________________

From report at bugs.python.org  Tue Oct 22 09:07:14 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 22 Oct 2019 13:07:14 +0000
Subject: [issue38303] Make audioop PEP-384 compatible
In-Reply-To: <1569676560.78.0.816775553942.issue38303@roundup.psfhosted.org>
Message-ID: <1571749634.88.0.559009007165.issue38303@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset f548a3e4a28c5496755f9f8d057fc8d031b27655 by Miss Skeleton (bot) (Tyler Kieft) in branch 'master':
bpo-38303: Make audioop extension module PEP-384 compatible (GH-16497)
https://github.com/python/cpython/commit/f548a3e4a28c5496755f9f8d057fc8d031b27655


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38303>
_______________________________________

From report at bugs.python.org  Tue Oct 22 09:21:10 2019
From: report at bugs.python.org (Tyler Kieft)
Date: Tue, 22 Oct 2019 13:21:10 +0000
Subject: [issue38303] Make audioop PEP-384 compatible
In-Reply-To: <1569676560.78.0.816775553942.issue38303@roundup.psfhosted.org>
Message-ID: <1571750470.81.0.995010394362.issue38303@roundup.psfhosted.org>


Change by Tyler Kieft <tyler.kieft at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38303>
_______________________________________

From report at bugs.python.org  Tue Oct 22 10:07:20 2019
From: report at bugs.python.org (EGN)
Date: Tue, 22 Oct 2019 14:07:20 +0000
Subject: [issue38556] Walrus operator in list comprehensions [Python 3.8.0]
In-Reply-To: <1571747965.17.0.120540707485.issue38556@roundup.psfhosted.org>
Message-ID: <1571753240.7.0.508463249802.issue38556@roundup.psfhosted.org>


EGN <pilatinum at gmail.com> added the comment:

from os import getcwd, listdir, rename
import re

[rename(f'{p}{n}', f"{p}{''.join([w[:3] if len(w) > 3 else w for w in re.split('[-_. ]', n)[:-1]])}.{n.split('.')[-1]}")
 for n in listdir(p := f"{getcwd()}\\{input('Folder: ')}\\")]

When I run this code, I'm getting:
  File "C:\Users\1\Desktop\sn.py", line 4
    [rename(f'{p}{n}',f"{p}{''.join([w[:3] if len(w)>3 else w for w in re.split('[-_. ]',n)[:-1]])}.{n.split('.')[-1]}") for n in listdir(p:=f"{getcwd()}\\{input('Folder: ')}\\")]
                                                                                                                                         ^
SyntaxError: assignment expression cannot be used in a comprehension iterable expression

Process finished with exit code 1

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38556>
_______________________________________

From report at bugs.python.org  Tue Oct 22 10:11:34 2019
From: report at bugs.python.org (EGN)
Date: Tue, 22 Oct 2019 14:11:34 +0000
Subject: [issue38556] Walrus operator in list comprehensions [Python 3.8.0]
In-Reply-To: <1571747965.17.0.120540707485.issue38556@roundup.psfhosted.org>
Message-ID: <1571753494.3.0.0959845780521.issue38556@roundup.psfhosted.org>


EGN <pilatinum at gmail.com> added the comment:

But if I'm taking main for loop out of the square brackets everything works fine.

from os import getcwd, listdir, rename
import re

for n in listdir(p := f"{getcwd()}\\{input('Folder: ')}\\"):
    [rename(f'{p}{n}', f"{p}{''.join([w[:3] if len(w) > 3 else w for w in re.split('[-_. ]', n)[:-1]])}.{n.split('.')[-1]}")]

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38556>
_______________________________________

From report at bugs.python.org  Tue Oct 22 10:27:09 2019
From: report at bugs.python.org (EGN)
Date: Tue, 22 Oct 2019 14:27:09 +0000
Subject: [issue38556] Walrus operator in list comprehensions [Python 3.8.0]
In-Reply-To: <1571747965.17.0.120540707485.issue38556@roundup.psfhosted.org>
Message-ID: <1571754429.01.0.923935598304.issue38556@roundup.psfhosted.org>


EGN <pilatinum at gmail.com> added the comment:

Even the simple code like this doesn't work:

[print(p) for n in (p := ['a', 'b', 'c'])]

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38556>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:03:49 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 22 Oct 2019 15:03:49 +0000
Subject: [issue33463] Can namedtuple._asdict return a regular dict instead of
 OrderedDict?
In-Reply-To: <1526009463.33.0.682650639539.issue33463@psf.upfronthosting.co.za>
Message-ID: <1571756629.74.0.955974624066.issue33463@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

we can close this (raymond resolved this in bpo-35864)

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33463>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:04:46 2019
From: report at bugs.python.org (Xavier de Gaye)
Date: Tue, 22 Oct 2019 15:04:46 +0000
Subject: [issue28562] test_asyncio fails on Android upon calling getaddrinfo()
In-Reply-To: <1477846363.43.0.193615088108.issue28562@psf.upfronthosting.co.za>
Message-ID: <1571756686.75.0.454574788546.issue28562@roundup.psfhosted.org>


Xavier de Gaye <xdegaye at gmail.com> added the comment:

According to my last post on this issue 2 years ago, this test "does not fail on android-24-x86_64". This means that it does not fail on API level 24. IMO the issue may be closed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28562>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:07:47 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 22 Oct 2019 15:07:47 +0000
Subject: [issue24313] json fails to serialise numpy.int64
In-Reply-To: <1432801951.51.0.0124262456045.issue24313@psf.upfronthosting.co.za>
Message-ID: <1571756867.87.0.745195733326.issue24313@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

What is the next step of this 4-year-old issue? I think i can prepare a patch for using __index__ (as suggested by @r.david.murray)

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24313>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:18:57 2019
From: report at bugs.python.org (Julin)
Date: Tue, 22 Oct 2019 15:18:57 +0000
Subject: [issue38539] Update demo files
In-Reply-To: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>
Message-ID: <1571757537.93.0.420642543999.issue38539@roundup.psfhosted.org>


Change by Julin <julinshaji02 at gmail.com>:


----------
keywords: +patch
pull_requests: +16428
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16890

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:19:17 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 22 Oct 2019 15:19:17 +0000
Subject: [issue25635] urllib2 cannot fully read FTP file
In-Reply-To: <1447681631.39.0.26682578174.issue25635@psf.upfronthosting.co.za>
Message-ID: <1571757557.92.0.964416669143.issue25635@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

It works as expected on master (3.9.0a0). I think we can close this

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue25635>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:20:48 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 22 Oct 2019 15:20:48 +0000
Subject: [issue35448] ConfigParser .read() - handling of nonexistent files
In-Reply-To: <1544373330.85.0.788709270274.issue35448@psf.upfronthosting.co.za>
Message-ID: <1571757648.66.0.778092484841.issue35448@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

Adrian are you still want to work on this or can i take it?

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35448>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:37:18 2019
From: report at bugs.python.org (Julin)
Date: Tue, 22 Oct 2019 15:37:18 +0000
Subject: [issue38539] Update demo files
In-Reply-To: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>
Message-ID: <1571758638.14.0.0130790901561.issue38539@roundup.psfhosted.org>


Julin <julinshaji02 at gmail.com> added the comment:

I've made a PR. Can you review it?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:40:24 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 22 Oct 2019 15:40:24 +0000
Subject: [issue33463] Can namedtuple._asdict return a regular dict instead of
 OrderedDict?
In-Reply-To: <1526009463.33.0.682650639539.issue33463@psf.upfronthosting.co.za>
Message-ID: <1571758824.68.0.968220374655.issue33463@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
resolution:  -> out of date
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33463>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:41:19 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Tue, 22 Oct 2019 15:41:19 +0000
Subject: [issue38554] A fatal error in test_descr
In-Reply-To: <1571714164.19.0.164454938501.issue38554@roundup.psfhosted.org>
Message-ID: <1571758879.82.0.0879980131714.issue38554@roundup.psfhosted.org>


Emmanuel Arias <emmanuelarias30 at gmail.com> added the comment:

I can't reproduce the error

----------
nosy: +eamanu

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38554>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:42:08 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Tue, 22 Oct 2019 15:42:08 +0000
Subject: [issue38554] A fatal error in test_descr
In-Reply-To: <1571714164.19.0.164454938501.issue38554@roundup.psfhosted.org>
Message-ID: <1571758928.94.0.376000817709.issue38554@roundup.psfhosted.org>


Emmanuel Arias <emmanuelarias30 at gmail.com> added the comment:

I' am using:
Python 3.9.0a0 (heads/master:f548a3e4a2, Oct 22 2019, 12:02:14) 
[GCC 6.3.0 20170516]

On Debian 9

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38554>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:46:02 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 22 Oct 2019 15:46:02 +0000
Subject: [issue38556] Walrus operator in list comprehensions [Python 3.8.0]
In-Reply-To: <1571747965.17.0.120540707485.issue38556@roundup.psfhosted.org>
Message-ID: <1571759162.83.0.139224027428.issue38556@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

This is explicitly mentioned in PEP 572 as being disallowed:

"Due to design constraints in the reference implementation (the symbol table analyser cannot easily detect when names are re-used between the leftmost comprehension iterable expression and the rest of the comprehension), named expressions are disallowed entirely as part of comprehension iterable expressions (the part after each "in", and before any subsequent "if" or "for" keyword):"

The error message also makes it clear.

----------
nosy: +eric.smith
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38556>
_______________________________________

From report at bugs.python.org  Tue Oct 22 11:51:00 2019
From: report at bugs.python.org (wim glenn)
Date: Tue, 22 Oct 2019 15:51:00 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
Message-ID: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>


New submission from wim glenn <wim.glenn at gmail.com>:

https://docs.python.org/3/c-api/tuple.html#c.PyTuple_GetSlice

In the c-api it says (emphasis mine):

    PyObject* PyTuple_GetSlice(PyObject *p, Py_ssize_t low, Py_ssize_t high)?
    Return value: New reference.

    Take a slice of the tuple pointed to by p from low to high and return it **as a new tuple**.

But when slicing the entire tuple, CPython will return already existing instance, not a new tuple.

https://github.com/python/cpython/blob/3.8/Objects/tupleobject.c#L448-L451

I propose the language in the docs be loosened so as not to tie the hands of implementation

----------
assignee: docs at python
components: Documentation
messages: 355141
nosy: docs at python, wim.glenn
priority: normal
severity: normal
status: open
title: PyTuple_GetSlice docs minor inaccuracy
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Tue Oct 22 13:16:26 2019
From: report at bugs.python.org (Sebastian Rittau)
Date: Tue, 22 Oct 2019 17:16:26 +0000
Subject: [issue38460] 3.8 Release Notes: document asyncio exception changes
In-Reply-To: <1570969254.43.0.827620904639.issue38460@roundup.psfhosted.org>
Message-ID: <1571764586.68.0.538020998344.issue38460@roundup.psfhosted.org>


Sebastian Rittau <srittau at rittau.biz> added the comment:

Also it seems there are various new arguments and methods in asyncio that are not in the release notes. (Via https://github.com/python/typeshed/issues/2313).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38460>
_______________________________________

From report at bugs.python.org  Tue Oct 22 13:46:42 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 22 Oct 2019 17:46:42 +0000
Subject: [issue24313] json fails to serialise numpy.int64
In-Reply-To: <1432801951.51.0.0124262456045.issue24313@psf.upfronthosting.co.za>
Message-ID: <1571766402.76.0.672131526621.issue24313@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

We could use __index__ for serializing numpy.int64. But what to do with numpy.float32 and numpy.float128? It is a part of a much larger problem (which includes other numbers, collections, encoded strings, named tuples and data classes, etc). I am working on it, but there is a lot of work.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24313>
_______________________________________

From report at bugs.python.org  Tue Oct 22 14:11:42 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Tue, 22 Oct 2019 18:11:42 +0000
Subject: [issue38460] 3.8 Release Notes: document asyncio exception changes
In-Reply-To: <1570969254.43.0.827620904639.issue38460@roundup.psfhosted.org>
Message-ID: <1571767902.21.0.619475413314.issue38460@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

> code that incorrectly imported directly from the submodules will break

That's true. Please note: incorrect code will break. The correct code keeps working.

I'm personally not sure if we need to reflect *private* API change in Release Notes.

Another question is: should Release Notes reflect all API updates? We strictly control `versionadded` and `versionchanged` usage in asyncio docs but don't do it for whatsnew files.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38460>
_______________________________________

From report at bugs.python.org  Tue Oct 22 14:33:05 2019
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 22 Oct 2019 18:33:05 +0000
Subject: [issue38466] [Easy doc] threading.excepthook doc talks about "object"
In-Reply-To: <1570981226.47.0.762418362865.issue38466@roundup.psfhosted.org>
Message-ID: <1571769185.37.0.136265449496.issue38466@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
keywords: +patch
pull_requests: +16430
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16891

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38466>
_______________________________________

From report at bugs.python.org  Tue Oct 22 15:53:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 19:53:55 +0000
Subject: [issue37415] Error build Python with Intel compiler: <stdatomic.h>
 doesn't provide atomic_uintptr_t
In-Reply-To: <1561563167.55.0.111630694926.issue37415@roundup.psfhosted.org>
Message-ID: <1571774035.36.0.337697052365.issue37415@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 028f7349a0f6eaea0fec31becb587fcdf6e3cb28 by Victor Stinner in branch 'master':
bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717)
https://github.com/python/cpython/commit/028f7349a0f6eaea0fec31becb587fcdf6e3cb28


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37415>
_______________________________________

From report at bugs.python.org  Tue Oct 22 15:54:04 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 22 Oct 2019 19:54:04 +0000
Subject: [issue37415] Error build Python with Intel compiler: <stdatomic.h>
 doesn't provide atomic_uintptr_t
In-Reply-To: <1561563167.55.0.111630694926.issue37415@roundup.psfhosted.org>
Message-ID: <1571774044.3.0.186132276142.issue37415@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16431
pull_request: https://github.com/python/cpython/pull/16892

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37415>
_______________________________________

From report at bugs.python.org  Tue Oct 22 15:54:38 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 22 Oct 2019 19:54:38 +0000
Subject: [issue37415] Error build Python with Intel compiler: <stdatomic.h>
 doesn't provide atomic_uintptr_t
In-Reply-To: <1561563167.55.0.111630694926.issue37415@roundup.psfhosted.org>
Message-ID: <1571774078.0.0.181407368322.issue37415@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16432
pull_request: https://github.com/python/cpython/pull/16893

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37415>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:05:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 20:05:59 +0000
Subject: [issue28562] test_asyncio fails on Android upon calling getaddrinfo()
In-Reply-To: <1477846363.43.0.193615088108.issue28562@psf.upfronthosting.co.za>
Message-ID: <1571774759.06.0.070877623401.issue28562@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Ok, thanks Xavier. If someone has an issue with test_asyncio on Android, either reopen this issue or open a new issue ;-)

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28562>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:09:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 20:09:03 +0000
Subject: [issue38447] test_multiprocessing_spawn: Dangling processes:
 {<SpawnProcess(QueueManager-1576, stopped)>} on AMD64 RHEL7 Refleaks 3.7
In-Reply-To: <1570798904.01.0.669672054648.issue38447@roundup.psfhosted.org>
Message-ID: <1571774943.91.0.940428668979.issue38447@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

New failure on AMD64 RHEL7 Refleaks 3.7:

https://buildbot.python.org/all/#/builders/311/builds/34

0:18:35 load avg: 2.24 [414/416/1] test_multiprocessing_spawn failed (env changed) (13 min 55 sec) -- running: test_concurrent_futures (8 min 43 sec), test_asyncio (5 min 48 sec)
beginning 6 repetitions
123456
.Warning -- Dangling processes: {<SpawnProcess(QueueManager-525, stopped)>}
.....

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38447>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:17:26 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 22 Oct 2019 20:17:26 +0000
Subject: [issue37415] Error build Python with Intel compiler: <stdatomic.h>
 doesn't provide atomic_uintptr_t
In-Reply-To: <1561563167.55.0.111630694926.issue37415@roundup.psfhosted.org>
Message-ID: <1571775446.01.0.368917629327.issue37415@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset b102e4f05278c1b06130885eba961bd0193733b4 by Miss Skeleton (bot) in branch '3.7':
bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717)
https://github.com/python/cpython/commit/b102e4f05278c1b06130885eba961bd0193733b4


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37415>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:19:35 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 22 Oct 2019 20:19:35 +0000
Subject: [issue37415] Error build Python with Intel compiler: <stdatomic.h>
 doesn't provide atomic_uintptr_t
In-Reply-To: <1561563167.55.0.111630694926.issue37415@roundup.psfhosted.org>
Message-ID: <1571775575.4.0.449440790551.issue37415@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset dbcea39ba713cc5b31fa1a243b16a0128c231c98 by Miss Skeleton (bot) in branch '3.8':
bpo-37415: Fix stdatomic.h header check for ICC compiler (GH-16717)
https://github.com/python/cpython/commit/dbcea39ba713cc5b31fa1a243b16a0128c231c98


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37415>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:24:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 20:24:32 +0000
Subject: [issue38323] test_ayncio: test_close_kill_running() hangs on AMD64
 RHEL7 Refleaks 3.x
In-Reply-To: <1569848255.08.0.155489980043.issue38323@roundup.psfhosted.org>
Message-ID: <1571775872.24.0.571645123262.issue38323@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Also on x86 Gentoo Refleaks 3.x:

https://buildbot.python.org/all/#/builders/1/builds/754

6:11:43 load avg: 1.44 [419/419/2] test_asyncio crashed (Exit code 1)
beginning 6 repetitions
123456
Timeout (3:15:00)!
Thread 0xb7c4d700 (most recent call first):
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/selectors.py", line 468 in select
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/asyncio/base_events.py", line 1837 in _run_once
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/asyncio/base_events.py", line 589 in run_forever
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/asyncio/base_events.py", line 621 in run_until_complete
  File "/buildbot/buildarea/cpython/3.x.ware-gentoo-x86.refleak/build/Lib/test/test_asyncio/test_subprocess.py", line 484 in test_close_kill_running

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38323>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:24:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 20:24:39 +0000
Subject: [issue38323] test_asyncio: test_close_kill_running() hangs on AMD64
 RHEL7 Refleaks 3.x
In-Reply-To: <1569848255.08.0.155489980043.issue38323@roundup.psfhosted.org>
Message-ID: <1571775879.66.0.860909536233.issue38323@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: test_ayncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x -> test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38323>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:27:12 2019
From: report at bugs.python.org (Matt Ward)
Date: Tue, 22 Oct 2019 20:27:12 +0000
Subject: [issue38558] Data Structures documentation out of sync with new
 Walrus operator
Message-ID: <1571776032.37.0.709698360286.issue38558@roundup.psfhosted.org>


New submission from Matt Ward <matt at matthewward.net>:

The 3.8 documentation still includes the text.

```Note that in Python, unlike C, assignment cannot occur inside expressions. C programmers may grumble about this, but it avoids a common class of problems encountered in C programs: typing = in an expression when == was intended.```

https://docs.python.org/3.8/tutorial/datastructures.html#more-on-conditions

This would seem to no longer be the case with with the inclusion of https://www.python.org/dev/peps/pep-0572/ in 3.8 unless I am misunderstanding the above statement.

----------
assignee: docs at python
components: Documentation
messages: 355151
nosy: Matt Ward, docs at python
priority: normal
severity: normal
status: open
title: Data Structures documentation out of sync with new Walrus operator
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38558>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:27:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 20:27:24 +0000
Subject: [issue37415] Error build Python with Intel compiler: <stdatomic.h>
 doesn't provide atomic_uintptr_t
In-Reply-To: <1561563167.55.0.111630694926.issue37415@roundup.psfhosted.org>
Message-ID: <1571776043.99.0.53219335945.issue37415@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

According to Adam J. Stewart, my PR 16717 fix the Python build on ICC:
https://github.com/python/cpython/pull/16717#issuecomment-544812182

So I merged it in 3.7, 3.8 and master branches.

Adam saw other failures, but it's unrelated issues which should be reported separately.

Thanks for the bug report Borja. It should now be fixed. Until a new Python version is released with the fix, you should either apply the patch manually or use a different compiler. GCC and Clang are well supported on Linux for example.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37415>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:37:52 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 20:37:52 +0000
Subject: [issue38466] [Easy doc] threading.excepthook doc talks about "object"
In-Reply-To: <1570981226.47.0.762418362865.issue38466@roundup.psfhosted.org>
Message-ID: <1571776672.68.0.118957436072.issue38466@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 91528f40c30717563a478920861c81d18da5bf63 by Victor Stinner (Daniel Baskal) in branch 'master':
bpo-38466: Fix threading.excepthook doc (GH-16891)
https://github.com/python/cpython/commit/91528f40c30717563a478920861c81d18da5bf63


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38466>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:37:59 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 22 Oct 2019 20:37:59 +0000
Subject: [issue38466] [Easy doc] threading.excepthook doc talks about "object"
In-Reply-To: <1570981226.47.0.762418362865.issue38466@roundup.psfhosted.org>
Message-ID: <1571776679.43.0.635489393779.issue38466@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16433
pull_request: https://github.com/python/cpython/pull/16894

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38466>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:45:07 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 22 Oct 2019 20:45:07 +0000
Subject: [issue38466] [Easy doc] threading.excepthook doc talks about "object"
In-Reply-To: <1570981226.47.0.762418362865.issue38466@roundup.psfhosted.org>
Message-ID: <1571777107.49.0.940505682833.issue38466@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 6329a56ca7f99075caa95a075024736a90ad2857 by Miss Skeleton (bot) in branch '3.8':
bpo-38466: Fix threading.excepthook doc (GH-16891)
https://github.com/python/cpython/commit/6329a56ca7f99075caa95a075024736a90ad2857


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38466>
_______________________________________

From report at bugs.python.org  Tue Oct 22 16:47:29 2019
From: report at bugs.python.org (Julien Palard)
Date: Tue, 22 Oct 2019 20:47:29 +0000
Subject: [issue38538] dictobject dictviews don't return NotImplemented for
 unrecognized types.
In-Reply-To: <1571585548.13.0.376831813762.issue38538@roundup.psfhosted.org>
Message-ID: <1571777249.22.0.465981484675.issue38538@roundup.psfhosted.org>


Julien Palard <julien+python at palard.fr> added the comment:

> It is not strange since dict.keys() in Python 2.7 returns list.

Oh, ok thanks :)

Do you think that it should be fixed? As it works with sets, I think so:

>>> set() | Ror()
set()

but it's not that simple as the __or__ of dictviews is less strict that the __or__ of set: __or__ of dictview accept any iterable, __or__ of set only accepts sets.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38538>
_______________________________________

From report at bugs.python.org  Tue Oct 22 17:32:03 2019
From: report at bugs.python.org (Adrian Wielgosik)
Date: Tue, 22 Oct 2019 21:32:03 +0000
Subject: [issue35448] ConfigParser .read() - handling of nonexistent files
In-Reply-To: <1544373330.85.0.788709270274.issue35448@psf.upfronthosting.co.za>
Message-ID: <1571779923.15.0.215760356679.issue35448@roundup.psfhosted.org>


Adrian Wielgosik <adrian.wielgosik at gmail.com> added the comment:

Yeah, I lost steam on this issue, sorry. Go ahead :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35448>
_______________________________________

From report at bugs.python.org  Tue Oct 22 17:38:49 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 21:38:49 +0000
Subject: [issue38323] test_asyncio: test_close_kill_running() hangs on AMD64
 RHEL7 Refleaks 3.x
In-Reply-To: <1569848255.08.0.155489980043.issue38323@roundup.psfhosted.org>
Message-ID: <1571780329.27.0.401942187775.issue38323@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I'm able to reproduce the issue locally using the command:

./python -m test test_asyncio --match=test.test_asyncio.test_subprocess.SubprocessMultiLoopWatcherTests.test_close_kill_running -v -F -j20 --timeout=30.0

Example:

...
0:00:47 load avg: 14.35 [287] test_asyncio passed -- running: test_asyncio (31.1 sec)
0:00:47 load avg: 14.35 [288] test_asyncio passed -- running: test_asyncio (31.3 sec)
0:00:47 load avg: 14.35 [289/1] test_asyncio crashed (Exit code 1)
Timeout (0:00:30)!
Thread 0x00007f3bbd098740 (most recent call first):
  File "/home/vstinner/python/master/Lib/selectors.py", line 468 in select
  File "/home/vstinner/python/master/Lib/asyncio/base_events.py", line 1837 in _run_once
  File "/home/vstinner/python/master/Lib/asyncio/base_events.py", line 589 in run_forever
  File "/home/vstinner/python/master/Lib/asyncio/base_events.py", line 621 in run_until_complete
  File "/home/vstinner/python/master/Lib/test/test_asyncio/test_subprocess.py", line 484 in test_close_kill_running
...


I added some debug traces.

Logs when it works:
---
0:01:39 load avg: 21.21 [512] test_asyncio passed -- running: test_asyncio (31.0 sec)
test_close_kill_running (test.test_asyncio.test_subprocess.SubprocessMultiLoopWatcherTests) ... MultiLoopChildWatcher: attach_loop <_UnixSelectorEventLoop running=False closed=False debug=False>
MultiLoopChildWatcher: SIGCHLD signal registered
MultiLoopChildWatcher: attach_loop None
MultiLoopChildWatcher: attach_loop None
MultiLoopChildWatcher: SIGCHLD signal registered
ok

----------------------------------------------------------------------

Ran 1 test in 0.054s

OK
MultiLoopChildWatcher: _do_waitpid 27887
MultiLoopChildWatcher: _do_waitpid (0, 0)
kill 27887 9
MultiLoopChildWatcher: _sig_chld
MultiLoopChildWatcher: _do_waitpid_all
MultiLoopChildWatcher: _do_waitpid 27887
MultiLoopChildWatcher: _do_waitpid (27887, 9)
MultiLoopChildWatcher: _do_waitpid: call (<bound method _UnixSelectorEventLoop._child_watcher_callback of <_UnixSelectorEventLoop running=True closed=False debug=False>>, <_UnixSelectorEventLoop running=True closed=False debug=False>)
---

Logs when it hangs:
---
0:01:40 load avg: 21.21 [514/1] test_asyncio crashed (Exit code 1)
test_close_kill_running (test.test_asyncio.test_subprocess.SubprocessMultiLoopWatcherTests) ... MultiLoopChildWatcher: attach_loop <_UnixSelectorEventLoop running=False closed=False debug=False>
MultiLoopChildWatcher: SIGCHLD signal registered
MultiLoopChildWatcher: _do_waitpid 26010
MultiLoopChildWatcher: _do_waitpid (0, 0)
kill 26010 9
Timeout (0:00:30)!
Thread 0x00007f4b73f35740 (most recent call first):
  File "/home/vstinner/python/master/Lib/selectors.py", line 468 in select
  File "/home/vstinner/python/master/Lib/asyncio/base_events.py", line 1837 in _run_once
  File "/home/vstinner/python/master/Lib/asyncio/base_events.py", line 589 in run_forever
  File "/home/vstinner/python/master/Lib/asyncio/base_events.py", line 621 in run_until_complete
  File "/home/vstinner/python/master/Lib/test/test_asyncio/test_subprocess.py", line 484 in test_close_kill_running
...
---

It seems like sometimes, MultiLoopChildWatcher._sig_chld() is not called.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38323>
_______________________________________

From report at bugs.python.org  Tue Oct 22 17:43:36 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 21:43:36 +0000
Subject: [issue38323] asyncio: MultiLoopWatcher has a race condition
 (test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x)
In-Reply-To: <1569848255.08.0.155489980043.issue38323@roundup.psfhosted.org>
Message-ID: <1571780616.43.0.0229705264016.issue38323@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x -> asyncio: MultiLoopWatcher has a race condition (test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x)

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38323>
_______________________________________

From report at bugs.python.org  Tue Oct 22 17:48:33 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 22 Oct 2019 21:48:33 +0000
Subject: [issue38559] async generators aclose() behavior in 3.8
Message-ID: <1571780913.57.0.640148082181.issue38559@roundup.psfhosted.org>


New submission from Yury Selivanov <yselivanov at gmail.com>:

I believe I might have discovered a problem with asynchronous generators in 3.8.


# Prelude

In Python prior to 3.8 it was possible to overlap running of "asend()" and "athrow()" methods for the same asynchronous generator.

In plain English, it was possible to await on "agen.asend()" while some other coroutine is already awaiting on "agen.asend()".  That created all kinds of problems with asynchronous generators when people used them to implement channels by trying to push values into the same asynchronous generator from different coroutines.  Regular code that used asynchronous generators in plain and non-sophisticated way did not care.

For classic synchronous generators we have a check for preventing overlapping use of "send()" and "throw()" -- the "gi_running" flag.  If the flag is set, both methods raise a RuntimeError saying that "generator already executing".


# Python 3.8

As was discussed in issues #30773 and #32526 we decided to replicate the same behavior for asynchronous generators, mainly:

* add an "ag_running" flag;

* set "ag_running" when "anext()" or "athrow()" begin to rung, and set it off when they are finished executing;

* if the flag is set when we are about to run "anext()" or "athrow()" it means that another coroutine is reusing the same generator object in parallel and so we raise a RuntimeError.


# Problem

Closing a generator involves throwing a GeneratorExit exception into it.  Throwing the exception is done via calling "throw()" for sync generators, and "athrow()" for async generators.

As shown in https://gist.github.com/1st1/d9860cbf6fe2e5d243e695809aea674c, it's an error to close a synchronous generator while it is being iterated.  This is how async generators *started to behave* in 3.8.

The problem is that asyncio's "loop.shutdown_asyncgens()" method tries to shutdown orphan asynchronous generators by calling "aclose()" on them.  The method is public API and is called by "asyncio.run()" automatically.

Prior to 3.8, calling "aclose()" worked (maybe not in the most clean way). A GeneratorExit was thrown into an asynchronous generator regardless of whether it was running or not, aborting the execution.

In 3.8, calling "aclose()" can crash with a RuntimeError.  It's no longer possible to *reliably cancel* a running asynchrounous generator.


# Dilemma

Replicating the behavior of synchronous generators in asynchronous generators seems like the right thing.  But it seems that the requirements for asynchronous generators are different, and 3.8 breaks backwards compat.


# Proposed Solution

We keep "asend()" and "athrow()" as is in 3.8.  They will continue to raise RuntimeError if used in parallel on the same async generator.

We modify "aclose()" to allow it being called in parallel with "asend()" or "athrow()".  This will restore the <3.8 behavior and fix the "loop.shutdown_asyncgens()" method.


Thoughts?

----------
components: Interpreter Core
messages: 355158
nosy: asvetlov, gvanrossum, lukasz.langa, ncoghlan, njs, yselivanov
priority: normal
severity: normal
status: open
title: async generators aclose() behavior in 3.8
type: behavior
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38559>
_______________________________________

From report at bugs.python.org  Tue Oct 22 17:58:23 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 21:58:23 +0000
Subject: [issue38323] asyncio: MultiLoopWatcher has a race condition
 (test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x)
In-Reply-To: <1569848255.08.0.155489980043.issue38323@roundup.psfhosted.org>
Message-ID: <1571781503.23.0.784560615987.issue38323@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It seems like MultiLoopChildWatcher doesn't respect the PEP 475: siginterrupt(False) must not be used. But the following change isn't enough to fix this issue (test_close_kill_running hang).

diff --git a/Lib/asyncio/unix_events.py b/Lib/asyncio/unix_events.py
index d8f653045a..887f837bad 100644
--- a/Lib/asyncio/unix_events.py
+++ b/Lib/asyncio/unix_events.py
@@ -1192,9 +1192,6 @@ class MultiLoopChildWatcher(AbstractChildWatcher):
                                "restore to default handler on watcher close.")
                 self._saved_sighandler = signal.SIG_DFL
 
-            # Set SA_RESTART to limit EINTR occurrences.
-            signal.siginterrupt(signal.SIGCHLD, False)
-
     def _do_waitpid_all(self):
         for pid in list(self._callbacks):
             self._do_waitpid(pid)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38323>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:09:37 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 22 Oct 2019 22:09:37 +0000
Subject: [issue38559] async generators aclose() behavior in 3.8
In-Reply-To: <1571780913.57.0.640148082181.issue38559@roundup.psfhosted.org>
Message-ID: <1571782177.3.0.18136069129.issue38559@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

Just discussed this issue off-list with Nathaniel.  Maybe this isn't as severe as I thought it is.

If we cancel all asyncio tasks before calling `loop.shutdown_asyncgens()` this *probably* becomes a non-issue.  And "asyncio.run()" does just that [1].

Any asynchronous generator ultimately needs a task to iterate it, so if we cancel tasks, we should cancel all asynchronous generators too.  Calling `loop.shutdown_asyncgens()` then ensures that there are no orphan async generators.  The only way (at least known to me) that that could be the case if some tasks ignores cancellation.  

Nathaniel, what do you think about this in the context of Trio?

If anything, we can update asyncio docs explaining the new behavior of async generators and how to use "loop.shutdown_asyncgens()".

[1] https://github.com/python/cpython/blob/91528f40c30717563a478920861c81d18da5bf63/Lib/asyncio/runners.py#L46

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38559>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:19:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 22:19:26 +0000
Subject: [issue38466] [Easy doc] threading.excepthook doc talks about "object"
In-Reply-To: <1570981226.47.0.762418362865.issue38466@roundup.psfhosted.org>
Message-ID: <1571782766.08.0.29058251147.issue38466@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Thanks Daniel Baskal for the fix and Sebastian Rittau for the bug report. The doc is now fixed in 3.8 and master branches.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38466>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:24:17 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 22 Oct 2019 22:24:17 +0000
Subject: [issue32526] Closing async generator while it is running does not
 raise an exception
In-Reply-To: <1515577162.33.0.467229070634.issue32526@psf.upfronthosting.co.za>
Message-ID: <1571783057.0.0.29727929345.issue32526@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

Was fixed as part of #30773.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32526>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:32:52 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 22:32:52 +0000
Subject: [issue38554] A fatal error in test_descr
In-Reply-To: <1571714164.19.0.164454938501.issue38554@roundup.psfhosted.org>
Message-ID: <1571783572.53.0.216083549754.issue38554@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38554>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:35:10 2019
From: report at bugs.python.org (Nathaniel Smith)
Date: Tue, 22 Oct 2019 22:35:10 +0000
Subject: [issue38559] async generators aclose() behavior in 3.8
In-Reply-To: <1571780913.57.0.640148082181.issue38559@roundup.psfhosted.org>
Message-ID: <1571783710.1.0.660341076101.issue38559@roundup.psfhosted.org>


Nathaniel Smith <njs at pobox.com> added the comment:

I think conceptually, cancelling all tasks and waiting for them to exit is the right thing to do. That way you run as much shutdown code as possible in regular context, and also avoid this problem ? if there are no tasks, then there can't be any tasks blocked in __anext__/asend/athrow/aclose, so calling aclose is safe.

This is also the right way to handle it from Trio's perspective ? we always wait for all tasks to exit before exiting our run loop. For asyncio it might be a bit more complicated though so we should think through the trade-offs.

> The only way (at least known to me) that that could be the case if some tasks ignores cancellation.  

Looking at runners.py, it seems like asyncio.run doesn't just call task.cancel(), but actually waits for all tasks to exit. (See the call to gather() inside _cancel_all_tasks.) So I think that does guarantee that by the time we hit shutdown_asyncgens(), we can be certain that all tasks have exited. (If a task ignores cancellation, then that will cause _cancel_all_tasks to hang, so we never reach shutdown_asyncgens at all. Not ideal, but not really our problem either ? if someone complains we just tell them they need to stop ignoring cancellation if they want  their program to shutdown cleanly.)

So I think asyncio.run is actually totally fine with the 3.8.0 behavior. It's only explicit calls to shutdown_asyncgens that might run into this, and I think that's probably OK? If you're calling shutdown_asyncgens by hand then you're kind of taking responsibility for dealing with any subtle issues around shutdown.

And if we did allow aclose() to run at any time, then I worry that that could cause serious problems. Users can call aclose() at will, and it's generally good practice to always call aclose() on your async generators explicitly. So it's entirely possible that users will accidentally call aclose() themselves while they have another task is blocked in __anext__. And in that case.... what do we do?

The aclose call has to consume the generator's frame, by definition. But in the mean time, we still have this __anext__ coroutine object hanging around pointing to the consumed frame, that the task scheduler thinks needs to be resumed at some point in response to some event, and that can cause all kinds of weird situations. The __anext__ might try to resume while the aclose() is running. The __anext__ might get stuck and never resume, because of the code run by aclose() accidentally unregistering the event that was going to wake it up, so you just get a deadlock instead of a useful error. It might cause some other code entirely to crash ? like if the __anext__ was blocked inside a call to 'await queue.get()', then aclose() interrupting that might corrupt the queue's internal state, so the next time some other task calls queue.put() they get an exception or other incorrect behavior. It all seems really tricky and messy to me.

So... this is super subtle and confusing, but I *think* the conclusion is that yeah, 3.8.0 is fine and there's no urgent action needed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38559>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:42:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 22:42:39 +0000
Subject: [issue12598] Move sys variable initialization from import.c to
 sysmodule.c
In-Reply-To: <1311204284.83.0.766064550687.issue12598@psf.upfronthosting.co.za>
Message-ID: <1571784159.16.0.529064949132.issue12598@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

No activity for 7 years, I close the issue.

----------
nosy: +vstinner
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12598>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:44:45 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Tue, 22 Oct 2019 22:44:45 +0000
Subject: [issue38559] async generators aclose() behavior in 3.8
In-Reply-To: <1571780913.57.0.640148082181.issue38559@roundup.psfhosted.org>
Message-ID: <1571784285.32.0.516848606511.issue38559@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

> So I think asyncio.run is actually totally fine with the 3.8.0 behavior.

Yes.  Looks like it.

> It's only explicit calls to shutdown_asyncgens that might run into this, and I think that's probably OK?

Yes.  Calling shutdown_asyncgens after all tasks are cancelled is still useful to cleanup asynchronous generators that were created but not yet GCed or iterated.

> And if we did allow aclose() to run at any time, then I worry that that could cause serious problems. Users can call aclose() at will, and it's generally good practice to always call aclose() on your async generators explicitly. So it's entirely possible that users will accidentally call aclose() themselves while they have another task is blocked in __anext__. And in that case.... what do we do?

I agree.  Avoiding that kind of mess was the main motivation to fix ag_running.

> So... this is super subtle and confusing, but I *think* the conclusion is that yeah, 3.8.0 is fine and there's no urgent action needed.

Let's see if anyone else thinks this might be a problem, but yeah, it seems that the only programs that can suffer from this change are those that don't use 'asyncio.run'.  And if so they should be fixed to explicitly cancel all tasks before calling shutdown_asyncgens.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38559>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:48:36 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 22:48:36 +0000
Subject: [issue17978] Python crashes if Py_Initialize/Py_Finalize are called
 multiple times
In-Reply-To: <1368565468.18.0.0802244129119.issue17978@psf.upfronthosting.co.za>
Message-ID: <1571784516.4.0.349383248202.issue17978@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Program described in msg189250 does not crash on the master branch of Python. The PEP 587 deeply reworked Python initialization code. There is now a preinitialization phase, for example.

Moreover, Programs/_testembed.c has a test calling Py_Initialize()+Py_Finalize() multiple times, and this test calls Py_SetProgramName() as well.

Upgrade to Python 3.8 to get the fix. (I didn't check if Python 3.7 is also fixed.)

----------
nosy: +vstinner
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17978>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:51:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 22:51:02 +0000
Subject: [issue38234] The value of Py_SetPath is not used to populate the
 configuration
In-Reply-To: <1568992794.36.0.557367208602.issue38234@roundup.psfhosted.org>
Message-ID: <1571784662.5.0.842012084011.issue38234@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The initial issue has been fixed, I close the issue.

> I would like to keep the issue open since I plan to do one more change: use PyWideStringList in _PyPathConfig for module_search_paths to support paths which contains DELIM (":" on Unix).

I may use bpo-38353 instead for that. See also bpo-31210.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38234>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:56:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 22:56:32 +0000
Subject: [issue12232] embedded python import cmath
In-Reply-To: <1306888300.23.0.381408538703.issue12232@psf.upfronthosting.co.za>
Message-ID: <1571784992.29.0.522719806325.issue12232@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

No activity since 2011, I close the issue.

----------
nosy: +vstinner
resolution:  -> out of date
stage: test needed -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12232>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:58:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 22:58:57 +0000
Subject: [issue13562] Notes about module load path
In-Reply-To: <1323397324.61.0.220189805252.issue13562@psf.upfronthosting.co.za>
Message-ID: <1571785137.47.0.10974565802.issue13562@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

No activity since 2012, I close the issue.

Moreover, the PEP 587 now provides a clean C API to configure sys.path.

https://docs.python.org/dev/c-api/init_config.html#c.PyConfig.module_search_paths

----------
nosy: +vstinner
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13562>
_______________________________________

From report at bugs.python.org  Tue Oct 22 18:59:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 22:59:42 +0000
Subject: [issue15047] Cygwin install (regen) problem
In-Reply-To: <1339438906.76.0.557865099456.issue15047@psf.upfronthosting.co.za>
Message-ID: <1571785182.66.0.984534829628.issue15047@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

No activity since 2012, I close the issue.

----------
nosy: +vstinner
resolution:  -> out of date
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue15047>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:03:09 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:03:09 +0000
Subject: [issue8787] warnings inside PyRun_SimpleString() display argv[1]
In-Reply-To: <1274536832.39.0.220188636264.issue8787@psf.upfronthosting.co.za>
Message-ID: <1571785389.51.0.918603828889.issue8787@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Fixed in bpo-33375.

commit 11a896652ee98aa44e59ed25237f9efb56635dcf
Author: Thomas Kluyver <takowl at gmail.com>
Date:   Fri Jun 8 21:28:37 2018 +0200

    bpo-33375: Get filename for warnings from frame.f_code.co_filename (GH-6622)
    
    More consistent with how other parts of Python find the filename (e.g. tracebacks and pdb).

----------
nosy: +vstinner
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8787>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:03:21 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:03:21 +0000
Subject: [issue8787] warnings inside PyRun_SimpleString() display argv[1]
In-Reply-To: <1274536832.39.0.220188636264.issue8787@psf.upfronthosting.co.za>
Message-ID: <1571785401.02.0.757161914789.issue8787@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
resolution: fixed -> duplicate
superseder:  -> warnings: get filename from frame.f_code.co_filename

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue8787>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:03:40 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:03:40 +0000
Subject: [issue33375] warnings: get filename from frame.f_code.co_filename
In-Reply-To: <1524847135.79.0.682650639539.issue33375@psf.upfronthosting.co.za>
Message-ID: <1571785420.67.0.922528596502.issue33375@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I closed bpo-8787 as a duplicate of this issue.

----------
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33375>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:08:35 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:08:35 +0000
Subject: [issue12919] Control what module is imported first
In-Reply-To: <1315331616.23.0.265275073086.issue12919@psf.upfronthosting.co.za>
Message-ID: <1571785715.1.0.188181066265.issue12919@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I close the issue since I see disagreement on the feature request.

Modules/getpath.c and PC/getpathp.c use Lib/os.py to detect the stdlib directory.

_PyUnicode_InitEncodings() is the first function importing modules: to import the Python codec of the filesystem encoding. If this import fails, Python now dumps the "path configuration" to help users to debug their setup. See bpo-38236.

Example:

$ PYTHONHOME=/xxx ./python -c pass
Python path configuration:
  PYTHONHOME = '/xxx'
  PYTHONPATH = (not set)
  program name = './python'
  isolated = 0
  environment = 1
  user site = 1
  import site = 1
  sys._base_executable = '/home/vstinner/python/master/python'
  sys.base_prefix = '/xxx'
  sys.base_exec_prefix = '/xxx'
  sys.executable = '/home/vstinner/python/master/python'
  sys.prefix = '/xxx'
  sys.exec_prefix = '/xxx'
  sys.path = [
    '/xxx/lib/python39.zip',
    '/xxx/lib/python3.9',
    '/xxx/lib/python3.9/lib-dynload',
  ]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x00007f845ca19740 (most recent call first):
<no Python frame>

----------
nosy: +vstinner
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12919>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:09:31 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:09:31 +0000
Subject: [issue17922] Crash in clear_weakref
In-Reply-To: <1367912280.08.0.116722269635.issue17922@psf.upfronthosting.co.za>
Message-ID: <1571785771.36.0.339616701984.issue17922@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

There is no activity since 2013. I guess that the user found a way to workaround this crash, or managed to get it fixed. I close the issue.

----------
nosy: +vstinner
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17922>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:11:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:11:39 +0000
Subject: [issue9098] MSYS build fails with `S_IXGRP' undeclared
In-Reply-To: <1277729031.36.0.263470334817.issue9098@psf.upfronthosting.co.za>
Message-ID: <1571785899.29.0.35241154423.issue9098@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

No activity since 2012, I close the issue.

----------
nosy: +vstinner
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue9098>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:15:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:15:00 +0000
Subject: [issue22139] python windows 2.7.8 64-bit did not install
In-Reply-To: <1407238374.16.0.107772681213.issue22139@psf.upfronthosting.co.za>
Message-ID: <1571786100.12.0.560621590549.issue22139@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

No activity since 2016, I close the issue.

----------
nosy: +vstinner
resolution: works for me -> out of date
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22139>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:18:35 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:18:35 +0000
Subject: [issue31074] Startup failure if executable is a \\?\ path on Windows
In-Reply-To: <1501310160.44.0.769037276135.issue31074@psf.upfronthosting.co.za>
Message-ID: <1571786315.13.0.58879445653.issue31074@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I got the same bug recently and I fixed it:

commit dec39716ca93ee2e8d9b94915ece33014eb58e9e
Author: Victor Stinner <vstinner at python.org>
Date:   Mon Sep 30 14:49:34 2019 +0200

    bpo-38322: Fix gotlandmark() of PC/getpathp.c (GH-16489)
    
    Write the filename into a temporary buffer instead of reusing prefix.
    The problem is that join() modifies prefix inplace. If prefix is not
    normalized, join() can make prefix shorter and so gotlandmark()
    does modify prefix instead of returning it unmodified.

----------
nosy: +vstinner
resolution:  -> fixed
stage: test needed -> resolved
status: open -> closed
superseder:  -> Azure Pipelines: appx tests fail: init_fs_encoding: failed to get the Python codec of the filesystem encoding

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31074>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:22:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:22:02 +0000
Subject: [issue13986] ValueError: cannot convert float NaN to integer
In-Reply-To: <1328874238.47.0.897260032056.issue13986@psf.upfronthosting.co.za>
Message-ID: <1571786522.51.0.728346125069.issue13986@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The issue has not been seen since 2017-03-04, I close the issue as out of date.

----------
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13986>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:30:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:30:03 +0000
Subject: [issue33384] Build does not work with closed stdin on NetBSD
In-Reply-To: <1524996995.63.0.682650639539.issue33384@psf.upfronthosting.co.za>
Message-ID: <1571787002.99.0.473688225374.issue33384@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I'm quite that this issue has been fixed by bpo-30225 which is part Python 3.7.4, Python 3.8.0 and newer. I mark the issue as duplicate of bpo-30225. Please reopen the bug if these versions still fail on NetBSD.


commit 1c4670ea0cc3d208121af11b9b973e6bb268e570
Author: Victor Stinner <victor.stinner at gmail.com>
Date:   Thu May 4 00:45:56 2017 +0200

    bpo-30225: Fix is_valid_fd() on macOS Tiger (#1443)
    
    is_valid_fd() now uses fstat() instead of dup() on macOS to return 0
    on a pipe when the other side of the pipe is closed. fstat() fails
    with EBADF in that case, whereas dup() succeed.

----------
nosy: +vstinner
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> EBADF error on x86 Tiger 3.x buildbot
title: Build does not work with closed stdin -> Build does not work with closed stdin on NetBSD

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33384>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:39:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:39:57 +0000
Subject: [issue3367] Uninitialized value read in parsetok.c
In-Reply-To: <1216153264.95.0.467111480464.issue3367@psf.upfronthosting.co.za>
Message-ID: <1571787597.29.0.468672520406.issue3367@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I close the issue, it has been fixed.


I'm no longer able to reproduce the initial issue:

$ ./configure --with-pydebug --with-valgrind
$ make clean
$ make
$ valgrind --suppressions=Misc/valgrind-python.supp ./python 

==2670== Memcheck, a memory error detector
==2670== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==2670== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==2670== Command: ./python
==2670== 
Python 3.9.0a0 (heads/master:91528f40c3, Oct 23 2019, 01:36:01) 
[GCC 9.2.1 20190827 (Red Hat 9.2.1-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> 
>>> exec("")
>>> ^D # CTRL+D
==2670== 
==2670== HEAP SUMMARY:
==2670==     in use at exit: 1,530,371 bytes in 26,288 blocks
==2670==   total heap usage: 49,485 allocs, 23,197 frees, 10,318,174 bytes allocated
==2670== 
==2670== LEAK SUMMARY:
==2670==    definitely lost: 0 bytes in 0 blocks
==2670==    indirectly lost: 0 bytes in 0 blocks
==2670==      possibly lost: 872,665 bytes in 5,936 blocks
==2670==    still reachable: 657,706 bytes in 20,352 blocks
==2670==         suppressed: 0 bytes in 0 blocks
==2670== Rerun with --leak-check=full to see details of leaked memory
==2670== 
==2670== For lists of detected and suppressed errors, rerun with: -s
==2670== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)


Moreover, Python initialization code has been reworked in the PEP 587 implementation to ensure that sys.argv is never empty. If it's called with an empty list, [""] is used instead.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue3367>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:40:58 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:40:58 +0000
Subject: [issue30060] Crash with subinterpreters and Py_NewInterpreter()
In-Reply-To: <1492020071.31.0.759008537591.issue30060@psf.upfronthosting.co.za>
Message-ID: <1571787658.92.0.497283231436.issue30060@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +eric.snow
title: Crash on Py_Finalize if Py_NoSiteFlag is used -> Crash with subinterpreters and Py_NewInterpreter()

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30060>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:42:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:42:02 +0000
Subject: [issue34309] Trouble when reloading extension modules.
In-Reply-To: <1533144973.44.0.56676864532.issue34309@psf.upfronthosting.co.za>
Message-ID: <1571787722.44.0.793383308966.issue34309@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34309>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:47:05 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:47:05 +0000
Subject: [issue16353] add function to os module for getting path to default
 shell
In-Reply-To: <1351473560.4.0.147895276383.issue16353@psf.upfronthosting.co.za>
Message-ID: <1571788025.63.0.618715748561.issue16353@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

This issue has been fixed. The subprocess module now uses '/system/bin/sh' by default on Android thanks to Xavier de Gaye!

----------
nosy: +vstinner
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16353>
_______________________________________

From report at bugs.python.org  Tue Oct 22 19:47:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2019 23:47:24 +0000
Subject: [issue23496] Steps for Android Native Build of Python 3.4.2
In-Reply-To: <1424551617.0.0.291471450783.issue23496@psf.upfronthosting.co.za>
Message-ID: <1571788044.12.0.0470181574915.issue23496@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It seems like attached patches are outdated: Python has been fixed to support Android. For example, Python now uses the UTF-8 codec rather than mbstowcs() to decode byte strings. I'm quite sure that there are still corner cases which are not well supported on Android, but I would suggest to open more specific issues in that case.

----------
nosy: +vstinner
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23496>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:04:05 2019
From: report at bugs.python.org (David Steele)
Date: Wed, 23 Oct 2019 00:04:05 +0000
Subject: [issue12806] argparse: Hybrid help text formatter
In-Reply-To: <1313973978.37.0.422477813424.issue12806@psf.upfronthosting.co.za>
Message-ID: <1571789045.31.0.874462557086.issue12806@roundup.psfhosted.org>


David Steele <dsteele at gmail.com> added the comment:

I came across this thread after making a simple argparse formatter for preserving paragraphs. The submissions here look better than that effort. Here is a quick, hacky look at the patches from one perspective.

I wanted to prefer ParagraphFormatterML, but didn't like that it doesn't appear to wrap bullet lines, and it wrapped help and epilogs to different lengths. For all options I found an initial textwrap.dedent() was needed to get the results I expected. When I did the dedent with ParagraphFormatter*, a subsequent textwrap.indent(" ") hack was needed to restore spaces at the wrap point. FlexiFormatter was incomplete - epilogs weren't affected.

Ultimately, I settled on reworking FlexiFormatter. My version has the following changes:

- Refactor the formatting code out a la ParagraphFormatter, and add to _fill_text() as well, so formatting is available for both epilogs and option help
- Add a leading textwrap.dedent(), to get it to feel more like HelpFormatter.

Note
- The result requires line feed escapes within paragraphs.
- I'm not using the "indent" argument for _fill_text(), with no apparent consequences.
- Automated tests show that FlexiFormatter adds a space to each blank line. I decided that was not a problem

Code is at:
https://github.com/davesteele/argparse_formatter
https://pypi.org/project/argparse-formatter/

Regarding licensing, my contributions (and presumably the others') is addressed by the CLA.

I'd very much like to see something from this thread merged. This looks to me to be good enough. Any objections to a pull request?

----------
nosy: +daves

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12806>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:06:03 2019
From: report at bugs.python.org (Carol Willing)
Date: Wed, 23 Oct 2019 00:06:03 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
In-Reply-To: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>
Message-ID: <1571789163.89.0.189432581806.issue38419@roundup.psfhosted.org>


Carol Willing <willingc at gmail.com> added the comment:


New changeset 20bf8e08a18c0f1eab49c54f3bd56f8364a2f5cc by Carol Willing (AMIR) in branch 'master':
 bpo-38419: fix "check-c-globals" path (GH-16680)
https://github.com/python/cpython/commit/20bf8e08a18c0f1eab49c54f3bd56f8364a2f5cc


----------
nosy: +willingc

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:06:49 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:06:49 +0000
Subject: [issue26693] Exception ignored in: <module 'threading' from
 ...threading.py> in _shutdown, assert tlock.locked()
In-Reply-To: <1459821105.82.0.884891417565.issue26693@psf.upfronthosting.co.za>
Message-ID: <1571789209.38.0.860972979256.issue26693@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Extract of test2.C:
---
  // in main thread
  Py_Initialize();
  PyEval_InitThreads();
  PyEval_SaveThread();

  // creating a new sub-interpreter, in my real app, this would be created
  //   in a sub-thread.
  PyInterpreterState* const mainInterpreterState = PyInterpreterState_New();
  PyThreadState* const taskState = PyThreadState_New(mainInterpreterState);
  PyEval_AcquireThread(taskState);
  PyThreadState * const sub_interp = Py_NewInterpreter();
  PyThreadState_Swap( taskState );
  PyEval_ReleaseThread( taskState );
---

IMO this code is not supported. It creates 3 interpreters:

* Py_Initialize(): good
* PyInterpreterState_New(): partially initialized
* Py_NewInterpreter(): created from the partially initialized interpreter

IMHO PyInterpreterState_New() should never be used outside Python internals. Only Py_NewInterpreter() should be used.

At least, this code now fails since PyInterpreterState_New() configuration (interp->config) is empty/uninitizalized, and so _PySys_InitMain() fails.

Moreover, the example uses PyGILState C API which isn't compatible with subinterpreters yet :-(

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26693>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:06:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:06:56 +0000
Subject: [issue26693] Exception ignored in: <module 'threading' from
 ...threading.py> in _shutdown, assert tlock.locked()
In-Reply-To: <1459821105.82.0.884891417565.issue26693@psf.upfronthosting.co.za>
Message-ID: <1571789216.18.0.655047003125.issue26693@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +eric.snow

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26693>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:11:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:11:30 +0000
Subject: [issue1635741] Py_Finalize() doesn't clear all Python objects at exit
Message-ID: <1571789490.17.0.868873182214.issue1635741@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I tested on the master branch of Python:
---
#include <Python.h>

void func()
{
    Py_Initialize(); Py_Finalize();
    Py_ssize_t cnt = _Py_GetRefTotal();
    printf("sys.gettotalrefcount(): %zd\n", cnt);
}

int main(int argc, char *argv[])
{
    Py_SetProgramName(L"./_testembed");
    for (int i=0; i < 10; i++) {
        func();
    }
}
---

Each iteration leaks around 5,000 Python objects:
---
sys.gettotalrefcount(): 15113
sys.gettotalrefcount(): 19527
sys.gettotalrefcount(): 23941
sys.gettotalrefcount(): 28355
sys.gettotalrefcount(): 32769
sys.gettotalrefcount(): 37183
sys.gettotalrefcount(): 41597
sys.gettotalrefcount(): 46011
sys.gettotalrefcount(): 50425
sys.gettotalrefcount(): 54839
---

----------
nosy: +vstinner
title: Interpreter seems to leak references after finalization -> Py_Finalize() doesn't clear all Python objects at exit
versions: +Python 3.9 -Python 2.7, Python 3.1, Python 3.2

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1635741>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:12:45 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:12:45 +0000
Subject: [issue6741] Garbage collector release method
In-Reply-To: <1250771912.15.0.32080385055.issue6741@psf.upfronthosting.co.za>
Message-ID: <1571789565.95.0.61054279473.issue6741@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

That's basically a duplicate of bpo-1635741.

----------
nosy: +vstinner
resolution:  -> duplicate
stage: test needed -> resolved
status: open -> closed
superseder:  -> Py_Finalize() doesn't clear all Python objects at exit

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue6741>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:12:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:12:59 +0000
Subject: [issue1635741] Py_Finalize() doesn't clear all Python objects at exit
Message-ID: <1571789579.97.0.178220196905.issue1635741@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I marked bpo-6741 as a duplicate of this issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1635741>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:15:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:15:07 +0000
Subject: [issue24770] Py_Finalize() doesn't stop daemon threads
In-Reply-To: <1438409335.5.0.147877338692.issue24770@psf.upfronthosting.co.za>
Message-ID: <1571789707.9.0.184465776157.issue24770@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: Py_Finalize not cleaning up all threads -> Py_Finalize() doesn't stop daemon threads

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24770>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:15:53 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:15:53 +0000
Subject: [issue26888] Multiple memory leaks after raw Py_Initialize and
 Py_Finalize.
In-Reply-To: <1461964498.64.0.249239175864.issue26888@psf.upfronthosting.co.za>
Message-ID: <1571789753.44.0.146786700548.issue26888@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

That's basically a duplicate of bpo-1635741.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Py_Finalize() doesn't clear all Python objects at exit

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26888>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:16:01 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:16:01 +0000
Subject: [issue1635741] Py_Finalize() doesn't clear all Python objects at exit
Message-ID: <1571789761.05.0.941590490866.issue1635741@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I marked bpo-26888 as a duplicate of this issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1635741>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:16:52 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:16:52 +0000
Subject: [issue21387] Memory leaks when embedded interpreter is reinitialized
In-Reply-To: <1398772537.74.0.909134635776.issue21387@psf.upfronthosting.co.za>
Message-ID: <1571789812.55.0.834380891045.issue21387@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Duplicate of bpo-1635741.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Py_Finalize() doesn't clear all Python objects at exit

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21387>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:17:06 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:17:06 +0000
Subject: [issue1635741] Py_Finalize() doesn't clear all Python objects at exit
Message-ID: <1571789826.72.0.391783074623.issue1635741@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I marked bpo-21387 as a duplicate of this issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1635741>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:19:27 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:19:27 +0000
Subject: [issue1635741] Py_Finalize() doesn't clear all Python objects at exit
Message-ID: <1571789967.42.0.154741504733.issue1635741@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

One part of this issue is that all C extensions of the stdlib should be updated to implement the PEP 489 "Multi-phase extension module initialization".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1635741>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:20:42 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Wed, 23 Oct 2019 00:20:42 +0000
Subject: [issue38560] Allow iterable argument unpacking after a keyword
 argument?
Message-ID: <1571790042.34.0.496395652559.issue38560@roundup.psfhosted.org>


New submission from Brandt Bucher <brandtbucher at gmail.com>:

Calls of the form f(name=value, *args) are currently legal syntax. The resulting argument binding is awkward, and almost never does what you want/expect it to:

>>> def f(x, y, z):
...     print(x, y, z)
... 

>>> f(x=0, *(1, 2))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: f() got multiple values for argument 'x'

>>> f(y=0, *(1, 2))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: f() got multiple values for argument 'y'

>>> f(z=0, *(1, 2))
1 2 0

I'm not sure if this is intentional, or an oversight. Every other way of passing positional arguments after keyword arguments results in an error:

f(kwarg=kwarg, arg)  # SyntaxError: positional argument follows keyword argument
f(**kwargs, arg)     # SyntaxError: positional argument follows keyword argument unpacking
f(**kwargs, *args)   # SyntaxError: iterable argument unpacking follows keyword argument unpacking

I think this case should raise a "SyntaxError: iterable argument unpacking follows keyword argument".

I'd like to work on this if we believe it should be changed.

----------
components: Interpreter Core
messages: 355195
nosy: brandtbucher
priority: normal
severity: normal
status: open
title: Allow iterable argument unpacking after a keyword argument?
type: behavior
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38560>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:22:49 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:22:49 +0000
Subject: [issue36107] aarch64 python3 buffer overflow with stack protector on
 rpi3 (alpine linux)
In-Reply-To: <1551113884.84.0.457828150843.issue36107@roundup.psfhosted.org>
Message-ID: <1571790169.21.0.271420906347.issue36107@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> It seems like python 3.7.2 works.

So yeah, use Python 3.7 or newer. Python 3.8 has been released ;-)

> Any idea which commit(s) may have fixed it?

I have no idea.

----------
nosy: +vstinner
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36107>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:26:38 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:26:38 +0000
Subject: [issue12179] Race condition using PyGILState_Ensure on a new thread
In-Reply-To: <1306353494.72.0.953237135168.issue12179@psf.upfronthosting.co.za>
Message-ID: <1571790398.27.0.472792404112.issue12179@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Bug report in 2011. I close this old issue.

----------
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue12179>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:27:31 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 23 Oct 2019 00:27:31 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
In-Reply-To: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>
Message-ID: <1571790451.63.0.027631462602.issue38419@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

Thank you for your contribution AMIR!

@willingc
Thank you for merging PR 16680 Carol :)
I am now closing this issue.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:27:48 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 23 Oct 2019 00:27:48 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
In-Reply-To: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>
Message-ID: <1571790468.49.0.277228675024.issue38419@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:29:24 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 23 Oct 2019 00:29:24 +0000
Subject: [issue38419] The path of check-c-globals.py on README is wrong
In-Reply-To: <1570592885.04.0.292567951687.issue38419@roundup.psfhosted.org>
Message-ID: <1571790564.46.0.47256977971.issue38419@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
assignee: docs at python -> 
components:  -Documentation
nosy:  -docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38419>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:29:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:29:57 +0000
Subject: [issue28202] Python 3.5.1 C API,
 the global variable is not destroyed when delete the module
In-Reply-To: <1474261347.8.0.510026601712.issue28202@psf.upfronthosting.co.za>
Message-ID: <1571790597.65.0.444435630429.issue28202@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> The problem is resolved if call PyGC_Collect() after PyDict_DelItemString(). Is it expected to call PyGC_Collect() here?

Yeah sadly, to handle such reference cycles, you have to trigger an explicit garbage collection.

It doesn't sound like a bug to me.

Python 3.4 made this way better with PEP 442.

Anyway, that's an old issue with no activity since 2016. I close it.

----------
nosy: +vstinner
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28202>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:31:44 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:31:44 +0000
Subject: [issue32026] Memory leaks in Python on Windows
In-Reply-To: <1510677428.51.0.213398074469.issue32026@psf.upfronthosting.co.za>
Message-ID: <1571790704.82.0.897476062055.issue32026@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It's basically a duplicate of bpo-1635741.

----------
resolution:  -> duplicate
stage: test needed -> resolved
status: open -> closed
superseder:  -> Py_Finalize() doesn't clear all Python objects at exit

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32026>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:32:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:32:00 +0000
Subject: [issue1635741] Py_Finalize() doesn't clear all Python objects at exit
Message-ID: <1571790720.97.0.771159316003.issue1635741@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I marked bpo-32026 as a duplicate of this issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue1635741>
_______________________________________

From report at bugs.python.org  Tue Oct 22 20:38:54 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 00:38:54 +0000
Subject: [issue27530] Non-Critical Compiler WARNING: Python Embedding C++11
 does not allow non-constant string literals
In-Reply-To: <1468688744.22.0.0620333802067.issue27530@psf.upfronthosting.co.za>
Message-ID: <1571791134.5.0.763284514322.issue27530@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

This issues has been fixed in Python 3: the second parameter of PyObject_CallMethod() is now a "const char*". Please upgrade to Python 3.

----------
nosy: +vstinner
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27530>
_______________________________________

From report at bugs.python.org  Tue Oct 22 21:33:34 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Wed, 23 Oct 2019 01:33:34 +0000
Subject: [issue27873] multiprocessing.pool.Pool.map should take more than one
 iterable
In-Reply-To: <1472253350.37.0.404019702525.issue27873@psf.upfronthosting.co.za>
Message-ID: <1571794414.15.0.899119674361.issue27873@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> Is it still open? What else needs to be done?

Yes, this patch needs to be translated into a GitHub PR. See https://devguide.python.org/pullrequest/ for more information on our PR workflow if you're not already familiar with it. Since naught101 wrote a patch, we should have their name in "Co-Authored-By" of the final commit to the PR if they have a GitHub account. If not, just mention it in a comment to the PR that they originally wrote the patch. 

Feel free to @mention me when you open the PR so I can help to review it, although this will likely require a final approval from a maintainer of multiprocessing module before it can be merged.

----------
nosy: +aeros

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27873>
_______________________________________

From report at bugs.python.org  Tue Oct 22 21:40:48 2019
From: report at bugs.python.org (Samuel Grayson)
Date: Wed, 23 Oct 2019 01:40:48 +0000
Subject: [issue38561] multiprocessing.Queue fails intermittently with "Broken
 pipe"
Message-ID: <1571794848.94.0.432646449728.issue38561@roundup.psfhosted.org>


New submission from Samuel Grayson <sam.grayson.ubuntu at gmail.com>:

See [this SO post for more details](https://stackoverflow.com/q/51680479/1078199)

----------
components: Library (Lib)
files: test.py
messages: 355204
nosy: Samuel Grayson
priority: normal
severity: normal
status: open
title: multiprocessing.Queue fails intermittently with "Broken pipe"
versions: Python 3.6, Python 3.7, Python 3.8
Added file: https://bugs.python.org/file48674/test.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38561>
_______________________________________

From report at bugs.python.org  Tue Oct 22 23:23:52 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 23 Oct 2019 03:23:52 +0000
Subject: [issue38539] Update demo files
In-Reply-To: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>
Message-ID: <1571801032.43.0.0679812404582.issue38539@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset a4aeb336697c85996d781271cc6b42bc6d4c2908 by Raymond Hettinger (Julin S) in branch 'master':
bpo-38539: Update demo files (GH-16890)
https://github.com/python/cpython/commit/a4aeb336697c85996d781271cc6b42bc6d4c2908


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Tue Oct 22 23:24:08 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 23 Oct 2019 03:24:08 +0000
Subject: [issue38539] Update demo files
In-Reply-To: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>
Message-ID: <1571801048.65.0.732966882723.issue38539@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Tue Oct 22 23:38:10 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 23 Oct 2019 03:38:10 +0000
Subject: [issue38539] Update demo files
In-Reply-To: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>
Message-ID: <1571801890.42.0.395927824097.issue38539@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
pull_requests: +16434
pull_request: https://github.com/python/cpython/pull/16896

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Tue Oct 22 23:42:54 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 23 Oct 2019 03:42:54 +0000
Subject: [issue38460] 3.8 Release Notes: document asyncio exception changes
In-Reply-To: <1570969254.43.0.827620904639.issue38460@roundup.psfhosted.org>
Message-ID: <1571802174.06.0.942118053093.issue38460@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

> I'm personally not sure if we need to reflect *private*
> API change in Release Notes

The whatsnew 3.8 document is for significant changes to public APIs.  The changelog (built from the news entries) has much more extensive detail.  The main docs are where we put versionadded/versionchanged so that there is a source for knowing which features run in which versions of Python.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38460>
_______________________________________

From report at bugs.python.org  Wed Oct 23 00:05:10 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 23 Oct 2019 04:05:10 +0000
Subject: [issue38539] Update demo files
In-Reply-To: <1571599055.13.0.42950539659.issue38539@roundup.psfhosted.org>
Message-ID: <1571803510.89.0.343797469413.issue38539@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset ea6041cd7ff0d752296d1759927eff898ceba864 by Raymond Hettinger in branch 'master':
bpo-38539:  Finish rename of ss1.py to spreadsheet.py (GH-16896)
https://github.com/python/cpython/commit/ea6041cd7ff0d752296d1759927eff898ceba864


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38539>
_______________________________________

From report at bugs.python.org  Wed Oct 23 01:01:21 2019
From: report at bugs.python.org (Ayse)
Date: Wed, 23 Oct 2019 05:01:21 +0000
Subject: [issue38562] pip install --upgrade git submodule update --recursive
 does not exist
Message-ID: <1571806881.21.0.49403497643.issue38562@roundup.psfhosted.org>


New submission from Ayse <adogan at okstate.edu>:

Hi, 

I was trying to apply a github code, for that I need to get this first:git clone --recursive https://github.com/rbgirshick/py-faster-rcnn.git  but it when I run this it is saying this:
PS C:\Users\Ayse Dogan> python -m pip install --user --upgrade git clone --recursive https://github.com/rbgirshick/py-faste
r-rcnn.git

Usage:
  C:\ProgramData\Anaconda3\python.exe -m pip install [options] <requirement specifier> [package-index-options] ...
  C:\ProgramData\Anaconda3\python.exe -m pip install [options] -r <requirements file> [package-index-options] ...
  C:\ProgramData\Anaconda3\python.exe -m pip install [options] [-e] <vcs project url> ...
  C:\ProgramData\Anaconda3\python.exe -m pip install [options] [-e] <local project path> ...
  C:\ProgramData\Anaconda3\python.exe -m pip install [options] <archive url/path> ...

no such option: --recursive

As I see from Issue35135 this was happening for some other packages. 
Could you please help me about it?

Sincerely, 
Ayse

----------
components: Installation
messages: 355208
nosy: aysedogan, docs at python, pgacv2, xtreak
priority: normal
severity: normal
status: open
title: pip install --upgrade git submodule update --recursive does not exist
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38562>
_______________________________________

From report at bugs.python.org  Wed Oct 23 01:45:05 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Wed, 23 Oct 2019 05:45:05 +0000
Subject: [issue37025] Misleading error message "Python failed to load the
 default activation context"
In-Reply-To: <1558646019.4.0.18611977167.issue37025@roundup.psfhosted.org>
Message-ID: <1571809505.23.0.420709130522.issue37025@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
pull_requests: +16435
pull_request: https://github.com/python/cpython/pull/16897

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37025>
_______________________________________

From report at bugs.python.org  Wed Oct 23 02:21:25 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 23 Oct 2019 06:21:25 +0000
Subject: [issue38562] pip install --upgrade git submodule update --recursive
 does not exist
In-Reply-To: <1571806881.21.0.49403497643.issue38562@roundup.psfhosted.org>
Message-ID: <1571811685.74.0.586693470739.issue38562@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Thanks for the report. As noted in the linked issue this tracker is for issues related to CPython. pip has it's own issue tracker in GitHub : https://github.com/pypa/pip . I am closing it as third party.

Possibly related : https://github.com/pypa/pip/issues/289

----------
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38562>
_______________________________________

From report at bugs.python.org  Wed Oct 23 02:24:49 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 23 Oct 2019 06:24:49 +0000
Subject: [issue38558] Data Structures documentation out of sync with new
 Walrus operator
In-Reply-To: <1571776032.37.0.709698360286.issue38558@roundup.psfhosted.org>
Message-ID: <1571811889.96.0.484446704784.issue38558@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +emilyemorehouse

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38558>
_______________________________________

From report at bugs.python.org  Wed Oct 23 06:12:12 2019
From: report at bugs.python.org (Carlton Gibson)
Date: Wed, 23 Oct 2019 10:12:12 +0000
Subject: [issue34687] asyncio: is it time to make ProactorEventLoop as the
 default event loop?
In-Reply-To: <1536953717.98.0.956365154283.issue34687@psf.upfronthosting.co.za>
Message-ID: <1571825532.43.0.73539907645.issue34687@roundup.psfhosted.org>


Carlton Gibson <carlton.gibson at noumenal.es> added the comment:

This change causes an issue in asgiref (and so Django) for Windows and Python 3.8. 

https://github.com/django/asgiref/issues/132
https://code.djangoproject.com/ticket/30900

It looks as if `ProactorEventLoop` needs to check the current thread before triggering the signal... 

```
File "C:\Jenkins\workspace\django-windows\database\sqlite3\label\windows\python\Python38\.env\lib\site-packages\asgiref\sync.py", line 130, in _run_event_loop
File "C:\Python38\lib\asyncio\proactor_events.py", line 679, in close
    signal.set_wakeup_fd(-1)
ValueError: set_wakeup_fd only works in main thread
```

... but I'm not familiar with the internals here as yet. 

(I'm guessing I need to create a new issue?)

----------
nosy: +carltongibson

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34687>
_______________________________________

From report at bugs.python.org  Wed Oct 23 06:20:15 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 10:20:15 +0000
Subject: [issue34687] asyncio: is it time to make ProactorEventLoop as the
 default event loop?
In-Reply-To: <1536953717.98.0.956365154283.issue34687@psf.upfronthosting.co.za>
Message-ID: <1571826015.34.0.647597950515.issue34687@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> (I'm guessing I need to create a new issue?)

Please open a new issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34687>
_______________________________________

From report at bugs.python.org  Wed Oct 23 07:48:12 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 23 Oct 2019 11:48:12 +0000
Subject: [issue38555] Undefined behavior in dictreviter_iternext
In-Reply-To: <1571736678.22.0.114806248729.issue38555@roundup.psfhosted.org>
Message-ID: <1571831292.87.0.030183910732.issue38555@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 2e3d873d3bd0ef4708c4fa06b6cd6972574cb9af by Serhiy Storchaka in branch 'master':
bpo-38555: Fix an undefined behavior. (GH-16883)
https://github.com/python/cpython/commit/2e3d873d3bd0ef4708c4fa06b6cd6972574cb9af


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38555>
_______________________________________

From report at bugs.python.org  Wed Oct 23 07:48:24 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Oct 2019 11:48:24 +0000
Subject: [issue38555] Undefined behavior in dictreviter_iternext
In-Reply-To: <1571736678.22.0.114806248729.issue38555@roundup.psfhosted.org>
Message-ID: <1571831304.11.0.212968815253.issue38555@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16436
pull_request: https://github.com/python/cpython/pull/16900

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38555>
_______________________________________

From report at bugs.python.org  Wed Oct 23 08:07:26 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Oct 2019 12:07:26 +0000
Subject: [issue38555] Undefined behavior in dictreviter_iternext
In-Reply-To: <1571736678.22.0.114806248729.issue38555@roundup.psfhosted.org>
Message-ID: <1571832446.38.0.0683734892136.issue38555@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset c5d3ea89ee5244714f221dcfcd3be96de2f1da8d by Miss Skeleton (bot) in branch '3.8':
bpo-38555: Fix an undefined behavior. (GH-16883)
https://github.com/python/cpython/commit/c5d3ea89ee5244714f221dcfcd3be96de2f1da8d


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38555>
_______________________________________

From report at bugs.python.org  Wed Oct 23 08:13:28 2019
From: report at bugs.python.org (Carlton Gibson)
Date: Wed, 23 Oct 2019 12:13:28 +0000
Subject: [issue38563] Asyncio regression on Windows with Python 3.8
Message-ID: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>


New submission from Carlton Gibson <carlton.gibson at noumenal.es>:

6ea29c5e90dde6c240bd8e0815614b52ac307ea1 for 
https://bugs.python.org/issue34687

"Make asynico use ProactorEventLoop by default"

This introducesd a regression in asgiref, and hence Django 3.0.x. 


https://github.com/django/asgiref/issues/132
https://code.djangoproject.com/ticket/30900


The error from the asgiref issue is clearest: 

```
asgiref\sync.py:97: in __call__
    loop_future.result()
..\..\..\AppData\Local\Programs\Python\Python38\lib\concurrent\futures\_base.py:432: in result
    return self.__get_result()
..\..\..\AppData\Local\Programs\Python\Python38\lib\concurrent\futures\_base.py:388: in __get_result
    raise self._exception
..\..\..\AppData\Local\Programs\Python\Python38\lib\concurrent\futures\thread.py:57: in run
    result = self.fn(*self.args, **self.kwargs)
asgiref\sync.py:130: in _run_event_loop
    loop.close()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _  

self = <ProactorEventLoop running=False closed=False debug=False>

    def close(self):
        if self.is_running():
            raise RuntimeError("Cannot close a running event loop")
        if self.is_closed():
            return
    
>       signal.set_wakeup_fd(-1)
E       ValueError: set_wakeup_fd only works in main thread
```

Off the main thread, we use a ThreadPoolExecutor and wait for the future to finish. 

It looks as if `ProactorEventLoop` needs to check the current thread before triggering the signal in close().

----------
components: asyncio
messages: 355214
nosy: asvetlov, carltongibson, yselivanov
priority: normal
severity: normal
status: open
title: Asyncio regression on Windows with Python 3.8
type: crash
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 08:14:41 2019
From: report at bugs.python.org (Carlton Gibson)
Date: Wed, 23 Oct 2019 12:14:41 +0000
Subject: [issue34687] asyncio: is it time to make ProactorEventLoop as the
 default event loop?
In-Reply-To: <1536953717.98.0.956365154283.issue34687@psf.upfronthosting.co.za>
Message-ID: <1571832881.98.0.665358756995.issue34687@roundup.psfhosted.org>


Carlton Gibson <carlton.gibson at noumenal.es> added the comment:

Created: https://bugs.python.org/issue38563 

Thanks!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34687>
_______________________________________

From report at bugs.python.org  Wed Oct 23 08:18:44 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 23 Oct 2019 12:18:44 +0000
Subject: [issue38555] Undefined behavior in dictreviter_iternext
In-Reply-To: <1571736678.22.0.114806248729.issue38555@roundup.psfhosted.org>
Message-ID: <1571833124.44.0.157941938781.issue38555@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38555>
_______________________________________

From report at bugs.python.org  Wed Oct 23 08:19:39 2019
From: report at bugs.python.org (Mariusz Felisiak)
Date: Wed, 23 Oct 2019 12:19:39 +0000
Subject: [issue38563] Asyncio regression on Windows with Python 3.8
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571833179.41.0.532155190463.issue38563@roundup.psfhosted.org>


Change by Mariusz Felisiak <felisiak.mariusz at gmail.com>:


----------
nosy: +Mariusz Felisiak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 08:22:43 2019
From: report at bugs.python.org (Carlton Gibson)
Date: Wed, 23 Oct 2019 12:22:43 +0000
Subject: [issue38563] Asyncio regression on Windows with Python 3.8
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571833363.48.0.47129087995.issue38563@roundup.psfhosted.org>


Carlton Gibson <carlton.gibson at noumenal.es> added the comment:

Reproduce steps, on Windows with Python 3.8.0, and a clean venv. 

git clone https://github.com/django/asgiref.git
cd asgiref
pip install -e .[tests]
py.test .

----------
nosy:  -Mariusz Felisiak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 08:41:38 2019
From: report at bugs.python.org (Mariusz Felisiak)
Date: Wed, 23 Oct 2019 12:41:38 +0000
Subject: [issue38563] Asyncio regression on Windows with Python 3.8
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571834498.2.0.128576728547.issue38563@roundup.psfhosted.org>


Change by Mariusz Felisiak <felisiak.mariusz at gmail.com>:


----------
nosy: +Mariusz Felisiak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 09:12:30 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Wed, 23 Oct 2019 13:12:30 +0000
Subject: [issue38563] Asyncio regression on Windows with Python 3.8
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571836350.08.0.472321768919.issue38563@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

Pull Request is welcome!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 09:12:37 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Wed, 23 Oct 2019 13:12:37 +0000
Subject: [issue38563] Asyncio regression on Windows with Python 3.8
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571836357.24.0.934546522763.issue38563@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


----------
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 09:35:16 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 23 Oct 2019 13:35:16 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571837716.4.0.528856626311.issue20443@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

This change isn't in Python 3.8 though, it's only in Python 3.9 (the PR merge date is after the beta 1 branch date).

Unless it was backported in a Python 3.8 PR that didn't link back to this issue or the original Python 3.9 PR?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:14:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 14:14:55 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571840095.88.0.879200411531.issue20443@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> This change isn't in Python 3.8 though, it's only in Python 3.9 (the PR merge date is after the beta 1 branch date).

Oh, you're right. Sorry, I thought that I made the change before 3.8 branch was created. In that case, we can do whatever we want :-) (We are free to revert.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:18:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 14:18:55 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571840335.88.0.504016098148.issue38563@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: Asyncio regression on Windows with Python 3.8 -> ProactorEventLoop.close(): set_wakeup_fd() only works in main thread

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:27:17 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 14:27:17 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571840837.87.0.219314617634.issue38563@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16438
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16901

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:27:17 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 14:27:17 +0000
Subject: [issue34679] asyncio.add_signal_handler call fails if not on main
 thread
In-Reply-To: <1536938865.53.0.956365154283.issue34679@psf.upfronthosting.co.za>
Message-ID: <1571840837.59.0.220278506941.issue34679@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16437
pull_request: https://github.com/python/cpython/pull/16901

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34679>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:28:41 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 14:28:41 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571840921.25.0.727687458797.issue38563@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

That's basically the same issue than bpo-34679 but on close() rather than on creating the event loop.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:42:33 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 14:42:33 +0000
Subject: [issue37224] test__xxsubinterpreters fails randomly
In-Reply-To: <1560214681.61.0.906498246375.issue37224@roundup.psfhosted.org>
Message-ID: <1571841753.99.0.184453894519.issue37224@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

AMD64 FreeBSD Shared 3.x:

https://buildbot.python.org/all/#/builders/371/builds/7

test_subinterpreter (test.test__xxsubinterpreters.IsRunningTests) ... Exception in thread Thread-8:
Traceback (most recent call last):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/threading.py", line 944, in _bootstrap_inner
    self.run()
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/threading.py", line 882, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test__xxsubinterpreters.py", line 51, in run
    interpreters.run_string(interp, dedent(f"""
RuntimeError: unrecognized interpreter ID 46
FAIL

test_already_running (test.test__xxsubinterpreters.RunStringTests) ... Exception in thread Thread-9:
Traceback (most recent call last):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/threading.py", line 944, in _bootstrap_inner
    self.run()
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/threading.py", line 882, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test__xxsubinterpreters.py", line 51, in run
    interpreters.run_string(interp, dedent(f"""
RuntimeError: interpreter already running
FAIL


======================================================================
FAIL: test_subinterpreter (test.test__xxsubinterpreters.IsRunningTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test__xxsubinterpreters.py", line 492, in test_subinterpreter
    self.assertTrue(interpreters.is_running(interp))
AssertionError: False is not true

======================================================================
FAIL: test_already_running (test.test__xxsubinterpreters.RunStringTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test__xxsubinterpreters.py", line 853, in test_already_running
    interpreters.run_string(self.id, 'print("spam")')
AssertionError: RuntimeError not raised

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37224>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:43:13 2019
From: report at bugs.python.org (Carlton Gibson)
Date: Wed, 23 Oct 2019 14:43:13 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571841793.72.0.45120509715.issue38563@roundup.psfhosted.org>


Carlton Gibson <carlton.gibson at noumenal.es> added the comment:

Thanks for the speedy patch Victor. Great effort!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:44:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 14:44:20 +0000
Subject: [issue38564] test_asyncio:
 test_run_coroutine_threadsafe_with_timeout()
Message-ID: <1571841860.24.0.514293762677.issue38564@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

AMD64 FreeBSD Shared 3.x:
https://buildbot.python.org/all/#/builders/371/builds/7

This buildbot worker is known to be very slow.

test_run_coroutine_threadsafe_with_timeout (test.test_asyncio.test_tasks.RunCoroutineThreadsafeTests)
Test coroutine submission from a thread to an event loop ... FAIL

FAIL: test_run_coroutine_threadsafe_with_timeout (test.test_asyncio.test_tasks.RunCoroutineThreadsafeTests)
Test coroutine submission from a thread to an event loop
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/home/buildbot/python/3.x.koobs-freebsd-564d/build/Lib/test/test_asyncio/test_tasks.py", line 3210, in test_run_coroutine_threadsafe_with_timeout
    self.loop.run_until_complete(future)
AssertionError: TimeoutError not raised

----------
components: Tests
messages: 355223
nosy: vstinner
priority: normal
severity: normal
status: open
title: test_asyncio: test_run_coroutine_threadsafe_with_timeout()
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38564>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:46:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 14:46:32 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571841992.01.0.748340395514.issue38563@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Thanks for the speedy patch Victor. Great effort!

Can you try to manually test PR 16901?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:50:53 2019
From: report at bugs.python.org (Carlton Gibson)
Date: Wed, 23 Oct 2019 14:50:53 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571842253.24.0.983548423796.issue38563@roundup.psfhosted.org>


Carlton Gibson <carlton.gibson at noumenal.es> added the comment:

OK, that seems fair :) Will do that tomorrow AM.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 10:50:54 2019
From: report at bugs.python.org (Scott Sanderson)
Date: Wed, 23 Oct 2019 14:50:54 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
Message-ID: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>


New submission from Scott Sanderson <scoutoss at gmail.com>:

In some circumstances, it's useful to be able in inspect the parameters with which an instance of functools.lru_cache was instantiated. It's currently possible to recover the cache's maxsize via the .cache_info() method, but there's no way to recover the value passed for `typed`, which controls whether the lru_cache's cache is partitioned by input type.

This came up in the context of cloudpickle, a library that tries to extend pickle to support more types (in particular, interactively-defined functions and classes) for use-cases like cluster computing. 

It's currently not possible to pickle an lru-cache decorated function that's defined in __main__ (which includes, e.g. a Jupyter Notebook). We can **almost** fix this with a pure library solution (see https://github.com/cloudpipe/cloudpickle/pull/309), but we're currently blocked by the fact that there's no way to recover the value that was passed for `typed`. Exposing a .typed attribute on the extension type for lru_cached functions fixes this

For more discussion, see the above linked PR, along with https://github.com/cloudpipe/cloudpickle/issues/178.

----------
components: Library (Lib)
messages: 355226
nosy: Scott Sanderson2
priority: normal
severity: normal
status: open
title: Expose the value passed of typed passed to functools.lru_cache
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:01:22 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 15:01:22 +0000
Subject: [issue38564] test_asyncio:
 test_run_coroutine_threadsafe_with_timeout()
In-Reply-To: <1571841860.24.0.514293762677.issue38564@roundup.psfhosted.org>
Message-ID: <1571842882.18.0.409580310759.issue38564@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

test_run_coroutine_threadsafe_with_timeout() has a race condition. It relies on "await asyncio.sleep(0.05)" synchronization primitive. That's not reliable.

    async def add(self, a, b, fail=False, cancel=False):
        """Wait 0.05 second and return a + b."""
        await asyncio.sleep(0.05)
        if fail:
            raise RuntimeError("Fail!")
        if cancel:
            asyncio.current_task(self.loop).cancel()
            await asyncio.sleep(0)
        return a + b

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38564>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:03:54 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 15:03:54 +0000
Subject: [issue38564] test_asyncio:
 test_run_coroutine_threadsafe_with_timeout()
In-Reply-To: <1571841860.24.0.514293762677.issue38564@roundup.psfhosted.org>
Message-ID: <1571843034.8.0.48225885493.issue38564@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I can reproduce the issue with this patch:

diff --git a/Lib/test/test_asyncio/test_tasks.py b/Lib/test/test_asyncio/test_tasks.py
index dde84b84b1..c94113712a 100644
--- a/Lib/test/test_asyncio/test_tasks.py
+++ b/Lib/test/test_asyncio/test_tasks.py
@@ -3160,7 +3160,7 @@ class RunCoroutineThreadsafeTests(test_utils.TestCase):
 
     async def add(self, a, b, fail=False, cancel=False):
         """Wait 0.05 second and return a + b."""
-        await asyncio.sleep(0.05)
+        await asyncio.sleep(1e-9)
         if fail:
             raise RuntimeError("Fail!")
         if cancel:

and the command:

./python -m test test_asyncio -m test_run_coroutine_threadsafe_with_timeout -v -F

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38564>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:12:43 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 15:12:43 +0000
Subject: [issue38564] test_asyncio:
 test_run_coroutine_threadsafe_with_timeout() has a race condition
In-Reply-To: <1571841860.24.0.514293762677.issue38564@roundup.psfhosted.org>
Message-ID: <1571843563.39.0.534851986823.issue38564@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: test_asyncio: test_run_coroutine_threadsafe_with_timeout() -> test_asyncio: test_run_coroutine_threadsafe_with_timeout() has a race condition

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38564>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:19:35 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 15:19:35 +0000
Subject: [issue34172] multiprocessing.Pool and ThreadPool leak resources after
 being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1571843975.75.0.624936875567.issue34172@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

What's the status of this issue?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34172>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:25:38 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 15:25:38 +0000
Subject: [issue34679] asyncio.add_signal_handler call fails if not on main
 thread
In-Reply-To: <1536938865.53.0.956365154283.issue34679@psf.upfronthosting.co.za>
Message-ID: <1571844338.01.0.929656231574.issue34679@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 1b53a24fb4417c764dd5933bce505f5c94249ca6 by Victor Stinner in branch 'master':
bpo-34679: ProactorEventLoop only uses set_wakeup_fd() in main thread (GH-16901)
https://github.com/python/cpython/commit/1b53a24fb4417c764dd5933bce505f5c94249ca6


----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34679>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:25:38 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 15:25:38 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571844338.27.0.553368683459.issue38563@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 1b53a24fb4417c764dd5933bce505f5c94249ca6 by Victor Stinner in branch 'master':
bpo-34679: ProactorEventLoop only uses set_wakeup_fd() in main thread (GH-16901)
https://github.com/python/cpython/commit/1b53a24fb4417c764dd5933bce505f5c94249ca6


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:25:55 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Oct 2019 15:25:55 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571844355.76.0.949845211476.issue38563@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16440
pull_request: https://github.com/python/cpython/pull/16902

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:25:55 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Oct 2019 15:25:55 +0000
Subject: [issue34679] asyncio.add_signal_handler call fails if not on main
 thread
In-Reply-To: <1536938865.53.0.956365154283.issue34679@psf.upfronthosting.co.za>
Message-ID: <1571844355.49.0.00318264193256.issue34679@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16439
pull_request: https://github.com/python/cpython/pull/16902

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34679>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:29:44 2019
From: report at bugs.python.org (Malek Ghantous)
Date: Wed, 23 Oct 2019 15:29:44 +0000
Subject: [issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 >
 alledged missing X509_VERIFY_PARAM_set1_host() support
In-Reply-To: <1530609211.5.0.56676864532.issue34028@psf.upfronthosting.co.za>
Message-ID: <1571844584.09.0.779043579928.issue34028@roundup.psfhosted.org>


Malek Ghantous <malek.ghantous at gmail.com> added the comment:

I'm having a similar problem.  I'm trying to compile on Red Hat 6.9 using a locally installed OpenSSL library.  I've tried everything here (I think) and I still get this error:

checking for openssl/ssl.h in /home/mf/dp/mpma/ghantousm/apptron/local/... yes   
checking whether compiling and linking against OpenSSL works... no               
checking for --with-ssl-default-suites... python                                 

I've ensured the libssl.* files are all present or linked to in /home/mf/dp/mpma/ghantousm/apptron/local/lib and .../lib64, the include files are present, the OpenSSL build seemed fine, and I compiled version 1.1.1d of openssl.  I've tried setting LDFLAGS and rpath and still no dice; the setup.py module doesn't seem to have any hard-coded paths so I'm really at a loss to understand what is wrong.  I've tried both versions 3.8.0 and 3.7.3 of python with the --with-openssl=/home/mf/dp/mpma/ghantousm/apptron/local option set, and version 3.6.8 (which doesn't accept any ssl related options).

This bug seems to have been preserved for a number of versions, so I'd like to help squash it if I can, but not sure where to go to from here.  I notice that some of the reports here suggest that they've had success with work-arounds, but as I stated none of them seem to work for me and I'm unable to compile with ssl support.

----------
nosy: +malektronic
type:  -> compile error
versions: +Python 3.8 -Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34028>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:44:03 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Oct 2019 15:44:03 +0000
Subject: [issue34679] asyncio.add_signal_handler call fails if not on main
 thread
In-Reply-To: <1536938865.53.0.956365154283.issue34679@psf.upfronthosting.co.za>
Message-ID: <1571845443.61.0.510264271439.issue34679@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset cbf474c98e702d12c97cd16a1e44ede10ea52b5b by Miss Skeleton (bot) in branch '3.8':
bpo-34679: ProactorEventLoop only uses set_wakeup_fd() in main thread (GH-16901)
https://github.com/python/cpython/commit/cbf474c98e702d12c97cd16a1e44ede10ea52b5b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34679>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:44:03 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Oct 2019 15:44:03 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571845443.85.0.895347275959.issue38563@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset cbf474c98e702d12c97cd16a1e44ede10ea52b5b by Miss Skeleton (bot) in branch '3.8':
bpo-34679: ProactorEventLoop only uses set_wakeup_fd() in main thread (GH-16901)
https://github.com/python/cpython/commit/cbf474c98e702d12c97cd16a1e44ede10ea52b5b


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:46:01 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 15:46:01 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571845560.93.0.963634597609.issue38563@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Yury and Andrew approved my PR 16901, so I merged it.

Thanks for the bug report Carlton Gibson.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 11:58:44 2019
From: report at bugs.python.org (Christian Heimes)
Date: Wed, 23 Oct 2019 15:58:44 +0000
Subject: [issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 >
 alledged missing X509_VERIFY_PARAM_set1_host() support
In-Reply-To: <1530609211.5.0.56676864532.issue34028@psf.upfronthosting.co.za>
Message-ID: <1571846324.58.0.77852691456.issue34028@roundup.psfhosted.org>


Christian Heimes <lists at cheimes.de> added the comment:

Python uses https://www.gnu.org/software/autoconf-archive/ax_check_openssl.html to detect and check for OpenSSL. Please check config.log for any errors. The log file will contain an error message. 

How did you compile OpenSSL? Did you configure the sources with "./config shared" ?

config.log:
...
configure:17184: checking whether compiling and linking against OpenSSL works
Trying link with OPENSSL_LDFLAGS=-L/home/heimes/dev/python/multissl/openssl/1.1.0l/lib; OPENSSL_LIBS=-lssl -lcrypto; OPENSSL_INCLUDES=-I/home/heimes/dev/python/multissl/openssl/1.1.0l/include
configure:17206: gcc -pthread -o conftest  -I/home/heimes/dev/python/multissl/openssl/1.1.0l/include   -L/home/heimes/dev/python/multissl/openssl/1.1.0l/lib conftest.c -lssl -lcrypto -lcrypt -lpthread -ldl  -lutil -lm >&5
configure:17206: $? = 0
configure:17208: result: yes
configure:17231: checking for X509_VERIFY_PARAM_set1_host in libssl
configure:17260: gcc -pthread -o conftest  -I/home/heimes/dev/python/multissl/openssl/1.1.0l/include   -L/home/heimes/dev/python/multissl/openssl/1.1.0l/lib conftest.c -lssl -lcrypto -lcrypt -lpthread -ldl  -lutil -lm >&5
configure:17260: $? = 0
configure:17271: result: yes
configure:17288: checking for --with-ssl-default-suites
configure:17317: result: python
...

make:
...
building '_ssl' extension
gcc -pthread -fPIC -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration -I./Include/internal -I/home/heimes/dev/python/multissl/openssl/1.1.0l/include -I./Include -I. -I/usr/local/include -I/home/heimes/dev/python/cpython/Include -I/home/heimes/dev/python/cpython -c /home/heimes/dev/python/cpython/Modules/_ssl.c -o build/temp.linux-x86_64-3.9/home/heimes/dev/python/cpython/Modules/_ssl.o
gcc -pthread -shared build/temp.linux-x86_64-3.9/home/heimes/dev/python/cpython/Modules/_ssl.o -L/home/heimes/dev/python/multissl/openssl/1.1.0l/lib -L/usr/local/lib -lssl -lcrypto -o build/lib.linux-x86_64-3.9/_ssl.cpython-39-x86_64-linux-gnu.so
...

./python
>>> import _ssl
>>> _ssl._OPENSSL_API_VERSION
(1, 1, 0, 12, 15)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34028>
_______________________________________

From report at bugs.python.org  Wed Oct 23 12:22:20 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 23 Oct 2019 16:22:20 +0000
Subject: [issue32856] Optimize the `for y in [x]` idiom in comprehensions
In-Reply-To: <1518770483.24.0.467229070634.issue32856@psf.upfronthosting.co.za>
Message-ID: <1571847740.77.0.617207295851.issue32856@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

OOC, rather than optimizing a fairly ugly use case, might another approach be to make walrus less leaky? Even if observable leakage is considered desirable, it strikes me that use cases for walrus in genexprs and comprehensions likely break up into:

1. 90%: Cases where variable is never used outside genexpr/comprehension (because functional programming constructs shouldn't have side-effects, gosh darn it!)
2. 5%: Cases where variable is used outside genexpr/comprehension and expects leakage
3. 5%: Cases where variable is used outside genexpr/comprehension, but never in a way that actually relies on the value set in the genexpr/comprehension (same name chosen by happenstance)

If the walrus behavior in genexpr/comprehensions were tweaked to say that it only leaks if:

1. It's running at global scope (unavoidable, since there's no way to tell if it's an intended part of the module's interface)

or

2. A global or nonlocal statement within the function made it clear the name was considered stateful (again, like running at global scope, there is no way to know for sure if the name will be used somewhere else)

or

3. At some point in the function, outside the genexpr/comprehension, the value of the walrus-assigned name was read.

Case #3 could be even more narrow if the Python AST optimizer was fancier, potentially something like "if the value was read *after* the genexpr/comprehension, but *before* any following *unconditional* writes to the same name" (so [leaked := x for x in it] wouldn't bother to leak "leaked" if the next line was "leaked = 1" even if "leaked" were read three lines later, or the only reads from leaked occurred before the genexpr/comprehension), but I don't think the optimizer is up to that; following simple rules similar to those the compiler already follows to identify local names should cover 90% of cases anyway.

Aside from the dict returned by locals, and the possibility of earlier finalizer invocation (which you couldn't rely on outside CPython anyway), there's not much difference in behavior between a leaking and non-leaking walrus when the value is never referred to again, and it seems like the 90% case for cases where unwanted leakage occurs would be covered by this. Sure, if my WAG on use case percentages is correct, 5% of use cases would continue to leak even though they didn't benefit from it, but it seems like optimizing the 90% case would do a lot more good than optimizing what's already a micro-optimization that 99% of Python programmers would never use (and shouldn't really be encouraged, since it would rely on CPython implementation details, and produce uglier code).

I was also inspired by this to look at replacing BUILD_LIST with BUILD_TUPLE when followed by GET_ITER (so "[y for x in it for y in [derived(x)]]" would at least get the performance benefit of looping over a one-element tuple rather than a one-element list), thinking it might reduce the overhead of [y for x in a for y in [x]] in your unpatched benchmark by making it equivalent to [y for x in a for y in (x,)] while reading more prettily, but it turns out you beat me to it with issue32925, so good show there! :-)

You should probably rerun your benchmarks though; with issue32925 committed (a month after you posted the benchmarks here), the performance discrepancy should be somewhat less (estimate based on local benchmarking says maybe 20% faster with BUILD_LIST being optimized to BUILD_TUPLE). Still much faster with the proposed optimization than without, but I suspect even optimized, few folks will think to write their comprehensions to take advantage of it, which is why I was suggesting tweaks to the more obvious walrus operator.

----------
nosy: +josh.r

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32856>
_______________________________________

From report at bugs.python.org  Wed Oct 23 12:27:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 16:27:42 +0000
Subject: [issue16381] Introduce option to force the interpreter to exit upon
 MemoryErrors
In-Reply-To: <1351775704.44.0.517582874178.issue16381@psf.upfronthosting.co.za>
Message-ID: <1571848062.42.0.310355907837.issue16381@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

It is possible to install a custom hook on memory allocators using the PEP 445: see for example attached fatalmalloc.c.

I don't see much traction to get this feature since 2013, I reject the feature request.

----------
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16381>
_______________________________________

From report at bugs.python.org  Wed Oct 23 12:28:38 2019
From: report at bugs.python.org (James Gerity)
Date: Wed, 23 Oct 2019 16:28:38 +0000
Subject: [issue38566] Description of '\w' behavior is vague in `re`
 documentation
Message-ID: <1571848118.32.0.881781017255.issue38566@roundup.psfhosted.org>


New submission from James Gerity <snoopjedi at gmail.com>:

The documentation for the `re` library? describes the behavior of the specifier '\w' as matching "Unicode word characters," which is very vague. The closest thing I can find that corresponds to this language is the guidance offered in Unicode Technical Standard #18?, which defines the class `<word_character>` to include all alphabetic and decimal codepoints, as well as U+200C ZERO WIDTH NON-JOINER and U+200D ZERO WIDTH JOINER. This does not appear to be a correct description of `re`, however, as these zero-width characters are not counted when matching '\w', e.g.:

```
>>> re.match('\w*', 'Auf\u200Clage')
<re.Match object; span=(0, 3), match='Auf'>
```

It seems from examining the CPython source? that SRE treats '\w' as meaning any alphanumeric character OR U+005F SPACING UNDERSCORE, which does not match any Unicode class definition I've been able to find.

Can anyone provide clarification on what part of Unicode this documentation is referring to? If there is some other definition, the documentation should be more specific about referring to it (and including a link would be preferred). If instead the documentation is incorrect, this language should be changed to describe the true meaning of \w.

? https://docs.python.org/3/library/re.html#index-32
? http://unicode.org/reports/tr18/
? https://github.com/python/cpython/blob/master/Modules/_sre.c#L125

----------
assignee: docs at python
components: Documentation
messages: 355239
nosy: docs at python, snoopjedi
priority: normal
severity: normal
status: open
title: Description of '\w' behavior is vague in `re` documentation

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38566>
_______________________________________

From report at bugs.python.org  Wed Oct 23 12:32:54 2019
From: report at bugs.python.org (Carlton Gibson)
Date: Wed, 23 Oct 2019 16:32:54 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571848374.02.0.610189793702.issue38563@roundup.psfhosted.org>


Carlton Gibson <carlton.gibson at noumenal.es> added the comment:

Super turn-around. Thank you all.

----------
resolution: fixed -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 12:38:10 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 23 Oct 2019 16:38:10 +0000
Subject: [issue38563] ProactorEventLoop.close(): set_wakeup_fd() only works in
 main thread
In-Reply-To: <1571832808.37.0.827662310876.issue38563@roundup.psfhosted.org>
Message-ID: <1571848690.66.0.00482294242234.issue38563@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
resolution:  -> fixed
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38563>
_______________________________________

From report at bugs.python.org  Wed Oct 23 13:27:32 2019
From: report at bugs.python.org (Charalampos Stratakis)
Date: Wed, 23 Oct 2019 17:27:32 +0000
Subject: [issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 >
 alledged missing X509_VERIFY_PARAM_set1_host() support
In-Reply-To: <1530609211.5.0.56676864532.issue34028@psf.upfronthosting.co.za>
Message-ID: <1571851652.63.0.202440285935.issue34028@roundup.psfhosted.org>


Charalampos Stratakis <cstratak at redhat.com> added the comment:

Have you also tried $ yum install openssl-devel ?

That should work without requiring to compile openssl from source, unless you want a later version, which isn't advisable to install system-wide, as it could break other things.

----------
nosy: +cstratak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34028>
_______________________________________

From report at bugs.python.org  Wed Oct 23 13:45:50 2019
From: report at bugs.python.org (stein-k)
Date: Wed, 23 Oct 2019 17:45:50 +0000
Subject: [issue38567] urllib.parse.unquote_plus raises incorrect errormessage
 when string parameter is bytes
Message-ID: <1571852750.66.0.0310766347617.issue38567@roundup.psfhosted.org>


New submission from stein-k <karlsen.stein at gmail.com>:

urllib.parse.unquote_plus(b'abc%20def')
...
TypeError: a bytes-like object is required, not 'str'

----------
components: Library (Lib)
messages: 355242
nosy: stein-k
priority: normal
severity: normal
status: open
title: urllib.parse.unquote_plus raises incorrect errormessage when string parameter is bytes
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38567>
_______________________________________

From report at bugs.python.org  Wed Oct 23 13:51:31 2019
From: report at bugs.python.org (stein-k)
Date: Wed, 23 Oct 2019 17:51:31 +0000
Subject: [issue38567] urllib.parse.unquote_plus raises incorrect errormessage
 when string parameter is bytes
In-Reply-To: <1571852750.66.0.0310766347617.issue38567@roundup.psfhosted.org>
Message-ID: <1571853091.53.0.431999801252.issue38567@roundup.psfhosted.org>


Change by stein-k <karlsen.stein at gmail.com>:


----------
keywords: +patch
pull_requests: +16441
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16903

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38567>
_______________________________________

From report at bugs.python.org  Wed Oct 23 14:16:03 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 23 Oct 2019 18:16:03 +0000
Subject: [issue37025] Misleading error message "Python failed to load the
 default activation context"
In-Reply-To: <1558646019.4.0.18611977167.issue37025@roundup.psfhosted.org>
Message-ID: <1571854563.83.0.121703433604.issue37025@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 009a6928727b23344613ab6a9a52b9da56ab905c by Steve Dower (Zackery Spytz) in branch '2.7':
bpo-37025: AddRefActCtx() shouldn't be checked for failure (GH-16897)
https://github.com/python/cpython/commit/009a6928727b23344613ab6a9a52b9da56ab905c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37025>
_______________________________________

From report at bugs.python.org  Wed Oct 23 14:17:14 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 23 Oct 2019 18:17:14 +0000
Subject: [issue37025] Misleading error message "Python failed to load the
 default activation context"
In-Reply-To: <1558646019.4.0.18611977167.issue37025@roundup.psfhosted.org>
Message-ID: <1571854634.7.0.779219454094.issue37025@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Merged the 2.7 fix. Let's just delete the whole block in master.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37025>
_______________________________________

From report at bugs.python.org  Wed Oct 23 14:34:37 2019
From: report at bugs.python.org (Riccardo Schirone)
Date: Wed, 23 Oct 2019 18:34:37 +0000
Subject: [issue30458] [security][CVE-2019-9740][CVE-2019-9947] HTTP Header
 Injection (follow-up of CVE-2016-5699)
In-Reply-To: <1495638091.75.0.96439752743.issue30458@psf.upfronthosting.co.za>
Message-ID: <1571855677.7.0.590359260206.issue30458@roundup.psfhosted.org>


Riccardo Schirone <rschiron at redhat.com> added the comment:

CVE-2019-18348 has been assigned to the issue explained in https://bugs.python.org/issue30458#msg347282 . Maybe a separate bug for it would be better though. CVE-2019-18348 is about injecting CRLF in HTTP requests through the *host* part of a URL.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30458>
_______________________________________

From report at bugs.python.org  Wed Oct 23 14:43:45 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 23 Oct 2019 18:43:45 +0000
Subject: [issue34172] multiprocessing.Pool and ThreadPool leak resources after
 being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1571856225.26.0.829979065296.issue34172@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

Pablo's fix looks like a superset of the original fix applied here, so I'm assuming it fixes this issue as well.

----------
nosy: +josh.r

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34172>
_______________________________________

From report at bugs.python.org  Wed Oct 23 14:45:00 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 23 Oct 2019 18:45:00 +0000
Subject: [issue34172] multiprocessing.Pool and ThreadPool leak resources after
 being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1571856300.95.0.761493657947.issue34172@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

It should probably be backport to all supported 3.x branches though, so people aren't required to move to 3.8 to benefit from it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34172>
_______________________________________

From report at bugs.python.org  Wed Oct 23 14:52:34 2019
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 23 Oct 2019 18:52:34 +0000
Subject: [issue38551] lib2to3 Grammar.txt doesn't have Python 3.8 grammar
 changes
In-Reply-To: <1571681443.98.0.927590549429.issue38551@roundup.psfhosted.org>
Message-ID: <1571856754.58.0.646588370516.issue38551@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

@Peter you can close this if issue36541 will fix your issue (i.e. both assignment expressions and positional-only parameters).

----------
nosy: +brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38551>
_______________________________________

From report at bugs.python.org  Wed Oct 23 14:58:52 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 23 Oct 2019 18:58:52 +0000
Subject: [issue38566] Description of '\w' behavior is vague in `re`
 documentation
In-Reply-To: <1571848118.32.0.881781017255.issue38566@roundup.psfhosted.org>
Message-ID: <1571857132.4.0.00176348603001.issue38566@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

The definition of \w, historically, has corresponded to the set of characters that can occur in legal variable names in C (alphanumeric ASCII plus underscores, making it equivalent to [a-zA-Z0-9_] for ASCII regex). That's why, on top of the definitely wordy alphabetic characters, and the arguably wordy numerics, it includes the underscore, _.

That definition predates Unicode entirely, and Python is just building on it by expanding the definition of "alphanumeric" to encompass all alphanumeric characters in Unicode.

We definitely can't remove underscores from the definition without breaking existing code which assumes a common subset of PCRE support (every regex flavor I know of includes underscores in \w). Adding the zero width characters seems of limited benefit (especially in the non-joiner case; if you're trying to pull out words, presumably you don't want to group letters across a non-joining boundary?). Basically, you're parsing "Unicode word characters" as "Unicode's definition of word characters", when it's really meant to mean "All word characters, not just ASCII".

You omitted the clarifying remarks from the documentation though, the full description is:

> Matches Unicode word characters; this includes most characters that can be part of a word in any language, as well as numbers and the underscore. If the ASCII flag is used, only [a-zA-Z0-9_] is matched.

That's about as precise as I think we can make it (because technically, some of the things that count as "word characters" aren't actually part of an "alphabet" in the technical definition). If you think there is a clearer way of expressing it, please suggest a better phrasing, and this can be fixed as a documentation bug.

----------
nosy: +josh.r

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38566>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:02:41 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 23 Oct 2019 19:02:41 +0000
Subject: [issue38560] Allow iterable argument unpacking after a keyword
 argument?
In-Reply-To: <1571790042.34.0.496395652559.issue38560@roundup.psfhosted.org>
Message-ID: <1571857361.94.0.890551692087.issue38560@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

I'd be +1 on this, but I'm worried about existing code relying on the functional use case from your example.

If we are going to discourage it, I think we either have to:

1. Have DeprecationWarning that turns into a SyntaxError, or
2. Never truly remove it, but make it a SyntaxWarning immediately and leave it that way indefinitely

----------
nosy: +josh.r

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38560>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:05:53 2019
From: report at bugs.python.org (Peter Ludemann)
Date: Wed, 23 Oct 2019 19:05:53 +0000
Subject: [issue36541] Make lib2to3 grammar more closely match Python
In-Reply-To: <1554514880.92.0.277848417721.issue36541@roundup.psfhosted.org>
Message-ID: <1571857553.23.0.562571886368.issue36541@roundup.psfhosted.org>


Peter Ludemann <peter.ludemann at gmail.com> added the comment:

Also the Grammar.txt diffs look about the same size as I've seen with other upgrades to lib2to3 when the Python grammar changed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36541>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:07:49 2019
From: report at bugs.python.org (Peter Ludemann)
Date: Wed, 23 Oct 2019 19:07:49 +0000
Subject: [issue38551] lib2to3 Grammar.txt doesn't have Python 3.8 grammar
 changes
In-Reply-To: <1571681443.98.0.927590549429.issue38551@roundup.psfhosted.org>
Message-ID: <1571857669.55.0.921372243308.issue38551@roundup.psfhosted.org>


Peter Ludemann <peter.ludemann at gmail.com> added the comment:

issue36541 and its proposed PR seem to cover my needs.

----------
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38551>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:09:14 2019
From: report at bugs.python.org (Ying Wang)
Date: Wed, 23 Oct 2019 19:09:14 +0000
Subject: [issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL
Message-ID: <1571857754.85.0.698050163763.issue38568@roundup.psfhosted.org>


New submission from Ying Wang <yingw787.personal at gmail.com>:

Hey,

I encountered an interesting bug when trying to do string parsing using f-strings. I am currently under the impression that within the curly braces is any expression that can be successfully evaluated in a REPL. Here's the error:

```bash
yingw787 at yingw787-Oryx-Pro:~/src/gpudb-dev-v6.2.0/kio/kio/tests/regression/_data/csv$ python
Python 3.7.5 (default, Oct 15 2019, 21:38:37) 
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> blah = '"hi"'
>>> blah
'"hi"'
>>> f'{blah.strip('"')}'
  File "<stdin>", line 1
    f'{blah.strip('"')}'
                       ^
SyntaxError: EOL while scanning string literal
>>> '{0}'.format(blah.strip('"'))
'hi'
>>> 
```

I can use '.format()' for now, but it might be nice to align f-string expr behavior w/ .format(). Please let me know if you need more reproduction steps, or if you need a helping hand :)

Thanks
Ying

----------
components: Interpreter Core
messages: 355254
nosy: yingw787
priority: normal
severity: normal
status: open
title: [3.7.5 x86_64 Linux] f-string parsing results in EOL
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38568>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:17:37 2019
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 23 Oct 2019 19:17:37 +0000
Subject: [issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL
In-Reply-To: <1571857754.85.0.698050163763.issue38568@roundup.psfhosted.org>
Message-ID: <1571858257.5.0.131067128933.issue38568@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:

This is because you're trying to use the string's delimiting character (') in the string itself, which won't work for fairly apparent reasons :).  Try removing the `f` prefix and see what happens.

You can get around this by using a triple-quoted string which will allow you to use both quote characters within the string:

>>> blah = '"hi"'
>>> f'''{blah.strip('"')}'''
'hi'

----------
nosy: +zach.ware
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38568>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:21:55 2019
From: report at bugs.python.org (Hobs)
Date: Wed, 23 Oct 2019 19:21:55 +0000
Subject: [issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL
In-Reply-To: <1571857754.85.0.698050163763.issue38568@roundup.psfhosted.org>
Message-ID: <CAMXOs+kb+vGr+zCKtayqF2XZ42MdNH2qMk0iu4w01Rb1C8570A@mail.gmail.com>


Hobs <hobsonlane at gmail.com> added the comment:

Not a bug. If you use quotes inside an f-string (or any other kind of
string) they need to be escaped.
--Hobson

On Wed, Oct 23, 2019 at 12:09 PM Ying Wang <report at bugs.python.org> wrote:

>
> New submission from Ying Wang <yingw787.personal at gmail.com>:
>
> Hey,
>
> I encountered an interesting bug when trying to do string parsing using
> f-strings. I am currently under the impression that within the curly braces
> is any expression that can be successfully evaluated in a REPL. Here's the
> error:
>
> ```bash
> yingw787 at yingw787-Oryx-Pro:~/src/gpudb-dev-v6.2.0/kio/kio/tests/regression/_data/csv$
> python
> Python 3.7.5 (default, Oct 15 2019, 21:38:37)
> [GCC 5.4.0 20160609] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> blah = '"hi"'
> >>> blah
> '"hi"'
> >>> f'{blah.strip('"')}'
>   File "<stdin>", line 1
>     f'{blah.strip('"')}'
>                        ^
> SyntaxError: EOL while scanning string literal
> >>> '{0}'.format(blah.strip('"'))
> 'hi'
> >>>
> ```
>
> I can use '.format()' for now, but it might be nice to align f-string expr
> behavior w/ .format(). Please let me know if you need more reproduction
> steps, or if you need a helping hand :)
>
> Thanks
> Ying
>
> ----------
> components: Interpreter Core
> messages: 355254
> nosy: yingw787
> priority: normal
> severity: normal
> status: open
> title: [3.7.5 x86_64 Linux] f-string parsing results in EOL
> type: behavior
> versions: Python 3.7
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue38568>
> _______________________________________
> _______________________________________________
> New-bugs-announce mailing list
> New-bugs-announce at python.org
> https://mail.python.org/mailman/listinfo/new-bugs-announce
>

----------
nosy: +Hobson.Lane

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38568>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:25:34 2019
From: report at bugs.python.org (James Gerity)
Date: Wed, 23 Oct 2019 19:25:34 +0000
Subject: [issue38566] Description of '\w' behavior is vague in `re`
 documentation
In-Reply-To: <1571848118.32.0.881781017255.issue38566@roundup.psfhosted.org>
Message-ID: <1571858734.73.0.714254220903.issue38566@roundup.psfhosted.org>


James Gerity <snoopjedi at gmail.com> added the comment:

Cheers for the additional context. My recommendation would be to change the language to avoid confusion with the consortium's formal specifications. Describing what SRE does should be fine:

> Matches any alphanumeric Unicode character, as well as '_'. If the ASCII flag is used, only [a-zA-Z0-9_] is matched.

I think it'd also be nice for the term "alphanumeric Unicode character" to link to the documentation for `str.isalnum()`, which provides enough clarity for the user to work out exactly what Unicode category properties will end up qualifying as a match.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38566>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:27:43 2019
From: report at bugs.python.org (David Hagen)
Date: Wed, 23 Oct 2019 19:27:43 +0000
Subject: [issue34776] Postponed annotations break inspection of dataclasses
In-Reply-To: <1537699529.98.0.956365154283.issue34776@psf.upfronthosting.co.za>
Message-ID: <1571858863.97.0.691626960575.issue34776@roundup.psfhosted.org>


David Hagen <david at drhagen.com> added the comment:

This PR has been sitting for a while. Any chance we can bring it over the finish line?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34776>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:28:14 2019
From: report at bugs.python.org (Hobs)
Date: Wed, 23 Oct 2019 19:28:14 +0000
Subject: [issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL
In-Reply-To: <CAMXOs+kb+vGr+zCKtayqF2XZ42MdNH2qMk0iu4w01Rb1C8570A@mail.gmail.com>
Message-ID: <CAMXOs+kgbjbPcuMrF9XwsOyve1iUc4Aea29yhGOh-qLTx5agLQ@mail.gmail.com>


Hobs <hobsonlane at gmail.com> added the comment:

It is a limitation of f-strings, though. We're not allowed to use
backslashes within the f-string expression in curly braces. So to do what
you want you have to create another variable containing the quote character:

```
>>> blah = '"hi"'
>>> blah
'"hi"'
>>> q = '"'
>>> f'{blah.strip(q)}'
'hi'
```
--Hobson

On Wed, Oct 23, 2019 at 12:21 PM Hobson Lane <hobson at totalgood.com> wrote:

> Not a bug. If you use quotes inside an f-string (or any other kind of
> string) they need to be escaped.
> --Hobson
>
>
> On Wed, Oct 23, 2019 at 12:09 PM Ying Wang <report at bugs.python.org> wrote:
>
>>
>> New submission from Ying Wang <yingw787.personal at gmail.com>:
>>
>> Hey,
>>
>> I encountered an interesting bug when trying to do string parsing using
>> f-strings. I am currently under the impression that within the curly braces
>> is any expression that can be successfully evaluated in a REPL. Here's the
>> error:
>>
>> ```bash
>> yingw787 at yingw787-Oryx-Pro:~/src/gpudb-dev-v6.2.0/kio/kio/tests/regression/_data/csv$
>> python
>> Python 3.7.5 (default, Oct 15 2019, 21:38:37)
>> [GCC 5.4.0 20160609] on linux
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> blah = '"hi"'
>> >>> blah
>> '"hi"'
>> >>> f'{blah.strip('"')}'
>>   File "<stdin>", line 1
>>     f'{blah.strip('"')}'
>>                        ^
>> SyntaxError: EOL while scanning string literal
>> >>> '{0}'.format(blah.strip('"'))
>> 'hi'
>> >>>
>> ```
>>
>> I can use '.format()' for now, but it might be nice to align f-string
>> expr behavior w/ .format(). Please let me know if you need more
>> reproduction steps, or if you need a helping hand :)
>>
>> Thanks
>> Ying
>>
>> ----------
>> components: Interpreter Core
>> messages: 355254
>> nosy: yingw787
>> priority: normal
>> severity: normal
>> status: open
>> title: [3.7.5 x86_64 Linux] f-string parsing results in EOL
>> type: behavior
>> versions: Python 3.7
>>
>> _______________________________________
>> Python tracker <report at bugs.python.org>
>> <https://bugs.python.org/issue38568>
>> _______________________________________
>> _______________________________________________
>> New-bugs-announce mailing list
>> New-bugs-announce at python.org
>> https://mail.python.org/mailman/listinfo/new-bugs-announce
>>
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38568>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:29:24 2019
From: report at bugs.python.org (Ying Wang)
Date: Wed, 23 Oct 2019 19:29:24 +0000
Subject: [issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL
In-Reply-To: <1571857754.85.0.698050163763.issue38568@roundup.psfhosted.org>
Message-ID: <1571858964.24.0.0468563327965.issue38568@roundup.psfhosted.org>


Ying Wang <yingw787.personal at gmail.com> added the comment:

Oh cool, I didn't know triple quotes can be used as part of f-strings! Thanks for the explanation!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38568>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:44:16 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 23 Oct 2019 19:44:16 +0000
Subject: [issue34776] Postponed annotations break inspection of dataclasses
In-Reply-To: <1537699529.98.0.956365154283.issue34776@psf.upfronthosting.co.za>
Message-ID: <1571859856.89.0.579854366777.issue34776@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34776>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:48:10 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 23 Oct 2019 19:48:10 +0000
Subject: [issue30458] [security][CVE-2019-9740][CVE-2019-9947] HTTP Header
 Injection (follow-up of CVE-2016-5699)
In-Reply-To: <1495638091.75.0.96439752743.issue30458@psf.upfronthosting.co.za>
Message-ID: <1571860090.85.0.62344352989.issue30458@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

Can you please open a separate issue for CVE-2019-18348?  It is easier to track that way.

(META: In general I think the CVE process is being abused and that these really did not deserve that treatment.  https://lwn.net/Articles/801157/  is good reading and food for thought.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30458>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:57:45 2019
From: report at bugs.python.org (Marco Sulla)
Date: Wed, 23 Oct 2019 19:57:45 +0000
Subject: [issue38569] Unknown distribution option: 'license_files'
Message-ID: <1571860665.03.0.77407877223.issue38569@roundup.psfhosted.org>


New submission from Marco Sulla <launchpad.net at marco.sulla.e4ward.com>:

I tried to add to `setuptools.setup()` the argument license_files. It works, but I get this warning:

/usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'license_files'

I suppose the warning can be removed.

----------
components: Distutils
messages: 355262
nosy: Marco Sulla, dstufft, eric.araujo
priority: normal
severity: normal
status: open
title: Unknown distribution option: 'license_files'
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38569>
_______________________________________

From report at bugs.python.org  Wed Oct 23 16:51:16 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 23 Oct 2019 20:51:16 +0000
Subject: [issue34384] os.readlink does not accept pathlib.Path on Windows
In-Reply-To: <1534045271.73.0.56676864532.issue34384@psf.upfronthosting.co.za>
Message-ID: <1571863876.96.0.381865949248.issue34384@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

can this be closed?

----------
nosy: +gregory.p.smith
status: pending -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34384>
_______________________________________

From report at bugs.python.org  Wed Oct 23 16:55:16 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 23 Oct 2019 20:55:16 +0000
Subject: [issue30618] readlink for pathlib paths
In-Reply-To: <1497052559.7.0.422106710991.issue30618@psf.upfronthosting.co.za>
Message-ID: <1571864116.49.0.766935588427.issue30618@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
assignee:  -> gregory.p.smith
nosy: +gregory.p.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30618>
_______________________________________

From report at bugs.python.org  Wed Oct 23 16:57:52 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 23 Oct 2019 20:57:52 +0000
Subject: [issue34384] os.readlink does not accept pathlib.Path on Windows
In-Reply-To: <1534045271.73.0.56676864532.issue34384@psf.upfronthosting.co.za>
Message-ID: <1571864272.85.0.280236188145.issue34384@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Yep

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34384>
_______________________________________

From report at bugs.python.org  Wed Oct 23 17:00:28 2019
From: report at bugs.python.org (timonegk)
Date: Wed, 23 Oct 2019 21:00:28 +0000
Subject: [issue38570] Shlex does not parse commands containing single quotes
 correctly
Message-ID: <1571864428.26.0.327920266668.issue38570@roundup.psfhosted.org>


New submission from timonegk <python at timonengelke.de>:

Steps to reproduce:
>>> from shlex import split
>>> line = "export F=$'\\''"
>>> split(line)
ValueError: No closing quotation

However, when printing the line

>>> print(line)
export F=$'\''

and pasting the output in bash, no further quotation marks are required.
The behavior of bash is described in its man page (line 497 for me, Chapter Quoting) and occurs also when bash is called with --posix. Therefore I guess that shlex does not reproduce the posix behavior here.

----------
components: Library (Lib)
messages: 355265
nosy: timonegk
priority: normal
severity: normal
status: open
title: Shlex does not parse commands containing single quotes correctly
type: behavior
versions: Python 2.7, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38570>
_______________________________________

From report at bugs.python.org  Wed Oct 23 17:18:46 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Oct 2019 21:18:46 +0000
Subject: [issue30618] readlink for pathlib paths
In-Reply-To: <1497052559.7.0.422106710991.issue30618@psf.upfronthosting.co.za>
Message-ID: <1571865526.1.0.118412969578.issue30618@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset a01ba333affcc0677146dc8af57179bdb808d608 by Miss Skeleton (bot) (Girts) in branch 'master':
bpo-30618: add readlink to pathlib.Path (GH-8285)
https://github.com/python/cpython/commit/a01ba333affcc0677146dc8af57179bdb808d608


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30618>
_______________________________________

From report at bugs.python.org  Wed Oct 23 17:20:14 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Wed, 23 Oct 2019 21:20:14 +0000
Subject: [issue38560] Allow iterable argument unpacking after a keyword
 argument?
In-Reply-To: <1571790042.34.0.496395652559.issue38560@roundup.psfhosted.org>
Message-ID: <1571865614.87.0.386950277379.issue38560@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

I've found one occurrence of this in the CPython codebase, in test_ast.py. Basically it makes sure that the following expression parses and compiles correctly:

f(1,2,c=3,*d,**e)

I doubt that this is to protect against regressions in this specific syntax. More likely it's just trying to create as many of the different argument passing AST nodes as possible in one call (it's the only test for function calls with arguments). It can probably be slightly refactored:

f(1,2,*c,d=3,**e)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38560>
_______________________________________

From report at bugs.python.org  Wed Oct 23 17:53:11 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 23 Oct 2019 21:53:11 +0000
Subject: [issue34776] Postponed annotations break inspection of dataclasses
In-Reply-To: <1537699529.98.0.956365154283.issue34776@psf.upfronthosting.co.za>
Message-ID: <1571867591.71.0.412591475998.issue34776@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

FWIW we discussed my patch with Eric at PyCon 2019 and I think he had no issues with it.  Eric, can I merge it?  Should we backport to 3.8?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34776>
_______________________________________

From report at bugs.python.org  Wed Oct 23 18:27:46 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 23 Oct 2019 22:27:46 +0000
Subject: [issue34776] Postponed annotations break inspection of dataclasses
In-Reply-To: <1537699529.98.0.956365154283.issue34776@psf.upfronthosting.co.za>
Message-ID: <1571869666.41.0.00544333652425.issue34776@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Yury: I'm okay with merging. If I recall, you were going to add a comment or two about the approach (a closure, if I remember correctly).

I think we should backport to 3.8 and 3.7: it's a bug.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34776>
_______________________________________

From report at bugs.python.org  Wed Oct 23 18:29:27 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 23 Oct 2019 22:29:27 +0000
Subject: [issue34776] Postponed annotations break inspection of dataclasses
In-Reply-To: <1537699529.98.0.956365154283.issue34776@psf.upfronthosting.co.za>
Message-ID: <1571869767.83.0.736534794896.issue34776@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

> Yury: I'm okay with merging. If I recall, you were going to add a comment or two about the approach (a closure, if I remember correctly).

Sure, I'll rebase and add a comment in a couple of days.  I'll elevate the status so that I don't forget before 3.8.1

----------
assignee: eric.smith -> yselivanov
priority:  -> deferred blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34776>
_______________________________________

From report at bugs.python.org  Wed Oct 23 18:37:43 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Wed, 23 Oct 2019 22:37:43 +0000
Subject: [issue30618] readlink for pathlib paths
In-Reply-To: <1497052559.7.0.422106710991.issue30618@psf.upfronthosting.co.za>
Message-ID: <1571870263.82.0.691140531479.issue30618@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

Thanks Girts!

----------
resolution:  -> fixed
stage: patch review -> commit review
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30618>
_______________________________________

From report at bugs.python.org  Wed Oct 23 18:42:58 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 23 Oct 2019 22:42:58 +0000
Subject: [issue30064] BaseSelectorEventLoop.sock_{recv,
 sendall}() don't remove their callbacks when canceled
In-Reply-To: <1492073709.93.0.33740565749.issue30064@psf.upfronthosting.co.za>
Message-ID: <1571870578.23.0.293332763653.issue30064@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

I think this broke asyncio a bit.  These two uvloop sock_* API tests no longer pass on asyncio 3.8:

* https://github.com/MagicStack/uvloop/blob/master/tests/test_sockets.py#L192

* https://github.com/MagicStack/uvloop/blob/master/tests/test_sockets.py#L238

Andrew, since this was your patch, please take a look.

----------
resolution: fixed -> 
stage: resolved -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30064>
_______________________________________

From report at bugs.python.org  Wed Oct 23 18:58:45 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Wed, 23 Oct 2019 22:58:45 +0000
Subject: [issue30064] BaseSelectorEventLoop.sock_{recv,
 sendall}() don't remove their callbacks when canceled
In-Reply-To: <1492073709.93.0.33740565749.issue30064@psf.upfronthosting.co.za>
Message-ID: <1571871525.12.0.763318190214.issue30064@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

I'll elevate the status so that we don't forget before 3.8.1 is too close

----------
priority: normal -> deferred blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30064>
_______________________________________

From report at bugs.python.org  Wed Oct 23 21:50:19 2019
From: report at bugs.python.org (Kevin Chen)
Date: Thu, 24 Oct 2019 01:50:19 +0000
Subject: [issue38571] Segfault with StopIteration
Message-ID: <1571881819.52.0.556347570713.issue38571@roundup.psfhosted.org>


New submission from Kevin Chen <kchen at mit.edu>:

Unfortunately, I don't currently have a simple test case, but after migrating an app from python 3.6 to python 3.7, python frequently (but not always) segfaults when running tests for my app in code related to StopIteration (perhaps somehow related to the implementation of PEP 479?).

I'm running a self-built (from python.org sources) unpatched build of Python 3.7.5 on Ubuntu Xenial.

(The output below is edited to redact some path names.)

Core was generated by `./python'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000000000044cc40 in PyException_GetContext (self=self at entry=0x441cbe0)
    at Objects/exceptions.c:338
338	    Py_XINCREF(context);

(gdb) py-bt
Traceback (most recent call first):
  File "lib/requests/models.py", line 750, in generate
    for chunk in self.raw.stream(chunk_size, decode_content=True):
  File "lib/requests/models.py", line 828, in content
    self._content = b''.join(self.iter_content(CONTENT_CHUNK_SIZE)) or b''
  File "lib/requests/sessions.py", line 686, in send
    r.content
  File "lib/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "lib/requests/sessions.py", line 546, in get
    return self.request('GET', url, **kwargs)
[trace continues with other files specific to my app]

(gdb) bt
#0  0x000000000044cc40 in PyException_GetContext (
    self=self at entry=<unknown at remote 0x441cbe0>) at Objects/exceptions.c:338
#1  0x000000000050b76d in PyErr_SetObject (
    exception=<type at remote 0x8b7c00>, value=StopIteration())
    at Python/errors.c:126
#2  0x000000000050ba17 in PyErr_SetNone (exception=<optimized out>)
    at Python/errors.c:163
#3  0x00000000005d254d in gen_send_ex (gen=0x4351b00, arg=<optimized out>, 
    exc=<optimized out>, closing=<optimized out>) at Objects/genobject.c:241
#4  0x0000000000429406 in _PyEval_EvalFrameDefault (f=<optimized out>, 
    throwflag=<optimized out>) at Python/ceval.c:2809
#5  0x00000000005d20cb in gen_send_ex (gen=0x457c1b0, arg=<optimized out>, 
    exc=<optimized out>, closing=<optimized out>) at Objects/genobject.c:221
#6  0x0000000000459679 in list_extend (self=self at entry=0x445a590, 
    iterable=iterable at entry=<generator at remote 0x457c1b0>)
    at Objects/listobject.c:897
#7  0x000000000045de55 in _PyList_Extend (self=self at entry=0x445a590, 
    iterable=iterable at entry=<generator at remote 0x457c1b0>)
    at Objects/listobject.c:937
#8  0x00000000005b76fc in PySequence_List (
    v=v at entry=<generator at remote 0x457c1b0>) at Objects/abstract.c:1905
#9  0x00000000005b867d in PySequence_Fast (v=<optimized out>, 
    m=m at entry=0x603715 "can only join an iterable") at Objects/abstract.c:1935
#10 0x0000000000438e02 in stringlib_bytes_join (sep=b'', 
    iterable=<optimized out>) at Objects/stringlib/join.h:22
#11 0x0000000000445b53 in _PyMethodDef_RawFastCallKeywords (
    method=0x8b0cc0 <bytes_methods+608>, self=self at entry=b'', 
    args=args at entry=0x4322f20, nargs=nargs at entry=1, kwnames=kwnames at entry=0x0)
    at Objects/call.c:648
#12 0x00000000005cfabf in _PyMethodDescr_FastCallKeywords (
    descrobj=<method_descriptor at remote 0x16f99f0>, 
    args=args at entry=0x4322f18, nargs=nargs at entry=2, kwnames=kwnames at entry=0x0)
    at Objects/descrobject.c:288
#13 0x000000000042df85 in call_function (kwnames=0x0, oparg=2, 
    pp_stack=<synthetic pointer>) at Python/ceval.c:4593
#14 _PyEval_EvalFrameDefault (f=<optimized out>, throwflag=<optimized out>)
    at Python/ceval.c:3110
#15 0x00000000004211c5 in function_code_fastcall (co=co at entry=0x3597c30, 
    args=<optimized out>, args at entry=0x3ce1f08, nargs=nargs at entry=1, 
    globals=globals at entry={'__name__': 'requests.models', '__doc__': '\nrequests.models\n~~~~~~~~~~~~~~~\n\nThis module contains the primary objects that power Requests.\n', '__package__': 'requests', '__loader__': <SourceFileLoader(name='requests.models', path='lib/requests/models.py') at remote 0x357cf70>, '__spec__': <ModuleSpec(name='requests.models', loader=<...>, origin='lib/requests/models.py', loader_state=None, submodule_search_locations=None, _set_fileattr=True, _cached='lib/requests/__pycache__/models.cpython-37.pyc', _initializing=False) at remote 0x354cd70>, '__file__': 'lib/requests/models.py', '__cached__': 'lib/requests/__pycache__/models.cpython-37.pyc', '__builtins__': {'__name__': 'builtins', '__doc__': "Built-in functions, exceptions, and other objects.\n\nNoteworthy: N...(truncated)) at Objects/call.c:283
#16 0x0000000000445180 in _PyFunction_FastCallDict (
    func=<function at remote 0x35b41c0>, args=0x3ce1f08, nargs=1, kwargs=0x0)
    at Objects/call.c:322
[remainder of trace redacted]

Sometimes the C backtrace is slightly different, but very similar:

Core was generated by `./python'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  PyErr_SetObject (exception=0x8b7c00 <_PyExc_StopIteration>, value=0x0)
    at Python/errors.c:101
101	        Py_INCREF(exc_value);

(gdb) bt
#0  PyErr_SetObject (exception=<type at remote 0x8b7c00>, value=0x0)
    at Python/errors.c:101
#1  0x000000000050ba17 in PyErr_SetNone (exception=<optimized out>)
    at Python/errors.c:163
#2  0x00000000005d254d in gen_send_ex (gen=0x3c71b10, arg=<optimized out>, 
    exc=<optimized out>, closing=<optimized out>) at Objects/genobject.c:241
[rest of trace not listed, since it appears to be the same as the previous one]

When running my app's tests, I've also seen one occurrence (possibly related to these crashes) when Python aborted because a reference count was -6.

----------
components: Interpreter Core
messages: 355274
nosy: kchen
priority: normal
severity: normal
status: open
title: Segfault with StopIteration
type: crash
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38571>
_______________________________________

From report at bugs.python.org  Wed Oct 23 22:15:37 2019
From: report at bugs.python.org (Eryk Sun)
Date: Thu, 24 Oct 2019 02:15:37 +0000
Subject: [issue38092] environment variables not passed correctly using new
 virtualenv launching in windows and python3.7+
In-Reply-To: <1568122359.92.0.800539114246.issue38092@roundup.psfhosted.org>
Message-ID: <1571883337.71.0.813489315289.issue38092@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

This should revert to setting `_python_exe = sys.executable` in Lib/multiprocessing/spawn.py. Then the code in Lib/multiprocessing/popen_spawn_win32.py will set __PYVENV_LAUNCHER__ in the spawned process to the virtual environment's sys.executable. Otherwise the worker process has no connection to the virtual environment, other than how sys.path gets manually copied from the parent process. In particular, without setting __PYVENV_LAUNCHER__, sys.executable is not the virtual-environment executable and sys.prefix is not the virtual-environment directory.

Also, the fix for the parameters that are passed to _winapi.CreateProcess needs to be backported to 3.7. Else __PYVENV_LAUNCHER__ won't actually be set in the child.

----------
nosy: +eryksun
resolution: fixed -> 
stage: resolved -> needs patch
status: closed -> open
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38092>
_______________________________________

From report at bugs.python.org  Wed Oct 23 22:47:00 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Thu, 24 Oct 2019 02:47:00 +0000
Subject: [issue38567] urllib.parse.unquote_plus raises incorrect error message
 when string parameter is bytes
In-Reply-To: <1571852750.66.0.0310766347617.issue38567@roundup.psfhosted.org>
Message-ID: <1571885220.41.0.661808918689.issue38567@roundup.psfhosted.org>


Change by Emmanuel Arias <emmanuelarias30 at gmail.com>:


----------
nosy: +eamanu
title: urllib.parse.unquote_plus raises incorrect errormessage when string parameter is bytes -> urllib.parse.unquote_plus raises incorrect error message when string parameter is bytes

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38567>
_______________________________________

From report at bugs.python.org  Thu Oct 24 00:03:21 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Thu, 24 Oct 2019 04:03:21 +0000
Subject: [issue38559] async generators aclose() behavior in 3.8
In-Reply-To: <1571780913.57.0.640148082181.issue38559@roundup.psfhosted.org>
Message-ID: <1571889801.14.0.542602704156.issue38559@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

The more I think about this the more I like new 3.8 behavior. I'm going to close this issue; if anything comes up I'll reopen it later. Sorry for the noise.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38559>
_______________________________________

From report at bugs.python.org  Thu Oct 24 01:33:48 2019
From: report at bugs.python.org (Manjusaka)
Date: Thu, 24 Oct 2019 05:33:48 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571895228.36.0.182096135178.issue38565@roundup.psfhosted.org>


Manjusaka <lizheao940510 at gmail.com> added the comment:

I think it's a good idea to expose the full arguments that people use in lru_cache()

----------
nosy: +Manjusaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 01:46:47 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 05:46:47 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571896007.63.0.156491545939.issue20443@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

Please revert.  An absolute path changes semantics in many real world situations (altering symlink traversals, etc).  People expect the current sys.argv[0] behavior which is "similar to C argv" and matches what was passed on the interpreter command line.

A getcwd() call doesn't even have to succeed.  A single file python program should still be able to run in that environment rather than fail to start.

To help address the original report filing issue, we could add a notion of .co_cwd to code objects for use in resolving co_filename.  Allow it to be '' if getcwd failed at source load time.  Code could check if co_cwd exists and join it with the co_filename.  Also let co_cwd remain empty when there is no valid co_filename for the code.

Preaching: Code that calls os.chdir() is always a potential problem as it alters process global state.  That call is best avoided as modifying globals is impolite.

----------
nosy: +gregory.p.smith
priority: normal -> release blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Thu Oct 24 01:47:26 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 05:47:26 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571896046.77.0.981821848496.issue38565@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 01:49:24 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 05:49:24 +0000
Subject: [issue36541] Make lib2to3 grammar more closely match Python
In-Reply-To: <1554514880.92.0.277848417721.issue36541@roundup.psfhosted.org>
Message-ID: <1571896164.02.0.837710960236.issue36541@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
versions: +Python 3.9 -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36541>
_______________________________________

From report at bugs.python.org  Thu Oct 24 01:54:08 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 05:54:08 +0000
Subject: [issue33348] lib2to3 doesn't parse f(*[] or [])
In-Reply-To: <1524573727.4.0.682650639539.issue33348@psf.upfronthosting.co.za>
Message-ID: <1571896448.66.0.316898784736.issue33348@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
versions: +Python 3.9 -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33348>
_______________________________________

From report at bugs.python.org  Thu Oct 24 01:56:26 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 05:56:26 +0000
Subject: [issue32496] lib2to3 fails to parse a ** of a conditional expression
In-Reply-To: <1515108489.44.0.467229070634.issue32496@psf.upfronthosting.co.za>
Message-ID: <1571896586.1.0.0547874708162.issue32496@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> lib2to3 doesn't parse f(*[] or [])
versions: +Python 3.8, Python 3.9 -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32496>
_______________________________________

From report at bugs.python.org  Thu Oct 24 01:59:52 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 05:59:52 +0000
Subject: [issue33348] lib2to3 doesn't parse f(*[] or [])
In-Reply-To: <1524573727.4.0.682650639539.issue33348@psf.upfronthosting.co.za>
Message-ID: <1571896792.11.0.391124199075.issue33348@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
assignee:  -> gregory.p.smith
nosy: +gregory.p.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33348>
_______________________________________

From report at bugs.python.org  Thu Oct 24 01:59:59 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 05:59:59 +0000
Subject: [issue33348] lib2to3 doesn't parse f(*[] or [])
In-Reply-To: <1524573727.4.0.682650639539.issue33348@psf.upfronthosting.co.za>
Message-ID: <1571896799.2.0.485048074435.issue33348@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
versions: +Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33348>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:01:55 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 06:01:55 +0000
Subject: [issue36541] Make lib2to3 grammar more closely match Python
In-Reply-To: <1554514880.92.0.277848417721.issue36541@roundup.psfhosted.org>
Message-ID: <1571896915.26.0.943787394657.issue36541@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
assignee:  -> gregory.p.smith
nosy: +gregory.p.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36541>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:04:11 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 06:04:11 +0000
Subject: [issue36541] Make lib2to3 grammar better match Python,
 support the := walrus
In-Reply-To: <1554514880.92.0.277848417721.issue36541@roundup.psfhosted.org>
Message-ID: <1571897051.25.0.794559995264.issue36541@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
title: Make lib2to3 grammar more closely match Python -> Make lib2to3 grammar better match Python, support the := walrus

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36541>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:15:27 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 06:15:27 +0000
Subject: [issue38571] Segfault with StopIteration
In-Reply-To: <1571881819.52.0.556347570713.issue38571@roundup.psfhosted.org>
Message-ID: <1571897727.98.0.954694826307.issue38571@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

There isn't really much we can do without a reasonable repeatable way to reproduce the problem.

----------
nosy: +gregory.p.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38571>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:19:14 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 24 Oct 2019 06:19:14 +0000
Subject: [issue33348] lib2to3 doesn't parse f(*[] or [])
In-Reply-To: <1524573727.4.0.682650639539.issue33348@psf.upfronthosting.co.za>
Message-ID: <1571897954.17.0.424253161365.issue33348@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 96b06aefe23521b61e4e9cdd44f5d30b00c7eb95 by Miss Skeleton (bot) (Zsolt Dollenstein) in branch 'master':
bpo-33348: parse expressions after * and ** in lib2to3 (GH-6586)
https://github.com/python/cpython/commit/96b06aefe23521b61e4e9cdd44f5d30b00c7eb95


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33348>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:19:24 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 24 Oct 2019 06:19:24 +0000
Subject: [issue33348] lib2to3 doesn't parse f(*[] or [])
In-Reply-To: <1524573727.4.0.682650639539.issue33348@psf.upfronthosting.co.za>
Message-ID: <1571897964.34.0.192851905811.issue33348@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16443
pull_request: https://github.com/python/cpython/pull/16913

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33348>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:19:30 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 24 Oct 2019 06:19:30 +0000
Subject: [issue33348] lib2to3 doesn't parse f(*[] or [])
In-Reply-To: <1524573727.4.0.682650639539.issue33348@psf.upfronthosting.co.za>
Message-ID: <1571897970.69.0.0661593111307.issue33348@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16444
pull_request: https://github.com/python/cpython/pull/16914

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33348>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:36:32 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 24 Oct 2019 06:36:32 +0000
Subject: [issue33348] lib2to3 doesn't parse f(*[] or [])
In-Reply-To: <1524573727.4.0.682650639539.issue33348@psf.upfronthosting.co.za>
Message-ID: <1571898992.24.0.73621056301.issue33348@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 0160a70acbd9c530802effdf320ab08c7132f4bf by Miss Skeleton (bot) in branch '3.7':
bpo-33348: parse expressions after * and ** in lib2to3 (GH-6586)
https://github.com/python/cpython/commit/0160a70acbd9c530802effdf320ab08c7132f4bf


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33348>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:37:25 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 24 Oct 2019 06:37:25 +0000
Subject: [issue33348] lib2to3 doesn't parse f(*[] or [])
In-Reply-To: <1524573727.4.0.682650639539.issue33348@psf.upfronthosting.co.za>
Message-ID: <1571899045.56.0.0386988580022.issue33348@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset d04661f9ca4a082a2dd9de52df687600d574407e by Miss Skeleton (bot) in branch '3.8':
bpo-33348: parse expressions after * and ** in lib2to3 (GH-6586)
https://github.com/python/cpython/commit/d04661f9ca4a082a2dd9de52df687600d574407e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33348>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:53:52 2019
From: report at bugs.python.org (Manjusaka)
Date: Thu, 24 Oct 2019 06:53:52 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571900032.97.0.513059788865.issue38565@roundup.psfhosted.org>


Change by Manjusaka <lizheao940510 at gmail.com>:


----------
keywords: +patch
pull_requests: +16445
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16915

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:55:32 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 06:55:32 +0000
Subject: [issue38572] Misleading AttributeError accessing fileno attribute in
 tarfile
Message-ID: <1571900132.35.0.991486656774.issue38572@roundup.psfhosted.org>


New submission from Karthikeyan Singaravelan <tir.karthi at gmail.com>:

This came up during https://github.com/psf/requests/issues/5229 . While fileno returns True as an attribute the actual implementation uses self.raw.fileno where the AttributeError is raised at https://github.com/python/cpython/blob/96b06aefe23521b61e4e9cdd44f5d30b00c7eb95/Lib/_pyio.py#L878 (Python implementation) . I guess it should be raising UnsupportedOperation when self.raw has no fileno so that the callers only need to catch UnsupportedOperation. Something like below for fileno implementation that will give a better exception.

   def fileno(self):
        if hasattr(self.raw, 'fileno'):
            return self.raw.fileno()
        else:
            self._unsupported("fileno")

# tarfile_fileno.py

import tarfile
import os

for f in ["foo.txt", "foo.tar"]:
    try:
        os.unlink(f)
    except OSError:
        pass

with open("foo.txt", "w") as f:
    f.write("foo.txt")
    with tarfile.open("foo.tar", "w:gz") as tarfile_obj:
        tarfile_obj.add(f.name)

with tarfile.open("foo.tar", "r:gz") as f:
    member = f.extractfile("foo.txt")
    print(f"Has attr : {hasattr(member, 'fileno')}")
    print(member.fileno())

# Current exception

python.exe .\tarfile_fileno.py
Has attr : True
Traceback (most recent call last):
  File ".\tarfile_fileno.py", line 18, in <module>
    print(member.fileno())
AttributeError: '_FileInFile' object has no attribute 'fileno'

# Proposed exception (Patching tarfile to use _pyio and modifying fileno as above) 

python.exe .\tarfile_fileno.py
Has attr : True
Traceback (most recent call last):
  File ".\tarfile_fileno.py", line 11, in <module>
    print(member.fileno())
  File "C:\Users\kasingar\AppData\Local\Programs\Python\Python37-32\lib\_pyio.py", line 831, in fileno
    self._unsupported("fileno")
  File "C:\Users\kasingar\AppData\Local\Programs\Python\Python37-32\lib\_pyio.py", line 320, in _unsupported
    (self.__class__.__name__, name))
io.UnsupportedOperation: ExFileObject.fileno() not supported

----------
components: Library (Lib)
messages: 355283
nosy: lars.gustaebel, serhiy.storchaka, xtreak
priority: normal
severity: normal
status: open
title: Misleading AttributeError accessing fileno attribute in tarfile
type: behavior
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38572>
_______________________________________

From report at bugs.python.org  Thu Oct 24 02:56:45 2019
From: report at bugs.python.org (Manjusaka)
Date: Thu, 24 Oct 2019 06:56:45 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571900205.48.0.279962256632.issue38565@roundup.psfhosted.org>


Manjusaka <lizheao940510 at gmail.com> added the comment:

I have already make a PR for this issue

but here's a problem. add a new field to cache_info maybe cause some special problem for the third-party libs what're dependent the cache_info

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:09:39 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 24 Oct 2019 07:09:39 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571900979.7.0.692505755.issue38565@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I'm fine with adding a new function:

   >>> f.cache_parameters()
   {'maxsize': 200, 'typed'=False}

----------
assignee:  -> rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:15:08 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 24 Oct 2019 07:15:08 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571901307.99.0.578580501394.issue38565@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:21:04 2019
From: report at bugs.python.org (Manjusaka)
Date: Thu, 24 Oct 2019 07:21:04 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571901664.93.0.490196391127.issue38565@roundup.psfhosted.org>


Manjusaka <lizheao940510 at gmail.com> added the comment:

I think add new function would be a better way 

I will make a new PR

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:29:59 2019
From: report at bugs.python.org (Yevgeny Pats)
Date: Thu, 24 Oct 2019 07:29:59 +0000
Subject: [issue38573] Not Implemented Error in stdLib HTMLParser
Message-ID: <1571902199.4.0.291984198853.issue38573@roundup.psfhosted.org>


New submission from Yevgeny Pats <yev.pats at gmail.com>:

Not implemented error in built-in HTMLParser

from html.parser import HTMLParser
parser = HTMLParser()
parser.feed(bytearray.fromhex('3c215b63612121').decode('ascii'))

# This will throw (found by https://github.com/fuzzitdev/pythonfuzz):
Traceback (most recent call last):
  File "/Users/yevgenyp/fuzzitdev/pythonfuzz/pythonfuzz/fuzzer.py", line 21, in worker
    target(buf)
  File "examples/htmlparser/fuzz.py", line 12, in fuzz
    pass
  File "/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/html/parser.py", line 111, in feed
    self.goahead(0)
  File "/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/html/parser.py", line 179, in goahead
    k = self.parse_html_declaration(i)
  File "/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/html/parser.py", line 264, in parse_html_declaration
    return self.parse_marked_section(i)
  File "/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/_markupbase.py", line 159, in parse_marked_section
    self.error('unknown status keyword %r in marked section' % rawdata[i+3:j])
  File "/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/_markupbase.py", line 34, in error
    "subclasses of ParserBase must override error()")
NotImplementedError: subclasses of ParserBase must override error()

----------
components: Library (Lib)
messages: 355287
nosy: yevgenyp
priority: normal
severity: normal
status: open
title: Not Implemented Error in stdLib HTMLParser
type: crash
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38573>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:33:27 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 24 Oct 2019 07:33:27 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571902407.8.0.871942398982.issue38565@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

It is easy:

diff --git a/Lib/functools.py b/Lib/functools.py
index 3192bd02d9..52c07db749 100644
--- a/Lib/functools.py
+++ b/Lib/functools.py
@@ -499,7 +499,9 @@ def lru_cache(maxsize=128, typed=False):
         # The user_function was passed in directly via the maxsize argument
         user_function, maxsize = maxsize, 128
         wrapper = _lru_cache_wrapper(user_function, maxsize, typed, _CacheInfo)
-        return update_wrapper(wrapper, user_function)
+        func = update_wrapper(wrapper, user_function)
+        func.cache_parameters = lambda: {'maxsize': maxsize, 'typed': typed}
+        return func
     elif maxsize is not None:
         raise TypeError(
             'Expected first argument to be an integer, a callable, or None')

But there are many design questions. Why method instead of just attribute?

        func.cache_parameters = {'maxsize': maxsize, 'typed': typed}

Or maybe just add the "typed" attribute?

        func.typed = typed


Also I consider adding the more general "make_key" parameter to lru_cache(). The "typed" parameter would just specify the default value for "make_key".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:34:34 2019
From: report at bugs.python.org (Leon Matthews)
Date: Thu, 24 Oct 2019 07:34:34 +0000
Subject: [issue38574] Dataclasses documentation should show the necessary
 imports
Message-ID: <1571902474.91.0.395635401957.issue38574@roundup.psfhosted.org>


New submission from Leon Matthews <leon.matthews at gmail.com>:

In the code sample documentation for other modules we show the necessary imports, we should do the same for dataclasses.

For example, the very first example uses the `dataclass` decorator without importing it first. It should read::

    from dataclasses import dataclass

    @dataclass
    class InventoryItem:
        ...

----------
assignee: docs at python
components: Documentation
messages: 355289
nosy: Leon Matthews, docs at python
priority: normal
severity: normal
status: open
title: Dataclasses documentation should show the necessary imports
type: enhancement
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38574>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:38:39 2019
From: report at bugs.python.org (Zhipeng Xie)
Date: Thu, 24 Oct 2019 07:38:39 +0000
Subject: [issue38575] Child process deadlock in subprocess.Popen
Message-ID: <1571902719.3.0.191965904237.issue38575@roundup.psfhosted.org>


New submission from Zhipeng Xie <775350901 at qq.com>:

Hi, we had a child process deadlock on _disabling_gc_lock in subprocess.Popen. It seems that after https://github.com/python/cpython/commit/5e8e371364ee58dadb9a4e4e51c7e9cf6bedbfae, subprocess.Popen no longer support to be called in preexec_fn.

Steps to reproduce:
[root at localhost ~]# python2 --version
Python 2.7.15
[root at localhost ~]# python2 mtfork.py 

wait for a while and the child process deadlock

Here is the gdb stack:

(gdb) py-bt
Traceback (most recent call first):
  Waiting for the GIL
  File "/usr/local/lib/python2.7/subprocess.py", line 931, in _execute_child
    with self._disabling_gc_lock:
  File "/usr/local/lib/python2.7/subprocess.py", line 394, in __init__
    errread, errwrite)
  File "mtfork.py", line 36, in run_cmd
    stderr=subprocess.PIPE)
  File "/usr/local/lib/python2.7/subprocess.py", line 989, in _execute_child
    preexec_fn()
  File "/usr/local/lib/python2.7/subprocess.py", line 394, in __init__
    errread, errwrite)
  File "mtfork.py", line 15, in run_command
    stdout=arg_stdout, stderr=arg_stderr, shell=True)
  File "mtfork.py", line 51, in _readerthread3
    status = run_command("/root/exe",preexec_fn=preexec_fn_no_args)
  File "/usr/local/lib/python2.7/threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/local/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/usr/local/lib/python2.7/threading.py", line 774, in __bootstrap
    self.__bootstrap_inner()
(gdb) py-list
 926                # The first char specifies the exception type: 0 means
 927                # OSError, 1 means some other error.
 928                errpipe_read, errpipe_write = self.pipe_cloexec()
 929                try:
 930                    try:
>931                        with self._disabling_gc_lock:
 932                            gc_was_enabled = gc.isenabled()
 933                            # Disable gc to avoid bug where gc -> file_dealloc ->
 934                            # write to stderr -> hang.
 935                            # https://bugs.python.org/issue1336
 936                            gc.disable()

----------
components: Library (Lib)
files: mtfork.py
messages: 355290
nosy: Zhipeng Xie
priority: normal
severity: normal
status: open
title: Child process deadlock in subprocess.Popen
type: behavior
versions: Python 2.7
Added file: https://bugs.python.org/file48675/mtfork.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38575>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:42:22 2019
From: report at bugs.python.org (Manjusaka)
Date: Thu, 24 Oct 2019 07:42:22 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571902942.74.0.43467986768.issue38565@roundup.psfhosted.org>


Manjusaka <lizheao940510 at gmail.com> added the comment:

I think to modify in lru_cache should be good in normal circumstance

But here's maybe some people modify the wrapped object that underlying in  lru_cache

So I prefer to add a new function in _functools.c?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:47:04 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 24 Oct 2019 07:47:04 +0000
Subject: [issue38574] Dataclasses documentation should show the necessary
 imports
In-Reply-To: <1571902474.91.0.395635401957.issue38574@roundup.psfhosted.org>
Message-ID: <1571903224.9.0.567238315988.issue38574@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

This is a duplicate of issue 36661.

----------
nosy: +eric.smith
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Missing dataclass decorator import in dataclasses module docs

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38574>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:50:34 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 07:50:34 +0000
Subject: [issue35745] Add import statement in dataclass code snippet
In-Reply-To: <1547566391.87.0.956827047672.issue35745@roundup.psfhosted.org>
Message-ID: <1571903434.38.0.851581840173.issue35745@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

See also https://bugs.python.org/issue36661

----------
nosy: +eric.smith, xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35745>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:51:18 2019
From: report at bugs.python.org (Riccardo Schirone)
Date: Thu, 24 Oct 2019 07:51:18 +0000
Subject: [issue38576] CVE-2019-18348 CRLF injection via the host part of the
 url passed to urlopen()
Message-ID: <1571903478.88.0.753943817426.issue38576@roundup.psfhosted.org>


New submission from Riccardo Schirone <rschiron at redhat.com>:

Copy-pasted from https://bugs.python.org/issue30458#msg347282

================
The commit b7378d77289c911ca6a0c0afaf513879002df7d5 is incomplete: it doesn't seem to check for control characters in the "host" part of the URL, only in the "path" part of the URL. Example:
---
try:
    from urllib import request as urllib_request
except ImportError:
    import urllib2 as urllib_request
import socket
def bug(*args):
    raise Exception(args)
# urlopen() must not call create_connection()
socket.create_connection = bug
urllib_request.urlopen('http://127.0.0.1\r\n\x20hihi\r\n :11211')
---

The URL comes from the first message of this issue:
https://bugs.python.org/issue30458#msg294360

Development branches 2.7 and master produce a similar output:
---
Traceback (most recent call last):
 ...
Exception: (('127.0.0.1\r\n hihi\r\n ', 11211), ..., None)
---

So urllib2/urllib.request actually does a real network connection (DNS query), whereas it should reject control characters in the "host" part of the URL.

***

A second problem comes into the game. Some C libraries like glibc strip the end of the hostname (strip at the first newline character) and so HTTP Header injection is still possible is this case:
https://bugzilla.redhat.com/show_bug.cgi?id=1673465

***

According to the RFC 3986, the "host" grammar doesn't allow any control character, it looks like:

   host          = IP-literal / IPv4address / reg-name

   ALPHA (letters)
   DIGIT (decimal digits)
   unreserved    = ALPHA / DIGIT / "-" / "." / "_" / "~"
      pct-encoded = "%" HEXDIG HEXDIG
      sub-delims  = "!" / "$" / "&" / "'" / "(" / ")"
                  / "*" / "+" / "," / ";" / "="
   reg-name      = *( unreserved / pct-encoded / sub-delims )

   IP-literal    = "[" ( IPv6address / IPvFuture  ) "]"
   IPvFuture     = "v" 1*HEXDIG "." 1*( unreserved / sub-delims / ":" )
   IPv6address   =                            6( h16 ":" ) ls32
                 /                       "::" 5( h16 ":" ) ls32
                 / [               h16 ] "::" 4( h16 ":" ) ls32
                 / [ *1( h16 ":" ) h16 ] "::" 3( h16 ":" ) ls32
                 / [ *2( h16 ":" ) h16 ] "::" 2( h16 ":" ) ls32
                 / [ *3( h16 ":" ) h16 ] "::"    h16 ":"   ls32
                 / [ *4( h16 ":" ) h16 ] "::"              ls32
                 / [ *5( h16 ":" ) h16 ] "::"              h16
                 / [ *6( h16 ":" ) h16 ] "::"
   h16           = 1*4HEXDIG
   ls32          = ( h16 ":" h16 ) / IPv4address
   IPv4address   = dec-octet "." dec-octet "." dec-octet "." dec-octet
================


CVE-2019-18348 was assigned to this flaw, which is similar to CVE-2019-9947 and CVE-2019-9740 but it is about the *host* part of a url.

----------
messages: 355294
nosy: rschiron
priority: normal
severity: normal
status: open
title: CVE-2019-18348 CRLF injection via the host part of the url passed to urlopen()
type: security

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38576>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:54:30 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 07:54:30 +0000
Subject: [issue38573] Not Implemented Error in stdLib HTMLParser
In-Reply-To: <1571902199.4.0.291984198853.issue38573@roundup.psfhosted.org>
Message-ID: <1571903670.81.0.476459742543.issue38573@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

See also https://bugs.python.org/issue32876 and https://bugs.python.org/issue31844

----------
nosy: +berker.peksag, ezio.melotti, xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38573>
_______________________________________

From report at bugs.python.org  Thu Oct 24 03:55:28 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 07:55:28 +0000
Subject: [issue38576] CVE-2019-18348 CRLF injection via the host part of the
 url passed to urlopen()
In-Reply-To: <1571903478.88.0.753943817426.issue38576@roundup.psfhosted.org>
Message-ID: <1571903728.59.0.823333286106.issue38576@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +vstinner, xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38576>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:02:46 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 08:02:46 +0000
Subject: [issue38566] Description of '\w' behavior is vague in `re`
 documentation
In-Reply-To: <1571848118.32.0.881781017255.issue38566@roundup.psfhosted.org>
Message-ID: <1571904166.48.0.575073826502.issue38566@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +serhiy.storchaka
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38566>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:06:28 2019
From: report at bugs.python.org (Manjusaka)
Date: Thu, 24 Oct 2019 08:06:28 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571904388.02.0.93583952696.issue38565@roundup.psfhosted.org>


Manjusaka <lizheao940510 at gmail.com> added the comment:

I have already make a new function like this

static PyObject *
lru_cache_cache_parameters(lru_cache_object *self)
{
    PyObject *cache_parameters =  PyDict_New();
    PyDict_SetItemString(cache_parameters, "maxsize", PyLong_FromSsize_t(self->maxsize));
    PyDict_SetItemString(cache_parameters, "typed", self->typed == 0 ? Py_False : Py_True);
    return cache_parameters;
}

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:08:50 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 24 Oct 2019 08:08:50 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571904530.78.0.995666032732.issue38565@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

The rule used in the lru_cache implementation is: do not write in C that can be written in Python.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:10:13 2019
From: report at bugs.python.org (Manjusaka)
Date: Thu, 24 Oct 2019 08:10:13 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571904613.08.0.413252001818.issue38565@roundup.psfhosted.org>


Change by Manjusaka <lizheao940510 at gmail.com>:


----------
pull_requests: +16446
pull_request: https://github.com/python/cpython/pull/16916

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:12:29 2019
From: report at bugs.python.org (Riccardo Schirone)
Date: Thu, 24 Oct 2019 08:12:29 +0000
Subject: [issue30458] [security][CVE-2019-9740][CVE-2019-9947] HTTP Header
 Injection (follow-up of CVE-2016-5699)
In-Reply-To: <1495638091.75.0.96439752743.issue30458@psf.upfronthosting.co.za>
Message-ID: <1571904749.3.0.802307895867.issue30458@roundup.psfhosted.org>


Riccardo Schirone <rschiron at redhat.com> added the comment:

I have created https://bugs.python.org/issue38576 to address CVE-2019-18348.

@gregory.p.smith if you have particular complains about these CVEs feel free to let me know (even privately). I think the security impact of these flaws is: an application that relies on urlopen/HTTPConnection/etc. where either the query part, the path part or the host part are user-controlled, could be exploited to send unintended HTTP headers to other hosts (maybe services that would not be directly reachable by the user).

FYI, there were some good replies to that CVE talk, one of which is https://grsecurity.net/reports_of_cves_death_greatly_exaggerated .

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30458>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:20:16 2019
From: report at bugs.python.org (=?utf-8?q?Bj=C3=B6rn_Pollex?=)
Date: Thu, 24 Oct 2019 08:20:16 +0000
Subject: [issue38577] OPENSSL_* flags not propagated to extensions during build
Message-ID: <1571905216.83.0.0723614632287.issue38577@roundup.psfhosted.org>


New submission from Bj?rn Pollex <bjoern.pollex at soundcloud.com>:

When building Python 3.7.2 using pyenv on MacOS, it will use `--with-openssl` to configure OpenSSL. With that option, the compiler options for OpenSSL will be passed via `OPENSSL_*` variables, rather than normal compiler flags (e.g. `OPENSSL_LDFLAGS` vs. `LDFLAGS`). When compiling an extension, these flags will not be propagated by `distutils`, and so an extension that depends on OpenSSL fails to compile.

I'm not sure what the expected behavior here is. Should the package handle this by querying `sysconfig` directly in `setup.py`? Or should this be handled automatically by `distutils`?

Specifically, I ran into this issue when trying to install `mysqlclient-python` (https://github.com/PyMySQL/mysqlclient-python).

----------
messages: 355299
nosy: Bj?rn Pollex
priority: normal
severity: normal
status: open
title: OPENSSL_* flags not propagated to extensions during build
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38577>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:24:00 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 08:24:00 +0000
Subject: [issue38172] Python 3.8 Segfult with Bandersnatch pytest Suite
In-Reply-To: <1568472460.87.0.817204992487.issue38172@roundup.psfhosted.org>
Message-ID: <1571905440.62.0.204233216735.issue38172@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

It seems now bandersnatch is tested with python 3.8.0 stable release and passes : https://travis-ci.org/pypa/bandersnatch/builds/599806554 . @cooperlees, can you please confirm and close the issue?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38172>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:25:25 2019
From: report at bugs.python.org (=?utf-8?q?Bj=C3=B6rn_Pollex?=)
Date: Thu, 24 Oct 2019 08:25:25 +0000
Subject: [issue38577] OPENSSL_* flags not propagated to extensions during build
In-Reply-To: <1571905216.83.0.0723614632287.issue38577@roundup.psfhosted.org>
Message-ID: <1571905525.86.0.701464857582.issue38577@roundup.psfhosted.org>


Change by Bj?rn Pollex <bjoern.pollex at soundcloud.com>:


----------
assignee:  -> christian.heimes
components: +Extension Modules, SSL, macOS
nosy: +christian.heimes, ned.deily, ronaldoussoren

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38577>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:37:37 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 08:37:37 +0000
Subject: [issue35293] make doctest (Sphinx) emits a lot of warnings
In-Reply-To: <1542835631.23.0.788709270274.issue35293@psf.upfronthosting.co.za>
Message-ID: <1571906257.6.0.72811602006.issue35293@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Relevant docutils upstream issue : https://sourceforge.net/p/docutils/bugs/373/ . Also the SyntaxWarning was changed to DeprecationWarning with msg349335.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35293>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:40:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 08:40:13 +0000
Subject: [issue38172] Python 3.8 Segfult with Bandersnatch pytest Suite
In-Reply-To: <1568472460.87.0.817204992487.issue38172@roundup.psfhosted.org>
Message-ID: <1571906413.45.0.670022912864.issue38172@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I will do it differently. Nobody managed to reproduce the bug. The upstream CI looks to be fine. So I close the issue.

If someone sees a crash, please open a new issue with more context, like explain how to reproduce it ;-)

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38172>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:45:46 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 08:45:46 +0000
Subject: [issue25430] speed up ipaddress __contain__ method
In-Reply-To: <1445083038.14.0.911555841878.issue25430@psf.upfronthosting.co.za>
Message-ID: <1571906746.61.0.455883546005.issue25430@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Closing it as resolved since the optimization was merged in 3.8.0 . Thanks @gescheit for the report and patch.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue25430>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:46:23 2019
From: report at bugs.python.org (Manjusaka)
Date: Thu, 24 Oct 2019 08:46:23 +0000
Subject: [issue38565] Expose the value passed of typed passed to
 functools.lru_cache
In-Reply-To: <1571842254.4.0.33528560442.issue38565@roundup.psfhosted.org>
Message-ID: <1571906783.34.0.780599055436.issue38565@roundup.psfhosted.org>


Manjusaka <lizheao940510 at gmail.com> added the comment:

Yes, you are right, we shouldn't consider about the unstandard using way. I will update my PR

BTW, what're means for the "make_key" parameter?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38565>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:47:12 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 08:47:12 +0000
Subject: [issue27992] Clarify %(prog)s in argparse help formatter returns
 basename of sys.argv[0] by default
In-Reply-To: <1473217852.97.0.553971829799.issue27992@psf.upfronthosting.co.za>
Message-ID: <1571906832.55.0.740144873267.issue27992@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27992>
_______________________________________

From report at bugs.python.org  Thu Oct 24 04:49:33 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 08:49:33 +0000
Subject: [issue31670] Associate .wasm with application/wasm
In-Reply-To: <1507011746.68.0.213398074469.issue31670@psf.upfronthosting.co.za>
Message-ID: <1571906973.7.0.307529697433.issue31670@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
superseder:  -> http.server module sets incorrect mimetype for WebAssembly files
versions:  -Python 2.7, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31670>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:00:00 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 09:00:00 +0000
Subject: [issue34792] Tutorial doesn''t discuss / and * function arguments
In-Reply-To: <1537811932.84.0.956365154283.issue34792@psf.upfronthosting.co.za>
Message-ID: <1571907600.35.0.912489835418.issue34792@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

With PEP 570 implementation docs were expanded : https://github.com/python/cpython/commit/b76302ddd0896cb39ce69909349b53db6e7776e2#diff-d764089fca21fdc70d55804714b1cba5

----------
nosy: +pablogsal

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34792>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:09:30 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 09:09:30 +0000
Subject: [issue32080] Re locale test fails after installing Python 3.6.3 on
 ubuntu 16.04
In-Reply-To: <1511157949.99.0.213398074469.issue32080@psf.upfronthosting.co.za>
Message-ID: <1571908170.38.0.265097417823.issue32080@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Looking at the traceback in the screenshot this seems to be same as issue29571 happening on en_IN locale.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32080>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:13:41 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 09:13:41 +0000
Subject: [issue37922] inspect.getsource returns wrong class definition when
 multiple class definitions share the same name (but are defined in different
 scopes)
In-Reply-To: <1566513967.26.0.232695535045.issue37922@roundup.psfhosted.org>
Message-ID: <1571908421.09.0.389686507588.issue37922@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Closing it as duplicate of issue35113.

----------
nosy: +serhiy.storchaka
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> inspect.getsource returns incorrect source for classes when class definition is part of multiline strings
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37922>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:14:34 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 09:14:34 +0000
Subject: [issue38578] test_concurrent_futures failed on AMD64 FreeBSD Shared
 3.8
Message-ID: <1571908474.05.0.296505367308.issue38578@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

On AMD64 FreeBSD Shared 3.8 which is know to be very slow, different test_concurrent_futures tests failed.

https://buildbot.python.org/all/#builders/374/builds/3

test_concurrent_futures was run twice. Once in parallel of other tests, then alone in sequence.


The first run emitted two "threading_cleanup() failed" warnings and test_idle_thread_reuse() failed:

test_idle_thread_reuse (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 1.05s Warning -- threading_cleanup() failed to cleanup 2 threads (count: 2, dangling: 3)
test_map (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 3.80s Warning -- threading_cleanup() failed to cleanup -2 threads (count: 0, dangling: 1)

FAIL: test_idle_thread_reuse (test.test_concurrent_futures.ThreadPoolExecutorTest)
----------------------------------------------------------------------
Traceback (most recent call last):
? File "/usr/home/buildbot/python/3.8.koobs-freebsd-564d/build/Lib/test/test_concurrent_futures.py", line 782, in test_idle_thread_reuse
? ? self.assertEqual(len(executor._threads), 1)
AssertionError: 2 != 1

At the second run, test_free_reference() failed:

1:15:08 load avg: 9.24 Re-running test_concurrent_futures in verbose mode

FAIL: test_free_reference (test.test_concurrent_futures.ThreadPoolExecutorTest)
----------------------------------------------------------------------
Traceback (most recent call last):
? File "/usr/home/buildbot/python/3.8.koobs-freebsd-564d/build/Lib/test/test_concurrent_futures.py", line 745, in test_free_reference
? ? self.assertIsNone(wr())
AssertionError: <test.test_concurrent_futures.MyObject object at 0x8031cc780> is not None

----------
components: Tests
messages: 355308
nosy: vstinner
priority: normal
severity: normal
status: open
title: test_concurrent_futures failed on AMD64 FreeBSD Shared 3.8
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38578>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:15:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 09:15:57 +0000
Subject: [issue38578] test_concurrent_futures failed on AMD64 FreeBSD Shared
 3.8
In-Reply-To: <1571908474.05.0.296505367308.issue38578@roundup.psfhosted.org>
Message-ID: <1571908557.87.0.943013168739.issue38578@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Logs around the first failure:

...
test_zero_timeout (test.test_concurrent_futures.ThreadPoolAsCompletedTest) ... 2.24s ok
test_default_workers (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 0.96s ok
test_free_reference (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 0.56s ok
test_idle_thread_reuse (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 1.05s Warning -- threading_cleanup() failed to cleanup 2 threads (count: 2, dangling: 3)
Dangling thread: <Thread(ThreadPoolExecutor-9_1, started daemon 34379716096)>
Dangling thread: <_MainThread(MainThread, started 34371022848)>
Dangling thread: <Thread(ThreadPoolExecutor-9_0, started daemon 34399619584)>
FAIL
test_map (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 3.80s Warning -- threading_cleanup() failed to cleanup -2 threads (count: 0, dangling: 1)
Dangling thread: <_MainThread(MainThread, started 34371022848)>
ok
test_map_exception (test.test_concurrent_futures.ThreadPoolExecutorTest) ... 1.67s ok
test_map_submits_without_iteration (test.test_concurrent_futures.ThreadPoolExecutorTest)
Tests verifying issue 11777. ... 2.64s ok
...

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38578>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:18:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 09:18:32 +0000
Subject: [issue38546] test_concurrent_futures: test_interpreter_shutdown()
 warning "reap_children() reaped child process" on AMD64 RHEL7 3.x
In-Reply-To: <1571656800.65.0.31860297071.issue38546@roundup.psfhosted.org>
Message-ID: <1571908712.91.0.231221107885.issue38546@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

New warning on AMD64 RHEL8 LTO + PGO 3.x:
https://buildbot.python.org/all/#/builders/284/builds/171

...
test_killed_child (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.26s ok
test_map (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.29s ok
test_map_chunksize (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.31s ok
test_map_exception (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.30s ok
test_map_timeout (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 6.29s ok
test_max_workers_negative (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.32s ok
test_max_workers_too_large (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... skipped 'Windows-only process limit'
test_no_stale_references (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.29s ok
test_ressources_gced_in_workers (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 1.58s ok
test_shutdown_race_issue12456 (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.30s Warning -- reap_children() reaped child process 10340
ok
test_submit (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.29s ok
test_submit_keyword (test.test_concurrent_futures.ProcessPoolSpawnProcessPoolExecutorTest) ... 0.31s ok
...

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38546>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:18:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 09:18:56 +0000
Subject: [issue38448] test_concurrent_futures: reap_children() reaped child
 process 26487 on AMD64 RHEL8 Refleaks 3.x
In-Reply-To: <1570799333.75.0.17786723855.issue38448@roundup.psfhosted.org>
Message-ID: <1571908736.41.0.509056423458.issue38448@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I close this issue as a duplicate of bpo-38546.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> test_concurrent_futures: test_interpreter_shutdown() warning "reap_children() reaped child process" on AMD64 RHEL7 3.x

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38448>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:19:40 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 09:19:40 +0000
Subject: [issue38546] test_concurrent_futures: reap_children() warnings on
 RHEL7 and RHEL8 buildbots
In-Reply-To: <1571656800.65.0.31860297071.issue38546@roundup.psfhosted.org>
Message-ID: <1571908780.3.0.987377000485.issue38546@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I closed bpo-38448 as duplicate of this issue. Copy of its only message:

AMD64 RHEL8 Refleaks 3.x:
https://buildbot.python.org/all/#/builders/272/builds/23

0:27:13 load avg: 4.88 [416/419/1] test_concurrent_futures failed (env changed) (17 min 11 sec) -- running: test_capi (7 min 28 sec), test_gdb (8 min 49 sec), test_asyncio (23 min 23 sec)
beginning 6 repetitions
123456
.Warning -- reap_children() reaped child process 26487
.....
Warning -- multiprocessing.process._dangling was modified by test_concurrent_futures
  Before: set()
  After:  {<weakref at 0x7fdc08f44e30; to 'SpawnProcess' at 0x7fdc0a467c30>}

----------
title: test_concurrent_futures: test_interpreter_shutdown() warning "reap_children() reaped child process" on AMD64 RHEL7 3.x -> test_concurrent_futures: reap_children() warnings on RHEL7 and RHEL8 buildbots

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38546>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:28:51 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 24 Oct 2019 09:28:51 +0000
Subject: [issue38323] asyncio: MultiLoopWatcher has a race condition
 (test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x)
In-Reply-To: <1569848255.08.0.155489980043.issue38323@roundup.psfhosted.org>
Message-ID: <1571909331.39.0.992746781783.issue38323@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
nosy: +aeros

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38323>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:31:30 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 09:31:30 +0000
Subject: [issue37911] Minor error in PEP567 code example
In-Reply-To: <1566428475.33.0.0889947555242.issue37911@roundup.psfhosted.org>
Message-ID: <1571909490.2.0.0407737118623.issue37911@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37911>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:35:46 2019
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 24 Oct 2019 09:35:46 +0000
Subject: [issue38577] OPENSSL_* flags not propagated to extensions during build
In-Reply-To: <1571905216.83.0.0723614632287.issue38577@roundup.psfhosted.org>
Message-ID: <1571909746.37.0.852915128366.issue38577@roundup.psfhosted.org>


Christian Heimes <lists at cheimes.de> added the comment:

'--with-openssl' purpose is to override the OpenSSL location for Python's internal _ssl and _hashlib module. It is not designed to interfere with 3rd party extensions that are built with distutils or setuptools.

It is the decision of a 3rd party package how it wants to handle these extra flags -- or if it is able to use them at all. In case of PyMySQL you must use the same shared libraries as libmysqlclient. You cannot use a  different OpenSSL ABIs, APIs, or shared libraries for PyMySQL and libmysqlclient.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38577>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:37:19 2019
From: report at bugs.python.org (=?utf-8?q?Bj=C3=B6rn_Pollex?=)
Date: Thu, 24 Oct 2019 09:37:19 +0000
Subject: [issue38577] OPENSSL_* flags not propagated to extensions during build
In-Reply-To: <1571905216.83.0.0723614632287.issue38577@roundup.psfhosted.org>
Message-ID: <1571909839.7.0.860745069866.issue38577@roundup.psfhosted.org>


Bj?rn Pollex <bjoern.pollex at soundcloud.com> added the comment:

Thanks for the response, that clarifies it! In that case this issue is invalid.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38577>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:42:12 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 09:42:12 +0000
Subject: [issue20271] urllib.parse.urlparse() accepts wrong URLs
In-Reply-To: <1389789129.93.0.775761654638.issue20271@psf.upfronthosting.co.za>
Message-ID: <1571910132.24.0.959674098159.issue20271@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

With Victor's PR 16780, "http://[::1]spam:80" would raise a ValueError.

ValueError: Invalid network location: '[::1]spam:80'

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20271>
_______________________________________

From report at bugs.python.org  Thu Oct 24 05:54:58 2019
From: report at bugs.python.org (Malek Ghantous)
Date: Thu, 24 Oct 2019 09:54:58 +0000
Subject: [issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 >
 alledged missing X509_VERIFY_PARAM_set1_host() support
In-Reply-To: <1530609211.5.0.56676864532.issue34028@psf.upfronthosting.co.za>
Message-ID: <1571910898.67.0.788180373232.issue34028@roundup.psfhosted.org>


Malek Ghantous <malek.ghantous at gmail.com> added the comment:

Thanks for your responses. Yum is not an option as I'm on a machine without root privileges.  

OK, so I have to be a bit contrite here, I tried everything you suggested, but in the end the solution goes back to this comment, and the LDFLAGS environment variable:

https://bugs.python.org/issue34028?@ok_message=msg%20355232%20cr%C3%A9%C3%A9%0Aissue%2034028%20message_count%2C%20type%2C%20versions%2C%20curieux%2C%20nosy_count%2C%20messages%20modifi%C3%A9%28s%29%20avec%20succ%C3%A8s&@template=item#msg339455

I think I was using the wrong compiler when I tried that solution the first time.  So I'm sorry about that.  

But while we're here, I may as well ask if there isn't another way to do this, without having recourse to the environment variable.  Is there a way to specify these flags using just the configure script?  Based on something I read somewhere on the web, I generally prefer to steer clear of setting environment variables, though perhaps I needn't be so reluctant.  Incidentally, the environment variables OPENSSL_LDFLAGS etc as suggested in config.log (thanks for that, I wouldn't have thought to look there) do not appear to work.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34028>
_______________________________________

From report at bugs.python.org  Thu Oct 24 06:10:09 2019
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 24 Oct 2019 10:10:09 +0000
Subject: [issue34028] Python 3.7.0 wont compile with SSL Support 1.1.0 >
 alledged missing X509_VERIFY_PARAM_set1_host() support
In-Reply-To: <1530609211.5.0.56676864532.issue34028@psf.upfronthosting.co.za>
Message-ID: <1571911809.92.0.536541792027.issue34028@roundup.psfhosted.org>


Christian Heimes <lists at cheimes.de> added the comment:

--with-openssl only sets the header location for the pre-processor and library path for the dynamic linker. It does *not* affect the search and lookup paths of the dynamic loader! If you have installed OpenSSL in a non-standard location then you need to tell the dynamic loader how to load the shared libraries. This can be done in three ways:

* configure the dynamic loader globally in /etc/ld.so.conf (not advised for custom OpenSSL)
* Add a rpath to the ELF header of _ssl and _hashlib extensions at link time. This can be accomplished by setting LD_RUN_PATH=/path/to/lib or LDFLAGS=-Wl,-rpath,/path/to/lib
* Add the shared library directory to the runtime lookup path of ld.so by setting LD_LIBRARY_PATH env var.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34028>
_______________________________________

From report at bugs.python.org  Thu Oct 24 06:29:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 10:29:32 +0000
Subject: [issue13131] FD leak in urllib2
In-Reply-To: <1318076753.32.0.0530567720617.issue13131@psf.upfronthosting.co.za>
Message-ID: <1571912972.85.0.731807326516.issue13131@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

This issue is a duplicate of bpo-12133 which has been fixed in Python 2.7 by:

commit c74a6ba2d6c1f331896cf8dacc698b0b88c7e670
Author: Victor Stinner <victor.stinner at haypocalc.com>
Date:   Fri Jun 17 14:06:27 2011 +0200

    Issue #12133: AbstractHTTPHandler.do_open() of urllib.request closes the HTTP
    connection if its getresponse() method fails with a socket error. Patch written
    by Ezio Melotti.

----------
nosy: +vstinner
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> ResourceWarning in urllib.request

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13131>
_______________________________________

From report at bugs.python.org  Thu Oct 24 06:31:24 2019
From: report at bugs.python.org (Dan Snider)
Date: Thu, 24 Oct 2019 10:31:24 +0000
Subject: [issue38579] 'u' formatted arrays mostly prevent appends of 4 byte
 characters
Message-ID: <1571913084.38.0.724512448926.issue38579@roundup.psfhosted.org>


New submission from Dan Snider <mr.assume.away at gmail.com>:

Unicode characters with code points above u+ffff can only be added to the end of an array, and only from a call to the "fromunicode" method. This is because "fromunicode" uses a different procedure to modify the array compared to __new__, __setitem__, append, and extend array methods, all of which eventually call u_setitem routine, which calls PyArg_Parse with a format spec of "u#". The error occurs in that call, from what at first glance appears to be an incorrect length determination for unicode objects of the 4 byte kind.

----------
components: Library (Lib)
messages: 355319
nosy: bup
priority: normal
severity: normal
status: open
title: 'u' formatted arrays mostly prevent appends of 4 byte characters
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38579>
_______________________________________

From report at bugs.python.org  Thu Oct 24 06:31:31 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 10:31:31 +0000
Subject: [issue27657] urlparse fails if the path is numeric
In-Reply-To: <1469908637.82.0.696114480311.issue27657@psf.upfronthosting.co.za>
Message-ID: <1571913091.42.0.356683035675.issue27657@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

This issue got fixes, so I close it.

----------
nosy: +vstinner
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue27657>
_______________________________________

From report at bugs.python.org  Thu Oct 24 06:32:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 10:32:56 +0000
Subject: [issue23505] [CVE-2015-2104] Urlparse insufficient validation leads
 to open redirect
In-Reply-To: <1424736713.95.0.74935935546.issue23505@psf.upfronthosting.co.za>
Message-ID: <1571913176.3.0.701640736259.issue23505@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: Urlparse insufficient validation leads to open redirect -> [CVE-2015-2104] Urlparse insufficient validation leads to open redirect

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23505>
_______________________________________

From report at bugs.python.org  Thu Oct 24 06:38:04 2019
From: report at bugs.python.org (Leonardo Taccari)
Date: Thu, 24 Oct 2019 10:38:04 +0000
Subject: [issue33384] Build does not work with closed stdin on NetBSD
In-Reply-To: <1571787002.99.0.473688225374.issue33384@roundup.psfhosted.org>
Message-ID: <5db17f08.1c69fb81.fd476.90b7@mx.google.com>


Leonardo Taccari <iamleot at gmail.com> added the comment:

Hello Victor,
I can confirm that I can no longer reproduce this problem with Python
3.7.5 on NetBSD and according a double-check to
Python/pylifecycle.c:is_valid_fd() now fstat() is always used on
NetBSD.

Thanks for the update and for looking at it!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33384>
_______________________________________

From report at bugs.python.org  Thu Oct 24 06:38:18 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 10:38:18 +0000
Subject: [issue36338] urlparse of urllib returns wrong hostname
In-Reply-To: <1552896371.92.0.122580708995.issue36338@roundup.psfhosted.org>
Message-ID: <1571913498.0.0.793316673015.issue36338@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

OMG parsing an URL is a can of worms... There are so many open issues related to URL parsing!

* bpo-18191: urllib.parse.splitport("::1")
* bpo-20271: urllib.parse.urlparse('http://[::1]spam:80')
* bpo-28841: urlparse.urlparse() parses invalid URI without generating an error (examples provided)
* bpo-33342: urlsplit("//user:[@host")
* bpo-34360: 'http://[::1]]'
* bpo-35377: urlparse doesn't validate the scheme
* bpo-35748: 'http://www.google.com\@xxx.com'
* bpo-36338 (this issue): urlparse('http://demo.com[attacker.com]')
* bpo-37678: urlparse('http://user:pass#?[word at example.com:80/path')

Related:

* bpo-3647: urlparse - relative url parsing and joins to be RFC3986 compliance
* bpo-16909: urlparse: add userinfo attribute
* bpo-18140: issue with 'http://auser:secr#et at 192.168.0.1:8080/a/b/c.html'
* bpo-22234: urllib.parse.urlparse accepts any falsy value as an url
* bpo-22852: "urllib.parse wrongly strips empty #fragment, ?query, //netloc"
* bpo-23328: issue with "http://someuser:a/b at 10.11.12.13:1234"
* bpo-23448: "urllib2 needs to remove scope from IPv6 address when creating Host header"
* bpo-23505: [CVE-2015-2104] Urlparse insufficient validation leads to open redirect

There are 124 open issues with "urllib" in their title and 12 open issues with "urlparse" in their title.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36338>
_______________________________________

From report at bugs.python.org  Thu Oct 24 06:39:12 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 10:39:12 +0000
Subject: [issue33384] Build does not work with closed stdin on NetBSD
In-Reply-To: <1524996995.63.0.682650639539.issue33384@psf.upfronthosting.co.za>
Message-ID: <1571913552.79.0.543353241238.issue33384@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> I can confirm that I can no longer reproduce this problem with Python
3.7.5 on NetBSD

Great!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33384>
_______________________________________

From report at bugs.python.org  Thu Oct 24 06:46:11 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 10:46:11 +0000
Subject: [issue32080] Re locale test fails after installing Python 3.6.3 on
 ubuntu 16.04
In-Reply-To: <1511157949.99.0.213398074469.issue32080@psf.upfronthosting.co.za>
Message-ID: <1571913971.31.0.252224752288.issue32080@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Yeah, that's a duplicate of bpo-29571 which has been fixed by:

New changeset 279657bac2856039ba422c18a3d7f227b455e9d6 by Victor Stinner in branch '3.7':
[3.7] bpo-29571: Fix test_re.test_locale_flag() (GH-12178)
https://github.com/python/cpython/commit/279657bac2856039ba422c18a3d7f227b455e9d6

Python 3.7.3 and newer include my fix.

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed
superseder:  -> test_re is failing when local is set for `en_IN`

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32080>
_______________________________________

From report at bugs.python.org  Thu Oct 24 06:47:17 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 10:47:17 +0000
Subject: [issue38576] CVE-2019-18348: CRLF injection via the host part of the
 url passed to urlopen()
In-Reply-To: <1571903478.88.0.753943817426.issue38576@roundup.psfhosted.org>
Message-ID: <1571914037.75.0.82710215598.issue38576@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
title: CVE-2019-18348 CRLF injection via the host part of the url passed to urlopen() -> CVE-2019-18348: CRLF injection via the host part of the url passed to urlopen()

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38576>
_______________________________________

From report at bugs.python.org  Thu Oct 24 07:08:46 2019
From: report at bugs.python.org (Jakub Stasiak)
Date: Thu, 24 Oct 2019 11:08:46 +0000
Subject: [issue38580] select()'s documentation claims only sequences are
 accepted, but it allows all iterables
Message-ID: <1571915326.93.0.150606644361.issue38580@roundup.psfhosted.org>


New submission from Jakub Stasiak <jakub+python.org at stasiak.at>:

Excerpt from the documentation:

"""This is a straightforward interface to the Unix select() system call. The first three arguments are sequences of ?waitable objects?: either integers representing file descriptors or objects with a parameterless method named fileno() returning such an integer:"""

In reality it accepts for example dictionary key views (that's how I discovered it) due to its internal usage of PySequence_Fast, which (from https://docs.python.org/3/c-api/sequence.html#c.PySequence_Fast):

"""Return the sequence or iterable o as an object usable by the other PySequence_Fast* family of functions. If the object is not a sequence or iterable, raises TypeError with m as the message text. Returns NULL on failure."""

I made a pull request to document this behavior in select (https://github.com/python/cpython/pull/16832) but it was recommended that I create this issue because the solution may not be obvious here.

----------
components: Library (Lib)
messages: 355325
nosy: corona10, jstasiak
priority: normal
pull_requests: 16447
severity: normal
status: open
title: select()'s documentation claims only sequences are accepted, but it allows all iterables
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38580>
_______________________________________

From report at bugs.python.org  Thu Oct 24 07:12:06 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 24 Oct 2019 11:12:06 +0000
Subject: [issue38580] select()'s documentation claims only sequences are
 accepted, but it allows all iterables
In-Reply-To: <1571915326.93.0.150606644361.issue38580@roundup.psfhosted.org>
Message-ID: <1571915526.14.0.863949298132.issue38580@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
nosy: +serhiy.storchaka, vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38580>
_______________________________________

From report at bugs.python.org  Thu Oct 24 07:20:13 2019
From: report at bugs.python.org (Lealinux)
Date: Thu, 24 Oct 2019 11:20:13 +0000
Subject: [issue38581] Crash on distutils/util.py when header variable isn't a
 string
Message-ID: <1571916013.0.0.277609072879.issue38581@roundup.psfhosted.org>


New submission from Lealinux <bureau at lea-linux.org>:

Hello,

With some pip3 package, distutils could crash if variable "header" isn't a real string variable :

--------------------------------

$ pip3 install bzr
Collecting bzr
  Using cached https://files.pythonhosted.org/packages/62/3a/81325e34bcc78f67cc33dfac64f44e7c8329d4481dec1b789267b98644c3/bzr-2.7.0.tar.gz
    ERROR: Complete output from command python setup.py egg_info:
    ERROR: running egg_info
    creating pip-egg-info/bzr.egg-info
    writing pip-egg-info/bzr.egg-info/PKG-INFO
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "pip-install/bzr/setup.py", line 781, in <module>
        setup(**ARGS)
      File "distutils/core.py", line 148, in setup
        dist.run_commands()
      File "distutils/dist.py", line 966, in run_commands
        self.run_command(cmd)
      File "distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "setuptools/command/egg_info.py", line 289, in run
        writer(self, ep.name, os.path.join(self.egg_info, ep.name))
      File "setuptools/command/egg_info.py", line 621, in write_pkg_info
        metadata.write_pkg_info(cmd.egg_info)
      File "distutils/dist.py", line 1117, in write_pkg_info
        self.write_pkg_file(pkg_info)
      File "setuptools/dist.py", line 165, in write_pkg_file
        long_desc = rfc822_escape(self.get_long_description())
      File "distutils/util.py", line 470, in rfc822_escape
        lines = header.split('\n')
    TypeError: a bytes-like object is required, not 'str'

-----------------------------

On this case (bzr), "header" is a bytes-like object.

On attachment, a patch proposal to have a (possible) solution


PS: newbie on python-core-patching and python-bug-report, sorry if we have missed something

----------
components: Library (Lib)
files: distutils_rfc822_escape.patch
keywords: patch
messages: 355326
nosy: Lealinux
priority: normal
severity: normal
status: open
title: Crash on distutils/util.py when header variable isn't a string
type: crash
versions: Python 3.8
Added file: https://bugs.python.org/file48676/distutils_rfc822_escape.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38581>
_______________________________________

From report at bugs.python.org  Thu Oct 24 07:22:49 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 11:22:49 +0000
Subject: [issue38581] Crash on distutils/util.py when header variable isn't a
 string
In-Reply-To: <1571916013.0.0.277609072879.issue38581@roundup.psfhosted.org>
Message-ID: <1571916169.88.0.973559983583.issue38581@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

That sounds like a bug in bzr. You may try Breezy which supports Python 3.

https://launchpad.net/brz

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38581>
_______________________________________

From report at bugs.python.org  Thu Oct 24 08:01:00 2019
From: report at bugs.python.org (veaba)
Date: Thu, 24 Oct 2019 12:01:00 +0000
Subject: [issue38582] Regular match overflow
Message-ID: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>


New submission from veaba <908662421 at qq.com>:

Regular match overflow
code:
```python
import re
# list => str
def list_to_str(str_list, code=""):
    if isinstance(str_list, list):
        return code.join(str_list)
    else:
        return ''
def fn_parse_code(list_str, text):
    code_text_str=''
    code_text_str = list_to_str(list_str, '|')  # => xxx|oo
    reg_list = ['+', '.', '[', ']','((','))']
    for reg in reg_list:
        code_text_str_temp = code_text_str.replace(reg, "\\" + reg).replace('((','(\\(').replace('))','))')
        code_text_str=code_text_str_temp

    # compile
    pattern_str = re.compile(code_text_str )

    #list_str=>\\1\\2\\...

    flag_str = ''

    for item in enumerate(list_str):
        flag_str = flag_str + "\\" + str(item[0] + 1)

    print("1:",pattern_str)
    print("2:",flag_str)
    print("3:",text)
    reg_text = re.sub(r''+code_text_str+'', "`" + flag_str + "`", text)
    return reg_text

# a list
strs=['(tf.batch_gather)', '(None)', '(tf.bitwise.bitwise_and)', '(None)', '(tf.bitwise.bitwise_or)', '(None)', '(tf.bitwise.bitwise_xor)', '(None)', '(tf.bitwise.invert)', '(None)', '(tf.bitwise.left_shift)', '(None)', '(tf.bitwise.right_shift)', '(None)', '(tf.clip_by_value)', '(None)', '(tf.concat)', "('concat')", '(tf.debugging.check_numerics)', '(None)', '(tf.dtypes.cast)', '(None)', '(tf.dtypes.complex)', '(None)', '(tf.dtypes.saturate_cast)', '(None)', '(tf.dynamic_partition)', '(None)', '(tf.expand_dims)', '(None)', '(None)', '(None)', '(tf.gather_nd)', '(None)', '(0)', '(tf.gather)', '(None)', '(None)', '(None)', '(0)', '(tf.identity)', '(None)', '(tf.io.decode_base64)', '(None)', '(tf.io.decode_compressed)', "('')", '(None)', '(tf.io.encode_base64)', '(False)', '(None)', '(tf.math.abs)', '(None)', '(tf.math.acos)', '(None)', '(tf.math.acosh)', '(None)', '(tf.math.add_n)', '(None)', '(tf.math.add)', '(None)', '(tf.math.angle)', '(None)', '(tf.math.asin)', '(None)', '(tf.math.asinh)', '(None)', '(tf.math.atan2)', '(None)', '(tf.math.atan)', '(None)', '(tf.math.atanh)', '(None)', '(tf.math.ceil)', '(None)', '(tf.math.conj)', '(None)', '(tf.math.cos)', '(None)', '(tf.math.cosh)', '(None)', '(tf.math.digamma)', '(None)', '(tf.math.divide_no_nan)', '(None)', '(tf.math.divide)', '(None)', '(tf.math.equal)', '(None)', '(tf.math.erf)', '(None)', '(tf.math.erfc)', '(None)', '(tf.math.exp)', '(None)', '(tf.math.expm1)', '(None)', '(tf.math.floor)', '(None)', '(tf.math.floordiv)', '(None)', '(tf.math.floormod)', '(None)', '(tf.math.greater_equal)', '(None)', '(tf.math.greater)', '(None)', '(tf.math.imag)', '(None)', '(tf.math.is_finite)', '(None)', '(tf.math.is_inf)', '(None)', '(tf.math.is_nan)', '(None)', '(tf.math.less_equal)', '(None)', '(tf.math.less)', '(None)', '(tf.math.lgamma)', '(None)', '(tf.math.log1p)', '(None)', '(tf.math.log_sigmoid)', '(None)', '(tf.math.log)', '(None)', '(tf.math.logical_and)', '(None)', '(tf.math.logical_not)', '(None)', '(tf.math.logical_or)', '(None)', '(tf.math.logical_xor)', "('LogicalXor')", '(tf.math.maximum)', '(None)', '(tf.math.minimum)', '(None)', '(tf.math.multiply)', '(None)', '(tf.math.negative)', '(None)', '(tf.math.not_equal)', '(None)', '(tf.math.pow)', '(None)', '(tf.math.real)', '(None)', '(tf.math.reciprocal)', '(None)', '(tf.math.reduce_any)', '(None)', '(False)', '(None)', '(tf.math.reduce_max)', '(None)', '(False)', '(None)', '(tf.math.reduce_mean)', '(None)', '(False)', '(None)', '(tf.math.reduce_min)', '(None)', '(False)', '(None)', '(tf.math.reduce_prod)', '(None)', '(False)', '(None)', '(tf.math.reduce_sum)', '(None)', '(False)', '(None)', '(tf.math.rint)', '(None)', '(tf.math.round)', '(None)', '(tf.math.rsqrt)', '(None)', '(tf.math.sign)', '(None)', '(tf.math.sin)', '(None)', '(tf.math.sinh)', '(None)', '(tf.math.sqrt)', '(None)', '(tf.math.square)', '(None)', '(tf.math.squared_difference)', '(None)', '(tf.math.subtract)', '(None)', '(tf.math.tan)', '(None)', '(tf.math.truediv)', '(None)', '(tf.math.unsorted_segment_max)', '(None)', '(tf.math.unsorted_segment_mean)', '(None)', '(tf.math.unsorted_segment_min)', '(None)', '(tf.math.unsorted_segment_prod)', '(None)', '(tf.math.unsorted_segment_sqrt_n)', '(None)', '(tf.math.unsorted_segment_sum)', '(None)', '(tf.ones_like)', '(None)', '(None)', '(True)', '(tf.rank)', '(None)', '(tf.realdiv)', '(None)', '(tf.reduce_all)', '(None)', '(False)', '(None)', '(tf.size)', '(None)', '(tf.int32)', '(tf.squeeze)', '(None)', '(None)', '(None)', '(tf.stack)', '(0)', "('stack')", '(tf.strings.as_string)', '(-1)', '(False)', '(False)', '(-1)', "('')", '(None)', '(tf.strings.join)', "('')", '(None)', '(tf.strings.length)', '(None)', "('BYTE')", '(tf.strings.reduce_join)', '(None)', '(False)', "('')", '(None)', '(tf.strings.regex_full_match)', '(None)', '(tf.strings.regex_replace)', '(True)', '(None)', '(tf.strings.strip)', '(None)', '(tf.strings.substr)', '(None)', "('BYTE')", '(tf.strings.to_hash_bucket_fast)', '(None)', '(tf.strings.to_hash_bucket_strong)', '(None)', '(tf.strings.to_hash_bucket)', '(None)', '(tf.strings.to_hash_bucket)', '(None)', '(tf.strings.to_number)', '(tf.float32)', '(None)', '(tf.strings.unicode_script)', '(None)', '(tf.tile)', '(None)', '(tf.truncatediv)', '(None)', '(tf.truncatemod)', '(None)', '(tf.where)', '(None)', '(None)', '(None)', '(tf.zeros_like)', '(None)', '(None)', '(True)']

codes=[]
for st in strs:
    codes.append('('+st+')')
    
for code in codes:
    x = fn_parse_code(codes, code)
    print("result",x)


# why ? (`@ABCDEFG89HIJKLMNO89PQRSTUVW89XYZ[\]^_89`abcdefg89hijklmno89pqrstuvw89xyz{|}~8901234567890123456789

# hope: (tf.batch_gather)=> `(tf.batch_gather)`

```

----------
files: QQ??20191024195805.png
hgrepos: 384
messages: 355328
nosy: veaba
priority: normal
severity: normal
status: open
title: Regular match overflow
type: security
Added file: https://bugs.python.org/file48677/QQ??20191024195805.png

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Thu Oct 24 08:17:14 2019
From: report at bugs.python.org (Lealinux)
Date: Thu, 24 Oct 2019 12:17:14 +0000
Subject: [issue38581] Crash on distutils/util.py when header variable isn't a
 string
In-Reply-To: <1571916013.0.0.277609072879.issue38581@roundup.psfhosted.org>
Message-ID: <1571919434.67.0.113671333146.issue38581@roundup.psfhosted.org>


Lealinux <bureau at lea-linux.org> added the comment:

bzr (2.7) fail on install with pip3.7/pip3.8
breezy (3.x) success on install with pip3.7/pip3.8

We can forget the patch and close the report issue;
Sorry for the disturb :(

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38581>
_______________________________________

From report at bugs.python.org  Thu Oct 24 08:21:21 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 12:21:21 +0000
Subject: [issue38340] ERROR WHILE BUILDING pyworld for x86_64-linux-gnu-gcc
In-Reply-To: <1569936251.44.0.0859719635079.issue38340@roundup.psfhosted.org>
Message-ID: <1571919681.91.0.301479070608.issue38340@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38340>
_______________________________________

From report at bugs.python.org  Thu Oct 24 09:10:05 2019
From: report at bugs.python.org (Ma Lin)
Date: Thu, 24 Oct 2019 13:10:05 +0000
Subject: [issue38582] Regular match overflow
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571922605.83.0.0725562599621.issue38582@roundup.psfhosted.org>


Change by Ma Lin <malincns at 163.com>:


----------
nosy: +Ma Lin
type: security -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Thu Oct 24 09:27:28 2019
From: report at bugs.python.org (Charalampos Stratakis)
Date: Thu, 24 Oct 2019 13:27:28 +0000
Subject: [issue38576] CVE-2019-18348: CRLF injection via the host part of the
 url passed to urlopen()
In-Reply-To: <1571903478.88.0.753943817426.issue38576@roundup.psfhosted.org>
Message-ID: <1571923648.86.0.214928093774.issue38576@roundup.psfhosted.org>


Change by Charalampos Stratakis <cstratak at redhat.com>:


----------
nosy: +cstratak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38576>
_______________________________________

From report at bugs.python.org  Thu Oct 24 09:32:52 2019
From: report at bugs.python.org (Ma Lin)
Date: Thu, 24 Oct 2019 13:32:52 +0000
Subject: [issue38582] Regular match overflow
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571923972.79.0.67132790957.issue38582@roundup.psfhosted.org>


Ma Lin <malincns at 163.com> added the comment:

An simpler reproduce code:

```
import re

NUM = 99

# items = [ '(001)', '(002)', '(003)', ..., '(NUM)']
items = [r'(%03d)' % i for i in range(1, 1+NUM)]
pattern = '|'.join(items)

# repl = '\1\2\3...\NUM'
temp = ('\\' + str(i) for i in range(1, 1+NUM))
repl = ''.join(temp)

text = re.sub(pattern, repl, '(001)')
print(text)

# if NUM == 99
# output: (001)
# if NUM == 100
# output: (001@)
# if NUM == 101
# output: (001 at A)
```

----------
components: +Regular Expressions
nosy: +ezio.melotti, mrabarnett

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Thu Oct 24 09:49:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 13:49:20 +0000
Subject: [issue38581] Crash on distutils/util.py when header variable isn't a
 string
In-Reply-To: <1571916013.0.0.277609072879.issue38581@roundup.psfhosted.org>
Message-ID: <1571924960.01.0.976977812358.issue38581@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I'm not sure of the status of bzr. Is it still maintained? It sounds like Breezy is the new upstream.

I don't think that it's worth it to bother with modifying distutils. Especially because it will take weeks or months until your system will get the fix.

I close the issue as rejected.

----------
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38581>
_______________________________________

From report at bugs.python.org  Thu Oct 24 10:19:43 2019
From: report at bugs.python.org (Ma Lin)
Date: Thu, 24 Oct 2019 14:19:43 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571926783.42.0.825365519688.issue38582@roundup.psfhosted.org>


Ma Lin <malincns at 163.com> added the comment:

Backreference number in replace string can't >= 100
https://github.com/python/cpython/blob/v3.8.0/Lib/sre_parse.py#L1022-L1036

If none take this, I will try to fix this issue tomorrow.

----------
nosy: +serhiy.storchaka
title: Regular match overflow -> re: backreference number in replace string can't >= 100
versions: +Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Thu Oct 24 10:32:03 2019
From: report at bugs.python.org (Mo)
Date: Thu, 24 Oct 2019 14:32:03 +0000
Subject: [issue38583] The activate script in Windows is not correct for venvs
 created in git-bash
Message-ID: <1571927523.33.0.935819222823.issue38583@roundup.psfhosted.org>


New submission from Mo <moabrahams at dashavoo.com>:

When creating a virtual environment on Windows from git-bash (using python -m venv), VIRTUAL_ENV in the activate script is set using a windows style path (C:\some\path) instead of the bash style (/c/some/path).

This means the system python and pip get used, despite the user thinking they are working in a venv after sourcing activate.

As activate is a bash script, the paths in it should always be in the bash style, regardless of platform.

This is described in a stack overflow issue here: https://stackoverflow.com/questions/57758841/windows-virtualenv-created-via-gitbash-using-system-python

I have confirmed the behaviour in 3.7.3, 3.7.4, 3.7.5 and 3.8.0.

----------
components: Windows
messages: 355333
nosy: Mo, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: The activate script in Windows is not correct for venvs created in git-bash
type: behavior
versions: Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38583>
_______________________________________

From report at bugs.python.org  Thu Oct 24 10:34:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 14:34:07 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571927647.84.0.976540891114.issue20443@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Please revert.

Ok ok, I will revert my change, but only on sys.argv[0].


> A getcwd() call doesn't even have to succeed.  A single file python program should still be able to run in that environment rather than fail to start.

The current implementation leaves a path unchanged if it fails to make it absolute:

config_run_filename_abspath:

    wchar_t *abs_filename;
    if (_Py_abspath(config->run_filename, &abs_filename) < 0) {
        /* failed to get the absolute path of the command line filename:
           ignore the error, keep the relative path */
        return _PyStatus_OK();
    }
    if (abs_filename == NULL) {
        return _PyStatus_NO_MEMORY();
    }

    PyMem_RawFree(config->run_filename);
    config->run_filename = abs_filename;

with:

/* Get an absolute path.
   On error (ex: fail to get the current directory), return -1.
   On memory allocation failure, set *abspath_p to NULL and return 0.
   On success, return a newly allocated to *abspath_p to and return 0.
   The string must be freed by PyMem_RawFree(). */
int _Py_abspath(const wchar_t *path, wchar_t **abspath_p);

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Thu Oct 24 10:38:54 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 14:38:54 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571927934.11.0.43632159832.issue20443@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> To help address the original report filing issue, we could add a notion of .co_cwd to code objects for use in resolving co_filename.  Allow it to be '' if getcwd failed at source load time.  Code could check if co_cwd exists and join it with the co_filename.  Also let co_cwd remain empty when there is no valid co_filename for the code.

Do you mean that co_filename attribute of code objects must remain relative?


> Preaching: Code that calls os.chdir() is always a potential problem as it alters process global state.  That call is best avoided as modifying globals is impolite.

I thought that calling os.chdir("/") is a good practice when launching a program as a daemon. And thne call os.fork() twice to detach the process from its parent and run it in background.

I commonly use os.chdir() in my programs for various reasons. A classical use case is to mimick a shell script doing something like (cd $DIRECTORY; command): temporary change the current directory.

cwd parameter of subprocess.Popen helps to avoid changing the currently directory, but sometimes subprocess is not used at all.

Maybe avoiding os.chdir() is a good practice, but it's hard to prevent users to call it. I don't see how os.chdir() is bad by design. I'm not sure that it's really useful to debate this neither :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Thu Oct 24 10:40:54 2019
From: report at bugs.python.org (Lucas Cimon)
Date: Thu, 24 Oct 2019 14:40:54 +0000
Subject: [issue38584] argparse: Specifying a whitespace-only help message to a
 positional arg triggers an IndexError when displaying --help
Message-ID: <1571928054.48.0.618310381662.issue38584@roundup.psfhosted.org>


New submission from Lucas Cimon <lucas.cimon at gmail.com>:

The test I am going to add to test_argparse.py:

    def test_whitespace_help(self):
        parser = self._get_parser()
        parser.add_argument(
            '--foo2', action='store_true', help=' ')
        parser.add_argument(
            'bar2', type=float, help=' ')
        parser.format_help()  # raises an IndexError

----------
components: Library (Lib)
messages: 355336
nosy: Lucas Cimon
priority: normal
severity: normal
status: open
title: argparse: Specifying a whitespace-only help message to a positional arg triggers an IndexError when displaying --help
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38584>
_______________________________________

From report at bugs.python.org  Thu Oct 24 10:44:04 2019
From: report at bugs.python.org (Lucas Cimon)
Date: Thu, 24 Oct 2019 14:44:04 +0000
Subject: [issue38584] argparse: Specifying a whitespace-only help message to a
 positional arg triggers an IndexError when displaying --help
In-Reply-To: <1571928054.48.0.618310381662.issue38584@roundup.psfhosted.org>
Message-ID: <1571928244.09.0.886141916378.issue38584@roundup.psfhosted.org>


Change by Lucas Cimon <lucas.cimon at gmail.com>:


----------
keywords: +patch
pull_requests: +16448
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16917

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38584>
_______________________________________

From report at bugs.python.org  Thu Oct 24 10:45:42 2019
From: report at bugs.python.org (Avi Kelman)
Date: Thu, 24 Oct 2019 14:45:42 +0000
Subject: [issue38585] defusedexpat not supported past python 3.3/3.4
Message-ID: <1571928342.44.0.0364587849841.issue38585@roundup.psfhosted.org>


New submission from Avi Kelman <avikelman at d3b.center>:

https://docs.python.org/3/library/xml.html continues to recommend defusedexpat, but that package won't install for any Python versions after 3.4 because the package isn't being maintained. https://bitbucket.org/tiran/defusedexpat/src/default/ linked from https://pypi.org/project/defusedexpat/ stops at 3.3. https://github.com/tiran/defusedexpat stops at 3.4.

If the package doesn't actually work for newer Pythons, the recommendation should be removed from official documentation.

----------
assignee: docs at python
components: Documentation
messages: 355337
nosy: Avi Kelman, docs at python
priority: normal
severity: normal
status: open
title: defusedexpat not supported past python 3.3/3.4
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38585>
_______________________________________

From report at bugs.python.org  Thu Oct 24 10:47:14 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 14:47:14 +0000
Subject: [issue38584] argparse: Specifying a whitespace-only help message to a
 positional arg triggers an IndexError when displaying --help
In-Reply-To: <1571928054.48.0.618310381662.issue38584@roundup.psfhosted.org>
Message-ID: <1571928434.26.0.720020667678.issue38584@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +paul.j3, rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38584>
_______________________________________

From report at bugs.python.org  Thu Oct 24 10:48:41 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2019 14:48:41 +0000
Subject: [issue38585] defusedexpat not supported past python 3.3/3.4
In-Reply-To: <1571928342.44.0.0364587849841.issue38585@roundup.psfhosted.org>
Message-ID: <1571928521.48.0.733792128851.issue38585@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy: +christian.heimes

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38585>
_______________________________________

From report at bugs.python.org  Thu Oct 24 11:16:03 2019
From: report at bugs.python.org (Lucas Cimon)
Date: Thu, 24 Oct 2019 15:16:03 +0000
Subject: [issue38586] logging: handlers names are not set when using fileConfig
Message-ID: <1571930163.44.0.759260613385.issue38586@roundup.psfhosted.org>


New submission from Lucas Cimon <lucas.cimon at gmail.com>:

The logging.Handler .name property is not set when the logging configuration is loaded with logging.fileConfig

----------
components: Library (Lib)
messages: 355338
nosy: Lucas Cimon
priority: normal
severity: normal
status: open
title: logging: handlers names are not set when using fileConfig
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38586>
_______________________________________

From report at bugs.python.org  Thu Oct 24 11:21:16 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 24 Oct 2019 15:21:16 +0000
Subject: [issue38586] logging: handlers names are not set when using fileConfig
In-Reply-To: <1571930163.44.0.759260613385.issue38586@roundup.psfhosted.org>
Message-ID: <1571930476.57.0.226075099903.issue38586@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +vinay.sajip

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38586>
_______________________________________

From report at bugs.python.org  Thu Oct 24 11:29:21 2019
From: report at bugs.python.org (Lucas Cimon)
Date: Thu, 24 Oct 2019 15:29:21 +0000
Subject: [issue38586] logging: handlers names are not set when using fileConfig
In-Reply-To: <1571930163.44.0.759260613385.issue38586@roundup.psfhosted.org>
Message-ID: <1571930961.47.0.487277808903.issue38586@roundup.psfhosted.org>


Change by Lucas Cimon <lucas.cimon at gmail.com>:


----------
keywords: +patch
pull_requests: +16450
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16918

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38586>
_______________________________________

From report at bugs.python.org  Thu Oct 24 12:51:34 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 16:51:34 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571935894.52.0.634519589212.issue20443@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

I think sys.argv[0] is the important one as program logic often tends to use that as an input.

I'm honestly unsure of if this will be as much of a problem for .co_filename or sys.path[0].

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Thu Oct 24 12:53:02 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 16:53:02 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571935982.34.0.503111790904.issue20443@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

(read that as: feel free to keep the behavior for co_filename and path[0] and lets see what happens :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Thu Oct 24 12:54:14 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Thu, 24 Oct 2019 16:54:14 +0000
Subject: [issue20443] __code__. co_filename should always be an absolute path
In-Reply-To: <1391048115.83.0.412883752117.issue20443@psf.upfronthosting.co.za>
Message-ID: <1571936054.31.0.545479299651.issue20443@roundup.psfhosted.org>


Change by Yury Selivanov <yselivanov at gmail.com>:


----------
nosy:  -yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20443>
_______________________________________

From report at bugs.python.org  Thu Oct 24 12:54:13 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 16:54:13 +0000
Subject: [issue33348] lib2to3 doesn't parse f(*[] or [])
In-Reply-To: <1524573727.4.0.682650639539.issue33348@psf.upfronthosting.co.za>
Message-ID: <1571936053.88.0.0819676866967.issue33348@roundup.psfhosted.org>


Gregory P. Smith <greg at krypto.org> added the comment:

I'm marking this fixed, technically it still exists in 2.7.  it'll be up to someone who cares about making a change to 2.7 to make a PR to go in there for the final release.  It has existed so long, I doubt it matters there.

----------
resolution:  -> fixed
stage: patch review -> commit review
status: open -> closed
versions:  -Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33348>
_______________________________________

From report at bugs.python.org  Thu Oct 24 12:55:03 2019
From: report at bugs.python.org (Caleb Donovick)
Date: Thu, 24 Oct 2019 16:55:03 +0000
Subject: [issue35113] inspect.getsource returns incorrect source for classes
 when class definition is part of multiline strings
In-Reply-To: <1540902777.26.0.788709270274.issue35113@psf.upfronthosting.co.za>
Message-ID: <1571936103.76.0.951177422323.issue35113@roundup.psfhosted.org>


Change by Caleb Donovick <donovick at cs.stanford.edu>:


----------
nosy: +donovick

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35113>
_______________________________________

From report at bugs.python.org  Thu Oct 24 12:55:12 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 16:55:12 +0000
Subject: [issue38576] CVE-2019-18348: CRLF injection via the host part of the
 url passed to urlopen()
In-Reply-To: <1571903478.88.0.753943817426.issue38576@roundup.psfhosted.org>
Message-ID: <1571936112.81.0.263928140976.issue38576@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
nosy: +gregory.p.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38576>
_______________________________________

From report at bugs.python.org  Thu Oct 24 12:55:24 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Thu, 24 Oct 2019 16:55:24 +0000
Subject: [issue38576] CVE-2019-18348: CRLF injection via the host part of the
 url passed to urlopen()
In-Reply-To: <1571903478.88.0.753943817426.issue38576@roundup.psfhosted.org>
Message-ID: <1571936124.68.0.96667880735.issue38576@roundup.psfhosted.org>


Change by Gregory P. Smith <greg at krypto.org>:


----------
stage:  -> needs patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38576>
_______________________________________

From report at bugs.python.org  Thu Oct 24 13:15:15 2019
From: report at bugs.python.org (paul j3)
Date: Thu, 24 Oct 2019 17:15:15 +0000
Subject: [issue38584] argparse: Specifying a whitespace-only help message to a
 positional arg triggers an IndexError when displaying --help
In-Reply-To: <1571928054.48.0.618310381662.issue38584@roundup.psfhosted.org>
Message-ID: <1571937315.09.0.306292344035.issue38584@roundup.psfhosted.org>


paul j3 <ajipanca at gmail.com> added the comment:

So the error occurs in HelpFormatter._format_action when 'help_lines' is an empty list:

        ....
        if action.help:
            help_text = self._expand_help(action)
            help_lines = self._split_lines(help_text, help_width)
     >>     parts.append('%*s%s\n' % (indent_first, '', help_lines[0]))
            for line in help_lines[1:]:
                parts.append('%*s%s\n' % (help_position, '', line))

It occurs with both optionals and positionals.  It does not occur with argparse.RawTextHelpFormatter.

The default _split_lines:

    def _split_lines(self, text, width):
        text = self._whitespace_matcher.sub(' ', text).strip()
        return _textwrap.wrap(text, width)

Because of the 'strip' it treats a help with space as empty

In [27]: f._split_lines('',40)                                                  
Out[27]: []
In [28]: f._split_lines('test',40)                                              
Out[28]: ['test']
In [29]: f._split_lines(' ',40)                                                 
Out[29]: []

None or '' don't trigger this because they are weeded out by the 'if action.help:' line.

Maybe the change proposed here, to skip the problem line if 'help_lines' is empty is the right one.  Assuming a list is non-empty can be dangerous.  But it would be wise to test the patch with the alternative formatters like the RawText.  

It may also be worth thinking about correcting the issue in _split_lines(), which is shorter.  The only difference in  RawTextHelpFormatter is in this method.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38584>
_______________________________________

From report at bugs.python.org  Thu Oct 24 13:15:46 2019
From: report at bugs.python.org (Matthew Barnett)
Date: Thu, 24 Oct 2019 17:15:46 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571937346.84.0.181324807427.issue38582@roundup.psfhosted.org>


Matthew Barnett <python at mrabarnett.plus.com> added the comment:

A numeric escape of 3 digits is an octal (base 8) escape; the octal escape "\100" gives the same character as the hexadecimal escape "\x40".

In a replacement template, you can use "\g<100>" if you want group 100 because \g<...> accepts both numeric and named group references.

However, \g<...> is not accepted in a pattern.

(By the way, in the "regex" module I added support for it in a pattern too.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Thu Oct 24 13:49:08 2019
From: report at bugs.python.org (Steve Dower)
Date: Thu, 24 Oct 2019 17:49:08 +0000
Subject: [issue38092] environment variables not passed correctly using new
 virtualenv launching in windows and python3.7+
In-Reply-To: <1568122359.92.0.800539114246.issue38092@roundup.psfhosted.org>
Message-ID: <1571939348.53.0.479198345478.issue38092@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

You're right, the logic to actually launch _base_executable is in there twice now, and the second one (that never gets used) is more important.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38092>
_______________________________________

From report at bugs.python.org  Thu Oct 24 14:21:36 2019
From: report at bugs.python.org (Ammar Askar)
Date: Thu, 24 Oct 2019 18:21:36 +0000
Subject: [issue38558] Data Structures documentation out of sync with new
 Walrus operator
In-Reply-To: <1571776032.37.0.709698360286.issue38558@roundup.psfhosted.org>
Message-ID: <1571941296.22.0.248299234527.issue38558@roundup.psfhosted.org>


Change by Ammar Askar <ammar at ammaraskar.com>:


----------
keywords: +patch
pull_requests: +16451
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16919

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38558>
_______________________________________

From report at bugs.python.org  Thu Oct 24 14:26:07 2019
From: report at bugs.python.org (Mike Driscoll)
Date: Thu, 24 Oct 2019 18:26:07 +0000
Subject: [issue38587] __set_name__ missing from descriptor howto documentation
Message-ID: <1571941567.01.0.700775981923.issue38587@roundup.psfhosted.org>


New submission from Mike Driscoll <kyosohma at gmail.com>:

I noticed that __set_name__ is not mentioned in https://docs.python.org/3/howto/descriptor.html even though it was added in https://www.python.org/dev/peps/pep-0487/ and mentioned here https://docs.python.org/3/whatsnew/3.6.html#pep-487-descriptor-protocol-enhancements

----------
assignee: docs at python
components: Documentation
messages: 355345
nosy: Mike Driscoll, docs at python
priority: normal
severity: normal
status: open
title: __set_name__ missing from descriptor howto documentation
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38587>
_______________________________________

From report at bugs.python.org  Thu Oct 24 14:32:25 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Thu, 24 Oct 2019 18:32:25 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571941945.33.0.80152696577.issue38582@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

Is this actually needed? I can't remember ever needing more than 4 (in a pattern). I find it very hard to believe someone might actually have such a regex with more than a hundred backreferences. Probably it's just a misguided attempt to parse a nested structure with a regex.

----------
nosy: +veky

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Thu Oct 24 14:41:30 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 24 Oct 2019 18:41:30 +0000
Subject: [issue38587] __set_name__ missing from descriptor howto documentation
In-Reply-To: <1571941567.01.0.700775981923.issue38587@roundup.psfhosted.org>
Message-ID: <1571942490.21.0.276534643904.issue38587@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
nosy: +ncoghlan
versions: +Python 3.9 -Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38587>
_______________________________________

From report at bugs.python.org  Thu Oct 24 15:16:18 2019
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 24 Oct 2019 19:16:18 +0000
Subject: [issue38569] Unknown distribution option: 'license_files'
In-Reply-To: <1571860665.03.0.77407877223.issue38569@roundup.psfhosted.org>
Message-ID: <1571944578.01.0.108398184612.issue38569@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

Why do you think the warning can be removed? Is it documented as supported in distutils? If setuptools supports that argument but not distutils then that would be a bug against them.

----------
nosy: +brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38569>
_______________________________________

From report at bugs.python.org  Thu Oct 24 16:28:19 2019
From: report at bugs.python.org (paul j3)
Date: Thu, 24 Oct 2019 20:28:19 +0000
Subject: [issue38438] argparse "usage" overly-complex with nargs="*"
In-Reply-To: <1570739079.02.0.395133592841.issue38438@roundup.psfhosted.org>
Message-ID: <1571948899.51.0.699116564897.issue38438@roundup.psfhosted.org>


Change by paul j3 <ajipanca at gmail.com>:


----------
nosy: +paul.j3

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38438>
_______________________________________

From report at bugs.python.org  Thu Oct 24 18:22:57 2019
From: report at bugs.python.org (Lucas Cimon)
Date: Thu, 24 Oct 2019 22:22:57 +0000
Subject: [issue38584] argparse: Specifying a whitespace-only help message to a
 positional arg triggers an IndexError when displaying --help
In-Reply-To: <1571928054.48.0.618310381662.issue38584@roundup.psfhosted.org>
Message-ID: <1571955777.41.0.59643766396.issue38584@roundup.psfhosted.org>


Lucas Cimon <lucas.cimon at gmail.com> added the comment:

Thanks for the feedbacks paul.j3 !

I totally agree it would be best to test all formatter classes.
I modified the new test to do so.

I think I should probably place this test somewhere else in test_argparse.py, but I'm having trouble figuring out where exactly... I just updated the PR and moved the new test to the TestOptionalsHelpVersionActions class.

About the best fix, I think a fix to _split_lines() would be more complex. It needs to return a list, so we would make it return [''] in that case ? That would be a bit strange.

What do you think ? :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38584>
_______________________________________

From report at bugs.python.org  Thu Oct 24 20:12:05 2019
From: report at bugs.python.org (paul j3)
Date: Fri, 25 Oct 2019 00:12:05 +0000
Subject: [issue38584] argparse: Specifying a whitespace-only help message to a
 positional arg triggers an IndexError when displaying --help
In-Reply-To: <1571928054.48.0.618310381662.issue38584@roundup.psfhosted.org>
Message-ID: <1571962325.39.0.838545454892.issue38584@roundup.psfhosted.org>


paul j3 <ajipanca at gmail.com> added the comment:

Just today on SO someone found a similar bug in the help format with metavars, that involved an unpacking the expected only one value, but got 2.

https://stackoverflow.com/questions/58541460/tuple-metavar-value-for-positional-argument-with-nargs-1

This had be raise years ago, as https://bugs.python.org/issue14074

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38584>
_______________________________________

From report at bugs.python.org  Thu Oct 24 21:59:15 2019
From: report at bugs.python.org (veaba)
Date: Fri, 25 Oct 2019 01:59:15 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571968755.98.0.163924451061.issue38582@roundup.psfhosted.org>


veaba <908662421 at qq.com> added the comment:

?????????????https://github.com/veaba/tensorflow-docs/blob/master/scripts/spider_tensorflow_docs.py#L39-L56???????????????????????python??????

????????????HTML tag ??????markdown???<code> ?????????`??????????????????\\* ?????

????????????????????????


??????????????????????????????????????????????

????????????????????????????????????
This is from a project I actually worked on (https://github.com/veaba/tensorflow-docs/blob/master/scripts/spider_tensorflow_docs.py#L39-L56). Of course, this method is not correct. It's just an attempt to learn python.



The project steps are as follows: extract the text according to HTML tag and change it to markdown format. The < code > label needs to be surrounded by the symbol "`", and then the matching characters are replaced by \ \ * in the loop.



So, as you can see, I found such a regular overflow error.




It would be nice for me to be able to let go of the infinite number of backslash substitutions. Of course, if I really don't need it, I'll try something else.

----------
hgrepos: +385

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Thu Oct 24 23:55:00 2019
From: report at bugs.python.org (Batuhan)
Date: Fri, 25 Oct 2019 03:55:00 +0000
Subject: [issue35448] ConfigParser .read() - handling of nonexistent files
In-Reply-To: <1544373330.85.0.788709270274.issue35448@psf.upfronthosting.co.za>
Message-ID: <1571975700.26.0.166739744031.issue35448@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


----------
keywords: +patch
pull_requests: +16452
stage: test needed -> patch review
pull_request: https://github.com/python/cpython/pull/16920

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35448>
_______________________________________

From report at bugs.python.org  Thu Oct 24 23:55:11 2019
From: report at bugs.python.org (Batuhan)
Date: Fri, 25 Oct 2019 03:55:11 +0000
Subject: [issue35448] ConfigParser .read() - handling of nonexistent files
In-Reply-To: <1544373330.85.0.788709270274.issue35448@psf.upfronthosting.co.za>
Message-ID: <1571975711.18.0.765520198642.issue35448@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


----------
versions: +Python 3.9 -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35448>
_______________________________________

From report at bugs.python.org  Fri Oct 25 00:36:52 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 25 Oct 2019 04:36:52 +0000
Subject: [issue38587] __set_name__ missing from descriptor howto documentation
In-Reply-To: <1571941567.01.0.700775981923.issue38587@roundup.psfhosted.org>
Message-ID: <1571978212.86.0.571386088024.issue38587@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Thanks for the note.  I've already go this in my pending edits.

----------
assignee: docs at python -> rhettinger
nosy: +rhettinger
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Descriptors HowTo doesn't mention __set_name__

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38587>
_______________________________________

From report at bugs.python.org  Fri Oct 25 01:19:34 2019
From: report at bugs.python.org (Ma Lin)
Date: Fri, 25 Oct 2019 05:19:34 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571980774.71.0.224653759701.issue38582@roundup.psfhosted.org>


Ma Lin <malincns at 163.com> added the comment:

@veaba 
Post only in English is fine.

> Is this actually needed?
Maybe very very few people dynamically generate some large patterns.

> However, \g<...> is not accepted in a pattern.
> in the "regex" module I added support for it in a pattern too.
Yes, backreference number in pattern also can't >= 100
Support \g<...> in pattern is a good idea.

If fix this issue, may produce backward compatibility issue: the parser will confuse backreference numbers and octal escape numbers.
Maybe can clarify the limit (<=99) in the document is enough.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Fri Oct 25 01:46:28 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Fri, 25 Oct 2019 05:46:28 +0000
Subject: [issue38519] Internal include files missing on Windows
In-Reply-To: <1571423438.26.0.118785392888.issue38519@roundup.psfhosted.org>
Message-ID: <1571982388.22.0.581266757334.issue38519@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
keywords: +patch
pull_requests: +16453
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16921

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38519>
_______________________________________

From report at bugs.python.org  Fri Oct 25 01:50:54 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Fri, 25 Oct 2019 05:50:54 +0000
Subject: [issue38519] Internal include files missing on Windows
In-Reply-To: <1571423438.26.0.118785392888.issue38519@roundup.psfhosted.org>
Message-ID: <1571982654.44.0.803061775981.issue38519@roundup.psfhosted.org>


Zackery Spytz <zspytz at gmail.com> added the comment:

Hi, Steve. I've created a PR for this.

----------
nosy: +ZackerySpytz

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38519>
_______________________________________

From report at bugs.python.org  Fri Oct 25 02:51:17 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Fri, 25 Oct 2019 06:51:17 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571986277.71.0.0947007010349.issue38582@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

I have no problem with long regexes. But those are not only long, those must be _deeply nested_ regexes, where simply 100 is an arbitrary limit. I'm quite sure if you really need depth 100, you must also need a dynamic depth of nesting, which you cannot really achieve with regexes.

Yes, if there is a will to change this, supporting \g would be a way to go.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Fri Oct 25 03:24:01 2019
From: report at bugs.python.org (veaba)
Date: Fri, 25 Oct 2019 07:24:01 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571988241.08.0.12918263297.issue38582@roundup.psfhosted.org>


veaba <908662421 at qq.com> added the comment:

Yes, this is not a good place to use regular expressions.

Using regular expressions?
def actual_re_demo():
    import re
    # This is an indefinite string...
    text = "tf.where(condition, x=None, y=None, name=None) tf.batch_gather ..."

    # Converting fields that need to be matched into regular expressions is also an indefinite string
    pattern_str = re.compile('(tf\\.batch_gather)|(None)|(a1)')

    #I don't know how many, so it's over \ \ 100 \ \ n
    x = re.sub(pattern_str, '`'+'\\1\\2'+'`', text)

    print(x)

    # hope if?tf.Prefix needs to match,The result will be:`tf.xx`?

    # But in fact, it's not just TF. As a prefix, it's a random character, it can be a suffix, it can be other characters.

    #  If more than 100, the result is=>?989???????89????????89????????89????????890123`, name=`None at ABCDEFG89HIJKLMNO89PQRSTUVW89XYZ[\]^_89`abcdefg89hijklmno89pqrstuvw89xyz{|}~8901234567890123456789

    # I noticed in the comment area that it was caused by a confusion of Radix, which seems to be embarrassing.


Use replace to solve it. It looks much better.
def no_need_re():
    text = "tf.where(condition, x=None, y=None, name=None) tf.batch_gather ..."
    pattern_list = ['tf.batch_gather', 'None']
    for item in pattern_list:
        text=text.replace(item, '`'+item+'`')

    print(text)

no_need_re()

Expect to report an error directly if it exceeds the limit, instead of overflowing the character, like this:

989???????89????????89????????89????????890123`, name=`None at ABCDEFG89HIJKLMNO89PQRSTUVW89XYZ[\]^_89`abcdefg89hijklmno89pqrstuvw89xyz{|}~8901234567890123456789

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Fri Oct 25 04:18:19 2019
From: report at bugs.python.org (Mo)
Date: Fri, 25 Oct 2019 08:18:19 +0000
Subject: [issue38583] The activate script in Windows is not correct for venvs
 created in git-bash
In-Reply-To: <1571927523.33.0.935819222823.issue38583@roundup.psfhosted.org>
Message-ID: <1571991499.68.0.815914394277.issue38583@roundup.psfhosted.org>


Mo <moabrahams at dashavoo.com> added the comment:

The issue comes as a result of abspath on line 59 of venv/__init__.py:
        env_dir = os.path.abspath(env_dir)

This returns a Windows-style path, and os.path.abspath returning in this way is *probably* correct, as the OS is Windows, despite trying to forget that by using bash.

It is still my view that the activate script is a bash script, and therefore should only contain paths in that style, but the simple solution to this issue is to change the double quotes around the definition of $VIRTUAL_ENV in the activate script to single quotes. It works. The output of "which python" is a bit odd, but this is clearly a quirk beyond Python's control.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38583>
_______________________________________

From report at bugs.python.org  Fri Oct 25 04:19:05 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 25 Oct 2019 08:19:05 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571991545.73.0.364428421661.issue38582@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I do not believe somebody uses handwritten regular expressions with more than 100 groups. But if you generate regular expression, you can use named groups (?P<g12345>...) (?P=g12345).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Fri Oct 25 04:44:34 2019
From: report at bugs.python.org (veaba)
Date: Fri, 25 Oct 2019 08:44:34 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571993074.54.0.135280392013.issue38582@roundup.psfhosted.org>


veaba <908662421 at qq.com> added the comment:

Aha, it's me. It's the mysterious power from the East. I just learned python.

I've solved my problem. It's a very simple replace replacement, and it's solved in three lines.

I'm trying to solve the problem of inadvertently finding out in the process of translating HTML text into markdown file. The document contains very complex strings, so I do that. Now it seems that the method I used before is a very inappropriate and inappropriate way to implement, which is a mistake.

However, I insist that this regular overflow is still a problem. It doesn't even translate a bunch of meaningless strings without any error.

I didn't find such a bug until I randomly selected and checked 2. K documents. I don't know if it's unlucky or lucky.

Then, I will not participate in the discussion of the remaining high-end issues.

Good luck.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Fri Oct 25 05:32:53 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Fri, 25 Oct 2019 09:32:53 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1571995973.8.0.26044405819.issue38582@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

The documentation clearly says:

> This special sequence can only be used to match one of the first 99 groups. If the first digit of number is 0, or number is 3 octal digits long, it will not be interpreted as a group match, but as the character with octal value number.

Maybe it should also mention Serhiy's technique at that place, something like

"If you need more than 99 groups, you can name them using..."

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Fri Oct 25 07:53:45 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 25 Oct 2019 11:53:45 +0000
Subject: [issue38564] test_asyncio:
 test_run_coroutine_threadsafe_with_timeout() has a race condition
In-Reply-To: <1571841860.24.0.514293762677.issue38564@roundup.psfhosted.org>
Message-ID: <1572004425.61.0.707239222205.issue38564@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

I can confirm Victor's method of reproducing the failure consistently, by using asyncio.sleep(1e-9) within `RunCoroutineThreadsafeTests.add()` instead of the current asyncio.sleep(0.05).

I also experimented with adjusting the sleep time, to figure out the "breaking point" where I could no longer run `./python -m test test_asyncio -m test_run_coroutine_threadsafe_with_timeout -v -F` without failures (within ~10,000 tests). From my results, the lowest reliable value was 0.001. At 1e-4, I was able to consistently reproduce the failure reported above:

FAIL: test_run_coroutine_threadsafe_with_timeout (test.test_asyncio.test_tasks.RunCoroutineThreadsafeTests)
Test coroutine submission from a thread to an event loop
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/aeros/repos/cpython/Lib/test/test_asyncio/test_tasks.py", line 3210, in test_run_coroutine_threadsafe_with_timeout
    self.loop.run_until_complete(future)
AssertionError: TimeoutError not raised

The failure becomes increasingly consistent with lowered time as expected, but at 1e-5 I was able to repeatedly reproduce the failure within 10 iterations of the test. At 1e-4 it took around 3000 iterations before failing (across multiple runs).

----------
nosy: +aeros

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38564>
_______________________________________

From report at bugs.python.org  Fri Oct 25 08:15:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 25 Oct 2019 12:15:57 +0000
Subject: [issue38564] test_asyncio:
 test_run_coroutine_threadsafe_with_timeout() has a race condition
In-Reply-To: <1571841860.24.0.514293762677.issue38564@roundup.psfhosted.org>
Message-ID: <1572005757.14.0.858816817952.issue38564@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

IHMO a test must not depend on time.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38564>
_______________________________________

From report at bugs.python.org  Fri Oct 25 08:27:24 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 25 Oct 2019 12:27:24 +0000
Subject: [issue38323] asyncio: MultiLoopWatcher has a race condition
 (test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x)
In-Reply-To: <1569848255.08.0.155489980043.issue38323@roundup.psfhosted.org>
Message-ID: <1572006444.65.0.306980283201.issue38323@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> I'm able to reproduce the issue locally using the command:
./python -m test test_asyncio --match=test.test_asyncio.test_subprocess.SubprocessMultiLoopWatcherTests.test_close_kill_running -v -F -j20 --timeout=30.0

I was unable to reproduce this locally on OS: Arch Linux 5.3.7 x86_64 and CPU: Intel i5-4460 from the latest commit (heads/master:96b06aefe2) within a reasonable number of tests (~10000). I also tried differing number of jobs, up to 100. What OS were you able to reproduce it locally on using that configuration?

This is of course still an issue since it's still occurring on multiple buildbots intermittently and Victor was able to reproduce it locally, but I was not able to do so on my local setup. This will be significantly harder to debug without a reliable means of reproducing the failure.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38323>
_______________________________________

From report at bugs.python.org  Fri Oct 25 08:30:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 25 Oct 2019 12:30:39 +0000
Subject: [issue38323] asyncio: MultiLoopWatcher has a race condition
 (test_asyncio: test_close_kill_running() hangs on AMD64 RHEL7 Refleaks 3.x)
In-Reply-To: <1569848255.08.0.155489980043.issue38323@roundup.psfhosted.org>
Message-ID: <1572006639.96.0.899607092646.issue38323@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I did my tests on Fedora 30 on my laptop which has 4 cores (8 logical CPUs).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38323>
_______________________________________

From report at bugs.python.org  Fri Oct 25 08:45:24 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 25 Oct 2019 12:45:24 +0000
Subject: [issue35448] ConfigParser .read() - handling of nonexistent files
In-Reply-To: <1544373330.85.0.788709270274.issue35448@psf.upfronthosting.co.za>
Message-ID: <1572007524.24.0.27876767837.issue35448@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I do not think that adding an extra parameter to .read() will solve any problem.

You need to read the documentation of read() to use this feature. You need to change your code, and this will work only in new version of Python, so you will need to support two versions of the code in any way. If you change your code, it is easier to make it using read_file(), this way is compatible with old Python versions, and you can use it today.

If you do not read the documentation and do not change your code this feature cannot help you. Changing the default behavior will break existing code.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35448>
_______________________________________

From report at bugs.python.org  Fri Oct 25 08:53:20 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 25 Oct 2019 12:53:20 +0000
Subject: [issue38564] test_asyncio:
 test_run_coroutine_threadsafe_with_timeout() has a race condition
In-Reply-To: <1571841860.24.0.514293762677.issue38564@roundup.psfhosted.org>
Message-ID: <1572008000.02.0.096696501474.issue38564@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> IHMO a test must not depend on time.

I would agree, the tests should optimally not depend on time. My above comment was primarily to confirm that the failure was able to be consistently reproduced, along with the minimum conditions to do so.

Yury had been the one to change it to "asyncio.sleep(0.05)" from the previous "asyncio.sleep(1)" in the following commit: https://github.com/python/cpython/commit/abe9625eeb71e40f042ccfccfe6a4489a6dcdf35 (Nov 13, 2015).

Perhaps he might have some insight or ideas as to how we could improve the test to use a more reliable means of synchronization that has been implemented since that change was made. I'll add him to the nosy list.

----------
nosy: +yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38564>
_______________________________________

From report at bugs.python.org  Fri Oct 25 09:25:50 2019
From: report at bugs.python.org (LCatro)
Date: Fri, 25 Oct 2019 13:25:50 +0000
Subject: [issue38588] Use-after-free in dict/list
Message-ID: <1572009950.92.0.0819194467929.issue38588@roundup.psfhosted.org>


New submission from LCatro <m4i1f0rt3st at sina.cn>:

Code :

The varanit bval forget call Py_INCREF to add reference in dict_equal()

    b->ma_keys->dk_lookup(b, key, ep->me_hash, &bval);  <--- ...
    if (bval == NULL) {
        Py_DECREF(key);
        Py_DECREF(aval);
        if (PyErr_Occurred())
            return -1;
        return 0;
    }
    cmp = PyObject_RichCompareBool(aval, bval, Py_EQ);


PoC 1 :

class poc() :
    def __eq__(self,other) :
        dict2.clear()
        return NotImplemented

dict1 = {0:poc()}
dict2 = {0:set()}
dict1 == dict2   ##  dict_equal() -> PyObject_RichCompareBool


Crash Detail :


(gdb) run ../python_poc_info/dict_poc_1.py 
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/fuzzing/Desktop/Python-3.8.0/python ../python_poc_info/dict_poc_1.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x000000000046e445 in do_richcompare (v=v at entry=0x7ffff7e767d0, w=w at entry=0x7ffff6dd88c0, op=op at entry=2)
    at Objects/object.c:725
725	    if (!checked_reverse_op && (f = w->ob_type->tp_richcompare) != NULL) {


======

Code :

The varanit wl->ob_item[i] forget call Py_INCREF to add reference in list_richcompare()

    for (i = 0; i < Py_SIZE(vl) && i < Py_SIZE(wl); i++) {
        int k = PyObject_RichCompareBool(vl->ob_item[i],
                                         wl->ob_item[i], Py_EQ);  <---


PoC 2 :

class poc() :
    def __eq__(self,other) :
        list1.clear()
        return NotImplemented


list1 = [poc()]
list2 = [1]
list1 == list2  #  list_richcompare() -> PyObject_RichCompareBool


Crash Detail :


(gdb) run ../python_poc_info/list_poc_1.py 
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/fuzzing/Desktop/Python-3.8.0/python ../python_poc_info/list_poc_1.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x000000000044bd07 in long_richcompare (self=0x961200 <small_ints+192>, other=0x7ffff7e767d0, op=2)
    at Objects/longobject.c:3083
3083	    CHECK_BINOP(self, other);


======

Code :

The varanit PyList_GET_ITEM(a, i) forget call Py_INCREF to add reference in list_contains()

list_contains(PyListObject *a, PyObject *el)
{
    Py_ssize_t i;
    int cmp;

    for (i = 0, cmp = 0 ; cmp == 0 && i < Py_SIZE(a); ++i)
        cmp = PyObject_RichCompareBool(el, PyList_GET_ITEM(a, i),
                                           Py_EQ);   <----


PoC 3 :

class poc() :
    def __eq__(self,other) :
        list1.clear()
        return NotImplemented

list1 = [ set() ]
poc() in list1  #  list_contains() -> PyObject_RichCompareBool


Crash Detail :


(gdb) run ../python_poc_info/list_poc_2.py 
Starting program: /home/fuzzing/Desktop/Python-3.8.0/python ../python_poc_info/list_poc_2.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x000000000046e445 in do_richcompare (v=v at entry=0x7ffff7e766e0, w=w at entry=0x7ffff6dd88c0, op=op at entry=2)
    at Objects/object.c:725
725	    if (!checked_reverse_op && (f = w->ob_type->tp_richcompare) != NULL) {

----------
messages: 355366
nosy: LCatro, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Use-after-free in dict/list
type: security
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38588>
_______________________________________

From report at bugs.python.org  Fri Oct 25 09:29:51 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 25 Oct 2019 13:29:51 +0000
Subject: [issue38588] Use-after-free in dict/list
In-Reply-To: <1572009950.92.0.0819194467929.issue38588@roundup.psfhosted.org>
Message-ID: <1572010191.95.0.199854842489.issue38588@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Thank you for your investigation LCatro! Do you mind to create a pull request?

----------
components: +Interpreter Core
type: security -> crash
versions: +Python 2.7, Python 3.7, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38588>
_______________________________________

From report at bugs.python.org  Fri Oct 25 09:33:52 2019
From: report at bugs.python.org (Clement Rouault)
Date: Fri, 25 Oct 2019 13:33:52 +0000
Subject: [issue29270] super call in ctypes sub-class fails in 3.6
In-Reply-To: <1484345422.14.0.967631121608.issue29270@psf.upfronthosting.co.za>
Message-ID: <1572010432.76.0.29332754505.issue29270@roundup.psfhosted.org>


Clement Rouault <python at hakril.net> added the comment:

Hello,

I have a Python2 project that relies heavily on ctypes and I cannot migrate this project to Python3 due to this bug. (I target 3.6)
I have some experience with CPython and submitting patchs and I would like to know what I can do to help moving this issue forward.

Thanks !

----------
nosy: +hakril

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29270>
_______________________________________

From report at bugs.python.org  Fri Oct 25 09:36:19 2019
From: report at bugs.python.org (Y3Kv Bv)
Date: Fri, 25 Oct 2019 13:36:19 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
Message-ID: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>


New submission from Y3Kv Bv <yk3b.bw.ggxwkimobz at gmail.com>:

Since Python 3.7 I'm getting broken shortcut to Python 3.x Manuals:
the installer doesn't seem to check for correct path to hh.exe; sets "C" as drive letter. (Yet path to python3xx.chm starts with correct drive letter.)

----------
messages: 355369
nosy: Y3Kv Bv
priority: normal
severity: normal
status: open
title: Bad target address assigned in Python Manuals shortcut on Python installation
versions: Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Fri Oct 25 09:50:46 2019
From: report at bugs.python.org (pmp-p)
Date: Fri, 25 Oct 2019 13:50:46 +0000
Subject: [issue28833] cross compilation of third-party extension modules
In-Reply-To: <1480431100.4.0.611325572748.issue28833@psf.upfronthosting.co.za>
Message-ID: <1572011446.98.0.549379497039.issue28833@roundup.psfhosted.org>


Change by pmp-p <pmpp.pub at gmail.com>:


----------
nosy: +pmpp

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28833>
_______________________________________

From report at bugs.python.org  Fri Oct 25 09:52:25 2019
From: report at bugs.python.org (Charles Coulombe)
Date: Fri, 25 Oct 2019 13:52:25 +0000
Subject: [issue38286] tarfile forgets set sgid when targetpath has it
In-Reply-To: <1569507139.8.0.49605570029.issue38286@roundup.psfhosted.org>
Message-ID: <1572011545.35.0.945569507073.issue38286@roundup.psfhosted.org>


Change by Charles Coulombe <charles.coulombe at calculquebec.ca>:


Removed file: https://bugs.python.org/file48626/tarfile_sgid.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38286>
_______________________________________

From report at bugs.python.org  Fri Oct 25 09:52:47 2019
From: report at bugs.python.org (Charles Coulombe)
Date: Fri, 25 Oct 2019 13:52:47 +0000
Subject: [issue38286] tarfile forgets set sgid when targetpath has it
In-Reply-To: <1569507139.8.0.49605570029.issue38286@roundup.psfhosted.org>
Message-ID: <1572011567.31.0.0455398070884.issue38286@roundup.psfhosted.org>


Change by Charles Coulombe <charles.coulombe at calculquebec.ca>:


Added file: https://bugs.python.org/file48678/tarfile_sgid.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38286>
_______________________________________

From report at bugs.python.org  Fri Oct 25 10:49:19 2019
From: report at bugs.python.org (Jeong-Min Lee)
Date: Fri, 25 Oct 2019 14:49:19 +0000
Subject: [issue38529] Python 3.8 improperly warns about closing properly
 closed streams
In-Reply-To: <1571510429.0.0.996597968813.issue38529@roundup.psfhosted.org>
Message-ID: <1572014959.11.0.217521170321.issue38529@roundup.psfhosted.org>


Change by Jeong-Min Lee <falsetru at gmail.com>:


----------
nosy: +falsetru

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38529>
_______________________________________

From report at bugs.python.org  Fri Oct 25 14:13:04 2019
From: report at bugs.python.org (Tim Sanders)
Date: Fri, 25 Oct 2019 18:13:04 +0000
Subject: [issue38590] argparse unexpected behavior with argument group inside
 mutually exclusive group
Message-ID: <1572027184.79.0.23480523249.issue38590@roundup.psfhosted.org>


New submission from Tim Sanders <gollum9999 at gmail.com>:

argparse allows adding argument_groups inside of mutually_exclusive_groups, but the behavior is unintuitive and a bit buggy.

Demo:


import argparse

parser = argparse.ArgumentParser()
single_group = parser.add_argument_group(title='single_group')
single_group.add_argument('--a', action='store_true')

mutex_group = parser.add_mutually_exclusive_group()
mutex_group.add_argument('--b', action='store_true')

nested_group = mutex_group.add_argument_group(title='nested_group')
nested_group.add_argument('--c', action='store_true')
nested_group.add_argument('--d', action='store_true')

parser.print_help()
print(parser.parse_args())


Example output:


$ ~/test_args.py --a --b --c --d
usage: test_args.py [-h] [--a] [--b] [--c] [--d]

optional arguments:
  -h, --help  show this help message and exit
  --b

single_group:
  --a
Namespace(a=True, b=True, c=True, d=True)



Two issues I've noticed with this:
 - Arguments in the nested group show up in the usage string, but not in the help text.  The nested arguments are still parsed and available in the result, as normal.
 - Arguments in the nested group are not mutually exclusive with any arguments in the containing mutually_exclusive_group.  
   - I would expect:
       --b          ok
       --c          ok
       --d          ok
       --b --c      error
       --b --d      error
       --c --d      error*
       --b --c --d  error

*From a design perspective, it seems like argument_groups are meant to control display, and mutually_exclusive_groups are meant to control logic, so I think "error" makes sense here.  I personally would like the ability to allow "--c --d", but I think that's a separate discussion and probably a new type of group.

----------
components: Library (Lib)
messages: 355370
nosy: Tim Sanders
priority: normal
severity: normal
status: open
title: argparse unexpected behavior with argument group inside mutually exclusive group
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38590>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:05:42 2019
From: report at bugs.python.org (Batuhan)
Date: Fri, 25 Oct 2019 19:05:42 +0000
Subject: [issue35448] ConfigParser .read() - handling of nonexistent files
In-Reply-To: <1544373330.85.0.788709270274.issue35448@psf.upfronthosting.co.za>
Message-ID: <1572030342.09.0.40701803774.issue35448@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

> I do not think that adding an extra parameter to .read() will solve any problem.

There is a use case of this (which some of tools depends) about checking if configuration exists and if not, raising an error. Now, they can solve this by just adding check_exist argument. 

> Changing the default behavior will break existing code.

Can you give an example of how this feature can/could break existing code?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35448>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:23:29 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 25 Oct 2019 19:23:29 +0000
Subject: [issue38591] Deprecating MultiLoopChildWatcher
Message-ID: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>


New submission from Kyle Stanley <aeros167 at gmail.com>:

Proposal: 
Deprecate the alternative process watcher implementation to ThreadedChildWatcher, MultiLoopChildWatcher.

Motivation:
The idea for this proposal came from a comment from Andrew Svetlov in GH-16552:
"I believe after polishing ThreadedChildWatcher we can start deprecation of watchers subsystem at all, it generates more problems than solves."

Although Andrew suggested the idea of deprecating the process watchers subsystem entirely, I think that it would be adequate to start with just deprecating MultiLoopChildWatcher and proceeding from there. This is because the other three watcher implementations are significantly more stable in comparison (based on number of issues), have less complex implementations, and have far more widespread usage across public repositories. I would not be opposed to deprecating the other alternative watchers as well, but MultiLoopChildWatcher likely has the most justification for removal.

Details:
The class MultiLoopChildWatcher has a fairly complex implementation, causes a number of issues, is fairly unstable, is rarely utilized in comparison with the rest of the watchers API. It seems to have become a significant burden on maintenance for asyncio development without providing a significant benefit to the vast majority of users. 

Current unresolved MultiLoopChildWatcher issues:
https://bugs.python.org/issue38323
https://bugs.python.org/issue38182
https://bugs.python.org/issue37573

(3 out of the 5 open process watcher issues are caused by MultiLoopChildWatcher)

GitHub code usage comparison:
MultiLoopChildWatcher: https://github.com/search?l=Python&q=MultiLoopChildWatcher&type=Code (20 results)
ThreadedChildWatcher: https://github.com/search?l=Python&q=ThreadedChildWatcher&type=Code (77 results) 
FastChildWatcher: https://github.com/search?l=Python&q=FastChildWatcher&type=Code (4,426 results)
SafeChildWatcher: https://github.com/search?l=Python&q=SafeChildWatcher&type=Code (7,007 results)
All of asyncio usage: https://github.com/search?l=Python&q=asyncio&type=Code (599,131 results)

Note that for the above results, it also includes matches in the CPython repository and for repositories that have exact copies of Lib/asyncio/unix_events.py. Also, ThreadedChildWatcher likely has significantly less results since it's already the default watcher returned by asyncio.get_child_watcher(), so there's less need to explicitly declare it compared to the others. There are of course private repositories and non-GitHub repositories this doesn't include, but it should provide a general idea of overall usage.

My experience in interacting with asyncio users is similar to the results. The process watchers subsystem seems to be minimally used compared to the rest of asyncio, with ThreadedChildWatcher likely being the most used as the default returned from `asyncio.get_child_watcher()`. I have not personally seen a realistic example of usage of MultiLoopChildWatcher outside of python/cpython, and all of the results returned on GitHub were copies of Lib/asyncio/unix_events.py or Lib/test/test_asyncio/test_subprocess.py.

I would be interested in working on this issue if it is approved, as I think it would provide a significant long term reduction in maintenance for asyncio; allowing us to focus on the improvement and development of other features that benefit a far larger audience.

----------
components: asyncio
messages: 355372
nosy: aeros, asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: Deprecating MultiLoopChildWatcher
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:24:15 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 25 Oct 2019 19:24:15 +0000
Subject: [issue38591] Deprecating MultiLoopChildWatcher
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572031455.59.0.884043222264.issue38591@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
assignee:  -> aeros
nosy: +vstinner
status: open -> pending

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:28:00 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 25 Oct 2019 19:28:00 +0000
Subject: [issue38591] Deprecating MultiLoopChildWatcher
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572031680.96.0.634381934333.issue38591@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

Didn't we just add MultiLoopChildWatcher in 3.8?

----------
status: pending -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:35:46 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 Oct 2019 19:35:46 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1572032146.11.0.658037501376.issue38533@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

For me, 'pyw -3.7 -m idlelib' in Command Prompt opens IDLE with 3.7.5.  So does the equivalent run by clicking the IDLE icon:
C:\Programs\Python37\pythonw.exe "C:\Programs\Python37\Lib\idlelib\idle.pyw"

This report reminds me that I should continue to install and minimally test each release.

----------
nosy: +terry.reedy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:37:03 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 25 Oct 2019 19:37:03 +0000
Subject: [issue38591] Deprecating MultiLoopChildWatcher
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572032223.99.0.568979713644.issue38591@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> Didn't we just add MultiLoopChildWatcher in 3.8?

Yep, that's correct: https://docs.python.org/3/library/asyncio-policy.html#asyncio.MultiLoopChildWatcher

I wasn't aware of that, but it would explain the current lack of usage. I'm generally in favor of Andrew's idea to deprecate the watchers subsystem, but perhaps if we go through with that we should remove MultiLoopChildWatcher from 3.8 (if it's not too late to do so) instead of deprecating it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:38:13 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 Oct 2019 19:38:13 +0000
Subject: [issue38538] dictobject dictviews don't return NotImplemented for
 unrecognized types.
In-Reply-To: <1571585548.13.0.376831813762.issue38538@roundup.psfhosted.org>
Message-ID: <1572032293.35.0.714796988816.issue38538@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
stage:  -> test needed
versions:  -Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38538>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:43:31 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 25 Oct 2019 19:43:31 +0000
Subject: [issue38591] Deprecating MultiLoopChildWatcher
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572032611.46.0.548029818532.issue38591@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

> but perhaps if we go through with that we should remove MultiLoopChildWatcher from 3.8 (if it's not too late to do so) instead of deprecating it.

I'll leave that up to Andrew to decide, but I'd be +1 to drop it asap, especially if we want to eventually deprecate watchers.  

Speaking of watchers -- big +1 from me to drop them all at some point. I would start as early as 3.9.

Linux has pidfd now, freebsd/macos has kqueue, windows has its own apis for watching processes. Threads can be the backup method for OSes that lack proper APIs for watching multiple processes (without using SIGCHLD etc).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:48:01 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 Oct 2019 19:48:01 +0000
Subject: [issue28866] Type cache is not correctly invalidated on a class
 defining mro()
In-Reply-To: <1480862145.72.0.468660451957.issue28866@psf.upfronthosting.co.za>
Message-ID: <1572032881.21.0.189082620636.issue28866@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

#38541 reports a severe attribute access slowdown in 3.7.4 in some situations.  (Fixed by the enhancement in #36922, which I presume cannot be backported.)

----------
nosy: +terry.reedy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28866>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:50:03 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 Oct 2019 19:50:03 +0000
Subject: [issue38541] Performance degradation of attribute accesses in Python
 3.7.4
In-Reply-To: <1571645744.43.0.285485842632.issue38541@roundup.psfhosted.org>
Message-ID: <1572033003.06.0.436540539118.issue38541@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

I added a note to #28866 about this.  The fix in #36922 is likely an enhancement that cannot be backported.  Please retest with 3.7.5 if you can, though I have no expectation of any change.

----------
nosy: +serhiy.storchaka, terry.reedy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38541>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:54:38 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 25 Oct 2019 19:54:38 +0000
Subject: [issue38591] Deprecating MultiLoopChildWatcher
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572033278.62.0.438850978012.issue38591@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> Speaking of watchers -- big +1 from me to drop them all at some point. I would start as early as 3.9.

Yeah that was my initial plan, to start the deprecation in 3.9 and finalize the removal in 3.11. We might be able to make an exception for MultiLoopChildWatcher and just remove it from 3.8 though. 

I think it will be necessary to fix the issues in the near future if we want to keep MultiLoopChildWatcher in 3.8 (as they apply to 3.8 and 3.9). I would certainly not be ecstatic about the idea of removing something that was just recently added (similar to how we had to revert the new streaming changes due to API design), but I'm even less in favor of keeping something around that's not stable in a final release. 

Based on my investigation of https://bugs.python.org/issue38323, it seems like it will be a rather complex issue to solve.

----------
status: open -> pending

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 15:58:23 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 25 Oct 2019 19:58:23 +0000
Subject: [issue38591] Deprecating MultiLoopChildWatcher
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572033503.44.0.471759482923.issue38591@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

Kyle, why are you resetting the status to "Pending"?

> I think it will be necessary to fix the issues in the near future if we want to keep MultiLoopChildWatcher in 3.8 (as they apply to 3.8 and 3.9). I would certainly not be ecstatic about the idea of removing something that was just recently added (similar to how we had to revert the new streaming changes due to API design), but I'm even less in favor of keeping something around that's not stable in a final release. 

Your opinion on this is duly noted.  

It would be great to hear what Andrew and Victor think about this.

----------
status: pending -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 16:01:29 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 25 Oct 2019 20:01:29 +0000
Subject: [issue38591] Deprecating MultiLoopChildWatcher
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572033689.55.0.451297387545.issue38591@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> Kyle, why are you resetting the status to "Pending"?

That was an accident, I think I had that set already on the page and submitted my comment just after you did yours.

I'm going to change the title of the issue to "Deprecate Process Child Watchers". I started the proposal bit more conservatively because I thought that it might be easier to just deprecate MultiLoopChildWatcher at first. But seeing as it was just added in 3.8, I don't think it would make as much sense to deprecate that one by itself.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 16:02:23 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 25 Oct 2019 20:02:23 +0000
Subject: [issue38591] Deprecate Process Child Watchers
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572033743.77.0.527059041207.issue38591@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
title: Deprecating MultiLoopChildWatcher -> Deprecate Process Child Watchers

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 16:06:48 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 25 Oct 2019 20:06:48 +0000
Subject: [issue38583] The activate script in Windows is not correct for venvs
 created in git-bash
In-Reply-To: <1571927523.33.0.935819222823.issue38583@roundup.psfhosted.org>
Message-ID: <1572034008.38.0.812525276293.issue38583@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

I agree this would be better, though it may not be that easy to do.

If you're running Windows Python from WSL, then your "bash style" path should be "/mnt/c/some/path", not "/c/some/path". So the answer isn't as simple as .replace('\\', '/').

I did some quick testing with posixpath and pathlib and neither has an obvious conversion from a Windows path to a POSIX path, though pathlib.PurePosixPath(pathlib.PureWindowsPath(p)) comes closest.

Perhaps the best approach here is to improve `activate` to determine its path when run, like we did for `activate.ps1`? Then we don't need to substitute the path in at creation time.

----------
versions: +Python 3.9 -Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38583>
_______________________________________

From report at bugs.python.org  Fri Oct 25 16:09:59 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 25 Oct 2019 20:09:59 +0000
Subject: [issue38533] v3.7.5 py script run ok with python.exe but not
 pythonw.exe (python silent console not working)
In-Reply-To: <1571545903.38.0.511013655415.issue38533@roundup.psfhosted.org>
Message-ID: <1572034199.29.0.259442893417.issue38533@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

> FWIW, the very first thing that I checked was the dependencies of pythonw.exe

The version in the Store has a different build of pythonw.exe (because it has to be able to determine its user site-packages location differently).

Dump of file C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.7_3.7.1520.0_x64__hd69rhyc2wevp\pythonw.exe

File Type: EXECUTABLE IMAGE

  Image has the following dependencies:

    api-ms-win-core-libraryloader-l1-2-0.dll
    api-ms-win-core-com-l1-1-0.dll
    api-ms-win-core-errorhandling-l1-1-0.dll
    SHELL32.dll
    python37.dll
    MSVCP140.dll  ****** bug here, but already fixed for next release
    VCRUNTIME140.dll
    api-ms-win-crt-runtime-l1-1-0.dll
    api-ms-win-crt-environment-l1-1-0.dll
    api-ms-win-crt-heap-l1-1-0.dll
    api-ms-win-crt-math-l1-1-0.dll
    api-ms-win-crt-stdio-l1-1-0.dll
    api-ms-win-crt-locale-l1-1-0.dll
    api-ms-win-crt-string-l1-1-0.dll
    api-ms-win-core-handle-l1-1-0.dll
    api-ms-win-core-synch-l1-1-0.dll
    api-ms-win-core-rtlsupport-l1-1-0.dll
    api-ms-win-core-processthreads-l1-1-0.dll
    api-ms-win-core-processthreads-l1-1-1.dll
    api-ms-win-core-debug-l1-1-0.dll
    api-ms-win-core-profile-l1-1-0.dll
    api-ms-win-core-sysinfo-l1-1-0.dll
    api-ms-win-core-interlocked-l1-1-0.dll
    KERNEL32.dll
    api-ms-win-core-winrt-l1-1-0.dll
    api-ms-win-core-winrt-string-l1-1-0.dll
    OLEAUT32.dll
    api-ms-win-core-winrt-error-l1-1-1.dll
    api-ms-win-core-winrt-error-l1-1-0.dll

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38533>
_______________________________________

From report at bugs.python.org  Fri Oct 25 16:18:20 2019
From: report at bugs.python.org (Marco Rougeth)
Date: Fri, 25 Oct 2019 20:18:20 +0000
Subject: [issue38592] Add pt-br to the language switcher at the Python docs
 website
Message-ID: <1572034700.82.0.68590075216.issue38592@roundup.psfhosted.org>


New submission from Marco Rougeth <marco at rougeth.com>:

The translation of the Python docs for Brazilian Portuguese is at around 20%. The Brazilian community have been working hard on it for the past 2 years, and as discussed with Julien, we believe this is a good moment to add the pt-br language switcher.

----------
messages: 355384
nosy: rougeth
priority: normal
severity: normal
status: open
title: Add pt-br to the language switcher at the Python docs website

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38592>
_______________________________________

From report at bugs.python.org  Fri Oct 25 16:18:29 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 25 Oct 2019 20:18:29 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572034709.8.0.0233762928961.issue38557@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Verified from Python.
>>> t = (1,2,3)
>>> t2 = t[:]
>>> id(t), id(t2)
(1672756229504, 1672756229504)

A partial slice cannot the original tuple, so I presume that the emphasis is about returning a (new) *tuple*, rather than some sort of view of the original.  However,
        Py_INCREF(a);
        return (PyObject *)a;
date back to at least 1997 (GvR), so the optimization is not new.  I don't know what should replace 'New reference.'  'Old or new reverence.'?

"Take a slice of the tuple pointed to by p from low to high and return it **as a new tuple**."

could be replaces with

"Return the slice of the tuple point to by p for low to high.  If it is a proper subslice, return a new tuple."

This leave it undefined when a complete slice.

----------
nosy: +terry.reedy
versions:  -Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Fri Oct 25 16:26:21 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Fri, 25 Oct 2019 20:26:21 +0000
Subject: [issue38580] select()'s documentation claims only sequences are
 accepted, but it allows all iterables
In-Reply-To: <1571915326.93.0.150606644361.issue38580@roundup.psfhosted.org>
Message-ID: <1572035181.06.0.948418352706.issue38580@roundup.psfhosted.org>


Change by Brandt Bucher <brandtbucher at gmail.com>:


----------
nosy: +brandtbucher

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38580>
_______________________________________

From report at bugs.python.org  Fri Oct 25 16:29:51 2019
From: report at bugs.python.org (Marco Rougeth)
Date: Fri, 25 Oct 2019 20:29:51 +0000
Subject: [issue38592] Add pt-br to the language switcher at the Python docs
 website
In-Reply-To: <1572034700.82.0.68590075216.issue38592@roundup.psfhosted.org>
Message-ID: <1572035391.62.0.155997858419.issue38592@roundup.psfhosted.org>


Change by Marco Rougeth <marco at rougeth.com>:


----------
keywords: +patch
pull_requests: +16454
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16924

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38592>
_______________________________________

From report at bugs.python.org  Fri Oct 25 17:15:13 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 25 Oct 2019 21:15:13 +0000
Subject: [issue38434] sys.addaudithook event is not documented
In-Reply-To: <1570724703.62.0.219483741722.issue38434@roundup.psfhosted.org>
Message-ID: <1572038113.87.0.721459402794.issue38434@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

The import audit event is also not documented.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38434>
_______________________________________

From report at bugs.python.org  Fri Oct 25 17:22:01 2019
From: report at bugs.python.org (Kevin Chen)
Date: Fri, 25 Oct 2019 21:22:01 +0000
Subject: [issue38571] Segfault with StopIteration
In-Reply-To: <1571881819.52.0.556347570713.issue38571@roundup.psfhosted.org>
Message-ID: <1572038521.31.0.709429140489.issue38571@roundup.psfhosted.org>


Kevin Chen <kevin at kevinchen.com> added the comment:

Sorry for the noise.  I upgraded my gevent (1.3.5 to 1.4.0) and greenlet (0.4.13 to 0.4.15) libraries, and that appears to have resolved the issue.  I assume there was an incompatibility in one or both of the older versions of these libraries with python 3.7, but I had not previously realized that they were causing the issue.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38571>
_______________________________________

From report at bugs.python.org  Fri Oct 25 17:28:15 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 25 Oct 2019 21:28:15 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572038895.64.0.76034776301.issue38557@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16455
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16925

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Fri Oct 25 17:34:31 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 25 Oct 2019 21:34:31 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572039271.46.0.603870004388.issue38557@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

The part about "new tuple" can be removed. The documentation olready contains an automatically generated note about a new reference.

PR 16925 improves the documentation for getting/setting items/slices of lists and tuples.

----------
nosy: +serhiy.storchaka
stage: patch review -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Fri Oct 25 17:51:08 2019
From: report at bugs.python.org (Valentyn Tymofieiev)
Date: Fri, 25 Oct 2019 21:51:08 +0000
Subject: [issue38593] Python 3.7 does not catch infinite recursion for some
 values of sys.getrecursionlimit()
Message-ID: <1572040268.11.0.31838216135.issue38593@roundup.psfhosted.org>


New submission from Valentyn Tymofieiev <valentyn at google.com>:

While investigating an issue[1] in Apache Beam, we observed that Python 3.7 does not catch an infinite recursion for some values of sys.getrecursionlimit().

Repro steps:

docker run -it --entrypoint=/bin/bash python:3.7-stretch
git clone https://github.com/tvalentyn/beam.git
cd beam
git checkout origin/reproduce_uncaught_recursion_error
cd sdks/python
pip install nose
pip install -e .[gcp,test]
python ./setup.py nosetests --nocapture --tests 'apache_beam/runners/dataflow/dataflow_runner_test.py:DataflowRunnerTest.test_remote_runner_display_data'

On Python 3.7, the test output is:

==========
Recursion limit set to: 1002
Caught maximum recursion depth exceeded while calling a Python object. Current recursionlimit is 1002
Recursion limit set to: 1003
Caught maximum recursion depth exceeded. Current recursionlimit is 1003
Recursion limit set to: 1004
Caught maximum recursion depth exceeded while calling a Python object. Current recursionlimit is 1004
Recursion limit set to: 1005
Caught maximum recursion depth exceeded while calling a Python object. Current recursionlimit is 1005
Recursion limit set to: 1006
Fatal Python error: Cannot recover from stack overflow.

Current thread 0x00007fd9f28a5700 (most recent call first):
  File "/usr/local/lib/python3.7/site-packages/dill/_dill.py", line 424 in get
...
==========

So, if we set recursion limit to 1006 in [2], Python 3.7 interpreter does not throw/catch RecursionError in [3]. On Python 3.5, 3.6 the same code successfully catches RecursionError.  
 
[1] https://issues.apache.org/jira/browse/BEAM-8397 
[2] https://github.com/tvalentyn/beam/blob/158cc9006fef74fc17d52a4220172758f7a82820/sdks/python/apache_beam/runners/dataflow/dataflow_runner_test.py#L235 
[3] https://github.com/tvalentyn/beam/blob/158cc9006fef74fc17d52a4220172758f7a82820/sdks/python/apache_beam/pipeline.py#L599

----------
components: Interpreter Core
messages: 355389
nosy: Valentyn Tymofieiev
priority: normal
severity: normal
status: open
title: Python 3.7 does not catch infinite recursion for some values of sys.getrecursionlimit()
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38593>
_______________________________________

From report at bugs.python.org  Fri Oct 25 17:51:35 2019
From: report at bugs.python.org (Valentyn Tymofieiev)
Date: Fri, 25 Oct 2019 21:51:35 +0000
Subject: [issue38593] Python 3.7 does not catch infinite recursion for some
 values of sys.getrecursionlimit()
In-Reply-To: <1572040268.11.0.31838216135.issue38593@roundup.psfhosted.org>
Message-ID: <1572040295.59.0.492478949155.issue38593@roundup.psfhosted.org>


Change by Valentyn Tymofieiev <valentyn at google.com>:


----------
type:  -> crash

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38593>
_______________________________________

From report at bugs.python.org  Fri Oct 25 18:05:39 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Fri, 25 Oct 2019 22:05:39 +0000
Subject: [issue38591] Deprecate Process Child Watchers
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572041139.45.0.52334921818.issue38591@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

ThreadedChildWatcher starts a thread per process but has O(1) complexity.

MultiLoopChildWatcher doesn't spawn threads, it can be used safely with asyncio loops spawn in multiple threads. The complexity is O(N) plus no other code should contest for SIG_CHLD subscription.

FastChildWatcher has O(1), this is the good news. All others are bad: the watcher conflicts even with blocking `subprocess.wait()` call, even if the call is performed from another thread.

SafeChildWatcher is safer than FastChildWatcher but working with asyncio subprocess API is still super complicated if asyncio code is running from multiple threads. SafeChildWatcher works well only if asyncio is run from the main thread only. Complexity is O(N).

I think FastChildWatcher and SafeChildWatcher should go, ThreadedChildWatcher should be kept default and MultiLoopChildWatcher is an option where ThreadedChildWatcher is not satisfactory.

MultiLoopChildWatcher problems can and should be fixed; there is nothing bad in the idea but slightly imperfect implementation.

Regarding pidfd and kqueue -- I love to see pull requests with proposals. Now nothing exists.
The pidfd is available starting from the latest released Linux 5.3;  we need to wait for a decade before all Linux distros adopt it and we can drop all other implementations.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 18:20:10 2019
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 25 Oct 2019 22:20:10 +0000
Subject: [issue38558] Data Structures documentation out of sync with new
 Walrus operator
In-Reply-To: <1571776032.37.0.709698360286.issue38558@roundup.psfhosted.org>
Message-ID: <1572042010.76.0.334326609941.issue38558@roundup.psfhosted.org>


Zachary Ware <zachary.ware at gmail.com> added the comment:


New changeset cb2cf06b0aad1851f54999497c1b50c381d1fdd8 by Zachary Ware (Ammar Askar) in branch 'master':
bpo-38558: Mention `:=` in conditions tutorial (GH-16919)
https://github.com/python/cpython/commit/cb2cf06b0aad1851f54999497c1b50c381d1fdd8


----------
nosy: +zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38558>
_______________________________________

From report at bugs.python.org  Fri Oct 25 18:20:19 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 25 Oct 2019 22:20:19 +0000
Subject: [issue38558] Data Structures documentation out of sync with new
 Walrus operator
In-Reply-To: <1571776032.37.0.709698360286.issue38558@roundup.psfhosted.org>
Message-ID: <1572042019.53.0.97746241959.issue38558@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16456
pull_request: https://github.com/python/cpython/pull/16926

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38558>
_______________________________________

From report at bugs.python.org  Fri Oct 25 18:23:16 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 25 Oct 2019 22:23:16 +0000
Subject: [issue38592] Add pt-br to the language switcher at the Python docs
 website
In-Reply-To: <1572034700.82.0.68590075216.issue38592@roundup.psfhosted.org>
Message-ID: <1572042196.67.0.673821482297.issue38592@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
assignee:  -> mdk
components: +Documentation
nosy: +mdk

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38592>
_______________________________________

From report at bugs.python.org  Fri Oct 25 18:26:03 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 25 Oct 2019 22:26:03 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572042363.79.0.533867578283.issue38589@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Fri Oct 25 18:27:10 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 25 Oct 2019 22:27:10 +0000
Subject: [issue38558] Data Structures documentation out of sync with new
 Walrus operator
In-Reply-To: <1571776032.37.0.709698360286.issue38558@roundup.psfhosted.org>
Message-ID: <1572042430.13.0.615341352913.issue38558@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset cf028b57169499f82b73dd0977fe0bab40778a60 by Miss Skeleton (bot) in branch '3.8':
bpo-38558: Mention `:=` in conditions tutorial (GH-16919)
https://github.com/python/cpython/commit/cf028b57169499f82b73dd0977fe0bab40778a60


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38558>
_______________________________________

From report at bugs.python.org  Fri Oct 25 19:35:44 2019
From: report at bugs.python.org (Daniel Hillier)
Date: Fri, 25 Oct 2019 23:35:44 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572046544.25.0.165541848275.issue38334@roundup.psfhosted.org>


Daniel Hillier <daniel.hillier at gmail.com> added the comment:

Hi,

I have another patch I would like to contribute to the zipfile module but would like to request a review of this one to minimise conflicts with later patches. If anyone is able to review the patch, I would really appreciate it :)

Also, with regards to selecting Python versions for this issue, is there any rule of thumb I should be following?

Thanks,
Dan

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Fri Oct 25 19:36:40 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 25 Oct 2019 23:36:40 +0000
Subject: [issue38591] Deprecate Process Child Watchers
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572046600.07.0.0177351166964.issue38591@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> I think FastChildWatcher and SafeChildWatcher should go, ThreadedChildWatcher should be kept default and MultiLoopChildWatcher is an option where ThreadedChildWatcher is not satisfactory.

Okay, I think I can understand the reasoning here. Do you think that FastChildWatcher and SafeChildWatcher could be deprecated starting in 3.9 and removed in 3.11? If so, I'd be glad to start working on adding the deprecation warnings and the 3.9 Whats New entries.

> MultiLoopChildWatcher problems can and should be fixed; there is nothing bad in the idea but slightly imperfect implementation.

Yeah my largest concern was just that the current issues seem especially complex to fix and I interpreted your previous comment as "I'd like to deprecate all the process watchers in the near future". Thus, it seemed to make sense to me that we could start removing them rather than sinking time into fixing something that might be removed soon. 

By "slightly imperfect implementation", do you have any ideas for particularly imperfect parts of it that could use improvement? 

I feel that I've developed a decent understanding of the implementation for ThreadedChildWatcher, but after looking at the race conditions for MultiLoopChildWatcher in https://bugs.python.org/issue38323, I'll admit that I felt a bit lost for where to find a solution. Primarily because my understanding of the signal module is quite limited in comparison to others; it's not an area that I've strongly focused on.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 20:36:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Sat, 26 Oct 2019 00:36:55 +0000
Subject: [issue38591] Deprecate Process Child Watchers
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572050215.17.0.575706189641.issue38591@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> ThreadedChildWatcher starts a thread per process but has O(1) complexity.

But it spawns a new Python thread per process which can be a blocker issue if a server memory is limited. What if you want to spawn 100 processes? Or 1000 processes? What is the memory usage?

I like FastChildWatcher!

> ... but working with asyncio subprocess API is still super complicated if asyncio code is running from multiple threads

Well, I like the ability to choose the child watcher implementation depending on my use case. If asyncio is only run from the main thread, FastChildWatcher is safe, fast and has low memory footprint, no?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 20:40:39 2019
From: report at bugs.python.org (STINNER Victor)
Date: Sat, 26 Oct 2019 00:40:39 +0000
Subject: [issue38591] Deprecate Process Child Watchers
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572050439.91.0.507117884915.issue38591@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Regarding pidfd and kqueue -- I love to see pull requests with proposals. Now nothing exists. The pidfd is available starting from the latest released Linux 5.3;  we need to wait for a decade before all Linux distros adopt it and we can drop all other implementations.

I hope that it will take less time to expose pidfd_open() in Python! It is *already* available in the Linux kernel 5.3. My laptop is already running Linux 5.3! (Thanks Fedora 30.)

I would prefer to keep an API to choose the child watcher since it seems like even in 2019, there are still new APIs (pidfd) to wait for a process completion. I expect that each implementation will have advantages and drawbacks.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Fri Oct 25 21:26:57 2019
From: report at bugs.python.org (Valentyn Tymofieiev)
Date: Sat, 26 Oct 2019 01:26:57 +0000
Subject: [issue38593] Python 3.7 does not catch infinite recursion for some
 values of sys.getrecursionlimit()
In-Reply-To: <1572040268.11.0.31838216135.issue38593@roundup.psfhosted.org>
Message-ID: <1572053217.42.0.880782043369.issue38593@roundup.psfhosted.org>


Valentyn Tymofieiev <valentyn at google.com> added the comment:

I observed this issue in Python 3.7.2, 3.7.4, 3.7.5, however it seems to be fixed in 3.8.0.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38593>
_______________________________________

From report at bugs.python.org  Fri Oct 25 21:59:26 2019
From: report at bugs.python.org (Ma Lin)
Date: Sat, 26 Oct 2019 01:59:26 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1572055166.09.0.270958905274.issue38582@roundup.psfhosted.org>


Ma Lin <malincns at 163.com> added the comment:

Octal escape:
    \ooo        Character with octal value ooo
    As in Standard C, up to three octal digits are accepted.

It only accepts UCS1 characters (ooo <= 0o377):
    >>> ord('\377')
    255
    >>> len('\378')
    2
    >>> '\378' == '\37' + '8'
    True

IMHO this is not useful, and creates confusions.
Maybe it can be deprecated in language level.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Fri Oct 25 22:08:08 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Sat, 26 Oct 2019 02:08:08 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1572055688.63.0.75124561149.issue38582@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

Not very useful, surely (now that we have hex escapes).
[I'd still retain \0 as a special case, since it really is useful.] But a lot more useful than a hundred backreferences.

And I'm as a matter of principle opposed to changing something that's been in the language for decades for the benefit of someone that's by their own words "just learned Python". [Changing documentation is fine.] They by definition don't see the whole picture. Now that we don't have a BDFL anymore, I think it's vitally important to have some principles such as this one.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Fri Oct 25 22:21:44 2019
From: report at bugs.python.org (Ma Lin)
Date: Sat, 26 Oct 2019 02:21:44 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1572056504.41.0.647067278688.issue38582@roundup.psfhosted.org>


Ma Lin <malincns at 163.com> added the comment:

> I'd still retain \0 as a special case, since it really is useful.

Yes, maybe \0 is used widely, I didn't think of it.
Changing is troublesome, let's keep it as is.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Fri Oct 25 22:37:05 2019
From: report at bugs.python.org (Matthew Barnett)
Date: Sat, 26 Oct 2019 02:37:05 +0000
Subject: [issue38582] re: backreference number in replace string can't >= 100
In-Reply-To: <1571918460.23.0.951384683462.issue38582@roundup.psfhosted.org>
Message-ID: <1572057425.52.0.192595641652.issue38582@roundup.psfhosted.org>


Matthew Barnett <python at mrabarnett.plus.com> added the comment:

If we did decide to remove it, but there was still a demand for octal escapes, then I'd suggest introducing \oXXX.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38582>
_______________________________________

From report at bugs.python.org  Fri Oct 25 23:24:54 2019
From: report at bugs.python.org (Gregory Szorc)
Date: Sat, 26 Oct 2019 03:24:54 +0000
Subject: [issue38594] importlib.metadata documentation deficiencies
Message-ID: <1572060294.8.0.317725248433.issue38594@roundup.psfhosted.org>


New submission from Gregory Szorc <gregory.szorc at gmail.com>:

As I was attempting to implement the find_distributions() interface for PyOxidizer, I got confused by importlib.metadata's documentation.

The documentation for this module states:

```
What this means in practice is that to support finding distribution package
metadata in locations other than the file system, you should derive from
``Distribution`` and implement the ``load_metadata()`` method. Then from
your finder, return instances of this derived ``Distribution`` in the
``find_distributions()`` method.
```

The reference to `load_metadata()` is the only occurrence of the string `load_metadata` in the CPython and importlib_metadata code bases. I therefore believe the documentation in both CPython and the importlib_metadata standalone package are wrong because they are referring to a method that is never implemented nor called.

Looking at the documentation and source code for importlib.metadata, I'm also a bit confused about how exactly I'm supposed to implement a custom Distribution which isn't based on filesystems. For example, I see that certain APIs return Path-like objects (which I will need to implement). But it isn't clear exactly which attributes are mandated to exist! Am I expected to implement the full pathlib.Path interface or just a subset?

Regarding how find_distributions() is called, I also don't understand why the Context is optional and how Context could be used in some situations. For example, the implementation of discover() can construct Context instances with no arguments, which is then fed into find_distributions(). So I guess context=None or context.name=None implies "return Distribution's for every known package?" If so, this behavior is undocumented.

I'm also not sure what Context.path is for. I /think/ it is only used for the path-based finder/distribution. But the way it is documented implies it should always exist, which doesn't seem appropriate for cases like PyOxidizer which will retrieve metadata from in-memory without filesystem I/O.

I think what I'm trying to say is that the existing documentation for importlib.metadata is not sufficient to robustly implement a custom find_distributions() + Distribution type. I would kindly request that a domain expert revise the documentation such that a 3rd party can implement a custom solution. My preferred solution would be for there to be formal interfaces in importlib.abc like there are for everything else in the importlib realm. (The interfaces for finders and loaders are super useful when implementing a finder/loader from scratch.)

FWIW I think I like the new metadata API and I think it is flexible enough to allow tools like PyOxidizer to do crazy things like divorce resources from the filesystem! But it is hard to say for sure since the interfaces aren't clearly defined at present.

----------
assignee: docs at python
components: Documentation
messages: 355402
nosy: barry, docs at python, indygreg, jaraco
priority: normal
severity: normal
status: open
title: importlib.metadata documentation deficiencies
type: enhancement
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38594>
_______________________________________

From report at bugs.python.org  Sat Oct 26 01:02:59 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Sat, 26 Oct 2019 05:02:59 +0000
Subject: [issue38570] Shlex does not parse commands containing single quotes
 correctly
In-Reply-To: <1571864428.26.0.327920266668.issue38570@roundup.psfhosted.org>
Message-ID: <1572066179.47.0.249930921545.issue38570@roundup.psfhosted.org>


Anthony Sottile <asottile at umich.edu> added the comment:

Try with `sh`:

(it prompts for continuation, I pressed ^D to end it)

$ export F=$'\''
> 
> 
> 
> 
> sh: 8: Syntax error: Unterminated quoted string


dollar-sign strings are a `bash` extension, I don't think they're supported by *sh*lex (maybe if there was a bashlex module :D)

There's the `posix=False` option to `shlex.split` -- I'm not sure what it does/doesn't enable though (the docs aren't thorough here and the code is a bit non-obvious):

>>> shlex.split(s, posix=False)
['export', "F=$'\\''"]

----------
nosy: +Anthony Sottile

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38570>
_______________________________________

From report at bugs.python.org  Sat Oct 26 01:19:33 2019
From: report at bugs.python.org (Ryan Govostes)
Date: Sat, 26 Oct 2019 05:19:33 +0000
Subject: [issue38595] io.BufferedRWPair doc warning may need clarification
Message-ID: <1572067173.75.0.622729203693.issue38595@roundup.psfhosted.org>


New submission from Ryan Govostes <rgovostes at gmail.com>:

The documentation for the io.BufferedRWPair class gives this warning:

> BufferedRWPair does not attempt to synchronize accesses to its underlying raw streams. You should not pass it the same object as reader and writer; use BufferedRandom instead.

I have a hard time understanding what this warning is trying to tell me.

1. What does it mean to "synchronize accesses"?

2. Why can't I pass the same object as reader and writer? The docstring in _pyio.py says, "This is typically used with a socket or two-way pipe."

3. How does BufferedRandom, which adds the seek() and tell() interfaces, address the issue of "synchroniz[ing] accesses"? Is synchronization automatic? What does this do for sockets or pipes which cannot seek?

----------
assignee: docs at python
components: Documentation
messages: 355404
nosy: docs at python, rgov
priority: normal
severity: normal
status: open
title: io.BufferedRWPair doc warning may need clarification
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38595>
_______________________________________

From report at bugs.python.org  Sat Oct 26 01:30:22 2019
From: report at bugs.python.org (Ryan Govostes)
Date: Sat, 26 Oct 2019 05:30:22 +0000
Subject: [issue38595] io.BufferedRWPair doc warning may need clarification
In-Reply-To: <1572067173.75.0.622729203693.issue38595@roundup.psfhosted.org>
Message-ID: <1572067822.14.0.642208130709.issue38595@roundup.psfhosted.org>


Ryan Govostes <rgovostes at gmail.com> added the comment:

The origin of this warning involves interleaving read and write operations, and was added here: https://bugs.python.org/issue12213

I'm not sure if it applies to sockets, pipes, etc. though.

The pySerial documentation advises using io.BufferedRWPair(x, x) where x is a serial device. But this StackOverflow post reports that it is problematic, in line with the warning. (The author appears to be talking about Windows.)

https://stackoverflow.com/questions/24498048/python-io-modules-textiowrapper-or-buffererwpair-functions-are-not-playing-nice

----------
nosy: +benjamin.peterson, pitrou, stutzbach

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38595>
_______________________________________

From report at bugs.python.org  Sat Oct 26 01:48:41 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Sat, 26 Oct 2019 05:48:41 +0000
Subject: [issue35714] Document that the null character '\0' terminates a
 struct format spec
In-Reply-To: <1547160130.27.0.885629506261.issue35714@roundup.psfhosted.org>
Message-ID: <1572068921.23.0.934275972066.issue35714@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
keywords: +patch
pull_requests: +16457
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16928

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35714>
_______________________________________

From report at bugs.python.org  Sat Oct 26 01:53:07 2019
From: report at bugs.python.org (Ammar Askar)
Date: Sat, 26 Oct 2019 05:53:07 +0000
Subject: [issue38558] Data Structures documentation out of sync with new
 Walrus operator
In-Reply-To: <1571776032.37.0.709698360286.issue38558@roundup.psfhosted.org>
Message-ID: <1572069187.15.0.0726859094685.issue38558@roundup.psfhosted.org>


Ammar Askar <ammar at ammaraskar.com> added the comment:

Thank you for the report Matt!

----------
nosy: +ammar2
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38558>
_______________________________________

From report at bugs.python.org  Sat Oct 26 04:39:22 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 26 Oct 2019 08:39:22 +0000
Subject: [issue35714] Document that the null character '\0' terminates a
 struct format spec
In-Reply-To: <1547160130.27.0.885629506261.issue35714@roundup.psfhosted.org>
Message-ID: <1572079162.77.0.23527897984.issue35714@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

I agree with Serhiy. Any other unrecognised character would raise an error. The null character should do the same.

----------
nosy: +mark.dickinson

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35714>
_______________________________________

From report at bugs.python.org  Sat Oct 26 04:45:04 2019
From: report at bugs.python.org (=?utf-8?b?RmXImXRpbMSDIEdlb3JnZSBDxIN0xINsaW4=?=)
Date: Sat, 26 Oct 2019 08:45:04 +0000
Subject: [issue38596] simple example give a Linux core dumped with atk-bridge
Message-ID: <1572079504.05.0.0514921170938.issue38596@roundup.psfhosted.org>


New submission from Fe?til? George C?t?lin <catalinfest at gmail.com>:

My simple notepad code with QtWidgets.QPlainTextEdit() give me a crash dump on Linux Fedora 30 with python3

Python 3.7.4 (default, Jul  9 2019, 16:32:37) 
[GCC 9.1.1 20190503 (Red Hat 9.1.1-1)] on linux

[mythcat at desk pyqt5_examples]$ uname -a
Linux desk 5.3.7-200.fc30.x86_64 #1 SMP Fri Oct 18 20:13:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

[mythcat at desk pyqt5_examples]$ python3 notepad.py 

** (python3:3077): WARNING **: 11:26:06.007: AT-SPI: Could not obtain desktop path or name


** (python3:3077): WARNING **: 11:26:06.029: atk-bridge: GetRegisteredEvents returned message with unknown signature

** (python3:3077): WARNING **: 11:26:06.029: atk-bridge: get_device_events_reply: unknown signature

** (python3:3077): WARNING **: 11:26:06.029: atk-bridge: get_device_events_reply: unknown signature
Traceback (most recent call last):
  File "notepad.py", line 222, in assign_syntax_py
    self.syntax = mytext(self.text_widget.document())
NameError: name 'mytext' is not defined
Traceback (most recent call last):
  File "notepad.py", line 222, in assign_syntax_py
    self.syntax = mytext(self.text_widget.document())
NameError: name 'mytext' is not defined
Aborted (core dumped)

The code is self.syntax = my_notepad.mytext(self.text_widget.document())

----------
components: Interpreter Core
messages: 355408
nosy: catafest
priority: normal
severity: normal
status: open
title: simple example give a Linux core dumped with atk-bridge
type: crash
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38596>
_______________________________________

From report at bugs.python.org  Sat Oct 26 04:45:41 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sat, 26 Oct 2019 08:45:41 +0000
Subject: [issue38591] Deprecate Process Child Watchers
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572079541.77.0.654047444631.issue38591@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

My non-LTS Ubuntu also has 5.3 kernel but I'm talking about the oldest supported RHEL/CentOS.

That's why pidfd_open() cannot be a single implementation. It's so new; my local man-pages system has not a record about the API yet (but the web has: http://man7.org/linux/man-pages/man2/pidfd_open.2.html).

> If asyncio is only run from the main thread, FastChildWatcher is safe, fast and has low memory footprint, no?

Unfortunately, no. FastChildWatcher is safe if you can guarantee that no code executed in asyncio main thread AND thread pools spawn subprocesses. Otherwise, the whole Python process becomes broken by the race condition between FastChildWatcher and any other wait()/waitpid()/waitid() call.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Sat Oct 26 05:50:50 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Sat, 26 Oct 2019 09:50:50 +0000
Subject: [issue35714] Document that the null character '\0' terminates a
 struct format spec
In-Reply-To: <1547160130.27.0.885629506261.issue35714@roundup.psfhosted.org>
Message-ID: <1572083450.81.0.15056794956.issue35714@roundup.psfhosted.org>


Zackery Spytz <zspytz at gmail.com> added the comment:

I've created a patch to reject null characters in the format string.

----------
nosy: +ZackerySpytz

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35714>
_______________________________________

From report at bugs.python.org  Sat Oct 26 06:22:48 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 26 Oct 2019 10:22:48 +0000
Subject: [issue38596] simple example give a Linux core dumped with atk-bridge
In-Reply-To: <1572079504.05.0.0514921170938.issue38596@roundup.psfhosted.org>
Message-ID: <1572085368.8.0.379478180682.issue38596@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

Can you please attach a simple reproducer script without any third party modules like qtwidgets to ensure crash is due to CPython and not due to the code in third party module itself.

----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38596>
_______________________________________

From report at bugs.python.org  Sat Oct 26 07:18:40 2019
From: report at bugs.python.org (timonegk)
Date: Sat, 26 Oct 2019 11:18:40 +0000
Subject: [issue38570] Shlex does not parse commands containing single quotes
 correctly
In-Reply-To: <1571864428.26.0.327920266668.issue38570@roundup.psfhosted.org>
Message-ID: <1572088720.54.0.496508222714.issue38570@roundup.psfhosted.org>


timonegk <python at timonengelke.de> added the comment:

Okay, thanks a lot. I am closing this since it is not a bug then.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38570>
_______________________________________

From report at bugs.python.org  Sat Oct 26 09:32:02 2019
From: report at bugs.python.org (=?utf-8?b?RmXImXRpbMSDIEdlb3JnZSBDxIN0xINsaW4=?=)
Date: Sat, 26 Oct 2019 13:32:02 +0000
Subject: [issue38596] simple example give a Linux core dumped with atk-bridge
In-Reply-To: <1572079504.05.0.0514921170938.issue38596@roundup.psfhosted.org>
Message-ID: <1572096722.07.0.805151971065.issue38596@roundup.psfhosted.org>


Fe?til? George C?t?lin <catalinfest at gmail.com> added the comment:

No. I don't have a reproducer script for this issue with Linux OS.
The mytext is a class from another script named my_notepad.
The problem comes with time when I use the menu to change the syntax value, as you can see:
self.syntax = mytext(self.text_widget.document())
My code is based on this example from GitHub account lfsando: https://github.com/lfsando/notepad/blob/master/highlighter.py maybe has the same error.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38596>
_______________________________________

From report at bugs.python.org  Sat Oct 26 09:46:09 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 13:46:09 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1572097569.13.0.156298254907.issue38535@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 26ae9f6d3d755734c9f371b9356325afe5764813 by Serhiy Storchaka in branch 'master':
bpo-38535: Fix positions for AST nodes for calls without arguments in decorators. (GH-16861)
https://github.com/python/cpython/commit/26ae9f6d3d755734c9f371b9356325afe5764813


----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sat Oct 26 09:46:34 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 26 Oct 2019 13:46:34 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1572097594.06.0.411749887622.issue38535@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16458
pull_request: https://github.com/python/cpython/pull/16929

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sat Oct 26 10:06:43 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 26 Oct 2019 14:06:43 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1572098803.49.0.666654227922.issue38535@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset ba3a566328e8df49741059b24a41480e248bf6d7 by Miss Skeleton (bot) in branch '3.8':
bpo-38535: Fix positions for AST nodes for calls without arguments in decorators. (GH-16861)
https://github.com/python/cpython/commit/ba3a566328e8df49741059b24a41480e248bf6d7


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sat Oct 26 10:07:20 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 14:07:20 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1572098840.81.0.705854372345.issue38535@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16459
pull_request: https://github.com/python/cpython/pull/16930

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sat Oct 26 10:13:32 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 14:13:32 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1572099212.66.0.497474600154.issue38535@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16460
pull_request: https://github.com/python/cpython/pull/16931

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sat Oct 26 10:30:17 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 14:30:17 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1572100217.28.0.363313821898.issue38535@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 91fc9cf43cc2e3a2f236ef9944cf1f4bed701545 by Serhiy Storchaka in branch '3.7':
[3.7] bpo-38535: Fix positions for AST nodes for calls without arguments in decorators. (GH-16861). (GH-16930)
https://github.com/python/cpython/commit/91fc9cf43cc2e3a2f236ef9944cf1f4bed701545


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sat Oct 26 10:30:33 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 14:30:33 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1572100233.55.0.65786066859.issue38535@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 493fef60a7600f83fe6916ed89d0fb0c0aab484d by Serhiy Storchaka in branch '2.7':
[2.7] bpo-38535: Fix positions for AST nodes for calls without arguments in decorators. (GH-16861). (GH-16931)
https://github.com/python/cpython/commit/493fef60a7600f83fe6916ed89d0fb0c0aab484d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sat Oct 26 11:02:39 2019
From: report at bugs.python.org (Matt Ward)
Date: Sat, 26 Oct 2019 15:02:39 +0000
Subject: [issue38558] Data Structures documentation out of sync with new
 Walrus operator
In-Reply-To: <1572069187.15.0.0726859094685.issue38558@roundup.psfhosted.org>
Message-ID: <CAB-rVRfKVDikKWMC2Sk4UdoCFgUXBM55HN-eyP0xtHV4Y9LNDw@mail.gmail.com>


Matt Ward <matt at matthewward.net> added the comment:

You're welcome!

On Fri, Oct 25, 2019 at 10:53 PM Ammar Askar <report at bugs.python.org> wrote:

>
> Ammar Askar <ammar at ammaraskar.com> added the comment:
>
> Thank you for the report Matt!
>
> ----------
> nosy: +ammar2
> resolution:  -> fixed
> stage: patch review -> resolved
> status: open -> closed
> versions: +Python 3.9
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue38558>
> _______________________________________
>

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38558>
_______________________________________

From report at bugs.python.org  Sat Oct 26 11:44:57 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 15:44:57 +0000
Subject: [issue38535] Incorrect col_offset for decorators with zero arguments
 (empty parentheses)
In-Reply-To: <1571559697.79.0.983996718555.issue38535@roundup.psfhosted.org>
Message-ID: <1572104697.18.0.716431015279.issue38535@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38535>
_______________________________________

From report at bugs.python.org  Sat Oct 26 12:52:02 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Sat, 26 Oct 2019 16:52:02 +0000
Subject: [issue38591] Deprecate Process Child Watchers
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572108722.41.0.819456584497.issue38591@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> > If asyncio is only run from the main thread, FastChildWatcher is safe, fast and has low memory footprint, no?

> Unfortunately, no. FastChildWatcher is safe if you can guarantee that no code executed in asyncio main thread AND thread pools spawn subprocesses

Am I misunderstanding something here or is this supposed to be "FastChildWatcher is safe if you can guarantee that no code executed *outside of* the asyncio main thread AND ..."? Alternatively, "FastChildWatcher is safe if you can guarantee that code *only* executed in the asyncio main thread". Both of the above have the same functional meaning. 

I think it was a typo, but I just wanted to make sure because the distinction from the original makes a functional difference in this case. 

Also, regarding the second part "thread pools spawn subprocesses", is that to say that subprocesses can only spawn within the thread pools? As in, FastChildWatcher becomes unsafe if subprocesses are spawned from anywhere else?

These answers may be fairly obvious to someone familiar working within the internals of FastChildWatcher, but it may not be overly clear to someone such as myself who has mostly just read through the documentation and looked over the implementation briefly. I'm only familiar with the internals of ThreadedChildWatcher.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Sat Oct 26 13:02:55 2019
From: report at bugs.python.org (Steve Dower)
Date: Sat, 26 Oct 2019 17:02:55 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572109375.84.0.56689226325.issue38589@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

If you look in your %TEMP% directory, you'll find a set of log files from your Python install (maybe sort by date).

One of these will end in "doc". Could you share that file?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Sat Oct 26 13:12:34 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Sat, 26 Oct 2019 17:12:34 +0000
Subject: [issue38591] Deprecate Process Child Watchers
In-Reply-To: <1572031409.68.0.540120244927.issue38591@roundup.psfhosted.org>
Message-ID: <1572109954.17.0.280718265206.issue38591@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> But it spawns a new Python thread per process which can be a blocker issue if a server memory is limited.

I understand that there's *some* overhead associated with spawning a new thread, but from my impression it's not substantial enough to make a significant impact in most cases. Each individual instance of threading.Thread is only 64 bytes. Have you seen any recent cases where the server memory is limited enough for the memory cost associated with having to spawn an additional thread per subprocess becomes the limiting factor?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38591>
_______________________________________

From report at bugs.python.org  Sat Oct 26 13:25:50 2019
From: report at bugs.python.org (Y3Kv Bv)
Date: Sat, 26 Oct 2019 17:25:50 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572110750.33.0.762736156233.issue38589@roundup.psfhosted.org>


Y3Kv Bv <yk3b.bw.ggxwkimobz at gmail.com> added the comment:

Here you go.

----------
Added file: https://bugs.python.org/file48679/Python 3.8.0 (64-bit)_20191026201510_005_doc_AllUsers.log

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Sat Oct 26 14:15:58 2019
From: report at bugs.python.org (Thomas Caswell)
Date: Sat, 26 Oct 2019 18:15:58 +0000
Subject: [issue37289] regression in Cython when pickling objects
In-Reply-To: <1560570212.11.0.192149114574.issue37289@roundup.psfhosted.org>
Message-ID: <1572113758.18.0.960927476643.issue37289@roundup.psfhosted.org>


Thomas Caswell <tcaswell at gmail.com> added the comment:

I believe this can be closed, the regression has been fixed and there is now a test to prevent it from coming back.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37289>
_______________________________________

From report at bugs.python.org  Sat Oct 26 14:33:49 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 26 Oct 2019 18:33:49 +0000
Subject: [issue38440] Possible new issues with IDLE
In-Reply-To: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>
Message-ID: <1572114829.99.0.614974845101.issue38440@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Reproducer for the jump-to-top bug:
* Start an IDLE interactive shell session
* Run:  File Save As tmp.py
* Press F5 to run the shell session (this is an error)

Effects:
* A message box with "Invalid Syntax" appears
* The cursor jumps to the top row and lands
  on the first "3" in:
  "Python 3.8.0 (v3.8.0:fa919fdf25, Oct 14 2019, 10:23:27) "

Suggestions:
* Don't have the cursor jump after "Invalid Syntax"
* Disable F5 for interactive prompt sessions

Impact:
* Students are saving their long-running shell sessions during class.  Occasionally, they press F5 to run a script but the interactive shell has the focus.  The "jump" described above is disruptive because it moves the cursor to the start of the session which may have occurred hours beforehand.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Sat Oct 26 15:48:20 2019
From: report at bugs.python.org (Kevin Schlossser)
Date: Sat, 26 Oct 2019 19:48:20 +0000
Subject: [issue38597] C Extension import limit
Message-ID: <1572119300.64.0.0138111717141.issue38597@roundup.psfhosted.org>


New submission from Kevin Schlossser <kevin.g.schlosser at gmail.com>:

System
Windows 7 x64 SP2
Ram 16GB
6 Core AMD @ 3.2ghz

CPython 3.7.2


C Extension (pyd) import cap.

There seems to be a cap on the number of extensions that a package is able to contain. I am able to import 123 extension modules that my package has but when i go to import number 124 i get the following traceback

ImportError: DLL load failed: A dynamic link library (DLL) initialization routine failed.

these extension modules are part of my package, importing an extension module from another package does not change this behavior. it is only when I import the 124th extension that is in my package does it occur. 

When I change the order of the imports the error does not follow the import. I end up getting the same error when the 124th extension gets loaded doesn't matter what extension it is. 

I have tried to see if maybe it was a module limit and I spread the imports across multiple files and it still fails when the 124th gets loaded. I also tried imp.load_dynamic and importlib.import_module and the same error occurs.

If there is a way to work around this limitation it would be very helpful.

----------
components: Extension Modules
messages: 355425
nosy: Kevin Schlossser
priority: normal
severity: normal
status: open
title: C Extension import limit
type: resource usage
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38597>
_______________________________________

From report at bugs.python.org  Sat Oct 26 15:49:52 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 19:49:52 +0000
Subject: [issue37289] regression in Cython when pickling objects
In-Reply-To: <1560570212.11.0.192149114574.issue37289@roundup.psfhosted.org>
Message-ID: <1572119392.8.0.944546396583.issue37289@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37289>
_______________________________________

From report at bugs.python.org  Sat Oct 26 15:52:26 2019
From: report at bugs.python.org (Steve Dower)
Date: Sat, 26 Oct 2019 19:52:26 +0000
Subject: [issue38434] sys.addaudithook event is not documented
In-Reply-To: <1570724703.62.0.219483741722.issue38434@roundup.psfhosted.org>
Message-ID: <1572119546.47.0.282189405178.issue38434@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords: +patch
pull_requests: +16461
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16932

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38434>
_______________________________________

From report at bugs.python.org  Sat Oct 26 15:59:22 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 19:59:22 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572119962.71.0.75277417375.issue38557@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset d898d20e8c228229eb68e545f544db13f246f216 by Serhiy Storchaka in branch 'master':
bpo-38557: Improve documentation for list and tuple C API. (GH-16925)
https://github.com/python/cpython/commit/d898d20e8c228229eb68e545f544db13f246f216


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Sat Oct 26 15:59:47 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 26 Oct 2019 19:59:47 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572119987.71.0.901670946606.issue38557@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16462
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16933

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Sat Oct 26 15:59:53 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 26 Oct 2019 19:59:53 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572119993.68.0.874168691874.issue38557@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16463
pull_request: https://github.com/python/cpython/pull/16934

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Sat Oct 26 16:00:00 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 26 Oct 2019 20:00:00 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572120000.05.0.57315644478.issue38557@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16464
pull_request: https://github.com/python/cpython/pull/16935

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Sat Oct 26 16:02:33 2019
From: report at bugs.python.org (Steve Dower)
Date: Sat, 26 Oct 2019 20:02:33 +0000
Subject: [issue38434] sys.addaudithook event is not documented
In-Reply-To: <1570724703.62.0.219483741722.issue38434@roundup.psfhosted.org>
Message-ID: <1572120153.71.0.175197302582.issue38434@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 894e30ce0bcc1c509eb01c8ffa9ba6d7701aeaaf by Steve Dower in branch 'master':
bpo-38434: Fixes some audit event documentation (GH-16932)
https://github.com/python/cpython/commit/894e30ce0bcc1c509eb01c8ffa9ba6d7701aeaaf


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38434>
_______________________________________

From report at bugs.python.org  Sat Oct 26 16:02:41 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 26 Oct 2019 20:02:41 +0000
Subject: [issue38434] sys.addaudithook event is not documented
In-Reply-To: <1570724703.62.0.219483741722.issue38434@roundup.psfhosted.org>
Message-ID: <1572120161.62.0.578285366566.issue38434@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16465
pull_request: https://github.com/python/cpython/pull/16936

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38434>
_______________________________________

From report at bugs.python.org  Sat Oct 26 16:03:46 2019
From: report at bugs.python.org (Steve Dower)
Date: Sat, 26 Oct 2019 20:03:46 +0000
Subject: [issue38434] sys.addaudithook event is not documented
In-Reply-To: <1570724703.62.0.219483741722.issue38434@roundup.psfhosted.org>
Message-ID: <1572120226.83.0.361473966479.issue38434@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38434>
_______________________________________

From report at bugs.python.org  Sat Oct 26 16:04:16 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 26 Oct 2019 20:04:16 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572120256.73.0.269722419202.issue38557@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 7356e10820b160d14b0ce0aba5427a8f9e757aa7 by Miss Skeleton (bot) in branch '2.7':
bpo-38557: Improve documentation for list and tuple C API. (GH-16925)
https://github.com/python/cpython/commit/7356e10820b160d14b0ce0aba5427a8f9e757aa7


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Sat Oct 26 16:05:21 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 26 Oct 2019 20:05:21 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572120321.26.0.865798748964.issue38557@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 334fc923b3a7a8d0d163692befd2a27b98b481df by Miss Skeleton (bot) in branch '3.7':
bpo-38557: Improve documentation for list and tuple C API. (GH-16925)
https://github.com/python/cpython/commit/334fc923b3a7a8d0d163692befd2a27b98b481df


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Sat Oct 26 16:06:37 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 26 Oct 2019 20:06:37 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572120397.58.0.991766302653.issue38557@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 4992dc6610fb354e36c0012a47ea9613b61c9038 by Miss Skeleton (bot) in branch '3.8':
bpo-38557: Improve documentation for list and tuple C API. (GH-16925)
https://github.com/python/cpython/commit/4992dc6610fb354e36c0012a47ea9613b61c9038


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Sat Oct 26 16:09:38 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 26 Oct 2019 20:09:38 +0000
Subject: [issue38434] sys.addaudithook event is not documented
In-Reply-To: <1570724703.62.0.219483741722.issue38434@roundup.psfhosted.org>
Message-ID: <1572120578.8.0.93985321992.issue38434@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 11f0f11c4859f5ca201cd40b379b13c65f05ec91 by Miss Skeleton (bot) in branch '3.8':
bpo-38434: Fixes some audit event documentation (GH-16932)
https://github.com/python/cpython/commit/11f0f11c4859f5ca201cd40b379b13c65f05ec91


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38434>
_______________________________________

From report at bugs.python.org  Sat Oct 26 16:16:34 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 20:16:34 +0000
Subject: [issue38597] C Extension import limit
In-Reply-To: <1572119300.64.0.0138111717141.issue38597@roundup.psfhosted.org>
Message-ID: <1572120994.96.0.0529568014438.issue38597@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
components: +Interpreter Core, Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38597>
_______________________________________

From report at bugs.python.org  Sat Oct 26 16:16:46 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 20:16:46 +0000
Subject: [issue38597] C Extension import limit
In-Reply-To: <1572119300.64.0.0138111717141.issue38597@roundup.psfhosted.org>
Message-ID: <1572121006.65.0.962825988454.issue38597@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
components:  -Extension Modules

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38597>
_______________________________________

From report at bugs.python.org  Sat Oct 26 17:03:56 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 26 Oct 2019 21:03:56 +0000
Subject: [issue38598] IDLE: Disable F5, etc, in Shell, even after saving
Message-ID: <1572123836.51.0.5425055858.issue38598@roundup.psfhosted.org>


New submission from Terry J. Reedy <tjreedy at udel.edu>:

When the Shell is active, the Run menu is disabled, but its shortcuts are not.  These are F5 Run Module, Shift-F5 Run ... Custom, and Alt-X Check Module.  If Shell has not been saved, the shortcuts do nothing, but once Shell has been saved, they try to compile the entire shell session.

The result is that the '3' in 'Python 3.8 ...' on the first line is highlighted as an error and the SyntaxError box pops up.  When the box is dismissed, the cursor is placed after the '3'.

Instead of calling compile, IDLE should beep and continue.

----------
assignee: terry.reedy
components: IDLE
messages: 355432
nosy: terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: IDLE: Disable F5, etc, in Shell, even after saving
type: behavior
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38598>
_______________________________________

From report at bugs.python.org  Sat Oct 26 17:12:30 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 21:12:30 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572124350.94.0.970514265316.issue38334@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16466
pull_request: https://github.com/python/cpython/pull/16937

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sat Oct 26 17:13:50 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 21:13:50 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572124430.84.0.0602811095849.issue38334@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

PR 16937 is simpler. It does not change the decrypter.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sat Oct 26 17:14:51 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2019 21:14:51 +0000
Subject: [issue38557] PyTuple_GetSlice docs minor inaccuracy
In-Reply-To: <1571759460.27.0.105772262724.issue38557@roundup.psfhosted.org>
Message-ID: <1572124491.2.0.156136390027.issue38557@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38557>
_______________________________________

From report at bugs.python.org  Sat Oct 26 17:45:36 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Sat, 26 Oct 2019 21:45:36 +0000
Subject: [issue38312] curses: add `set_tabsize` and `set_escdelay`
In-Reply-To: <1569721208.44.0.258918770799.issue38312@roundup.psfhosted.org>
Message-ID: <1572126336.75.0.66215871924.issue38312@roundup.psfhosted.org>


Change by Anthony Sottile <asottile at umich.edu>:


----------
keywords: +patch
pull_requests: +16467
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16938

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38312>
_______________________________________

From report at bugs.python.org  Sat Oct 26 18:25:26 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 26 Oct 2019 22:25:26 +0000
Subject: [issue38598] IDLE: Disable F5, etc, in Shell and Output windows.
In-Reply-To: <1572123836.51.0.5425055858.issue38598@roundup.psfhosted.org>
Message-ID: <1572128726.44.0.431515435584.issue38598@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Trying to compile grep output is also bad.  The ultimate fix is to subclass the specialized code editor from the general text editor, instead of vice versa as at present, but I leave that for later, and will simply check if the window about to be compiled is an instance of OutputWindow (which is also the PyShell superclass).

----------
title: IDLE: Disable F5, etc, in Shell, even after saving -> IDLE: Disable F5, etc, in Shell and Output windows.

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38598>
_______________________________________

From report at bugs.python.org  Sat Oct 26 18:26:24 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 26 Oct 2019 22:26:24 +0000
Subject: [issue38598] IDLE: Disable F5, etc, in Shell and Output windows.
In-Reply-To: <1572123836.51.0.5425055858.issue38598@roundup.psfhosted.org>
Message-ID: <1572128784.97.0.487613357916.issue38598@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
keywords: +patch
pull_requests: +16468
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/16939

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38598>
_______________________________________

From report at bugs.python.org  Sat Oct 26 18:28:25 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 26 Oct 2019 22:28:25 +0000
Subject: [issue38440] Possible new issues with IDLE
In-Reply-To: <1570768048.83.0.927013766779.issue38440@roundup.psfhosted.org>
Message-ID: <1572128905.67.0.198399146926.issue38440@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Given this, I reproduced the issue on Windows for both 3.7 and 3.8.  The bug is trying to compile the Shell window, after it has been saved, or an Output window, with a prompt to save, for any of F5, Shift-F5, and Alt-X.  There is no existing issue I know of, so I opened #38598 and added PR 16939.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38440>
_______________________________________

From report at bugs.python.org  Sat Oct 26 18:41:11 2019
From: report at bugs.python.org (Daniel Hillier)
Date: Sat, 26 Oct 2019 22:41:11 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572129671.01.0.0107363069562.issue38334@roundup.psfhosted.org>


Daniel Hillier <daniel.hillier at gmail.com> added the comment:

Thanks for looking at the PR.


I got carried away refactoring the decrypter for a future scenario where there could be different decrypters (possibly using certificates too) :) Your PR is much simpler.

Would you also be able to take a look at some other PRs I've submitted for zipfile. They are both pretty small changes:

https://bugs.python.org/issue36993
https://bugs.python.org/issue37523

Thanks again,
Dan

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sat Oct 26 20:54:46 2019
From: report at bugs.python.org (Javier Castillo II)
Date: Sun, 27 Oct 2019 00:54:46 +0000
Subject: [issue21622] ctypes.util incorrectly fails for libraries without
 DT_SONAME
In-Reply-To: <1401593302.24.0.994822187168.issue21622@psf.upfronthosting.co.za>
Message-ID: <1572137686.84.0.573658969956.issue21622@roundup.psfhosted.org>


Change by Javier Castillo II <j.castillo.2nd at gmail.com>:


----------
pull_requests: +16469
pull_request: https://github.com/python/cpython/pull/16940

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21622>
_______________________________________

From report at bugs.python.org  Sat Oct 26 21:15:26 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 01:15:26 +0000
Subject: [issue38598] IDLE: Disable F5, etc, in Shell and Output windows.
In-Reply-To: <1572123836.51.0.5425055858.issue38598@roundup.psfhosted.org>
Message-ID: <1572138926.17.0.210652093757.issue38598@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:


New changeset e3f90b217a5152275b180b466bd503658a734462 by Terry Jan Reedy in branch 'master':
bpo-38598: Do not try to compile IDLE shell or output windows (GH-16939)
https://github.com/python/cpython/commit/e3f90b217a5152275b180b466bd503658a734462


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38598>
_______________________________________

From report at bugs.python.org  Sat Oct 26 21:15:23 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 01:15:23 +0000
Subject: [issue38598] IDLE: Disable F5, etc, in Shell and Output windows.
In-Reply-To: <1572123836.51.0.5425055858.issue38598@roundup.psfhosted.org>
Message-ID: <1572138923.96.0.572270035763.issue38598@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16470
pull_request: https://github.com/python/cpython/pull/16941

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38598>
_______________________________________

From report at bugs.python.org  Sat Oct 26 21:22:20 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 01:22:20 +0000
Subject: [issue38598] IDLE: Disable F5, etc, in Shell and Output windows.
In-Reply-To: <1572123836.51.0.5425055858.issue38598@roundup.psfhosted.org>
Message-ID: <1572139340.0.0.867772605865.issue38598@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16471
pull_request: https://github.com/python/cpython/pull/16942

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38598>
_______________________________________

From report at bugs.python.org  Sat Oct 26 21:32:14 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 01:32:14 +0000
Subject: [issue38598] IDLE: Disable F5, etc, in Shell and Output windows.
In-Reply-To: <1572123836.51.0.5425055858.issue38598@roundup.psfhosted.org>
Message-ID: <1572139934.8.0.758529803648.issue38598@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 849b1b9f6c538085839f8059e0d6a5536d2fdb52 by Miss Skeleton (bot) in branch '3.7':
bpo-38598: Do not try to compile IDLE shell or output windows (GH-16939)
https://github.com/python/cpython/commit/849b1b9f6c538085839f8059e0d6a5536d2fdb52


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38598>
_______________________________________

From report at bugs.python.org  Sat Oct 26 21:37:08 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 01:37:08 +0000
Subject: [issue34162] idlelib/NEWS.txt for 3.8.0 (and backports)
In-Reply-To: <1532067299.29.0.56676864532.issue34162@psf.upfronthosting.co.za>
Message-ID: <1572140228.54.0.951773046947.issue34162@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests: +16472
pull_request: https://github.com/python/cpython/pull/16943

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34162>
_______________________________________

From report at bugs.python.org  Sat Oct 26 21:41:29 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 01:41:29 +0000
Subject: [issue38598] IDLE: Disable F5, etc, in Shell and Output windows.
In-Reply-To: <1572123836.51.0.5425055858.issue38598@roundup.psfhosted.org>
Message-ID: <1572140489.19.0.627855982493.issue38598@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset e3a477aa072a737d5119b0778d14d9f3ddb9f587 by Miss Skeleton (bot) in branch '3.8':
bpo-38598: Do not try to compile IDLE shell or output windows (GH-16939)
https://github.com/python/cpython/commit/e3a477aa072a737d5119b0778d14d9f3ddb9f587


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38598>
_______________________________________

From report at bugs.python.org  Sat Oct 26 21:42:09 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 01:42:09 +0000
Subject: [issue38598] IDLE: Disable F5, etc, in Shell and Output windows.
In-Reply-To: <1572123836.51.0.5425055858.issue38598@roundup.psfhosted.org>
Message-ID: <1572140529.17.0.0312100264251.issue38598@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38598>
_______________________________________

From report at bugs.python.org  Sat Oct 26 22:19:59 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 02:19:59 +0000
Subject: [issue34162] idlelib/NEWS.txt for 3.8.0 (and backports)
In-Reply-To: <1532067299.29.0.56676864532.issue34162@psf.upfronthosting.co.za>
Message-ID: <1572142799.9.0.255748093991.issue34162@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:


New changeset e31a79a5b44357b409d71949dc5308889970f9ab by Terry Jan Reedy in branch 'master':
bpo-34162: Last idlelib/NEWS.txt items for 3.8.0. (GH-16943)
https://github.com/python/cpython/commit/e31a79a5b44357b409d71949dc5308889970f9ab


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34162>
_______________________________________

From report at bugs.python.org  Sat Oct 26 22:20:11 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 02:20:11 +0000
Subject: [issue34162] idlelib/NEWS.txt for 3.8.0 (and backports)
In-Reply-To: <1532067299.29.0.56676864532.issue34162@psf.upfronthosting.co.za>
Message-ID: <1572142811.88.0.905506426627.issue34162@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16473
pull_request: https://github.com/python/cpython/pull/16944

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34162>
_______________________________________

From report at bugs.python.org  Sat Oct 26 22:20:19 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 02:20:19 +0000
Subject: [issue34162] idlelib/NEWS.txt for 3.8.0 (and backports)
In-Reply-To: <1532067299.29.0.56676864532.issue34162@psf.upfronthosting.co.za>
Message-ID: <1572142819.04.0.33468876903.issue34162@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16474
pull_request: https://github.com/python/cpython/pull/16945

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34162>
_______________________________________

From report at bugs.python.org  Sat Oct 26 22:22:19 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 02:22:19 +0000
Subject: [issue34162] idlelib/NEWS.txt for 3.8.0 (and backports)
In-Reply-To: <1532067299.29.0.56676864532.issue34162@psf.upfronthosting.co.za>
Message-ID: <1572142939.15.0.462492525487.issue34162@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34162>
_______________________________________

From report at bugs.python.org  Sat Oct 26 22:37:28 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 02:37:28 +0000
Subject: [issue34162] idlelib/NEWS.txt for 3.8.0 (and backports)
In-Reply-To: <1532067299.29.0.56676864532.issue34162@psf.upfronthosting.co.za>
Message-ID: <1572143848.47.0.0363230162541.issue34162@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 7a3b1a6f0b0a5ac6e9af4c5ee8b89a2fca96efb6 by Miss Skeleton (bot) in branch '3.8':
bpo-34162: Last idlelib/NEWS.txt items for 3.8.0. (GH-16943)
https://github.com/python/cpython/commit/7a3b1a6f0b0a5ac6e9af4c5ee8b89a2fca96efb6


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34162>
_______________________________________

From report at bugs.python.org  Sat Oct 26 22:38:29 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 02:38:29 +0000
Subject: [issue34162] idlelib/NEWS.txt for 3.8.0 (and backports)
In-Reply-To: <1532067299.29.0.56676864532.issue34162@psf.upfronthosting.co.za>
Message-ID: <1572143909.63.0.725449955387.issue34162@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset bc30db1ee70b6708aa436868e548aef919567448 by Miss Skeleton (bot) in branch '3.7':
bpo-34162: Last idlelib/NEWS.txt items for 3.8.0. (GH-16943)
https://github.com/python/cpython/commit/bc30db1ee70b6708aa436868e548aef919567448


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34162>
_______________________________________

From report at bugs.python.org  Sat Oct 26 23:00:59 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Sun, 27 Oct 2019 03:00:59 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572145259.46.0.803344728284.issue34790@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> Actually, since Andrew also agrees that we need to deprecate passing coroutines to wait(), I'll keep this issue open until we add an actual DeprecationWarning in 3.8.

Since 3.8 has been released and the deprecation notice is in the 3.8 whatsnew document, should we implement the warning in Lib/asyncio/tasks.py? If so, I can open a PR. 

> PendingDeprecationWarning

Also, it's not clear to me if this should be a DeprecationWarning or PendingDeprecationWarning. The most recent message from Yury in the issue suggests a PendingDeprecationWarning, but the actual entry in the documentation (https://docs.python.org/3/library/asyncio-task.html?highlight=asyncio%20wait#asyncio.wait) seems like it might imply that it would be a DeprecationWarning:

> Deprecated since version 3.8: If any awaitable in aws is a coroutine, it is automatically scheduled as a Task. Passing coroutines objects to wait() directly is deprecated as it leads to confusing behavior.

----------
nosy: +aeros
status: pending -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Sun Oct 27 00:49:46 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 04:49:46 +0000
Subject: [issue34162] idlelib/NEWS.txt for 3.8.0 (and backports)
In-Reply-To: <1532067299.29.0.56676864532.issue34162@psf.upfronthosting.co.za>
Message-ID: <1572151786.65.0.779514469284.issue34162@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34162>
_______________________________________

From report at bugs.python.org  Sun Oct 27 00:53:50 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 04:53:50 +0000
Subject: [issue37309] idlelib/NEWS.txt for 3.9.0 and backports
In-Reply-To: <1560723721.58.0.865881864361.issue37309@roundup.psfhosted.org>
Message-ID: <1572152030.7.0.931833346916.issue37309@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
keywords: +patch
pull_requests: +16475
stage: commit review -> patch review
pull_request: https://github.com/python/cpython/pull/16947

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37309>
_______________________________________

From report at bugs.python.org  Sun Oct 27 01:01:14 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 05:01:14 +0000
Subject: [issue37309] idlelib/NEWS.txt for 3.9.0 and backports
In-Reply-To: <1560723721.58.0.865881864361.issue37309@roundup.psfhosted.org>
Message-ID: <1572152474.49.0.932920795048.issue37309@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests: +16476
pull_request: https://github.com/python/cpython/pull/16948

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37309>
_______________________________________

From report at bugs.python.org  Sun Oct 27 01:04:40 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 05:04:40 +0000
Subject: [issue37309] idlelib/NEWS.txt for 3.9.0 and backports
In-Reply-To: <1560723721.58.0.865881864361.issue37309@roundup.psfhosted.org>
Message-ID: <1572152680.12.0.164617310734.issue37309@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests: +16477
pull_request: https://github.com/python/cpython/pull/16949

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37309>
_______________________________________

From report at bugs.python.org  Sun Oct 27 01:23:33 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 05:23:33 +0000
Subject: [issue37309] idlelib/NEWS.txt for 3.9.0 and backports
In-Reply-To: <1560723721.58.0.865881864361.issue37309@roundup.psfhosted.org>
Message-ID: <1572153813.55.0.328084810139.issue37309@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:


New changeset a8fb9327fb9387b404d4b6ce55c608125f66b9ae by Terry Jan Reedy in branch 'master':
bpo-37309: First idlelib/NEWS.txt for 3.9.0 (GH-16947)
https://github.com/python/cpython/commit/a8fb9327fb9387b404d4b6ce55c608125f66b9ae


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37309>
_______________________________________

From report at bugs.python.org  Sun Oct 27 01:25:30 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 05:25:30 +0000
Subject: [issue37309] idlelib/NEWS.txt for 3.9.0 and backports
In-Reply-To: <1560723721.58.0.865881864361.issue37309@roundup.psfhosted.org>
Message-ID: <1572153930.3.0.348562221716.issue37309@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:


New changeset 6d6418a075f272aeab93c6f2ec15c10257b94e1d by Terry Jan Reedy in branch '3.8':
[3.8] bpo-37309: First idlelib/NEWS.txt for 3.8.1 (GH-16947)
https://github.com/python/cpython/commit/6d6418a075f272aeab93c6f2ec15c10257b94e1d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37309>
_______________________________________

From report at bugs.python.org  Sun Oct 27 01:53:24 2019
From: report at bugs.python.org (Daniel Hillier)
Date: Sun, 27 Oct 2019 05:53:24 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572155604.94.0.632035189748.issue38334@roundup.psfhosted.org>


Daniel Hillier <daniel.hillier at gmail.com> added the comment:

I also think that the `read_init` method in my PR is a useful refactor as it locates all the state that needs to be (re)set when starting a read into the same location.

At the moment this state is set in 1) __init__ and 2) the seek method when seeking back beyond what is in the buffer.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sun Oct 27 02:38:23 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 27 Oct 2019 06:38:23 +0000
Subject: [issue37309] idlelib/NEWS.txt for 3.9.0 and backports
In-Reply-To: <1560723721.58.0.865881864361.issue37309@roundup.psfhosted.org>
Message-ID: <1572158303.83.0.651439021083.issue37309@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:


New changeset baf2657eff82f5c33ae8194499d97ba963871655 by Terry Jan Reedy in branch '3.7':
[3.7] bpo-37309: First idlelib/NEWS.txt for 3.7.6 (GH-) (#16949)
https://github.com/python/cpython/commit/baf2657eff82f5c33ae8194499d97ba963871655


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37309>
_______________________________________

From report at bugs.python.org  Sun Oct 27 03:01:58 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sun, 27 Oct 2019 07:01:58 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572159718.16.0.511409582497.issue34790@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

I think we can add `DeprecationWarning` for 3.9.

Since it is a) just a warning b) already marked as deprecated in docs -- the harm is minimal.

Honestly, we just missed the issue when were prepared for 3.8

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Sun Oct 27 03:08:05 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sun, 27 Oct 2019 07:08:05 +0000
Subject: [issue38599] Deprecate creation of asyncio object when the loop is
 not running
Message-ID: <1572160085.79.0.39835517746.issue38599@roundup.psfhosted.org>


New submission from Andrew Svetlov <andrew.svetlov at gmail.com>:

Consider the following code:

import asyncio

q = asyncio.Queue()

async def main():
    await asyncio.gather(q.put(1), q.get(1))

asyncio.run(main())


This code just hangs since run() creates a loop but queue is bound with another (default) event loop.

The error is confusing and hard-to-debug.

We should raise a warning at least for the case; start from DeprecationWarning and make the system stricter later.

asyncio/locks.py is also affected since it has first-class classes (classes that instantiated by a user directly without factories).

----------
components: asyncio
messages: 355449
nosy: asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: Deprecate creation of asyncio object when the loop is not running
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38599>
_______________________________________

From report at bugs.python.org  Sun Oct 27 03:25:51 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Sun, 27 Oct 2019 07:25:51 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572161151.82.0.039178476058.issue34790@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> I think we can add `DeprecationWarning` for 3.9.

If we add the deprecation warning just for 3.9, would the removal release also be pushed forward? 

> Honestly, we just missed the issue when were prepared for 3.8

Yeah that's definitely understandable, there were quite a number of major changes made in 3.8. It was the first time I saw a deprecation clearly documented in a final release that didn't have an associated deprecation warning. 

As for 3.8, I would like to update the whatsnew entry to add a link to this bpo issue if that's okay, as it does not at the moment. I recently included the entry in a PR that added entries for multiple significant changes for asyncio in the 3.8, but I forgot to include the bpo link (mostly because I found it in the documentation, rather than from the bpo issue).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Sun Oct 27 03:32:13 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Sun, 27 Oct 2019 07:32:13 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572161533.43.0.484921065958.issue34790@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> It was the first time I saw a deprecation clearly documented in a final release that didn't have an associated deprecation warning. 

I want to clarify that this may be a more common occurrence than I'm realizing, I'm not entirely certain. Also it's not intended at all as a criticism, it just surprised me since it was the first time I saw it happen.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:16:09 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2019 08:16:09 +0000
Subject: [issue38600] Change the mark up of NULL
Message-ID: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

Currently NULL is mostly marked up as *NULL* in the C API documentation (although it is marked up as ``NULL`` outside of the C API documentation). It is rendered with italic font as function parameters and contradicts with formatting other macros and constants with monospace font.

The proposed PR replaces all *NULL* with ``NULL``.

----------
assignee: docs at python
components: Documentation
messages: 355452
nosy: docs at python, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Change the mark up of NULL
type: enhancement
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:18:45 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2019 08:18:45 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572164325.42.0.295670007176.issue38600@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16478
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16950

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:22:19 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2019 08:22:19 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572164539.71.0.675203258514.issue38334@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 5c32af7522d908e8c7da0243af37618433289cc5 by Serhiy Storchaka in branch 'master':
bpo-38334: Fix seeking backward on an encrypted zipfile.ZipExtFile. (GH-16937)
https://github.com/python/cpython/commit/5c32af7522d908e8c7da0243af37618433289cc5


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:22:44 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 08:22:44 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572164564.42.0.971658088427.issue38334@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16479
pull_request: https://github.com/python/cpython/pull/16951

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:22:51 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 08:22:51 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572164571.86.0.577916577202.issue38334@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16480
pull_request: https://github.com/python/cpython/pull/16952

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:30:15 2019
From: report at bugs.python.org (Julien Palard)
Date: Sun, 27 Oct 2019 08:30:15 +0000
Subject: [issue38592] Add pt-br to the language switcher at the Python docs
 website
In-Reply-To: <1572034700.82.0.68590075216.issue38592@roundup.psfhosted.org>
Message-ID: <1572165015.5.0.235044385314.issue38592@roundup.psfhosted.org>


Julien Palard <julien+python at palard.fr> added the comment:


New changeset 85c6f8c65cd4f7219522c1f304bdfff19f785e7a by Julien Palard (Marco Rougeth) in branch 'master':
bpo-38592 Add pt-br switcher to Python Docs website (GH-16924)
https://github.com/python/cpython/commit/85c6f8c65cd4f7219522c1f304bdfff19f785e7a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38592>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:30:23 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 08:30:23 +0000
Subject: [issue38592] Add pt-br to the language switcher at the Python docs
 website
In-Reply-To: <1572034700.82.0.68590075216.issue38592@roundup.psfhosted.org>
Message-ID: <1572165023.76.0.0704819113561.issue38592@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16481
pull_request: https://github.com/python/cpython/pull/16953

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38592>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:30:29 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 08:30:29 +0000
Subject: [issue38592] Add pt-br to the language switcher at the Python docs
 website
In-Reply-To: <1572034700.82.0.68590075216.issue38592@roundup.psfhosted.org>
Message-ID: <1572165029.92.0.896233591064.issue38592@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16482
pull_request: https://github.com/python/cpython/pull/16954

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38592>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:40:47 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 08:40:47 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572165647.64.0.726932560881.issue38334@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 76fbdaa2a693caaa1b8eb34104720fc774ff80df by Miss Skeleton (bot) in branch '3.8':
bpo-38334: Fix seeking backward on an encrypted zipfile.ZipExtFile. (GH-16937)
https://github.com/python/cpython/commit/76fbdaa2a693caaa1b8eb34104720fc774ff80df


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:41:30 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 27 Oct 2019 08:41:30 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572165690.54.0.433344626046.issue38334@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset ed2db3113d54a5f8af1b419a9f5fdf3642285c82 by Miss Skeleton (bot) in branch '3.7':
bpo-38334: Fix seeking backward on an encrypted zipfile.ZipExtFile. (GH-16937)
https://github.com/python/cpython/commit/ed2db3113d54a5f8af1b419a9f5fdf3642285c82


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sun Oct 27 04:47:50 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sun, 27 Oct 2019 08:47:50 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572166070.59.0.244129300307.issue34790@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

> If we add the deprecation warning just for 3.9, would the removal release also be pushed forward? 

Yes, deprecating in 3.9 with removal in 3.11 is fine.

Regarding 3.8 release notes update -- not sure if it is needed flr docs-only change.

In the current situation, we have so-called *soft deprecation*: bare coroutines are deprecated in docs without any code change. This is perfectly fine, we give our users extra time to prepare for changes.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Sun Oct 27 05:18:00 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2019 09:18:00 +0000
Subject: [issue37523] zipfile: Raise ValueError for i/o operations on closed
 zipfile.ZipExtFile
In-Reply-To: <1562656011.62.0.508019848995.issue37523@roundup.psfhosted.org>
Message-ID: <1572167880.73.0.553612950504.issue37523@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Could you please test what performance effect it has on read()?

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37523>
_______________________________________

From report at bugs.python.org  Sun Oct 27 06:11:18 2019
From: report at bugs.python.org (Julien Palard)
Date: Sun, 27 Oct 2019 10:11:18 +0000
Subject: [issue38592] Add pt-br to the language switcher at the Python docs
 website
In-Reply-To: <1572034700.82.0.68590075216.issue38592@roundup.psfhosted.org>
Message-ID: <1572171078.81.0.182520145515.issue38592@roundup.psfhosted.org>


Julien Palard <julien+python at palard.fr> added the comment:


New changeset 955f96f6aae7c1a54d88c3f7a51c2e142ac7e4d4 by Julien Palard (Miss Skeleton (bot)) in branch '3.8':
bpo-38592 Add pt-br switcher to Python Docs website (GH-16924) (GH-16953)
https://github.com/python/cpython/commit/955f96f6aae7c1a54d88c3f7a51c2e142ac7e4d4


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38592>
_______________________________________

From report at bugs.python.org  Sun Oct 27 06:13:13 2019
From: report at bugs.python.org (Julien Palard)
Date: Sun, 27 Oct 2019 10:13:13 +0000
Subject: [issue38592] Add pt-br to the language switcher at the Python docs
 website
In-Reply-To: <1572034700.82.0.68590075216.issue38592@roundup.psfhosted.org>
Message-ID: <1572171193.45.0.314526433908.issue38592@roundup.psfhosted.org>


Julien Palard <julien+python at palard.fr> added the comment:


New changeset 155a9dc129c129270763525cd3eb2704990e406d by Julien Palard (Miss Skeleton (bot)) in branch '3.7':
bpo-38592 Add pt-br switcher to Python Docs website (GH-16924) (GH-16954)
https://github.com/python/cpython/commit/155a9dc129c129270763525cd3eb2704990e406d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38592>
_______________________________________

From report at bugs.python.org  Sun Oct 27 06:19:02 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2019 10:19:02 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572171542.34.0.659832025604.issue38334@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

> I got carried away refactoring the decrypter for a future scenario where there could be different decrypters (possibly using certificates too) :)

The decrypter was implemented with a generator for performance. The performance of decrypting is not critical, but this got us 2x speed up without complicating the code. See issue10030. If the support of other decrypters be added, they will likely be implemented in C in any case.

> I also think that the `read_init` method in my PR is a useful refactor as it locates all the state that needs to be (re)set when starting a read into the same location.

This is a different issue.

> Would you also be able to take a look at some other PRs I've submitted for zipfile.

Thank you, they look good to me. I left just few comments.

As for the original issue, I have doubts that backward seeking in a compressed file is a good idea. But this feature was added, and it worked with encrypted files if seek in the range of the buffer, so not working out of the range of the buffer is a bug which we should fix.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type: enhancement -> behavior
versions: +Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Sun Oct 27 06:22:07 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2019 10:22:07 +0000
Subject: [issue24430] ZipFile.read() cannot decrypt multiple members from
 Windows 7zFM
In-Reply-To: <1434030821.12.0.415764944762.issue24430@psf.upfronthosting.co.za>
Message-ID: <1572171727.09.0.92977639979.issue24430@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24430>
_______________________________________

From report at bugs.python.org  Sun Oct 27 08:07:16 2019
From: report at bugs.python.org (Lewis Gaul)
Date: Sun, 27 Oct 2019 12:07:16 +0000
Subject: [issue38351] Modernize email example from %-formatting to f-string
In-Reply-To: <1570034736.68.0.500723145519.issue38351@roundup.psfhosted.org>
Message-ID: <1572178036.85.0.795900062392.issue38351@roundup.psfhosted.org>


Lewis Gaul <lewis.gaul at gmail.com> added the comment:

Hi all, I'm a newcomer interested in making this small fix, but it looks like this has become a bit of a contentious issue. Are there any advances on whether this is a desirable fix?

----------
nosy: +Lewis Gaul

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38351>
_______________________________________

From report at bugs.python.org  Sun Oct 27 08:09:24 2019
From: report at bugs.python.org (Kiran Kumar Kotari)
Date: Sun, 27 Oct 2019 12:09:24 +0000
Subject: [issue38601] Couldn't able to install multiple python minor version
 in windows
Message-ID: <1572178164.18.0.338058343246.issue38601@roundup.psfhosted.org>


New submission from Kiran Kumar Kotari <kirankotari at live.com>:

Today, Python 2.x/3.x Windows installation script is check for any python minor versions installed from the same train and updating it. This creates a problem of checking the project features. We solved multi-trains like 3.5 and 3.6 installation using pyenv-win but the minor version was a problem due to EXE file validation before installation and if any it updates the same. 

Can you please help us on updating the EXE script to with 
 - validate the minor versions by default
 - off the validate the minor version on installation

This feature helps us with minor version validation.

----------
components: Installation
messages: 355463
nosy: kkotari
priority: normal
severity: normal
status: open
title: Couldn't able to install multiple python minor version in windows
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38601>
_______________________________________

From report at bugs.python.org  Sun Oct 27 08:10:15 2019
From: report at bugs.python.org (Kiran Kumar Kotari)
Date: Sun, 27 Oct 2019 12:10:15 +0000
Subject: [issue38601] Couldn't able to install multiple python minor version
 in windows due to EXE script
In-Reply-To: <1572178164.18.0.338058343246.issue38601@roundup.psfhosted.org>
Message-ID: <1572178215.02.0.44422927309.issue38601@roundup.psfhosted.org>


Change by Kiran Kumar Kotari <kirankotari at live.com>:


----------
title: Couldn't able to install multiple python minor version in windows -> Couldn't able to install multiple python minor version in windows due to EXE script

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38601>
_______________________________________

From report at bugs.python.org  Sun Oct 27 08:47:11 2019
From: report at bugs.python.org (Benjamin Edwards)
Date: Sun, 27 Oct 2019 12:47:11 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1572180431.92.0.683104884896.issue38534@roundup.psfhosted.org>


Change by Benjamin Edwards <benjaminedwards at live.co.uk>:


----------
pull_requests: +16483
pull_request: https://github.com/python/cpython/pull/16955

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Sun Oct 27 09:06:13 2019
From: report at bugs.python.org (Benjamin Edwards)
Date: Sun, 27 Oct 2019 13:06:13 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1572181573.81.0.961847815259.issue38534@roundup.psfhosted.org>


Benjamin Edwards <benjaminedwards at live.co.uk> added the comment:

Have made a new PR, am just waiting for my CLA to be approved.

----------
nosy: +benedwards14

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Sun Oct 27 09:23:22 2019
From: report at bugs.python.org (Benjamin Edwards)
Date: Sun, 27 Oct 2019 13:23:22 +0000
Subject: [issue38314] Implement unix read_pipe.is_reading() method
In-Reply-To: <1569756133.59.0.955288942116.issue38314@roundup.psfhosted.org>
Message-ID: <1572182602.96.0.853842312404.issue38314@roundup.psfhosted.org>


Benjamin Edwards <benjaminedwards at live.co.uk> added the comment:

Shubham are you still interested in this, or are you ok with me taking it on?

----------
nosy: +benedwards14

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38314>
_______________________________________

From report at bugs.python.org  Sun Oct 27 09:27:03 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sun, 27 Oct 2019 13:27:03 +0000
Subject: [issue38602] Add fcntl.F_OFD_XXXX constant
Message-ID: <1572182823.74.0.700361916573.issue38602@roundup.psfhosted.org>


New submission from Dong-hee Na <donghee.na92 at gmail.com>:

Since Linux 3.15 is released.
fcntl.F_OFD_XXXX is used for python code.
It can be found on GitHub.
(https://github.com/ceph/ceph/blob/41d3fdc554ce920a631c7c6699a383134173fcff/qa/workunits/fs/misc/filelock_interrupt.py#L13)

I am working on this issue.

----------
components: Library (Lib)
messages: 355466
nosy: corona10, serhiy.storchaka, vstinner
priority: normal
severity: normal
status: open
title: Add fcntl.F_OFD_XXXX constant
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38602>
_______________________________________

From report at bugs.python.org  Sun Oct 27 09:27:15 2019
From: report at bugs.python.org (Benjamin Edwards)
Date: Sun, 27 Oct 2019 13:27:15 +0000
Subject: [issue17306] Improve the way abstract base classes are shown in help()
In-Reply-To: <1361932149.15.0.421194254516.issue17306@psf.upfronthosting.co.za>
Message-ID: <1572182835.94.0.411791795359.issue17306@roundup.psfhosted.org>


Benjamin Edwards <benjaminedwards at live.co.uk> added the comment:

Michael are you still interested in doing this, if not can I take it on?

----------
nosy: +benedwards14

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17306>
_______________________________________

From report at bugs.python.org  Sun Oct 27 09:31:24 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Sun, 27 Oct 2019 13:31:24 +0000
Subject: [issue38602] Add fcntl.F_OFD_XXXX constant
In-Reply-To: <1572182823.74.0.700361916573.issue38602@roundup.psfhosted.org>
Message-ID: <1572183084.53.0.184876892912.issue38602@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
keywords: +patch
pull_requests: +16484
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16956

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38602>
_______________________________________

From report at bugs.python.org  Sun Oct 27 10:26:02 2019
From: report at bugs.python.org (Lewis Gaul)
Date: Sun, 27 Oct 2019 14:26:02 +0000
Subject: [issue21002] _sre.SRE_Scanner object should have a fullmatch() method
In-Reply-To: <1395365477.75.0.293934412072.issue21002@psf.upfronthosting.co.za>
Message-ID: <1572186362.88.0.956391379861.issue21002@roundup.psfhosted.org>


Lewis Gaul <lewis.gaul at gmail.com> added the comment:

Scanner is not documented in CPython's own re documentation: https://docs.python.org/3/library/re.html#regular-expression-objects, so I'd say there's no obligation to maintain consistency with public APIs.

Is anyone able to make a call on whether this issue should be closed, or alternatively give some guidance on what work this issue should encompass?

----------
nosy: +Lewis Gaul

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21002>
_______________________________________

From report at bugs.python.org  Sun Oct 27 10:55:17 2019
From: report at bugs.python.org (Benjamin Edwards)
Date: Sun, 27 Oct 2019 14:55:17 +0000
Subject: [issue16142] ArgumentParser inconsistent with parse_known_args
In-Reply-To: <1349448801.58.0.783623579173.issue16142@psf.upfronthosting.co.za>
Message-ID: <1572188117.06.0.686002932664.issue16142@roundup.psfhosted.org>


Benjamin Edwards <benjaminedwards at live.co.uk> added the comment:

Hey this has been open for quite a while, is there anything that needs finishing off?

----------
nosy: +benedwards14

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16142>
_______________________________________

From report at bugs.python.org  Sun Oct 27 11:06:42 2019
From: report at bugs.python.org (Benjamin Edwards)
Date: Sun, 27 Oct 2019 15:06:42 +0000
Subject: [issue15243] Misleading documentation for __prepare__
In-Reply-To: <1341328118.33.0.670602196671.issue15243@psf.upfronthosting.co.za>
Message-ID: <1572188802.32.0.695239375169.issue15243@roundup.psfhosted.org>


Benjamin Edwards <benjaminedwards at live.co.uk> added the comment:

Is this still open, does the patch still need a pull request?

----------
nosy: +benedwards14

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue15243>
_______________________________________

From report at bugs.python.org  Sun Oct 27 11:14:56 2019
From: report at bugs.python.org (Lewis Gaul)
Date: Sun, 27 Oct 2019 15:14:56 +0000
Subject: [issue23692] Undocumented feature prevents re module from finding
 certain matches
In-Reply-To: <1426618184.57.0.811463464384.issue23692@psf.upfronthosting.co.za>
Message-ID: <1572189296.56.0.538866650381.issue23692@roundup.psfhosted.org>


Lewis Gaul <lewis.gaul at gmail.com> added the comment:

Hi there, if anyone's able to provide any guidance on this issue I'd be happy to take a look into it.

Is this a behaviour that is feasible to fix, or should this just be documented in some way as suggested by Evgeny?

----------
nosy: +Lewis Gaul

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23692>
_______________________________________

From report at bugs.python.org  Sun Oct 27 11:24:34 2019
From: report at bugs.python.org (Antony Lee)
Date: Sun, 27 Oct 2019 15:24:34 +0000
Subject: [issue38603] inspect.getdoc could examine the __class__ cell for
 dynamically generated subclasses
Message-ID: <1572189874.33.0.728183278975.issue38603@roundup.psfhosted.org>


New submission from Antony Lee <anntzer.lee at gmail.com>:

Currently, `inspect.getdoc()` fails to inherit docstrings in dynamically generated subclasses, such as
```
class Base:
    def method(self): "some docstring"

def make_subclass():
    class subclass(Base):
        def method(self): return super().method()
    return subclass

subclass = make_subclass()
inspect.getdoc(subclass.method)  # => returns None
```
because `inspect._findclass()` tries to find the base class by parsing `subclass.method.__qualname__` which is `"make_subclass.<locals>.subclass.method"` and chokes over `.<locals>.`.

In the case where the method does rely on `super()`, there is another way we can go back to the "owning" class of the method: by looking up the contents of the `__class__` cell (which is set up to make 0-arg super()).

Perhaps a `__class__` cell could even be set up for *all* methods defined in dynamically created subclasses (i.e. whose `__qualname__` includes `.<locals>.`), to help with introspection?

----------
components: Library (Lib)
messages: 355472
nosy: Antony.Lee
priority: normal
severity: normal
status: open
title: inspect.getdoc could examine the __class__ cell for dynamically generated subclasses
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38603>
_______________________________________

From report at bugs.python.org  Sun Oct 27 11:28:37 2019
From: report at bugs.python.org (Antony Lee)
Date: Sun, 27 Oct 2019 15:28:37 +0000
Subject: [issue38603] inspect.getdoc could examine the __class__ cell for
 dynamically generated subclasses
In-Reply-To: <1572189874.33.0.728183278975.issue38603@roundup.psfhosted.org>
Message-ID: <1572190117.36.0.0405666898492.issue38603@roundup.psfhosted.org>


Change by Antony Lee <anntzer.lee at gmail.com>:


----------
keywords: +patch
pull_requests: +16485
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16957

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38603>
_______________________________________

From report at bugs.python.org  Sun Oct 27 11:32:36 2019
From: report at bugs.python.org (Lewis Gaul)
Date: Sun, 27 Oct 2019 15:32:36 +0000
Subject: [issue22491] Support Unicode line boundaries in regular expression
In-Reply-To: <1411628187.04.0.177569242065.issue22491@psf.upfronthosting.co.za>
Message-ID: <1572190356.89.0.600925603864.issue22491@roundup.psfhosted.org>


Lewis Gaul <lewis.gaul at gmail.com> added the comment:

Hi there, I'm running 'EnHackathon' in a couple of weeks, and was wondering if this could be a good issue for a small team of first-time contributors with experience in C to work on.

Would anyone be able to offer any guidance for where to start in Modules/_sre.c?

----------
nosy: +Lewis Gaul

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22491>
_______________________________________

From report at bugs.python.org  Sun Oct 27 11:44:27 2019
From: report at bugs.python.org (TROUVERIE Joachim)
Date: Sun, 27 Oct 2019 15:44:27 +0000
Subject: [issue29612] TarFile.extract() suffers from hard links inside tarball
In-Reply-To: <1487671846.82.0.103027933595.issue29612@psf.upfronthosting.co.za>
Message-ID: <1572191067.23.0.171044076492.issue29612@roundup.psfhosted.org>


Change by TROUVERIE Joachim <joachim.trouverie at linoame.fr>:


----------
pull_requests: +16486
pull_request: https://github.com/python/cpython/pull/16958

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29612>
_______________________________________

From report at bugs.python.org  Sun Oct 27 11:49:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 27 Oct 2019 15:49:30 +0000
Subject: [issue37330] open(): remove 'U' mode, deprecated since Python 3.3
In-Reply-To: <1560872905.7.0.609892598407.issue37330@roundup.psfhosted.org>
Message-ID: <1572191370.12.0.174612641078.issue37330@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16487
pull_request: https://github.com/python/cpython/pull/16959

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37330>
_______________________________________

From report at bugs.python.org  Sun Oct 27 11:56:48 2019
From: report at bugs.python.org (Benjamin Edwards)
Date: Sun, 27 Oct 2019 15:56:48 +0000
Subject: [issue18765] unittest needs a way to launch pdb.post_mortem or other
 debug hooks
In-Reply-To: <1376696752.64.0.473845221037.issue18765@psf.upfronthosting.co.za>
Message-ID: <1572191808.01.0.0757779092591.issue18765@roundup.psfhosted.org>


Benjamin Edwards <benjaminedwards at live.co.uk> added the comment:

Hi R?mi, I'd also be happy to take a look at your problem, if it's still open, do you have patch of what you've done so far?

----------
nosy: +benedwards14

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue18765>
_______________________________________

From report at bugs.python.org  Sun Oct 27 12:02:05 2019
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 27 Oct 2019 16:02:05 +0000
Subject: [issue38604] Schedule Py_UNICODE API removal
Message-ID: <1572192125.35.0.636716899488.issue38604@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

Python 3.3 deprecated the C API functions using Py_UNICODE type. Examples in the doc:

* https://docs.python.org/dev/c-api/unicode.html#c.Py_UNICODE
* https://docs.python.org/dev/c-api/unicode.html#deprecated-py-unicode-apis

Currently, functions removal is scheduled for Python 4.0 but I would prefer that Python 4.0 doesn't have a long list of removed features, but no more than usual. So I'm trying to remove a few functions from Python 3.9, and try to prepare removal for others.

Py_UNICODE C API was mostly kept for backward compatibility with Python 2. Since Python 2 support ends at the end of the year, can we start to organize Py_UNICODE C API removal?

There are multiple questions:

* Should we drop the whole API at once? Or can we/should we start by removing a few functions, and then the others?
* Deprecation warnings are emitted at compilation. But I'm not aware of DeprecationWarning emited at runtime. IMHO we should emit DesprecationWarning at runtime during at least one release, so most developers ignore compilation warnings.

I propose to:

* (Right now) write an exhaustive list of all deprecated APIs: functions, constants, types, etc.
* Modify C code to emit DeprecationWarning at runtime in Python 3.9
* Experiment a modified Python without these APIs and test how many projects are broken by this removal: see PEP 608
* Schedule the actual removal of all these APIS from Python 3.10

Honestly, if the removal is causing too much issues, I'm fine to make slowdown the removal. It's just a matter of clearly communicating our intent.

Maybe we should also announce the scheduled removal in What's in Python 3.9 and in the capi-sig mailing list.

----------
components: Library (Lib)
messages: 355475
nosy: vstinner
priority: normal
severity: normal
status: open
title: Schedule Py_UNICODE API removal
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38604>
_______________________________________

From report at bugs.python.org  Sun Oct 27 12:07:10 2019
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 27 Oct 2019 16:07:10 +0000
Subject: [issue38605] [typing] PEP 563: Postponed evaluation of annotations:
 enable it by default before Python 4.0
Message-ID: <1572192430.43.0.755831692199.issue38605@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

The PEP 563: Postponed evaluation of annotations was introduced an opt-in feature using "from __future__ import annotations". It is scheduled to become the default in Python 4.0.

I would prefer to limit the number of incompatible changes in Python 4.0: it should just a "regular" release, with a regular number of incompatible changes. The version number change is going to cause enough troubles...

Would it be possible possible to enable postponed evaluation of annotations either before or after Python 4.0? For example, can we imagine to enable it by default in Python 3.9? If not, what about Python 3.10?

See also the PEP 608 (Coordinated Python release) and bpo-38604 (Schedule Py_UNICODE API removal).

----------
components: Library (Lib)
messages: 355476
nosy: lukasz.langa, vstinner
priority: normal
severity: normal
status: open
title: [typing] PEP 563: Postponed evaluation of annotations: enable it by default before Python 4.0
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38605>
_______________________________________

From report at bugs.python.org  Sun Oct 27 12:13:33 2019
From: report at bugs.python.org (Benjamin Edwards)
Date: Sun, 27 Oct 2019 16:13:33 +0000
Subject: [issue37838] typing.get_type_hints not working with
 forward-declaration and decorated functions
In-Reply-To: <1565692979.16.0.678723196671.issue37838@roundup.psfhosted.org>
Message-ID: <1572192813.26.0.946578203622.issue37838@roundup.psfhosted.org>


Benjamin Edwards <benjaminedwards at live.co.uk> added the comment:

Hey Netzeband, are you still working on this, or would it be ok for me to have a go? 

If all you needed was help with a PR let me know, i have some experience?

----------
nosy: +benedwards14

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37838>
_______________________________________

From report at bugs.python.org  Sun Oct 27 12:15:56 2019
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 27 Oct 2019 16:15:56 +0000
Subject: [issue38604] Schedule Py_UNICODE API removal
In-Reply-To: <1572192125.35.0.636716899488.issue38604@roundup.psfhosted.org>
Message-ID: <1572192956.9.0.665945669721.issue38604@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> (Right now) write an exhaustive list of all deprecated APIs: functions, constants, types, etc.

I searched "4.0" in the documentation:

* Py_UNICODE type
* array.array: "u" type
* PyArg_ParseTuple, Py_BuildValue: "u", "u#", "Z", "Z#" formats

* PyUnicode_FromUnicode()
* PyUnicode_GetSize(), PyUnicode_GET_SIZE()
* PyUnicode_AsUnicode(), PyUnicode_AS_UNICODE(), PyUnicode_AS_DATA()
* PyUnicode_AsUnicodeAndSize()
* PyUnicode_AsUnicodeCopy()

* PyUnicode_FromObject()
* PyLong_FromUnicode()
* PyUnicode_TransformDecimalToASCII()

* PyUnicode_Encode()
* PyUnicode_EncodeUTF7()
* PyUnicode_EncodeUTF8()
* PyUnicode_EncodeUTF32()
* PyUnicode_EncodeUTF16()
* PyUnicode_EncodeUnicodeEscape()
* PyUnicode_EncodeRawUnicodeEscape()
* PyUnicode_EncodeLatin1()
* PyUnicode_EncodeASCII()
* PyUnicode_EncodeMBCS()
* PyUnicode_EncodeCharmap()
* PyUnicode_TranslateCharmap()

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38604>
_______________________________________

From report at bugs.python.org  Sun Oct 27 12:16:48 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 27 Oct 2019 16:16:48 +0000
Subject: [issue38605] [typing] PEP 563: Postponed evaluation of annotations:
 enable it by default before Python 4.0
In-Reply-To: <1572192430.43.0.755831692199.issue38605@roundup.psfhosted.org>
Message-ID: <1572193008.13.0.261088813991.issue38605@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +levkivskyi

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38605>
_______________________________________

From report at bugs.python.org  Sun Oct 27 12:17:16 2019
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 27 Oct 2019 16:17:16 +0000
Subject: [issue37330] open(): remove 'U' mode, deprecated since Python 3.3
In-Reply-To: <1560872905.7.0.609892598407.issue37330@roundup.psfhosted.org>
Message-ID: <1572193036.26.0.649650648982.issue37330@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I cited this change in the PEP 608 "Coordinated Python release".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37330>
_______________________________________

From report at bugs.python.org  Sun Oct 27 12:17:44 2019
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 27 Oct 2019 16:17:44 +0000
Subject: [issue32354] Unclear intention of deprecating Py_UNICODE_TOLOWER /
 Py_UNICODE_TOUPPER
In-Reply-To: <1513562412.88.0.213398074469.issue32354@psf.upfronthosting.co.za>
Message-ID: <1572193064.81.0.452551883933.issue32354@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

See also bpo-38604: Schedule Py_UNICODE API removal.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32354>
_______________________________________

From report at bugs.python.org  Sun Oct 27 12:38:07 2019
From: report at bugs.python.org (Ron Frederick)
Date: Sun, 27 Oct 2019 16:38:07 +0000
Subject: [issue38529] Python 3.8 improperly warns about closing properly
 closed streams
In-Reply-To: <1571510429.0.0.996597968813.issue38529@roundup.psfhosted.org>
Message-ID: <1572194287.65.0.0101744654775.issue38529@roundup.psfhosted.org>


Ron Frederick <ronf at timeheart.net> added the comment:

I think the following change might address this problem:

***************
*** 233,239 ****
  
      def _on_reader_gc(self, wr):
          transport = self._transport
!         if transport is not None:
              # connection_made was called
              context = {
                  'message': ('An open stream object is being garbage '
--- 233,239 ----
  
      def _on_reader_gc(self, wr):
          transport = self._transport
!         if transport is not None and not transport.is_closing():
              # connection_made was called
              context = {
                  'message': ('An open stream object is being garbage '

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38529>
_______________________________________

From report at bugs.python.org  Sun Oct 27 12:41:05 2019
From: report at bugs.python.org (Ron Frederick)
Date: Sun, 27 Oct 2019 16:41:05 +0000
Subject: [issue38529] Python 3.8 improperly warns about closing properly
 closed streams
In-Reply-To: <1571510429.0.0.996597968813.issue38529@roundup.psfhosted.org>
Message-ID: <1572194465.96.0.752581493601.issue38529@roundup.psfhosted.org>


Ron Frederick <ronf at timeheart.net> added the comment:

Sorry, I should have said that the change below was in the file asyncio/streams.py.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38529>
_______________________________________

From report at bugs.python.org  Sun Oct 27 15:17:48 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sun, 27 Oct 2019 19:17:48 +0000
Subject: [issue38605] [typing] PEP 563: Postponed evaluation of annotations:
 enable it by default before Python 4.0
In-Reply-To: <1572192430.43.0.755831692199.issue38605@roundup.psfhosted.org>
Message-ID: <1572203868.16.0.884065857054.issue38605@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

IMO 3.10 would be better, since 3.9 would be too soon (it would be like a schedule for a normal deprecation).

Also if we are really doing this, I think it is better to announce this soon.

Also we should try to fix relevant issues related to string annotations (in typing and dataclasses), like https://github.com/python/typing/issues/508, https://github.com/python/typing/issues/574, https://bugs.python.org/issue37838, https://bugs.python.org/issue34776 and https://bugs.python.org/issue37948.

----------
nosy: +gvanrossum

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38605>
_______________________________________

From report at bugs.python.org  Sun Oct 27 15:13:07 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 27 Oct 2019 19:13:07 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572203587.18.0.487052988799.issue38606@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

Thank you for the suggestion. I don't think this fits that well with the view of the math module as a set of basic building blocks: this is quite a specialist function that wouldn't come up often in applications.

----------
nosy: +mark.dickinson

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Sun Oct 27 14:36:00 2019
From: report at bugs.python.org (Matthew Barnett)
Date: Sun, 27 Oct 2019 18:36:00 +0000
Subject: [issue23692] Undocumented feature prevents re module from finding
 certain matches
In-Reply-To: <1426618184.57.0.811463464384.issue23692@psf.upfronthosting.co.za>
Message-ID: <1572201360.12.0.222969488777.issue23692@roundup.psfhosted.org>


Matthew Barnett <python at mrabarnett.plus.com> added the comment:

Suppose you had a pattern:

    .*

It would advance one character on each iteration of the * until the . failed to match. The text is finite, so it would stop matching eventually.

Now suppose you had a pattern:

    (?:)*

On each iteration of the * it wouldn't advance, so it would keep matching forever.

A way to avoid that is to stop the * if it hasn't advanced.

The example pattern shows that there's still a problem. It advances if a group has matched, but that group doens't match until the first iteration, after the test, and does not, itself, advance. The * stops because it hasn't advanced, but, in this instance, that doesn't mean it never will.

The solution is for the * to check not only whether it has advanced, but also whether a group has changed. (Strictly speaking, the latter check is needed only if the repeated part tests whether a group also in the repeated part has changed, but it's probably not worth "optimising" for that possibility.)

In the regex module, it increments a "capture changed" counter whenever any group is changed (a group's first match or a change to a group's span). That makes it easier for the * to check. The code needs to save that counter for backtracking and restore it when backtracking.

I've mentioned only the *, but the same remarks apply to + and {...}, except that the {...} should keep repeating until it has reached its prescribed minimum.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23692>
_______________________________________

From report at bugs.python.org  Sun Oct 27 14:14:33 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Sun, 27 Oct 2019 18:14:33 +0000
Subject: [issue21002] _sre.SRE_Scanner object should have a fullmatch() method
In-Reply-To: <1395365477.75.0.293934412072.issue21002@psf.upfronthosting.co.za>
Message-ID: <1572200073.58.0.433735949007.issue21002@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21002>
_______________________________________

From report at bugs.python.org  Sun Oct 27 14:17:55 2019
From: report at bugs.python.org (ishan gambhir)
Date: Sun, 27 Oct 2019 18:17:55 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
Message-ID: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>


New submission from ishan gambhir <ishugambhir2001 at gmail.com>:

The function given in attached file can be added in math module

----------
components: 2to3 (2.x to 3.x conversion tool)
messages: 355490
nosy: ishan gambhir
priority: normal
severity: normal
status: open
title: Function to count total number of common divisors of two numbers
type: enhancement
Added file: https://bugs.python.org/file48680/cd_count.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Sun Oct 27 14:20:07 2019
From: report at bugs.python.org (ishan gambhir)
Date: Sun, 27 Oct 2019 18:20:07 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572200407.24.0.828072817218.issue38606@roundup.psfhosted.org>


Change by ishan gambhir <ishugambhir2001 at gmail.com>:


----------
components:  -2to3 (2.x to 3.x conversion tool)

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Sun Oct 27 14:17:00 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Sun, 27 Oct 2019 18:17:00 +0000
Subject: [issue21002] _sre.SRE_Scanner object should have a fullmatch() method
In-Reply-To: <1395365477.75.0.293934412072.issue21002@psf.upfronthosting.co.za>
Message-ID: <1572200220.9.0.762919161733.issue21002@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> Is anyone able to make a call on whether this issue should be closed, or alternatively give some guidance on what work this issue should encompass?

Added Serhiy to the nosy list, since he's an active maintainer for the re module.

----------
nosy: +aeros

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21002>
_______________________________________

From report at bugs.python.org  Sun Oct 27 14:18:43 2019
From: report at bugs.python.org (Ben Spiller)
Date: Sun, 27 Oct 2019 18:18:43 +0000
Subject: [issue38607] Document that cprofile/profile only profile the main
 thread
Message-ID: <1572200323.18.0.841143569385.issue38607@roundup.psfhosted.org>


New submission from Ben Spiller <spiller.ben at gmail.com>:

The built-in profiling modules only provide information about the main thread (at least when invoked as documented). 

To avoid user confusion we should state this in the documentation at https://docs.python.org/3/library/profile.html. 

Potentially we could also suggest mitigations such as manually creating a Profile instance in the user's thread code, but the most important thing is to make clear what the module does/does not do out of the box. 

(see also https://bugs.python.org/issue9609 which discusses a possible non-doc change to help with multi-threading, but looks like that's stalled, so best to push ahead with doc'ng this.

----------
assignee: docs at python
components: Documentation
messages: 355492
nosy: benspiller, docs at python
priority: normal
severity: normal
status: open
title: Document that cprofile/profile only profile the main thread
type: enhancement
versions: Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38607>
_______________________________________

From report at bugs.python.org  Sun Oct 27 15:26:58 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 27 Oct 2019 19:26:58 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572204418.35.0.30741113628.issue38606@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

Sorry, but I'm rejecting this: I don't think this is likely to have value to a range of users, and it's not a basic building block - as such, it doesn't really fit with the current design and intended usage of the math module.

You might consider publishing your code and recipes in a PyPI package: if that package gets a lot of users, that could be motivation to consider adding its functionality to core Python.

----------
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Sun Oct 27 13:32:23 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Sun, 27 Oct 2019 17:32:23 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572197543.43.0.305466324383.issue34790@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

I'd add `and will be removed in 3.11.` now.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Sun Oct 27 14:18:20 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Sun, 27 Oct 2019 18:18:20 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572200300.72.0.323664133318.issue34790@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

Sounds good, I'll work on opening a PR.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Sun Oct 27 15:29:52 2019
From: report at bugs.python.org (ishan gambhir)
Date: Sun, 27 Oct 2019 19:29:52 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572204592.3.0.0932860655484.issue38606@roundup.psfhosted.org>


ishan gambhir <ishugambhir2001 at gmail.com> added the comment:

no issue I will consider your worthy sugestion

----------
resolution: rejected -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Sun Oct 27 15:30:46 2019
From: report at bugs.python.org (ishan gambhir)
Date: Sun, 27 Oct 2019 19:30:46 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572204646.16.0.134743799305.issue38606@roundup.psfhosted.org>


Change by ishan gambhir <ishugambhir2001 at gmail.com>:


----------
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Sun Oct 27 14:26:47 2019
From: report at bugs.python.org (ishan gambhir)
Date: Sun, 27 Oct 2019 18:26:47 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572200807.92.0.697083818405.issue38606@roundup.psfhosted.org>


Change by ishan gambhir <ishugambhir2001 at gmail.com>:


----------
components: +Library (Lib)

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Sun Oct 27 13:15:01 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Sun, 27 Oct 2019 17:15:01 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572196501.36.0.194286381688.issue34790@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> Regarding 3.8 release notes update -- not sure if it is needed flr docs-only change.

I'm not certain if the entry is necessary; my main concern is just that it's already present in the 3.8 release notes/whatsnew without anywhere to look for further information. 

> In the current situation, we have so-called *soft deprecation*: bare coroutines are deprecated in docs without any code change. This is perfectly fine, we give our users extra time to prepare for changes.

So is something considered to be a "soft deprecation" if there is no code change? If so, I may have made a mistake by specifying a release in the entry I recently added for it (https://docs.python.org/3/whatsnew/3.8.html#deprecated):

"The explicit passing of coroutine objects to asyncio.wait() has been deprecated and will be removed in version 3.10."

I would propose to adjust this to:

"The explicit passing of coroutine objects to asyncio.wait() has been deprecated. (Contributed by Yury Selivanov in :issue:`34790`.)"

Then for 3.9 whatsnew, we could specify the release:

"The explicit passing of coroutine objects to asyncio.wait() has been deprecated and will be removed in 3.11."

Thoughts?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Sun Oct 27 13:29:48 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Sun, 27 Oct 2019 17:29:48 +0000
Subject: [issue38599] Deprecate creation of asyncio object when the loop is
 not running
In-Reply-To: <1572160085.79.0.39835517746.issue38599@roundup.psfhosted.org>
Message-ID: <1572197388.15.0.786999185453.issue38599@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

Yes.

As a remedy for this particular problem we can add checks here and there comparing `asyncio.get_running_loop()` and `self._loop`.  Performance will suffer a bit but the usability will greatly improve.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38599>
_______________________________________

From report at bugs.python.org  Sun Oct 27 13:24:29 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sun, 27 Oct 2019 17:24:29 +0000
Subject: [issue38314] Implement unix read_pipe.is_reading() method
In-Reply-To: <1569756133.59.0.955288942116.issue38314@roundup.psfhosted.org>
Message-ID: <1572197069.2.0.964527662996.issue38314@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

Please do.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38314>
_______________________________________

From report at bugs.python.org  Sun Oct 27 13:26:42 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Sun, 27 Oct 2019 17:26:42 +0000
Subject: [issue38529] Python 3.8 improperly warns about closing properly
 closed streams
In-Reply-To: <1571510429.0.0.996597968813.issue38529@roundup.psfhosted.org>
Message-ID: <1572197202.39.0.57648303683.issue38529@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

Yes, I've experienced this bug. We need to fix this in 3.8.1.

----------
nosy: +lukasz.langa
priority: normal -> release blocker

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38529>
_______________________________________

From report at bugs.python.org  Sun Oct 27 13:34:29 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sun, 27 Oct 2019 17:34:29 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572197669.81.0.0275934999732.issue34790@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

lgtm

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Sun Oct 27 15:55:01 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 27 Oct 2019 19:55:01 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1572206101.69.0.848946687435.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I think I am going to proceed modifying PR 16858 by adding the name and the object to the AttributeError exceptions.

This should not extend the lifetime of the object more than the current exception is doing as the exception keeps alive the whole frame stack in the __traceback__ attribute. Consider this code for example:

class Target:
    def __del__(self):
        print("The object is dead!")

def f():
    g()

def g():
    h()

def h():
    theobj = Target()
    theobj.thevalue

try:
    f()
except Exception as e:
    print(e.__traceback__.tb_next.tb_next.tb_next.tb_frame.f_locals["theobj"])
    print("End of except")
print("Begining of the next line")


This code prints:

<__main__.Target object at 0x7f064adbfe10>
End of except
The object is dead!
Beginning of the next line

We can notice two things:
   * The target objects are reachable from the exception.
   * When the exception dies, the target object dies.

Adding another reference to the target object to the exception won't change the current lifetime, neither will create reference cycles as the target object will not have (unless explicitly created) a reference to the exception. We can conclude that this change should be safe.

In the resolution email for PEP473 the council stated that "Discussions about adding more attributes to built-in exceptions can continue on the issue tracker on a per-exception basis". As I think this will be very beneficial for the feature discussed in the issue, I will proceed as indicated.

Notice that if we want to change all internal CPython code that raises AttributeError to use the new fields, this should be done in a different PR to keep this minimal. For this feature, we still need to intercept AttributeError raised by the user without these fields added.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sun Oct 27 15:55:41 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 27 Oct 2019 19:55:41 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1572206141.27.0.0281506609454.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

I think I am going to proceed to modify PR 16856 by adding the name and the object to the AttributeError exceptions.

This should not extend the lifetime of the object more than the current exception is doing as the exception keeps alive the whole frame stack in the __traceback__ attribute. Consider this code for example:

class Target:
    def __del__(self):
        print("The object is dead!")

def f():
    g()

def g():
    h()

def h():
    theobj = Target()
    theobj.thevalue

try:
    f()
except Exception as e:
    print(e.__traceback__.tb_next.tb_next.tb_next.tb_frame.f_locals["theobj"])
    print("End of except")
print("Begining of the next line")


This code prints:

<__main__.Target object at 0x7f064adbfe10>
End of except
The object is dead!
Beginning of the next line

We can notice two things:
   * The target objects are reachable from the exception.
   * When the exception dies, the target object dies.

Adding another reference to the target object to the exception won't change the current lifetime, neither will create reference cycles as the target object will not have (unless explicitly created) a reference to the exception. We can conclude that this change should be safe.

In the resolution email for PEP473 the council stated that "Discussions about adding more attributes to built-in exceptions can continue on the issue tracker on a per-exception basis". As I think this will be very beneficial for the feature discussed in the issue, I will proceed as indicated.

Notice that if we want to change all internal CPython code that raises AttributeError to use the new fields, this should be done in a different PR to keep this minimal. For this feature, we still need to intercept AttributeError raised by the user without these fields added.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sun Oct 27 15:55:48 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 27 Oct 2019 19:55:48 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1572206148.25.0.519137685444.issue38530@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
Removed message: https://bugs.python.org/msg355498

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sun Oct 27 15:56:21 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2019 19:56:21 +0000
Subject: [issue21002] _sre.SRE_Scanner object should have a fullmatch() method
In-Reply-To: <1395365477.75.0.293934412072.issue21002@psf.upfronthosting.co.za>
Message-ID: <1572206181.14.0.199455997359.issue21002@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I concur with David. The SRE_Scanner object is not public. Its search() method is used for implementing finditer(). Its match() method could be useful for implementing a functional equivalent of \G in Perl. But I do not know a use case for its fullmatch() method.

If anybody provide a use case for SRE_Scanner.fullmatch() this issue can be reopened.

----------
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21002>
_______________________________________

From report at bugs.python.org  Sun Oct 27 16:03:59 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 27 Oct 2019 20:03:59 +0000
Subject: [issue37838] typing.get_type_hints not working with
 forward-declaration and decorated functions
In-Reply-To: <1565692979.16.0.678723196671.issue37838@roundup.psfhosted.org>
Message-ID: <1572206639.97.0.692560095707.issue37838@roundup.psfhosted.org>


Joannah Nanjekye <nanjekyejoannah at gmail.com> added the comment:

@benedwards14 Feel free to open a PR. @netbnd said anyone can take on the issue since he may take long to revert with a PR.

----------
nosy: +nanjekyejoannah

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37838>
_______________________________________

From report at bugs.python.org  Sun Oct 27 16:05:53 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 27 Oct 2019 20:05:53 +0000
Subject: [issue37838] typing.get_type_hints not working with
 forward-declaration and decorated functions
In-Reply-To: <1565692979.16.0.678723196671.issue37838@roundup.psfhosted.org>
Message-ID: <1572206753.79.0.0405459037995.issue37838@roundup.psfhosted.org>


Joannah Nanjekye <nanjekyejoannah at gmail.com> added the comment:

Actually there is a patch. So please @netbnd please open a PR https://github.com/python/cpython

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37838>
_______________________________________

From report at bugs.python.org  Sun Oct 27 16:20:10 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2019 20:20:10 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1572207610.04.0.78917312193.issue38530@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Interesting, why locals are not cleared when an exception leaves a frame?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Sun Oct 27 17:01:08 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2019 21:01:08 +0000
Subject: [issue38602] Add fcntl.F_OFD_XXXX constant
In-Reply-To: <1572182823.74.0.700361916573.issue38602@roundup.psfhosted.org>
Message-ID: <1572210068.05.0.360131280635.issue38602@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

See also issue22367.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38602>
_______________________________________

From report at bugs.python.org  Sun Oct 27 18:32:25 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Sun, 27 Oct 2019 22:32:25 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572215545.1.0.907209649061.issue38606@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Also, next time I suggest that you try running the code at least once before submitting it, as your code contains a syntax error that prevents it from running.

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Sun Oct 27 18:51:45 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Sun, 27 Oct 2019 22:51:45 +0000
Subject: [issue38605] [typing] PEP 563: Postponed evaluation of annotations:
 enable it by default before Python 4.0
In-Reply-To: <1572192430.43.0.755831692199.issue38605@roundup.psfhosted.org>
Message-ID: <1572216705.78.0.183726916794.issue38605@roundup.psfhosted.org>


Change by Eric V. Smith <eric at trueblade.com>:


----------
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38605>
_______________________________________

From report at bugs.python.org  Sun Oct 27 19:23:41 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Sun, 27 Oct 2019 23:23:41 +0000
Subject: [issue38605] [typing] PEP 563: Postponed evaluation of annotations:
 enable it by default before Python 4.0
In-Reply-To: <1572216705.82.0.609942732916.issue38605@roundup.psfhosted.org>
Message-ID: <CAP7+vJKBq_4S2XjsLKvcegxVbVHcsGbf7g-uduAeWkdyJ_MmDQ@mail.gmail.com>


Guido van Rossum <guido at python.org> added the comment:

We never should have mentioned 4.0 as the target date to make this the
default (and only) behavior -- who knows whether there will ever even be a
Python 4.0? Even 3.10 might be on the early side (assuming we'll switch to
a year-long release cycle per PEP 602 -- we will then make deprecations in
general take two release cycles).

I do agree that we should start the process of deprecating the
non-__future__ behavior here in 3.9. I know of one project with a private
fork of Python (for other reasons) that has made this default.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38605>
_______________________________________

From report at bugs.python.org  Sun Oct 27 19:55:45 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sun, 27 Oct 2019 23:55:45 +0000
Subject: [issue38599] Deprecate creation of asyncio object when the loop is
 not running
In-Reply-To: <1572160085.79.0.39835517746.issue38599@roundup.psfhosted.org>
Message-ID: <1572220544.99.0.483068662437.issue38599@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

At least it is my learned lesson from aiohttp development.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38599>
_______________________________________

From report at bugs.python.org  Sun Oct 27 19:55:17 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Sun, 27 Oct 2019 23:55:17 +0000
Subject: [issue38599] Deprecate creation of asyncio object when the loop is
 not running
In-Reply-To: <1572160085.79.0.39835517746.issue38599@roundup.psfhosted.org>
Message-ID: <1572220517.17.0.719967711059.issue38599@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

I have a different feeling: we should start raising deprecation for asyncio.Queue() if it is created without running event loop.

It required `get_event_loop()` and `loop.is_running()` checks.

Later the pair can be replaced with `get_running_loop()`.

I think no check at awaiting time is needed; we never do it for other asyncio parts.  Just control of the loop at creation time is enough; if the object is created inside a running loop the sane code will use it with this loop context always.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38599>
_______________________________________

From report at bugs.python.org  Sun Oct 27 21:50:13 2019
From: report at bugs.python.org (Wei-Cheng Pan)
Date: Mon, 28 Oct 2019 01:50:13 +0000
Subject: [issue38608] Undocumented behavior that IsolatedAsyncioTestCase would
 enable event loop debug mode
Message-ID: <1572227413.17.0.184690601558.issue38608@roundup.psfhosted.org>


New submission from Wei-Cheng Pan <legnaleurc at gmail.com>:

In bpo-32972 we enabled debug mode in IsolatedAsyncioTestCase._setupAsyncioLoop, which may print some warnings that are not that important to tests.
(e.g. Executing <Future ...> took 0.110 seconds)

I personally don't really like it being turn on by default, but if it needs to be so, maybe include it in document would be a good idea.

Add Andrew to nosy list because he was the author.

----------
components: Tests
messages: 355509
nosy: asvetlov, legnaleurc
priority: normal
severity: normal
status: open
title: Undocumented behavior that IsolatedAsyncioTestCase would enable event loop debug mode
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38608>
_______________________________________

From report at bugs.python.org  Sun Oct 27 21:59:10 2019
From: report at bugs.python.org (Ma Lin)
Date: Mon, 28 Oct 2019 01:59:10 +0000
Subject: [issue23692] Undocumented feature prevents re module from finding
 certain matches
In-Reply-To: <1426618184.57.0.811463464384.issue23692@psf.upfronthosting.co.za>
Message-ID: <1572227950.07.0.255125910512.issue23692@roundup.psfhosted.org>


Change by Ma Lin <malincns at 163.com>:


----------
nosy: +Ma Lin

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23692>
_______________________________________

From report at bugs.python.org  Sun Oct 27 22:44:52 2019
From: report at bugs.python.org (ysnt27)
Date: Mon, 28 Oct 2019 02:44:52 +0000
Subject: [issue38609] Trashcan mechanism segfault during interpreter
 finalization in Python 3.7.5
Message-ID: <1572230692.1.0.462220822628.issue38609@roundup.psfhosted.org>


New submission from ysnt27 <yoshint2012 at gmail.com>:

My original issue was reported to Boost.Python,
https://github.com/boostorg/python/issues/248
And I found similar issue
https://bugs.python.org/issue17703

It seems root cause exists in Python not Boost.Python.
As the issue #17703 is already closed, I want to open a new issue.

I attached a sample source code, "sample1.cc".
With the code, I can reproduce segmantation fault, like this.

% gdb /usr/local/python375/bin/python3.7dm
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-115.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/python375/bin/python3.7dm...done.
(gdb) run
Starting program: /usr/local/python375/bin/python3.7dm 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Python 3.7.5 (default, Oct 25 2019, 16:11:10) 
[GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sample1
something called
>>> sample1.dummy()
[1]
>>> exit()
~something called

Program received signal SIGSEGV, Segmentation fault.
0x000000000044602a in list_dealloc (op=op at entry=0x7ffff7f4b360)
    at ../Objects/listobject.c:316
316	    Py_TRASHCAN_SAFE_BEGIN(op)
(gdb) p _PyRuntime.gilstate.tstate_current
$1 = {_value = 0}
(gdb) where
#0  0x000000000044602a in list_dealloc (op=op at entry=0x7ffff7f4b360)
    at ../Objects/listobject.c:316
#1  0x0000000000466452 in _Py_Dealloc (op=0x7ffff7f4b360)
    at ../Objects/object.c:1971
#2  0x00007ffff051cc28 in something::~something (this=0x7ffff071e140 <obj>, 
    __in_chrg=<optimized out>) at sample1.cc:26
#3  0x00007ffff6eeac99 in __run_exit_handlers (status=status at entry=0, 
    listp=0x7ffff72786c8 <__exit_funcs>, 
    run_list_atexit=run_list_atexit at entry=true) at exit.c:77
#4  0x00007ffff6eeace7 in __GI_exit (status=status at entry=0) at exit.c:99
#5  0x00000000005178e4 in Py_Exit (sts=sts at entry=0)
    at ../Python/pylifecycle.c:2292
#6  0x000000000051faf4 in handle_system_exit () at ../Python/pythonrun.c:636
#7  0x0000000000520d88 in PyErr_PrintEx (
    set_sys_last_vars=set_sys_last_vars at entry=1) at ../Python/pythonrun.c:646
#8  0x000000000052115f in PyErr_Print () at ../Python/pythonrun.c:542
#9  0x0000000000521d1a in PyRun_InteractiveLoopFlags (
    fp=fp at entry=0x7ffff7279640 <_IO_2_1_stdin_>, 
    filename_str=filename_str at entry=0x5e55b2 "<stdin>", 
    flags=flags at entry=0x7fffffffe2f0) at ../Python/pythonrun.c:134
#10 0x00000000005223d8 in PyRun_AnyFileExFlags (
    fp=fp at entry=0x7ffff7279640 <_IO_2_1_stdin_>, filename=0x5e55b2 "<stdin>", 
    closeit=closeit at entry=0, flags=flags at entry=0x7fffffffe2f0)
---Type <return> to continue, or q <return> to quit---
    at ../Python/pythonrun.c:78
#11 0x0000000000422023 in pymain_run_file (fp=0x7ffff7279640 <_IO_2_1_stdin_>, 
    filename=0x0, p_cf=p_cf at entry=0x7fffffffe2f0) at ../Modules/main.c:427
#12 0x00000000004220e5 in pymain_run_filename (
    pymain=pymain at entry=0x7fffffffe320, cf=cf at entry=0x7fffffffe2f0)
    at ../Modules/main.c:1606
#13 0x00000000004221d8 in pymain_run_python (pymain=pymain at entry=0x7fffffffe320)
    at ../Modules/main.c:2867
#14 0x000000000042550f in pymain_main (pymain=pymain at entry=0x7fffffffe320)
    at ../Modules/main.c:3028
#15 0x0000000000425589 in _Py_UnixMain (argc=<optimized out>, 
    argv=<optimized out>) at ../Modules/main.c:3063
#16 0x000000000041f116 in main (argc=<optimized out>, argv=<optimized out>)
    at ../Programs/python.c:15
(gdb) l
311	static void
312	list_dealloc(PyListObject *op)
313	{
314	    Py_ssize_t i;
315	    PyObject_GC_UnTrack(op);
316	    Py_TRASHCAN_SAFE_BEGIN(op)
317	    if (op->ob_item != NULL) {
318	        /* Do it backwards, for Christian Tismer.
319	           There's a simple test case where somehow this reduces
320	           thrashing when a *very* large list is created and
(gdb)

----------
components: Interpreter Core
files: sample1.cc
messages: 355510
nosy: ysnt27
priority: normal
severity: normal
status: open
title: Trashcan mechanism segfault during interpreter finalization in Python 3.7.5
type: crash
versions: Python 3.7
Added file: https://bugs.python.org/file48681/sample1.cc

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38609>
_______________________________________

From report at bugs.python.org  Mon Oct 28 00:27:30 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Mon, 28 Oct 2019 04:27:30 +0000
Subject: [issue38602] Add fcntl.F_OFD_XXXX constant
In-Reply-To: <1572182823.74.0.700361916573.issue38602@roundup.psfhosted.org>
Message-ID: <1572236850.12.0.211151266007.issue38602@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

> See also issue22367.

Okay I will take a look at it also. :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38602>
_______________________________________

From report at bugs.python.org  Mon Oct 28 00:29:13 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Mon, 28 Oct 2019 04:29:13 +0000
Subject: [issue22367] Add open_file_descriptor parameter to fcntl.lockf() (use
 the new F_OFD_SETLK flag)
In-Reply-To: <1410207529.54.0.778133775349.issue22367@psf.upfronthosting.co.za>
Message-ID: <1572236953.03.0.0489312020473.issue22367@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

On issue 38602, the constant related to open file descriptors will be added.
I will finalize this issue after issue 38602 is closed.

----------
assignee:  -> corona10
nosy: +corona10

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22367>
_______________________________________

From report at bugs.python.org  Mon Oct 28 01:49:18 2019
From: report at bugs.python.org (LCatro)
Date: Mon, 28 Oct 2019 05:49:18 +0000
Subject: [issue38610] use-after-free in list object function
Message-ID: <1572241758.28.0.0734328499539.issue38610@roundup.psfhosted.org>


New submission from LCatro <m4i1f0rt3st at sina.cn>:

Code 1 :

static PyObject *
list_index_impl(PyListObject *self, PyObject *value, Py_ssize_t start,
                Py_ssize_t stop)
// ...
    for (i = start; i < stop && i < Py_SIZE(self); i++) {
        int cmp = PyObject_RichCompareBool(self->ob_item[i], value, Py_EQ);  <=  self->ob_item[i] can uaf ..


PoC :

class rewrite_list_eq(list) :
    def __eq__(self,other) :
        str(other)   #  <== that will call the object recall function tp_repr and call it ..
        return NotImplemented

class poc() :
    def __eq__(self,other) :
        list1.clear()
        return NotImplemented

list1 = [ poc() ]
list1.index(list1)   #  list_index_impl() -> PyObject_RichCompareBool()


Crash Report :

(gdb) run ../py_poc/list_poc_3.py
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /tangjitao/Python-3.8.0/python ../py_poc/list_poc_3.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
PyObject_Str (v=0x7ffff6e82d20) at Objects/object.c:573
573         if (Py_TYPE(v)->tp_str == NULL)

===== 

Code 2 :

static PyObject *
list_count(PyListObject *self, PyObject *value)
{
    Py_ssize_t count = 0;
    Py_ssize_t i;

    for (i = 0; i < Py_SIZE(self); i++) {
        int cmp = PyObject_RichCompareBool(self->ob_item[i], value, Py_EQ);  //  <=


PoC :

class rewrite_list_eq(list) :
    def __eq__(self,other) :
        str(other)
        return NotImplemented

class poc() :
    def __eq__(self,other) :
        list1.clear()
        return NotImplemented

list1 = rewrite_list_eq([ poc() ])
list1.count(list1)   #  list_count() -> PyObject_RichCompareBool()


Crash Report :

(gdb) run ../py_poc/list_poc_4.py
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /tangjitao/Python-3.8.0/python ../py_poc/list_poc_4.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
PyObject_Str (v=0x7ffff6e82d20) at Objects/object.c:573
573         if (Py_TYPE(v)->tp_str == NULL)


===

Code 3 :

static PyObject *
list_remove(PyListObject *self, PyObject *value)
/*[clinic end generated code: output=f087e1951a5e30d1 input=2dc2ba5bb2fb1f82]*/
{
    Py_ssize_t i;

    for (i = 0; i < Py_SIZE(self); i++) {
		Py_INCREF(self->ob_item[i]);
        int cmp = PyObject_RichCompareBool(self->ob_item[i], value, Py_EQ);


PoC :

class rewrite_list_eq(list) :
    def __eq__(self,other) :
        str(other)
        return NotImplemented

class poc() :
    def __eq__(self,other) :
        list1.clear()
        return NotImplemented

list1 = rewrite_list_eq([ poc() ])
list1.remove(list1)   #  list_count() -> PyObject_RichCompareBool()


Crash Report :

(gdb) run ../py_poc/list_poc_5.py
Starting program: /tangjitao/Python-3.8.0/python ../py_poc/list_poc_5.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
PyObject_Str (v=0x7ffff6e82d20) at Objects/object.c:573
573         if (Py_TYPE(v)->tp_str == NULL)

----------
components: Interpreter Core
messages: 355513
nosy: LCatro, serhiy.storchaka
priority: normal
severity: normal
status: open
title: use-after-free in list object function
type: crash
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38610>
_______________________________________

From report at bugs.python.org  Mon Oct 28 01:50:36 2019
From: report at bugs.python.org (LCatro)
Date: Mon, 28 Oct 2019 05:50:36 +0000
Subject: [issue38588] Use-after-free in dict/list
In-Reply-To: <1572009950.92.0.0819194467929.issue38588@roundup.psfhosted.org>
Message-ID: <1572241836.09.0.788383146786.issue38588@roundup.psfhosted.org>


LCatro <m4i1f0rt3st at sina.cn> added the comment:

Sure ,but how can i pull my fix code ?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38588>
_______________________________________

From report at bugs.python.org  Mon Oct 28 03:31:34 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 07:31:34 +0000
Subject: [issue38602] Add fcntl.F_OFD_XXXX constant
In-Reply-To: <1572182823.74.0.700361916573.issue38602@roundup.psfhosted.org>
Message-ID: <1572247894.35.0.864517260209.issue38602@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 3bfc8e0fcc707d200c267ff05b052fd6a63c985a by Serhiy Storchaka (Dong-hee Na) in branch 'master':
bpo-38602: Add fcntl.F_OFD_XXXX for fcntlmodule (GH-16956)
https://github.com/python/cpython/commit/3bfc8e0fcc707d200c267ff05b052fd6a63c985a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38602>
_______________________________________

From report at bugs.python.org  Mon Oct 28 03:31:53 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 07:31:53 +0000
Subject: [issue38602] Add fcntl.F_OFD_XXXX constant
In-Reply-To: <1572182823.74.0.700361916573.issue38602@roundup.psfhosted.org>
Message-ID: <1572247913.4.0.0490068427267.issue38602@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type:  -> enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38602>
_______________________________________

From report at bugs.python.org  Mon Oct 28 04:14:50 2019
From: report at bugs.python.org (ishan gambhir)
Date: Mon, 28 Oct 2019 08:14:50 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572250490.35.0.167171724009.issue38606@roundup.psfhosted.org>


ishan gambhir <ishugambhir2001 at gmail.com> added the comment:

Sorry For it now it is corrected.

----------
Added file: https://bugs.python.org/file48682/cd_count.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Mon Oct 28 04:15:17 2019
From: report at bugs.python.org (ishan gambhir)
Date: Mon, 28 Oct 2019 08:15:17 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572250517.87.0.00564509071531.issue38606@roundup.psfhosted.org>


Change by ishan gambhir <ishugambhir2001 at gmail.com>:


Removed file: https://bugs.python.org/file48680/cd_count.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Mon Oct 28 04:17:20 2019
From: report at bugs.python.org (ishan gambhir)
Date: Mon, 28 Oct 2019 08:17:20 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572250640.53.0.890656029323.issue38606@roundup.psfhosted.org>


Change by ishan gambhir <ishugambhir2001 at gmail.com>:


Removed file: https://bugs.python.org/file48682/cd_count.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Mon Oct 28 04:17:49 2019
From: report at bugs.python.org (ishan gambhir)
Date: Mon, 28 Oct 2019 08:17:49 +0000
Subject: [issue38606] Function to count total number of common divisors of two
 numbers
In-Reply-To: <1572200275.66.0.453308218443.issue38606@roundup.psfhosted.org>
Message-ID: <1572250669.32.0.494291816444.issue38606@roundup.psfhosted.org>


Change by ishan gambhir <ishugambhir2001 at gmail.com>:


Added file: https://bugs.python.org/file48683/cd_count.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38606>
_______________________________________

From report at bugs.python.org  Mon Oct 28 04:29:38 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 28 Oct 2019 08:29:38 +0000
Subject: [issue38538] dictobject dictviews don't return NotImplemented for
 unrecognized types.
In-Reply-To: <1571585548.13.0.376831813762.issue38538@roundup.psfhosted.org>
Message-ID: <1572251378.18.0.240482833715.issue38538@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

> but it's not that simple as the __or__ of dictviews is less strict that the __or__ of set: __or__ of dictview accept any iterable, __or__ of set only accepts sets.

I want to make it same to set.
But it is a backward incompatible...

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38538>
_______________________________________

From report at bugs.python.org  Mon Oct 28 05:11:15 2019
From: report at bugs.python.org (Jim Carroll)
Date: Mon, 28 Oct 2019 09:11:15 +0000
Subject: [issue38611] Bug in traceback.py
Message-ID: <1572253875.02.0.816082787085.issue38611@roundup.psfhosted.org>


New submission from Jim Carroll <jim at carroll.com>:

_elementtree.c defines a custom exception 'xml.etree.ElementTree.ParseError' that inherits from SyntaxError. According to the docs https://docs.python.org/3/library/exceptions.html#SyntaxError

``Instances of this class have attributes filename, lineno, offset and text for easier access to the details.``

The ElementTree.Parser does not provide these extra attributes. While unittesting a badly formatted string passed to ET.fromstring(), the unittests/results.py module passes the exception to traceback.py, which attempts to extract the members causing it to raise a new exception.

Either ElementTree.Parser should be raising something other than SyntaxErrors, or it should be providing the required attributes, or traceback.py needs to be more flexible and test for the extra attributes before accessing.

I'm willing to submit a patch, but before diving in, wasn't sure which path people would prefer to see fixed?

The code in traceback.py is from lines 516 - 521.

----------
components: Library (Lib)
messages: 355518
nosy: jamercee
priority: normal
severity: normal
status: open
title: Bug in traceback.py
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38611>
_______________________________________

From report at bugs.python.org  Mon Oct 28 05:36:40 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Mon, 28 Oct 2019 09:36:40 +0000
Subject: [issue38608] Undocumented behavior that IsolatedAsyncioTestCase would
 enable event loop debug mode
In-Reply-To: <1572227413.17.0.184690601558.issue38608@roundup.psfhosted.org>
Message-ID: <1572255400.51.0.99239426545.issue38608@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

This print comes from asyncio debug mode when async function is blocked by time longer than 0.1 sec (see loop.slow_callback_duration at loop.slow_callback_duration).
Usually, it is a sign of a problem in user code, e.g. something should be pushed into executor.

A test case is executed in debug mode. I think it is reasonable for the test run, isn't it?

The mode can be disabled by `asyncio.get_running_loop().set_debug(False)` in `asyncSetUp()` method.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38608>
_______________________________________

From report at bugs.python.org  Mon Oct 28 06:51:38 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Mon, 28 Oct 2019 10:51:38 +0000
Subject: [issue4630] IDLE: add cursor noblink option
In-Reply-To: <1228982754.08.0.523311497339.issue4630@psf.upfronthosting.co.za>
Message-ID: <1572259898.96.0.310338275014.issue4630@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
pull_requests: +16488
pull_request: https://github.com/python/cpython/pull/16960

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue4630>
_______________________________________

From report at bugs.python.org  Mon Oct 28 06:52:32 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 10:52:32 +0000
Subject: [issue37224] test__xxsubinterpreters fails randomly
In-Reply-To: <1560214681.61.0.906498246375.issue37224@roundup.psfhosted.org>
Message-ID: <1572259952.05.0.263721326786.issue37224@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

See also bpo-33868: test__xxsubinterpreters fails randomly since at least 2018-06-15.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37224>
_______________________________________

From report at bugs.python.org  Mon Oct 28 06:54:47 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Mon, 28 Oct 2019 10:54:47 +0000
Subject: [issue4630] IDLE: add cursor noblink option
In-Reply-To: <1228982754.08.0.523311497339.issue4630@psf.upfronthosting.co.za>
Message-ID: <1572260087.09.0.490035377886.issue4630@roundup.psfhosted.org>


Zackery Spytz <zspytz at gmail.com> added the comment:

I have created a pull request for this issue.

----------
nosy: +ZackerySpytz

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue4630>
_______________________________________

From report at bugs.python.org  Mon Oct 28 06:59:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 10:59:26 +0000
Subject: [issue22367] Add open_file_descriptor parameter to fcntl.lockf() (use
 the new F_OFD_SETLK flag)
In-Reply-To: <1410207529.54.0.778133775349.issue22367@psf.upfronthosting.co.za>
Message-ID: <1572260366.79.0.536548850021.issue22367@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> On issue 38602, the constant related to open file descriptors will be added. I will finalize this issue after issue 38602 is closed.

issue 38602 added constants, but this issue also modify lockf() to add open_file_descriptor parameter to choose between F_SETLK/F_SETLKW and F_OFD_SETLK/F_OFD_SETLKW.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22367>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:03:22 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 11:03:22 +0000
Subject: [issue38605] [typing] PEP 563: Postponed evaluation of annotations:
 enable it by default before Python 4.0
In-Reply-To: <1572192430.43.0.755831692199.issue38605@roundup.psfhosted.org>
Message-ID: <1572260602.82.0.492560896166.issue38605@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> We never should have mentioned 4.0 as the target date to make this the
default (and only) behavior

I am fine with modifying __future__ documentation to only modify the "Mandatory" column to remove Python 4.0, and then close this issue:
https://docs.python.org/dev/library/__future__.html

--

But I like the "PEP 563: Postponed evaluation of annotations", IMHO it would be nice to get it as the default behavior :-) It's just a matter of properly organize the transition ;-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38605>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:06:13 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 11:06:13 +0000
Subject: [issue38604] Schedule Py_UNICODE API removal
In-Reply-To: <1572192125.35.0.636716899488.issue38604@roundup.psfhosted.org>
Message-ID: <1572260773.59.0.536371691456.issue38604@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

A preleminary step was to modify PyUnicode_AsWideChar() and PyUnicode_AsWideCharString() to remove the internal caching: it has been done in Python 3.8.0 with bpo-30863.

----------
nosy: +inada.naoki, serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38604>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:08:00 2019
From: report at bugs.python.org (Richard Pausch)
Date: Mon, 28 Oct 2019 11:08:00 +0000
Subject: [issue38612] some non-ascii charcters link to same identifier/data
Message-ID: <1572260880.13.0.309355653543.issue38612@roundup.psfhosted.org>


New submission from Richard Pausch <r.pausch at hzdr.de>:

The issue was first reported in https://github.com/ipython/ipython/issues/11918. 

Some non-ascii characters like ? (\u03c6) and ? (\u03d5) map/link to the same data/identifier. 

```python
? = 1
? = 2
print(?) # results in 2 - should be 1
print(?) # results in 2
```

It has so far been shown to occur both in python 3.6 and 3.7.

----------
messages: 355525
nosy: PrometheusPi
priority: normal
severity: normal
status: open
title: some non-ascii charcters link to same identifier/data
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38612>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:16:51 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 28 Oct 2019 11:16:51 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572261411.2.0.238942929873.issue38600@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

In  
'If *exc* is *NULL*, then the exception is cleared and the value is clipped to *PY_SSIZE_T_MIN* for a negative integer or *PY_SSIZE_T_MAX* for a positive integer.', should PY_SSIZE_T_MIN and PY_SSIZE_T_MAX be changed too?

----------
nosy: +shihai1991

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:17:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 11:17:59 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1572261479.55.0.0168651037952.issue38530@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Helping the developer to suggest a fix introduces a minor but non-zero overhead, I would prefer to only enable it as an opt-in option. Maybe enable it using in the development mode (-X dev/PYTHONDEVMODE=1)?

> https://github.com/dutc/didyoumean (by James Powell)

This project hooks into PyObject_GetAttr() by modifying PyObject_GetAttr() machine code, which is definitely not a portable approach.

Maybe one approach would be to add a way to install a hook to customize AttributeError exceptions?

Can this issue be implemented using sys.excepthook?

--

This issue is specific to AttributeError, but I vaguely recall that Yury Selivanov told me that he wanted to something but for any exception. Detect the most common mistakes and propose a solution. I don't think that he ever sent anything in public sadly.

I add Yury in the nosy list.

--

Here is another project which also catch NameError, AttributeError, ImportError, TypeError, ValueError, SyntaxError, MemoryError, OverflowError, OSError, RuntimeError, etc. :
https://github.com/SylvainDe/DidYouMean-Python

It is implemented with sys.excepthook, but it is also compatible with IPython "custom exception handler" (call get_ipython().set_custom_exc()).

By the way, does IPython have a feature like this?

In short, https://github.com/SylvainDe/DidYouMean-Python seems to already implement this issue in the proper way, no?

--

Similar project for Ruby:
https://github.com/yuki24/did_you_mean

----------
nosy: +yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:20:00 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 28 Oct 2019 11:20:00 +0000
Subject: [issue38604] Schedule Py_UNICODE API removal
In-Reply-To: <1572192125.35.0.636716899488.issue38604@roundup.psfhosted.org>
Message-ID: <1572261600.97.0.038763643666.issue38604@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

I want to remove them in 3.10 too.
If we chose the annual release cycle, I'm OK to postpone the removal to 3.11.

FWIW, ujson is apopular extension that uses these APIs.
But it is not maintained for a long time, and there are many alternative JSON libraries.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38604>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:22:28 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 11:22:28 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572261748.76.0.274765406576.issue38600@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Yes of course, but I'll fix them in a separate PR. PR 16950 is mostly automatic replacements.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:24:44 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 28 Oct 2019 11:24:44 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1572261884.33.0.850677583814.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

> By the way, does IPython have a feature like this?

Not that I know of.

> In short, https://github.com/SylvainDe/DidYouMean-Python seems to already implement this issue in the proper way, no?

I briefly checked the project. My current approach exposes the object and the name directly on the exception, so the display hook can directly using them instead of fiddling with frames and other things.

Additionally, I think it would be very beneficial to have it in the core, as many people learning python for example cannot install packages.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:25:44 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 28 Oct 2019 11:25:44 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1572261944.84.0.691045824566.issue38530@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

> Helping the developer to suggest a fix introduces a minor but non-zero overhead, I would prefer to only enable it as an opt-in option. Maybe enable it using in the development mode (-X dev/PYTHONDEVMODE=1)?

I think doing that would make it lose almost completely its value.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:28:03 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 11:28:03 +0000
Subject: [issue38604] Schedule Py_UNICODE API removal
In-Reply-To: <1572192125.35.0.636716899488.issue38604@roundup.psfhosted.org>
Message-ID: <1572262083.49.0.667502690659.issue38604@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

See issue36346.

First we need to add compile-time deprecation warnings to all C API. Then add runtime deprecation warnings. And since this is a major compatibility breakage, it can take longer deprecation period.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38604>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:28:17 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 11:28:17 +0000
Subject: [issue38530] Offer suggestions on AttributeError
In-Reply-To: <1571511451.65.0.74942926189.issue38530@roundup.psfhosted.org>
Message-ID: <1572262097.1.0.836316091593.issue38530@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Ruby has it integrated into the core : https://bugs.ruby-lang.org/issues/11252 . It was initially a gem that got merged into core.

GCC also provides more and more hints. Example:

   int main() { int hello = 1; return helo; }

GCC:

   error: 'helo' undeclared (first use in this function); did you mean 'hello'?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38530>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:34:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 11:34:46 +0000
Subject: [issue38604] Schedule Py_UNICODE API removal
In-Reply-To: <1572192125.35.0.636716899488.issue38604@roundup.psfhosted.org>
Message-ID: <1572262486.81.0.238671621962.issue38604@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> See issue36346.

Oh, I failed to find this issue. Ok, I close mine as a duplicate.

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Prepare for removing the legacy Unicode C API

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38604>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:35:14 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 11:35:14 +0000
Subject: [issue36346] Prepare for removing the legacy Unicode C API
In-Reply-To: <1552918981.83.0.901300276481.issue36346@roundup.psfhosted.org>
Message-ID: <1572262514.85.0.795438360698.issue36346@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I closed bpo-38604 as a duplicate. Copy of my messages.

 msg355475 - (view) 	Author: STINNER Victor (vstinner) * (Python committer) 	Date: 2019-10-27 16:02

Python 3.3 deprecated the C API functions using Py_UNICODE type. Examples in the doc:

* https://docs.python.org/dev/c-api/unicode.html#c.Py_UNICODE
* https://docs.python.org/dev/c-api/unicode.html#deprecated-py-unicode-apis

Currently, functions removal is scheduled for Python 4.0 but I would prefer that Python 4.0 doesn't have a long list of removed features, but no more than usual. So I'm trying to remove a few functions from Python 3.9, and try to prepare removal for others.

Py_UNICODE C API was mostly kept for backward compatibility with Python 2. Since Python 2 support ends at the end of the year, can we start to organize Py_UNICODE C API removal?

There are multiple questions:

* Should we drop the whole API at once? Or can we/should we start by removing a few functions, and then the others?
* Deprecation warnings are emitted at compilation. But I'm not aware of DeprecationWarning emited at runtime. IMHO we should emit DesprecationWarning at runtime during at least one release, so most developers ignore compilation warnings.

I propose to:

* (Right now) write an exhaustive list of all deprecated APIs: functions, constants, types, etc.
* Modify C code to emit DeprecationWarning at runtime in Python 3.9
* Experiment a modified Python without these APIs and test how many projects are broken by this removal: see PEP 608
* Schedule the actual removal of all these APIS from Python 3.10

Honestly, if the removal is causing too much issues, I'm fine to make slowdown the removal. It's just a matter of clearly communicating our intent.

Maybe we should also announce the scheduled removal in What's in Python 3.9 and in the capi-sig mailing list.

msg355478 - (view) 	Author: STINNER Victor (vstinner) * (Python committer) 	Date: 2019-10-27 16:15

> (Right now) write an exhaustive list of all deprecated APIs: functions, constants, types, etc.

I searched "4.0" in the documentation:

* Py_UNICODE type
* array.array: "u" type
* PyArg_ParseTuple, Py_BuildValue: "u", "u#", "Z", "Z#" formats

* PyUnicode_FromUnicode()
* PyUnicode_GetSize(), PyUnicode_GET_SIZE()
* PyUnicode_AsUnicode(), PyUnicode_AS_UNICODE(), PyUnicode_AS_DATA()
* PyUnicode_AsUnicodeAndSize()
* PyUnicode_AsUnicodeCopy()

* PyUnicode_FromObject()
* PyLong_FromUnicode()
* PyUnicode_TransformDecimalToASCII()

* PyUnicode_Encode()
* PyUnicode_EncodeUTF7()
* PyUnicode_EncodeUTF8()
* PyUnicode_EncodeUTF32()
* PyUnicode_EncodeUTF16()
* PyUnicode_EncodeUnicodeEscape()
* PyUnicode_EncodeRawUnicodeEscape()
* PyUnicode_EncodeLatin1()
* PyUnicode_EncodeASCII()
* PyUnicode_EncodeMBCS()
* PyUnicode_EncodeCharmap()
* PyUnicode_TranslateCharmap()

msg355524 - (view) 	Author: STINNER Victor (vstinner) * (Python committer) 	Date: 2019-10-28 11:06

A preleminary step was to modify PyUnicode_AsWideChar() and PyUnicode_AsWideCharString() to remove the internal caching: it has been done in Python 3.8.0 with bpo-30863.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36346>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:36:23 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 11:36:23 +0000
Subject: [issue21622] ctypes.util incorrectly fails for libraries without
 DT_SONAME
In-Reply-To: <1401593302.24.0.994822187168.issue21622@psf.upfronthosting.co.za>
Message-ID: <1572262583.89.0.511919170039.issue21622@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
nosy:  -vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21622>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:55:45 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 28 Oct 2019 11:55:45 +0000
Subject: [issue38613] Optimize some set operations in dictkeys object
Message-ID: <1572263745.15.0.0692968844895.issue38613@roundup.psfhosted.org>


New submission from Inada Naoki <songofacandy at gmail.com>:

-, |, and ^ of dictkeys are implemented as:

PyObject *result = PySet_New(self);
// Call set.difference_update, set.update, set.symmetric_difference_update with other.

PySet_New(iterable) has optimized step for iterable is dict.
But since iterable is dictkeys, PyIter_Next() is called for all elements in the dict.

We can pass dict instead of dictkey object to PySet_New.

  $ ./python -m pyperf timeit -o patched.json -s 'k = dict.fromkeys("abcdefghijklmnopqrstuvwxyz").keys(); s={1,2,3}' -- 'k | {1,2,3}'
  $ ./python -m pyperf compare_to master.json patched.json
  Mean +- std dev: [master] 778 ns +- 17 ns -> [patched] 550 ns +- 24 ns: 1.42x faster (-29%)

----------
components: Interpreter Core
messages: 355536
nosy: inada.naoki
priority: normal
severity: normal
status: open
title: Optimize some set operations in dictkeys object
type: performance
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38613>
_______________________________________

From report at bugs.python.org  Mon Oct 28 07:57:25 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 28 Oct 2019 11:57:25 +0000
Subject: [issue38613] Optimize some set operations in dictkeys object
In-Reply-To: <1572263745.15.0.0692968844895.issue38613@roundup.psfhosted.org>
Message-ID: <1572263845.65.0.548249641498.issue38613@roundup.psfhosted.org>


Change by Inada Naoki <songofacandy at gmail.com>:


----------
keywords: +patch
pull_requests: +16489
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16961

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38613>
_______________________________________

From report at bugs.python.org  Mon Oct 28 08:18:15 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 12:18:15 +0000
Subject: [issue38614] test_asyncio: test_communicate() failed on AMD64 FreeBSD
 Shared 3.8
Message-ID: <1572265095.84.0.80833057987.issue38614@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

AMD64 FreeBSD Shared 3.8:
https://buildbot.python.org/all/#builders/374/builds/10

This buildbot worker is known to be very slow. It became even slower recently.


ERROR: test_communicate (test.test_asyncio.test_subprocess.SubprocessMultiLoopWatcherTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-564d/build/Lib/test/test_asyncio/test_subprocess.py", line 147, in test_communicate
    exitcode, stdout = self.loop.run_until_complete(task)
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-564d/build/Lib/asyncio/base_events.py", line 608, in run_until_complete
    return future.result()
  File "/usr/home/buildbot/python/3.8.koobs-freebsd-564d/build/Lib/asyncio/tasks.py", line 490, in wait_for
    raise exceptions.TimeoutError()
asyncio.exceptions.TimeoutError

Extract of the test:

    def test_communicate(self):
        args = PROGRAM_CAT

        async def run(data):
            proc = await asyncio.create_subprocess_exec(
                *args,
                stdin=subprocess.PIPE,
                stdout=subprocess.PIPE,
            )
            stdout, stderr = await proc.communicate(data)
            return proc.returncode, stdout

        task = run(b'some data')
        task = asyncio.wait_for(task, 60.0)
        exitcode, stdout = self.loop.run_until_complete(task)    # <==== HERE
        self.assertEqual(exitcode, 0)
        self.assertEqual(stdout, b'some data')

It seems like the test has an hardcoded timeout of 1 minute. The first thing that we can do is to increase this timeout to 5 minutes.

----------
components: Tests
messages: 355537
nosy: vstinner
priority: normal
severity: normal
status: open
title: test_asyncio: test_communicate() failed on AMD64 FreeBSD Shared 3.8
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38614>
_______________________________________

From report at bugs.python.org  Mon Oct 28 08:48:32 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 28 Oct 2019 12:48:32 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572266912.6.0.606456795759.issue38600@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

Ok, it's fine to me.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Mon Oct 28 09:04:25 2019
From: report at bugs.python.org (Richard Pausch)
Date: Mon, 28 Oct 2019 13:04:25 +0000
Subject: [issue38612] some non-ascii charcters link to same identifier/data
In-Reply-To: <1572260880.13.0.309355653543.issue38612@roundup.psfhosted.org>
Message-ID: <1572267865.7.0.028870987789.issue38612@roundup.psfhosted.org>


Change by Richard Pausch <r.pausch at hzdr.de>:


----------
components: +Unicode
nosy: +ezio.melotti, vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38612>
_______________________________________

From report at bugs.python.org  Mon Oct 28 09:21:05 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Mon, 28 Oct 2019 13:21:05 +0000
Subject: [issue38612] some non-ascii charcters link to same identifier/data
In-Reply-To: <1572260880.13.0.309355653543.issue38612@roundup.psfhosted.org>
Message-ID: <1572268865.27.0.054941502545.issue38612@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

This is an intentional feature: identifiers are normalised using NFKC normalization.

    py> from dis import dis
    py> dis(compile('?=1', '', 'single'))
      1           0 LOAD_CONST               0 (1)
                  3 STORE_NAME               0 (?)
                  6 LOAD_CONST               1 (None)
                  9 RETURN_VALUE
    py> from unicodedata import normalize
    py> normalize('NFKC', '?')
    '?'


So not a bug.

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38612>
_______________________________________

From report at bugs.python.org  Mon Oct 28 09:23:12 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Mon, 28 Oct 2019 13:23:12 +0000
Subject: [issue38612] some non-ascii charcters link to same identifier/data
In-Reply-To: <1572260880.13.0.309355653543.issue38612@roundup.psfhosted.org>
Message-ID: <1572268992.34.0.707653946817.issue38612@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Its also documented here:

https://docs.python.org/3/reference/lexical_analysis.html#identifiers

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38612>
_______________________________________

From report at bugs.python.org  Mon Oct 28 09:33:42 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 13:33:42 +0000
Subject: [issue38613] Optimize some set operations in dictkeys object
In-Reply-To: <1572263745.15.0.0692968844895.issue38613@roundup.psfhosted.org>
Message-ID: <1572269622.6.0.590523310363.issue38613@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

How does it work with dict subclasses?

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38613>
_______________________________________

From report at bugs.python.org  Mon Oct 28 09:58:01 2019
From: report at bugs.python.org (Jairo Llopis)
Date: Mon, 28 Oct 2019 13:58:01 +0000
Subject: [issue38615] imaplib has no timeout setting
Message-ID: <1572271081.51.0.380114547236.issue38615@roundup.psfhosted.org>


New submission from Jairo Llopis <yajo.sk8 at gmail.com>:

No way to pass a timeout to imaplib.IMAP4 or imaplib.IMAP4_SSL.

When opening the connection, the only way is to use socket.settimeout(), which affects the global execution environment.

It's interesting that poplib includes the needed timeout parameter instead... weird. I think it was forgotten for imaplib.

----------
components: Library (Lib)
messages: 355542
nosy: Jairo Llopis
priority: normal
severity: normal
status: open
title: imaplib has no timeout setting
type: enhancement
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38615>
_______________________________________

From report at bugs.python.org  Mon Oct 28 10:38:55 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 28 Oct 2019 14:38:55 +0000
Subject: [issue38615] imaplib has no timeout setting
In-Reply-To: <1572271081.51.0.380114547236.issue38615@roundup.psfhosted.org>
Message-ID: <1572273535.7.0.694200739449.issue38615@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +barry, maxking, r.david.murray

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38615>
_______________________________________

From report at bugs.python.org  Mon Oct 28 10:40:21 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 14:40:21 +0000
Subject: [issue37330] open(): remove 'U' mode, deprecated since Python 3.3
In-Reply-To: <1560872905.7.0.609892598407.issue37330@roundup.psfhosted.org>
Message-ID: <1572273621.34.0.909119330964.issue37330@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset e471e72977c83664f13d041c78549140c86c92de by Victor Stinner in branch 'master':
bpo-37330: open() no longer accept 'U' in file mode (GH-16959)
https://github.com/python/cpython/commit/e471e72977c83664f13d041c78549140c86c92de


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37330>
_______________________________________

From report at bugs.python.org  Mon Oct 28 10:40:57 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 14:40:57 +0000
Subject: [issue37330] open(): remove 'U' mode, deprecated since Python 3.3
In-Reply-To: <1560872905.7.0.609892598407.issue37330@roundup.psfhosted.org>
Message-ID: <1572273657.66.0.161667097226.issue37330@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Thanks for the review Serhiy ;-)

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37330>
_______________________________________

From report at bugs.python.org  Mon Oct 28 10:41:07 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 28 Oct 2019 14:41:07 +0000
Subject: [issue38616] Using Py_XDECREF to replace Py_DECREF in
 PyAST_FromNodeObject()
Message-ID: <1572273667.46.0.78113656156.issue38616@roundup.psfhosted.org>


New submission from hai shi <shihai1991 at 126.com>:

`if (c.c_normalize) {
     Py_DECREF(c.c_normalize);
}` 
--> 
`Py_XDECREF(c.c_normalize);`

----------
components: Interpreter Core
messages: 355545
nosy: shihai1991
priority: normal
severity: normal
status: open
title: Using Py_XDECREF to replace Py_DECREF in PyAST_FromNodeObject()
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38616>
_______________________________________

From report at bugs.python.org  Mon Oct 28 10:43:22 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 28 Oct 2019 14:43:22 +0000
Subject: [issue38616] Using Py_XDECREF to replace Py_DECREF in
 PyAST_FromNodeObject()
In-Reply-To: <1572273667.46.0.78113656156.issue38616@roundup.psfhosted.org>
Message-ID: <1572273802.68.0.55547361056.issue38616@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
keywords: +patch
pull_requests: +16490
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16962

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38616>
_______________________________________

From report at bugs.python.org  Mon Oct 28 10:43:52 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Mon, 28 Oct 2019 14:43:52 +0000
Subject: [issue38605] [typing] PEP 563: Postponed evaluation of annotations:
 enable it by default before Python 4.0
In-Reply-To: <1572192430.43.0.755831692199.issue38605@roundup.psfhosted.org>
Message-ID: <1572273832.2.0.0244986353243.issue38605@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

You can bring the deprecation schedule up on discourse or python-dev so more folks can let us know whether they'd be okay with 3.9 or 3.10.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38605>
_______________________________________

From report at bugs.python.org  Mon Oct 28 10:56:23 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 28 Oct 2019 14:56:23 +0000
Subject: [issue38617] Using Py_XINCREF to replace Py_INCREF in
 PyAST_CompileObject
Message-ID: <1572274583.69.0.135811249474.issue38617@roundup.psfhosted.org>


New submission from hai shi <shihai1991 at 126.com>:

1) param is unpredictable;
2) the compiler_free() use Py_XDECREF(c->c_filename) in PyAST_CompileObject();

----------
components: Interpreter Core
messages: 355547
nosy: shihai1991
priority: normal
severity: normal
status: open
title: Using Py_XINCREF to replace Py_INCREF in PyAST_CompileObject
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38617>
_______________________________________

From report at bugs.python.org  Mon Oct 28 10:59:12 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 28 Oct 2019 14:59:12 +0000
Subject: [issue38617] Using Py_XINCREF to replace Py_INCREF in
 PyAST_CompileObject
In-Reply-To: <1572274583.69.0.135811249474.issue38617@roundup.psfhosted.org>
Message-ID: <1572274752.79.0.0806699934841.issue38617@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
keywords: +patch
pull_requests: +16491
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16963

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38617>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:03:25 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 15:03:25 +0000
Subject: [issue38614] test_asyncio: test_communicate() failed on AMD64 FreeBSD
 Shared 3.8
In-Reply-To: <1572265095.84.0.80833057987.issue38614@roundup.psfhosted.org>
Message-ID: <1572275005.44.0.328179801772.issue38614@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16492
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16964

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38614>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:08:30 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 28 Oct 2019 15:08:30 +0000
Subject: [issue38618] Why not use refcount of c.c_filename in
 PyAST_FromNodeObject()
Message-ID: <1572275310.19.0.141379413528.issue38618@roundup.psfhosted.org>


New submission from hai shi <shihai1991 at 126.com>:

I don't know why don't use refcount
`
/* borrowed reference */
c.c_filename = filename;
`
in https://github.com/python/cpython/blob/master/Python/ast.c#L786-L787

like
`
Py_INCREF(filename);
c.c_filename = filename;
`
in https://github.com/python/cpython/blob/master/Python/compile.c#L333

----------
components: Interpreter Core
messages: 355548
nosy: shihai1991
priority: normal
severity: normal
status: open
title: Why not use refcount of c.c_filename in PyAST_FromNodeObject()
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38618>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:11:37 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 28 Oct 2019 15:11:37 +0000
Subject: [issue38618] Why not use refcount of c.c_filename in
 PyAST_FromNodeObject()
In-Reply-To: <1572275310.19.0.141379413528.issue38618@roundup.psfhosted.org>
Message-ID: <1572275497.31.0.888977568363.issue38618@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

Due to victor add the desc(`/* borrowed reference */`)
so noisy+ victor ;)

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38618>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:32:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 15:32:03 +0000
Subject: [issue38618] Why not use refcount of c.c_filename in
 PyAST_FromNodeObject()
In-Reply-To: <1572275310.19.0.141379413528.issue38618@roundup.psfhosted.org>
Message-ID: <1572276723.36.0.91051821254.issue38618@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Due to victor add the desc(`/* borrowed reference */`)

I added the comment, but the code was always like that.

In short, borrowed references are used to simply the implementation (avoid the need to DECREF on error) and/or for efficiency.

I don't understand the purpose of this issue. The bug tracker is not the right place to ask question. If you think that it's a bug, please explain how to trigger the bug.

I suggest to close the issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38618>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:38:40 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 15:38:40 +0000
Subject: [issue38618] Why not use refcount of c.c_filename in
 PyAST_FromNodeObject()
In-Reply-To: <1572275310.19.0.141379413528.issue38618@roundup.psfhosted.org>
Message-ID: <1572277120.61.0.946653007239.issue38618@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Because there is no need to use refcount.

And there is no need to use refcount in compile.c too.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38618>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:46:29 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 15:46:29 +0000
Subject: [issue38617] Using Py_XINCREF to replace Py_INCREF in
 PyAST_CompileObject
In-Reply-To: <1572274583.69.0.135811249474.issue38617@roundup.psfhosted.org>
Message-ID: <1572277589.7.0.858485704694.issue38617@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

The filename argument must be non-NULL. The code that uses c_filename requires this.

Py_XDECREF in compiler_free() could be replaced with Py_DECREF. But this is too tiny change which does not have significant effect.

Actually both Py_INCREF and Py_XDECREF could be removed.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38617>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:50:18 2019
From: report at bugs.python.org (Felipe)
Date: Mon, 28 Oct 2019 15:50:18 +0000
Subject: [issue38619] [Doc] UUID.hex is lowercase
Message-ID: <1572277818.51.0.346216542748.issue38619@roundup.psfhosted.org>


New submission from Felipe <felipe.nospam.ochoa at gmail.com>:

The hex property of `UUID` is implemented as `'%032x' % self.int`

Is it specified that this will always be lowercase? If so, can we add a note to the documentation indicating so?

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 355553
nosy: docs at python, fov
priority: normal
severity: normal
status: open
title: [Doc] UUID.hex is lowercase
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38619>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:53:30 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 15:53:30 +0000
Subject: [issue38616] Using Py_XDECREF to replace Py_DECREF in
 PyAST_FromNodeObject()
In-Reply-To: <1572273667.46.0.78113656156.issue38616@roundup.psfhosted.org>
Message-ID: <1572278010.24.0.132329890936.issue38616@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Both code are equivalent. There is reason to rewrite this. It would just increase code churn.

----------
nosy: +serhiy.storchaka
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38616>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:58:09 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 15:58:09 +0000
Subject: [issue38619] [Doc] UUID.hex is lowercase
In-Reply-To: <1572277818.51.0.346216542748.issue38619@roundup.psfhosted.org>
Message-ID: <1572278289.87.0.386584277102.issue38619@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

There are examples which show the hex is lowercase. I do not think a special note is needed. All conversions to hex are lowercase by default.

If you need uppercase, you can use str.upper().

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38619>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:58:59 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 15:58:59 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572278339.52.0.223235128078.issue28029@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

The current behavior is really surprising.

>>> "".replace("", "|")
'|'
>>> "".replace("", "|", -1)
'|'

vs

>>> "".replace("", "|", 0)
''
>>> "".replace("", "|", 1)
''
>>> "".replace("", "|", 1000)
''

I always expect "|".

---

This behavior makes sense to me:

>>> "abc".replace("", "|")
'|a|b|c|'
>>> "abc".replace("", "|", -1)
'|a|b|c|'
>>> "abc".replace("", "|", 0)
'abc'
>>> "abc".replace("", "|", 1)
'|abc'
>>> "abc".replace("", "|", 100)
'|a|b|c|'

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Mon Oct 28 11:59:23 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 15:59:23 +0000
Subject: [issue38617] Using Py_XINCREF to replace Py_INCREF in
 PyAST_CompileObject
In-Reply-To: <1572274583.69.0.135811249474.issue38617@roundup.psfhosted.org>
Message-ID: <1572278363.6.0.681157776189.issue38617@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> not a bug
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38617>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:04:27 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 16:04:27 +0000
Subject: [issue35448] ConfigParser .read() - handling of nonexistent files
In-Reply-To: <1544373330.85.0.788709270274.issue35448@psf.upfronthosting.co.za>
Message-ID: <1572278667.74.0.298450691583.issue35448@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> I would expect that this basic usage is very popular. If the file doesn't exist, the normal usage pattern fails in a confusing way: (...)

Well, the configparser is well defined. As you wrote: "If a file named in filenames cannot be opened, that file will be ignored."

You can check if the file exists or not by checking read() result:

"read(): (...) returning a list of filenames which were successfully parsed."
https://docs.python.org/dev/library/configparser.html#configparser.ConfigParser.read

I suggest to close this issue as "not a bug".

--

For me, a better option would be to be able to pass an open file to configparser. So the caller can decide how to handle the open() error.

----------
nosy: +vstinner

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35448>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:07:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 16:07:24 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572278844.54.0.116520895743.issue28029@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Well, in fact, I would expect that "".replace(...) would always return "": for any argument passed to replace().

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:16:57 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Mon, 28 Oct 2019 16:16:57 +0000
Subject: [issue37948] get_type_hints fails if there are un-annotated fields in
 a dataclass
In-Reply-To: <1566800952.19.0.982220665774.issue37948@roundup.psfhosted.org>
Message-ID: <1572279417.21.0.734134208431.issue37948@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

I'm not sure what can be done with this. The problem is that the decorator doesn't know what's in the caller's namespace. The type being added is "typing.Any". If the caller doesn't import typing, then get_type_hints will fail (as demonstrated here).

The only thing I can think of is using a type that's in builtins. "object" springs to mine, but of course that's semantically incorrect.

Or, maybe I could use "dataclasses.sys.modules['typing'].Any". I don't currently import sys (I don't think), but this should be a cheap import. Then if typing.get_type_hints() is called, we know typing will have already been importing.

But what if "dataclasses" isn't in the caller's namespace? I guess if I could find some way to navigate to sys.modules from __builtins__, that would largely work, absent playing games with builtins.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37948>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:17:21 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 16:17:21 +0000
Subject: [issue35448] ConfigParser .read() - handling of nonexistent files
In-Reply-To: <1544373330.85.0.788709270274.issue35448@psf.upfronthosting.co.za>
Message-ID: <1572279441.56.0.278766979231.issue35448@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

> There is a use case of this (which some of tools depends) about checking if configuration exists and if not, raising an error. Now, they can solve this by just adding check_exist argument.

No, it can be solved by using open() and read_file(). It can also be solved by checking the result of read(), as Victor suggested. Your proposition adds third way, but unlike to the first two it could be used only in new Python versions.

> Can you give an example of how this feature can/could break existing code?

You pass a list containing user configuration path, system-wide configuration path, and default configuration path (it can contain also per-directory configuration path). At first run of your program there is no user configuration file.

> For me, a better option would be to be able to pass an open file to configparser. So the caller can decide how to handle the open() error.

There is the read_file() method which accept an open file.

----------
resolution:  -> rejected
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35448>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:17:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 16:17:26 +0000
Subject: [issue38620] Shell python-config --includes returns the same path
 twice
Message-ID: <1572279446.17.0.15456686003.issue38620@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

When the shell script implementation of python-config was introduced, $PLATINCDIR variable was added:

commit 874211978c8097b8e747c90fa3ff41aacabe340f
Author: doko at python.org <doko at python.org>
Date:   Sat Jan 26 11:39:31 2013 +0100

    - Issue #16235: Implement python-config as a shell script.

...
+INCDIR="-I$includedir/python${VERSION}${ABIFLAGS}"
+PLATINCDIR="-I$includedir/python${VERSION}${ABIFLAGS}"
...
+        --includes)
+            echo "$INCDIR $PLATINCDIR"
+        ;;
+        --cflags)
+            echo "$INCDIR $PLATINCDIR $BASECFLAGS $CFLAGS $OPT"
+        ;;
...

But this variable is always equal to $INCDIR: it doesn't seem possible to change its value.

What is the purpose of emitting the same path twice?

Example on Fedora 30:

$ file /usr/bin/python3.8-x86_64-config 
/usr/bin/python3.8-x86_64-config: a /usr/bin/sh script, ..

$ /usr/bin/python3.8-x86_64-config --includes
-I/usr/include/python3.8 -I/usr/include/python3.8

=> /usr/include/python3.8 is giving twice

----------
components: Build
messages: 355561
nosy: doko, vstinner
priority: normal
severity: normal
status: open
title: Shell python-config --includes returns the same path twice
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38620>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:19:29 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 16:19:29 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572279569.41.0.736136089817.issue28029@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

What result would you expect of `"" in ""` and `"".count("")`?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:24:43 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Mon, 28 Oct 2019 16:24:43 +0000
Subject: [issue38336] Remove the __set__ method restriction on data
 descriptors for attribute lookup precedence
In-Reply-To: <1569930991.59.0.212656372364.issue38336@roundup.psfhosted.org>
Message-ID: <1572279883.09.0.46815141336.issue38336@roundup.psfhosted.org>


Change by G?ry <gery.ogam at gmail.com>:


----------
versions: +Python 3.8 -Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38336>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:42:22 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 28 Oct 2019 16:42:22 +0000
Subject: [issue38617] Using Py_XINCREF to replace Py_INCREF in
 PyAST_CompileObject
In-Reply-To: <1572274583.69.0.135811249474.issue38617@roundup.psfhosted.org>
Message-ID: <1572280942.63.0.850312740823.issue38617@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

Got it, thanks, Serhiy.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38617>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:47:43 2019
From: report at bugs.python.org (Fred Drake)
Date: Mon, 28 Oct 2019 16:47:43 +0000
Subject: [issue38621] Bad decoding of encoded-words in unstructured email
 headers
Message-ID: <1572281263.86.0.289924184677.issue38621@roundup.psfhosted.org>


New submission from Fred Drake <fdrake at gmail.com>:

I've encountered a problem parsing an email with this Subject: header:

Subject: Be sure to redeem your =?utf-8?Q?$?=201.71 credit card reward
 certificate by the end of the year

email._header_value_parser.get_unstructured defers to get_encoded_word, passing the argument

  '=?utf-8?Q?$?=201.71 credit card reward certificate by the end of the year'

get_encoded_word eventually calls email._encoded_words.decode with the argument

  '=?utf-8?Q?$?=201.71 credit card reward certificate by the end of the year?='

This doesn't seem right, but I'm unsure of the syntactic priority of =XX and ?= in this case.

The policy for this is email.policy.SMTP + email.policy.strict (not sure if that's ideal; I'm retrieving messages from mbox files and over IMAP).

----------
assignee: r.david.murray
messages: 355564
nosy: barry, fdrake, r.david.murray
priority: normal
severity: normal
status: open
title: Bad decoding of encoded-words in unstructured email headers

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38621>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:49:11 2019
From: report at bugs.python.org (Fred Drake)
Date: Mon, 28 Oct 2019 16:49:11 +0000
Subject: [issue38621] Bad decoding of encoded-words in unstructured email
 headers
In-Reply-To: <1572281263.86.0.289924184677.issue38621@roundup.psfhosted.org>
Message-ID: <1572281351.95.0.840110786703.issue38621@roundup.psfhosted.org>


Fred Drake <fdrake at gmail.com> added the comment:

It's worth noting that dealing with this header eventually causes the header parser to enter an infinite loop.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38621>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:50:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 16:50:02 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572281402.72.0.915493421409.issue28029@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> What result would you expect of `"" in ""` and `"".count("")`?

I don't suggest to change these operator and method:

>>> "" in ""
True
>>> "".count("")
1

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:51:07 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 28 Oct 2019 16:51:07 +0000
Subject: [issue38621] Bad decoding of encoded-words in unstructured email
 headers
In-Reply-To: <1572281263.86.0.289924184677.issue38621@roundup.psfhosted.org>
Message-ID: <1572281467.13.0.736031558631.issue38621@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +maxking

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38621>
_______________________________________

From report at bugs.python.org  Mon Oct 28 12:55:30 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Mon, 28 Oct 2019 16:55:30 +0000
Subject: [issue38619] [Doc] UUID.hex is lowercase
In-Reply-To: <1572277818.51.0.346216542748.issue38619@roundup.psfhosted.org>
Message-ID: <1572281730.29.0.718848220449.issue38619@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Yes, it's always guaranteed to be lowercase. I don't think it would hurt to mention lowercase briefly (like add just one word!).

----------
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38619>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:03:37 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 17:03:37 +0000
Subject: [issue38519] Internal include files missing on Windows
In-Reply-To: <1571423438.26.0.118785392888.issue38519@roundup.psfhosted.org>
Message-ID: <1572282217.21.0.419643301949.issue38519@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset edb172a87296d9359593a23cd9a09f5867ea1f0e by Steve Dower (Zackery Spytz) in branch 'master':
bpo-38519: Internal include files missing on Windows (GH-16921)
https://github.com/python/cpython/commit/edb172a87296d9359593a23cd9a09f5867ea1f0e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38519>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:04:04 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 Oct 2019 17:04:04 +0000
Subject: [issue38519] Internal include files missing on Windows
In-Reply-To: <1571423438.26.0.118785392888.issue38519@roundup.psfhosted.org>
Message-ID: <1572282244.15.0.534713251271.issue38519@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16493
pull_request: https://github.com/python/cpython/pull/16966

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38519>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:06:14 2019
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 28 Oct 2019 17:06:14 +0000
Subject: [issue38605] [typing] PEP 563: Postponed evaluation of annotations:
 enable it by default before Python 4.0
In-Reply-To: <1572192430.43.0.755831692199.issue38605@roundup.psfhosted.org>
Message-ID: <1572282374.49.0.310286917953.issue38605@roundup.psfhosted.org>


Change by Barry A. Warsaw <barry at python.org>:


----------
nosy: +barry

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38605>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:06:36 2019
From: report at bugs.python.org (hai shi)
Date: Mon, 28 Oct 2019 17:06:36 +0000
Subject: [issue38618] Why not use refcount of c.c_filename in
 PyAST_FromNodeObject()
In-Reply-To: <1572275310.19.0.141379413528.issue38618@roundup.psfhosted.org>
Message-ID: <1572282396.81.0.703155482715.issue38618@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

> I don't understand the purpose of this issue. The bug tracker is not the right place to ask question. If you think that it's a bug, please explain how to trigger the bug.

Hi, victor. What i want to express is that the refcount operation of filename should be same between ast.c and compile.c.

I am not sure i express it clearly. 

If the refcount of filename in ast.c is redundant as Serhiy said, maybe we should remove it? 

Hm, If we think it's fine, just keep it, i will close it soon.
And pls forgive me adding a noisy bpo again ;(

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38618>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:15:46 2019
From: report at bugs.python.org (Brett Cannon)
Date: Mon, 28 Oct 2019 17:15:46 +0000
Subject: [issue38593] Python 3.7 does not catch infinite recursion for some
 values of sys.getrecursionlimit()
In-Reply-To: <1572040268.11.0.31838216135.issue38593@roundup.psfhosted.org>
Message-ID: <1572282946.54.0.430921592884.issue38593@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

Can you provide a small reproducer? Otherwise the recursion check is mostly best effort if you have recursion in C code which never goes out to Python code where the recursion check is implemented.

----------
nosy: +brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38593>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:17:46 2019
From: report at bugs.python.org (Brett Cannon)
Date: Mon, 28 Oct 2019 17:17:46 +0000
Subject: [issue38611] ElementTree.ParseError does not implement SyntaxError
 interface as expected
In-Reply-To: <1572253875.02.0.816082787085.issue38611@roundup.psfhosted.org>
Message-ID: <1572283066.42.0.549290371107.issue38611@roundup.psfhosted.org>


Change by Brett Cannon <brett at python.org>:


----------
title: Bug in traceback.py -> ElementTree.ParseError does not implement SyntaxError interface as expected

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38611>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:23:13 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 Oct 2019 17:23:13 +0000
Subject: [issue38519] Internal include files missing on Windows
In-Reply-To: <1571423438.26.0.118785392888.issue38519@roundup.psfhosted.org>
Message-ID: <1572283393.26.0.571224958602.issue38519@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 07eee640cb3a4eaf1df942bc31a891e7517de763 by Miss Skeleton (bot) in branch '3.8':
bpo-38519: Internal include files missing on Windows (GH-16921)
https://github.com/python/cpython/commit/07eee640cb3a4eaf1df942bc31a891e7517de763


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38519>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:25:43 2019
From: report at bugs.python.org (daniel hahler)
Date: Mon, 28 Oct 2019 17:25:43 +0000
Subject: [issue17446] doctest test finder doesnt find line numbers of
 properties
In-Reply-To: <1363536507.07.0.43500928967.issue17446@psf.upfronthosting.co.za>
Message-ID: <1572283543.16.0.159161563283.issue17446@roundup.psfhosted.org>


daniel hahler <python-bugs at thequod.de> added the comment:

The PR appears to need a better test according to https://github.com/python/cpython/pull/3419#issuecomment-350570083.

----------
nosy: +blueyed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue17446>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:28:33 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 28 Oct 2019 17:28:33 +0000
Subject: [issue37330] open(): remove 'U' mode, deprecated since Python 3.3
In-Reply-To: <1560872905.7.0.609892598407.issue37330@roundup.psfhosted.org>
Message-ID: <1572283713.08.0.936670861873.issue37330@roundup.psfhosted.org>


Anthony Sottile <asottile at umich.edu> added the comment:

should we backport a documentation change for this? (the deprecatedremoved says 4.0 currently)

----------
nosy: +Anthony Sottile

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37330>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:33:52 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 17:33:52 +0000
Subject: [issue38453] ntpath.realpath() does not fully resolve relative paths
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1572284032.4.0.857388959357.issue38453@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
pull_requests: +16494
pull_request: https://github.com/python/cpython/pull/16967

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:35:38 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 17:35:38 +0000
Subject: [issue38453] ntpath.realpath() does not fully resolve relative paths
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1572284138.42.0.184152586025.issue38453@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

PR 16967 should fix the relative path resolution property, by joining with cwd if the original path is unprefixed and not absolute, and then joining with any symlink directories if their link is not absolute.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:44:02 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 17:44:02 +0000
Subject: [issue38453] ntpath.realpath() does not fully resolve relative paths
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1572284642.64.0.270587416668.issue38453@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

I also had to special-case "realpath('nul')" to maintain the behaviour that we deliberately maintained in another bug, and I think isabs() should always return true for "\\?\" prefixed paths (given that join() will promote a "\\?\" prefixed path to the root).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:49:28 2019
From: report at bugs.python.org (Fred Drake)
Date: Mon, 28 Oct 2019 17:49:28 +0000
Subject: [issue38619] [Doc] UUID.hex is lowercase
In-Reply-To: <1572277818.51.0.346216542748.issue38619@roundup.psfhosted.org>
Message-ID: <1572284968.82.0.156074096824.issue38619@roundup.psfhosted.org>


Fred Drake <fdrake at gmail.com> added the comment:

While I don't know Felipe's use case, I would expect the documentation to be clear that the representation won't change in the future so users will know that this can be relied on to generate keys into some other persistent structure.

----------
nosy: +fdrake

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38619>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:49:33 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 17:49:33 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572284973.14.0.610771086542.issue38589@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Thanks. Turns out it's a typo that's been around forever, but is really not obvious until you install Windows somewhere other than C:\Windows.

Apparently that's far less common than it used to be :)

We'll get it fixed in the next round of releases.

----------
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:50:37 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 17:50:37 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572285037.82.0.685815566087.issue38589@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
keywords: +patch
pull_requests: +16495
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16968

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:52:12 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 17:52:12 +0000
Subject: [issue38597] C Extension import limit
In-Reply-To: <1572119300.64.0.0138111717141.issue38597@roundup.psfhosted.org>
Message-ID: <1572285132.58.0.428157491474.issue38597@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

There is an implicit cap due to the C runtime (specifically vcruntime140.dll) allocating fibre local storage on load, which seems like the one you are hitting. However, we discovered this before the first 3.5 release and fixed it.

How are you compiling your packages? Or where are you getting them from?

It's possible that someone else is building and statically linking the C runtime, which will cause this, but distutils (and hence CPython) should not be doing it by default.

----------
components: +Distutils
nosy: +dstufft, eric.araujo

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38597>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:53:54 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 17:53:54 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1572285234.43.0.875105531065.issue38534@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 794616f837c254c68d8384ab48fb78123a3c8a8b by Steve Dower (benedwards14) in branch 'master':
bpo-38534: Replace wrong KB number references (GH-16955)
https://github.com/python/cpython/commit/794616f837c254c68d8384ab48fb78123a3c8a8b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:54:10 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 Oct 2019 17:54:10 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1572285250.69.0.733408313103.issue38534@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16496
pull_request: https://github.com/python/cpython/pull/16969

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Mon Oct 28 13:54:55 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 17:54:55 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1572285295.37.0.910323980411.issue38534@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Thanks for the fix!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Mon Oct 28 14:00:37 2019
From: report at bugs.python.org (Ashley Whetter)
Date: Mon, 28 Oct 2019 18:00:37 +0000
Subject: [issue34938] Fix mimetype.init() to account for from import
In-Reply-To: <1539036789.21.0.545547206417.issue34938@psf.upfronthosting.co.za>
Message-ID: <1572285637.29.0.702469430805.issue34938@roundup.psfhosted.org>


Ashley Whetter <ashley at awhetter.co.uk> added the comment:

Maybe updating the dictionaries isn't right at all.
I think if you were experienced enough you would have the intuition that mutable attributes like this are not going to change in your local scope if you import them into it. But relying on this knowledge makes it difficult for newer users. Plus we all make mistakes ;) So a note in the docs sounds like a good idea to me.

I think `init` does rebuild when `files` is `None` (https://github.com/python/cpython/blob/edb172a87296d9359593a23cd9a09f5867ea1f0e/Lib/mimetypes.py#L350) but it's not clear to me whether rebuilding should include any additional types registered with `add_type`. At the moment it says `the mapping will be added to the official MIME types`, but I think an additional note that this means that it will persist after subsequent calls to `init` would make that clear.

As for importing `init` into the local scope, I think ideally we wouldn't use `global` at all. We should be able to make `init` import `mimetypes` locally and explicitly access attributes on the module?
Another option is we make the module attributes accessible through a module level `__getattr__` which gets the attributes off of the global `Mimetypes` object stored in `mimetypes._db`. But that would still require usage of a `global _db`.

----------
nosy: +AWhetter

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34938>
_______________________________________

From report at bugs.python.org  Mon Oct 28 14:15:27 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 Oct 2019 18:15:27 +0000
Subject: [issue38534] Version 3.8.0 has released with a wrong MS KB number
 reference
In-Reply-To: <1571558364.86.0.253246786334.issue38534@roundup.psfhosted.org>
Message-ID: <1572286527.11.0.312024245292.issue38534@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset a4ee7abd2056c4956df45125fcf451a531247017 by Miss Skeleton (bot) in branch '3.8':
bpo-38534: Replace wrong KB number references (GH-16955)
https://github.com/python/cpython/commit/a4ee7abd2056c4956df45125fcf451a531247017


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38534>
_______________________________________

From report at bugs.python.org  Mon Oct 28 14:18:57 2019
From: report at bugs.python.org (tholl)
Date: Mon, 28 Oct 2019 18:18:57 +0000
Subject: [issue38622] _ctypes.dlsym (py_dl_sym) does not trigger audit hooks
Message-ID: <1572286737.48.0.245277798688.issue38622@roundup.psfhosted.org>


New submission from tholl <py at any.tholl.xyz>:

The dlsym operation generally (e.g. when done through a ctypes.CDLL object) triggers the "ctypes.dlsym" audit event. However, using _ctypes.dlsym directly does not trigger this event. This appears to be an oversight, given that _ctypes.dlopen *does* trigger the "ctypes.dlopen" audit event.

A (very minimal) patch is attached.

I was not entirely sure what format the DLL handle should take when it is passed to the audit function, so for now it just turns it back into a number via PyLong_FromVoidPtr (i.e. into the same format in which it is passed into _ctypes.dlsym in the first place).

----------
components: Extension Modules
files: audit.patch
keywords: patch
messages: 355583
nosy: tholl
priority: normal
severity: normal
status: open
title: _ctypes.dlsym (py_dl_sym) does not trigger audit hooks
versions: Python 3.8, Python 3.9
Added file: https://bugs.python.org/file48684/audit.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38622>
_______________________________________

From report at bugs.python.org  Mon Oct 28 14:30:27 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Mon, 28 Oct 2019 18:30:27 +0000
Subject: [issue38615] imaplib has no timeout setting
In-Reply-To: <1572271081.51.0.380114547236.issue38615@roundup.psfhosted.org>
Message-ID: <1572287427.65.0.324469645734.issue38615@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

I think this is a reasonable request. It would have to be a 3.9 feature.

Perhaps some code (and tests) can be stolen from poplib.

----------
nosy: +eric.smith
stage:  -> needs patch
versions:  -Python 3.5, Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38615>
_______________________________________

From report at bugs.python.org  Mon Oct 28 14:34:18 2019
From: report at bugs.python.org (Netzeband)
Date: Mon, 28 Oct 2019 18:34:18 +0000
Subject: [issue37838] typing.get_type_hints not working with
 forward-declaration and decorated functions
In-Reply-To: <1565692979.16.0.678723196671.issue37838@roundup.psfhosted.org>
Message-ID: <1572287658.32.0.774347193333.issue37838@roundup.psfhosted.org>


Netzeband <andre at netzeband.eu> added the comment:

Hello,

I'm very sorry, I was not able to find the time to finish the patch in the quality I wanted to have. So @benedwards14 please feel free to provide a pull request.

Best regards,
Andr?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37838>
_______________________________________

From report at bugs.python.org  Mon Oct 28 14:35:53 2019
From: report at bugs.python.org (Ian Good)
Date: Mon, 28 Oct 2019 18:35:53 +0000
Subject: [issue34975] start_tls() difficult when using asyncio.start_server()
In-Reply-To: <1539460993.6.0.788709270274.issue34975@psf.upfronthosting.co.za>
Message-ID: <1572287753.85.0.579357906586.issue34975@roundup.psfhosted.org>


Ian Good <icgood at gmail.com> added the comment:

#36889 was reverted, so this is not resolved.

I'm guessing this needs to be moved to 3.9 now too. Is my original PR worth revisiting? https://github.com/python/cpython/pull/13143/files

----------
resolution: fixed -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34975>
_______________________________________

From report at bugs.python.org  Mon Oct 28 14:49:42 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Mon, 28 Oct 2019 18:49:42 +0000
Subject: [issue34975] start_tls() difficult when using asyncio.start_server()
In-Reply-To: <1539460993.6.0.788709270274.issue34975@psf.upfronthosting.co.za>
Message-ID: <1572288582.36.0.178398540619.issue34975@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

I think it should be closed; Yuri thinks that current streams API is frozen for the sake of shiny brand new streams (don't exist yet).

----------
resolution:  -> wont fix
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34975>
_______________________________________

From report at bugs.python.org  Mon Oct 28 14:54:43 2019
From: report at bugs.python.org (Berry Schoenmakers)
Date: Mon, 28 Oct 2019 18:54:43 +0000
Subject: [issue38599] Deprecate creation of asyncio object when the loop is
 not running
In-Reply-To: <1572160085.79.0.39835517746.issue38599@roundup.psfhosted.org>
Message-ID: <1572288883.03.0.566974288324.issue38599@roundup.psfhosted.org>


Berry Schoenmakers <l.a.m.schoenmakers at tue.nl> added the comment:

The current implementation of asyncio.run() is focused quite a bit on one-shot use. After the call returns, the default event loop is even gone: calling asyncio.get_event_loop() gives "RuntimeError: There is no current event loop in thread 'MainThread'."

It would be nice if asyncio.run() uses the default loop if it's available (and not running), and that the default loop remains intact after the call returns. 

This way multiple calls to asyncio.run() that all use the default loop are supported, maybe using an asyncio.Queue (or whatever) across these calls---attaching everything to the same (default) loop.

I find this very useful, for instance when writing unit tests.

----------
nosy: +lschoe

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38599>
_______________________________________

From report at bugs.python.org  Mon Oct 28 15:07:49 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Mon, 28 Oct 2019 19:07:49 +0000
Subject: [issue38599] Deprecate creation of asyncio object when the loop is
 not running
In-Reply-To: <1572160085.79.0.39835517746.issue38599@roundup.psfhosted.org>
Message-ID: <1572289669.74.0.542530747409.issue38599@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

> It would be nice if asyncio.run() uses the default loop if it's available (and not running), and that the default loop remains intact after the call returns. 

Unfortunately it's not possible to implement that reliably and without a bunch of surprising behaviors.

Also, if you want the loop to be intact after asyncio.run, it means that you would not want to close it;that would defeat the purpose of asyncio.run.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38599>
_______________________________________

From report at bugs.python.org  Mon Oct 28 15:29:55 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 28 Oct 2019 19:29:55 +0000
Subject: [issue35448] ConfigParser .read() - handling of nonexistent files
In-Reply-To: <1544373330.85.0.788709270274.issue35448@psf.upfronthosting.co.za>
Message-ID: <1572290995.23.0.568961321225.issue35448@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

FWIW, I agree with closing this.  I already changed my mind from my earlier comment and decided that IDLE should maybe switch to using open and read_file in different places, for the reasons given above.  It might make testing without depending on a local config, which does not exist on buildbots, easier.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35448>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:13:04 2019
From: report at bugs.python.org (Larry Hastings)
Date: Mon, 28 Oct 2019 20:13:04 +0000
Subject: [issue31026] test_dbm fails when run directly
In-Reply-To: <1500984617.08.0.739686632306.issue31026@psf.upfronthosting.co.za>
Message-ID: <1572293584.84.0.881731683905.issue31026@roundup.psfhosted.org>


Larry Hastings <larry at hastings.org> added the comment:

For what it's worth, I'm cherry-picking this back into 3.5 for 3.5.8 final.  I (finally?) got bit by this, and since the patch is literally only changes in the Lib/test directory I consider it safe to merge even after 3.5.8rc2.  (I was in a bit of a hurry, I didn't use the Python cherry picker technology, I just used "git cherry-pick".)

----------
nosy: +larry

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31026>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:20:33 2019
From: report at bugs.python.org (Cooper Lees)
Date: Mon, 28 Oct 2019 20:20:33 +0000
Subject: [issue38483] [venv] Add ~/.venvrc to change module defaults
In-Reply-To: <1571136700.53.0.3102397559.issue38483@roundup.psfhosted.org>
Message-ID: <1572294033.33.0.0672827750554.issue38483@roundup.psfhosted.org>


Cooper Lees <me at cooperlees.com> added the comment:

Updated PR to use venv.ini. Will fix any CI errors encountered.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38483>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:46:16 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:46:16 +0000
Subject: [issue32092] mock.patch with autospec does not consume self / cls
 argument
In-Reply-To: <1511193021.31.0.213398074469.issue32092@psf.upfronthosting.co.za>
Message-ID: <1572295576.26.0.711385757982.issue32092@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32092>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:47:46 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:47:46 +0000
Subject: [issue38091] Import deadlock detection causes deadlock
In-Reply-To: <1568122000.74.0.240735069302.issue38091@roundup.psfhosted.org>
Message-ID: <1572295666.02.0.305221173927.issue38091@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38091>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:47:39 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:47:39 +0000
Subject: [issue7897] Support parametrized tests in unittest
In-Reply-To: <1265768482.24.0.694001982317.issue7897@psf.upfronthosting.co.za>
Message-ID: <1572295659.89.0.636641870989.issue7897@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue7897>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:47:42 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:47:42 +0000
Subject: [issue38384] An assertion failure in test_pickle
In-Reply-To: <1570369149.47.0.841206648458.issue38384@roundup.psfhosted.org>
Message-ID: <1572295662.79.0.811247088692.issue38384@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38384>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:47:37 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:47:37 +0000
Subject: [issue38122] AsyncMock force always creating an AsyncMock for child
 mocks
In-Reply-To: <1568222694.73.0.217906468671.issue38122@roundup.psfhosted.org>
Message-ID: <1572295657.26.0.909571910966.issue38122@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38122>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:48:21 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:48:21 +0000
Subject: [issue18108] shutil.chown should support dir_fd and follow_symlinks
 keyword arguments
In-Reply-To: <1370005797.04.0.715885093574.issue18108@psf.upfronthosting.co.za>
Message-ID: <1572295701.7.0.608018075286.issue18108@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue18108>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:48:12 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:48:12 +0000
Subject: [issue30587] Mock with spec object does not ensure method call
 signatures
In-Reply-To: <1496837046.98.0.920527641247.issue30587@psf.upfronthosting.co.za>
Message-ID: <1572295692.52.0.293132995402.issue30587@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30587>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:47:49 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:47:49 +0000
Subject: [issue38505] Mock.call_args and Mock.call_args_list not propagated to
 parent Mock
In-Reply-To: <1571315034.98.0.296986686038.issue38505@roundup.psfhosted.org>
Message-ID: <1572295669.34.0.499528936731.issue38505@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38505>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:48:16 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:48:16 +0000
Subject: [issue37052] Add examples for mocking async for and async context
 manager in unittest.mock docs
In-Reply-To: <1558857063.08.0.951093658338.issue37052@roundup.psfhosted.org>
Message-ID: <1572295696.35.0.796008227417.issue37052@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37052>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:48:08 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:48:08 +0000
Subject: [issue38494] Add assert_not_called_with
In-Reply-To: <1571206970.26.0.707248566898.issue38494@roundup.psfhosted.org>
Message-ID: <1572295688.44.0.631161841214.issue38494@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38494>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:48:25 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:48:25 +0000
Subject: [issue23882] unittest discovery doesn't detect namespace packages
 when given no parameters
In-Reply-To: <1428406596.02.0.0629964312505.issue23882@psf.upfronthosting.co.za>
Message-ID: <1572295705.83.0.41608881317.issue23882@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23882>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:48:31 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:48:31 +0000
Subject: [issue25299] argparse: TypeError: __init__() takes at least 4
 arguments (4 given)
In-Reply-To: <1443785146.27.0.85852377889.issue25299@psf.upfronthosting.co.za>
Message-ID: <1572295711.12.0.427284914817.issue25299@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue25299>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:48:34 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:48:34 +0000
Subject: [issue35617] unittest discover does not work with implicit namespaces
In-Reply-To: <1546162337.0.0.646769357962.issue35617@roundup.psfhosted.org>
Message-ID: <1572295714.58.0.299490103359.issue35617@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35617>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:48:40 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:48:40 +0000
Subject: [issue36723] Unittest Discovery for namespace subpackages dot
 notation fails
In-Reply-To: <1556219043.29.0.793780129066.issue36723@roundup.psfhosted.org>
Message-ID: <1572295720.2.0.136796967772.issue36723@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36723>
_______________________________________

From report at bugs.python.org  Mon Oct 28 16:48:53 2019
From: report at bugs.python.org (Phil Connell)
Date: Mon, 28 Oct 2019 20:48:53 +0000
Subject: [issue25597] unittest.mock does not wrap dunder methods (__getitem__
 etc)
In-Reply-To: <1447174958.96.0.448093662654.issue25597@psf.upfronthosting.co.za>
Message-ID: <1572295733.98.0.783930463985.issue25597@roundup.psfhosted.org>


Change by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue25597>
_______________________________________

From report at bugs.python.org  Mon Oct 28 17:27:58 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 21:27:58 +0000
Subject: [issue38494] Add assert_not_called_with
In-Reply-To: <1571206970.26.0.707248566898.issue38494@roundup.psfhosted.org>
Message-ID: <1572298078.52.0.893596759351.issue38494@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38494>
_______________________________________

From report at bugs.python.org  Mon Oct 28 17:34:31 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 21:34:31 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572298471.51.0.956852862056.issue38589@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:


New changeset 0ac6137dd3d1e2c8f9558153ad63021f57e05e73 by Steve Dower in branch 'master':
bpo-38589: Fixes HTML Help shortcut when Windows is not installed to C drive (GH-16968)
https://github.com/python/cpython/commit/0ac6137dd3d1e2c8f9558153ad63021f57e05e73


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Mon Oct 28 17:34:43 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 Oct 2019 21:34:43 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572298483.03.0.754779405411.issue38589@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16497
pull_request: https://github.com/python/cpython/pull/16970

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Mon Oct 28 17:34:52 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 Oct 2019 21:34:52 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572298492.42.0.72466344063.issue38589@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16498
pull_request: https://github.com/python/cpython/pull/16971

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Mon Oct 28 17:35:40 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 28 Oct 2019 21:35:40 +0000
Subject: [issue38618] Why not use refcount of c.c_filename in
 PyAST_FromNodeObject()
In-Reply-To: <1572275310.19.0.141379413528.issue38618@roundup.psfhosted.org>
Message-ID: <1572298540.19.0.442266796863.issue38618@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

There is no bug. We can add Py_INCREF/Py_DECREF in ast.c. We can remove Py_INCREF/Py_DECREF from compile.c. But all this would just add code churn.

----------
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38618>
_______________________________________

From report at bugs.python.org  Mon Oct 28 17:35:48 2019
From: report at bugs.python.org (Steve Dower)
Date: Mon, 28 Oct 2019 21:35:48 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572298548.48.0.0677773979663.issue38589@roundup.psfhosted.org>


Change by Steve Dower <steve.dower at python.org>:


----------
assignee:  -> steve.dower
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Mon Oct 28 17:47:48 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 28 Oct 2019 21:47:48 +0000
Subject: [issue38336] Remove the __set__ method restriction on data
 descriptors for attribute lookup precedence
In-Reply-To: <1569930991.59.0.212656372364.issue38336@roundup.psfhosted.org>
Message-ID: <1572299268.15.0.210047831601.issue38336@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee: docs at python -> rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38336>
_______________________________________

From report at bugs.python.org  Mon Oct 28 17:52:03 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 Oct 2019 21:52:03 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572299523.9.0.391407633278.issue38589@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 379b55b526a04e6db40c7070fd70f0d7d37bba64 by Miss Skeleton (bot) in branch '3.7':
bpo-38589: Fixes HTML Help shortcut when Windows is not installed to C drive (GH-16968)
https://github.com/python/cpython/commit/379b55b526a04e6db40c7070fd70f0d7d37bba64


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Mon Oct 28 17:52:39 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 28 Oct 2019 21:52:39 +0000
Subject: [issue38336] Remove the __set__ method restriction on data
 descriptors for attribute lookup precedence
In-Reply-To: <1569930991.59.0.212656372364.issue38336@roundup.psfhosted.org>
Message-ID: <1572299559.44.0.403308015173.issue38336@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
priority: normal -> low

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38336>
_______________________________________

From report at bugs.python.org  Mon Oct 28 17:55:13 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 28 Oct 2019 21:55:13 +0000
Subject: [issue38589] Bad target address assigned in Python Manuals shortcut
 on Python installation
In-Reply-To: <1572010579.06.0.155387350533.issue38589@roundup.psfhosted.org>
Message-ID: <1572299713.84.0.0983197818903.issue38589@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 2267cb9da4a1fd8bb4962beb893e1f69a37909a7 by Miss Skeleton (bot) in branch '3.8':
bpo-38589: Fixes HTML Help shortcut when Windows is not installed to C drive (GH-16968)
https://github.com/python/cpython/commit/2267cb9da4a1fd8bb4962beb893e1f69a37909a7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38589>
_______________________________________

From report at bugs.python.org  Mon Oct 28 18:09:45 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 28 Oct 2019 22:09:45 +0000
Subject: [issue37330] open(): remove 'U' mode, deprecated since Python 3.3
In-Reply-To: <1560872905.7.0.609892598407.issue37330@roundup.psfhosted.org>
Message-ID: <1572300585.01.0.448259809912.issue37330@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16499
pull_request: https://github.com/python/cpython/pull/16972

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37330>
_______________________________________

From report at bugs.python.org  Mon Oct 28 18:19:49 2019
From: report at bugs.python.org (Berry Schoenmakers)
Date: Mon, 28 Oct 2019 22:19:49 +0000
Subject: [issue38599] Deprecate creation of asyncio object when the loop is
 not running
In-Reply-To: <1572160085.79.0.39835517746.issue38599@roundup.psfhosted.org>
Message-ID: <1572301189.56.0.622024761127.issue38599@roundup.psfhosted.org>


Berry Schoenmakers <l.a.m.schoenmakers at tue.nl> added the comment:

Well, I'm basically using a run method defined as a shorthand for self.loop.run_until_complete (without closing loop, reusing it throughout). It would be nice if asyncio.run could simply be used instead, but I understand you're saying this is easier said than done, which is fine with me. Thanks.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38599>
_______________________________________

From report at bugs.python.org  Mon Oct 28 18:23:41 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Mon, 28 Oct 2019 22:23:41 +0000
Subject: [issue38599] Deprecate creation of asyncio object when the loop is
 not running
In-Reply-To: <1572160085.79.0.39835517746.issue38599@roundup.psfhosted.org>
Message-ID: <1572301421.26.0.421336657332.issue38599@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

> Well, I'm basically using a run method defined as a shorthand for self.loop.run_until_complete (without closing loop, reusing it throughout). It would be nice if asyncio.run could simply be used instead, but I understand you're saying this is easier said than done, which is fine with me. Thanks.

Yes. `asyncio.run()` is similar to `loop.run_until_complete()` but adds some guarantees + sane setup/cleanup. If we strip proper cleanup then there's no point in `asyncio.run()`.  So using `loop.run_until_complete()` is totally fine when you want to preserve the event loop between runs.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38599>
_______________________________________

From report at bugs.python.org  Mon Oct 28 18:39:25 2019
From: report at bugs.python.org (Peter Bittner)
Date: Mon, 28 Oct 2019 22:39:25 +0000
Subject: [issue38623] Python documentation should mention how to find
 site-packages
Message-ID: <1572302365.38.0.0160311403424.issue38623@roundup.psfhosted.org>


New submission from Peter Bittner <peter.bittner at gmx.net>:

A popular question on StackOverflow is, "How do I find the location of my Python site-packages directory?" [1]

While this may hint at a deeper problem that needs to be solved, a user suggested [2] the accepted answer to be added to Python's official documentation.

The most appropriate place I could find to add related information is ``Doc/tutorial/modules.rst``.

[1] https://stackoverflow.com/questions/122327/how-do-i-find-the-location-of-my-python-site-packages-directory/46071447
[2] https://stackoverflow.com/questions/122327/how-do-i-find-the-location-of-my-python-site-packages-directory/46071447#comment103247041_46071447

----------
assignee: docs at python
components: Documentation
messages: 355599
nosy: bittner, docs at python
priority: normal
severity: normal
status: open
title: Python documentation should mention how to find site-packages
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38623>
_______________________________________

From report at bugs.python.org  Mon Oct 28 18:45:51 2019
From: report at bugs.python.org (Peter Bittner)
Date: Mon, 28 Oct 2019 22:45:51 +0000
Subject: [issue38623] Python documentation should mention how to find
 site-packages
In-Reply-To: <1572302365.38.0.0160311403424.issue38623@roundup.psfhosted.org>
Message-ID: <1572302751.44.0.303855272068.issue38623@roundup.psfhosted.org>


Change by Peter Bittner <peter.bittner at gmx.net>:


----------
keywords: +patch
pull_requests: +16500
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16974

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38623>
_______________________________________

From report at bugs.python.org  Mon Oct 28 18:54:26 2019
From: report at bugs.python.org (Inyeol Lee)
Date: Mon, 28 Oct 2019 22:54:26 +0000
Subject: [issue38624] pathlib .suffix, .suffixes,
 .stem unexpected behavior for pathname with trailing dot
Message-ID: <1572303266.25.0.298826612475.issue38624@roundup.psfhosted.org>


New submission from Inyeol Lee <inyeol.lee at gmail.com>:

Python3.8 pathlib treats dot between path stem and suffix as part of suffix in general:

>>> a = pathlib.Path('foo.txt')
>>> a.stem, a.suffix
('foo', '.txt')
>>> a.with_suffix('')
PosixPath('foo')

However, if pathname ends with dot, it treats the trailing dot as part of stem, not part of suffix:

>>> b = pathlib.Path('bar.')
>>> b.stem, b.suffix
('bar.', '')

This looks like a bug. It should return ('bar', '.').
There are couple of unexpected behavior related to this:

>>> pathlib.Path('foo.txt').with_suffix('.')
...
ValueError: Invalid suffix '.' <== Why not PosixPath('foo.') ?
>>> c = pathlib.Path('foo..')
>>> c.stem, c.suffix, c.suffixes
('foo..', '', [])

I think above should return ('foo.', '.', ['.', '.'])

Tested with macOS 10.15 and Python3.8. Python3.7 behaves the same.

----------
components: Library (Lib)
messages: 355600
nosy: inyeollee
priority: normal
severity: normal
status: open
title: pathlib .suffix, .suffixes, .stem unexpected behavior for pathname with trailing dot
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38624>
_______________________________________

From report at bugs.python.org  Mon Oct 28 18:59:07 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Mon, 28 Oct 2019 22:59:07 +0000
Subject: [issue38599] Deprecate creation of asyncio object when the loop is
 not running
In-Reply-To: <1572160085.79.0.39835517746.issue38599@roundup.psfhosted.org>
Message-ID: <1572303547.74.0.351673328652.issue38599@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

I'm pretty happy with asyncio.run() functionalit.

I used run() for the bug demonstration, but the example can be rewritten easily without this function.

The problem is not in run() but in an object lifecycle. Implicit loop creation plus module-level initialization provides a pretty big set of ways to shoot in the foot :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38599>
_______________________________________

From report at bugs.python.org  Mon Oct 28 19:25:13 2019
From: report at bugs.python.org (Graham Coster)
Date: Mon, 28 Oct 2019 23:25:13 +0000
Subject: [issue38625] SpooledTemporaryFile does not seek correctly after being
 rolled over
Message-ID: <1572305113.57.0.424265086892.issue38625@roundup.psfhosted.org>


Change by Graham Coster <graham_coster999 at yahoo.co.uk>:


----------
components: Library (Lib)
files: spooled-temp-file-does-not-seek-correctly-after-being-rolled.py
nosy: Gary Fernie, James Hennessy, graham.coster, inada.naoki, martin.panter, nubirstein, r.david.murray, serhiy.storchaka, terry.reedy
priority: normal
severity: normal
status: open
title: SpooledTemporaryFile does not seek correctly after being rolled over
type: behavior
versions: Python 3.7
Added file: https://bugs.python.org/file48685/spooled-temp-file-does-not-seek-correctly-after-being-rolled.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38625>
_______________________________________

From report at bugs.python.org  Mon Oct 28 19:46:46 2019
From: report at bugs.python.org (Graham Coster)
Date: Mon, 28 Oct 2019 23:46:46 +0000
Subject: [issue38625] SpooledTemporaryFile does not seek correctly after being
 rolled over
Message-ID: <1572306406.72.0.0542092082155.issue38625@roundup.psfhosted.org>


New submission from Graham Coster <graham_coster999 at yahoo.co.uk>:

Hi there,

As demonstrated in the attached script, I found that a StopIteration exception occurs once a SpooledTemporaryFile has been rolled over from memory to disk, even though seek(0) had move the file position to the top of the file.

I had previously been using a TemporaryFile, which wrote directly to disk, without any issues.  However, once I swapped to a SpooledTemporaryFile, the StopIteration exception started to appear.  

I'm guessing the problem relates to the csv reader having an Iterator that is no longer looking at the correct file after the SpooledTemporaryFile is rolled-over.  I found that instantiating a new csv reader post roll-over works around the problem.

I had expected that I could just swap from a TemporaryFile to a SpooledTemporaryFile with no change to behaviour. However, if this is not the case, perhaps the SpooledTemporaryFile documentation should explicitly state this.

Cheers, Graham.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38625>
_______________________________________

From report at bugs.python.org  Mon Oct 28 20:07:13 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Tue, 29 Oct 2019 00:07:13 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572307633.3.0.503179691667.issue34790@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
pull_requests: +16502
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16975

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Mon Oct 28 20:10:28 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Tue, 29 Oct 2019 00:10:28 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572307828.03.0.936936259391.issue34790@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

GH-16975 Is a simple fix for the asyncio.wait() whatsnew entry for 3.8. I'll implement the deprecation warning and add a 3.9 whatsnew entry in a separate PR, since those changes won't be backported.

----------
stage: patch review -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Mon Oct 28 20:13:04 2019
From: report at bugs.python.org (Daniel Hillier)
Date: Tue, 29 Oct 2019 00:13:04 +0000
Subject: [issue38334] zipfile: Seeking encrypted file breaks after seeking
 backwards
In-Reply-To: <1569917842.05.0.044912868688.issue38334@roundup.psfhosted.org>
Message-ID: <1572307984.4.0.71159624525.issue38334@roundup.psfhosted.org>


Daniel Hillier <daniel.hillier at gmail.com> added the comment:

Thanks for your help! Good point, I'll create a new change for the refactoring.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38334>
_______________________________________

From report at bugs.python.org  Mon Oct 28 21:56:30 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Tue, 29 Oct 2019 01:56:30 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572314190.46.0.278742124571.issue34790@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
pull_requests: +16503
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16977

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Mon Oct 28 21:59:29 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 29 Oct 2019 01:59:29 +0000
Subject: [issue38624] pathlib .suffix, .suffixes,
 .stem unexpected behavior for pathname with trailing dot
In-Reply-To: <1572303266.25.0.298826612475.issue38624@roundup.psfhosted.org>
Message-ID: <1572314369.33.0.389932414986.issue38624@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +pitrou

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38624>
_______________________________________

From report at bugs.python.org  Mon Oct 28 21:59:34 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Tue, 29 Oct 2019 01:59:34 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572314374.33.0.654785851965.issue34790@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

GH-16977 Implements the deprecation warning, adds tests, and adds the 3.9 whatsnew entry. Once this PR is finalized, I think this issue can be closed.

----------
stage: patch review -> 

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Mon Oct 28 22:44:07 2019
From: report at bugs.python.org (Windson Yang)
Date: Tue, 29 Oct 2019 02:44:07 +0000
Subject: [issue38125] Can' build document in Sphinx v2.2.0
In-Reply-To: <1568246312.85.0.271143869481.issue38125@roundup.psfhosted.org>
Message-ID: <1572317047.32.0.822656868797.issue38125@roundup.psfhosted.org>


Change by Windson Yang <wiwindson at outlook.com>:


----------
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38125>
_______________________________________

From report at bugs.python.org  Mon Oct 28 23:03:16 2019
From: report at bugs.python.org (Windson Yang)
Date: Tue, 29 Oct 2019 03:03:16 +0000
Subject: [issue38626] small change at bisect_left function for easy
 understanding
Message-ID: <1572318196.84.0.0964323507502.issue38626@roundup.psfhosted.org>


New submission from Windson Yang <wiwindson at outlook.com>:

bisect_left should be similar to bisect_right. However, the current implement didn't reflect it. A little bit update for the bisect_left function could make the user easy to understand their relation.

def bisect_left(a, x, lo=0, hi=None):
    if lo < 0:
        raise ValueError('lo must be non-negative')
    if hi is None:
        hi = len(a)
    while lo < hi:
        mid = (lo+hi)//2
        # <= should be the only difference between bisect_left and bisect_right
        if x <= a[mid]: hi = mid
        else: lo = mid+1
    return lo

----------
components: Library (Lib)
messages: 355606
nosy: Windson Yang
priority: normal
severity: normal
status: open
title: small change at bisect_left function for easy understanding
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38626>
_______________________________________

From report at bugs.python.org  Mon Oct 28 23:26:53 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 03:26:53 +0000
Subject: [issue38626] small change at bisect_left function for easy
 understanding
In-Reply-To: <1572318196.84.0.0964323507502.issue38626@roundup.psfhosted.org>
Message-ID: <1572319613.94.0.640454383627.issue38626@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
assignee:  -> rhettinger
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38626>
_______________________________________

From report at bugs.python.org  Mon Oct 28 23:27:53 2019
From: report at bugs.python.org (Tim Peters)
Date: Tue, 29 Oct 2019 03:27:53 +0000
Subject: [issue38626] small change at bisect_left function for easy
 understanding
In-Reply-To: <1572318196.84.0.0964323507502.issue38626@roundup.psfhosted.org>
Message-ID: <1572319673.55.0.716322154278.issue38626@roundup.psfhosted.org>


Tim Peters <tim at python.org> added the comment:

So as far as possible, CPython only uses __lt__ ("<") element comparisons for its order-sensitive algorithms.  This is documented for list.sort(), but the bisect and heapq modules strive to do the same.

The point is to minimize the number of comparison methods a new type needs to implement to participate (and "just one:  __lt__" is ideal).

Your change would require they implement "__le__" too, so is unlikely to be accepted for CPython.

----------
assignee: rhettinger -> 
nosy: +tim.peters -rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38626>
_______________________________________

From report at bugs.python.org  Mon Oct 28 23:30:28 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 03:30:28 +0000
Subject: [issue38626] small change at bisect_left function for easy
 understanding
In-Reply-To: <1572318196.84.0.0964323507502.issue38626@roundup.psfhosted.org>
Message-ID: <1572319828.86.0.767404501973.issue38626@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

I concur with Tim.

Thank you for the suggestion though.

----------
nosy: +rhettinger
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38626>
_______________________________________

From report at bugs.python.org  Mon Oct 28 23:43:04 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 03:43:04 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572320584.69.0.398647561916.issue34790@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Is this whatsnew/3.8.rst entry correct and complete?

'''
The :func:`asyncio.coroutine` :term:`decorator` is deprecated and will be removed in version 3.10.  Instead of ``@asyncio.coroutine``, use :keyword:`async def` instead. (Contributed by Andrew Svetlov in :issue:`36921`.)
'''

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Tue Oct 29 00:06:36 2019
From: report at bugs.python.org (hai shi)
Date: Tue, 29 Oct 2019 04:06:36 +0000
Subject: [issue38618] Why not use refcount of c.c_filename in
 PyAST_FromNodeObject()
In-Reply-To: <1572275310.19.0.141379413528.issue38618@roundup.psfhosted.org>
Message-ID: <1572321996.24.0.192352267574.issue38618@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

Thanks for your patience, Serhiy.

IMHO, i called the moving operation `clean code`: Consistent understanding, Consistent code. And the `clean code` should be a part of `enhancement`.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38618>
_______________________________________

From report at bugs.python.org  Tue Oct 29 00:19:32 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 04:19:32 +0000
Subject: [issue38626] small change at bisect_left function for easy
 understanding
In-Reply-To: <1572318196.84.0.0964323507502.issue38626@roundup.psfhosted.org>
Message-ID: <1572322772.86.0.505774781131.issue38626@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
pull_requests: +16504
pull_request: https://github.com/python/cpython/pull/16978

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38626>
_______________________________________

From report at bugs.python.org  Tue Oct 29 00:32:44 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Tue, 29 Oct 2019 04:32:44 +0000
Subject: [issue34790] Deprecate passing coroutine objects to asyncio.wait()
In-Reply-To: <1537807353.36.0.956365154283.issue34790@psf.upfronthosting.co.za>
Message-ID: <1572323564.28.0.622542129885.issue34790@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> Is this whatsnew/3.8.rst entry correct and complete?

> The :func:`asyncio.coroutine` :term:`decorator` is deprecated and will be removed in version 3.10.  Instead of ``@asyncio.coroutine``, use :keyword:`async def` instead. (Contributed by Andrew Svetlov in :issue:`36921`.)

It looks to be fully consistent with the asyncio docs: https://docs.python.org/3/library/asyncio-task.html#generator-based-coroutines. From the blame of the documentation, it seems like Yury added the deprecation notice (GH-9314) to that section with the listed release for removal as 4.0, and then changed it to 3.10 (GH-9579). At a later date, Andrew implemented the actual deprecation (GH-13346).

So as far as I can tell, yes.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue34790>
_______________________________________

From report at bugs.python.org  Tue Oct 29 00:38:56 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 Oct 2019 04:38:56 +0000
Subject: [issue38626] small change at bisect_left function for easy
 understanding
In-Reply-To: <1572318196.84.0.0964323507502.issue38626@roundup.psfhosted.org>
Message-ID: <1572323936.5.0.0758073080522.issue38626@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 3c88199e0be352c0813f145d7c4c83af044268aa by Miss Skeleton (bot) (Raymond Hettinger) in branch 'master':
bpo-38626:  Add comment explaining why __lt__ is used. (GH-16978)
https://github.com/python/cpython/commit/3c88199e0be352c0813f145d7c4c83af044268aa


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38626>
_______________________________________

From report at bugs.python.org  Tue Oct 29 01:37:09 2019
From: report at bugs.python.org (Wei-Cheng Pan)
Date: Tue, 29 Oct 2019 05:37:09 +0000
Subject: [issue38608] Undocumented behavior that IsolatedAsyncioTestCase would
 enable event loop debug mode
In-Reply-To: <1572227413.17.0.184690601558.issue38608@roundup.psfhosted.org>
Message-ID: <1572327429.65.0.75102531081.issue38608@roundup.psfhosted.org>


Wei-Cheng Pan <legnaleurc at gmail.com> added the comment:

> Usually, it is a sign of a problem in user code, e.g. something should be pushed into executor.

Sometimes also happens on low-end CI machines.

And the message is somewhat unclear to me.
I have to grep cpython sources to understand that it is coming from debug mode and it means there is a slow awaitable ... in somewhere, because the displayed file:line is not always the right position.

> A test case is executed in debug mode. I think it is reasonable for the test run, isn't it?

Probably.

> The mode can be disabled by `asyncio.get_running_loop().set_debug(False)` in `asyncSetUp()` method.

Glad to know that. Thanks.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38608>
_______________________________________

From report at bugs.python.org  Tue Oct 29 01:40:18 2019
From: report at bugs.python.org (Larry Hastings)
Date: Tue, 29 Oct 2019 05:40:18 +0000
Subject: [issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py
In-Reply-To: <1569032250.18.0.545337961077.issue38243@roundup.psfhosted.org>
Message-ID: <1572327618.63.0.0615071165989.issue38243@roundup.psfhosted.org>


Larry Hastings <larry at hastings.org> added the comment:


New changeset 3fe1b19265b55c290fc956e9aafcf661803782de by larryhastings (Victor Stinner) in branch '3.5':
bpo-38243, xmlrpc.server: Escape the server_title (GH-16373) (GH-16441) (#16516)
https://github.com/python/cpython/commit/3fe1b19265b55c290fc956e9aafcf661803782de


----------
nosy: +larry

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38243>
_______________________________________

From report at bugs.python.org  Tue Oct 29 01:43:00 2019
From: report at bugs.python.org (Larry Hastings)
Date: Tue, 29 Oct 2019 05:43:00 +0000
Subject: [issue38243] A reflected XSS in python/Lib/DocXMLRPCServer.py
In-Reply-To: <1569032250.18.0.545337961077.issue38243@roundup.psfhosted.org>
Message-ID: <1572327780.69.0.981087928686.issue38243@roundup.psfhosted.org>


Change by Larry Hastings <larry at hastings.org>:


----------
resolution:  -> fixed
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38243>
_______________________________________

From report at bugs.python.org  Tue Oct 29 01:46:54 2019
From: report at bugs.python.org (Daniel Hillier)
Date: Tue, 29 Oct 2019 05:46:54 +0000
Subject: [issue37523] zipfile: Raise ValueError for i/o operations on closed
 zipfile.ZipExtFile
In-Reply-To: <1562656011.62.0.508019848995.issue37523@roundup.psfhosted.org>
Message-ID: <1572328014.34.0.723678747799.issue37523@roundup.psfhosted.org>


Daniel Hillier <daniel.hillier at gmail.com> added the comment:

Here's the script I used for profiling and the results I observed with and without the closed check in read:

import zipfile

test_zip = "time_test.zip"
test_name = "test_name.txt"

with zipfile.ZipFile(test_zip, "w") as zf:
    zf.writestr(test_name, "Hi there! " * 300)

with zipfile.ZipFile(test_zip) as zf:
    for i in range(100000):
        zf.read(test_name)

# Current code (no closed check), three different profiling sessions:
# ncalls  tottime  percall  cumtime  percall filename:lineno(function)
# 100000    0.612    0.000    6.638    0.000 zipfile.py:884(read)
# 100000    0.598    0.000    6.489    0.000 zipfile.py:884(read)
# 100000    0.600    0.000    6.485    0.000 zipfile.py:884(read)

# With closed check, three different profiling sessions:
# ncalls  tottime  percall  cumtime  percall filename:lineno(function)
# 100000    0.632    0.000    6.587    0.000 zipfile.py:884(read)
# 100000    0.623    0.000    6.564    0.000 zipfile.py:884(read)
# 100000    0.638    0.000    6.700    0.000 zipfile.py:884(read)

-------

I based this change on the what BytesIO does: https://github.com/python/cpython/blob/master/Lib/_pyio.py#L912

Let me know if you want me to make any changes.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37523>
_______________________________________

From report at bugs.python.org  Tue Oct 29 01:55:17 2019
From: report at bugs.python.org (Sebastian Linke)
Date: Tue, 29 Oct 2019 05:55:17 +0000
Subject: [issue38627] Add copy() method to pathlib
Message-ID: <1572328517.33.0.0527318368455.issue38627@roundup.psfhosted.org>


New submission from Sebastian Linke <Seb_Linke at arcor.de>:

pathlib.Path() could wrap shutil.copy() with something like this:

def copy(self, target):
    if not self.is_file():
        # No support for directories here
        raise ValueError("Path must point to a regular file")
    # copy() appends filename when Path is copied to a directory
    # see shutil.copy() docstring and source for details
    target = shutil.copy(self, target)
    return self.__class__(target)

----------
components: Library (Lib)
messages: 355616
nosy: seblin
priority: normal
severity: normal
status: open
title: Add copy() method to pathlib
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38627>
_______________________________________

From report at bugs.python.org  Tue Oct 29 02:04:06 2019
From: report at bugs.python.org (Sebastian Linke)
Date: Tue, 29 Oct 2019 06:04:06 +0000
Subject: [issue38627] Add copy() method to pathlib
In-Reply-To: <1572328517.33.0.0527318368455.issue38627@roundup.psfhosted.org>
Message-ID: <1572329046.66.0.654237403291.issue38627@roundup.psfhosted.org>


Sebastian Linke <Seb_Linke at arcor.de> added the comment:

Docstring could be:

Copy file content and permission bits of this path to the target path
and return a new Path instance pointing to the target path.
If target is a directory, the base filename of this path is added to
the target and a new file corresponding to the target is created.
If target points to an existing file, that file is overwritten.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38627>
_______________________________________

From report at bugs.python.org  Tue Oct 29 02:20:01 2019
From: report at bugs.python.org (Inada Naoki)
Date: Tue, 29 Oct 2019 06:20:01 +0000
Subject: [issue38613] Optimize some set operations in dictkeys object
In-Reply-To: <1572263745.15.0.0692968844895.issue38613@roundup.psfhosted.org>
Message-ID: <1572330001.19.0.181131545221.issue38613@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

> How does it work with dict subclasses?

PySet_New(iterable) uses fast path only when `PyDict_CheckExact(iterable)` is true.

So there is no change for dict subclasses.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38613>
_______________________________________

From report at bugs.python.org  Tue Oct 29 02:45:21 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 06:45:21 +0000
Subject: [issue38613] Optimize some set operations in dictkeys object
In-Reply-To: <1572263745.15.0.0692968844895.issue38613@roundup.psfhosted.org>
Message-ID: <1572331521.05.0.849202729717.issue38613@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

But what if a dict subclass overrides __iter__? You can get different result if set(d) != set(d.keys()).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38613>
_______________________________________

From report at bugs.python.org  Tue Oct 29 02:52:53 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 06:52:53 +0000
Subject: [issue38627] Add copy() method to pathlib
In-Reply-To: <1572328517.33.0.0527318368455.issue38627@roundup.psfhosted.org>
Message-ID: <1572331973.22.0.905013081203.issue38627@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Since shutil.copy() accepts path-like object, I do not think there is a need to add the copy method to Path.

As for additional limitation, it looks arbitrary and application specific. You can easy implement a simple helper function as you just demonstrated. And you can easily modify it if your needs change (for example if you decide to not copy links). Not every three lines of code should be added as a function to the stdlib.

----------
nosy: +serhiy.storchaka
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38627>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:01:37 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 07:01:37 +0000
Subject: [issue37523] zipfile: Raise ValueError for i/o operations on closed
 zipfile.ZipExtFile
In-Reply-To: <1562656011.62.0.508019848995.issue37523@roundup.psfhosted.org>
Message-ID: <1572332497.45.0.439587820519.issue37523@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Thank you Daniel. But profiling is not good for benchmarking, it adds too much overhead. It can help to find narrow places, but for measuring effect of optimization you need to measure the raw time on non-debug build.

Semantically your changes are correct. I just want to know whether this adds a significant overhead. If it is, we should consider some kind of optimizations. It does not matter for Python implementation of BytesIO because in normal we use the C implementation.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37523>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:04:07 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 07:04:07 +0000
Subject: [issue38336] Remove the __set__ method restriction on data
 descriptors for attribute lookup precedence
In-Reply-To: <1569930991.59.0.212656372364.issue38336@roundup.psfhosted.org>
Message-ID: <1572332647.21.0.270400081295.issue38336@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:


New changeset 4c155f738dc2e70ccb574f5169ad89c01753c6f7 by Raymond Hettinger (G?ry Ogam) in branch 'master':
bpo-38336: Remove the __set__ method restriction on data descriptors for attribute lookup precedence (GH-16520)
https://github.com/python/cpython/commit/4c155f738dc2e70ccb574f5169ad89c01753c6f7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38336>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:04:33 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 07:04:33 +0000
Subject: [issue38336] Remove the __set__ method restriction on data
 descriptors for attribute lookup precedence
In-Reply-To: <1569930991.59.0.212656372364.issue38336@roundup.psfhosted.org>
Message-ID: <1572332673.91.0.409089496315.issue38336@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38336>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:24:21 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 07:24:21 +0000
Subject: [issue36993] zipfile: tuple IndexError on extract
In-Reply-To: <1558441969.28.0.928640082083.issue36993@roundup.psfhosted.org>
Message-ID: <1572333861.81.0.863921736139.issue36993@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset da6ce58dd5ac109485af45878fca6bfd265b43e9 by Serhiy Storchaka (Daniel Hillier) in branch 'master':
bpo-36993: Improve error reporting for zipfiles with bad zip64 extra data. (GH-14656)
https://github.com/python/cpython/commit/da6ce58dd5ac109485af45878fca6bfd265b43e9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36993>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:25:54 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 Oct 2019 07:25:54 +0000
Subject: [issue36993] zipfile: tuple IndexError on extract
In-Reply-To: <1558441969.28.0.928640082083.issue36993@roundup.psfhosted.org>
Message-ID: <1572333954.66.0.852786426145.issue36993@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16505
pull_request: https://github.com/python/cpython/pull/16979

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36993>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:26:02 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 Oct 2019 07:26:02 +0000
Subject: [issue36993] zipfile: tuple IndexError on extract
In-Reply-To: <1558441969.28.0.928640082083.issue36993@roundup.psfhosted.org>
Message-ID: <1572333962.28.0.449215356716.issue36993@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16506
pull_request: https://github.com/python/cpython/pull/16980

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36993>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:34:04 2019
From: report at bugs.python.org (ttrd)
Date: Tue, 29 Oct 2019 07:34:04 +0000
Subject: [issue38541] Performance degradation of attribute accesses in Python
 3.7.4
In-Reply-To: <1571645744.43.0.285485842632.issue38541@roundup.psfhosted.org>
Message-ID: <1572334444.97.0.934977363245.issue38541@roundup.psfhosted.org>


ttrd <randy.doering at tracetronic.de> added the comment:

I just ran the test with Python 3.7.5: As expected, I got the same results as in Python 3.7.4.

Nevertheless, thanks for the response. So we will stay with Python 3.7.3 for now and switch to Python 3.8 as soon as possible.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38541>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:40:26 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 07:40:26 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572334826.88.0.896710728956.issue28029@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16507
pull_request: https://github.com/python/cpython/pull/16981

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:43:40 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 Oct 2019 07:43:40 +0000
Subject: [issue36993] zipfile: tuple IndexError on extract
In-Reply-To: <1558441969.28.0.928640082083.issue36993@roundup.psfhosted.org>
Message-ID: <1572335020.7.0.0554033758006.issue36993@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset f7d50f8f997fbfce1556991a3700826536871fe7 by Miss Skeleton (bot) in branch '3.7':
bpo-36993: Improve error reporting for zipfiles with bad zip64 extra data. (GH-14656)
https://github.com/python/cpython/commit/f7d50f8f997fbfce1556991a3700826536871fe7


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36993>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:44:10 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 Oct 2019 07:44:10 +0000
Subject: [issue36993] zipfile: tuple IndexError on extract
In-Reply-To: <1558441969.28.0.928640082083.issue36993@roundup.psfhosted.org>
Message-ID: <1572335050.38.0.380097826281.issue36993@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 3801b2699eb9441ca31c6ec8fa956fc0fe755ef7 by Miss Skeleton (bot) in branch '3.8':
bpo-36993: Improve error reporting for zipfiles with bad zip64 extra data. (GH-14656)
https://github.com/python/cpython/commit/3801b2699eb9441ca31c6ec8fa956fc0fe755ef7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36993>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:56:20 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 07:56:20 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572335780.0.0.310767073177.issue28029@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

There are expected some relations between str methods. For example,

s.replace(a, b, n) == s.replace(a, b)   if n >= s.count(a)
len(s.replace(a, b, n)) == len(s) + (len(b)-len(a)) * n   if 0 <= n <= s.count(a)
len(s.replace(a, b, n)) == len(s) + (len(b)-len(a)) * s.count(a)   if n >= s.count(a)

Inconsistency between "".replace("", s, n) and "".replace("", s) is just a bug, and it should be fixed in the most consistent way. There are precedences, the behavior of replace() already was changed 3 times in the past. I think that chances to break some code are tiny, we just fix inconsistency why can puzzle users.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Tue Oct 29 03:57:37 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 07:57:37 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572335857.9.0.348917020328.issue28029@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Note that no tests were affected by this change.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Tue Oct 29 04:00:50 2019
From: report at bugs.python.org (Larry Hastings)
Date: Tue, 29 Oct 2019 08:00:50 +0000
Subject: [issue31026] test_dbm fails when run directly
In-Reply-To: <1500984617.08.0.739686632306.issue31026@psf.upfronthosting.co.za>
Message-ID: <1572336050.79.0.787771708165.issue31026@roundup.psfhosted.org>


Larry Hastings <larry at hastings.org> added the comment:


New changeset d7b336fe5d54f73c758802df426e06e8a674bd63 by Larry Hastings (Serhiy Storchaka) in branch '3.5':
[3.5] bpo-31026: Fix test_dbm if dbm.ndbm is build with Berkeley DB. (GH-6632)
https://github.com/python/cpython/commit/d7b336fe5d54f73c758802df426e06e8a674bd63


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31026>
_______________________________________

From report at bugs.python.org  Tue Oct 29 04:12:07 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 08:12:07 +0000
Subject: [issue36993] zipfile: tuple IndexError on extract
In-Reply-To: <1558441969.28.0.928640082083.issue36993@roundup.psfhosted.org>
Message-ID: <1572336727.31.0.00754505935638.issue36993@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Thank you for your contribution Daniel.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36993>
_______________________________________

From report at bugs.python.org  Tue Oct 29 04:45:45 2019
From: report at bugs.python.org (Daniel Hillier)
Date: Tue, 29 Oct 2019 08:45:45 +0000
Subject: [issue37523] zipfile: Raise ValueError for i/o operations on closed
 zipfile.ZipExtFile
In-Reply-To: <1562656011.62.0.508019848995.issue37523@roundup.psfhosted.org>
Message-ID: <1572338745.23.0.435465032692.issue37523@roundup.psfhosted.org>


Daniel Hillier <daniel.hillier at gmail.com> added the comment:

Good point. Thanks for the advice. I've updated it to use timeit. Does that give a better indication?

import zipfile

test_zip = "time_test.zip"
test_name = "test_name.txt"

# with zipfile.ZipFile(test_zip, "w") as zf:
#     zf.writestr(test_name, "Hi there! " * 300)

def test():
    with zipfile.ZipFile(test_zip) as zf:
        for i in range(100000):
            zf.read(test_name)


if __name__ == "__main__":
    import timeit
    print(timeit.repeat("test()", setup="from __main__ import test", number=1, repeat=10))


On my machine (running a usual workload) the best of 10 was:

master:
3.812s

check closed:
3.874s

But I think my machine had a quite a bit of variance between runs.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37523>
_______________________________________

From report at bugs.python.org  Tue Oct 29 05:17:23 2019
From: report at bugs.python.org (Ayappan)
Date: Tue, 29 Oct 2019 09:17:23 +0000
Subject: [issue38628] Issue with ctypes in AIX
Message-ID: <1572340643.38.0.935669039099.issue38628@roundup.psfhosted.org>


New submission from Ayappan <ayappanec at gmail.com>:

There seems to be a behavioral issue with ctypes in AIX. 
The specific symptom is that passing structures containing arrays to a C function by value appears to be broken.
Consider the below program.,

#!/usr/bin/env python3

from ctypes import *

libc = CDLL('libc.a(shr_64.o)')


class MemchrArgsHack(Structure):
    _fields_ = [("s", c_char_p), ("c", c_ulong), ("n", c_ulong)]


memchr_args_hack = MemchrArgsHack()
memchr_args_hack.s = b"abcdef"
memchr_args_hack.c = ord('d')
memchr_args_hack.n = 7


class MemchrArgsHack2(Structure):
    _fields_ = [("s", c_char_p), ("c_n", c_ulong * 2)]


memchr_args_hack2 = MemchrArgsHack2()
memchr_args_hack2.s = b"abcdef"
memchr_args_hack2.c_n[0] = ord('d')
memchr_args_hack2.c_n[1] = 7

print(
    CFUNCTYPE(c_char_p, c_char_p, c_uint, c_ulong,
              c_void_p)(('memchr', libc))(b"abcdef", c_uint(ord('d')),
                                          c_ulong(7), None))
print(
    CFUNCTYPE(c_char_p, MemchrArgsHack,
              c_void_p)(('memchr', libc))(memchr_args_hack, None))
print(
    CFUNCTYPE(c_char_p, MemchrArgsHack2,
              c_void_p)(('memchr', libc))(memchr_args_hack2, None))

This one uses memchr from the C library and passing it structures that would map to the registers that correspond to the arguments of memchr. This works for the first structure type in the reproducer; however, using the second structure type (which should be treated the same way) does not work.

In the failing case, the last register that should be used for the structure is not populated from the structure. The reproducer passes an extra argument so that the register is instead populated from that argument for the failing case (instead of working because the register still contains the correct value from a previous call).

The output should be the same for all three calls, but we get:
b'def'
b'def'
None

The last line is None, because memchr got 0 (the None passed on the call) for its length argument.

----------
components: ctypes
messages: 355632
nosy: Ayappan
priority: normal
severity: normal
status: open
title: Issue with ctypes in AIX
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38628>
_______________________________________

From report at bugs.python.org  Tue Oct 29 05:32:51 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 Oct 2019 09:32:51 +0000
Subject: [issue37330] open(): remove 'U' mode, deprecated since Python 3.3
In-Reply-To: <1560872905.7.0.609892598407.issue37330@roundup.psfhosted.org>
Message-ID: <1572341571.94.0.65549203496.issue37330@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 1d2862a323ae1387e306942253b1e487018e2b7f by Victor Stinner in branch '3.8':
bpo-37330: open(): "U" mode is removed in Python 3.9 (GH-16972)
https://github.com/python/cpython/commit/1d2862a323ae1387e306942253b1e487018e2b7f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37330>
_______________________________________

From report at bugs.python.org  Tue Oct 29 05:33:08 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 Oct 2019 09:33:08 +0000
Subject: [issue37330] open(): remove 'U' mode, deprecated since Python 3.3
In-Reply-To: <1560872905.7.0.609892598407.issue37330@roundup.psfhosted.org>
Message-ID: <1572341588.71.0.189232527184.issue37330@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16508
pull_request: https://github.com/python/cpython/pull/16982

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37330>
_______________________________________

From report at bugs.python.org  Tue Oct 29 05:34:31 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 29 Oct 2019 09:34:31 +0000
Subject: [issue14196] Unhandled exceptions in pdb return value display
In-Reply-To: <1330906516.74.0.432612109172.issue14196@psf.upfronthosting.co.za>
Message-ID: <1572341671.18.0.849147725778.issue14196@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

Can't reproducible in py3 (3.8), IMHO can be closed.

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue14196>
_______________________________________

From report at bugs.python.org  Tue Oct 29 05:38:41 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 29 Oct 2019 09:38:41 +0000
Subject: [issue37330] open(): remove 'U' mode, deprecated since Python 3.3
In-Reply-To: <1560872905.7.0.609892598407.issue37330@roundup.psfhosted.org>
Message-ID: <1572341921.33.0.0701475656859.issue37330@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset 4cb08b6c0ae6989d169dd48c2b24087941f6d0b0 by Miss Skeleton (bot) in branch '3.7':
bpo-37330: open(): "U" mode is removed in Python 3.9 (GH-16972)
https://github.com/python/cpython/commit/4cb08b6c0ae6989d169dd48c2b24087941f6d0b0


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37330>
_______________________________________

From report at bugs.python.org  Tue Oct 29 05:40:22 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 Oct 2019 09:40:22 +0000
Subject: [issue37330] open(): remove 'U' mode, deprecated since Python 3.3
In-Reply-To: <1560872905.7.0.609892598407.issue37330@roundup.psfhosted.org>
Message-ID: <1572342022.05.0.671522506694.issue37330@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> should we backport a documentation change for this? (the deprecatedremoved says 4.0 currently)

Done. Thanks for the reminder.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37330>
_______________________________________

From report at bugs.python.org  Tue Oct 29 05:46:15 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 29 Oct 2019 09:46:15 +0000
Subject: [issue19510] lib2to3.fixes.fix_import gets confused if implicit
 relative imports and absolute imports are on the same line
In-Reply-To: <1383697659.1.0.717023788788.issue19510@psf.upfronthosting.co.za>
Message-ID: <1572342375.75.0.482421783209.issue19510@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

> It?s still a bug though :)

It gives a warning about this though
     RefactoringTool: ### In file test/t.py ###
     RefactoringTool: Line 1: absolute and local imports together

If it still counts as a bug, let me know and i'll try to prepare a patch.

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue19510>
_______________________________________

From report at bugs.python.org  Tue Oct 29 05:51:21 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 29 Oct 2019 09:51:21 +0000
Subject: [issue21142] Daily/weekly ABI scan?
In-Reply-To: <1396515016.38.0.140196375249.issue21142@psf.upfronthosting.co.za>
Message-ID: <1572342681.02.0.337232063375.issue21142@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

Tools/c-globals moved under Tools/c-analyzer

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21142>
_______________________________________

From report at bugs.python.org  Tue Oct 29 06:02:07 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 29 Oct 2019 10:02:07 +0000
Subject: [issue38316] docs: Code object's "co_stacksize" field is described
 with mistake
In-Reply-To: <1569789294.48.0.284805020981.issue38316@roundup.psfhosted.org>
Message-ID: <1572343327.7.0.0639667879041.issue38316@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


----------
keywords: +patch
pull_requests: +16509
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16983

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38316>
_______________________________________

From report at bugs.python.org  Tue Oct 29 06:02:36 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Tue, 29 Oct 2019 10:02:36 +0000
Subject: [issue38608] Undocumented behavior that IsolatedAsyncioTestCase would
 enable event loop debug mode
In-Reply-To: <1572227413.17.0.184690601558.issue38608@roundup.psfhosted.org>
Message-ID: <1572343356.14.0.987999474264.issue38608@roundup.psfhosted.org>


Andrew Svetlov <andrew.svetlov at gmail.com> added the comment:

Well, if the reported line is invalid it should be fixed

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38608>
_______________________________________

From report at bugs.python.org  Tue Oct 29 06:02:47 2019
From: report at bugs.python.org (Andrew Svetlov)
Date: Tue, 29 Oct 2019 10:02:47 +0000
Subject: [issue38608] Undocumented behavior that IsolatedAsyncioTestCase would
 enable event loop debug mode
In-Reply-To: <1572227413.17.0.184690601558.issue38608@roundup.psfhosted.org>
Message-ID: <1572343367.39.0.315836063719.issue38608@roundup.psfhosted.org>


Change by Andrew Svetlov <andrew.svetlov at gmail.com>:


----------
components: +asyncio
nosy: +yselivanov

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38608>
_______________________________________

From report at bugs.python.org  Tue Oct 29 06:07:03 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 29 Oct 2019 10:07:03 +0000
Subject: [issue26669] time.localtime(float("NaN")) does not raise a ValueError
 on all platforms
In-Reply-To: <1459322243.53.0.921219428076.issue26669@psf.upfronthosting.co.za>
Message-ID: <1572343623.01.0.447764572557.issue26669@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

Victor's PR 11507 is closed, what actions are going to be taken next? Close the issue as Mariatta said?

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26669>
_______________________________________

From report at bugs.python.org  Tue Oct 29 06:12:32 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 29 Oct 2019 10:12:32 +0000
Subject: [issue32081] ipaddress should support fast IP lookups
In-Reply-To: <1511168238.6.0.213398074469.issue32081@psf.upfronthosting.co.za>
Message-ID: <1572343952.83.0.000343984036962.issue32081@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


----------
nosy: +BTaskaya, pmoody

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32081>
_______________________________________

From report at bugs.python.org  Tue Oct 29 06:14:49 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 29 Oct 2019 10:14:49 +0000
Subject: [issue30533] missing feature in inspect module: getmembers_static
In-Reply-To: <1496271168.24.0.639482608296.issue30533@psf.upfronthosting.co.za>
Message-ID: <1572344089.8.0.582065891946.issue30533@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


----------
nosy: +BTaskaya
versions: +Python 3.9 -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30533>
_______________________________________

From report at bugs.python.org  Tue Oct 29 06:15:51 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 29 Oct 2019 10:15:51 +0000
Subject: [issue36971] Add subsections in C API "Common Object Structures" page
In-Reply-To: <1558365249.02.0.267009483185.issue36971@roundup.psfhosted.org>
Message-ID: <1572344151.0.0.22656886316.issue36971@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

PR 13446 is merged, anything else is needed or can this issue be closed?

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36971>
_______________________________________

From report at bugs.python.org  Tue Oct 29 06:18:17 2019
From: report at bugs.python.org (Ran Benita)
Date: Tue, 29 Oct 2019 10:18:17 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
Message-ID: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>


New submission from Ran Benita <ran at unusedvar.com>:

The numbers.Real ABC requires the __ceil__ and __floor__ methods (https://github.com/python/cpython/blob/v3.8.0/Lib/numbers.py#L178-L186), however, the float type does not have them.

In regular Python, this is not a problem, because math.ceil() and math.floor() special-case float and work on it directly, and numbers.Real is implemented on float by explicitly registering it (so it's not checked that all required methods are implemented).

Where it becomes a (minor) problem is in typeshed, where the type checker *does* check that all abstract methods are implemented. So, because float is missing these two, typeshed cannot have float implement numbers.Real.

Refs: https://github.com/python/typeshed/issues/3195

----------
components: Interpreter Core, Library (Lib)
messages: 355642
nosy: bluetech
priority: normal
severity: normal
status: open
title: float is missing __ceil__() and __floor__(), required by numbers.Real
type: behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Tue Oct 29 06:39:32 2019
From: report at bugs.python.org (Benjamin Edwards)
Date: Tue, 29 Oct 2019 10:39:32 +0000
Subject: [issue37838] typing.get_type_hints not working with
 forward-declaration and decorated functions
In-Reply-To: <1565692979.16.0.678723196671.issue37838@roundup.psfhosted.org>
Message-ID: <1572345572.81.0.820177376617.issue37838@roundup.psfhosted.org>


Benjamin Edwards <benjaminedwards at live.co.uk> added the comment:

Thanks Netzeband,

Will get on this.

Ben

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37838>
_______________________________________

From report at bugs.python.org  Tue Oct 29 07:12:36 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 Oct 2019 11:12:36 +0000
Subject: [issue26669] time.localtime(float("NaN")) does not raise a ValueError
 on all platforms
In-Reply-To: <1459322243.53.0.921219428076.issue26669@psf.upfronthosting.co.za>
Message-ID: <1572347556.41.0.278336468784.issue26669@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

Python 2 users have this bug since 2010, I think that it's fine to not fix it. Python 2 support ends at the end of the year. I close the issue.

The issue has been fixed in Python 3.6 and newer.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue26669>
_______________________________________

From report at bugs.python.org  Tue Oct 29 07:18:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 Oct 2019 11:18:26 +0000
Subject: [issue38630] subprocess.Popen.send_signal() should poll the process
Message-ID: <1572347906.82.0.50492662575.issue38630@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

subprocess.Popen.send_signal() doesn't check if the process exited since the poll() method has been called for the last time. If the process exit just before os.kill() is called, the signal can be sent to the wrong process if the process identified is recycled.

Attached PR simply calls poll() once to reduce the time window when this race condition can occur, but it doesn't fully kill the race condition.

--

See also the new "pidfd" API which only landed very recently in the Linux kernel to prevent this issue:

* https://lwn.net/Articles/773459/
  "Toward race-free process signaling" (this articles describes this issue)
* https://lwn.net/Articles/789023/ 
  "New system calls: pidfd_open() and close_range()"
* https://kernel-recipes.org/en/2019/talks/pidfds-process-file-descriptors-on-linux/
  "pidfds: Process file descriptors on Linux" by Chrisitan Brauner

Illumos, OpenBSD, NetBSD and FreeBSD have similar concepts.

I don't propose to use pidfd here, but it's just to highlight that it's a real issue and that kernels are evolving to provide more reliable solutions against the kill(pid, sig) race condition ;-)

----------
components: Library (Lib)
messages: 355645
nosy: vstinner
priority: normal
severity: normal
status: open
title: subprocess.Popen.send_signal() should poll the process
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38630>
_______________________________________

From report at bugs.python.org  Tue Oct 29 07:18:52 2019
From: report at bugs.python.org (Lewis Gaul)
Date: Tue, 29 Oct 2019 11:18:52 +0000
Subject: [issue23692] Undocumented feature prevents re module from finding
 certain matches
In-Reply-To: <1426618184.57.0.811463464384.issue23692@psf.upfronthosting.co.za>
Message-ID: <1572347932.05.0.988491408876.issue23692@roundup.psfhosted.org>


Lewis Gaul <lewis.gaul at gmail.com> added the comment:

Thanks for the explanation Matthew, I'll take a further look at some point in the coming weeks.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23692>
_______________________________________

From report at bugs.python.org  Tue Oct 29 07:37:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 Oct 2019 11:37:07 +0000
Subject: [issue38630] subprocess.Popen.send_signal() should poll the process
In-Reply-To: <1572347906.82.0.50492662575.issue38630@roundup.psfhosted.org>
Message-ID: <1572349027.15.0.317474893392.issue38630@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16510
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16984

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38630>
_______________________________________

From report at bugs.python.org  Tue Oct 29 07:41:10 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 Oct 2019 11:41:10 +0000
Subject: [issue38630] subprocess.Popen.send_signal() should poll the process
In-Reply-To: <1572347906.82.0.50492662575.issue38630@roundup.psfhosted.org>
Message-ID: <1572349270.21.0.912435474628.issue38630@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

I noticed this issue by reading subprocess code while working on bpo-38207 ("subprocess: Popen.kill() + Popen.communicate() is blocking until all processes using the pipe close the pipe") and bpo-38502 ("regrtest: use process groups").

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38630>
_______________________________________

From report at bugs.python.org  Tue Oct 29 08:29:14 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 29 Oct 2019 12:29:14 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
In-Reply-To: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>
Message-ID: <1572352154.28.0.582376003069.issue38629@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

Ran, do you want to work on this or can i take it?

----------
nosy: +BTaskaya

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Tue Oct 29 08:29:57 2019
From: report at bugs.python.org (Mark Borgerding)
Date: Tue, 29 Oct 2019 12:29:57 +0000
Subject: [issue36666] threading.Thread should have way to catch an exception
 thrown within
In-Reply-To: <1555637775.9.0.13238688405.issue36666@roundup.psfhosted.org>
Message-ID: <1572352197.15.0.811124481934.issue36666@roundup.psfhosted.org>


Mark Borgerding <mborgerd at gmail.com> added the comment:

@pitrou  I don't necessarily agree that "current behavior can't be changed". One major selling point of exceptions is that they cannot be accidentally ignored.  The exception is how the current threading.Thread ignores them.

You are correct that changing Thread.join() so it propagates exceptions by default may break code that relies on the implicit behavior of a thread dying when the target/run method raises.  I'd argue such code deserves to be broken -- "explicit is better than implicit".

I suspect there is more code that will be fixed by such a change than broken.

----------
nosy: +Mark Borgerding

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36666>
_______________________________________

From report at bugs.python.org  Tue Oct 29 08:31:59 2019
From: report at bugs.python.org (Ran Benita)
Date: Tue, 29 Oct 2019 12:31:59 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
In-Reply-To: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>
Message-ID: <1572352318.99.0.862733086038.issue38629@roundup.psfhosted.org>


Ran Benita <ran at unusedvar.com> added the comment:

You can take it - thanks!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Tue Oct 29 08:32:07 2019
From: report at bugs.python.org (pmp-p)
Date: Tue, 29 Oct 2019 12:32:07 +0000
Subject: [issue36666] threading.Thread should have way to catch an exception
 thrown within
In-Reply-To: <1555637775.9.0.13238688405.issue36666@roundup.psfhosted.org>
Message-ID: <1572352327.96.0.680167160011.issue36666@roundup.psfhosted.org>


Change by pmp-p <pmpp.pub at gmail.com>:


----------
nosy: +pmpp

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36666>
_______________________________________

From report at bugs.python.org  Tue Oct 29 08:38:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 Oct 2019 12:38:55 +0000
Subject: [issue38631] Replace Py_FatalError() with regular Python exceptions
Message-ID: <1572352735.51.0.915792481752.issue38631@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

I replaced dozens of Py_FatalError() calls with better error reporting, but there are still many places calling Py_FatalError().

The problem of Py_FatalError() is when Python is embedded into an application: Python must not kill the whole process.

Well, even in the "regular" Python (/usr/bin/python3), Python should not exit immediately on an error.

For example, the readline module calls Py_FatalError() on memory allocation failure, whereas PyErr_NoMemory() could be used: PyErr_NoMemory() should work since it should not allocate memory.

----------
components: Interpreter Core
messages: 355651
nosy: vstinner
priority: normal
severity: normal
status: open
title: Replace Py_FatalError() with regular Python exceptions
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38631>
_______________________________________

From report at bugs.python.org  Tue Oct 29 08:58:55 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 29 Oct 2019 12:58:55 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
In-Reply-To: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>
Message-ID: <1572353935.76.0.858992821004.issue38629@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +mark.dickinson

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Tue Oct 29 09:03:17 2019
From: report at bugs.python.org (Zack Weinberg)
Date: Tue, 29 Oct 2019 13:03:17 +0000
Subject: [issue38632] setup.py sdist should honor SOURCE_DATE_EPOCH
Message-ID: <1572354197.87.0.67466678891.issue38632@roundup.psfhosted.org>


New submission from Zack Weinberg <zackw at panix.com>:

Reproducibility has so far been concerned primarily with binary packages, but it's also desirable for source tarballs to be reproducible starting from a version-control checkout.  This is particularly important for Python, where 'setup.py sdist' can run arbitrary code and generated files (e.g. Cython-generated C) are often included in sdists.

As a small step toward this goal, please add support for the SOURCE_DATE_EPOCH environment variable to distutils.command.sdist.  The most natural way to implement this would be with an additional user option, perhaps called 'timestamp_limit', which takes a date and time argument.  File modification timestamps in the generated tarball or zipfile will be adjusted to be no later than that time.  If 'timestamp_limit' is not set, it defaults to the value of os.environ['SOURCE_DATE_EPOCH'].

The specification for SOURCE_DATE_EPOCH may be found at https://reproducible-builds.org/specs/source-date-epoch/ .

----------
components: Distutils
messages: 355652
nosy: dstufft, eric.araujo, zwol
priority: normal
severity: normal
status: open
title: setup.py sdist should honor SOURCE_DATE_EPOCH

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38632>
_______________________________________

From report at bugs.python.org  Tue Oct 29 09:36:08 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 29 Oct 2019 13:36:08 +0000
Subject: [issue35745] Add import statement in dataclass code snippet
In-Reply-To: <1547566391.87.0.956827047672.issue35745@roundup.psfhosted.org>
Message-ID: <1572356168.73.0.868093372623.issue35745@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Closed in favor of issue 36661 (which I realize was opened later, but has more discussion, so I'm using it going forward).

----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35745>
_______________________________________

From report at bugs.python.org  Tue Oct 29 09:43:32 2019
From: report at bugs.python.org (Fred Drake)
Date: Tue, 29 Oct 2019 13:43:32 +0000
Subject: [issue38621] Bad decoding of encoded-words in unstructured email
 headers
In-Reply-To: <1572281263.86.0.289924184677.issue38621@roundup.psfhosted.org>
Message-ID: <1572356612.57.0.6006630759.issue38621@roundup.psfhosted.org>


Fred Drake <fdrake at gmail.com> added the comment:

This problem does not exist in Python 3.6 or Python 3.8; it appears to only exist in Python 3.7.

----------
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38621>
_______________________________________

From report at bugs.python.org  Tue Oct 29 10:17:13 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 29 Oct 2019 14:17:13 +0000
Subject: [issue38621] Bad decoding of encoded-words in unstructured email
 headers
In-Reply-To: <1572281263.86.0.289924184677.issue38621@roundup.psfhosted.org>
Message-ID: <1572358633.86.0.648603787543.issue38621@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38621>
_______________________________________

From report at bugs.python.org  Tue Oct 29 10:34:38 2019
From: report at bugs.python.org (Peter)
Date: Tue, 29 Oct 2019 14:34:38 +0000
Subject: [issue38633] shutil.copystat fails with PermissionError in WSL
Message-ID: <1572359678.82.0.846153471805.issue38633@roundup.psfhosted.org>


New submission from Peter <peter.schmidb at gmail.com>:

Using shutil.copystat (and therefore also shutil.copytree) in WSL on any directories from a mounted Windows drive (i.e. /mnt/c/...) raises an shutil.Error "[Errno 13] Permission denied". 

It seems to fail when copying the extended filesystem attribute "system.wsl_case_sensitive" using os.setxattr() here: 
https://github.com/python/cpython/blob/da6ce58dd5ac109485af45878fca6bfd265b43e9/Lib/shutil.py#L322

Note that this only happens when both src and dst are on the mounted drive. If only one is on the drive and the other is e.g. in the home directory /home/username/, it will not raise an error. 

Quick way to test: 

cd /mnt/c/ && mkdir test1 && mkdir test2 && python -c "import shutil; shutil.copystat('test1', 'test2')"

----------
components: Library (Lib), Windows
messages: 355655
nosy: paul.moore, pspeter, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: shutil.copystat fails with PermissionError in WSL
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38633>
_______________________________________

From report at bugs.python.org  Tue Oct 29 10:37:08 2019
From: report at bugs.python.org (Batuhan)
Date: Tue, 29 Oct 2019 14:37:08 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
In-Reply-To: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>
Message-ID: <1572359828.27.0.448305866025.issue38629@roundup.psfhosted.org>


Change by Batuhan <batuhanosmantaskaya at gmail.com>:


----------
keywords: +patch
pull_requests: +16511
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16985

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Tue Oct 29 11:17:05 2019
From: report at bugs.python.org (serge-sans-paille)
Date: Tue, 29 Oct 2019 15:17:05 +0000
Subject: [issue38634] Symbol resolution conflict when embeding python in an
 application using libedit
Message-ID: <1572362225.21.0.644355885677.issue38634@roundup.psfhosted.org>


New submission from serge-sans-paille <serge.guelton at telecom-bretagne.eu>:

See https://bugs.llvm.org/show_bug.cgi?id=43830, but basically the follwing code:

```
// a.c
#include <Python.h>

int main() {
  Py_Initialize();
  PyRun_SimpleString("import readline; print(readline.__doc__)");
  return 0;
}
```

compiled like this:

```
% gcc a.c `./install/bin/python3-config --cflags --ldflags --libs` -lpython3.9
```

runs fine:

```
% ./a.out                                          
Importing this module enables command line editing using GNU readline.
```

However the following:

```
% gcc a.c `./install/bin/python3-config --cflags --ldflags --libs` -ledit -lpython3.9
```

compiles but segfaults at runtime.

----------
messages: 355656
nosy: serge-sans-paille
priority: normal
severity: normal
status: open
title: Symbol resolution conflict when embeding python in an application using libedit
type: crash

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38634>
_______________________________________

From report at bugs.python.org  Tue Oct 29 11:17:41 2019
From: report at bugs.python.org (serge-sans-paille)
Date: Tue, 29 Oct 2019 15:17:41 +0000
Subject: [issue38634] Symbol resolution conflict when embeding python in an
 application using libedit
In-Reply-To: <1572362225.21.0.644355885677.issue38634@roundup.psfhosted.org>
Message-ID: <1572362261.16.0.175087474994.issue38634@roundup.psfhosted.org>


Change by serge-sans-paille <serge.guelton at telecom-bretagne.eu>:


----------
keywords: +patch
pull_requests: +16512
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16986

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38634>
_______________________________________

From report at bugs.python.org  Tue Oct 29 11:19:40 2019
From: report at bugs.python.org (Fred Drake)
Date: Tue, 29 Oct 2019 15:19:40 +0000
Subject: [issue38621] Bad decoding of encoded-words in unstructured email
 headers
In-Reply-To: <1572281263.86.0.289924184677.issue38621@roundup.psfhosted.org>
Message-ID: <1572362380.69.0.0948477116924.issue38621@roundup.psfhosted.org>


Fred Drake <fdrake at gmail.com> added the comment:

It turns out this was a problem in 3.7.4; Python 3.7.5 seems to have fixed this.

Sorry for the noise.

Guess it's time to update my application to use 3.7.5!

----------
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38621>
_______________________________________

From report at bugs.python.org  Tue Oct 29 11:28:37 2019
From: report at bugs.python.org (pmp-p)
Date: Tue, 29 Oct 2019 15:28:37 +0000
Subject: [issue38634] Symbol resolution conflict when embeding python in an
 application using libedit
In-Reply-To: <1572362225.21.0.644355885677.issue38634@roundup.psfhosted.org>
Message-ID: <1572362917.94.0.51028597443.issue38634@roundup.psfhosted.org>


Change by pmp-p <pmpp.pub at gmail.com>:


----------
nosy: +pmpp

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38634>
_______________________________________

From report at bugs.python.org  Tue Oct 29 11:45:28 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 29 Oct 2019 15:45:28 +0000
Subject: [issue30548] typo in documentation for create_autospec
In-Reply-To: <1496394381.09.0.91116482689.issue30548@psf.upfronthosting.co.za>
Message-ID: <1572363928.33.0.10646331015.issue30548@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30548>
_______________________________________

From report at bugs.python.org  Tue Oct 29 11:48:29 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Tue, 29 Oct 2019 15:48:29 +0000
Subject: [issue38560] Disallow iterable argument unpacking after a keyword
 argument?
In-Reply-To: <1571790042.34.0.496395652559.issue38560@roundup.psfhosted.org>
Message-ID: <1572364109.35.0.137043160421.issue38560@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

I?ve thought about it and I?m +1 on DeprecationWarning in 3.9 and SyntaxError in 3.10.

Removing any type of legal function call is tricky, but this is such obscure, sneaky syntax that it?s likely an accident/bug if it does pop up (that?s how I discovered it). And every instance can be trivially refactored.

----------
title: Allow iterable argument unpacking after a keyword argument? -> Disallow iterable argument unpacking after a keyword argument?

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38560>
_______________________________________

From report at bugs.python.org  Tue Oct 29 11:58:17 2019
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Tue, 29 Oct 2019 15:58:17 +0000
Subject: [issue38620] Shell python-config --includes returns the same path
 twice
In-Reply-To: <1572279446.17.0.15456686003.issue38620@roundup.psfhosted.org>
Message-ID: <1572364697.63.0.787558620286.issue38620@roundup.psfhosted.org>


Change by Miro Hron?ok <miro at hroncok.cz>:


----------
nosy: +hroncok

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38620>
_______________________________________

From report at bugs.python.org  Tue Oct 29 12:09:10 2019
From: report at bugs.python.org (Matthias Klose)
Date: Tue, 29 Oct 2019 16:09:10 +0000
Subject: [issue38620] Shell python-config --includes returns the same path
 twice
In-Reply-To: <1572279446.17.0.15456686003.issue38620@roundup.psfhosted.org>
Message-ID: <1572365350.73.0.331138765457.issue38620@roundup.psfhosted.org>


Matthias Klose <doko at debian.org> added the comment:

Some distros have two include directories in the path,

 /usr/include
 /usr/include/<multiarch>

The latter for architecture specific files, so on these distributions the python config file is installed there.  Then you'll need to have both include directories.  Unfortunately most third party only expect one, and because the config file is installed in a subdir, then fail to build.

So the solution is to provide a rather arch specific ugly wrapper file to get away with one include directory.

https://salsa.debian.org/cpython-team/python3/blob/master/debian/multiarch.h.in

Also done on other distros like
https://src.fedoraproject.org/rpms/gmp/blob/master/f/gmp.h

I still think the two directories should be emitted, maybe check in the script if they are different.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38620>
_______________________________________

From report at bugs.python.org  Tue Oct 29 12:16:20 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 16:16:20 +0000
Subject: [issue38560] Disallow iterable argument unpacking after a keyword
 argument?
In-Reply-To: <1571790042.34.0.496395652559.issue38560@roundup.psfhosted.org>
Message-ID: <1572365780.33.0.216473540752.issue38560@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Changes to the grammar of the language need to be discussed on python-dev (especially ones that can break existing code and ones that change syntax that has worked for many years).  Arguably, this is something that should just go into a lint tool.

----------
nosy: +gvanrossum, rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38560>
_______________________________________

From report at bugs.python.org  Tue Oct 29 12:28:00 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 16:28:00 +0000
Subject: [issue36666] threading.Thread should have way to catch an exception
 thrown within
In-Reply-To: <1555637775.9.0.13238688405.issue36666@roundup.psfhosted.org>
Message-ID: <1572366480.37.0.141245320131.issue36666@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

> I'd argue such code deserves to be broken

That argument falls flat with me and it doesn't show respect for our users.  The proposal would be a major change to the "rules of the game" and would likely require discussion and buy-in on python-dev and perhaps a PEP.

Please heed Antoine's advice.  This is his area of expertise, and he has suggested a plausible way to go forward.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36666>
_______________________________________

From report at bugs.python.org  Tue Oct 29 12:29:45 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 16:29:45 +0000
Subject: [issue38613] Optimize some set operations in dictkeys object
In-Reply-To: <1572263745.15.0.0692968844895.issue38613@roundup.psfhosted.org>
Message-ID: <1572366585.88.0.456633169717.issue38613@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Consider testing PyDict_CheckExact.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38613>
_______________________________________

From report at bugs.python.org  Tue Oct 29 13:28:43 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 29 Oct 2019 17:28:43 +0000
Subject: [issue38560] Disallow iterable argument unpacking after a keyword
 argument?
In-Reply-To: <1571790042.34.0.496395652559.issue38560@roundup.psfhosted.org>
Message-ID: <1572370123.43.0.575679890212.issue38560@roundup.psfhosted.org>


Guido van Rossum <guido at python.org> added the comment:

Well, as you point out, f(z=0, *(1, 2)) is legal, and the parser doesn't know what the names of the keyword arguments are. SO this cannot be changed.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38560>
_______________________________________

From report at bugs.python.org  Tue Oct 29 13:56:00 2019
From: report at bugs.python.org (Mark Borgerding)
Date: Tue, 29 Oct 2019 17:56:00 +0000
Subject: [issue36666] threading.Thread should have way to catch an exception
 thrown within
In-Reply-To: <1555637775.9.0.13238688405.issue36666@roundup.psfhosted.org>
Message-ID: <1572371760.91.0.822704066847.issue36666@roundup.psfhosted.org>


Mark Borgerding <mborgerd at gmail.com> added the comment:

I'm not trying to disrespect anyone: not users nor certainly Python developers.  I have loved Python since I learned it in 2001.  I was merely trying to respond to what seemed like an automatic rejection of changing legacy behavior.  I certainly agree changes to default behavior should not be made lightly, but sometimes they *should* be made.

This may be such a case:
a) A user writing a thread function either consciously thinks about exceptions while they write function or they do not.  Sure, we should always do the former; just like we should always eat our veggies and get lots of exercise, but ....
b) If they *do* think about exceptions, they will either
b.1) write exception handlers within that function, or
b.2) rely on default behavior that simply prints out the exception string to stderr and lets the thread quietly die.
c) If they did not explicitly think about exceptions while they wrote the function, they may have in the back of their mind the reasonable expectation that an exception will not be ignored.

Changing `join()` to propagate unhandled exceptions would admittedly break b.2 code, but provides absolution for all sinners who have written case c.

This is what I meant by, "I suspect there is more code that will be fixed by such a change than broken."

I'll confess I only just now became aware of `threading.excepthook` added in python 3.8.  Does it change this problem?

----------
Added file: https://bugs.python.org/file48686/ignored_thread_exc.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36666>
_______________________________________

From report at bugs.python.org  Tue Oct 29 14:12:48 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 29 Oct 2019 18:12:48 +0000
Subject: [issue14196] Unhandled exceptions in pdb return value display
In-Reply-To: <1330906516.74.0.432612109172.issue14196@psf.upfronthosting.co.za>
Message-ID: <1572372768.41.0.308607852532.issue14196@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Batuhan, thanks for the nudge.  For the record ...

If __new__ were a normal instance method, then 'some_class.__new__()' would be a correct call, as 'some_class' would be passed to '__new__' as its first and perhaps only argument.  But " __new__() is a static method (special-cased so you need not declare it as such)".
https://docs.python.org/3/reference/datamodel.html#object.__new__
Its special-casing makes it easy to forget that its first argument, a class, must be passed explicitly.  Hence Xavier's comment.

In current 2.7.17 and 3.8 (for instance), with pdb left out of the picture, the missing cls argument results in
  TypeError: object.__new__(): not enough arguments

When I pdb.run('A()') new and step, it catches the error and refuses to advance.

> <pyshell#10>(3)__new__()
(Pdb) s
TypeError: object.__new__(): not enough arguments
> <pyshell#10>(3)__new__()

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue14196>
_______________________________________

From report at bugs.python.org  Tue Oct 29 14:21:51 2019
From: report at bugs.python.org (Joel Croteau)
Date: Tue, 29 Oct 2019 18:21:51 +0000
Subject: [issue36666] threading.Thread should have way to catch an exception
 thrown within
In-Reply-To: <1555637775.9.0.13238688405.issue36666@roundup.psfhosted.org>
Message-ID: <1572373311.75.0.200258436688.issue36666@roundup.psfhosted.org>


Joel Croteau <jcroteau at liveramp.com> added the comment:

I'm kind of in agreement with Mark on this, actually. I came across this problem when examining some threaded code that was clearly not working as intended, but was reporting success. Figuring out why that was was not easy. The code had been hastily ported to a multi-threaded version from an iterative version by my predecessor, and neither of us had enough familiarity with Python threads to realize what the problem was. The whole point of having exceptions is that it gives you a way of knowing when errors happen without having to add a bunch of extra error checking to your own code. It rather defeats the purpose if code can silently fail while still throwing exceptions, and we have to add extra code to handle special cases like this where they are ignored.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36666>
_______________________________________

From report at bugs.python.org  Tue Oct 29 14:39:15 2019
From: report at bugs.python.org (=?utf-8?q?Rapha=C3=ABl_M?=)
Date: Tue, 29 Oct 2019 18:39:15 +0000
Subject: [issue35459] Use PyDict_GetItemWithError() instead of PyDict_GetItem()
In-Reply-To: <1544525657.6.0.788709270274.issue35459@psf.upfronthosting.co.za>
Message-ID: <1572374355.12.0.839842234444.issue35459@roundup.psfhosted.org>


Rapha?l M <raphael.monat at lip6.fr> added the comment:

I stumbled upon this issue while reading Python 3.8 and this made me curious.

I've tried writing some Python code to reproduce this bug, but I'm unable to -- I should be missing something. Is there a simple snippet showing the issue? 


Also, the changelog states that "The CPython interpreter can swallow exceptions in some circumstances". Are there other documented cases of those circumstances?

----------
nosy: +raphaelm

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35459>
_______________________________________

From report at bugs.python.org  Tue Oct 29 14:48:02 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 18:48:02 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
In-Reply-To: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>
Message-ID: <1572374882.4.0.622343490316.issue38629@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

If float.__ceil__ is only needed for typeshed, maybe add a special case for typeshed?

I have doubts about adding a C code which is never even executed.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Tue Oct 29 14:59:18 2019
From: report at bugs.python.org (Tal Einat)
Date: Tue, 29 Oct 2019 18:59:18 +0000
Subject: [issue38598] IDLE: Disable F5, etc, in Shell and Output windows.
In-Reply-To: <1572123836.51.0.5425055858.issue38598@roundup.psfhosted.org>
Message-ID: <1572375558.44.0.418291049957.issue38598@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

As a better design for a long-term fix, I suggest:

* Avoiding isinstance() checks by instead using a dedicated class attribute and checking that. (I've recently used this pattern for line numbers.)
* Instead of baling out inside the "check module" and "run" handlers, don't include the related items in the menus in the first place. (Make them conditional on the above-mentioned class attribute's value.)

----------
nosy: +taleinat

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38598>
_______________________________________

From report at bugs.python.org  Tue Oct 29 15:01:24 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Tue, 29 Oct 2019 19:01:24 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
In-Reply-To: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>
Message-ID: <1572375684.43.0.474502374543.issue38629@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

> I have doubts about adding a C code which is never even executed.

My reading of the PR is that it *would* be executed: the math module first looks for the __floor__ special method, then falls back to using the libm floor if that doesn't exist. Am I missing something?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Tue Oct 29 15:07:13 2019
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 29 Oct 2019 19:07:13 +0000
Subject: [issue38627] Add copy() method to pathlib
In-Reply-To: <1572328517.33.0.0527318368455.issue38627@roundup.psfhosted.org>
Message-ID: <1572376033.67.0.95580293587.issue38627@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

And just to add Serhiy's logic, think of pathlib more as an equivalent to os.path than a be-all solution to anything path-related.

----------
nosy: +brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38627>
_______________________________________

From report at bugs.python.org  Tue Oct 29 15:40:16 2019
From: report at bugs.python.org (serge-sans-paille)
Date: Tue, 29 Oct 2019 19:40:16 +0000
Subject: [issue13501] Make libedit support more generic;
 port readline / libedit to FreeBSD
In-Reply-To: <1322579942.3.0.601983912656.issue13501@psf.upfronthosting.co.za>
Message-ID: <1572378016.1.0.14828219558.issue13501@roundup.psfhosted.org>


Change by serge-sans-paille <serge.guelton at telecom-bretagne.eu>:


----------
pull_requests: +16513
pull_request: https://github.com/python/cpython/pull/16986

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue13501>
_______________________________________

From report at bugs.python.org  Tue Oct 29 15:42:04 2019
From: report at bugs.python.org (Ned Deily)
Date: Tue, 29 Oct 2019 19:42:04 +0000
Subject: [issue38634] Symbol resolution conflict when embeding python in an
 application using libedit
In-Reply-To: <1572362225.21.0.644355885677.issue38634@roundup.psfhosted.org>
Message-ID: <1572378124.33.0.163799254536.issue38634@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:

This appears to be essentially a duplicate of Issue13631 which has long proposed full support of libedit.

----------
assignee:  -> gregory.p.smith
nosy: +gregory.p.smith, ned.deily

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38634>
_______________________________________

From report at bugs.python.org  Tue Oct 29 15:42:34 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 19:42:34 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
In-Reply-To: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>
Message-ID: <1572378154.38.0.427955887222.issue38629@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Oh, you are right. I misunderstood the original issue and thought that the code first checks PyFloat_Check() or PyFloat_CheckExact().

If float.__ceil__ will be executed it will add significant overhead for creating and executing the method object.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Tue Oct 29 16:16:13 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 20:16:13 +0000
Subject: [issue24686] zipfile is intolerant of extra bytes
In-Reply-To: <1437585382.21.0.339790988945.issue24686@psf.upfronthosting.co.za>
Message-ID: <1572380173.86.0.818171028277.issue24686@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Interesting, but all extra after the Extended Timestamp field is a UTF-8 encoded text:

b"\n\x00 \x00\x00\x00\x00\x00\x01\x00\x18\x00\x00\xeb\x93\x91'\xef\xbf\xbd\xef\xbf\xbd\x01\x00\xde\xa8\xef\xbf\xbd\xef\xbf\xbd\xef\xbf\xbd\x01\x00\xde\xa8\xef\xbf\xbd\xef\xbf\xbd\xef\xbf\xbd\x01" == "\n\x00 \x00\x00\x00\x00\x00\x01\x00\x18\x00\x00\ub4d1'\ufffd\ufffd\x01\x00\u07a8\ufffd\ufffd\ufffd\x01\x00\u07a8\ufffd\ufffd\ufffd\x01".encode()

The chance that random binary data is a UTF-8 encoded text is small, so it looks like garbage text encoded with UTF-8 was appended to the extra.

It is definitely not Python issue.

----------
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24686>
_______________________________________

From report at bugs.python.org  Tue Oct 29 16:24:55 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Tue, 29 Oct 2019 20:24:55 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
In-Reply-To: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>
Message-ID: <1572380695.93.0.069482948598.issue38629@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

> If float.__ceil__ will be executed it will add significant overhead for creating and executing the method object.

Yes, I'd definitely like to see timings; I think Victor already asked for those on the PR.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Tue Oct 29 16:35:00 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 20:35:00 +0000
Subject: [issue38635] Simplify decoding the ZIP64 extra field and make it
 tolerant to extra data
Message-ID: <1572381300.43.0.604148893279.issue38635@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

The decoding code can be much shorter and efficient.

Also, the Info-ZIP unzip utility is tolerant to extra bytes. We can be too.

----------
components: Library (Lib)
messages: 355676
nosy: serhiy.storchaka
priority: normal
severity: normal
status: open
title: Simplify decoding the ZIP64 extra field and make it tolerant to extra data
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38635>
_______________________________________

From report at bugs.python.org  Tue Oct 29 16:36:29 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 20:36:29 +0000
Subject: [issue38635] Simplify decoding the ZIP64 extra field and make it
 tolerant to extra data
In-Reply-To: <1572381300.43.0.604148893279.issue38635@roundup.psfhosted.org>
Message-ID: <1572381389.9.0.826842535732.issue38635@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16514
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16988

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38635>
_______________________________________

From report at bugs.python.org  Tue Oct 29 16:46:45 2019
From: report at bugs.python.org (will rogers)
Date: Tue, 29 Oct 2019 20:46:45 +0000
Subject: [issue36702] test_dtrace failed
In-Reply-To: <1556002133.06.0.696794109378.issue36702@roundup.psfhosted.org>
Message-ID: <1572382005.93.0.1675545516.issue36702@roundup.psfhosted.org>


will rogers <willrogers3 at gmail.com> added the comment:

I also encountered this on Scientific Linux 7.4 (Linux 3.10.0-693.11.6.el7.x86_64) while trying to build Python 3.8.0.

I think it is due to differences in versions of 'dtrace' on different platforms.
On my MacOS-X v10.14.6 (Mojave) system, the 'dtrace' command has a  -q (quiet the output) option.
On SL 7.4, it does not. The options are quite different.


This is output and versions from my test run:

    ./python  ./Tools/scripts/run_tests.py 
    == CPython 3.8.0 (default, Oct 29 2019, 14:37:09) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)]
    == Linux-3.10.0-693.11.6.el7.x86_64-x86_64-with-glibc2.17 little-endian
    == cwd: /opt/Python-3.8.0/build/test_python_30482
    == CPU count: 2
    == encodings: locale=UTF-8, FS=utf-8

Below is an error from the test log that shows the 'q' option being rejected from 'dtrace' (linux'):

    0:10:16 load avg: 1.79 Re-running test_dtrace in verbose mode
    skipped "dtrace(1) failed: ('/usr/bin/dtrace', 'invalid option', '-q')\nUsage /usr/bin/dtrace [--help] [-h | -G] [-C [-I<Path>]] -s File.d [-o <File>]"

Assuming 'dtrace' is run as a sub-process, the different versions could be producing very different results.

I attached a (clipped) version of my 'make test' output, it is essentially the same as sayno996's results.
There are also some error from 'test_nis" which can be ignoed for this issue.

I hope this helps.

----------
nosy: +willrogers3
versions: +Python 3.8
Added file: https://bugs.python.org/file48687/make_test-clipped.txt

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36702>
_______________________________________

From report at bugs.python.org  Tue Oct 29 17:14:08 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Tue, 29 Oct 2019 21:14:08 +0000
Subject: [issue38636] "Alt + T" and "Alt + U" Broken in IDLE on Windows
Message-ID: <1572383648.52.0.228001978432.issue38636@roundup.psfhosted.org>


New submission from Stephen Paul Chappell <Noctis.Skytower at gmail.com>:

In the latest Python 3.8.0 installation when running IDLE on Windows, pressing "Alt + T" generates the following error:

    Exception in Tkinter callback
    Traceback (most recent call last):
      File "C:\Program Files\Python38\Lib\tkinter\__init__.py", line 1883, in __call__
        return self.func(*args)
      File "C:\Program Files\Python38\Lib\idlelib\multicall.py", line 176, in handler
        r = l[i](event)
    TypeError: toggle_tabs_event() missing 1 required positional argument: 'event'

Similarly, pressing "Alt + U" will generate a very similar error:

    Exception in Tkinter callback
    Traceback (most recent call last):
      File "C:\Program Files\Python38\Lib\tkinter\__init__.py", line 1883, in __call__
        return self.func(*args)
      File "C:\Program Files\Python38\Lib\idlelib\multicall.py", line 176, in handler
        r = l[i](event)
    TypeError: change_indentwidth_event() missing 1 required positional argument: 'event'

----------
assignee: terry.reedy
components: IDLE, Windows
messages: 355678
nosy: Zero, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: "Alt + T" and "Alt + U" Broken in IDLE on Windows
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38636>
_______________________________________

From report at bugs.python.org  Tue Oct 29 17:31:18 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 21:31:18 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572384678.86.0.795613160841.issue28029@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

The current docs could certainly use clarification.

FWIW, here is a link to my explanation for the existing logic in str.replace():  https://stackoverflow.com/questions/16645083 
Perhaps some of that wording may be helpful.

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Tue Oct 29 17:33:26 2019
From: report at bugs.python.org (Steve Dower)
Date: Tue, 29 Oct 2019 21:33:26 +0000
Subject: [issue38453] ntpath.realpath() does not fully resolve relative paths
In-Reply-To: <1570832840.2.0.910161330311.issue38453@roundup.psfhosted.org>
Message-ID: <1572384806.58.0.764210223804.issue38453@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

The discussion on the PR has raised one scenario where our algorithm conflicts with what we can reasonably emulate from the IO manager (which is itself not entirely self-consistent):

If you call ntpath.realpath(r"C:\spam\eggs") where "spam" is a symlink/junction to "D:\foo\baz" and "D:\foo\baz\eggs" is a relative symlink to "..\bar" and "D:\foo\bar" does not exist, we will incorrectly return "C:\bar".

Note that if "D:\foo\bar" *does* exist, we will return the correct result. And if "C:\spam" is *not* a symlink/junction, we will return the correct result.

Essentially, we fail in the case where ntpath.exists(X) fails and realpath(dirname(X)) != dirname(X) and readlink(X).startswith("..\\") is True.

Considering it's taken months of patient explanation from Eryk Sun for me to understand this, and nobody has ever complained about it, I'm prepared to call it a known limitation.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38453>
_______________________________________

From report at bugs.python.org  Tue Oct 29 17:34:36 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 21:34:36 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572384876.46.0.965565007609.issue28029@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Raymond, the link is about str.split(), not str.replace().

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Tue Oct 29 17:40:45 2019
From: report at bugs.python.org (Jamie Bliss)
Date: Tue, 29 Oct 2019 21:40:45 +0000
Subject: [issue37839] makesetup Doesn't Handle Defines with Equal Sign
In-Reply-To: <1565694009.91.0.692452487744.issue37839@roundup.psfhosted.org>
Message-ID: <1572385245.58.0.692775302288.issue37839@roundup.psfhosted.org>


Jamie Bliss <astronouth7303 at gmail.com> added the comment:

Similarly, stumbled across this working on https://github.com/pyz-dispenser/cpython-static

This is particularly problematic because of the SQLite module's MODULE_NAME macro.

----------
nosy: +astronouth7303

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37839>
_______________________________________

From report at bugs.python.org  Tue Oct 29 18:00:41 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 29 Oct 2019 22:00:41 +0000
Subject: [issue38312] curses: add `set_tabsize` and `set_escdelay`
In-Reply-To: <1569721208.44.0.258918770799.issue38312@roundup.psfhosted.org>
Message-ID: <1572386441.04.0.898624952233.issue38312@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

There are also ncurses functions get_tabsize() and get_escdelay(). In other implementations they can be modeled by returning the TABSIZE and ESCDELAY global variables.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38312>
_______________________________________

From report at bugs.python.org  Tue Oct 29 18:03:15 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 29 Oct 2019 22:03:15 +0000
Subject: [issue38568] [3.7.5 x86_64 Linux] f-string parsing results in EOL
In-Reply-To: <1571857754.85.0.698050163763.issue38568@roundup.psfhosted.org>
Message-ID: <1572386595.82.0.688661449255.issue38568@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

> It is a limitation of f-strings, though. We're not allowed to use
> backslashes within the f-string expression in curly braces.

I've considered relaxing these restrictions, although it's very complicated. The parser would need to become aware of what's inside an f-string (the braces, the expressions, the optional format spec, the doubled braces, escaped characters, etc.). See PEP 536 for a rough outline. The = format for "debugging" with f-strings (see issue 36817) also makes this more complicated.

----------
nosy: +eric.smith

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38568>
_______________________________________

From report at bugs.python.org  Tue Oct 29 18:09:41 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Tue, 29 Oct 2019 22:09:41 +0000
Subject: [issue38312] curses: add `set_tabsize` and `set_escdelay`
In-Reply-To: <1569721208.44.0.258918770799.issue38312@roundup.psfhosted.org>
Message-ID: <1572386981.54.0.465290048905.issue38312@roundup.psfhosted.org>


Anthony Sottile <asottile at umich.edu> added the comment:

ah, I'll add those too -- I can do that in the current PR

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38312>
_______________________________________

From report at bugs.python.org  Tue Oct 29 18:13:50 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 22:13:50 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572387230.11.0.298141449097.issue28029@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
Removed message: https://bugs.python.org/msg355679

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Tue Oct 29 18:14:00 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 29 Oct 2019 22:14:00 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572387240.75.0.958040938109.issue28029@roundup.psfhosted.org>


Change by Raymond Hettinger <raymond.hettinger at gmail.com>:


----------
Removed message: https://bugs.python.org/msg355681

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Tue Oct 29 18:46:43 2019
From: report at bugs.python.org (Jim Carroll)
Date: Tue, 29 Oct 2019 22:46:43 +0000
Subject: [issue38611] ElementTree.ParseError does not implement SyntaxError
 interface as expected
In-Reply-To: <1572253875.02.0.816082787085.issue38611@roundup.psfhosted.org>
Message-ID: <1572389203.57.0.35979259068.issue38611@roundup.psfhosted.org>


Jim Carroll <jim at carroll.com> added the comment:

This patch solves the issue

diff --git a/Modules/_elementtree.c b/Modules/_elementtree.c
index c3f30c9339..d265021f75 100644
--- a/Modules/_elementtree.c
+++ b/Modules/_elementtree.c
@@ -2782,6 +2782,7 @@ treebuilder_handle_start(TreeBuilderObject* self, PyObject* tag,
                 st->parseerror_obj,
                 "multiple elements on top level"
                 );
+                       PyErr_SyntaxLocationEx("xml.etree.ElementTree", 0, 0);
             goto error;
         }
         Py_INCREF(node);
@@ -3267,6 +3268,7 @@ expat_set_error(enum XML_Error error_code, Py_ssize_t line, Py_ssize_t column,
     Py_DECREF(position);

     PyErr_SetObject(st->parseerror_obj, error);
+       PyErr_SyntaxLocationEx("xml.etree.ElementTree", (int)line, (int)column);
     Py_DECREF(error);
 }

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38611>
_______________________________________

From report at bugs.python.org  Tue Oct 29 20:02:34 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Wed, 30 Oct 2019 00:02:34 +0000
Subject: [issue37957] Allow regrtest to receive a file with test (and
 subtests) to ignore
In-Reply-To: <1566864234.54.0.166621143796.issue37957@roundup.psfhosted.org>
Message-ID: <1572393754.81.0.802059972512.issue37957@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +patch
pull_requests: +16515
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16989

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37957>
_______________________________________

From report at bugs.python.org  Tue Oct 29 20:42:20 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 30 Oct 2019 00:42:20 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1572396140.59.0.565683325533.issue38382@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Maybe we should hold-off on adding negative number support unless a compelling use case arises.  It is telling that scipy.stats.hmean() and that MS Excel's harmean() haven't found justification to add negative number support.

In all likelihood, a negative input is an error in the input and users would be better-off seeing an exception raised.  In a number of contexts, the negative input wouldn't make sense all:

* a 10 ohm resistor wired in parallel with a negative 5 ohm resistor
* travel 1 km at 5 kph then another 1 km at -10 kph

We really don't have to go down this route just because we can.  The usual rule is to keep the API minimal unless real use cases arise to inform the design.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Tue Oct 29 22:05:46 2019
From: report at bugs.python.org (toywei)
Date: Wed, 30 Oct 2019 02:05:46 +0000
Subject: [issue38637] fix GROWTH_RATE comments bug
Message-ID: <1572401146.1.0.358314054297.issue38637@roundup.psfhosted.org>


New submission from toywei <g1e2t3 at foxmail.com>:

It also exists in 3.7/3.6/3.3.

----------
assignee: docs at python
components: Documentation
messages: 355688
nosy: docs at python, toywei
priority: normal
pull_requests: 16516
severity: normal
status: open
title: fix GROWTH_RATE comments bug
type: resource usage
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38637>
_______________________________________

From report at bugs.python.org  Tue Oct 29 22:12:26 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 30 Oct 2019 02:12:26 +0000
Subject: [issue38611] ElementTree.ParseError does not implement SyntaxError
 interface as expected
In-Reply-To: <1572253875.02.0.816082787085.issue38611@roundup.psfhosted.org>
Message-ID: <1572401546.5.0.575629305546.issue38611@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +scoder

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38611>
_______________________________________

From report at bugs.python.org  Tue Oct 29 22:22:50 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Wed, 30 Oct 2019 02:22:50 +0000
Subject: [issue38637] fix GROWTH_RATE comments bug
In-Reply-To: <1572401146.1.0.358314054297.issue38637@roundup.psfhosted.org>
Message-ID: <1572402170.93.0.8199614117.issue38637@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Please explain the bug here on the bug tracker, people shouldn't have to drill down into the PR to find out what it means.

Before fixing the bug, you should find out whether or not it actually is a bug. In my testing, the comment is approximately correct:

    py> from random import random
    py> d = dict((random(), None) for i in range(20))
    py> sys.getsizeof(d)
    432
    py> while sys.getsizeof(d) == 432:
    ...     d[random()] = None
    ...
    py> sys.getsizeof(d)
    816


That looks closer to double than triple to me. Try a larger dict:

    py> for i in range(10000):
    ...     d[random()] = None
    ...
    py> sys.getsizeof(d)
    196656
    py> while sys.getsizeof(d) == 196656:
    ...     d[random()] = None
    ...
    py> sys.getsizeof(d)
    393264

Still looks like double to me.

Unless an expert on the dict internals agrees with you, the comment is correct, it is not a bug, and this issue should be closed.

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38637>
_______________________________________

From report at bugs.python.org  Tue Oct 29 23:06:29 2019
From: report at bugs.python.org (gaoxinge)
Date: Wed, 30 Oct 2019 03:06:29 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1572404789.15.0.0456001767678.issue38382@roundup.psfhosted.org>


gaoxinge <gaoxx5 at gmail.com> added the comment:

I think that three kinds of mean should behave like:

- `geometric mean`: input should be float, finite and positive
- `harmonic mean`: input should be float, finite and nonzero
- `mean` or `fmean`: input should be float, finite

Otherwise these mean functions should raise a `StatisticsError`. 

Two points that we should pay attention to:

- Why every input should be float? Because it is a statstics library, we should focus on the float instead of complex number or string or `math.nan`.

- Why every input shoud be finite? Becuse we should get rid of `math.inf`.

----------
nosy: +gaoxinge

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Tue Oct 29 23:10:26 2019
From: report at bugs.python.org (gaoxinge)
Date: Wed, 30 Oct 2019 03:10:26 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1572405026.43.0.699499740487.issue38382@roundup.psfhosted.org>


gaoxinge <gaoxx5 at gmail.com> added the comment:

The document https://github.com/WarrenWeckesser/cpython/blob/master/Lib/statistics.py#L389 in `harmonic_mean` is out-dated. I think we can simply follow the wiki:

- [arithemic mean](https://en.wikipedia.org/wiki/Arithmetic_mean)
- [geometric mean](https://en.wikipedia.org/wiki/Geometric_mean)
- [harmonic mean](https://en.wikipedia.org/wiki/Harmonic_mean)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Wed Oct 30 01:21:25 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Wed, 30 Oct 2019 05:21:25 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1572404789.15.0.0456001767678.issue38382@roundup.psfhosted.org>
Message-ID: <20191030052117.GM3574@ando.pearwood.info>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Thank you for your comments, but accepting non-floats like Decimal and 
Fraction (and int, of course!) is a hard requirement for the statistics 
module. fmean will naturally convert any data to float for speed, but 
the other means will attempt to keep the original data type if possible, 
so that the mean() of Decimals will be a Decimal, the mean of Fractions 
will be a Fraction, etc.

The median_low and median_high functions don't require numbers at all, 
the data points just need to be ordinal data and support sorting. The 
mode function doesn't even require ordinal data, it can work with 
nominal data. That is part of the definition of median and mode, and 
will not change.

http://intellspot.com/nominal-vs-ordinal-data/

So long as Python support IEEE-754 floating point arithmetic, which is 
the most common standard for floating point, there will be NANs and 
INFs. We should not reject them unnecessarily. You can always pre-filter 
your data before passing it the statistics module.

Why do you object to float INF?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Wed Oct 30 01:50:10 2019
From: report at bugs.python.org (Dino Viehland)
Date: Wed, 30 Oct 2019 05:50:10 +0000
Subject: [issue36971] Add subsections in C API "Common Object Structures" page
In-Reply-To: <1558365249.02.0.267009483185.issue36971@roundup.psfhosted.org>
Message-ID: <1572414610.89.0.420277765269.issue36971@roundup.psfhosted.org>


Dino Viehland <dinoviehland at gmail.com> added the comment:

@BTaskaya Seems done, I'll go ahead and close it

----------
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36971>
_______________________________________

From report at bugs.python.org  Wed Oct 30 02:06:20 2019
From: report at bugs.python.org (gaoxinge)
Date: Wed, 30 Oct 2019 06:06:20 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1572415580.11.0.561866986665.issue38382@roundup.psfhosted.org>


gaoxinge <gaoxx5 at gmail.com> added the comment:

Your point makes sense. We should still also consider the `int`, `Decimal`, `Fraction`, `math.nan`, `math.inf`, `np.int` and so on. So

- `geometric mean`: input should be positive (>= 0)
- `harmonic mean`: input should be nonzero (!= 0)
- `mean` or `fmean`: no input restriction

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Wed Oct 30 03:39:49 2019
From: report at bugs.python.org (Inada Naoki)
Date: Wed, 30 Oct 2019 07:39:49 +0000
Subject: [issue38613] Optimize some set operations in dictkeys object
In-Reply-To: <1572263745.15.0.0692968844895.issue38613@roundup.psfhosted.org>
Message-ID: <1572421189.21.0.584722518422.issue38613@roundup.psfhosted.org>


Inada Naoki <songofacandy at gmail.com> added the comment:

done.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38613>
_______________________________________

From report at bugs.python.org  Wed Oct 30 04:09:46 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Wed, 30 Oct 2019 08:09:46 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1572415580.11.0.561866986665.issue38382@roundup.psfhosted.org>
Message-ID: <20191030080939.GN3574@ando.pearwood.info>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

Have you read the rest of the thread? There is a compelling reason to 
support harmonic mean including zero (resistors in parallel) but not yet 
any compelling reason to support negative values.

If you have a good use-case for harmonic mean of negative values, please 
tell us. Until then, I agree with Raymond: negative values should be 
treated as an error, as documented.

Can we go back to the original issue? Should we just document the 
"early out" behaviour on hitting zero, or should we follow the 
suggestion to check for bad data and raise?

I'm currently undecided which I would prefer.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Wed Oct 30 04:35:30 2019
From: report at bugs.python.org (=?utf-8?q?Erik_Bystr=C3=B6m?=)
Date: Wed, 30 Oct 2019 08:35:30 +0000
Subject: [issue30548] typo in documentation for create_autospec
In-Reply-To: <1496394381.09.0.91116482689.issue30548@psf.upfronthosting.co.za>
Message-ID: <1572424530.47.0.461248894344.issue30548@roundup.psfhosted.org>


Erik Bystr?m <erik.bystrom at gmail.com> added the comment:

Yes, you're right. I do think the docs are a bit misleading.

Maybe something like this would make it more clear?

"If a class is used as a spec then the returned object will be a mock of that class. When the constructor of the returned mock class is invoked an instance object is returned that has the same spec as a normal instance object would have. By passing instance=True you can directly create a mock instance of the class."

If not, feel free to close this issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue30548>
_______________________________________

From report at bugs.python.org  Wed Oct 30 05:21:06 2019
From: report at bugs.python.org (Alexander Kurakin)
Date: Wed, 30 Oct 2019 09:21:06 +0000
Subject: [issue38638] Backtrace of exit phase of context managers
Message-ID: <1572427266.54.0.98752253476.issue38638@roundup.psfhosted.org>


New submission from Alexander Kurakin <kuraga333 at mail.ru>:

class CM:

    def __init__(self):
        pass

    def __enter__(self):
        return self

    def __exit__(self, exc_type, exc_val, exc_tb):
        raise RuntimeError()

if __name__ == '__main__':
    with CM() as cm:
        print('Hello')


$ python3 cm.py 
Hello
Traceback (most recent call last):
  File "cm.py", line 14, in <module>
    print('Hello')  # <--
  File "cm.py", line 10, in __exit__
    raise RuntimeError()
RuntimeError


Is it correct that print presents in backtrace? Well it's the last line but...

Thanks.

----------
components: Interpreter Core
messages: 355698
nosy: kuraga
priority: normal
severity: normal
status: open
title: Backtrace of exit phase of context managers
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38638>
_______________________________________

From report at bugs.python.org  Wed Oct 30 05:29:36 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 09:29:36 +0000
Subject: [issue38639] Optimize floor() and ceil() for floats
Message-ID: <1572427776.81.0.21510885347.issue38639@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

Currently math.floor(), math.ceil() and math.trunc() look up special methods __floor__, __ceil__ and __trunc__ correspondingly and execute them if found. Otherwise they execute common code for floats. There are no special slots for these methods, so looking up these names in type dicts takes some time. It is a waste of time for most common case -- float objects.

The proposed PR adds checks PyFloat_CheckExact() before looking up the special method. Some microbenchmarks:

$ ./python -m pyperf timeit -s "from math import floor" --duplicate 100 "floor(12345.6)"
Before:  Mean +- std dev: 63.2 ns +- 1.7 ns
After:   Mean +- std dev: 51.8 ns +- 1.3 ns

$ ./python -m pyperf timeit -s "from math import ceil" --duplicate 100 "ceil(12345.6)"
Before:  Mean +- std dev: 61.1 ns +- 1.5 ns
After:   Mean +- std dev: 51.9 ns +- 1.1 ns

$ ./python -m pyperf timeit -s "from math import trunc" --duplicate 100 "trunc(12345.6)"
Before:  Mean +- std dev: 72.0 ns +- 1.5 ns
After:   Mean +- std dev: 34.7 ns +- 1.4 ns

We should also check how this optimization affects other types:

$ ./python -m pyperf timeit -s "from math import floor" --duplicate 100 "floor(12345)"
Before:  Mean +- std dev: 56.3 ns +- 1.3 ns
After:   Mean +- std dev: 56.3 ns +- 1.4 ns

$ ./python -m pyperf timeit -s "from math import ceil" --duplicate 100 "ceil(12345)"
Before:  Mean +- std dev: 55.7 ns +- 1.6 ns
After:   Mean +- std dev: 56.8 ns +- 1.6 ns

$ ./python -m pyperf timeit -s "from math import trunc" --duplicate 100 "trunc(12345)"
Before:  Mean +- std dev: 54.7 ns +- 1.3 ns
After:   Mean +- std dev: 56.7 ns +- 1.5 ns

----------
components: Interpreter Core
messages: 355699
nosy: mark.dickinson, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Optimize floor() and ceil() for floats
type: performance
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38639>
_______________________________________

From report at bugs.python.org  Wed Oct 30 05:30:46 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 09:30:46 +0000
Subject: [issue38639] Optimize floor(), ceil() and trunc() for floats
In-Reply-To: <1572427776.81.0.21510885347.issue38639@roundup.psfhosted.org>
Message-ID: <1572427846.81.0.112548009931.issue38639@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
title: Optimize floor() and ceil() for floats -> Optimize floor(), ceil() and trunc() for floats

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38639>
_______________________________________

From report at bugs.python.org  Wed Oct 30 05:33:44 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 09:33:44 +0000
Subject: [issue38639] Optimize floor(), ceil() and trunc() for floats
In-Reply-To: <1572427776.81.0.21510885347.issue38639@roundup.psfhosted.org>
Message-ID: <1572428024.9.0.0907237301403.issue38639@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16517
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16991

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38639>
_______________________________________

From report at bugs.python.org  Wed Oct 30 05:48:06 2019
From: report at bugs.python.org (Hugo Dupras)
Date: Wed, 30 Oct 2019 09:48:06 +0000
Subject: [issue38640] while False: break => SyntaxError: 'break' outside loop
Message-ID: <1572428886.51.0.45563670991.issue38640@roundup.psfhosted.org>


New submission from Hugo Dupras <jabesq at gmail.com>:

In python 3.8 the following code raises an exception, which was not the case with previous python.

```
while False:
    ...
    break
```
It raises the following exception: SyntaxError: 'break' outside loop.
This `while False` loop was used to temporary disable a while loop in our code base.

Workaround to fix this:
```
enable=False
while enable:
    ...
    break
``` (or use the walrus operator)

----------
components: Interpreter Core
messages: 355700
nosy: jabesq
priority: normal
severity: normal
status: open
title: while False: break => SyntaxError: 'break' outside loop
type: behavior
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38640>
_______________________________________

From report at bugs.python.org  Wed Oct 30 05:52:41 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 30 Oct 2019 09:52:41 +0000
Subject: [issue38636] IDLE regression: toggle tabs and change indent width
 functions
In-Reply-To: <1572383648.52.0.228001978432.issue38636@roundup.psfhosted.org>
Message-ID: <1572429161.23.0.126341441419.issue38636@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Both the menu items and the short cuts for these two functions on the Format menu give these call errors.  They are only visible if IDLE is started from a console.

They work in 3.6; the regression is due to #36390.  These 2 functions were moved separately from the others in the 3rd PR, PR 14827, changeset 1b3892243433da7eae7f5f3a4f98f13d309c8926.  I found the mistake and believe I have one possible version of a working fix on a new branch.

The diff contains this comment:
  # With mixed indents not allowed, these are semi-useless and not unittested.
I was thinking that they should be removed, but regardless, they should have been manually tested.  However, in one test with 3.6, a mixed indent -- tab + 4 spaces following a 4 space tab -- did work, so I am not sure of the rule.  I will try to add a unittest along with the fix.

----------
components:  -Windows
nosy:  -paul.moore, steve.dower, tim.golden, zach.ware
stage:  -> test needed
title: "Alt + T" and "Alt + U" Broken in IDLE on Windows -> IDLE regression: toggle tabs and change indent width functions
versions: +Python 3.7, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38636>
_______________________________________

From report at bugs.python.org  Wed Oct 30 06:03:27 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 10:03:27 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572429807.33.0.67110934637.issue38600@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 25fc088607c855060ed142296dc1bd0125fad1af by Serhiy Storchaka in branch 'master':
bpo-38600: Change the mark up of NULL in the C API documentation. (GH-16950)
https://github.com/python/cpython/commit/25fc088607c855060ed142296dc1bd0125fad1af


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 06:03:56 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 10:03:56 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572429836.78.0.861892648995.issue28029@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 865c3b257fe38154a4320c7ee6afb416f665b9c2 by Serhiy Storchaka in branch 'master':
bpo-28029: Make "".replace("", s, n) returning s for any n != 0. (GH-16981)
https://github.com/python/cpython/commit/865c3b257fe38154a4320c7ee6afb416f665b9c2


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Wed Oct 30 06:06:16 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 10:06:16 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572429976.3.0.629023156874.issue28029@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Because of possible compatibility issue (very unlikely) this change is done only in master and will not be backported.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.9 -Python 2.7, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Wed Oct 30 06:10:22 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Wed, 30 Oct 2019 10:10:22 +0000
Subject: [issue38382] statistics.harmonic_mean fails to raise error with
 negative input that follows a 0
In-Reply-To: <1570326378.93.0.0728676630318.issue38382@roundup.psfhosted.org>
Message-ID: <1572430222.67.0.921169980418.issue38382@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

> Maybe we should hold-off on adding negative number support unless a compelling use case arises.

+100. It makes little sense mathematically, and I'm sceptical that such use cases exist in real life.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38382>
_______________________________________

From report at bugs.python.org  Wed Oct 30 06:17:43 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 10:17:43 +0000
Subject: [issue38640] while False: break => SyntaxError: 'break' outside loop
In-Reply-To: <1572428886.51.0.45563670991.issue38640@roundup.psfhosted.org>
Message-ID: <1572430663.03.0.344391879287.issue38640@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +3.8regression
nosy: +pablogsal, serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38640>
_______________________________________

From report at bugs.python.org  Wed Oct 30 07:24:15 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Wed, 30 Oct 2019 11:24:15 +0000
Subject: [issue38640] while False: break => SyntaxError: 'break' outside loop
In-Reply-To: <1572428886.51.0.45563670991.issue38640@roundup.psfhosted.org>
Message-ID: <1572434655.82.0.170550498598.issue38640@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +patch
pull_requests: +16518
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16992

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38640>
_______________________________________

From report at bugs.python.org  Wed Oct 30 07:26:26 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 11:26:26 +0000
Subject: [issue38630] subprocess.Popen.send_signal() should poll the process
In-Reply-To: <1572347906.82.0.50492662575.issue38630@roundup.psfhosted.org>
Message-ID: <1572434786.13.0.290284945735.issue38630@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> subprocess.Popen.send_signal() doesn't check if the process exited since the poll() method has been called for the last time. If the process exit just before os.kill() is called, the signal can be sent to the wrong process if the process identified is recycled.

I'm not sure under which conditions this case happens.

I understood that the pid is released (and so can be reused) as soon as the child process completes *and* waitpid() has been called.

Two cases:

* os.waitpid(pid, 0) can be called directly ("raw call")
* Popen API used, but called from a different thread: thread A calls send_signal(), thread B calls waitpid()

I'm mostly concerned by the multithreading case. I noticed the race condition while working on regrtest which uses 2 threads. One thread which is responsible for the process (call .communicate(), call .wait(), etc.), and one "main" thread which sends a signal to every child processes to interrupt them.

My first implementation called .wait() after calling .send_signal() in the main thread. But it seems like Popen is not "fully" thread safe: the "waitpid lock" only protects the os.waitpid() call, it doesn't protect the self.returncode attribute.

I modified regrtest to only call .waitpid() in the thread responsible of the process, to avoid such race condition. It seems like the new design is more reliable. The main thread only calls .send_signal(): it doesn't call .wait() (which calls os.waitpid()) anymore.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38630>
_______________________________________

From report at bugs.python.org  Wed Oct 30 07:32:55 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 11:32:55 +0000
Subject: [issue28029] Replace and empty strings
In-Reply-To: <1473366641.62.0.989746465638.issue28029@psf.upfronthosting.co.za>
Message-ID: <1572435175.2.0.13542247683.issue28029@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

> Because of possible compatibility issue (very unlikely) this change is done only in master and will not be backported.

Yeah, I agree. It would be a mistake to change the Python behavior in a minor release.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue28029>
_______________________________________

From report at bugs.python.org  Wed Oct 30 07:41:46 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 11:41:46 +0000
Subject: [issue38614] test_asyncio: test_communicate() failed on AMD64 FreeBSD
 Shared 3.8
In-Reply-To: <1572265095.84.0.80833057987.issue38614@roundup.psfhosted.org>
Message-ID: <1572435706.29.0.187090716751.issue38614@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 24c6258269acd842914450f55491690ba87dded9 by Victor Stinner in branch 'master':
bpo-38614: Add timeout constants to test.support (GH-16964)
https://github.com/python/cpython/commit/24c6258269acd842914450f55491690ba87dded9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38614>
_______________________________________

From report at bugs.python.org  Wed Oct 30 07:53:29 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Wed, 30 Oct 2019 11:53:29 +0000
Subject: [issue38640] while False: break => SyntaxError: 'break' outside loop
In-Reply-To: <1572428886.51.0.45563670991.issue38640@roundup.psfhosted.org>
Message-ID: <1572436409.48.0.770069141134.issue38640@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:


New changeset 6c3e66a34b95fff07df0ad5086104dd637a091ce by Pablo Galindo in branch 'master':
bpo-38640: Allow break and continue in always false while loops (GH-16992)
https://github.com/python/cpython/commit/6c3e66a34b95fff07df0ad5086104dd637a091ce


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38640>
_______________________________________

From report at bugs.python.org  Wed Oct 30 07:53:39 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 30 Oct 2019 11:53:39 +0000
Subject: [issue38640] while False: break => SyntaxError: 'break' outside loop
In-Reply-To: <1572428886.51.0.45563670991.issue38640@roundup.psfhosted.org>
Message-ID: <1572436419.08.0.488306425279.issue38640@roundup.psfhosted.org>


Change by miss-islington <mariatta.wijaya+miss-islington at gmail.com>:


----------
pull_requests: +16519
pull_request: https://github.com/python/cpython/pull/16993

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38640>
_______________________________________

From report at bugs.python.org  Wed Oct 30 07:57:25 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Wed, 30 Oct 2019 11:57:25 +0000
Subject: [issue38640] while False: break => SyntaxError: 'break' outside loop
In-Reply-To: <1572428886.51.0.45563670991.issue38640@roundup.psfhosted.org>
Message-ID: <1572436645.56.0.249178414657.issue38640@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

Thanks, Hugo Dupras for the report! :)

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38640>
_______________________________________

From report at bugs.python.org  Wed Oct 30 08:11:44 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 30 Oct 2019 12:11:44 +0000
Subject: [issue38640] while False: break => SyntaxError: 'break' outside loop
In-Reply-To: <1572428886.51.0.45563670991.issue38640@roundup.psfhosted.org>
Message-ID: <1572437504.16.0.747848835168.issue38640@roundup.psfhosted.org>


miss-islington <mariatta.wijaya+miss-islington at gmail.com> added the comment:


New changeset dcb338ea1b8f14e21dde3564658b9040df996349 by Miss Skeleton (bot) in branch '3.8':
bpo-38640: Allow break and continue in always false while loops (GH-16992)
https://github.com/python/cpython/commit/dcb338ea1b8f14e21dde3564658b9040df996349


----------
nosy: +miss-islington

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38640>
_______________________________________

From report at bugs.python.org  Wed Oct 30 08:18:45 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Wed, 30 Oct 2019 12:18:45 +0000
Subject: [issue38636] IDLE regression: toggle tabs and change indent width
 functions
In-Reply-To: <1572383648.52.0.228001978432.issue38636@roundup.psfhosted.org>
Message-ID: <1572437925.43.0.393151656577.issue38636@roundup.psfhosted.org>


Stephen Paul Chappell <Noctis.Skytower at gmail.com> added the comment:

When I start IDLE and the shell window appears, my first task is to press "Alt + T" to change from using tabs to spaces and then "Alt + U" to change from using 8 spaces to 4. This allows code pasted from the shell into an editor window or other IDE to not require reformatting since those settings seem to be common for Python code. If the defaults for these settings were to be exposed in IDLE's settings under the General tab (maybe near the new "Show line numbers in new windows" checkbox), would it be best to make that request here or to open a new bug with an enhancement suggestion?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38636>
_______________________________________

From report at bugs.python.org  Wed Oct 30 09:06:24 2019
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 30 Oct 2019 13:06:24 +0000
Subject: [issue32117] Tuple unpacking in return and yield statements
In-Reply-To: <1511393509.38.0.213398074469.issue32117@psf.upfronthosting.co.za>
Message-ID: <1572440784.6.0.662688628951.issue32117@roundup.psfhosted.org>


Change by Roundup Robot <devnull at psf.upfronthosting.co.za>:


----------
pull_requests: +16520
pull_request: https://github.com/python/cpython/pull/16994

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32117>
_______________________________________

From report at bugs.python.org  Wed Oct 30 09:19:43 2019
From: report at bugs.python.org (Vlad Emelianov)
Date: Wed, 30 Oct 2019 13:19:43 +0000
Subject: [issue38641] lib2to3 does not support py38 return/yield syntax with
 starred expressions
Message-ID: <1572441583.83.0.896942127015.issue38641@roundup.psfhosted.org>


New submission from Vlad Emelianov <volshebnyi at gmail.com>:

Lib2to3 does not support changes made in https://bugs.python.org/issue32117

```python
def test():
    my_list = ["value2", "value3"]
    yield "value1", *my_list
    return "value1", *my_list
```

The idea is to use `testlist_star_expr` instead of `testlist`.

This is a backwards compatible change, because testlist_star_expr supports test as well like testlist does.

----------
components: 2to3 (2.x to 3.x conversion tool)
messages: 355713
nosy: Vlad Emelianov
priority: normal
pull_requests: 16521
severity: normal
status: open
title: lib2to3 does not support py38 return/yield syntax with starred expressions
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38641>
_______________________________________

From report at bugs.python.org  Wed Oct 30 09:24:33 2019
From: report at bugs.python.org (Vlad Emelianov)
Date: Wed, 30 Oct 2019 13:24:33 +0000
Subject: [issue38641] lib2to3 does not support py38 return/yield syntax with
 starred expressions
In-Reply-To: <1572441583.83.0.896942127015.issue38641@roundup.psfhosted.org>
Message-ID: <1572441873.64.0.513018681242.issue38641@roundup.psfhosted.org>


Change by Vlad Emelianov <volshebnyi at gmail.com>:


----------
versions: +Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38641>
_______________________________________

From report at bugs.python.org  Wed Oct 30 10:06:00 2019
From: report at bugs.python.org (Marco Ippolito)
Date: Wed, 30 Oct 2019 14:06:00 +0000
Subject: [issue38642] python3.7.3 seems to cause add-apt-repository to rejct
 or not find gi library
Message-ID: <1572444360.24.0.26930433052.issue38642@roundup.psfhosted.org>


New submission from Marco Ippolito <ippolito.marco at gmail.com>:

Following the indications found here: https://docs.docker.com/install/linux/docker-ce/ubuntu/#install-using-the-repository 
I was trying to install Docker Engine in Ubuntu 18.04.02 Server Edition.

The first installation's steps went fine but I encountered this error message:

    (base) marco at pc:~$ sudo add-apt-repository \ 
    > "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
    > $(lsb_release -cs) \
    > stable"
    Traceback (most recent call last):
      File "/usr/bin/add-apt-repository", line 11, in <module>
        from softwareproperties.SoftwareProperties import SoftwareProperties, 
    shortcut_handler
      File "/usr/lib/python3/dist-packages/softwareproperties
    /SoftwareProperties.py", line 67, in <module>
        from gi.repository import Gio
      File "/usr/lib/python3/dist-packages/gi/__init__.py", line 42, in 
    <module>
        from . import _gi
    ImportError: cannot import name '_gi' from 'gi' (/usr/lib/python3/dist-
    packages/gi/__init__.py)

But import gi in python3 works fine:

    (base) marco at pc:~$ python3
    Python 3.7.3 (default, Mar 27 2019, 22:11:17) 
    [GCC 7.3.0] :: Anaconda, Inc. on linux
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import gi
    >>> 


After changing the first line of /usr/bin/add-apt-repository in order to point to 3.6 version :  #!/usr/bin/python3.6 everything went fine: 

    (base) marco at pc:~$ sudo add-apt-repository \
    >    "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
    >    $(lsb_release -cs) \
    >    stable"
    Hit:1 http://gb.archive.ubuntu.com/ubuntu bionic InRelease
    Get:2 https://download.docker.com/linux/ubuntu bionic InRelease [64.4 kB]                                                            
    Get:3 http://gb.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 
    kB]                                                         
    Get:4 http://gb.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6
     kB]
    Get:5 https://download.docker.com/linux/ubuntu bionic/stable amd64    
    Packages [9594 B]
    Get:6 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe i386 
    Packages [985 kB]  
    Get:7 http://gb.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
    Packages [1017 kB]
    Hit:8 http://apt.postgresql.org/pub/repos/apt bionic-pgdg InRelease                                                                                                                                        
    Hit:9 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease                                                                                                                                     
    Get:10 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 
    kB]                                                                                                                               
    Fetched 2328 kB in 11s (217 kB/s)                                                                                                                                                                          
    Reading package lists... Done

    (base) marco at pc:~$ sudo apt-get update
    Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
    Hit:2 http://apt.postgresql.org/pub/repos/apt bionic-pgdg InRelease
    Hit:3 http://gb.archive.ubuntu.com/ubuntu bionic InRelease
    Hit:4 http://gb.archive.ubuntu.com/ubuntu bionic-updates InRelease               
    Hit:5 http://gb.archive.ubuntu.com/ubuntu bionic-backports InRelease             
    Hit:6 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease
    Hit:7 https://download.docker.com/linux/ubuntu bionic InRelease
    Reading package lists... Done

    (base) marco at pc:~$ sudo apt-get install docker-ce docker-ce-cli 
    containerd.io
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    The following additional packages will be installed:
      aufs-tools cgroupfs-mount pigz
    The following NEW packages will be installed
      aufs-tools cgroupfs-mount containerd.io docker-ce docker-ce-cli pigz
    0 to upgrade, 6 to newly install, 0 to remove and 0 not to upgrade.
    Need to get 85.6 MB of archives.
    After this operation, 384 MB of additional disk space will be used.
    Do you want to continue? [Y/n] Y

So it seems that python3.7.3 has something which causes add-apt-repository to reject/not find gi library

----------
messages: 355714
nosy: Marco Ippolito
priority: normal
severity: normal
status: open
title: python3.7.3 seems to cause add-apt-repository to rejct or not find gi library
type: compile error
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38642>
_______________________________________

From report at bugs.python.org  Wed Oct 30 10:13:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 14:13:00 +0000
Subject: [issue38614] test_asyncio: test_communicate() failed on AMD64 FreeBSD
 Shared 3.8
In-Reply-To: <1572265095.84.0.80833057987.issue38614@roundup.psfhosted.org>
Message-ID: <1572444780.3.0.0367764200688.issue38614@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
pull_requests: +16522
pull_request: https://github.com/python/cpython/pull/16995

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38614>
_______________________________________

From report at bugs.python.org  Wed Oct 30 10:20:36 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Wed, 30 Oct 2019 14:20:36 +0000
Subject: [issue38643] Assertion failures when calling PyNumber_ToBase() with
 an invalid base
Message-ID: <1572445236.44.0.527192204316.issue38643@roundup.psfhosted.org>


New submission from Zackery Spytz <zspytz at gmail.com>:

If a base other than 2, 8, or 16 is passed to PyNumber_ToBase(), an assertion failure will occur. An exception should be raised instead.

This was mentioned in bpo-38249 (msg353039).

----------
components: Interpreter Core
messages: 355715
nosy: ZackerySpytz
priority: normal
severity: normal
status: open
title: Assertion failures when calling PyNumber_ToBase() with an invalid base
type: crash
versions: Python 2.7, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38643>
_______________________________________

From report at bugs.python.org  Wed Oct 30 10:24:53 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Wed, 30 Oct 2019 14:24:53 +0000
Subject: [issue38643] Assertion failures when calling PyNumber_ToBase() with
 an invalid base
In-Reply-To: <1572445236.44.0.527192204316.issue38643@roundup.psfhosted.org>
Message-ID: <1572445493.49.0.689071149479.issue38643@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
keywords: +patch
pull_requests: +16523
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16996

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38643>
_______________________________________

From report at bugs.python.org  Wed Oct 30 10:31:24 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 14:31:24 +0000
Subject: [issue38644] Pass explicitly tstate to function calls
Message-ID: <1572445884.39.0.966254854932.issue38644@roundup.psfhosted.org>


New submission from STINNER Victor <vstinner at python.org>:

Follow-up of bpo-36710 for function calls.

----------
components: Interpreter Core
messages: 355716
nosy: vstinner
priority: normal
severity: normal
status: open
title: Pass explicitly tstate to function calls
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38644>
_______________________________________

From report at bugs.python.org  Wed Oct 30 10:46:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 14:46:20 +0000
Subject: [issue38644] Pass explicitly tstate to function calls
In-Reply-To: <1572445884.39.0.966254854932.issue38644@roundup.psfhosted.org>
Message-ID: <1572446780.21.0.796178664497.issue38644@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16524
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16997

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38644>
_______________________________________

From report at bugs.python.org  Wed Oct 30 11:00:20 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 15:00:20 +0000
Subject: [issue38644] Pass explicitly tstate to function calls
In-Reply-To: <1572445884.39.0.966254854932.issue38644@roundup.psfhosted.org>
Message-ID: <1572447620.48.0.543290634624.issue38644@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

PR 16997 is a first step. The second step will be to pass tstate to:

* _PyObject_Vectorcall()
* _PyObject_MakeTpCall()
* _Py_CheckFunctionResult()

(I have a local branch that I have to rewrite on top of PR 16997.)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38644>
_______________________________________

From report at bugs.python.org  Wed Oct 30 11:00:47 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 15:00:47 +0000
Subject: [issue38614] test_asyncio: test_communicate() failed on AMD64 FreeBSD
 Shared 3.8
In-Reply-To: <1572265095.84.0.80833057987.issue38614@roundup.psfhosted.org>
Message-ID: <1572447647.89.0.648505682578.issue38614@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset a4ed6ed9f3779b6eda41bb65f5c09004a2b937ef by Victor Stinner in branch 'master':
bpo-38614: Increase asyncio test_communicate() timeout (GH-16995)
https://github.com/python/cpython/commit/a4ed6ed9f3779b6eda41bb65f5c09004a2b937ef


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38614>
_______________________________________

From report at bugs.python.org  Wed Oct 30 11:01:34 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 15:01:34 +0000
Subject: [issue38614] test_asyncio: test_communicate() failed on AMD64 FreeBSD
 Shared 3.8
In-Reply-To: <1572265095.84.0.80833057987.issue38614@roundup.psfhosted.org>
Message-ID: <1572447694.35.0.228945883276.issue38614@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:

PR 16995 should be backported to 3.7 and 3.8, but I will backport it once PR 16964 will be backported.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38614>
_______________________________________

From report at bugs.python.org  Wed Oct 30 11:03:02 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 15:03:02 +0000
Subject: [issue38631] Replace Py_FatalError() with regular Python exceptions
In-Reply-To: <1572352735.51.0.915792481752.issue38631@roundup.psfhosted.org>
Message-ID: <1572447782.96.0.528323968271.issue38631@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at python.org>:


----------
keywords: +patch
pull_requests: +16525
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/16998

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38631>
_______________________________________

From report at bugs.python.org  Wed Oct 30 11:07:25 2019
From: report at bugs.python.org (Michael Zhang)
Date: Wed, 30 Oct 2019 15:07:25 +0000
Subject: [issue38645] datetime.datetime.fromtimestamp(0,
 tzlocal()) throws error
Message-ID: <1572448045.56.0.183251608823.issue38645@roundup.psfhosted.org>


New submission from Michael Zhang <mzhangthirteen at gmail.com>:

Discovered this while trying to use a function in `boto3`. Seems like when tzlocal() is passed with a 0 to datetime.datetime.fromtimestamp(), it throws an "[Errno 22] Invalid argument" error. Using 3.7.4 via Anaconda on Windows 10, and tzlocal().tznames's local timezone for me is EST/EDT.

Can replicate through this:
```
import datetime
from dateutil.tz import tzlocal

print(datetime.datetime.fromtimestamp(0, tzlocal()))
```

----------
messages: 355720
nosy: mzhang13
priority: normal
severity: normal
status: open
title: datetime.datetime.fromtimestamp(0, tzlocal()) throws error
type: crash
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38645>
_______________________________________

From report at bugs.python.org  Wed Oct 30 11:09:43 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 30 Oct 2019 15:09:43 +0000
Subject: [issue38645] datetime.datetime.fromtimestamp(0,
 tzlocal()) throws error
In-Reply-To: <1572448045.56.0.183251608823.issue38645@roundup.psfhosted.org>
Message-ID: <1572448183.13.0.601517684634.issue38645@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +belopolsky, p-ganssle

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38645>
_______________________________________

From report at bugs.python.org  Wed Oct 30 11:39:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2019 15:39:30 +0000
Subject: [issue38631] Replace Py_FatalError() with regular Python exceptions
In-Reply-To: <1572352735.51.0.915792481752.issue38631@roundup.psfhosted.org>
Message-ID: <1572449970.7.0.739262622439.issue38631@roundup.psfhosted.org>


STINNER Victor <vstinner at python.org> added the comment:


New changeset 1d8da61f5ad26274556e0bbce260ce292d0402a1 by Victor Stinner in branch 'master':
bpo-38631: Avoid Py_FatalError() in readline (GH-16998)
https://github.com/python/cpython/commit/1d8da61f5ad26274556e0bbce260ce292d0402a1


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38631>
_______________________________________

From report at bugs.python.org  Wed Oct 30 12:12:03 2019
From: report at bugs.python.org (Batuhan)
Date: Wed, 30 Oct 2019 16:12:03 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
In-Reply-To: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>
Message-ID: <1572451923.56.0.921073493829.issue38629@roundup.psfhosted.org>


Batuhan <batuhanosmantaskaya at gmail.com> added the comment:

$ ./python -m pyperf timeit -s "from math import floor" --duplicate 100 "floor(12345.6)"
Before:  Mean +- std dev: 52.5 ns +- 2.6 ns
After:  Mean +- std dev: 71.0 ns +- 1.7 ns

$ ./python -m pyperf timeit -s "from math import ceil" --duplicate 100 "ceil(12345.6)"
Before:  Mean +- std dev: 51.2 ns +- 1.5 ns
After:  Mean +- std dev: 74.4 ns +- 2.2 ns

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Wed Oct 30 12:32:09 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 16:32:09 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572453129.75.0.185430475153.issue38600@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16526
pull_request: https://github.com/python/cpython/pull/16999

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 12:32:28 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 16:32:28 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572453148.09.0.13093734105.issue38600@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16527
pull_request: https://github.com/python/cpython/pull/17000

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 13:29:23 2019
From: report at bugs.python.org (Tom Lane)
Date: Wed, 30 Oct 2019 17:29:23 +0000
Subject: [issue38646] Invalid check on the result of pthread_self() leads to
 libpython startup failure
Message-ID: <1572456563.05.0.622338652634.issue38646@roundup.psfhosted.org>


New submission from Tom Lane <tgl at sss.pgh.pa.us>:

Assorted code in the Python core supposes that the result of pthread_self() cannot be equal to PYTHREAD_INVALID_THREAD_ID, ie (void *) -1.  If it is, you get a crash at interpreter startup.  Unfortunately, this supposition is directly contrary to the POSIX specification for pthread_self(), which defines no failure return value; and it is violated by NetBSD's implementation in some circumstances.  In particular, we (the Postgres project) are observing that libpython.so fails when dynamically loaded into a host executable that does not itself link libpthread.  NetBSD's code always returns -1 if libpthread was not present at main program start, as they do not support forking new threads in that case.  They assert (and I can't disagree) that their implementation conforms to POSIX.

A lazy man's solution might be to change PYTHREAD_INVALID_THREAD_ID to some other value like -3, but that's not fixing the core problem that you're violating POSIX by testing for any specific value at all.

Details and background info can be found in this email thread:

https://www.postgresql.org/message-id/flat/25662.1560896200%40sss.pgh.pa.us

----------
components: Interpreter Core
messages: 355723
nosy: tgl
priority: normal
severity: normal
status: open
title: Invalid check on the result of pthread_self() leads to libpython startup failure
type: crash
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38646>
_______________________________________

From report at bugs.python.org  Wed Oct 30 13:30:53 2019
From: report at bugs.python.org (Brandt Bucher)
Date: Wed, 30 Oct 2019 17:30:53 +0000
Subject: [issue38637] fix GROWTH_RATE comments bug
In-Reply-To: <1572401146.1.0.358314054297.issue38637@roundup.psfhosted.org>
Message-ID: <1572456653.58.0.0977230224702.issue38637@roundup.psfhosted.org>


Brandt Bucher <brandtbucher at gmail.com> added the comment:

This PR was closed as invalid for the same reasons Steven mentioned above.

----------
nosy: +brandtbucher
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38637>
_______________________________________

From report at bugs.python.org  Wed Oct 30 13:32:47 2019
From: report at bugs.python.org (Yoshihiro Nagano)
Date: Wed, 30 Oct 2019 17:32:47 +0000
Subject: [issue38647] Why only the MacOSXOSAScript in webbrowser does not have
 the name property?
Message-ID: <1572456767.92.0.8897291562.issue38647@roundup.psfhosted.org>


New submission from Yoshihiro Nagano <y.nagano.92 at gmail.com>:

Hello.

I am using the webbrowser library in macOS and just found that only the MacOSXOSAScript object has `_name` property instead of `name.`
All of the other class, which is inherited from the BaseBrowser, has `name` property.
Are there any specific reasons for this API?
Or, are there any ways to access the name of the browser object independent from the browser type?

The corresponding implementation is shown below:
https://github.com/python/cpython/blob/4cb08b6c0ae6989d169dd48c2b24087941f6d0b0/Lib/webbrowser.py#L641-L643

Thank you.

----------
components: Library (Lib), macOS
messages: 355725
nosy: Yoshihiro Nagano, ned.deily, ronaldoussoren
priority: normal
severity: normal
status: open
title: Why only the MacOSXOSAScript in webbrowser does not have the name property?
type: behavior
versions: Python 2.7, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38647>
_______________________________________

From report at bugs.python.org  Wed Oct 30 13:57:18 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 17:57:18 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572458238.3.0.0391517784409.issue38600@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16528
pull_request: https://github.com/python/cpython/pull/17001

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 14:27:32 2019
From: report at bugs.python.org (Maxwell Bernstein)
Date: Wed, 30 Oct 2019 18:27:32 +0000
Subject: [issue38648] Py_tp_free is specified twice in Python-ast.c
Message-ID: <1572460052.6.0.456691292805.issue38648@roundup.psfhosted.org>


New submission from Maxwell Bernstein <tekk.nolagi at gmail.com>:

This looks like a typo due to copy-paste.

----------
messages: 355726
nosy: tekknolagi
priority: normal
severity: normal
status: open
title: Py_tp_free is specified twice in Python-ast.c
versions: Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38648>
_______________________________________

From report at bugs.python.org  Wed Oct 30 14:27:56 2019
From: report at bugs.python.org (Maxwell Bernstein)
Date: Wed, 30 Oct 2019 18:27:56 +0000
Subject: [issue38648] Py_tp_free is specified twice in Python-ast.c
In-Reply-To: <1572460052.6.0.456691292805.issue38648@roundup.psfhosted.org>
Message-ID: <1572460076.53.0.176656845281.issue38648@roundup.psfhosted.org>


Change by Maxwell Bernstein <tekk.nolagi at gmail.com>:


----------
keywords: +patch
pull_requests: +16529
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/17002

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38648>
_______________________________________

From report at bugs.python.org  Wed Oct 30 15:36:33 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 19:36:33 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572464193.94.0.00156242579854.issue38600@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 7f7f986cc485c40d80bae504333e3946ce9e96ba by Serhiy Storchaka in branch '3.7':
[3.7] bpo-38600: Change the mark up of NULL in the C API documentation. (GH-16950) (GH-17000)
https://github.com/python/cpython/commit/7f7f986cc485c40d80bae504333e3946ce9e96ba


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 15:36:38 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 19:36:38 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572464198.98.0.284337385639.issue38600@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset f2ba17be2aec873741c2d8a55b1342afa360aec2 by Serhiy Storchaka in branch '3.8':
[3.8] bpo-38600: Change the mark up of NULL in the C API documentation. (GH-16950) (GH-16999)
https://github.com/python/cpython/commit/f2ba17be2aec873741c2d8a55b1342afa360aec2


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 15:37:05 2019
From: report at bugs.python.org (David Lambert)
Date: Wed, 30 Oct 2019 19:37:05 +0000
Subject: [issue38649] tkinter messagebox is sloppy
Message-ID: <1572464225.7.0.112082789313.issue38649@roundup.psfhosted.org>


New submission from David Lambert <b49p23tivg at gmail.com>:

Does aksokcancel return "true" or True ?  The docstring should say True   This is pervasive throughout the module.  tkinter has such a mishmash of numbers supplied as strings, strings supplied as constants making this carelessness egregious.  On the topic of constants, the messagebox module redefines OK.  You might argue that the definition didn't change.  I suspect this issue applies to all versions of tkinter or Tkinter having the messagebox.

# types
ABORTRETRYIGNORE = "abortretryignore"
OK = "ok"
...

# replies
...
OK = "ok"



def askokcancel(title=None, message=None, **options):
    "Ask if operation should proceed; return true if the answer is ok"
    s = _show(title, message, QUESTION, OKCANCEL, **options)
    return s == OK

----------
assignee: docs at python
components: Documentation
messages: 355729
nosy: David Lambert, docs at python
priority: normal
severity: normal
status: open
title: tkinter messagebox is sloppy
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38649>
_______________________________________

From report at bugs.python.org  Wed Oct 30 15:37:21 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 19:37:21 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572464241.57.0.10416070985.issue38600@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset e835b31d2b212c3c7820364398979cae2a9740b2 by Serhiy Storchaka in branch 'master':
bpo-38600: NULL -> ``NULL``. (GH-17001)
https://github.com/python/cpython/commit/e835b31d2b212c3c7820364398979cae2a9740b2


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 15:40:24 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 19:40:24 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572464424.97.0.715918477038.issue38600@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16530
pull_request: https://github.com/python/cpython/pull/17003

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 15:44:35 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 19:44:35 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572464675.88.0.0666133819988.issue38600@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
pull_requests: +16531
pull_request: https://github.com/python/cpython/pull/17004

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 16:01:43 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 20:01:43 +0000
Subject: [issue38650] Add constantness to PyStructSequence_UnnamedField
Message-ID: <1572465703.12.0.701099038847.issue38650@roundup.psfhosted.org>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

Currently the variable PyStructSequence_UnnamedField has type "char *". It is used as a special value for setting to the name field of PyStructSequence_Field. But the type of the name field is "const char *".

I propose to change the declaration of PyStructSequence_UnnamedField to "const char * const". Makes it referring to immutable character string and make it itself immutable.

It is binary compatible change, but some user code can complain at compilation time if it uses PyStructSequence_UnnamedField in unusual way (assigns to the "char *" variable, etc). It is very unlikely.

----------
components: Interpreter Core
messages: 355731
nosy: serhiy.storchaka
priority: normal
severity: normal
status: open
title: Add constantness to PyStructSequence_UnnamedField
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38650>
_______________________________________

From report at bugs.python.org  Wed Oct 30 16:05:36 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 20:05:36 +0000
Subject: [issue38650] Add constantness to PyStructSequence_UnnamedField
In-Reply-To: <1572465703.12.0.701099038847.issue38650@roundup.psfhosted.org>
Message-ID: <1572465936.34.0.0902366673836.issue38650@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
keywords: +patch
pull_requests: +16532
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/17005

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38650>
_______________________________________

From report at bugs.python.org  Wed Oct 30 16:17:36 2019
From: report at bugs.python.org (Steve Dower)
Date: Wed, 30 Oct 2019 20:17:36 +0000
Subject: [issue23903] Generate PC/python3.def by scraping headers
In-Reply-To: <1428637761.13.0.348463350169.issue23903@psf.upfronthosting.co.za>
Message-ID: <1572466656.24.0.786537349478.issue23903@roundup.psfhosted.org>


Steve Dower <steve.dower at python.org> added the comment:

Reawakening this issue so we can finish it off - the stable ABI has been declared "clean" on python-dev, so there shouldn't be any more concerns about APIs leaking in now. We can assume that everything accessible from the header files should be included in python3.def.

If it has been cleaned up though, we might need to go through and restore anything that used to be in python3.def but wasn't meant to be. Those are stable.

----------
versions: +Python 3.8, Python 3.9 -Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue23903>
_______________________________________

From report at bugs.python.org  Wed Oct 30 16:39:55 2019
From: report at bugs.python.org (Daniel Johnson)
Date: Wed, 30 Oct 2019 20:39:55 +0000
Subject: [issue38651] Add WolfSSL support
Message-ID: <1572467995.9.0.965883938595.issue38651@roundup.psfhosted.org>


New submission from Daniel Johnson <djwirecat at gmail.com>:

WolfSSL is an SSL library targeted at embedded development that focuses on size and speed. It's also FIPS certified which is is important for anyone working with federal agencies.

WolfSSL website: https://www.wolfssl.com/
WolfSSL github: https://github.com/wolfSSL/wolfssl

I have two ideas currently on how Python could support WolfSSL:

1.) Shim WolfSSL's OpenSSL compatibility layer in. They don't provide a complete shim for OpenSSL and I'm not sure if they provide all the symbols Python would care about.
2.) Provide an optional configuration to use WolfSSL and it's API instead of OpenSSL.

Would either options be something the Python maintainers would be interested in? I'm testing the waters to see if this is something anyone is interested in.

Thank you for the time!

----------
assignee: christian.heimes
components: SSL
messages: 355733
nosy: Daniel Johnson, christian.heimes
priority: normal
severity: normal
status: open
title: Add WolfSSL support
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38651>
_______________________________________

From report at bugs.python.org  Wed Oct 30 16:45:00 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 20:45:00 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572468300.5.0.477343435223.issue38600@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 2c921c65e9d0aa7e3a38c96a22d5eec56724da72 by Serhiy Storchaka in branch '3.8':
[3.8] bpo-38600: NULL -> ``NULL``. (GH-17001) (GH-17003)
https://github.com/python/cpython/commit/2c921c65e9d0aa7e3a38c96a22d5eec56724da72


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 16:45:17 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 30 Oct 2019 20:45:17 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572468317.86.0.977613844032.issue38600@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 951b6c314a8567be3b5d901059fde866c79f5ff0 by Serhiy Storchaka in branch '3.7':
[3.7] bpo-38600: NULL -> ``NULL``. (GH-17001) (GH-17004)
https://github.com/python/cpython/commit/951b6c314a8567be3b5d901059fde866c79f5ff0


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Wed Oct 30 18:11:08 2019
From: report at bugs.python.org (Anselmo Melo)
Date: Wed, 30 Oct 2019 22:11:08 +0000
Subject: [issue38576] CVE-2019-18348: CRLF injection via the host part of the
 url passed to urlopen()
In-Reply-To: <1571903478.88.0.753943817426.issue38576@roundup.psfhosted.org>
Message-ID: <1572473468.11.0.551617880868.issue38576@roundup.psfhosted.org>


Change by Anselmo Melo <anselmo.melo at intel.com>:


----------
nosy: +Anselmo Melo

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38576>
_______________________________________

From report at bugs.python.org  Wed Oct 30 21:08:20 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Thu, 31 Oct 2019 01:08:20 +0000
Subject: [issue38648] Py_tp_free is specified twice in Python-ast.c
In-Reply-To: <1572460052.6.0.456691292805.issue38648@roundup.psfhosted.org>
Message-ID: <1572484100.83.0.557313414355.issue38648@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset bdac32e9fe25fdb97a7172a93aabd1ffead89462 by Benjamin Peterson (Max Bernstein) in branch 'master':
closes bpo-38648: Remove double tp_free slot in Python-ast.c. (GH-17002)
https://github.com/python/cpython/commit/bdac32e9fe25fdb97a7172a93aabd1ffead89462


----------
nosy: +benjamin.peterson
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38648>
_______________________________________

From report at bugs.python.org  Wed Oct 30 21:58:11 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 31 Oct 2019 01:58:11 +0000
Subject: [issue38636] IDLE regression: toggle tabs and change indent width
 functions
In-Reply-To: <1572383648.52.0.228001978432.issue38636@roundup.psfhosted.org>
Message-ID: <1572487091.52.0.942734149147.issue38636@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Interesting.  The result of making these changes is legal code looking like
>>> if a:
    if b:
        c = 3
This has been proposed as the way Shell should work, but rejected as likely too confusing to beginners as the indented code does not look indented compared to the line above.  The use of tabs for indents in Shell has long been considered a wart that is a 'least bad solution'.

Please hold your proposals.  I intend to solve the issue by moving the prompt to a shell sidebar and use the same indent in shell as in editors.  #37903 has a PR under review.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38636>
_______________________________________

From report at bugs.python.org  Wed Oct 30 22:13:22 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 31 Oct 2019 02:13:22 +0000
Subject: [issue38636] IDLE regression: toggle tabs and change indent width
 functions
In-Reply-To: <1572383648.52.0.228001978432.issue38636@roundup.psfhosted.org>
Message-ID: <1572488002.4.0.867743528448.issue38636@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
keywords: +patch
pull_requests: +16533
stage: test needed -> patch review
pull_request: https://github.com/python/cpython/pull/17008

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38636>
_______________________________________

From report at bugs.python.org  Wed Oct 30 22:20:17 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 31 Oct 2019 02:20:17 +0000
Subject: [issue38636] IDLE regression: toggle tabs and change indent width
 functions
In-Reply-To: <1572383648.52.0.228001978432.issue38636@roundup.psfhosted.org>
Message-ID: <1572488417.82.0.437955718015.issue38636@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

The old, long discussion of Shell indents is #7676 and a preceding issue reference therein.  My replacement is #37892.

The PR patch is simple enough to apply by to existing 3.7.5 and 3.8.0 installs.

----------
stage: patch review -> test needed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38636>
_______________________________________

From report at bugs.python.org  Thu Oct 31 02:14:41 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 31 Oct 2019 06:14:41 +0000
Subject: [issue38652] Remove/update provisional note for
 asyncio.BufferedProtocol
Message-ID: <1572502481.2.0.695475270667.issue38652@roundup.psfhosted.org>


New submission from Kyle Stanley <aeros167 at gmail.com>:

In the documentation (https://docs.python.org/3.9/library/asyncio-protocol.html#buffered-streaming-protocols) for asyncio.BufferedProtocol there is a provisional API note. This should be updated/removed for 3.8 and 3.9 since it became a part of the stable API in 3.8.

Current:

> New in version 3.7: Important: this has been added to asyncio in Python 3.7 on a provisional basis! This is as an experimental API that might be changed or removed completely in Python 3.8.

I would propose to changing it to:

> New in version 3.7.

----------
assignee: docs at python
components: Documentation
messages: 355739
nosy: aeros, asvetlov, docs at python, yselivanov
priority: normal
severity: normal
status: open
title: Remove/update provisional note for asyncio.BufferedProtocol
versions: Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38652>
_______________________________________

From report at bugs.python.org  Thu Oct 31 02:20:16 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 31 Oct 2019 06:20:16 +0000
Subject: [issue38652] Remove/update provisional note for
 asyncio.BufferedProtocol
In-Reply-To: <1572502481.2.0.695475270667.issue38652@roundup.psfhosted.org>
Message-ID: <1572502816.48.0.848474386251.issue38652@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> I would propose to changing it to:

propose changing it to*

Also, I think this issue would be a good candidate for "newcomer friendly", since it's a simple and well-defined documentation update. It could provide a decent introduction for contributing to CPython.

----------
keywords: +newcomer friendly

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38652>
_______________________________________

From report at bugs.python.org  Thu Oct 31 02:22:02 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 31 Oct 2019 06:22:02 +0000
Subject: [issue38652] Remove/update provisional note for
 asyncio.BufferedProtocol
In-Reply-To: <1572502481.2.0.695475270667.issue38652@roundup.psfhosted.org>
Message-ID: <1572502922.71.0.627093416085.issue38652@roundup.psfhosted.org>


Change by Kyle Stanley <aeros167 at gmail.com>:


----------
components: +asyncio

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38652>
_______________________________________

From report at bugs.python.org  Thu Oct 31 02:50:51 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Thu, 31 Oct 2019 06:50:51 +0000
Subject: [issue22367] Add open_file_descriptor parameter to fcntl.lockf() (use
 the new F_OFD_SETLK flag)
In-Reply-To: <1410207529.54.0.778133775349.issue22367@psf.upfronthosting.co.za>
Message-ID: <1572504650.99.0.495628437949.issue22367@roundup.psfhosted.org>


Change by Dong-hee Na <donghee.na92 at gmail.com>:


----------
pull_requests: +16534
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/17010

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue22367>
_______________________________________

From report at bugs.python.org  Thu Oct 31 04:04:02 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 31 Oct 2019 08:04:02 +0000
Subject: [issue16575] ctypes: unions as arguments
In-Reply-To: <1354163044.21.0.431588472559.issue16575@psf.upfronthosting.co.za>
Message-ID: <1572509042.56.0.719610086376.issue16575@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset 79d4ed102a5069c6cebaed2627cb1645637f0429 by Vinay Sajip in branch 'master':
bpo-16575: Add checks for unions passed by value to functions. (GH-16799)
https://github.com/python/cpython/commit/79d4ed102a5069c6cebaed2627cb1645637f0429


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16575>
_______________________________________

From report at bugs.python.org  Thu Oct 31 04:06:29 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 31 Oct 2019 08:06:29 +0000
Subject: [issue38586] logging: handlers names are not set when using fileConfig
In-Reply-To: <1571930163.44.0.759260613385.issue38586@roundup.psfhosted.org>
Message-ID: <1572509189.03.0.794432369872.issue38586@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset b15100fe7def8580c78ed16f0bb4b72b2ae7af3f by Vinay Sajip (Lucas Cimon) in branch 'master':
bpo-38586: setting logging.Handler .name property in fileConfig (GH-16918)
https://github.com/python/cpython/commit/b15100fe7def8580c78ed16f0bb4b72b2ae7af3f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38586>
_______________________________________

From report at bugs.python.org  Thu Oct 31 04:07:24 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 31 Oct 2019 08:07:24 +0000
Subject: [issue38586] logging: handlers names are not set when using fileConfig
In-Reply-To: <1571930163.44.0.759260613385.issue38586@roundup.psfhosted.org>
Message-ID: <1572509244.64.0.561440920401.issue38586@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type:  -> enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38586>
_______________________________________

From report at bugs.python.org  Thu Oct 31 05:13:54 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 31 Oct 2019 09:13:54 +0000
Subject: [issue38312] curses: add `set_tabsize` and `set_escdelay`
In-Reply-To: <1569721208.44.0.258918770799.issue38312@roundup.psfhosted.org>
Message-ID: <1572513234.84.0.512230551196.issue38312@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset b32cb97bce472dad337c6b2f071883f6234e21d8 by Serhiy Storchaka (Anthony Sottile) in branch 'master':
bpo-38312: Add curses.{get,set}_escdelay and curses.{get,set}_tabsize. (GH-16938)
https://github.com/python/cpython/commit/b32cb97bce472dad337c6b2f071883f6234e21d8


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38312>
_______________________________________

From report at bugs.python.org  Thu Oct 31 05:14:27 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 31 Oct 2019 09:14:27 +0000
Subject: [issue38312] curses: add `set_tabsize` and `set_escdelay`
In-Reply-To: <1569721208.44.0.258918770799.issue38312@roundup.psfhosted.org>
Message-ID: <1572513267.6.0.604890544456.issue38312@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38312>
_______________________________________

From report at bugs.python.org  Thu Oct 31 06:41:40 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 31 Oct 2019 10:41:40 +0000
Subject: [issue38600] Change the mark up of NULL
In-Reply-To: <1572164169.73.0.860465695362.issue38600@roundup.psfhosted.org>
Message-ID: <1572518500.69.0.245197290487.issue38600@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38600>
_______________________________________

From report at bugs.python.org  Thu Oct 31 06:54:54 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Thu, 31 Oct 2019 10:54:54 +0000
Subject: [issue38629] float is missing __ceil__() and __floor__(),
 required by numbers.Real
In-Reply-To: <1572344297.94.0.916739375163.issue38629@roundup.psfhosted.org>
Message-ID: <1572519294.13.0.338887270849.issue38629@roundup.psfhosted.org>


Vedran ?a?i? <vedgar at gmail.com> added the comment:

However, this is an instance of a general problem: whenever we want to strongly type (via dunders) protocols that specialcase builtin types, we will have to choose between three options:

* special case them also in typing engine, complicating the typing engine
* implement dummy dunders, puzzling readers of the code
* implement dunders that do the right thing but never actually execute, puzzling Serhiy (and probably others)
* implement dunders that are actually called (un-specialcasing builtin types), slowing down the common path

Do we have a preference for a "default" position when we encounter such problems in the future? Of course, we can override it on a case-by-case basis in the presence of good arguments, but still, a default would be nice to have.

I don't know much about static typing (which is why I loved Python until this typing craze happened:), but it seems to me that we might have another option: we can currently say that a type might be a virtual subclass of an abstract class in more than one way, right? For example, we still support old-style iterators (via __getitem__ and IndexError), IIRC. So, can we say that a type can implement numbers.Real also in two ways: by having some dunders, or by being (a literal or a subtype of) float?

----------
nosy: +veky

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38629>
_______________________________________

From report at bugs.python.org  Thu Oct 31 07:28:28 2019
From: report at bugs.python.org (Hartmut Goebel)
Date: Thu, 31 Oct 2019 11:28:28 +0000
Subject: [issue38653] pkgutil.extend_path fails with zipped eggs if not at
 first place
Message-ID: <1572521308.12.0.490608170281.issue38653@roundup.psfhosted.org>


New submission from Hartmut Goebel <h.goebel at crazy-compilers.com>:

I have a test site containing nested namespace packages in zipped and unzipped eggs_

- nspkg3_aaa.egg - unzipped egg, namespaces: nspkg3
- nspkg3_bbb.egg - zipped egg  , namespaces: nspkg3, nspkg3.bbb
- nspkg3_ccc.egg - unzipped egg, namespaces: nspkg3

When using order "aaa, bbb, ccc" in PYTHONPATH, importing "nspkg3.bbb" FAILS,
whereas
when using order "bbb, aaa, ccc" in PYTHONPATH, importing "nspkg3.bbb" PASSES,

I would expect "nspk3.bbb" to ba importable 8as a namespace package) no matter which possition it has in PYTHONPATH.


How to reproduce

Preperation: get hands on the eggs in question:

$ wget https://github.com/pyinstaller/pyinstaller/archive/v3.5.zip
$ unzip v3.5.zip
$ cd pyinstaller-3.5/tests/functional/modules/nspkg3-pkg/

Order "aaa, bbb, ccc": fails

$ PYTHONPATH=nspkg3_aaa.egg:nspkg3_bbb.egg:nspkg3_ccc.egg python3.7 -c "import nspkg3.bbb.zzz"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'nspkg3.bbb'

Order "bbb, aaa, ccc": passes:

$ PYTHONPATH=nspkg3_bbb.egg:nspkg3_aaa.egg:nspkg3_ccc.egg python3.7 -c "import nspkg3.bbb.zzz"
this is module nspkg3.bbb.zzz


Further information

I did some research and found that the zipped egg (bbb) is *not added* to the package path when using order "aaa, bbb, ccc":

Order "aaa, bbb, ccc":  bbb is missing here

$ PYTHONPATH=nspkg3_aaa.egg:nspkg3_bbb.egg:nspkg3_ccc.egg \
   python3.7 -c "import nspkg3 ; print(nspkg3.__path__)"
['?/nspkg3_aaa.egg/nspkg3', '?/nspkg3_ccc.egg/nspkg3']

Order "bbb, aaa, ccc":  bbb is included

$ PYTHONPATH=nspkg3_bbb.egg:nspkg3_aaa.egg:nspkg3_ccc.egg \
   python3.7 -c "import nspkg3 ; print(nspkg3.__path__)"
['?/nspkg3_bbb.egg/nspkg3', '?/nspkg3_aaa.egg/nspkg3', '?/nspkg3_ccc.egg/nspkg3']


Also tested with Python 2.7: Same results

----------
components: Library (Lib)
messages: 355745
nosy: htgoebel
priority: normal
severity: normal
status: open
title: pkgutil.extend_path fails with zipped eggs if not at first place
type: behavior
versions: Python 2.7, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38653>
_______________________________________

From report at bugs.python.org  Thu Oct 31 07:55:13 2019
From: report at bugs.python.org (Benjamin Edwards)
Date: Thu, 31 Oct 2019 11:55:13 +0000
Subject: [issue38652] Remove/update provisional note for
 asyncio.BufferedProtocol
In-Reply-To: <1572502481.2.0.695475270667.issue38652@roundup.psfhosted.org>
Message-ID: <1572522913.09.0.506399821886.issue38652@roundup.psfhosted.org>


Benjamin Edwards <benjaminedwards at live.co.uk> added the comment:

Hey Kyle,

I'm a newcomer, would it be ok for me to take on this propsal?

Ben

----------
nosy: +benedwards14

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38652>
_______________________________________

From report at bugs.python.org  Thu Oct 31 08:28:33 2019
From: report at bugs.python.org (Netzeband)
Date: Thu, 31 Oct 2019 12:28:33 +0000
Subject: [issue37838] typing.get_type_hints not working with
 forward-declaration and decorated functions
In-Reply-To: <1565692979.16.0.678723196671.issue37838@roundup.psfhosted.org>
Message-ID: <1572524913.68.0.0281472975593.issue37838@roundup.psfhosted.org>


Netzeband <andre at netzeband.eu> added the comment:

Thanks a lot!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37838>
_______________________________________

From report at bugs.python.org  Thu Oct 31 08:52:24 2019
From: report at bugs.python.org (Jackson Riley)
Date: Thu, 31 Oct 2019 12:52:24 +0000
Subject: [issue9338] argparse optionals with nargs='?',
 '*' or '+' can't be followed by positionals
In-Reply-To: <1279881989.28.0.725806934086.issue9338@psf.upfronthosting.co.za>
Message-ID: <1572526344.48.0.625142489927.issue9338@roundup.psfhosted.org>


Jackson Riley <jacriley at cisco.com> added the comment:

I'm a newcomer and thought about trying to follow up on this and potentially update existing patches, would this be a good idea?

----------
nosy: +jacksonriley

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue9338>
_______________________________________

From report at bugs.python.org  Thu Oct 31 08:53:31 2019
From: report at bugs.python.org (Jackson Riley)
Date: Thu, 31 Oct 2019 12:53:31 +0000
Subject: =?utf-8?q?=5Bissue9182=5D_document_=E2=80=9C--=E2=80=9D_as_a_way_to_disti?=
 =?utf-8?q?nguish_option_w/_narg=3D=27+=27_from_positional_argument_in_arg?=
 =?utf-8?q?parse?=
In-Reply-To: <1278433481.81.0.201692715302.issue9182@psf.upfronthosting.co.za>
Message-ID: <1572526411.62.0.0749248845539.issue9182@roundup.psfhosted.org>


Jackson Riley <jacriley at cisco.com> added the comment:

Hi all, I'm a newcomer and wanted to try to make this change, is it still wanted/needed?

----------
nosy: +jacksonriley

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue9182>
_______________________________________

From report at bugs.python.org  Thu Oct 31 09:01:34 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 31 Oct 2019 13:01:34 +0000
Subject: [issue16575] ctypes: unions as arguments
In-Reply-To: <1354163044.21.0.431588472559.issue16575@psf.upfronthosting.co.za>
Message-ID: <1572526894.68.0.205560544364.issue16575@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests: +16535
pull_request: https://github.com/python/cpython/pull/17016

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16575>
_______________________________________

From report at bugs.python.org  Thu Oct 31 09:09:54 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 31 Oct 2019 13:09:54 +0000
Subject: [issue16575] ctypes: unions as arguments
In-Reply-To: <1354163044.21.0.431588472559.issue16575@psf.upfronthosting.co.za>
Message-ID: <1572527394.25.0.710072973355.issue16575@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests: +16536
pull_request: https://github.com/python/cpython/pull/17017

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16575>
_______________________________________

From report at bugs.python.org  Thu Oct 31 09:17:53 2019
From: report at bugs.python.org (Efanzh)
Date: Thu, 31 Oct 2019 13:17:53 +0000
Subject: [issue38654] `urllib.request.Request` uses mutable value as default
 value
Message-ID: <1572527873.7.0.615539123104.issue38654@roundup.psfhosted.org>


New submission from Efanzh <efanzh at gmail.com>:

The `headers` argument of the `__init__` method of `urllib.request.Request` class uses `{}` as default value, which is mutable. It is not a good idea.

----------
components: Library (Lib)
messages: 355750
nosy: EFanZh
priority: normal
pull_requests: 16537
severity: normal
status: open
title: `urllib.request.Request` uses mutable value as default value
type: enhancement
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38654>
_______________________________________

From report at bugs.python.org  Thu Oct 31 09:34:11 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 31 Oct 2019 13:34:11 +0000
Subject: [issue16575] ctypes: unions as arguments
In-Reply-To: <1354163044.21.0.431588472559.issue16575@psf.upfronthosting.co.za>
Message-ID: <1572528851.84.0.0784510274078.issue16575@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset 952899704800a5aa438e84d50f0b6fc498c72e89 by Vinay Sajip in branch '3.8':
[3.8] bpo-16575: Add checks for unions passed by value to functions. (GH-16799) (GH-17016)
https://github.com/python/cpython/commit/952899704800a5aa438e84d50f0b6fc498c72e89


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16575>
_______________________________________

From report at bugs.python.org  Thu Oct 31 09:58:26 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 13:58:26 +0000
Subject: [issue37903] IDLE Shell sidebar.
In-Reply-To: <1566370033.98.0.615651298891.issue37903@roundup.psfhosted.org>
Message-ID: <1572530306.56.0.503593621523.issue37903@roundup.psfhosted.org>


Stephen Paul Chappell <Noctis.Skytower at gmail.com> added the comment:

The documentation for sys.ps1 and sys.ps2 states that they "are only defined if the interpreter is in interactive mode." Since the IDLE shell is meant to be interactive (and to reduce the differences between the shell and running Python directly), would it be helpful if ps1 and ps2 were defined when running IDLE? The shell could then honor their values.

If such a direction was explored, one issue may be that the sidebar could not simply be 3 char wide. The documentation also states that non-strings are evaluated each time they are needed by the interpreter. This allows for such interesting possibilities as shown with the code below but may not be desired functionality for the IDLE shell window.

import sys
from datetime import datetime

class TimePrompt:
    def __init__(self, prefix, suffix):
        self.prefix, self.suffix = prefix, suffix
    def __str__(self):
        return f'{self.prefix}{datetime.now()}{self.suffix}'

sys.ps1, sys.ps2 = TimePrompt('', ' >>> '), TimePrompt('', ' ... ')

----------
nosy: +Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37903>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:04:51 2019
From: report at bugs.python.org (pascalhofmann)
Date: Thu, 31 Oct 2019 14:04:51 +0000
Subject: [issue38655] ipaddress.ip_network('0.0.0.0/0').is_private == True
Message-ID: <1572530691.84.0.462430681921.issue38655@roundup.psfhosted.org>


New submission from pascalhofmann <mail at pascalhofmann.de>:

ipaddress.ip_network('0.0.0.0/0').is_private returns True, even though 0.0.0.0/0 clearly is no private network.

----------
components: Library (Lib)
messages: 355753
nosy: pascalhofmann
priority: normal
severity: normal
status: open
title: ipaddress.ip_network('0.0.0.0/0').is_private == True
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38655>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:15:18 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 31 Oct 2019 14:15:18 +0000
Subject: [issue16575] ctypes: unions as arguments
In-Reply-To: <1354163044.21.0.431588472559.issue16575@psf.upfronthosting.co.za>
Message-ID: <1572531318.12.0.94554290926.issue16575@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset 0118d109d54bf75c99a8b0fa9aeae1a478ac4b7e by Vinay Sajip in branch '3.7':
[3.7] bpo-16575: Add checks for unions passed by value to functions. (GH-16799) (GH-17017)
https://github.com/python/cpython/commit/0118d109d54bf75c99a8b0fa9aeae1a478ac4b7e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16575>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:17:04 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 31 Oct 2019 14:17:04 +0000
Subject: [issue16575] ctypes: unions as arguments
In-Reply-To: <1354163044.21.0.431588472559.issue16575@psf.upfronthosting.co.za>
Message-ID: <1572531424.26.0.420065272761.issue16575@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
assignee: docs at python -> vinay.sajip
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue16575>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:17:46 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 31 Oct 2019 14:17:46 +0000
Subject: [issue11410] Use GCC visibility attrs in PyAPI_*
In-Reply-To: <1299391945.72.0.037942723875.issue11410@psf.upfronthosting.co.za>
Message-ID: <1572531466.44.0.123303367396.issue11410@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue11410>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:19:46 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Thu, 31 Oct 2019 14:19:46 +0000
Subject: [issue35328] Set a environment variable for venv prompt
In-Reply-To: <1543335149.71.0.788709270274.issue35328@psf.upfronthosting.co.za>
Message-ID: <1572531586.55.0.741902051184.issue35328@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
versions: +Python 3.9 -Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35328>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:21:44 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 14:21:44 +0000
Subject: [issue7676] IDLE shell shouldn't use TABs
In-Reply-To: <1263213381.47.0.181451927584.issue7676@psf.upfronthosting.co.za>
Message-ID: <1572531704.48.0.429080188993.issue7676@roundup.psfhosted.org>


Change by Stephen Paul Chappell <Noctis.Skytower at gmail.com>:


----------
nosy:  -Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue7676>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:22:00 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 14:22:00 +0000
Subject: [issue31476] Stdlib source files not installed
In-Reply-To: <1505418617.55.0.339159278979.issue31476@psf.upfronthosting.co.za>
Message-ID: <1572531720.65.0.765726384261.issue31476@roundup.psfhosted.org>


Change by Stephen Paul Chappell <Noctis.Skytower at gmail.com>:


----------
nosy:  -Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31476>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:22:13 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 14:22:13 +0000
Subject: [issue31848] "aifc" module does not always initialize
 "Aifc_read._ssnd_chunk"
In-Reply-To: <1508765581.06.0.213398074469.issue31848@psf.upfronthosting.co.za>
Message-ID: <1572531733.17.0.854687832836.issue31848@roundup.psfhosted.org>


Change by Stephen Paul Chappell <Noctis.Skytower at gmail.com>:


----------
nosy:  -Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31848>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:22:25 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 14:22:25 +0000
Subject: [issue18558] Iterable glossary entry needs clarification
In-Reply-To: <1374796651.89.0.668716719647.issue18558@psf.upfronthosting.co.za>
Message-ID: <1572531745.91.0.373607392291.issue18558@roundup.psfhosted.org>


Change by Stephen Paul Chappell <Noctis.Skytower at gmail.com>:


----------
nosy:  -Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue18558>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:22:37 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 14:22:37 +0000
Subject: [issue21537] functools.lru_cache does not cache exceptions
In-Reply-To: <1400525939.56.0.613557499448.issue21537@psf.upfronthosting.co.za>
Message-ID: <1572531757.36.0.31731973777.issue21537@roundup.psfhosted.org>


Change by Stephen Paul Chappell <Noctis.Skytower at gmail.com>:


----------
nosy:  -Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21537>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:22:49 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 14:22:49 +0000
Subject: [issue24185] Add Function for Sending File to Trash (or Recycling Bin)
In-Reply-To: <1431574601.59.0.7462724115.issue24185@psf.upfronthosting.co.za>
Message-ID: <1572531769.44.0.465310450218.issue24185@roundup.psfhosted.org>


Change by Stephen Paul Chappell <Noctis.Skytower at gmail.com>:


----------
nosy:  -Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue24185>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:22:57 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 14:22:57 +0000
Subject: [issue21957] ASCII Formfeed (FF) & ASCII Vertical Tab (VT) Have
 Hexadecimal Representation
In-Reply-To: <1405088980.95.0.801380317459.issue21957@psf.upfronthosting.co.za>
Message-ID: <1572531777.56.0.702427496271.issue21957@roundup.psfhosted.org>


Change by Stephen Paul Chappell <Noctis.Skytower at gmail.com>:


----------
nosy:  -Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21957>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:23:06 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 14:23:06 +0000
Subject: [issue21402] tkinter.ttk._val_or_dict assumes tkinter._default_root
 exists
In-Reply-To: <1398885763.19.0.937315925175.issue21402@psf.upfronthosting.co.za>
Message-ID: <1572531786.24.0.161476536278.issue21402@roundup.psfhosted.org>


Change by Stephen Paul Chappell <Noctis.Skytower at gmail.com>:


----------
nosy:  -Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue21402>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:23:16 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 14:23:16 +0000
Subject: [issue18601] Example "command-line interface to difflib" has
 typographical error
In-Reply-To: <1375211246.29.0.527231910426.issue18601@psf.upfronthosting.co.za>
Message-ID: <1572531796.39.0.15131546476.issue18601@roundup.psfhosted.org>


Change by Stephen Paul Chappell <Noctis.Skytower at gmail.com>:


----------
nosy:  -Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue18601>
_______________________________________

From report at bugs.python.org  Thu Oct 31 10:23:36 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 14:23:36 +0000
Subject: [issue6188] Error Evaluating float(x) ** float(y)
In-Reply-To: <1244035203.68.0.223995405838.issue6188@psf.upfronthosting.co.za>
Message-ID: <1572531816.94.0.731316284084.issue6188@roundup.psfhosted.org>


Change by Stephen Paul Chappell <Noctis.Skytower at gmail.com>:


----------
nosy:  -Zero

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue6188>
_______________________________________

From report at bugs.python.org  Thu Oct 31 11:03:59 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 31 Oct 2019 15:03:59 +0000
Subject: [issue37903] IDLE Shell sidebar.
In-Reply-To: <1566370033.98.0.615651298891.issue37903@roundup.psfhosted.org>
Message-ID: <1572534239.07.0.239216240514.issue37903@roundup.psfhosted.org>


Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:

Will the current interactive shell continue to be available?

----------
nosy: +rhettinger

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37903>
_______________________________________

From report at bugs.python.org  Thu Oct 31 11:10:29 2019
From: report at bugs.python.org (Tal Einat)
Date: Thu, 31 Oct 2019 15:10:29 +0000
Subject: [issue37903] IDLE Shell sidebar.
In-Reply-To: <1566370033.98.0.615651298891.issue37903@roundup.psfhosted.org>
Message-ID: <1572534629.25.0.125129503942.issue37903@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:

Stehpen, I'm not sure what your use-case is... To me it seems that sys.ps1 (and ps2?) aren't quite relevant any more when using a sidebar, since there are no longer inline prompts.

Raymond, with the current PR, this replaces the inline prompts. Making it toggle-able could be very awkward. Is this a deal-breaker in your opinion?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37903>
_______________________________________

From report at bugs.python.org  Thu Oct 31 11:10:41 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 31 Oct 2019 15:10:41 +0000
Subject: [issue38654] `urllib.request.Request` uses mutable value as default
 value
In-Reply-To: <1572527873.7.0.615539123104.issue38654@roundup.psfhosted.org>
Message-ID: <1572534641.22.0.739948217862.issue38654@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

There is nothing wrong with using {} as default value.

----------
nosy: +serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38654>
_______________________________________

From report at bugs.python.org  Thu Oct 31 11:37:22 2019
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Thu, 31 Oct 2019 15:37:22 +0000
Subject: [issue37903] IDLE Shell sidebar.
In-Reply-To: <1566370033.98.0.615651298891.issue37903@roundup.psfhosted.org>
Message-ID: <1572536242.34.0.534435700768.issue37903@roundup.psfhosted.org>


Stephen Paul Chappell <Noctis.Skytower at gmail.com> added the comment:

Maybe my impression has been false this whole time, but the Python interactive interpreter seems to be very similar to the IDLE shell window. My question is, "Why not make them even more so?" Having IDLE react to sys.ps1 and sys.ps2 opens up the shell to similar use cases as having them defined in the interactive interpreter. My suggestion is not to have them added as text as is usual in a terminal window but to print the values of ps1 and ps2 in the proposed ShellIO subclass. That would make label customization possible in a way that is already documented and standard.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37903>
_______________________________________

From report at bugs.python.org  Thu Oct 31 12:08:45 2019
From: report at bugs.python.org (=?utf-8?q?D=C3=A1vid_Nemeskey?=)
Date: Thu, 31 Oct 2019 16:08:45 +0000
Subject: [issue36664] argparse: parser aliases in subparsers stores alias in
 dest variable
In-Reply-To: <1555630232.08.0.518571967107.issue36664@roundup.psfhosted.org>
Message-ID: <1572538125.91.0.658116976344.issue36664@roundup.psfhosted.org>


D?vid Nemeskey <nemeskeyd at gmail.com> added the comment:

I ran into the same problem. I know of the set_defaults() method, in fact, that is what I have always been using. But why was dest added if not to provide a better solution?

I agree that changing it would _perhaps_ break some code, so I agree that this issue cannot be "fixed" for Python 3.7 (and probably 3.8). But what about 3.9 or 4.0?

BTW much higher profile backward-incompatible changes do happen in Python; take PEP 563 (https://www.python.org/dev/peps/pep-0563/), for instance.

----------
nosy: +nemeskeyd

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36664>
_______________________________________

From report at bugs.python.org  Thu Oct 31 12:18:01 2019
From: report at bugs.python.org (Ronan Lamy)
Date: Thu, 31 Oct 2019 16:18:01 +0000
Subject: [issue37645] Replace PyEval_GetFuncName/PyEval_GetFuncDesc
In-Reply-To: <1563731175.2.0.136240000148.issue37645@roundup.psfhosted.org>
Message-ID: <1572538681.44.0.164659392061.issue37645@roundup.psfhosted.org>


Change by Ronan Lamy <ronan.lamy at gmail.com>:


----------
nosy: +Ronan.Lamy

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue37645>
_______________________________________

From report at bugs.python.org  Thu Oct 31 12:59:47 2019
From: report at bugs.python.org (Andriy Maletsky)
Date: Thu, 31 Oct 2019 16:59:47 +0000
Subject: [issue35182] Popen.communicate() breaks when child closes its side of
 pipe but not exits
In-Reply-To: <1541586210.62.0.788709270274.issue35182@psf.upfronthosting.co.za>
Message-ID: <1572541187.64.0.135477150936.issue35182@roundup.psfhosted.org>


Andriy Maletsky <andriy.maletsky at gmail.com> added the comment:

@josh.r but you?re correct regarding cached data that isn?t sent on subsequent communicate() calls. If the child consumes the input too slowly, and timeout occurs before sending all input, the remaining part will be lost.

Maybe it is not a bug, but it?s quite a confusing behavior, and I think it should be mentioned in the doc.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35182>
_______________________________________

From report at bugs.python.org  Thu Oct 31 13:01:01 2019
From: report at bugs.python.org (Andriy Maletsky)
Date: Thu, 31 Oct 2019 17:01:01 +0000
Subject: [issue35182] Popen.communicate() breaks when child closes its side of
 pipe but not exits
In-Reply-To: <1541586210.62.0.788709270274.issue35182@psf.upfronthosting.co.za>
Message-ID: <1572541261.52.0.949389100885.issue35182@roundup.psfhosted.org>


Change by Andriy Maletsky <andriy.maletsky at gmail.com>:


----------
keywords: +patch
pull_requests: +16538
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/17020

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35182>
_______________________________________

From report at bugs.python.org  Thu Oct 31 13:10:22 2019
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 31 Oct 2019 17:10:22 +0000
Subject: [issue38651] Add WolfSSL support
In-Reply-To: <1572467995.9.0.965883938595.issue38651@roundup.psfhosted.org>
Message-ID: <1572541822.56.0.975366808395.issue38651@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

My guess is we won't want to take code specific to WolfSSL due to maintenance overhead of trying to support another SSL library. There has been talk about trying to move away from our OpenSSL dependency and switch to using the OS's native secure sockets library which may make this easier to handle for third-parties.

But I'm personally going to leave it up to Christian to comment in case I got something wrong.

----------
nosy: +brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38651>
_______________________________________

From report at bugs.python.org  Thu Oct 31 13:14:52 2019
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 31 Oct 2019 17:14:52 +0000
Subject: [issue38649] tkinter messagebox is sloppy
In-Reply-To: <1572464225.7.0.112082789313.issue38649@roundup.psfhosted.org>
Message-ID: <1572542092.42.0.770202652778.issue38649@roundup.psfhosted.org>


Brett Cannon <brett at python.org> added the comment:

Please note that calling something "sloppy" and that somehow its development was done in some "carelessness" fashion to the point of being "egregious" is not motivating to others to try and help. Trying to support all of this code for free in one's spare time is not easy, so I would ask you try to be more understanding and nicer in your comments.

----------
nosy: +brett.cannon

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38649>
_______________________________________

From report at bugs.python.org  Thu Oct 31 15:05:11 2019
From: report at bugs.python.org (toonn)
Date: Thu, 31 Oct 2019 19:05:11 +0000
Subject: [issue38656] mimetypes for python 3.7.5 fails to detect matroska video
Message-ID: <1572548711.23.0.824957089431.issue38656@roundup.psfhosted.org>


New submission from toonn <python at toonn.io>:

A user reported an error to us which seems to derive from the ``mimetypes`` library failing to guess the mime type for ``.mkv`` matroska video files:
https://github.com/ranger/ranger/issues/1744#issuecomment-548514373

This is a regression because the same query successfully identifies the filename as being of the ``video/x-mastroska`` mime type.

----------
components: Library (Lib)
messages: 355763
nosy: toonn
priority: normal
severity: normal
status: open
title: mimetypes for python 3.7.5 fails to detect matroska video
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38656>
_______________________________________

From report at bugs.python.org  Thu Oct 31 15:28:19 2019
From: report at bugs.python.org (Jake Tesler)
Date: Thu, 31 Oct 2019 19:28:19 +0000
Subject: [issue36084] Threading: add builtin TID attribute to Thread objects
In-Reply-To: <1550875571.41.0.297490361597.issue36084@roundup.psfhosted.org>
Message-ID: <1572550099.67.0.495834366824.issue36084@roundup.psfhosted.org>


Jake Tesler <jake.tesler at gmail.com> added the comment:

I have encountered a minor bug with this new feature. The bug occurs when creating a new multiprocessing.Process object on Unix (or on any platform where the multiprocessing start_method is 'fork' or 'forkserver').

When creating a new process via fork, the Native ID in the new MainThread is incorrect. The new forked process' threading.MainThread object inherits the Native ID from the parent process' MainThread instead of capturing/updating its own (new) Native ID.

See the following snippet:

>>> import threading, multiprocessing
>>> multiprocessing.set_start_method('fork') # or 'forkserver'
>>> def proc(): print(threading.get_native_id(), threading.main_thread().native_id) # get_native_id(), mainthread.native_id
>>> proc()
22605 22605 # get_native_id(), mainthread.native_id
>>> p = multiprocessing.Process(target=proc)
>>> p.start()
22648 22605 # get_native_id(), mainthread.native_id
>>>
>>> def update(): threading.main_thread()._set_native_id()
>>> def print_and_update(): proc(); update(); proc()
>>> print_and_update()
22605 22605 # get_native_id(), mainthread.native_id
22605 22605 
>>> p2=multiprocessing.Process(target=print_and_update); p2.start()
22724 22605 # get_native_id(), mainthread.native_id
22724 22724
>>> print_and_update()
22605 22605 # get_native_id(), mainthread.native_id
22605 22605

As you can see, the new Process object's MainThread.native_id attribute matches that of the MainThread of its parent process. 

Unfortunately, I'm not too familiar with the underlying mechanisms that Multiprocessing uses to create forked processes. 
I believe this behavior occurs because (AFAIK) a forked multiprocessing.Process copies the MainThread object from its parent process, rather than reinitializing a new one. Looking further into the multiprocessing code, it appears the right spot to fix this would be in the multiprocessing.Process.bootstrap() function. 

I've created a branch containing a working fix - I'm also open to suggestions of how a fix might otherwise be implemented. 
If it looks correct I'll create a PR against the CPython 3.8 branch. 

See the branch here: https://github.com/jaketesler/cpython/tree/fix-mp-native-id

Thanks all!
-Jake

----------
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36084>
_______________________________________

From report at bugs.python.org  Thu Oct 31 16:14:45 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Thu, 31 Oct 2019 20:14:45 +0000
Subject: [issue38654] `urllib.request.Request` uses mutable value as default
 value
In-Reply-To: <1572527873.7.0.615539123104.issue38654@roundup.psfhosted.org>
Message-ID: <1572552885.58.0.968686315561.issue38654@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

I agree with Serhiy that using mutable defaults is not automatically a bad idea. This is unnecessary code churn that fixes no bugs and adds no new functionality and doesn't make the code "better".

The PR removes one harmless use of a mutable default but adds the "code smell" that assumes that None is the only possible falsey value. This means that the ``__init__`` method will accept any falsey value without complaint:

    Request(url, headers=0.0)

which is worse than the current code.

----------
nosy: +steven.daprano

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38654>
_______________________________________

From report at bugs.python.org  Thu Oct 31 16:34:16 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Thu, 31 Oct 2019 20:34:16 +0000
Subject: [issue38610] use-after-free in list object function
In-Reply-To: <1572241758.28.0.0734328499539.issue38610@roundup.psfhosted.org>
Message-ID: <1572554056.26.0.13640464116.issue38610@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


----------
keywords: +patch
pull_requests: +16539
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/17022

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38610>
_______________________________________

From report at bugs.python.org  Thu Oct 31 16:35:48 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Thu, 31 Oct 2019 20:35:48 +0000
Subject: [issue38610] use-after-free in list object function
In-Reply-To: <1572241758.28.0.0734328499539.issue38610@roundup.psfhosted.org>
Message-ID: <1572554148.4.0.296148089293.issue38610@roundup.psfhosted.org>


Zackery Spytz <zspytz at gmail.com> added the comment:

I have created a patch to fix these crashes. Please consider taking a look.

----------
nosy: +ZackerySpytz
versions: +Python 2.7, Python 3.7, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38610>
_______________________________________

From report at bugs.python.org  Thu Oct 31 16:36:00 2019
From: report at bugs.python.org (Pete Wicken)
Date: Thu, 31 Oct 2019 20:36:00 +0000
Subject: [issue38657] String format for hexadecimal notation breaks padding
 with alternative form
Message-ID: <1572554160.44.0.882070489525.issue38657@roundup.psfhosted.org>


New submission from Pete Wicken <petewicken at gmail.com>:

When formatting an integer as a hexadecimal value, the '#' alternate form modifier inserts a preceding '0x'. 
If this is used in combination with padding modifiers, the '0x' is counted as part of the overall width, which does not feel like the natural behaviour as extra calculation is required to get the correct post '0x' precision.

Example:

In [7]: f'{num:04x}'
Out[7]: '0800'

In [8]: f'{num:#04x}'
Out[8]: '0x800'

To get the hexadecimal representation padded to 4 digits, you have to account for the preceding 0x:

In [10]: f'{num:#06x}'
Out[10]: '0x0800'

----------
messages: 355767
nosy: Wicken
priority: normal
severity: normal
status: open
title: String format for hexadecimal notation breaks padding with alternative form
type: behavior
versions: Python 3.7, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38657>
_______________________________________

From report at bugs.python.org  Thu Oct 31 17:24:08 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 31 Oct 2019 21:24:08 +0000
Subject: [issue38652] Remove/update provisional note for
 asyncio.BufferedProtocol
In-Reply-To: <1572502481.2.0.695475270667.issue38652@roundup.psfhosted.org>
Message-ID: <1572557048.98.0.0636332544829.issue38652@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> I'm a newcomer, would it be ok for me to take on this propsal?

It will need approval from Yury and/or Andrew before it can be merged, but I think this is relatively uncontroversial. You can definitely work on it though.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38652>
_______________________________________

From report at bugs.python.org  Thu Oct 31 17:38:53 2019
From: report at bugs.python.org (ThePokestarFan)
Date: Thu, 31 Oct 2019 21:38:53 +0000
Subject: [issue38658] Python Program crashes when running in fore and back
 ground
Message-ID: <1572557933.17.0.948616559199.issue38658@roundup.psfhosted.org>


New submission from ThePokestarFan <sarkaraoyan at gmail.com>:

I have a Python process that should not die that is multiprocessed. I have a queue process that feeds the queue every so often, but my program should use up queue items faster than the queue adds them. I have four worker threads that make requests to an API and update an SQL table with the results. However, if I use nohup and run it, it crashes. Even if I directly run it, it crashes. It used to run forever when I loaded it in PyCharm, but even that crashes it.

----------
components: macOS
files: crash.txt
messages: 355769
nosy: ThePokestarFan, ned.deily, ronaldoussoren
priority: normal
severity: normal
status: open
title: Python Program crashes when running in fore and back ground
type: crash
versions: Python 3.8
Added file: https://bugs.python.org/file48688/crash.txt

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38658>
_______________________________________

From report at bugs.python.org  Thu Oct 31 17:42:58 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Thu, 31 Oct 2019 21:42:58 +0000
Subject: [issue38652] Remove/update provisional note for
 asyncio.BufferedProtocol
In-Reply-To: <1572502481.2.0.695475270667.issue38652@roundup.psfhosted.org>
Message-ID: <1572558178.84.0.426116459439.issue38652@roundup.psfhosted.org>


Yury Selivanov <yselivanov at gmail.com> added the comment:

Yeah, please do the change! Thanks!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38652>
_______________________________________

From report at bugs.python.org  Thu Oct 31 17:46:48 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 31 Oct 2019 21:46:48 +0000
Subject: [issue32309] Implement asyncio.run_in_executor shortcut
In-Reply-To: <1513194861.88.0.213398074469.issue32309@psf.upfronthosting.co.za>
Message-ID: <1572558408.76.0.295752768805.issue32309@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> I don't like the low-level API of run_in_executor.  "executor" being the first argument, the inability to pass **kwargs, etc.

> I mean it's great that we can use 'concurrent.futures' in asyncio, but having native asyncio pools implementation would be way more convenient to the users.

I agree that there's an issue with this, but I think for the high level API it can be an asynchronous context manager that makes use of concurrent.futures.ThreadPoolExecutor, since that one seems to fit the majority of asyncio use cases. If users want to utilize concurrent.futures.ProcessPoolExecutor or a customized one, they can use loop.run_in_executor() instead. 

Unless there's something I'm missing with regards to concurrent.futures.ThreadPoolExecutor that specifically makes it less usable. Can't asyncio.ThreadPool make use of concurrent.futures.ThreadPoolExecutor in the internal details while providing a better API?

> I'd expect to see a more high-level API, perhaps the one that supports 'async with':

> asyncio.ThreadPool() sounds great. Maybe thread group can provide better api.

I'd be willing to work on implementing the asyncio.ThreadPool API as Yury described it.

> But for Python 3.8 adding `run_in_executor` top-level function looks the only easy and obvious way to help people getting rid of explicit loop usage.

I can see your point Andrew, but I think that if we implement asyncio.run_in_executor() and then later add asyncio.ThreadPool(), it's going to be against "one obvious way" and we'll end up adding two high-level functions for the same purpose. This principle can't always be adhered to, but I think we should try to when it's possible. 

Personally, I think the API for asyncio.ThreadPool would be much more robust, so it seems worthwhile to try implementing this one first. If there are a number of unforeseen complications, asyncio.run_in_executor() might still be a decent fallback.

----------
nosy: +aeros

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32309>
_______________________________________

From report at bugs.python.org  Thu Oct 31 17:46:53 2019
From: report at bugs.python.org (ThePokestarFan)
Date: Thu, 31 Oct 2019 21:46:53 +0000
Subject: [issue38645] datetime.datetime.fromtimestamp(0,
 tzlocal()) throws error
In-Reply-To: <1572448045.56.0.183251608823.issue38645@roundup.psfhosted.org>
Message-ID: <1572558413.22.0.39365452188.issue38645@roundup.psfhosted.org>


ThePokestarFan <sarkaraoyan at gmail.com> added the comment:

For me, it seems that dateutil is not a standard Python library module. When I run `import dateutil` it reports that there is no module called dateutil.

```
>>> import dateutil
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named dateutil
```

----------
nosy: +ThePokestarFan

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38645>
_______________________________________

From report at bugs.python.org  Thu Oct 31 17:49:19 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Thu, 31 Oct 2019 21:49:19 +0000
Subject: [issue32309] Implement asyncio.run_in_executor shortcut
In-Reply-To: <1513194861.88.0.213398074469.issue32309@psf.upfronthosting.co.za>
Message-ID: <1572558559.76.0.221146637206.issue32309@roundup.psfhosted.org>


Kyle Stanley <aeros167 at gmail.com> added the comment:

> end up adding two high-level functions

Clarification: asyncio.run_in_executor() would be a function, but asyncio.ThreadPool would be a context manager class.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32309>
_______________________________________

From report at bugs.python.org  Thu Oct 31 19:10:14 2019
From: report at bugs.python.org (Efanzh)
Date: Thu, 31 Oct 2019 23:10:14 +0000
Subject: [issue38654] `urllib.request.Request` uses mutable value as default
 value
In-Reply-To: <1572527873.7.0.615539123104.issue38654@roundup.psfhosted.org>
Message-ID: <1572563414.64.0.50605698029.issue38654@roundup.psfhosted.org>


Efanzh <efanzh at gmail.com> added the comment:

How about changing `if headers` to `if headers is not None`?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38654>
_______________________________________

From report at bugs.python.org  Thu Oct 31 19:11:32 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 31 Oct 2019 23:11:32 +0000
Subject: [issue38654] `urllib.request.Request` uses mutable value as default
 value
In-Reply-To: <1572527873.7.0.615539123104.issue38654@roundup.psfhosted.org>
Message-ID: <1572563492.43.0.0861233536498.issue38654@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

It is not needed. There is no bug. Nothing to change.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38654>
_______________________________________

From report at bugs.python.org  Thu Oct 31 19:40:22 2019
From: report at bugs.python.org (Andriy Maletsky)
Date: Thu, 31 Oct 2019 23:40:22 +0000
Subject: [issue35182] Popen.communicate() breaks when child closes its side of
 pipe but not exits
In-Reply-To: <1541586210.62.0.788709270274.issue35182@psf.upfronthosting.co.za>
Message-ID: <1572565222.65.0.954808522242.issue35182@roundup.psfhosted.org>


Change by Andriy Maletsky <andriy.maletsky at gmail.com>:


----------
pull_requests: +16540
pull_request: https://github.com/python/cpython/pull/17023

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35182>
_______________________________________

From report at bugs.python.org  Thu Oct 31 19:52:30 2019
From: report at bugs.python.org (tholl)
Date: Thu, 31 Oct 2019 23:52:30 +0000
Subject: [issue38622] _ctypes.dlsym (py_dl_sym) does not trigger audit hooks
In-Reply-To: <1572286737.48.0.245277798688.issue38622@roundup.psfhosted.org>
Message-ID: <1572565950.26.0.141543321507.issue38622@roundup.psfhosted.org>


tholl <py at any.tholl.xyz> added the comment:

I probably should have done this earlier, but here's a small test case that reproduces the issue. The assert fails in vanilla Python 3.8, but passes with the patch.

----------
type:  -> behavior
Added file: https://bugs.python.org/file48689/audit-test.py

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38622>
_______________________________________

From report at bugs.python.org  Thu Oct 31 21:12:48 2019
From: report at bugs.python.org (Gregory P. Smith)
Date: Fri, 01 Nov 2019 01:12:48 +0000
Subject: [issue38659] enum classes cause slow startup time
Message-ID: <1572570768.69.0.355804772721.issue38659@roundup.psfhosted.org>


New submission from Gregory P. Smith <greg at krypto.org>:

Creating an enum subclass (ie: defining an enum) is slow.  This dramatically impacts startup time of Python programs that import a bunch of potentially needed constant definitions at startup before any proper code executes.

How slow?  So slow that a module defining a ~300 enums takes nearly 100ms just to import from its pyc file.

Example code: https://github.com/googleads/google-ads-python/blob/96fd08bb62435f1930df4871033ba8689333b67f/google/ads/google_ads/v2/services/enums.py

We've known this, we should do something about it.  (Even if it means implementing the guts of the magic enum machinery in C.)  ie, it came up in https://bugs.python.org/issue28637 as a stdlib startup time regression and is likely to come up in similar contexts elsewhere.

----------
components: Library (Lib)
messages: 355777
nosy: gregory.p.smith
priority: normal
severity: normal
stage: needs patch
status: open
title: enum classes cause slow startup time
type: performance
versions: Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38659>
_______________________________________

From report at bugs.python.org  Thu Oct 31 21:46:44 2019
From: report at bugs.python.org (Efanzh)
Date: Fri, 01 Nov 2019 01:46:44 +0000
Subject: [issue38654] `urllib.request.Request` uses mutable value as default
 value
In-Reply-To: <1572527873.7.0.615539123104.issue38654@roundup.psfhosted.org>
Message-ID: <1572572804.38.0.904283083718.issue38654@roundup.psfhosted.org>


Efanzh <efanzh at gmail.com> added the comment:

I agree that this doesn?t fix any bug. But is is easy to make mistakes by using mutable default values (See https://docs.python-guide.org/writing/gotchas/#mutable-default-arguments). Both PyCharm and pylint show warnings about mutable default arguments even there is no bug in the code.

Using `{}` as default value, by looking at the function signature, I might wonder whether this argument stays the same on each function call, since it is mutable. But by using `None` as default value, I am know this argument will always be `None` on each function call. Using `None` as default value makes the function interface more easy to understand.

Also, if some new Python coders saw `[]` or `{}` being used as default values in the standard library, they might think ?I?ll do it too since the standard library does it?.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38654>
_______________________________________

From report at bugs.python.org  Thu Oct 31 21:51:18 2019
From: report at bugs.python.org (paul j3)
Date: Fri, 01 Nov 2019 01:51:18 +0000
Subject: [issue36664] argparse: parser aliases in subparsers stores alias in
 dest variable
In-Reply-To: <1555630232.08.0.518571967107.issue36664@roundup.psfhosted.org>
Message-ID: <1572573078.16.0.192410872328.issue36664@roundup.psfhosted.org>


paul j3 <ajipanca at gmail.com> added the comment:

Just clarify how the code currently works.  `subparsers` is a positional Action of subclass _SubParsersAction.  It has a nargs='+...', requiring at least one string, and taking all remaining strings.  Its __call__ has the standard signature.  So everything that's special about subparsers is embodied in this Action subclass.  

    def __call__(self, parser, namespace, values, option_string=None):
        parser_name = values[0]
        arg_strings = values[1:]

        # set the parser name if requested
        if self.dest is not SUPPRESS:
            setattr(namespace, self.dest, parser_name)

        # select the parser
        try:
            parser = self._name_parser_map[parser_name]
        ...

So the `parser_name` is first string, the actual alias that user provided.  It is added to the namespace if a `dest` was provided (the default `dest` is SUPPRESS).  That's all of the relevant code - the alias is simply added to to Namespace.

As mentioned before `parser_name` is used find the actual sub parser, which is called with the remaining `arg_strings`.

Earlier in the subclasses `add_parser` method, the 'name' and 'alias' list are used to populate the '_name_parser_map' mapping, and also create the metavar that's used in the help display.  But neither is saved as an attribute.

---

I still think 'set_defaults' is the cleanest way of saving a unique name for a sub parser.

    parser_foo.set_defaults(func=foo, name='foo')

---

One further note - if you make subparsers required, you should also set a dest name:

    parser.add_subparsers(dest='cmd', required=True)

otherwise the missing-subparsers error message will raise an error.  It needs to identify the missing action in some way.  Functionally, this might be the most important reason to set the 'dest'.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue36664>
_______________________________________

From report at bugs.python.org  Thu Oct 31 21:56:14 2019
From: report at bugs.python.org (Dong-hee Na)
Date: Fri, 01 Nov 2019 01:56:14 +0000
Subject: [issue38645] datetime.datetime.fromtimestamp(0,
 tzlocal()) throws error
In-Reply-To: <1572448045.56.0.183251608823.issue38645@roundup.psfhosted.org>
Message-ID: <1572573374.76.0.693902177941.issue38645@roundup.psfhosted.org>


Dong-hee Na <donghee.na92 at gmail.com> added the comment:

Python 3.9.0a0 (heads/master:112f2b805b, Nov  1 2019, 10:48:20)
[GCC 7.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import datetime
>>> utc_tzinfo = datetime.timezone.utc
>>> print(datetime.datetime.fromtimestamp(0, utc_tzinfo))
1970-01-01 00:00:00+00:00

works properly on my Linux machine.
Can you gave me which can reproduce based on stdlib library?

----------
nosy: +corona10

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38645>
_______________________________________

From report at bugs.python.org  Thu Oct 31 21:58:49 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 01 Nov 2019 01:58:49 +0000
Subject: [issue38659] enum classes cause slow startup time
In-Reply-To: <1572570768.69.0.355804772721.issue38659@roundup.psfhosted.org>
Message-ID: <1572573529.77.0.413564742401.issue38659@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +ethan.furman

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38659>
_______________________________________

From report at bugs.python.org  Thu Oct 31 22:18:13 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 01 Nov 2019 02:18:13 +0000
Subject: [issue38656] mimetypes for python 3.7.5 fails to detect matroska video
In-Reply-To: <1572548711.23.0.824957089431.issue38656@roundup.psfhosted.org>
Message-ID: <1572574693.0.0.686322508061.issue38656@roundup.psfhosted.org>


Change by Karthikeyan Singaravelan <tir.karthi at gmail.com>:


----------
nosy: +xtreak

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38656>
_______________________________________

From report at bugs.python.org  Thu Oct 31 22:23:32 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 01 Nov 2019 02:23:32 +0000
Subject: [issue38656] mimetypes for python 3.7.5 fails to detect matroska video
In-Reply-To: <1572548711.23.0.824957089431.issue38656@roundup.psfhosted.org>
Message-ID: <1572575012.88.0.352757397381.issue38656@roundup.psfhosted.org>


Karthikeyan Singaravelan <tir.karthi at gmail.com> added the comment:

I couldn't find mkv in mimetypes with search. Can you please post the output of the mimetypes query in 3.7.4 and 3.7.5 for the regression? In the attached GitHub issue the user reports mkv returns None and mp4 is detected.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38656>
_______________________________________

From report at bugs.python.org  Thu Oct 31 22:38:42 2019
From: report at bugs.python.org (Ammar Askar)
Date: Fri, 01 Nov 2019 02:38:42 +0000
Subject: [issue38656] mimetypes for python 3.7.5 fails to detect matroska video
In-Reply-To: <1572548711.23.0.824957089431.issue38656@roundup.psfhosted.org>
Message-ID: <1572575922.25.0.26979538525.issue38656@roundup.psfhosted.org>


Ammar Askar <ammar at ammaraskar.com> added the comment:

This is what I get on master, will try 3.7.5+ as noted in the Github issue:


Python 3.9.0a0 (heads/noopt-dirty:f3b170812d, Oct  1 2019, 20:15:53) [MSC v.1916 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import mimetypes
>>> print(mimetypes.guess_type('E01.mkv'))
('video/x-matroska', None)

----------
nosy: +ammar2

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38656>
_______________________________________

From report at bugs.python.org  Thu Oct 31 22:53:46 2019
From: report at bugs.python.org (Michael Zhang)
Date: Fri, 01 Nov 2019 02:53:46 +0000
Subject: [issue38645] datetime.datetime.fromtimestamp(0,
 tzlocal()) throws error
In-Reply-To: <1572448045.56.0.183251608823.issue38645@roundup.psfhosted.org>
Message-ID: <1572576826.25.0.119222578354.issue38645@roundup.psfhosted.org>


Michael Zhang <mzhangthirteen at gmail.com> added the comment:

I think it might be something Windows specific; the original comment includes the version and code to reproduce.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38645>
_______________________________________

From report at bugs.python.org  Thu Oct 31 22:59:08 2019
From: report at bugs.python.org (ThePokestarFan)
Date: Fri, 01 Nov 2019 02:59:08 +0000
Subject: [issue38645] datetime.datetime.fromtimestamp(0,
 tzlocal()) throws error
In-Reply-To: <1572448045.56.0.183251608823.issue38645@roundup.psfhosted.org>
Message-ID: <1572577148.19.0.343869300653.issue38645@roundup.psfhosted.org>


ThePokestarFan <sarkaraoyan at gmail.com> added the comment:

Can you run

>>>import dateutil
>>>print(repr(dateutil))

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38645>
_______________________________________

From report at bugs.python.org  Thu Oct 31 23:00:30 2019
From: report at bugs.python.org (Ammar Askar)
Date: Fri, 01 Nov 2019 03:00:30 +0000
Subject: [issue38645] datetime.datetime.fromtimestamp(0,
 tzlocal()) throws error
In-Reply-To: <1572448045.56.0.183251608823.issue38645@roundup.psfhosted.org>
Message-ID: <1572577230.6.0.907220632477.issue38645@roundup.psfhosted.org>


Ammar Askar <ammar at ammaraskar.com> added the comment:

It is windows specific, but I don't think this is a dateutil bug rather than the python stdlib:

Python 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 16:07:46) [MSC v.1900 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import datetime
>>> from dateutil.tz import tzlocal
>>> print(datetime.datetime.fromtimestamp(0, tzlocal()))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "D:\Python365\lib\site-packages\dateutil\tz\_common.py", line 144, in fromutc
    return f(self, dt)
  File "D:\Python365\lib\site-packages\dateutil\tz\_common.py", line 258, in fromutc
    dt_wall = self._fromutc(dt)
  File "D:\Python365\lib\site-packages\dateutil\tz\_common.py", line 238, in _fromutc
    dtdst = enfold(dt, fold=1).dst()
  File "D:\Python365\lib\site-packages\dateutil\tz\tz.py", line 225, in dst
    if self._isdst(dt):
  File "D:\Python365\lib\site-packages\dateutil\tz\tz.py", line 288, in _isdst
    if self.is_ambiguous(dt):
  File "D:\Python365\lib\site-packages\dateutil\tz\tz.py", line 250, in is_ambiguous
    (naive_dst != self._naive_is_dst(dt - self._dst_saved)))
  File "D:\Python365\lib\site-packages\dateutil\tz\tz.py", line 254, in _naive_is_dst
    return time.localtime(timestamp + time.timezone).tm_isdst
OSError: [Errno 22] Invalid argument


As you can see, none of that backtrace is within Python, it's all inside dateutil code. More than likely they are calling `time.localtime` with a value of less than 0 which throws an error on Windows. (see also issue29097)

----------
nosy: +ammar2

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38645>
_______________________________________

From report at bugs.python.org  Thu Oct 31 23:01:19 2019
From: report at bugs.python.org (Ammar Askar)
Date: Fri, 01 Nov 2019 03:01:19 +0000
Subject: [issue38645] datetime.datetime.fromtimestamp(0,
 tzlocal()) throws error
In-Reply-To: <1572448045.56.0.183251608823.issue38645@roundup.psfhosted.org>
Message-ID: <1572577279.68.0.552156453627.issue38645@roundup.psfhosted.org>


Ammar Askar <ammar at ammaraskar.com> added the comment:

Err...I mean I think this is a dateutil bug rather than in the Python stdlib.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38645>
_______________________________________

From report at bugs.python.org  Thu Oct 31 23:03:01 2019
From: report at bugs.python.org (Michael Zhang)
Date: Fri, 01 Nov 2019 03:03:01 +0000
Subject: [issue38645] datetime.datetime.fromtimestamp(0,
 tzlocal()) throws error
In-Reply-To: <1572448045.56.0.183251608823.issue38645@roundup.psfhosted.org>
Message-ID: <1572577381.91.0.825454302944.issue38645@roundup.psfhosted.org>


Michael Zhang <mzhangthirteen at gmail.com> added the comment:

Yeah, seconded with my own tracing as well.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38645>
_______________________________________

From report at bugs.python.org  Thu Oct 31 23:11:09 2019
From: report at bugs.python.org (Ammar Askar)
Date: Fri, 01 Nov 2019 03:11:09 +0000
Subject: [issue38645] datetime.datetime.fromtimestamp(0,
 tzlocal()) throws error
In-Reply-To: <1572448045.56.0.183251608823.issue38645@roundup.psfhosted.org>
Message-ID: <1572577869.22.0.202247674061.issue38645@roundup.psfhosted.org>


Ammar Askar <ammar at ammaraskar.com> added the comment:

Closing, here's the bug in dateutil's repo: https://github.com/dateutil/dateutil/issues/197

----------
resolution:  -> third party
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38645>
_______________________________________

From report at bugs.python.org  Thu Oct 31 23:31:39 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 01 Nov 2019 03:31:39 +0000
Subject: [issue38642] python3.7.3 seems to cause add-apt-repository to rejct
 or not find gi library
In-Reply-To: <1572444360.24.0.26930433052.issue38642@roundup.psfhosted.org>
Message-ID: <1572579099.38.0.0986406250797.issue38642@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


----------
nosy: +doko -Marco Ippolito

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38642>
_______________________________________