From report at bugs.python.org  Wed Aug  1 05:15:56 2018
From: report at bugs.python.org (Michael Fischer)
Date: Wed, 01 Aug 2018 09:15:56 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533114956.03.0.56676864532.issue34273@psf.upfronthosting.co.za>


Michael Fischer <michael-fischer89 at web.de> added the comment:

Thank you for your quick reply. I understand why you chose this description better now. However in C %f behaves exactly the same as in Python (for floating-point numbers) and you will mostly find the description for it along the lines of:

'%f' Print a floating-point number in normal (fixed-point) notation. [The GNU C Library Reference Manual - https://www.gnu.org/software/libc/manual/pdf/libc.pdf]

For the sake of simplicity I suggest the following wording:

Fixed point notation. Displays the (floating-point) number as a fixed-point number. The default precision is 6.

In my opinion this emphasizes the intent (fixed precision representation) and hints at the independence of input type, by putting the floating-point in brackets.

----------

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

From berker.peksag at gmail.com  Wed Aug  1 08:54:47 2018
From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=)
Date: Wed, 1 Aug 2018 15:54:47 +0300
Subject: [docs] Documentation python3/library/signal: example does not
 work: SIGALARM unknow in signal
In-Reply-To: <db29a57a-5525-80ec-70f8-5d2f17c266e3@gmx.de>
References: <db29a57a-5525-80ec-70f8-5d2f17c266e3@gmx.de>
Message-ID: <CAF4280KXrGmXYWd7rEeCMfZ+A5aS6R1ZtCt674b-ZUkywG5ybA@mail.gmail.com>

On Mon, Jul 30, 2018 at 12:51 PM, Gottfried M?ller
<gottfried.mueller at gmx.de> wrote:
> Hello,
>
> I've got this message:
>
> signal.signal(signal.SIGALARM, myHandler)
> AttributeError: module 'signal' has no attribute 'SIGALARM'

Hi Gottfried,

There is a typo in the snippet you've posted. If you replace
'signal.SIGALARM' with 'signal.SIGALRM' (no 'a' after 'l') it should
work:

>>> import signal
>>> def handler(signum, frame): pass
...
>>> signal.signal(signal.SIGALRM, handler)
0

--Berker

> I am using Manjaro/Python version 3.6.6.
>
> Gottfried
>
>
>
>
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs

From report at bugs.python.org  Wed Aug  1 10:18:09 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 01 Aug 2018 14:18:09 +0000
Subject: [docs] [issue32752] no information about accessing typing.Generic
 type arguments
In-Reply-To: <1517612346.62.0.467229070634.issue32752@psf.upfronthosting.co.za>
Message-ID: <1533133089.87.0.56676864532.issue32752@psf.upfronthosting.co.za>


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

> 3.7 is less convenient and less consistent

Taking into account that internal API is something one should never use, I don't think these terms apply here. Anyway, we will provide some helpers for external use in one of the next releases.

----------

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

From report at bugs.python.org  Thu Aug  2 06:53:50 2018
From: report at bugs.python.org (sakamoto aya)
Date: Thu, 02 Aug 2018 10:53:50 +0000
Subject: [docs] [issue34317] Improve docstring Environment variables in
 Windows NT
Message-ID: <1533207230.71.0.56676864532.issue34317@psf.upfronthosting.co.za>


New submission from sakamoto aya <aya.sakamoto at outlook.com>:

Expired link in windows.rst:  
https://support.microsoft.com/en-us/help/100843/environment-variables-in-windows-nt

May I make a suggestion?

The new link:https://www.microsoft.com/en-us/wdsi/help/folder-variables

----------
assignee: docs at python
components: Documentation
messages: 322944
nosy: HiyashiChuka, docs at python
priority: normal
severity: normal
status: open
title: Improve docstring   Environment variables in Windows NT
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Aug  2 07:00:07 2018
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Aug 2018 11:00:07 +0000
Subject: [docs] [issue34317] Improve docstring Environment variables in
 Windows NT
In-Reply-To: <1533207230.71.0.56676864532.issue34317@psf.upfronthosting.co.za>
Message-ID: <1533207607.18.0.902498594338.issue34317@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Aug  2 07:52:33 2018
From: report at bugs.python.org (Thomas Nyberg)
Date: Thu, 02 Aug 2018 11:52:33 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
Message-ID: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>


New submission from Thomas Nyberg <tomnyberg at gmail.com>:

This came out of the following posts:

https://mail.python.org/pipermail/python-ideas/2018-August/052549.html
https://mail.python.org/pipermail/python-ideas/2018-August/052553.html

Basically my request would be to change the documentation here:

https://docs.python.org/3.7/library/pathlib.html#pathlib.Path.read_text

I would like to add a note that the underlying file object itself is closed after the read_text() method is called. Maybe I'm just a little dense and it should be obvious that the functionality here would be different than open("filepath").read(), but given that thread I linked, I don't believe I'm the only one.

----------
assignee: docs at python
components: Documentation
messages: 322947
nosy: docs at python, thomas.nyberg
priority: normal
severity: normal
status: open
title: Clarify pathlib.Path("filepath").read_text()

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

From report at bugs.python.org  Thu Aug  2 08:28:44 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 02 Aug 2018 12:28:44 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1533212924.17.0.902498594338.issue34319@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Aug  2 11:57:41 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 02 Aug 2018 15:57:41 +0000
Subject: [docs] [issue30984] traceback.print_exc return value documentation
In-Reply-To: <1500651170.07.0.787106480078.issue30984@psf.upfronthosting.co.za>
Message-ID: <1533225461.33.0.56676864532.issue30984@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

The documentation you've quoted is for traceback.extract_tb(). traceback.format_tb() documentation only says:

    A shorthand for ``format_list(extract_tb(tb, limit))``.

Issue 27910 is about updating the documentation of extract_tb(), format_list(), and StackSummary.from_list().

I'm closing this as a duplicate of issue 27910.

----------
nosy: +berker.peksag
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Doc/library/traceback.rst ? references to tuples should be replaced with new FrameSummary object
type:  -> behavior

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

From report at bugs.python.org  Thu Aug  2 12:09:02 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 02 Aug 2018 16:09:02 +0000
Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?=
 =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?=
 =?utf-8?q?eSummary_object?=
In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za>
Message-ID: <1533226142.61.0.56676864532.issue27910@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset f394ee5eaf6d6d8f45e0478e77d4dbff25c6bea7 by Berker Peksag (torsava) in branch 'master':
bpo-27910: Update documentation of traceback module (GH-6116)
https://github.com/python/cpython/commit/f394ee5eaf6d6d8f45e0478e77d4dbff25c6bea7


----------

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

From report at bugs.python.org  Thu Aug  2 12:09:24 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 02 Aug 2018 16:09:24 +0000
Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?=
 =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?=
 =?utf-8?q?eSummary_object?=
In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za>
Message-ID: <1533226164.84.0.902498594338.issue27910@psf.upfronthosting.co.za>


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


----------
pull_requests: +8134

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

From report at bugs.python.org  Thu Aug  2 12:10:20 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 02 Aug 2018 16:10:20 +0000
Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?=
 =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?=
 =?utf-8?q?eSummary_object?=
In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za>
Message-ID: <1533226220.38.0.902498594338.issue27910@psf.upfronthosting.co.za>


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


----------
pull_requests: +8135

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

From report at bugs.python.org  Thu Aug  2 12:51:51 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 02 Aug 2018 16:51:51 +0000
Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?=
 =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?=
 =?utf-8?q?eSummary_object?=
In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za>
Message-ID: <1533228711.89.0.56676864532.issue27910@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 0f9df886d6d1c6b239a2861a0ad0d56bb59e3922 by Berker Peksag (Miss Islington (bot)) in branch '3.7':
bpo-27910: Update documentation of traceback module (GH-6116)
https://github.com/python/cpython/commit/0f9df886d6d1c6b239a2861a0ad0d56bb59e3922


----------

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

From report at bugs.python.org  Thu Aug  2 13:01:00 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 02 Aug 2018 17:01:00 +0000
Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?=
 =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?=
 =?utf-8?q?eSummary_object?=
In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za>
Message-ID: <1533229260.77.0.56676864532.issue27910@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 295342adbfd905d5b4a77f960ea39649df7d9997 by Berker Peksag (Miss Islington (bot)) in branch '3.6':
bpo-27910: Update documentation of traceback module (GH-6116)
https://github.com/python/cpython/commit/295342adbfd905d5b4a77f960ea39649df7d9997


----------

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

From report at bugs.python.org  Thu Aug  2 13:01:28 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 02 Aug 2018 17:01:28 +0000
Subject: [docs] =?utf-8?q?=5Bissue27910=5D_Doc/library/traceback=2Erst_?=
 =?utf-8?q?=E2=80=94_references_to_tuples_should_be_replaced_with_new_Fram?=
 =?utf-8?q?eSummary_object?=
In-Reply-To: <1472637889.08.0.384463773035.issue27910@psf.upfronthosting.co.za>
Message-ID: <1533229288.03.0.902498594338.issue27910@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.6

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

From report at bugs.python.org  Thu Aug  2 13:46:45 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 02 Aug 2018 17:46:45 +0000
Subject: [docs] [issue26502] traceback.extract_tb breaks compatibility by
 returning FrameSummary
In-Reply-To: <1457349348.27.0.253072992901.issue26502@psf.upfronthosting.co.za>
Message-ID: <1533232005.21.0.902498594338.issue26502@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


----------
keywords: +patch
pull_requests: +8137
stage: needs patch -> patch review

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

From report at bugs.python.org  Thu Aug  2 13:54:06 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 02 Aug 2018 17:54:06 +0000
Subject: [docs] [issue25573] FrameSummary repr() does not support previously
 working uses of repr in traceback module
In-Reply-To: <1446845666.11.0.0803768990935.issue25573@psf.upfronthosting.co.za>
Message-ID: <1533232446.38.0.902498594338.issue25573@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


----------
nosy: +berker.peksag

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

From report at bugs.python.org  Thu Aug  2 16:11:08 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 02 Aug 2018 20:11:08 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1533240668.18.0.56676864532.issue34319@psf.upfronthosting.co.za>


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

How about if we add "The file is opened and then closed." before "The optional parameters have the same meaning as in open()."

----------
nosy: +terry.reedy
stage:  -> needs patch
versions: +Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Aug  2 19:19:01 2018
From: report at bugs.python.org (Lysandros Nikolaou)
Date: Thu, 02 Aug 2018 23:19:01 +0000
Subject: [docs] [issue34324] Doc README wrong directory name for vent
Message-ID: <1533251941.31.0.56676864532.issue34324@psf.upfronthosting.co.za>


New submission from Lysandros Nikolaou <lisandrosnik at gmail.com>:

In the Doc README there is the following sentence after the make venv command:
Assuming the virtual environment was created in the env directory (the default; configurable with the VENVDIR variable)

Should't it be venv directory instead? In the makefile the VENVDIR variable is set to venv by default.

----------
assignee: docs at python
components: Documentation
messages: 322997
nosy: docs at python, lys.nikolaou
priority: normal
severity: normal
status: open
title: Doc README wrong directory name for vent
versions: Python 3.8

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

From report at bugs.python.org  Thu Aug  2 19:19:47 2018
From: report at bugs.python.org (Lysandros Nikolaou)
Date: Thu, 02 Aug 2018 23:19:47 +0000
Subject: [docs] [issue34324] Doc README wrong directory name for venv
In-Reply-To: <1533251941.31.0.56676864532.issue34324@psf.upfronthosting.co.za>
Message-ID: <1533251987.87.0.902498594338.issue34324@psf.upfronthosting.co.za>


Change by Lysandros Nikolaou <lisandrosnik at gmail.com>:


----------
title: Doc README wrong directory name for vent -> Doc README wrong directory name for venv

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

From report at bugs.python.org  Thu Aug  2 22:44:08 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 03 Aug 2018 02:44:08 +0000
Subject: [docs] [issue34317] Improve docstring Environment variables in
 Windows NT
In-Reply-To: <1533207230.71.0.56676864532.issue34317@psf.upfronthosting.co.za>
Message-ID: <1533264248.78.0.56676864532.issue34317@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:


New changeset 46ebe61c7f3511b97268b44d5373a9e9cf0b5cc7 by Mariatta (HiyashiChuka) in branch 'master':
bpo-34317: Fix a dead url to Windows documentation (GH-8622)
https://github.com/python/cpython/commit/46ebe61c7f3511b97268b44d5373a9e9cf0b5cc7


----------
nosy: +Mariatta

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

From report at bugs.python.org  Thu Aug  2 22:44:32 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 03 Aug 2018 02:44:32 +0000
Subject: [docs] [issue34317] Improve docstring Environment variables in
 Windows NT
In-Reply-To: <1533207230.71.0.56676864532.issue34317@psf.upfronthosting.co.za>
Message-ID: <1533264272.88.0.902498594338.issue34317@psf.upfronthosting.co.za>


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


----------
pull_requests: +8144

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

From report at bugs.python.org  Thu Aug  2 23:01:17 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 03 Aug 2018 03:01:17 +0000
Subject: [docs] [issue34317] Improve docstring Environment variables in
 Windows NT
In-Reply-To: <1533207230.71.0.56676864532.issue34317@psf.upfronthosting.co.za>
Message-ID: <1533265277.58.0.56676864532.issue34317@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Thanks!

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

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

From report at bugs.python.org  Thu Aug  2 23:29:43 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 03 Aug 2018 03:29:43 +0000
Subject: [docs] [issue34317] Improve docstring Environment variables in
 Windows NT
In-Reply-To: <1533207230.71.0.56676864532.issue34317@psf.upfronthosting.co.za>
Message-ID: <1533266983.5.0.56676864532.issue34317@psf.upfronthosting.co.za>


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


New changeset 34f59a7a7843d8e2c1922c830a99b5b7a022f4be by Miss Islington (bot) in branch '3.7':
bpo-34317: Fix a dead url to Windows documentation (GH-8622)
https://github.com/python/cpython/commit/34f59a7a7843d8e2c1922c830a99b5b7a022f4be


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

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

From report at bugs.python.org  Fri Aug  3 00:52:37 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 03 Aug 2018 04:52:37 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1533271957.19.0.902498594338.issue34319@psf.upfronthosting.co.za>


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


----------
keywords: +patch
pull_requests: +8148
stage: needs patch -> patch review

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

From report at bugs.python.org  Fri Aug  3 01:21:37 2018
From: report at bugs.python.org (sakamotoaya)
Date: Fri, 03 Aug 2018 05:21:37 +0000
Subject: [docs] [issue34328] Question Incorrect URL for the Visual C++ Build
 Tools
Message-ID: <1533273697.75.0.56676864532.issue34328@psf.upfronthosting.co.za>


New submission from sakamotoaya <aya.sakamoto at outlook.com>:

I try "python setup.py". 
The following issue has occurred.

Excerpt from Error
?????????????????????
reading manifest template 'MANIFEST.in'
writing manifest file 'scikit_learn.egg-info\SOURCES.txt'
running build_ext
No module named 'numpy.distutils._msvccompiler' in numpy.distutils; trying from
distutils
customize MSVCCompiler
Missing compiler_cxx fix for MSVCCompiler
customize MSVCCompiler using build_clib
building 'libsvm-skl' library
compiling C sources
error: Microsoft Visual C++ 14.0 is required. Get it with "Microsoft Visual C++
Build Tools": http://landinghub.visualstudio.com/visual-cpp-build-tools
?????????????????????

Expired link:  
http://landinghub.visualstudio.com/visual-cpp-build-tools

I think The new link:
https://download.microsoft.com/download/5/F/7/5F7ACAEB-8363-451F-9425-68A90F98B238/visualcppbuildtools_full.exe


Please give me advice on how I should correct those error message.

----------
components: Windows
messages: 323024
nosy: HiyashiChuka, docs at python, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Question Incorrect URL for the Visual C++ Build Tools
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Aug  3 01:22:39 2018
From: report at bugs.python.org (sakamotoaya)
Date: Fri, 03 Aug 2018 05:22:39 +0000
Subject: [docs] [issue34328] Incorrect URL for the Visual C++ Build Tools
In-Reply-To: <1533273697.75.0.56676864532.issue34328@psf.upfronthosting.co.za>
Message-ID: <1533273759.9.0.902498594338.issue34328@psf.upfronthosting.co.za>


Change by sakamotoaya <aya.sakamoto at outlook.com>:


----------
title: Question Incorrect URL for the Visual C++ Build Tools -> Incorrect URL for the Visual C++ Build Tools

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

From report at bugs.python.org  Fri Aug  3 01:56:29 2018
From: report at bugs.python.org (sakamotoaya)
Date: Fri, 03 Aug 2018 05:56:29 +0000
Subject: [docs] [issue34328] Incorrect URL for the Visual C++ Build Tools
In-Reply-To: <1533273697.75.0.56676864532.issue34328@psf.upfronthosting.co.za>
Message-ID: <1533275789.17.0.902498594338.issue34328@psf.upfronthosting.co.za>


Change by sakamotoaya <aya.sakamoto at outlook.com>:


----------
nosy: +CuriousLearner, ncoghlan, serhiy.storchaka, xtreak

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

From report at bugs.python.org  Fri Aug  3 01:57:15 2018
From: report at bugs.python.org (Ronald Oussoren)
Date: Fri, 03 Aug 2018 05:57:15 +0000
Subject: [docs] [issue34328] Incorrect URL for the Visual C++ Build Tools
In-Reply-To: <1533273697.75.0.56676864532.issue34328@psf.upfronthosting.co.za>
Message-ID: <1533275835.76.0.56676864532.issue34328@psf.upfronthosting.co.za>


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

This message is generated by setuptools (in module setuptools.msvc). 

The GitHub repository for setuptools is at <https://github.com/pypa/setuptools>, please contact the developers there.

----------
nosy: +ronaldoussoren
resolution:  -> third party
stage:  -> resolved
status: open -> pending

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

From report at bugs.python.org  Fri Aug  3 02:00:30 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 03 Aug 2018 06:00:30 +0000
Subject: [docs] [issue34328] Incorrect URL for the Visual C++ Build Tools
In-Reply-To: <1533273697.75.0.56676864532.issue34328@psf.upfronthosting.co.za>
Message-ID: <1533276030.02.0.56676864532.issue34328@psf.upfronthosting.co.za>


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

Upstream issue was resolved : https://github.com/pypa/setuptools/issues/1394

Thanks

----------
status: pending -> open

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

From report at bugs.python.org  Fri Aug  3 02:01:54 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 03 Aug 2018 06:01:54 +0000
Subject: [docs] [issue34328] Incorrect URL for the Visual C++ Build Tools
In-Reply-To: <1533273697.75.0.56676864532.issue34328@psf.upfronthosting.co.za>
Message-ID: <1533276114.92.0.56676864532.issue34328@psf.upfronthosting.co.za>


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

Ah sorry, I don't know why it opened this bug while adding a comment. Feel free to change the status.

Thanks

----------

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

From report at bugs.python.org  Fri Aug  3 02:14:15 2018
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 03 Aug 2018 06:14:15 +0000
Subject: [docs] [issue34328] Incorrect URL for the Visual C++ Build Tools
In-Reply-To: <1533273697.75.0.56676864532.issue34328@psf.upfronthosting.co.za>
Message-ID: <1533276855.4.0.902498594338.issue34328@psf.upfronthosting.co.za>


Change by St?phane Wirtel <stephane at wirtel.be>:


----------
status: open -> pending

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

From report at bugs.python.org  Fri Aug  3 02:39:42 2018
From: report at bugs.python.org (sakamotoaya)
Date: Fri, 03 Aug 2018 06:39:42 +0000
Subject: [docs] [issue34328] Incorrect URL for the Visual C++ Build Tools
In-Reply-To: <1533273697.75.0.56676864532.issue34328@psf.upfronthosting.co.za>
Message-ID: <1533278382.03.0.56676864532.issue34328@psf.upfronthosting.co.za>


sakamotoaya <aya.sakamoto at outlook.com> added the comment:

Everyone Thank you.
That was really helpful.

Problem already been resolved.
I change status?Pending to close.

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

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

From report at bugs.python.org  Fri Aug  3 02:51:45 2018
From: report at bugs.python.org (Thomas Nyberg)
Date: Fri, 03 Aug 2018 06:51:45 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1533279105.89.0.56676864532.issue34319@psf.upfronthosting.co.za>


Thomas Nyberg <tomnyberg at gmail.com> added the comment:

For what it's worth as the original opener of the bug report, I think Terry's recommendation clarifies things quite well.

----------

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

From report at bugs.python.org  Fri Aug  3 02:54:22 2018
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 03 Aug 2018 06:54:22 +0000
Subject: [docs] [issue34324] Doc README wrong directory name for venv
In-Reply-To: <1533251941.31.0.56676864532.issue34324@psf.upfronthosting.co.za>
Message-ID: <1533279262.99.0.902498594338.issue34324@psf.upfronthosting.co.za>


Change by St?phane Wirtel <stephane at wirtel.be>:


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

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

From report at bugs.python.org  Fri Aug  3 02:54:54 2018
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 03 Aug 2018 06:54:54 +0000
Subject: [docs] [issue34324] Doc README wrong directory name for venv
In-Reply-To: <1533251941.31.0.56676864532.issue34324@psf.upfronthosting.co.za>
Message-ID: <1533279294.58.0.56676864532.issue34324@psf.upfronthosting.co.za>


St?phane Wirtel <stephane at wirtel.be> added the comment:

I just pushed a PR.

----------
nosy: +matrixise

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

From report at bugs.python.org  Fri Aug  3 05:58:05 2018
From: report at bugs.python.org (Stefan Otte)
Date: Fri, 03 Aug 2018 09:58:05 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
Message-ID: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>


New submission from Stefan Otte <stefan.otte at gmail.com>:

Hello folks!

I didn't realize that you can remove a suffix with the `with_suffix` function of the `Path` class of `pathlib` and I always used a little utility function that I wrote.
I wanted to add that functionality (removing of a suffix) and submit a PR but then I saw that `with_suffix` has you covered already. I'm just documenting this feature with the PR I'll submit.

----------
assignee: docs at python
components: Documentation
messages: 323042
nosy: docs at python, sotte
priority: normal
severity: normal
status: open
title: Document how to remove a suffix with pathlib.Path.with_suffix
type: enhancement

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

From report at bugs.python.org  Fri Aug  3 06:01:13 2018
From: report at bugs.python.org (Stefan Otte)
Date: Fri, 03 Aug 2018 10:01:13 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533290473.4.0.902498594338.issue34329@psf.upfronthosting.co.za>


Change by Stefan Otte <stefan.otte at gmail.com>:


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

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

From report at bugs.python.org  Fri Aug  3 09:12:55 2018
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 03 Aug 2018 13:12:55 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533301975.04.0.56676864532.issue34329@psf.upfronthosting.co.za>


St?phane Wirtel <stephane at wirtel.be> added the comment:

Good catch, thank you.
Could you sign the CLA, without the CLA, we can't process your PR.

Thank you

----------
nosy: +matrixise

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

From report at bugs.python.org  Fri Aug  3 09:59:56 2018
From: report at bugs.python.org (Stefan Otte)
Date: Fri, 03 Aug 2018 13:59:56 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533304796.68.0.56676864532.issue34329@psf.upfronthosting.co.za>


Stefan Otte <stefan.otte at gmail.com> added the comment:

I'm waiting for the CLA to be accepted. I'll get back to you ASAP.

----------

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

From report at bugs.python.org  Fri Aug  3 10:01:47 2018
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 03 Aug 2018 14:01:47 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533304907.79.0.56676864532.issue34329@psf.upfronthosting.co.za>


St?phane Wirtel <stephane at wirtel.be> added the comment:

yep, it's a manual modification in b.p.o but after that, we can check your PR. thank you for your patience.

----------

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

From report at bugs.python.org  Fri Aug  3 10:04:13 2018
From: report at bugs.python.org (Stefan Otte)
Date: Fri, 03 Aug 2018 14:04:13 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533305053.69.0.56676864532.issue34329@psf.upfronthosting.co.za>


Stefan Otte <stefan.otte at gmail.com> added the comment:

No problem, I'm just excited to contribute to python (as small as the contribution might be) :)

----------

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

From report at bugs.python.org  Fri Aug  3 10:12:18 2018
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 03 Aug 2018 14:12:18 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533305538.95.0.56676864532.issue34329@psf.upfronthosting.co.za>


St?phane Wirtel <stephane at wirtel.be> added the comment:

It's the same thing for everything, for example, in Karate, you will start with the white belt and with practice, you will get the black belt.

Thank you again for your contribution.

----------

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

From report at bugs.python.org  Fri Aug  3 10:25:01 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 03 Aug 2018 14:25:01 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533306301.18.0.56676864532.issue34329@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

This seems like a reasonable request. The feature was added in https://github.com/python/cpython/commit/e50dafcd636ba32db890600164698bb070d40d97 (issue 20639) in Python 3.4.

I'd normally suggest adding a ".. versionchanged:: 3.4" marker, but since the change is quite old and it's already in all of the current maintenance releases, I think we don't need to add it.

----------
nosy: +berker.peksag
versions: +Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Aug  3 15:47:21 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 03 Aug 2018 19:47:21 +0000
Subject: [docs] [issue34256] Python treats ASCII record separator ('\x1e')
 as a newline
In-Reply-To: <1532772549.2.0.56676864532.issue34256@psf.upfronthosting.co.za>
Message-ID: <1533325641.56.0.56676864532.issue34256@psf.upfronthosting.co.za>


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

A database record is equivalent to a logical line, possible wrapped onto multiple physical lines. So it is plausible.

The 7643 in the test name refers to issue #7643, What is a Unicode line break character?"  It contains this:
"
> We may add some words to the documentation for str.splitlines() and bytes.splitlines() to explain what is considered a line break character.

For ASCII we should make the list of characters explicit.
For Unicode, we should mention the above definition and give
the table as example list (the Unicode database may add more
such characters in the future).
"
The test was added but the doc not.  I agree that it would be useful.  Feel free to suggest a doc change.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, terry.reedy
title: Python treats ASCII record seperator ('\x1e') as a newline -> Python treats ASCII record separator ('\x1e') as a newline
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Fri Aug  3 16:49:44 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 03 Aug 2018 20:49:44 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533329384.56.0.56676864532.issue34329@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 46dc4e34ed8005a688d7f3512844ef227a3465f4 by Berker Peksag (Stefan Otte) in branch 'master':
bpo-34329: Doc'd how to remove suffix of pathlib.Path() (GH-8655)
https://github.com/python/cpython/commit/46dc4e34ed8005a688d7f3512844ef227a3465f4


