From report at bugs.python.org  Fri Nov  1 12:54:23 2013
From: report at bugs.python.org (Marco Buttu)
Date: Fri, 01 Nov 2013 11:54:23 +0000
Subject: [docs] [issue19472] inspect.getsource() raises a wrong exception
	type
Message-ID: <1383306863.35.0.879382426433.issue19472@psf.upfronthosting.co.za>


New submission from Marco Buttu:

I was looking at inspect.getsource(). In Python 3.3 and 3.4 either the docstring and the online doc say it raises a OSError, and in fact: 


>>> import inspect
>>> def foo():
...     pass
... 
>>> inspect.getsource(foo)
Traceback (most recent call last):
    ...
OSError: could not get source code


However, getsource() calls getfile(), and this one raises a TypeError:


>>> inspect.getsource(0)
Traceback (most recent call last):
 ...
TypeError: 0 is not a module, class, method, function, traceback, frame, or code object

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 201891
nosy: docs at python, marco.buttu
priority: normal
severity: normal
status: open
title: inspect.getsource() raises a wrong exception type
type: behavior
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Nov  1 19:43:21 2013
From: report at bugs.python.org (Stefan Behnel)
Date: Fri, 01 Nov 2013 18:43:21 +0000
Subject: [docs] [issue19477] document tp_print() as being dead in Py3
Message-ID: <1383331401.83.0.986088466963.issue19477@psf.upfronthosting.co.za>


New submission from Stefan Behnel:

The "tp_print" slot is still documented as it was in Py2, although it is no longer used in Py3.

http://docs.python.org/3.4/c-api/typeobj.html?highlight=tp_print#PyTypeObject.tp_print

Given that it no longer serves any purpose, it should at least be deprecated and documented as unused/ignored (and eventually removed completely, at the same time as tp_reserved).

----------
assignee: docs at python
components: Documentation
messages: 201933
nosy: docs at python, scoder
priority: normal
severity: normal
status: open
title: document tp_print() as being dead in Py3
type: behavior
versions: Python 3.1, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Nov  2 03:55:46 2013
From: report at bugs.python.org (Martin Panter)
Date: Sat, 02 Nov 2013 02:55:46 +0000
Subject: [docs] [issue19411] binascii.hexlify docs say it returns a string
	(it	returns bytes)
In-Reply-To: <1382807910.82.0.748740374727.issue19411@psf.upfronthosting.co.za>
Message-ID: <1383360946.65.0.72933306827.issue19411@psf.upfronthosting.co.za>


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


----------
nosy: +vadmium

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

From report at bugs.python.org  Sat Nov  2 05:26:16 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sat, 02 Nov 2013 04:26:16 +0000
Subject: [docs] [issue19411] binascii.hexlify docs say it returns a string
	(it	returns bytes)
In-Reply-To: <1382807910.82.0.748740374727.issue19411@psf.upfronthosting.co.za>
Message-ID: <1383366376.41.0.298270798078.issue19411@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

Attached the patch to fix the doc. I also fix the module doc because I think bytes and str data types are matter of life and death in this binascii module.

----------
keywords: +patch
nosy: +vajrasky
Added file: http://bugs.python.org/file32459/fix_doc_binascii.patch

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

From report at bugs.python.org  Sun Nov  3 04:34:26 2013
From: report at bugs.python.org (Zachary Ware)
Date: Sun, 03 Nov 2013 03:34:26 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383449666.9.0.165231282438.issue19391@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


----------
assignee: docs at python -> zach.ware
stage:  -> patch review

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

From report at bugs.python.org  Sun Nov  3 05:48:53 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sun, 03 Nov 2013 04:48:53 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383454133.55.0.924675194227.issue19391@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

Zachary, perharps you could make a diff with mercurial so we can have Rietveld review link. I don't know whether git can do that or not.

----------
nosy: +vajrasky

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

From report at bugs.python.org  Sun Nov  3 06:07:55 2013
From: report at bugs.python.org (Zachary Ware)
Date: Sun, 03 Nov 2013 05:07:55 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383455275.33.0.722938717162.issue19391@psf.upfronthosting.co.za>


Zachary Ware added the comment:

These diffs are produced by `hg diff --git`.  If I'm not mistaken, the reason there is no review link is because these patches are not against default branch.  Here's one without the `--git` option though, just to see if I'm wrong :).  If I am, I'll replace all of them.

----------
Added file: http://bugs.python.org/file32468/pcbuild_readme-2.7.diff-w-no-git

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

From report at bugs.python.org  Sun Nov  3 06:11:42 2013
From: report at bugs.python.org (Zachary Ware)
Date: Sun, 03 Nov 2013 05:11:42 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383455502.24.0.357043503423.issue19391@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


Removed file: http://bugs.python.org/file32356/pcbuild_readme-2.7.diff

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

From report at bugs.python.org  Sun Nov  3 06:11:58 2013
From: report at bugs.python.org (Zachary Ware)
Date: Sun, 03 Nov 2013 05:11:58 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383455517.05.0.724541350496.issue19391@psf.upfronthosting.co.za>


Zachary Ware added the comment:

How wrong I was...

----------
Added file: http://bugs.python.org/file32469/pcbuild_readme-2.7.diff

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

From report at bugs.python.org  Sun Nov  3 06:13:40 2013
From: report at bugs.python.org (Zachary Ware)
Date: Sun, 03 Nov 2013 05:13:40 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383455620.94.0.19830908195.issue19391@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


Removed file: http://bugs.python.org/file32354/pcbuild_readme-3.3.diff

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

From report at bugs.python.org  Sun Nov  3 06:13:54 2013
From: report at bugs.python.org (Zachary Ware)
Date: Sun, 03 Nov 2013 05:13:54 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383455633.75.0.56636385575.issue19391@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


Added file: http://bugs.python.org/file32470/pcbuild_readme-3.3.diff

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

From report at bugs.python.org  Sun Nov  3 06:15:35 2013
From: report at bugs.python.org (Zachary Ware)
Date: Sun, 03 Nov 2013 05:15:35 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383455735.22.0.284227402178.issue19391@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


Removed file: http://bugs.python.org/file32468/pcbuild_readme-2.7.diff-w-no-git

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

From report at bugs.python.org  Sun Nov  3 06:25:42 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 03 Nov 2013 05:25:42 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383456342.48.0.109113727568.issue19391@psf.upfronthosting.co.za>


R. David Murray added the comment:

With the --git option, the rietveld service only tries against the default branch.  Without the --git option, it can figure out the changeset the patch is based against and use that.

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

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

From report at bugs.python.org  Sun Nov  3 16:12:10 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sun, 03 Nov 2013 15:12:10 +0000
Subject: [docs] [issue19485] Slightly incorrect doc for get_param method
	in	Lib/email/message.py
Message-ID: <1383491530.88.0.114432864855.issue19485@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

Lib/email/message.py, line 665 & 666:

    param = msg.get_param('foo')
    param = email.utils.collapse_rfc2231_value(rawparam)

Where does rawparam come from?

On top of that, sending the result of get_param to collapse_rfc2231_value can make it chokes if the result of get_param is None. I already proposed the change in collapse_rfc2231_value to handle None gracefully in another ticket #19063, though.

----------
assignee: docs at python
components: Documentation
files: fix_doc_get_param_in_email_message.patch
keywords: patch
messages: 202029
nosy: docs at python, vajrasky
priority: normal
severity: normal
status: open
title: Slightly incorrect doc for get_param method in Lib/email/message.py
versions: Python 3.4
Added file: http://bugs.python.org/file32480/fix_doc_get_param_in_email_message.patch

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

From report at bugs.python.org  Sun Nov  3 16:12:23 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sun, 03 Nov 2013 15:12:23 +0000
Subject: [docs] [issue19485] Slightly incorrect doc for get_param method
	in	Lib/email/message.py
In-Reply-To: <1383491530.88.0.114432864855.issue19485@psf.upfronthosting.co.za>
Message-ID: <1383491543.65.0.291452518573.issue19485@psf.upfronthosting.co.za>


Changes by Vajrasky Kok <sky.kok at speaklikeaking.com>:


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

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

From report at bugs.python.org  Sun Nov  3 17:10:04 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 03 Nov 2013 16:10:04 +0000
Subject: [docs] [issue19485] Slightly incorrect doc for get_param method
	in	Lib/email/message.py
In-Reply-To: <1383491530.88.0.114432864855.issue19485@psf.upfronthosting.co.za>
Message-ID: <1383495004.52.0.0499663232476.issue19485@psf.upfronthosting.co.za>


R. David Murray added the comment:

Vajrasky: FYI, you can select the 'email' component for tickets like this, and I'll be automatically made nosy (as will Barry Warsaw).

----------
components: +email
nosy: +barry
type:  -> behavior
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Sun Nov  3 18:08:39 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 03 Nov 2013 17:08:39 +0000
Subject: [docs] [issue18985] Improve the documentation in fcntl module
In-Reply-To: <1378722919.93.0.901392318122.issue18985@psf.upfronthosting.co.za>
Message-ID: <1383498519.95.0.575345723804.issue18985@psf.upfronthosting.co.za>


R. David Murray added the comment:

Vajrasky: what do you think of my version?  Is it clear enough?

I wonder if we want to document the constants someday.

----------
stage:  -> patch review
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Sun Nov  3 18:34:03 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 03 Nov 2013 17:34:03 +0000
Subject: [docs] [issue19485] Slightly incorrect doc for get_param method
	in	Lib/email/message.py
In-Reply-To: <1383491530.88.0.114432864855.issue19485@psf.upfronthosting.co.za>
Message-ID: <3dCPPd2kFhz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset c574951deadd by R David Murray in branch '3.3':
#19485: clarify get_param example.
http://hg.python.org/cpython/rev/c574951deadd

New changeset e3180c58a78c by R David Murray in branch 'default':
Merge #19485: clarify get_param example.
http://hg.python.org/cpython/rev/e3180c58a78c

----------
nosy: +python-dev

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

From report at bugs.python.org  Sun Nov  3 18:35:49 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 03 Nov 2013 17:35:49 +0000
Subject: [docs] [issue19485] Slightly incorrect doc for get_param method
	in	Lib/email/message.py
In-Reply-To: <1383491530.88.0.114432864855.issue19485@psf.upfronthosting.co.za>
Message-ID: <1383500149.8.0.0635281413426.issue19485@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks, Vajrasky.  Looks like this was a cut and paste error when Barry updated the docs for 3.3, since it is correct in the 2.7 module.

----------
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sun Nov  3 18:38:46 2013
From: report at bugs.python.org (iMom0)
Date: Sun, 03 Nov 2013 17:38:46 +0000
Subject: [docs] [issue19487] Correct the error of the example given in the
	doc of	partialmethod
Message-ID: <1383500326.49.0.984893748301.issue19487@psf.upfronthosting.co.za>


Changes by iMom0 <mobeiheart at gmail.com>:


----------
assignee: docs at python
components: Documentation
files: partialmethod-doc-fix.patch
keywords: patch
nosy: docs at python, imom0
priority: normal
severity: normal
status: open
title: Correct the error of the example given in the doc of partialmethod
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file32484/partialmethod-doc-fix.patch

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

From report at bugs.python.org  Sun Nov  3 19:22:44 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 03 Nov 2013 18:22:44 +0000
Subject: [docs] [issue19411] binascii.hexlify docs say it returns a string
	(it	returns bytes)
In-Reply-To: <1382807910.82.0.748740374727.issue19411@psf.upfronthosting.co.za>
Message-ID: <3dCQVC3cDqz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 25d89a4faede by R David Murray in branch '3.3':
#19411: Clarify that b2a_hex/hexlify returns a bytes object.
http://hg.python.org/cpython/rev/25d89a4faede

New changeset ac190d03aed5 by R David Murray in branch 'default':
Merge #19411: Clarify that b2a_hex/hexlify returns a bytes object.
http://hg.python.org/cpython/rev/ac190d03aed5

----------
nosy: +python-dev

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

From report at bugs.python.org  Sun Nov  3 19:23:42 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 03 Nov 2013 18:23:42 +0000
Subject: [docs] [issue19411] binascii.hexlify docs say it returns a string
	(it	returns bytes)
In-Reply-To: <1382807910.82.0.748740374727.issue19411@psf.upfronthosting.co.za>
Message-ID: <1383503022.66.0.574533389341.issue19411@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks, Vajrasky.  I modified the patch slightly since I prefer the term "bytes object" to just "bytes" (I think it reads better in English).

----------
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sun Nov  3 19:37:32 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 03 Nov 2013 18:37:32 +0000
Subject: [docs] [issue19487] Correct the error of the example given in the
	doc of	partialmethod
Message-ID: <1383503852.68.0.684978986837.issue19487@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Nov  3 20:15:54 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 03 Nov 2013 19:15:54 +0000
Subject: [docs] [issue19454] devguide: Document what a "platform support" is
In-Reply-To: <1383159116.46.0.184690879028.issue19454@psf.upfronthosting.co.za>
Message-ID: <1383506154.99.0.972436486772.issue19454@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Nov  4 00:56:39 2013
From: report at bugs.python.org (Brian Curtin)
Date: Sun, 03 Nov 2013 23:56:39 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383522999.71.0.43409104692.issue19391@psf.upfronthosting.co.za>


Brian Curtin added the comment:

Both patches look fine to me.

----------

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

From report at bugs.python.org  Mon Nov  4 04:53:10 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 04 Nov 2013 03:53:10 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <3dCg8P2Pwgz7LjN@mail.python.org>


Roundup Robot added the comment:

New changeset 7b6ac858bb17 by Zachary Ware in branch '2.7':
Issue #19391: Clean up PCbuild/readme.txt
http://hg.python.org/cpython/rev/7b6ac858bb17

New changeset f28a2d072767 by Zachary Ware in branch '3.3':
Issue #19391: Clean up PCbuild/readme.txt
http://hg.python.org/cpython/rev/f28a2d072767

----------

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

From report at bugs.python.org  Mon Nov  4 04:58:45 2013
From: report at bugs.python.org (Zachary Ware)
Date: Mon, 04 Nov 2013 03:58:45 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
In-Reply-To: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>
Message-ID: <1383537525.69.0.669867832273.issue19391@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Thanks for the lesson, Vajrasky and David, and thank you for the review Brian.

The final commit did have a couple changes not in the posted patch, just fixes of the same two obvious typos in both branches (avalible -> available, lniked -> linked).

----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Mon Nov  4 07:08:50 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Mon, 04 Nov 2013 06:08:50 +0000
Subject: [docs] [issue18985] Improve the documentation in fcntl module
In-Reply-To: <1378722919.93.0.901392318122.issue18985@psf.upfronthosting.co.za>
Message-ID: <1383545330.89.0.570565058746.issue18985@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

Except for the typo noticed by Victor, your patch looks good.

----------

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

From report at bugs.python.org  Mon Nov  4 07:28:30 2013
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 04 Nov 2013 06:28:30 +0000
Subject: [docs] [issue19489] move quick search box above TOC
Message-ID: <1383546510.68.0.587653327623.issue19489@psf.upfronthosting.co.za>


New submission from Georg Brandl:

>From Mark Summerfield:,

    The Quick search box is really useful, but it is annoying that its
    position varies from page to page. On pages with long tables of
    contents it is often out of sight.

    Why not put it above the Table of Contents. That way it is always
    in the same place and easily accessible.

----------
assignee: docs at python
components: Documentation
messages: 202091
nosy: docs at python, georg.brandl
priority: normal
severity: normal
status: open
title: move quick search box above TOC

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

From j.ammon at dr-ammon.de  Fri Nov  1 07:38:58 2013
From: j.ammon at dr-ammon.de (Johannes Ammon)
Date: Fri, 01 Nov 2013 07:38:58 +0100
Subject: [docs] Suggestion for documentation improvement
Message-ID: <52734C82.2010007@dr-ammon.de>

Dear python developpers,

I ran into the unicode problem of the csv module in the python standard
library (2.7.5) and immediately found the solution in the docs. I just
used the UTF8Recoder/UnicodeReader/UnicodeWriter proposed in
http://docs.python.org/2/library/csv.html#examples. Thank you for that!

There is just one little problem with UnicodeWriter, which imho has an
easy solution:

class UnicodeWriter:
"..."
    def writerow(self, row):
        self.writer.writerow([s.encode("utf-8") for s in row])
        "..."

When "s" is not a string (i.e. when "row" contains an element, that is
e.g. None or an int, which is ok for csv.writer), I get a

"AttributeError: 'NoneType' object has no attribute 'encode'"

So I changed this bit of code to

    def writerow(self, row):
        self.writer.writerow([unicode(s).encode("utf-8") if s is not None
                              else "" for s in row])
        "..."

Ok, this is a bit complicated for an educational code sample, but I
think there are more people like me, that just use the code samples from
the docs.

Best regards, Johannes


From bgailer at gmail.com  Fri Nov  1 14:49:46 2013
From: bgailer at gmail.com (bob gailer)
Date: Fri, 01 Nov 2013 09:49:46 -0400
Subject: [docs] Undocumented feature - should be documented.
Message-ID: <5273B17A.4030701@gmail.com>

According to the FM:

"str.translate(map)
Return a copy of the s where all characters have been mapped through the map
which must be a dictionary of Unicode ordinals (integers) to Unicode
ordinals, strings or None. Unmapped characters are left untouched.
Characters mapped to None are deleted."

So 'acxd'.translate(' '*97 + 'sdfg') should raise an exception, as the 
map is NOT a dictionary.

However it runs and returns 'sfxg' This is a very nice feature - let's 
document it!

-- 
Bob Gailer
919-636-4239
Chapel Hill NC


From report at bugs.python.org  Mon Nov  4 10:28:17 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 04 Nov 2013 09:28:17 +0000
Subject: [docs] [issue17827] Document codecs.encode and codecs.decode
In-Reply-To: <1366811140.15.0.0983174574305.issue17827@psf.upfronthosting.co.za>
Message-ID: <1383557297.77.0.73687239763.issue17827@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Hmm, I just noticed an interesting issue here in drafting the 2.7 backport: as near as I can tell, these aren't tested, so other implementations that failed to provide them would pass the 2.7 and 3.3 test suites.

----------
Added file: http://bugs.python.org/file32492/issue17827_docs_py27.diff

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

From report at bugs.python.org  Mon Nov  4 10:31:43 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 04 Nov 2013 09:31:43 +0000
Subject: [docs] [issue17827] Document and test codecs.encode and
	codecs.decode
In-Reply-To: <1366811140.15.0.0983174574305.issue17827@psf.upfronthosting.co.za>
Message-ID: <1383557503.55.0.674000971603.issue17827@psf.upfronthosting.co.za>


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


