From report at bugs.python.org  Thu Aug  1 10:17:57 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 01 Aug 2019 14:17:57 +0000
Subject: [docs] [issue37726] Tutorial should not recommend getopt
In-Reply-To: <1564546690.91.0.192257836854.issue37726@roundup.psfhosted.org>
Message-ID: <1564669077.29.0.263810682785.issue37726@roundup.psfhosted.org>


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


New changeset 2491134029b195d3159a489e1803ee22a7839b41 by Guido van Rossum (mental) in branch 'master':
bpo-37726: Prefer argparse over getopt in stdlib tutorial (#15052)
https://github.com/python/cpython/commit/2491134029b195d3159a489e1803ee22a7839b41


----------

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

From report at bugs.python.org  Thu Aug  1 10:19:06 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 01 Aug 2019 14:19:06 +0000
Subject: [docs] [issue37726] Tutorial should not recommend getopt
In-Reply-To: <1564546690.91.0.192257836854.issue37726@roundup.psfhosted.org>
Message-ID: <1564669146.04.0.424197408381.issue37726@roundup.psfhosted.org>


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


----------
pull_requests: +14816
pull_request: https://github.com/python/cpython/pull/15069

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

From report at bugs.python.org  Thu Aug  1 10:19:15 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 01 Aug 2019 14:19:15 +0000
Subject: [docs] [issue37726] Tutorial should not recommend getopt
In-Reply-To: <1564546690.91.0.192257836854.issue37726@roundup.psfhosted.org>
Message-ID: <1564669155.91.0.743830831573.issue37726@roundup.psfhosted.org>


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


----------
pull_requests: +14817
pull_request: https://github.com/python/cpython/pull/15070

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

From report at bugs.python.org  Thu Aug  1 10:35:04 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 01 Aug 2019 14:35:04 +0000
Subject: [docs] [issue37726] Tutorial should not recommend getopt
In-Reply-To: <1564546690.91.0.192257836854.issue37726@roundup.psfhosted.org>
Message-ID: <1564670104.35.0.199229875129.issue37726@roundup.psfhosted.org>


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


New changeset dcc53ebbff384076b0763c1f842966c189417071 by Guido van Rossum (Miss Islington (bot)) in branch '3.8':
bpo-37726: Prefer argparse over getopt in stdlib tutorial (GH-15052) (#15070)
https://github.com/python/cpython/commit/dcc53ebbff384076b0763c1f842966c189417071


----------

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

From report at bugs.python.org  Thu Aug  1 10:35:23 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 01 Aug 2019 14:35:23 +0000
Subject: [docs] [issue37726] Tutorial should not recommend getopt
In-Reply-To: <1564546690.91.0.192257836854.issue37726@roundup.psfhosted.org>
Message-ID: <1564670123.57.0.165563217091.issue37726@roundup.psfhosted.org>


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


New changeset 8990ac0ab0398bfb9c62031288030fe7c630c2c7 by Guido van Rossum (Miss Islington (bot)) in branch '3.7':
bpo-37726: Prefer argparse over getopt in stdlib tutorial (GH-15052) (#15069)
https://github.com/python/cpython/commit/8990ac0ab0398bfb9c62031288030fe7c630c2c7


----------

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

From report at bugs.python.org  Thu Aug  1 10:36:25 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 01 Aug 2019 14:36:25 +0000
Subject: [docs] [issue37726] Tutorial should not recommend getopt
In-Reply-To: <1564546690.91.0.192257836854.issue37726@roundup.psfhosted.org>
Message-ID: <1564670185.41.0.090343521796.issue37726@roundup.psfhosted.org>


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

Thanks mental! All done.

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

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

From report at bugs.python.org  Thu Aug  1 10:36:53 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Thu, 01 Aug 2019 14:36:53 +0000
Subject: [docs] [issue37726] Tutorial should not recommend getopt
In-Reply-To: <1564546690.91.0.192257836854.issue37726@roundup.psfhosted.org>
Message-ID: <1564670213.7.0.816801737404.issue37726@roundup.psfhosted.org>


Change by Guido van Rossum <guido at python.org>:


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

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

From report at bugs.python.org  Thu Aug  1 14:47:05 2019
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 01 Aug 2019 18:47:05 +0000
Subject: [docs] [issue37741] importlib.metadata docs not showing up in the
 module index
Message-ID: <1564685225.86.0.948746560612.issue37741@roundup.psfhosted.org>


New submission from Brett Cannon <brett at python.org>:

If you look at https://docs.python.org/3.9/py-modindex.html#cap-i you will see that importlib.metadata isn't listed (same goes for the 3.8 docs).

Or are you leaving it out due to it being provisional?

----------
assignee: docs at python
components: Documentation
messages: 348872
nosy: barry, brett.cannon, docs at python, jaraco
priority: normal
severity: normal
status: open
title: importlib.metadata docs not showing up in the module index
versions: Python 3.8, Python 3.9

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

From report at bugs.python.org  Thu Aug  1 15:51:49 2019
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Thu, 01 Aug 2019 19:51:49 +0000
Subject: [docs] [issue37741] importlib.metadata docs not showing up in the
 module index
In-Reply-To: <1564685225.86.0.948746560612.issue37741@roundup.psfhosted.org>
Message-ID: <1564689109.23.0.661997058183.issue37741@roundup.psfhosted.org>


Fred L. Drake, Jr. <fdrake at gmail.com> added the comment:

Provisional status should not cause a module or other API element to be omitted from the indexes.  So long as it's marked provisional where it's described, it should be locatable.

----------
nosy: +fdrake

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

From report at bugs.python.org  Fri Aug  2 18:41:19 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 02 Aug 2019 22:41:19 +0000
Subject: [docs] [issue34564] Tutorial Section 2.1 Windows Installation Path
 Correction
In-Reply-To: <1535912620.22.0.56676864532.issue34564@psf.upfronthosting.co.za>
Message-ID: <1564785679.65.0.139742963128.issue34564@roundup.psfhosted.org>


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

I updated this section in a separate issue.

----------
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Aug  2 18:44:27 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 02 Aug 2019 22:44:27 +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: <1564785867.83.0.447495926342.issue30974@roundup.psfhosted.org>


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


New changeset 8e568ef266a2805f9a6042003723d9c050830461 by Steve Dower (Timo Furrer) in branch 'master':
bpo-30974: Change os.path.samefile docstring to match docs (GH-7337)
https://github.com/python/cpython/commit/8e568ef266a2805f9a6042003723d9c050830461


----------

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

From report at bugs.python.org  Fri Aug  2 18:44:51 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 02 Aug 2019 22:44:51 +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: <1564785891.74.0.411368733029.issue30974@roundup.psfhosted.org>


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


----------
pull_requests: +14831
pull_request: https://github.com/python/cpython/pull/15086

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

From report at bugs.python.org  Fri Aug  2 18:44:57 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 02 Aug 2019 22:44:57 +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: <1564785897.45.0.216395278754.issue30974@roundup.psfhosted.org>


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


----------
pull_requests: +14832
pull_request: https://github.com/python/cpython/pull/15087

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

From report at bugs.python.org  Fri Aug  2 18:46:09 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 02 Aug 2019 22:46:09 +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: <1564785969.28.0.615226064301.issue30974@roundup.psfhosted.org>


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

I'm not personally thrilled about it being documented like this, but it's certainly how the current documentation reads. Consistency is better until we get motivated enough to fix all of it.

Thanks for the patch!

----------
stage: patch review -> backport needed

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

From report at bugs.python.org  Fri Aug  2 18:46:38 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 02 Aug 2019 22:46:38 +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: <1564785998.4.0.690221695858.issue30974@roundup.psfhosted.org>


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

Still needs a 2.7 backport if someone would like to do it.

----------

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

From report at bugs.python.org  Fri Aug  2 18:47:32 2019
From: report at bugs.python.org (Steve Dower)
Date: Fri, 02 Aug 2019 22:47:32 +0000
Subject: [docs] [issue34142] Windows launcher version lookup flawed
In-Reply-To: <1531879775.21.0.56676864532.issue34142@psf.upfronthosting.co.za>
Message-ID: <1564786052.87.0.592440795349.issue34142@roundup.psfhosted.org>


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


----------
versions: +Python 3.8, Python 3.9

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

From report at bugs.python.org  Fri Aug  2 19:04:57 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 02 Aug 2019 23:04:57 +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: <1564787097.13.0.898950557143.issue30974@roundup.psfhosted.org>


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


New changeset 6b833901fe9053937c289c6371bb731c9aceb58e by Miss Islington (bot) in branch '3.8':
bpo-30974: Change os.path.samefile docstring to match docs (GH-7337)
https://github.com/python/cpython/commit/6b833901fe9053937c289c6371bb731c9aceb58e


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

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

From report at bugs.python.org  Fri Aug  2 19:11:36 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 02 Aug 2019 23:11:36 +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: <1564787496.77.0.394356330158.issue30974@roundup.psfhosted.org>


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


New changeset a49f203e052c6fb1244d4e55c3fccc439dda0e2e by Miss Islington (bot) in branch '3.7':
bpo-30974: Change os.path.samefile docstring to match docs (GH-7337)
https://github.com/python/cpython/commit/a49f203e052c6fb1244d4e55c3fccc439dda0e2e


----------

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

From report at bugs.python.org  Sat Aug  3 04:10:30 2019
From: report at bugs.python.org (Greg Price)
Date: Sat, 03 Aug 2019 08:10:30 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1564819830.63.0.85225382037.issue36502@roundup.psfhosted.org>


Change by Greg Price <gnprice at gmail.com>:


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

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

From report at bugs.python.org  Sat Aug  3 04:18:56 2019
From: report at bugs.python.org (Greg Price)
Date: Sat, 03 Aug 2019 08:18:56 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1564820336.45.0.44310060774.issue36502@roundup.psfhosted.org>


Greg Price <gnprice at gmail.com> added the comment:

The actual behavior turns out to match that comment. See attached PR, which adds a test confirming that and also corrects the documentation.

(A related issue is #18236 -- we should probably adjust the definition to match the one Unicode now provides. But meanwhile we'll want to correct the docs.)

----------
nosy: +Greg Price

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

From report at bugs.python.org  Sat Aug  3 04:54:37 2019
From: report at bugs.python.org (hai shi)
Date: Sat, 03 Aug 2019 08:54:37 +0000
Subject: [docs] [issue37750] PyBuffer_FromContiguous not documented
Message-ID: <1564822477.7.0.508122978433.issue37750@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
assignee: docs at python
components: Documentation
nosy: docs at python, shihai1991
priority: normal
severity: normal
status: open
title: PyBuffer_FromContiguous not documented

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

From report at bugs.python.org  Sat Aug  3 04:56:58 2019
From: report at bugs.python.org (hai shi)
Date: Sat, 03 Aug 2019 08:56:58 +0000
Subject: [docs] [issue37750] PyBuffer_FromContiguous not documented
Message-ID: <1564822618.55.0.397769114373.issue37750@roundup.psfhosted.org>


New submission from hai shi <shihai1991 at 126.com>:

as the title said.

----------

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

From report at bugs.python.org  Sat Aug  3 04:58:55 2019
From: report at bugs.python.org (hai shi)
Date: Sat, 03 Aug 2019 08:58:55 +0000
Subject: [docs] [issue37750] PyBuffer_FromContiguous not documented
In-Reply-To: <1564822618.55.0.397769114373.issue37750@roundup.psfhosted.org>
Message-ID: <1564822735.41.0.477096423408.issue37750@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


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

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

From patrick.dunham at markforged.com  Fri Aug  2 14:55:34 2019
From: patrick.dunham at markforged.com (Patrick Dunham)
Date: Fri, 2 Aug 2019 14:55:34 -0400
Subject: [docs] ftplib Line Ending Documentation Discrepancy
Message-ID: <CABK1C8x_hbarLmORSUgok1NbJ2=0b-yFAfFnSi16b55twdK3Fw@mail.gmail.com>

Hi! I think I?ve found a discrepancy in the documentation in Python?s ftplib
.

A comment on line 75 claims that ftplib supports \r, \n, and \r\n line
endings

# Line terminators (we always output CRLF, but accept any of CRLF, CR, LF)

but after attempting to use it to read a 2 MB file with \r line endings off
of an FTP server, this does not appear to be the case. The entire file is
read out as a single ?line? (after increasing the size of FTP.maxline). It
looks like this is intentional, as the the implementation of FTP.retrlines()
and FTP_TLS.retrlines() only strips \n and \r\n (snippet from line 452)

if line[-2:] == CRLF:    line = line[:-2]
elif line[-1:] == '\n':
    line = line[:-1]
callback(line)

Am I missing something? Or just interpreting the documentation wrong? I
know this is not a common occurrence (esp. since RFC 959 states that ASCII
line endings should be \r\n), but it seems confusing, and doesn?t mesh with
Python?s generally excellent universal newline support.

This seems to be the case with the versions of ftplib in Ubuntu 18.04.2?s
distribution of Python 2.7.15+ and Python 3.6.8. The FTP server in question
is run off of an unknown RTOS on a Zumbach ODAC-14XY laser micrometer. I
can provide an example of the file in question if required.
-- 
Cheers,

Patrick Dunham
Scale-Up Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190802/4b91e73f/attachment.html>

From report at bugs.python.org  Sun Aug  4 09:43:39 2019
From: report at bugs.python.org (miss-islington)
Date: Sun, 04 Aug 2019 13:43:39 +0000
Subject: [docs] [issue37730] NotImplemented is used instead of
 NotImplementedError in docs
In-Reply-To: <1564576160.73.0.181501805035.issue37730@roundup.psfhosted.org>
Message-ID: <1564926219.26.0.366234579868.issue37730@roundup.psfhosted.org>


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


New changeset dd5f8abb54923bf2efea51b7a553ca1fca9cad68 by Miss Islington (bot) in branch '3.8':
bpo-37730: Fix usage of NotImplemented instead of NotImplementedError in docs. (GH-15062)
https://github.com/python/cpython/commit/dd5f8abb54923bf2efea51b7a553ca1fca9cad68


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

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

From report at bugs.python.org  Sun Aug  4 09:48:09 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 04 Aug 2019 13:48:09 +0000
Subject: [docs] [issue37730] NotImplemented is used instead of
 NotImplementedError in docs
In-Reply-To: <1564576160.73.0.181501805035.issue37730@roundup.psfhosted.org>
Message-ID: <1564926489.46.0.717370970716.issue37730@roundup.psfhosted.org>


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


----------
pull_requests: +14848
pull_request: https://github.com/python/cpython/pull/15106

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

From report at bugs.python.org  Sun Aug  4 10:06:58 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 04 Aug 2019 14:06:58 +0000
Subject: [docs] [issue37730] NotImplemented is used instead of
 NotImplementedError in docs
In-Reply-To: <1564576160.73.0.181501805035.issue37730@roundup.psfhosted.org>
Message-ID: <1564927618.41.0.41821761417.issue37730@roundup.psfhosted.org>


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


New changeset 8cd630578451a062dcf46fbb21274520ae36c399 by Serhiy Storchaka in branch '3.7':
[3.7] bpo-37730: Fix usage of NotImplemented instead of NotImplementedError in docs. (GH-15062). (GH-15106)
https://github.com/python/cpython/commit/8cd630578451a062dcf46fbb21274520ae36c399


----------

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

From report at bugs.python.org  Mon Aug  5 03:23:40 2019
From: report at bugs.python.org (Tatsuo Sekine)
Date: Mon, 05 Aug 2019 07:23:40 +0000
Subject: [docs] [issue37761] Inaccurate explanation of
 ArgumentParser.add_argument()'s name-or-flags in JA
Message-ID: <1564989820.31.0.707943982318.issue37761@roundup.psfhosted.org>


New submission from Tatsuo Sekine <sekine.t at gmail.com>:

Second sentence of name-or-flags explanation of argparse.ArgumentParser.add_argument() in ja lang. is:

> ?????add_argument() ??1????????????????????????????????
#[1]

while its original English is:

> The first arguments passed to add_argument() must therefore be either a series of flags, or a simple argument name.
# [2]

If I translate Japanese language one back to English, it'd be something:

The first argument passed to add_argument() must therefore be either a list of flags, or a simple argument name.

Japanese one's explanation means, name-or-flags could be either
- "name"
- ["-f", "--flag"]

So, Japanese translation could be improved to clarify that name-of-flags (i.e. first argument*s*) could be either name or *series* (not list) of flags.

Note that, following sentences in the doc have many supporting explanations, and also, there is argparse HOWTO doc with many examples, so this is not critical issue at all.

[1] https://docs.python.org/ja/3/library/argparse.html#name-or-flags
[2] https://docs.python.org/3/library/argparse.html#name-or-flags

----------
assignee: docs at python
components: Documentation
messages: 349031
nosy: Tatsuo Sekine, docs at python
priority: normal
severity: normal
status: open
title: Inaccurate explanation of ArgumentParser.add_argument()'s name-or-flags in JA
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Mon Aug  5 03:27:13 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 05 Aug 2019 07:27:13 +0000
Subject: [docs] [issue37761] Inaccurate explanation of
 ArgumentParser.add_argument()'s name-or-flags in JA
In-Reply-To: <1564989820.31.0.707943982318.issue37761@roundup.psfhosted.org>
Message-ID: <1564990033.7.0.495038271709.issue37761@roundup.psfhosted.org>


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

Japanese translation is tracked as part of GitHub issues at https://github.com/python/python-docs-ja .

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

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

From report at bugs.python.org  Mon Aug  5 03:36:24 2019
From: report at bugs.python.org (Inada Naoki)
Date: Mon, 05 Aug 2019 07:36:24 +0000
Subject: [docs] [issue37761] Inaccurate explanation of
 ArgumentParser.add_argument()'s name-or-flags in JA
In-Reply-To: <1564989820.31.0.707943982318.issue37761@roundup.psfhosted.org>
Message-ID: <1564990584.48.0.440041261522.issue37761@roundup.psfhosted.org>


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


----------
resolution:  -> third party
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Mon Aug  5 05:06:17 2019
From: report at bugs.python.org (David Heiberg)
Date: Mon, 05 Aug 2019 09:06:17 +0000
Subject: [docs] [issue37730] NotImplemented is used instead of
 NotImplementedError in docs
In-Reply-To: <1564576160.73.0.181501805035.issue37730@roundup.psfhosted.org>
Message-ID: <1564995977.27.0.013664861537.issue37730@roundup.psfhosted.org>


Change by David Heiberg <dhdavvie at gmail.com>:


----------
pull_requests: +14872
pull_request: https://github.com/python/cpython/pull/15133

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

From report at bugs.python.org  Mon Aug  5 05:19:32 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 05 Aug 2019 09:19:32 +0000
Subject: [docs] [issue37730] NotImplemented is used instead of
 NotImplementedError in docs
In-Reply-To: <1564576160.73.0.181501805035.issue37730@roundup.psfhosted.org>
Message-ID: <1564996772.68.0.884432317334.issue37730@roundup.psfhosted.org>


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


New changeset 35f9bccd8198330579ecb4b4c503062f8b5da130 by Serhiy Storchaka (David H) in branch '2.7':
[2.7] bpo-37730: Fix usage of NotImplemented instead of NotImplementedError in docs. (GH-15062). (GH-15133)
https://github.com/python/cpython/commit/35f9bccd8198330579ecb4b4c503062f8b5da130


----------

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

From report at bugs.python.org  Mon Aug  5 05:20:17 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 05 Aug 2019 09:20:17 +0000
Subject: [docs] [issue37730] NotImplemented is used instead of
 NotImplementedError in docs
In-Reply-To: <1564576160.73.0.181501805035.issue37730@roundup.psfhosted.org>
Message-ID: <1564996817.58.0.055607275584.issue37730@roundup.psfhosted.org>


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

Thank you for your contribution David!

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

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

From report at bugs.python.org  Mon Aug  5 13:25:49 2019
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 05 Aug 2019 17:25:49 +0000
Subject: [docs] [issue37741] importlib.metadata docs not showing up in the
 module index
In-Reply-To: <1564685225.86.0.948746560612.issue37741@roundup.psfhosted.org>
Message-ID: <1565025949.31.0.993881870813.issue37741@roundup.psfhosted.org>


Barry A. Warsaw <barry at python.org> added the comment:

There's an importlib.metadata.rst file which describes how to use the API, but that doesn't appear to be linked from either the main library ToC or the importlib documentation itself.  I'll see if I can put together a PR to fix this.

----------
assignee: docs at python -> barry

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

From report at bugs.python.org  Mon Aug  5 14:21:33 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 05 Aug 2019 18:21:33 +0000
Subject: [docs] [issue37741] importlib.metadata docs not showing up in the
 module index
In-Reply-To: <1564685225.86.0.948746560612.issue37741@roundup.psfhosted.org>
Message-ID: <1565029293.5.0.199577674352.issue37741@roundup.psfhosted.org>


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

Including a module directive with synopsis as below in importlib.metadata.rst seems to fix this. It would also be good to include a link to source code from the importlib.metadata docs page since it's written in Python.

.. module:: importlib.metadata
   :synopsis: The implementation of the importlib metadata.

**Source code:** :source:`Lib/importlib/metadata/__init__.py`

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

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

From report at bugs.python.org  Mon Aug  5 14:25:39 2019
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 05 Aug 2019 18:25:39 +0000
Subject: [docs] [issue37741] importlib.metadata docs not showing up in the
 module index
In-Reply-To: <1564685225.86.0.948746560612.issue37741@roundup.psfhosted.org>
Message-ID: <1565029539.88.0.585083018564.issue37741@roundup.psfhosted.org>


Barry A. Warsaw <barry at python.org> added the comment:

@jaraco - Why is the code in `Lib/importlib/metadata/__init__.py` instead of `Lib/importlib/metadata.py`?  Is that to make it easier to port between CPython stdlib and the standalone version?

----------

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

From report at bugs.python.org  Mon Aug  5 19:20:31 2019
From: report at bugs.python.org (Jason R. Coombs)
Date: Mon, 05 Aug 2019 23:20:31 +0000
Subject: [docs] [issue37741] importlib.metadata docs not showing up in the
 module index
In-Reply-To: <1564685225.86.0.948746560612.issue37741@roundup.psfhosted.org>
Message-ID: <1565047231.58.0.761172405692.issue37741@roundup.psfhosted.org>


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

> Why is the code in `Lib/importlib/metadata/__init__.py`

Mainly because originally, the code was in multiple modules. I'm happy for it to move into a single file module.

----------

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

From report at bugs.python.org  Tue Aug  6 13:38:00 2019
From: report at bugs.python.org (hai shi)
Date: Tue, 06 Aug 2019 17:38:00 +0000
Subject: [docs] [issue37775] update doc of compileall
Message-ID: <1565113080.48.0.890450145581.issue37775@roundup.psfhosted.org>


New submission from hai shi <shihai1991 at 126.com>:

due to https://github.com/python/cpython/commit/a6b3ec5b6d4f6387820fccc570eea08b9615620d,
we need update invalidation_mode's value from py_compile.PycInvalidationMode.TIMESTAMP to None in compile_xx function.

----------
assignee: docs at python
components: Documentation
messages: 349120
nosy: docs at python, shihai1991
priority: normal
severity: normal
status: open
title: update doc of compileall
versions: Python 3.9

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

From report at bugs.python.org  Tue Aug  6 13:40:23 2019
From: report at bugs.python.org (hai shi)
Date: Tue, 06 Aug 2019 17:40:23 +0000
Subject: [docs] [issue37775] update doc of compileall
In-Reply-To: <1565113080.48.0.890450145581.issue37775@roundup.psfhosted.org>
Message-ID: <1565113223.21.0.757913851796.issue37775@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


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

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

From report at bugs.python.org  Tue Aug  6 17:05:03 2019
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 06 Aug 2019 21:05:03 +0000
Subject: [docs] [issue37775] update doc of compileall
In-Reply-To: <1565113080.48.0.890450145581.issue37775@roundup.psfhosted.org>
Message-ID: <1565125503.96.0.763114819594.issue37775@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Tue Aug  6 17:07:42 2019
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 06 Aug 2019 21:07:42 +0000
Subject: [docs] [issue37741] importlib.metadata docs not showing up in the
 module index
In-Reply-To: <1564685225.86.0.948746560612.issue37741@roundup.psfhosted.org>
Message-ID: <1565125662.44.0.867092250529.issue37741@roundup.psfhosted.org>


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

If there's no porting benefit then let's move it to a single module instead of a package.

----------

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

From report at bugs.python.org  Tue Aug  6 18:04:22 2019
From: report at bugs.python.org (Barry A. Warsaw)
Date: Tue, 06 Aug 2019 22:04:22 +0000
Subject: [docs] [issue37741] importlib.metadata docs not showing up in the
 module index
In-Reply-To: <1565125662.44.0.867092250529.issue37741@roundup.psfhosted.org>
Message-ID: <85E28E2B-3C03-40DB-AF87-03A673C16F39@python.org>


Barry A. Warsaw <barry at python.org> added the comment:

I?ll do a PR for that too.

> On Aug 6, 2019, at 14:07, Brett Cannon <report at bugs.python.org> wrote:
> 
> 
> Brett Cannon <brett at python.org> added the comment:
> 
> If there's no porting benefit then let's move it to a single module instead of a package.
> 
> ----------
> 
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue37741>
> _______________________________________

----------

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

From report at bugs.python.org  Tue Aug  6 18:44:34 2019
From: report at bugs.python.org (Barry A. Warsaw)
Date: Tue, 06 Aug 2019 22:44:34 +0000
Subject: [docs] [issue37741] importlib.metadata docs not showing up in the
 module index
In-Reply-To: <1564685225.86.0.948746560612.issue37741@roundup.psfhosted.org>
Message-ID: <1565131474.23.0.419564354999.issue37741@roundup.psfhosted.org>


Change by Barry A. Warsaw <barry at python.org>:


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

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

From report at bugs.python.org  Tue Aug  6 21:08:28 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 07 Aug 2019 01:08:28 +0000
Subject: [docs] [issue37646] eval() in a list comprehension
In-Reply-To: <1563751465.46.0.439346831661.issue37646@roundup.psfhosted.org>
Message-ID: <1565140108.62.0.252689671348.issue37646@roundup.psfhosted.org>


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


----------
assignee:  -> docs at python
components: +Documentation -Interpreter Core
nosy: +docs at python
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

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

From report at bugs.python.org  Tue Aug  6 21:36:03 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 07 Aug 2019 01:36:03 +0000
Subject: [docs] [issue37741] importlib.metadata docs not showing up in the
 module index
In-Reply-To: <1564685225.86.0.948746560612.issue37741@roundup.psfhosted.org>
Message-ID: <1565141763.05.0.831917176485.issue37741@roundup.psfhosted.org>


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


----------
pull_requests: +14889
pull_request: https://github.com/python/cpython/pull/15154

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

From report at bugs.python.org  Wed Aug  7 00:37:15 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 07 Aug 2019 04:37:15 +0000
Subject: [docs] [issue37004] SequenceMatcher.ratio() noncommutativity not
 well-documented
In-Reply-To: <1558490955.4.0.899055526874.issue37004@roundup.psfhosted.org>
Message-ID: <1565152635.51.0.877850059694.issue37004@roundup.psfhosted.org>


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


New changeset e9cbcd0018abd2a5f2348c45d5c9c4265c4f42dc by Miss Islington (bot) (sweeneyde) in branch 'master':
bpo-37004: Documented asymmetry of string arguments in difflib.SequenceMatcher for ratio method (GH-13482)
https://github.com/python/cpython/commit/e9cbcd0018abd2a5f2348c45d5c9c4265c4f42dc


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

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

From report at bugs.python.org  Wed Aug  7 00:37:21 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 07 Aug 2019 04:37:21 +0000
Subject: [docs] [issue37004] SequenceMatcher.ratio() noncommutativity not
 well-documented
In-Reply-To: <1558490955.4.0.899055526874.issue37004@roundup.psfhosted.org>
Message-ID: <1565152641.81.0.307965623298.issue37004@roundup.psfhosted.org>


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


----------
pull_requests: +14891
pull_request: https://github.com/python/cpython/pull/15157

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

From report at bugs.python.org  Wed Aug  7 00:37:28 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 07 Aug 2019 04:37:28 +0000
Subject: [docs] [issue37004] SequenceMatcher.ratio() noncommutativity not
 well-documented
In-Reply-To: <1558490955.4.0.899055526874.issue37004@roundup.psfhosted.org>
Message-ID: <1565152648.46.0.0816329211872.issue37004@roundup.psfhosted.org>


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


----------
pull_requests: +14892
pull_request: https://github.com/python/cpython/pull/15158

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

From report at bugs.python.org  Wed Aug  7 00:37:34 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 07 Aug 2019 04:37:34 +0000
Subject: [docs] [issue37004] SequenceMatcher.ratio() noncommutativity not
 well-documented
In-Reply-To: <1558490955.4.0.899055526874.issue37004@roundup.psfhosted.org>
Message-ID: <1565152654.84.0.712328422542.issue37004@roundup.psfhosted.org>


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


----------
pull_requests: +14893
pull_request: https://github.com/python/cpython/pull/15159

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

From report at bugs.python.org  Wed Aug  7 03:47:28 2019
From: report at bugs.python.org (SilentGhost)
Date: Wed, 07 Aug 2019 07:47:28 +0000
Subject: [docs] [issue37779] configparser: add documentation about several
 read() behaviour
In-Reply-To: <1565122960.66.0.217084239893.issue37779@roundup.psfhosted.org>
Message-ID: <1565164048.03.0.682922366786.issue37779@roundup.psfhosted.org>


Change by SilentGhost <ghost.adh at runbox.com>:


----------
assignee:  -> docs at python
components: +Documentation -Cross-Build
nosy: +docs at python -Alex.Willmer

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

From report at bugs.python.org  Wed Aug  7 05:00:58 2019
From: report at bugs.python.org (=?utf-8?q?D=C3=A1vid_Nemeskey?=)
Date: Wed, 07 Aug 2019 09:00:58 +0000
Subject: [docs] [issue35786] get_lock() method is not present for Values
 created using multiprocessing.Manager()
In-Reply-To: <1547934632.93.0.223661167179.issue35786@roundup.psfhosted.org>
Message-ID: <1565168458.62.0.854655737827.issue35786@roundup.psfhosted.org>


D?vid Nemeskey <nemeskeyd at gmail.com> added the comment:

Nothing in the documentation says that multiprocessing.Value and the object returned by manager.Value() is any different. Nor is it clear why they should be.

It is perfectly understandable to expect that manager.Value() is actually of type multiprocessing.Value. It is also a valid assumption that the "canonical" way to acquire such objects are from a Manager, not directly. An example that reinforces this assumption is that of the Queue class, which HAS to be created through a Manager, lest we get "RuntimeError: Queue objects should only be shared between processes through inheritance".

In conclusion, I think this is definitely a valid issue. What I am not so sure about is if it is (just) an issue in the documentation or the API itself.

----------
nosy: +nemeskeyd
versions: +Python 3.7

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

From report at bugs.python.org  Wed Aug  7 05:03:56 2019
From: report at bugs.python.org (=?utf-8?q?D=C3=A1vid_Nemeskey?=)
Date: Wed, 07 Aug 2019 09:03:56 +0000
Subject: [docs] [issue35786] get_lock() method is not present for Values
 created using multiprocessing.Manager()
In-Reply-To: <1547934632.93.0.223661167179.issue35786@roundup.psfhosted.org>
Message-ID: <1565168636.78.0.16449865165.issue35786@roundup.psfhosted.org>


D?vid Nemeskey <nemeskeyd at gmail.com> added the comment:

OK, actually: trying to create a multiprocessing.Value object and sharing it between a Pool of processes results in "RuntimeError: Synchronized objects should only be shared between processes through inheritance". So the only way seems to be through a Manager, but its Value() is of a different class?

----------

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

From report at bugs.python.org  Wed Aug  7 08:31:12 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Wed, 07 Aug 2019 12:31:12 +0000
Subject: [docs] [issue37779] configparser: add documentation about several
 read() behaviour
In-Reply-To: <1565122960.66.0.217084239893.issue37779@roundup.psfhosted.org>
Message-ID: <1565181072.3.0.947792353728.issue37779@roundup.psfhosted.org>


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

@St?phane, thanks for suggesting the above documentation.

Feel free to open a pull request here: https://github.com/python/cpython with this draft for review.

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

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

From report at bugs.python.org  Wed Aug  7 08:37:06 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Wed, 07 Aug 2019 12:37:06 +0000
Subject: [docs] [issue37779] configparser: add documentation about several
 read() behaviour
In-Reply-To: <1565122960.66.0.217084239893.issue37779@roundup.psfhosted.org>
Message-ID: <1565181426.53.0.0938362159418.issue37779@roundup.psfhosted.org>


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

I think you can build on the story in the quick start section.

You can build on from the last section that starts with the paragraph:

Now that we have created and saved a configuration file, let?s read it back and explore the data it holds.

As it has some examples on read().

----------

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

From report at bugs.python.org  Wed Aug  7 08:56:36 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Wed, 07 Aug 2019 12:56:36 +0000
Subject: [docs] [issue37438] ConfigParser.set() docs should mention
 allow_no_value
In-Reply-To: <1561713800.79.0.286500391609.issue37438@roundup.psfhosted.org>
Message-ID: <1565182596.59.0.789455865478.issue37438@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Wed Aug  7 11:39:36 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 07 Aug 2019 15:39:36 +0000
Subject: [docs] [issue37004] SequenceMatcher.ratio() noncommutativity not
 well-documented
In-Reply-To: <1558490955.4.0.899055526874.issue37004@roundup.psfhosted.org>
Message-ID: <1565192376.01.0.836077309125.issue37004@roundup.psfhosted.org>


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


New changeset 1a3a40c1cb582e436d568009fae2b06c0b1978ed by Terry Jan Reedy (Miss Islington (bot)) in branch '3.8':
bpo-37004: Documented asymmetry of string arguments in difflib.SequenceMatcher for ratio method (GH-13482) (#15157)
https://github.com/python/cpython/commit/1a3a40c1cb582e436d568009fae2b06c0b1978ed


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

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

From report at bugs.python.org  Wed Aug  7 11:39:52 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 07 Aug 2019 15:39:52 +0000
Subject: [docs] [issue37004] SequenceMatcher.ratio() noncommutativity not
 well-documented
In-Reply-To: <1558490955.4.0.899055526874.issue37004@roundup.psfhosted.org>
Message-ID: <1565192392.53.0.90420184706.issue37004@roundup.psfhosted.org>


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


New changeset 7dafbe81bd0afb8bd67bc3a4c851a6c728fd87fe by Terry Jan Reedy (Miss Islington (bot)) in branch '3.7':
bpo-37004: Documented asymmetry of string arguments in difflib.SequenceMatcher for ratio method (GH-13482) (#15158)
https://github.com/python/cpython/commit/7dafbe81bd0afb8bd67bc3a4c851a6c728fd87fe


----------

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

From report at bugs.python.org  Wed Aug  7 12:13:49 2019
From: report at bugs.python.org (Tim Peters)
Date: Wed, 07 Aug 2019 16:13:49 +0000
Subject: [docs] [issue37004] SequenceMatcher.ratio() noncommutativity not
 well-documented
In-Reply-To: <1558490955.4.0.899055526874.issue37004@roundup.psfhosted.org>
Message-ID: <1565194429.32.0.426685155732.issue37004@roundup.psfhosted.org>


Change by Tim Peters <tim at python.org>:


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

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

From report at bugs.python.org  Wed Aug  7 13:59:59 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Wed, 07 Aug 2019 17:59:59 +0000
Subject: [docs] [issue11165] Document PyEval_Call* functions
In-Reply-To: <1297292171.0.0.0899611103523.issue11165@psf.upfronthosting.co.za>
Message-ID: <1565200799.48.0.553573462539.issue11165@roundup.psfhosted.org>


Jeroen Demeyer <jeroen.k.demeyer at gmail.com> added the comment:

These functions are now officially deprecated, see PR 14804. So I think that this issue can be closed.

----------
nosy: +jdemeyer

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

From report at bugs.python.org  Wed Aug  7 14:54:01 2019
From: report at bugs.python.org (Josh Rosenberg)
Date: Wed, 07 Aug 2019 18:54:01 +0000
Subject: [docs] [issue35786] get_lock() method is not present for Values
 created using multiprocessing.Manager()
In-Reply-To: <1547934632.93.0.223661167179.issue35786@roundup.psfhosted.org>
Message-ID: <1565204041.78.0.746819210248.issue35786@roundup.psfhosted.org>


Josh Rosenberg <shadowranger+python at gmail.com> added the comment:

Reading the docs, I'd definitely expect multiprocessing.Manager().Value to obey the same interface as multiprocessing.Value. The SyncManager docs say:

> Its methods create and return Proxy Objects for a number of commonly used data types to be synchronized across processes.

It does also say (under the linked definition for Proxy Objects):

> A proxy object has methods which invoke corresponding methods of its referent (although not every method of the referent will necessarily be available through the proxy).

which implies the proxy might be more limited, but in fact the proxy is wrapping a completely different underlying class, multiprocessing.managers.Value (that has nothing to do with the class you'd get from calling multiprocessing.Value or multiprocessing.sharedctypes.Value).

It looks like there was, at some point, an attempt to make certain interfaces match; multiprocessing.managers.Value's initializer has a prototype of:

def __init__(self, typecode, value, lock=True):

(documented prototype excludes the lock argument), but AFAICT, lock is completely ignored, and typecode is stored as _typecode on the underlying Value, but otherwise ignored; the multiprocessing.managers.ValueProxy object returned by manager.Value() doesn't expose it (except insofar as you can call ._getvalue() on it to retrieve a copy of the underlying Value), and even if you get the unwrapped object, all _typecode does is change the repr; it's not used anywhere else.

It seems like SyncManager.Value is just the worst of all possible worlds; it has a prototype that (roughly) matches multiprocessing.Value/multiprocessing.sharedctypes.Value, and the limited documentation implies it serves the same function, but:

1. It effectively ignores every argument aside from value (which is the second argument, so you're stuck passing the first argument even though nothing uses it)
2. It doesn't actually use ctypes to achieve efficient storage/IPC communication (updating value involves pickling it, not just sending the raw data of a C array/struct)
3. It doesn't provide any of the interface of the other Value, so you can't use get_lock (or use a with statement to lock it, or manually call acquire or release) or get_obj.

I'm not sure what to do about it though; the manager version of Value is much more flexible, and I'm sure there is existing code that takes advantage of that, so we can't rewrite to make it ctypes backed. The multiprocessing.managers code is too new/complex for me to determine if any easy solution exists to expand multiprocessing.managers.ValueProxy to support context management/get_lock/get_obj to match the behavior of the class returned by multiprocessing.Value/multiprocessing.sharedctypes.Value, but it seems like, if we're going to let the docs imply a relationship, we ought to at least try to make the API of the two classes roughly match.

----------
nosy: +josh.r

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

From report at bugs.python.org  Wed Aug  7 15:22:23 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Wed, 07 Aug 2019 19:22:23 +0000
Subject: [docs] [issue37789] Update doc strings for test.bytecode_helper
In-Reply-To: <1565205727.21.0.329229994167.issue37789@roundup.psfhosted.org>
Message-ID: <1565205743.08.0.0299783355446.issue37789@roundup.psfhosted.org>


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


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
versions: +Python 3.9

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

From report at bugs.python.org  Wed Aug  7 15:22:55 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Wed, 07 Aug 2019 19:22:55 +0000
Subject: [docs] [issue37789] Update doc strings for test.bytecode_helper
In-Reply-To: <1565205727.21.0.329229994167.issue37789@roundup.psfhosted.org>
Message-ID: <1565205775.56.0.0848280748313.issue37789@roundup.psfhosted.org>


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

*supposed not supported.

----------

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

From report at bugs.python.org  Wed Aug  7 15:31:54 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Wed, 07 Aug 2019 19:31:54 +0000
Subject: [docs] [issue18578] Rename and document test.bytecode_helper as
 test.support.bytecode_helper
In-Reply-To: <1375014946.89.0.0130176350727.issue18578@psf.upfronthosting.co.za>
Message-ID: <1565206314.38.0.262282444899.issue18578@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug  8 02:45:17 2019
From: report at bugs.python.org (Philipp Rauch)
Date: Thu, 08 Aug 2019 06:45:17 +0000
Subject: [docs] [issue25810] Python 3 documentation for eval is incorrect
In-Reply-To: <1449346403.16.0.483198527619.issue25810@psf.upfronthosting.co.za>
Message-ID: <1565246717.62.0.91235983304.issue25810@roundup.psfhosted.org>


Change by Philipp Rauch <smokephil at gmail.com>:


----------
versions: +Python 3.7

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

From report at bugs.python.org  Thu Aug  8 02:45:48 2019
From: report at bugs.python.org (Philipp Rauch)
Date: Thu, 08 Aug 2019 06:45:48 +0000
Subject: [docs] [issue25810] Python 3 documentation for eval is incorrect
In-Reply-To: <1449346403.16.0.483198527619.issue25810@psf.upfronthosting.co.za>
Message-ID: <1565246748.76.0.125753852466.issue25810@roundup.psfhosted.org>


Change by Philipp Rauch <smokephil at gmail.com>:


----------
versions: +Python 3.8, Python 3.9

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

From report at bugs.python.org  Thu Aug  8 03:06:55 2019
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 08 Aug 2019 07:06:55 +0000
Subject: [docs] [issue25810] Python 3 documentation for eval is incorrect
In-Reply-To: <1449346403.16.0.483198527619.issue25810@psf.upfronthosting.co.za>
Message-ID: <1565248015.82.0.244511577553.issue25810@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug  8 05:24:26 2019
From: report at bugs.python.org (Inada Naoki)
Date: Thu, 08 Aug 2019 09:24:26 +0000
Subject: [docs] [issue11165] Document PyEval_Call* functions
In-Reply-To: <1297292171.0.0.0899611103523.issue11165@psf.upfronthosting.co.za>
Message-ID: <1565256266.77.0.972969957554.issue11165@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug  8 09:30:55 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 08 Aug 2019 13:30:55 +0000
Subject: [docs] [issue37793] argparse uses "container object",
 should be "iterable"
Message-ID: <1565271055.06.0.436207643911.issue37793@roundup.psfhosted.org>


New submission from Eric V. Smith <eric at trueblade.com>:

https://docs.python.org/3/library/argparse.html#choices says "These can be handled by passing a container object as the choices keyword argument to add_argument()".

I think this should be "iterable" instead. Internally, argparse reads the iterable and converts it to a list so that it can read it multiple times (among other reasons, I'm sure). One of the examples uses range(), which is not a container.

"container" is also used in https://docs.python.org/3/library/argparse.html#the-add-argument-method

Bonus points for fixing the docstring in argparse.py. I didn't check if anywhere else in that file needs to be fixed.

----------
assignee: docs at python
components: Documentation
keywords: newcomer friendly
messages: 349234
nosy: docs at python, eric.smith
priority: normal
severity: normal
status: open
title: argparse uses "container object", should be "iterable"
versions: Python 3.8

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

From report at bugs.python.org  Thu Aug  8 09:59:22 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Blondon?=)
Date: Thu, 08 Aug 2019 13:59:22 +0000
Subject: [docs] [issue37779] configparser: add documentation about several
 read() behaviour
In-Reply-To: <1565122960.66.0.217084239893.issue37779@roundup.psfhosted.org>
Message-ID: <1565272762.33.0.725034792816.issue37779@roundup.psfhosted.org>


Change by St?phane Blondon <stephane.blondon at gmail.com>:


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

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

From report at bugs.python.org  Thu Aug  8 10:06:04 2019
From: report at bugs.python.org (Srinivas Nyayapati)
Date: Thu, 08 Aug 2019 14:06:04 +0000
Subject: [docs] [issue37793] argparse uses "container object",
 should be "iterable"
In-Reply-To: <1565271055.06.0.436207643911.issue37793@roundup.psfhosted.org>
Message-ID: <1565273164.84.0.315873721828.issue37793@roundup.psfhosted.org>


Srinivas Nyayapati <shireenrao at gmail.com> added the comment:

Can I work on this?

----------
nosy: +shireenrao

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

From report at bugs.python.org  Thu Aug  8 10:15:06 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 08 Aug 2019 14:15:06 +0000
Subject: [docs] [issue37793] argparse uses "container object",
 should be "iterable"
In-Reply-To: <1565271055.06.0.436207643911.issue37793@roundup.psfhosted.org>
Message-ID: <1565273706.21.0.849243708879.issue37793@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

shireenrao: yes, please! As they say, PR's accepted!

I'll warn you that I think the only way this could become newcomer-unfriendly is if there are objections that "iterable" is too much jargon for the argparse documentation. But I'll argue that there's a separate tutorial for beginners, and that the documentation should be precise.

----------

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

From report at bugs.python.org  Thu Aug  8 10:38:39 2019
From: report at bugs.python.org (Srinivas Nyayapati)
Date: Thu, 08 Aug 2019 14:38:39 +0000
Subject: [docs] [issue37793] argparse uses "container object",
 should be "iterable"
In-Reply-To: <1565271055.06.0.436207643911.issue37793@roundup.psfhosted.org>
Message-ID: <1565275119.87.0.434114411441.issue37793@roundup.psfhosted.org>


Change by Srinivas Nyayapati <shireenrao at gmail.com>:


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

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

From report at bugs.python.org  Thu Aug  8 10:40:46 2019
From: report at bugs.python.org (Srinivas Nyayapati)
Date: Thu, 08 Aug 2019 14:40:46 +0000
Subject: [docs] [issue37793] argparse uses "container object",
 should be "iterable"
In-Reply-To: <1565271055.06.0.436207643911.issue37793@roundup.psfhosted.org>
Message-ID: <1565275246.44.0.701673909046.issue37793@roundup.psfhosted.org>


Srinivas Nyayapati <shireenrao at gmail.com> added the comment:

Done. Thank you.

----------

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

From report at bugs.python.org  Thu Aug  8 10:50:59 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 08 Aug 2019 14:50:59 +0000
Subject: [docs] [issue37793] argparse uses "container object",
 should be "iterable"
In-Reply-To: <1565271055.06.0.436207643911.issue37793@roundup.psfhosted.org>
Message-ID: <1565275859.55.0.976964370726.issue37793@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

Actually, I might have mislead you on this. I now think that plain iterators won't work. I'm still researching this, I'll get back to you on it. I apologize if it turns out I wasted your time.

----------

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

From report at bugs.python.org  Thu Aug  8 10:56:55 2019
From: report at bugs.python.org (Srinivas Nyayapati)
Date: Thu, 08 Aug 2019 14:56:55 +0000
Subject: [docs] [issue37793] argparse uses "container object",
 should be "iterable"
In-Reply-To: <1565271055.06.0.436207643911.issue37793@roundup.psfhosted.org>
Message-ID: <1565276215.27.0.0245202496551.issue37793@roundup.psfhosted.org>


Srinivas Nyayapati <shireenrao at gmail.com> added the comment:

Not at all. I just started contributing to cpython 2 days ago and finally got the hang of it and was able to push this without any issues on my side. So either way I would still call this a win for me :)

----------

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

From report at bugs.python.org  Thu Aug  8 14:50:16 2019
From: report at bugs.python.org (=?utf-8?q?St=C3=A9phane_Blondon?=)
Date: Thu, 08 Aug 2019 18:50:16 +0000
Subject: [docs] [issue37779] configparser: add documentation about several
 read() behaviour
In-Reply-To: <1565122960.66.0.217084239893.issue37779@roundup.psfhosted.org>
Message-ID: <1565290216.25.0.265404605905.issue37779@roundup.psfhosted.org>


St?phane Blondon <stephane.blondon at gmail.com> added the comment:

Thank you for the idea. :)

I committed something else, based on the previous example of the 'Quick Start' section.

What do you think about it?

----------

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

From report at bugs.python.org  Thu Aug  8 19:58:05 2019
From: report at bugs.python.org (Philip Dye)
Date: Thu, 08 Aug 2019 23:58:05 +0000
Subject: [docs] [issue18697] Unify arguments names in Unicode object C API
 documentation
In-Reply-To: <1376074126.58.0.40251146149.issue18697@psf.upfronthosting.co.za>
Message-ID: <1565308685.91.0.693973762182.issue18697@roundup.psfhosted.org>


Change by Philip Dye <philip.h.dye at phd-solutions.com>:


----------
nosy: +Philip Dye

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

From report at bugs.python.org  Thu Aug  8 22:38:23 2019
From: report at bugs.python.org (Philip Dye)
Date: Fri, 09 Aug 2019 02:38:23 +0000
Subject: [docs] [issue23560] Group the docs of similar methods in
 stdtypes.rst
In-Reply-To: <1425288490.4.0.288876913126.issue23560@psf.upfronthosting.co.za>
Message-ID: <1565318303.53.0.826745845097.issue23560@roundup.psfhosted.org>


Change by Philip Dye <philip.h.dye at phd-solutions.com>:


----------
nosy: +Philip Dye

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

From report at bugs.python.org  Thu Aug  8 23:16:37 2019
From: report at bugs.python.org (Philip Dye)
Date: Fri, 09 Aug 2019 03:16:37 +0000
Subject: [docs] [issue15436] __sizeof__ is not documented
In-Reply-To: <1343073282.53.0.774447573036.issue15436@psf.upfronthosting.co.za>
Message-ID: <1565320597.79.0.450360573464.issue15436@roundup.psfhosted.org>


Change by Philip Dye <philip.h.dye at phd-solutions.com>:


----------
nosy: +Philip Dye

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

From report at bugs.python.org  Fri Aug  9 04:29:56 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Fri, 09 Aug 2019 08:29:56 +0000
Subject: [docs] [issue35181] Doc: Namespace Packages: Inconsistent
 documentation of __loader__ being None
In-Reply-To: <1541543349.68.0.788709270274.issue35181@psf.upfronthosting.co.za>
Message-ID: <1565339396.26.0.987210913624.issue35181@roundup.psfhosted.org>


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


----------
pull_requests: +14922
pull_request: https://github.com/python/cpython/pull/15190

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

From report at bugs.python.org  Fri Aug  9 05:38:48 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Fri, 09 Aug 2019 09:38:48 +0000
Subject: [docs] [issue37799] Renaming Doc/reference/ to Doc/language/
Message-ID: <1565343528.85.0.0920762754632.issue37799@roundup.psfhosted.org>


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

The page https://docs.python.org/3/ lists these two parts:

- Library Reference
- Language Reference

So both parts are "references".

However in the cpython GitHub repository, the Doc/ directory contains these two directories:

- library/
- reference/

So to be consistent, shouldn't we rename the Doc/reference/ directory to Doc/language/?

----------
assignee: docs at python
components: Documentation
messages: 349280
nosy: docs at python, maggyero
priority: normal
severity: normal
status: open
title: Renaming Doc/reference/ to Doc/language/
versions: Python 3.7

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

From report at bugs.python.org  Fri Aug  9 05:39:06 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Fri, 09 Aug 2019 09:39:06 +0000
Subject: [docs] [issue37799] Renaming Doc/reference/ to Doc/language/
In-Reply-To: <1565343528.85.0.0920762754632.issue37799@roundup.psfhosted.org>
Message-ID: <1565343546.32.0.975886962294.issue37799@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Aug  9 06:11:12 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Fri, 09 Aug 2019 10:11:12 +0000
Subject: [docs] [issue37800] Clean up the documentation on module attributes
Message-ID: <1565345472.14.0.507081166865.issue37800@roundup.psfhosted.org>


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


----------
assignee: docs at python
components: Documentation
nosy: docs at python, eric.snow, maggyero
priority: normal
pull_requests: 14923
severity: normal
status: open
title: Clean up the documentation on module attributes
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Fri Aug  9 21:40:11 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Sat, 10 Aug 2019 01:40:11 +0000
Subject: [docs] [issue37799] Renaming Doc/reference/ to Doc/language/
In-Reply-To: <1565343528.85.0.0920762754632.issue37799@roundup.psfhosted.org>
Message-ID: <1565401211.64.0.896787966657.issue37799@roundup.psfhosted.org>


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

Hello maggyero,

I thinks that could be a good improve. But this structure is
used on since old cpython versions, so I don't know if it will be a necessary change.

But, if you don't receive some feedback from here, you can propose
a PR, maybe other core dev could review it and tell you their opinion
:-)

----------
nosy: +eamanu

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

From report at bugs.python.org  Sat Aug 10 00:47:14 2019
From: report at bugs.python.org (Mariatta)
Date: Sat, 10 Aug 2019 04:47:14 +0000
Subject: [docs] [issue37799] Renaming Doc/reference/ to Doc/language/
In-Reply-To: <1565343528.85.0.0920762754632.issue37799@roundup.psfhosted.org>
Message-ID: <1565412434.08.0.433693401346.issue37799@roundup.psfhosted.org>


Mariatta <mariatta at python.org> added the comment:

The change is not worth doing for several reasons:

- renaming filename/directory breaks git history on GitHub web UI. The history can still be viewed if you use the command line e.g. git log --follow. 
 
- other pages like stack overflow or blog posts have linked to the /reference for ages. We'll be breaking links. We might be able to set up redirect to the new path, but the effort is not worth the gain IMO.

There is very little to be gained compared to all the pitfalls.

So I'm closing this issue.

Thanks.

----------
nosy: +Mariatta
priority: normal -> low
resolution:  -> rejected
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Aug 10 12:41:45 2019
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Sat, 10 Aug 2019 16:41:45 +0000
Subject: [docs] [issue37809] Alias typing.NamedTuple to collections
In-Reply-To: <1565426100.13.0.700794454326.issue37809@roundup.psfhosted.org>
Message-ID: <1565455305.2.0.694552683044.issue37809@roundup.psfhosted.org>


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

> FWIW, I had updated the docs for namedtuple() to link to typing.NamedTuple.  I think that should suffice.

Thank you!  I looked at the docs everything looks good.  I think this can be closed now.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Aug 10 12:50:42 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 10 Aug 2019 16:50:42 +0000
Subject: [docs] [issue37809] Alias typing.NamedTuple to collections
In-Reply-To: <1565426100.13.0.700794454326.issue37809@roundup.psfhosted.org>
Message-ID: <1565455842.44.0.387482447558.issue37809@roundup.psfhosted.org>


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

Further notes for posterity:

* Anything written using collections.NamedTuple would instantly lose its backwards compatibility.  

* The casing of NamedTuple is more in line with the typing module:  List, Deque, NamedTuple and doesn't fit well with the deque, namedtuple, and ChainMap in the collections module. 

* Nothing in the collections module currently requires typing, but NamedTuple can only be used with typing.  

* We really don't want to increase import times for collections. This proposal would defeat the entire purpose of having moved _collections_abc to a separate module outside of the collections package.

----------

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

From report at bugs.python.org  Sat Aug 10 17:46:12 2019
From: report at bugs.python.org (=?utf-8?b?R8Opcnk=?=)
Date: Sat, 10 Aug 2019 21:46:12 +0000
Subject: [docs] [issue37813] PEP 7 line-breaking with binary operations
 contradicts Knuth's rule
Message-ID: <1565473572.7.0.81062665759.issue37813@roundup.psfhosted.org>


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

I have just read PEP 7 and noticed that its line-breaking recommandation in presence of binary operations seems to contradict its analogue in PEP 8 which follows Knuth's rule.

PEP 7 (https://www.python.org/dev/peps/pep-0007/#code-lay-out):

> When you break a long expression at a binary operator, the operator
> goes at the end of the previous line, and braces should be formatted
> as shown. E.g.:
> 
> if (type->tp_dictoffset != 0 && base->tp_dictoffset == 0 &&
>     type->tp_dictoffset == b_size &&
>     (size_t)t_size == b_size + sizeof(PyObject *))
> {
>     return 0; /* "Forgive" adding a __dict__ only */
> }

PEP 8 (https://www.python.org/dev/peps/pep-0008/#should-a-line-break-before-or-after-a-binary-operator):

> To solve this readability problem, mathematicians and their
> publishers follow the opposite convention. Donald Knuth explains the
> traditional rule in his Computers and Typesetting series: "Although
> formulas within a paragraph always break after binary operations and
> relations, displayed formulas always break before binary operations"
> [3].
> 
> Following the tradition from mathematics usually results in more
> readable code:
> 
> # Yes: easy to match operators with operands
> income = (gross_wages
>           + taxable_interest
>           + (dividends - qualified_dividends)
>           - ira_deduction
>           - student_loan_interest)
> In Python code, it is permissible to break before or after a binary
> operator, as long as the convention is consistent locally. For new
> code Knuth's style is suggested.

----------
assignee: docs at python
components: Documentation
messages: 349361
nosy: docs at python, maggyero
priority: normal
severity: normal
status: open
title: PEP 7 line-breaking with binary operations contradicts Knuth's rule
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Sat Aug 10 20:36:34 2019
From: report at bugs.python.org (Josh Holland)
Date: Sun, 11 Aug 2019 00:36:34 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
Message-ID: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>


New submission from Josh Holland <anowlcalledjosh at gmail.com>:

The empty tuple syntax in type annotations, `Tuple[()]`, is not obvious from the examples given in the documentation (I naively expected `Tuple[]` to work); it has been documented in PEP 484[1] and in mypy[2], but not in the documentation for the typing module.

[1]: https://www.python.org/dev/peps/pep-0484/#the-typing-module
[2]: https://github.com/python/mypy/pull/4313

----------
assignee: docs at python
components: Documentation
messages: 349366
nosy: anowlcalledjosh, docs at python
priority: normal
severity: normal
status: open
title: typing module: empty tuple syntax is undocumented
type: enhancement

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

From report at bugs.python.org  Sat Aug 10 21:06:41 2019
From: report at bugs.python.org (Glenn Linderman)
Date: Sun, 11 Aug 2019 01:06:41 +0000
Subject: [docs] [issue37816] f-string documentation not fully accurate
Message-ID: <1565485601.85.0.782571390413.issue37816@roundup.psfhosted.org>


New submission from Glenn Linderman <v+python at g.nevcal.com>:

I noticed the following description for f-strings:

> Escape sequences are decoded like in ordinary string literals (except when a literal is also marked as a raw string). After decoding, the grammar for the contents of the string is:

followed by lots of stuff, followed by

> Backslashes are not allowed in format expressions and will raise an error:
> f"newline: {ord('\n')}"  # raises SyntaxError

If f-strings are processed AS DESCRIBED, the \n would never seen by the format expression... but in fact, it does produce an error.

PEP 498 has a more accurate description, that the {} parsing actually happens before the escape processing. The string or raw-string escape processing is done only to the literal string pieces.

So the string content is first parsed for format expressions enclosed in {}, on the way, converting {{ and }} to { and } in the literal parts of the string, and then the literal parts are treated exactly like independent string literals (with regular or raw-string escaping performed), to be concatenated with the evaluation of the format expressions, and subsequent literal parts.

The evaluation of the format expressions presently precludes the use of # and \ for comments and escapes, but otherwise tries to sort of by the same as a python expression possibly followed by a format mini-language part.  I am not the expert here, just the messenger.

----------
assignee: docs at python
components: Documentation
messages: 349370
nosy: docs at python, v+python
priority: normal
severity: normal
status: open
title: f-string documentation not fully accurate
versions: Python 3.6, Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Sat Aug 10 22:54:30 2019
From: report at bugs.python.org (John Rogers)
Date: Sun, 11 Aug 2019 02:54:30 +0000
Subject: [docs] [issue37818] Behaviors of binary bitwise operators
 contradicting documentation
Message-ID: <1565492070.46.0.473056579761.issue37818@roundup.psfhosted.org>


New submission from John Rogers <luinnissar at yahoo.com>:

In Python Language Reference (version 3.7), section 6.9 it states that the arguments of binary bitwise operators must be integers. However, the following expressions work without error:

    True & False
    False | True
    True ^ True

Each produces a boolean result (not integer) (False, True, False, respectively). Also I find that mixing booleans and integers does work too, though this time it produces integers.

One can easily test it on Python home page's console window. I also tested it on my Linux box running version 3.5.3. So it appears that it has been overlooked for quite some time!

As an aside: I do assume that boolean values are *distinct* from integers. If they are not, then my apologies!

----------
assignee: docs at python
components: Documentation
messages: 349372
nosy: The Blue Wizard, docs at python
priority: normal
severity: normal
status: open
title: Behaviors of binary bitwise operators contradicting documentation
type: behavior
versions: Python 3.5, Python 3.7

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

From report at bugs.python.org  Sat Aug 10 23:17:56 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 11 Aug 2019 03:17:56 +0000
Subject: [docs] [issue37816] f-string documentation not fully accurate
In-Reply-To: <1565485601.85.0.782571390413.issue37816@roundup.psfhosted.org>
Message-ID: <1565493476.23.0.00214677475103.issue37816@roundup.psfhosted.org>


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


----------
nosy: +eric.smith

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

From report at bugs.python.org  Sat Aug 10 23:19:23 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 11 Aug 2019 03:19:23 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565493563.35.0.998779461784.issue37814@roundup.psfhosted.org>


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


----------
nosy: +gvanrossum, levkivskyi

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

From report at bugs.python.org  Sat Aug 10 23:43:43 2019
From: report at bugs.python.org (Steven D'Aprano)
Date: Sun, 11 Aug 2019 03:43:43 +0000
Subject: [docs] [issue37818] Behaviors of binary bitwise operators
 contradicting documentation
In-Reply-To: <1565492070.46.0.473056579761.issue37818@roundup.psfhosted.org>
Message-ID: <1565495023.83.0.477156209211.issue37818@roundup.psfhosted.org>


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

bools are integers, specifically they are a subclass of int:

py> isinstance(True, int)
True
py> issubclass(bool, int)
True

so the behaviour is correct.

----------
nosy: +steven.daprano
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Aug 10 23:54:04 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Sun, 11 Aug 2019 03:54:04 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565495644.12.0.860916884703.issue37814@roundup.psfhosted.org>


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

That?s correct. Mind making a PR?

----------

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

From report at bugs.python.org  Sun Aug 11 02:01:19 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 11 Aug 2019 06:01:19 +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: <1565503279.7.0.170649380919.issue15248@roundup.psfhosted.org>


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

This isn't interacting well with IDLE.

====================================================
--- Works fine at the regular interactive prompt ---

$ python3.8
Python 3.8.0b3 (v3.8.0b3:4336222407, Jul 29 2019, 09:46:03)
[Clang 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> data = [
...          (1, 2, 3) # oops, missing comma!
...          (4, 5, 6)
...      ]
<stdin>:2: SyntaxWarning: 'tuple' object is not callable; perhaps you missed a comma?
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>


====================================================
--- Behaves differently in the IDLE Shell        ---

Python 3.8.0b3 (v3.8.0b3:4336222407, Jul 29 2019, 09:46:03) 
[Clang 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license()" for more information.
>>> data = [
         (1, 2, 3) # oops, missing comma!
         (4, 5, 6)
     ]
SyntaxError: 'tuple' object is not callable; perhaps you missed a comma?

----------
assignee: docs at python -> terry.reedy
components: +IDLE -Documentation
nosy: +rhettinger
status: closed -> open

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

From report at bugs.python.org  Sun Aug 11 04:17:31 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 11 Aug 2019 08:17:31 +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: <1565511451.43.0.814880821328.issue15248@roundup.psfhosted.org>


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

I think it would be better to open a separate issue for IDLE.

----------

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

From Michael.Faust at nemetris.com  Thu Aug  8 04:40:53 2019
From: Michael.Faust at nemetris.com (Michael Faust)
Date: Thu, 8 Aug 2019 08:40:53 +0000
Subject: [docs] Documentation Bug - Telnet
Message-ID: <e721d485d9ca4f0f9b3f182d8a7e3fcb@nem-exc-01.nemetris.local>

Hello,

I think I found a bug in the Telnet docs: https://docs.python.org/3/library/telnetlib.html

In the section https://docs.python.org/3/library/telnetlib.html#telnetlib.Telnet the "open()" link should probably point to https://docs.python.org/3/library/telnetlib.html#telnetlib.Telnet.open but instead it points to https://docs.python.org/3/library/functions.html#open

Best regards, Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190808/e966425d/attachment-0001.html>

From report at bugs.python.org  Sun Aug 11 08:22:10 2019
From: report at bugs.python.org (Josh Holland)
Date: Sun, 11 Aug 2019 12:22:10 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565526130.58.0.511012167548.issue37814@roundup.psfhosted.org>


Change by Josh Holland <anowlcalledjosh at gmail.com>:


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

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

From report at bugs.python.org  Sun Aug 11 09:00:24 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 11 Aug 2019 13:00:24 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565528424.71.0.691936481599.issue37814@roundup.psfhosted.org>


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

What is better, Tuple[()] or Literal[()]?

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

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

From report at bugs.python.org  Sun Aug 11 09:50:39 2019
From: report at bugs.python.org (Josh Holland)
Date: Sun, 11 Aug 2019 13:50:39 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565531439.3.0.316699724494.issue37814@roundup.psfhosted.org>


Josh Holland <anowlcalledjosh at gmail.com> added the comment:

PEP 586 doesn't currently allow Literal to contain tuples, so Tuple[()] is the only option.

----------

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

From report at bugs.python.org  Sun Aug 11 11:22:29 2019
From: report at bugs.python.org (Tal Einat)
Date: Sun, 11 Aug 2019 15:22:29 +0000
Subject: [docs] [issue23220] IDLE: Document how Shell displays user code
 output
In-Reply-To: <1420937687.17.0.885670059147.issue23220@psf.upfronthosting.co.za>
Message-ID: <1565536949.33.0.0707613006322.issue23220@roundup.psfhosted.org>


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


----------
pull_requests: +14939
pull_request: https://github.com/python/cpython/pull/15211

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

From report at bugs.python.org  Sun Aug 11 11:23:12 2019
From: report at bugs.python.org (Tal Einat)
Date: Sun, 11 Aug 2019 15:23:12 +0000
Subject: [docs] [issue23220] IDLE: Document how Shell displays user code
 output
In-Reply-To: <1420937687.17.0.885670059147.issue23220@psf.upfronthosting.co.za>
Message-ID: <1565536992.91.0.845400861404.issue23220@roundup.psfhosted.org>


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

See initial working implementation of handling \r and \b characters is the shell, PR GH-15211.

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

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

From report at bugs.python.org  Sun Aug 11 12:13:29 2019
From: report at bugs.python.org (Mariatta)
Date: Sun, 11 Aug 2019 16:13:29 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
Message-ID: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>


New submission from Mariatta <mariatta at python.org>:

Bug in the Telnet docs: https://docs.python.org/3/library/telnetlib.html

In the section https://docs.python.org/3/library/telnetlib.html#telnetlib.Telnet the ?open()? link should probably point to https://docs.python.org/3/library/telnetlib.html#telnetlib.Telnet.open but instead it points to https://docs.python.org/3/library/functions.html#open

This is newcomer friendly and I would prefer it be done by first time contributors.

Reported in docs mailing list: https://mail.python.org/pipermail/docs/2019-August/041817.html

----------
assignee: docs at python
components: Documentation
keywords: easy, newcomer friendly
messages: 349393
nosy: Mariatta, docs at python
priority: normal
severity: normal
stage: needs patch
status: open
title: Telnet documentation: fix the link to open()
versions: Python 2.7, Python 3.7, Python 3.8, Python 3.9

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

From mariatta.wijaya at gmail.com  Sun Aug 11 12:14:12 2019
From: mariatta.wijaya at gmail.com (Mariatta)
Date: Sun, 11 Aug 2019 09:14:12 -0700
Subject: [docs] Documentation Bug - Telnet
In-Reply-To: <e721d485d9ca4f0f9b3f182d8a7e3fcb@nem-exc-01.nemetris.local>
References: <e721d485d9ca4f0f9b3f182d8a7e3fcb@nem-exc-01.nemetris.local>
Message-ID: <CAGbohnYr5ODzMSjk4BAfn9J3HLi5SoQ3ShTJ+dWLkaBLkDxBTA@mail.gmail.com>

Thanks. I've filed the bug in our issue tracker.

https://bugs.python.org/issue37823?@ok_message=msg%20349393%20created%0Aissue%2037823%20created&@template=item

On Sun, Aug 11, 2019, 3:12 AM Michael Faust <Michael.Faust at nemetris.com>
wrote:

> Hello,
>
>
>
> I think I found a bug in the Telnet docs:
> https://docs.python.org/3/library/telnetlib.html
>
>
>
> In the section
> https://docs.python.org/3/library/telnetlib.html#telnetlib.Telnet the
> ?open()? link should probably point to
> https://docs.python.org/3/library/telnetlib.html#telnetlib.Telnet.open
> but instead it points to
> https://docs.python.org/3/library/functions.html#open
>
>
>
> Best regards, Michael
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190811/b6c0a0e7/attachment.html>

From report at bugs.python.org  Sun Aug 11 12:26:06 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 11 Aug 2019 16:26:06 +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: <1565540766.74.0.620665950379.issue15248@roundup.psfhosted.org>


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

This is not related to this particular warning, but to how IDLE handles SyntaxWarning. See issue34857.

----------
assignee: terry.reedy -> 
components: +Interpreter Core -IDLE
status: open -> closed

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

From report at bugs.python.org  Sun Aug 11 13:53:40 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Sun, 11 Aug 2019 17:53:40 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565546020.28.0.300399745398.issue37814@roundup.psfhosted.org>


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

> What is better, Tuple[()] or Literal[()]?

In this context, Tuple[()] is better, as the discussion is about how to write the type of various tuples. Tuple[()] is just the edge case of the type of the empty tuple.

Josh, please sign the CLA and adjust the wording per my request in the PR.

----------

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

From report at bugs.python.org  Sun Aug 11 14:36:06 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Sun, 11 Aug 2019 18:36:06 +0000
Subject: [docs] [issue37826] Document PEP 3134 in tutorials/errors.rst
Message-ID: <1565548566.46.0.213467869715.issue37826@roundup.psfhosted.org>


New submission from Abhilash Raj <raj.abhilash1 at gmail.com>:

Looking at the docs, I couldn't find the `raise from` documentation anywhere in the Errors and Exceptions page (https://docs.python.org/3/tutorial/errors.html) page, which seems to be the landing page for Python Exceptions. 

I do see however that it is documented on the top page of https://docs.python.org/3/library/exceptions.html and raise statement's docs (https://docs.python.org/3/reference/simple_stmts.html#raise), both of which are pretty hard to discover. 

It would be nice to add the docs for `raise from` in the Errors and Exception page too.

----------
assignee: docs at python
components: Documentation
messages: 349406
nosy: docs at python, maxking
priority: normal
severity: normal
status: open
title: Document PEP 3134 in tutorials/errors.rst

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

From report at bugs.python.org  Sun Aug 11 21:16:16 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 12 Aug 2019 01:16:16 +0000
Subject: [docs] [issue37826] Document PEP 3134 in tutorials/errors.rst
In-Reply-To: <1565548566.46.0.213467869715.issue37826@roundup.psfhosted.org>
Message-ID: <1565572576.75.0.877763566313.issue37826@roundup.psfhosted.org>


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

This is a reasonable suggestion.

Would you like to submit a pull request?

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

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

From report at bugs.python.org  Sun Aug 11 23:38:14 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 12 Aug 2019 03:38:14 +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: <1565581094.67.0.0756946367496.issue15248@roundup.psfhosted.org>


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

IDLE's Shell has treated SyntaxWarnings as errors since 2001.  I don't know if any other IDE's do the same.  Raymond's example did not concern me, as I think not calling known non-callables is preferable.

But not executing literal-with-is code, such as "a = 1; a is 1" and "0 is ''" is wrong.  See msg349431 of #34857 for more discussion of these cases.

----------

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

From report at bugs.python.org  Mon Aug 12 01:28:15 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 12 Aug 2019 05:28:15 +0000
Subject: [docs] [issue23220] IDLE: Document how Shell displays user code
 output
In-Reply-To: <1420937687.17.0.885670059147.issue23220@psf.upfronthosting.co.za>
Message-ID: <1565587695.39.0.894162572977.issue23220@roundup.psfhosted.org>


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

The conclusion of this discussion was that we should insert control chars, in particular \b and \r, as are into tk.Text and document the (variable) result.  Please describe your proposed new behavior, how it differs from the current behavior, and why you think it better.  I think that this should be a new issue.

----------

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

From report at bugs.python.org  Mon Aug 12 02:59:33 2019
From: report at bugs.python.org (Tal Einat)
Date: Mon, 12 Aug 2019 06:59:33 +0000
Subject: [docs] [issue23220] IDLE: Document how Shell displays user code
 output
In-Reply-To: <1420937687.17.0.885670059147.issue23220@psf.upfronthosting.co.za>
Message-ID: <1565593173.05.0.37700606301.issue23220@roundup.psfhosted.org>


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

Ah, sorry for missing that, Terry. See new issue, #37827, for the proposed change.

----------

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

From report at bugs.python.org  Mon Aug 12 03:00:43 2019
From: report at bugs.python.org (Tal Einat)
Date: Mon, 12 Aug 2019 07:00:43 +0000
Subject: [docs] [issue23220] IDLE: Document how Shell displays user code
 output
In-Reply-To: <1420937687.17.0.885670059147.issue23220@psf.upfronthosting.co.za>
Message-ID: <1565593243.67.0.876095103387.issue23220@roundup.psfhosted.org>


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


----------
pull_requests:  -14939

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

From report at bugs.python.org  Mon Aug 12 04:25:59 2019
From: report at bugs.python.org (pasenor)
Date: Mon, 12 Aug 2019 08:25:59 +0000
Subject: [docs] [issue37829] Documentation of stdlib: add example of mixed
 arguments to dict()
Message-ID: <1565598359.42.0.652909866188.issue37829@roundup.psfhosted.org>


New submission from pasenor <gosha at fro.lv>:

The following use of the dict() function with both positional and keyword arguments  does follow from the description, but probably needs it's own example:

dict({'a': 1}, b=2}) == {'a': 1, 'b': 2}

----------
assignee: docs at python
components: Documentation
messages: 349446
nosy: docs at python, pasenor
priority: normal
severity: normal
status: open
title: Documentation of stdlib: add example of mixed arguments to dict()
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Mon Aug 12 04:40:28 2019
From: report at bugs.python.org (pasenor)
Date: Mon, 12 Aug 2019 08:40:28 +0000
Subject: [docs] [issue37829] Documentation of stdlib: add example of mixed
 arguments to dict()
In-Reply-To: <1565598359.42.0.652909866188.issue37829@roundup.psfhosted.org>
Message-ID: <1565599228.3.0.221666212854.issue37829@roundup.psfhosted.org>


Change by pasenor <gosha at fro.lv>:


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

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

From report at bugs.python.org  Mon Aug 12 06:28:03 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Mon, 12 Aug 2019 10:28:03 +0000
Subject: [docs] [issue37829] Documentation of stdlib: add example of mixed
 arguments to dict()
In-Reply-To: <1565598359.42.0.652909866188.issue37829@roundup.psfhosted.org>
Message-ID: <1565605683.25.0.685014842536.issue37829@roundup.psfhosted.org>


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


----------
nosy: +inada.naoki, rhettinger
versions:  -Python 3.5, Python 3.6

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

From report at bugs.python.org  Mon Aug 12 07:34:15 2019
From: report at bugs.python.org (Matthew Bruggeman)
Date: Mon, 12 Aug 2019 11:34:15 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1565609655.82.0.276714935548.issue37823@roundup.psfhosted.org>


Matthew Bruggeman <brugz at google.com> added the comment:

I can take a look

----------
nosy: +Matthew Bruggeman

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

From finswimmer77 at gmail.com  Mon Aug 12 05:09:41 2019
From: finswimmer77 at gmail.com (fin swimmer)
Date: Mon, 12 Aug 2019 11:09:41 +0200
Subject: [docs] File included in bdist
Message-ID: <CALFY5SBKEBxvAv__5LCDp7cAMzWifOwwYQ8SPzw3mE26g0c5jg@mail.gmail.com>

Hello,

for sdist there is a documentation which files are included by default into
the distribution:
https://docs.python.org/3/distutils/sourcedist.html#specifying-the-files-to-distribute

I cannot found this for bdist. So which files are included by default?

Thanks a lot for an answer.

Fin Swimmer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190812/c2e36352/attachment.html>

From report at bugs.python.org  Mon Aug 12 20:55:47 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Tue, 13 Aug 2019 00:55:47 +0000
Subject: [docs] [issue37826] Document PEP 3134 in tutorials/errors.rst
In-Reply-To: <1565548566.46.0.213467869715.issue37826@roundup.psfhosted.org>
Message-ID: <1565657747.14.0.0238790244655.issue37826@roundup.psfhosted.org>


Abhilash Raj <raj.abhilash1 at gmail.com> added the comment:

Yes, I am gonna work on a PR.

----------

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

From report at bugs.python.org  Mon Aug 12 21:27:28 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Tue, 13 Aug 2019 01:27:28 +0000
Subject: [docs] [issue37826] Document PEP 3134 in tutorials/errors.rst
In-Reply-To: <1565548566.46.0.213467869715.issue37826@roundup.psfhosted.org>
Message-ID: <1565659648.23.0.436732433167.issue37826@roundup.psfhosted.org>


Change by Abhilash Raj <raj.abhilash1 at gmail.com>:


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

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

From report at bugs.python.org  Tue Aug 13 06:23:34 2019
From: report at bugs.python.org (Sanyam Khurana)
Date: Tue, 13 Aug 2019 10:23:34 +0000
Subject: [docs] [issue37256] urllib.request.Request documentation
 erroneously refers to the "final two"
In-Reply-To: <1560366755.97.0.221740241329.issue37256@roundup.psfhosted.org>
Message-ID: <1565691814.2.0.383138943616.issue37256@roundup.psfhosted.org>


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

Thanks for the bug report Alan & for the PR Ngalim!

I've checked the current docs and this is a valid bug.

I've also reviewed the Pull request and it looks good to me.

@Mariatta, @Senthil can you please have a look at this?

Many thanks!

----------
nosy: +CuriousLearner, Mariatta, orsenthil
versions:  -Python 3.5, Python 3.6

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

From report at bugs.python.org  Tue Aug 13 09:24:04 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Tue, 13 Aug 2019 13:24:04 +0000
Subject: [docs] [issue25299] TypeError: __init__() takes at least 4
 arguments (4 given)
In-Reply-To: <1443785146.27.0.85852377889.issue25299@psf.upfronthosting.co.za>
Message-ID: <1565702644.09.0.550522313923.issue25299@roundup.psfhosted.org>


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

paul.j3, 

The fix looks promising. Do you want to open a PR with this fix?

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

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

From report at bugs.python.org  Tue Aug 13 10:26:25 2019
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 13 Aug 2019 14:26:25 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
 (or operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1565706385.68.0.496114678154.issue17576@roundup.psfhosted.org>


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

It started to write a new issue, but then I found this issue issue (created in 2013!) which is still open. So let me write my comment here instead.

The code to convert a number to an integer is quite complex in Python. There are *many* ways to do that and each way has subtle behavior differences (ex: __index__ vs __int__). Python tolerates some behavior which lead to even more confusion. For example, some functions explicitly reject the float type but accept Decimal:

* bpo-20861
* bpo-35707

PyLong_Long(obj) calls type(obj).__index__() if it's defined, but it accepts subtypes of int, not only exactly the int type (type(x) == int). This feature is deprecated since Python 3.3 (released in 2012), since this change:

commit 31a655411a79b00517cdcd0a2752824d183db792
Author: Serhiy Storchaka <storchaka at gmail.com>
Date:   Wed Dec 11 21:07:54 2013 +0200

    Issue #17576: Deprecation warning emitted now when __int__() or __index__()
    return not int instance.  Introduced _PyLong_FromNbInt() and refactored
    PyLong_As*() functions.

I propose to now fail with an exception if __int__() or __index__() return type is not exactly int.

Note: My notes on Python numbers: https://pythondev.readthedocs.io/numbers.html

----------

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

From report at bugs.python.org  Tue Aug 13 11:37:46 2019
From: report at bugs.python.org (Anthony Sottile)
Date: Tue, 13 Aug 2019 15:37:46 +0000
Subject: [docs] [issue8243] curses writing to window's bottom right position
 raises: `_curses.error: addstr() returned ERR'
In-Reply-To: <1352121880.55.0.191535515397.issue8243@psf.upfronthosting.co.za>
Message-ID: <1565710666.2.0.00764905591949.issue8243@roundup.psfhosted.org>


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

In case it helps someone else, `insstr` seems to not have this limitation

----------
nosy: +Anthony Sottile

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

From report at bugs.python.org  Tue Aug 13 12:42:57 2019
From: report at bugs.python.org (paul j3)
Date: Tue, 13 Aug 2019 16:42:57 +0000
Subject: [docs] [issue25299] TypeError: __init__() takes at least 4
 arguments (4 given)
In-Reply-To: <1443785146.27.0.85852377889.issue25299@psf.upfronthosting.co.za>
Message-ID: <1565714577.83.0.575563129688.issue25299@roundup.psfhosted.org>


paul j3 <ajipanca at gmail.com> added the comment:

I'm not set up to work with the current development distribution (via github).  All my proposed patches are diffs for earlier repos.

Paul

----------

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

From report at bugs.python.org  Tue Aug 13 13:11:35 2019
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 13 Aug 2019 17:11:35 +0000
Subject: [docs] [issue37813] PEP 7 line-breaking with binary operations
 contradicts Knuth's rule
In-Reply-To: <1565473572.7.0.81062665759.issue37813@roundup.psfhosted.org>
Message-ID: <1565716295.1.0.368749587002.issue37813@roundup.psfhosted.org>


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


----------
nosy: +barry

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

From report at bugs.python.org  Tue Aug 13 13:17:46 2019
From: report at bugs.python.org (Barry A. Warsaw)
Date: Tue, 13 Aug 2019 17:17:46 +0000
Subject: [docs] [issue37813] PEP 7 line-breaking with binary operations
 contradicts Knuth's rule
In-Reply-To: <1565473572.7.0.81062665759.issue37813@roundup.psfhosted.org>
Message-ID: <1565716666.71.0.810240687509.issue37813@roundup.psfhosted.org>


Barry A. Warsaw <barry at python.org> added the comment:

I personally don't think we need to change this.  C and Python are different, and the PEP 7 rules have been in place for ages.

+Guido

----------
nosy: +gvanrossum

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

From report at bugs.python.org  Tue Aug 13 13:27:48 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 13 Aug 2019 17:27:48 +0000
Subject: [docs] [issue37813] PEP 7 line-breaking with binary operations
 contradicts Knuth's rule
In-Reply-To: <1565473572.7.0.81062665759.issue37813@roundup.psfhosted.org>
Message-ID: <1565717268.37.0.572976099773.issue37813@roundup.psfhosted.org>


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

PEP 8 contains contradictory examples.

https://www.python.org/dev/peps/pep-0008/#indentation

>     # No extra indentation.
>     if (this_is_one_thing and
>         that_is_another_thing):
>         do_something()
> 
>     # Add a comment, which will provide some distinction in editors
>     # supporting syntax highlighting.
>     if (this_is_one_thing and
>         that_is_another_thing):
>         # Since both conditions are true, we can frobnicate.
>         do_something()
> 
>     # Add some extra indentation on the conditional continuation line.
>     if (this_is_one_thing
>             and that_is_another_thing):
>         do_something()
> 
> (Also see the discussion of whether to break before or after binary
> operators below.)

(It was already reported in other issue.)

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

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

From report at bugs.python.org  Tue Aug 13 13:28:10 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 13 Aug 2019 17:28:10 +0000
Subject: [docs] [issue37813] PEP 7 line-breaking with binary operations
 contradicts Knuth's rule
In-Reply-To: <1565473572.7.0.81062665759.issue37813@roundup.psfhosted.org>
Message-ID: <1565717290.7.0.640798444599.issue37813@roundup.psfhosted.org>


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


----------
versions:  -Python 3.7

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

From report at bugs.python.org  Tue Aug 13 14:06:10 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 13 Aug 2019 18:06:10 +0000
Subject: [docs] [issue37813] PEP 7 line-breaking with binary operations
 contradicts Knuth's rule
In-Reply-To: <1565473572.7.0.81062665759.issue37813@roundup.psfhosted.org>
Message-ID: <1565719569.97.0.067600524826.issue37813@roundup.psfhosted.org>


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

PEP 8 intentionally allows users to choose whether to put the operator at the start or end of the line (as long as they're consistent within a file or project). This is to avoid a barrage of "style fixes" that are just noise.

But PEP 7 is only for CPython's own C code style, and here I don't want things to change. When it comes to readability of our code surely there are bigger fish to fry.

So I'm closing this as won't fix.

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

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

From report at bugs.python.org  Tue Aug 13 15:05:17 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 13 Aug 2019 19:05:17 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565723116.98.0.382708896347.issue37814@roundup.psfhosted.org>


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


New changeset 8a784af750fa82c8355903309e5089eb2b60c16b by Miss Islington (bot) (Josh Holland) in branch 'master':
bpo-37814: Document the empty tuple type annotation syntax (GH-15208)
https://github.com/python/cpython/commit/8a784af750fa82c8355903309e5089eb2b60c16b


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

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

From report at bugs.python.org  Tue Aug 13 15:05:56 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 13 Aug 2019 19:05:56 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565723156.31.0.689020557359.issue37814@roundup.psfhosted.org>


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


----------
pull_requests: +14980
pull_request: https://github.com/python/cpython/pull/15261

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

From report at bugs.python.org  Tue Aug 13 15:12:58 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 13 Aug 2019 19:12:58 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565723578.86.0.193735023792.issue37814@roundup.psfhosted.org>


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


New changeset 6ad902a08814909b4d52c4000d5a10ce58516dac by Miss Islington (bot) in branch '3.8':
bpo-37814: Document the empty tuple type annotation syntax (GH-15208)
https://github.com/python/cpython/commit/6ad902a08814909b4d52c4000d5a10ce58516dac


----------

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

From report at bugs.python.org  Tue Aug 13 15:16:02 2019
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 13 Aug 2019 19:16:02 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565723762.36.0.585173253483.issue37814@roundup.psfhosted.org>


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

Thanks Josh! The automated backport to 3.7 didn't work, that's okay, so I'll close this now. (Though if you want to experiment with the cherry-picker tool go ahead.)

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

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

From report at bugs.python.org  Tue Aug 13 15:20:24 2019
From: report at bugs.python.org (Josh Holland)
Date: Tue, 13 Aug 2019 19:20:24 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565724024.18.0.948597278672.issue37814@roundup.psfhosted.org>


Change by Josh Holland <anowlcalledjosh at gmail.com>:


----------
pull_requests: +14981
pull_request: https://github.com/python/cpython/pull/15262

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

From report at bugs.python.org  Tue Aug 13 15:26:19 2019
From: report at bugs.python.org (miss-islington)
Date: Tue, 13 Aug 2019 19:26:19 +0000
Subject: [docs] [issue37814] typing module: empty tuple syntax is
 undocumented
In-Reply-To: <1565483794.67.0.80364614628.issue37814@roundup.psfhosted.org>
Message-ID: <1565724379.84.0.977340057158.issue37814@roundup.psfhosted.org>


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


New changeset 37fd9f73e2fa439554977cfba427bf94c1fedb6b by Miss Islington (bot) (Josh Holland) in branch '3.7':
[3.7] bpo-37814: Document the empty tuple type annotation syntax (GH-15208) (GH-15262)
https://github.com/python/cpython/commit/37fd9f73e2fa439554977cfba427bf94c1fedb6b


----------

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

From report at bugs.python.org  Tue Aug 13 21:11:04 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Wed, 14 Aug 2019 01:11:04 +0000
Subject: [docs] [issue37256] urllib.request.Request documentation
 erroneously refers to the "final two"
In-Reply-To: <1560366755.97.0.221740241329.issue37256@roundup.psfhosted.org>
Message-ID: <1565745064.14.0.518396424322.issue37256@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:


New changeset 38c7199beb30ae9a5005c0f0d9df9fae0da3680a by Senthil Kumaran (Ngalim Siregar) in branch 'master':
bpo-37256: Wording in Request class docs (#14792)
https://github.com/python/cpython/commit/38c7199beb30ae9a5005c0f0d9df9fae0da3680a


----------

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

From report at bugs.python.org  Tue Aug 13 22:44:09 2019
From: report at bugs.python.org (Windson Yang)
Date: Wed, 14 Aug 2019 02:44:09 +0000
Subject: [docs] [issue37846] declare that Text I/O use buffer inside
Message-ID: <1565750649.11.0.831019575323.issue37846@roundup.psfhosted.org>


New submission from Windson Yang <wiwindson at outlook.com>:

At the beginning of https://docs.python.org/3.7/library/io.html#io.RawIOBase, we declared that 

> Binary I/O (also called buffered I/O)
and 
> Raw I/O (also called unbuffered I/O)

But we didn't mention if Text I/O use buffer or not which led to confusion. Even though we talked about it later in https://docs.python.org/3.7/library/io.html#class-hierarchy

> The TextIOBase ABC, another subclass of IOBase, deals with streams whose bytes represent text, and handles encoding and decoding to and from strings. TextIOWrapper, which extends it, is a buffered text interface to a buffered raw stream (BufferedIOBase). Finally, StringIO is an in-memory stream for text.

IMO, it will be better to declare 'Reads and writes are internally buffered in order to speed things up' at the very beginning in 

> Text I/O
> Text I/O expects and produces str objects...

or maybe

> class io.TextIOBase
> Base class for text streams. This class provides a character and line based interface to stream I/O. It inherits IOBase. There is no public constructor.

----------
assignee: docs at python
components: Documentation
messages: 349633
nosy: Windson Yang, docs at python
priority: normal
severity: normal
status: open
title: declare that Text I/O use buffer inside
type: enhancement
versions: Python 3.8

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

From report at bugs.python.org  Wed Aug 14 01:47:14 2019
From: report at bugs.python.org (Inada Naoki)
Date: Wed, 14 Aug 2019 05:47:14 +0000
Subject: [docs] [issue37846] declare that Text I/O use buffer inside
In-Reply-To: <1565750649.11.0.831019575323.issue37846@roundup.psfhosted.org>
Message-ID: <1565761634.43.0.480109491677.issue37846@roundup.psfhosted.org>


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

It's just an implementation detail.  Python implementation and C implementation behave slightly different.  But user program shouldn't rely on the detail.

Why do you think implementation details should be declared?
Who needs the information?

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

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

From report at bugs.python.org  Wed Aug 14 02:20:57 2019
From: report at bugs.python.org (Windson Yang)
Date: Wed, 14 Aug 2019 06:20:57 +0000
Subject: [docs] [issue37846] declare that Text I/O use buffer inside
In-Reply-To: <1565750649.11.0.831019575323.issue37846@roundup.psfhosted.org>
Message-ID: <1565763657.71.0.452393653834.issue37846@roundup.psfhosted.org>


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

I found the document is not that clear when I try to understand what happens when Python read/write a file. I'm not sure who also needs this information. As you said, It wouldn't help the user program in Python. However, make it more clear maybe help users have a better feeling of what is happening under the hood.

----------

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

From saiakshay72 at gmail.com  Tue Aug 13 12:06:02 2019
From: saiakshay72 at gmail.com (Sai Akshay Erupaka)
Date: Tue, 13 Aug 2019 21:36:02 +0530
Subject: [docs] I am Sai Akshay Erupaka I found an mistake in the
 documentation in the regular expressions part
Message-ID: <CAPBLZWj-egKdKt2FiqEg1Z9gdKOnfXE-yqOAE-vntdGNpYjCtw@mail.gmail.com>

Regular expressions



*?, +?, ??

The '*', '+', and '?' qualifiers are all greedy; they match as much text as
possible. Sometimes this behaviour isn?t desired; if the RE <.*> is matched
against '<a> b <c>', it will match the entire string, and not just '<a>'.
Adding ? after the qualifier makes it perform the match in non-greedy or
minimal fashion; as few characters as possible will be matched. Using the
RE <.*?> will match only '<a>'.

It says that the RE <.*?> matches only <a> but it also matches <c>




 I am also attaching the pdf document with the same content
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190813/11ff2441/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Python documenataion bug-converted.pdf
Type: application/pdf
Size: 94759 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190813/11ff2441/attachment-0001.pdf>

From report at bugs.python.org  Wed Aug 14 07:05:23 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 14 Aug 2019 11:05:23 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1565780723.35.0.179550960749.issue36502@roundup.psfhosted.org>


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


New changeset 6bccbe7dfb998af862a183f2c36f0d4603af2c29 by Victor Stinner (Greg Price) in branch 'master':
bpo-36502: Correct documentation of str.isspace() (GH-15019)
https://github.com/python/cpython/commit/6bccbe7dfb998af862a183f2c36f0d4603af2c29


----------

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

From report at bugs.python.org  Wed Aug 14 09:41:28 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 14 Aug 2019 13:41:28 +0000
Subject: [docs] [issue37256] urllib.request.Request documentation
 erroneously refers to the "final two"
In-Reply-To: <1560366755.97.0.221740241329.issue37256@roundup.psfhosted.org>
Message-ID: <1565790088.29.0.353676048811.issue37256@roundup.psfhosted.org>


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


----------
pull_requests: +15000
pull_request: https://github.com/python/cpython/pull/15277

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

From report at bugs.python.org  Wed Aug 14 09:41:34 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 14 Aug 2019 13:41:34 +0000
Subject: [docs] [issue37256] urllib.request.Request documentation
 erroneously refers to the "final two"
In-Reply-To: <1560366755.97.0.221740241329.issue37256@roundup.psfhosted.org>
Message-ID: <1565790094.54.0.0574144515367.issue37256@roundup.psfhosted.org>


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


----------
pull_requests: +15001
pull_request: https://github.com/python/cpython/pull/15278

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

From report at bugs.python.org  Wed Aug 14 09:55:57 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 14 Aug 2019 13:55:57 +0000
Subject: [docs] [issue37256] urllib.request.Request documentation
 erroneously refers to the "final two"
In-Reply-To: <1560366755.97.0.221740241329.issue37256@roundup.psfhosted.org>
Message-ID: <1565790957.69.0.548033102385.issue37256@roundup.psfhosted.org>


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


New changeset 3e1f135b26cf5fb3583d7e75d39b7b7a9edb472c by Miss Islington (bot) in branch '3.7':
bpo-37256: Wording in Request class docs (GH-14792)
https://github.com/python/cpython/commit/3e1f135b26cf5fb3583d7e75d39b7b7a9edb472c


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

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

From report at bugs.python.org  Wed Aug 14 11:21:36 2019
From: report at bugs.python.org (Michael Anckaert)
Date: Wed, 14 Aug 2019 15:21:36 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1565796096.0.0.171567215599.issue37823@roundup.psfhosted.org>


Change by Michael Anckaert <michael.anckaert at sinax.be>:


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

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

From report at bugs.python.org  Wed Aug 14 11:23:17 2019
From: report at bugs.python.org (Michael Anckaert)
Date: Wed, 14 Aug 2019 15:23:17 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1565796197.5.0.658628491061.issue37823@roundup.psfhosted.org>


Michael Anckaert <michael.anckaert at sinax.be> added the comment:

I created a PR for this issue (PR 15281). If any changes are required I'm more than happy to make them.

----------
nosy: +michaelanckaert

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

From report at bugs.python.org  Wed Aug 14 11:40:51 2019
From: report at bugs.python.org (Michael Anckaert)
Date: Wed, 14 Aug 2019 15:40:51 +0000
Subject: [docs] [issue19820] docs are missing info about module attributes
In-Reply-To: <1385620941.03.0.287546381963.issue19820@psf.upfronthosting.co.za>
Message-ID: <1565797250.99.0.174526746876.issue19820@roundup.psfhosted.org>


Michael Anckaert <michael.anckaert at sinax.be> added the comment:

As far as I can tell there is at least some information missing from the 'Types and members' section. Not all attributes are listed in the table. 

For example the attribute __cached__ is missing from the module type but it is documented in the inspect module. 

I can update the docs but I would rely on the comments in Lib/inspect.py on what to include. Executing inspect.getmembers on a module returns a lot more attributes than documented in ismodule.

----------
nosy: +michaelanckaert

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

From report at bugs.python.org  Wed Aug 14 13:10:14 2019
From: report at bugs.python.org (Eric Snow)
Date: Wed, 14 Aug 2019 17:10:14 +0000
Subject: [docs] [issue19820] docs are missing info about module attributes
In-Reply-To: <1385620941.03.0.287546381963.issue19820@psf.upfronthosting.co.za>
Message-ID: <1565802614.75.0.0299807685506.issue19820@roundup.psfhosted.org>


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

The relevant module attributes are described in the importlib docs: https://docs.python.org/3/library/importlib.html#importlib.abc.Loader.load_module

----------
versions: +Python 3.7, Python 3.8, Python 3.9 -Python 3.3, Python 3.4

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

From report at bugs.python.org  Wed Aug 14 13:46:09 2019
From: report at bugs.python.org (Sanyam Khurana)
Date: Wed, 14 Aug 2019 17:46:09 +0000
Subject: [docs] [issue37775] update doc of compileall
In-Reply-To: <1565113080.48.0.890450145581.issue37775@roundup.psfhosted.org>
Message-ID: <1565804769.94.0.871905241364.issue37775@roundup.psfhosted.org>


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

I've checked and approved this PR.

This needs a core-review now.

Thanks, Hai for your contribution.

----------
nosy: +CuriousLearner, Mariatta

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

From report at bugs.python.org  Wed Aug 14 13:55:12 2019
From: report at bugs.python.org (Emmanuel Arias)
Date: Wed, 14 Aug 2019 17:55:12 +0000
Subject: [docs] [issue19820] docs are missing info about module attributes
In-Reply-To: <1385620941.03.0.287546381963.issue19820@psf.upfronthosting.co.za>
Message-ID: <1565805312.16.0.264579784197.issue19820@roundup.psfhosted.org>


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

> I can update the docs but I would rely on the comments in Lib/inspect.py on what to include. Executing inspect.getmembers on a module returns a lot more attributes than documented in ismodule.

I can help too.

----------
nosy: +eamanu

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

From report at bugs.python.org  Wed Aug 14 15:00:03 2019
From: report at bugs.python.org (Michael Anckaert)
Date: Wed, 14 Aug 2019 19:00:03 +0000
Subject: [docs] [issue19820] docs are missing info about module attributes
In-Reply-To: <1385620941.03.0.287546381963.issue19820@psf.upfronthosting.co.za>
Message-ID: <1565809203.74.0.183340608147.issue19820@roundup.psfhosted.org>


Michael Anckaert <michael.anckaert at sinax.be> added the comment:

@emmanuel: thanks for offering your help. 

I made a first attempt at improving the docs in this branch: https://github.com/MichaelAnckaert/cpython/tree/bpo-19820

----------

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

From report at bugs.python.org  Wed Aug 14 17:11:36 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 14 Aug 2019 21:11:36 +0000
Subject: [docs] [issue37826] Document PEP 3134 in tutorials/errors.rst
In-Reply-To: <1565548566.46.0.213467869715.issue37826@roundup.psfhosted.org>
Message-ID: <1565817096.29.0.763853088135.issue37826@roundup.psfhosted.org>


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


New changeset dcfe111eb5602333135b8776996332a8dcf59392 by Miss Islington (bot) (Abhilash Raj) in branch 'master':
bpo-37826: Document exception chaining in Python tutorial for errors. (GH-15243)
https://github.com/python/cpython/commit/dcfe111eb5602333135b8776996332a8dcf59392


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

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

From report at bugs.python.org  Wed Aug 14 17:14:46 2019
From: report at bugs.python.org (Ashwin Ramaswami)
Date: Wed, 14 Aug 2019 21:14:46 +0000
Subject: [docs] [issue37860] Add netlify deploy preview for docs
Message-ID: <1565817286.53.0.142673590989.issue37860@roundup.psfhosted.org>


New submission from Ashwin Ramaswami <aramaswamis at gmail.com>:

It would be good to preview the cpython documentation on PRs using Netlify.

See https://github.com/python/core-workflow/issues/348

----------
assignee: docs at python
components: Documentation
messages: 349752
nosy: docs at python, epicfaace
priority: normal
severity: normal
status: open
title: Add netlify deploy preview for docs
versions: Python 3.9

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

From report at bugs.python.org  Wed Aug 14 17:15:03 2019
From: report at bugs.python.org (Ashwin Ramaswami)
Date: Wed, 14 Aug 2019 21:15:03 +0000
Subject: [docs] [issue37860] Add netlify deploy preview for docs
In-Reply-To: <1565817286.53.0.142673590989.issue37860@roundup.psfhosted.org>
Message-ID: <1565817303.83.0.293727892521.issue37860@roundup.psfhosted.org>


Change by Ashwin Ramaswami <aramaswamis at gmail.com>:


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

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

From report at bugs.python.org  Wed Aug 14 17:16:18 2019
From: report at bugs.python.org (Ashwin Ramaswami)
Date: Wed, 14 Aug 2019 21:16:18 +0000
Subject: [docs] [issue37860] Add netlify deploy preview for docs
In-Reply-To: <1565817286.53.0.142673590989.issue37860@roundup.psfhosted.org>
Message-ID: <1565817378.94.0.824235654999.issue37860@roundup.psfhosted.org>


Change by Ashwin Ramaswami <aramaswamis at gmail.com>:


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

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

From report at bugs.python.org  Wed Aug 14 18:03:14 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 14 Aug 2019 22:03:14 +0000
Subject: [docs] [issue37775] update doc of compileall
In-Reply-To: <1565113080.48.0.890450145581.issue37775@roundup.psfhosted.org>
Message-ID: <1565820194.57.0.50068050546.issue37775@roundup.psfhosted.org>


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


New changeset 68e495df909a33e719e3f1ef5b4893ec785e10a4 by Victor Stinner (Hai Shi) in branch 'master':
bpo-37775: Update compileall doc for invalidation_mode parameter (GH-15148)
https://github.com/python/cpython/commit/68e495df909a33e719e3f1ef5b4893ec785e10a4


----------

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

From report at bugs.python.org  Wed Aug 14 18:03:22 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 14 Aug 2019 22:03:22 +0000
Subject: [docs] [issue37775] update doc of compileall
In-Reply-To: <1565113080.48.0.890450145581.issue37775@roundup.psfhosted.org>
Message-ID: <1565820202.76.0.220927146276.issue37775@roundup.psfhosted.org>


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


----------
pull_requests: +15017
pull_request: https://github.com/python/cpython/pull/15294

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

From report at bugs.python.org  Wed Aug 14 18:22:05 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 14 Aug 2019 22:22:05 +0000
Subject: [docs] [issue37775] update doc of compileall
In-Reply-To: <1565113080.48.0.890450145581.issue37775@roundup.psfhosted.org>
Message-ID: <1565821325.94.0.592294844694.issue37775@roundup.psfhosted.org>


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


New changeset dbe4c286ce28402c3bce71d568ae55b91280e777 by Miss Islington (bot) in branch '3.8':
bpo-37775: Update compileall doc for invalidation_mode parameter (GH-15148)
https://github.com/python/cpython/commit/dbe4c286ce28402c3bce71d568ae55b91280e777


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

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

From report at bugs.python.org  Wed Aug 14 21:13:06 2019
From: report at bugs.python.org (Kim Oldfield)
Date: Thu, 15 Aug 2019 01:13:06 +0000
Subject: [docs] [issue37862] Search doesn't find built-in functions
Message-ID: <1565831586.7.0.196033639625.issue37862@roundup.psfhosted.org>


New submission from Kim Oldfield <python at oldfield.wattle.id.au>:

The python 3 documentation search
https://docs.python.org/3/search.html
doesn't always find built-in functions.

For example, searching for "zip" takes me to
https://docs.python.org/3/search.html?q=zip

I would expect the first match to be a link to
https://docs.python.org/3/library/functions.html#zip
but I can't see a link to this page anywhere in the 146 results.

----------
assignee: docs at python
components: Documentation
messages: 349781
nosy: docs at python, kim.oldfield
priority: normal
severity: normal
status: open
title: Search doesn't find built-in functions
type: behavior
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Wed Aug 14 23:17:09 2019
From: report at bugs.python.org (Greg Price)
Date: Thu, 15 Aug 2019 03:17:09 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1565839029.23.0.838184213119.issue36502@roundup.psfhosted.org>


Change by Greg Price <gnprice at gmail.com>:


----------
pull_requests: +15019
pull_request: https://github.com/python/cpython/pull/15296

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

From report at bugs.python.org  Thu Aug 15 00:48:02 2019
From: report at bugs.python.org (Greg Price)
Date: Thu, 15 Aug 2019 04:48:02 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1565844482.01.0.0224373287408.issue36502@roundup.psfhosted.org>


Change by Greg Price <gnprice at gmail.com>:


----------
pull_requests: +15026
pull_request: https://github.com/python/cpython/pull/15301

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

From report at bugs.python.org  Thu Aug 15 08:47:03 2019
From: report at bugs.python.org (SilentGhost)
Date: Thu, 15 Aug 2019 12:47:03 +0000
Subject: [docs] [issue37867] docs says subprocess.run accepts a string but
 this does not work on linux
In-Reply-To: <1565865522.62.0.177919974549.issue37867@roundup.psfhosted.org>
Message-ID: <1565873223.59.0.22231409286.issue37867@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

The only place this phrase appears is in CompletedProcess.args description and it is correct there. Whether args arguments of subprocess.run (or generally Popen) can be a list or a string is discussed in Frequently Used Arguments section, and it is perfectly clear from reading the text under which condition you can pass a string as args argument. I don't think anything needs fixing, both implementation and docs are correct.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +SilentGhost, docs at python
type:  -> behavior

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

From report at bugs.python.org  Thu Aug 15 08:52:56 2019
From: report at bugs.python.org (simon mackenzie)
Date: Thu, 15 Aug 2019 12:52:56 +0000
Subject: [docs] [issue37867] docs says subprocess.run accepts a string but
 this does not work on linux
In-Reply-To: <1565873223.59.0.22231409286.issue37867@roundup.psfhosted.org>
Message-ID: <CAGG2XGeMwcVzJwtxUJeN4B_4zCFrij-tFtDF_zTsmMbNBdWTwA@mail.gmail.com>


simon mackenzie <simonm3 at gmail.com> added the comment:

Technically true but I am not the first person to have incorrectly
interpreted this that it can be a string which suggests it is not clear to
the reader. Maybe should be explicitly stated in the description of run as
it is not obvious or intuitive.

On Thu, 15 Aug 2019 at 13:47, SilentGhost <report at bugs.python.org> wrote:

>
> SilentGhost <ghost.adh at runbox.com> added the comment:
>
> The only place this phrase appears is in CompletedProcess.args description
> and it is correct there. Whether args arguments of subprocess.run (or
> generally Popen) can be a list or a string is discussed in Frequently Used
> Arguments section, and it is perfectly clear from reading the text under
> which condition you can pass a string as args argument. I don't think
> anything needs fixing, both implementation and docs are correct.
>
> ----------
> assignee:  -> docs at python
> components: +Documentation
> nosy: +SilentGhost, docs at python
> type:  -> behavior
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue37867>
> _______________________________________
>

----------
title: docs says subprocess.run  accepts a string but this does not work on linux -> docs says subprocess.run accepts a string but this does not work on linux

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

From report at bugs.python.org  Thu Aug 15 10:04:59 2019
From: report at bugs.python.org (SilentGhost)
Date: Thu, 15 Aug 2019 14:04:59 +0000
Subject: [docs] [issue37867] docs says subprocess.run accepts a string but
 this does not work on linux
In-Reply-To: <1565865522.62.0.177919974549.issue37867@roundup.psfhosted.org>
Message-ID: <1565877899.94.0.743385738963.issue37867@roundup.psfhosted.org>


SilentGhost <ghost.adh at runbox.com> added the comment:

But docs don't say that at all. You're looking at description of an attribute of returned object. And of course it can be a string, under certain conditions. The attributes of CompletedProcess and function arguments are described in the standard way, and I haven't heard of anyone mixing the two before.

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

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

From report at bugs.python.org  Thu Aug 15 10:17:52 2019
From: report at bugs.python.org (simon mackenzie)
Date: Thu, 15 Aug 2019 14:17:52 +0000
Subject: [docs] [issue37867] docs says subprocess.run accepts a string but
 this does not work on linux
In-Reply-To: <1565877899.94.0.743385738963.issue37867@roundup.psfhosted.org>
Message-ID: <CAGG2XGfcXtQ==GTqrnbF-dEtJ3HPkN1-UZ_UqSz51jRis8DB2Q@mail.gmail.com>


simon mackenzie <simonm3 at gmail.com> added the comment:

Would be clearer if the arguments were listed before the return object.

On Thu, 15 Aug 2019 at 15:05, SilentGhost <report at bugs.python.org> wrote:

>
> SilentGhost <ghost.adh at runbox.com> added the comment:
>
> But docs don't say that at all. You're looking at description of an
> attribute of returned object. And of course it can be a string, under
> certain conditions. The attributes of CompletedProcess and function
> arguments are described in the standard way, and I haven't heard of anyone
> mixing the two before.
>
> ----------
> resolution:  -> not a bug
> stage:  -> resolved
> status: open -> closed
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <https://bugs.python.org/issue37867>
> _______________________________________
>

----------

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

From report at bugs.python.org  Thu Aug 15 12:22:22 2019
From: report at bugs.python.org (Brett Cannon)
Date: Thu, 15 Aug 2019 16:22:22 +0000
Subject: [docs] [issue37860] Add netlify deploy preview for docs
In-Reply-To: <1565817286.53.0.142673590989.issue37860@roundup.psfhosted.org>
Message-ID: <1565886142.08.0.262729201932.issue37860@roundup.psfhosted.org>


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


----------
nosy: +brett.cannon

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

From report at bugs.python.org  Fri Aug 16 04:27:39 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 16 Aug 2019 08:27:39 +0000
Subject: [docs] [issue37256] urllib.request.Request documentation
 erroneously refers to the "final two"
In-Reply-To: <1560366755.97.0.221740241329.issue37256@roundup.psfhosted.org>
Message-ID: <1565944059.1.0.563869481969.issue37256@roundup.psfhosted.org>


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


New changeset f9919121460bffc04f935dbdb85f0af3ffbd3ddf by Miss Islington (bot) in branch '3.8':
bpo-37256: Wording in Request class docs (GH-14792)
https://github.com/python/cpython/commit/f9919121460bffc04f935dbdb85f0af3ffbd3ddf


----------

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

From report at bugs.python.org  Fri Aug 16 04:28:18 2019
From: report at bugs.python.org (Senthil Kumaran)
Date: Fri, 16 Aug 2019 08:28:18 +0000
Subject: [docs] [issue37256] urllib.request.Request documentation
 erroneously refers to the "final two"
In-Reply-To: <1560366755.97.0.221740241329.issue37256@roundup.psfhosted.org>
Message-ID: <1565944098.81.0.338065431622.issue37256@roundup.psfhosted.org>


Senthil Kumaran <senthil at uthcode.com> added the comment:

Thank you for the patch, CuriousLearner.

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

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

From report at bugs.python.org  Fri Aug 16 13:26:02 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 16 Aug 2019 17:26:02 +0000
Subject: [docs] [issue25299] TypeError: __init__() takes at least 4
 arguments (4 given)
In-Reply-To: <1443785146.27.0.85852377889.issue25299@psf.upfronthosting.co.za>
Message-ID: <1565976362.43.0.231300962264.issue25299@roundup.psfhosted.org>


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

> this argument defaults to "None"

Am leaning to the fact that this works as required. The documentation does not just say defaults to none. It says:

With the 'store_const' and 'append_const' actions, the const keyword argument must be given. For other actions, it defaults to None.

In the scenario, you have given, you are using 'store_const' so the const keyword argument must be given.

This should be closed If you agree with what I have just stated.

----------

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

From report at bugs.python.org  Fri Aug 16 15:53:55 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 16 Aug 2019 19:53:55 +0000
Subject: [docs] [issue37878] sub-ineterpreters : Document
 PyThreadState_DeleteCurrent() ?
Message-ID: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>


New submission from Joannah Nanjekye <nanjekyejoannah at gmail.com>:

I just noticed that PyThreadState_DeleteCurrent()in Python/pystate.c is not documented.

Relevant documentation should go in Doc/c-api/init.rst If no one objects to this.

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 349881
nosy: docs at python, eric.snow, nanjekyejoannah, ncoghlan, vstinner
priority: normal
severity: normal
stage: needs patch
status: open
title: sub-ineterpreters : Document PyThreadState_DeleteCurrent() ?
versions: Python 3.8, Python 3.9

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

From report at bugs.python.org  Fri Aug 16 15:55:46 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 16 Aug 2019 19:55:46 +0000
Subject: [docs] [issue37878] Sub-ineterpreters : Document
 PyThreadState_DeleteCurrent() ?
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1565985346.92.0.52556417275.issue37878@roundup.psfhosted.org>


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


----------
title: sub-ineterpreters : Document PyThreadState_DeleteCurrent() ? -> Sub-ineterpreters : Document PyThreadState_DeleteCurrent() ?

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

From report at bugs.python.org  Fri Aug 16 15:57:21 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 16 Aug 2019 19:57:21 +0000
Subject: [docs] [issue37878] Sub-Interpreters : Document
 PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1565985441.17.0.60227147726.issue37878@roundup.psfhosted.org>


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


----------
title: Sub-ineterpreters : Document PyThreadState_DeleteCurrent() ? -> Sub-Interpreters : Document PyThreadState_DeleteCurrent()

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

From report at bugs.python.org  Fri Aug 16 16:00:06 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Fri, 16 Aug 2019 20:00:06 +0000
Subject: [docs] [issue37878] Sub-Interpreters : Document
 PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1565985606.51.0.454869657172.issue37878@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Aug 16 17:58:04 2019
From: report at bugs.python.org (Abhilash Raj)
Date: Fri, 16 Aug 2019 21:58:04 +0000
Subject: [docs] [issue37826] Document PEP 3134 in tutorials/errors.rst
In-Reply-To: <1565548566.46.0.213467869715.issue37826@roundup.psfhosted.org>
Message-ID: <1565992684.47.0.704358513296.issue37826@roundup.psfhosted.org>


Change by Abhilash Raj <raj.abhilash1 at gmail.com>:


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

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

From report at bugs.python.org  Sat Aug 17 03:09:09 2019
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 17 Aug 2019 07:09:09 +0000
Subject: [docs] [issue36947] [Good first issue] Fix 3.3.3.1 Metaclasses
 Documentation
In-Reply-To: <1558103271.07.0.643884881507.issue36947@roundup.psfhosted.org>
Message-ID: <1566025749.71.0.459345297261.issue36947@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sat Aug 17 09:42:50 2019
From: report at bugs.python.org (A. Skrobov)
Date: Sat, 17 Aug 2019 13:42:50 +0000
Subject: [docs] [issue25299] TypeError: __init__() takes at least 4
 arguments (4 given)
In-Reply-To: <1443785146.27.0.85852377889.issue25299@psf.upfronthosting.co.za>
Message-ID: <1566049370.48.0.476950697389.issue25299@roundup.psfhosted.org>


A. Skrobov <tyomitch at gmail.com> added the comment:

Joannah, I see that under #25314, the docs were updated to match the implementation: https://github.com/python/cpython/commit/b4912b8ed367e540ee060fe912f841cc764fd293

On the other hand, the discussion here (from 2015) and on #25314 (from 2016) includes suggestions for improvements in the implementation as well.

----------

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

From godabavinay at gmail.com  Thu Aug 15 12:08:05 2019
From: godabavinay at gmail.com (Vinay Godaba)
Date: Thu, 15 Aug 2019 21:38:05 +0530
Subject: [docs] ISSUE I FOUND IN TUPLES
Message-ID: <CALg-vLHjn9eGvGuNGj2o+K5bOK8dfBzL15h__JqD04aSNutuYw@mail.gmail.com>

Hello I'm Vinay
recently I started learning python and in this process, I noticed there is
a glitch in tuples.
I don't know whether it's a glitch or not but what I noticed is a list
containing single list can identify inner list as a single element of the
list whereas in tuples a tuple containing single tuple is unable to
identify as a single element unless a comma is specified.

# in case of lists
a = [[1,2,3]]
for i in a:
    print(i)   # this outputs [1,2,3]

# in case of tuples
a = ((1,2,3))
for i in a:
    print(i)
# outputs as
1
2
3

# but if we specify comma
a = ((1,2,3),)
for i in a:
    print(i)  # this outputs (1,2,3)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190815/2dc5b14d/attachment.html>

From report at bugs.python.org  Sat Aug 17 20:40:44 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 18 Aug 2019 00:40:44 +0000
Subject: [docs] [issue25299] TypeError: __init__() takes at least 4
 arguments (4 given)
In-Reply-To: <1443785146.27.0.85852377889.issue25299@psf.upfronthosting.co.za>
Message-ID: <1566088844.72.0.503062615292.issue25299@roundup.psfhosted.org>


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

Since both the docs and implementation now match, I suggest we close this and open a new issue suggesting to change the implementation back to make const=None when action='store_const'.

----------
stage: needs patch -> resolved

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

From report at bugs.python.org  Sat Aug 17 20:42:03 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 18 Aug 2019 00:42:03 +0000
Subject: [docs] [issue25299] TypeError: __init__() takes at least 4
 arguments (4 given)
In-Reply-To: <1443785146.27.0.85852377889.issue25299@psf.upfronthosting.co.za>
Message-ID: <1566088923.03.0.963829634816.issue25299@roundup.psfhosted.org>


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

Opened issue37880 to track this change.

----------

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

From report at bugs.python.org  Sat Aug 17 23:09:58 2019
From: report at bugs.python.org (Brendan Barnwell)
Date: Sun, 18 Aug 2019 03:09:58 +0000
Subject: [docs] [issue16697] argparse kwarg 'choices' documentation
In-Reply-To: <1355666035.13.0.877787561314.issue16697@psf.upfronthosting.co.za>
Message-ID: <1566097798.05.0.0871166017723.issue16697@roundup.psfhosted.org>


Brendan Barnwell <brenbarn at brenbarn.net> added the comment:

This issue has sat idle for six years.  Meanwhile, the docs are still incorrect, giving every user wrong information about how the module works.  Can we consider just changing the documentation instead of worrying about what the behavior should be or what the rationale is?

----------
nosy: +BrenBarn
versions: +Python 3.5, Python 3.6, Python 3.7

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

From report at bugs.python.org  Sun Aug 18 14:36:18 2019
From: report at bugs.python.org (=?utf-8?q?R=C3=A9mi_Lapeyre?=)
Date: Sun, 18 Aug 2019 18:36:18 +0000
Subject: [docs] [issue37883] threading.Lock.locked is not documented
Message-ID: <1566153378.15.0.0440090654943.issue37883@roundup.psfhosted.org>


New submission from R?mi Lapeyre <remi.lapeyre at henki.fr>:

As far as I can tell, it has never been documented. I'm not sure if it is deprecated but it has a docstring so it seems to me, that it just needs documentation in Doc/Library/threading.rst

PS: I don't know how to set the beginner friendly flag.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 349923
nosy: docs at python, remi.lapeyre
priority: normal
severity: normal
status: open
title: threading.Lock.locked is not documented
type: enhancement
versions: Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Mon Aug 19 01:54:24 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 19 Aug 2019 05:54:24 +0000
Subject: [docs] [issue37862] Search doesn't find built-in functions
In-Reply-To: <1565831586.7.0.196033639625.issue37862@roundup.psfhosted.org>
Message-ID: <1566194064.42.0.539715834014.issue37862@roundup.psfhosted.org>


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

The search page is the last thing one should use.  There is the index
https://docs.python.org/3/genindex-Z.html
and for builtin function, chapter 2 of the library manual.
https://docs.python.org/3/library/functions.html#built-in-functions

I don't know if the operation of the search page is documented anytwhere.

----------
nosy: +terry.reedy
versions:  -Python 3.5, Python 3.6

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

From report at bugs.python.org  Mon Aug 19 05:53:40 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 19 Aug 2019 09:53:40 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1566208420.83.0.209995676503.issue36502@roundup.psfhosted.org>


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


New changeset 8c1c426a631ba02357112657193f82c58d3e08b4 by Victor Stinner (Greg Price) in branch '3.8':
bpo-36502: Correct documentation of str.isspace() (GH-15019) (GH-15296)
https://github.com/python/cpython/commit/8c1c426a631ba02357112657193f82c58d3e08b4


----------

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

From report at bugs.python.org  Mon Aug 19 05:53:53 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 19 Aug 2019 09:53:53 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1566208433.36.0.992764883592.issue36502@roundup.psfhosted.org>


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


----------
pull_requests: +15050
pull_request: https://github.com/python/cpython/pull/15332

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

From report at bugs.python.org  Mon Aug 19 06:10:23 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 19 Aug 2019 10:10:23 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1566209423.31.0.212187671723.issue36502@roundup.psfhosted.org>


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


New changeset 0fcdd8d6d67f57733203fc79e6a07a89b924a390 by Miss Islington (bot) in branch '3.7':
bpo-36502: Correct documentation of str.isspace() (GH-15019) (GH-15296)
https://github.com/python/cpython/commit/0fcdd8d6d67f57733203fc79e6a07a89b924a390


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

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

From report at bugs.python.org  Mon Aug 19 06:14:33 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 19 Aug 2019 10:14:33 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1566209673.44.0.880809431233.issue36502@roundup.psfhosted.org>


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

str.isspace() documentation has been fixed, thanks Greg Price for the fix! I close the issue.

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

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

From report at bugs.python.org  Mon Aug 19 06:40:00 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 19 Aug 2019 10:40:00 +0000
Subject: [docs] [issue37878] Sub-Interpreters : Document
 PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1566211200.15.0.534809978575.issue37878@roundup.psfhosted.org>


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

I'm not sure why PyThreadState_DeleteCurrent() is exposed. Why would anyone use it?

It is used internally by the _thread module when the thread function completes.

I suggest to make the function internal instead of documenting it.

Eric, Joannah: what do you think?

----------

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

From report at bugs.python.org  Mon Aug 19 11:31:01 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Mon, 19 Aug 2019 15:31:01 +0000
Subject: [docs] [issue37878] Sub-Interpreters : Document
 PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1566228661.44.0.499997134577.issue37878@roundup.psfhosted.org>


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

>From what I know the GIL is released by calling PyEval_ReleaseThread() or PyEval_SaveThread(). 

I see we can use PyThreadState_Delete() to clean up-specifically destroy thread state but does not release the GIL and requires a thread state. On the other hand, PyThreadState_DeleteCurrent() allows to both clean up the current thread state - no thread state is required as well release the GIL which is convenient. I would not fight so much to keep it public given we have PyEval_ReleaseThread() or PyEval_SaveThread().

----------

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

From report at bugs.python.org  Mon Aug 19 19:33:17 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 19 Aug 2019 23:33:17 +0000
Subject: [docs] [issue37878] Sub-Interpreters : Document
 PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1566257597.3.0.527107633415.issue37878@roundup.psfhosted.org>


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

Is it safe to call PyThreadState_DeleteCurrent()?

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

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

From report at bugs.python.org  Mon Aug 19 20:15:35 2019
From: report at bugs.python.org (Pablo Galindo Salgado)
Date: Tue, 20 Aug 2019 00:15:35 +0000
Subject: [docs] [issue37883] threading.Lock.locked is not documented
In-Reply-To: <1566153378.15.0.0440090654943.issue37883@roundup.psfhosted.org>
Message-ID: <1566260135.27.0.329913048134.issue37883@roundup.psfhosted.org>


Change by Pablo Galindo Salgado <pablogsal at gmail.com>:


----------
keywords: +newcomer friendly

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

From report at bugs.python.org  Mon Aug 19 21:33:56 2019
From: report at bugs.python.org (Greg Price)
Date: Tue, 20 Aug 2019 01:33:56 +0000
Subject: [docs] [issue36502] str.isspace() for U+00A0 and U+202F differs
 from document
In-Reply-To: <1554186967.56.0.21483381742.issue36502@roundup.psfhosted.org>
Message-ID: <1566264836.07.0.45444041395.issue36502@roundup.psfhosted.org>


Greg Price <gnprice at gmail.com> added the comment:

Thanks Victor for the reviews and merges!

(Unmarking 2.7, because https://docs.python.org/2/library/stdtypes.html seems to not have this issue.)

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

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

From echen at blizzard.com  Mon Aug 19 12:54:32 2019
From: echen at blizzard.com (Evan Chen)
Date: Mon, 19 Aug 2019 16:54:32 +0000
Subject: [docs] Bug in documentation: 'Pythonwin' under 'platform-specific
 GUI toolkits' links to the wrong place.
Message-ID: <MWHPR1201MB01744C4F52C6A6B9169DEE42C0A80@MWHPR1201MB0174.namprd12.prod.outlook.com>

On this page here (screenshot below)  https://docs.python.org/3/faq/gui.html#what-platform-specific-gui-toolkits-exist-for-python,
"Pythonwin" links to https://docs.python.org/3/faq/windows.html#windows-faq.

I think it should link to https://github.com/mhammond/pywin32

Thank you!

- Evan

[cid:image003.jpg at 01D55674.189F5D30]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190819/2a53d5e0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 75538 bytes
Desc: image003.jpg
URL: <http://mail.python.org/pipermail/docs/attachments/20190819/2a53d5e0/attachment-0001.jpg>

From report at bugs.python.org  Tue Aug 20 03:21:07 2019
From: report at bugs.python.org (Niels Albers)
Date: Tue, 20 Aug 2019 07:21:07 +0000
Subject: [docs] [issue37891] Exceptions tutorial page does not mention raise
 from
Message-ID: <1566285667.91.0.992762773609.issue37891@roundup.psfhosted.org>


New submission from Niels Albers <nralbers at gmail.com>:

raise <Exception> from <exception instance> has been in the language since python 3, yet the tutorial page teaching about exceptions does not mention it. (see https://docs.python.org/3.7/tutorial/errors.html#raising-exceptions)
It would be especially helpful to language newcomers to touch on the possibility of passing error context when raising a new exception in an exception handler.

----------
assignee: docs at python
components: Documentation
messages: 349994
nosy: Niels Albers, docs at python
priority: normal
severity: normal
status: open
title: Exceptions tutorial page does not mention raise from
versions: Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Tue Aug 20 03:22:12 2019
From: report at bugs.python.org (Niels Albers)
Date: Tue, 20 Aug 2019 07:22:12 +0000
Subject: [docs] [issue37891] Exceptions tutorial page does not mention raise
 from
In-Reply-To: <1566285667.91.0.992762773609.issue37891@roundup.psfhosted.org>
Message-ID: <1566285732.6.0.533915605414.issue37891@roundup.psfhosted.org>


Change by Niels Albers <nralbers at gmail.com>:


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

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

From report at bugs.python.org  Tue Aug 20 11:08:41 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 20 Aug 2019 15:08:41 +0000
Subject: [docs] [issue37891] Exceptions tutorial page does not mention raise
 from
In-Reply-To: <1566285667.91.0.992762773609.issue37891@roundup.psfhosted.org>
Message-ID: <1566313721.85.0.0612568213789.issue37891@roundup.psfhosted.org>


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

Thanks for spotting this omission.  Would you like to submit a PR with a short paragraph on exception chaining and "raise from"?

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

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

From report at bugs.python.org  Tue Aug 20 14:52:16 2019
From: report at bugs.python.org (Srinivas Nyayapati)
Date: Tue, 20 Aug 2019 18:52:16 +0000
Subject: [docs] [issue37891] Exceptions tutorial page does not mention raise
 from
In-Reply-To: <1566285667.91.0.992762773609.issue37891@roundup.psfhosted.org>
Message-ID: <1566327136.01.0.876523670032.issue37891@roundup.psfhosted.org>


Srinivas Nyayapati <shireenrao at gmail.com> added the comment:

In case Niels Albers is not interested, can I submit a PR?
I noticed the linked raise reference documentation from the tutorial having details on exception chaining (https://docs.python.org/3.7/reference/simple_stmts.html#raise). Does it make sense to mention exception chaining in the tutorial and say "read details in the reference docs"? Or as you mentioned.. just write a short paragraph on exception chaining and give an example in the tutorial?

----------
nosy: +shireenrao

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

From report at bugs.python.org  Tue Aug 20 15:21:32 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 20 Aug 2019 19:21:32 +0000
Subject: [docs] [issue37891] Exceptions tutorial page does not mention raise
 from
In-Reply-To: <1566285667.91.0.992762773609.issue37891@roundup.psfhosted.org>
Message-ID: <1566328892.56.0.674644574026.issue37891@roundup.psfhosted.org>


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

Please give Niel a chance to submit wording, even a post here on the tracker will be fine.  We usually defer to the person who actually encountered the issue.  

If after a week or so, there is no response, you can pick this up.  Try to be minimal with it and avoid the temptation to go gonzo.  The "from" part of exception semantics is one of its most minor and easily ignored features.  Accordingly, it should get minimal space in the tutorial and probably doesn't even warrant an example if a simple, clear sentence will suffice.

----------

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

From julien at palard.fr  Tue Aug 20 15:52:55 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 20 Aug 2019 19:52:55 +0000
Subject: [docs] Bug in documentation: 'Pythonwin' under
 'platform-specific GUI toolkits' links to the wrong place.
In-Reply-To: <MWHPR1201MB01744C4F52C6A6B9169DEE42C0A80@MWHPR1201MB0174.namprd12.prod.outlook.com>
References: <MWHPR1201MB01744C4F52C6A6B9169DEE42C0A80@MWHPR1201MB0174.namprd12.prod.outlook.com>
Message-ID: <agxvRBI5WvZInkKPlbi3kYliFNsRRw5cuFpR3scfdX4x4xZ7JqJql2QvDCsqq7ja38ZBOoTcbgp_MOb9e_we4ZwtAFlT4bETJBgFr5mPMMs=@palard.fr>

Hi Evan,

> On this page here (screenshot below)  https://docs.python.org/3/faq/gui.html#what-platform-specific-gui-toolkits-exist-for-python,
>
> ?Pythonwin? links to https://docs.python.org/3/faq/windows.html#windows-faq.
>
> I think it should link to https://github.com/mhammond/pywin32

This looks right, would you mind opening an issue on https://bugs.python.org about it and if you want you can also open a pull request on https://github.com/python/cpython?

--?
Julien Palard
https://mdk.fr


From julien at palard.fr  Tue Aug 20 16:04:36 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 20 Aug 2019 20:04:36 +0000
Subject: [docs] ISSUE I FOUND IN TUPLES
In-Reply-To: <CALg-vLHjn9eGvGuNGj2o+K5bOK8dfBzL15h__JqD04aSNutuYw@mail.gmail.com>
References: <CALg-vLHjn9eGvGuNGj2o+K5bOK8dfBzL15h__JqD04aSNutuYw@mail.gmail.com>
Message-ID: <mnaH_lo72AGRU9Klz4Slu7-736PqovJaSAHcv-Q2wULAHzLqSMD7IoP0UBJKv5Evu0MpQsOJiW4Vo2ULwkX3DvJIQyKTXekaSGim7vOL2T8=@palard.fr>

Hi Vinay,

> I noticed is a list containing single list can identify inner list as a single element of the list whereas in tuples a tuple containing single tuple is unable to identify as a single element unless a comma is specified.

Thanks for reporting!

This is known and documented, quoting the doc [1]:

> A special problem is the construction of tuples containing 0 or 1 items: the syntax has some extra quirks to accommodate these. Empty tuples are constructed by an empty pair of parentheses; a tuple with one item is constructed by following a value with a comma (it is not sufficient to enclose a single value in parentheses). Ugly, but effective. For example:

This is because parenthesis play multiple roles like describing tuples and mathematical priority:

Should:

    (1 + 1) * 2

be interpreted "twice the tuple containing the result of 1 + 1" which is (2, 2), or the number 4?

To disambiguate, the trick is to add a trailing coma:

>>> (1 + 1) * 2
4
>>> (1 + 1, ) * 2
(2, 2)

If you have a better idea, please tell :)

If you worry about it, don't, you won't use often tuples of a single element, and it's still possible to build them, so it's OK.

[1]: https://docs.python.org/3/tutorial/datastructures.html#tuples-and-sequences
--?
Julien Palard
https://mdk.fr


From julien at palard.fr  Tue Aug 20 16:10:59 2019
From: julien at palard.fr (Julien Palard)
Date: Tue, 20 Aug 2019 20:10:59 +0000
Subject: [docs] I am Sai Akshay Erupaka I found an mistake in the
 documentation in the regular expressions part
In-Reply-To: <CAPBLZWj-egKdKt2FiqEg1Z9gdKOnfXE-yqOAE-vntdGNpYjCtw@mail.gmail.com>
References: <CAPBLZWj-egKdKt2FiqEg1Z9gdKOnfXE-yqOAE-vntdGNpYjCtw@mail.gmail.com>
Message-ID: <NIxnX81CNfcWmJfrFJGS6d37mtUngx0VFVp-_6rnKUG0Bq1XibISl9hhwtjrztteLmeQ5wmU-5gyff2YCVXCgyTBbVggOO6NJTsmufqCp-c=@palard.fr>

Hi Sai,

> It says that the RE <.*?> matches only <a> but it also matches <c>

That's right (yet if you use re.match or re.search it will stop at matching only <a> so that's not wrong either).

"Fixing" it would make the sentence longer, I think in the current state it explain the point clearly, making it longer won't easily make it clearer.

If you still fill it can be enhanced, feel free to open a pull request on https://github.com/python/cpython/

Bests,
--?
Julien Palard
https://mdk.fr



From report at bugs.python.org  Wed Aug 21 06:56:07 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 21 Aug 2019 10:56:07 +0000
Subject: [docs] [issue25299] argparse: TypeError: __init__() takes at least
 4 arguments (4 given)
In-Reply-To: <1443785146.27.0.85852377889.issue25299@psf.upfronthosting.co.za>
Message-ID: <1566384967.17.0.185072771781.issue25299@roundup.psfhosted.org>


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


----------
title: TypeError: __init__() takes at least 4 arguments (4 given) -> argparse: TypeError: __init__() takes at least 4 arguments (4 given)

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

From report at bugs.python.org  Wed Aug 21 07:13:42 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 21 Aug 2019 11:13:42 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1566386022.63.0.100779469701.issue37823@roundup.psfhosted.org>


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


New changeset e0b6117e2723327d6741d0aa599408514add5b30 by Victor Stinner (Michael Anckaert) in branch 'master':
bpo-37823: Fix open() link in telnetlib doc (GH-15281)
https://github.com/python/cpython/commit/e0b6117e2723327d6741d0aa599408514add5b30


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

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

From report at bugs.python.org  Wed Aug 21 07:14:02 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 21 Aug 2019 11:14:02 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1566386042.96.0.106784816635.issue37823@roundup.psfhosted.org>


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


----------
pull_requests: +15067
pull_request: https://github.com/python/cpython/pull/15355

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

From report at bugs.python.org  Wed Aug 21 07:14:08 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 21 Aug 2019 11:14:08 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1566386048.91.0.819555548953.issue37823@roundup.psfhosted.org>


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


----------
pull_requests: +15068
pull_request: https://github.com/python/cpython/pull/15356

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

From report at bugs.python.org  Wed Aug 21 07:28:42 2019
From: report at bugs.python.org (Lawrence R. Normie)
Date: Wed, 21 Aug 2019 11:28:42 +0000
Subject: [docs] [issue37904] Suggested edit to Python Tutorial - Section 4
Message-ID: <1566386922.03.0.919785821856.issue37904@roundup.psfhosted.org>


New submission from Lawrence R. Normie <lrnormie at gmail.com>:

Suggest amending the text of the first sentence in Section 4, from:

"Besides the while statement just introduced, Python knows the usual control flow statements known from other languages, with some twists."

to:

Besides the while statement just introduced, Python follows the usual syntax fir control flow statements known from other languages, with some twists."

----------
assignee: docs at python
components: Documentation
messages: 350068
nosy: docs at python, lrnormie at gmail.com
priority: normal
severity: normal
status: open
title: Suggested edit to Python Tutorial - Section 4
type: enhancement
versions: Python 3.7

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

From report at bugs.python.org  Wed Aug 21 07:34:08 2019
From: report at bugs.python.org (Eric V. Smith)
Date: Wed, 21 Aug 2019 11:34:08 +0000
Subject: [docs] [issue37904] Suggested edit to Python Tutorial - Section 4
In-Reply-To: <1566386922.03.0.919785821856.issue37904@roundup.psfhosted.org>
Message-ID: <1566387248.13.0.634540724362.issue37904@roundup.psfhosted.org>


Eric V. Smith <eric at trueblade.com> added the comment:

I think I'd prefer "... Python uses the usual flow control statements known from other languages ..."

It's not just syntax, after all.

----------
keywords: +newcomer friendly
nosy: +eric.smith
stage:  -> needs patch

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

From report at bugs.python.org  Wed Aug 21 07:38:08 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 21 Aug 2019 11:38:08 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1566387488.17.0.0302042865612.issue37823@roundup.psfhosted.org>


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


New changeset c777dec6f47ce649f3dea88d308e36e45538fdac by Miss Islington (bot) in branch '3.8':
bpo-37823: Fix open() link in telnetlib doc (GH-15281)
https://github.com/python/cpython/commit/c777dec6f47ce649f3dea88d308e36e45538fdac


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

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

From report at bugs.python.org  Wed Aug 21 07:38:28 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 21 Aug 2019 11:38:28 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1566387508.72.0.255146585143.issue37823@roundup.psfhosted.org>


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


New changeset 72088d56247ee422d8abeef94a89be463737b982 by Miss Islington (bot) in branch '3.7':
bpo-37823: Fix open() link in telnetlib doc (GH-15281)
https://github.com/python/cpython/commit/72088d56247ee422d8abeef94a89be463737b982


----------

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

From report at bugs.python.org  Wed Aug 21 07:39:19 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 21 Aug 2019 11:39:19 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1566387559.44.0.74926079488.issue37823@roundup.psfhosted.org>


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


----------
pull_requests: +15069
pull_request: https://github.com/python/cpython/pull/15357

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

From report at bugs.python.org  Wed Aug 21 07:52:08 2019
From: report at bugs.python.org (miss-islington)
Date: Wed, 21 Aug 2019 11:52:08 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1566388328.59.0.996110245012.issue37823@roundup.psfhosted.org>


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


New changeset 98b11e1160a1749bfdb48bbf4c0dda177296b005 by Miss Islington (bot) in branch '2.7':
bpo-37823: Fix open() link in telnetlib doc (GH-15281)
https://github.com/python/cpython/commit/98b11e1160a1749bfdb48bbf4c0dda177296b005


----------

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

From report at bugs.python.org  Wed Aug 21 07:53:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 21 Aug 2019 11:53:30 +0000
Subject: [docs] [issue37823] Telnet documentation: fix the link to open()
In-Reply-To: <1565540009.68.0.907395311638.issue37823@roundup.psfhosted.org>
Message-ID: <1566388410.04.0.542658057867.issue37823@roundup.psfhosted.org>


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

Thanks Michael Anckaert, I merged your PR and backported it to 2.7, 3.7 and 3.8 branches.

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

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

From report at bugs.python.org  Wed Aug 21 08:23:23 2019
From: report at bugs.python.org (Michael Anckaert)
Date: Wed, 21 Aug 2019 12:23:23 +0000
Subject: [docs] [issue19820] docs are missing info about module attributes
In-Reply-To: <1385620941.03.0.287546381963.issue19820@psf.upfronthosting.co.za>
Message-ID: <1566390203.44.0.963413983946.issue19820@roundup.psfhosted.org>


Change by Michael Anckaert <michael.anckaert at sinax.be>:


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

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

From report at bugs.python.org  Wed Aug 21 09:08:50 2019
From: report at bugs.python.org (Carol Willing)
Date: Wed, 21 Aug 2019 13:08:50 +0000
Subject: [docs] [issue37860] Add netlify deploy preview for docs
In-Reply-To: <1565817286.53.0.142673590989.issue37860@roundup.psfhosted.org>
Message-ID: <1566392930.45.0.973491828974.issue37860@roundup.psfhosted.org>


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


New changeset 87bc3b7a0b0c41ea5da2aa137c4145f437a1c9fd by Carol Willing (Ashwin Ramaswami) in branch 'master':
bpo-37860: Add netlify deploy preview for docs (GH-15288)
https://github.com/python/cpython/commit/87bc3b7a0b0c41ea5da2aa137c4145f437a1c9fd


----------
nosy: +willingc

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

From report at bugs.python.org  Wed Aug 21 12:22:10 2019
From: report at bugs.python.org (hai shi)
Date: Wed, 21 Aug 2019 16:22:10 +0000
Subject: [docs] [issue9938] Documentation for argparse interactive use
In-Reply-To: <1285338690.84.0.283413950067.issue9938@psf.upfronthosting.co.za>
Message-ID: <1566404530.47.0.479727148242.issue9938@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


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

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

From report at bugs.python.org  Wed Aug 21 12:27:18 2019
From: report at bugs.python.org (hai shi)
Date: Wed, 21 Aug 2019 16:27:18 +0000
Subject: [docs] [issue9938] Improving interactive use of argparse
In-Reply-To: <1285338690.84.0.283413950067.issue9938@psf.upfronthosting.co.za>
Message-ID: <1566404838.43.0.003460670114.issue9938@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

It is a good idea. So I update this title and add PR 15362.

I am not sure there have a problem of xuanli's CLA or not~

----------
components:  -Documentation
nosy: +shihai1991
title: Documentation for argparse interactive use -> Improving interactive use of argparse
versions: +Python 3.9 -Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Wed Aug 21 13:04:18 2019
From: report at bugs.python.org (hai shi)
Date: Wed, 21 Aug 2019 17:04:18 +0000
Subject: [docs] [issue37775] update doc of compileall
In-Reply-To: <1565113080.48.0.890450145581.issue37775@roundup.psfhosted.org>
Message-ID: <1566407058.62.0.322762865606.issue37775@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


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

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

From report at bugs.python.org  Wed Aug 21 13:05:20 2019
From: report at bugs.python.org (hai shi)
Date: Wed, 21 Aug 2019 17:05:20 +0000
Subject: [docs] [issue37698] Update doc of PyBuffer_ToContiguous
In-Reply-To: <1564334680.0.0.401210106575.issue37698@roundup.psfhosted.org>
Message-ID: <1566407120.51.0.472885106706.issue37698@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
nosy: +pitrou

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

From report at bugs.python.org  Wed Aug 21 13:05:22 2019
From: report at bugs.python.org (hai shi)
Date: Wed, 21 Aug 2019 17:05:22 +0000
Subject: [docs] [issue37750] PyBuffer_FromContiguous not documented
In-Reply-To: <1564822618.55.0.397769114373.issue37750@roundup.psfhosted.org>
Message-ID: <1566407122.92.0.801440960938.issue37750@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
nosy: +pitrou

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

From report at bugs.python.org  Wed Aug 21 13:11:33 2019
From: report at bugs.python.org (hai shi)
Date: Wed, 21 Aug 2019 17:11:33 +0000
Subject: [docs] [issue37908] Add some examples of ArgumentParser.exit()
Message-ID: <1566407493.49.0.869927821626.issue37908@roundup.psfhosted.org>


New submission from hai shi <shihai1991 at 126.com>:

As paul said in bpo 9938:
The exit and error methods are mentioned in the 3.4 documentation, but there are no examples of modifying them.

    16.4.5.9. Exiting methods
    ArgumentParser.exit(status=0, message=None)
    ArgumentParser.error(message)

I will update the examples in this weekend.

----------
assignee: docs at python
components: Documentation
messages: 350097
nosy: docs at python, shihai1991
priority: normal
severity: normal
status: open
title: Add some examples of ArgumentParser.exit()

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

From report at bugs.python.org  Wed Aug 21 13:12:09 2019
From: report at bugs.python.org (hai shi)
Date: Wed, 21 Aug 2019 17:12:09 +0000
Subject: [docs] [issue37908] Add some examples of ArgumentParser.exit()
In-Reply-To: <1566407493.49.0.869927821626.issue37908@roundup.psfhosted.org>
Message-ID: <1566407529.39.0.234600781466.issue37908@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

issue 9938

----------

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

From report at bugs.python.org  Wed Aug 21 13:12:48 2019
From: report at bugs.python.org (hai shi)
Date: Wed, 21 Aug 2019 17:12:48 +0000
Subject: [docs] [issue37908] Add some examples of ArgumentParser.exit()
In-Reply-To: <1566407493.49.0.869927821626.issue37908@roundup.psfhosted.org>
Message-ID: <1566407568.38.0.836305684816.issue37908@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
nosy: +paul.j3

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

From report at bugs.python.org  Wed Aug 21 14:19:36 2019
From: report at bugs.python.org (sushma)
Date: Wed, 21 Aug 2019 18:19:36 +0000
Subject: [docs] [issue36858] f-string '=' debugging output needs to be
 documented
In-Reply-To: <1557347816.05.0.714667733239.issue36858@roundup.psfhosted.org>
Message-ID: <1566411576.06.0.460236804963.issue36858@roundup.psfhosted.org>


sushma <sushma.y at gmail.com> added the comment:

Hello,

I'd like to work on this and will take a look.

----------
nosy: +syadlapalli

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

From neil.millikin at gmail.com  Wed Aug 21 15:07:32 2019
From: neil.millikin at gmail.com (Neil Millikin)
Date: Wed, 21 Aug 2019 13:07:32 -0600
Subject: [docs] trivial typographic error that may lead to confusion
Message-ID: <BEDD518A-D1ED-43F5-A739-E6E8FB5FBAE2@gmail.com>

Perhaps trivial, but I belive that on page https://docs.python.org/2/library/random.html <https://docs.python.org/2/library/random.html>

	"Return the next random floating point number in the range [0.0, 1.0).?   ?  (one bracket one paren)

		  should read      "range [0.0, 1.0].?  ? (both with brackets)
		or perhaps      "range (0.0, 1.0).?  ?  (both with parens)



screenshot of online docs: 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190821/2b837fe4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PastedGraphic-6.png
Type: image/png
Size: 176105 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190821/2b837fe4/attachment-0001.png>

From report at bugs.python.org  Wed Aug 21 19:01:15 2019
From: report at bugs.python.org (Semyon)
Date: Wed, 21 Aug 2019 23:01:15 +0000
Subject: [docs] [issue37911] Minor error in PEP567 code example
Message-ID: <1566428475.33.0.0889947555242.issue37911@roundup.psfhosted.org>


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

In PEP-567 there is a code example in `contextvars.Context` section (https://www.python.org/dev/peps/pep-0567/#contextvars-context):

```
# Print all context variables and their values in 'ctx':
print(ctx.items())
```

But `ctx.items()` doesn't return a list of tuples as probably expected by this code; instead it returns a `items` object which, unlike `dict_items`, does not contain any sensible `repr` or `str`. So this print statement will output something like `<items at 0x7f7fbd91e468>`.

I think this code example should be chaned to something like `print(list(ctx.items()))`.

----------
assignee: docs at python
components: Documentation
messages: 350129
nosy: MarSoft, docs at python
priority: normal
severity: normal
status: open
title: Minor error in PEP567 code example
versions: Python 3.7

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

From report at bugs.python.org  Wed Aug 21 21:34:49 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 22 Aug 2019 01:34:49 +0000
Subject: [docs] [issue37911] Minor error in PEP567 code example
In-Reply-To: <1566428475.33.0.0889947555242.issue37911@roundup.psfhosted.org>
Message-ID: <1566437689.94.0.734330759656.issue37911@roundup.psfhosted.org>


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

PEPs have their own GitHub issue tracker though I am not sure of edits to this PEP.
 GitHub : https://github.com/python/peps/issues . This can be closed as third party.

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

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

From report at bugs.python.org  Wed Aug 21 22:41:25 2019
From: report at bugs.python.org (Kim Oldfield)
Date: Thu, 22 Aug 2019 02:41:25 +0000
Subject: [docs] [issue37862] Search doesn't find built-in functions
In-Reply-To: <1565831586.7.0.196033639625.issue37862@roundup.psfhosted.org>
Message-ID: <1566441685.51.0.757510493583.issue37862@roundup.psfhosted.org>


Kim Oldfield <python at oldfield.wattle.id.au> added the comment:

Usually the search page is the quickest way to find documentation about a module or function - quicker than navigating through a couple of levels of pages (documentation home, index, index by letter, scroll or search in page to find desired name, click on name).

Searching for builtin functions is inconsistent. Some functions (eg getattr) are found as expected in a search, while other functions (eg zip and many others) aren't found in the search results. This could easily lead someone to incorrectly concluding that the function they are search for doesn't exist in python.

I find the response of "The search page is the last thing one should use" strange. Surely as the option to search is there, and it mostly works, we should be making incremental improvements as necessary to make it better so that everyone can easily find the right parts of the python documentation.

----------

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

From report at bugs.python.org  Wed Aug 21 22:51:15 2019
From: report at bugs.python.org (Ammar Askar)
Date: Thu, 22 Aug 2019 02:51:15 +0000
Subject: [docs] [issue37862] Search doesn't find built-in functions
In-Reply-To: <1565831586.7.0.196033639625.issue37862@roundup.psfhosted.org>
Message-ID: <1566442275.27.0.685539228241.issue37862@roundup.psfhosted.org>


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

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

There is some related work done by Julien there as well: https://github.com/JulienPalard/pydocsearch

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

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

From report at bugs.python.org  Thu Aug 22 01:28:36 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 22 Aug 2019 05:28:36 +0000
Subject: [docs] [issue37862] Search doesn't find built-in functions
In-Reply-To: <1565831586.7.0.196033639625.issue37862@roundup.psfhosted.org>
Message-ID: <1566451716.12.0.139098438709.issue37862@roundup.psfhosted.org>


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

Even if click 'Library Reference', click '2. Built-in...', click name in the index at the top of the page to go to the entry I know I want to read is sometimes slower that 'click search box', enter word, hit Return, wait for results, scan results to find that entry, I prefer a consistent and dependable result.

That said, perhaps the search algorithm should start with looking words up in the builtins list, the module index, the glossary, and the index, and display those first  Index pages with definitions should get heavy weight too.  But is seems from your example that the obvious places might be downweighted instead.

As for my answer, I believe that the search once used Google, which was and still is terrible at returning results from the current doc.  For instance, just now, the 2nd return for 'Python zip' is the zip entry in chapter 2 ... for 3.3.7!  'Python zip 3.7' does return
https://docs.python.org/3/library/functions.html
as first entry. I would rather click click to get to the same place.

If Julien and Ammar can improve Search [      ] to beat that, and be consistently useful to beginners, more power to them.

----------

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

From report at bugs.python.org  Thu Aug 22 02:24:44 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 06:24:44 +0000
Subject: [docs] [issue32471] Add an UML class diagram to the collections.abc
 module documentation
In-Reply-To: <1514785654.69.0.467229070634.issue32471@psf.upfronthosting.co.za>
Message-ID: <1566455084.62.0.157544710823.issue32471@roundup.psfhosted.org>


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

See the rationale in the closed PR.  I rather liked this idea but it didn't prove to be a net win during user testing.

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

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

From songofacandy at gmail.com  Thu Aug 22 02:46:33 2019
From: songofacandy at gmail.com (Inada Naoki)
Date: Thu, 22 Aug 2019 15:46:33 +0900
Subject: [docs] trivial typographic error that may lead to confusion
In-Reply-To: <BEDD518A-D1ED-43F5-A739-E6E8FB5FBAE2@gmail.com>
References: <BEDD518A-D1ED-43F5-A739-E6E8FB5FBAE2@gmail.com>
Message-ID: <CAEfz+TyMMMQ-N2qk1bSZDfQdEFJx4jAzCer0gcYtfA3P_fqzHw@mail.gmail.com>

This is a mathematic representation.
https://en.wikipedia.org/wiki/Interval_(mathematics)

[0, 4] -- 0 ? x ? 4
(0, 4) -- 0 < x < 4
[0, 4) -- 0 ? x < 4


On Thu, Aug 22, 2019 at 5:51 AM Neil Millikin <neil.millikin at gmail.com> wrote:
>
> Perhaps trivial, but I belive that on page https://docs.python.org/2/library/random.html
>
> "Return the next random floating point number in the range [0.0, 1.0).?   ?  (one bracket one paren)
>
>   should read      "range [0.0, 1.0].?  ? (both with brackets)
> or perhaps      "range (0.0, 1.0).?  ?  (both with parens)
>
>
>
> screenshot of online docs:
>
> _______________________________________________
> docs mailing list
> docs at python.org
> https://mail.python.org/mailman/listinfo/docs



-- 
Inada Naoki  <songofacandy at gmail.com>

From report at bugs.python.org  Thu Aug 22 03:06:58 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 07:06:58 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
In-Reply-To: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>
Message-ID: <1566457618.49.0.797228844849.issue14050@roundup.psfhosted.org>


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


----------
pull_requests: +15091
pull_request: https://github.com/python/cpython/pull/15381

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

From report at bugs.python.org  Thu Aug 22 03:23:05 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 07:23:05 +0000
Subject: [docs] [issue24659] dict() built-in fails on iterators with a
 "keys" attribute
In-Reply-To: <1437209700.05.0.411435282726.issue24659@psf.upfronthosting.co.za>
Message-ID: <1566458585.81.0.0273073490611.issue24659@roundup.psfhosted.org>


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

This doesn't appear to have been an ongoing source of confusion.  Over time, the existence of the glossary entries and the collections ABCs seems to have provided the needed clarity.

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

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

From report at bugs.python.org  Thu Aug 22 05:03:27 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 09:03:27 +0000
Subject: [docs] [issue32554] random.seed(tuple) uses the randomized hash
 function and so is not reproductible
In-Reply-To: <1516007302.18.0.467229070634.issue32554@psf.upfronthosting.co.za>
Message-ID: <1566464607.23.0.809407094464.issue32554@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 22 06:05:04 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 10:05:04 +0000
Subject: [docs] [issue20727] Improved roundrobin itertools recipe
In-Reply-To: <1393051018.22.0.696460210134.issue20727@psf.upfronthosting.co.za>
Message-ID: <1566468304.71.0.322228797654.issue20727@roundup.psfhosted.org>


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

Thanks for the suggestion.  I appreciate it even though I've decided to keep the current recipe.

While he proposed recipe is really good at eliminating exhausted input sources, it is slower at its core task of yielding outputs (which is typically the important part).

The O(n) step in the current code runs at C speed and is really fast.  On my six year old machine, running :cycle(islice(nexts, num_active))" for 1,000 nexts takes only 186ns.

One other thought:  The existing recipe is also useful for showing off ways to use the itertools (which was really the principal purpose of having a recipes section).

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

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

From report at bugs.python.org  Thu Aug 22 06:17:07 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Thu, 22 Aug 2019 10:17:07 +0000
Subject: [docs] [issue37913] Document that __length_hint__ may return
 NotImplemented
Message-ID: <1566469027.85.0.30597516641.issue37913@roundup.psfhosted.org>


New submission from Jeroen Demeyer <jeroen.k.demeyer at gmail.com>:

The special method __length_hint__ can return NotImplemented. In this case, the result is as if the __length_hint__ method didn't exist at all. This behaviour is implemented and tested but not documented.

----------
assignee: docs at python
components: Documentation
messages: 350180
nosy: docs at python, jdemeyer
priority: normal
severity: normal
status: open
title: Document that __length_hint__ may return NotImplemented
type: enhancement
versions: Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Thu Aug 22 06:26:51 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Thu, 22 Aug 2019 10:26:51 +0000
Subject: [docs] [issue37913] Document that __length_hint__ may return
 NotImplemented
In-Reply-To: <1566469027.85.0.30597516641.issue37913@roundup.psfhosted.org>
Message-ID: <1566469611.37.0.60822654002.issue37913@roundup.psfhosted.org>


Change by Jeroen Demeyer <jeroen.k.demeyer at gmail.com>:


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

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

From report at bugs.python.org  Thu Aug 22 12:11:38 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 16:11:38 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
In-Reply-To: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>
Message-ID: <1566490298.2.0.58477747932.issue14050@roundup.psfhosted.org>


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


New changeset 4109263a7edce11194e301138cf66fa2d07f7ce4 by Raymond Hettinger in branch 'master':
bpo-14050: Note that not all data can be sorted (GH-15381)
https://github.com/python/cpython/commit/4109263a7edce11194e301138cf66fa2d07f7ce4


----------

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

From report at bugs.python.org  Thu Aug 22 12:11:45 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 22 Aug 2019 16:11:45 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
In-Reply-To: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>
Message-ID: <1566490305.33.0.655273577557.issue14050@roundup.psfhosted.org>


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


----------
pull_requests: +15103
pull_request: https://github.com/python/cpython/pull/15395

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

From report at bugs.python.org  Thu Aug 22 12:19:39 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 16:19:39 +0000
Subject: [docs] [issue32554] random.seed(tuple) uses the randomized hash
 function and so is not reproductible
In-Reply-To: <1516007302.18.0.467229070634.issue32554@psf.upfronthosting.co.za>
Message-ID: <1566490779.75.0.243628024499.issue32554@roundup.psfhosted.org>


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


New changeset d0cdeaab76fef8a6e5a04665df226b6659111e4e by Raymond Hettinger in branch 'master':
bpo-32554: Deprecate hashing arbitrary types in random.seed() (GH-15382)
https://github.com/python/cpython/commit/d0cdeaab76fef8a6e5a04665df226b6659111e4e


----------

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

From report at bugs.python.org  Thu Aug 22 12:20:08 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 16:20:08 +0000
Subject: [docs] [issue32554] random.seed(tuple) uses the randomized hash
 function and so is not reproductible
In-Reply-To: <1516007302.18.0.467229070634.issue32554@psf.upfronthosting.co.za>
Message-ID: <1566490808.66.0.842542101094.issue32554@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 22 12:35:30 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 16:35:30 +0000
Subject: [docs] [issue23987] docs about containers membership testing wrong
 for broken objects
In-Reply-To: <1429258165.63.0.284734084008.issue23987@psf.upfronthosting.co.za>
Message-ID: <1566491730.09.0.943475350887.issue23987@roundup.psfhosted.org>


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

It looks like the identity-implies-equality part of this has already been taken care of.   The __hash__ invariant also appears to now have extensive coverage, some in the glossary and much more in the data model section of the reference.  Cute puzzles like a __hash__ returning a random value can be left for stackoverflow.

----------
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Aug 22 12:39:59 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 16:39:59 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
In-Reply-To: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>
Message-ID: <1566491999.32.0.254590207866.issue14050@roundup.psfhosted.org>


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


New changeset cb8de91dadf15925fb95069cb190398e1d485f56 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-14050: Note that not all data can be sorted (GH-15381) (GH-15395)
https://github.com/python/cpython/commit/cb8de91dadf15925fb95069cb190398e1d485f56


----------

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

From report at bugs.python.org  Thu Aug 22 12:40:18 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 16:40:18 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
In-Reply-To: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>
Message-ID: <1566492018.22.0.241303142895.issue14050@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 22 13:29:28 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 17:29:28 +0000
Subject: [docs] [issue30550] Document order-preserving dictionary output in
 json
In-Reply-To: <1496396847.32.0.655591837652.issue30550@psf.upfronthosting.co.za>
Message-ID: <1566494968.16.0.39480619049.issue30550@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 22 14:37:15 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 18:37:15 +0000
Subject: [docs] [issue35654] Remove 'guarantee' that sorting only relies on
 __lt__ from sorting howto
In-Reply-To: <1546551341.08.0.0908752668479.issue35654@roundup.psfhosted.org>
Message-ID: <1566499035.36.0.539199703341.issue35654@roundup.psfhosted.org>


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

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

It is in fact by design :-)

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

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

From report at bugs.python.org  Thu Aug 22 18:14:47 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 22:14:47 +0000
Subject: [docs] [issue30550] Document order-preserving dictionary output in
 json
In-Reply-To: <1496396847.32.0.655591837652.issue30550@psf.upfronthosting.co.za>
Message-ID: <1566512087.51.0.985933490943.issue30550@roundup.psfhosted.org>


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


New changeset 657008ea0336ff4f275ed3f0c2b6dd2e52de2bba by Raymond Hettinger in branch 'master':
bpo-30550: Clarify JSON ordering guarantees (GH-15397)
https://github.com/python/cpython/commit/657008ea0336ff4f275ed3f0c2b6dd2e52de2bba


----------

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

From report at bugs.python.org  Thu Aug 22 18:15:49 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 22 Aug 2019 22:15:49 +0000
Subject: [docs] [issue30550] Document order-preserving dictionary output in
 json
In-Reply-To: <1496396847.32.0.655591837652.issue30550@psf.upfronthosting.co.za>
Message-ID: <1566512149.82.0.87447649549.issue30550@roundup.psfhosted.org>


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


----------
pull_requests: +15110
pull_request: https://github.com/python/cpython/pull/15403

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

From report at bugs.python.org  Thu Aug 22 18:50:37 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 22:50:37 +0000
Subject: [docs] [issue30550] Document order-preserving dictionary output in
 json
In-Reply-To: <1496396847.32.0.655591837652.issue30550@psf.upfronthosting.co.za>
Message-ID: <1566514237.46.0.407193975273.issue30550@roundup.psfhosted.org>


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


New changeset 4a40498ea96a3c606952712c7951b2ea4ab258e4 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-30550: Clarify JSON ordering guarantees (GH-15397) (GH-15403)
https://github.com/python/cpython/commit/4a40498ea96a3c606952712c7951b2ea4ab258e4


----------

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

From report at bugs.python.org  Thu Aug 22 18:51:19 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 22:51:19 +0000
Subject: [docs] [issue30550] Document order-preserving dictionary output in
 json
In-Reply-To: <1496396847.32.0.655591837652.issue30550@psf.upfronthosting.co.za>
Message-ID: <1566514279.66.0.0178202224678.issue30550@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 22 19:15:20 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 23:15:20 +0000
Subject: [docs] [issue19441] itertools.tee improve documentation
In-Reply-To: <1383087333.66.0.191656186181.issue19441@psf.upfronthosting.co.za>
Message-ID: <1566515720.62.0.2215881475.issue19441@roundup.psfhosted.org>


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

This is out of date.  The docs currently have:

''' Once :func:`tee` has made a split, the original *iterable* should not be used anywhere else; otherwise, the *iterable* could get advanced without the tee objects being informed.
'''

----------
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Thu Aug 22 19:36:26 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 23:36:26 +0000
Subject: [docs] [issue12634] Random Remarks in class documentation
In-Reply-To: <1311575810.71.0.0727071558423.issue12634@psf.upfronthosting.co.za>
Message-ID: <1566516986.79.0.717968615239.issue12634@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 22 19:37:13 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 23:37:13 +0000
Subject: [docs] [issue12634] Random Remarks in class documentation
In-Reply-To: <1311575810.71.0.0727071558423.issue12634@psf.upfronthosting.co.za>
Message-ID: <1566517033.3.0.292451215442.issue12634@roundup.psfhosted.org>


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


----------
versions: +Python 3.8, Python 3.9 -Python 2.7, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Thu Aug 22 19:39:54 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 22 Aug 2019 23:39:54 +0000
Subject: [docs] [issue27561] Warn against subclassing builtins,
 and overriding their methods
In-Reply-To: <1468848651.49.0.804648096873.issue27561@psf.upfronthosting.co.za>
Message-ID: <1566517194.11.0.634203837434.issue27561@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Aug 23 00:42:18 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 04:42:18 +0000
Subject: [docs] [issue30826] More details in reference 'Looping through a
 list in Python and modifying it'
In-Reply-To: <1498969328.51.0.74139016573.issue30826@psf.upfronthosting.co.za>
Message-ID: <1566535338.12.0.112193209416.issue30826@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Aug 23 01:15:37 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 05:15:37 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
 without explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1566537337.94.0.428041163362.issue14112@roundup.psfhosted.org>


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


----------
pull_requests: +15113
pull_request: https://github.com/python/cpython/pull/15408

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

From report at bugs.python.org  Fri Aug 23 01:38:17 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 05:38:17 +0000
Subject: [docs] [issue29330] __slots__ needs documentation
In-Reply-To: <1484865040.1.0.923136956691.issue29330@psf.upfronthosting.co.za>
Message-ID: <1566538697.9.0.504195336754.issue29330@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Aug 23 01:50:28 2019
From: report at bugs.python.org (=?utf-8?q?Miro_Hron=C4=8Dok?=)
Date: Fri, 23 Aug 2019 05:50:28 +0000
Subject: [docs] [issue37924] Embedding Python in Another Application:
 Compiling under Unix misses the --embed flag
Message-ID: <1566539428.8.0.420349967118.issue37924@roundup.psfhosted.org>


New submission from Miro Hron?ok <miro at hroncok.cz>:

Based on changes in https://docs.python.org/3.8/whatsnew/3.8.html#debug-build-uses-the-same-abi-as-release-build I belive we should document the python3.8-config --embed flag in https://docs.python.org/3.8/extending/embedding.html#compiling-and-linking-under-unix-like-systems

----------
assignee: docs at python
components: Documentation
messages: 350249
nosy: docs at python, hroncok, vstinner
priority: normal
severity: normal
status: open
title: Embedding Python in Another Application: Compiling under Unix misses the --embed flag
versions: Python 3.8, Python 3.9

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

From report at bugs.python.org  Fri Aug 23 02:24:41 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 06:24:41 +0000
Subject: [docs] [issue32621] Problem of consistency in collection.abc
 documentation
In-Reply-To: <1516631316.64.0.467229070634.issue32621@psf.upfronthosting.co.za>
Message-ID: <1566541480.98.0.608375560227.issue32621@roundup.psfhosted.org>


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

The table is correct.  See the interactive session below for confirmation.  I think the source of your confusion is that some of the more complex ABCs are able to generate some of the required methods from the ones that are listed (for example, Mapping is able to automatically create __contains__ from __getitem__, so the former is not listed as a required abstract method).


>>> Container.__abstractmethods__
frozenset({'__contains__'})
>>> Hashable.__abstractmethods__
frozenset({'__hash__'})
>>> Iterable.__abstractmethods__
frozenset({'__iter__'})
>>> Reversible.__abstractmethods__
frozenset({'__reversed__', '__iter__'})
>>> Generator.__abstractmethods__
frozenset({'send', 'throw'})
>>> Sized.__abstractmethods__
frozenset({'__len__'})
>>> Callable.__abstractmethods__
frozenset({'__call__'})
>>> Collection.__abstractmethods__
frozenset({'__iter__', '__len__', '__contains__'})
>>> Sequence.__abstractmethods__
frozenset({'__getitem__', '__len__'})
>>> MutableSequence.__abstractmethods__
frozenset({'insert', '__getitem__', '__len__', '__delitem__', '__setitem__'})
>>> ByteString.__abstractmethods__
frozenset({'__getitem__', '__len__'})
>>> Set.__abstractmethods__
frozenset({'__iter__', '__len__', '__contains__'})
>>> MutableSet.__abstractmethods__
frozenset({'add', '__len__', '__iter__', 'discard', '__contains__'})
>>> Mapping.__abstractmethods__
frozenset({'__getitem__', '__iter__', '__len__'})
>>> MutableMapping.__abstractmethods__
frozenset({'__getitem__', '__len__', '__iter__', '__delitem__', '__setitem__'})
>>> MappingView.__abstractmethods__
frozenset()
>>> ItemsView.__abstractmethods__
frozenset()
>>> KeysView.__abstractmethods__
frozenset()
>>> ValuesView.__abstractmethods__
frozenset()
>>> Awaitable.__abstractmethods__
frozenset({'__await__'})
>>> Coroutine.__abstractmethods__
frozenset({'send', 'throw', '__await__'})
>>> AsyncIterable.__abstractmethods__
frozenset({'__aiter__'})
>>> AsyncIterator.__abstractmethods__
frozenset({'__anext__'})
>>> AsyncGenerator.__abstractmethods__
frozenset({'athrow', 'asend'})

----------
resolution:  -> not a bug
stage: needs patch -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Aug 23 02:27:17 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 23 Aug 2019 06:27:17 +0000
Subject: [docs] [issue12634] Random Remarks in class documentation
In-Reply-To: <1311575810.71.0.0727071558423.issue12634@psf.upfronthosting.co.za>
Message-ID: <1566541637.11.0.1522166181.issue12634@roundup.psfhosted.org>


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


----------
pull_requests: +15114
pull_request: https://github.com/python/cpython/pull/15409

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

From report at bugs.python.org  Fri Aug 23 02:27:25 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 06:27:25 +0000
Subject: [docs] [issue12634] Random Remarks in class documentation
In-Reply-To: <1311575810.71.0.0727071558423.issue12634@psf.upfronthosting.co.za>
Message-ID: <1566541645.51.0.82031707162.issue12634@roundup.psfhosted.org>


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


New changeset 483ae0cf1dcf46f8b71c4bf32419dd138e908553 by Raymond Hettinger in branch 'master':
bpo-12634: Clarify an awkward section of the tutorial (GH-15406)
https://github.com/python/cpython/commit/483ae0cf1dcf46f8b71c4bf32419dd138e908553


----------

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

From report at bugs.python.org  Fri Aug 23 02:44:22 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 06:44:22 +0000
Subject: [docs] [issue30826] More details in reference 'Looping through a
 list in Python and modifying it'
In-Reply-To: <1498969328.51.0.74139016573.issue30826@psf.upfronthosting.co.za>
Message-ID: <1566542662.61.0.487097150251.issue30826@roundup.psfhosted.org>


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


New changeset 6fcb6cfb139ade1aac6dbee0b18ca72b18cbe0d2 by Raymond Hettinger in branch 'master':
bpo-30826: Improve control flow examples (GH-15407)
https://github.com/python/cpython/commit/6fcb6cfb139ade1aac6dbee0b18ca72b18cbe0d2


----------

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

From report at bugs.python.org  Fri Aug 23 02:44:29 2019
From: report at bugs.python.org (miss-islington)
Date: Fri, 23 Aug 2019 06:44:29 +0000
Subject: [docs] [issue30826] More details in reference 'Looping through a
 list in Python and modifying it'
In-Reply-To: <1498969328.51.0.74139016573.issue30826@psf.upfronthosting.co.za>
Message-ID: <1566542669.7.0.623516328887.issue30826@roundup.psfhosted.org>


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


----------
pull_requests: +15115
pull_request: https://github.com/python/cpython/pull/15410

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

From report at bugs.python.org  Fri Aug 23 02:45:59 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 06:45:59 +0000
Subject: [docs] [issue12634] Random Remarks in class documentation
In-Reply-To: <1311575810.71.0.0727071558423.issue12634@psf.upfronthosting.co.za>
Message-ID: <1566542759.86.0.532022645836.issue12634@roundup.psfhosted.org>


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


New changeset f6a7f5bc50f4267cfb7fe0c4ea16d5359c009cbd by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-12634: Clarify an awkward section of the tutorial (GH-15406) (GH-15409)
https://github.com/python/cpython/commit/f6a7f5bc50f4267cfb7fe0c4ea16d5359c009cbd


----------

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

From report at bugs.python.org  Fri Aug 23 02:46:25 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 06:46:25 +0000
Subject: [docs] [issue12634] Random Remarks in class documentation
In-Reply-To: <1311575810.71.0.0727071558423.issue12634@psf.upfronthosting.co.za>
Message-ID: <1566542785.54.0.670766565739.issue12634@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Aug 23 02:52:18 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 06:52:18 +0000
Subject: [docs] [issue30826] More details in reference 'Looping through a
 list in Python and modifying it'
In-Reply-To: <1498969328.51.0.74139016573.issue30826@psf.upfronthosting.co.za>
Message-ID: <1566543138.02.0.0106079497743.issue30826@roundup.psfhosted.org>


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


New changeset b6341e676af2f58f3ad9b51a0d2fb7db5a3428e3 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-30826: Improve control flow examples (GH-15407) (GH-15410)
https://github.com/python/cpython/commit/b6341e676af2f58f3ad9b51a0d2fb7db5a3428e3


----------

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

From report at bugs.python.org  Fri Aug 23 02:52:47 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 06:52:47 +0000
Subject: [docs] [issue30826] More details in reference 'Looping through a
 list in Python and modifying it'
In-Reply-To: <1498969328.51.0.74139016573.issue30826@psf.upfronthosting.co.za>
Message-ID: <1566543167.43.0.790082578522.issue30826@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Fri Aug 23 02:59:20 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 06:59:20 +0000
Subject: [docs] [issue37454] Clarify docs for math.log1p()
In-Reply-To: <1561933178.32.0.315765765879.issue37454@roundup.psfhosted.org>
Message-ID: <1566543560.58.0.891336630238.issue37454@roundup.psfhosted.org>


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

Sometimes you guys make me feel dumb as a rock.  Sorry for the distraction.

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

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

From report at bugs.python.org  Fri Aug 23 03:36:47 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 07:36:47 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
 without explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1566545807.27.0.53149457403.issue14112@roundup.psfhosted.org>


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

How about we just like "shallow copy" to the copy module docs.  That way, a person can follow-up with more detail if they're interested, yet still can read-on without interruption if they choose (this entry occurs *very* early in the tutorial).

----------

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

From report at bugs.python.org  Fri Aug 23 03:47:11 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 23 Aug 2019 07:47:11 +0000
Subject: [docs] [issue33830] Error in the output of one example in the
 httplib docs
In-Reply-To: <1528713903.44.0.592728768989.issue33830@psf.upfronthosting.co.za>
Message-ID: <1566546431.01.0.268830655258.issue33830@roundup.psfhosted.org>


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

Closing this since PRs have been merged. Thanks Aifu LIU for the report.

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

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

From malik.a.rumi at gmail.com  Thu Aug 22 16:08:05 2019
From: malik.a.rumi at gmail.com (Malik Rumi)
Date: Thu, 22 Aug 2019 15:08:05 -0500
Subject: [docs] Inadequate documentation on re.sub()
Message-ID: <CAKd6oBzaNqKmbY4Rrv+C=a8yn1dQZowOx5HG9vBC4Ztt6BsMWw@mail.gmail.com>

1. I am aware of issues 34304 and 28450. I am writing because I think those
fixes are inadequate. This is my proposed language change to
https://docs.python.org/3/library/re.html#re.sub

re.sub(pattern, repl, string, count=0, flags=0)
Return the string obtained by replacing the leftmost non-overlapping
occurrences of pattern in string by the replacement repl. If the pattern
isn?t found, string is returned unchanged. repl can be a string or a
function; if it is a string, any backslash escapes in it are processed. This
includes common re forms such as "\d". It also means the raw string prefix
"r'" will *not* work the way you might expect. ***If you want to replace %d
with literal \d, you need to repeat the backslash 4 times:

    pattern = re.sub('%d', '\\\\d+', pattern)

or use a raw string literal and repeat the backslash 2 times:

    pattern = re.sub('%d', r'\\d+', pattern)***

That is, \n is converted to a single newline character ...'*
################################################
I have always been told that '\n' was **already** a single character:
        >>> s = "How many chars in \n?"
        >>> len(s)
        20
        >>> s2 = "How many chars in n?"
        >>> len(s2)
        20
So this sentence means nothing to me.
################################################

Unknown escapes of ASCII letters are reserved for future use and treated as
errors...

###############################################
I would never in a *million* years have guessed that '\d' was an "unknown
escape". It is far too fundamental to regex for me to conceive of it that
way. Why didn't you tell us what the right way to do it is? If I had not
found  https://bugs.python.org/issue34304#msg322854 I would STILL not know
how to fix this problem. I am confident I am not the only one.


***Source of some of the new language:
https://bugs.python.org/issue34304#msg322854***

I am not able to log in to the bug tracker. I don't know why. I tried
posting about it as an issue on github, but I don't see it now. Maybe it
has to be moderated?




*?None of you has faith until he loves for his brother or his neighbor what
he loves for himself.?*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190822/3e2690e1/attachment-0001.html>

From report at bugs.python.org  Fri Aug 23 11:08:15 2019
From: report at bugs.python.org (Tim Peters)
Date: Fri, 23 Aug 2019 15:08:15 +0000
Subject: [docs] [issue37454] Clarify docs for math.log1p()
In-Reply-To: <1561933178.32.0.315765765879.issue37454@roundup.psfhosted.org>
Message-ID: <1566572895.77.0.918786510339.issue37454@roundup.psfhosted.org>


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

> Sometimes you guys make me feel dumb as a rock.

I expect we all do that favor for each other at times ;-)

----------

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

From report at bugs.python.org  Fri Aug 23 13:55:34 2019
From: report at bugs.python.org (hai shi)
Date: Fri, 23 Aug 2019 17:55:34 +0000
Subject: [docs] [issue9938] Add optional kwargs to argparse
In-Reply-To: <1285338690.84.0.283413950067.issue9938@psf.upfronthosting.co.za>
Message-ID: <1566582934.88.0.91877274793.issue9938@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
title: Improving interactive use of argparse -> Add optional kwargs to argparse

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

From report at bugs.python.org  Fri Aug 23 14:01:44 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 23 Aug 2019 18:01:44 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
 without explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1566583304.41.0.0751347685525.issue14112@roundup.psfhosted.org>


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

With /like/link/ I agree.

----------

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

From report at bugs.python.org  Fri Aug 23 17:49:06 2019
From: report at bugs.python.org (Kyle Stanley)
Date: Fri, 23 Aug 2019 21:49:06 +0000
Subject: [docs] [issue37934] Docs: Clarify NotImplemented use cases
Message-ID: <1566596946.3.0.57144717386.issue37934@roundup.psfhosted.org>


New submission from Kyle Stanley <aeros167 at gmail.com>:

In the documentation for the NotImplemented constant (https://docs.python.org/3/library/constants.html#NotImplemented), the only use case mentioned is for binary special methods, (such as object.__eq__(other)). However, based on a conversation in a recent PR (https://github.com/python/cpython/pull/15327#discussion_r316561140), there seems be several other use cases as well.  It's quite useful to utilize when it's desired to express that a particular operation is not supported, without raising an error.

Expanding upon the use cases will provide readers an idea of other cases in which the constant could be useful. Also, the current wording could potentially come across as implying that the _only_ use case for the constant is for binary special methods, and as far as I'm aware, that is not the case.

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 350333
nosy: aeros167, docs at python, eric.araujo, ezio.melotti, mdk, willingc
priority: normal
severity: normal
stage: needs patch
status: open
title: Docs: Clarify NotImplemented use cases
type: enhancement
versions: Python 3.9

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

From report at bugs.python.org  Fri Aug 23 17:58:33 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 21:58:33 +0000
Subject: [docs] [issue22001] containers "same" does not always mean "__eq__".
In-Reply-To: <1405625961.78.0.30088981548.issue22001@psf.upfronthosting.co.za>
Message-ID: <1566597513.84.0.703667838651.issue22001@roundup.psfhosted.org>


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


----------
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Fri Aug 23 18:01:14 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 23 Aug 2019 22:01:14 +0000
Subject: [docs] [issue29352] provide the authorative source for s[i:j]
 negative slice indices (<-len(s)) behavior for standard sequences
In-Reply-To: <1485190156.24.0.631194950251.issue29352@psf.upfronthosting.co.za>
Message-ID: <1566597674.11.0.65546636326.issue29352@roundup.psfhosted.org>


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


----------
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Aug 24 02:27:42 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 24 Aug 2019 06:27:42 +0000
Subject: [docs] [issue32118] Doc for comparison of sequences with
 non-orderable elements
In-Reply-To: <1511411221.22.0.213398074469.issue32118@psf.upfronthosting.co.za>
Message-ID: <1566628062.14.0.114377628539.issue32118@roundup.psfhosted.org>


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


----------
pull_requests: +15141
pull_request: https://github.com/python/cpython/pull/15450

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

From report at bugs.python.org  Sat Aug 24 04:56:28 2019
From: report at bugs.python.org (Jeroen Demeyer)
Date: Sat, 24 Aug 2019 08:56:28 +0000
Subject: [docs] [issue37934] Docs: Clarify NotImplemented use cases
In-Reply-To: <1566596946.3.0.57144717386.issue37934@roundup.psfhosted.org>
Message-ID: <1566636988.14.0.648219000348.issue37934@roundup.psfhosted.org>


Change by Jeroen Demeyer <jeroen.k.demeyer at gmail.com>:


----------
nosy: +jdemeyer

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

From report at bugs.python.org  Sat Aug 24 06:00:35 2019
From: report at bugs.python.org (Ram Rachum)
Date: Sat, 24 Aug 2019 10:00:35 +0000
Subject: [docs] [issue37937] Mention ``frame.f_trace`` in
 :func:`sys.settrace` docs.
Message-ID: <1566640835.52.0.579357659417.issue37937@roundup.psfhosted.org>


Change by Ram Rachum <ram at rachum.com>:


----------
assignee: docs at python
components: Documentation
nosy: cool-RR, docs at python
priority: normal
pull_requests: 15149
severity: normal
status: open
title: Mention ``frame.f_trace`` in :func:`sys.settrace` docs.
type: enhancement
versions: Python 3.9

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

From report at bugs.python.org  Sat Aug 24 06:11:29 2019
From: report at bugs.python.org (hai shi)
Date: Sat, 24 Aug 2019 10:11:29 +0000
Subject: [docs] [issue37908] Add some examples of ArgumentParser.exit()
In-Reply-To: <1566407493.49.0.869927821626.issue37908@roundup.psfhosted.org>
Message-ID: <1566641489.47.0.757869411391.issue37908@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


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

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

From report at bugs.python.org  Sat Aug 24 06:17:18 2019
From: report at bugs.python.org (hai shi)
Date: Sat, 24 Aug 2019 10:17:18 +0000
Subject: [docs] [issue37908] Add some examples of ArgumentParser.exit()
In-Reply-To: <1566407493.49.0.869927821626.issue37908@roundup.psfhosted.org>
Message-ID: <1566641838.0.0.563786773757.issue37908@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

Adding an example of ArgumentParser.exit(), because some user would like cathing errors manually or consider exit progress or not when an error occurs.

I have not add example of ArgumentParser.error(), because i can not think some user scenarios:(

----------

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

From report at bugs.python.org  Sat Aug 24 06:17:37 2019
From: report at bugs.python.org (hai shi)
Date: Sat, 24 Aug 2019 10:17:37 +0000
Subject: [docs] [issue37908] Add an example of ArgumentParser.exit()
In-Reply-To: <1566407493.49.0.869927821626.issue37908@roundup.psfhosted.org>
Message-ID: <1566641857.22.0.843266207839.issue37908@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
title: Add some examples of ArgumentParser.exit() -> Add an example of ArgumentParser.exit()
type:  -> resource usage

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

From report at bugs.python.org  Sat Aug 24 06:22:52 2019
From: report at bugs.python.org (hai shi)
Date: Sat, 24 Aug 2019 10:22:52 +0000
Subject: [docs] [issue37908] Add an example of ArgumentParser.exit()
In-Reply-To: <1566407493.49.0.869927821626.issue37908@roundup.psfhosted.org>
Message-ID: <1566642172.93.0.430039639661.issue37908@roundup.psfhosted.org>


Change by hai shi <shihai1991 at 126.com>:


----------
nosy: +bethard

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

From report at bugs.python.org  Sat Aug 24 06:29:35 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 24 Aug 2019 10:29:35 +0000
Subject: [docs] [issue29535] datetime hash is deterministic in some cases
In-Reply-To: <1486826213.38.0.893503150194.issue29535@psf.upfronthosting.co.za>
Message-ID: <1566642575.19.0.361241218255.issue29535@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sat Aug 24 13:42:52 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 24 Aug 2019 17:42:52 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
 without explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1566668572.14.0.982144647758.issue14112@roundup.psfhosted.org>


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


----------
pull_requests: +15157
pull_request: https://github.com/python/cpython/pull/15465

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

From report at bugs.python.org  Sat Aug 24 13:43:58 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 24 Aug 2019 17:43:58 +0000
Subject: [docs] [issue32118] Doc for comparison of sequences with
 non-orderable elements
In-Reply-To: <1511411221.22.0.213398074469.issue32118@psf.upfronthosting.co.za>
Message-ID: <1566668637.99.0.420916595432.issue32118@roundup.psfhosted.org>


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


New changeset edd21129dd304e178ca8be82ba689488dfb58276 by Raymond Hettinger in branch 'master':
bpo-32118:  Simplify docs for sequence comparison (GH-15450)
https://github.com/python/cpython/commit/edd21129dd304e178ca8be82ba689488dfb58276


----------

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

From report at bugs.python.org  Sat Aug 24 13:44:05 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 24 Aug 2019 17:44:05 +0000
Subject: [docs] [issue32118] Doc for comparison of sequences with
 non-orderable elements
In-Reply-To: <1511411221.22.0.213398074469.issue32118@psf.upfronthosting.co.za>
Message-ID: <1566668645.33.0.170316324736.issue32118@roundup.psfhosted.org>


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


----------
pull_requests: +15158
pull_request: https://github.com/python/cpython/pull/15466

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

From report at bugs.python.org  Sat Aug 24 13:53:11 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 24 Aug 2019 17:53:11 +0000
Subject: [docs] [issue32118] Doc for comparison of sequences with
 non-orderable elements
In-Reply-To: <1511411221.22.0.213398074469.issue32118@psf.upfronthosting.co.za>
Message-ID: <1566669191.89.0.729163034847.issue32118@roundup.psfhosted.org>


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


New changeset 0ad85681de639792751ea53ec964d87d4ad45d71 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-32118:  Simplify docs for sequence comparison (GH-15450) (#15466)
https://github.com/python/cpython/commit/0ad85681de639792751ea53ec964d87d4ad45d71


----------

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

From report at bugs.python.org  Sat Aug 24 13:53:33 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 24 Aug 2019 17:53:33 +0000
Subject: [docs] [issue32118] Doc for comparison of sequences with
 non-orderable elements
In-Reply-To: <1511411221.22.0.213398074469.issue32118@psf.upfronthosting.co.za>
Message-ID: <1566669213.81.0.927757936869.issue32118@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sat Aug 24 14:15:47 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 24 Aug 2019 18:15:47 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
 without explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1566670547.23.0.301461224206.issue14112@roundup.psfhosted.org>


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


New changeset 69ee87e99cfe0b79389cffa92d126af868baf353 by Raymond Hettinger in branch 'master':
bpo-14112: Allow beginners to explore shallowness in greater depth ;-) (GH-15465)
https://github.com/python/cpython/commit/69ee87e99cfe0b79389cffa92d126af868baf353


----------

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

From report at bugs.python.org  Sat Aug 24 14:15:55 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 24 Aug 2019 18:15:55 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
 without explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1566670555.07.0.298544934307.issue14112@roundup.psfhosted.org>


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


----------
pull_requests: +15160
pull_request: https://github.com/python/cpython/pull/15469

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

From report at bugs.python.org  Sat Aug 24 14:33:21 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 24 Aug 2019 18:33:21 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
 without explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1566671601.21.0.695706362818.issue14112@roundup.psfhosted.org>


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


New changeset a8424940b4873791fc178a9f19a7bf1779a6cf42 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-14112: Allow beginners to explore shallowness in greater depth ;-) (GH-15465) (GH-15469)
https://github.com/python/cpython/commit/a8424940b4873791fc178a9f19a7bf1779a6cf42


----------

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

From report at bugs.python.org  Sat Aug 24 14:33:45 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 24 Aug 2019 18:33:45 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
 without explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1566671625.89.0.0417699615124.issue14112@roundup.psfhosted.org>


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

Thanks Terry.

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

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

From report at bugs.python.org  Sat Aug 24 19:19:32 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sat, 24 Aug 2019 23:19:32 +0000
Subject: [docs] [issue15542] Documentation incorrectly suggests __init__
 called after direct __new__ call
In-Reply-To: <1343946223.73.0.562621858875.issue15542@psf.upfronthosting.co.za>
Message-ID: <1566688772.97.0.39574257271.issue15542@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sat Aug 24 19:22:15 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sat, 24 Aug 2019 23:22:15 +0000
Subject: [docs] [issue15542] Documentation incorrectly suggests __init__
 called after direct __new__ call
In-Reply-To: <1343946223.73.0.562621858875.issue15542@psf.upfronthosting.co.za>
Message-ID: <1566688935.02.0.452691432509.issue15542@roundup.psfhosted.org>


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

Since this has taken long on the tracker, I just opened a PR with proposed changes from Aaron.

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

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

From report at bugs.python.org  Sat Aug 24 20:50:57 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 25 Aug 2019 00:50:57 +0000
Subject: [docs] [issue23061] Update pep8 to specify explicitly 'module
 level' imports at top of file
In-Reply-To: <1418703864.09.0.281927050653.issue23061@psf.upfronthosting.co.za>
Message-ID: <1566694257.01.0.328455940165.issue23061@roundup.psfhosted.org>


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

Since this is a PEP related issue, it should be moved to the PEP Github repository here : https://github.com/python/peps . If it still exists.

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

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

From report at bugs.python.org  Sat Aug 24 21:00:21 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 25 Aug 2019 01:00:21 +0000
Subject: [docs] [issue13341] Incorrect documentation for "u" PyArg_Parse
 format unit
In-Reply-To: <1320412814.48.0.657162308895.issue13341@psf.upfronthosting.co.za>
Message-ID: <1566694821.2.0.137968728482.issue13341@roundup.psfhosted.org>


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

This is has taken years but am curious, are we allowed to patch Python 2 given its EOL is almost due.

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

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

From report at bugs.python.org  Sat Aug 24 21:53:40 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 25 Aug 2019 01:53:40 +0000
Subject: [docs] [issue20806] os.times document points to wrong section of
 non-Linux manual
In-Reply-To: <1393590805.13.0.860460942185.issue20806@psf.upfronthosting.co.za>
Message-ID: <1566698020.31.0.210933454105.issue20806@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Sat Aug 24 21:57:05 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 25 Aug 2019 01:57:05 +0000
Subject: [docs] [issue20806] os.times document points to wrong section of
 non-Linux manual
In-Reply-To: <1393590805.13.0.860460942185.issue20806@psf.upfronthosting.co.za>
Message-ID: <1566698225.59.0.0905885978296.issue20806@roundup.psfhosted.org>


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

I opened a PR for this. @david please review.

----------
nosy: +nanjekyejoannah
stage: patch review -> 

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

From report at bugs.python.org  Sat Aug 24 22:21:52 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 25 Aug 2019 02:21:52 +0000
Subject: [docs] [issue23061] Update pep8 to specify explicitly 'module
 level' imports at top of file
In-Reply-To: <1418703864.09.0.281927050653.issue23061@psf.upfronthosting.co.za>
Message-ID: <1566699712.46.0.221204553363.issue23061@roundup.psfhosted.org>


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

At least some idlelib imports are delayed to avoid circular import errors, as described by Nick.

The patch adds 'Module level' before 'imports'.
Pro: techinically correct as only module level imports can be put at the top.
Com: might be seen as giving too much license to putting imports elsewhere.

Raymond, what do you think?  If you are not 'pro' enough to make the change, I think we should close.

----------

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

From report at bugs.python.org  Sat Aug 24 22:39:39 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 25 Aug 2019 02:39:39 +0000
Subject: [docs] [issue23061] Update pep8 to specify explicitly 'module
 level' imports at top of file
In-Reply-To: <1418703864.09.0.281927050653.issue23061@psf.upfronthosting.co.za>
Message-ID: <1566700779.25.0.822189872936.issue23061@roundup.psfhosted.org>


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

I concur that this should be closed.

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

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

From report at bugs.python.org  Sun Aug 25 00:42:15 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 25 Aug 2019 04:42:15 +0000
Subject: [docs] [issue15542] Documentation incorrectly suggests __init__
 called after direct __new__ call
In-Reply-To: <1343946223.73.0.562621858875.issue15542@psf.upfronthosting.co.za>
Message-ID: <1566708135.27.0.414976642812.issue15542@roundup.psfhosted.org>


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

FWIW, the underlying code for this in Objects/typeobject.c::type_new().

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

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

From report at bugs.python.org  Sun Aug 25 03:00:53 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Sun, 25 Aug 2019 07:00:53 +0000
Subject: [docs] [issue23423] XPath Support in ElementTree doc omission
In-Reply-To: <1423510779.4.0.551912157105.issue23423@psf.upfronthosting.co.za>
Message-ID: <1566716453.78.0.400505339299.issue23423@roundup.psfhosted.org>


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


----------
nosy: +scoder

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

From report at bugs.python.org  Sun Aug 25 03:45:59 2019
From: report at bugs.python.org (Stefan Behnel)
Date: Sun, 25 Aug 2019 07:45:59 +0000
Subject: [docs] [issue23423] XPath Support in ElementTree doc omission
In-Reply-To: <1423510779.4.0.551912157105.issue23423@psf.upfronthosting.co.za>
Message-ID: <1566719159.15.0.718334381997.issue23423@roundup.psfhosted.org>


Stefan Behnel <stefan_ml at behnel.de> added the comment:

Already fixed in later versions of the documentation:
https://docs.python.org/3/library/xml.etree.elementtree.html#supported-xpath-syntax

Note that Py3.4 is no longer maintained.

----------
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sun Aug 25 05:31:37 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 25 Aug 2019 09:31:37 +0000
Subject: [docs] [issue20806] os.times document points to wrong section of
 non-Linux manual
In-Reply-To: <1393590805.13.0.860460942185.issue20806@psf.upfronthosting.co.za>
Message-ID: <1566725497.46.0.245992223311.issue20806@roundup.psfhosted.org>


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

Section 3p is OS specific (Debian and derivatives). `man 3 times` works as well.

But the manpages-posix-dev is not installed by default, so changing this will add a regression on Linux.

I thank that it would be better to add both references, times(2) and times(3). And we can also add a link to MSDN.

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

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

From report at bugs.python.org  Sun Aug 25 07:17:35 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Sun, 25 Aug 2019 11:17:35 +0000
Subject: [docs] [issue20806] os.times document points to wrong section of
 non-Linux manual
In-Reply-To: <1393590805.13.0.860460942185.issue20806@psf.upfronthosting.co.za>
Message-ID: <1566731855.93.0.193962737852.issue20806@roundup.psfhosted.org>


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

Serhiy,

This sounds good.

I will update the PR.

----------

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

From report at bugs.python.org  Sun Aug 25 19:53:51 2019
From: report at bugs.python.org (Eryk Sun)
Date: Sun, 25 Aug 2019 23:53:51 +0000
Subject: [docs] [issue20806] os.times document points to wrong section of
 non-Linux manual
In-Reply-To: <1393590805.13.0.860460942185.issue20806@psf.upfronthosting.co.za>
Message-ID: <1566777231.85.0.772319743886.issue20806@roundup.psfhosted.org>


Eryk Sun <eryksun at gmail.com> added the comment:

The function's doc string also needs to be updated to use the correct field names: "user", "system", "children_user", "children_system", and "elapsed".

> And we can also add a link to MSDN.

os.times calls GetProcessTimes [1]. The user and kernel process times are incremented in clock ticks, i.e. in integer multiples of the system clock interrupt time. QueryUnbiasedInterruptTime [2] could thus be used for the value of `elapsed`. 

(Windows doesn't implement a process tree for the children_user and children_system values. It has jobs, which are similar to Linux control groups, but jobs aren't applicable here. POSIX doesn't have anything like Windows jobs or Linux cgroups.)

[1] https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-getprocesstimes
[2] https://docs.microsoft.com/en-us/windows/win32/api/realtimeapiset/nf-realtimeapiset-queryunbiasedinterrupttime

----------
nosy: +eryksun

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

From report at bugs.python.org  Sun Aug 25 23:47:02 2019
From: report at bugs.python.org (=?utf-8?b?VmVkcmFuIMSMYcSNacSH?=)
Date: Mon, 26 Aug 2019 03:47:02 +0000
Subject: [docs] [issue37934] Docs: Clarify NotImplemented use cases
In-Reply-To: <1566596946.3.0.57144717386.issue37934@roundup.psfhosted.org>
Message-ID: <1566791222.92.0.541603623165.issue37934@roundup.psfhosted.org>


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

Well, it is the _intended_ use of NotImplemented. Of course you can use it whenever you want, just as you can use Ellipsis whenever you want. But I don't think docs should encourage that.

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

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

From report at bugs.python.org  Mon Aug 26 00:26:49 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 26 Aug 2019 04:26:49 +0000
Subject: [docs] [issue37934] Docs: Clarify NotImplemented use cases
In-Reply-To: <1566596946.3.0.57144717386.issue37934@roundup.psfhosted.org>
Message-ID: <1566793609.56.0.783170218578.issue37934@roundup.psfhosted.org>


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

It is not the purpose of the docs to list use cases.  Mostly we say what something does or how it is defined.  As Vedran says, how people use it is their own business.

Also, please be careful expanded the docs.  They quickly become a promise.  Per Doc/reference/introduction.rst, "It is dangerous to add too many implementation details to a language reference document --- the implementation may change, and other implementations of the
same language may work differently."

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

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

From report at bugs.python.org  Mon Aug 26 02:53:15 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 26 Aug 2019 06:53:15 +0000
Subject: [docs] [issue15542] Documentation incorrectly suggests __init__
 called after direct __new__ call
In-Reply-To: <1343946223.73.0.562621858875.issue15542@psf.upfronthosting.co.za>
Message-ID: <1566802395.1.0.794461454243.issue15542@roundup.psfhosted.org>


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


New changeset 6b16d938d6d1ccb443815e20e8812deed274dc09 by Raymond Hettinger (Joannah Nanjekye) in branch 'master':
bpo-15542: Documentation incorrectly suggests __init__ called after direct  __new__ call (GH-15478)
https://github.com/python/cpython/commit/6b16d938d6d1ccb443815e20e8812deed274dc09


----------

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

From report at bugs.python.org  Mon Aug 26 02:53:23 2019
From: report at bugs.python.org (miss-islington)
Date: Mon, 26 Aug 2019 06:53:23 +0000
Subject: [docs] [issue15542] Documentation incorrectly suggests __init__
 called after direct __new__ call
In-Reply-To: <1343946223.73.0.562621858875.issue15542@psf.upfronthosting.co.za>
Message-ID: <1566802403.25.0.494027200267.issue15542@roundup.psfhosted.org>


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


----------
pull_requests: +15192
pull_request: https://github.com/python/cpython/pull/15506

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

From report at bugs.python.org  Mon Aug 26 03:19:23 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 26 Aug 2019 07:19:23 +0000
Subject: [docs] [issue15542] Documentation incorrectly suggests __init__
 called after direct __new__ call
In-Reply-To: <1343946223.73.0.562621858875.issue15542@psf.upfronthosting.co.za>
Message-ID: <1566803963.46.0.322588266579.issue15542@roundup.psfhosted.org>


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


New changeset c841fb9e065c393bba5d5505238f7e286f1dcfc6 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-15542: Documentation incorrectly suggests __init__ called after direct  __new__ call (GH-15478) (GH-15506)
https://github.com/python/cpython/commit/c841fb9e065c393bba5d5505238f7e286f1dcfc6


----------

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

From report at bugs.python.org  Mon Aug 26 03:20:23 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 26 Aug 2019 07:20:23 +0000
Subject: [docs] [issue15542] Documentation incorrectly suggests __init__
 called after direct __new__ call
In-Reply-To: <1343946223.73.0.562621858875.issue15542@psf.upfronthosting.co.za>
Message-ID: <1566804023.96.0.693138726908.issue15542@roundup.psfhosted.org>


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

Thanks everyone.

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

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

From report at bugs.python.org  Mon Aug 26 06:24:17 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Mon, 26 Aug 2019 10:24:17 +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: <1566815057.74.0.193291669669.issue30076@roundup.psfhosted.org>


Change by Zackery Spytz <zspytz at gmail.com>:


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

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

From report at bugs.python.org  Mon Aug 26 06:26:10 2019
From: report at bugs.python.org (Zackery Spytz)
Date: Mon, 26 Aug 2019 10:26:10 +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: <1566815170.81.0.0811789259518.issue30076@roundup.psfhosted.org>


Zackery Spytz <zspytz at gmail.com> added the comment:

I have created a pull request for this issue. Please take a look.

----------
nosy: +ZackerySpytz

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

From report at bugs.python.org  Mon Aug 26 08:17:39 2019
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 26 Aug 2019 12:17:39 +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: <1566821859.81.0.389321365795.issue30076@roundup.psfhosted.org>


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


----------
versions: +Python 3.9 -Python 3.6, Python 3.7, Python 3.8

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

From report at bugs.python.org  Mon Aug 26 11:11:48 2019
From: report at bugs.python.org (Paulo Henrique Silva)
Date: Mon, 26 Aug 2019 15:11:48 +0000
Subject: [docs] [issue37955] mock.patch incorrect reference to Mock
Message-ID: <1566832308.08.0.460509709565.issue37955@roundup.psfhosted.org>


New submission from Paulo Henrique Silva <ph.silva at gmail.com>:

When explaining the usage of keyword arguments on mock.patch:

```
patch() takes arbitrary keyword arguments. These will be passed to the Mock (or new_callable) on construction.
```

default new_callable is MagicMock and it should be mentioned here instead of Mock (even tough MagickMock inherits from it).

----------
assignee: docs at python
components: Documentation
messages: 350537
nosy: docs at python, phsilva
priority: normal
severity: normal
status: open
title: mock.patch incorrect reference to Mock
versions: Python 3.9

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

From report at bugs.python.org  Mon Aug 26 11:24:56 2019
From: report at bugs.python.org (Paulo Henrique Silva)
Date: Mon, 26 Aug 2019 15:24:56 +0000
Subject: [docs] [issue37955] mock.patch incorrect reference to Mock
In-Reply-To: <1566832308.08.0.460509709565.issue37955@roundup.psfhosted.org>
Message-ID: <1566833096.02.0.716666869545.issue37955@roundup.psfhosted.org>


Change by Paulo Henrique Silva <ph.silva at gmail.com>:


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

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

From report at bugs.python.org  Mon Aug 26 18:05:01 2019
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 26 Aug 2019 22:05:01 +0000
Subject: [docs] [issue13341] Incorrect documentation for "u" PyArg_Parse
 format unit
In-Reply-To: <1320412814.48.0.657162308895.issue13341@psf.upfronthosting.co.za>
Message-ID: <1566857101.72.0.711636586521.issue13341@roundup.psfhosted.org>


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

I don't think that it's still worth it to update Python 2 documentation at this point. I suggest to focus on enhancement of the Python 3 documentation instead.

----------

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

From floworld at web.de  Tue Aug 27 01:45:03 2019
From: floworld at web.de (Florian Ernst)
Date: Tue, 27 Aug 2019 07:45:03 +0200
Subject: [docs] Wrong roman numeral
Message-ID: <trinity-985fe5eb-4c47-48e3-ba77-87204f9236f4-1566884703430@3c-app-webde-bs62>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190827/72928fc2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2019-08-26 12_42_05-Unicode HOWTO ? Python 3.7.4 documentation.png
Type: image/png
Size: 10636 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190827/72928fc2/attachment.png>

From report at bugs.python.org  Wed Aug 28 12:26:39 2019
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 28 Aug 2019 16:26:39 +0000
Subject: [docs] [issue37970] urllib.parse docstrings incomplete
Message-ID: <1567009599.74.0.471882594509.issue37970@roundup.psfhosted.org>


New submission from Zachary Ware <zachary.ware at gmail.com>:

For example, urlsplit:

>>> from urllib.parse import urlsplit
>>> help(urlsplit)
Help on function urlsplit in module urllib.parse:

urlsplit(url, scheme='', allow_fragments=True)
    Parse a URL into 5 components:
    <scheme>://<netloc>/<path>?<query>#<fragment>
    Return a 5-tuple: (scheme, netloc, path, query, fragment).
    Note that we don't break the components up in smaller bits
    (e.g. netloc is a single string) and we don't expand % escapes.


The current docstring does not describe the `scheme` or `allow_fragments` arguments.  Also, the note about not splitting netloc is misleading; the components of netloc (username, password, hostname, and port) are available as extra attributes of the returned SplitResult.

urlparse has similar issues; other functions could stand to be checked.

----------
assignee: docs at python
components: Documentation, Library (Lib)
keywords: newcomer friendly
messages: 350668
nosy: docs at python, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title: urllib.parse docstrings incomplete
versions: Python 3.7, Python 3.8, Python 3.9

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

From report at bugs.python.org  Wed Aug 28 12:32:48 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Wed, 28 Aug 2019 16:32:48 +0000
Subject: [docs] [issue37878] Sub-Interpreters : Document
 PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1567009968.62.0.411249273487.issue37878@roundup.psfhosted.org>


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

I updated the PR to make the function internal.

----------

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

From report at bugs.python.org  Wed Aug 28 13:13:35 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Wed, 28 Aug 2019 17:13:35 +0000
Subject: [docs] [issue20806] os.times document points to wrong section of
 non-Linux manual
In-Reply-To: <1393590805.13.0.860460942185.issue20806@psf.upfronthosting.co.za>
Message-ID: <1567012415.85.0.0534137836226.issue20806@roundup.psfhosted.org>


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

I updated the PR to reference times(2) and times(3) along with an MSDN link.

----------

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

From report at bugs.python.org  Wed Aug 28 13:56:08 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 28 Aug 2019 17:56:08 +0000
Subject: [docs] [issue23674] super() documentation isn't very clear
In-Reply-To: <1426448451.56.0.492486239807.issue23674@psf.upfronthosting.co.za>
Message-ID: <1567014968.24.0.00580532476189.issue23674@roundup.psfhosted.org>


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


----------
pull_requests: +15239
pull_request: https://github.com/python/cpython/pull/15564

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

From report at bugs.python.org  Wed Aug 28 14:02:42 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 28 Aug 2019 18:02:42 +0000
Subject: [docs] [issue37176] super() docs don't say what super() does
In-Reply-To: <1559837218.79.0.128349910274.issue37176@roundup.psfhosted.org>
Message-ID: <1567015362.53.0.931068290955.issue37176@roundup.psfhosted.org>


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

I've add PR 15564 to clarify some known ambiguities for the super() docs including a specific example "what it actually does".

----------

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

From report at bugs.python.org  Wed Aug 28 23:16:57 2019
From: report at bugs.python.org (Sergey Fedoseev)
Date: Thu, 29 Aug 2019 03:16:57 +0000
Subject: [docs] [issue37973] improve docstrings of sys.float_info
Message-ID: <1567048617.81.0.748558704563.issue37973@roundup.psfhosted.org>


New submission from Sergey Fedoseev <fedoseev.sergey at gmail.com>:

In [8]: help(sys.float_info)

...

 |  
 |  dig
 |      DBL_DIG -- digits
 |

This is not very helpful, https://docs.python.org/3/library/sys.html#sys.float_info is more verbose, so probably docstrings should be updated from where.

----------
assignee: docs at python
components: Documentation
messages: 350703
nosy: docs at python, sir-sigurd
priority: normal
severity: normal
status: open
title: improve docstrings of sys.float_info
type: enhancement

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

From report at bugs.python.org  Wed Aug 28 23:30:45 2019
From: report at bugs.python.org (Sergey Fedoseev)
Date: Thu, 29 Aug 2019 03:30:45 +0000
Subject: [docs] [issue37974] zip() docstring should say 'iterator' instead
 of 'object with __next__()'
Message-ID: <1567049445.71.0.232910822835.issue37974@roundup.psfhosted.org>


New submission from Sergey Fedoseev <fedoseev.sergey at gmail.com>:

In [3]: help(zip)

class zip(object)
 |  zip(*iterables) --> zip object
 |  
 |  Return a zip object whose .__next__() method returns a tuple where
 |  the i-th element comes from the i-th iterable argument.  The .__next__()
 |  method continues until the shortest iterable in the argument sequence
 |  is exhausted and then it raises StopIteration.

This description is awkward and should use term 'iterator' as https://docs.python.org/3/library/functions.html#zip does.

The same applies to chain(), count() and zip_longest() from itertools.

----------
assignee: docs at python
components: Documentation
messages: 350704
nosy: docs at python, sir-sigurd
priority: normal
severity: normal
status: open
title: zip() docstring should say 'iterator' instead of 'object with __next__()'

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

From report at bugs.python.org  Thu Aug 29 00:51:58 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 04:51:58 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
In-Reply-To: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>
Message-ID: <1567054318.94.0.727992928146.issue36743@roundup.psfhosted.org>


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

Collecting various factlets on this topic

PEP 252 gives the specification for the descriptor protocol: "__get__(): a function callable with one or two arguments that retrieves the attribute value from an object."

function_get, property_get, classmethod_get, and staticmethod_get all support calls with one or two arguments:

    >>> a = A()
    >>> class A:
            def m(self):
                return 42
            @property
            def p(self):
                return 43
            @classmethod
            def c(cls):
                return 44
            @staticmethod
            def s():
                return 45
            
    >>> a = A()
    >>> vars(A)['m'].__get__(a)()
    42
    >>> vars(A)['m'].__get__(a, A)()
    42
    >>> vars(A)['p'].__get__(a)
    43
    >>> vars(A)['p'].__get__(a, A)
    43
    >>> vars(A)['c'].__get__(a)()
    44
    >>> vars(A)['c'].__get__(a, A)()
    44
    >>> vars(A)['s'].__get__(a)()
    45
    >>> vars(A)['s'].__get__(a, A)()
    45

Python functions that comply with the specification should also do the same (as taught by the descriptor HOWTO).  That said, I have found multiple Python functions that aren't providing the None default.  I will fix those as I find them.

type.__getattribute__, object.__getattribute__ and super.__getattribute__ always call __get__ with both attributes specified:

    >>> class D:
            def __get__(*args):
                print(args)

    >>> class C:
            d = D()

    >>> class S(C):
            def f(self):
                return super().d
        
    >>> C.d
    (<__main__.D object at 0x104d967f0>, None, <class '__main__.C'>)
    >>> C().d
    (<__main__.D object at 0x104d967f0>, <__main__.C object at 0x104df77c0>, <class '__main__.C'>)
    >>> S().f()
    (<__main__.D object at 0x104d967f0>, <__main__.S object at 0x104df7580>, <class '__main__.S'>

----------

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

From report at bugs.python.org  Thu Aug 29 01:23:07 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 05:23:07 +0000
Subject: [docs] [issue25777] Misleading descriptions in docs about invoking
 descriptors.
In-Reply-To: <1449058941.53.0.26351823319.issue25777@psf.upfronthosting.co.za>
Message-ID: <1567056187.44.0.44584140078.issue25777@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 29 01:59:46 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 05:59:46 +0000
Subject: [docs] [issue25777] Misleading descriptions in docs about invoking
 descriptors.
In-Reply-To: <1449058941.53.0.26351823319.issue25777@psf.upfronthosting.co.za>
Message-ID: <1567058386.06.0.817063314029.issue25777@roundup.psfhosted.org>


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


New changeset 03acba6f1a851064ba1fa78965ece4354d499c04 by Raymond Hettinger in branch 'master':
bpo-25777: Wording describes a lookup, not a call (GH-15573)
https://github.com/python/cpython/commit/03acba6f1a851064ba1fa78965ece4354d499c04


----------

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

From report at bugs.python.org  Thu Aug 29 01:59:54 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 29 Aug 2019 05:59:54 +0000
Subject: [docs] [issue25777] Misleading descriptions in docs about invoking
 descriptors.
In-Reply-To: <1449058941.53.0.26351823319.issue25777@psf.upfronthosting.co.za>
Message-ID: <1567058394.88.0.339653070646.issue25777@roundup.psfhosted.org>


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


----------
pull_requests: +15252
pull_request: https://github.com/python/cpython/pull/15576

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

From report at bugs.python.org  Thu Aug 29 02:07:51 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 06:07:51 +0000
Subject: [docs] [issue12077] Harmonizing descriptor protocol documentation
In-Reply-To: <1305381385.94.0.81554539251.issue12077@psf.upfronthosting.co.za>
Message-ID: <1567058870.96.0.198282871021.issue12077@roundup.psfhosted.org>


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

[Davide]
> - use the same names for __get__ arguments throughout 
> the documentation (both the reference and the tutorial),
>  e.g. __get__(self, instance, owner)

Early on the choice of variable names diverged (including in various PEPs and in the C source).  I will harmonize where I can but the cat is out of the bag.

> - decide whether the third argument should be optional, 
> or state the common usage in the reference, and fix 
> accordingly the examples in the howto

PEP 252 specifies that it is optional.  Various builtin descriptors also make it optional (function_get, staticmethod_get, classmethod_get, and property_get).

I'm fixing the main docs and non-compliant code in PR 12992

> explain data, non-data and read-only descriptors in 
> the __set__ reference, or more simply, how the >
> defintion of __set__ affects these things.

That is reasonable.  Will add to the datamodel docs.

[Jay Parlar]
> Another problem is that the examples and text in 
> the section "Functions and Methods" is no longer 
> correct in 3.x. Namely the the references to
> unbound methods

That was fixed a good while ago.

----------

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

From report at bugs.python.org  Thu Aug 29 02:12:16 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 06:12:16 +0000
Subject: [docs] [issue25777] Misleading descriptions in docs about invoking
 descriptors.
In-Reply-To: <1449058941.53.0.26351823319.issue25777@psf.upfronthosting.co.za>
Message-ID: <1567059136.9.0.635265368578.issue25777@roundup.psfhosted.org>


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


New changeset f3dca6acee609a3a12f22152fd98602c1cbadde0 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-25777: Wording describes a lookup, not a call (GH-15573) (GH-15576)
https://github.com/python/cpython/commit/f3dca6acee609a3a12f22152fd98602c1cbadde0


----------

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

From report at bugs.python.org  Thu Aug 29 02:12:51 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 06:12:51 +0000
Subject: [docs] [issue25777] Misleading descriptions in docs about invoking
 descriptors.
In-Reply-To: <1449058941.53.0.26351823319.issue25777@psf.upfronthosting.co.za>
Message-ID: <1567059171.28.0.286918143779.issue25777@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 29 02:15:56 2019
From: report at bugs.python.org (Ned Deily)
Date: Thu, 29 Aug 2019 06:15:56 +0000
Subject: [docs] [issue35946] Ambiguous documentation for assert_called_with()
In-Reply-To: <1549664108.48.0.268470561842.issue35946@roundup.psfhosted.org>
Message-ID: <1567059356.53.0.00934130863137.issue35946@roundup.psfhosted.org>


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


New changeset f5896a05edf5df91fb1b55bd481ba5b2a3682f4e by Ned Deily (R?mi Lapeyre) in branch 'master':
bpo-35946: Improve assert_called_with documentation (GH-11796)
https://github.com/python/cpython/commit/f5896a05edf5df91fb1b55bd481ba5b2a3682f4e


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

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

From report at bugs.python.org  Thu Aug 29 02:16:25 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 29 Aug 2019 06:16:25 +0000
Subject: [docs] [issue35946] Ambiguous documentation for assert_called_with()
In-Reply-To: <1549664108.48.0.268470561842.issue35946@roundup.psfhosted.org>
Message-ID: <1567059385.1.0.180388019703.issue35946@roundup.psfhosted.org>


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


----------
pull_requests: +15255
pull_request: https://github.com/python/cpython/pull/15579

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

From report at bugs.python.org  Thu Aug 29 02:22:12 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 06:22:12 +0000
Subject: [docs] [issue12077] Harmonizing descriptor protocol documentation
In-Reply-To: <1305381385.94.0.81554539251.issue12077@psf.upfronthosting.co.za>
Message-ID: <1567059732.75.0.633648352957.issue12077@roundup.psfhosted.org>


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

See PR 12992 for the cross-reference from the __set__ docs to the section covering data and non-data descriptors.

----------

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

From report at bugs.python.org  Thu Aug 29 02:39:50 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 29 Aug 2019 06:39:50 +0000
Subject: [docs] [issue35946] Ambiguous documentation for assert_called_with()
In-Reply-To: <1549664108.48.0.268470561842.issue35946@roundup.psfhosted.org>
Message-ID: <1567060790.67.0.00811815078628.issue35946@roundup.psfhosted.org>


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


New changeset 612d3935ec0b2fbe88b3fae8167f0c503c61a9ca by Miss Islington (bot) in branch '3.8':
bpo-35946: Improve assert_called_with documentation (GH-11796)
https://github.com/python/cpython/commit/612d3935ec0b2fbe88b3fae8167f0c503c61a9ca


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

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

From report at bugs.python.org  Thu Aug 29 02:46:53 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 06:46:53 +0000
Subject: [docs] [issue25435] Wrong function calls and referring to not
 removed concepts in descriptor HowTo (documentation)
In-Reply-To: <1445194189.09.0.0973348556564.issue25435@psf.upfronthosting.co.za>
Message-ID: <1567061213.37.0.296145058186.issue25435@roundup.psfhosted.org>


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

This was fixed a long time ago.

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

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

From report at bugs.python.org  Thu Aug 29 03:06:34 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 29 Aug 2019 07:06:34 +0000
Subject: [docs] [issue37974] zip() docstring should say 'iterator' instead
 of 'object with __next__()'
In-Reply-To: <1567049445.71.0.232910822835.issue37974@roundup.psfhosted.org>
Message-ID: <1567062394.8.0.138488879107.issue37974@roundup.psfhosted.org>


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


----------
nosy: +rhettinger
type:  -> behavior

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

From report at bugs.python.org  Thu Aug 29 03:10:10 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 07:10:10 +0000
Subject: [docs] [issue37974] zip() docstring should say 'iterator' instead
 of 'object with __next__()'
In-Reply-To: <1567049445.71.0.232910822835.issue37974@roundup.psfhosted.org>
Message-ID: <1567062610.59.0.119430483652.issue37974@roundup.psfhosted.org>


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

This looks fine to me.

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

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

From report at bugs.python.org  Thu Aug 29 03:30:23 2019
From: report at bugs.python.org (Ned Deily)
Date: Thu, 29 Aug 2019 07:30:23 +0000
Subject: [docs] [issue35946] Ambiguous documentation for assert_called_with()
In-Reply-To: <1549664108.48.0.268470561842.issue35946@roundup.psfhosted.org>
Message-ID: <1567063823.48.0.339206214699.issue35946@roundup.psfhosted.org>


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

Thanks for the report and thanks for the PR!  Merged for 3.8.0b4.

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

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

From report at bugs.python.org  Thu Aug 29 03:44:06 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 07:44:06 +0000
Subject: [docs] [issue23674] super() documentation isn't very clear
In-Reply-To: <1426448451.56.0.492486239807.issue23674@psf.upfronthosting.co.za>
Message-ID: <1567064646.69.0.0317294252318.issue23674@roundup.psfhosted.org>


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


New changeset cd81f0500fe98c7f4cddb06530fffabd14f036b8 by Raymond Hettinger in branch 'master':
bpo-23674:  Clarify ambiguities in super() docs (#15564)
https://github.com/python/cpython/commit/cd81f0500fe98c7f4cddb06530fffabd14f036b8


----------

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

From report at bugs.python.org  Thu Aug 29 03:44:13 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 29 Aug 2019 07:44:13 +0000
Subject: [docs] [issue23674] super() documentation isn't very clear
In-Reply-To: <1426448451.56.0.492486239807.issue23674@psf.upfronthosting.co.za>
Message-ID: <1567064653.16.0.215007675706.issue23674@roundup.psfhosted.org>


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


----------
pull_requests: +15261
pull_request: https://github.com/python/cpython/pull/15585

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

From report at bugs.python.org  Thu Aug 29 03:54:45 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 29 Aug 2019 07:54:45 +0000
Subject: [docs] [issue23674] super() documentation isn't very clear
In-Reply-To: <1426448451.56.0.492486239807.issue23674@psf.upfronthosting.co.za>
Message-ID: <1567065285.07.0.429584588857.issue23674@roundup.psfhosted.org>


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


----------
pull_requests: +15262
pull_request: https://github.com/python/cpython/pull/15586

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

From report at bugs.python.org  Thu Aug 29 03:56:22 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 07:56:22 +0000
Subject: [docs] [issue23674] super() documentation isn't very clear
In-Reply-To: <1426448451.56.0.492486239807.issue23674@psf.upfronthosting.co.za>
Message-ID: <1567065382.89.0.540111635556.issue23674@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 29 03:56:54 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 07:56:54 +0000
Subject: [docs] [issue37176] super() docs don't say what super() does
In-Reply-To: <1559837218.79.0.128349910274.issue37176@roundup.psfhosted.org>
Message-ID: <1567065414.17.0.756024648061.issue37176@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 29 04:03:04 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 08:03:04 +0000
Subject: [docs] [issue23674] super() documentation isn't very clear
In-Reply-To: <1426448451.56.0.492486239807.issue23674@psf.upfronthosting.co.za>
Message-ID: <1567065784.82.0.633473971745.issue23674@roundup.psfhosted.org>


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


New changeset 43b7ed77a8224c378b436ad3385733454198be41 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-23674:  Clarify ambiguities in super() docs (GH-15564) (GH-15586)
https://github.com/python/cpython/commit/43b7ed77a8224c378b436ad3385733454198be41


----------

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

From report at bugs.python.org  Thu Aug 29 04:27:45 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 08:27:45 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
In-Reply-To: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>
Message-ID: <1567067265.18.0.655984856965.issue36743@roundup.psfhosted.org>


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


New changeset 0dac68f1e593c11612ed54af9edb865d398f3b05 by Raymond Hettinger in branch 'master':
bpo-36743: __get__ is sometimes called without the owner argument (#12992)
https://github.com/python/cpython/commit/0dac68f1e593c11612ed54af9edb865d398f3b05


----------

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

From report at bugs.python.org  Thu Aug 29 04:27:54 2019
From: report at bugs.python.org (miss-islington)
Date: Thu, 29 Aug 2019 08:27:54 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
In-Reply-To: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>
Message-ID: <1567067274.08.0.697959042768.issue36743@roundup.psfhosted.org>


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


----------
pull_requests: +15265
pull_request: https://github.com/python/cpython/pull/15589

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

From report at bugs.python.org  Thu Aug 29 04:28:45 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 08:28:45 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
In-Reply-To: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>
Message-ID: <1567067325.25.0.414621441123.issue36743@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 29 04:29:06 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 29 Aug 2019 08:29:06 +0000
Subject: [docs] [issue37973] improve docstrings of sys.float_info
In-Reply-To: <1567048617.81.0.748558704563.issue37973@roundup.psfhosted.org>
Message-ID: <1567067346.52.0.989579952371.issue37973@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

Unhelpful indeed. +1 to updating those docstrings to match the details at docs.python.org.

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

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

From report at bugs.python.org  Thu Aug 29 04:29:30 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 08:29:30 +0000
Subject: [docs] [issue12077] Harmonizing descriptor protocol documentation
In-Reply-To: <1305381385.94.0.81554539251.issue12077@psf.upfronthosting.co.za>
Message-ID: <1567067370.92.0.372595700511.issue12077@roundup.psfhosted.org>


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


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

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

From report at bugs.python.org  Thu Aug 29 05:01:20 2019
From: report at bugs.python.org (Aleksey)
Date: Thu, 29 Aug 2019 09:01:20 +0000
Subject: [docs] =?utf-8?q?=5Bissue37975=5D_Typo_in_the_documentation_by_C?=
 =?utf-8?q?-API_DateTime_Objects=C2=B6?=
Message-ID: <1567069280.84.0.885119110407.issue37975@roundup.psfhosted.org>


New submission from Aleksey <st.p.inomirie at gmail.com>:

In the documentation by Python 3.5 C-API DateTime Objects (https://docs.python.org/3.5/c-api/datetime.html) method PyDateTime_DELTA_GET_MICROSECOND has not "S" in the end of method name. But in the header file "datetime.h", this method has "S" and so named PyDateTime_DELTA_GET_MICROSECONDS.

----------
assignee: docs at python
components: Documentation
messages: 350758
nosy: Nukopol, docs at python
priority: normal
severity: normal
status: open
title: Typo in the documentation by C-API DateTime Objects?
type: behavior
versions: Python 3.5

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

From report at bugs.python.org  Thu Aug 29 05:02:55 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 29 Aug 2019 09:02:55 +0000
Subject: [docs] [issue36743] Docs: Descript __get__ signature defined
 differently across the docs
In-Reply-To: <1556387803.45.0.177981206888.issue36743@roundup.psfhosted.org>
Message-ID: <1567069375.43.0.0633568838986.issue36743@roundup.psfhosted.org>


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


New changeset c71ae1a45bd6e6d0f5aebc470b35f5a7dc0d8078 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-36743: __get__ is sometimes called without the owner argument (GH-12992) (GH-15589)
https://github.com/python/cpython/commit/c71ae1a45bd6e6d0f5aebc470b35f5a7dc0d8078


----------

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

From report at bugs.python.org  Thu Aug 29 05:16:18 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Thu, 29 Aug 2019 09:16:18 +0000
Subject: [docs] =?utf-8?q?=5Bissue37975=5D_Typo_in_the_documentation_by_C?=
 =?utf-8?q?-API_DateTime_Objects=C2=B6?=
In-Reply-To: <1567069280.84.0.885119110407.issue37975@roundup.psfhosted.org>
Message-ID: <1567070178.78.0.81492190638.issue37975@roundup.psfhosted.org>


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

Thanks for the report. This was fixed in 82cd3cede804ca694fb0657fd985d5eff84a414f (https://bugs.python.org/issue31678). It was not merged to 3.5 at that time. Now 3.5 only accepts security fixes so I would propose closing this as duplicate of issue31678.

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

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

From report at bugs.python.org  Thu Aug 29 09:09:30 2019
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 29 Aug 2019 13:09:30 +0000
Subject: [docs] [issue37878] Sub-Interpreters : Document
 PyThreadState_DeleteCurrent()
In-Reply-To: <1565985235.6.0.212314052144.issue37878@roundup.psfhosted.org>
Message-ID: <1567084170.47.0.563134829544.issue37878@roundup.psfhosted.org>


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

I did a GitHub code search on "PyThreadState_DeleteCurrent" in C code:
https://github.com/search?l=C&q=PyThreadState_DeleteCurrent&type=Code

I looked at the first 6 pages: I only found copies of the Python source code, but no *call* to this function. It seems like this function is not used outside Python, so it's fine to remove it.

Anyway, if an user complains lately, we can add it back. It's fine.

In case of doubt, in this case, I'm fine with removing the function.

----------

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

From report at bugs.python.org  Thu Aug 29 09:28:33 2019
From: report at bugs.python.org (Daniel Pope)
Date: Thu, 29 Aug 2019 13:28:33 +0000
Subject: [docs] [issue37977] Big red pickle security warning should stress
 the point even more
Message-ID: <1567085313.43.0.156950423126.issue37977@roundup.psfhosted.org>


New submission from Daniel Pope <lord.mauve at gmail.com>:

CVEs related to unpickling untrusted data continue to come up a few times a year:

https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=pickle

This is certainly the tip of the iceberg. In a previous role I noted several internal services that could be compromised with maliciously crafted pickles. In my current role I can already see two internal services that look vulnerable. And in both organisations, little attention was paid to pickle data exchanged with other users over network filesystems, which may allow privilege escalation.

Chatting to Alex Willmer after his Europython talk in 2018 (https://github.com/moreati/pickle-fuzz/blob/master/Rehabilitating%20Pickle.pdf) we discussed that the red warning in the docs is still not prominent enough, even after moving it to the top of the page in https://bugs.python.org/issue9105.

The warning currently says:

"Warning: The pickle module is not secure against erroneous or maliciously constructed data. Never unpickle data received from an untrusted or unauthenticated source."

I would suggest several improvements:

* Simpler, more direct English.
* Explain the severity of vulnerability that doing this will cause.
* Link to the hmac module which can be used to prevent tampering.
* Link to the json module which is safer if less powerful.
* Simply making the red box bigger (adding more text) will increase the prominence of the warning.

----------
assignee: docs at python
components: Documentation
messages: 350777
nosy: docs at python, lordmauve
priority: normal
severity: normal
status: open
title: Big red pickle security warning should stress the point even more
type: security
versions: Python 3.8, Python 3.9

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

From report at bugs.python.org  Thu Aug 29 09:32:53 2019
From: report at bugs.python.org (Daniel Pope)
Date: Thu, 29 Aug 2019 13:32:53 +0000
Subject: [docs] [issue37977] Big red pickle security warning should stress
 the point even more
In-Reply-To: <1567085313.43.0.156950423126.issue37977@roundup.psfhosted.org>
Message-ID: <1567085573.34.0.525872720912.issue37977@roundup.psfhosted.org>


Change by Daniel Pope <lord.mauve at gmail.com>:


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

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

From report at bugs.python.org  Thu Aug 29 12:31:00 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Thu, 29 Aug 2019 16:31:00 +0000
Subject: [docs] [issue37970] urllib.parse docstrings incomplete
In-Reply-To: <1567009599.74.0.471882594509.issue37970@roundup.psfhosted.org>
Message-ID: <1567096260.25.0.223547906432.issue37970@roundup.psfhosted.org>


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

> Also, the note about not splitting netloc is misleading; the components > of netloc (username, password, hostname, and port) are available as >extra attributes of the returned SplitResult.

Also, the docs in urllib.parse.rst should also be updated to correct this misleading statement.

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

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

From report at bugs.python.org  Thu Aug 29 12:41:25 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Thu, 29 Aug 2019 16:41:25 +0000
Subject: [docs] [issue37973] improve docstrings of sys.float_info
In-Reply-To: <1567048617.81.0.748558704563.issue37973@roundup.psfhosted.org>
Message-ID: <1567096885.54.0.481534448661.issue37973@roundup.psfhosted.org>


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

See also #37970

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

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

From report at bugs.python.org  Thu Aug 29 12:52:21 2019
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 29 Aug 2019 16:52:21 +0000
Subject: [docs] [issue37973] improve docstrings of sys.float_info
In-Reply-To: <1567048617.81.0.748558704563.issue37973@roundup.psfhosted.org>
Message-ID: <1567097541.87.0.763864564929.issue37973@roundup.psfhosted.org>


Mark Dickinson <dickinsm at gmail.com> added the comment:

@nanjekyejoannah I'm not seeing how that issue is related to this one (except that they're both about docstrings). Can you elaborate?

----------

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

From report at bugs.python.org  Thu Aug 29 12:58:46 2019
From: report at bugs.python.org (Joannah Nanjekye)
Date: Thu, 29 Aug 2019 16:58:46 +0000
Subject: [docs] [issue37973] improve docstrings of sys.float_info
In-Reply-To: <1567048617.81.0.748558704563.issue37973@roundup.psfhosted.org>
Message-ID: <1567097926.06.0.978434173958.issue37973@roundup.psfhosted.org>


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

I just referenced another area that may need help updating/improving doc strings.

----------

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

From report at bugs.python.org  Thu Aug 29 13:49:45 2019
From: report at bugs.python.org (hai shi)
Date: Thu, 29 Aug 2019 17:49:45 +0000
Subject: [docs] [issue15125] argparse: positional arguments containing - in
 name not handled well
In-Reply-To: <1340292847.64.0.123942573403.issue15125@psf.upfronthosting.co.za>
Message-ID: <1567100985.6.0.156418127469.issue15125@roundup.psfhosted.org>


hai shi <shihai1991 at 126.com> added the comment:

How about:
1. Adding documentation as steven said.
2. If user use '-' of positional arguments in latest cpython, we cloud remind user that `the '-' of positional arguments be replaced by '_' since cpython 4.0`
3.Applying Simon Law's patch.

----------
nosy: +shihai1991

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

From report at bugs.python.org  Fri Aug 30 01:50:47 2019
From: report at bugs.python.org (Karthikeyan Singaravelan)
Date: Fri, 30 Aug 2019 05:50:47 +0000
Subject: [docs] =?utf-8?q?=5Bissue37975=5D_Typo_in_the_documentation_by_C?=
 =?utf-8?q?-API_DateTime_Objects=C2=B6?=
In-Reply-To: <1567069280.84.0.885119110407.issue37975@roundup.psfhosted.org>
Message-ID: <1567144247.91.0.685954015412.issue37975@roundup.psfhosted.org>


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


----------
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Incorrect C Function name for timedelta

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

From sh.zahidali at yahoo.com  Thu Aug 29 13:31:56 2019
From: sh.zahidali at yahoo.com (Zahid Ali)
Date: Thu, 29 Aug 2019 17:31:56 +0000 (UTC)
Subject: [docs] The Python Bug report
References: <758750876.291005.1567099916720.ref@mail.yahoo.com>
Message-ID: <758750876.291005.1567099916720@mail.yahoo.com>

Dear Python Team,
I find a following issue in python string function.Kindly run the following example and check
Example 1
txt = "Hello, welcome to my world."
x = txt.find("l", 0, 4)
print(x)
Out put is 2------------------------------------------------------------------------Example 2
txt = "Hello, welcome to my world."
x = txt.find("ll", 0, 4)
print(x)
Out put is 2?
Conclusion: The my point of view is example 2 answer should be 1 because we find in example #2 'll' double l, so it should be 1?









-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190829/7e160e39/attachment-0001.html>

From tetpapx at bk.ru  Tue Aug 27 15:20:36 2019
From: tetpapx at bk.ru (Alexander Ilin)
Date: Tue, 27 Aug 2019 22:20:36 +0300
Subject: [docs] functional howto documentation typo
Message-ID: <6b40f96f-5262-9eea-2f86-bea0d2ca9493@bk.ru>

Good afternoon!

I've noticed a tiny typo in the documentation 
<https://docs.python.org/3/howto/functional.html>- in a generator 
expressions module ... seems to be placed 1 line upper than necessary

for expr3 in sequence3 ...
if condition3
for exprN in sequenceN

instead of

for expr3 in sequence3
if condition3 ...
for exprN in sequenceN

Here is a screenshot

Sorry if I've misunderstood something and ellipsis should be on their 
current position

Best,
Alexander

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190827/825fc6c4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hoddkgfljcppkmfl.png
Type: image/png
Size: 50309 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20190827/825fc6c4/attachment-0001.png>

From report at bugs.python.org  Fri Aug 30 20:43:41 2019
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 31 Aug 2019 00:43:41 +0000
Subject: [docs] [issue37989] documentation format error in Chinese version
Message-ID: <1567212221.93.0.936577335407.issue37989@roundup.psfhosted.org>


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

The translations of the docs are maintained in a separate repository by a separate group of people.  The sidebar on the left of the page you linked to has a link called '?? Bug' to 
https://docs.python.org/zh-cn/3/bugs.html.  I am guessing that this page or one it links to has instruction on where to send translation bug reports.

----------
nosy: +mdk, terry.reedy
resolution:  -> third party
stage:  -> resolved
status: open -> closed

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

From report at bugs.python.org  Sat Aug 31 01:51:36 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 31 Aug 2019 05:51:36 +0000
Subject: [docs] [issue37977] Big red pickle security warning should stress
 the point even more
In-Reply-To: <1567085313.43.0.156950423126.issue37977@roundup.psfhosted.org>
Message-ID: <1567230696.52.0.765744520561.issue37977@roundup.psfhosted.org>


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


New changeset daa82d019c52e95c3c57275307918078c1c0ac81 by Raymond Hettinger (Daniel Pope) in branch 'master':
bpo-37977: Warn more strongly and clearly about pickle security (GH-15595)
https://github.com/python/cpython/commit/daa82d019c52e95c3c57275307918078c1c0ac81


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

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

From report at bugs.python.org  Sat Aug 31 01:52:21 2019
From: report at bugs.python.org (miss-islington)
Date: Sat, 31 Aug 2019 05:52:21 +0000
Subject: [docs] [issue37977] Big red pickle security warning should stress
 the point even more
In-Reply-To: <1567085313.43.0.156950423126.issue37977@roundup.psfhosted.org>
Message-ID: <1567230741.92.0.70464047158.issue37977@roundup.psfhosted.org>


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


----------
pull_requests: +15297
pull_request: https://github.com/python/cpython/pull/15629

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

From report at bugs.python.org  Sat Aug 31 02:02:18 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 31 Aug 2019 06:02:18 +0000
Subject: [docs] [issue37977] Big red pickle security warning should stress
 the point even more
In-Reply-To: <1567085313.43.0.156950423126.issue37977@roundup.psfhosted.org>
Message-ID: <1567231338.63.0.909413542581.issue37977@roundup.psfhosted.org>


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


New changeset 6922b9e4fce635339cb94c2fdef6bba4e2a99621 by Raymond Hettinger (Miss Islington (bot)) in branch '3.8':
bpo-37977: Warn more strongly and clearly about pickle security (GH-15595) (GH-15629)
https://github.com/python/cpython/commit/6922b9e4fce635339cb94c2fdef6bba4e2a99621


----------

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

From report at bugs.python.org  Sat Aug 31 02:02:42 2019
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 31 Aug 2019 06:02:42 +0000
Subject: [docs] [issue37977] Big red pickle security warning should stress
 the point even more
In-Reply-To: <1567085313.43.0.156950423126.issue37977@roundup.psfhosted.org>
Message-ID: <1567231362.25.0.503830531828.issue37977@roundup.psfhosted.org>


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


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

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

From harmony.is.valued at gmail.com  Sat Aug 31 07:28:50 2019
From: harmony.is.valued at gmail.com (=?UTF-8?B?44GQ44Gj44Gh44KH44KT?=)
Date: Sat, 31 Aug 2019 20:28:50 +0900
Subject: [docs] I want Python 3.5.4 Documentation
Message-ID: <CAH37RTXGH8GTtGkEyVLOrwM0vA1JdQ1M6vj+DKhCpGOWm1Kb0g@mail.gmail.com>

Hi

I want Python 3.5.4 Documentation

Could you please send Python 3.5.4 Documentation?

Thank you for you help.

takayasu taniguchi

From tombelpasso at gmail.com  Sat Aug 31 18:37:42 2019
From: tombelpasso at gmail.com (Tom Belpasso)
Date: Sat, 31 Aug 2019 15:37:42 -0700
Subject: [docs] Documentation bug: struct library,
 endian format chars are reversed
Message-ID: <CAAoy8jLQHtE2=EyLsJHB7tjN2urHhLpNn3YoD5LMp45EtJt=Mg@mail.gmail.com>

Dear Python Docs:

The struct library has table with format values for pack and unpack.
In section: 7.1.2.1. Byte Order, Size, and Alignment

The big endian and little endian characters are reversed in the table.

'>' should be little endian, just like the character looks.
'<' should be big endian, just like the character.

I have verified that this is the correct behavior after use the wrong one
in my program and wondering why I was seeing so many large fluctuations in
my plots. I had wasted many day's rewiring my prototype to get rid of the
noise.  It turned out it was just the byte order of my 16bit data what was
getting misinterpreted.

I found the problem, when I was attempting to write a WAV format file,
which is big endian and it was coming out backwards!

To verify my assertion:
## hex 16 bit number is the bytes for H and L, where 'H' is MS byte
struct.pack('<H',0x484c)
# should return: 'b'LH' which is big endian, 'H' is at the end.

struct.pack('>H',0x484c)
# should return: 'b'HL'

Thank you for your hard work.

Kind regards,
Tom Belpasso
Integrated Vision
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20190831/33e71347/attachment.html>