----------

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

From report at bugs.python.org  Fri Aug  3 16:50:29 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 03 Aug 2018 20:50:29 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533329429.88.0.902498594338.issue34329@psf.upfronthosting.co.za>


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


----------
pull_requests: +8156

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

From report at bugs.python.org  Fri Aug  3 16:50:40 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 03 Aug 2018 20:50:40 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533329440.66.0.902498594338.issue34329@psf.upfronthosting.co.za>


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


----------
pull_requests: +8157

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

From report at bugs.python.org  Fri Aug  3 17:21:58 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 03 Aug 2018 21:21:58 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533331317.96.0.56676864532.issue34273@psf.upfronthosting.co.za>


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

The closest anchor is https://docs.python.org/3.8/library/string.html#format-specification-mini-language.

The table title is "The available presentation types for floating point and decimal values are:".

This is slightly confusing to me.  Does this mean instances of 'float' and 'decimal' classes?  or 'floating point numbers (floats and decimals)  and integral numbers, sometimes called decimals since usually written with decimal digits'?

Within the table, 'number' refers to whatever the title refers to. So I think adding '(floating point)' would be confusing and wrong, as it excludes 'decimals' whatever they are.  On the other hand, changing 'Fixed point' to 'Fixed point notation', in parallel with 'Exponential notation', is correct and should be helpful.

----------
nosy: +terry.reedy
stage:  -> needs patch
versions: +Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Aug  3 17:45:24 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 03 Aug 2018 21:45:24 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533332724.31.0.56676864532.issue34329@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 764f9d09b03654d7cd70d59afafafd51d24f2750 by Berker Peksag (Miss Islington (bot)) in branch '3.6':
bpo-34329: Doc'd how to remove suffix of pathlib.Path() (GH-8655)
https://github.com/python/cpython/commit/764f9d09b03654d7cd70d59afafafd51d24f2750


----------

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

From report at bugs.python.org  Fri Aug  3 17:45:49 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 03 Aug 2018 21:45:49 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533332749.88.0.56676864532.issue34329@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 39fcd9949832323b672f7ff05fd1498b8844a329 by Berker Peksag (Miss Islington (bot)) in branch '3.7':
bpo-34329: Doc'd how to remove suffix of pathlib.Path() (GH-8655)
https://github.com/python/cpython/commit/39fcd9949832323b672f7ff05fd1498b8844a329


----------

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

From report at bugs.python.org  Fri Aug  3 17:46:15 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 03 Aug 2018 21:46:15 +0000
Subject: [docs] [issue34329] Document how to remove a suffix with
 pathlib.Path.with_suffix
In-Reply-To: <1533290285.58.0.56676864532.issue34329@psf.upfronthosting.co.za>
Message-ID: <1533332775.86.0.902498594338.issue34329@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


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

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

From report at bugs.python.org  Fri Aug  3 19:55:15 2018
From: report at bugs.python.org (Martin Panter)
Date: Fri, 03 Aug 2018 23:55:15 +0000
Subject: [docs] [issue34256] Python treats ASCII record separator ('\x1e')
 as a newline
In-Reply-To: <1532772549.2.0.56676864532.issue34256@psf.upfronthosting.co.za>
Message-ID: <1533340515.32.0.56676864532.issue34256@psf.upfronthosting.co.za>


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

What documentation were you looking at? I remember adding 0x1E and others to the list in Issue 12855. See <https://docs.python.org/3.5/library/stdtypes.html#str.splitlines>:

???
str.splitlines([keepends])
  . . .
  
  This method splits on the following line boundaries. . . .
  
  Representation  Description
  ==============  ===========
  . . .
  \x1e            Record Separator
  . . .
???

----------
nosy: +martin.panter

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

From report at bugs.python.org  Sat Aug  4 09:08:41 2018
From: report at bugs.python.org (Michael Fischer)
Date: Sat, 04 Aug 2018 13:08:41 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533388121.91.0.56676864532.issue34273@psf.upfronthosting.co.za>


Michael Fischer <michael-fischer89 at web.de> added the comment:

Terry: I absolutely agree with you. Changing 'Fixed point' to 'Fixed point notation' is the optimal solution here.

----------

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

From report at bugs.python.org  Sat Aug  4 09:10:34 2018
From: report at bugs.python.org (tzickel)
Date: Sat, 04 Aug 2018 13:10:34 +0000
Subject: [docs] [issue34172] multiprocessing.Pool and ThreadPool leak
 resources after being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1533388234.49.0.56676864532.issue34172@psf.upfronthosting.co.za>


tzickel <icebreak at yahoo.com> added the comment:

It actually makes tons of sense that while the thread is running, that the object representing it is alive. After the thread finishes its work, the object dies.

>>> import time, threading, weakref, gc
>>> t = threading.Thread(target=time.sleep, args=(10,))
>>> wr = weakref.ref(t)
>>> t.start()
>>> del t
>>> gc.collect()
>>> wr()
<Thread(Thread-1, started 139937234327296)>
Wait 10 seconds...
>>> gc.collect()
>>> wr()

The thread is gone (which doesn't happen with the pool).

Anyhow, I've submitted a patch to fix the bug that was introduced 9 years ago on GH, feel free to check it.

----------

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

From report at bugs.python.org  Sat Aug  4 09:40:17 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 04 Aug 2018 13:40:17 +0000
Subject: [docs] [issue34172] multiprocessing.Pool and ThreadPool leak
 resources after being deleted
In-Reply-To: <1532105129.76.0.56676864532.issue34172@psf.upfronthosting.co.za>
Message-ID: <1533390017.0.0.56676864532.issue34172@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Thanks a lot tzickle, I'll take a look.

----------

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

From report at bugs.python.org  Sat Aug  4 11:01:25 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 04 Aug 2018 15:01:25 +0000
Subject: [docs] [issue13574] refresh example in doc for Extending and
 Embedding
In-Reply-To: <1323546725.7.0.960922330938.issue13574@psf.upfronthosting.co.za>
Message-ID: <1533394885.07.0.56676864532.issue13574@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

The documentation has been modernized in https://github.com/python/cpython/commit/1d80a561734b9932961c546b0897405a3bfbf3e6 and the "Weak Reference Support" section has been updated to show the modern way of adding weakref support:

    https://github.com/python/cpython/commit/1d80a561734b9932961c546b0897405a3bfbf3e6#diff-1ace1cc14bb5b7f4ee77f22238ede084R556

----------
nosy: +berker.peksag
resolution:  -> out of date
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Aug  4 11:34:15 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 04 Aug 2018 15:34:15 +0000
Subject: [docs] [issue33736] Improve the documentation of asyncio stream API
In-Reply-To: <1528472164.69.0.592728768989.issue33736@psf.upfronthosting.co.za>
Message-ID: <1533396855.19.0.902498594338.issue33736@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


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

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

From report at bugs.python.org  Sat Aug  4 13:17:22 2018
From: report at bugs.python.org (Martin Altmayer)
Date: Sat, 04 Aug 2018 17:17:22 +0000
Subject: [docs] [issue33649] asyncio docs overhaul
In-Reply-To: <1527277722.54.0.682650639539.issue33649@psf.upfronthosting.co.za>
Message-ID: <1533403042.8.0.902498594338.issue33649@psf.upfronthosting.co.za>


Change by Martin Altmayer <martin.altmayer at web.de>:


----------
nosy: +MartinAltmayer

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

From report at bugs.python.org  Sat Aug  4 13:36:26 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Sat, 04 Aug 2018 17:36:26 +0000
Subject: [docs] [issue33649] asyncio docs overhaul
In-Reply-To: <1527277722.54.0.682650639539.issue33649@psf.upfronthosting.co.za>
Message-ID: <1533404186.4.0.56676864532.issue33649@psf.upfronthosting.co.za>


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

Status update: I'm working on a first rewrite. I expect to have something to review on a couple of weeks.

----------

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

From report at bugs.python.org  Sat Aug  4 15:22:32 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 04 Aug 2018 19:22:32 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533410552.21.0.902498594338.issue34273@psf.upfronthosting.co.za>


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


----------
keywords: +patch
pull_requests: +8165
stage: needs patch -> patch review

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

From report at bugs.python.org  Sat Aug  4 15:48:24 2018
From: report at bugs.python.org (Sanyam Khurana)
Date: Sat, 04 Aug 2018 19:48:24 +0000
Subject: [docs] [issue33187] Document ElementInclude (XInclude) support in
 ElementTree
In-Reply-To: <1522427694.7.0.467229070634.issue33187@psf.upfronthosting.co.za>
Message-ID: <1533412104.41.0.56676864532.issue33187@psf.upfronthosting.co.za>


Sanyam Khurana <sanyam.khurana01 at gmail.com> added the comment:

Hello Anjali,

As far as I remember, you started this in a PyDelhi Dev Sprint. So, just wanted to check around, if you're looking for any help :)

----------
nosy: +CuriousLearner

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

From report at bugs.python.org  Sat Aug  4 19:05:34 2018
From: report at bugs.python.org (Mikhail Terekhov)
Date: Sat, 04 Aug 2018 23:05:34 +0000
Subject: [docs] [issue32258] Rewrite asyncio docs to use async/await syntax
In-Reply-To: <1512813975.64.0.213398074469.issue32258@psf.upfronthosting.co.za>
Message-ID: <1533423934.56.0.978306453185.issue32258@psf.upfronthosting.co.za>


Change by Mikhail Terekhov <termim at gmail.com>:


----------
pull_requests: +8168

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

From report at bugs.python.org  Sat Aug  4 20:35:57 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 05 Aug 2018 00:35:57 +0000
Subject: [docs] [issue24937] Multiple problems in getters & setters in
 capsulethunk.h
In-Reply-To: <1440520892.99.0.130273606833.issue24937@psf.upfronthosting.co.za>
Message-ID: <1533429357.04.0.56676864532.issue24937@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

It would be nice to remove PyCObject_* entries from Doc/data/refcounts.dat.

+.. _documentation: http://py3c.readthedocs.org/en/latest/capsulethunk.html

Nit: We could the HTTPS link.

----------
nosy: +berker.peksag
stage:  -> patch review
type:  -> enhancement
versions: +Python 3.7, Python 3.8 -Python 2.7, Python 3.2, Python 3.5

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

From report at bugs.python.org  Sun Aug  5 02:51:25 2018
From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=)
Date: Sun, 05 Aug 2018 06:51:25 +0000
Subject: [docs] [issue34336] Don't promote possibility to omit Optional on
 optional/defaulted arguments
Message-ID: <1533451885.05.0.56676864532.issue34336@psf.upfronthosting.co.za>


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

The documentation of typing.Optional seems to promote practices for not specifying Optional that are recommended against in PEP 484:

https://www.python.org/dev/peps/pep-0484/#union-types -- end of chapter recommends against inferring Optional.

https://docs.python.org/3.8/library/typing.html#typing.Optional -- second paragraph promotes the possibility of leaving out Optional.

I'm not sure how to improve the typing.Optional doc wording, perhaps it would be better to just remove the second paragraph altogether.

----------
assignee: docs at python
components: Documentation
messages: 323132
nosy: docs at python, scop
priority: normal
severity: normal
status: open
title: Don't promote possibility to omit Optional on optional/defaulted arguments
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Sun Aug  5 02:53:25 2018
From: report at bugs.python.org (=?utf-8?q?Ville_Skytt=C3=A4?=)
Date: Sun, 05 Aug 2018 06:53:25 +0000
Subject: [docs] [issue34336] Don't promote possibility to omit Optional on
 optional/defaulted arguments
In-Reply-To: <1533451885.05.0.56676864532.issue34336@psf.upfronthosting.co.za>
Message-ID: <1533452005.19.0.902498594338.issue34336@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Aug  5 10:25:49 2018
From: report at bugs.python.org (Sanyam Khurana)
Date: Sun, 05 Aug 2018 14:25:49 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1533479149.0.0.56676864532.issue34319@psf.upfronthosting.co.za>


Sanyam Khurana <sanyam.khurana01 at gmail.com> added the comment:

+1 to Terry's suggestion.

I've reviewed xtreak's PR and it looks good to me.

----------
nosy: +CuriousLearner

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

From report at bugs.python.org  Sun Aug  5 12:38:07 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sun, 05 Aug 2018 16:38:07 +0000
Subject: [docs] [issue34336] Don't promote possibility to omit Optional on
 optional/defaulted arguments
In-Reply-To: <1533451885.05.0.56676864532.issue34336@psf.upfronthosting.co.za>
Message-ID: <1533487087.32.0.56676864532.issue34336@psf.upfronthosting.co.za>


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


New changeset 336c945858055059a65134d4c501a85037d70d99 by Ivan Levkivskyi (Ville Skytt?) in branch 'master':
bpo-34336: Don't promote possibility to leave out typing.Optional (#8677)
https://github.com/python/cpython/commit/336c945858055059a65134d4c501a85037d70d99


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

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

From report at bugs.python.org  Sun Aug  5 13:04:21 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 05 Aug 2018 17:04:21 +0000
Subject: [docs] [issue34336] Don't promote possibility to omit Optional on
 optional/defaulted arguments
In-Reply-To: <1533451885.05.0.56676864532.issue34336@psf.upfronthosting.co.za>
Message-ID: <1533488661.15.0.902498594338.issue34336@psf.upfronthosting.co.za>


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


----------
pull_requests: +8174

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

From report at bugs.python.org  Sun Aug  5 13:04:37 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 05 Aug 2018 17:04:37 +0000
Subject: [docs] [issue34336] Don't promote possibility to omit Optional on
 optional/defaulted arguments
In-Reply-To: <1533451885.05.0.56676864532.issue34336@psf.upfronthosting.co.za>
Message-ID: <1533488677.68.0.902498594338.issue34336@psf.upfronthosting.co.za>


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


----------
pull_requests: +8175

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

From report at bugs.python.org  Sun Aug  5 13:22:50 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 05 Aug 2018 17:22:50 +0000
Subject: [docs] [issue34336] Don't promote possibility to omit Optional on
 optional/defaulted arguments
In-Reply-To: <1533451885.05.0.56676864532.issue34336@psf.upfronthosting.co.za>
Message-ID: <1533489770.25.0.56676864532.issue34336@psf.upfronthosting.co.za>


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


New changeset 02c4eae35cd24ab71c12b5e61ec22e993ac4839b by Miss Islington (bot) in branch '3.6':
bpo-34336: Don't promote possibility to leave out typing.Optional (GH-8677)
https://github.com/python/cpython/commit/02c4eae35cd24ab71c12b5e61ec22e993ac4839b


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

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

From report at bugs.python.org  Sun Aug  5 13:36:07 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 05 Aug 2018 17:36:07 +0000
Subject: [docs] [issue34336] Don't promote possibility to omit Optional on
 optional/defaulted arguments
In-Reply-To: <1533451885.05.0.56676864532.issue34336@psf.upfronthosting.co.za>
Message-ID: <1533490567.16.0.56676864532.issue34336@psf.upfronthosting.co.za>


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


New changeset e610c4f9984d50b45eb00e04c73c4208c0542a3b by Miss Islington (bot) in branch '3.7':
bpo-34336: Don't promote possibility to leave out typing.Optional (GH-8677)
https://github.com/python/cpython/commit/e610c4f9984d50b45eb00e04c73c4208c0542a3b


----------

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

From report at bugs.python.org  Sun Aug  5 13:43:07 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sun, 05 Aug 2018 17:43:07 +0000
Subject: [docs] [issue34336] Don't promote possibility to omit Optional on
 optional/defaulted arguments
In-Reply-To: <1533451885.05.0.56676864532.issue34336@psf.upfronthosting.co.za>
Message-ID: <1533490987.04.0.902498594338.issue34336@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Aug  5 22:57:35 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 06 Aug 2018 02:57:35 +0000
Subject: [docs] [issue26515] Update extending/embedding docs to new way to
 build modules in C
In-Reply-To: <1457491421.2.0.684118231911.issue26515@psf.upfronthosting.co.za>
Message-ID: <1533524255.05.0.902498594338.issue26515@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


----------
keywords: +patch
pull_requests: +8177
stage: needs patch -> patch review

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

From report at bugs.python.org  Sun Aug  5 23:05:47 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 06 Aug 2018 03:05:47 +0000
Subject: [docs] [issue26515] Update extending/embedding docs to new way to
 build modules in C
In-Reply-To: <1457491421.2.0.684118231911.issue26515@psf.upfronthosting.co.za>
Message-ID: <1533524747.76.0.902498594338.issue26515@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


----------
nosy: +berker.peksag
type:  -> enhancement
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Mon Aug  6 03:59:21 2018
From: report at bugs.python.org (Shahriyar Rzayev)
Date: Mon, 06 Aug 2018 07:59:21 +0000
Subject: [docs] [issue34342] Fix the broken links in CPythonVmInternals wiki
 page
Message-ID: <1533542361.92.0.56676864532.issue34342@psf.upfronthosting.co.za>


New submission from Shahriyar Rzayev <rzayev.sehriyar at gmail.com>:

Please see:
https://wiki.python.org/moin/CPythonVmInternals

There are some links under "Particularly useful pieces of documentation: " which are broken and should be updated respectively as follows:

[Execution Model] -> https://docs.python.org/3/reference/executionmodel.html

[GIL] -> https://docs.python.org/3/c-api/init.html#thread-state-and-the-global-interpreter-lock or this one https://wiki.python.org/moin/GlobalInterpreterLock

[Bytecodes] -> Which is now can be found in https://docs.python.org/3/library/dis.html

[Disassembler] -> same here https://docs.python.org/3/library/dis.html

----------
assignee: docs at python
components: Documentation
messages: 323182
nosy: docs at python, shako
priority: normal
severity: normal
status: open
title: Fix the broken links in CPythonVmInternals wiki page
type: enhancement

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

From report at bugs.python.org  Mon Aug  6 04:32:46 2018
From: report at bugs.python.org (Berker Peksag)
Date: Mon, 06 Aug 2018 08:32:46 +0000
Subject: [docs] [issue34342] Fix the broken links in CPythonVmInternals wiki
 page
In-Reply-To: <1533542361.92.0.56676864532.issue34342@psf.upfronthosting.co.za>
Message-ID: <1533544366.31.0.56676864532.issue34342@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thanks for the report. wiki.python.org is maintained by the Python community, not by Python core developers. You can fix those broken links by creating an account and requesting edit access by emailing to pydotorg-www at python.org. See https://wiki.python.org/moin/FrontPage#Editing_pages for details.

----------
nosy: +berker.peksag
resolution:  -> third party
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Aug  6 06:04:47 2018
From: report at bugs.python.org (Vlad Starostin)
Date: Mon, 06 Aug 2018 10:04:47 +0000
Subject: [docs] [issue34344] Fix the docstring for
 AbstractEventLoopPolicy.get_event_loop
Message-ID: <1533549887.39.0.56676864532.issue34344@psf.upfronthosting.co.za>


New submission from Vlad Starostin <drtyrsa at yandex.ru>:

The docstring says "This may be None or an instance of EventLoop". But docs explicitly state that get_event_loop "must never return None". The same docstring is also in the example in docs: https://docs.python.org/3.6/library/asyncio-eventloops.html#customizing-the-event-loop-policy

I propose changing it to:

def get_event_loop(self):
    """Get the event loop.

    Returns an instance of EventLoop or raises an exception.
    """

If the wording is ok, I'll make a PR.

----------
assignee: docs at python
components: Documentation, asyncio
messages: 323190
nosy: asvetlov, docs at python, drtyrsa, yselivanov
priority: normal
severity: normal
status: open
title: Fix the docstring for AbstractEventLoopPolicy.get_event_loop
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Aug  6 08:41:26 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 06 Aug 2018 12:41:26 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533559286.67.0.56676864532.issue34273@psf.upfronthosting.co.za>


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