----------
title: Document codecs.encode and codecs.decode -> Document and test codecs.encode and codecs.decode
versions: +Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Nov  4 10:47:21 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 04 Nov 2013 09:47:21 +0000
Subject: [docs] [issue17827] Document codecs.encode and codecs.decode
In-Reply-To: <1366811140.15.0.0983174574305.issue17827@psf.upfronthosting.co.za>
Message-ID: <1383558441.13.0.728179256022.issue17827@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Oops, never mind - the tests are already there (and have been since MAL's original commit prior to Python 2.4), I just fail at searching code.

----------
title: Document and test codecs.encode and codecs.decode -> Document codecs.encode and codecs.decode
versions:  -Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Nov  4 11:08:46 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 04 Nov 2013 10:08:46 +0000
Subject: [docs] [issue17827] Document codecs.encode and codecs.decode
In-Reply-To: <1366811140.15.0.0983174574305.issue17827@psf.upfronthosting.co.za>
Message-ID: <3dCqTn5PDGz7Ljv@mail.python.org>


Roundup Robot added the comment:

New changeset bdb30bdf60a5 by Nick Coghlan in branch '2.7':
Close #17827: Document codecs.encode & codecs.decode
http://hg.python.org/cpython/rev/bdb30bdf60a5

----------
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Mon Nov  4 14:34:21 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 04 Nov 2013 13:34:21 +0000
Subject: [docs] [issue19487] Correct the error of the example given in the
	doc of	partialmethod
Message-ID: <1383572061.25.0.822641144667.issue19487@psf.upfronthosting.co.za>


New submission from Nick Coghlan:

Thanks for the report, this has now been fixed in http://hg.python.org/cpython/rev/ac1685661b07

----------
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Tue Nov  5 03:54:49 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 05 Nov 2013 02:54:49 +0000
Subject: [docs] [issue19154] AttributeError: 'NoneType' in http/client.py
	when using	select when file descriptor is closed.
In-Reply-To: <1380820358.99.0.777618727237.issue19154@psf.upfronthosting.co.za>
Message-ID: <1383620089.62.0.304771464725.issue19154@psf.upfronthosting.co.za>


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


----------
versions:  -Python 2.7, Python 3.3

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

From georg at python.org  Tue Nov  5 07:32:16 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 05 Nov 2013 07:32:16 +0100
Subject: [docs] python2.7/subprocess.py Popen on Ubuntu 10.04 Bug
In-Reply-To: <OF0B78D7B9.90A03F9D-ONC2257C14.004BCA58-C2257C14.004CD910@il.ibm.com>
References: <OF0B78D7B9.90A03F9D-ONC2257C14.004BCA58-C2257C14.004CD910@il.ibm.com>
Message-ID: <527890F0.2000700@python.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 30.10.2013 14:59, schrieb Eyal Moscovici:
> Hi,
> 
> I found that using Popen with both executable and shell parameters set
> creates a bug:
> 
> For example:
> 
> Calling:
> 
> Popen(["-a"], exacutable="/bin/ls", shell=True)
> 
> Exacutes: /bin/ls -c -a instead of: /bin/sh -c "/bin/ls -a"
> 
> The bug in the function: def _execute_child(self, args, executable,
> preexec_fn, close_fds, cwd, env, universal_newlines, startupinfo,
> creationflags, shell, p2cread, p2cwrite, c2pread, c2pwrite, errread,
> errwrite): """Execute program (POSIX version)"""
> 
> Lines: 1124-1127:
> 
> if shell: args = ["/bin/sh", "-c"] + args if executable: args[0] =
> executable

Hi Eyal,

thanks for your report.  This is working as documented; if shell is true
the "executable" argument specifies a replacement for /bin/sh, not for the
command.

Also you'll always have to include an executable name in your args as well:

Popen('ls -a', shell=True)

cheers,
Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlJ4kPAACgkQN9GcIYhpnLBVAACfUQFDBt5YnbwlX5XWrqOBXSpk
vM8Ani4spDk68YckLcIAd5xOoSqPQUzg
=Nxrk
-----END PGP SIGNATURE-----

From report at bugs.python.org  Tue Nov  5 14:46:42 2013
From: report at bugs.python.org (Eric V. Smith)
Date: Tue, 05 Nov 2013 13:46:42 +0000
Subject: [docs] [issue19504] Change "customise" to "customize".
Message-ID: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za>


New submission from Eric V. Smith:

The python source code usually uses "customiz*" (341 instances) over "customis*" (19 instance, 8 of which are in logging).

I realize "foolish consistency", and all that, but I think the documentation should all use the same conventions. I'd be happy to change the documentation.

Most of these changes are in documentation or docstrings, but some are in comments. Which is why I'm assigning to docs at . I didn't change 2.0.rst, because that seemed like a historical document.

----------
assignee: docs at python
components: Documentation
files: customise.diff
keywords: easy, patch
messages: 202210
nosy: docs at python, eric.smith
priority: low
severity: normal
stage: patch review
status: open
title: Change "customise" to "customize".
versions: Python 3.4
Added file: http://bugs.python.org/file32507/customise.diff

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

From report at bugs.python.org  Tue Nov  5 17:55:55 2013
From: report at bugs.python.org (Cameron Allan)
Date: Tue, 05 Nov 2013 16:55:55 +0000
Subject: [docs] [issue19504] Change "customise" to "customize".
In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za>
Message-ID: <1383670548.62.0.175715316802.issue19504@psf.upfronthosting.co.za>


Cameron Allan added the comment:

Done using Notepad++ and regex as needed.

Also changed file name appropriately.

----------
nosy: +c3n9
Added file: http://bugs.python.org/file32510/customize.diff

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

From report at bugs.python.org  Tue Nov  5 18:09:43 2013
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Tue, 05 Nov 2013 17:09:43 +0000
Subject: [docs] [issue19504] Change "customise" to "customize".
In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za>
Message-ID: <1383671383.55.0.00662939347319.issue19504@psf.upfronthosting.co.za>


Fred L. Drake, Jr. added the comment:

Not a foolish consistency; Guido ruled long ago that American spellings should be used.

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

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

From report at bugs.python.org  Tue Nov  5 23:52:08 2013
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 05 Nov 2013 22:52:08 +0000
Subject: [docs] [issue19508] Add warning that Python doesn't verify SSL
	certs by	default
Message-ID: <1383691927.99.0.022250098505.issue19508@psf.upfronthosting.co.za>


New submission from Christian Heimes:

Developers are still surprised that Python's ssl library doesn't validate SSL certs by default. We should add a *big* warning to the SSL module as well as to all consumers (http, ftp, imap, pop, smtp, nntp ...) that neither the CA cert chain nor the hostname are validated by default. (AFAIK only http.client does match_hostname()).

----------
assignee: docs at python
components: Documentation
messages: 202245
nosy: christian.heimes, docs at python, giampaolo.rodola, janssen, pitrou
priority: high
severity: normal
stage: needs patch
status: open
title: Add warning that Python doesn't verify SSL certs by default
type: enhancement
versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Wed Nov  6 01:44:59 2013
From: report at bugs.python.org (Chris Cooper)
Date: Wed, 06 Nov 2013 00:44:59 +0000
Subject: [docs] [issue18840] Tutorial recommends pickle module without any
	warning of	insecurity
In-Reply-To: <1377520678.97.0.369666733509.issue18840@psf.upfronthosting.co.za>
Message-ID: <1383698699.58.0.488507550786.issue18840@psf.upfronthosting.co.za>


Chris Cooper added the comment:

Here's a patch that focuses on the json module, with a smaller pickle section including the warning from the pickle docs.

----------
nosy: +ChrisCooper
Added file: http://bugs.python.org/file32513/issue18840

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

From report at bugs.python.org  Wed Nov  6 09:54:56 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 06 Nov 2013 08:54:56 +0000
Subject: [docs] [issue19508] Add warning that Python doesn't verify SSL
	certs by	default
In-Reply-To: <1383691927.99.0.022250098505.issue19508@psf.upfronthosting.co.za>
Message-ID: <1383728096.32.0.681470653398.issue19508@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

There is already an entire section about this:
http://docs.python.org/dev/library/ssl.html#security-considerations

It's up to consumers of the API to choose their security policy, the ssl module merely provides building blocks to implement it. I think the ssl docs are sufficiently explicit about it right now, we're not going to add warnings every time we think something is important to read.

As for "developers [who] are still surprised", well, most of them shouldn't use the ssl module directly.

----------

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

From report at bugs.python.org  Wed Nov  6 10:29:15 2013
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 06 Nov 2013 09:29:15 +0000
Subject: [docs] [issue19508] Add warning that Python doesn't verify SSL
	certs by	default
In-Reply-To: <1383691927.99.0.022250098505.issue19508@psf.upfronthosting.co.za>
Message-ID: <1383730155.36.0.854902089148.issue19508@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> There is already an entire section about this:
> http://docs.python.org/dev/library/ssl.html#security-considerations

So we just need to add a link from http, ftp, imap, ... to this section?

Using only http://docs.python.org/dev/library/ftplib.html#ftp-tls-objects documentation, I don't see how to plug my own SSL validation code. I don't see any SSL context object or things like that.

----------
nosy: +haypo

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

From report at bugs.python.org  Wed Nov  6 20:16:20 2013
From: report at bugs.python.org (A.M. Kuchling)
Date: Wed, 06 Nov 2013 19:16:20 +0000
Subject: [docs] [issue3849] FUD in documentation for urllib.urlopen()
In-Reply-To: <1221246343.23.0.128587140594.issue3849@psf.upfronthosting.co.za>
Message-ID: <1383765380.65.0.0331794782927.issue3849@psf.upfronthosting.co.za>


Changes by A.M. Kuchling <lists at amk.ca>:


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

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

From report at bugs.python.org  Wed Nov  6 21:36:15 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 06 Nov 2013 20:36:15 +0000
Subject: [docs] [issue19441] itertools.tee improve documentation
In-Reply-To: <1383087333.66.0.191656186181.issue19441@psf.upfronthosting.co.za>
Message-ID: <1383770175.2.0.144446553169.issue19441@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

I don't want to recommend overwriting the variable name but will add a note for the rest:

"Copied iterators depend the original iterator. If the original advances, then so do the copies.  After teeing the iterators, the usual practice is
to stop working with the original iterator and operate only on the new tee-ed iterators."

FWIW, the situation is analogous to str.upper().  We note that string methods produce new strings.  We don't state that a best practice is to overwrite the variable with "s = s.upper()".  That is sometimes what you want and sometimes not.

----------
priority: normal -> low

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

From report at bugs.python.org  Wed Nov  6 22:20:53 2013
From: report at bugs.python.org (A.M. Kuchling)
Date: Wed, 06 Nov 2013 21:20:53 +0000
Subject: [docs] [issue7061] Improve turtle module documentation
In-Reply-To: <1254717274.49.0.570691979968.issue7061@psf.upfronthosting.co.za>
Message-ID: <1383772853.18.0.73515312839.issue7061@psf.upfronthosting.co.za>


A.M. Kuchling added the comment:

Is there anything left to do for this issue?

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

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

From report at bugs.python.org  Thu Nov  7 10:42:50 2013
From: report at bugs.python.org (Yury V. Zaytsev)
Date: Thu, 07 Nov 2013 09:42:50 +0000
Subject: [docs] [issue19517] sysconfig variables introduced by PEP-3149 are
	currently	undocumented
Message-ID: <1383817370.06.0.832101604134.issue19517@psf.upfronthosting.co.za>


New submission from Yury V. Zaytsev:

PEP-3149 (issue9193) introduces new variables (SO and SOABI) so that one can find out what are the supported extension suffixes.

Quote from the PEP:

>>> sysconfig.get_config_var('SO')
'.cpython-32mu.so'
>>> sysconfig.get_config_var('SOABI')
'cpython-32mu'

Later, in issue16754, doko introduced EXT_SUFFIX & SHLIB_SUFFIX and planned to update the PEP, but this didn't happen. This caused discrepancy in the news (issue11234), and the news item was fixed:

http://docs.python.org/3.4/whatsnew/3.2.html?highlight=soabi

>>> sysconfig.get_config_var('SOABI')       # find the version tag
'cpython-32mu'
>>> sysconfig.get_config_var('EXT_SUFFIX')  # find the full filename extension
'.cpython-32mu.so'

However, the PEP is still not up-to-date and is in conflict with the implementation.

In an IRC discussion with Barry he suggested that PEPs shouldn't be considered documentation, so updating the PEP is not the right way to go.

My proposal is then to document the intent behind SO, SOABI, EXT_SUFFIX & SHLIB_SUFFIX on the sysconfig documentation page and mention that they are platform-specific, and maybe add a link to this page to the PEP.

As of now, I find the situation highly confusing... Any opinions or suggestions please?

Thanks,

Z.

----------
assignee: docs at python
components: Documentation
messages: 202321
nosy: barry, docs at python, doko, zaytsev
priority: normal
severity: normal
status: open
title: sysconfig variables introduced by PEP-3149 are currently undocumented
type: enhancement
versions: Python 3.3

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

From report at bugs.python.org  Thu Nov  7 16:53:52 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 07 Nov 2013 15:53:52 +0000
Subject: [docs] [issue18985] Improve the documentation in fcntl module
In-Reply-To: <1378722919.93.0.901392318122.issue18985@psf.upfronthosting.co.za>
Message-ID: <3dFq0c0cp1zR3q@mail.python.org>


Roundup Robot added the comment:

New changeset 0e0dded5d616 by R David Murray in branch '3.3':
#18985: Improve fcntl documentation.
http://hg.python.org/cpython/rev/0e0dded5d616

New changeset ddf6da99b3cd by R David Murray in branch 'default':
Merge #18985: Improve fcntl documentation.
http://hg.python.org/cpython/rev/ddf6da99b3cd

New changeset 645aa4f44aa4 by R David Murray in branch '2.7':
backport #18985: Improve fcntl documentation.
http://hg.python.org/cpython/rev/645aa4f44aa4

----------
nosy: +python-dev

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

From report at bugs.python.org  Thu Nov  7 16:54:48 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 07 Nov 2013 15:54:48 +0000
Subject: [docs] [issue18985] Improve the documentation in fcntl module
In-Reply-To: <1378722919.93.0.901392318122.issue18985@psf.upfronthosting.co.za>
Message-ID: <1383839688.0.0.825605417713.issue18985@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks, Vajrasky (and Victor :)

----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Thu Nov  7 22:34:52 2013
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 07 Nov 2013 21:34:52 +0000
Subject: [docs] [issue19431] Document PyFrame_FastToLocals()
	and	PyFrame_FastToLocalsWithError()
In-Reply-To: <1383040535.91.0.284405039579.issue19431@psf.upfronthosting.co.za>
Message-ID: <1383860092.84.0.123752717059.issue19431@psf.upfronthosting.co.za>


STINNER Victor added the comment:

c_api_frame.patch: document some C functions of the frame object in the C API.

----------
keywords: +patch
Added file: http://bugs.python.org/file32537/c_api_frame.patch

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

From report at bugs.python.org  Sat Nov  9 11:29:06 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Sat, 09 Nov 2013 10:29:06 +0000
Subject: [docs] [issue19504] Change "customise" to "customize".
In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za>
Message-ID: <1383992946.47.0.827443873569.issue19504@psf.upfronthosting.co.za>


Changes by Tshepang Lekhonkhobe <tshepang at gmail.com>:


----------
nosy: +tshepang

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

From report at bugs.python.org  Sun Nov 10 05:21:33 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Sun, 10 Nov 2013 04:21:33 +0000
Subject: [docs] [issue19540] PEP339: Fix link to Zephyr ASDL paper
Message-ID: <1384057293.34.0.202657112056.issue19540@psf.upfronthosting.co.za>


Changes by anatoly techtonik <techtonik at gmail.com>:


----------
assignee: docs at python
components: Documentation
hgrepos: 213
nosy: docs at python, techtonik
priority: normal
severity: normal
status: open
title: PEP339: Fix link to Zephyr ASDL paper

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

From report at bugs.python.org  Sun Nov 10 06:16:58 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Sun, 10 Nov 2013 05:16:58 +0000
Subject: [docs] [issue19541] ast.dump(indent=True) prettyprinting
Message-ID: <1384060618.33.0.960245227555.issue19541@psf.upfronthosting.co.za>


New submission from anatoly techtonik:

ast.dump needs an indent argument for pretty printing.

  from pprint import pprint as pp
  pp(ast.dump(node))

  "Assign(targets=[Tuple(elts=[Name(id='d', ctx=Store()), Name(id='m', ctx=Store())], ctx=Store())], value=Call(func=Name(id='divmod', ctx=Load()), args=[Call(func=Name(id='len', ctx=Load()), args=[Name(id='seq', ctx=Load())], keywords=[], starargs=None, kwargs=None), Name(id='size', ctx=Load())], keywords=[], starargs=None, kwargs=None))"

----------
assignee: docs at python
components: Documentation
messages: 202506
nosy: docs at python, techtonik
priority: normal
severity: normal
status: open
title: ast.dump(indent=True) prettyprinting

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

From report at bugs.python.org  Sun Nov 10 21:00:32 2013
From: report at bugs.python.org (Benjamin Peterson)
Date: Sun, 10 Nov 2013 20:00:32 +0000
Subject: [docs] [issue19540] PEP339: Fix link to Zephyr ASDL paper
Message-ID: <1384113632.77.0.778275071687.issue19540@psf.upfronthosting.co.za>


New submission from Benjamin Peterson:

c0d120cf0aac

----------
nosy: +benjamin.peterson
resolution:  -> fixed
status: open -> closed

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

From report at bugs.python.org  Mon Nov 11 01:22:07 2013
From: report at bugs.python.org (Jan Kaliszewski)
Date: Mon, 11 Nov 2013 00:22:07 +0000
Subject: [docs] [issue19539] The 'raw_unicode_escape' codec buggy + not
	apropriate	for Python 3.x
In-Reply-To: <1384051905.56.0.969775270474.issue19539@psf.upfronthosting.co.za>
Message-ID: <1384129327.95.0.829693890955.issue19539@psf.upfronthosting.co.za>


Jan Kaliszewski added the comment:

Which means that the description "Produce a string that is suitable as raw Unicode literal in Python source code" is (in Python 3.x) no longer true.

So, if change/removal is not possible because of internal significance of the codec, I believe that the description should be changed to something like: "For internal use. This codec *does not* produce anything suitable as a raw string literal in Python 3.x source code."

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
versions: +Python 3.2, Python 3.3

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

From report at bugs.python.org  Mon Nov 11 02:29:13 2013
From: report at bugs.python.org (Jan Kaliszewski)
Date: Mon, 11 Nov 2013 01:29:13 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
Message-ID: <1384133353.82.0.173341188397.issue19548@psf.upfronthosting.co.za>


New submission from Jan Kaliszewski:

When learning about the 'codecs' module I encountered several places in the docs of the module that, I believe, could be improved to be clearer and easier for codecs-begginers: 

1. Ad `codecs.encode` and `codecs.decode` descriptions: I believe it would be worth to mention that, unlike str.encode()/bytes.decode(), these functions (and all their counterparts in the classes the module contains) support not only "traditional str/bytes encodings", but also bytes-to-bytes as well as str-to-str encodings. 

2. Ad 'codecs.register': in two places there is such a text: `These have to be factory functions providing the following interface: factory([...] errors='strict')` -- `errors='strict'` may be confusing (at the first sight it may suggest that the only valid value is 'strict'; maybe `factory(errors=<error handler label>)` with an appropriate description below would be better?).

3. Ad `codecs.open`: I believe there should be a reference to the built-in open() as an alternative that is better is most cases.

4. Ad `codecs.BOM*`: `These constants define various encodings of the Unicode byte order mark (BOM).` -- the world `encodings` seems to be confusing here; maybe `These constants define various byte sequences being Unicode byte order marks (BOMs) for several encodings. They are used...` would be better?

5. Ad `7.2.1. Codec Base Classes` + `codecs.IncrementalEncoder`/`codecs/IncrementalDecoder`:
  * `Each codec has to define four interfaces to make it usable as codec in Python: stateless encoder, stateless decoder, stream reader and stream writer` -- only four? Not six? What about incremental encoder/decoder???
  * Comparing the fragments (and tables) about error halding methods (Codecs Base Classes, IncrementalEncoder, IncrementalDecoder) with similar fragment in the `codecs.register` description and with the `codecs.register_error` description I was confused: is it the matter of a particular codec implementation or of a registered error handler to implement a particular way of error handling? I believe it would be worth to describe clearly relations between these elements of the API. Also more detailed description of differences beetween error handling for encoding and decoding, and translation would be a good thing. 

6. Ad `7.2.1.6. StreamReaderWriter Objects` and `7.2.1.7. StreamRecoder Objects`: It would be worth to say explicitly that, contrary to previously described abstract classes (IncrementalEncoder/Decoder, StreamReader/Writer), these classes are *concrete* ones (if I understand it correctly).

7. Ad `7.2.4. Python Specific Encodings`:
  * `raw_unicode_encoding` -- see: ticket #19539.
  * `unicode_encoding` -- `Produce a string that is suitable as Unicode literal in Python source code` but it is *not* a string; it's a *bytes* object (which could be used in source code using an `ascii`-compatibile encoding).
  * `bytes-to-bytes` and `str-to-str` encodings -- maybe it would be nice to mention that these encodings cannot be used with str.encode()/bytes.decode() methods (and to mention again they *can* be used with the functions/method provided by the `codecs` module).

----------
assignee: docs at python
components: Documentation
messages: 202593
nosy: docs at python, zuo
priority: normal
severity: normal
status: open
title: 'codecs' module docs improvements
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Nov 11 02:31:10 2013
From: report at bugs.python.org (Jan Kaliszewski)
Date: Mon, 11 Nov 2013 01:31:10 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384133353.82.0.173341188397.issue19548@psf.upfronthosting.co.za>
Message-ID: <1384133470.83.0.485815810078.issue19548@psf.upfronthosting.co.za>


Jan Kaliszewski added the comment:

s/world/word
s/begginers/beginners

(sorry, it's late night here)

----------

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

From report at bugs.python.org  Mon Nov 11 02:56:00 2013
From: report at bugs.python.org (Jan Kaliszewski)
Date: Mon, 11 Nov 2013 01:56:00 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384133353.82.0.173341188397.issue19548@psf.upfronthosting.co.za>
Message-ID: <1384134960.27.0.809048925872.issue19548@psf.upfronthosting.co.za>


Jan Kaliszewski added the comment:

8. Again ad `codecs.open`: the default file mode is actually 'rb', not 'r'.

9. Several places in the docs -- ad: `codecs.register_error`, `codecs.open`, `codecs.EncodedFile`, `Codec.encode/decode`, `codecs.StreamWriter/StreamReader` -- do not cover cases of using bytes-to-bytes and/or str-to-str encodings (especially when using `string`/`bytes` and `text`/`binary` terms).

10. `codecs.replace_errors` -- `bytestring` should be replaced with `bytes-like object` (as in other places).

----------

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

From report at bugs.python.org  Mon Nov 11 03:14:06 2013
From: report at bugs.python.org (Jan Kaliszewski)
Date: Mon, 11 Nov 2013 02:14:06 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384133353.82.0.173341188397.issue19548@psf.upfronthosting.co.za>
Message-ID: <1384136046.19.0.973892175061.issue19548@psf.upfronthosting.co.za>


Jan Kaliszewski added the comment:

11. Ad encoding 'undefined': The sentence `Can be used as the system encoding if no automatic coercion between byte and Unicode strings is desired.` was suitable for Python 2.x, but not for Python 3.x'. I believe, this sentence should be removed.

----------

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

From report at bugs.python.org  Mon Nov 11 03:15:10 2013
From: report at bugs.python.org (Jan Kaliszewski)
Date: Mon, 11 Nov 2013 02:15:10 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384133353.82.0.173341188397.issue19548@psf.upfronthosting.co.za>
Message-ID: <1384136110.79.0.682378276858.issue19548@psf.upfronthosting.co.za>


Changes by Jan Kaliszewski <zuo at chopin.edu.pl>:


----------
versions:  -Python 2.6, Python 2.7, Python 3.1

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

From report at bugs.python.org  Mon Nov 11 05:51:59 2013
From: report at bugs.python.org (Ned Deily)
Date: Mon, 11 Nov 2013 04:51:59 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384133353.82.0.173341188397.issue19548@psf.upfronthosting.co.za>
Message-ID: <1384145519.16.0.976214630769.issue19548@psf.upfronthosting.co.za>


Changes by Ned Deily <nad at acm.org>:


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

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

From report at bugs.python.org  Mon Nov 11 06:27:27 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 11 Nov 2013 05:27:27 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384145519.16.0.976214630769.issue19548@psf.upfronthosting.co.za>
Message-ID: <CADiSq7fxCOKky=4+AM4PsAUwjyF5wwCdfdLAvXdKUd6J2XRF6w@mail.gmail.com>


Nick Coghlan added the comment:

A few more:

- codec name normalisation (lower case,  space to hyphen) is not mentioned
in the codecs.register description

- search function registration is not reversible, which doesn't play well
with module reloading

- codecs.CodecInfo init signature is not covered

----------

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

From report at bugs.python.org  Mon Nov 11 06:51:38 2013
From: report at bugs.python.org (David Chambers)
Date: Mon, 11 Nov 2013 05:51:38 +0000
Subject: [docs] [issue19238] Misleading explanation of fill and align in
	format_spec
In-Reply-To: <1381616869.75.0.196962613989.issue19238@psf.upfronthosting.co.za>
Message-ID: <1384149098.67.0.19160505617.issue19238@psf.upfronthosting.co.za>


David Chambers added the comment:

These commits contain a typo: s/preceeded/preceded/

----------

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

From report at bugs.python.org  Mon Nov 11 15:20:30 2013
From: report at bugs.python.org (Alan Cristhian)
Date: Mon, 11 Nov 2013 14:20:30 +0000
Subject: [docs] [issue19441] itertools.tee improve documentation
In-Reply-To: <1383087333.66.0.191656186181.issue19441@psf.upfronthosting.co.za>
Message-ID: <1384179630.34.0.676665216504.issue19441@psf.upfronthosting.co.za>


Alan Cristhian added the comment:

Ok, I agree.

----------

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

From report at bugs.python.org  Mon Nov 11 19:23:39 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 11 Nov 2013 18:23:39 +0000
Subject: [docs] [issue19539] The 'raw_unicode_escape' codec buggy + not
	apropriate	for Python 3.x
In-Reply-To: <1384051905.56.0.969775270474.issue19539@psf.upfronthosting.co.za>
Message-ID: <1384194219.8.0.426563924694.issue19539@psf.upfronthosting.co.za>


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


----------
components:  -Library (Lib)
nosy:  -serhiy.storchaka
stage:  -> needs patch
type:  -> enhancement
versions:  -Python 3.2, Python 3.5

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

From report at bugs.python.org  Mon Nov 11 20:19:23 2013
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Mon, 11 Nov 2013 19:19:23 +0000
Subject: [docs] [issue19539] The 'raw_unicode_escape' codec buggy + not
	appropriate	for Python 3.x
In-Reply-To: <1384051905.56.0.969775270474.issue19539@psf.upfronthosting.co.za>
Message-ID: <1384197563.26.0.45577927483.issue19539@psf.upfronthosting.co.za>


Marc-Andre Lemburg added the comment:

Jan, the codec implements an encoding which has certain characteristics just like any other codec. It works both in Python 2 and 3 without problems.

The documentation is no longer true, though. Ever since we added encoding markers to source files, the raw Unicode string literals depended on this encoding setting. Before this change the docs were fine, since Unicode literals were interpreted as Latin-1 encoded.

More correct would be: "Produce a string that uses Unicode escapes to encode non-Latin-1 code points. It is used in the Python pickle protocol."

----------
nosy: +lemburg
title: The 'raw_unicode_escape' codec buggy + not apropriate for Python 3.x -> The 'raw_unicode_escape' codec buggy + not appropriate for Python 3.x

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

From report at bugs.python.org  Mon Nov 11 21:32:30 2013
From: report at bugs.python.org (A.M. Kuchling)
Date: Mon, 11 Nov 2013 20:32:30 +0000
Subject: [docs] [issue16776] Document PyCFunction_New and PyCFunction_NewEx
	functions
In-Reply-To: <1356434154.16.0.0981038830976.issue16776@psf.upfronthosting.co.za>
Message-ID: <1384201950.9.0.869921985351.issue16776@psf.upfronthosting.co.za>


A.M. Kuchling added the comment:

Here's a patch that contains text for a description of these two functions.  However, I can't figure out what section they would belong in.  They don't really belong in http://docs.python.org/3.4/c-api/structures.html, which is for the C structures.

Also note that PyCFunctionObject isn't described anywhere.  Should it be?

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

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

From report at bugs.python.org  Mon Nov 11 21:32:48 2013
From: report at bugs.python.org (A.M. Kuchling)
Date: Mon, 11 Nov 2013 20:32:48 +0000
Subject: [docs] [issue16776] Document PyCFunction_New and PyCFunction_NewEx
	functions
In-Reply-To: <1356434154.16.0.0981038830976.issue16776@psf.upfronthosting.co.za>
Message-ID: <1384201968.1.0.0108285315616.issue16776@psf.upfronthosting.co.za>


A.M. Kuchling added the comment:

Mis-clicked and forgot to attach the patch.

----------
Added file: http://bugs.python.org/file32578/16776.txt

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

From report at bugs.python.org  Tue Nov 12 05:20:57 2013
From: report at bugs.python.org (Zachary Ware)
Date: Tue, 12 Nov 2013 04:20:57 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1384230057.21.0.482340091722.issue18326@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Any further thoughts on this?  I think my vote is for v3, except s/must/can only/.  "must" makes it sound like you are forced to pass those arguments.

----------

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

From report at bugs.python.org  Tue Nov 12 07:52:24 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Tue, 12 Nov 2013 06:52:24 +0000
Subject: [docs] [issue19557] ast - docs for every node type are missing
Message-ID: <1384239144.67.0.857427270426.issue19557@psf.upfronthosting.co.za>


New submission from anatoly techtonik:

http://docs.python.org/2/library/ast.html

AST module doc is incomplete. To write node visitor, you need to know possible types of parameters and expected values for every node type. They are different.

http://hg.python.org/cpython/file/1ee45eb6aab9/Parser/Python.asdl

For example, visit_Assign expects:
 Assign(targets, value)
   `targets` can be List, Tuple or Name

When there is List, and when there is Tuple? It should be documented.

----------
assignee: docs at python
components: Devguide, Documentation
messages: 202675
nosy: docs at python, ezio.melotti, techtonik
priority: normal
severity: normal
status: open
title: ast - docs for every node type are missing

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

From report at bugs.python.org  Tue Nov 12 14:33:52 2013
From: report at bugs.python.org (Tom Lynn)
Date: Tue, 12 Nov 2013 13:33:52 +0000
Subject: [docs] [issue19560] PEP 8 operator precedence across parens
Message-ID: <1384263232.23.0.922688589796.issue19560@psf.upfronthosting.co.za>


New submission from Tom Lynn:

PEP 8 currently has::

  Yes::

      ...
      c = (a+b) * (a-b)

  No::

      ...
      c = (a + b) * (a - b)

That looks wrong to me -- surely the parens are a sufficient
precedence hint, and don't need further squashing inside?
This will be worse with any non-trivial example.  I suspect
it may also lead to silly complications in code formatting tools.

This was changed by Guido as part of a reversion in issue 16239,
but I wonder whether that example was intended to be included?

----------
assignee: docs at python
components: Documentation
messages: 202687
nosy: docs at python, tlynn
priority: normal
severity: normal
status: open
title: PEP 8 operator precedence across parens
type: enhancement

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

From report at bugs.python.org  Tue Nov 12 14:55:24 2013
From: report at bugs.python.org (Tom Lynn)
Date: Tue, 12 Nov 2013 13:55:24 +0000
Subject: [docs] [issue19560] PEP 8 operator precedence across parens
In-Reply-To: <1384263232.23.0.922688589796.issue19560@psf.upfronthosting.co.za>
Message-ID: <1384264524.56.0.301176530071.issue19560@psf.upfronthosting.co.za>


Tom Lynn added the comment:

FWIW, this pair of examples differs from the others in this section
as they were both explicitly okayed in the first version of PEP 8
<http://hg.python.org/peps/rev/4c31c25bdc03?revcount=120>::

    - Use your better judgment for the insertion of spaces around
      arithmetic operators.  Always be consistent about whitespace on
      either side of a binary operator.  Some examples:

          i = i+1
          submitted = submitted + 1
          x = x*2 - 1
          hypot2 = x*x + y*y
          c = (a+b) * (a-b)
          c = (a + b) * (a - b)

My guess is that this is still the intention?

----------

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

From report at bugs.python.org  Tue Nov 12 15:12:48 2013
From: report at bugs.python.org (Barry A. Warsaw)
Date: Tue, 12 Nov 2013 14:12:48 +0000
Subject: [docs] [issue19560] PEP 8 operator precedence across parens
In-Reply-To: <1384263232.23.0.922688589796.issue19560@psf.upfronthosting.co.za>
Message-ID: <1384265568.16.0.0197457087009.issue19560@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Nov 12 15:41:00 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 12 Nov 2013 14:41:00 +0000
Subject: [docs] [issue19560] PEP 8 operator precedence across parens
In-Reply-To: <1384263232.23.0.922688589796.issue19560@psf.upfronthosting.co.za>
Message-ID: <1384267260.92.0.57998311048.issue19560@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

See msg173785.

The example in the "no" section is not "wrong" -- it's just worse than the one in the "yes" section because it provides less hints about the groups and it's less readable, so it has no reason to be used.

If you note the introductory paragraph it says "Use your better judgment for the insertion of spaces around arithmetic operators.".  This means that even if the general rule is to add spaces around the operators, in some situations it is better to omit them, and one should decide on a case by case basis.

To provide a further example, see:
  a = 2 * (b+c)
and 
  a = 2*(b+c) - 2/(d+e)

The first part -- 2*(b+c) -- is the same in both the examples, but the spaces change depending on the context.  In the first case you can emphasize the multiplication between 2 and b+c, whereas in the second case there are two "groups" that get subtracted, so the spaces around the * and / can be removed to emphasize these two bigger groups.

I think that section is OK, and doesn't need to be changed.

----------
assignee: docs at python -> gvanrossum
nosy: +ezio.melotti, gvanrossum
status: open -> pending

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

From report at bugs.python.org  Tue Nov 12 16:25:23 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 12 Nov 2013 15:25:23 +0000
Subject: [docs] [issue12828] xml.dom.minicompat is not documented
In-Reply-To: <1314121617.5.0.895410943337.issue12828@psf.upfronthosting.co.za>
Message-ID: <3dJt7Q0D39z7LtM@mail.python.org>


Roundup Robot added the comment:

New changeset 3710514aa92a by Andrew Kuchling in branch '3.3':
Closes #12828: add docstring text noting this is an internal-only module
http://hg.python.org/cpython/rev/3710514aa92a

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Tue Nov 12 16:43:02 2013
From: report at bugs.python.org (Brett Cannon)
Date: Tue, 12 Nov 2013 15:43:02 +0000
Subject: [docs] [issue19557] ast - docs for every node type are missing
In-Reply-To: <1384239144.67.0.857427270426.issue19557@psf.upfronthosting.co.za>
Message-ID: <1384270982.14.0.652851108161.issue19557@psf.upfronthosting.co.za>


Brett Cannon added the comment:

The node types are all listed right there in the docs in the abstract grammar section, so arguing they are incomplete I don't think is accurate.

I'm willing to leave this open in case some ambitious person wants to write docs for every node type, but I think this is a very low priority task.

----------
nosy: +brett.cannon
priority: normal -> low

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

From report at bugs.python.org  Tue Nov 12 17:08:23 2013
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 12 Nov 2013 16:08:23 +0000
Subject: [docs] [issue19560] PEP 8 operator precedence across parens
In-Reply-To: <1384263232.23.0.922688589796.issue19560@psf.upfronthosting.co.za>
Message-ID: <1384272503.26.0.601351544016.issue19560@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Style is a matter of taste, not of correctness.  It is pointless to debate the finer points in a bug report.

----------
resolution:  -> invalid
status: pending -> closed

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

From report at bugs.python.org  Tue Nov 12 17:10:21 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 12 Nov 2013 16:10:21 +0000
Subject: [docs] [issue19560] PEP 8 operator precedence across parens
In-Reply-To: <1384263232.23.0.922688589796.issue19560@psf.upfronthosting.co.za>
Message-ID: <1384272621.87.0.417749709179.issue19560@psf.upfronthosting.co.za>


Changes by Ezio Melotti <ezio.melotti at gmail.com>:


----------
stage:  -> committed/rejected

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

From report at bugs.python.org  Tue Nov 12 21:12:46 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 12 Nov 2013 20:12:46 +0000
Subject: [docs] [issue19290] Clarify compile and eval interaction.
In-Reply-To: <1382135132.91.0.187309157375.issue19290@psf.upfronthosting.co.za>
Message-ID: <1384287166.11.0.409240144027.issue19290@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I find your suggestion difficult to read.  Maybe using a list would make it more understandable?

----------
nosy: +ezio.melotti
type:  -> enhancement

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

From report at bugs.python.org  Tue Nov 12 22:53:07 2013
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 12 Nov 2013 21:53:07 +0000
Subject: [docs] [issue16776] Document PyCFunction_New and PyCFunction_NewEx
	functions
In-Reply-To: <1356434154.16.0.0981038830976.issue16776@psf.upfronthosting.co.za>
Message-ID: <1384293187.56.0.609044110801.issue16776@psf.upfronthosting.co.za>


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


----------
nosy: +haypo

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

From report at bugs.python.org  Wed Nov 13 20:33:43 2013
From: report at bugs.python.org (Antony Lee)
Date: Wed, 13 Nov 2013 19:33:43 +0000
Subject: [docs] [issue19573] Fix the docstring of inspect.Parameter and
	the	implementation of _ParameterKind
Message-ID: <1384371223.06.0.467962768293.issue19573@psf.upfronthosting.co.za>


New submission from Antony Lee:

The following patch corrects the docstring of `inspect.Parameter`, as the `default` and `annotation` attributes are in fact set to `empty` if no value is provided, and the `kind` attribute is in fact an `int` (more precisely, a `_ParameterKind`).  It also reimplements the `_ParameterKind` type as an `IntEnum`, as the previous implementation (which predates stdlib enums) was more or less a hand-rolled `IntEnum`.

----------
assignee: docs at python
components: Documentation
files: inspect.py.diff
keywords: patch
messages: 202773
nosy: Antony.Lee, docs at python
priority: normal
severity: normal
status: open
title: Fix the docstring of inspect.Parameter and the implementation of _ParameterKind
type: enhancement
Added file: http://bugs.python.org/file32600/inspect.py.diff

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

From report at bugs.python.org  Wed Nov 13 22:49:30 2013
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 13 Nov 2013 21:49:30 +0000
Subject: [docs] [issue19576] "Non-Python created threads" documentation
	doesn't	mention PyEval_InitThreads()
Message-ID: <1384379370.85.0.232061958171.issue19576@psf.upfronthosting.co.za>


New submission from STINNER Victor:

While working on a unit test for the issue #14432, I hit a bug. My C thread got the GIL with PyGILState_Ensure(), but it was strange because the main Python thread also had the GIL...

Then I saw that gil_created() returned false. The solution is to call PyEval_InitThreads() to create the GIL.

I was reading "Non-Python created threads" documentation, but this section doesn't mention PyEval_InitThreads().

I don't know if it's something new in Python 3.2 with the new GIL.

----------
assignee: docs at python
components: Documentation
messages: 202787
nosy: christian.heimes, docs at python, haypo, pitrou
priority: normal
severity: normal
status: open
title: "Non-Python created threads" documentation doesn't mention PyEval_InitThreads()
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Thu Nov 14 02:39:23 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 14 Nov 2013 01:39:23 +0000
Subject: [docs] [issue19576] "Non-Python created threads" documentation
	doesn't	mention PyEval_InitThreads()
In-Reply-To: <1384379370.85.0.232061958171.issue19576@psf.upfronthosting.co.za>
Message-ID: <1384393163.52.0.647639353021.issue19576@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Perhaps we can fix PyGILState to call PyEval_InitThreads automatically?

----------

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

From report at bugs.python.org  Thu Nov 14 09:28:02 2013
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 14 Nov 2013 08:28:02 +0000
Subject: [docs] [issue19576] "Non-Python created threads" documentation
	doesn't	mention PyEval_InitThreads()
In-Reply-To: <1384379370.85.0.232061958171.issue19576@psf.upfronthosting.co.za>
Message-ID: <1384417682.25.0.829972568274.issue19576@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> Perhaps we can fix PyGILState to call PyEval_InitThreads automatically?

Yes, I had the same idea. Here is a patch to call PyEval_InitThreads() in PyGILState_Ensure() for new threads.

----------
keywords: +patch
Added file: http://bugs.python.org/file32609/PyGILState_Ensure.patch

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

From report at bugs.python.org  Thu Nov 14 19:35:17 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 14 Nov 2013 18:35:17 +0000
Subject: [docs] [issue19540] PEP339: Fix link to Zephyr ASDL paper
In-Reply-To: <1384113632.77.0.778275071687.issue19540@psf.upfronthosting.co.za>
Message-ID: <1384454117.17.0.194635191099.issue19540@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

It conflicts. =(

https://bitbucket.org/rirror/peps/pull-request/1/pep-0339txt-fix-link-to-zephyr-asdl-paper/diff

----------

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

From report at bugs.python.org  Fri Nov 15 21:59:01 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 15 Nov 2013 20:59:01 +0000
Subject: [docs] [issue19504] Change "customise" to "customize".
In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za>
Message-ID: <3dLsP05xqsz7Ljb@mail.python.org>


Roundup Robot added the comment:

New changeset e9d9bebb979f by Vinay Sajip in branch '2.7':
Issue #19504: Used American spelling for 'customize'.
http://hg.python.org/cpython/rev/e9d9bebb979f

New changeset 1c714c35c02a by Vinay Sajip in branch '3.3':
Issue #19504: Used American spelling for 'customize'.
http://hg.python.org/cpython/rev/1c714c35c02a

New changeset 08c7bc4266e6 by Vinay Sajip in branch 'default':
Issue #19504: Used American spelling for 'customize'.
http://hg.python.org/cpython/rev/08c7bc4266e6

----------
nosy: +python-dev

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

From report at bugs.python.org  Sat Nov 16 01:42:02 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 16 Nov 2013 00:42:02 +0000
Subject: [docs] [issue19539] The 'raw_unicode_escape' codec buggy + not
	appropriate	for Python 3.x
In-Reply-To: <1384051905.56.0.969775270474.issue19539@psf.upfronthosting.co.za>
Message-ID: <1384562522.6.0.735074135407.issue19539@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Nov 16 01:44:05 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 16 Nov 2013 00:44:05 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384133353.82.0.173341188397.issue19548@psf.upfronthosting.co.za>
Message-ID: <1384562645.94.0.165918062089.issue19548@psf.upfronthosting.co.za>


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


----------
versions:  -Python 3.2

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

From report at bugs.python.org  Sat Nov 16 01:46:26 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 16 Nov 2013 00:46:26 +0000
Subject: [docs] [issue19557] ast - docs for every node type are missing
In-Reply-To: <1384239144.67.0.857427270426.issue19557@psf.upfronthosting.co.za>
Message-ID: <1384562786.39.0.755521435466.issue19557@psf.upfronthosting.co.za>


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


----------
components:  -Devguide

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

From report at bugs.python.org  Sat Nov 16 03:31:52 2013
From: report at bugs.python.org (Christopher Welborn)
Date: Sat, 16 Nov 2013 02:31:52 +0000
Subject: [docs] [issue19620] tokenize documentation contains typos (argment
	instead	of argument)
Message-ID: <1384569112.62.0.796047767365.issue19620@psf.upfronthosting.co.za>


New submission from Christopher Welborn:

Documentation for tokenize contains typos, functions detect_encoding() and tokenize() at least. The lines are:

The tokenize() generator requires one argment, readline,...

It requires one argment, readline,

...where argment is supposed to be 'argument' i'm sure. Things like that bug me in my own code/docs, and since it's been there since 2.7 (Also in 3.3 and 3.4), I figured no one had noticed.

----------
assignee: docs at python
components: Documentation
messages: 203005
nosy: cjwelborn, docs at python
priority: normal
severity: normal
status: open
title: tokenize documentation contains typos (argment instead of argument)
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Nov 16 03:33:58 2013
From: report at bugs.python.org (Christopher Welborn)
Date: Sat, 16 Nov 2013 02:33:58 +0000
Subject: [docs] [issue19620] tokenize documentation contains typos (argment
	instead	of argument)
In-Reply-To: <1384569112.62.0.796047767365.issue19620@psf.upfronthosting.co.za>
Message-ID: <1384569238.69.0.637056088418.issue19620@psf.upfronthosting.co.za>


Christopher Welborn added the comment:

Oops, forgot to mention the documentation I am speaking of is the actual doc strings. The actual test is to run:
import tokenize
help(tokenize)

or just:

`python -c "import tokenize;help(tokenize)" | grep "argment"`

----------

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

From report at bugs.python.org  Sat Nov 16 06:22:14 2013
From: report at bugs.python.org (Martin Panter)
Date: Sat, 16 Nov 2013 05:22:14 +0000
Subject: [docs] [issue19622] Default buffering for input and output pipes
	in	subprocess module
Message-ID: <1384579334.66.0.612676075589.issue19622@psf.upfronthosting.co.za>


New submission from Martin Panter:

Currently the documentation for the ?bufsize? parameter in the ?subprocess? module says:

"""
Changed in version 3.2.4,: 3.3.1

bufsize now defaults to -1 to enable buffering by default to match the behavior that most code expects. In 3.2.0 through 3.2.3 and 3.3.0 it incorrectly defaulted to 0 which was unbuffered and allowed short reads. This was unintentional and did not match the behavior of Python 2 as most code expected.
"""

First of all the formatting is a bit screwy. There?s a colon in the wrong place, so it?s not obvious that the ?changed in version? heading applies to the following paragraph.

The main issue is that I got the impression the default of 0 was a regression, and that Python 3.1 and Python 2 defaulted to -1. However, as far as I can tell the default was actually 0 in 3.1 and 2.

The change to -1 was for Issue 17488, which seems to be focussed on the behaviour of reading from a subprocess?s output pipe. In Python 2, file.read() blocks to read as much as possible, even when buffering is disabled. In Python 3, you end up with either a FileIO or a BufferedIOBase object, and they have different read() behaviours.

Perhaps the documentation should say something like

"""
The ?bufsize? argument now defaults to -1 to enable buffering. In 3.2.3, 3.3.0, and earlier, it defaulted to 0 which was unbuffered and allowed short reads.
"""

I would take out the ?most code expects buffering? bits. Maybe most code expects the greedy read behaviour from output pipes, but I would say most code writing to an input pipe expects unbuffered behaviour. The big issue with buffering for me is that BufferedWriter.close() may raise a broken pipe condition.

If you want to mention Python 2, maybe say that Python 2 did not use buffering by default, but that file.read() always had blocking read behaviour, which can be emulated by using buffered reading in Python 3.

----------
assignee: docs at python
components: Documentation
messages: 203010
nosy: docs at python, vadmium
priority: normal
severity: normal
status: open
title: Default buffering for input and output pipes in subprocess module
type: behavior
versions: Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Nov 16 07:46:55 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 16 Nov 2013 06:46:55 +0000
Subject: [docs] [issue19504] Change "customise" to "customize".
In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za>
Message-ID: <1384584415.11.0.181726562577.issue19504@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Can be closed?

----------
nosy: +georg.brandl, vinay.sajip

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

From report at bugs.python.org  Sat Nov 16 13:04:26 2013
From: report at bugs.python.org (Vinay Sajip)
Date: Sat, 16 Nov 2013 12:04:26 +0000
Subject: [docs] [issue19504] Change "customise" to "customize".
In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za>
Message-ID: <1384603466.34.0.591254520714.issue19504@psf.upfronthosting.co.za>


Vinay Sajip added the comment:

> Can be closed?

Not sure - I've just updated the logging, venv and launcher code and docs.

----------

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

From report at bugs.python.org  Sat Nov 16 14:25:02 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 16 Nov 2013 13:25:02 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384133353.82.0.173341188397.issue19548@psf.upfronthosting.co.za>
Message-ID: <1384608302.39.0.349312640487.issue19548@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Another big one: the encodings module API is not documented in the prose docs, and nor is the interface between the default search function and the individual encoding definitions. There's some decent info in help(encoding) though.

The interaction with the import system could also be documented better - you can actually blacklist codecs by manipulating sys.modules and the encodings namespace, and you can search additional locations for codec modules by manipulating encodings.__path__ (even without it being declared as a namespace package)

----------

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

From report at bugs.python.org  Sat Nov 16 14:33:13 2013
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Sat, 16 Nov 2013 13:33:13 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384608302.39.0.349312640487.issue19548@psf.upfronthosting.co.za>
Message-ID: <52877416.9070908@egenix.com>


Marc-Andre Lemburg added the comment:

On 16.11.2013 14:25, Nick Coghlan wrote:
> 
> Nick Coghlan added the comment:
> 
> Another big one: the encodings module API is not documented in the prose docs, and nor is the interface between the default search function and the individual encoding definitions. There's some decent info in help(encoding) though.
> 
> The interaction with the import system could also be documented better - you can actually blacklist codecs by manipulating sys.modules and the encodings namespace, and you can search additional locations for codec modules by manipulating encodings.__path__ (even without it being declared as a namespace package)

Those were not documented on purpose, since they are an implementation
detail of the encodings package search function.

If you document them now, you'll set the implementation in stone,
making future changes to the logic difficult. I'd advise against
this to stay flexible, unless you want to open up the encodings
package as namespace package - then you'd have to add documentation
for the import interface.

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

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

From report at bugs.python.org  Sat Nov 16 15:03:59 2013
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 16 Nov 2013 14:03:59 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384133353.82.0.173341188397.issue19548@psf.upfronthosting.co.za>
Message-ID: <1384610639.68.0.328314640621.issue19548@psf.upfronthosting.co.za>


Mark Lawrence added the comment:

Could they be documented with a massive warning in red "Cpython implementation detail - subject to change without notice"?  Or documented in a place that is only accessible to developers and not users?  Or...???

----------
nosy: +BreamoreBoy

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

From report at bugs.python.org  Sat Nov 16 15:13:42 2013
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Sat, 16 Nov 2013 14:13:42 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <1384610639.68.0.328314640621.issue19548@psf.upfronthosting.co.za>
Message-ID: <52877D93.1070101@egenix.com>


Marc-Andre Lemburg added the comment:

On 16.11.2013 15:03, Mark Lawrence wrote:
> 
> Mark Lawrence added the comment:
> 
> Could they be documented with a massive warning in red "Cpython implementation detail - subject to change without notice"?  Or documented in a place that is only accessible to developers and not users?  Or...???

The API is documented in encodings/__init__.py for developers.

----------

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

From report at bugs.python.org  Sat Nov 16 15:55:12 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 16 Nov 2013 14:55:12 +0000
Subject: [docs] [issue19548] 'codecs' module docs improvements
In-Reply-To: <52877416.9070908@egenix.com>
Message-ID: <CADiSq7ftH0v0pDBn4AjawRxv78pyDAo0-Jd8N4TMXYPSDYb3=g@mail.gmail.com>


Nick Coghlan added the comment:

On 16 November 2013 23:33, Marc-Andre Lemburg <report at bugs.python.org> wrote:
> On 16.11.2013 14:25, Nick Coghlan wrote:
> Those were not documented on purpose, since they are an implementation
> detail of the encodings package search function.
>
> If you document them now, you'll set the implementation in stone,
> making future changes to the logic difficult. I'd advise against
> this to stay flexible, unless you want to open up the encodings
> package as namespace package - then you'd have to add documentation
> for the import interface.

Yes, that was what got me thinking along those lines, but to make that
possible, the contents of encodings/__init__.py would need to be moved
somewhere else. So this probably isn't on the table for 3.4.

----------

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

From report at bugs.python.org  Sat Nov 16 19:53:01 2013
From: report at bugs.python.org (Bulwersator)
Date: Sat, 16 Nov 2013 18:53:01 +0000
Subject: [docs] [issue19627] python open built-in function - "updating" is
	not defined
Message-ID: <1384627981.21.0.789966534785.issue19627@psf.upfronthosting.co.za>


New submission from Bulwersator:

see http://stackoverflow.com/questions/1466000/python-open-built-in-function-difference-between-modes-a-a-w-w-and-r - "The Python docs conveniently leave out the crucial explanation that "open the file for updating" means "opens the file for both reading and writing", which answers my question."

----------
assignee: docs at python
components: Documentation
messages: 203075
nosy: Bulwersator, docs at python
priority: normal
severity: normal
status: open
title: python open built-in function - "updating" is not defined

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

From report at bugs.python.org  Sat Nov 16 20:05:08 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 16 Nov 2013 19:05:08 +0000
Subject: [docs] [issue19573] Fix the docstring of inspect.Parameter and
	the	implementation of _ParameterKind
In-Reply-To: <1384371223.06.0.467962768293.issue19573@psf.upfronthosting.co.za>
Message-ID: <1384628708.49.0.557362891191.issue19573@psf.upfronthosting.co.za>


Changes by Ezio Melotti <ezio.melotti at gmail.com>:


----------
components: +Library (Lib)
nosy: +ethan.furman, ezio.melotti, ncoghlan
stage:  -> patch review
versions: +Python 3.4

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

From report at bugs.python.org  Sat Nov 16 23:37:55 2013
From: report at bugs.python.org (Martin Panter)
Date: Sat, 16 Nov 2013 22:37:55 +0000
Subject: [docs] [issue19627] python open built-in function - "updating" is
	not defined
In-Reply-To: <1384627981.21.0.789966534785.issue19627@psf.upfronthosting.co.za>
Message-ID: <1384641475.54.0.37024294611.issue19627@psf.upfronthosting.co.za>


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


----------
nosy: +vadmium

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

From report at bugs.python.org  Sun Nov 17 01:07:34 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 17 Nov 2013 00:07:34 +0000
Subject: [docs] [issue19362] Documentation for len() fails to mention that
	it	works	on sets
In-Reply-To: <1382530928.74.0.685857253341.issue19362@psf.upfronthosting.co.za>
Message-ID: <1384646854.5.0.890748154868.issue19362@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I think it's better to do:
-Return the number of items of a sequence or mapping.
+Return the number of items of a sequence or container.

While it's true that most sequences are clearly containers (e.g. lists), the same is not so evident for other types like bytes or strings.
I'm also starting from the assumption that people reading the docstring of len just started with Python or programming in general, so it's more important to keep it simple and understandable rather than being 100% accurate.

----------

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

From report at bugs.python.org  Sun Nov 17 01:12:52 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 17 Nov 2013 00:12:52 +0000
Subject: [docs] [issue19412] Add docs for test.support.requires_docstrings
	decorator
In-Reply-To: <1382809267.31.0.380635405032.issue19412@psf.upfronthosting.co.za>
Message-ID: <1384647172.89.0.20810223494.issue19412@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I was bitten by this in #19535. See the third point about test_contextlib in msg203071.  I would expect support.requires_docstring to skip the test if -OO is used and the docstrings are missing.

----------

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

From report at bugs.python.org  Sun Nov 17 01:23:18 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 17 Nov 2013 00:23:18 +0000
Subject: [docs] [issue19454] devguide: Document what a "platform support" is
In-Reply-To: <1383159116.46.0.184690879028.issue19454@psf.upfronthosting.co.za>
Message-ID: <1384647798.18.0.484965733211.issue19454@psf.upfronthosting.co.za>


Changes by Ezio Melotti <ezio.melotti at gmail.com>:


----------
stage:  -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Sun Nov 17 01:47:51 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 17 Nov 2013 00:47:51 +0000
Subject: [docs] [issue19238] Misleading explanation of fill and align in
	format_spec
In-Reply-To: <1381616869.75.0.196962613989.issue19238@psf.upfronthosting.co.za>
Message-ID: <3dMZQb0xvsz7Lkd@mail.python.org>


Roundup Robot added the comment:

New changeset 2b0690c9a026 by Ezio Melotti in branch '2.7':
#19238: fix typo in documentation.
http://hg.python.org/cpython/rev/2b0690c9a026

New changeset 7e3f8026ed30 by Ezio Melotti in branch '3.3':
#19238: fix typo in documentation.
http://hg.python.org/cpython/rev/7e3f8026ed30

New changeset 829b95824867 by Ezio Melotti in branch 'default':
#19238: merge with 3.3.
http://hg.python.org/cpython/rev/829b95824867

----------

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

From report at bugs.python.org  Sun Nov 17 01:48:33 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 17 Nov 2013 00:48:33 +0000
Subject: [docs] [issue19238] Misleading explanation of fill and align in
	format_spec
In-Reply-To: <1381616869.75.0.196962613989.issue19238@psf.upfronthosting.co.za>
Message-ID: <1384649313.08.0.398422161501.issue19238@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for noticing!

----------

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

From report at bugs.python.org  Sun Nov 17 01:53:48 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 17 Nov 2013 00:53:48 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1384649628.43.0.111392588786.issue18326@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I think v2 is enough, but v3 is fine with me if people think v3 it's better.

----------

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

From report at bugs.python.org  Sun Nov 17 14:35:47 2013
From: report at bugs.python.org (engelbert gruber)
Date: Sun, 17 Nov 2013 13:35:47 +0000
Subject: [docs] [issue19631] "exec" BNF in simple statements
Message-ID: <1384695347.39.0.482466517942.issue19631@psf.upfronthosting.co.za>


New submission from engelbert gruber:

the doc says::

  exec_stmt ::= "exec" or_expr ["in" expression ["," expression]]

imho it should read ::

  exec_stmt ::= "exec" expression ["in" expression ["," expression]]
                | "exec(" expression [ ", expression" [ ", expression" ]] ")"

----------
assignee: docs at python
components: Documentation
messages: 203146
nosy: docs at python, grubert
priority: normal
severity: normal
status: open
title: "exec" BNF in simple statements
versions: Python 2.6, Python 2.7

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

From report at bugs.python.org  Sun Nov 17 14:58:16 2013
From: report at bugs.python.org (Christian Heimes)
Date: Sun, 17 Nov 2013 13:58:16 +0000
Subject: [docs] [issue19438] Where is NoneType in Python 3?
In-Reply-To: <1383078691.36.0.6145513581.issue19438@psf.upfronthosting.co.za>
Message-ID: <1384696696.35.0.989183548994.issue19438@psf.upfronthosting.co.za>


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


----------
nosy:  -christian.heimes
priority: normal -> low
versions: +Python 3.4

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

From report at bugs.python.org  Sun Nov 17 15:01:35 2013
From: report at bugs.python.org (Christian Heimes)
Date: Sun, 17 Nov 2013 14:01:35 +0000
Subject: [docs] [issue19508] Add warning that Python doesn't verify SSL
	certs by	default
In-Reply-To: <1383691927.99.0.022250098505.issue19508@psf.upfronthosting.co.za>
Message-ID: <1384696895.71.0.405317836103.issue19508@psf.upfronthosting.co.za>


Christian Heimes added the comment:

I suggest that we add a red warning box at the top of the SSL module, too.

----------

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

From report at bugs.python.org  Sun Nov 17 15:11:17 2013
From: report at bugs.python.org (Christian Heimes)
Date: Sun, 17 Nov 2013 14:11:17 +0000
Subject: [docs] [issue17006] Warn users about hashing secrets?
In-Reply-To: <1358758082.76.0.415880124971.issue17006@psf.upfronthosting.co.za>
Message-ID: <1384697476.99.0.66983113553.issue17006@psf.upfronthosting.co.za>


Christian Heimes added the comment:

ping :)

----------

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

From report at bugs.python.org  Sun Nov 17 15:15:36 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 17 Nov 2013 14:15:36 +0000
Subject: [docs] [issue19508] Add warning that Python doesn't verify SSL
	certs by	default
In-Reply-To: <1383691927.99.0.022250098505.issue19508@psf.upfronthosting.co.za>
Message-ID: <1384697736.44.0.236733993229.issue19508@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Something like the following?

----------
keywords: +patch
Added file: http://bugs.python.org/file32668/sslsec.patch

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

From report at bugs.python.org  Sun Nov 17 15:29:49 2013
From: report at bugs.python.org (Christian Heimes)
Date: Sun, 17 Nov 2013 14:29:49 +0000
Subject: [docs] [issue18617] TLS and Intermediate Certificates
In-Reply-To: <1375376317.99.0.429350247521.issue18617@psf.upfronthosting.co.za>
Message-ID: <1384698589.82.0.077652663686.issue18617@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Donald, could you please provide a doc update that explains the problem?

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

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

From report at bugs.python.org  Sun Nov 17 15:30:55 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 17 Nov 2013 14:30:55 +0000
Subject: [docs] [issue18617] TLS and Intermediate Certificates
In-Reply-To: <1375376317.99.0.429350247521.issue18617@psf.upfronthosting.co.za>
Message-ID: <1384698655.75.0.548907697741.issue18617@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I'm afraid downloading certs on the fly would open a whole new can of worms, so I'd rather have it documented indeed :)

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

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

From report at bugs.python.org  Sun Nov 17 15:35:19 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 17 Nov 2013 14:35:19 +0000
Subject: [docs] [issue19508] Add warning that Python doesn't verify SSL
	certs by	default
In-Reply-To: <1383691927.99.0.022250098505.issue19508@psf.upfronthosting.co.za>
Message-ID: <1384698919.63.0.478421220783.issue19508@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Sounds good.

----------
nosy: +georg.brandl

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

From report at bugs.python.org  Sun Nov 17 15:36:13 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 17 Nov 2013 14:36:13 +0000
Subject: [docs] [issue19508] Add warning that Python doesn't verify SSL
	certs by	default
In-Reply-To: <1383691927.99.0.022250098505.issue19508@psf.upfronthosting.co.za>
Message-ID: <3dMwpN2Nnzz7Ljl@mail.python.org>


Roundup Robot added the comment:

New changeset f86fdaf529ea by Antoine Pitrou in branch '3.3':
Issue #19508: direct the user to read the security considerations for the ssl module
http://hg.python.org/cpython/rev/f86fdaf529ea

New changeset 18d95780100e by Antoine Pitrou in branch 'default':
Issue #19508: direct the user to read the security considerations for the ssl module
http://hg.python.org/cpython/rev/18d95780100e

----------
nosy: +python-dev

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

From report at bugs.python.org  Sun Nov 17 15:37:44 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 17 Nov 2013 14:37:44 +0000
Subject: [docs] [issue8402] Add a function to escape metacharacters in
	glob/fnmatch
In-Reply-To: <1271292687.68.0.249436327738.issue8402@psf.upfronthosting.co.za>
Message-ID: <1384699063.86.0.73923728075.issue8402@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Could anyone please review the patch before feature freeze?

----------

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

From report at bugs.python.org  Sun Nov 17 15:37:44 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 17 Nov 2013 14:37:44 +0000
Subject: [docs] [issue19632] doc build warning
Message-ID: <1384699064.41.0.714714605877.issue19632@psf.upfronthosting.co.za>


New submission from Antoine Pitrou:

This is on 2.7:

reading sources... [100%] whatsnew/index                                                                                                              
/home/antoine/cpython/27/Doc/library/functions.rst:1186: WARNING: duplicate object description of repr, other instance in /home/antoine/cpython/27/Doc/library/repr.rst, use :noindex: for one of them
looking for now-outdated files... none found

----------
assignee: docs at python
components: Documentation
messages: 203180
nosy: docs at python, pitrou
priority: low
severity: normal
stage: needs patch
status: open
title: doc build warning
versions: Python 2.7

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

From report at bugs.python.org  Sun Nov 17 15:43:04 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 17 Nov 2013 14:43:04 +0000
Subject: [docs] [issue19508] Add warning that Python doesn't verify SSL
	certs by	default
In-Reply-To: <1383691927.99.0.022250098505.issue19508@psf.upfronthosting.co.za>
Message-ID: <3dMwyH4yzdz7Ln5@mail.python.org>


Roundup Robot added the comment:

New changeset a197b3c3b2c9 by Antoine Pitrou in branch '2.7':
Issue #19508: warn that ssl doesn't validate certificates by default
http://hg.python.org/cpython/rev/a197b3c3b2c9

----------

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

From report at bugs.python.org  Sun Nov 17 15:43:40 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 17 Nov 2013 14:43:40 +0000
Subject: [docs] [issue19508] Add warning that Python doesn't verify SSL
	certs by	default
In-Reply-To: <1383691927.99.0.022250098505.issue19508@psf.upfronthosting.co.za>
Message-ID: <1384699420.76.0.881869543259.issue19508@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I've added a different warning to 2.7, as the ssl docs there don't have the "security considerations" section.

----------
resolution:  -> fixed
stage: needs patch -> committed/rejected
versions:  -Python 2.7, Python 3.2

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

From report at bugs.python.org  Sun Nov 17 16:48:06 2013
From: report at bugs.python.org (=?utf-8?q?Michele_Orr=C3=B9?=)
Date: Sun, 17 Nov 2013 15:48:06 +0000
Subject: [docs] [issue8402] Add a function to escape metacharacters in
	glob/fnmatch
In-Reply-To: <1271292687.68.0.249436327738.issue8402@psf.upfronthosting.co.za>
Message-ID: <1384703286.55.0.0634708232881.issue8402@psf.upfronthosting.co.za>


Changes by Michele Orr? <maker.py at gmail.com>:


----------
nosy:  -maker

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

From report at bugs.python.org  Sun Nov 17 19:51:00 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 17 Nov 2013 18:51:00 +0000
Subject: [docs] [issue17006] Warn users about hashing secrets?
In-Reply-To: <1358758082.76.0.415880124971.issue17006@psf.upfronthosting.co.za>
Message-ID: <1384714260.52.0.849498091139.issue17006@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

This might be useful to whoever attempts to write a patch: http://docs.python.org/devguide/documenting.html#security-considerations-and-other-concerns

----------

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

From report at bugs.python.org  Sun Nov 17 23:44:38 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 17 Nov 2013 22:44:38 +0000
Subject: [docs] [issue8402] Add a function to escape metacharacters in
	glob/fnmatch
In-Reply-To: <1271292687.68.0.249436327738.issue8402@psf.upfronthosting.co.za>
Message-ID: <1384728277.94.0.797586123031.issue8402@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Updated patch addresses Ezio's and Eric's comments.

----------
Added file: http://bugs.python.org/file32673/glob_escape_2.patch

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

From report at bugs.python.org  Mon Nov 18 00:05:47 2013
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 17 Nov 2013 23:05:47 +0000
Subject: [docs] [issue17006] Warn users about hashing secrets?
In-Reply-To: <1358758082.76.0.415880124971.issue17006@psf.upfronthosting.co.za>
Message-ID: <1384729547.18.0.0955878925289.issue17006@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> For passwords a key stretching and key derivation function like PBKDF2, bcrypt or scrypt is much more secure.

It looks like Python 3.4 now provides something for pbkdf2, so it may be interested to mention it on the top of the hashlib in your warning.

http://docs.python.org/dev/library/hashlib.html#hashlib.pbkdf2_hmac

----------
nosy: +haypo

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

From report at bugs.python.org  Mon Nov 18 02:10:32 2013
From: report at bugs.python.org (Eric V. Smith)
Date: Mon, 18 Nov 2013 01:10:32 +0000
Subject: [docs] [issue19504] Change "customise" to "customize".
In-Reply-To: <1383659200.62.0.979344465483.issue19504@psf.upfronthosting.co.za>
Message-ID: <1384737030.73.0.676091657467.issue19504@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

This patch covers the files that Vinay did not update.

----------
Added file: http://bugs.python.org/file32677/customise-2.diff

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

From report at bugs.python.org  Mon Nov 18 04:05:28 2013
From: report at bugs.python.org (Jon Gauthier)
Date: Mon, 18 Nov 2013 03:05:28 +0000
Subject: [docs] [issue19164] Update uuid.UUID TypeError exception: integer
	should not	be an argument.
In-Reply-To: <1380885490.13.0.480584034262.issue19164@psf.upfronthosting.co.za>
Message-ID: <1384743928.51.0.505814108577.issue19164@psf.upfronthosting.co.za>


Changes by Jon Gauthier <jon at gauthiers.net>:


----------
keywords: +patch
Added file: http://bugs.python.org/file32678/issue19164.patch

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

From report at bugs.python.org  Mon Nov 18 10:35:16 2013
From: report at bugs.python.org (Claudiu.Popa)
Date: Mon, 18 Nov 2013 09:35:16 +0000
Subject: [docs] [issue19639] Improve re match objects display
Message-ID: <1384767316.36.0.259346591403.issue19639@psf.upfronthosting.co.za>


New submission from Claudiu.Popa:

When issue17087 was accepted, the documentation wasn't changed to reflect the new changes. The attached patch fixes this, replacing the old <_sre.Match object ...> with the deterministic repr of the match object.

----------
assignee: docs at python
components: Documentation
files: re_doc.patch
keywords: patch
messages: 203268
nosy: Claudiu.Popa, docs at python
priority: normal
severity: normal
status: open
title: Improve re match objects display
versions: Python 3.4
Added file: http://bugs.python.org/file32684/re_doc.patch

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

From report at bugs.python.org  Mon Nov 18 10:50:56 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 18 Nov 2013 09:50:56 +0000
Subject: [docs] [issue19639] Improve re match objects display
In-Reply-To: <1384767316.36.0.259346591403.issue19639@psf.upfronthosting.co.za>
Message-ID: <1384768256.02.0.40441036737.issue19639@psf.upfronthosting.co.za>


Changes by Ezio Melotti <ezio.melotti at gmail.com>:


----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
stage:  -> patch review
type:  -> enhancement

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

From report at bugs.python.org  Mon Nov 18 11:33:55 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 18 Nov 2013 10:33:55 +0000
Subject: [docs] [issue8402] Add a function to escape metacharacters in
	glob/fnmatch
In-Reply-To: <1271292687.68.0.249436327738.issue8402@psf.upfronthosting.co.za>
Message-ID: <1384770835.46.0.083682130932.issue8402@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Updated patch addresses Eric's comment.

----------
Added file: http://bugs.python.org/file32687/glob_escape_3.patch

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

From report at bugs.python.org  Mon Nov 18 11:59:31 2013
From: report at bugs.python.org (Eric V. Smith)
Date: Mon, 18 Nov 2013 10:59:31 +0000
Subject: [docs] [issue8402] Add a function to escape metacharacters in
	glob/fnmatch
In-Reply-To: <1271292687.68.0.249436327738.issue8402@psf.upfronthosting.co.za>
Message-ID: <1384772371.1.0.300554781993.issue8402@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

Looks good to me.

----------

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

From report at bugs.python.org  Mon Nov 18 12:07:37 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 18 Nov 2013 11:07:37 +0000
Subject: [docs] [issue8402] Add a function to escape metacharacters in
	glob/fnmatch
In-Reply-To: <1271292687.68.0.249436327738.issue8402@psf.upfronthosting.co.za>
Message-ID: <3dNS7D59Rqz7Mdv@mail.python.org>


Roundup Robot added the comment:

New changeset 5fda36bff39d by Serhiy Storchaka in branch 'default':
Issue #8402: Added the escape() function to the glob module.
http://hg.python.org/cpython/rev/5fda36bff39d

----------
nosy: +python-dev

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

From report at bugs.python.org  Mon Nov 18 12:09:40 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 18 Nov 2013 11:09:40 +0000
Subject: [docs] [issue8402] Add a function to escape metacharacters in
	glob/fnmatch
In-Reply-To: <1271292687.68.0.249436327738.issue8402@psf.upfronthosting.co.za>
Message-ID: <1384772980.37.0.188171915421.issue8402@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you Ezio and Eric for your reviews.

----------
assignee:  -> serhiy.storchaka
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From tomwallroth at gmail.com  Mon Nov  4 16:07:15 2013
From: tomwallroth at gmail.com (Tom Wallroth)
Date: Mon, 4 Nov 2013 16:07:15 +0100
Subject: [docs] pygettext is obsolete
Message-ID: <CAO3QW_5AE5N4Uo9rdRbhqhKqBtuA7tD6cRgrStS43xnHgz0cKA@mail.gmail.com>

Dear mailing list,

The documentation for i18n support is a bit outdated. It mentions
pygettext, but it seems that pygettext was declared obsolete by just about
anybody in 2004 and was replaced by its original implementation "xgettext".

Here's a link to the part of the documentation, which is outdated:
http://docs.python.org/3.3/library/gettext.html#id3

And some proof of pygettext not being used anymore since 2004:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=246332

Sincerely,
Tom Wallroth
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131104/375dbd80/attachment-0001.html>

From dhaval.bhanu at gmail.com  Tue Nov  5 10:41:56 2013
From: dhaval.bhanu at gmail.com (Dhawal Bhanushali)
Date: Tue, 5 Nov 2013 15:11:56 +0530
Subject: [docs] Doc Bug: argparse positional argument documentation is wrong.
Message-ID: <CABx4=BYr1gudhwSUPuaRSr0viHE_DQo5d44XX+PBfUDLqg=VBg@mail.gmail.com>

I tried the example for argparse in my shell
http://docs.python.org/2/howto/argparse.html#introducing-positional-arguments

Found that the output is different from the one I got in the shell.

Here is the output in the shell.

http://ideone.com/D0as2n

Thanks,
DYB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131105/a532e2d4/attachment.html>

From shalinshah1993 at gmail.com  Tue Nov  5 14:45:10 2013
From: shalinshah1993 at gmail.com (Shalin Shah)
Date: Tue, 5 Nov 2013 19:15:10 +0530
Subject: [docs] Subprocess Crashes on OSX using wxpython GUI
Message-ID: <CAPJsyhqPgyEi5TfnzO2UX=47BKA_KzR6kj95EqrdVSqS6M5vgA@mail.gmail.com>

Hello,

I have a GUI software in which I wanted to do some heavy tasks so I create
new subprocesses to run those tasks. To do this I am using multiprocessing
module and this works perfectly fine on windows as well as unix. However
when I try the same for OSX 10.6 process crash occurs and I get a long
error report which I cannot decipher. Here is something I used to make a
sub-process :-

p = multiprocessing.Process(target = encode.encode , args =
(self.path,self.savePath,) , name = "Encode Process")
p.start()
temp = wx.ProgressDialog('Please wait...', 'Encoding the File....This
may take several minutes....\n\t....so sit back and relax....',parent
= self,style = wx.PD_APP_MODAL | wx.PD_CAN_ABORT)
temp.SetSize((450,130))while len(multiprocessing.active_children()) != 0:
      time.sleep(0.1)
      if not temp.UpdatePulse("Encoding the File....This may take
several minutes...\n\tso sit back and relax.....")[0]:
                   p.terminate()
                   terminated = True
                   break
temp.Destroy()
p.join()
p.terminate()


Here is the crash report :-

Path:/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/PythonIdentifier:
     PythonVersion:         ??? (???)Code Type:       X86
(Native)Parent Process:  Python [52639]
Date/Time:       2013-07-23 12:22:46.170 +0530
OS Version:      Mac OS X 10.6.7 (10J869)Report Version:  6
Interval Since Last Report:          14328 secCrashes Since Last
Report:           9Per-App Crashes Since Last Report:   9Anonymous
UUID:                      DE5488A5-8468-4937-800F-F898E4F09392
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)Exception Codes:
KERN_INVALID_ADDRESS at 0x000000000d28e02eCrashed Thread:  0  Dispatch
queue: com.apple.main-thread
Application Specific Information:*** multi-threaded process forked ***
Thread 0 Crashed:  Dispatch queue: com.apple.main-thread0
...ple.ApplicationServices.ATS  0x929b43a0 _eGetGlyphVectorIndex +
2191   ...ple.ApplicationServices.ATS  0x929bec46
OldGlyphsCacheRun(TStrike*, int, unsigned long, unsigned short const*,
void (*)(unsigned long, unsigned short const*, unsigned long, unsigned
char* const*, void const*), void*) + 3542
...ple.ApplicationServices.ATS  0x929c2502 _eGCGetGlyphDeviceMetrics +
4753   ...ple.ApplicationServices.ATS  0x929c56fd
GCGetGlyphDeviceMetrics + 1174   com.apple.QD
0x906cc386 GetLayoutDevMetricsGroup(ATSGlyphVector*, unsigned long,
unsigned long, Rect*) + 11055   com.apple.QD
0x906ca6c9 MakeLayoutDeviceValues + 6166   com.apple.QD
    0x906ca434 PositionDeviceGlyphs + 1367   com.apple.QD
      0x906c87a7 TTextLineLayout::EnsureLayoutIsUpToDate(unsigned
long, unsigned char, unsigned long, TATSUGlyphRecordArray**) + 5018
com.apple.QD                    0x90747ebe
TTextLineLayout::OffsetToPosition(unsigned long, unsigned char,
unsigned short, ATSUCaret*, ATSUCaret*, unsigned char*) + 1689
com.apple.QD                    0x90735ca5 ATSUOffsetToCursorPosition
+ 11710  com.apple.QD                    0x90735cfc
ATSUOffsetToPosition + 6111  com.apple.HIToolbox
0x957dea93 CUnicodeTextRun::CharacterToPixel(LineRunDisplayInfo
const&, short, void*, void*) + 55112  com.apple.HIToolbox
0x957ef995 CLine::RunCharToPixel(LineRunInfo const*, long, unsigned
char, ATSUCaret*, ATSUCaret*) + 8713  com.apple.HIToolbox
0x957eff7b CLine::CharacterToPixel(TCharOffset, char, ATSUCaret*) +
22114  com.apple.HIToolbox             0x957f0063
CLine::GetLineHilites(TCharOffsetRange, CLineHilitesList*, unsigned
char, char) + 7915  com.apple.HIToolbox             0x957b60ea
CTextensionDisplay::GetLineHilites(long, TCharOffsetRange,
CLineHilitesList*, unsigned char, char) + 10616  com.apple.HIToolbox
          0x957e8819 CSelection::CalcRangeRect(TCharOffsetRange,
TLongRect*, unsigned char) + 19717  com.apple.HIToolbox
0x957e88df CSelection::CalcCaretRect() + 6118  com.apple.HIToolbox
        0x957e893d CSelection::GetCaretRect(TLongRect*) + 3319
com.apple.HIToolbox             0x957b6132
CTextensionDisplay::CharToPoint(TCharOffset, long*, long*, long*) +
6020  com.apple.HIToolbox             0x957b6e66
CTextensionDisplay::CharToPoint(TCharOffset, long*) + 5821
com.apple.HIToolbox             0x957ebd2a
CSelection::UpdateAnchors(TCharOffsetRange const&, unsigned char,
unsigned char) + 9822  com.apple.HIToolbox             0x957b9b4b
CTextensionDisplay::EndEdit(TEditInfo const&, long, long,
TCharOffset*) + 16523  com.apple.HIToolbox             0x957c80e2
CTextension::EndEdit(TEditInfo const&, long, long, TCharOffset*,
unsigned char) + 5624  com.apple.HIToolbox             0x957d930a
CUnicodeTextension::UnicodeReplaceRange(long, long, TReplaceParams
const&, unsigned char, unsigned char) + 260025  com.apple.HIToolbox
         0x957d9509 CUnicodeTextension::ReplaceRange(long, long,
TReplaceParams const&, unsigned char, unsigned char) + 10126
com.apple.HIToolbox             0x957ca5cd
CReplaceTextCommand::DoMainAction() + 6727  com.apple.HIToolbox
     0x957ca035 CTextensionEditCommand::DoIt(short*) + 2928
com.apple.HIToolbox             0x957c9920
CTextensionCommand::Execute(short*) + 5429  com.apple.HIToolbox
     0x957cf9c9 OpaqueTXNObject::ExecuteCurrCommand() + 11330
com.apple.HIToolbox             0x957cff11
OpaqueTXNObject::NewCommand(short, AttrObjModifier const*,
TKeyDownParams*, TReplaceParams*) + 106131  com.apple.HIToolbox
     0x957bd030 DoSetDataCommand(OpaqueTXNObject*, unsigned long,
unsigned long, TReplaceParams*) + 29932  com.apple.HIToolbox
  0x957c4fd3 TXNSetData + 68333  libwx_macud-2.8.0.dylib
0x0171d9f8 wxMacMLTEControl::SetTXNData(wxString const&, unsigned
long, unsigned long) + 16834  libwx_macud-2.8.0.dylib
0x017207b5 wxMacMLTEControl::WriteText(wxString const&) + 20535
libwx_macud-2.8.0.dylib         0x0171fa82
wxTextCtrl::WriteText(wxString const&) + 24236  _controls_.so
         0x05c88633 _wrap_TextCtrl_AppendText + 247 (wxPython.h:48)37
org.python.python               0x000c8841 PyEval_EvalFrameEx +
2076938  org.python.python               0x000ca90a PyEval_EvalCodeEx
+ 204239  org.python.python               0x000c8b33
PyEval_EvalFrameEx + 2152340  org.python.python
0x000c9933 PyEval_EvalFrameEx + 2510741  org.python.python
  0x000ca90a PyEval_EvalCodeEx + 204242  org.python.python
  0x00042832 function_call + 16243  org.python.python
0x0000f5b5 PyObject_Call + 8544  org.python.python
0x00021ff6 instancemethod_call + 42245  org.python.python
 0x0000f5b5 PyObject_Call + 8546  org.python.python
0x000c278e PyEval_CallObjectWithKeywords + 7847  org.python.python
          0x00038f02 PyFile_WriteObject + 35448  org.python.python
          0x000c6c4c PyEval_EvalFrameEx + 1361249  org.python.python
            0x000c9933 PyEval_EvalFrameEx + 2510750  org.python.python
              0x000ca90a PyEval_EvalCodeEx + 204251  org.python.python
              0x00042832 function_call + 16252  org.python.python
         0x0000f5b5 PyObject_Call + 8553  org.python.python
   0x000c617b PyEval_EvalFrameEx + 1084354  org.python.python
     0x000c9933 PyEval_EvalFrameEx + 2510755  org.python.python
       0x000c9933 PyEval_EvalFrameEx + 2510756  org.python.python
         0x000ca90a PyEval_EvalCodeEx + 204257  org.python.python
         0x00042832 function_call + 16258  org.python.python
    0x0000f5b5 PyObject_Call + 8559  org.python.python
0x00021ff6 instancemethod_call + 42260  org.python.python
 0x0000f5b5 PyObject_Call + 8561  org.python.python
0x0007dd17 slot_tp_init + 8762  org.python.python
0x0007c710 type_call + 17663  org.python.python
0x0000f5b5 PyObject_Call + 8564  org.python.python
0x000c6ef6 PyEval_EvalFrameEx + 1429465  org.python.python
  0x000c9933 PyEval_EvalFrameEx + 2510766  org.python.python
    0x000ca90a PyEval_EvalCodeEx + 204267  org.python.python
    0x00042832 function_call + 16268  org.python.python
0x0000f5b5 PyObject_Call + 8569  org.python.python
0x00021ff6 instancemethod_call + 42270  org.python.python
 0x0000f5b5 PyObject_Call + 8571  org.python.python
0x000c278e PyEval_CallObjectWithKeywords + 7872  _core_.so
          0x0100ab2e wxPyCallback::EventThunker(wxEvent&) + 234
(helpers.cpp:1759)73  libwx_macud-2.8.0.dylib         0x0169c97a
wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&) + 10874  libwx_macud-2.8.0.dylib
0x0169ca20 wxEvtHandler::SearchDynamicEventTable(wxEvent&) + 8075
libwx_macud-2.8.0.dylib         0x0169d81f
wxEvtHandler::ProcessEvent(wxEvent&) + 22576  libwx_macud-2.8.0.dylib
       0x016cf6b1 wxControl::ProcessCommand(wxCommandEvent&) + 2777
