From report at bugs.python.org  Tue Jan  1 02:35:47 2019
From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=)
Date: Tue, 01 Jan 2019 07:35:47 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
Message-ID: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>


New submission from Ville Skytt? <ville.skytta at iki.fi>:

The typing docs for List includes a note to use generic collection types, but lists AbstractSet and Mapping which aren't generally replacements for a List. It would be better to remove those types from the List note and add corresponding ones to Dict and Set which are currently lacking it.

Additionally, some examples in the typing docs are in violation of the above stated preference, using Lists and Dicts as parameters.

----------
assignee: docs at python
components: Documentation
messages: 332842
nosy: docs at python, scop
priority: normal
severity: normal
status: open
title: Improve typing docs wrt abstract/concrete collection types
type: enhancement

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

From report at bugs.python.org  Tue Jan  1 02:37:39 2019
From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=)
Date: Tue, 01 Jan 2019 07:37:39 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546328259.85.0.592903963466.issue35631@roundup.psfhosted.org>


Change by Ville Skytt? <ville.skytta at iki.fi>:


----------
keywords: +patch
pull_requests: +10774
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan  1 02:37:44 2019
From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=)
Date: Tue, 01 Jan 2019 07:37:44 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546328264.79.0.555625214136.issue35631@roundup.psfhosted.org>


Change by Ville Skytt? <ville.skytta at iki.fi>:


----------
keywords: +patch, patch
pull_requests: +10774, 10775
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan  1 02:37:49 2019
From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=)
Date: Tue, 01 Jan 2019 07:37:49 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546328269.92.0.483803214564.issue35631@roundup.psfhosted.org>


Change by Ville Skytt? <ville.skytta at iki.fi>:


----------
keywords: +patch, patch, patch
pull_requests: +10774, 10775, 10776
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan  1 02:58:03 2019
From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=)
Date: Tue, 01 Jan 2019 07:58:03 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546329482.43.0.676426916.issue35631@roundup.psfhosted.org>


Ville Skytt? <ville.skytta at iki.fi> added the comment:

(s/generic collection types/abstract collection types/ in the initial message)

----------

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

From report at bugs.python.org  Tue Jan  1 20:57:49 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Wed, 02 Jan 2019 01:57:49 +0000
Subject: [docs] [issue35630] Missing code tag for "python3" in README.rst
In-Reply-To: <1546289591.73.0.0479486789763.issue35630@roundup.psfhosted.org>
Message-ID: <1546394266.71.0.601260250807.issue35630@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset 7e3fb40b923cb09ecc67816d3191197868593737 by Benjamin Peterson (Suriyaa ???) in branch 'master':
closes bpo-35630: Use code tag for 'python3' in 'README.rst' (GH-11394)
https://github.com/python/cpython/commit/7e3fb40b923cb09ecc67816d3191197868593737


----------
nosy: +benjamin.peterson
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Jan  1 20:58:17 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 01:58:17 +0000
Subject: [docs] [issue35630] Missing code tag for "python3" in README.rst
In-Reply-To: <1546289591.73.0.0479486789763.issue35630@roundup.psfhosted.org>
Message-ID: <1546394296.1.0.0552196251161.issue35630@roundup.psfhosted.org>


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


----------
pull_requests: +10777

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

From report at bugs.python.org  Tue Jan  1 20:58:21 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 01:58:21 +0000
Subject: [docs] [issue35630] Missing code tag for "python3" in README.rst
In-Reply-To: <1546289591.73.0.0479486789763.issue35630@roundup.psfhosted.org>
Message-ID: <1546394300.29.0.301234113697.issue35630@roundup.psfhosted.org>


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


----------
pull_requests: +10777, 10778

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

From report at bugs.python.org  Tue Jan  1 20:58:25 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 01:58:25 +0000
Subject: [docs] [issue35630] Missing code tag for "python3" in README.rst
In-Reply-To: <1546289591.73.0.0479486789763.issue35630@roundup.psfhosted.org>
Message-ID: <1546394304.46.0.391166839173.issue35630@roundup.psfhosted.org>


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


----------
pull_requests: +10778, 10779

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

From report at bugs.python.org  Tue Jan  1 20:58:29 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 01:58:29 +0000
Subject: [docs] [issue35630] Missing code tag for "python3" in README.rst
In-Reply-To: <1546289591.73.0.0479486789763.issue35630@roundup.psfhosted.org>
Message-ID: <1546394308.69.0.00233409348289.issue35630@roundup.psfhosted.org>


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


----------
pull_requests: +10779, 10780

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

From report at bugs.python.org  Tue Jan  1 20:58:33 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 01:58:33 +0000
Subject: [docs] [issue35630] Missing code tag for "python3" in README.rst
In-Reply-To: <1546289591.73.0.0479486789763.issue35630@roundup.psfhosted.org>
Message-ID: <1546394312.78.0.337375115528.issue35630@roundup.psfhosted.org>


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


----------
pull_requests: +10779, 10780, 10781

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

From report at bugs.python.org  Tue Jan  1 21:03:59 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 02:03:59 +0000
Subject: [docs] [issue35630] Missing code tag for "python3" in README.rst
In-Reply-To: <1546289591.73.0.0479486789763.issue35630@roundup.psfhosted.org>
Message-ID: <1546394637.18.0.06042759702.issue35630@roundup.psfhosted.org>


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


New changeset 513fab2c67365e1693216dd59e4df0a5f6bfeb26 by Miss Islington (bot) in branch '3.7':
closes bpo-35630: Use code tag for 'python3' in 'README.rst' (GH-11394)
https://github.com/python/cpython/commit/513fab2c67365e1693216dd59e4df0a5f6bfeb26


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

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

From report at bugs.python.org  Tue Jan  1 21:04:30 2019
From: report at bugs.python.org (Benjamin Peterson)
Date: Wed, 02 Jan 2019 02:04:30 +0000
Subject: [docs] [issue35630] Missing code tag for "python3" in README.rst
In-Reply-To: <1546289591.73.0.0479486789763.issue35630@roundup.psfhosted.org>
Message-ID: <1546394667.77.0.575410208678.issue35630@roundup.psfhosted.org>


Benjamin Peterson <benjamin at python.org> added the comment:


New changeset de66b8d498e47ed9d70607ac9b9f72468241da77 by Benjamin Peterson (Miss Islington (bot)) in branch '3.6':
closes bpo-35630: Use code tag for 'python3' in 'README.rst' (GH-11400)
https://github.com/python/cpython/commit/de66b8d498e47ed9d70607ac9b9f72468241da77


----------

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

From report at bugs.python.org  Wed Jan  2 07:52:05 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 02 Jan 2019 12:52:05 +0000
Subject: [docs] [issue35603] table header in output of
 difflib.HtmlDiff.make_table is not escaped and can be rendered as code in
 the browser
In-Reply-To: <1545988680.87.0.068090288545.issue35603@roundup.psfhosted.org>
Message-ID: <1546433525.86.0.932696195449.issue35603@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
versions: +Python 2.7 -Python 3.5, Python 3.6

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

From report at bugs.python.org  Wed Jan  2 09:01:10 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 02 Jan 2019 14:01:10 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546437670.0.0.70769539442.issue35631@roundup.psfhosted.org>


Change by Ivan Levkivskyi <levkivskyi at gmail.com>:


----------
nosy: +levkivskyi

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

From report at bugs.python.org  Wed Jan  2 11:47:05 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Wed, 02 Jan 2019 16:47:05 +0000
Subject: [docs] [issue35609] Improve of abc.py docstring
In-Reply-To: <1546052751.93.0.333388893142.issue35609@roundup.psfhosted.org>
Message-ID: <1546447624.54.0.978597804864.issue35609@roundup.psfhosted.org>


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

Hi Serhiy, 

A little question. Is there a planned version to remove the deprecated?

----------

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

From report at bugs.python.org  Wed Jan  2 14:31:10 2019
From: report at bugs.python.org (Yash Aggarwal)
Date: Wed, 02 Jan 2019 19:31:10 +0000
Subject: [docs] [issue35434] Wrong bpo linked in What's New in 3.8
In-Reply-To: <1544157988.47.0.788709270274.issue35434@psf.upfronthosting.co.za>
Message-ID: <1546457470.03.0.404321830517.issue35434@roundup.psfhosted.org>


Change by Yash Aggarwal <aggarwal.yash2011 at gmail.com>:


----------
pull_requests: +10809

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

From report at bugs.python.org  Wed Jan  2 14:31:19 2019
From: report at bugs.python.org (Yash Aggarwal)
Date: Wed, 02 Jan 2019 19:31:19 +0000
Subject: [docs] [issue35434] Wrong bpo linked in What's New in 3.8
In-Reply-To: <1544157988.47.0.788709270274.issue35434@psf.upfronthosting.co.za>
Message-ID: <1546457479.76.0.430336936946.issue35434@roundup.psfhosted.org>


Change by Yash Aggarwal <aggarwal.yash2011 at gmail.com>:


----------
pull_requests: +10809, 10810

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

From report at bugs.python.org  Wed Jan  2 14:31:28 2019
From: report at bugs.python.org (Yash Aggarwal)
Date: Wed, 02 Jan 2019 19:31:28 +0000
Subject: [docs] [issue35434] Wrong bpo linked in What's New in 3.8
In-Reply-To: <1544157988.47.0.788709270274.issue35434@psf.upfronthosting.co.za>
Message-ID: <1546457488.84.0.412432290058.issue35434@roundup.psfhosted.org>


Change by Yash Aggarwal <aggarwal.yash2011 at gmail.com>:


----------
pull_requests: +10809, 10810, 10811

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

From report at bugs.python.org  Wed Jan  2 15:53:25 2019
From: report at bugs.python.org (Tal Einat)
Date: Wed, 02 Jan 2019 20:53:25 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546462404.26.0.628300114916.issue35525@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests:  -10554

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

From report at bugs.python.org  Wed Jan  2 15:53:30 2019
From: report at bugs.python.org (Tal Einat)
Date: Wed, 02 Jan 2019 20:53:30 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546462408.48.0.97219663569.issue35525@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests:  -10554, 10555

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

From report at bugs.python.org  Wed Jan  2 16:05:29 2019
From: report at bugs.python.org (Tal Einat)
Date: Wed, 02 Jan 2019 21:05:29 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463127.55.0.774496670225.issue35525@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset e9a044ec16989bd4b39763c0588c17200a925350 by Tal Einat (Harmandeep Singh) in branch 'master':
bpo-35525: Correct the argument name for NNTP.starttls() (GH-11310)
https://github.com/python/cpython/commit/e9a044ec16989bd4b39763c0588c17200a925350


----------
nosy: +taleinat

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

From report at bugs.python.org  Wed Jan  2 16:05:46 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 21:05:46 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463145.49.0.742730189467.issue35525@roundup.psfhosted.org>


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


----------
pull_requests: +10817

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

From report at bugs.python.org  Wed Jan  2 16:05:51 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 21:05:51 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463150.59.0.215653870873.issue35525@roundup.psfhosted.org>


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


----------
pull_requests: +10817, 10818

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

From report at bugs.python.org  Wed Jan  2 16:05:55 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 21:05:55 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463154.68.0.0837009296085.issue35525@roundup.psfhosted.org>


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


----------
pull_requests: +10818, 10820

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

From report at bugs.python.org  Wed Jan  2 16:06:00 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 21:06:00 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463159.74.0.973833222208.issue35525@roundup.psfhosted.org>


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


----------
pull_requests: +10817, 10818, 10819, 10820

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

From report at bugs.python.org  Wed Jan  2 16:06:07 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 21:06:07 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463165.63.0.811436816058.issue35525@roundup.psfhosted.org>


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


----------
pull_requests: +10819, 10820, 10822

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

From report at bugs.python.org  Wed Jan  2 16:06:14 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 21:06:14 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463172.58.0.764985228108.issue35525@roundup.psfhosted.org>


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


----------
pull_requests: +10819, 10820, 10821, 10822

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

From report at bugs.python.org  Wed Jan  2 16:09:25 2019
From: report at bugs.python.org (Tal Einat)
Date: Wed, 02 Jan 2019 21:09:25 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463363.73.0.755252322474.issue35525@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests:  -10818

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

From report at bugs.python.org  Wed Jan  2 16:09:29 2019
From: report at bugs.python.org (Tal Einat)
Date: Wed, 02 Jan 2019 21:09:29 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463368.74.0.210071735225.issue35525@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests:  -10818, 10819

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

From report at bugs.python.org  Wed Jan  2 16:09:35 2019
From: report at bugs.python.org (Tal Einat)
Date: Wed, 02 Jan 2019 21:09:35 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463373.95.0.128203594687.issue35525@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests:  -10818, 10819, 10822

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

From report at bugs.python.org  Wed Jan  2 16:09:39 2019
From: report at bugs.python.org (Tal Einat)
Date: Wed, 02 Jan 2019 21:09:39 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463378.33.0.994336396857.issue35525@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests:  -10818, 10819, 10821, 10822

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

From report at bugs.python.org  Wed Jan  2 16:11:06 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 02 Jan 2019 21:11:06 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1546463462.68.0.10962674341.issue35525@roundup.psfhosted.org>


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


New changeset d7cb2034bbaa26170cdc66eb54626e3ce1b8678a by Miss Islington (bot) in branch '3.7':
bpo-35525: Correct the argument name for NNTP.starttls() (GH-11310)
https://github.com/python/cpython/commit/d7cb2034bbaa26170cdc66eb54626e3ce1b8678a


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

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

From report at bugs.python.org  Wed Jan  2 22:28:25 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 03 Jan 2019 03:28:25 +0000
Subject: [docs] [issue35609] Improve of abc.py docstring
In-Reply-To: <1546052751.93.0.333388893142.issue35609@roundup.psfhosted.org>
Message-ID: <1546486104.45.0.94303416306.issue35609@roundup.psfhosted.org>


INADA Naoki <songofacandy at gmail.com> added the comment:

No plan for removal.  See https://bugs.python.org/issue28886#msg282582

----------
nosy: +inada.naoki

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

From report at bugs.python.org  Thu Jan  3 04:06:16 2019
From: report at bugs.python.org (flokX)
Date: Thu, 03 Jan 2019 09:06:16 +0000
Subject: [docs] [issue35648] Add use_srcentry parameter to shutil.copytree()
Message-ID: <1546506372.52.0.724433917377.issue35648@roundup.psfhosted.org>


New submission from flokX <accounts at fkcore.de>:

Currently it is decided if to use the srcentry in the copy_function by checking if the copy_function is copy() or copy2(). This will fail if the copy_function is a modified copy() or copy2() function. To control if the copy_function gets a srcentry or srcname parameter, added the use_srcentry parameter.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 332923
nosy: docs at python, flokX
priority: normal
severity: normal
status: open
title: Add use_srcentry parameter to shutil.copytree()
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Thu Jan  3 04:07:44 2019
From: report at bugs.python.org (flokX)
Date: Thu, 03 Jan 2019 09:07:44 +0000
Subject: [docs] [issue35648] Add use_srcentry parameter to shutil.copytree()
In-Reply-To: <1546506372.52.0.724433917377.issue35648@roundup.psfhosted.org>
Message-ID: <1546506463.68.0.0254570991397.issue35648@roundup.psfhosted.org>


Change by flokX <accounts at fkcore.de>:


----------
keywords: +patch
pull_requests: +10832
stage:  -> patch review

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

From report at bugs.python.org  Thu Jan  3 04:07:50 2019
From: report at bugs.python.org (flokX)
Date: Thu, 03 Jan 2019 09:07:50 +0000
Subject: [docs] [issue35648] Add use_srcentry parameter to shutil.copytree()
In-Reply-To: <1546506372.52.0.724433917377.issue35648@roundup.psfhosted.org>
Message-ID: <1546506468.83.0.188611283717.issue35648@roundup.psfhosted.org>


Change by flokX <accounts at fkcore.de>:


----------
keywords: +patch, patch
pull_requests: +10832, 10833
stage:  -> patch review

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

From report at bugs.python.org  Thu Jan  3 04:07:56 2019
From: report at bugs.python.org (flokX)
Date: Thu, 03 Jan 2019 09:07:56 +0000
Subject: [docs] [issue35648] Add use_srcentry parameter to shutil.copytree()
In-Reply-To: <1546506372.52.0.724433917377.issue35648@roundup.psfhosted.org>
Message-ID: <1546506474.57.0.577099637201.issue35648@roundup.psfhosted.org>


Change by flokX <accounts at fkcore.de>:


----------
keywords: +patch, patch, patch
pull_requests: +10832, 10833, 10835
stage:  -> patch review

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

From report at bugs.python.org  Thu Jan  3 04:08:02 2019
From: report at bugs.python.org (flokX)
Date: Thu, 03 Jan 2019 09:08:02 +0000
Subject: [docs] [issue35648] Add use_srcentry parameter to shutil.copytree()
In-Reply-To: <1546506372.52.0.724433917377.issue35648@roundup.psfhosted.org>
Message-ID: <1546506480.17.0.766306219178.issue35648@roundup.psfhosted.org>


Change by flokX <accounts at fkcore.de>:


----------
keywords: +patch, patch, patch, patch
pull_requests: +10832, 10833, 10834, 10835
stage:  -> patch review

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

From report at bugs.python.org  Thu Jan  3 05:51:23 2019
From: report at bugs.python.org (Yash Aggarwal)
Date: Thu, 03 Jan 2019 10:51:23 +0000
Subject: [docs] [issue35434] Wrong bpo linked in What's New in 3.8
In-Reply-To: <1544157988.47.0.788709270274.issue35434@psf.upfronthosting.co.za>
Message-ID: <1546512683.31.0.412648838719.issue35434@roundup.psfhosted.org>


Change by Yash Aggarwal <aggarwal.yash2011 at gmail.com>:


----------
pull_requests:  -10809

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

From report at bugs.python.org  Thu Jan  3 05:51:39 2019
From: report at bugs.python.org (Yash Aggarwal)
Date: Thu, 03 Jan 2019 10:51:39 +0000
Subject: [docs] [issue35434] Wrong bpo linked in What's New in 3.8
In-Reply-To: <1544157988.47.0.788709270274.issue35434@psf.upfronthosting.co.za>
Message-ID: <1546512699.15.0.648954208204.issue35434@roundup.psfhosted.org>


Change by Yash Aggarwal <aggarwal.yash2011 at gmail.com>:


----------
pull_requests:  -10810

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

From report at bugs.python.org  Thu Jan  3 05:51:58 2019
From: report at bugs.python.org (Yash Aggarwal)
Date: Thu, 03 Jan 2019 10:51:58 +0000
Subject: [docs] [issue35434] Wrong bpo linked in What's New in 3.8
In-Reply-To: <1544157988.47.0.788709270274.issue35434@psf.upfronthosting.co.za>
Message-ID: <1546512718.6.0.774588925243.issue35434@roundup.psfhosted.org>


Change by Yash Aggarwal <aggarwal.yash2011 at gmail.com>:


----------
pull_requests:  -10811

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

From report at bugs.python.org  Thu Jan  3 12:34:29 2019
From: report at bugs.python.org (Mark Amery)
Date: Thu, 03 Jan 2019 17:34:29 +0000
Subject: [docs] [issue35651] PEP 257 (active) references PEP 258 (rejected)
 as if it were active
Message-ID: <1546536866.6.0.633154963858.issue35651@roundup.psfhosted.org>


New submission from Mark Amery <markamery at btinternet.com>:

PEP 257 says:

> Please see PEP 258, "Docutils Design Specification" [2], for a detailed description of attribute and additional docstrings.

But PEP 258 is rejected. It doesn't seem coherent that an active PEP can defer some of its details to a rejected PEP - and indeed it makes me unsure how much of the surrounding commentary in PEP 257 to treat as active. e.g. should I treat the entire concepts of "attribute docstrings" and "additional docstrings" as rejected, given the rejection of PEP 258, or are they still part of the current spec, given that they're referenced in PEP 257 prior to any mention of PEP 258? It's currently completely unclear.

----------
assignee: docs at python
components: Documentation
messages: 332940
nosy: ExplodingCabbage, docs at python
priority: normal
severity: normal
status: open
title: PEP 257 (active) references PEP 258 (rejected) as if it were active
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Jan  3 12:45:40 2019
From: report at bugs.python.org (Barry A. Warsaw)
Date: Thu, 03 Jan 2019 17:45:40 +0000
Subject: [docs] [issue35651] PEP 257 (active) references PEP 258 (rejected)
 as if it were active
In-Reply-To: <1546536866.6.0.633154963858.issue35651@roundup.psfhosted.org>
Message-ID: <1546537539.46.0.367662487421.issue35651@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/issue35651>
_______________________________________

From report at bugs.python.org  Thu Jan  3 14:50:50 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Thu, 03 Jan 2019 19:50:50 +0000
Subject: [docs] [issue35605] backported patch requires new sphinx,
 minimum sphinx version was not bumped
In-Reply-To: <1546016436.32.0.942702382011.issue35605@roundup.psfhosted.org>
Message-ID: <1546545048.43.0.211914451855.issue35605@roundup.psfhosted.org>


Anthony Sottile <asottile at umich.edu> added the comment:

I also had to update the patch for sphinx.util.status_iterator which was also introduced in sphinx 1.6

----------

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

From report at bugs.python.org  Thu Jan  3 15:21:42 2019
From: report at bugs.python.org (Martin Panter)
Date: Thu, 03 Jan 2019 20:21:42 +0000
Subject: [docs] [issue35649] http.client doesn't close.  Infinite loop
In-Reply-To: <1546533708.33.0.81545579375.issue35649@roundup.psfhosted.org>
Message-ID: <1546546901.23.0.686832241357.issue35649@roundup.psfhosted.org>


Martin Panter <vadmium+py at gmail.com> added the comment:

This was changed in Python 3.2+ in Issue 16723. The response object no longer sets the ?closed? attribute when it runs out of data; it is only set when the ?close? method is called. Perhaps the example should be amended so that it checks if ?read? returned an empty string, rather than checking ?closed?.

Another problem with the example is that printing the chunk as a bytes object can trigger BytesWarning. I would add a ?repr? call to avoid that.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, martin.panter

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

From report at bugs.python.org  Thu Jan  3 16:35:45 2019
From: report at bugs.python.org (Martijn Pieters)
Date: Thu, 03 Jan 2019 21:35:45 +0000
Subject: [docs] [issue35654] Remove 'guarantee' that sorting only relies on
 __lt__ from sorting howto
Message-ID: <1546551341.08.0.0908752668479.issue35654@roundup.psfhosted.org>


New submission from Martijn Pieters <mj at python.org>:

Currently, the sorting HOWTO at https://docs.python.org/3/howto/sorting.html#odd-and-ends contains the text:

> The sort routines are guaranteed to use __lt__() when making comparisons between two objects. So, it is easy to add a standard sort order to a class by defining an __lt__() method

Nowhere else in the Python documentation is this guarantee made, however. That sort currently uses __lt__ only is, in my opinion, an implementation detail.

The above advice also goes against the advice PEP 8 gives:

> When implementing ordering operations with rich comparisons, it is best to implement all six operations (__eq__, __ne__, __lt__, __le__, __gt__, __ge__) rather than relying on other code to only exercise a particular comparison.
>
> To minimize the effort involved, the functools.total_ordering() decorator provides a tool to generate missing comparison methods.

The 'guarantee' seems to have been copied verbatim from the Wiki version of the HOWTO in https://github.com/python/cpython/commit/0fe095e87f727f4a19b6cbfd718d51935a888740, where that part of the Wiki page was added by an anonymous user in revision 44 to the page: https://wiki.python.org/moin/HowTo/Sorting?action=diff&rev1=43&rev2=44

Can this be removed from the HOWTO?

----------
assignee: docs at python
components: Documentation
messages: 332949
nosy: docs at python, mjpieters, rhettinger
priority: normal
severity: normal
status: open
title: Remove 'guarantee' that sorting only relies on __lt__ from sorting howto
versions: Python 3.6

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

From report at bugs.python.org  Thu Jan  3 17:07:35 2019
From: report at bugs.python.org (skorpeo)
Date: Thu, 03 Jan 2019 22:07:35 +0000
Subject: [docs] [issue35649] http.client doesn't close. Infinite loop
In-Reply-To: <1546546901.23.0.686832241357.issue35649@roundup.psfhosted.org>
Message-ID: <CAMXrOMPB7Qvqwuw0F619u+F6+ejh=PnpcShPTFyQFxcThaqgXA@mail.gmail.com>


skorpeo <skorpeo11 at gmail.com> added the comment:

Ha, ok that would explain it.  Yes, I think it would indeed be helpful to
update the example, but then again I guess leaving it as is may be a good
way to find out if people are reading the docs.

On Thu, Jan 3, 2019 at 10:21 PM Martin Panter <report at bugs.python.org>
wrote:

>
> Martin Panter <vadmium+py at gmail.com> added the comment:
>
> This was changed in Python 3.2+ in Issue 16723. The response object no
> longer sets the ?closed? attribute when it runs out of data; it is only set
> when the ?close? method is called. Perhaps the example should be amended so
> that it checks if ?read? returned an empty string, rather than checking
> ?closed?.
>
> Another problem with the example is that printing the chunk as a bytes
> object can trigger BytesWarning. I would add a ?repr? call to avoid that.
>
> ----------
> assignee:  -> docs at python
> components: +Documentation
> nosy: +docs at python, martin.panter
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue35649>
> _______________________________________
>

----------
title: http.client doesn't close.  Infinite loop -> http.client doesn't close. Infinite loop

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

From report at bugs.python.org  Thu Jan  3 17:20:39 2019
From: report at bugs.python.org (Tim Peters)
Date: Thu, 03 Jan 2019 22:20:39 +0000
Subject: [docs] [issue35654] Remove 'guarantee' that sorting only relies on
 __lt__ from sorting howto
In-Reply-To: <1546551341.08.0.0908752668479.issue35654@roundup.psfhosted.org>
Message-ID: <1546554037.66.0.953301677455.issue35654@roundup.psfhosted.org>


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

I don't know that the language needs to define this, but sticking to __lt__ was a wholly deliberate design decision for CPython.

----------
nosy: +tim.peters

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

From report at bugs.python.org  Thu Jan  3 19:39:10 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Fri, 04 Jan 2019 00:39:10 +0000
Subject: [docs] [issue35654] Remove 'guarantee' that sorting only relies on
 __lt__ from sorting howto
In-Reply-To: <1546551341.08.0.0908752668479.issue35654@roundup.psfhosted.org>
Message-ID: <1546562348.66.0.479829328187.issue35654@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

> That sort currently uses __lt__ only is, in my opinion, an implementation detail.

Its only an implementation detail until the language specification defines it as a guarantee of the language. Then it becomes part of the sorting API.

Personally, I think it is a nice feature that sorting works for objects which define only __lt__, and it sounds like Tim is happy for that to be part of the sort API.

This is documented under list.sort() but not sorted():

https://docs.python.org/3/library/stdtypes.html#list.sort

https://docs.python.org/3/library/functions.html#sorted

Rather than removing it from the HOWTO, I would rather document that fact under sorted() as well.

If you still want to argue that we should not document this as a language guarantee, for the sake of other implementations such as Jython and IronPython, you should raise it on Python-Dev. It would probably help if you had other implementation maintainers state that this was a burden on them.

For what it is worth, it seems that Jython 2.5 supports this feature too.

----------
nosy: +steven.daprano

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

From report at bugs.python.org  Thu Jan  3 21:38:33 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 04 Jan 2019 02:38:33 +0000
Subject: [docs] [issue35654] Remove 'guarantee' that sorting only relies on
 __lt__ from sorting howto
In-Reply-To: <1546551341.08.0.0908752668479.issue35654@roundup.psfhosted.org>
Message-ID: <1546569511.17.0.686116615813.issue35654@roundup.psfhosted.org>


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

I also prefer to leave this as is.  FWIW, heapq and bisect are also deliberately based on __lt__.  The PEP 8 advice (something I wrote) is primarily about making code less fragile and avoiding surprising behavior.

----------
assignee: docs at python -> rhettinger

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

From report at bugs.python.org  Thu Jan  3 22:33:02 2019
From: report at bugs.python.org (Tim Peters)
Date: Fri, 04 Jan 2019 03:33:02 +0000
Subject: [docs] [issue35654] Remove 'guarantee' that sorting only relies on
 __lt__ from sorting howto
In-Reply-To: <1546551341.08.0.0908752668479.issue35654@roundup.psfhosted.org>
Message-ID: <1546572781.17.0.681999017076.issue35654@roundup.psfhosted.org>


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

Steven, thanks for noticing the docs!  I was surprised to hear it wasn't documented, but not surprised enough to check myself ;-)

This decision was suggested by me, and endorsed by Guido, when designing timsort looking ahead to Python 3, where __cmp__ was going to vanish.  The convenience of needing to add only a single method to support a custom sort order is considerable.

Since it's working as designed and dccumented, and I know for certain that code in the wild relises on it, I'm inclined to reject this report.  However, rather than add more words to `sorted()`, I'd suggest removing words from `sorted()`, pointing instead to the `.sort()` docs for all specification of `sorted()`'s sorting behavior.

----------

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

From report at bugs.python.org  Fri Jan  4 05:38:46 2019
From: report at bugs.python.org (Martijn Pieters)
Date: Fri, 04 Jan 2019 10:38:46 +0000
Subject: [docs] [issue35654] Remove 'guarantee' that sorting only relies on
 __lt__ from sorting howto
In-Reply-To: <1546551341.08.0.0908752668479.issue35654@roundup.psfhosted.org>
Message-ID: <1546598324.35.0.306140741928.issue35654@roundup.psfhosted.org>


Martijn Pieters <mj at python.org> added the comment:

Well, if this is indeed by design (and I missed the list.sort() reference) then I agree the HOWTO should not be changed!

I'd be happy to change this to asking for more explicit mentions in the docs for sorted, heapq and bisect that using only < (__lt__) is a deliberate choice.

----------

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

From report at bugs.python.org  Fri Jan  4 05:39:30 2019
From: report at bugs.python.org (Martijn Pieters)
Date: Fri, 04 Jan 2019 10:39:30 +0000
Subject: [docs] [issue35654] Remove 'guarantee' that sorting only relies on
 __lt__ from sorting howto
In-Reply-To: <1546551341.08.0.0908752668479.issue35654@roundup.psfhosted.org>
Message-ID: <1546598368.17.0.342130703443.issue35654@roundup.psfhosted.org>


Martijn Pieters <mj at python.org> added the comment:

(I have no opinion on this having to be a language feature however)

----------

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

From report at bugs.python.org  Fri Jan  4 06:02:44 2019
From: report at bugs.python.org (Juan)
Date: Fri, 04 Jan 2019 11:02:44 +0000
Subject: [docs] [issue35655] documentation have wrong info about fibo module
 examples
Message-ID: <1546599762.04.0.11226790108.issue35655@roundup.psfhosted.org>


New submission from Juan <juanbaio10 at gmail.com>:

The below sections in modules documentation have wrong information about fibo module:
6. Modules
6.1. More on Modules
6.1.1. Executing modules as scripts
6.3. The dir() Function

The name of module is Fibo not fibo and the attributes are fab,fab2 not fib,fib2.


