From report at bugs.python.org  Thu Mar  1 15:14:20 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 01 Mar 2018 20:14:20 +0000
Subject: [docs] [issue18855] Inconsistent README filenames
In-Reply-To: <1377616570.1.0.108273179071.issue18855@psf.upfronthosting.co.za>
Message-ID: <1519935260.78.0.714561066657.issue18855@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


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

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

From report at bugs.python.org  Thu Mar  1 16:02:58 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 01 Mar 2018 21:02:58 +0000
Subject: [docs] [issue30607] Extract documentation theme into a separate
 package
In-Reply-To: <1496981279.71.0.300273355047.issue30607@psf.upfronthosting.co.za>
Message-ID: <1519938178.39.0.467229070634.issue30607@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:


New changeset bf63e8d55fd2853df3bb99d66de7f428107aadb3 by Ned Deily (Jon Wayne Parrott) in branch 'master':
bpo-30607: Use external python-doc-theme (GH-2017)
https://github.com/python/cpython/commit/bf63e8d55fd2853df3bb99d66de7f428107aadb3


----------
nosy: +ned.deily

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

From report at bugs.python.org  Thu Mar  1 16:07:07 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 01 Mar 2018 21:07:07 +0000
Subject: [docs] [issue30607] Extract documentation theme into a separate
 package
In-Reply-To: <1496981279.71.0.300273355047.issue30607@psf.upfronthosting.co.za>
Message-ID: <1519938427.21.0.467229070634.issue30607@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

Thanks, Jon, and every one else who helped with and commented on the PR.

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

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

From report at bugs.python.org  Thu Mar  1 16:23:19 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 01 Mar 2018 21:23:19 +0000
Subject: [docs] [issue18855] Inconsistent README filenames
In-Reply-To: <1377616570.1.0.108273179071.issue18855@psf.upfronthosting.co.za>
Message-ID: <1519939399.7.0.467229070634.issue18855@psf.upfronthosting.co.za>


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

Thanks. I'm going to reject this and to keep the readme files as is.
The consequence of renaming files, now that we are on GitHub, is that GitHub doesn't retain the complete file history.
So while on GitHub, clicking the file's "History" will only show the history of the file after the rename.
In addition, locally you need to do `git log --follow` to see the complete history.
I find that to be an inconvenience.

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

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

From report at bugs.python.org  Thu Mar  1 16:42:19 2018
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 01 Mar 2018 21:42:19 +0000
Subject: [docs] [issue32971] Docs on unittest.TestCase.assertRaises() should
 clarify context manager details
In-Reply-To: <1519840682.18.0.467229070634.issue32971@psf.upfronthosting.co.za>
Message-ID: <1519940539.57.0.714561066657.issue32971@psf.upfronthosting.co.za>


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


----------
title: Docs on unittest.TestCase.assertRaises() should be improved -> Docs on unittest.TestCase.assertRaises() should clarify context manager details

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

From polisetp at amazon.com  Fri Mar  2 06:37:01 2018
From: polisetp at amazon.com (Polisetti, Phanindra Kumar)
Date: Fri, 2 Mar 2018 11:37:01 +0000
Subject: [docs] Document Download links doesn't seem to be working
Message-ID: <9DA3A564-0637-4A24-80C2-5E9C2BE503F7@amazon.com>

Hello there,

I am trying to download the Python documentation pdf and it I get a 404 error.

https://www.python.org/ftp/python/doc/3.5.5/python-3.5.5-docs-pdf-a4.zip


?404 Not Found
nginx
?

Could you please fix this

Regards,
Phanindra Polisetti
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180302/af6c0114/attachment-0001.html>

From report at bugs.python.org  Fri Mar  2 14:19:44 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 02 Mar 2018 19:19:44 +0000
Subject: [docs] [issue32963] Python 2.7 tutorial claims source code is UTF-8
 encoded
In-Reply-To: <1519722263.23.0.467229070634.issue32963@psf.upfronthosting.co.za>
Message-ID: <1520018384.82.0.467229070634.issue32963@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

If no one gets to this before the sprints at PyCon US I will take care of it, but anyone can feel free to submit a pull request to fix this.

----------
assignee: docs at python -> brett.cannon
keywords: +easy

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

From report at bugs.python.org  Fri Mar  2 14:39:22 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Fri, 02 Mar 2018 19:39:22 +0000
Subject: [docs] [issue32963] Python 2.7 tutorial claims source code is UTF-8
 encoded
In-Reply-To: <1519722263.23.0.467229070634.issue32963@psf.upfronthosting.co.za>
Message-ID: <1520019562.58.0.467229070634.issue32963@psf.upfronthosting.co.za>


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

I'm not intending to work on this, nothing until after PyCon :) Feel free to pick it up.

----------

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

From report at bugs.python.org  Fri Mar  2 16:30:38 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 02 Mar 2018 21:30:38 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520026238.85.0.714561066657.issue32758@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Mar  2 17:03:34 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 02 Mar 2018 22:03:34 +0000
Subject: [docs] [issue32963] Python 2.7 tutorial claims source code is UTF-8
 encoded
In-Reply-To: <1519722263.23.0.467229070634.issue32963@psf.upfronthosting.co.za>
Message-ID: <1520028214.41.0.714561066657.issue32963@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Mar  2 17:09:50 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 02 Mar 2018 22:09:50 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520028590.88.0.467229070634.issue32758@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

The PR adds the documentation warnings. Serhiy, can you double-check that I have the appropriate functions and the comment is acceptable?

----------

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

From report at bugs.python.org  Fri Mar  2 17:10:23 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 02 Mar 2018 22:10:23 +0000
Subject: [docs] [issue32963] Python 2.7 tutorial claims source code is UTF-8
 encoded
In-Reply-To: <1519722263.23.0.467229070634.issue32963@psf.upfronthosting.co.za>
Message-ID: <1520028623.76.0.467229070634.issue32963@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:


New changeset 20003f9162631c47b79202316036d13d74484e4c by Brett Cannon in branch '2.7':
bpo-32963: Fix the tutorial to state source has a default encoding of ASCII (GH-5961)
https://github.com/python/cpython/commit/20003f9162631c47b79202316036d13d74484e4c


----------

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

From report at bugs.python.org  Fri Mar  2 17:10:52 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 02 Mar 2018 22:10:52 +0000
Subject: [docs] [issue32963] Python 2.7 tutorial claims source code is UTF-8
 encoded
In-Reply-To: <1519722263.23.0.467229070634.issue32963@psf.upfronthosting.co.za>
Message-ID: <1520028652.5.0.467229070634.issue32963@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

Thanks for the bug report, Martijn!

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

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

From report at bugs.python.org  Fri Mar  2 20:09:54 2018
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 03 Mar 2018 01:09:54 +0000
Subject: [docs] [issue28124] Rework SSL module documentation
In-Reply-To: <1473762840.76.0.666078412099.issue28124@psf.upfronthosting.co.za>
Message-ID: <1520039394.47.0.714561066657.issue28124@psf.upfronthosting.co.za>


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


----------
pull_requests: +5731

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

From report at bugs.python.org  Sat Mar  3 06:53:46 2018
From: report at bugs.python.org (Martijn Pieters)
Date: Sat, 03 Mar 2018 11:53:46 +0000
Subject: [docs] [issue32963] Python 2.7 tutorial claims source code is UTF-8
 encoded
In-Reply-To: <1519722263.23.0.467229070634.issue32963@psf.upfronthosting.co.za>
Message-ID: <1520078026.7.0.467229070634.issue32963@psf.upfronthosting.co.za>


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

Thanks for the quick fix, sorry I didn't have a PR for this one!

----------

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

From report at bugs.python.org  Sat Mar  3 06:55:24 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 03 Mar 2018 11:55:24 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520078124.4.0.467229070634.issue32758@psf.upfronthosting.co.za>


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

Thank you Brett! The comment LGTM.

Is it worth to add warnings to other functions?

* compile(), exec() and eval(). They are crashed due to recursion in the AST optimizer. This is a regression of 3.7. compile(..., PyCF_ONLY_AST) is the same as ast.parse() and crashed in older versions.

* dbm.dumb.open(). It calls ast.literal_eval(). The dbm.dumb databases are considered slow but portable. Before issue22885 this function was even more vulnerable due to using eval(). Since changing it to ast.literal_eval() some developers could consider it safe, but this is not true.

* A number of functions in the inspect module which directly or indirectly call ast.parse() on the __text_signature__ attribute. The risk of this vulnerability is very low.

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

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

From report at bugs.python.org  Sat Mar  3 13:59:41 2018
From: report at bugs.python.org (Brett Cannon)
Date: Sat, 03 Mar 2018 18:59:41 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520103581.68.0.467229070634.issue32758@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

You're probably right and it's worth propagating the warning a bit wider.

----------
assignee: docs at python -> brett.cannon

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

From report at bugs.python.org  Sat Mar  3 14:00:27 2018
From: report at bugs.python.org (Brett Cannon)
Date: Sat, 03 Mar 2018 19:00:27 +0000
Subject: [docs] [issue32963] Python 2.7 tutorial claims source code is UTF-8
 encoded
In-Reply-To: <1519722263.23.0.467229070634.issue32963@psf.upfronthosting.co.za>
Message-ID: <1520103627.82.0.467229070634.issue32963@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

No need to apologize! We all only have so much free time.

----------

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

From report at bugs.python.org  Sun Mar  4 08:22:12 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 04 Mar 2018 13:22:12 +0000
Subject: [docs] [issue28955] Not matched behavior of numeric comparison with
 the documentation
In-Reply-To: <1481602171.57.0.675005739221.issue28955@psf.upfronthosting.co.za>
Message-ID: <1520169732.83.0.714561066657.issue28955@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


----------
keywords: +easy
stage:  -> needs patch
type: behavior -> enhancement
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Sun Mar  4 14:37:26 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 04 Mar 2018 19:37:26 +0000
Subject: [docs] [issue28626] Tutorial: rearrange discussion of output
 formatting to encourage f-strings
In-Reply-To: <1478452855.22.0.932657206329.issue28626@psf.upfronthosting.co.za>
Message-ID: <1520192246.07.0.467229070634.issue28626@psf.upfronthosting.co.za>


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

@akuchling

Would you be able to make a PR for this patch?  Thanks.

----------
nosy: +csabella
versions: +Python 3.8 -Python 3.6

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

From report at bugs.python.org  Sun Mar  4 17:06:32 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 04 Mar 2018 22:06:32 +0000
Subject: [docs] [issue30974] Update os.samefile docstring to match
 documentation
In-Reply-To: <1500538030.77.0.17785692497.issue30974@psf.upfronthosting.co.za>
Message-ID: <1520201192.92.0.714561066657.issue30974@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


----------
keywords: +easy
stage:  -> needs patch
versions: +Python 3.8 -Python 3.6

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

From report at bugs.python.org  Sun Mar  4 17:46:42 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 04 Mar 2018 22:46:42 +0000
Subject: [docs] [issue30147] Change in re.escape output is not documented in
 whatsnew
In-Reply-To: <1492972796.84.0.355071171235.issue30147@psf.upfronthosting.co.za>
Message-ID: <1520203602.87.0.714561066657.issue30147@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


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

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

From report at bugs.python.org  Sun Mar  4 18:06:59 2018
From: report at bugs.python.org (Ned Deily)
Date: Sun, 04 Mar 2018 23:06:59 +0000
Subject: [docs] [issue30147] Change in re.escape output is not documented in
 whatsnew
In-Reply-To: <1492972796.84.0.355071171235.issue30147@psf.upfronthosting.co.za>
Message-ID: <1520204819.74.0.467229070634.issue30147@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:


New changeset 18fd89246333bfa1b76c1623df689214f3ce2bf3 by Ned Deily (Cheryl Sabella) in branch 'master':
bpo-30147: Add re.escape changes to 3.7 What's New (GH-5978)
https://github.com/python/cpython/commit/18fd89246333bfa1b76c1623df689214f3ce2bf3


----------
nosy: +ned.deily

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

From report at bugs.python.org  Sun Mar  4 18:07:10 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 04 Mar 2018 23:07:10 +0000
Subject: [docs] [issue30147] Change in re.escape output is not documented in
 whatsnew
In-Reply-To: <1492972796.84.0.355071171235.issue30147@psf.upfronthosting.co.za>
Message-ID: <1520204830.43.0.714561066657.issue30147@psf.upfronthosting.co.za>


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


----------
pull_requests: +5745

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

From report at bugs.python.org  Sun Mar  4 18:22:35 2018
From: report at bugs.python.org (Ned Deily)
Date: Sun, 04 Mar 2018 23:22:35 +0000
Subject: [docs] [issue30147] Change in re.escape output is not documented in
 whatsnew
In-Reply-To: <1492972796.84.0.355071171235.issue30147@psf.upfronthosting.co.za>
Message-ID: <1520205755.06.0.467229070634.issue30147@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:


New changeset f92478d57a6b4014dcc0882d43b534fae1e7b929 by Ned Deily (Miss Islington (bot)) in branch '3.7':
[3.7] bpo-30147: Add re.escape changes to 3.7 What's New (GH-5978) (GH-5979)
https://github.com/python/cpython/commit/f92478d57a6b4014dcc0882d43b534fae1e7b929


----------

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

From report at bugs.python.org  Sun Mar  4 18:24:40 2018
From: report at bugs.python.org (Ned Deily)
Date: Sun, 04 Mar 2018 23:24:40 +0000
Subject: [docs] [issue30147] Change in re.escape output is not documented in
 3.7 whatsnew
In-Reply-To: <1492972796.84.0.355071171235.issue30147@psf.upfronthosting.co.za>
Message-ID: <1520205880.25.0.467229070634.issue30147@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

Thanks, @csabella, for the PR!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
title: Change in re.escape output is not documented in whatsnew -> Change in re.escape output is not documented in 3.7 whatsnew
versions: +Python 3.8

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

From report at bugs.python.org  Sun Mar  4 18:43:38 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 04 Mar 2018 23:43:38 +0000
Subject: [docs] [issue25197] Allow documentation switcher to change url to
 /3/ and /dev/
In-Reply-To: <1442780092.62.0.798906880968.issue25197@psf.upfronthosting.co.za>
Message-ID: <1520207018.83.0.467229070634.issue25197@psf.upfronthosting.co.za>


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

With the current dropdown for the documentation switcher (it has dev, prerelease, and stable options) and the addition of the language switcher, I believe this issue may be out of date.  Can it be closed?  Thanks!

----------
nosy: +csabella

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

From report at bugs.python.org  Mon Mar  5 03:55:45 2018
From: report at bugs.python.org (Anthony Flury)
Date: Mon, 05 Mar 2018 08:55:45 +0000
Subject: [docs] [issue28955] Not matched behavior of numeric comparison with
 the documentation
In-Reply-To: <1481602171.57.0.675005739221.issue28955@psf.upfronthosting.co.za>
Message-ID: <1520240145.13.0.714561066657.issue28955@psf.upfronthosting.co.za>


Change by Anthony Flury <anthony.flury at btinternet.com>:


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

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

From report at bugs.python.org  Mon Mar  5 05:11:32 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 05 Mar 2018 10:11:32 +0000
Subject: [docs] [issue32995] Add a glossary entry for context variables
Message-ID: <1520244692.22.0.467229070634.issue32995@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

I think the term context variable is worth adding into the glossary.

----------
assignee: docs at python
components: Documentation
messages: 313241
nosy: docs at python, serhiy.storchaka, yselivanov
priority: normal
severity: normal
status: open
title: Add a glossary entry for context variables
type: enhancement
versions: Python 3.7, Python 3.8

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

From aashiq.d at gmail.com  Fri Mar  2 17:10:14 2018
From: aashiq.d at gmail.com (Aashiq)
Date: Fri, 02 Mar 2018 22:10:14 +0000
Subject: [docs] datetime format bug
Message-ID: <CACokX6bdti7_qBSPM6KYkx2Gpex142EjjO+7QORQBDzOc3VBAw@mail.gmail.com>

import datetime
d1 = datetime.datetime(2018,2,26,10,2)
d2 = datetime.datetime(2018,2,26,10,4)
ss = "{:%m} {:%m}".format(d1,d2)
print(ss)

Expected: 02 04
Actual: 02 02
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180302/41dfff63/attachment.html>

From aashiq.d at gmail.com  Fri Mar  2 17:57:41 2018
From: aashiq.d at gmail.com (Aashiq)
Date: Fri, 02 Mar 2018 22:57:41 +0000
Subject: [docs] datetime format bug
In-Reply-To: <CACokX6bdti7_qBSPM6KYkx2Gpex142EjjO+7QORQBDzOc3VBAw@mail.gmail.com>
References: <CACokX6bdti7_qBSPM6KYkx2Gpex142EjjO+7QORQBDzOc3VBAw@mail.gmail.com>
Message-ID: <CACokX6a6Gmcc=6a2Myq3niu2_hKW_OBWRn+vxANj_XALj4mK+g@mail.gmail.com>

Ignore that, I screwed up my date formatting.. should be %M.

On Fri, Mar 2, 2018 at 4:15 PM Aashiq <aashiq.d at gmail.com> wrote:

> import datetime
> d1 = datetime.datetime(2018,2,26,10,2)
> d2 = datetime.datetime(2018,2,26,10,4)
> ss = "{:%m} {:%m}".format(d1,d2)
> print(ss)
>
> Expected: 02 04
> Actual: 02 02
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180302/385dd82d/attachment.html>

From karthikveluri19 at gmail.com  Mon Mar  5 06:42:08 2018
From: karthikveluri19 at gmail.com (Karthik Veluri)
Date: Mon, 5 Mar 2018 17:12:08 +0530
Subject: [docs] Bug found in count() method
Message-ID: <CAAWF65idTHCiNYrBK+2q2Dq8OyUyxwmVdUhZp0T3MbWZkJdEUw@mail.gmail.com>

The count method for string does not work when the string that is being
counted shares characters with strings that should also be counted.

--> Update the count menthod so that 'sasas'.count('sas') returns 2!

Please tell me if my interpretation is right. Thanks!


Karthik Veluri,
karthikveluri19 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180305/905f4c91/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python2.png
Type: image/png
Size: 13279 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180305/905f4c91/attachment-0001.png>

From report at bugs.python.org  Mon Mar  5 06:56:46 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 05 Mar 2018 11:56:46 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
Message-ID: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka <storchaka+cpython at gmail.com>:

The following PR fixes and improves formatting in the "What's New in Python 3.7" document, adds links to issues and authors names.

This is just one step. Somebody need to review NEWS entries and adds corresponding What's New entries if they are worth this, and later edit the wording of the final document.

----------
assignee: docs at python
components: Documentation
messages: 313243
nosy: docs at python, ned.deily, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Improve What's New in 3.7
type: enhancement
versions: Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Mar  5 06:58:52 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 05 Mar 2018 11:58:52 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1520251132.12.0.714561066657.issue32996@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Mar  5 07:06:01 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 05 Mar 2018 12:06:01 +0000
Subject: [docs] [issue28955] Not matched behavior of numeric comparison with
 the documentation
In-Reply-To: <1481602171.57.0.675005739221.issue28955@psf.upfronthosting.co.za>
Message-ID: <1520251561.25.0.714561066657.issue28955@psf.upfronthosting.co.za>


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


----------
nosy: +mark.dickinson

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

From report at bugs.python.org  Mon Mar  5 11:23:37 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Mon, 05 Mar 2018 16:23:37 +0000
Subject: [docs] [issue32969] Add more constants to zlib module
In-Reply-To: <1519808340.69.0.467229070634.issue32969@psf.upfronthosting.co.za>
Message-ID: <1520267017.03.0.714561066657.issue32969@psf.upfronthosting.co.za>


Change by Xiang Zhang <angwerzx at 126.com>:


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

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

From report at bugs.python.org  Mon Mar  5 17:36:31 2018
From: report at bugs.python.org (W. Trevor King)
Date: Mon, 05 Mar 2018 22:36:31 +0000
Subject: [docs] [issue33003] urllib: Document parse_http_list
Message-ID: <1520289391.9.0.467229070634.issue33003@psf.upfronthosting.co.za>


New submission from W. Trevor King <wking at tremily.us>:

Python has had a parse_http_list helper since urllib2 landed in 6d7e47b8ea (EXPERIMENTAL, 2000-01-20).  With Python3 it was moved into urllib.request, and the implementation hasn't changed since (at least as of 4c19b9573, 2018-03-05).  External projects depend on the currently undocumented function [1,2], so it would be nice to have some user-facing documentation for it.  If that sounds appealing, I'm happy to work up a pull request.

[1]: https://github.com/requests/requests/blob/v2.18.4/requests/compat.py#L42
[2]: https://github.com/requests/requests/blob/v2.18.4/requests/compat.py#L58

----------
assignee: docs at python
components: Documentation
messages: 313294
nosy: docs at python, labrat
priority: normal
severity: normal
status: open
title: urllib: Document parse_http_list
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/issue33003>
_______________________________________

From report at bugs.python.org  Mon Mar  5 20:36:31 2018
From: report at bugs.python.org (Pierre Thibault)
Date: Tue, 06 Mar 2018 01:36:31 +0000
Subject: [docs] [issue33006] docstring of filter function is incorrect
Message-ID: <1520300191.48.0.467229070634.issue33006@psf.upfronthosting.co.za>


New submission from Pierre Thibault <pierre.thibault1.dev at gmail.com>:

> help(filter)

Help on built-in function filter in module __builtin__:

filter(...)
    filter(function or None, sequence) -> list, tuple, or string

    Return those items of sequence for which function(item) is true.  If
    function is None, return the items that are true.  If sequence is a tuple
    or string, return the same type, else return a list.
(END)

The second argument can be an iterable. Suggestion: Replace the docstring with the definition found at https://docs.python.org/2/library/functions.html#filter.

----------
assignee: docs at python
components: Documentation
messages: 313302
nosy: Pierre Thibault, docs at python
priority: normal
severity: normal
status: open
title: docstring of filter function is incorrect
versions: Python 2.7

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

From report at bugs.python.org  Mon Mar  5 20:43:41 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Tue, 06 Mar 2018 01:43:41 +0000
Subject: [docs] [issue32969] Add more constants to zlib module
In-Reply-To: <1519808340.69.0.467229070634.issue32969@psf.upfronthosting.co.za>
Message-ID: <1520300621.69.0.714561066657.issue32969@psf.upfronthosting.co.za>


Change by Xiang Zhang <angwerzx at 126.com>:


----------
type: enhancement -> 
versions: +Python 3.6, Python 3.7

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

From report at bugs.python.org  Mon Mar  5 20:53:11 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 06 Mar 2018 01:53:11 +0000
Subject: [docs] [issue25197] Allow documentation switcher to change url to
 /3/ and /dev/
In-Reply-To: <1442780092.62.0.798906880968.issue25197@psf.upfronthosting.co.za>
Message-ID: <1520301191.28.0.467229070634.issue25197@psf.upfronthosting.co.za>


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

Yeah I believe this issue is out of date. Thanks.

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

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

From report at bugs.python.org  Tue Mar  6 10:13:59 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 06 Mar 2018 15:13:59 +0000
Subject: [docs] [issue20150] API change in string formatting with :s option
 should be documented in What's New.
In-Reply-To: <1389032161.42.0.577933973443.issue20150@psf.upfronthosting.co.za>
Message-ID: <1520349239.06.0.467229070634.issue20150@psf.upfronthosting.co.za>


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

I believe this has been added to the 3.4 What's New already:

object.__format__() no longer accepts non-empty format strings, it now raises a TypeError instead. Using a non-empty string has been deprecated since Python 3.2. This change has been made to prevent a situation where previously working (but incorrect) code would start failing if an object gained a __format__ method, which means that your code may now raise a TypeError if you are using an 's' format code with objects that do not have a __format__ method that handles it. See bpo-7994 for background

Closing as resolved.

----------
nosy: +csabella
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Mar  6 10:50:40 2018
From: report at bugs.python.org (David Beazley)
Date: Tue, 06 Mar 2018 15:50:40 +0000
Subject: [docs] [issue33014] Clarify doc string for str.isidentifier()
Message-ID: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>


New submission from David Beazley <dave at dabeaz.com>:

This is a minor nit, but the doc string for str.isidentifier() states:

    Use keyword.iskeyword() to test for reserved identifiers such as "def" and "class".

At first glance, I thought that it meant you'd do this (doesn't work):

    'def'.iskeyword()

As opposed to this:

    import keyword
    keyword.iskeyword('def')

Perhaps a clarification that "keyword" refers to the keyword module could be added.   Or better yet, just make 'iskeyword()` a string method ;-).

----------
assignee: docs at python
components: Documentation
messages: 313335
nosy: dabeaz, docs at python
priority: normal
severity: normal
status: open
title: Clarify doc string for str.isidentifier()
versions: Python 3.7

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

From report at bugs.python.org  Tue Mar  6 11:06:24 2018
From: report at bugs.python.org (Sanyam Khurana)
Date: Tue, 06 Mar 2018 16:06:24 +0000
Subject: [docs] [issue33014] Clarify doc string for str.isidentifier()
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520352383.98.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

Hey David,

I'm working on this issue. Will submit a PR in a while :)

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

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

From report at bugs.python.org  Tue Mar  6 20:04:34 2018
From: report at bugs.python.org (A.M. Kuchling)
Date: Wed, 07 Mar 2018 01:04:34 +0000
Subject: [docs] [issue8840] truncate() semantics changed in 3.1.2
In-Reply-To: <1275005546.82.0.0795236723796.issue8840@psf.upfronthosting.co.za>
Message-ID: <1520384674.75.0.714561066657.issue8840@psf.upfronthosting.co.za>


Change by A.M. Kuchling <amk at amk.ca>:


----------
keywords: +patch
pull_requests: +5776

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

From report at bugs.python.org  Wed Mar  7 00:05:39 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 07 Mar 2018 05:05:39 +0000
Subject: [docs] [issue32969] Add more constants to zlib module
In-Reply-To: <1519808340.69.0.467229070634.issue32969@psf.upfronthosting.co.za>
Message-ID: <1520399139.67.0.467229070634.issue32969@psf.upfronthosting.co.za>


Xiang Zhang <angwerzx at 126.com> added the comment:


New changeset bc3f2289b9007396bfb7f986bee477b6176c1822 by Xiang Zhang in branch 'master':
bpo-32969: Expose some missing constants in zlib and fix the doc (GH-5988)
https://github.com/python/cpython/commit/bc3f2289b9007396bfb7f986bee477b6176c1822


----------

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

From report at bugs.python.org  Wed Mar  7 00:05:47 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 07 Mar 2018 05:05:47 +0000
Subject: [docs] [issue32969] Add more constants to zlib module
In-Reply-To: <1519808340.69.0.467229070634.issue32969@psf.upfronthosting.co.za>
Message-ID: <1520399147.54.0.714561066657.issue32969@psf.upfronthosting.co.za>


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


----------
pull_requests: +5777

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