libwx_macud-2.8.0.dylib         0x016ca2f6
wxButton::MacControlHit(void*, void*) + 6278  libwx_macud-2.8.0.dylib
       0x01734d47
wxMacWindowControlEventHandler(OpaqueEventHandlerCallRef*,
OpaqueEventRef*, void*) + 60579  libwx_macud-2.8.0.dylib
0x017356a9 wxMacWindowEventHandler(OpaqueEventHandlerCallRef*,
OpaqueEventRef*, void*) + 19780  com.apple.HIToolbox
0x95582c2f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*,
HandlerCallRec*) + 156781  com.apple.HIToolbox             0x95581ef6
SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*,
HandlerCallRec*) + 41182  com.apple.HIToolbox             0x955a47f3
SendEventToEventTarget + 5283  com.apple.HIToolbox
0x955f3cce SendControlHit(HIView*, OpaqueEventRef*, short, unsigned
long) + 29684  com.apple.HIToolbox             0x955f3b4f
HIView::NotifyControlHit(OpaqueEventRef*, short, unsigned long) + 4585
 com.apple.HIToolbox             0x9565865f
HIView::ClickInternal(CGPoint const&, unsigned long, void
(*)(OpaqueControlRef*, short), OpaqueEventRef*, bool) + 24586
com.apple.HIToolbox             0x95659c18
HIView::ClickSelf(OpaqueEventRef*) + 36887  com.apple.HIToolbox
     0x95595af9 HIView::EventHandler(OpaqueEventHandlerCallRef*,
OpaqueEventRef*, void*) + 236388  com.apple.HIToolbox
0x95582c2f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*,
HandlerCallRec*) + 156789  com.apple.HIToolbox             0x95581ef6
SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*,
HandlerCallRec*) + 41190  com.apple.HIToolbox             0x955a47f3
SendEventToEventTarget + 5291  com.apple.HIToolbox
0x955f2b8e HIView::Click(OpaqueEventRef*) + 48092  com.apple.HIToolbox
            0x955f295b HandleClickAsHIView(OpaqueWindowPtr*,
OpaqueEventRef*) + 15193  com.apple.HIToolbox             0x955f1238
HandleWindowClick(OpaqueWindowPtr*, Point, short, unsigned long,
OpaqueEventRef*) + 49194  com.apple.HIToolbox             0x955f0d3b
HandleMouseEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 78695
com.apple.HIToolbox             0x955f0652
StandardWindowEventHandler(OpaqueEventHandlerCallRef*,
OpaqueEventRef*, void*) + 9396  com.apple.HIToolbox
0x95582c2f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*,
HandlerCallRec*) + 156797  com.apple.HIToolbox             0x95581ef6
SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*,
HandlerCallRec*) + 41198  com.apple.HIToolbox             0x955a47f3
SendEventToEventTarget + 5299  com.apple.HIToolbox
0x955b634f ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*,
OpaqueEventRef*, void*) + 1257100 com.apple.HIToolbox
0x95583080 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*,
HandlerCallRec*) + 2672101 com.apple.HIToolbox             0x95581ef6
SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*,
HandlerCallRec*) + 411102 com.apple.HIToolbox             0x955a47f3
SendEventToEventTarget + 52103 libwx_macud-2.8.0.dylib
0x016bfd9a wxApp::MacHandleOneEvent(void*) + 34104
libwx_macud-2.8.0.dylib         0x016bfe62 wxApp::MacDoOneEvent() +
120105 libwx_macud-2.8.0.dylib         0x016da3de
wxEventLoop::Dispatch() + 32106 libwx_macud-2.8.0.dylib
0x0179667d wxEventLoopManual::Run() + 97107 libwx_macud-2.8.0.dylib
     0x0176c7fe wxAppBase::MainLoop() + 76108 _core_.so
       0x010018dc wxPyApp::MainLoop() + 52 (helpers.cpp:215)109