New changeset 28c7f8c8ce34a0cb848822a252a9d0a761fb42d5 by Terry Jan Reedy in branch 'master':
bpo-34273: Change 'Fixed point' to 'Fixed-point notation'. (#8673)
https://github.com/python/cpython/commit/28c7f8c8ce34a0cb848822a252a9d0a761fb42d5


----------

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

From report at bugs.python.org  Mon Aug  6 08:41:35 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 06 Aug 2018 12:41:35 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533559295.86.0.902498594338.issue34273@psf.upfronthosting.co.za>


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


----------
pull_requests: +8181

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

From report at bugs.python.org  Mon Aug  6 08:41:43 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 06 Aug 2018 12:41:43 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533559303.36.0.902498594338.issue34273@psf.upfronthosting.co.za>


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


----------
pull_requests: +8182

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

From report at bugs.python.org  Mon Aug  6 08:47:39 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 06 Aug 2018 12:47:39 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533559659.62.0.56676864532.issue34273@psf.upfronthosting.co.za>


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


New changeset e39fb207f26f8007e95fcf120f5ff1cb7372791a by Miss Islington (bot) in branch '3.7':
bpo-34273: Change 'Fixed point' to 'Fixed-point notation'. (GH-8673)
https://github.com/python/cpython/commit/e39fb207f26f8007e95fcf120f5ff1cb7372791a


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

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

From report at bugs.python.org  Mon Aug  6 08:49:37 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 06 Aug 2018 12:49:37 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533559777.9.0.56676864532.issue34273@psf.upfronthosting.co.za>


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


New changeset ed8dd598ae7e0d944974af0fd73c2fbb6105fd5c by Miss Islington (bot) in branch '3.6':
bpo-34273: Change 'Fixed point' to 'Fixed-point notation'. (GH-8673)
https://github.com/python/cpython/commit/ed8dd598ae7e0d944974af0fd73c2fbb6105fd5c


----------

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

From report at bugs.python.org  Mon Aug  6 08:57:07 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 06 Aug 2018 12:57:07 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533560227.06.0.902498594338.issue34273@psf.upfronthosting.co.za>


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


----------
pull_requests: +8183

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

From report at bugs.python.org  Mon Aug  6 09:03:48 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 06 Aug 2018 13:03:48 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533560628.0.0.56676864532.issue34273@psf.upfronthosting.co.za>


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


New changeset 9027502e99cba700cadb675b3b2db03c311d1c4d by Terry Jan Reedy in branch '2.7':
[2.7] bpo-34273: Change 'Fixed point' to 'Fixed-point notation'. (GH-8673)
https://github.com/python/cpython/commit/9027502e99cba700cadb675b3b2db03c311d1c4d


----------

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

From report at bugs.python.org  Mon Aug  6 09:04:24 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 06 Aug 2018 13:04:24 +0000
Subject: [docs] [issue34273] %f is confusingly associated with fixed point
 format
In-Reply-To: <1532899552.57.0.56676864532.issue34273@psf.upfronthosting.co.za>
Message-ID: <1533560664.55.0.902498594338.issue34273@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Aug  6 15:55:06 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 06 Aug 2018 19:55:06 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1533585306.8.0.56676864532.issue34319@psf.upfronthosting.co.za>


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


New changeset 5b2657fb8c5aaa98e5748e1c325c74b97ea12fd1 by Terry Jan Reedy (Xtreak) in branch 'master':
bpo-34319: Clarify file handler closure in pathlib.read_text (GH-8645)
https://github.com/python/cpython/commit/5b2657fb8c5aaa98e5748e1c325c74b97ea12fd1


----------

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

From report at bugs.python.org  Mon Aug  6 15:55:45 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 06 Aug 2018 19:55:45 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1533585345.18.0.902498594338.issue34319@psf.upfronthosting.co.za>


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


----------
pull_requests: +8188

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

From report at bugs.python.org  Mon Aug  6 15:55:55 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 06 Aug 2018 19:55:55 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1533585355.83.0.902498594338.issue34319@psf.upfronthosting.co.za>


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


----------
pull_requests: +8189

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

From report at bugs.python.org  Mon Aug  6 15:59:45 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 06 Aug 2018 19:59:45 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1533585585.77.0.56676864532.issue34319@psf.upfronthosting.co.za>


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


New changeset 1c6df83e9318ab4ef8e32b805b8226b1324e1ffd by Miss Islington (bot) in branch '3.7':
bpo-34319: Clarify file handler closure in pathlib.read_text (GH-8645)
https://github.com/python/cpython/commit/1c6df83e9318ab4ef8e32b805b8226b1324e1ffd


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

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

From report at bugs.python.org  Mon Aug  6 16:04:33 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 06 Aug 2018 20:04:33 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1533585873.76.0.56676864532.issue34319@psf.upfronthosting.co.za>


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


New changeset 3da5c5c76d90ddfc4c188cc801d9387501b63b7f by Miss Islington (bot) in branch '3.6':
bpo-34319: Clarify file handler closure in pathlib.read_text (GH-8645)
https://github.com/python/cpython/commit/3da5c5c76d90ddfc4c188cc801d9387501b63b7f


----------

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

From report at bugs.python.org  Tue Aug  7 22:35:47 2018
From: report at bugs.python.org (Glenn Linderman)
Date: Wed, 08 Aug 2018 02:35:47 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
In-Reply-To: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>
Message-ID: <1533695747.27.0.56676864532.issue28044@psf.upfronthosting.co.za>


Glenn Linderman <v+python at g.nevcal.com> added the comment:

Nice implementation of sticky sidebar.
https://css-tricks.com/sticky-smooth-active-nav/#more-273952

I haven't looked at the patch, and don't know what R. David Murray doesn't like about how it works, but I find the Python sidebar extremely annoying because it scrolls off the top, and would rather it stayed around visible.

----------
nosy: +v+python

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

From report at bugs.python.org  Tue Aug  7 22:50:23 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 08 Aug 2018 02:50:23 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
In-Reply-To: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>
Message-ID: <1533696623.57.0.56676864532.issue28044@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Really sorry, but this issue is now out of date, and the patch no longer applies.

The Python documentation theme is now being tracked in https://github.com/python/python-docs-theme/

Perhaps bring up this issue there?

Thanks.

----------
nosy: +Mariatta
resolution:  -> out of date
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Aug  7 22:58:08 2018
From: report at bugs.python.org (Glenn Linderman)
Date: Wed, 08 Aug 2018 02:58:08 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
In-Reply-To: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>
Message-ID: <1533697088.6.0.56676864532.issue28044@psf.upfronthosting.co.za>


Glenn Linderman <v+python at g.nevcal.com> added the comment:

Uh, thanks, I guess, but it wasn't marked out of date or resolved or closed when I commented. I haven't used the GitHub issue tracker. Sigh. There should be a link here to the issue that was copied there, to make it easy and obvious?

----------
nosy:  -Mariatta

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

From report at bugs.python.org  Tue Aug  7 23:08:32 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 08 Aug 2018 03:08:32 +0000
Subject: [docs] [issue28044] Make the sidebar in the documentation follow
 the section automatically
In-Reply-To: <1473423727.81.0.401970346659.issue28044@psf.upfronthosting.co.za>
Message-ID: <1533697712.21.0.56676864532.issue28044@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

You can file a new issue in https://github.com/python/python-docs-theme/ and just add a link to this issue from GitHub in the description.

----------
nosy: +Mariatta

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

From report at bugs.python.org  Thu Aug  9 01:03:49 2018
From: report at bugs.python.org (Kevin Norris)
Date: Thu, 09 Aug 2018 05:03:49 +0000
Subject: [docs] [issue34365] datetime's documentation refers to "comparison
 [...] falling back to the default scheme of comparing object addresses"
Message-ID: <1533791029.87.0.56676864532.issue34365@psf.upfronthosting.co.za>


New submission from Kevin Norris <nykevin.norris at gmail.com>:

The 3.x datetime documentation contains the following footnote:

> In other words, date1 < date2 if and only if date1.toordinal() < date2.toordinal(). In order to stop comparison from falling back to the default scheme of comparing object addresses, date comparison normally raises TypeError if the other comparand isn?t also a date object. However, NotImplemented is returned instead if the other comparand has a timetuple() attribute. This hook gives other kinds of date objects a chance at implementing mixed-type comparison. If not, when a date object is compared to an object of a different type, TypeError is raised unless the comparison is == or !=. The latter cases return False or True, respectively.

But in 3.x, comparison no longer falls back to comparing object addresses.  Also, some of the comments on issue 8005 seem to suggest that this footnote is not actually true in 3.x (aside from the first sentence, of course).  But regardless, the footnote should not refer to a long dead interpreter behavior as if it were still around.

----------
assignee: docs at python
components: Documentation
messages: 323314
nosy: Kevin.Norris, docs at python
priority: normal
severity: normal
status: open
title: datetime's documentation refers to "comparison [...] falling back to the default scheme of comparing object addresses"
versions: 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/issue34365>
_______________________________________

From report at bugs.python.org  Thu Aug  9 11:05:43 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 09 Aug 2018 15:05:43 +0000
Subject: [docs] [issue34324] Doc README wrong directory name for venv
In-Reply-To: <1533251941.31.0.56676864532.issue34324@psf.upfronthosting.co.za>
Message-ID: <1533827142.91.0.56676864532.issue34324@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:


New changeset 599bfa18f8ebcb23af300b6855934048c3c64e7d by Mariatta (St?phane Wirtel) in branch 'master':
bpo-34324: Doc README wrong directory name for venv (GH-8650)
https://github.com/python/cpython/commit/599bfa18f8ebcb23af300b6855934048c3c64e7d


----------
nosy: +Mariatta

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

From report at bugs.python.org  Thu Aug  9 11:06:12 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 09 Aug 2018 15:06:12 +0000
Subject: [docs] [issue34324] Doc README wrong directory name for venv
In-Reply-To: <1533251941.31.0.56676864532.issue34324@psf.upfronthosting.co.za>
Message-ID: <1533827172.49.0.902498594338.issue34324@psf.upfronthosting.co.za>


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


----------
pull_requests: +8200

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

From report at bugs.python.org  Thu Aug  9 11:06:21 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 09 Aug 2018 15:06:21 +0000
Subject: [docs] [issue34324] Doc README wrong directory name for venv
In-Reply-To: <1533251941.31.0.56676864532.issue34324@psf.upfronthosting.co.za>
Message-ID: <1533827181.36.0.902498594338.issue34324@psf.upfronthosting.co.za>


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


----------
pull_requests: +8201

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

From report at bugs.python.org  Thu Aug  9 11:06:49 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 09 Aug 2018 15:06:49 +0000
Subject: [docs] [issue34324] Doc README wrong directory name for venv
In-Reply-To: <1533251941.31.0.56676864532.issue34324@psf.upfronthosting.co.za>
Message-ID: <1533827209.41.0.56676864532.issue34324@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Thanks!

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

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

From report at bugs.python.org  Thu Aug  9 11:10:31 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 09 Aug 2018 15:10:31 +0000
Subject: [docs] [issue34324] Doc README wrong directory name for venv
In-Reply-To: <1533251941.31.0.56676864532.issue34324@psf.upfronthosting.co.za>
Message-ID: <1533827431.15.0.56676864532.issue34324@psf.upfronthosting.co.za>


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


New changeset fe8f90aa3ca3f277cac634cdb96b829039225c6b by Miss Islington (bot) in branch '3.7':
bpo-34324: Doc README wrong directory name for venv (GH-8650)
https://github.com/python/cpython/commit/fe8f90aa3ca3f277cac634cdb96b829039225c6b


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

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

From report at bugs.python.org  Thu Aug  9 11:17:14 2018
From: report at bugs.python.org (miss-islington)
Date: Thu, 09 Aug 2018 15:17:14 +0000
Subject: [docs] [issue34324] Doc README wrong directory name for venv
In-Reply-To: <1533251941.31.0.56676864532.issue34324@psf.upfronthosting.co.za>
Message-ID: <1533827834.66.0.56676864532.issue34324@psf.upfronthosting.co.za>


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


New changeset 0ee2a29585e3c17e38eb6e6a2515405e40be22b5 by Miss Islington (bot) in branch '3.6':
bpo-34324: Doc README wrong directory name for venv (GH-8650)
https://github.com/python/cpython/commit/0ee2a29585e3c17e38eb6e6a2515405e40be22b5


----------

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

From report at bugs.python.org  Fri Aug 10 17:28:50 2018
From: report at bugs.python.org (Karan)
Date: Fri, 10 Aug 2018 21:28:50 +0000
Subject: [docs] [issue34378] Documentation 3.5+
Message-ID: <1533936530.23.0.56676864532.issue34378@psf.upfronthosting.co.za>


New submission from Karan <karan.svnit at gmail.com>:

The documentation link for 3.5+ is having an issue with the left sidebar where the index is present. In 2.7 if I scroll the main doc below to mid of the document the sidebar still shows me the index. The same is not present in the 3.5+. 

I know this is a very minor thing but for a new learner like me who is constantly reading these docs, this very small thing irritates a lot. 

Thanks

----------
assignee: docs at python
components: Documentation
files: imgonline-com-ua-twotoone-eLRSfZftmcsz.jpg
messages: 323393
nosy: Kapple, docs at python
priority: normal
severity: normal
status: open
title: Documentation 3.5+
type: behavior
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8
Added file: https://bugs.python.org/file47745/imgonline-com-ua-twotoone-eLRSfZftmcsz.jpg

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

From report at bugs.python.org  Fri Aug 10 17:56:18 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 10 Aug 2018 21:56:18 +0000
Subject: [docs] [issue34378] Documentation 3.5+
In-Reply-To: <1533936530.23.0.56676864532.issue34378@psf.upfronthosting.co.za>
Message-ID: <1533938178.19.0.56676864532.issue34378@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Sorry you're having trouble with this.
There is similar issue as https://bugs.python.org/issue28044.

The Python documentation Sphinx theme is now being maintained over at https://github.com/python/python-docs-theme/

Please file the issue there. Thanks.

----------
nosy: +Mariatta
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Make the sidebar in the documentation follow the section automatically

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

From report at bugs.python.org  Fri Aug 10 18:10:19 2018
From: report at bugs.python.org (Evan Allrich)
Date: Fri, 10 Aug 2018 22:10:19 +0000
Subject: [docs] [issue34379] Move note about repeated calls to json.dump
 using the same fp to the json.dump section
Message-ID: <1533939019.03.0.56676864532.issue34379@psf.upfronthosting.co.za>


New submission from Evan Allrich <psf at allri.ch>:

At present the note [0] appears under the documentation for `json.dumps` (which does not use the `fp` argument). It seems the note would be better placed with the documentation for the affected function.

[0] 
> Note
> 
> Unlike pickle and marshal, JSON is not a framed protocol, so trying to > serialize multiple objects with repeated calls to dump() using the same > fp will result in an invalid JSON file.

----------
assignee: docs at python
components: Documentation
messages: 323396
nosy: docs at python, eallrich
priority: normal
severity: normal
status: open
title: Move note about repeated calls to json.dump using the same fp to the json.dump section
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Fri Aug 10 18:20:18 2018
From: report at bugs.python.org (Evan Allrich)
Date: Fri, 10 Aug 2018 22:20:18 +0000
Subject: [docs] [issue34379] Move note about repeated calls to json.dump
 using the same fp to the json.dump section
In-Reply-To: <1533939019.03.0.56676864532.issue34379@psf.upfronthosting.co.za>
Message-ID: <1533939618.13.0.902498594338.issue34379@psf.upfronthosting.co.za>


Change by Evan Allrich <psf at allri.ch>:


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

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

From report at bugs.python.org  Sat Aug 11 03:34:05 2018
From: report at bugs.python.org (INADA Naoki)
Date: Sat, 11 Aug 2018 07:34:05 +0000
Subject: [docs] [issue34379] Move note about repeated calls to json.dump
 using the same fp to the json.dump section
In-Reply-To: <1533939019.03.0.56676864532.issue34379@psf.upfronthosting.co.za>
Message-ID: <1533972844.96.0.56676864532.issue34379@psf.upfronthosting.co.za>


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


New changeset 9e840848510d20e644a19c723b803877377d3765 by INADA Naoki (Evan Allrich) in branch 'master':
bpo-34379: Doc: Move note for json.dump (GH-8730)
https://github.com/python/cpython/commit/9e840848510d20e644a19c723b803877377d3765


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

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

From report at bugs.python.org  Sat Aug 11 03:34:20 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 11 Aug 2018 07:34:20 +0000
Subject: [docs] [issue34379] Move note about repeated calls to json.dump
 using the same fp to the json.dump section
In-Reply-To: <1533939019.03.0.56676864532.issue34379@psf.upfronthosting.co.za>
Message-ID: <1533972860.89.0.902498594338.issue34379@psf.upfronthosting.co.za>


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


----------
pull_requests: +8222

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

From report at bugs.python.org  Sat Aug 11 03:34:26 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 11 Aug 2018 07:34:26 +0000
Subject: [docs] [issue34379] Move note about repeated calls to json.dump
 using the same fp to the json.dump section
In-Reply-To: <1533939019.03.0.56676864532.issue34379@psf.upfronthosting.co.za>
Message-ID: <1533972866.75.0.902498594338.issue34379@psf.upfronthosting.co.za>


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


----------
pull_requests: +8223

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

From report at bugs.python.org  Sat Aug 11 04:02:11 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 11 Aug 2018 08:02:11 +0000
Subject: [docs] [issue34379] Move note about repeated calls to json.dump
 using the same fp to the json.dump section
In-Reply-To: <1533939019.03.0.56676864532.issue34379@psf.upfronthosting.co.za>
Message-ID: <1533974531.26.0.56676864532.issue34379@psf.upfronthosting.co.za>


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


New changeset 6b145085225d4b114b4422f6d3c6e859e75b97d7 by Miss Islington (bot) in branch '3.7':
bpo-34379: Doc: Move note for json.dump (GH-8730)
https://github.com/python/cpython/commit/6b145085225d4b114b4422f6d3c6e859e75b97d7


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

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

From report at bugs.python.org  Sat Aug 11 05:13:10 2018
From: report at bugs.python.org (INADA Naoki)
Date: Sat, 11 Aug 2018 09:13:10 +0000
Subject: [docs] [issue34379] Move note about repeated calls to json.dump
 using the same fp to the json.dump section
In-Reply-To: <1533939019.03.0.56676864532.issue34379@psf.upfronthosting.co.za>
Message-ID: <1533978790.5.0.56676864532.issue34379@psf.upfronthosting.co.za>


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


New changeset eb6ed12f486f184cb00fc35662d012dbb1f30d2e by INADA Naoki (Miss Islington (bot)) in branch '3.6':
bpo-34379: Doc: Move note for json.dump (GH-8730)
https://github.com/python/cpython/commit/eb6ed12f486f184cb00fc35662d012dbb1f30d2e


----------

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

From report at bugs.python.org  Sat Aug 11 05:13:33 2018
From: report at bugs.python.org (INADA Naoki)
Date: Sat, 11 Aug 2018 09:13:33 +0000
Subject: [docs] [issue34379] Move note about repeated calls to json.dump
 using the same fp to the json.dump section
In-Reply-To: <1533939019.03.0.56676864532.issue34379@psf.upfronthosting.co.za>
Message-ID: <1533978813.98.0.902498594338.issue34379@psf.upfronthosting.co.za>


Change by INADA Naoki <songofacandy at gmail.com>:


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

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

From report at bugs.python.org  Sat Aug 11 18:11:03 2018
From: report at bugs.python.org (Martin Panter)
Date: Sat, 11 Aug 2018 22:11:03 +0000
Subject: [docs] [issue33300] Bad usage example in id() DocString
In-Reply-To: <1523995335.26.0.682650639539.issue33300@psf.upfronthosting.co.za>
Message-ID: <1534025463.82.0.902498594338.issue33300@psf.upfronthosting.co.za>


Change by Martin Panter <vadmium+py at gmail.com>:


----------
resolution:  -> duplicate
status: open -> pending

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

From report at bugs.python.org  Sat Aug 11 20:21:28 2018
From: report at bugs.python.org (Martin Panter)
Date: Sun, 12 Aug 2018 00:21:28 +0000
Subject: [docs] [issue34369] kqueue.control() documentation and
 implementation mismatch
In-Reply-To: <1533882016.89.0.56676864532.issue34369@psf.upfronthosting.co.za>
Message-ID: <1534033287.92.0.56676864532.issue34369@psf.upfronthosting.co.za>


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

I think this was an attempt to specify a positional-only parameter (by using square brackets), and include a default value in the signature. The usual approach in this situation is to use square brackets, but only mention the default value in the text:

control(changelist, max_events[, timeout])
. . .
The default for "timeout" is None, to wait forever.

In Issue 13386 Ezio suggested against showing both square brackets and a default value, and I agree.

Berker: your "select" and "poll" cases all include the PEP 457 slash "/" notation, which was supposed to indicate positional-only parameters. See Issue 21314 about explaining this notation in the documentation somewhere.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python, martin.panter
versions: +Python 2.7

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

From report at bugs.python.org  Sun Aug 12 03:50:05 2018
From: report at bugs.python.org (Tal Einat)
Date: Sun, 12 Aug 2018 07:50:05 +0000
Subject: [docs] [issue34369] kqueue.control() documentation and
 implementation mismatch
In-Reply-To: <1533882016.89.0.56676864532.issue34369@psf.upfronthosting.co.za>
Message-ID: <1534060205.77.0.56676864532.issue34369@psf.upfronthosting.co.za>


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

In Python 3.8 this will have already been fixed (thanks to the recent conversion of the select module to use Argument Clinic); see below output from a recent build from the master branch.

Given that, is this worth fixing on 2.7 and <3.8?


Help on built-in function control:

control(changelist, maxevents, timeout=None, /) method of select.kqueue instance
    Calls the kernel kevent function.

    changelist
      Must be an iterable of kevent objects describing the changes to be made
      to the kernel's watch list or None.
    maxevents
      The maximum number of events that the kernel will return.
    timeout
      The maximum time to wait in seconds, or else None to wait forever.
      This accepts floats for smaller timeouts, too.

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

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

From report at bugs.python.org  Sun Aug 12 05:00:30 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 12 Aug 2018 09:00:30 +0000
Subject: [docs] [issue21314] Document '/' in signatures
In-Reply-To: <1397988439.5.0.703056699862.issue21314@psf.upfronthosting.co.za>
Message-ID: <1534064430.6.0.56676864532.issue21314@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

I'd suggest adding a FAQ entry to the "Core Language" section at https://docs.python.org/3/faq/programming.html#core-language then we can link to it from the places (except pydoc docs) Zachary listed in msg223893.

----------
nosy: +berker.peksag

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

From report at bugs.python.org  Sun Aug 12 05:56:15 2018
From: report at bugs.python.org (Martin Panter)
Date: Sun, 12 Aug 2018 09:56:15 +0000
Subject: [docs] [issue34369] kqueue.control() documentation and
 implementation mismatch
In-Reply-To: <1533882016.89.0.56676864532.issue34369@psf.upfronthosting.co.za>
Message-ID: <1534067775.72.0.56676864532.issue34369@psf.upfronthosting.co.za>


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

Even in 3.8, the main documentation is not fixed: https://docs.python.org/dev/library/select.html#kqueue-objects

----------

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

From report at bugs.python.org  Sun Aug 12 06:21:54 2018
From: report at bugs.python.org (Tal Einat)
Date: Sun, 12 Aug 2018 10:21:54 +0000
Subject: [docs] [issue34369] kqueue.control() documentation and
 implementation mismatch
In-Reply-To: <1533882016.89.0.56676864532.issue34369@psf.upfronthosting.co.za>
Message-ID: <1534069314.36.0.56676864532.issue34369@psf.upfronthosting.co.za>


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

We can just remove the "=None" in the docs for select.kqueue.control() to conform with the rest of that doc.

We don't use the PEP 457 slash notation in the docs for select (or perhaps at all?).

----------

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

From report at bugs.python.org  Mon Aug 13 08:36:26 2018
From: report at bugs.python.org (Semyon)
Date: Mon, 13 Aug 2018 12:36:26 +0000
Subject: [docs] [issue34394] Descriptors HowTo doesn't mention __set_name__
Message-ID: <1534163786.32.0.56676864532.issue34394@psf.upfronthosting.co.za>


New submission from Semyon <simeon+bpo at maryasin.name>:

There is a great HowTo document for descriptors https://github.com/python/cpython/blob/master/Doc/howto/descriptor.rst
But it doesn't even mention the __set_name__ method which was added in py3. And it lists the descriptor protocol without that method as if it is the full protocol. The only way to know about that method is to go to the link for any other method and then you'll see that there is a __set_name__.
I think the guide sholud be updated to include at least information about existence of __set_name__.

----------
assignee: docs at python
components: Documentation
messages: 323479
nosy: MarSoft, docs at python
priority: normal
severity: normal
status: open
title: Descriptors HowTo doesn't mention __set_name__
versions: 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/issue34394>
_______________________________________

From report at bugs.python.org  Mon Aug 13 11:13:28 2018
From: report at bugs.python.org (Shiva Saxena)
Date: Mon, 13 Aug 2018 15:13:28 +0000
Subject: [docs] [issue34117] Rename "generator expressions" to "generator
 comprehensions"
In-Reply-To: <1531614433.94.0.56676864532.issue34117@psf.upfronthosting.co.za>
Message-ID: <1534173208.11.0.56676864532.issue34117@psf.upfronthosting.co.za>


Shiva Saxena <shivasaxena911 at gmail.com> added the comment:

I am interested to work on this issue. It would be my first contribution in cpython. Should I go ahead?

----------
nosy: +GeekyShacklebolt

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

From report at bugs.python.org  Mon Aug 13 18:12:06 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 13 Aug 2018 22:12:06 +0000
Subject: [docs] [issue34394] Descriptors HowTo doesn't mention __set_name__
In-Reply-To: <1534163786.32.0.56676864532.issue34394@psf.upfronthosting.co.za>
Message-ID: <1534198326.69.0.56676864532.issue34394@psf.upfronthosting.co.za>


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

Thanks. I'm already working on this.

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

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

From report at bugs.python.org  Mon Aug 13 20:53:51 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 14 Aug 2018 00:53:51 +0000
Subject: [docs] [issue34117] Rename "generator expressions" to "generator
 comprehensions"
In-Reply-To: <1531614433.94.0.56676864532.issue34117@psf.upfronthosting.co.za>
Message-ID: <1534208031.62.0.56676864532.issue34117@psf.upfronthosting.co.za>


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

Results from two Python courses:

* In terms of teaching gexexps, there was no net gain or loss.  When genexps are show side-by-side with list/dict/set comps the symmetric relationship was obvious regardless of terminology.

* In terms of being able to search StackOverflow, blog posts, and external resources, the new terminology made the resources unfindable.

* When using the new terminology, I did get questions that never came up before, "why don't the parentheses mean tuple-comprehension".

Based on those results, I recommend we keep the terminology the same as it is now.  The loss of searchability isn't worth it (there doesn't seem to be any upside) and it is concerning that a new category of confusion (list/tuple comprehension) seems to be arising from the change in terminology.

----------

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

From report at bugs.python.org  Tue Aug 14 03:52:28 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Tue, 14 Aug 2018 07:52:28 +0000
Subject: [docs] [issue34398] Docs search does not index glossary
Message-ID: <1534233148.48.0.56676864532.issue34398@psf.upfronthosting.co.za>


New submission from Jonathan Fine <jfine2358 at gmail.com>:

The docs contain a very useful page https://docs.python.org/3.5/glossary.html. However, the search feature does not index the glossary.

Thus, the search https://docs.python.org/3.5/search.html?q=iterable does not produce the helpful glossary entry
===
iterable
An object capable of returning its members one at a time. Examples of iterables include all sequence types (such as list, str, and tuple) and some non-sequence types like dict, file objects, and objects of any  [...]
===

#788509 is the only docs issue I could find, whose title contains glossary. It gives insight into the thoughts then about the tutorial. In msg44460 Skip Montaro says (1) that the glossary is "for the tutorial", and (2) he'd like to improve links into the tutorial. 

I suggest that part of the fix for this issue is on the home page page Glossary in the first grouping "Parts of the documentation."

----------
assignee: docs at python
components: Documentation
messages: 323503
nosy: docs at python, jfine2358
priority: normal
severity: normal
status: open
title: Docs search does not index glossary
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/issue34398>
_______________________________________

From report at bugs.python.org  Tue Aug 14 08:34:23 2018
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 14 Aug 2018 12:34:23 +0000
Subject: [docs] [issue15258] argparse documentation: Improve optparse
 section regarding allow_interspersed_args
In-Reply-To: <1341528073.03.0.435446433545.issue15258@psf.upfronthosting.co.za>
Message-ID: <1534250062.98.0.56676864532.issue15258@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

ArgumentParser.parse_intermixed_arg() has been added in https://github.com/python/cpython/commit/0f6b9d230674da784ca79a0cf1a03d2af5a8b6a8 (Issue 14191) and the "Upgrading optparse code" section now has the following item:

* Replace optparse.OptionParser.disable_interspersed_args()
  by using ArgumentParser.parse_intermixed_args() instead of
  ArgumentParser.parse_args().

Closing this as 'outdated'.

----------
nosy: +berker.peksag
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Aug 14 11:04:48 2018
From: report at bugs.python.org (Alisue Lambda)
Date: Tue, 14 Aug 2018 15:04:48 +0000
Subject: [docs] [issue34406] Type in documentation
Message-ID: <1534259088.23.0.56676864532.issue34406@psf.upfronthosting.co.za>


New submission from Alisue Lambda <lambdalisue at hashnote.net>:

https://docs.python.org/3.8/using/windows.html#removing-the-max-path-limitation

Current
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem at LongPathsEnabled

Should be
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled

----------
assignee: docs at python
components: Documentation
messages: 323527
nosy: Alisue Lambda, docs at python
priority: normal
severity: normal
status: open
title: Type in documentation
versions: Python 3.8

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

From report at bugs.python.org  Tue Aug 14 11:04:57 2018
From: report at bugs.python.org (Alisue Lambda)
Date: Tue, 14 Aug 2018 15:04:57 +0000
Subject: [docs] [issue34406] Typo in documentation
In-Reply-To: <1534259088.23.0.56676864532.issue34406@psf.upfronthosting.co.za>
Message-ID: <1534259097.26.0.902498594338.issue34406@psf.upfronthosting.co.za>


Change by Alisue Lambda <lambdalisue at hashnote.net>:


----------
title: Type in documentation -> Typo in documentation

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

From report at bugs.python.org  Tue Aug 14 11:25:43 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 14 Aug 2018 15:25:43 +0000
Subject: [docs] [issue34398] Docs search does not index glossary
In-Reply-To: <1534233148.48.0.56676864532.issue34398@psf.upfronthosting.co.za>
Message-ID: <1534260343.01.0.56676864532.issue34398@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Hmm the search is built-in functionality in Sphinx, and I don't think we have any way to control or customize that.

----------
nosy: +Mariatta
resolution:  -> third party
status: open -> pending
versions:  -Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Tue Aug 14 11:58:55 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Tue, 14 Aug 2018 15:58:55 +0000
Subject: [docs] [issue34398] Docs search does not index glossary
In-Reply-To: <1534233148.48.0.56676864532.issue34398@psf.upfronthosting.co.za>
Message-ID: <1534262335.11.0.56676864532.issue34398@psf.upfronthosting.co.za>


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

Good discovery. The glossary uses the RST glossary directive.
https://github.com/python/cpython/blob/master/Doc/glossary.rst

The Sphinx docs have a glossary, which is indexed by its search.
http://www.sphinx-doc.org/en/master/search.html?q=domain

So maybe Sphinx already has the functionality we require. Perhaps it's simply a matter of configuring the Python docs to use it. (This is optimism.)

----------
status: pending -> open

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

From report at bugs.python.org  Tue Aug 14 15:11:41 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 14 Aug 2018 19:11:41 +0000
Subject: [docs] [issue34406] Typo in documentation
In-Reply-To: <1534259088.23.0.56676864532.issue34406@psf.upfronthosting.co.za>
Message-ID: <1534273901.84.0.56676864532.issue34406@psf.upfronthosting.co.za>


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

Isn't this saying that LongPathsEnabled is a value on the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem?

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

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

From report at bugs.python.org  Tue Aug 14 15:12:55 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 14 Aug 2018 19:12:55 +0000
Subject: [docs] [issue34406] Typo in documentation
In-Reply-To: <1534259088.23.0.56676864532.issue34406@psf.upfronthosting.co.za>
Message-ID: <1534273974.98.0.56676864532.issue34406@psf.upfronthosting.co.za>


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

I am not sure how people usually refer to the Windows register but this seems that the current line is differentiating from the path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

and the value

LongPathsEnabled

----------

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

