From senthil at uthcode.com  Tue Oct  1 07:13:54 2013
From: senthil at uthcode.com (Senthil Kumaran)
Date: Mon, 30 Sep 2013 22:13:54 -0700
Subject: [docs] Typo in urlparse documentation
In-Reply-To: <CAMVLGWRMCPhj+PO+A1Ogrk3CCTR0szdMdCcKyfgWMssEBOkPRA@mail.gmail.com>
References: <CAMVLGWT7rF3Bmn4K5XXPNB8E_V8_ndfDBaUdEo=ettNg7tzeZQ@mail.gmail.com>
 <CAPOVWOR9NOpPkm1HE41DmvXibOWMqOGQBukcckW924FybEdEOg@mail.gmail.com>
 <CAMVLGWRMCPhj+PO+A1Ogrk3CCTR0szdMdCcKyfgWMssEBOkPRA@mail.gmail.com>
Message-ID: <CAPOVWOQx7b3U=HJbRZ5U8jF_8dYZN+x809m2GUD5VCx2yubrRw@mail.gmail.com>

Thanks for persisting.

Fixed this in:

changeset 70850d6a16ee
changeset 0e204fbb0b08
changeset 7ccc64db4abe



On Mon, Sep 30, 2013 at 12:09 AM, Omri Oren <omri at everything.me> wrote:

> Please run the line of code and you'll see the output doesn't contain ":80"
>
>
> *Omri Oren*   Algorithm Engineer  <omri at everything.me>omri at everything.me <http://corp.everything.me/>
> visit us at http://everything.me <http://corp.everything.me/>
> <https://play.google.com/store/apps/details?id=me.everything.launcher&referrer=utm_source%3Devme%26utm_medium%3Demailsig>
>
>
>
>
>
>
>
>
>
>
>
>
> On Sun, Sep 29, 2013 at 3:11 AM, Senthil Kumaran <senthil at uthcode.com>wrote:
>
>> Hi Omri,
>>
>> > should contain
>> >   "path='www.cwi.nl/%7Eguido/Python.html'"
>> > instead of
>> >   "path='www.cwi.nl:80/%7Eguido/Python.html'"
>>
>>
>> It does not matter in my opinion. Why do think think that the current
>> example is wrong?
>>
>> Thanks,
>> Senthil
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130930/f400bbbc/attachment.html>

From report at bugs.python.org  Tue Oct  1 09:14:23 2013
From: report at bugs.python.org (Graham Wideman)
Date: Tue, 01 Oct 2013 07:14:23 +0000
Subject: [docs] [issue19136] CSV, builtin open(),
	newline arg. Docs broken again.
Message-ID: <1380611663.89.0.558350750014.issue19136@psf.upfronthosting.co.za>


New submission from Graham Wideman:

The docs appear to be incorrect for CSV at: http://docs.python.org/3.3/library/csv.html.

Per issue http://bugs.python.org/issue7198 , there's a long history of contention between os.open and csv.writer, in which, on Windows, the default result is an unwanted additional '\r'. That was 'fixed' by using the newline='' argument to open(). 

This is reflected in the docs at the above link:

with open('eggs.csv', 'w', newline='') as csvfile:
    spamwriter = csv.writer(csvfile, delimiter=...)

However, in python 3.3.2 use of the newline argument returns: "TypeError: 'newline' is an invalid keyword argument for this function."

In brief testing, it appears that a correct result can be obtain by calling open as follows:

with open(somepath, 'wb') as writerfile: 
    writer = csv.writer(writerfile, delimiter=...)

Note: binary mode, not text as previously needed and currently documented.

----------
assignee: docs at python
components: Documentation
messages: 198752
nosy: docs at python, gwideman
priority: normal
severity: normal
status: open
title: CSV, builtin open(), newline arg. Docs broken again.
type: behavior
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Tue Oct  1 15:13:55 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 01 Oct 2013 13:13:55 +0000
Subject: [docs] [issue15964] SyntaxError in asdl when building 2.7 with
	system Python	3
In-Reply-To: <1347978379.29.0.810502621141.issue15964@psf.upfronthosting.co.za>
Message-ID: <3cq1C64R2Yz7LjN@mail.python.org>


Roundup Robot added the comment:

New changeset 56ed149e597a by Eli Bendersky in branch 'default':
Mention 'make touch' in the devguide.
http://hg.python.org/devguide/rev/56ed149e597a

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

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

From report at bugs.python.org  Tue Oct  1 15:27:41 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Tue, 01 Oct 2013 13:27:41 +0000
Subject: [docs] [issue15964] SyntaxError in asdl when building 2.7 with
	system Python	3
In-Reply-To: <1347978379.29.0.810502621141.issue15964@psf.upfronthosting.co.za>
Message-ID: <1380634061.38.0.284457480756.issue15964@psf.upfronthosting.co.za>


Eli Bendersky added the comment:

`make touch` was added to the bots in #19106 and is now also recommended in the devguide for folks running into this problem. IMHO this is all we need here, because there's no point toiling to make the auto-generation scripts in every version to work with any other version of Python. It's error prone and keeps us back (there's no reason not to use modern Python practices in the ASDL generator of 3.4, say, and instead cling to Python 2.4).

So I'm going to close this issue in a few days unless new feedback emerges.

----------

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

From report at bugs.python.org  Tue Oct  1 15:54:05 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 01 Oct 2013 13:54:05 +0000
Subject: [docs] [issue19136] CSV, builtin open(),
	newline arg. Docs broken again.
In-Reply-To: <1380611663.89.0.558350750014.issue19136@psf.upfronthosting.co.za>
Message-ID: <1380635645.75.0.809645885995.issue19136@psf.upfronthosting.co.za>


R. David Murray added the comment:

You must have a different 'open' in your namespace when you execute that.  Dropping a keyword argument like that is something we would never do without a deprecation period.

Your example works fine for me.

----------
nosy: +r.david.murray
resolution:  -> invalid
status: open -> closed

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

From report at bugs.python.org  Tue Oct  1 22:26:16 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 01 Oct 2013 20:26:16 +0000
Subject: [docs] [issue18512] sys.stdout.write does not allow bytes in Python
	3.x
In-Reply-To: <1374287481.36.0.643885131326.issue18512@psf.upfronthosting.co.za>
Message-ID: <1380659176.84.0.587722596454.issue18512@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Oct  1 22:58:29 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 01 Oct 2013 20:58:29 +0000
Subject: [docs] [issue19130] PCbuild/readme.txt not up-to-date
In-Reply-To: <1380473921.46.0.878582120992.issue19130@psf.upfronthosting.co.za>
Message-ID: <1380661109.56.0.628441749653.issue19130@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Thanks Christian!

----------
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
versions: +Python 3.3

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

From report at bugs.python.org  Wed Oct  2 00:01:08 2013
From: report at bugs.python.org (Graham Wideman)
Date: Tue, 01 Oct 2013 22:01:08 +0000
Subject: [docs] [issue19136] CSV, builtin open(),
	newline arg. Docs broken again.
In-Reply-To: <1380611663.89.0.558350750014.issue19136@psf.upfronthosting.co.za>
Message-ID: <1380664868.37.0.637252798374.issue19136@psf.upfronthosting.co.za>


Graham Wideman added the comment:

David:
Yes, as it turns out you are absolutely right, in a manner of speaking.  I have retested this exhaustively today, and here's the root cause.

It turns out that in testing, I must have activate a particular simplified test script by invoking only scriptname.py rather than invoking 'python scriptname.py'. (And then repeating that mistake by reinvoking via console history... doh!)

The latter reliably invokes python 3.3.2, because that's the only python in my PATH.  The former, it turns out, invokes the Windows Python Launcher, which finds a previously installed Python 2.7.1, despite that not being on the PATH. 

So, in my mind, the possibility of launching any version other than Python 3.3.2 did not enter the picture.

Prior to this, I was only vaguely aware that Windows Python Launcher existed. Ironically, it was probably installed by Python 3.3.2.

Sorry for the bogus bug alert.

----------

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

From report at bugs.python.org  Wed Oct  2 17:17:55 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Wed, 02 Oct 2013 15:17:55 +0000
Subject: [docs] [issue17827] Document codecs.encode and codecs.decode
In-Reply-To: <1366811140.15.0.0983174574305.issue17827@psf.upfronthosting.co.za>
Message-ID: <1380727075.31.0.0190327626693.issue17827@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

We should fix the docs for the earlier versions as well.

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

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

From report at bugs.python.org  Wed Oct  2 19:17:36 2013
From: report at bugs.python.org (Andrew Parker)
Date: Wed, 02 Oct 2013 17:17:36 +0000
Subject: [docs] [issue19147] pydoc3 fcntl.flock documentation gives wrong
	man page	section for flock
Message-ID: <1380734255.97.0.651100978858.issue19147@psf.upfronthosting.co.za>


New submission from Andrew Parker:

On my Linux system the docs for fcntl.flock gives me "man 3 flock" for more details:

    $ pydoc3 fcntl.flock
    Help on built-in function flock in fcntl:
    
    fcntl.flock = flock(...)
        flock(fd, operation)
    
        Perform the lock operation op on file descriptor fd.  See the Unix 
        manual page for flock(3) for details.  (On some systems, this function is
        emulated using fcntl().)

However, at least for Fedora 19 and RHEL 6, that should be "man 2 flock" or "See the manual page for flock(2) for details":

    $ man 3 flock | wc -l
    No manual entry for flock in section 3
    0
    $ man 2 flock | wc -l
    85

Note that http://docs.python.org/3/library/fcntl.html#fcntl.flock and http://docs.python.org/2/library/fcntl.html#fcntl.flock both have it right.

----------
assignee: docs at python
components: Documentation
messages: 198856
nosy: Andrew.Parker, docs at python
priority: normal
severity: normal
status: open
title: pydoc3 fcntl.flock documentation gives wrong man page section for flock
versions: Python 2.6, Python 2.7, Python 3.3

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

From report at bugs.python.org  Wed Oct  2 21:22:32 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 02 Oct 2013 19:22:32 +0000
Subject: [docs] [issue19147] pydoc3 fcntl.flock documentation gives wrong
	man page	section for flock
In-Reply-To: <1380734255.97.0.651100978858.issue19147@psf.upfronthosting.co.za>
Message-ID: <3cqnKz5QRQz7LjN@mail.python.org>


Roundup Robot added the comment:

New changeset 43064ded64cb by Ned Deily in branch '2.7':
Issue #19147: Fix docstring for fcntl.flock to refer to correct man section.
http://hg.python.org/cpython/rev/43064ded64cb

New changeset 735d8b856928 by Ned Deily in branch '3.3':
Issue #19147: Fix docstring for fcntl.flock to refer to correct man section.
http://hg.python.org/cpython/rev/735d8b856928

New changeset 1cb0c05d71af by Ned Deily in branch 'default':
Issue #19147: merge from 3.3
http://hg.python.org/cpython/rev/1cb0c05d71af

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

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

From report at bugs.python.org  Wed Oct  2 21:23:42 2013
From: report at bugs.python.org (Ned Deily)
Date: Wed, 02 Oct 2013 19:23:42 +0000
Subject: [docs] [issue19147] pydoc3 fcntl.flock documentation gives wrong
	man page	section for flock
In-Reply-To: <1380734255.97.0.651100978858.issue19147@psf.upfronthosting.co.za>
Message-ID: <1380741822.9.0.975305774784.issue19147@psf.upfronthosting.co.za>


Ned Deily added the comment:

Thanks for the report!

----------
nosy: +ned.deily
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
versions: +Python 3.4 -Python 2.6

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

From report at bugs.python.org  Wed Oct  2 22:29:21 2013
From: report at bugs.python.org (Esa Peuha)
Date: Wed, 02 Oct 2013 20:29:21 +0000
Subject: [docs] [issue19148] Minor issues with Enum docs
Message-ID: <1380745761.79.0.183004061407.issue19148@psf.upfronthosting.co.za>


New submission from Esa Peuha:

I noticed a couple of issues with the Enum documentation. First, there are some markup bugs which should be fixed by the attached file. Second, I think "If the only change desired is no aliases allowed" is very bad English and should be reworded; I would go with "If you only want to disallow aliases" but maybe other people have better ideas.

----------
assignee: docs at python
components: Documentation
files: enum.diff
keywords: patch
messages: 198869
nosy: Esa.Peuha, docs at python
priority: normal
severity: normal
status: open
title: Minor issues with Enum docs
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file31947/enum.diff

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

From report at bugs.python.org  Wed Oct  2 23:23:38 2013
From: report at bugs.python.org (Ethan Furman)
Date: Wed, 02 Oct 2013 21:23:38 +0000
Subject: [docs] [issue19148] Minor issues with Enum docs
In-Reply-To: <1380745761.79.0.183004061407.issue19148@psf.upfronthosting.co.za>
Message-ID: <1380749018.37.0.972290407006.issue19148@psf.upfronthosting.co.za>


Changes by Ethan Furman <ethan at stoneleaf.us>:


----------
nosy: +ethan.furman

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

From report at bugs.python.org  Thu Oct  3 08:30:13 2013
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 03 Oct 2013 06:30:13 +0000
Subject: [docs] [issue19148] Minor issues with Enum docs
In-Reply-To: <1380745761.79.0.183004061407.issue19148@psf.upfronthosting.co.za>
Message-ID: <1380781813.81.0.781220946111.issue19148@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Patch LGTM.

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

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

From report at bugs.python.org  Fri Oct  4 03:36:13 2013
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Fri, 04 Oct 2013 01:36:13 +0000
Subject: [docs] [issue19160] Inconsistent size for GIL release in hashlib
Message-ID: <1380850573.19.0.333542059882.issue19160@psf.upfronthosting.co.za>


New submission from Jes?s Cea Avi?n:

In http://docs.python.org/3.3/library/hashlib.html there is a contradiction:

"""
For better multithreading performance, the Python GIL is released for strings of more than 2047 bytes at object creation or on update.

[...]

Changed in version 3.1: The Python GIL is released to allow other threads to run while hash updates on data larger than 2048 bytes is taking place when using hash algorithms supplied by OpenSSL.
"""

So is it 2047 or 2048? :)

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 198930
nosy: docs at python, jcea
priority: normal
severity: normal
status: open
title: Inconsistent size for GIL release in hashlib
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Oct  4 03:57:46 2013
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 04 Oct 2013 01:57:46 +0000
Subject: [docs] [issue19160] Inconsistent size for GIL release in hashlib
In-Reply-To: <1380850573.19.0.333542059882.issue19160@psf.upfronthosting.co.za>
Message-ID: <1380851866.7.0.712828610562.issue19160@psf.upfronthosting.co.za>


Berker Peksag added the comment:

It looks like it is 2048: http://hg.python.org/cpython/rev/f9f5d9047a05/

See also issue 4751.

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

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

From report at bugs.python.org  Fri Oct  4 04:12:49 2013
From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=)
Date: Fri, 04 Oct 2013 02:12:49 +0000
Subject: [docs] [issue19160] Inconsistent size for GIL release in hashlib
In-Reply-To: <1380850573.19.0.333542059882.issue19160@psf.upfronthosting.co.za>
Message-ID: <1380852769.14.0.547778102851.issue19160@psf.upfronthosting.co.za>


Jes?s Cea Avi?n added the comment:

For extra safety, I just checked the source of 3.4:

"""
#define HASHLIB_GIL_MINSIZE 2048

[...]

if (self->lock == NULL && view.len >= HASHLIB_GIL_MINSIZE) {

[...]

if (view.len >= HASHLIB_GIL_MINSIZE) {

[...]

if (len >= HASHLIB_GIL_MINSIZE) {
"""

So, yes, the GIL is released if len >= 2048 bytes.

BTW, in Python 3.x hashes can't be calculated on strings, but bytes.

I take care of this. Commit in 5 minutes.

----------
assignee: docs at python -> jcea

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

From report at bugs.python.org  Fri Oct  4 04:16:06 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 04 Oct 2013 02:16:06 +0000
Subject: [docs] [issue19160] Inconsistent size for GIL release in hashlib
In-Reply-To: <1380850573.19.0.333542059882.issue19160@psf.upfronthosting.co.za>
Message-ID: <3crZSk0WTFz7LjW@mail.python.org>


Roundup Robot added the comment:

New changeset 310c26df3234 by Jesus Cea in branch '3.3':
Close #19160: Inconsistent size for GIL release in hashlib
http://hg.python.org/cpython/rev/310c26df3234

New changeset 9503097ce1b7 by Jesus Cea in branch 'default':
MERGE: Close #19160: Inconsistent size for GIL release in hashlib
http://hg.python.org/cpython/rev/9503097ce1b7

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

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

From report at bugs.python.org  Fri Oct  4 04:21:23 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 04 Oct 2013 02:21:23 +0000
Subject: [docs] [issue19160] Inconsistent size for GIL release in hashlib
In-Reply-To: <1380850573.19.0.333542059882.issue19160@psf.upfronthosting.co.za>
Message-ID: <3crZZp2DzNz7LjS@mail.python.org>


Roundup Robot added the comment:

New changeset bfebfadfc4aa by Jesus Cea in branch '3.3':
Close #19160: Inconsistent size for GIL release in hashlib
http://hg.python.org/cpython/rev/bfebfadfc4aa

New changeset 989ea05b2500 by Jesus Cea in branch 'default':
MERGE: Close #19160: Inconsistent size for GIL release in hashlib
http://hg.python.org/cpython/rev/989ea05b2500

----------

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

From report at bugs.python.org  Fri Oct  4 13:09:58 2013
From: report at bugs.python.org (hiroaki itoh)
Date: Fri, 04 Oct 2013 11:09:58 +0000
Subject: [docs] [issue19163] PyString_Format with dict
Message-ID: <1380884998.67.0.733002313929.issue19163@psf.upfronthosting.co.za>


New submission from hiroaki itoh:

http://docs.python.org/2.7/c-api/string.html#PyString_Format

The documents says `The args argument must be a tuple.',
But if format is like '%(key)s', PyString_Format claims
args must be mapping protocol.
(At least 2.7.3.)

----------
assignee: docs at python
components: Documentation
messages: 198942
nosy: docs at python, xwhhsprings
priority: normal
severity: normal
status: open
title: PyString_Format with dict
type: behavior
versions: Python 2.7

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

From report at bugs.python.org  Fri Oct  4 13:18:10 2013
From: report at bugs.python.org (Marco Buccini)
Date: Fri, 04 Oct 2013 11:18:10 +0000
Subject: [docs] [issue19164] Update uuid.UUID TypeError exception: integer
	should not	be an argument.
Message-ID: <1380885490.13.0.480584034262.issue19164@psf.upfronthosting.co.za>


New submission from Marco Buccini:

When you try to use uuid.UUID() without arguments you get a TypeError exception saying that you can actually use an integer (while you cannot). 

Python 2.6.8 (default, Apr 26 2013, 16:24:53) 
[GCC 4.6.3] on linux2
>>> uuid.UUID()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.6/uuid.py", line 129, in __init__
    raise TypeError('need one of hex, bytes, bytes_le, fields, or int')
TypeError: need one of hex, bytes, bytes_le, fields, or int

>>> uuid.UUID(uuid.uuid4().int)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.6/uuid.py", line 131, in __init__
    hex = hex.replace('urn:', '').replace('uuid:', '')
AttributeError: 'long' object has no attribute 'replace'

So, let's check with an integer - maybe an int has 'replace'.
>>> uuid.UUID(1231231)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.6/uuid.py", line 131, in __init__
    hex = hex.replace('urn:', '').replace('uuid:', '')
AttributeError: 'int' object has no attribute 'replace'

No, it doesn't. Anyway, with a propery hex value, it works (of course!).

>>> uuid.UUID(uuid.uuid4().hex)
UUID('89b1283d-c32e-4b8a-a9e3-a699445fdd4d')

----------
assignee: docs at python
components: Documentation
messages: 198943
nosy: docs at python, makronized
priority: normal
severity: normal
status: open
title: Update uuid.UUID TypeError exception: integer should not be an argument.
type: behavior
versions: Python 2.6

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

From report at bugs.python.org  Fri Oct  4 15:01:10 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Fri, 04 Oct 2013 13:01:10 +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: <1380891670.1.0.384800629586.issue19164@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

The exception message is correct. You can give an integer argument. But you have to use keyword argument.

>>> uuid.UUID(int=uuid.uuid4().int)
UUID('62ad61e5-b492-4f01-81e6-790049051c4f')

>From the documentation:

 __init__(self, hex=None, bytes=None, bytes_le=None, fields=None, int=None, v
ersion=None)
 |      Create a UUID from either a string of 32 hexadecimal digits,
 |      a string of 16 bytes as the 'bytes' argument, a string of 16 bytes
 |      in little-endian order as the 'bytes_le' argument, a tuple of six
 |      integers (32-bit time_low, 16-bit time_mid, 16-bit time_hi_version,
 |      8-bit clock_seq_hi_variant, 8-bit clock_seq_low, 48-bit node) as
 |      the 'fields' argument, or a single 128-bit integer as the 'int'
 |      argument.  When a string of hex digits is given, curly braces,
 |      hyphens, and a URN prefix are all optional.  For example, these
 |      expressions all yield the same UUID:

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

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

From report at bugs.python.org  Fri Oct  4 16:55:27 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 04 Oct 2013 14:55:27 +0000
Subject: [docs] [issue19163] PyString_Format with dict
In-Reply-To: <1380884998.67.0.733002313929.issue19163@psf.upfronthosting.co.za>
Message-ID: <3crvJt3GMxz7LjY@mail.python.org>


Roundup Robot added the comment:

New changeset 405245885569 by Benjamin Peterson in branch '2.7':
dict is also allowed (closes #19163)
http://hg.python.org/cpython/rev/405245885569

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

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

From report at bugs.python.org  Fri Oct  4 17:12:44 2013
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 04 Oct 2013 15:12:44 +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: <1380899564.65.0.945840530165.issue19164@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Yeah, the first message should probably say "one of the hex, bytes, bytes_le, fields, or int arguments must be given"

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

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

From report at bugs.python.org  Fri Oct  4 22:05:41 2013
From: report at bugs.python.org (Phil Connell)
Date: Fri, 04 Oct 2013 20:05:41 +0000
Subject: [docs] [issue16195] Difficult or impossible to figure out how
	garbage	collector and weak references should interact for
	user-defined	extension types
In-Reply-To: <1349961021.39.0.560161023056.issue16195@psf.upfronthosting.co.za>
Message-ID: <1380917141.51.0.386019397471.issue16195@psf.upfronthosting.co.za>


Changes by Phil Connell <pconnell at gmail.com>:


----------
nosy: +pconnell

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

From report at bugs.python.org  Fri Oct  4 22:40:03 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 04 Oct 2013 20:40:03 +0000
Subject: [docs] [issue19153] Embedding into a shared library fails again
In-Reply-To: <1380818213.13.0.0445211197564.issue19153@psf.upfronthosting.co.za>
Message-ID: <1380919202.97.0.992278141108.issue19153@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Ok, making it a documentation issue in case it deserves clarification in the docs.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python

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

From report at bugs.python.org  Sat Oct  5 02:31:32 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 05 Oct 2013 00:31:32 +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: <1380933092.19.0.924543020096.issue19164@psf.upfronthosting.co.za>


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


----------
keywords: +easy
nosy: +ezio.melotti
stage:  -> needs patch
versions: +Python 2.7 -Python 2.6

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

From report at bugs.python.org  Sat Oct  5 03:10:00 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 05 Oct 2013 01:10:00 +0000
Subject: [docs] [issue19124] os.execv executes in background on Windows
In-Reply-To: <1380451602.11.0.517013085188.issue19124@psf.upfronthosting.co.za>
Message-ID: <1380935400.26.0.447239402339.issue19124@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

In general, os module functions lightly wrap the corresponding operating system calls. It does not mask differences between OSes, or between versions of an OS. So the unix-windows difference is not a bug and the behavior will not change. 

The difference could, however, be described succinctly in the doc. In the first paragraph, after "On Unix, the new executable is loaded into the current process, and will have the same process id as the caller.", we could add something like

On Windows, the new process is executed in the background but can send output to a console if the original process was started in a console.

This has to be worded carefully because the process could instead have been started from an icon, including in Start Menu or Windows Explorer.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python, terry.reedy
stage: committed/rejected -> needs patch
versions: +Python 3.4

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

From report at bugs.python.org  Sat Oct  5 03:11:02 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 05 Oct 2013 01:11:02 +0000
Subject: [docs] [issue19129] 6.2.1. Regular Expression Syntax flags
In-Reply-To: <1380470947.27.0.0292455287204.issue19129@psf.upfronthosting.co.za>
Message-ID: <1380935462.18.0.849390371309.issue19129@psf.upfronthosting.co.za>


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


----------
stage:  -> needs patch
versions: +Python 2.7, Python 3.4

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

From report at bugs.python.org  Sat Oct  5 03:13:45 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 05 Oct 2013 01:13:45 +0000
Subject: [docs] [issue19148] Minor issues with Enum docs
In-Reply-To: <1380745761.79.0.183004061407.issue19148@psf.upfronthosting.co.za>
Message-ID: <3cs92J34LtzQKr@mail.python.org>


Roundup Robot added the comment:

New changeset db94fc7218fa by Ezio Melotti in branch 'default':
#19148: fix markup errors and wording in enum docs.  Patch by Esa Peuha.
http://hg.python.org/cpython/rev/db94fc7218fa

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

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

From report at bugs.python.org  Sat Oct  5 03:16:10 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 05 Oct 2013 01:16:10 +0000
Subject: [docs] [issue19148] Minor issues with Enum docs
In-Reply-To: <1380745761.79.0.183004061407.issue19148@psf.upfronthosting.co.za>
Message-ID: <1380935770.54.0.154560228635.issue19148@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report and the patch!
I used a slightly different wording than the one you suggested because the rest of the document doesn't seem to use "you".

----------
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/issue19148>
_______________________________________

From report at bugs.python.org  Sat Oct  5 05:12:15 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 05 Oct 2013 03:12:15 +0000
Subject: [docs] [issue19129] 6.2.1. Regular Expression Syntax flags
In-Reply-To: <1380470947.27.0.0292455287204.issue19129@psf.upfronthosting.co.za>
Message-ID: <1380942735.85.0.705330030794.issue19129@psf.upfronthosting.co.za>


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


----------
keywords: +easy
type:  -> enhancement
versions:  -Python 2.7

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

From report at bugs.python.org  Sat Oct  5 10:27:09 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Sat, 05 Oct 2013 08:27:09 +0000
Subject: [docs] [issue19121] Documentation guidelines enhancements
In-Reply-To: <1380446758.24.0.414615784712.issue19121@psf.upfronthosting.co.za>
Message-ID: <1380961629.04.0.659150392456.issue19121@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/issue19121>
_______________________________________

From report at bugs.python.org  Sat Oct  5 11:56:16 2013
From: report at bugs.python.org (Stefan Behnel)
Date: Sat, 05 Oct 2013 09:56:16 +0000
Subject: [docs] [issue16195] Difficult or impossible to figure out how
	garbage	collector and weak references should interact for
	user-defined	extension types
In-Reply-To: <1349961021.39.0.560161023056.issue16195@psf.upfronthosting.co.za>
Message-ID: <1380966976.85.0.716582330096.issue16195@psf.upfronthosting.co.za>


Stefan Behnel added the comment:

Just as a quick update here: Cython has since then switched to only using PyObject_ClearWeakRefs() and otherwise leaves the handling of the weakref slot to CPython.

----------

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

From report at bugs.python.org  Sat Oct  5 13:58:54 2013
From: report at bugs.python.org (CliffM)
Date: Sat, 05 Oct 2013 11:58:54 +0000
Subject: [docs] [issue19121] Documentation guidelines enhancements
In-Reply-To: <1380446758.24.0.414615784712.issue19121@psf.upfronthosting.co.za>
Message-ID: <1380974334.44.0.503618374545.issue19121@psf.upfronthosting.co.za>


CliffM added the comment:

Improving documentation is a fine aim.  However,  finding the correct balance between reference, tuition and precis (i.e. overview) is tricky.

I would like to see more documentation laid out with the code and tests.  This at least binds the examples with running code.

I am sure this has been asked already, but has anyone done an analysis of the web-server log  for the documentation sites ?

----------
nosy: +CliffM

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

From report at bugs.python.org  Sat Oct  5 15:43:41 2013
From: report at bugs.python.org (Santosh Kumar)
Date: Sat, 05 Oct 2013 13:43:41 +0000
Subject: [docs] [issue19129] 6.2.1. Regular Expression Syntax flags
In-Reply-To: <1380470947.27.0.0292455287204.issue19129@psf.upfronthosting.co.za>
Message-ID: <1380980621.29.0.243900841013.issue19129@psf.upfronthosting.co.za>


Changes by Santosh Kumar <san00718 at gmail.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file31963/re_u.patch

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

From report at bugs.python.org  Sat Oct  5 23:21:33 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 05 Oct 2013 21:21:33 +0000
Subject: [docs] [issue19060] docs: note that subprocess doesn't replace
	os.exec*
In-Reply-To: <1379748595.57.0.00736365306091.issue19060@psf.upfronthosting.co.za>
Message-ID: <1381008093.01.0.757297846983.issue19060@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
stage:  -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Sat Oct  5 23:40:29 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 05 Oct 2013 21:40:29 +0000
Subject: [docs] [issue19068] Some built-in complex docstrings are not PEP-8
	compatible
In-Reply-To: <1379833742.32.0.289149108308.issue19068@psf.upfronthosting.co.za>
Message-ID: <3cshFn09tMz7LjT@mail.python.org>


Roundup Robot added the comment:

New changeset 54213ef5bb19 by Ezio Melotti in branch '3.3':
#19068: use imperative mood in complex object docstrings.  Patch by Marco Buttu.
http://hg.python.org/cpython/rev/54213ef5bb19

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

New changeset 3ef157674abc by Ezio Melotti in branch '2.7':
#19068: use imperative mood in complex object docstrings.  Patch by Marco Buttu.
http://hg.python.org/cpython/rev/3ef157674abc

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

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

From report at bugs.python.org  Sat Oct  5 23:40:30 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 05 Oct 2013 21:40:30 +0000
Subject: [docs] [issue19067] Built-in range docstrings are not PEP-8
	compatible
In-Reply-To: <1379833275.25.0.770459256521.issue19067@psf.upfronthosting.co.za>
Message-ID: <3cshFn5ZjVz7LkD@mail.python.org>


Roundup Robot added the comment:

New changeset 5135a431f7b3 by Ezio Melotti in branch '3.3':
#19067: use imperative mood in range object docstrings.  Patch by Marco Buttu.
http://hg.python.org/cpython/rev/5135a431f7b3

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

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

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

From report at bugs.python.org  Sat Oct  5 23:41:27 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 05 Oct 2013 21:41:27 +0000
Subject: [docs] [issue19067] Built-in range docstrings are not PEP-8
	compatible
In-Reply-To: <1379833275.25.0.770459256521.issue19067@psf.upfronthosting.co.za>
Message-ID: <1381009287.89.0.0568269645647.issue19067@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the patch!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sat Oct  5 23:42:01 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 05 Oct 2013 21:42:01 +0000
Subject: [docs] [issue19068] Some built-in complex docstrings are not PEP-8
	compatible
In-Reply-To: <1379833742.32.0.289149108308.issue19068@psf.upfronthosting.co.za>
Message-ID: <1381009321.73.0.76420690039.issue19068@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the patch!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
versions: +Python 2.7, Python 3.4 -Python 3.2

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

From report at bugs.python.org  Sat Oct  5 23:47:26 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 05 Oct 2013 21:47:26 +0000
Subject: [docs] [issue19069] Built-in float docstrings are not PEP-8
	compatible
In-Reply-To: <1379834291.01.0.660875879281.issue19069@psf.upfronthosting.co.za>
Message-ID: <3cshPn2XKtz7LjM@mail.python.org>


Roundup Robot added the comment:

New changeset ca8e75190402 by Ezio Melotti in branch '2.7':
#19069: use imperative mood in float object docstrings.  Patch by Marco Buttu.
http://hg.python.org/cpython/rev/ca8e75190402

New changeset 563074ace473 by Ezio Melotti in branch '3.3':
#19069: use imperative mood in float object docstrings.  Patch by Marco Buttu.
http://hg.python.org/cpython/rev/563074ace473

New changeset 63a10c942b50 by Ezio Melotti in branch 'default':
#19069: merge with 3.3.
http://hg.python.org/cpython/rev/63a10c942b50

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

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

From report at bugs.python.org  Sat Oct  5 23:48:40 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 05 Oct 2013 21:48:40 +0000
Subject: [docs] [issue19069] Built-in float docstrings are not PEP-8
	compatible
In-Reply-To: <1379834291.01.0.660875879281.issue19069@psf.upfronthosting.co.za>
Message-ID: <1381009720.03.0.923368751568.issue19069@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the patch!

----------
assignee: docs at python -> ezio.melotti
nosy: +ezio.melotti
resolution: duplicate -> fixed
stage:  -> committed/rejected
versions: +Python 2.7, Python 3.4 -Python 3.2

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

From report at bugs.python.org  Sun Oct  6 00:02:33 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 05 Oct 2013 22:02:33 +0000
Subject: [docs] [issue19074] Add PySide to GUI FAQ
In-Reply-To: <1379859377.69.0.892253164041.issue19074@psf.upfronthosting.co.za>
Message-ID: <3cshlD2TzmzQN7@mail.python.org>


Roundup Robot added the comment:

New changeset eddd46b5691a by Ezio Melotti in branch '2.7':
#19074: mention PySide in the GUI FAQs.
http://hg.python.org/cpython/rev/eddd46b5691a

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

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

From report at bugs.python.org  Sun Oct  6 00:03:49 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 05 Oct 2013 22:03:49 +0000
Subject: [docs] [issue19074] Add PySide to GUI FAQ
In-Reply-To: <1379859377.69.0.892253164041.issue19074@psf.upfronthosting.co.za>
Message-ID: <1381010629.17.0.356208362234.issue19074@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I backported the relevant text from ccfb5ba50a44.

----------
assignee: docs at python -> ezio.melotti
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
type:  -> enhancement
versions:  -Python 3.3, Python 3.4

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

From report at bugs.python.org  Sun Oct  6 01:38:19 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 05 Oct 2013 23:38:19 +0000
Subject: [docs] [issue19024] Document asterisk (*), splat or star operator
In-Reply-To: <1379251118.66.0.684713404389.issue19024@psf.upfronthosting.co.za>
Message-ID: <1381016299.68.0.476857034303.issue19024@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

> 223 people + me out of 1422 disagree with you both.

Note that those votes doesn't necessarily mean "I didn't know about the feature" -- they might mean "I find this feature useful/I like this feature".  Features like decorators have even more votes and I don't think they are "hidden" features.

> Current page
 http://docs.python.org/3/tutorial/controlflow.html#unpacking-argument-lists is
> about functionality, not about operators

These operators are documented here:
http://docs.python.org/3/reference/expressions.html#index-36
http://docs.python.org/3/reference/expressions.html#index-37
This can be found from the doc index (which admittedly is not the most obvious place where to look):
http://docs.python.org/3/genindex-Symbols.html

If the problem is the content of the docs, you can suggest what exactly should be improved (and how).  If the problem is the discoverability, you should open a separate issue on the Sphinx bug tracker about allowing the search of operators.

----------

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

From report at bugs.python.org  Sun Oct  6 01:42:58 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 05 Oct 2013 23:42:58 +0000
Subject: [docs] [issue19055] Regular expressions: * does not match as
	many	repetitions as possible.
In-Reply-To: <1379629723.54.0.556911663587.issue19055@psf.upfronthosting.co.za>
Message-ID: <1381016578.89.0.0664704693672.issue19055@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation
keywords: +easy
nosy: +docs at python
stage:  -> needs patch
type: behavior -> enhancement

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

From report at bugs.python.org  Sun Oct  6 06:14:25 2013
From: report at bugs.python.org (David Chambers)
Date: Sun, 06 Oct 2013 04:14:25 +0000
Subject: [docs] [issue19175] Erroneous reference to "integer" in format
	string grammar
Message-ID: <1381032864.93.0.113807397977.issue19175@psf.upfronthosting.co.za>


New submission from David Chambers:

I first raised this issue on Stack Overflow: http://stackoverflow.com/questions/19203194

The [replacement field grammar][1] states that an [integer][2] is a valid field_name, but this is inaccurate:

    >>> '{0}'.format('zero')
    'zero'
    >>> '{0x0}.format('zero')
    KeyError: '0x0'
    >>> '{0o0}.format('zero')
    KeyError: '0o0'
    >>> '{0b0}.format('zero')
    KeyError: '0b0'

This [comment][3] by Eric Smith suggests that the above is the intended behaviour:

> get_integer uses the narrowest possible definition for integer indexes,
> in order to pass all other strings to mappings.

The documentation should be updated to match the actual behaviour. abarnert on Stack Overflow suggested the following change:

    -arg_name          ::=  [identifier | integer]
    +arg_name          ::=  [identifier | digit+]


[1]: http://docs.python.org/2/library/string.html#format-string-syntax
[2]: http://docs.python.org/2/reference/lexical_analysis.html#grammar-token-integer
[3]: http://bugs.python.org/issue8985#msg107705

----------
assignee: docs at python
components: Documentation
messages: 199024
nosy: davidchambers, docs at python
priority: normal
severity: normal
status: open
title: Erroneous reference to "integer" in format string grammar
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/issue19175>
_______________________________________

From report at bugs.python.org  Sun Oct  6 08:46:03 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 06:46:03 +0000
Subject: [docs] [issue19175] Erroneous reference to "integer" in format
	string grammar
In-Reply-To: <1381032864.93.0.113807397977.issue19175@psf.upfronthosting.co.za>
Message-ID: <1381041963.17.0.451783912678.issue19175@psf.upfronthosting.co.za>


Georg Brandl added the comment:

The bug is that "integer" links to the "integer" production in the Python grammar.  This shouldn't happen; I'll have a look on the Sphinx side.

As a workaround, "integer" can be replaced by "digit+" as requested (it occurs twice).

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

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

From report at bugs.python.org  Sun Oct  6 08:46:10 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 06:46:10 +0000
Subject: [docs] [issue19175] Erroneous reference to "integer" in format
	string grammar
In-Reply-To: <1381032864.93.0.113807397977.issue19175@psf.upfronthosting.co.za>
Message-ID: <1381041970.49.0.920529749197.issue19175@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
assignee: docs at python -> eric.smith
nosy: +eric.smith

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

From report at bugs.python.org  Sun Oct  6 08:59:12 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 06:59:12 +0000
Subject: [docs] [issue11176] give more meaningful argument names in
	argparse	documentation
In-Reply-To: <1297352937.46.0.470038569364.issue11176@psf.upfronthosting.co.za>
Message-ID: <1381042751.86.0.481088913858.issue11176@psf.upfronthosting.co.za>


Georg Brandl added the comment:

> Also see this e-mail to docs@:
> http://mail.python.org/pipermail/docs/2012-December/012028.html

No, please don't see this e-mail.  It's not worth it.  The poster clearly has no clue whatsoever about either a) common placeholders, or b) manners.

I don't want to claim that foo/bar/etc. are superior to a well-thought-out example (which takes time to come up with), but they are certainly better than no example at all.

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

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

From georg at python.org  Sun Oct  6 09:04:31 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:04:31 +0200
Subject: [docs] bug in documentation
In-Reply-To: <CAEgVYQT+bWM-vuTf53ye5prYHDx5+sw+aU1epDQfmxP_6oJUMQ@mail.gmail.com>
References: <CAEgVYQT+bWM-vuTf53ye5prYHDx5+sw+aU1epDQfmxP_6oJUMQ@mail.gmail.com>
Message-ID: <52510B7F.70005@python.org>

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

Am 18.09.2013 08:46, schrieb Rajesh Panigrahi:
> Hello Team, There need a small correction in documentation page for
> 
> "14. Floating Point Arithmetic: Issues and Limitations"
> 
> 
> Issue Description:- It has been written 0/2 + 0/4 + 1/8 = 0.001.
> 
> Expected :- The mathematical calculation should be written as 0.125.
> 
> Due to some problem i am not able to attach the screen shot.

Hi Rajesh,

the "0.001" here is a *binary* fraction, not a decimal fraction.  (It is
stated in the next sentence that the two example fractions are of the
same value.)  Therefore the documentation is correct.

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

iEYEARECAAYFAlJRC38ACgkQN9GcIYhpnLAo8gCeKcDF4WWGkvFp3phyyZ4H+fmU
XNMAn1a97h7UDWcvxx3VhAF9dNpRfGM2
=wvQD
-----END PGP SIGNATURE-----

From artur.krzysztof.fornal at gmail.com  Tue Oct  1 12:35:15 2013
From: artur.krzysztof.fornal at gmail.com (Artur Fornal)
Date: Tue, 01 Oct 2013 12:35:15 +0200
Subject: [docs] Python Docs Mobile
Message-ID: <qkbmdng0ha5ns2w2hrimrdty.1380620298806@email.android.com>

Hello ;)

I want to prepare my own few mobile apps for Android OS and firstly I think about mobile app with Python documentation for versions 2.6, 2.7, 3.2, 3.3, 3.4. 
Here I have question to You, can I use Yours python icon and docs inside this app, is it possible without any license problems? I want to make it completely free, no ads, no statistic. Should be very fast and easy to use. 
If You have any questions about details please ask;)

Artur Fornal

From w at felixhandte.com  Wed Oct  2 06:27:03 2013
From: w at felixhandte.com (W. Felix Handte)
Date: Wed, 02 Oct 2013 00:27:03 -0400
Subject: [docs] SSL Module Documentation Broken Link
Message-ID: <524BA097.7030503@felixhandte.com>

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

Howdy,

The page for the ssl module in the documentation for most Python
versions, ("http://docs.python.org/" + s + "/library/ssl.html" for s
in ("2.7", "3.2", "3.3", "3.4")), links to
http://www3.rad.com/networks/applications/secure/tls.htm in the See
Also section, under the title "TLS (Transport Layer Security) and SSL
(Secure Socket Layer)". That URL doesn't resolve, and replacing the
"www3." with "www." doesn't fix it either. It should be removed, I guess.

Thanks for your dedication to a wonderful project!,
Felix Handte

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJSS6COAAoJEKdBXzVr1+nzyfIP/0OPcN2DPJfWvbAdWrUwj+Qo
iGTJfOITf1UpH/tt0Xl8QaO0lfG/S9DQnrGoSk8E4IZYncZqvKabBHqtlmMVQrJW
x8Of5AtnXntAeEQUW8b8kRagsW3O1GclLdd+HhnbSsN61bECqxzcGAn0Ql6rY6Ls
52n76iXUdhUs7CKuxhSLfvQA52nYMybEy7dnWnwJvnOVdWeg97GRbUpJLPtEaua6
881qbXVOhL55IhCfnpGWXYzMoUj0S6NgAw0u72rObdzRVNvaDY8NST+jecfcIdsB
LABFou5P2NVRV1kTz9sLYlxjUsVVJRALR7kV84uKwLptZ2hT0FyQDMfRkS6HIiHE
U23BigiVo3NgO4gsh2dcW1HK+gCdj7p0rne9+ga5JrlVLHyxxlpBQXF2UeoTFcHH
EV0UT/93Bh4jLo0HlBueyEltR2Ipjz4SP7gVapEn+H0nEcMvKGzydKBDl17Rabca
zXrsIOMZpuNXZ81EjlknjI/9iEgA6K9pl+qz2GIvGpZgsgrI2K0gC3N0SuUF0eWc
LuyQ8GwANVpMztwcR16m8i3NyxbJv/kzqNeCbZN4+CXlxbs8qfhZ+/deMRqQDl0w
HdNubqzPwi2bOjEt3ZvDS3e3mqfLomqmQGo25LHqeYw47PmUVB7zci7OC2PLPGI9
yxRIljWuXNWQJktvIBRs
=BQd+
-----END PGP SIGNATURE-----

From grupobetatesting at gmail.com  Thu Oct  3 06:29:34 2013
From: grupobetatesting at gmail.com (Sofware Libre)
Date: Thu, 3 Oct 2013 01:29:34 -0300
Subject: [docs] Pithon Bug Report
Message-ID: <CAB7xb6Lq0q2=Xq0O7pjA1WuyUnb1T5pnLO7Nc9-KZafmuAd+3A@mail.gmail.com>

Hello! My name is Martin, a member of Free Software in Comahue National
University of Neuqu?n, Argentina. We have detected an error in the compiler
for Python 2.7 using Ubuntu 12.04: I write the code, without realizing I
leave a comment with syntax error in that line (do not put the # of
comments), compile and get error of sistaxis in that line. Fix the error
adding # to comment, I do compile again and it shows me various errors that
take over the Python compiler and I am forced to close it. Hope your
response with a possible solution to this problem, my idea is to continue
using this version of Python. Thank you!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131003/6d630d5b/attachment.html>

From cclauss at bluewin.ch  Sat Oct  5 07:50:55 2013
From: cclauss at bluewin.ch (Christian Clauss)
Date: Sat, 5 Oct 2013 07:50:55 +0200
Subject: [docs] Python2orPython3 link to gevent needstobe updated
In-Reply-To: <CDA704DA-7866-41B0-848F-25018C75F99C@bluewin.ch>
References: <DFFCA4CA-3B16-41AF-8D92-9B5C6A5B9ABF@bluewin.ch>
 <CDA704DA-7866-41B0-848F-25018C75F99C@bluewin.ch>
Message-ID: <9715F43D-700E-4D74-8129-452AC049D8C1@bluewin.ch>

On https://wiki.python.org/moin/Python2orPython3 the gevent link should be updated to point to http://gevent.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131005/3ab8990e/attachment.html>

From cclauss at bluewin.ch  Sat Oct  5 08:01:56 2013
From: cclauss at bluewin.ch (Christian Clauss)
Date: Sat, 5 Oct 2013 08:01:56 +0200
Subject: [docs] Python2orPython3 link to PyQT needs to be updated
References: <CDA704DA-7866-41B0-848F-25018C75F99C@bluewin.ch>
Message-ID: <9E792647-105B-4DD2-83EA-C46CFF8CD119@bluewin.ch>

https://wiki.python.org/moin/Python2orPython3 currently says:

"For creating GUI applications Python 3 [...] has been supported by PyQt4 almost from the day Python 3 was released."

The "4" should be stripped off so it just reads PyQT and the link updated to something like http://www.riverbankcomputing.com/software/pyqt or https://pypi.python.org/pypi/PyQt5

The current text will push potential users to the older PyQT4 instead of the more modern PyQT5.

Thanks for listening!  CCC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131005/cfc7a6c5/attachment.html>

From georg at python.org  Sun Oct  6 09:08:07 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:08:07 +0200
Subject: [docs] Python2orPython3 sites dormant modules as a reason not
 to move to Python3
In-Reply-To: <CDA704DA-7866-41B0-848F-25018C75F99C@bluewin.ch>
References: <DFFCA4CA-3B16-41AF-8D92-9B5C6A5B9ABF@bluewin.ch>
 <CDA704DA-7866-41B0-848F-25018C75F99C@bluewin.ch>
Message-ID: <52510C57.3010604@python.org>

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


Am 29.09.2013 16:38, schrieb Christian Clauss:
> Also the gevent link should be updated to point to http://gevent.org
> 
> Sent from my iPad
> 
> On Sep 29, 2013, at 16:30, Christian Clauss <cclauss at bluewin.ch 
> <mailto:cclauss at bluewin.ch>> wrote:
> 
>> https://wiki.python.org/moin/Python2orPython3 currently says:
>> 
>> "Popular modules that don't yet support Python 3 include Twisted 
>> <http://twistedmatrix.com/trac/wiki> (for networking and other 
>> applications), gevent <http://code.google.com/p/gevent/> (like Twisted,
>> but different), and PIL <http://www.pythonware.com/products/pil/> (for
>> processing images)."
>> 
>> But this obscures the reality that gevent and PIL are *both dormant*.
>> There have been no gevent updates posted to pypi for more than a year.
>> There have been no PIL updates in *4 years* and the "friendly" fork named
>> "Pillow" does support both Python 2 and 3 with similar or improved
>> functionality.  The Twisted community has work to do to but is already on
>> a path to Python 3 compatibility.    Pillow:
>> https://pypi.python.org/pypi/Pillow/2.1.0
>> 
>> Python2or3 also says: "For creating GUI applications Python 3 [...] has
>> been supported by PyQt4 <https://wiki.python.org/moin/PyQt4> almost from
>> the day Python 3 was released."
>> 
>> This will push potential users to the older PyQT4 instead of the more
>> modern *PyQT5*. https://pypi.python.org/pypi/PyQt5/5.0.1
>> 
>> Thanks for listening!  CCC
> 
> 
> _______________________________________________ docs mailing list 
> docs at python.org https://mail.python.org/mailman/listinfo/docs
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)

iEYEARECAAYFAlJRDFcACgkQN9GcIYhpnLAQtQCgpeRXBDR7rn0v9y8R57Fg7ViY
wYYAn1uy7dKkprg5+AmH+LBios0Ebxai
=w77C
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:08:16 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:08:16 +0200
Subject: [docs] Python2orPython3 sites dormant modules as a reason not
 to move to Python3
In-Reply-To: <CDA704DA-7866-41B0-848F-25018C75F99C@bluewin.ch>
References: <DFFCA4CA-3B16-41AF-8D92-9B5C6A5B9ABF@bluewin.ch>
 <CDA704DA-7866-41B0-848F-25018C75F99C@bluewin.ch>
Message-ID: <52510C60.5050806@python.org>

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

Hi Christian,

these pages are on the Python Wiki, which means that anybody can change
them for the better.  Please consider creating an account and helping us
improve the Wiki.

thanks,
Georg

Am 29.09.2013 16:38, schrieb Christian Clauss:
> Also the gevent link should be updated to point to http://gevent.org
> 
> Sent from my iPad
> 
> On Sep 29, 2013, at 16:30, Christian Clauss <cclauss at bluewin.ch 
> <mailto:cclauss at bluewin.ch>> wrote:
> 
>> https://wiki.python.org/moin/Python2orPython3 currently says:
>> 
>> "Popular modules that don't yet support Python 3 include Twisted 
>> <http://twistedmatrix.com/trac/wiki> (for networking and other 
>> applications), gevent <http://code.google.com/p/gevent/> (like Twisted,
>> but different), and PIL <http://www.pythonware.com/products/pil/> (for
>> processing images)."
>> 
>> But this obscures the reality that gevent and PIL are *both dormant*.
>> There have been no gevent updates posted to pypi for more than a year.
>> There have been no PIL updates in *4 years* and the "friendly" fork named
>> "Pillow" does support both Python 2 and 3 with similar or improved
>> functionality.  The Twisted community has work to do to but is already on
>> a path to Python 3 compatibility.    Pillow:
>> https://pypi.python.org/pypi/Pillow/2.1.0
>> 
>> Python2or3 also says: "For creating GUI applications Python 3 [...] has
>> been supported by PyQt4 <https://wiki.python.org/moin/PyQt4> almost from
>> the day Python 3 was released."
>> 
>> This will push potential users to the older PyQT4 instead of the more
>> modern *PyQT5*. https://pypi.python.org/pypi/PyQt5/5.0.1
>> 
>> Thanks for listening!  CCC
> 
> 
> _______________________________________________ docs mailing list 
> docs at python.org https://mail.python.org/mailman/listinfo/docs
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)

iEYEARECAAYFAlJRDGAACgkQN9GcIYhpnLAV1wCglTOaCRm2H5sW0uyetoGt6Vky
Nh4AmwY+vVSIMoninGaYG6JEbXzx6jUu
=58k9
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:14:21 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:14:21 +0200
Subject: [docs] [bug] Another error message (documentation)
In-Reply-To: <CAF8hVHsAJqSwEoOdfUtkpct2rdygZbUeYwUJC2La9Mg4yA_P=w@mail.gmail.com>
References: <CAF8hVHsAJqSwEoOdfUtkpct2rdygZbUeYwUJC2La9Mg4yA_P=w@mail.gmail.com>
Message-ID: <52510DCD.1010402@python.org>

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

Am 28.09.2013 15:31, schrieb Pavel Fedotov:
> Python 3.3, documentation: 
> http://docs.python.org/3.3/tutorial/errors.html#exceptions
> 
> First expression output another error message:
> 
>>>> 10 * (1/0)
> Traceback (most recent call last): File "<stdin>", line 1, in <module> 
> ZeroDivisionError: division by zero
> 
> (instead of ... File "<stdin>", line 1, in ? ZeroDivisionError: int
> division or modulo by zero that documentation reports)

Hi Pavel,

thanks for the report, this is now fixed in the repository (and will
be live soon).

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

iEYEARECAAYFAlJRDc0ACgkQN9GcIYhpnLBBYgCdHK/MOt2uhTJ/FoJoRNMd6YEw
KuUAnizMmnNH8ZZzjvp6ukE3ligueiLl
=RJRq
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:15:49 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:15:49 +0200
Subject: [docs] Else ,elif
In-Reply-To: <6BAB10A8-0A9B-49A3-A2E0-B8A0A77E9051@aol.com>
References: <6BAB10A8-0A9B-49A3-A2E0-B8A0A77E9051@aol.com>
Message-ID: <52510E25.4020700@python.org>

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

Am 25.09.2013 20:45, schrieb abjimnen at aol.com:
> I am new to programming but have been seriously been bitten by the buy and
> I am working with the book Python for Dummies by Stef Maruch and Aahz
> Maruch. I am working on a coin toss program which is suppose to  be
> something like   MY issue is that when I try to use the else or elif
> function  it comes back as SyntaxError: invalid syntax  and search as I
> might I can' t seem to find help to address this one issue.  And I was
> hoping you guys can lead me someplace to solve this.   I am using Python
> 3.3.2 on a Mac. Yours Truly Roman
> 
> import random userinput = ' ' print"Now tossing a coin    " while
> userinput.lower() != "q": flip = random.choice(['heads', 'tails']) if flip
> == 'heads': headcount+= 1 print"heads! the number of heads is now %d"%
> tailcount else: tailcount += 1 print"tails! the number of tails is now %d"%
> tailcount print"press 'Q' to quit", userinput = raw_input("or another key
> to toss again:") print" the total number of heads:", headcount print"the
> total number off tails:", tailcount

Hi,

you will have to remove indentation of the "else" clause, so that the
"else" line is indented the same as the "if" line.

Please write to the tutor at python.org list if you have further questions; this
list is for the discussion and improvement of the Python docs.

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

iEYEARECAAYFAlJRDiUACgkQN9GcIYhpnLBlHgCffjTZPw0ikR137SOapjm+a9ip
YjsAnA6BBKyBj7FwbWitwM6zdHsPihyw
=d9rO
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:18:17 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:18:17 +0200
Subject: [docs] Typo in Python docs
In-Reply-To: <etPan.52447dba.6b8b4567.ad@Kirks-MacBook-Air.local>
References: <etPan.52447dba.6b8b4567.ad@Kirks-MacBook-Air.local>
Message-ID: <52510EB9.70105@python.org>

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

Am 26.09.2013 20:32, schrieb Kirk Strauser:
> On http://docs.python.org/2/library/profile.html , the title of section
> 26.4.8. should be "Using a /custom/ timer", not "Using a /customer/ timer".
> 
> 
> - Kirk

Hi Kirk,

thanks for the report, this is now fixed in the repository and will be live soon.

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

iEYEARECAAYFAlJRDrkACgkQN9GcIYhpnLCMCwCeJJ5HqiTOe0CdFUcgV49CJZ39
rtwAoK+b0wgUMHsGT6yxCP1AL5ZTT+PS
=/JLv
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:19:45 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:19:45 +0200
Subject: [docs] little bug with python.
In-Reply-To: <SNT146-W3CF9F04FE6015A719FDC5C9280@phx.gbl>
References: <SNT146-W3CF9F04FE6015A719FDC5C9280@phx.gbl>
Message-ID: <52510F11.3080502@python.org>

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

Am 27.09.2013 01:45, schrieb THE KING HARKINIAN:
> hello, this is my first time writing for python, i wanted to report a
> little bug that it makes the sound of a critical error instead the beep
> when i write this :
> 
> print "\a"
> 
> i'm using windows 8, and i don't know how to fix that, if you can thank you
> very much.

Hi,

this is nothing that Python can do anything about, it just writes the character
to the console. Windows apparently chooses to interpret the "bell" character
with a critical error sound.

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

iEYEARECAAYFAlJRDxEACgkQN9GcIYhpnLAQSACfcWG7jyKS9at5MVo3tedR95BD
jAQAnR84FR1zJLq2oy73LZH+2+ewW/hn
=N5o4
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:21:20 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:21:20 +0200
Subject: [docs] Python Docs Mobile
In-Reply-To: <qkbmdng0ha5ns2w2hrimrdty.1380620298806@email.android.com>
References: <qkbmdng0ha5ns2w2hrimrdty.1380620298806@email.android.com>
Message-ID: <52510F70.7080300@python.org>

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

Am 01.10.2013 12:35, schrieb Artur Fornal:
> Hello ;)
> 
> I want to prepare my own few mobile apps for Android OS and firstly I
> think about mobile app with Python documentation for versions 2.6, 2.7,
> 3.2, 3.3, 3.4. Here I have question to You, can I use Yours python icon and
> docs inside this app, is it possible without any license problems? I want
> to make it completely free, no ads, no statistic. Should be very fast and
> easy to use.
> 
> If You have any questions about details please ask;)

Hi Artur,

as long as the terms of the Python license are followed (in particular,
clause 2 and clause 3), there is no problem from our side.

The license can be read here: http://docs.python.org/2/license.html

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

iEYEARECAAYFAlJRD3AACgkQN9GcIYhpnLDxZACdFotWQJOPFJY+Vy6R5MnSsJ3B
+KwAni4XtrvW5RuioxfN1hpxY1vOgFsa
=UthE
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:21:58 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:21:58 +0200
Subject: [docs] Documentation error
In-Reply-To: <31A5A925033707429B15A6DAC8BF48BA03943B90@AZ25EXM06.gddsi.com>
References: <31A5A925033707429B15A6DAC8BF48BA03943B90@AZ25EXM06.gddsi.com>
Message-ID: <52510F96.1000500@python.org>

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

Am 25.09.2013 14:35, schrieb Marc.Perlmutter at gdc4s.com:
> Found on:
> 
> http://docs.python.org/2.7/tutorial/datastructures.html
> 
> 
> 
> in Section 5.6. ?Looping Techniques?
> 
> 
> 
> Correct the text from:
> 
> *for*i *in*reversed(xrange(1,10,2)):
> 
> 
> 
> to:
> 
> *for* i *in* reversed(range(1,10,2)):
> 
> 
> 
> Reason:
> 
> Python 2.7 does not have xrange function

Hi Marc,

I think you're confusing Python 2 and 3; xrange is present in all 2.x
versions but not in 3.x.

cheers,
Georg

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)

iEYEARECAAYFAlJRD5YACgkQN9GcIYhpnLBGpACgrDsZIRqexaFI/v5uSNoF/gbG
//EAn2Q8chrL7oR2sshafXzPbrT0Afeq
=idSZ
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:23:43 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:23:43 +0200
Subject: [docs] Minor documentation error
In-Reply-To: <20130923193402.GA3764@lairds.us>
References: <20130923193402.GA3764@lairds.us>
Message-ID: <52510FFF.6080605@python.org>

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

Am 23.09.2013 21:34, schrieb Cameron Laird:
> <URL: http://docs.python.org/2/library/xml.etree.elementtree.html > advises
> that
> 
> ... Element.text() accesses the element's text ...
> 
> That should be
> 
> ... Element.text accesses the element's text ...
> 
> The code sample which follows immediately after correctly illustrates use
> of text as attribute, rather than method.

Hi Cameron,

thanks for the report, this is now fixed in the repository and will be
live soon.

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

iEYEARECAAYFAlJRD/8ACgkQN9GcIYhpnLA/PgCfd31fiHgAErR8joxpsvt7ir5x
KF8AnA5Caygbx4MflRRULwjqgigq2m2E
=SR6E
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:26:03 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:26:03 +0200
Subject: [docs] Pithon Bug Report
In-Reply-To: <CAB7xb6Lq0q2=Xq0O7pjA1WuyUnb1T5pnLO7Nc9-KZafmuAd+3A@mail.gmail.com>
References: <CAB7xb6Lq0q2=Xq0O7pjA1WuyUnb1T5pnLO7Nc9-KZafmuAd+3A@mail.gmail.com>
Message-ID: <5251108B.6020303@python.org>

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

Am 03.10.2013 06:29, schrieb Sofware Libre:
> Hello! My name is Martin, a member of Free Software in Comahue National 
> University of Neuqu?n, Argentina. We have detected an error in the compiler
> for Python 2.7 using Ubuntu 12.04: I write the code, without realizing I
> leave a comment with syntax error in that line (do not put the # of
> comments), compile and get error of sistaxis in that line. Fix the error
> adding # to comment, I do compile again and it shows me various errors that
> take over the Python compiler and I am forced to close it. Hope your
> response with a possible solution to this problem, my idea is to continue
> using this version of Python. Thank you!

Hi Martin,

I'm afraid I can't see from your description what the exact error is that you
wish to report.

In any case, this list is about improving and discussing the documentation of
Python; I recommend writing to the tutor at python.org or python-list at python.org
lists for help with the interpreter.

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

iEYEARECAAYFAlJREIsACgkQN9GcIYhpnLCcRgCeIzyqBnLgMJvUlUow2NPJ8oVg
xJIAn05SXaexacrZvWH862WORdtl7Qwv
=Jn01
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:30:49 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:30:49 +0200
Subject: [docs] SSL Module Documentation Broken Link
In-Reply-To: <524BA097.7030503@felixhandte.com>
References: <524BA097.7030503@felixhandte.com>
Message-ID: <525111A9.8050807@python.org>

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

Am 02.10.2013 06:27, schrieb W. Felix Handte:
> Howdy,
> 
> The page for the ssl module in the documentation for most Python versions,
> ("http://docs.python.org/" + s + "/library/ssl.html" for s in ("2.7",
> "3.2", "3.3", "3.4")), links to 
> http://www3.rad.com/networks/applications/secure/tls.htm in the See Also
> section, under the title "TLS (Transport Layer Security) and SSL (Secure
> Socket Layer)". That URL doesn't resolve, and replacing the "www3." with
> "www." doesn't fix it either. It should be removed, I guess.

Hi Felix,

I've created a tracker issue here: http://bugs.python.org/issue19177  so
that we can decide if we want to include an alternate see-also document.

Thanks for your report!
Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)

iEYEARECAAYFAlJREakACgkQN9GcIYhpnLDkWQCeKw81+jGYcvFc2ColCiKXWLcY
2f4An0sF9Q/yALceiynx1zlQg10xfVVk
=7R9f
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:32:41 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:32:41 +0200
Subject: [docs] Dead link "404"
In-Reply-To: <CAAr3Zubyi8SkK-37EP5_coT4d3UbJ1xJAeJEq1EfzQdGxiwZ_g@mail.gmail.com>
References: <CAAr3Zubyi8SkK-37EP5_coT4d3UbJ1xJAeJEq1EfzQdGxiwZ_g@mail.gmail.com>
Message-ID: <52511219.3020501@python.org>

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

Am 18.09.2013 13:29, schrieb Ralf Ganswindt:
> On Python manual for 2.7.5, section 24.1, "Tkinter...", the following link
> is 404:
> 
> An Introduction to Tkinter 
> <http://www.pythonware.com/library/an-introduction-to-tkinter.htm> Fredrik
> Lundh?s on-line reference material.
> 
> The link appears to have been moved... without forwarding.
> 

Hi Ralf,

thanks for the report, I've removed the link now in the repository, it should
be live soon.

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

iEYEARECAAYFAlJREhkACgkQN9GcIYhpnLDEYACgmw4dPT1cqVBN4AbYU0J+IAAp
M1sAn3Gu7T8L3G8O0A1A2qdVUiDm2mDT
=0dRa
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:36:38 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:36:38 +0200
Subject: [docs] subprocess module constant documentation
In-Reply-To: <CANc-5UyoYFcYr_wNXNnaY3bGJeJn9MyB=iY_D-_txoWG6yt1pg@mail.gmail.com>
References: <CANc-5UyoYFcYr_wNXNnaY3bGJeJn9MyB=iY_D-_txoWG6yt1pg@mail.gmail.com>
Message-ID: <52511306.1060406@python.org>

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

Am 20.09.2013 17:40, schrieb Skip Montanaro:
> The subprocess module documentation mentions a lot of constants in section
> 17.5.3.1. That is the only section labeled "Constants", though it seems
> likely from the section hierarchy and the obscure names in that section,
> that these are all Windows-specific constants. On my Mac, I see DEVNULL,
> PIPE and STDOUT. While these are mentioned in section 17.5.1, they aren't
> documented specifically as constants, rather as "special value"s. I think
> the docs should have a single "Constants" section one level up in the
> hierarchy from where it currently live. It should describe all constants
> the user might encounter, marking those which are platform-specific.

Hi Skip,

please create a tracker issue for this.

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

iEYEARECAAYFAlJREwYACgkQN9GcIYhpnLDNNACcCey7VruvvwrthA3C5QztWQ11
MUEAn0tXpwbBMcIgOeL78FBrY1jdAOts
=WMUg
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:38:09 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:38:09 +0200
Subject: [docs] itertools documentation does not link to source
In-Reply-To: <CAEcE8Rid2i_+Y=+5DWiq9QPwrbdMY8MAZPZYo4CNzuBztkwaxw@mail.gmail.com>
References: <CAEcE8Rid2i_+Y=+5DWiq9QPwrbdMY8MAZPZYo4CNzuBztkwaxw@mail.gmail.com>
Message-ID: <52511361.8000308@python.org>

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

Am 19.09.2013 20:13, schrieb Thomas Winwood:
> Raymond Hettinger has spoken on how important it is to let people find the 
> source from the documentation, but there's no link from the itertools 
> documentation to the source.

Hi Thomas,

this is because the itertools module is written in C, and there's not much
that can be learned from that source (if you're not an expert, and know how
to find the source anyway).

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

iEYEARECAAYFAlJRE2EACgkQN9GcIYhpnLBGuACdH8gjAyu100QlY79CFXNf9O13
1TAAn2mrowhuegfRAaW+1bhOf+npy/sE
=xZsq
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:40:33 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:40:33 +0200
Subject: [docs] Intersphinx Linking to Anchors in Python Docs
In-Reply-To: <6A5F6FCB-5436-4A67-92DE-A1A67812D152@gmail.com>
References: <6A5F6FCB-5436-4A67-92DE-A1A67812D152@gmail.com>
Message-ID: <525113F1.3070805@python.org>

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

Am 28.09.2013 22:12, schrieb Alexander Rudy:
> Hi,
> 
> I'm working on some documentation for the `astropy <http://astropy.org>`` 
> project where I'd like to use inter sphinx to link to python
> documentation. Intersphinx creates the links without a problem, and
> includes anchors (I'm trying to link to the following: 
> http://docs.python.org/library/string.html#formatstrings which I am
> linking with the following reST: :ref:`python:formatstrings`). However, in
> the redirection from this link to the final destination 
> (http://docs.python.org/2/library/string.html) the anchor (part after the
> #) is lost. This feels broken. Is there something I can do, or something
> the python docs generation can do to fix this problem? It is annoying to
> send users looking for "format string syntax" to the top of the string
> module page. I can hardlink, but that seems silly, when I have intesrphinx.
> I could also always send them to the python 2 or python 3 version, but that
> too seems unfortunate.

Hi Alexander,

which version of Sphinx are you using?

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

iEYEARECAAYFAlJRE/EACgkQN9GcIYhpnLBZTwCdHtjAJT5aUV6/bXzYLI2PEWY9
prkAnjTNnl2Ca9sCOXmntSfY/5ANJJiV
=IOgJ
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:46:00 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:46:00 +0200
Subject: [docs] Bug / Room for Improvement
In-Reply-To: <000501ceae28$99b7d690$cd2783b0$@com>
References: <000501ceae28$99b7d690$cd2783b0$@com>
Message-ID: <52511538.8050503@python.org>

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

Am 10.09.2013 15:21, schrieb Sterling Robertson:
> In section 9.2.1 of the tutorial, at 
> http://docs.python.org/3/tutorial/classes.html, the sample program does
> not work.  The following is what happens when someone tries to type it in
> (I?m using IDLE for Python 3.3.2):
> 
> 
> 
>>>> def scope_test():
> 
> def do_local():
> 
> spam = "local spam"
> 
> def do_nonlocal():
> 
> nonlocal spam
> 
> 
> 
> SyntaxError: no binding for nonlocal 'spam' found
> 
> 
> 
> This needs to be corrected, especially when you consider the poor
> explanations and lack of clarity throughout these tutorials and especially
> this chapter.  I?m a professional programmer, and I?m still having a hard
> time following your tutorials.
> 
> 
> 
> One of the biggest issues is that you?re trying to put too much detail into
> too few words.  *Many* different facts are being thrown at absolute
> beginners all at once, with very little elaboration.  Many of the details
> you?re trying to describe are not fully explained, causing critical gaps of
> information.  You should do one of two things:
> 
> 
> 
> 1)      Expand your tutorials and elaborate more fully on what it is
> you?re trying to communicate, making sure that every detail is *completely*
> explained and well-defined.
> 
> 2)      Remove many of the details that you?re getting sidetracked on, and 
> re-invest that amount of space in the tutorials to more clearly explaining
> the parts of the language that are more central and important for a
> beginner who is studying the language for the first time.
> 
> 
> 
> Furthermore section 9.2 is using unorthodox terminology with little or no 
> explanation, and it?s not very well-written in general.  This section
> appears to be trying to explain a concept in overly complicated,
> ?beat-around-the-bush? wording, and it?s not even doing that very well.  It
> should be re-written from the ground up, and it should either use more
> standard terminology, or if unorthodox terminology is a necessity, provide
> a more thorough explanation of what that terminology means.  Even for
> professional programmers, it is very hard to read and follow.
> 
> 
> 
> Please understand that I am not trying to be overly negative or critical,
> but I do believe someone needs to go through the tutorial and look it over
> for things like this.  Remember that some of the people reading this have
> no previous programming experience, and when it?s already difficult for
> professionals to follow, it would be almost impossible for them.  Thank
> you.

Hi Sterling,

I understand your concerns completely; the whole "Classes" tutorial has grown to
be an unwieldy mixture of tutorial and reference (myself I think that "nonlocal"
has no place in a tutorial for beginners anyway), and should be rewritten from
start; unfortunately that is quite a big (and ungrateful) job for volunteer
work.

I've at least fixed your first issue, the problem was that the newline in the
method definition as shown tells the interactive interpreter that the method
definition is finished; this would not happen in source files.  I've removed
the newline from the example now so that it can be pasted more easily in
interactive mode.

cheers,
Georg



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)

iEYEARECAAYFAlJRFTgACgkQN9GcIYhpnLCChQCfe89hah5n4YaPqkYpgf0hKGqR
9x8AmwbikisU1NiL9UVcTrTA2RTwG8jA
=mNzz
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:49:41 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:49:41 +0200
Subject: [docs] Omit parens from hashlib.md5() in hmac
In-Reply-To: <1379131609-sup-3749@javelin>
References: <1379131609-sup-3749@javelin>
Message-ID: <52511615.8060503@python.org>

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

Am 14.09.2013 06:07, schrieb Edward Z. Yang:
> Presently we have this text at http://docs.python.org/2/library/hmac.html:
> 
> Return a new hmac object. If msg is present, the method call update(msg) is
> made. digestmod is the digest constructor or module for the HMAC object to
> use. It defaults to the hashlib.md5() constructor.
> 
> This text is misleading, as it suggests that the usage of the digestmod
> param is:
> 
> hmac.new(secret, msg, hashlib.sha256())
> 
> which is not right.

Hi Edward,

thanks for the report, this is now fixed and should be going live soon.

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

iEYEARECAAYFAlJRFhUACgkQN9GcIYhpnLBThgCgmSX9X6BBSuYu/AzEMYmp/UP+
IX0AoIHZZBvBC/rnq8MyDAz5LqU8k2uk
=vd4s
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:51:10 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:51:10 +0200
Subject: [docs] Small error in argparse documentation
In-Reply-To: <CAN6rOxgbREa7e85Bs2DtPQ2EjkzLL_vkX46s5x8LJUjXin4x=Q@mail.gmail.com>
References: <CAN6rOxgbREa7e85Bs2DtPQ2EjkzLL_vkX46s5x8LJUjXin4x=Q@mail.gmail.com>
Message-ID: <5251166E.4080800@python.org>

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

Am 13.09.2013 18:58, schrieb John Kooker:
> Hey Python docs team,
> 
> I think I may have found a small error in the docs. The last example in
> the argparse add_help section doesn't look correct. The dashes should be
> plus signs.
> 
> http://docs.python.org/dev/library/argparse.html#add-help
> 
> Thanks for all your hard work! These docs are fantastic.

Hi John,

thanks for your report; this is now fixed and should be going live
soon.

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

iEYEARECAAYFAlJRFm4ACgkQN9GcIYhpnLChMwCeJI19QQ/ZCH+uQFwwlwdFk5bp
k3kAn3x303Eq3VK0I7SENtoPMqfAblA7
=tUiJ
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 09:53:47 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:53:47 +0200
Subject: [docs] os.path.getctime
In-Reply-To: <CE4E3CAF.35191%mayerbw@ornl.gov>
References: <CE4E3CAF.35191%mayerbw@ornl.gov>
Message-ID: <5251170B.9080704@python.org>

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

Am 05.09.2013 19:50, schrieb Mayer, Benjamin W.:
> The os.path.getctime documention is misleading for Unix. Inserting the
> word "inode" into the follow is more accurate description of what is
> happening:
> 
> Return the system's ctime which on some systems (like Unix) is the time of 
> the last in ode change,?

Hi Ben,

thanks for the report, I fixed this (using "metadata change" like in the
description of the os.stat() function) and it should be going live soon.

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

iEYEARECAAYFAlJRFwsACgkQN9GcIYhpnLBCDwCfauUQNJqdnh6/XqCW9OTR0EyH
YFEAn1F4ysHkqqTAF1WTu2rZpaeejG+f
=c8K/
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 10:05:44 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 10:05:44 +0200
Subject: [docs] Demo code error in "Curses Programming with Python"
In-Reply-To: <CAFE=xWsik9qHE2aHUdqrXc+1ikatQTjii8v73gjxXz0pn+q==w@mail.gmail.com>
References: <CAFE=xWsik9qHE2aHUdqrXc+1ikatQTjii8v73gjxXz0pn+q==w@mail.gmail.com>
Message-ID: <525119D8.1080202@python.org>

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

Am 02.09.2013 13:52, schrieb ???:
> Dears: I found demo code of cruses wrapper() ( the code just before
> "Windows and Pads") in docs  "Curses Programming with Python" have some
> code error.
> 
> "    for i in range(0, 10):" should be "    for i in range(11):", or that
> would not raises ZeroDivisionError.
> 
> Bo-Sian Li

Hi,

thanks for the report; this is now fixed and should be live soon.

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

iEYEARECAAYFAlJRGdgACgkQN9GcIYhpnLB+jgCgr+SjcetLksxn15swGjUU2CyJ
17kAn3/B5wAQyB/5TZF1LDMM6e8jOMwe
=pTFY
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 10:08:47 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 10:08:47 +0200
Subject: [docs] backslash ending raw string literals.
In-Reply-To: <C450F7046A908F498A5A88FE4A3612E00B80A428@VNMSGPPCSFO24.passportcapital.com>
References: <C450F7046A908F498A5A88FE4A3612E00B80A428@VNMSGPPCSFO24.passportcapital.com>
Message-ID: <52511A8F.9090001@python.org>

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

Am 26.08.2013 23:59, schrieb Scot Kelly:
> From the doc: http://docs.python.org/2/reference/lexical_analysis.html
> 
> r"\"is not a valid string literal (even a raw string cannot end in an odd 
> number of backslashes). Specifically, //a raw string cannot end in a
> single backslash// (since the backslash would escape the following quote
> character).
> 
> 
> 
> If it?s a raw string, then the backslash will _not_escape the following
> quote character.  Ergo r?\? should be allowed.

Hi Scot,

this is due to a limitation of the Python lexer; the inconsistency is minor
and is accepted as the lesser evil and documented.

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

iEYEARECAAYFAlJRGo8ACgkQN9GcIYhpnLC6FwCggteSdBwGeqplhx7hwDDOgc5Y
hYAAoJ+BXB9WHg5SQy4joFyWQ0nl06vN
=XSi6
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 10:12:05 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 10:12:05 +0200
Subject: [docs] Typo error 21.10.ossaudiodev Python 2.7 documentation
In-Reply-To: <CAPYtohK9zK0o63VxnVqJQ=5nmX7VUTx2Zi7FTQYVyHBZCeHu=w@mail.gmail.com>
References: <CAPYtohK9zK0o63VxnVqJQ=5nmX7VUTx2Zi7FTQYVyHBZCeHu=w@mail.gmail.com>
Message-ID: <52511B55.4080203@python.org>

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

Am 24.08.2013 06:58, schrieb Ken Housley:
> In 21.10.1 Audio Device Objects near the end of the section there is an
> example of how to use the setparameters() method. The example is said to be
> equivalent to three separate statements. The last of the three statements
> is:
> 
> rate = dsp.rate(channels)
> 
> I think the statement should be
> 
> rate = dsp.rate(rate)
> 
> It is a minor correction, but we would want to fix the small errors as well
> as the big ones, right?  The error appears on the web at
> 
> http://docs.python.org/2/library/ossaudiodev.html
> 
> and in the pdf file library.pdf in the python 2.7 documentation.

Hi Ken,

thanks for the report; this is now fixed and should appear online soon.

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

iEUEARECAAYFAlJRG1UACgkQN9GcIYhpnLBP7wCfZwPlJ47+9tiz8Z2SqaRu3aBV
eR0AkwR999ckHEHCNHx55T/jxbjsK9M=
=ajlA
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct  6 10:22:11 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 08:22:11 +0000
Subject: [docs] [issue18646] Improve tutorial entry on 'Lambda Forms'.
In-Reply-To: <1375562526.59.0.207872880438.issue18646@psf.upfronthosting.co.za>
Message-ID: <3csyVB2ZrszSwZ@mail.python.org>


Roundup Robot added the comment:

New changeset d4eb47c3d681 by Georg Brandl in branch '2.7':
Closes #18646: improve lambda docs in tutorial.  Original patch by Terry Reedy.
http://hg.python.org/cpython/rev/d4eb47c3d681

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

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

From report at bugs.python.org  Sun Oct  6 10:22:25 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 08:22:25 +0000
Subject: [docs] [issue18646] Improve tutorial entry on 'Lambda Forms'.
In-Reply-To: <1375562526.59.0.207872880438.issue18646@psf.upfronthosting.co.za>
Message-ID: <3csyVS59Dcz7Ljd@mail.python.org>


Roundup Robot added the comment:

New changeset ef1a17d5e263 by Georg Brandl in branch '3.3':
Closes #18646: improve lambda docs in tutorial.  Original patch by Terry Reedy.
http://hg.python.org/cpython/rev/ef1a17d5e263

----------

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

From report at bugs.python.org  Sun Oct  6 10:24:37 2013
From: report at bugs.python.org (Berker Peksag)
Date: Sun, 06 Oct 2013 08:24:37 +0000
Subject: [docs] [issue18790] incorrect text in argparse add_help example
In-Reply-To: <1377025104.92.0.641943823333.issue18790@psf.upfronthosting.co.za>
Message-ID: <1381047877.56.0.595452750956.issue18790@psf.upfronthosting.co.za>


Berker Peksag added the comment:

This is fixed by changesets:

- http://hg.python.org/cpython/rev/e2456381fa14 (3.4)
- http://hg.python.org/cpython/rev/ee394a61dade (3.3)
- http://hg.python.org/cpython/rev/c5f57a7fd4d8 (2.7)

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

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

From report at bugs.python.org  Sun Oct  6 10:25:57 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 08:25:57 +0000
Subject: [docs] [issue18646] Improve tutorial entry on 'Lambda Forms'.
In-Reply-To: <1375562526.59.0.207872880438.issue18646@psf.upfronthosting.co.za>
Message-ID: <1381047957.32.0.735673351406.issue18646@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thanks for the patch; I modified it a little (removed the sentence about the name attribute; this is too involved for the tutorial, and used "lambda expression").  Will fix more "lambda form" in the docs in another changeset.

----------
nosy: +georg.brandl
resolution: fixed -> 
stage: committed/rejected -> patch review
status: closed -> open

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

From report at bugs.python.org  Sun Oct  6 10:31:12 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 08:31:12 +0000
Subject: [docs] [issue18972] Use argparse in email example scripts
In-Reply-To: <1378652028.96.0.621116344908.issue18972@psf.upfronthosting.co.za>
Message-ID: <1381048272.07.0.220486261595.issue18972@psf.upfronthosting.co.za>


Georg Brandl added the comment:

LGTM, please apply. (FileType is imported but not used in the second example?)

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

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

From report at bugs.python.org  Sun Oct  6 10:33:05 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 08:33:05 +0000
Subject: [docs] [issue18790] incorrect text in argparse add_help example
In-Reply-To: <1377025104.92.0.641943823333.issue18790@psf.upfronthosting.co.za>
Message-ID: <1381048385.31.0.725901113526.issue18790@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thanks for closing this!

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

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

From report at bugs.python.org  Sun Oct  6 10:34:25 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 06 Oct 2013 08:34:25 +0000
Subject: [docs] [issue18972] Use argparse in email example scripts
In-Reply-To: <1378652028.96.0.621116344908.issue18972@psf.upfronthosting.co.za>
Message-ID: <1381048465.57.0.00302040139946.issue18972@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

FileType have some problems (see issue13824).

----------

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

From report at bugs.python.org  Sun Oct  6 10:35:48 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 08:35:48 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381048548.39.0.502593987876.issue18758@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Definitely not.

----------

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

From report at bugs.python.org  Sun Oct  6 10:35:56 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 06 Oct 2013 08:35:56 +0000
Subject: [docs] [issue18646] Improve tutorial entry on 'Lambda Forms'.
In-Reply-To: <1375562526.59.0.207872880438.issue18646@psf.upfronthosting.co.za>
Message-ID: <1381048556.19.0.870848297984.issue18646@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

I think this was a nice improvement.

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

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

From report at bugs.python.org  Sun Oct  6 10:39:24 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 08:39:24 +0000
Subject: [docs] [issue18646] Improve tutorial entry on 'Lambda Forms'.
In-Reply-To: <1375562526.59.0.207872880438.issue18646@psf.upfronthosting.co.za>
Message-ID: <1381048764.84.0.385053738413.issue18646@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


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

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

From report at bugs.python.org  Sun Oct  6 10:42:53 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 08:42:53 +0000
Subject: [docs] [issue19178] Entries for "module" and "package" in glossary
Message-ID: <1381048973.81.0.279739415702.issue19178@psf.upfronthosting.co.za>


New submission from Georg Brandl:

>From Kevin Murphy on docs@:

> I think newbies might like having 'module' and 'package' defined in 
> the glossary, e.g. http://docs.python.org/2/glossary.html

I agree.

----------
assignee: docs at python
components: Documentation
messages: 199052
nosy: docs at python, georg.brandl
priority: normal
severity: normal
stage: needs patch
status: open
title: Entries for "module" and "package" in glossary
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4

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

From georg at python.org  Sun Oct  6 10:44:16 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 10:44:16 +0200
Subject: [docs] Suggestion for Python glossary
In-Reply-To: <96AE3A91-929A-4FFD-A4E2-9B2EB969A85F@gmail.com>
References: <96AE3A91-929A-4FFD-A4E2-9B2EB969A85F@gmail.com>
Message-ID: <525122E0.3050902@python.org>

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

Am 18.09.2013 20:32, schrieb Kevin Murphy:
> I think newbies might like having 'module' and 'package' defined in the 
> glossary, e.g. http://docs.python.org/2/glossary.html

Hi Kevin,

I agree; I have opened http://bugs.python.org/issue19178 to track this
request.

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

iEYEARECAAYFAlJRIuAACgkQN9GcIYhpnLA/OwCeI2pq6EouKUvh/icMZXdI1ODJ
C/QAnjMftQJnrkdmZwPlPuBYwyQQ3yNa
=CYS3
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct  6 10:45:49 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 08:45:49 +0000
Subject: [docs] [issue18972] Use argparse in email example scripts
In-Reply-To: <1378652028.96.0.621116344908.issue18972@psf.upfronthosting.co.za>
Message-ID: <3csz1S6b8HzSb8@mail.python.org>


Roundup Robot added the comment:

New changeset 1b1b1d4b28e8 by Serhiy Storchaka in branch 'default':
Issue #18972: Modernize email examples and use the argparse module in them.
http://hg.python.org/cpython/rev/1b1b1d4b28e8

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

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

From report at bugs.python.org  Sun Oct  6 10:46:53 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 06 Oct 2013 08:46:53 +0000
Subject: [docs] [issue18972] Use argparse in email example scripts
In-Reply-To: <1378652028.96.0.621116344908.issue18972@psf.upfronthosting.co.za>
Message-ID: <1381049213.61.0.533645190497.issue18972@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you Georg for the review

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

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

From report at bugs.python.org  Sun Oct  6 10:48:03 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 08:48:03 +0000
Subject: [docs] [issue18927] Lock.acquire() docs incorrect about negative
	timeout
In-Reply-To: <1378331648.69.0.879815072803.issue18927@psf.upfronthosting.co.za>
Message-ID: <3csz422X5Cz7Ljp@mail.python.org>


Roundup Robot added the comment:

New changeset ff5fb419967f by Georg Brandl in branch '3.3':
Closes #18927: Lock.acquire only accepts -1 or positive values for timeout.
http://hg.python.org/cpython/rev/ff5fb419967f

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

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

From report at bugs.python.org  Sun Oct  6 10:50:22 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 08:50:22 +0000
Subject: [docs] [issue13951] Document that Seg Fault in .so called by ctypes
	causes	the interpreter to Seg Fault
In-Reply-To: <1328535030.63.0.73417525944.issue13951@psf.upfronthosting.co.za>
Message-ID: <3csz6j6Z3lz7Ljn@mail.python.org>


Roundup Robot added the comment:

New changeset 1e163fdf8cf3 by Georg Brandl in branch '3.3':
Closes #13951: Add a "faulthandler" reference in the ctypes docs talking about crashes.
http://hg.python.org/cpython/rev/1e163fdf8cf3

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

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

From georg at python.org  Sun Oct  6 10:57:28 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 10:57:28 +0200
Subject: [docs] Confusing default redirects
In-Reply-To: <CADg_278+dmzttUKo+esTQMh+tCZDr0jG1-9_FXzXw3Ln-dMmaA@mail.gmail.com>
References: <CADg_278+dmzttUKo+esTQMh+tCZDr0jG1-9_FXzXw3Ln-dMmaA@mail.gmail.com>
Message-ID: <525125F8.1010008@python.org>

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

Am 09.08.2013 19:21, schrieb Dra?en Lu?anin:
> Dear Sir/Madam,
> 
> When I open http://docs.python.org/ it redirects me to
> http://docs.python.org/3/
> 
> When I open http://docs.python.org/library/ it redirects me to 
> http://docs.python.org/2/library/
> 
> Expected - all "versionless" URLs should redirect to the same (current 
> stable and recommended) version of Python.

Hi Dra?en,

this is intentional, see http://www.python.org/dev/peps/pep-0430/ for the
details.

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

iEYEARECAAYFAlJRJfgACgkQN9GcIYhpnLAVkACfZlk4W5zuBwOMx8/znTaoY9mn
FCIAoJW8Xu+Vrq673qInPQFa1yRsfeWA
=7nZP
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:00:09 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:00:09 +0200
Subject: [docs] Documention bug
In-Reply-To: <CADcxe66UsUNqtBjQP-f=RsBE_VO9q_W5zKbo_ehb3t6eYR0exQ@mail.gmail.com>
References: <CADcxe66UsUNqtBjQP-f=RsBE_VO9q_W5zKbo_ehb3t6eYR0exQ@mail.gmail.com>
Message-ID: <52512699.9070209@python.org>

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

Am 06.08.2013 08:47, schrieb Owen Johnson:
> On page:
> 
> http://docs.python.org/3.0/library/csv.html
> 
> Under Examples:
> 
> ---- The simplest example of reading a CSV file:
> 
> import csv reader = csv.reader(open("some.csv", "rb")) for row in reader: 
> print(row) ----
> 
> Code works in python 2, but in python 3, it throws error:
> 
> ---- Traceback (most recent call last): File "WeeklyDepletionParser.py",
> line 3, in <module> for row in reader: _csv.Error: iterator should return
> strings, not bytes (did you open the file in text mode?) ----
> 
> Fix was straightforward to change parameter "rb" to "rt".
> 
> I am running:
> 
> Python 3.3.2 (v3.3.2:d047928ae3f6, May 13 2013, 13:52:24) [GCC 4.2.1 (Apple
> Inc. build 5666) (dot 3)] on darwin

Hi Owen,

please update your links to use the most recent version of the
docs; the /3.0/ docs are not updated anymore.  The current Python
3 docs at

http://docs.python.org/3/library/csv.html

are already correct.

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

iEYEARECAAYFAlJRJpkACgkQN9GcIYhpnLA36gCcCXd3O0LQWcJtR6yrMiVgh028
EaMAoKQ744RFrkOpigRYoxHrkueH+DlP
=LJlv
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:03:45 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:03:45 +0200
Subject: [docs] Possible document issue.
In-Reply-To: <CAFxYmVoHjn35=U4RFsq2YW+syFCw3mujxF2YO=2wa-mY-zbrpA@mail.gmail.com>
References: <CAFxYmVoHjn35=U4RFsq2YW+syFCw3mujxF2YO=2wa-mY-zbrpA@mail.gmail.com>
Message-ID: <52512771.4020407@python.org>

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

Am 02.08.2013 16:01, schrieb Issaria Peng:
> Hi,
> 
> http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst
> 
> 509 
> <http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l509>
> /* Time to call the callback */ 510 
> <http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l510>
> arglist = Py_BuildValue("(i)", arg); 511 
> <http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l511>
> result = PyObject_CallObject(my_callback, arglist); 512 
> <http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l512>
> Py_DECREF(arglist); 513 
> <http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l513>
>
> 
514
> <http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l514>
> :c:func:`PyObject_CallObject` returns a Python object pointer: this is the
> return 515 
> <http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l515>
> value of the Python function. :c:func:`PyObject_CallObject` is 516 
> <http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l516>
> "reference-count-neutral" with respect to its arguments. In the example a
> new 517 
> <http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l517>
> tuple was created to serve as the argument list, which is
> :c:func:`Py_DECREF`\ 518 
> <http://hg.python.org/cpython/file/52e166a975f9/Doc/extending/extending.rst#l518>
> -ed immediately after the call.
> 
> According to the explain directly after the code, line 512 should be:
> 
> Py_DECREF(result);


Hi Issaria,

thanks for the report; I've clarified this now and it should appear online soon.

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

iEYEARECAAYFAlJRJ3EACgkQN9GcIYhpnLCTKQCeIk2fjP1o4FPNiMMFDGw5TFsC
UQsAoIw+RKPmk7wTfCsBApNqZv8Vfzcz
=YnxU
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:05:15 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:05:15 +0200
Subject: [docs] possible bug in regular expression documentation
In-Reply-To: <CAP+wG8OTZwahuzz44FA_7jWhH+KL28rseX0t_9fgXgepqC9hBw@mail.gmail.com>
References: <CAP+wG8OTZwahuzz44FA_7jWhH+KL28rseX0t_9fgXgepqC9hBw@mail.gmail.com>
Message-ID: <525127CB.2020207@python.org>

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

Am 02.08.2013 12:06, schrieb Bart Aelterman:
> Dear,
> 
> While reading the python documentation, chapter 7.2 "Regular expression 
> operations", I noticed a sentence that could be experienced as confusing:
> 
> " \d When the UNICODE flag is not specified, matches any decimal digit;
> this is equivalent to the set [0-9]. With UNICODE, it will match whatever
> is classified as a decimal digit in the Unicode character properties
> database. "
> 
> I have a problem with "decimal digit". These patterns match only one
> character. Therefore, one character can never be decimal, as that would
> imply the presence of at least one digit and a decimal character (dot). I
> would propose to delete the word "decimal". \d matches a digit. Unless you
> want to say that \d+ matches a decimal digit, for instance "2.2". But when
> I try that in ipython, \d+ only matches "2".

Hi Bart,

in this case "decimal" means a digit from the base-10 system, to
differentiate from digits from other number systems that may indicate
values of 10, 11 etc.

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

iEYEARECAAYFAlJRJ8sACgkQN9GcIYhpnLDeHQCgrkT2CnWuLOO/7x3jaZBOSf9z
x8oAoJKllr7HMK8oWJwtFPKv9ysLfv3c
=eXu5
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:06:22 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:06:22 +0200
Subject: [docs] Phyton tutorial als 1 file
In-Reply-To: <CAOfyMSR1q-5JF6V9eB7YpQXJv3_dGZH-TxsdoYSYzbjFfbuwKw@mail.gmail.com>
References: <CAOfyMSR1q-5JF6V9eB7YpQXJv3_dGZH-TxsdoYSYzbjFfbuwKw@mail.gmail.com>
Message-ID: <5251280E.8010009@python.org>

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

Am 29.07.2013 21:06, schrieb Joseph Melotte:
> geachte,
> 
> website http://www.coolpython.nl/tutorials/tut/tut.html
> 
> is deze tutorial ook te downloade als 1 file ? indien ja, graag dan de
> website.
> 
> vriendelijke groeten,
> 
> Melotte Joseph in B

Hi Joseph,

this tutorial is not provided by python.org, but appears to be
a translation by volunteers.

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

iEYEARECAAYFAlJRKA4ACgkQN9GcIYhpnLAJIgCfX/Btq32PXFpURc1es4lbPS8A
5jwAn0oF6quOqY6GBBjVSCMJGlD4UXfG
=NK4i
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:07:09 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:07:09 +0200
Subject: [docs] Fwd: Order in Python documentation search results
In-Reply-To: <CACvLUamWcfYR97_ZLqvD4=G9z75XH1jAZ0PQEV4w_vmuhpv1-Q@mail.gmail.com>
References: <CACvLUangzuQfrHZV9r=2eSpPreYWkBJ0H0AttZKfY9_HFV-udQ@mail.gmail.com>
 <CAL6gwWVY0HMXD4ZWJeCUV4f3gh2EabK3jMJnaF04E2MRYq5Cpw@mail.gmail.com>
 <CACvLUamWcfYR97_ZLqvD4=G9z75XH1jAZ0PQEV4w_vmuhpv1-Q@mail.gmail.com>
Message-ID: <5251283D.2020503@python.org>

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

Hi Drekin,

the Sphinx version used on docs.python.org will be updated when Sphinx 1.2
final is released (which will be very soon).

cheers,
Georg

Am 29.07.2013 15:16, schrieb Draic Kin:
> Hello, in January there was an attempt by Hernan Grecco to improve the
> order in documentation search. Even a patch for Sphinx was accepted,
> however the improvement wasn't implemented on docs.python.org
> <http://docs.python.org>. It would be nice to be done. See forwarded
> message for details.
> 
> Thank you for reaction, Drekin
> 
> 
> ---------- Forwarded message ---------- From: *Hernan Grecco*
> <hernan.grecco at gmail.com <mailto:hernan.grecco at gmail.com>> Date: Mon, Jul
> 29, 2013 at 2:26 PM Subject: Re: Order in Python documentation search
> results To: Draic Kin <drekin at gmail.com <mailto:drekin at gmail.com>>
> 
> 
> Hi,
> 
> The patch was accepted into sphinx. What is missing is a new sphinx release
> and that this release is installed in docs.python.org 
> <http://docs.python.org>. It would be really nice if this functionality is
> available in docs.python.org <http://docs.python.org> (that was the
> original aim of the patch) but it is outside my reach. Maybe you can e-mail
> the maintainer of the site.
> 
> cheers,
> 
> Hernan
> 
> 
> 
> On Mon, Jul 29, 2013 at 8:13 AM, Draic Kin <drekin at gmail.com 
> <mailto:drekin at gmail.com>> wrote:
>> Hello, I have found your nice improvement of Python documentation search 
>> (http://mail.python.org/pipermail/python-ideas/2013-January/018500.html).
>> As I understand, you have finished the patch of sphinx 
>> (https://bitbucket.org/birkenfeld/sphinx/issue/1067/better-search-results).
>>
>> 
However your improvement doesn't seem to be actually implemented on
>> docs.python.org <http://docs.python.org>. Is there a chance it will be
>> so? It
> would be very nice if
>> search on docs.python.org <http://docs.python.org> worked like in your
>> improvement (http://hgrecco.github.io/searchpydocs/).
>> 
>> Thank you for information, Drekin
> 
> 
> 
> _______________________________________________ docs mailing list 
> docs at python.org http://mail.python.org/mailman/listinfo/docs
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)

iEYEARECAAYFAlJRKD0ACgkQN9GcIYhpnLC7vgCfWgx7Y2j4UE8dxdoPiZq7rB0D
PB8AoIHz3gRRF8v6Xgyfgl2T9ViIsT8z
=CkoP
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:09:27 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:09:27 +0200
Subject: [docs] Minor bug on
	http://docs.python.org/2/tutorial/interpreter.html
In-Reply-To: <CAOHKUnLoCc57y+BBCiXMA4u735_upA47vadX9EFtSMnEdNkxng@mail.gmail.com>
References: <CAOHKUnLoCc57y+BBCiXMA4u735_upA47vadX9EFtSMnEdNkxng@mail.gmail.com>
Message-ID: <525128C7.5010202@python.org>

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

Am 27.07.2013 20:13, schrieb Hugh O'Brien:
> Section 2.2.5 shows the following demo code:
> 
>>>> import site site.getusersitepackages()
> '/home/user/.local/lib/python3.2/site-packages'
> 
> The path provided is for python3, not 2.
> 
> Thanks for the docs,
> 
> Hugh

Hi Hugh,

thanks for the report, this is now fixed and will be online soon.

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

iEYEARECAAYFAlJRKMcACgkQN9GcIYhpnLDdxACbBC1QmCzzVKihphDQL60q4miS
vfcAmgJB3mK6Jcr2fif17q0PAbW/IcAS
=1ufM
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:09:46 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:09:46 +0200
Subject: [docs] minor bug in
	http://docs.python.org/3/tutorial/modules.html
In-Reply-To: <CAOHKUnKuK1i+Js9UPDfiGkU56uty0tuHrksxkmJB-ud0SoQX_Q@mail.gmail.com>
References: <CAOHKUnKuK1i+Js9UPDfiGkU56uty0tuHrksxkmJB-ud0SoQX_Q@mail.gmail.com>
Message-ID: <525128DA.6000603@python.org>

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

Am 29.07.2013 00:04, schrieb Hugh O'Brien:
> In section 6.4 the example file hierarchy seems to be affected by Python
> syntax highlighting, resulting in the 'for' term appearing bold.
> 

Hi Hugh,

this is now also fixed and will be online soon.  Thanks for the reports
and your patience.

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

iEYEARECAAYFAlJRKNoACgkQN9GcIYhpnLBC0gCgjE11fIJTnp35vvj9FEpqqmW2
/7oAn2xrFcpEvSvWoaJTErNKF4HXFwN8
=Dse2
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:11:52 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:11:52 +0200
Subject: [docs] Unittest documentation points to deprecated resource
In-Reply-To: <CAOoSJ_qwYnLskw055Mmc9OWwgqib_RvmaaQ31Sx4FD7x-94H_w@mail.gmail.com>
References: <CAOoSJ_qwYnLskw055Mmc9OWwgqib_RvmaaQ31Sx4FD7x-94H_w@mail.gmail.com>
Message-ID: <52512958.2090506@python.org>

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

Am 27.07.2013 12:21, schrieb Daniel Greenfeld:
> On http://docs.python.org/2/library/unittest.html
> 
> The "seealso" includes a link to "The Python Testing Tools Taxonomy", which
> states that it is deprecated in favor of contents on the official Python
> wiki: http://wiki.python.org/moin/PythonTestingToolsTaxonomy

Hi Daniel,

thanks for the report; this is now fixed and will appear online soon.

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

iEYEARECAAYFAlJRKVgACgkQN9GcIYhpnLCIaACdF8NjUMXoROPbG24hJKpXQTQx
tOQAnilelsP0LMqUopbhhXL50/Wm0xJu
=+tY0
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:13:01 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:13:01 +0200
Subject: [docs] very miscellaneous doc bug
In-Reply-To: <CAN_7T0+ay0Avr9xU53i0pfgv-MSGnEsM+pvZEGNb69cnUAaBPw@mail.gmail.com>
References: <CAN_7T0+ay0Avr9xU53i0pfgv-MSGnEsM+pvZEGNb69cnUAaBPw@mail.gmail.com>
Message-ID: <5251299D.5070109@python.org>

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

Am 22.07.2013 22:02, schrieb tomo cocoa:
> Hello
> 
> I am a translator on Japanese Python documents.
> 
> A period was omitted after the word ":func:`distutils.util.execute`"
> 
> http://docs.python.org/3.3/distutils/apiref.html#distutils.ccompiler.CCompiler.execute
>
>  Excuse me for reporting a small mistake :p

Hi tomo,

thanks for the report; this is now fixed.

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

iEYEARECAAYFAlJRKZ0ACgkQN9GcIYhpnLCbrgCffG2RxJw9YW9acJ9FZ7zB1G6V
Lz0An3HI43BSMtNgMKMq6rQA+xilaTLy
=3pl5
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:19:17 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:19:17 +0200
Subject: [docs] There is a spelling mistakes in Python source code
In-Reply-To: <BLU402-EAS1031633E217291364CBAFFF9D5F0@phx.gbl>
References: <BLU402-EAS1031633E217291364CBAFFF9D5F0@phx.gbl>
Message-ID: <52512B15.8030101@python.org>

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

Am 08.08.2013 14:48, schrieb ???:
> Hello: I found there is a spelling mistakes in Python source code comment. 
> In file: Python\lib\_pyio.py Line 413: """closed: bool.  True iff the file
> has been closed. Best regards! peipei

Hi peipei,

this is in fact not a mistake; "iff" is a common abbreviation for
"if and only if".

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

iEUEARECAAYFAlJRKxUACgkQN9GcIYhpnLA7PACYyEOANwR9p75z7eIsV2SOmOUM
IQCfU3SQMBebwmxBXAdaZk08sHHoL3c=
=WB/X
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct  6 11:20:14 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:20:14 +0000
Subject: [docs] [issue18529] Use long dash
In-Reply-To: <1374499433.16.0.583158051605.issue18529@psf.upfronthosting.co.za>
Message-ID: <1381051214.29.0.945336706926.issue18529@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Agreed.

----------
nosy: +georg.brandl
resolution:  -> wont fix
status: open -> closed

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

From georg at python.org  Sun Oct  6 11:25:12 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:25:12 +0200
Subject: [docs] Possible error
In-Reply-To: <CAALHx9R-ncGqUnO4fXcoZiEqA2RnWqoSrsHwo4Q=ttojSf07sQ@mail.gmail.com>
References: <CAALHx9R-ncGqUnO4fXcoZiEqA2RnWqoSrsHwo4Q=ttojSf07sQ@mail.gmail.com>
Message-ID: <52512C78.2050709@python.org>

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

Am 04.07.2013 15:34, schrieb Blanca Mancilla:
> Hi, I'm going through the documentation and came across the following
> error:
> 
> in http://docs.python.org/2.7/tutorial/interpreter.html, in the Source
> Encoding Section, there is a program:
> 
> # -*- coding: iso-8859-15 -*-
> 
> currency = u"?" print ord(currency)
> 
> which presents a problem when running:
> 
> 
> Traceback (most recent call last):
> 
> File "encoding.py", line 6, in <module> print ord(currency) TypeError:
> ord() expected a character, but string of length 3 found
> 
> but if I change the encoding to UTF-8 it works:
> 
> 
> # -*- coding: UTF -*-
> 
> it give the desired results. Not sure if it is a real bug.

Hi Blanca,

the encoding declaration has to match the actual encoding of the source file.
It appears that your editor saves as UTF-8 by default.

I have clarified this now; it should be online soon.

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

iEYEARECAAYFAlJRLHgACgkQN9GcIYhpnLB+kQCgkFTNXoT6bPxJrOiHRU5ZyPQB
11wAn3nUeUyxLyST5IIMenD6kNiZgAVd
=vVqT
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:26:34 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:26:34 +0200
Subject: [docs] About loops
In-Reply-To: <CAALHx9T+0BW_Rv-ixw4-w=kVm+rcShoh0ukhLq54h2Ud8Y5Hzw@mail.gmail.com>
References: <CAALHx9T+0BW_Rv-ixw4-w=kVm+rcShoh0ukhLq54h2Ud8Y5Hzw@mail.gmail.com>
Message-ID: <52512CCA.8050405@python.org>

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

Am 05.07.2013 14:26, schrieb Blanca Mancilla:
> Hi, In section 4.4 break and continue Statements and else Clauses in loops,
> the first program has an issue: the second for: for x in range(2,n) is not
> entered in the first iteration of the n for (for n in range(2,10)) as range
> (2,2) give an empty range:
> 
>>>> range(2,2)
> []
> 
> therefore 2 is never "declared" prime.
> 
> Also the break is in the wrong place.

Hi Blanca,

if you look closely at the source, the "else" clause belongs to the "for"
loop.  If you indent the clause correctly, the code will work as expected.

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

iEYEARECAAYFAlJRLMoACgkQN9GcIYhpnLDrFwCdFAF2SlbI5weQCU0AVFhg0W9i
9uwAnj0FZOVu1Yso6Y7vxqBsiVRVPquX
=ew97
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:27:50 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:27:50 +0200
Subject: [docs] bytearray and language usage.
In-Reply-To: <CAMjeLr9vrc0zUPrk4vkvZ4+UmCgtZb=xPM15bV2TocWGUNvZ0Q@mail.gmail.com>
References: <CAMjeLr9vrc0zUPrk4vkvZ4+UmCgtZb=xPM15bV2TocWGUNvZ0Q@mail.gmail.com>
Message-ID: <52512D16.9070800@python.org>

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

Am 28.06.2013 01:50, schrieb Mark Janssen:
> Looking at the Python docs for v2.7.5.
> 
> Section 2.
> 
> bytearray([source[, encoding[, errors]]])
> 
> "  Return a new array of bytes. The bytearray type is a mutable sequence of
> integers in the range 0 <= x < 256."
> 
> This should not be called a "mutable sequence of integers", because to call
> them "integers" already casts raw bits into a particular *type*. They
> could, hypothetically be very short floats, for example.
> 
> More accurately, they are merely "uninterpreted bits presented to the user
> in 8-bit chunks, with a consistent starting boundary" (held by the machine
> storage address).

Hi Mark,

the language is actually correct; Python treats bytearrays as sequences
of integers.  Try this:

>>> list(bytearray(b"abc"))
[97, 98, 99]

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

iEYEARECAAYFAlJRLRYACgkQN9GcIYhpnLCDIACfSAgx4jI0ye8o6Dk+Tc1KbPPl
8VcAn0vSiK4JkaIU49HLu6t7K0kTj9po
=sKwd
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 11:28:54 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:28:54 +0200
Subject: [docs] I found bugs in the Queue documentation
In-Reply-To: <CAEpyERub=nGZ3eptdK9L5ZEHCzqmSHzYa3OjiUtgxS1kUe6JHA@mail.gmail.com>
References: <CAEpyERub=nGZ3eptdK9L5ZEHCzqmSHzYa3OjiUtgxS1kUe6JHA@mail.gmail.com>
Message-ID: <52512D56.7010808@python.org>

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

Am 28.06.2013 08:09, schrieb ???:
> http://docs.python.org/2/library/queue.html
> 
> There are two typing errors in this document
> 
> http://docs.python.org/2/library/queue.html#Queue.Queue.put 
> http://docs.python.org/2/library/queue.html#Queue.Queue.get
> 
> there is a same sentence within this two function descriptions,
> 
> If optional args /block/ is true and /timeout/ is None (the default)
> 
> In this sentence, I think it should be "True" not "true" because it stands
> for actual python Boolean value.

Hi ??,

the documents are actually correct; we use "true" when we mean "any object
that is considered true by bool()".

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

iEYEARECAAYFAlJRLVYACgkQN9GcIYhpnLD/DgCeMQzYGdgpjlQI2jnpHLLFcIhF
5UgAoKqyAjA+Ie+iCqW/9bGSAhu5mimA
=CiHy
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct  6 11:44:33 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 09:44:33 +0000
Subject: [docs] [issue19129] 6.2.1. Regular Expression Syntax flags
In-Reply-To: <1380470947.27.0.0292455287204.issue19129@psf.upfronthosting.co.za>
Message-ID: <1381052673.86.0.125936166294.issue19129@psf.upfronthosting.co.za>


Georg Brandl added the comment:

This is intended, the U flag is a legacy flag that is not supposed to by used in new code.

----------
nosy: +georg.brandl
resolution:  -> rejected
status: open -> closed

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

From report at bugs.python.org  Sun Oct  6 12:08:15 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 10:08:15 +0000
Subject: [docs] [issue15956] backreference to named group does not work
In-Reply-To: <1347888827.23.0.363134887653.issue15956@psf.upfronthosting.co.za>
Message-ID: <3ct0rZ30HrzRNt@mail.python.org>


Roundup Robot added the comment:

New changeset bee2736296c5 by Georg Brandl in branch '2.7':
Closes #15956: improve documentation of named groups and how to reference them.
http://hg.python.org/cpython/rev/bee2736296c5

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

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

From report at bugs.python.org  Sun Oct  6 12:08:26 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 10:08:26 +0000
Subject: [docs] [issue15956] backreference to named group does not work
In-Reply-To: <1347888827.23.0.363134887653.issue15956@psf.upfronthosting.co.za>
Message-ID: <3ct0rn4YQQz7Ljp@mail.python.org>


Roundup Robot added the comment:

New changeset f765a29309d1 by Georg Brandl in branch '3.3':
Closes #15956: improve documentation of named groups and how to reference them.
http://hg.python.org/cpython/rev/f765a29309d1

----------

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

From report at bugs.python.org  Sun Oct  6 12:10:21 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 10:10:21 +0000
Subject: [docs] [issue15956] backreference to named group does not work
In-Reply-To: <1347888827.23.0.363134887653.issue15956@psf.upfronthosting.co.za>
Message-ID: <1381054221.42.0.937988370865.issue15956@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thanks for the patch.  I made a few changes, such as explaining what the example pattern does.

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

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

From georg at python.org  Sun Oct  6 12:37:42 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 12:37:42 +0200
Subject: [docs] Typo in collections.Counter class example
In-Reply-To: <CADzNYBef4TKqA-NH-r2dbHfKnS675R5RYyEFxFGw4pXOaAMnRg@mail.gmail.com>
References: <CADzNYBef4TKqA-NH-r2dbHfKnS675R5RYyEFxFGw4pXOaAMnRg@mail.gmail.com>
Message-ID: <52513D76.4080609@python.org>

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

Am 05.06.2013 19:16, schrieb ?????? ???????:
> Hello,
> 
> It seems that I found micro bug in Python documentation describing 
> collections.Counter class 
> <http://docs.python.org/3.3/library/collections.html#counter-objects>. 
> There is the following snippet of code
> 
> c.most_common()[:-n:-1]         # n least common elements
> 
> Actually this expression returns not /n/ least common elements, but rather
> /n - 1,/ beacuse second boundary  is not included (as usual with slices). 
> You probably meant c.most_common()[-n:] orc.most_common()[:-n-1:-1] if
> reverse ordering is nesessary.

Hi Mikhail,

thanks for the report; this is now fixed and will appear online soon.

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

iEYEARECAAYFAlJRPXYACgkQN9GcIYhpnLAtSgCaApE3cvKKFIhzGywsaeYgD6W3
cewAoLAFPh8sEA7HP5ulqF5w5L6p5gvg
=vHAo
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 12:39:55 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 12:39:55 +0200
Subject: [docs] Should say 'REAL' not 'FLOAT' as the SQLite datatype in
 11.13.1 of sqlite3.
In-Reply-To: <51B33EF1.6090601@millstream.com>
References: <51B33EF1.6090601@millstream.com>
Message-ID: <52513DFB.30905@python.org>

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

Am 08.06.2013 16:25, schrieb Richard Kelsall:
> Hello Python Docs,
> 
> 
> TLDR: I think it should probably say 'REAL' not 'FLOAT' as the SQLite 
> datatype in 11.13.1 of sqlite3.
> 
> 
> I am reading the sqlite3 page
> 
> http://docs.python.org/2/library/sqlite3.html
> 
> for Python v2.7.5. It says in 11.13.1:
> 
> "SQLite natively supports only the types TEXT, INTEGER, FLOAT, BLOB and 
> NULL."
> 
> This made me wonder, is this a double or single FLOAT? (I have not used 
> this database or this Python module before.) And I looked in the SQLite 
> documentation here
> 
> http://sqlite.org/datatype3.html
> 
> This says that SQLite version 3 uses an 8 byte (i.e. double) float and has
> this as type REAL. So I go back to the python page thinking maybe this is
> an earlier version of SQLite - maybe Python 2 provides SQLite 2 for
> backwards compatibility and the module name 'sqlite3' does not follow the
> SQLite version number for some reason. I cannot see on this page mention of
> what version of SQLite this module provides, maybe I missed that? But I see
> in 11.13.5.1:
> 
> "SQLite natively supports the following types: NULL, INTEGER, REAL, TEXT,
> BLOB."
> 
> So this internal contradiction makes me think section 11.13.1 is 
> incorrect.
> 
> I feel posting to this public list, of unknown proportions, may be a rather
> loud way of reporting such a minor problem, but the documentation page
> seems to ask me to do this. A wiki might have been an easier and less noisy
> way to suggest corrections. I expect many people would not go to the
> trouble of emailing a public mailing list to get a detail like this
> corrected and that there are many similar bugs which are found but not
> immediately reported for this reason.

Hi Richard,

posting here is exactly the right way of reporting, even if it sometimes
takes a while :)  Thanks for the report, I've fixed this now and it will
appear online soon.

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

iEYEARECAAYFAlJRPfsACgkQN9GcIYhpnLDhiwCgqDZhLgO747r5Y1B4M959NUBr
i7oAoIZstIh7LVI72b+NFB4LHcYmUMEr
=3xIi
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 12:41:39 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 12:41:39 +0200
Subject: [docs] binascii.b2a_base64 can convert data length more than 57
In-Reply-To: <C56D1F42E5FDF943894DEECA8D1D03547BD65084@ALA-MBA.corp.ad.wrs.com>
References: <C56D1F42E5FDF943894DEECA8D1D03547BD65084@ALA-MBA.corp.ad.wrs.com>
Message-ID: <52513E63.5010908@python.org>

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

Am 05.06.2013 05:09, schrieb Chen, Liying:
> Hi,
> 
> 
> 
> In the document binascii.b2a_base64(data) said the data length should less
> than 57.But I can use it for more than 57.Can you give me an explain?
> 
> 
> 
>>>> import struct import binascii payload =
>>>> struct.pack('>hhiii',4,0,0,0,0) payload = payload*10 len(payload)
> 160
>>>> binascii.b2a_base64(payload)
> 'AAQAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAA==\n'
>>>>
> 
a = binascii.b2a_base64(payload)
>>>> len(a)
> 217
>>>> 

Hi Liying,

the function itself can process arbitrary lengths.  The documentation just
states that if you want the *result* to be compatible to the base64 standard,
the input should be <= 57 characters in length.

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

iEYEARECAAYFAlJRPmMACgkQN9GcIYhpnLDK9gCglvQZYDlpj+aCw3//PwxWOWyo
pMoAnivHlRIPjlXuBDkfy/xGFdiGllKS
=7eiH
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 12:43:01 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 12:43:01 +0200
Subject: [docs] Bug in last httplib example in Python 2.7.5 docs in
 section 20.7.3
In-Reply-To: <CAFU4XYdkojKSqptBw-CZS-A155r6d-JQFyuNEqjb_RL7kcA_9g@mail.gmail.com>
References: <CAFU4XYdkojKSqptBw-CZS-A155r6d-JQFyuNEqjb_RL7kcA_9g@mail.gmail.com>
Message-ID: <52513EB5.8020208@python.org>

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

Am 04.06.2013 15:37, schrieb Alex MacAulay:
> On the following page in the Python 2.7.5 docs: 
> http://docs.python.org/2/library/httplib.html In section 20.7.3, the last
> example has:
> 
>>>> response = conn.getresponse() print resp.status, response.reason
> 
> 
> However it should be:
> 
>>>> response = conn.getresponse() print response.status, response.reason

Hi Alex,

thanks for the report; this is now fixed and should appear online soon.

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

iEYEARECAAYFAlJRPrUACgkQN9GcIYhpnLCRLQCfWzduaPFBizKhYjWEbF6x8tLv
zW4AnA8A9aeGnjZPztjZUye/Y/ddm3Gg
=qfbo
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 12:46:57 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 12:46:57 +0200
Subject: [docs] Wrong toolkit for PythonCAD
In-Reply-To: <CAMoy75XFqKzjfouvNZ=AyEU=NsgJQzaxXT2Ti5Y0vQjVm6-cig@mail.gmail.com>
References: <CAMoy75XFqKzjfouvNZ=AyEU=NsgJQzaxXT2Ti5Y0vQjVm6-cig@mail.gmail.com>
Message-ID: <52513FA1.4030700@python.org>

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

Am 03.06.2013 13:37, schrieb Helge Stenstr?m:
> According to http://docs.python.org/2/library/othergui.html, PythonCAD is 
> written in pygtk, but according to the project page, 
> http://sourceforge.net/projects/pythoncad/, it uses PyQt.

Hi Helge,

thanks for the report; I've now replaced the example by Wing IDE.

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

iEYEARECAAYFAlJRP6EACgkQN9GcIYhpnLCoUACeK7GEJJM0u45THw+dAqB1w6hA
L/cAn0rxleO/k5CXwbTLPJ2BOcr3abkg
=cAeb
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct  6 12:50:31 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 10:50:31 +0000
Subject: [docs] [issue15172] Document nasm-2.10.01 as required version for
	openssl
In-Reply-To: <1340569947.64.0.165180800824.issue15172@psf.upfronthosting.co.za>
Message-ID: <1381056631.61.0.646077558076.issue15172@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Fixed, I guess?

----------
nosy: +georg.brandl
resolution:  -> fixed
status: open -> closed

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

From georg at python.org  Sun Oct  6 12:53:11 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 12:53:11 +0200
Subject: [docs] venv 3.3.2 docs - "create_directories" should be
	"ensure_directories"
In-Reply-To: <CANKxYhu3iKcXo6xbH+VysmTKZ+YDoG2dxUSoNSPGYvtQ=oeqUg@mail.gmail.com>
References: <CANKxYhu3iKcXo6xbH+VysmTKZ+YDoG2dxUSoNSPGYvtQ=oeqUg@mail.gmail.com>
Message-ID: <52514117.6060208@python.org>

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

Am 16.06.2013 03:27, schrieb Michael Rand:
> To whom it may concern,
> 
> When subclassing venv.EnvBuilder and customizing create(), the docs say
> that one should use "self.create_directories(env_dir)".
> 
> This call raises an AttributeError. When looking at the subclass, I don't
> see "create_directories" but instead I see the method "ensure_directories",
> which has the following docstring:
> 
> "Create the directories for the environment".
> 
> It seems like either the docs should be fixed to reflect
> "ensure_directories" as the appropriate method name or the method should be
> renamed "create_directories".
> 
> Apologies if I'm mistaken on this ... this is my first doc bug report.

Hi Michael,

thanks for the report; this is now fixed and will be online soon.

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

iEYEARECAAYFAlJRQRcACgkQN9GcIYhpnLC2xACePdRqKwSXOfwVt2UgER4zyksy
SvIAn1XfyFQFiuvcMNZsGczuFomnlnyY
=2EGR
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct  6 12:53:42 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 10:53:42 +0000
Subject: [docs] [issue18229] attribute headers of
	http.server.BaseHTTPRequestHandler	sometimes does not exists
In-Reply-To: <1371376761.5.0.41138715811.issue18229@psf.upfronthosting.co.za>
Message-ID: <1381056822.14.0.617925139945.issue18229@psf.upfronthosting.co.za>


Georg Brandl added the comment:

This appears to be a bug in the _lowerHTTP module, which does not ship with Python.

----------
nosy: +georg.brandl
resolution:  -> invalid
status: open -> closed

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

From georg at python.org  Sun Oct  6 12:58:52 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 12:58:52 +0200
Subject: [docs] bug in re documentation (python 3.3.2)
In-Reply-To: <CALMUFh9oKi_W6TWTD08B9jbs-eZ019ipxftzksMP_zFH_u8vxQ@mail.gmail.com>
References: <CALMUFh9oKi_W6TWTD08B9jbs-eZ019ipxftzksMP_zFH_u8vxQ@mail.gmail.com>
Message-ID: <5251426C.7000507@python.org>

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

Am 27.06.2013 02:25, schrieb Alexander Heger:
> http://docs.python.org/3.3/library/re.html
> 
> 6.2.1. Regular Expression Syntax
> 
> (way down)
> 
> it says:
> 
> \number Matches the contents of the group of the same number. Groups are
> numbered starting from 1. For example, (.+) \1 matches 'the the' or '55
> 55', but not 'the end' (note the space after the group). This special
> sequence can only be used to match one of the first 99 groups. If the first
> digit of number is 0, or number is 3 octal digits long, it will not be
> interpreted as a group match, but as the character with octal value number.
> Inside the '[' and ']' of a character class, all numeric escapes are
> treated as characters.
> 
> The example of what does not work is wrong
> 
> In [1]: import re
> 
> In [2]: re.findall(r'(.+) \1','the end') Out[2]: ['e']
> 
> It probably should be
> 
> \number Matches the contents of the group of the same number. Groups are
> numbered starting from 1. For example, (.+) \1 matches 'the the' or '55
> 55', but not 'thethe' (note the space after the group). This special
> sequence can only be used to match one of the first 99 groups. If the first
> digit of number is 0, or number is 3 octal digits long, it will not be
> interpreted as a group match, but as the character with octal value number.
> Inside the '[' and ']' of a character class, all numeric escapes are
> treated as characters.

Hi Alexander,

thanks for the report; this is now fixed and should be online soon.

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

iEYEARECAAYFAlJRQmwACgkQN9GcIYhpnLALdgCdG16SAUH9eBZWjXNnl6yWGkeW
0bcAnRXELerjnSVWaAO2yx4F/iWZPqLR
=c8Xy
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 13:01:45 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 13:01:45 +0200
Subject: [docs] Tutorial bug
In-Reply-To: <CA+ks6EcsB3A3+DHXh6Fnd0RG8dNiSgj1Ubx0GSJ03iY6sJxvFw@mail.gmail.com>
References: <CA+ks6EcsB3A3+DHXh6Fnd0RG8dNiSgj1Ubx0GSJ03iY6sJxvFw@mail.gmail.com>
Message-ID: <52514319.3080102@python.org>

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

Am 28.05.2013 22:36, schrieb Leonardo Pereira:
> http://docs.python.org/3.3/tutorial/datastructures.html does not list
> .clear() and .copy() methods introduced in 3.3

Hi Leonardo,

thanks for the report; this is now fixed and will appear online soon.

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

iEYEARECAAYFAlJRQxkACgkQN9GcIYhpnLA3+gCghfG292yrZPODMhXlTOt/FKH2
J5IAniZnZekGrPNkXV6C9L+/8rrlBY48
=wy5B
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct  6 13:02:09 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:02:09 +0000
Subject: [docs] [issue19179] doc bug: confusing table of values
In-Reply-To: <52514342.6020404@python.org>
Message-ID: <1381057329.1.0.0569009623579.issue19179@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
assignee:  -> docs at python
components: +Documentation
nosy: +christian.heimes, docs at python

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

From report at bugs.python.org  Sun Oct  6 13:03:16 2013
From: report at bugs.python.org (Martin Panter)
Date: Sun, 06 Oct 2013 11:03:16 +0000
Subject: [docs] [issue12350] Improve stat_result.st_blocks and
	st_blksize	documentation
In-Reply-To: <1308256127.22.0.581997138097.issue12350@psf.upfronthosting.co.za>
Message-ID: <1381057396.18.0.224946778178.issue12350@psf.upfronthosting.co.za>


Martin Panter added the comment:

What happened to this patch? The current documentation is very misleading because the descriptions of the two block fields appear to complement each other.

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

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

From report at bugs.python.org  Sun Oct  6 13:07:47 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:07:47 +0000
Subject: [docs] [issue19180] some RFC references could be updated
In-Reply-To: <519ADE01.7090104@ieca.com>
Message-ID: <525144B9.3040305@python.org>


New submission from Georg Brandl:

-------- Original-Nachricht --------
Betreff: [docs] some RFC references could be updated
Datum: Mon, 20 May 2013 22:37:53 -0400
Von: Sean Turner <turners at ieca.com>
An: docs at python.org

Hi,

Just starting to learn python and have noted that at the bottom of this
page:

http://docs.python.org/3/library/ssl.html

There's a couple of out of date references:

0) RFC 1750 has been been obsoleted by RFC 4086 so maybe this is a
better reference (and I prefer the datatracker view as opposed to the
tools view):

http://datatracker.ietf.org/doc/rfc4086/

Same could be done on this link:

http://docs.python.org/3.4/library/ssl.html

1) RFC 3280 has been obsoleted by RFC 5280 so maybe:

http://datatracker.ietf.org/doc/rfc5280/

Same could be done on this link:

http://docs.python.org/3.4/library/ssl.html

2) RFC 4366 has been obsoleted by RFC 6066 so maybe:

http://datatracker.ietf.org/doc/rfc6066/

On http://docs.python.org/3.4/library/ssl.html you could probably just
drop the reference and change in the ssl.HAS_SNI section.

3) The link to TLS seems broken maybe just point to:

TLS 1.0 http://datatracker.ietf.org/doc/rfc2246/
TLS 1.1 http://datatracker.ietf.org/doc/rfc4346/
TLS 1.2 http://datatracker.ietf.org/doc/rfc5246/
SSL 3.0 http://datatracker.ietf.org/doc/rfc6101/

Actually the same link is broken on:

http://docs.python.org/3.4/library/ssl.html

4) (this is a shameless plug) Might be worth adding a reference in the
ssl.PROTOCOL_SSLv2 section that points to:

http://datatracker.ietf.org/doc/rfc6146/

----------
assignee: docs at python
components: Documentation
messages: 199069
nosy: docs at python, georg.brandl
priority: normal
severity: normal
status: open
title: some RFC references could be updated

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

From georg at python.org  Sun Oct  6 13:10:30 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 13:10:30 +0200
Subject: [docs] [BUG]About `add_mutually_exclusive_group' in argparse
 module doc
In-Reply-To: <5193B8D1.8050106@gmail.com>
References: <5193B8D1.8050106@gmail.com>
Message-ID: <52514526.1010903@python.org>

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

Am 15.05.2013 18:33, schrieb Tanky Woo:
> Today, I read the argparse doc and find the Mutual exclusion 
> section(http://docs.python.org/2/library/argparse.html#mutual-exclusion)
> has a problem
> 
> 
> The function `*add_mutually_exclusive_group*' in the section is :
> 
> *argparse.add_mutually_exclusive_group(required=False)*
> 
> but add_mutually_exclusive_group belongs to *ArgumentParser* object, not
> direct to *argparse*, maybe this is a bug?

Hi,

thanks for the report, this is indeed a bug.  I fixed it and it should appear
online soon.

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

iEYEARECAAYFAlJRRSYACgkQN9GcIYhpnLAvJgCgo3YGhcVYlw9zKCdBK+dXZwkE
FgsAoIJIML+cvQD/HFzOC/RZhnE/iTVg
=bmgx
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 13:17:41 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 13:17:41 +0200
Subject: [docs] I suspect a reversal
In-Reply-To: <E1UaWu7-0005Om-OO@utter.chaos.org.uk>
References: <E1UaWu7-0005Om-OO@utter.chaos.org.uk>
Message-ID: <525146D5.5010607@python.org>

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

Am 09.05.2013 21:53, schrieb Edward Welbourne:
> Hi doc-team,
> 
> On http://docs.python.org/3/library/codecs.html under codecs.register, I
> see the description: <quote>
> 
> streamreader and streamwriter: These have to be factory functions providing
> the following interface:
> 
> factory(stream, errors='strict')
> 
> The factory functions must return objects providing the interfaces defined
> by the base classes StreamWriter and StreamReader, respectively.
> 
> </quote> and am instantly suspicious: apparently, streamreader should have
> the interface of StreamWriter and streamwrite that of StreamReader. This is
> either a doc bug or a horribly bad choice of names for the .register()
> function's parameters !

Hi Edward,

thanks for the report; this was indeed a bug in the docs, is now fixed and
should appear online soon.

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

iEYEARECAAYFAlJRRtUACgkQN9GcIYhpnLA1BwCfY8aI0o1MoaRgiIKGww8mfSRC
2YYAn3qJ9E0fF+8CJ7cLUodoEki7yraF
=yj+P
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 13:25:09 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 13:25:09 +0200
Subject: [docs] Typo in distutils document
In-Reply-To: <CALqAb4xVtwZ8Xxjgbj3HH4eeQ2foFRTKRdrmEhXMZF9OC5R=xg@mail.gmail.com>
References: <CALqAb4xVtwZ8Xxjgbj3HH4eeQ2foFRTKRdrmEhXMZF9OC5R=xg@mail.gmail.com>
Message-ID: <52514895.1070103@python.org>

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

Am 23.04.2013 04:01, schrieb Bo Bayles:
> Hello,
> 
> I noticed a typo in the distutils module's documentation, e.g. at: 
> http://docs.python.org/3/library/distutils.html
> 
> It currently reads: " If also contains instructions for end-users..."
> 
> It should read: "It also contains instructions for end-users..."
> 
> Best regards, -Bo

Hi Bo,

thanks for the report; this is now fixed.

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

iEYEARECAAYFAlJRSJUACgkQN9GcIYhpnLAJVQCeKjJryjiz36MHs0DrVNUZmiWt
rrsAoJVZnWgE8EC/tsbCOZ+WdVhtKQM1
=7iXF
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct  6 13:28:44 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 11:28:44 +0000
Subject: [docs] [issue19181] ftp.cwi.nl used as example does not exist
	anymore
In-Reply-To: <002d01cded5f$6d1fa980$475efc80$@gravitymarketing.com.au>
Message-ID: <525149A2.2010402@python.org>


New submission from Georg Brandl:

ftp.python.org doesn't seem to listen on port 21 either... anyone know a public
FTP server we can use as example?

-------- Original-Nachricht --------
Betreff: 	[docs] quick note on ftplib for python
Datum: 	Tue, 8 Jan 2013 16:17:14 +1100
Von: 	Jeremy Orchard <jeremy at gravitymarketing.com.au>
An: 	<docs at python.org>

Hello,

Quick note, ftplib gives example host ftp.cwi.nl

In its documentation which is a url which is no longer active? when you try the
dummy example, ftplib doesn?t really output a clear error so it might be worth
updating the host, (though most programmers should assume this quickly),

Python 2.7 > documentation for ftplib which introduced the feature FTP_TLS gives
the examplehost ftp.python.org <ftp://ftp.python.org> which is possibly the
ideal candidate for the change.

Not really a bug, thought id save you the trouble by reporting just incase, it
was something worth changing.

----------
assignee: docs at python
components: Documentation
messages: 199070
nosy: docs at python, georg.brandl
priority: normal
severity: normal
status: open
title: ftp.cwi.nl used as example does not exist anymore

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

From report at bugs.python.org  Sun Oct  6 13:52:32 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 06 Oct 2013 11:52:32 +0000
Subject: [docs] [issue19181] ftp.cwi.nl used as example does not exist
	anymore
In-Reply-To: <525149A2.2010402@python.org>
Message-ID: <1381060352.04.0.896759535158.issue19181@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

ftp://ftp.ietf.org/ ? ftp://ftp.debian.org/ ?

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

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

From report at bugs.python.org  Sun Oct  6 14:51:23 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 06 Oct 2013 12:51:23 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381063883.47.0.239390684809.issue18758@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Serhiy, are you planning to work on more patches or can this be closed?

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

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

From report at bugs.python.org  Sun Oct  6 16:50:40 2013
From: report at bugs.python.org (Jordan Szubert)
Date: Sun, 06 Oct 2013 14:50:40 +0000
Subject: [docs] [issue18229] attribute headers of
	http.server.BaseHTTPRequestHandler	sometimes does not exists
In-Reply-To: <1371376761.5.0.41138715811.issue18229@psf.upfronthosting.co.za>
Message-ID: <1381071040.18.0.246214788539.issue18229@psf.upfronthosting.co.za>


Jordan Szubert added the comment:

what _lowerHTTP does is try read request header 'X-Forwarded-For', but instance of request handler have attribute headers only if thing that connected to port where server listens happened to send valid enough http request

my problem is, documentation does not help write code that would not crash when client sends random bytes instead of expected http request

----------
resolution: invalid -> 
status: closed -> open

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

From report at bugs.python.org  Sun Oct  6 17:18:33 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sun, 06 Oct 2013 15:18:33 +0000
Subject: [docs] [issue16355] inspect.getcomments() does not work in the
	interactive	shell
In-Reply-To: <1351511930.82.0.59071323276.issue16355@psf.upfronthosting.co.za>
Message-ID: <1381072713.14.0.898477062922.issue16355@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

I pep-8 Phil Connell's work and revamped the unit test based on  R. David Murray's request.

----------
nosy: +vajrasky
Added file: http://bugs.python.org/file31975/issue16355_v2.diff

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

From report at bugs.python.org  Sun Oct  6 17:39:49 2013
From: report at bugs.python.org (Jordan Szubert)
Date: Sun, 06 Oct 2013 15:39:49 +0000
Subject: [docs] [issue18229] attribute headers of
	http.server.BaseHTTPRequestHandler	sometimes does not exists
In-Reply-To: <1371376761.5.0.41138715811.issue18229@psf.upfronthosting.co.za>
Message-ID: <1381073989.11.0.419670748927.issue18229@psf.upfronthosting.co.za>


Jordan Szubert added the comment:

#minimal server:
#!/c/Python33/python.exe
from http.server import HTTPServer as S, BaseHTTPRequestHandler as H
class HNDL(H):
	def log_request(req,code):
		print('header is',req.headers.get('X-Forwarder-For'),', code',code)
		H.log_request(req)
s=S(('',54321),HNDL)
s.serve_forever()


#non-http client:
#!/c/Python33/python.exe
import socket,os
s=socket.socket(socket.AF_INET, socket.SOCK_STREAM)
s.connect(('localhost', 54321))
s.sendall(os.urandom(1024))
buf=s.recv(2048)
s.close()
print(buf)


#running server:
$ ./server.py
127.0.0.1 - - [06/Oct/2013 17:33:41] code 400, message Bad HTTP/0.9 request type
 ('E)\xaeE^2?\xf2W\x8f\xb3aG')
----------------------------------------
Exception happened during processing of request from ('127.0.0.1', 18234)
Traceback (most recent call last):
  File "c:\Python33\lib\socketserver.py", line 306, in _handle_request_noblock
    self.process_request(request, client_address)
  File "c:\Python33\lib\socketserver.py", line 332, in process_request
    self.finish_request(request, client_address)
  File "c:\Python33\lib\socketserver.py", line 345, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "c:\Python33\lib\socketserver.py", line 666, in __init__
    self.handle()
  File "c:\Python33\lib\http\server.py", line 400, in handle
    self.handle_one_request()
  File "c:\Python33\lib\http\server.py", line 380, in handle_one_request
    if not self.parse_request():
  File "c:\Python33\lib\http\server.py", line 311, in parse_request
    "Bad HTTP/0.9 request type (%r)" % command)
  File "c:\Python33\lib\http\server.py", line 428, in send_error
    self.send_response(code, message)
  File "c:\Python33\lib\http\server.py", line 443, in send_response
    self.log_request(code)
  File "./server.py", line 5, in log_request
    print('header is',req.headers.get('X-Forwarder-For'),', code',code)
AttributeError: 'HNDL' object has no attribute 'headers'
----------------------------------------


#running client:
$ ./client.py
b''
$

----------

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

From report at bugs.python.org  Sun Oct  6 17:43:34 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 15:43:34 +0000
Subject: [docs] [issue18229] attribute headers of
	http.server.BaseHTTPRequestHandler	sometimes does not exists
In-Reply-To: <1371376761.5.0.41138715811.issue18229@psf.upfronthosting.co.za>
Message-ID: <1381074214.49.0.502571202982.issue18229@psf.upfronthosting.co.za>


Georg Brandl added the comment:

OK, so I guess it could be documented that the "headers" attribute is not set if the request cannot be parsed as a HTTP request.  That's a valid point.

By the way, you should really call your "self" argument "self".

----------
versions: +Python 2.7, Python 3.4

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

From report at bugs.python.org  Sun Oct  6 18:11:32 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:11:32 +0000
Subject: [docs] [issue12350] Improve stat_result.st_blocks and
	st_blksize	documentation
In-Reply-To: <1308256127.22.0.581997138097.issue12350@psf.upfronthosting.co.za>
Message-ID: <3ct8vl6gp0zShd@mail.python.org>


Roundup Robot added the comment:

New changeset ef5aa8d7e932 by Georg Brandl in branch '3.3':
Closes #12350: clarify blocks/block size members of stat result.
http://hg.python.org/cpython/rev/ef5aa8d7e932

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

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

From report at bugs.python.org  Sun Oct  6 18:11:39 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:11:39 +0000
Subject: [docs] [issue12350] Improve stat_result.st_blocks and
	st_blksize	documentation
In-Reply-To: <1308256127.22.0.581997138097.issue12350@psf.upfronthosting.co.za>
Message-ID: <3ct8vv0mMxz7Lkf@mail.python.org>


Roundup Robot added the comment:

New changeset c32657e278f6 by Georg Brandl in branch '2.7':
Closes #12350: clarify blocks/block size members of stat result.
http://hg.python.org/cpython/rev/c32657e278f6

----------

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

From report at bugs.python.org  Sun Oct  6 18:17:34 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:17:34 +0000
Subject: [docs] [issue19181] ftp.cwi.nl used as example does not exist
	anymore
In-Reply-To: <525149A2.2010402@python.org>
Message-ID: <3ct92k0kmXz7Ljd@mail.python.org>


Roundup Robot added the comment:

New changeset d41aab121366 by Georg Brandl in branch '3.3':
Closes #19181: replace non-existing host ftp.cwi.nl with ftp.debian.org in ftplib example.
http://hg.python.org/cpython/rev/d41aab121366

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

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

From report at bugs.python.org  Sun Oct  6 18:17:42 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:17:42 +0000
Subject: [docs] [issue19181] ftp.cwi.nl used as example does not exist
	anymore
In-Reply-To: <525149A2.2010402@python.org>
Message-ID: <3ct92t27Rbz7Lkf@mail.python.org>


Roundup Robot added the comment:

New changeset 635e6239aa8e by Georg Brandl in branch '2.7':
Closes #19181: replace non-existing host ftp.cwi.nl with ftp.debian.org in ftplib example.
http://hg.python.org/cpython/rev/635e6239aa8e

----------

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

From georg at python.org  Sun Oct  6 18:27:30 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 18:27:30 +0200
Subject: [docs] hashlib - Missing FAQ section for hash collisions
In-Reply-To: <268B6C97-096A-4251-9B57-FF25401A4DF8@gmail.com>
References: <268B6C97-096A-4251-9B57-FF25401A4DF8@gmail.com>
Message-ID: <52518F72.2010008@python.org>

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

Am 01.05.2013 03:11, schrieb Christina Meono:
> Hello Python.org <http://Python.org>:
> 
> I was reading the docs for hashlib and there is a reference to algorithm 
> hash collisions, which the document specified would be addressed in an FAQ
> at the end of the doc, but said FAQ section cannot be found. Check it out
> here:
> 
> http://docs.python.org/2/library/hashlib.html
> 
> Please let me know if you have any questions.

Hi Christina,

thanks for the report. The FAQ was in fact a link in the "See also" section
which has since been changed to a Wikipedia link.  I've fixed this reference
now and it should be online soon.

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

iEYEARECAAYFAlJRj3IACgkQN9GcIYhpnLCgxwCeOqR2y1c+V6hVCxpggEU9Vaua
7UMAmgMR6TzQEOkqK2sz4kkKZiUcG8Fq
=NKoA
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct  6 18:36:47 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:36:47 +0000
Subject: [docs] [issue17725] English mistake in Extending and Embedding
	Python doc	page.
In-Reply-To: <1365923367.93.0.414383739407.issue17725@psf.upfronthosting.co.za>
Message-ID: <3ct9St5xrNzLr2@mail.python.org>


Roundup Robot added the comment:

New changeset 8ce8eae6abfa by Georg Brandl in branch '3.3':
Closes #17725: small grammar fix.
http://hg.python.org/cpython/rev/8ce8eae6abfa

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

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

From report at bugs.python.org  Sun Oct  6 18:37:21 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:37:21 +0000
Subject: [docs] [issue17725] English mistake in Extending and Embedding
	Python doc	page.
In-Reply-To: <1365923367.93.0.414383739407.issue17725@psf.upfronthosting.co.za>
Message-ID: <3ct9TX650qzQLd@mail.python.org>


Roundup Robot added the comment:

New changeset 27f1a3b0b340 by Georg Brandl in branch '2.7':
Closes #17725: small grammar fix.
http://hg.python.org/cpython/rev/27f1a3b0b340

----------

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

From report at bugs.python.org  Sun Oct  6 18:46:52 2013
From: report at bugs.python.org (Ned Batchelder)
Date: Sun, 06 Oct 2013 16:46:52 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
Message-ID: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>


New submission from Ned Batchelder:

The order of values on the stack is backwards for RAISE_VARARGS.  The docs say:

"Raises an exception. argc indicates the number of parameters to the raise statement, ranging from 0 to 3. The handler will find the traceback as TOS2, the parameter as TOS1, and the exception as TOS."

But in fact, the order is reverse of that.  In the one-parameter case, the exception is TOS, in the two-parameter case, the value is TOS, and in the three-parameter case, the traceback is TOS.  Not sure how to write that concisely, thought.  :)

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 199096
nosy: docs at python, nedbat
priority: normal
severity: normal
status: open
title: dis module has incorrect docs for RAISE_VARARGS
versions: Python 2.7, Python 3.4

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

From report at bugs.python.org  Sun Oct  6 18:47:51 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:47:51 +0000
Subject: [docs] [issue15213] _PyOS_URandom documentation
In-Reply-To: <1340845023.83.0.143337072725.issue15213@psf.upfronthosting.co.za>
Message-ID: <3ct9jg0nqQzQsm@mail.python.org>


Roundup Robot added the comment:

New changeset 3e5078c3784e by Georg Brandl in branch '2.7':
Closes #15213: update comment for _PyOS_URandom
http://hg.python.org/cpython/rev/3e5078c3784e

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

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

From report at bugs.python.org  Sun Oct  6 18:56:21 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:56:21 +0000
Subject: [docs] [issue11807] Documentation of add_subparsers lacks
	information about	parametres
In-Reply-To: <1302340872.99.0.0231583237732.issue11807@psf.upfronthosting.co.za>
Message-ID: <3ct9vS3TLlz7LjQ@mail.python.org>


Roundup Robot added the comment:

New changeset b930b4e67c8a by Georg Brandl in branch '3.3':
Closes #11807: document argparse add_subparsers method better.
http://hg.python.org/cpython/rev/b930b4e67c8a

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

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

From report at bugs.python.org  Sun Oct  6 18:56:22 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:56:22 +0000
Subject: [docs] [issue15213] _PyOS_URandom documentation
In-Reply-To: <1340845023.83.0.143337072725.issue15213@psf.upfronthosting.co.za>
Message-ID: <3ct9vT1mBXz7Ljg@mail.python.org>


Roundup Robot added the comment:

New changeset 176bb5a98463 by Georg Brandl in branch '3.3':
Closes #15213: update comment for _PyOS_URandom
http://hg.python.org/cpython/rev/176bb5a98463

----------

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

From report at bugs.python.org  Sun Oct  6 18:56:28 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:56:28 +0000
Subject: [docs] [issue11807] Documentation of add_subparsers lacks
	information about	parametres
In-Reply-To: <1302340872.99.0.0231583237732.issue11807@psf.upfronthosting.co.za>
Message-ID: <3ct9vb2kNXz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset d5027e489c25 by Georg Brandl in branch '2.7':
Closes #11807: document argparse add_subparsers method better.
http://hg.python.org/cpython/rev/d5027e489c25

----------

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

From report at bugs.python.org  Sun Oct  6 18:57:21 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 16:57:21 +0000
Subject: [docs] [issue15228] os.utime() docs not clear on behavior on
	nonexistant	files
In-Reply-To: <1341086123.85.0.135321380132.issue15228@psf.upfronthosting.co.za>
Message-ID: <3ct9wd1LB6z7Ljp@mail.python.org>


Roundup Robot added the comment:

New changeset 62321359c35b by Georg Brandl in branch '3.3':
Closes #15228: remove reference to Unix "touch"; it is confusing since the path needs to exist for os.utime() to succeed
http://hg.python.org/cpython/rev/62321359c35b

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

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

From report at bugs.python.org  Sun Oct  6 19:01:18 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 17:01:18 +0000
Subject: [docs] [issue15432] gzip.py: mtime argument only since python 2.7
In-Reply-To: <1343035771.6.0.0683574772688.issue15432@psf.upfronthosting.co.za>
Message-ID: <3ctB194w68z7LjS@mail.python.org>


Roundup Robot added the comment:

New changeset 74ae6064d3e8 by Georg Brandl in branch '2.7':
Closes #15432: GzipFile mtime argument was added in 2.7.
http://hg.python.org/cpython/rev/74ae6064d3e8

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

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

From report at bugs.python.org  Sun Oct  6 19:01:30 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 17:01:30 +0000
Subject: [docs] [issue15432] gzip.py: mtime argument only since python 2.7
In-Reply-To: <1343035771.6.0.0683574772688.issue15432@psf.upfronthosting.co.za>
Message-ID: <3ctB1P2tMyz7Ljq@mail.python.org>


Roundup Robot added the comment:

New changeset ad19a9982b03 by Georg Brandl in branch '3.3':
Closes #15432: GzipFile mtime argument is new in 3.1.
http://hg.python.org/cpython/rev/ad19a9982b03

----------

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

From georg at python.org  Sun Oct  6 19:15:11 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 19:15:11 +0200
Subject: [docs] Typo in example code for operator.attrgetter
In-Reply-To: <513760A3.5020206@quantopian.com>
References: <513760A3.5020206@quantopian.com>
Message-ID: <52519A9F.4050009@python.org>

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

Am 06.03.2013 16:28, schrieb Jonathan Kamens:
> At http://docs.python.org/2/library/operator.html#operator.attrgetter, the 
> example code in one instance "resolve_att" where it should be
> "resolve_attr".
> 
> Regards,
> 
> Jonathan Kamens

Hi Jonathan,

thanks for the report; this is now fixed and will appear online soon.

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

iEUEARECAAYFAlJRmp8ACgkQN9GcIYhpnLDX5wCY9BgiRoBKFDC9TBnLB1ItrxfI
gwCfdCU08jhE/pLkoAwNch8yD5ko4do=
=DUnA
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 19:19:51 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 19:19:51 +0200
Subject: [docs] platform.win32_ver() returns more than (version, csd,
 ptype)
In-Reply-To: <513CD8D5.3030407@gmail.com>
References: <513CD8D5.3030407@gmail.com>
Message-ID: <52519BB7.6050604@python.org>

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

Am 10.03.2013 20:02, schrieb Andrew Berg:
> http://docs.python.org/3.3/library/platform.html#platform.win32_ver
> 
> The documentation explicitly states that platform.win32_ver() returns 
> (version, csd, ptype), but in fact, it returns (release, version, csd, 
> ptype).
> 
> On Windows 8 (Python 3.3 of course):
>>>> platform.win32_ver()
> ('post2008Server', '6.2.9200', '', 'Multiprocessor Free')

Hi Andrew,

thanks for the report; this is now fixed and should appear online soon.

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

iEYEARECAAYFAlJRm7cACgkQN9GcIYhpnLAqMgCff0/Jlp4rdKOocguuho8v8n5g
U0MAn2qbfBenq1j2r7j0XbA2lCQBxdK/
=LoF5
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 19:21:43 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 19:21:43 +0200
Subject: [docs] 2.7.3 documentation: "6.4.1. Importing * From a Package"
 sounds/ should be sound/
In-Reply-To: <513E53EB.6000805@castleamber.com>
References: <513E53EB.6000805@castleamber.com>
Message-ID: <52519C27.5070203@python.org>

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

Am 11.03.2013 23:00, schrieb John Bokma:
> http://docs.python.org/2/tutorial/modules.html
> 
> "the file sounds/effects/__init__.py "
> 
> ^ should be sound, not sounds.

Hi John,

thanks for the report; this is now fixed and should be online soon.

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

iEYEARECAAYFAlJRnCcACgkQN9GcIYhpnLBx3ACfXNaJcO8bmzZUHK0utlauskT5
SgMAniXTTBhnB0pu4SCGYyoGtztn9g4N
=6HVC
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 19:24:37 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 19:24:37 +0200
Subject: [docs] bug in ipaddress module documentation
In-Reply-To: <D4C870855482434484604001080C5C3604C0DB@SKYMB2.trustwave.com>
References: <D4C870855482434484604001080C5C3604C0DB@SKYMB2.trustwave.com>
Message-ID: <52519CD5.4020709@python.org>

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

Am 12.03.2013 22:15, schrieb Tom Kalt:
> There is a slight problem with the documentation for the ipaddress module 
> (http://docs.python.org/3.4/library/ipaddress.html).  In
> 
> section 21.28.2.3.1,  operators such as  <, <=, ==, !=  are called
> "logical operators."  They should be called "relational operators."
> 
> http://en.wikipedia.org/wiki/Relational_operator.  Alternatively, sometimes
> they are called "comparison operators."
> 
> 
> 
> By contrast, "logical operator" refers to and, or, xor, etc.
> 
> 
> 
> I hope this helps.

Hi Tom,

thanks for the report; this is now fixed and should appear online soon.

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

iEYEARECAAYFAlJRnNUACgkQN9GcIYhpnLC9HACeLrBzg4OADiFHYrNhahwShTV5
7fkAoJmKE16dd+u/8kEXWR5lkA3OGW5b
=VTFz
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 19:27:35 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 19:27:35 +0200
Subject: [docs] Trivial os.path documentation bug
In-Reply-To: <CAARaemcDMao6+Of5fJ8uDmq0e9HLe69U3fbUpVCcM5jPQVm1YA@mail.gmail.com>
References: <CAARaemcDMao6+Of5fJ8uDmq0e9HLe69U3fbUpVCcM5jPQVm1YA@mail.gmail.com>
Message-ID: <52519D87.107@python.org>

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

Am 15.03.2013 17:06, schrieb Neil Bushong:
> Tiny typo: in the Python 3.3 os.makedirs documentation at
> http://docs.python.org/3.3/library/os.html#os.makedirs, the sentence
> saying "If exist*s*_ok is False (the default), an OSError is raised..."
> refers to the keyword argument as "exists_ok" (with an "s"), while the
> other parts refer to the keyword parameter as "exist_ok" (without the
> "s").
> 
> Thanks for providing and maintaining all the excellent documentation.

Hi Neil,

thanks for the report; this is now fixed and will appear online soon.

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

iEYEARECAAYFAlJRnYcACgkQN9GcIYhpnLCuIACcCq9oEWCwjmwacTJw1KKLt3ip
YngAn2xHmTeSPQIK/MFv1tZvsYVbYuGC
=9k2v
-----END PGP SIGNATURE-----

From georg at python.org  Sun Oct  6 19:34:54 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 19:34:54 +0200
Subject: [docs] /3/library/argparse.html#module-argparse
In-Reply-To: <CAKiQ7fV4YDVKPfaiMeLx78BdmN+_aW-7eCs8+mmGPOhAHbx0Lg@mail.gmail.com>
References: <CAKiQ7fV4YDVKPfaiMeLx78BdmN+_aW-7eCs8+mmGPOhAHbx0Lg@mail.gmail.com>
Message-ID: <52519F3E.9010105@python.org>

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

Am 22.03.2013 17:03, schrieb Micheal Wells:
> An observation:
> 
> In example 16.4.1, a script named 'prog.py' is given, and the user is told
> that they may execute it from the command line like so:  $  prog.py
> 
> My issue with this, is that it doesn't mention that the script starts with
> a shebang or is made executable with chmod +x, and even then the command
> would be $ ./prog.py.
> 
> A minor gripe, but I think that too much is assumed of the reader.   For
> reference:
> 
> 
> 
> Assuming the Python code above is saved into a file called prog.py, it can
> be run at the command line and provides useful help messages:
> 
> $ prog.py -h

Hi Micheal,

thanks for the report; I've replaced the invocations by "$ python prog.py" which
should work on every platform.  The change will go live soon.

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

iEYEARECAAYFAlJRnz4ACgkQN9GcIYhpnLCS/QCdGOjCnbh4fsOHaB7xYVERhoQ+
7ZoAoKGUnuscumnuAXsSTa1F103kAo0E
=E1wH
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct  6 19:35:45 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 17:35:45 +0000
Subject: [docs] [issue14101] example function in tertools.count docstring
	is	misindented
In-Reply-To: <1330027633.46.0.670191761588.issue14101@psf.upfronthosting.co.za>
Message-ID: <1381080945.97.0.965701776005.issue14101@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
resolution:  -> duplicate
status: open -> closed
superseder:  -> Intendation issue in example code in itertools.count documentation

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

From report at bugs.python.org  Sun Oct  6 19:41:07 2013
From: report at bugs.python.org (Vinay Sajip)
Date: Sun, 06 Oct 2013 17:41:07 +0000
Subject: [docs] [issue18939] Venv docs regarding original python install
In-Reply-To: <1378418560.94.0.0370764034466.issue18939@psf.upfronthosting.co.za>
Message-ID: <1381081267.79.0.147128933399.issue18939@psf.upfronthosting.co.za>


Vinay Sajip added the comment:

Closing, as documentation has now been updated.

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

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

From report at bugs.python.org  Sun Oct  6 20:29:15 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 18:29:15 +0000
Subject: [docs] [issue10709] Misc/AIX-NOTES needs updating
In-Reply-To: <1292428256.05.0.89055748757.issue10709@psf.upfronthosting.co.za>
Message-ID: <1381084155.22.0.574809001581.issue10709@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Ping? :)

----------

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

From report at bugs.python.org  Sun Oct  6 20:45:38 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 18:45:38 +0000
Subject: [docs] [issue11585] Documentation 1.8 shows Python 2 example
In-Reply-To: <1300369208.25.0.790450898206.issue11585@psf.upfronthosting.co.za>
Message-ID: <1381085138.05.0.629564574638.issue11585@psf.upfronthosting.co.za>


Georg Brandl added the comment:

This has since been fixed already.

----------
nosy: +georg.brandl
resolution:  -> out of date
status: open -> closed

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

From report at bugs.python.org  Sun Oct  6 20:50:30 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 18:50:30 +0000
Subject: [docs] [issue11789] Extend upon metaclass/type class documentation,
	here: zope.interface and usage of instances of classes as base
	classes
In-Reply-To: <1302126921.15.0.0291977163306.issue11789@psf.upfronthosting.co.za>
Message-ID: <1381085430.9.0.862355458836.issue11789@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
resolution:  -> works for me
status: open -> closed

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

From report at bugs.python.org  Sun Oct  6 21:01:01 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 19:01:01 +0000
Subject: [docs] [issue12162] Documentation about re \number
In-Reply-To: <1306195657.59.0.977782679394.issue12162@psf.upfronthosting.co.za>
Message-ID: <1381086061.53.0.303951530926.issue12162@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I can't see the issue here.  The RE docs are much better off with the regexes unquoted.

The '(.+) \1' example was fixed today (the string supposed to not match actually did match).

----------
nosy: +georg.brandl
resolution:  -> works for me
status: open -> closed

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

From report at bugs.python.org  Sun Oct  6 21:21:22 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 06 Oct 2013 19:21:22 +0000
Subject: [docs] [issue1215] documentation doesn't say that you can't handle
	C	segfaults from python
In-Reply-To: <1190912724.9.0.418130471784.issue1215@psf.upfronthosting.co.za>
Message-ID: <1381087281.96.0.156075450441.issue1215@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I see not much to be done here, except from committing Martin's patch updated to the current trunk.

----------

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

From report at bugs.python.org  Sun Oct  6 21:22:43 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 06 Oct 2013 19:22:43 +0000
Subject: [docs] [issue1215] documentation doesn't say that you can't handle
	C	segfaults from python
In-Reply-To: <1190912724.9.0.418130471784.issue1215@psf.upfronthosting.co.za>
Message-ID: <3ctF8L2rb3z7LjP@mail.python.org>


Roundup Robot added the comment:

New changeset b4444d16e333 by Georg Brandl in branch '3.3':
Closes #1215: document better why it is not a good idea to catch e.g. SIGSEGV and refer to faulthandler.
http://hg.python.org/cpython/rev/b4444d16e333

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

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

From report at bugs.python.org  Mon Oct  7 04:34:56 2013
From: report at bugs.python.org (Chris Rebert)
Date: Mon, 07 Oct 2013 02:34:56 +0000
Subject: [docs] [issue17359] Mention "__main__.py" explicitly in command
	line docs
In-Reply-To: <1362512425.64.0.937549165034.issue17359@psf.upfronthosting.co.za>
Message-ID: <1381113296.48.0.661705556009.issue17359@psf.upfronthosting.co.za>


Changes by Chris Rebert <pybugs at rebertia.com>:


----------
nosy: +cvrebert

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

From report at bugs.python.org  Mon Oct  7 19:49:54 2013
From: report at bugs.python.org (Eric Snow)
Date: Mon, 07 Oct 2013 17:49:54 +0000
Subject: [docs] [issue19178] Entries for "module" and "package" in glossary
In-Reply-To: <1381048973.81.0.279739415702.issue19178@psf.upfronthosting.co.za>
Message-ID: <1381168194.39.0.854909175553.issue19178@psf.upfronthosting.co.za>


Eric Snow added the comment:

They are defined in the Python 3 glossary [1], so I expect it just a matter of backporting those entries.

[1] http://docs.python.org/3/glossary.html

----------
nosy: +eric.snow
versions:  -Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Oct  7 20:41:43 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2013 18:41:43 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381171303.22.0.488303225413.issue18758@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Yes. I have 180 Kb patch which touches 107 files, and this is yet too large for one issue. I will continue split this patch for lesser issues.

----------

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

From report at bugs.python.org  Mon Oct  7 22:13:31 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 07 Oct 2013 20:13:31 +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: <1381176811.46.0.758787673744.issue19154@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

We are both talking about 2.7 httplib.HTTPResponse.fileno. I should have said that users should try: ...fileno(); except AttributeError rather than ValueError. Any caller can understand AttributeError as well as ValueError or any other exception.

It is not an error for a python function to raise an exception. In fact, it is the normal thing to do when it cannot do as requested. API changes are not allowed in 2.7 and this one would be dubious even in a future 3.x.

I do think the doc should be more informative and that

Return(s) the fileno of the underlying socket.

should be extended to indicate the specific exception raised when that is not possible.

Return the fileno of the underlying socket if there is one or raise AttributeError.

This should also be added as a docstring (currently missing).

The above is also true for 3.x as self.fp continues to be replaced with None on closing.

The HTTPResponse docs are known to be deficient. #3430

--
I do not think select needs to be changed to understand the HTTPResponse.fileno error indicator because it does not call that method. As indicated in the traceback, it calls (in 2.7) socket._fileinput.fileno. I believe it is only a bug in nappstore (that would be harder to reproduce in 3.x) that _fileinput.fileno is forwarded to HTTPResponse.fileno instead of _socket.fileno. The latter seem to be the clear intention. Even if I am wrong, changing something in the select or socket modules would be a different issue from changing something in the client module.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
keywords: +easy, patch
nosy: +docs at python
stage: test needed -> needs patch
type: behavior -> enhancement
versions: +Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Oct  7 22:39:14 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2013 20:39:14 +0000
Subject: [docs] [issue19189] Improve cross-references in pickle
	documentation.
Message-ID: <1381178353.55.0.131251765353.issue19189@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the documentation of the pickle package.

----------
assignee: docs at python
components: Documentation
files: refs.pickle.patch
keywords: patch
messages: 199162
nosy: alexandre.vassalotti, docs at python, pitrou, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in pickle documentation.
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31988/refs.pickle.patch

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

From report at bugs.python.org  Mon Oct  7 22:40:09 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2013 20:40:09 +0000
Subject: [docs] [issue19190] Improve cross-references in builtins
	documentation.
Message-ID: <1381178406.23.0.925502914141.issue19190@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references for in the documentation of builtins.

----------
assignee: docs at python
components: Documentation
files: refs.builtins.patch
keywords: patch
messages: 199163
nosy: docs at python, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in builtins documentation.
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file31989/refs.builtins.patch

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

From report at bugs.python.org  Mon Oct  7 23:20:07 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2013 21:20:07 +0000
Subject: [docs] [issue19190] Improve cross-references in builtins
	documentation.
In-Reply-To: <1381178406.23.0.925502914141.issue19190@psf.upfronthosting.co.za>
Message-ID: <1381180807.45.0.439217534401.issue19190@psf.upfronthosting.co.za>


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


Removed file: http://bugs.python.org/file31989/refs.builtins.patch

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

From report at bugs.python.org  Mon Oct  7 23:22:14 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 07 Oct 2013 21:22:14 +0000
Subject: [docs] [issue19190] Improve cross-references in builtins
	documentation.
In-Reply-To: <1381178406.23.0.925502914141.issue19190@psf.upfronthosting.co.za>
Message-ID: <1381180934.17.0.0182873608641.issue19190@psf.upfronthosting.co.za>


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


Added file: http://bugs.python.org/file31990/refs.builtins.patch

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

From report at bugs.python.org  Tue Oct  8 06:13:16 2013
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 08 Oct 2013 04:13:16 +0000
Subject: [docs] [issue19178] Entries for "module" and "package" in glossary
In-Reply-To: <1381048973.81.0.279739415702.issue19178@psf.upfronthosting.co.za>
Message-ID: <1381205596.02.0.408204147026.issue19178@psf.upfronthosting.co.za>


Berker Peksag added the comment:

For 3.x, I've added cross references between module and package entries.

For 2.7, I've backported importing, module and package entries.

----------
keywords: +patch
nosy: +berker.peksag
stage: needs patch -> patch review
Added file: http://bugs.python.org/file31994/issue19178_py3.diff

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

From report at bugs.python.org  Tue Oct  8 06:13:27 2013
From: report at bugs.python.org (Berker Peksag)
Date: Tue, 08 Oct 2013 04:13:27 +0000
Subject: [docs] [issue19178] Entries for "module" and "package" in glossary
In-Reply-To: <1381048973.81.0.279739415702.issue19178@psf.upfronthosting.co.za>
Message-ID: <1381205607.33.0.650256291393.issue19178@psf.upfronthosting.co.za>


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


Added file: http://bugs.python.org/file31995/issue19178_py2.diff

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

From report at bugs.python.org  Tue Oct  8 07:41:02 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 05:41:02 +0000
Subject: [docs] [issue19190] Improve cross-references in builtins
	documentation.
In-Reply-To: <1381178406.23.0.925502914141.issue19190@psf.upfronthosting.co.za>
Message-ID: <1381210862.25.0.599040586388.issue19190@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Why the need for these changes -- the references I checked are working fine as is.

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

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

From report at bugs.python.org  Tue Oct  8 07:43:31 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 05:43:31 +0000
Subject: [docs] [issue19178] Entries for "module" and "package" in glossary
In-Reply-To: <1381048973.81.0.279739415702.issue19178@psf.upfronthosting.co.za>
Message-ID: <1381211011.13.0.937451292978.issue19178@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Looks good to me.

----------

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

From report at bugs.python.org  Tue Oct  8 08:05:44 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 08 Oct 2013 06:05:44 +0000
Subject: [docs] [issue19178] Entries for "module" and "package" in glossary
In-Reply-To: <1381048973.81.0.279739415702.issue19178@psf.upfronthosting.co.za>
Message-ID: <3cv7Mq15t7z7LkY@mail.python.org>


Roundup Robot added the comment:

New changeset 5e1f359d54c4 by Georg Brandl in branch '2.7':
Closes #19178: backport entries for "module" and "package" from 3.x glossary. Patch by Berker Peksag.
http://hg.python.org/cpython/rev/5e1f359d54c4

New changeset b6205505e1e4 by Georg Brandl in branch '3.3':
Closes #19178: some more cross-references about packages in glossary. Patch by Berker Peksag.
http://hg.python.org/cpython/rev/b6205505e1e4

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

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

From report at bugs.python.org  Tue Oct  8 10:55:56 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 08:55:56 +0000
Subject: [docs] [issue19190] Improve cross-references in builtins
	documentation.
In-Reply-To: <1381178406.23.0.925502914141.issue19190@psf.upfronthosting.co.za>
Message-ID: <1381222554.91.0.829440390929.issue19190@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Indeed, there are false changes. Thank you Georg.

Here is cleaned patch.

----------
Added file: http://bugs.python.org/file31998/refs.builtins_2.patch

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

From report at bugs.python.org  Tue Oct  8 14:30:42 2013
From: report at bugs.python.org (Florent Viard)
Date: Tue, 08 Oct 2013 12:30:42 +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: <1381235442.84.0.712463429466.issue19154@psf.upfronthosting.co.za>


Florent Viard added the comment:

Thank you for your reply.
But I just realised that in my bug issue, I completely forgot to indicate what is "req" and so this is maybe the root of you telling me that the best is to fix the client code side as the traceback could be confusing.

This is how is defined req.:
opener = urllib2.build_opener(proxy_handler)
req    = urllib2.Request(url_src)

then:
while 1:
  read_list = select([req], ...)[0]
  if read_list:
    req.read(CHUNK_SIZE)


I found this issue with python 2.7, but I don't care a lot for it to be fixed in 2.7. As I saw that the code looks unchanged in python 3.x, I just reported the issue for it to be fixed/better handled in 3.x :-)

----------

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

From report at bugs.python.org  Tue Oct  8 15:09:22 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Tue, 08 Oct 2013 13:09:22 +0000
Subject: [docs] [issue15964] SyntaxError in asdl when building 2.7 with
	system Python	3
In-Reply-To: <1347978379.29.0.810502621141.issue15964@psf.upfronthosting.co.za>
Message-ID: <1381237762.25.0.878557426541.issue15964@psf.upfronthosting.co.za>


Changes by Eli Bendersky <eliben at gmail.com>:


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

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

From report at bugs.python.org  Tue Oct  8 15:12:19 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Tue, 08 Oct 2013 13:12:19 +0000
Subject: [docs] [issue14332] Better explain "junk" concept in difflib doc
In-Reply-To: <1331877125.66.0.103153393744.issue14332@psf.upfronthosting.co.za>
Message-ID: <1381237939.77.0.692368678531.issue14332@psf.upfronthosting.co.za>


Eli Bendersky added the comment:

Tim, any suggestions?

----------

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

From report at bugs.python.org  Tue Oct  8 17:51:59 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 08 Oct 2013 15:51:59 +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: <1381247519.78.0.433848459234.issue19154@psf.upfronthosting.co.za>


R. David Murray added the comment:

It seems to me that there is indeed an issue of some sort here, but its locus is (to me) unclear.  I haven't commented before this because I wanted to read the docs...but I haven't had time yet :)  

One question is, is it even expected that passing a Request to select will work?  If it *is* expected, then what is the API that req should be conforming to?  This API may be an implicit one that is not documented, or perhaps it is documented in select (I haven't checked).  If req is conforming to the explicit or implicit API, then the bug would be in select.  Otherwise it is in httplib.

Or, if this isn't something we've been supporting in the past, then as Terry says it is a new feature.

----------

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

From report at bugs.python.org  Tue Oct  8 17:53:30 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 08 Oct 2013 15:53:30 +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: <1381247610.09.0.533783926752.issue19154@psf.upfronthosting.co.za>


R. David Murray added the comment:

s/httplib/urllib/

----------

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

From report at bugs.python.org  Tue Oct  8 19:17:34 2013
From: report at bugs.python.org (Florent Viard)
Date: Tue, 08 Oct 2013 17:17:34 +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: <1381252654.03.0.541006704777.issue19154@psf.upfronthosting.co.za>


Florent Viard added the comment:

R. David, what you say is correct, supporting "select" that would be nice but i'm also not sure that is supposed to, and in that case, maybe select as to be fixed for that.

But:
a) As urllib2 through httplib provide publicly a fileno, i was excepting so.
b) The real point of my issue is that i noticed that there is 3 different return values, for the similar fileno function in 3 different modules of python, when the file descriptor is closed or inexistant:
- in urllib2->httplib: AttributeError as "None" as no "fileno()" attribute.
- in socket : ValueError
- in fileinput: -1

And for the 2 firsts, one is finally using the fileno function of the other.

----------

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

From report at bugs.python.org  Tue Oct  8 19:28:42 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 17:28:42 +0000
Subject: [docs] [issue13436] compile() doesn't work on ImportFrom with
	level=None
In-Reply-To: <1321747479.31.0.688458511993.issue13436@psf.upfronthosting.co.za>
Message-ID: <1381253321.99.0.655263110637.issue13436@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
Removed message: http://bugs.python.org/msg148146

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

From report at bugs.python.org  Tue Oct  8 20:00:45 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 18:00:45 +0000
Subject: [docs] [issue14224] packaging: path description of resources is
	mixed up
In-Reply-To: <1331157234.71.0.528832694178.issue14224@psf.upfronthosting.co.za>
Message-ID: <1381255245.63.0.630235693768.issue14224@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Doc/packaging has been removed.

----------
nosy: +georg.brandl
resolution:  -> out of date
status: open -> closed

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

From report at bugs.python.org  Tue Oct  8 20:12:50 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 18:12:50 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381255970.94.0.039372880584.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Improve cross-references in builtins documentation., Improve cross-references in pickle documentation.

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

From report at bugs.python.org  Tue Oct  8 20:16:58 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 18:16:58 +0000
Subject: [docs] [issue19193] Improve cross-references in tutorial
Message-ID: <1381256218.12.0.311002758548.issue19193@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the tutorial.

----------
assignee: docs at python
components: Documentation
files: refs.tutorial.patch
keywords: patch
messages: 199228
nosy: docs at python, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in tutorial
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32001/refs.tutorial.patch

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

From report at bugs.python.org  Tue Oct  8 20:18:41 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 18:18:41 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381256321.54.0.250496062545.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Improve cross-references in tutorial

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

From report at bugs.python.org  Tue Oct  8 20:26:55 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 08 Oct 2013 18:26:55 +0000
Subject: [docs] [issue13867] misleading comment in weakrefobject.h
In-Reply-To: <1327532476.25.0.872465463087.issue13867@psf.upfronthosting.co.za>
Message-ID: <3cvRq16qswz7Ljh@mail.python.org>


Roundup Robot added the comment:

New changeset 1800107873c0 by Georg Brandl in branch 'default':
Closes #13867: remove untrue comment about PyWeakref_Check().
http://hg.python.org/cpython/rev/1800107873c0

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

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

From report at bugs.python.org  Tue Oct  8 20:32:08 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 08 Oct 2013 18:32:08 +0000
Subject: [docs] [issue13867] misleading comment in weakrefobject.h
In-Reply-To: <1327532476.25.0.872465463087.issue13867@psf.upfronthosting.co.za>
Message-ID: <3cvRx32tWfz7LjM@mail.python.org>


Roundup Robot added the comment:

New changeset 1cd2fca12abf by Georg Brandl in branch '3.3':
Closes #13867: remove untrue comment about PyWeakref_Check().
http://hg.python.org/cpython/rev/1cd2fca12abf

----------

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

From report at bugs.python.org  Tue Oct  8 20:33:01 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 08 Oct 2013 18:33:01 +0000
Subject: [docs] [issue13867] misleading comment in weakrefobject.h
In-Reply-To: <1327532476.25.0.872465463087.issue13867@psf.upfronthosting.co.za>
Message-ID: <3cvRy45LHxzSyK@mail.python.org>


Roundup Robot added the comment:

New changeset 39e5ab118602 by Georg Brandl in branch '2.7':
Closes #13867: remove untrue comment about PyWeakref_Check().
http://hg.python.org/cpython/rev/39e5ab118602

----------

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

From report at bugs.python.org  Tue Oct  8 20:34:48 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 18:34:48 +0000
Subject: [docs] [issue15264] PyErr_SetFromErrnoWithFilenameObject()
	undocumented
In-Reply-To: <1341592840.74.0.991788798601.issue15264@psf.upfronthosting.co.za>
Message-ID: <1381257288.74.0.399945328592.issue15264@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Has been documented meanwhile.

----------
nosy: +georg.brandl
resolution:  -> out of date
status: open -> closed

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

From report at bugs.python.org  Tue Oct  8 20:42:19 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 18:42:19 +0000
Subject: [docs] [issue15455] index entries not showing up in glossary
In-Reply-To: <1343292936.36.0.839564467916.issue15455@psf.upfronthosting.co.za>
Message-ID: <1381257739.46.0.925874057685.issue15455@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
resolution:  -> invalid
status: open -> closed

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

From report at bugs.python.org  Tue Oct  8 20:46:39 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 18:46:39 +0000
Subject: [docs] [issue15863] Fine-grained info about Python versions which
	support	changes introduced in micro releases
In-Reply-To: <1346798659.62.0.336544157965.issue15863@psf.upfronthosting.co.za>
Message-ID: <1381257999.69.0.177549828237.issue15863@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I don't think this is necessary.

----------
nosy: +georg.brandl
resolution:  -> works for me
status: open -> closed

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

From report at bugs.python.org  Tue Oct  8 20:58:49 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 18:58:49 +0000
Subject: [docs] [issue11009] urllib.splituser is not documented
In-Reply-To: <1295987078.02.0.421774194417.issue11009@psf.upfronthosting.co.za>
Message-ID: <1381258729.82.0.973761505685.issue11009@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
status: open -> closed

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

From georg at python.org  Tue Oct  8 21:29:04 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 21:29:04 +0200
Subject: [docs] The delimiter '->' is missing in section 2.6
	documentation
In-Reply-To: <D88D6CBD04B9E647B778917814A70F9A923EDC10@USSLMMBX003.net.plm.eds.com>
References: <D88D6CBD04B9E647B778917814A70F9A923EDC10@USSLMMBX003.net.plm.eds.com>
Message-ID: <52545D00.4020600@python.org>

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

Am 16.01.2013 21:11, schrieb Harding, James:
> Hello,
> 
> 
> 
> A minor quibble. I do not see the token ?->? used with function
> annotations listed among the delimiters in section 2.6 of the reference
> manual for Python v3.3.0.

Hi James,

thanks for the report; this is now fixed and will be live soon.

cheers,
Georg

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)

iEYEARECAAYFAlJUXQAACgkQN9GcIYhpnLCXWwCbB9oK6LBvlV4s6ETWlsb1o0Wh
DykAoIwhaYUE5BhB6t00NqSzZ6ICY3+x
=oChv
-----END PGP SIGNATURE-----

From georg at python.org  Tue Oct  8 21:44:19 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 21:44:19 +0200
Subject: [docs] Invalid link in "SystemExit" documentation (2.x,
 Section 6)
In-Reply-To: <345A300EFDE6A344AD4F35DBC5E1AC8BE7C9A90A99@03S08EXMB01.zebra.lan>
References: <345A300EFDE6A344AD4F35DBC5E1AC8BE7C9A90A99@03S08EXMB01.zebra.lan>
Message-ID: <52546093.2030409@python.org>

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

Am 27.02.2013 16:04, schrieb Bock, Harry:
> Hi,
> 
> 
> 
> I stumbled upon a bug in the ?SystemExit? exception documentation for
> Python 2.x:
> 
> http://docs.python.org/2/library/exceptions.html#exceptions.SystemExit
> 
> 
> 
> The line ?Instances have an attribute *code*? has a reference to the ?code?
> module:
> 
> http://docs.python.org/2/library/code.html#module-code
> 
> 
> 
> Which is not what the SystemExit attribute is referring to.  The
> cross-reference should be removed, and no other change is needed. The
> documentation explains the attribute well.
> 
> 
> Thanks for the great documentation!  Keep up the great work.

Hi Harry,

thanks for the report; this is now fixed and will appear online soon.

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

iEYEARECAAYFAlJUYJMACgkQN9GcIYhpnLD3GACgjdEOQU38dEyYJACQRFLRxYMM
Tp8AoKdLmUcfl8dhRYdH6VIPaSWyaPuY
=k8XA
-----END PGP SIGNATURE-----

From georg at python.org  Tue Oct  8 21:47:53 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 21:47:53 +0200
Subject: [docs] Bugs in Python3 division and right-shift docs
In-Reply-To: <CAEyAk53bDXqgwiSLec63BQotz_9mazu67uVAxCe3su8eigSKpg@mail.gmail.com>
References: <CAEyAk53bDXqgwiSLec63BQotz_9mazu67uVAxCe3su8eigSKpg@mail.gmail.com>
Message-ID: <52546169.1000007@python.org>

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

Am 27.02.2013 21:30, schrieb Albert Hofkamp:
> While reporting a doc bug in the right-shift operator, I found another one
> in the division description. I combined them both below.
> 
> 
> http://docs.python.org/3/reference/expressions.html?highlight=shift#binary-arithmetic-operations
>
> 
A quote:
> " ... The / (division) and // (floor division) operators yield the quotient
> of their arguments. The numeric arguments are first converted to a common
> type. Integer division yields a float, while floor division of integers
> results in an integer; ..."
> 
> The term "Integer division" does not get defined here.  Perhaps "Division
> of integers yields ..." would be better?
> 
> 
> 
> 
> http://docs.python.org/3/reference/expressions.html?highlight=shift#shifting-operations
>
> 
A quote from 6.7 (Shifting operations) of the python 3 language reference:
> 
> "...These operators accept integers as arguments. They shift the first 
> argument to the left or right by the number of bits given by the second
> argument. A right shift by n bits is defined as division by pow(2,n). A
> left shift by n bits is defined as multiplication with pow(2,n). ..."
> 
> By the latter sentence, I can interpret 2 >> 5 as 2 / pow(2, 5), which is
> 0.0625. On the other hand, 2 >> 5 is 0 according to Python 3.3 . Perhaps it
> should say "floor division" in the explanation above?

Hi Albert,

thanks for the suggestions; they are now incorporated and will appear online soon.

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

iEYEARECAAYFAlJUYWkACgkQN9GcIYhpnLCUIgCfYrbCI+vObbGEORuxrp/4pX0L
LcIAoK76JLT+lOXHVydTBul6heKUcMv3
=xNMa
-----END PGP SIGNATURE-----

From report at bugs.python.org  Tue Oct  8 21:50:40 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 19:50:40 +0000
Subject: [docs] [issue19194] Improve cross-references in fcntl documentation
Message-ID: <1381261840.65.0.334313272339.issue19194@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the documentation of the fcntl package.

----------
assignee: docs at python
components: Documentation
files: refs.fcntl.patch
keywords: patch
messages: 199242
nosy: docs at python, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in fcntl documentation
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32002/refs.fcntl.patch

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

From report at bugs.python.org  Tue Oct  8 21:51:23 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 19:51:23 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381261883.54.0.443836679915.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Improve cross-references in fcntl documentation

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

From georg at python.org  Tue Oct  8 21:55:12 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 21:55:12 +0200
Subject: [docs] typo in http://docs.python.org/2/howto/argparse.html
In-Reply-To: <CAOo6sOOaXyyw9b0vrM5DjPjjF3RYN8xM8sFOm_5uoEEfT7k47Q@mail.gmail.com>
References: <CAOo6sOOaXyyw9b0vrM5DjPjjF3RYN8xM8sFOm_5uoEEfT7k47Q@mail.gmail.com>
Message-ID: <52546320.9060903@python.org>

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

Am 16.05.2013 19:04, schrieb Jason Sachs:
> minor grammatical typo:
> 
> ?how it works simply by reading it?s help text?: ?it?s? should be ?its?

Hi Jason,

thanks for the report; this is now fixed and will appear online soon.

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

iEYEARECAAYFAlJUYyAACgkQN9GcIYhpnLCcXACfYk8OEdhgw3yBcbXyQHr6Dnf6
jHIAn3CfrvQXQiblu12rzWdMgKmcyPaf
=iVuu
-----END PGP SIGNATURE-----

From report at bugs.python.org  Tue Oct  8 21:56:32 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 19:56:32 +0000
Subject: [docs] [issue19195] Improve cross-references in C API
Message-ID: <1381262191.72.0.573497194321.issue19195@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in C API and extension documentation.

----------
assignee: docs at python
components: Documentation
files: refs.c-api.patch
keywords: patch
messages: 199243
nosy: docs at python, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in C API
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32003/refs.c-api.patch

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

From report at bugs.python.org  Tue Oct  8 21:57:00 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 19:57:00 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381262220.1.0.0551108717507.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Improve cross-references in C API

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

From report at bugs.python.org  Tue Oct  8 22:00:00 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 20:00:00 +0000
Subject: [docs] [issue19196] Improve cross-references in pickle documentation
Message-ID: <1381262400.58.0.379802599514.issue19196@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in distutils  documentation.

----------
assignee: docs at python
components: Documentation
files: refs.distutils.patch
keywords: patch
messages: 199244
nosy: docs at python, eric.araujo, serhiy.storchaka, tarek
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in pickle documentation
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32004/refs.distutils.patch

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

From report at bugs.python.org  Tue Oct  8 22:00:24 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 20:00:24 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381262424.12.0.508945844202.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Improve cross-references in pickle documentation

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

From georg at python.org  Tue Oct  8 22:19:35 2013
From: georg at python.org (georg at python.org)
Date: Tue, 08 Oct 2013 20:19:35 -0000
Subject: [docs] Improve cross-references in fcntl documentation (issue 19194)
Message-ID: <20131008201935.24133.12477@psf.upfronthosting.co.za>


http://bugs.python.org/review/19194/diff/9474/Doc/library/fcntl.rst
File Doc/library/fcntl.rst (right):

http://bugs.python.org/review/19194/diff/9474/Doc/library/fcntl.rst#newcode1
Doc/library/fcntl.rst:1: :mod:`fcntl` --- The :c:func:`fcntl` and
:c:func:`ioctl` system calls
these references should just be replaced by ``fcntl`` and ``ioctl``.

http://bugs.python.org/review/19194/diff/9474/Doc/library/fcntl.rst#newcode128
Doc/library/fcntl.rst:128: * :const:`0` -- relative to the start of the
file (:const:`os.SEEK_SET`)
:data: is the correct role for module-level constants.

http://bugs.python.org/review/19194/

From georg at python.org  Tue Oct  8 22:22:46 2013
From: georg at python.org (georg at python.org)
Date: Tue, 08 Oct 2013 20:22:46 -0000
Subject: [docs] Improve cross-references in C API (issue 19195)
Message-ID: <20131008202246.5252.11330@psf.upfronthosting.co.za>


http://bugs.python.org/review/19195/diff/9475/Doc/c-api/buffer.rst
File Doc/c-api/buffer.rst (right):

http://bugs.python.org/review/19195/diff/9475/Doc/c-api/buffer.rst#newcode47
Doc/c-api/buffer.rst:47: the buffer interface can be written to a file. 
While :meth:`~io.BufferedIOBase.write` only
just replace by ``write()``, two references in two sentences is not
needed

http://bugs.python.org/review/19195/diff/9475/Doc/c-api/typeobj.rst
File Doc/c-api/typeobj.rst (right):

http://bugs.python.org/review/19195/diff/9475/Doc/c-api/typeobj.rst#newcode643
Doc/c-api/typeobj.rst:643: When a type's :attr:`~object.__slots__`
declaration contains a slot named
here too: too many links are not needed and distract.

http://bugs.python.org/review/19195/

From report at bugs.python.org  Tue Oct  8 22:23:30 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 08 Oct 2013 20:23:30 +0000
Subject: [docs] [issue19196] Improve cross-references in distutils
	documentation
In-Reply-To: <1381262400.58.0.379802599514.issue19196@psf.upfronthosting.co.za>
Message-ID: <1381263810.9.0.321244806185.issue19196@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
title: Improve cross-references in pickle documentation -> Improve cross-references in distutils documentation

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

From report at bugs.python.org  Tue Oct  8 22:24:19 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 08 Oct 2013 20:24:19 +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: <1381263859.92.0.334299176977.issue19154@psf.upfronthosting.co.za>


R. David Murray added the comment:

OK, I've looked at the docs and code, and as far as I can see this bug does not exist in Python3.  Or at least in 3.4, which is the only place I'd feel safe about making a change to the exception type.

To summarize: in 3.4 socket logic is based on RawIOBase, as is HTTPResponse.  And RawIOBase checks to see if the file is closed and raises a ValueError if it is, when fileno is called on the 'fp' attribute of the HTTPResponse.  At least, that's what I think based on reading the code.

So, unless you can reproduce the error in 3.3 and/or 3.4, I think we should close this issue as out of date, since as Terry said there is a non-trivial danger of backward incompatibility if we were to change the exception type in 2.7.

----------

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

From georg at python.org  Tue Oct  8 22:25:09 2013
From: georg at python.org (georg at python.org)
Date: Tue, 08 Oct 2013 20:25:09 -0000
Subject: [docs] Improve cross-references in pickle documentation (issue
	19196)
Message-ID: <20131008202509.24133.31425@psf.upfronthosting.co.za>


http://bugs.python.org/review/19196/diff/9476/Doc/distutils/apiref.rst
File Doc/distutils/apiref.rst (right):

http://bugs.python.org/review/19196/diff/9476/Doc/distutils/apiref.rst#newcode997
Doc/distutils/apiref.rst:997: *preserve_mode* and *preserve_times* are
the same as for :func:`~distutils.file_util.copy_file` in
in this case, leave out the tilde and remove the "in :mod:`blah`".

http://bugs.python.org/review/19196/diff/9476/Doc/distutils/apiref.rst#newcode1002
Doc/distutils/apiref.rst:1002: as for
:func:`~distutils.file_util.copy_file`.
unneeded.

http://bugs.python.org/review/19196/diff/9476/Doc/distutils/extending.rst
File Doc/distutils/extending.rst (right):

http://bugs.python.org/review/19196/diff/9476/Doc/distutils/extending.rst#newcode20
Doc/distutils/extending.rst:20: :class:`~distutils.cmd.Command`, while
replacements often derive from :class:`~distutils.cmd.Command`
second and third one unneeded.

http://bugs.python.org/review/19196/diff/9476/Doc/distutils/setupscript.rst
File Doc/distutils/setupscript.rst (right):

http://bugs.python.org/review/19196/diff/9476/Doc/distutils/setupscript.rst#newcode149
Doc/distutils/setupscript.rst:149: The
:class:`~distutils.core.Extension` class can be imported from
:mod:`distutils.core` along
unneeded... etc.

http://bugs.python.org/review/19196/

From georg at python.org  Tue Oct  8 22:26:16 2013
From: georg at python.org (georg at python.org)
Date: Tue, 08 Oct 2013 20:26:16 -0000
Subject: [docs] Improve cross-references in tutorial (issue 19193)
Message-ID: <20131008202616.24134.96427@psf.upfronthosting.co.za>

Looks good.

http://bugs.python.org/review/19193/

From georg at python.org  Tue Oct  8 22:31:08 2013
From: georg at python.org (georg at python.org)
Date: Tue, 08 Oct 2013 20:31:08 -0000
Subject: [docs] Improve cross-references in builtins documentation. (issue
	19190)
Message-ID: <20131008203108.24133.22695@psf.upfronthosting.co.za>


http://bugs.python.org/review/19190/diff/9471/Doc/glossary.rst
File Doc/glossary.rst (right):

http://bugs.python.org/review/19190/diff/9471/Doc/glossary.rst#newcode419
Doc/glossary.rst:419: :meth:`~iterator.__next__` method just raise
:exc:`StopIteration` again.
unneeded

http://bugs.python.org/review/19190/diff/9471/Doc/library/functions.rst
File Doc/library/functions.rst (right):

http://bugs.python.org/review/19190/diff/9471/Doc/library/functions.rst#newcode545
Doc/library/functions.rst:545: 
unrelated change

http://bugs.python.org/review/19190/diff/9471/Doc/library/functions.rst#newcode1406
Doc/library/functions.rst:1406: or any other object with a
:attr:`~object.__dict__` attribute.
unneeded, etc. below

http://bugs.python.org/review/19190/diff/9471/Doc/library/numbers.rst
File Doc/library/numbers.rst (right):

http://bugs.python.org/review/19190/diff/9471/Doc/library/numbers.rst#newcode160
Doc/library/numbers.rst:160: :meth:`__add__`.  (Or ``A`` may not
implement :meth:`__add__` at
unrelated change

http://bugs.python.org/review/19190/diff/9471/Doc/library/stdtypes.rst
File Doc/library/stdtypes.rst (right):

http://bugs.python.org/review/19190/diff/9471/Doc/library/stdtypes.rst#newcode343
Doc/library/stdtypes.rst:343: :mod:`math` module for well-defined
conversions.
leave out ~, remove "in the math module"

http://bugs.python.org/review/19190/diff/9471/Doc/library/stdtypes.rst#newcode637
Doc/library/stdtypes.rst:637: made available to Python as the
:attr:`~sys.hash_info.modulus` attribute of
leave out tilde, remove "of sys.hash_info"

http://bugs.python.org/review/19190/diff/9471/Doc/library/stdtypes.rst#newcode3361
Doc/library/stdtypes.rst:3361: :attr:`~object.__dict__` attribute is not
possible (you can write
unneeded

http://bugs.python.org/review/19190/diff/9471/Doc/reference/datamodel.rst
File Doc/reference/datamodel.rst (right):

http://bugs.python.org/review/19190/diff/9471/Doc/reference/datamodel.rst#newcode607
Doc/reference/datamodel.rst:607: body of the function:  calling the
iterator's :meth:`iterator.__next__`
good catch :)

http://bugs.python.org/review/19190/

From report at bugs.python.org  Tue Oct  8 22:36:40 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 08 Oct 2013 20:36:40 +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: <1381264600.51.0.72555353496.issue19154@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Florent, for future reference, marking an issue for 2.7 says to us "I  want this fixed for 2.7".

I agree that having 3 different error indicators for 3 similar functions is nasty. But this is partly due to the difference between object that *has* a fd (socket) versus a object that *wraps such an object. The problem is that changing any of them could break code that just uses one of them. 

The select doc says that a 'waitable' object must have .fileno() that return a valid fd int. It says nothing about an allowed error return. This could be interpreted as meaning that not returning an fd int makes the object (such as a closed HTTPResponse) unwaitable. Or this could be interpreted as a deficiency in the select doc or code. In the module/selectmodule.c code, the various poll methods interpret -1 as the error return for a closed fd. I do not know how it deals with socket.fileno raising ValueError (or returning None?).

In the client doc, none of several examples of using HTTPResponses use select. They just use the various methods to retrieve data. I could interpret this to mean that they are not intended to work with select. The fact that they do not, reinforces that.

----------

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

From report at bugs.python.org  Tue Oct  8 23:03:50 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 21:03:50 +0000
Subject: [docs] [issue19197] Improve cross-references in shlex documentation
Message-ID: <1381266229.65.0.408303361922.issue19197@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the documentation of the shlex module.

----------
assignee: docs at python
components: Documentation
files: refs.shlex.patch
keywords: patch
messages: 199247
nosy: docs at python, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in shlex documentation
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32005/refs.shlex.patch

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

From report at bugs.python.org  Tue Oct  8 23:05:35 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 21:05:35 +0000
Subject: [docs] [issue19198] Improve cross-references in cgi documentation
Message-ID: <1381266335.84.0.645626523869.issue19198@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the documentation of the cgi module.

----------
assignee: docs at python
components: Documentation
files: refs.cgi.patch
keywords: patch
messages: 199249
nosy: docs at python, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in cgi documentation
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32006/refs.cgi.patch

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

From report at bugs.python.org  Tue Oct  8 23:06:23 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 08 Oct 2013 21:06:23 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381266383.28.0.0887660069095.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Improve cross-references in cgi documentation, Improve cross-references in shlex documentation

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

From report at bugs.python.org  Tue Oct  8 23:11:00 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 08 Oct 2013 21:11:00 +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: <1381266660.54.0.0640448787801.issue19154@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I think ValueError should generally be raised when calling fileno() on a closed file. However, this is not something we're gonna change in a bugfix release, so it would go in 3.4 at the earliest.

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

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

From report at bugs.python.org  Wed Oct  9 00:33:38 2013
From: report at bugs.python.org (Elazar Gershuni)
Date: Tue, 08 Oct 2013 22:33:38 +0000
Subject: [docs] [issue19200] grammar in forkserver docs
Message-ID: <1381271618.79.0.0617201422198.issue19200@psf.upfronthosting.co.za>


New submission from Elazar Gershuni:

in http://docs.python.org/3.4/library/multiprocessing.html#start-methods
for `forkserver`:
"whenever a new process is need the parent process connects to the server and requests that it fork a new process."

replace "need " with "needed, ".

----------
assignee: docs at python
components: Documentation
messages: 199269
nosy: docs at python, elazar
priority: normal
severity: normal
status: open
title: grammar in forkserver docs
versions: Python 3.4

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

From report at bugs.python.org  Wed Oct  9 04:23:40 2013
From: report at bugs.python.org (Berker Peksag)
Date: Wed, 09 Oct 2013 02:23:40 +0000
Subject: [docs] [issue19200] grammar in forkserver docs
In-Reply-To: <1381271618.79.0.0617201422198.issue19200@psf.upfronthosting.co.za>
Message-ID: <1381285420.99.0.721356205049.issue19200@psf.upfronthosting.co.za>


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


----------
nosy: +sbt

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

From storchaka at gmail.com  Wed Oct  9 08:43:25 2013
From: storchaka at gmail.com (storchaka at gmail.com)
Date: Wed, 09 Oct 2013 06:43:25 -0000
Subject: [docs] Improve cross-references in C API (issue 19195)
Message-ID: <20131009064325.24133.4967@psf.upfronthosting.co.za>

Reviewers: Georg,


http://bugs.python.org/review/19195/diff/9475/Doc/c-api/buffer.rst
File Doc/c-api/buffer.rst (right):

http://bugs.python.org/review/19195/diff/9475/Doc/c-api/buffer.rst#newcode47
Doc/c-api/buffer.rst:47: the buffer interface can be written to a file. 
While :meth:`~io.BufferedIOBase.write` only
On 2013/10/08 22:22:46, Georg wrote:
> just replace by ``write()``, two references in two sentences is not
needed

Perhaps :meth:`!write`? Or left as is? I suppose documentation formatter
can use special style decorations for different roles.

http://bugs.python.org/review/19195/diff/9475/Doc/c-api/typeobj.rst
File Doc/c-api/typeobj.rst (right):

http://bugs.python.org/review/19195/diff/9475/Doc/c-api/typeobj.rst#newcode643
Doc/c-api/typeobj.rst:643: When a type's :attr:`~object.__slots__`
declaration contains a slot named
On 2013/10/08 22:22:46, Georg wrote:
> here too: too many links are not needed and distract.

Doesn't many :c:member:`~PyTypeObject.tp_weaklistoffset` distract?



Please review this at http://bugs.python.org/review/19195/

Affected files:
  Doc/c-api/buffer.rst
  Doc/c-api/codec.rst
  Doc/c-api/file.rst
  Doc/c-api/object.rst
  Doc/c-api/set.rst
  Doc/c-api/typeobj.rst
  Doc/c-api/unicode.rst
  Doc/c-api/veryhigh.rst
  Doc/extending/building.rst
  Doc/extending/extending.rst
  Doc/extending/newtypes.rst


diff -r a49d313a28ae Doc/c-api/buffer.rst
--- a/Doc/c-api/buffer.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/c-api/buffer.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -44,7 +44,7 @@
 
 An example consumer of the buffer interface is the :meth:`~io.BufferedIOBase.write`
 method of file objects: any object that can export a series of bytes through
-the buffer interface can be written to a file.  While :meth:`write` only
+the buffer interface can be written to a file.  While :meth:`~io.BufferedIOBase.write` only
 needs read-only access to the internal contents of the object passed to it,
 other methods such as :meth:`~io.BufferedIOBase.readinto` need write access
 to the contents of their argument.  The buffer interface allows objects to
diff -r a49d313a28ae Doc/c-api/codec.rst
--- a/Doc/c-api/codec.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/c-api/codec.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -52,19 +52,19 @@
 
 .. c:function:: PyObject* PyCodec_IncrementalEncoder(const char *encoding, const char *errors)
 
-   Get an :class:`IncrementalEncoder` object for the given *encoding*.
+   Get an :class:`~codecs.IncrementalEncoder` object for the given *encoding*.
 
 .. c:function:: PyObject* PyCodec_IncrementalDecoder(const char *encoding, const char *errors)
 
-   Get an :class:`IncrementalDecoder` object for the given *encoding*.
+   Get an :class:`~codecs.IncrementalDecoder` object for the given *encoding*.
 
 .. c:function:: PyObject* PyCodec_StreamReader(const char *encoding, PyObject *stream, const char *errors)
 
-   Get a :class:`StreamReader` factory function for the given *encoding*.
+   Get a :class:`~codecs.StreamReader` factory function for the given *encoding*.
 
 .. c:function:: PyObject* PyCodec_StreamWriter(const char *encoding, PyObject *stream, const char *errors)
 
-   Get a :class:`StreamWriter` factory function for the given *encoding*.
+   Get a :class:`~codecs.StreamWriter` factory function for the given *encoding*.
 
 
 Registry API for Unicode encoding error handlers
diff -r a49d313a28ae Doc/c-api/file.rst
--- a/Doc/c-api/file.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/c-api/file.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -40,7 +40,7 @@
 
    Return the file descriptor associated with *p* as an :c:type:`int`.  If the
    object is an integer, its value is returned.  If not, the
-   object's :meth:`fileno` method is called if it exists; the method must return
+   object's :meth:`~io.IOBase.fileno` method is called if it exists; the method must return
    an integer, which is returned as the file descriptor value.  Sets an
    exception and returns ``-1`` on failure.
 
@@ -50,7 +50,7 @@
    .. index:: single: EOFError (built-in exception)
 
    Equivalent to ``p.readline([n])``, this function reads one line from the
-   object *p*.  *p* may be a file object or any object with a :meth:`readline`
+   object *p*.  *p* may be a file object or any object with a :meth:`~io.IOBase.readline`
    method.  If *n* is ``0``, exactly one line is read, regardless of the length of
    the line.  If *n* is greater than ``0``, no more than *n* bytes will be read
    from the file; a partial line can be returned.  In both cases, an empty string
diff -r a49d313a28ae Doc/c-api/object.rst
--- a/Doc/c-api/object.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/c-api/object.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -60,7 +60,7 @@
    Generic attribute getter function that is meant to be put into a type
    object's ``tp_getattro`` slot.  It looks for a descriptor in the dictionary
    of classes in the object's MRO as well as an attribute in the object's
-   :attr:`__dict__` (if present).  As outlined in :ref:`descriptors`, data
+   :attr:`~object.__dict__` (if present).  As outlined in :ref:`descriptors`, data
    descriptors take preference over instance attributes, while non-data
    descriptors don't.  Otherwise, an :exc:`AttributeError` is raised.
 
@@ -85,7 +85,7 @@
    object's ``tp_setattro`` slot.  It looks for a data descriptor in the
    dictionary of classes in the object's MRO, and if found it takes preference
    over setting the attribute in the instance dictionary. Otherwise, the
-   attribute is set in the object's :attr:`__dict__` (if present).  Otherwise,
+   attribute is set in the object's :attr:`~object.__dict__` (if present).  Otherwise,
    an :exc:`AttributeError` is raised and ``-1`` is returned.
 
 
@@ -189,7 +189,7 @@
    be done against every entry in *cls*. The result will be ``1`` when at least one
    of the checks returns ``1``, otherwise it will be ``0``. If *inst* is not a
    class instance and *cls* is neither a type object, nor a class object, nor a
-   tuple, *inst* must have a :attr:`__class__` attribute --- the class relationship
+   tuple, *inst* must have a :attr:`~instance.__class__` attribute --- the class relationship
    of the value of that attribute with *cls* will be used to determine the result
    of this function.
 
@@ -201,8 +201,8 @@
 either is not a class object, a more general mechanism is used to determine the
 class relationship of the two objects.  When testing if *B* is a subclass of
 *A*, if *A* is *B*, :c:func:`PyObject_IsSubclass` returns true.  If *A* and *B*
-are different objects, *B*'s :attr:`__bases__` attribute is searched in a
-depth-first fashion for *A* --- the presence of the :attr:`__bases__` attribute
+are different objects, *B*'s :attr:`~class.__bases__` attribute is searched in a
+depth-first fashion for *A* --- the presence of the :attr:`~class.__bases__` attribute
 is considered sufficient for this determination.
 
 
diff -r a49d313a28ae Doc/c-api/set.rst
--- a/Doc/c-api/set.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/c-api/set.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -140,7 +140,7 @@
 
    Return 1 if found and removed, 0 if not found (no action taken), and -1 if an
    error is encountered.  Does not raise :exc:`KeyError` for missing keys.  Raise a
-   :exc:`TypeError` if the *key* is unhashable.  Unlike the Python :meth:`discard`
+   :exc:`TypeError` if the *key* is unhashable.  Unlike the Python :meth:`~set.discard`
    method, this function does not automatically convert unhashable sets into
    temporary frozensets. Raise :exc:`PyExc_SystemError` if *set* is an not an
    instance of :class:`set` or its subtype.
diff -r a49d313a28ae Doc/c-api/typeobj.rst
--- a/Doc/c-api/typeobj.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/c-api/typeobj.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -510,7 +510,7 @@
 
    On the other hand, even if you know a member can never be part of a cycle, as a
    debugging aid you may want to visit it anyway just so the :mod:`gc` module's
-   :func:`get_referents` function will include it.
+   :func:`~gc.get_referents` function will include it.
 
    Note that :c:func:`Py_VISIT` requires the *visit* and *arg* parameters to
    :c:func:`local_traverse` to have these specific names; don't name them just
@@ -635,17 +635,17 @@
    reference list head than the base type.  Since the list head is always found via
    :c:member:`~PyTypeObject.tp_weaklistoffset`, this should not be a problem.
 
-   When a type defined by a class statement has no :attr:`__slots__` declaration,
+   When a type defined by a class statement has no :attr:`~object.__slots__` declaration,
    and none of its base types are weakly referenceable, the type is made weakly
    referenceable by adding a weak reference list head slot to the instance layout
    and setting the :c:member:`~PyTypeObject.tp_weaklistoffset` of that slot's offset.
 
-   When a type's :attr:`__slots__` declaration contains a slot named
+   When a type's :attr:`~object.__slots__` declaration contains a slot named
    :attr:`__weakref__`, that slot becomes the weak reference list head for
    instances of the type, and the slot's offset is stored in the type's
    :c:member:`~PyTypeObject.tp_weaklistoffset`.
 
-   When a type's :attr:`__slots__` declaration does not contain a slot named
+   When a type's :attr:`~object.__slots__` declaration does not contain a slot named
    :attr:`__weakref__`, the type inherits its :c:member:`~PyTypeObject.tp_weaklistoffset` from its
    base type.
 
@@ -825,15 +825,15 @@
    dictionary at a difference offset than the base type.  Since the dictionary is
    always found via :c:member:`~PyTypeObject.tp_dictoffset`, this should not be a problem.
 
-   When a type defined by a class statement has no :attr:`__slots__` declaration,
+   When a type defined by a class statement has no :attr:`~object.__slots__` declaration,
    and none of its base types has an instance variable dictionary, a dictionary
    slot is added to the instance layout and the :c:member:`~PyTypeObject.tp_dictoffset` is set to
    that slot's offset.
 
-   When a type defined by a class statement has a :attr:`__slots__` declaration,
+   When a type defined by a class statement has a :attr:`~object.__slots__` declaration,
    the type inherits its :c:member:`~PyTypeObject.tp_dictoffset` from its base type.
 
-   (Adding a slot named :attr:`__dict__` to the :attr:`__slots__` declaration does
+   (Adding a slot named :attr:`~object.__dict__` to the :attr:`~object.__slots__` declaration does
    not have the expected effect, it just causes confusion.  Maybe this should be
    added as a feature just like :attr:`__weakref__` though.)
 
diff -r a49d313a28ae Doc/c-api/unicode.rst
--- a/Doc/c-api/unicode.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/c-api/unicode.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -978,7 +978,7 @@
 
    Create a Unicode object by decoding *size* bytes of the encoded string *s*.
    *encoding* and *errors* have the same meaning as the parameters of the same name
-   in the :func:`unicode` built-in function.  The codec to be used is looked up
+   in the :func:`str` built-in function.  The codec to be used is looked up
    using the Python codec registry.  Return *NULL* if an exception was raised by
    the codec.
 
@@ -988,7 +988,7 @@
 
    Encode a Unicode object and return the result as Python bytes object.
    *encoding* and *errors* have the same meaning as the parameters of the same
-   name in the Unicode :meth:`encode` method. The codec to be used is looked up
+   name in the Unicode :meth:`~str.encode` method. The codec to be used is looked up
    using the Python codec registry. Return *NULL* if an exception was raised by
    the codec.
 
@@ -998,7 +998,7 @@
 
    Encode the :c:type:`Py_UNICODE` buffer *s* of the given *size* and return a Python
    bytes object.  *encoding* and *errors* have the same meaning as the
-   parameters of the same name in the Unicode :meth:`encode` method.  The codec
+   parameters of the same name in the Unicode :meth:`~str.encode` method.  The codec
    to be used is looked up using the Python codec registry.  Return *NULL* if an
    exception was raised by the codec.
 
diff -r a49d313a28ae Doc/c-api/veryhigh.rst
--- a/Doc/c-api/veryhigh.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/c-api/veryhigh.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -312,7 +312,7 @@
    frame *f* is executed, interpreting bytecode and executing calls as needed.
    The additional *throwflag* parameter can mostly be ignored - if true, then
    it causes an exception to immediately be thrown; this is used for the
-   :meth:`throw` methods of generator objects.
+   :meth:`~generator.throw` methods of generator objects.
 
 
 .. c:function:: int PyEval_MergeCompilerFlags(PyCompilerFlags *cf)
diff -r a49d313a28ae Doc/extending/building.rst
--- a/Doc/extending/building.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/extending/building.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -58,8 +58,9 @@
 It is common to pre-compute arguments to :func:`setup`, to better structure the
 driver script. In the example above, the\ ``ext_modules`` argument to
 :func:`setup` is a list of extension modules, each of which is an instance of
-the :class:`Extension`. In the example, the instance defines an extension named
-``demo`` which is build by compiling a single source file, :file:`demo.c`.
+the :class:`~distutils.extension.Extension`. In the example, the instance
+defines an extension named ``demo`` which is build by compiling a single source
+file, :file:`demo.c`.
 
 In many cases, building an extension is more complex, since additional
 preprocessor defines and libraries may be needed. This is demonstrated in the
diff -r a49d313a28ae Doc/extending/extending.rst
--- a/Doc/extending/extending.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/extending/extending.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -860,9 +860,9 @@
 The cycle detector is able to detect garbage cycles and can reclaim them so long
 as there are no finalizers implemented in Python (:meth:`__del__` methods).
 When there are such finalizers, the detector exposes the cycles through the
-:mod:`gc` module (specifically, the
-``garbage`` variable in that module).  The :mod:`gc` module also exposes a way
-to run the detector (the :func:`collect` function), as well as configuration
+:mod:`gc` module (specifically, the :attr:`~gc.garbage` variable in that module).
+The :mod:`gc` module also exposes a way to run the detector (the
+:func:`~gc.collect` function), as well as configuration
 interfaces and the ability to disable the detector at runtime.  The cycle
 detector is considered an optional component; though it is included by default,
 it can be disabled at build time using the :option:`--without-cycle-gc` option
diff -r a49d313a28ae Doc/extending/newtypes.rst
--- a/Doc/extending/newtypes.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/extending/newtypes.rst	Tue Oct 08 22:54:20 2013 +0300
@@ -137,7 +137,7 @@
    If you want your type to be subclassable from Python, and your type has the same
    :c:member:`~PyTypeObject.tp_basicsize` as its base type, you may have problems with multiple
    inheritance.  A Python subclass of your type will have to list your type first
-   in its :attr:`__bases__`, or else it will not be able to call your type's
+   in its :attr:`~class.__bases__`, or else it will not be able to call your type's
    :meth:`__new__` method without getting an error.  You can avoid this problem by
    ensuring that your type has a larger value for :c:member:`~PyTypeObject.tp_basicsize` than its
    base type does.  Most of the time, this will be true anyway, because either your



From report at bugs.python.org  Wed Oct  9 08:56:59 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 09 Oct 2013 06:56:59 +0000
Subject: [docs] [issue19193] Improve cross-references in tutorial
In-Reply-To: <1381256218.12.0.311002758548.issue19193@psf.upfronthosting.co.za>
Message-ID: <3cvmSV554xz7LjT@mail.python.org>


Roundup Robot added the comment:

New changeset ac826284fdd1 by Serhiy Storchaka in branch '2.7':
Issue #19193: Improved cross-references in the tutorial.
http://hg.python.org/cpython/rev/ac826284fdd1

New changeset 012380d57e44 by Serhiy Storchaka in branch '3.3':
Issue #19193: Improved cross-references in the tutorial.
http://hg.python.org/cpython/rev/012380d57e44

New changeset e338a5c8fcfa by Serhiy Storchaka in branch 'default':
Issue #19193: Improved cross-references in the tutorial.
http://hg.python.org/cpython/rev/e338a5c8fcfa

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

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

From report at bugs.python.org  Wed Oct  9 08:59:35 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 06:59:35 +0000
Subject: [docs] [issue19193] Improve cross-references in tutorial
In-Reply-To: <1381256218.12.0.311002758548.issue19193@psf.upfronthosting.co.za>
Message-ID: <1381301975.13.0.121631656802.issue19193@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you Georg for the review.

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

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

From storchaka at gmail.com  Wed Oct  9 09:13:02 2013
From: storchaka at gmail.com (storchaka at gmail.com)
Date: Wed, 09 Oct 2013 07:13:02 -0000
Subject: [docs] Improve cross-references in builtins documentation.
	(issue 19190)
Message-ID: <20131009071302.5252.764@psf.upfronthosting.co.za>

Reviewers: Georg,


http://bugs.python.org/review/19190/diff/9471/Doc/library/stdtypes.rst
File Doc/library/stdtypes.rst (right):

http://bugs.python.org/review/19190/diff/9471/Doc/library/stdtypes.rst#newcode637
Doc/library/stdtypes.rst:637: made available to Python as the
:attr:`~sys.hash_info.modulus` attribute of
On 2013/10/08 22:31:08, Georg wrote:
> leave out tilde, remove "of sys.hash_info"

Actually a link to sys.hash_info.modulus doesn't work yet, but a link to
sys.hash_info does. I change it in hope that we will make attributes
referencable in future.



Please review this at http://bugs.python.org/review/19190/

Affected files:
  Doc/glossary.rst
  Doc/library/functions.rst
  Doc/library/numbers.rst
  Doc/library/stdtypes.rst
  Doc/reference/datamodel.rst
  Doc/reference/expressions.rst



From report at bugs.python.org  Wed Oct  9 09:15:18 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 07:15:18 +0000
Subject: [docs] [issue19190] Improve cross-references in builtins
	documentation.
In-Reply-To: <1381178406.23.0.925502914141.issue19190@psf.upfronthosting.co.za>
Message-ID: <1381302917.12.0.55098657526.issue19190@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Updated patch addresses more Georg's comments.

----------
Added file: http://bugs.python.org/file32011/refs.builtins_3.patch

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

From georg at python.org  Wed Oct  9 09:54:56 2013
From: georg at python.org (georg at python.org)
Date: Wed, 09 Oct 2013 07:54:56 -0000
Subject: [docs] Improve cross-references in C API (issue 19195)
Message-ID: <20131009075456.24134.18476@psf.upfronthosting.co.za>


http://bugs.python.org/review/19195/diff/9475/Doc/c-api/buffer.rst
File Doc/c-api/buffer.rst (right):

http://bugs.python.org/review/19195/diff/9475/Doc/c-api/buffer.rst#newcode47
Doc/c-api/buffer.rst:47: the buffer interface can be written to a file. 
While :meth:`~io.BufferedIOBase.write` only
Left as-is is fine as well.

Special decorations aren't really required; we shouldn't add semantic
markup for purity's sake, only when it's useful for linking.

On 2013/10/09 08:43:25, storchaka wrote:
> On 2013/10/08 22:22:46, Georg wrote:
> > just replace by ``write()``, two references in two sentences is not
needed
> 
> Perhaps :meth:`!write`? Or left as is? I suppose documentation
formatter can use
> special style decorations for different roles.

http://bugs.python.org/review/19195/diff/9475/Doc/c-api/typeobj.rst
File Doc/c-api/typeobj.rst (right):

http://bugs.python.org/review/19195/diff/9475/Doc/c-api/typeobj.rst#newcode643
Doc/c-api/typeobj.rst:643: When a type's :attr:`~object.__slots__`
declaration contains a slot named
Yes, of course.  This markup was there before, I only looked at your
changes.

On 2013/10/09 08:43:25, storchaka wrote:
> On 2013/10/08 22:22:46, Georg wrote:
> > here too: too many links are not needed and distract.
> 
> Doesn't many :c:member:`~PyTypeObject.tp_weaklistoffset` distract?

http://bugs.python.org/review/19195/

From georg at python.org  Wed Oct  9 09:56:26 2013
From: georg at python.org (georg at python.org)
Date: Wed, 09 Oct 2013 07:56:26 -0000
Subject: [docs] Improve cross-references in builtins documentation.
	(issue 19190)
Message-ID: <20131009075626.5252.8587@psf.upfronthosting.co.za>


http://bugs.python.org/review/19190/diff/9471/Doc/library/stdtypes.rst
File Doc/library/stdtypes.rst (right):

http://bugs.python.org/review/19190/diff/9471/Doc/library/stdtypes.rst#newcode637
Doc/library/stdtypes.rst:637: made available to Python as the
:attr:`~sys.hash_info.modulus` attribute of
Right; in that case I would prefer the original version.

On 2013/10/09 09:13:02, storchaka wrote:
> On 2013/10/08 22:31:08, Georg wrote:
> > leave out tilde, remove "of sys.hash_info"
> 
> Actually a link to sys.hash_info.modulus doesn't work yet, but a link
to
> sys.hash_info does. I change it in hope that we will make attributes
> referencable in future.

http://bugs.python.org/review/19190/

From storchaka at gmail.com  Wed Oct  9 10:05:55 2013
From: storchaka at gmail.com (storchaka at gmail.com)
Date: Wed, 09 Oct 2013 08:05:55 -0000
Subject: [docs] Improve cross-references in pickle documentation (issue
	19196)
Message-ID: <20131009080555.5252.5427@psf.upfronthosting.co.za>

Reviewers: Georg,


http://bugs.python.org/review/19196/diff/9476/Doc/distutils/setupscript.rst
File Doc/distutils/setupscript.rst (right):

http://bugs.python.org/review/19196/diff/9476/Doc/distutils/setupscript.rst#newcode149
Doc/distutils/setupscript.rst:149: The
:class:`~distutils.core.Extension` class can be imported from
:mod:`distutils.core` along
On 2013/10/08 22:25:09, Georg wrote:
> unneeded... etc.

Perhaps left one link per subsection?



Please review this at http://bugs.python.org/review/19196/

Affected files:
  Doc/distutils/apiref.rst
  Doc/distutils/extending.rst
  Doc/distutils/setupscript.rst


diff -r a49d313a28ae Doc/distutils/apiref.rst
--- a/Doc/distutils/apiref.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/distutils/apiref.rst	Tue Oct 08 22:58:19 2013 +0300
@@ -994,12 +994,12 @@
    simply the list of all files under *src*, with the names changed to be under
    *dst*.
 
-   *preserve_mode* and *preserve_times* are the same as for :func:`copy_file` in
+   *preserve_mode* and *preserve_times* are the same as for :func:`~distutils.file_util.copy_file` in
    :mod:`distutils.file_util`; note that they only apply to regular files, not to
    directories.  If *preserve_symlinks* is true, symlinks will be copied as
    symlinks (on platforms that support them!); otherwise (the default), the
    destination of the symlink will be copied.  *update* and *verbose* are the same
-   as for :func:`copy_file`.
+   as for :func:`~distutils.file_util.copy_file`.
 
    Files in *src* that begin with :file:`.nfs` are skipped (more information on
    these files is available in answer D2 of the `NFS FAQ page
@@ -1175,7 +1175,7 @@
    Generate a useful error message from an :exc:`OSError` exception object.
    Handles Python 1.5.1 and later styles, and does what it can to deal with
    exception objects that don't have a filename (which happens when the error
-   is due to a two-file operation, such as :func:`rename` or :func:`link`).
+   is due to a two-file operation, such as :func:`~os.rename` or :func:`~os.link`).
    Returns the error message as a string prefixed with *prefix*.
 
 
@@ -1265,7 +1265,7 @@
               built/installed/distributed
 
 
-This module provides the :class:`Distribution` class, which represents the
+This module provides the :class:`~distutils.core.Distribution` class, which represents the
 module distribution being built/installed/distributed.
 
 
@@ -1712,7 +1712,7 @@
    options, is the :meth:`run` method, which must also be implemented by every
    command class.
 
-   The class constructor takes a single argument *dist*, a :class:`Distribution`
+   The class constructor takes a single argument *dist*, a :class:`~distutils.core.Distribution`
    instance.
 
 
diff -r a49d313a28ae Doc/distutils/extending.rst
--- a/Doc/distutils/extending.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/distutils/extending.rst	Tue Oct 08 22:58:19 2013 +0300
@@ -17,9 +17,9 @@
 
 Most distutils command implementations are subclasses of the
 :class:`distutils.cmd.Command` class.  New commands may directly inherit from
-:class:`Command`, while replacements often derive from :class:`Command`
+:class:`~distutils.cmd.Command`, while replacements often derive from :class:`~distutils.cmd.Command`
 indirectly, directly subclassing the command they are replacing.  Commands are
-required to derive from :class:`Command`.
+required to derive from :class:`~distutils.cmd.Command`.
 
 .. % \section{Extending existing commands}
 .. % \label{extend-existing}
diff -r a49d313a28ae Doc/distutils/setupscript.rst
--- a/Doc/distutils/setupscript.rst	Tue Oct 08 21:08:48 2013 +0300
+++ b/Doc/distutils/setupscript.rst	Tue Oct 08 22:58:19 2013 +0300
@@ -139,14 +139,14 @@
 
 All of this is done through another keyword argument to :func:`setup`, the
 :option:`ext_modules` option.  :option:`ext_modules` is just a list of
-:class:`Extension` instances, each of which describes a single extension module.
+:class:`~distutils.core.Extension` instances, each of which describes a single extension module.
 Suppose your distribution includes a single extension, called :mod:`foo` and
 implemented by :file:`foo.c`.  If no additional instructions to the
 compiler/linker are needed, describing this extension is quite simple::
 
     Extension('foo', ['foo.c'])
 
-The :class:`Extension` class can be imported from :mod:`distutils.core` along
+The :class:`~distutils.core.Extension` class can be imported from :mod:`distutils.core` along
 with :func:`setup`.  Thus, the setup script for a module distribution that
 contains only this one extension and nothing else might be::
 
@@ -156,7 +156,7 @@
           ext_modules=[Extension('foo', ['foo.c'])],
           )
 
-The :class:`Extension` class (actually, the underlying extension-building
+The :class:`~distutils.core.Extension` class (actually, the underlying extension-building
 machinery implemented by the :command:`build_ext` command) supports a great deal
 of flexibility in describing Python extensions, which is explained in the
 following sections.
@@ -165,7 +165,7 @@
 Extension names and packages
 ----------------------------
 
-The first argument to the :class:`Extension` constructor is always the name of
+The first argument to the :class:`~distutils.core.Extension` constructor is always the name of
 the extension, including any package names.  For example, ::
 
     Extension('foo', ['src/foo1.c', 'src/foo2.c'])
@@ -196,7 +196,7 @@
 Extension source files
 ----------------------
 
-The second argument to the :class:`Extension` constructor is a list of source
+The second argument to the :class:`~distutils.core.Extension` constructor is a list of source
 files.  Since the Distutils currently only support C, C++, and Objective-C
 extensions, these are normally C/C++/Objective-C source files.  (Be sure to use
 appropriate extensions to distinguish C++\ source files: :file:`.cc` and
@@ -232,7 +232,7 @@
 Preprocessor options
 --------------------
 
-Three optional arguments to :class:`Extension` will help if you need to specify
+Three optional arguments to :class:`~distutils.core.Extension` will help if you need to specify
 include directories to search or preprocessor macros to define/undefine:
 ``include_dirs``, ``define_macros``, and ``undef_macros``.
 



From report at bugs.python.org  Wed Oct  9 10:11:12 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 08:11:12 +0000
Subject: [docs] [issue19196] Improve cross-references in distutils
	documentation
In-Reply-To: <1381262400.58.0.379802599514.issue19196@psf.upfronthosting.co.za>
Message-ID: <1381306272.6.0.446655031981.issue19196@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Updated patch addresses Georg's comments.

----------
Added file: http://bugs.python.org/file32012/refs.distutils_2.patch

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

From georg at python.org  Wed Oct  9 10:20:37 2013
From: georg at python.org (georg at python.org)
Date: Wed, 09 Oct 2013 08:20:37 -0000
Subject: [docs] Improve cross-references in pickle documentation (issue
	19196)
Message-ID: <20131009082037.24134.71120@psf.upfronthosting.co.za>


http://bugs.python.org/review/19196/diff/9476/Doc/distutils/setupscript.rst
File Doc/distutils/setupscript.rst (right):

http://bugs.python.org/review/19196/diff/9476/Doc/distutils/setupscript.rst#newcode149
Doc/distutils/setupscript.rst:149: The
:class:`~distutils.core.Extension` class can be imported from
:mod:`distutils.core` along
Yes, something like that is fine.

On 2013/10/09 10:05:55, storchaka wrote:
> On 2013/10/08 22:25:09, Georg wrote:
> > unneeded... etc.
> 
> Perhaps left one link per subsection?

http://bugs.python.org/review/19196/

From georg at python.org  Wed Oct  9 10:20:37 2013
From: georg at python.org (georg at python.org)
Date: Wed, 09 Oct 2013 08:20:37 -0000
Subject: [docs] Improve cross-references in pickle documentation (issue
	19196)
Message-ID: <20131009082037.24133.37302@psf.upfronthosting.co.za>

http://bugs.python.org/review/19196/

From report at bugs.python.org  Wed Oct  9 12:09:16 2013
From: report at bugs.python.org (Esa Peuha)
Date: Wed, 09 Oct 2013 10:09:16 +0000
Subject: [docs] [issue19202] Additions to docs
Message-ID: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>


New submission from Esa Peuha:

Here are some additions to documentation of a few functions:

all, any: alternative definitions using functools.reduce
enumerate: alternative definition using zip and itertools.count
sum: equivalent definition using functools.reduce and operator.add
functools.reduce: equivalent definitions, use operator.add in example
itertools.accumulate: point to functools.reduce
itertools.filterfalse: point to filter

----------
assignee: docs at python
components: Documentation
files: doc.diff
keywords: patch
messages: 199281
nosy: Esa.Peuha, docs at python
priority: normal
severity: normal
status: open
title: Additions to docs
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file32013/doc.diff

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

From report at bugs.python.org  Wed Oct  9 12:29:57 2013
From: report at bugs.python.org (Georg Brandl)
Date: Wed, 09 Oct 2013 10:29:57 +0000
Subject: [docs] [issue19202] Additions to docs
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381314597.8.0.741606061038.issue19202@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Most of these changes should not be applied: the "alternate" equivalents in terms of reduce() will not help understanding,  Equivalents for reduce() may be useful, but I would limit them to one per case, possibly even just one function that covers both cases.

I'm deferring to Raymond for the changes to the itertools docs.

----------
nosy: +georg.brandl, rhettinger

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

From report at bugs.python.org  Wed Oct  9 13:00:30 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 09 Oct 2013 11:00:30 +0000
Subject: [docs] [issue19195] Improve cross-references in C API
In-Reply-To: <1381262191.72.0.573497194321.issue19195@psf.upfronthosting.co.za>
Message-ID: <3cvssT2ZFVz7Ljm@mail.python.org>


Roundup Robot added the comment:

New changeset 9b855a701e28 by Serhiy Storchaka in branch '2.7':
Issue 19195: Improved cross-references in C API documentation.
http://hg.python.org/cpython/rev/9b855a701e28

New changeset f0491617b098 by Serhiy Storchaka in branch '3.3':
Issue 19195: Improved cross-references in C API documentation.
http://hg.python.org/cpython/rev/f0491617b098

New changeset e30b27927e49 by Serhiy Storchaka in branch 'default':
Issue 19195: Improved cross-references in C API documentation.
http://hg.python.org/cpython/rev/e30b27927e49

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

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

From report at bugs.python.org  Wed Oct  9 13:04:13 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 09 Oct 2013 11:04:13 +0000
Subject: [docs] [issue19190] Improve cross-references in builtins
	documentation.
In-Reply-To: <1381178406.23.0.925502914141.issue19190@psf.upfronthosting.co.za>
Message-ID: <3cvsxm5CGGzRND@mail.python.org>


Roundup Robot added the comment:

New changeset 7565df5939de by Serhiy Storchaka in branch '2.7':
Issue #19190: Improve cross-references in builtin types and functions documentation.
http://hg.python.org/cpython/rev/7565df5939de

New changeset 207e1e1cb17a by Serhiy Storchaka in branch '3.3':
Issue #19190: Improve cross-references in builtin types and functions documentation.
http://hg.python.org/cpython/rev/207e1e1cb17a

New changeset a3f6e5920881 by Serhiy Storchaka in branch 'default':
Issue #19190: Improve cross-references in builtin types and functions documentation.
http://hg.python.org/cpython/rev/a3f6e5920881

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

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

From report at bugs.python.org  Wed Oct  9 13:10:07 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 09 Oct 2013 11:10:07 +0000
Subject: [docs] [issue19196] Improve cross-references in distutils
	documentation
In-Reply-To: <1381262400.58.0.379802599514.issue19196@psf.upfronthosting.co.za>
Message-ID: <3cvt4Z5dXzz7LjQ@mail.python.org>


Roundup Robot added the comment:

New changeset e0b9e0ed561a by Serhiy Storchaka in branch '2.7':
#19196: Improved cross-references in distutils documentation.
http://hg.python.org/cpython/rev/e0b9e0ed561a

New changeset 0879b60de41f by Serhiy Storchaka in branch '3.3':
#19196: Improved cross-references in distutils documentation.
http://hg.python.org/cpython/rev/0879b60de41f

New changeset d70799f69d25 by Serhiy Storchaka in branch 'default':
#19196: Improved cross-references in distutils documentation.
http://hg.python.org/cpython/rev/d70799f69d25

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

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

From report at bugs.python.org  Wed Oct  9 13:11:55 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 11:11:55 +0000
Subject: [docs] [issue19195] Improve cross-references in C API
In-Reply-To: <1381262191.72.0.573497194321.issue19195@psf.upfronthosting.co.za>
Message-ID: <1381317115.89.0.301050907175.issue19195@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for the review Georg.

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

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

From report at bugs.python.org  Wed Oct  9 13:12:30 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 11:12:30 +0000
Subject: [docs] [issue19190] Improve cross-references in builtins
	documentation.
In-Reply-To: <1381178406.23.0.925502914141.issue19190@psf.upfronthosting.co.za>
Message-ID: <1381317150.33.0.855410351162.issue19190@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for the review Georg.

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

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

From report at bugs.python.org  Wed Oct  9 13:12:56 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 11:12:56 +0000
Subject: [docs] [issue19196] Improve cross-references in distutils
	documentation
In-Reply-To: <1381262400.58.0.379802599514.issue19196@psf.upfronthosting.co.za>
Message-ID: <1381317176.27.0.969484318102.issue19196@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for the review Georg.

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

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

From report at bugs.python.org  Wed Oct  9 13:23:15 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 09 Oct 2013 11:23:15 +0000
Subject: [docs] [issue19194] Improve cross-references in fcntl documentation
In-Reply-To: <1381261840.65.0.334313272339.issue19194@psf.upfronthosting.co.za>
Message-ID: <3cvtMl13GPz7LjQ@mail.python.org>


Roundup Robot added the comment:

New changeset 372abcca25fc by Serhiy Storchaka in branch '2.7':
#19194: Improved cross-references in the fcntl module documentation.
http://hg.python.org/cpython/rev/372abcca25fc

New changeset 9015a84d694e by Serhiy Storchaka in branch '3.3':
#19194: Improved cross-references in the fcntl module documentation.
http://hg.python.org/cpython/rev/9015a84d694e

New changeset d76e91a29f64 by Serhiy Storchaka in branch 'default':
#19194: Improved cross-references in the fcntl module documentation.
http://hg.python.org/cpython/rev/d76e91a29f64

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

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

From report at bugs.python.org  Wed Oct  9 13:54:56 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 11:54:56 +0000
Subject: [docs] [issue19194] Improve cross-references in fcntl documentation
In-Reply-To: <1381261840.65.0.334313272339.issue19194@psf.upfronthosting.co.za>
Message-ID: <1381319696.57.0.696504504372.issue19194@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for the review Georg.

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

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

From report at bugs.python.org  Wed Oct  9 14:17:58 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 12:17:58 +0000
Subject: [docs] [issue19203] Improve cross-references in curses howto
Message-ID: <1381321077.27.0.332235799284.issue19203@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the howto of the curses module.

----------
assignee: docs at python
components: Documentation
files: refs.curses-howto.patch
keywords: patch
messages: 199291
nosy: akuchling, docs at python, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in curses howto
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32014/refs.curses-howto.patch

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

From report at bugs.python.org  Wed Oct  9 14:18:19 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 12:18:19 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381321099.95.0.804830636013.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Improve cross-references in curses howto

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

From report at bugs.python.org  Wed Oct  9 14:19:25 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 12:19:25 +0000
Subject: [docs] [issue19203] Improve cross-references in curses howto
In-Reply-To: <1381321077.27.0.332235799284.issue19203@psf.upfronthosting.co.za>
Message-ID: <1381321165.08.0.320760446544.issue19203@psf.upfronthosting.co.za>


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


Removed file: http://bugs.python.org/file32014/refs.curses-howto.patch

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

From report at bugs.python.org  Wed Oct  9 14:19:41 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 12:19:41 +0000
Subject: [docs] [issue19203] Improve cross-references in curses howto
In-Reply-To: <1381321077.27.0.332235799284.issue19203@psf.upfronthosting.co.za>
Message-ID: <1381321181.01.0.943249895693.issue19203@psf.upfronthosting.co.za>


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


Added file: http://bugs.python.org/file32015/refs.curses-howto.patch

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

From report at bugs.python.org  Wed Oct  9 14:27:22 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 12:27:22 +0000
Subject: [docs] [issue19204] Improve cross-references in urllib documentation
Message-ID: <1381321641.68.0.236509571307.issue19204@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the documentation of the urllib package.

----------
assignee: docs at python
components: Documentation
files: refs.urllib.patch
keywords: patch
messages: 199292
nosy: docs at python, orsenthil, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in urllib documentation
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32016/refs.urllib.patch

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

From report at bugs.python.org  Wed Oct  9 14:27:42 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 12:27:42 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381321662.5.0.676546011488.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Improve cross-references in urllib documentation

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

From report at bugs.python.org  Wed Oct  9 15:39:11 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 13:39:11 +0000
Subject: [docs] [issue19207] Improve cross-references in os documentation
Message-ID: <1381325950.91.0.175108750844.issue19207@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

Here is a patch which fixes internal references in the documentation of the os, os.path and posix modules.

----------
assignee: docs at python
components: Documentation
files: refs.os.patch
keywords: patch
messages: 199296
nosy: docs at python, loewis, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Improve cross-references in os documentation
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32018/refs.os.patch

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

From report at bugs.python.org  Wed Oct  9 15:40:35 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 13:40:35 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381326035.38.0.167359497382.issue18758@psf.upfronthosting.co.za>


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


----------
dependencies: +Improve cross-references in os documentation

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

From report at bugs.python.org  Wed Oct  9 15:51:13 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 13:51:13 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381326671.1.0.824649139104.issue18758@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

And here is a patch with small changes which doesn't worth separated issue.

----------
keywords: +patch
stage:  -> patch review
Added file: http://bugs.python.org/file32019/refs.patch

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

From report at bugs.python.org  Wed Oct  9 15:51:14 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 09 Oct 2013 13:51:14 +0000
Subject: [docs] [issue19200] grammar in forkserver docs
In-Reply-To: <1381271618.79.0.0617201422198.issue19200@psf.upfronthosting.co.za>
Message-ID: <3cvxfQ2kJkz7Ljv@mail.python.org>


Roundup Robot added the comment:

New changeset c0f3d18d79fd by Georg Brandl in branch 'default':
Closes #19200: small grammar fix in multiprocessing docs. Thanks to Elazar Gershuni.
http://hg.python.org/cpython/rev/c0f3d18d79fd

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

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

From report at bugs.python.org  Wed Oct  9 16:03:33 2013
From: report at bugs.python.org (Georg Brandl)
Date: Wed, 09 Oct 2013 14:03:33 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381327413.34.0.372397255103.issue18758@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Looks good, except that buffer doesn't really correspond to bytearray.  No memoryview involved there?

----------

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

From report at bugs.python.org  Wed Oct  9 16:13:23 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 09 Oct 2013 14:13:23 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381328003.6.0.959379740618.issue18758@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

No. BytesWarning is related only to bytes and bytearray.

----------

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

From report at bugs.python.org  Wed Oct  9 16:18:37 2013
From: report at bugs.python.org (Georg Brandl)
Date: Wed, 09 Oct 2013 14:18:37 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381328317.67.0.464645976034.issue18758@psf.upfronthosting.co.za>


Georg Brandl added the comment:

OK then -- so much the better.

----------

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

From report at bugs.python.org  Wed Oct  9 18:58:09 2013
From: report at bugs.python.org (Esa Peuha)
Date: Wed, 09 Oct 2013 16:58:09 +0000
Subject: [docs] [issue19202] Additions to docs
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381337889.61.0.891570498163.issue19202@psf.upfronthosting.co.za>


Esa Peuha added the comment:

How would you give a single definition of reduce() that helps people to understand both 2-arg and 3-arg variants? The way it is implemented in C is impossible to duplicate in pure Python; the best you could do is a hack that works unless someone *tries* to break it, but that would just be confusing.

----------

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

From report at bugs.python.org  Wed Oct  9 19:13:17 2013
From: report at bugs.python.org (Georg Brandl)
Date: Wed, 09 Oct 2013 17:13:17 +0000
Subject: [docs] [issue19202] Additions to docs
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381338797.18.0.352890402378.issue19202@psf.upfronthosting.co.za>


Georg Brandl added the comment:

What about

def reduce(function, iterable, initializer=None):
    it = iter(iterable)
    if initializer is None:
        value = next(it)
    else:
        value = initializer
    for element in it:
        value = function(value, element)
    return value

Remember, an equivalent doesn't have to be 100% compatible, it is a way for the user to quickly get an idea what the function does.

----------

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

From report at bugs.python.org  Wed Oct  9 22:04:10 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 09 Oct 2013 20:04:10 +0000
Subject: [docs] [issue16355] inspect.getcomments() does not work in the
	interactive	shell
In-Reply-To: <1351511930.82.0.59071323276.issue16355@psf.upfronthosting.co.za>
Message-ID: <1381349050.11.0.252817019187.issue16355@psf.upfronthosting.co.za>


R. David Murray added the comment:

Looking at the source, the suppression of errors is clearly intentional.  Looking at the change that added the TypeError check, we see this from Jeremy Hilton in March 2002 (9c2ca37bdeec):

    It appears that getcomments() can get called for classes defined in
    C.  Since these don't have source code, it can't do anything useful.
    A function buried many levels deep was raising a TypeError that was
    not caught.

    Who knows why this broke...

Which implies that getcomments was being called from somewhere in Python itself...at least back then.

The check for OSError (IOError, then) was from shortly after the module was first added, in February of 2001 by Ka-Ping Yee.

So, the motivation behind this behavior are shrouded in the mists of time :)

Should we really be changing something of that long standing, when it raising a TypeError previously clearly broke something?

I'm thinking not.  I'm thinking we should leave well enough alone.  It is, after all, working as documented....in the doc string, from the time Jeremy made the TypeError change.  So after all this work (sorry people, I do appreciate the work!), I think we should just make a doc fix that copies the line about returning None if source can't be found into the rst docs.

----------

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

From report at bugs.python.org  Thu Oct 10 00:45:36 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Wed, 09 Oct 2013 22:45:36 +0000
Subject: [docs] [issue18177] Incorect quote marks in code section-headers in
	PDF	version of docs
In-Reply-To: <1370829780.84.0.0627044566719.issue18177@psf.upfronthosting.co.za>
Message-ID: <1381358735.98.0.348172683756.issue18177@psf.upfronthosting.co.za>


Tshepang Lekhonkhobe added the comment:

A work-around: http://stackoverflow.com/a/16164658/321731.

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

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

From report at bugs.python.org  Thu Oct 10 01:06:01 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Wed, 09 Oct 2013 23:06:01 +0000
Subject: [docs] [issue16805] when building docs on Debian 7 --> ERROR: Error
	in	"note" directive
In-Reply-To: <1356739435.76.0.304211925624.issue16805@psf.upfronthosting.co.za>
Message-ID: <1381359961.92.0.3537677633.issue16805@psf.upfronthosting.co.za>


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


Removed file: http://bugs.python.org/file28482/remove-directives-warnings-3.2.diff

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

From report at bugs.python.org  Thu Oct 10 01:07:20 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Wed, 09 Oct 2013 23:07:20 +0000
Subject: [docs] [issue16805] when building docs on Debian 7 --> ERROR: Error
	in	"note" directive
In-Reply-To: <1356739435.76.0.304211925624.issue16805@psf.upfronthosting.co.za>
Message-ID: <1381360039.98.0.974303631246.issue16805@psf.upfronthosting.co.za>


Tshepang Lekhonkhobe added the comment:

BTW, these patches still apply, one to 2.7 and another to 3.3 and 3.4. They are pretty much harmless, so do not be afraid to accept them.

----------

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

From report at bugs.python.org  Thu Oct 10 10:04:24 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 10 Oct 2013 08:04:24 +0000
Subject: [docs] [issue15329] clarify which deque methods are thread-safe
In-Reply-To: <1342044644.52.0.376014623438.issue15329@psf.upfronthosting.co.za>
Message-ID: <1381392264.49.0.651682697503.issue15329@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> So, is deque a faster replacement for Queue.Queue or not?

Yes, it is faster.  The Queue module itself uses the deque internally.
  And the Queue is slowed down a bit through locks, function indirection, and additional features such as maxsize, join, and task_done.

The deque's append(), appendleft(), pop(), popleft(), and len(d) operations are thread-safe in CPython.   The append methods have a DECREF at the end (for cases where maxlen has been set), but this happens after all of the structure updates have been made and the invariants have been restored, so it is okay to treat these operations as atomic.

Closing this tracker item.

----------

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

From report at bugs.python.org  Thu Oct 10 10:36:07 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 10 Oct 2013 08:36:07 +0000
Subject: [docs] [issue15329] clarify which deque methods are thread-safe
In-Reply-To: <1342044644.52.0.376014623438.issue15329@psf.upfronthosting.co.za>
Message-ID: <1381394167.76.0.961173138526.issue15329@psf.upfronthosting.co.za>


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


----------
resolution:  -> invalid
status: open -> closed

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

From report at bugs.python.org  Thu Oct 10 17:57:21 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Thu, 10 Oct 2013 15:57:21 +0000
Subject: [docs] [issue16355] inspect.getcomments() does not work in the
	interactive	shell
In-Reply-To: <1351511930.82.0.59071323276.issue16355@psf.upfronthosting.co.za>
Message-ID: <1381420641.89.0.59474474679.issue16355@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

Only doc fix? What about unit test confirming that getcomments and getsource return None if inspect can not find the source code?

----------

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

From report at bugs.python.org  Thu Oct 10 18:14:22 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 10 Oct 2013 16:14:22 +0000
Subject: [docs] [issue16355] inspect.getcomments() does not work in the
	interactive	shell
In-Reply-To: <1351511930.82.0.59071323276.issue16355@psf.upfronthosting.co.za>
Message-ID: <1381421662.38.0.817824836812.issue16355@psf.upfronthosting.co.za>


R. David Murray added the comment:

Yes, good point, those tests should definitely be added, which means the test work doesn't go to waste :)

Note, however, that getsource *does* raise.

----------

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

From report at bugs.python.org  Thu Oct 10 21:44:21 2013
From: report at bugs.python.org (Vladimir Rutsky)
Date: Thu, 10 Oct 2013 19:44:21 +0000
Subject: [docs] [issue18243] mktime_tz documentation out-of-date
In-Reply-To: <1371482642.16.0.49381484414.issue18243@psf.upfronthosting.co.za>
Message-ID: <1381434261.29.0.42960725063.issue18243@psf.upfronthosting.co.za>


Changes by Vladimir Rutsky <altsysrq at gmail.com>:


----------
nosy: +rutsky

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

From report at bugs.python.org  Fri Oct 11 03:23:10 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 11 Oct 2013 01:23:10 +0000
Subject: [docs] [issue18177] Incorect quote marks in code section-headers in
	PDF	version of docs
In-Reply-To: <1370829780.84.0.0627044566719.issue18177@psf.upfronthosting.co.za>
Message-ID: <1381454590.16.0.560019091229.issue18177@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Should this be moved to the Sphinx bug tracker?

----------
nosy: +georg.brandl
status: open -> pending

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

From report at bugs.python.org  Fri Oct 11 12:02:57 2013
From: report at bugs.python.org (hiroaki itoh)
Date: Fri, 11 Oct 2013 10:02:57 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
Message-ID: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>


New submission from hiroaki itoh:

http://docs.python.org/2.7/c-api/exceptions.html#standard-exceptions

Python2.7 (at least 2.7.5) has PyExc_BufferError, but the document does not tell it.

----------
assignee: docs at python
components: Documentation
messages: 199458
nosy: docs at python, xwhhsprings
priority: normal
severity: normal
status: open
title: lack of PyExc_BufferError doc
type: behavior
versions: Python 2.7

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

From report at bugs.python.org  Fri Oct 11 12:19:24 2013
From: report at bugs.python.org (hiroaki itoh)
Date: Fri, 11 Oct 2013 10:19:24 +0000
Subject: [docs] [issue19225] lack of PyExc_BufferError doc
In-Reply-To: <1381485777.95.0.364414099437.issue19225@psf.upfronthosting.co.za>
Message-ID: <1381486764.0.0.620307040551.issue19225@psf.upfronthosting.co.za>


hiroaki itoh added the comment:

also:

* GeneratorExit
* StopIteration
* VMSError (#ifdef __VMS)
* UnboundLocalError
* IndentationError
* TabError
* UnicodeError
* UnicodeDecodeError
* UnicodeEncodeError
* UnicodeTranslateError

* Warning;
* UserWarning;
* DeprecationWarning;
* PendingDeprecationWarning;
* SyntaxWarning;
* RuntimeWarning;
* FutureWarning;
* ImportWarning;
* UnicodeWarning;
* BytesWarning;

Or, erase `For completeness, here are all the variables' statement...?

----------

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

From report at bugs.python.org  Fri Oct 11 18:26:12 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Fri, 11 Oct 2013 16:26:12 +0000
Subject: [docs] [issue19180] some RFC references could be updated
In-Reply-To: <525144B9.3040305@python.org>
Message-ID: <1381508772.49.0.623017509472.issue19180@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/issue19180>
_______________________________________

From report at bugs.python.org  Fri Oct 11 18:37:15 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 11 Oct 2013 16:37:15 +0000
Subject: [docs] [issue19180] some RFC references could be updated
In-Reply-To: <525144B9.3040305@python.org>
Message-ID: <1381509435.75.0.218493938099.issue19180@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

See also http://comments.gmane.org/gmane.comp.python.devel/139953 .

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

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

From report at bugs.python.org  Sat Oct 12 02:00:07 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 12 Oct 2013 00:00:07 +0000
Subject: [docs] [issue19179] doc bug: confusing table of values
In-Reply-To: <52514342.6020404@python.org>
Message-ID: <1381536007.61.0.0299619348018.issue19179@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I agree that this could be improved. It took a few readings to convince myself that True == Vulnerable. (Assuming that this is correct ;-) the table needs a title like Vulernable or a lead in sentence: "The following table indicates which modules are susceptible to which attacks."  Since True and False are names of Python objects, I would also prefer Yes and No or X and <blank> or '-'.

----------
nosy: +eli.bendersky, terry.reedy

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

From report at bugs.python.org  Sat Oct 12 02:14:02 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 12 Oct 2013 00:14:02 +0000
Subject: [docs] [issue19202] Additions to function docs: reduce and
	itertools.
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381536842.75.0.462890071564.issue19202@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I think the reduce equivalent given by Georg would be excellent.

I think the enumerate equivalent already given is fine because I think equivalents should use basic syntax (for loops), not something that might be more obscure.

----------
nosy: +terry.reedy
title: Additions to docs -> Additions to function docs: reduce and itertools.
versions: +Python 3.3

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

From report at bugs.python.org  Sat Oct 12 06:35:19 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sat, 12 Oct 2013 04:35:19 +0000
Subject: [docs] [issue16355] inspect.getcomments() does not work in the
	interactive	shell
In-Reply-To: <1351511930.82.0.59071323276.issue16355@psf.upfronthosting.co.za>
Message-ID: <1381552519.53.0.462753412327.issue16355@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

Added the doc fix and modified the test.

----------
Added file: http://bugs.python.org/file32057/issue16355_v3.diff

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

From report at bugs.python.org  Sat Oct 12 09:15:50 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 12 Oct 2013 07:15:50 +0000
Subject: [docs] [issue19202] Additions to function docs: reduce and
	itertools.
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381562150.42.0.755963104229.issue19202@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 12 09:20:14 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 12 Oct 2013 07:20:14 +0000
Subject: [docs] [issue19202] Additions to function docs: reduce and
	itertools.
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381562414.06.0.360830280669.issue19202@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Almost all of these make the docs worse and should not be applied.  The purpose of the "equivalent" code is simply to make the documentation clearer, not to show all the ways it could have been done.

I do think Georg's reduce() equivalent should be added because it is clearer than the current prose description.

----------

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

From report at bugs.python.org  Sat Oct 12 13:46:58 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 11:46:58 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
In-Reply-To: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>
Message-ID: <1381578418.84.0.469971646345.issue13203@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Suggestion attached.

----------
keywords: +patch
Added file: http://bugs.python.org/file32059/id_unique.diff

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

From report at bugs.python.org  Sat Oct 12 14:31:50 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 12 Oct 2013 12:31:50 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
In-Reply-To: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>
Message-ID: <1381581110.23.0.0493982262656.issue13203@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

LGTM

+ created and deleted during execution of the ``id()``

If you want to be more accurate you could say "before and after" instead of "during".

----------

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

From report at bugs.python.org  Sat Oct 12 14:53:13 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 12 Oct 2013 12:53:13 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381582393.12.0.425173311447.issue18758@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Here is a patch to Sphinx which helped me to search dead internal references. Not all references were fixed by proposed patches.

----------
Added file: http://bugs.python.org/file32061/sphinx_warn_refs.patch

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

From report at bugs.python.org  Sat Oct 12 18:13:49 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 12 Oct 2013 16:13:49 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
In-Reply-To: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>
Message-ID: <3cxrgc3LrDzSDW@mail.python.org>


Roundup Robot added the comment:

New changeset 8525cc1f342f by Georg Brandl in branch '2.7':
Closes #13203: add a FAQ section about seemingly duplicate id()s.
http://hg.python.org/cpython/rev/8525cc1f342f

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

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

From report at bugs.python.org  Sat Oct 12 18:14:53 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 12 Oct 2013 16:14:53 +0000
Subject: [docs] [issue13203] Doc: say id() is only useful for existing
	objects
In-Reply-To: <1318873835.36.0.466865504792.issue13203@psf.upfronthosting.co.za>
Message-ID: <3cxrhR35bxzSDW@mail.python.org>


Roundup Robot added the comment:

New changeset 0d5de993db66 by Georg Brandl in branch '3.3':
Closes #13203: add a FAQ section about seemingly duplicate id()s.
http://hg.python.org/cpython/rev/0d5de993db66

----------

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

From drazen.lucanin at gmail.com  Mon Oct  7 13:17:55 2013
From: drazen.lucanin at gmail.com (=?ISO-8859-2?Q?Dra=BEen_Lu=E8anin?=)
Date: Mon, 7 Oct 2013 13:17:55 +0200
Subject: [docs] Confusing default redirects
In-Reply-To: <525125F8.1010008@python.org>
References: <CADg_278+dmzttUKo+esTQMh+tCZDr0jG1-9_FXzXw3Ln-dMmaA@mail.gmail.com>
 <525125F8.1010008@python.org>
Message-ID: <CADg_278Dc_a0rw3TDuw4LWqJtF20EbCQ_qeAEuGesFL14V6wew@mail.gmail.com>

Hi Georg,

OK, I see. Still a bit confusing in my opinion, but I guess it's not so
important.

Cheers,
Dra?en


On Sun, Oct 6, 2013 at 10:57 AM, Georg Brandl <georg at python.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am 09.08.2013 19:21, schrieb Dra?en Lu?anin:
> > Dear Sir/Madam,
> >
> > When I open http://docs.python.org/ it redirects me to
> > http://docs.python.org/3/
> >
> > When I open http://docs.python.org/library/ it redirects me to
> > http://docs.python.org/2/library/
> >
> > Expected - all "versionless" URLs should redirect to the same (current
> > stable and recommended) version of Python.
>
> Hi Dra?en,
>
> this is intentional, see http://www.python.org/dev/peps/pep-0430/ for the
> details.
>
> cheers,
> Georg
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.21 (GNU/Linux)
>
> iEYEARECAAYFAlJRJfgACgkQN9GcIYhpnLAVkACfZlk4W5zuBwOMx8/znTaoY9mn
> FCIAoJW8Xu+Vrq673qInPQFa1yRsfeWA
> =7nZP
> -----END PGP SIGNATURE-----
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131007/7bc939fe/attachment-0001.html>

From reham.m.ayoub at gmail.com  Tue Oct  8 05:32:35 2013
From: reham.m.ayoub at gmail.com (Reham Mostafa)
Date: Tue, 8 Oct 2013 07:32:35 +0400
Subject: [docs] export TSV file
Message-ID: <CADPsXz3Q39sDNgnvjXHV2TQ0J4rjsxmQ9C9TQSpjFXY3yJhOug@mail.gmail.com>

Dear Sir,

I have TSV file and I want to export it as a FITS binary table. How to do
that.

Regards,
Reham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131008/d9ce3ddb/attachment-0001.html>

From rdmurray at bitdance.com  Wed Oct  9 21:49:08 2013
From: rdmurray at bitdance.com (rdmurray at bitdance.com)
Date: Wed, 09 Oct 2013 19:49:08 -0000
Subject: [docs] inspect.getcomments() does not work in the interactive shell
	(issue 16355)
Message-ID: <20131009194908.24133.71141@psf.upfronthosting.co.za>

I didn't review the tests because I got hung up on whether or not this
is a good idea at all when I looked at the source.

See tracker comments for more.


http://bugs.python.org/review/16355/diff/9453/Doc/library/inspect.rst
File Doc/library/inspect.rst (right):

http://bugs.python.org/review/16355/diff/9453/Doc/library/inspect.rst#newcode346
Doc/library/inspect.rst:346: the object is a built-in module, class or
function.
To stay parallel to the nearby text, this should read "This will fail
with an :exc:`OSError` if..."

http://bugs.python.org/review/16355/diff/9453/Doc/library/inspect.rst#newcode354
Doc/library/inspect.rst:354: 
This can be shortened to "Errors are raised as noted, where previously
``None`` was returned.

http://bugs.python.org/review/16355/

From vlado at poti.sk  Thu Oct 10 19:27:35 2013
From: vlado at poti.sk (Vlado Potisk)
Date: Thu, 10 Oct 2013 19:27:35 +0200
Subject: [docs] socket.fileno() documentation
Message-ID: <1984648.JD0MPFlghQ@noisy.pr41.sk>

I might be wrong but in my opinion the socket library documentation is not 
clear enough regarding the behaviour of the fileno() method in a case of a 
failure.

In the Python 3.2 socket library documentation there is:
----
exception socket.error

    A subclass of IOError, this exception is raised for socket-related errors. 
-----
 socket.close()

    Close the socket. All future operations on the socket object will fail.
----
 socket.fileno()

    Return the socket?s file descriptor (a small integer).
----

Based on the information quoted above, I wrote a test if a socket is active or 
if it has been closed already:

try:
	sock.fileno()
except socket.error:
	return False
return True

But is doesn't work. I have found out that fileno() returns -1 on a closed 
socket. Replacing fileno() with e.g. getsockname() fixes the code.

It looks like a fileno's failure - unlike to getsockname's failure - is not 
expressed by raising an exception, but by returning -1. However this seems to 
be not documented and that's why I'm unsure if I may rely on this.


From skip at pobox.com  Fri Oct 11 20:42:56 2013
From: skip at pobox.com (Skip Montanaro)
Date: Fri, 11 Oct 2013 13:42:56 -0500
Subject: [docs] datetime.strftime nits
Message-ID: <CANc-5UzQfMsRx=oa-=6xMk8sGBKFXEsv1Pr+RaJqCkv-rfcyxA@mail.gmail.com>

A small nit with the datetime.strftime documentation: "%s" (lower case
s) is mentioned in the table for format characters. I looked at the
2.7.5, 3.3, and development versions. All were missing this format
character.  Not sure when it was added, but it was there as far back
as (at least) 2.4. Even if it's not available everywhere (I only have
access to Solaris, Linux and Mac), it should be documented.

Thx

Skip

From report at bugs.python.org  Sat Oct 12 18:19:21 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 12 Oct 2013 16:19:21 +0000
Subject: [docs] [issue19179] doc bug: confusing table of values
In-Reply-To: <52514342.6020404@python.org>
Message-ID: <3cxrnb6ZPkz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 6b0ca3963ff1 by Georg Brandl in branch '3.3':
Closes #19179: make table of XML vulnerabilities clearer by using "everyday" booleans and explaining the table beforehand.
http://hg.python.org/cpython/rev/6b0ca3963ff1

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

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

From report at bugs.python.org  Sat Oct 12 18:19:29 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 12 Oct 2013 16:19:29 +0000
Subject: [docs] [issue19179] doc bug: confusing table of values
In-Reply-To: <52514342.6020404@python.org>
Message-ID: <3cxrnl3XFSz7Ljs@mail.python.org>


Roundup Robot added the comment:

New changeset 9aae58596349 by Georg Brandl in branch '2.7':
Closes #19179: make table of XML vulnerabilities clearer by using "everyday" booleans and explaining the table beforehand.
http://hg.python.org/cpython/rev/9aae58596349

----------

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

From report at bugs.python.org  Sat Oct 12 18:19:40 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 16:19:40 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381594780.74.0.124990857275.issue18758@psf.upfronthosting.co.za>


Georg Brandl added the comment:

The -n (nitpicky) option to Sphinx should also report missing references.

----------

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

From report at bugs.python.org  Sat Oct 12 18:20:50 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 16:20:50 +0000
Subject: [docs] [issue19202] Additions to function docs: reduce and
	itertools.
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381594850.81.0.770039137508.issue19202@psf.upfronthosting.co.za>


Georg Brandl added the comment:

What do you think of the two references added to the itertools docs?

----------

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

From georg at python.org  Sat Oct 12 18:23:43 2013
From: georg at python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 18:23:43 +0200
Subject: [docs] datetime.strftime nits
In-Reply-To: <CANc-5UzQfMsRx=oa-=6xMk8sGBKFXEsv1Pr+RaJqCkv-rfcyxA@mail.gmail.com>
References: <CANc-5UzQfMsRx=oa-=6xMk8sGBKFXEsv1Pr+RaJqCkv-rfcyxA@mail.gmail.com>
Message-ID: <5259778F.5040108@python.org>

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

Am 11.10.2013 20:42, schrieb Skip Montanaro:
> A small nit with the datetime.strftime documentation: "%s" (lower case s)
> is mentioned in the table for format characters. I looked at the 2.7.5,
> 3.3, and development versions. All were missing this format character.  Not
> sure when it was added, but it was there as far back as (at least) 2.4.
> Even if it's not available everywhere (I only have access to Solaris, Linux
> and Mac), it should be documented.

Hi Skip,

our policy has always been to only document the format codes available in
POSIX; %s does not seem to be POSIX-compliant.  (There is a sentence to
the effect that there may be additional non-portable codes available.)

We could of course change this, but it would require a survey of the
most used systems and a bit of effort.

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

iEYEARECAAYFAlJZd48ACgkQN9GcIYhpnLDcdgCfW0207OJW+Jd8n08Up3Fp9075
dWkAoK09TqC4MoxCQLpb0bKFMuGhck1P
=Wnyt
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sat Oct 12 18:24:10 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 16:24:10 +0000
Subject: [docs] [issue16355] inspect.getcomments() does not work in the
	interactive	shell
In-Reply-To: <1351511930.82.0.59071323276.issue16355@psf.upfronthosting.co.za>
Message-ID: <1381595050.31.0.56592326074.issue16355@psf.upfronthosting.co.za>


Georg Brandl added the comment:

"lives in the interactive shell" is not precise; I would prefer "has been defined in ...".

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

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

From report at bugs.python.org  Sat Oct 12 18:26:00 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 16:26:00 +0000
Subject: [docs] [issue18177] Incorect quote marks in code section-headers in
	PDF	version of docs
In-Reply-To: <1370829780.84.0.0627044566719.issue18177@psf.upfronthosting.co.za>
Message-ID: <1381595160.05.0.471070099703.issue18177@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Yes, there is already one or two issues there (e.g. number 1239).

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

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

From georg at python.org  Sat Oct 12 18:28:38 2013
From: georg at python.org (georg at python.org)
Date: Sat, 12 Oct 2013 16:28:38 -0000
Subject: [docs] Improve cross-references in os documentation (issue 19207)
Message-ID: <20131012162838.11221.25025@psf.upfronthosting.co.za>


http://bugs.python.org/review/19207/diff/9487/Doc/library/os.path.rst
File Doc/library/os.path.rst (right):

http://bugs.python.org/review/19207/diff/9487/Doc/library/os.path.rst#newcode274
Doc/library/os.path.rst:274: These structures may have been returned by
:func:`~os.fstat`, :func:`~os.lstat`, or
I think here it works even better without the tildes.

http://bugs.python.org/review/19207/diff/9487/Doc/library/os.rst
File Doc/library/os.rst (right):

http://bugs.python.org/review/19207/diff/9487/Doc/library/os.rst#newcode2777
Doc/library/os.rst:2777: functions.  If either of these values is given,
the :func:`spawn\* <spawnl>` functions
the second is not needed

http://bugs.python.org/review/19207/diff/9487/Doc/library/os.rst#newcode2787
Doc/library/os.rst:2787: functions.  If this is given as *mode*, the
:func:`spawn\* <spawnl>` functions will not
etc

http://bugs.python.org/review/19207/

From georg at python.org  Sat Oct 12 18:29:20 2013
From: georg at python.org (georg at python.org)
Date: Sat, 12 Oct 2013 16:29:20 -0000
Subject: [docs] Improve cross-references in urllib documentation (issue
	19204)
Message-ID: <20131012162920.11221.17367@psf.upfronthosting.co.za>

Looks good.

http://bugs.python.org/review/19204/

From georg at python.org  Sat Oct 12 18:29:52 2013
From: georg at python.org (georg at python.org)
Date: Sat, 12 Oct 2013 16:29:52 -0000
Subject: [docs] Improve cross-references in curses howto (issue 19203)
Message-ID: <20131012162952.11221.72507@psf.upfronthosting.co.za>

Looks good.

http://bugs.python.org/review/19203/

From georg at python.org  Sat Oct 12 18:30:28 2013
From: georg at python.org (georg at python.org)
Date: Sat, 12 Oct 2013 16:30:28 -0000
Subject: [docs] Improve cross-references in cgi documentation (issue 19198)
Message-ID: <20131012163028.11221.1321@psf.upfronthosting.co.za>

Looks good.

http://bugs.python.org/review/19198/

From georg at python.org  Sat Oct 12 18:31:32 2013
From: georg at python.org (georg at python.org)
Date: Sat, 12 Oct 2013 16:31:32 -0000
Subject: [docs] Improve cross-references in shlex documentation (issue 19197)
Message-ID: <20131012163132.11221.39872@psf.upfronthosting.co.za>


http://bugs.python.org/review/19197/diff/9477/Doc/library/shlex.rst
File Doc/library/shlex.rst (right):

http://bugs.python.org/review/19197/diff/9477/Doc/library/shlex.rst#newcode27
Doc/library/shlex.rst:27: (setting the :attr:`~shlex.shlex.commenters`
attribute of the
for all attributes, `~shlex.commenters` etc. should be enough.

http://bugs.python.org/review/19197/

From report at bugs.python.org  Sat Oct 12 18:33:57 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 16:33:57 +0000
Subject: [docs] [issue19234] socket.fileno() documentation
In-Reply-To: <1984648.JD0MPFlghQ@noisy.pr41.sk>
Message-ID: <52597A2F.60807@python.org>


New submission from Georg Brandl:

-------- Original-Nachricht --------
Betreff: [docs] socket.fileno() documentation
Datum: Thu, 10 Oct 2013 19:27:35 +0200
Von: Vlado Potisk <vlado at poti.sk>
An: docs at python.org

I might be wrong but in my opinion the socket library documentation is not
clear enough regarding the behaviour of the fileno() method in a case of a
failure.

In the Python 3.2 socket library documentation there is:
----
exception socket.error

    A subclass of IOError, this exception is raised for socket-related errors.
-----
 socket.close()

    Close the socket. All future operations on the socket object will fail.
----
 socket.fileno()

    Return the socket?s file descriptor (a small integer).
----

Based on the information quoted above, I wrote a test if a socket is active or
if it has been closed already:

try:
	sock.fileno()
except socket.error:
	return False
return True

But is doesn't work. I have found out that fileno() returns -1 on a closed
socket. Replacing fileno() with e.g. getsockname() fixes the code.

It looks like a fileno's failure - unlike to getsockname's failure - is not
expressed by raising an exception, but by returning -1. However this seems to
be not documented and that's why I'm unsure if I may rely on this.

----------
assignee: docs at python
components: Documentation
messages: 199592
nosy: docs at python, georg.brandl
priority: normal
severity: normal
status: open
title: socket.fileno() documentation

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

From report at bugs.python.org  Sat Oct 12 18:40:36 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 12 Oct 2013 16:40:36 +0000
Subject: [docs] [issue13026] Dis module - documentation of MAKE_FUNCTION
In-Reply-To: <1316642558.64.0.601129278503.issue13026@psf.upfronthosting.co.za>
Message-ID: <3cxsGW63LtzPXl@mail.python.org>


Roundup Robot added the comment:

New changeset b9ab48c491d5 by Georg Brandl in branch '3.3':
Closes #13026: fix documentation of MAKE_FUNCTION for 3.x.
http://hg.python.org/cpython/rev/b9ab48c491d5

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

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

From report at bugs.python.org  Sat Oct 12 18:41:44 2013
From: report at bugs.python.org (R. David Murray)
Date: Sat, 12 Oct 2013 16:41:44 +0000
Subject: [docs] [issue19234] socket.fileno() documentation
In-Reply-To: <52597A2F.60807@python.org>
Message-ID: <1381596104.78.0.835367268719.issue19234@psf.upfronthosting.co.za>


R. David Murray added the comment:

See also issue 19154.  For consistency with the rest of Python it should probably raise ValueError.  But at this point it has done what it does for a long time (which is to return what the underlying posix function returns), so we should probably just document it.

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

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

From report at bugs.python.org  Sat Oct 12 18:43:48 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 12 Oct 2013 16:43:48 +0000
Subject: [docs] [issue13905] Built-in Types Comparisons should mention
	rich	comparison methods
In-Reply-To: <1327867132.3.0.913390477966.issue13905@psf.upfronthosting.co.za>
Message-ID: <3cxsKp5lVHz7Ljk@mail.python.org>


Roundup Robot added the comment:

New changeset 9f1e1da820fb by Georg Brandl in branch '2.7':
Closes #13905: mention rich-comparison methods in addition to __cmp__ when documenting how to make classes comparable and orderable.
http://hg.python.org/cpython/rev/9f1e1da820fb

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

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

From report at bugs.python.org  Sat Oct 12 18:44:14 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 12 Oct 2013 16:44:14 +0000
Subject: [docs] [issue19202] Additions to function docs: reduce and
	itertools.
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381596254.94.0.375288742729.issue19202@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

The reference from accumulate() to reduce() may be useful.

I'm opposed to most of the other equivalents and cross-references.  They bloat the docs without adding value.  Terry is right in saying that the equivalent for enumerate() is better as a basic loop than as a composition of functional tools.   I think the OP has missed what the purpose of the code equivalents was trying to do.

----------

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

From senthil at uthcode.com  Sat Oct 12 18:48:00 2013
From: senthil at uthcode.com (senthil at uthcode.com)
Date: Sat, 12 Oct 2013 16:48:00 -0000
Subject: [docs] Improve cross-references in urllib documentation (issue
	19204)
Message-ID: <20131012164800.11221.40589@psf.upfronthosting.co.za>

Thanks. Everything  looks good.

http://bugs.python.org/review/19204/

From report at bugs.python.org  Sat Oct 12 18:51:52 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 16:51:52 +0000
Subject: [docs] [issue19202] Additions to function docs: reduce and
	itertools.
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381596712.8.0.849977286318.issue19202@psf.upfronthosting.co.za>


Georg Brandl added the comment:

I agree. Will prepare a patch to the reduce() doc.

----------

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

From report at bugs.python.org  Sat Oct 12 18:55:14 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 16:55:14 +0000
Subject: [docs] [issue19202] Additions to function docs: reduce and
	itertools.
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381596914.53.0.702266602685.issue19202@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


Added file: http://bugs.python.org/file32063/reduce_equiv.diff

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

From report at bugs.python.org  Sat Oct 12 19:02:58 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 12 Oct 2013 17:02:58 +0000
Subject: [docs] [issue13833] No documentation for PyStructSequence
In-Reply-To: <1327010174.09.0.407534369688.issue13833@psf.upfronthosting.co.za>
Message-ID: <3cxsmK4TzSz7Lk8@mail.python.org>


Roundup Robot added the comment:

New changeset 05dcaf761c7d by Georg Brandl in branch '3.3':
Closes #13833: document PyStructSequence C-API functions.
http://hg.python.org/cpython/rev/05dcaf761c7d

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

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

From report at bugs.python.org  Sat Oct 12 19:12:51 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 12 Oct 2013 17:12:51 +0000
Subject: [docs] [issue13915] Update tutorial/modules for PEP 3147
In-Reply-To: <1328053198.63.0.994035147287.issue13915@psf.upfronthosting.co.za>
Message-ID: <3cxszk3hYgzSyF@mail.python.org>


Roundup Robot added the comment:

New changeset 6ecef57f57f9 by Georg Brandl in branch '3.3':
Closes #13915: update tutorial with respect to .pyc files (__pycache__ / PEP 3147).
http://hg.python.org/cpython/rev/6ecef57f57f9

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

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

From report at bugs.python.org  Sat Oct 12 19:12:46 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 17:12:46 +0000
Subject: [docs] [issue13915] Update tutorial/modules for PEP 3147
In-Reply-To: <1328053198.63.0.994035147287.issue13915@psf.upfronthosting.co.za>
Message-ID: <1381597966.79.0.0947699578507.issue13915@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thanks for the suggestion!

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

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

From report at bugs.python.org  Sat Oct 12 20:31:50 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 18:31:50 +0000
Subject: [docs] [issue11233] clarifying Availability: Unix
In-Reply-To: <1297969399.53.0.187875867799.issue11233@psf.upfronthosting.co.za>
Message-ID: <1381602710.42.0.784812432645.issue11233@psf.upfronthosting.co.za>


Georg Brandl added the comment:

A draft is attached.  The directive currently just always links to the "availability" notes, which I have moved to the main "Operating system services" document.  Please review!

----------
keywords: +patch
Added file: http://bugs.python.org/file32065/availability-directive.patch

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

From skip at pobox.com  Sat Oct 12 21:18:46 2013
From: skip at pobox.com (Skip Montanaro)
Date: Sat, 12 Oct 2013 14:18:46 -0500
Subject: [docs] datetime.strftime nits
In-Reply-To: <5259778F.5040108@python.org>
References: <CANc-5UzQfMsRx=oa-=6xMk8sGBKFXEsv1Pr+RaJqCkv-rfcyxA@mail.gmail.com>
 <5259778F.5040108@python.org>
Message-ID: <CANc-5UyVqZedB3A95a+=vRPX=F6K87kBWJ5WyTVfgpvTXfyt9g@mail.gmail.com>

On Sat, Oct 12, 2013 at 11:23 AM, Georg Brandl <georg at python.org> wrote:
> our policy has always been to only document the format codes available in
> POSIX; %s does not seem to be POSIX-compliant.  (There is a sentence to
> the effect that there may be additional non-portable codes available.)
>
> We could of course change this, but it would require a survey of the
> most used systems and a bit of effort.

Georg,

Thanks for the reply. If you are only going to document some of the
format codes, I think it makes sense to document those which you can't
find elsewhere. If someone was to read the documentation, they
wouldn't learn about %s. Leaving it undocumented makes propagation of
this knowledge only possible by word-of-mouth or examination of
somebody's code. That also tends to foster a bit of a "high priest"
perspective. You're in on the secret or you're not.

Skip

From georg at python.org  Sat Oct 12 21:25:15 2013
From: georg at python.org (Georg Brandl)
Date: Sat, 12 Oct 2013 21:25:15 +0200
Subject: [docs] datetime.strftime nits
In-Reply-To: <CANc-5UyVqZedB3A95a+=vRPX=F6K87kBWJ5WyTVfgpvTXfyt9g@mail.gmail.com>
References: <CANc-5UzQfMsRx=oa-=6xMk8sGBKFXEsv1Pr+RaJqCkv-rfcyxA@mail.gmail.com>	<5259778F.5040108@python.org>
 <CANc-5UyVqZedB3A95a+=vRPX=F6K87kBWJ5WyTVfgpvTXfyt9g@mail.gmail.com>
Message-ID: <5259A21B.6040406@python.org>

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

Am 12.10.2013 21:18, schrieb Skip Montanaro:
> On Sat, Oct 12, 2013 at 11:23 AM, Georg Brandl <georg at python.org> wrote:
>> our policy has always been to only document the format codes available
>> in POSIX; %s does not seem to be POSIX-compliant.  (There is a sentence
>> to the effect that there may be additional non-portable codes
>> available.)
>> 
>> We could of course change this, but it would require a survey of the most
>> used systems and a bit of effort.

[s/POSIX/ANSI C/g]

> Georg,
> 
> Thanks for the reply. If you are only going to document some of the format
> codes, I think it makes sense to document those which you can't find
> elsewhere. If someone was to read the documentation, they wouldn't learn
> about %s. Leaving it undocumented makes propagation of this knowledge only
> possible by word-of-mouth or examination of somebody's code. That also
> tends to foster a bit of a "high priest" perspective. You're in on the
> secret or you're not.

Well, as I said, this is not because the other codes are secret, it is
because they are not portable.  Documenting them must necessarily either
spread (F)UD, or meticulously list the supporting platforms.  If someone
is willing to do the latter, it will not be rejected.

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

iEYEARECAAYFAlJZohsACgkQN9GcIYhpnLDJVgCghpOdhH/zSnGvEhaStf9FRS52
QNUAn1hy94GFgNjh7IANkwmtLkQh0zqg
=RTfL
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sat Oct 12 23:24:42 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 12 Oct 2013 21:24:42 +0000
Subject: [docs] [issue11233] clarifying Availability: Unix
In-Reply-To: <1297969399.53.0.187875867799.issue11233@psf.upfronthosting.co.za>
Message-ID: <1381613082.1.0.136663699833.issue11233@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I can't comment on the Sphinx extension code but this is a good idea.

----------

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

From report at bugs.python.org  Sun Oct 13 00:27:49 2013
From: report at bugs.python.org (David Chambers)
Date: Sat, 12 Oct 2013 22:27:49 +0000
Subject: [docs] [issue19238] Misleading explanation of fill and align in
	format_spec
Message-ID: <1381616869.75.0.196962613989.issue19238@psf.upfronthosting.co.za>


New submission from David Chambers:

>From http://docs.python.org/3/library/string.html#formatspec:

> The presence of a fill character is signaled by the character
> following it, which must be one of the alignment options. If the
> second character of format_spec is not a valid alignment option,
> then it is assumed that both the fill character and the alignment
> option are absent.

The fact that the second character in the format_spec is not an
alignment option is not sufficient to declare that the alignment
option is absent: the alignment option may be the first character
in the format_spec. For example:

    >>> '{:^10}'.format(42)
    '    42    '

I suggest the following wording:

The presence of a fill character is signaled by the character
following it, which must be one of the alignment options. Unless
the second character of format_spec is a valid alignment option,
the fill character is assumed to be absent.

----------
assignee: docs at python
components: Documentation
messages: 199633
nosy: davidchambers, docs at python
priority: normal
severity: normal
status: open
title: Misleading explanation of fill and align in format_spec

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

From skip at pobox.com  Sun Oct 13 01:02:53 2013
From: skip at pobox.com (Skip Montanaro)
Date: Sat, 12 Oct 2013 18:02:53 -0500
Subject: [docs] datetime.strftime nits
In-Reply-To: <5259A21B.6040406@python.org>
References: <CANc-5UzQfMsRx=oa-=6xMk8sGBKFXEsv1Pr+RaJqCkv-rfcyxA@mail.gmail.com>
 <5259778F.5040108@python.org>
 <CANc-5UyVqZedB3A95a+=vRPX=F6K87kBWJ5WyTVfgpvTXfyt9g@mail.gmail.com>
 <5259A21B.6040406@python.org>
Message-ID: <CANc-5Uy2_YWQr4qjnh2DbkhvRKa+8n8vRx3o2DQLJ7NsLPPMxQ@mail.gmail.com>

How about this modification? From this:

The full set of format codes supported varies across platforms,
because Python calls the platform C library?s strftime()function, and
platform variations are common.

to this:

The full set of format codes supported varies across platforms,
because Python calls the platform C library?s strftime()function, and
platform variations are common. To see the full set of format codes
supported on your platform, consult the strftime(3) documentation.

?

Skip

From report at bugs.python.org  Sun Oct 13 01:05:09 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 12 Oct 2013 23:05:09 +0000
Subject: [docs] [issue19202] Additions to function docs: reduce and
	itertools.
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <3cy1nq30zLz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 3b6401c27e39 by Raymond Hettinger in branch '3.3':
Issue #19202:  Add cross-reference and a rough code equivalent
http://hg.python.org/cpython/rev/3b6401c27e39

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

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

From report at bugs.python.org  Sun Oct 13 01:05:51 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Sat, 12 Oct 2013 23:05:51 +0000
Subject: [docs] [issue19202] Additions to function docs: reduce and
	itertools.
In-Reply-To: <1381313356.45.0.650070848794.issue19202@psf.upfronthosting.co.za>
Message-ID: <1381619151.18.0.77334444739.issue19202@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Thanks Georg.

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

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

From report at bugs.python.org  Sun Oct 13 01:31:20 2013
From: report at bugs.python.org (Ned Deily)
Date: Sat, 12 Oct 2013 23:31:20 +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: <1381620680.6.0.6738207905.issue19238@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Oct 13 02:51:38 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 13 Oct 2013 00:51:38 +0000
Subject: [docs] [issue19234] socket.fileno() documentation
In-Reply-To: <52597A2F.60807@python.org>
Message-ID: <1381625498.32.0.686521135823.issue19234@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Indeed, this should probably be documented as-is - or, if we want to change the behaviour, discussed on python-dev first.

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

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

From report at bugs.python.org  Sun Oct 13 05:52:40 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sun, 13 Oct 2013 03:52:40 +0000
Subject: [docs] [issue16355] inspect.getcomments() does not work in the
	interactive	shell
In-Reply-To: <1351511930.82.0.59071323276.issue16355@psf.upfronthosting.co.za>
Message-ID: <1381636360.8.0.0669915020803.issue16355@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

Attached the patch to address Georg Brandl's concern (Thank you!). I also added test for checking the comment of the object defined in C (list, open, etc). I have given thought about testing the comment of the object in interactive shell. But it is too much hassle. So I skip it.

----------
Added file: http://bugs.python.org/file32073/issue16355_v4.diff

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

From report at bugs.python.org  Sun Oct 13 10:01:56 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 08:01:56 +0000
Subject: [docs] [issue13744] raw byte strings are described in a confusing
	way
In-Reply-To: <1326116062.09.0.84789277908.issue13744@psf.upfronthosting.co.za>
Message-ID: <1381651316.89.0.0633503378687.issue13744@psf.upfronthosting.co.za>


Georg Brandl added the comment:

3.3 is now released with both "br" and "rb" allowed, and in 2.7 the current text looks good enough for me.

----------
nosy: +georg.brandl
resolution:  -> out of date
status: open -> closed

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

From report at bugs.python.org  Sun Oct 13 10:07:14 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 08:07:14 +0000
Subject: [docs] [issue14486] Add some versionchanged notes in threading docs
In-Reply-To: <1333501522.24.0.791616845298.issue14486@psf.upfronthosting.co.za>
Message-ID: <3cyFqJ74fDz7LjZ@mail.python.org>


Roundup Robot added the comment:

New changeset 81c28c415718 by Georg Brandl in branch '2.7':
Closes #14486: add versionchanged notices throughout the threading docs for PEP8-compliant APIs; the note at the top of the page is too hard to notice.
http://hg.python.org/cpython/rev/81c28c415718

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

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

From report at bugs.python.org  Sun Oct 13 10:14:55 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 08:14:55 +0000
Subject: [docs] [issue11120] threading.Thread.daemon Documentation Incomplete
In-Reply-To: <1296848896.87.0.703380092713.issue11120@psf.upfronthosting.co.za>
Message-ID: <1381652095.08.0.627892410695.issue11120@psf.upfronthosting.co.za>


Georg Brandl added the comment:

This is now fixed with changeset 81c28c415718.

----------
nosy: +georg.brandl
resolution:  -> fixed
status: open -> closed

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

From report at bugs.python.org  Sun Oct 13 10:23:06 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 08:23:06 +0000
Subject: [docs] [issue15829] Threading Lock - Wrong Exception Name
In-Reply-To: <1346406935.1.0.0548021295601.issue15829@psf.upfronthosting.co.za>
Message-ID: <3cyG9c33vNz7LkB@mail.python.org>


Roundup Robot added the comment:

New changeset d7e9c0a6dbcf by Georg Brandl in branch '2.7':
Closes #15829: document ThreadError and fix exception raised for releasing unlocked locks.
http://hg.python.org/cpython/rev/d7e9c0a6dbcf

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

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

From report at bugs.python.org  Sun Oct 13 10:23:54 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 08:23:54 +0000
Subject: [docs] [issue15829] Threading Lock - Wrong Exception Name
In-Reply-To: <1346406935.1.0.0548021295601.issue15829@psf.upfronthosting.co.za>
Message-ID: <1381652634.34.0.38729471567.issue15829@psf.upfronthosting.co.za>


Georg Brandl added the comment:

3.3 didn't need to be updated; it's RuntimeError there everywhere.

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

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

From report at bugs.python.org  Sun Oct 13 10:24:35 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 08:24:35 +0000
Subject: [docs] [issue14502] Document better what happens on releasing an
	unacquired	lock
In-Reply-To: <1333609616.9.0.633115743228.issue14502@psf.upfronthosting.co.za>
Message-ID: <1381652675.62.0.680261799813.issue14502@psf.upfronthosting.co.za>


Georg Brandl added the comment:

This is now fixed for 2.7 (see #15829); no fix needed for 3.3+.

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

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

From report at bugs.python.org  Sun Oct 13 10:43:38 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 08:43:38 +0000
Subject: [docs] [issue17375] Add docstrings to methods in the threading
	module
In-Reply-To: <1362648255.88.0.520762515957.issue17375@psf.upfronthosting.co.za>
Message-ID: <3cyGdJ4hVwz7Ljp@mail.python.org>


Roundup Robot added the comment:

New changeset 24429118988b by Georg Brandl in branch '3.3':
Closes #17375: port new threading docstrings from 2.7.
http://hg.python.org/cpython/rev/24429118988b

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

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

From report at bugs.python.org  Sun Oct 13 10:48:59 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 08:48:59 +0000
Subject: [docs] [issue13740] winsound.SND_NOWAIT ignored on modern Windows
	platforms
In-Reply-To: <1326059265.01.0.0567556069676.issue13740@psf.upfronthosting.co.za>
Message-ID: <3cyGlt2MV7z7LjY@mail.python.org>


Roundup Robot added the comment:

New changeset e08dea96b6e2 by Georg Brandl in branch '3.3':
Closes #13740: SND_NOWAIT seems to be ignored on modern Windows.
http://hg.python.org/cpython/rev/e08dea96b6e2

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

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

From report at bugs.python.org  Sun Oct 13 10:49:30 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 08:49:30 +0000
Subject: [docs] [issue13740] winsound.SND_NOWAIT ignored on modern Windows
	platforms
In-Reply-To: <1326059265.01.0.0567556069676.issue13740@psf.upfronthosting.co.za>
Message-ID: <3cyGm513Vxz7Lk6@mail.python.org>


Roundup Robot added the comment:

New changeset 3c8feb068694 by Georg Brandl in branch '2.7':
Closes #13740: SND_NOWAIT seems to be ignored on modern Windows.
http://hg.python.org/cpython/rev/3c8feb068694

----------

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

From report at bugs.python.org  Sun Oct 13 10:53:44 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 08:53:44 +0000
Subject: [docs] [issue16253] Docs for PyArg_ParseTupleAndKeywords say it
	doesn't	accept nested tuples
In-Reply-To: <1350415684.72.0.0946925077197.issue16253@psf.upfronthosting.co.za>
Message-ID: <1381654424.46.0.453065245924.issue16253@psf.upfronthosting.co.za>


Georg Brandl added the comment:

This sentence appears to be from the 1.5.2 docs; I can't find it anywhere else.

----------
nosy: +georg.brandl
resolution:  -> invalid
status: open -> closed

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

From report at bugs.python.org  Sun Oct 13 16:56:14 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 14:56:14 +0000
Subject: [docs] [issue17827] Document codecs.encode and codecs.decode
In-Reply-To: <1366811140.15.0.0983174574305.issue17827@psf.upfronthosting.co.za>
Message-ID: <3cyQvd4dt8z7LjX@mail.python.org>


Roundup Robot added the comment:

New changeset b607ce6c9ee6 by Nick Coghlan in branch '3.3':
Issue #17827: Document codecs.encode and codecs.decode
http://hg.python.org/cpython/rev/b607ce6c9ee6

New changeset 32f3d6721c84 by Nick Coghlan in branch 'default':
Issue #17827: document codecs.encode and codecs.decode
http://hg.python.org/cpython/rev/32f3d6721c84

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

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

From report at bugs.python.org  Sun Oct 13 17:05:57 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 13 Oct 2013 15:05:57 +0000
Subject: [docs] [issue17827] Document codecs.encode and codecs.decode
In-Reply-To: <1366811140.15.0.0983174574305.issue17827@psf.upfronthosting.co.za>
Message-ID: <1381676757.82.0.567017298807.issue17827@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Still need to backport this to 2.7

(Thanks for the preliminary patch Grant, but I'm afraid it didn't make it into what I ended up committing)

----------
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  Sun Oct 13 18:06:30 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 16:06:30 +0000
Subject: [docs] [issue19247] Describe surrogateescape algorithm in the
	Library	Reference
In-Reply-To: <1381673577.83.0.634006615694.issue19247@psf.upfronthosting.co.za>
Message-ID: <1381680390.61.0.116361243293.issue19247@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


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

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

From report at bugs.python.org  Sun Oct 13 18:20:18 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 16:20:18 +0000
Subject: [docs] [issue19198] Improve cross-references in cgi documentation
In-Reply-To: <1381266335.84.0.645626523869.issue19198@psf.upfronthosting.co.za>
Message-ID: <3cySmd1q2Pz7LjS@mail.python.org>


Roundup Robot added the comment:

New changeset 053eb1db0bf8 by Serhiy Storchaka in branch '2.7':
Issue #19198: Improved cross-references in the cgi module documentation.
http://hg.python.org/cpython/rev/053eb1db0bf8

New changeset e52e259d42e8 by Serhiy Storchaka in branch '3.3':
Issue #19198: Improved cross-references in the cgi module documentation.
http://hg.python.org/cpython/rev/e52e259d42e8

New changeset 781deb421ad0 by Serhiy Storchaka in branch 'default':
Issue #19198: Improved cross-references in the cgi module documentation.
http://hg.python.org/cpython/rev/781deb421ad0

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

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

From report at bugs.python.org  Sun Oct 13 18:20:40 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 16:20:40 +0000
Subject: [docs] [issue19203] Improve cross-references in curses howto
In-Reply-To: <1381321077.27.0.332235799284.issue19203@psf.upfronthosting.co.za>
Message-ID: <3cySmf0gdgz7LjS@mail.python.org>


Roundup Robot added the comment:

New changeset 54d422f5a5c6 by Serhiy Storchaka in branch '3.3':
Issue #19203: Improved cross-references in the curses howto.
http://hg.python.org/cpython/rev/54d422f5a5c6

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

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

From report at bugs.python.org  Sun Oct 13 18:25:07 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 16:25:07 +0000
Subject: [docs] [issue19203] Improve cross-references in curses howto
In-Reply-To: <1381321077.27.0.332235799284.issue19203@psf.upfronthosting.co.za>
Message-ID: <3cyStB3T73z7LjS@mail.python.org>


Roundup Robot added the comment:

New changeset 542f96b913ac by Serhiy Storchaka in branch 'default':
Issue #19203: Improved cross-references in the curses howto.
http://hg.python.org/cpython/rev/542f96b913ac

----------

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

From georg at python.org  Sun Oct 13 18:39:33 2013
From: georg at python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 18:39:33 +0200
Subject: [docs] datetime.strftime nits
In-Reply-To: <CANc-5Uy2_YWQr4qjnh2DbkhvRKa+8n8vRx3o2DQLJ7NsLPPMxQ@mail.gmail.com>
References: <CANc-5UzQfMsRx=oa-=6xMk8sGBKFXEsv1Pr+RaJqCkv-rfcyxA@mail.gmail.com>	<5259778F.5040108@python.org>	<CANc-5UyVqZedB3A95a+=vRPX=F6K87kBWJ5WyTVfgpvTXfyt9g@mail.gmail.com>	<5259A21B.6040406@python.org>
 <CANc-5Uy2_YWQr4qjnh2DbkhvRKa+8n8vRx3o2DQLJ7NsLPPMxQ@mail.gmail.com>
Message-ID: <525ACCC5.6040109@python.org>

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

Am 13.10.2013 01:02, schrieb Skip Montanaro:
> How about this modification? From this:
> 
> The full set of format codes supported varies across platforms, because
> Python calls the platform C library?s strftime()function, and platform
> variations are common.
> 
> to this:
> 
> The full set of format codes supported varies across platforms, because
> Python calls the platform C library?s strftime()function, and platform
> variations are common. To see the full set of format codes supported on
> your platform, consult the strftime(3) documentation.

+1, added it in all branches (and also in the time.strftime docs).

Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)

iEYEARECAAYFAlJazMUACgkQN9GcIYhpnLAnQwCeOVZuwfZtlJvmgztYdjJcZUCi
ByQAnjCPAWG/PZuXqNf6HSqPxXgPfB5g
=HEJ4
-----END PGP SIGNATURE-----

From report at bugs.python.org  Sun Oct 13 19:08:16 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 17:08:16 +0000
Subject: [docs] [issue19204] Improve cross-references in urllib documentation
In-Reply-To: <1381321641.68.0.236509571307.issue19204@psf.upfronthosting.co.za>
Message-ID: <3cyTqz6L84z7LjP@mail.python.org>


Roundup Robot added the comment:

New changeset 3901ff1e6547 by Serhiy Storchaka in branch '3.3':
Improve #19204: Improved cross-references in the urllib package documentation.
http://hg.python.org/cpython/rev/3901ff1e6547

New changeset b5bd28d39cf3 by Serhiy Storchaka in branch 'default':
Improve #19204: Improved cross-references in the urllib package documentation.
http://hg.python.org/cpython/rev/b5bd28d39cf3

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

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

From report at bugs.python.org  Sun Oct 13 19:14:32 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 17:14:32 +0000
Subject: [docs] [issue19207] Improve cross-references in os documentation
In-Reply-To: <1381325950.91.0.175108750844.issue19207@psf.upfronthosting.co.za>
Message-ID: <3cyTzC67TVz7LkJ@mail.python.org>


Roundup Robot added the comment:

New changeset 7ea984fc9be1 by Serhiy Storchaka in branch '3.3':
Issue #19207: Improved cross-references in the os, os.path, and posix modules
http://hg.python.org/cpython/rev/7ea984fc9be1

New changeset 74c3cf05fb1e by Serhiy Storchaka in branch 'default':
Issue #19207: Improved cross-references in the os, os.path, and posix modules
http://hg.python.org/cpython/rev/74c3cf05fb1e

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

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

From report at bugs.python.org  Sun Oct 13 19:26:20 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 17:26:20 +0000
Subject: [docs] [issue19207] Improve cross-references in os documentation
In-Reply-To: <1381325950.91.0.175108750844.issue19207@psf.upfronthosting.co.za>
Message-ID: <3cyVDq2LH3z7LjQ@mail.python.org>


Roundup Robot added the comment:

New changeset fd2c34e0104b by Serhiy Storchaka in branch '2.7':
Issue #19207: Improved cross-references in the os, os.path, and posix modules
http://hg.python.org/cpython/rev/fd2c34e0104b

----------

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

From report at bugs.python.org  Sun Oct 13 19:26:47 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2013 17:26:47 +0000
Subject: [docs] [issue19198] Improve cross-references in cgi documentation
In-Reply-To: <1381266335.84.0.645626523869.issue19198@psf.upfronthosting.co.za>
Message-ID: <1381685207.34.0.0456984751033.issue19198@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/issue19198>
_______________________________________

From report at bugs.python.org  Sun Oct 13 19:28:51 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2013 17:28:51 +0000
Subject: [docs] [issue19203] Improve cross-references in curses howto
In-Reply-To: <1381321077.27.0.332235799284.issue19203@psf.upfronthosting.co.za>
Message-ID: <1381685331.41.0.439040528778.issue19203@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I haven't applied patch to 2.7 because 2.7 and 3.3 are desynchronized enough. If anyone want update curses howto in 2.7 it should do this in separated issue.

----------

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

From report at bugs.python.org  Sun Oct 13 19:29:12 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2013 17:29:12 +0000
Subject: [docs] [issue19203] Improve cross-references in curses howto
In-Reply-To: <1381321077.27.0.332235799284.issue19203@psf.upfronthosting.co.za>
Message-ID: <1381685352.46.0.218831005814.issue19203@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Oct 13 19:42:53 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2013 17:42:53 +0000
Subject: [docs] [issue19204] Improve cross-references in urllib documentation
In-Reply-To: <1381321641.68.0.236509571307.issue19204@psf.upfronthosting.co.za>
Message-ID: <1381686173.22.0.734326938228.issue19204@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

I haven't applied the patch to 2.7 because in 2.7 urllib is totally different.

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

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

From report at bugs.python.org  Sun Oct 13 19:43:48 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2013 17:43:48 +0000
Subject: [docs] [issue19207] Improve cross-references in os documentation
In-Reply-To: <1381325950.91.0.175108750844.issue19207@psf.upfronthosting.co.za>
Message-ID: <1381686228.48.0.914045968213.issue19207@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/issue19207>
_______________________________________

From report at bugs.python.org  Sun Oct 13 19:56:31 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 17:56:31 +0000
Subject: [docs] [issue18512] sys.stdout.write does not allow bytes in Python
	3.x
In-Reply-To: <1374287481.36.0.643885131326.issue18512@psf.upfronthosting.co.za>
Message-ID: <1381686991.94.0.962169937952.issue18512@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


----------
resolution:  -> wont fix
status: pending -> closed

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

From report at bugs.python.org  Sun Oct 13 20:08:24 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 18:08:24 +0000
Subject: [docs] [issue18736] Invalid charset in HTML pages inside
	documentation in	CHM format
In-Reply-To: <1376481546.2.0.725412367622.issue18736@psf.upfronthosting.co.za>
Message-ID: <1381687704.51.0.556715620657.issue18736@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


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

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

From report at bugs.python.org  Sun Oct 13 20:21:19 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 18:21:19 +0000
Subject: [docs] [issue19197] Improve cross-references in shlex documentation
In-Reply-To: <1381266229.65.0.408303361922.issue19197@psf.upfronthosting.co.za>
Message-ID: <3cyWRs2bNhz7LjS@mail.python.org>


Roundup Robot added the comment:

New changeset bca5ba1ea5aa by Serhiy Storchaka in branch '2.7':
Issue #19197: Improved cross-references in the shlex module documentation.
http://hg.python.org/cpython/rev/bca5ba1ea5aa

New changeset 325fedff6178 by Serhiy Storchaka in branch '3.3':
Issue #19197: Improved cross-references in the shlex module documentation.
http://hg.python.org/cpython/rev/325fedff6178

New changeset dfbd5115fb95 by Serhiy Storchaka in branch 'default':
Issue #19197: Improved cross-references in the shlex module documentation.
http://hg.python.org/cpython/rev/dfbd5115fb95

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

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

From report at bugs.python.org  Sun Oct 13 20:23:29 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2013 18:23:29 +0000
Subject: [docs] [issue19197] Improve cross-references in shlex documentation
In-Reply-To: <1381266229.65.0.408303361922.issue19197@psf.upfronthosting.co.za>
Message-ID: <1381688609.96.0.649641339475.issue19197@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/issue19197>
_______________________________________

From report at bugs.python.org  Sun Oct 13 20:25:43 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2013 18:25:43 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381688743.08.0.49369279871.issue18758@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

> The -n (nitpicky) option to Sphinx should also report missing references.

Great.

----------

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

From georg at python.org  Sun Oct 13 20:29:35 2013
From: georg at python.org (georg at python.org)
Date: Sun, 13 Oct 2013 18:29:35 -0000
Subject: [docs] Improve cross-references in pickle documentation. (issue
	19189)
Message-ID: <20131013182935.10897.32439@psf.upfronthosting.co.za>


http://bugs.python.org/review/19189/diff/9465/Doc/library/pickle.rst
File Doc/library/pickle.rst (right):

http://bugs.python.org/review/19189/diff/9465/Doc/library/pickle.rst#newcode394
Doc/library/pickle.rst:394: calling :meth:`~.object.__getstate__` is
picklable  (see section
~object. should never be needed for methods.

These appear to be false positives.

http://bugs.python.org/review/19189/

From report at bugs.python.org  Sun Oct 13 21:09:31 2013
From: report at bugs.python.org (Nick Guenther)
Date: Sun, 13 Oct 2013 19:09:31 +0000
Subject: [docs] [issue19248] sphinx is not py3k compatible
Message-ID: <1381691371.24.0.619813163861.issue19248@psf.upfronthosting.co.za>


New submission from Nick Guenther:

I'm running Arch. I just checked out python's hg and tried to build the docs, and found that I couldn't:

$ cd cpython/doc
$ make update
[lots of output stripped]
$ make pydoc-topics
mkdir -p build/pydoc-topics build/doctrees
python tools/sphinx-build.py -b pydoc-topics -d build/doctrees -D latex_paper_size=  . build/pydoc-topics 
Traceback (most recent call last):
  File "tools/sphinx-build.py", line 27, in <module>
    from sphinx import main
  File "/home/kousu/pro/cpython/Doc/tools/sphinx/__init__.py", line 44
    except ImportError, err:
                      ^
SyntaxError: invalid syntax
make: *** [build] Error 1

I edited the Makefile to say PYTHON       = python2
and then it worked. Is the assumption that python2 is still supposed to be the default python everywhere? Is python 3 not able to build itself yet?



[kousu at galleon Doc]$ pacman -Qi python
Name           : python
Version        : 3.3.2-2
Description    : Next generation of the python high-level scripting language
Architecture   : x86_64
URL            : http://www.python.org/
Licenses       : custom
Groups         : None
Provides       : python3
Depends On     : expat  bzip2  gdbm  openssl  libffi  zlib
Optional Deps  : tk: for tkinter [installed]
                 sqlite [installed]
Required By    : cython  ipython  ktoblzcheck  libreoffice-common  python-cairo  python-dateutil  python-dbus  python-markupsafe
                 python-numpy  python-pyparsing  python-pytz  python-pyzmq  python-setuptools  python-sip  python-six  python-sympy
                 python-tornado  python-xdg  ranger  youtube-dl
Optional For   : systemd
Conflicts With : None
Replaces       : python3
Installed Size : 86980.00 KiB
Packager       : Bart
Build Date     : Fri Sep 6 03:31:57 2013
Install Date   : Tue Sep 17 10:29:36 2013
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By   : Signature

----------
assignee: docs at python
components: Documentation
messages: 199764
nosy: docs at python, kousu
priority: normal
severity: normal
status: open
title: sphinx is not py3k compatible
versions: Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Sun Oct 13 21:11:21 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 13 Oct 2013 19:11:21 +0000
Subject: [docs] [issue19248] sphinx is not py3k compatible
In-Reply-To: <1381691371.24.0.619813163861.issue19248@psf.upfronthosting.co.za>
Message-ID: <1381691481.23.0.0113859204249.issue19248@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

This is a duplicate of #10224.

----------
nosy: +ezio.melotti
resolution:  -> duplicate
stage:  -> committed/rejected
status: open -> closed
superseder:  -> Build 3.x documentation using python3.x
type:  -> enhancement

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

From report at bugs.python.org  Sun Oct 13 21:19:33 2013
From: report at bugs.python.org (Nick Guenther)
Date: Sun, 13 Oct 2013 19:19:33 +0000
Subject: [docs] [issue19248] sphinx is not py3k compatible
In-Reply-To: <1381691371.24.0.619813163861.issue19248@psf.upfronthosting.co.za>
Message-ID: <1381691973.51.0.461927409857.issue19248@psf.upfronthosting.co.za>


Nick Guenther added the comment:

I see that in Doc/tools/sphinx-build.py there is this check:

    if sys.version_info[:3] < (2, 4, 0):
        sys.stderr.write("""\
Error: Sphinx needs to be executed with Python 2.4 or newer (not 3.0 though).
(If you run this from the Makefile, you can set the PYTHON variable
to the path of an alternative interpreter executable, e.g.,
``make html PYTHON=python2.5``).
""")

But I never saw this and had to debug it myself. I submit the attached patch as a solution.

----------
keywords: +patch
resolution: duplicate -> 
status: closed -> open
type: enhancement -> 
Added file: http://bugs.python.org/file32093/sphinx_version_check.patch

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

From report at bugs.python.org  Sun Oct 13 21:22:29 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 19:22:29 +0000
Subject: [docs] [issue19248] sphinx is not py3k compatible
In-Reply-To: <1381691371.24.0.619813163861.issue19248@psf.upfronthosting.co.za>
Message-ID: <1381692149.44.0.0409309113013.issue19248@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Looks ok for now.

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

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

From report at bugs.python.org  Sun Oct 13 21:40:35 2013
From: report at bugs.python.org (Nick Guenther)
Date: Sun, 13 Oct 2013 19:40:35 +0000
Subject: [docs] [issue19250] Duplicate import documentation in py3k
Message-ID: <1381693235.0.0.590158180035.issue19250@psf.upfronthosting.co.za>


New submission from Nick Guenther:

Python3's docs given by
>> help("import")

duplicate these two paragraphs:
"The *public names* defined by a module are determined by checking the
module's namespace for a variable named ``__all__``; if defined, it
must be a sequence of strings which are names defined or imported by
that module.  The names given in ``__all__`` are all considered public
and are required to exist.  If ``__all__`` is not defined, the set of
public names includes all names found in the module's namespace which
do not begin with an underscore character (``'_'``).  ``__all__``
should contain the entire public API. It is intended to avoid
accidentally exporting items that are not part of the API (such as
library modules which were imported and used within the module).

The ``from`` form with ``*`` may only occur in a module scope.
Attempting to use it in class or function definitions will raise a
``SyntaxError``."

(full output attached for proof)

Digging through the sources, I can't find where this is defined. The python2 on my system has the same two paragraphs but they are *not* duplicated there, and in the sources, which admittedly I don't know my way around, Doc/reference/simple_stmts.rst contains these paragraphs but only once each, and grep seems to imply this is the source of them.

Did sphinx screw up somewhere between your hg and my distro mirror?

Here's my version info (arch linux, 64 bit)
[kousu at galleon ~]$ pacman -Qi python
Name           : python
Version        : 3.3.2-2
Description    : Next generation of the python high-level scripting language
Architecture   : x86_64
URL            : http://www.python.org/
Licenses       : custom
Groups         : None
Provides       : python3
Depends On     : expat  bzip2  gdbm  openssl  libffi  zlib
Optional Deps  : tk: for tkinter [installed]
                 sqlite [installed]
Required By    : cython  ipython  ktoblzcheck  libreoffice-common  python-cairo  python-dateutil  python-dbus  python-markupsafe
                 python-numpy  python-pyparsing  python-pytz  python-pyzmq  python-setuptools  python-sip  python-six  python-sympy
                 python-tornado  python-xdg  ranger  youtube-dl
Optional For   : systemd
Conflicts With : None
Replaces       : python3
Installed Size : 86980.00 KiB
Packager       : Bart
Build Date     : Fri Sep 6 03:31:57 2013
Install Date   : Tue Sep 17 10:29:36 2013
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By   : Signature

----------
assignee: docs at python
components: Documentation
files: The ``import`` statement - (2013-10-13 15:36:07)
messages: 199775
nosy: docs at python, kousu
priority: normal
severity: normal
status: open
title: Duplicate import documentation in py3k
versions: Python 3.3
Added file: http://bugs.python.org/file32096/The ``import`` statement - (2013-10-13 15:36:07)

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

From report at bugs.python.org  Sun Oct 13 21:46:44 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 13 Oct 2013 19:46:44 +0000
Subject: [docs] [issue19250] Duplicate import documentation in py3k
In-Reply-To: <1381693235.0.0.590158180035.issue19250@psf.upfronthosting.co.za>
Message-ID: <1381693604.35.0.61215738439.issue19250@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I can reproduce on 3.3; looks OK on 3.4.

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

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

From report at bugs.python.org  Sun Oct 13 22:01:05 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 20:01:05 +0000
Subject: [docs] [issue19250] Duplicate import documentation in py3k
In-Reply-To: <1381693235.0.0.590158180035.issue19250@psf.upfronthosting.co.za>
Message-ID: <1381694465.52.0.833998072569.issue19250@psf.upfronthosting.co.za>


Georg Brandl added the comment:

This is already fixed in the 3.3 branch (see #17938); it will be updated for pydoc "automatically" before the next bugfix release (the actual content comes from Lib/pydoc_data/topics.py).

----------
nosy: +georg.brandl
resolution:  -> fixed
status: open -> closed

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

From report at bugs.python.org  Sun Oct 13 22:02:17 2013
From: report at bugs.python.org (Nick Guenther)
Date: Sun, 13 Oct 2013 20:02:17 +0000
Subject: [docs] [issue19250] Duplicate import documentation in py3k
In-Reply-To: <1381693235.0.0.590158180035.issue19250@psf.upfronthosting.co.za>
Message-ID: <1381694537.72.0.380322079192.issue19250@psf.upfronthosting.co.za>


Nick Guenther added the comment:

Thank you. Sorry for the duplicates. I tried to search the bug tracker but nothing stood out to me.

----------

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

From report at bugs.python.org  Sun Oct 13 22:16:56 2013
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 13 Oct 2013 20:16:56 +0000
Subject: [docs] [issue17352] Be clear that __prepare__ must be declared as a
	class	method
In-Reply-To: <1362409892.83.0.717786566871.issue17352@psf.upfronthosting.co.za>
Message-ID: <1381695416.14.0.00730893817108.issue17352@psf.upfronthosting.co.za>


Changes by Georg Brandl <georg at python.org>:


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

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

From report at bugs.python.org  Sun Oct 13 22:19:42 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 20:19:42 +0000
Subject: [docs] [issue19248] sphinx is not py3k compatible
In-Reply-To: <1381691371.24.0.619813163861.issue19248@psf.upfronthosting.co.za>
Message-ID: <3cyZ4S51n1zS2g@mail.python.org>


Roundup Robot added the comment:

New changeset 6e65ee2a0073 by Georg Brandl in branch '3.3':
Closes #19248: actually check for Python 3.x in tools/sphinx-build.py.
http://hg.python.org/cpython/rev/6e65ee2a0073

----------
nosy: +python-dev
resolution:  -> fixed
status: open -> closed

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

From report at bugs.python.org  Sun Oct 13 22:35:00 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 13 Oct 2013 20:35:00 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <3cyZQW727Bz7Ljc@mail.python.org>


Roundup Robot added the comment:

New changeset fa7cfbec0d32 by Serhiy Storchaka in branch '2.7':
Issue #18758: Fixed and improved cross-references.
http://hg.python.org/cpython/rev/fa7cfbec0d32

New changeset 907da535ed9d by Serhiy Storchaka in branch '3.3':
Issue #18758: Fixed and improved cross-references.
http://hg.python.org/cpython/rev/907da535ed9d

New changeset 261d9bf0cc2b by Serhiy Storchaka in branch 'default':
Issue #18758: Fixed and improved cross-references.
http://hg.python.org/cpython/rev/261d9bf0cc2b

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

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

From report at bugs.python.org  Sun Oct 13 22:42:23 2013
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Sun, 13 Oct 2013 20:42:23 +0000
Subject: [docs] [issue19248] sphinx is not py3k compatible
In-Reply-To: <1381691371.24.0.619813163861.issue19248@psf.upfronthosting.co.za>
Message-ID: <1381696943.76.0.139241598968.issue19248@psf.upfronthosting.co.za>


Arfrever Frehtes Taifersar Arahesis added the comment:

> Is the assumption that python2 is still supposed to be the default python everywhere?
> Is python 3 not able to build itself yet?

You can manually install Sphinx >=1.1 (preferably >=1.2.*) (and its dependencies) using Python 3, and directly call `sphinx-build` from so installed Sphinx, instead of using `make`.

----------
nosy: +Arfrever

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

From report at bugs.python.org  Sun Oct 13 22:48:39 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 13 Oct 2013 20:48:39 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381697319.48.0.131567143647.issue18758@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you Georg for all your reviews.

Only patch for pickle left, and this is not trivial one.

----------
resolution:  -> fixed
stage: patch review -> committed/rejected

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

From storchaka at gmail.com  Sun Oct 13 23:07:18 2013
From: storchaka at gmail.com (storchaka at gmail.com)
Date: Sun, 13 Oct 2013 21:07:18 -0000
Subject: [docs] Improve cross-references in pickle documentation. (issue
	19189)
Message-ID: <20131013210718.10891.94659@psf.upfronthosting.co.za>

Reviewers: Georg,


http://bugs.python.org/review/19189/diff/9465/Doc/library/pickle.rst
File Doc/library/pickle.rst (right):

http://bugs.python.org/review/19189/diff/9465/Doc/library/pickle.rst#newcode394
Doc/library/pickle.rst:394: calling :meth:`~.object.__getstate__` is
picklable  (see section
On 2013/10/13 20:29:35, Georg wrote:
> ~object. should never be needed for methods.
> 
> These appear to be false positives.

Here is not "~object." but "~.object.". These methods are declared in
the "." module (see line 438 below). Do you know how declare empty
module?



Please review this at http://bugs.python.org/review/19189/

Affected files:
  Doc/library/pickle.rst



From georg at python.org  Sun Oct 13 23:13:12 2013
From: georg at python.org (georg at python.org)
Date: Sun, 13 Oct 2013 21:13:12 -0000
Subject: [docs] Improve cross-references in pickle documentation. (issue
	19189)
Message-ID: <20131013211312.10897.28379@psf.upfronthosting.co.za>


http://bugs.python.org/review/19189/diff/9465/Doc/library/pickle.rst
File Doc/library/pickle.rst (right):

http://bugs.python.org/review/19189/diff/9465/Doc/library/pickle.rst#newcode394
Doc/library/pickle.rst:394: calling :meth:`~.object.__getstate__` is
picklable  (see section
On 2013/10/13 23:07:18, storchaka wrote:
> On 2013/10/13 20:29:35, Georg wrote:
> > ~object. should never be needed for methods.
> > 
> > These appear to be false positives.
> 
> Here is not "~object." but "~.object.". These methods are declared in
the "."
> module (see line 438 below). Do you know how declare empty module?


Yes, use ``.. currentmodule:: None``.

http://bugs.python.org/review/19189/

From report at bugs.python.org  Mon Oct 14 04:32:17 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 14 Oct 2013 02:32:17 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
	without	explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1381717937.74.0.612913657278.issue14112@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Here is a patch that adds glossary entries for deep and shallow copy.  I tried to keep them simple and clear enough.

FWIW http://docs.python.org/3.4/library/copy.html also has a definition of the terms.

If my definitions are OK I will add links to the terms were appropriate.

----------
keywords: +patch
nosy: +georg.brandl
stage:  -> patch review
type:  -> enhancement
versions: +Python 3.4 -Python 3.2
Added file: http://bugs.python.org/file32107/issue14112.diff

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

From report at bugs.python.org  Mon Oct 14 06:30:34 2013
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 14 Oct 2013 04:30:34 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
	without	explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1381725034.04.0.370845128705.issue14112@psf.upfronthosting.co.za>


Georg Brandl added the comment:

The text talks about containers which, although often the case, is not general enough; copy() and deepcopy() can work with any object.

----------

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

From storchaka at gmail.com  Mon Oct 14 09:31:24 2013
From: storchaka at gmail.com (storchaka at gmail.com)
Date: Mon, 14 Oct 2013 07:31:24 -0000
Subject: [docs] Improve cross-references in pickle documentation. (issue
	19189)
Message-ID: <20131014073124.10891.31301@psf.upfronthosting.co.za>


http://bugs.python.org/review/19189/diff/9465/Doc/library/pickle.rst
File Doc/library/pickle.rst (right):

http://bugs.python.org/review/19189/diff/9465/Doc/library/pickle.rst#newcode394
Doc/library/pickle.rst:394: calling :meth:`~.object.__getstate__` is
picklable  (see section
On 2013/10/13 23:13:12, Georg wrote:
> On 2013/10/13 23:07:18, storchaka wrote:
> > On 2013/10/13 20:29:35, Georg wrote:
> > > ~object. should never be needed for methods.
> > > 
> > > These appear to be false positives.
> > 
> > Here is not "~object." but "~.object.". These methods are declared
in the "."
> > module (see line 438 below). Do you know how declare empty module?
> 
> 
> Yes, use ``.. currentmodule:: None``.

Thank you. This will made the patch much better.

http://bugs.python.org/review/19189/

From report at bugs.python.org  Mon Oct 14 09:44:57 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 14 Oct 2013 07:44:57 +0000
Subject: [docs] [issue19189] Improve cross-references in pickle
	documentation.
In-Reply-To: <1381178353.55.0.131251765353.issue19189@psf.upfronthosting.co.za>
Message-ID: <3cysHX3Cn1z7LjQ@mail.python.org>


Roundup Robot added the comment:

New changeset c99a3566be83 by Serhiy Storchaka in branch '2.7':
Issue #19189: Improved cross-references in the pickle module documentation.
http://hg.python.org/cpython/rev/c99a3566be83

New changeset f2c725fb4b2f by Serhiy Storchaka in branch '3.3':
Issue #19189: Improved cross-references in the pickle module documentation.
http://hg.python.org/cpython/rev/f2c725fb4b2f

New changeset 37c06d20dda5 by Serhiy Storchaka in branch 'default':
Issue #19189: Improved cross-references in the pickle module documentation.
http://hg.python.org/cpython/rev/37c06d20dda5

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

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

From report at bugs.python.org  Mon Oct 14 09:49:42 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 14 Oct 2013 07:49:42 +0000
Subject: [docs] [issue19189] Improve cross-references in pickle
	documentation.
In-Reply-To: <1381178353.55.0.131251765353.issue19189@psf.upfronthosting.co.za>
Message-ID: <1381736982.57.0.516722810945.issue19189@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you Georg for your review and for your suggestion.

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

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

From report at bugs.python.org  Mon Oct 14 09:49:57 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 14 Oct 2013 07:49:57 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381736997.95.0.315067636001.issue18758@psf.upfronthosting.co.za>


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


----------
status: open -> closed

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

From report at bugs.python.org  Mon Oct 14 18:04:52 2013
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 14 Oct 2013 16:04:52 +0000
Subject: [docs] [issue18758] Fix internal references in the documentation
In-Reply-To: <1376678338.7.0.979265810368.issue18758@psf.upfronthosting.co.za>
Message-ID: <1381766692.44.0.934343527146.issue18758@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Thank you for all the effort you put into this!

----------

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

From report at bugs.python.org  Tue Oct 15 02:44:16 2013
From: report at bugs.python.org (Tyler B)
Date: Tue, 15 Oct 2013 00:44:16 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1381797856.38.0.221281106816.issue19184@psf.upfronthosting.co.za>


Tyler B added the comment:

Looked at the code and found differences between 3.4 and 2.7. 2.7 has 3 exceptions that can be raised while 3.4 has 4 exceptions. 

I propose removing the "list of parameters" from the documenation to keep things simple and not repeat the code. 

# 2.7
"Raises an exception. argc indicates the number of parameters to the raise statement, ranging from 0 to 3. The parameters consist of the traceback as TOS1, the value as TOS2, the exception as TOS3, and None as TOS4."

# 3.4  
"Raises an exception. argc indicates the number of parameters to the raise statement, ranging from 0 to 2. The parameters consist of the cause as TOS1, the exception as TOS2, and None as TOS3."

How does this sound?

----------
nosy: +Tyler.B

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

From report at bugs.python.org  Tue Oct 15 11:03:51 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Tue, 15 Oct 2013 09:03:51 +0000
Subject: [docs] [issue17221] Resort Misc/NEWS
In-Reply-To: <1361135741.75.0.253129131493.issue17221@psf.upfronthosting.co.za>
Message-ID: <1381827831.82.0.83439528721.issue17221@psf.upfronthosting.co.za>


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


----------
status: closed -> open

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

From report at bugs.python.org  Tue Oct 15 11:06:55 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 15 Oct 2013 09:06:55 +0000
Subject: [docs] [issue17221] Resort Misc/NEWS
In-Reply-To: <1361135741.75.0.253129131493.issue17221@psf.upfronthosting.co.za>
Message-ID: <3czW3f5CRdz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 484ce82b7873 by Serhiy Storchaka in branch 'default':
Issue #17221: Merge 3.4.0 Alpha 1 entries before and after 3.3.1 release candidate 1.
http://hg.python.org/cpython/rev/484ce82b7873

----------

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

From report at bugs.python.org  Tue Oct 15 12:24:53 2013
From: report at bugs.python.org (Tyler B)
Date: Tue, 15 Oct 2013 10:24:53 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1381832693.62.0.501698027773.issue19184@psf.upfronthosting.co.za>


Tyler B added the comment:

I wanted to make an edit so here's my revised comment:

Looked at the code and found differences between 3.4 and 2.7. 2.7 has 4 exceptions that can be raised while 3.4 has 3 exceptions. 

I propose removing the "list of parameters" from the documenation to keep things simple and not repeat the code. 

# 2.7
"Raises an exception. argc indicates the number of parameters to the raise statement, ranging from 0 to 3. The parameters consist of the traceback as TOS1, the value as TOS2, the exception as TOS3, and None as TOS4."

# 3.4  
"Raises an exception. argc indicates the number of parameters to the raise statement, ranging from 0 to 2. The parameters consist of the cause as TOS1, the exception as TOS2, and None as TOS3."

How does this sound?

----------

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

From report at bugs.python.org  Tue Oct 15 12:37:13 2013
From: report at bugs.python.org (Tyler B)
Date: Tue, 15 Oct 2013 10:37:13 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1381833433.85.0.310576252915.issue19184@psf.upfronthosting.co.za>


Tyler B added the comment:

One last edit:

Looked at the code and found differences between 3.4 and 2.7. 2.7 has 4 exceptions that can be raised while 3.4 has 3 exceptions. 

I propose including the full list of parameters but describing the exceptions in a way that's less specific about the TOS order to keep the documentation as simple as possible.   

# 2.7
"Raises an exception. argc indicates the number of parameters to the raise statement, ranging from 0 to 3. The parameters can consist of the traceback as TOS1, the value as TOS2, the exception as TOS3, and None as TOS4."

# 3.4  
"Raises an exception. argc indicates the number of parameters to the raise statement, ranging from 0 to 2. The parameters can consist of the cause as TOS1, the exception as TOS2, and None as TOS3."

How does this sound?

----------

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

From report at bugs.python.org  Tue Oct 15 13:32:38 2013
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 15 Oct 2013 11:32:38 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1381836758.89.0.671351190459.issue19184@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Tyler, thanks for the suggestion.  However it doesn't really solve the issue: the parameter order is the opposite of the current doc text (and your suggested text).

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

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

From report at bugs.python.org  Wed Oct 16 02:50:11 2013
From: report at bugs.python.org (Tyler B)
Date: Wed, 16 Oct 2013 00:50:11 +0000
Subject: [docs] [issue19184] dis module has incorrect docs for RAISE_VARARGS
In-Reply-To: <1381078012.05.0.236677780468.issue19184@psf.upfronthosting.co.za>
Message-ID: <1381884610.87.0.887747400998.issue19184@psf.upfronthosting.co.za>


Tyler B added the comment:

Here's a revised suggestion that has the order changed. I have additional concerns but please provide comment on this revision. Thanks

# 2.7
"Raises an exception. argc indicates the number of parameters to the raise statement, ranging from 0 to 3. The parameters can consist of None as TOS1, the exception as TOS2, the value as TOS3, and the traceback as TOS4."

# 3.4  
"Raises an exception. argc indicates the number of parameters to the raise statement, ranging from 0 to 2. The parameters can consist of None as TOS1, the exception as TOS2, and the cause as TOS3."

----------

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

From report at bugs.python.org  Wed Oct 16 10:50:11 2013
From: report at bugs.python.org (Mark Lawrence)
Date: Wed, 16 Oct 2013 08:50:11 +0000
Subject: [docs] [issue19271] Update OrderedDict "see also" link
Message-ID: <1381913411.15.0.258294798121.issue19271@psf.upfronthosting.co.za>


New submission from Mark Lawrence:

Both Python 2 and 3 docs refer to Raymond Hettinger's original recipe here http://code.activestate.com/recipes/576693/.  Would it be better to link to pypi https://pypi.python.org/pypi/ordereddict?

----------
assignee: docs at python
components: Documentation
messages: 200041
nosy: BreamoreBoy, docs at python
priority: normal
severity: normal
status: open
title: Update OrderedDict "see also" link
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Wed Oct 16 10:56:07 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 16 Oct 2013 08:56:07 +0000
Subject: [docs] [issue19271] Update OrderedDict "see also" link
In-Reply-To: <1381913411.15.0.258294798121.issue19271@psf.upfronthosting.co.za>
Message-ID: <1381913767.73.0.0855956083371.issue19271@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Oct 16 22:52:06 2013
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 16 Oct 2013 20:52:06 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
Message-ID: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>


New submission from Zachary Ware:

Full title: Update PCbuild/readme.txt to be more accurate, more descriptive, more complete, less repetitive, more audience-aware, and all around, hopefully, better.

What started as a simple patch to fix the supported Windows versions list, the legacy build folders list, and a couple other minor factual errors turned into a nearly complete rewrite of the whole file.  The changes are too extensive to list out in this message; I'll use Rietveld to point out particular changes and my reasoning for them as soon as I'm able.  Also, due to the nature of the changes, it may be simpler to review the changed file itself rather than the patch, so I'll post the patched file as well.

At least 90% of these changes also apply to 3.3, but not all; I'd be happy to backport this patch or provide a new patch that strictly addresses factual errors in 3.3, as desired.

Thanks,

Zach

----------
assignee: docs at python
components: Documentation, Windows
files: pcbuild_readme.diff
keywords: patch
messages: 200085
nosy: docs at python, zach.ware
priority: normal
severity: normal
status: open
title: Update PCbuild/readme.txt
versions: Python 3.4
Added file: http://bugs.python.org/file32148/pcbuild_readme.diff

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

From report at bugs.python.org  Wed Oct 16 22:52:49 2013
From: report at bugs.python.org (Zachary Ware)
Date: Wed, 16 Oct 2013 20:52:49 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>
Message-ID: <1381956768.6.0.102808177348.issue19273@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Here's the patched file for easier review.

----------
Added file: http://bugs.python.org/file32149/patched_pcbuild_readme.txt

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

From report at bugs.python.org  Thu Oct 17 02:43:35 2013
From: report at bugs.python.org (Ned Deily)
Date: Thu, 17 Oct 2013 00:43:35 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>
Message-ID: <1381970615.73.0.130188212944.issue19273@psf.upfronthosting.co.za>


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


----------
nosy: +brian.curtin, christian.heimes, loewis, tim.golden

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

From report at bugs.python.org  Thu Oct 17 09:55:31 2013
From: report at bugs.python.org (Tobias Oberstein)
Date: Thu, 17 Oct 2013 07:55:31 +0000
Subject: [docs] [issue19277] zlib compressobj: missing parameter doc strings
Message-ID: <1381996531.24.0.0813249128928.issue19277@psf.upfronthosting.co.za>


New submission from Tobias Oberstein:

Currently the `zlib` module documents

    zlib.compressobj([level])

However, there are more parameters present already today:

    zlib.compressobj([level, method, wbits])

These other parameters are used in at least 2 deployed libraries (in the context of WebSocket compression):

https://github.com/tavendo/AutobahnPython/blob/master/autobahn/autobahn/compress_deflate.py#L527

http://code.google.com/p/pywebsocket/source/browse/trunk/src/mod_pywebsocket/util.py#231

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 200113
nosy: docs at python, oberstet
priority: normal
severity: normal
status: open
title: zlib compressobj: missing parameter doc strings
type: enhancement
versions: Python 2.7

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

From report at bugs.python.org  Thu Oct 17 19:50:30 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 17 Oct 2013 17:50:30 +0000
Subject: [docs] [issue19277] zlib compressobj: missing parameter doc strings
In-Reply-To: <1381996531.24.0.0813249128928.issue19277@psf.upfronthosting.co.za>
Message-ID: <3d0yZS6zy9z7LjZ@mail.python.org>


Roundup Robot added the comment:

New changeset c54c8e71b79a by Georg Brandl in branch '2.7':
Closes #19277: document all parameters of compressobj().
http://hg.python.org/cpython/rev/c54c8e71b79a

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

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

From report at bugs.python.org  Thu Oct 17 20:01:41 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 17 Oct 2013 18:01:41 +0000
Subject: [docs] [issue19277] zlib compressobj: missing parameter doc strings
In-Reply-To: <1381996531.24.0.0813249128928.issue19277@psf.upfronthosting.co.za>
Message-ID: <1382032901.73.0.254227373622.issue19277@psf.upfronthosting.co.za>


R. David Murray added the comment:

Hmm.  Looks like the name of the temp files used by the failing test (which is in bsddb, by the way) have changed, so my delete command didn't delete them.  So now /tmp is definitely clean, and the next build on that bot should work (crosses fingers).

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

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

From report at bugs.python.org  Thu Oct 17 20:02:00 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 17 Oct 2013 18:02:00 +0000
Subject: [docs] [issue19277] zlib compressobj: missing parameter doc strings
In-Reply-To: <1381996531.24.0.0813249128928.issue19277@psf.upfronthosting.co.za>
Message-ID: <1382032920.18.0.768894277526.issue19277@psf.upfronthosting.co.za>


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


----------
Removed message: http://bugs.python.org/msg200151

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

From report at bugs.python.org  Fri Oct 18 00:37:01 2013
From: report at bugs.python.org (Ethan Furman)
Date: Thu, 17 Oct 2013 22:37:01 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1382049421.75.0.557517389544.issue17576@psf.upfronthosting.co.za>


Ethan Furman added the comment:

Where do we stand with this issue?

----------

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

From report at bugs.python.org  Fri Oct 18 09:08:23 2013
From: report at bugs.python.org (Nick Guenther)
Date: Fri, 18 Oct 2013 07:08:23 +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: <1382080103.53.0.759267473411.issue10976@psf.upfronthosting.co.za>


Changes by Nick Guenther <nick at kousu.ca>:


----------
nosy: +kousu

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

From report at bugs.python.org  Fri Oct 18 09:57:48 2013
From: report at bugs.python.org (Ethan Furman)
Date: Fri, 18 Oct 2013 07:57:48 +0000
Subject: [docs] [issue19272] Can't pickle lambda (while named functions are
	ok)
In-Reply-To: <1381942596.3.0.421261732602.issue19272@psf.upfronthosting.co.za>
Message-ID: <1382083067.53.0.499719632111.issue19272@psf.upfronthosting.co.za>


Ethan Furman added the comment:

Added some clarification to the docs to make it clearer that lambda functions cannot be pickled.

Facundo [1], if you want to pursue being able to pickle lambda functions please open an enhancement issue.  Some of the questions that come to mind:

 1) for a random name, where will the name be stored  (I'm thinking a
    __pickle__ dict on the module)? 

 2) for pickling the code object itself, what are the ramifications
    (this is directly contrary to how pickle was designed) 

These questions should be discussed on PyDev, and will probably require a PEP.


[1] or anyone else :)

----------
assignee:  -> docs at python
nosy: +docs at python
resolution:  -> invalid
stage:  -> committed/rejected
status: open -> closed
versions:  -Python 3.3

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

From report at bugs.python.org  Fri Oct 18 10:00:28 2013
From: report at bugs.python.org (Mark Dickinson)
Date: Fri, 18 Oct 2013 08:00:28 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1382083227.91.0.392220647613.issue17576@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

I still need to act on some of Serhiy's comments.  I do plan to get this in for 3.4.

----------

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

From report at bugs.python.org  Fri Oct 18 16:06:29 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Fri, 18 Oct 2013 14:06:29 +0000
Subject: [docs] [issue17221] Resort Misc/NEWS
In-Reply-To: <1361135741.75.0.253129131493.issue17221@psf.upfronthosting.co.za>
Message-ID: <1382105189.19.0.51129077683.issue17221@psf.upfronthosting.co.za>


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


----------
stage: commit review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Fri Oct 18 22:38:38 2013
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Fri, 18 Oct 2013 20:38:38 +0000
Subject: [docs] [issue17576] PyNumber_Index() is not int-subclass friendly
	(or	operator.index() docos lie)
In-Reply-To: <1364595911.19.0.826873230127.issue17576@psf.upfronthosting.co.za>
Message-ID: <1382128718.48.0.614186541099.issue17576@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/issue17576>
_______________________________________

From report at bugs.python.org  Fri Oct 18 23:31:42 2013
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 18 Oct 2013 21:31:42 +0000
Subject: [docs] [issue19289] Incorrect documentation for format's fill
	character.
Message-ID: <1382131901.96.0.924496461441.issue19289@psf.upfronthosting.co.za>


New submission from Eric V. Smith:

In http://docs.python.org/library/string.html#format-specification-mini-language, it says "The fill character can be any character other than ?{? or ?}?."

But that's not actually true. It's only true when using str.format, as it does the parsing and the { and } mean special things for that parser. 

But for format itself there is no restriction:

>>> format(3, '{>10')
'{{{{{{{{{3'

As this section should be documenting the format specifiers themselves, I think it should not concern itself with restrictions imposed by str.format.

----------
assignee: docs at python
components: Documentation
messages: 200308
nosy: docs at python, eric.smith
priority: low
severity: normal
status: open
title: Incorrect documentation for format's fill character.
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Oct 19 00:25:32 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 18 Oct 2013 22:25:32 +0000
Subject: [docs] [issue19290] Clarify compile and eval interaction.
Message-ID: <1382135132.91.0.187309157375.issue19290@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

This issue was stimulated by #17294 where there seems to be some confusion over the purpose of the compile modes with regards to return values. I then noticed that the eval doc starts wrong and later corrects itself.

I think the following sentence from the compile doc could be improved. The current version:

"The mode argument specifies what kind of code must be compiled; it can be 'exec' if source consists of a sequence of statements, 'eval' if it consists of a single expression, or 'single' if it consists of a single interactive statement (in the latter case, expression statements that evaluate to something other than None will be printed)."

My suggestion:

"The mode argument specifies the allowed source and the return value when the result is passed to eval(). It can be 'exec' for any source (a sequence of 0 to many statements); the return value will be None. It can be 'eval' if the source is a single expression; the return value will be the value of the expression. It can be 'single' if the source is a single non-empty interactive statement; the return value will be None, as with 'exec', but if the statement is an expression that evaluates to something other than None, the value will be printed."

(#13677 is about changing the doc and docstring for the compile flags argument. Patches for that and this should be disjoint.)

The eval(expression, ..) doc say that expression is a string. It much later says that it can also be a code object. I think the eval doc should follow the exec doc and call the first positional-only arg 'object' and then say the same thing: 'object must be either a string or a code object.' I don't have a complete suggested revision yet.

----------
assignee: docs at python
components: Documentation
messages: 200318
nosy: docs at python, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Clarify compile and eval interaction.
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Oct 19 01:07:17 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 18 Oct 2013 23:07:17 +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: <1382137637.87.0.34128975564.issue19238@psf.upfronthosting.co.za>


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


----------
nosy: +terry.reedy
versions: +Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Oct 19 01:36:07 2013
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 18 Oct 2013 23:36:07 +0000
Subject: [docs] [issue19289] Incorrect documentation for format's fill
	character.
In-Reply-To: <1382131901.96.0.924496461441.issue19289@psf.upfronthosting.co.za>
Message-ID: <1382139367.18.0.0692343558565.issue19289@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

See also issue 19238.

----------

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

From report at bugs.python.org  Sat Oct 19 01:36:35 2013
From: report at bugs.python.org (Eric V. Smith)
Date: Fri, 18 Oct 2013 23:36:35 +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: <1382139395.66.0.274695839038.issue19238@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

See also issue 19289.

----------

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

From report at bugs.python.org  Sat Oct 19 05:47:01 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 19 Oct 2013 03:47:01 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382154421.18.0.141729313063.issue18958@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I'm not sure this should be documented in json.load/loads, and I'm not sure people will look there once they get this exception.
The error is raised because the wrong codec is used (either by open() before passing the file object to json.load or by json.loads), so it's a user error rather than a problem with the json module.  The error turns out to be particularly misleading because the decoding is successful even though it produces a wrong result, and the problem becomes apparent only once it reaches json.
ISTM that the documentation is already clear enough that json doesn't auto-detect encodings and uses UTF-8 by default, and that different encodings should be specified explicitly.
I think that a better and backward-compatible solution would be to detect the UTF-8 BOM and provide a better error message hinting at utf-8-sig.

----------

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

From report at bugs.python.org  Sat Oct 19 06:08:24 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 19 Oct 2013 04:08:24 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382155704.03.0.419375939602.issue18958@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Here is a proof of concept that raises this error:
>>> import json; json.load(open('input.json'))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/wolf/dev/py/2.7/Lib/json/__init__.py", line 290, in load
    **kw)
  File "/home/wolf/dev/py/2.7/Lib/json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "/home/wolf/dev/py/2.7/Lib/json/decoder.py", line 365, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/wolf/dev/py/2.7/Lib/json/decoder.py", line 381, in raw_decode
    obj, end = self.scan_once(s, idx)
ValueError: Unexpected UTF-8 BOM (decode using utf-8-sig): line 1 column 1 (char 0)

If the idea is OK I will add tests and implement it for the Python scanner too (and possibly tweak the error message if you have better suggestions).

----------

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

From report at bugs.python.org  Sat Oct 19 06:08:43 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 19 Oct 2013 04:08:43 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382155723.17.0.952581410521.issue18958@psf.upfronthosting.co.za>


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


Added file: http://bugs.python.org/file32213/issue18958.diff

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

From report at bugs.python.org  Sat Oct 19 06:09:56 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 19 Oct 2013 04:09:56 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382155796.59.0.936860477111.issue18958@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Forgot to add that the patch is for 2.7, and it also needs to be implemented in the unicode scanner.

----------

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

From report at bugs.python.org  Sat Oct 19 06:37:21 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 19 Oct 2013 04:37:21 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382157441.5.0.232005828698.issue18958@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

I like the new error message as a low-risk immediate improvement that nudges people in the direction of utf8-sig. It also leaves the door open to silently ignoring the BoM in the future without immediately committing to that approach.

----------

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

From ezio.melotti at gmail.com  Sat Oct 19 06:41:33 2013
From: ezio.melotti at gmail.com (ezio.melotti at gmail.com)
Date: Sat, 19 Oct 2013 04:41:33 -0000
Subject: [docs] Improve the documentation in fcntl module (issue 18985)
Message-ID: <20131019044133.3770.53096@psf.upfronthosting.co.za>

The patch looks good, but I see 3 different options about the names of
the args:
1) use opt for both -- this is simple and consistent, however opt sounds
to me like the abbreviation of option;
2) use the same name of the man pages -- closer to the original, but
more inconsistent;
3) use something like "operation" or maybe "oper" for both;

I don't have any strong preference, so unless there are reasons to
prefer options 2 or 3 I think the patch can be committed as is.


http://bugs.python.org/review/18985/diff/9318/Modules/fcntlmodule.c
File Modules/fcntlmodule.c (right):

http://bugs.python.org/review/18985/diff/9318/Modules/fcntlmodule.c#newcode80
Modules/fcntlmodule.c:80: "fcntl(fd, opt, [arg])\n\
FTR, on the man pages opt is called "cmd".

http://bugs.python.org/review/18985/diff/9318/Modules/fcntlmodule.c#newcode309
Modules/fcntlmodule.c:309: "flock(fd, opt)\n\
On the man pages this is called "operation".
Is opt supposed to be the abbreviation of operation? option?

http://bugs.python.org/review/18985/

From report at bugs.python.org  Sat Oct 19 06:41:49 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 19 Oct 2013 04:41:49 +0000
Subject: [docs] [issue18985] Improve the documentation in fcntl module
In-Reply-To: <1378722919.93.0.901392318122.issue18985@psf.upfronthosting.co.za>
Message-ID: <1382157709.16.0.630106764889.issue18985@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 19 06:44:20 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 19 Oct 2013 04:44:20 +0000
Subject: [docs] [issue18918] help('FILES') finds no documentation
In-Reply-To: <1378269620.52.0.763555902483.issue18918@psf.upfronthosting.co.za>
Message-ID: <1382157860.65.0.456055938744.issue18918@psf.upfronthosting.co.za>


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


----------
nosy: +georg.brandl
stage: needs patch -> patch review

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

From report at bugs.python.org  Sat Oct 19 07:15:46 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 19 Oct 2013 05:15:46 +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: <1382159746.88.0.27652537157.issue19238@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Oct 19 07:16:02 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 19 Oct 2013 05:16:02 +0000
Subject: [docs] [issue19289] Incorrect documentation for format's fill
	character.
In-Reply-To: <1382131901.96.0.924496461441.issue19289@psf.upfronthosting.co.za>
Message-ID: <1382159762.38.0.360928876603.issue19289@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/issue19289>
_______________________________________

From report at bugs.python.org  Sat Oct 19 07:17:27 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 19 Oct 2013 05:17:27 +0000
Subject: [docs] [issue19271] Update OrderedDict "see also" link
In-Reply-To: <1381913411.15.0.258294798121.issue19271@psf.upfronthosting.co.za>
Message-ID: <1382159847.82.0.295515841724.issue19271@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
stage:  -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Sat Oct 19 07:18:25 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 19 Oct 2013 05:18:25 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>
Message-ID: <1382159905.09.0.513911357503.issue19273@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
stage:  -> patch review
type:  -> enhancement

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

From report at bugs.python.org  Sat Oct 19 21:07:19 2013
From: report at bugs.python.org (Claudiu.Popa)
Date: Sat, 19 Oct 2013 19:07:19 +0000
Subject: [docs] [issue19304] Typo in statistics.rst
Message-ID: <1382209639.62.0.731892223733.issue19304@psf.upfronthosting.co.za>


New submission from Claudiu.Popa:

There are two small typos in statistics.rst.

----------
assignee: docs at python
components: Documentation
files: typos.patch
keywords: patch
messages: 200480
nosy: Claudiu.Popa, docs at python
priority: normal
severity: normal
status: open
title: Typo in statistics.rst
versions: Python 3.4
Added file: http://bugs.python.org/file32230/typos.patch

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

From report at bugs.python.org  Sat Oct 19 21:10:53 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 19 Oct 2013 19:10:53 +0000
Subject: [docs] [issue19304] Typo in statistics.rst
In-Reply-To: <1382209639.62.0.731892223733.issue19304@psf.upfronthosting.co.za>
Message-ID: <3d2DGH44H0zSB7@mail.python.org>


Roundup Robot added the comment:

New changeset 900460f0fb2a by Ned Deily in branch 'default':
Issue #19304: Fix typos noted by Claudiu Popa.
http://hg.python.org/cpython/rev/900460f0fb2a

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

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

From report at bugs.python.org  Sat Oct 19 21:11:34 2013
From: report at bugs.python.org (Ned Deily)
Date: Sat, 19 Oct 2013 19:11:34 +0000
Subject: [docs] [issue19304] Typo in statistics.rst
In-Reply-To: <1382209639.62.0.731892223733.issue19304@psf.upfronthosting.co.za>
Message-ID: <1382209894.27.0.503906122648.issue19304@psf.upfronthosting.co.za>


Ned Deily added the comment:

Thanks for the patch.

----------
nosy: +ned.deily
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Sun Oct 20 05:23:28 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 20 Oct 2013 03:23:28 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382239408.5.0.410330970235.issue18958@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Here is an updated patch with tests.

----------
stage: needs patch -> patch review
Added file: http://bugs.python.org/file32235/issue18958-2.diff

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

From report at bugs.python.org  Sun Oct 20 05:32:26 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2013 03:32:26 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382239946.06.0.513305661362.issue18958@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Updated patch looks good to me.

----------

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

From report at bugs.python.org  Sun Oct 20 05:44:55 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 20 Oct 2013 03:44:55 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382240695.81.0.924148119824.issue18958@psf.upfronthosting.co.za>


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


Added file: http://bugs.python.org/file32237/issue18958-2-py3k.diff

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

From report at bugs.python.org  Sun Oct 20 05:52:01 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2013 03:52:01 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382241121.93.0.0311932512351.issue18958@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

As does the Py3k version :)

----------

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

From report at bugs.python.org  Sun Oct 20 06:12:52 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2013 04:12:52 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382242372.59.0.485282156757.issue18958@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Discussing this with Ezio on IRC, we decided that it probably makes more sense to do this check outside the scanner as preliminary validation of the input passed in via the public API. That will minimise the overhead and also avoids any potential side effects if "idx==0" is ever true in cases we're not currently testing.

The tests from the current patches should be OK, though.

Ezio also found that, for Py3k, adding an explicit check for non-str input and throwing an appropriate error would also be an improvement over the status quo:

>>> import json
>>> json.loads(b'')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/ncoghlan/devel/py3k/Lib/json/__init__.py", line 316, in loads
    return _default_decoder.decode(s)
  File "/home/ncoghlan/devel/py3k/Lib/json/decoder.py", line 344, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: can't use a string pattern on a bytes-like object

----------

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

From report at bugs.python.org  Sun Oct 20 07:24:07 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 20 Oct 2013 05:24:07 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382246647.14.0.640226507591.issue18958@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I opened a new issue about improving the error message: #19307.
After further discussion on IRC, we think that both #19307 and this issue should only be applied on 3.4 (the attached patch produces an even more misleading error that would require backporting #19307).

----------
dependencies: +Improve TypeError message in json.loads()
versions: +Python 3.4 -Python 2.7
Added file: http://bugs.python.org/file32239/issue18958-3.diff

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

From report at bugs.python.org  Sun Oct 20 12:25:11 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 20 Oct 2013 10:25:11 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382264711.18.0.288060155515.issue18958@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

The patch needs to be rebased on top of the issue 19307 patch, but I like this approach.

I say go ahead and commit it whenever you're ready :)

----------

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

From report at bugs.python.org  Sun Oct 20 20:19:33 2013
From: report at bugs.python.org (Christoph Baumgartner)
Date: Sun, 20 Oct 2013 18:19:33 +0000
Subject: [docs] [issue19319] misleading comment regarding C
Message-ID: <1382293173.85.0.561092351963.issue19319@psf.upfronthosting.co.za>


New submission from Christoph Baumgartner:

The documentation about ctypes.sizeof:

"Returns the size in bytes of a ctypes type or instance memory buffer. Does the same as the C sizeof() function."

'sizeof' is an operator. I would drop the parentheses as well.

----------
assignee: docs at python
components: Documentation
messages: 200604
nosy: Christoph.Baumgartner, docs at python
priority: normal
severity: normal
status: open
title: misleading comment regarding C

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

From report at bugs.python.org  Sun Oct 20 20:24:22 2013
From: report at bugs.python.org (Martin Matusiak)
Date: Sun, 20 Oct 2013 18:24:22 +0000
Subject: [docs] [issue19319] misleading comment regarding C
In-Reply-To: <1382293173.85.0.561092351963.issue19319@psf.upfronthosting.co.za>
Message-ID: <1382293462.9.0.334344843964.issue19319@psf.upfronthosting.co.za>


Changes by Martin Matusiak <numerodix at gmail.com>:


----------
nosy: +numerodix

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

From report at bugs.python.org  Sun Oct 20 21:41:21 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 20 Oct 2013 19:41:21 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382298081.78.0.334105392907.issue18958@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

LGTM.

----------

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

From report at bugs.python.org  Mon Oct 21 01:11:30 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 20 Oct 2013 23:11:30 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <3d2xYS6jfBz7Ljy@mail.python.org>


Roundup Robot added the comment:

New changeset ac016cba7e64 by Ezio Melotti in branch 'default':
#18958: Improve error message for json.load(s) while passing a string that starts with a UTF-8 BOM.
http://hg.python.org/cpython/rev/ac016cba7e64

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

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

From report at bugs.python.org  Mon Oct 21 01:11:58 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 20 Oct 2013 23:11:58 +0000
Subject: [docs] [issue18958] Exception('No JSON object could be decoded')
	when	parsing a valid JSON
In-Reply-To: <1378557195.07.0.581794298686.issue18958@psf.upfronthosting.co.za>
Message-ID: <1382310718.23.0.859508356908.issue18958@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the feedback!

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

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

From report at bugs.python.org  Mon Oct 21 01:35:34 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 20 Oct 2013 23:35:34 +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: <1382312134.38.0.485810912424.issue19238@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Here's a patch.  This also include a fix for #19289.

----------
keywords: +patch
stage:  -> patch review
Added file: http://bugs.python.org/file32266/issue19238.diff

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

From report at bugs.python.org  Mon Oct 21 01:36:12 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 20 Oct 2013 23:36:12 +0000
Subject: [docs] [issue19289] Incorrect documentation for format's fill
	character.
In-Reply-To: <1382131901.96.0.924496461441.issue19289@psf.upfronthosting.co.za>
Message-ID: <1382312172.58.0.200005490268.issue19289@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I uploaded a patch on #19238 that also fixes this.

----------
stage:  -> patch review
type:  -> enhancement

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

From report at bugs.python.org  Mon Oct 21 01:40:30 2013
From: report at bugs.python.org (Eric V. Smith)
Date: Sun, 20 Oct 2013 23:40:30 +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: <1382312430.85.0.453675956499.issue19238@psf.upfronthosting.co.za>


Eric V. Smith added the comment:

Looks good to me. Thanks!

----------

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

From report at bugs.python.org  Mon Oct 21 01:45:57 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 20 Oct 2013 23:45:57 +0000
Subject: [docs] [issue19271] Update OrderedDict "see also" link
In-Reply-To: <1381913411.15.0.258294798121.issue19271@psf.upfronthosting.co.za>
Message-ID: <1382312757.7.0.383767368852.issue19271@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Here's a patch.  The request seems reasonable to me, more so since the PyPI page links to the recipe.  If the goal of the link is to show the code of the implementation, the :source: directive can also be used.

----------
keywords: +patch
stage: needs patch -> patch review
Added file: http://bugs.python.org/file32268/issue19271.diff

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

From report at bugs.python.org  Mon Oct 21 01:54:34 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 20 Oct 2013 23:54:34 +0000
Subject: [docs] [issue19289] Incorrect documentation for format's fill
	character.
In-Reply-To: <1382131901.96.0.924496461441.issue19289@psf.upfronthosting.co.za>
Message-ID: <3d2yW90VlDz7Ljg@mail.python.org>


Roundup Robot added the comment:

New changeset e3ff2065c548 by Ezio Melotti in branch '3.3':
#19238, #19289: fix description of the align and fill values of the format specification.
http://hg.python.org/cpython/rev/e3ff2065c548

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

New changeset 0592dc076bb7 by Ezio Melotti in branch '2.7':
#19238, #19289: fix description of the align and fill values of the format specification.
http://hg.python.org/cpython/rev/0592dc076bb7

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

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

From report at bugs.python.org  Mon Oct 21 01:54:34 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 20 Oct 2013 23:54:34 +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: <3d2yW82F6hz7LjX@mail.python.org>


Roundup Robot added the comment:

New changeset e3ff2065c548 by Ezio Melotti in branch '3.3':
#19238, #19289: fix description of the align and fill values of the format specification.
http://hg.python.org/cpython/rev/e3ff2065c548

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

New changeset 0592dc076bb7 by Ezio Melotti in branch '2.7':
#19238, #19289: fix description of the align and fill values of the format specification.
http://hg.python.org/cpython/rev/0592dc076bb7

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

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

From report at bugs.python.org  Mon Oct 21 01:55:27 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 20 Oct 2013 23:55:27 +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: <1382313327.32.0.818129560604.issue19238@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the review!

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

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

From report at bugs.python.org  Mon Oct 21 01:55:47 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 20 Oct 2013 23:55:47 +0000
Subject: [docs] [issue19289] Incorrect documentation for format's fill
	character.
In-Reply-To: <1382131901.96.0.924496461441.issue19289@psf.upfronthosting.co.za>
Message-ID: <1382313347.18.0.666651707407.issue19289@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Oct 21 02:14:20 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 21 Oct 2013 00:14:20 +0000
Subject: [docs] [issue13515] Consistent documentation practices for security
	concerns	and considerations
In-Reply-To: <1322726017.57.0.923133254266.issue13515@psf.upfronthosting.co.za>
Message-ID: <3d2yyL2BLlzQXg@mail.python.org>


Roundup Robot added the comment:

New changeset 8bb5f4301e01 by Ezio Melotti in branch 'default':
#13515: document security-related documentation practices.
http://hg.python.org/devguide/rev/8bb5f4301e01

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

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

From report at bugs.python.org  Mon Oct 21 02:14:50 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 21 Oct 2013 00:14:50 +0000
Subject: [docs] [issue13515] Consistent documentation practices for security
	concerns	and considerations
In-Reply-To: <1322726017.57.0.923133254266.issue13515@psf.upfronthosting.co.za>
Message-ID: <1382314490.42.0.994176935083.issue13515@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> ezio.melotti
resolution:  -> fixed
stage: commit review -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Mon Oct 21 03:42:45 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 21 Oct 2013 01:42:45 +0000
Subject: [docs] [issue19319] misleading comment regarding C
In-Reply-To: <1382293173.85.0.561092351963.issue19319@psf.upfronthosting.co.za>
Message-ID: <3d30vz4pdHz7LjX@mail.python.org>


Roundup Robot added the comment:

New changeset 737b79e524aa by Ezio Melotti in branch '2.7':
#19319: fix ctypes docs: sizeof is an operator in C, not a function.
http://hg.python.org/cpython/rev/737b79e524aa

New changeset d8e352e2f110 by Ezio Melotti in branch '3.3':
#19319: fix ctypes docs: sizeof is an operator in C, not a function.
http://hg.python.org/cpython/rev/d8e352e2f110

New changeset 49f8d07b6c5c by Ezio Melotti in branch 'default':
#19319: merge with 3.3.
http://hg.python.org/cpython/rev/49f8d07b6c5c

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

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

From report at bugs.python.org  Mon Oct 21 03:43:14 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 21 Oct 2013 01:43:14 +0000
Subject: [docs] [issue19319] misleading comment regarding C
In-Reply-To: <1382293173.85.0.561092351963.issue19319@psf.upfronthosting.co.za>
Message-ID: <1382319794.77.0.309518278803.issue19319@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
versions: +Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Oct 21 05:37:14 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 21 Oct 2013 03:37:14 +0000
Subject: [docs] [issue19271] Update OrderedDict "see also" link
In-Reply-To: <1381913411.15.0.258294798121.issue19271@psf.upfronthosting.co.za>
Message-ID: <1382326634.34.0.734957662536.issue19271@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Ezio, we already have a sourcelink at the top of the collections module.

Mark, I want to keep the ASPN link in the 2.7 docs.  The goal wasn't to point to "an original recipe".  The intent was to show how to backport to old versions of Python if needed.

I will take the link out of the 3.4 docs because it no longer serves a purpose.

----------

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

From report at bugs.python.org  Mon Oct 21 05:42:37 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 21 Oct 2013 03:42:37 +0000
Subject: [docs] [issue19271] Update OrderedDict "see also" link
In-Reply-To: <1381913411.15.0.258294798121.issue19271@psf.upfronthosting.co.za>
Message-ID: <3d33ZH4dPJz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 9e322a8f80d9 by Raymond Hettinger in branch 'default':
Issue #19271:  By Python3.4, the Python 2.4 backport links are no longer of much interest.
http://hg.python.org/cpython/rev/9e322a8f80d9

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

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

From report at bugs.python.org  Mon Oct 21 05:43:05 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 21 Oct 2013 03:43:05 +0000
Subject: [docs] [issue19271] Update OrderedDict "see also" link
In-Reply-To: <1381913411.15.0.258294798121.issue19271@psf.upfronthosting.co.za>
Message-ID: <1382326985.45.0.166668549747.issue19271@psf.upfronthosting.co.za>


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


----------
resolution:  -> fixed
status: open -> closed
versions:  -Python 2.7, Python 3.3

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

From report at bugs.python.org  Mon Oct 21 09:05:12 2013
From: report at bugs.python.org (Michael Merickel)
Date: Mon, 21 Oct 2013 07:05:12 +0000
Subject: [docs] [issue19323] typo in statistics documentation
Message-ID: <1382339112.75.0.593469307038.issue19323@psf.upfronthosting.co.za>


New submission from Michael Merickel:

http://docs.python.org/dev/library/statistics.html#mean describes the mean as "effected" by outliers, when it should say "affected".

----------
assignee: docs at python
components: Documentation
messages: 200704
nosy: docs at python, mmerickel
priority: normal
severity: normal
status: open
title: typo in statistics documentation
versions: Python 3.4

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

From report at bugs.python.org  Mon Oct 21 09:08:05 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 21 Oct 2013 07:08:05 +0000
Subject: [docs] [issue19323] typo in statistics documentation
In-Reply-To: <1382339112.75.0.593469307038.issue19323@psf.upfronthosting.co.za>
Message-ID: <3d387M3Htnz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 1f466354a85b by Georg Brandl in branch 'default':
Closes #19323: fix typo. Thanks to Michael Merickel.
http://hg.python.org/cpython/rev/1f466354a85b

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

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

From report at bugs.python.org  Mon Oct 21 12:01:25 2013
From: report at bugs.python.org (Stefan Krah)
Date: Mon, 21 Oct 2013 10:01:25 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <1295653779.62.0.836506069174.issue10977@psf.upfronthosting.co.za>
Message-ID: <1382349685.55.0.44346001991.issue10977@psf.upfronthosting.co.za>


Stefan Krah added the comment:

I'm also in favor of a clean separation between the concrete and abstract
APIs (see also #12965).  Why can't the concrete functions be locked down
with *CheckExact()?  If there's any breakage in third party modules,
it's easy to fix (probably much easier than the Unicode changes in 3.3).

----------
nosy: +skrah

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

From report at bugs.python.org  Mon Oct 21 13:42:21 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 21 Oct 2013 11:42:21 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <1382349685.55.0.44346001991.issue10977@psf.upfronthosting.co.za>
Message-ID: <CADiSq7cN79SSoS5bkZmHWmRSaCiLuT8N4LyH77E2TiiMXnqjyQ@mail.gmail.com>


Nick Coghlan added the comment:

Because calling them *from* method implementations in concrete subclasses
is often a perfectly reasonable thing to do.

----------

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

From report at bugs.python.org  Mon Oct 21 14:25:45 2013
From: report at bugs.python.org (Christian Heimes)
Date: Mon, 21 Oct 2013 12:25:45 +0000
Subject: [docs] [issue17006] Warn users about hashing secrets?
In-Reply-To: <1358758082.76.0.415880124971.issue17006@psf.upfronthosting.co.za>
Message-ID: <1382358345.44.0.545125824239.issue17006@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Who likes to step in? Alex?

----------
nosy: +alex

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

From report at bugs.python.org  Mon Oct 21 17:04:59 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2013 15:04:59 +0000
Subject: [docs] [issue19270] Document that sched.cancel() doesn't
	distinguish equal	events and can break order
In-Reply-To: <1381913252.24.0.629122693277.issue19270@psf.upfronthosting.co.za>
Message-ID: <1382367898.97.0.000947749981537.issue19270@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Well. In any case I have no ideas how fix it. Any behavior change will break existing code.

I requalify this issue as documentation enhancement. The documentation should specify that evens scheduled on same tame with same priority considered equal. That cancel() doesn't distinguish equal events and can cancel arbitrary of them. That cancel() doesn't preserve order of equal events.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
keywords: +easy
nosy: +docs at python
title: sched.cancel() breaks events order -> Document that sched.cancel() doesn't distinguish equal events and can break order
type: behavior -> enhancement
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Mon Oct 21 17:09:20 2013
From: report at bugs.python.org (STINNER Victor)
Date: Mon, 21 Oct 2013 15:09:20 +0000
Subject: [docs] [issue19270] Document that sched.cancel() doesn't
	distinguish equal	events and can break order
In-Reply-To: <1381913252.24.0.629122693277.issue19270@psf.upfronthosting.co.za>
Message-ID: <1382368160.22.0.605298739308.issue19270@psf.upfronthosting.co.za>


STINNER Victor added the comment:

@Raymond: The logic is essentially the same as is used in popular event loops like Tornado.

Sorry, I didn't understand your sentence: do you mean that sched must keep the insertion order or the order is undefined?

Undefined order is fine if it's documented.

----------

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

From report at bugs.python.org  Mon Oct 21 17:38:02 2013
From: report at bugs.python.org (Eric Snow)
Date: Mon, 21 Oct 2013 15:38:02 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <1295653779.62.0.836506069174.issue10977@psf.upfronthosting.co.za>
Message-ID: <1382369882.06.0.385738542601.issue10977@psf.upfronthosting.co.za>


Eric Snow added the comment:

> Because calling them *from* method implementations in concrete subclasses...

We do the same thing from Python all the time (though less so with the availability of super).
E.G. dict.__init__(self, ...) and dict.__set item__(self, key, value).

Now, if the C-API had some equivalent to super...

----------

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

From report at bugs.python.org  Mon Oct 21 20:53:31 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 21 Oct 2013 18:53:31 +0000
Subject: [docs] [issue19270] Document that sched.cancel() doesn't
	distinguish equal	events and can break order
In-Reply-To: <1381913252.24.0.629122693277.issue19270@psf.upfronthosting.co.za>
Message-ID: <1382381611.37.0.170209595346.issue19270@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

I'm not strong on a new invariant, however I think bug #1 would deserve fixing:

> 1. sched.cancel() can remove wrong event (because it uses equality instead identity).

----------

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

From report at bugs.python.org  Mon Oct 21 21:43:03 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 21 Oct 2013 19:43:03 +0000
Subject: [docs] [issue19270] Document that sched.cancel() doesn't
	distinguish equal	events and can break order
In-Reply-To: <1381913252.24.0.629122693277.issue19270@psf.upfronthosting.co.za>
Message-ID: <1382384583.15.0.0282469575897.issue19270@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

> I'm not strong on a new invariant, however I think bug #1 would deserve fixing:

How would you do this?

1. Use identity instead equality to search canceled event. It will break code where an user cancels an event by time and priority: scheduler.cancel(Event(time, priority, ...)).

2. Always cancel chronologically last (first) of equals events. This requires popp-ing and push-ing all events. Too slooooow.

3. Add an ordered number to the event. This will slow down all too.

4. Mixed strategy. First use identity search, then equality search, and only if found several equals events fallback to slow variant. This is too complicated. It will work as expected in most normal cases, but in rare cases... This behavior would hard to document and understand.

If you have better idea, patch is welcome.

----------

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

From report at bugs.python.org  Mon Oct 21 21:46:15 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 21 Oct 2013 19:46:15 +0000
Subject: [docs] [issue19270] Document that sched.cancel() doesn't
	distinguish equal	events and can break order
In-Reply-To: <1382384583.15.0.0282469575897.issue19270@psf.upfronthosting.co.za>
Message-ID: <1382384743.2487.29.camel@fsol>


Antoine Pitrou added the comment:

> 4. Mixed strategy. First use identity search, then equality search,
> and only if found several equals events fallback to slow variant. This
> is too complicated. It will work as expected in most normal cases, but
> in rare cases... This behavior would hard to document and understand.

You're right. So perhaps this should simply be documented as is.

----------

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

From report at bugs.python.org  Mon Oct 21 21:49:05 2013
From: report at bugs.python.org (Giampaolo Rodola')
Date: Mon, 21 Oct 2013 19:49:05 +0000
Subject: [docs] [issue19270] Document that sched.cancel() doesn't
	distinguish equal	events and can break order
In-Reply-To: <1381913252.24.0.629122693277.issue19270@psf.upfronthosting.co.za>
Message-ID: <1382384945.38.0.954879644743.issue19270@psf.upfronthosting.co.za>


Giampaolo Rodola' added the comment:

> This module has been around for a long time and no users have reported 
> any issues with respect to event ordering.  The logic is essentially 
> the same as is used in popular event loops like Tornado.
> Please don't just make-up a new invariant for this module.

+1

----------

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

From report at bugs.python.org  Mon Oct 21 22:27:33 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 21 Oct 2013 20:27:33 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <1382369882.06.0.385738542601.issue10977@psf.upfronthosting.co.za>
Message-ID: <CADiSq7e_Gv8-JCd8qLtR-xTp-YYzart3Zsm69S57a2-C+NeCJw@mail.gmail.com>


Nick Coghlan added the comment:

I haven't fully thought this one through, but perhaps we could:
- deprecate calling the current concrete APIs with subclasses (since doing
so may break subclass invariants)
- add "PyBaseDict_*" APIs (etc) that subclass implementations can call.
- offer a compatibility header for earlier versions that #defines the new
APIs back to the old ones

This would be 3.5 PEP territory, though.

----------

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

From report at bugs.python.org  Mon Oct 21 22:41:30 2013
From: report at bugs.python.org (Eric Snow)
Date: Mon, 21 Oct 2013 20:41:30 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <1295653779.62.0.836506069174.issue10977@psf.upfronthosting.co.za>
Message-ID: <1382388090.58.0.151692646437.issue10977@psf.upfronthosting.co.za>


Eric Snow added the comment:

I had roughly the same idea, Nick, though my approach to address backward compatibility was more complicated.  Definitely worth at least looking into for 3.5.

----------

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

From report at bugs.python.org  Tue Oct 22 10:58:23 2013
From: report at bugs.python.org (Marius Gedminas)
Date: Tue, 22 Oct 2013 08:58:23 +0000
Subject: [docs] [issue19342] Improve grp module docstrings
Message-ID: <1382432303.67.0.186570774383.issue19342@psf.upfronthosting.co.za>


New submission from Marius Gedminas:

This patch gives grp.getgrnam and grp.getgrgid sligtly more useful docstrings, and brings them in line with pwd.getpwnam/pwd.getpwuid.

Compare pydoc pwd.getpwnam:

    pwd.getpwnam = getpwnam(...)
        getpwnam(name) -> (pw_name,pw_passwd,pw_uid,
                            pw_gid,pw_gecos,pw_dir,pw_shell)
        Return the password database entry for the given user name.
        See help(pwd) for more on password database entries.

After looking at it I know that I can convert a name to an UID by doing pwd.getpwnam(name).pw_uid.

Meanwhile pydoc grp.getgrnam:

    grp.getgrnam = getgrnam(...)
        getgrnam(name) -> tuple
        Return the group database entry for the given group name.  If
        name is not valid, raise KeyError.

is rather unfriendly and makes me reach for Google just so that I could find out the names of the namedtuple members.

----------
assignee: docs at python
components: Documentation
files: grpmodule-docstrings.patch
keywords: patch
messages: 200896
nosy: docs at python, mgedmin
priority: normal
severity: normal
status: open
title: Improve grp module docstrings
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file32295/grpmodule-docstrings.patch

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

From report at bugs.python.org  Tue Oct 22 11:51:59 2013
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 22 Oct 2013 09:51:59 +0000
Subject: [docs] [issue19344] ReStructuredText error in whatsnew/3.4.rst
In-Reply-To: <1382435263.38.0.923957095202.issue19344@psf.upfronthosting.co.za>
Message-ID: <1382435519.62.0.264179373661.issue19344@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Fixed in http://hg.python.org/cpython/rev/af628ab4272a

Thanks!

----------
nosy: +christian.heimes
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Tue Oct 22 11:53:43 2013
From: report at bugs.python.org (Marius Gedminas)
Date: Tue, 22 Oct 2013 09:53:43 +0000
Subject: [docs] [issue19345] Unclear phrasing in whatsnew/3.4.rst
Message-ID: <1382435623.18.0.649588636826.issue19345@psf.upfronthosting.co.za>


New submission from Marius Gedminas:

Quoting http://docs.python.org/dev/whatsnew/3.4.html#deprecated-functions-and-types-of-the-c-api

> The PyThreadState.tick_counter field has been value: its value was meaningless since Python 3.2 (?new GIL?).

I've no idea what "has been value" is supposed to be.  Perhaps "has been deprecated"?

No patch this time since I'm not sure what was meant here.

----------
assignee: docs at python
components: Documentation
messages: 200909
nosy: docs at python, mgedmin
priority: normal
severity: normal
status: open
title: Unclear phrasing in whatsnew/3.4.rst
versions: Python 3.4

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

From report at bugs.python.org  Tue Oct 22 11:47:43 2013
From: report at bugs.python.org (Marius Gedminas)
Date: Tue, 22 Oct 2013 09:47:43 +0000
Subject: [docs] [issue19344] ReStructuredText error in whatsnew/3.4.rst
Message-ID: <1382435263.38.0.923957095202.issue19344@psf.upfronthosting.co.za>


New submission from Marius Gedminas:

Trivial syntax fix attached

----------
assignee: docs at python
components: Documentation
files: whatsnew-rst-fix.patch
keywords: patch
messages: 200907
nosy: docs at python, mgedmin
priority: normal
severity: normal
status: open
title: ReStructuredText error in whatsnew/3.4.rst
versions: Python 3.4
Added file: http://bugs.python.org/file32296/whatsnew-rst-fix.patch

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

From report at bugs.python.org  Tue Oct 22 17:41:05 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 22 Oct 2013 15:41:05 +0000
Subject: [docs] [issue19345] Unclear phrasing in whatsnew/3.4.rst
In-Reply-To: <1382435623.18.0.649588636826.issue19345@psf.upfronthosting.co.za>
Message-ID: <1382456465.27.0.667654595029.issue19345@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


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

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

From report at bugs.python.org  Tue Oct 22 17:49:23 2013
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 22 Oct 2013 15:49:23 +0000
Subject: [docs] [issue19345] Unclear phrasing in whatsnew/3.4.rst
In-Reply-To: <1382435623.18.0.649588636826.issue19345@psf.upfronthosting.co.za>
Message-ID: <1382456963.91.0.918856923493.issue19345@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> The PyThreadState.tick_counter field has been value: its value was meaningless since Python 3.2 (?new GIL?).

oops, "has been removed" :-)

----------

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

From report at bugs.python.org  Wed Oct 23 14:22:08 2013
From: report at bugs.python.org (Gareth Rees)
Date: Wed, 23 Oct 2013 12:22:08 +0000
Subject: [docs] [issue19362] Documentation for len() fails to mention that
	it works	on sets
Message-ID: <1382530928.74.0.685857253341.issue19362@psf.upfronthosting.co.za>


New submission from Gareth Rees:

The help text for the len() built-in function says:

    Return the number of items of a sequence or mapping.

This omits to mention that len() works on sets too. I suggest this be changed to:

    Return the number of items of a sequence, mapping, or set.

Similarly, the documentation for len() says:

    The argument may be a sequence (string, tuple or list) or a mapping (dictionary).

I suggest this be changed to

    The argument may be a sequence (string, tuple or list), a mapping (dictionary), or a set.

(Of course, strictly speaking, len() accepts any object with a __len__ method, but sequences, mappings and sets are the ones that are built-in to the Python core, and so these are the ones it is important to mention in the help and the documentation.)

----------
assignee: docs at python
components: Documentation
files: len-set.patch
keywords: patch
messages: 201019
nosy: Gareth.Rees, docs at python
priority: normal
severity: normal
status: open
title: Documentation for len() fails to mention that it works on sets
type: enhancement
Added file: http://bugs.python.org/file32313/len-set.patch

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

From report at bugs.python.org  Wed Oct 23 14:31:37 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 23 Oct 2013 12:31:37 +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: <1382531497.46.0.717435586064.issue19362@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/issue19362>
_______________________________________

From report at bugs.python.org  Wed Oct 23 15:38:02 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 23 Oct 2013 13:38:02 +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: <1382535482.47.0.0893816633892.issue19362@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

"Return the number of items of a container" sounds simple and accurate to me.

----------
nosy: +pitrou, rhettinger

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

From report at bugs.python.org  Wed Oct 23 15:59:50 2013
From: report at bugs.python.org (Gareth Rees)
Date: Wed, 23 Oct 2013 13:59:50 +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: <1382536790.76.0.000627324571274.issue19362@psf.upfronthosting.co.za>


Gareth Rees added the comment:

I considered suggesting "container", but the problem is that "container" is used elsewhere to mean "object supporting the 'in' operator" (in particular, collections.abc.Container has a __contains__ method but no __len__ method).

The abstract base class for "object with a length" is collections.abc.Sized, but I don't think using the term "sized" would be clear to users.

----------

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

From report at bugs.python.org  Wed Oct 23 16:05:54 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 23 Oct 2013 14:05:54 +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: <1382537154.14.0.377182050817.issue19362@psf.upfronthosting.co.za>


R. David Murray added the comment:

Perhaps it would be better to say that "the argument may be any object with a __len__, such as the commonly used Python sequence and container types str, bytes, tuple, list, dict, and set".  After all, there are other built in types it works on as well: bytearray, frozenset, memoryview.

For the other, "the number of items in a sequence or container type" would mostly cover it, but at the cost of being a bit obscure.  Perhaps that's OK for the help text, though, since it is supposed to be a reminder, not the full documentation.  Another even more obscure alternative would be "the number of items in a Sized object", which would also be more accurate (since an object with a __len__ doesn't *have* to conform fully to the sequence or container ABCs...nor does a container *have* to implement __len__).

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

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

From report at bugs.python.org  Wed Oct 23 16:09:37 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 23 Oct 2013 14:09:37 +0000
Subject: [docs] [issue19362] Documentation for len() fails to mention that
	it	works	on sets
In-Reply-To: <1382537154.14.0.377182050817.issue19362@psf.upfronthosting.co.za>
Message-ID: <489756252.104824019.1382537349780.JavaMail.root@zimbra10-e2.priv.proxad.net>


Antoine Pitrou added the comment:

> Perhaps it would be better to say that "the argument may be any
> object with a __len__, such as the commonly used Python sequence and
> container types str, bytes, tuple, list, dict, and set".  After all,
> there are other built in types it works on as well: bytearray,
> frozenset, memoryview.

__len__ is an implementation detail for experts. Beginners don't need
to know about __len__ in order to understand querying the length of
a container. Similarly, they don't need to know about ABCs to understand,
intuitively, what a container is ;-)

----------
title: Documentation for len() fails to mention that it works on sets -> Documentation for len() fails to mention that it works	on sets

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

From report at bugs.python.org  Wed Oct 23 16:22:11 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 23 Oct 2013 14:22:11 +0000
Subject: [docs] [issue19345] Unclear phrasing in whatsnew/3.4.rst
In-Reply-To: <1382435623.18.0.649588636826.issue19345@psf.upfronthosting.co.za>
Message-ID: <1382538131.71.0.308000186924.issue19345@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


----------
assignee: docs at python -> haypo

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

From report at bugs.python.org  Wed Oct 23 16:37:15 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 23 Oct 2013 14:37:15 +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: <1382539035.47.0.393791481945.issue19362@psf.upfronthosting.co.za>


R. David Murray added the comment:

I thought we were talking about the reference guide, not the tutorial?

----------

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

From report at bugs.python.org  Wed Oct 23 16:40:46 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 23 Oct 2013 14:40:46 +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: <1382539246.27.0.277543747789.issue19362@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Well, the patch is for the builtins documentation as well as len.__doc__.

----------

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

From report at bugs.python.org  Wed Oct 23 18:55:14 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 23 Oct 2013 16:55:14 +0000
Subject: [docs] [issue19345] Unclear phrasing in whatsnew/3.4.rst
In-Reply-To: <1382435623.18.0.649588636826.issue19345@psf.upfronthosting.co.za>
Message-ID: <3d4d3w737Gz7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 5e606f093d8f by Victor Stinner in branch 'default':
Close #19345: fix typo
http://hg.python.org/cpython/rev/5e606f093d8f

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

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

From report at bugs.python.org  Thu Oct 24 11:05:49 2013
From: report at bugs.python.org (Tim Golden)
Date: Thu, 24 Oct 2013 09:05:49 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>
Message-ID: <1382605549.44.0.490319616809.issue19273@psf.upfronthosting.co.za>


Tim Golden added the comment:

I've looked this over and, basically, +1. We could argue the toss back and forth over changes, but I think the changes do the right amount of cruft-clearing and avoid the danger of being a mere reflection of one person's aesthetic choices over another's.

If no-one objects, I propose to commit this in a day or two.

----------
assignee: docs at python -> tim.golden

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

From report at bugs.python.org  Thu Oct 24 11:57:27 2013
From: report at bugs.python.org (Tim Golden)
Date: Thu, 24 Oct 2013 09:57:27 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
	without	explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1382608647.33.0.278626744113.issue14112@psf.upfronthosting.co.za>


Changes by Tim Golden <mail at timgolden.me.uk>:


----------
nosy:  -tim.golden

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

From report at bugs.python.org  Thu Oct 24 15:52:14 2013
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2013 13:52:14 +0000
Subject: [docs] [issue19376] document that strptime() does not support the
	Feb 29 if	the format does not contain the year
In-Reply-To: <1382608937.44.0.992947795428.issue19376@psf.upfronthosting.co.za>
Message-ID: <1382622734.71.0.275233569891.issue19376@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
title: datetime.datetime.strptime without a year fails on Feb 29 -> document that strptime() does not support the Feb 29 if the format does not contain the year

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

From report at bugs.python.org  Thu Oct 24 16:05:01 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 24 Oct 2013 14:05:01 +0000
Subject: [docs] [issue19376] document that strptime() does not support the
	Feb 29 if	the format does not contain the year
In-Reply-To: <1382608937.44.0.992947795428.issue19376@psf.upfronthosting.co.za>
Message-ID: <1382623501.35.0.669787243652.issue19376@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Note: the actual explanation is that Feb 29th doesn't exist in *1900* which is the default year in strptime(). The same error happens if you ask for "Feb 30" or "Apr 31", it has nothing to do with leap years specifically.

In other words, the documentation looks sufficient to me as-is, and adding special wording for this would only make it longer than it should be.

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

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

From report at bugs.python.org  Thu Oct 24 16:09:23 2013
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 24 Oct 2013 14:09:23 +0000
Subject: [docs] [issue19376] document that strptime() does not support the
	Feb 29 if	the format does not contain the year
In-Reply-To: <1382608937.44.0.992947795428.issue19376@psf.upfronthosting.co.za>
Message-ID: <1382623763.65.0.156726206795.issue19376@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> In other words, the documentation looks sufficient to me as-is, and adding special wording for this would only make it longer than it should be.

Adding a note would not hurt.

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

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

From report at bugs.python.org  Thu Oct 24 16:57:29 2013
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 24 Oct 2013 14:57:29 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>
Message-ID: <1382626649.3.0.075043957036.issue19273@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Thanks, Tim!  There are a couple minor things I'd like to get into a new patch before it's committed (there are a couple tabs that should be spaces, and I'd like to add a very short note to the Sub-Projects header about sub-projects being contained in .vcxproj and .vcxproj.filters files).  I'll try to have a new patch up tonight or tomorrow.

----------

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

From report at bugs.python.org  Thu Oct 24 18:03:20 2013
From: report at bugs.python.org (Andrei Dorian Duma)
Date: Thu, 24 Oct 2013 16:03:20 +0000
Subject: [docs] [issue18959] Create a "Superseded modules" section in
	standard	library ToC
In-Reply-To: <1378559362.61.0.726437189184.issue18959@psf.upfronthosting.co.za>
Message-ID: <1382630600.51.0.547716731283.issue18959@psf.upfronthosting.co.za>


Andrei Dorian Duma added the comment:

The patch adds a 'Deprecated Modules' heading in the library's ToC and moves 'imp' & 'optparse' to the new entry.

----------
keywords: +patch
nosy: +andrei.duma
Added file: http://bugs.python.org/file32331/doc_add_a_deprecated_modules_heading.patch

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

From report at bugs.python.org  Thu Oct 24 18:12:12 2013
From: report at bugs.python.org (Andrei Dorian Duma)
Date: Thu, 24 Oct 2013 16:12:12 +0000
Subject: [docs] [issue18959] Create a "Superseded modules" section in
	standard	library ToC
In-Reply-To: <1378559362.61.0.726437189184.issue18959@psf.upfronthosting.co.za>
Message-ID: <1382631131.96.0.784406029906.issue18959@psf.upfronthosting.co.za>


Andrei Dorian Duma added the comment:

I changed 'Deprecated Modules' into 'Superseded Modules', as indicated by the issue title.

----------
Added file: http://bugs.python.org/file32332/doc_add_a_deprecated_modules_heading2.patch

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

From report at bugs.python.org  Thu Oct 24 18:13:21 2013
From: report at bugs.python.org (Matthew Earl)
Date: Thu, 24 Oct 2013 16:13:21 +0000
Subject: [docs] [issue19376] document that strptime() does not support the
	Feb 29 if	the format does not contain the year
In-Reply-To: <1382608937.44.0.992947795428.issue19376@psf.upfronthosting.co.za>
Message-ID: <1382631201.48.0.0410832374995.issue19376@psf.upfronthosting.co.za>


Matthew Earl added the comment:

Out of interest, what's the reason for accepting the time.strptime() version as a bug, but not datetime.datetime.strptime()? Is it that time.strptime() is meant to be a simple parsing from string to tuple (with minimal checks), whereas datetime.datetime.strptime() should represent an actual point in time, therefore extra validation is expected to occur?

If so I'm happy to either close or add a small note to the docs (I don't mind which.)

----------

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

From report at bugs.python.org  Thu Oct 24 18:29:45 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 24 Oct 2013 16:29:45 +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: <1382632185.92.0.554689732128.issue19362@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

> "Return the number of items of a container" sounds 
> simple and accurate to me.

I agree this would be best.

----------

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

From report at bugs.python.org  Thu Oct 24 19:08:23 2013
From: report at bugs.python.org (Alexander Belopolsky)
Date: Thu, 24 Oct 2013 17:08:23 +0000
Subject: [docs] [issue19376] document that strptime() does not support the
	Feb 29 if	the format does not contain the year
In-Reply-To: <1382608937.44.0.992947795428.issue19376@psf.upfronthosting.co.za>
Message-ID: <1382634503.77.0.716938480537.issue19376@psf.upfronthosting.co.za>


Alexander Belopolsky added the comment:

> what's the reason for accepting the time.strptime()
> version as a bug, but not datetime.datetime.strptime()?

In case of time.strptime(), we have an option of returning (1900, 2, 29, ..) which while not being a valid date, is a valid (time)tuple:

>>> time.mktime((1900, 2, 29, 0, 0, 0, 0, 0, 0))
-2203873200.0

The time module treats 1900-02-29 as 1900-03-01:

>>> time.mktime((1900, 3, 1, 0, 0, 0, 0, 0, 0))
-2203873200.0


Datetime is stricter than that:

>>> datetime(1900, 2, 29)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: day is out of range for month


There is no valid datetime value that can reasonably be returned from datetime.strptime('Feb 29', '%b %d').

----------

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

From report at bugs.python.org  Thu Oct 24 21:14:28 2013
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 24 Oct 2013 19:14:28 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>
Message-ID: <1382642067.95.0.958018005047.issue19273@psf.upfronthosting.co.za>


Zachary Ware added the comment:

Here's the new patch, a few tabs converted, a few trailing spaces removed, and one sentence added to the Sub-projects section description.

----------
Added file: http://bugs.python.org/file32336/pcbuild_readme.v2.diff

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

From report at bugs.python.org  Thu Oct 24 21:38:06 2013
From: report at bugs.python.org (Tim Golden)
Date: Thu, 24 Oct 2013 19:38:06 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1382642067.95.0.958018005047.issue19273@psf.upfronthosting.co.za>
Message-ID: <52697715.9040604@timgolden.me.uk>


Tim Golden added the comment:

Thanks, Zachary. Do you see this going against just tip, or should it be 
backported to 3.3 / 2.7? (I'm not sure how well the latter would be 
received, truth be told).

----------

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

From report at bugs.python.org  Thu Oct 24 21:55:05 2013
From: report at bugs.python.org (Zachary Ware)
Date: Thu, 24 Oct 2013 19:55:05 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>
Message-ID: <1382644505.23.0.951615248636.issue19273@psf.upfronthosting.co.za>


Zachary Ware added the comment:

This patch will only apply to tip.  There would need to be some changes to backport to 3.3 and I haven't actually looked at 2.7, but I expect it would require extensive changes that probably wouldn't be worth it.  There are a few factual errors in 3.3 (such as supported platforms including Win2k) that should probably be corrected (and likely some in 2.7 as well), but that could be a separate issue.

I think it would be best not to backport this patch, and I'll open a separate issue to correct any errors in 2.7/3.3.

----------

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

From report at bugs.python.org  Thu Oct 24 21:58:07 2013
From: report at bugs.python.org (Tim Golden)
Date: Thu, 24 Oct 2013 19:58:07 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1382644505.23.0.951615248636.issue19273@psf.upfronthosting.co.za>
Message-ID: <52697BC8.6060309@timgolden.me.uk>


Tim Golden added the comment:

Fine. I'll commit it later. (Probably tomorrow at this point)

----------

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

From report at bugs.python.org  Fri Oct 25 07:57:11 2013
From: report at bugs.python.org (Stefan Behnel)
Date: Fri, 25 Oct 2013 05:57:11 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <1295653779.62.0.836506069174.issue10977@psf.upfronthosting.co.za>
Message-ID: <1382680631.72.0.241308159941.issue10977@psf.upfronthosting.co.za>


Stefan Behnel added the comment:

-1 on any changes that make the specific C-API functions less specific. They are perfectly adequate for gaining speed in well defined situations.

+0 on any changes that special case concrete types in abstract calls if they prove to be worth the hassle.

+1 for making sure CPython does not accidentally exclude subclasses internally for anything that's provided by users.

+1 on CPython being the wrong place to work around this for external code. If extensions use the wrong function, *they* must be fixed. At most, there might be a documentation issue hidden here.

Also, we should be careful with adding yet another substantial set of C-API functions. It's not clear to me that they are really needed in practice.

----------
nosy: +scoder

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

From report at bugs.python.org  Fri Oct 25 10:01:37 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 25 Oct 2013 08:01:37 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>
Message-ID: <3d5d7J1JFzz7LjP@mail.python.org>


Roundup Robot added the comment:

New changeset 212b4b61fa05 by Tim Golden in branch 'default':
Closes issue #19273: clean up the pcbuild readme.txt (Patch by Zachary Ware)
http://hg.python.org/cpython/rev/212b4b61fa05

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

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

From report at bugs.python.org  Fri Oct 25 11:30:56 2013
From: report at bugs.python.org (Tim Golden)
Date: Fri, 25 Oct 2013 09:30:56 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>
Message-ID: <1382693456.57.0.826327360503.issue19273@psf.upfronthosting.co.za>


Tim Golden added the comment:

Done. Thanks for the patch.

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

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

From report at bugs.python.org  Fri Oct 25 17:56:06 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 25 Oct 2013 15:56:06 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <1382680631.72.0.241308159941.issue10977@psf.upfronthosting.co.za>
Message-ID: <CADiSq7c02dG84EZAJ=iXArZdH1Kf1=9ci7=-qLZ0FSiDLC5KBQ@mail.gmail.com>


Nick Coghlan added the comment:

The problem we're trying to solve is CPython *silently* breaking subclass
invariants, which is what the concrete APIs currently do. At the moment,
trying to swap out dicts with ordered dicts in various places will corrupt
the ordered dict instead of calling the appropriate subclass methods or
throwing a type error.

----------

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

From report at bugs.python.org  Fri Oct 25 18:18:05 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 25 Oct 2013 16:18:05 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <CADiSq7c02dG84EZAJ=iXArZdH1Kf1=9ci7=-qLZ0FSiDLC5KBQ@mail.gmail.com>
Message-ID: <1382717852.2523.0.camel@fsol>


Antoine Pitrou added the comment:

> The problem we're trying to solve is CPython *silently* breaking subclass
> invariants, which is what the concrete APIs currently do.

To be clear: the problem is with CPython calling the concrete APIs when
it shouldn't, rather than with the concrete APIs not behaving properly.

----------

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

From report at bugs.python.org  Fri Oct 25 18:23:05 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 25 Oct 2013 16:23:05 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <1382717852.2523.0.camel@fsol>
Message-ID: <CADiSq7e6BOV=jpteLD-bsDt+8TD340Lgda-CTjX_y7kyJt9ggA@mail.gmail.com>


Nick Coghlan added the comment:

On 26 Oct 2013 02:18, "Antoine Pitrou" <report at bugs.python.org> wrote:
>
>
> Antoine Pitrou added the comment:
>
> > The problem we're trying to solve is CPython *silently* breaking
subclass
> > invariants, which is what the concrete APIs currently do.
>
> To be clear: the problem is with CPython calling the concrete APIs when
> it shouldn't, rather than with the concrete APIs not behaving properly.

The boilerplate required to use them correctly renders them broken in my
view, particularly when they silently corrupt internal subclass state when
misused instead of throwing an exception.

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

----------

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

From report at bugs.python.org  Fri Oct 25 18:25:21 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Fri, 25 Oct 2013 16:25:21 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <CADiSq7e6BOV=jpteLD-bsDt+8TD340Lgda-CTjX_y7kyJt9ggA@mail.gmail.com>
Message-ID: <1382718289.2523.2.camel@fsol>


Antoine Pitrou added the comment:

> > To be clear: the problem is with CPython calling the concrete APIs when
> > it shouldn't, rather than with the concrete APIs not behaving properly.
> 
> The boilerplate required to use them correctly renders them broken in my
> view, particularly when they silently corrupt internal subclass state when
> misused instead of throwing an exception.

IMO the boilerplate should actually be included inside the abstract
APIs, so as to automatically enable optimized shortcuts when possible.

----------

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

From report at bugs.python.org  Fri Oct 25 18:34:31 2013
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 25 Oct 2013 16:34:31 +0000
Subject: [docs] [issue19391] Fix PCbuild/readme.txt in 2.7 and 3.3
Message-ID: <1382718870.17.0.951198917656.issue19391@psf.upfronthosting.co.za>


New submission from Zachary Ware:

As discussed in issue19273, here are a pair of patches that correct factual errors in PCbuild/readme.txt in both 2.7 and 3.3.

The 3.3 patch makes the following changes:
- Remove Win2k mentions, it is not supported (Tcl nmake command also adjusted)
- MSVCRT9 -> MSVCRT10
- SQLite 3.7.4 -> 3.7.12, remove "(see below)" with nothing to see
- .vcproj -> .vcxproj, all occurrences 
- _bz2.vcxproj isn't as magical as it was made out to be, and it can clean itself
- nasmw -> nasm
- Remove untrue part of Building for Itanium section
- Update msdn link
- .vsprops -> .props
- Trim trailing space

Due to the large number of lines in the diff due to trailing space, I'll also be attaching a patch created by `hg diff -w` for ease of review.

----------
assignee: docs at python
components: Documentation, Windows
files: pcbuild_readme-3.3.diff
keywords: patch
messages: 201253
nosy: brian.curtin, christian.heimes, docs at python, ezio.melotti, loewis, python-dev, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Fix PCbuild/readme.txt in 2.7 and 3.3
type: enhancement
versions: Python 2.7, Python 3.3
Added 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  Fri Oct 25 18:34:51 2013
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 25 Oct 2013 16:34:51 +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: <1382718891.84.0.627274898531.issue19391@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Oct 25 18:36:28 2013
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 25 Oct 2013 16:36:28 +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: <1382718987.76.0.867178203057.issue19391@psf.upfronthosting.co.za>


Zachary Ware added the comment:

The 2.7 patch makes the following changes:
- python30.dll -> python27.dll
- remove "(see below)" from _bsddb and _sqlite3 which have nothing to see below
- bz2.vcproj isn't as magical as it made out to be, and it can clean itself
- nasmw -> nasm
- Remove untrue part of Building for Itanium section
- Update msdn link
- Trim trailing space

There is also a diff -w patch for 2.7, due to the large number of lines with trailing space.

----------
Added 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  Fri Oct 25 18:36:42 2013
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 25 Oct 2013 16:36: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: <1382719002.98.0.515720561063.issue19391@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Oct 25 18:44:42 2013
From: report at bugs.python.org (Stefan Behnel)
Date: Fri, 25 Oct 2013 16:44:42 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <CADiSq7e6BOV=jpteLD-bsDt+8TD340Lgda-CTjX_y7kyJt9ggA@mail.gmail.com>
Message-ID: <526A9FB6.5060503@behnel.de>


Stefan Behnel added the comment:

Nick Coghlan added the comment:
> Antoine Pitrou added the comment:
>> To be clear: the problem is with CPython calling the concrete APIs when
>> it shouldn't, rather than with the concrete APIs not behaving properly.
> 
> The boilerplate required to use them correctly renders them broken in my
> view

I think we disagree here. There is no boilerplate at all involved, as long
as its guaranteed that they are being called on the correct type of object.
User code may provide that guarantee either implicitly or explicitly, and
only the explicit way involves additional code (such as a type check). The
implicit way (that simply knows the exact type) would suffer from any code
additions to the fast paths in the specific C-API functions.

> particularly when they silently corrupt internal subclass state when
> misused instead of throwing an exception.

It has bothered me more than once that even the fast paths in those
functions usually contain type checks, which often means that the type
check is being executed twice: once as a special casing check before
calling the function and once as a safety check after entering it. As long
as the functions are being used correctly, the second check is just useless
code that unnecessarily takes time.

IMHO, it would be nice to have those internal type checks enabled *only*
for debug builds, although even then, there may be legitimate usages that
call these functions on subtypes (such as when called from within a well
defined subtype implementation, as you mentioned).

----------

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

From report at bugs.python.org  Fri Oct 25 19:00:54 2013
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 25 Oct 2013 17:00:54 +0000
Subject: [docs] [issue19392] document importlib.reload() requires __loader__
	to be	defined
Message-ID: <1382720454.45.0.30306791962.issue19392@psf.upfronthosting.co.za>


New submission from Brett Cannon:

Make sure importlib.reload() (and by extension imp.reload()) mention that __loader__ must be defined as well as __name__.

----------
assignee: docs at python
components: Documentation
messages: 201259
nosy: brett.cannon, docs at python
priority: normal
severity: normal
status: open
title: document importlib.reload() requires __loader__ to be defined
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Oct 25 19:02:44 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Fri, 25 Oct 2013 17:02:44 +0000
Subject: [docs] [issue10977] Concrete object C API considered harmful to
	subclasses	of builtin types
In-Reply-To: <526A9FB6.5060503@behnel.de>
Message-ID: <CADiSq7fV3KHkb1oH31z0q8DYf2vLtYOPYcjKqeCsQdSowfFkiQ@mail.gmail.com>


Nick Coghlan added the comment:

Keep in mind that part of the problem here is finding stdlib code that
needs to be fixed to handle subclasses correctly. The existing APIs have
permitted use with subclasses for years but are, in fact, the wrong tool
for that in many cases.

The problem to be solved isn't "this code should handle ducktyping" but,
"this code should either reject subclasses or else handle them without
corrupting them". Using the same API for both external invocation and for
subclasses calling up to the parent is a problem. For code in critical
paths, doing the same type check twice is also a problem.

----------

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

From report at bugs.python.org  Fri Oct 25 19:24:37 2013
From: report at bugs.python.org (Eric Snow)
Date: Fri, 25 Oct 2013 17:24:37 +0000
Subject: [docs] [issue19392] document importlib.reload() requires __loader__
	to be	defined
In-Reply-To: <1382720454.45.0.30306791962.issue19392@psf.upfronthosting.co.za>
Message-ID: <1382721877.84.0.768668015814.issue19392@psf.upfronthosting.co.za>


Changes by Eric Snow <ericsnowcurrently at gmail.com>:


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

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

From report at bugs.python.org  Fri Oct 25 19:49:32 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 25 Oct 2013 17:49:32 +0000
Subject: [docs] [issue19392] document importlib.reload() requires __loader__
	to be	defined
In-Reply-To: <1382720454.45.0.30306791962.issue19392@psf.upfronthosting.co.za>
Message-ID: <3d5tB34K75z7LkB@mail.python.org>


Roundup Robot added the comment:

New changeset f575f6298eb1 by Brett Cannon in branch '3.3':
Issue #19392: Document that imp.reload() now relies on __loader__
http://hg.python.org/cpython/rev/f575f6298eb1

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

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

From report at bugs.python.org  Fri Oct 25 19:53:56 2013
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 25 Oct 2013 17:53:56 +0000
Subject: [docs] [issue19392] document importlib.reload() requires __loader__
	to be	defined
In-Reply-To: <1382720454.45.0.30306791962.issue19392@psf.upfronthosting.co.za>
Message-ID: <1382723636.13.0.81120078808.issue19392@psf.upfronthosting.co.za>


Brett Cannon added the comment:

importlib.reload() already states that the loader is reused, so this only required imp.reload() to be updated.

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

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

From report at bugs.python.org  Sat Oct 26 02:14:45 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 26 Oct 2013 00:14:45 +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: <1382746485.14.0.968842146028.issue19362@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I would prefer 'collections with a known size' but 'collections' should be good enough for the doc string. The manual can follow with examples.

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

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

From report at bugs.python.org  Sat Oct 26 10:40:20 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2013 08:40:20 +0000
Subject: [docs] [issue19405] Fix outdated comments in the _sre module
Message-ID: <1382776819.97.0.0101067680791.issue19405@psf.upfronthosting.co.za>


New submission from Serhiy Storchaka:

The _sre module contains comments which refers to 16-bit SRE_CODE. Now SRE_CODE is 32-bit.

Antoine partially reviewed this change in issue19329.

----------
assignee: docs at python
components: Documentation, Regular Expressions
files: sre_comments.patch
keywords: patch
messages: 201330
nosy: docs at python, ezio.melotti, mrabarnett, pitrou, serhiy.storchaka
priority: normal
severity: normal
stage: patch review
status: open
title: Fix outdated comments in the _sre module
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file32368/sre_comments.patch

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

From report at bugs.python.org  Sat Oct 26 19:18:30 2013
From: report at bugs.python.org (Devin Jeanpierre)
Date: Sat, 26 Oct 2013 17:18:30 +0000
Subject: [docs] [issue19411] binascii.hexlify docs say it returns a string
	(it	returns bytes)
Message-ID: <1382807910.82.0.748740374727.issue19411@psf.upfronthosting.co.za>


New submission from Devin Jeanpierre:

http://docs.python.org/3.4/library/binascii.html#binascii.hexlify

----------
assignee: docs at python
components: Documentation
messages: 201376
nosy: Devin Jeanpierre, docs at python
priority: normal
severity: normal
status: open
title: binascii.hexlify docs say it returns a string (it returns bytes)
versions: Python 3.1, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sat Oct 26 22:25:05 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Sat, 26 Oct 2013 20:25:05 +0000
Subject: [docs] [issue19405] Fix outdated comments in the _sre module
In-Reply-To: <1382776819.97.0.0101067680791.issue19405@psf.upfronthosting.co.za>
Message-ID: <1382819105.36.0.423081926999.issue19405@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Looks good to me, except that it probably shouldn't apply to 2.7 (does it?).

----------

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

From report at bugs.python.org  Sat Oct 26 22:41:39 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sat, 26 Oct 2013 20:41:39 +0000
Subject: [docs] [issue19405] Fix outdated comments in the _sre module
In-Reply-To: <1382776819.97.0.0101067680791.issue19405@psf.upfronthosting.co.za>
Message-ID: <1382820099.12.0.833393558408.issue19405@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

In 2.7 SRE_CODE is 32-bit too (since issue1160). Only last chunk in Lib/sre_compile.py patch shouldn't apply to 2.7.

----------

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

From report at bugs.python.org  Sun Oct 27 07:09:34 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 27 Oct 2013 06:09:34 +0000
Subject: [docs] [issue19405] Fix outdated comments in the _sre module
In-Reply-To: <1382776819.97.0.0101067680791.issue19405@psf.upfronthosting.co.za>
Message-ID: <3d6pYV13Gqz7Lnm@mail.python.org>


Roundup Robot added the comment:

New changeset b7f71babc622 by Serhiy Storchaka in branch '2.7':
Issue #19405: Fixed outdated comments in the _sre module.
http://hg.python.org/cpython/rev/b7f71babc622

New changeset 220e3e40d176 by Serhiy Storchaka in branch '3.3':
Issue #19405: Fixed outdated comments in the _sre module.
http://hg.python.org/cpython/rev/220e3e40d176

New changeset d6f427f94d85 by Serhiy Storchaka in branch 'default':
Issue #19405: Fixed outdated comments in the _sre module.
http://hg.python.org/cpython/rev/d6f427f94d85

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

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

From report at bugs.python.org  Sun Oct 27 07:25:08 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2013 06:25:08 +0000
Subject: [docs] [issue19405] Fix outdated comments in the _sre module
In-Reply-To: <1382776819.97.0.0101067680791.issue19405@psf.upfronthosting.co.za>
Message-ID: <1382855108.36.0.740504326682.issue19405@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Oct 27 14:18:25 2013
From: report at bugs.python.org (Roy Smith)
Date: Sun, 27 Oct 2013 13:18:25 +0000
Subject: [docs] [issue19416] NNTP page has incorrect links
Message-ID: <1382879905.74.0.020204746466.issue19416@psf.upfronthosting.co.za>


New submission from Roy Smith:

http://docs.python.org/2/library/nntplib.html contains intra-page references such as:

NNTP.next()
Send a NEXT command. Return as for stat().

The problem is that the link for "stat" points to the stat module (i.e. http://docs.python.org/2/library/stat.html#module-stat).  It should be pointing to the NNTP.stat() entry on this page.

The problem exists for :

NNTP.next()
NNTP.last()
NNTP.head(id)
NNTP.body(id[, file])
NNTP.article(id)

and maybe some others I missed.

----------
assignee: docs at python
components: Documentation
messages: 201456
nosy: docs at python, roysmith
priority: normal
severity: normal
status: open
title: NNTP page has incorrect links
versions: Python 2.7

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

From report at bugs.python.org  Sun Oct 27 15:28:11 2013
From: report at bugs.python.org (Ramchandra Apte)
Date: Sun, 27 Oct 2013 14:28:11 +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: <1382884090.92.0.138824043665.issue19362@psf.upfronthosting.co.za>


Ramchandra Apte added the comment:

I also prefer collection.

----------
nosy: +Ramchandra Apte

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

From report at bugs.python.org  Sun Oct 27 17:38:54 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 27 Oct 2013 16:38:54 +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: <1382891934.9.0.644301077664.issue19411@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/issue19411>
_______________________________________

From report at bugs.python.org  Sun Oct 27 17:46:55 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 27 Oct 2013 16:46:55 +0000
Subject: [docs] [issue17668] re.split loses characters matching ungrouped
	parts of a	pattern
In-Reply-To: <1365445138.49.0.018016443065.issue17668@psf.upfronthosting.co.za>
Message-ID: <1382892415.68.0.132455158542.issue17668@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Oct 27 19:01:00 2013
From: report at bugs.python.org (Tim Golden)
Date: Sun, 27 Oct 2013 18:01:00 +0000
Subject: [docs] [issue19273] Update PCbuild/readme.txt
In-Reply-To: <1381956724.6.0.425752006149.issue19273@psf.upfronthosting.co.za>
Message-ID: <1382896860.33.0.580101413167.issue19273@psf.upfronthosting.co.za>


Changes by Tim Golden <mail at timgolden.me.uk>:


----------
stage: patch review -> committed/rejected

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

From report at bugs.python.org  Mon Oct 28 03:07:15 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 28 Oct 2013 02:07:15 +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: <1382926035.58.0.284599717235.issue19412@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

OK, since David agrees the updated behaviour of the requires_docstring decorator makes sense (i.e. skipping __doc__ related tests whenever the docstrings are unreliable, regardless of the reason), I'm morphing this to be a test.support docs issue.

At least requires_docstring should be documented, but it may be worth documenting HAVE_DOCSTRINGS and MISSING_C_DOCSTRINGS as well.

----------
assignee:  -> docs at python
components: +Documentation -Tests
nosy: +docs at python
title: Add a test.support decorator for tests that require C level docstrings -> Add docs for test.support.requires_docstrings decorator

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

From report at bugs.python.org  Mon Oct 28 12:06:10 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 28 Oct 2013 11:06:10 +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: <1382958370.31.0.763386457677.issue19411@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


----------
stage:  -> needs patch
versions:  -Python 3.1, Python 3.2

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

From cocoatomo77 at gmail.com  Mon Oct 14 07:29:03 2013
From: cocoatomo77 at gmail.com (tomo cocoa)
Date: Mon, 14 Oct 2013 05:29:03 -0000
Subject: [docs] typo in datetime library document
Message-ID: <CAN_7T0+7rNfiAPVpFoRKtrBDfPVRWWn9uqMB2PZmFmcNO_kY8g@mail.gmail.com>

Hello,

I am a Japanese translator of Python document.

This mail is a report for typo in the datetime library document.

http://docs.python.org/3.3/library/datetime.html#strftime-and-strptime-behavior

The first note on the formatting directive table contains a word 'js_JP',
but it should be 'ja_JP'.
As far as I know, Japanese language is publicly used in Japan :)


Regards,

cocoatomo

-- 
class Cocoatomo:
    name = 'cocoatomo'
    email_address = 'cocoatomo77 at gmail.com'
    twitter_id = '@cocoatomo'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131014/62089de9/attachment-0001.html>

From mikael_monnier at hotmail.com  Thu Oct 17 15:44:12 2013
From: mikael_monnier at hotmail.com (mikael monnier)
Date: Thu, 17 Oct 2013 15:44:12 +0200
Subject: [docs] =?iso-8859-1?q?rapport_de_bug/_m=E9lange_de_traduction?=
Message-ID: <DUB125-W447CF3869D875C99395950EB050@phx.gbl>

Bonjour,
sur la page
http://www.afpy.org/doc/python/2.7/tutorial/classes.html
il existe un m?lange fran?ais/anglais avec plus ou moins de duplications.
(au 17/10/2013 15h41)
exemple : "spring into existence" etc.
Cordialement
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131017/786a5c73/attachment-0001.html>

From keith.briggs at bt.com  Mon Oct 21 15:01:39 2013
From: keith.briggs at bt.com (keith.briggs at bt.com)
Date: Mon, 21 Oct 2013 14:01:39 +0100
Subject: [docs] http://www.python.org/doc//current/
Message-ID: <BA02A06A22A52C449E4B5EE4CE1DBC3F9C69C74595@EMV66-UKRD.domain1.systemhost.net>

Why does http://www.python.org/doc//current/ point to the old Python v2.6.5c2 documentation?

Keith



From Bill.Melvin at esc.edu  Tue Oct 22 22:11:16 2013
From: Bill.Melvin at esc.edu (Bill.Melvin at esc.edu)
Date: Tue, 22 Oct 2013 16:11:16 -0400
Subject: [docs] re.split suggestion
Message-ID: <OFB16A7DD7.79FE7C52-ON85257C0C.006D1EFC-85257C0C.006EE5AD@esc.edu>

Hi Docs,

I just tripped myself up with the maxsplit parameter to re.split while 
parsing SPF records ...

>>> max = 2
>>> re.split(':','ip6:fe80:dead:beef:cafe::36',maxsplit=max)
['ip6', 'fe80', 'dead:beef:cafe::36']
>>>
>>> max = 1
>>> re.split(':','ip6:fe80:dead:beef:cafe::36',maxsplit=max)
['ip6', 'fe80:dead:beef:cafe::36']

Re-re-re-reading the docs I see now that maxsplit is in fact the maximum 
number of _splits_ that occur not the number of fields that result.

FWIW I am relatively new to Python so my terminology will be off but does 
a patch something like the appended make sense?

tnx,

/b

http://docs.python.org/n.m/_sources/library/re.txt

$ diff -uw re.orig re.txt
--- re.orig     2013-10-22 16:01:50.876739700 -0400
+++ re.txt      2013-10-22 16:02:39.752052500 -0400
@@ -589,7 +589,7 @@
    Split *string* by the occurrences of *pattern*.  If capturing 
parentheses are
    used in *pattern*, then the text of all groups in the pattern are also 
returned
    as part of the resulting list. If *maxsplit* is nonzero, at most 
*maxsplit*
-   splits occur, and the remainder of the string is returned as the final 
element
+   splits occur, creating a list *maxsplit+1* elements in length with the 
remainder of the string is returned as the final element
    of the list. ::

       >>> re.split('\W+', 'Words, words, words.')
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131022/3acb1fd0/attachment-0001.html>

From keith at geoffreybrown.com  Wed Oct 23 09:52:45 2013
From: keith at geoffreybrown.com (Keith Brown)
Date: Wed, 23 Oct 2013 09:52:45 +0200
Subject: [docs] Library Reference Changes
Message-ID: <5267804D.9040302@geoffreybrown.com>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131023/bbfc7517/attachment-0001.html>

From staticd.growthecommons at gmail.com  Thu Oct 24 07:47:13 2013
From: staticd.growthecommons at gmail.com (staticd)
Date: Thu, 24 Oct 2013 11:17:13 +0530
Subject: [docs] Pickle (0-2) is reading is *not* backward compatible
Message-ID: <CAJysKErRxnvgFi2pTiFG=4hnYezcK2xFFW3DGSP+UDoMjnBx7Q@mail.gmail.com>

Pickle in version 3.x cannot read any 2.x pickles if they contain any
binary data. (e.g. numpy arrays) This has been a bug that has been open for
the last 4 years. So there will be many installations of python 3 affected
by this.(http://bugs.python.org/issue6784)

I think it is essential that the documentation makes it clear that pickle
is *not* backwards compatible for reading old data. It will save a lot of
grief when debugging.

 It might also be a factor when people choose a persistence format for
their data if they have to support multiple versions of python.

BTW, I'm no great programmer but I would love to contribute to the python
docs (like processing requests that come on this mailing list) and wiki.
how can I sign on for that?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131024/6cf46d7f/attachment-0001.html>

From grgoffe at yahoo.com  Thu Oct 24 21:09:25 2013
From: grgoffe at yahoo.com (George R Goffe)
Date: Thu, 24 Oct 2013 12:09:25 -0700 (PDT)
Subject: [docs] A possible Python bug.
Message-ID: <1382641765.29536.YahooMailNeo@web162103.mail.bf1.yahoo.com>

Hi,

I seem to recall reading something about this a while ago but don't recall exactly where.

I build Python 2.7 and 3.x from the repositories and both exhibit the same behavior:



python
Python 2.7.3 (default, Jul 24 2012, 11:41:40) 
[GCC 4.6.3 20120306 (Red Hat 4.6.3-2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> 182.12-95.80
86.32000000000001


/tools/python/cpython# ./python 
Python 3.4.0a0 (default:f315fecdfeb8, Apr? 6 2013, 13:13:19) 
[GCC 4.9.0 20130405 (experimental)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> 182.12-95.80
86.32000000000001

the bc utility on my system produces what I would term the correct answer:

bc
bc 1.06.95
Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'. 
182.12-95.80
86.32


Am I missing something?

If this is a bug, I would be most willing to test any code changes that you might come up with.


Regards,

George...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131024/b561336b/attachment-0001.html>

From jleykam at gmail.com  Fri Oct 25 09:43:51 2013
From: jleykam at gmail.com (Jacqueline Leykam)
Date: Fri, 25 Oct 2013 18:43:51 +1100
Subject: [docs] Documentation Error: curses.newwin
Message-ID: <CAN53-rq2agYDt3VTaKM9+r6NDJUqAXc1Mj5T5Niy6YO9=C59Yw@mail.gmail.com>

Hello,

I have encountered an error in the Python Curses documentation, on this
page: http://docs.python.org/3.3/library/curses.html#curses.newwin

The curses.newwin documentation states that when the function is called
with two arguments they are interpreted as the begin_y and begin_x
attributes of the created window. In fact, the function interprets them as
the window's nlines and ncols attributes (respectively). This error seems
to be present in all versions of the documentation available.

Regards,
Jacqueline Leykam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131025/eb8a4298/attachment-0001.html>

From andres.soto.v at gmail.com  Fri Oct 25 10:39:25 2013
From: andres.soto.v at gmail.com (Andres Soto)
Date: Fri, 25 Oct 2013 10:39:25 +0200
Subject: [docs] problem using pickle
Message-ID: <CALB+hXTdepZYEOQ8-o8F7oroeCYJx1NUK=kw6xJAZMciamO_GA@mail.gmail.com>

Hi,
I am trying to save a Naive Bayes classifier with cPickle (as it says in
NLTK: Storing Taggers http://nltk.org/book/ch05.html), but I got an error.
These are the function code I used to save/load it:

import cPickle as cp

def salva_fichC(fich1,data):
    fich=fich1+'.dmp'
    f = open(fich, 'wb')
    cp.dump(data, f,-1)
    f.close()

def carga_fichC(fich1):
    fich=fich1+'.dmp'
    f = open(fich, 'rb')
    data = cp.load(f)
    f.close()
    return data

I have tried also with pickle, with and without -1 in dump
Can you help me? Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131025/9cf10976/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Captura de pantalla 2013-10-25 a la(s) 10.30.50.png
Type: image/png
Size: 33588 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20131025/9cf10976/attachment-0001.png>

From augustusfrancis at gmail.com  Fri Oct 25 18:23:32 2013
From: augustusfrancis at gmail.com (Augustus Francis)
Date: Fri, 25 Oct 2013 21:53:32 +0530
Subject: [docs] Documentation rectification
Message-ID: <CACSwGANG-8yEPouOgJiHDTSA1p0v0fAHkooL4YvUtqYGp+DVGQ@mail.gmail.com>

Page: http://www.docs.python.org/2/tutorial/introduction.html

print b won't work. It should be print (b)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131025/b15f5abc/attachment.html>

From cocoatomo77 at gmail.com  Sun Oct 27 13:36:30 2013
From: cocoatomo77 at gmail.com (tomo cocoa)
Date: Sun, 27 Oct 2013 21:36:30 +0900
Subject: [docs] Confusing text which may came from a work to update documents
Message-ID: <CAN_7T0Lqq=FwJ=btQs_WCmz-TeaFvYnNNj_7Xwn+4YTGuSYWjw@mail.gmail.com>

Hello,

I am a Japanese translator of Python documentation.

In the third paragraph of the section "Reading and Writing Unicode Data"
(
http://docs.python.org/3.3/howto/unicode.html#reading-and-writing-unicode-data
),
there is some confusing text: "open a file, read an 8-bit bytes object from
it, and convert the string with bytes.decode(encoding)"

Words "the string" in it may refer to "an 8-bit bytes object", but usually
we do not call a bytes object "string". This sentence confuses me.


To know why and where such a strange word came from, I got back into Python
documentation on version 2.7
(
http://docs.python.org/2.7/howto/unicode.html#reading-and-writing-unicode-data
).
On this version, a corresponding old text is "open a file, read an 8-bit
string from it, and convert the string with unicode(str, encoding)".
As you might notice, the object read from a file is "string", but not
"bytes" which appeared in Python 3.0.
When this paragraph was converted, words "the string" might be missed and
left.


As my conclusion, I suggest that words "the string" should be "the bytes".


Regards,
cocoatomo


-- 
class Cocoatomo:
    name = 'cocoatomo'
    email_address = 'cocoatomo77 at gmail.com'
    twitter_id = '@cocoatomo'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131027/e1093901/attachment.html>

From georg at python.org  Tue Oct 29 08:05:43 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 29 Oct 2013 08:05:43 +0100
Subject: [docs] typo in datetime library document
In-Reply-To: <CAN_7T0+7rNfiAPVpFoRKtrBDfPVRWWn9uqMB2PZmFmcNO_kY8g@mail.gmail.com>
References: <CAN_7T0+7rNfiAPVpFoRKtrBDfPVRWWn9uqMB2PZmFmcNO_kY8g@mail.gmail.com>
Message-ID: <526F5E47.8090208@python.org>

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

Am 14.10.2013 07:28, schrieb tomo cocoa:
> Hello,
> 
> I am a Japanese translator of Python document.
> 
> This mail is a report for typo in the datetime library document.
> 
> http://docs.python.org/3.3/library/datetime.html#strftime-and-strptime-behavior
>
>  The first note on the formatting directive table contains a word 'js_JP',
> but it should be 'ja_JP'. As far as I know, Japanese language is publicly
> used in Japan :)

Hi,

thanks for the report, this is now fixed and will be online soon.

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

iEYEARECAAYFAlJvXkcACgkQN9GcIYhpnLD9OQCfdsnrJ8gLKSrG2xusILYMlofQ
SIYAoIkCEIq3O+KSo/cmjI4ULEhdgp1r
=H/eK
-----END PGP SIGNATURE-----

From georg at python.org  Tue Oct 29 08:08:02 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 29 Oct 2013 08:08:02 +0100
Subject: [docs] A possible Python bug.
In-Reply-To: <1382641765.29536.YahooMailNeo@web162103.mail.bf1.yahoo.com>
References: <1382641765.29536.YahooMailNeo@web162103.mail.bf1.yahoo.com>
Message-ID: <526F5ED2.40408@python.org>

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

Am 24.10.2013 21:09, schrieb George R Goffe:
> Hi,
> 
> I seem to recall reading something about this a while ago but don't recall 
> exactly where.
> 
> I build Python 2.7 and 3.x from the repositories and both exhibit the same
> behavior:
> 
> 
> python Python 2.7.3 (default, Jul 24 2012, 11:41:40) [GCC 4.6.3 20120306
> (Red Hat 4.6.3-2)] on linux2 Type "help", "copyright", "credits" or
> "license" for more information.
>>>> 182.12-95.80
> 86.32000000000001
> 
> /tools/python/cpython# ./python Python 3.4.0a0 (default:f315fecdfeb8, Apr
> 6 2013, 13:13:19) [GCC 4.9.0 20130405 (experimental)] on linux Type "help",
> "copyright", "credits" or "license" for more information.
>>>> 182.12-95.80
> 86.32000000000001
> 
> the bc utility on my system produces what I would term the correct answer:
> 
> bc bc 1.06.95 Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006 Free
> Software Foundation, Inc. This is free software with ABSOLUTELY NO
> WARRANTY. For details type `warranty'. 182.12-95.80 86.32
> 
> Am I missing something?
> 
> If this is a bug, I would be most willing to test any code changes that
> you might come up with.

Hi George,

this is an innate limitation of floating-point arithmetic.
Please have a look at http://docs.python.org/2/tutorial/floatingpoint.html
for an explanation of this behavior.

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

iEYEARECAAYFAlJvXtIACgkQN9GcIYhpnLBS1ACgiEwVQWFpgu8udACdwiZ6qRkw
7ikAoKFXpogxoEDImMlxN1bX3lk2872T
=xNk8
-----END PGP SIGNATURE-----

From georg at python.org  Tue Oct 29 08:10:17 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 29 Oct 2013 08:10:17 +0100
Subject: [docs] Documentation Error: curses.newwin
In-Reply-To: <CAN53-rq2agYDt3VTaKM9+r6NDJUqAXc1Mj5T5Niy6YO9=C59Yw@mail.gmail.com>
References: <CAN53-rq2agYDt3VTaKM9+r6NDJUqAXc1Mj5T5Niy6YO9=C59Yw@mail.gmail.com>
Message-ID: <526F5F59.90102@python.org>

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

Am 25.10.2013 09:43, schrieb Jacqueline Leykam:
> Hello,
> 
> I have encountered an error in the Python Curses documentation, on this 
> page: http://docs.python.org/3.3/library/curses.html#curses.newwin
> 
> The curses.newwin documentation states that when the function is called
> with two arguments they are interpreted as the begin_y and begin_x
> attributes of the created window. In fact, the function interprets them as
> the window's nlines and ncols attributes (respectively). This error seems
> to be present in all versions of the documentation available.

Hi Jacqueline,

thanks for the report; this is now fixed and will appear online shortly.

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

iEYEARECAAYFAlJvX1kACgkQN9GcIYhpnLBeFACff7FlvYcp9myYNk4EMIBqqd+T
L4QAnR8ovGgd7Q/AxYLsmntIxblm3Rvk
=bAPI
-----END PGP SIGNATURE-----

From report at bugs.python.org  Tue Oct 29 08:16:10 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 29 Oct 2013 07:16:10 +0000
Subject: [docs] [issue19416] NNTP page has incorrect links
In-Reply-To: <1382879905.74.0.020204746466.issue19416@psf.upfronthosting.co.za>
Message-ID: <3d83xP2Py5z7LjR@mail.python.org>


Roundup Robot added the comment:

New changeset 6b2352f1d365 by Georg Brandl in branch '2.7':
Closes #19416: fix references in the nntplib docs.
http://hg.python.org/cpython/rev/6b2352f1d365

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

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

From georg at python.org  Tue Oct 29 08:17:27 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 29 Oct 2013 08:17:27 +0100
Subject: [docs] Confusing text which may came from a work to update
	documents
In-Reply-To: <CAN_7T0Lqq=FwJ=btQs_WCmz-TeaFvYnNNj_7Xwn+4YTGuSYWjw@mail.gmail.com>
References: <CAN_7T0Lqq=FwJ=btQs_WCmz-TeaFvYnNNj_7Xwn+4YTGuSYWjw@mail.gmail.com>
Message-ID: <526F6107.3070503@python.org>

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

Am 27.10.2013 13:36, schrieb tomo cocoa:
> Hello,
> 
> I am a Japanese translator of Python documentation.
> 
> In the third paragraph of the section "Reading and Writing Unicode Data" 
> (http://docs.python.org/3.3/howto/unicode.html#reading-and-writing-unicode-data),
>
> 
there is some confusing text: "open a file, read an 8-bit bytes object from it,
> and convert the string with bytes.decode(encoding)"
> 
> Words "the string" in it may refer to "an 8-bit bytes object", but usually
> we do not call a bytes object "string". This sentence confuses me.
> 
> 
> To know why and where such a strange word came from, I got back into
> Python documentation on version 2.7 
> (http://docs.python.org/2.7/howto/unicode.html#reading-and-writing-unicode-data).
>
> 
On this version, a corresponding old text is "open a file, read an 8-bit string
> from it, and convert the string with unicode(str, encoding)". As you might
> notice, the object read from a file is "string", but not "bytes" which
> appeared in Python 3.0. When this paragraph was converted, words "the
> string" might be missed and left.
> 
> 
> As my conclusion, I suggest that words "the string" should be "the bytes".

Hi,

thanks for this report, it is also fixed now.

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

iEYEARECAAYFAlJvYQcACgkQN9GcIYhpnLCfHgCeMPbMUltZoHpUchBeKg9DHC4s
fjcAoJI7EOfyATJ/e7GT4tzugoQBB2NG
=RLFq
-----END PGP SIGNATURE-----

From georg at python.org  Tue Oct 29 08:18:07 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 29 Oct 2013 08:18:07 +0100
Subject: [docs] Documentation rectification
In-Reply-To: <CACSwGANG-8yEPouOgJiHDTSA1p0v0fAHkooL4YvUtqYGp+DVGQ@mail.gmail.com>
References: <CACSwGANG-8yEPouOgJiHDTSA1p0v0fAHkooL4YvUtqYGp+DVGQ@mail.gmail.com>
Message-ID: <526F612F.9070703@python.org>

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

Am 25.10.2013 18:23, schrieb Augustus Francis:
> Page: http://www.docs.python.org/2/tutorial/introduction.html
> 
> print b won't work. It should be print (b)

Hi Augustus,

this is the documentation for Python 2.x, where "print b" is actually correct.
For Python 3.x please refer to the tutorial at
http://docs.python.org/3/tutorial

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

iEYEARECAAYFAlJvYS8ACgkQN9GcIYhpnLBpPQCgjZ/krU4uTCojzkKbMwD7tE7W
omwAn21TPeABcSR+qXrmfmCuJ4y3zqPz
=dbR5
-----END PGP SIGNATURE-----

From georg at python.org  Tue Oct 29 08:19:44 2013
From: georg at python.org (Georg Brandl)
Date: Tue, 29 Oct 2013 08:19:44 +0100
Subject: [docs] http://www.python.org/doc//current/
In-Reply-To: <BA02A06A22A52C449E4B5EE4CE1DBC3F9C69C74595@EMV66-UKRD.domain1.systemhost.net>
References: <BA02A06A22A52C449E4B5EE4CE1DBC3F9C69C74595@EMV66-UKRD.domain1.systemhost.net>
Message-ID: <526F6190.4060700@python.org>

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

Am 21.10.2013 15:01, schrieb keith.briggs at bt.com:
> Why does http://www.python.org/doc//current/ point to the old Python
> v2.6.5c2 documentation?
> 
> Keith

Hi Keith,

that's a good question; the "normalized" URL with one slash before "current"
does the right thing.  I'll have a look at our Apache configs.

cheers,
Georg



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

iEYEARECAAYFAlJvYZAACgkQN9GcIYhpnLDkhwCeO/sUxdlfjj5AE2XNOFN9q6vo
Jg8An2ZpmoO0X1yH/jcMInk0P1UMpIYA
=BXZq
-----END PGP SIGNATURE-----

From report at bugs.python.org  Tue Oct 29 08:18:48 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 29 Oct 2013 07:18:48 +0000
Subject: [docs] [issue19416] NNTP page has incorrect links
In-Reply-To: <1382879905.74.0.020204746466.issue19416@psf.upfronthosting.co.za>
Message-ID: <3d840R56Xdz7LjS@mail.python.org>


Roundup Robot added the comment:

New changeset 03fa1b0af343 by Georg Brandl in branch '3.3':
Closes #19416: fix references in the nntplib docs.
http://hg.python.org/cpython/rev/03fa1b0af343

----------

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

From report at bugs.python.org  Tue Oct 29 10:55:35 2013
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 29 Oct 2013 09:55:35 +0000
Subject: [docs] [issue19431] Document PyFrame_FastToLocals()
	and	PyFrame_FastToLocalsWithError()
Message-ID: <1383040535.91.0.284405039579.issue19431@psf.upfronthosting.co.za>


New submission from STINNER Victor:

(Copy of an email) Georg Brandl via python.org 
	
Am 29.10.2013 01:19, schrieb victor.stinner:
> http://hg.python.org/cpython/rev/4ef4578db38a
> changeset:   86715:4ef4578db38a
> user:        Victor Stinner <victor.stinner at gmail.com>
> date:        Tue Oct 29 01:19:37 2013 +0100
> summary:
>   Issue #18408: Add a new PyFrame_FastToLocalsWithError() function to handle
> exceptions when merging fast locals into f_locals of a frame.
> PyEval_GetLocals() now raises an exception and return NULL on failure.

You'll have to either make this private or document it.

----------
assignee: docs at python
components: Documentation
messages: 201618
nosy: docs at python, georg.brandl, haypo, pitrou
priority: normal
severity: normal
status: open
title: Document PyFrame_FastToLocals() and PyFrame_FastToLocalsWithError()
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Tue Oct 29 16:51:30 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Tue, 29 Oct 2013 15:51:30 +0000
Subject: [docs] [issue19434] Wrong documentation of MIMENonMultipart class
Message-ID: <1383061890.83.0.167475194564.issue19434@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

>>> from email.mime.nonmultipart import MIMENonMultipart
>>> MIMENonMultipart.__doc__
'Base class for MIME multipart/* type messages.'
>>>

Attached the patch to fix the doc of MIMENonMultipart class.

----------
assignee: docs at python
components: Documentation
files: fix_doc_for_mime_non_multipart.patch
keywords: patch
messages: 201643
nosy: docs at python, r.david.murray, vajrasky
priority: normal
severity: normal
status: open
title: Wrong documentation of MIMENonMultipart class
versions: Python 3.4
Added file: http://bugs.python.org/file32410/fix_doc_for_mime_non_multipart.patch

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

From report at bugs.python.org  Tue Oct 29 21:31:31 2013
From: report at bugs.python.org (mpb)
Date: Tue, 29 Oct 2013 20:31:31 +0000
Subject: [docs] [issue19438] Where is NoneType in Python 3?
Message-ID: <1383078691.36.0.6145513581.issue19438@psf.upfronthosting.co.za>


New submission from mpb:

types.NoneType seems to have disappeared in Python 3.  This is probably intentional, but I cannot figure out how to test if a variable is of type NoneType in Python 3.

Specifically, I want to write:
assert  type (v) in ( bytes, types.NoneType )

Yes, I could write:
assert  v is None or type (v) is bytes

But the first assert statement is easier to read (IMO).

Here are links to various Python 3 documentation about None:

[1] http://docs.python.org/3/library/stdtypes.html#index-2

[2] http://docs.python.org/3/library/constants.html#None

Link [2] says: "None  The sole value of the type NoneType."  However, NoneType is not listed in the Python 3 documentation index.  (As compared with the Python 2 index, where NoneType is listed.)

[3] http://docs.python.org/3/library/types.html

If NoneType is gone in Python 3, mention of NoneType should probably be removed from link [2].  If NoneType is present in Python 3, the docs (presumably at least one of the above links, and hopefully also the index) should tell me how to use it.

Here is another link:

[4] http://docs.python.org/3/library/stdtypes.html#bltin-type-objects

"The standard module types defines names for all standard built-in types."  (Except <class 'NoneType'> ???)

None is a built-in constant.  It has a type.  If None's type is not considered to be a "standard built-in type", then IMO this is surprising(!!) and should be documented somewhere (for example, at link [4], and possibly elsewhere as well.)

Thanks!

----------
assignee: docs at python
components: Documentation
messages: 201666
nosy: docs at python, mpb
priority: normal
severity: normal
status: open
title: Where is NoneType in Python 3?
versions: Python 3.3

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

From report at bugs.python.org  Tue Oct 29 21:33:51 2013
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 29 Oct 2013 20:33:51 +0000
Subject: [docs] [issue19438] Where is NoneType in Python 3?
In-Reply-To: <1383078691.36.0.6145513581.issue19438@psf.upfronthosting.co.za>
Message-ID: <1383078831.71.0.593986373142.issue19438@psf.upfronthosting.co.za>


Christian Heimes added the comment:

How about:

    type(v) in (bytes, type(None))

or:

   isinstance(v, (bytes, type(None))

or:

   v is None or type(v) is bytes

or:

  v is None or isinstance(v, bytes)

----------
nosy: +christian.heimes

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

From report at bugs.python.org  Tue Oct 29 21:49:24 2013
From: report at bugs.python.org (mpb)
Date: Tue, 29 Oct 2013 20:49:24 +0000
Subject: [docs] [issue19438] Where is NoneType in Python 3?
In-Reply-To: <1383078691.36.0.6145513581.issue19438@psf.upfronthosting.co.za>
Message-ID: <1383079764.13.0.795241439573.issue19438@psf.upfronthosting.co.za>


mpb added the comment:

Of your 4 suggestions, I mentioned #3 and #4 in my post.  They are less readable, IMO.

1 and 2 are nicer, but both have an "extra" set of nested parenthesis.

While I appreciate the suggestions, I submitted this as a documentation bug, because I think I should be able to find these suggestions somewhere in the Python 3 documentation, at one (or more) of the links I included in my bug report.  Also, the Python 3 documentation does mention NoneType, and if NoneType is not part of Python 3, I claim this is an error in the documentation.

And then, there is my personal favorite work-around:

NoneType = type (None)    # only needed once
assert type (v) in ( bytes, NoneType )

Or (perhaps more confusingly, LOL!):

none = type (None)
assert type (v) in ( bytes, none )

isinstance is more confusing because it takes two arguments.  Whenever I use it I have to think, "isinstance" vs "instanceof", which is Python, which is Java?  (And I haven't used Java seriously in years!)  And then I have to think about the order of the arguments (v, cls) vs (cls, v).  type is just simpler than isinstance.

----------

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

From report at bugs.python.org  Tue Oct 29 23:07:06 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 29 Oct 2013 22:07:06 +0000
Subject: [docs] [issue19438] Where is NoneType in Python 3?
In-Reply-To: <1383078691.36.0.6145513581.issue19438@psf.upfronthosting.co.za>
Message-ID: <1383084426.72.0.906406588747.issue19438@psf.upfronthosting.co.za>


R. David Murray added the comment:

See http://www.python.org/dev/peps/pep-0294/ for some background on this.  The unexpected thing is actually that the types module still exists at all in Python3 :)

That said, its documentation could, indeed, use some improvement to address this kind of question.

Searching the python-dev email list for 'NoneType removal types module" turns up some interesting posts, back in the 2.3 days...basically, type(None) is the One True Way to get NoneType :)

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

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

From report at bugs.python.org  Tue Oct 29 23:55:33 2013
From: report at bugs.python.org (Alan Cristhian)
Date: Tue, 29 Oct 2013 22:55:33 +0000
Subject: [docs] [issue19441] itertools.tee improve documentation
Message-ID: <1383087333.66.0.191656186181.issue19441@psf.upfronthosting.co.za>


New submission from Alan Cristhian:

I had some problems using itertools.tee function. Fortunately I found the following advice on the PEP-323:

"Currently, the copied iterators remaintied to the original iterator. If the original advances, then so do all of the copies. Good practice is to overwrite the original So THAT anamolies do result: a, b = t (a)."

I believe that such advice should be in the documentation as well:

"Currently, the copied iterators remaintied to the original iterator. If the original advances, then so do all of the copies and vice versa. Good practice is to overwrite the original So THAT anamolies do result: a, b = t (a ). "

Note that I added "and vice versa".

----------
assignee: docs at python
components: Documentation
messages: 201693
nosy: Alan.Cristhian, docs at python
priority: normal
severity: normal
status: open
title: itertools.tee improve documentation
type: enhancement
versions: Python 3.3

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

From report at bugs.python.org  Wed Oct 30 02:17:22 2013
From: report at bugs.python.org (mpb)
Date: Wed, 30 Oct 2013 01:17:22 +0000
Subject: [docs] [issue19438] Where is NoneType in Python 3?
In-Reply-To: <1383078691.36.0.6145513581.issue19438@psf.upfronthosting.co.za>
Message-ID: <1383095841.7.0.839309548437.issue19438@psf.upfronthosting.co.za>


mpb added the comment:

Regarding http://www.python.org/dev/peps/pep-0294/ ...

Complete removal of the types module makes more sense to me than letting types continue, but removing NoneType from it!

If type(None) is the one_true_way, then the docs should say that, possibly in multiple locations.

----------

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

From report at bugs.python.org  Wed Oct 30 06:02:07 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 30 Oct 2013 05:02:07 +0000
Subject: [docs] [issue19441] itertools.tee improve documentation
In-Reply-To: <1383087333.66.0.191656186181.issue19441@psf.upfronthosting.co.za>
Message-ID: <1383109327.82.0.854479303461.issue19441@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Oct 30 07:01:21 2013
From: report at bugs.python.org (Blaise Gassend)
Date: Wed, 30 Oct 2013 06:01:21 +0000
Subject: [docs] [issue19445] heapq.heapify is n log(n), not linear
Message-ID: <1383112881.24.0.0958145237124.issue19445@psf.upfronthosting.co.za>


New submission from Blaise Gassend:

The documentation for heapq.heapify indicates that it runs in linear time. I believe that this is incorrect, and that it runs in worst case n * log(n) time. I checked the implementation, and there are indeed n _siftup operations, which each appear to be worst case log(n).

One example of the documentation pages that are wrong.
http://docs.python.org/3.4/library/heapq.html#heapq.heappush

----------
assignee: docs at python
components: Documentation
messages: 201712
nosy: Blaise.Gassend, docs at python
priority: normal
severity: normal
status: open
title: heapq.heapify is n log(n), not linear
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Wed Oct 30 08:17:48 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 30 Oct 2013 07:17:48 +0000
Subject: [docs] [issue19445] heapq.heapify is n log(n), not linear
In-Reply-To: <1383112881.24.0.0958145237124.issue19445@psf.upfronthosting.co.za>
Message-ID: <1383117468.54.0.285328683418.issue19445@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Oct 30 08:33:02 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 30 Oct 2013 07:33:02 +0000
Subject: [docs] [issue19445] heapq.heapify is n log(n), not linear
In-Reply-To: <1383112881.24.0.0958145237124.issue19445@psf.upfronthosting.co.za>
Message-ID: <1383118382.88.0.274797566546.issue19445@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

The run time is O(n) because the heapify algorithm runs bottom-to-top so most of the n//2 sift operations are working on very short heaps (i.e. half of them are at depth 1, a quarter of them are at depth 2, one eight at depth 3, etc).  Please take a look at on-line references for heapifying.

----------
resolution:  -> invalid
status: open -> closed

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

From report at bugs.python.org  Wed Oct 30 10:23:44 2013
From: report at bugs.python.org (Christian Heimes)
Date: Wed, 30 Oct 2013 09:23:44 +0000
Subject: [docs] [issue19444] mmap.mmap() allocates a file descriptor that
	isn't	CLOEXEC
In-Reply-To: <1383110349.25.0.857290073089.issue19444@psf.upfronthosting.co.za>
Message-ID: <1383125024.63.0.549718685127.issue19444@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Can you suggest a documentation update?

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +christian.heimes, docs at python
stage:  -> needs patch
versions: +Python 3.2

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

From report at bugs.python.org  Wed Oct 30 10:33:44 2013
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2013 09:33:44 +0000
Subject: [docs] [issue19444] mmap.mmap() allocates a file descriptor that
	isn't	CLOEXEC
In-Reply-To: <1383110349.25.0.857290073089.issue19444@psf.upfronthosting.co.za>
Message-ID: <1383125623.97.0.697475009841.issue19444@psf.upfronthosting.co.za>


STINNER Victor added the comment:

"the file descriptor that mmap.mmap() allocates is not set to close-on-exec"

In Python 3.4, the file descriptor is now non-inheritable, as a side effect of the PEP 446.
http://www.python.org/dev/peps/pep-0446/

----------
versions: +Python 3.3, Python 3.4 -Python 3.2

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

From report at bugs.python.org  Wed Oct 30 10:35:24 2013
From: report at bugs.python.org (STINNER Victor)
Date: Wed, 30 Oct 2013 09:35:24 +0000
Subject: [docs] [issue19444] mmap.mmap() allocates a file descriptor that
	isn't	CLOEXEC
In-Reply-To: <1383110349.25.0.857290073089.issue19444@psf.upfronthosting.co.za>
Message-ID: <1383125724.43.0.391271031537.issue19444@psf.upfronthosting.co.za>


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


----------
nosy: +neologix

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

From report at bugs.python.org  Wed Oct 30 10:45:36 2013
From: report at bugs.python.org (Robert Merrill)
Date: Wed, 30 Oct 2013 09:45:36 +0000
Subject: [docs] [issue19444] mmap.mmap() allocates a file descriptor that
	isn't	CLOEXEC
In-Reply-To: <1383110349.25.0.857290073089.issue19444@psf.upfronthosting.co.za>
Message-ID: <1383126336.73.0.264345539996.issue19444@psf.upfronthosting.co.za>


Robert Merrill added the comment:

I'm adding Library again because I think the current behavior is a bug and should be fixed in the 2.7 tree. Perhaps the documentation in older versions should be updated 

mmap.mmap should always set the FD_CLOEXEC flag on the descriptor that it gets from dup(). I don't see why we wouldn't do this, because if we are calling exec(), we are blowing away all python state, and only the mmap object should be using this file descriptor (since its existence is hidden from the user).

Users should not be depending on the old behavior, because the interface which is presented to them gives them no indication that this fd even exists. Users are probably expecting the proposed behavior, because anyone who has worked with unix file descriptors in C would not expect:

fd = os.open(...)
mmap = mmap.mmap(fd, size)
# do some stuff
os.close(fd)

To result in an extra inheritable fd still being there. Nothing in the documentation indicates that this would happen, either.

----------
components: +Library (Lib)
versions:  -Python 3.4

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

From report at bugs.python.org  Wed Oct 30 11:34:27 2013
From: report at bugs.python.org (Robert Merrill)
Date: Wed, 30 Oct 2013 10:34:27 +0000
Subject: [docs] [issue19444] mmap.mmap() allocates a file descriptor that
	isn't	CLOEXEC
In-Reply-To: <1383110349.25.0.857290073089.issue19444@psf.upfronthosting.co.za>
Message-ID: <1383129267.85.0.242189612689.issue19444@psf.upfronthosting.co.za>


Robert Merrill added the comment:

Sorry, I correct my earlier statement: even if the fd you pass to mmap.mmap() is set to FD_CLOEXEC, the dup'd fd /will not be/

So this is a REALLY bad bug because users cannot workaround it except by just not using mmap

----------

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

From report at bugs.python.org  Wed Oct 30 14:57:26 2013
From: report at bugs.python.org (Peter Harris)
Date: Wed, 30 Oct 2013 13:57:26 +0000
Subject: [docs] [issue19452] ElementTree iterparse documentation
Message-ID: <1383141446.52.0.417040462191.issue19452@psf.upfronthosting.co.za>


New submission from Peter Harris:

Documentation on python website says:

    xml.etree.ElementTree.iterparse(source, events=None, parser=None)
Parses an XML section into an element tree incrementally, and reports what?s going on to the user. source is a filename or file object containing XML data. events is a list of events to report back.

But 'events' must be a *tuple* or iterparse raises "TypeError: invalid event tuple"

Possibly also worth explaining that "start-ns" event is accompanied by a tuple of (namespace, url) rather than an element from the XML document. Currently the description just says "ns events are used to get detailed namespace information" but doesn't say how or give an example.

----------
assignee: docs at python
components: Documentation
messages: 201734
nosy: Peter.Harris, docs at python
priority: normal
severity: normal
status: open
title: ElementTree iterparse documentation
versions: Python 3.3

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

From report at bugs.python.org  Wed Oct 30 17:25:31 2013
From: report at bugs.python.org (Blaise Gassend)
Date: Wed, 30 Oct 2013 16:25:31 +0000
Subject: [docs] [issue19445] heapq.heapify is n log(n), not linear
In-Reply-To: <1383112881.24.0.0958145237124.issue19445@psf.upfronthosting.co.za>
Message-ID: <1383150331.4.0.438000311662.issue19445@psf.upfronthosting.co.za>


Blaise Gassend added the comment:

I stand corrected. Sorry for the noise.

----------

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

From report at bugs.python.org  Wed Oct 30 17:41:13 2013
From: report at bugs.python.org (Stefan Behnel)
Date: Wed, 30 Oct 2013 16:41:13 +0000
Subject: [docs] [issue19452] ElementTree iterparse documentation
In-Reply-To: <1383141446.52.0.417040462191.issue19452@psf.upfronthosting.co.za>
Message-ID: <1383151273.46.0.340129636995.issue19452@psf.upfronthosting.co.za>


Stefan Behnel added the comment:

How about actually allowing a list in addition to a tuple? And, in fact, any sequence? I can't see a reason not to.

For reference, lxml only expects it to be either None or an iterable. Essentially, I consider it more of a set-like filter, since the linear aspect of a tuple/list/sequence has no meaning for it.

----------
components: +XML
nosy: +eli.bendersky, scoder
type:  -> behavior

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

From report at bugs.python.org  Wed Oct 30 18:47:07 2013
From: report at bugs.python.org (=?utf-8?q?Charles-Fran=C3=A7ois_Natali?=)
Date: Wed, 30 Oct 2013 17:47:07 +0000
Subject: [docs] [issue19444] mmap.mmap() allocates a file descriptor that
	isn't	CLOEXEC
In-Reply-To: <1383129267.85.0.242189612689.issue19444@psf.upfronthosting.co.za>
Message-ID: <CAH_1eM0L2A0t_=VZzRbY+i5Xn3oowJ8D0HoKFhCARUyAD8vZEg@mail.gmail.com>


Charles-Fran?ois Natali added the comment:

I agree this should be fixed.
Robert, want to submit a patch?

----------

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

From report at bugs.python.org  Wed Oct 30 19:20:23 2013
From: report at bugs.python.org (Peter Harris)
Date: Wed, 30 Oct 2013 18:20:23 +0000
Subject: [docs] [issue19452] ElementTree iterparse documentation
In-Reply-To: <1383141446.52.0.417040462191.issue19452@psf.upfronthosting.co.za>
Message-ID: <1383157223.75.0.345219953178.issue19452@psf.upfronthosting.co.za>


Peter Harris added the comment:

Yeah it would make sense to accept any iterable, but I'm only proposing a documentation fix not a feature enhancement.

----------

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

From report at bugs.python.org  Wed Oct 30 19:51:56 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Wed, 30 Oct 2013 18:51:56 +0000
Subject: [docs] [issue19454] devguide: Document what a "platform support" is
Message-ID: <1383159116.46.0.184690879028.issue19454@psf.upfronthosting.co.za>


New submission from anatoly techtonik:

As a followup to issue19377 it would be nice if devguide contained a paragraph to resolve the conflicting point provided by http://bugs.python.org/msg187373 and http://bugs.python.org/msg201141 arguments.

----------
assignee: docs at python
components: Devguide, Documentation
messages: 201762
nosy: docs at python, ezio.melotti, techtonik
priority: normal
severity: normal
status: open
title: devguide: Document what a "platform support" is

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

From report at bugs.python.org  Thu Oct 31 00:11:54 2013
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Wed, 30 Oct 2013 23:11:54 +0000
Subject: [docs] [issue19444] mmap.mmap() allocates a file descriptor that
	isn't	CLOEXEC
In-Reply-To: <1383110349.25.0.857290073089.issue19444@psf.upfronthosting.co.za>
Message-ID: <1383174714.88.0.547777111532.issue19444@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/issue19444>
_______________________________________

From report at bugs.python.org  Thu Oct 31 13:51:01 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 31 Oct 2013 12:51:01 +0000
Subject: [docs] [issue19452] ElementTree iterparse documentation
In-Reply-To: <1383141446.52.0.417040462191.issue19452@psf.upfronthosting.co.za>
Message-ID: <1383223861.69.0.31577094759.issue19452@psf.upfronthosting.co.za>


Eli Bendersky added the comment:

Thanks for the report, Peter. This is indeed a documentation fix for Python 3.3; note that in 3.4 (default branch), the restriction was lifted and iterparse now accepts any iterable sequence. The documentation also reflects that (saying that 'events' is a sequence).

I'll update the 3.3 docs to address this issue.

----------

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

From report at bugs.python.org  Thu Oct 31 13:51:12 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 31 Oct 2013 12:51:12 +0000
Subject: [docs] [issue19452] ElementTree iterparse documentation
In-Reply-To: <1383141446.52.0.417040462191.issue19452@psf.upfronthosting.co.za>
Message-ID: <1383223872.03.0.397960483754.issue19452@psf.upfronthosting.co.za>


Changes by Eli Bendersky <eliben at gmail.com>:


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

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

From report at bugs.python.org  Thu Oct 31 13:55:46 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 31 Oct 2013 12:55:46 +0000
Subject: [docs] [issue19452] ElementTree iterparse documentation
In-Reply-To: <1383141446.52.0.417040462191.issue19452@psf.upfronthosting.co.za>
Message-ID: <3d9RNL0p43zT0m@mail.python.org>


Roundup Robot added the comment:

New changeset e6941225e014 by Eli Bendersky in branch '3.3':
Issue #19452: Clarify the documentation of iterparse w.r.t. events argument.
http://hg.python.org/cpython/rev/e6941225e014

New changeset 2a996cecf762 by Eli Bendersky in branch 'default':
Null merge for issue #19452
http://hg.python.org/cpython/rev/2a996cecf762

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

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

From report at bugs.python.org  Thu Oct 31 13:56:10 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 31 Oct 2013 12:56:10 +0000
Subject: [docs] [issue19452] ElementTree iterparse documentation
In-Reply-To: <1383141446.52.0.417040462191.issue19452@psf.upfronthosting.co.za>
Message-ID: <1383224170.37.0.615796975046.issue19452@psf.upfronthosting.co.za>


Changes by Eli Bendersky <eliben at gmail.com>:


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

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

From report at bugs.python.org  Thu Oct 31 22:36:01 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 31 Oct 2013 21:36:01 +0000
Subject: [docs] [issue18985] Improve the documentation in fcntl module
In-Reply-To: <1378722919.93.0.901392318122.issue18985@psf.upfronthosting.co.za>
Message-ID: <1383255361.15.0.296683204535.issue18985@psf.upfronthosting.co.za>


R. David Murray added the comment:

Here's my suggestion.

----------
Added file: http://bugs.python.org/file32442/fcntl-doc.patch

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

From report at bugs.python.org  Thu Oct 31 23:24:11 2013
From: report at bugs.python.org (STINNER Victor)
Date: Thu, 31 Oct 2013 22:24:11 +0000
Subject: [docs] [issue19444] mmap.mmap() allocates a file descriptor that
	isn't	CLOEXEC
In-Reply-To: <1383110349.25.0.857290073089.issue19444@psf.upfronthosting.co.za>
Message-ID: <1383258251.78.0.428597210193.issue19444@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> Robert, want to submit a patch?

If someone wants to work on a patch, here is the code of Python 3.4 to duplicate a file descriptor and make it non-inheritable.
  http://hg.python.org/cpython/file/e97d9926da83/Python/fileutils.c#l978
and
  http://hg.python.org/cpython/file/e97d9926da83/Python/fileutils.c#l618

The code is complex because it has optimized versions for each operating system. Only supporting Windows and fcntl() is enough for Python 2.

----------

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

From EYALMO at il.ibm.com  Wed Oct 30 14:59:10 2013
From: EYALMO at il.ibm.com (Eyal Moscovici)
Date: Wed, 30 Oct 2013 15:59:10 +0200
Subject: [docs] python2.7/subprocess.py Popen on Ubuntu 10.04 Bug
Message-ID: <OF0B78D7B9.90A03F9D-ONC2257C14.004BCA58-C2257C14.004CD910@il.ibm.com>

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


Eyal Moscovici
Networking and Virtualization Technologies
IBM Haifa Research Lab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131030/3d2260c1/attachment.html>

From adam at zaleski.org  Wed Oct 30 18:41:06 2013
From: adam at zaleski.org (Adam Zaleski)
Date: Wed, 30 Oct 2013 18:41:06 +0100
Subject: [docs] Webpage BUG
Message-ID: <CAKdzqG+bu_ifthnJw+4eTsM+BgCQa9VrKdBiSjfdA9KAYeyeRA@mail.gmail.com>

http://docs.python.org/2/search.html?q=



-- 
pozdrawiam
Adam Zaleski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20131030/1c3d1f5b/attachment.html>

From victor.stinner at gmail.com  Thu Oct 31 23:26:05 2013
From: victor.stinner at gmail.com (victor.stinner at gmail.com)
Date: Thu, 31 Oct 2013 22:26:05 -0000
Subject: [docs] Improve the documentation in fcntl module (issue 18985)
Message-ID: <20131031222605.22763.74987@psf.upfronthosting.co.za>


http://bugs.python.org/review/18985/diff/9767/Doc/library/fcntl.rst
File Doc/library/fcntl.rst (right):

http://bugs.python.org/review/18985/diff/9767/Doc/library/fcntl.rst#newcode35
Doc/library/fcntl.rst:35: for for *op* are operating system dependent,
and are available as constants
double for :-)

http://bugs.python.org/review/18985/