_core_.so                       0x0104f03a _wrap_PyApp_MainLoop + 82
(_core_wrap.cpp:31686)110 org.python.python               0x000c8841
PyEval_EvalFrameEx + 20769111 org.python.python
0x000ca90a PyEval_EvalCodeEx + 2042112 org.python.python
0x00042832 function_call + 162113 org.python.python
0x0000f5b5 PyObject_Call + 85114 org.python.python
0x00021ff6 instancemethod_call + 422115 org.python.python
 0x0000f5b5 PyObject_Call + 85116 org.python.python
0x000c6ef6 PyEval_EvalFrameEx + 14294117 org.python.python
  0x000c9933 PyEval_EvalFrameEx + 25107118 org.python.python
    0x000ca90a PyEval_EvalCodeEx + 2042119 org.python.python
    0x000caa97 PyEval_EvalCode + 87120 org.python.python
0x000ef158 PyRun_FileExFlags + 168121 org.python.python
0x000f0087 PyRun_SimpleFileExFlags + 855122 org.python.python
     0x00109137 Py_Main + 3255123 org.python.python
0x00001f82 0x1000 + 3970


I am not sure what the problem is as it works perfectly fine on windows and
unix. Any kind of help is appreciated. I ran this again using sudo and this
time there is no crash but on the other hand there is no output. Already
seen this *issue* <http://bugs.python.org/issue9405> but how should I fix
it in my case?

-- 
Regards,
Shalin Shah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131105/a553fb56/attachment-0001.html>

From cclauss at bluewin.ch  Wed Nov  6 10:56:35 2013
From: cclauss at bluewin.ch (Christian Clauss)
Date: Wed, 6 Nov 2013 10:56:35 +0100
Subject: [docs] Python on the Mac page needs an update
Message-ID: <5A1104E5-43B5-4DA5-ACB8-95CB255CAADE@bluewin.ch>

http://www.python.org/download/mac

Given that Mac OS X now ships with Python v2.7.5 by default on all Macs, the Python on the Mac page is in serous need of an update.

That page currently mentions a lot of our of date Mac OS X releases (Panther, Leopard, etc.)

From SWHOMOL at embratel.com.br  Wed Nov  6 15:15:59 2013
From: SWHOMOL at embratel.com.br (CAIXA DE SERVICO  SWHOMOL)
Date: Wed, 6 Nov 2013 12:15:59 -0200
Subject: [docs] Doubt
In-Reply-To: <607E40E4F441B14A94FE5AC972557F130158B643A355@2K3RJOCX003.nt.embratel.com.br>
References: <607E40E4F441B14A94FE5AC972557F130158B643A355@2K3RJOCX003.nt.embratel.com.br>
Message-ID: <607E40E4F441B14A94FE5AC972557F130158B643A4F7@2K3RJOCX003.nt.embratel.com.br>

Good morning
Python.

The Python software  it's very interesting, therefore we have a question.

Would like to know if it's allowed to use free the  Python 3.3.2 AMD64 software for commercial projects or if only through acquisition a purchase order?





Regards,
Marcos
_______________________
Homologa??o de Hardware e Software

Embratel (Brazilian Telecommunications Company)
swhomol at embratel.com.br<mailto:swhomol at embratel.com.br>


[cid:image001.jpg at 01CEDA1F.884F1AD0]


________________________________
AVISO DE CONFIDENCIALIDADE
Esta mensagem e seus anexos s?o de uso exclusivo de pessoas e entidades autorizadas pela Embratel e podem conter informa??es confidenciais e/ou privilegiadas. ? proibido revelar, alterar, copiar, divulgar ou se beneficiar, direta ou indiretamente, destas informa??es sem a autoriza??o de seus autores. Se voc? recebeu este e-mail por engano, por favor, informe o remetente e apague a mensagem imediatamente. A Embratel se reserva o direito de pleitear ressarcimento pelos preju?zos decorrentes do uso indevido das informa??es e de requerer a aplica??o das penalidades cab?veis.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131106/2e0ea7a8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2711 bytes
Desc: image001.jpg
URL: <http://mail.python.org/pipermail/docs/attachments/20131106/2e0ea7a8/attachment-0001.jpg>

From Guang.Xu at uea.ac.uk  Thu Nov  7 12:52:10 2013
From: Guang.Xu at uea.ac.uk (Guangzhi Xu (ENV))
Date: Thu, 7 Nov 2013 11:52:10 +0000
Subject: [docs] A possible bug in the "property()" function documentation
Message-ID: <72275826D4AEA64E82A17348819991B90477E8@ueastuexch03.UEA.AC.UK>

Hello:

I have noticed one, probably not strictly a "bug", maybe just one problematic sentence:

"This code is exactly equivalent to the first example. Be sure to give the additional functions the same name as the original property (x in this case.)"

My doubt is that those 2 blocks of codes are not exactly equivalent.

In the first example:

class C(object):
    def __init__(self):
        self._x = None

    def getx(self):
        return self._x
    def setx(self, value):
        self._x = value
    def delx(self):
        del self._x
    x = property(getx, setx, delx, "I'm the 'x' property.")

If I type in "del c.x", it will delete the value attached to "x", and again give "x"
the initial value as assigned in the __init__(), in this case it is None. Therefore
if I type in "tyep(c.x)", it will give me <type 'NoneType'>

Here is screen output:

>>> c.x=10
>>> c.x
10
>>> del c.x
>>> type(c.x)
<type 'NoneType'>

While if I use the 2nd example:

class C(object):
    def __init__(self):
        self._x = 50

    @property
    def x(self):
        """I'm the 'x' property."""
        return self._x

    @x.setter
    def x(self, value):
        self._x = value

    @x.deleter
    def x(self):
        del self._x

Issuing "del c.x" seems to really delete that attribute so "c.x" no longer exists:

>>> c.x
50
>>> del c.x
>>> c.x
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "testproperty.py", line 28, in x
    return self._x
AttributeError: 'C' object has no attribute '_x'

So the deleters in those 2 examples are behaving differently.

Regards
Guangzhi



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131107/60f21793/attachment-0001.html>

From viktor.lucza at gmail.com  Fri Nov  8 14:00:29 2013
From: viktor.lucza at gmail.com (Viktor Lucza)
Date: Fri, 8 Nov 2013 14:00:29 +0100
Subject: [docs] Invalid method name in example for multiprocessing 3.2
Message-ID: <CAMOqX7xD1t6sq79B_qytRjSKRpfbeRK5nyAaJGq3mRBhKpaxNQ@mail.gmail.com>

The problem was found here:
http://docs.python.org/3.2/library/multiprocessing.html#module-multiprocessing.pool

I believe one of these should be called next instead of __next__:

# Proxy type for generator objectsclass GeneratorProxy(BaseProxy):
    _exposed_ = ('next', '__next__')
    def __iter__(self):
        return self
    def __next__(self):
        return self._callmethod('next')
    def __next__(self):
        return self._callmethod('__next__')


-- 
Viktor Lucza
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131108/0ada5bb7/attachment.html>

From michel at albert.lu  Fri Nov  8 18:19:08 2013
From: michel at albert.lu (Michel Albert)
Date: Fri, 8 Nov 2013 18:19:08 +0100
Subject: [docs] Documentation is missing for distutils.version for Python 3.2
Message-ID: <CAM8bmgBy45GXxBE47Fc6OTP+XzPmGOFN0GLOqDHNBeHffYHJ2g@mail.gmail.com>

See
http://docs.python.org/3.2/distutils/apiref.html#module-distutils.version

Apparently, the docs for 2.7 are empty as well:
http://docs.python.org/2/distutils/apiref.html#module-distutils.version
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131108/eda5e7a4/attachment.html>

From arbautjc at gmail.com  Sun Nov 10 09:49:34 2013
From: arbautjc at gmail.com (Jean-Claude Arbaut)
Date: Sun, 10 Nov 2013 09:49:34 +0100
Subject: [docs] little mistake in PEP 373
Message-ID: <CANufCk7POcPj_V7w3t25dPZzrfgQ9V=kPt4f+QLuya=ROq=OqQ@mail.gmail.com>

Hello,

I'm not sure it's the right place to post this, but on page

        http://www.python.org/dev/peps/pep-0373/

There is a mistake in the release date of 2.7.6, which is given as "2.7.6
2012-11-10"
I'm not sure for the day (*), but the year is certainly wrong.

Jean-Claude Arbaut

(*) It's today, except in Alaska, where it's still saturday right know :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131110/117c0306/attachment-0001.html>

From cclauss at me.com  Mon Nov 11 12:31:50 2013
From: cclauss at me.com (cclauss)
Date: Mon, 11 Nov 2013 12:31:50 +0100
Subject: [docs] 2.7.6 release has a headline that says 2.6.9!!! Looks like a
 copy/paste error
Message-ID: <1D0A89E8-5100-4744-AB5D-369F8A982CFD@me.com>

Python 2.6.9 released

Python 2.7.6 is now available.

Published: Sun, 10 November 2013, 02:30 -0500
Python 2.6.9 final available

The final release of Python 2.6.9 (and the final release of the 2.6 series) is now available.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131111/fe15f3f6/attachment.html>

From rothstei at cs.kent.edu  Mon Nov 11 18:36:17 2013
From: rothstei at cs.kent.edu (Michael Rothstein)
Date: Mon, 11 Nov 2013 12:36:17 -0500
Subject: [docs] Global variables at the interpreter level?
Message-ID: <20131111173617.GA20798@cs.kent.edu>

There seems to be a total disconnect between interpreter level variables and
global variables. Is that correct? The attached code illustrates the issue:
the global count changes values, but the interpreter level count remains
steadfastly at 0. Also, it does not reset to 0 if I set:
count = 0
at the interpreter level.
Is this a bug or a feature, or am I doing something wrong?
Thanks for the help!
Michael Rothstein
-- 
---------------------------------------------------------------------------
Michael Rothstein Ph D                | Office (at 268 MSB)  (330)-672-9065
Dept. of Computer Science             | Fax:    (330)-672-0737
Kent State University                 | Email:  rothstei at cs.kent.edu
PO Box 5190                           | http://www.cs.kent.edu/~rothstei
Kent, OH 44242-0001                   | 
---------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fibo1.py
Type: text/x-python
Size: 175 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20131111/ae9e700a/attachment-0001.py>

From dfong at dfong.com  Wed Nov 13 08:40:16 2013
From: dfong at dfong.com (don fong)
Date: Tue, 12 Nov 2013 23:40:16 -0800
Subject: [docs] bug in pydoc documentation
Message-ID: <52832CE0.8090808@dfong.com>

on this page, http://docs.python.org/2/library/pydoc.html,
there is no mention of nor explanation of what a docstring is.
there is no mention of what formatting conventions docstrings
should follow in order for pydoc to work.  if there's no single
standard then the page should say so explicitly and give
pointers to a few of the competing conventions.