From report at bugs.python.org  Wed Aug 15 02:57:55 2018
From: report at bugs.python.org (Ammar Askar)
Date: Wed, 15 Aug 2018 06:57:55 +0000
Subject: [docs] [issue34406] Typo in documentation
In-Reply-To: <1534259088.23.0.56676864532.issue34406@psf.upfronthosting.co.za>
Message-ID: <1534316275.35.0.56676864532.issue34406@psf.upfronthosting.co.za>


Ammar Askar <ammar at ammaraskar.com> added the comment:

For what its worth, window's reg command also makes a distinction between the registry key and value:


C:\Users\ammar>reg.exe QUERY HKLM\Software\Microsoft\.NETFramework\Enable64Bit
ERROR: The system was unable to find the specified registry key or value.

C:\Users\ammar>reg.exe QUERY HKLM\Software\Microsoft\.NETFramework /V Enable64Bit

HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework
    Enable64Bit    REG_DWORD    0x1


Maybe it can just be phrased as something like, "set the registry value LongPathsEnabled in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem"

----------
nosy: +ammar2

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

From report at bugs.python.org  Wed Aug 15 03:16:31 2018
From: report at bugs.python.org (Ammar Askar)
Date: Wed, 15 Aug 2018 07:16:31 +0000
Subject: [docs] [issue34398] Docs search does not index glossary
In-Reply-To: <1534233148.48.0.56676864532.issue34398@psf.upfronthosting.co.za>
Message-ID: <1534317391.84.0.56676864532.issue34398@psf.upfronthosting.co.za>


Ammar Askar <ammar at ammaraskar.com> added the comment:

Hmm, are you sure its not indexed? Look at this search result: https://docs.python.org/3/search.html?q=__slots__

The glossary page shows up in the results for me.

Or are you suggesting that if you search for a term defined in the glossary, it be prominently shown at the top of the search page?

----------
nosy: +ammar2

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

From report at bugs.python.org  Wed Aug 15 03:51:48 2018
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 15 Aug 2018 07:51:48 +0000
Subject: [docs] [issue34406] Typo in documentation
In-Reply-To: <1534259088.23.0.56676864532.issue34406@psf.upfronthosting.co.za>
Message-ID: <1534319508.64.0.902498594338.issue34406@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


----------
nosy: +steve.dower

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

From report at bugs.python.org  Wed Aug 15 04:08:48 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Wed, 15 Aug 2018 08:08:48 +0000
Subject: [docs] [issue34398] Docs search does not index glossary items
In-Reply-To: <1534233148.48.0.56676864532.issue34398@psf.upfronthosting.co.za>
Message-ID: <1534320528.62.0.56676864532.issue34398@psf.upfronthosting.co.za>


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

You're right! Thank you. However, there's still a problem. A user searches for a technical term, and the carefully written glossary entry defining it does not appear.

For my search term (iterable), there was a single entry with a link to the Glossary page, whose associated text was simply the first few entries in the glossary.
===
Glossary
...active shell when entering code for an indented code block or within a pair of matching left and right delimiters (parentheses, square brackets or curly braces). 2to3 A tool that tries to convert Python 2.x code to Pyt...
===

On a related matter. Sphinx provides an anchor, used for internal navigation with the glossary. But it doesn't provide a permalink to that anchor. Compare 
https://docs.python.org/3.5/glossary.html#term-iterable
https://docs.python.org/3.5/reference/compound_stmts.html#with