root at archlinux ~]# python2 --version
Python 2.7.15
[root at archlinux ~]# pip2 --version
pip 18.1 from /usr/lib/python2.7/site-packages/pip (python 2.7)
[root at archlinux ~]# pip2 install fibo
Collecting fibo
  Using cached https://files.pythonhosted.org/packages/24/50/e74bd48bbef1040afb01b107e6cfbc3c1e991be24c10c40a37e335383e54/Fibo-1.0.0.tar.gz
Installing collected packages: fibo
  Running setup.py install for fibo ... done
Successfully installed fibo-1.0.0
[root at archlinux ~]# pip2 list modules |grep -i fibo
Fibo         1.0.0  
[root at archlinux ~]# python2
Python 2.7.15 (default, Jun 27 2018, 13:05:28) 
[GCC 8.1.1 20180531] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import fibo
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named fibo
>>> import Fibo
>>> Fibo.fib(10)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'fib'
>>> Fibo.fib2(10)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute 'fib2'
>>> Fibo.fab(10)
1
1
2
3
5
8
13
21
34
55
>>> Fibo.fab2(10)
[1, 1, 2, 3, 5, 8, 13, 21, 34, 55]
>>> Fibo.__name__
'Fibo'
>>> dir(Fibo)
['Fab', '__builtins__', '__doc__', '__file__', '__name__', '__package__', 'fab', 'fab2', 'fab4']

----------
assignee: docs at python
components: Documentation
messages: 332967
nosy: docs at python, eric.araujo, ezio.melotti, juanbaio10, mdk, willingc
priority: normal
severity: normal
status: open
title: documentation have wrong info about fibo module examples
type: enhancement
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Jan  4 06:11:24 2019
From: report at bugs.python.org (Christian Heimes)
Date: Fri, 04 Jan 2019 11:11:24 +0000
Subject: [docs] [issue35655] documentation have wrong info about fibo module
 examples
In-Reply-To: <1546599762.04.0.11226790108.issue35655@roundup.psfhosted.org>
Message-ID: <1546600282.84.0.316992473614.issue35655@roundup.psfhosted.org>


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

The documentation examples are not based on the 3rd party Fibo Python package. All examples are based on the short script https://docs.python.org/3/tutorial/modules.html?highlight=fibo#modules :

  For instance, use your favorite text editor to create a file
  called fibo.py in the current directory with the following contents

----------
nosy: +christian.heimes
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Jan  4 08:00:09 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Fri, 04 Jan 2019 13:00:09 +0000
Subject: [docs] [issue35609] Improve of abc.py docstring
In-Reply-To: <1546052751.93.0.333388893142.issue35609@roundup.psfhosted.org>
Message-ID: <1546606808.02.0.499057950841.issue35609@roundup.psfhosted.org>


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

> No plan for removal.  See https://bugs.python.org/issue28886#msg282582

Thanks!

----------

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

From report at bugs.python.org  Fri Jan  4 09:14:38 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 04 Jan 2019 14:14:38 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546611276.58.0.172731957545.issue35631@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:


New changeset 31ec52a9afedd77e36a3ddc31c4c45664b8ac410 by Ivan Levkivskyi (Ville Skytt?) in branch 'master':
bpo-35631: Improve typing docs wrt abstract/concrete collection types (GH-11396)
https://github.com/python/cpython/commit/31ec52a9afedd77e36a3ddc31c4c45664b8ac410


----------

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

From report at bugs.python.org  Fri Jan  4 09:15:00 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Jan 2019 14:15:00 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546611300.28.0.634471078113.issue35631@roundup.psfhosted.org>


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


----------
pull_requests: +10853

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

From report at bugs.python.org  Fri Jan  4 09:15:06 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Jan 2019 14:15:06 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546611306.12.0.247515372337.issue35631@roundup.psfhosted.org>


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


----------
pull_requests: +10853, 10854

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

From report at bugs.python.org  Fri Jan  4 09:15:12 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Jan 2019 14:15:12 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546611312.91.0.716995455376.issue35631@roundup.psfhosted.org>


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


----------
pull_requests: +10854, 10856

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

From report at bugs.python.org  Fri Jan  4 09:15:20 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Jan 2019 14:15:20 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546611320.49.0.462531491939.issue35631@roundup.psfhosted.org>


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


----------
pull_requests: +10856, 10857

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

From report at bugs.python.org  Fri Jan  4 09:15:26 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Jan 2019 14:15:26 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546611326.61.0.907039231337.issue35631@roundup.psfhosted.org>


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


----------
pull_requests: +10856, 10857, 10858

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

From report at bugs.python.org  Fri Jan  4 09:15:32 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Jan 2019 14:15:32 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546611332.56.0.765837578142.issue35631@roundup.psfhosted.org>


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


----------
pull_requests: +10853, 10854, 10855, 10856, 10857, 10858

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

From report at bugs.python.org  Fri Jan  4 09:20:23 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 04 Jan 2019 14:20:23 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546611621.73.0.364812516131.issue35631@roundup.psfhosted.org>


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


New changeset 902196d867a34cc154fa9c861c883e69232251c6 by Miss Islington (bot) in branch '3.7':
bpo-35631: Improve typing docs wrt abstract/concrete collection types (GH-11396)
https://github.com/python/cpython/commit/902196d867a34cc154fa9c861c883e69232251c6


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

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

From report at bugs.python.org  Fri Jan  4 09:26:43 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 04 Jan 2019 14:26:43 +0000
Subject: [docs] [issue35631] Improve typing docs wrt abstract/concrete
 collection types
In-Reply-To: <1546328143.85.0.754432945533.issue35631@roundup.psfhosted.org>
Message-ID: <1546612002.46.0.883399873751.issue35631@roundup.psfhosted.org>


Ivan Levkivskyi <levkivskyi at gmail.com> added the comment:

I think this can be closed now. Whether to merge doc-fix backport to now security-only 3.6 branch is up to Ned.

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

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

From report at bugs.python.org  Fri Jan  4 11:11:05 2019
From: report at bugs.python.org (Ajay Mahato)
Date: Fri, 04 Jan 2019 16:11:05 +0000
Subject: [docs] [issue9305] Don't use east/west of UTC in date/time
 documentation
In-Reply-To: <1279556505.28.0.814004588201.issue9305@psf.upfronthosting.co.za>
Message-ID: <1546618257.88.0.960668055513.issue9305@roundup.psfhosted.org>


Ajay Mahato <ajjayymahato at gmail.com> added the comment:

I would like to work on this issue. Please assign this to me.

----------
nosy: +Ajay Mahato

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

From report at bugs.python.org  Fri Jan  4 13:52:13 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 04 Jan 2019 18:52:13 +0000
Subject: [docs] [issue35168] shlex punctuation_chars inconsistency
In-Reply-To: <1541439134.06.0.788709270274.issue35168@psf.upfronthosting.co.za>
Message-ID: <1546627933.61.0.363528191135.issue35168@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
keywords: +easy
nosy: +docs at python
stage:  -> needs patch
versions:  -Python 3.6

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

From report at bugs.python.org  Fri Jan  4 14:31:43 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Jan 2019 19:31:43 +0000
Subject: [docs] [issue35625] Comprehension doc doesn't mention buggy class
 scope behavior
In-Reply-To: <1546253280.49.0.920078772343.issue35625@roundup.psfhosted.org>
Message-ID: <1546630301.55.0.014392849266.issue35625@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
title: documentation of list, set & dict comprehension make no mention of buggy class scope behavior -> Comprehension doc doesn't mention buggy class scope behavior
versions: +Python 3.8 -Python 2.7, Python 3.4, Python 3.5, Python 3.6

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

From report at bugs.python.org  Fri Jan  4 14:47:05 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 04 Jan 2019 19:47:05 +0000
Subject: [docs] [issue33896] Document what components make up the
 filecmp.cmp os.stat signature.
In-Reply-To: <1529345931.78.0.56676864532.issue33896@psf.upfronthosting.co.za>
Message-ID: <1546631225.33.0.970934730804.issue33896@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
versions:  -Python 3.6

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

From report at bugs.python.org  Fri Jan  4 15:35:24 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 04 Jan 2019 20:35:24 +0000
Subject: [docs] [issue15457] consistent treatment of generator terminology
In-Reply-To: <1343302676.51.0.168761959505.issue15457@psf.upfronthosting.co.za>
Message-ID: <1546634121.33.0.335753501144.issue15457@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

Issue24400 changed some of the documentation wording around generators.  I don't know if there is still interest in applying the other parts of this patch.

----------
nosy: +cheryl.sabella
versions: +Python 3.7, Python 3.8 -Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Jan  4 16:13:14 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 04 Jan 2019 21:13:14 +0000
Subject: [docs] [issue35616] Change references to '4.0'.
In-Reply-To: <1546145542.58.0.745728606206.issue35616@roundup.psfhosted.org>
Message-ID: <1546636393.01.0.00919448906012.issue35616@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Removing the C API function is a major breaking change. AFAIK there was no precedence since 3.0. It may be that we will name the new version 4.0 after doing this.

In any case, first than remove this API, we need to pass the following steps:

* Implement Py_DEPRECATED on Windows and use it for *all* deprecated functions.
* Get rid of using deprecated API in the core and stdlib. I'm working on this.
* I think it is good idea to implement a custom build without wchar_t cache and deprecated API for testing with third-party code. I'm working on this.

One or two versions after using Py_DEPRECATED for all deprecated functions (but not earlier than EOL of 2.7) we can make them issuing run-time warnings. One or two versions after this we can replace them with stub functions that always fail. I think they can be removed after around 5 years from now. Currently we do not have exact terms. I do not see a problem with using 4.0 as a hypothetical removal term.

----------
nosy: +serhiy.storchaka

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

From report at bugs.python.org  Fri Jan  4 16:32:56 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Jan 2019 21:32:56 +0000
Subject: [docs] [issue35649] http.client doesn't close. Infinite loop
In-Reply-To: <1546533708.33.0.81545579375.issue35649@roundup.psfhosted.org>
Message-ID: <1546637576.13.0.786231413479.issue35649@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
versions: +Python 3.8 -Python 3.5, Python 3.6

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

From report at bugs.python.org  Fri Jan  4 16:36:02 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Jan 2019 21:36:02 +0000
Subject: [docs] [issue35651] PEP 257 (active) references PEP 258 (rejected)
 as if it were active
In-Reply-To: <1546536866.6.0.633154963858.issue35651@roundup.psfhosted.org>
Message-ID: <1546637759.61.0.252179561533.issue35651@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Guido, you are the

----------
nosy: +goodger, gvanrossum, terry.reedy
versions:  -Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Jan  4 16:36:22 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Jan 2019 21:36:22 +0000
Subject: [docs] [issue35651] PEP 257 (active) references PEP 258 (rejected)
 as if it were active
In-Reply-To: <1546536866.6.0.633154963858.issue35651@roundup.psfhosted.org>
Message-ID: <1546637780.9.0.351703099101.issue35651@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
Removed message: https://bugs.python.org/msg333003

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

From report at bugs.python.org  Fri Jan  4 16:39:10 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Jan 2019 21:39:10 +0000
Subject: [docs] [issue35654] Remove 'guarantee' that sorting only relies on
 __lt__ from sorting howto
In-Reply-To: <1546551341.08.0.0908752668479.issue35654@roundup.psfhosted.org>
Message-ID: <1546637950.74.0.330703079876.issue35654@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


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

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

From report at bugs.python.org  Fri Jan  4 17:04:49 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 04 Jan 2019 22:04:49 +0000
Subject: [docs] [issue35616] Change references to '4.0'.
In-Reply-To: <1546145542.58.0.745728606206.issue35616@roundup.psfhosted.org>
Message-ID: <1546639488.4.0.857752980912.issue35616@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

After reading Serhiy's explanation, I agree that '4.0' is better than a specific '3.nn'.  I did not realize how much was still left to be done.  We can revisit this when there is a definite removal date.  A literal 'sometime' might be better, but not worth arguing for.  Most of the other occurrences of '4.0' are related to the old unicode API.

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

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

From report at bugs.python.org  Fri Jan  4 17:58:08 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Jan 2019 22:58:08 +0000
Subject: [docs] [issue35616] Change references to '4.0'.
In-Reply-To: <1546145542.58.0.745728606206.issue35616@roundup.psfhosted.org>
Message-ID: <1546642686.84.0.997362808149.issue35616@roundup.psfhosted.org>


STINNER Victor <vstinner at redhat.com> added the comment:

I disagree. It's acceptable to break the C API in a minor release if the change has been properly promoted, documented, announced, etc.

IMHO breaking the C API in 4.0 is going to send a bad signal to users.

Multiple core developers asked multiple times to wait until Python 2 is really dead before removing some features which are used on Python 2 and Python 3. So at least, we must wait until January 1st, 2020, before removing Py_UNICODE APIs.

I also would like to see the deprecation warning supported on Windows.

I didn't see any announcement of future removal of C API on the capi-sig mailing list.

----------

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

From report at bugs.python.org  Fri Jan  4 18:00:50 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 04 Jan 2019 23:00:50 +0000
Subject: [docs] [issue35616] Change references to '4.0'.
In-Reply-To: <1546145542.58.0.745728606206.issue35616@roundup.psfhosted.org>
Message-ID: <1546642849.61.0.974971744349.issue35616@roundup.psfhosted.org>


STINNER Victor <vstinner at redhat.com> added the comment:

> One or two versions after using Py_DEPRECATED for all deprecated functions (but not earlier than EOL of 2.7) we can make them issuing run-time warnings.

Maybe we can experiment adding warnings only in development mode, when python3 -X dev is used?

> I'm working on this.

Thanks :-)

----------

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

From report at bugs.python.org  Fri Jan  4 21:23:14 2019
From: report at bugs.python.org (Windson Yang)
Date: Sat, 05 Jan 2019 02:23:14 +0000
Subject: [docs] [issue35105] Document that CPython accepts "invalid"
 identifiers
In-Reply-To: <1540815891.13.0.788709270274.issue35105@psf.upfronthosting.co.za>
Message-ID: <1546654990.74.0.0538765185155.issue35105@roundup.psfhosted.org>


Windson Yang <wiwindson at outlook.com> added the comment:

I agreed with @Raymond Hettinger, I will update the PR from your suggestion if no other ideas in next week.

----------

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

From report at bugs.python.org  Fri Jan  4 21:54:53 2019
From: report at bugs.python.org (Windson Yang)
Date: Sat, 05 Jan 2019 02:54:53 +0000
Subject: [docs] [issue35325] imp.find_module() return value documentation
 discrepancy
In-Reply-To: <1543303624.81.0.788709270274.issue35325@psf.upfronthosting.co.za>
Message-ID: <1546656891.12.0.57769235005.issue35325@roundup.psfhosted.org>


Windson Yang <wiwindson at outlook.com> added the comment:

> The documentation should state that "pathname" will be None (not the empty string) for built-in and frozen modules in order to be in line with the implementation.

Both the "file" and "pathname" will be None for built-in and frozen modules, right? In the PR @ericsnowcurrently suggested add:

>  If the module is built-in or frozen then *file* and *pathname* are both ``None`` and the *description* tuple contains empty...

I think it also works.

----------

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

From report at bugs.python.org  Fri Jan  4 23:20:49 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 05 Jan 2019 04:20:49 +0000
Subject: [docs] [issue35625] Comprehension doc doesn't mention buggy class
 scope behavior
In-Reply-To: <1546253280.49.0.920078772343.issue35625@roundup.psfhosted.org>
Message-ID: <1546662045.53.0.334033020611.issue35625@roundup.psfhosted.org>


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

We should remove the "equivalent to for-loops" wording for list comprehensions.  That is a hold-over from 2.7 where it used to be true.  That said, the list comprehension section is too early in the tutorial to go into scopes and generators, so a full explanation will need to be deferred.

> As an aside, I agree with the developers who consider 
> this scope "limitation" a bug and not (paraphrasing) 
> "just how the language works", since the exact same two
> lines of code, which depend on no other variables or 
> functions, work in a function or module but not in a class.

If you view classes as just another nested scope, I can see why you might think the behavior is buggy, limited, or undesirable.  That however is not how the language is designed.  Think about why methods have to reference class variables using "self.classvar" rather than just "classvar".  When the methods run, they have access to their own locals() and to the module level globals().  To access the locals() for the class, they need use "self.classvar" or "classname.classvar".  This is central to how python works .  There are two separate lookup chains, one for variables (locals -> nested scopes -> globals -> __builtins__ -> NameError) and another for attributes (inst_dict -> class_dict -> parent_class_dict -> AttributeError).

Guido intentionally shifted list comprehensions to work like generator expressions.  In a class scope, they behave like methods in that they have access to the outer globals but no direct access to the locals() in the class.

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

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

From report at bugs.python.org  Sat Jan  5 00:28:15 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 05 Jan 2019 05:28:15 +0000
Subject: [docs] [issue35325] imp.find_module() return value documentation
 discrepancy
In-Reply-To: <1543303624.81.0.788709270274.issue35325@psf.upfronthosting.co.za>
Message-ID: <1546666094.35.0.804254035882.issue35325@roundup.psfhosted.org>


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


----------
nosy: +brett.cannon
versions:  -Python 3.4, Python 3.5, Python 3.6

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

From report at bugs.python.org  Sat Jan  5 02:41:03 2019
From: report at bugs.python.org (Ajay Mahato)
Date: Sat, 05 Jan 2019 07:41:03 +0000
Subject: [docs] [issue9305] Don't use east/west of UTC in date/time
 documentation
In-Reply-To: <1279556505.28.0.814004588201.issue9305@psf.upfronthosting.co.za>
Message-ID: <1546674056.62.0.826862687449.issue9305@roundup.psfhosted.org>


Ajay Mahato <ajjayymahato at gmail.com> added the comment:

I am taking up this issue.

----------

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

From report at bugs.python.org  Sat Jan  5 10:09:00 2019
From: report at bugs.python.org (Julien Palard)
Date: Sat, 05 Jan 2019 15:09:00 +0000
Subject: [docs] [issue35584] Wrong statement about ^ in howto/regex.rst
In-Reply-To: <1545775848.12.0.712150888896.issue35584@roundup.psfhosted.org>
Message-ID: <1546700939.68.0.993148954618.issue35584@roundup.psfhosted.org>


Julien Palard <julien+python at palard.fr> added the comment:

yes.

----------

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

From report at bugs.python.org  Sat Jan  5 10:30:29 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 05 Jan 2019 15:30:29 +0000
Subject: [docs] [issue35625] Comprehension doc doesn't mention buggy class
 scope behavior
In-Reply-To: <1546253280.49.0.920078772343.issue35625@roundup.psfhosted.org>
Message-ID: <1546702226.91.0.397940761154.issue35625@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

See also issue3692.

----------
nosy: +serhiy.storchaka

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

From report at bugs.python.org  Sat Jan  5 11:08:03 2019
From: report at bugs.python.org (Carl Bordum Hansen)
Date: Sat, 05 Jan 2019 16:08:03 +0000
Subject: [docs] [issue35666] Update design FAQ about assignment expression
Message-ID: <1546704480.61.0.245493701505.issue35666@roundup.psfhosted.org>


New submission from Carl Bordum Hansen <carl at bordum.dk>:

Hi there,

In ``Doc/faq/design.rst`` there is an explanation of why Python does not have assignment in expressions. This is dated since PEP 572 / Python 3.8.

Online version: https://docs.python.org/3/faq/design.html#why-can-t-i-use-an-assignment-in-an-expression

I suggest updating it to the attached file. `git diff`:

```
diff --git a/Doc/faq/design.rst b/Doc/faq/design.rst
index e2d63a0323..e61284611d 100644
--- a/Doc/faq/design.rst
+++ b/Doc/faq/design.rst
@@ -149,7 +149,15 @@ to tell Python which namespace to use.
 Why can't I use an assignment in an expression?
 -----------------------------------------------
 
-Many people used to C or Perl complain that they want to use this C idiom:
+In Python 3.8 and newer, you can use assignment in an expression with the
+``:=`` operator (as described in :pep:`572`)::
+
+    while line := f.readline():
+        ...  # do something with line
+
+For more than 25 years it was not possible to do assignments in expressions in
+Python. Naturally, many people used to C or Perl would complain that they want
+to use this C idiom:
 
 .. code-block:: c
 
@@ -157,7 +165,7 @@ Many people used to C or Perl complain that they want to use this C idiom:
        // do something with line
    }
 
-where in Python you're forced to write this::
+where in Python you would be forced to write this::
 
    while True:
        line = f.readline()
@@ -165,8 +173,10 @@ where in Python you're forced to write this::
            break
        ...  # do something with line
 
-The reason for not allowing assignment in Python expressions is a common,
-hard-to-find bug in those other languages, caused by this construct:
+The reason different operators are used for assignment and assignment in
+expressions (``=`` and ``:=``, respectively), and why Python didn't allow
+assignment in expressions for a long time is a common, hard-to-find bug in
+those other languages, caused by this construct:
 
 .. code-block:: c
 
@@ -180,11 +190,6 @@ hard-to-find bug in those other languages, caused by this construct:
 The error is a simple typo: ``x = 0``, which assigns 0 to the variable ``x``,
 was written while the comparison ``x == 0`` is certainly what was intended.
 
-Many alternatives have been proposed.  Most are hacks that save some typing but
-use arbitrary or cryptic syntax or keywords, and fail the simple criterion for
-language change proposals: it should intuitively suggest the proper meaning to a
-human reader who has not yet been introduced to the construct.
-
 An interesting phenomenon is that most experienced Python programmers recognize
 the ``while True`` idiom and don't seem to be missing the assignment in
 expression construct much; it's only newcomers who express a strong desire to

```

----------
assignee: docs at python
components: Documentation
files: design.rst
messages: 333063
nosy: carlbordum, docs at python
priority: normal
severity: normal
status: open
title: Update design FAQ about assignment expression
type: enhancement
versions: Python 3.8
Added file: https://bugs.python.org/file48025/design.rst

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

From report at bugs.python.org  Sat Jan  5 11:30:02 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 05 Jan 2019 16:30:02 +0000
Subject: [docs] [issue35666] Update design FAQ about assignment expression
In-Reply-To: <1546704480.61.0.245493701505.issue35666@roundup.psfhosted.org>
Message-ID: <1546705800.76.0.339849855414.issue35666@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


----------
dependencies: +PEP 572: Assignment Expressions

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

From report at bugs.python.org  Sat Jan  5 11:32:28 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 05 Jan 2019 16:32:28 +0000
Subject: [docs] [issue35666] Update design FAQ about assignment expression
In-Reply-To: <1546704480.61.0.245493701505.issue35666@roundup.psfhosted.org>
Message-ID: <1546705945.3.0.643643944505.issue35666@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

This can be changed only after implementing PEP 572.

----------
nosy: +serhiy.storchaka

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

From report at bugs.python.org  Sat Jan  5 12:41:14 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Sat, 05 Jan 2019 17:41:14 +0000
Subject: [docs] [issue35651] PEP 257 (active) references PEP 258 (rejected)
 as if it were active
In-Reply-To: <1546536866.6.0.633154963858.issue35651@roundup.psfhosted.org>
Message-ID: <1546710072.51.0.673373238449.issue35651@roundup.psfhosted.org>


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

A rejected PEP still exists in perpetuity, and can still be used as a reference. Also, the reason for PEP 258's rejection is not that it is invalid, but that it's not slated for stdlib inclusion. So I think that the reference is still useful, and I don't think there's anything that needs to be done here.

----------
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Jan  5 14:19:40 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 05 Jan 2019 19:19:40 +0000
Subject: [docs] [issue35603] table header in output of
 difflib.HtmlDiff.make_table is not escaped and can be rendered as code in
 the browser
In-Reply-To: <1545988680.87.0.068090288545.issue35603@roundup.psfhosted.org>
Message-ID: <1546715978.21.0.566797421405.issue35603@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

Yes, please make a documentation PR. Since this behavior can cause a security hole in the user code, make this note visually attractive (maybe use the "note" directive).

----------
stage: patch review -> needs patch

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

From report at bugs.python.org  Sat Jan  5 14:51:59 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 05 Jan 2019 19:51:59 +0000
Subject: [docs] [issue35603] table header in output of
 difflib.HtmlDiff.make_table is not escaped and can be rendered as code in
 the browser
In-Reply-To: <1545988680.87.0.068090288545.issue35603@roundup.psfhosted.org>
Message-ID: <1546717919.39.0.844484278931.issue35603@roundup.psfhosted.org>


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


----------
pull_requests: +10878
stage: needs patch -> patch review

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

From report at bugs.python.org  Sat Jan  5 14:52:07 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 05 Jan 2019 19:52:07 +0000
Subject: [docs] [issue35603] table header in output of
 difflib.HtmlDiff.make_table is not escaped and can be rendered as code in
 the browser
In-Reply-To: <1545988680.87.0.068090288545.issue35603@roundup.psfhosted.org>
Message-ID: <1546717927.53.0.232260409384.issue35603@roundup.psfhosted.org>


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


----------
pull_requests: +10878, 10879
stage: needs patch -> patch review

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

From report at bugs.python.org  Sat Jan  5 14:52:15 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 05 Jan 2019 19:52:15 +0000
Subject: [docs] [issue35603] table header in output of
 difflib.HtmlDiff.make_table is not escaped and can be rendered as code in
 the browser
In-Reply-To: <1545988680.87.0.068090288545.issue35603@roundup.psfhosted.org>
Message-ID: <1546717935.73.0.490908487587.issue35603@roundup.psfhosted.org>


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


----------
pull_requests: +10878, 10879, 10880
stage: needs patch -> patch review

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

From report at bugs.python.org  Sat Jan  5 14:56:42 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 05 Jan 2019 19:56:42 +0000
Subject: [docs] [issue35603] table header in output of
 difflib.HtmlDiff.make_table is not escaped and can be rendered as code in
 the browser
In-Reply-To: <1545988680.87.0.068090288545.issue35603@roundup.psfhosted.org>
Message-ID: <1546718200.77.0.681618041363.issue35603@roundup.psfhosted.org>


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

I have added a doc note under make_file docs which has docs for fromdesc and todesc. make_table refers to make_file for fromdesc and todesc docs. I have added a screenshot of the rendering using note and warning directive. I feel note directive is sufficient for this. Placement and wording suggestions are welcome.

----------

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

From report at bugs.python.org  Sat Jan  5 16:30:53 2019
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Sat, 05 Jan 2019 21:30:53 +0000
Subject: [docs] [issue35616] Change references to '4.0'.
In-Reply-To: <1546145542.58.0.745728606206.issue35616@roundup.psfhosted.org>
Message-ID: <1546723851.82.0.775265565403.issue35616@roundup.psfhosted.org>


Marc-Andre Lemburg <mal at egenix.com> added the comment:

Why not change the wording to read "... will be considered for removal in the next major Python release".

Note that removal of Py_UNICODE APIs will not only break compatibility with Python 2, but also with the early Python 3 releases.

And please also consider that we may see another change in the Unicode implementation... I've heard discussions about using UTF-8 as internal representation to address the issues with the current unified approach.

----------
nosy: +lemburg

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

From report at bugs.python.org  Sat Jan  5 16:39:27 2019
From: report at bugs.python.org (Seval Geyik)
Date: Sat, 05 Jan 2019 21:39:27 +0000
Subject: [docs] [issue35625] Comprehension doc doesn't mention buggy class
 scope behavior
In-Reply-To: <1546253280.49.0.920078772343.issue35625@roundup.psfhosted.org>
Message-ID: <1546724363.63.0.670786118013.issue35625@roundup.psfhosted.org>


Change by Seval Geyik <gulseval1987 at gmail.com>:


----------
components: +email
nosy: +barry, r.david.murray
type: behavior -> security
Added file: https://bugs.python.org/file48026/keyfile.png

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

From report at bugs.python.org  Sat Jan  5 16:40:03 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Sat, 05 Jan 2019 21:40:03 +0000
Subject: [docs] [issue35616] Change references to '4.0'.
In-Reply-To: <1546145542.58.0.745728606206.issue35616@roundup.psfhosted.org>
Message-ID: <1546724402.01.0.686562715737.issue35616@roundup.psfhosted.org>


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

Hello!

IMHO I don't think is good say  that they will remove on a version that is not planned yet. 

I agree with Marc-Andre is better say " they will be remove in the next major release"

----------

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

From report at bugs.python.org  Sat Jan  5 18:07:27 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 05 Jan 2019 23:07:27 +0000
Subject: [docs] [issue30487] DOC: automatically create a venv and install
 Sphinx when running make
In-Reply-To: <1495817388.46.0.640927890572.issue30487@psf.upfronthosting.co.za>
Message-ID: <1546729644.8.0.344374899987.issue30487@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

I believe this can be closed as resolved?  Thanks.

----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Sat Jan  5 18:18:32 2019
From: report at bugs.python.org (Ashwin Ramaswami)
Date: Sat, 05 Jan 2019 23:18:32 +0000
Subject: [docs] [issue13127] xml.dom.Attr.name is not labeled as read-only
In-Reply-To: <1318047492.07.0.217686953928.issue13127@psf.upfronthosting.co.za>
Message-ID: <1546730306.36.0.557575549869.issue13127@roundup.psfhosted.org>


Ashwin Ramaswami <aramaswamis at gmail.com> added the comment:

This behavior appears to be working as expected per the documentation when using Python 3.7.1. I am able to change name, but changing localName gives me a NoModificationAllowedErr error.

----------
nosy: +Ashwin Ramaswami
versions: +Python 3.7 -Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Sat Jan  5 18:27:06 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 05 Jan 2019 23:27:06 +0000
Subject: [docs] [issue34431] Docs does not eval allows code object as
 argument
In-Reply-To: <1534608199.83.0.56676864532.issue34431@psf.upfronthosting.co.za>
Message-ID: <1546730820.43.0.871071157398.issue34431@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

Hi Jonathan,

Did you have any additional questions about opening a pull request for these changes?  Thanks!

----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Sat Jan  5 20:09:30 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Jan 2019 01:09:30 +0000
Subject: [docs] [issue35649] http.client doesn't close. Infinite loop
In-Reply-To: <1546533708.33.0.81545579375.issue35649@roundup.psfhosted.org>
Message-ID: <1546736970.33.0.539792720339.issue35649@roundup.psfhosted.org>


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


----------
keywords: +patch
pull_requests: +10884
stage:  -> patch review

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

From report at bugs.python.org  Sat Jan  5 20:09:36 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Jan 2019 01:09:36 +0000
Subject: [docs] [issue35649] http.client doesn't close. Infinite loop
In-Reply-To: <1546533708.33.0.81545579375.issue35649@roundup.psfhosted.org>
Message-ID: <1546736976.53.0.847879074293.issue35649@roundup.psfhosted.org>


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


----------
keywords: +patch, patch
pull_requests: +10884, 10885
stage:  -> patch review

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

From report at bugs.python.org  Sat Jan  5 20:09:43 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Jan 2019 01:09:43 +0000
Subject: [docs] [issue35649] http.client doesn't close. Infinite loop
In-Reply-To: <1546533708.33.0.81545579375.issue35649@roundup.psfhosted.org>
Message-ID: <1546736983.58.0.479457149249.issue35649@roundup.psfhosted.org>


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


----------
keywords: +patch, patch, patch
pull_requests: +10884, 10885, 10887
stage:  -> patch review

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

From report at bugs.python.org  Sat Jan  5 20:09:50 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Jan 2019 01:09:50 +0000
Subject: [docs] [issue35649] http.client doesn't close. Infinite loop
In-Reply-To: <1546533708.33.0.81545579375.issue35649@roundup.psfhosted.org>
Message-ID: <1546736990.35.0.053353655197.issue35649@roundup.psfhosted.org>


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