From asadiatu at ualberta.ca  Wed Nov 13 22:06:45 2013
From: asadiatu at ualberta.ca (Kavosh Asadi Atui)
Date: Wed, 13 Nov 2013 16:06:45 -0500
Subject: [docs] Unbelievable bug
Message-ID: <CAJE4znCWYky4ePv1-pykhVAWD-HBGN4NsZwbVDmGQWE-PVZHeg@mail.gmail.com>

python cannot compute 1.2 + 0.6 2.7.3 and 3.2
tested on linux and windows. It returns 1.79999 for this sum

even worse, it cannot compute any sum like 1.2*(2^i) + 0.6*(2^i) !!!!!

>>> 1.2+0.6
1.7999999999999998
>>> !!!!!!!!!
SyntaxError: invalid syntax
>>> 1.2+0.6 == 1.8
False
>>> !!!!!!!!!!!!!!!!!
SyntaxError: invalid syntax
>>> 2.4+1.2
3.5999999999999996
>>> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131113/daa3022c/attachment-0001.html>

From brett_h_l at q.com  Thu Nov 14 18:59:40 2013
From: brett_h_l at q.com (bhl)
Date: Thu, 14 Nov 2013 11:59:40 -0600
Subject: [docs] pow(x, y[, z])
Message-ID: <52850F8C.1020503@q.com>

http://docs.python.org/3.3/library/functions.html#pow

for all versions

wrong syntax

-- 
bhl


From Bruce_Montague at symantec.com  Fri Nov 15 01:47:28 2013
From: Bruce_Montague at symantec.com (Bruce Montague)
Date: Thu, 14 Nov 2013 16:47:28 -0800
Subject: [docs] Spurios " a " in section 6.9 of Lang Ref Manual.
Message-ID: <402AE8E1D2FBB84ABE4AB494310DC4A962F28B4148@TUS1XCHEVSPIN33.SYMC.SYMANTEC.COM>

Hi, docs at python.org. I'm reporting a minor typo (spurious " a ") in section 6.9 of the Python Language Reference, web page at:

 http://docs.python.org/3.4/reference/expressions.html#index-63


7th paragraph from the bottom of Section 6.9, 3rd sentence:

".for which?in?tests whether a the dictionary has."   -->   "".for which in tests whether the dictionary has."   


Thanks,

-bruce


From marek.b.rudnicki at gmail.com  Mon Nov 18 12:11:14 2013
From: marek.b.rudnicki at gmail.com (Marek Rudnicki)
Date: Mon, 18 Nov 2013 12:11:14 +0100
Subject: [docs] Spelling error in tutorial
Message-ID: <CAAzBOacUEhGVCbcPZObKLhRCLtNMoTjRWefo7U5hcXxbNp4H0g@mail.gmail.com>

Hello,

On page http://docs.python.org/2/tutorial/introduction.html in section
3.1.3 it says "This lead to very much confusion". It should say "This led
to very much confusion" instead.

Please see http://www.grammar-monster.com/easily_confused/lead_led.htm if
you have any doubts.

Kind regards,

Marek Rudnicki
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131118/2ac314c1/attachment-0001.html>

From Oisin.OCuanachain at lsi.com  Mon Nov 18 12:51:57 2013
From: Oisin.OCuanachain at lsi.com (OCuanachain, Oisin (Oisin))
Date: Mon, 18 Nov 2013 11:51:57 +0000
Subject: [docs] Bug in tutorial
Message-ID: <43babc3e60bf4fa39c17f809552e33c1@BN1PR07MB440.namprd07.prod.outlook.com>

Hi,

There appears to an error in the section http://docs.python.org/2/tutorial/errors.html#handling-exceptions of the tutorial. It states:

If an exception occurs which does not match the exception named in the except clause, it is passed on to outer try<http://docs.python.org/2/reference/compound_stmts.html#try> statements; if no handler is found, it is an unhandled exception and execution stops with a message as shown above.

The problem I see is with the final clause, 'with a message as shown above'. It is not clear to me that there is any such message, what does this refer to ? The hypothetical message that would ensue should the user run the preceding code snippet with a particular input maybe ? Or something else ? As I say, this is far from clear, to me at any rate.

Ois?n
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131118/6e95a07a/attachment-0001.html>

From report at bugs.python.org  Tue Nov 19 20:19:33 2013
From: report at bugs.python.org (Dustin Haffner)
Date: Tue, 19 Nov 2013 19:19:33 +0000
Subject: [docs] [issue18032] set methods should specify whether they
	consume	iterators "lazily"
In-Reply-To: <1369223923.83.0.620034016791.issue18032@psf.upfronthosting.co.za>
Message-ID: <1384888772.96.0.548609324586.issue18032@psf.upfronthosting.co.za>


Dustin Haffner added the comment:

I've made an attempt at patching set_issubset() to match the Python from Raymond's message. I've rearranged the set_issubset function so that it checks for a set/frozenset, dict, or iterable in that order. In the iterable case it will create a temporary set and add elements to it as it consumes them from the iterable, returning early when possible.

This is my first patch, please let me know how I may improve it!

----------
keywords: +patch
nosy: +dhaffner
Added file: http://bugs.python.org/file32706/issubset_improvement.patch

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

From report at bugs.python.org  Tue Nov 19 21:38:36 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 19 Nov 2013 20:38:36 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1384893516.76.0.508358908306.issue15204@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Could anyone please review the patch?

----------

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

From report at bugs.python.org  Tue Nov 19 22:22:46 2013
From: report at bugs.python.org (Guido van Rossum)
Date: Tue, 19 Nov 2013 21:22:46 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1384896166.04.0.173551690427.issue15204@psf.upfronthosting.co.za>


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


----------
nosy:  -gvanrossum, jackjansen

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

From report at bugs.python.org  Tue Nov 19 22:58:11 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 19 Nov 2013 21:58:11 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1384898291.2.0.482492945849.issue15204@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Updated patch addresses Victor's comments.

----------
Added file: http://bugs.python.org/file32708/deprecate-U-mode_2.patch

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

From report at bugs.python.org  Wed Nov 20 02:15:28 2013
From: report at bugs.python.org (Julian Gindi)
Date: Wed, 20 Nov 2013 01:15:28 +0000
Subject: [docs] [issue18566] In unittest.TestCase docs for setUp() and
	tearDown()	don't mention AssertionError
In-Reply-To: <1374901937.1.0.747872580847.issue18566@psf.upfronthosting.co.za>
Message-ID: <1384910128.54.0.111114670341.issue18566@psf.upfronthosting.co.za>


Julian Gindi added the comment:

I did some further testing and it seems that you are right, testcase.SkipTest() never causes an error in setUp or tearDown but "raise AssertionError" does (even in setUp or tearDown). I went ahead and made relevant documentation changes, let me know what you think.

----------
keywords: +patch
nosy: +Julian.Gindi
Added file: http://bugs.python.org/file32716/issue18566.patch

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

From report at bugs.python.org  Wed Nov 20 08:49:59 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 20 Nov 2013 07:49:59 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1384933799.4.0.178632742387.issue15204@psf.upfronthosting.co.za>


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


Removed file: http://bugs.python.org/file26198/deprecate-U-mode-stage2.patch

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

From report at bugs.python.org  Wed Nov 20 08:50:58 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 20 Nov 2013 07:50:58 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1384933858.79.0.539530070981.issue15204@psf.upfronthosting.co.za>


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


Removed file: http://bugs.python.org/file27345/deprecate-U-mode-stage1_2.patch

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

From report at bugs.python.org  Wed Nov 20 21:20:25 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 20 Nov 2013 20:20:25 +0000
Subject: [docs] [issue19669] remove mention of the old LaTeX docs
Message-ID: <1384978825.66.0.587760682432.issue19669@psf.upfronthosting.co.za>


New submission from Antoine Pitrou:

The devguide mentions the old LaTeX doc format:
http://docs.python.org/devguide/documenting.html#differences-to-the-latex-markup

This doesn't really sound useful anymore, so many years later.

----------
assignee: docs at python
components: Devguide, Documentation
messages: 203527
nosy: docs at python, ezio.melotti, fdrake, georg.brandl, pitrou
priority: low
severity: normal
status: open
title: remove mention of the old LaTeX docs

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

From report at bugs.python.org  Wed Nov 20 21:23:07 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 20 Nov 2013 20:23:07 +0000
Subject: [docs] [issue19669] remove mention of the old LaTeX docs
In-Reply-To: <1384978825.66.0.587760682432.issue19669@psf.upfronthosting.co.za>
Message-ID: <1384978987.88.0.686066233988.issue19669@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

SGTM.

----------
keywords: +easy
stage:  -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Wed Nov 20 22:49:29 2013
From: report at bugs.python.org (Sworddragon)
Date: Wed, 20 Nov 2013 21:49:29 +0000
Subject: [docs] [issue19672] Listing of all exceptions for every function
Message-ID: <1384984169.87.0.182568254733.issue19672@psf.upfronthosting.co.za>


New submission from Sworddragon:

Currently the documentation does sometimes say about specific exceptions but most times not. As I'm often catching exceptions to ensure a high stability this gets a little difficult. For example print() can trigger a BrokenPipeError and the most file functions like flush() can trigger other related IOError's.

So I would like to see something like a listing on every function which contains all exceptions that may appear. Also there are some special cases like close(). For example it can trigger an IOError too if there are pending write operations due to an implicit call of flush(). But if the file object is opened in read-only mode or there are no write operations this can't happen. Maybe such additional information can be added too.

----------
assignee: docs at python
components: Documentation
messages: 203535
nosy: Sworddragon, docs at python
priority: normal
severity: normal
status: open
title: Listing of all exceptions for every function
type: enhancement
versions: Python 2.7, Python 3.3

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

From report at bugs.python.org  Wed Nov 20 23:39:38 2013
From: report at bugs.python.org (Martin Panter)
Date: Wed, 20 Nov 2013 22:39:38 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1384987178.07.0.959544181641.issue15204@psf.upfronthosting.co.za>


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


----------
nosy: +vadmium

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

From report at bugs.python.org  Thu Nov 21 00:04:09 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 20 Nov 2013 23:04:09 +0000
Subject: [docs] [issue19672] Listing of all exceptions for every function
In-Reply-To: <1384984169.87.0.182568254733.issue19672@psf.upfronthosting.co.za>
Message-ID: <1384988649.73.0.370265228503.issue19672@psf.upfronthosting.co.za>


R. David Murray added the comment:

This is not something we are going to do.  We don't know what every exception is that every function can raise.

Adding mentions of unusual special cases that aren't currently documented would be OK, though.  You should open specific issues for things you think should be clarified.

----------
nosy: +r.david.murray
resolution:  -> rejected
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Thu Nov 21 00:21:58 2013
From: report at bugs.python.org (Sworddragon)
Date: Wed, 20 Nov 2013 23:21:58 +0000
Subject: [docs] [issue19672] Listing of all exceptions for every function
In-Reply-To: <1384984169.87.0.182568254733.issue19672@psf.upfronthosting.co.za>
Message-ID: <1384989718.5.0.51375065517.issue19672@psf.upfronthosting.co.za>


Sworddragon added the comment:

I'm fine with this decision as it will be really much work. But this also means programming with Python isn't considered for high stability applications - due to the lack of important informations in the documentation.

An alternate way would be to rely on error codes and abandon exceptions. But this would be a case for a PEP and I'm assuming that it is absolutely unrealistic that this will be changed.

----------

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

From report at bugs.python.org  Thu Nov 21 00:30:47 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 20 Nov 2013 23:30:47 +0000
Subject: [docs] [issue19672] Listing of all exceptions for every function
In-Reply-To: <1384984169.87.0.182568254733.issue19672@psf.upfronthosting.co.za>
Message-ID: <1384990247.22.0.790464448967.issue19672@psf.upfronthosting.co.za>


R. David Murray added the comment:

If switching to error codes would solve your problem, then catching Exception at appropriate places should also solve your problem.

----------

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

From report at bugs.python.org  Thu Nov 21 00:35:16 2013
From: report at bugs.python.org (Sworddragon)
Date: Wed, 20 Nov 2013 23:35:16 +0000
Subject: [docs] [issue19672] Listing of all exceptions for every function
In-Reply-To: <1384984169.87.0.182568254733.issue19672@psf.upfronthosting.co.za>
Message-ID: <1384990516.06.0.306716455738.issue19672@psf.upfronthosting.co.za>


Sworddragon added the comment:

Correct, but the second part of my last message was just my opinion that I would prefer error codes over exceptions because it implies already a completed documentation for this part due to return codes/error arguments/other potential ways.

----------

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

From report at bugs.python.org  Thu Nov 21 09:12:32 2013
From: report at bugs.python.org (mpb)
Date: Thu, 21 Nov 2013 08:12:32 +0000
Subject: [docs] [issue17145] memoryview(array.array)
In-Reply-To: <1360170754.31.0.614797074916.issue17145@psf.upfronthosting.co.za>
Message-ID: <1385021552.02.0.5653562219.issue17145@psf.upfronthosting.co.za>


Changes by mpb <mpb.mail at gmail.com>:


----------
nosy: +mpb

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

From report at bugs.python.org  Thu Nov 21 13:29:46 2013
From: report at bugs.python.org (Bohuslav "Slavek" Kabrda)
Date: Thu, 21 Nov 2013 12:29:46 +0000
Subject: [docs] [issue19680] Help missing for exec and print
Message-ID: <1385036985.98.0.128644104733.issue19680@psf.upfronthosting.co.za>


New submission from Bohuslav "Slavek" Kabrda:

Steps to reproduce:

[bkabrda at zizalka python]$ python
>>> help()
help> keywords
<snip>
# prints lots of keywords including "print" and "exec"
</snip>
help> print
no documentation found for 'print'


So either keywords should not list "print" and "exec" or the documentation for them should be built. IIUC, the help for these should be part of pydoc_data/topics.py, which gets generated by Doc/tools/sphinxext/pyspecific.py. However, in revision [1] some topics got removed ("print" and "exec" amongst them) without the commit message saying anything helpful. Either way, this is inconsistent and should be fixed (assuming that Python 2.7 is still supposed to get this sort of fixes).

Thanks.

[1] http://hg.python.org/cpython/rev/76aa98f69251

----------
assignee: docs at python
components: Documentation
messages: 203625
nosy: bkabrda, docs at python
priority: normal
severity: normal
status: open
title: Help missing for exec and print
versions: Python 2.7

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

From report at bugs.python.org  Fri Nov 22 11:57:19 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Fri, 22 Nov 2013 10:57:19 +0000
Subject: [docs] [issue19557] ast - docs for every node type are missing
In-Reply-To: <1384239144.67.0.857427270426.issue19557@psf.upfronthosting.co.za>
Message-ID: <1385117839.78.0.165915994807.issue19557@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

Neither you nor docs answer the question when Assign node gets Tuple as argument, when List and when Subscript.

While it is obvious to you, I personally don't know what a Subscript is. This is the kind of stuff that I'd like to see documented.

----------

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

From report at bugs.python.org  Fri Nov 22 15:21:49 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 22 Nov 2013 14:21:49 +0000
Subject: [docs] [issue19691] Weird wording in RuntimeError doc
Message-ID: <1385130108.97.0.877442110994.issue19691@psf.upfronthosting.co.za>


New submission from Antoine Pitrou:

The RuntimeError documentation has a strange sentence embedded in it:

"""This exception is mostly a relic from a previous version of the interpreter; it is not used very much any more"""

http://docs.python.org/dev/library/exceptions.html#RuntimeError

That's quite wrong. RuntimeError may not be raised inside the interpreter core, but it's raised by a bunch of stdlib modules.

----------
assignee: docs at python
components: Documentation
messages: 203763
nosy: docs at python, neologix, pitrou
priority: normal
severity: normal
status: open
title: Weird wording in RuntimeError doc
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Nov 22 16:07:20 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 22 Nov 2013 15:07:20 +0000
Subject: [docs] [issue19669] remove mention of the old LaTeX docs
In-Reply-To: <1384978825.66.0.587760682432.issue19669@psf.upfronthosting.co.za>
Message-ID: <1385132840.81.0.176686362943.issue19669@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Done in 33f58b469a4d (forgot to mention the issue id there).

----------
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Fri Nov 22 17:45:05 2013
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 22 Nov 2013 16:45:05 +0000
Subject: [docs] [issue19710] Make sure documentation for PEP 451 is finished
Message-ID: <1385138705.49.0.0614847614933.issue19710@psf.upfronthosting.co.za>


New submission from Brett Cannon:

This includes both importlib.rst and docstrings for various methods.

----------
assignee: docs at python
components: Documentation
messages: 203804
nosy: brett.cannon, docs at python, eric.snow, ncoghlan
priority: normal
severity: normal
stage: needs patch
status: open
title: Make sure documentation for PEP 451 is finished
versions: Python 3.4

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

From report at bugs.python.org  Fri Nov 22 21:04:34 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 22 Nov 2013 20:04:34 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <3dR7rx4nKrz7LkK@mail.python.org>


Roundup Robot added the comment:

New changeset 9192c0798a90 by Zachary Ware in branch '3.3':
Issue #18326: Clarify that list.sort's arguments are keyword-only.
http://hg.python.org/cpython/rev/9192c0798a90

New changeset 3f1c332c5e2e by Zachary Ware in branch 'default':
Issue #18326: merge with 3.3
http://hg.python.org/cpython/rev/3f1c332c5e2e

----------
nosy: +python-dev

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

From report at bugs.python.org  Fri Nov 22 21:06:42 2013
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 22 Nov 2013 20:06:42 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1385150802.34.0.902506168801.issue18326@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


----------
assignee: docs at python -> zach.ware
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Fri Nov 22 21:49:33 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 22 Nov 2013 20:49:33 +0000
Subject: [docs] [issue19680] Help missing for exec and print
In-Reply-To: <1385036985.98.0.128644104733.issue19680@psf.upfronthosting.co.za>
Message-ID: <1385153373.6.0.209812004448.issue19680@psf.upfronthosting.co.za>


?ric Araujo added the comment:

The changeset you refer to may be a backport of a Python 3 changeset, where print and exec are not keywords but functions (adding Sandro to nosy so that he may confirm).

Would you like to make a patch to fix this in 2.7?  http://docs.python.org/devguide contains more info about that.

----------
nosy: +eric.araujo, sandro.tosi

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

From report at bugs.python.org  Fri Nov 22 21:56:24 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 22 Nov 2013 20:56:24 +0000
Subject: [docs] [issue19639] Improve re match objects display
In-Reply-To: <1384767316.36.0.259346591403.issue19639@psf.upfronthosting.co.za>
Message-ID: <1385153784.31.0.379003438304.issue19639@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Good catch, thanks!

----------
nosy: +eric.araujo

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

From report at bugs.python.org  Fri Nov 22 21:58:48 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 22 Nov 2013 20:58:48 +0000
Subject: [docs] [issue19627] python open built-in function - "updating" is
	not defined
In-Reply-To: <1384627981.21.0.789966534785.issue19627@psf.upfronthosting.co.za>
Message-ID: <1385153928.33.0.0476287630947.issue19627@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Would you like to propose a patch to the documentation?  It?s possible that ?updating? is explained in one place but not everywhere (doc for open, doc for io, doc about file objects).

----------
nosy: +eric.araujo

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

From report at bugs.python.org  Fri Nov 22 22:00:30 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 22 Nov 2013 21:00:30 +0000
Subject: [docs] [issue19620] tokenize documentation contains typos (argment
	instead	of argument)
In-Reply-To: <1384569112.62.0.796047767365.issue19620@psf.upfronthosting.co.za>
Message-ID: <1385154030.65.0.0766190311472.issue19620@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Thanks for catching this, would you like to make a patch?
http://docs.python.org/devguide gives help to do that.

----------
nosy: +eric.araujo

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

From report at bugs.python.org  Sat Nov 23 03:29:28 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 23 Nov 2013 02:29:28 +0000
Subject: [docs] [issue19731] Fix copyright footer
Message-ID: <1385173768.12.0.946242825352.issue19731@psf.upfronthosting.co.za>


New submission from Antoine Pitrou:

Marc-Andr? pointed out that the copyright footer has the wrong date. See attached patch.

----------
assignee: docs at python
components: Documentation
files: copyright.patch
keywords: patch
messages: 203959
nosy: docs at python, lemburg, pitrou
priority: low
severity: normal
status: open
title: Fix copyright footer
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32791/copyright.patch

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

From report at bugs.python.org  Sat Nov 23 03:31:00 2013
From: report at bugs.python.org (STINNER Victor)
Date: Sat, 23 Nov 2013 02:31:00 +0000
Subject: [docs] [issue19731] Fix copyright footer
In-Reply-To: <1385173768.12.0.946242825352.issue19731@psf.upfronthosting.co.za>
Message-ID: <1385173860.28.0.0571778809771.issue19731@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> Marc-Andr? pointed out that the copyright footer has the wrong date.

In an email? Could you please give the reference to the mail?

(I never understood these copyright dates, so it may help me to understand :-))

----------
nosy: +haypo

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

From report at bugs.python.org  Sat Nov 23 03:31:58 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 23 Nov 2013 02:31:58 +0000
Subject: [docs] [issue19731] Fix copyright footer
In-Reply-To: <1385173768.12.0.946242825352.issue19731@psf.upfronthosting.co.za>
Message-ID: <1385173918.96.0.564951915064.issue19731@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

See https://mail.python.org/pipermail/python-legal-sig/2013-November/000059.html

----------

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

From report at bugs.python.org  Sat Nov 23 17:51:01 2013
From: report at bugs.python.org (Zahari Dim)
Date: Sat, 23 Nov 2013 16:51:01 +0000
Subject: [docs] [issue19737] Documentation of globals() and locals() should
	be	improved
Message-ID: <1385225461.09.0.671908077084.issue19737@psf.upfronthosting.co.za>


New submission from Zahari Dim:

The globals() notification states:

Return a dictionary representing the current global symbol table.[...]

This doc and the fact that globals() is called as a function made me think that globals() returns a copy of the global namespace dict, rather than an object that could be used to actually modify the namespace. I don't find obvious the meaning of "representing" in this context.

This of course led to a very nasty and sneaky bug in my code.

The docs of locals() don't seem clear to me either, thought at least it seems to imply that it is actually modifying the namespace.

----------
assignee: docs at python
components: Documentation
messages: 204052
nosy: Zahari.Dim, docs at python
priority: normal
severity: normal
status: open
title: Documentation of globals() and locals() should be improved

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

From report at bugs.python.org  Sat Nov 23 18:06:39 2013
From: report at bugs.python.org (R. David Murray)
Date: Sat, 23 Nov 2013 17:06:39 +0000
Subject: [docs] [issue19737] Documentation of globals() and locals() should
	be	improved
In-Reply-To: <1385225461.09.0.671908077084.issue19737@psf.upfronthosting.co.za>
Message-ID: <1385226399.55.0.593185094982.issue19737@psf.upfronthosting.co.za>


R. David Murray added the comment:

We've tried improving the locals docs several times.  Modifying it is not "safe", in the sense that what happens when you do is not defined by the language.  Which locals docs were you looking at?

I agree that 'representing' is not as clear as would be optimal in the globals description.  Again, which bit of the docs are you looking at?

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

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

From report at bugs.python.org  Sat Nov 23 19:27:43 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 23 Nov 2013 18:27:43 +0000
Subject: [docs] [issue19639] Improve re match objects display
In-Reply-To: <1384767316.36.0.259346591403.issue19639@psf.upfronthosting.co.za>
Message-ID: <3dRjfk0mCMz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset bbfc559f7190 by Ezio Melotti in branch 'default':
#19639: update the repr of the match objects in the docs.  Patch by Claudiu Popa.
http://hg.python.org/cpython/rev/bbfc559f7190

----------
nosy: +python-dev

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

From report at bugs.python.org  Sat Nov 23 19:28:31 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 23 Nov 2013 18:28:31 +0000
Subject: [docs] [issue19639] Improve re match objects display
In-Reply-To: <1384767316.36.0.259346591403.issue19639@psf.upfronthosting.co.za>
Message-ID: <1385231311.44.0.000641556324659.issue19639@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!

----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sat Nov 23 19:32:26 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Sat, 23 Nov 2013 18:32:26 +0000
Subject: [docs] [issue19557] ast - docs for every node type are missing
In-Reply-To: <1384239144.67.0.857427270426.issue19557@psf.upfronthosting.co.za>
Message-ID: <1385231546.0.0.763481789677.issue19557@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

http://stackoverflow.com/questions/8370132/what-syntax-is-represented-by-an-extslice-node-in-pythons-ast

----------

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

From report at bugs.python.org  Sat Nov 23 20:47:20 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 23 Nov 2013 19:47:20 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1385236040.11.0.896221700088.issue15204@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Updated patch addresses Ezio's comments.

----------
Added file: http://bugs.python.org/file32809/deprecate-U-mode_3.patch

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

From report at bugs.python.org  Sat Nov 23 20:53:07 2013
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Sat, 23 Nov 2013 19:53:07 +0000
Subject: [docs] [issue19710] Make sure documentation for PEP 451 is finished
In-Reply-To: <1385138705.49.0.0614847614933.issue19710@psf.upfronthosting.co.za>
Message-ID: <1385236387.52.0.0187869180701.issue19710@psf.upfronthosting.co.za>


Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com>:


----------
nosy: +Arfrever

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

From report at bugs.python.org  Sat Nov 23 21:13:13 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 23 Nov 2013 20:13:13 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <3dRm0T0MT1z7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 70bd6f7e013b by Serhiy Storchaka in branch 'default':
Issue #15204: Deprecated the 'U' mode in file-like objects.
http://hg.python.org/cpython/rev/70bd6f7e013b

----------
nosy: +python-dev

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

From report at bugs.python.org  Sat Nov 23 21:14:27 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 23 Nov 2013 20:14:27 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1385237667.53.0.129800442387.issue15204@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thanks Victor and Ezio for the reviews.

----------

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

From report at bugs.python.org  Sat Nov 23 23:36:57 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 23 Nov 2013 22:36:57 +0000
Subject: [docs] [issue19465] selectors: provide a helper to choose a
	selector using	constraints
In-Reply-To: <1383258981.48.0.274242938687.issue19465@psf.upfronthosting.co.za>
Message-ID: <1385246217.43.0.701550374977.issue19465@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python

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

From report at bugs.python.org  Sun Nov 24 00:37:04 2013
From: report at bugs.python.org (Zahari Dim)
Date: Sat, 23 Nov 2013 23:37:04 +0000
Subject: [docs] [issue19737] Documentation of globals() and locals() should
	be	improved
In-Reply-To: <1385225461.09.0.671908077084.issue19737@psf.upfronthosting.co.za>
Message-ID: <1385249824.3.0.620368773578.issue19737@psf.upfronthosting.co.za>


Zahari Dim added the comment:

I am looking at the docs of the built-in functions:

http://docs.python.org/2/library/functions.html

----------

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

From report at bugs.python.org  Sun Nov 24 01:01:25 2013
From: report at bugs.python.org (Martin Panter)
Date: Sun, 24 Nov 2013 00:01:25 +0000
Subject: [docs] [issue19737] Documentation of globals() and locals() should
	be	improved
In-Reply-To: <1385225461.09.0.671908077084.issue19737@psf.upfronthosting.co.za>
Message-ID: <1385251285.46.0.637446377469.issue19737@psf.upfronthosting.co.za>


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


----------
nosy: +vadmium

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

From report at bugs.python.org  Sun Nov 24 01:53:57 2013
From: report at bugs.python.org (Martin Panter)
Date: Sun, 24 Nov 2013 00:53:57 +0000
Subject: [docs] [issue19691] Weird wording in RuntimeError doc
In-Reply-To: <1385130108.97.0.877442110994.issue19691@psf.upfronthosting.co.za>
Message-ID: <1385254437.79.0.745871001199.issue19691@psf.upfronthosting.co.za>


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


----------
nosy: +vadmium

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

From report at bugs.python.org  Sun Nov 24 16:19:18 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 24 Nov 2013 15:19:18 +0000
Subject: [docs] [issue15759] "make suspicious" doesn't display instructions
	in case	of failure
In-Reply-To: <1345613663.78.0.519613331574.issue15759@psf.upfronthosting.co.za>
Message-ID: <1385306358.91.0.689977133745.issue15759@psf.upfronthosting.co.za>


Changes by Ezio Melotti <ezio.melotti at gmail.com>:


----------
keywords: +easy
stage: commit review -> patch review
versions: +Python 3.4 -Python 3.2

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

From report at bugs.python.org  Sun Nov 24 16:36:29 2013
From: report at bugs.python.org (Brett Cannon)
Date: Sun, 24 Nov 2013 15:36:29 +0000
Subject: [docs] [issue19557] ast - docs for every node type are missing
In-Reply-To: <1384239144.67.0.857427270426.issue19557@psf.upfronthosting.co.za>
Message-ID: <1385307389.95.0.589704379906.issue19557@psf.upfronthosting.co.za>


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


----------
nosy:  -brett.cannon

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

From report at bugs.python.org  Sun Nov 24 22:13:49 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 24 Nov 2013 21:13:49 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <3dSPHw3wD8z7Ljn@mail.python.org>


Roundup Robot added the comment:

New changeset 694e2708b4a8 by Serhiy Storchaka in branch 'default':
Issue #15204: Silence and check the 'U' mode deprecation warnings in tests.
http://hg.python.org/cpython/rev/694e2708b4a8