I think there's a real problem, and that my initial diagnosis was wrong. So I've changed the issue title slightly. (I hope you don't mind.)

The problem is, perhaps, that it is the glossary page that is indexed, rather than the glossary items. Another fix would be, as you suggest, pop up at top of results page a glossary item.

----------
title: Docs search does not index glossary -> Docs search does not index glossary items

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

From report at bugs.python.org  Wed Aug 15 09:31:13 2018
From: report at bugs.python.org (Steve Dower)
Date: Wed, 15 Aug 2018 13:31:13 +0000
Subject: [docs] [issue34406] Typo in documentation
In-Reply-To: <1534259088.23.0.56676864532.issue34406@psf.upfronthosting.co.za>
Message-ID: <1534339873.21.0.56676864532.issue34406@psf.upfronthosting.co.za>


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

Yeah, it definitely shouldn't be a backslash there. The @ isn't my invention, but last time someone questioned it I couldn't find any public examples, so it may be an internal Microsoft thing? I'm not totally attached to it, but if you want to fix it it'll need to be written out in full that it's "a value named X of type Y".

----------

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

From report at bugs.python.org  Wed Aug 15 09:48:16 2018
From: report at bugs.python.org (Ammar Askar)
Date: Wed, 15 Aug 2018 13:48:16 +0000
Subject: [docs] [issue34398] Docs search does not index glossary items
In-Reply-To: <1534233148.48.0.56676864532.issue34398@psf.upfronthosting.co.za>
Message-ID: <1534340896.6.0.902498594338.issue34398@psf.upfronthosting.co.za>


Change by Ammar Askar <ammar at ammaraskar.com>:


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

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

From report at bugs.python.org  Wed Aug 15 09:50:41 2018
From: report at bugs.python.org (Ammar Askar)
Date: Wed, 15 Aug 2018 13:50:41 +0000
Subject: [docs] [issue34398] Docs search does not index glossary items
In-Reply-To: <1534233148.48.0.56676864532.issue34398@psf.upfronthosting.co.za>
Message-ID: <1534341041.0.0.56676864532.issue34398@psf.upfronthosting.co.za>


Ammar Askar <ammar at ammaraskar.com> added the comment:

I think showing glossary results up top in the search page is a good idea, so I wrote up a quick proof of concept sphinx extension to do so. The diff isn't very big or complicated but it does need a bit of cleanup, especially the javascript and presentation side.

There are some screenshots in the pull request.

(Adding Berker since they reviewed the change to move the search bar in the header for the docs)

----------
nosy: +berker.peksag

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

From report at bugs.python.org  Wed Aug 15 10:00:27 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Wed, 15 Aug 2018 14:00:27 +0000
Subject: [docs] [issue34398] Docs search does not index glossary items
In-Reply-To: <1534233148.48.0.56676864532.issue34398@psf.upfronthosting.co.za>
Message-ID: <1534341627.15.0.56676864532.issue34398@psf.upfronthosting.co.za>


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

Thank you for this, Ammar. Proof of concept solution is good progress. I'm well impressed. The screen shots convince me that it's well worth doing.

For me, the one thing that's missing is a link just above the glossary item. Something like "Glossary: iterable". You're probably aware of this, and so far it's only proof-of-concept.

Oh, and of course that the links in the displayed item work. My be a gotcha here for links to other glossary items.

So, well done, and thank you very much.

----------

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

From report at bugs.python.org  Wed Aug 15 10:05:52 2018
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 15 Aug 2018 14:05:52 +0000
Subject: [docs] [issue34398] Docs search does not index glossary items
In-Reply-To: <1534233148.48.0.56676864532.issue34398@psf.upfronthosting.co.za>
Message-ID: <1534341952.36.0.56676864532.issue34398@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Ammar's pull request looks good to me, but it would be nice to include the item's title in the box. I will add my comments about the design and implementation in the pull request.

----------
resolution: third party -> 

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

From report at bugs.python.org  Wed Aug 15 11:09:53 2018
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 15 Aug 2018 15:09:53 +0000
Subject: [docs] [issue27026] async/await keywords are missing from reference
 docs
In-Reply-To: <1463299580.57.0.0973198258941.issue27026@psf.upfronthosting.co.za>
Message-ID: <1534345793.1.0.56676864532.issue27026@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

The list has been updated in https://github.com/python/cpython/commit/bf9d317626eebcf79bd0756b4dd43df82d5cc186 (Issue 31810

Closing this as 'outdated'. Thanks for the report and for the patch.

----------
nosy: +berker.peksag
resolution:  -> out of date
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Aug 16 05:23:27 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 16 Aug 2018 09:23:27 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1534411407.26.0.902498594338.issue33216@psf.upfronthosting.co.za>


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


----------
pull_requests: +8256

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

From report at bugs.python.org  Thu Aug 16 06:25:31 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 16 Aug 2018 10:25:31 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1534415131.19.0.902498594338.issue33216@psf.upfronthosting.co.za>


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


----------
pull_requests: +8257

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

From report at bugs.python.org  Thu Aug 16 11:46:13 2018
From: report at bugs.python.org (Eric Snow)
Date: Thu, 16 Aug 2018 15:46:13 +0000
Subject: [docs] [issue34413] Porting section of 3.5 "What's New" doc does
 not mention bytecode changes.
Message-ID: <1534434373.24.0.56676864532.issue34413@psf.upfronthosting.co.za>


New submission from Eric Snow <ericsnowcurrently at gmail.com>:

In the 3.5 "What's New" doc, the porting section [1] does not mention the bytecode changes resulting from the PEP 448 implementation. [2][3]  It should.

I've marked this issue for the versions past 3.5 because each branch has its own "What's New" doc for 3.5.

[1] https://docs.python.org/3/whatsnew/3.5.html#porting-to-python-3-5
[2] bpo-33216
[3] https://github.com/python/cpython/pull/8783#discussion_r210642202

----------
assignee: docs at python
components: Documentation
messages: 323605
nosy: docs at python, eric.snow, serhiy.storchaka
priority: low
severity: normal
stage: needs patch
status: open
title: Porting section of 3.5 "What's New" doc does not mention bytecode changes.
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/issue34413>
_______________________________________

From report at bugs.python.org  Thu Aug 16 11:48:42 2018
From: report at bugs.python.org (Eric Snow)
Date: Thu, 16 Aug 2018 15:48:42 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1534434522.07.0.56676864532.issue33216@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

FTR, the change was introduced by the PEP 448 implementation. [1]

[1] https://github.com/python/cpython/pull/8338#issuecomment-406256152

----------
nosy: +eric.snow

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

From report at bugs.python.org  Thu Aug 16 11:51:00 2018
From: report at bugs.python.org (Eric Snow)
Date: Thu, 16 Aug 2018 15:51:00 +0000
Subject: [docs] [issue33216] [3.5] Wrong order of stack for
 CALL_FUNCTION_VAR and CALL_FUNCTION_VAR_KW
In-Reply-To: <1522784543.83.0.467229070634.issue33216@psf.upfronthosting.co.za>
Message-ID: <1534434660.89.0.56676864532.issue33216@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

FYI, I opened bpo-34413 to address how the bytecode change is not mentioned in the porting section of the 3.5 "What's New" doc.  In retrospect (I didn't notice that this issue was still open), I suppose that doesn't need a separate issue so feel free to close #34413 in favor of this one. :)

----------

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

From report at bugs.python.org  Fri Aug 17 02:08:18 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 17 Aug 2018 06:08:18 +0000
Subject: [docs] [issue34413] Porting section of 3.5 "What's New" doc does
 not mention bytecode changes.
In-Reply-To: <1534434373.24.0.56676864532.issue34413@psf.upfronthosting.co.za>
Message-ID: <1534486098.75.0.56676864532.issue34413@psf.upfronthosting.co.za>


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

I don't think this needs to be exposed in What's New. This is a very low level implementation detail and isn't interested for most users. I think it would just distract attention from more significant changes.

But it may be worth to document this change in the NEWS file.

Changes in BUILD_MAP affected more users and also was not mentioned in the NEWS file. It was documented in the dis module documentation only in issue26213.

----------

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

From report at bugs.python.org  Fri Aug 17 03:45:47 2018
From: report at bugs.python.org (Sebastian Rittau)
Date: Fri, 17 Aug 2018 07:45:47 +0000
Subject: [docs] [issue34418] Arguments missing from documentation for
 HTTPErrorProcessor.http(s)_response()
Message-ID: <1534491947.25.0.56676864532.issue34418@psf.upfronthosting.co.za>


New submission from Sebastian Rittau <srittau at rittau.biz>:

The documentation at https://docs.python.org/3/library/urllib.request.html#urllib.request.HTTPErrorProcessor does not list the two arguments "request" and "response" that HTTPErrorProcessor.http_response() and https_response() actually require. (I checked the implementation in Python 3.5 and 3.7.)

----------
assignee: docs at python
components: Documentation
messages: 323638
nosy: docs at python, srittau
priority: normal
severity: normal
status: open
title: Arguments missing from documentation for HTTPErrorProcessor.http(s)_response()
versions: Python 3.5, Python 3.7

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

From report at bugs.python.org  Fri Aug 17 03:53:41 2018
From: report at bugs.python.org (Sebastian Rittau)
Date: Fri, 17 Aug 2018 07:53:41 +0000
Subject: [docs] [issue34418] Arguments missing from documentation for
 HTTPErrorProcessor.http(s)_response()
In-Reply-To: <1534491947.25.0.56676864532.issue34418@psf.upfronthosting.co.za>
Message-ID: <1534492421.27.0.902498594338.issue34418@psf.upfronthosting.co.za>


Change by Sebastian Rittau <srittau at rittau.biz>:


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

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

From report at bugs.python.org  Fri Aug 17 05:47:35 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 17 Aug 2018 09:47:35 +0000
Subject: [docs] [issue34418] Arguments missing from documentation for
 HTTPErrorProcessor.http(s)_response()
In-Reply-To: <1534491947.25.0.56676864532.issue34418@psf.upfronthosting.co.za>
Message-ID: <1534499255.72.0.56676864532.issue34418@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset c53aaec793e018edef4e72a3edbd338b10db10aa by Berker Peksag (Sebastian Rittau) in branch 'master':
bpo-34418: Fix HTTPErrorProcessor documentation (GH-8793)
https://github.com/python/cpython/commit/c53aaec793e018edef4e72a3edbd338b10db10aa


----------
nosy: +berker.peksag

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

From report at bugs.python.org  Fri Aug 17 05:48:23 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 17 Aug 2018 09:48:23 +0000
Subject: [docs] [issue34418] Arguments missing from documentation for
 HTTPErrorProcessor.http(s)_response()
In-Reply-To: <1534491947.25.0.56676864532.issue34418@psf.upfronthosting.co.za>
Message-ID: <1534499303.53.0.902498594338.issue34418@psf.upfronthosting.co.za>


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


----------
pull_requests: +8269

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

From report at bugs.python.org  Fri Aug 17 05:48:34 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 17 Aug 2018 09:48:34 +0000
Subject: [docs] [issue34418] Arguments missing from documentation for
 HTTPErrorProcessor.http(s)_response()
In-Reply-To: <1534491947.25.0.56676864532.issue34418@psf.upfronthosting.co.za>
Message-ID: <1534499314.51.0.902498594338.issue34418@psf.upfronthosting.co.za>


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


----------
pull_requests: +8270

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

From report at bugs.python.org  Fri Aug 17 06:02:14 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 17 Aug 2018 10:02:14 +0000
Subject: [docs] [issue34418] Arguments missing from documentation for
 HTTPErrorProcessor.http(s)_response()
In-Reply-To: <1534491947.25.0.56676864532.issue34418@psf.upfronthosting.co.za>
Message-ID: <1534500134.31.0.56676864532.issue34418@psf.upfronthosting.co.za>


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


New changeset 05d89ef785ab3cb6dd28f10f312f68f8e6a163ce by Miss Islington (bot) in branch '3.7':
bpo-34418: Fix HTTPErrorProcessor documentation (GH-8793)
https://github.com/python/cpython/commit/05d89ef785ab3cb6dd28f10f312f68f8e6a163ce


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

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

From report at bugs.python.org  Fri Aug 17 06:35:55 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 17 Aug 2018 10:35:55 +0000
Subject: [docs] [issue34418] Arguments missing from documentation for
 HTTPErrorProcessor.http(s)_response()
In-Reply-To: <1534491947.25.0.56676864532.issue34418@psf.upfronthosting.co.za>
Message-ID: <1534502155.84.0.56676864532.issue34418@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 02c4d4b6dcd772ec3a7fdca517118f3fa53b0b88 by Berker Peksag (Miss Islington (bot)) in branch '3.6':
bpo-34418: Fix HTTPErrorProcessor documentation (GH-8793)
https://github.com/python/cpython/commit/02c4d4b6dcd772ec3a7fdca517118f3fa53b0b88


----------

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

From report at bugs.python.org  Fri Aug 17 06:37:24 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 17 Aug 2018 10:37:24 +0000
Subject: [docs] [issue34418] Arguments missing from documentation for
 HTTPErrorProcessor.http(s)_response()
In-Reply-To: <1534491947.25.0.56676864532.issue34418@psf.upfronthosting.co.za>
Message-ID: <1534502244.29.0.56676864532.issue34418@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thanks for the report and for the patch! 3.5 is in security-fix-only mode, so it doesn't get documentation fixes anymore.

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type:  -> behavior
versions: +Python 3.6, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Fri Aug 17 13:58:49 2018
From: report at bugs.python.org (Steve Dower)
Date: Fri, 17 Aug 2018 17:58:49 +0000
Subject: [docs] [issue34365] datetime's documentation refers to "comparison
 [...] falling back to the default scheme of comparing object addresses"
In-Reply-To: <1533791029.87.0.56676864532.issue34365@psf.upfronthosting.co.za>
Message-ID: <1534528729.54.0.902498594338.issue34365@psf.upfronthosting.co.za>


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


----------
keywords: +easy
versions:  -Python 3.4, Python 3.5

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

From report at bugs.python.org  Fri Aug 17 16:40:47 2018
From: report at bugs.python.org (Eric Snow)
Date: Fri, 17 Aug 2018 20:40:47 +0000
Subject: [docs] [issue34413] Porting section of 3.5 "What's New" doc does
 not mention bytecode changes.
In-Reply-To: <1534434373.24.0.56676864532.issue34413@psf.upfronthosting.co.za>
Message-ID: <1534538447.32.0.56676864532.issue34413@psf.upfronthosting.co.za>


Eric Snow <ericsnowcurrently at gmail.com> added the comment:

Fair enough.  Having the note in the 3.5 docs should be fine. :)

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

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

From report at bugs.python.org  Sat Aug 18 01:35:11 2018
From: report at bugs.python.org (Nojima Takahide)
Date: Sat, 18 Aug 2018 05:35:11 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
Message-ID: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>


New submission from Nojima Takahide <nozzy123nozzy at gmail.com>:

In the Section "LLTRACE" of $(Python3.6-source)/Misc/SpecialBuilds.txt , it describes variable name is "__lltrace__",however it seems to be wrong, "__ltrace__" is correct. Would someone correct this document?

----------
assignee: docs at python
components: Documentation
messages: 323692
nosy: Nojima Takahide, docs at python
priority: normal
severity: normal
status: open
title: "__lltrace__"  seems to be wrong , "__ltrace__" is correct in Misc/SpecialBuilds.txt
type: behavior
versions: Python 3.6

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

From report at bugs.python.org  Sat Aug 18 04:53:45 2018
From: report at bugs.python.org (Danish Prakash)
Date: Sat, 18 Aug 2018 08:53:45 +0000
Subject: [docs] [issue34365] datetime's documentation refers to "comparison
 [...] falling back to the default scheme of comparing object addresses"
In-Reply-To: <1533791029.87.0.56676864532.issue34365@psf.upfronthosting.co.za>
Message-ID: <1534582425.75.0.56676864532.issue34365@psf.upfronthosting.co.za>


Danish Prakash <grafitykoncept at gmail.com> added the comment:

> But in 3.x, comparison no longer falls back to comparing object addresses.

What is the default fallback in 3.x?

----------
nosy: +prakashdanish

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

From report at bugs.python.org  Sat Aug 18 07:00:17 2018
From: report at bugs.python.org (dwich)
Date: Sat, 18 Aug 2018 11:00:17 +0000
Subject: [docs] [issue34429] On Windows tempfile.TemporaryFile behaves like
 NamedTemporaryFile
Message-ID: <1534590017.91.0.56676864532.issue34429@psf.upfronthosting.co.za>


New submission from dwich <michal.konvalinka at gmail.com>:

On Windows tempfile.TemporaryFile() accepts delete attribute. On Linux TemporaryFile() raises TypeError if delete attribute is used.

In tempfile.py source is the code below which means that on Windows TemporaryFile behaves like NamedTemporaryFile. I suppose the code should not be changed but the behaviour should be mentioned in documentation.

if _os.name != 'posix' or _os.sys.platform == 'cygwin':
    # On non-POSIX and Cygwin systems, assume that we cannot unlink a file
    # while it is open.
    TemporaryFile = NamedTemporaryFile

Steps to reproduce:
>>> import tempfile
>>> tf = tempfile.TemporaryFile(delete=False)

On Linux Python throws TypeError:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: TemporaryFile() got an unexpected keyword argument 'delete'

On Windows Python does not throw TypeError because on Windows TemporaryFile is in fact NamedTemporaryFile which accepts delete attribute.

Tested on all these versions: 3.7.0 64 bit, 3.6.5 32 bit, 3.5.4 32 bit, 3.4.4 32 bit, 2.7.15 32 bit 


Proposed text to tempfile.TemporaryFile documentation:

On non POSIX or Cygwin platforms TemporaryFile behaves exacly like NamedTemporaryFile including the fact that TemporaryFile accepts delete attribute and does not raise
TypeError: TemporaryFile() got an unexpected keyword argument 'delete'.

----------
assignee: docs at python
components: Documentation
messages: 323702
nosy: docs at python, dwich
priority: normal
severity: normal
status: open
title: On Windows tempfile.TemporaryFile behaves like NamedTemporaryFile
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Sat Aug 18 09:15:30 2018
From: report at bugs.python.org (Kevin Norris)
Date: Sat, 18 Aug 2018 13:15:30 +0000
Subject: [docs] [issue34365] datetime's documentation refers to "comparison
 [...] falling back to the default scheme of comparing object addresses"
In-Reply-To: <1533791029.87.0.56676864532.issue34365@psf.upfronthosting.co.za>
Message-ID: <1534598130.19.0.56676864532.issue34365@psf.upfronthosting.co.za>


Kevin Norris <nykevin.norris at gmail.com> added the comment:

There is none.  It raises a TypeError.  See https://docs.python.org/3/reference/expressions.html#value-comparisons

----------

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

From report at bugs.python.org  Sat Aug 18 12:03:19 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Sat, 18 Aug 2018 16:03:19 +0000
Subject: [docs] [issue34431] Docs does not eval allows code object as
 argument
Message-ID: <1534608199.83.0.56676864532.issue34431@psf.upfronthosting.co.za>


New submission from Jonathan Fine <jfine2358 at gmail.com>:

See https://docs.python.org/3.6/library/functions.html#eval
This says the following won't happen. But it does.

Python 3.6.2 (default, Jul 29 2017, 00:00:00) 
[GCC 4.8.4] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> def fn(): print(3); return 4
... 
>>> eval(fn.__code__)
3
4

Compare with https://docs.python.org/3.6/library/functions.html#exec

Search for eval in title of open issues bring up related

#22057 (The doc say all globals are copied on eval(), but only __builtins__ is copied)
#25810 (Python 3 documentation for eval is incorrect)

----------
assignee: docs at python
components: Documentation
messages: 323716
nosy: docs at python, jfine2358
priority: normal
severity: normal
status: open
title: Docs does not eval allows code object as argument
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/issue34431>
_______________________________________

From report at bugs.python.org  Sat Aug 18 12:49:19 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 18 Aug 2018 16:49:19 +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: <1534610959.82.0.56676864532.issue34431@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thank you for your report.

Quoting from https://docs.python.org/3.6/library/functions.html#eval

    This function can also be used to execute arbitrary code objects
    (such as those created by compile()). In this case pass a code
    object instead of a string.

So, your example is already documented as a legal way of using the eval() function.

I don't see anything wrong here.

----------
nosy: +berker.peksag
resolution:  -> not a bug
status: open -> pending
type:  -> behavior
versions:  -Python 3.4, Python 3.5

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

From report at bugs.python.org  Sat Aug 18 13:05:23 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 18 Aug 2018 17:05:23 +0000
Subject: [docs] [issue34432] doc Mention complex and decimal.Decimal on
 str.format note about locales
Message-ID: <1534611923.59.0.56676864532.issue34432@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

On str.format method, the note about how locales are dealt with reads:

"When formatting a number (int, float, float and subclasses)..."

PR removes the second float, and mentions complex and decimal.Decimal.

The bug which introduced this note is: #31900

----------
assignee: docs at python
components: Documentation
messages: 323718
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Mention complex and decimal.Decimal on str.format note about locales
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat Aug 18 13:06:40 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 18 Aug 2018 17:06:40 +0000
Subject: [docs] [issue34432] doc Mention complex and decimal.Decimal on
 str.format note about locales
In-Reply-To: <1534611923.59.0.56676864532.issue34432@psf.upfronthosting.co.za>
Message-ID: <1534612000.76.0.902498594338.issue34432@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


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

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

From report at bugs.python.org  Sat Aug 18 13:15:27 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Sat, 18 Aug 2018 17:15:27 +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: <1534612527.64.0.56676864532.issue34431@psf.upfronthosting.co.za>


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

Summary: There's my problem, and others. I'm willing to provide a patch, if supported.

There's a gotcha here. I fell into it. The docs for eval state
===
eval(expression, globals=None, locals=None)
The arguments are a string and optional globals and locals.
===
I read this and concluded, fairly I think, that I'm not allowed to pass in a code object [1]. So I didn't read any further. I'd already got the answer to my question.

But I knew that exec would take a code object, so I had doubt, and did my little experiment.

I'd prefer something more like exec, which says
===
This function supports dynamic execution of Python code. object must be either a string or a code object.
===

There are other problems, such as not agreeing with the help(eval) etc messages (and the still open #22057, #25810):
===
eval(source, globals=None, locals=None, /)
    Evaluate the given source in the context of globals and locals.
    
    The source may be a string representing a Python expression
    or a code object as returned by compile().
    The globals must be a dictionary and locals can be any mapping,
    defaulting to the current globals and locals.
    If only globals is given, locals defaults to it.
===
exec(source, globals=None, locals=None, /)
    Execute the given source in the context of globals and locals.
    
    The source may be a string representing one or more Python statements
    or a code object as returned by compile().
    The globals must be a dictionary and locals can be any mapping,
    defaulting to the current globals and locals.
    If only globals is given, locals defaults to it.
===

Finally, I'm willing to provide a patch, if supported. (I've not contributed to Python before.)

[1] I'd just read the docs for exec, which is up-front about 'string or code'.

----------
status: pending -> open

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

From report at bugs.python.org  Sat Aug 18 13:36:27 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Sat, 18 Aug 2018 17:36:27 +0000
Subject: [docs] [issue34432] doc Mention complex and decimal.Decimal on
 str.format note about locales
In-Reply-To: <1534611923.59.0.56676864532.issue34432@psf.upfronthosting.co.za>
Message-ID: <1534613787.29.0.56676864532.issue34432@psf.upfronthosting.co.za>


Eric V. Smith <eric at trueblade.com> added the comment:


New changeset 93b5655c040a33f9ba4cdbd303afc8398c8413c7 by Eric V. Smith (Andr?s Delfino) in branch 'master':
bpo-34432: doc Mention complex and decimal.Decimal on str.format not about locales (GH-8808)
https://github.com/python/cpython/commit/93b5655c040a33f9ba4cdbd303afc8398c8413c7


----------
nosy: +eric.smith

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

From report at bugs.python.org  Sat Aug 18 13:36:40 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 18 Aug 2018 17:36:40 +0000
Subject: [docs] [issue34432] doc Mention complex and decimal.Decimal on
 str.format note about locales
In-Reply-To: <1534611923.59.0.56676864532.issue34432@psf.upfronthosting.co.za>
Message-ID: <1534613800.82.0.902498594338.issue34432@psf.upfronthosting.co.za>


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


----------
pull_requests: +8286

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

From report at bugs.python.org  Sat Aug 18 13:36:57 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 18 Aug 2018 17:36:57 +0000
Subject: [docs] [issue34432] doc Mention complex and decimal.Decimal on
 str.format note about locales
In-Reply-To: <1534611923.59.0.56676864532.issue34432@psf.upfronthosting.co.za>
Message-ID: <1534613817.14.0.902498594338.issue34432@psf.upfronthosting.co.za>


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


----------
pull_requests: +8287

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

From report at bugs.python.org  Sat Aug 18 13:41:11 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 18 Aug 2018 17:41:11 +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: <1534614071.43.0.56676864532.issue34431@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Ok, I think it would be a good idea to mention that the function accepts a code object in the first sentence. I'd be happy to review such PR. The eval() documentation is located at https://github.com/python/cpython/blob/master/Doc/library/functions.rst

See https://devguide.python.org/ for more details about the contribution process.

Note that you need to sign the CLA in order to contribute to Python: https://www.python.org/psf/contrib/contrib-form/

#22057 and #25810 are out of scope for this issue, so let's not discuss them here.

----------
resolution: not a bug -> 
stage:  -> needs patch

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

From report at bugs.python.org  Sat Aug 18 13:43:41 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Sat, 18 Aug 2018 17:43:41 +0000
Subject: [docs] [issue34432] doc Mention complex and decimal.Decimal on
 str.format note about locales
In-Reply-To: <1534611923.59.0.56676864532.issue34432@psf.upfronthosting.co.za>
Message-ID: <1534614221.74.0.902498594338.issue34432@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


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

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

From report at bugs.python.org  Sat Aug 18 13:52:27 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Sat, 18 Aug 2018 17:52:27 +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: <1534614747.47.0.56676864532.issue34431@psf.upfronthosting.co.za>


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

OK. I'll do as you say. I've just signed the CLA.

----------

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

From report at bugs.python.org  Sat Aug 18 14:16:06 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Sat, 18 Aug 2018 18:16:06 +0000
Subject: [docs] [issue34432] doc Mention complex and decimal.Decimal on
 str.format note about locales
In-Reply-To: <1534611923.59.0.56676864532.issue34432@psf.upfronthosting.co.za>
Message-ID: <1534616165.95.0.56676864532.issue34432@psf.upfronthosting.co.za>


Eric V. Smith <eric at trueblade.com> added the comment:


New changeset fbd0a14cc941e340df0979d94ac55191dd31ad00 by Eric V. Smith (Miss Islington (bot)) in branch '3.6':
bpo-34432: doc Mention complex and decimal.Decimal on str.format not about locales (GH-8808) (GH-8810)
https://github.com/python/cpython/commit/fbd0a14cc941e340df0979d94ac55191dd31ad00


----------

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

From report at bugs.python.org  Sat Aug 18 14:16:39 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Sat, 18 Aug 2018 18:16:39 +0000
Subject: [docs] [issue34432] doc Mention complex and decimal.Decimal on
 str.format note about locales
In-Reply-To: <1534611923.59.0.56676864532.issue34432@psf.upfronthosting.co.za>
Message-ID: <1534616199.12.0.56676864532.issue34432@psf.upfronthosting.co.za>


Eric V. Smith <eric at trueblade.com> added the comment:


New changeset 0fd6f832a9c30404bf595a4af36e171d11fab024 by Eric V. Smith (Miss Islington (bot)) in branch '3.7':
bpo-34432: doc Mention complex and decimal.Decimal on str.format note about locales (GH-8808) (GH-8809)
https://github.com/python/cpython/commit/0fd6f832a9c30404bf595a4af36e171d11fab024


----------

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

From report at bugs.python.org  Sat Aug 18 16:09:47 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Sat, 18 Aug 2018 20:09:47 +0000
Subject: [docs] [issue34432] doc Mention complex and decimal.Decimal on
 str.format note about locales
In-Reply-To: <1534611923.59.0.56676864532.issue34432@psf.upfronthosting.co.za>
Message-ID: <1534622987.47.0.56676864532.issue34432@psf.upfronthosting.co.za>


Eric V. Smith <eric at trueblade.com> added the comment:

Thanks, Andr?s!

----------
assignee: docs at python -> eric.smith
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Aug 18 18:18:08 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 18 Aug 2018 22:18:08 +0000
Subject: [docs] [issue22057] The doc say all globals are copied on eval(),
 but only __builtins__ is copied
In-Reply-To: <1406210389.95.0.0796853252426.issue22057@psf.upfronthosting.co.za>
Message-ID: <1534630688.42.0.902498594338.issue22057@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


----------
pull_requests: +8290

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

From report at bugs.python.org  Sat Aug 18 18:19:40 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 18 Aug 2018 22:19:40 +0000
Subject: [docs] [issue22057] The doc say all globals are copied on eval(),
 but only __builtins__ is copied
In-Reply-To: <1406210389.95.0.0796853252426.issue22057@psf.upfronthosting.co.za>
Message-ID: <1534630780.73.0.56676864532.issue22057@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

I like Martin's suggestion in msg282262 and I've just created PR 8812 to implement it.

----------
nosy: +berker.peksag
type:  -> behavior
versions: +Python 3.8 -Python 3.5

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

From report at bugs.python.org  Sat Aug 18 20:07:48 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 Aug 2018 00:07:48 +0000
Subject: [docs] [issue26363] __builtins__ propagation is misleading
 described in exec and eval documentation
In-Reply-To: <1455532935.35.0.388834921119.issue26363@psf.upfronthosting.co.za>
Message-ID: <1534637267.76.0.56676864532.issue26363@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thank you for the report, Xavier.

This is a duplicate of issue 22057.

PR 8812 clarifies the behavior when a dictionary without a "__builtins__" key is passed as *globals* to eval(). I think that makes the opposite case much easier to understand.

>>> eval("print(spam)", {'__builtins__': {'spam': 'eggs'}})
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<string>", line 1, in <module>
NameError: name 'print' is not defined

>>> eval("print(spam)", {'__builtins__': {'spam': 'eggs', 'print': print}})
eggs

Also, I never needed to pass a dictionary with a "__builtins__" key to eval() before, so I don't think it's an important detail to document.

----------
nosy: +berker.peksag
resolution:  -> duplicate
stage: patch review -> resolved
status: open -> closed
superseder:  -> The doc say all globals are copied on eval(), but only __builtins__ is copied
type:  -> behavior
versions: +Python 3.8 -Python 3.5

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

From report at bugs.python.org  Sat Aug 18 22:38:36 2018
From: report at bugs.python.org (Danish Prakash)
Date: Sun, 19 Aug 2018 02:38:36 +0000
Subject: [docs] [issue34365] datetime's documentation refers to "comparison
 [...] falling back to the default scheme of comparing object addresses"
In-Reply-To: <1533791029.87.0.56676864532.issue34365@psf.upfronthosting.co.za>
Message-ID: <1534646316.29.0.902498594338.issue34365@psf.upfronthosting.co.za>


Change by Danish Prakash <grafitykoncept at gmail.com>:


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

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

From report at bugs.python.org  Sat Aug 18 22:52:43 2018
From: report at bugs.python.org (Danish Prakash)
Date: Sun, 19 Aug 2018 02:52:43 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1534647163.77.0.56676864532.issue34426@psf.upfronthosting.co.za>


Danish Prakash <grafitykoncept at gmail.com> added the comment:

> however it seems to be wrong, "__ltrace__" is correct

just curious how did you figure it out?

----------
nosy: +prakashdanish

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

From report at bugs.python.org  Sun Aug 19 06:25:40 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 Aug 2018 10:25:40 +0000
Subject: [docs] [issue22057] The doc say all globals are copied on eval(),
 but only __builtins__ is copied
In-Reply-To: <1406210389.95.0.0796853252426.issue22057@psf.upfronthosting.co.za>
Message-ID: <1534674340.49.0.56676864532.issue22057@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:


New changeset 225b05548027d55aafb11b65f6a4a2bef2f5196f by Berker Peksag in branch 'master':
bpo-22057: Clarify eval() documentation (GH-8812)
https://github.com/python/cpython/commit/225b05548027d55aafb11b65f6a4a2bef2f5196f


----------

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

From report at bugs.python.org  Sun Aug 19 06:25:46 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 19 Aug 2018 10:25:46 +0000
Subject: [docs] [issue22057] The doc say all globals are copied on eval(),
 but only __builtins__ is copied
In-Reply-To: <1406210389.95.0.0796853252426.issue22057@psf.upfronthosting.co.za>
Message-ID: <1534674345.99.0.902498594338.issue22057@psf.upfronthosting.co.za>


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


----------
pull_requests: +8296

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

From report at bugs.python.org  Sun Aug 19 06:25:54 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 19 Aug 2018 10:25:54 +0000
Subject: [docs] [issue22057] The doc say all globals are copied on eval(),
 but only __builtins__ is copied
In-Reply-To: <1406210389.95.0.0796853252426.issue22057@psf.upfronthosting.co.za>
Message-ID: <1534674354.23.0.902498594338.issue22057@psf.upfronthosting.co.za>


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


----------
pull_requests: +8297

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

From report at bugs.python.org  Sun Aug 19 06:29:53 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 19 Aug 2018 10:29:53 +0000
Subject: [docs] [issue22057] The doc say all globals are copied on eval(),
 but only __builtins__ is copied
In-Reply-To: <1406210389.95.0.0796853252426.issue22057@psf.upfronthosting.co.za>
Message-ID: <1534674593.11.0.56676864532.issue22057@psf.upfronthosting.co.za>


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


New changeset 0e1e8dbb0b99ec78f4567382428fdd46e2244d40 by Miss Islington (bot) in branch '3.7':
bpo-22057: Clarify eval() documentation (GH-8812)
https://github.com/python/cpython/commit/0e1e8dbb0b99ec78f4567382428fdd46e2244d40


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

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

From report at bugs.python.org  Sun Aug 19 06:32:15 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 19 Aug 2018 10:32:15 +0000
Subject: [docs] [issue22057] The doc say all globals are copied on eval(),
 but only __builtins__ is copied
In-Reply-To: <1406210389.95.0.0796853252426.issue22057@psf.upfronthosting.co.za>
Message-ID: <1534674735.59.0.56676864532.issue22057@psf.upfronthosting.co.za>


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


New changeset f19579b8f1fcd2dd8ffaf3e443b09930057c01d1 by Miss Islington (bot) in branch '3.6':
bpo-22057: Clarify eval() documentation (GH-8812)
https://github.com/python/cpython/commit/f19579b8f1fcd2dd8ffaf3e443b09930057c01d1


----------

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

From report at bugs.python.org  Sun Aug 19 06:53:32 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 Aug 2018 10:53:32 +0000
Subject: [docs] [issue22057] The doc say all globals are copied on eval(),
 but only __builtins__ is copied
In-Reply-To: <1406210389.95.0.0796853252426.issue22057@psf.upfronthosting.co.za>
Message-ID: <1534676012.06.0.56676864532.issue22057@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thanks for the review, Martin, and thanks for the report, Alon!

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

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

From report at bugs.python.org  Sun Aug 19 07:20:42 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 Aug 2018 11:20:42 +0000
Subject: [docs] [issue25810] Python 3 documentation for eval is incorrect
In-Reply-To: <1449346403.16.0.483198527619.issue25810@psf.upfronthosting.co.za>
Message-ID: <1534677642.22.0.902498594338.issue25810@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


----------
nosy: +berker.peksag

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

From report at bugs.python.org  Sun Aug 19 08:08:26 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 Aug 2018 12:08:26 +0000
Subject: [docs] [issue27088] doc: select: epoll.poll: incorrect timeout
 units, missing maxevents
In-Reply-To: <1463960371.93.0.0941923922389.issue27088@psf.upfronthosting.co.za>
Message-ID: <1534680506.29.0.56676864532.issue27088@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

Thanks for the report. In the title, you mentioned epoll.poll(), but you gave the link to the poll.poll() documentation. Also, the part you quoted

    If timeout is given, it specifies the length of time in milliseconds
    which the system will wait for events before returning.

is from the poll.poll() documentation.

Currently, the documentation for epoll.poll() is pretty minimal:

    epoll.poll(timeout=-1, maxevents=-1)
    
    Wait for events. timeout in seconds (float)

There is an open issue to improve epoll.poll() documentation: Issue 29247. Also, there is a review comment about explaining the *maxevent* parameter (https://github.com/python/cpython/pull/4798/files#r174309761), so I'm going to address the issues you've mentioned in msg266118 as part of issue 29247.

In the meantime, I'm closing this as a duplicate of issue 29247.

----------
nosy: +berker.peksag
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Document return value of epoll.poll
type:  -> behavior

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

From report at bugs.python.org  Sun Aug 19 08:16:23 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 19 Aug 2018 12:16:23 +0000
Subject: [docs] [issue18925] select.poll.modify is not documented
In-Reply-To: <1378328037.99.0.424927131422.issue18925@psf.upfronthosting.co.za>
Message-ID: <1534680983.21.0.56676864532.issue18925@psf.upfronthosting.co.za>


Berker Peksag <berker.peksag at gmail.com> added the comment:

poll.modify() is documented in both Python 2 and Python 3 docs:

* https://docs.python.org/2/library/select.html#select.poll.modify

* https://docs.python.org/3/library/select.html#select.poll.modify

> I believe that should be "Modify a registered file descriptor"...

This has already been fixed in https://github.com/python/cpython/commit/632c812942d662b764ade56ef492850e00d92877.

Closing this as 'out of date'.

----------
nosy: +berker.peksag
resolution:  -> out of date
stage:  -> resolved
status: open -> closed
type:  -> behavior

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

From report at bugs.python.org  Sun Aug 19 12:12:22 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 19 Aug 2018 16:12:22 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1534695142.05.0.56676864532.issue34426@psf.upfronthosting.co.za>


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

Hi @Nojima and thank you for the report. Do you mind doing a PR?

If not, I can do it myself.

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

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

From report at bugs.python.org  Sun Aug 19 12:12:44 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 19 Aug 2018 16:12:44 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1534695164.12.0.902498594338.issue34426@psf.upfronthosting.co.za>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


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

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

From report at bugs.python.org  Sun Aug 19 12:12:49 2018
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Sun, 19 Aug 2018 16:12:49 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1534695169.94.0.56676864532.issue34426@psf.upfronthosting.co.za>


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

Content	
 
Hi @Nojima and thank you for the report. Do you mind doing a PR?

If not, I can do it myself if you prefer.

----------

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

From report at bugs.python.org  Sun Aug 19 12:35:50 2018
From: report at bugs.python.org (Danish Prakash)
Date: Sun, 19 Aug 2018 16:35:50 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1534696550.76.0.56676864532.issue34426@psf.upfronthosting.co.za>


Danish Prakash <grafitykoncept at gmail.com> added the comment:

@pablogsal I would love to fix this up

----------

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

From report at bugs.python.org  Sun Aug 19 13:08:21 2018
From: report at bugs.python.org (Danish Prakash)
Date: Sun, 19 Aug 2018 17:08:21 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1534698501.59.0.902498594338.issue34426@psf.upfronthosting.co.za>


Change by Danish Prakash <grafitykoncept at gmail.com>:


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

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

From report at bugs.python.org  Mon Aug 20 15:29:12 2018
From: report at bugs.python.org (Brett Cannon)
Date: Mon, 20 Aug 2018 19:29:12 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1534793352.36.0.56676864532.issue34434@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

Any interest in submitting a pull request to update the documentation?

----------
assignee:  -> docs at python
components: +Documentation
nosy: +brett.cannon, docs at python
title: Removal of kwargs for int() etc not described as change -> Removal of kwargs for built-in types not covered with "changed in Python" note in documentation

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

From report at bugs.python.org  Mon Aug 20 15:43:36 2018
From: report at bugs.python.org (Paul Ganssle)
Date: Mon, 20 Aug 2018 19:43:36 +0000
Subject: [docs] [issue34365] datetime's documentation refers to "comparison
 [...] falling back to the default scheme of comparing object addresses"
In-Reply-To: <1533791029.87.0.56676864532.issue34365@psf.upfronthosting.co.za>
Message-ID: <1534794216.69.0.902498594338.issue34365@psf.upfronthosting.co.za>


Change by Paul Ganssle <p.ganssle at gmail.com>:


----------
nosy: +p-ganssle

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

From report at bugs.python.org  Tue Aug 21 00:42:32 2018
From: report at bugs.python.org (underscore_asterisk)
Date: Tue, 21 Aug 2018 04:42:32 +0000
Subject: [docs] [issue33187] Document ElementInclude (XInclude) support in
 ElementTree
In-Reply-To: <1522427694.7.0.467229070634.issue33187@psf.upfronthosting.co.za>
Message-ID: <1534826552.69.0.56676864532.issue33187@psf.upfronthosting.co.za>


underscore_asterisk <ap.goel98 at gmail.com> added the comment:

Hello,

Can I take this up? I will create a PR either later today or tomorrow.

----------
nosy: +underscore_asterisk

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

From report at bugs.python.org  Tue Aug 21 06:45:08 2018
From: report at bugs.python.org (Louis Sautier)
Date: Tue, 21 Aug 2018 10:45:08 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1534848308.16.0.902498594338.issue34434@psf.upfronthosting.co.za>


Change by Louis Sautier <sautier.louis at gmail.com>:


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

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

From report at bugs.python.org  Tue Aug 21 14:50:18 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Tue, 21 Aug 2018 18:50:18 +0000
Subject: [docs] [issue34451] docs: tutorial/introduction doesn't mention
 toggle of prompts
Message-ID: <1534877418.64.0.56676864532.issue34451@psf.upfronthosting.co.za>


New submission from Jonathan Fine <jfine2358 at gmail.com>:

Interactive code examples need the prompt to be stripped, before copy-and-paste. This is explained in https://docs.python.org/3/tutorial/introduction.html

But this page does not tell us about the [>>>] prompt-toggle at top of each interactive code example. This caused a user error, reported in  https://mail.python.org/pipermail/python-ideas/2018-August/052869.html.

The [>>>] toggle isn't in the Python 2.7 docs, so nothing to fix there!

----------
assignee: docs at python
components: Documentation
messages: 323839
nosy: docs at python, jfine2358
priority: normal
severity: normal
status: open
title: docs: tutorial/introduction doesn't mention toggle of prompts
versions: 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/issue34451>
_______________________________________

From report at bugs.python.org  Tue Aug 21 15:01:13 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Tue, 21 Aug 2018 19:01:13 +0000
Subject: [docs] [issue34452] docs: help text for [>>>] toggle always in
 English
Message-ID: <1534878073.37.0.56676864532.issue34452@psf.upfronthosting.co.za>


New submission from Jonathan Fine <jfine2358 at gmail.com>:

As subject. Background information in #34451.

See https://docs.python.org/fr/3/tutorial/introduction.html

The hover help text for the [>>>] is in English, not French. Korean and Japanese documentation has the same problem.

----------
assignee: docs at python
components: Documentation
messages: 323840
nosy: docs at python, jfine2358
priority: normal
severity: normal
status: open
title: docs: help text for [>>>] toggle always in English
type: behavior
versions: 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/issue34452>
_______________________________________

From report at bugs.python.org  Tue Aug 21 15:23:02 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 21 Aug 2018 19:23:02 +0000
Subject: [docs] [issue34452] docs: help text for [>>>] toggle always in
 English
In-Reply-To: <1534878073.37.0.56676864532.issue34452@psf.upfronthosting.co.za>
Message-ID: <1534879382.78.0.56676864532.issue34452@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

The help text that says "Show the prompts and output" comes from python-docs-theme, and it is tracked in a separate repo: https://github.com/python/python-docs-theme/

Not sure if there's any customization that we can do here. I suggest raising the issue in python-docs-theme first.

----------
nosy: +Mariatta
resolution:  -> third party
stage:  -> resolved
status: open -> pending

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

From report at bugs.python.org  Tue Aug 21 15:23:11 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 21 Aug 2018 19:23:11 +0000
Subject: [docs] [issue34452] docs: help text for [>>>] toggle always in
 English
In-Reply-To: <1534878073.37.0.56676864532.issue34452@psf.upfronthosting.co.za>
Message-ID: <1534879391.84.0.902498594338.issue34452@psf.upfronthosting.co.za>


Change by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

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

From report at bugs.python.org  Tue Aug 21 15:51:39 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Tue, 21 Aug 2018 19:51:39 +0000
Subject: [docs] [issue34452] docs: help text for [>>>] toggle always in
 English
In-Reply-To: <1534878073.37.0.56676864532.issue34452@psf.upfronthosting.co.za>
Message-ID: <1534881099.74.0.56676864532.issue34452@psf.upfronthosting.co.za>


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

Thank you. I've raised
"The help text for [>>>] toggle always in English"
https://github.com/python/python-docs-theme/issues/23

----------

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

From report at bugs.python.org  Wed Aug 22 10:04:49 2018
From: report at bugs.python.org (Anjali Bansal)
Date: Wed, 22 Aug 2018 14:04:49 +0000
Subject: [docs] [issue33187] Document ElementInclude (XInclude) support in
 ElementTree
In-Reply-To: <1522427694.7.0.467229070634.issue33187@psf.upfronthosting.co.za>
Message-ID: <1534946689.92.0.902498594338.issue33187@psf.upfronthosting.co.za>


Change by Anjali Bansal <anjali.mca17.du at gmail.com>:


----------
keywords: +patch
pull_requests: +8332
stage: needs patch -> patch review

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

From report at bugs.python.org  Wed Aug 22 10:18:18 2018
From: report at bugs.python.org (Anjali Bansal)
Date: Wed, 22 Aug 2018 14:18:18 +0000
Subject: [docs] [issue33187] Document ElementInclude (XInclude) support in
 ElementTree
In-Reply-To: <1522427694.7.0.467229070634.issue33187@psf.upfronthosting.co.za>
Message-ID: <1534947498.79.0.56676864532.issue33187@psf.upfronthosting.co.za>


Anjali Bansal <anjali.mca17.du at gmail.com> added the comment:

Hello, 

I had created the PR for this issue. Please review and let me know if any modification required.

GitHub PR: https://github.com/python/cpython/pull/8861

bpo-33187: Fix document ElementInclude (XInclude) support in ElementTree issue.

----------

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

From report at bugs.python.org  Wed Aug 22 11:17:40 2018
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 22 Aug 2018 15:17:40 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1534951060.41.0.56676864532.issue34434@psf.upfronthosting.co.za>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

Bloating the documentation is almost certainly unjustifiable for list and tuple, and only barely justifiable for int, bool and float, given that:

1. The documentation (at least for Python 3) has *never* claimed the arguments could be passed by keyword (all of them used brackets to indicate the argument was optional without implying a meaningful default, which is typically how "does not take arguments by keyword" was described before the current "/" convention)

and

2. Aside from bool and float (and to a lesser extent, int), the documented name of said parameter didn't match the name it was accepted under, e.g.:

   a. The docs for tuple and list claimed the name was "iterable"; the only accepted name was "sequence"
   b. The online docs for int gave a wholly invalid "name", calling it "number | string", when in fact it was accepted only as "x". That said, int's docstring does describe the name "correctly" as "x"

So for tuple/list it would have been impossible to write code that depended on being able to pass the first parameter by keyword unless you'd gone mucking about in the CPython source code to figure out the secret keyword name. I could justify a note for int/bool/float given that the docstrings for all of them named the argument, and bool/float named it in the online docs, but we don't need to document a change that no one could have taken a dependency on without going to extreme trouble.

----------
nosy: +josh.r

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

From report at bugs.python.org  Wed Aug 22 11:34:33 2018
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 22 Aug 2018 15:34:33 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1534952073.48.0.56676864532.issue34434@psf.upfronthosting.co.za>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

Oh, I was checking old docs when I said the online docs didn't call int's argument "x"; the current docs do, so int, float and bool all justify a change (barely), it's just tuple and list for which it's completely unjustifiable.

----------

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

From report at bugs.python.org  Wed Aug 22 12:50:23 2018
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 22 Aug 2018 16:50:23 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1534956623.13.0.56676864532.issue34434@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

Please don't use over-the-top language like "completely unjustifiable" because it is unnecessary and in this case wrong. We treat our documentation as a recording of the semantics of the stdlib as well as a recording of what semantic changes occurred between versions. Something did change semantically and so it should be documented. Whether the way the docs have previously been written would have suggested that someone accidentally used keyword arguments is not the critical point. Anyone could have looked at e.g. help() or simply stumbled upon the fact keyword arguments used to work and then suddenly discovered they didn't. At that point it's more helpful to the user to know when that changed occurred then to try and minimize the amount of text in the  docs simply because they happened to have not been written to suggest keyword arguments worked when they, in fact, did.

IOW adding a "version changed" note is not bloat, it's about letting people know who happened to have used keyword arguments what version of Python is going to break their code.

----------

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

From report at bugs.python.org  Wed Aug 22 15:08:50 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Wed, 22 Aug 2018 19:08:50 +0000
Subject: [docs] [issue34464] docs: keywords are special - eg constants.html
Message-ID: <1534964930.72.0.56676864532.issue34464@psf.upfronthosting.co.za>


New submission from Jonathan Fine <jfine2358 at gmail.com>:

The identifiers True, False, None and __debug__ are keywords in the language.  For example
>>> __debug__ = __debug__
SyntaxError: assignment to keyword


1. The page constants.html incorrectly says then are in the built-in namespace. Some of them were, once.

2. The list keyword.kwlist does not contain __debug__. (Problem in Lib/keyword.py.)

3. https://docs.python.org/3/reference/datamodel.html for None, NotImplemented, etc.

4. There may be other places that need looking at.

See also: https://github.com/jfine2358/py-jfine2358/blob/master/docs/none-is-special.md

Credit: The __debug__ problem arises from Steve D'Aprano's message

https://mail.python.org/pipermail/python-ideas/2018-August/052917.html
The std lib contains a test that this correctly raises SyntaxError:
def f(*, x=lambda __debug__:0): pass

----------
assignee: docs at python
components: Documentation
messages: 323904
nosy: docs at python, jfine2358
priority: normal
severity: normal
status: open
title: docs: keywords are special - eg constants.html
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/issue34464>
_______________________________________

From report at bugs.python.org  Wed Aug 22 15:10:55 2018
From: report at bugs.python.org (Jonathan Fine)
Date: Wed, 22 Aug 2018 19:10:55 +0000
Subject: [docs] [issue34464] docs: keywords are special - eg constants.html
In-Reply-To: <1534964930.72.0.56676864532.issue34464@psf.upfronthosting.co.za>
Message-ID: <1534965055.88.0.56676864532.issue34464@psf.upfronthosting.co.za>


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

I'm happy to work on improving the text here. I'm new to contributing to Python. I'm being mentored to work on #34431.

Once I'm done with that, I'll be better placed to contributed to this issue.

----------

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

From report at bugs.python.org  Wed Aug 22 15:51:47 2018
From: report at bugs.python.org (R. David Murray)
Date: Wed, 22 Aug 2018 19:51:47 +0000
Subject: [docs] [issue34464] There are inconsitencies in the treatment of
 True, False, None, and __debug__ keywords in the docs
In-Reply-To: <1534964930.72.0.56676864532.issue34464@psf.upfronthosting.co.za>
Message-ID: <1534967507.12.0.56676864532.issue34464@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

I've removed 2.7 since those constants are not keywords in 2.7 (although None and __debug__ do raise syntax errors even in 2.7, they are not keywords there).  Which is almost certainly why the docs treat them inconsistently (leftovers from before they weren't keywords).  

We only update docs for the actively maintained versions, so I've removed everything before 3.6.  I also tried to clarify the issue in the title.

I don't know why you mention NotImplemented, that's not a keyword.

The issue with __debug__ and keywords.py probably requires a code change, since that file is auto-generated.  Please open a separate issue for that.

Thanks for wanting to improve python!

----------
nosy: +r.david.murray
title: docs: keywords are special - eg constants.html -> There are inconsitencies in the treatment of True, False, None, and __debug__ keywords in the docs
versions:  -Python 2.7, Python 3.4, Python 3.5

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

From report at bugs.python.org  Wed Aug 22 15:58:59 2018
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 22 Aug 2018 19:58:59 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1534967939.45.0.56676864532.issue34434@psf.upfronthosting.co.za>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

For tuple and list, no, they couldn't have looked at the help (because the help calls the argument "iterable", while the only keyword accepted was "sequence"). Nor was "sequence" documented in the online docs, nor anywhere else that I can find; it was solely in the C source code.

If it was discoverable in any other way, I wouldn't say documenting the change (outside of What's New) was completely unjustifiable (I acknowledge that int, bool and float warrant a mention, since they did document a functioning name for the argument; I was a little too down on them in my original messages).

