From report at bugs.python.org  Sat Apr  1 06:50:49 2017
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 01 Apr 2017 10:50:49 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491043849.46.0.0267428378321.issue29956@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

> I suggest changing the main docs to match the existing docstring, "Return e raised to the power of x."  

+1 for this description.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sat Apr  1 08:02:46 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 01 Apr 2017 12:02:46 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1491048166.73.0.123816942875.issue29751@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

Thank you.  I've added that change.

For the backporting, I think that would only be applicable to 3.6 and 3.7?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Sat Apr  1 08:22:59 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 01 Apr 2017 12:22:59 +0000
Subject: [docs] [issue29725] sqlite3.Cursor doesn't properly document
 "arraysize"
In-Reply-To: <1488732449.69.0.822466282685.issue29725@psf.upfronthosting.co.za>
Message-ID: <1491049379.07.0.248038713282.issue29725@psf.upfronthosting.co.za>


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


----------
pull_requests: +1129

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29725>
_______________________________________

From report at bugs.python.org  Sat Apr  1 08:27:29 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 01 Apr 2017 12:27:29 +0000
Subject: [docs] [issue29725] sqlite3.Cursor doesn't properly document
 "arraysize"
In-Reply-To: <1488732449.69.0.822466282685.issue29725@psf.upfronthosting.co.za>
Message-ID: <1491049649.81.0.0070749893164.issue29725@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

Thank you so much for being patient with me and explaining that.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29725>
_______________________________________

From report at bugs.python.org  Sat Apr  1 09:18:38 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 01 Apr 2017 13:18:38 +0000
Subject: [docs] [issue26947] Documentation improvement needed
In-Reply-To: <1462364495.31.0.190726094652.issue26947@psf.upfronthosting.co.za>
Message-ID: <1491052718.38.0.51019982144.issue26947@psf.upfronthosting.co.za>


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


----------
pull_requests: +1130

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 10:51:42 2017
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 01 Apr 2017 14:51:42 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491058302.56.0.292220213048.issue29956@psf.upfronthosting.co.za>


Changes by Mark Dickinson <dickinsm at gmail.com>:


----------
pull_requests: +1133

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sat Apr  1 10:53:01 2017
From: report at bugs.python.org (Mark Dickinson)
Date: Sat, 01 Apr 2017 14:53:01 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491058381.64.0.989339649426.issue29956@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

PR made. New wording is:

"""
Return e raised to the power *x*, where e = 2.718281... is the base of natural logarithms.
"""

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sat Apr  1 16:54:21 2017
From: report at bugs.python.org (R. David Murray)
Date: Sat, 01 Apr 2017 20:54:21 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491080061.39.0.684303796833.issue29947@psf.upfronthosting.co.za>


R. David Murray added the comment:

Given how old socket server is, and that it doesn't actually require that API, we should probably just reword the documentation so that it is clear that RequestHandlerClass is the default Handler implementation (and that you can work with setup/handle/finish if you want to subclass it), and document what the *actual* requirements on the Handler are.  

We are unlikely to change socketserver's actual API at this point.

I don't think there's any need for a new issue, let's just make this a documentation issue.  The original title still even applies :)  We will need signoff from someone with more direct interest in the socketserver module than me, but given that the "future" for the stuff socketserver handles is asyncio, I suspect the only objection we might get is "it's not worth it".  But if someone wants to do the work, *I* don't see a reason to reject it.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage: resolved -> 
type: enhancement -> behavior
versions: +Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 18:16:24 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Sat, 01 Apr 2017 22:16:24 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491084984.73.0.490497235367.issue29947@psf.upfronthosting.co.za>


Dominic Mayers added the comment:

The reason why I feel we should not make it immediately a documentation issue is that I don't know how a person working on documentation could proceed ahead without a clear go ahead signal from developers. In that sense,  having a documentation that says that the variable name does not reflect its intent seems tricky. It's very easy to change a variable name. It cannot possibly break the code, except for a collision, but they are easy to avoid.  If we don't have the interest of developers, not even for a simple renaming, I don't see a go ahead signal in this.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 18:34:22 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Sat, 01 Apr 2017 22:34:22 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491086062.66.0.942604041138.issue29947@psf.upfronthosting.co.za>


Dominic Mayers added the comment:

Oops, I did not realize that David was one of the developers. Well, may be this needs the attention of more than one developer.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 19:13:50 2017
From: report at bugs.python.org (Martin Panter)
Date: Sat, 01 Apr 2017 23:13:50 +0000
Subject: [docs] [issue26947] Hashable documentation improvement needed
In-Reply-To: <1462364495.31.0.190726094652.issue26947@psf.upfronthosting.co.za>
Message-ID: <1491088430.63.0.545865076675.issue26947@psf.upfronthosting.co.za>


Martin Panter added the comment:

The pull request currently suggests ?All of Python?s immutable built-in objects are hashable; mutable containers (such as lists or dictionaries) are not.? This seems better wording than the original.

FWIW, I would have tried ?Python?s built-in immutable objects are hashable, while mutable containers (such as lists and dictionaries) are not hashable.?

----------
nosy: +martin.panter
title: Documentation improvement needed -> Hashable documentation improvement needed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 22:50:50 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Sun, 02 Apr 2017 02:50:50 +0000
Subject: [docs] [issue26947] Hashable documentation improvement needed
In-Reply-To: <1462364495.31.0.190726094652.issue26947@psf.upfronthosting.co.za>
Message-ID: <1491101450.11.0.311811062274.issue26947@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:


New changeset 64c887ab3a400cf91bde4f0c5ef69eacc88bc5e1 by Senthil Kumaran (csabella) in branch 'master':
bpo-26947: DOC: clarify wording on hashable in glossary (#948)
https://github.com/python/cpython/commit/64c887ab3a400cf91bde4f0c5ef69eacc88bc5e1


----------
nosy: +orsenthil

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 22:52:58 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Sun, 02 Apr 2017 02:52:58 +0000
Subject: [docs] [issue26947] Hashable documentation improvement needed
In-Reply-To: <1462364495.31.0.190726094652.issue26947@psf.upfronthosting.co.za>
Message-ID: <1491101578.44.0.245585501917.issue26947@psf.upfronthosting.co.za>


Changes by Senthil Kumaran <senthil at uthcode.com>:


----------
pull_requests: +1139

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 22:53:02 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Sun, 02 Apr 2017 02:53:02 +0000
Subject: [docs] [issue26947] Hashable documentation improvement needed
In-Reply-To: <1462364495.31.0.190726094652.issue26947@psf.upfronthosting.co.za>
Message-ID: <1491101582.66.0.313382386628.issue26947@psf.upfronthosting.co.za>


Changes by Senthil Kumaran <senthil at uthcode.com>:


----------
pull_requests: +1140

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 23:00:38 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Sun, 02 Apr 2017 03:00:38 +0000
Subject: [docs] [issue26947] Hashable documentation improvement needed
In-Reply-To: <1462364495.31.0.190726094652.issue26947@psf.upfronthosting.co.za>
Message-ID: <1491102038.66.0.817118401883.issue26947@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:


New changeset a71a3ad54d14483cfaebd8e0fb96c97c798d9e32 by Senthil Kumaran in branch '3.6':
bpo-26947: DOC: clarify wording on hashable in glossary (#948) (#957)
https://github.com/python/cpython/commit/a71a3ad54d14483cfaebd8e0fb96c97c798d9e32


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 23:00:43 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Sun, 02 Apr 2017 03:00:43 +0000
Subject: [docs] [issue26947] Hashable documentation improvement needed
In-Reply-To: <1462364495.31.0.190726094652.issue26947@psf.upfronthosting.co.za>
Message-ID: <1491102043.82.0.0950867325058.issue26947@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:


New changeset 51fc7e3d6a29de7b3142e51f8caf4d31f7ac72a0 by Senthil Kumaran in branch '3.5':
bpo-26947: DOC: clarify wording on hashable in glossary (#948) (#958)
https://github.com/python/cpython/commit/51fc7e3d6a29de7b3142e51f8caf4d31f7ac72a0


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 23:02:29 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Sun, 02 Apr 2017 03:02:29 +0000
Subject: [docs] [issue26947] Hashable documentation improvement needed
In-Reply-To: <1462364495.31.0.190726094652.issue26947@psf.upfronthosting.co.za>
Message-ID: <1491102149.96.0.524849097214.issue26947@psf.upfronthosting.co.za>


Changes by Senthil Kumaran <senthil at uthcode.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 23:03:20 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Sun, 02 Apr 2017 03:03:20 +0000
Subject: [docs] [issue26947] Hashable documentation improvement needed
In-Reply-To: <1462364495.31.0.190726094652.issue26947@psf.upfronthosting.co.za>
Message-ID: <1491102200.64.0.430170185025.issue26947@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:

I reviewed in the pull request. I agree that the wording was slightly better than the original.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 23:11:39 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Sun, 02 Apr 2017 03:11:39 +0000
Subject: [docs] [issue26947] Hashable documentation improvement needed
In-Reply-To: <1462364495.31.0.190726094652.issue26947@psf.upfronthosting.co.za>
Message-ID: <1491102699.84.0.991356303846.issue26947@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:

I have to admit, I did not see some of the negative votes in this ticket before merging the patch. If your is opposition is strong,  please comment and suggest a better improvement over the patch. thank you!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26947>
_______________________________________

From report at bugs.python.org  Sat Apr  1 23:20:32 2017
From: report at bugs.python.org (Martin Panter)
Date: Sun, 02 Apr 2017 03:20:32 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1491103232.81.0.283717141782.issue29751@psf.upfronthosting.co.za>


Martin Panter added the comment:

Underscores are only applicable to 3.6+, but the original concern about leading zeros applies to 3.5.

On Git Hub I suggested dropping the details and just referring to the Lexical Analysis section <https://docs.python.org/3.5/reference/lexical_analysis.html#integer-literals> for the details.

FWIW here is my understanding of integer literals (with base=0):

* 0x10 => hexadecimal
* 0b10 => binary
* 0o10 => octal (corresponds to 010 in Python 2)
* 01 => illegal (avoids conflict with Python 2)
* 00 => zero (special case; was treated as octal zero in Python 2)
* 10 => decimal (must not start with digit 0)

If you want to spell out the rules, in my mind there are four special prefixes, 0x, 0b, 0o and 0, and the default is decimal if none of those prefixes apply.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Sun Apr  2 01:44:07 2017
From: report at bugs.python.org (Martin Panter)
Date: Sun, 02 Apr 2017 05:44:07 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491111847.33.0.913700721302.issue29947@psf.upfronthosting.co.za>


Martin Panter added the comment:

By ?factory instance?, I presume you just mean a function (or class or method) that returns an appropriate object when called. (I think these are normally called ?factory functions?. Instances are objects, the things that class constructors and factories return.)

What is being proposed? The best idea that I understand is hinted in <https://bugs.python.org/issue29947#msg290976>. That is, to document and allow any function (not just a class or factory) to be passed as (or instead of) the RequestHandlerClass parameter.

This is a significant change to the documentation and API, but I would support it, and I think it should already be supported by the implementation.

The question of renaming the RequestHandlerClass parameter is a harder decision IMO. I think it would be easier to make the documentation clear that it is a misnomer and does not have to be a class. But in the long term, renaming the parameter seems nicer.

If it was ?renamed?, we would first have to add a competing parameter, keep the old parameter around, consider adding deprecation warnings in 2020 when Python 2 is dead, document both parameters, decide if anything should happen when both parameters are passed, etc. Much trickier, but possible. This renaming process is similar to ?base64.encodestring? vs ?encodebytes?, but more involved. I can?t think of an example where a function or constructor parameter was renamed like this.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Sun Apr  2 02:41:14 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Sun, 02 Apr 2017 06:41:14 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491115274.44.0.184259610978.issue29947@psf.upfronthosting.co.za>


Dominic Mayers added the comment:

I did not think very far when said that renaming the parameter could not possibly break the code ! Oh well ! But, renaming the parameter was not important in itself.  It was to make the situation clearer and easier for those who write the documentation. Martin mentioned that it is a big change for the API. This is what I had in mind. And yes, I should have used 'factory function', not 'factory instance'. Oh well ! I am glad things are working and that we will move ahead to resolve this issue.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Sun Apr  2 06:45:42 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 02 Apr 2017 10:45:42 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491129942.57.0.106981000781.issue19225@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset e8c763128fb459c5c98194e4312f31493c0f12df by Serhiy Storchaka (cocoatomo) in branch 'master':
bpo-19225: Add a table of warning names and missed exception names in C API doc (#881)
https://github.com/python/cpython/commit/e8c763128fb459c5c98194e4312f31493c0f12df


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Sun Apr  2 06:48:03 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 02 Apr 2017 10:48:03 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491130083.3.0.713499171293.issue19225@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for your patch Kinebuchi. Do you mind to backport it to other branches?

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Sun Apr  2 09:34:54 2017
From: report at bugs.python.org (R. David Murray)
Date: Sun, 02 Apr 2017 13:34:54 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491140093.97.0.250192515553.issue29947@psf.upfronthosting.co.za>


R. David Murray added the comment:

Yes, the difficulty in renaming the parameter was why I suggested a doc change only.  I'm not sure it it is worth it to go through a deprecation cycle for socketserver to change the name, though it certainly would be nice.  Martin and I could make that decision, but it would be better to get input from other devs.  And, if we make this the documentation issue, we should open a separate issue for the parameter rename.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Sun Apr  2 19:37:38 2017
From: report at bugs.python.org (Kinebuchi Tomohiko)
Date: Sun, 02 Apr 2017 23:37:38 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491176258.64.0.221717237122.issue19225@psf.upfronthosting.co.za>


Changes by Kinebuchi Tomohiko <cocoatomo77 at gmail.com>:


----------
pull_requests: +1143

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Sun Apr  2 19:42:25 2017
From: report at bugs.python.org (Kinebuchi Tomohiko)
Date: Sun, 02 Apr 2017 23:42:25 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491176545.26.0.0988405359198.issue19225@psf.upfronthosting.co.za>


Changes by Kinebuchi Tomohiko <cocoatomo77 at gmail.com>:


----------
pull_requests: +1144

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Sun Apr  2 19:46:13 2017
From: report at bugs.python.org (Kinebuchi Tomohiko)
Date: Sun, 02 Apr 2017 23:46:13 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491176773.04.0.741863238363.issue19225@psf.upfronthosting.co.za>


Changes by Kinebuchi Tomohiko <cocoatomo77 at gmail.com>:


----------
pull_requests: +1145

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Sun Apr  2 21:43:30 2017
From: report at bugs.python.org (Kinebuchi Tomohiko)
Date: Mon, 03 Apr 2017 01:43:30 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491183810.29.0.611219598359.issue19225@psf.upfronthosting.co.za>


Kinebuchi Tomohiko added the comment:

I created backporting pull requests for 2.7, 3.5 and 3.6.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Sun Apr  2 22:06:58 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Mon, 03 Apr 2017 02:06:58 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491185218.15.0.446146861103.issue29947@psf.upfronthosting.co.za>


Changes by Dominic Mayers <dominic_mayers at yahoo.com>:


Removed file: http://bugs.python.org/file46768/factorymixinclass

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Sun Apr  2 22:07:52 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Mon, 03 Apr 2017 02:07:52 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491185272.16.0.0664474905142.issue29947@psf.upfronthosting.co.za>


Changes by Dominic Mayers <dominic_mayers at yahoo.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file46770/Issue29947_for_discussion.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Sun Apr  2 22:10:35 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Mon, 03 Apr 2017 02:10:35 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491185435.79.0.00484421808982.issue29947@psf.upfronthosting.co.za>


Dominic Mayers added the comment:

I started to look at the documentation to see what would need to be changed, assuming that we agree for a change in the API. Just for the purpose of this discussion, I created a patch that only change the comments in socketserver.py.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Mon Apr  3 04:09:30 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Mon, 03 Apr 2017 08:09:30 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491206970.15.0.506154583981.issue29947@psf.upfronthosting.co.za>


Dominic Mayers added the comment:

The key point, IMHO, is that the BaseRequestHandler class is just provided as an option and its API (setup, handle and finish) is ignored by the code that we support. 

Some applications may have used the API, but these are details in applications. Simply, we keep BaseRequestHandler as it is so that we do not break these applications. 

So, yes, we should keep supporting the API, but we do not expect this API on our side. The latter is the key point.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Mon Apr  3 05:16:56 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 03 Apr 2017 09:16:56 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491211016.24.0.0945004214301.issue19225@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +1146

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Mon Apr  3 05:20:56 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 03 Apr 2017 09:20:56 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491211256.4.0.76749063689.issue19225@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +1147

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Mon Apr  3 08:49:25 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Mon, 03 Apr 2017 12:49:25 +0000
Subject: [docs] [issue29968] Document that no characters are allowed to
 proceed \ in explicit line joining
Message-ID: <1491223765.12.0.65807116216.issue29968@psf.upfronthosting.co.za>


New submission from Jim Fasarakis-Hilliard:

After looking through the code, the tokenizer only allows a new line character to proceed `\` in explicit line joining [1].

The Devguide section on it [2] actually states many of the limitations of using `\` but not directly that nothing is allowed after it (it does have a remark on comments). 

Would it be a good idea to amend it to state that no characters are allowed after `\`?

[1]: https://github.com/python/cpython/blob/734125938d4653459593ebd28a0aec086efb1f27/Parser/tokenizer.c#L1847
[2]: https://docs.python.org/3/reference/lexical_analysis.html#explicit-line-joining

----------
assignee: docs at python
components: Documentation
messages: 291067
nosy: Jim Fasarakis-Hilliard, docs at python
priority: normal
severity: normal
status: open
title: Document that no characters are allowed to proceed \ in explicit line joining

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29968>
_______________________________________

From report at bugs.python.org  Mon Apr  3 08:57:04 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Mon, 03 Apr 2017 12:57:04 +0000
Subject: [docs] [issue29968] Document that no characters are allowed to
 proceed \ in explicit line joining
In-Reply-To: <1491223765.12.0.65807116216.issue29968@psf.upfronthosting.co.za>
Message-ID: <1491224224.93.0.0642389600066.issue29968@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

Alternatively, stripping all white-space that proceed `\` could be considered if it seems like a good idea.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29968>
_______________________________________

From report at bugs.python.org  Mon Apr  3 11:34:14 2017
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 03 Apr 2017 15:34:14 +0000
Subject: [docs] [issue29973] Travis CI docs broken: UnboundLocalError: local
 variable 'prefix' referenced before assignment
Message-ID: <1491233654.37.0.108307382934.issue29973@psf.upfronthosting.co.za>


New submission from STINNER Victor:

https://travis-ci.org/python/cpython/jobs/218107336

CPython: master branch
Sphinx 1.5.4

make[1]: Entering directory `/home/travis/build/python/cpython/Doc'
./venv/bin/python -m sphinx -b suspicious -d build/doctrees -D latex_elements.papersize= -q -W . build/suspicious 

Exception occurred:
  File "/home/travis/virtualenv/python3.6.0/lib/python3.6/site-packages/sphinx/domains/python.py", line 317, in before_content
    if prefix:
UnboundLocalError: local variable 'prefix' referenced before assignment

----------
assignee: docs at python
components: Documentation, Tests
messages: 291075
nosy: docs at python, haypo
priority: normal
severity: normal
status: open
title: Travis CI docs broken: UnboundLocalError: local variable 'prefix' referenced before assignment
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29973>
_______________________________________

From report at bugs.python.org  Mon Apr  3 11:44:19 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 03 Apr 2017 15:44:19 +0000
Subject: [docs] [issue29973] Travis CI docs broken: UnboundLocalError: local
 variable 'prefix' referenced before assignment
In-Reply-To: <1491233654.37.0.108307382934.issue29973@psf.upfronthosting.co.za>
Message-ID: <1491234259.02.0.793047127359.issue29973@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

This already is fixed in mainstream. https://github.com/sphinx-doc/sphinx/issues/3597

Sphinx 1.5.5 will be released soon. https://github.com/sphinx-doc/sphinx/issues/3598

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29973>
_______________________________________

From report at bugs.python.org  Mon Apr  3 12:07:45 2017
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 03 Apr 2017 16:07:45 +0000
Subject: [docs] [issue29973] Travis CI docs broken: UnboundLocalError: local
 variable 'prefix' referenced before assignment
In-Reply-To: <1491233654.37.0.108307382934.issue29973@psf.upfronthosting.co.za>
Message-ID: <1491235665.76.0.0601650711045.issue29973@psf.upfronthosting.co.za>


STINNER Victor added the comment:

https://pypi.org/project/Sphinx/1.5.5/ has been released. How can I schedule a recheck on Travis CI on PRs where the docs job failed?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29973>
_______________________________________

From report at bugs.python.org  Mon Apr  3 12:13:56 2017
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 03 Apr 2017 16:13:56 +0000
Subject: [docs] [issue29973] Travis CI docs broken: UnboundLocalError: local
 variable 'prefix' referenced before assignment
In-Reply-To: <1491233654.37.0.108307382934.issue29973@psf.upfronthosting.co.za>
Message-ID: <1491236036.96.0.989795007993.issue29973@psf.upfronthosting.co.za>


STINNER Victor added the comment:

Oh, Zachary Were "restarted the docs job on most of the blocked PRs". So I close this issue.

That one was hopefully quickly fixed :-)

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29973>
_______________________________________

From report at bugs.python.org  Mon Apr  3 13:32:43 2017
From: report at bugs.python.org (Mathias Rav)
Date: Mon, 03 Apr 2017 17:32:43 +0000
Subject: [docs] [issue29974] typing.TYPE_CHECKING doc example is incorrect
Message-ID: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>


New submission from Mathias Rav:

The documentation of typing.TYPE_CHECKING has an example (introduced in issue #26141) that would lead to NameError at runtime. The example shows how to limit the import of "expensive_mod" to type checkers, but then goes on to use "expensive_mod.some_type" in a type annotation that is evaluated at runtime ("local_var: expensive_mod.some_type"). The use case of TYPE_CHECKING is probably meant for type annotations placed in comments, e.g. "local_var  # type: expensive_mod.some_type".

----------
assignee: docs at python
components: Documentation
messages: 291085
nosy: docs at python, rav
priority: normal
severity: normal
status: open
title: typing.TYPE_CHECKING doc example is incorrect
type: enhancement
versions: Python 3.4, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Mon Apr  3 13:33:16 2017
From: report at bugs.python.org (Mathias Rav)
Date: Mon, 03 Apr 2017 17:33:16 +0000
Subject: [docs] [issue29974] typing.TYPE_CHECKING doc example is incorrect
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1491240796.54.0.26743553687.issue29974@psf.upfronthosting.co.za>


Changes by Mathias Rav <mathiasrav at gmail.com>:


----------
pull_requests: +1155

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Mon Apr  3 19:25:10 2017
From: report at bugs.python.org (R. David Murray)
Date: Mon, 03 Apr 2017 23:25:10 +0000
Subject: [docs] [issue29968] Document that no characters are allowed to
 proceed \ in explicit line joining
In-Reply-To: <1491223765.12.0.65807116216.issue29968@psf.upfronthosting.co.za>
Message-ID: <1491261910.66.0.0873196552603.issue29968@psf.upfronthosting.co.za>


R. David Murray added the comment:

I think you meant "the language reference" rather than "the devguide".  The sentence about the comment is redundant with the preceding line that says that the thing that results in a join is a physical line that ends with a backslash ("that is not part of..."), which is a definitive statement that no characters may follow it.

So, I don't see any doc bug here, unless we want to delete that redundant statement about the comment because it is confusing.  But I doubt we want to do that, as some people will think that a comment is "the same as there being nothing" (despite the statement about "physical line") which it is not.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29968>
_______________________________________

From report at bugs.python.org  Mon Apr  3 19:26:03 2017
From: report at bugs.python.org (R. David Murray)
Date: Mon, 03 Apr 2017 23:26:03 +0000
Subject: [docs] [issue29968] Document that no characters are allowed to
 proceed \ in explicit line joining
In-Reply-To: <1491223765.12.0.65807116216.issue29968@psf.upfronthosting.co.za>
Message-ID: <1491261963.48.0.70953147055.issue29968@psf.upfronthosting.co.za>


R. David Murray added the comment:

I also have no idea what your comment about stripping white space is in reference to ;)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29968>
_______________________________________

From report at bugs.python.org  Mon Apr  3 21:36:23 2017
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 04 Apr 2017 01:36:23 +0000
Subject: [docs] [issue29974] typing.TYPE_CHECKING doc example is incorrect
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1491269783.49.0.293068909434.issue29974@psf.upfronthosting.co.za>


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


----------
stage:  -> patch review
type: enhancement -> behavior
versions:  -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Mon Apr  3 22:32:59 2017
From: report at bugs.python.org (Martin Panter)
Date: Tue, 04 Apr 2017 02:32:59 +0000
Subject: [docs] [issue29968] Document that no characters are allowed to
 proceed \ in explicit line joining
In-Reply-To: <1491223765.12.0.65807116216.issue29968@psf.upfronthosting.co.za>
Message-ID: <1491273179.08.0.850128458022.issue29968@psf.upfronthosting.co.za>


Martin Panter added the comment:

I think he means make something like the following legal, where dots (.) indicate space characters:

a.=.\.
....b

At the moment it is a SyntaxError:

>>> a = \ 
  File "<stdin>", line 1
    a = \ 
         ^
SyntaxError: unexpected character after line continuation character

I don?t think it is worthwhile changing that.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29968>
_______________________________________

From report at bugs.python.org  Mon Apr  3 22:36:41 2017
From: report at bugs.python.org (Namjun Kim)
Date: Tue, 04 Apr 2017 02:36:41 +0000
Subject: [docs] [issue29975] Issue in extending documentation
Message-ID: <1491273401.15.0.69165837027.issue29975@psf.upfronthosting.co.za>


New submission from Namjun Kim:

https://docs.python.org/3.7/extending/extending.html

"Should it become a dangling pointer, C code which raises the exception could cause a core dump or other unintended side effects."

The typo error in this sentence.

"If it become a dangling pointer, C code which raises the exception could cause a core dump or other unintended side effects."

fix the typo error.

----------
assignee: docs at python
components: Documentation
messages: 291098
nosy: Namjun Kim, docs at python
priority: normal
severity: normal
status: open
title: Issue in extending documentation
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29975>
_______________________________________

From report at bugs.python.org  Mon Apr  3 23:12:35 2017
From: report at bugs.python.org (Martin Panter)
Date: Tue, 04 Apr 2017 03:12:35 +0000
Subject: [docs] [issue29975] Issue in extending documentation
In-Reply-To: <1491273401.15.0.69165837027.issue29975@psf.upfronthosting.co.za>
Message-ID: <1491275555.14.0.520609541028.issue29975@psf.upfronthosting.co.za>


Martin Panter added the comment:

FWIW I don?t see any error in the first quote. ?Should X happen, Y happens? is valid English. Though I admit this kind of grammar is not used that often.

If it is too hard to understand, it should be okay to change it to ?If it becomes a danging pointer, . . .?.

[become ? becomes]

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29975>
_______________________________________

From report at bugs.python.org  Tue Apr  4 00:15:21 2017
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 04 Apr 2017 04:15:21 +0000
Subject: [docs] [issue29975] Issue in extending documentation
In-Reply-To: <1491273401.15.0.69165837027.issue29975@psf.upfronthosting.co.za>
Message-ID: <1491279321.95.0.187503469864.issue29975@psf.upfronthosting.co.za>


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


----------
pull_requests: +1156

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29975>
_______________________________________

From report at bugs.python.org  Tue Apr  4 00:56:37 2017
From: report at bugs.python.org (Jelle Zijlstra)
Date: Tue, 04 Apr 2017 04:56:37 +0000
Subject: [docs] [issue29974] typing.TYPE_CHECKING doc example is incorrect
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1491281797.12.0.0022375223878.issue29974@psf.upfronthosting.co.za>


Jelle Zijlstra added the comment:

The example is actually correct; I just confirmed by running it in my shell. Type annotations on local variables are not evaluated at runtime; see PEP 526.

----------
nosy: +Jelle Zijlstra

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Tue Apr  4 01:15:09 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Tue, 04 Apr 2017 05:15:09 +0000
Subject: [docs] [issue29725] sqlite3.Cursor doesn't properly document
 "arraysize"
In-Reply-To: <1488732449.69.0.822466282685.issue29725@psf.upfronthosting.co.za>
Message-ID: <1491282909.72.0.632086850238.issue29725@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:

Thanks for working on this.

row_factory seems to be another parameter that can be set in the Cursor object. https://github.com/python/cpython/blob/master/Modules/_sqlite/cursor.c#L65 

This can addressed in a different issue/ pr.

----------
nosy: +orsenthil

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29725>
_______________________________________

From report at bugs.python.org  Tue Apr  4 01:16:16 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Tue, 04 Apr 2017 05:16:16 +0000
Subject: [docs] [issue29725] sqlite3.Cursor doesn't properly document
 "arraysize"
In-Reply-To: <1488732449.69.0.822466282685.issue29725@psf.upfronthosting.co.za>
Message-ID: <1491282976.24.0.797407406525.issue29725@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:


New changeset 02e12138000da834f23719521a011fa93763384d by Senthil Kumaran (csabella) in branch 'master':
bpo-29725: DOC: add text for arraysize in sqlite3.Cursor (#947)
https://github.com/python/cpython/commit/02e12138000da834f23719521a011fa93763384d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29725>
_______________________________________

From report at bugs.python.org  Tue Apr  4 01:21:22 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Tue, 04 Apr 2017 05:21:22 +0000
Subject: [docs] [issue29725] sqlite3.Cursor doesn't properly document
 "arraysize"
In-Reply-To: <1488732449.69.0.822466282685.issue29725@psf.upfronthosting.co.za>
Message-ID: <1491283281.99.0.601808696993.issue29725@psf.upfronthosting.co.za>


Changes by Senthil Kumaran <senthil at uthcode.com>:


----------
pull_requests: +1157

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29725>
_______________________________________

From report at bugs.python.org  Tue Apr  4 01:21:26 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Tue, 04 Apr 2017 05:21:26 +0000
Subject: [docs] [issue29725] sqlite3.Cursor doesn't properly document
 "arraysize"
In-Reply-To: <1488732449.69.0.822466282685.issue29725@psf.upfronthosting.co.za>
Message-ID: <1491283286.04.0.646466334247.issue29725@psf.upfronthosting.co.za>


Changes by Senthil Kumaran <senthil at uthcode.com>:


----------
pull_requests: +1158

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29725>
_______________________________________

From report at bugs.python.org  Tue Apr  4 01:27:17 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Tue, 04 Apr 2017 05:27:17 +0000
Subject: [docs] [issue29725] sqlite3.Cursor doesn't properly document
 "arraysize"
In-Reply-To: <1488732449.69.0.822466282685.issue29725@psf.upfronthosting.co.za>
Message-ID: <1491283637.51.0.668888492095.issue29725@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:


New changeset cb1e002c07622e027e80a3843d27a623d1617430 by Senthil Kumaran in branch '3.6':
bpo-29725: DOC: add text for arraysize in sqlite3.Cursor (#947) (#985)
https://github.com/python/cpython/commit/cb1e002c07622e027e80a3843d27a623d1617430


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29725>
_______________________________________

From report at bugs.python.org  Tue Apr  4 01:28:25 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Tue, 04 Apr 2017 05:28:25 +0000
Subject: [docs] [issue29725] sqlite3.Cursor doesn't properly document
 "arraysize"
In-Reply-To: <1488732449.69.0.822466282685.issue29725@psf.upfronthosting.co.za>
Message-ID: <1491283705.91.0.629569381913.issue29725@psf.upfronthosting.co.za>


Senthil Kumaran added the comment:


New changeset 0f9ceaf322cc9358373167115fd4c21ab2d9ad50 by Senthil Kumaran in branch '3.5':
bpo-29725: DOC: add text for arraysize in sqlite3.Cursor (#947) (#986)
https://github.com/python/cpython/commit/0f9ceaf322cc9358373167115fd4c21ab2d9ad50


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29725>
_______________________________________

From report at bugs.python.org  Tue Apr  4 01:29:07 2017
From: report at bugs.python.org (Senthil Kumaran)
Date: Tue, 04 Apr 2017 05:29:07 +0000
Subject: [docs] [issue29725] sqlite3.Cursor doesn't properly document
 "arraysize"
In-Reply-To: <1488732449.69.0.822466282685.issue29725@psf.upfronthosting.co.za>
Message-ID: <1491283747.05.0.243204990901.issue29725@psf.upfronthosting.co.za>


Changes by Senthil Kumaran <senthil at uthcode.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29725>
_______________________________________

From report at bugs.python.org  Tue Apr  4 02:30:34 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 04 Apr 2017 06:30:34 +0000
Subject: [docs] [issue19180] some RFC references could be updated
In-Reply-To: <525144B9.3040305@python.org>
Message-ID: <1491287434.27.0.0380380010696.issue19180@psf.upfronthosting.co.za>


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


----------
nosy: +christian.heimes
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19180>
_______________________________________

From report at bugs.python.org  Tue Apr  4 03:22:44 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Tue, 04 Apr 2017 07:22:44 +0000
Subject: [docs] [issue29968] Document that no characters are allowed to
 proceed \ in explicit line joining
In-Reply-To: <1491223765.12.0.65807116216.issue29968@psf.upfronthosting.co.za>
Message-ID: <1491290564.47.0.779824892862.issue29968@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

Ah, yes, the Ref. Manual, not the devguide, silly mistake.

It definitely isn't a documentation bug (the documentation doesn't state something wrong) as much as I think it might be a slight omission. I really wasn't aware of how strict the tokenizer is with any characters after `\`.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29968>
_______________________________________

From report at bugs.python.org  Tue Apr  4 08:11:01 2017
From: report at bugs.python.org (Mathias Rav)
Date: Tue, 04 Apr 2017 12:11:01 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1491307861.89.0.753506314904.issue29974@psf.upfronthosting.co.za>


Changes by Mathias Rav <mathiasrav at gmail.com>:


----------
title: typing.TYPE_CHECKING doc example is incorrect -> Change typing.TYPE_CHECKING doc example

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Tue Apr  4 08:13:36 2017
From: report at bugs.python.org (Mathias Rav)
Date: Tue, 04 Apr 2017 12:13:36 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1491308016.83.0.00748743784017.issue29974@psf.upfronthosting.co.za>


Mathias Rav added the comment:

I have updated the patch after feedback from Jelle Zijlstra and Ivan Levkevskyi. Indeed the example was correct; the patch now adds wording from PEP 484 and PEP 526 to clarify why a function parameter annotation needs to be in quotes and a local variable annotation does not.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Tue Apr  4 10:25:53 2017
From: report at bugs.python.org (R. David Murray)
Date: Tue, 04 Apr 2017 14:25:53 +0000
Subject: [docs] [issue29968] Document that no characters are allowed to
 proceed \ in explicit line joining
In-Reply-To: <1491223765.12.0.65807116216.issue29968@psf.upfronthosting.co.za>
Message-ID: <1491315953.32.0.979691245057.issue29968@psf.upfronthosting.co.za>


R. David Murray added the comment:

I don't see any omission, myself.  Keep in mind that the language reference is as much or more of a specification as it is a reference, so we tend to try to use the minimum language that precisely describes the expected behavior. Which is why I suggested that if anything the sentence about trailing comments should be dropped :)  

And I would vote -1 on allowing trailing whitespace.  (More than -1, actually :)  If that's what you meant: you said "proceed \", which doesn't sound like *trailing* whitespace.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29968>
_______________________________________

From report at bugs.python.org  Tue Apr  4 13:44:01 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Tue, 04 Apr 2017 17:44:01 +0000
Subject: [docs] [issue29968] Document that no characters are allowed to
 proceed \ in explicit line joining
In-Reply-To: <1491223765.12.0.65807116216.issue29968@psf.upfronthosting.co.za>
Message-ID: <1491327841.32.0.440700351768.issue29968@psf.upfronthosting.co.za>


Jim Fasarakis-Hilliard added the comment:

Gotcha, thanks for the input, David. I'll leave it to you to decide if the sentence on the trailing comments warrants removal.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29968>
_______________________________________

From report at bugs.python.org  Tue Apr  4 14:01:11 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 04 Apr 2017 18:01:11 +0000
Subject: [docs] [issue29981] Update Index set, dict,
 and generator 'comprehensions'
Message-ID: <1491328871.52.0.864348862414.issue29981@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

The index currently has

comprehensions
   *list*

with *list* linked to 6.2.5 List displays.  I suggest:

1. Link *comprehensions* to 6.2.4. Displays for lists, sets and dictionaries
2. Add subentries *set*, *dict*, and *generator* linked to
2a. 6.2.6. Set displays
2b. 6.2.7. Dictionary displays
2c. 6.2.8. Generator expressions

We don't *call* generator expressions 'generator comprehensions', but that is what they are syntactically and one looking for 'comprehensions' should be able to find them there.

There is already

*list*
   ...
   *comprehensions*
   ...
*list comprehensions*

with 'list' and 'list comprehensions' linked to glossary entries, while 'list, comprehensions' links to the same section as 'comprehensions, list'.  

3. Add 'set/dictionary, comprehensions' sub-entries linked like 'list, com
4. Add Glossary entries and links like 'list comprehensions'

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 291129
nosy: docs at python, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Update Index set, dict, and generator 'comprehensions'
type: behavior
versions: Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29981>
_______________________________________

From report at bugs.python.org  Tue Apr  4 14:31:12 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 04 Apr 2017 18:31:12 +0000
Subject: [docs] [issue29983] Reference TOC: expand 'Atoms' and 'Primaries'
Message-ID: <1491330672.66.0.700114037172.issue29983@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

Today there is a fairly long python-list thread about the difficult of finding info on 'dict comprehensions' in the doc.  Point 1 is missing index entries.  I opened #29981 for this.  Point 2 is something I have also noticed: the obscurity of 'Atoms' and 'Primaries' as titles of sections in the Expressions chapter.  These are fairly esoteric Computer Science language theory terms.  Compare these to beginner-friendly 'Binary arithmetic operators' and 'Comparisons'.

My specific suggestions, subject to change:

Atoms, including identifiers, literals, displays, and comprehensions
Primaries: attributes, subscripts, slices, and calls

----------
assignee: docs at python
components: Documentation
messages: 291131
nosy: docs at python, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Reference TOC: expand 'Atoms' and 'Primaries'
type: enhancement
versions: Python 2.7, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29983>
_______________________________________

From report at bugs.python.org  Tue Apr  4 14:33:04 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 04 Apr 2017 18:33:04 +0000
Subject: [docs] [issue29981] Update Index for set, dict,
 and generator 'comprehensions'
In-Reply-To: <1491328871.52.0.864348862414.issue29981@psf.upfronthosting.co.za>
Message-ID: <1491330784.8.0.20606906074.issue29981@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

See #29983 for expanding the title of the 'atoms' section containing subsections on comprehensions.

----------
title: Update Index set, dict, and generator 'comprehensions' -> Update Index for set, dict, and generator 'comprehensions'

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29981>
_______________________________________

From report at bugs.python.org  Tue Apr  4 14:45:31 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 04 Apr 2017 18:45:31 +0000
Subject: [docs] [issue29983] Reference TOC: expand 'Atoms' and 'Primaries'
In-Reply-To: <1491330672.66.0.700114037172.issue29983@psf.upfronthosting.co.za>
Message-ID: <1491331531.15.0.594550293422.issue29983@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

'displays' is partly redundant with 'comprehensions'.  Since many think of other 'displays' as a type of literal, leave 'displays' out.  They are well indexed.  I think the most likely term people have trouble finding in the TOC is 'comprehension'.  It was not immediately obvious to most that should be 'atoms'.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29983>
_______________________________________

From report at bugs.python.org  Tue Apr  4 15:38:26 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Tue, 04 Apr 2017 19:38:26 +0000
Subject: [docs] [issue28681] About function renaming in the tutorial
In-Reply-To: <1479008196.92.0.673244295473.issue28681@psf.upfronthosting.co.za>
Message-ID: <1491334706.12.0.441145316007.issue28681@psf.upfronthosting.co.za>


Changes by Jim Fasarakis-Hilliard <d.f.hilliard at gmail.com>:


----------
nosy: +Jim Fasarakis-Hilliard

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28681>
_______________________________________

From report at bugs.python.org  Tue Apr  4 17:43:17 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Tue, 04 Apr 2017 21:43:17 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491342197.63.0.823678123047.issue29947@psf.upfronthosting.co.za>


Dominic Mayers added the comment:

I simplified the patch. Using a class as a factory function is the simplest case, so I took advantage of this. I also give one way to pass extra parameters to the handler in the factory function, because it's the main reason why we cannot always use a class.

----------
Added file: http://bugs.python.org/file46774/Issue29947_for_discussion_02.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Tue Apr  4 17:45:15 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Tue, 04 Apr 2017 21:45:15 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491342315.77.0.0441739502967.issue29947@psf.upfronthosting.co.za>


Changes by Dominic Mayers <dominic_mayers at yahoo.com>:


Removed file: http://bugs.python.org/file46770/Issue29947_for_discussion.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Tue Apr  4 18:41:14 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Tue, 04 Apr 2017 22:41:14 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491345674.08.0.77107137804.issue29947@psf.upfronthosting.co.za>


Changes by Dominic Mayers <dominic_mayers at yahoo.com>:


Removed file: http://bugs.python.org/file46774/Issue29947_for_discussion_02.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Tue Apr  4 18:41:29 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Tue, 04 Apr 2017 22:41:29 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491345689.98.0.717582001415.issue29947@psf.upfronthosting.co.za>


Changes by Dominic Mayers <dominic_mayers at yahoo.com>:


Added file: http://bugs.python.org/file46775/Issue29947_for_discussion_03.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Tue Apr  4 18:51:54 2017
From: report at bugs.python.org (Devin Jeanpierre)
Date: Tue, 04 Apr 2017 22:51:54 +0000
Subject: [docs] [issue29986] Documentation recommends raising TypeError from
 tp_richcompare
Message-ID: <1491346313.99.0.131506773991.issue29986@psf.upfronthosting.co.za>


New submission from Devin Jeanpierre:

am not sure when TypeError is the right choice. Definitely, most of the time I've seen it done, it causes trouble, and NotImplemented usually does something better.

For example, see the work in https://bugs.python.org/issue8743 to get set to interoperate correctly with other set-like classes --- a problem caused by the use of TypeError instead of returning NotImplemented (e.g. https://hg.python.org/cpython/rev/3615cdb3b86d).

This advice seems to conflict with the usual and expected behavior of objects from Python: e.g. object().__lt__(1) returns NotImplemented rather than raising TypeError, despite < not "making sense" for object. Similarly for file objects and other uncomparable classes. Even complex numbers only return NotImplemented!


>>> 1j.__lt__(1j)
NotImplemented


If this note should be kept, this section could use a decent explanation of the difference between "undefined" (should return NotImplemented) and "nonsensical" (should apparently raise TypeError). Perhaps a reference to an example from the stdlib.

----------
assignee: docs at python
components: Documentation
messages: 291144
nosy: Devin Jeanpierre, docs at python
priority: normal
pull_requests: 1167
severity: normal
status: open
title: Documentation recommends raising TypeError from tp_richcompare

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29986>
_______________________________________

From report at bugs.python.org  Tue Apr  4 19:01:22 2017
From: report at bugs.python.org (Devin Jeanpierre)
Date: Tue, 04 Apr 2017 23:01:22 +0000
Subject: [docs] [issue29986] Documentation recommends raising TypeError from
 tp_richcompare
In-Reply-To: <1491346313.99.0.131506773991.issue29986@psf.upfronthosting.co.za>
Message-ID: <1491346882.65.0.198052312144.issue29986@psf.upfronthosting.co.za>


Devin Jeanpierre added the comment:

Sorry, forgot to link to docs because I was copy-pasting from the PR:

https://docs.python.org/2/c-api/typeobj.html#c.PyTypeObject.tp_richcompare

https://docs.python.org/3/c-api/typeobj.html#c.PyTypeObject.tp_richcompare

> Note: If you want to implement a type for which only a limited set of comparisons makes sense (e.g. == and !=, but not < and friends), directly raise TypeError in the rich comparison function.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29986>
_______________________________________

From report at bugs.python.org  Tue Apr  4 19:32:04 2017
From: report at bugs.python.org (R. David Murray)
Date: Tue, 04 Apr 2017 23:32:04 +0000
Subject: [docs] [issue29986] Documentation recommends raising TypeError from
 tp_richcompare
In-Reply-To: <1491346313.99.0.131506773991.issue29986@psf.upfronthosting.co.za>
Message-ID: <1491348723.99.0.753020484877.issue29986@psf.upfronthosting.co.za>


R. David Murray added the comment:

The documentation is technically correct, as far as I can see.  Issue 8743 is not about disallowing certain comparison operations, but rather incorrectly implementing the earlier sentence in that same doc section: "If the comparison is undefined, it must return Py_NotImplemented".  Perhaps the wording should be changed so that instead of saying "only a limited set of comparisons makes sense" it says "if you wish to disallow certain comparison operations while allowing others".  It should also probably be demoted from being a '.. note', since it is, as you note, an exceptional case, not a common one.

But you might be right that it would be better to delete it altogether, since it is generally better to let the comparison machinery raise the error if none of the types implements the comparison...what would be the rationale for a blanket *dis*allowing of a particular comparison operation?  

Let's see what Raymond thinks.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29986>
_______________________________________

From report at bugs.python.org  Tue Apr  4 20:15:20 2017
From: report at bugs.python.org (Devin Jeanpierre)
Date: Wed, 05 Apr 2017 00:15:20 +0000
Subject: [docs] [issue29986] Documentation recommends raising TypeError from
 tp_richcompare
In-Reply-To: <1491346313.99.0.131506773991.issue29986@psf.upfronthosting.co.za>
Message-ID: <1491351320.7.0.708286063549.issue29986@psf.upfronthosting.co.za>


Devin Jeanpierre added the comment:

Yeah, I agree there might be a use-case (can't find one offhand, but in principle), but I think it's rare enough that you're more likely to be led astray from reading this note -- almost always, NotImplemented does what you want.

In a way this is a special case of being able to raise an exception at all, which is mentioned earlier ("if another error occurred it must return NULL and set an exception condition.")

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29986>
_______________________________________

From report at bugs.python.org  Wed Apr  5 00:35:34 2017
From: report at bugs.python.org (Louie Lu)
Date: Wed, 05 Apr 2017 04:35:34 +0000
Subject: [docs] [issue29981] Update Index for set, dict,
 and generator 'comprehensions'
In-Reply-To: <1491328871.52.0.864348862414.issue29981@psf.upfronthosting.co.za>
Message-ID: <1491366934.32.0.745768004691.issue29981@psf.upfronthosting.co.za>


Changes by Louie Lu <me at louie.lu>:


----------
nosy: +louielu

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29981>
_______________________________________

From report at bugs.python.org  Wed Apr  5 01:08:07 2017
From: report at bugs.python.org (Louie Lu)
Date: Wed, 05 Apr 2017 05:08:07 +0000
Subject: [docs] [issue29981] Update Index for set, dict,
 and generator 'comprehensions'
In-Reply-To: <1491328871.52.0.864348862414.issue29981@psf.upfronthosting.co.za>
Message-ID: <1491368887.5.0.378526127456.issue29981@psf.upfronthosting.co.za>


Changes by Louie Lu <me at louie.lu>:


----------
pull_requests: +1170

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29981>
_______________________________________

From report at bugs.python.org  Wed Apr  5 07:00:54 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 05 Apr 2017 11:00:54 +0000
Subject: [docs] [issue28415] PyUnicode_FromFormat integer format handling
 different from printf about zeropad
In-Reply-To: <1476176180.11.0.398413685253.issue28415@psf.upfronthosting.co.za>
Message-ID: <1491390054.02.0.257695704014.issue28415@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

(Response to what I believe is latest patch.)  In msg278666, my two suggestions were 'either...or', not both.  The list came from Antti's msg278528, but the correct list for Python appears to be different, and different for bytes and unicode.  When I made the suggestion, I did not realize that 'exactly' was repeated for each conversion type in a table.  As a note, I think the following might work. "For <list of> conversion types, the 0-conversion flag has effect even when a precision is given."

I also think that 'exactly could be dropped when it is not exactly true.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28415>
_______________________________________

From report at bugs.python.org  Wed Apr  5 11:13:01 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Wed, 05 Apr 2017 15:13:01 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491405181.56.0.419300396161.issue29947@psf.upfronthosting.co.za>


Dominic Mayers added the comment:

An improved version of the patch, I hope. I will remove the old patch, because it's really does not help to see the old versions.

----------
Added file: http://bugs.python.org/file46781/Issue29947_for_discussion_04.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Wed Apr  5 11:13:24 2017
From: report at bugs.python.org (Dominic Mayers)
Date: Wed, 05 Apr 2017 15:13:24 +0000
Subject: [docs] [issue29947] In SocketServer,
 why not passing a factory instance for the RequestHandlerClass
 instead of the class itself?
In-Reply-To: <1490875733.83.0.750732897079.issue29947@psf.upfronthosting.co.za>
Message-ID: <1491405204.68.0.844282465172.issue29947@psf.upfronthosting.co.za>


Changes by Dominic Mayers <dominic_mayers at yahoo.com>:


Removed file: http://bugs.python.org/file46775/Issue29947_for_discussion_03.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29947>
_______________________________________

From report at bugs.python.org  Wed Apr  5 14:46:35 2017
From: report at bugs.python.org (Arthur Goldberg)
Date: Wed, 05 Apr 2017 18:46:35 +0000
Subject: [docs] [issue29997] Suggested changes for
 https://docs.python.org/3.6/extending/extending.html
Message-ID: <1491417995.71.0.832434605196.issue29997@psf.upfronthosting.co.za>


New submission from Arthur Goldberg:

I've just taught myself how to write C extensions to Python with https://docs.python.org/3.6/extending/extending.html. I think it's quite good.

Nevertheless, I've some suggested improvements. These all use the vi s/// replacement syntax.

Ambiguous 'it':
s/If the latter header file does not exist on your system, it declares the functions malloc(), free() and realloc() directly./If the latter header file does not exist on your system, Python.h declares the functions malloc(), free() and realloc() directly./

Unclear, as 'The C function' refers to the specific example, whereas 'always has' implies that this applies to all calls from Python to C:
s/The C function always has two arguments, conventionally/A C function called by Python always has two arguments, conventionally/

In 
PyMODINIT_FUNC
PyInit_spam(void)
{
    PyObject *m;

    m = PyModule_Create(&spammodule);
    if (m == NULL)
        return NULL;

    SpamError = PyErr_NewException("spam.error", NULL, NULL);
    Py_INCREF(SpamError);
    PyModule_AddObject(m, "error", SpamError);
    return m;
}

remove
    m = PyModule_Create(&spammodule);
    if (m == NULL)
        return NULL;
and replace it with
    
    ...
    
because it won't compile because spammodule has not been described yet on the page.

Self-contradictory: 'normally always' is an oxymoron. 
s/It should normally always be METH_VARARGS or METH_VARARGS | METH_KEYWORDS; a value of 0 means that an obsolete variant of PyArg_ParseTuple() is used./It should always be METH_VARARGS or METH_VARARGS | METH_KEYWORDS; however, legacy code may use 0, which indicates that an obsolete variant of PyArg_ParseTuple() is being used./

Incomplete: this comment doesn't contain a complete thought
s/module documentation, may be NULL/pointer to a string containing the module's documentation, or NULL if none is provided/

Provide hyperlink: for user convenience, add a hyperlink to 'Modules/xxmodule.c'
s/included in the Python source distribution as Modules/xxmodule.c/included in the Python source distribution as Modules/xxmodule.c/

Incomplete: It would be good to lead programmers towards the easiest approach. 
s/ If you use dynamic loading,/<new paragraph> If you can use dynamic loading, the the easiest approach is to use Python's distutils module to build your module. If you use dynamic loading,/

----------
assignee: docs at python
components: Documentation
messages: 291192
nosy: ArthurGoldberg, docs at python
priority: normal
severity: normal
status: open
title: Suggested changes for https://docs.python.org/3.6/extending/extending.html
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29997>
_______________________________________

From report at bugs.python.org  Wed Apr  5 15:52:21 2017
From: report at bugs.python.org (Arthur Goldberg)
Date: Wed, 05 Apr 2017 19:52:21 +0000
Subject: [docs] [issue29997] Suggested changes for
 https://docs.python.org/3.6/extending/extending.html
In-Reply-To: <1491417995.71.0.832434605196.issue29997@psf.upfronthosting.co.za>
Message-ID: <1491421941.58.0.657837531516.issue29997@psf.upfronthosting.co.za>


Arthur Goldberg added the comment:

Also, 

Incorrect number agreement:
s/strategy that minimizes this kind of errors/strategy that minimizes this kind of error/

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29997>
_______________________________________

From report at bugs.python.org  Wed Apr  5 16:07:15 2017
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Wed, 05 Apr 2017 20:07:15 +0000
Subject: [docs] [issue29997] Suggested changes for
 https://docs.python.org/3.6/extending/extending.html
In-Reply-To: <1491417995.71.0.832434605196.issue29997@psf.upfronthosting.co.za>
Message-ID: <1491422835.32.0.794908660985.issue29997@psf.upfronthosting.co.za>


Changes by Fred L. Drake, Jr. <fdrake at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29997>
_______________________________________

From report at bugs.python.org  Wed Apr  5 20:50:50 2017
From: report at bugs.python.org (AJ Jordan)
Date: Thu, 06 Apr 2017 00:50:50 +0000
Subject: [docs] [issue30001] CPython contribution docs reference missing
 /issuetracker page
Message-ID: <1491439850.02.0.465996386955.issue30001@psf.upfronthosting.co.za>


New submission from AJ Jordan:

https://cpython-devguide.readthedocs.io/pullrequest.html#licensing (and presumably other pages in this project) references https://cpython-devguide.readthedocs.io/issuetracker, but this page returns 404 Not Found.

----------
assignee: docs at python
components: Documentation
messages: 291202
nosy: docs at python, strugee
priority: normal
severity: normal
status: open
title: CPython contribution docs reference missing /issuetracker page

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30001>
_______________________________________

From report at bugs.python.org  Wed Apr  5 22:29:36 2017
From: report at bugs.python.org (Arthur Goldberg)
Date: Thu, 06 Apr 2017 02:29:36 +0000
Subject: [docs] [issue30002] Minor change to
 https://docs.python.org/3.6/extending/building.html
Message-ID: <1491445776.09.0.388961752083.issue30002@psf.upfronthosting.co.za>


New submission from Arthur Goldberg:

The core example on this page starts:

from distutils.core import setup, Extension

module1 = Extension('demo',
                    sources = ['demo.c'])

...

I suggest that 'sources = ['demo.c']' be changed to 'sources = ['demomodule.c']', because this would make the example consistent with https://docs.python.org/3.6/extending/extending.html which says: "Begin by creating a file spammodule.c. (Historically, if a module is called spam, the C file containing its implementation is called spammodule.c; ... )"
This minor change may help encourage this standard practice.

Arthur

----------
assignee: docs at python
components: Documentation
messages: 291203
nosy: ArthurGoldberg, docs at python
priority: normal
severity: normal
status: open
title: Minor change to https://docs.python.org/3.6/extending/building.html
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30002>
_______________________________________

From report at bugs.python.org  Wed Apr  5 22:43:59 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 06 Apr 2017 02:43:59 +0000
Subject: [docs] [issue30002] Minor change to
 https://docs.python.org/3.6/extending/building.html
In-Reply-To: <1491445776.09.0.388961752083.issue30002@psf.upfronthosting.co.za>
Message-ID: <1491446639.74.0.287387931993.issue30002@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

I'm not really sure that is a standard or even a best practice.  I think some people do it and some don't.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30002>
_______________________________________

From report at bugs.python.org  Wed Apr  5 23:36:12 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 06 Apr 2017 03:36:12 +0000
Subject: [docs] [issue30001] CPython contribution docs reference missing
 /issuetracker page
In-Reply-To: <1491439850.02.0.465996386955.issue30001@psf.upfronthosting.co.za>
Message-ID: <1491449772.23.0.963305506416.issue30001@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks for the report, Alex.

The issue tracker for the devguide is at https://github.com/python/devguide

Do you mind filling the issue there?
I'm closing this since this tracks only issues for CPython.
Thanks :)

----------
nosy: +Mariatta
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30001>
_______________________________________

From report at bugs.python.org  Thu Apr  6 00:40:42 2017
From: report at bugs.python.org (Cristian Barbarosie)
Date: Thu, 06 Apr 2017 04:40:42 +0000
Subject: [docs] [issue30004] in regex-howto, improve example on grouping
Message-ID: <1491453642.54.0.802330198745.issue30004@psf.upfronthosting.co.za>


New submission from Cristian Barbarosie:

In the Regular Expression HOWTO
https://docs.python.org/3.6/howto/regex.html#regex-howto
the last example in the "Grouping" section has a bug. The code is supposed to find repeated words, but it catches false repetitions.

>>> p = re.compile(r'(\b\w+)\s+\1')
>>> p.search('Paris in the the spring').group()
'the the'
>>> p.search('k is the thermal coefficient').group()
'the the'

I propose adding a \b after \1, this solves the problem :

>>> p = re.compile(r'(\b\w+)\s+\1\b')
>>> p.search('Paris in the the spring').group()
'the the'
>>> print p.search('k is the thermal coefficient')
None

----------
assignee: docs at python
components: Documentation
messages: 291209
nosy: Cristian Barbarosie, docs at python
priority: normal
severity: normal
status: open
title: in regex-howto, improve example on grouping
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30004>
_______________________________________

From report at bugs.python.org  Thu Apr  6 01:16:16 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 06 Apr 2017 05:16:16 +0000
Subject: [docs] [issue30004] in regex-howto, improve example on grouping
In-Reply-To: <1491453642.54.0.802330198745.issue30004@psf.upfronthosting.co.za>
Message-ID: <1491455776.45.0.618116935602.issue30004@psf.upfronthosting.co.za>


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


----------
nosy: +akuchling

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30004>
_______________________________________

From report at bugs.python.org  Thu Apr  6 10:00:26 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 06 Apr 2017 14:00:26 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491487226.26.0.154991416479.issue19225@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset 2cfe583ac8d3eaa98e3d2aca597577ce4787ca20 by Serhiy Storchaka (cocoatomo) in branch '3.5':
[3.5] bpo-19225: Lack of c api exceptions doc (#965)
https://github.com/python/cpython/commit/2cfe583ac8d3eaa98e3d2aca597577ce4787ca20


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Thu Apr  6 10:22:28 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 06 Apr 2017 14:22:28 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491488548.0.0.0576164416152.issue19225@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Sorry, but I just found that warning categories are enumerated near the documentation of PyErr_WarnEx(). I think that that enumeration is no longer needed and can be removed.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Thu Apr  6 13:01:14 2017
From: report at bugs.python.org (Alex Jordan)
Date: Thu, 06 Apr 2017 17:01:14 +0000
Subject: [docs] [issue30001] CPython contribution docs reference missing
 /issuetracker page
In-Reply-To: <1491439850.02.0.465996386955.issue30001@psf.upfronthosting.co.za>
Message-ID: <1491498074.05.0.10955529986.issue30001@psf.upfronthosting.co.za>


Alex Jordan added the comment:

Filed https://github.com/python/devguide/issues/156.

Sorry for the noise! I just assumed everything went through bpo. Guess not :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30001>
_______________________________________

From report at bugs.python.org  Thu Apr  6 16:57:53 2017
From: report at bugs.python.org (Cristian Barbarosie)
Date: Thu, 06 Apr 2017 20:57:53 +0000
Subject: [docs] [issue30004] in regex-howto, improve example on grouping
In-Reply-To: <1491453642.54.0.802330198745.issue30004@psf.upfronthosting.co.za>
Message-ID: <1491512273.49.0.387945928937.issue30004@psf.upfronthosting.co.za>


Cristian Barbarosie added the comment:

Just discovered that a nearly identical example is presented in the end of section "Non-capturing and Named Groups". My proposal applies to this other example, too.
And, by the way, reading this HOWTO has been very useful to me.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30004>
_______________________________________

From stefan at bytereef.org  Thu Apr  6 12:58:35 2017
From: stefan at bytereef.org (stefan at bytereef.org)
Date: Thu, 06 Apr 2017 16:58:35 -0000
Subject: [docs] Sync-up docstrings in C version of the the decimal
 module (issue 27779)
Message-ID: <20170406165835.16266.7042@psf.upfronthosting.co.za>


https://bugs.python.org/review/27779/diff/18450/Modules/_decimal/docstrings.h
File Modules/_decimal/docstrings.h (right):

https://bugs.python.org/review/27779/diff/18450/Modules/_decimal/docstrings.h#newcode244
Modules/_decimal/docstrings.h:244: Represents the number as a triple
tuple, to show the internals exactly as\n\
I meant "show the internals exactly as they are". This is not true for
the C version.

It is not true for the Python version because it uses a string for the
coefficient -- the initial version had the tuple IIRC.

https://bugs.python.org/review/27779/

From report at bugs.python.org  Fri Apr  7 13:50:07 2017
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 07 Apr 2017 17:50:07 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1491587407.77.0.115884374211.issue29974@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Fri Apr  7 14:38:07 2017
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 07 Apr 2017 18:38:07 +0000
Subject: [docs] [issue23984] Documentation error: Descriptors
In-Reply-To: <1429245728.01.0.810263114275.issue23984@psf.upfronthosting.co.za>
Message-ID: <1491590287.79.0.603644541643.issue23984@psf.upfronthosting.co.za>


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


----------
pull_requests: +1189

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23984>
_______________________________________

From report at bugs.python.org  Fri Apr  7 14:55:09 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 07 Apr 2017 18:55:09 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491591309.24.0.20154156875.issue29956@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Is math.exp(x) always more accurate than math.e ** x?  If so, doc could say so.  Otherwise, should this be closed?

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Fri Apr  7 15:29:47 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 07 Apr 2017 19:29:47 +0000
Subject: [docs] [issue29975] Issue in extending documentation
In-Reply-To: <1491273401.15.0.69165837027.issue29975@psf.upfronthosting.co.za>
Message-ID: <1491593387.32.0.266088808946.issue29975@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I agree with the rejection on the PR.

----------
nosy: +terry.reedy
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed
type:  -> behavior

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29975>
_______________________________________

From report at bugs.python.org  Sat Apr  8 02:19:26 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 08 Apr 2017 06:19:26 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491632366.43.0.941411276548.issue19225@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset 7f85947106aff5b1f166a57f644f987db4d38bf0 by Serhiy Storchaka (cocoatomo) in branch '2.7':
[2.7] bpo-19225: Lack of c api exceptions doc (#964)
https://github.com/python/cpython/commit/7f85947106aff5b1f166a57f644f987db4d38bf0


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Sat Apr  8 02:43:07 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 08 Apr 2017 06:43:07 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491633787.75.0.881732002115.issue29956@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Not always. For example for x = 0 both methods give the same exact result.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sat Apr  8 04:12:54 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 08 Apr 2017 08:12:54 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
Message-ID: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Proposed patch adds examples of using re.escape().

See also issue29995.

----------
assignee: docs at python
components: Documentation, Regular Expressions
messages: 291326
nosy: docs at python, ezio.melotti, mrabarnett, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Add examples for re.escape()
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Sat Apr  8 04:14:33 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 08 Apr 2017 08:14:33 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
In-Reply-To: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>
Message-ID: <1491639273.66.0.481513595044.issue30021@psf.upfronthosting.co.za>


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


----------
pull_requests: +1200

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Sat Apr  8 12:07:15 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 08 Apr 2017 16:07:15 +0000
Subject: [docs] [issue29725] sqlite3.Cursor doesn't properly document
 "arraysize"
In-Reply-To: <1488732449.69.0.822466282685.issue29725@psf.upfronthosting.co.za>
Message-ID: <1491667635.33.0.80350248839.issue29725@psf.upfronthosting.co.za>


Berker Peksag added the comment:

> row_factory seems to be another parameter that can be set in the Cursor object.
> https://github.com/python/cpython/blob/master/Modules/_sqlite/cursor.c#L65 
> 
> This can addressed in a different issue/ pr.

Like I already said in msg290943, Cursor.row_factory is kept for backwards compatibility reasons and it shouldn't be documented.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29725>
_______________________________________

From report at bugs.python.org  Sat Apr  8 12:09:12 2017
From: report at bugs.python.org (KINEBUCHI Tomohiko)
Date: Sat, 08 Apr 2017 16:09:12 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491667752.36.0.0369213371902.issue19225@psf.upfronthosting.co.za>


KINEBUCHI Tomohiko added the comment:

Oh, I have overlooked these sentences.
I will create an additional pull request to remove duplication.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Sat Apr  8 20:16:35 2017
From: report at bugs.python.org (Martin Panter)
Date: Sun, 09 Apr 2017 00:16:35 +0000
Subject: [docs] [issue23674] super() documentation isn't very clear
In-Reply-To: <1426448451.56.0.492486239807.issue23674@psf.upfronthosting.co.za>
Message-ID: <1491696995.46.0.285442537637.issue23674@psf.upfronthosting.co.za>


Martin Panter added the comment:

The magical no-argument call could also be clarified:

8. Define in the main text what happens when you omit the first argument (the subclass) to ?super?. At the moment, I think the reader could infer that it is the method?s class, but this is only hinted by reading the comment in the illustration and Raymond?s external web page. The documentation should also clarify how it works, or at least be clear when it is not supported (e.g. one method assigned to multiple classes, functions defined outside a class definition, decorators that re-create the class, ?super? renamed).

9. The no-argument call creates an instance bound to the first argument of the method, not an unbound instance. Determining the ?self? argument is also magical: it does not seem to work with default arguments, variable positional arguments, nor keyword-only arguments. List comprehensions, generator expressions, etc seem to override it, and the argument is not seen by exec and eval.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23674>
_______________________________________

From report at bugs.python.org  Sun Apr  9 02:16:55 2017
From: report at bugs.python.org (Philip Lee)
Date: Sun, 09 Apr 2017 06:16:55 +0000
Subject: [docs] [issue30023] Example code becomes invalid for "Why do
 lambdas defined in a loop with different values all return the same
 result?"
Message-ID: <1491718615.9.0.544401247511.issue30023@psf.upfronthosting.co.za>


New submission from Philip Lee:

There example code here becomes invalid 
https://docs.python.org/3/faq/programming.html#why-do-lambdas-defined-in-a-loop-with-different-values-all-return-the-same-result
>>> squares = []
>>> for x in range(5):
	squares.append(lambda: x**2)

	
>>> squares
[<function <lambda> at 0x01FB7A08>, <function <lambda> at 0x01F82390>, <function <lambda> at 0x01FBA3D8>, <function <lambda> at 0x01FBA420>, <function <lambda> at 0x01FBA468>]
>>> 

There returned value is a List of lambda functions, not numbers

----------
assignee: docs at python
components: Documentation
messages: 291353
nosy: docs at python, iMath
priority: normal
severity: normal
status: open
title: Example code becomes invalid for "Why do lambdas defined in a loop with different values all return the same result?"
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30023>
_______________________________________

From report at bugs.python.org  Sun Apr  9 05:55:54 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 09:55:54 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1491731754.68.0.394817666882.issue22702@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Raymond, in the review comments on https://github.com/python/cpython/pull/156 Xiang noted that the current apparently duplicated iterable isn't entirely redundant:

- the first reference is to the term "iterable"
- the second reference is to the parameter name "*iterable*"

"Return a string which is the concatenation of the strings in the :term:`iterable` *iterable*."

So if we're going to drop one of them, it should probably be the link to the term, rather than the parameter name:


"Return a string which is the concatenation of the strings in *iterable*."

Does that sound reasonable to you?

----------
nosy: +ncoghlan, xiang.zhang

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22702>
_______________________________________

From report at bugs.python.org  Sun Apr  9 05:59:20 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 09:59:20 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1491731960.34.0.287927961867.issue22702@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Noting for the record: Marco Buttu proposed my suggested approach on the PR back in early March.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22702>
_______________________________________

From report at bugs.python.org  Sun Apr  9 06:03:20 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 10:03:20 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1491732199.87.0.954252727948.issue29506@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Assigning to myself since Sanyam submitted the related PR at the PyCon Pune sprints.

----------
assignee: docs at python -> ncoghlan

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29506>
_______________________________________

From report at bugs.python.org  Sun Apr  9 06:17:03 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 10:17:03 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1491733023.01.0.890038556343.issue29506@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

I'm going to merge Sanyam's PR as-is, as while David's reformulation shorten the overall sentence, it complicates the core description of the problem (copying things that you didn't want copied) by merging it with the stereotypical example of why you might not want to copy something (i.e. you intended to share a common reference between otherwise independent copies).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29506>
_______________________________________

From report at bugs.python.org  Sun Apr  9 06:22:33 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 10:22:33 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1491733352.98.0.381751522211.issue29506@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset 19e04942562a980ad2519f6ff79c455a7472783b by Nick Coghlan (Sanyam Khurana) in branch 'master':
bpo-29506: Clarify deep copy note in copy module
https://github.com/python/cpython/commit/19e04942562a980ad2519f6ff79c455a7472783b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29506>
_______________________________________

From report at bugs.python.org  Sun Apr  9 06:25:08 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 10:25:08 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1491733508.56.0.325900864122.issue29506@psf.upfronthosting.co.za>


Changes by Nick Coghlan <ncoghlan at gmail.com>:


----------
pull_requests: +1208

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29506>
_______________________________________

From report at bugs.python.org  Sun Apr  9 06:25:59 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 10:25:59 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1491733559.39.0.466738998546.issue29506@psf.upfronthosting.co.za>


Changes by Nick Coghlan <ncoghlan at gmail.com>:


----------
pull_requests: +1209

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29506>
_______________________________________

From report at bugs.python.org  Sun Apr  9 06:33:59 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 10:33:59 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1491734039.11.0.088769151664.issue29506@psf.upfronthosting.co.za>


Changes by Nick Coghlan <ncoghlan at gmail.com>:


----------
pull_requests: +1210

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29506>
_______________________________________

From report at bugs.python.org  Sun Apr  9 06:57:06 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 10:57:06 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1491735426.33.0.425875099058.issue29506@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset a524d6307273e3920d410452ace89610c843f051 by Nick Coghlan in branch '3.6':
bpo-29506: Clarify deep copy note in copy module
https://github.com/python/cpython/commit/a524d6307273e3920d410452ace89610c843f051


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29506>
_______________________________________

From report at bugs.python.org  Sun Apr  9 06:57:17 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 10:57:17 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1491735437.82.0.827103196272.issue29506@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset bd18351c31573ab9a8580677004370a774a4eaae by Nick Coghlan in branch '3.5':
bpo-29506: Clarify deep copy note in copy module
https://github.com/python/cpython/commit/bd18351c31573ab9a8580677004370a774a4eaae


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29506>
_______________________________________

From report at bugs.python.org  Sun Apr  9 06:57:31 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 10:57:31 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1491735451.08.0.898708054742.issue29506@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset ab16dc180e362e4cdb9eb163fae0a75664dcea3e by Nick Coghlan in branch '2.7':
bpo-29506: Clarify deep copy note in copy module
https://github.com/python/cpython/commit/ab16dc180e362e4cdb9eb163fae0a75664dcea3e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29506>
_______________________________________

From report at bugs.python.org  Sun Apr  9 06:58:19 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 09 Apr 2017 10:58:19 +0000
Subject: [docs] [issue29506] Incorrect documentation for the copy module
In-Reply-To: <1486591364.1.0.297030175166.issue29506@psf.upfronthosting.co.za>
Message-ID: <1491735499.31.0.0529081276167.issue29506@psf.upfronthosting.co.za>


Changes by Nick Coghlan <ncoghlan at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29506>
_______________________________________

From report at bugs.python.org  Sun Apr  9 10:29:22 2017
From: report at bugs.python.org (Eric V. Smith)
Date: Sun, 09 Apr 2017 14:29:22 +0000
Subject: [docs] [issue30023] Example code becomes invalid for "Why do
 lambdas defined in a loop with different values all return the same
 result?"
In-Reply-To: <1491718615.9.0.544401247511.issue30023@psf.upfronthosting.co.za>
Message-ID: <1491748162.7.0.19886821443.issue30023@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

That's consistent with the example: it's showing you how to create a list of functions, that when called, return squares.

"This gives you a list that contains 5 lambdas that calculate x**2"

Maybe "squares" isn't the most awesome name, but I think if you read the example in its entirety, it's all consistent and correct.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30023>
_______________________________________

From report at bugs.python.org  Sun Apr  9 11:38:34 2017
From: report at bugs.python.org (Eric V. Smith)
Date: Sun, 09 Apr 2017 15:38:34 +0000
Subject: [docs] [issue30023] Example code becomes invalid for "Why do
 lambdas defined in a loop with different values all return the same
 result?"
In-Reply-To: <1491718615.9.0.544401247511.issue30023@psf.upfronthosting.co.za>
Message-ID: <1491752314.53.0.313002500603.issue30023@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30023>
_______________________________________

From report at bugs.python.org  Sun Apr  9 12:12:54 2017
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 09 Apr 2017 16:12:54 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491754374.45.0.458085211161.issue29956@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

> Is math.exp(x) always more accurate than math.e ** x?

As Serhiy says: not always, and in general the answer is going to depend on the relative quality of the libm implementations of pow and exp. But on typical machines, it is going to be true that `math.exp(x)` is a better (faster, more accurate) way of computing the exponential function than `math.e ** x`. (Similarly, `math.sqrt(x)` should be preferred over `x ** 0.5`.) I'm not sure whether it's worth encoding such recommendations in the documentation or not.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sun Apr  9 12:23:03 2017
From: report at bugs.python.org (Max)
Date: Sun, 09 Apr 2017 16:23:03 +0000
Subject: [docs] [issue30026] Hashable doesn't check for __eq__
Message-ID: <1491754983.55.0.46541300109.issue30026@psf.upfronthosting.co.za>


New submission from Max:

I think collections.abc.Hashable.__subclasshook__ should check __eq__ method in addition to __hash__ method. This helps detect classes that are unhashable due to:

to __eq__ = None

Of course, it still cannot detect:

def __eq__: return NotImplemented

but it's better than nothing.

In addition, it's probably worth documenting that explicitly inheriting from Hashable has (correct but unexpected) effect of *suppressing* hashability that was already present:

from collections.abc import Hashable
class X: pass
assert issubclass(X, Hashable)
x = X()

class X(Hashable): pass
assert issubclass(X, Hashable)
x = X() # Can't instantiate abstract class X with abstract methods

----------
assignee: docs at python
components: Documentation, Interpreter Core
messages: 291382
nosy: docs at python, max
priority: normal
severity: normal
status: open
title: Hashable doesn't check for __eq__

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30026>
_______________________________________

From report at bugs.python.org  Sun Apr  9 12:25:43 2017
From: report at bugs.python.org (Max)
Date: Sun, 09 Apr 2017 16:25:43 +0000
Subject: [docs] [issue30026] Hashable doesn't check for __eq__
In-Reply-To: <1491754983.55.0.46541300109.issue30026@psf.upfronthosting.co.za>
Message-ID: <1491755143.45.0.958313626576.issue30026@psf.upfronthosting.co.za>


Max added the comment:

Sorry, this should be just a documentation issue.

I just realized that __eq__ = None isn't correct anyway, so instead we should just document that Hashable cannot check for __eq__ and that explicitly deriving from Hashable suppresses hashability.

----------
components:  -Interpreter Core

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30026>
_______________________________________

From report at bugs.python.org  Sun Apr  9 14:40:47 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 09 Apr 2017 18:40:47 +0000
Subject: [docs] [issue30026] Hashable doesn't check for __eq__
In-Reply-To: <1491754983.55.0.46541300109.issue30026@psf.upfronthosting.co.za>
Message-ID: <1491763247.05.0.35238345932.issue30026@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> # Can't instantiate abstract class X with abstract methods

Sorry, this is how ABCs are supposed to work.  They use @abstractmethod to specify requirements that a subclass if required to implement.  The ABC metaclass then enforces that requirement, preventing instantiation unless those requirements are met.  If not met, they give a reasonably clear error message, "TypeError: Can't instantiate abstract class A with abstract methods __hash__".

----------
assignee: docs at python -> rhettinger
nosy: +rhettinger
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30026>
_______________________________________

From report at bugs.python.org  Sun Apr  9 14:55:02 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 09 Apr 2017 18:55:02 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491764102.55.0.385064251509.issue29956@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> Is math.exp(x) always more accurate than math.e ** x? 

It is usually at least as accurate, but we can't really guarantee anything because math.exp does whatever the underlying C math library does (so good libary -> good result, bad library -> bad result).

Rather than gum-up the math library docs, I suggest having a FAQ entry or wiki entry somewhere.  Getting extreme accuracy is a nebulous topic in general and even more so in Python (where there is very little you can do to prevent double rounding and whatnot).  

In addition to extreme accuracy issues, there are also performance issues which will vary from implementation to implementation and from release to release.

Historically, the docs have tried to rise above the fray and make very few if any promises about accuracy or speed.  This should be doubly true when it comes to numerical methods which are a mix of art, science, and dark art (and where the answers to "what is best" may change depending on the range of input values).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sun Apr  9 15:11:49 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 09 Apr 2017 19:11:49 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491765109.76.0.383355573777.issue29956@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

To include corner cases, I should have asked 'at least as accurate' rather than 'more accurate'.  It would be a sad libm that had specialized functions worse than pow, since the specialized functions could, at worse, use pow.

For an expert point of view, the reason for math to have the specialized functions is to give access to functions in the libm of the compiler used. A beginner ignorant of such things might wonder whether exp and sqrt are just trivial abbreviations, and if not, which to use.  I believe this question has appeared on python-list.  It definitely has on StackOverflow.

For e**x, there is, for instance,
https://stackoverflow.com/questions/30756983/difference-between-math-exp2-and-math-e2
with this comment "Voting to reopen. There's more going on here than simply "floating-point is inaccurate". In particular, as the two answers explain, there are good reasons to expect exp(x) to be more accurate than e**x. ? Mark Dickinson " ;-).

Searching "[python] math.sqrt pow" gets more hits.
https://stackoverflow.com/questions/18965524/exponentiation-in-python-should-i-prefer-operator-instead-of-math-pow-and-m
https://stackoverflow.com/questions/33684948/difference-between-1-2-math-sqrt-and-cmath-sqrt
and multiple questions about relative speed.

So I am inclined to add "This is generally better than math.e ** x and math.pow(e, 0.5)." (for math.exp) and "than x ** 0.5 and math.pow(x, 0.5)" for math.sqrt, and similarly for cmath.sqrt).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sun Apr  9 15:17:17 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 09 Apr 2017 19:17:17 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491765437.93.0.47702327556.issue29956@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Raymond added his comment while I was writing mine.  A FAQ with added caveats might be even better, but it will be mostly missed.  If we add one, I might add a comment to some of the SO questions.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sun Apr  9 15:27:12 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 09 Apr 2017 19:27:12 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491766032.1.0.879012879234.issue29956@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

FWIW, these kind of nuances really aren't beginner topics.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sun Apr  9 15:40:06 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 09 Apr 2017 19:40:06 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491766806.72.0.311794011928.issue29956@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Nuances of expm1(), log1p(), log2() and log10() aren't beginner topics, but they are documented. I think it wouldn't harm if add "This is usually more accurate than ``e ** x`` or ``pow(e, x)``."

The only issue is how to distinguish ``math`` constant ``e`` from mathematical constant *e*.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sun Apr  9 19:33:59 2017
From: report at bugs.python.org (KINEBUCHI Tomohiko)
Date: Sun, 09 Apr 2017 23:33:59 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1491780839.06.0.603669126444.issue19225@psf.upfronthosting.co.za>


Changes by KINEBUCHI Tomohiko <cocoatomo77 at gmail.com>:


----------
pull_requests: +1214

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Sun Apr  9 20:53:04 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 10 Apr 2017 00:53:04 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491785584.56.0.69680322682.issue29956@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> The only issue is how to distinguish ``math`` constant ``e``
> from mathematical constant *e*.

Sorry, I think you're inventing an issue here.  ``math.e`` is the nearest representable value to the mathematical constant *e*.  This is no more interesting or useful that distinguishing ``math.pi`` from the mathematical constant *pi*.  I don't know of any other language that tries to split hairs like this.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Sun Apr  9 22:42:35 2017
From: report at bugs.python.org (Martin Panter)
Date: Mon, 10 Apr 2017 02:42:35 +0000
Subject: [docs] [issue14039] Add "metavar" argument to add_subparsers() in
 argparse
In-Reply-To: <1329436304.54.0.709137632289.issue14039@psf.upfronthosting.co.za>
Message-ID: <1491792155.66.0.645058181651.issue14039@psf.upfronthosting.co.za>


Martin Panter added the comment:

Thanks to Issue 11807, the documentation now lists ?metavar?. (However, it looks like a positional argument, rather than keyword-only, and its use seems to be discouraged, but those issues are not specific to ?metavar?.)

Some points specific to ?metavar? that I think could be clarified:

1. Metavar seems to affect the placeholder in the ?usage? message, and a heading that precedes a multi-line list of commands, but it does not affect the presentation of the multi-line list itself.

2. The relationship between the ?metavar? parameter of ?add_argument? and ?add_subparsers? needs clarifying. At the moment, there is a hyperlink, which implies that the description of add_argument?s parameter applies to add_subparsers. But it only discusses the ?dest? parameter and CLI options (a.k.a. ?optionals?), neither of which make sense in the context of subcommands. Issue 29030 (choices vs metavar) may be related.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14039>
_______________________________________

From report at bugs.python.org  Mon Apr 10 00:49:12 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 10 Apr 2017 04:49:12 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1491785584.56.0.69680322682.issue29956@psf.upfronthosting.co.za>
Message-ID: <4909666.sEOa66sIsc@raxxla>


Serhiy Storchaka added the comment:

This is the original issue, it isn't invented by me. ``math.e`` is the nearest
representable value to the mathematical constant *e* and ``math.exp(x)`` is 
the nearest representable value to the mathematical constant *e* raised to the 
power *x*, but not the nearest representable value to ``math.e`` raised to the 
power *x*.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Mon Apr 10 01:34:38 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 10 Apr 2017 05:34:38 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491802478.22.0.10151183436.issue29956@psf.upfronthosting.co.za>


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


----------
pull_requests: +1216

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Mon Apr 10 01:36:57 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 10 Apr 2017 05:36:57 +0000
Subject: [docs] [issue29956] math.exp documentation is misleading
In-Reply-To: <1490990917.06.0.404933995002.issue29956@psf.upfronthosting.co.za>
Message-ID: <1491802617.61.0.528584271349.issue29956@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Proposed patch applies Mark's fix to math.expm1() and cmath.exp(), adds the accuracy note to math.exp(), adds italic to mathematical constants, fixes empty lines.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29956>
_______________________________________

From report at bugs.python.org  Mon Apr 10 13:27:52 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 10 Apr 2017 17:27:52 +0000
Subject: [docs] [issue29521] Minor warning messages when compiling
 documentation
In-Reply-To: <1486714459.11.0.428886237265.issue29521@psf.upfronthosting.co.za>
Message-ID: <1491845272.87.0.00978141591806.issue29521@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset e0cba5b45a5c4bafd1ae772be52ca0d69651da24 by Mariatta in branch '2.7':
[2.7] bpo-29521: Fix two minor documentation build warnings (GH-41) (GH-670)
https://github.com/python/cpython/commit/e0cba5b45a5c4bafd1ae772be52ca0d69651da24


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29521>
_______________________________________

From clar0193 at visi.com  Mon Apr 10 11:56:33 2017
From: clar0193 at visi.com (Ted Clark)
Date: Mon, 10 Apr 2017 10:56:33 -0500
Subject: [docs] Typo in the Python 2.7 tutorial, section 3.1.2
Message-ID: <1491839793.13962.4.camel@visi.com>

There's a typo in the Python 2.7 tutorial, section 3.1.2:

>>> 'doesn\'t'??# use \' to escape the single quote...
"doesn't"

should be:

>>> 'doesn\'t'??# use \' to escape the single quote...
'doesn\'t'


From clar0193 at visi.com  Mon Apr 10 12:00:01 2017
From: clar0193 at visi.com (Ted Clark)
Date: Mon, 10 Apr 2017 11:00:01 -0500
Subject: [docs] Typo in the Python 2.7 tutorial, section 3.1.2
In-Reply-To: <1491839793.13962.4.camel@visi.com>
References: <1491839793.13962.4.camel@visi.com>
Message-ID: <1491840001.14469.0.camel@visi.com>

I think I might be confusing input (and comments) with output. ?I'm not
sure...


On Mon, 2017-04-10 at 10:56 -0500, Ted Clark wrote:
> There's a typo in the Python 2.7 tutorial, section 3.1.2:
> 
> > 
> > > 
> > > > 
> > > > 'doesn\'t'??# use \' to escape the single quote...
> "doesn't"
> 
> should be:
> 
> > 
> > > 
> > > > 
> > > > 'doesn\'t'??# use \' to escape the single quote...
> 'doesn\'t'

From report at bugs.python.org  Tue Apr 11 03:51:50 2017
From: report at bugs.python.org (Dutcho)
Date: Tue, 11 Apr 2017 07:51:50 +0000
Subject: [docs] [issue30037] inspect documentation on code attributes
 incomplete
Message-ID: <1491897110.71.0.340435065051.issue30037@psf.upfronthosting.co.za>


New submission from Dutcho:

The table at the top of the inspect documentation (https://docs.python.org/3/library/inspect.html#types-and-members) omits co_cellvars, co_freevars, and co_kwonlyargcount attributes of type code

(note: the type's doc string does provide these attributes)

----------
assignee: docs at python
components: Documentation
messages: 291464
nosy: Dutcho, docs at python
priority: normal
severity: normal
status: open
title: inspect documentation on code attributes incomplete
type: enhancement
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30037>
_______________________________________

From report at bugs.python.org  Tue Apr 11 04:27:16 2017
From: report at bugs.python.org (Martin Panter)
Date: Tue, 11 Apr 2017 08:27:16 +0000
Subject: [docs] [issue30037] inspect documentation on code attributes
 incomplete
In-Reply-To: <1491897110.71.0.340435065051.issue30037@psf.upfronthosting.co.za>
Message-ID: <1491899236.33.0.164981769561.issue30037@psf.upfronthosting.co.za>


Martin Panter added the comment:

Looks like a there is already a patch discussed at Issue 26985.

----------
nosy: +martin.panter
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Information about CodeType in inspect documentation is outdated

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30037>
_______________________________________

From Xiang.Gao at esi-group.com  Mon Apr 10 16:08:19 2017
From: Xiang.Gao at esi-group.com (Xiang Gao)
Date: Mon, 10 Apr 2017 20:08:19 +0000
Subject: [docs] A bug in python 2.7.12 and 3.5.2 ?
Message-ID: <HE1PR0502MB30665F847682A8278A4ADCA8A6010@HE1PR0502MB3066.eurprd05.prod.outlook.com>

Hi?


I noticed something strange when initializing an empty list of a given size using:


>>> a = [ [] ] * 3   # create an empty list of size 3, with each element being an empty list

>>> a[1].append('a')   # modify element[1], leave element[0] and [2] unchanged.

>>> a

>>> [ ['a'], ['a'], ['a'] ]   # Result suggests all elements have shared references, that doesn't look right.


This is not critical, since I can re-initialize the empty list: (But, it would be nice to fix it. )


>>> for i in range(len(a)):

>>>     a[i] = []

>>>

>>> a[1].append('a')

>>> a

>>> [ [], ['a'], [] ]   # This is what I expected.


Thanks for your attention !


Xiang

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

From report at bugs.python.org  Tue Apr 11 19:22:47 2017
From: report at bugs.python.org (OSAMU NAKAMURA)
Date: Tue, 11 Apr 2017 23:22:47 +0000
Subject: [docs] [issue30047] Typos in Doc/library/select.rst
Message-ID: <1491952967.06.0.143723768718.issue30047@psf.upfronthosting.co.za>


New submission from OSAMU NAKAMURA:

In 18.3.2. Edge and Level Trigger Polling (epoll) Objects,
there is duplicated 'on' in description of `EPOLLEXCLUSIVE`.

   Wake only ... objects polling on on a fd.
                                 ^^^^^

----------
assignee: docs at python
components: Documentation
messages: 291520
nosy: OSAMU.NAKAMURA, docs at python
priority: normal
severity: normal
status: open
title: Typos in Doc/library/select.rst
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30047>
_______________________________________

From report at bugs.python.org  Tue Apr 11 19:27:13 2017
From: report at bugs.python.org (OSAMU NAKAMURA)
Date: Tue, 11 Apr 2017 23:27:13 +0000
Subject: [docs] [issue30047] Typos in Doc/library/select.rst
In-Reply-To: <1491952967.06.0.143723768718.issue30047@psf.upfronthosting.co.za>
Message-ID: <1491953233.21.0.0864801664295.issue30047@psf.upfronthosting.co.za>


Changes by OSAMU NAKAMURA <osamu0329nakamura at gmail.com>:


----------
pull_requests: +1230

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30047>
_______________________________________

From report at bugs.python.org  Tue Apr 11 21:34:38 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 12 Apr 2017 01:34:38 +0000
Subject: [docs] [issue29933] asyncio: set_write_buffer_limits() doc doesn't
 specify unit of the parameters
In-Reply-To: <1490707139.27.0.838851028066.issue29933@psf.upfronthosting.co.za>
Message-ID: <1491960878.68.0.177982856035.issue29933@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29933>
_______________________________________

From report at bugs.python.org  Tue Apr 11 21:34:47 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 12 Apr 2017 01:34:47 +0000
Subject: [docs] [issue29933] asyncio: set_write_buffer_limits() doc doesn't
 specify unit of the parameters
In-Reply-To: <1490707139.27.0.838851028066.issue29933@psf.upfronthosting.co.za>
Message-ID: <1491960887.79.0.00325369788579.issue29933@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29933>
_______________________________________

From report at bugs.python.org  Tue Apr 11 23:52:33 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 12 Apr 2017 03:52:33 +0000
Subject: [docs] [issue26985] Information about CodeType in inspect
 documentation is outdated
In-Reply-To: <1462803102.24.0.542356144335.issue26985@psf.upfronthosting.co.za>
Message-ID: <1491969153.58.0.925111746603.issue26985@psf.upfronthosting.co.za>


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


----------
type: behavior -> 
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26985>
_______________________________________

From report at bugs.python.org  Wed Apr 12 05:26:23 2017
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 12 Apr 2017 09:26:23 +0000
Subject: [docs] [issue30051] Document that the random module doesn't support
 fork
In-Reply-To: <1491989089.77.0.552733144958.issue30051@psf.upfronthosting.co.za>
Message-ID: <1491989183.33.0.590968204686.issue30051@psf.upfronthosting.co.za>


Changes by STINNER Victor <victor.stinner at gmail.com>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python, rhettinger, serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30051>
_______________________________________

From report at bugs.python.org  Wed Apr 12 05:30:03 2017
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 12 Apr 2017 09:30:03 +0000
Subject: [docs] [issue30051] Document that the random module doesn't support
 fork
In-Reply-To: <1491989089.77.0.552733144958.issue30051@psf.upfronthosting.co.za>
Message-ID: <1491989403.01.0.571368120939.issue30051@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I'm not sure that's necessary.  fork() is a low-level primitive, people can/should use multiprocessing.Process instead, which does re-seed the PRNG.

----------
nosy: +pitrou

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30051>
_______________________________________

From report at bugs.python.org  Wed Apr 12 05:48:32 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 12 Apr 2017 09:48:32 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
In-Reply-To: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>
Message-ID: <1491990512.87.0.94351438968.issue30021@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> serhiy.storchaka

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Wed Apr 12 06:02:53 2017
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 12 Apr 2017 10:02:53 +0000
Subject: [docs] [issue30051] Document that the random module doesn't support
 fork
In-Reply-To: <1491989403.01.0.571368120939.issue30051@psf.upfronthosting.co.za>
Message-ID: <CAMpsgwb5XoMw-oBci297KDXVbReVBcg4vbmoN8EhxQmW77NK0w@mail.gmail.com>


STINNER Victor added the comment:

> I'm not sure that's necessary.

Do you mean that adding a note is not necessary? Or proposing a
solution in the note?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30051>
_______________________________________

From report at bugs.python.org  Wed Apr 12 06:04:48 2017
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 12 Apr 2017 10:04:48 +0000
Subject: [docs] [issue30051] Document that the random module doesn't support
 fork
In-Reply-To: <1491989089.77.0.552733144958.issue30051@psf.upfronthosting.co.za>
Message-ID: <1491991488.06.0.0116776069287.issue30051@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I mean mentioning fork(), which people usually don't call directly, is not necessary, so, indeed, a note isn't necessary.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30051>
_______________________________________

From report at bugs.python.org  Wed Apr 12 06:16:47 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 12 Apr 2017 10:16:47 +0000
Subject: [docs] [issue26985] Information about CodeType in inspect
 documentation is outdated
In-Reply-To: <1462803102.24.0.542356144335.issue26985@psf.upfronthosting.co.za>
Message-ID: <1491992207.74.0.117746091754.issue26985@psf.upfronthosting.co.za>


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


----------
pull_requests: +1233

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26985>
_______________________________________

From report at bugs.python.org  Wed Apr 12 06:30:42 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 12 Apr 2017 10:30:42 +0000
Subject: [docs] [issue30047] Typos in Doc/library/select.rst
In-Reply-To: <1491952967.06.0.143723768718.issue30047@psf.upfronthosting.co.za>
Message-ID: <1491993042.65.0.922183431552.issue30047@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset 3e0f1fc4e0ffcfcc706015fa3d67c262948ef171 by Serhiy Storchaka (NAKAMURA Osamu) in branch 'master':
bpo-30047: Fix a typo in Doc/library/select.rst (#1086)
https://github.com/python/cpython/commit/3e0f1fc4e0ffcfcc706015fa3d67c262948ef171


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30047>
_______________________________________

From report at bugs.python.org  Wed Apr 12 06:36:32 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 12 Apr 2017 10:36:32 +0000
Subject: [docs] [issue30051] Document that the random module doesn't support
 fork
In-Reply-To: <1491989089.77.0.552733144958.issue30051@psf.upfronthosting.co.za>
Message-ID: <1491993392.11.0.681781373499.issue30051@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I think it is worth documenting.

Even if multiprocessing reseeds the module-global random generator, it doesn't reseed other instances of Random.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30051>
_______________________________________

From report at bugs.python.org  Wed Apr 12 08:49:34 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 12 Apr 2017 12:49:34 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
Message-ID: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>


New submission from Cheryl Sabella:

On the URL Quoting page, the following line:

`string may be either a str or a bytes.`

Has the `str` link to:
https://docs.python.org/3/library/stdtypes.html#str

But the `bytes` link to:
https://docs.python.org/3/library/functions.html#bytes

Should the `bytes` link to?
https://docs.python.org/3/library/stdtypes.html#bytes

----------
assignee: docs at python
components: Documentation
messages: 291546
nosy: csabella, docs at python
priority: normal
severity: normal
status: open
title: URL Quoting page links to function Bytes instead of defintion
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Wed Apr 12 09:59:26 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 12 Apr 2017 13:59:26 +0000
Subject: [docs] [issue29791] print documentation: flush is also a keyword
 argument
In-Reply-To: <1489179993.27.0.31165504732.issue29791@psf.upfronthosting.co.za>
Message-ID: <1492005566.77.0.374885439671.issue29791@psf.upfronthosting.co.za>


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


----------
pull_requests: +1235

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29791>
_______________________________________

From report at bugs.python.org  Wed Apr 12 09:59:58 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 12 Apr 2017 13:59:58 +0000
Subject: [docs] [issue29791] print documentation: flush is also a keyword
 argument
In-Reply-To: <1489179993.27.0.31165504732.issue29791@psf.upfronthosting.co.za>
Message-ID: <1492005598.96.0.556796130834.issue29791@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29791>
_______________________________________

From report at bugs.python.org  Wed Apr 12 10:59:31 2017
From: report at bugs.python.org (Marco Buttu)
Date: Wed, 12 Apr 2017 14:59:31 +0000
Subject: [docs] [issue30055] Missed testcleanup in decimal.rst
Message-ID: <1492009171.7.0.643211980228.issue30055@psf.upfronthosting.co.za>


New submission from Marco Buttu:

The testsetup in Doc/library/decimal.rst is not enough for isolating the tests in respect to the other rst files.  Currently we have the following testsetup, without a testcleanup:

 .. testsetup:: *
 
    import decimal
    import math
    from decimal import *
    # make sure each group gets a fresh context
    setcontext(Context())

Without a testcleanup, the changes on the context will affect the other files that use the context (like Doc/library/statistics.rst).  We should better isolate the tests adding also a testcleanup:

.. testcleanup:: *

   # make sure other tests (outside this file) get a fresh context
   setcontext(Context())

I am opening a PR.

----------
assignee: docs at python
components: Documentation
messages: 291559
nosy: docs at python, marco.buttu, skrah
priority: normal
severity: normal
status: open
title: Missed testcleanup in decimal.rst
type: enhancement
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30055>
_______________________________________

From report at bugs.python.org  Wed Apr 12 11:11:52 2017
From: report at bugs.python.org (Marco Buttu)
Date: Wed, 12 Apr 2017 15:11:52 +0000
Subject: [docs] [issue30055] Missed testcleanup in decimal.rst
In-Reply-To: <1492009171.7.0.643211980228.issue30055@psf.upfronthosting.co.za>
Message-ID: <1492009912.82.0.310749305375.issue30055@psf.upfronthosting.co.za>


Changes by Marco Buttu <marco.buttu at gmail.com>:


----------
pull_requests: +1236

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30055>
_______________________________________

From report at bugs.python.org  Wed Apr 12 13:25:17 2017
From: report at bugs.python.org (Michael Seifert)
Date: Wed, 12 Apr 2017 17:25:17 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
Message-ID: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>


New submission from Michael Seifert:

The "Py_Ellipsis" object is part of the public C-API but it isn't documented anywhere.

It is defined in "sliceobject.o/.h" so I created a PR and added it to the "slice" documentation.

----------
assignee: docs at python
components: Documentation
messages: 291567
nosy: MSeifert, docs at python
priority: normal
pull_requests: 1238
severity: normal
status: open
title: No documentation for C type Py_Ellipsis
type: enhancement
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Wed Apr 12 14:48:44 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 12 Apr 2017 18:48:44 +0000
Subject: [docs] [issue30047] Typos in Doc/library/select.rst
In-Reply-To: <1491952967.06.0.143723768718.issue30047@psf.upfronthosting.co.za>
Message-ID: <1492022924.37.0.770233490075.issue30047@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

This needs backport, which I will do later today. Thanks.

----------
assignee: docs at python -> Mariatta
nosy: +Mariatta
stage:  -> backport needed
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30047>
_______________________________________

From report at bugs.python.org  Wed Apr 12 15:01:37 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 12 Apr 2017 19:01:37 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492023697.21.0.723711036449.issue30059@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I'm wondering if it is worth to add a separate section for Ellipsis at the same level as "Slice Objects", but in the same file. See for example "Instance Method Objects" and "Method Objects" in method.rst.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Wed Apr 12 15:29:25 2017
From: report at bugs.python.org (Michael Seifert)
Date: Wed, 12 Apr 2017 19:29:25 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492025365.84.0.349522597521.issue30059@psf.upfronthosting.co.za>


Michael Seifert added the comment:

> I'm wondering if it is worth to add a separate section for Ellipsis at the same level as "Slice Objects", but in the same file.

I'm not sure either. 

There seems to be no precedent in the documentation, for example "Py_NotImplemented" is also just another (but mentioned first) point in the Object protocol [https://docs.python.org/3/c-api/object.html#object-protocol] and "Py_None" even has a complete page [https://docs.python.org/3/c-api/none.html].

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Wed Apr 12 18:14:50 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 12 Apr 2017 22:14:50 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1492035290.4.0.75807937675.issue30052@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

I've looked into this a little more and it seems that, in all instances, the :class:`bytes` and :class:`bytearray` mark-up link to the Built-In Functions page instead of the Built-In Types page.

It also looks like the Built-In Functions page has specific code for many types (dict, frozenset, memoryview, list, tuple, str, etc) so that it wouldn't link to this (the functions) page.  However, bytes and bytearray aren't part of that list.  I don't know if they were excluded on purpose or if their links should behave like the other types.

Please let me know if this should change.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Wed Apr 12 22:38:31 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 13 Apr 2017 02:38:31 +0000
Subject: [docs] [issue26985] Information about CodeType in inspect
 documentation is outdated
In-Reply-To: <1462803102.24.0.542356144335.issue26985@psf.upfronthosting.co.za>
Message-ID: <1492051110.99.0.186320616665.issue26985@psf.upfronthosting.co.za>


Xiang Zhang added the comment:


New changeset a6902e662c18dc837d40664eaafe50a44aae6366 by Xiang Zhang in branch 'master':
bpo-26985: Add missing info of code object in inspect documentation (GH-1090)
https://github.com/python/cpython/commit/a6902e662c18dc837d40664eaafe50a44aae6366


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26985>
_______________________________________

From report at bugs.python.org  Wed Apr 12 22:52:13 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 13 Apr 2017 02:52:13 +0000
Subject: [docs] [issue30047] Typos in Doc/library/select.rst
In-Reply-To: <1491952967.06.0.143723768718.issue30047@psf.upfronthosting.co.za>
Message-ID: <1492051933.55.0.577644556135.issue30047@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +1241

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30047>
_______________________________________

From report at bugs.python.org  Wed Apr 12 22:53:13 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 13 Apr 2017 02:53:13 +0000
Subject: [docs] [issue26985] Information about CodeType in inspect
 documentation is outdated
In-Reply-To: <1462803102.24.0.542356144335.issue26985@psf.upfronthosting.co.za>
Message-ID: <1492051993.29.0.0195842398011.issue26985@psf.upfronthosting.co.za>


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


----------
pull_requests: +1242

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26985>
_______________________________________

From report at bugs.python.org  Wed Apr 12 22:53:55 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 13 Apr 2017 02:53:55 +0000
Subject: [docs] [issue26985] Information about CodeType in inspect
 documentation is outdated
In-Reply-To: <1462803102.24.0.542356144335.issue26985@psf.upfronthosting.co.za>
Message-ID: <1492052035.19.0.858240985022.issue26985@psf.upfronthosting.co.za>


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


----------
pull_requests: +1243

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26985>
_______________________________________

From report at bugs.python.org  Wed Apr 12 23:02:23 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 13 Apr 2017 03:02:23 +0000
Subject: [docs] [issue30047] Typos in Doc/library/select.rst
In-Reply-To: <1491952967.06.0.143723768718.issue30047@psf.upfronthosting.co.za>
Message-ID: <1492052543.73.0.437813839447.issue30047@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset f0c416799b33742af36d7c6608b9a422615fb3d2 by Mariatta in branch '3.6':
[3.6] bpo-30047: Fix a typo in Doc/library/select.rst (GH-1086) (GH-1098)
https://github.com/python/cpython/commit/f0c416799b33742af36d7c6608b9a422615fb3d2


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30047>
_______________________________________

From report at bugs.python.org  Wed Apr 12 23:03:28 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 13 Apr 2017 03:03:28 +0000
Subject: [docs] [issue30047] Typos in Doc/library/select.rst
In-Reply-To: <1491952967.06.0.143723768718.issue30047@psf.upfronthosting.co.za>
Message-ID: <1492052608.96.0.709021707416.issue30047@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Backported to 3.6.
Closing this now.
Thanks all :)

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30047>
_______________________________________

From report at bugs.python.org  Wed Apr 12 23:14:19 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 13 Apr 2017 03:14:19 +0000
Subject: [docs] [issue26985] Information about CodeType in inspect
 documentation is outdated
In-Reply-To: <1462803102.24.0.542356144335.issue26985@psf.upfronthosting.co.za>
Message-ID: <1492053259.35.0.679093126113.issue26985@psf.upfronthosting.co.za>


Xiang Zhang added the comment:


New changeset 14944c62300f741488c2f28cb91ad1e3fef7343b by Xiang Zhang in branch '3.6':
bpo-26985: Add missing info of code object in inspect documentation (GH-1090) (GH-1099)
https://github.com/python/cpython/commit/14944c62300f741488c2f28cb91ad1e3fef7343b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26985>
_______________________________________

From report at bugs.python.org  Wed Apr 12 23:37:40 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 13 Apr 2017 03:37:40 +0000
Subject: [docs] [issue26985] Information about CodeType in inspect
 documentation is outdated
In-Reply-To: <1462803102.24.0.542356144335.issue26985@psf.upfronthosting.co.za>
Message-ID: <1492054660.4.0.22701103384.issue26985@psf.upfronthosting.co.za>


Xiang Zhang added the comment:


New changeset 72b1d419ac5f7cd9ef82ffd2ffe21aa9b34e21d2 by Xiang Zhang in branch '3.5':
bpo-26985: Add missing info of code object in inspect documentation (GH-1090) (GH-1100)
https://github.com/python/cpython/commit/72b1d419ac5f7cd9ef82ffd2ffe21aa9b34e21d2


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26985>
_______________________________________

From report at bugs.python.org  Wed Apr 12 23:38:14 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 13 Apr 2017 03:38:14 +0000
Subject: [docs] [issue26985] Information about CodeType in inspect
 documentation is outdated
In-Reply-To: <1462803102.24.0.542356144335.issue26985@psf.upfronthosting.co.za>
Message-ID: <1492054694.93.0.976802920122.issue26985@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26985>
_______________________________________

From report at bugs.python.org  Thu Apr 13 07:30:27 2017
From: report at bugs.python.org (Stefan Krah)
Date: Thu, 13 Apr 2017 11:30:27 +0000
Subject: [docs] [issue30055] Missed testcleanup in decimal.rst
In-Reply-To: <1492009171.7.0.643211980228.issue30055@psf.upfronthosting.co.za>
Message-ID: <1492083027.47.0.250679529514.issue30055@psf.upfronthosting.co.za>


Stefan Krah added the comment:


New changeset 2c0b5c664ba7d36dc09788d3778d5b33e3fa1bd0 by Stefan Krah (Marco Buttu) in branch 'master':
bpo-30055: add testcleanup to leave a fresh context (#1094)
https://github.com/python/cpython/commit/2c0b5c664ba7d36dc09788d3778d5b33e3fa1bd0


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30055>
_______________________________________

From report at bugs.python.org  Thu Apr 13 07:35:49 2017
From: report at bugs.python.org (Stefan Krah)
Date: Thu, 13 Apr 2017 11:35:49 +0000
Subject: [docs] [issue30055] Missed testcleanup in decimal.rst
In-Reply-To: <1492009171.7.0.643211980228.issue30055@psf.upfronthosting.co.za>
Message-ID: <1492083349.15.0.867659523673.issue30055@psf.upfronthosting.co.za>


Stefan Krah added the comment:

Thanks, looks good.  (I hope GitHub runs the doctests at Travis CI, locally most of them failed so I didn't bother to run the tests for this one.)

----------
assignee: docs at python -> skrah
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30055>
_______________________________________

From report at bugs.python.org  Thu Apr 13 07:50:16 2017
From: report at bugs.python.org (Marco Buttu)
Date: Thu, 13 Apr 2017 11:50:16 +0000
Subject: [docs] [issue30055] Missed testcleanup in decimal.rst
In-Reply-To: <1492009171.7.0.643211980228.issue30055@psf.upfronthosting.co.za>
Message-ID: <1492084216.05.0.684421544563.issue30055@psf.upfronthosting.co.za>


Marco Buttu added the comment:

We are not executing the doctests on Travis CI, but I executed them locally.  That's why I realized there was a missed testcleanup.  The issue27200 wants to fix all doctests, and I actually completed the job, but three PRs are still opened, and I am waiting for review approval.  If you want to contribute to the reviews, look for 'bpo-27200' on the GitHub PRs.  I hope the doctest will be run on Travis as soon as possible.  Thanks, Marco

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30055>
_______________________________________

From report at bugs.python.org  Thu Apr 13 08:17:56 2017
From: report at bugs.python.org (John Taylor)
Date: Thu, 13 Apr 2017 12:17:56 +0000
Subject: [docs] [issue29284] Include thread_name_prefix in the
 concurrent.futures.ThreadPoolExecutor example 17.4.2.1
In-Reply-To: <1484584964.59.0.239435362381.issue29284@psf.upfronthosting.co.za>
Message-ID: <1492085876.94.0.670999893526.issue29284@psf.upfronthosting.co.za>


John Taylor added the comment:

Can this be added to Python 3.7?

https://docs.python.org/3.7/library/concurrent.futures.html#threadpoolexecutor-example

Thanks.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29284>
_______________________________________

From report at bugs.python.org  Thu Apr 13 08:23:50 2017
From: report at bugs.python.org (Stefan Krah)
Date: Thu, 13 Apr 2017 12:23:50 +0000
Subject: [docs] [issue30055] Missed testcleanup in decimal.rst
In-Reply-To: <1492084216.05.0.684421544563.issue30055@psf.upfronthosting.co.za>
Message-ID: <20170413122340.GA12572@bytereef.org>


Stefan Krah added the comment:

Ok great, maybe I'll take a look.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30055>
_______________________________________

From report at bugs.python.org  Thu Apr 13 08:31:36 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 13 Apr 2017 12:31:36 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492086696.37.0.393914429888.issue30059@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

There are precedences in tuple.rst and method.rst.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Thu Apr 13 08:48:20 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 13 Apr 2017 12:48:20 +0000
Subject: [docs] [issue29791] print documentation: flush is also a keyword
 argument
In-Reply-To: <1489179993.27.0.31165504732.issue29791@psf.upfronthosting.co.za>
Message-ID: <1492087700.15.0.678335787342.issue29791@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 61b9ac93712df8092a25223cd56fa6528359792b by Berker Peksag in branch 'master':
bpo-29791: Clarify that flush is keyword-only argument (#1093)
https://github.com/python/cpython/commit/61b9ac93712df8092a25223cd56fa6528359792b


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29791>
_______________________________________

From report at bugs.python.org  Thu Apr 13 08:51:59 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 13 Apr 2017 12:51:59 +0000
Subject: [docs] [issue29791] print documentation: flush is also a keyword
 argument
In-Reply-To: <1489179993.27.0.31165504732.issue29791@psf.upfronthosting.co.za>
Message-ID: <1492087919.6.0.902086601468.issue29791@psf.upfronthosting.co.za>


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


----------
pull_requests: +1252

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29791>
_______________________________________

From cxzeng at gmail.com  Tue Apr 11 18:36:30 2017
From: cxzeng at gmail.com (Chenxi Zeng)
Date: Tue, 11 Apr 2017 15:36:30 -0700
Subject: [docs] A typo/bug on Python3 documentation.
Message-ID: <CAAUPu7NAU+MoF_-Cew0Txfo1sagrQqpvk=8EBc2Ok3KJ8y6sCg@mail.gmail.com>

Hi, I find a typo on the page:
https://docs.python.org/3/tutorial/controlflow.html

In section 4.7.7 Function Annotations, the first line of result of 'f('spam')'
should be:

Annotations: {'ham': <class 'str'>, 'eggs': <class 'str'>, 'return': <class
'str'>}

not the one:

Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs':
<class 'str'>}

Please fix this, thank you.


-- 
Best wishes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170411/d3bd35bf/attachment-0001.html>

From emerald_ugo at outlook.com  Tue Apr 11 01:38:00 2017
From: emerald_ugo at outlook.com (Emmanuel Eze)
Date: Tue, 11 Apr 2017 05:38:00 +0000
Subject: [docs] Python tutorial....
Message-ID: <AM4P191MB0132D7F9665FBE6726F7961488000@AM4P191MB0132.EURP191.PROD.OUTLOOK.COM>

I'm a starter 

From marc.nich at icloud.com  Tue Apr 11 19:06:23 2017
From: marc.nich at icloud.com (Marc Nich)
Date: Tue, 11 Apr 2017 19:06:23 -0400
Subject: [docs] Python 2.7 for iOS
Message-ID: <9A998EF8-EAB5-449F-B2E7-AAD9E65242C3@icloud.com>

Thank you for offering this version for iOS.
I am no computer scientist, but I do enjoy programming for fun and I am enrolled in a course. There is an issue in this version that does not allow me to define functions. It continuously finds syntax errors. 
Thank you very much, 
Marc Nich

From mnikulyak at gmail.com  Thu Apr 13 08:30:22 2017
From: mnikulyak at gmail.com (Maksym Nikulyak)
Date: Thu, 13 Apr 2017 15:30:22 +0300
Subject: [docs] A small bug on the "6.2. re" page
Message-ID: <CAD+HHAQv5wT2Xqr77bTuvOejCMUpM4LA7iDVXbnWyK7xRXPixg@mail.gmail.com>

Hi,

On the 3.6.1 documentation's "6.2. re ? Regular expression operations"
page, it is said "... consult the Friedl book referenced above, ...";
however, the actual reference of this book is given below.

Best regards, and great Thank you,
mx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170413/4593f0dc/attachment.html>

From mnikulyak at gmail.com  Thu Apr 13 08:34:52 2017
From: mnikulyak at gmail.com (Maksym Nikulyak)
Date: Thu, 13 Apr 2017 15:34:52 +0300
Subject: [docs] A suggestion re page "6.2. re"
Message-ID: <CAD+HHATXgxZGVR2LRxW07q48e+ygCo_-_pgZ5xwEjw-CA3a90w@mail.gmail.com>

Hi,

On the 3.6.1 documentation's "6.2. re ? Regular expression operations"
page, you might want to mention that, in fact, an

{m,n}?

regex is equivalent to a simpler

{m}

one.

Best regards, and great Thank you,
mx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170413/9b899b31/attachment.html>

From report at bugs.python.org  Thu Apr 13 08:54:48 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 13 Apr 2017 12:54:48 +0000
Subject: [docs] [issue29791] print documentation: flush is also a keyword
 argument
In-Reply-To: <1489179993.27.0.31165504732.issue29791@psf.upfronthosting.co.za>
Message-ID: <1492088088.56.0.380257872726.issue29791@psf.upfronthosting.co.za>


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


----------
pull_requests: +1253

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29791>
_______________________________________

From report at bugs.python.org  Thu Apr 13 09:16:32 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 13 Apr 2017 13:16:32 +0000
Subject: [docs] [issue29791] print documentation: flush is also a keyword
 argument
In-Reply-To: <1489179993.27.0.31165504732.issue29791@psf.upfronthosting.co.za>
Message-ID: <1492089392.19.0.875492746142.issue29791@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset df9783720e40773e7854d2f4e4cfc93f0a2c08b8 by Berker Peksag in branch '3.5':
bpo-29791: Clarify that flush is keyword-only argument (GH-1093)
https://github.com/python/cpython/commit/df9783720e40773e7854d2f4e4cfc93f0a2c08b8


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29791>
_______________________________________

From report at bugs.python.org  Thu Apr 13 09:17:03 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 13 Apr 2017 13:17:03 +0000
Subject: [docs] [issue29791] print documentation: flush is also a keyword
 argument
In-Reply-To: <1489179993.27.0.31165504732.issue29791@psf.upfronthosting.co.za>
Message-ID: <1492089423.94.0.589534657351.issue29791@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 119d94ad37a99ecb0b8329467d04cd9d909e310e by Berker Peksag in branch '3.6':
bpo-29791: Clarify that flush is keyword-only argument (GH-1093)
https://github.com/python/cpython/commit/119d94ad37a99ecb0b8329467d04cd9d909e310e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29791>
_______________________________________

From report at bugs.python.org  Thu Apr 13 09:17:49 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 13 Apr 2017 13:17:49 +0000
Subject: [docs] [issue29791] print documentation: flush is also a keyword
 argument
In-Reply-To: <1489179993.27.0.31165504732.issue29791@psf.upfronthosting.co.za>
Message-ID: <1492089469.29.0.198621419341.issue29791@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the report!

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29791>
_______________________________________

From berker.peksag at gmail.com  Thu Apr 13 09:29:35 2017
From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=)
Date: Thu, 13 Apr 2017 16:29:35 +0300
Subject: [docs] A small bug on the "6.2. re" page
In-Reply-To: <CAD+HHAQv5wT2Xqr77bTuvOejCMUpM4LA7iDVXbnWyK7xRXPixg@mail.gmail.com>
References: <CAD+HHAQv5wT2Xqr77bTuvOejCMUpM4LA7iDVXbnWyK7xRXPixg@mail.gmail.com>
Message-ID: <CAF4280KPO1m0SUQQOqCyxzh4gvSouTPMpzb6XkkNXC9jBULFEQ@mail.gmail.com>

On Thu, Apr 13, 2017 at 3:30 PM, Maksym Nikulyak <mnikulyak at gmail.com> wrote:
> Hi,
>
> On the 3.6.1 documentation's "6.2. re ? Regular expression operations" page,
> it is said "... consult the Friedl book referenced above, ..."; however, the
> actual reference of this book is given below.

Thanks for the report. https://github.com/python/cpython/pull/1113
should correct the typo.

--Berker

From report at bugs.python.org  Thu Apr 13 12:17:39 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 13 Apr 2017 16:17:39 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
In-Reply-To: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>
Message-ID: <1492100258.97.0.581479680452.issue30021@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset 8fc7bc2b7631ee819ee614e47b6f44bacebe1574 by Serhiy Storchaka in branch 'master':
bpo-30021: Add examples for re.escape(). (#1048)
https://github.com/python/cpython/commit/8fc7bc2b7631ee819ee614e47b6f44bacebe1574


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Thu Apr 13 12:25:05 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 13 Apr 2017 16:25:05 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
In-Reply-To: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>
Message-ID: <1492100705.52.0.271137797545.issue30021@psf.upfronthosting.co.za>


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


----------
pull_requests: +1254

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Thu Apr 13 12:31:25 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 13 Apr 2017 16:31:25 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
In-Reply-To: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>
Message-ID: <1492101085.33.0.851882282175.issue30021@psf.upfronthosting.co.za>


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


----------
pull_requests: +1255

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Thu Apr 13 12:41:04 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 13 Apr 2017 16:41:04 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
In-Reply-To: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>
Message-ID: <1492101664.08.0.785088751413.issue30021@psf.upfronthosting.co.za>


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


----------
pull_requests: +1256

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Thu Apr 13 12:41:21 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 13 Apr 2017 16:41:21 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
In-Reply-To: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>
Message-ID: <1492101681.26.0.063885001244.issue30021@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset 936633282220768a6fec9bd6bb53ee9e3ec354df by Serhiy Storchaka in branch '3.6':
bpo-30021: Add examples for re.escape(). (#1048) (#1115)
https://github.com/python/cpython/commit/936633282220768a6fec9bd6bb53ee9e3ec354df


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Thu Apr 13 12:41:28 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 13 Apr 2017 16:41:28 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
In-Reply-To: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>
Message-ID: <1492101688.5.0.776873787678.issue30021@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset e2cf9a918439006fb27f67c1939d0370886650e7 by Serhiy Storchaka in branch '3.5':
bpo-30021: Add examples for re.escape(). (#1048) (#1116)
https://github.com/python/cpython/commit/e2cf9a918439006fb27f67c1939d0370886650e7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Thu Apr 13 12:47:20 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 13 Apr 2017 16:47:20 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
In-Reply-To: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>
Message-ID: <1492102040.54.0.622115549802.issue30021@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset 53ad68434ce914defcc1b734cce4b9b4d79ca3fc by Serhiy Storchaka in branch '2.7':
bpo-30021: Add examples for re.escape(). (#1048) (#1118)
https://github.com/python/cpython/commit/53ad68434ce914defcc1b734cce4b9b4d79ca3fc


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Thu Apr 13 12:57:40 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 13 Apr 2017 16:57:40 +0000
Subject: [docs] [issue30021] Add examples for re.escape()
In-Reply-To: <1491639174.85.0.00703016878323.issue30021@psf.upfronthosting.co.za>
Message-ID: <1492102660.43.0.752372303668.issue30021@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30021>
_______________________________________

From report at bugs.python.org  Fri Apr 14 01:07:23 2017
From: report at bugs.python.org (Howie Benefiel)
Date: Fri, 14 Apr 2017 05:07:23 +0000
Subject: [docs] [issue29651] Inconsistent/undocumented urlsplit/urlparse
 behavior on invalid inputs
In-Reply-To: <1488051927.22.0.367579438822.issue29651@psf.upfronthosting.co.za>
Message-ID: <1492146443.69.0.73245566665.issue29651@psf.upfronthosting.co.za>


Howie Benefiel added the comment:

I'm going to make a note in the documentation. I should have a PR for it in about 1 day.

----------
nosy: +Howie Benefiel

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29651>
_______________________________________

From report at bugs.python.org  Fri Apr 14 01:38:02 2017
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 14 Apr 2017 05:38:02 +0000
Subject: [docs] [issue29651] Inconsistent/undocumented urlsplit/urlparse
 behavior on invalid inputs
In-Reply-To: <1488051927.22.0.367579438822.issue29651@psf.upfronthosting.co.za>
Message-ID: <1492148282.56.0.438750783563.issue29651@psf.upfronthosting.co.za>


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


----------
pull_requests: +1263

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29651>
_______________________________________

From report at bugs.python.org  Fri Apr 14 11:26:20 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 14 Apr 2017 15:26:20 +0000
Subject: [docs] [issue22702] to improve documentation for join() (str method)
In-Reply-To: <1414017441.98.0.187335340973.issue22702@psf.upfronthosting.co.za>
Message-ID: <1492183580.73.0.711569618649.issue22702@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

A reference to the iterable term was added in issue7116 when str.join() started accepting arbitrary iterables rather than just sequences.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue22702>
_______________________________________

From report at bugs.python.org  Fri Apr 14 11:56:11 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 14 Apr 2017 15:56:11 +0000
Subject: [docs] [issue23787] sum() function docstring lists arguments
 incorrectly
In-Reply-To: <1427455446.97.0.658394608092.issue23787@psf.upfronthosting.co.za>
Message-ID: <1492185371.01.0.432482445806.issue23787@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Raymond, could you open a pull request?

----------
keywords: +easy
nosy: +serhiy.storchaka
priority: normal -> low
status: open -> pending

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23787>
_______________________________________

From report at bugs.python.org  Fri Apr 14 15:18:37 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 14 Apr 2017 19:18:37 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492197517.51.0.789544642526.issue30059@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset 0dc5c3169dcd4853612d11ed8c92b12fa210c07f by Serhiy Storchaka (Michael Seifert) in branch 'master':
bpo-30059: Include Py_Ellipsis in C API documentation (#1018)
https://github.com/python/cpython/commit/0dc5c3169dcd4853612d11ed8c92b12fa210c07f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Fri Apr 14 15:42:35 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 14 Apr 2017 19:42:35 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492198955.48.0.670324178468.issue30059@psf.upfronthosting.co.za>


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


----------
stage:  -> backport needed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From berker.peksag at gmail.com  Fri Apr 14 20:14:35 2017
From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=)
Date: Sat, 15 Apr 2017 03:14:35 +0300
Subject: [docs] small doc typo
In-Reply-To: <CA+XNkn02eDRCPA4UM41wpecChOqRwURPYpJPkqjJuvHn965tOg@mail.gmail.com>
References: <CA+XNkn02eDRCPA4UM41wpecChOqRwURPYpJPkqjJuvHn965tOg@mail.gmail.com>
Message-ID: <CAF4280JZyKmk26VFVrBUx2WfqYLSZD90OfsSWnZ2RmSRAnkaRA@mail.gmail.com>

On Tue, Mar 28, 2017 at 3:47 AM, Sean Canavan <seantcanavan at gmail.com> wrote:
> Under
> https://docs.python.org/2/howto/argparse.html#introducing-optional-arguments
>
> "So far we, have been playing with positional arguments" should probably be
> "So far we have been playing with positional arguments"

Hi Sean,

Thanks for the report. I've opened
https://github.com/python/cpython/pull/1141 to fix this.

--Berker

From report at bugs.python.org  Fri Apr 14 20:23:13 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 15 Apr 2017 00:23:13 +0000
Subject: [docs] [issue29651] Inconsistent/undocumented urlsplit/urlparse
 behavior on invalid inputs
In-Reply-To: <1488051927.22.0.367579438822.issue29651@psf.upfronthosting.co.za>
Message-ID: <1492215793.2.0.365859430262.issue29651@psf.upfronthosting.co.za>


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


----------
stage: needs patch -> patch review
versions: +Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29651>
_______________________________________

From report at bugs.python.org  Fri Apr 14 21:16:17 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 15 Apr 2017 01:16:17 +0000
Subject: [docs] [issue10379] locale.format() input regression
In-Reply-To: <1289345606.99.0.972407204822.issue10379@psf.upfronthosting.co.za>
Message-ID: <1492218977.1.0.134156036976.issue10379@psf.upfronthosting.co.za>


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


----------
pull_requests: +1276

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10379>
_______________________________________

From report at bugs.python.org  Fri Apr 14 21:18:45 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 15 Apr 2017 01:18:45 +0000
Subject: [docs] [issue10379] locale.format() input regression
In-Reply-To: <1289345606.99.0.972407204822.issue10379@psf.upfronthosting.co.za>
Message-ID: <1492219124.98.0.0720178346153.issue10379@psf.upfronthosting.co.za>


Berker Peksag added the comment:

I think the solution in PR 259 is great, but I still find the documentation a little bit vague. I've just opened PR 1145 to add some examples specifiers.

----------
nosy: +berker.peksag
stage: needs patch -> patch review
versions: +Python 3.7 -Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10379>
_______________________________________

From report at bugs.python.org  Fri Apr 14 21:38:26 2017
From: report at bugs.python.org (Michael Seifert)
Date: Sat, 15 Apr 2017 01:38:26 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492220306.19.0.676290534569.issue30059@psf.upfronthosting.co.za>


Changes by Michael Seifert <michaelseifert04 at yahoo.de>:


----------
pull_requests: +1278

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Fri Apr 14 21:38:28 2017
From: report at bugs.python.org (Michael Seifert)
Date: Sat, 15 Apr 2017 01:38:28 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492220308.7.0.658588822058.issue30059@psf.upfronthosting.co.za>


Changes by Michael Seifert <michaelseifert04 at yahoo.de>:


----------
pull_requests: +1279

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Fri Apr 14 21:38:50 2017
From: report at bugs.python.org (Michael Seifert)
Date: Sat, 15 Apr 2017 01:38:50 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492220330.04.0.396513963811.issue30059@psf.upfronthosting.co.za>


Changes by Michael Seifert <michaelseifert04 at yahoo.de>:


----------
pull_requests: +1280

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Fri Apr 14 22:03:44 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 15 Apr 2017 02:03:44 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492221824.17.0.652454896073.issue30059@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 05bfbcd233b2f5ba0d0634a380092d6ead6b35e1 by Mariatta (Michael Seifert) in branch '3.6':
[3.6] bpo-30059: Include Py_Ellipsis in C API documentation (GH-1018) (GH-1149)
https://github.com/python/cpython/commit/05bfbcd233b2f5ba0d0634a380092d6ead6b35e1


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Fri Apr 14 22:04:24 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 15 Apr 2017 02:04:24 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492221864.16.0.210346498149.issue30059@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 0b46fcf45afe32402b34240770e01be9b5da3031 by Mariatta (Michael Seifert) in branch '2.7':
[2.7] bpo-30059: Include Py_Ellipsis in C API documentation (GH-1018) (GH-1147)
https://github.com/python/cpython/commit/0b46fcf45afe32402b34240770e01be9b5da3031


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Fri Apr 14 22:05:02 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 15 Apr 2017 02:05:02 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492221902.4.0.647640520436.issue30059@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset f40e72dbe60038eae69bc72e207ac47851d96752 by Mariatta (Michael Seifert) in branch '3.5':
[3.5] bpo-30059: Include Py_Ellipsis in C API documentation (GH-1018) (GH-1148)
https://github.com/python/cpython/commit/f40e72dbe60038eae69bc72e207ac47851d96752


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Fri Apr 14 22:05:54 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sat, 15 Apr 2017 02:05:54 +0000
Subject: [docs] [issue30059] No documentation for C type Py_Ellipsis
In-Reply-To: <1492017917.83.0.872522904102.issue30059@psf.upfronthosting.co.za>
Message-ID: <1492221954.9.0.31771923794.issue30059@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30059>
_______________________________________

From report at bugs.python.org  Fri Apr 14 22:06:05 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 15 Apr 2017 02:06:05 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1492221964.69.0.918410361659.issue19225@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset eaeda64c2fd2abd33e59b03298f9cdc9e8efef89 by Berker Peksag (cocoatomo) in branch 'master':
bpo-19225: Remove duplicated description for standard warning categories (GH-1068)
https://github.com/python/cpython/commit/eaeda64c2fd2abd33e59b03298f9cdc9e8efef89


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Sat Apr 15 03:03:40 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 15 Apr 2017 07:03:40 +0000
Subject: [docs] [issue25632] Document BUILD_*_UNPACK opcodes
In-Reply-To: <1447654337.27.0.0979674663638.issue25632@psf.upfronthosting.co.za>
Message-ID: <1492239820.44.0.37934282431.issue25632@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

They were documented in issue26213.

----------
nosy: +serhiy.storchaka
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Document BUILD_*_UNPACK opcodes

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue25632>
_______________________________________

From report at bugs.python.org  Sat Apr 15 03:06:10 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 15 Apr 2017 07:06:10 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1492239970.87.0.983998647387.issue19184@psf.upfronthosting.co.za>


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


----------
stage:  -> needs patch
versions: +Python 3.5, Python 3.6, Python 3.7 -Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19184>
_______________________________________

From report at bugs.python.org  Sat Apr 15 07:02:27 2017
From: report at bugs.python.org (Kaeptm Blaubaer)
Date: Sat, 15 Apr 2017 11:02:27 +0000
Subject: [docs] [issue29378] Invalid example in documentation for PyErr_Fetch
In-Reply-To: <1485447904.37.0.693014852804.issue29378@psf.upfronthosting.co.za>
Message-ID: <1492254147.53.0.742656652684.issue29378@psf.upfronthosting.co.za>


Kaeptm Blaubaer added the comment:

Please don't close the bug until it is fixed in the python 3.5 documentation!

----------
resolution: not a bug -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29378>
_______________________________________

From report at bugs.python.org  Sat Apr 15 07:35:47 2017
From: report at bugs.python.org (Kaeptm Blaubaer)
Date: Sat, 15 Apr 2017 11:35:47 +0000
Subject: [docs] [issue29378] Invalid example in documentation for PyErr_Fetch
In-Reply-To: <1485447904.37.0.693014852804.issue29378@psf.upfronthosting.co.za>
Message-ID: <1492256147.81.0.436830658268.issue29378@psf.upfronthosting.co.za>


Kaeptm Blaubaer added the comment:

The error is fixed in Python 3.5.3 documentation.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29378>
_______________________________________

From report at bugs.python.org  Sat Apr 15 16:49:45 2017
From: report at bugs.python.org (Ilya Kazakevich)
Date: Sat, 15 Apr 2017 20:49:45 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
Message-ID: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>


New submission from Ilya Kazakevich:

In Py3 it is possible to run test filelike 
"python -m unittest tests/test_something.py" (it is *not* possible in Py2!)
Here is doc: https://docs.python.org/3/library/unittest.html

But "--help" seems to be simply copied from Py2 because it does not have information nor examples about such execution. 

Please add it to "examples" section at least because this type of usage is very useful.

----------
assignee: docs at python
components: Documentation
messages: 291729
nosy: Ilya Kazakevich, docs at python
priority: normal
severity: normal
status: open
title: "-m unittest --help" says nothing about direct script exection
versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Sat Apr 15 17:09:19 2017
From: report at bugs.python.org (R. David Murray)
Date: Sat, 15 Apr 2017 21:09:19 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
In-Reply-To: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>
Message-ID: <1492290559.53.0.0141650097226.issue30078@psf.upfronthosting.co.za>


R. David Murray added the comment:

Agreed that it looks like another example line should be added to the help for this case.

----------
nosy: +r.david.murray
stage:  -> needs patch
versions: +Python 3.7 -Python 3.3, Python 3.4, Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Sat Apr 15 23:10:04 2017
From: report at bugs.python.org (Philip Lee)
Date: Sun, 16 Apr 2017 03:10:04 +0000
Subject: [docs] [issue30079] Explain why it is recommended to pass args as a
 string rather than as a sequence If shell is True
Message-ID: <1492312204.85.0.288489442565.issue30079@psf.upfronthosting.co.za>


New submission from Philip Lee:

The doc here 
https://docs.python.org/3/library/subprocess.html#subprocess.Popen
says :
"If shell is True, it is recommended to pass args as a string rather than as a sequence."
but without explain why ? Please add the explanation !
while in
https://docs.python.org/3/library/subprocess.html#frequently-used-arguments
says:
"args is required for all calls and should be a string, or a sequence of program arguments. Providing a sequence of arguments is generally preferred, as it allows the module to take care of any required escaping and quoting of arguments (e.g. to permit spaces in file names). If passing a single string, either shell must be True (see below) or else the string must simply name the program to be executed without specifying any arguments."

In the case of shell =True ,  I found providing a sequence of arguments  rather than  a string argument can take the advantage of auto escaping and quoting of arguments (e.g. to permit spaces in file names) , so what is the advantage of pass args as a string rather than as a sequence as says in the doc when shell is True?

----------
assignee: docs at python
components: Documentation
messages: 291733
nosy: docs at python, iMath
priority: normal
severity: normal
status: open
title: Explain why it is recommended to pass args as a string rather than as a sequence If shell is True
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30079>
_______________________________________

From report at bugs.python.org  Sun Apr 16 00:19:45 2017
From: report at bugs.python.org (R. David Murray)
Date: Sun, 16 Apr 2017 04:19:45 +0000
Subject: [docs] [issue30079] Explain why it is recommended to pass args as a
 string rather than as a sequence If shell is True
In-Reply-To: <1492312204.85.0.288489442565.issue30079@psf.upfronthosting.co.za>
Message-ID: <1492316385.74.0.948135662162.issue30079@psf.upfronthosting.co.za>


R. David Murray added the comment:

Because passing a sequence to shell=True won't work on unix.  It only works more-or-less by accident on windows, even though the current docs kind of encourage it.  Yes, I think it would be good if these sentences were clarified.

See also issue 7839.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30079>
_______________________________________

From report at bugs.python.org  Sun Apr 16 00:29:43 2017
From: report at bugs.python.org (Louie Lu)
Date: Sun, 16 Apr 2017 04:29:43 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1492316983.88.0.284643987226.issue19184@psf.upfronthosting.co.za>


Changes by Louie Lu <me at louie.lu>:


----------
pull_requests: +1288

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19184>
_______________________________________

From report at bugs.python.org  Sun Apr 16 01:14:03 2017
From: report at bugs.python.org (Eryk Sun)
Date: Sun, 16 Apr 2017 05:14:03 +0000
Subject: [docs] [issue30079] Explain why it is recommended to pass args as a
 string rather than as a sequence If shell is True
In-Reply-To: <1492312204.85.0.288489442565.issue30079@psf.upfronthosting.co.za>
Message-ID: <1492319643.32.0.769540885822.issue30079@psf.upfronthosting.co.za>


Eryk Sun added the comment:

In Unix, passing an args list with shell=True makes the first element the -c command. The remaining elements are arguments for the shell itself, which makes them $N variables. For example:

    >>> subprocess.call(['echo $0, $1', 'spam', 'eggs'], shell=True)
    spam, eggs

In Windows, subprocess.list2cmdline assumes VC++ rules for creating a command line from a list. cmd's parsing rules are very different -- e.g. '^' is the escape character, and double quotes also escape special characters, except not '%'. (Shockingly there is no way to escape '%' on the cmd.exe command line -- only in batch files by doubling it. If you think '^' escapes it, you're wrong. cmd looks for an environment variable containing the '^' character. By luck it's usually not found.) cmd's parsing is convoluted, to say the least. Now combine that with having to pass command lines for external programs in way that they survive cmd's parsing without also breaking how the external program parses its command line. This problem is intractable. Just use a string. For anything complicated you may have to experiment a few times to figure out some permutation that works. The best option is to not use the shell at all.

----------
nosy: +eryksun

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30079>
_______________________________________

From report at bugs.python.org  Sun Apr 16 01:56:14 2017
From: report at bugs.python.org (Louie Lu)
Date: Sun, 16 Apr 2017 05:56:14 +0000
Subject: [docs] [issue28698] Python 3.x ctypes c_wchar_p return is different
 from official documentation example
In-Reply-To: <1479230636.43.0.863548306007.issue28698@psf.upfronthosting.co.za>
Message-ID: <1492322174.55.0.128226617098.issue28698@psf.upfronthosting.co.za>


Changes by Louie Lu <me at louie.lu>:


----------
pull_requests: +1289

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28698>
_______________________________________

From report at bugs.python.org  Sun Apr 16 12:49:50 2017
From: report at bugs.python.org (R. David Murray)
Date: Sun, 16 Apr 2017 16:49:50 +0000
Subject: [docs] [issue30079] Explain why it is recommended to pass args as a
 string rather than as a sequence If shell is True
In-Reply-To: <1492312204.85.0.288489442565.issue30079@psf.upfronthosting.co.za>
Message-ID: <1492361390.81.0.515305960715.issue30079@psf.upfronthosting.co.za>


R. David Murray added the comment:

Note the subtlety here on unix:

rdmurray at pydev:~/python/p36[3.6]>cat temp.sh
#!/bin/bash
echo $0
echo $1

>>> subprocess.call(['./temp.sh', 'spam', 'eggs'], shell=True)
./temp.sh


0
>>> subprocess.call(['./temp.sh $0 $1', 'spam', 'eggs'], shell=True)
./temp.sh
spam
eggs
0

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30079>
_______________________________________

From report at bugs.python.org  Sun Apr 16 12:51:02 2017
From: report at bugs.python.org (R. David Murray)
Date: Sun, 16 Apr 2017 16:51:02 +0000
Subject: [docs] [issue30079] Explain why it is recommended to pass args as a
 string rather than as a sequence If shell is True
In-Reply-To: <1492312204.85.0.288489442565.issue30079@psf.upfronthosting.co.za>
Message-ID: <1492361462.88.0.313821994356.issue30079@psf.upfronthosting.co.za>


R. David Murray added the comment:

Woops, cut and paste error, there should have been an "echo $2" line in that script as well.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30079>
_______________________________________

From report at bugs.python.org  Sun Apr 16 12:57:52 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 16 Apr 2017 16:57:52 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1492361872.8.0.457929457604.issue19184@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

May be just provide Python statements that correspond different numbers of parameters? 0 -- ``raise``, 1 -- ``raise TOS``, 2 -- ``raise TOS1 from TOS``.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19184>
_______________________________________

From report at bugs.python.org  Sun Apr 16 18:02:12 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 16 Apr 2017 22:02:12 +0000
Subject: [docs] [issue23787] sum() function docstring lists arguments
 incorrectly
In-Reply-To: <1427455446.97.0.658394608092.issue23787@psf.upfronthosting.co.za>
Message-ID: <1492380132.67.0.828317642079.issue23787@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

[Serhiy]
> Raymond, could you open a pull request?

Perhaps you could do it for me.  I still haven't had time to wrestle with the github switchover, so I'm effectively crippled for a while.

[Valentine]
> Seems like mentioning string was really a bad idea .... that's
> why I considered the docstring [subtly] wrong.

Not really wrong in a way that confuses typical users.  That docstring has been successfully communicating the basic API for over a decade.

Over time, the docs have slowly converted the old "sequence" references to "iterable".  The docs were never really wrong; instead, we just got more precise by what we meant by sequence versus iterable (i.e. before the ABCs were introduced, the term "sequence" was used in a somewhat generic way to mean "a succession of data values"). 

Also note, it is an interesting paradox that docstrings that are the most helpful to most people most of the time are brief and little loose with terminology.  In general, they reward those who are doing quick lookups for API reminders, but do not reward pedantic close readings.

We'll go ahead and change "sequence" to "iterable" for sum(), but I think that is only a minor win.  The change makes it more technically correct but less friendly to some users (i.e. people need to be taught what "iterable" means while they tend to get the notion of "sequence of values" without any training).

As far as the exclusion of string goes, there were plenty of debate about whether to allow them or to more broadly disallow many data types where summing works quadratically.  The final decision was made by the BDFL and it seems to have been the right decision for just about everyone.  You can take issue with his decision, but that would be pointless.

----------
nosy: +rhettinger
status: pending -> open

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23787>
_______________________________________

From report at bugs.python.org  Sun Apr 16 19:39:06 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 16 Apr 2017 23:39:06 +0000
Subject: [docs] [issue23787] sum() function docstring lists arguments
 incorrectly
In-Reply-To: <1427455446.97.0.658394608092.issue23787@psf.upfronthosting.co.za>
Message-ID: <1492385946.37.0.762955222939.issue23787@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
assignee: docs at python -> Mariatta
nosy: +Mariatta
versions: +Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23787>
_______________________________________

From report at bugs.python.org  Sun Apr 16 21:41:53 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 17 Apr 2017 01:41:53 +0000
Subject: [docs] [issue30051] Document that the random module doesn't support
 fork
In-Reply-To: <1491989089.77.0.552733144958.issue30051@psf.upfronthosting.co.za>
Message-ID: <1492393313.15.0.076151624657.issue30051@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30051>
_______________________________________

From report at bugs.python.org  Sun Apr 16 22:04:36 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 17 Apr 2017 02:04:36 +0000
Subject: [docs] [issue30051] Document that the random module doesn't support
 fork
In-Reply-To: <1491989089.77.0.552733144958.issue30051@psf.upfronthosting.co.za>
Message-ID: <1492394676.93.0.154269220331.issue30051@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Several thoughts:

* AFAICT, in entire the history of this module, no user has ever reported this as being a source of confusion, so I don't think there is a real documentation issue here. 

* Regarding, "after fork, the parent and the child produce the same "random" number sequence", this is the expected behavior of a PRNG.  If it did something thing different, THAT would be a bug.

* There random module is likely the wrong place for a note.   It is more properly a topic about forking itself.  Perhaps there is room for a FAQ entry about forking elaborating on the broad range of state that is shared across forks (lock and file descriptors, etc).

* For those who need it, the API already supports reseeding and a way to make new instances of Random.  Both of those are the standard ways of doing it for people who need independent generators in different threads.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30051>
_______________________________________

From report at bugs.python.org  Sun Apr 16 22:27:09 2017
From: report at bugs.python.org (Steven D'Aprano)
Date: Mon, 17 Apr 2017 02:27:09 +0000
Subject: [docs] [issue30085] Discourage operator.__dunder__ functions
Message-ID: <1492396029.61.0.720198059802.issue30085@psf.upfronthosting.co.za>


New submission from Steven D'Aprano:

As discussed on the Python-Ideas mailing list, it is time to discourage the use of operator.__dunder__ functions. Not to remove them or deprecate them, just change the documentation to make it clear that the dunderless versions are preferred.

Guido +1'ed this suggestion, and there were no objections:

https://mail.python.org/pipermail/python-ideas/2017-April/045424.html

----------
assignee: docs at python
components: Documentation
messages: 291774
nosy: docs at python, ncoghlan, steven.daprano, terry.reedy
priority: normal
severity: normal
status: open
title: Discourage operator.__dunder__ functions

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30085>
_______________________________________

From report at bugs.python.org  Sun Apr 16 23:08:24 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 17 Apr 2017 03:08:24 +0000
Subject: [docs] [issue23787] sum() function docstring lists arguments
 incorrectly
In-Reply-To: <1427455446.97.0.658394608092.issue23787@psf.upfronthosting.co.za>
Message-ID: <1492398504.75.0.838476448746.issue23787@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

I believe this is just a 2.7 issue.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23787>
_______________________________________

From report at bugs.python.org  Mon Apr 17 01:38:40 2017
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 17 Apr 2017 05:38:40 +0000
Subject: [docs] [issue23174] shelve.open fails with error "anydbm.error: db
 type could not be determined"
In-Reply-To: <1420502722.34.0.451688646321.issue23174@psf.upfronthosting.co.za>
Message-ID: <1492407520.94.0.34961166679.issue23174@psf.upfronthosting.co.za>


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


----------
pull_requests: +1291

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23174>
_______________________________________

From report at bugs.python.org  Mon Apr 17 01:38:58 2017
From: report at bugs.python.org (Anand Reddy Pandikunta)
Date: Mon, 17 Apr 2017 05:38:58 +0000
Subject: [docs] [issue23174] shelve.open fails with error "anydbm.error: db
 type could not be determined"
In-Reply-To: <1420502722.34.0.451688646321.issue23174@psf.upfronthosting.co.za>
Message-ID: <1492407538.88.0.787355519964.issue23174@psf.upfronthosting.co.za>


Anand Reddy Pandikunta added the comment:

dbm.whichdb mentions that it returns empty string ('') if the file?s format can?t be guessed. Enhancing exception message should suffice.

----------
nosy: +ChillarAnand

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23174>
_______________________________________

From report at bugs.python.org  Mon Apr 17 01:48:13 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 17 Apr 2017 05:48:13 +0000
Subject: [docs] [issue23174] shelve.open fails with error "anydbm.error: db
 type could not be determined"
In-Reply-To: <1420502722.34.0.451688646321.issue23174@psf.upfronthosting.co.za>
Message-ID: <1492408093.26.0.804423890452.issue23174@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Proposed error message isn't correct. The file extension is not the only method for determining db type.

Current error message looks good to me and I don't see how it can be enhanced.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23174>
_______________________________________

From report at bugs.python.org  Mon Apr 17 03:36:49 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 17 Apr 2017 07:36:49 +0000
Subject: [docs] [issue30051] Document that the random module doesn't support
 fork
In-Reply-To: <1491989089.77.0.552733144958.issue30051@psf.upfronthosting.co.za>
Message-ID: <1492414609.74.0.877353433262.issue30051@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

os.fork() documentation contains a warning that refers to ssl documentation where the use of OpenSSL?s internal random number generator in forked processes is documented more detailed. I think the same should be added for the random module.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30051>
_______________________________________

From report at bugs.python.org  Mon Apr 17 07:44:54 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 17 Apr 2017 11:44:54 +0000
Subject: [docs] [issue23174] shelve.open fails with error "anydbm.error: db
 type could not be determined"
In-Reply-To: <1420502722.34.0.451688646321.issue23174@psf.upfronthosting.co.za>
Message-ID: <1492429493.89.0.158520390159.issue23174@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

[Serhiy]
> Current error message looks good to me and I don't see how
> it can be enhanced.

I concur with Serhiy and David.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23174>
_______________________________________

From report at bugs.python.org  Mon Apr 17 07:46:37 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 17 Apr 2017 11:46:37 +0000
Subject: [docs] [issue30051] Document that the random module doesn't support
 fork
In-Reply-To: <1491989089.77.0.552733144958.issue30051@psf.upfronthosting.co.za>
Message-ID: <1492429597.59.0.648426769235.issue30051@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> os.fork() documentation contains a warning that refers to ssl
> documentation where the use of OpenSSL?s internal random number
> generator in forked processes is documented more detailed. 
> I think the same should be added for the random module.

+1 It is reasonable to extend the docs for os.fork().

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30051>
_______________________________________

From report at bugs.python.org  Mon Apr 17 23:57:09 2017
From: report at bugs.python.org (Jim DeLaHunt)
Date: Tue, 18 Apr 2017 03:57:09 +0000
Subject: [docs] [issue29428] Doctest documentation unclear about multi-line
 fixtures
In-Reply-To: <1486103112.9.0.326343032946.issue29428@psf.upfronthosting.co.za>
Message-ID: <1492487829.71.0.939465254125.issue29428@psf.upfronthosting.co.za>


Jim DeLaHunt added the comment:

Bump. Could I get a few more eyes looking at the current state of https://github.com/python/cpython/pull/45/ ? 

* @bitdancer made some suggestions. I accepted some, and replied to others where I think we should keep looking for common ground. I'd like to see replies.

* I've made changes in response to other comments.

I think pull/45 represents a targeted set of changes to those parts of the module documentation which are particularly unclear. It is not a wholesale re-write; that's a task for a different time. I believe it is responsive to comments so far. I'd appreciate more eyes to help arrive at consensus on those improvements where we can. 

Thank you!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29428>
_______________________________________

From report at bugs.python.org  Tue Apr 18 15:45:51 2017
From: report at bugs.python.org (Sanket Dasgupta)
Date: Tue, 18 Apr 2017 19:45:51 +0000
Subject: [docs] [issue30085] Discourage operator.__dunder__ functions
In-Reply-To: <1492396029.61.0.720198059802.issue30085@psf.upfronthosting.co.za>
Message-ID: <1492544751.16.0.348976957826.issue30085@psf.upfronthosting.co.za>


Changes by Sanket Dasgupta <sanketdasgupta at gmail.com>:


----------
pull_requests: +1301

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30085>
_______________________________________

From report at bugs.python.org  Tue Apr 18 15:51:38 2017
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 18 Apr 2017 19:51:38 +0000
Subject: [docs] [issue30096] Update examples in abc documentation to use
 abc.ABC
Message-ID: <1492545098.58.0.705598301268.issue30096@psf.upfronthosting.co.za>


New submission from Brett Cannon:

I noticed that the documentation for the abc module (https://docs.python.org/3/library/abc.html) has all example classes use ABCMeta instead of ABC which is what most people probably want. To keep things simple the docs should probably be updated to inherit from abc.ABC.

----------
assignee: docs at python
components: Documentation
messages: 291842
nosy: brett.cannon, docs at python
priority: normal
severity: normal
stage: needs patch
status: open
title: Update examples in abc documentation to use abc.ABC
type: enhancement
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30096>
_______________________________________

From report at bugs.python.org  Tue Apr 18 17:28:05 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 18 Apr 2017 21:28:05 +0000
Subject: [docs] [issue30096] Update examples in abc documentation to use
 abc.ABC
In-Reply-To: <1492545098.58.0.705598301268.issue30096@psf.upfronthosting.co.za>
Message-ID: <1492550885.47.0.521379696174.issue30096@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

+1 It would be nice to have the examples show the usual best practices.

That said, in the doc for abc.ABC itself, it would be nice to show an brief example both ways (much like we do for the property() docstring) to show the relationship between the two.  In other words, I want people to inherit from ABC but don't want the knowledge of ABCMeta to be lost.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30096>
_______________________________________

From report at bugs.python.org  Wed Apr 19 07:07:42 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 19 Apr 2017 11:07:42 +0000
Subject: [docs] [issue28698] Python 3.x ctypes c_wchar_p return is different
 from official documentation example
In-Reply-To: <1479230636.43.0.863548306007.issue28698@psf.upfronthosting.co.za>
Message-ID: <1492600062.37.0.822257467099.issue28698@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28698>
_______________________________________

From report at bugs.python.org  Wed Apr 19 10:16:41 2017
From: report at bugs.python.org (Louie Lu)
Date: Wed, 19 Apr 2017 14:16:41 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
In-Reply-To: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>
Message-ID: <1492611401.09.0.456862848527.issue30078@psf.upfronthosting.co.za>


Changes by Louie Lu <me at louie.lu>:


----------
pull_requests: +1306

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Wed Apr 19 10:17:19 2017
From: report at bugs.python.org (Louie Lu)
Date: Wed, 19 Apr 2017 14:17:19 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
In-Reply-To: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>
Message-ID: <1492611439.39.0.747537755901.issue30078@psf.upfronthosting.co.za>


Louie Lu added the comment:

Add a simple line to `MAIN_EXAMPLES`:

"%(prog)s path/to/test_file.py      - run tests from test_file.py"

----------
nosy: +louielu

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Wed Apr 19 12:32:35 2017
From: report at bugs.python.org (Louie Lu)
Date: Wed, 19 Apr 2017 16:32:35 +0000
Subject: [docs] [issue21150] Add quick links table to argparse docs
In-Reply-To: <1396558035.28.0.485991636726.issue21150@psf.upfronthosting.co.za>
Message-ID: <1492619555.85.0.683208687843.issue21150@psf.upfronthosting.co.za>


Changes by Louie Lu <me at louie.lu>:


----------
nosy: +louielu

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21150>
_______________________________________

From report at bugs.python.org  Wed Apr 19 12:43:44 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 19 Apr 2017 16:43:44 +0000
Subject: [docs] [issue21150] Add quick links table to argparse docs
In-Reply-To: <1396558035.28.0.485991636726.issue21150@psf.upfronthosting.co.za>
Message-ID: <1492620224.31.0.447346026689.issue21150@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Gaurav, overall this looks nice.  

I would drop the example column because it will make the row too wide for viewing.  Alternatively, put the examples in a separate table (as was done for the combinatoric functions in the itertools docs: https://docs.python.org/3/library/itertools.html#module-itertools ).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21150>
_______________________________________

From report at bugs.python.org  Wed Apr 19 12:44:07 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 19 Apr 2017 16:44:07 +0000
Subject: [docs] [issue21150] Add quick links table to argparse docs
In-Reply-To: <1396558035.28.0.485991636726.issue21150@psf.upfronthosting.co.za>
Message-ID: <1492620247.92.0.706288789592.issue21150@psf.upfronthosting.co.za>


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


----------
nosy: +bethard

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21150>
_______________________________________

From erik.sommer at posteo.de  Wed Apr 19 15:47:23 2017
From: erik.sommer at posteo.de (Erik Sommer)
Date: Wed, 19 Apr 2017 22:47:23 +0300
Subject: [docs] Bug in
 https://docs.python.org/3.6/tutorial/introduction.html#strings
Message-ID: <534D9E88-11BA-4ECE-8FC3-3449370AEB7D@posteo.de>

In the first Codeblock at the sixth example it should be:

>>> '"Isn\'t," she said.' 
'"Isn't," she said.'

In the current version the answer of the interpreter shows the backslash character as well. That's not correct.

Best Regards 
Erik Sommer 
-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170419/2cd7db07/attachment.html>

From zachary.ware+pydocs at gmail.com  Wed Apr 19 15:57:07 2017
From: zachary.ware+pydocs at gmail.com (Zachary Ware)
Date: Wed, 19 Apr 2017 14:57:07 -0500
Subject: [docs] Bug in
 https://docs.python.org/3.6/tutorial/introduction.html#strings
In-Reply-To: <534D9E88-11BA-4ECE-8FC3-3449370AEB7D@posteo.de>
References: <534D9E88-11BA-4ECE-8FC3-3449370AEB7D@posteo.de>
Message-ID: <CAKJDb-M=H8n7R=-x-cckrskv0x5gQrGT_aQfnWCHf8PekyR81Q@mail.gmail.com>

Hi Erik,

On Wed, Apr 19, 2017 at 2:47 PM, Erik Sommer <erik.sommer at posteo.de> wrote:
> In the first Codeblock at the sixth example it should be:
>
>>>> '"Isn\'t," she said.'
> '"Isn't," she said.'
>
> In the current version the answer of the interpreter shows the backslash
> character as well. That's not correct.

The example is correct as is, try it for yourself!  Also have a look
at the following paragraph and example which explain what's going on
there.

Thanks for your report,
-- 
Zach

From report at bugs.python.org  Wed Apr 19 17:58:35 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 19 Apr 2017 21:58:35 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
In-Reply-To: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>
Message-ID: <1492639115.23.0.353461477431.issue30078@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti, michael.foord, rbcollins
stage: needs patch -> patch review

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Wed Apr 19 22:59:26 2017
From: report at bugs.python.org (KINEBUCHI Tomohiko)
Date: Thu, 20 Apr 2017 02:59:26 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1492657166.67.0.232413701393.issue19225@psf.upfronthosting.co.za>


Changes by KINEBUCHI Tomohiko <cocoatomo77 at gmail.com>:


----------
pull_requests: +1324

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Wed Apr 19 23:00:23 2017
From: report at bugs.python.org (KINEBUCHI Tomohiko)
Date: Thu, 20 Apr 2017 03:00:23 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1492657223.18.0.884855930503.issue19225@psf.upfronthosting.co.za>


Changes by KINEBUCHI Tomohiko <cocoatomo77 at gmail.com>:


----------
pull_requests: +1325

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Wed Apr 19 23:01:46 2017
From: report at bugs.python.org (KINEBUCHI Tomohiko)
Date: Thu, 20 Apr 2017 03:01:46 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1492657306.86.0.19116218787.issue19225@psf.upfronthosting.co.za>


Changes by KINEBUCHI Tomohiko <cocoatomo77 at gmail.com>:


----------
pull_requests: +1326

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Wed Apr 19 23:47:02 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 03:47:02 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
In-Reply-To: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>
Message-ID: <1492660021.79.0.984345217795.issue30078@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset f7e62cf8adfb8ab6a6a870903defe8ff218a0383 by Berker Peksag (Louie Lu) in branch 'master':
bpo-30078: Add an example of passing a path to unittest (#1178)
https://github.com/python/cpython/commit/f7e62cf8adfb8ab6a6a870903defe8ff218a0383


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Wed Apr 19 23:49:38 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 03:49:38 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
In-Reply-To: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>
Message-ID: <1492660178.4.0.271362488514.issue30078@psf.upfronthosting.co.za>


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


----------
pull_requests: +1327

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Wed Apr 19 23:51:13 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 03:51:13 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
In-Reply-To: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>
Message-ID: <1492660273.76.0.283190999807.issue30078@psf.upfronthosting.co.za>


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


----------
pull_requests: +1328

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Wed Apr 19 23:54:08 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 03:54:08 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1492660448.36.0.060535342947.issue19225@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 5fb4bf91e78e128a22b5b58da179f09d0b307f2d by Berker Peksag (cocoatomo) in branch '3.6':
bpo-19225: Remove duplicated description for standard warning categories (GH-1068)
https://github.com/python/cpython/commit/5fb4bf91e78e128a22b5b58da179f09d0b307f2d


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Wed Apr 19 23:56:07 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 03:56:07 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1492660567.27.0.92036963863.issue19225@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 7e56fe35efe3aef0b9aac989255c4f13dfc01b09 by Berker Peksag (cocoatomo) in branch '3.5':
bpo-19225: Remove duplicated description for standard warning categories (GH-1068)
https://github.com/python/cpython/commit/7e56fe35efe3aef0b9aac989255c4f13dfc01b09


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Wed Apr 19 23:57:23 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 03:57:23 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1492660643.65.0.743051370856.issue19225@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 450a69c6a4bfee6a10cbcc0c43b221bb135689c8 by Berker Peksag (cocoatomo) in branch '2.7':
bpo-19225: Remove duplicated description for standard warning categories (GH-1068)
https://github.com/python/cpython/commit/450a69c6a4bfee6a10cbcc0c43b221bb135689c8


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Wed Apr 19 23:58:48 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 03:58:48 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1492660728.54.0.137521749123.issue19225@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the backport PRs!

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19225>
_______________________________________

From report at bugs.python.org  Thu Apr 20 00:36:59 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 04:36:59 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
In-Reply-To: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>
Message-ID: <1492663019.76.0.330767683681.issue30078@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 596e714d79a22d1d53f26ae1a579dcd43f15865a by Berker Peksag in branch '3.6':
bpo-30078: Add an example of passing a path to unittest (GH-1178)
https://github.com/python/cpython/commit/596e714d79a22d1d53f26ae1a579dcd43f15865a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Thu Apr 20 00:37:20 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 04:37:20 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
In-Reply-To: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>
Message-ID: <1492663040.26.0.228856830145.issue30078@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 6fb0f801d73b1e2794888772d016d978eccf52a6 by Berker Peksag in branch '3.5':
bpo-30078: Add an example of passing a path to unittest (GH-1178)
https://github.com/python/cpython/commit/6fb0f801d73b1e2794888772d016d978eccf52a6


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Thu Apr 20 00:37:46 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 04:37:46 +0000
Subject: [docs] [issue30078] "-m unittest --help" says nothing about direct
 script exection
In-Reply-To: <1492289385.37.0.918058800689.issue30078@psf.upfronthosting.co.za>
Message-ID: <1492663066.59.0.123549317437.issue30078@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks!

----------
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed
type:  -> enhancement
versions: +Python 3.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30078>
_______________________________________

From report at bugs.python.org  Thu Apr 20 00:38:45 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 04:38:45 +0000
Subject: [docs] [issue10379] locale.format() input regression
In-Reply-To: <1289345606.99.0.972407204822.issue10379@psf.upfronthosting.co.za>
Message-ID: <1492663125.54.0.329555676298.issue10379@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 6dbdedb0b18a5ca850ab8ce512fda24d5a9d0688 by Berker Peksag in branch 'master':
bpo-10379: Add %char examples to locale.format() docs (GH-1145)
https://github.com/python/cpython/commit/6dbdedb0b18a5ca850ab8ce512fda24d5a9d0688


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10379>
_______________________________________

From report at bugs.python.org  Thu Apr 20 00:39:00 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 20 Apr 2017 04:39:00 +0000
Subject: [docs] [issue10379] locale.format() input regression
In-Reply-To: <1289345606.99.0.972407204822.issue10379@psf.upfronthosting.co.za>
Message-ID: <1492663140.42.0.548026802011.issue10379@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10379>
_______________________________________

From report at bugs.python.org  Thu Apr 20 02:06:50 2017
From: report at bugs.python.org (Louie Lu)
Date: Thu, 20 Apr 2017 06:06:50 +0000
Subject: [docs] [issue21150] Add quick links table to argparse docs
In-Reply-To: <1396558035.28.0.485991636726.issue21150@psf.upfronthosting.co.za>
Message-ID: <1492668410.14.0.268556300693.issue21150@psf.upfronthosting.co.za>


Changes by Louie Lu <me at louie.lu>:


----------
pull_requests: +1332

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21150>
_______________________________________

From report at bugs.python.org  Thu Apr 20 12:13:49 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 20 Apr 2017 16:13:49 +0000
Subject: [docs] [issue29387] Tabs vs spaces FAQ out of date
In-Reply-To: <1485734038.81.0.0566253928841.issue29387@psf.upfronthosting.co.za>
Message-ID: <1492704829.57.0.93170576864.issue29387@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29387>
_______________________________________

From report at bugs.python.org  Thu Apr 20 14:33:57 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 20 Apr 2017 18:33:57 +0000
Subject: [docs] [issue30085] Discourage operator.__dunder__ functions
In-Reply-To: <1492396029.61.0.720198059802.issue30085@psf.upfronthosting.co.za>
Message-ID: <1492713237.5.0.0986060878828.issue30085@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

My suggestion from the python-ideas thread:: replace the current

"The function names are those used for special class methods; variants without leading and trailing __ are also provided for convenience."

with

""Many function names are those used for special methods, minus the double underscores.  For backward compatibility, many of these have a variant with the double underscores kept.  We recommend using the dunderless form.  Note that operator.__add__(x, y), for instance, being the same as x + y, is not the same as x.__add__(y)."

Possibly add ", since the first two may result in calling y.__radd__(x)".



Raymond assigned the

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30085>
_______________________________________

From report at bugs.python.org  Thu Apr 20 14:48:47 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 20 Apr 2017 18:48:47 +0000
Subject: [docs] [issue30085] Discourage operator.__dunder__ functions
In-Reply-To: <1492396029.61.0.720198059802.issue30085@psf.upfronthosting.co.za>
Message-ID: <1492714127.48.0.875888687019.issue30085@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Raymond assigned the PR to himself, so I added him here as nosy and assignee.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30085>
_______________________________________

From report at bugs.python.org  Thu Apr 20 17:26:04 2017
From: report at bugs.python.org (Eric Appelt)
Date: Thu, 20 Apr 2017 21:26:04 +0000
Subject: [docs] [issue30096] Update examples in abc documentation to use
 abc.ABC
In-Reply-To: <1492545098.58.0.705598301268.issue30096@psf.upfronthosting.co.za>
Message-ID: <1492723564.38.0.383651405897.issue30096@psf.upfronthosting.co.za>


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


----------
pull_requests: +1343

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30096>
_______________________________________

From report at bugs.python.org  Thu Apr 20 17:30:24 2017
From: report at bugs.python.org (Eric Appelt)
Date: Thu, 20 Apr 2017 21:30:24 +0000
Subject: [docs] [issue30096] Update examples in abc documentation to use
 abc.ABC
In-Reply-To: <1492545098.58.0.705598301268.issue30096@psf.upfronthosting.co.za>
Message-ID: <1492723824.77.0.620789527212.issue30096@psf.upfronthosting.co.za>


Eric Appelt added the comment:

I created a PR to update the documentation to use this pattern and follow Raymond's suggestion of showing both ways to define an abc.

In order to make the examples comprehensible when read from beginning to end, I reordered the classes so that abc.ABC is described first.

----------
nosy: +Eric Appelt

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30096>
_______________________________________

From report at bugs.python.org  Fri Apr 21 00:03:19 2017
From: report at bugs.python.org (Decorater)
Date: Fri, 21 Apr 2017 04:03:19 +0000
Subject: [docs] [issue30122] Added missing things to Windows docs.
Message-ID: <1492747399.44.0.402463454209.issue30122@psf.upfronthosting.co.za>


New submission from Decorater:

I realized the Windows docs lacked some information so I added it. I will try to create an cherry pick for 3.6 and 3.6 as well. Also if desired I could also see if it can be applied to the 2.7 branch as well.

----------
assignee: docs at python
components: Documentation
messages: 292005
nosy: Decorater, docs at python
priority: normal
severity: normal
status: open
title: Added missing things to Windows docs.
versions: Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30122>
_______________________________________

From report at bugs.python.org  Fri Apr 21 00:03:31 2017
From: report at bugs.python.org (Decorater)
Date: Fri, 21 Apr 2017 04:03:31 +0000
Subject: [docs] [issue30122] Added missing things to Windows docs.
In-Reply-To: <1492747399.44.0.402463454209.issue30122@psf.upfronthosting.co.za>
Message-ID: <1492747411.29.0.836940336598.issue30122@psf.upfronthosting.co.za>


Changes by Decorater <seandhunt_7 at yahoo.com>:


----------
pull_requests: +1347

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30122>
_______________________________________

From report at bugs.python.org  Fri Apr 21 00:19:08 2017
From: report at bugs.python.org (Decorater)
Date: Fri, 21 Apr 2017 04:19:08 +0000
Subject: [docs] [issue30122] Added missing things to Windows docs.
In-Reply-To: <1492747399.44.0.402463454209.issue30122@psf.upfronthosting.co.za>
Message-ID: <1492748348.45.0.659604621511.issue30122@psf.upfronthosting.co.za>


Changes by Decorater <seandhunt_7 at yahoo.com>:


----------
pull_requests: +1348

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30122>
_______________________________________

From report at bugs.python.org  Fri Apr 21 00:22:47 2017
From: report at bugs.python.org (Decorater)
Date: Fri, 21 Apr 2017 04:22:47 +0000
Subject: [docs] [issue30122] Added missing things to Windows docs.
In-Reply-To: <1492747399.44.0.402463454209.issue30122@psf.upfronthosting.co.za>
Message-ID: <1492748567.34.0.661167497347.issue30122@psf.upfronthosting.co.za>


Changes by Decorater <seandhunt_7 at yahoo.com>:


----------
pull_requests: +1349

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30122>
_______________________________________

From report at bugs.python.org  Fri Apr 21 00:39:14 2017
From: report at bugs.python.org (Decorater)
Date: Fri, 21 Apr 2017 04:39:14 +0000
Subject: [docs] [issue30122] Added missing archive programs and close option
 to Windows docs.
In-Reply-To: <1492747399.44.0.402463454209.issue30122@psf.upfronthosting.co.za>
Message-ID: <1492749554.12.0.0409963755606.issue30122@psf.upfronthosting.co.za>


Changes by Decorater <seandhunt_7 at yahoo.com>:


----------
title: Added missing things to Windows docs. -> Added missing archive programs and close option to Windows docs.

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30122>
_______________________________________

From report at bugs.python.org  Fri Apr 21 09:09:52 2017
From: report at bugs.python.org (R. David Murray)
Date: Fri, 21 Apr 2017 13:09:52 +0000
Subject: [docs] [issue30122] Added missing archive programs and close option
 to Windows docs.
In-Reply-To: <1492747399.44.0.402463454209.issue30122@psf.upfronthosting.co.za>
Message-ID: <1492780192.43.0.893157810977.issue30122@psf.upfronthosting.co.za>


R. David Murray added the comment:

Please close the redundant PRs.  I've commented on pr1228.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30122>
_______________________________________

From report at bugs.python.org  Fri Apr 21 09:11:20 2017
From: report at bugs.python.org (R. David Murray)
Date: Fri, 21 Apr 2017 13:11:20 +0000
Subject: [docs] [issue30122] Added missing archive programs and close option
 to Windows docs.
In-Reply-To: <1492747399.44.0.402463454209.issue30122@psf.upfronthosting.co.za>
Message-ID: <1492780280.29.0.853643845136.issue30122@psf.upfronthosting.co.za>


R. David Murray added the comment:

To be clear: backport PRs should be created only after a PR has been approved.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30122>
_______________________________________

From report at bugs.python.org  Fri Apr 21 09:18:20 2017
From: report at bugs.python.org (R. David Murray)
Date: Fri, 21 Apr 2017 13:18:20 +0000
Subject: [docs] [issue30122] Added missing archive programs and close option
 to Windows docs.
In-Reply-To: <1492747399.44.0.402463454209.issue30122@psf.upfronthosting.co.za>
Message-ID: <1492780700.88.0.0918090186996.issue30122@psf.upfronthosting.co.za>


R. David Murray added the comment:

Also, please review the (newly rewritten) section in the devguide about PRs.  I see now that there were changes made from the original here already, but I don't see the commits that made those changes.  The history of changes should be kept during PR development (they get squashed at the end).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30122>
_______________________________________

From report at bugs.python.org  Fri Apr 21 09:20:52 2017
From: report at bugs.python.org (Diego Costantini)
Date: Fri, 21 Apr 2017 13:20:52 +0000
Subject: [docs] [issue30127] argparse action not correctly describing the
 right behavior
Message-ID: <1492780852.4.0.162539678149.issue30127@psf.upfronthosting.co.za>


New submission from Diego Costantini:

Here https://docs.python.org/2/library/argparse.html#action we have the following:

>>> parser = argparse.ArgumentParser()
>>> parser.add_argument('--foo', action='store_true')
>>> parser.add_argument('--bar', action='store_false')
>>> parser.add_argument('--baz', action='store_false')
>>> parser.parse_args('--foo --bar'.split())
Namespace(bar=False, baz=True, foo=True)

baz should be False because omitted.
I also tested it.

----------
assignee: docs at python
components: Documentation
messages: 292044
nosy: Diego Costantini, docs at python
priority: normal
severity: normal
status: open
title: argparse action not correctly describing the right behavior
type: behavior
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30127>
_______________________________________

From report at bugs.python.org  Fri Apr 21 09:28:01 2017
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 21 Apr 2017 13:28:01 +0000
Subject: [docs] [issue30127] argparse action not correctly describing the
 right behavior
In-Reply-To: <1492780852.4.0.162539678149.issue30127@psf.upfronthosting.co.za>
Message-ID: <1492781281.92.0.597731514169.issue30127@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

I think the example is correct. Because baz's action is store_false, the default is True. So if baz is omitted, it should have a True value. That's what the example shows, and what I see when I run this code.

Can you show what you tested, what you saw, and what you expected?

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30127>
_______________________________________

From report at bugs.python.org  Fri Apr 21 09:44:59 2017
From: report at bugs.python.org (Diego Costantini)
Date: Fri, 21 Apr 2017 13:44:59 +0000
Subject: [docs] [issue30127] argparse action not correctly describing the
 right behavior
In-Reply-To: <1492780852.4.0.162539678149.issue30127@psf.upfronthosting.co.za>
Message-ID: <1492782299.51.0.657759979429.issue30127@psf.upfronthosting.co.za>


Diego Costantini added the comment:

You are right, I misunderstood the part where it sets defaults opposite to the stored value, although apparently over one year ago I did understand it correctly when I first went through that documentation.

Today my second pair of eyes had my same understanding of it though :)

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30127>
_______________________________________

From report at bugs.python.org  Fri Apr 21 10:27:21 2017
From: report at bugs.python.org (Ralph Corderoy)
Date: Fri, 21 Apr 2017 14:27:21 +0000
Subject: [docs] [issue30128] xid_start definition for Unicode identifiers
 refers to xid_continue
Message-ID: <1492784841.26.0.847903278881.issue30128@psf.upfronthosting.co.za>


New submission from Ralph Corderoy:

https://docs.python.org/3/reference/lexical_analysis.html#identifiers has a grammar.

    identifier   ::=  xid_start xid_continue*
    id_start     ::=  <all characters in general categories Lu, Ll, Lt, Lm, Lo, Nl, the underscore, and characters with the Other_ID_Start property>
    id_continue  ::=  <all characters in id_start, plus characters in the categories Mn, Mc, Nd, Pc and others with the Other_ID_Continue property>
    xid_start    ::=  <all characters in id_start whose NFKC normalization is in "id_start xid_continue*">
    xid_continue ::=  <all characters in id_continue whose NFKC normalization is in "id_continue*">

I struggle to make sense of it unless I remove `xid_continue*' from `xid_start's definition.
I suspect it ended up there due to cut and paste.

----------
assignee: docs at python
components: Documentation
messages: 292049
nosy: docs at python, ralph.corderoy
priority: normal
severity: normal
status: open
title: xid_start definition for Unicode identifiers refers to xid_continue
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30128>
_______________________________________

From report at bugs.python.org  Fri Apr 21 12:28:48 2017
From: report at bugs.python.org (Sanket Dasgupta)
Date: Fri, 21 Apr 2017 16:28:48 +0000
Subject: [docs] [issue30085] Discourage operator.__dunder__ functions
In-Reply-To: <1492396029.61.0.720198059802.issue30085@psf.upfronthosting.co.za>
Message-ID: <1492792128.06.0.796676986346.issue30085@psf.upfronthosting.co.za>


Sanket Dasgupta added the comment:

@terry, I have updated the same, thanks!

----------
nosy: +sanketdg

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30085>
_______________________________________

From report at bugs.python.org  Fri Apr 21 14:13:30 2017
From: report at bugs.python.org (Decorater)
Date: Fri, 21 Apr 2017 18:13:30 +0000
Subject: [docs] [issue30122] Added missing archive programs.
In-Reply-To: <1492747399.44.0.402463454209.issue30122@psf.upfronthosting.co.za>
Message-ID: <1492798410.2.0.875306575851.issue30122@psf.upfronthosting.co.za>


Decorater added the comment:

Oh

----------
title: Added missing archive programs and close option to Windows docs. -> Added missing archive programs.

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30122>
_______________________________________

From report at bugs.python.org  Fri Apr 21 23:10:23 2017
From: report at bugs.python.org (KINEBUCHI Tomohiko)
Date: Sat, 22 Apr 2017 03:10:23 +0000
Subject: [docs] [issue29952] "keys and values" preferred to "keys and
 elements" for dict constituent
In-Reply-To: <1490931613.41.0.406216073022.issue29952@psf.upfronthosting.co.za>
Message-ID: <1492830623.2.0.141275689353.issue29952@psf.upfronthosting.co.za>


Changes by KINEBUCHI Tomohiko <cocoatomo77 at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29952>
_______________________________________

From report at bugs.python.org  Fri Apr 21 23:49:31 2017
From: report at bugs.python.org (KINEBUCHI Tomohiko)
Date: Sat, 22 Apr 2017 03:49:31 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
Message-ID: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>


New submission from KINEBUCHI Tomohiko:

In Python 2.6, BytesWarning was added, but a description of that warning is missing from the document, library/exceptions.rst.

----------
assignee: docs at python
components: Documentation
messages: 292099
nosy: cocoatomo, docs at python
priority: normal
severity: normal
status: open
title: BytesWarning is missing from the documents
versions: Python 2.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30134>
_______________________________________

From report at bugs.python.org  Fri Apr 21 23:57:05 2017
From: report at bugs.python.org (KINEBUCHI Tomohiko)
Date: Sat, 22 Apr 2017 03:57:05 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1492833425.32.0.9007778433.issue30134@psf.upfronthosting.co.za>


Changes by KINEBUCHI Tomohiko <cocoatomo77 at gmail.com>:


----------
pull_requests: +1365

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30134>
_______________________________________

From report at bugs.python.org  Sat Apr 22 00:41:59 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 22 Apr 2017 04:41:59 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1492836119.73.0.868326084231.issue30134@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

BytesWarning should be added in the table in warnings.rst (and check that all other built-in warning categories are in this table). It is worth to mention the -b option.

And I think the docstring of BytesWarning should be corrected. "Unicode" should be used rather that "str" since str and bytes is the same in 2.7.

----------
nosy: +benjamin.peterson, r.david.murray, serhiy.storchaka
stage:  -> patch review
type:  -> enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30134>
_______________________________________

From report at bugs.python.org  Sat Apr 22 01:02:59 2017
From: report at bugs.python.org (Louie Lu)
Date: Sat, 22 Apr 2017 05:02:59 +0000
Subject: [docs] [issue30136] Add test.support.script_helper to documentation
Message-ID: <1492837378.99.0.351852944309.issue30136@psf.upfronthosting.co.za>


New submission from Louie Lu:

`test.support.script_helper` didn't document at `test` document.

It should be add on.

----------
assignee: docs at python
components: Documentation
messages: 292103
nosy: docs at python, louielu
priority: normal
severity: normal
status: open
title: Add test.support.script_helper to documentation
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30136>
_______________________________________

From report at bugs.python.org  Sat Apr 22 01:15:27 2017
From: report at bugs.python.org (Berker Peksag)
Date: Sat, 22 Apr 2017 05:15:27 +0000
Subject: [docs] [issue30136] Add test.support.script_helper to documentation
In-Reply-To: <1492837378.99.0.351852944309.issue30136@psf.upfronthosting.co.za>
Message-ID: <1492838127.95.0.203275226336.issue30136@psf.upfronthosting.co.za>


Berker Peksag added the comment:

This is a duplicate of issue 18576.

----------
nosy: +berker.peksag
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed
superseder:  -> Document test.support.script_helper

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30136>
_______________________________________

From report at bugs.python.org  Sat Apr 22 02:18:37 2017
From: report at bugs.python.org (Louie Lu)
Date: Sat, 22 Apr 2017 06:18:37 +0000
Subject: [docs] [issue18576] Document test.support.script_helper
In-Reply-To: <1375014764.64.0.152576599022.issue18576@psf.upfronthosting.co.za>
Message-ID: <1492841917.9.0.935187571452.issue18576@psf.upfronthosting.co.za>


Changes by Louie Lu <me at louie.lu>:


----------
pull_requests: +1367

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue18576>
_______________________________________

From report at bugs.python.org  Sat Apr 22 08:20:37 2017
From: report at bugs.python.org (Louie Lu)
Date: Sat, 22 Apr 2017 12:20:37 +0000
Subject: [docs] [issue18576] Document test.support.script_helper
In-Reply-To: <1375014764.64.0.152576599022.issue18576@psf.upfronthosting.co.za>
Message-ID: <1492863637.58.0.850020370544.issue18576@psf.upfronthosting.co.za>


Louie Lu added the comment:

The PR on GitHub is based on bobcatfist's patch, addressed on Martin request and some minor change.

----------
nosy: +louielu

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue18576>
_______________________________________

From report at bugs.python.org  Sat Apr 22 11:08:09 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 22 Apr 2017 15:08:09 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492873689.46.0.348636148168.issue15718@psf.upfronthosting.co.za>


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


----------
pull_requests: +1369

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sat Apr 22 12:09:18 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 22 Apr 2017 16:09:18 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492877357.95.0.137775687598.issue15718@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Has or will builtin classes be modified to follow advice to include a separate __bool__?  In 3.6.1,

>>> r = range(19**100)
>>> bool(r)
Traceback (most recent call last):
  File "<pyshell#1>", line 1, in <module>
    bool(r)
OverflowError: Python int too large to convert to C ssize_t

----------
nosy: +serhiy.storchaka
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sat Apr 22 12:28:26 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 22 Apr 2017 16:28:26 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492878506.87.0.882706538767.issue15718@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Yes, and the range object already is fixed by issue28876.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sat Apr 22 13:24:09 2017
From: report at bugs.python.org (Stephen J. Turnbull)
Date: Sat, 22 Apr 2017 17:24:09 +0000
Subject: [docs] [issue30138] Incorrect documentation of replacement of slice
 of length 0
Message-ID: <1492881849.39.0.723167334866.issue30138@psf.upfronthosting.co.za>


New submission from Stephen J. Turnbull:

In section 4.6.3. "Mutable Sequence Types" of current documentation, Note 1 to the table says "[iterable] t must have the same length as the slice it is replacing." This is incorrect in the case of extension: s[len(s):] = t according to the rest of the documentation, as well as experiment.

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 292127
nosy: docs at python, sjt
priority: normal
severity: normal
status: open
title: Incorrect documentation of replacement of slice of length 0
type: behavior
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30138>
_______________________________________

From report at bugs.python.org  Sat Apr 22 13:29:56 2017
From: report at bugs.python.org (Stephen J. Turnbull)
Date: Sat, 22 Apr 2017 17:29:56 +0000
Subject: [docs] [issue30138] Incorrect documentation of replacement of slice
 of length 0
In-Reply-To: <1492881849.39.0.723167334866.issue30138@psf.upfronthosting.co.za>
Message-ID: <1492882196.6.0.873208288754.issue30138@psf.upfronthosting.co.za>


Stephen J. Turnbull added the comment:

Sorry, I just realized this note only applies to slices with a stride (k in i:j:k).  Closing.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30138>
_______________________________________

From report at bugs.python.org  Sat Apr 22 14:04:58 2017
From: report at bugs.python.org (Stephen J. Turnbull)
Date: Sat, 22 Apr 2017 18:04:58 +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: <1492884298.9.0.641504063815.issue29352@psf.upfronthosting.co.za>


Stephen J. Turnbull added the comment:

I prefer Josh's wording.  The important point to me is that

>>> [1, 2][2:0] = "AB"
[1, 2, "A", "B"]

not an error or ["B", "A"] == [1, 2][2:0:-1].  I think too much talk about the endpoints obscures this important fact.  (I think I'd like it to be an error, since the interpretation of s[2:0] = t could reasonably be any of s[0:0] = t, s[1:1] = t, or s[2:2] = t, but I haven't thought carefully enough yet, and "backward compatibility".)

Note: Josh's wording is already used in 3.7 (https://docs.python.org/dev/library/stdtypes.html#common-sequence-operations, as of the timestamp of this message).  I didn't check if it's been backported.

----------
nosy: +sjt

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29352>
_______________________________________

From report at bugs.python.org  Sat Apr 22 21:13:15 2017
From: report at bugs.python.org (Martin Panter)
Date: Sun, 23 Apr 2017 01:13:15 +0000
Subject: [docs] [issue30134] BytesWarning is missing from the documents
In-Reply-To: <1492832971.85.0.91707037101.issue30134@psf.upfronthosting.co.za>
Message-ID: <1492909995.04.0.612259080889.issue30134@psf.upfronthosting.co.za>


Martin Panter added the comment:

.
Issue 11681 is already open for the -b option, with a patch in progress.

If updating the doc string, also change ?buffer? to ?bytearray?. This is what ?bytearray? was originally called in Python 3, and ?buffer? is something different in Python 2.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30134>
_______________________________________

From report at bugs.python.org  Sun Apr 23 01:38:00 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 23 Apr 2017 05:38:00 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492925880.37.0.387391811653.issue15718@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset 85157cd89a6edac347a5b6871fcf20c500c6fbbf by Serhiy Storchaka in branch 'master':
bpo-15718: Document the upper bound constrain on the __len__ return value. (#1256)
https://github.com/python/cpython/commit/85157cd89a6edac347a5b6871fcf20c500c6fbbf


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sun Apr 23 01:42:52 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 23 Apr 2017 05:42:52 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492926171.99.0.352380442899.issue15718@psf.upfronthosting.co.za>


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


----------
pull_requests: +1372

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sun Apr 23 01:43:24 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 23 Apr 2017 05:43:24 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492926204.64.0.802308721644.issue15718@psf.upfronthosting.co.za>


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


----------
pull_requests: +1373

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sun Apr 23 01:49:59 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 23 Apr 2017 05:49:59 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492926599.81.0.975286407708.issue15718@psf.upfronthosting.co.za>


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


----------
pull_requests: +1374

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sun Apr 23 01:50:16 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 23 Apr 2017 05:50:16 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492926616.57.0.821039473578.issue15718@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset f2ed2858eea7569c8915b3611ca5ec92ae10b17f by Serhiy Storchaka in branch '3.6':
[3.6] bpo-15718: Document the upper bound constrain on the __len__ return value. (GH-1256) (#1259)
https://github.com/python/cpython/commit/f2ed2858eea7569c8915b3611ca5ec92ae10b17f


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sun Apr 23 01:50:24 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 23 Apr 2017 05:50:24 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492926624.22.0.935018345347.issue15718@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset c358536fd5e40e8f29ee4f086588a82fccb25a09 by Serhiy Storchaka in branch '3.5':
[3.5] bpo-15718: Document the upper bound constrain on the __len__ return value. (GH-1256) (#1260)
https://github.com/python/cpython/commit/c358536fd5e40e8f29ee4f086588a82fccb25a09


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sun Apr 23 01:58:11 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 23 Apr 2017 05:58:11 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492927091.19.0.785655480279.issue15718@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset bfc7dff63b9b30371e3423a5c35ccda2f3b52218 by Serhiy Storchaka in branch '2.7':
[2.7] bpo-15718: Document the upper bound constrain on the __len__ return value. (GH-1256). (#1261)
https://github.com/python/cpython/commit/bfc7dff63b9b30371e3423a5c35ccda2f3b52218


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sun Apr 23 03:12:39 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 23 Apr 2017 07:12:39 +0000
Subject: [docs] [issue15718] Possible OverflowError in __len__ method
 undocumented (when called via len() function)
In-Reply-To: <1345202279.02.0.767068523185.issue15718@psf.upfronthosting.co.za>
Message-ID: <1492931559.46.0.180846849431.issue15718@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15718>
_______________________________________

From report at bugs.python.org  Sun Apr 23 08:00:24 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 23 Apr 2017 12:00:24 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
Message-ID: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

The "callable" fixer was removed in dbdf029a5575f6e6ec0140260236963ed7d2c2be, but it still is mentioned in the documentation.

https://docs.python.org/3/library/2to3.html#2to3fixer-callable

----------
assignee: docs at python
components: 2to3 (2.x to 3.x conversion tool), Documentation
messages: 292162
nosy: benjamin.peterson, docs at python, gregory.p.smith, serhiy.storchaka
priority: normal
severity: normal
status: open
title: The "callable" fixer doesn't exist
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Sun Apr 23 09:36:28 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 23 Apr 2017 13:36:28 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1492954588.06.0.529349528079.issue30142@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
assignee: docs at python -> Mariatta
keywords: +easy
nosy: +Mariatta
stage:  -> needs patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Sun Apr 23 11:16:42 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 23 Apr 2017 15:16:42 +0000
Subject: [docs] [issue30145] Create a How to or Tutorial documentation for
 asyncio
Message-ID: <1492960602.26.0.461554169011.issue30145@psf.upfronthosting.co.za>


New submission from Mariatta Wijaya:

We could use a How To or a tutorial for asyncio in the docs.

----------
assignee: docs at python
components: Documentation, asyncio
messages: 292168
nosy: Mariatta, docs at python, yselivanov
priority: normal
severity: normal
status: open
title: Create a How to or Tutorial documentation for asyncio
versions: Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30145>
_______________________________________

From report at bugs.python.org  Sun Apr 23 12:45:55 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 23 Apr 2017 16:45:55 +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: <1492965955.76.0.921797400063.issue29352@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29352>
_______________________________________

From report at bugs.python.org  Sun Apr 23 15:10:06 2017
From: report at bugs.python.org (R. David Murray)
Date: Sun, 23 Apr 2017 19:10:06 +0000
Subject: [docs] [issue30147] change in re.escape output is not docuented in
 whatsnew
In-Reply-To: <1492972796.84.0.355071171235.issue30147@psf.upfronthosting.co.za>
Message-ID: <1492974605.98.0.173747399863.issue30147@psf.upfronthosting.co.za>


R. David Murray added the comment:

re.escape was escaping too much previously, and this has been fixed in 3.7 (and only 3.7, because it may cause testing issues such as you have observed).  See issue 29995.

A note needs to be added to the 'porting' section of whats new covering this.

----------
assignee:  -> docs at python
components: +Documentation -Regular Expressions
nosy: +docs at python, r.david.murray, serhiy.storchaka
stage:  -> needs patch
title: change in interface for compiled regex.pattern -> change in re.escape output is not docuented in whatsnew
type:  -> behavior

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

From report at bugs.python.org  Sun Apr 23 15:39:06 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 23 Apr 2017 19:39:06 +0000
Subject: [docs] [issue30147] Change in re.escape output is not documented in
 whatsnew
In-Reply-To: <1492972796.84.0.355071171235.issue30147@psf.upfronthosting.co.za>
Message-ID: <1492976346.86.0.919941898838.issue30147@psf.upfronthosting.co.za>


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


----------
title: change in re.escape output is not docuented in whatsnew -> Change in re.escape output is not documented in whatsnew

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

From report at bugs.python.org  Sun Apr 23 23:54:12 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 24 Apr 2017 03:54:12 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1493006051.93.0.589489722594.issue29751@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 26896f2832324dde85cdd63d525571ca669f6f0b by Mariatta (csabella) in branch 'master':
bpo-29751: Improve PyLong_FromString documentation (GH-915)
https://github.com/python/cpython/commit/26896f2832324dde85cdd63d525571ca669f6f0b


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Sun Apr 23 23:56:13 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 24 Apr 2017 03:56:13 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1493006173.53.0.667780478051.issue29751@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Sun Apr 23 23:56:20 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 24 Apr 2017 03:56:20 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1493006180.52.0.685465892808.issue29751@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +1378

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Sun Apr 23 23:56:24 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 24 Apr 2017 03:56:24 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1493006184.0.0.0104023126169.issue29751@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +1379

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Mon Apr 24 00:02:00 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 24 Apr 2017 04:02:00 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1493006520.48.0.88904063344.issue29751@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +1380

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Mon Apr 24 00:02:32 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 24 Apr 2017 04:02:32 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1493006552.55.0.288169963101.issue29751@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset d51d093b9bbca108f59bad0f1730c48ebf5b2e14 by Mariatta in branch '3.5':
[3.5] bpo-29751: Improve PyLong_FromString documentation (GH-915) (#1267)
https://github.com/python/cpython/commit/d51d093b9bbca108f59bad0f1730c48ebf5b2e14


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Mon Apr 24 00:05:03 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 24 Apr 2017 04:05:03 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1493006703.52.0.958219736432.issue29751@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset ea0efa3bc1d0b832da75519c6f85d767ae44feda by Mariatta in branch '3.6':
[3.6] bpo-29751: Improve PyLong_FromString documentation (GH-915) (#1266)
https://github.com/python/cpython/commit/ea0efa3bc1d0b832da75519c6f85d767ae44feda


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Mon Apr 24 00:05:21 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 24 Apr 2017 04:05:21 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1493006721.65.0.693707597232.issue29751@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 9eb5ca0774f94215be48442100c829db2484e146 by Mariatta in branch 'master':
bpo-29751: add Cheryl Sabella to Misc/ACKS (GH-1268)
https://github.com/python/cpython/commit/9eb5ca0774f94215be48442100c829db2484e146


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Mon Apr 24 00:06:38 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Mon, 24 Apr 2017 04:06:38 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1493006798.73.0.933224121119.issue29751@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

I merged the PR, backported it to 3.5 and 3.6, and added Cheryl to Misc/ACKS.

Thanks everyone :)

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Mon Apr 24 05:33:13 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 24 Apr 2017 09:33:13 +0000
Subject: [docs] [issue29751] PyLong_FromString documentation wrong on
 numbers with leading zero and base=0
In-Reply-To: <1488922068.27.0.463542328186.issue29751@psf.upfronthosting.co.za>
Message-ID: <1493026393.91.0.624801328247.issue29751@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

Oh, I didn't expect that.  That is so cool!  Thanks Mariatta.  :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29751>
_______________________________________

From report at bugs.python.org  Mon Apr 24 05:35:38 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 24 Apr 2017 09:35:38 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493026538.77.0.481292851387.issue30052@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

Since no one has said that this change shouldn't be made, I'll start working on this.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From erik.sommer at posteo.de  Wed Apr 19 16:00:00 2017
From: erik.sommer at posteo.de (Erik Sommer)
Date: Wed, 19 Apr 2017 23:00:00 +0300
Subject: [docs] Bug in
 https://docs.python.org/3.6/tutorial/introduction.html#strings
In-Reply-To: <CAKJDb-M=H8n7R=-x-cckrskv0x5gQrGT_aQfnWCHf8PekyR81Q@mail.gmail.com>
References: <534D9E88-11BA-4ECE-8FC3-3449370AEB7D@posteo.de>
 <CAKJDb-M=H8n7R=-x-cckrskv0x5gQrGT_aQfnWCHf8PekyR81Q@mail.gmail.com>
Message-ID: <8099426C-D98C-4651-9248-50328622926A@posteo.de>

Yeah... I realized that some minutes later. Sorry for the inconvenience. Thanks for the answer. 

Am 19. April 2017 22:57:07 OESZ schrieb Zachary Ware <zachary.ware+pydocs at gmail.com>:
>Hi Erik,
>
>On Wed, Apr 19, 2017 at 2:47 PM, Erik Sommer <erik.sommer at posteo.de>
>wrote:
>> In the first Codeblock at the sixth example it should be:
>>
>>>>> '"Isn\'t," she said.'
>> '"Isn't," she said.'
>>
>> In the current version the answer of the interpreter shows the
>backslash
>> character as well. That's not correct.
>
>The example is correct as is, try it for yourself!  Also have a look
>at the following paragraph and example which explain what's going on
>there.
>
>Thanks for your report,
>-- 
>Zach

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170419/9b169c11/attachment-0001.html>

From kfogel at red-bean.com  Fri Apr 21 20:17:15 2017
From: kfogel at red-bean.com (Karl Fogel)
Date: Fri, 21 Apr 2017 19:17:15 -0500
Subject: [docs] Suggested easy improvement to Python "getopt" documentation.
Message-ID: <8737d1i9dg.fsf@kwork>

This suggestion is for both https://docs.python.org/2/library/getopt.html and https://docs.python.org/3/library/getopt.html.

In the example that follows this text:

  "In a script, typical usage is something like this:"

I'd like to suggest that commas be added to emphasize list syntax, as in this patch:

  --- a	2017-04-21 19:04:28.596468414 -0500
  +++ b	2017-04-21 19:04:37.300326415 -0500
  @@ -13,10 +13,10 @@
       for o, a in opts:
           if o == "-v":
               verbose = True
  -        elif o in ("-h", "--help"):
  +        elif o in ("-h", "--help",):
               usage()
               sys.exit()
  -        elif o in ("-o", "--output"):
  +        elif o in ("-o", "--output",):
               output = a
           else:
               assert False, "unhandled option"

Adding the commas would prevent the following bad scenario:

If someone copies the example code and modifies it heavily, they could easily end up with something like this:

  for o, a in opts:
      if o in ("-h", "-?", "--help", "--usage"):
          usage()
          sys.exit(0)
      elif o in ("--show-columns"):
          show_columns = True
      elif o in ("-c", "--config"):
          config = parse_config_file(a)
      else:
          assert False, "unhandled option"

You can see the problem with the first 'elif' case.  When the value of 'o' is "-c", it will improperly match, because

  o in ("--show-columns")

would be improperly True, whereas

  o in ("--show-columns",)

would have been properly False.

Adding the commas would emphasize that these are lists, and make this kind of copy-paste-massage bug less likely to happen.

(By the way, I tried to report this by filing a bug in http://bugs.python.org/, but some glitch in the registration process won't let me register "kfogel" now.  I'm already deep enough in yak shaving that I don't want to debug that problem at the moment, but if you can reset/clear that account, I'd be happy to simply re-try the registration process.)

Best regards,
-Karl Fogel

From m.faleo at call.maran.it  Sat Apr 22 04:55:32 2017
From: m.faleo at call.maran.it (Michele Faleo)
Date: Sat, 22 Apr 2017 10:55:32 +0200
Subject: [docs] ASKING FOR INFORMATION
Message-ID: <02a701d2bb46$32c19d20$9844d760$@faleo@call.maran.it>

Good Morning,

my name is Michele Faleo.

I've recently discovered Phyton since I want to start to study a new
programming language by myself.

 

I just want to be sure to start reading a proper manual.

Do you have any suggestion in order to choose the best manual to start my
"Phyton Uknowledge"?

 

Thanks for your attention.

Best regards.

 

----------------------------------------------------------------------------
-----

Michele Faleo | Supervisor Business Analysis Unit

T +39 0743 294 651 | M +39 320 6262 567 | e-mail
<mailto:m.faleo at call.maran.it> m.faleo at call.maran.it

Maran Credit Solution SpA | Via degli Operai, 25 | 06049 - SPOLETO (PG)
ITALY

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170422/9ce75628/attachment.html>

From report at bugs.python.org  Mon Apr 24 08:22:00 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 24 Apr 2017 12:22:00 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493036520.41.0.472776223195.issue30052@psf.upfronthosting.co.za>


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


----------
nosy: +georg.brandl

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Mon Apr 24 14:11:52 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 24 Apr 2017 18:11:52 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493057512.19.0.452321653697.issue30052@psf.upfronthosting.co.za>


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


----------
pull_requests: +1382

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Mon Apr 24 17:17:20 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 24 Apr 2017 21:17:20 +0000
Subject: [docs] [issue28851] namedtuples field_names sequence preferred
In-Reply-To: <1480601135.13.0.00871251418973.issue28851@psf.upfronthosting.co.za>
Message-ID: <1493068640.26.0.614059967883.issue28851@psf.upfronthosting.co.za>


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


----------
pull_requests: +1385

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28851>
_______________________________________

From report at bugs.python.org  Mon Apr 24 17:18:56 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Mon, 24 Apr 2017 21:18:56 +0000
Subject: [docs] [issue28851] namedtuples field_names sequence preferred
In-Reply-To: <1480601135.13.0.00871251418973.issue28851@psf.upfronthosting.co.za>
Message-ID: <1493068736.68.0.10643357198.issue28851@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

Hope it's OK that I've made a PR for these changes.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28851>
_______________________________________

From report at bugs.python.org  Mon Apr 24 21:54:13 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 25 Apr 2017 01:54:13 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493085253.67.0.600858207227.issue30052@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
stage:  -> patch review
versions: +Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Tue Apr 25 10:41:18 2017
From: report at bugs.python.org (Raymond Hettinger)
Date: Tue, 25 Apr 2017 14:41:18 +0000
Subject: [docs] [issue28851] namedtuples field_names sequence preferred
In-Reply-To: <1480601135.13.0.00871251418973.issue28851@psf.upfronthosting.co.za>
Message-ID: <1493131278.39.0.167839788731.issue28851@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Mariatta, I've approved Cheryl's PR.  Would like to do the honors and apply it.

----------
assignee: rhettinger -> Mariatta
nosy: +Mariatta

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28851>
_______________________________________

From report at bugs.python.org  Tue Apr 25 10:44:44 2017
From: report at bugs.python.org (Mike)
Date: Tue, 25 Apr 2017 14:44:44 +0000
Subject: [docs] [issue30160] BaseHTTPRequestHandler.wfile: supported usage
 unclear
Message-ID: <1493131484.95.0.842958745675.issue30160@psf.upfronthosting.co.za>


New submission from Mike:

The documentation for BaseHTTPRequestHandler explicitly prohibits protocol
violations when writing to the `wfile` stream:

> BaseHTTPRequestHandler has the following instance variables:
>
> [...]
>
> **`wfile`**
>
> > Contains the output stream for writing a response back to the client.
> > Proper adherence to the HTTP protocol must be used when writing to this
> > stream.

I am interested in testing web browser behavior in response to protocol
violations, and my initial interpretation of this text (and the term "must" in
particular) is that such conditions are not guaranteed to achievable with this
module. However, my colleague believes the text is simply intended to
communicate that there is no safety mechanism in place, and that protocol
violations will not be corrected. [1]

Local testing and a quick reading of the source tends to confirm the latter
interpretation, but this may simply be coincidental and not necessarily stable
behavior.

If it is in fact stable, then I would like to request a modification to the
documentation. Changing the word "must" to "should" would help, although it
might be better to be more explicit--something like, "Bytes are transmitted
'as-is'; HTTP protocol violations will not be corrected."

Thanks!

[1] https://github.com/w3c/web-platform-tests/issues/5668

----------
assignee: docs at python
components: Documentation
messages: 292263
nosy: docs at python, jugglinmike
priority: normal
severity: normal
status: open
title: BaseHTTPRequestHandler.wfile: supported usage unclear

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30160>
_______________________________________

From report at bugs.python.org  Tue Apr 25 10:58:54 2017
From: report at bugs.python.org (R. David Murray)
Date: Tue, 25 Apr 2017 14:58:54 +0000
Subject: [docs] [issue30160] BaseHTTPRequestHandler.wfile: supported usage
 unclear
In-Reply-To: <1493131484.95.0.842958745675.issue30160@psf.upfronthosting.co.za>
Message-ID: <1493132334.02.0.355639796065.issue30160@psf.upfronthosting.co.za>


R. David Murray added the comment:

I would like to say that the latter interpretation is "obviously" correct, except that it clearly wasn't obvious to you.  The fact that it "contains the output stream" I would have thought was pretty clear: if you are writing to it, you are responsible for anything you do to that output stream.  The "must" refers to the same the the RFC "must" refers to: in order to be RFC compliant, you must conform to the RFC.

Perhaps we could clarify that sentence by saying: "Proper adherence to the HTTP protocol must be used when writing to this stream in order to achieve successful interoperation with http clients."  I think that would make it clear that if you don't, you'll be testing the client's response to protocol violations :)

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30160>
_______________________________________

From report at bugs.python.org  Tue Apr 25 11:55:06 2017
From: report at bugs.python.org (Mike)
Date: Tue, 25 Apr 2017 15:55:06 +0000
Subject: [docs] [issue30160] BaseHTTPRequestHandler.wfile: supported usage
 unclear
In-Reply-To: <1493131484.95.0.842958745675.issue30160@psf.upfronthosting.co.za>
Message-ID: <1493135706.77.0.415950485662.issue30160@psf.upfronthosting.co.za>


Mike added the comment:

That would certainly satisfy me!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30160>
_______________________________________

From report at bugs.python.org  Tue Apr 25 12:14:48 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 25 Apr 2017 16:14:48 +0000
Subject: [docs] [issue28851] namedtuples field_names sequence preferred
In-Reply-To: <1480601135.13.0.00871251418973.issue28851@psf.upfronthosting.co.za>
Message-ID: <1493136888.1.0.0173690873294.issue28851@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 97bf722fcd1de1236824377e052369dc7686b644 by Mariatta (csabella) in branch 'master':
bpo-28851: Improve namedtuple documentation (GH-1274)
https://github.com/python/cpython/commit/97bf722fcd1de1236824377e052369dc7686b644


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28851>
_______________________________________

From report at bugs.python.org  Tue Apr 25 12:15:55 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Tue, 25 Apr 2017 16:15:55 +0000
Subject: [docs] [issue28851] namedtuples field_names sequence preferred
In-Reply-To: <1480601135.13.0.00871251418973.issue28851@psf.upfronthosting.co.za>
Message-ID: <1493136954.67.0.982994989757.issue28851@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

My pleasure :) I merged the PR, and will do the backport later today.

----------
stage:  -> backport needed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28851>
_______________________________________

From report at bugs.python.org  Tue Apr 25 15:16:27 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 25 Apr 2017 19:16:27 +0000
Subject: [docs] [issue29576] Improve some deprecations in the importlib
In-Reply-To: <1487208454.1.0.000568467436348.issue29576@psf.upfronthosting.co.za>
Message-ID: <1493147787.73.0.864923613143.issue29576@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

This change made test_importlib emitting warnings. See issue30158.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29576>
_______________________________________

From report at bugs.python.org  Tue Apr 25 15:20:17 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 25 Apr 2017 19:20:17 +0000
Subject: [docs] [issue29576] Improve some deprecations in the importlib
In-Reply-To: <1487208454.1.0.000568467436348.issue29576@psf.upfronthosting.co.za>
Message-ID: <1493148017.89.0.524019870539.issue29576@psf.upfronthosting.co.za>


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


----------
pull_requests: +1393

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29576>
_______________________________________

From report at bugs.python.org  Tue Apr 25 19:02:07 2017
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 25 Apr 2017 23:02:07 +0000
Subject: [docs] [issue29576] Improve some deprecations in the importlib
In-Reply-To: <1487208454.1.0.000568467436348.issue29576@psf.upfronthosting.co.za>
Message-ID: <1493161327.51.0.618422238409.issue29576@psf.upfronthosting.co.za>


STINNER Victor added the comment:

This issue introduced new warnings when running test_importlib: see issue #30158.

----------
nosy: +haypo

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29576>
_______________________________________

From report at bugs.python.org  Tue Apr 25 21:18:19 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 26 Apr 2017 01:18:19 +0000
Subject: [docs] [issue28851] namedtuples field_names sequence preferred
In-Reply-To: <1480601135.13.0.00871251418973.issue28851@psf.upfronthosting.co.za>
Message-ID: <1493169499.83.0.349779989615.issue28851@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +1394

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28851>
_______________________________________

From report at bugs.python.org  Tue Apr 25 21:23:07 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 26 Apr 2017 01:23:07 +0000
Subject: [docs] [issue28851] namedtuples field_names sequence preferred
In-Reply-To: <1480601135.13.0.00871251418973.issue28851@psf.upfronthosting.co.za>
Message-ID: <1493169787.21.0.390112897865.issue28851@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 16b6f971bd8afc72b439b83324eba744460adb67 by Mariatta in branch '3.6':
[3.6] bpo-28851: Improve namedtuple documentation (GH-1274) (GH-1286)
https://github.com/python/cpython/commit/16b6f971bd8afc72b439b83324eba744460adb67


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28851>
_______________________________________

From report at bugs.python.org  Tue Apr 25 21:23:57 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 26 Apr 2017 01:23:57 +0000
Subject: [docs] [issue28851] namedtuples field_names sequence preferred
In-Reply-To: <1480601135.13.0.00871251418973.issue28851@psf.upfronthosting.co.za>
Message-ID: <1493169837.18.0.497974193066.issue28851@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Backported to 3.6.

Thanks, everyone :)

----------
resolution: later -> fixed
stage: backport needed -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28851>
_______________________________________

From report at bugs.python.org  Wed Apr 26 00:01:52 2017
From: report at bugs.python.org (Louie Lu)
Date: Wed, 26 Apr 2017 04:01:52 +0000
Subject: [docs] [issue21150] Add quick links table to argparse docs
In-Reply-To: <1396558035.28.0.485991636726.issue21150@psf.upfronthosting.co.za>
Message-ID: <1493179312.44.0.224915567258.issue21150@psf.upfronthosting.co.za>


Louie Lu added the comment:

Could Raymond, Gaurav or paul help to review the PR's summary table?
Thanks!

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21150>
_______________________________________

From report at bugs.python.org  Wed Apr 26 01:47:04 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 26 Apr 2017 05:47:04 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493185624.3.0.395232395372.issue30052@psf.upfronthosting.co.za>


Nick Coghlan added the comment:


New changeset c6db4811f9ea3aeff0e1fafe1c60a22835ef359e by Nick Coghlan (csabella) in branch 'master':
bpo-30052: Link `bytes` & `bytearray` to stdtypes not functions  (GH-1271)
https://github.com/python/cpython/commit/c6db4811f9ea3aeff0e1fafe1c60a22835ef359e


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Wed Apr 26 02:51:31 2017
From: report at bugs.python.org (Louie Lu)
Date: Wed, 26 Apr 2017 06:51:31 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1493189491.18.0.321589835339.issue19184@psf.upfronthosting.co.za>


Louie Lu added the comment:

I've made a PR, could serhiy or georg help for review?
Thanks!

----------
nosy: +louielu

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19184>
_______________________________________

From report at bugs.python.org  Wed Apr 26 04:15:09 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 08:15:09 +0000
Subject: [docs] [issue28698] Python 3.x ctypes c_wchar_p return is different
 from official documentation example
In-Reply-To: <1479230636.43.0.863548306007.issue28698@psf.upfronthosting.co.za>
Message-ID: <1493194509.17.0.347571518697.issue28698@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 0d637e236d7099f7b724026c8cb7bd83d8e12e6b by Berker Peksag (Louie Lu) in branch 'master':
bpo-28698: Fix c_wchar_p doc example (GH-1160)
https://github.com/python/cpython/commit/0d637e236d7099f7b724026c8cb7bd83d8e12e6b


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28698>
_______________________________________

From report at bugs.python.org  Wed Apr 26 04:20:18 2017
From: report at bugs.python.org (Louie Lu)
Date: Wed, 26 Apr 2017 08:20:18 +0000
Subject: [docs] [issue28698] Python 3.x ctypes c_wchar_p return is different
 from official documentation example
In-Reply-To: <1479230636.43.0.863548306007.issue28698@psf.upfronthosting.co.za>
Message-ID: <1493194818.72.0.65554044709.issue28698@psf.upfronthosting.co.za>


Changes by Louie Lu <me at louie.lu>:


----------
pull_requests: +1398

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28698>
_______________________________________

From report at bugs.python.org  Wed Apr 26 04:21:28 2017
From: report at bugs.python.org (Louie Lu)
Date: Wed, 26 Apr 2017 08:21:28 +0000
Subject: [docs] [issue28698] Python 3.x ctypes c_wchar_p return is different
 from official documentation example
In-Reply-To: <1479230636.43.0.863548306007.issue28698@psf.upfronthosting.co.za>
Message-ID: <1493194888.29.0.65795682161.issue28698@psf.upfronthosting.co.za>


Changes by Louie Lu <me at louie.lu>:


----------
pull_requests: +1399

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28698>
_______________________________________

From report at bugs.python.org  Wed Apr 26 04:45:33 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 08:45:33 +0000
Subject: [docs] [issue28698] Python 3.x ctypes c_wchar_p return is different
 from official documentation example
In-Reply-To: <1479230636.43.0.863548306007.issue28698@psf.upfronthosting.co.za>
Message-ID: <1493196333.44.0.0796601957517.issue28698@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 9f6828119df23fca9e799f47e02baabe87adca2a by Berker Peksag (Louie Lu) in branch '3.6':
bpo-28698: Fix c_wchar_p doc example (GH-1160)
https://github.com/python/cpython/commit/9f6828119df23fca9e799f47e02baabe87adca2a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28698>
_______________________________________

From report at bugs.python.org  Wed Apr 26 04:47:05 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 08:47:05 +0000
Subject: [docs] [issue28698] Python 3.x ctypes c_wchar_p return is different
 from official documentation example
In-Reply-To: <1479230636.43.0.863548306007.issue28698@psf.upfronthosting.co.za>
Message-ID: <1493196425.4.0.76381368931.issue28698@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset c7b8367076dc7771dabcb9491bd98218c788d489 by Berker Peksag (Louie Lu) in branch '3.5':
bpo-28698: Fix c_wchar_p doc example (GH-1160)
https://github.com/python/cpython/commit/c7b8367076dc7771dabcb9491bd98218c788d489


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28698>
_______________________________________

From report at bugs.python.org  Wed Apr 26 04:48:40 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 08:48:40 +0000
Subject: [docs] [issue28698] Python 3.x ctypes c_wchar_p return is different
 from official documentation example
In-Reply-To: <1479230636.43.0.863548306007.issue28698@psf.upfronthosting.co.za>
Message-ID: <1493196520.47.0.316838597067.issue28698@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Thanks for the report, Alex and thanks for the PRs, Louie!

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28698>
_______________________________________

From report at bugs.python.org  Wed Apr 26 06:49:49 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 10:49:49 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493203789.18.0.105887729322.issue29974@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 87c07fe9d908d0a2143fcc8369255c6ff3241503 by Berker Peksag (Mathias Rav) in branch 'master':
bpo-29974: Improve typing.TYPE_CHECKING example (GH-982)
https://github.com/python/cpython/commit/87c07fe9d908d0a2143fcc8369255c6ff3241503


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Wed Apr 26 07:06:53 2017
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 26 Apr 2017 11:06:53 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493204813.16.0.664091150907.issue29974@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Wed Apr 26 07:09:11 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 26 Apr 2017 11:09:11 +0000
Subject: [docs] [issue28315] incorrect "in ?" output in 'divide' example at
 "Defining Clean-up Actions" in tutorial
In-Reply-To: <1475194645.41.0.947079052008.issue28315@psf.upfronthosting.co.za>
Message-ID: <1493204951.63.0.569531858504.issue28315@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

@Mariatta

I believe you can do this now?

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28315>
_______________________________________

From report at bugs.python.org  Wed Apr 26 07:32:48 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 11:32:48 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493206368.86.0.958510806187.issue29974@psf.upfronthosting.co.za>


Berker Peksag added the comment:

87c07fe9d908d0a2143fcc8369255c6ff3241503 should still be backported to 3.5 and 3.6 branches so please don't close it yet.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From skz5k2 at gmail.com  Tue Apr 25 14:34:40 2017
From: skz5k2 at gmail.com (F SkZ M)
Date: Tue, 25 Apr 2017 15:34:40 -0300
Subject: [docs] Documentation in PDF A4
Message-ID: <CAPEWdcWWk_o3WFnCn0+B_SFTVeZN3-oYCkXf22DgKtd3rfQZ3A@mail.gmail.com>

I downloaded the A4 version of the documentation from the site, but when I
check in the properties the pdf files result to be in letter, and comparing
with the letter version of the same document, they have effectively the
same format (pages 102 of c-api.pdf of "a4" and letter version are
identical, that it would be not possible considering the different size of
the page format).

python-3.6.1 :)pdfinfo c-api.pdf
> Title:
> Subject:
> Keywords:
> Author:
> Creator:        LaTeX with hyperref package
> Producer:       pdfTeX-1.40.14
> CreationDate:   Tue Apr 25 00:15:56 2017
> ModDate:        Tue Apr 25 00:15:56 2017
> Tagged:         no
> Form:           none
> Pages:          226
> Encrypted:      no
> Page size:      612 x 792 pts (letter)
> Page rot:       0
> File size:      947872 bytes
> Optimized:      no
> PDF version:    1.5
>

Francesco Mauro

PS: the size of the compress file is actually 12MiB and not 8MiB


--and rising one morning with the rosy dawn, he went before the sun, and
spake thus unto it:
Thou great star! What would be thy happiness if thou hadst not those for
whom thou shinest! (Nietzsche, AsZ)
Software is like sex: it's better when it's free (Linus T.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170425/b8ae48bc/attachment.html>

From report at bugs.python.org  Wed Apr 26 08:44:01 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Wed, 26 Apr 2017 12:44:01 +0000
Subject: [docs] [issue30168] Class Logger is unindented in the documentation.
Message-ID: <1493210640.98.0.578541878256.issue30168@psf.upfronthosting.co.za>


New submission from Jim Fasarakis-Hilliard:

Currently, `Logger` in `logging.rst` doesn't have an indent after `.. class:: Logger`. This causes the formatting for the specific section to look somewhat unexpected [1]. 

I've already created a PR that indents the methods/attributes accordingly. 

After @bitdancer's request, created this issue to get feedback from vinay if this was done on purpose.

[1]: https://docs.python.org/3/library/logging.html#logging.Logger

----------
assignee: docs at python
components: Documentation
messages: 292336
nosy: Jim Fasarakis-Hilliard, docs at python, vinay.sajip
priority: normal
severity: normal
status: open
title: Class Logger is unindented in the documentation.
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30168>
_______________________________________

From report at bugs.python.org  Wed Apr 26 08:44:17 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Wed, 26 Apr 2017 12:44:17 +0000
Subject: [docs] [issue30168] Class Logger is unindented in the documentation.
In-Reply-To: <1493210640.98.0.578541878256.issue30168@psf.upfronthosting.co.za>
Message-ID: <1493210657.23.0.328095879242.issue30168@psf.upfronthosting.co.za>


Changes by Jim Fasarakis-Hilliard <d.f.hilliard at gmail.com>:


----------
pull_requests: +1402

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30168>
_______________________________________

From report at bugs.python.org  Wed Apr 26 09:18:59 2017
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 26 Apr 2017 13:18:59 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1493212739.16.0.593391149923.issue30142@psf.upfronthosting.co.za>


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


----------
pull_requests: +1403

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Wed Apr 26 09:31:53 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 13:31:53 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493213513.5.0.459925588182.issue29974@psf.upfronthosting.co.za>


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


----------
pull_requests: +1404

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Wed Apr 26 09:34:24 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 13:34:24 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493213664.63.0.633302108517.issue29974@psf.upfronthosting.co.za>


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


----------
pull_requests: +1406

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Wed Apr 26 10:10:13 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 14:10:13 +0000
Subject: [docs] [issue18669] curses.chgat() moves cursor,
 documentation says it shouldn't
In-Reply-To: <1375800170.73.0.20062232661.issue18669@psf.upfronthosting.co.za>
Message-ID: <1493215813.13.0.0572184626819.issue18669@psf.upfronthosting.co.za>


Berker Peksag added the comment:

I think this is a documentation issue. curses.chgat() documentation tries to describe different signatures in one place and some of these signatures change the behavior of the function. For example, curses.chgat() calls mvwchgat() when users pass y and x to it and mvwchgat() is documented as "the mvwchgat function does a cursor move before acting".

----------
keywords: +easy
nosy: +berker.peksag
stage:  -> needs patch
versions: +Python 3.6, Python 3.7 -Python 3.2, Python 3.4

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue18669>
_______________________________________

From report at bugs.python.org  Wed Apr 26 10:23:52 2017
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 26 Apr 2017 14:23:52 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493216632.25.0.139029229944.issue29974@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

> 87c07fe9d908d0a2143fcc8369255c6ff3241503 should still be backported to 3.5 and 3.6 branches so please don't close it yet.

Thanks for making backport PRs! (and sorry for closing prematurely)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Wed Apr 26 10:24:08 2017
From: report at bugs.python.org (Mike)
Date: Wed, 26 Apr 2017 14:24:08 +0000
Subject: [docs] [issue30160] BaseHTTPRequestHandler.wfile: supported usage
 unclear
In-Reply-To: <1493131484.95.0.842958745675.issue30160@psf.upfronthosting.co.za>
Message-ID: <1493216648.71.0.941222234036.issue30160@psf.upfronthosting.co.za>


Changes by Mike <mike at mikepennisi.com>:


----------
pull_requests: +1407

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30160>
_______________________________________

From report at bugs.python.org  Wed Apr 26 10:24:38 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 14:24:38 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493216678.42.0.94565034791.issue29974@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 271a289a03ad10c91c5326bde3020f1cdf6a1fff by Berker Peksag in branch '3.5':
bpo-29974: Improve typing.TYPE_CHECKING example (GH-982)
https://github.com/python/cpython/commit/271a289a03ad10c91c5326bde3020f1cdf6a1fff


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Wed Apr 26 10:24:56 2017
From: report at bugs.python.org (Mark Lawrence)
Date: Wed, 26 Apr 2017 14:24:56 +0000
Subject: [docs] [issue18669] curses.chgat() moves cursor,
 documentation says it shouldn't
In-Reply-To: <1375800170.73.0.20062232661.issue18669@psf.upfronthosting.co.za>
Message-ID: <1493216696.95.0.87206212398.issue18669@psf.upfronthosting.co.za>


Changes by Mark Lawrence <breamoreboy at gmail.com>:


----------
nosy:  -BreamoreBoy

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue18669>
_______________________________________

From report at bugs.python.org  Wed Apr 26 10:25:39 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 14:25:39 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493216739.21.0.908873062411.issue29974@psf.upfronthosting.co.za>


Berker Peksag added the comment:


New changeset 04f389b8b357c8507b6c9642adcb8b956489e034 by Berker Peksag in branch '3.6':
bpo-29974: Improve typing.TYPE_CHECKING example (GH-982)
https://github.com/python/cpython/commit/04f389b8b357c8507b6c9642adcb8b956489e034


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Wed Apr 26 10:28:41 2017
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 26 Apr 2017 14:28:41 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493216921.52.0.889070249003.issue29974@psf.upfronthosting.co.za>


Berker Peksag added the comment:

Now all backport PRs have been merged. Thanks for the PR, Mathias.

> Thanks for making backport PRs! (and sorry for closing prematurely)

No problem, thanks for the reviews! By the way, sorry I missed the typo in your last name while doing the initial merge.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Wed Apr 26 11:18:35 2017
From: report at bugs.python.org (Mathias Rav)
Date: Wed, 26 Apr 2017 15:18:35 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493219915.22.0.903013711056.issue29974@psf.upfronthosting.co.za>


Mathias Rav added the comment:

Sorry for making a typo in your last name, Ivan Levkivskyi! I should know better and use copy-and-paste.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Wed Apr 26 11:21:38 2017
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Wed, 26 Apr 2017 15:21:38 +0000
Subject: [docs] [issue29974] Change typing.TYPE_CHECKING doc example
In-Reply-To: <1491240763.76.0.717121375128.issue29974@psf.upfronthosting.co.za>
Message-ID: <1493220098.2.0.383231141484.issue29974@psf.upfronthosting.co.za>


Ivan Levkivskyi added the comment:

> Sorry for making a typo in your last name

No problem!
This actually happened maaany times with me :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29974>
_______________________________________

From report at bugs.python.org  Wed Apr 26 12:10:21 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 26 Apr 2017 16:10:21 +0000
Subject: [docs] [issue30176] curses attribute constants list is incomplete
Message-ID: <1493223021.35.0.365955422989.issue30176@psf.upfronthosting.co.za>


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


----------
assignee: docs at python
components: Documentation
nosy: berker.peksag, docs at python, haypo, xiang.zhang
priority: normal
severity: normal
stage: patch review
status: open
title: curses attribute constants list is incomplete
versions: Python 2.7, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30176>
_______________________________________

From report at bugs.python.org  Wed Apr 26 12:12:13 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 26 Apr 2017 16:12:13 +0000
Subject: [docs] [issue30176] curses attribute constants list is incomplete
Message-ID: <1493223133.93.0.321886899927.issue30176@psf.upfronthosting.co.za>


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


----------
pull_requests: +1409

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30176>
_______________________________________

From report at bugs.python.org  Wed Apr 26 12:16:23 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 26 Apr 2017 16:16:23 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1493223383.63.0.741715391803.issue30142@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset a90b990480f45b6a0ad02d43455cf8b620bac9c5 by Mariatta (Dong-hee Na) in branch 'master':
bpo-30142: Remove "callable" from the 2to3fixer documentation. (GH-1296)
https://github.com/python/cpython/commit/a90b990480f45b6a0ad02d43455cf8b620bac9c5


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Wed Apr 26 12:30:38 2017
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 26 Apr 2017 16:30:38 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1493224238.55.0.424449154716.issue30142@psf.upfronthosting.co.za>


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


----------
pull_requests: +1410

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Wed Apr 26 12:31:30 2017
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 26 Apr 2017 16:31:30 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1493224290.26.0.803145583163.issue30142@psf.upfronthosting.co.za>


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


----------
pull_requests: +1411

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Wed Apr 26 12:31:53 2017
From: report at bugs.python.org (Dong-hee Na)
Date: Wed, 26 Apr 2017 16:31:53 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1493224313.71.0.720628116517.issue30142@psf.upfronthosting.co.za>


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


----------
pull_requests: +1412

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Wed Apr 26 12:55:24 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 26 Apr 2017 16:55:24 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1493225723.99.0.597732866942.issue30142@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 9a626ec4e58c0bca1b4f71154e9e1da7e6d7e4a7 by Mariatta (Dong-hee Na) in branch '3.5':
[3.5] bpo-30142: Remove "callable" from the 2to3fixer documentation. (GH-1304)
https://github.com/python/cpython/commit/9a626ec4e58c0bca1b4f71154e9e1da7e6d7e4a7


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Wed Apr 26 12:55:34 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 26 Apr 2017 16:55:34 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1493225734.79.0.806442191764.issue30142@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 19b3a4885cc685adb42db6f8f7b625768f6d1baf by Mariatta (Dong-hee Na) in branch '2.7':
[2.7] bpo-30142: Remove "callable" from the 2to3fixer documentation. (GH-1305)
https://github.com/python/cpython/commit/19b3a4885cc685adb42db6f8f7b625768f6d1baf


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Wed Apr 26 12:55:58 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 26 Apr 2017 16:55:58 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1493225758.11.0.847843735343.issue30142@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 2fc3c543fc93d6211de8dcfaeac3a0fd10a356e0 by Mariatta (Dong-hee Na) in branch '3.6':
[3.6] bpo-30142: Remove "callable" from the 2to3fixer documentation. (GH-1303)
https://github.com/python/cpython/commit/2fc3c543fc93d6211de8dcfaeac3a0fd10a356e0


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Wed Apr 26 12:56:53 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 26 Apr 2017 16:56:53 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1493225813.43.0.064465168749.issue30142@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Wed Apr 26 13:13:34 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Wed, 26 Apr 2017 17:13:34 +0000
Subject: [docs] [issue30178] Indent methods and attributes of MimeTypes class
Message-ID: <1493226814.74.0.770717289652.issue30178@psf.upfronthosting.co.za>


New submission from Jim Fasarakis-Hilliard:

Similar to #30168 opened earlier. The MimeTypes class's methods and attributes aren't indented and the resulting documentation is not indented and duplicates the class name. 

Didn't find anything that might indicate this was intentional when trying to blame this change. It seems to have happened at some point between 2.6 [1] and 2.7 [2], though, where the class directive was moved to the MimeTypes Objects section. Also didn't find an expert for this module in the index. 

Proposed change just indents these. 

[1]: https://github.com/python/cpython/blame/2.6/Doc/library/mimetypes.rst
[2]: https://github.com/python/cpython/blame/2.7/Doc/library/mimetypes.rst

----------
assignee: docs at python
components: Documentation
messages: 292374
nosy: Jim Fasarakis-Hilliard, docs at python
priority: normal
severity: normal
status: open
title: Indent methods and attributes of MimeTypes class
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30178>
_______________________________________

From report at bugs.python.org  Wed Apr 26 13:14:16 2017
From: report at bugs.python.org (Jim Fasarakis-Hilliard)
Date: Wed, 26 Apr 2017 17:14:16 +0000
Subject: [docs] [issue30178] Indent methods and attributes of MimeTypes class
In-Reply-To: <1493226814.74.0.770717289652.issue30178@psf.upfronthosting.co.za>
Message-ID: <1493226856.02.0.636277291121.issue30178@psf.upfronthosting.co.za>


Changes by Jim Fasarakis-Hilliard <d.f.hilliard at gmail.com>:


----------
pull_requests: +1413

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30178>
_______________________________________

From report at bugs.python.org  Wed Apr 26 13:15:06 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 26 Apr 2017 17:15:06 +0000
Subject: [docs] [issue30176] curses attribute constants list is incomplete
Message-ID: <1493226906.47.0.950642994662.issue30176@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Initially constants was enumerated in alphabetical order (except A_ITALIC). Maybe continue supporting this order? On other hand, it may be worth to group highlighting attributes separately. A_ATTRIBUTES, A_CHARTEXT and A_COLOR are not specific attributes, but bit masks, they also could be grouped separately or moved into a separate table.

Perhaps it is worth to add notes for A_ITALIC and highlighting attributes. They are not always available.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30176>
_______________________________________

From report at bugs.python.org  Wed Apr 26 13:16:45 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 26 Apr 2017 17:16:45 +0000
Subject: [docs] [issue30142] The "callable" fixer doesn't exist
In-Reply-To: <1492948824.23.0.412292082563.issue30142@psf.upfronthosting.co.za>
Message-ID: <1493227005.22.0.736732822551.issue30142@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thanks Dong-hee Na and Mariatta.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30142>
_______________________________________

From report at bugs.python.org  Wed Apr 26 13:25:12 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Wed, 26 Apr 2017 17:25:12 +0000
Subject: [docs] [issue30176] curses attribute constants list is incomplete
In-Reply-To: <1493226906.47.0.950642994662.issue30176@psf.upfronthosting.co.za>
Message-ID: <1493227512.15.0.107914546529.issue30176@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

+1 for group. I added "The exact constants available are system dependent" to note some may be absent.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30176>
_______________________________________

From report at bugs.python.org  Wed Apr 26 13:38:18 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 26 Apr 2017 17:38:18 +0000
Subject: [docs] [issue27618] docs for threading.Lock claim it's a class
 (since 3.3), but it's not (and has never been, apparently)
In-Reply-To: <1469480103.96.0.342423272445.issue27618@psf.upfronthosting.co.za>
Message-ID: <1493228298.16.0.104959364524.issue27618@psf.upfronthosting.co.za>


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


----------
pull_requests: +1414

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue27618>
_______________________________________

From report at bugs.python.org  Wed Apr 26 13:46:26 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 26 Apr 2017 17:46:26 +0000
Subject: [docs] [issue30176] curses attribute constants list is incomplete
In-Reply-To: <1493226906.47.0.950642994662.issue30176@psf.upfronthosting.co.za>
Message-ID: <1493228786.32.0.638240352037.issue30176@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I still think that the difference between the groups should be documented in more details. Not all functions that support A_BOLD support also A_ITALIC and A_HORIZONTAL (even if they are defined). Bit masks are used in totally different way than other constants.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30176>
_______________________________________

From report at bugs.python.org  Wed Apr 26 13:47:58 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 26 Apr 2017 17:47:58 +0000
Subject: [docs] [issue30176] curses attribute constants list is incomplete
In-Reply-To: <1493226906.47.0.950642994662.issue30176@psf.upfronthosting.co.za>
Message-ID: <1493228878.75.0.337917619114.issue30176@psf.upfronthosting.co.za>


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


----------
nosy: +twouters

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30176>
_______________________________________

From report at bugs.python.org  Wed Apr 26 18:19:39 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 26 Apr 2017 22:19:39 +0000
Subject: [docs] [issue30179] Update Copyright to 2017
Message-ID: <1493245179.59.0.780402360042.issue30179@psf.upfronthosting.co.za>


New submission from Cheryl Sabella:

The copyright page is only through 2016.

----------
assignee: docs at python
components: Documentation
messages: 292383
nosy: csabella, docs at python
priority: normal
severity: normal
status: open
title: Update Copyright to 2017
type: enhancement
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30179>
_______________________________________

From report at bugs.python.org  Wed Apr 26 18:22:15 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Wed, 26 Apr 2017 22:22:15 +0000
Subject: [docs] [issue30179] Update Copyright to 2017
In-Reply-To: <1493245179.59.0.780402360042.issue30179@psf.upfronthosting.co.za>
Message-ID: <1493245335.47.0.138546369452.issue30179@psf.upfronthosting.co.za>


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


----------
pull_requests: +1416

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30179>
_______________________________________

From report at bugs.python.org  Wed Apr 26 18:34:47 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Wed, 26 Apr 2017 22:34:47 +0000
Subject: [docs] [issue30179] Update Copyright to 2017
In-Reply-To: <1493245179.59.0.780402360042.issue30179@psf.upfronthosting.co.za>
Message-ID: <1493246087.32.0.378253260199.issue30179@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Duplicate of http://bugs.python.org/issue29555.

----------
nosy: +Mariatta
resolution:  -> duplicate
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30179>
_______________________________________

From report at bugs.python.org  Wed Apr 26 20:51:12 2017
From: report at bugs.python.org (Joe Jevnik)
Date: Thu, 27 Apr 2017 00:51:12 +0000
Subject: [docs] [issue30180] PyArg_ParseTupleAndKeywords supports required
 keyword only arguments
In-Reply-To: <1493254262.66.0.357413160828.issue30180@psf.upfronthosting.co.za>
Message-ID: <1493254272.7.0.596844835287.issue30180@psf.upfronthosting.co.za>


Changes by Joe Jevnik <joe at quantopian.com>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30180>
_______________________________________

From report at bugs.python.org  Wed Apr 26 22:48:43 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 27 Apr 2017 02:48:43 +0000
Subject: [docs] [issue30176] curses attribute constants list is incomplete
In-Reply-To: <1493226906.47.0.950642994662.issue30176@psf.upfronthosting.co.za>
Message-ID: <1493261323.57.0.377180597764.issue30176@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

I can't find any official, portable doc about the details so I don't prefer to have them. I support bit-masks are different. Previously I don't what's the better way to organize them, now I have a try. Please check the update. :-)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30176>
_______________________________________

From report at bugs.python.org  Wed Apr 26 22:50:12 2017
From: report at bugs.python.org (Jesse Gonzalez)
Date: Thu, 27 Apr 2017 02:50:12 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
Message-ID: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>


New submission from Jesse Gonzalez:

When reviewing the Unicode HOWTO, I found a reference to ISO as "International Standards Organization", which should instead read "International Organization for Standardization".

https://www.iso.org/home.html

----------
assignee: docs at python
components: Documentation
messages: 292389
nosy: Jesse Gonzalez, docs at python
priority: normal
severity: normal
status: open
title: Incorrect in referring to ISO as "International Standards Organization"

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Wed Apr 26 22:53:18 2017
From: report at bugs.python.org (Louie Lu)
Date: Thu, 27 Apr 2017 02:53:18 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493261598.4.0.694639760952.issue30182@psf.upfronthosting.co.za>


Louie Lu added the comment:

Add the link: 

Python 3: https://docs.python.org/3/howto/unicode.html
Python 2: https://docs.python.org/2/howto/unicode.html

Both of 2 and 3 howto unicode use "International Standards Organization"


Jesse, would you like to create a PR for this?

----------
nosy: +louielu
versions: +Python 2.7, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Wed Apr 26 23:36:38 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 27 Apr 2017 03:36:38 +0000
Subject: [docs] [issue28415] PyUnicode_FromFormat integer format handling
 different from printf about zeropad
In-Reply-To: <1476176180.11.0.398413685253.issue28415@psf.upfronthosting.co.za>
Message-ID: <1493264198.11.0.984939329955.issue28415@psf.upfronthosting.co.za>


Xiang Zhang added the comment:


New changeset 88c38b32b761cb566759b8ad96704bff590a1de9 by Xiang Zhang (Louie Lu) in branch 'master':
bpo-28415: Note 0 conversion different between Python and C (#885)
https://github.com/python/cpython/commit/88c38b32b761cb566759b8ad96704bff590a1de9


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28415>
_______________________________________

From report at bugs.python.org  Wed Apr 26 23:38:33 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 27 Apr 2017 03:38:33 +0000
Subject: [docs] [issue28415] PyUnicode_FromFormat integer format handling
 different from printf about zeropad
In-Reply-To: <1476176180.11.0.398413685253.issue28415@psf.upfronthosting.co.za>
Message-ID: <1493264313.08.0.349523340713.issue28415@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
stage: needs patch -> resolved
status: open -> closed
versions:  -Python 2.7, Python 3.5, Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28415>
_______________________________________

From report at bugs.python.org  Wed Apr 26 23:43:28 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 27 Apr 2017 03:43:28 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493264608.05.0.225243194807.issue30182@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 00:41:57 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 27 Apr 2017 04:41:57 +0000
Subject: [docs] [issue21071] struct.Struct.format is bytes, but should be str
In-Reply-To: <1395856133.5.0.672707015318.issue21071@psf.upfronthosting.co.za>
Message-ID: <1493268117.33.0.48479665619.issue21071@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

+1 for change bytes to str. But struct.Struct() accepts both bytes and str, maybe in future buffer objects. When it gets a bytes object, converting it to a str looks unnecessary to me, and as OP said, comparison (a theoretical use case) could still fail. Could we just leave what the user passes in? bytes(bytes-like) -> bytes, str -> str. This looks more natural to me.

----------
nosy: +xiang.zhang

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21071>
_______________________________________

From report at bugs.python.org  Thu Apr 27 00:43:32 2017
From: report at bugs.python.org (Jesse Gonzalez)
Date: Thu, 27 Apr 2017 04:43:32 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493268212.53.0.890628697429.issue30182@psf.upfronthosting.co.za>


Changes by Jesse Gonzalez <jesse.gonzalez.jr at gmail.com>:


----------
pull_requests: +1419

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 00:54:01 2017
From: report at bugs.python.org (Jesse Gonzalez)
Date: Thu, 27 Apr 2017 04:54:01 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493268841.39.0.437684327974.issue30182@psf.upfronthosting.co.za>


Jesse Gonzalez added the comment:

PR created. CLA signed, but indicates otherwise in my account details.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 01:16:32 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 27 Apr 2017 05:16:32 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493270192.81.0.794525773217.issue30182@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +1420

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 01:16:39 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 27 Apr 2017 05:16:39 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493270199.35.0.0209779204277.issue30182@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +1421

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 01:16:45 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 27 Apr 2017 05:16:45 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493270205.9.0.131445108916.issue30182@psf.upfronthosting.co.za>


Changes by Mariatta Wijaya <mariatta.wijaya at gmail.com>:


----------
pull_requests: +1422

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 01:18:56 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 27 Apr 2017 05:18:56 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493270336.0.0.83324371752.issue30182@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 33a5568f69301562d536852d12b9e03cd8dfc3a4 by Mariatta in branch '3.6':
[3.6] bpo-30182: Use the correct name for ISO in Unicode HOWTO. (GH-1312) (GH-1313)
https://github.com/python/cpython/commit/33a5568f69301562d536852d12b9e03cd8dfc3a4


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 01:19:11 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 27 Apr 2017 05:19:11 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493270351.9.0.278966233392.issue30182@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset c4dfe2537fee970dc1bf3eb4fc2a3e007b36531c by Mariatta in branch '3.5':
[3.5] bpo-30182: Use the correct name for ISO in Unicode HOWTO. (GH-1312) (GH-1314)
https://github.com/python/cpython/commit/c4dfe2537fee970dc1bf3eb4fc2a3e007b36531c


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 01:25:42 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 27 Apr 2017 05:25:42 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493270742.53.0.112412066859.issue30182@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:


New changeset 24404b4c92fc4195422c38563d0c6204fa7b16b1 by Mariatta in branch '2.7':
[2.7] bpo-30182: Use the correct name for ISO in Unicode HOWTO. (GH-1312). (#1315)
https://github.com/python/cpython/commit/24404b4c92fc4195422c38563d0c6204fa7b16b1


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 01:26:28 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Thu, 27 Apr 2017 05:26:28 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493270788.08.0.875138264167.issue30182@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

Thanks :)

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 01:45:36 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Thu, 27 Apr 2017 05:45:36 +0000
Subject: [docs] [issue30182] Incorrect in referring to ISO as "International
 Standards Organization"
In-Reply-To: <1493261412.39.0.965032185029.issue30182@psf.upfronthosting.co.za>
Message-ID: <1493271936.52.0.0637669850785.issue30182@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Since I had the same wrong idea, I dug further into the site.
The explanation is at https://www.iso.org/about-us.html
'''
It's all in the name

Because 'International Organization for Standardization' would have different acronyms in different languages (IOS in English, OIN in French for Organisation internationale de normalisation), our founders decided to give it the short form ISO. ISO is derived from the Greek isos, meaning equal. Whatever the country, whatever the language, we are always ISO.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30182>
_______________________________________

From report at bugs.python.org  Thu Apr 27 03:05:22 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 27 Apr 2017 07:05:22 +0000
Subject: [docs] [issue21071] struct.Struct.format is bytes, but should be str
In-Reply-To: <1395856133.5.0.672707015318.issue21071@psf.upfronthosting.co.za>
Message-ID: <1493276722.75.0.96912630692.issue21071@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

After changing the type of Struct.format to str we perhaps should deprecate accepting bytes as format. Currently this can lead to emitting a BytesWarning.

$ ./python -Wa -b
>>> import struct
>>> struct.pack('I', 12345)
b'90\x00\x00'
>>> struct.pack(b'I', 12345)
__main__:1: BytesWarning: Comparison between bytes and string
__main__:1: BytesWarning: Comparison between bytes and string
b'90\x00\x00'

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21071>
_______________________________________

From report at bugs.python.org  Thu Apr 27 03:41:13 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 27 Apr 2017 07:41:13 +0000
Subject: [docs] [issue30179] Update Copyright to 2017
In-Reply-To: <1493245179.59.0.780402360042.issue30179@psf.upfronthosting.co.za>
Message-ID: <1493278873.03.0.592147688336.issue30179@psf.upfronthosting.co.za>


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


----------
superseder:  -> Update Python Software Foundation Copyright Year

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30179>
_______________________________________

From report at bugs.python.org  Thu Apr 27 04:48:52 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Thu, 27 Apr 2017 08:48:52 +0000
Subject: [docs] [issue21071] struct.Struct.format is bytes, but should be str
In-Reply-To: <1395856133.5.0.672707015318.issue21071@psf.upfronthosting.co.za>
Message-ID: <1493282932.27.0.529772913213.issue21071@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

The warnings are possible to remove I think... but deprecate bytes arguments sounds good.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21071>
_______________________________________

From report at bugs.python.org  Thu Apr 27 06:04:34 2017
From: report at bugs.python.org (Berker Peksag)
Date: Thu, 27 Apr 2017 10:04:34 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493287474.41.0.390418039906.issue30052@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Thu Apr 27 07:53:43 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 27 Apr 2017 11:53:43 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493294023.72.0.870223903244.issue30052@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

FYI.

When I tested this change locally, I needed to do a 'make clean' then a 'make html' for all the pages to relink to the stdtypes page for :class:`bytes`.  I had asked on the IRC channel about that and thought maybe the merge into the master would do that automatically, but checking some of the links (like on the urllib.parse page), it didn't update them.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Thu Apr 27 08:15:37 2017
From: report at bugs.python.org (Martin Panter)
Date: Thu, 27 Apr 2017 12:15:37 +0000
Subject: [docs] [issue30160] BaseHTTPRequestHandler.wfile: supported usage
 unclear
In-Reply-To: <1493131484.95.0.842958745675.issue30160@psf.upfronthosting.co.za>
Message-ID: <1493295337.05.0.246669904613.issue30160@psf.upfronthosting.co.za>


Martin Panter added the comment:

The ?Proper adherence? sentence has always bothered me. Why does ?wfile? have to adhere, but not other other APIs (rfile, send_header, etc)? I wonder if the sentence is useful at all. (Of course you have to use HTTP to operate with HTTP clients.)

Perhaps it was intended to say that socket-level HTTP is written to wfile, that it is up to the caller to ensure the encoding, content length, etc is consistent with the HTTP header, and/or the caller has to supply the header (either direct through wfile or via send_header etc). A plausable alternative would be a higher-level file object like the request body in ?http.client?, where encoding and content length is handled by the library.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30160>
_______________________________________

From report at bugs.python.org  Thu Apr 27 08:27:32 2017
From: report at bugs.python.org (R. David Murray)
Date: Thu, 27 Apr 2017 12:27:32 +0000
Subject: [docs] [issue30160] BaseHTTPRequestHandler.wfile: supported usage
 unclear
In-Reply-To: <1493131484.95.0.842958745675.issue30160@psf.upfronthosting.co.za>
Message-ID: <1493296052.74.0.022322730141.issue30160@psf.upfronthosting.co.za>


R. David Murray added the comment:

My impression is that the sentence is there because you are acting directly on the raw byte stream, which you are not in the other cases.  (Well, rfile, but that's reading, so what you do there doesn't affect the wire protocol you send).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30160>
_______________________________________

From report at bugs.python.org  Thu Apr 27 09:35:18 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 27 Apr 2017 13:35:18 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493300118.84.0.317846740535.issue30052@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Indeed, checking the dev build at https://docs.python.org/dev/library/urllib.parse.html#url-quoting shows it still linking to the old location.

Perhaps the `autobuild-dev-html` target in the Makefile should be adding `-E` and `-a` so it always regenerates everything, rather than re-using the potentially stale cached info from the previous day?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Thu Apr 27 17:14:32 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Thu, 27 Apr 2017 21:14:32 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493327672.04.0.478415736674.issue30052@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

I don't think it would add a lot of time or processing to rebuild it daily, would it?  Seems safer than not doing it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Fri Apr 28 01:39:19 2017
From: report at bugs.python.org (Mandeep Bhutani)
Date: Fri, 28 Apr 2017 05:39:19 +0000
Subject: [docs] [issue30004] in regex-howto, improve example on grouping
In-Reply-To: <1491453642.54.0.802330198745.issue30004@psf.upfronthosting.co.za>
Message-ID: <1493357959.18.0.346813593293.issue30004@psf.upfronthosting.co.za>


Mandeep Bhutani added the comment:

Looks like both examples need a closing \b. Is this being worked on or should I submit a PR?

----------
nosy: +mandeepb

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30004>
_______________________________________

From report at bugs.python.org  Fri Apr 28 05:30:14 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 28 Apr 2017 09:30:14 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493371814.21.0.496708429959.issue30052@psf.upfronthosting.co.za>


Changes by Nick Coghlan <ncoghlan at gmail.com>:


----------
pull_requests: +1450

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Fri Apr 28 05:33:44 2017
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 28 Apr 2017 09:33:44 +0000
Subject: [docs] [issue30052] URL Quoting page links to function Bytes
 instead of defintion
In-Reply-To: <1492001374.68.0.411275444037.issue30052@psf.upfronthosting.co.za>
Message-ID: <1493372024.72.0.620517906398.issue30052@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

New PR disabling the output caching and adding a corresponding NEWS entry: https://github.com/python/cpython/pull/1339

On my local machine, it takes a "nothing changed" build from less than 2 seconds to just under 2 minutes, but I think that's fine for a daily build task.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30052>
_______________________________________

From report at bugs.python.org  Fri Apr 28 17:14:04 2017
From: report at bugs.python.org (Ivan Levkivskyi)
Date: Fri, 28 Apr 2017 21:14:04 +0000
Subject: [docs] [issue30145] Create a How to or Tutorial documentation for
 asyncio
In-Reply-To: <1492960602.26.0.461554169011.issue30145@psf.upfronthosting.co.za>
Message-ID: <1493414044.69.0.97672596464.issue30145@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30145>
_______________________________________

From report at bugs.python.org  Fri Apr 28 17:17:33 2017
From: report at bugs.python.org (Yury Selivanov)
Date: Fri, 28 Apr 2017 21:17:33 +0000
Subject: [docs] [issue30145] Create a How to or Tutorial documentation for
 asyncio
In-Reply-To: <1492960602.26.0.461554169011.issue30145@psf.upfronthosting.co.za>
Message-ID: <1493414253.51.0.869027083901.issue30145@psf.upfronthosting.co.za>


Yury Selivanov added the comment:

Yes, this is a very longstanding open issue. I've already discussed this with Guido many times, and even found someone to help us. Will try to kickstart the project this weekend.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30145>
_______________________________________

From report at bugs.python.org  Fri Apr 28 23:07:47 2017
From: report at bugs.python.org (Martin Panter)
Date: Sat, 29 Apr 2017 03:07:47 +0000
Subject: [docs] [issue21071] struct.Struct.format is bytes, but should be str
In-Reply-To: <1395856133.5.0.672707015318.issue21071@psf.upfronthosting.co.za>
Message-ID: <1493435267.17.0.911335605178.issue21071@psf.upfronthosting.co.za>


Martin Panter added the comment:

I don?t think the API should be expanded to accept arbitrary bytes-like objects as format strings. Struct formats are strings of ASCII-compatible characters, but not arbitrary chunks of memory.

I think the main question is whether it is okay to break compatibility (Victor?s pull request, or my format-str.patch), or whether there has to be a backwards-compatible deprecation of the existing bytes attribute. FWIW I am okay with breaking compatibility, since the main documentation already implies it should be a text string.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21071>
_______________________________________

From report at bugs.python.org  Sat Apr 29 00:06:51 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 29 Apr 2017 04:06:51 +0000
Subject: [docs] [issue29576] Improve some deprecations in the importlib
In-Reply-To: <1487208454.1.0.000568467436348.issue29576@psf.upfronthosting.co.za>
Message-ID: <1493438811.38.0.42083128684.issue29576@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:


New changeset 3cc8259b71ef784a9f7593f04da96043afe2228a by Serhiy Storchaka in branch 'master':
bpo-30158: Fix deprecation warnings in test_importlib introduced by bpo-29576. (#1285)
https://github.com/python/cpython/commit/3cc8259b71ef784a9f7593f04da96043afe2228a


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29576>
_______________________________________

From report at bugs.python.org  Sat Apr 29 08:24:10 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Sat, 29 Apr 2017 12:24:10 +0000
Subject: [docs] [issue30128] xid_start definition for Unicode identifiers
 refers to xid_continue
In-Reply-To: <1492784841.26.0.847903278881.issue30128@psf.upfronthosting.co.za>
Message-ID: <1493468650.72.0.315416608974.issue30128@psf.upfronthosting.co.za>


Xiang Zhang added the comment:

Quoting from PEP3131:

XID_Start then closes this set under normalization, by removing all characters whose NFKC normalization is not of the form ID_Start ID_Continue* anymore.

----------
nosy: +loewis, xiang.zhang

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30128>
_______________________________________

From report at bugs.python.org  Sat Apr 29 09:42:38 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 29 Apr 2017 13:42:38 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
Message-ID: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>


New submission from Cheryl Sabella:

Fix some small typos in IDLE doc.

----------
assignee: docs at python
components: Documentation
messages: 292593
nosy: csabella, docs at python
priority: normal
severity: normal
status: open
title: Small typos in IDLE doc
type: enhancement

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 09:53:06 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 29 Apr 2017 13:53:06 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493473986.41.0.76876360682.issue30208@psf.upfronthosting.co.za>


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


----------
pull_requests: +1466

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 14:46:02 2017
From: report at bugs.python.org (Anthony Flury)
Date: Sat, 29 Apr 2017 18:46:02 +0000
Subject: [docs] [issue30210] No Documentation on tkinter dnd module
Message-ID: <1493491562.01.0.41832322565.issue30210@psf.upfronthosting.co.za>


New submission from Anthony Flury:

There is a level of drag and drop support within the tkinter package - namely the tkinter.dnd module. However there is no documentation at this time about drag and drop either on docs.python.org or on the tkinter reference manual.

The only documentation available is via the help command in the python console. or by reading the source code - neither of which are the first point of call for documentation.

----------
assignee: docs at python
components: Documentation
messages: 292596
nosy: anthony-flury, docs at python
priority: normal
severity: normal
status: open
title: No Documentation on tkinter dnd module
type: enhancement
versions: Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30210>
_______________________________________

From report at bugs.python.org  Sat Apr 29 15:54:20 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sat, 29 Apr 2017 19:54:20 +0000
Subject: [docs] [issue30211] Bdb: add docstrings
Message-ID: <1493495660.85.0.350046044168.issue30211@psf.upfronthosting.co.za>


New submission from Cheryl Sabella:

Add docstrings to Bdb.  See issue 19417.

----------
assignee: docs at python
components: Documentation
messages: 292598
nosy: csabella, docs at python, terry.reedy
priority: normal
pull_requests: 1467
severity: normal
status: open
title: Bdb: add docstrings
type: enhancement
versions: Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30211>
_______________________________________

From report at bugs.python.org  Sat Apr 29 18:28:38 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 29 Apr 2017 22:28:38 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493504918.81.0.555572942377.issue30208@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:


New changeset 9dc2b3809f38be2e403ee264958106badfda142d by terryjreedy (csabella) in branch 'master':
bpo-30208: DOC: fix small typos in IDLE (#1354)
https://github.com/python/cpython/commit/9dc2b3809f38be2e403ee264958106badfda142d


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 19:00:02 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 29 Apr 2017 23:00:02 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493506802.61.0.09404862546.issue30208@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Thank you for the review.  These are definitely bugs.  Please check IDLE component also for IDLE doc issues.  That will auto-assign them to me.

Your first merged PR?  If so, congrats.

Changes should be applied to at least 3.6, if not 3.5 and 2.7.  3.6 doc should be essentially identical, so I expect merge without conflict.  Likely true for others.  Can you (easily) prepare the PRs?  Can you use the cherry-pick script?

----------
assignee: docs at python -> terry.reedy
stage:  -> backport needed
versions: +Python 2.7, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 19:00:24 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 29 Apr 2017 23:00:24 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493506824.03.0.672773534559.issue30208@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 20:24:27 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 30 Apr 2017 00:24:27 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493511867.79.0.645187964948.issue30208@psf.upfronthosting.co.za>


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


----------
pull_requests: +1468

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 20:25:28 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 30 Apr 2017 00:25:28 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493511928.32.0.745753683453.issue30208@psf.upfronthosting.co.za>


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


----------
pull_requests: +1469

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 20:26:13 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 30 Apr 2017 00:26:13 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493511973.53.0.725051644152.issue30208@psf.upfronthosting.co.za>


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


----------
pull_requests: +1470

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 20:31:04 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 30 Apr 2017 00:31:04 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493512264.22.0.830412953908.issue30208@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

I followed the steps for cherry-pick, but messed up a little as I made 3 PRs instead of one.  However, I couldn't do the labels asked for in this section:

When a cherry-pick was applied successfully, this script will open up a browser tab that points to the pull request creation page.

The url of the pull request page looks similar to the following:

https://github.com/python/cpython/compare/3.5...<username>:backport-6de2b78-3.5?expand=1

    Apply the appropriate cherry-pick for ... label
    Press the Create Pull Request button.
    Remove the needs backport to ... label from the original pull request against master.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 20:42:05 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 30 Apr 2017 00:42:05 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493512925.7.0.196831784075.issue30208@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:


New changeset 5a8dcec93936de816cef5c17522e48fca9c30b43 by terryjreedy (csabella) in branch '3.6':
[3.6] bpo-30208: DOC: fix small typos in IDLE (#1356)
https://github.com/python/cpython/commit/5a8dcec93936de816cef5c17522e48fca9c30b43


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 20:43:13 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 30 Apr 2017 00:43:13 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493512993.26.0.0807175036715.issue30208@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:


New changeset 52630ae17aa5bd8bffdb430b6515d07ffbaabc9e by terryjreedy (csabella) in branch '3.5':
[3.5] bpo-30208: DOC: fix small typos in IDLE (#1357)
https://github.com/python/cpython/commit/52630ae17aa5bd8bffdb430b6515d07ffbaabc9e


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 20:44:06 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 30 Apr 2017 00:44:06 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493513046.72.0.798630541048.issue30208@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:


New changeset 4734c2d5c0529632e4b51eb75104b50955afd692 by terryjreedy (csabella) in branch '2.7':
[2.7] bpo-30208: DOC: fix small typos in IDLE (#1358)
https://github.com/python/cpython/commit/4734c2d5c0529632e4b51eb75104b50955afd692


----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 20:49:42 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 30 Apr 2017 00:49:42 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493513382.47.0.888566218904.issue30208@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

>From what I have seen, one PR for each branch is correct.  I believe cherry-pick.py was initially written by Mariatta.  Please bring up any problems or questions using it on core-mentorship, where she and others will see it.

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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 20:51:47 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 30 Apr 2017 00:51:47 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493513507.6.0.860308459159.issue30208@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

For this "Please check IDLE component also for IDLE doc issues.", I see the same text as the doc page in idlelib/help/html.  Is that the one you want me to change or is that created automatically by Sphinx?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sat Apr 29 20:58:02 2017
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 30 Apr 2017 00:58:02 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493513882.04.0.271480612721.issue30208@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I mean 'IDLE' in the Components: box, to the left of the Versions: box, both in the 'classification' frame near the top of this page.

----------
components: +IDLE

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sun Apr 30 05:22:52 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 30 Apr 2017 09:22:52 +0000
Subject: [docs] [issue30208] Small typos in IDLE doc
In-Reply-To: <1493473358.59.0.135881718149.issue30208@psf.upfronthosting.co.za>
Message-ID: <1493544171.99.0.761958852892.issue30208@psf.upfronthosting.co.za>


Cheryl Sabella added the comment:

LOL, well I made that a lot harder than you intended.  :-)

----------
components:  -Documentation

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30208>
_______________________________________

From report at bugs.python.org  Sun Apr 30 07:23:11 2017
From: report at bugs.python.org (Xiang Zhang)
Date: Sun, 30 Apr 2017 11:23:11 +0000
Subject: [docs] [issue30210] No Documentation on tkinter dnd module
In-Reply-To: <1493491562.01.0.41832322565.issue30210@psf.upfronthosting.co.za>
Message-ID: <1493551391.9.0.631167729609.issue30210@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30210>
_______________________________________

From report at bugs.python.org  Sun Apr 30 07:38:59 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 30 Apr 2017 11:38:59 +0000
Subject: [docs] [issue30211] Bdb: add docstrings
In-Reply-To: <1493495660.85.0.350046044168.issue30211@psf.upfronthosting.co.za>
Message-ID: <1493552339.46.0.799398300554.issue30211@psf.upfronthosting.co.za>


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


----------
components: +IDLE -Documentation

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30211>
_______________________________________

From report at bugs.python.org  Sun Apr 30 07:39:09 2017
From: report at bugs.python.org (Cheryl Sabella)
Date: Sun, 30 Apr 2017 11:39:09 +0000
Subject: [docs] [issue30211] Bdb: add docstrings
In-Reply-To: <1493495660.85.0.350046044168.issue30211@psf.upfronthosting.co.za>
Message-ID: <1493552349.1.0.215552777313.issue30211@psf.upfronthosting.co.za>


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


----------
components: +Documentation -IDLE

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30211>
_______________________________________

From report at bugs.python.org  Sun Apr 30 07:45:55 2017
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 30 Apr 2017 11:45:55 +0000
Subject: [docs] [issue30210] No Documentation on tkinter dnd module
In-Reply-To: <1493491562.01.0.41832322565.issue30210@psf.upfronthosting.co.za>
Message-ID: <1493552755.54.0.731523957164.issue30210@psf.upfronthosting.co.za>


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


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

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30210>
_______________________________________

From report at bugs.python.org  Sun Apr 30 08:05:43 2017
From: report at bugs.python.org (Martin Panter)
Date: Sun, 30 Apr 2017 12:05:43 +0000
Subject: [docs] [issue15346] Tkinter extention modules have no documentation
In-Reply-To: <1342198047.2.0.619885102312.issue15346@psf.upfronthosting.co.za>
Message-ID: <1493553943.58.0.238797764319.issue15346@psf.upfronthosting.co.za>


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


----------
dependencies: +No Documentation on tkinter dnd module

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15346>
_______________________________________

From report at bugs.python.org  Sun Apr 30 08:14:13 2017
From: report at bugs.python.org (Martin Panter)
Date: Sun, 30 Apr 2017 12:14:13 +0000
Subject: [docs] [issue30145] Create a How to or Tutorial documentation for
 asyncio
In-Reply-To: <1492960602.26.0.461554169011.issue30145@psf.upfronthosting.co.za>
Message-ID: <1493554453.56.0.851518967608.issue30145@psf.upfronthosting.co.za>


Martin Panter added the comment:

See Issue 27579, where Victor wanted to focus on <https://github.com/asyncio-doc/asyncio-doc> outside of Python.

----------
nosy: +haypo, martin.panter

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30145>
_______________________________________

From report at bugs.python.org  Sun Apr 30 13:14:36 2017
From: report at bugs.python.org (Mariatta Wijaya)
Date: Sun, 30 Apr 2017 17:14:36 +0000
Subject: [docs] [issue30145] Create a How to or Tutorial documentation for
 asyncio
In-Reply-To: <1492960602.26.0.461554169011.issue30145@psf.upfronthosting.co.za>
Message-ID: <1493572476.03.0.591393936565.issue30145@psf.upfronthosting.co.za>


Mariatta Wijaya added the comment:

I think it will still be useful to have an authoritative tutorial within CPython docs.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30145>
_______________________________________

From report at bugs.python.org  Sun Apr 30 15:56:00 2017
From: report at bugs.python.org (Eric O. LEBIGOT)
Date: Sun, 30 Apr 2017 19:56:00 +0000
Subject: [docs] [issue30217] Missing entry for the tilde (~) operator in the
 Index
Message-ID: <1493582160.76.0.882487661277.issue30217@psf.upfronthosting.co.za>


New submission from Eric O. LEBIGOT:

The index (https://docs.python.org/3.6/genindex-Symbols.html) is missing an entry for the tilde operator ~ (there is also no entry under "tilde").

A relevant pointer could be to object.__invert__ (https://docs.python.org/3.6/reference/datamodel.html#object.__invert__).

----------
assignee: docs at python
components: Documentation
messages: 292641
nosy: docs at python, lebigot
priority: normal
severity: normal
status: open
title: Missing entry for the tilde (~) operator in the Index
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30217>
_______________________________________

From report at bugs.python.org  Sun Apr 30 18:27:57 2017
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 30 Apr 2017 22:27:57 +0000
Subject: [docs] [issue30145] Create a How to or Tutorial documentation for
 asyncio
In-Reply-To: <1493572476.03.0.591393936565.issue30145@psf.upfronthosting.co.za>
Message-ID: <CAMpsgwbm6=K18jx8aj2M5GNZbPQZf4w24GsHvKnADwjimnsbGQ@mail.gmail.com>


STINNER Victor added the comment:

Mariatta Wijaya added the comment:

I think it will still be useful to have an authoritative tutorial within
CPython docs.

The problem is that Python stdlib is quite limited: no HTTP, no SQL client,
etc. An external tutorial can use 3rd party modules like aiohttp.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30145>
_______________________________________

From report at bugs.python.org  Sun Apr 30 18:30:32 2017
From: report at bugs.python.org (Yury Selivanov)
Date: Sun, 30 Apr 2017 22:30:32 +0000
Subject: [docs] [issue30145] Create a How to or Tutorial documentation for
 asyncio
In-Reply-To: <1492960602.26.0.461554169011.issue30145@psf.upfronthosting.co.za>
Message-ID: <1493591432.69.0.444740565249.issue30145@psf.upfronthosting.co.za>


Yury Selivanov added the comment:

> The problem is that Python stdlib is quite limited: no HTTP, no SQL client,
etc. An external tutorial can use 3rd party modules like aiohttp.

Even without aiohttp we can show how to use asyncio correctly. I agree with Mariatta that we should have a tutorial etc. Working on it.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue30145>
_______________________________________

From hunt.robertj at gmail.com  Wed Apr 26 22:59:10 2017
From: hunt.robertj at gmail.com (Robert Hunt)
Date: Thu, 27 Apr 2017 14:59:10 +1200
Subject: [docs] Section not updated
Message-ID: <8cbc49a7-9ab5-dc93-9175-5c3b20a23813@gmail.com>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20170427/cf3dd1be/attachment.html>