----------

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

From report at bugs.python.org  Sun Nov 24 22:15:30 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 24 Nov 2013 21:15:30 +0000
Subject: [docs] [issue15204] Deprecate the 'U' open mode
In-Reply-To: <1340792991.22.0.497199331706.issue15204@psf.upfronthosting.co.za>
Message-ID: <1385327730.76.0.454385017232.issue15204@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Mon Nov 25 04:16:28 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 25 Nov 2013 03:16:28 +0000
Subject: [docs] [issue19620] tokenize documentation contains typos (argment
	instead	of argument)
In-Reply-To: <1384569112.62.0.796047767365.issue19620@psf.upfronthosting.co.za>
Message-ID: <3dSYLL4X2Fz7LmY@mail.python.org>


Roundup Robot added the comment:

New changeset 9b170d74a0a2 by Ezio Melotti in branch '2.7':
#19620: Fix typo in docstring (noticed by Christopher Welborn).
http://hg.python.org/cpython/rev/9b170d74a0a2

New changeset 3f99564b712e by Ezio Melotti in branch '3.3':
#19620: Fix typo in docstring (noticed by Christopher Welborn).
http://hg.python.org/cpython/rev/3f99564b712e

New changeset 0d5da548b80a by Ezio Melotti in branch 'default':
#19620: merge with 3.3.
http://hg.python.org/cpython/rev/0d5da548b80a

----------
nosy: +python-dev

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

From report at bugs.python.org  Mon Nov 25 04:17:16 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 25 Nov 2013 03:17:16 +0000
Subject: [docs] [issue19620] tokenize documentation contains typos (argment
	instead	of argument)
In-Reply-To: <1384569112.62.0.796047767365.issue19620@psf.upfronthosting.co.za>
Message-ID: <1385349436.6.0.644029944011.issue19620@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type:  -> enhancement

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

From report at bugs.python.org  Mon Nov 25 04:23:46 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 25 Nov 2013 03:23:46 +0000
Subject: [docs] [issue19627] python open built-in function - "updating" is
	not defined
In-Reply-To: <1384627981.21.0.789966534785.issue19627@psf.upfronthosting.co.za>
Message-ID: <1385349826.58.0.571313695955.issue19627@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Is the doc in 3.4 (http://docs.python.org/3.4/library/functions.html#open) clear enough?

If so it could be backported on 2.7/3.3.

----------
nosy: +ezio.melotti
type:  -> enhancement

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

From report at bugs.python.org  Mon Nov 25 04:28:26 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 25 Nov 2013 03:28:26 +0000
Subject: [docs] [issue19632] doc build warning
In-Reply-To: <1384699064.41.0.714714605877.issue19632@psf.upfronthosting.co.za>
Message-ID: <1385350106.56.0.490222093759.issue19632@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

See #14489.

----------
nosy: +ezio.melotti, georg.brandl

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

From report at bugs.python.org  Mon Nov 25 04:45:56 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 25 Nov 2013 03:45:56 +0000
Subject: [docs] [issue19680] Help missing for exec and print
In-Reply-To: <1385036985.98.0.128644104733.issue19680@psf.upfronthosting.co.za>
Message-ID: <1385351156.66.0.999096388819.issue19680@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Attached patch seems to fix the issue.

----------
assignee: docs at python -> ezio.melotti
keywords: +patch
nosy: +ezio.melotti, georg.brandl
stage:  -> patch review
type:  -> behavior
Added file: http://bugs.python.org/file32826/issue19680.diff

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

From report at bugs.python.org  Mon Nov 25 04:46:47 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 25 Nov 2013 03:46:47 +0000
Subject: [docs] [issue19691] Weird wording in RuntimeError doc
In-Reply-To: <1385130108.97.0.877442110994.issue19691@psf.upfronthosting.co.za>
Message-ID: <1385351207.5.0.377281117022.issue19691@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

So maybe it can just be removed?

----------
keywords: +easy
nosy: +ezio.melotti
stage:  -> needs patch

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

From report at bugs.python.org  Mon Nov 25 04:47:59 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 25 Nov 2013 03:47:59 +0000
Subject: [docs] [issue19710] Make sure documentation for PEP 451 is finished
In-Reply-To: <1385138705.49.0.0614847614933.issue19710@psf.upfronthosting.co.za>
Message-ID: <1385351279.07.0.846513328355.issue19710@psf.upfronthosting.co.za>


Changes by Ezio Melotti <ezio.melotti at gmail.com>:


----------
nosy: +ezio.melotti

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

From report at bugs.python.org  Mon Nov 25 05:41:18 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Mon, 25 Nov 2013 04:41:18 +0000
Subject: [docs] [issue19762] Incorrect function documentation
	of	_get_object_traceback and _get_traces in _tracemalloc module
Message-ID: <1385354478.04.0.931471819915.issue19762@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

>>> import _tracemalloc
>>> _tracemalloc._get_object_traceback.__doc__
'get_object_traceback(obj)\n\nGet the traceback where the Python object obj was allocated.\nReturn a tuple of (filename: str, lineno: int) tuples.\n\nReturn None if the tracemalloc module is disabled or did not\ntrace the allocation of the object.'
>>> _tracemalloc._get_traces.__doc__
'get_traces() -> list\n\nGet traces of all memory blocks allocated by Python.\nReturn a list of (size: int, traceback: tuple) tuples.\ntraceback is a tuple of (filename: str, lineno: int) tuples.\n\nReturn an empty list if the tracemalloc module is disabled.'

----------
assignee: docs at python
components: Documentation, Extension Modules
files: fix_doc__tracemalloc.patch
keywords: patch
messages: 204293
nosy: docs at python, haypo, vajrasky
priority: normal
severity: normal
status: open
title: Incorrect function documentation of _get_object_traceback and _get_traces in _tracemalloc module
versions: Python 3.4
Added file: http://bugs.python.org/file32827/fix_doc__tracemalloc.patch

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

From report at bugs.python.org  Mon Nov 25 07:55:21 2013
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 25 Nov 2013 06:55:21 +0000
Subject: [docs] [issue19691] Weird wording in RuntimeError doc
In-Reply-To: <1385130108.97.0.877442110994.issue19691@psf.upfronthosting.co.za>
Message-ID: <1385362520.99.0.627586773158.issue19691@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I think so.

----------
nosy: +georg.brandl

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

From report at bugs.python.org  Mon Nov 25 07:57:03 2013
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 25 Nov 2013 06:57:03 +0000
Subject: [docs] [issue19762] Incorrect function documentation
	of	_get_object_traceback and _get_traces in _tracemalloc module
In-Reply-To: <1385354478.04.0.931471819915.issue19762@psf.upfronthosting.co.za>
Message-ID: <1385362623.76.0.38518570203.issue19762@psf.upfronthosting.co.za>


Georg Brandl added the comment:

LGTM.

----------
nosy: +georg.brandl

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

From report at bugs.python.org  Mon Nov 25 08:00:29 2013
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 25 Nov 2013 07:00:29 +0000
Subject: [docs] [issue19632] doc build warning
In-Reply-To: <1384699064.41.0.714714605877.issue19632@psf.upfronthosting.co.za>
Message-ID: <1385362829.06.0.863829225069.issue19632@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Well, there's no bug here: it's what you get when you call a library the same as a builtin :)

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

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

From report at bugs.python.org  Mon Nov 25 08:46:21 2013
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 25 Nov 2013 07:46:21 +0000
Subject: [docs] [issue19631] "exec" BNF in simple statements
In-Reply-To: <1384695347.39.0.482466517942.issue19631@psf.upfronthosting.co.za>
Message-ID: <1385365581.79.0.0524789543936.issue19631@psf.upfronthosting.co.za>


Georg Brandl added the comment:

That would be correct as a handwaving description, but it's wrong as a formal spec.  The "or_expr" already includes the possibility of a tuple; there is no "exec(" token etc.

----------
nosy: +georg.brandl
resolution:  -> works for me
status: open -> closed

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

From report at bugs.python.org  Mon Nov 25 08:50:55 2013
From: report at bugs.python.org (Bulwersator)
Date: Mon, 25 Nov 2013 07:50:55 +0000
Subject: [docs] [issue19627] python open built-in function - "updating" is
	not defined
In-Reply-To: <1384627981.21.0.789966534785.issue19627@psf.upfronthosting.co.za>
Message-ID: <1385365855.21.0.875628053242.issue19627@psf.upfronthosting.co.za>


Bulwersator added the comment:

yes, "open a disk file for updating (reading and writing)" is a good explanation

----------

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

From report at bugs.python.org  Mon Nov 25 08:52:31 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 25 Nov 2013 07:52:31 +0000
Subject: [docs] [issue19622] Default buffering for input and output pipes
	in	subprocess module
In-Reply-To: <1384579334.66.0.612676075589.issue19622@psf.upfronthosting.co.za>
Message-ID: <3dSgSt3Nnsz7LnP@mail.python.org>


Roundup Robot added the comment:

New changeset 0f0dc0276a7c by Georg Brandl in branch '3.3':
Closes #19622: clarify message about bufsize changes in 3.2.4 and 3.3.1.
http://hg.python.org/cpython/rev/0f0dc0276a7c

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Mon Nov 25 09:03:08 2013
From: report at bugs.python.org (Bohuslav "Slavek" Kabrda)
Date: Mon, 25 Nov 2013 08:03:08 +0000
Subject: [docs] [issue19680] Help missing for exec and print
In-Reply-To: <1385036985.98.0.128644104733.issue19680@psf.upfronthosting.co.za>
Message-ID: <1385366588.88.0.894505058814.issue19680@psf.upfronthosting.co.za>


Bohuslav "Slavek" Kabrda added the comment:

Seems that Ezio was faster :)
Yep, the attached patch does seem to solve the issue.

----------

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

From report at bugs.python.org  Mon Nov 25 09:34:46 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 25 Nov 2013 08:34:46 +0000
Subject: [docs] [issue19762] Incorrect function documentation
	of	_get_object_traceback and _get_traces in _tracemalloc module
In-Reply-To: <1385354478.04.0.931471819915.issue19762@psf.upfronthosting.co.za>
Message-ID: <3dShPd70M4z7Lmk@mail.python.org>


Roundup Robot added the comment:

New changeset 2e2ec595dc58 by Victor Stinner in branch 'default':
Close #19762: Fix name of _get_traces() and _get_object_traceback() function
http://hg.python.org/cpython/rev/2e2ec595dc58

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Mon Nov 25 18:13:19 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 25 Nov 2013 17:13:19 +0000
Subject: [docs] [issue19691] Weird wording in RuntimeError doc
In-Reply-To: <1385130108.97.0.877442110994.issue19691@psf.upfronthosting.co.za>
Message-ID: <1385399599.73.0.282643958894.issue19691@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

The mention was already there in 1994 (2ec96140a36b), under the following form:

+\begin{excdesc}{RuntimeError}
+  Raised when an error is detected that doesn't fall in any of the
+  other categories.  The associated value is a string indicating what
+  precisely went wrong.  (This exception is a relic from a previous
+  version of the interpreter; it is not used any more except by some
+  extension modules that haven't been converted to define their own
+  exceptions yet.)
+\end{excdesc}

It was changed slightly from being "a relic" to "mostly a relic" in 1997 (238a8b6096e1):

 \begin{excdesc}{RuntimeError}
   Raised when an error is detected that doesn't fall in any of the
   other categories.  The associated value is a string indicating what
-  precisely went wrong.  (This exception is a relic from a previous
-  version of the interpreter; it is not used any more except by some
-  extension modules that haven't been converted to define their own
-  exceptions yet.)
+  precisely went wrong.  (This exception is mostly a relic from a
+  previous version of the interpreter; it is not used very much any
+  more.)
 \end{excdesc}

----------

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

From report at bugs.python.org  Mon Nov 25 19:08:39 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 25 Nov 2013 18:08:39 +0000
Subject: [docs] [issue19691] Weird wording in RuntimeError doc
In-Reply-To: <1385130108.97.0.877442110994.issue19691@psf.upfronthosting.co.za>
Message-ID: <3dSx7p5Fqzz7LkR@mail.python.org>


Roundup Robot added the comment:

New changeset 313d9bb253bf by Antoine Pitrou in branch '2.7':
Issue #19691: remove outdated mention about RuntimeError
http://hg.python.org/cpython/rev/313d9bb253bf

----------
nosy: +python-dev

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

From report at bugs.python.org  Mon Nov 25 19:12:53 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 25 Nov 2013 18:12:53 +0000
Subject: [docs] [issue19691] Weird wording in RuntimeError doc
In-Reply-To: <1385130108.97.0.877442110994.issue19691@psf.upfronthosting.co.za>
Message-ID: <3dSxDh1vM9zN4d@mail.python.org>


Roundup Robot added the comment:

New changeset 6aeaaa614a19 by Antoine Pitrou in branch '3.3':
Issue #19691: remove outdated mention about RuntimeError
http://hg.python.org/cpython/rev/6aeaaa614a19

New changeset f4de1c5e381d by Antoine Pitrou in branch 'default':
Issue #19691: remove outdated mention about RuntimeError
http://hg.python.org/cpython/rev/f4de1c5e381d

----------

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

From report at bugs.python.org  Mon Nov 25 19:13:51 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 25 Nov 2013 18:13:51 +0000
Subject: [docs] [issue19691] Weird wording in RuntimeError doc
In-Reply-To: <1385130108.97.0.877442110994.issue19691@psf.upfronthosting.co.za>
Message-ID: <1385403231.15.0.344336751252.issue19691@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


----------
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Mon Nov 25 21:37:16 2013
From: report at bugs.python.org (Claudiu.Popa)
Date: Mon, 25 Nov 2013 20:37:16 +0000
Subject: [docs] [issue19778] Change re.compile display
Message-ID: <1385411836.14.0.1819060635.issue19778@psf.upfronthosting.co.za>


New submission from Claudiu.Popa:

Hello. I attached a minimal patch which fixes the re.compile display in documentation, after issue13592 was closed.

----------
assignee: docs at python
components: Documentation
files: sre_re.patch
keywords: patch
messages: 204402
nosy: Claudiu.Popa, docs at python, serhiy.storchaka
priority: normal
severity: normal
status: open
title: Change re.compile display
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file32841/sre_re.patch

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

From report at bugs.python.org  Mon Nov 25 21:47:19 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 25 Nov 2013 20:47:19 +0000
Subject: [docs] [issue19778] Change re.compile display
In-Reply-To: <1385411836.14.0.1819060635.issue19778@psf.upfronthosting.co.za>
Message-ID: <3dT0ft3PmFz7LjQ@mail.python.org>


Roundup Robot added the comment:

New changeset 5237e7da8a76 by Ezio Melotti in branch 'default':
#19778: fix a couple of re reprs in the documentation.
http://hg.python.org/cpython/rev/5237e7da8a76

----------
nosy: +python-dev

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

From report at bugs.python.org  Mon Nov 25 21:48:08 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 25 Nov 2013 20:48:08 +0000
Subject: [docs] [issue19778] Change re.compile display
In-Reply-To: <1385411836.14.0.1819060635.issue19778@psf.upfronthosting.co.za>
Message-ID: <1385412488.16.0.752240977744.issue19778@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Tue Nov 26 06:14:20 2013
From: report at bugs.python.org (Simon Weber)
Date: Tue, 26 Nov 2013 05:14:20 +0000
Subject: [docs] [issue19789] Improve wording of how to "undo" a call
	to	logging.disable(lvl)
Message-ID: <1385442860.38.0.88263802784.issue19789@psf.upfronthosting.co.za>


New submission from Simon Weber:

In http://bugs.python.org/issue14864, this line was added to the logging.disable docstring:

To undo the effect of a call to logging.disable(lvl), call logging.disable(logging.NOTSET).

To prevent misunderstanding, I propose that this line be changed to:

Calling logging.disable(logging.NOTSET) will undo all previous calls to logging.disable(lvl).


While the original change was an improvement, it's misleading. "undoing the effect of a call" reads as "undoing the effect of the last call", which implies a stack -- think of text editor "undo" functionality. In other words, the current documentation implies behavior like a context manager:

>>> import logging
# start with all logging enabled

>>> logging.disable(logging.CRITICAL)
#     all logging disabled

>>> logging.disable(logging.WARNING)
#         only CRITICAL enabled

>>> logging.disable(logging.NOTSET)
#     undo; all logging disabled

>>> logging.disable(logging.NOTSET)
# undo; all logging enabled

Since logging.disable is idempotent, we're not undoing *a call*, we're undoing *all calls*.

----------
assignee: docs at python
components: Documentation
messages: 204451
nosy: docs at python, eric.araujo, ezio.melotti, georg.brandl, simonmweber
priority: normal
severity: normal
status: open
title: Improve wording of how to "undo" a call to logging.disable(lvl)
type: enhancement

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

From report at bugs.python.org  Tue Nov 26 06:53:23 2013
From: report at bugs.python.org (Martin Panter)
Date: Tue, 26 Nov 2013 05:53:23 +0000
Subject: [docs] [issue19622] Default buffering for input and output pipes
	in	subprocess module
In-Reply-To: <1384579334.66.0.612676075589.issue19622@psf.upfronthosting.co.za>
Message-ID: <1385445203.92.0.595036748442.issue19622@psf.upfronthosting.co.za>


Martin Panter added the comment:

The updated text to ?suprocess.rst? is better, but now it looks like the whole paragraph fails to render at http://docs.python.org/dev/library/subprocess#subprocess.Popen. I have no idea about the syntax but maybe the blank line separating ?versionchanged? from its paragraph shouldn?t be there?

----------

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

From report at bugs.python.org  Tue Nov 26 08:25:48 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 26 Nov 2013 07:25:48 +0000
Subject: [docs] [issue19622] Default buffering for input and output pipes
	in	subprocess module
In-Reply-To: <1384579334.66.0.612676075589.issue19622@psf.upfronthosting.co.za>
Message-ID: <1385450748.17.0.775450479741.issue19622@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thanks, should be fixed now.

----------
nosy: +georg.brandl

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

From report at bugs.python.org  Tue Nov 26 10:05:49 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 26 Nov 2013 09:05:49 +0000
Subject: [docs] [issue19793] Formatting of True/Falsein in pathlib docs
Message-ID: <1385456749.57.0.871940933045.issue19793@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

The proposed patch improves formatting of True/False in pathlib documentation. "True" becomes "``True``" if it means True constant and "true" if it means true value.

----------
assignee: docs at python
components: Documentation
messages: 204461
nosy: chris.jerdonek, docs at python, pitrou, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Formatting of True/Falsein in pathlib docs
type: enhancement
versions: Python 3.4

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

From report at bugs.python.org  Tue Nov 26 10:06:10 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 26 Nov 2013 09:06:10 +0000
Subject: [docs] [issue19793] Formatting of True/Falsein in pathlib docs
In-Reply-To: <1385456749.57.0.871940933045.issue19793@psf.upfronthosting.co.za>
Message-ID: <1385456770.94.0.653375966189.issue19793@psf.upfronthosting.co.za>


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


----------
keywords: +patch
Added file: http://bugs.python.org/file32852/doc_pathlib_truefalse.patch

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

From report at bugs.python.org  Tue Nov 26 10:06:41 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 26 Nov 2013 09:06:41 +0000
Subject: [docs] [issue19793] Formatting of True/False in pathlib docs
In-Reply-To: <1385456749.57.0.871940933045.issue19793@psf.upfronthosting.co.za>
Message-ID: <1385456801.19.0.227100433062.issue19793@psf.upfronthosting.co.za>


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


----------
title: Formatting of True/Falsein in pathlib docs -> Formatting of True/False in pathlib docs

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

From report at bugs.python.org  Tue Nov 26 10:10:08 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 26 Nov 2013 09:10:08 +0000
Subject: [docs] [issue19794] Formatting of True/False in decimal docs
Message-ID: <1385457007.96.0.784815460487.issue19794@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

The proposed patch improves formatting of True/False in decimal documentation. "True/False" constants become "``True``/``False``".

----------
assignee: docs at python
components: Documentation
files: doc_decimal_truefalse.patch
keywords: patch
messages: 204462
nosy: docs at python, facundobatista, mark.dickinson, rhettinger, serhiy.storchaka, skrah
priority: normal
severity: normal
stage: patch review
status: open
title: Formatting of True/False in decimal docs
type: enhancement
versions: Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32853/doc_decimal_truefalse.patch

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

From report at bugs.python.org  Tue Nov 26 10:18:45 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 26 Nov 2013 09:18:45 +0000
Subject: [docs] [issue19795] Formatting of True/False in docs
Message-ID: <1385457525.93.0.980812903017.issue19795@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

The proposed patch improves formatting of True/False in the documentation. "True" becomes "``True``" if it means True constant and "true" if it means true value (in input arguments).

See also issue19793 and issue19794.

----------
assignee: docs at python
components: Documentation
files: doc_truefalse.patch
keywords: patch
messages: 204463
nosy: docs at python, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Formatting of True/False in docs
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32854/doc_truefalse.patch

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

From report at bugs.python.org  Tue Nov 26 10:59:18 2013
From: report at bugs.python.org (Alex Willmer)
Date: Tue, 26 Nov 2013 09:59:18 +0000
Subject: [docs] [issue19796] urllib2.HTTPError.reason is not documented as
	"Added in	2.7"
Message-ID: <1385459958.78.0.648544615764.issue19796@psf.upfronthosting.co.za>


New submission from Alex Willmer:

issue13211 added a .reason attribute to urllib2.HTTPError in Python 2.7, issue16634 documented it (http://hg.python.org/cpython/rev/deb60efd32eb).

The documentation for Python 2.7 doesn't mention that this attribute was added in that release. This (at least weakly) implies it's available to use in previous 2.x releases.

----------
assignee: docs at python
components: Documentation
files: HTTPError.reason-versionadded.diff
keywords: patch
messages: 204465
nosy: docs at python, moreati
priority: normal
severity: normal
status: open
title: urllib2.HTTPError.reason is not documented as "Added in 2.7"
type: behavior
versions: Python 2.7
Added file: http://bugs.python.org/file32855/HTTPError.reason-versionadded.diff

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

From report at bugs.python.org  Tue Nov 26 15:51:35 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Tue, 26 Nov 2013 14:51:35 +0000
Subject: [docs] [issue19557] ast - docs for every node type are missing
In-Reply-To: <1384239144.67.0.857427270426.issue19557@psf.upfronthosting.co.za>
Message-ID: <1385477495.78.0.784084255626.issue19557@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

https://greentreesnakes.readthedocs.org/en/latest/

----------

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

From report at bugs.python.org  Tue Nov 26 16:14:19 2013
From: report at bugs.python.org (Mark Dickinson)
Date: Tue, 26 Nov 2013 15:14:19 +0000
Subject: [docs] [issue19794] Formatting of True/False in decimal docs
In-Reply-To: <1385457007.96.0.784815460487.issue19794@psf.upfronthosting.co.za>
Message-ID: <1385478859.01.0.335212140472.issue19794@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

LGTM.

----------

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

From report at bugs.python.org  Tue Nov 26 16:33:52 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 26 Nov 2013 15:33:52 +0000
Subject: [docs] [issue19794] Formatting of True/False in decimal docs
In-Reply-To: <1385457007.96.0.784815460487.issue19794@psf.upfronthosting.co.za>
Message-ID: <3dTTfl3kTFz7Ln2@mail.python.org>


Roundup Robot added the comment:

New changeset 04c4f141874b by Serhiy Storchaka in branch '2.7':
Issue #19794: Improved markup for True/False constants.
http://hg.python.org/cpython/rev/04c4f141874b

New changeset c1d163203f21 by Serhiy Storchaka in branch '3.3':
Issue #19794: Improved markup for True/False constants.
http://hg.python.org/cpython/rev/c1d163203f21

New changeset 67e642f5ab5d by Serhiy Storchaka in branch 'default':
Issue #19794: Improved markup for True/False constants.
http://hg.python.org/cpython/rev/67e642f5ab5d

----------
nosy: +python-dev

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

From report at bugs.python.org  Tue Nov 26 16:34:51 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 26 Nov 2013 15:34:51 +0000
Subject: [docs] [issue19794] Formatting of True/False in decimal docs
In-Reply-To: <1385457007.96.0.784815460487.issue19794@psf.upfronthosting.co.za>
Message-ID: <1385480091.27.0.830123013648.issue19794@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thanks Mark.

----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Tue Nov 26 18:00:22 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 26 Nov 2013 17:00:22 +0000
Subject: [docs] [issue19793] Formatting of True/False in pathlib docs
In-Reply-To: <1385456749.57.0.871940933045.issue19793@psf.upfronthosting.co.za>
Message-ID: <1385485222.93.0.329585072264.issue19793@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I think :const:`True` is the norm, but the patch looks good to me regardless.

----------

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

From georg at python.org  Tue Nov 26 18:37:58 2013
From: georg at python.org (georg at python.org)
Date: Tue, 26 Nov 2013 17:37:58 -0000
Subject: [docs] Formatting of True/False in docs (issue 19795)
Message-ID: <20131126173758.16653.88382@psf.upfronthosting.co.za>

Looks good overall, see a few comments.


http://bugs.python.org/review/19795/diff/10113/Doc/library/dis.rst
File Doc/library/dis.rst (right):

http://bugs.python.org/review/19795/diff/10113/Doc/library/dis.rst#newcode272
Doc/library/dis.rst:272: line started by this opcode (if any), otherwise
None
None should also be ``-ified :)  another patch forthcoming?

http://bugs.python.org/review/19795/diff/10113/Doc/library/logging.rst
File Doc/library/logging.rst (right):

http://bugs.python.org/review/19795/diff/10113/Doc/library/logging.rst#newcode163
Doc/library/logging.rst:163: ``False``. If specified as True, stack
information is added to the logging
you missed a True here

http://bugs.python.org/review/19795/diff/10113/Doc/library/logging.rst#newcode881
Doc/library/logging.rst:881: ``False``. If specified as True, stack
information is added to the logging
another True missed

http://bugs.python.org/review/19795/diff/10113/Doc/library/sqlite3.rst
File Doc/library/sqlite3.rst (right):

http://bugs.python.org/review/19795/diff/10113/Doc/library/sqlite3.rst#newcode245
Doc/library/sqlite3.rst:245: can call this function with *flag* as true.
Afterwards, you will get tracebacks
"with flag as true" doesn't sound right -- this could be formulated
differently while you're at it

http://bugs.python.org/review/19795/diff/10113/Doc/reference/datamodel.rst
File Doc/reference/datamodel.rst (right):

http://bugs.python.org/review/19795/diff/10113/Doc/reference/datamodel.rst#newcode203
Doc/reference/datamodel.rst:203: These represent the truth values
``False`` and ``True``.  The two objects representing
this should not be code since it's not talking about the objects, but
the (Platonic ideal) values.

http://bugs.python.org/review/19795/

From georg at python.org  Tue Nov 26 18:38:34 2013
From: georg at python.org (georg at python.org)
Date: Tue, 26 Nov 2013 17:38:34 -0000
Subject: [docs] Formatting of True/False in pathlib docs (issue 19793)
Message-ID: <20131126173834.17364.73887@psf.upfronthosting.co.za>

LGTM.

http://bugs.python.org/review/19793/

From report at bugs.python.org  Tue Nov 26 18:39:13 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 26 Nov 2013 17:39:13 +0000
Subject: [docs] [issue19793] Formatting of True/False in pathlib docs
In-Reply-To: <1385456749.57.0.871940933045.issue19793@psf.upfronthosting.co.za>
Message-ID: <1385487552.98.0.497585585084.issue19793@psf.upfronthosting.co.za>


Georg Brandl added the comment:

``False`` is actually the preferred way, being shorter and easier to read (and we don't need to link to the documentation for False).

----------
nosy: +georg.brandl

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

From report at bugs.python.org  Tue Nov 26 19:28:54 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 26 Nov 2013 18:28:54 +0000
Subject: [docs] [issue19557] ast - docs for every node type are missing
In-Reply-To: <1384239144.67.0.857427270426.issue19557@psf.upfronthosting.co.za>
Message-ID: <1385490534.87.0.713823990719.issue19557@psf.upfronthosting.co.za>


Georg Brandl added the comment:

When citing a link, it's customary to give at least a comment *why* you are citing it.

----------
nosy: +georg.brandl

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

From report at bugs.python.org  Tue Nov 26 20:37:44 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 26 Nov 2013 19:37:44 +0000
Subject: [docs] [issue19793] Formatting of True/False in pathlib docs
In-Reply-To: <1385456749.57.0.871940933045.issue19793@psf.upfronthosting.co.za>
Message-ID: <3dTb471YZkzQN7@mail.python.org>


Roundup Robot added the comment:

New changeset 835007ccf2b0 by Serhiy Storchaka in branch 'default':
Issue #19793: Improved markup for True/False constants in pathlib documentation.
http://hg.python.org/cpython/rev/835007ccf2b0

----------
nosy: +python-dev

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

From report at bugs.python.org  Tue Nov 26 20:39:29 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 26 Nov 2013 19:39:29 +0000
Subject: [docs] [issue19793] Formatting of True/False in pathlib docs
In-Reply-To: <1385456749.57.0.871940933045.issue19793@psf.upfronthosting.co.za>
Message-ID: <1385494769.88.0.617495271088.issue19793@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From storchaka at gmail.com  Tue Nov 26 20:56:29 2013
From: storchaka at gmail.com (storchaka at gmail.com)
Date: Tue, 26 Nov 2013 19:56:29 -0000
Subject: [docs] Formatting of True/False in docs (issue 19795)
Message-ID: <20131126195629.22542.42854@psf.upfronthosting.co.za>

Reviewers: Georg,

Message:
Thank you Georg. Could you please help me with wording in doubtful
places?


http://bugs.python.org/review/19795/diff/10113/Doc/library/dis.rst
File Doc/library/dis.rst (right):

http://bugs.python.org/review/19795/diff/10113/Doc/library/dis.rst#newcode272
Doc/library/dis.rst:272: line started by this opcode (if any), otherwise
None
On 2013/11/26 18:37:58, Georg wrote:
> None should also be ``-ified :)  another patch forthcoming?