----------
keywords: +patch, patch, patch, patch
pull_requests: +10884, 10885, 10886, 10887
stage:  -> patch review

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

From report at bugs.python.org  Sat Jan  5 21:34:49 2019
From: report at bugs.python.org (Caleb Hattingh)
Date: Sun, 06 Jan 2019 02:34:49 +0000
Subject: [docs] [issue30487] DOC: automatically create a venv and install
 Sphinx when running make
In-Reply-To: <1495817388.46.0.640927890572.issue30487@psf.upfronthosting.co.za>
Message-ID: <1546742085.05.0.236214046067.issue30487@roundup.psfhosted.org>


Caleb Hattingh <caleb.hattingh at gmail.com> added the comment:

@cheryl.sabella I am ok with closing this, but the original motivation for this work was from @zack.ware so he should weigh in.

I am not going to work on this any further for the forseeable future (I've got my hands full already with the asyncio docs I'm trying to write in #34831).

----------

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

From report at bugs.python.org  Sat Jan  5 21:37:47 2019
From: report at bugs.python.org (Caleb Hattingh)
Date: Sun, 06 Jan 2019 02:37:47 +0000
Subject: [docs] [issue34831] Asyncio Tutorial
In-Reply-To: <1538134577.09.0.545547206417.issue34831@psf.upfronthosting.co.za>
Message-ID: <1546742261.51.0.759363068031.issue34831@roundup.psfhosted.org>


Caleb Hattingh <caleb.hattingh at gmail.com> added the comment:

A quick note to say I have not abandoned this, it's just that life got complicated for me in late 2018. I intend to pick up progress again within the next month or two.

----------

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

From report at bugs.python.org  Sun Jan  6 09:05:35 2019
From: report at bugs.python.org (R. David Murray)
Date: Sun, 06 Jan 2019 14:05:35 +0000
Subject: [docs] [issue35625] Comprehension doc doesn't mention buggy class
 scope behavior
In-Reply-To: <1546253280.49.0.920078772343.issue35625@roundup.psfhosted.org>
Message-ID: <1546783534.21.0.535439624476.issue35625@roundup.psfhosted.org>


Change by R. David Murray <rdmurray at bitdance.com>:


----------
components:  -email
nosy:  -barry, r.david.murray
type: security -> behavior

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

From report at bugs.python.org  Sun Jan  6 09:06:05 2019
From: report at bugs.python.org (R. David Murray)
Date: Sun, 06 Jan 2019 14:06:05 +0000
Subject: [docs] [issue35625] Comprehension doc doesn't mention buggy class
 scope behavior
In-Reply-To: <1546253280.49.0.920078772343.issue35625@roundup.psfhosted.org>
Message-ID: <1546783563.76.0.773433950156.issue35625@roundup.psfhosted.org>


Change by R. David Murray <rdmurray at bitdance.com>:


Removed file: https://bugs.python.org/file48026/keyfile.png

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

From report at bugs.python.org  Sun Jan  6 11:56:31 2019
From: report at bugs.python.org (Ned Deily)
Date: Sun, 06 Jan 2019 16:56:31 +0000
Subject: [docs] [issue30487] DOC: automatically create a venv and install
 Sphinx when running make
In-Reply-To: <1495817388.46.0.640927890572.issue30487@psf.upfronthosting.co.za>
Message-ID: <1546793787.48.0.513419982333.issue30487@roundup.psfhosted.org>


Change by Ned Deily <nad at python.org>:


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

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

From report at bugs.python.org  Sun Jan  6 23:17:49 2019
From: report at bugs.python.org (=?utf-8?b?15DXldeo15kg16jXldeT15HXqNeS?=)
Date: Mon, 07 Jan 2019 04:17:49 +0000
Subject: [docs] [issue35676] class TestCase: docs are not correct
Message-ID: <1546834667.39.0.848001961358.issue35676@roundup.psfhosted.org>


New submission from ???? ?????? <uri at speedy.net>:

I think some functions of `class TestCase` are not documented correctly in the docs. For example in https://docs.python.org/3.5/library/unittest.html and also https://docs.python.org/3.6/library/unittest.html and https://docs.python.org/3.7/library/unittest.html.

Some of the functions which are not documented correctly:

assertListEqual
assertSetEqual
assertDictEqual
assertIsNone

And many other functions.

You can see some more details on https://github.com/python/typeshed/issues/2716.

----------
assignee: docs at python
components: Documentation
messages: 333137
nosy: docs at python, ???? ??????
priority: normal
severity: normal
status: open
title: class TestCase: docs are not correct
versions: Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Sun Jan  6 23:27:45 2019
From: report at bugs.python.org (=?utf-8?b?15DXldeo15kg16jXldeT15HXqNeS?=)
Date: Mon, 07 Jan 2019 04:27:45 +0000
Subject: [docs] [issue35676] class TestCase: docs are not correct
In-Reply-To: <1546834667.39.0.848001961358.issue35676@roundup.psfhosted.org>
Message-ID: <1546835263.74.0.800251992216.issue35676@roundup.psfhosted.org>


???? ?????? <uri at speedy.net> added the comment:

1. I think the main problem is where it's documented "first, second" while the real argument names are different.

2. I think maybe https://docs.python.org/2.7/library/unittest.html is also affected in functions such as:

assertGreater(first, second, msg=None)
assertGreaterEqual(first, second, msg=None)
assertLess(first, second, msg=None)
assertLessEqual(first, second, msg=None)

----------
versions: +Python 2.7

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

From report at bugs.python.org  Sun Jan  6 23:30:17 2019
From: report at bugs.python.org (=?utf-8?b?15DXldeo15kg16jXldeT15HXqNeS?=)
Date: Mon, 07 Jan 2019 04:30:17 +0000
Subject: [docs] [issue35676] class TestCase: docs are not correct
In-Reply-To: <1546834667.39.0.848001961358.issue35676@roundup.psfhosted.org>
Message-ID: <1546835417.21.0.978175856242.issue35676@roundup.psfhosted.org>


Change by ???? ?????? <uri at speedy.net>:


----------
versions: +Python 3.4, Python 3.8

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

From pedro.mendes at gmx.com  Sun Jan  6 17:10:07 2019
From: pedro.mendes at gmx.com (Pedro MENDES)
Date: Sun, 6 Jan 2019 23:10:07 +0100
Subject: [docs] 404 Not Found : Download Python 3.7.2 Documentation
Message-ID: <929e1840-abce-b368-3f28-f5f9d42ac2aa@gmx.com>

Hi Team ;)