From report at bugs.python.org  Wed Mar  7 00:06:45 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 07 Mar 2018 05:06:45 +0000
Subject: [docs] [issue32969] Add more constants to zlib module
In-Reply-To: <1519808340.69.0.467229070634.issue32969@psf.upfronthosting.co.za>
Message-ID: <1520399205.24.0.714561066657.issue32969@psf.upfronthosting.co.za>


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


----------
pull_requests: +5778

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

From report at bugs.python.org  Wed Mar  7 00:26:22 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 07 Mar 2018 05:26:22 +0000
Subject: [docs] [issue32969] Add more constants to zlib module
In-Reply-To: <1519808340.69.0.467229070634.issue32969@psf.upfronthosting.co.za>
Message-ID: <1520400382.09.0.467229070634.issue32969@psf.upfronthosting.co.za>


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


New changeset c4d77a661138debbbe584b8b08410afc8719a9b1 by Miss Islington (bot) in branch '3.7':
bpo-32969: Expose some missing constants in zlib and fix the doc (GH-5988)
https://github.com/python/cpython/commit/c4d77a661138debbbe584b8b08410afc8719a9b1


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

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

From report at bugs.python.org  Wed Mar  7 00:46:13 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 07 Mar 2018 05:46:13 +0000
Subject: [docs] [issue32969] Add more constants to zlib module
In-Reply-To: <1519808340.69.0.467229070634.issue32969@psf.upfronthosting.co.za>
Message-ID: <1520401573.03.0.467229070634.issue32969@psf.upfronthosting.co.za>


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


New changeset 7592c0a686a80b9fbe2e6d519a486aca58b3260b by Miss Islington (bot) in branch '3.6':
bpo-32969: Expose some missing constants in zlib and fix the doc (GH-5988)
https://github.com/python/cpython/commit/7592c0a686a80b9fbe2e6d519a486aca58b3260b


----------

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

From report at bugs.python.org  Wed Mar  7 00:55:49 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 07 Mar 2018 05:55:49 +0000
Subject: [docs] [issue32969] Add more constants to zlib module
In-Reply-To: <1519808340.69.0.467229070634.issue32969@psf.upfronthosting.co.za>
Message-ID: <1520402149.7.0.714561066657.issue32969@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/issue32969>
_______________________________________

From report at bugs.python.org  Wed Mar  7 03:00:51 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 07 Mar 2018 08:00:51 +0000
Subject: [docs] [issue33014] Clarify doc string for str.isidentifier()
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520409651.8.0.714561066657.issue33014@psf.upfronthosting.co.za>


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


----------
keywords: +easy

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

From report at bugs.python.org  Wed Mar  7 04:27:41 2018
From: report at bugs.python.org (Anthony Flury)
Date: Wed, 07 Mar 2018 09:27:41 +0000
Subject: [docs] [issue33006] docstring of filter function is incorrect
In-Reply-To: <1520300191.48.0.467229070634.issue33006@psf.upfronthosting.co.za>
Message-ID: <1520414861.17.0.714561066657.issue33006@psf.upfronthosting.co.za>


Change by Anthony Flury <anthony.flury at btinternet.com>:


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

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

From report at bugs.python.org  Wed Mar  7 21:54:22 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 08 Mar 2018 02:54:22 +0000
Subject: [docs] [issue22822] IPv6Network constructor docs incorrect about
 valid input
In-Reply-To: <1415468629.6.0.255055357939.issue22822@psf.upfronthosting.co.za>
Message-ID: <1520477662.06.0.714561066657.issue22822@psf.upfronthosting.co.za>


Change by Xiang Zhang <angwerzx at 126.com>:


----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> ipaddress documentation errors

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

From report at bugs.python.org  Wed Mar  7 21:56:24 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 08 Mar 2018 02:56:24 +0000
Subject: [docs] [issue18802] ipaddress documentation errors
In-Reply-To: <1377118857.87.0.169407991036.issue18802@psf.upfronthosting.co.za>
Message-ID: <1520477784.62.0.467229070634.issue18802@psf.upfronthosting.co.za>


Xiang Zhang <angwerzx at 126.com> added the comment:

Ahh, I also find some errors here in ipaddress doc and opened https://github.com/python/cpython/pull/6021 to fix them.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python, xiang.zhang
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Wed Mar  7 22:22:33 2018
From: report at bugs.python.org (Eric Appelt)
Date: Thu, 08 Mar 2018 03:22:33 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520479353.29.0.714561066657.issue26701@psf.upfronthosting.co.za>


Change by Eric Appelt <eric.appelt at gmail.com>:


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

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

From report at bugs.python.org  Thu Mar  8 05:01:02 2018
From: report at bugs.python.org (Richard Neumann)
Date: Thu, 08 Mar 2018 10:01:02 +0000
Subject: [docs] [issue33028] tempfile.TemporaryDirectory incorrectly
 documented
Message-ID: <1520503262.87.0.467229070634.issue33028@psf.upfronthosting.co.za>


New submission from Richard Neumann <r.neumann at homeinfo.de>:

The tempfile.TemporaryDirectory is incorrectly documented at https://docs.python.org/3.6/library/tempfile.html#tempfile.TemporaryDirectory.

It is described as a function, though actually being a class (unlinke tempfile.NamedTemporaryFile).
The respective property "name" and method "cleanup" are only documented in the continuous text but not explicitely highlighted as the properties and method of e.g. TarFile (https://docs.python.org/3/library/tarfile.html#tarfile-objects).

----------
assignee: docs at python
components: Documentation
messages: 313431
nosy: Richard Neumann, docs at python
priority: normal
severity: normal
status: open
title: tempfile.TemporaryDirectory incorrectly documented
type: enhancement
versions: Python 3.6

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

From report at bugs.python.org  Thu Mar  8 10:20:20 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 08 Mar 2018 15:20:20 +0000
Subject: [docs] [issue33028] tempfile.TemporaryDirectory incorrectly
 documented
In-Reply-To: <1520503262.87.0.467229070634.issue33028@psf.upfronthosting.co.za>
Message-ID: <1520522420.98.0.714561066657.issue33028@psf.upfronthosting.co.za>


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


----------
nosy: +lars.gustaebel
versions: +Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Mar  8 10:20:54 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 08 Mar 2018 15:20:54 +0000
Subject: [docs] [issue33028] tempfile.TemporaryDirectory incorrectly
 documented
In-Reply-To: <1520503262.87.0.467229070634.issue33028@psf.upfronthosting.co.za>
Message-ID: <1520522454.77.0.714561066657.issue33028@psf.upfronthosting.co.za>


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


----------
type: enhancement -> 

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

From report at bugs.python.org  Thu Mar  8 15:06:11 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 08 Mar 2018 20:06:11 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520539571.64.0.467229070634.issue26701@psf.upfronthosting.co.za>


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

What about __floor__ and __ceil__?

I think all these three method do not deserve separate paragraphs in Doc/reference/datamodel.rst, but they should be grouped together with __round__.

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

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

From report at bugs.python.org  Thu Mar  8 18:22:58 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 08 Mar 2018 23:22:58 +0000
Subject: [docs] [issue33032] Mention implicit cache in struct.Struct docs
Message-ID: <1520551378.96.0.467229070634.issue33032@psf.upfronthosting.co.za>


New submission from Nick Coghlan <ncoghlan at gmail.com>:

The struct.Struct docs claim that creating and re-using a Struct object will be noticeably faster than calling the module level methods repeatedly with the same format string, as it will avoid parsing the format string multiple times: https://docs.python.org/3/library/struct.html#struct.Struct

This claim is questionable, as struct has used an internal Struct cache since at least 2.5, so if you're using less than 100 different struct layouts in any given process, the only thing you'll be saving is a string-keyed dictionary lookup.

----------
assignee: docs at python
components: Documentation
messages: 313468
nosy: docs at python, ncoghlan
priority: normal
severity: normal
stage: needs patch
status: open
title: Mention implicit cache in struct.Struct docs
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Mar  8 18:27:51 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 08 Mar 2018 23:27:51 +0000
Subject: [docs] [issue33032] Mention implicit cache in struct.Struct docs
In-Reply-To: <1520551378.96.0.467229070634.issue33032@psf.upfronthosting.co.za>
Message-ID: <1520551671.27.0.467229070634.issue33032@psf.upfronthosting.co.za>


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

The note on https://docs.python.org/3/library/re.html#re.compile provides a useful precedent for possible wording here, as the struct cache and the regex cache are quite similar.

----------

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

From report at bugs.python.org  Thu Mar  8 19:47:58 2018
From: report at bugs.python.org (Antony Lee)
Date: Fri, 09 Mar 2018 00:47:58 +0000
Subject: [docs] [issue33033] Clarify that the signed number convertors to
 PyArg_ParseTuple... *do* overflow checking
Message-ID: <1520556478.43.0.467229070634.issue33033@psf.upfronthosting.co.za>


New submission from Antony Lee <anntzer.lee at gmail.com>:

At https://docs.python.org/3/c-api/arg.html#numbers, it is explicitly documented that the unsigned number convertors do not perform overflow checking.  Implicitly, this suggests that the signed convertors *do* perform overflow checking, which they indeed do; but it would be nice to document this behavior explicitly (as overflow checking is not always expected of C-level functions).

----------
assignee: docs at python
components: Documentation
messages: 313471
nosy: Antony.Lee, docs at python
priority: normal
severity: normal
status: open
title: Clarify that the signed number convertors to PyArg_ParseTuple... *do* overflow checking
versions: Python 3.6

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

From report at bugs.python.org  Thu Mar  8 21:36:34 2018
From: report at bugs.python.org (A.M. Kuchling)
Date: Fri, 09 Mar 2018 02:36:34 +0000
Subject: [docs] [issue28626] Tutorial: rearrange discussion of output
 formatting to encourage f-strings
In-Reply-To: <1478452855.22.0.932657206329.issue28626@psf.upfronthosting.co.za>
Message-ID: <1520562994.83.0.714561066657.issue28626@psf.upfronthosting.co.za>


Change by A.M. Kuchling <amk at amk.ca>:


----------
pull_requests: +5798

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

From report at bugs.python.org  Fri Mar  9 02:16:25 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 09 Mar 2018 07:16:25 +0000
Subject: [docs] [issue33033] Clarify that the signed number convertors to
 PyArg_ParseTuple... *do* overflow checking
In-Reply-To: <1520556478.43.0.467229070634.issue33033@psf.upfronthosting.co.za>
Message-ID: <1520579784.98.0.467229070634.issue33033@psf.upfronthosting.co.za>


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

This doesn't look a good idea to me. It is implied that all checks are performed. For example it is implied that an error will be raised if the argument is of wrong type. I think that adding "with overflow checking" to every converting from a Python integer will just clutter the documentation.

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

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

From report at bugs.python.org  Fri Mar  9 04:34:18 2018
From: report at bugs.python.org (Antony Lee)
Date: Fri, 09 Mar 2018 09:34:18 +0000
Subject: [docs] [issue33033] Clarify that the signed number convertors to
 PyArg_ParseTuple... *do* overflow checking
In-Reply-To: <1520556478.43.0.467229070634.issue33033@psf.upfronthosting.co.za>
Message-ID: <1520588058.75.0.467229070634.issue33033@psf.upfronthosting.co.za>


Antony Lee <anntzer.lee at gmail.com> added the comment:

One could just add, immediately below the "Numbers" section, something like: "The signed convertors (b, h, i, ...) perform overflow checking.  The unsigned convertors (B, H, I, ...) do not."  That would actually be shorter than the current version, which repeats the second half for each unsigned entry...

----------

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

From clear0755 at naver.com  Thu Mar  8 09:05:50 2018
From: clear0755 at naver.com (=?utf-8?B?64W47Jew7IiY?=)
Date: Thu, 08 Mar 2018 23:05:50 +0900
Subject: [docs] =?utf-8?q?I_am_a_student_studying_Python_in_Korea=2E__I_f?=
	=?utf-8?q?ound_strange_thing_while_studying_through_idle?=
Message-ID: <42aded71abe77e317214394aa26c7c5@cweb19.nm.nhnsystem.com>

If you type print (" hello\ rpython ") into the python shell, only the python is printed and i learned it's a crystal. However, if you type print (" hello\ rpython ") in the python idle, it is output as hellopython. I wonder why it prints like this. I would appreciate your answer. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180308/038f1fb8/attachment.html>

From romansky at ualberta.ca  Tue Mar  6 18:12:38 2018
From: romansky at ualberta.ca (Stephen Romansky)
Date: Tue, 6 Mar 2018 16:12:38 -0700
Subject: [docs] documentation code download
Message-ID: <CAKR_C8a4u9Z5S6TkrBtoVoyafHHbn0VtAYEGmnqWjyj+ukzV0g@mail.gmail.com>

Hi,

Is it possible to only download all of the code samples from the
documentation?


Regards,

Stephen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180306/f450c99a/attachment.html>

From report at bugs.python.org  Fri Mar  9 10:27:32 2018
From: report at bugs.python.org (Stephen Wille Padnos)
Date: Fri, 09 Mar 2018 15:27:32 +0000
Subject: [docs] [issue33035] Some examples in documentation section 4.7.2
 are incorrect
Message-ID: <1520609252.53.0.467229070634.issue33035@psf.upfronthosting.co.za>


New submission from Stephen Wille Padnos <steve at thothsystems.com>:

Section 4.7.2 of the documentation, "Keyword Arguments", has several examples of valid calls to the sample function parrot.

The function definition is:
def parrot(voltage, state='a stiff', action='voom', type='Norwegian Blue'):

The last two calls in the valid samples are actually not valid, since they are missing the required "voltage" parameter.
parrot('a million', 'bereft of life', 'jump')         # 3 positional arguments
parrot('a thousand', state='pushing up the daisies')  # 1 positional, 1 keyword

They should be changed to include a value for voltage, along with a change to the comment:
parrot(1000, 'a million', 'bereft of life', 'jump')         # 4 positional arguments
parrot(1000, 'a thousand', state='pushing up the daisies')  # 2 positional, 1 keyword

This issue is present in all currently available versions of the documentation: 2.7; 3.5; 3.6.4; pre (3.7); and dev (3.8).

----------
assignee: docs at python
components: Documentation
messages: 313485
nosy: docs at python, stephenwp
priority: normal
severity: normal
status: open
title: Some examples in documentation section 4.7.2 are incorrect
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Mar  9 10:35:26 2018
From: report at bugs.python.org (Emanuel Barry)
Date: Fri, 09 Mar 2018 15:35:26 +0000
Subject: [docs] [issue33035] Some examples in documentation section 4.7.2
 are incorrect
In-Reply-To: <1520609252.53.0.467229070634.issue33035@psf.upfronthosting.co.za>
Message-ID: <1520609726.74.0.467229070634.issue33035@psf.upfronthosting.co.za>


Emanuel Barry <barry at dadadata.net> added the comment:

The documentation is correct. The first argument in both of those cases is a str, which may not be what you were expecting, but the calls are still valid.

----------
nosy: +ebarry
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From mariatta.wijaya at gmail.com  Fri Mar  9 13:46:25 2018
From: mariatta.wijaya at gmail.com (Mariatta Wijaya)
Date: Fri, 9 Mar 2018 10:46:25 -0800
Subject: [docs] I am a student studying Python in Korea. I found strange
 thing while studying through idle
In-Reply-To: <42aded71abe77e317214394aa26c7c5@cweb19.nm.nhnsystem.com>
References: <42aded71abe77e317214394aa26c7c5@cweb19.nm.nhnsystem.com>
Message-ID: <CAGbohnZLZsxWKdM6MMYkvh7+Yw8=TRyFsjRLWCvPKWJbBN3cqQ@mail.gmail.com>

Hi,

There are known differences in the output of IDLE and the terminal window.
There is some documentation here:
https://docs.python.org/3/library/idle.html#idle-console-differences

In addition, IDLE seems to only handle \n  character, but other charater
like \r \b aren't handled.

There is an issue in the bug tracker that discusses this:
https://bugs.python.org/issue23220

Hope this helps.


Mariatta Wijaya

?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180309/b659d3c8/attachment.html>

From report at bugs.python.org  Fri Mar  9 15:03:25 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 09 Mar 2018 20:03:25 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520625805.47.0.467229070634.issue32758@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:


New changeset 7a7f100eb352d08938ee0f5ba59c18f56dc4a7b5 by Brett Cannon in branch 'master':
bpo-32758: Warn that ast.parse() and ast.literal_eval() can segfault the interpreter (GH-5960)
https://github.com/python/cpython/commit/7a7f100eb352d08938ee0f5ba59c18f56dc4a7b5


----------

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

From report at bugs.python.org  Fri Mar  9 15:04:31 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 09 Mar 2018 20:04:31 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520625871.25.0.714561066657.issue32758@psf.upfronthosting.co.za>


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


----------
pull_requests: +5802

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

From report at bugs.python.org  Fri Mar  9 15:06:30 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 09 Mar 2018 20:06:30 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520625990.76.0.714561066657.issue32758@psf.upfronthosting.co.za>


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


----------
pull_requests: +5803

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

From report at bugs.python.org  Fri Mar  9 15:20:17 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 09 Mar 2018 20:20:17 +0000
Subject: [docs] [issue30940] Documentation for round() is incorrect.
In-Reply-To: <1500223918.38.0.72996478594.issue30940@psf.upfronthosting.co.za>
Message-ID: <1520626817.07.0.467229070634.issue30940@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

This issue seems to have slipped through the cracks with a couple of long-standing PR's open.  Anyone feel up to finishing it?

----------
nosy: +ned.deily
stage: needs patch -> patch review
versions: +Python 3.8 -Python 3.5

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

From report at bugs.python.org  Fri Mar  9 15:26:06 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 09 Mar 2018 20:26:06 +0000
Subject: [docs] [issue33014] Clarify doc string for str.isidentifier()
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520627166.45.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

No new string method ;-).  "Call function keyword.iskeyword() ..." should make it clear that iskeyword is not a string method.  Samyam, I suggest getting agreement on new wording first.  Then do PR that is more or less 'pre-approved'.

----------
nosy: +terry.reedy

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

From report at bugs.python.org  Fri Mar  9 15:35:23 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 09 Mar 2018 20:35:23 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520627723.54.0.467229070634.issue32758@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:


New changeset b316c44b0105d11a80ff971636143735f3655bbf by Brett Cannon (Miss Islington (bot)) in branch '3.6':
bpo-32758: Warn that ast.parse() and ast.literal_eval() can segfault the interpreter (GH-5960) (GH-6042)
https://github.com/python/cpython/commit/b316c44b0105d11a80ff971636143735f3655bbf


----------

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

From report at bugs.python.org  Fri Mar  9 15:35:44 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 09 Mar 2018 20:35:44 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520627744.52.0.467229070634.issue32758@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:


New changeset f2fffd41b42d88fe36b483852ae33d5a415b7082 by Brett Cannon (Miss Islington (bot)) in branch '3.7':
bpo-32758: Warn that ast.parse() and ast.literal_eval() can segfault the interpreter (GH-5960) (GH-6041)
https://github.com/python/cpython/commit/f2fffd41b42d88fe36b483852ae33d5a415b7082


----------

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

From report at bugs.python.org  Fri Mar  9 15:42:59 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 09 Mar 2018 20:42:59 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520628179.37.0.467229070634.issue32758@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

I have the changes in for Python 3 for the ast module.

Updated TODO list:

- [x] ast module
- [ ] compile()
- [ ] eval() for >= 3.7
- [ ] exec() for >= 3.7
- [ ] dbm.dumb.open()
- [ ] inspect

----------

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

From report at bugs.python.org  Fri Mar  9 15:43:53 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 09 Mar 2018 20:43:53 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520628233.28.0.467229070634.issue32758@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

Actually, the TODO list is:

- [x] ast module for Python 3
- [ ] compile()
- [ ] eval() for >= 3.7
- [ ] exec() for >= 3.7
- [ ] dbm.dumb.open()
- [ ] inspect
- [ ] ast module for Python 2 (see https://github.com/python/cpython/pull/5960)

----------

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

From report at bugs.python.org  Fri Mar  9 15:44:25 2018
From: report at bugs.python.org (David Beazley)
Date: Fri, 09 Mar 2018 20:44:25 +0000
Subject: [docs] [issue33014] Clarify doc string for str.isidentifier()
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520628265.45.0.467229070634.issue33014@psf.upfronthosting.co.za>


David Beazley <dave at dabeaz.com> added the comment:

That wording isn't much better in my opinion.  If I'm sitting there looking at methods like str.isdigit(), str.isnumeric(), str.isascii(), and str.isidentifier(), seeing keyword.iskeyword() makes me think it's a method regardless of whether you label it a function or method.  Explicitly stating that "keyword" is actually the keyword module makes it much clearer. Or at least including the argument as well keyword.iskeyword(kw).

It really should be a string method though ;-)

----------

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

From report at bugs.python.org  Fri Mar  9 15:53:30 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 09 Mar 2018 20:53:30 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520628810.68.0.714561066657.issue32758@psf.upfronthosting.co.za>


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


----------
pull_requests: +5804

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

From report at bugs.python.org  Fri Mar  9 16:19:40 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 09 Mar 2018 21:19:40 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520630380.5.0.714561066657.issue32758@psf.upfronthosting.co.za>


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


----------
pull_requests: +5806

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

From report at bugs.python.org  Fri Mar  9 16:19:47 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 09 Mar 2018 21:19:47 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520630387.21.0.714561066657.issue32758@psf.upfronthosting.co.za>


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


----------
pull_requests: +5807

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

From report at bugs.python.org  Fri Mar  9 16:19:56 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 09 Mar 2018 21:19:56 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520630396.7.0.467229070634.issue32758@psf.upfronthosting.co.za>


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

I think we can ignore the inspect module. It is unlikely that it will cause a crash unintentionally, and it is hard to use this for attacks. The attacker needs to create an extension function with malicious __text_signature__, but if he is able to execute arbitrary binary code, there is a much larger problem.

And perhaps there is no need to repeat the warning for exec() and eval(). They are considered more dangerous than compile().

----------

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

From report at bugs.python.org  Fri Mar  9 16:42:35 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 09 Mar 2018 21:42:35 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520631755.63.0.467229070634.issue32758@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

Thanks for the feedback, Serhiy! Based on that, the new TODO list is:

- [x] ast module for Python 3
- [x] compile() for Python 3
- [ ] dbm.dumb.open()
- [ ] ast module for Python 2 (see https://github.com/python/cpython/pull/5960)
- [ ] compile() for Python 2 (see https://github.com/python/cpython/pull/6043)

----------

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

From report at bugs.python.org  Fri Mar  9 16:55:01 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 09 Mar 2018 21:55:01 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520632501.61.0.467229070634.issue32758@psf.upfronthosting.co.za>


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

In 3.7 compile() can crash not only when compiling to an AST object (due to recursive AST optimization).

----------

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

From report at bugs.python.org  Fri Mar  9 16:55:26 2018
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 09 Mar 2018 21:55:26 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520632526.37.0.714561066657.issue32758@psf.upfronthosting.co.za>


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


----------
nosy:  -yselivanov

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

From report at bugs.python.org  Fri Mar  9 18:17:11 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 09 Mar 2018 23:17:11 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520637430.96.0.467229070634.issue32758@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

@Serhiy: Correct, which is what the warning says: https://github.com/python/cpython/pull/6043/files .

----------

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

From report at bugs.python.org  Fri Mar  9 18:53:07 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 09 Mar 2018 23:53:07 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520639587.56.0.714561066657.issue32758@psf.upfronthosting.co.za>


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


----------
pull_requests: +5808

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

From report at bugs.python.org  Fri Mar  9 18:59:26 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 09 Mar 2018 23:59:26 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520639966.09.0.714561066657.issue32758@psf.upfronthosting.co.za>


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


----------
pull_requests: +5809

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

From report at bugs.python.org  Fri Mar  9 19:14:06 2018
From: report at bugs.python.org (Brett Cannon)
Date: Sat, 10 Mar 2018 00:14:06 +0000
Subject: [docs] [issue32758] Stack overflow when parse long expression to AST
In-Reply-To: <1517682171.17.0.467229070634.issue32758@psf.upfronthosting.co.za>
Message-ID: <1520640846.75.0.467229070634.issue32758@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:

- [x] ast module for Python 3
- [x] compile() for Python 3
- [x] dbm.dumb.open()
- [ ] ast module for Python 2 (see https://github.com/python/cpython/pull/5960)
- [ ] compile() for Python 2 (see https://github.com/python/cpython/pull/6043)

At this point there is only Python 2 stuff and I'm not bothered enough to see those changed, so I will leave this open for anyone who wants to put in the effort to backport the warnings.

----------
assignee: brett.cannon -> 
keywords: +easy -patch
versions:  -Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat Mar 10 03:44:20 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 10 Mar 2018 08:44:20 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520671460.34.0.467229070634.issue26701@psf.upfronthosting.co.za>


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


New changeset 308eab979d153f1ab934383dc08bc4546ced8b6c by Nick Coghlan (Eric Appelt) in branch 'master':
bpo-26701: Add documentation for __trunc__ (GH-6022)
https://github.com/python/cpython/commit/308eab979d153f1ab934383dc08bc4546ced8b6c


----------
nosy: +ncoghlan

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

From report at bugs.python.org  Sat Mar 10 03:44:23 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 10 Mar 2018 08:44:23 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520671463.25.0.714561066657.issue26701@psf.upfronthosting.co.za>


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


----------
pull_requests: +5810

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

From report at bugs.python.org  Sat Mar 10 03:45:21 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 10 Mar 2018 08:45:21 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520671521.52.0.714561066657.issue26701@psf.upfronthosting.co.za>


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


----------
pull_requests: +5811

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

From report at bugs.python.org  Sat Mar 10 04:03:27 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 10 Mar 2018 09:03:27 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520672607.02.0.467229070634.issue26701@psf.upfronthosting.co.za>


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

I think __trunc__ is special here, as it's called by a built-in type constructor, whereas __floor__ and __ceil__ really are specific to their respective math module functions. That said, I also wouldn't be opposed to listing all 4 methods together (or else listing __floor__ and __ceil__ with the just added entry for __trunc__).

I also filed https://bugs.python.org/issue33039 to cover an anomaly Eric found after I suggested adding __index__ to the list of methods tried, which is that int() and math.trunc() *don't* call __index__ implicitly: the type has to set "__int__ = __index__" and "__trunc__ = __index__" to get them to work.

I suspect we just didn't notice when PEP 357 was implemented because the developers that wanted __index__ were adding it to types that *already* defined __int__ and __trunc__.

----------

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

From report at bugs.python.org  Sat Mar 10 06:34:44 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 10 Mar 2018 11:34:44 +0000
Subject: [docs] [issue33039] int() and math.trunc don't accept objects that
 only define __index__
In-Reply-To: <1520672231.04.0.467229070634.issue33039@psf.upfronthosting.co.za>
Message-ID: <1520681684.27.0.467229070634.issue33039@psf.upfronthosting.co.za>


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

Marking this as a documentation enhancement request for now, but I think we should also consider changing the type creation behaviour in 3.8 to implicitly add __int__ and __trunc__ definitions when __index__ is defined, but they aren't.

That way, no behaviour will change for classes that explicitly define __int__ or __trunc__, but classes that only define __index__ without defining the other methods will behave more intuitively.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> needs patch
type:  -> enhancement
versions: +Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat Mar 10 10:02:23 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 10 Mar 2018 15:02:23 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520694143.24.0.714561066657.issue26701@psf.upfronthosting.co.za>


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


----------
pull_requests: +5815

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

From report at bugs.python.org  Sat Mar 10 10:10:39 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 10 Mar 2018 15:10:39 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520694639.46.0.467229070634.issue26701@psf.upfronthosting.co.za>


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


New changeset f34e0d60e27acff3f9604ec63e9de36878c3743a by Nick Coghlan (Miss Islington (bot)) in branch '3.7':
bpo-26701: Add documentation for __trunc__ (GH-6049)
https://github.com/python/cpython/commit/f34e0d60e27acff3f9604ec63e9de36878c3743a


----------

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

From report at bugs.python.org  Sat Mar 10 10:10:48 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 10 Mar 2018 15:10:48 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520694648.04.0.467229070634.issue26701@psf.upfronthosting.co.za>


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


New changeset 1028ca4f04c14cf40a8f3e7951623a96ec0143c2 by Nick Coghlan (Miss Islington (bot)) in branch '3.6':
bpo-26701: Add documentation for __trunc__ (GH-6050)
https://github.com/python/cpython/commit/1028ca4f04c14cf40a8f3e7951623a96ec0143c2


----------

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

From report at bugs.python.org  Sat Mar 10 10:16:36 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 10 Mar 2018 15:16:36 +0000
Subject: [docs] [issue33014] Clarify doc string for str.isidentifier()
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520694996.72.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

If this docstring needs an improvement Terry's wording LGTM. I'm -1 for further complicating it.

Where did you get the idea that iskeyword() is a string method? Nothing in the docstring points to this. "keyword" is not used as an alias of "str". It is not used anywhere else in the docstring at all.

I think this is an attempt to solve a non-problem.

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

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

From report at bugs.python.org  Sat Mar 10 10:18:35 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 10 Mar 2018 15:18:35 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520695115.04.0.467229070634.issue26701@psf.upfronthosting.co.za>


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


New changeset 496431ffb6c29719332bf2af773349e8dd85e45a by Serhiy Storchaka in branch 'master':
bpo-26701: Improve documentation for the rounding special methods. (#6054)
https://github.com/python/cpython/commit/496431ffb6c29719332bf2af773349e8dd85e45a


----------

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

From report at bugs.python.org  Sat Mar 10 10:19:42 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 10 Mar 2018 15:19:42 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520695182.06.0.714561066657.issue26701@psf.upfronthosting.co.za>


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


----------
pull_requests: +5817

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

From report at bugs.python.org  Sat Mar 10 10:20:41 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 10 Mar 2018 15:20:41 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520695241.23.0.714561066657.issue26701@psf.upfronthosting.co.za>


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


----------
pull_requests: +5818

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

From report at bugs.python.org  Sat Mar 10 10:49:26 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 10 Mar 2018 15:49:26 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520696966.72.0.467229070634.issue26701@psf.upfronthosting.co.za>


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


New changeset 89090789debb9d76892af566277cb71740808945 by Miss Islington (bot) in branch '3.7':
bpo-26701: Improve documentation for the rounding special methods. (GH-6054)
https://github.com/python/cpython/commit/89090789debb9d76892af566277cb71740808945


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

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

From report at bugs.python.org  Sat Mar 10 10:55:15 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 10 Mar 2018 15:55:15 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520697315.22.0.467229070634.issue26701@psf.upfronthosting.co.za>


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


New changeset de8567e38c44b1509f0b906aec54437256848f14 by Miss Islington (bot) in branch '3.6':
bpo-26701: Improve documentation for the rounding special methods. (GH-6054)
https://github.com/python/cpython/commit/de8567e38c44b1509f0b906aec54437256848f14


----------

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

From report at bugs.python.org  Sat Mar 10 11:24:47 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Mar 2018 16:24:47 +0000
Subject: [docs] [issue33014] Clarify doc string for str.isidentifier()
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520699087.55.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

I don't think my suggestion is much better either, and I otherwise agree with Serhiy.  There are a thousand+ more important doc issues.

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

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

From report at bugs.python.org  Sat Mar 10 11:27:32 2018
From: report at bugs.python.org (David Beazley)
Date: Sat, 10 Mar 2018 16:27:32 +0000
Subject: [docs] [issue33014] Clarify doc string for str.isidentifier()
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520699252.18.0.467229070634.issue33014@psf.upfronthosting.co.za>


David Beazley <dave at dabeaz.com> added the comment:

s = 'Some String'
s.isalnum()
s.isalpha()
s.isdecimal()
s.isdigit()
s.isidentifier()
s.islower()
s.isnumeric()
s.isprintable()
s.isspace()
s.istitle()
s.isupper()

Not really sure where I would have gotten the idea that it might be referring to s.iskeyword().  But what do I know?  I'll stop submitting further suggestions.

----------

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

From report at bugs.python.org  Sat Mar 10 11:53:39 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Mar 2018 16:53:39 +0000
Subject: [docs] [issue33014] Clarify doc string for str.isidentifier()
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520700819.55.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

Part of my reason for closing is that we have an index entry "iskeyword() (in module keyword)"  to help anyone who tries the function as a method.  But I am reopening for 2 reasons:

 1. I think the following is a better improvement that reads better as well as being more informative.  I would be willing to merge it.

"Call keyword.iskeyword(s) to test whether string s is a reserved identifier, such as "def" or "class".

2. We should fix the buggy iskeyword docstring in 2.7 and 3.x.

>>> keyword.iskeyword.__doc__
'x.__contains__(y) <==> y in x.'

Replace with the doc entry: "Return true if s is a Python keyword."

----------
resolution: rejected -> 
stage: resolved -> needs patch
status: closed -> open
type:  -> behavior
versions: +Python 2.7, Python 3.6, Python 3.8

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

From report at bugs.python.org  Sat Mar 10 11:55:10 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Mar 2018 16:55:10 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring,
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520700910.65.0.714561066657.issue33014@psf.upfronthosting.co.za>


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


----------
title: Clarify doc string for str.isidentifier() -> Clarify str.isidentifier docstring, fix keyword.iskeyword docstring

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

From report at bugs.python.org  Sat Mar 10 12:11:50 2018
From: report at bugs.python.org (Carol Willing)
Date: Sat, 10 Mar 2018 17:11:50 +0000
Subject: [docs] [issue33014] Clarify doc string for str.isidentifier()
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520701910.6.0.467229070634.issue33014@psf.upfronthosting.co.za>


Carol Willing <willingc at gmail.com> added the comment:

Terry's latest documentation suggestion sounds good and "explicit" by including an example.

David, I appreciate your doc suggestions. If it's befuddling you, it's likely doing the same for others.

CuriousLearner, do you wish to try to incorporate Terry's latest suggestions?

Thanks all.

----------
nosy: +willingc
title: Clarify str.isidentifier docstring, fix keyword.iskeyword docstring -> Clarify doc string for str.isidentifier()

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

From report at bugs.python.org  Sat Mar 10 12:30:28 2018
From: report at bugs.python.org (Carol Willing)
Date: Sat, 10 Mar 2018 17:30:28 +0000
Subject: [docs] [issue33043] Add a 'Contributing to Docs' link at the bottom
 of docs.python.org
Message-ID: <1520703028.47.0.467229070634.issue33043@psf.upfronthosting.co.za>


New submission from Carol Willing <willingc at gmail.com>:

Adding a 'Contributing to Docs' link at the bottom of the docs.python.org page between 'Reporting bugs' and 'About Documentation'.

This could link to the devguide section on contributing to docs or provide a short paragraph including:
- the importance of CPython docs as well as other Python projects (warehouse, popular libraries, etc.)
- link to the devguide and its section on documentation
- link to the core mentorship mailing list
- link to docs mailing list

As an example, the Rust project's Docs-Contributing page is a good start: https://www.rust-lang.org/en-US/contribute-docs.html

----------
assignee: docs at python
components: Documentation
messages: 313549
nosy: docs at python, willingc
priority: normal
severity: normal
stage: needs patch
status: open
title: Add a 'Contributing to Docs' link at the bottom of docs.python.org

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

From report at bugs.python.org  Sat Mar 10 12:44:28 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Mar 2018 17:44:28 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring,
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520703868.67.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

Debating historical design decisions that effectively cannot be changed is off topic for the tracker (but fair game on python-list).  However, I will explain this much.  The s.isxyz questions are answered by examining the characters and codepoints in s.  Answering iskeyword(s) requires reference to the collection of keywords, kwlist, which must be exposed to users, and which may change in any new version.  We usually attach constant data attributes to modules (other than builtins), and never (that I can think of) to built-in classes.  "def iskeyword(s): return s in kwlist:" belongs in the module with kwlist.

----------
nosy:  -willingc
title: Clarify doc string for str.isidentifier() -> Clarify str.isidentifier docstring, fix keyword.iskeyword docstring

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

From report at bugs.python.org  Sat Mar 10 12:51:08 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Mar 2018 17:51:08 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520704268.51.0.714561066657.issue33014@psf.upfronthosting.co.za>


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


----------
nosy: +willingc -serhiy.storchaka
title: Clarify str.isidentifier docstring, fix keyword.iskeyword docstring -> Clarify str.isidentifier docstring; fix keyword.iskeyword docstring
versions:  -Python 2.7, Python 3.6, Python 3.8

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

From report at bugs.python.org  Sat Mar 10 12:51:44 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 10 Mar 2018 17:51:44 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520704304.84.0.714561066657.issue33014@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Mar 10 13:31:50 2018
From: report at bugs.python.org (Ned Deily)
Date: Sat, 10 Mar 2018 18:31:50 +0000
Subject: [docs] [issue33043] Add a 'Contributing to Docs' link at the bottom
 of docs.python.org
In-Reply-To: <1520703028.47.0.467229070634.issue33043@psf.upfronthosting.co.za>
Message-ID: <1520706710.46.0.467229070634.issue33043@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

That's a good idea.  I see that there is already a "Found a bug?" link at the bottom of each doc page and that links to a page like:

https://docs.python.org/3/bugs.html

and that page has a Documentation Bugs section.  Perhaps adding a link or two in there would help.

----------
nosy: +ned.deily

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

From report at bugs.python.org  Sat Mar 10 13:35:34 2018
From: report at bugs.python.org (Himanshu Lakhara)
Date: Sat, 10 Mar 2018 18:35:34 +0000
Subject: [docs] [issue27428] Document WindowsRegistryFinder inherits from
 MetaPathFinder
In-Reply-To: <1467326072.76.0.431868228595.issue27428@psf.upfronthosting.co.za>
Message-ID: <1520706934.31.0.714561066657.issue27428@psf.upfronthosting.co.za>


Change by Himanshu Lakhara <himanshulakhara1947 at gmail.com>:


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

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

From report at bugs.python.org  Sat Mar 10 17:27:06 2018
From: report at bugs.python.org (Matt Eaton)
Date: Sat, 10 Mar 2018 22:27:06 +0000
Subject: [docs] [issue33045] SSL Dcumentation Error
Message-ID: <1520720825.94.0.467229070634.issue33045@psf.upfronthosting.co.za>


New submission from Matt Eaton <agnosticdev at gmail.com>:

I was reading through the SSL documentation and noticed a typo on Diffe-Hellman and wanted to clean it up.  

PR is coming soon.

----------
assignee: docs at python
components: Documentation
messages: 313559
nosy: agnosticdev, docs at python
priority: normal
severity: normal
status: open
title: SSL Dcumentation Error
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sat Mar 10 17:35:06 2018
From: report at bugs.python.org (Matt Eaton)
Date: Sat, 10 Mar 2018 22:35:06 +0000
Subject: [docs] [issue33045] SSL Dcumentation Error
In-Reply-To: <1520720825.94.0.467229070634.issue33045@psf.upfronthosting.co.za>
Message-ID: <1520721306.26.0.714561066657.issue33045@psf.upfronthosting.co.za>


Change by Matt Eaton <agnosticdev at gmail.com>:


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

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

From report at bugs.python.org  Sat Mar 10 18:25:47 2018
From: report at bugs.python.org (Carol Willing)
Date: Sat, 10 Mar 2018 23:25:47 +0000
Subject: [docs] [issue33043] Add a 'Contributing to Docs' link at the bottom
 of docs.python.org
In-Reply-To: <1520703028.47.0.467229070634.issue33043@psf.upfronthosting.co.za>
Message-ID: <1520724347.34.0.467229070634.issue33043@psf.upfronthosting.co.za>


Carol Willing <willingc at gmail.com> added the comment:

Great suggestion Ned. It would be great to have some links on the bug page too.

----------

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

From report at bugs.python.org  Sat Mar 10 18:41:26 2018
From: report at bugs.python.org (Carol Willing)
Date: Sat, 10 Mar 2018 23:41:26 +0000
Subject: [docs] [issue25910] Fixing links in documentation
In-Reply-To: <1450530544.1.0.9187941337.issue25910@psf.upfronthosting.co.za>
Message-ID: <1520725286.23.0.467229070634.issue25910@psf.upfronthosting.co.za>


Carol Willing <willingc at gmail.com> added the comment:

A number of PRs have been merged since this issue opened in 2015. After Victor's merge of GH-1933 in January 2018, this looks ready to close. I'm going to close it. 

If there are further links that need fixing as they sometimes fall out of date, please open a new issue with specific links needing updating. Thanks.

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

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

From report at bugs.python.org  Sat Mar 10 20:00:08 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 11 Mar 2018 01:00:08 +0000
Subject: [docs] [issue33045] SSL Dcumentation Error
In-Reply-To: <1520720825.94.0.467229070634.issue33045@psf.upfronthosting.co.za>
Message-ID: <1520730007.41.0.467229070634.issue33045@psf.upfronthosting.co.za>


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


New changeset 9cf8c42f3231d3f066670d087a997bd1278482a0 by Berker Peksag (Matt Eaton) in branch 'master':
bpo-33045: Fix typos in SSL documentation (GH-6065)
https://github.com/python/cpython/commit/9cf8c42f3231d3f066670d087a997bd1278482a0


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

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

From report at bugs.python.org  Sat Mar 10 20:00:20 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 11 Mar 2018 01:00:20 +0000
Subject: [docs] [issue33045] SSL Dcumentation Error
In-Reply-To: <1520720825.94.0.467229070634.issue33045@psf.upfronthosting.co.za>
Message-ID: <1520730020.36.0.714561066657.issue33045@psf.upfronthosting.co.za>


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


----------
pull_requests: +5830

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

From report at bugs.python.org  Sat Mar 10 20:01:13 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 11 Mar 2018 01:01:13 +0000
Subject: [docs] [issue33045] SSL Dcumentation Error
In-Reply-To: <1520720825.94.0.467229070634.issue33045@psf.upfronthosting.co.za>
Message-ID: <1520730072.92.0.714561066657.issue33045@psf.upfronthosting.co.za>


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


----------
pull_requests: +5831

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

From report at bugs.python.org  Sat Mar 10 20:21:30 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 11 Mar 2018 01:21:30 +0000
Subject: [docs] [issue33045] SSL Dcumentation Error
In-Reply-To: <1520720825.94.0.467229070634.issue33045@psf.upfronthosting.co.za>
Message-ID: <1520731290.07.0.467229070634.issue33045@psf.upfronthosting.co.za>


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


New changeset 17b6c19d39229619de649f5a9e28a46779ef1c51 by Berker Peksag (Miss Islington (bot)) in branch '3.7':
bpo-33045: Fix typos in SSL documentation (GH-6065)
https://github.com/python/cpython/commit/17b6c19d39229619de649f5a9e28a46779ef1c51


----------

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

From report at bugs.python.org  Sat Mar 10 20:26:04 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 11 Mar 2018 01:26:04 +0000
Subject: [docs] [issue33045] SSL Dcumentation Error
In-Reply-To: <1520720825.94.0.467229070634.issue33045@psf.upfronthosting.co.za>
Message-ID: <1520731563.83.0.467229070634.issue33045@psf.upfronthosting.co.za>


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


New changeset 3f439d14ad48f5d4f6017fc814326fb1f6237b53 by Berker Peksag (Miss Islington (bot)) in branch '3.6':
bpo-33045: Fix typos in SSL documentation (GH-6065)
https://github.com/python/cpython/commit/3f439d14ad48f5d4f6017fc814326fb1f6237b53


----------

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

From report at bugs.python.org  Sat Mar 10 20:27:06 2018
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 11 Mar 2018 01:27:06 +0000
Subject: [docs] [issue33045] SSL Dcumentation Error
In-Reply-To: <1520720825.94.0.467229070634.issue33045@psf.upfronthosting.co.za>
Message-ID: <1520731625.81.0.467229070634.issue33045@psf.upfronthosting.co.za>


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

Thank you, Matt (and welcome to Python development!)

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

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

From report at bugs.python.org  Sat Mar 10 20:29:23 2018
From: report at bugs.python.org (Matt Eaton)
Date: Sun, 11 Mar 2018 01:29:23 +0000
Subject: [docs] [issue33045] SSL Dcumentation Error
In-Reply-To: <1520720825.94.0.467229070634.issue33045@psf.upfronthosting.co.za>
Message-ID: <1520731763.6.0.467229070634.issue33045@psf.upfronthosting.co.za>


Matt Eaton <agnosticdev at gmail.com> added the comment:

Thank you very much, Berker!!

----------

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

From report at bugs.python.org  Sat Mar 10 20:48:17 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 11 Mar 2018 01:48:17 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1520732897.1.0.467229070634.issue32996@psf.upfronthosting.co.za>


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


New changeset 51302a5fcc557e6afc0bf1e3b371f5f37c76dc77 by Serhiy Storchaka in branch 'master':
bpo-32996: Improve What's New in 3.7. (#5983)
https://github.com/python/cpython/commit/51302a5fcc557e6afc0bf1e3b371f5f37c76dc77


----------

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

From report at bugs.python.org  Sat Mar 10 20:49:29 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 11 Mar 2018 01:49:29 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1520732969.8.0.714561066657.issue32996@psf.upfronthosting.co.za>


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


----------
pull_requests: +5832

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

From report at bugs.python.org  Sun Mar 11 01:29:35 2018
From: report at bugs.python.org (miss-islington)
Date: Sun, 11 Mar 2018 06:29:35 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1520749775.59.0.467229070634.issue32996@psf.upfronthosting.co.za>


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


New changeset 720a4b69c6b66ae5d6f447d5814bd204170c94b3 by Miss Islington (bot) in branch '3.7':
bpo-32996: Improve What's New in 3.7. (GH-5983)
https://github.com/python/cpython/commit/720a4b69c6b66ae5d6f447d5814bd204170c94b3


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

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

From dick at d-jackson.com  Fri Mar  9 17:51:54 2018
From: dick at d-jackson.com (Dick Jackson)
Date: Fri, 9 Mar 2018 14:51:54 -0800
Subject: [docs] Tutorial and Glossary misleading/ambiguous wording on "floor
 division"
Message-ID: <D49D6D81-0F1C-4B14-B971-51D8A763B0C3@d-jackson.com>

Hi,

On https://docs.python.org/3.6/tutorial/introduction.html <https://docs.python.org/3.6/tutorial/introduction.html>
I think this wording is misleading:
To do floor division <https://docs.python.org/3.6/glossary.html#term-floor-division> and get an integer result (discarding any fractional result) you can use the // operator;

Considering negative numbers (where -4 // 3 gives -2, which is clearly not "discarding the fraction" from -1.333), this would be better:
To do floor division <https://docs.python.org/3.6/glossary.html#term-floor-division> and get an integer result (rounding down to next lower integer) you can use the // operator;

Actually, I'd say the glossary definition of "floor division" could be improved as well, at https://docs.python.org/3.6/glossary.html#term-floor-division <https://docs.python.org/3.6/glossary.html#term-floor-division> :
Mathematical division that rounds down to nearest integer.
? might be better as:
Mathematical division that rounds down to the next lower integer.

The idea of "rounding" to the "nearest integer" might make a lot of people think of normal rounding, even though the word "down" is there. I think my phrasing is less ambiguous. Thanks for considering these changes!

Cheers,
-Dick
Dick Jackson Software Consulting Inc.
Victoria, BC, Canada    +1-250-220-6117	
dick at d-jackson.com <mailto:dick at d-jackson.com>
http://www.d-jackson.com <http://www.d-jackson.com/>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180309/4977cb4d/attachment-0001.html>

From linux4ever197 at gmail.com  Fri Mar  9 10:19:53 2018
From: linux4ever197 at gmail.com (Yousef Elsayed)
Date: Fri, 9 Mar 2018 17:19:53 +0200
Subject: [docs] No download for python 3.5 docs
Message-ID: <CADHb8=mfEoMkgTnOVhQzogSRGY7eE2wKsKwBxoSaTXH4bkttew@mail.gmail.com>

Hello,
I can not download python's docs - version 3.5 - from the next URL:
https://docs.python.org/3.5/download.html

Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180309/1e2d2236/attachment.html>

From report at bugs.python.org  Sun Mar 11 12:02:46 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 11 Mar 2018 16:02:46 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1520784166.83.0.467229070634.issue32996@psf.upfronthosting.co.za>


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

The most breaking change in 3.7 (according to the statistics of GitHub issues) is making async a keyword. But this change is even not mentioned in What's New.

----------

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

From report at bugs.python.org  Sun Mar 11 14:16:31 2018
From: report at bugs.python.org (Trey Hunner)
Date: Sun, 11 Mar 2018 18:16:31 +0000
Subject: [docs] [issue33049] itertools.count() confusingly mentions zip()
 and sequence numbers
Message-ID: <1520792191.75.0.467229070634.issue33049@psf.upfronthosting.co.za>


New submission from Trey Hunner <trey at truthful.technology>:

>From the itertools documentation: https://docs.python.org/3/library/itertools.html?highlight=itertools#itertools.count

> Also, used with zip() to add sequence numbers.

I'm not certain what the goal of the original sentence was, but I think it's unclear as currently written.

I assume this is what's meant:

my_sequence = [1, 2, 3, 4]
for i, item in zip(count(1), my_sequence):
    print(i, item)

This is a strange thing to note though because enumerate would be a better use here.

my_sequence = [1, 2, 3, 4]
for i, item in enumerate(my_sequence, start=1):
    print(i, item)

Maybe what is meant is that count can be used with a step while enumerate cannot?

my_sequence = [1, 2, 3, 4]
for i, item in zip(count(step=5), my_sequence):
    print(i, item)

If that's the case it seems like step should instead be mentioned there instead of "sequence numbers".

----------
assignee: docs at python
components: Documentation
messages: 313606
nosy: docs at python, trey
priority: normal
severity: normal
status: open
title: itertools.count() confusingly mentions zip() and sequence numbers
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/issue33049>
_______________________________________

From report at bugs.python.org  Sun Mar 11 14:17:26 2018
From: report at bugs.python.org (Timothy VanSlyke)
Date: Sun, 11 Mar 2018 18:17:26 +0000
Subject: [docs] [issue33050] Centralized documentation of assumptions made
 by C code
Message-ID: <1520792246.5.0.467229070634.issue33050@psf.upfronthosting.co.za>


New submission from Timothy VanSlyke <vanslyke.t at husky.neu.edu>:

It would be nice for those who write C extensions to have a resource that explicitly states what assumptions are made by the CPython implementation that are otherwise implementation-defined in standard C.  

For example, Python versions >= 3.6 require:
- That UCHAR_MAX is defined to be 255 (from Python.h)
- That fixed-width intXX_t and uintXX_t types are provided in stdint.h and inttypes.h (from PEP7)

These two requirements also pretty much guarantee that CHAR_BIT == 8.  These kinds of things are nice to know for anybody working with the C API; we can make the same assumptions in our own code without having hunt through the API docs or the CPython source tree every time something comes up.

>From what I've found, there isn't any component of the documentation that explicitly lists these assumptions in one place (I apologize if there is and I somehow missed it...).  Could this be addressed in the future?  

Thanks!

----------
assignee: docs at python
components: Documentation
messages: 313607
nosy: docs at python, tvanslyke
priority: normal
severity: normal
status: open
title: Centralized documentation of assumptions made by C code
versions: Python 3.6

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

From report at bugs.python.org  Sun Mar 11 14:37:59 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 11 Mar 2018 18:37:59 +0000
Subject: [docs] [issue33049] itertools.count() confusingly mentions zip()
 and sequence numbers
In-Reply-To: <1520792191.75.0.467229070634.issue33049@psf.upfronthosting.co.za>
Message-ID: <1520793479.01.0.467229070634.issue33049@psf.upfronthosting.co.za>


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

For example zip(my_sequence, count(1)).

----------
nosy: +rhettinger, serhiy.storchaka

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

From report at bugs.python.org  Sun Mar 11 15:28:39 2018
From: report at bugs.python.org (R. David Murray)
Date: Sun, 11 Mar 2018 19:28:39 +0000
Subject: [docs] [issue32971] Docs on unittest.TestCase.assertRaises() should
 clarify context manager details
In-Reply-To: <1519840682.18.0.467229070634.issue32971@psf.upfronthosting.co.za>
Message-ID: <1520796519.31.0.467229070634.issue32971@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

The implementation is literally that no non-keyword arguments other than the exception are given.  If any keyword arguments other than msg are given, you get a warning. To say just "no callable" would be about as confusing as the 'and possibly' given the documented prototype, since in fact any non-keyword argument will be assumed to be the callable. So the text is correct as written, and I'm not sure how one would make it clearer and still be technically correct.  But further suggestions are welcome.

----------
nosy: +r.david.murray

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

From report at bugs.python.org  Sun Mar 11 16:26:27 2018
From: report at bugs.python.org (bbayles)
Date: Sun, 11 Mar 2018 20:26:27 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1520799987.03.0.467229070634.issue32996@psf.upfronthosting.co.za>


bbayles <bbayles at gmail.com> added the comment:

Two things I'm familiar with that should probably be mentioned in the Library updates:

* bpo-32102: New argument capture_output for subprocess.run
* bpo-21417: Added support for setting the compression level for zipfile.ZipFile.

----------
nosy: +bbayles

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

From report at bugs.python.org  Sun Mar 11 17:29:49 2018
From: report at bugs.python.org (Ned Deily)
Date: Sun, 11 Mar 2018 21:29:49 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1520803789.91.0.467229070634.issue32996@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

Thanks for the comments here.  As noted by Yury in PR 5983:  "Looks good. Keep in mind that @elprans and I will edit what's new (as we did for 3.5 & 3.6) closer to 3.7 release."

----------
nosy: +Elvis.Pranskevichus, yselivanov

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

From report at bugs.python.org  Sun Mar 11 18:55:17 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 11 Mar 2018 22:55:17 +0000
Subject: [docs] [issue18802] ipaddress documentation errors
In-Reply-To: <1377118857.87.0.169407991036.issue18802@psf.upfronthosting.co.za>
Message-ID: <1520808917.88.0.714561066657.issue18802@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


----------
pull_requests: +5844

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

From report at bugs.python.org  Sun Mar 11 18:56:14 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 11 Mar 2018 22:56:14 +0000
Subject: [docs] [issue18802] ipaddress documentation errors
In-Reply-To: <1377118857.87.0.169407991036.issue18802@psf.upfronthosting.co.za>
Message-ID: <1520808974.52.0.467229070634.issue18802@psf.upfronthosting.co.za>


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

I've made a PR for Berker's patch.

----------

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

From report at bugs.python.org  Mon Mar 12 01:07:35 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 12 Mar 2018 05:07:35 +0000
Subject: [docs] [issue33049] itertools.count() confusingly mentions zip()
 and sequence numbers
In-Reply-To: <1520792191.75.0.467229070634.issue33049@psf.upfronthosting.co.za>
Message-ID: <1520831255.74.0.467229070634.issue33049@psf.upfronthosting.co.za>


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

> This is a strange thing to note though because enumerate 
> would be a better use here.

IIRC, the wording predates the addition of enumerate() and before enumerate() grew a *start* argument.  That said, enumerate() just addresses care the most common case.  It is still worth mentioning that count() is still useful for the general case of adding sequence numbers to data streams woven together by zip() -- like the way auto-increment is used in SQL:

    from time import ctime

    def timestamp():
        while True:
            yield ctime()
           
    def user_request():
        while True:
            yield input()
     
    logged_requests = zip(user_request(), count(1), timestamp(), cycle(available_servers))

> it seems like step should instead be mentioned there
> instead of "sequence numbers".

The *step* argument was a late addition to the API and isn't used much in practice.  When it is used, its meaning and use case tend to be self-evident (i.e. counting 60 seconds at a time, or counting backwards), so it doesn't warrant further elaboration.

The sentence as-is is imperfect (it makes you wonder why not just use enumerate) but it seems better than either saying less by not mentioning the use case or getting too wordy which would place too much emphasis on use cases less common that those served by enumerate().  So, my preference is to leave the sentence as it stands.  The intent of the two sentences mentioning map() and zip() was to hint at the possibilities while still keeping the paragraph primary focused on what count() actually does.

----------
assignee: docs at python -> rhettinger
priority: normal -> low

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

From report at bugs.python.org  Mon Mar 12 02:29:39 2018
From: report at bugs.python.org (Benjamin Peterson)
Date: Mon, 12 Mar 2018 06:29:39 +0000
Subject: [docs] [issue33050] Centralized documentation of assumptions made
 by C code
In-Reply-To: <1520792246.5.0.467229070634.issue33050@psf.upfronthosting.co.za>
Message-ID: <1520836179.51.0.467229070634.issue33050@psf.upfronthosting.co.za>


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

In general, we try to confine ourselves to C99 aside from widely supported extensions like intXX_t (no one wants to go around writing int_least32_t).

----------
nosy: +benjamin.peterson

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

From report at bugs.python.org  Mon Mar 12 09:03:01 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 12 Mar 2018 13:03:01 +0000
Subject: [docs] [issue26701] Documentation for int constructor mentions
 __int__ but not __trunc__
In-Reply-To: <1459933312.1.0.479151701513.issue26701@psf.upfronthosting.co.za>
Message-ID: <1520859781.41.0.467229070634.issue26701@psf.upfronthosting.co.za>


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

With both Eric's and Serhiy's updates merged, and issue 33039 broken out for the __index__ oddities, this is resolved now.

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

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

From report at bugs.python.org  Mon Mar 12 13:47:25 2018
From: report at bugs.python.org (Sanyam Khurana)
Date: Mon, 12 Mar 2018 17:47:25 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520876845.54.0.714561066657.issue33014@psf.upfronthosting.co.za>


Change by Sanyam Khurana <sanyam.khurana01 at gmail.com>:


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

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

From report at bugs.python.org  Mon Mar 12 13:49:14 2018
From: report at bugs.python.org (Sanyam Khurana)
Date: Mon, 12 Mar 2018 17:49:14 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520876954.78.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

Carol, Yes, I've raised a PR.

Currently, I've updated the docs for `str.isidentifier` clarifying the usage of `keyword.iskeyword`

For updating the docstring of `keyword.iskeyword`, I saw that `Lib/Keyword.py` defines this on line 55: `iskeyword = frozenset(kwlist).__contains__`

The docstring of the file says that it is automatically generated from `graminit.c`. I observed that file and have no clue on how to proceed to have the doc string updated. Can someone provide me a pointer on this please?

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

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

From report at bugs.python.org  Mon Mar 12 14:16:25 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 12 Mar 2018 18:16:25 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520878585.69.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

The change that will add a docstring to keyword.iskeyword() inevitable will have a negative performance effect. Is it worth it?

----------
nosy: +rhettinger, serhiy.storchaka

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

From report at bugs.python.org  Mon Mar 12 15:30:02 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 12 Mar 2018 19:30:02 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520883002.04.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

As I posted above, keywork.iskeyword already has a bizarrely incorrect docstring, so how can there be a performance impact? And why single out such a rarely used function?

----------

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

From report at bugs.python.org  Mon Mar 12 16:01:50 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 12 Mar 2018 20:01:50 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520884910.71.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

For changing a docstring we have to change the implementation of iskeyword(). It seems to me that the current implementation is the fastest, and any other implementation will be a tiny bit slower.

I just wanted to say that this enhancement has a non-zero cost.

----------

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

From report at bugs.python.org  Mon Mar 12 16:25:02 2018
From: report at bugs.python.org (Carol Willing)
Date: Mon, 12 Mar 2018 20:25:02 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520886302.7.0.467229070634.issue33014@psf.upfronthosting.co.za>


Carol Willing <willingc at gmail.com> added the comment:

I've made an additional suggestion on the open PR to add an example to the `.rst` doc that better clarifies the differences and usage of `iskeyword` and `isidentifier`.

Perhaps making that addition and skipping the updates to the C source code would be a reasonable step forward. While perhaps not ideal, it seems a reasonable compromise to provide more helpful documentation without any potential performance impact or regression.

----------

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

From report at bugs.python.org  Mon Mar 12 16:38:13 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 12 Mar 2018 20:38:13 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520887093.53.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

Too bad we couldn't do:

iskeyword = frozenset(kwlist).__contains__
iskeyword.__doc__ = 'Test whether a string is a reserved identifier.'

But I'm sure there are reasons for this:
AttributeError: attribute '__doc__' of 'builtin_function_or_method' objects is not writable

----------
nosy: +csabella

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

From report at bugs.python.org  Mon Mar 12 18:34:03 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 12 Mar 2018 22:34:03 +0000
Subject: [docs] [issue21018] [patch] added missing documentation about
 escaping characters for configparser
In-Reply-To: <1395464420.76.0.68706986346.issue21018@psf.upfronthosting.co.za>
Message-ID: <1520894042.94.0.467229070634.issue21018@psf.upfronthosting.co.za>


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

@Arun.Persaud, would you be interested in converting your patch to a Github pull request?

----------
nosy: +csabella
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Mon Mar 12 19:30:13 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 12 Mar 2018 23:30:13 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1520897413.28.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

Separate PRs for doc and code changes will be needed anyway if the code change is restricted to 3.8.

To me, changing keyword.iskeyword.__doc__ from the irrelevant Python tautology 'x.__contains__(y) <==> y in x.' to something that says what the function does, as docstrings should,  is a bug fix, not an enhancement.  Hence a slight slowdown is not a concern to me.  I see 4 possible types of fixes.

1. Write a python function with docstring.  3.8 only as it changes type(iskeyword).

def iskeyword(s):
    "Return true if s is a Python keyword."
    return s in kwlist

2. Change the aberrant set/frozenset.__contains__.__doc__ so it makes some sense as a docstring for a bound method (as with list and dict).  
  list/tuple.__contains__.__doc__ is 'Return key in self.'
  dict.__contains__.__doc__ is 'True if the dictionary has the specified key, else False.'

I would copy the dict __contains__ docstring, with 'Return' prefixed, to set and frozenset, with the obvious substitution.  I don't know about backporting this.

3. Make bound_method docstrings writable, like with Python function docstrings (3.8 only).  Then we could use Cheryl's suggestion.  Or add a function bounddoc(bound_method, docstring) that can change a bound_method's docsting.

CPython uses 2 types for built-in methods bound to an instance.  The choice is not consistent within a class or across classes for a particular method.
  builtin_function_or_method ([].append, frozenset().__contains__)
  method-wrapper ([].__contains__)
Python classes result in 'bound method'.  All 3 copy the docstring of the instance method.  (For Python classes, one can temporarily change the method docstring before creating a new bound method.)

4. Add makebound(method, instance, docstring) that creates a bound method (of the appropriate type) but with the passed docstring (3.8 only)

3 or 4 would allow any public bound method to have a custom docstring.

----------

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

From report at bugs.python.org  Mon Mar 12 21:23:24 2018
From: report at bugs.python.org (Ned Deily)
Date: Tue, 13 Mar 2018 01:23:24 +0000
Subject: [docs] [issue29719] "Date" of what's new is confusing
In-Reply-To: <1488627745.64.0.63277330553.issue29719@psf.upfronthosting.co.za>
Message-ID: <1520904204.04.0.467229070634.issue29719@psf.upfronthosting.co.za>


Ned Deily <nad at python.org> added the comment:

> I believe this can be closed as 'fixed'?

Well, it *was* fixed!  But then I reintroduced the boilerplate when I created the 3.7 and 3.8 whatsnew files - now fixed.  Thanks for the reminder!

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
versions: +Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue Mar 13 10:21:27 2018
From: report at bugs.python.org (Paul Ganssle)
Date: Tue, 13 Mar 2018 14:21:27 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
Message-ID: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>


New submission from Paul Ganssle <p.ganssle at gmail.com>:

I've been asked to post this by @brainwave (who is having some trouble getting an account on bpo due to technical difficulties).

Per twine's github issue 311 ( https://github.com/pypa/twine/issues/311 ), it seems that distutil's docs Update setuptools and distutils docs, e.g., https://docs.python.org/3.6/distutils/packageindex.html#the-upload-command should be clarified to indicate that PyPI does not require register anymore, although other package indexes might.

----------
assignee: docs at python
components: Distutils, Documentation
messages: 313749
nosy: docs at python, dstufft, eric.araujo, p-ganssle
priority: normal
severity: normal
status: open
title: Document that PyPI no longer requires 'register'
type: enhancement

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

From report at bugs.python.org  Tue Mar 13 10:27:59 2018
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 13 Mar 2018 14:27:59 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1520951279.14.0.714561066657.issue33071@psf.upfronthosting.co.za>


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


----------
components:  -Distutils
keywords: +easy
versions: +Python 2.7, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Tue Mar 13 19:02:02 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 13 Mar 2018 23:02: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: <1520982122.53.0.467229070634.issue27910@psf.upfronthosting.co.za>


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

Tomas,

Would you be willing to make a Github pull request with your patch?  Thanks.

----------
nosy: +csabella
stage: commit review -> needs patch
versions: +Python 3.8 -Python 3.5, Python 3.6

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

From report at bugs.python.org  Tue Mar 13 19:09:41 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 13 Mar 2018 23:09:41 +0000
Subject: [docs] [issue27902] pstats.Stats: strip_dirs() method cannot handle
 file paths from different OS
In-Reply-To: <1472590175.77.0.992836532809.issue27902@psf.upfronthosting.co.za>
Message-ID: <1520982581.65.0.714561066657.issue27902@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


----------
keywords: +easy
versions: +Python 3.7, Python 3.8 -Python 3.5, Python 3.6

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

From report at bugs.python.org  Tue Mar 13 19:47:12 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 13 Mar 2018 23:47:12 +0000
Subject: [docs] [issue28612] str.translate needs a mapping example
In-Reply-To: <1478278954.92.0.793705359912.issue28612@psf.upfronthosting.co.za>
Message-ID: <1520984832.08.0.467229070634.issue28612@psf.upfronthosting.co.za>


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

IDLE just added similar functionality to pyparse (issue 32940) using:

    class ParseMap(dict):
        def __missing__(self, key):
            return 120 # ord('x')

    # Map all ascii to 120 to avoid __missing__ call, then replace some.
    trans = ParseMap.fromkeys(range(128), 120)
    trans.update((ord(c), ord('(')) for c in "({[")  # open brackets => '(';
    trans.update((ord(c), ord(')')) for c in ")}]")  # close brackets => ')'.
    trans.update((ord(c), ord(c)) for c in "\"'\\\n#") # Keep these.

    code = code.translate(trans)

Of course, all that is probably too much for a docs example, but it uses a mapping without the side effect of defaultdict.  I wonder if defining the dict subclass with __missing__ and then the example of keeping only lowercase letters would work for the docs?

----------
nosy: +csabella

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

From report at bugs.python.org  Tue Mar 13 20:40:12 2018
From: report at bugs.python.org (Sumana Harihareswara)
Date: Wed, 14 Mar 2018 00:40:12 +0000
Subject: [docs] [issue33071] Document that PyPI no longer requires 'register'
In-Reply-To: <1520950887.05.0.467229070634.issue33071@psf.upfronthosting.co.za>
Message-ID: <1520988012.13.0.714561066657.issue33071@psf.upfronthosting.co.za>


Change by Sumana Harihareswara <sh at changeset.nyc>:


----------
nosy: +sumanah

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

From hunt.robertj at gmail.com  Mon Mar 12 05:14:27 2018
From: hunt.robertj at gmail.com (Robert Hunt)
Date: Mon, 12 Mar 2018 22:14:27 +1300
Subject: [docs] Small html fault
Message-ID: <c5815e84-7130-f3e3-bb95-10ba35b3861f@gmail.com>

https://docs.python.org/3.7/library/tkinter.ttk.html#tkinter.ttk.Spinbox 
goes to the wrong spot on the page. (It takes you to 26.2.5.3 instead of 
26.2.5.)

Robert.


From report at bugs.python.org  Wed Mar 14 14:03:00 2018
From: report at bugs.python.org (Tomas Orsava)
Date: Wed, 14 Mar 2018 18:03: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: <1521050580.75.0.714561066657.issue27910@psf.upfronthosting.co.za>


Change by Tomas Orsava <tomas.n at orsava.cz>:


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

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

From report at bugs.python.org  Wed Mar 14 14:03:55 2018
From: report at bugs.python.org (Tomas Orsava)
Date: Wed, 14 Mar 2018 18:03:55 +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: <1521050635.46.0.467229070634.issue27910@psf.upfronthosting.co.za>


Tomas Orsava <tomas.n at orsava.cz> added the comment:

Hey Cheryl,
here is the pull request: https://github.com/python/cpython/pull/6116

----------

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

From report at bugs.python.org  Wed Mar 14 20:33:15 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 15 Mar 2018 00:33:15 +0000
Subject: [docs] [issue12731] python lib re uses obsolete sense of \w in full
 violation of UTS#18 RL1.2a
In-Reply-To: <1313090311.62.0.0473644856742.issue12731@psf.upfronthosting.co.za>
Message-ID: <1521073995.86.0.467229070634.issue12731@psf.upfronthosting.co.za>


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

Whatever I may have said before, I favor supporting the Unicode standard for \w, which is related to the standard for identifiers.

This is one of 2 issues about \w being defined too narrowly.  I am somewhat arbitrarily closing #1693050 as a duplicate of this (fewer digits ;-).

There are 3 issues about tokenize.tokenize failing on valid identifiers, defined as \w sequences whose first char is an identifier itself (and therefore a start char).  In msg313814 of #32987, Serhiy indicates which start and continue identifier characters are matched by \W for re and regex.  I am leaving #24194 open as the tokenizer name issue.

----------
stage: needs patch -> test needed
versions: +Python 3.6, Python 3.7, Python 3.8 -Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Thu Mar 15 04:42:38 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 15 Mar 2018 08:42:38 +0000
Subject: [docs] [issue32822] finally block doesn't re-raise exception if
 return statement exists inside
In-Reply-To: <1518387497.4.0.467229070634.issue32822@psf.upfronthosting.co.za>
Message-ID: <1521103358.39.0.714561066657.issue32822@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation -Interpreter Core
nosy: +docs at python
status: pending -> open
type: behavior -> enhancement
versions: +Python 2.7, Python 3.6, Python 3.7, Python 3.8 -Python 3.4

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

From report at bugs.python.org  Thu Mar 15 06:20:38 2018
From: report at bugs.python.org (Simon Lipp)
Date: Thu, 15 Mar 2018 10:20:38 +0000
Subject: [docs] [issue33079] subprocess: document the interaction between
 subprocess.Popen and os.set_inheritable
Message-ID: <1521109238.05.0.467229070634.issue33079@psf.upfronthosting.co.za>


New submission from Simon Lipp <keejaisi at hwold.net>:

>From current `os` documentation:

> A file descriptor has an ?inheritable? flag which indicates if the file descriptor can be inherited by child processes

from current `subprocess` documentation:

> If close_fds is true, all file descriptors except 0, 1 and 2 will be closed before the child process is executed

It would be helpful to explicitly specify that subprocess.Popen does not takes into account the inheritable flag ; thas is, that inheritable fds will still be closed with open_fds = False, and that non-inheritable fds will still be kept with open_fds = True.

----------
assignee: docs at python
components: Documentation
messages: 313868
nosy: docs at python, sloonz
priority: normal
severity: normal
status: open
title: subprocess: document the interaction between subprocess.Popen and os.set_inheritable
versions: Python 3.6

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

From magnus2loberg at gmail.com  Thu Mar 15 04:31:57 2018
From: magnus2loberg at gmail.com (=?UTF-8?B?TWFnbnVzIEJqw7hybnNlbiBMw7hiZXJn?=)
Date: Thu, 15 Mar 2018 09:31:57 +0100
Subject: [docs] download error
Message-ID: <CAN14nHw45FgA4Ap0-nSxsGGszVhgcnMXfYAUGF00UZQLgb8Vtw@mail.gmail.com>

on this page

https://docs.python.org/3.5/download.html

some links give 404 error

kind regards
Magnus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180315/84cadedd/attachment.html>

From report at bugs.python.org  Thu Mar 15 13:50:06 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 15 Mar 2018 17:50:06 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1521136206.08.0.714561066657.issue28677@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


----------
keywords: +easy
stage:  -> needs patch
versions: +Python 3.7, Python 3.8

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

From report at bugs.python.org  Thu Mar 15 14:50:50 2018
From: report at bugs.python.org (Chad)
Date: Thu, 15 Mar 2018 18:50:50 +0000
Subject: [docs] [issue33082] multiprocessing docs bury very important
 'callback=' args
Message-ID: <1521139850.07.0.467229070634.issue33082@psf.upfronthosting.co.za>


New submission from Chad <millchad at amazon.com>:

Callbacks are really important in multiprocessing. Doc writer almost ignores them.

----------
assignee: docs at python
components: Documentation
messages: 313905
nosy: chadmiller-amzn, docs at python
priority: normal
severity: normal
status: open
title: multiprocessing docs bury very important 'callback=' args
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/issue33082>
_______________________________________

From report at bugs.python.org  Thu Mar 15 14:51:31 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 15 Mar 2018 18:51:31 +0000
Subject: [docs] [issue33082] multiprocessing docs bury very important
 'callback=' args
In-Reply-To: <1521139850.07.0.467229070634.issue33082@psf.upfronthosting.co.za>
Message-ID: <1521139891.11.0.714561066657.issue33082@psf.upfronthosting.co.za>


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


----------
nosy: +davin, pitrou
versions:  -Python 3.4, Python 3.5

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

From report at bugs.python.org  Thu Mar 15 14:55:08 2018
From: report at bugs.python.org (Chad)
Date: Thu, 15 Mar 2018 18:55:08 +0000
Subject: [docs] [issue33082] multiprocessing docs bury very important
 'callback=' args
In-Reply-To: <1521139850.07.0.467229070634.issue33082@psf.upfronthosting.co.za>
Message-ID: <1521140108.5.0.467229070634.issue33082@psf.upfronthosting.co.za>


Chad <millchad at amazon.com> added the comment:

https://github.com/chadmiller-amzn/cpython/pull/1

(Putting that in "GitHub PR" field says "Edit Error: Unknown PR format, acceptable formats are: full github URL, #pr_number, pr_number")

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

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

From report at bugs.python.org  Thu Mar 15 15:14:01 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 15 Mar 2018 19:14:01 +0000
Subject: [docs] [issue21611] int() docstring - unclear what number is
In-Reply-To: <1401440335.97.0.776400017562.issue21611@psf.upfronthosting.co.za>
Message-ID: <1521141241.44.0.467229070634.issue21611@psf.upfronthosting.co.za>


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

Is this superseded by issue 26701?

----------
nosy: +csabella

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

From report at bugs.python.org  Thu Mar 15 16:23:14 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 15 Mar 2018 20:23:14 +0000
Subject: [docs] [issue25735] math.factorial doc should mention integer
 return type
In-Reply-To: <1448480671.49.0.139605050425.issue25735@psf.upfronthosting.co.za>
Message-ID: <1521145394.11.0.467229070634.issue25735@psf.upfronthosting.co.za>


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

Should the documentation patch for this be converted to a PR or does this need to change to a bug issue to address Mark's concerns?

Thanks!

----------
nosy: +csabella
stage:  -> needs patch
versions: +Python 3.7, Python 3.8 -Python 3.5

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

From report at bugs.python.org  Thu Mar 15 16:27:04 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 15 Mar 2018 20:27:04 +0000
Subject: [docs] [issue25735] math.factorial doc should mention integer
 return type
In-Reply-To: <1448480671.49.0.139605050425.issue25735@psf.upfronthosting.co.za>
Message-ID: <1521145624.54.0.467229070634.issue25735@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

> Should the documentation patch for this be converted to a PR

I think so, yes. How about we open a new issue for the factorial(Decimal(...)) behaviour, and keep this one focused on the original reported issue?

----------

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

From report at bugs.python.org  Thu Mar 15 16:34:02 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 15 Mar 2018 20:34:02 +0000
Subject: [docs] [issue25735] math.factorial doc should mention integer
 return type
In-Reply-To: <1448480671.49.0.139605050425.issue25735@psf.upfronthosting.co.za>
Message-ID: <1521146042.66.0.467229070634.issue25735@psf.upfronthosting.co.za>


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

Sounds good.  Thanks, Mark.

@mine0901, would you like to open a Github pull request for your patch?  Thanks!

----------

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

From report at bugs.python.org  Thu Mar 15 16:39:08 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 15 Mar 2018 20:39:08 +0000
Subject: [docs] [issue25735] math.factorial doc should mention integer
 return type
In-Reply-To: <1448480671.49.0.139605050425.issue25735@psf.upfronthosting.co.za>
Message-ID: <1521146348.85.0.467229070634.issue25735@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

I opened #33083, and copied the nosy list from this issue across.

----------

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

From report at bugs.python.org  Thu Mar 15 16:46:10 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 15 Mar 2018 20:46:10 +0000
Subject: [docs] [issue33082] multiprocessing docs bury very important
 'callback=' args
In-Reply-To: <1521139850.07.0.467229070634.issue33082@psf.upfronthosting.co.za>
Message-ID: <1521146770.25.0.467229070634.issue33082@psf.upfronthosting.co.za>


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

Can you make your PR in python/cpython GitHub repo, instead of your own fork?

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

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

From report at bugs.python.org  Thu Mar 15 16:46:42 2018
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 15 Mar 2018 20:46:42 +0000
Subject: [docs] [issue33082] multiprocessing docs bury very important
 'callback=' args
In-Reply-To: <1521139850.07.0.467229070634.issue33082@psf.upfronthosting.co.za>
Message-ID: <1521146802.39.0.714561066657.issue33082@psf.upfronthosting.co.za>


Change by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
versions:  -Python 3.4, Python 3.5

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

From report at bugs.python.org  Thu Mar 15 17:10:27 2018
From: report at bugs.python.org (Chad)
Date: Thu, 15 Mar 2018 21:10:27 +0000
Subject: [docs] [issue33082] multiprocessing docs bury very important
 'callback=' args
In-Reply-To: <1521139850.07.0.467229070634.issue33082@psf.upfronthosting.co.za>
Message-ID: <1521148227.14.0.714561066657.issue33082@psf.upfronthosting.co.za>


Change by Chad <millchad at amazon.com>:


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

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

From report at bugs.python.org  Thu Mar 15 22:18:16 2018
From: report at bugs.python.org (Ned Deily)
Date: Fri, 16 Mar 2018 02:18:16 +0000
Subject: [docs] [issue33079] subprocess: document the interaction between
 subprocess.Popen and os.set_inheritable
In-Reply-To: <1521109238.05.0.467229070634.issue33079@psf.upfronthosting.co.za>
Message-ID: <1521166696.5.0.714561066657.issue33079@psf.upfronthosting.co.za>


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


----------
nosy: +gregory.p.smith

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

From report at bugs.python.org  Fri Mar 16 04:52:00 2018
From: report at bugs.python.org (Dmitry Andreychuk)
Date: Fri, 16 Mar 2018 08:52:00 +0000
Subject: [docs] [issue21611] int() docstring - unclear what number is
In-Reply-To: <1401440335.97.0.776400017562.issue21611@psf.upfronthosting.co.za>
Message-ID: <1521190319.8.0.467229070634.issue21611@psf.upfronthosting.co.za>


Dmitry Andreychuk <and.dmitry at gmail.com> added the comment:

I created this issue almost 4 years ago. Looking at it now, I think that I was asking too much of that docstring. I believe it's current version quite sufficient.

I would close the issue, but I'm not sure if it's up to me to decide.

----------

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

From report at bugs.python.org  Fri Mar 16 06:56:45 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 16 Mar 2018 10:56:45 +0000
Subject: [docs] [issue33077] typing: Unexpected result with value of
 instance of class inherited from typing.NamedTuple
In-Reply-To: <1521066290.44.0.467229070634.issue33077@psf.upfronthosting.co.za>
Message-ID: <1521197805.56.0.467229070634.issue33077@psf.upfronthosting.co.za>


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

> Apart from the fact that it's too late, if you had to do it over again,
could it be done as a class decorator?

Yes, this could be done as a decorator which would replace the original class with a named tuple after inspecting `__annotations__` and `__dict__`. (But again, the name would be different, since `@NamedTuple` looks weird to me.)

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> needs patch

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

From report at bugs.python.org  Fri Mar 16 07:24:53 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Fri, 16 Mar 2018 11:24:53 +0000
Subject: [docs] [issue21611] int() docstring - unclear what number is
In-Reply-To: <1401440335.97.0.776400017562.issue21611@psf.upfronthosting.co.za>
Message-ID: <1521199493.95.0.714561066657.issue21611@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Documentation for int constructor mentions __int__ but not __trunc__

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

From report at bugs.python.org  Fri Mar 16 12:42:58 2018
From: report at bugs.python.org (Arun Persaud)
Date: Fri, 16 Mar 2018 16:42:58 +0000
Subject: [docs] [issue21018] [patch] added missing documentation about
 escaping characters for configparser
In-Reply-To: <1520894042.94.0.467229070634.issue21018@psf.upfronthosting.co.za>
Message-ID: <be2fbfe7-aaf4-8789-16fb-4524df47a200@gmail.com>


Arun Persaud <arun.persaud at gmail.com> added the comment:

> @Arun.Persaud, would you be interested in converting your patch to a Github pull request?

sure, I'll give it a try.

Arun

----------

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

From report at bugs.python.org  Fri Mar 16 12:45:53 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 16 Mar 2018 16:45:53 +0000
Subject: [docs] [issue33077] typing: Unexpected result with value of
 instance of class inherited from typing.NamedTuple
In-Reply-To: <1521066290.44.0.467229070634.issue33077@psf.upfronthosting.co.za>
Message-ID: <1521218753.61.0.467229070634.issue33077@psf.upfronthosting.co.za>


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

Would it be worthwhile to show an example of a subclass that overrides or extends  __new__?   

Elsewhere in Python, the usual technique for changing method defaults is for a subclass to override or extend the method in question.  

    class A:
        def somemeth(self, value: bool = True):
            print(value)

    class B(A):
        def somemeth(self, value: bool = False):
            super().somemeth(value)

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

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

From report at bugs.python.org  Fri Mar 16 14:56:03 2018
From: report at bugs.python.org (David Rebbe)
Date: Fri, 16 Mar 2018 18:56:03 +0000
Subject: [docs] [issue32822] finally block doesn't re-raise exception if
 return statement exists inside
In-Reply-To: <1518387497.4.0.467229070634.issue32822@psf.upfronthosting.co.za>
Message-ID: <1521226563.5.0.467229070634.issue32822@psf.upfronthosting.co.za>


David Rebbe <drebbe at intrepidcs.com> added the comment:

I'll have to look into this as I have yet to commit anything but I'll put it on my list of things to do.

----------

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

From report at bugs.python.org  Fri Mar 16 15:27:09 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 16 Mar 2018 19:27:09 +0000
Subject: [docs] [issue30940] Documentation for round() is incorrect.
In-Reply-To: <1500223918.38.0.72996478594.issue30940@psf.upfronthosting.co.za>
Message-ID: <1521228429.87.0.714561066657.issue30940@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Mar 16 17:55:23 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 16 Mar 2018 21:55:23 +0000
Subject: [docs] [issue33049] itertools.count() confusingly mentions zip()
 and sequence numbers
In-Reply-To: <1520792191.75.0.467229070634.issue33049@psf.upfronthosting.co.za>
Message-ID: <1521237323.05.0.467229070634.issue33049@psf.upfronthosting.co.za>


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

I think 'sequential numbers' would be slightly better than 'sequence numbers'.  To be, it better includes stepped and descending sequences.  (Enough better that I would be willing to do the PR and merge.)  Otherwise, I think leave it alone.

----------
nosy: +terry.reedy
versions:  -Python 3.4, Python 3.5

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

From report at bugs.python.org  Fri Mar 16 18:01:24 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 16 Mar 2018 22:01:24 +0000
Subject: [docs] [issue33049] itertools.count() confusingly mentions zip()
 and sequence numbers
In-Reply-To: <1520792191.75.0.467229070634.issue33049@psf.upfronthosting.co.za>
Message-ID: <1521237684.25.0.467229070634.issue33049@psf.upfronthosting.co.za>


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

Since I don't like "sequential numbers", let's opt for the "leave it alone" option :-)

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Mar 17 01:41:29 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 17 Mar 2018 05:41:29 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1521265289.53.0.467229070634.issue32374@psf.upfronthosting.co.za>


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


New changeset c2b0b12d1a137ada1023ab7c10b8d9a0249d95f9 by Nick Coghlan (Marcel Plch) in branch 'master':
bpo-32374:  m_traverse may be called with m_state=NULL (GH-5140)
https://github.com/python/cpython/commit/c2b0b12d1a137ada1023ab7c10b8d9a0249d95f9


----------

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

From report at bugs.python.org  Sat Mar 17 01:41:48 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 17 Mar 2018 05:41:48 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1521265308.76.0.714561066657.issue32374@psf.upfronthosting.co.za>


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


----------
pull_requests: +5890

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

From report at bugs.python.org  Sat Mar 17 01:42:30 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 17 Mar 2018 05:42:30 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1521265350.83.0.714561066657.issue32374@psf.upfronthosting.co.za>


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


----------
pull_requests: +5891

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

From report at bugs.python.org  Sat Mar 17 02:03:58 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 17 Mar 2018 06:03:58 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1521266638.78.0.467229070634.issue32374@psf.upfronthosting.co.za>


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


New changeset 136905fffd5f77395f80e3409630c11756b5469c by Miss Islington (bot) in branch '3.7':
bpo-32374:  m_traverse may be called with m_state=NULL (GH-5140)
https://github.com/python/cpython/commit/136905fffd5f77395f80e3409630c11756b5469c


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

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

From report at bugs.python.org  Sat Mar 17 02:29:32 2018
From: report at bugs.python.org (miss-islington)
Date: Sat, 17 Mar 2018 06:29:32 +0000
Subject: [docs] [issue32374] Document that m_traverse for multi-phase
 initialized modules can be called with m_state=NULL
In-Reply-To: <1513694438.46.0.213398074469.issue32374@psf.upfronthosting.co.za>
Message-ID: <1521268172.37.0.467229070634.issue32374@psf.upfronthosting.co.za>


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


New changeset 1da0479f687613a43620430616f4db87e2ed4423 by Miss Islington (bot) in branch '3.6':
bpo-32374:  m_traverse may be called with m_state=NULL (GH-5140)
https://github.com/python/cpython/commit/1da0479f687613a43620430616f4db87e2ed4423


----------

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

From nth10sd at gmail.com  Thu Mar 15 19:54:58 2018
From: nth10sd at gmail.com (Gary Kwong)
Date: Thu, 15 Mar 2018 16:54:58 -0700
Subject: [docs] None of the links work to download Python 3.5.5 documentation
Message-ID: <9130d320-e8a8-64ee-202e-02900b9e53e4@gmail.com>

Hi,

I tried all the links to different formats of the Python 3.5.5 
documentation, but none work.

https://docs.python.org/3.5/download.html

Even the .chm files are not available on the page that they're supposed 
to be available:

https://www.python.org/downloads/release/python-355/

I understand that binaries are no longer produced for Python 3.5.5, but 
surely documentation should still be generated?

(use case: I fly to places with intermittent connections, and will be 
shifting projects to be using Python 3.5.x and up as the minimum 
requirement)

Regards,

-- 
-Gary


From solal.pirelli at gmail.com  Thu Mar 15 11:15:15 2018
From: solal.pirelli at gmail.com (Solal Pirelli)
Date: Thu, 15 Mar 2018 16:15:15 +0100
Subject: [docs] Offline docs links not working for Python 3.5.5
Message-ID: <CAAWV9ri5GnnOts_E6ne0pVGro0MJebHDtj0H-SeuEoyL1NZCLw@mail.gmail.com>

Hi,

Quick bug report: None of the archive links referenced to by
https://docs.python.org/3.5/download.html work right now.
Manually changing the URLs to 3.5.4 works though.

Cheers,
Solal Pirelli
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180315/e1b69a64/attachment.html>

From report at bugs.python.org  Sat Mar 17 17:34:41 2018
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 17 Mar 2018 21:34:41 +0000
Subject: [docs] [issue21018] [patch] added missing documentation about
 escaping characters for configparser
In-Reply-To: <1395464420.76.0.68706986346.issue21018@psf.upfronthosting.co.za>
Message-ID: <1521322481.12.0.714561066657.issue21018@psf.upfronthosting.co.za>


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


----------
pull_requests: +5894

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

From report at bugs.python.org  Sat Mar 17 17:36:08 2018
From: report at bugs.python.org (Arun Persaud)
Date: Sat, 17 Mar 2018 21:36:08 +0000
Subject: [docs] [issue21018] [patch] added missing documentation about
 escaping characters for configparser
In-Reply-To: <be2fbfe7-aaf4-8789-16fb-4524df47a200@gmail.com>
Message-ID: <eb3eb99e-b899-31fa-2a77-eb45f8662537@gmail.com>


Arun Persaud <arun.persaud at gmail.com> added the comment:

created github PR #6137. Hope everything is in the correct format.

Arun

----------

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

From report at bugs.python.org  Sat Mar 17 23:32:22 2018
From: report at bugs.python.org (R. David Murray)
Date: Sun, 18 Mar 2018 03:32:22 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1521343942.35.0.467229070634.issue33014@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

For the original report that this issue was opened for:

   Use keyword.iskeyword() to test for reserved identifiers such as "def" and "class".

The obvious replacement is:

   Use the iskeyword() function from the keyword module to test for reserved identifiers such as "def" and "class".

----------
nosy: +r.david.murray

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

From report at bugs.python.org  Sun Mar 18 01:57:16 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 18 Mar 2018 05:57:16 +0000
Subject: [docs] [issue33095] Cross-reference isolated mode from relevant
 locations
Message-ID: <1521352636.34.0.467229070634.issue33095@psf.upfronthosting.co.za>


New submission from Nick Coghlan <ncoghlan at gmail.com>:

In https://bugs.python.org/issue33053#msg313966, jwilk noted that it isn't obvious from https://docs.python.org/3/using/cmdline.html#cmdoption-m how to keep the current directory from being added to `sys.path` when using the -m switch. The answer is to pass the `-I` switch as well (to activate isolated mode), but there's no cross reference to help readers discover that fact.

https://docs.python.org/3/using/cmdline.html#id2 is the main documentation for isolated mode, so the steps needed to close this issue are:

1. At least add a reference from the -m switch documentation to the -I switch documentation
2. Review the other parts of the `using` docs that describe how `sys.path` is initialised, and reference the -I switch documentation where relevant

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 314022
nosy: docs at python, jwilk, ncoghlan
priority: normal
severity: normal
stage: needs patch
status: open
title: Cross-reference isolated mode from relevant locations
type: enhancement
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Sun Mar 18 06:40:23 2018
From: report at bugs.python.org (Jakub Wilk)
Date: Sun, 18 Mar 2018 10:40:23 +0000
Subject: [docs] [issue33095] Cross-reference isolated mode from relevant
 locations
In-Reply-To: <1521352636.34.0.467229070634.issue33095@psf.upfronthosting.co.za>
Message-ID: <1521369623.04.0.714561066657.issue33095@psf.upfronthosting.co.za>


Change by Jakub Wilk <jwilk at jwilk.net>:


----------
nosy:  -jwilk

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

From alireza.jahanpary at ut.ac.ir  Sat Mar 17 11:24:44 2018
From: alireza.jahanpary at ut.ac.ir (alireza.jahanpary)
Date: Sat, 17 Mar 2018 18:54:44 +0330
Subject: [docs] docs.python
Message-ID: <d3b7c4a05987a83c559653abb38d7b91@ut.ac.ir>

heloo 

please send me documentation of python, i need it to solve my project,  

thanks a lot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180317/ce9731bc/attachment.html>

From hemanthps83 at gmail.com  Sat Mar 17 18:00:10 2018
From: hemanthps83 at gmail.com (Hemanth p s)
Date: Sun, 18 Mar 2018 03:30:10 +0530
Subject: [docs] Python3_Documentation.pdf
Message-ID: <CAL2rW3navpiD0XhZj_Ts6FJrEOKSiw6-QppMan2qpQ=N0=uzig@mail.gmail.com>

The python3 documentation(pdf format) could not be downloaded from the
website.
So is there anyother way I can get the python3 documentation pdf file?
If yes please do respond.

Hemanth P S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180318/d164b393/attachment.html>

From report at bugs.python.org  Mon Mar 19 12:21:06 2018
From: report at bugs.python.org (Eric Appelt)
Date: Mon, 19 Mar 2018 16:21:06 +0000
Subject: [docs] [issue33104] Documentation for EXTENDED_ARG in dis module is
 incorrect for >=3.6
Message-ID: <1521476466.68.0.467229070634.issue33104@psf.upfronthosting.co.za>


New submission from Eric Appelt <eric.appelt at gmail.com>:

The documentation for the EXTENDED_ARG instruction in the dis module documentation refers to the way the opcode worked before 3.6: https://docs.python.org/3.6/library/dis.html#opcode-EXTENDED_ARG

As I understand, since moving to 2-byte wordcode in 3.6, each EXTENDED_ARG effectively adds a byte to the argument of the next instruction and they can be chained to allow up to a 32-bit argument. The current documentation refers the 2-byte arguments from the older bytecode used in 3.5 and below.

I'm trying to think of a clear and concise wording for how it works now and will add a PR to fix this issue unless someone gets to it before me.

----------
assignee: docs at python
components: Documentation
messages: 314100
nosy: Eric Appelt, docs at python
priority: normal
severity: normal
status: open
title: Documentation for EXTENDED_ARG in dis module is incorrect for >=3.6
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Mar 19 12:27:26 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 19 Mar 2018 16:27:26 +0000
Subject: [docs] [issue33104] Documentation for EXTENDED_ARG in dis module is
 incorrect for >=3.6
In-Reply-To: <1521476466.68.0.467229070634.issue33104@psf.upfronthosting.co.za>
Message-ID: <1521476846.12.0.467229070634.issue33104@psf.upfronthosting.co.za>


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

Isn't this a duplicate of issue32625?

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

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

From report at bugs.python.org  Mon Mar 19 13:51:21 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 19 Mar 2018 17:51:21 +0000
Subject: [docs] [issue25433] whitespace in strip()/lstrip()/rstrip()
In-Reply-To: <1445170536.34.0.94220475409.issue25433@psf.upfronthosting.co.za>
Message-ID: <1521481881.64.0.714561066657.issue25433@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


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

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

From report at bugs.python.org  Mon Mar 19 14:08:00 2018
From: report at bugs.python.org (Eric Appelt)
Date: Mon, 19 Mar 2018 18:08:00 +0000
Subject: [docs] [issue32625] Update the dis module documentation to reflect
 switch to wordcode
In-Reply-To: <1516642902.05.0.467229070634.issue32625@psf.upfronthosting.co.za>
Message-ID: <1521482880.26.0.714561066657.issue32625@psf.upfronthosting.co.za>


Change by Eric Appelt <eric.appelt at gmail.com>:


----------
nosy: +Eric Appelt

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

From report at bugs.python.org  Mon Mar 19 14:09:55 2018
From: report at bugs.python.org (Eric Appelt)
Date: Mon, 19 Mar 2018 18:09:55 +0000
Subject: [docs] [issue33104] Documentation for EXTENDED_ARG in dis module is
 incorrect for >=3.6
In-Reply-To: <1521476466.68.0.467229070634.issue33104@psf.upfronthosting.co.za>
Message-ID: <1521482995.07.0.467229070634.issue33104@psf.upfronthosting.co.za>


Eric Appelt <eric.appelt at gmail.com> added the comment:

Yes, thanks. I failed to see the duplicate searching for open issues, closing.

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

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

From wangdi03 at ppdai.com  Tue Mar 20 05:31:06 2018
From: wangdi03 at ppdai.com (=?gb2312?B?zfW1zw==?=)
Date: Tue, 20 Mar 2018 09:31:06 +0000
Subject: [docs] a doc bug in itertools.islice
Message-ID: <SH2PR01MB218AAB3FFD3814A750DB4D6C8AB0@SH2PR01MB218.CHNPR01.prod.partner.outlook.cn>

Hi!
I found a bug in https://docs.python.org/3/library/itertools.html, where the argument should be ?seq, start, [stop, step].?which makes me puzzled for the example.
[cid:image001.png at 01D3C071.391FD020]
Thanks.
---------------------------------
Best regards?
Andy Wang


E-mail:   wangdi03 at ppdai.com
Website:  www.ppdai.com<http://www.ppdai.com>


********************************************************************************

?????????????????????????????????????????????????????????????????????????????????????????????????????????????

This E-mail and any attachments are confidential and intended solely for the addressees. If you receive this E-mail in error, please delete it and immediately notify the sender. If the reader of this E-mail is not the intended recipient, you are hereby notified that any unauthorized use, copying or dissemination is prohibited. Please delete this E-mail and all its attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180320/e992be7e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5170 bytes
Desc: image001.png
URL: <http://mail.python.org/pipermail/docs/attachments/20180320/e992be7e/attachment-0001.png>

From report at bugs.python.org  Tue Mar 20 15:45:29 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 20 Mar 2018 19:45:29 +0000
Subject: [docs] [issue33082] multiprocessing docs bury very important
 'callback=' args
In-Reply-To: <1521139850.07.0.467229070634.issue33082@psf.upfronthosting.co.za>
Message-ID: <1521575129.62.0.467229070634.issue33082@psf.upfronthosting.co.za>


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

I don't really agree that "callbacks are really important in multiprocessing" (I think I've hardly ever used them).  I agree with the other doc changes in the PR.

----------

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

From report at bugs.python.org  Tue Mar 20 16:20:53 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Tue, 20 Mar 2018 20:20:53 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1521577253.44.0.467229070634.issue27212@psf.upfronthosting.co.za>


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

Hi Nofar,

Are you still interested in working on this issue?  Thanks!

----------
nosy: +csabella

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

From report at bugs.python.org  Tue Mar 20 18:04:41 2018
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Tue, 20 Mar 2018 22:04:41 +0000
Subject: [docs] [issue33077] typing: Unexpected result with value of
 instance of class inherited from typing.NamedTuple
In-Reply-To: <1521066290.44.0.467229070634.issue33077@psf.upfronthosting.co.za>
Message-ID: <1521583480.99.0.467229070634.issue33077@psf.upfronthosting.co.za>


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

> Would it be worthwhile to show an example of a subclass that overrides or extends  __new__?

I think yes. I would actually add few examples what could (and maybe also couldn't) be done with named tuples.

----------

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

From report at bugs.python.org  Tue Mar 20 20:09:18 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 21 Mar 2018 00:09:18 +0000
Subject: [docs] [issue18802] ipaddress documentation errors
In-Reply-To: <1377118857.87.0.169407991036.issue18802@psf.upfronthosting.co.za>
Message-ID: <1521590958.43.0.467229070634.issue18802@psf.upfronthosting.co.za>


Xiang Zhang <angwerzx at 126.com> added the comment:


New changeset 5609b78392d59c7362ef8aa5c4a4529325f01f27 by Xiang Zhang (Cheryl Sabella) in branch 'master':
 bpo-18802: Add more details to ipaddress documentation (GH-6083)
https://github.com/python/cpython/commit/5609b78392d59c7362ef8aa5c4a4529325f01f27


----------

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

From report at bugs.python.org  Tue Mar 20 20:10:42 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 21 Mar 2018 00:10:42 +0000
Subject: [docs] [issue18802] ipaddress documentation errors
In-Reply-To: <1377118857.87.0.169407991036.issue18802@psf.upfronthosting.co.za>
Message-ID: <1521591042.87.0.714561066657.issue18802@psf.upfronthosting.co.za>


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


----------
pull_requests: +5921

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

From report at bugs.python.org  Tue Mar 20 20:11:26 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 21 Mar 2018 00:11:26 +0000
Subject: [docs] [issue18802] ipaddress documentation errors
In-Reply-To: <1377118857.87.0.169407991036.issue18802@psf.upfronthosting.co.za>
Message-ID: <1521591086.75.0.714561066657.issue18802@psf.upfronthosting.co.za>


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


----------
pull_requests: +5922

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

From report at bugs.python.org  Tue Mar 20 20:30:45 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 21 Mar 2018 00:30:45 +0000
Subject: [docs] [issue18802] ipaddress documentation errors
In-Reply-To: <1377118857.87.0.169407991036.issue18802@psf.upfronthosting.co.za>
Message-ID: <1521592245.69.0.467229070634.issue18802@psf.upfronthosting.co.za>


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


New changeset a323eee4c481c88f2b4030bbb224d9bc6bc14c9c by Miss Islington (bot) in branch '3.7':
bpo-18802: Add more details to ipaddress documentation (GH-6083)
https://github.com/python/cpython/commit/a323eee4c481c88f2b4030bbb224d9bc6bc14c9c


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

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

From report at bugs.python.org  Tue Mar 20 20:59:04 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 21 Mar 2018 00:59:04 +0000
Subject: [docs] [issue18802] ipaddress documentation errors
In-Reply-To: <1377118857.87.0.169407991036.issue18802@psf.upfronthosting.co.za>
Message-ID: <1521593943.32.0.467229070634.issue18802@psf.upfronthosting.co.za>


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


New changeset 481cbe8d6202658a7908d97f19f7e9e6061e3df3 by Miss Islington (bot) in branch '3.6':
bpo-18802: Add more details to ipaddress documentation (GH-6083)
https://github.com/python/cpython/commit/481cbe8d6202658a7908d97f19f7e9e6061e3df3


----------

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

From report at bugs.python.org  Tue Mar 20 21:57:16 2018
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 21 Mar 2018 01:57:16 +0000
Subject: [docs] [issue18802] ipaddress documentation errors
In-Reply-To: <1377118857.87.0.169407991036.issue18802@psf.upfronthosting.co.za>
Message-ID: <1521597436.37.0.714561066657.issue18802@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/issue18802>
_______________________________________

From report at bugs.python.org  Wed Mar 21 09:40:52 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Mar 2018 13:40:52 +0000
Subject: [docs] [issue15248] Better explain "TypeError: 'tuple' object is
 not callable"
In-Reply-To: <1341379722.78.0.0866285571225.issue15248@psf.upfronthosting.co.za>
Message-ID: <1521639652.23.0.467229070634.issue15248@psf.upfronthosting.co.za>


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

It is possible to make the compiler producing warnings for such kind of errors. The following sample patch does this. I'm not sure it is worth to do.

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

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

From report at bugs.python.org  Wed Mar 21 09:41:21 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Mar 2018 13:41:21 +0000
Subject: [docs] [issue15248] Better explain "TypeError: 'tuple' object is
 not callable"
In-Reply-To: <1341379722.78.0.0866285571225.issue15248@psf.upfronthosting.co.za>
Message-ID: <1521639681.05.0.714561066657.issue15248@psf.upfronthosting.co.za>


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


----------
keywords: +patch
Added file: https://bugs.python.org/file47496/compile-warnings.diff

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

From report at bugs.python.org  Wed Mar 21 10:52:57 2018
From: report at bugs.python.org (Scott Eilerman)
Date: Wed, 21 Mar 2018 14:52:57 +0000
Subject: [docs] [issue33114] random.sample() behavior is unexpected/unclear
 from docs
Message-ID: <1521643977.18.0.467229070634.issue33114@psf.upfronthosting.co.za>


New submission from Scott Eilerman <scott.j.eilerman at gmail.com>:

I ran into a "bug" when using random.sample() in which I got some results I didn't expect. After digging a little more, this is either a side effect of  the optimization that's made when k > 5, or I am using the function in a way that wasn't intended. If that's the case, I would recommend calling out this behavior in the documentation.

The crux of the issue is that, for a given seed, random.sample(choices,k) gives the same sequence of results for k=1 to k=5, but that sequence can be different (for the same seed) at k=6 and higher. From my initial testing this seems to only occur when 'choices' has an even length.

Example code to reproduce this issue:

import random
seed = 199
choices = range(-10,12)

for k in range(10):
    random.seed(seed)
    print(random.sample(choices,k))


Example code to look at many different occurrences of this issue:

import random
choices = range(-10,12)
count = 0
for seed in range(200):
    for k in range(8):
        random.seed(seed)
        seq1 = random.sample(choices, k)
        random.seed(seed)
        seq2 = random.sample(choices, k+1)
        if seq1 != seq2[:-1]:
            print(seed)
            print(seq1)
            print(seq2)
            count += 1
print(f'Number of bugged results: {count}/200')


To illustrate the odd/even issue, changing choices to range(-10,11) results in zero bugged results.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 314201
nosy: Scott Eilerman, docs at python
priority: normal
severity: normal
status: open
title: random.sample() behavior is unexpected/unclear from docs
type: behavior
versions: Python 3.6

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

From report at bugs.python.org  Wed Mar 21 11:17:33 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 21 Mar 2018 15:17:33 +0000
Subject: [docs] [issue33114] random.sample() behavior is unexpected/unclear
 from docs
In-Reply-To: <1521643977.18.0.467229070634.issue33114@psf.upfronthosting.co.za>
Message-ID: <1521645453.87.0.467229070634.issue33114@psf.upfronthosting.co.za>


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

What additional wording do you propose?

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

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

From report at bugs.python.org  Wed Mar 21 11:22:31 2018
From: report at bugs.python.org (Scott Eilerman)
Date: Wed, 21 Mar 2018 15:22:31 +0000
Subject: [docs] [issue33114] random.sample() behavior is unexpected/unclear
 from docs
In-Reply-To: <1521643977.18.0.467229070634.issue33114@psf.upfronthosting.co.za>
Message-ID: <1521645751.34.0.467229070634.issue33114@psf.upfronthosting.co.za>


Scott Eilerman <scott.j.eilerman at gmail.com> added the comment:

Something along the lines of: "For a fixed seed, random.sample(population, k) is not guaranteed to return the same samples for different values of k."

----------

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

From report at bugs.python.org  Wed Mar 21 11:26:54 2018
From: report at bugs.python.org (Scott Eilerman)
Date: Wed, 21 Mar 2018 15:26:54 +0000
Subject: [docs] [issue33114] random.sample() behavior is unexpected/unclear
 from docs
In-Reply-To: <1521643977.18.0.467229070634.issue33114@psf.upfronthosting.co.za>
Message-ID: <1521646014.27.0.467229070634.issue33114@psf.upfronthosting.co.za>


Scott Eilerman <scott.j.eilerman at gmail.com> added the comment:

To clarify the use case where this behavior was problematic for me, I wanted to get the nth random draw from a given distribution, so I used something like:

random.seed(fixed_seed)
random.sample(choices, n)[-1]

Then, later, I want the next draw, so I did:

random.seed(fixed_seed)
random.sample(choices, n)[-1]


The workaround would be to use random.shuffle and pick the nth item, or use random.sample once with the highest k value I expect to need and then pick the nth element from that list. But I settled on the above implementation because for the first few cases I tested, it returned the results I expected, and nothing in the docs suggested I should expect otherwise.

----------

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

From report at bugs.python.org  Wed Mar 21 11:31:08 2018
From: report at bugs.python.org (Scott Eilerman)
Date: Wed, 21 Mar 2018 15:31:08 +0000
Subject: [docs] [issue33114] random.sample() behavior is unexpected/unclear
 from docs
In-Reply-To: <1521643977.18.0.467229070634.issue33114@psf.upfronthosting.co.za>
Message-ID: <1521646268.75.0.467229070634.issue33114@psf.upfronthosting.co.za>


Scott Eilerman <scott.j.eilerman at gmail.com> added the comment:

Sorry, there's a typo in that example. It should look like:


random.seed(fixed_seed)
random.sample(choices, n)[-1]

Then, later, I want the next draw, so I did:

random.seed(fixed_seed)
random.sample(choices, n+1)[-1]

----------

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

From report at bugs.python.org  Wed Mar 21 14:21:20 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 21 Mar 2018 18:21:20 +0000
Subject: [docs] [issue15248] Better explain "TypeError: 'tuple' object is
 not callable"
In-Reply-To: <1341379722.78.0.0866285571225.issue15248@psf.upfronthosting.co.za>
Message-ID: <1521656480.47.0.467229070634.issue15248@psf.upfronthosting.co.za>


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

Reviewing Serhiy's patch, I changed my mind from 6 years ago (msg164774).  I may have over-estimated the difficulty; in any case the code patch is written.  (Tests are still needed.)  And the code is rather straightforward and readable.

Beyond that, I see the patch as detecting a SyntaxError during compilation, as explained below, with the hint being frosting on top of that.  (It is not an 'Error' as the grammar is now, but it is an error as we might like it to be, hence Serhiy used SyntaxWarning instead.)

In addition, we now have the 'print' precedent of 'print'.
  >>> print 1
  SyntaxError: Missing parentheses in call to 'print'. Did you mean print(1)?
I don't remember when this was added, but I don't see any mention above.

And it seems from other discussions, like the recent python-ideas thread about possibly deprecating 'string' 'joining', that several people have much more of a problem with missing commas than some of us do.

If it were possible, we would like the 'call' production to be
  call ::=  callable "(" [argument_list [","] | comprehension] ")"
but 'callable' is not syntactically definable.  What is syntactically definable and what Serhiy's patch implements is
 possible_callable  ::= primary - <obvious exclusions>
 call  ::= possible_callable ...

As it happens, our grammar metasyntax does not (I believe) include set difference, and I suspect that implementing 'possible_callable' by set addition would result in something that is not LL(1) and possibly ambiguous.  Even if 'possible_callable' could be defined within the LL(1) constraint, I suspect it would be messy, and special-casing would still be needed for the special-case message.

Ditto for 'possibly_subscriptable'.

I have 3 questions:
1. Why 'chech' instead of 'check'?
2. Will chech_index catch "[1,2] [3,4]"? (I am guessing that is the intent.)
3. Does Syntax Warning stop compilation, or at least execution, as at a >>> prompt?

Aside from that, I would be inclined to mark this for 'Interpreter Core' and seriously consider it.

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

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

From report at bugs.python.org  Wed Mar 21 14:59:34 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 21 Mar 2018 18:59:34 +0000
Subject: [docs] [issue15248] Better explain "TypeError: 'tuple' object is
 not callable"
In-Reply-To: <1341379722.78.0.0866285571225.issue15248@psf.upfronthosting.co.za>
Message-ID: <1521658774.29.0.467229070634.issue15248@psf.upfronthosting.co.za>


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

Actually the precedence was a warning for an assert like:

    assert(x % 2 == 0, "x is odd")

Currently it is the only syntax warning produced by the compiler.

> 1. Why 'chech' instead of 'check'?

Just a typo replicated with a copy-paste.

> 2. Will chech_index catch "[1,2] [3,4]"? (I am guessing that is the intent.)

Yes, it is. It could be extended to catch also "['foo','bar'] ['baz']".

> 3. Does Syntax Warning stop compilation, or at least execution, as at a >>> prompt?

No, it is just a warning unless you run Python with -Werror.

This patch was inspired by usability improvements in GCC 8 [1]. I haven't created a pull request because I have doubts about that this should be in the compiler rather of a third-party linter. But if several other core developers will support this idea I'll continue working in this direction.

[1] https://developers.redhat.com/blog/2018/03/15/gcc-8-usability-improvements/

----------

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

From report at bugs.python.org  Wed Mar 21 16:33:53 2018
From: report at bugs.python.org (Steven Downum)
Date: Wed, 21 Mar 2018 20:33:53 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1521664433.92.0.714561066657.issue28677@psf.upfronthosting.co.za>


Change by Steven Downum <devilaether at gmail.com>:


----------
nosy: +steven.downum

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

From report at bugs.python.org  Wed Mar 21 17:06:46 2018
From: report at bugs.python.org (Henrique Fingler)
Date: Wed, 21 Mar 2018 21:06:46 +0000
Subject: [docs] [issue33117] asyncio example uses non-existing/documented
 method
Message-ID: <1521666406.67.0.467229070634.issue33117@psf.upfronthosting.co.za>


New submission from Henrique Fingler <idnpolar at gmail.com>:

In the documentation of asyncio.run_coroutine_threadsafe(coro, loop), in Section 19.5.3.6 (https://docs.python.org/3/library/asyncio-task.html#asyncio.run_coroutine_threadsafe), the example code does the following:

    future = asyncio.run_coroutine_threadsafe(coro, loop)
    # Wait for the result with an optional timeout argument
    assert future.result(timeout) == 3

 The problem is that the result method of a future, according to the documentation doesn't take parameters. It's in Section 19.5.3.4 (https://docs.python.org/3.8/library/asyncio-task.html#asyncio.Future.done)

    result()
        Return the result this future represents.


 The same function is used in Section 18.5.9.3 (https://docs.python.org/3/library/asyncio-dev.html#concurrency-and-multithreading)


 This error is present in all Python 3.* docs.

 From the asyncio source code (https://github.com/python/cpython/blob/master/Lib/asyncio/futures.py), we have this in the Future class definition:

class Future:
    """This class is *almost* compatible with concurrent.futures.Future.
    Differences:
    - This class is not thread-safe.
    - result() and exception() do not take a timeout argument and
      raise an exception when the future isn't done yet.

    ....

So this example needs to be reworked, I'd do it if I knew more about asyncio. My ideas involve either using a add_done_callback with a flag or just busy waiting until future.done().

----------
assignee: docs at python
components: Documentation
messages: 314223
nosy: Henrique Fingler, docs at python
priority: normal
severity: normal
status: open
title: asyncio example uses non-existing/documented method
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Wed Mar 21 22:05:34 2018
From: report at bugs.python.org (Ned Deily)
Date: Thu, 22 Mar 2018 02:05:34 +0000
Subject: [docs] [issue33117] asyncio example uses non-existing/documented
 method
In-Reply-To: <1521666406.67.0.467229070634.issue33117@psf.upfronthosting.co.za>
Message-ID: <1521684334.22.0.714561066657.issue33117@psf.upfronthosting.co.za>


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


----------
nosy: +asvetlov, giampaolo.rodola, yselivanov

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

From report at bugs.python.org  Thu Mar 22 02:38:35 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Mar 2018 06:38:35 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1521700715.5.0.467229070634.issue27212@psf.upfronthosting.co.za>


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

Cheryl, I think you take this one.  It hasn't been touched in a long time and Nofar is focused on another issue.

----------
assignee: Nofar Schnider -> csabella

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

From report at bugs.python.org  Thu Mar 22 04:35:47 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 22 Mar 2018 08:35:47 +0000
Subject: [docs] [issue4819] Misc/cheatsheet needs updating
In-Reply-To: <1230988594.32.0.497089911482.issue4819@psf.upfronthosting.co.za>
Message-ID: <1521707747.42.0.714561066657.issue4819@psf.upfronthosting.co.za>


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


----------
status: open -> pending
versions:  -Python 3.2, Python 3.3

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

From report at bugs.python.org  Thu Mar 22 04:38:26 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 22 Mar 2018 08:38:26 +0000
Subject: [docs] [issue13677] correct docstring for builtin compile
In-Reply-To: <1325180963.04.0.479072583529.issue13677@psf.upfronthosting.co.za>
Message-ID: <1521707906.38.0.714561066657.issue13677@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.6, Python 3.7, Python 3.8 -Python 3.2, Python 3.3

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

From report at bugs.python.org  Thu Mar 22 05:19:51 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 22 Mar 2018 09:19:51 +0000
Subject: [docs] [issue25836] Documentation of
 MAKE_FUNCTION/MAKE_CLOSURE_EXTENDED_ARG is misleading
In-Reply-To: <1449807235.86.0.17166679506.issue25836@psf.upfronthosting.co.za>
Message-ID: <1521710391.14.0.467229070634.issue25836@psf.upfronthosting.co.za>


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

MAKE_FUNCTION was changed in 3.6, and its documentation was changed accordingly. 3.5 is now in security-only fixes stage.

----------
nosy: +serhiy.storchaka
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Mar 22 05:21:13 2018
From: report at bugs.python.org (Jonathan Huot)
Date: Thu, 22 Mar 2018 09:21:13 +0000
Subject: [docs] [issue33119] python sys.argv argument parsing not clear
Message-ID: <1521710473.18.0.467229070634.issue33119@psf.upfronthosting.co.za>


New submission from Jonathan Huot <jonathan.huot at thomsonreuters.com>:

Executing python modules with -m can lead to weird sys.argv parsing.

"Argument parsing" section at https://docs.python.org/3.8/tutorial/interpreter.html#argument-passing mention :

- When -m module is used, sys.argv[0] is set to the full name of the located module.

The word "located" is used, but it doesn't mention anything when the module is not *yet* "located".

For instance, let's see what is the sys.argv for each python files:


$ cat mainmodule/__init__.py
import sys; print("{}: {}".format(sys.argv, __file__))
$ cat mainmodule/submodule/__init__.py
import sys; print("{}: {}".format(sys.argv, __file__))
$ cat mainmodule/submodule/foobar.py
import sys; print("{}: {}".format(sys.argv, __file__))


Then we call "foobar" with -m:

$ python -m mainmodule.submodule.foobar -o -b
['-m', '-o', 'b']: (..)/mainmodule/__init__.py
['-m', '-o', 'b']: (..)/mainmodule/submodule/__init__.py
['(..)/mainmodule/submodule/foobar.py', '-o', 'b']: (..)/mainmodule/submodule/foobar.py
$


We notice that only "-m" is in sys.argv before we found "foobar". This can lead to a lot of troubles when we have meaningful processing in __init__.py which rely on sys.argv to initialize stuff.

IMHO, it either should be the sys.argv intact ['-m', 'mainmodule.submodule.foobar', '-o', '-b'] or empty ['', '-o', '-b'] or  only the latest ['-o', '-b'], but it should not be ['-m', '-o', '-b'] which is very confusing.

----------
assignee: docs at python
components: Documentation
messages: 314239
nosy: Jonathan Huot, docs at python
priority: normal
severity: normal
status: open
title: python sys.argv argument parsing not clear
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/issue33119>
_______________________________________

From report at bugs.python.org  Thu Mar 22 06:21:05 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 22 Mar 2018 10:21:05 +0000
Subject: [docs] [issue30076] Opcode names BUILD_MAP_UNPACK_WITH_CALL and
 BUILD_TUPLE_UNPACK_WITH_CALL are too long
In-Reply-To: <1492277239.5.0.348724747458.issue30076@psf.upfronthosting.co.za>
Message-ID: <1521714065.72.0.714561066657.issue30076@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> needs patch
versions: +Python 3.6, Python 3.8

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

From report at bugs.python.org  Thu Mar 22 10:15:08 2018
From: report at bugs.python.org (joders)
Date: Thu, 22 Mar 2018 14:15:08 +0000
Subject: [docs] [issue33121] recv returning 0 on closed connection not
 documented
Message-ID: <1521728108.91.0.467229070634.issue33121@psf.upfronthosting.co.za>


New submission from joders <jona.enders at yahoo.com>:

The "Linux Programmer's Manual" states:

When a stream socket peer has performed an orderly shutdown, the return value will be 0 (the traditional "end-of-file" return).

I find that information pretty important which is why I am asking if you might want to add it to the python documentation as well. It would have prevented a bug in my code.

----------
assignee: docs at python
components: Documentation
messages: 314260
nosy: docs at python, joders
priority: normal
severity: normal
status: open
title: recv returning 0 on closed connection not documented
type: enhancement
versions: Python 3.6

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

From report at bugs.python.org  Thu Mar 22 11:52:55 2018
From: report at bugs.python.org (Chad)
Date: Thu, 22 Mar 2018 15:52:55 +0000
Subject: [docs] [issue33082] multiprocessing docs bury very important
 'callback=' args
In-Reply-To: <1521139850.07.0.467229070634.issue33082@psf.upfronthosting.co.za>
Message-ID: <1521733975.69.0.467229070634.issue33082@psf.upfronthosting.co.za>


Chad <millchad at amazon.com> added the comment:

On topic: My CLA is signed as of Monday, 19 March. My status here is not updated yet.


pitrou, off-topic: Without callbacks, users who want multiprocessing functions to return something, not just mutate state somewhere else, must gather jobs in a list and continually iterate through them polling to see if each has finished yet and conditionally popping it from the list. It's expensive and ugly and error-prone. Callbacks are really great, you should try them again.

So much better:

pool.apply_async(func, args, callback=when_finished_call_with_result)

----------

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

From report at bugs.python.org  Thu Mar 22 12:05:44 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 22 Mar 2018 16:05:44 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1521734744.72.0.467229070634.issue27212@psf.upfronthosting.co.za>


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

Thanks, Raymond.  I'll take a look.

----------

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

From report at bugs.python.org  Thu Mar 22 19:09:21 2018
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 22 Mar 2018 23:09:21 +0000
Subject: [docs] [issue33119] python sys.argv argument parsing not clear
In-Reply-To: <1521710473.18.0.467229070634.issue33119@psf.upfronthosting.co.za>
Message-ID: <1521760161.37.0.714561066657.issue33119@psf.upfronthosting.co.za>


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


----------
nosy: +ncoghlan

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

From report at bugs.python.org  Thu Mar 22 19:27:53 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 22 Mar 2018 23:27:53 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1521761273.12.0.714561066657.issue27212@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


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

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

From report at bugs.python.org  Fri Mar 23 12:49:06 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 23 Mar 2018 16:49:06 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
Message-ID: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>


New submission from Antoine Pitrou <pitrou at free.fr>:

The following C functions are available for C code but not documented:
- PyBuffer_ToContiguous()
- PyBuffer_FromContiguous()
- PyObject_CopyData()

I am not sure how to describe those functions myself.

----------
assignee: docs at python
components: Documentation
messages: 314315
nosy: docs at python, pitrou, skrah
priority: normal
severity: normal
stage: needs patch
status: open
title: Some C buffer protocol APIs not documented
type: behavior
versions: Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Fri Mar 23 17:20:26 2018
From: report at bugs.python.org (Julien Palard)
Date: Fri, 23 Mar 2018 21:20:26 +0000
Subject: [docs] [issue31793] Allow to specialize smart quotes in
 documentation translations
In-Reply-To: <1508060988.99.0.213398074469.issue31793@psf.upfronthosting.co.za>
Message-ID: <1521840026.21.0.467229070634.issue31793@psf.upfronthosting.co.za>


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

Reopening as smart quotes is still a source of bugs in Japanese translation, see: https://github.com/python/docsbuild-scripts/issues/32#issuecomment-375801129

----------
status: closed -> open

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

From report at bugs.python.org  Fri Mar 23 17:22:28 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Mar 2018 21:22:28 +0000
Subject: [docs] [issue33114] random.sample() behavior is unexpected/unclear
 from docs
In-Reply-To: <1521643977.18.0.467229070634.issue33114@psf.upfronthosting.co.za>
Message-ID: <1521840148.27.0.467229070634.issue33114@psf.upfronthosting.co.za>


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

> Something along the lines of: "For a fixed seed, random.sample(population, k)
> is not guaranteed to return the same samples for different values of k."

In a way, the proposed wording succinctly directly addresses the problem you had.  So, it would seem like a reasonable suggestion.  On the other hand, it would be easy for others who haven't had this problem to have a hard time figuring out what it means (when should they be worried, what should be avoided, why is it a concern at all, what to do about it).

In general, the docs are worded in an affirmative manner (here's what something does, here's what it is for, and here is how to use it correctly).  In this case, the docs already indicate the intended way to address this use case: "the resulting list is in selection order so that all sub-slices will also be valid random samples.  This allows raffle winners (the sample) to be partitioned into grand prize and second place winners (the subslices)."

Perhaps there could be an algorithmic note, "internally, sample() shifts selection algorithms depending on the proportion of the population being sampled".  However, this would be unusual -- we don't usually document implementation details.  Numpy[1] and R[2] make no mention of the internals.  Julia[3] does discuss the algorithms but primarily from an efficiency point-of-view rather than as a usage note.

Perhaps it may be best to leave this alone rather than adding a note that may itself create confusion and worry.  AFAICT, this hasn't come up before in the 15 year history of random.sample(), not even a StackOverflow question.

[1] https://docs.scipy.org/doc/numpy-1.14.0/reference/generated/numpy.random.choice.html
[2] https://www.rdocumentation.org/packages/base/versions/3.4.3/topics/sample
[3] http://juliastats.github.io/StatsBase.jl/stable/sampling.html#Sampling-API-1

----------

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

From report at bugs.python.org  Fri Mar 23 17:26:38 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 23 Mar 2018 21:26:38 +0000
Subject: [docs] [issue27428] Document WindowsRegistryFinder inherits from
 MetaPathFinder
In-Reply-To: <1467326072.76.0.431868228595.issue27428@psf.upfronthosting.co.za>
Message-ID: <1521840398.19.0.467229070634.issue27428@psf.upfronthosting.co.za>


Brett Cannon <brett at python.org> added the comment:


New changeset 5cbb84106efefd200933aa31e22abf39267d2557 by Brett Cannon (Himanshu Lakhara) in branch 'master':
bpo-27428: Fix WindowsRegistryFinder documentation to list appropriate ABC (GH-6061)
https://github.com/python/cpython/commit/5cbb84106efefd200933aa31e22abf39267d2557


----------

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

From report at bugs.python.org  Fri Mar 23 17:27:50 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 23 Mar 2018 21:27:50 +0000
Subject: [docs] [issue27428] Document WindowsRegistryFinder inherits from
 MetaPathFinder
In-Reply-To: <1467326072.76.0.431868228595.issue27428@psf.upfronthosting.co.za>
Message-ID: <1521840470.93.0.714561066657.issue27428@psf.upfronthosting.co.za>


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


----------
pull_requests: +5949

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

From report at bugs.python.org  Fri Mar 23 17:28:09 2018
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 23 Mar 2018 21:28:09 +0000
Subject: [docs] [issue32362] multiprocessing.connection.Connection
 misdocumented as multiprocessing.Connection
In-Reply-To: <1513592247.3.0.213398074469.issue32362@psf.upfronthosting.co.za>
Message-ID: <1521840489.65.0.714561066657.issue32362@psf.upfronthosting.co.za>


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


----------
keywords: +easy
stage:  -> needs patch
type:  -> behavior
versions:  -Python 3.4, Python 3.5

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

From report at bugs.python.org  Fri Mar 23 17:28:44 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 23 Mar 2018 21:28:44 +0000
Subject: [docs] [issue27428] Document WindowsRegistryFinder inherits from
 MetaPathFinder
In-Reply-To: <1467326072.76.0.431868228595.issue27428@psf.upfronthosting.co.za>
Message-ID: <1521840524.68.0.714561066657.issue27428@psf.upfronthosting.co.za>


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


----------
pull_requests: +5950

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

From report at bugs.python.org  Fri Mar 23 17:41:28 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 23 Mar 2018 21:41:28 +0000
Subject: [docs] [issue27428] Document WindowsRegistryFinder inherits from
 MetaPathFinder
In-Reply-To: <1467326072.76.0.431868228595.issue27428@psf.upfronthosting.co.za>
Message-ID: <1521841288.58.0.467229070634.issue27428@psf.upfronthosting.co.za>


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


New changeset 45738ede5ac8507b88b35fb0d6e2806a7b2e2efc by Miss Islington (bot) in branch '3.7':
bpo-27428: Fix WindowsRegistryFinder documentation to list appropriate ABC (GH-6061)
https://github.com/python/cpython/commit/45738ede5ac8507b88b35fb0d6e2806a7b2e2efc


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

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

From report at bugs.python.org  Fri Mar 23 17:50:15 2018
From: report at bugs.python.org (miss-islington)
Date: Fri, 23 Mar 2018 21:50:15 +0000
Subject: [docs] [issue27428] Document WindowsRegistryFinder inherits from
 MetaPathFinder
In-Reply-To: <1467326072.76.0.431868228595.issue27428@psf.upfronthosting.co.za>
Message-ID: <1521841814.95.0.467229070634.issue27428@psf.upfronthosting.co.za>


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


New changeset 643a781188539de038745d23d0e8e5a03b781209 by Miss Islington (bot) in branch '3.6':
bpo-27428: Fix WindowsRegistryFinder documentation to list appropriate ABC (GH-6061)
https://github.com/python/cpython/commit/643a781188539de038745d23d0e8e5a03b781209


----------

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

From report at bugs.python.org  Fri Mar 23 18:27:31 2018
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 23 Mar 2018 22:27:31 +0000
Subject: [docs] [issue27428] Document WindowsRegistryFinder inherits from
 MetaPathFinder
In-Reply-To: <1467326072.76.0.431868228595.issue27428@psf.upfronthosting.co.za>
Message-ID: <1521844051.07.0.714561066657.issue27428@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Mar 23 20:05:44 2018
From: report at bugs.python.org (Vince Reuter)
Date: Sat, 24 Mar 2018 00:05:44 +0000
Subject: [docs] [issue33130] functools.reduce signature/docstring discordance
Message-ID: <1521849944.24.0.467229070634.issue33130@psf.upfronthosting.co.za>


New submission from Vince Reuter <vince.reuter at gmail.com>:

The signature for functools.reduce correctly refers to the collection parameter as an iterable, but the docstring refers to it as "sequence," which the input need not be and does not match the parameter name despite being italicized.

----------
assignee: docs at python
components: Documentation
messages: 314344
nosy: docs at python, vreuter
priority: normal
pull_requests: 5951
severity: normal
status: open
title: functools.reduce signature/docstring discordance
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/issue33130>
_______________________________________

From report at bugs.python.org  Fri Mar 23 20:07:46 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 24 Mar 2018 00:07:46 +0000
Subject: [docs] [issue33117] asyncio example uses non-existing/documented
 method
In-Reply-To: <1521666406.67.0.467229070634.issue33117@psf.upfronthosting.co.za>
Message-ID: <1521850066.34.0.714561066657.issue33117@psf.upfronthosting.co.za>


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


----------
versions:  -Python 3.5

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

From report at bugs.python.org  Fri Mar 23 21:15:22 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 24 Mar 2018 01:15:22 +0000
Subject: [docs] [issue33119] python sys.argv argument parsing not clear
In-Reply-To: <1521710473.18.0.467229070634.issue33119@psf.upfronthosting.co.za>
Message-ID: <1521854122.05.0.467229070634.issue33119@psf.upfronthosting.co.za>


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

Two of your 3 suggested alternatives could lead to bugs. To use your example:
 python -m mainmodule.submodule.foobar -o -b
is a convenient alternative and abbreviation for
 python .../somedir/mainmodule/submodule/foobar.py -o -b
The two invocations should give equivalent results and to the extent possible the same result.

[What might be different is the form of argv[0].  In the first case, argv[0] will be the "preferred" form of the path to the python file while in the second, it will be whatever is given.  On Windows, the difference might look like 'F:\\Python\\a\\tem2.py' versus 'f:/python/a/tem2.py']

Unless __init__.py does some evil monkeypatching, it cannot affect the main module unless imported directly or indirectly.  So its behavior should be the same whether imported before or after execution of the main module.  This means that argv must be the same either way (except for argv[0]).  So argv[0:2] must be condensed to one arg before executing __init__.  I don't see that '' is an improvement over '-m'.

Command line arguments are intended for the invoked command.  An __init__.py file is never the command unless invoked by its full path: "python somepath/__init__.py".  In such a case, sys.argv access should be within a "__name__ == '__main__':" clause or a function called therein.

----------
nosy: +terry.reedy
versions:  -Python 3.4, Python 3.5

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

From report at bugs.python.org  Fri Mar 23 21:29:03 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 24 Mar 2018 01:29:03 +0000
Subject: [docs] [issue33121] recv returning 0 on closed connection not
 documented
In-Reply-To: <1521728108.91.0.467229070634.issue33121@psf.upfronthosting.co.za>
Message-ID: <1521854943.54.0.467229070634.issue33121@psf.upfronthosting.co.za>


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

Please make a specific suggestion for a change in a specific location in the current online version of a particular doc -- the one you wish had been there already.

----------
nosy: +terry.reedy

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

From report at bugs.python.org  Sat Mar 24 00:25:00 2018
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 24 Mar 2018 04:25:00 +0000
Subject: [docs] [issue33119] python sys.argv argument parsing not clear
In-Reply-To: <1521710473.18.0.467229070634.issue33119@psf.upfronthosting.co.za>
Message-ID: <1521865500.67.0.467229070634.issue33119@psf.upfronthosting.co.za>


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

This is deliberate, and is covered in the documentation at https://docs.python.org/3/using/cmdline.html#cmdoption-m where it says 'If this option is given, the first element of sys.argv will be the full path to the module file (while the module file is being located, the first element will be set to "-m").'

The part in parentheses is the bit that's applicable here.

We've not going to change that, as the interpreter startup relies on checking sys.argv[0] for "-m" and "-c" in order to work out how it's expected to handle sys.path initialization.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Mar 24 01:21:38 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 24 Mar 2018 05:21:38 +0000
Subject: [docs] [issue33130] functools.reduce signature/docstring discordance
In-Reply-To: <1521849944.24.0.467229070634.issue33130@psf.upfronthosting.co.za>
Message-ID: <1521868898.1.0.714561066657.issue33130@psf.upfronthosting.co.za>


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


----------
nosy: +ncoghlan, rhettinger
versions:  -Python 3.5

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

From report at bugs.python.org  Sat Mar 24 01:42:45 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 24 Mar 2018 05:42:45 +0000
Subject: [docs] [issue33006] docstring of filter function is incorrect
In-Reply-To: <1520300191.48.0.467229070634.issue33006@psf.upfronthosting.co.za>
Message-ID: <1521870165.49.0.714561066657.issue33006@psf.upfronthosting.co.za>


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


----------
nosy: +ncoghlan, rhettinger

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

From report at bugs.python.org  Sat Mar 24 01:56:44 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 24 Mar 2018 05:56:44 +0000
Subject: [docs] [issue31544] gettext.Catalog title is not flagged as a class
In-Reply-To: <1506007626.15.0.9927755066.issue31544@psf.upfronthosting.co.za>
Message-ID: <1521871004.67.0.467229070634.issue31544@psf.upfronthosting.co.za>


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


New changeset 0694b6a651ba2a53f6323ffb3b23358f43885815 by Serhiy Storchaka (scoder) in branch '2.7':
bpo-31544: Avoid calling "PyObject_GetAttrString()" (and potentially executing user code) with a live exception set. (GH-3992)
https://github.com/python/cpython/commit/0694b6a651ba2a53f6323ffb3b23358f43885815


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

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

From report at bugs.python.org  Sat Mar 24 01:59:40 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 24 Mar 2018 05:59:40 +0000
Subject: [docs] [issue31544] gettext.Catalog title is not flagged as a class
In-Reply-To: <1506007626.15.0.9927755066.issue31544@psf.upfronthosting.co.za>
Message-ID: <1521871180.23.0.714561066657.issue31544@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Mar 24 02:48:53 2018
From: report at bugs.python.org (Aaron Ang)
Date: Sat, 24 Mar 2018 06:48:53 +0000
Subject: [docs] [issue28677] difficult to parse sentence structure in "When
 an instance attribute is referenced that isn't a data attribute"
In-Reply-To: <1478986337.93.0.398450030776.issue28677@psf.upfronthosting.co.za>
Message-ID: <1521874133.27.0.714561066657.issue28677@psf.upfronthosting.co.za>


Change by Aaron Ang <awz.ang at gmail.com>:


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

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

From report at bugs.python.org  Sat Mar 24 06:27:46 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 24 Mar 2018 10:27:46 +0000
Subject: [docs] [issue32996] Improve What's New in 3.7
In-Reply-To: <1520251006.69.0.467229070634.issue32996@psf.upfronthosting.co.za>
Message-ID: <1521887266.2.0.467229070634.issue32996@psf.upfronthosting.co.za>


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

Different projects solve the problem with async in different ways. Many of them rename "async" parameter to "async_". Some renames it to "_async" or replace with an opposite parameter "sync". Some projects keep supporting of "async" in older Python versions by using var-keyword parameters, but not all are aware of this possibility. If the preferable way be described in the What's New, it would help porting to 3.7.

Another important language change missed in the What's New is keeping insertion order in dicts.

----------

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

From report at bugs.python.org  Sat Mar 24 17:53:19 2018
From: report at bugs.python.org (Stefan Krah)
Date: Sat, 24 Mar 2018 21:53:19 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1521928399.24.0.467229070634.issue33126@psf.upfronthosting.co.za>


Stefan Krah <stefan at bytereef.org> added the comment:

I fixed PyBuffer_ToContiguous() in 3.3, PyBuffer_FromContiguous() was broken until #23370.

For a start, here's a doc patch for PyBuffer_ToContiguous().

PyBuffer_FromContiguous() does the opposite and loads a contiguous buffer
into a possibly non-contiguous view.

PyObject_CopyData() copies the data from exporter src to the writable exporter dest.

I have never used the last two functions.

----------
keywords: +patch
Added file: https://bugs.python.org/file47497/issue33126.diff

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

From report at bugs.python.org  Sat Mar 24 18:37:55 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 24 Mar 2018 22:37:55 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1521931074.98.0.467229070634.issue33126@psf.upfronthosting.co.za>


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

Thanks.  The PyBuffer_ToContiguous() API is weird: why pass `len` if it cannot be anything other than `src->len`?
Also, it would be nice to explain whether the actual buffer data is copied around (with a memory allocation?) or if it's just the Py_buffer struct.

----------

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

From report at bugs.python.org  Sat Mar 24 21:53:57 2018
From: report at bugs.python.org (bbayles)
Date: Sun, 25 Mar 2018 01:53:57 +0000
Subject: [docs] [issue32362] multiprocessing.connection.Connection
 misdocumented as multiprocessing.Connection
In-Reply-To: <1513592247.3.0.213398074469.issue32362@psf.upfronthosting.co.za>
Message-ID: <1521942837.02.0.714561066657.issue32362@psf.upfronthosting.co.za>


Change by bbayles <bbayles at gmail.com>:


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

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

From report at bugs.python.org  Sat Mar 24 21:54:22 2018
From: report at bugs.python.org (bbayles)
Date: Sun, 25 Mar 2018 01:54:22 +0000
Subject: [docs] [issue32362] multiprocessing.connection.Connection
 misdocumented as multiprocessing.Connection
In-Reply-To: <1513592247.3.0.213398074469.issue32362@psf.upfronthosting.co.za>
Message-ID: <1521942862.38.0.714561066657.issue32362@psf.upfronthosting.co.za>


Change by bbayles <bbayles at gmail.com>:


----------
nosy: +bbayles

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

From report at bugs.python.org  Sun Mar 25 02:05:09 2018
From: report at bugs.python.org (Tim Peters)
Date: Sun, 25 Mar 2018 06:05:09 +0000
Subject: [docs] [issue33114] random.sample() behavior is unexpected/unclear
 from docs
In-Reply-To: <1521643977.18.0.467229070634.issue33114@psf.upfronthosting.co.za>
Message-ID: <1521957909.56.0.467229070634.issue33114@psf.upfronthosting.co.za>


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

There's nothing in the docs I can see that implies `sample(x, n)` is a prefix of what `sample(x, n+1)` would have returned had the latter been called instead.  If so, then - as always - it's "at your own risk" when you rely on behaviors that haven't been specified.  Since the universe of _possible_ behaviors that haven't been specified is immense, I'd rather we didn't even start to list all of them ;-)

Seriously, when the docs don't promise something, it's usually a mistake to assume they just forgot to mention it.  I'd leave the docs alone in this case.

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

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

From report at bugs.python.org  Sun Mar 25 10:26:27 2018
From: report at bugs.python.org (Martin Panter)
Date: Sun, 25 Mar 2018 14:26:27 +0000
Subject: [docs] [issue33079] subprocess: document the interaction between
 subprocess.Popen and os.set_inheritable
In-Reply-To: <1521109238.05.0.467229070634.issue33079@psf.upfronthosting.co.za>
Message-ID: <1521987987.85.0.467229070634.issue33079@psf.upfronthosting.co.za>


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

There is no ?open_fds? parameter as far as I know. I presume you meant heritable descriptors are still closed with close_fds=True (not open_fds=False).

Are you sure about the second part? In my experiments on Linux, unless I use ?pass_fds? or one of the ?stdin? etc parameters, a non-heritable descriptor is never passed to the child, no matter what I use for ?close_fds?.

Reading through Issue 6559, the intention of ?pass_fds? seems to be to list extra file descriptors, in addition to 0, 1 and 2 that are normally passed. The documentation says descriptors greater than 2 are closed (due to close_fds=True), but in reality the ?pass_fds? descriptors seem to be always left open, even when they are marked non-heritable.

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

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

From report at bugs.python.org  Sun Mar 25 12:36:59 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 25 Mar 2018 16:36:59 +0000
Subject: [docs] [issue15088] PyGen_NeedsFinalizing is public,
 but undocumented
In-Reply-To: <1339906861.99.0.42415214654.issue15088@psf.upfronthosting.co.za>
Message-ID: <1521995819.82.0.467229070634.issue15088@psf.upfronthosting.co.za>


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

What should be done for the PyGen_NeedsFinalizing API?  Does it need to be documented or should it be removed since it's no longer used in the code base?

Thanks!

----------
nosy: +csabella
versions: +Python 3.7, Python 3.8 -Python 3.2, Python 3.3

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

From report at bugs.python.org  Sun Mar 25 12:49:52 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 25 Mar 2018 16:49:52 +0000
Subject: [docs] [issue31869] commentary on ssl.PROTOCOL_TLS
In-Reply-To: <1508947295.4.0.213398074469.issue31869@psf.upfronthosting.co.za>
Message-ID: <1521996592.06.0.467229070634.issue31869@psf.upfronthosting.co.za>


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

This was changed for 3.7 and 3.6 in PR1355, but there's no corresponding bpo number for that.  Should the relevant changes be backported to 2.7?

----------
nosy: +csabella

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

From report at bugs.python.org  Sun Mar 25 12:50:36 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 25 Mar 2018 16:50:36 +0000
Subject: [docs] [issue31869] commentary on ssl.PROTOCOL_TLS
In-Reply-To: <1508947295.4.0.213398074469.issue31869@psf.upfronthosting.co.za>
Message-ID: <1521996636.92.0.714561066657.issue31869@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


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

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

From report at bugs.python.org  Sun Mar 25 12:55:14 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 25 Mar 2018 16:55:14 +0000
Subject: [docs] [issue24356] venv documentation incorrect / misleading
In-Reply-To: <1433197293.5.0.203233804739.issue24356@psf.upfronthosting.co.za>
Message-ID: <1521996914.09.0.714561066657.issue24356@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


----------
keywords: +easy
stage:  -> needs patch
type:  -> enhancement
versions: +Python 3.7, Python 3.8 -Python 3.3

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

From report at bugs.python.org  Sun Mar 25 13:28:01 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Sun, 25 Mar 2018 17:28:01 +0000
Subject: [docs] [issue33079] subprocess: document the interaction between
 subprocess.Popen and os.set_inheritable
In-Reply-To: <1521109238.05.0.467229070634.issue33079@psf.upfronthosting.co.za>
Message-ID: <1521998881.11.0.714561066657.issue33079@psf.upfronthosting.co.za>


Change by Gregory P. Smith <greg at krypto.org>:


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

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

From report at bugs.python.org  Sun Mar 25 13:37:50 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Sun, 25 Mar 2018 17:37:50 +0000
Subject: [docs] [issue33079] subprocess: document the interaction between
 subprocess.Popen and os.set_inheritable
In-Reply-To: <1521109238.05.0.467229070634.issue33079@psf.upfronthosting.co.za>
Message-ID: <1521999470.36.0.467229070634.issue33079@psf.upfronthosting.co.za>


Gregory P. Smith <greg at krypto.org> added the comment:

I assumed simon meant "close_fds=False" when he wrote open_fds = True.

Regardless, supplying any pass_fds forces close_fds=True behavior.

File descriptors listed in pass_fds are explicitly set inheritable from within the child process prior to calling exec().  See the start of child_exec() within Modules/_posixsubprocess.c.

----------

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

From report at bugs.python.org  Sun Mar 25 13:44:07 2018
From: report at bugs.python.org (Gregory P. Smith)
Date: Sun, 25 Mar 2018 17:44:07 +0000
Subject: [docs] [issue33079] subprocess: document the interaction between
 subprocess.Popen and os.set_inheritable
In-Reply-To: <1521109238.05.0.467229070634.issue33079@psf.upfronthosting.co.za>
Message-ID: <1521999847.83.0.467229070634.issue33079@psf.upfronthosting.co.za>


Gregory P. Smith <greg at krypto.org> added the comment:

I clarified the docs to mention that the inheritable flag is heeded when close_fds=False in https://github.com/python/cpython/pull/6240/files

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

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

From report at bugs.python.org  Sun Mar 25 14:18:52 2018
From: report at bugs.python.org (Stefan Krah)
Date: Sun, 25 Mar 2018 18:18:52 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1522001931.97.0.467229070634.issue33126@psf.upfronthosting.co.za>


Stefan Krah <stefan at bytereef.org> added the comment:

Yes, the signatures are weird. In PyBuffer_FromContiguous(), "len" is
the size of "buf" in bytes.

If "buf" contains 6 floats, but "view" only has space for 4, then only
4 are copied into "view".


To avoid that sort of thing, I changed PyBuffer_ToContiguous() to
be more restrictive in 3.3, but kept the len parameter.

In PyBuffer_ToContiguous() it would not matter though if len(buf) > src->len, in which case buf would contain uninitialized bytes at
the end.


TBH, I don't think these functions are used very often. :-)

----------

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

From report at bugs.python.org  Sun Mar 25 14:32:25 2018
From: report at bugs.python.org (Stefan Krah)
Date: Sun, 25 Mar 2018 18:32:25 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1522002745.87.0.467229070634.issue33126@psf.upfronthosting.co.za>


Stefan Krah <stefan at bytereef.org> added the comment:

And if view->len > len in PyBuffer_FromContiguous(), then
view will contain uninitialized bytes, which is bad.

----------

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

From report at bugs.python.org  Sun Mar 25 19:29:23 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 25 Mar 2018 23:29:23 +0000
Subject: [docs] [issue23952] cgi: Document the 'maxlen' member of the cgi
 module
In-Reply-To: <1429034285.17.0.254053228622.issue23952@psf.upfronthosting.co.za>
Message-ID: <1522020563.11.0.714561066657.issue23952@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> needs patch
title: Document the 'maxlen' member of the cgi module -> cgi: Document the 'maxlen' member of the cgi module
versions: +Python 3.7, Python 3.8 -Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6

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

From Cheng.Nie at utdallas.edu  Tue Mar 20 11:27:06 2018
From: Cheng.Nie at utdallas.edu (Nie, Cheng)
Date: Tue, 20 Mar 2018 15:27:06 +0000
Subject: [docs] Python 3.5 documents download fail
Message-ID: <500E30F9-0240-4C18-BBF8-2D715A685203@utdallas.edu>

Hi There,

All links have 404 error when I try to download the documents:


Best,
Cheng


From fvalder at redhat.com  Wed Mar 21 05:08:43 2018
From: fvalder at redhat.com (Filip Valder)
Date: Wed, 21 Mar 2018 10:08:43 +0100
Subject: [docs] email.header examples
Message-ID: <4375253.XaZs00s8rC@fvalder.remote.redhat.com>

Hi all.

I would like to request documentation changes for code examples in:
https://docs.python.org/2/library/email.header.html
https://docs.python.org/3/library/email.header.html

Please see below & change it as desired or discard completely if it is 
unwanted.

The main point is that people who are not familiar with mail headers format 
actually use otherwise working examples from the docs and they do not know 
that the headers would be formatted inappropriately (in Python 3).

The fix below is still not yet complete, as optimal would be adding: 
header_name='Subject' to the params when creating the Header. Still it (at 
least) covers the main/significant difference between the two Python versions.


For Python 2 - add .encode() method and the comment:
>>> msg['Subject'] = h
Change to:
>>> msg['Subject'] = h.encode()  # .encode() ensures same behavior when
>>>                              # porting code to Python 3


For Python 3 - just add the .encode() method:
>>> msg['Subject'] = h
Change to:
>>> msg['Subject'] = h.encode()


Regards, thank you,
Filip

-- 
Filip Valder
EMEA Software Engineer
+420 532 270 041
fvalder at redhat.com

Red Hat Czech
Purky?ova 71/99, 3080/97b, 647/111
612 00, Brno (CZ)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: example.png
Type: image/png
Size: 19649 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180321/4617b7f5/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.python.org/pipermail/docs/attachments/20180321/4617b7f5/attachment-0001.sig>

From ib.oumarsama at gmail.com  Tue Mar 20 15:42:47 2018
From: ib.oumarsama at gmail.com (oumar sama)
Date: Tue, 20 Mar 2018 20:42:47 +0100
Subject: [docs] unavailability of documentation
Message-ID: <CA+sOxC8HiGBSsnTKzXBMv4L=+S_U02rETgakEe1YOzP39inV-w@mail.gmail.com>

just to warn you that your documentation page
https://docs.python.org/3/download.htmlhave no available link at all
Thanks to considere fixing that issues
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180320/cea84c1e/attachment.html>

From jean-marc.seillon.external at ariane.group  Fri Mar 23 04:26:01 2018
From: jean-marc.seillon.external at ariane.group (SEILLON, Jean-Marc (AUSY))
Date: Fri, 23 Mar 2018 08:26:01 +0000
Subject: [docs] Defaut sur une page de documentation
Message-ID: <182D9F356CF5F148B3E1F98F56137746373549@dg011mur-mx004.dg011.fg01.fr.space.corp>

Bonjour,
?        J'ai remarqu? un d?faut sur la page ? Python<https://www.python.org/>   Documentation<https://docs.python.org/fr/3/index.html> La biblioth?que standard<https://docs.python.org/fr/3/library/index.html> 29. Runtime Python<https://docs.python.org/fr/3/library/python.html> ?

29.1. sys - Para?tres et fonctions propres ? des syst?mes?


Cordialement

Jean-Marc SEILLON


Ce courriel (incluant ses ?ventuelles pi?ces jointes) peut contenir des informations confidentielles et/ou prot?g?es ou dont la diffusion est restreinte ou soumise aux r?glementations relatives au contr?le des exportations ou ayant un caract?re priv?. Si vous avez re?u ce courriel par erreur, vous ne devez ni le reproduire, ni l'utiliser, ni en divulguer le contenu ? quiconque. Merci d'en avertir imm?diatement l'exp?diteur et de supprimer de votre syst?me informatique ce courriel ainsi que tous les documents qui y sont attach?s. Toute exportation ou r?exportation non autoris?e est interdite. ArianeGroup SAS d?cline toute responsabilit? en cas de corruption par virus, d'alt?ration ou de falsification de ce courriel lors de sa transmission par voie ?lectronique.
This email (including any attachments) may contain confidential or proprietary and/or privileged information or information otherwise protected from disclosure or may be subject to export control laws and regulations. If you are not the intended recipient, please notify the sender immediately, do not reproduce this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Unauthorized export or re-export is prohibited. ArianeGroup SAS disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. ArianeGroup SAS (519 032 247 RCS PARIS) - Capital social : 265 904 408 EUR - Si?ge social : Tour Cristal, 7-11 Quai Andr? Citro?n, 75015 Paris - TVA FR 82 519 032 247 - APE/NAF 3030Z
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180323/dcb3e733/attachment.html>

From richard.holt at gmail.com  Sat Mar 24 17:05:33 2018
From: richard.holt at gmail.com (Richard)
Date: Sat, 24 Mar 2018 17:05:33 -0400
Subject: [docs] broken links https://docs.python.org/3.5/download.html
Message-ID: <CAA8fd_tE0Yz=efztyw0kjCWZzQ+4OPRd0qTHUk=p362P1kNdZg@mail.gmail.com>

All of the links of the 3.5 docs seem to be broken.
I tried them all.
That's the version installed in my Debian based linux.

Minimal internet access at present.
Email via cell data plan.

Thanks and regards,
Richard.
richard.holt at gmail.com
Venezuela.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180324/632e344c/attachment-0001.html>

From richard.holt at gmail.com  Sat Mar 24 17:09:34 2018
From: richard.holt at gmail.com (Richard)
Date: Sat, 24 Mar 2018 17:09:34 -0400
Subject: [docs] broken links https://docs.python.org/3.5/download.html
In-Reply-To: <CAA8fd_tE0Yz=efztyw0kjCWZzQ+4OPRd0qTHUk=p362P1kNdZg@mail.gmail.com>
References: <CAA8fd_tE0Yz=efztyw0kjCWZzQ+4OPRd0qTHUk=p362P1kNdZg@mail.gmail.com>
Message-ID: <CAA8fd_s7BmQWqZDM-bBn3OX95Fx8ojvZFtuXr9mnVqGMx8Ef=A@mail.gmail.com>

Never mind.
Apologies.
It wanted right click to download.
PEBKAC error.
Thanks for reading.

Richard.

2018-03-24 17:05 GMT-04:00 Richard <richard.holt at gmail.com>:

> All of the links of the 3.5 docs seem to be broken.
> I tried them all.
> That's the version installed in my Debian based linux.
>
> Minimal internet access at present.
> Email via cell data plan.
>
> Thanks and regards,
> Richard.
> richard.holt at gmail.com
> Venezuela.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180324/0a5189ff/attachment-0001.html>

From szzhao at sei.ecnu.edu.cn  Mon Mar 26 05:06:56 2018
From: szzhao at sei.ecnu.edu.cn (=?GBK?B?1dTKwNbS?=)
Date: Mon, 26 Mar 2018 17:06:56 +0800
Subject: [docs] Python's bugs on numerical calculation
Message-ID: <180326170656242114001273@sei.ecnu.edu.cn>

To whom it may concern,

    Hello, I am Shizhong Zhao, and work at East China Normal University. My major is Computer Arithmetic. I know that numerical calculation is unstable in most of the softwares. 

   Please read the attachment.

Yours Sincerely,
Shizhong Zhao



----------------Here is an error-controlled calculator? http://www.zhaoshizhong.org/download.htm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180326/8a436609/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: final.pdf
Type: application/pdf
Size: 380650 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180326/8a436609/attachment-0001.pdf>

From wangdi03 at ppdai.com  Tue Mar 20 05:32:00 2018
From: wangdi03 at ppdai.com (=?gb2312?B?zfW1zw==?=)
Date: Tue, 20 Mar 2018 09:32:00 +0000
Subject: [docs] a doc bug in itertools.islice
In-Reply-To: <SH2PR01MB218AAB3FFD3814A750DB4D6C8AB0@SH2PR01MB218.CHNPR01.prod.partner.outlook.cn>
References: <SH2PR01MB218AAB3FFD3814A750DB4D6C8AB0@SH2PR01MB218.CHNPR01.prod.partner.outlook.cn>
Message-ID: <SH2PR01MB218425E8497539A6EF42718C8AB0@SH2PR01MB218.CHNPR01.prod.partner.outlook.cn>

Hi!
I found a bug in https://docs.python.org/3/library/itertools.html, where the argument should be ?seq, start, [stop, step].?which makes me puzzled for the example.
[cid:image001.png at 01D3C071.391FD020]
Thanks.
---------------------------------
Best regards?
Andy Wang


E-mail:   wangdi03 at ppdai.com<mailto:wangdi03 at ppdai.com>
Website:  www.ppdai.com<http://www.ppdai.com>


********************************************************************************

?????????????????????????????????????????????????????????????????????????????????????????????????????????????

This E-mail and any attachments are confidential and intended solely for the addressees. If you receive this E-mail in error, please delete it and immediately notify the sender. If the reader of this E-mail is not the intended recipient, you are hereby notified that any unauthorized use, copying or dissemination is prohibited. Please delete this E-mail and all its attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180320/6fb5a56a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5170 bytes
Desc: image001.png
URL: <http://mail.python.org/pipermail/docs/attachments/20180320/6fb5a56a/attachment.png>

From report at bugs.python.org  Mon Mar 26 09:49:48 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 26 Mar 2018 13:49:48 +0000
Subject: [docs] [issue24024] str.__doc__ needs an update
In-Reply-To: <1429708426.75.0.208318155296.issue24024@psf.upfronthosting.co.za>
Message-ID: <1522072188.34.0.467229070634.issue24024@psf.upfronthosting.co.za>


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

The current docstring is correct. The signature str(object, encoding="utf-8", errors="strict") is not correct, because str(object) is not the same as str(object, encoding="utf-8", errors="strict").

>>> str([1, 2])
'[1, 2]'
>>> str([1, 2], encoding="utf-8", errors="strict")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: decoding to str: need a bytes-like object, list found
>>> str(b'abc')
__main__:1: BytesWarning: str() on a bytes instance
"b'abc'"
>>> str(b'abc', encoding="utf-8", errors="strict")
'abc'

----------
nosy: +serhiy.storchaka
status: open -> pending

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

From report at bugs.python.org  Mon Mar 26 11:01:36 2018
From: report at bugs.python.org (Scott Eilerman)
Date: Mon, 26 Mar 2018 15:01:36 +0000
Subject: [docs] [issue33114] random.sample() behavior is unexpected/unclear
 from docs
In-Reply-To: <1521643977.18.0.467229070634.issue33114@psf.upfronthosting.co.za>
Message-ID: <1522076496.27.0.467229070634.issue33114@psf.upfronthosting.co.za>


Scott Eilerman <scott.j.eilerman at gmail.com> added the comment:

Raymond, Tim, thanks for your replies so far. I understand (and for the most part, agree with) your points about not being able to list every behavior, and not wanting to cause uncertainty in users. However, let me argue my case one more time, and if you still disagree, feel free to close this.

1. It is expected (in fact, one might argue it's the entire point) that initializing random.seed() with a fixed value will produce a repeatable set of results for a traditional random number generator. An user expects that calling the following should always produce the same sequence of numbers:

random.seed(22)
random.random()
random.random()
random.random()

2. Based on that behavior for one of the most typical/traditional functions in the random module, a naive user (me) might assume that random.sample() is drawing from its population in a similar manner (i.e. that sequence of returned items, regardless of how many you ask the function to return, is uniquely determined by the seed). While this is certainly an assumption...

2a. This assumption is somewhat validated by the introductory section of the random module docs, which states "Almost all module functions depend on the basic function random()..."

2b. More importantly, an user can "validate" this assumption by doing some simple tests, e.g.:

choices = range(100)
random.seed(22)
random.sample(choices,1)
random.seed(22)
random.sample(choices,2)
random.seed(22)
random.sample(choices,3)
... and so on

Because of the nature of the set/list optimization, it is VERY possible that an user could do due diligence in testing like this (a few different seeds, a few different sets of "choices", testing up to k=10) and never uncover the problematic behavior. You'd pretty much have to set up some loops like I did earlier in this thread, which I don't think many users would do unless the expect to find a problem. Even then, with certain selections of "choices", you might still get the "expected" results.

2c. If you suspected a problem, or really wanted to be sure the function does what you assume it will do, obviously you can open up random.py and take a look. However, I doubt many users do this for every built-in module and function they use; clearly the point of documentation is to avoid this scenario.

3. As Raymond mentioned, this does not appear to be a "common" problem, and perhaps that is enough to not add anything to the docs. However, due to the somewhat elusive nature of the behavior, it could certainly go undetected in many cases, potentially causing problems without anyone noticing. Perhaps I chose a very unorthodox implementation to get the results I desired; I easily could have used random.shuffle() or random.sample(pop, len(pop)) and picked the nth element. However, one could imagine cases in which you have a very large population and you want to optimize by using sample() to get the nth random draw rather than randomizing the entire list, so I don't think it's an entirely unjustified approach.

4. Given the above points, I'd argue that a one-line insertion into the docs would help users steer clear of a hard-to-anticipate, potentially costly pitfall. My suggested language is a more direct identification of the possible consequences, though I agree that it it perhaps too worry-inducing without specifying the "cause" of the problem. Raymond's algorithmic note may be a better choice and would have been enough of an indicator for me to avoid the mistake I made.

----------

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

From report at bugs.python.org  Mon Mar 26 11:02:21 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 26 Mar 2018 15:02:21 +0000
Subject: [docs] [issue31504] Documentation for return value for
 string.rindex is missing when search string is empty
In-Reply-To: <1505721887.17.0.00733091873512.issue31504@psf.upfronthosting.co.za>
Message-ID: <1522076541.04.0.714561066657.issue31504@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Mar 26 11:24:20 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 26 Mar 2018 15:24:20 +0000
Subject: [docs] [issue31201] make test: module test that failed doesn't exist
In-Reply-To: <1502707428.17.0.905101363291.issue31201@psf.upfronthosting.co.za>
Message-ID: <1522077860.58.0.714561066657.issue31201@psf.upfronthosting.co.za>


Change by Cheryl Sabella <chekat2 at gmail.com>:


----------
keywords: +easy
stage:  -> needs patch
title: module test that failed doesn't exist -> make test: module test that failed doesn't exist
type:  -> enhancement
versions: +Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Mar 26 11:57:26 2018
From: report at bugs.python.org (Steven Downum)
Date: Mon, 26 Mar 2018 15:57:26 +0000
Subject: [docs] [issue24356] venv documentation incorrect / misleading
In-Reply-To: <1433197293.5.0.203233804739.issue24356@psf.upfronthosting.co.za>
Message-ID: <1522079846.5.0.714561066657.issue24356@psf.upfronthosting.co.za>


Change by Steven Downum <devilaether at gmail.com>:


----------
nosy: +steven.downum

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

From report at bugs.python.org  Mon Mar 26 15:36:01 2018
From: report at bugs.python.org (Mark Dickinson)
Date: Mon, 26 Mar 2018 19:36:01 +0000
Subject: [docs] [issue4819] Misc/cheatsheet needs updating
In-Reply-To: <1230988594.32.0.497089911482.issue4819@psf.upfronthosting.co.za>
Message-ID: <1522092961.38.0.467229070634.issue4819@psf.upfronthosting.co.za>


Mark Dickinson <dickinsm at gmail.com> added the comment:

Given that Misc/cheatsheet doesn't exist any more in the Python 3 repo, and Python 2 is nearing end-of-life, I suspect this should just be closed.

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

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

From report at bugs.python.org  Mon Mar 26 20:54:28 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 27 Mar 2018 00:54:28 +0000
Subject: [docs] [issue33114] random.sample() behavior is unexpected/unclear
 from docs
In-Reply-To: <1521643977.18.0.467229070634.issue33114@psf.upfronthosting.co.za>
Message-ID: <1522112067.98.0.467229070634.issue33114@psf.upfronthosting.co.za>


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

>  However, let me argue my case one more time, and if you still disagree, feel free to close this.

Thank you for expressing your ideas so clearly.  However, I'm going to go with Tim's recommendation and leave the docs as is.

At this point, you already have a complete understanding of what the tool does and how to use it, so there isn't anything at stake other than a feeling a vindication for a bug that is already resolved.  Looking to the needs of other users, I think we're best off not even bringing up non-guaranteed implementation details and instead follow the example of Numpy and R.  Thanks again for the suggestion, but we'll respectfully decline this time around.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Mar 26 21:29:36 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 27 Mar 2018 01:29:36 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1522114176.36.0.467229070634.issue27212@psf.upfronthosting.co.za>


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


New changeset da1734c58d2f97387ccc9676074717d38b044128 by Raymond Hettinger (Cheryl Sabella) in branch 'master':
bpo-27212: Modify islice recipe to consume initial values preceding start (GH-6195)
https://github.com/python/cpython/commit/da1734c58d2f97387ccc9676074717d38b044128


----------

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

From report at bugs.python.org  Mon Mar 26 21:30:51 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 27 Mar 2018 01:30:51 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1522114251.66.0.714561066657.issue27212@psf.upfronthosting.co.za>


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


----------
pull_requests: +5991

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

From report at bugs.python.org  Mon Mar 26 21:31:43 2018
From: report at bugs.python.org (miss-islington)
Date: Tue, 27 Mar 2018 01:31:43 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1522114303.92.0.714561066657.issue27212@psf.upfronthosting.co.za>


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


----------
pull_requests: +5992

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

From report at bugs.python.org  Mon Mar 26 22:23:36 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 27 Mar 2018 02:23:36 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1522117416.81.0.467229070634.issue27212@psf.upfronthosting.co.za>


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


New changeset f328caf4caafd4521c356af8cb8a299f27603c90 by Raymond Hettinger (Miss Islington (bot)) in branch '3.7':
bpo-27212: Modify islice recipe to consume initial values preceding start (GH-6195) (#GH-6266)
https://github.com/python/cpython/commit/f328caf4caafd4521c356af8cb8a299f27603c90


----------

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

From report at bugs.python.org  Mon Mar 26 22:24:04 2018
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 27 Mar 2018 02:24:04 +0000
Subject: [docs] [issue27212] Doc for itertools,
 'islice()' implementation have unwanted behavior for recipe
 'consume()'
In-Reply-To: <1465018426.98.0.63725897135.issue27212@psf.upfronthosting.co.za>
Message-ID: <1522117444.91.0.467229070634.issue27212@psf.upfronthosting.co.za>


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


New changeset c8698cff7ccc8dc730c58523c7ef4113ea8d3049 by Raymond Hettinger (Miss Islington (bot)) in branch '3.6':
bpo-27212: Modify islice recipe to consume initial values preceding start (GH-6195) (GH-6267)
https://github.com/python/cpython/commit/c8698cff7ccc8dc730c58523c7ef4113ea8d3049


----------

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

From report at bugs.python.org  Tue Mar 27 05:38:18 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 27 Mar 2018 09:38:18 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1522143498.03.0.467229070634.issue33014@psf.upfronthosting.co.za>


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

I concur with David about the docstring. But I think that no changes are needed in the module documentation. David's wording would contain two links (for iskeyword() and for keyword), and many links distract the attention.

We already spent for this issue more time than it deserves.

----------

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

From report at bugs.python.org  Tue Mar 27 09:41:30 2018
From: report at bugs.python.org (R. David Murray)
Date: Tue, 27 Mar 2018 13:41:30 +0000
Subject: [docs] [issue33014] Clarify str.isidentifier docstring;
 fix keyword.iskeyword docstring
In-Reply-To: <1520351440.06.0.467229070634.issue33014@psf.upfronthosting.co.za>
Message-ID: <1522158090.07.0.467229070634.issue33014@psf.upfronthosting.co.za>


R. David Murray <rdmurray at bitdance.com> added the comment:

I think my wording would be an improvement to the docs as well.  You could link just the keyword function if you are worried about too many links, since that would keep the link count the same.

----------

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

From report at bugs.python.org  Wed Mar 28 07:48:46 2018
From: report at bugs.python.org (Matt Eaton)
Date: Wed, 28 Mar 2018 11:48:46 +0000
Subject: [docs] [issue33167] RFC Documentation Updates to urllib.parse.rst
Message-ID: <1522237726.19.0.467229070634.issue33167@psf.upfronthosting.co.za>


New submission from Matt Eaton <agnosticdev at gmail.com>:

A recent patch that I worked on resulted in an agreement that there could be a use case for a new URL API to be added to urllib.parse.  See: https://bugs.python.org/issue33034

In my research to develop this new API I have been looking at the documentation for urllib.parse -https://docs.python.org/3/library/urllib.parse.html and thought that the descriptions for the RFC documents could use an update to better reflect the meaning of the document.

----------
assignee: docs at python
components: Documentation
messages: 314584
nosy: agnosticdev, docs at python
priority: normal
severity: normal
status: open
title: RFC Documentation Updates to urllib.parse.rst
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/issue33167>
_______________________________________

From report at bugs.python.org  Wed Mar 28 07:53:08 2018
From: report at bugs.python.org (Matt Eaton)
Date: Wed, 28 Mar 2018 11:53:08 +0000
Subject: [docs] [issue33167] RFC Documentation Updates to urllib.parse.rst
In-Reply-To: <1522237726.19.0.467229070634.issue33167@psf.upfronthosting.co.za>
Message-ID: <1522237988.04.0.714561066657.issue33167@psf.upfronthosting.co.za>


Change by Matt Eaton <agnosticdev at gmail.com>:


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

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

From report at bugs.python.org  Wed Mar 28 11:04:28 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Mar 2018 15:04:28 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1522249468.14.0.714561066657.issue33126@psf.upfronthosting.co.za>


Change by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Wed Mar 28 11:04:53 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Mar 2018 15:04:53 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1522249493.02.0.467229070634.issue33126@psf.upfronthosting.co.za>


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

Ok, it seems only PyBuffer_ToContiguous() is worth documenting.

----------

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

From report at bugs.python.org  Wed Mar 28 11:26:37 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Mar 2018 15:26:37 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1522250797.59.0.467229070634.issue33126@psf.upfronthosting.co.za>


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


New changeset aa50bf08e64f49d57917ab0b1aadf4308a3168a6 by Antoine Pitrou in branch 'master':
bpo-33126: Document PyBuffer_ToContiguous() (#6292)
https://github.com/python/cpython/commit/aa50bf08e64f49d57917ab0b1aadf4308a3168a6


----------

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

From report at bugs.python.org  Wed Mar 28 11:27:55 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 28 Mar 2018 15:27:55 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1522250875.18.0.714561066657.issue33126@psf.upfronthosting.co.za>


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


----------
pull_requests: +6017

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

From report at bugs.python.org  Wed Mar 28 11:29:01 2018
From: report at bugs.python.org (miss-islington)
Date: Wed, 28 Mar 2018 15:29:01 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1522250941.45.0.714561066657.issue33126@psf.upfronthosting.co.za>


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


----------
pull_requests: +6018

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

From report at bugs.python.org  Wed Mar 28 11:47:36 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Mar 2018 15:47:36 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1522252056.83.0.467229070634.issue33126@psf.upfronthosting.co.za>


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


New changeset 18fdc87207ea65b3906f07cb47c51a609e442f93 by Antoine Pitrou (Miss Islington (bot)) in branch '3.6':
bpo-33126: Document PyBuffer_ToContiguous() (GH-6292) (GH-6293)
https://github.com/python/cpython/commit/18fdc87207ea65b3906f07cb47c51a609e442f93


----------

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

From report at bugs.python.org  Wed Mar 28 11:50:27 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Mar 2018 15:50:27 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1522252227.19.0.467229070634.issue33126@psf.upfronthosting.co.za>


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


New changeset 6124d8ec0d1eb8016e5e54a4d341b8f4f995623c by Antoine Pitrou (Miss Islington (bot)) in branch '3.7':
bpo-33126: Document PyBuffer_ToContiguous() (GH-6292) (GH-6294)
https://github.com/python/cpython/commit/6124d8ec0d1eb8016e5e54a4d341b8f4f995623c


----------

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

From report at bugs.python.org  Wed Mar 28 11:50:58 2018
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 28 Mar 2018 15:50:58 +0000
Subject: [docs] [issue33126] Some C buffer protocol APIs not documented
In-Reply-To: <1521823746.22.0.467229070634.issue33126@psf.upfronthosting.co.za>
Message-ID: <1522252258.94.0.714561066657.issue33126@psf.upfronthosting.co.za>


Change by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Wed Mar 28 20:32:01 2018
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 29 Mar 2018 00:32:01 +0000
Subject: [docs] [issue32798] mmap.flush() on Linux does not accept the
 "offset" and "size" args
In-Reply-To: <1518102419.01.0.467229070634.issue32798@psf.upfronthosting.co.za>
Message-ID: <1522283521.69.0.467229070634.issue32798@psf.upfronthosting.co.za>


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

By the way, there is a note in the "Change History" section of the msync() documentation at http://pubs.opengroup.org/onlinepubs/9699919799/

    The second [EINVAL] error condition is made mandatory.

The second EINVAL error condition they mention is:

    [EINVAL] The value of addr is not a multiple of the page size as returned by sysconf().

So unless I'm missing something obvious, the "the msync() function may fail if" part may now be outdated?

Also, I noticed that we don't have tests for mm.flush(offset) and mm.flush(offset, size) cases. It would be nice to add some tests even if we decide to not merge the documentation PR.

----------

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

From report at bugs.python.org  Thu Mar 29 15:59:00 2018
From: report at bugs.python.org (Joel Johnson)
Date: Thu, 29 Mar 2018 19:59:00 +0000
Subject: [docs] [issue25433] whitespace in strip()/lstrip()/rstrip()
In-Reply-To: <1445170536.34.0.94220475409.issue25433@psf.upfronthosting.co.za>
Message-ID: <1522353540.48.0.467229070634.issue25433@psf.upfronthosting.co.za>


Joel Johnson <particlemanj2 at gmail.com> added the comment:

I have started working on this and will have a pull request submitted by the end of the week. 

The term "whitespace" appears in several contextual situations throughout the documentation. While all situations would benefit from the definition of "whitespace" contained in the str.isspace() documentation, not all of the situations would benefit from a link to str.isspace() whose primary goal is to document the str.isspace() function and not to provide a global definition of what a whitespace character is.

Therefore I suggest the documentation of Python 3 create a new glossary definition of "whitespace" (which contains the definition currently in the str.isspace() documentation) and is pointed to wherever the term "whitespace" is used in any documentation related to strings - including this specific case of strip()/lstrip()/rstrip().

----------
nosy: +joel.johnson

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

From report at bugs.python.org  Fri Mar 30 02:39:52 2018
From: report at bugs.python.org (Dimitri Papadopoulos Orfanos)
Date: Fri, 30 Mar 2018 06:39:52 +0000
Subject: [docs] [issue25433] whitespace in strip()/lstrip()/rstrip()
In-Reply-To: <1445170536.34.0.94220475409.issue25433@psf.upfronthosting.co.za>
Message-ID: <1522391992.83.0.467229070634.issue25433@psf.upfronthosting.co.za>


Dimitri Papadopoulos Orfanos <dimitri.papadopoulos at gmail.com> added the comment:

I agree on avoiding a link to str.isspace() and defining "whitespace" instead.

However please note there are many de facto definitions of "whitespace". All of them must be documented - or at least the conceptual classes of "whitespace" and clarify which class each of the following belongs to:

* Unicode whitespaces are by very far the most common: str.isspace(), strip()/lstrip()/rstrip(), Py_UNICODE_ISSPACE.

* Py_ISSPACE targets byte/bytearray but is never used!

* bytearray.strip() does not use Py_ISSPACE but a hardcoded list of ASCII whitespaces instead.

* finally string.whitespace is probably equivalent to the list used by bytearray.strip().

Beyond the docs, I think Python 3 should rationalize bytearray.strip() /  Py_ISSPACE / string.whitespace, probably having bytearray.strip() rely on Py_ISSPACE, and Py_ISSPACE rely on string.whitespace unless string.whitespace is obsoleted.

----------

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

From report at bugs.python.org  Fri Mar 30 12:34:54 2018
From: report at bugs.python.org (Stefan Behnel)
Date: Fri, 30 Mar 2018 16:34:54 +0000
Subject: [docs] [issue33187] Document ElementInclude (XInclude) support in
 ElementTree
Message-ID: <1522427694.7.0.467229070634.issue33187@psf.upfronthosting.co.za>


New submission from Stefan Behnel <stefan_ml at behnel.de>:

The ElementInclude module in ElementTree seems undocumented. I couldn't find any documentation in the stdlib docs. Pretty much the only source that I could find is here:

http://effbot.org/zone/element-xinclude.htm

I noticed it while looking for a place to document the changes of #20928.

----------
assignee: docs at python
components: Documentation
messages: 314691
nosy: docs at python, scoder
priority: normal
severity: normal
status: open
title: Document ElementInclude (XInclude) support in ElementTree
type: enhancement

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

From report at bugs.python.org  Fri Mar 30 16:33:28 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 30 Mar 2018 20:33:28 +0000
Subject: [docs] [issue33130] functools.reduce signature/docstring discordance
In-Reply-To: <1521849944.24.0.467229070634.issue33130@psf.upfronthosting.co.za>
Message-ID: <1522442008.07.0.467229070634.issue33130@psf.upfronthosting.co.za>


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

inspect.signature(functools.reduce) raises, so I presume you mean the header for the reduce entry at
https://docs.python.org/3/library/functools.html#functools.reduce.  The first line of the docstring, functools.reduce.__doc__, also displayed by help(functools.reduce) has an old version of the signature, which disagrees also on the 3rd parameter name. 
doc header: functools.reduce(function, iterable[, initializer])
.__doc__:   reduce(function, sequence[, initial]) -> value

The current PR only touches the body of the doc entry, not what we call the docstring.  It replaces 'sequence' with 'iterable'.

Functools does not have a Python-coded backup for the C-coded reduce, which only accepts arguments by position.  I have not looked at the C code, whose names are not accessible from Python.  The doc and docstring should match, and should use the parameter names we would want to use of args were ever passed by name.  So I think the docstring (in the C code) should be changed to match the doc.

There should really be a '/,' to indicate that args must be passed by position, or do we only use that in ArgClinic signatures (which show up in help output)?

----------
nosy: +terry.reedy

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

From report at bugs.python.org  Fri Mar 30 16:47:47 2018
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 30 Mar 2018 20:47:47 +0000
Subject: [docs] [issue33147] Update references for RFC 3548 to RFC 4648
In-Reply-To: <1522082721.06.0.467229070634.issue33147@psf.upfronthosting.co.za>
Message-ID: <1522442867.33.0.467229070634.issue33147@psf.upfronthosting.co.za>


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

Ewa handles recording of CAs.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +Ewa.Jodlowska, docs at python, terry.reedy
stage:  -> patch review
versions: +Python 3.8

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

From report at bugs.python.org  Fri Mar 30 22:13:41 2018
From: report at bugs.python.org (Zackery Spytz)
Date: Sat, 31 Mar 2018 02:13:41 +0000
Subject: [docs] [issue23495] The writer.writerows method should be
 documented as accepting any iterable (not only a list)
In-Reply-To: <1424465153.78.0.58816335685.issue23495@psf.upfronthosting.co.za>
Message-ID: <1522462421.66.0.714561066657.issue23495@psf.upfronthosting.co.za>


Change by Zackery Spytz <zspytz at gmail.com>:


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

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

From report at bugs.python.org  Fri Mar 30 22:26:04 2018
From: report at bugs.python.org (Zackery Spytz)
Date: Sat, 31 Mar 2018 02:26:04 +0000
Subject: [docs] [issue23495] The writer.writerows method should be
 documented as accepting any iterable (not only a list)
In-Reply-To: <1424465153.78.0.58816335685.issue23495@psf.upfronthosting.co.za>
Message-ID: <1522463164.09.0.467229070634.issue23495@psf.upfronthosting.co.za>


Zackery Spytz <zspytz at gmail.com> added the comment:

Commit 7901b48a1f89b9bfa9d111ae3725400b466a9baa removed the unnecessary list conversion (3.5+), but the documentation issue remains.

----------
nosy: +ZackerySpytz
versions: +Python 3.6, Python 3.7, Python 3.8 -Python 3.4, Python 3.5

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

From report at bugs.python.org  Sat Mar 31 08:23:32 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 31 Mar 2018 12:23:32 +0000
Subject: [docs] [issue31544] gettext.Catalog title is not flagged as a class
In-Reply-To: <1506007626.15.0.9927755066.issue31544@psf.upfronthosting.co.za>
Message-ID: <1522499012.86.0.467229070634.issue31544@psf.upfronthosting.co.za>


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


New changeset c498cd8bf81fc47acf2f1f702e8b3bc9bd4aed65 by Serhiy Storchaka (scoder) in branch '2.7':
bpo-31544: Fix a reference leak to 'self' after the previous target error handling fixes. (GH-6318)
https://github.com/python/cpython/commit/c498cd8bf81fc47acf2f1f702e8b3bc9bd4aed65


----------

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

From report at bugs.python.org  Sat Mar 31 08:28:02 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 31 Mar 2018 12:28:02 +0000
Subject: [docs] [issue31544] gettext.Catalog title is not flagged as a class
In-Reply-To: <1506007626.15.0.9927755066.issue31544@psf.upfronthosting.co.za>
Message-ID: <1522499282.33.0.467229070634.issue31544@psf.upfronthosting.co.za>


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

The correct issue for 0694b6a651ba2a53f6323ffb3b23358f43885815 and c498cd8bf81fc47acf2f1f702e8b3bc9bd4aed65 is issue31455.

----------

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

From report at bugs.python.org  Sat Mar 31 08:29:13 2018
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 31 Mar 2018 12:29:13 +0000
Subject: [docs] [issue31544] gettext.Catalog title is not flagged as a class
In-Reply-To: <1506007626.15.0.9927755066.issue31544@psf.upfronthosting.co.za>
Message-ID: <1522499353.64.0.714561066657.issue31544@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Mar 31 16:57:20 2018
From: report at bugs.python.org (Nitish)
Date: Sat, 31 Mar 2018 20:57:20 +0000
Subject: [docs] [issue25433] whitespace in strip()/lstrip()/rstrip()
In-Reply-To: <1445170536.34.0.94220475409.issue25433@psf.upfronthosting.co.za>
Message-ID: <1522529840.36.0.714561066657.issue25433@psf.upfronthosting.co.za>


Change by Nitish <nitishch at protonmail.com>:


----------
nosy: +nitishch

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

From report at bugs.python.org  Sat Mar 31 18:32:24 2018
From: report at bugs.python.org (Jakub Wilk)
Date: Sat, 31 Mar 2018 22:32:24 +0000
Subject: [docs] [issue25433] whitespace in strip()/lstrip()/rstrip()
In-Reply-To: <1445170536.34.0.94220475409.issue25433@psf.upfronthosting.co.za>
Message-ID: <1522535544.03.0.714561066657.issue25433@psf.upfronthosting.co.za>


Change by Jakub Wilk <jwilk at jwilk.net>:


----------
nosy: +jwilk

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

From report at bugs.python.org  Sat Mar 31 20:21:50 2018
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 01 Apr 2018 00:21:50 +0000
Subject: [docs] [issue24978] Contributing to Python 2x and 3x Documentation.
 Translation to Russian.
In-Reply-To: <1441109047.57.0.29993860249.issue24978@psf.upfronthosting.co.za>
Message-ID: <1522542108.18.0.467229070634.issue24978@psf.upfronthosting.co.za>


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

Adding a reference to PEP 545 for contributing documentation translations.

----------
nosy: +csabella

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

From biggs842002-ag at yahoo.com  Tue Mar 27 11:27:23 2018
From: biggs842002-ag at yahoo.com (GBiggs)
Date: Tue, 27 Mar 2018 15:27:23 +0000 (UTC)
Subject: [docs] Python 3.5.5 documentation
References: <1741954631.427005.1522164443171.ref@mail.yahoo.com>
Message-ID: <1741954631.427005.1522164443171@mail.yahoo.com>

Hello. I am trying to download the documentation for Python v3.5.5 for offline usage. However, each attempt results in a 404 error for every available format.

From jessemccarthy at outlook.com  Tue Mar 27 12:54:39 2018
From: jessemccarthy at outlook.com (Jesse McCarthy)
Date: Tue, 27 Mar 2018 16:54:39 +0000
Subject: [docs] Unable to Download Docs (404)
Message-ID: <SN2PR10MB0014BCDAE0E1CD6796272733ADAC0@SN2PR10MB0014.namprd10.prod.outlook.com>

Hello to whomever this may concern; I hope this correspondence finds
you happy and healthy.

I am currently attempting to download the documentation for Python
3.5.5 @?https://docs.python.org/3.5/download.html. All of available
links lead to the 404 page shown in the attached image.

It's possible that the directory containing the files was moved or
renamed on the server and the web-page does not yet reflect those
changes.

I would sincerely appreciate an email if/when this is fixed, or if
there is an external source that I may get these files from.

Thank you for your time and consideration.

Regards,
Jesse.

?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Pydocs-404.png
Type: image/png
Size: 164288 bytes
Desc: Pydocs-404.png
URL: <http://mail.python.org/pipermail/docs/attachments/20180327/38c804d6/attachment-0001.png>

From marcospdaveiga at gmail.com  Tue Mar 27 13:01:43 2018
From: marcospdaveiga at gmail.com (Marcos Da Veiga)
Date: Tue, 27 Mar 2018 14:01:43 -0300
Subject: [docs] Bug
Message-ID: <A38B0F87-F7EB-43D4-9E92-C72B0CA1179E@gmail.com>

Hi, everytime what i do ? or ? my IDLE close automatically. I have a MacBook Pro 2017 and a Phyton Version 3.6.0

Atte. Marcos Paulo da Veiga from Paraguay

From rahbarm at gmail.com  Tue Mar 27 23:41:40 2018
From: rahbarm at gmail.com (Rahbar Maghsoudi)
Date: Tue, 27 Mar 2018 22:41:40 -0500
Subject: [docs] missing break statement in one of the examples on prime
 numbers.
Message-ID: <CAAqcCVx9DQG4a6uuQKDnQC-AEnjrQ1q9TQJxMjomUZ_YXeJK8w@mail.gmail.com>

Greetings,
I noticed  a minor mistake in one of the examples in the program to find
prime numbers in the range(2,10)
After the print statement, we a need a break to prevent multiple prints.

You can find the example under the following section with link given there.

4.4. break and continue Statements, and else Clauses on Loops?

https://docs.python.org/3/tutorial/controlflow.html#if-statements

Kind regards,
Rahbar

-- 
Rahbar Maghsoudi, D.Phil. (Oxon), P.E.

This e-mail and any files transmitted with it may contain privileged and
confidential information and are intended solely for the use of the
individual or entity to which they are addressed. If you are not the
intended recipient or the person responsible for delivering the e-mail to
the intended recipient, you are hereby notified that any dissemination or
copying of this e-mail or any of its attachment(s) is strictly prohibited.
If you have received this e-mail in error, please immediately notify the
sending individual or entity by e-mail and permanently delete the original
e-mail and attachment(s) from your computer system. Thank you for your
cooperation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180327/11fce562/attachment.html>

From sbp1825 at gmail.com  Sat Mar 31 02:47:30 2018
From: sbp1825 at gmail.com (Smit Patel)
Date: Sat, 31 Mar 2018 12:17:30 +0530
Subject: [docs] Python Issue
Message-ID: <5A7F905C-BD3F-4A7D-8BA4-002E9626326D@gmail.com>

I have an Issue with my python 3.6.5.
I installed a module named pandas and I am not able to run program with importing this module pandas
This is my code






This is the error which I am getting.
Please help to solve it.















-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180331/acf98ad7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: code.jpg
Type: image/jpeg
Size: 3689831 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180331/acf98ad7/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: error.jpg
Type: image/jpeg
Size: 2758685 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20180331/acf98ad7/attachment-0003.jpg>

From yearofthesheep at gmail.com  Sat Mar 31 16:04:46 2018
From: yearofthesheep at gmail.com (k chang)
Date: Sat, 31 Mar 2018 16:04:46 -0400
Subject: [docs] Python 3.5 Doc Download URL Issues
Message-ID: <CACSb1e49avKJa7KuiFNhxpQB_aBeUR7ZYjafVvXjG3RNpZMXKA@mail.gmail.com>

Hi Python Docs team

I am trying to download Python 3.5 documentation pdfs from
https://docs.python.org/3.5/download.html
However, it seems the file is no longer there due to 404 issues. Could you
send me the PDF (A4 paper size)  pdf, repair the link or link me to a new
working link?

All the best,
Bruce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180331/13ccaceb/attachment.html>

From zavalaat at hotmail.com  Tue Mar 27 20:59:47 2018
From: zavalaat at hotmail.com (Art Zavala)
Date: Wed, 28 Mar 2018 00:59:47 +0000
Subject: [docs] 3.1.1. Numbers
Message-ID: <DM5PR1901MB208781E26A7BABB76EC7BB94DBA30@DM5PR1901MB2087.namprd19.prod.outlook.com>

In interactive mode, the last printed expression is assigned to the variable _

Should expression be expression result?


>>> tax = 12.5 / 100
>>> price = 100.50
>>> price * tax
12.5625
>>> price + _
113.0625
>>> round(_, 2)
113.06

>>> tax * _  is not the same as  tax * price in the third statement!


Regards,

ART T ZAVALA




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