Good idea. I'll submit new patch later.

http://bugs.python.org/review/19795/diff/10113/Doc/library/logging.rst
File Doc/library/logging.rst (right):

http://bugs.python.org/review/19795/diff/10113/Doc/library/logging.rst#newcode163
Doc/library/logging.rst:163: ``False``. If specified as True, stack
information is added to the logging
On 2013/11/26 18:37:58, Georg wrote:
> you missed a True here

I doubt about wording. Any true value means same as ``True`` in boolean
context. But "as true" perhaps doesn't sound right. Could you please
propose right wording?

There are other places which I have not changed for the same reason.

http://bugs.python.org/review/19795/diff/10113/Doc/library/sqlite3.rst
File Doc/library/sqlite3.rst (right):

http://bugs.python.org/review/19795/diff/10113/Doc/library/sqlite3.rst#newcode245
Doc/library/sqlite3.rst:245: can call this function with *flag* as true.
Afterwards, you will get tracebacks
On 2013/11/26 18:37:58, Georg wrote:
> "with flag as true" doesn't sound right -- this could be formulated
differently
> while you're at it

I can't do this. Could you please propose better wording?

http://bugs.python.org/review/19795/diff/10113/Doc/reference/datamodel.rst
File Doc/reference/datamodel.rst (right):

http://bugs.python.org/review/19795/diff/10113/Doc/reference/datamodel.rst#newcode203
Doc/reference/datamodel.rst:203: These represent the truth values
``False`` and ``True``.  The two objects representing
On 2013/11/26 18:37:58, Georg wrote:
> this should not be code since it's not talking about the objects, but
the
> (Platonic ideal) values.

Done.



Please review this at http://bugs.python.org/review/19795/

Affected files:
  Doc/howto/curses.rst
  Doc/howto/functional.rst
  Doc/library/ast.rst
  Doc/library/bdb.rst
  Doc/library/bz2.rst
  Doc/library/ctypes.rst
  Doc/library/difflib.rst
  Doc/library/dis.rst
  Doc/library/email.message.rst
  Doc/library/functions.rst
  Doc/library/gc.rst
  Doc/library/http.client.rst
  Doc/library/http.cookiejar.rst
  Doc/library/imp.rst
  Doc/library/importlib.rst
  Doc/library/io.rst
  Doc/library/itertools.rst
  Doc/library/logging.handlers.rst
  Doc/library/logging.rst
  Doc/library/lzma.rst
  Doc/library/mmap.rst
  Doc/library/nntplib.rst
  Doc/library/os.path.rst
  Doc/library/os.rst
  Doc/library/pickle.rst
  Doc/library/plistlib.rst
  Doc/library/sched.rst
  Doc/library/sqlite3.rst
  Doc/library/ssl.rst
  Doc/library/stdtypes.rst
  Doc/library/struct.rst
  Doc/library/subprocess.rst
  Doc/library/sys.rst
  Doc/library/tarfile.rst
  Doc/library/tkinter.ttk.rst
  Doc/library/turtle.rst
  Doc/library/unittest.mock.rst
  Doc/library/urllib.request.rst
  Doc/library/venv.rst
  Doc/library/zipfile.rst
  Doc/library/zipimport.rst
  Doc/reference/datamodel.rst
  Doc/whatsnew/3.3.rst



From georg at python.org  Tue Nov 26 21:00:48 2013
From: georg at python.org (georg at python.org)
Date: Tue, 26 Nov 2013 20:00:48 -0000
Subject: [docs] Formatting of True/False in docs (issue 19795)
Message-ID: <20131126200048.22542.9750@psf.upfronthosting.co.za>


http://bugs.python.org/review/19795/diff/10113/Doc/library/logging.rst
File Doc/library/logging.rst (right):

http://bugs.python.org/review/19795/diff/10113/Doc/library/logging.rst#newcode163
Doc/library/logging.rst:163: ``False``. If specified as True, stack
information is added to the logging
On 2013/11/26 20:56:30, storchaka wrote:
> On 2013/11/26 18:37:58, Georg wrote:
> > you missed a True here
> 
> I doubt about wording. Any true value means same as ``True`` in
boolean context.
> But "as true" perhaps doesn't sound right. Could you please propose
right
> wording?

Just "If true" should be good.

http://bugs.python.org/review/19795/diff/10113/Doc/library/sqlite3.rst
File Doc/library/sqlite3.rst (right):

http://bugs.python.org/review/19795/diff/10113/Doc/library/sqlite3.rst#newcode245
Doc/library/sqlite3.rst:245: can call this function with *flag* as true.
Afterwards, you will get tracebacks
On 2013/11/26 20:56:30, storchaka wrote:
> On 2013/11/26 18:37:58, Georg wrote:
> > "with flag as true" doesn't sound right -- this could be formulated
> differently
> > while you're at it
> 
> I can't do this. Could you please propose better wording?

Hmm, what about

"you can call this function with *flag* set to ``True``"

http://bugs.python.org/review/19795/

From report at bugs.python.org  Tue Nov 26 21:29:24 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Tue, 26 Nov 2013 20:29:24 +0000
Subject: [docs] [issue19557] ast - docs for every node type are missing
In-Reply-To: <1384239144.67.0.857427270426.issue19557@psf.upfronthosting.co.za>
Message-ID: <1385497764.17.0.883976473521.issue19557@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

SO link serves a proof that a problem is actual. It is needed, because, for example Brett doesn't think it is important.

2nd link is the same proof, and also an example of documentation wanted.

----------

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

From report at bugs.python.org  Tue Nov 26 21:30:44 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Tue, 26 Nov 2013 20:30:44 +0000
Subject: [docs] [issue19557] ast - docs for every node type are missing
In-Reply-To: <1384239144.67.0.857427270426.issue19557@psf.upfronthosting.co.za>
Message-ID: <1385497844.27.0.877589619814.issue19557@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

In fact it may be the documentation that could be merged.

----------

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

From report at bugs.python.org  Wed Nov 27 05:32:09 2013
From: report at bugs.python.org (Graham Wideman)
Date: Wed, 27 Nov 2013 04:32:09 +0000
Subject: [docs] [issue19805] Revise FAQ Dictionary: consistent key order item
Message-ID: <1385526729.76.0.941069828347.issue19805@psf.upfronthosting.co.za>


New submission from Graham Wideman:

FAQ entry:
http://docs.python.org/3/faq/programming.html#how-can-i-get-a-dictionary-to-display-its-keys-in-a-consistent-order
claims that there's no way for a dictionary to return keys in a consistent order. However, there's OrderedDict which should probably be mentioned here.

----------
assignee: docs at python
components: Documentation
messages: 204550
nosy: docs at python, gwideman
priority: normal
severity: normal
status: open
title: Revise FAQ Dictionary: consistent key order item
type: enhancement
versions: Python 3.3

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

From report at bugs.python.org  Wed Nov 27 06:06:26 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 27 Nov 2013 05:06:26 +0000
Subject: [docs] [issue19805] Revise FAQ Dictionary: consistent key order item
In-Reply-To: <1385526729.76.0.941069828347.issue19805@psf.upfronthosting.co.za>
Message-ID: <3dTqhL0KCmz7Lk0@mail.python.org>


Roundup Robot added the comment:

New changeset 22e514e41fac by Benjamin Peterson in branch '3.3':
recommend OrderedDict for this FAQ (closes #19805)
http://hg.python.org/cpython/rev/22e514e41fac

New changeset ddbcb86afbdc by Benjamin Peterson in branch 'default':
merge 3.3 (#19805)
http://hg.python.org/cpython/rev/ddbcb86afbdc

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Wed Nov 27 11:18:41 2013
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 27 Nov 2013 10:18:41 +0000
Subject: [docs] [issue19809] Doc: subprocess should warn uses on race
	conditions when	multiple threads spawn child processes
In-Reply-To: <1385544646.44.0.340337636792.issue19809@psf.upfronthosting.co.za>
Message-ID: <1385547521.93.0.208571320396.issue19809@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
title: Python get stuck in second Popen call -> Doc: subprocess should warn uses on race conditions when multiple threads spawn child processes

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

From report at bugs.python.org  Thu Nov 28 02:08:46 2013
From: report at bugs.python.org (Martin Panter)
Date: Thu, 28 Nov 2013 01:08:46 +0000
Subject: [docs] [issue17232] Improve -O docs
In-Reply-To: <1361255101.21.0.948205073894.issue17232@psf.upfronthosting.co.za>
Message-ID: <1385600926.46.0.193878645614.issue17232@psf.upfronthosting.co.za>


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


----------
nosy: +vadmium

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

From report at bugs.python.org  Thu Nov 28 07:42:21 2013
From: report at bugs.python.org (Eric Snow)
Date: Thu, 28 Nov 2013 06:42:21 +0000
Subject: [docs] [issue19820] docs are missing info about module attributes
Message-ID: <1385620941.03.0.287546381963.issue19820@psf.upfronthosting.co.za>


New submission from Eric Snow:

The docs for the inspect module and the types module do not list all the import-related module attributes.  I'm guessing they've been out of sync a while.

The docstring for for inspect.ismodule() is likewise missing information.

----------
assignee: docs at python
components: Documentation
messages: 204642
nosy: docs at python, eric.snow
priority: low
severity: normal
stage: needs patch
status: open
title: docs are missing info about module attributes
type: enhancement
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Thu Nov 28 07:42:32 2013
From: report at bugs.python.org (Eric Snow)
Date: Thu, 28 Nov 2013 06:42:32 +0000
Subject: [docs] [issue19820] docs are missing info about module attributes
In-Reply-To: <1385620941.03.0.287546381963.issue19820@psf.upfronthosting.co.za>
Message-ID: <1385620952.5.0.590286419522.issue19820@psf.upfronthosting.co.za>


Changes by Eric Snow <ericsnowcurrently at gmail.com>:


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

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

From report at bugs.python.org  Thu Nov 28 14:59:29 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 28 Nov 2013 13:59:29 +0000
Subject: [docs] [issue19822] PEP process entrypoint
Message-ID: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>


New submission from anatoly techtonik:

https://bitbucket.org/rirror/peps

PEP repository readme lacks information about how to send Python Enhancement Proposal step-by-step.

1. hg clone https://bitbucket.org/rirror/peps
2. cd peps
3. # choose number
4. cp ??? pep-{{number}}.txt
5. # commit
6. # send pull request
7. # discuss

----------
assignee: docs at python
components: Devguide, Documentation
messages: 204652
nosy: docs at python, ezio.melotti, techtonik
priority: normal
severity: normal
status: open
title: PEP process entrypoint

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

From report at bugs.python.org  Thu Nov 28 15:04:49 2013
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 28 Nov 2013 14:04:49 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <1385647489.51.0.143830717275.issue19822@psf.upfronthosting.co.za>


Christian Heimes added the comment:

The process is well explained in the PEP templates right at the top of the PEP list:

http://www.python.org/dev/peps/pep-0009/
http://www.python.org/dev/peps/pep-0012/

New PEP authors should get in touch with experienced core developers or mentors in order to get assistance.

----------
nosy: +christian.heimes
resolution:  -> invalid
status: open -> closed

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

From report at bugs.python.org  Thu Nov 28 15:06:59 2013
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 28 Nov 2013 14:06:59 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <1385647619.22.0.525526306839.issue19822@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> PEP process entrypoint

Do you work with developers of the distutils-* objects? It looks like Daniel Holth works on such PEP for example:
https://mail.python.org/pipermail/distutils-sig/2013-July/021854.html

You may join this mailing list:
https://mail.python.org/mailman/listinfo/distutils-sig

----------
nosy: +haypo

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

From report at bugs.python.org  Thu Nov 28 15:28:10 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 28 Nov 2013 14:28:10 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <1385648890.13.0.0743824754357.issue19822@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

The "entrypoint" here means the point of entry for new Python Enhancement Proposals. Christian, what you propose is a 4th order link for someone who knows what PEPs are, and clones PEP repository to submit own proposal.

What I propose it to make PEP repository self-sufficient, so that person who cloned it, can immediately get to work. You can argue that people who don't have time to read on all previous stuff, should not write PEPs, but I'd object that it is good to be inclusive.

----------
resolution: invalid -> 
status: closed -> pending

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

From report at bugs.python.org  Thu Nov 28 15:34:12 2013
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Thu, 28 Nov 2013 14:34:12 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <1385649252.34.0.887308954603.issue19822@psf.upfronthosting.co.za>


Marc-Andre Lemburg added the comment:

Anatoly, please read http://www.python.org/dev/peps/pep-0012/

The process you are describing is not correct. In particular, the discussion happens before sending in a pull request.

As for discussion of the PEP process: that should happen on python-dev, not in some ticket in the tracker.

Closing the ticket again.

----------
nosy: +lemburg
resolution:  -> invalid
status: pending -> closed

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

From report at bugs.python.org  Thu Nov 28 15:45:05 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 28 Nov 2013 14:45:05 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <1385649905.17.0.7033270811.issue19822@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

> The process you are describing is not correct. In particular, the discussion happens before sending in a pull request.

Post the link to correct process into README.rst and then this issue can be closed.

As for python-dev, I thought it is too obvious and minor issue (still issue) to raise there, so it is just a matter of somebody with knowledge, time and commit privileges to commit the patch. It may worth to raise the question there anyway as I see that communicating usability concerns is a big problem.

----------
resolution: invalid -> 
status: closed -> open

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

From report at bugs.python.org  Thu Nov 28 15:50:39 2013
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 28 Nov 2013 14:50:39 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <1385650239.79.0.31891406509.issue19822@psf.upfronthosting.co.za>


Christian Heimes added the comment:

The ticket has been closed by two people. Why do you keep re-opening the ticket?

----------
resolution:  -> invalid
status: open -> closed

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

From report at bugs.python.org  Thu Nov 28 16:26:50 2013
From: report at bugs.python.org (Marc-Andre Lemburg)
Date: Thu, 28 Nov 2013 15:26:50 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385649905.17.0.7033270811.issue19822@psf.upfronthosting.co.za>
Message-ID: <529760B7.1040509@egenix.com>


Marc-Andre Lemburg added the comment:

On 28.11.2013 15:45, anatoly techtonik wrote:
> 
> anatoly techtonik added the comment:
> 
>> The process you are describing is not correct. In particular, the discussion happens before sending in a pull request.
> 
> Post the link to correct process into README.rst and then this issue can be closed.

The repo readme is not the right place for this. Christian already mentioned
the PEPs and anything should go into the dev guide.

If you have something to contribute, please open a ticket, add a patch
and request review.

Thanks,
-- 
Marc-Andre Lemburg
eGenix.com

----------

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

From report at bugs.python.org  Thu Nov 28 18:07:04 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 28 Nov 2013 17:07:04 +0000
Subject: [docs] [issue19824] string.Template: Add PHP-style variable
	expansion example
Message-ID: <1385658424.56.0.963803246137.issue19824@psf.upfronthosting.co.za>


New submission from anatoly techtonik:

http://docs.python.org/2/library/string.html#template-strings

This class could be more useful with the following example:

>>> from string import Template
>>> t = Template('$who likes $what')
>>> who = 'tim'
>>> what = 'kung pao'
>>> t.substitute(locals())
'tim likes kung pao'

This will help PHP folks to transition their .php files.

----------
assignee: docs at python
components: Documentation
messages: 204677
nosy: docs at python, techtonik
priority: normal
severity: normal
status: open
title: string.Template: Add PHP-style variable expansion example

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

From report at bugs.python.org  Thu Nov 28 18:19:30 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 28 Nov 2013 17:19:30 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <1385659170.9.0.824834529791.issue19822@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

> The ticket has been closed by two people. Why do you keep re-opening the ticket?

Because you're not providing any arguments. If it is not important for you, just ignore. If something is not clear - ask. What you do is just closing the stuff, because you _feel_ that is not an issue. Provide rationale, address my points and then I'll close it myself. The particular stuff that is not clarified:

>> Post the link to correct process into README.rst and then this
>> issue can be closed.
> The repo readme is not the right place for this. Christian already
> mentioned the PEPs and anything should go into the dev guide.

I want to know why PEPs repository README is not the place to direct users to starting point for submitting enhancement proposals?

> If you have something to contribute, please open a ticket, add a patch
and request review.

I am already keep opening it, damn. I want to contribute an improvement for the PEP process and not forget about it. That's why I fill in into tracker, and not into email.

----------
resolution: invalid -> postponed
status: closed -> open

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

From report at bugs.python.org  Thu Nov 28 18:32:00 2013
From: report at bugs.python.org (Barry A. Warsaw)
Date: Thu, 28 Nov 2013 17:32:00 +0000
Subject: [docs] [issue19824] string.Template: Add PHP-style variable
	expansion example
In-Reply-To: <1385658424.56.0.963803246137.issue19824@psf.upfronthosting.co.za>
Message-ID: <1385659920.97.0.305265885943.issue19824@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Nov 28 18:35:15 2013
From: report at bugs.python.org (Barry A. Warsaw)
Date: Thu, 28 Nov 2013 17:35:15 +0000
Subject: [docs] [issue19824] string.Template: Add PHP-style variable
	expansion example
In-Reply-To: <1385658424.56.0.963803246137.issue19824@psf.upfronthosting.co.za>
Message-ID: <20131128123517.5d087dd6@anarchist>


Barry A. Warsaw added the comment:

On Nov 28, 2013, at 05:07 PM, anatoly techtonik wrote:

>This class could be more useful with the following example:
>
>>>> from string import Template
>>>> t = Template('$who likes $what')
>>>> who = 'tim'
>>>> what = 'kung pao'
>>>> t.substitute(locals())
>'tim likes kung pao'
>
>This will help PHP folks to transition their .php files.

I'm not sure what you want to add to the class.  Your example works out of the
box.  See this for an approach my third party library takes:

http://pythonhosted.org/flufl.i18n/docs/using.html#substitutions-and-placeholders

----------

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

From report at bugs.python.org  Thu Nov 28 18:41:17 2013
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 28 Nov 2013 17:41:17 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385659170.9.0.824834529791.issue19822@psf.upfronthosting.co.za>
Message-ID: <CAMpsgwZjECdFYE3kXUS3MQXD_APXBwC5L9td2eCUxZsQnFhocQ@mail.gmail.com>


STINNER Victor added the comment:

Anatoly, please stop reopening the issue, it's *really* annoying. Not
only you failed to understand correctly your problem (it looks like
nor Christian nor Marc-Andre nor me understood your request), but it
looks like you don't care of our answers.

> PEP repository readme lacks information about how to send Python Enhancement Proposal step-by-step.

Did you at least read the *first* PEP, the PEP which describes the PEP process?
http://www.python.org/dev/peps/pep-0001/

Did you also read the developer guide? The PEP process is also explained there:
http://docs.python.org/devguide/langchanges.html#pep-process

> What I propose it to make PEP repository self-sufficient,

The PEP 1, 9 and 12 are already included in the PEP repository.

I don't understand why you are focused on the README.rst file. PEPs
are more convinient because automatically exported online at:
http://www.python.org/dev/peps/

For example, you must read:
http://www.python.org/dev/peps/pep-0001/

> I am already keep opening it, damn. I want to contribute an improvement for the PEP process and not forget about it. That's why I fill in into tracker, and not into email.

The PEP process is already well described, so your issue is invalid.

You don't propose anything concrete. Example of concrete thing: a
patch on the pep-0001.rst or on README.rst. Or contribute to the
devguide.

Did you sign the contributor agreement?
http://docs.python.org/devguide/coredev.html#sign-a-contributor-agreement

I know that you don't want to sign it, even if I don't understand why
(please don't start discuss it here, the legal mailing list is the
right place), but it's required to contribute to CPython.

--

The PEP process is not so formal. Just start discussing an idea on
python-idea, don't worry of the exact structure of a PEP document. It
can be written later. It is a waste of time to write a full PEP if an
idea is quickly rejected.

----------

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

From report at bugs.python.org  Thu Nov 28 18:59:01 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 28 Nov 2013 17:59:01 +0000
Subject: [docs] [issue19824] string.Template: Add PHP-style variable
	expansion example
In-Reply-To: <1385658424.56.0.963803246137.issue19824@psf.upfronthosting.co.za>
Message-ID: <1385661541.24.0.32016820377.issue19824@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

There is nothing to add to the class itself. It is about expanding docs section with helpful examples. `string.Template` is undervalued, because it is hard to see how it can be more useful than standard string formatting functions. But for people coming from PHP world, this can be a good start. The docs just need an entrypoint that shows how to use locally defined variables in template string. PHP does this for strings automatically.

----------

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

From report at bugs.python.org  Thu Nov 28 19:00:02 2013
From: report at bugs.python.org (Alex Gaynor)
Date: Thu, 28 Nov 2013 18:00:02 +0000
Subject: [docs] [issue19824] string.Template: Add PHP-style variable
	expansion example
In-Reply-To: <1385658424.56.0.963803246137.issue19824@psf.upfronthosting.co.za>
Message-ID: <1385661602.82.0.834833543244.issue19824@psf.upfronthosting.co.za>


Alex Gaynor added the comment:

Using locals() in this fashion is a serious anti-pattern, I'm -? on the docs suggesting it.

----------
nosy: +alex

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

From report at bugs.python.org  Thu Nov 28 19:03:55 2013
From: report at bugs.python.org (Giampaolo Rodola')
Date: Thu, 28 Nov 2013 18:03:55 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <1385661835.53.0.26592787694.issue19822@psf.upfronthosting.co.za>


Changes by Giampaolo Rodola' <g.rodola at gmail.com>:


----------
nosy: +giampaolo.rodola

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

From report at bugs.python.org  Thu Nov 28 20:50:45 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 28 Nov 2013 19:50:45 +0000
Subject: [docs] [issue19826] Document that bug reporting by email is possible
Message-ID: <1385668245.52.0.0107396832211.issue19826@psf.upfronthosting.co.za>


New submission from anatoly techtonik:

I found this to be convenient: http://techtonik.rainforce.org/2013/11/roundup-tracker-create-issues-by-email.html

And this is missing from here: http://docs.python.org/release/2.7/bugs.html#using-the-python-issue-tracker
Anf from here:
http://docs.python.org/devguide/triaging.html

Disclaimer: I didn't sign the CLA, and people keep telling me that I need it to do documentation edits. But I edit Wikipedia freely and I find it wrong that I can not edit Python documentation without signing papers. So I am not sending patches until either Wikipedia requires CLA to edit its contents, or PSF abandons its ill FUD policies in favor of creating collaborative environment.

Regarding my aforementioned blog post, feel free to copy-paste it, as an author I release this into CC0/public domain. Ask python-legal-sig if it is enough.

----------
assignee: docs at python
components: Documentation
messages: 204693
nosy: docs at python, techtonik
priority: normal
severity: normal
status: open
title: Document that bug reporting by email is possible

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

From report at bugs.python.org  Thu Nov 28 21:00:36 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 28 Nov 2013 20:00:36 +0000
Subject: [docs] [issue19824] string.Template: Add PHP-style variable
	expansion example
In-Reply-To: <1385658424.56.0.963803246137.issue19824@psf.upfronthosting.co.za>
Message-ID: <1385668836.92.0.438028135116.issue19824@psf.upfronthosting.co.za>


anatoly techtonik added the comment:

@Alex, have you seen http://pythonhosted.org/flufl.i18n/docs/using.html#substitutions-and-placeholders? I really like the brevity, and it is the function that does the magic, so it is fully transparent and you don't need to instantiate string.Template every time. I think its awesome.

Do you have some explanations why passing locals() to string.Template is anti-pattern? I understand that passing "all that you have" is not good, but from my past experience with PHP I can't remember any problems that there are more names than I used. It is templating after all - what do you want to protect from?

----------

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

From report at bugs.python.org  Thu Nov 28 21:06:20 2013
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 28 Nov 2013 20:06:20 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <1385669180.85.0.989838560666.issue19822@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Closing for the hopefully final time.  Anatoly, if you keep reopening this ticket you have to expect removal of tracker privileges.

----------
nosy: +georg.brandl
resolution: postponed -> rejected
status: open -> closed

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

From report at bugs.python.org  Thu Nov 28 22:12:59 2013
From: report at bugs.python.org (Barry A. Warsaw)
Date: Thu, 28 Nov 2013 21:12:59 +0000
Subject: [docs] [issue19824] string.Template: Add PHP-style variable
	expansion example
In-Reply-To: <1385668836.92.0.438028135116.issue19824@psf.upfronthosting.co.za>
Message-ID: <20131128161259.14035dea@anarchist>


Barry A. Warsaw added the comment:

A few notes about flufl.i18n's style.  We chose this (extracted from the GNU
Mailman project) because $strings are *way* less error prone for translators
than %s strings, especially when you consider that some languages change the
order of placeholders.  The automatic extraction of substitutions from locals
and globals (under the hood, via the sys._getframe() hack) was critical to
making the source code readable, by avoiding not just duplication, but
triplication of names.

There is a potential security hole though - a malicious translator with access
to the source could analyze the local and global context in which the
translation+substitution is being made, and craft a gettext catalog that adds
some new substitutions that expose sensitive information.  Given that most
translations get little scrutiny, this could be used as an attack vector for
users of some languages (though not English, since it's typically the source
language and thus not translated).

We've decided to accept the risks in exchange for the huge convenience.  We've
never seen such an attack and if we did, we'd address it in the code by
manipulating the globals and locals to avoid the possibility of a leak.  (We'd
also learn to never trust the translators that added the hack.)

----------

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

From report at bugs.python.org  Fri Nov 29 11:22:58 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 29 Nov 2013 10:22:58 +0000
Subject: [docs] [issue19795] Formatting of True/False in docs
In-Reply-To: <1385457525.93.0.980812903017.issue19795@psf.upfronthosting.co.za>
Message-ID: <3dWBcc5qVFz7LjP@mail.python.org>


Roundup Robot added the comment:

New changeset f51ca196d77a by Serhiy Storchaka in branch '2.7':
Issue #19795: Improved markup of True/False constants.
http://hg.python.org/cpython/rev/f51ca196d77a

New changeset b2066bc8cab9 by Serhiy Storchaka in branch '3.3':
Issue #19795: Improved markup of True/False constants.
http://hg.python.org/cpython/rev/b2066bc8cab9

New changeset 6a3e09cd96f3 by Serhiy Storchaka in branch 'default':
Issue #19795: Improved markup of True/False constants.
http://hg.python.org/cpython/rev/6a3e09cd96f3

----------
nosy: +python-dev

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

From report at bugs.python.org  Fri Nov 29 11:46:29 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 29 Nov 2013 10:46:29 +0000
Subject: [docs] [issue19795] Formatting of True/False in docs
In-Reply-To: <1385457525.93.0.980812903017.issue19795@psf.upfronthosting.co.za>
Message-ID: <1385721987.52.0.785533052204.issue19795@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you Georg for your help.

Here is a patch which fixes markups for the None constant. It is more unequivocal.

----------
Added file: http://bugs.python.org/file32885/doc_none.patch

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

From report at bugs.python.org  Fri Nov 29 15:09:20 2013
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 29 Nov 2013 14:09:20 +0000
Subject: [docs] [issue19826] Document that bug reporting by email is possible
In-Reply-To: <1385668245.52.0.0107396832211.issue19826@psf.upfronthosting.co.za>
Message-ID: <1385734160.59.0.0176712389754.issue19826@psf.upfronthosting.co.za>


Brett Cannon added the comment:

We cannot accept anything you produce until you sign the CLA.

----------
nosy: +brett.cannon

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

From report at bugs.python.org  Fri Nov 29 15:09:49 2013
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 29 Nov 2013 14:09:49 +0000
Subject: [docs] [issue19826] Document that bug reporting by email is possible
In-Reply-To: <1385668245.52.0.0107396832211.issue19826@psf.upfronthosting.co.za>
Message-ID: <1385734189.12.0.316248542332.issue19826@psf.upfronthosting.co.za>


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


----------
priority: normal -> low
stage:  -> needs patch

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

From report at bugs.python.org  Fri Nov 29 15:19:07 2013
From: report at bugs.python.org (Bohuslav "Slavek" Kabrda)
Date: Fri, 29 Nov 2013 14:19:07 +0000
Subject: [docs] [issue15657] Error in Python 3 docs for PyMethodDef
In-Reply-To: <1344970966.7.0.115664419243.issue15657@psf.upfronthosting.co.za>
Message-ID: <1385734747.28.0.339286537265.issue15657@psf.upfronthosting.co.za>


Changes by Bohuslav "Slavek" Kabrda <bkabrda at redhat.com>:


----------
nosy: +bkabrda

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

From report at bugs.python.org  Fri Nov 29 16:16:16 2013
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 29 Nov 2013 15:16:16 +0000
Subject: [docs] [issue19833] asyncio: patches to document EventLoop and add
	more	examples
Message-ID: <1385738176.38.0.477367051955.issue19833@psf.upfronthosting.co.za>


New submission from STINNER Victor:

Attached patches document get_event_loop() and BaseEventLoop; and add two "hello world" examples copied from:
http://code.google.com/p/tulip/source/browse/#hg%2Fexamples

----------
assignee: docs at python
components: Documentation
files: asyncio_doc_eventloop.patch
keywords: patch
messages: 204724
nosy: docs at python, gvanrossum, haypo, pitrou
priority: normal
severity: normal
status: open
title: asyncio: patches to document EventLoop and add more examples
versions: Python 3.4
Added file: http://bugs.python.org/file32889/asyncio_doc_eventloop.patch

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

From report at bugs.python.org  Fri Nov 29 16:17:31 2013
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 29 Nov 2013 15:17:31 +0000
Subject: [docs] [issue19833] asyncio: patches to document EventLoop and add
	more	examples
In-Reply-To: <1385738176.38.0.477367051955.issue19833@psf.upfronthosting.co.za>
Message-ID: <1385738251.97.0.78933573619.issue19833@psf.upfronthosting.co.za>


STINNER Victor added the comment:

I know that the documentation contains a lot of XXX, but it documents at least the prototype of the methods. I may provide more patches fixing XXX later ;-)

I hesitated to document the Handle class, but it looks like Guido prefers to not document it?

----------
Added file: http://bugs.python.org/file32890/asyncio_doc_examples.patch

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

From report at bugs.python.org  Fri Nov 29 16:22:09 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 29 Nov 2013 15:22:09 +0000
Subject: [docs] [issue19833] asyncio: patches to document EventLoop and add
	more	examples
In-Reply-To: <1385738176.38.0.477367051955.issue19833@psf.upfronthosting.co.za>
Message-ID: <1385738529.03.0.10815753334.issue19833@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Since there are many event loop methods, I structured the doc so that methods are grouped in different sections: see the existing "delayed calls" and "creating connections" sections.

I'm not saying it's the best solution (is it?), but I think it would be nice to be consistent :)