But the only way someone would accidentally use keyword arguments for list/tuple is if they were fuzzing the constructor by submitting random keyword arguments until something worked. That seems an odd thing to worry about breaking. The error message wouldn't help either; the exception raised tells you what argument was unrecognized, but not the names of recognized arguments.

Even if you want to document it, it's hard to do so without being confusing, inaccurate, or both. The original PR's versionchanged message was:

*iterable* is now a positional-only parameter.

But "iterable" was never a legal keyword, so saying it's "now a positional-only parameter" implies that at some point, it wasn't, and you could pass it with the name "iterable", which is wrong/confusing. If you mention "sequence", you're mentioning a now defunct detail (confusing, but not wrong). I suppose you could have the versionchanged say "This function does not accept keyword arguments", but again, for all discoverable purposes, it never did.

I'm not saying *no* documentation of the change is needed, but I am saying, for list/tuple, the What's New note is sufficient to cover it for those people who went mucking through the CPython source code to find an undocumented keyword they could use.

----------

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

From report at bugs.python.org  Wed Aug 22 23:04:07 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 23 Aug 2018 03:04:07 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1534993447.2.0.56676864532.issue34434@psf.upfronthosting.co.za>


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

> I'm not saying *no* documentation of the change is needed, 
> but I am saying, for list/tuple, the What's New note is 
> sufficient to cover it for those people who went mucking 
> through the CPython source code to find an undocumented 
> keyword they could use.

That seems like a reasonable position to take.

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

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

From report at bugs.python.org  Thu Aug 23 10:41:27 2018
From: report at bugs.python.org (=?utf-8?b?SHJ2b2plIE5pa8WhacSH?=)
Date: Thu, 23 Aug 2018 14:41:27 +0000
Subject: [docs] [issue34476] asyncio.sleep(0) not documented
Message-ID: <1535035287.88.0.56676864532.issue34476@psf.upfronthosting.co.za>


New submission from Hrvoje Nik?i? <hniksic at gmail.com>:

Looking at the implementation and at the old issue at https://github.com/python/asyncio/issues/284 shows that asyncio.sleep special-cases asyncio.sleep(0) to mean "yield control to the event loop" without incurring additional overhead of sleeping. However, this is not documented at https://docs.python.org/3/library/asyncio-task.html#asyncio.sleep .

I propose to add to the documentation a statement along the lines of:

"""
A delay of 0 will relinquish control to the event loop, allowing other tasks and callbacks to run. The control will be returned to the coroutine as soon as they have run, without an explicit delay.
"""

----------
assignee: docs at python
components: Documentation, asyncio
messages: 323949
nosy: asvetlov, docs at python, hniksic, yselivanov
priority: normal
severity: normal
status: open
title: asyncio.sleep(0) not documented
versions: Python 3.7

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

From report at bugs.python.org  Thu Aug 23 10:42:20 2018
From: report at bugs.python.org (=?utf-8?b?SHJ2b2plIE5pa8WhacSH?=)
Date: Thu, 23 Aug 2018 14:42:20 +0000
Subject: [docs] [issue34476] asyncio.sleep(0) not documented
In-Reply-To: <1535035287.88.0.56676864532.issue34476@psf.upfronthosting.co.za>
Message-ID: <1535035340.07.0.56676864532.issue34476@psf.upfronthosting.co.za>


Hrvoje Nik?i? <hniksic at gmail.com> added the comment:

Also, the "Create a coroutine ..." wording in the current documentation is a bit strange - sleep() is already marked as a coroutine, and documentation of other coroutines simply state their effect in imperative.

----------

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

From report at bugs.python.org  Thu Aug 23 11:07:34 2018
From: report at bugs.python.org (Segev Finer)
Date: Thu, 23 Aug 2018 15:07:34 +0000
Subject: [docs] [issue34478] Possibly misleading/wrong documentation about
 PyModuleDef.m_free
Message-ID: <1535036854.66.0.56676864532.issue34478@psf.upfronthosting.co.za>


New submission from Segev Finer <segev208 at gmail.com>:

This section in the documentation https://docs.python.org/3.7/howto/cporting.html#module-initialization-and-state shows how to implement an extension module that works for both Python 2 and 3. It also shows how to use m_size to manage module state instead of using static globals. But it omits implementing m_free. This is also done in https://www.python.org/dev/peps/pep-3121/#example

To my understanding, m_clear is *only* called by the Python GC when the object is a part of a reference cycle. It won't be called for a normal free when the object wasn't a part of a reference cycle. This means that for such a case the objects referenced in the state structure will leak!

Looking around the standard library, it seems the extension modules there point m_free to calling the function used to implement m_clear.

The documentation of the structure is also quite unclear on the subject https://docs.python.org/3/c-api/module.html?highlight=pymoduledef#c.PyModuleDef.

P.S. There is also no freeing/DECREF-ing stuff in the state on error in the Python 2 case, but I think even the standard library is like this.

----------
assignee: docs at python
components: Documentation
messages: 323955
nosy: Segev Finer, docs at python
priority: normal
severity: normal
status: open
title: Possibly misleading/wrong documentation about PyModuleDef.m_free
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Aug 23 16:37:31 2018
From: report at bugs.python.org (Stefan Behnel)
Date: Thu, 23 Aug 2018 20:37:31 +0000
Subject: [docs] [issue33187] Document ElementInclude (XInclude) support in
 ElementTree
In-Reply-To: <1522427694.7.0.467229070634.issue33187@psf.upfronthosting.co.za>
Message-ID: <1535056651.03.0.902498594338.issue33187@psf.upfronthosting.co.za>


Change by Stefan Behnel <stefan_ml at behnel.de>:


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

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

From report at bugs.python.org  Thu Aug 23 17:14:39 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 23 Aug 2018 21:14:39 +0000
Subject: [docs] [issue34484] Unicode HOWTO incorrectly refers to Private Use
 Area for surrogateescape
Message-ID: <1535058879.5.0.56676864532.issue34484@psf.upfronthosting.co.za>


New submission from Mark Dickinson <dickinsm at gmail.com>:

The Unicode HOWTO currently has contains this text in the "Files in an Unknown Encoding" section [1]:

> The surrogateescape error handler will decode any non-ASCII bytes as code
> points in the Unicode Private Use Area ranging from U+DC80 to U+DCFF. These
> private code points will then be turned back into the same bytes when the
> surrogateescape error handler is used when encoding the data and writing it
> back out.

Unless I'm missing something, the subrange U+DC80 to U+DCFF of the low surrogates is *not* a Private Use Area. There *is* a kinda-sorta PUA in the high surrogates from U+DB80 to U+DBFF (because the only valid codepoints that use these surrogates in their UTF-16 encoding are the codepoints in planes 15 and 16, which are almost entirely PUA codepoints), but that's not what the surrogateescape handler is using.


[1] https://docs.python.org/3/howto/unicode.html#files-in-an-unknown-encoding

----------
assignee: docs at python
components: Documentation
messages: 323976
nosy: docs at python, mark.dickinson
priority: normal
severity: normal
status: open
title: Unicode HOWTO incorrectly refers to Private Use Area for surrogateescape
versions: Python 3.6, Python 3.7

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

From report at bugs.python.org  Thu Aug 23 17:24:39 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 23 Aug 2018 21:24:39 +0000
Subject: [docs] [issue34484] Unicode HOWTO incorrectly refers to Private Use
 Area for surrogateescape
In-Reply-To: <1535058879.5.0.56676864532.issue34484@psf.upfronthosting.co.za>
Message-ID: <1535059479.73.0.56676864532.issue34484@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

For history, this text was introduced as a result of issue #4163.

----------

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

From report at bugs.python.org  Thu Aug 23 17:25:15 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 23 Aug 2018 21:25:15 +0000
Subject: [docs] [issue34484] Unicode HOWTO incorrectly refers to Private Use
 Area for surrogateescape
In-Reply-To: <1535058879.5.0.56676864532.issue34484@psf.upfronthosting.co.za>
Message-ID: <1535059515.32.0.56676864532.issue34484@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

Whoops. Sorry, that should be #4153.

----------

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

From report at bugs.python.org  Thu Aug 23 19:52:02 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 23 Aug 2018 23:52:02 +0000
Subject: [docs] [issue28206] signal.Signals not documented
In-Reply-To: <1474297204.47.0.613989661481.issue28206@psf.upfronthosting.co.za>
Message-ID: <1535068322.14.0.902498594338.issue28206@psf.upfronthosting.co.za>


Change by Berker Peksag <berker.peksag at gmail.com>:


----------
nosy: +berker.peksag
type:  -> enhancement
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Fri Aug 24 10:44:31 2018
From: report at bugs.python.org (Gerrit Holl)
Date: Fri, 24 Aug 2018 14:44:31 +0000
Subject: [docs] [issue34487] enum _sunder_ names mix metaclass and enum
 class attributes
Message-ID: <1535121871.11.0.56676864532.issue34487@psf.upfronthosting.co.za>


New submission from Gerrit Holl <gerrit.holl at gmail.com>:

In the [`enum` module](https://docs.python.org/3/library/enum.html#supported-sunder-names) documentation, some of the `_sunder_` names are on `EnumMeta`, whereas others are on the produced `Enum` class:

> 8.13.15.3.2. Supported `_sunder_` names

> * `_name_` ? name of the member
> * `_value_` ? value of the member; can be set / modified in __new__
> * `_missing_` ? a lookup function used when a value is not found; may be overridden
> * `_ignore_` ? a list of names, either as a list() or a str(), that will not be transformed into members, and will be removed from the final class
> * `_order_` ? used in Python 2/3 code to ensure member order is consistent (class attribute, removed during class creation)
> * `_generate_next_value_` ? used by the Functional API and by auto to get an appropriate value for an enum member; may be overridden

Experimentally, it appears `_name_` and `_value_` are on the `Enum` class, whereas the others are all on the `EnumMeta` class:

In [272]: class Test(enum.Enum): a = 0

In [273]: Test.a._name_
Out[273]: 'a'

In [274]: Test._name
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-274-8d4f758e0fb7> in <module>()
----> 1 Test._name

/group_workspaces/cems2/fiduceo/Users/gholl/anaconda3/envs/FCDR37a/lib/python3.7/enum.py in __getattr__(cls, name)
    344             return cls._member_map_[name]
    345         except KeyError:
--> 346             raise AttributeError(name) from None
    347 
    348     def __getitem__(cls, name):

AttributeError: _name

In [275]: Test.a._value_
Out[275]: 0

In [276]: Test._value
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-276-a1cd5032d83d> in <module>()
----> 1 Test._value

/group_workspaces/cems2/fiduceo/Users/gholl/anaconda3/envs/FCDR37a/lib/python3.7/enum.py in __getattr__(cls, name)
    344             return cls._member_map_[name]
    345         except KeyError:
--> 346             raise AttributeError(name) from None
    347 
    348     def __getitem__(cls, name):

AttributeError: _value

In [277]: Test.a._missing_
Out[277]: <bound method Enum._missing_ of <enum 'Test'>>

In [278]: Test._missing_
Out[278]: <bound method Enum._missing_ of <enum 'Test'>>


This is not clear from the documentation.

----------
assignee: docs at python
components: Documentation
messages: 324003
nosy: Gerrit.Holl, docs at python
priority: normal
severity: normal
status: open
title: enum _sunder_ names mix metaclass and enum class attributes
versions: 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/issue34487>
_______________________________________

From report at bugs.python.org  Fri Aug 24 15:43:12 2018
From: report at bugs.python.org (Sergey G. Brester)
Date: Fri, 24 Aug 2018 19:43:12 +0000
Subject: [docs] [issue33515] subprocess.Popen on a Windows batch file always
 acts as if shell=True
In-Reply-To: <1526382091.26.0.682650639539.issue33515@psf.upfronthosting.co.za>
Message-ID: <1535139792.03.0.902498594338.issue33515@psf.upfronthosting.co.za>


Change by Sergey G. Brester <serg.brester at sebres.de>:


----------
keywords: +patch
pull_requests: +8375
stage: needs patch -> patch review

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

From report at bugs.python.org  Fri Aug 24 21:48:25 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 25 Aug 2018 01:48:25 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1535161705.51.0.902498594338.issue34426@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Aug 24 22:00:30 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Aug 2018 02:00:30 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1535162430.15.0.56676864532.issue34426@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:


New changeset 09efe49c07e2d5f93b415ead757c87e20cc0026f by Mariatta (Danish Prakash) in branch 'master':
bpo-34426: fix typo (__lltrace__ -> __ltrace__) (GH-8822)
https://github.com/python/cpython/commit/09efe49c07e2d5f93b415ead757c87e20cc0026f


----------
nosy: +Mariatta

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

From report at bugs.python.org  Fri Aug 24 22:00:36 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 25 Aug 2018 02:00:36 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1535162436.2.0.902498594338.issue34426@psf.upfronthosting.co.za>


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


----------
pull_requests: +8387

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

From report at bugs.python.org  Fri Aug 24 22:00:42 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 25 Aug 2018 02:00:42 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1535162442.04.0.902498594338.issue34426@psf.upfronthosting.co.za>


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


----------
pull_requests: +8388

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

From report at bugs.python.org  Fri Aug 24 22:08:01 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Aug 2018 02:08:01 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1535162881.56.0.56676864532.issue34426@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Thanks!

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

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

From report at bugs.python.org  Fri Aug 24 22:14:14 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 25 Aug 2018 02:14:14 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1535163254.78.0.56676864532.issue34426@psf.upfronthosting.co.za>


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


New changeset 0dc75f04575a6bfb2b072f62e5233444aea23e89 by Miss Islington (bot) in branch '3.7':
bpo-34426: fix typo (__lltrace__ -> __ltrace__) (GH-8822)
https://github.com/python/cpython/commit/0dc75f04575a6bfb2b072f62e5233444aea23e89


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

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

From report at bugs.python.org  Fri Aug 24 22:15:59 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Aug 2018 02:15:59 +0000
Subject: [docs] [issue34426] "__lltrace__"  seems to be wrong ,
 "__ltrace__" is correct in Misc/SpecialBuilds.txt
In-Reply-To: <1534570511.08.0.56676864532.issue34426@psf.upfronthosting.co.za>
Message-ID: <1535163359.36.0.56676864532.issue34426@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:


New changeset b26fcd6e22b7c150318d555f67b009cedcf5c797 by Mariatta (Miss Islington (bot)) in branch '3.6':
bpo-34426: fix typo (__lltrace__ -> __ltrace__) (GH-8822)
https://github.com/python/cpython/commit/b26fcd6e22b7c150318d555f67b009cedcf5c797


----------

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

From report at bugs.python.org  Fri Aug 24 22:21:30 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 25 Aug 2018 02:21:30 +0000
Subject: [docs] [issue34429] On Windows tempfile.TemporaryFile behaves like
 NamedTemporaryFile
In-Reply-To: <1534590017.91.0.56676864532.issue34429@psf.upfronthosting.co.za>
Message-ID: <1535163690.13.0.56676864532.issue34429@psf.upfronthosting.co.za>


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

3.4 and 3.5 only get security fixes.

Anyone preparing PR should check that behavior and doc is same on master; I just assumed in setting Versions header.

In the proposed text, it is not clear that 'non' applies to cygwin also.  Instead: "On platforms that are neither Posix nor Cygwin, ..."
Or "On non-Posix, non-Cygwin platforms, ..."

----------
nosy: +terry.reedy
versions: +Python 3.8 -Python 3.4, Python 3.5

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

From report at bugs.python.org  Fri Aug 24 22:28:17 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 25 Aug 2018 02:28:17 +0000
Subject: [docs] [issue33550] Sigpipe handling issue should be documented
In-Reply-To: <1526514952.03.0.682650639539.issue33550@psf.upfronthosting.co.za>
Message-ID: <1535164097.7.0.902498594338.issue33550@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Aug 24 22:29:01 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Aug 2018 02:29:01 +0000
Subject: [docs] [issue33550] Sigpipe handling issue should be documented
In-Reply-To: <1526514952.03.0.682650639539.issue33550@psf.upfronthosting.co.za>
Message-ID: <1535164141.74.0.56676864532.issue33550@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:


New changeset 7b0ed43af55c1e2844aa0ccd5e088b2ddd38dbdb by Mariatta (Miss Islington (bot)) in branch '3.7':
bpo-33550: Warn not to set SIGPIPE to SIG_DFL (GH-6773)
https://github.com/python/cpython/commit/7b0ed43af55c1e2844aa0ccd5e088b2ddd38dbdb


----------
nosy: +Mariatta

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

From report at bugs.python.org  Fri Aug 24 22:32:02 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 25 Aug 2018 02:32:02 +0000
Subject: [docs] [issue33550] Sigpipe handling issue should be documented
In-Reply-To: <1526514952.03.0.682650639539.issue33550@psf.upfronthosting.co.za>
Message-ID: <1535164322.52.0.56676864532.issue33550@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

Thanks!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions:  -Python 2.7, Python 3.4, Python 3.5, Python 3.6

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

From report at bugs.python.org  Sat Aug 25 11:09:41 2018
From: report at bugs.python.org (=?utf-8?q?Micka=C3=ABl_Schoentgen?=)
Date: Sat, 25 Aug 2018 15:09:41 +0000
Subject: [docs] [issue34500] Fix ResourceWarning in difflib.py
Message-ID: <1535209778.67.0.56676864532.issue34500@psf.upfronthosting.co.za>


New submission from Micka?l Schoentgen <contact at tiger-222.fr>:

Fix 2 unclosed files in the documentation and the difflib.py script:

diff.py:77: ResourceWarning: unclosed file <_io.TextIOWrapper name='/tmp/tmpnby8pemn' mode='U' encoding='UTF-8'>
    fromlines = open(fromfile, 'U').readlines()
diff.py:78: ResourceWarning: unclosed file <_io.TextIOWrapper name='/tmp/tmpnby8pemm' mode='U' encoding='UTF-8'>
    self.tolines = open(tofile, 'U').readlines()

----------
assignee: docs at python
components: Demos and Tools, Documentation
messages: 324071
nosy: David Bieber, Tiger-222, docs at python
priority: normal
severity: normal
status: open
title: Fix ResourceWarning in difflib.py
versions: Python 2.7

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

From report at bugs.python.org  Sat Aug 25 11:15:23 2018
From: report at bugs.python.org (=?utf-8?q?Micka=C3=ABl_Schoentgen?=)
Date: Sat, 25 Aug 2018 15:15:23 +0000
Subject: [docs] [issue34500] Fix ResourceWarning in difflib.py
In-Reply-To: <1535209778.67.0.56676864532.issue34500@psf.upfronthosting.co.za>
Message-ID: <1535210123.8.0.902498594338.issue34500@psf.upfronthosting.co.za>


Change by Micka?l Schoentgen <contact at tiger-222.fr>:


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

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

From report at bugs.python.org  Sat Aug 25 11:18:51 2018
From: report at bugs.python.org (=?utf-8?q?Micka=C3=ABl_Schoentgen?=)
Date: Sat, 25 Aug 2018 15:18:51 +0000
Subject: [docs] [issue34500] Fix ResourceWarning in difflib.py
In-Reply-To: <1535209778.67.0.56676864532.issue34500@psf.upfronthosting.co.za>
Message-ID: <1535210331.7.0.56676864532.issue34500@psf.upfronthosting.co.za>


Micka?l Schoentgen <contact at tiger-222.fr> added the comment:

This is a little patch to mostly keep aligned with https://github.com/google/python-fire/pull/135.

----------

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

From report at bugs.python.org  Sat Aug 25 13:54:28 2018
From: report at bugs.python.org (Alexey Izbyshev)
Date: Sat, 25 Aug 2018 17:54:28 +0000
Subject: [docs] [issue34502] Docs of sys.exit() mention utf8_mode for an
 unclear reason
Message-ID: <1535219668.13.0.56676864532.issue34502@psf.upfronthosting.co.za>


New submission from Alexey Izbyshev <izbyshev at ispras.ru>:

Docs for sys.exit() contain the following note added in https://github.com/python/cpython/blame/1871a4a35123b278443b960255cb14314ce196f6/Doc/library/sys.rst#L336

Changed in version 3.7: Added utf8_mode attribute for the new -X utf8 flag.

Does it belong to the adjacent docs for sys.flags (though they mention utf8_mode too)?

----------
assignee: docs at python
components: Documentation
messages: 324086
nosy: docs at python, izbyshev, vstinner
priority: normal
severity: normal
status: open
title: Docs of sys.exit() mention utf8_mode for an unclear reason
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat Aug 25 13:57:27 2018
From: report at bugs.python.org (Alexey Izbyshev)
Date: Sat, 25 Aug 2018 17:57:27 +0000
Subject: [docs] [issue34502] Docs of sys.exit() mention utf8_mode for an
 unclear reason
In-Reply-To: <1535219668.13.0.56676864532.issue34502@psf.upfronthosting.co.za>
Message-ID: <1535219847.99.0.902498594338.issue34502@psf.upfronthosting.co.za>


Change by Alexey Izbyshev <izbyshev at ispras.ru>:


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

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

From report at bugs.python.org  Sat Aug 25 14:23:04 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Sat, 25 Aug 2018 18:23:04 +0000
Subject: [docs] [issue34502] Docs of sys.exit() mention utf8_mode for an
 unclear reason
In-Reply-To: <1535219668.13.0.56676864532.issue34502@psf.upfronthosting.co.za>
Message-ID: <1535221384.78.0.56676864532.issue34502@psf.upfronthosting.co.za>


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


New changeset 44838be9f79870ff3c9e04b7398a1dc3d56d53ed by Benjamin Peterson (Alexey Izbyshev) in branch 'master':
closes bpo-34502: Remove a note about utf8_mode from sys.exit() docs. (GH-8928)
https://github.com/python/cpython/commit/44838be9f79870ff3c9e04b7398a1dc3d56d53ed


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

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

From report at bugs.python.org  Sat Aug 25 14:23:18 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 25 Aug 2018 18:23:18 +0000
Subject: [docs] [issue34502] Docs of sys.exit() mention utf8_mode for an
 unclear reason
In-Reply-To: <1535219668.13.0.56676864532.issue34502@psf.upfronthosting.co.za>
Message-ID: <1535221398.64.0.902498594338.issue34502@psf.upfronthosting.co.za>


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


----------
pull_requests: +8401

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

From report at bugs.python.org  Sat Aug 25 14:36:22 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 25 Aug 2018 18:36:22 +0000
Subject: [docs] [issue34502] Docs of sys.exit() mention utf8_mode for an
 unclear reason
In-Reply-To: <1535219668.13.0.56676864532.issue34502@psf.upfronthosting.co.za>
Message-ID: <1535222182.64.0.56676864532.issue34502@psf.upfronthosting.co.za>


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


New changeset 42a1ca65d00ba59fe63cc65df0ff297a885e61b8 by Miss Islington (bot) in branch '3.7':
closes bpo-34502: Remove a note about utf8_mode from sys.exit() docs. (GH-8928)
https://github.com/python/cpython/commit/42a1ca65d00ba59fe63cc65df0ff297a885e61b8


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

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

From report at bugs.python.org  Sun Aug 26 16:49:49 2018
From: report at bugs.python.org (harobed)
Date: Sun, 26 Aug 2018 20:49:49 +0000
Subject: [docs] [issue34511] I suggest to add documentation about "method"
 parameter of urllib.request.Request class
Message-ID: <1535316589.49.0.56676864532.issue34511@psf.upfronthosting.co.za>


New submission from harobed <stephane at harobed.org>:

Hi,

I see "method=None" parameter in urllib.request.Request constructor (https://github.com/python/cpython/blob/master/Lib/urllib/request.py#L327) but I don't see "method" parameter in documentation: https://docs.python.org/3.2/library/urllib.request.html#urllib.request.Request

I suggest to add documentation about "method".

Best regards,
St?phane

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 324134
nosy: docs at python, harobed
priority: normal
severity: normal
status: open
title: I suggest to add documentation about "method" parameter of urllib.request.Request class
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Sun Aug 26 17:05:59 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 26 Aug 2018 21:05:59 +0000
Subject: [docs] [issue34511] I suggest to add documentation about "method"
 parameter of urllib.request.Request class
In-Reply-To: <1535316589.49.0.56676864532.issue34511@psf.upfronthosting.co.za>
Message-ID: <1535317559.36.0.56676864532.issue34511@psf.upfronthosting.co.za>


Mariatta Wijaya <mariatta.wijaya at gmail.com> added the comment:

method is added in Python 3.3. You're referencing documentation of Python 3.2.

The documentation is correct for later Python versions: https://docs.python.org/3.7/library/urllib.request.html#urllib.request.Request

----------
nosy: +Mariatta
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun Aug 26 17:06:22 2018
From: report at bugs.python.org (Alexey Izbyshev)
Date: Sun, 26 Aug 2018 21:06:22 +0000
Subject: [docs] [issue34512] Document platform-specific strftime() behavior
 for non-ASCII format strings
Message-ID: <1535317582.77.0.56676864532.issue34512@psf.upfronthosting.co.za>


New submission from Alexey Izbyshev <izbyshev at ispras.ru>:

If a format string contains code points outside of ASCII range, time.strftime() can behave in four different ways depending on the platform, the current locale and the code points:

* raise a UnicodeEncodeError
* return an empty string
* for surrogates in \uDC80-\uDCFF range, replace them with different code points in the output (potentially mangling nearby parts of the output as well)
* round-trip them correctly

Some examples:

* Linux (glibc 2.27):
Python 3.6.4 (default, Jan 03 2018, 13:52:55) [GCC] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import time, locale
>>> locale.getlocale()
('en_US', 'UTF-8')
>>> time.strftime('\x80')
'\x80'
>>> time.strftime('\u044f')
'?' # '\u044f'
>>> time.strftime('\ud800')
'\ud800'
>>> time.strftime('\udcff')
'\udcff'
>>> locale.setlocale(locale.LC_CTYPE, 'C')
'C'
>>> time.strftime('\x80')
'\x80'
>>> time.strftime('\u044f')
'?' # '\u044f'
>>> time.strftime('\ud800')
'\ud800'
>>> time.strftime('\udcff')
'\udcff'

* macOS 10.13.6 and FreeBSD 11.1:
Python 3.7.0 (default, Jul 23 2018, 20:22:55)
[Clang 9.1.0 (clang-902.0.39.2)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import time, locale
>>> locale.getlocale()
('en_US', 'UTF-8')
>>> time.strftime('\x80')
'\x80'
>>> time.strftime('\u044f')
'?' # '\u044f'
>>> time.strftime('\ud800')
''
>>> time.strftime('\udcff')
''
>>> locale.setlocale(locale.LC_CTYPE, 'C')
'C'
>>> time.strftime('\x80')
'\x80'
>>> time.strftime('\u044f')
''
>>> time.strftime('\ud800')
''
>>> time.strftime('\udcff')
''

* Windows 8.1:
Python 3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)] on win32
>>> import time, locale
>>> locale.getlocale()
(None, None)
>>> time.strftime('\x80')
'\x80'
>>> time.strftime('\u044f')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeEncodeError: 'locale' codec can't encode character '\u044f' in position 0: encoding error
>>> time.strftime('\ud800')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeEncodeError: 'locale' codec can't encode character '\ud800' in position 0: encoding error
>>> time.strftime('\udcff')
'y' # '\xff'
>>> locale.setlocale(locale.LC_CTYPE, '')
'Russian_Russia.1251'
>>> time.strftime('\x80')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeEncodeError: 'locale' codec can't encode character '\x80' in position 0: encoding error
>>> time.strftime('\u044f')
'?' # '\u044f'
>>> time.strftime('\ud800')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
UnicodeEncodeError: 'locale' codec can't encode character '\ud800' in position 0: encoding error
>>> time.strftime('\udcff')
'?' # '\u044f'

The reasons of such differences are the following:
* Reliance on either wcsftime() or strftime() from the C library depending on the platform.
* For strftime(), the input is encoded into the charset of the current locale with 'surrogateescape' error handler, and the output is decoded back in the same way.
* Different handling of code points which are unrepresentable in the charset of the current locale by glibc and macOS/FreeBSD.

I suggest to at least document that the format string, despite being an 'str', requires special care if it contains non-ASCII code points.

The 'datetime' module docs warn about the locale-dependent output, but only with regard to particular format specifiers [1].

I'll submit a draft PR. Suggestions are welcome.

[1] https://docs.python.org/3.7/library/datetime.html#strftime-and-strptime-behavior

----------
assignee: docs at python
components: Documentation
messages: 324136
nosy: belopolsky, docs at python, izbyshev, p-ganssle, taleinat
priority: normal
severity: normal
status: open
title: Document platform-specific strftime() behavior for non-ASCII format strings
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Aug 26 17:09:52 2018
From: report at bugs.python.org (Alexey Izbyshev)
Date: Sun, 26 Aug 2018 21:09:52 +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: <1535317792.68.0.902498594338.issue34512@psf.upfronthosting.co.za>


Change by Alexey Izbyshev <izbyshev at ispras.ru>:


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

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

From report at bugs.python.org  Mon Aug 27 00:18:01 2018
From: report at bugs.python.org (Sanyam Khurana)
Date: Mon, 27 Aug 2018 04:18:01 +0000
Subject: [docs] [issue34319] Clarify pathlib.Path("filepath").read_text()
In-Reply-To: <1533210753.86.0.56676864532.issue34319@psf.upfronthosting.co.za>
Message-ID: <1535343481.45.0.56676864532.issue34319@psf.upfronthosting.co.za>


Sanyam Khurana <sanyam.khurana01 at gmail.com> added the comment:

Marking this bug as fixed via https://github.com/python/cpython/pull/8645

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

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

From report at bugs.python.org  Mon Aug 27 04:28:33 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 27 Aug 2018 08:28:33 +0000
Subject: [docs] [issue34487] enum _sunder_ names mix metaclass and enum
 class attributes
In-Reply-To: <1535121871.11.0.56676864532.issue34487@psf.upfronthosting.co.za>
Message-ID: <1535358513.56.0.902498594338.issue34487@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Aug 27 04:39:46 2018
From: report at bugs.python.org (harobed)
Date: Mon, 27 Aug 2018 08:39:46 +0000
Subject: [docs] [issue34511] I suggest to add documentation about "method"
 parameter of urllib.request.Request class
In-Reply-To: <1535316589.49.0.56676864532.issue34511@psf.upfronthosting.co.za>
Message-ID: <1535359186.59.0.56676864532.issue34511@psf.upfronthosting.co.za>


harobed <stephane at harobed.org> added the comment:

? Mariatta Wijaya

Thanks.

Sorry for my bad issue.

----------

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

From report at bugs.python.org  Mon Aug 27 04:44:48 2018
From: report at bugs.python.org (=?utf-8?b?SHJ2b2plIE5pa8WhacSH?=)
Date: Mon, 27 Aug 2018 08:44:48 +0000
Subject: [docs] [issue34518] Documentation for coroutine objects
Message-ID: <1535359488.51.0.56676864532.issue34518@psf.upfronthosting.co.za>


New submission from Hrvoje Nik?i? <hniksic at gmail.com>:

Coroutine objects have public methods such as send, close, and throw, which do not appear to be documented. For example, at https://stackoverflow.com/q/51975658/1600898 a StackOverflow user asks how to abort an already created (but not submitted) coroutine without a RuntimeWarning, with the answer being to use the close() method. The user asked where does one find the close method.

Currently methods only appear to be documented in PEP 492, referring to generator documentation for details. The glossary entry for coroutine (object) links to PEP 492 and to the async def statement. Various places in the documentation, e.g. the index, link to https://docs.python.org/3/library/asyncio-task.html#coroutine but that page is mostly concerned with the usage of coroutines within asyncio, where the methods on individual coroutine objects should not be used.

I would expect to find documentation on coroutine objects under built-in types, https://docs.python.org/3/library/stdtypes.html .

In comparison, generator-iterator methods are documented in the language reference:

https://docs.python.org/3/reference/expressions.html#generator-iterator-methods

----------
assignee: docs at python
components: Documentation
messages: 324157
nosy: docs at python, hniksic
priority: normal
severity: normal
status: open
title: Documentation for coroutine objects
versions: Python 3.7

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

From report at bugs.python.org  Mon Aug 27 06:39:40 2018
From: report at bugs.python.org (INADA Naoki)
Date: Mon, 27 Aug 2018 10:39:40 +0000
Subject: [docs] [issue34487] enum _sunder_ names mix metaclass and enum
 class attributes
In-Reply-To: <1535121871.11.0.56676864532.issue34487@psf.upfronthosting.co.za>
Message-ID: <1535366380.35.0.56676864532.issue34487@psf.upfronthosting.co.za>


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

Is it really need to be documented?
How is it important when using enum?

If there are no problem, I prefer keeping it implementation detail and don't make document fatter.

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

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

From report at bugs.python.org  Mon Aug 27 06:45:30 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Mon, 27 Aug 2018 10:45:30 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1535366730.01.0.56676864532.issue34434@psf.upfronthosting.co.za>


Xiang Zhang <angwerzx at 126.com> added the comment:


New changeset 3fe89dac42809a7741d50ebf595be98833b79b97 by Xiang Zhang (Louis Sautier) in branch 'master':
bpo-34434: Update doc for bool(), float() and int() arguments (GH-8834)
https://github.com/python/cpython/commit/3fe89dac42809a7741d50ebf595be98833b79b97


----------
nosy: +xiang.zhang

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

From report at bugs.python.org  Mon Aug 27 06:45:36 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 27 Aug 2018 10:45:36 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1535366736.79.0.902498594338.issue34434@psf.upfronthosting.co.za>


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


----------
pull_requests: +8429

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

From report at bugs.python.org  Mon Aug 27 06:59:00 2018
From: report at bugs.python.org (miss-islington)
Date: Mon, 27 Aug 2018 10:59:00 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1535367540.49.0.56676864532.issue34434@psf.upfronthosting.co.za>


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


New changeset fa3fd4cb181120007aefc408366c0cef6fb62f9d by Miss Islington (bot) in branch '3.7':
bpo-34434: Update doc for bool(), float() and int() arguments (GH-8834)
https://github.com/python/cpython/commit/fa3fd4cb181120007aefc408366c0cef6fb62f9d


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

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

From report at bugs.python.org  Mon Aug 27 07:00:42 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Mon, 27 Aug 2018 11:00:42 +0000
Subject: [docs] [issue34434] Removal of kwargs for built-in types not
 covered with "changed in Python" note in documentation
In-Reply-To: <1534685830.81.0.56676864532.issue34434@psf.upfronthosting.co.za>
Message-ID: <1535367642.22.0.902498594338.issue34434@psf.upfronthosting.co.za>


Change by Xiang Zhang <angwerzx at 126.com>:


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

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

From report at bugs.python.org  Mon Aug 27 08:58:06 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 27 Aug 2018 12:58:06 +0000
Subject: [docs] [issue34518] Documentation for coroutine objects
In-Reply-To: <1535359488.51.0.56676864532.issue34518@psf.upfronthosting.co.za>
Message-ID: <1535374686.45.0.902498594338.issue34518@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Aug 27 09:06:53 2018
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 27 Aug 2018 13:06:53 +0000
Subject: [docs] [issue34518] Documentation for coroutine objects
In-Reply-To: <1535359488.51.0.56676864532.issue34518@psf.upfronthosting.co.za>
Message-ID: <1535375213.84.0.56676864532.issue34518@psf.upfronthosting.co.za>


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

Is this what you are referring to that has docs for send, close and throw in coroutine objects ? 
Coroutine object docs : https://docs.python.org/3/reference/datamodel.html#coroutine-objects

If the above is the one then I think we can improve on the visibility by linking it from other pages since it doesn't show up with Google for 'coroutine close'. I had to use Docs folder in source code and sphinx search in docs.python.org with 'coroutine close' to get there.

Thanks

----------

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

From report at bugs.python.org  Mon Aug 27 09:22:24 2018
From: report at bugs.python.org (=?utf-8?b?SHJ2b2plIE5pa8WhacSH?=)
Date: Mon, 27 Aug 2018 13:22:24 +0000
Subject: [docs] [issue34518] Documentation for coroutine objects
In-Reply-To: <1535359488.51.0.56676864532.issue34518@psf.upfronthosting.co.za>
Message-ID: <1535376144.86.0.56676864532.issue34518@psf.upfronthosting.co.za>


Hrvoje Nik?i? <hniksic at gmail.com> added the comment:

That's exactly it, thanks! I have no idea how I missed it, despite looking (I thought) carefully.

But yes, they should be linked from https://docs.python.org/3/library/stdtypes.html . Just as currently there is https://docs.python.org/3/library/stdtypes.html#generator-types that links to https://docs.python.org/3/reference/expressions.html#yieldexpr , there could be a #coroutine-types that links to https://docs.python.org/3/reference/datamodel.html#coroutine-objects

Another place to link is https://docs.python.org/3/glossary.html#term-coroutine - it currently does link to the reference, but only to the "async def" syntax.

Since https://docs.python.org/3/reference/compound_stmts.html#async-def is linked from many places, it might make sense to mention that *calling* a coroutine immediately returns a coroutine object, with a link to https://docs.python.org/3/reference/datamodel.html#coroutine-objects

----------

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

From report at bugs.python.org  Mon Aug 27 09:32:34 2018
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 27 Aug 2018 13:32:34 +0000
Subject: [docs] [issue34502] Docs of sys.exit() mention utf8_mode for an
 unclear reason
In-Reply-To: <1535219668.13.0.56676864532.issue34502@psf.upfronthosting.co.za>
Message-ID: <1535376754.9.0.56676864532.issue34502@psf.upfronthosting.co.za>


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

Yes, it's a note for sys.flags. Can you please add it back to sys.flags?

Sorry, I added the note at the wrong place.

----------

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

From report at bugs.python.org  Mon Aug 27 09:32:45 2018
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 27 Aug 2018 13:32:45 +0000
Subject: [docs] [issue34502] Docs of sys.exit() mention utf8_mode for an
 unclear reason
In-Reply-To: <1535219668.13.0.56676864532.issue34502@psf.upfronthosting.co.za>
Message-ID: <1535376765.02.0.902498594338.issue34502@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Aug 27 10:51:31 2018
From: report at bugs.python.org (Alexey Izbyshev)
Date: Mon, 27 Aug 2018 14:51:31 +0000
Subject: [docs] [issue34502] Docs of sys.exit() mention utf8_mode for an
 unclear reason
In-Reply-To: <1535219668.13.0.56676864532.issue34502@psf.upfronthosting.co.za>
Message-ID: <1535381491.39.0.56676864532.issue34502@psf.upfronthosting.co.za>


Alexey Izbyshev <izbyshev at ispras.ru> added the comment:

Victor, but sys.flags docs *do* contain the note[1]:

Changed in version 3.7: Added dev_mode attribute for the new -X dev flag and utf8_mode attribute for the new -X utf8 flag.

I've tried to express that in msg324086, but obviously failed.

[1] https://docs.python.org/3/library/sys.html#sys.flags

----------

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

From report at bugs.python.org  Mon Aug 27 10:55:36 2018
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 27 Aug 2018 14:55:36 +0000
Subject: [docs] [issue34502] Docs of sys.exit() mention utf8_mode for an
 unclear reason
In-Reply-To: <1535219668.13.0.56676864532.issue34502@psf.upfronthosting.co.za>
Message-ID: <1535381736.38.0.56676864532.issue34502@psf.upfronthosting.co.za>


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

Ah ok, in this case, everything is fine :-)

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

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

From report at bugs.python.org  Mon Aug 27 18:27:19 2018
From: report at bugs.python.org (Ethan Furman)
Date: Mon, 27 Aug 2018 22:27:19 +0000
Subject: [docs] [issue34487] enum _sunder_ names mix metaclass and enum
 class attributes
In-Reply-To: <1535121871.11.0.56676864532.issue34487@psf.upfronthosting.co.za>
Message-ID: <1535408839.79.0.56676864532.issue34487@psf.upfronthosting.co.za>


Ethan Furman <ethan at stoneleaf.us> added the comment:

All those attributes live in the Enum class.  If you use a non-existent attribute, such as _name, then the metaclass will be called to check if that name is actually an Enum member.

----------
assignee: docs at python -> ethan.furman
nosy: +ethan.furman

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

From report at bugs.python.org  Mon Aug 27 20:35:58 2018
From: report at bugs.python.org (Richard Evans)
Date: Tue, 28 Aug 2018 00:35:58 +0000
Subject: [docs] [issue34524] Format conversion documentation example don't
 match comment
Message-ID: <1535416558.65.0.56676864532.issue34524@psf.upfronthosting.co.za>


New submission from Richard Evans <rarevans at hotmail.com>:

When reading the documentation for string formats I found that the conversion examples had comments that didn't match the example.

----------
assignee: docs at python
components: Documentation
messages: 324207
nosy: Richard Evans, docs at python
priority: normal
severity: normal
status: open
title: Format conversion documentation example don't match comment
versions: Python 3.8

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

From report at bugs.python.org  Mon Aug 27 20:37:31 2018
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 28 Aug 2018 00:37:31 +0000
Subject: [docs] [issue34524] Format conversion documentation example don't
 match comment
In-Reply-To: <1535416558.65.0.56676864532.issue34524@psf.upfronthosting.co.za>
Message-ID: <1535416650.98.0.56676864532.issue34524@psf.upfronthosting.co.za>


Eric V. Smith <eric at trueblade.com> added the comment:

Can you be more specific?

----------
nosy: +eric.smith

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

From report at bugs.python.org  Mon Aug 27 20:44:53 2018
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 28 Aug 2018 00:44:53 +0000
Subject: [docs] [issue34524] Format conversion documentation example don't
 match comment
In-Reply-To: <1535416558.65.0.56676864532.issue34524@psf.upfronthosting.co.za>
Message-ID: <1535417093.46.0.902498594338.issue34524@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Aug 27 21:09:10 2018
From: report at bugs.python.org (Richard Evans)
Date: Tue, 28 Aug 2018 01:09:10 +0000
Subject: [docs] [issue34524] Format conversion documentation example don't
 match comment
In-Reply-To: <1535416558.65.0.56676864532.issue34524@psf.upfronthosting.co.za>
Message-ID: <1535418550.17.0.902498594338.issue34524@psf.upfronthosting.co.za>


Change by Richard Evans <rarevans at hotmail.com>:


----------
resolution:  -> not a bug
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Aug 27 22:10:42 2018
From: report at bugs.python.org (Sebastian Rittau)
Date: Tue, 28 Aug 2018 02:10:42 +0000
Subject: [docs] [issue34525] smtplib's authobject return value wrongly
 documented
Message-ID: <1535422242.76.0.56676864532.issue34525@psf.upfronthosting.co.za>


New submission from Sebastian Rittau <srittau at rittau.biz>:

smtplib's authobject() callback is supposed to return bytes, according to both the documentation at https://docs.python.org/3/library/smtplib.html as well as the docstring of SMTP.auth(). This does neither match the implementation of auth(), which immediately calls encode() on the return value, nor that of the auth_cram_md5() et al, which return str.

----------
assignee: docs at python
components: Documentation
messages: 324209
nosy: docs at python, srittau
priority: normal
severity: normal
status: open
title: smtplib's authobject return value wrongly documented
versions: Python 3.7

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

From report at bugs.python.org  Mon Aug 27 22:15:52 2018
From: report at bugs.python.org (Sebastian Rittau)
Date: Tue, 28 Aug 2018 02:15:52 +0000
Subject: [docs] [issue34525] smtplib's authobject return value wrongly
 documented
In-Reply-To: <1535422242.76.0.56676864532.issue34525@psf.upfronthosting.co.za>
Message-ID: <1535422552.65.0.902498594338.issue34525@psf.upfronthosting.co.za>


Change by Sebastian Rittau <srittau at rittau.biz>:


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

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

From report at bugs.python.org  Tue Aug 28 04:42:29 2018
From: report at bugs.python.org (Antony Lee)
Date: Tue, 28 Aug 2018 08:42:29 +0000
Subject: [docs] [issue34526] Path.relative_to() taking multiple arguments
 could be better documented
Message-ID: <1535445749.23.0.56676864532.issue34526@psf.upfronthosting.co.za>


New submission from Antony Lee <anntzer.lee at gmail.com>:

Currently, the docs for Path.relative_to read

    PurePath.relative_to(*other)
    Compute a version of this path relative to the path represented by other. If it?s impossible, ValueError is raised: (examples follow)

It's a bit confusing why other is a star-args, especially as no example actually passes more than one argument to relative_to.

The docstring is a tiny bit clearer:

    Return the relative path to another path identified by the passed
    arguments.  If the operation is not possible (because this is not
    a subpath of the other path), raise ValueError.

Effectively, a Path is constructed from all *other args and used as base for the computation of the relative path.  It looks a bit like a misfeature to me, but at least it could be better documented (e.g. by adding `Path("/tmp/foo/bar").relative_to("/tmp", "foo") == Path("bar")` as example in the docs).

----------
assignee: docs at python
components: Documentation
messages: 324224
nosy: Antony.Lee, docs at python
priority: normal
severity: normal
status: open
title: Path.relative_to() taking multiple arguments could be better documented
versions: Python 3.7

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

From report at bugs.python.org  Tue Aug 28 11:05:27 2018
From: report at bugs.python.org (Mitch Gann)
Date: Tue, 28 Aug 2018 15:05:27 +0000
Subject: [docs] [issue24632] Improve documentation about __main__.py
In-Reply-To: <1436856841.67.0.538500952598.issue24632@psf.upfronthosting.co.za>
Message-ID: <1535468727.29.0.56676864532.issue24632@psf.upfronthosting.co.za>


Mitch Gann <mgann85 at gmail.com> added the comment:

Can someone please update the Docs on this?  Its been over 3 years since the issue was raised and seems fairly straightforward to address.  Also considering its a fairly important feature of the language which deals with the entry point for packages/modules to be executed, I know many Engineers/Developers using and learning the language would benefit from official documentation on this aspect.

----------
nosy: +MGann85

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

From report at bugs.python.org  Tue Aug 28 11:31:27 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 28 Aug 2018 15:31:27 +0000
Subject: [docs] [issue34531] doc Move comment about list sorting behavour
 outside impl-detail directive
Message-ID: <1535470287.16.0.56676864532.issue34531@psf.upfronthosting.co.za>


New submission from Andr?s Delfino <adelfino at gmail.com>:

As this text is phrased:

CPython implementation detail: While a list is being sorted, the effect of attempting to mutate, or even inspect, the list is undefined. The C implementation of Python makes the list appear empty for the duration, and raises ValueError if it can detect that the list has been mutated during a sort.

I take it that the first sentence is a general comment for all implementations, as the second sentence does define a specific behavior in CPython, so it's not undefined there.

I propose taking the first sentence out of the impl-detail directive.

----------
assignee: docs at python
components: Documentation
messages: 324259
nosy: adelfino, docs at python
priority: normal
severity: normal
status: open
title: doc Move comment about list sorting behavour outside impl-detail directive
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue Aug 28 11:33:39 2018
From: report at bugs.python.org (=?utf-8?q?Andr=C3=A9s_Delfino?=)
Date: Tue, 28 Aug 2018 15:33:39 +0000
Subject: [docs] [issue34531] doc Move comment about list sorting behavour
 outside impl-detail directive
In-Reply-To: <1535470287.16.0.56676864532.issue34531@psf.upfronthosting.co.za>
Message-ID: <1535470419.95.0.902498594338.issue34531@psf.upfronthosting.co.za>


Change by Andr?s Delfino <adelfino at gmail.com>:


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

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

From report at bugs.python.org  Tue Aug 28 14:12:08 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 28 Aug 2018 18:12:08 +0000
Subject: [docs] [issue34531] doc Move comment about list sorting behavour
 outside impl-detail directive
In-Reply-To: <1535470287.16.0.56676864532.issue34531@psf.upfronthosting.co.za>
Message-ID: <1535479928.54.0.56676864532.issue34531@psf.upfronthosting.co.za>


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

The sentence should be left as-is.  It is there to make the following two sentences more intelligible.

The docs otherwise make no promises about other implementations and this is as it should be.

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

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

From report at bugs.python.org  Tue Aug 28 14:25:07 2018
From: report at bugs.python.org (Elliot Edmunds)
Date: Tue, 28 Aug 2018 18:25:07 +0000
Subject: [docs] [issue25433] whitespace in strip()/lstrip()/rstrip()
In-Reply-To: <1445170536.34.0.94220475409.issue25433@psf.upfronthosting.co.za>
Message-ID: <1535480707.66.0.56676864532.issue25433@psf.upfronthosting.co.za>


Elliot Edmunds <edmundselliot at gmail.com> added the comment:

Not sure how helpful it would be to have the re.sub expressions for lstrip and rstrip, but I think it would look like:

l_stripped = re.sub(r'^\s*', '', foo)
r_stripped = re.sub(r'\s*$', '', foo)

----------
nosy: +Elliot Edmunds
Added file: https://bugs.python.org/file47769/whitespace_regex.py

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

From report at bugs.python.org  Tue Aug 28 16:40:51 2018
From: report at bugs.python.org (Nathaniel Manista)
Date: Tue, 28 Aug 2018 20:40:51 +0000
Subject: [docs] [issue34538] Remove encouragement to author a base class for
 all Exception subclasses in a module