For information purposes and trying to download packet from /Python>> 
French - 3.7.2 Documentation/(https://docs.python.org/fr/3/download.html)
many packets, when we try to download them, indicate 404 Not Found :

PDF (US-Letter paper size)? [all packets]
PDF (A4 paper size) [all packets]
EPUB [all packets]

Regards

Pedro



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190106/71277b27/attachment.html>

From shicanwei at jingmeiti.com  Mon Jan  7 01:48:37 2019
From: shicanwei at jingmeiti.com (shicanwei at jingmeiti.com)
Date: Mon, 7 Jan 2019 14:48:37 +0800
Subject: [docs] =?gb2312?b?c2NoZWQgoaogRXZlbnQgc2NoZWR1bGVyIKGqIFB5dGhv?=
 =?gb2312?b?biAzLjcuMiBkb2N1bWVudGF0aW9u?=
Message-ID: <2019010714483664387812@jingmeiti.com>+E5027203D18B062C

your example is wrong, "priority small do first"





https://docs.python.org/3/library/sched.html



my execution is like below:


shicanwei at jingmeiti.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190107/fec0c83b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Catch.jpg
Type: image/jpeg
Size: 133185 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190107/fec0c83b/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Catch1A6C.jpg
Type: image/jpeg
Size: 188208 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190107/fec0c83b/attachment-0003.jpg>

From report at bugs.python.org  Mon Jan  7 08:38:31 2019
From: report at bugs.python.org (Jonathan Fine)
Date: Mon, 07 Jan 2019 13:38:31 +0000
Subject: [docs] [issue34431] Docs does not eval allows code object as
 argument
In-Reply-To: <1534608199.83.0.56676864532.issue34431@psf.upfronthosting.co.za>
Message-ID: <1546868307.44.0.748857017861.issue34431@roundup.psfhosted.org>


Jonathan Fine <jfine2358 at gmail.com> added the comment:

This graceful reminder is most welcome. At present, it's not help I'm short of, but time. I've given myself a reminder, to spend time on this before the end of this month (January 2019).

Once again, thank you for this reminder. This is something I want to do. It would be my first Python contribution.

----------

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

From report at bugs.python.org  Mon Jan  7 10:16:00 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 07 Jan 2019 15:16:00 +0000
Subject: [docs] [issue35676] unittest assert helper methods have incorrect
 signature in docs
In-Reply-To: <1546834667.39.0.848001961358.issue35676@roundup.psfhosted.org>
Message-ID: <1546874159.21.0.525046637236.issue35676@roundup.psfhosted.org>


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

Thanks for the report. Looking at git history it seems there were some changes done in issue10573 to use (actual, expected) for consistency and later changed to use (first, second) in the same issue at msg126911. Discussion for the issue : https://mail.python.org/pipermail/python-dev/2010-December/106875.html

I think this is a bug as seen from typeshed https://github.com/python/typeshed/pull/2724/. But I will defer it to the maintainer to take a call on the same given there was a discussion in the past.

Removing versions that are on security fix only mode. I am changing the subject. Feel free to reword/revert.

----------
nosy: +ezio.melotti, xtreak
title: class TestCase: docs are not correct -> unittest assert helper methods have incorrect signature in docs
versions:  -Python 3.4, Python 3.5, Python 3.6

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

From report at bugs.python.org  Mon Jan  7 18:09:06 2019
From: report at bugs.python.org (Tatz Sekine)
Date: Mon, 07 Jan 2019 23:09:06 +0000
Subject: [docs] [issue35681] urllib.request.HTTPPasswordMgr.add_password
 requires more information for HTTPPasswordMgrWithDefaultRealm
Message-ID: <1546902543.15.0.573868900421.issue35681@roundup.psfhosted.org>


New submission from Tatz Sekine <tsekine at google.com>:

TL;DR
  HTTPPasswordMgrWithDefaultRealm.add_password() doesn't have proper documentation.

All known version of urllib.request (or urllib2 in Python 2.x) documentaion have the same issue.

Details:

HTTPPasswordMgrWithDefaultRealm object doesn't have its own documentation. Instead of that, HTTPPasswordMgr's doc have information for those 2 objects:
https://docs.python.org/3.8/library/urllib.request.html?highlight=httppasswordmgr#http-password-mgr

Both objects have just 2 functions: add_password() and find_user_password(). The doc for find_user_password() has explanation how different between those 2 objects, while the one for add_password() doesn't.

One of the missing explanation for HTTPPasswordMgrWithDefaultRealm.add_passowrd() is the value of realm. The document has now "realm, user and passwd must be strings.", but realm could be None for HTTPPasswordMgrWithDefaultRealm, to set default realm-less password.

That's typical use case of HTTPPasswordMgrWithDefaultRealm.add_password(), or, that's exactly urllib howto doc mentions in
 https://docs.python.org/3.8/howto/urllib2.html?highlight=httppasswordmgrwithdefaultrealm

Conclusion:

So, documentation of HTTPPasswordMgr.add_passoword() should have additional explanation for realm which could be None for HTTPPasswordMgrWithDefaultRealm. Or, HTTPPasswordMgrWithDefaultRealm objects could have independent section from HTTPPasswordMgr, to clarify its usage.

Why is this matter?
  Typeshed (https://github.com/python/typeshed) depends on the doc. I (or somebody else in the company) will report it separately.

----------
assignee: docs at python
components: Documentation
messages: 333189
nosy: docs at python, tsekine
priority: normal
severity: normal
status: open
title: urllib.request.HTTPPasswordMgr.add_password requires more information for HTTPPasswordMgrWithDefaultRealm
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Jan  7 21:57:37 2019
From: report at bugs.python.org (Steve Dower)
Date: Tue, 08 Jan 2019 02:57:37 +0000
Subject: [docs] [issue35374] Windows doc build does not find autodetected
 hhc.exe
In-Reply-To: <1543743728.61.0.788709270274.issue35374@psf.upfronthosting.co.za>
Message-ID: <1546916255.03.0.399443171911.issue35374@roundup.psfhosted.org>


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


New changeset e61cc481e02b758c8d8289163102c236d0658a55 by Steve Dower (chrullrich) in branch 'master':
bpo-35374: Avoid trailing space in hhc file name if found on PATH. (GH-10849)
https://github.com/python/cpython/commit/e61cc481e02b758c8d8289163102c236d0658a55


----------

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

From report at bugs.python.org  Mon Jan  7 21:58:10 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Jan 2019 02:58:10 +0000
Subject: [docs] [issue35374] Windows doc build does not find autodetected
 hhc.exe
In-Reply-To: <1543743728.61.0.788709270274.issue35374@psf.upfronthosting.co.za>
Message-ID: <1546916289.25.0.531938321206.issue35374@roundup.psfhosted.org>


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


----------
pull_requests: +10950

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

From report at bugs.python.org  Mon Jan  7 21:58:22 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Jan 2019 02:58:22 +0000
Subject: [docs] [issue35374] Windows doc build does not find autodetected
 hhc.exe
In-Reply-To: <1543743728.61.0.788709270274.issue35374@psf.upfronthosting.co.za>
Message-ID: <1546916301.05.0.144934018896.issue35374@roundup.psfhosted.org>


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


----------
pull_requests: +10950, 10951

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

From report at bugs.python.org  Mon Jan  7 21:58:32 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Jan 2019 02:58:32 +0000
Subject: [docs] [issue35374] Windows doc build does not find autodetected
 hhc.exe
In-Reply-To: <1543743728.61.0.788709270274.issue35374@psf.upfronthosting.co.za>
Message-ID: <1546916311.17.0.416184042143.issue35374@roundup.psfhosted.org>


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


----------
pull_requests: +10950, 10951, 10952

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

From report at bugs.python.org  Mon Jan  7 22:04:19 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 08 Jan 2019 03:04:19 +0000
Subject: [docs] [issue35374] Windows doc build does not find autodetected
 hhc.exe
In-Reply-To: <1543743728.61.0.788709270274.issue35374@psf.upfronthosting.co.za>
Message-ID: <1546916657.26.0.319496248337.issue35374@roundup.psfhosted.org>


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


New changeset 5d1e0124cf562153a681d1b5b362e7c8e23edea9 by Miss Islington (bot) in branch '3.7':
bpo-35374: Avoid trailing space in hhc file name if found on PATH. (GH-10849)
https://github.com/python/cpython/commit/5d1e0124cf562153a681d1b5b362e7c8e23edea9


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

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

From report at bugs.python.org  Mon Jan  7 22:23:10 2019
From: report at bugs.python.org (Steve Dower)
Date: Tue, 08 Jan 2019 03:23:10 +0000
Subject: [docs] [issue35374] Windows doc build does not find autodetected
 hhc.exe
In-Reply-To: <1543743728.61.0.788709270274.issue35374@psf.upfronthosting.co.za>
Message-ID: <1546917789.15.0.120566385136.issue35374@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/issue35374>
_______________________________________

From report at bugs.python.org  Tue Jan  8 07:37:59 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Tue, 08 Jan 2019 12:37:59 +0000
Subject: [docs] [issue35685] Add samples on patch.dict of the use of
 decorator and in class
Message-ID: <1546951077.39.0.591357222806.issue35685@roundup.psfhosted.org>


New submission from Emmanuel Arias <emmanuelarias30 at gmail.com>:

Hi!

I create this PR to add a samples of the use of patch.dict with decorator on method and class. I think that is a good improve because the doc mentions the use of patch.dict with decorator on method and class but don't show any samples. 

Other, question, why on unittest.mock documentation is used `assert *something* == *something*` and it is not used the assertEquals (and others)? IMHO this would be better for unittest docs.

Regards

----------
assignee: docs at python
components: Documentation
messages: 333226
nosy: docs at python, eamanu, michael.foord
priority: normal
severity: normal
status: open
title: Add samples on patch.dict of the use of decorator and in class
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Tue Jan  8 07:43:18 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Tue, 08 Jan 2019 12:43:18 +0000
Subject: [docs] [issue35685] Add samples on patch.dict of the use of
 decorator and in class
In-Reply-To: <1546951077.39.0.591357222806.issue35685@roundup.psfhosted.org>
Message-ID: <1546951398.56.0.727340780339.issue35685@roundup.psfhosted.org>


Change by Emmanuel Arias <emmanuelarias30 at gmail.com>:


----------
keywords: +patch
pull_requests: +10959
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan  8 07:43:26 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Tue, 08 Jan 2019 12:43:26 +0000
Subject: [docs] [issue35685] Add samples on patch.dict of the use of
 decorator and in class
In-Reply-To: <1546951077.39.0.591357222806.issue35685@roundup.psfhosted.org>
Message-ID: <1546951406.13.0.938471905479.issue35685@roundup.psfhosted.org>


Change by Emmanuel Arias <emmanuelarias30 at gmail.com>:


----------
keywords: +patch, patch
pull_requests: +10959, 10960
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan  8 07:43:32 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Tue, 08 Jan 2019 12:43:32 +0000
Subject: [docs] [issue35685] Add samples on patch.dict of the use of
 decorator and in class
In-Reply-To: <1546951077.39.0.591357222806.issue35685@roundup.psfhosted.org>
Message-ID: <1546951412.4.0.0521597134624.issue35685@roundup.psfhosted.org>


Change by Emmanuel Arias <emmanuelarias30 at gmail.com>:


----------
keywords: +patch, patch, patch
pull_requests: +10959, 10960, 10961
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan  8 14:03:20 2019
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 08 Jan 2019 19:03:20 +0000
Subject: [docs] [issue35676] unittest assert helper methods have incorrect
 signature in docs
In-Reply-To: <1546834667.39.0.848001961358.issue35676@roundup.psfhosted.org>
Message-ID: <1546974200.0.0.376113190092.issue35676@roundup.psfhosted.org>


Change by Brett Cannon <brett at python.org>:


----------
nosy: +michael.foord, rbcollins

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

From report at bugs.python.org  Wed Jan  9 17:52:29 2019
From: report at bugs.python.org (Brian Curtin)
Date: Wed, 09 Jan 2019 22:52:29 +0000
Subject: [docs] [issue35404] Document how to import _structure in
 email.message
In-Reply-To: <1543914095.32.0.788709270274.issue35404@psf.upfronthosting.co.za>
Message-ID: <1547074343.44.0.345231580025.issue35404@roundup.psfhosted.org>


Brian Curtin <brian at python.org> added the comment:


New changeset e394ba32147f687b6bc7518d461f1d84211698e0 by Brian Curtin (Charles-Axel Dein) in branch 'master':
bpo-35404: Clarify how to import _structure in email.message doc (GH-10886)
https://github.com/python/cpython/commit/e394ba32147f687b6bc7518d461f1d84211698e0


----------
nosy: +brian.curtin

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

From zzxening at gmail.com  Thu Jan 10 07:29:06 2019
From: zzxening at gmail.com (=?UTF-8?B?5byg55u45oGp?=)
Date: Thu, 10 Jan 2019 20:29:06 +0800
Subject: [docs] Feedback on the error page
Message-ID: <CAFQSybrvtNPNtMUfpkdpxpUtVY_rDJXtDAJt6EfPkFHvZiDXJA@mail.gmail.com>

     I am a Python enthusiast from China. I have been studying this manual
recently, but I found a problem and hope to solve it as soon as possible.
The problem bothering me. I believe it will also plague other beginners.
       This is url ?
https://docs.python.org/zh-cn/3.7/archives/python-3.7.2-docs-pdf-a4.zip
       wrong description? 404 Not Found
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190110/ad6cb9f2/attachment.html>

From julien at palard.fr  Thu Jan 10 08:45:13 2019
From: julien at palard.fr (Julien Palard)
Date: Thu, 10 Jan 2019 13:45:13 +0000
Subject: [docs] Feedback on the error page
In-Reply-To: <CAFQSybrvtNPNtMUfpkdpxpUtVY_rDJXtDAJt6EfPkFHvZiDXJA@mail.gmail.com>
References: <CAFQSybrvtNPNtMUfpkdpxpUtVY_rDJXtDAJt6EfPkFHvZiDXJA@mail.gmail.com>
Message-ID: <Shm5AgdNyrkIGp_r0dUevsrA9AIbcJ-_DaCTvkl-998o-80VuEFVsZigLz4SPzH4NfPaKlk6pQti3nE1XsZ8PWuYsQHd0AoypFNUXRjv6a0=@palard.fr>

Hi, thanks for the feedback.

> I found a problem and hope to solve it as soon as possible. The problem bothering me. I believe it will also plague other beginners.

This is a known issue (https://github.com/python/psf-salt/issues/145 / https://github.com/python/python-docs-fr/issues/199).

I'm having a full build from yesterday on my laptop I have to upload manually to temporary fix it, did't had time to upload it yet, maybe this night (UTC+2).

Bests,
--
Julien Palard
https://mdk.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190110/baaa2ba1/attachment.html>

From midalist at gmail.com  Thu Jan 10 08:56:07 2019
From: midalist at gmail.com (=?utf-8?Q?Micha=C5=82_Listowski?=)
Date: Thu, 10 Jan 2019 14:56:07 +0100
Subject: [docs] EPUB Version is too big.
Message-ID: <0FCC1513-A89D-4952-AF4E-3F58B1BCDD48@gmail.com>

Hello
I believe that you should cut epub file in parts like PDF. This one file is almost unreadable for most of readers like Pocketbook or 
Kindle (after convert to mobi).
When i open on PocketBook Inkpad 3 it shows me that file have 5500+ pages, even start to change pages is really difficuld for device.
I think on tablets it's not a big problem because CPU in them are faster.

Thanks a lot for your work and response
Micha? Listowski

From report at bugs.python.org  Thu Jan 10 17:42:14 2019
From: report at bugs.python.org (Dan Snider)
Date: Thu, 10 Jan 2019 22:42:14 +0000
Subject: [docs] [issue35714] Document that the null character '\0'
 terminates a struct format spec
Message-ID: <1547160130.27.0.885629506261.issue35714@roundup.psfhosted.org>


New submission from Dan Snider <mr.assume.away at gmail.com>:

ie.:
    >>> from struct import calcsize
    >>> calcsize('\144\u0064\000xf\U00000031000\60d\121\U00000051')
    16

I'm sure some people think it's obvious or even expect the null character to signal EOF but it probably isn't obvious at all to those without experience in lower level languages. It actually seems like Python goes out of its way to make sure everything treats the null character no more special than the letter "H", which is good.

At first glance I'd think something like this was just another trivial quirk of the language and not bring it up, but because the documentation doesn't mention it I actually got stuck on something related for half an hour when unit testing some dynamically generated format specs. 

Without going into unnecessary detail, what happened was that a typo in another tangentially related part of the test was enabling the generation of a rogue null byte. I'm bad at those "find face in the crowd" puzzles and this was hardly different, being literally camouflaged within a 300 character format spec containing a random mixture of escaped and non-escaped source characters in the forms: \Uffffffff, \uffff, \777, \xff, \x00, + latin/ascii.

If I'm not the only one who sees this as a slightly bigger deal than poor documentation, the fix is trivial with an extra call to PyBytes_GET_SIZE when null is found. But just because I can't think of a use case in allowing the null character to precede other characters in the format string doesn't mean there isn't one, which is why only documentation is currently selected.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 333424
nosy: bup, docs at python
priority: normal
severity: normal
status: open
title: Document that the null character '\0' terminates a struct format spec
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Jan 10 20:03:30 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Fri, 11 Jan 2019 01:03:30 +0000
Subject: [docs] [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: <1547168607.96.0.245850146428.issue35714@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

I'm not sure whether having NULLs terminate a struct format string is a feature or a bug.

Given that nearly every other string in Python treat NULLs as ordinary characters, I'm inclined to say this is a bug. Or at least an unnecessary restriction that ought to be lifted.

----------
nosy: +steven.daprano
type:  -> behavior

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

From report at bugs.python.org  Fri Jan 11 01:02:09 2019
From: report at bugs.python.org (Jorge Ramos)
Date: Fri, 11 Jan 2019 06:02:09 +0000
Subject: [docs] [issue35156] Consider revising documentation on Python
 Builds from source
In-Reply-To: <1541288069.11.0.788709270274.issue35156@psf.upfronthosting.co.za>
Message-ID: <1547186529.15.0.420515615937.issue35156@roundup.psfhosted.org>


Change by Jorge Ramos <neyuru at gmail.com>:


----------
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Jan 11 02:28:17 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Jan 2019 07:28:17 +0000
Subject: [docs] [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: <1547191695.01.0.672572906735.issue35714@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:

I think the null character is illegal character in the format string, and struct functions should raise a struct.error for it.

----------
nosy: +serhiy.storchaka

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

From report at bugs.python.org  Fri Jan 11 04:32:51 2019
From: report at bugs.python.org (Ricardo Fraile)
Date: Fri, 11 Jan 2019 09:32:51 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
Message-ID: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>


New submission from Ricardo Fraile <rfraile at rfraile.eu>:

Add macOS to CLOCK_MONOTONIC_RAW description because it is already available since 10.12.

----------
assignee: docs at python
components: Documentation
files: 001.patch
keywords: patch
messages: 333445
nosy: docs at python, rfrail3, vstinner
priority: normal
severity: normal
status: open
title: CLOCK_MONOTONIC_RAW available on macOS
type: enhancement
Added file: https://bugs.python.org/file48041/001.patch

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

From report at bugs.python.org  Fri Jan 11 05:18:44 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Jan 2019 10:18:44 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547201924.75.0.857445712737.issue35716@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at redhat.com>:


----------
components: +macOS
nosy: +ned.deily, ronaldoussoren

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

From report at bugs.python.org  Fri Jan 11 05:22:51 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Jan 2019 10:22:51 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547202169.47.0.596869163588.issue35716@roundup.psfhosted.org>


STINNER Victor <vstinner at redhat.com> added the comment:

Ronald, Ned: What is the macOS version used to build Python binaries distributed on python.org? Do we get the constant on macOS 10.12 if binaries are built on macOS 10.11 for example?

I guess that people building Python from source like hombrew will get the constant.

Joannah: Can you please convert attached patch into a pull request? Please mention Ricardo Fraile as co-author of the change (mention his name in the commit message). Such change doesn't need to be mentioned in the changelog (no NEWS entry needed).

----------
nosy: +nanjekyejoannah

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

From report at bugs.python.org  Fri Jan 11 05:47:19 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 11 Jan 2019 10:47:19 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547203639.35.0.53926776399.issue35716@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


----------
pull_requests: +11086
stage:  -> patch review

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

From report at bugs.python.org  Fri Jan 11 05:47:32 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 11 Jan 2019 10:47:32 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547203652.96.0.662423383636.issue35716@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


----------
pull_requests: +11086, 11087
stage:  -> patch review

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

From report at bugs.python.org  Fri Jan 11 05:47:46 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 11 Jan 2019 10:47:46 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547203666.22.0.412102599774.issue35716@roundup.psfhosted.org>


Change by Joannah Nanjekye <nanjekyejoannah at gmail.com>:


----------
pull_requests: +11086, 11087, 11088
stage:  -> patch review

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

From report at bugs.python.org  Fri Jan 11 05:51:29 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 11 Jan 2019 10:51:29 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547203887.92.0.434271785136.issue35716@roundup.psfhosted.org>


Joannah Nanjekye <nanjekyejoannah at gmail.com> added the comment:

@vstinner I have created the PR for this.

----------

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

From report at bugs.python.org  Fri Jan 11 06:01:12 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Jan 2019 11:01:12 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547204470.73.0.427682311059.issue35716@roundup.psfhosted.org>


STINNER Victor <vstinner at redhat.com> added the comment:

@Ricardo: Can you please give you email address? It's to credit you in the commit message. (You don't have to, it's up to you to share it or not :-))

----------

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

From report at bugs.python.org  Fri Jan 11 06:32:00 2019
From: report at bugs.python.org (Ricardo Fraile)
Date: Fri, 11 Jan 2019 11:32:00 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547206319.11.0.352078425574.issue35716@roundup.psfhosted.org>


Ricardo Fraile <rfraile at rfraile.eu> added the comment:

@vstinner here you have rfraile at rfraile.eu :)

----------

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

From report at bugs.python.org  Fri Jan 11 07:15:38 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 11 Jan 2019 12:15:38 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547208937.21.0.399393187078.issue35716@roundup.psfhosted.org>


Joannah Nanjekye <nanjekyejoannah at gmail.com> added the comment:

@Ricardo, Thanks, commit message updated.

----------

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

From report at bugs.python.org  Fri Jan 11 08:20:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Jan 2019 13:20:00 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547212799.67.0.33362085158.issue35716@roundup.psfhosted.org>


STINNER Victor <vstinner at redhat.com> added the comment:


New changeset fd7d539be3ce1cc098a4f104b7a7816ca00add16 by Victor Stinner (Joannah Nanjekye) in branch 'master':
bpo-35716: Update time.CLOCK_MONOTONIC_RAW doc (GH-11517)
https://github.com/python/cpython/commit/fd7d539be3ce1cc098a4f104b7a7816ca00add16


----------

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

From report at bugs.python.org  Fri Jan 11 08:26:21 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 11 Jan 2019 13:26:21 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547213181.62.0.165781854085.issue35716@roundup.psfhosted.org>


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


----------
pull_requests: +11089

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

From report at bugs.python.org  Fri Jan 11 08:26:30 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 11 Jan 2019 13:26:30 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547213190.37.0.241467500143.issue35716@roundup.psfhosted.org>


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


----------
pull_requests: +11089, 11090

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

From report at bugs.python.org  Fri Jan 11 08:26:41 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 11 Jan 2019 13:26:41 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547213201.42.0.420763755138.issue35716@roundup.psfhosted.org>


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


----------
pull_requests: +11089, 11090, 11091

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

From report at bugs.python.org  Fri Jan 11 08:32:15 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 11 Jan 2019 13:32:15 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547213534.05.0.158175057443.issue35716@roundup.psfhosted.org>


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


New changeset 8a5b1aa98f97923c39734b508aead152a5a1c911 by Miss Islington (bot) in branch '3.7':
bpo-35716: Update time.CLOCK_MONOTONIC_RAW doc (GH-11517)
https://github.com/python/cpython/commit/8a5b1aa98f97923c39734b508aead152a5a1c911


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

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

From report at bugs.python.org  Fri Jan 11 08:33:40 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 11 Jan 2019 13:33:40 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547213618.67.0.282070551757.issue35716@roundup.psfhosted.org>


STINNER Victor <vstinner at redhat.com> added the comment:

Thanks Joannah Nanjekye for the PR. I rewrote the commit message to format properly the co-authored-by tag. The doc has been updated in 3.7 and master.

Ricardo Fraile: *Please*. Don't use this clock :-) It must not be used except if you really understand well what you are doing :-)

https://www.python.org/dev/peps/pep-0418/#clock-monotonic-clock-monotonic-raw-clock-boottime

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Jan 11 09:44:18 2019
From: report at bugs.python.org (Ronald Oussoren)
Date: Fri, 11 Jan 2019 14:44:18 +0000
Subject: [docs] [issue35716] CLOCK_MONOTONIC_RAW available on macOS
In-Reply-To: <1547199168.5.0.0198252527214.issue35716@roundup.psfhosted.org>
Message-ID: <1547217856.1.0.653346087627.issue35716@roundup.psfhosted.org>


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

Victor, the binaries are build on the macOS version mentioned in the download. That is, the modern 64-bit installers are build on macOS 10.9 with the 10.9 SDK, the older 32/64-bit intel installers are build on macOS 10.6 with the 10.6 SDK.

With some work it should be possible to build the 64-bit installer on newer macOS releases, but that requires some work to ensure the code deals well with weakly linked symbols.  I've added such support in the past for older macOS releases, so this is definitely doable.  I'd love to work on this, but don't know when I'll have time to do so.

BTW. I'm pretty sure there's an issue about this, but cannot find it at the moment.

----------

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

From SCHUAH003 at e.ntu.edu.sg  Sat Jan 12 01:14:19 2019
From: SCHUAH003 at e.ntu.edu.sg (#CHUAH SHEOU SHUANG#)
Date: Sat, 12 Jan 2019 06:14:19 +0000
Subject: [docs] Report bugs on the leaps year
Message-ID: <SL2PR01MB26684A1AE3038DA3EA8D15D489860@SL2PR01MB2668.apcprd01.prod.exchangelabs.com>


Dear Sir/Madam,

[cid:image002.png at 01D4AA81.1B676110]

I accidentally found out that for years 1700, 1800, and 1900, they should be leaps year but then it shows that it has 28 days on February.

Best Regards,
Sheou Shuang.

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190112/7107e544/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: E91D7E1BC79A4EF98AB146BC05A2EA87.png
Type: image/png
Size: 105638 bytes
Desc: E91D7E1BC79A4EF98AB146BC05A2EA87.png
URL: <http://mail.python.org/pipermail/docs/attachments/20190112/7107e544/attachment-0001.png>

From report at bugs.python.org  Sat Jan 12 12:22:01 2019
From: report at bugs.python.org (Tal Einat)
Date: Sat, 12 Jan 2019 17:22:01 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547313717.1.0.0619800896693.issue34512@roundup.psfhosted.org>


Tal Einat <taleinat at gmail.com> added the comment:


New changeset 1cffd0eed313011c0c2bb071c8affeb4a7ed05c7 by Tal Einat (Alexey Izbyshev) in branch 'master':
bpo-34512: Document platform-specific strftime() behavior for non-ASCII format strings (GH-8948)
https://github.com/python/cpython/commit/1cffd0eed313011c0c2bb071c8affeb4a7ed05c7


----------

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

From report at bugs.python.org  Sat Jan 12 12:22:29 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Jan 2019 17:22:29 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547313747.46.0.302068806672.issue34512@roundup.psfhosted.org>


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


----------
pull_requests: +11134

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

From report at bugs.python.org  Sat Jan 12 12:22:42 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Jan 2019 17:22:42 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547313761.07.0.682864187417.issue34512@roundup.psfhosted.org>


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


----------
pull_requests: +11134, 11135

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

From report at bugs.python.org  Sat Jan 12 12:22:56 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Jan 2019 17:22:56 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547313774.45.0.812869613145.issue34512@roundup.psfhosted.org>


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


----------
pull_requests: +11134, 11135, 11136

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

From report at bugs.python.org  Sat Jan 12 12:23:09 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Jan 2019 17:23:09 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547313787.83.0.563419235834.issue34512@roundup.psfhosted.org>


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


----------
pull_requests: +11134, 11135, 11136, 11137

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

From report at bugs.python.org  Sat Jan 12 12:23:22 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Jan 2019 17:23:22 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547313801.12.0.734381205754.issue34512@roundup.psfhosted.org>


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


----------
pull_requests: +11135, 11136, 11137, 11139

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

From report at bugs.python.org  Sat Jan 12 12:23:34 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Jan 2019 17:23:34 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547313812.67.0.100231909302.issue34512@roundup.psfhosted.org>


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


----------
pull_requests: +11135, 11136, 11137, 11138, 11139

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

From report at bugs.python.org  Sat Jan 12 12:27:36 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Jan 2019 17:27:36 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547314052.6.0.508680920545.issue34512@roundup.psfhosted.org>


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


New changeset 678c5c07521caca809b1356d954975e6234c49ae by Miss Islington (bot) in branch '3.7':
bpo-34512: Document platform-specific strftime() behavior for non-ASCII format strings (GH-8948)
https://github.com/python/cpython/commit/678c5c07521caca809b1356d954975e6234c49ae


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

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

From report at bugs.python.org  Sat Jan 12 12:28:11 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 12 Jan 2019 17:28:11 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547314088.87.0.0180252490557.issue34512@roundup.psfhosted.org>


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


New changeset 77b80c956f39df34722bd8646cf5b83d149832c4 by Miss Islington (bot) in branch '2.7':
bpo-34512: Document platform-specific strftime() behavior for non-ASCII format strings (GH-8948)
https://github.com/python/cpython/commit/77b80c956f39df34722bd8646cf5b83d149832c4


----------

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

From report at bugs.python.org  Sat Jan 12 12:46:54 2019
From: report at bugs.python.org (Tal Einat)
Date: Sat, 12 Jan 2019 17:46:54 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547315212.27.0.864390871812.issue34512@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests:  -11135

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

From report at bugs.python.org  Sat Jan 12 12:47:09 2019
From: report at bugs.python.org (Tal Einat)
Date: Sat, 12 Jan 2019 17:47:09 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547315227.9.0.954819569285.issue34512@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests:  -11135, 11137

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

From report at bugs.python.org  Sat Jan 12 12:47:23 2019
From: report at bugs.python.org (Tal Einat)
Date: Sat, 12 Jan 2019 17:47:23 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547315241.72.0.709658056717.issue34512@roundup.psfhosted.org>


Change by Tal Einat <taleinat at gmail.com>:


----------
pull_requests:  -11135, 11137, 11139

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

From report at bugs.python.org  Sat Jan 12 12:48:29 2019
From: report at bugs.python.org (Tal Einat)
Date: Sat, 12 Jan 2019 17:48:29 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547315307.24.0.427633157077.issue34512@roundup.psfhosted.org>


Change by Tal Einat <taleinat 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/issue34512>
_______________________________________

From zachary.ware+pydocs at gmail.com  Sat Jan 12 12:59:03 2019
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Sat, 12 Jan 2019 11:59:03 -0600
Subject: [docs] Report bugs on the leaps year
In-Reply-To: <SL2PR01MB26684A1AE3038DA3EA8D15D489860@SL2PR01MB2668.apcprd01.prod.exchangelabs.com>
References: <SL2PR01MB26684A1AE3038DA3EA8D15D489860@SL2PR01MB2668.apcprd01.prod.exchangelabs.com>
Message-ID: <CAKJDb-MjmDBANcSy0cL=FqZVAB3YPKe9A3T-i9umVkR4eRHUJw@mail.gmail.com>

On Sat, Jan 12, 2019 at 9:00 AM #CHUAH SHEOU SHUANG#
<SCHUAH003 at e.ntu.edu.sg> wrote:
> Dear Sir/Madam,
>
> I accidentally found out that for years 1700, 1800, and 1900, they should be leaps year but then it shows that it has 28 days on February.

Sorry, but Python has it right here.  In the Gregorian calendar, years
that are divisible by 100 but not divisible by 400 are not leap years.
See https://en.wikipedia.org/wiki/Leap_year#Gregorian_calendar for
more information.

Regards,
-- 
Zach

From SCHUAH003 at e.ntu.edu.sg  Sat Jan 12 13:01:33 2019
From: SCHUAH003 at e.ntu.edu.sg (#CHUAH SHEOU SHUANG#)
Date: Sat, 12 Jan 2019 18:01:33 +0000
Subject: [docs] Report bugs on the leaps year
In-Reply-To: <CAKJDb-MjmDBANcSy0cL=FqZVAB3YPKe9A3T-i9umVkR4eRHUJw@mail.gmail.com>
References: <SL2PR01MB26684A1AE3038DA3EA8D15D489860@SL2PR01MB2668.apcprd01.prod.exchangelabs.com>,
 <CAKJDb-MjmDBANcSy0cL=FqZVAB3YPKe9A3T-i9umVkR4eRHUJw@mail.gmail.com>
Message-ID: <SL2PR01MB2668637B6A9003FE9BE9DEF989860@SL2PR01MB2668.apcprd01.prod.exchangelabs.com>

Thank you so much for the information ?





Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10



________________________________
From: Zachary Ware <zachary.ware+pydocs at gmail.com>
Sent: Sunday, January 13, 2019 1:59:03 AM
To: docs at python.org
Cc: #CHUAH SHEOU SHUANG#
Subject: Re: [docs] Report bugs on the leaps year

On Sat, Jan 12, 2019 at 9:00 AM #CHUAH SHEOU SHUANG#
<SCHUAH003 at e.ntu.edu.sg> wrote:
> Dear Sir/Madam,
>
> I accidentally found out that for years 1700, 1800, and 1900, they should be leaps year but then it shows that it has 28 days on February.

Sorry, but Python has it right here.  In the Gregorian calendar, years
that are divisible by 100 but not divisible by 400 are not leap years.
See https://en.wikipedia.org/wiki/Leap_year#Gregorian_calendar for
more information.

Regards,
--
Zach
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190112/8a6c6679/attachment.html>

From report at bugs.python.org  Sun Jan 13 02:47:36 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 13 Jan 2019 07:47:36 +0000
Subject: [docs] [issue33039] int() and math.trunc don't accept objects that
 only define __index__
In-Reply-To: <1520672231.04.0.467229070634.issue33039@psf.upfronthosting.co.za>
Message-ID: <1547365652.5.0.498996648744.issue33039@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

@R?mi Aye, filling out derived slots is one of the things PyType_Ready does.

This would need a discussion on python-dev before going ahead and doing it though, as the closest equivalent we have to this right now is the "negative" derivation, where overriding __eq__ without overriding __hash__ implicitly marks the derived class as unhashable (look for "type->tp_hash = PyObject_HashNotImplemented;").

----------

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

From report at bugs.python.org  Sun Jan 13 18:18:07 2019
From: report at bugs.python.org (Antoine Wecxsteen)
Date: Sun, 13 Jan 2019 23:18:07 +0000
Subject: [docs] [issue35732] Typo in library/warnings documentation
Message-ID: <1547421481.41.0.571803871053.issue35732@roundup.psfhosted.org>


New submission from Antoine Wecxsteen <antoine at wecxsteen.net>:

Hello,

I believe there's a mistake in the documentation of library/warnings.

https://docs.python.org/3.8/library/warnings.html#warnings.warn

"This function raises an exception if the particular warning issued is changed into an error by the warnings filter see above."

I think "see above" should be enclosed in brackets (or maybe completely removed as there is already a "(see above)" in the same text block).

Regards.

----------
assignee: docs at python
components: Documentation
messages: 333574
nosy: awecx, docs at python, eric.araujo, ezio.melotti, mdk, willingc
priority: normal
severity: normal
status: open
title: Typo in library/warnings documentation
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Jan 13 19:46:43 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Mon, 14 Jan 2019 00:46:43 +0000
Subject: [docs] [issue35732] Typo in library/warnings documentation
In-Reply-To: <1547421481.41.0.571803871053.issue35732@roundup.psfhosted.org>
Message-ID: <1547426799.66.0.86036369396.issue35732@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

That looks like an error indeed. Are you interested on making a PR for fixing this?

----------
nosy: +pablogsal

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

From report at bugs.python.org  Mon Jan 14 03:15:29 2019
From: report at bugs.python.org (Antoine Wecxsteen)
Date: Mon, 14 Jan 2019 08:15:29 +0000
Subject: [docs] [issue35732] Typo in library/warnings documentation
In-Reply-To: <1547421481.41.0.571803871053.issue35732@roundup.psfhosted.org>
Message-ID: <1547453725.9.0.989764464104.issue35732@roundup.psfhosted.org>


Antoine Wecxsteen <antoine at wecxsteen.net> added the comment:

Hello Pablo,

Yes, I'll be happy to make a PR.

I don't think it should be removed after all as, actually, the two "see above" do not refer to the same paragraph ("Warning Categories" and "The Warnings Filter" respectively).

----------

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

From report at bugs.python.org  Mon Jan 14 03:23:29 2019
From: report at bugs.python.org (Antoine Wecxsteen)
Date: Mon, 14 Jan 2019 08:23:29 +0000
Subject: [docs] [issue35732] Typo in library/warnings documentation
In-Reply-To: <1547421481.41.0.571803871053.issue35732@roundup.psfhosted.org>
Message-ID: <1547454208.3.0.852950612864.issue35732@roundup.psfhosted.org>


Change by Antoine Wecxsteen <antoine at wecxsteen.net>:


----------
keywords: +patch
pull_requests: +11171
stage:  -> patch review

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

From report at bugs.python.org  Mon Jan 14 03:23:41 2019
From: report at bugs.python.org (Antoine Wecxsteen)
Date: Mon, 14 Jan 2019 08:23:41 +0000
Subject: [docs] [issue35732] Typo in library/warnings documentation
In-Reply-To: <1547421481.41.0.571803871053.issue35732@roundup.psfhosted.org>
Message-ID: <1547454219.69.0.309457243011.issue35732@roundup.psfhosted.org>


Change by Antoine Wecxsteen <antoine at wecxsteen.net>:


----------
keywords: +patch, patch
pull_requests: +11171, 11172
stage:  -> patch review

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

From report at bugs.python.org  Mon Jan 14 03:23:52 2019
From: report at bugs.python.org (Antoine Wecxsteen)
Date: Mon, 14 Jan 2019 08:23:52 +0000
Subject: [docs] [issue35732] Typo in library/warnings documentation
In-Reply-To: <1547421481.41.0.571803871053.issue35732@roundup.psfhosted.org>
Message-ID: <1547454231.1.0.614123136567.issue35732@roundup.psfhosted.org>


Change by Antoine Wecxsteen <antoine at wecxsteen.net>:


----------
keywords: +patch, patch, patch
pull_requests: +11171, 11172, 11173
stage:  -> patch review

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

From report at bugs.python.org  Mon Jan 14 03:24:04 2019
From: report at bugs.python.org (Antoine Wecxsteen)
Date: Mon, 14 Jan 2019 08:24:04 +0000
Subject: [docs] [issue35732] Typo in library/warnings documentation
In-Reply-To: <1547421481.41.0.571803871053.issue35732@roundup.psfhosted.org>
Message-ID: <1547454243.81.0.297335147906.issue35732@roundup.psfhosted.org>


Change by Antoine Wecxsteen <antoine at wecxsteen.net>:


----------
keywords: +patch, patch, patch, patch
pull_requests: +11171, 11172, 11173, 11174
stage:  -> patch review

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

From report at bugs.python.org  Mon Jan 14 03:28:41 2019
From: report at bugs.python.org (Antoine Wecxsteen)
Date: Mon, 14 Jan 2019 08:28:41 +0000
Subject: [docs] [issue35732] Typo in library/warnings documentation
In-Reply-To: <1547421481.41.0.571803871053.issue35732@roundup.psfhosted.org>
Message-ID: <1547454519.03.0.286140522887.issue35732@roundup.psfhosted.org>


Antoine Wecxsteen <antoine at wecxsteen.net> added the comment:

https://github.com/python/cpython/pull/11549

Reading the dev guide, I see there is actually no need to open an issue for mere typos. I should have made a PR directly...

----------

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

From report at bugs.python.org  Mon Jan 14 05:20:33 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 14 Jan 2019 10:20:33 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
In-Reply-To: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>
Message-ID: <1547461229.21.0.837336739002.issue34512@roundup.psfhosted.org>


STINNER Victor <vstinner at redhat.com> added the comment:

A solution to make time.strftime() more portable would be to split the format string, format each "%xxx" substring separately but don't pass substrings between "%xxx" to strftime(). There is a similar discussion about trailing "%": bpo-35066.

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

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

From report at bugs.python.org  Mon Jan 14 13:56:04 2019
From: report at bugs.python.org (Jayanth Raman)
Date: Mon, 14 Jan 2019 18:56:04 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of three
Message-ID: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>


New submission from Jayanth Raman <raman.jayanth at gmail.com>:

In the Examples section of the timeit documentation, repeat() returns a list of size three.  But the default is now five and the documentation should reflect that.
Thanks.

----------
assignee: docs at python
components: Documentation
messages: 333635
nosy: docs at python, jayanth
priority: normal
severity: normal
status: open
title: Update timeit documentation to reflect default repeat of three
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Mon Jan 14 14:07:45 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 14 Jan 2019 19:07:45 +0000
Subject: [docs] [issue35732] Typo in library/warnings documentation
In-Reply-To: <1547421481.41.0.571803871053.issue35732@roundup.psfhosted.org>
Message-ID: <1547492864.48.0.0867696035675.issue35732@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> Doc: warnings.rst - add links to references

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

From report at bugs.python.org  Mon Jan 14 14:08:40 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 14 Jan 2019 19:08:40 +0000
Subject: [docs] [issue35732] Typo in library/warnings documentation
In-Reply-To: <1547421481.41.0.571803871053.issue35732@roundup.psfhosted.org>
Message-ID: <1547492914.8.0.374640534981.issue35732@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

Closing as a duplicate of #35563, which converts the 'see above' to links.

----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Mon Jan 14 14:12:11 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 14 Jan 2019 19:12:11 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of three
In-Reply-To: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>
Message-ID: <1547493131.74.0.532066734409.issue35738@roundup.psfhosted.org>


Change by Serhiy Storchaka <storchaka+cpython at gmail.com>:


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

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

From report at bugs.python.org  Tue Jan 15 01:18:24 2019
From: report at bugs.python.org (Henry Chen)
Date: Tue, 15 Jan 2019 06:18:24 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of three
In-Reply-To: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>
Message-ID: <1547533104.48.0.89526551028.issue35738@roundup.psfhosted.org>


Change by Henry Chen <tahafut at gmail.com>:


----------
keywords: +patch
pull_requests: +11196
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan 15 01:18:29 2019
From: report at bugs.python.org (Henry Chen)
Date: Tue, 15 Jan 2019 06:18:29 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of three
In-Reply-To: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>
Message-ID: <1547533109.78.0.89131410048.issue35738@roundup.psfhosted.org>


Change by Henry Chen <tahafut at gmail.com>:


----------
keywords: +patch, patch
pull_requests: +11196, 11197
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan 15 01:18:36 2019
From: report at bugs.python.org (Henry Chen)
Date: Tue, 15 Jan 2019 06:18:36 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of three
In-Reply-To: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>
Message-ID: <1547533116.65.0.0488453444812.issue35738@roundup.psfhosted.org>


Change by Henry Chen <tahafut at gmail.com>:


----------
keywords: +patch, patch, patch
pull_requests: +11196, 11197, 11198
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan 15 01:23:17 2019
From: report at bugs.python.org (Henry Chen)
Date: Tue, 15 Jan 2019 06:23:17 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of five
In-Reply-To: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>
Message-ID: <1547533397.29.0.643103399235.issue35738@roundup.psfhosted.org>


Change by Henry Chen <tahafut at gmail.com>:


----------
title: Update timeit documentation to reflect default repeat of three -> Update timeit documentation to reflect default repeat of five

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

From report at bugs.python.org  Tue Jan 15 05:29:25 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Jan 2019 10:29:25 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of five
In-Reply-To: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>
Message-ID: <1547548163.88.0.220139027028.issue35738@roundup.psfhosted.org>


Serhiy Storchaka <storchaka+cpython at gmail.com> added the comment:


New changeset 06f8b57212b2e2cd2e63af36cecdfa3075b324a2 by Serhiy Storchaka (Henry Chen) in branch 'master':
bpo-35738: Update the example for timer.Timer.repeat(). (GH-11559)
https://github.com/python/cpython/commit/06f8b57212b2e2cd2e63af36cecdfa3075b324a2


----------
nosy: +serhiy.storchaka

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

From report at bugs.python.org  Tue Jan 15 05:29:42 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 15 Jan 2019 10:29:42 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of five
In-Reply-To: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>
Message-ID: <1547548182.02.0.992075243943.issue35738@roundup.psfhosted.org>


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


----------
pull_requests: +11208

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

From report at bugs.python.org  Tue Jan 15 05:29:48 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 15 Jan 2019 10:29:48 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of five
In-Reply-To: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>
Message-ID: <1547548188.38.0.92025146879.issue35738@roundup.psfhosted.org>


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


----------
pull_requests: +11208, 11209

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

From report at bugs.python.org  Tue Jan 15 05:49:21 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 15 Jan 2019 10:49:21 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of five
In-Reply-To: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>
Message-ID: <1547549359.24.0.722196228371.issue35738@roundup.psfhosted.org>


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


New changeset 0bb6b891154b5718c2d7604fc4aa7a51a2f9fe70 by Miss Islington (bot) in branch '3.7':
bpo-35738: Update the example for timer.Timer.repeat(). (GH-11559)
https://github.com/python/cpython/commit/0bb6b891154b5718c2d7604fc4aa7a51a2f9fe70


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

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

From report at bugs.python.org  Tue Jan 15 05:54:05 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Jan 2019 10:54:05 +0000
Subject: [docs] [issue35738] Update timeit documentation to reflect default
 repeat of five
In-Reply-To: <1547492160.57.0.532136359252.issue35738@roundup.psfhosted.org>
Message-ID: <1547549645.55.0.108058188644.issue35738@roundup.psfhosted.org>


Change by STINNER Victor <vstinner at redhat.com>:


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

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

From report at bugs.python.org  Tue Jan 15 08:12:15 2019
From: report at bugs.python.org (Jay)
Date: Tue, 15 Jan 2019 13:12:15 +0000
Subject: [docs] [issue35744] Problem in the documentation of
 numpy.random.randint in python 2.7
Message-ID: <1547557932.37.0.905069096511.issue35744@roundup.psfhosted.org>


New submission from Jay <jay.pokarna10 at gmail.com>:

Official Documentation of python 2.7 mentions that numpy.random.randint(a,b) will return a random integer from N such that a<=N<=b. But I have run the code and I have found that it never returns equal to b. So, what I did was I ran numpy.random.randint(0,1) for 50 milion times and finally printed the sum. 

The output was 0. 

I don't know if this a documentation or an implementation issue, but this is an issue which needs to be looked at. I am attaching the code that I ran.

----------
assignee: docs at python
components: Documentation
files: sample.py
messages: 333701
nosy: Jay, docs at python
priority: normal
severity: normal
status: open
title: Problem in the documentation of numpy.random.randint in python 2.7
type: behavior
versions: Python 2.7
Added file: https://bugs.python.org/file48051/sample.py

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

From report at bugs.python.org  Tue Jan 15 08:13:50 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 15 Jan 2019 13:13:50 +0000
Subject: [docs] [issue35744] Problem in the documentation of
 numpy.random.randint in python 2.7
In-Reply-To: <1547557932.37.0.905069096511.issue35744@roundup.psfhosted.org>
Message-ID: <1547558029.45.0.0763324580341.issue35744@roundup.psfhosted.org>


STINNER Victor <vstinner at redhat.com> added the comment:

Sorry but this is the bug tracker of Python, not of numpy. Please use https://github.com/numpy/numpy/issues instead.

----------
nosy: +vstinner
resolution:  -> third party
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Jan 15 10:33:15 2019
From: report at bugs.python.org (Windson Yang)
Date: Tue, 15 Jan 2019 15:33:15 +0000
Subject: [docs] [issue35745] Add import statement in dataclass code snippet
Message-ID: <1547566391.87.0.956827047672.issue35745@roundup.psfhosted.org>


New submission from Windson Yang <wiwindson at outlook.com>:

Most of the example in https://docs.python.org/3/library/dataclasses.html miss code like

from dataclasses import dataclass, field
from typing import List

I think we should add this statement in the code snippet.

----------
assignee: docs at python
components: Documentation
messages: 333707
nosy: Windson Yang, docs at python
priority: normal
severity: normal
status: open
title: Add import statement in dataclass code snippet
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue Jan 15 10:36:54 2019
From: report at bugs.python.org (Windson Yang)
Date: Tue, 15 Jan 2019 15:36:54 +0000
Subject: [docs] [issue35745] Add import statement in dataclass code snippet
In-Reply-To: <1547566391.87.0.956827047672.issue35745@roundup.psfhosted.org>
Message-ID: <1547566612.21.0.8406398449.issue35745@roundup.psfhosted.org>


Windson Yang <wiwindson at outlook.com> added the comment:

I'm not sure if we should put 

from dataclasses import dataclass

everywhere or we should put it just in the first example as I did in the PR.

----------

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

From h.h.ottinger at googlemail.com  Thu Jan 17 06:31:54 2019
From: h.h.ottinger at googlemail.com (Heinrich Ottinger)
Date: Thu, 17 Jan 2019 12:31:54 +0100
Subject: [docs] PDF-Files only available in Letter-Format
Message-ID: <CAFzhXs9PiX9=+J1a+oPxB7Nxmiem14bciy+aeJVEiqm04PNfug@mail.gmail.com>

*Dear Mr. van Rossum, *
*dear members of the great Python-Team! *

I want to thank you for your job and what you make available for the
public!

Please let my say, that there seams to be a little mistake in the PDF-Files
you offered for download this night: In the ZIP-File "
https://docs.python.org/3.7/archives/python-3.7.2-docs-pdf-a4.zip" there
are PDF-Files in the Letter-Format as well - instead of A4-Format!

With kind regards from T?bingen in Southern Germany,
*Heinrich Ottinger*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190117/e9226cce/attachment.html>

From report at bugs.python.org  Thu Jan 17 15:30:45 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 17 Jan 2019 20:30:45 +0000
Subject: [docs] [issue23156] Update tix install information in tkinter tix
 chapter of doc
In-Reply-To: <1420322124.69.0.0233808198239.issue23156@psf.upfronthosting.co.za>
Message-ID: <1547757042.77.0.881881118274.issue23156@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

Since tix has been deprecated since 3.6 (according to the docs with commit bd63353b7433ea8aa831ffb158ac29fb646a6fc9), should this ticket be closed as out of date?

----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Thu Jan 17 17:51:48 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 22:51:48 +0000
Subject: [docs] [issue23156] Update tix install information in tkinter tix
 chapter of doc
In-Reply-To: <1420322124.69.0.0233808198239.issue23156@psf.upfronthosting.co.za>
Message-ID: <1547765506.5.0.875634503887.issue23156@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
keywords: +patch
pull_requests: +11298
stage: needs patch -> patch review

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

From report at bugs.python.org  Thu Jan 17 17:52:04 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 22:52:04 +0000
Subject: [docs] [issue23156] Update tix install information in tkinter tix
 chapter of doc
In-Reply-To: <1420322124.69.0.0233808198239.issue23156@psf.upfronthosting.co.za>
Message-ID: <1547765522.35.0.684514778958.issue23156@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
keywords: +patch, patch
pull_requests: +11298, 11299
stage: needs patch -> patch review

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

From report at bugs.python.org  Thu Jan 17 17:52:19 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 22:52:19 +0000
Subject: [docs] [issue23156] Update tix install information in tkinter tix
 chapter of doc
In-Reply-To: <1420322124.69.0.0233808198239.issue23156@psf.upfronthosting.co.za>
Message-ID: <1547765537.84.0.858293869683.issue23156@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
keywords: +patch, patch, patch
pull_requests: +11298, 11299, 11300
stage: needs patch -> patch review

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

From report at bugs.python.org  Thu Jan 17 17:56:13 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 22:56:13 +0000
Subject: [docs] [issue23156] Update tix install information in tkinter tix
 chapter of doc
In-Reply-To: <1420322124.69.0.0233808198239.issue23156@psf.upfronthosting.co.za>
Message-ID: <1547765769.53.0.564591266267.issue23156@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

If the obsolete text is not to revised, it should be removed, as Ned suggested.  I don't now think a replacement list is needed.

Serhiy, if you have any opinion either way, please say go.

----------
stage: patch review -> needs patch
versions: +Python 3.8 -Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Thu Jan 17 17:57:02 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 22:57:02 +0000
Subject: [docs] [issue23156] Update tix install information in tkinter tix
 chapter of doc
In-Reply-To: <1420322124.69.0.0233808198239.issue23156@psf.upfronthosting.co.za>
Message-ID: <1547765818.39.0.412769627582.issue23156@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

/go/so

----------

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

From report at bugs.python.org  Thu Jan 17 18:24:40 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:24:40 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547767480.68.0.58728261592.issue34161@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests: +11304

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

From report at bugs.python.org  Thu Jan 17 18:24:47 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:24:47 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547767487.08.0.311484316603.issue34161@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests: +11304, 11305

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

From report at bugs.python.org  Thu Jan 17 18:24:55 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:24:55 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547767495.3.0.500361728331.issue34161@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests: +11304, 11305, 11306

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

From report at bugs.python.org  Thu Jan 17 18:26:58 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:26:58 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547767618.41.0.727199255761.issue34161@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests:  -11306

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

From report at bugs.python.org  Thu Jan 17 18:27:12 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:27:12 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547767632.27.0.622244032615.issue34161@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests:  -11305

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

From report at bugs.python.org  Thu Jan 17 18:27:25 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:27:25 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547767645.22.0.655854632266.issue34161@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests:  -11304

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

From report at bugs.python.org  Thu Jan 17 18:44:24 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:44:24 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547768662.56.0.267473640057.issue34161@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:


New changeset 56c16057c639acc2fb89c6b783425320f23a5f6c by Terry Jan Reedy in branch 'master':
bpo-34161: Update idlelib/NEWS.txt to 2019 Jan 17 (GH-11597)
https://github.com/python/cpython/commit/56c16057c639acc2fb89c6b783425320f23a5f6c


----------
nosy: +terry.reedy

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

From report at bugs.python.org  Thu Jan 17 18:44:43 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 17 Jan 2019 23:44:43 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547768683.43.0.19640394164.issue34161@roundup.psfhosted.org>


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


----------
pull_requests: +11308

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

From report at bugs.python.org  Thu Jan 17 18:44:55 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 17 Jan 2019 23:44:55 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547768695.34.0.598839806707.issue34161@roundup.psfhosted.org>


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


----------
pull_requests: +11308, 11309

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

From report at bugs.python.org  Thu Jan 17 18:45:06 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 17 Jan 2019 23:45:06 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547768706.76.0.945826168376.issue34161@roundup.psfhosted.org>


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


----------
pull_requests: +11308, 11309, 11310

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

From report at bugs.python.org  Thu Jan 17 18:50:24 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:50:24 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547769024.65.0.620618253783.issue34161@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests:  -11310

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

From report at bugs.python.org  Thu Jan 17 18:50:46 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:50:46 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547769046.28.0.649008755385.issue34161@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests:  -11309

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

From report at bugs.python.org  Thu Jan 17 18:51:06 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:51:06 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547769066.73.0.713445547528.issue34161@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
pull_requests:  -11308

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

From report at bugs.python.org  Thu Jan 17 18:52:16 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:52:16 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547769136.21.0.368595366103.issue34161@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
Removed message: https://bugs.python.org/msg333912

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

From report at bugs.python.org  Thu Jan 17 18:55:28 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 17 Jan 2019 23:55:28 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547769326.77.0.83936651891.issue34161@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

Sorry for the noise.  It seems like a bug to me that GitHub keeps a secret link to the original title and uses it in the merge box.

----------

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

From report at bugs.python.org  Thu Jan 17 19:00:57 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 18 Jan 2019 00:00:57 +0000
Subject: [docs] [issue23156] Update tix install information in tkinter tix
 chapter of doc
In-Reply-To: <1420322124.69.0.0233808198239.issue23156@psf.upfronthosting.co.za>
Message-ID: <1547769654.02.0.605834293609.issue23156@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:


New changeset cf27c06229eb4b8280bb5f2b93a57e33163411f4 by Terry Jan Reedy in branch 'master':
bpo-23156: Remove obsolete tix install directions (GH-11595)
https://github.com/python/cpython/commit/cf27c06229eb4b8280bb5f2b93a57e33163411f4


----------

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

From report at bugs.python.org  Thu Jan 17 19:05:34 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Jan 2019 00:05:34 +0000
Subject: [docs] [issue34161] (good first issue) Tutorial 7.1 str.format()
 code example syntax error
In-Reply-To: <1532062323.28.0.56676864532.issue34161@psf.upfronthosting.co.za>
Message-ID: <1547769934.99.0.511602027115.issue34161@roundup.psfhosted.org>


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


----------
pull_requests: +11315

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

From report at bugs.python.org  Thu Jan 17 19:07:16 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 18 Jan 2019 00:07:16 +0000
Subject: [docs] [issue23156] Update tix install information in tkinter tix
 chapter of doc
In-Reply-To: <1420322124.69.0.0233808198239.issue23156@psf.upfronthosting.co.za>
Message-ID: <1547770033.09.0.81835760966.issue23156@roundup.psfhosted.org>


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


New changeset ebb08beb08461eb5f147aaca6f86cafa4ea15bff by Miss Islington (bot) in branch '3.7':
bpo-23156: Remove obsolete tix install directions (GH-11595)
https://github.com/python/cpython/commit/ebb08beb08461eb5f147aaca6f86cafa4ea15bff


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

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

From report at bugs.python.org  Thu Jan 17 19:31:44 2019
From: report at bugs.python.org (Patrick Rice)
Date: Fri, 18 Jan 2019 00:31:44 +0000
Subject: [docs] [issue35765] Document references object x but doesn't show
 it in the example
Message-ID: <1547771500.83.0.912392206765.issue35765@roundup.psfhosted.org>


New submission from Patrick Rice <price at zoox.com>:

https://docs.python.org/3.5/tutorial/inputoutput.html

If you have an object x, you can view its JSON string representation with a simple line of code:

>>>
>>> import json
>>> json.dumps([1, 'simple', 'list'])
'[1, "simple", "list"]'

----------
assignee: docs at python
components: Documentation
messages: 333917
nosy: Patrick Rice, docs at python
priority: normal
severity: normal
status: open
title: Document references object x but doesn't show it in the example
versions: Python 3.5

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

From report at bugs.python.org  Thu Jan 17 19:51:17 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 18 Jan 2019 00:51:17 +0000
Subject: [docs] [issue23156] Remove tix install information in tkinter tix
 chapter of doc
In-Reply-To: <1420322124.69.0.0233808198239.issue23156@psf.upfronthosting.co.za>
Message-ID: <1547772675.85.0.469199298528.issue23156@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
title: Update tix install information in tkinter tix chapter of doc -> Remove tix install information in tkinter tix chapter of doc
versions: +Python 3.7

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

From report at bugs.python.org  Thu Jan 17 20:07:45 2019
From: report at bugs.python.org (Ned Deily)
Date: Fri, 18 Jan 2019 01:07:45 +0000
Subject: [docs] [issue35525] Incorrect keyword name in NNTP.starttls()
 documentation
In-Reply-To: <1545146886.62.0.788709270274.issue35525@psf.upfronthosting.co.za>
Message-ID: <1547773661.63.0.881403600222.issue35525@roundup.psfhosted.org>


Ned Deily <nad at python.org> added the comment:


New changeset 7887c02d3372ebe3b39379588364134521a36c4e by Ned Deily (Miss Islington (bot)) in branch '3.6':
bpo-35525: Correct the argument name for NNTP.starttls() (GH-11310) (GH-11417)
https://github.com/python/cpython/commit/7887c02d3372ebe3b39379588364134521a36c4e


----------
nosy: +ned.deily

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

From report at bugs.python.org  Thu Jan 17 21:18:09 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 18 Jan 2019 02:18:09 +0000
Subject: [docs] [issue35765] Document references object x but doesn't show
 it in the example
In-Reply-To: <1547771500.83.0.912392206765.issue35765@roundup.psfhosted.org>
Message-ID: <1547777887.69.0.643341687654.issue35765@roundup.psfhosted.org>


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

Thanks for the report. I think x here is implied as [1, 'simple', 'list']. Do you want to make it explicit with x = [1, 'simple', 'list'] in the code block?

Removing 3.5 since it's in security fixes only mode.

----------
nosy: +xtreak
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Fri Jan 18 10:22:03 2019
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 18 Jan 2019 15:22:03 +0000
Subject: [docs] [issue33995] test_min_max_version in test_ssl.py fails when
 Python is built against LibreSSL;
 {min,max}imum_version behavior differs from OpenSSL
In-Reply-To: <1530250345.83.0.56676864532.issue33995@psf.upfronthosting.co.za>
Message-ID: <1547824915.53.0.795009094979.issue33995@roundup.psfhosted.org>


STINNER Victor <vstinner at redhat.com> added the comment:

Oh, this issue looks like bpo-35045 which has been fixed.

----------
nosy: +vstinner
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> test_min_max_version (test.test_ssl.ContextTests) fails on Fedora 29+ and openssl 1.1.1

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

From report at bugs.python.org  Fri Jan 18 23:50:56 2019
From: report at bugs.python.org (yuji38kwmt)
Date: Sat, 19 Jan 2019 04:50:56 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
Message-ID: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>


New submission from yuji38kwmt <yuji38kwmt at gmail.com>:

### Target Documentation

https://docs.python.org/3/howto/logging.html#configuring-logging


### Actual Sample Code

```
# 'application' code
logger.debug('debug message')
logger.info('info message')
logger.warn('warn message')
logger.error('error message')
logger.critical('critical message')
```

### Expected Sample Code

```
# 'application' code
logger.debug('debug message')
logger.info('info message')
logger.warning('warn message')
logger.error('error message')
logger.critical('critical message')
```

### Reference

> There is an obsolete method warn which is functionally identical to warning. As warn is deprecated, please do not use it - use warning instead.

https://docs.python.org/3.7/library/logging.html#logging.Logger.warning

----------
assignee: docs at python
components: Documentation
messages: 334030
nosy: docs at python, yuji38kwmt
priority: normal
severity: normal
status: open
title: `logger.warn` method is used in "Logging HOWTO" documentation though `logger.warn` method is deprecated in Python 3.7
type: behavior
versions: Python 3.7

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

From report at bugs.python.org  Sat Jan 19 00:05:05 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 19 Jan 2019 05:05:05 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1547874304.69.0.129631257161.issue35781@roundup.psfhosted.org>


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

Thanks for the report. Would you like to propose a PR for this? 

Cases of using warn method in documentation examples : 

* https://github.com/python/cpython/blob/master/Doc/howto/logging.rst
* https://github.com/python/cpython/blob/master/Doc/howto/logging-cookbook.rst

Doc/howto/logging.rst
613:    logger.warn('warn message')
643:    logger.warn('warn message')

Doc/howto/logging-cookbook.rst
189:    logger.warn('warn message')
298:            logger.warn('warn message')

----------
nosy: +vinay.sajip, xtreak
versions: +Python 3.8

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

From report at bugs.python.org  Sat Jan 19 02:42:57 2019
From: report at bugs.python.org (Martin Panter)
Date: Sat, 19 Jan 2019 07:42:57 +0000
Subject: [docs] [issue13322] buffered read() and write() does not raise
 BlockingIOError
In-Reply-To: <1320246535.71.0.465783773129.issue13322@psf.upfronthosting.co.za>
Message-ID: <1547883766.29.0.33860906315.issue13322@roundup.psfhosted.org>


Martin Panter <vadmium+py at gmail.com> added the comment:

Issue 35762 was opened specifically about Izbyshev?s case: TextIOWrapper behaviour with a non-blocking file. Calling ?os.fdopen? with mode='r' (text mode) returns a TextIOWrapper object.

----------

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

From report at bugs.python.org  Sat Jan 19 03:40:21 2019
From: report at bugs.python.org (=?utf-8?b?0JzQsNC60YEg0JLQtdGA0L3QtdGA?=)
Date: Sat, 19 Jan 2019 08:40:21 +0000
Subject: [docs] [issue35783] incorrect example of fetching messages in
 imaplib documentation
Message-ID: <1547887217.4.0.578077466695.issue35783@roundup.psfhosted.org>


New submission from ???? ?????? <mvarnar at gmail.com>:

An example of fetching messages from the mailbox given in "IMAP4 Example" section is incorrect:

typ, data = M.fetch(num, '(RFC822)')
print('Message %s\n%s\n' % (num, data[0][1]))

"fetch" may return server data that was not requested (see "7.4.2.  FETCH Response" section of RFC 3501). In that case "data[0][1]" won't return what user expects.
This is a bad example, that many people repeat and advise to other developers:
https://stackoverflow.com/questions/13210737/get-only-new-emails-imaplib-and-python
https://gist.github.com/robulouski/7441883
https://stackoverflow.com/questions/51098962/check-if-email-inbox-is-empty-imaplib-python3
https://stackoverflow.com/questions/21116498/imaplib-not-getting-all-emails-in-folder
https://stackoverflow.com/questions/2230037/how-to-fetch-an-email-body-using-imaplib-in-python

I guess, this peculiarity should be clarified in the documentation. I offer to mark this fetching method is not safe and requests careful fetch result parsing.

----------
assignee: docs at python
components: Documentation, email
messages: 334048
nosy: barry, docs at python, r.david.murray, ???? ??????
priority: normal
severity: normal
status: open
title: incorrect example of fetching messages in imaplib documentation
type: enhancement
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/issue35783>
_______________________________________

From report at bugs.python.org  Sat Jan 19 04:51:56 2019
From: report at bugs.python.org (=?utf-8?q?J=C3=B6rn_Heissler?=)
Date: Sat, 19 Jan 2019 09:51:56 +0000
Subject: [docs] [issue35784] document that hashlib.new takes kwargs
Message-ID: <1547891512.78.0.551625258156.issue35784@roundup.psfhosted.org>


New submission from J?rn Heissler <launchpad at joern.heissler.de>:

This code works:
hashlib.new('blake2b', b'foo', digest_size=7)

https://github.com/python/cpython/blob/master/Lib/hashlib.py#L7
documents the function as: new(name, data=b'', **kwargs)

But the **kwargs argument is missing in https://docs.python.org/3/library/hashlib.html#hashlib.new and there aren't any examples either.

----------
assignee: docs at python
components: Documentation
messages: 334053
nosy: docs at python, joernheissler
priority: normal
severity: normal
status: open
title: document that hashlib.new takes kwargs
type: enhancement

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

From report at bugs.python.org  Sat Jan 19 05:58:13 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sat, 19 Jan 2019 10:58:13 +0000
Subject: [docs] [issue35784] document that hashlib.new takes kwargs
In-Reply-To: <1547891512.78.0.551625258156.issue35784@roundup.psfhosted.org>
Message-ID: <1547895493.6.0.628946359657.issue35784@roundup.psfhosted.org>


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


----------
nosy: +christian.heimes, gregory.p.smith
versions: +Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat Jan 19 12:52:26 2019
From: report at bugs.python.org (Vinay Badhan)
Date: Sat, 19 Jan 2019 17:52:26 +0000
Subject: [docs] [issue35533] argparse standard error usage for exit / error
In-Reply-To: <1545220030.92.0.788709270274.issue35533@psf.upfronthosting.co.za>
Message-ID: <1547920344.66.0.50423073284.issue35533@roundup.psfhosted.org>


Vinay Badhan <vinay.badhan21 at gmail.com> added the comment:

Add documentation for exit() function

----------
keywords: +patch
nosy: +vinayb21
pull_requests: +11377
stage:  -> patch review

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

From report at bugs.python.org  Sat Jan 19 16:50:36 2019
From: report at bugs.python.org (Lorenzo Persichetti)
Date: Sat, 19 Jan 2019 21:50:36 +0000
Subject: [docs] [issue35786] get_lock() method is not present for Values
 created using multiprocessing.Manager()
Message-ID: <1547934632.93.0.223661167179.issue35786@roundup.psfhosted.org>


New submission from Lorenzo Persichetti <lpersichetti at gmail.com>:

According to the documentation of the multiprocessing.Value() class available here https://docs.python.org/3.6/library/multiprocessing.html#multiprocessing.Value

Operations like += which involve a read and write are not atomic. So if, for instance, you want to atomically increment a shared value it is insufficient to just do

counter.value += 1
Assuming the associated lock is recursive (which it is by default) you can instead do

with counter.get_lock():
    counter.value += 1

What happens is that when running the following snippet

import multiprocessing
manager = multiprocessing.Manager()
value = manager.Value('i', 0)
value.get_lock()

the result is 
AttributeError: 'ValueProxy' object has no attribute 'get_lock'

----------
assignee: docs at python
components: Documentation, Library (Lib), Windows
messages: 334070
nosy: Lorenzo Persichetti, docs at python, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: get_lock() method is not present for Values created using multiprocessing.Manager()
versions: Python 3.6

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

From velson.horie at manchester.ac.uk  Sat Jan 19 09:33:08 2019
From: velson.horie at manchester.ac.uk (C Velson Horie)
Date: Sat, 19 Jan 2019 14:33:08 +0000
Subject: [docs] 3. An Informal Introduction to Python
Message-ID: <630728BF36473644B1A8D20CD2D1D8598D52F89D@MBXP13.ds.man.ac.uk>

I am just starting to learn Python.
I miscoded the block, because I did not understand the formatting conventions.  As a result the Fibonacci series was 0,0,0.. and I could not stop it except by closing the command window.  I tried cntl-X, Esc etc - nothing worked.

How do I stop a process in Python?

--
Velson Horie

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190119/c75333c8/attachment.html>

From report at bugs.python.org  Sun Jan 20 10:12:34 2019
From: report at bugs.python.org (Jim Carroll)
Date: Sun, 20 Jan 2019 15:12:34 +0000
Subject: [docs] [issue35789] Typo in unittest.mock docs
Message-ID: <1547997151.52.0.475948555823.issue35789@roundup.psfhosted.org>


New submission from Jim Carroll <jim at carroll.com>:

There is a typo in the unittest.mock documentation found at https://docs.python.org/3/library/unittest.mock.html.

There are seven(7) instances of the word assret, where the author clearly intended assert.

----------
assignee: docs at python
components: Documentation
messages: 334087
nosy: docs at python, jamercee
priority: normal
severity: normal
status: open
title: Typo in unittest.mock docs
type: enhancement
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Jan 20 10:15:18 2019
From: report at bugs.python.org (Jim Carroll)
Date: Sun, 20 Jan 2019 15:15:18 +0000
Subject: [docs] [issue35789] Typo in unittest.mock docs
In-Reply-To: <1547997151.52.0.475948555823.issue35789@roundup.psfhosted.org>
Message-ID: <1547997317.46.0.785674332881.issue35789@roundup.psfhosted.org>


Jim Carroll <jim at carroll.com> added the comment:

Never mind....i see this issue has been reported previously and the typo is considered intentional.

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

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

From report at bugs.python.org  Sun Jan 20 11:39:47 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Sun, 20 Jan 2019 16:39:47 +0000
Subject: [docs] [issue35790] Correct a statement about sys.exc_info() values
 restoration
Message-ID: <1548002384.27.0.286179066843.issue35790@roundup.psfhosted.org>


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

In the documentation of the try statement (https://docs.python.org/3/reference/compound_stmts.html#the-try-statement), I think that the sentence:

"sys.exc_info() values are restored to their previous values (before the call) when returning from a function that handled an exception."

should be replaced by this sentence:

"sys.exc_info() values are restored to their previous values (before the call) when leaving an exception handler."

as proven by this code which does not use any "function that handled an exception" and yet restores sys.exc_info() values:


>>> try:
...     raise ValueError
... except:
...     try:
...          raise TypeError
...     except:
...         print(sys.exc_info())
...     print(sys.exc_info())
... 
(<class 'TypeError'>, TypeError(), <traceback object at 0x10ca19bc8>)
(<class 'ValueError'>, ValueError(), <traceback object at 0x10ca19c08>)

----------
assignee: docs at python
components: Documentation
messages: 334092
nosy: docs at python, eric.araujo, ezio.melotti, maggyero, mdk, willingc
priority: normal
severity: normal
status: open
title: Correct a statement about sys.exc_info() values restoration
versions: Python 3.7

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

From report at bugs.python.org  Sun Jan 20 11:56:52 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Sun, 20 Jan 2019 16:56:52 +0000
Subject: [docs] [issue35790] Correct a statement about sys.exc_info() values
 restoration
In-Reply-To: <1548002384.27.0.286179066843.issue35790@roundup.psfhosted.org>
Message-ID: <1548003412.81.0.775855083614.issue35790@roundup.psfhosted.org>


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


----------
keywords: +patch
pull_requests: +11386
stage:  -> patch review

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

From report at bugs.python.org  Sun Jan 20 11:57:03 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Sun, 20 Jan 2019 16:57:03 +0000
Subject: [docs] [issue35790] Correct a statement about sys.exc_info() values
 restoration
In-Reply-To: <1548002384.27.0.286179066843.issue35790@roundup.psfhosted.org>
Message-ID: <1548003423.12.0.0459139891201.issue35790@roundup.psfhosted.org>


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


----------
keywords: +patch, patch
pull_requests: +11386, 11387
stage:  -> patch review

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

From report at bugs.python.org  Sun Jan 20 11:57:12 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Sun, 20 Jan 2019 16:57:12 +0000
Subject: [docs] [issue35790] Correct a statement about sys.exc_info() values
 restoration
In-Reply-To: <1548002384.27.0.286179066843.issue35790@roundup.psfhosted.org>
Message-ID: <1548003432.08.0.935382875145.issue35790@roundup.psfhosted.org>


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


----------
keywords: +patch, patch, patch
pull_requests: +11386, 11387, 11388
stage:  -> patch review

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

From report at bugs.python.org  Sun Jan 20 14:00:41 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 20 Jan 2019 19:00:41 +0000
Subject: [docs] [issue32603] Deprecation warning on strings used in re module
In-Reply-To: <1516404051.77.0.467229070634.issue32603@psf.upfronthosting.co.za>
Message-ID: <1548010839.44.0.778640093201.issue32603@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/issue32603>
_______________________________________

From gallium.arsenide at gmail.com  Sun Jan 20 15:00:40 2019
From: gallium.arsenide at gmail.com (John Yeung)
Date: Sun, 20 Jan 2019 15:00:40 -0500
Subject: [docs] The `errors` parameter for `pickle.load`
Message-ID: <CAA2zXtAJQVut06s6frR0uhux-Yq4=8sunV0ntY6WM+28X-rikQ@mail.gmail.com>

The docs for `pickle.load` and `pickle.loads` mention that the default
value for `errors` is 'strict' but don't say anything about what else
it could be.

If you're silly enough to try 'loose', you get

LookupError: unknown error handler name 'loose'

Where can someone find out more about this parameter? If it's too long
to explain right there in the docs for `load`, but something is
already published, I propose that the docs point to that. If it's a
case of "if you really want to use this, you really have to know what
you're doing, and you can figure it out for yourself from the source",
then the docs should say something to that effect.

Another possibility is that using a value other than the default is so
rare and specialized that the parameter might as well not be
documented (since you have to read the source to learn how to use it
anyway, in which case the source *is* your documentation).

Finally, as an orthogonal issue, the optional keyword arguments
paragraph is identical for both `load` and `loads`. I propose that it
follows the less repetitive pattern of `dump` and `dumps`.

John Y.

From arthur.p.goldberg at mssm.edu  Sun Jan 20 16:03:25 2019
From: arthur.p.goldberg at mssm.edu (Goldberg, Arthur P)
Date: Sun, 20 Jan 2019 21:03:25 +0000
Subject: [docs] Issue in https://docs.python.org/3/library/importlib.html
Message-ID: <2AAB8393-FEC5-4C5C-B759-B33F6F8996AE@mssm.edu>

In ?ValueError is also raised a relative name would escape its containing package (e.g. requesting ..bacon from within the spam package).?, s/raised a relative/raised if a relative/ and the example isn?t clear as no package hierarchy is illustrated.

Thanks for your great docs overall.

Arthur

Arthur Goldberg, PhD
Associate Professor of Genetics and Genomic Sciences
Institute for Data Science and Genomic Technology
Mount Sinai School of Medicine
1255 Fifth Ave., Suite C-2
New York, NY 10029
646 526 5020
Karr Lab
Arthur.Goldberg at mssm.edu<mailto:Arthur.Goldberg at mssm.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190120/3f1df482/attachment.html>

From report at bugs.python.org  Sun Jan 20 17:04:18 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 20 Jan 2019 22:04:18 +0000
Subject: [docs] [issue35786] get_lock() method is not present for Values
 created using multiprocessing.Manager()
In-Reply-To: <1547934632.93.0.223661167179.issue35786@roundup.psfhosted.org>
Message-ID: <1548021855.98.0.884594362447.issue35786@roundup.psfhosted.org>


Pablo Galindo Salgado <pablogsal at gmail.com> added the comment:

You are not using multiprocessing.Value:

>>> import multiprocessing
>>> x = multiprocessing.Value("i", 0)
>>> x.get_lock()
<RLock(None, 0)>

----------
nosy: +pablogsal

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

From report at bugs.python.org  Sun Jan 20 18:49:18 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 20 Jan 2019 23:49:18 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548028158.3.0.965784426564.issue35722@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella 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/issue35722>
_______________________________________

From report at bugs.python.org  Sun Jan 20 23:32:32 2019
From: report at bugs.python.org (Demian Brecht)
Date: Mon, 21 Jan 2019 04:32:32 +0000
Subject: [docs] [issue20582] socket.getnameinfo() does not document flags
In-Reply-To: <1392042265.22.0.885252016144.issue20582@psf.upfronthosting.co.za>
Message-ID: <1548045151.75.0.512847802344.issue20582@roundup.psfhosted.org>


Change by Demian Brecht <demianbrecht at gmail.com>:


----------
nosy: +demian.brecht

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

From report at bugs.python.org  Sun Jan 20 23:51:46 2019
From: report at bugs.python.org (Demian Brecht)
Date: Mon, 21 Jan 2019 04:51:46 +0000
Subject: [docs] [issue20582] socket.getnameinfo() does not document flags
In-Reply-To: <1392042265.22.0.885252016144.issue20582@psf.upfronthosting.co.za>
Message-ID: <1548046303.7.0.102497556745.issue20582@roundup.psfhosted.org>


Demian Brecht <demianbrecht at gmail.com> added the comment:

What if the docs for socket functions that took system-level flag parameters had links to relevant online man pages? I don't think a single entry at the top of the page would be optimal. I know that I tend to skip the preamble and just go directly to the function I'm interested in.

I know that it's not a perfect solution because there's a good chance of those links going stale. I'm also relatively sure that we wouldn't want to have an exhaustive list. However, I think in this instance that /something/ would be better than nothing. Even if the link is stale or the target OS isn't included, it would give the reader a place to start, which is currently lacking.

----------

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

From report at bugs.python.org  Mon Jan 21 04:39:39 2019
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 21 Jan 2019 09:39:39 +0000
Subject: [docs] [issue35168] shlex punctuation_chars inconsistency
In-Reply-To: <1541439134.06.0.788709270274.issue35168@psf.upfronthosting.co.za>
Message-ID: <1548063579.49.0.287426720809.issue35168@roundup.psfhosted.org>


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


----------
keywords: +patch
pull_requests: +11400
stage: needs patch -> patch review

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

From report at bugs.python.org  Mon Jan 21 04:39:50 2019
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 21 Jan 2019 09:39:50 +0000
Subject: [docs] [issue35168] shlex punctuation_chars inconsistency
In-Reply-To: <1541439134.06.0.788709270274.issue35168@psf.upfronthosting.co.za>
Message-ID: <1548063591.0.0.500341462038.issue35168@roundup.psfhosted.org>


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


----------
keywords: +patch, patch
pull_requests: +11400, 11401
stage: needs patch -> patch review

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

From report at bugs.python.org  Mon Jan 21 04:40:02 2019
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 21 Jan 2019 09:40:02 +0000
Subject: [docs] [issue35168] shlex punctuation_chars inconsistency
In-Reply-To: <1541439134.06.0.788709270274.issue35168@psf.upfronthosting.co.za>
Message-ID: <1548063602.75.0.317101231285.issue35168@roundup.psfhosted.org>


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


----------
keywords: +patch, patch, patch
pull_requests: +11400, 11401, 11402
stage: needs patch -> patch review

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

From report at bugs.python.org  Mon Jan 21 04:40:11 2019
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 21 Jan 2019 09:40:11 +0000
Subject: [docs] [issue35168] shlex punctuation_chars inconsistency
In-Reply-To: <1541439134.06.0.788709270274.issue35168@psf.upfronthosting.co.za>
Message-ID: <1548063611.64.0.485482372003.issue35168@roundup.psfhosted.org>


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


----------
keywords: +patch, patch, patch, patch
pull_requests: +11400, 11401, 11402, 11403
stage: needs patch -> patch review

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

From report at bugs.python.org  Mon Jan 21 05:15:46 2019
From: report at bugs.python.org (Yuuji KAWAMATSU)
Date: Mon, 21 Jan 2019 10:15:46 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548065744.26.0.749911359748.issue35781@roundup.psfhosted.org>


Yuuji KAWAMATSU <kawamatsu_yuuji at kurusugawa.jp> added the comment:

Thank you!
I will create PR.

----------
nosy: +Yuuji KAWAMATSU

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

From report at bugs.python.org  Mon Jan 21 10:10:44 2019
From: report at bugs.python.org (Christian Ullrich)
Date: Mon, 21 Jan 2019 15:10:44 +0000
Subject: [docs] [issue35797] concurrent.futures.ProcessPoolExecutor does not
 work in venv on Windows
Message-ID: <1548083441.54.0.942305079713.issue35797@roundup.psfhosted.org>


New submission from Christian Ullrich <chris at chrullrich.net>:

Using concurrent.futures.ProcessPoolExecutor on Windows fails immediately with a lot of exceptions of the "access denied", "file not found", and "invalid handle" varieties. Running the script that creates the ProcessPoolExecutor from the main system-wide installation works correctly.

Due to Windows' infamous lack of fork(), ProcessPoolExecutor launches its worker processes by setting up an inheritable handle to a pipe and passing the handle on the command line.

In a venv situation, it appears that the venv's python.exe internally launches the parent environment's python.exe and passes on its command line, but not its handle table. This sub-subprocess therefore does not have the original handle, and may have a different handle at the same index.


Output of the ProcessPoolExecutor example program from the docs when run with the main installation:

C:\Daten>py cft.py
112272535095293 is prime: True
112582705942171 is prime: True
112272535095293 is prime: True
115280095190773 is prime: True
115797848077099 is prime: True
1099726899285419 is prime: False


Output when run using a venv:

C:\Daten>pyv\v37\Scripts\python.exe cft.py
Process SpawnProcess-4:
Traceback (most recent call last):
  File "C:\Program Files\Python37\lib\multiprocessing\process.py", line 297, in _bootstrap
    self.run()
  File "C:\Program Files\Python37\lib\multiprocessing\process.py", line 99, in run
    self._target(*self._args, **self._kwargs)
  File "C:\Program Files\Python37\lib\concurrent\futures\process.py", line 226, in _process_worker
    call_item = call_queue.get(block=True)
  File "C:\Program Files\Python37\lib\multiprocessing\queues.py", line 93, in get
    with self._rlock:
  File "C:\Program Files\Python37\lib\multiprocessing\synchronize.py", line 95, in __enter__
    return self._semlock.__enter__()
PermissionError: [WinError 5] Access is denied
Process SpawnProcess-5:
Traceback (most recent call last):
  File "C:\Program Files\Python37\lib\multiprocessing\process.py", line 297, in _bootstrap
    self.run()
  File "C:\Program Files\Python37\lib\multiprocessing\process.py", line 99, in run
    self._target(*self._args, **self._kwargs)
  File "C:\Program Files\Python37\lib\concurrent\futures\process.py", line 226, in _process_worker
    call_item = call_queue.get(block=True)
  File "C:\Program Files\Python37\lib\multiprocessing\queues.py", line 93, in get
    with self._rlock:
  File "C:\Program Files\Python37\lib\multiprocessing\synchronize.py", line 95, in __enter__
    return self._semlock.__enter__()
PermissionError: [WinError 5] Access is denied
Traceback (most recent call last):
  File "cft.py", line 28, in <module>
    main()
  File "cft.py", line 24, in main
    for number, prime in zip(PRIMES, executor.map(is_prime, PRIMES)):
  File "C:\Program Files\Python37\lib\concurrent\futures\process.py", line 476, in _chain_from_iterable_of_lists
    for element in iterable:
  File "C:\Program Files\Python37\lib\concurrent\futures\_base.py", line 586, in result_iterator
    yield fs.pop().result()
  File "C:\Program Files\Python37\lib\concurrent\futures\_base.py", line 432, in result
    return self.__get_result()
  File "C:\Program Files\Python37\lib\concurrent\futures\_base.py", line 384, in __get_result
    raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.

----------
assignee: docs at python
components: Documentation, Library (Lib), Windows
messages: 334142
nosy: chrullrich, docs at python, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: concurrent.futures.ProcessPoolExecutor does not work in venv on Windows
type: behavior
versions: Python 3.7

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

From report at bugs.python.org  Mon Jan 21 13:15:55 2019
From: report at bugs.python.org (jez)
Date: Mon, 21 Jan 2019 18:15:55 +0000
Subject: [docs] [issue35777] mismatched eval() and ast.literal_eval()
 behavior with unicode_literals
In-Reply-To: <1547846800.05.0.589923940496.issue35777@roundup.psfhosted.org>
Message-ID: <1548094553.76.0.712322563821.issue35777@roundup.psfhosted.org>


jez <jezhill at gmail.com> added the comment:

I take the point about breaking backward compatibility. The problem, then, is in the `ast` documentation, and may not be confined to Python 2.7

The `literal_eval` doc <https://docs.python.org/2/library/ast.html#ast-helpers> states no more than that the function evaluates a "string containing a Python literal".  The future statement effectively changes the definition of "a Python literal" but of course, as the official `__future__` doc <https://docs.python.org/2/reference/simple_stmts.html#future> explains, this is done for the compilation of each "particular module" in isolation. The question is left open whether the occurrence of this term in `ast` documentation should be read as "a Python literal (as defined by the ast module itself at compile time)",  or "a Python literal (as defined by the caller at compile time)".

More generally, future statements effectively change the definition of the term "Python syntax", sometimes also simply referred to as "Python".  Unfortunately, the `ast` documentation uses these terms loosely throughout, without acknowledging that they are mutable. I propose that the `ast` module documentation flag cases in which the `ast` module's own definitions of "Python" and "Python syntax" may not match those of a caller who has included `__future__` statements, leading to unexpected behavior.

I am insufficiently familiar with the full functionality of `ast` to be able to identify where this is and is not an issue, except in `literal_eval`, but I can see it could in principle affect Python 3.x too.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
versions:  -Python 2.7

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

From report at bugs.python.org  Mon Jan 21 13:48:47 2019
From: report at bugs.python.org (Paul Watson)
Date: Mon, 21 Jan 2019 18:48:47 +0000
Subject: [docs] [issue35801] venv in 3.7 references python3 executable
Message-ID: <1548096524.26.0.673516861772.issue35801@roundup.psfhosted.org>


New submission from Paul Watson <paul.hermeneutic at gmail.com>:

The documentation for venv in Python 3.7 references using `python3` to run venv. I do not find a `python3` executable in the kit.

https://docs.python.org/3.7/library/venv.html#module-venv

----------
assignee: docs at python
components: Documentation
messages: 334165
nosy: Paul Watson, docs at python
priority: normal
severity: normal
status: open
title: venv in 3.7 references python3 executable
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Mon Jan 21 17:07:05 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 21 Jan 2019 22:07:05 +0000
Subject: [docs] [issue35803] Test and document that `dir=...` in tempfile
 may be PathLike
Message-ID: <1548108422.42.0.0789815194403.issue35803@roundup.psfhosted.org>


New submission from Anthony Sottile <asottile at umich.edu>:

This appears to be true in 3.6+ -- I'd like to add a test and documentation ensuring that going forward.

Related: https://github.com/python/typeshed/issues/2749

----------
assignee: docs at python
components: Documentation, Tests
messages: 334188
nosy: Anthony Sottile, docs at python
priority: normal
severity: normal
status: open
title: Test and document that `dir=...` in tempfile may be PathLike
type: behavior
versions: Python 3.8

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

From report at bugs.python.org  Mon Jan 21 17:36:55 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 21 Jan 2019 22:36:55 +0000
Subject: [docs] [issue35803] Test and document that `dir=...` in tempfile
 may be PathLike
In-Reply-To: <1548108422.42.0.0789815194403.issue35803@roundup.psfhosted.org>
Message-ID: <1548110214.17.0.0169398095735.issue35803@roundup.psfhosted.org>


Change by Anthony Sottile <asottile at umich.edu>:


----------
keywords: +patch
pull_requests: +11424
stage:  -> patch review

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

From report at bugs.python.org  Mon Jan 21 17:37:00 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 21 Jan 2019 22:37:00 +0000
Subject: [docs] [issue35803] Test and document that `dir=...` in tempfile
 may be PathLike
In-Reply-To: <1548108422.42.0.0789815194403.issue35803@roundup.psfhosted.org>
Message-ID: <1548110219.09.0.517212402667.issue35803@roundup.psfhosted.org>


Change by Anthony Sottile <asottile at umich.edu>:


----------
keywords: +patch, patch
pull_requests: +11424, 11425
stage:  -> patch review

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

From report at bugs.python.org  Mon Jan 21 17:37:05 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 21 Jan 2019 22:37:05 +0000
Subject: [docs] [issue35803] Test and document that `dir=...` in tempfile
 may be PathLike
In-Reply-To: <1548108422.42.0.0789815194403.issue35803@roundup.psfhosted.org>
Message-ID: <1548110224.05.0.357663955744.issue35803@roundup.psfhosted.org>


Change by Anthony Sottile <asottile at umich.edu>:


----------
keywords: +patch, patch, patch
pull_requests: +11424, 11425, 11426
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan 22 06:20:29 2019
From: report at bugs.python.org (Nick Coghlan)
Date: Tue, 22 Jan 2019 11:20:29 +0000
Subject: [docs] [issue35486] subprocess module import hooks breaks back
 compatibility
In-Reply-To: <1544742855.44.0.788709270274.issue35486@psf.upfronthosting.co.za>
Message-ID: <1548156027.03.0.346625241991.issue35486@roundup.psfhosted.org>


Nick Coghlan <ncoghlan at gmail.com> added the comment:

Aye, we can :)

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Jan 22 20:41:21 2019
From: report at bugs.python.org (Yuuji KAWAMATSU)
Date: Wed, 23 Jan 2019 01:41:21 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548207681.58.0.605569966834.issue35781@roundup.psfhosted.org>


Change by Yuuji KAWAMATSU <kawamatsu_yuuji at kurusugawa.jp>:


----------
keywords: +patch
pull_requests: +11442
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan 22 20:41:32 2019
From: report at bugs.python.org (Yuuji KAWAMATSU)
Date: Wed, 23 Jan 2019 01:41:32 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548207692.32.0.749055644472.issue35781@roundup.psfhosted.org>


Change by Yuuji KAWAMATSU <kawamatsu_yuuji at kurusugawa.jp>:


----------
keywords: +patch, patch
pull_requests: +11442, 11443
stage:  -> patch review

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

From report at bugs.python.org  Tue Jan 22 20:41:43 2019
From: report at bugs.python.org (Yuuji KAWAMATSU)
Date: Wed, 23 Jan 2019 01:41:43 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548207703.04.0.134987297827.issue35781@roundup.psfhosted.org>


Change by Yuuji KAWAMATSU <kawamatsu_yuuji at kurusugawa.jp>:


----------
keywords: +patch, patch, patch
pull_requests: +11442, 11443, 11444
stage:  -> patch review

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

From report at bugs.python.org  Wed Jan 23 02:12:44 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:12:44 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548227562.99.0.188317800767.issue35722@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset f0c743604fc841d35a48822b936ef2e5919e43c1 by Vinay Sajip (G?ry Ogam) in branch 'master':
bpo-35722: Updated the documentation for the 'disable_existing_loggers' parameter (GH-11525)
https://github.com/python/cpython/commit/f0c743604fc841d35a48822b936ef2e5919e43c1


----------

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

From report at bugs.python.org  Wed Jan 23 02:13:47 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Jan 2019 07:13:47 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548227627.12.0.107322735963.issue35722@roundup.psfhosted.org>


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


----------
keywords: +patch
pull_requests: +11445

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

From report at bugs.python.org  Wed Jan 23 02:14:01 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Jan 2019 07:14:01 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548227641.57.0.288529598427.issue35722@roundup.psfhosted.org>


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


----------
keywords: +patch, patch
pull_requests: +11445, 11446

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

From report at bugs.python.org  Wed Jan 23 02:14:13 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Jan 2019 07:14:13 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548227653.85.0.668028969367.issue35722@roundup.psfhosted.org>


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


----------
keywords: +patch, patch, patch
pull_requests: +11445, 11446, 11447

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

From report at bugs.python.org  Wed Jan 23 02:14:23 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Jan 2019 07:14:23 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548227663.96.0.324516718101.issue35722@roundup.psfhosted.org>


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


----------
keywords: +patch, patch, patch, patch
pull_requests: +11445, 11446, 11447, 11449

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

From report at bugs.python.org  Wed Jan 23 02:14:33 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Jan 2019 07:14:33 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548227673.96.0.600880767067.issue35722@roundup.psfhosted.org>


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


----------
keywords: 
pull_requests: +11446, 11447, 11449, 11450

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

From report at bugs.python.org  Wed Jan 23 02:14:44 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Jan 2019 07:14:44 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548227684.24.0.745496054786.issue35722@roundup.psfhosted.org>


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


----------
keywords: +patch, patch, patch, patch, patch
pull_requests: +11445, 11446, 11447, 11448, 11449, 11450

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

From report at bugs.python.org  Wed Jan 23 02:17:21 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:17:21 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548227841.29.0.627922818418.issue35781@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests:  -11444

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

From report at bugs.python.org  Wed Jan 23 02:17:41 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:17:41 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548227861.63.0.6286684946.issue35781@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests:  -11443

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

From report at bugs.python.org  Wed Jan 23 02:21:40 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:21:40 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548228098.23.0.321076112642.issue35722@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset 552478bb1086ef371e4f1da0b430b90eba4785d5 by Vinay Sajip (Miss Islington (bot)) in branch '3.7':
bpo-35722: Updated the documentation for the 'disable_existing_loggers' parameter (GH-11525) (GH-11655)
https://github.com/python/cpython/commit/552478bb1086ef371e4f1da0b430b90eba4785d5


----------

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

From report at bugs.python.org  Wed Jan 23 02:22:10 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:22:10 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548228130.51.0.540892364689.issue35722@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests:  -11446

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

From report at bugs.python.org  Wed Jan 23 02:22:33 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:22:33 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548228153.52.0.133263248174.issue35722@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests:  -11447

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

From report at bugs.python.org  Wed Jan 23 02:22:52 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:22:52 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548228172.59.0.656878807533.issue35722@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests:  -11450

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

From report at bugs.python.org  Wed Jan 23 02:23:23 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:23:23 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548228203.81.0.734158495872.issue35722@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests:  -11449

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

From report at bugs.python.org  Wed Jan 23 02:24:43 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:24:43 +0000
Subject: [docs] [issue35722] disable_existing_loggers does not apply to the
 root logger
In-Reply-To: <1547235149.9.0.274775552253.issue35722@roundup.psfhosted.org>
Message-ID: <1548228283.47.0.517158839622.issue35722@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/issue35722>
_______________________________________

From report at bugs.python.org  Wed Jan 23 02:27:19 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:27:19 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548228437.92.0.23457050071.issue35781@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset cda73a5af2ff064ca82140342b3158851d43868f by Vinay Sajip (yuji38kwmt) in branch 'master':
bpo-35781: Changed references to deprecated 'warn' method in logging documentation in favour of 'warning' (GH-11654)
https://github.com/python/cpython/commit/cda73a5af2ff064ca82140342b3158851d43868f


----------

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

From report at bugs.python.org  Wed Jan 23 02:27:30 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 23 Jan 2019 07:27:30 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548228450.43.0.124357635025.issue35781@roundup.psfhosted.org>


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


----------
pull_requests: +11451, 11453

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

From report at bugs.python.org  Wed Jan 23 02:27:47 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:27:47 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548228467.45.0.470914749365.issue35781@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests:  -11453

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

From report at bugs.python.org  Wed Jan 23 02:29:26 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:29:26 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548228566.17.0.947014293627.issue35781@roundup.psfhosted.org>


Change by Vinay Sajip <vinay_sajip at yahoo.co.uk>:


----------
pull_requests:  -11452

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

From report at bugs.python.org  Wed Jan 23 02:43:43 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:43:43 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548229421.61.0.325897135612.issue35781@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:


New changeset 3be19c082b7f0ba3cf6c28922d3577126871788e by Vinay Sajip (Miss Islington (bot)) in branch '3.7':
bpo-35781: Changed references to deprecated 'warn' method in logging documentation in favour of 'warning' (GH-11654) (GH-11657)
https://github.com/python/cpython/commit/3be19c082b7f0ba3cf6c28922d3577126871788e


----------

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

From report at bugs.python.org  Wed Jan 23 02:44:19 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 23 Jan 2019 07:44:19 +0000
Subject: [docs] [issue35781] `logger.warn` method is used in "Logging HOWTO"
 documentation though `logger.warn` method is deprecated in Python 3.7
In-Reply-To: <1547873452.27.0.124013164829.issue35781@roundup.psfhosted.org>
Message-ID: <1548229459.05.0.644385256356.issue35781@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/issue35781>
_______________________________________

From report at bugs.python.org  Wed Jan 23 08:53:52 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Wed, 23 Jan 2019 13:53:52 +0000
Subject: [docs] [issue28890] logging.handlers: Document that QueueListener
 is a daemon thread
Message-ID: <1548251632.71.0.221795815334.issue28890@roundup.psfhosted.org>


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


----------
nosy: +vinay.sajip, xtreak
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Wed Jan 23 17:45:30 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 23 Jan 2019 22:45:30 +0000
Subject: [docs] [issue5028] tokenize.generate_tokens doesn't always return
 logical line
In-Reply-To: <1232588343.15.0.723713394492.issue5028@psf.upfronthosting.co.za>
Message-ID: <1548283528.49.0.361847748219.issue5028@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
components: +Documentation -Library (Lib)
keywords: +easy
stage:  -> needs patch
versions: +Python 3.8 -Python 2.6

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

From report at bugs.python.org  Wed Jan 23 18:34:44 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 23 Jan 2019 23:34:44 +0000
Subject: [docs] [issue18610] wsgiref.validate expects wsgi.input read to
 give exactly one arg
In-Reply-To: <1375310901.82.0.276465395742.issue18610@psf.upfronthosting.co.za>
Message-ID: <1548286482.98.0.96550938809.issue18610@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
pull_requests: +11467
stage: needs patch -> patch review

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

From report at bugs.python.org  Wed Jan 23 18:34:53 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 23 Jan 2019 23:34:53 +0000
Subject: [docs] [issue18610] wsgiref.validate expects wsgi.input read to
 give exactly one arg
In-Reply-To: <1375310901.82.0.276465395742.issue18610@psf.upfronthosting.co.za>
Message-ID: <1548286492.87.0.632159324049.issue18610@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
pull_requests: +11467, 11468
stage: needs patch -> patch review

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

From report at bugs.python.org  Wed Jan 23 18:35:03 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 23 Jan 2019 23:35:03 +0000
Subject: [docs] [issue18610] wsgiref.validate expects wsgi.input read to
 give exactly one arg
In-Reply-To: <1375310901.82.0.276465395742.issue18610@psf.upfronthosting.co.za>
Message-ID: <1548286501.78.0.43392233439.issue18610@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
pull_requests: +11467, 11468, 11469
stage: needs patch -> patch review

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

From report at bugs.python.org  Wed Jan 23 18:51:46 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 23 Jan 2019 23:51:46 +0000
Subject: [docs] [issue18610] wsgiref.validate expects wsgi.input read to
 give exactly one arg
In-Reply-To: <1375310901.82.0.276465395742.issue18610@psf.upfronthosting.co.za>
Message-ID: <1548287505.28.0.146126260451.issue18610@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
pull_requests:  -11468

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

From report at bugs.python.org  Wed Jan 23 18:51:57 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 23 Jan 2019 23:51:57 +0000
Subject: [docs] [issue18610] wsgiref.validate expects wsgi.input read to
 give exactly one arg
In-Reply-To: <1375310901.82.0.276465395742.issue18610@psf.upfronthosting.co.za>
Message-ID: <1548287516.06.0.595009398873.issue18610@roundup.psfhosted.org>


Change by Cheryl Sabella <cheryl.sabella at gmail.com>:


----------
pull_requests:  -11469

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

From report at bugs.python.org  Thu Jan 24 12:06:30 2019
From: report at bugs.python.org (Mayank Singhal)
Date: Thu, 24 Jan 2019 17:06:30 +0000
Subject: [docs] [issue15248] Better explain "TypeError: 'tuple' object is
 not callable"
In-Reply-To: <1341379722.78.0.0866285571225.issue15248@psf.upfronthosting.co.za>
Message-ID: <1548349584.25.0.109755935846.issue15248@roundup.psfhosted.org>


Mayank Singhal <17mayanksinghal at gmail.com> added the comment:

Hey, if nobody is working on this can I go for it?

----------
nosy: +storymode7

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

From report at bugs.python.org  Thu Jan 24 12:10:04 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 24 Jan 2019 17:10:04 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMzE5ODJdIDguMy4gY29sbGVjdGlvbnMg4oCU?=
 =?utf-8?q?_Container_datatypes?=
In-Reply-To: <1510157451.94.0.213398074469.issue31982@psf.upfronthosting.co.za>
Message-ID: <1548349800.14.0.11693434194.issue31982@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

This is a duplicate of issue 31075, which was closed as 'Not a bug'.

----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Thu Jan 24 15:07:23 2019
From: report at bugs.python.org (Chris Jerdonek)
Date: Thu, 24 Jan 2019 20:07:23 +0000
Subject: [docs] [issue35821] Clarify when logging events are propagated when
 propagate is true
Message-ID: <1548360439.22.0.955979079327.issue35821@roundup.psfhosted.org>


New submission from Chris Jerdonek <chris.jerdonek at gmail.com>:

Currently, the logging docs are a bit ambiguous or at least not completely clear as to when events are propagated when Logger.propagate is true. The docs currently say [1]--

"If [the `propagate`] attribute evaluates to true, events logged to this logger will be passed to the handlers of higher level (ancestor) loggers, in addition to any handlers attached to this logger."

But it's not clear if "logged to this logger" means (1) a log method like info() or error() was called on the logger, or (2) the event was passed to the logger's handlers (i.e. satisfied the logger's log level threshold and any filters).

Empirically, I found that the meaning is (2).

[1]: https://docs.python.org/3/library/logging.html#logging.Logger.propagate

----------
assignee: docs at python
components: Documentation
messages: 334320
nosy: chris.jerdonek, docs at python
priority: normal
severity: normal
stage: needs patch
status: open
title: Clarify when logging events are propagated when propagate is true
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Thu Jan 24 15:45:17 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 24 Jan 2019 20:45:17 +0000
Subject: [docs] [issue15248] Better explain "TypeError: 'tuple' object is
 not callable"
In-Reply-To: <1341379722.78.0.0866285571225.issue15248@psf.upfronthosting.co.za>
Message-ID: <1548362711.76.0.430781336529.issue15248@roundup.psfhosted.org>


Terry J. Reedy <tjreedy at udel.edu> added the comment:

I am not sure what you could do at the moment.  We have not yet settled whether this is a documentation or interpreter core issue.

I posted "Add more SyntaxWarnings?" to pydev to get more comments on Serhiy's patch, especially for other core developers.  Depending on what people think, that *might* result in someone converting the diff (with the typo corrected) into a PR.

I already posted here a prototype doc entry for TypeError messages.  I decided that I should take time out from IDLE to post my idea for a separate error message doc.  I will include a fleshed-out TypeError entry (with code example) as an example entry.

----------

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

From report at bugs.python.org  Thu Jan 24 17:24:25 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 24 Jan 2019 22:24:25 +0000
Subject: [docs] [issue15248] Better explain "TypeError: 'tuple' object is
 not callable"
In-Reply-To: <1341379722.78.0.0866285571225.issue15248@psf.upfronthosting.co.za>
Message-ID: <1548368661.23.0.433380825176.issue15248@roundup.psfhosted.org>


Change by Guido van Rossum <guido at python.org>:


----------
nosy: +gvanrossum

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

From report at bugs.python.org  Thu Jan 24 19:08:55 2019
From: report at bugs.python.org (Igor Z)
Date: Fri, 25 Jan 2019 00:08:55 +0000
Subject: [docs] [issue35822] _queue _queuemodule.c is missing inside the
 Setup file
Message-ID: <1548374932.46.0.67529287669.issue35822@roundup.psfhosted.org>


New submission from Igor Z <igorzy.694 at gmail.com>:

I had to install manually new urllib3 (zip archive) module inside python 3.7 and got and error that module "_queue" is missing.
I did not find anything related to such module inside the Setup file.
Then I found this module in the github and manually added:
_queue _queuemodule.c and did "make" once again to get new "libpython3.7m.so.1.0" that I needed for the project. The problem was solved.

----------
assignee: docs at python
components: Build, Documentation, Library (Lib)
messages: 334329
nosy: Igor Z, docs at python
priority: normal
severity: normal
status: open
title: _queue _queuemodule.c is missing inside the Setup file
type: behavior
versions: Python 3.7

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

From report at bugs.python.org  Thu Jan 24 19:27:30 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 25 Jan 2019 00:27:30 +0000
Subject: [docs] [issue35821] Clarify when logging events are propagated when
 propagate is true
In-Reply-To: <1548360439.22.0.955979079327.issue35821@roundup.psfhosted.org>
Message-ID: <1548376048.73.0.111851094832.issue35821@roundup.psfhosted.org>


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


----------
nosy: +vinay.sajip, xtreak

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

From report at bugs.python.org  Thu Jan 24 19:42:02 2019
From: report at bugs.python.org (Chris Jerdonek)
Date: Fri, 25 Jan 2019 00:42:02 +0000
Subject: [docs] [issue35821] Clarify when logging events are propagated when
 propagate is true
In-Reply-To: <1548360439.22.0.955979079327.issue35821@roundup.psfhosted.org>
Message-ID: <1548376920.1.0.951958240975.issue35821@roundup.psfhosted.org>


Chris Jerdonek <chris.jerdonek at gmail.com> added the comment:

Also, does "logged to this logger" include events propagated to it from a child logger? For example, if an event is logged to logger "A.B.C" and propagated to "A.B", will the propagate attribute of the latter effect whether logger "A" (or its handlers) sees it?

----------

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

From report at bugs.python.org  Fri Jan 25 00:46:08 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 25 Jan 2019 05:46:08 +0000
Subject: [docs] [issue35821] Clarify when logging events are propagated when
 propagate is true
In-Reply-To: <1548360439.22.0.955979079327.issue35821@roundup.psfhosted.org>
Message-ID: <1548395166.02.0.436157345563.issue35821@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

I believe the information is clear from this link in the documentation:

https://docs.python.org/3/howto/logging.html#logging-flow

However, if you can suggest alternative wording which you think is clearer, I'll certainly take a look at it. Perhaps a link could be added to this section from the logging.Logger.propagate section.

----------

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

From report at bugs.python.org  Fri Jan 25 01:58:49 2019
From: report at bugs.python.org (Chris Jerdonek)
Date: Fri, 25 Jan 2019 06:58:49 +0000
Subject: [docs] [issue35821] Clarify when logging events are propagated when
 propagate is true
In-Reply-To: <1548360439.22.0.955979079327.issue35821@roundup.psfhosted.org>
Message-ID: <1548399525.45.0.682804342841.issue35821@roundup.psfhosted.org>


Chris Jerdonek <chris.jerdonek at gmail.com> added the comment:

Thanks for the diagram. How about the following as a replacement?

"If this attribute is true and the event isn't rejected by the logger's level and filters, an event passed to this logger will recursively be passed to its parent logger and handled by the parent logger's handlers (after being handled by the original logger's handlers). The logger level and filters only come into play for the very first logger in this chain. For subsequent loggers, only the propagate attribute determines whether the event is passed to the parent."

----------

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

From report at bugs.python.org  Fri Jan 25 02:05:27 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 25 Jan 2019 07:05:27 +0000
Subject: [docs] [issue35666] Update design FAQ about assignment expression
In-Reply-To: <1546704480.61.0.245493701505.issue35666@roundup.psfhosted.org>
Message-ID: <1548399925.29.0.0449631710051.issue35666@roundup.psfhosted.org>


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

> I believe a spot where assignment expressions are explicitly mentioned as not being included in the language, which is no longer the case

Emily, I guess you were referring to this issue in https://bugs.python.org/issue35224#msg334331 . Now that PEP 572 implementation is merged this can be updated.

Thanks

----------
nosy: +emilyemorehouse, xtreak

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

From report at bugs.python.org  Fri Jan 25 02:10:06 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 25 Jan 2019 07:10:06 +0000
Subject: [docs] [issue35666] Update design FAQ about assignment expression
In-Reply-To: <1546704480.61.0.245493701505.issue35666@roundup.psfhosted.org>
Message-ID: <1548400204.4.0.871240425701.issue35666@roundup.psfhosted.org>


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

Ah sorry I think this could be a duplicate of issue34237 where you have added an update.

----------

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

From report at bugs.python.org  Fri Jan 25 05:44:16 2019
From: report at bugs.python.org (Kevin Mai-Hsuan Chia)
Date: Fri, 25 Jan 2019 10:44:16 +0000
Subject: [docs] [issue35826] Typo in example for async with statement with
 condition
Message-ID: <1548413052.91.0.387178410518.issue35826@roundup.psfhosted.org>


New submission from Kevin Mai-Hsuan Chia <kevin at mhchia.com>:

In the [example](https://docs.python.org/3.8/library/asyncio-sync.html#asyncio.Condition) of the equivalent code to the `async with statement`:
```python
cond = asyncio.Condition()

# ... later
await lock.acquire()
try:
    await cond.wait()
finally:
    lock.release()
```

`lock.acquire()` should be replaced by `cond.acquire()`, and `lock.release()` replaced by `cond.release()`. So the resulting code snippet becomes:

```python
cond = asyncio.Condition()

# ... later
await cond.acquire()
try:
    await cond.wait()
finally:
    cond.release()
```

----------
assignee: docs at python
components: Documentation
messages: 334349
nosy: docs at python, mhchia
priority: normal
severity: normal
status: open
title: Typo in example for async with statement with condition
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Fri Jan 25 05:45:15 2019
From: report at bugs.python.org (Kevin Mai-Hsuan Chia)
Date: Fri, 25 Jan 2019 10:45:15 +0000
Subject: [docs] [issue35826] Typo in example for async with statement with
 condition
In-Reply-To: <1548413052.91.0.387178410518.issue35826@roundup.psfhosted.org>
Message-ID: <1548413114.61.0.24849994852.issue35826@roundup.psfhosted.org>


Kevin Mai-Hsuan Chia <kevin at mhchia.com> added the comment:

In the [example](https://docs.python.org/3.8/library/asyncio-sync.html#asyncio.Condition) of the equivalent code to the `async with` statement:
```python
cond = asyncio.Condition()

# ... later
await lock.acquire()
try:
    await cond.wait()
finally:
    lock.release()
```

`lock.acquire()` should be replaced by `cond.acquire()`, and `lock.release()` replaced by `cond.release()`. So the resulting code snippet becomes:

```python
cond = asyncio.Condition()

# ... later
await cond.acquire()
try:
    await cond.wait()
finally:
    cond.release()
```

----------

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

From report at bugs.python.org  Fri Jan 25 07:05:07 2019
From: report at bugs.python.org (Ori Avtalion)
Date: Fri, 25 Jan 2019 12:05:07 +0000
Subject: [docs] [issue35827] C API dictionary views type checkers are not
 documented
Message-ID: <1548417904.67.0.718119168094.issue35827@roundup.psfhosted.org>


New submission from Ori Avtalion <ori at avtalion.name>:

dictobject.h defines several helpers to ease checking of dictionary view types. If they are meant to be part of the API, they should be documented.

PyDictKeys_Check
PyDictItems_Check
PyDictValues_Check
PyDictViewSet_Check

Should they be added to dict.rst, or a separate file?

----------
assignee: docs at python
components: Documentation
messages: 334355
nosy: docs at python, salty-horse
priority: normal
severity: normal
status: open
title: C API dictionary views type checkers are not documented
type: enhancement
versions: Python 3.6

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

From report at bugs.python.org  Fri Jan 25 08:32:43 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 25 Jan 2019 13:32:43 +0000
Subject: [docs] [issue35821] Clarify when logging events are propagated when
 propagate is true
In-Reply-To: <1548360439.22.0.955979079327.issue35821@roundup.psfhosted.org>
Message-ID: <1548423160.6.0.115582801338.issue35821@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

That isn't quite accurate. A logger's attached handlers will always be offered a chance to handle an event if the logger's level and filters allow. However, the event is not actually passed to ancestor loggers - it is directly offered to any handlers attached to ancestor loggers, until a logger is encountered where propagate is false - and that is the last logger whose handlers are offered the event. All handlers have their own levels and filters and may or may not process an event according to those levels and filters.

----------

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

From report at bugs.python.org  Fri Jan 25 08:45:02 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 25 Jan 2019 13:45:02 +0000
Subject: [docs] [issue30548] typo in documentation for create_autospec
In-Reply-To: <1496394381.09.0.91116482689.issue30548@psf.upfronthosting.co.za>
Message-ID: <1548423900.23.0.759804680211.issue30548@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

Mario is right that this isn't a typo.  Here's a code example to illustrate what he said:

>>> class MyClass:
...     a = 3
...     def foo(self): pass
...
>>> mock_class = create_autospec(MyClass)
>>> mock_class
<MagicMock spec='MyClass' id='16678696'>
>>> mock_class()
<NonCallableMagicMock name='mock()' spec='MyClass' id='16752016'>
>>> mock_class.foo
<MagicMock name='mock.foo' spec='function' id='16751032'>

>>> mock_instance = create_autospec(MyClass, instance=True)
>>> mock_instance
<NonCallableMagicMock spec='MyClass' id='16757832'>
>>> mock_instance()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'NonCallableMagicMock' object is not callable
>>> mock_instance.foo
<MagicMock name='mock.foo' spec='function' id='16750024'>

As per the docs, the instance object uses the class as the spec and it isn't callable, whereas the mock class is.  Would adding this example to the docs help or would a different code example help make this less misleading?

----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Fri Jan 25 09:15:38 2019
From: report at bugs.python.org (Chris Jerdonek)
Date: Fri, 25 Jan 2019 14:15:38 +0000
Subject: [docs] [issue35821] Clarify when logging events are propagated when
 propagate is true
In-Reply-To: <1548360439.22.0.955979079327.issue35821@roundup.psfhosted.org>
Message-ID: <1548425735.77.0.951546919363.issue35821@roundup.psfhosted.org>


Chris Jerdonek <chris.jerdonek at gmail.com> added the comment:

I'm not sure which part of what I wrote you think is inaccurate. All of what you wrote matches what I was trying to convey.

For example, my saying "pass to the parent logger" corresponds to the "set current logger to parent" box in the diagram. And by "handled by the parent logger's handlers" I meant "directly offered to any handlers attached to ancestor loggers." And "only the propagate attribute determines whether the event is passed" matches your "until a logger is encountered where propagate is false."

----------

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

From report at bugs.python.org  Fri Jan 25 18:10:31 2019
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 25 Jan 2019 23:10:31 +0000
Subject: [docs] [issue35826] Typo in example for async with statement with
 condition
In-Reply-To: <1548413052.91.0.387178410518.issue35826@roundup.psfhosted.org>
Message-ID: <1548457828.64.0.253737031509.issue35826@roundup.psfhosted.org>


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

Please submit a PR!

----------
components: +asyncio -Documentation
keywords: +easy
nosy: +asvetlov, yselivanov

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

From report at bugs.python.org  Fri Jan 25 18:45:53 2019
From: report at bugs.python.org (Carol Willing)
Date: Fri, 25 Jan 2019 23:45:53 +0000
Subject: [docs] [issue35826] Typo in example for async with statement with
 condition
In-Reply-To: <1548413052.91.0.387178410518.issue35826@roundup.psfhosted.org>
Message-ID: <1548459951.9.0.90856523205.issue35826@roundup.psfhosted.org>


Change by Carol Willing <willingc at gmail.com>:


----------
nosy: +willingc

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

From report at bugs.python.org  Fri Jan 25 19:55:35 2019
From: report at bugs.python.org (Stefan Seefeld)
Date: Sat, 26 Jan 2019 00:55:35 +0000
Subject: [docs] [issue35830] building multiple (binary) packages from a
 single project
Message-ID: <1548464133.32.0.379789250574.issue35830@roundup.psfhosted.org>


New submission from Stefan Seefeld <stefan at seefeld.name>:

I'm working on a project that I'd like to split into multiple separately installable components. The main component is a command-line tool without any external dependencies. Another component is a GUI frontend that adds some third-party dependencies.
Therefore, I'd like to distribute the code in a single source package, but separate binary packages (so users can install only what they actually need).

I couldn't find any obvious way to support such a scenario with either `distutils` nor `setuptools`. Is there an easy solution to this ? (I'm currently thinking of adding two `setup()` calls to my `setup.py` script. That would then call all commands twice, so I'd need to override the `sdist` command to only build a single (joint) source package.
Is there a better way to achieve what I want ?

----------
assignee: docs at python
components: Distutils, Documentation
messages: 334381
nosy: docs at python, dstufft, eric.araujo, stefan
priority: normal
severity: normal
status: open
title: building multiple (binary) packages from a single project
type: behavior

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

From report at bugs.python.org  Fri Jan 25 20:10:54 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Sat, 26 Jan 2019 01:10:54 +0000
Subject: [docs] [issue35830] building multiple (binary) packages from a
 single project
In-Reply-To: <1548464133.32.0.379789250574.issue35830@roundup.psfhosted.org>
Message-ID: <1548465052.66.0.195175263975.issue35830@roundup.psfhosted.org>


Steven D'Aprano <steve+python at pearwood.info> added the comment:

This is a bug tracker for reporting bugs and enhancement requests, not a help desk.

Do you have a *specific* feature request or a bug to report? If not, you should ask this on a community forum such as Stackoverflow, Reddit's r/learnpython, the Python-list mailing list or the Python IRC channel.

----------
nosy: +steven.daprano

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

From report at bugs.python.org  Fri Jan 25 20:14:01 2019
From: report at bugs.python.org (Stefan Seefeld)
Date: Sat, 26 Jan 2019 01:14:01 +0000
Subject: [docs] [issue35830] building multiple (binary) packages from a
 single project
In-Reply-To: <1548464133.32.0.379789250574.issue35830@roundup.psfhosted.org>
Message-ID: <1548465240.46.0.626000646076.issue35830@roundup.psfhosted.org>


Stefan Seefeld <stefan at seefeld.name> added the comment:

Yes. Depending on the answer to my question(s), the request either becomes: "please add support for this use-case", or "this use-case isn't documented properly", i.e. a feature request or a bug report. You choose. :-)

----------

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

From report at bugs.python.org  Fri Jan 25 21:28:43 2019
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 26 Jan 2019 02:28:43 +0000
Subject: [docs] [issue35830] building multiple (binary) packages from a
 single project
In-Reply-To: <1548464133.32.0.379789250574.issue35830@roundup.psfhosted.org>
Message-ID: <1548469721.97.0.477736234133.issue35830@roundup.psfhosted.org>


?ric Araujo <merwok at netwok.org> added the comment:

The way to achieve this is to make sure your two components live in two separate directories, each with its setup.py.

This is the simple way that works with distutils/setuptools and pip install-from-vcs (you can install from a subdir of a repo).

----------

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

From report at bugs.python.org  Fri Jan 25 23:06:32 2019
From: report at bugs.python.org (Mitchell L Model)
Date: Sat, 26 Jan 2019 04:06:32 +0000
Subject: [docs] [issue35831] Format Spec example says limited to 3.1+ but
 works in 2.7
In-Reply-To: <1548475560.75.0.51760850853.issue35831@roundup.psfhosted.org>
Message-ID: <1548475592.52.0.192090566788.issue35831@roundup.psfhosted.org>


Change by Mitchell L Model <mlm at users.sourceforge.net>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python

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

From report at bugs.python.org  Fri Jan 25 23:12:45 2019
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Sat, 26 Jan 2019 04:12:45 +0000
Subject: [docs] [issue35831] Format Spec example says limited to 3.1+ but
 works in 2.7
In-Reply-To: <1548475560.75.0.51760850853.issue35831@roundup.psfhosted.org>
Message-ID: <1548475963.28.0.805560598266.issue35831@roundup.psfhosted.org>


Fred L. Drake, Jr. <fdrake at gmail.com> added the comment:

The 3.X docs generally don't refer to the 2.X series.

What that comment is pointing out is that leaving the field identifier out (the number inside the {...} placeholder syntax) was not in the 3.0, but added in 3.1.

Unfortunately, I don't have a 3.0 interpreter available to show the exception that's raised.

No change is required.

----------
nosy: +fdrake
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Jan 26 00:54:44 2019
From: report at bugs.python.org (Kevin Mai-Hsuan Chia)
Date: Sat, 26 Jan 2019 05:54:44 +0000
Subject: [docs] [issue35826] Typo in example for async with statement with
 condition
In-Reply-To: <1548413052.91.0.387178410518.issue35826@roundup.psfhosted.org>
Message-ID: <1548482083.5.0.427287354984.issue35826@roundup.psfhosted.org>


Change by Kevin Mai-Hsuan Chia <kevin at mhchia.com>:


----------
keywords: +patch
pull_requests: +11511
stage:  -> patch review

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

From report at bugs.python.org  Sat Jan 26 00:54:53 2019
From: report at bugs.python.org (Kevin Mai-Hsuan Chia)
Date: Sat, 26 Jan 2019 05:54:53 +0000
Subject: [docs] [issue35826] Typo in example for async with statement with
 condition
In-Reply-To: <1548413052.91.0.387178410518.issue35826@roundup.psfhosted.org>
Message-ID: <1548482092.05.0.184818268727.issue35826@roundup.psfhosted.org>


Change by Kevin Mai-Hsuan Chia <kevin at mhchia.com>:


----------
keywords: +patch, patch
pull_requests: +11511, 11512
stage:  -> patch review

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

From report at bugs.python.org  Sat Jan 26 00:55:00 2019
From: report at bugs.python.org (Kevin Mai-Hsuan Chia)
Date: Sat, 26 Jan 2019 05:55:00 +0000
Subject: [docs] [issue35826] Typo in example for async with statement with
 condition
In-Reply-To: <1548413052.91.0.387178410518.issue35826@roundup.psfhosted.org>
Message-ID: <1548482099.5.0.673340923366.issue35826@roundup.psfhosted.org>


Change by Kevin Mai-Hsuan Chia <kevin at mhchia.com>:


----------
keywords: +patch, patch, patch
pull_requests: +11511, 11512, 11514
stage:  -> patch review

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

From report at bugs.python.org  Sat Jan 26 00:55:07 2019
From: report at bugs.python.org (Kevin Mai-Hsuan Chia)
Date: Sat, 26 Jan 2019 05:55:07 +0000
Subject: [docs] [issue35826] Typo in example for async with statement with
 condition
In-Reply-To: <1548413052.91.0.387178410518.issue35826@roundup.psfhosted.org>
Message-ID: <1548482106.75.0.972617673633.issue35826@roundup.psfhosted.org>


Change by Kevin Mai-Hsuan Chia <kevin at mhchia.com>:


----------
keywords: +patch, patch, patch, patch
pull_requests: +11511, 11512, 11513, 11514
stage:  -> patch review

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

From pydoc84 at scotdoyle.com  Fri Jan 25 14:21:28 2019
From: pydoc84 at scotdoyle.com (pydoc84 at scotdoyle.com)
Date: Fri, 25 Jan 2019 19:21:28 +0000 (UTC)
Subject: [docs] Doctest directives are not rendered into html or text?
Message-ID: <alpine.LNX.2.20.1901251900460.8638@mx.scotdoyle.com>

The html and text documentation (3.6, 3.7, 3.8) for doctest directives at
  Library Reference -> 26.3 Doctest -> 26.3.3.6 Directives
is missing the actual directives, but they are visible in the
source at master/Doc/library/doctest.rst.


For example, doctest.rst has:

>>> print(list(range(20))) # doctest: +NORMALIZE_WHITESPACE

while the web and text documentation has:

>>> print(list(range(20)))

From report at bugs.python.org  Sat Jan 26 13:12:51 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 26 Jan 2019 18:12:51 +0000
Subject: [docs] [issue5028] tokenize.generate_tokens doesn't always return
 logical line
In-Reply-To: <1232588343.15.0.723713394492.issue5028@psf.upfronthosting.co.za>
Message-ID: <1548526369.65.0.373140789582.issue5028@roundup.psfhosted.org>


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


----------
keywords: +patch
pull_requests: +11518
stage: needs patch -> patch review

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

From report at bugs.python.org  Sat Jan 26 13:13:01 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 26 Jan 2019 18:13:01 +0000
Subject: [docs] [issue5028] tokenize.generate_tokens doesn't always return
 logical line
In-Reply-To: <1232588343.15.0.723713394492.issue5028@psf.upfronthosting.co.za>
Message-ID: <1548526379.2.0.782660524918.issue5028@roundup.psfhosted.org>


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


----------
keywords: +patch, patch
pull_requests: +11518, 11519
stage: needs patch -> patch review

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

From report at bugs.python.org  Sat Jan 26 13:13:10 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 26 Jan 2019 18:13:10 +0000
Subject: [docs] [issue5028] tokenize.generate_tokens doesn't always return
 logical line
In-Reply-To: <1232588343.15.0.723713394492.issue5028@psf.upfronthosting.co.za>
Message-ID: <1548526388.99.0.153852026733.issue5028@roundup.psfhosted.org>


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


----------
keywords: +patch, patch, patch
pull_requests: +11518, 11519, 11520
stage: needs patch -> patch review

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

From report at bugs.python.org  Sat Jan 26 13:13:20 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 26 Jan 2019 18:13:20 +0000
Subject: [docs] [issue5028] tokenize.generate_tokens doesn't always return
 logical line
In-Reply-To: <1232588343.15.0.723713394492.issue5028@psf.upfronthosting.co.za>
Message-ID: <1548526398.82.0.301753366078.issue5028@roundup.psfhosted.org>


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


----------
keywords: +patch, patch, patch, patch
pull_requests: +11518, 11519, 11520, 11521
stage: needs patch -> patch review

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

From report at bugs.python.org  Sat Jan 26 19:48:38 2019
From: report at bugs.python.org (Martin Panter)
Date: Sun, 27 Jan 2019 00:48:38 +0000
Subject: [docs] [issue19670] SimpleCookie Generates Non-RFC6265-Compliant
 Cookies
In-Reply-To: <1384979004.61.0.0353093814459.issue19670@psf.upfronthosting.co.za>
Message-ID: <1548550116.99.0.0523359139814.issue19670@roundup.psfhosted.org>


Martin Panter <vadmium+py at gmail.com> added the comment:

I think the solution here is to document what ?SimpleCookie.value_encode? really does: RFC 2109 quoted-string escaping. If you want to a generate RFC-6265-compliant Set-Cookie string, do not include non-compliant characters in the cookie value, and consider using BaseCookie rather than SimpleCookie, especially if your ?morsel? values are enclosed in double quotes.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, martin.panter

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

From report at bugs.python.org  Sat Jan 26 21:00:41 2019
From: report at bugs.python.org (Martin Panter)
Date: Sun, 27 Jan 2019 02:00:41 +0000
Subject: [docs] [issue11315] unicode support in Cookie module
In-Reply-To: <1298606703.83.0.56959729812.issue11315@psf.upfronthosting.co.za>
Message-ID: <1548554435.57.0.131596624782.issue11315@roundup.psfhosted.org>


Martin Panter <vadmium+py at gmail.com> added the comment:

Sorry, but changing to bytes after ten years of using str in this module in Python 3 is not going to happen. Let?s just document the state of Python 2 (see ?ric: https://bugs.python.org/issue11315#msg129448).

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, ezio.melotti, martin.panter, vstinner
title: Fix type regression in http.cookies.load (want bytes, not str) -> unicode support in Cookie module
versions: +Python 2.7 -Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

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

From arthur.p.goldberg at mssm.edu  Sat Jan 26 11:03:28 2019
From: arthur.p.goldberg at mssm.edu (Goldberg, Arthur P)
Date: Sat, 26 Jan 2019 16:03:28 +0000
Subject: [docs]
 https://docs.python.org/3/tutorial/errors.html#defining-clean-up-actions
Message-ID: <52428811-706C-4654-B3F2-1FCBE7AFE4D6@mssm.edu>

I am suggesting an improvement. The page says ?As you can see, the finally clause is executed in any event?. However the example above this sentence does not illustrate what it says.
It would be better to have an example that includes a raise, break, continue, or return in the try before finally. I think it would be best to include 2 of these, probably raise and return. I can create an example if you?d like.

Regards
Arthur

Arthur Goldberg, PhD
Associate Professor of Genetics and Genomic Sciences
Institute for Data Science and Genomic Technology
Mount Sinai School of Medicine
1255 Fifth Ave., Suite C-2
New York, NY 10029
646 526 5020
Karr Lab
Arthur.Goldberg at mssm.edu<mailto:Arthur.Goldberg at mssm.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190126/f630f48d/attachment-0001.html>

From report at bugs.python.org  Sun Jan 27 06:24:00 2019
From: report at bugs.python.org (SilentGhost)
Date: Sun, 27 Jan 2019 11:24:00 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548588240.57.0.0101350773684.issue35835@roundup.psfhosted.org>


Change by SilentGhost <ghost.adh at runbox.com>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> needs patch

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

From report at bugs.python.org  Sun Jan 27 07:13:49 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 27 Jan 2019 12:13:49 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548591227.99.0.750411969903.issue35835@roundup.psfhosted.org>


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

> New in version 3.7: breakpoint() replaces the previous line.

replaces sounds little more like removed or deprecated to me. How about the below under pdb.set_trace() doc and example using it in the beginning?

New in version 3.7: breakpoint() is a convenience function that internally calls pdb.set_trace()

Thanks

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

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

From report at bugs.python.org  Sun Jan 27 07:19:03 2019
From: report at bugs.python.org (jcrmatos)
Date: Sun, 27 Jan 2019 12:19:03 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548591541.89.0.328366873762.issue35835@roundup.psfhosted.org>


jcrmatos <jcrmatos at gmail.com> added the comment:

Hello,

What about like this
import pdb; pdb.set_trace()
New in version 3.7: breakpoint() is preferable to using the previous line.

Thanks,

JM

----------

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

From report at bugs.python.org  Sun Jan 27 07:26:31 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 27 Jan 2019 12:26:31 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548591989.61.0.713441565141.issue35835@roundup.psfhosted.org>


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

I didn't want the doc to sound like breakpoint() is encouraged since it's optional and a shortcut. Hence my personal preference to just add a note with link to breakpoint() that it does the same thing. I will wait for someone else to rephrase it better since I am not a native speaker myself.

Thanks

----------

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

From report at bugs.python.org  Sun Jan 27 08:21:14 2019
From: report at bugs.python.org (Mark Lawrence)
Date: Sun, 27 Jan 2019 13:21:14 +0000
Subject: [docs] [issue11315] unicode support in Cookie module
In-Reply-To: <1298606703.83.0.56959729812.issue11315@psf.upfronthosting.co.za>
Message-ID: <1548595271.3.0.699527488002.issue11315@roundup.psfhosted.org>


Change by Mark Lawrence <breamoreboy at gmail.com>:


----------
nosy:  -BreamoreBoy

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

From report at bugs.python.org  Sun Jan 27 08:51:29 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 27 Jan 2019 13:51:29 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548597085.24.0.0326589091436.issue35835@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

I agree with Karthikeyan.  If it's added to the pdb doc page, I think the existing text should stay as it is, but a 'New in 3.7' added after it.

Something like:

The typical usage to break into the debugger from a running program is to insert

import pdb; pdb.set_trace()

at the location you want to break into the debugger. You can then step through the code following this statement, and continue running without the debugger using the continue command.

New in version 3.7: The built-in :func:`breakpoint()`, when called with defaults, can be used instead of ``import pdb; pdb.set_trace()``.

----------
nosy: +cheryl.sabella

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

From report at bugs.python.org  Sun Jan 27 08:58:06 2019
From: report at bugs.python.org (jcrmatos)
Date: Sun, 27 Jan 2019 13:58:06 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548597482.35.0.232398514917.issue35835@roundup.psfhosted.org>


jcrmatos <jcrmatos at gmail.com> added the comment:

Hello,

In my first message I said exactly that (the replacement used the previous text, if you check it).

I'm ok with the wording from Cheryl. How about you Karthikeyan?

Thanks,

JM

----------

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

From report at bugs.python.org  Sun Jan 27 09:32:50 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 27 Jan 2019 14:32:50 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548599568.57.0.275837213565.issue35835@roundup.psfhosted.org>


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

I am ok with Cheryl's idea too.

----------

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

From report at bugs.python.org  Sun Jan 27 14:42:04 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 27 Jan 2019 19:42:04 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548618120.65.0.00993683521842.issue35835@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

@jcrmatos, would you like to create a Github pull request with the change?

----------

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

From report at bugs.python.org  Sun Jan 27 14:42:18 2019
From: report at bugs.python.org (Barry A. Warsaw)
Date: Sun, 27 Jan 2019 19:42:18 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548618136.46.0.837007549472.issue35835@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/issue35835>
_______________________________________

From report at bugs.python.org  Sun Jan 27 14:43:27 2019
From: report at bugs.python.org (jcrmatos)
Date: Sun, 27 Jan 2019 19:43:27 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548618202.23.0.363669961452.issue35835@roundup.psfhosted.org>


jcrmatos <jcrmatos at gmail.com> added the comment:

Hello,

I'm sorry, I have no idea how to do it.

JM

----------

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

From report at bugs.python.org  Sun Jan 27 17:19:43 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 27 Jan 2019 22:19:43 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548627577.8.0.75312520061.issue35835@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

@jcrmatos,

No problem.  :-)  If you are interested in learning how, we can guide you.  However, if you'd rather not, then that's OK too and we'll make the patch.  Just let us know which you'd prefer.

If you need help deciding, take a look at the devguide on how to get started.  
https://devguide.python.org/

Thanks!

----------

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

From report at bugs.python.org  Sun Jan 27 22:34:48 2019
From: report at bugs.python.org (jcrmatos)
Date: Mon, 28 Jan 2019 03:34:48 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548646484.19.0.84061378698.issue35835@roundup.psfhosted.org>


jcrmatos <jcrmatos at gmail.com> added the comment:

Hello,

Yes, I'm interested in learning, thanks.
I use Windows not Linux. Is that a problem?
I will read the guide and let you know if I have any questions. Thanks again.

JM

----------

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

From report at bugs.python.org  Sun Jan 27 23:12:10 2019
From: report at bugs.python.org (jcrmatos)
Date: Mon, 28 Jan 2019 04:12:10 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548648725.8.0.336331301582.issue35835@roundup.psfhosted.org>


jcrmatos <jcrmatos at gmail.com> added the comment:

Hello,

I'm using Github web interface.
I did these steps:
- Forked cpython and changed the pdb.rst file.
- Created a branch called "fix-issue-35835".
- Made the commit with description "Add reference to Python 3.7 new function breakpoint()".
- Made the pull request with title "bpo-35835: Add reference to Python 3.7 new function breakpoint()".
- Made the merge commit.

Now I have an option to delete the fix-issue-35835 branch.
Should I do it? I read some Git tutorials and I think I can, but can you confirm?

After that, how should I procede to create the patch?

Thanks,

JM

----------

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

From report at bugs.python.org  Sun Jan 27 23:40:17 2019
From: report at bugs.python.org (jcrmatos)
Date: Mon, 28 Jan 2019 04:40:17 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548650412.47.0.593397222761.issue35835@roundup.psfhosted.org>


jcrmatos <jcrmatos at gmail.com> added the comment:

Hello,

On the previous message I forgot to mention that the pull request was made in my fork, not the cpython repo.
Should I made a PR in the cpython repo at this point?

Thanks,

JM

----------

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

From report at bugs.python.org  Sun Jan 27 23:44:43 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 28 Jan 2019 04:44:43 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548650678.77.0.290512215771.issue35835@roundup.psfhosted.org>


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

@jcrmatos yes, you should be making a PR to CPython repo's master branch since GitHub PRs are accepted. I hope also need to sign the CLA for your contribution to get merged though it's a documentation fix.

Thanks

----------

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

From report at bugs.python.org  Sun Jan 27 23:47:48 2019
From: report at bugs.python.org (jcrmatos)
Date: Mon, 28 Jan 2019 04:47:48 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548650863.1.0.534210955691.issue35835@roundup.psfhosted.org>


jcrmatos <jcrmatos at gmail.com> added the comment:

Hello,

Yes, I signed the CLA and now I have to wait at least 1 business day.
So I will wait for that confirmation before making the PR to the CPython repo.

Thanks,

JM

----------

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

From report at bugs.python.org  Mon Jan 28 06:39:14 2019
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 28 Jan 2019 11:39:14 +0000
Subject: [docs] [issue35822] _queue _queuemodule.c is missing inside the
 Setup file
In-Reply-To: <1548374932.46.0.67529287669.issue35822@roundup.psfhosted.org>
Message-ID: <1548675552.19.0.694803580972.issue35822@roundup.psfhosted.org>


INADA Naoki <songofacandy at gmail.com> added the comment:

_queue is normal extension module, not builtin module.
In my environment:

>>> import _queue
>>> _queue.__file__
'/usr/local/Cellar/python/3.7.2_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/lib-dynload/_queue.cpython-37m-darwin.so'

It seems your environment is somewhat broken.

----------
nosy: +inada.naoki

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

From report at bugs.python.org  Mon Jan 28 08:36:16 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 28 Jan 2019 13:36:16 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548682570.67.0.963329567646.issue35835@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

@jcrmatos - Sounds like you're on the right track.  :-)

Based on the steps you've outlined, I just had one question.  Were you able to rebuild the docs locally in order to see how your changes looked?  Here's the direct link to building the docs:
https://devguide.python.org/documenting/#building-doc

In section 7.5.1, it mentions Windows, so you should be able to follow that.  Although, I've had to use `./make html` in Powershell, so if `make html` doesn't work, then try that.

----------

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

From report at bugs.python.org  Mon Jan 28 09:14:50 2019
From: report at bugs.python.org (jcrmatos)
Date: Mon, 28 Jan 2019 14:14:50 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548684885.45.0.485270944264.issue35835@roundup.psfhosted.org>


jcrmatos <jcrmatos at gmail.com> added the comment:

Hello,

I didn't do anything locally. I did the change and preview it on GitHub's web interface.

Has I said, I did a PR to my own fork and now I think I have to do a PR to the cpython master. Is that correct?
The PR to my own fork was required, or the commit was enough?

Now I have an option to delete the fix-issue-35835 branch.
Should I do it? I read some Git tutorials and I think I can, but can you confirm?


Thanks in advance,

JM

----------

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

From report at bugs.python.org  Mon Jan 28 10:22:54 2019
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 28 Jan 2019 15:22:54 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548688970.37.0.679693187445.issue35835@roundup.psfhosted.org>


Cheryl Sabella <cheryl.sabella at gmail.com> added the comment:

As Karthikeyan said, you do need to open a PR against the CPython master.  I'm not a Git expert, but this page (section 3.3) discusses the steps to open that PR:
https://devguide.python.org/pullrequest/

Those are the steps I follow and it's a good write-up so there's not much I can add to it.  I don't think the PR on your own fork was required.  It doesn't usually ask to delete the branch until the PR against CPython master has been merged (which is the last step in section 3.3), but since you merged against your own fork, that's probably why it's asking now.  Do you still get an option to create a PR against CPython master using your branch as per this part of section 3.3?

> Finally go on https://github.com/<your-username>/cpython: you will see a box with the branch you just pushed and a green button that allows you to create a pull request against the official CPython repository.

----------

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

From report at bugs.python.org  Mon Jan 28 13:03:15 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 28 Jan 2019 18:03:15 +0000
Subject: [docs] [issue35843] importlib.util docs for namespace packages
 innaccurate
Message-ID: <1548698590.94.0.426601552573.issue35843@roundup.psfhosted.org>


New submission from Anthony Sottile <asottile at umich.edu>:

For instance:


# `a` is an empty directory, a PEP 420 namespace package

>>> import importlib.util
>>> importlib.util.find_spec('a')
ModuleSpec(name='a', loader=None, origin='namespace', submodule_search_locations=_NamespacePath(['/tmp/x/a']))


https://docs.python.org/3/library/importlib.html#importlib.machinery.ModuleSpec.origin

> ...  Normally ?origin? should be set, but it may be None (the default) which indicates it is unspecified (e.g. for namespace packages).

above the `origin` is `'namespace'`

https://docs.python.org/3/library/importlib.html#importlib.machinery.ModuleSpec.submodule_search_locations

> List of strings for where to find submodules, if a package (None otherwise).

However the `_NamespacePath` object above is not indexable:

>>> x = importlib.util.find_spec('a').submodule_search_locations
>>> x[0]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: '_NamespacePath' object does not support indexing


I can work around however with:

>>> next(iter(x))
'/tmp/x/a'


======================


so I guess a few things can/should come out of this:

- Document the `'namespace'` origin
- Document that `submodule_search_paths` is a Sized[str] instead
- Add `__getitem__` to `_NamespacePath` such that it implements the full `Sized` protocol

----------
assignee: docs at python
components: Documentation
messages: 334484
nosy: Anthony Sottile, docs at python
priority: normal
severity: normal
status: open
title: importlib.util docs for namespace packages innaccurate
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Jan 28 13:07:30 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 28 Jan 2019 18:07:30 +0000
Subject: [docs] [issue35843] importlib.util docs for namespace packages
 innaccurate
In-Reply-To: <1548698590.94.0.426601552573.issue35843@roundup.psfhosted.org>
Message-ID: <1548698846.5.0.764327842913.issue35843@roundup.psfhosted.org>


Anthony Sottile <asottile at umich.edu> added the comment:

Hmmm, it appears this was changed in python3.7 to have `None` for the origin instead of `'namespace'` -- however the `submodule_search_locations` is still not indexable:



>>> importlib.util.find_spec('a')
ModuleSpec(name='a', loader=None, submodule_search_locations=_NamespacePath(['/tmp/x/a']))
>>> importlib.util.find_spec('a').origin
>>> spec = importlib.util.find_spec('a')
>>> spec.submodule_search_locations
_NamespacePath(['/tmp/x/a'])
>>> spec.submodule_search_locations[0]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: '_NamespacePath' object does not support indexing

----------

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

From report at bugs.python.org  Mon Jan 28 13:24:01 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 28 Jan 2019 18:24:01 +0000
Subject: [docs] [issue35843] importlib.util docs for namespace packages
 innaccurate
In-Reply-To: <1548698590.94.0.426601552573.issue35843@roundup.psfhosted.org>
Message-ID: <1548699840.44.0.855141680881.issue35843@roundup.psfhosted.org>


Change by Anthony Sottile <asottile at umich.edu>:


----------
keywords: +patch
pull_requests: +11529
stage:  -> patch review

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

From report at bugs.python.org  Mon Jan 28 13:24:07 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 28 Jan 2019 18:24:07 +0000
Subject: [docs] [issue35843] importlib.util docs for namespace packages
 innaccurate
In-Reply-To: <1548698590.94.0.426601552573.issue35843@roundup.psfhosted.org>
Message-ID: <1548699845.7.0.843178891082.issue35843@roundup.psfhosted.org>


Change by Anthony Sottile <asottile at umich.edu>:


----------
keywords: +patch, patch
pull_requests: +11529, 11530
stage:  -> patch review

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

From report at bugs.python.org  Mon Jan 28 13:24:13 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Mon, 28 Jan 2019 18:24:13 +0000
Subject: [docs] [issue35843] importlib.util docs for namespace packages
 innaccurate
In-Reply-To: <1548698590.94.0.426601552573.issue35843@roundup.psfhosted.org>
Message-ID: <1548699851.55.0.626513202299.issue35843@roundup.psfhosted.org>


Change by Anthony Sottile <asottile at umich.edu>:


----------
keywords: +patch, patch, patch
pull_requests: +11529, 11530, 11531
stage:  -> patch review

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

From report at bugs.python.org  Mon Jan 28 13:34:23 2019
From: report at bugs.python.org (jcrmatos)
Date: Mon, 28 Jan 2019 18:34:23 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548700460.25.0.879744230369.issue35835@roundup.psfhosted.org>


Change by jcrmatos <jcrmatos at gmail.com>:


----------
keywords: +patch
pull_requests: +11532
stage: needs patch -> patch review

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

From report at bugs.python.org  Mon Jan 28 13:34:33 2019
From: report at bugs.python.org (jcrmatos)
Date: Mon, 28 Jan 2019 18:34:33 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548700469.37.0.26037553747.issue35835@roundup.psfhosted.org>


Change by jcrmatos <jcrmatos at gmail.com>:


----------
keywords: +patch, patch
pull_requests: +11532, 11533
stage: needs patch -> patch review

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

From report at bugs.python.org  Mon Jan 28 13:34:41 2019
From: report at bugs.python.org (jcrmatos)
Date: Mon, 28 Jan 2019 18:34:41 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548700478.51.0.779756584067.issue35835@roundup.psfhosted.org>


Change by jcrmatos <jcrmatos at gmail.com>:


----------
keywords: +patch, patch, patch
pull_requests: +11532, 11533, 11534
stage: needs patch -> patch review

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

From report at bugs.python.org  Mon Jan 28 13:34:49 2019
From: report at bugs.python.org (jcrmatos)
Date: Mon, 28 Jan 2019 18:34:49 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548700487.66.0.780668101948.issue35835@roundup.psfhosted.org>


Change by jcrmatos <jcrmatos at gmail.com>:


----------
keywords: +patch, patch, patch, patch
pull_requests: +11532, 11533, 11534, 11535
stage: needs patch -> patch review

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

From report at bugs.python.org  Mon Jan 28 13:51:57 2019
From: report at bugs.python.org (jcrmatos)
Date: Mon, 28 Jan 2019 18:51:57 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548701512.89.0.0257729706337.issue35835@roundup.psfhosted.org>


jcrmatos <jcrmatos at gmail.com> added the comment:

I deleted the fork and started again.
This time I didn't PR to my own fork but to cpython master.
It is now waiting for review, "skip news" labeling and CLA (I'm still waiting on my request).

----------

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

From report at bugs.python.org  Mon Jan 28 14:32:44 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 28 Jan 2019 19:32:44 +0000
Subject: [docs] [issue35843] importlib.util docs for namespace packages
 innaccurate
In-Reply-To: <1548698590.94.0.426601552573.issue35843@roundup.psfhosted.org>
Message-ID: <1548703960.09.0.692288699059.issue35843@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/issue35843>
_______________________________________

From report at bugs.python.org  Mon Jan 28 15:28:55 2019
From: report at bugs.python.org (Samuel Grayson)
Date: Mon, 28 Jan 2019 20:28:55 +0000
Subject: [docs] [issue35844] Calling `Multiprocessing.Queue.close()` too
 quickly causes intermittent failure (BrokenPipeError)
Message-ID: <1548707332.73.0.0560406738777.issue35844@roundup.psfhosted.org>


New submission from Samuel Grayson <sam at samgrayson.me>:

If all processes try to close the Queue immediately after someone has written to it, this causes [an error][1] (see the link for more details). Uncommenting any of the `time.sleep`s makes it work consistently again.

    import multiprocessing
    import time
    import logging
    import multiprocessing.util
    multiprocessing.util.log_to_stderr(level=logging.DEBUG)
    
    queue = multiprocessing.Queue(maxsize=10)
    
    def worker(queue):
        queue.put('abcdefghijklmnop')
    
        # "Indicate that no more data will be put on this queue by the
        # current process." --Documentation
        # time.sleep(0.01)
        queue.close()
    
    proc = multiprocessing.Process(target=worker, args=(queue,))
    proc.start()
    
    # "Indicate that no more data will be put on this queue by the current
    # process." --Documentation
    # time.sleep(0.01)
    queue.close()
    
    proc.join()

Perhaps this is because I am not understanding the documentation correctly, but in that case I would contend this is a documentation bug.

    Traceback (most recent call last):
      File "/usr/lib/python3.7/multiprocessing/queues.py", line 242, in _feed
        send_bytes(obj)
      File "/usr/lib/python3.7/multiprocessing/connection.py", line 200, in send_bytes
        self._send_bytes(m[offset:offset + size])
      File "/usr/lib/python3.7/multiprocessing/connection.py", line 404, in _send_bytes
        self._send(header + buf)
      File "/usr/lib/python3.7/multiprocessing/connection.py", line 368, in _send
        n = write(self._handle, buf)
    BrokenPipeError: [Errno 32] Broken pipe

[1]: https://stackoverflow.com/q/51680479/1078199

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 334490
nosy: charmonium, docs at python
priority: normal
severity: normal
status: open
title: Calling `Multiprocessing.Queue.close()` too quickly causes intermittent failure (BrokenPipeError)
versions: Python 3.7

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

From report at bugs.python.org  Mon Jan 28 17:09:10 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 28 Jan 2019 22:09:10 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548713348.55.0.414369248686.issue25592@roundup.psfhosted.org>


Change by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Mon Jan 28 17:17:06 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 28 Jan 2019 22:17:06 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548713822.36.0.976666563634.issue25592@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:

Though it's difficult to say for certain (distutils' option selection logic is obscure and difficult to follow), it seems that Jeroen's analysis is right.

----------
nosy: +pitrou

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

From report at bugs.python.org  Tue Jan 29 02:41:18 2019
From: report at bugs.python.org (Vinay Sajip)
Date: Tue, 29 Jan 2019 07:41:18 +0000
Subject: [docs] [issue35821] Clarify when logging events are propagated when
 propagate is true
In-Reply-To: <1548360439.22.0.955979079327.issue35821@roundup.psfhosted.org>
Message-ID: <1548747674.25.0.102339063449.issue35821@roundup.psfhosted.org>


Vinay Sajip <vinay_sajip at yahoo.co.uk> added the comment:

> I'm not sure which part of what I wrote you think is inaccurate.

It's just that language can be tricky. When you said "pass to the parent logger" this might be misconstrued as some kind of call to a method of the parent logger.

Your OP says that you think "logged to this logger" means (2), but actually it means (1). Expanding with examples:

If the propagate attribute of the logger named A.B.C evaluates to true, any event logged to A.B.C via a method call such as logging.getLogger('A.B.C').error(...) will [subject to passing that logger's level and filter settings] be passed in turn to any handlers attached to loggers named A.B, A and the root logger, after first being passed to any handlers attached to A.B.C. If any logger in the chain A.B.C, A.B, A has its propagate attribute set to false, then that is the last logger whose handlers are offered the event to handle, and propagation stops at that point.

----------

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

From report at bugs.python.org  Tue Jan 29 04:10:07 2019
From: report at bugs.python.org (Ronald Oussoren)
Date: Tue, 29 Jan 2019 09:10:07 +0000
Subject: [docs] [issue35843] importlib.util docs for namespace packages
 innaccurate
In-Reply-To: <1548698590.94.0.426601552573.issue35843@roundup.psfhosted.org>
Message-ID: <1548753002.42.0.893907982151.issue35843@roundup.psfhosted.org>


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

See also #35673.

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

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

From report at bugs.python.org  Tue Jan 29 05:10:17 2019
From: report at bugs.python.org (Henry S. Thompson)
Date: Tue, 29 Jan 2019 10:10:17 +0000
Subject: [docs] [issue12731] python lib re uses obsolete sense of \w in full
 violation of UTS#18 RL1.2a
In-Reply-To: <1313090311.62.0.0473644856742.issue12731@psf.upfronthosting.co.za>
Message-ID: <1548756615.09.0.777541096001.issue12731@roundup.psfhosted.org>


Henry S. Thompson <ht at inf.ed.ac.uk> added the comment:

This issue is also implicated in a failure of isalpha and friends.
Easy way to see this is to compare
>>> isalpha('?')
True
>>> isalpha('?'.lower())
False

This results from the use of a combining character to encode lower-case Turkish dotted i:
>>> len('?'.lower())
2
>>> unicodedata.category('?'.lower()[1])
'Mn'

----------
nosy: +HThompson

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

From report at bugs.python.org  Tue Jan 29 07:17:51 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Tue, 29 Jan 2019 12:17:51 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548764265.89.0.218377130974.issue25592@roundup.psfhosted.org>


Jeroen Demeyer <J.Demeyer at UGent.be> added the comment:

> it seems that Jeroen's analysis is right.

So would you be willing to merge the PR then?

----------

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

From report at bugs.python.org  Tue Jan 29 09:35:47 2019
From: report at bugs.python.org (SilentGhost)
Date: Tue, 29 Jan 2019 14:35:47 +0000
Subject: [docs] [issue35848] readinto is not a method on io.TextIOBase
In-Reply-To: <1548753520.89.0.970608711782.issue35848@roundup.psfhosted.org>
Message-ID: <1548772547.89.0.0469720711192.issue35848@roundup.psfhosted.org>


Change by SilentGhost <ghost.adh at runbox.com>:


----------
assignee:  -> docs at python
components: +Documentation -IO
nosy: +docs at python
stage:  -> needs patch
versions: +Python 3.8

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

From report at bugs.python.org  Tue Jan 29 09:37:53 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 29 Jan 2019 14:37:53 +0000
Subject: [docs] [issue35848] readinto is not a method on io.TextIOBase
In-Reply-To: <1548753520.89.0.970608711782.issue35848@roundup.psfhosted.org>
Message-ID: <1548772671.43.0.0230599316103.issue35848@roundup.psfhosted.org>


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

https://docs.python.org/3/library/io.html#io.TextIOBase

> Base class for text streams. This class provides a character and line based interface to stream I/O. There is no readinto() method because Python?s character strings are immutable. It inherits IOBase. There is no public constructor.

io.TextIOBase docs say there is no readinto method in the documentation.

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

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

From report at bugs.python.org  Tue Jan 29 09:40:10 2019
From: report at bugs.python.org (Roel Schroeven)
Date: Tue, 29 Jan 2019 14:40:10 +0000
Subject: [docs] [issue35851] Make search result in online docs keep their
 position when search finishes
Message-ID: <1548772807.63.0.497905321537.issue35851@roundup.psfhosted.org>


New submission from Roel Schroeven <roel at roelschroeven.net>:

Search in the online documentation shows results while the search continues in the background, which is very nice.

Only problem is: when the search finishes, a line with the text "Search finished, found x page(s) matching the search query." appears which pushes all the search results down a bit. When the result you were looking for was already displayed, you suddenly have to aim the mouse cursor at a new position, or it can happen that you accidentally open the wrong link because of the results not staying in their place.

Is it possible to allocate space for the "Search finished, ..." line from the beginning, so that search results stay in the same place the whole time?

----------
assignee: docs at python
components: Documentation
messages: 334525
nosy: docs at python, roelschroeven
priority: normal
severity: normal
status: open
title: Make search result in online docs keep their position when search finishes
type: enhancement
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue Jan 29 10:11:52 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Tue, 29 Jan 2019 15:11:52 +0000
Subject: [docs] [issue35851] Make search result in online docs keep their
 position when search finishes
In-Reply-To: <1548772807.63.0.497905321537.issue35851@roundup.psfhosted.org>
Message-ID: <1548774710.85.0.990336608753.issue35851@roundup.psfhosted.org>


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

I have minimum experience with CSS but this seems to be a Sphinx level enhancement that needs to be made. The text is set after search completion at [0]. The element [1] to which the text is added has no fixed height and is empty at the beginning so adding a fixed height might ensure the text doesn't push it down. But the relevant file is part of sphinx repo and doesn't have an id associated with it so I am not sure how feasible it is to customize this as part of Python doc distribution.

[0] https://github.com/sphinx-doc/sphinx/blob/97d99f830258a4612a6c77f5be084819634dcbad/sphinx/themes/basic/static/searchtools.js#L299
[1] https://github.com/sphinx-doc/sphinx/blob/97d99f830258a4612a6c77f5be084819634dcbad/sphinx/themes/basic/static/searchtools.js#L133

----------
nosy: +mdk, xtreak
versions:  -Python 2.7, Python 3.4, Python 3.5, Python 3.6

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

From e.reissner at ankrit.de  Tue Jan 29 10:09:39 2019
From: e.reissner at ankrit.de (=?iso-8859-1?Q?Ernst_Rei=DFner?=)
Date: Tue, 29 Jan 2019 15:09:39 +0000
Subject: [docs] socket shutdown
Message-ID: <51656a75fee14540a0031f74e1d63192@ankrit.de>

Hi All,

https://docs.python.org/3/library/socket.html#constants
is missing the constants socket.SHUT_RD and so on...

Greetings,
Mit freundlichen Gr??en
Ernst Rei?ner
[Ankrit Technologies GmbH]
Ankrit Technologies GmbH
Dammstr. 1
86420 Diedorf

www.ankrit.de<http://www.ankrit.de/>
e.reissner at ankrit.de<mailto:e.reissner at ankrit.de>
Tel.: 08238/9667609
Fax.: 08238/9667612

Handelsregister Augsburg HRB 26664
Gesch?ftsf?hrer: Julia Sailer
Diese E-Mail enth?lt vertrauliche und/oder rechtlich gesch?tzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt?mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190129/0283692c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4531 bytes
Desc: image001.jpg
URL: <http://mail.python.org/pipermail/docs/attachments/20190129/0283692c/attachment.jpg>

From connor415 at gmail.com  Tue Jan 29 13:41:23 2019
From: connor415 at gmail.com (Hugh O'Connor)
Date: Tue, 29 Jan 2019 19:41:23 +0100
Subject: [docs] Python Documentation
Message-ID: <CABiZPXmHyr7OVf9fwx=aUeASrGqPOvjWO-rn5DKxtJLX3qd9bw@mail.gmail.com>

Hello

I am looking to use Python offline so I got your documentation. It is quite
a long list of documents, not just one. Can you help me make sense of this
list? I just wanted to look up one in-built function.

Thanks

Hugh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190129/1bb89dd4/attachment.html>

From report at bugs.python.org  Wed Jan 30 09:54:31 2019
From: report at bugs.python.org (Utkarsh Gupta)
Date: Wed, 30 Jan 2019 14:54:31 +0000
Subject: [docs] [issue30951] Documentation error in inspect module
In-Reply-To: <1500312575.69.0.52467451771.issue30951@psf.upfronthosting.co.za>
Message-ID: <1548860069.37.0.187942699937.issue30951@roundup.psfhosted.org>


Utkarsh Gupta <guptautkarsh2102 at gmail.com> added the comment:

Serhiy: What change d'you possibly suggest then?

----------

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

From ajsccacho at gmail.com  Wed Jan 30 09:46:32 2019
From: ajsccacho at gmail.com (Antonio Cacho)
Date: Wed, 30 Jan 2019 14:46:32 +0000
Subject: [docs] bug in asyncio-subprocess documentation web pages
Message-ID: <5C51B8C8.2050505@gmail.com>

Hi
There is a bug In these asyncio-subprocess web pages:
     https://docs.python.org/3.8/library/asyncio-subprocess.html
     https://docs.python.org/3.7/library/asyncio-subprocess.html
The bug occurs in the first example program. It lacks the conditional 
use of WindowsProactorEventLoopPolicy from the sys package.
The erroneous code and the tested working code are attached.
I couldn't find this bug in the documenting issue tracker, but I doubt 
no one has stumbled on it before, and I was in hurry.
Cheers,
     Antonio Jose Cacho






---
Este e-mail foi verificado em termos de v?rus pelo software antiv?rus Avast.
https://www.avast.com/antivirus
-------------- next part --------------
import asyncio

async def run(cmd):
    proc = await asyncio.create_subprocess_shell(
        cmd,
        stdout=asyncio.subprocess.PIPE,
        stderr=asyncio.subprocess.PIPE)

    stdout, stderr = await proc.communicate()

    print(f'[{cmd!r} exited with {proc.returncode}]')
    if stdout:
        print(f'[stdout]\n{stdout.decode()}')
    if stderr:
        print(f'[stderr]\n{stderr.decode()}')

asyncio.run(run('ls /zzz'))
-------------- next part --------------

import asyncio
import sys

async def run(cmd):
    proc = await asyncio.create_subprocess_shell(
        cmd,
        stdout=asyncio.subprocess.PIPE,
        stderr=asyncio.subprocess.PIPE)

    stdout, stderr = await proc.communicate()

    print(f'[{cmd!r} exited with {proc.returncode}]')
    if stdout:
        print(f'[stdout]\n{stdout.decode()}')
    if stderr:
        print(f'[stderr]\n{stderr.decode()}')

if sys.platform == "win32":
    asyncio.set_event_loop_policy(
        asyncio.WindowsProactorEventLoopPolicy())

asyncio.run(run('dir ..'))

From report at bugs.python.org  Wed Jan 30 10:49:49 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 30 Jan 2019 15:49:49 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548863384.52.0.319719291843.issue25592@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:


New changeset 598e15d4feaee3849a91d92c9ca51f17baafe19c by Antoine Pitrou (jdemeyer) in branch 'master':
bpo-25592: Improve documentation of distutils data_files (GH-9767)
https://github.com/python/cpython/commit/598e15d4feaee3849a91d92c9ca51f17baafe19c


----------

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

From report at bugs.python.org  Wed Jan 30 10:50:06 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 30 Jan 2019 15:50:06 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548863403.79.0.992158995843.issue25592@roundup.psfhosted.org>


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


----------
pull_requests: +11551

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

From report at bugs.python.org  Wed Jan 30 10:50:19 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 30 Jan 2019 15:50:19 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548863415.09.0.107191558294.issue25592@roundup.psfhosted.org>


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


----------
pull_requests: +11551, 11552

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

From report at bugs.python.org  Wed Jan 30 10:50:31 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 30 Jan 2019 15:50:31 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548863427.63.0.136657494174.issue25592@roundup.psfhosted.org>


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


----------
pull_requests: +11551, 11552, 11553

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

From report at bugs.python.org  Wed Jan 30 10:54:11 2019
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 30 Jan 2019 15:54:11 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548863645.42.0.164444636416.issue25592@roundup.psfhosted.org>


?ric Araujo <merwok at netwok.org> added the comment:

Thanks for the analysis and PR!  Sorry that the slow process here was frustrating.

----------

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

From report at bugs.python.org  Wed Jan 30 10:56:59 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 30 Jan 2019 15:56:59 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548863813.73.0.990904537567.issue25592@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:


New changeset ebae1ce9c40e62ce52dc968f86ed11578d2fcdfd by Antoine Pitrou (Miss Islington (bot)) in branch '3.7':
bpo-25592: Improve documentation of distutils data_files (GH-9767) (GH-11701)
https://github.com/python/cpython/commit/ebae1ce9c40e62ce52dc968f86ed11578d2fcdfd


----------

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

From report at bugs.python.org  Wed Jan 30 10:57:36 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 30 Jan 2019 15:57:36 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548863850.51.0.377154654092.issue25592@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:

Fixing this on 2.7 would require additional investigation (distutils might have diverged), so I'm closing now.

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

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

From report at bugs.python.org  Wed Jan 30 12:23:47 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 30 Jan 2019 17:23:47 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548869023.47.0.220951358075.issue35835@roundup.psfhosted.org>


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


New changeset cf991e653ac550a9f011631447c61ce583404a57 by Miss Islington (bot) (Jo?o Matos) in branch 'master':
bpo-35835: Add reference to Python 3.7 new breakpoint() function in pdb documentation. (GH-11691)
https://github.com/python/cpython/commit/cf991e653ac550a9f011631447c61ce583404a57


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

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

From report at bugs.python.org  Wed Jan 30 12:24:00 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 30 Jan 2019 17:24:00 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548869038.07.0.199638674192.issue35835@roundup.psfhosted.org>


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


----------
pull_requests: +11555

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

From report at bugs.python.org  Wed Jan 30 12:24:07 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 30 Jan 2019 17:24:07 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548869045.42.0.350021512267.issue35835@roundup.psfhosted.org>


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


----------
pull_requests: +11555, 11556

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

From report at bugs.python.org  Wed Jan 30 12:24:15 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 30 Jan 2019 17:24:15 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548869052.71.0.770663394155.issue35835@roundup.psfhosted.org>


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


----------
pull_requests: +11555, 11556, 11557

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

From report at bugs.python.org  Wed Jan 30 12:25:54 2019
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 30 Jan 2019 17:25:54 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548869149.62.0.249370285325.issue35835@roundup.psfhosted.org>


Mariatta Wijaya <mariatta at python.org> added the comment:

Thanks!

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

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

From report at bugs.python.org  Wed Jan 30 12:28:17 2019
From: report at bugs.python.org (jcrmatos)
Date: Wed, 30 Jan 2019 17:28:17 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548869292.8.0.0844060275686.issue35835@roundup.psfhosted.org>


jcrmatos <jcrmatos at gmail.com> added the comment:

Thank you all for the help.

----------

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

From report at bugs.python.org  Wed Jan 30 12:42:00 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 30 Jan 2019 17:42:00 +0000
Subject: [docs] [issue35835] There is no mention of breakpoint() in the pdb
 documentation
In-Reply-To: <1548544149.44.0.0958996770934.issue35835@roundup.psfhosted.org>
Message-ID: <1548870115.53.0.709114250943.issue35835@roundup.psfhosted.org>


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


New changeset 7516f265a8517e4fdc7d6e63d72ae1b57fda26ee by Miss Islington (bot) in branch '3.7':
bpo-35835: Add reference to Python 3.7 new breakpoint() function in pdb documentation. (GH-11691)
https://github.com/python/cpython/commit/7516f265a8517e4fdc7d6e63d72ae1b57fda26ee


----------

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

From report at bugs.python.org  Thu Jan 31 00:57:35 2019
From: report at bugs.python.org (Pascal van der Donck)
Date: Thu, 31 Jan 2019 05:57:35 +0000
Subject: [docs] [issue20767] Some python extensions can't be compiled with
 clang 3.4
In-Reply-To: <1393335198.15.0.97052317234.issue20767@psf.upfronthosting.co.za>
Message-ID: <1548914247.61.0.27003354784.issue20767@roundup.psfhosted.org>


Change by Pascal van der Donck <pvddonck at gmail.com>:


----------
assignee:  -> docs at python
components: +2to3 (2.x to 3.x conversion tool), Argument Clinic, Build, Cross-Build, Demos and Tools, Documentation, Extension Modules, FreeBSD, IDLE, IO, Installation, Interpreter Core, Library (Lib), Regular Expressions, SSL, Tests, Tkinter, Unicode, XML, asyncio, ctypes, email
nosy: +Alex.Willmer, asvetlov, barry, docs at python, larry, mrabarnett, r.david.murray, terry.reedy, yselivanov
type: compile error -> resource usage
versions: +Python 3.4

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

From report at bugs.python.org  Thu Jan 31 01:00:23 2019
From: report at bugs.python.org (Larry Hastings)
Date: Thu, 31 Jan 2019 06:00:23 +0000
Subject: [docs] [issue20767] Some python extensions can't be compiled with
 clang 3.4
In-Reply-To: <1393335198.15.0.97052317234.issue20767@psf.upfronthosting.co.za>
Message-ID: <1548914411.29.0.548773746913.issue20767@roundup.psfhosted.org>


Larry Hastings <larry at hastings.org> added the comment:

It's too late to fix this for Python 3.4 and 3.5, as those are now in security-fixes-only mode.  Also, please don't select every possible component that could be remotely connected.

----------
components:  -2to3 (2.x to 3.x conversion tool), Argument Clinic, Build, Cross-Build, Demos and Tools, Distutils, Documentation, FreeBSD, IDLE, IO, Installation, Interpreter Core, Library (Lib), Regular Expressions, SSL, Tests, Tkinter, Unicode, XML, asyncio, ctypes, email
versions:  -Python 3.4, Python 3.5

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

From report at bugs.python.org  Thu Jan 31 01:01:56 2019
From: report at bugs.python.org (Larry Hastings)
Date: Thu, 31 Jan 2019 06:01:56 +0000
Subject: [docs] [issue20767] Some python extensions can't be compiled with
 clang 3.4
In-Reply-To: <1393335198.15.0.97052317234.issue20767@psf.upfronthosting.co.za>
Message-ID: <1548914506.78.0.691185517982.issue20767@roundup.psfhosted.org>


Change by Larry Hastings <larry at hastings.org>:


----------
priority: high -> normal
type: resource usage -> compile error

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

From report at bugs.python.org  Thu Jan 31 01:14:21 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Thu, 31 Jan 2019 06:14:21 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548915255.55.0.535864356755.issue25592@roundup.psfhosted.org>


Jeroen Demeyer <J.Demeyer at UGent.be> added the comment:

> Fixing this on 2.7 would require additional investigation (distutils might have diverged)

Let's be honest, we are talking about distutils here. So it's way more likely that it didn't diverge and that the behavior is exactly the same on 2.7 and 3.8. So I would suggest to backport it to 2.7 also.

----------

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

From report at bugs.python.org  Thu Jan 31 03:10:14 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 31 Jan 2019 08:10:14 +0000
Subject: [docs] [issue35865] configparser document refers about random dict
 order
Message-ID: <1548922210.28.0.356473813231.issue35865@roundup.psfhosted.org>


New submission from INADA Naoki <songofacandy at gmail.com>:

GH-6819 (bpo-33504) changed OrderedDict to dict, and removed note about randomness of dict order in dict.

But it is only for 3.8.  Python 3.7 document should remove the note too.

----------
assignee: docs at python
components: Documentation
messages: 334609
nosy: docs at python, inada.naoki
priority: normal
severity: normal
status: open
title: configparser document refers about random dict order
versions: Python 3.7

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

From report at bugs.python.org  Thu Jan 31 03:13:30 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 31 Jan 2019 08:13:30 +0000
Subject: [docs] [issue35865] configparser document refers about random dict
 order
In-Reply-To: <1548922210.28.0.356473813231.issue35865@roundup.psfhosted.org>
Message-ID: <1548922410.06.0.611450221983.issue35865@roundup.psfhosted.org>


Change by INADA Naoki <songofacandy at gmail.com>:


----------
keywords: +patch
pull_requests: +11567
stage:  -> patch review

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

From report at bugs.python.org  Thu Jan 31 03:13:35 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 31 Jan 2019 08:13:35 +0000
Subject: [docs] [issue35865] configparser document refers about random dict
 order
In-Reply-To: <1548922210.28.0.356473813231.issue35865@roundup.psfhosted.org>
Message-ID: <1548922415.07.0.369780596365.issue35865@roundup.psfhosted.org>


Change by INADA Naoki <songofacandy at gmail.com>:


----------
keywords: +patch, patch
pull_requests: +11567, 11568
stage:  -> patch review

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

From report at bugs.python.org  Thu Jan 31 03:13:39 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 31 Jan 2019 08:13:39 +0000
Subject: [docs] [issue35865] configparser document refers about random dict
 order
In-Reply-To: <1548922210.28.0.356473813231.issue35865@roundup.psfhosted.org>
Message-ID: <1548922419.82.0.906172950152.issue35865@roundup.psfhosted.org>


Change by INADA Naoki <songofacandy at gmail.com>:


----------
keywords: +patch, patch, patch
pull_requests: +11567, 11568, 11569
stage:  -> patch review

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

From report at bugs.python.org  Thu Jan 31 03:30:25 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 31 Jan 2019 08:30:25 +0000
Subject: [docs] [issue33800] Fix default argument for parameter dict_type of
 ConfigParser/RawConfigParser
In-Reply-To: <1528401689.57.0.592728768989.issue33800@psf.upfronthosting.co.za>
Message-ID: <1548923423.4.0.434440453667.issue33800@roundup.psfhosted.org>


INADA Naoki <songofacandy at gmail.com> added the comment:

This should be reverted in 3.7.
bpo-33504 changed dict_type from 3.8+, not 3.7.

----------
nosy: +inada.naoki

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

From report at bugs.python.org  Thu Jan 31 03:34:30 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 31 Jan 2019 08:34:30 +0000
Subject: [docs] [issue33800] Fix default argument for parameter dict_type of
 ConfigParser/RawConfigParser
In-Reply-To: <1528401689.57.0.592728768989.issue33800@psf.upfronthosting.co.za>
Message-ID: <1548923666.95.0.216119101057.issue33800@roundup.psfhosted.org>


INADA Naoki <songofacandy at gmail.com> added the comment:

I revert this change in GH-35865.

----------

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

From report at bugs.python.org  Thu Jan 31 03:35:35 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 31 Jan 2019 08:35:35 +0000
Subject: [docs] [issue35865] configparser document refers about random dict
 order
In-Reply-To: <1548922210.28.0.356473813231.issue35865@roundup.psfhosted.org>
Message-ID: <1548923733.31.0.514002738754.issue35865@roundup.psfhosted.org>


INADA Naoki <songofacandy at gmail.com> added the comment:

Also revert GH-7542 (bpo-33800) too.

----------

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

From report at bugs.python.org  Thu Jan 31 03:53:08 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 31 Jan 2019 08:53:08 +0000
Subject: [docs] [issue33800] Fix default argument for parameter dict_type of
 ConfigParser/RawConfigParser
In-Reply-To: <1528401689.57.0.592728768989.issue33800@psf.upfronthosting.co.za>
Message-ID: <1548924785.1.0.860554667832.issue33800@roundup.psfhosted.org>


INADA Naoki <songofacandy at gmail.com> added the comment:

I'm sorry. bpo-35865 (GH-11711)

----------

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

From report at bugs.python.org  Thu Jan 31 03:54:59 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 31 Jan 2019 08:54:59 +0000
Subject: [docs] [issue35865] configparser document refers about random dict
 order
In-Reply-To: <1548922210.28.0.356473813231.issue35865@roundup.psfhosted.org>
Message-ID: <1548924897.53.0.422153645313.issue35865@roundup.psfhosted.org>


INADA Naoki <songofacandy at gmail.com> added the comment:


New changeset 59014449721966a7890f6323616431ad869ec7cc by Inada Naoki in branch '3.7':
bpo-35865: doc: Remove wrong note and directives (GH-11711)
https://github.com/python/cpython/commit/59014449721966a7890f6323616431ad869ec7cc


----------

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

From report at bugs.python.org  Thu Jan 31 03:56:39 2019
From: report at bugs.python.org (INADA Naoki)
Date: Thu, 31 Jan 2019 08:56:39 +0000
Subject: [docs] [issue35865] configparser document refers about random dict
 order
In-Reply-To: <1548922210.28.0.356473813231.issue35865@roundup.psfhosted.org>
Message-ID: <1548924999.52.0.398698151189.issue35865@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/issue35865>
_______________________________________

From report at bugs.python.org  Thu Jan 31 05:03:10 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 31 Jan 2019 10:03:10 +0000
Subject: [docs] [issue20767] Some python extensions can't be compiled with
 clang 3.4
In-Reply-To: <1393335198.15.0.97052317234.issue20767@psf.upfronthosting.co.za>
Message-ID: <1548928978.31.0.514806849645.issue20767@roundup.psfhosted.org>


Change by Terry J. Reedy <tjreedy at udel.edu>:


----------
nosy:  -terry.reedy

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

From report at bugs.python.org  Thu Jan 31 05:04:31 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 31 Jan 2019 10:04:31 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548929068.77.0.944850156857.issue25592@roundup.psfhosted.org>


Change by Antoine Pitrou <pitrou at free.fr>:


----------
status: closed -> open

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

From report at bugs.python.org  Thu Jan 31 05:08:19 2019
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 31 Jan 2019 10:08:19 +0000
Subject: [docs] [issue25592] distutils docs: data_files always uses
 sys.prefix
In-Reply-To: <1447135572.7.0.138478279434.issue25592@psf.upfronthosting.co.za>
Message-ID: <1548929293.39.0.0193272801299.issue25592@roundup.psfhosted.org>


Antoine Pitrou <pitrou at free.fr> added the comment:

Jeroen you're right.  Could you still give it a quick check?  Then I'll mark the PR for a 2.7 backport.

----------

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

From report at bugs.python.org  Thu Jan 31 05:27:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 31 Jan 2019 10:27:00 +0000
Subject: [docs] [issue20767] Some python extensions can't be compiled with
 clang 3.4
In-Reply-To: <1393335198.15.0.97052317234.issue20767@psf.upfronthosting.co.za>
Message-ID: <1548930406.87.0.278441928811.issue20767@roundup.psfhosted.org>


STINNER Victor <vstinner at redhat.com> added the comment:

> If the intent is to use this issue to track the resolution of the original issue (clang compilation broken) and cover the new PR (which just moves the code from os detection to compiler detection), then it can remain open. Otherwise it can be closed, as the original issue 'has' been fixed.

Ok, I close the issue.

On https://github.com/python/cpython/pull/5233 bapt asked "code changes", but I don't understand what exactly and I'm not interested to continue to work on these changes. If someone is interested, please open a new issue (pointing to this one).

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

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

From report at bugs.python.org  Thu Jan 31 13:13:53 2019
From: report at bugs.python.org (Victor Porton)
Date: Thu, 31 Jan 2019 18:13:53 +0000
Subject: [docs] [issue35870] readline() specification is unclear
Message-ID: <1548958431.25.0.44536557418.issue35870@roundup.psfhosted.org>


New submission from Victor Porton <porton at narod.ru>:

In https://docs.python.org/3/library/io.html it is forgotten to say whether '\n' is appened to the return value of readline().

It is also unclear what happens if the last line not terminated by '\n' is read.

It is also unclear what is returned if a text file (say with '\r\n' terminators) is read. Is it appended to the return value '\n', '\r\n' or nothing?

----------
assignee: docs at python
components: Documentation
messages: 334634
nosy: docs at python, porton
priority: normal
severity: normal
status: open
title: readline() specification is unclear
versions: Python 3.8

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

From report at bugs.python.org  Thu Jan 31 17:45:22 2019
From: report at bugs.python.org (R. David Murray)
Date: Thu, 31 Jan 2019 22:45:22 +0000
Subject: [docs] [issue20767] Some python extensions can't be compiled with
 clang 3.4
In-Reply-To: <1393335198.15.0.97052317234.issue20767@psf.upfronthosting.co.za>
Message-ID: <1548974711.66.0.0477914556708.issue20767@roundup.psfhosted.org>


Change by R. David Murray <rdmurray at bitdance.com>:


----------
nosy:  -r.david.murray

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

From report at bugs.python.org  Thu Jan 31 18:28:46 2019
From: report at bugs.python.org (Martin Panter)
Date: Thu, 31 Jan 2019 23:28:46 +0000
Subject: [docs] [issue35870] readline() specification is unclear
In-Reply-To: <1548958431.25.0.44536557418.issue35870@roundup.psfhosted.org>
Message-ID: <1548977325.06.0.248213750705.issue35870@roundup.psfhosted.org>


Martin Panter <vadmium+py at gmail.com> added the comment:

I agree that the documentation should be clearer about the first two points. Considering that the "input" function and by default the "str.splitlines" method both behave differently, I often had to re-learn this when I had less Python experience.

The expected behaviour as I understand is the line terminator is included if it was read. It is not included if the size limit or EOF was reached first. The Python 2 documentation <https://docs.python.org/2/library/stdtypes.html#file.readline> is clear about both the newline being included and EOF behaviour.

Regarding text files, if you mean the "TextIOWrapper.readline" method, I think it is reasonable to assume you get the translated line endings as specified by the constructor's "newline" argument: <https://docs.python.org/3/library/io.html#io.TextIOWrapper>. Newline='' and newline='\r\n' would keep the '\r\n' terminators, and newline=None would translate them to '\n'.

----------
nosy: +martin.panter

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