----------

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

From report at bugs.python.org  Fri Nov 29 16:58:59 2013
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 29 Nov 2013 15:58:59 +0000
Subject: [docs] [issue19833] asyncio: patches to document EventLoop and add
	more	examples
In-Reply-To: <1385738176.38.0.477367051955.issue19833@psf.upfronthosting.co.za>
Message-ID: <1385740739.23.0.981288335184.issue19833@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> Since there are many event loop methods, I structured the doc so that methods are grouped in different sections: see the existing "delayed calls" and "creating connections" sections.

Seriously, I read the documentation three times (HTML and the source), but I didn't notice that asyncio.call_later() is not a function, but a method of an object.

> I'm not saying it's the best solution (is it?), but I think it would be nice to be consistent :)

There are too many methods, it's a good solution. I will rewrite asyncio_doc_eventloop.patch to group the methods.

Before that, here is a patch to mention the class for methods.

----------
Added file: http://bugs.python.org/file32891/asyncio_doc_methods.patch

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

From report at bugs.python.org  Fri Nov 29 18:24:41 2013
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 29 Nov 2013 17:24:41 +0000
Subject: [docs] [issue19833] asyncio: patches to document EventLoop and add
	more	examples
In-Reply-To: <1385738176.38.0.477367051955.issue19833@psf.upfronthosting.co.za>
Message-ID: <1385745881.46.0.742856326733.issue19833@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

I would much rather review the docs after they've been committed.

----------

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

From report at bugs.python.org  Fri Nov 29 19:26:59 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 29 Nov 2013 18:26:59 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <3dWPM65cPSz7Ljt@mail.python.org>


Roundup Robot added the comment:

New changeset 34cb64cdbf7b by Guido van Rossum in branch 'default':
Add brief explanation and web pointers to README.txt. Fixes issue 19822.
http://hg.python.org/peps/rev/34cb64cdbf7b

----------
nosy: +python-dev

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

From report at bugs.python.org  Fri Nov 29 19:35:26 2013
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 29 Nov 2013 18:35:26 +0000
Subject: [docs] [issue19822] PEP process entrypoint
In-Reply-To: <1385647169.27.0.622120668783.issue19822@psf.upfronthosting.co.za>
Message-ID: <1385750126.43.0.356041927269.issue19822@psf.upfronthosting.co.za>


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


----------
resolution: rejected -> fixed

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

From report at bugs.python.org  Fri Nov 29 19:40:10 2013
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 29 Nov 2013 18:40:10 +0000
Subject: [docs] [issue19454] devguide: Document what a "platform support" is
In-Reply-To: <1383159116.46.0.184690879028.issue19454@psf.upfronthosting.co.za>
Message-ID: <1385750410.29.0.534150572555.issue19454@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

This is explicitly left up to the core developers' finely tuned sense of judgment.  Adding a definition will not simplify decisions or reduce disagreements, it will just cause more pointless legalistic debate about the meaning of specific words.

----------
nosy: +gvanrossum
resolution:  -> wont fix
stage: needs patch -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Fri Nov 29 20:52:15 2013
From: report at bugs.python.org (=?utf-8?q?Charles-Fran=C3=A7ois_Natali?=)
Date: Fri, 29 Nov 2013 19:52:15 +0000
Subject: [docs] [issue19836] selectors: improve examples section
Message-ID: <1385754735.32.0.742504427925.issue19836@psf.upfronthosting.co.za>


New submission from Charles-Fran?ois Natali:

Here's a patch improving the "examples" section for the selectors module.

----------
assignee: docs at python
components: Documentation
files: selectors_examples.diff
keywords: needs review, patch
messages: 204750
nosy: docs at python, neologix
priority: normal
severity: normal
stage: patch review
status: open
title: selectors: improve examples section
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file32894/selectors_examples.diff

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

From report at bugs.python.org  Fri Nov 29 21:39:03 2013
From: report at bugs.python.org (=?utf-8?q?Charles-Fran=C3=A7ois_Natali?=)
Date: Fri, 29 Nov 2013 20:39:03 +0000
Subject: [docs] [issue19836] selectors: improve examples section
In-Reply-To: <1385754735.32.0.742504427925.issue19836@psf.upfronthosting.co.za>
Message-ID: <1385757543.65.0.320628004036.issue19836@psf.upfronthosting.co.za>


Changes by Charles-Fran?ois Natali <cf.natali at gmail.com>:


Removed file: http://bugs.python.org/file32894/selectors_examples.diff

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

From report at bugs.python.org  Fri Nov 29 21:39:18 2013
From: report at bugs.python.org (=?utf-8?q?Charles-Fran=C3=A7ois_Natali?=)
Date: Fri, 29 Nov 2013 20:39:18 +0000
Subject: [docs] [issue19836] selectors: improve examples section
In-Reply-To: <1385754735.32.0.742504427925.issue19836@psf.upfronthosting.co.za>
Message-ID: <1385757558.54.0.393340748068.issue19836@psf.upfronthosting.co.za>


Changes by Charles-Fran?ois Natali <cf.natali at gmail.com>:


Added file: http://bugs.python.org/file32895/selectors_examples.diff

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

From report at bugs.python.org  Fri Nov 29 21:42:52 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 29 Nov 2013 20:42:52 +0000
Subject: [docs] [issue19836] selectors: improve examples section
In-Reply-To: <1385754735.32.0.742504427925.issue19836@psf.upfronthosting.co.za>
Message-ID: <1385757772.07.0.397919319787.issue19836@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

This sounds ok to me.

----------
nosy: +gvanrossum, pitrou

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

From report at bugs.python.org  Fri Nov 29 22:01:03 2013
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 29 Nov 2013 21:01:03 +0000
Subject: [docs] [issue19836] selectors: improve examples section
In-Reply-To: <1385754735.32.0.742504427925.issue19836@psf.upfronthosting.co.za>
Message-ID: <1385758863.51.0.907873646953.issue19836@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

This is definitely an improvement over the previous example, but I think both examples are still pretty unrealistic; they seem to be more useful as smoke tests than as examples.  My primary concern is that, in order to be both self-contained and small, both examples have both the sender and the receiver in the same code (connected by a socketpair).  But this makes them useless as starting points for simple applications built around a typical select loop.

Perhaps a basic echo service would be a better starting point?  I'll try to create one.

----------

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

From report at bugs.python.org  Fri Nov 29 22:15:13 2013
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 29 Nov 2013 21:15:13 +0000
Subject: [docs] [issue19836] selectors: improve examples section
In-Reply-To: <1385754735.32.0.742504427925.issue19836@psf.upfronthosting.co.za>
Message-ID: <1385759713.37.0.338591571533.issue19836@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Here's my suggestion.  It can use a lot of cleaning up, but it shows the fundamentals of a selector-based I/O loop.

----------
Added file: http://bugs.python.org/file32896/echo.py

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

From report at bugs.python.org  Fri Nov 29 22:18:30 2013
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 29 Nov 2013 21:18:30 +0000
Subject: [docs] [issue19836] selectors: improve examples section
In-Reply-To: <1385754735.32.0.742504427925.issue19836@psf.upfronthosting.co.za>
Message-ID: <1385759910.03.0.544267747364.issue19836@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Sorry, here's a version with slightly more logical order of the code.

----------
Added file: http://bugs.python.org/file32897/echo.py

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

From report at bugs.python.org  Fri Nov 29 22:18:42 2013
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 29 Nov 2013 21:18:42 +0000
Subject: [docs] [issue19836] selectors: improve examples section
In-Reply-To: <1385754735.32.0.742504427925.issue19836@psf.upfronthosting.co.za>
Message-ID: <1385759922.09.0.494088722247.issue19836@psf.upfronthosting.co.za>


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


Removed file: http://bugs.python.org/file32896/echo.py

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

From report at bugs.python.org  Fri Nov 29 22:26:31 2013
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Fri, 29 Nov 2013 21:26:31 +0000
Subject: [docs] [issue19795] Formatting of True/False in docs
In-Reply-To: <1385457525.93.0.980812903017.issue19795@psf.upfronthosting.co.za>
Message-ID: <1385760390.96.0.741155256434.issue19795@psf.upfronthosting.co.za>


Arfrever Frehtes Taifersar Arahesis added the comment:

> New changeset b2066bc8cab9 by Serhiy Storchaka in branch '3.3':
> Issue #19795: Improved markup of True/False constants.
> http://hg.python.org/cpython/rev/b2066bc8cab9

Accidental, unrelated changes in Doc/library/importlib.rst (and with conflict marker).

----------
nosy: +Arfrever

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

From report at bugs.python.org  Fri Nov 29 22:43:22 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 29 Nov 2013 21:43:22 +0000
Subject: [docs] [issue19795] Formatting of True/False in docs
In-Reply-To: <1385457525.93.0.980812903017.issue19795@psf.upfronthosting.co.za>
Message-ID: <3dWTjk14qFz7LjY@mail.python.org>


Roundup Robot added the comment:

New changeset 9d0dc3d7bf01 by Serhiy Storchaka in branch '3.3':
Revert unrelated changes introduced by changeset b2066bc8cab9  (issue #19795).
http://hg.python.org/cpython/rev/9d0dc3d7bf01

----------

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

From report at bugs.python.org  Fri Nov 29 22:44:19 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 29 Nov 2013 21:44:19 +0000
Subject: [docs] [issue19795] Formatting of True/False in docs
In-Reply-To: <1385457525.93.0.980812903017.issue19795@psf.upfronthosting.co.za>
Message-ID: <1385761459.12.0.764129850721.issue19795@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you Arfrever.

----------

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

From report at bugs.python.org  Fri Nov 29 22:50:01 2013
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Fri, 29 Nov 2013 21:50:01 +0000
Subject: [docs] [issue17232] Improve -O docs
In-Reply-To: <1361255101.21.0.948205073894.issue17232@psf.upfronthosting.co.za>
Message-ID: <1385761801.31.0.884031450997.issue17232@psf.upfronthosting.co.za>


Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com>:


----------
nosy: +Arfrever

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

From report at bugs.python.org  Fri Nov 29 22:50:38 2013
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Fri, 29 Nov 2013 21:50:38 +0000
Subject: [docs] [issue19820] docs are missing info about module attributes
In-Reply-To: <1385620941.03.0.287546381963.issue19820@psf.upfronthosting.co.za>
Message-ID: <1385761838.01.0.553991172547.issue19820@psf.upfronthosting.co.za>


Changes by Arfrever Frehtes Taifersar Arahesis <Arfrever.FTA at GMail.Com>:


----------
nosy: +Arfrever

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

From report at bugs.python.org  Fri Nov 29 23:46:27 2013
From: report at bugs.python.org (=?utf-8?q?Charles-Fran=C3=A7ois_Natali?=)
Date: Fri, 29 Nov 2013 22:46:27 +0000
Subject: [docs] [issue19836] selectors: improve examples section
In-Reply-To: <1385759922.09.0.494088722247.issue19836@psf.upfronthosting.co.za>
Message-ID: <CAH_1eM07j9e4=qA-V02S-Ui4W-SEFeCG-j6FY+_rgd5hzTR9NA@mail.gmail.com>


Charles-Fran?ois Natali added the comment:

Here's an updated patch adding your echo server to the examples section.

----------
Added file: http://bugs.python.org/file32899/selectors_example-1.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19836>
_______________________________________
-------------- next part --------------
diff -r a1a936a3b2f6 Doc/library/selectors.rst
--- a/Doc/library/selectors.rst	Fri Nov 29 18:57:47 2013 +0100
+++ b/Doc/library/selectors.rst	Fri Nov 29 23:44:50 2013 +0100
@@ -210,33 +210,41 @@
       :func:`select.kqueue` object.
 
 
-Examples of selector usage::
+Examples
+--------
 
-   >>> import selectors
-   >>> import socket
-   >>>
-   >>> s = selectors.DefaultSelector()
-   >>> r, w = socket.socketpair()
-   >>>
-   >>> r.setblocking(False)
-   >>> w.setblocking(False)
-   >>>
-   >>> s.register(r, selectors.EVENT_READ)
-   SelectorKey(fileobj=<socket.socket fd=4, family=AddressFamily.AF_UNIX, type=2049, proto=0>, fd=4, events=1, data=None)
-   >>> s.register(w, selectors.EVENT_WRITE)
-   SelectorKey(fileobj=<socket.socket fd=5, family=AddressFamily.AF_UNIX, type=2049, proto=0>, fd=5, events=2, data=None)
-   >>>
-   >>> print(s.select())
-   [(SelectorKey(fileobj=<socket.socket fd=5, family=AddressFamily.AF_UNIX, type=2049, proto=0>, fd=5, events=2, data=None), 2)]
-   >>>
-   >>> for key, events in s.select():
-   ...     if events & selectors.EVENT_WRITE:
-   ...         key.fileobj.send(b'spam')
-   ...
-   4
-   >>> for key, events in s.select():
-   ...     if events & selectors.EVENT_READ:
-   ...         print(key.fileobj.recv(1024))
-   ...
-   b'spam'
-   >>> s.close()
+Here is a simple echo server implementation::
+
+   import selectors
+   import socket
+
+
+   sel = selectors.DefaultSelector()
+
+   def accept(sock, mask):
+       conn, addr = sock.accept()  # Should be ready
+       print('accepted', conn, 'from', addr)
+       conn.setblocking(False)
+       sel.register(conn, selectors.EVENT_READ, read)
+
+   def read(conn, mask):
+       data = conn.recv(1000)  # Should be ready
+       if data:
+           print('echoing', repr(data), 'to', conn)
+           conn.send(data)  # Hope it won't block
+       else:
+           print('closing', conn)
+           sel.unregister(conn)
+           conn.close()
+
+   sock = socket.socket()
+   sock.bind(('localhost', 1234))
+   sock.listen(100)
+   sock.setblocking(False)
+   sel.register(sock, selectors.EVENT_READ, accept)
+
+   while True:
+       events = sel.select()
+       for key, mask in events:
+           callback = key.data
+           callback(key.fileobj, mask)

From report at bugs.python.org  Fri Nov 29 23:54:00 2013
From: report at bugs.python.org (Guido van Rossum)
Date: Fri, 29 Nov 2013 22:54:00 +0000
Subject: [docs] [issue19836] selectors: improve examples section
In-Reply-To: <1385754735.32.0.742504427925.issue19836@psf.upfronthosting.co.za>
Message-ID: <1385765640.48.0.373427632839.issue19836@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Committed: revision 2a679870d7d2.

----------
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sat Nov 30 01:52:21 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 30 Nov 2013 00:52:21 +0000
Subject: [docs] [issue19833] asyncio: patches to document EventLoop and add
	more	examples
In-Reply-To: <1385738176.38.0.477367051955.issue19833@psf.upfronthosting.co.za>
Message-ID: <1385772741.17.0.424704799614.issue19833@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

One reason I originally didn't add the class names to the methods is that I don't know if we want to document the inheritance hierarchy. Guido, what do you think?

----------

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

From report at bugs.python.org  Sat Nov 30 03:54:33 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 30 Nov 2013 02:54:33 +0000
Subject: [docs] [issue19731] Fix copyright footer
In-Reply-To: <1385173768.12.0.946242825352.issue19731@psf.upfronthosting.co.za>
Message-ID: <1385780073.77.0.887823301434.issue19731@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

As I first noted, 1990 is before the first release of Python in 1992, so that seemed to be too early. I think Marc-Andre's fix is good enough and should be applied.

Victor, you want something weird? You can probably find technical books now copyrighted '2014'. Publishers sometime postdate (lie) so the book will not seem obsolete so soon. But is does not mean that it is not copyrighted (protected) now.

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

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

From report at bugs.python.org  Sat Nov 30 04:25:55 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 30 Nov 2013 03:25:55 +0000
Subject: [docs] [issue19737] Documentation of globals() and locals() should
	be	improved
In-Reply-To: <1385225461.09.0.671908077084.issue19737@psf.upfronthosting.co.za>
Message-ID: <1385781954.76.0.439057459948.issue19737@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

In my opinion, vague ideas like this one should go to python-ideas first.

I agree with David that globals() and locals() are separate issues. Since there have been and perhaps still are locals() doc issues, I will take this one to be about 'globals()'.

A 'symbol table' is a mapping between 'symbols' and 'values'. I presume such were originally implemented as a concrete list of pairs, but the term is now is an abstraction. In the Python context, I think 'namespace' would be a better word, but I would not make the change without getting other opinions, such as on python-ideas. 

The [...] that you omitted says "This is always the dictionary of the current module (...)." I cannot interpret 'is' to mean a copy. So I think "[concrete] dictionary represents [abstract] symbol table [namespace]" is fine.

----------
nosy: +terry.reedy
versions: +Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Nov 30 05:16:36 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 30 Nov 2013 04:16:36 +0000
Subject: [docs] [issue19833] asyncio: patches to document EventLoop and add
	more	examples
In-Reply-To: <1385738176.38.0.477367051955.issue19833@psf.upfronthosting.co.za>
Message-ID: <1385784996.03.0.780777076744.issue19833@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Nov 30 06:31:16 2013
From: report at bugs.python.org (Martin Panter)
Date: Sat, 30 Nov 2013 05:31:16 +0000
Subject: [docs] [issue19737] Documentation of globals() and locals() should
	be	improved
In-Reply-To: <1385225461.09.0.671908077084.issue19737@psf.upfronthosting.co.za>
Message-ID: <1385789476.96.0.199953999245.issue19737@psf.upfronthosting.co.za>


Martin Panter added the comment:

How about swapping the two sentences for globals() then:

?Returns the dictionary of the module . . . This represents the symbol table . . .?

I thought the current locals() entry is fairly clear. It actually says _not_ to modify the dictionary!

----------

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

From report at bugs.python.org  Sat Nov 30 08:07:17 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 30 Nov 2013 07:07:17 +0000
Subject: [docs] [issue19789] Improve wording of how to "undo" a call
	to	logging.disable(lvl)
In-Reply-To: <1385442860.38.0.88263802784.issue19789@psf.upfronthosting.co.za>
Message-ID: <1385795237.08.0.490969608697.issue19789@psf.upfronthosting.co.za>


Changes by Ezio Melotti <ezio.melotti at gmail.com>:


----------
nosy: +vinay.sajip

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

From report at bugs.python.org  Sat Nov 30 12:07:07 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 30 Nov 2013 11:07:07 +0000
Subject: [docs] [issue10976] json.loads() raises TypeError on bytes object
In-Reply-To: <1295636509.41.0.0138366952356.issue10976@psf.upfronthosting.co.za>
Message-ID: <1385809627.05.0.210333798057.issue10976@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Sat Nov 30 12:16:54 2013
From: report at bugs.python.org (Vinay Sajip)
Date: Sat, 30 Nov 2013 11:16:54 +0000
Subject: [docs] [issue19789] Improve wording of how to "undo" a call
	to	logging.disable(lvl)
In-Reply-To: <1385442860.38.0.88263802784.issue19789@psf.upfronthosting.co.za>
Message-ID: <1385810214.77.0.833138333397.issue19789@psf.upfronthosting.co.za>


Vinay Sajip added the comment:

It's not the docstring in the code, it's the actual documentation. I propose to change it so that the documentation for disable will read:

Provides an overriding level *lvl* for all loggers which takes precedence over the logger's own level. When the need arises to temporarily throttle logging output down across the whole application, this function can be useful. Its effect is to disable all logging calls of severity *lvl* and below, so that if you call it with a value of INFO, then all INFO and DEBUG events would be discarded, whereas those of severity WARNING and above would be processed according to the logger's effective level. If ``logging.disable(logging.NOTSET)`` is called, it effectively removes this overriding level, so that logging output again depends on the effective levels of individual loggers.

Please confirm if this is still not clear enough, otherwise I will commit this in a day or two and close the issue.

----------
versions: +Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Nov 30 15:06:01 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 30 Nov 2013 14:06:01 +0000
Subject: [docs] [issue10976] json.loads() raises TypeError on bytes object
In-Reply-To: <1295636509.41.0.0138366952356.issue10976@psf.upfronthosting.co.za>
Message-ID: <1385820361.46.0.742716891009.issue10976@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Issue 19837 is the complementary problem on the serialisation side - users migrating from Python 2 are accustomed to being able to use the json module directly as a wire protocol module, but the strict Python 3 interpretation as a text transform means that isn't possible - you have to apply the text encoding step separately.

What appears to have happened is that the way JSON is used in practice has diverged from JSON as a formal spec.

Formal spec (this is what the Py3k JSON module implements, and Py2 implements with ensure_ascii=False): JSON is a Unicode text transform, which may optionally be serialised as UTF-8, UTF-16 or UTF-32.

Practice (what the Py2 JSON module implements with ensure_ascii=True, and what is covered in RFC 4627): JSON is a UTF-8 encoded wire protocol

So now we're left with the options:

- try to tweak the existing json APIs to handle both the str<->str and str<->bytes use cases (ugly)
- add new APIs within the existing json module
- add a new "jsonb" module, which dumps to UTF-8 encoded bytes, and reads from UTF-8, UTF-16 or UTF-32 encoded bytes in accordance with RFC 4627 (but being more tolerant in terms of what is allowed at the top level)

I'm currently leaning towards the "jsonb" module option, and deprecating the "encoding" argument in the pure text version. It's not pretty, but I think it's better than the alternatives.

----------
versions: +Python 3.5 -Python 3.3

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

From report at bugs.python.org  Sat Nov 30 16:16:50 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 30 Nov 2013 15:16:50 +0000
Subject: [docs] [issue16404] Uses of PyLong_FromLong that don't check for
	errors
In-Reply-To: <1352041027.23.0.922968343734.issue16404@psf.upfronthosting.co.za>
Message-ID: <1385824610.34.0.708107213025.issue16404@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Here is a patch. arraymodule.c is already fixed. Instead I found other bug in sysmodule.c. I'm not sure about extending.rst, PyLong_FromLong(0L) should never fail if NSMALLNEGINTS + NSMALLPOSINTS > 0.

----------
keywords: +patch
stage: needs patch -> patch review
versions:  -Python 3.2
Added file: http://bugs.python.org/file32908/issue16404.patch

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

From report at bugs.python.org  Sat Nov 30 16:39:26 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 30 Nov 2013 15:39:26 +0000
Subject: [docs] [issue16404] Uses of PyLong_FromLong that don't check for
	errors
In-Reply-To: <1352041027.23.0.922968343734.issue16404@psf.upfronthosting.co.za>
Message-ID: <1385825966.09.0.899108893741.issue16404@psf.upfronthosting.co.za>


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


Removed file: http://bugs.python.org/file32908/issue16404.patch

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

From report at bugs.python.org  Sat Nov 30 16:40:15 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 30 Nov 2013 15:40:15 +0000
Subject: [docs] [issue16404] Uses of PyLong_FromLong that don't check for
	errors
In-Reply-To: <1352041027.23.0.922968343734.issue16404@psf.upfronthosting.co.za>
Message-ID: <1385826015.15.0.705496324241.issue16404@psf.upfronthosting.co.za>


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


----------
components:  -Documentation, Interpreter Core
Added file: http://bugs.python.org/file32910/issue16404.patch

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

From report at bugs.python.org  Sat Nov 30 20:52:04 2013
From: report at bugs.python.org (Alexandre Vassalotti)
Date: Sat, 30 Nov 2013 19:52:04 +0000
Subject: [docs] [issue6673] Uncaught comprehension SyntaxError eats up all
	memory
In-Reply-To: <1249826985.41.0.2934011008.issue6673@psf.upfronthosting.co.za>
Message-ID: <1385841124.0.0.14989569067.issue6673@psf.upfronthosting.co.za>


Changes by Alexandre Vassalotti <alexandre at peadrop.com>:


----------
assignee:  -> docs at python
components: +Documentation -Interpreter Core
keywords:  -64bit
nosy: +docs at python
stage:  -> needs patch
type: resource usage -> enhancement
versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3

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

From report at bugs.python.org  Sat Nov 30 21:54:02 2013
From: report at bugs.python.org (Mark Lawrence)
Date: Sat, 30 Nov 2013 20:54:02 +0000
Subject: [docs] [issue19845] Compiling Python on Windows docs
Message-ID: <1385844842.4.0.324477828597.issue19845@psf.upfronthosting.co.za>


New submission from Mark Lawrence:

http://docs.python.org/3/using/windows.html#compiling-python-on-windows still refers to Visual Studio 97 but there's no mention of 2010.  Can we have this updated please?

----------
assignee: docs at python
components: Documentation
messages: 204844
nosy: BreamoreBoy, docs at python
priority: normal
severity: normal
status: open
title: Compiling Python on Windows docs
versions: Python 3.4

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

From report at bugs.python.org  Sat Nov 30 22:04:11 2013
From: report at bugs.python.org (Simon Weber)
Date: Sat, 30 Nov 2013 21:04:11 +0000
Subject: [docs] [issue19789] Improve wording of how to "undo" a call
	to	logging.disable(lvl)
In-Reply-To: <1385442860.38.0.88263802784.issue19789@psf.upfronthosting.co.za>
Message-ID: <1385845451.09.0.673337093064.issue19789@psf.upfronthosting.co.za>


Simon Weber added the comment:

That sounds much clearer. Thanks!

----------

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

From report at bugs.python.org  Sat Nov 30 23:23:56 2013
From: report at bugs.python.org (Zachary Ware)
Date: Sat, 30 Nov 2013 22:23:56 +0000
Subject: [docs] [issue19845] Compiling Python on Windows docs
In-Reply-To: <1385844842.4.0.324477828597.issue19845@psf.upfronthosting.co.za>
Message-ID: <1385850236.07.0.593647765108.issue19845@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


----------
nosy: +zach.ware

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

From report at bugs.python.org  Sat Nov 30 23:24:20 2013
From: report at bugs.python.org (Zachary Ware)
Date: Sat, 30 Nov 2013 22:24:20 +0000
Subject: [docs] [issue19845] Compiling Python on Windows docs
In-Reply-To: <1385844842.4.0.324477828597.issue19845@psf.upfronthosting.co.za>
Message-ID: <1385850260.22.0.0251564882557.issue19845@psf.upfronthosting.co.za>


Changes by Zachary Ware <zachary.ware at gmail.com>:


----------
keywords: +easy
stage:  -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Sat Nov 30 23:46:42 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 30 Nov 2013 22:46:42 +0000
Subject: [docs] [issue19789] Improve wording of how to "undo" a call
	to	logging.disable(lvl)
In-Reply-To: <1385442860.38.0.88263802784.issue19789@psf.upfronthosting.co.za>
Message-ID: <3dX74K4mx3z7Lk2@mail.python.org>


Roundup Robot added the comment:

New changeset b6377ca8087a by Vinay Sajip in branch '2.7':
Issue #19789: Clarified documentation for logging.disable.
http://hg.python.org/cpython/rev/b6377ca8087a

New changeset 5c8130b85c17 by Vinay Sajip in branch '3.3':
Issue #19789: Clarified documentation for logging.disable.
http://hg.python.org/cpython/rev/5c8130b85c17

New changeset eae4b83108fb by Vinay Sajip in branch 'default':
Closes #19789: Merged update from 3.3.
http://hg.python.org/cpython/rev/eae4b83108fb

----------
nosy: +python-dev
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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