Message-ID: <1535488851.13.0.56676864532.issue34538@psf.upfronthosting.co.za>


New submission from Nathaniel Manista <nathaniel at google.com>:

https://docs.python.org/3.8/tutorial/errors.html (and all other versions of that page back at least as far as 2.7) currently contain the guidance "When creating a module that can raise several distinct errors, a common practice is to create a base class for exceptions defined by that module, and subclass that to create specific exception classes for different error conditions: <code example>".

It may have seemed like a good idea at the time, but we now know from years of experience that this is an experiment that didn't pan out and we can consider this guidance a Now-Contraindicated Best Practice Of Yesteryear?.

Modules define subclasses of Exception for lots of reasons. Some of those subclasses have no relation to one another except that they are subclasses of Exception. Some of those subclasses define Exception instances that are never raised by code in the module, but that are expected to be raised by code passed to and called by the module.

Yes, there are times when a common base class may be appropriate - such as when an inheritance hierarchy and polymorphism that satisfy the Liskov Substitution Principle make sense for the Exception subclasses, and when the base class itself is used (such as when the base class is an item in the Raises: section of a function's doc string). But these cases aren't so common as to justify the advice being offered generally about all Exception subclass definitions.

Exception subclasses are just classes. Advising that authors may wish to define a common base class for all Exception subclasses in a module is like advising authors that they may wish to define a common base class for all object subclasses in a module - it's very, very, very occasionally a good idea in the particular circumstances of a particular module's implementation, but very generally not.

----------
assignee: docs at python
components: Documentation
messages: 324286
nosy: Nathaniel Manista, docs at python
priority: normal
severity: normal
status: open
title: Remove encouragement to author a base class for all Exception subclasses in a module
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/issue34538>
_______________________________________

From report at bugs.python.org  Wed Aug 29 03:09:23 2018
From: report at bugs.python.org (INADA Naoki)
Date: Wed, 29 Aug 2018 07:09:23 +0000
Subject: [docs] [issue34538] Remove encouragement to author a base class for
 all Exception subclasses in a module
In-Reply-To: <1535488851.13.0.56676864532.issue34538@psf.upfronthosting.co.za>
Message-ID: <1535526563.03.0.56676864532.issue34538@psf.upfronthosting.co.za>


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

I agree with you.

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

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

From report at bugs.python.org  Wed Aug 29 05:38:44 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 29 Aug 2018 09:38:44 +0000
Subject: [docs] [issue34538] Remove encouragement to author a base class for
 all Exception subclasses in a module
In-Reply-To: <1535488851.13.0.56676864532.issue34538@psf.upfronthosting.co.za>
Message-ID: <1535535524.73.0.56676864532.issue34538@psf.upfronthosting.co.za>


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

I think the advice should stay as-is.  In my experience as a teacher, the possibility doesn't usually occur to people without it having been suggested.  Also, it mirrors practices in the standard library (decimal.DecimalException and sqlite3.DatabaseError).  For users, it provides a way to catch possible errors that are specific to a particular module.

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

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

From report at bugs.python.org  Wed Aug 29 06:20:13 2018
From: report at bugs.python.org (INADA Naoki)
Date: Wed, 29 Aug 2018 10:20:13 +0000
Subject: [docs] [issue34538] Remove encouragement to author a base class for
 all Exception subclasses in a module
In-Reply-To: <1535488851.13.0.56676864532.issue34538@psf.upfronthosting.co.za>
Message-ID: <1535538013.09.0.56676864532.issue34538@psf.upfronthosting.co.za>


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

> Also, it mirrors practices in the standard library  (decimal.DecimalException and sqlite3.DatabaseError).

As Nathaniel said, "it's good idea in the particular circumstances of a particular module's implementation, but generally not."  (I removed "very" because it is too noisy)

For example, socket.error was migrated into OSError.
So not having base exception class for module is also "practices in the standard library".


> For users, it provides a way to catch possible errors that are specific to a particular module.

For tutorial readers, caching errors specific to particular cause should be suggested, instead of particular module.


"How/When custom base exception class is useful" is very high level topic.
It's too difficult for tutorial.

If tutorial reader start using base exception class without any real benefit, it will lead ugly code like this:

  try:
      # some code here
  except ValueError as e:
      raise CustomValueError(e.args)
  except TypeError as e:
      raise CustomTypeError(e.args)
  except ...

----------

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

From report at bugs.python.org  Wed Aug 29 15:17:05 2018
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 29 Aug 2018 19:17:05 +0000
Subject: [docs] [issue34538] Remove encouragement to author a base class for
 all Exception subclasses in a module
In-Reply-To: <1535488851.13.0.56676864532.issue34538@psf.upfronthosting.co.za>
Message-ID: <1535570225.42.0.56676864532.issue34538@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

I think the question is how often in real code to people want to catch all exceptions produced by a package or module but not any others. Perhaps it would be better to re-word the advice that when there are many related exceptions that it is suggested you have a base class for them?

----------
nosy: +brett.cannon

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

From report at bugs.python.org  Thu Aug 30 10:48:07 2018
From: report at bugs.python.org (Nick)
Date: Thu, 30 Aug 2018 14:48:07 +0000
Subject: [docs] [issue34549] unittest docs could use another header
Message-ID: <1535640487.61.0.56676864532.issue34549@psf.upfronthosting.co.za>


New submission from Nick <manifes7o at gmail.com>:

I find myself reaching for a list of the assert methods in the unittest library often. There are several methods but no clear way to link a URL via a header if you intend to bookmark or send it out.

I have been using the method above the section in the meantime

https://docs.python.org/3.7/library/unittest.html#unittest.TestCase.debug

Would be great to have an `Assert Methods` header or some other equivalent.

Thank you!

----------
assignee: docs at python
components: Documentation
messages: 324385
nosy: docs at python, napsterinblue
priority: normal
severity: normal
status: open
title: unittest docs could use another header
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Thu Aug 30 11:54:20 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 30 Aug 2018 15:54:20 +0000
Subject: [docs] [issue34538] Remove encouragement to author a base class for
 all Exception subclasses in a module
In-Reply-To: <1535488851.13.0.56676864532.issue34538@psf.upfronthosting.co.za>
Message-ID: <1535644459.93.0.56676864532.issue34538@psf.upfronthosting.co.za>


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

See https://bugs.python.org/issue443559 and "git log -p 13af42822cd".

One other example from real code:  requests.RequestException

----------
nosy: +fdrake

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

From report at bugs.python.org  Thu Aug 30 12:10:36 2018
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 30 Aug 2018 16:10:36 +0000
Subject: [docs] [issue34538] Remove encouragement to author a base class for
 all Exception subclasses in a module
In-Reply-To: <1535488851.13.0.56676864532.issue34538@psf.upfronthosting.co.za>
Message-ID: <1535645436.65.0.56676864532.issue34538@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

I'm not questioning if people have ever created a base exception for an entire package, I'm just asking how often it's actually used when the base exception didn't make sense outside of the rule-of-thumb Nathaniel is pointing out?

For instance, it could makes sense in requests' case to have a base exception to help facilitate catching network-related errors but let through e.g. TypeError. But does that extend to most packages such that users regularly write an 'except' clause catching that package's common base exception type? That's my question and I personally don't have an answer beyond reflecting on this and not really remembering a case where I have (I _can_ remember following this pattern simply because it's habit at this point for some unknown reason :) .

----------

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

From report at bugs.python.org  Thu Aug 30 12:34:36 2018
From: report at bugs.python.org (Ammar Askar)
Date: Thu, 30 Aug 2018 16:34:36 +0000
Subject: [docs] [issue34538] Remove encouragement to author a base class for
 all Exception subclasses in a module
In-Reply-To: <1535488851.13.0.56676864532.issue34538@psf.upfronthosting.co.za>
Message-ID: <1535646876.16.0.56676864532.issue34538@psf.upfronthosting.co.za>


Ammar Askar <ammar at ammaraskar.com> added the comment:

For some empirical data, I went through some popular packages that follow this pattern and searched for usage of their base exception classes:

Requests: https://github.com/search?q=except+requests.RequestException&type=Code

PyYaml: https://github.com/search?q=except+yaml.YAMLError&type=Code

Jinja2: https://github.com/search?q=%22except+jinja2.TemplateError%22&type=Code

https://github.com/search?q=%22except+jinja2.exceptions.TemplateError%22&type=Code

https://github.com/search?q=%22except+TemplateError%22&type=Code

----------
nosy: +ammar2

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

From report at bugs.python.org  Thu Aug 30 14:58:24 2018
From: report at bugs.python.org (Tercio Gaudencio Filho)
Date: Thu, 30 Aug 2018 18:58:24 +0000
Subject: [docs] [issue34226] cgi.parse_multipart() requires undocumented
 CONTENT-LENGTH in Python 3.7
In-Reply-To: <1532530540.72.0.56676864532.issue34226@psf.upfronthosting.co.za>
Message-ID: <1535655504.94.0.902498594338.issue34226@psf.upfronthosting.co.za>


Change by Tercio Gaudencio Filho <terciofilho at gmail.com>:


----------
nosy: +Tercio Gaudencio Filho

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

From report at bugs.python.org  Fri Aug 31 01:37:52 2018
From: report at bugs.python.org (Windson Yang)
Date: Fri, 31 Aug 2018 05:37:52 +0000
Subject: [docs] [issue34552] Clarify built-in types comparisons
Message-ID: <1535693872.67.0.56676864532.issue34552@psf.upfronthosting.co.za>


New submission from Windson Yang <wiwindson at gmail.com>:

In https://docs.python.org/3.5/library/stdtypes.html#comparisons 

"some types (for example, function objects) support only a degenerate notion of comparison where any two objects of that type are unequal."

We had some discussion at zulipchat already:

"more seriously: I think we can just delete that sentence. The next sentence makes clear that < and friends arne't always defined, and the sentence after that notes that == defaults to is if there's nothing better." - by Nathaniel J. Smith

IMO, I think we should also clarify the relationship between "==", "is" and "__eq__".

----------
assignee: docs at python
components: Documentation
messages: 324403
nosy: Windson Yang, docs at python, gvanrossum, njs, zach.ware
priority: normal
severity: normal
status: open
title: Clarify built-in types comparisons
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/issue34552>
_______________________________________

From report at bugs.python.org  Fri Aug 31 03:19:44 2018
From: report at bugs.python.org (INADA Naoki)
Date: Fri, 31 Aug 2018 07:19:44 +0000
Subject: [docs] [issue34538] Remove encouragement to author a base class for
 all Exception subclasses in a module
In-Reply-To: <1535488851.13.0.56676864532.issue34538@psf.upfronthosting.co.za>
Message-ID: <1535699984.05.0.56676864532.issue34538@psf.upfronthosting.co.za>


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

I didn't claim this pattern is not used anymore.
My point is "should we suggest this pattern for tutorial readers?"

* Is this pattern recommended blindly?  -- I think no.
* How / when this pattern is recommended?  -- When there is use case people want to catch the base exception.
* Should it be in tutorial?  -- I doubt it.  This topic requires some experience to understand.

----------

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

From report at bugs.python.org  Fri Aug 31 04:48:49 2018
From: report at bugs.python.org (INADA Naoki)
Date: Fri, 31 Aug 2018 08:48:49 +0000
Subject: [docs] [issue34538] Remove encouragement to author a base class for
 all Exception subclasses in a module
In-Reply-To: <1535488851.13.0.56676864532.issue34538@psf.upfronthosting.co.za>
Message-ID: <1535705329.02.0.56676864532.issue34538@psf.upfronthosting.co.za>


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

> https://github.com/search?q=%22except+TemplateError%22&type=Code

For example, I found flask_mako's TemplateException in this search result.

Strictly speaking, this is not base exception class.  It is wraps exception during template rendering.  But "why this class is useful?" is very similar to base exception class.

It provides better traceback for mako template.  They use this class for "particular reason", not because it's generally recommended practice.

And this "particular reason" shouldn't be in Python tutorial, clearly.

---

If we really need exception class hierarchy in tutorial, I think OSError is the best example.  When opening a file, `except OSError:` is much better than `except (PermissionError, FileNotFound, ...)`.  It's the most clear example when common base class for some distinct exceptions is useful.

----------

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

From dudik at cybermdx.com  Tue Aug  7 05:49:04 2018
From: dudik at cybermdx.com (Dudi Kovarski)
Date: Tue, 07 Aug 2018 09:49:04 -0000
Subject: [docs] BUG - pdb with asyncio
Message-ID: <CAHZMA2ASqSDNf-5fgyPdQW8Ktwsz6CstxgWP_ajZsD2pR3Rpyw@mail.gmail.com>

Hi,

I think I found a bug on python(pdb/asyncio) version 3.5.2.

The BUG shows up when debugging a code using pdb and the last row in the
method is:
await func(...)

What's happening is that on execute this last line ('await'), the pdb get
stuck and never back, BUT, if I'm adding one more row below in the same
method, everything is ok.

Thanks,
Dudi


-- 

*  Dudi Kovarski*

*  Senior Software Developer, CyberMDX*

*  Mobile: +972533332826*

[image:
/Users/JonR/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_991614229]
<http://www.cybermdx.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180807/81cc1fa0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6905 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180807/81cc1fa0/attachment-0001.png>

From polpuca at gmail.com  Thu Aug  9 06:15:39 2018
From: polpuca at gmail.com (Pol Pujols)
Date: Thu, 09 Aug 2018 10:15:39 -0000
Subject: [docs] from opc ua import client Security Policy not Supported
Message-ID: <CACWvN+_Cwgs3enxfzDZ49MZfH2AWmF0SHX=1TczTCsuiLLqcKA@mail.gmail.com>

Hello,
I am working with opc ua client package in python and i have seen that
Basic256Sha256 policy is not Supported.

client.set_security_string("Basic256Sha256,SignAndEncrypt,,certificate-example.der,private-key-example.pem")

I have looked for info but I haven't seen nothing related just Basic256 or
others

Is it a Bug or is something getting under development?
Is it going to last? since I am working on it and it would be really
usefull to have it avaliable.

Have a nice day,
Sincerely,
Pol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180809/7e0ac750/attachment-0001.html>

From ajay.putaka555 at gmail.com  Sun Aug 12 00:38:05 2018
From: ajay.putaka555 at gmail.com (Ajay Kumar)
Date: Sun, 12 Aug 2018 04:38:05 -0000
Subject: [docs] (no subject)
Message-ID: <CAKKb95a5z4SvXvpdW-jQj9k+JUEj6L-nynQbygh4wdJseA1ejA@mail.gmail.com>

can you please send Me any related pdf notes in python with new version
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180812/e15e3013/attachment-0001.html>

From doulidi at 126.com  Tue Aug 14 02:06:15 2018
From: doulidi at 126.com (=?UTF-8?B?56qm5Li95aij?=)
Date: Tue, 14 Aug 2018 06:06:15 -0000
Subject: [docs] (no subject)
Message-ID: <6126dfeb.5360.16536ed9bd6.Coremail.doulidi@126.com>

Dear who is in charge, 
sorry to bother you , I have fronted some problems when I use idle, I dont why erytime when I try to run the module, it always present with RESTART, erytime, which really hinders me from learning python, and i looked for answer on Internet, but there is no solution for me
so ,could you reply me as soon as possible,


Best regards
Leah












-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180814/8608c4a5/attachment-0001.html>

From kgrenczuk at gmail.com  Tue Aug 14 06:42:03 2018
From: kgrenczuk at gmail.com (jacob m)
Date: Tue, 14 Aug 2018 10:42:03 -0000
Subject: [docs] zpifile.py error - no crc 32 attribute
Message-ID: <CAD67o9Hx3pcEZi0tCm88OtbDEi0WwhNbphLtC0_brSa1=8tisQ@mail.gmail.com>

Hi guys,
I have a problem with zipfile and zlib module, and hope to get some help.

That's my error:
"    import zipfile
  File "/home/lib/python3.7/lib/python3.7/zipfile.py", line 19, in <module>
    crc32 = zlib.crc32
AttributeError: module 'zlib' has no attribute 'crc32' "

I have no idea what to do with that :/. I suppose that my zipfile.py is
probably 13.5 version. ANyway I don't see "AttributeError" exception on
github <https://github.com/python/cpython/blob/3.7/Lib/zipfile.py> (lines
17 - 22) and that's why I'm reporting a bug.
Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180814/4c321bdf/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: zipfile.py
Type: application/octet-stream
Size: 79734 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180814/4c321bdf/attachment-0001.obj>

From kgrenczuk at gmail.com  Tue Aug 14 06:47:13 2018
From: kgrenczuk at gmail.com (jacob m)
Date: Tue, 14 Aug 2018 10:47:13 -0000
Subject: [docs] zpifile.py error - no crc 32 attribute
In-Reply-To: <CAD67o9Hx3pcEZi0tCm88OtbDEi0WwhNbphLtC0_brSa1=8tisQ@mail.gmail.com>
References: <CAD67o9Hx3pcEZi0tCm88OtbDEi0WwhNbphLtC0_brSa1=8tisQ@mail.gmail.com>
Message-ID: <CAD67o9HDRwdOLcZxNY_4dp2Y+57bb6EVr43CrrVz40J_YgdbDA@mail.gmail.com>

Hi,
I'm sorry I saw now thats email contact for documentation bugs. Anyway I
will be happy to be redirected to someone who might help me :)
Regards

On 14 August 2018 at 12:42, jacob m <kgrenczuk at gmail.com> wrote:

> Hi guys,
> I have a problem with zipfile and zlib module, and hope to get some help.
>
> That's my error:
> "    import zipfile
>   File "/home/lib/python3.7/lib/python3.7/zipfile.py", line 19, in
> <module>
>     crc32 = zlib.crc32
> AttributeError: module 'zlib' has no attribute 'crc32' "
>
> I have no idea what to do with that :/. I suppose that my zipfile.py is
> probably 13.5 version. ANyway I don't see "AttributeError" exception on
> github <https://github.com/python/cpython/blob/3.7/Lib/zipfile.py> (lines
> 17 - 22) and that's why I'm reporting a bug.
> Regards
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180814/61af775a/attachment-0001.html>

From estellenlend at gmail.com  Thu Aug 16 13:09:50 2018
From: estellenlend at gmail.com (Estelle Nn)
Date: Thu, 16 Aug 2018 17:09:50 -0000
Subject: [docs] Bug sur Python
Message-ID: <CAOg5eWOyqmk7DPBx=Zx5odx84sxOihrhjWzdMJm_rkFoSi4RTA@mail.gmail.com>

Hello,

<I have a problem with my Python's programm. I can't write a command list
without a reinitialisation.

For instance :

>>> a = 12

...print("a is superior to 0.")

 File "<stdin>", line 2

    print("a is sup?rior to 0.")

IdentificationError: expected an indented block

>>>

Could you tell me where is the bug in the last version 3.0.7 ?

Thanks ^^
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180816/57260b82/attachment-0001.html>

From dougbmorris at yahoo.com  Thu Aug 16 23:51:43 2018
From: dougbmorris at yahoo.com (Douglas Morris)
Date: Fri, 17 Aug 2018 03:51:43 -0000
Subject: [docs] Misleading to disparage the -b option and focus on what it
 does NOT do.
References: <664129134.8861650.1534477870522.ref@mail.yahoo.com>
Message-ID: <664129134.8861650.1534477870522@mail.yahoo.com>

Hello, volunteer who is working harder than me. I spent something on the order of an hour, not sure, time flies when you have no clue, trying to compile and run python 3.6 bytecode without the source code. That is possible ONLY with the -b option. I first tried what I though were more obvious possibilities.

This will NOT work:# python -OO -m compileall <package># find <package> -name \*.py -type f -execdir rm '{}' \;# python <package>.main.main()ImportError or something that says can't find whatever module or method, don't remember exactly.
Turns out I need the 'legacy' bytecode, but it's not legacy. It's currently useful as the only way to get standalone bytecode to work. Who in his right mind would try an outdated option? Not me for too long, that's who.

Here is the Standard Library documentation for the -b option, under the compileall module:-b
Write the byte-code files to their legacy locations and names, which mayoverwrite byte-code files created by another version of Python. The defaultis to write files to their PEP 3147 locations and names, which allowsbyte-code files from multiple versions of Python to coexist.

The description is more the not -b option. The emphasis on 'legacy' trivializes the option into irrelevance. Legacy code is unused, unsupported code. The -b option DOES SOMETHING IMPORTANT:-b
Write the byte-code files to their historically original filename locations (and format?), which is the only way the python interpreter will run bytecode without the concomitant presence of its source code. Without the -b option, bytecode files are written to a __pycache__ subdirectory under a version-specific filename, which allows different versions of bytecode derived from the same source to coexist in storage. For details see PEP 3147.

I am not sure if the format of the standalone bytecode uses magic number + timestamp as the 'legacy' .pyc files did per the intro of the PEP, or if that has been dropped. If not dropped, then the 'legacy' qualifier is not even partially true in any technical sense, and will remain so until the bytecode protocol is scrapped. There is no reason to consider the old way depreciated rather than specialized. It is simply not the default way but earns its keep with its complementary pros and cons.

My use case: I want to use only bytecode for a Web service. Sure, I could be doing it wrong. This is a learning experience for me all the way.

Douglas Morris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180817/fb104969/attachment-0001.html>

From firlx010 at umn.edu  Sat Aug 25 11:55:17 2018
From: firlx010 at umn.edu (Tanner Firl)
Date: Sat, 25 Aug 2018 10:55:17 -0500
Subject: [docs] http.server silently exists
Message-ID: <CAOxqgXw4TTy68LG18CvzJqT51REK8fABbPD+jYGgN9oSV7r4eQ@mail.gmail.com>

Hello,

It appears the documentation for http.server is slightly out of date. When
I run the following example following the code from
https://docs.python.org/3/library/http.server.html:

The SimpleHTTPRequestHandler
<https://docs.python.org/3/library/http.server.html#http.server.SimpleHTTPRequestHandler>
 class can be used in the following manner in order to create a very basic
webserver serving files relative to the current directory:

import http.serverimport socketserver
PORT = 8000
Handler = http.server.SimpleHTTPRequestHandler
with socketserver.TCPServer(("", PORT), Handler) as httpd:
    print("serving at port", PORT)
    httpd.serve_forever()

http.server
<https://docs.python.org/3/library/http.server.html#module-http.server> can
also be invoked directly using the -m
<https://docs.python.org/3/using/cmdline.html#cmdoption-m> switch of the
interpreter with a port number argument. Similar to the previous example,
this serves files relative to the current directory:

python -m http.server 8000


It silently exits. Removing the with and not calling __enter__ or __exit__,
however, does appear to work fine.

Thanks!

Tanner
5079938498
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180825/c096e7c8/attachment-0001.html>

From niranjana26 at gmail.com  Sun Aug 26 03:44:27 2018
From: niranjana26 at gmail.com (Niranjana KM)
Date: Sun, 26 Aug 2018 13:14:27 +0530
Subject: [docs] PDF (A4 paper size) of Python documentation are US letter
 sized
Message-ID: <610210e9-f48a-f1ca-dbdd-389b1a0e504f@gmail.com>

Dear Python Doc,

 ??? The PDF (A4 paper size) of Python documentation given for download at

https://docs.python.org/3.6/archives/python-3.6.6-docs-pdf-a4.tar.bz2

are actually in US letter size. Please change the build settings.

-- 


Regards

Dr. Niranjana


From zoodss at yandex.ru  Sun Aug 26 13:00:58 2018
From: zoodss at yandex.ru (=?utf-8?B?0J3QuNC60LjRgtCwINCb0Y7RiNC90LXQvdC60L4=?=)
Date: Sun, 26 Aug 2018 20:00:58 +0300
Subject: [docs] Bug in the glossary documentation.
Message-ID: <10328101535302858@sas2-db6b18f976b3.qloud-c.yandex.net>

Term struct sequence, the word "ether" repeated 2 times in the row here: "elements can either be accessed either by index or as an attribute."

I suggest: "elements can ether be accessed by index or as an attribute."

Link - https://docs.python.org/3/glossary.html#term-struct-sequence

Sorry for poor English.

--?
Sincerely,
ZooDSS
ZooDSS at yandex.ru


From fan.shuxiang24 at gmail.com  Tue Aug 28 12:18:40 2018
From: fan.shuxiang24 at gmail.com (=?UTF-8?B?5qiK5pu457+U?=)
Date: Wed, 29 Aug 2018 01:18:40 +0900
Subject: [docs] Letters Garbled
Message-ID: <CAMgpji8pfrH1Aa0BBFX6KNZiCkrGyv8D0ekES4n0tQXB4N_T2w@mail.gmail.com>

Dear maintainer,

    I'm using python document to learn basic python grammars. But there are
always letters garbled in this document,wherever in win7 or win10. I hope
you can fix this problem. below I'll attach the picture of garbled letters.
   Thank you for your patience.


Sincerely,
Shon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180829/4415914f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2018-08-29.png
Type: image/png
Size: 228728 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180829/4415914f/attachment-0001.png>

From fan.shuxiang24 at gmail.com  Tue Aug 28 13:17:38 2018
From: fan.shuxiang24 at gmail.com (=?UTF-8?B?5qiK5pu457+U?=)
Date: Wed, 29 Aug 2018 02:17:38 +0900
Subject: [docs] Letters Garbled
In-Reply-To: <CAMgpji8pfrH1Aa0BBFX6KNZiCkrGyv8D0ekES4n0tQXB4N_T2w@mail.gmail.com>
References: <CAMgpji8pfrH1Aa0BBFX6KNZiCkrGyv8D0ekES4n0tQXB4N_T2w@mail.gmail.com>
Message-ID: <CAMgpji8+sKhbAZ-BkbPLWYkSK-Y4-voSjphvPpsh4XhPOLcGCA@mail.gmail.com>

Dear maintainers,

      I?ve solved this problem. I?m sorry for mailing to interrupt you.

Sincerely,
Shon

2018?8?29?(?) 1:18 ??? <fan.shuxiang24 at gmail.com>:

> Dear maintainer,
>
>     I'm using python document to learn basic python grammars. But there
> are always letters garbled in this document,wherever in win7 or win10. I
> hope you can fix this problem. below I'll attach the picture of garbled
> letters.
>    Thank you for your patience.
>
>
> Sincerely,
> Shon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180829/6aadaf23/attachment.html>