From report at bugs.python.org  Wed Feb  1 00:39:58 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 31 Jan 2012 23:39:58 +0000
Subject: [docs] [issue13915] Update Tutorial 6.1.3 for PEP 3145
Message-ID: <1328053198.63.0.994035147287.issue13915@psf.upfronthosting.co.za>


New submission from Terry J. Reedy <tjreedy at udel.edu>:

http://docs.python.org/py3k/tutorial/modules.html#compiled-python-files
needs to be updated for 3.2+ to reflect 
http://python.org/dev/peps/pep-3147/

The first sentence is still technically correct, but finding x.pyc in the same directory as x.py is now an anomaly, so that sentence, revised, should be near the bottom. Otherwise, the text should say that the default is to put x.<version>.pyc in __pycache__, where <version> is, for instance, 'cpython-32'. Note that this allows other implementations and other versions of cpython to use the same .py file.

I do not know if there is anywhere else that this info is or should be. Using Python?.

----------
assignee: docs at python
components: Documentation
messages: 152415
nosy: docs at python, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Update Tutorial 6.1.3 for PEP 3145
type: behavior
versions: Python 3.2, Python 3.3

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

From report at bugs.python.org  Wed Feb  1 15:12:21 2012
From: report at bugs.python.org (=?utf-8?q?C=C3=A9dric_Krier?=)
Date: Wed, 01 Feb 2012 14:12:21 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
Message-ID: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>


New submission from C?dric Krier <cedric.krier at b2ck.com>:

atof has a func argument used to instantiate the result but it is missing in the documentation.

----------
assignee: docs at python
components: Documentation
messages: 152430
nosy: ced, docs at python
priority: normal
severity: normal
status: open
title: locale.atof documentation is missing func argument
type: enhancement

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

From report at bugs.python.org  Wed Feb  1 15:42:16 2012
From: report at bugs.python.org (=?utf-8?q?Bo=C5=A1tjan_Mejak?=)
Date: Wed, 01 Feb 2012 14:42:16 +0000
Subject: [docs] [issue13868] Add hyphen doc fix
In-Reply-To: <1327535890.98.0.936666267948.issue13868@psf.upfronthosting.co.za>
Message-ID: <1328107336.58.0.228642086108.issue13868@psf.upfronthosting.co.za>


Bo?tjan Mejak <bostjan.mejak at gmail.com> added the comment:

Seriously, how old are you?two?clowns?

----------

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

From report at bugs.python.org  Wed Feb  1 15:45:15 2012
From: report at bugs.python.org (Sandro Tosi)
Date: Wed, 01 Feb 2012 14:45:15 +0000
Subject: [docs] [issue13868] Add hyphen doc fix
In-Reply-To: <1328107336.58.0.228642086108.issue13868@psf.upfronthosting.co.za>
Message-ID: <CAPdtAj37dLD99HuBUEjZyqr8VRpgYYjtwnpOOKHPC9TuGj8g_g@mail.gmail.com>


Sandro Tosi <sandro.tosi at gmail.com> added the comment:

On Wed, Feb 1, 2012 at 15:42, Bo?tjan Mejak <report at bugs.python.org> wrote:
> Seriously, how old are you?two?clowns?

I think it's enough: FTR I'm +1 on removing Retro tracker account,
effective immediately (if any admin is around).

----------

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

From report at bugs.python.org  Wed Feb  1 15:59:57 2012
From: report at bugs.python.org (=?utf-8?q?Bo=C5=A1tjan_Mejak?=)
Date: Wed, 01 Feb 2012 14:59:57 +0000
Subject: [docs] [issue13868] Add hyphen doc fix
In-Reply-To: <1327535890.98.0.936666267948.issue13868@psf.upfronthosting.co.za>
Message-ID: <1328108397.84.0.815601933101.issue13868@psf.upfronthosting.co.za>


Bo?tjan Mejak <bostjan.mejak at gmail.com> added the comment:

Kiss?my?ball?sac!

----------

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

From report at bugs.python.org  Wed Feb  1 16:03:26 2012
From: report at bugs.python.org (=?utf-8?q?Bo=C5=A1tjan_Mejak?=)
Date: Wed, 01 Feb 2012 15:03:26 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMTM5MTldIGtpc3PCoG15wqBiYWxswqBzYWM=?=
Message-ID: <1328108606.27.0.912449136381.issue13919@psf.upfronthosting.co.za>


Changes by Bo?tjan Mejak <bostjan.mejak at gmail.com>:


----------
assignee: docs at python
components: Documentation
nosy: Retro, docs at python
priority: normal
severity: normal
status: open
title: kiss?my?ball?sac
type: enhancement
versions: Python 2.7

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

From report at bugs.python.org  Wed Feb  1 16:08:47 2012
From: report at bugs.python.org (Nadeem Vawda)
Date: Wed, 01 Feb 2012 15:08:47 +0000
Subject: [docs] =?utf-8?b?W2lzc3VlMTM5MTldIGtpc3PCoG15wqBiYWxswqBzYWM=?=
Message-ID: <1328108927.77.0.906853313635.issue13919@psf.upfronthosting.co.za>


Changes by Nadeem Vawda <nadeem.vawda at gmail.com>:


----------
resolution:  -> invalid
stage:  -> committed/rejected
status: open -> closed
type: enhancement -> 

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

From report at bugs.python.org  Wed Feb  1 16:13:26 2012
From: report at bugs.python.org (=?utf-8?q?Bo=C5=A1tjan_Mejak?=)
Date: Wed, 01 Feb 2012 15:13:26 +0000
Subject: [docs] [issue13920] intern() doc wrong spelling
Message-ID: <1328109206.92.0.270712922412.issue13920@psf.upfronthosting.co.za>


New submission from Bo?tjan Mejak <bostjan.mejak at gmail.com>:

http://docs.python.org/library/functions.html#intern

Visit the upper link andewsqEz80olp

----------
assignee: docs at python
components: Documentation
hgrepos: 110
messages: 152435
nosy: Retro, docs at python
priority: normal
severity: normal
status: open
title: intern() doc wrong spelling
versions: Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Wed Feb  1 16:14:06 2012
From: report at bugs.python.org (=?utf-8?q?Bo=C5=A1tjan_Mejak?=)
Date: Wed, 01 Feb 2012 15:14:06 +0000
Subject: [docs] [issue13920] intern() doc wrong spelling
In-Reply-To: <1328109206.92.0.270712922412.issue13920@psf.upfronthosting.co.za>
Message-ID: <1328109246.89.0.283472974904.issue13920@psf.upfronthosting.co.za>


Changes by Bo?tjan Mejak <bostjan.mejak at gmail.com>:


----------
hgrepos:  -110

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

From report at bugs.python.org  Wed Feb  1 16:17:06 2012
From: report at bugs.python.org (=?utf-8?q?Bo=C5=A1tjan_Mejak?=)
Date: Wed, 01 Feb 2012 15:17:06 +0000
Subject: [docs] [issue13920] intern() doc wrong spelling
In-Reply-To: <1328109206.92.0.270712922412.issue13920@psf.upfronthosting.co.za>
Message-ID: <1328109426.36.0.470302369132.issue13920@psf.upfronthosting.co.za>


Bo?tjan Mejak <bostjan.mejak at gmail.com> added the comment:

http://docs.python.org/library/functions.html#intern

Visit the upper link and fix 2 words that say "compare" to "comparison".

Hint: "blah blah blah pointer compare ... string compare ..."

----------

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

From report at bugs.python.org  Wed Feb  1 16:17:46 2012
From: report at bugs.python.org (=?utf-8?q?Bo=C5=A1tjan_Mejak?=)
Date: Wed, 01 Feb 2012 15:17:46 +0000
Subject: [docs] [issue13920] intern() doc wrong spelling
In-Reply-To: <1328109206.92.0.270712922412.issue13920@psf.upfronthosting.co.za>
Message-ID: <1328109466.26.0.530695913404.issue13920@psf.upfronthosting.co.za>


Changes by Bo?tjan Mejak <bostjan.mejak at gmail.com>:


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

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

From report at bugs.python.org  Wed Feb  1 16:21:59 2012
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 01 Feb 2012 15:21:59 +0000
Subject: [docs] [issue13868] Add hyphen doc fix
In-Reply-To: <1327535890.98.0.936666267948.issue13868@psf.upfronthosting.co.za>
Message-ID: <1328109718.99.0.914806032331.issue13868@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Retro, your contributions are not welcome anymore.

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

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

From report at bugs.python.org  Wed Feb  1 16:43:54 2012
From: report at bugs.python.org (Brian Curtin)
Date: Wed, 01 Feb 2012 15:43:54 +0000
Subject: [docs] [issue13920] intern() doc wrong spelling
In-Reply-To: <1328109206.92.0.270712922412.issue13920@psf.upfronthosting.co.za>
Message-ID: <1328111034.65.0.738334512415.issue13920@psf.upfronthosting.co.za>


Brian Curtin <brian at python.org> added the comment:

This is fine as is.

----------
nosy: +brian.curtin
resolution:  -> wont fix
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Wed Feb  1 16:44:05 2012
From: report at bugs.python.org (Brian Curtin)
Date: Wed, 01 Feb 2012 15:44:05 +0000
Subject: [docs] [issue13920] intern() doc wrong spelling
In-Reply-To: <1328109206.92.0.270712922412.issue13920@psf.upfronthosting.co.za>
Message-ID: <1328111045.35.0.398497350962.issue13920@psf.upfronthosting.co.za>


Changes by Brian Curtin <brian at python.org>:


----------
nosy:  -brian.curtin

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

From report at bugs.python.org  Wed Feb  1 20:37:28 2012
From: report at bugs.python.org (Georg Brandl)
Date: Wed, 01 Feb 2012 19:37:28 +0000
Subject: [docs] [issue13868] Add hyphen doc fix
In-Reply-To: <1327535890.98.0.936666267948.issue13868@psf.upfronthosting.co.za>
Message-ID: <1328125048.91.0.723000920394.issue13868@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/issue13868>
_______________________________________

From report at bugs.python.org  Thu Feb  2 01:49:34 2012
From: report at bugs.python.org (Mark Dickinson)
Date: Thu, 02 Feb 2012 00:49:34 +0000
Subject: [docs] [issue13919] invalid
Message-ID: <1328143774.67.0.735715459313.issue13919@psf.upfronthosting.co.za>


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


----------
title: kiss?my?ball?sac -> invalid

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

From report at bugs.python.org  Thu Feb  2 06:40:18 2012
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 02 Feb 2012 05:40:18 +0000
Subject: [docs] [issue13868] Add hyphen doc fix
In-Reply-To: <1327535890.98.0.936666267948.issue13868@psf.upfronthosting.co.za>
Message-ID: <1328161218.41.0.998830948981.issue13868@psf.upfronthosting.co.za>


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

Bo?tjan, please stop wasting everyone's time.

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

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

From report at bugs.python.org  Thu Feb  2 17:47:17 2012
From: report at bugs.python.org (Stefan Krah)
Date: Thu, 02 Feb 2012 16:47:17 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>
Message-ID: <1328201237.03.0.377627077762.issue13124@psf.upfronthosting.co.za>


Stefan Krah <stefan-usenet at bytereef.org> added the comment:

Here's a terse shell script that IMO even moderately experienced admins
will prefer to the current version.

I'm not sure if the devguide is the right place for this, since
non-devs are very welcome to set up buildbots.

----------
nosy: +pitrou
Added file: http://bugs.python.org/file24398/buildslave_install.sh

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

From report at bugs.python.org  Thu Feb  2 17:59:47 2012
From: report at bugs.python.org (Stefan Krah)
Date: Thu, 02 Feb 2012 16:59:47 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>
Message-ID: <1328201987.63.0.971999133751.issue13124@psf.upfronthosting.co.za>


Changes by Stefan Krah <stefan-usenet at bytereef.org>:


Added file: http://bugs.python.org/file24399/buildslave_install.txt

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

From report at bugs.python.org  Thu Feb  2 18:00:04 2012
From: report at bugs.python.org (Stefan Krah)
Date: Thu, 02 Feb 2012 17:00:04 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>
Message-ID: <1328202004.8.0.807518040921.issue13124@psf.upfronthosting.co.za>


Changes by Stefan Krah <stefan-usenet at bytereef.org>:


Removed file: http://bugs.python.org/file24398/buildslave_install.txt

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

From report at bugs.python.org  Thu Feb  2 18:08:50 2012
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 02 Feb 2012 17:08:50 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1328201237.03.0.377627077762.issue13124@psf.upfronthosting.co.za>
Message-ID: <1328202378.3418.6.camel@localhost.localdomain>


Antoine Pitrou <pitrou at free.fr> added the comment:

> Here's a terse shell script that IMO even moderately experienced admins
> will prefer to the current version.

I'm sure some admins will prefer using their system's packages (I think
buildbot is packaged for Debian/Ubuntu, I see it in Mageia's packages,
not sure about Fedora).

Anyway, the current instructions are on the wiki:
http://wiki.python.org/moin/BuildBot
You could add your script or link to it there.

----------

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

From report at bugs.python.org  Thu Feb  2 20:30:25 2012
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 02 Feb 2012 19:30:25 +0000
Subject: [docs] [issue13402] Document absoluteness of sys.executable
In-Reply-To: <1321289437.84.0.982753479785.issue13402@psf.upfronthosting.co.za>
Message-ID: <E1Rt2MO-00029J-TO@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset fdcda5b74317 by Petri Lehtinen in branch '3.2':
Document absoluteness of sys.executable
http://hg.python.org/cpython/rev/fdcda5b74317

New changeset 8b591a86fc91 by Petri Lehtinen in branch 'default':
Merge branch 3.2
http://hg.python.org/cpython/rev/8b591a86fc91

New changeset c351536e804a by Petri Lehtinen in branch '2.7':
Document absoluteness of sys.executable
http://hg.python.org/cpython/rev/c351536e804a

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

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

From report at bugs.python.org  Thu Feb  2 22:29:15 2012
From: report at bugs.python.org (Georg Brandl)
Date: Thu, 02 Feb 2012 21:29:15 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1328218155.24.0.521535404776.issue13918@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

I don't think that argument needs to be documented.  It's just there because somebody thought that copying 3 lines from atof into atoi was a bad idea.

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

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

From report at bugs.python.org  Thu Feb  2 22:36:30 2012
From: report at bugs.python.org (=?utf-8?q?C=C3=A9dric_Krier?=)
Date: Thu, 02 Feb 2012 21:36:30 +0000
Subject: [docs] [issue13918] locale.atof documentation is missing func
	argument
In-Reply-To: <1328105541.08.0.458455853203.issue13918@psf.upfronthosting.co.za>
Message-ID: <1328218590.83.0.968634001708.issue13918@psf.upfronthosting.co.za>


C?dric Krier <cedric.krier at b2ck.com> added the comment:

Indeed I find it useful to use to get a Decimal instead of a float.
So I was wondering if I can rely on it or not in my application?

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

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

From report at bugs.python.org  Thu Feb  2 23:29:28 2012
From: report at bugs.python.org (Eric V. Smith)
Date: Thu, 02 Feb 2012 22:29:28 +0000
Subject: [docs] [issue13927] Extra spaces in the output of time.ctime
In-Reply-To: <1328215776.48.0.974828105123.issue13927@psf.upfronthosting.co.za>
Message-ID: <1328221768.76.0.642439616195.issue13927@psf.upfronthosting.co.za>


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

That's definitely the expected behavior. It's the same as the C library version of ctime().

But I couldn't find it documented in the Python docs, so I'm changing this to a documentation issue.

Thanks for the report.

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

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

From report at bugs.python.org  Fri Feb  3 01:07:47 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 03 Feb 2012 00:07:47 +0000
Subject: [docs] [issue12902] help("modules") executes module code
In-Reply-To: <1315251083.43.0.259542197646.issue12902@psf.upfronthosting.co.za>
Message-ID: <1328227667.37.0.0410956204187.issue12902@psf.upfronthosting.co.za>


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

#13902 is essentially a duplicate of this and I may close it.
I am thinking now that executing unknown amounts of unknown code from unknown modules is a really bad idea. If a module just crashes the system, as happened with the OP of the above, there is no way to tell what the culprit is. So if we do not disable 'modules', I thing it should just read directory names and forget about docstrings. In any case, output should be flushed as available if not now.

----------

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

From report at bugs.python.org  Fri Feb  3 08:10:52 2012
From: report at bugs.python.org (Georg Brandl)
Date: Fri, 03 Feb 2012 07:10:52 +0000
Subject: [docs] [issue13927] Extra spaces in the output of time.ctime
In-Reply-To: <1328215776.48.0.974828105123.issue13927@psf.upfronthosting.co.za>
Message-ID: <1328253052.08.0.497945753054.issue13927@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

asctime() docs say it's a 24 char string.

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

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

From report at bugs.python.org  Fri Feb  3 11:41:07 2012
From: report at bugs.python.org (Stefan Krah)
Date: Fri, 03 Feb 2012 10:41:07 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1328202378.3418.6.camel@localhost.localdomain>
Message-ID: <20120203104103.GA21108@sleipnir.bytereef.org>


Stefan Krah <stefan-usenet at bytereef.org> added the comment:

Antoine Pitrou <report at bugs.python.org> wrote:
> I'm sure some admins will prefer using their system's packages (I think
> buildbot is packaged for Debian/Ubuntu, I see it in Mageia's packages,
> not sure about Fedora).

Yes, certainly. I had a bad experience using the packaged buildbot-slave,
but I don't remember which distro it was.

Generally speaking, I've had so much trouble with rarely used packages
on multiple distros that I *always* compile or install that kind of
software directly from upstream.

> Anyway, the current instructions are on the wiki:
> http://wiki.python.org/moin/BuildBot

That's probably the best place.

Eric: I'm afraid the excerpts from the mailing list discussion you put
there are a bit confusing and don't reflect any kind of majority opinion.

For example I'm running two bots and I don't even know what this means:

"Some tests, as the start of this thread [...] indicates, must have some
 special logic to make sure they do or do not run, or run differently, in
 privileged vs. unprivileged configurations, but generally speaking most
 things should work in both places."

That does not concern a buildbot owner, since he has no influence on that.

Also, you included that nasty quote "executing arbitrarily horrible and/or
malicious code". I re-read the thread, and that quote is a half-sarcastic
concession from Glyph (who actually had a much lighter view on the whole
situation initially!) to the concerns of the people who were almost accusing
buildbot owners of being clueless.

The other side of the discussion (Martin's view) is missing completely,
despite the fact that most core developers *probably* share that view.

I'm sure you meant well, but I think we should give buildbot admins some
credit. Experienced admins don't need any advice, inexperienced admins
would be served better by a cookbook approach.

The script I posted is a start: All buildbot software is in /home/buildbot
and runs under the password-less user buildbot. In combination with a VM,
this is enough for me. If anyone thinks this is not secure enough and wants
to add chroot, jails, whatever, the best way forward is to post an improved
version.

----------

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

From report at bugs.python.org  Fri Feb  3 14:41:39 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 13:41:39 +0000
Subject: [docs] [issue13850] Summary tables for argparse add_argument options
In-Reply-To: <1327384498.23.0.981832544617.issue13850@psf.upfronthosting.co.za>
Message-ID: <1328276499.2.0.421899429572.issue13850@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


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

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

From report at bugs.python.org  Fri Feb  3 14:48:48 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 13:48:48 +0000
Subject: [docs] [issue13865] distutils documentation says Extension has
	"optional"	argument
In-Reply-To: <1327525493.46.0.373823292504.issue13865@psf.upfronthosting.co.za>
Message-ID: <1328276928.16.0.934665613779.issue13865@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

It was me who ported that doc change from 3.2, but distutils in 2.7 does not provide that feature.  Thanks for catching it, I?ll revert the commit when I get the chance.

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

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

From report at bugs.python.org  Fri Feb  3 14:49:01 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 13:49:01 +0000
Subject: [docs] [issue13865] distutils documentation says Extension has
	"optional"	argument
In-Reply-To: <1327525493.46.0.373823292504.issue13865@psf.upfronthosting.co.za>
Message-ID: <1328276941.29.0.825936508882.issue13865@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
assignee: docs at python -> eric.araujo

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

From report at bugs.python.org  Fri Feb  3 14:54:42 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 13:54:42 +0000
Subject: [docs] [issue13875] cmd: no user documentation
In-Reply-To: <1327588077.77.0.0954132482021.issue13875@psf.upfronthosting.co.za>
Message-ID: <1328277282.53.0.871675858088.issue13875@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

+1 to expanding the introduction.  Do you have a phrasing suggestion?

> MOTW links are a more global issue that was discussion on python-dev (I forget the outcome,
> but I think it was "no").
IIRC it was on python-ideas, and (among other criticisms about licensing, site reliability, etc.) the strongest opinion against adding links was Alexander?s, who reviewed the PyMOTW page for datetime and was not satisfied.  So the discussion ruled out systematic addition of links for all modules, but I think that as usual a core dev is free to add a link to an external resource if they think it is useful.

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

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

From report at bugs.python.org  Fri Feb  3 14:55:13 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 13:55:13 +0000
Subject: [docs] [issue13875] Improve description of cmd module
In-Reply-To: <1327588077.77.0.0954132482021.issue13875@psf.upfronthosting.co.za>
Message-ID: <1328277313.98.0.751745413819.issue13875@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
resolution: works for me -> 
stage:  -> needs patch
title: cmd: no user documentation -> Improve description of cmd module

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

From report at bugs.python.org  Fri Feb  3 14:58:21 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 13:58:21 +0000
Subject: [docs] [issue13605] document argparse's nargs=REMAINDER
In-Reply-To: <1323955710.42.0.753468095058.issue13605@psf.upfronthosting.co.za>
Message-ID: <1328277501.08.0.776584551838.issue13605@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

It would be best if the 3.x docs did not use a print statement <wink>.  The code block should also be preceded by ::.

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

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

From report at bugs.python.org  Fri Feb  3 14:58:59 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 13:58:59 +0000
Subject: [docs] [issue13879] Argparse does not support subparser aliases in
	2.7
In-Reply-To: <1327597168.42.0.828007379667.issue13879@psf.upfronthosting.co.za>
Message-ID: <1328277539.11.0.0919353619301.issue13879@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Agreed, this looks like a doc glitch.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python, eric.araujo, ezio.melotti

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

From report at bugs.python.org  Fri Feb  3 15:09:52 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 14:09:52 +0000
Subject: [docs] [issue13833] No documentation for PyStructSequence
In-Reply-To: <1327010174.09.0.407534369688.issue13833@psf.upfronthosting.co.za>
Message-ID: <1328278192.22.0.879663105298.issue13833@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
nosy: +eric.araujo
stage:  -> patch review
versions: +Python 2.7, Python 3.2

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

From report at bugs.python.org  Fri Feb  3 15:13:23 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 14:13:23 +0000
Subject: [docs] [issue13799] Base 16 should be hexadecimal in Unicode HOWTO
In-Reply-To: <1326718246.49.0.980962494093.issue13799@psf.upfronthosting.co.za>
Message-ID: <1328278403.45.0.110097054804.issue13799@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


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

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

From report at bugs.python.org  Fri Feb  3 15:15:40 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 14:15:40 +0000
Subject: [docs] [issue13770] python3 & json: add ensure_ascii documentation
In-Reply-To: <1326300131.17.0.750918490995.issue13770@psf.upfronthosting.co.za>
Message-ID: <1328278540.51.0.222500604329.issue13770@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

FTR I?ve fixed this and now need to find a place with SSH access so I can push.

----------

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

From report at bugs.python.org  Fri Feb  3 15:35:00 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 03 Feb 2012 14:35:00 +0000
Subject: [docs] [issue13826] Having a shlex example in the subprocess.Popen
	docs is	confusing
In-Reply-To: <1326983115.48.0.551767400168.issue13826@psf.upfronthosting.co.za>
Message-ID: <1328279700.78.0.882346001875.issue13826@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


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

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

From report at bugs.python.org  Fri Feb  3 18:38:54 2012
From: report at bugs.python.org (Eric Snow)
Date: Fri, 03 Feb 2012 17:38:54 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1318011517.56.0.343886781977.issue13124@psf.upfronthosting.co.za>
Message-ID: <1328290734.44.0.984144953749.issue13124@psf.upfronthosting.co.za>


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

No problem, Stefan.  :)  The main motivation was to capture the discussion at the time so that something actually came of it.

Adding info to the devguide, essentially the catalog/how-to of core dev activities, was meant to simply provide another clear avenue for those that wanted to help with Python's core development.  If not a dedicated page, we should at least have a link in the "Contributing" section to the (single, authoritative) resource we have on setting-up/running a build slave, regardless of where that resource resides.

That said, I gladly defer to those that are more involved with the buildbots.  Incidentally, the second patch is a bit cleaner than the first.

----------

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

From report at bugs.python.org  Fri Feb  3 19:03:36 2012
From: report at bugs.python.org (Tim Willis)
Date: Fri, 03 Feb 2012 18:03:36 +0000
Subject: [docs] [issue13879] Argparse does not support subparser aliases in
	2.7
In-Reply-To: <1327597168.42.0.828007379667.issue13879@psf.upfronthosting.co.za>
Message-ID: <1328292216.63.0.614115651886.issue13879@psf.upfronthosting.co.za>


Tim Willis <schadenfreude328 at gmail.com> added the comment:

The documentation appears to be up to date in the current 2.7 repository, so this can probably be marked as closed/fixed.

----------

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

From report at bugs.python.org  Fri Feb  3 21:18:16 2012
From: report at bugs.python.org (Stefan Krah)
Date: Fri, 03 Feb 2012 20:18:16 +0000
Subject: [docs] [issue13124] Add "Running a Build Slave" page to the devguide
In-Reply-To: <1328290734.44.0.984144953749.issue13124@psf.upfronthosting.co.za>
Message-ID: <20120203201812.GA24627@sleipnir.bytereef.org>


Stefan Krah <stefan-usenet at bytereef.org> added the comment:

Eric Snow <report at bugs.python.org> wrote:
> Incidentally, the second patch is a bit cleaner than the first.

Yes, indeed it is. :) To prevent a misunderstanding: In my last mail I was
talking about the "Build Slaves and Security" additions to:

http://wiki.python.org/moin/BuildBot

----------

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

From report at bugs.python.org  Sat Feb  4 02:39:18 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 04 Feb 2012 01:39:18 +0000
Subject: [docs] [issue12955] urllib.request example should use "with ... as:"
In-Reply-To: <1315650628.73.0.673162910121.issue12955@psf.upfronthosting.co.za>
Message-ID: <1328319557.89.0.674064527887.issue12955@psf.upfronthosting.co.za>


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

Senthil:
http://docs.python.org/dev/library/contextlib.html#contextlib.closing
currently has this example:

from urllib.request import urlopen
with closing(urlopen('http://www.python.org')) as page:

which is misleading in that the object returned from urlopen
<class 'http.client.HTTPResponse'>
has __enter__ and __exit__ methods and therefore is a c.m. in itself and does not need to be wrapped in closing(). I did not really understand from your comment whether there is any need to use closing() with anything returned in urllib. 

At the moment, shelves are not C.M.s, and would make better examples, but #13896 suggests 'fixing' that also.

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

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

From report at bugs.python.org  Sat Feb  4 02:58:13 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 04 Feb 2012 01:58:13 +0000
Subject: [docs] [issue13899] re pattern r"[\A]" should work like "A" but
	matches	nothing. Ditto B and Z.
In-Reply-To: <1327789733.95.0.48339527102.issue13899@psf.upfronthosting.co.za>
Message-ID: <1328320693.04.0.426159892049.issue13899@psf.upfronthosting.co.za>


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

Does anyone have regex installed, to see what it does?

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

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

From report at bugs.python.org  Sat Feb  4 03:28:01 2012
From: report at bugs.python.org (John Roth)
Date: Sat, 04 Feb 2012 02:28:01 +0000
Subject: [docs] [issue13915] Update Tutorial 6.1.3 for PEP 3145
In-Reply-To: <1328053198.63.0.994035147287.issue13915@psf.upfronthosting.co.za>
Message-ID: <1328322481.74.0.780663998328.issue13915@psf.upfronthosting.co.za>


John Roth <JohnRoth1 at gmail.com> added the comment:

I apologize for not submitting this in patch format, but I don't have a development system available.

I suggest replacing the entire 6.1.3 section with: 

To speed up loading modules, Python caches the compiled version of each module in the __pycache__ directory under the name module.cpython-xy.pyc, where xy is the Python version number. For example, in release 3.2 the compiled version of spam.py would be cached as __pycache__/spam.cpython-32.pyc. This naming convention allows compiled modules from different releases and different versions of Python to coexist.

Python checks the revision date of the source against the compiled version to see if it?s out of date and needs to be recompiled. This is a completely automatic process. Also, the compiled modules are platform-independent, so the same library can be shared among systems with different architectures.

Python does not check the cache in two circumstances. First, it always recompiles and does not store the result for the module that?s loaded directly from the command line. Second, it does not check the cache if there is no source module. To support a non-source (compiled only) distribution, the compiled module must be in the source directory, and there must not be a source module.

Some tips for experts:

* You can use the -O or -OO switches on the Python command to reduce the size of a compiled module. The -O switch removes assert statements, the -OO switch removes both assert statements and __doc__ strings. Neither optimization affects running time, however it?s possible that they may affect run-time behavior. Optimized modules have a .pyo rather than a .pyc suffix. Future releases may change the effects of optimization.

*   The module compileall can create .pyc files (or .pyo files when -O is used) for all modules in a directory.

*   There is more detail on this process, including a flow chart of the decisions, in PEP 3147.

----------
nosy: +JohnRoth1

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

From report at bugs.python.org  Sat Feb  4 04:08:52 2012
From: report at bugs.python.org (Matthew Barnett)
Date: Sat, 04 Feb 2012 03:08:52 +0000
Subject: [docs] [issue13899] re pattern r"[\A]" should work like "A" but
	matches	nothing. Ditto B and Z.
In-Reply-To: <1327789733.95.0.48339527102.issue13899@psf.upfronthosting.co.za>
Message-ID: <1328324932.36.0.327062416186.issue13899@psf.upfronthosting.co.za>


Matthew Barnett <python at mrabarnett.plus.com> added the comment:

This should answer that question:

>>> re.findall(r"[\A\C]", r"\AC")
['C']
>>> regex.findall(r"[\A\C]", r"\AC")
['A', 'C']

The behaviour of regex is intended to match that of re for backwards compatibility.

----------

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

From report at bugs.python.org  Sat Feb  4 05:56:09 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 04 Feb 2012 04:56:09 +0000
Subject: [docs] [issue13899] re pattern r"[\A]" should work like "A" but
	matches	nothing. Ditto B and Z.
In-Reply-To: <1327789733.95.0.48339527102.issue13899@psf.upfronthosting.co.za>
Message-ID: <1328331369.43.0.804705765042.issue13899@psf.upfronthosting.co.za>


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

I presume you intend regex to match the spec rather than bugs. So if re has a bug in an obsure corner case and the spec is ambiguous, as I have the impression is the case here, using the interpretation embodied in regex would avoid creating a conflict.

----------

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

From report at bugs.python.org  Sat Feb  4 08:11:07 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 04 Feb 2012 07:11:07 +0000
Subject: [docs] [issue12955] urllib.request example should use "with ... as:"
In-Reply-To: <1315650628.73.0.673162910121.issue12955@psf.upfronthosting.co.za>
Message-ID: <1328339467.1.0.73619062067.issue12955@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Either we find a commonly used stdlib class that is not a context manager but has a close method and is not going to become a context manager (I can?t see why such a thing would be), or we can add something like: ?closing is useful with code that you can?t change to add context management, for example urllib.urlopen before Python 3.3?.

----------

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

From report at bugs.python.org  Sat Feb  4 08:20:08 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 04 Feb 2012 07:20:08 +0000
Subject: [docs] [issue13879] Argparse does not support subparser aliases in
	2.7
In-Reply-To: <1327597168.42.0.828007379667.issue13879@psf.upfronthosting.co.za>
Message-ID: <1328340008.07.0.314458393978.issue13879@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Ah, I did not see that your first message talked about the dev doc, which is 3.3.

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

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

From report at bugs.python.org  Sat Feb  4 09:20:43 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 04 Feb 2012 08:20:43 +0000
Subject: [docs] [issue13915] Update Tutorial 6.1.3 for PEP 3145
In-Reply-To: <1328053198.63.0.994035147287.issue13915@psf.upfronthosting.co.za>
Message-ID: <1328343643.72.0.89843167646.issue13915@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


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

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

From report at bugs.python.org  Sat Feb  4 12:23:28 2012
From: report at bugs.python.org (Johannes Bauer)
Date: Sat, 04 Feb 2012 11:23:28 +0000
Subject: [docs] [issue13700] imaplib.IMAP4.authenticate authobject fails
	with PLAIN	mechanism
In-Reply-To: <1325553089.14.0.504978991098.issue13700@psf.upfronthosting.co.za>
Message-ID: <1328354608.75.0.695810964899.issue13700@psf.upfronthosting.co.za>


Johannes Bauer <dfnsonfsduifb at gmx.de> added the comment:

Issue also affects Python3.1. Hunk succeeds against 3.1 imaplib.py and works for me.

----------
nosy: +joebauer
versions: +Python 3.1

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

From julian.ceipek at students.olin.edu  Fri Feb  3 05:08:46 2012
From: julian.ceipek at students.olin.edu (Julian Ceipek)
Date: Thu, 2 Feb 2012 23:08:46 -0500
Subject: [docs] 18.1.2.1. FeedParser API Error
Message-ID: <CAKqeJerm_-5U9JaCWqBEWr4s6HQQe+7kbO6OZuguG5U+F_8j1Q@mail.gmail.com>

The following is inaccurate in 18.1.2.1.:

Here is the API for the FeedParser:
> class email.parser.FeedParser([_factory])
> Create a FeedParser instance. Optional _factory is a no-argument callable
> that will be called whenever a new message object is needed. It defaults to
> the email.message.Message class.


It seems to actually be "email.FeedParser.FeedParser("

-Julian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120202/99a892ae/attachment.html>

From ted.sybil at gmail.com  Thu Feb  2 05:53:42 2012
From: ted.sybil at gmail.com (Ted Yin)
Date: Thu, 2 Feb 2012 12:53:42 +0800
Subject: [docs] Bug in the Reference Data Model
Message-ID: <CALL10kpr1+ahWR690+nD+W15HRw2Kw3wDyw05YHnC8AaADRSAQ@mail.gmail.com>

It's said that :

When it would yield a class method object, it is transformed into a bound
user-defined method object whose im_class and im_self attributes are both C.

in the Reference <http://docs.python.org/reference/datamodel.html>

And I did an EX.

>>> class C(object) :
...     @classmethod
...     def cm(cls) : print cls
...
>>> C.cm
<bound method type.cm of <class '__main__.C'>>
>>> C.cm.im_self
<class '__main__.C'>
>>> C.cm.im_class
<type 'type'>

It's not hard for me to understand the result.

But unfortunately, in the reference, it's told that im_self should be *the
same* as im_class.

And in my opinion , 'im_self' shold be C, but im_class is 'type' since C's
metaclass is type. So they're obviously *not* 'both C'.
-- 
[This information is automatically generated]
*ted.sybil* aka. *ymfoi* aka. *Ted Yin*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120202/b98e3466/attachment-0001.html>

From report at bugs.python.org  Sat Feb  4 19:37:26 2012
From: report at bugs.python.org (Matthew Barnett)
Date: Sat, 04 Feb 2012 18:37:26 +0000
Subject: [docs] [issue13899] re pattern r"[\A]" should work like "A" but
	matches	nothing. Ditto B and Z.
In-Reply-To: <1327789733.95.0.48339527102.issue13899@psf.upfronthosting.co.za>
Message-ID: <1328380646.34.0.0881770948178.issue13899@psf.upfronthosting.co.za>


Matthew Barnett <python at mrabarnett.plus.com> added the comment:

In re, "\A" within a character set should be similar to "\C", but instead it's still interpreted as meaning the start of the string. That's definitely a bug.

If it doesn't do what it's supposed to do, then it's a bug.

regex tries to be backwards compatible with re but fix such bugs.

The only buggy behaviour which it retains in its version 0 (compatible) behaviour is not splitting on a zero-width match, and that's only because GvR believes that some existing code which uses re may rely on that behaviour. In its version 1 (extended) behaviour it does split on a zero-width match.

----------

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

From report at bugs.python.org  Sun Feb  5 04:04:40 2012
From: report at bugs.python.org (Ramchandra Apte)
Date: Sun, 05 Feb 2012 03:04:40 +0000
Subject: [docs] [issue13944] HMAC object called hmac
Message-ID: <1328411080.71.0.906401120074.issue13944@psf.upfronthosting.co.za>


New submission from Ramchandra Apte <maniandram01 at gmail.com>:

When the documentation for hashlib says "An HMAC object has the following methods:" the list of methods says hmac.xxx which is wrong and should be HMAC.xxx.
Thanks

----------
assignee: docs at python
components: Documentation
messages: 152657
nosy: docs at python, ramchandra.apte
priority: normal
severity: normal
status: open
title: HMAC object called hmac
type: enhancement
versions: Python 2.7, Python 3.2

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

From report at bugs.python.org  Sun Feb  5 09:28:41 2012
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 05 Feb 2012 08:28:41 +0000
Subject: [docs] [issue13944] HMAC object called hmac
In-Reply-To: <1328411080.71.0.906401120074.issue13944@psf.upfronthosting.co.za>
Message-ID: <E1RtxSi-0003OX-4j@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 7c263bfc92f5 by Georg Brandl in branch '2.7':
Closes #13944: fix capitalization of class name.
http://hg.python.org/cpython/rev/7c263bfc92f5

New changeset cd748bab3cdd by Georg Brandl in branch '3.2':
Closes #13944: fix capitalization of class name.
http://hg.python.org/cpython/rev/cd748bab3cdd

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

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

From report at bugs.python.org  Sun Feb  5 13:50:12 2012
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 05 Feb 2012 12:50:12 +0000
Subject: [docs] [issue13770] python3 & json: add ensure_ascii documentation
In-Reply-To: <1326300131.17.0.750918490995.issue13770@psf.upfronthosting.co.za>
Message-ID: <E1Ru1Xm-0007BK-Ve@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 33d6da1b1c71 by ?ric Araujo in branch '3.2':
Document json.dump ensure_ascii parameter (#13770)
http://hg.python.org/cpython/rev/33d6da1b1c71

New changeset 1cb9b8126534 by ?ric Araujo in branch 'default':
Merge edits from 3.2 (#13716, #1040439, #2945, #13770, #6715)
http://hg.python.org/cpython/rev/1cb9b8126534

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

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

From report at bugs.python.org  Sun Feb  5 13:50:14 2012
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 05 Feb 2012 12:50:14 +0000
Subject: [docs] [issue13716] distutils doc contains lots of XXX
In-Reply-To: <1325790136.17.0.881224521536.issue13716@psf.upfronthosting.co.za>
Message-ID: <E1Ru1Xm-0007BK-Vu@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 3d25869fce0c by ?ric Araujo in branch '3.2':
Hide or remove user-visible XXX notes from distutils doc (#13716).
http://hg.python.org/cpython/rev/3d25869fce0c

New changeset 1cb9b8126534 by ?ric Araujo in branch 'default':
Merge edits from 3.2 (#13716, #1040439, #2945, #13770, #6715)
http://hg.python.org/cpython/rev/1cb9b8126534

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

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

From report at bugs.python.org  Sun Feb  5 13:50:15 2012
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 05 Feb 2012 12:50:15 +0000
Subject: [docs] [issue1040439] Missing documentation on how to link with
	libpython
Message-ID: <E1Ru1Xm-0007BK-Vp@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 79e8de78abd0 by ?ric Araujo in branch '3.2':
Markup improvements for the embedding CPython doc patch from #1040439
http://hg.python.org/cpython/rev/79e8de78abd0

New changeset 1cb9b8126534 by ?ric Araujo in branch 'default':
Merge edits from 3.2 (#13716, #1040439, #2945, #13770, #6715)
http://hg.python.org/cpython/rev/1cb9b8126534

----------

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

From report at bugs.python.org  Mon Feb  6 16:51:33 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 06 Feb 2012 15:51:33 +0000
Subject: [docs] [issue1040439] Missing documentation on how to link with
	libpython
Message-ID: <1328543493.14.0.0255328761893.issue1040439@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Is there still work to do on this issue?

----------

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

From report at bugs.python.org  Mon Feb  6 17:20:59 2012
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 06 Feb 2012 16:20:59 +0000
Subject: [docs] [issue1040439] Missing documentation on how to link with
	libpython
Message-ID: <1328545259.19.0.339436682557.issue1040439@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

> Is there still work to do on this issue?

Not for Unix, no. I don't if it's applicable to Windows.

----------

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

From report at bugs.python.org  Mon Feb  6 17:36:20 2012
From: report at bugs.python.org (Amaury Forgeot d'Arc)
Date: Mon, 06 Feb 2012 16:36:20 +0000
Subject: [docs] [issue13951] 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: <1328546180.74.0.860120423953.issue13951@psf.upfronthosting.co.za>


Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:

[Please do not change issue titles - your recommendation was enough]

Indeed, incorrect usage of ctypes can crash the program, and there is nothing Python can do.

But I could not find any warning about this in the documentation, except maybe this sentence: "There are, however, enough ways to crash Python with ctypes, so you should be careful anyway."
Let's turn this into a doc issue, then.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +amaury.forgeotdarc, docs at python
title: please close - Seg Fault in .so called by ctypes causes the interpreter to Seg Fault -> Seg Fault in .so called by ctypes causes the interpreter to Seg Fault

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

From report at bugs.python.org  Mon Feb  6 19:20:25 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Mon, 06 Feb 2012 18:20:25 +0000
Subject: [docs] [issue8255] Packaging step-by-step tutorial
In-Reply-To: <1269787637.04.0.463586986817.issue8255@psf.upfronthosting.co.za>
Message-ID: <1328552425.76.0.225478345346.issue8255@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/issue8255>
_______________________________________

From report at bugs.python.org  Tue Feb  7 03:06:21 2012
From: report at bugs.python.org (Sung-Yu Chen)
Date: Tue, 07 Feb 2012 02:06:21 +0000
Subject: [docs] [issue12970] os.walk() consider some symlinks as dirs
	instead of	non-dirs
In-Reply-To: <1315918932.02.0.810529185276.issue12970@psf.upfronthosting.co.za>
Message-ID: <1328580381.73.0.371450945481.issue12970@psf.upfronthosting.co.za>


Changes by Sung-Yu Chen <eesonyu at gmail.com>:


----------
nosy: +Sung-Yu.Chen

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

From report at bugs.python.org  Tue Feb  7 12:54:27 2012
From: report at bugs.python.org (Nick Coghlan)
Date: Tue, 07 Feb 2012 11:54:27 +0000
Subject: [docs] [issue12970] os.walk() consider some symlinks as dirs
	instead of	non-dirs
In-Reply-To: <1315918932.02.0.810529185276.issue12970@psf.upfronthosting.co.za>
Message-ID: <1328615667.67.0.554991283436.issue12970@psf.upfronthosting.co.za>


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

This behaviour came up recently when implementing os.fwalk() [1]. There are problems with all 3 possible approaches (list as dirs, list as files, don't list at all) when followlinks is False. Since all alternatives are potentially surprising, the current behaviour wins by default (as people will already have written their code to cope with that behaviour and there's no net gain in changing the default, since the desired treatment of such links will vary according to the task at hand).

As a result, I'm converting this to a pure documentation issue - the os.walk() docs should definitely mention this subtlety. The behaviour won't be changing, though.

[1] http://bugs.python.org/issue13734,#msg151077

----------
components:  -Library (Lib)
nosy: +ncoghlan
type: behavior -> enhancement
versions:  -Python 3.1, Python 3.4

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

From report at bugs.python.org  Wed Feb  8 00:44:29 2012
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 07 Feb 2012 23:44:29 +0000
Subject: [docs] [issue13286] PEP 3151 breaks backward compatibility: it
	should be	documented
In-Reply-To: <1319811530.69.0.689775391155.issue13286@psf.upfronthosting.co.za>
Message-ID: <1328658269.12.0.886836053352.issue13286@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

The code was fixed in importlib. I don't think that this borderline case should be documented anywhere, so I close this issue.

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

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

From report at bugs.python.org  Wed Feb  8 04:42:16 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Wed, 08 Feb 2012 03:42:16 +0000
Subject: [docs] [issue11379] Remove "lightweight" from minidom description
In-Reply-To: <1299093908.17.0.828802315354.issue11379@psf.upfronthosting.co.za>
Message-ID: <1328672535.95.0.338904305328.issue11379@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

IMHO this wording proposed by Stefan:

"""
[[Note: The xml.dom.minidom module provides an implementation of the W3C-DOM whose API is similar to that in other programming languages. Users who are unfamiliar with the W3C-DOM interface or who would like to write less code for processing XML files should consider using the xml.etree.ElementTree module instead.]]
"""

Sounds very reasonable. Perhaps something about a more Pythonic API can also be added there, in addition to "to write less code".

Any objections?

----------
nosy: +eli.bendersky

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

From report at bugs.python.org  Wed Feb  8 11:30:08 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Wed, 08 Feb 2012 10:30:08 +0000
Subject: [docs] [issue11379] Remove "lightweight" from minidom description
In-Reply-To: <1299093908.17.0.828802315354.issue11379@psf.upfronthosting.co.za>
Message-ID: <1328697008.25.0.412130044141.issue11379@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/issue11379>
_______________________________________

From senthil at uthcode.com  Wed Feb  8 15:32:52 2012
From: senthil at uthcode.com (Senthil Kumaran)
Date: Wed, 8 Feb 2012 22:32:52 +0800
Subject: [docs] [issue11379] Remove "lightweight" from minidom
	description
In-Reply-To: <1328672535.95.0.338904305328.issue11379@psf.upfronthosting.co.za>
References: <1299093908.17.0.828802315354.issue11379@psf.upfronthosting.co.za>
	<1328672535.95.0.338904305328.issue11379@psf.upfronthosting.co.za>
Message-ID: <20120208143252.GC1896@mathmagic>

On Wed, Feb 08, 2012 at 03:42:16AM +0000, Eli Bendersky wrote:
> Any objections?

None. The explanation sounds reasonable.



From report at bugs.python.org  Wed Feb  8 16:11:53 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 08 Feb 2012 15:11:53 +0000
Subject: [docs] [issue11379] Remove "lightweight" from minidom description
In-Reply-To: <1299093908.17.0.828802315354.issue11379@psf.upfronthosting.co.za>
Message-ID: <1328713913.24.0.0637324565991.issue11379@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

+1 to the suggested wording.

-1 to talking about a more pythonic API.

(Want a nit?  s/W3C-DOM/W3C DOM/)

----------

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

From report at bugs.python.org  Wed Feb  8 17:27:54 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 08 Feb 2012 16:27:54 +0000
Subject: [docs] [issue13915] Update tutorial/modules for PEP 3147
In-Reply-To: <1328053198.63.0.994035147287.issue13915@psf.upfronthosting.co.za>
Message-ID: <1328718474.96.0.775354732112.issue13915@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
title: Update Tutorial 6.1.3 for PEP 3145 -> Update tutorial/modules for PEP 3147

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

From report at bugs.python.org  Thu Feb  9 05:10:31 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 09 Feb 2012 04:10:31 +0000
Subject: [docs] [issue11379] Remove "lightweight" from minidom description
In-Reply-To: <1299093908.17.0.828802315354.issue11379@psf.upfronthosting.co.za>
Message-ID: <1328760630.83.0.204863401001.issue11379@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

Martin, do you find the wording I quoted (*without* the reference to a more Pythonic API) acceptable?

----------

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

From report at bugs.python.org  Thu Feb  9 05:32:57 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 09 Feb 2012 04:32:57 +0000
Subject: [docs] [issue1040439] Missing documentation on how to link with
	libpython
Message-ID: <1328761977.36.0.406346701453.issue1040439@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

ISTM that part of the doc specifically deals with Unix, so this issue can be closed as completed.

Windows is a different issue. Perhaps the documentation should have a new section on embedding on Windows, similarly to the "Building C and C++ Extensions on Windows" section in the "extending" documentation. Anyway, if there's interest in that, it should be a separate issue.

----------

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

From report at bugs.python.org  Thu Feb  9 05:35:49 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 09 Feb 2012 04:35:49 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1302623785.46.0.16009713021.issue11836@psf.upfronthosting.co.za>
Message-ID: <1328762149.24.0.409781879709.issue11836@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

Sandro, can you commit, taking Antoine's note into account?

----------

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

From report at bugs.python.org  Thu Feb  9 11:23:00 2012
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 09 Feb 2012 10:23:00 +0000
Subject: [docs] [issue9021] no copy.copy problem description
In-Reply-To: <1276816713.34.0.416523004663.issue9021@psf.upfronthosting.co.za>
Message-ID: <E1RvR9X-0001JE-AV@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 0e050b38e92b by Senthil Kumaran in branch '2.7':
Issue #9021: Add an introduction to the copy module. Doc changes suggested by Terry Reedy.
http://hg.python.org/cpython/rev/0e050b38e92b

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

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

From report at bugs.python.org  Thu Feb  9 11:28:07 2012
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 09 Feb 2012 10:28:07 +0000
Subject: [docs] [issue9021] no copy.copy problem description
In-Reply-To: <1276816713.34.0.416523004663.issue9021@psf.upfronthosting.co.za>
Message-ID: <E1RvREU-0001rm-7w@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset a352e24b9907 by Senthil Kumaran in branch '3.2':
Issue #9021 - Introduce copy module better. Doc changes suggested by Terry
http://hg.python.org/cpython/rev/a352e24b9907

New changeset bf6f306ad5cf by Senthil Kumaran in branch 'default':
merge from 3.2
http://hg.python.org/cpython/rev/bf6f306ad5cf

----------

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

From report at bugs.python.org  Thu Feb  9 11:29:15 2012
From: report at bugs.python.org (Senthil Kumaran)
Date: Thu, 09 Feb 2012 10:29:15 +0000
Subject: [docs] [issue9021] no copy.copy problem description
In-Reply-To: <1276816713.34.0.416523004663.issue9021@psf.upfronthosting.co.za>
Message-ID: <1328783355.82.0.11598382993.issue9021@psf.upfronthosting.co.za>


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

Added suggested changes to the documentation. Thanks.

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

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

From report at bugs.python.org  Thu Feb  9 11:38:52 2012
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 09 Feb 2012 10:38:52 +0000
Subject: [docs] [issue9021] no copy.copy problem description
In-Reply-To: <1276816713.34.0.416523004663.issue9021@psf.upfronthosting.co.za>
Message-ID: <1328783932.51.0.082441750152.issue9021@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Perfectionist in me says that now copy.copy theory should be diluted with examples for those who can't grasp the concept of "binding of variables", but the patch perfectly covers the original user story. Thanks.

----------

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

From report at bugs.python.org  Thu Feb  9 21:16:44 2012
From: report at bugs.python.org (Petri Lehtinen)
Date: Thu, 09 Feb 2012 20:16:44 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <1328818604.3.0.0946249859951.issue13491@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

Attaching an updated patch with the following changes:

- Updated to apply on current default branch

- No examples included in the documentation now require createdb.py to be run. There were only three examples that required it, but these were refactored a bit. In the Doc/includes/sqlite3 directory there are still some scripts that require the createdb.py, so I didn't nuke the file.

- I also removed the strange "The arguments to :meth:`executescript` must be :func:`bytes` objects" sentence from the patch. I assume it was a mistake, as it's wrong.

----------
Added file: http://bugs.python.org/file24469/sqlite_code_update_v3.patch

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

From report at bugs.python.org  Thu Feb  9 21:17:41 2012
From: report at bugs.python.org (Petri Lehtinen)
Date: Thu, 09 Feb 2012 20:17:41 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <1328818661.05.0.175873319468.issue13491@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

Ah, and I added a working example of a custom text_factory function to Doc/includes/sqlite3/text_factory.py, too.

----------

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

From report at bugs.python.org  Fri Feb 10 05:11:20 2012
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 10 Feb 2012 04:11:20 +0000
Subject: [docs] [issue9442] Update sys.version doc
In-Reply-To: <1280605593.44.0.301230771819.issue9442@psf.upfronthosting.co.za>
Message-ID: <E1RvhpN-0000vs-EV@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 0cc1fbbb473d by ?ric Araujo in branch 'default':
Use sys.version_info instead of sys.version.
http://hg.python.org/distutils2/rev/0cc1fbbb473d

----------

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

From report at bugs.python.org  Fri Feb 10 05:21:01 2012
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 10 Feb 2012 04:21:01 +0000
Subject: [docs] [issue9442] Update sys.version doc
In-Reply-To: <1280605593.44.0.301230771819.issue9442@psf.upfronthosting.co.za>
Message-ID: <E1Rvhyl-0001jA-Qg@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 6fdcfe348435 by ?ric Araujo in branch 'default':
Use sys.version_info instead of sys.version in packaging.
http://hg.python.org/cpython/rev/6fdcfe348435

----------

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

From report at bugs.python.org  Fri Feb 10 05:32:27 2012
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 10 Feb 2012 04:32:27 +0000
Subject: [docs] [issue13865] distutils documentation says Extension has
	"optional"	argument
In-Reply-To: <1327525493.46.0.373823292504.issue13865@psf.upfronthosting.co.za>
Message-ID: <E1Rvi9j-0002T4-3o@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset cf1c466ee9e0 by ?ric Araujo in branch '2.7':
distutils 2.7?s Extension does not support optional (#13865).
http://hg.python.org/cpython/rev/cf1c466ee9e0

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

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

From report at bugs.python.org  Fri Feb 10 05:36:24 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 10 Feb 2012 04:36:24 +0000
Subject: [docs] [issue13865] distutils documentation says Extension has
	"optional"	argument
In-Reply-To: <1327525493.46.0.373823292504.issue13865@psf.upfronthosting.co.za>
Message-ID: <1328848583.93.0.108665331138.issue13865@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Fixed, cheers!

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

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

From report at bugs.python.org  Sat Feb 11 06:12:14 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 11 Feb 2012 05:12:14 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <1328937134.2.0.177722215774.issue13491@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> No examples included in the documentation now require createdb.py to be run.
Cool!  These fixes should make it to 2.7 too; I can propose a patch if you don?t want to backport yourself.

> In the Doc/includes/sqlite3 directory there are still some scripts that require the
> createdb.py, so I didn't nuke the file.
Do these scripts (or a README file) explain about createdb.py?

> I also removed the strange "The arguments to :meth:`executescript` must be :func:`bytes`
> objects" sentence from the patch. I assume it was a mistake, as it's wrong.
Why not change it so that it?s correct?  (Maybe looking at the file history would show where the mistake comes from.)

> Ah, and I added a working example of a custom text_factory function
Nice.

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

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

From report at bugs.python.org  Sat Feb 11 21:16:17 2012
From: report at bugs.python.org (Matthew Woodcraft)
Date: Sat, 11 Feb 2012 20:16:17 +0000
Subject: [docs] [issue13995] sqlite3 Cursor.rowcount documentation for old
	sqlite bug
Message-ID: <1328991377.3.0.315009784222.issue13995@psf.upfronthosting.co.za>


New submission from Matthew Woodcraft <matthew at woodcraft.me.uk>:

The documentation for the sqlite3 module contains the following statement, under 'Cursor.rowcount':

  For DELETE statements, SQLite reports rowcount as 0 if you make a DELETE FROM table without any condition.

This doesn't happen for me (with sqlite 3.7.9): rowcount returns the correct value in this case.

According to http://www.sqlite.org/lang_delete.html#truncateopt , this was a bug that was fixed in SQLite 3.6.5 (in 2008).

So I think the Python documentation should either omit this paragraph, or else explain that it only applies to older versions of SQLite.


Also, the first example under 'Using shortcut methods' has code to work around this bug, which should perhaps be removed.

----------
assignee: docs at python
components: Documentation
messages: 153136
nosy: docs at python, mattheww
priority: normal
severity: normal
status: open
title: sqlite3 Cursor.rowcount documentation for old sqlite bug

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

From report at bugs.python.org  Sat Feb 11 22:11:09 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Sat, 11 Feb 2012 21:11:09 +0000
Subject: [docs] [issue13996] "What's New in Python" should have initial
	release date	on heading
Message-ID: <1328994669.43.0.0878472757687.issue13996@psf.upfronthosting.co.za>


New submission from Tshepang Lekhonkhobe <tshepang at gmail.com>:

As an example, the date near the top of this document http://docs.python.org/py3k/whatsnew/3.0.html matches that of today, which can be misleading (it appears as if the thing was released today).

Also, by initial release, I mean the first "final", not the point release. Maybe any other date mentioned would perhaps be the date the docs were updated, *not* the date they were rebuilt.

----------
assignee: docs at python
components: Documentation
messages: 153138
nosy: docs at python, tshepang
priority: normal
severity: normal
status: open
title: "What's New in Python" should have initial release date on heading
type: enhancement
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3

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

From report at bugs.python.org  Sat Feb 11 22:25:41 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 11 Feb 2012 21:25:41 +0000
Subject: [docs] [issue13996] "What's New in Python" should have initial
	release date	on heading
In-Reply-To: <1328994669.43.0.0878472757687.issue13996@psf.upfronthosting.co.za>
Message-ID: <1328995541.36.0.513787041797.issue13996@psf.upfronthosting.co.za>


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


----------
nosy: +eric.araujo, ezio.melotti, georg.brandl, terry.reedy
versions:  -Python 2.6, Python 3.1

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

From report at bugs.python.org  Sun Feb 12 03:44:36 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 12 Feb 2012 02:44:36 +0000
Subject: [docs] [issue13996] "What's New in Python" should have initial
	release date	on heading
In-Reply-To: <1328994669.43.0.0878472757687.issue13996@psf.upfronthosting.co.za>
Message-ID: <1329014676.08.0.549774333181.issue13996@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I agree that the date of the release would be more useful than the date of the doc build.

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

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

From report at bugs.python.org  Sun Feb 12 04:51:14 2012
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 12 Feb 2012 03:51:14 +0000
Subject: [docs] [issue13996] "What's New in Python" should have initial
	release date	on heading
In-Reply-To: <1328994669.43.0.0878472757687.issue13996@psf.upfronthosting.co.za>
Message-ID: <1329018674.55.0.270436776969.issue13996@psf.upfronthosting.co.za>


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

I think this is the wrong place to show release dates (a subject that would be further confused by having multiple point releases).

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

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

From report at bugs.python.org  Sun Feb 12 06:56:22 2012
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 12 Feb 2012 05:56:22 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329026182.16.0.134541940719.issue13997@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
title: Add open_ascii() builtin -> Clearly explain the bare minimum Python 3 users should know about Unicode
versions: +Python 3.2, Python 3.3

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

From report at bugs.python.org  Sun Feb 12 07:00:47 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 12 Feb 2012 06:00:47 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329026182.16.0.134541940719.issue13997@psf.upfronthosting.co.za>
Message-ID: <CAF-Rda8s4pBc56ihFM_w=zCxoUoSdr633=CKeTLRurm1k79wDA@mail.gmail.com>


Eli Bendersky <eliben at gmail.com> added the comment:

If the concept is accepted. I see no better place for this than the
Unicode HOWTO. If it's too long, then a TL;DR; section should be added
in the beginning detailing "the bare minimum". No need to scatter such
information in bits and pieces around the documentation. That's what
the Unicode HOWTO is for.

----------

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

From support at buddyns.com  Mon Feb  6 18:46:17 2012
From: support at buddyns.com (support at buddyns.com)
Date: Mon, 6 Feb 2012 18:46:17 +0100
Subject: [docs] example in "18.1.11. email: Examples" lacks "Date" field
Message-ID: <F78763F6-C78F-4E82-B6C9-0CF0723AC7B5@buddyns.com>

Hi folks,

Just reporting on an improvement point:

The examples in 18.1.11 about how to generate email objects produce
emails lacking the "Date" field. This field is required by RFC2822:
"The only required header fields are the origination date field and
the originator address field(s)."

The fix to the examples' code is trivial:

====================================
msg['Subject'] = "Link"
msg['From'] = me
msg['To'] = you
====================================

-->

====================================
from email.utils import formatdate	# to be added

msg['Subject'] = "Link"
msg['From'] = me
msg['To'] = you
msg['Date'] = formatdate()			# to be added
====================================

cheers
michele
The BuddyNS team

--
Follow the status of BuddyNS @ http://twitter.com/BuddyNS





From matthew.lefavor at nasa.gov  Tue Feb  7 20:11:17 2012
From: matthew.lefavor at nasa.gov (Lefavor, Matthew  (GSFC-582.0)[MICROTEL LLC])
Date: Tue, 7 Feb 2012 13:11:17 -0600
Subject: [docs] Bug Report: Incorrect Abstract Method Requirements in
 numbers.Integral Documentation
Message-ID: <CB56E185.697B%matthew.lefavor@nasa.gov>

To whom it may concern:

The documentation for numbers.Integral reports incorrect abstract method requirements for numbers.Integral.

The documentation for numbers.Integral (in both Python 2.7 and Python 3.2) states:

Subtypes Rational<http://docs.python.org/library/numbers.html#numbers.Rational> and adds a conversion to int<http://docs.python.org/library/functions.html#int>. Provides defaults for float()<http://docs.python.org/library/functions.html#float>, numerator<http://docs.python.org/library/numbers.html#numbers.Rational.numerator>, and denominator<http://docs.python.org/library/numbers.html#numbers.Rational.denominator>, and bit-string operations: <<, >>, &, ^, |, ~.

Defaults for operations <<, >>, &, ^, |, and ~ are not provided, and a look at the source code shows that they are all given as abstract methods. In addition, in Python 2.x, numbers.Integral adds an abstract conversion to long. This is not recorded in the documentation.

Originally, I was going to report this as a bug, because PEP 3141<http://www.python.org/dev/peps/pep-3141/> (the PEP that specifies the numbers module) goes so far as to include the <<, >>, &, ^, |, and ~ in the source code for numbers.Integral. It looks like somebody already had reported this years ago, however, to python-dev with Issue 3056<http://bugs.python.org/issue3056>. The issue was never resolved, but has since been closed.

Since the development community does not seem interested in adding these features, the features should be removed from documentation.

Thank you for your time,

Matthew Lefavor

NASA GSFC [Microtel, LLC]
Mail Code 699.0/Org Code 582.0
matthew.lefavor at nasa.gov
(301) 614-6818 (Desk)
(443) 758-4891 (Cell)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120207/9924f338/attachment-0001.html>

From glingle at gmail.com  Tue Feb  7 23:28:11 2012
From: glingle at gmail.com (G Lingle)
Date: Tue, 7 Feb 2012 14:28:11 -0800
Subject: [docs] strptime %m not fully specified
Message-ID: <CABvOPgTcu-zMgNbrkMNwyHng5o30QX=1K4fF1Y_NDV7FyB1Fwg@mail.gmail.com>

Hi,
In section 8.1.7 of python 2.7 docs:

.../python-2.7.1-docs-html/library/datetime.html#strftime-strptime-behavior
and in section 7.1.8 in the 3.2 docs:

There is a table that purportedly tells the behavior of strftime() and
strptime().

The entry for month is like:

%m       Month as a decimal number [01,12].

This indicates that strptime will parse 2-digit months and raise an
exception
if the month string isn't 2-digit.

I think that a note should be added to indicate that strptime()
will accept a 1-digit month.

My .02 - thx!
G
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120207/66d81b0b/attachment-0001.html>

From zhu195781 at 163.com  Wed Feb  8 03:18:06 2012
From: zhu195781 at 163.com (zhu195781)
Date: Wed, 8 Feb 2012 10:18:06 +0800
Subject: [docs] InterfaceError: connection already closed
Message-ID: <2012020810180614094411@163.com>

Hello,
I have a question about celery,before my services operation are normal,when I changed the PostgreSQL of a configuration restart service after.
Although the celery service to run normally.Now my celery running problem,the log file is always prompt "InterfaceError: connection already closed" .
I can not receive message .But I don't know how to solve it.Can you help me?
Thank you!



zhu195781
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120208/0b9eb2d0/attachment-0001.html>

From dturgut at gmail.com  Fri Feb 10 02:58:47 2012
From: dturgut at gmail.com (Deniz Turgut)
Date: Thu, 9 Feb 2012 20:58:47 -0500
Subject: [docs] "copy" function links in shutil module docs point to wrong
	destination
Message-ID: <CAL6eQ-5L+BnKQXRj+=z787NVsoAhkM-qhWyHxg7jXNL1dOJcHg@mail.gmail.com>

All the links for the "copy()" function in "shutil module" (
http://docs.python.org/library/shutil.html ) point to the "copy module" (
http://docs.python.org/library/copy.html#module-copy ) whereas they should
point to the copy function in the shutil module (
http://docs.python.org/library/shutil.html#shutil.copy ) instead.

Deniz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120209/1d7f9f39/attachment.html>

From winston at cs.wisc.edu  Fri Feb 10 18:17:31 2012
From: winston at cs.wisc.edu (Winston C. Yang)
Date: Fri, 10 Feb 2012 12:17:31 -0500
Subject: [docs] some example code uses a parameter called "next",
 resulting in a name conflict
Message-ID: <4F35512B.7090104@cs.wisc.edu>

The code below has an issue: the __init__ method has a parameter called 
"next", which conflicts with the built-in "next" in Python.

In the link, the "next" parameter is syntax-colored green instead of 
black, showing its special status.

Winston



http://docs.python.org/py3k/tutorial/errors.html
8.5 User-defined Exceptions

class  TransitionError(Error):
     """Raised when an operation attempts a state transition that's not
     allowed.

     Attributes:
         previous -- state at beginning of transition
         next -- attempted new state
         message -- explanation of why the specific transition is not allowed
     """

     def  __init__(self,  previous,  next,  message):
         self.previous  =  previous
         self.next  =  next
         self.message  =  message



From shtycksb at yandex.ru  Fri Feb 10 18:46:01 2012
From: shtycksb at yandex.ru (Sergey)
Date: Fri, 10 Feb 2012 21:46:01 +0400
Subject: [docs] Some mistakes in docs
Message-ID: <165401328895961@web3.yandex.ru>

Python 2.7.2 docs
=================

* 1
2011.08.12 02:58 Moscow Time
File /whatsnew/2.4.txt line 953.
Two words "are" instead one.
The same is in python-2.7.2-docs-html/whatsnew/2.4.html.

debian at debian:~/Documents/TXT$ cat -n  python-2.7.2-docs-text/whatsnew/2.4.txt |  grep "are are"
   953    ``dict.__contains__()`` are are now implemented as

* 2
2011.08.11 03:57 Moscow Time
File /whatsnew/2.4.txt line 1561.
Unneeded space in "Hye-Shik Chan".

debian at debian:~/Documents/TXT$ cat -n python-2.7.2-docs-text/whatsnew/2.4.txt | grep Shik  | tail -1
  1561  article: Koray Can, Hye- Shik Chang, Michael Dyck, Raymond Hettinger,

* 3
2011.08.15 02:53 Moscow Time
WT..?    
File /whatsnew/2.6.txt line 8 

$ head  -12  2.6.txt

What's New in Python 2.7
************************

Author:
   A.M. Kuchling (amk at amk.ca)

Release:
   2.7.2

Date:
   July 31, 2011



-- 
Sergey
La Russie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: clear_docs.txt
Type: application/octet-stream
Size: 864 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20120210/89c08a44/attachment.obj>

From jim.kovacs at gmail.com  Sun Feb 12 04:44:08 2012
From: jim.kovacs at gmail.com (Jim Kovacs)
Date: Sat, 11 Feb 2012 19:44:08 -0800
Subject: [docs] Python v2.7.2 documentation > The Python Tutorial > 5.1 More
	on Lists
Message-ID: <CAJ=RWHN+fbiZNmj4ieOn4LnhP8T4CL3e+yr8TOfEh+dywYE3jw@mail.gmail.com>

Regarding the Python v2.7.2 documentation > The Python Tutorial > 5.1
More on Lists (
http://docs.python.org/tutorial/datastructures.html#more-on-lists ),
for list.sort() consider briefly mentioning that an "ordering
relation" must be defined.

E.g. this results in an error:

a = ['abc', 3.14159, complex(1,-1), 123]
print a.sort()

    print a.sort()
TypeError: no ordering relation is defined for complex numbers

From gustavo at gustavo.eng.br  Sun Feb 12 05:40:55 2012
From: gustavo at gustavo.eng.br (Gustavo Ambrozio)
Date: Sun, 12 Feb 2012 02:40:55 -0200
Subject: [docs] Python and doxygen
Message-ID: <CAB5XREf7ceZbxTqnc3U3QjFEZLmfu_Zywr-sA1MRghXOutxHmg@mail.gmail.com>

I'm new to Python and I have to resort to the documentation a lot.

And as an iOS developer I use an OSX app called Dash that is just wonderful
when it comes to searching for iOS documentation.

And there's a way to add more reference manuals into Dash using a doxygen
generated docset file. The author of Dash managed to generate docsets for
PHP, jquery and a few other languages but he told me it's hard for Python
because the only input format is HTML and it's not well structured for his
converter.

Since I want to have a pyhton docset to use in Dash I decided to reach out.
Is there any other file format that I can get python's documentation in?
Like XML? How are the HTML files generated?

Cheers,
Gustavo
--------------------------------------------------------------
Check out Snap!: http://snap.codecrop.com/
Snap turns your iPhone camera into a productivity tool.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120212/d4a33bcd/attachment.html>

From report at bugs.python.org  Sun Feb 12 09:17:48 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 12 Feb 2012 08:17:48 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329034668.75.0.784541863382.issue13997@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Feb 12 09:42:54 2012
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 12 Feb 2012 08:42:54 +0000
Subject: [docs] [issue4966] Improving Lib Doc Sequence Types Section
In-Reply-To: <1232149418.64.0.0450574767427.issue4966@psf.upfronthosting.co.za>
Message-ID: <1329036174.67.0.923124805625.issue4966@psf.upfronthosting.co.za>


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

Just noting that this has slipped a bit down my Python to-do list (there are other things I want to focus on before the first 3.3 alpha).

I'll get back to it at some point, but if someone want to take my branch and run with it in the meantime, please feel free.

----------
assignee: ncoghlan -> 

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

From report at bugs.python.org  Sun Feb 12 09:58:47 2012
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 12 Feb 2012 08:58:47 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329037127.54.0.928948885614.issue13997@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

> A common programming task is "I want to process this text file,
> I know it's in an ASCII compatible encoding, I don't know which
> one specifically, but I'm only manipulating the ASCII parts
> so it doesn't matter".

Can you give more detail about this use case? Why would you ignore non-ASCII characters?

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

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

From report at bugs.python.org  Sun Feb 12 10:19:38 2012
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 12 Feb 2012 09:19:38 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329038378.58.0.474374234993.issue13997@psf.upfronthosting.co.za>


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

Usually because the file may contain certain ASCII markers (or you're inserting such markers), but beyond that, you only care that it's in a consistent ASCII compatible encoding.

Parsing log files from sources that aren't set up correctly often falls into this category - you know the markers are ASCII, but the actual message contents may not be properly encoded. (e.g. they use a locale dependent encoding, but not all the log files are from the same machine and not all machines have their locale set up properly). (although errors="replace" can be a better option for such "read-only" use cases).

A use case where you really do need "errors='surrogateescape'" is when you're reformatting a log file and you want to preserve the encoding for the messages while manipulating the pure ASCII timestamps and message headers. In that case, surrogateescape is the right answer, because you can manipulate the ASCII bits freely while preserving the log message contents when you write the reformatted files back out. The reformatting script offers an API that says "put any ASCII compatible encoding in, and you'll get that same encoding back out".

You'll get weird behaviour (i.e. as you do in Python 2) if the assumption of an ASCII compatible encoding is ever violated, but that would be equally true if the script tried to process things at the raw bytes level.

The assumption of an ASCII compatibile text encoding is a useful one a lot of the time. The problem with Python 2 is it makes that assumption implicitly, and makes it almost impossible to disable it. Python 3, on the other hand, assumes very little by default (basically what it returns from sys.getfilesystemencoding() and locale.getpreferredencoding()), this requiring that the programmer know how to state their assumptions explicitly.

----------

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

From report at bugs.python.org  Sun Feb 12 10:55:49 2012
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 12 Feb 2012 09:55:49 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329038378.58.0.474374234993.issue13997@psf.upfronthosting.co.za>
Message-ID: <CAMpsgwaUJLrgJXj6nfkK=ajqx-8fLk2uRFLEZyFsjmXG+W1Pmw@mail.gmail.com>


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

Why do you use Unicode with the ugly surrogateescape error handler in
this case? Bytes are just fine for such usecase.

The surrogateescape error handler produces unusual characters in range
U+DC80-U+DCFF which cannot be printed to a console because sys.stdout
uses the strict error handler, and sys.stderr  uses the
backslashreplace error handler. If I remember correctly, only UTF-7
encoder allow lone surrogate characters.

----------

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

From sandro.tosi at gmail.com  Sun Feb 12 11:30:19 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sun, 12 Feb 2012 11:30:19 +0100
Subject: [docs] Python and doxygen
In-Reply-To: <CAB5XREf7ceZbxTqnc3U3QjFEZLmfu_Zywr-sA1MRghXOutxHmg@mail.gmail.com>
References: <CAB5XREf7ceZbxTqnc3U3QjFEZLmfu_Zywr-sA1MRghXOutxHmg@mail.gmail.com>
Message-ID: <CAPdtAj3wkFM+i8Gw7A5JviLNRVmSxs6NYQ5LUeeyXP50GfmVyw@mail.gmail.com>

Hello Gustavo,
thanks for contacting us!

On Sun, Feb 12, 2012 at 05:40, Gustavo Ambrozio <gustavo at gustavo.eng.br> wrote:
> Since I want to have a pyhton docset to use in Dash I decided to reach out.
> Is there any other file format that I can get python's documentation in?
> Like XML? How are the HTML files generated?

The python documentation (at least in its recent versions, f.e. from
2.6 onwards) it's generated from ReST files, that are later converted
to several output formats (HTML, PDF, TXT, and so on) by a wonderful
tool: sphinx.

So you can definetely use the ReST format: you can clone the CPython
mercurial repository and start playing with those files; you can refer
to:

* http://docs.python.org/devguide/#quick-start
* http://docs.python.org/devguide/docquality.html

for additional details, and in case of doubts, don't hesitate to ask
again on this list.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Sun Feb 12 11:37:04 2012
From: report at bugs.python.org (Nadeem Vawda)
Date: Sun, 12 Feb 2012 10:37:04 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329043024.24.0.591417272653.issue13997@psf.upfronthosting.co.za>


Changes by Nadeem Vawda <nadeem.vawda at gmail.com>:


----------
nosy: +nadeem.vawda

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

From report at bugs.python.org  Sun Feb 12 12:18:49 2012
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 12 Feb 2012 11:18:49 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329045529.5.0.619347316857.issue13997@psf.upfronthosting.co.za>


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

If such use cases are indeed better handled as bytes, then that's what should be documented. However, there are some text processing assumptions that no longer hold when using bytes instead of strings (such as "x[0:1] == x[0]"). You also can't safely pass such byte sequences to various other APIs (e.g. urllib.parse will happily process surrogate escaped text without corrupting them, but will throw UnicodeDecodeError for bytes sequences that aren't pure 7-bit ASCII).

Using surrogateescape instead means that you're only going to have problems if you go to encode the data to an encoding other than the source one. That's basically the things work in Python 2 with 8-bit strings.

----------

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

From report at bugs.python.org  Sun Feb 12 13:16:36 2012
From: report at bugs.python.org (Paul Moore)
Date: Sun, 12 Feb 2012 12:16:36 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329048996.28.0.292415350086.issue13997@psf.upfronthosting.co.za>


Paul Moore <p.f.moore at gmail.com> added the comment:

A better example in terms of "intended to be text" might be ChangeLog files. These are clearly text files, but of sufficiently standard format that they can be manipulated programmatically.

Consider a program to get a list of all authors who changed a particular file. Scan the file for date lines, then scan the block of text below for the filename you care about. Extract the author from the date line, put into a set, sort and print.

All of this can be done assuming the file is ASCII-compatible, but requires non-trivial text processing that would be a pain to do on bytes. But author names are quite likely to be non-ASCII, especially if it's an international project. And the changelog file is manually edited by people on different machines, so the possibility of inconsistent encodings is definitely there. (I have seen this happen - it's not theoretical!)

For my code, all I care about is that the names round-trip, so that I'm not damaging people's names any more than has already happened.

encoding="ascii",errors="surrogateescape" sounds like precisely the right answer here.

(If it's hard to find a good answer in Python 3, it's very easy to decide to use Python 2 which "just works", or even other tools like awk which also take Python 2's naive approach - and dismiss Python 3's Unicode model as "too hard").

My mental model here is text editors, which let you open any file, do their best to display as much as they can and allow you to manipulate it without damaging the bits you don't change. I don't see any reason why people shouldn't be able to write Python 3 code that way if they need to.

----------
nosy: +pmoore

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

From report at bugs.python.org  Sun Feb 12 14:00:19 2012
From: report at bugs.python.org (Florent Xicluna)
Date: Sun, 12 Feb 2012 13:00:19 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329051619.25.0.415362656921.issue13997@psf.upfronthosting.co.za>


Changes by Florent Xicluna <florent.xicluna at gmail.com>:


----------
nosy: +flox

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

From report at bugs.python.org  Sun Feb 12 15:53:12 2012
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 12 Feb 2012 14:53:12 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329048996.28.0.292415350086.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329058207.3456.2.camel@localhost.localdomain>


Antoine Pitrou <pitrou at free.fr> added the comment:

> My mental model here is text editors, which let you open any file, do
> their best to display as much as they can and allow you to manipulate
> it without damaging the bits you don't change. I don't see any reason
> why people shouldn't be able to write Python 3 code that way if they
> need to.

Some text editors try to guess the encoding, which is different from
"display invalid characters anyway".
Other text editors like gedit pop up an error when there are invalid
bytes according to the configured encoding.

That said, people *are* able to write Python 3 code the way you said.
They simply have to use the "surrogateescape" error handler.

----------

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

From sandro.tosi at gmail.com  Sun Feb 12 18:35:24 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sun, 12 Feb 2012 18:35:24 +0100
Subject: [docs] example in "18.1.11. email: Examples" lacks "Date" field
In-Reply-To: <F78763F6-C78F-4E82-B6C9-0CF0723AC7B5@buddyns.com>
References: <F78763F6-C78F-4E82-B6C9-0CF0723AC7B5@buddyns.com>
Message-ID: <CAPdtAj34vmddxiWWqenZU1_wtD_gd=KUYB6_U+9Wtv=sN54tDg@mail.gmail.com>

Hello Michele,
thanks for you email.

On Mon, Feb 6, 2012 at 18:46,  <support at buddyns.com> wrote:
> The examples in 18.1.11 about how to generate email objects produce
> emails lacking the "Date" field. This field is required by RFC2822:
> "The only required header fields are the origination date field and
> the originator address field(s)."

This is surely true, but the missing Date field is added automatically
by the MTA on localhost (which is what we are delegating to send our
email). I'm not sure it's needed to complicate adding also the Date
field, dunno what others think tho.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Sun Feb 12 18:39:27 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sun, 12 Feb 2012 18:39:27 +0100
Subject: [docs] InterfaceError: connection already closed
In-Reply-To: <2012020810180614094411@163.com>
References: <2012020810180614094411@163.com>
Message-ID: <CAPdtAj0STVvbbTFK6G4A3Eh905=rs2Agd3=GsDmk_Nm+yLUALA@mail.gmail.com>

Hello,

On Wed, Feb 8, 2012 at 03:18, zhu195781 <zhu195781 at 163.com> wrote:
> Hello,
> I have a question about celery,before my services operation?are normal,when
> I changed the PostgreSQL of a configuration restart service after.
> Although the celery service to run normally.Now?my celery running
> problem,the log file is always prompt
> "InterfaceError:?connection?already?closed" .
> I can not receive message .But I don't know how to solve it.Can you help me?

I'm sorry but this mailing list is about improving/fixing the CPython
documentation, so it's not the right place you are looking for. I
suggest to write on a celery support forum/mailing list or for a
general python questions audience on python list at
http://mail.python.org/mailman/listinfo/python-list

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Sun Feb 12 19:32:14 2012
From: report at bugs.python.org (Sandro Tosi)
Date: Sun, 12 Feb 2012 18:32:14 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1302623785.46.0.16009713021.issue11836@psf.upfronthosting.co.za>
Message-ID: <1329071534.26.0.192426320686.issue11836@psf.upfronthosting.co.za>


Sandro Tosi <sandro.tosi at gmail.com> added the comment:

Thanks Eli for the heads-up, I had missed Antoine's comment!

Antoine, I'm probably missing something, but SimpleQueue is present in 2.7 and 3.2 too, so why not mention it in the doc for those versions too?

----------

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

From report at bugs.python.org  Sun Feb 12 19:34:35 2012
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 12 Feb 2012 18:34:35 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1302623785.46.0.16009713021.issue11836@psf.upfronthosting.co.za>
Message-ID: <1329071675.29.0.806371403295.issue11836@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

> Antoine, I'm probably missing something, but SimpleQueue is present in 
> 2.7 and 3.2 too, so why not mention it in the doc for those versions too?

What I mean is that "multiprocessing.SimpleQueue" is a new API, so should be 3.3-only (while "multiprocessing.queues.SimpleQueue" already exists).

----------

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

From report at bugs.python.org  Sun Feb 12 19:46:04 2012
From: report at bugs.python.org (Sandro Tosi)
Date: Sun, 12 Feb 2012 18:46:04 +0000
Subject: [docs] [issue13999] Queue references in multiprocessing doc points
	to Queue	module and not to self
Message-ID: <1329072364.23.0.444581618774.issue13999@psf.upfronthosting.co.za>


New submission from Sandro Tosi <sandro.tosi at gmail.com>:

At the subject says, several references to Queue are linking to Queue module and not to multiprocessing.

----------
assignee: docs at python
components: Documentation
messages: 153218
nosy: docs at python, sandro.tosi
priority: normal
severity: normal
stage: needs patch
status: open
title: Queue references in multiprocessing doc points to Queue module and not to self
versions: Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Sun Feb 12 19:50:16 2012
From: report at bugs.python.org (Sandro Tosi)
Date: Sun, 12 Feb 2012 18:50:16 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1302623785.46.0.16009713021.issue11836@psf.upfronthosting.co.za>
Message-ID: <1329072616.54.0.862706873509.issue11836@psf.upfronthosting.co.za>


Sandro Tosi <sandro.tosi at gmail.com> added the comment:

It's the way all the subclasses are imported into the main module that got me in fault, I think. OK, so if I got it correctly, I should document multiprocessing.queue.SimpleQueue in 2.7 and 3.1 and multiprocessing.SimpleQueue in 3.3 also adding the hunk to __init__ (thus changing the API).

I'd say to document int still near to Queue() and JoinableQueue() - do you agree?

----------

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

From report at bugs.python.org  Sun Feb 12 19:59:42 2012
From: report at bugs.python.org (Antoine Pitrou)
Date: Sun, 12 Feb 2012 18:59:42 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1329072616.54.0.862706873509.issue11836@psf.upfronthosting.co.za>
Message-ID: <1329073001.3456.12.camel@localhost.localdomain>


Antoine Pitrou <pitrou at free.fr> added the comment:

> It's the way all the subclasses are imported into the main module that
> got me in fault, I think. OK, so if I got it correctly, I should
> document multiprocessing.queue.SimpleQueue in 2.7 and 3.1 and
> multiprocessing.SimpleQueue in 3.3 also adding the hunk to __init__
> (thus changing the API).

Yes.

> I'd say to document int still near to Queue() and JoinableQueue() - do
> you agree?

Yes, too.

----------

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

From report at bugs.python.org  Sun Feb 12 20:13:14 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 12 Feb 2012 19:13:14 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1302623785.46.0.16009713021.issue11836@psf.upfronthosting.co.za>
Message-ID: <1329073994.09.0.149243743007.issue11836@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

>> OK, so if I got it correctly, I should document multiprocessing.queue.SimpleQueue in 2.7 and 3.1 [...]

and 3.2, we're no longer updating 3.1 with such changes

----------

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

From report at bugs.python.org  Sun Feb 12 20:13:55 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 12 Feb 2012 19:13:55 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1302623785.46.0.16009713021.issue11836@psf.upfronthosting.co.za>
Message-ID: <1329074035.93.0.778183584317.issue11836@psf.upfronthosting.co.za>


Changes by Eli Bendersky <eliben at gmail.com>:


----------
Removed message: http://bugs.python.org/msg153224

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

From report at bugs.python.org  Sun Feb 12 20:14:24 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 12 Feb 2012 19:14:24 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1302623785.46.0.16009713021.issue11836@psf.upfronthosting.co.za>
Message-ID: <1329074064.63.0.977210290074.issue11836@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

> OK, so if I got it correctly, I should document multiprocessing.queue.SimpleQueue in 2.7 and 3.1 [...]


s/3.1/3.2/

----------

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

From report at bugs.python.org  Sun Feb 12 20:23:19 2012
From: report at bugs.python.org (Petri Lehtinen)
Date: Sun, 12 Feb 2012 19:23:19 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <1329074599.03.0.56858018181.issue13491@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

> > In the Doc/includes/sqlite3 directory there are still some scripts that require the
> > createdb.py, so I didn't nuke the file.
>
> Do these scripts (or a README file) explain about createdb.py?

No. There's no mention of createdb.py anywhere.

> > I also removed the strange "The arguments to :meth:`executescript` must be :func:`bytes`
> > objects" sentence from the patch. I assume it was a mistake, as it's wrong.
>
> Why not change it so that it?s correct?  (Maybe looking at the file history would
> show where the mistake comes from.)

It's just not in the history, it was only in OP's patch. And it's wrong, as executescript() takes an str argument, not bytes.

Having slept over this, I think execute_1.py and execute_2.py should be merged as one file, as after my patch, execute_2.py would not be runnable by itself.

This would also be a good chance to look at all the examples and have them cleaned up. That could also be a separate patch.

----------

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

From report at bugs.python.org  Sun Feb 12 20:53:45 2012
From: report at bugs.python.org (Sandro Tosi)
Date: Sun, 12 Feb 2012 19:53:45 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1329074064.63.0.977210290074.issue11836@psf.upfronthosting.co.za>
Message-ID: <CAPdtAj0f0ScG6o1x4FhDQc9tpdrurWTkBbKBavHXjW_zoLEnTg@mail.gmail.com>


Sandro Tosi <sandro.tosi at gmail.com> added the comment:

>> OK, so if I got it correctly, I should document multiprocessing.queue.SimpleQueue in 2.7 and 3.1 [...]
>
> s/3.1/3.2/

yeah, just a typo :)

----------

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

From report at bugs.python.org  Mon Feb 13 10:13:27 2012
From: report at bugs.python.org (Giampaolo Rodola')
Date: Mon, 13 Feb 2012 09:13:27 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329124407.92.0.564353046297.issue13997@psf.upfronthosting.co.za>


Changes by Giampaolo Rodola' <g.rodola at gmail.com>:


----------
nosy: +giampaolo.rodola

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

From report at bugs.python.org  Mon Feb 13 10:45:36 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Mon, 13 Feb 2012 09:45:36 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329126336.38.0.454593854085.issue13997@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/issue13997>
_______________________________________

From senthil at uthcode.com  Mon Feb 13 16:37:15 2012
From: senthil at uthcode.com (Senthil Kumaran)
Date: Mon, 13 Feb 2012 23:37:15 +0800
Subject: [docs] "copy" function links in shutil module docs point to
 wrong destination
In-Reply-To: <CAL6eQ-5L+BnKQXRj+=z787NVsoAhkM-qhWyHxg7jXNL1dOJcHg@mail.gmail.com>
References: <CAL6eQ-5L+BnKQXRj+=z787NVsoAhkM-qhWyHxg7jXNL1dOJcHg@mail.gmail.com>
Message-ID: <20120213153715.GA1916@mathmagic>

On Thu, Feb 09, 2012 at 08:58:47PM -0500, Deniz Turgut wrote:
> All the links for the "copy()" function in "shutil module" ( http://
> docs.python.org/library/shutil.html ) point to the "copy module" ( http://
> docs.python.org/library/copy.html#module-copy ) whereas they should point to

Yeah, those were indeed the case. I have just fixed those docs by
making them point explicitly to :func:`shutil.copy`.

Thanks,
Senthil

From senthil at uthcode.com  Mon Feb 13 16:55:48 2012
From: senthil at uthcode.com (Senthil Kumaran)
Date: Mon, 13 Feb 2012 23:55:48 +0800
Subject: [docs] strptime %m not fully specified
In-Reply-To: <CABvOPgTcu-zMgNbrkMNwyHng5o30QX=1K4fF1Y_NDV7FyB1Fwg@mail.gmail.com>
References: <CABvOPgTcu-zMgNbrkMNwyHng5o30QX=1K4fF1Y_NDV7FyB1Fwg@mail.gmail.com>
Message-ID: <20120213155548.GC1916@mathmagic>

On Tue, Feb 07, 2012 at 02:28:11PM -0800, G Lingle wrote:
> The entry for month is like:
> 
> %m       Month as a decimal number [01,12].
> 
> This indicates that strptime will parse 2-digit months and raise an exception
> if the month string isn't 2-digit. 

I think, only if there were an Exception while using one digit month, then a
mention of it would have helped as less-formal warning. Otherwise, I do not
think, there is need for a special mention. I think, it just that strftime
returns it in 2-digit that strptime mentioned that it takes input as 2-digit.

-- 
Senthil

From report at bugs.python.org  Mon Feb 13 18:17:31 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Mon, 13 Feb 2012 17:17:31 +0000
Subject: [docs] [issue4966] Improving Lib Doc Sequence Types Section
In-Reply-To: <1232149418.64.0.0450574767427.issue4966@psf.upfronthosting.co.za>
Message-ID: <1329153451.05.0.00392116419355.issue4966@psf.upfronthosting.co.za>


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


----------
keywords: +patch
Added file: http://bugs.python.org/file24511/0a49f6382467.diff

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

From report at bugs.python.org  Mon Feb 13 20:05:35 2012
From: report at bugs.python.org (=?utf-8?b?0KDQvtC80LDQvSDQlNC+0L3Rh9C10L3QutC+?=)
Date: Mon, 13 Feb 2012 19:05:35 +0000
Subject: [docs] [issue14003] __self__ on built-in functions is not as
	documented
Message-ID: <1329159935.3.0.264942191971.issue14003@psf.upfronthosting.co.za>


New submission from ????? ???????? <DXDragon at yandex.ru>:

The language reference says this in section 3.2:
 
~
Built-in functions
 
A built-in function object is a wrapper around a C function. Examples of built-in functions are len() and math.sin() <...> Special read-only attributes: <...> __self__ is set to None (but see the next item) <...>.
~

That is not the case:

ActivePython 3.2.2.3 (ActiveState Software Inc.) based on
Python 3.2.2 (default, Sep  8 2011, 10:55:13) [MSC v.1500 64 bit (AMD64)]  
on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> len.__self__
<module 'builtins' (built-in)>
>>> open.__self__
<module 'io' (built-in)>
>>> import math
>>> math.sin.__self__
<module 'math' (built-in)>

----------
assignee: docs at python
components: Documentation
messages: 153287
nosy: SpecLad, docs at python
priority: normal
severity: normal
status: open
title: __self__ on built-in functions is not as documented
type: behavior
versions: Python 3.2

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

From report at bugs.python.org  Mon Feb 13 20:20:27 2012
From: report at bugs.python.org (R. David Murray)
Date: Mon, 13 Feb 2012 19:20:27 +0000
Subject: [docs] [issue14003] __self__ on built-in functions is not as
	documented
In-Reply-To: <1329159935.3.0.264942191971.issue14003@psf.upfronthosting.co.za>
Message-ID: <1329160827.21.0.514734583338.issue14003@psf.upfronthosting.co.za>


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

It looks like this changed between 2.x and 3.x but the docs were not updated.  None makes more sense than the module as __self__, though, so perhaps it is actually a bug.  Then, again, since Python functions don't have a __self__, the __self__ of built-in functions seems like an anomaly to begin with...

----------
nosy: +r.david.murray
versions: +Python 3.3

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

From report at bugs.python.org  Mon Feb 13 21:39:55 2012
From: report at bugs.python.org (Michael Foord)
Date: Mon, 13 Feb 2012 20:39:55 +0000
Subject: [docs] [issue14003] __self__ on built-in functions is not as
	documented
In-Reply-To: <1329159935.3.0.264942191971.issue14003@psf.upfronthosting.co.za>
Message-ID: <1329165595.33.0.807482837612.issue14003@psf.upfronthosting.co.za>


Michael Foord <michael at voidspace.org.uk> added the comment:

It's nicer for introspection if __self__ is None on builtin functions. But fixing the docs is easier (and more backwards compatible).

----------
nosy: +michael.foord

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

From report at bugs.python.org  Tue Feb 14 01:10:09 2012
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 14 Feb 2012 00:10:09 +0000
Subject: [docs] [issue13951] 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: <1329178209.77.0.433619471916.issue13951@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at gmail.com> added the comment:

> Should it seg fault or just throw an exception?

Python cannot do anything useful on such fatal error. In Python 3.3, there is a faulthandler module which can help to debug: it dumps the traceback of all threads on such fatal error. It is also available as a third party module on PyPI:
http://pypi.python.org/pypi/faulthandler

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

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

From report at bugs.python.org  Tue Feb 14 01:23:27 2012
From: report at bugs.python.org (STINNER Victor)
Date: Tue, 14 Feb 2012 00:23:27 +0000
Subject: [docs] [issue13927] Extra spaces in the output of time.ctime
In-Reply-To: <1328215776.48.0.974828105123.issue13927@psf.upfronthosting.co.za>
Message-ID: <1329179007.15.0.720575652887.issue13927@psf.upfronthosting.co.za>


STINNER Victor <victor.stinner at gmail.com> added the comment:

> asctime() docs say it's a 24 char string.

I'm not sure that all platform conform to this "specification"... which is not future proof!

$ ./python 
Python 3.3.0a0 (default:af1a9508f7fa, Feb 14 2012, 01:18:15) 
[GCC 4.6.2 20111027 (Red Hat 4.6.2-1)] on linux
>>> import time
>>> time.ctime(2**38)
'Wed Jul 14 08:09:04 10680'
>>> len(time.ctime(2**38))
25

I suppose that you can say that the month day is formatted as 2 characters (padded with a space if needed).

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

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

From report at bugs.python.org  Tue Feb 14 01:25:57 2012
From: report at bugs.python.org (R. David Murray)
Date: Tue, 14 Feb 2012 00:25:57 +0000
Subject: [docs] [issue13927] Extra spaces in the output of time.ctime
In-Reply-To: <1328215776.48.0.974828105123.issue13927@psf.upfronthosting.co.za>
Message-ID: <1329179157.29.0.842349886477.issue13927@psf.upfronthosting.co.za>


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

Or you could give the strftime specification string that produces the equivalent output.

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

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

From report at bugs.python.org  Tue Feb 14 04:28:45 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Tue, 14 Feb 2012 03:28:45 +0000
Subject: [docs] [issue14006] Improve the documentation of
	xml.etree.ElementTree
Message-ID: <1329190125.69.0.69162565954.issue14006@psf.upfronthosting.co.za>


New submission from Eli Bendersky <eliben at gmail.com>:

The documentation of xml.etree.ElementTree has to be improved. The first, very obvious step, would be to start the documentation page with a general overview of the module + some simple examples. The current opening section makes no sense for this module.

----------
assignee: docs at python
components: Documentation
keywords: easy
messages: 153318
nosy: docs at python, eli.bendersky, eric.araujo, ezio.melotti, flox, scoder
priority: normal
severity: normal
status: open
title: Improve the documentation of xml.etree.ElementTree
type: enhancement
versions: Python 3.3

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

From report at bugs.python.org  Tue Feb 14 11:49:27 2012
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Tue, 14 Feb 2012 10:49:27 +0000
Subject: [docs] [issue14006] Improve the documentation of
	xml.etree.ElementTree
In-Reply-To: <1329190125.69.0.69162565954.issue14006@psf.upfronthosting.co.za>
Message-ID: <1329216567.31.0.861715688258.issue14006@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/issue14006>
_______________________________________

From report at bugs.python.org  Tue Feb 14 12:00:34 2012
From: report at bugs.python.org (Stefan Behnel)
Date: Tue, 14 Feb 2012 11:00:34 +0000
Subject: [docs] [issue14006] Improve the documentation of
	xml.etree.ElementTree
In-Reply-To: <1329190125.69.0.69162565954.issue14006@psf.upfronthosting.co.za>
Message-ID: <1329217234.18.0.582377834817.issue14006@psf.upfronthosting.co.za>


Stefan Behnel <scoder at users.sourceforge.net> added the comment:

Both lxml and ElementTree have tutorials:

http://effbot.org/zone/element.htm

http://lxml.de/tutorial.html

Here is another tutorial that may server as a source for an intro:

http://infohost.nmt.edu/tcc/help/pubs/pylxml/web/index.html

And the general ET documentation is here:

http://effbot.org/zone/element-index.htm#documentation

In terms of licensing, I can't speak for any of the other sources, but as for the lxml documentation, feel free to copy any ET related parts of it that you see fit.

I think the lxml tutorial is gentle enough even for beginners to follow. Note, however, that it uses lxml specific APIs in some places. In the specific case of XPath, the examples should be easily replaced with ElementPath, though.

----------

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

From report at bugs.python.org  Tue Feb 14 12:03:38 2012
From: report at bugs.python.org (Stefan Behnel)
Date: Tue, 14 Feb 2012 11:03:38 +0000
Subject: [docs] [issue14006] Improve the documentation of
	xml.etree.ElementTree
In-Reply-To: <1329190125.69.0.69162565954.issue14006@psf.upfronthosting.co.za>
Message-ID: <1329217418.32.0.312065385611.issue14006@psf.upfronthosting.co.za>


Stefan Behnel <scoder at users.sourceforge.net> added the comment:

Oh, and here are the ReST sources of the lxml docs:

https://github.com/lxml/lxml/tree/master/doc/

Specifically the tutorial:

https://raw.github.com/lxml/lxml/master/doc/tutorial.txt

and the parsing part:

https://raw.github.com/lxml/lxml/master/doc/parsing.txt

----------

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

From report at bugs.python.org  Tue Feb 14 16:26:43 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 14 Feb 2012 15:26:43 +0000
Subject: [docs] [issue14009] Clearer documentation for cElementTree
Message-ID: <1329233203.38.0.944311933185.issue14009@psf.upfronthosting.co.za>


New submission from ?ric Araujo <merwok at netwok.org>:

This patch should clarify how to use cElementTree usage, as well as improving indexing.

----------
assignee: docs at python
components: Documentation
messages: 153338
nosy: docs at python, eli.bendersky, eric.araujo
priority: normal
severity: normal
stage: commit review
status: open
title: Clearer documentation for cElementTree
versions: Python 2.7, Python 3.2

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

From report at bugs.python.org  Tue Feb 14 16:27:43 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 14 Feb 2012 15:27:43 +0000
Subject: [docs] [issue14009] Clearer documentation for cElementTree
In-Reply-To: <1329233203.38.0.944311933185.issue14009@psf.upfronthosting.co.za>
Message-ID: <1329233263.84.0.369687865547.issue14009@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
keywords: +patch
Added file: http://bugs.python.org/file24519/doc-cET.diff

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

From report at bugs.python.org  Tue Feb 14 16:41:19 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 14 Feb 2012 15:41:19 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <1329234079.29.0.25765177872.issue13491@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I think you can commit your patch, with our without merging execute_[12].py, as you think best.  Then you can do other patches (with or without pre-commit review) to fix or clean up the examples.

----------

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

From report at bugs.python.org  Tue Feb 14 17:27:27 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 14 Feb 2012 16:27:27 +0000
Subject: [docs] [issue14013] tarfile should expose supported formats
Message-ID: <1329236847.51.0.270430673151.issue14013@psf.upfronthosting.co.za>


New submission from ?ric Araujo <merwok at netwok.org>:

shutil contains high-level functions to create a zipfile or a tarball.  When a new format is added to the tarfile module, then shutil needs to be updated manually.  If tarfile exposed the names of the compressors it supports, then shutil could just automatically support everything that tarfile supports instead of having to re-do import dances for optional modules (bz2, lzma, zlib) and also duplicate formats in its doc.

This may also be useful for other code wanting to do some introspection.

Attached patch implements tarfile.formats, a list of strings (I thought about using a frozenset but then followed the precedent set by the 3.3 crypt module).  Tests and docs not updated, I wanted to get Lars? approval on the principle first.

One could argue that this is not needed: compression modules are not added often; updating shutil after updating tarfile is not hard; it is not that useful to have access to the list of supported formats.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 153350
nosy: docs at python, eric.araujo, lars.gustaebel, nadeem.vawda
priority: normal
severity: normal
stage: patch review
status: open
title: tarfile should expose supported formats
type: enhancement
versions: Python 3.3

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

From report at bugs.python.org  Tue Feb 14 17:29:16 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 14 Feb 2012 16:29:16 +0000
Subject: [docs] [issue14013] tarfile should expose supported formats
In-Reply-To: <1329236847.51.0.270430673151.issue14013@psf.upfronthosting.co.za>
Message-ID: <1329236956.48.0.866435335799.issue14013@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
keywords: +patch
Added file: http://bugs.python.org/file24521/add-tarfile.formats.diff

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

From report at bugs.python.org  Tue Feb 14 19:56:30 2012
From: report at bugs.python.org (Jim Jewett)
Date: Tue, 14 Feb 2012 18:56:30 +0000
Subject: [docs] [issue14015] surrogateescape largely missing from
	documentation
Message-ID: <1329245790.15.0.430373154575.issue14015@psf.upfronthosting.co.za>


New submission from Jim Jewett <jimjjewett at gmail.com>:

Recent discussion on the mailing lists and in http://bugs.python.org/issue13997 make it clear that the best way to get python2 results for "ASCII-in-the-parts-I-might-process-or-change" is to replace 

    f = open(fname)
with
    f = open(fname, encoding="ascii", errors="surrogateescape")

Unfortunately, surrogateescape (let alone this recipe) is not easily discoverable.  

http://docs.python.org/dev/library/functions.html#open lists 5 error-handlers -- but not this one.  It says that other error handlers are possible if they are registered with http://docs.python.org/dev/library/codecs.html#codecs.register_error but I haven't found a way to determine which error handlers are already registered.

The codecs.register (as opposed to register_error) documentation does list it as a possible value, but that is the only reference.

The other 5 error handlers are also available as module-level functions within the codecs module, and have their own documenation sections within http://docs.python.org/dev/library/codecs.html

Neither help(open) nor import codecs; help(codecs) provides any hints of the existence of surrogateescape.  Both explicitly suggest that it does not exist, by enumerating other values.

----------
assignee: docs at python
components: Documentation, Unicode
messages: 153359
nosy: Jim.Jewett, docs at python, ezio.melotti
priority: normal
severity: normal
status: open
title: surrogateescape largely missing from documentation
versions: Python 3.1, Python 3.2, Python 3.3

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

From report at bugs.python.org  Tue Feb 14 19:57:29 2012
From: report at bugs.python.org (Jim Jewett)
Date: Tue, 14 Feb 2012 18:57:29 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329245849.37.0.308576097241.issue13997@psf.upfronthosting.co.za>


Jim Jewett <jimjjewett at gmail.com> added the comment:

See bugs/python.org/issue14015 for one reason that surrogateescape isn't better known.

----------
nosy: +Jim.Jewett

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

From report at bugs.python.org  Tue Feb 14 20:46:50 2012
From: report at bugs.python.org (Gregory P. Smith)
Date: Tue, 14 Feb 2012 19:46:50 +0000
Subject: [docs] [issue9127] subprocess.Popen.communicate() and SIGCHLD
	handlers
In-Reply-To: <1277913297.34.0.963310724242.issue9127@psf.upfronthosting.co.za>
Message-ID: <1329248810.54.0.590134226675.issue9127@psf.upfronthosting.co.za>


Gregory P. Smith <greg at krypto.org> added the comment:

fixed via http://hg.python.org/cpython/rev/767420808a62

----------
dependencies: +race condition in subprocess module
nosy: +gregory.p.smith

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

From report at bugs.python.org  Wed Feb 15 00:27:26 2012
From: report at bugs.python.org (Chris Rebert)
Date: Tue, 14 Feb 2012 23:27:26 +0000
Subject: [docs] [issue14015] surrogateescape largely missing from
	documentation
In-Reply-To: <1329245790.15.0.430373154575.issue14015@psf.upfronthosting.co.za>
Message-ID: <1329262046.34.0.0722510822004.issue14015@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/issue14015>
_______________________________________

From report at bugs.python.org  Wed Feb 15 16:23:05 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 15 Feb 2012 15:23:05 +0000
Subject: [docs] [issue14015] surrogateescape largely missing from
	documentation
In-Reply-To: <1329245790.15.0.430373154575.issue14015@psf.upfronthosting.co.za>
Message-ID: <1329319385.21.0.43257322866.issue14015@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
versions:  -Python 3.1

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

From report at bugs.python.org  Wed Feb 15 18:32:39 2012
From: report at bugs.python.org (=?utf-8?b?0KDQvtC80LDQvSDQlNC+0L3Rh9C10L3QutC+?=)
Date: Wed, 15 Feb 2012 17:32:39 +0000
Subject: [docs] [issue14023] bytes implied to be mutable
Message-ID: <1329327159.64.0.799949559846.issue14023@psf.upfronthosting.co.za>


New submission from ????? ???????? <DXDragon at yandex.ru>:

The language reference in section 5.2.2 states:

~
With the exception of bytes literals, these all correspond to immutable data types, <...>
~

But bytes objects are immutable as well.

----------
assignee: docs at python
components: Documentation
messages: 153422
nosy: SpecLad, docs at python
priority: normal
severity: normal
status: open
title: bytes implied to be mutable
type: behavior
versions: Python 3.2

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

From report at bugs.python.org  Wed Feb 15 21:26:13 2012
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 15 Feb 2012 20:26:13 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <E1RxlQZ-0007K5-8C@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 9eb77d455be1 by Petri Lehtinen in branch '3.2':
Issue #13491: Fix many errors in sqlite3 documentation
http://hg.python.org/cpython/rev/9eb77d455be1

New changeset ba5b337ecc27 by Petri Lehtinen in branch 'default':
Merge branch '3.2'
http://hg.python.org/cpython/rev/ba5b337ecc27

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

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

From report at bugs.python.org  Wed Feb 15 21:28:11 2012
From: report at bugs.python.org (Petri Lehtinen)
Date: Wed, 15 Feb 2012 20:28:11 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <1329337690.98.0.059462272282.issue13491@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

?ric: You can make a patch for 2.7 if you want to, I left the issue open.

----------

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

From report at bugs.python.org  Wed Feb 15 23:32:03 2012
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 15 Feb 2012 22:32:03 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1302623785.46.0.16009713021.issue11836@psf.upfronthosting.co.za>
Message-ID: <E1RxnOL-0003B3-Hg@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 3b127a415643 by Sandro Tosi in branch '2.7':
Issue #11836: document multiprocessing.queues.SimpleQueue
http://hg.python.org/cpython/rev/3b127a415643

New changeset fe5eb6d35025 by Sandro Tosi in branch '3.2':
Issue #11836: document multiprocessing.queues.SimpleQueue
http://hg.python.org/cpython/rev/fe5eb6d35025

New changeset bf536b46d7f2 by Sandro Tosi in branch 'default':
Issue #11836: document and expose multiprocessing.SimpleQueue
http://hg.python.org/cpython/rev/bf536b46d7f2

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

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

From report at bugs.python.org  Wed Feb 15 23:33:47 2012
From: report at bugs.python.org (Sandro Tosi)
Date: Wed, 15 Feb 2012 22:33:47 +0000
Subject: [docs] [issue11836] multiprocessing.queues.SimpleQueue is
	undocumented
In-Reply-To: <1302623785.46.0.16009713021.issue11836@psf.upfronthosting.co.za>
Message-ID: <1329345226.93.0.57866452968.issue11836@psf.upfronthosting.co.za>


Sandro Tosi <sandro.tosi at gmail.com> added the comment:

Thanks for all you inputs!

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

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

From Christopher.Field at sigmaspace.com  Tue Feb 14 22:00:19 2012
From: Christopher.Field at sigmaspace.com (Christopher Field)
Date: Tue, 14 Feb 2012 21:00:19 +0000
Subject: [docs] Suggested (small) addition to python documentation
Message-ID: <C0BC4C6A-D5BE-497B-A5B4-439D1704287F@sigmaspace.com>

I was reading the python documentation (which is generally really great) about modules at
http://docs.python.org/tutorial/modules.html
and have a suggestion of a very small addition.
The last line of the second paragraph of section 6.1.3
just before "Some tips for experts:"
says
"The contents of the spam.pyc file are platform independent, so a Python module directory can be shared by machines of different architectures."

This may be true, but when I tried to distribute my python code as .pyc I was surprised by the fact that they are not independent of the python run system version. So I suggesting one of the following two changes to the line.

"The contents of the spam.pyc file are platform independent (but not version independent), so a Python module directory can be shared by machines of different architectures."
or
"The contents of the spam.pyc file are platform independent, so a Python module directory can be shared by machines of different architectures, as long as they same Python version is used."

Great product. Keep up the good work.
Christopher Field

Sigma Space
4600 Forbes Blvd
Lanham, MD 20706

301-552-6000 (main)
301-552-6057 (direct)
301-552-6411 Fax



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

From mbillerwell at gmail.com  Mon Feb 13 08:03:15 2012
From: mbillerwell at gmail.com (Markus Billerwell)
Date: Mon, 13 Feb 2012 18:03:15 +1100
Subject: [docs] smtplib minor change
Message-ID: <CAORfpewCDgauM_xh8JQVHTfa2Fi3Jkq6J5Gs5qNDHOJ-0PVcsA@mail.gmail.com>

Hi,

In a future version of smtplib, could you please change all the
commands to uppercase as per RFC821?

Leading email clients such as Thunderbird and Outlook send their SMTP
commands in this way and I believe it would be helpful and beneficial
to follow the suggested method as shown in RFC821.

Thank you and regards,

Markus

From palehose at gmail.com  Tue Feb 14 06:27:44 2012
From: palehose at gmail.com (Erik Johnson)
Date: Mon, 13 Feb 2012 23:27:44 -0600
Subject: [docs] Documentation bug for datetime.time()
Message-ID: <20120214052744.GA5083@gmail.com>

http://docs.python.org/library/datetime.html?highlight=datetime#datetime.datetime.time

The word "time" in this function links to the documentation for the
"time" module (http://docs.python.org/library/time.html#module-time). It
should link to the following URL:

http://docs.python.org/library/datetime.html?highlight=datetime#time-objects


-- 

-Erik

"For me, it is far better to grasp the universe as it really is than to
persist in delusion, however satisfying and reassuring."  --Carl Sagan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20120213/8d476458/attachment.pgp>

From support at buddyns.com  Sun Feb 12 19:01:19 2012
From: support at buddyns.com (support at buddyns.com)
Date: Sun, 12 Feb 2012 19:01:19 +0100
Subject: [docs] example in "18.1.11. email: Examples" lacks "Date" field
In-Reply-To: <CAPdtAj34vmddxiWWqenZU1_wtD_gd=KUYB6_U+9Wtv=sN54tDg@mail.gmail.com>
References: <F78763F6-C78F-4E82-B6C9-0CF0723AC7B5@buddyns.com>
	<CAPdtAj34vmddxiWWqenZU1_wtD_gd=KUYB6_U+9Wtv=sN54tDg@mail.gmail.com>
Message-ID: <7A266C51-341A-422E-A6C2-72D7287E6300@buddyns.com>

Hey Sandro!

Thanks for looking into this.

> but the missing Date field is added automatically
> by the MTA on localhost (which is what we are delegating to send our
> email). I'm not sure it's needed to complicate adding also the Date
> field, dunno what others think tho.

Interesting! This appears to be an implementation-dependent behavior
at the MTA, as qmail and postfix do not fill out required fields for you.
When sending through either, the email arrives at the recipient as sent.

Also, this behavior seems to be borderline with RFC5322:
"[The origination date field] is specifically not intended to convey the
   time that the message is actually transported, but rather the time at
   which the human or other creator of the message has put the message
   into its final form, ready for transport"

In any case, given the purpose of the example, I think showing how to
add the Date field is a good thing.

Again, just my 2 cents.

cheers
michele
The BuddyNS team

--
Follow the status of BuddyNS @ http://twitter.com/BuddyNS

From terra.xemnas at gmail.com  Wed Feb 15 17:10:37 2012
From: terra.xemnas at gmail.com (Daniel Gibson)
Date: Wed, 15 Feb 2012 10:10:37 -0600
Subject: [docs] Broken Link
Message-ID: <CA+qzbTQDUqeRjGAbPm5FGs5kfHbRj_v0rN8Wm8S-eJC94a04pw@mail.gmail.com>

http://wiki.python.org/moin/UsingPickle The UsingPickle page on the
Python.org wiki has a broken link at the top, "Official Pickle Use
Documentation."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120215/bb16b09c/attachment.html>

From sandro.tosi at gmail.com  Wed Feb 15 23:46:34 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Wed, 15 Feb 2012 23:46:34 +0100
Subject: [docs] Broken Link
In-Reply-To: <CA+qzbTQDUqeRjGAbPm5FGs5kfHbRj_v0rN8Wm8S-eJC94a04pw@mail.gmail.com>
References: <CA+qzbTQDUqeRjGAbPm5FGs5kfHbRj_v0rN8Wm8S-eJC94a04pw@mail.gmail.com>
Message-ID: <CAPdtAj0aCKzWSaQ2ApDCmucCCUoaxcDWqQKi8_TjwOOuTKUCbg@mail.gmail.com>

Hello Daniel,
Thanks for your interest in the Python documentation

On Wed, Feb 15, 2012 at 17:10, Daniel Gibson <terra.xemnas at gmail.com> wrote:
> http://wiki.python.org/moin/UsingPickle The UsingPickle page on the
> Python.org wiki has a broken link at the top, "Official Pickle Use
> Documentation."

It's a wiki, anyone could edit it: would you like to do it?

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Thu Feb 16 04:48:45 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 16 Feb 2012 03:48:45 +0000
Subject: [docs] [issue14009] Clearer documentation for cElementTree
In-Reply-To: <1329233203.38.0.944311933185.issue14009@psf.upfronthosting.co.za>
Message-ID: <1329364125.78.0.0202965508128.issue14009@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

?ric, indeed it clarifies the usage, but my concern is that it also moves the first mention of the module further down.

There's no real reason for someone using CPython 2.7 or 3.2 *not* to use cET. So, some mention should appear in the opening paragraph. I'm attaching a patch that shows one possibility (based on your patch). It was generated vs. branch 2.7

----------
Added file: http://bugs.python.org/file24527/issue14009.doc_cET.1.patch

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

From report at bugs.python.org  Thu Feb 16 04:50:45 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 16 Feb 2012 03:50:45 +0000
Subject: [docs] [issue14009] Clearer documentation for cElementTree
In-Reply-To: <1329233203.38.0.944311933185.issue14009@psf.upfronthosting.co.za>
Message-ID: <1329364245.69.0.475170897754.issue14009@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

Also, I must add that I absolutely hate the opening paragraph of the documentation in this module. Once 14006 is implemented, parts of it should be backported to 2.7 and 3.2

That would be an orthogonal change to what we're discussion here, though

----------

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

From report at bugs.python.org  Thu Feb 16 04:54:03 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 16 Feb 2012 03:54:03 +0000
Subject: [docs] [issue14023] bytes implied to be mutable
In-Reply-To: <1329327159.64.0.799949559846.issue14023@psf.upfronthosting.co.za>
Message-ID: <1329364443.61.0.311467017539.issue14023@psf.upfronthosting.co.za>


Changes by Eli Bendersky <eliben at gmail.com>:


----------
nosy: +eli.bendersky

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

From report at bugs.python.org  Thu Feb 16 04:55:37 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 16 Feb 2012 03:55:37 +0000
Subject: [docs] [issue14009] Clearer documentation for cElementTree
In-Reply-To: <1329233203.38.0.944311933185.issue14009@psf.upfronthosting.co.za>
Message-ID: <1329364537.38.0.818056601433.issue14009@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

+1.  Barring other feedback, I will commit your patch.

> Also, I must add that I absolutely hate the opening paragraph of the
> documentation in this module.

This:

  The :class:`Element` type is a flexible container object, designed to store
  hierarchical data structures in memory.  The type can be described as a cross
  between a list and a dictionary.

?  Yeah, it?s not quite good.

----------

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

From report at bugs.python.org  Thu Feb 16 04:59:53 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Thu, 16 Feb 2012 03:59:53 +0000
Subject: [docs] [issue14009] Clearer documentation for cElementTree
In-Reply-To: <1329233203.38.0.944311933185.issue14009@psf.upfronthosting.co.za>
Message-ID: <1329364793.52.0.461004966296.issue14009@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

If you want to collect additional feedback, you may want to add some other people to the Nosy list :-) Alternatively, since it's a small doc change you can just commit it and it can be fixed later if someone strongly objects.

>>>
This:

  The :class:`Element` type is a flexible container object, designed to store
  hierarchical data structures in memory.  The type can be described as a cross
  between a list and a dictionary.

?  Yeah, it?s not quite good.
>>>

Yes. You read the first section of a module's doc and you have *no idea* what the module is and how to use it. I plant to work on this for 3.3 in the context of issue 14006.

----------

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

From report at bugs.python.org  Thu Feb 16 19:34:22 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Thu, 16 Feb 2012 18:34:22 +0000
Subject: [docs] [issue14034] the example in argparse doc is too complex
Message-ID: <1329417262.26.0.419020263055.issue14034@psf.upfronthosting.co.za>


New submission from Tshepang Lekhonkhobe <tshepang at gmail.com>:

The argparse example (http://docs.python.org/dev/library/argparse.html#example) introduces way too many concepts too early. It's written as if targeted to existing users of optparse, instead of newcomers to Python's CLI handling.

Perhaps the example could be more gentle, or if there is insistence on showing off, maybe the page could be kept as-is, but with a link to some tutorial (as is done with logging: http://docs.python.org/dev/library/logging.html).

----------
assignee: docs at python
components: Documentation
messages: 153491
nosy: docs at python, tshepang
priority: normal
severity: normal
status: open
title: the example in argparse doc is too complex
type: enhancement
versions: Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Thu Feb 16 20:47:35 2012
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 16 Feb 2012 19:47:35 +0000
Subject: [docs] [issue13995] sqlite3 Cursor.rowcount documentation for old
	sqlite bug
In-Reply-To: <1328991377.3.0.315009784222.issue13995@psf.upfronthosting.co.za>
Message-ID: <E1Ry7Ih-0002oV-2o@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 74b2da95c6be by Petri Lehtinen in branch '3.2':
sqlite3: Fix documentation errors concerning Cursor.rowcount
http://hg.python.org/cpython/rev/74b2da95c6be

New changeset a1f17e108a1b by Petri Lehtinen in branch '2.7':
Fix errors in sqlite3's Cursor.rowcount documentation
http://hg.python.org/cpython/rev/a1f17e108a1b

New changeset 08699214f79b by Petri Lehtinen in branch 'default':
Merge branch '3.2'
http://hg.python.org/cpython/rev/08699214f79b

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

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

From report at bugs.python.org  Thu Feb 16 20:48:06 2012
From: report at bugs.python.org (Petri Lehtinen)
Date: Thu, 16 Feb 2012 19:48:06 +0000
Subject: [docs] [issue13995] sqlite3 Cursor.rowcount documentation for old
	sqlite bug
In-Reply-To: <1328991377.3.0.315009784222.issue13995@psf.upfronthosting.co.za>
Message-ID: <1329421685.93.0.688454241519.issue13995@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

Fixed, thanks!

----------
nosy: +petri.lehtinen
versions: +Python 2.7, Python 3.2, Python 3.3

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

From sandro.tosi at gmail.com  Thu Feb 16 22:25:26 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Thu, 16 Feb 2012 22:25:26 +0100
Subject: [docs] Broken Link
In-Reply-To: <CA+qzbTTMr-kY42BoMTUQE5BpiJW=nxpYDn72-Hzupdu3k199dg@mail.gmail.com>
References: <CA+qzbTQDUqeRjGAbPm5FGs5kfHbRj_v0rN8Wm8S-eJC94a04pw@mail.gmail.com>
	<CAPdtAj0aCKzWSaQ2ApDCmucCCUoaxcDWqQKi8_TjwOOuTKUCbg@mail.gmail.com>
	<CA+qzbTTMr-kY42BoMTUQE5BpiJW=nxpYDn72-Hzupdu3k199dg@mail.gmail.com>
Message-ID: <CAPdtAj3tXhF-Voiz8xegEiqJKRL7j6s6XxEj5MXm-JDSL6tWzQ@mail.gmail.com>

Hi Daniel,

On Thu, Feb 16, 2012 at 00:05, Daniel Gibson <terra.xemnas at gmail.com> wrote:
> I would like to correct the link (I just made an account!),

that's awesome!

> but I am not
> exactly sure where the "Official Pickle Use Documentation" is supposed to
> link. The links below it already connect the reader to the official
> documentation page for pickle. I may as well just omit the first link, yes?

i've checked on the waybackmachine.org[1] what node64 was and it
pointed to pickle "Data stream format" which now points to [2]

[1] http://web.archive.org/web/20060818224837/http://docs.python.org/lib/node64.html
[2] http://docs.python.org/library/pickle.html#data-stream-format

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From paul at giannaros.org  Thu Feb 16 13:12:49 2012
From: paul at giannaros.org (Paul A. Giannaros)
Date: Thu, 16 Feb 2012 12:12:49 +0000
Subject: [docs] compileall module: exclusion example is path
	separator-specific
Message-ID: <CAEq8tJSfeR1WjJO-LPGCYsK3tp=B9v=XkiSXVHB1Cg3-p4k3vw@mail.gmail.com>

Hi,



The docs for compileall give an example of compiling pyc files in a
directory while excluding '.svn' subdirectories:

compileall.compile_dir('Lib/', rx=re.compile('/[.]svn'), force=True)

Neither this part nor documentation for the 'rx' attribute make clear that
the paths searched with the regular expression will have OS specific
separators. This example doesn't work on Windows, for example. I think the
example should be explicit that the paths will contain the native
separators (or it should use pathsep instead of '/', or maybe '[/\\]', to
make it clearer in the example).


Thanks,

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

From report at bugs.python.org  Fri Feb 17 17:06:32 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 17 Feb 2012 16:06:32 +0000
Subject: [docs] [issue14009] Clearer documentation for cElementTree
In-Reply-To: <1329233203.38.0.944311933185.issue14009@psf.upfronthosting.co.za>
Message-ID: <1329494792.81.0.249946872868.issue14009@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> If you want to collect additional feedback, you may want to add some other
> people to the Nosy list :-)
I did not want more feedback, I wanted to leave time for interested parties to find this bug for themselves and eventually comment :)

One question: when I merge the new doc from 3.2 to 3.3, do I remove the new section, as the cET module is now deprecated?  If I do that we?d lose the indexing (i.e. without a module directive there will be no entry in the module index not the alphabetical index).  I could leave the cET section so that we get the indexing but change the text to ?Deprecated alias of ET.?

----------

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

From report at bugs.python.org  Fri Feb 17 17:34:17 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 17 Feb 2012 16:34:17 +0000
Subject: [docs] [issue13995] sqlite3 Cursor.rowcount documentation for old
	sqlite bug
In-Reply-To: <1328991377.3.0.315009784222.issue13995@psf.upfronthosting.co.za>
Message-ID: <1329496457.84.0.58728484163.issue13995@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> With SQLite versions before 3.6.5, :attr:`rowcount` is set to 0 if
> you make a ``DELETE FROM table`` without any condition.

Is there a fixed version of SQLite used by each Python version?  If yes, then I think it could be more useful to talk about the Python version in that paragraph.

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

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

From report at bugs.python.org  Fri Feb 17 18:03:56 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 17 Feb 2012 17:03:56 +0000
Subject: [docs] [issue14034] the example in argparse doc is too complex
In-Reply-To: <1329417262.26.0.419020263055.issue14034@psf.upfronthosting.co.za>
Message-ID: <1329498236.92.0.161779539641.issue14034@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I really don?t think there was any willingness to ?show off?, and wouldn?t be surprised if the doc was written optparse users.  It?s just an accident of history, and we can try to make it better instead of calling people names :)

Do you have a wording idea for a gentler introduction?

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

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

From report at bugs.python.org  Fri Feb 17 18:36:05 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Fri, 17 Feb 2012 17:36:05 +0000
Subject: [docs] [issue14034] the example in argparse doc is too complex
In-Reply-To: <1329498236.92.0.161779539641.issue14034@psf.upfronthosting.co.za>
Message-ID: <CAA77j2CzxqMPTff+LqT5FcaHfyZ6kYb2TRyMcRgJKxk4QMLw7Q@mail.gmail.com>


Tshepang Lekhonkhobe <tshepang at gmail.com> added the comment:

On Fri, Feb 17, 2012 at 19:03, ?ric Araujo <report at bugs.python.org> wrote:
>
> ?ric Araujo <merwok at netwok.org> added the comment:
>
> I really don?t think there was any willingness to ?show off?, and wouldn?t be surprised if the doc was written optparse users. ?It?s just an accident of history, and we can try to make it better instead of calling people names :)

I did not mean to sound rude. Forgive me.

> Do you have a wording idea for a gentler introduction?

I will work on something.

----------

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

From report at bugs.python.org  Fri Feb 17 19:37:30 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Fri, 17 Feb 2012 18:37:30 +0000
Subject: [docs] [issue14009] Clearer documentation for cElementTree
In-Reply-To: <1329494792.81.0.249946872868.issue14009@psf.upfronthosting.co.za>
Message-ID: <CAF-Rda-ihyxXVtSf0v5MPtYOPNLYwVOFBqANcED8cjeGYnyYPA@mail.gmail.com>


Eli Bendersky <eliben at gmail.com> added the comment:

> > If you want to collect additional feedback, you may want to add some
> other
> > people to the Nosy list :-)
> I did not want more feedback, I wanted to leave time for interested
> parties to find this bug for themselves and eventually comment :)
>
> One question: when I merge the new doc from 3.2 to 3.3, do I remove the
> new section, as the cET module is now deprecated?  If I do that we?d lose
> the indexing (i.e. without a module directive there will be no entry in the
> module index not the alphabetical index).  I could leave the cET section so
> that we get the indexing but change the text to ?Deprecated alias of ET.?
>

I don't see a need for cElementTree to be indexed in the doc of 3.3
Assuming a new Python user who starts with 3.3, he should not even know
about the existence of cElementTree (bar a small notice that says it's
deprecated, which will be of no interest to him). The cElementTree module
stays in its place in 3.3, but that's only for backwards compatibility.
Officially, it doesn't exist :)

----------

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

From report at bugs.python.org  Fri Feb 17 20:12:31 2012
From: report at bugs.python.org (Petri Lehtinen)
Date: Fri, 17 Feb 2012 19:12:31 +0000
Subject: [docs] [issue13995] sqlite3 Cursor.rowcount documentation for old
	sqlite bug
In-Reply-To: <1329496457.84.0.58728484163.issue13995@psf.upfronthosting.co.za>
Message-ID: <20120217191227.GA2029@ihaa>


Petri Lehtinen <petri at digip.org> added the comment:

?ric Araujo wrote:
> Is there a fixed version of SQLite used by each Python version? If
> yes, then I think it could be more useful to talk about the Python
> version in that paragraph.

No. In each Python version, setup.py only checks that SQLite is 3.0.8
or newer.

----------

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

From report at bugs.python.org  Fri Feb 17 21:50:32 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 17 Feb 2012 20:50:32 +0000
Subject: [docs] [issue14009] Clearer documentation for cElementTree
In-Reply-To: <1329233203.38.0.944311933185.issue14009@psf.upfronthosting.co.za>
Message-ID: <1329511832.34.0.982630162122.issue14009@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

> Officially, it doesn't exist :)

Keep in mind that many users will find about it from the Internet, and it's better to clearly say what it is and that it shouldn't be used anymore than pretending it doesn't exist.  (AFAIU this is the current situation, since there is a warning, but leaving it indexed wouldn't hurt IMHO.)

----------
nosy: +ezio.melotti

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

From report at bugs.python.org  Fri Feb 17 22:02:34 2012
From: report at bugs.python.org (Fred L. Drake, Jr.)
Date: Fri, 17 Feb 2012 21:02:34 +0000
Subject: [docs] [issue14009] Clearer documentation for cElementTree
In-Reply-To: <1329511832.34.0.982630162122.issue14009@psf.upfronthosting.co.za>
Message-ID: <CAFT4OTE1eQQKEbqqR1UmaU_CMML-dXjfeWjb2tQXZTb9uisG5g@mail.gmail.com>


Fred L. Drake, Jr. <fred at fdrake.net> added the comment:

Developers with existing code can reasonably be expected to look it up
based on what they're currently importing, so an entry that points to
the new recommended practice is good.

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

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

From lianliankan2010 at gmail.com  Fri Feb 17 15:24:35 2012
From: lianliankan2010 at gmail.com (kan lianlian)
Date: Fri, 17 Feb 2012 22:24:35 +0800
Subject: [docs] Fix a documentation bug in python v3.2.2 documentation
Message-ID: <CAGc_ELPbFbSe+VuvFXs3t6PT8pRvPjuUpBjDnEOt6v6BM+QdyQ@mail.gmail.com>

There is an example about memoryview objects in section 4.9:
==========================================
>>> data = bytearray(b'abcefg')
>>> v = memoryview(data)
>>> v.readonly
False
>>> v[0] = b'z'
>>> data
bytearray(b'zbcefg')
>>> v[1:4] = b'123'
>>> data
bytearray(b'a123fg')                       ### This line is wrong.
>>> v[2] = b'spam'
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: cannot modify size of memoryview object
==========================================

After v[0] = b'z' and  v[1:4] = b'123', data should be bytearray(b'z123efg'),
but not bytearray(b'a123fg'). That's it.


INT3/uiq8
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120217/83a84647/attachment.html>

From report at bugs.python.org  Fri Feb 17 23:25:27 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 17 Feb 2012 22:25:27 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329517527.26.0.827944331099.issue13997@psf.upfronthosting.co.za>


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

I agree with no new builtin and appreciate that being taken off the table.

I think the place is the Unicode How-to. I think that document should be renamed Encodings and Unicode How-to. The reasons are 1) one has to first understand the concept of encoding characters and text as numbers, and 2) this issue (and the python-ideas discussion) is not about Unicode, but about using pre- (and non-)Unicode encodings with Python3's bytes and string types, and how that differs in Python3 versus using Python2's unicode and string types. If only Unicode encodings were used, with utf-8 dominant on the Internet (and it is now most common for web pages), the problems of concern here would not exist.

Learning about Unicode would mean learning about code units versus codepoints, normal versus surrogate chars, BMP versus extended chars (all of which are non-issues in wide builds and Py 3.3), 256-char planes, BOMs, surrogates, normalization forms, and character properties. While sometimes useful, these subjects are not the issue here.

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

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

From report at bugs.python.org  Sat Feb 18 00:02:55 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 17 Feb 2012 23:02:55 +0000
Subject: [docs] [issue14003] __self__ on built-in functions is not as
	documented
In-Reply-To: <1329159935.3.0.264942191971.issue14003@psf.upfronthosting.co.za>
Message-ID: <1329519775.91.0.999301311537.issue14003@psf.upfronthosting.co.za>


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

Python-coded functions do not have .__self__.
>>> def f(): pass

>>> f.__self__
...
AttributeError: 'function' object has no attribute '__self__'

Unbound builtin methods, which are simply builtins functions attached to a class, do not have .__self__
>>> list.__len__.__self__
...
AttributeError: 'wrapper_descriptor' object has no attribute '__self__'

So it makes no sense to me that builtin non-method functions should have this attribute.

"Built-in methods 
This is really a different disguise of a built-in function, this time containing an object passed to the C function as an implicit extra argument. An example of a built-in method is alist.append(), assuming alist is a list object. In this case, the special read-only attribute __self__ is set to the object denoted by alist."

should have 'method' replaced with 'instance method' as it is only talking about instance methods, as the term is used in the rest of the section. Or this section should be deleted as it duplicates the previous Instance Method section. Or it should be revised to actually discuss unbound builtin methods.

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

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

From report at bugs.python.org  Sat Feb 18 01:19:12 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 18 Feb 2012 00:19:12 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329524352.54.0.762904442945.issue13997@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

FWIW I recently made a talk at PyCon Finland called "Understanding Encodings" that goes through the things you mentioned in the last message.

I could turn that in a patch for the Unicode Howto.

----------

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

From report at bugs.python.org  Sat Feb 18 01:59:15 2012
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 18 Feb 2012 00:59:15 +0000
Subject: [docs] [issue14023] bytes implied to be mutable
In-Reply-To: <1329327159.64.0.799949559846.issue14023@psf.upfronthosting.co.za>
Message-ID: <E1RyYdu-0002gM-9o@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 88522997b021 by Terry Jan Reedy in branch '3.2':
Issue 14023 Revert edit to 2.7 version. (I suspect edit is from when we thought
http://hg.python.org/cpython/rev/88522997b021

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

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

From report at bugs.python.org  Sat Feb 18 02:00:58 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 18 Feb 2012 01:00:58 +0000
Subject: [docs] [issue14023] bytes implied to be mutable
In-Reply-To: <1329327159.64.0.799949559846.issue14023@psf.upfronthosting.co.za>
Message-ID: <1329526858.43.0.245840232111.issue14023@psf.upfronthosting.co.za>


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

applied to 3.3 also

----------
assignee: docs at python -> terry.reedy
nosy: +terry.reedy
resolution:  -> fixed
status: open -> closed
versions: +Python 3.3

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

From report at bugs.python.org  Sat Feb 18 02:07:32 2012
From: report at bugs.python.org (Matt Joiner)
Date: Sat, 18 Feb 2012 01:07:32 +0000
Subject: [docs] [issue14003] __self__ on built-in functions is not as
	documented
In-Reply-To: <1329159935.3.0.264942191971.issue14003@psf.upfronthosting.co.za>
Message-ID: <1329527252.85.0.271264936892.issue14003@psf.upfronthosting.co.za>


Changes by Matt Joiner <anacrolix at gmail.com>:


----------
nosy: +anacrolix

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

From report at bugs.python.org  Sat Feb 18 02:11:07 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 18 Feb 2012 01:11:07 +0000
Subject: [docs] [issue13999] Queue references in multiprocessing doc points
	to Queue	module and not to self
In-Reply-To: <1329072364.23.0.444581618774.issue13999@psf.upfronthosting.co.za>
Message-ID: <1329527467.35.0.990784621304.issue13999@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

:class:`~multiprocessing.Queue` should probably be used.

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

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

From report at bugs.python.org  Sat Feb 18 02:22:22 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 18 Feb 2012 01:22:22 +0000
Subject: [docs] [issue14003] __self__ on built-in functions is not as
	documented
In-Reply-To: <1329159935.3.0.264942191971.issue14003@psf.upfronthosting.co.za>
Message-ID: <1329528142.01.0.300393335617.issue14003@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I think that functions in C modules are implemented as methods of module objects, which would explain why len.__self__ is builtins.

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

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

From report at bugs.python.org  Sat Feb 18 02:33:14 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 18 Feb 2012 01:33:14 +0000
Subject: [docs] [issue14042] json.dumps() documentation is slightly
	incorrect.
In-Reply-To: <1329494870.59.0.571991231564.issue14042@psf.upfronthosting.co.za>
Message-ID: <1329528794.54.0.924203513739.issue14042@psf.upfronthosting.co.za>


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

Entry for dump says
"If ensure_ascii is False (default: True), then some chunks written to fp may be unicode instances,"
Entry for dumps says
"If ensure_ascii is False, then the return value will be a unicode instance."
Entry for JSONEncoder says
"If ensure_ascii is True (the default), the output is guaranteed to be str objects with all incoming unicode characters escaped. If ensure_ascii is False, the output will be a unicode object."

I suspect the latter two meant to say something like
"If ensure_ascii is False and any chunk would be unicode, then the whole output is unicode."

And should 'all incoming unicode characters' either be or include 'all non-ascii chars (as in 3.x)?

---
In 3.x, ensure_ascii apparently has a different meaning.
"If ensure_ascii is True (the default), the output is guaranteed to have all incoming non-ASCII characters escaped. If ensure_ascii is False, these characters will be output as-is."

Unlike other params used in multiple json functions, ensure_ascii is only defined once, under json.JSONEncoder and not under dump and dumps. Should the JSONEncoder entry to copied to dump and dumps?

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python, ezio.melotti, rhettinger, terry.reedy
stage:  -> needs patch
versions: +Python 3.2, Python 3.3 -Python 2.6

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

From zearin at gonk.net  Sat Feb 18 01:16:31 2012
From: zearin at gonk.net (Zearin)
Date: Fri, 17 Feb 2012 19:16:31 -0500
Subject: [docs] Diagrams Wanted
Message-ID: <CDD7F200-5B2B-480A-AADA-E541A65894B6@gonk.net>

I think the Python documentation is among some of the best open source documentation out there.  It?s very well-written, well-organized, and pretty damn thorough.  

But I have one problem: I?m a visual thinker?and there are no diagrams. ?  

Diagrams are valuable.  They can convey information at glance that would otherwise take paragraphs.  And let me assure you, I *do* appreciate the written word?quite a bit, in fact.  I enjoy writing, and I enjoy improving existing writing.  But the main documentation already has solid writing.  And although I?ve learned much from it, diagrams would help solidifying some concepts into memory ten times easier.

Would it be possible to generate diagrams for the documentation?  Or, to start with, the Standard Library?  

(Specifically, I?m thinking of UML Class Diagrams.  When I want a quick overview of what something does, they are invaluable.  And if they contain hypertext that links from the diagram to the full text, they are my salvation! :) 


?Zearin (Tony)

From bannerts at gmail.com  Sat Feb 18 10:03:16 2012
From: bannerts at gmail.com (Scott Bannert)
Date: Sat, 18 Feb 2012 03:03:16 -0600
Subject: [docs] calendar bug related to September 2-14, 1752
Message-ID: <CAGwSiD325K-P49_05ww2AH+xsPv78UuUMicbp7Fggibaa+MsZw@mail.gmail.com>

Hello,

I think I might have found an issue with the calendar related to the point
of time in history when the date was necessary to correct by 11 days.
Anyhow, the correction is made in a GNU+linux machine, so it seems like
something worth fixing in python.  I have created an account at
bugs.python.org (username: bannerts) and submitted a bug (ID: 14048),
however I'm new at this so I thought I would send an email too.

*How I discovered it: *
I was reading through some posts on reddit when I came up on this one:
http://www.reddit.com/r/linux/comments/9jl2t/1_open_a_linux_terminal_2_enter_cal_9_1752_3_shit/
which seemed to state that in the September of 1752, they decided to skip
from Wednesday the 2nd to Thursday the 14th.  Out of curiosity, I decided
to see if Python had it recorded this way by typing in the following
commands in python:

>>> import calendar
>>> calendar.TextCalendar().pryear(1752)

The calendar printed does not show this correction, which I suppose is
something that might be worth fixing.

Anyhow, I'm relatively new to using python and I have found that the
language is really useful.  Whoever you are, keep up the good work.

-- 
Scott Bannert

Cell: (979) 418-2422
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120218/558cb885/attachment.html>

From report at bugs.python.org  Sat Feb 18 11:39:50 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 18 Feb 2012 10:39:50 +0000
Subject: [docs] [issue13999] Queue references in multiprocessing doc points
	to Queue	module and not to self
In-Reply-To: <1329072364.23.0.444581618774.issue13999@psf.upfronthosting.co.za>
Message-ID: <1329561590.37.0.10318773705.issue13999@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Feb 18 11:41:37 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 18 Feb 2012 10:41:37 +0000
Subject: [docs] [issue14003] __self__ on built-in functions is not as
	documented
In-Reply-To: <1329159935.3.0.264942191971.issue14003@psf.upfronthosting.co.za>
Message-ID: <1329561697.62.0.835826232745.issue14003@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/issue14003>
_______________________________________

From report at bugs.python.org  Sat Feb 18 11:44:35 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 18 Feb 2012 10:44:35 +0000
Subject: [docs] [issue14034] the example in argparse doc is too complex
In-Reply-To: <1329417262.26.0.419020263055.issue14034@psf.upfronthosting.co.za>
Message-ID: <1329561875.62.0.814700596784.issue14034@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Feb 18 11:48:24 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 18 Feb 2012 10:48:24 +0000
Subject: [docs] [issue14042] json.dumps() documentation is slightly
	incorrect.
In-Reply-To: <1329494870.59.0.571991231564.issue14042@psf.upfronthosting.co.za>
Message-ID: <1329562104.33.0.318713488793.issue14042@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

See #13770 and #13769.

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

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

From report at bugs.python.org  Sat Feb 18 13:59:58 2012
From: report at bugs.python.org (anatoly techtonik)
Date: Sat, 18 Feb 2012 12:59:58 +0000
Subject: [docs] [issue14049] execfile() fails on files that use global
	variables	inside functions
Message-ID: <1329569998.87.0.931536345344.issue14049@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

main.py below fails to execute local.py, which work ok (outputs '2') when processed directly in console.

Docs are not explaining anything. They spread fear and uncertainty around locals, but nothing is said why globals may fail.
http://docs.python.org/library/functions.html#execfile


---[cut main.py]---
values = {}
glavues = {}
execfile('local.py', glavues, values)
---[/cut]-----------

---[cut local.py]---
x = 1
def weird():
    y = x + 1
    return y
print weird()
---[/cut]-----------



Traceback (most recent call last):
  File "main.py", line 5, in <module>
    execfile('local.py', glavues, values)
  File "local.py", line 7, in <module>
    print weird()
  File "local.py", line 5, in weird
    y = x + 1
NameError: global name 'x' is not defined

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 153643
nosy: docs at python, techtonik
priority: normal
severity: normal
status: open
title: execfile() fails on files that use global variables inside functions
versions: Python 2.7

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

From sandro.tosi at gmail.com  Sat Feb 18 14:16:15 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sat, 18 Feb 2012 14:16:15 +0100
Subject: [docs] Diagrams Wanted
In-Reply-To: <CDD7F200-5B2B-480A-AADA-E541A65894B6@gonk.net>
References: <CDD7F200-5B2B-480A-AADA-E541A65894B6@gonk.net>
Message-ID: <CAPdtAj31U6JD9nZxFnxw8zAFLiFbWN2L56bz-OEdGLvTtz+u=A@mail.gmail.com>

Hello Zearin,
thanks for your email.

On Sat, Feb 18, 2012 at 01:16, Zearin <zearin at gonk.net> wrote:
> Would it be possible to generate diagrams for the documentation? ?Or, to start with, the Standard Library?

I think it would be nice if you can sketch-up something, just to show
how exactly you'd like to see. Also, regarding UML diagrams, it's not
that Python has that huge classes hierarchy (a-la Java) and probably
the result wouldn't be what you'd expected.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Sat Feb 18 15:58:57 2012
From: report at bugs.python.org (Nick Coghlan)
Date: Sat, 18 Feb 2012 14:58:57 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329577136.92.0.644653115348.issue13997@psf.upfronthosting.co.za>


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

The other thing that came out of the rambling Unicode thread on python-ideas is that we should clearly articulate the options for processing files in a task-based fashion and describe the trade-offs for the different alternatives.

I started writing up my notes on that as a tracker comment, but the became a little... long: http://readthedocs.org/docs/ncoghlan_devs-python-notes/en/latest/py3k_text_file_processing.html

----------

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

From sandro.tosi at gmail.com  Sat Feb 18 16:12:36 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sat, 18 Feb 2012 16:12:36 +0100
Subject: [docs] Fix a documentation bug in python v3.2.2 documentation
In-Reply-To: <CAGc_ELPbFbSe+VuvFXs3t6PT8pRvPjuUpBjDnEOt6v6BM+QdyQ@mail.gmail.com>
References: <CAGc_ELPbFbSe+VuvFXs3t6PT8pRvPjuUpBjDnEOt6v6BM+QdyQ@mail.gmail.com>
Message-ID: <CAPdtAj0T3Hp3RmnJx3PHdgd=9RUadXefj+Wu-30dzHRJJrM+pw@mail.gmail.com>

Hello kan,
thanks for the report.

On Fri, Feb 17, 2012 at 15:24, kan lianlian <lianliankan2010 at gmail.com> wrote:
> bytearray(b'a123fg') ? ? ? ? ? ? ? ? ? ? ? ### This line is wrong.

This has been fixed in 3.2 and 3.3 with this changesets:
9ce5d456138b , 5a19909f5845

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From drewvb at lantic.net  Sat Feb 18 14:04:52 2012
From: drewvb at lantic.net (Drew)
Date: Sat, 18 Feb 2012 15:04:52 +0200
Subject: [docs] python using my bandwidth
Message-ID: <4F3FA1F4.3030904@lantic.net>

Hi,
I have bought a new computer and installed Ubuntu Linux 11.10
My bandwidth is being used up very quickly.
I used 'sudo nethogs eth0' in a terminal
This showed that /usr/bin/python is the only program continually using 
the internet and using my bandwidth.
What can I do to stop this happening?
Thank you and regards
Drew von Bratt
Port Elizabeth
South Africa

From sandro.tosi at gmail.com  Sat Feb 18 16:18:04 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sat, 18 Feb 2012 16:18:04 +0100
Subject: [docs] python using my bandwidth
In-Reply-To: <4F3FA1F4.3030904@lantic.net>
References: <4F3FA1F4.3030904@lantic.net>
Message-ID: <CAPdtAj1tVeHve_s-vKuQWs5bt=u7v_esPnoXBOOmeRm4Qt-4DA@mail.gmail.com>

Hello Drew,
i'm sorry but this is not the right forum to solve your problem.

On Sat, Feb 18, 2012 at 14:04, Drew <drewvb at lantic.net> wrote:
> Hi,
> I have bought a new computer and installed Ubuntu Linux 11.10
> My bandwidth is being used up very quickly.
> I used 'sudo nethogs eth0' in a terminal
> This showed that /usr/bin/python is the only program continually using the
> internet and using my bandwidth.
> What can I do to stop this happening?

You have installed ubuntu, so you should seek help from their help
forums (either mailing lists, chats or whatever). The fact you're
seeing a 'python' process running it indicates to me it might be a
script or a program written in python that's running, not the Python
interpreter itself that's causing that.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Sat Feb 18 17:58:49 2012
From: report at bugs.python.org (Sandro Tosi)
Date: Sat, 18 Feb 2012 16:58:49 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
Message-ID: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>


New submission from Sandro Tosi <sandro.tosi at gmail.com>:

I'm providing patches for what reported at http://mail.python.org/pipermail/docs/2012-February/007481.html . I'm not sure on wording or even if we want them in the tutorial section, but I think it would be nice to have it documented nonetheless.

----------
assignee: docs at python
components: Documentation
files: list_sort-py27.diff
keywords: patch
messages: 153648
nosy: docs at python, sandro.tosi
priority: normal
severity: normal
stage: patch review
status: open
title: Tutorial, list.sort() and items comparability
versions: Python 2.7, Python 3.2, Python 3.3
Added file: http://bugs.python.org/file24557/list_sort-py27.diff

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

From report at bugs.python.org  Sat Feb 18 17:58:56 2012
From: report at bugs.python.org (Sandro Tosi)
Date: Sat, 18 Feb 2012 16:58:56 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
In-Reply-To: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>
Message-ID: <1329584336.56.0.149418509866.issue14050@psf.upfronthosting.co.za>


Changes by Sandro Tosi <sandro.tosi at gmail.com>:


Added file: http://bugs.python.org/file24558/list_sort-py32.diff

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

From sandro.tosi at gmail.com  Sat Feb 18 18:01:52 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sat, 18 Feb 2012 18:01:52 +0100
Subject: [docs] Python v2.7.2 documentation > The Python Tutorial > 5.1
 More on Lists
In-Reply-To: <CAJ=RWHN+fbiZNmj4ieOn4LnhP8T4CL3e+yr8TOfEh+dywYE3jw@mail.gmail.com>
References: <CAJ=RWHN+fbiZNmj4ieOn4LnhP8T4CL3e+yr8TOfEh+dywYE3jw@mail.gmail.com>
Message-ID: <CAPdtAj1jRUT07O8juu_iTkAHmbOfjWC7VxkuV75U5C+fxR86pQ@mail.gmail.com>

Hello Jim,
thanks for your report.

On Sun, Feb 12, 2012 at 04:44, Jim Kovacs <jim.kovacs at gmail.com> wrote:
> Regarding the Python v2.7.2 documentation > The Python Tutorial > 5.1
> More on Lists (
> http://docs.python.org/tutorial/datastructures.html#more-on-lists ),
> for list.sort() consider briefly mentioning that an "ordering
> relation" must be defined.
>
> E.g. this results in an error:
>
> a = ['abc', 3.14159, complex(1,-1), 123]
> print a.sort()
>
> ? ?print a.sort()
> TypeError: no ordering relation is defined for complex numbers

i've opened http://bugs.python.org/issue14050 to fix it.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Sat Feb 18 18:26:46 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sat, 18 Feb 2012 18:26:46 +0100
Subject: [docs] smtplib minor change
In-Reply-To: <CAORfpewCDgauM_xh8JQVHTfa2Fi3Jkq6J5Gs5qNDHOJ-0PVcsA@mail.gmail.com>
References: <CAORfpewCDgauM_xh8JQVHTfa2Fi3Jkq6J5Gs5qNDHOJ-0PVcsA@mail.gmail.com>
Message-ID: <CAPdtAj25fz3cfge=9B8kHZZ2HgAt30T0rfcw9sFeoOtXRo6k8w@mail.gmail.com>

Hello Markus,
thanks for your email.

On Mon, Feb 13, 2012 at 08:03, Markus Billerwell <mbillerwell at gmail.com> wrote:
> In a future version of smtplib, could you please change all the
> commands to uppercase as per RFC821?

The RFC clearly states, at section 2, that:

   Commands and replies are not case sensitive.  That is, a command or
   reply word may be upper case, lower case, or any mixture of upper and
   lower case.

So I think we have nothing to change.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Sat Feb 18 19:04:44 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sat, 18 Feb 2012 19:04:44 +0100
Subject: [docs] 18.1.2.1. FeedParser API Error
In-Reply-To: <CAKqeJerm_-5U9JaCWqBEWr4s6HQQe+7kbO6OZuguG5U+F_8j1Q@mail.gmail.com>
References: <CAKqeJerm_-5U9JaCWqBEWr4s6HQQe+7kbO6OZuguG5U+F_8j1Q@mail.gmail.com>
Message-ID: <CAPdtAj029jninD-GLRBq3veWQW5Kg59utbp3SKh8vzFvECAaBQ@mail.gmail.com>

Hello Julian,
thanks for your email.

On Fri, Feb 3, 2012 at 05:08, Julian Ceipek
<julian.ceipek at students.olin.edu> wrote:
> The following is inaccurate in 18.1.2.1.:
>
>> Here is the API for the?FeedParser:
>> class?email.parser.FeedParser([_factory])
>> Create a?FeedParser?instance. Optional?_factory?is a no-argument callable
>> that will be called whenever a new message object is needed. It defaults to
>> the?email.message.Message?class.
>
> It seems to actually be "email.FeedParser.FeedParser("

Could you please explain why you think it's another class? I just did:

$ ./python
Python 2.7.2+ (2.7:f0666e56a552, Jan  7 2012, 16:31:06)
[GCC 4.6.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from email.parser import FeedParser
>>> dir(FeedParser)
['__doc__', '__init__', '__module__', '_call_parse', '_new_message',
'_parse_headers', '_parsegen', '_pop_message', '_set_headersonly',
'close', 'feed']

(a similar output is for 3.2 and 3.3), so the documented class.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Sat Feb 18 19:10:04 2012
From: report at bugs.python.org (=?utf-8?q?Lars_Gust=C3=A4bel?=)
Date: Sat, 18 Feb 2012 18:10:04 +0000
Subject: [docs] [issue14013] tarfile should expose supported formats
In-Reply-To: <1329236847.51.0.270430673151.issue14013@psf.upfronthosting.co.za>
Message-ID: <1329588604.33.0.900412148835.issue14013@psf.upfronthosting.co.za>


Lars Gust?bel <lars at gustaebel.de> added the comment:

I think this is a reasonable proposal. I think it is good style to let tarfile figure out which supported compression methods are available instead of shutil or the user. So far I have no objections.

Following 3.3's crypt module, I think the name `methods' is superior to `formats' (maybe `compression_methods' is even better). Also, crypt's concept of a sorted list from stronger to weaker could also make sense here: ["xz", "bz2", "gz"]. Why not?

----------

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

From report at bugs.python.org  Sat Feb 18 19:42:05 2012
From: report at bugs.python.org (Arfrever Frehtes Taifersar Arahesis)
Date: Sat, 18 Feb 2012 18:42:05 +0000
Subject: [docs] [issue14003] __self__ on built-in functions is not as
	documented
In-Reply-To: <1329159935.3.0.264942191971.issue14003@psf.upfronthosting.co.za>
Message-ID: <1329590525.27.0.0613703419002.issue14003@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/issue14003>
_______________________________________

From sandro.tosi at gmail.com  Sat Feb 18 20:35:04 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sat, 18 Feb 2012 20:35:04 +0100
Subject: [docs] Documentation bug for datetime.time()
In-Reply-To: <20120214052744.GA5083@gmail.com>
References: <20120214052744.GA5083@gmail.com>
Message-ID: <CAPdtAj0KjshDX9gnj9Q09QNZTAiZq39KvpWVURCT=1kfTGspOw@mail.gmail.com>

Hello Erik,
thanks for your report.

On Tue, Feb 14, 2012 at 06:27, Erik Johnson <palehose at gmail.com> wrote:
> http://docs.python.org/library/datetime.html?highlight=datetime#datetime.datetime.time
>
> The word "time" in this function links to the documentation for the
> "time" module (http://docs.python.org/library/time.html#module-time). It
> should link to the following URL:
>
> http://docs.python.org/library/datetime.html?highlight=datetime#time-objects

That's been fixed with: http://hg.python.org/cpython/rev/30ff707ed75f

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Sat Feb 18 20:42:43 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 18 Feb 2012 19:42:43 +0000
Subject: [docs] [issue13997] Clearly explain the bare minimum Python 3 users
	should	know about Unicode
In-Reply-To: <1329021187.19.0.262146289648.issue13997@psf.upfronthosting.co.za>
Message-ID: <1329594163.37.0.00436649168239.issue13997@psf.upfronthosting.co.za>


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

Yes, the 'how to' alternatives, with + and -, should be included in the doc addition. I thought it the best thing to come out of the python-ideas thread.

----------

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

From report at bugs.python.org  Sun Feb 19 09:34:34 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 19 Feb 2012 08:34:34 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
In-Reply-To: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>
Message-ID: <1329640474.63.0.212753555001.issue14050@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

We could just mention that a TypeError is raised if some of the elements can't be compared. (Note that sorting a list that contains some types that cannot be compared might still succeed in some corner cases, but there's no reason to mention this).

----------
nosy: +ezio.melotti

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

From report at bugs.python.org  Sun Feb 19 09:36:25 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 19 Feb 2012 08:36:25 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
In-Reply-To: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>
Message-ID: <1329640585.58.0.818467593225.issue14050@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

If I had read your patched version when I was a beginner, I don?t think it would have helped me much.  (Sorry for not coming up with an alternative right now, it?s late/early here and I?m tired :)

----------
nosy: +eric.araujo, terry.reedy

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

From sandro.tosi at gmail.com  Sun Feb 19 12:49:50 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sun, 19 Feb 2012 12:49:50 +0100
Subject: [docs] Some mistakes in docs
In-Reply-To: <165401328895961@web3.yandex.ru>
References: <165401328895961@web3.yandex.ru>
Message-ID: <CAPdtAj3usaGWwU=7uTNMnwWS9Rd0BRsGP5z-WKT65fDRW7G=iw@mail.gmail.com>

Hello Sergey,
thanks for your email.

On Fri, Feb 10, 2012 at 18:46, Sergey <shtycksb at yandex.ru> wrote:
> * 1
> 2011.08.12 02:58 Moscow Time
> File /whatsnew/2.4.txt line 953.
> Two words "are" instead one.
> The same is in python-2.7.2-docs-html/whatsnew/2.4.html.
>
> debian at debian:~/Documents/TXT$ cat -n ?python-2.7.2-docs-text/whatsnew/2.4.txt | ?grep "are are"
> ? 953 ? ?``dict.__contains__()`` are are now implemented as

This has been fixed some time ago with this changeset: 86e3943d0d5b

> * 2
> 2011.08.11 03:57 Moscow Time
> File /whatsnew/2.4.txt line 1561.
> Unneeded space in "Hye-Shik Chan".
>
> debian at debian:~/Documents/TXT$ cat -n python-2.7.2-docs-text/whatsnew/2.4.txt | grep Shik ?| tail -1
> ?1561 ?article: Koray Can, Hye- Shik Chang, Michael Dyck, Raymond Hettinger,

This has just been fixed in all active branches.

> * 3
> 2011.08.15 02:53 Moscow Time
> WT..?
> File /whatsnew/2.6.txt line 8
>
> $ head ?-12 ?2.6.txt
>
> What's New in Python 2.7
> ************************

this has already been fixed:
http://docs.python.org/release/2.7.2/whatsnew/2.6.html

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Sun Feb 19 19:59:45 2012
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 19 Feb 2012 18:59:45 +0000
Subject: [docs] [issue13605] document argparse's nargs=REMAINDER
In-Reply-To: <1323955710.42.0.753468095058.issue13605@psf.upfronthosting.co.za>
Message-ID: <E1RzByz-0001S9-EZ@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 996efb0425c5 by Sandro Tosi in branch '3.2':
Issue #13605: use print() in argparse nargs example
http://hg.python.org/cpython/rev/996efb0425c5

New changeset c3daa6a834c6 by Sandro Tosi in branch 'default':
Issue #13605: merge with 3.2
http://hg.python.org/cpython/rev/c3daa6a834c6

----------

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

From report at bugs.python.org  Sun Feb 19 23:54:13 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 19 Feb 2012 22:54:13 +0000
Subject: [docs] [issue14034] first example in argparse doc is too complicated
In-Reply-To: <1329417262.26.0.419020263055.issue14034@psf.upfronthosting.co.za>
Message-ID: <1329692053.5.0.754612134253.issue14034@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I think I was rude too when I called you off, apologies.  I?ll gladly review or help with a patch.

----------
title: the example in argparse doc is too complex -> first example in argparse doc is too complicated

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

From report at bugs.python.org  Mon Feb 20 01:52:57 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 20 Feb 2012 00:52:57 +0000
Subject: [docs] [issue13605] document argparse's nargs=REMAINDER
In-Reply-To: <1323955710.42.0.753468095058.issue13605@psf.upfronthosting.co.za>
Message-ID: <1329699177.47.0.805700810902.issue13605@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I have added the missing ?::? before code blocks (one was added by the patch you committed, others were already here).

I?m not entirely sure they are needed (Python code blocks seem to be autodetected and show up colorized too), but I did it for consistency (and to make my editor detect them).

----------

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

From report at bugs.python.org  Mon Feb 20 03:19:39 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 20 Feb 2012 02:19:39 +0000
Subject: [docs] [issue14013] tarfile should expose supported formats
In-Reply-To: <1329236847.51.0.270430673151.issue14013@psf.upfronthosting.co.za>
Message-ID: <1329704379.77.0.821033351466.issue14013@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Thanks for the quick reply.

> I think it is good style to let tarfile figure out which supported compression methods are
> available instead of shutil or the user.
Note that shutil will not be wholly transparent when I?m done with the refactoring, as it will be able to translate 'xztar', 'bztar' and 'gztar' to tarfile mode strings, but will need to have a special case to morph 'bztar' to 'bz2'.  It will be a small ugliness.

(There will also be ugliness in packaging: Even if I make it transparently supports all formats that shutil supports, I?ll need to have a bit of duplication because packaging has a preferred format by platform.  Well.)

> Following 3.3's crypt module, I think the name `methods' is superior to `formats' (maybe
> `compression_methods' is even better).
Note that crypt?s methods really are instances of something called Method.  hashlib has algorithms_guaranteed and algorithms_available since 3.2 and shutil uses get_archive_formats and get_unpack_formats.  I went for tarfile.compression_formats.

> Also, crypt's concept of a sorted list from stronger to weaker could also make sense here:
Sure.  In my first patch I put gz first as it should be universally available, and then put xz before bz2 as I think bz2 is quickly losing ground to xz (even GNU and Debian are switching to xz for their archives).  The attached patch follows your idea.

BTW I will gladly wait for commits related to the other bugs (misc bugs and misc doc edits) and refresh my patch then.

----------
Added file: http://bugs.python.org/file24573/add-tarfile.compression_formats.diff

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

From report at bugs.python.org  Mon Feb 20 08:14:24 2012
From: report at bugs.python.org (Sandro Tosi)
Date: Mon, 20 Feb 2012 07:14:24 +0000
Subject: [docs] [issue13605] document argparse's nargs=REMAINDER
In-Reply-To: <1329699177.47.0.805700810902.issue13605@psf.upfronthosting.co.za>
Message-ID: <CAPdtAj0apsz2oi15MwAACWRTQ9Hde+TCioxRWEyi7Z8Q1nrFng@mail.gmail.com>


Sandro Tosi <sandro.tosi at gmail.com> added the comment:

On Mon, Feb 20, 2012 at 01:52, ?ric Araujo <report at bugs.python.org> wrote:
> I?m not entirely sure they are needed (Python code blocks seem to be autodetected and show up colorized too), but I did it for consistency (and to make my editor detect them).

Yeah, I refrained to add them since the code blocks were already
correctly identified; but consistency is Good :)

----------

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

From report at bugs.python.org  Mon Feb 20 09:18:43 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Mon, 20 Feb 2012 08:18:43 +0000
Subject: [docs] [issue14034] first example in argparse doc is too complicated
In-Reply-To: <1329417262.26.0.419020263055.issue14034@psf.upfronthosting.co.za>
Message-ID: <1329725921.63.0.327975806201.issue14034@psf.upfronthosting.co.za>


Tshepang Lekhonkhobe <tshepang at gmail.com> added the comment:

I chose to go the way of a howto. I find argparse complex enough to deserve one.

note: I have checked each example on the 3 releases that possess the module (2.7, 3.2, and 3.3), and the differences in output are very small.

----------
keywords: +patch
Added file: http://bugs.python.org/file24576/argparse_howto.patch

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

From report at bugs.python.org  Mon Feb 20 09:24:45 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Mon, 20 Feb 2012 08:24:45 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
In-Reply-To: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>
Message-ID: <1329726285.89.0.859090277623.issue14050@psf.upfronthosting.co.za>


Tshepang Lekhonkhobe <tshepang at gmail.com> added the comment:

An an aside, shouldn't that be "in-place" instead of "in place (http://en.wikipedia.org/wiki/In-place)?

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

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

From report at bugs.python.org  Mon Feb 20 09:39:10 2012
From: report at bugs.python.org (Georg Brandl)
Date: Mon, 20 Feb 2012 08:39:10 +0000
Subject: [docs] [issue13605] document argparse's nargs=REMAINDER
In-Reply-To: <1323955710.42.0.753468095058.issue13605@psf.upfronthosting.co.za>
Message-ID: <1329727150.36.0.154270556306.issue13605@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

Blocks not introduced by "::" are *NOT* code blocks.

If they happen to begin with ">>> ", they are recognized as doctest blocks and colorized as doctests.

Doctest blocks shouldn't be indented. (The indent is a blockquote in this case.)

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

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

From report at bugs.python.org  Mon Feb 20 11:26:25 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Mon, 20 Feb 2012 10:26:25 +0000
Subject: [docs] [issue13605] document argparse's nargs=REMAINDER
In-Reply-To: <1323955710.42.0.753468095058.issue13605@psf.upfronthosting.co.za>
Message-ID: <1329733585.51.0.233173986338.issue13605@psf.upfronthosting.co.za>


Tshepang Lekhonkhobe <tshepang at gmail.com> added the comment:

(this is only concerning the latest commit)

Not sure if I should open a new issue, but why is there a print function at all, given that:

>>> print(parser.parse_args('--foo B cmd --arg1 XX ZZ'.split()))
Namespace(args=['--arg1', 'XX', 'ZZ'], command='cmd', foo='B')

>>> parser.parse_args('--foo B cmd --arg1 XX ZZ'.split())
Namespace(args=['--arg1', 'XX', 'ZZ'], command='cmd', foo='B')

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

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

From felix.antoine.fortin at gmail.com  Sun Feb 19 19:29:17 2012
From: felix.antoine.fortin at gmail.com (=?iso-8859-1?Q?F=E9lix-Antoine_Fortin?=)
Date: Sun, 19 Feb 2012 13:29:17 -0500
Subject: [docs] error Python 3.* - 9.3 operator, section 9.3.1, Division
Message-ID: <6DC1DA3F-51C4-4914-B99A-39EFF270D1F2@gmail.com>

Hi,

There is an error in the documentation of Python 3.*.

In abstract operations table in section 9.3.1 the first of two lines
on Division, the associated function should be : truediv() instead of div().

F?lix-Antoine Fortin



From gustavo at gustavo.eng.br  Mon Feb 20 19:05:46 2012
From: gustavo at gustavo.eng.br (Gustavo Ambrozio)
Date: Mon, 20 Feb 2012 16:05:46 -0200
Subject: [docs] Python and doxygen
In-Reply-To: <CAPdtAj3wkFM+i8Gw7A5JviLNRVmSxs6NYQ5LUeeyXP50GfmVyw@mail.gmail.com>
References: <CAB5XREf7ceZbxTqnc3U3QjFEZLmfu_Zywr-sA1MRghXOutxHmg@mail.gmail.com>
	<CAPdtAj3wkFM+i8Gw7A5JviLNRVmSxs6NYQ5LUeeyXP50GfmVyw@mail.gmail.com>
Message-ID: <CAB5XREcC1w=7wf0qD0n52nfQjWb13L4OqX8OvK5sPTZ7p95rew@mail.gmail.com>

Sandro,

I managed to generate docset versions of Python's docs from the HTML docs
and posted about it here:

http://blog.codecropper.com/2012/02/pythons-documentation-at-your-fingertips/

I think you may like it.

Cheers,
Gustavo
--------------------------------------------------------------
Check out Snap!: http://snap.codecrop.com/
Snap turns your iPhone camera into a productivity tool.



On Sun, Feb 12, 2012 at 8:30 AM, Sandro Tosi <sandro.tosi at gmail.com> wrote:

> Hello Gustavo,
> thanks for contacting us!
>
> On Sun, Feb 12, 2012 at 05:40, Gustavo Ambrozio <gustavo at gustavo.eng.br>
> wrote:
> > Since I want to have a pyhton docset to use in Dash I decided to reach
> out.
> > Is there any other file format that I can get python's documentation in?
> > Like XML? How are the HTML files generated?
>
> The python documentation (at least in its recent versions, f.e. from
> 2.6 onwards) it's generated from ReST files, that are later converted
> to several output formats (HTML, PDF, TXT, and so on) by a wonderful
> tool: sphinx.
>
> So you can definetely use the ReST format: you can clone the CPython
> mercurial repository and start playing with those files; you can refer
> to:
>
> * http://docs.python.org/devguide/#quick-start
> * http://docs.python.org/devguide/docquality.html
>
> for additional details, and in case of doubts, don't hesitate to ask
> again on this list.
>
> Regards,
> --
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120220/b0501377/attachment.html>

From report at bugs.python.org  Tue Feb 21 01:00:40 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 21 Feb 2012 00:00:40 +0000
Subject: [docs] [issue14050] Tutorial, list.sort() and items comparability
In-Reply-To: <1329584329.12.0.545057513034.issue14050@psf.upfronthosting.co.za>
Message-ID: <1329782440.01.0.542914649895.issue14050@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Nope, the expression would be hyphenated only when used as an adjective:

- ?This sorts the sequence in place?
vs.
? ?Performs an in-place rearrangement by birthdate?

----------

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

From report at bugs.python.org  Tue Feb 21 01:01:43 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 21 Feb 2012 00:01:43 +0000
Subject: [docs] [issue14034] Add argparse howto
In-Reply-To: <1329417262.26.0.419020263055.issue14034@psf.upfronthosting.co.za>
Message-ID: <1329782503.49.0.103312870639.issue14034@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Nice.  I?ll find time to review later; Steven, do you have objections on the idea of adding an argparse howto?  Do you want to review it yourself?

----------
nosy: +bethard
title: first example in argparse doc is too complicated -> Add argparse howto

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

From report at bugs.python.org  Tue Feb 21 01:11:59 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Tue, 21 Feb 2012 00:11:59 +0000
Subject: [docs] [issue13605] document argparse's nargs=REMAINDER
In-Reply-To: <1323955710.42.0.753468095058.issue13605@psf.upfronthosting.co.za>
Message-ID: <1329783119.81.0.233064819032.issue13605@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> Blocks not introduced by "::" are *NOT* code blocks.
> If they happen to begin with ">>> ", they are recognized as doctest blocks
> and colorized as doctests.

Ah, that?s it!  Thanks.  So we have two valid ways of marking up doctest-like blocks, ?::? ? indent and implicit markup, right?

----------

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

From report at bugs.python.org  Tue Feb 21 07:17:30 2012
From: report at bugs.python.org (Georg Brandl)
Date: Tue, 21 Feb 2012 06:17:30 +0000
Subject: [docs] [issue13605] document argparse's nargs=REMAINDER
In-Reply-To: <1323955710.42.0.753468095058.issue13605@psf.upfronthosting.co.za>
Message-ID: <1329805050.56.0.830857655323.issue13605@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

Yes, that's correct.

----------

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

From report at bugs.python.org  Tue Feb 21 11:35:03 2012
From: report at bugs.python.org (Steven Bethard)
Date: Tue, 21 Feb 2012 10:35:03 +0000
Subject: [docs] [issue14034] Add argparse howto
In-Reply-To: <1329417262.26.0.419020263055.issue14034@psf.upfronthosting.co.za>
Message-ID: <1329820503.83.0.166066116123.issue14034@psf.upfronthosting.co.za>


Steven Bethard <steven.bethard at gmail.com> added the comment:

I have no objections on adding a howto, and something like the attached patch would be fine with me (though I don't have time to review it in full and trust you to).

You might want to coordinate with Issue 13850 a bit - they want a quick reference table before the first example (which would therefore mean before this howto which is replacing the first example).

----------

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

From report at bugs.python.org  Tue Feb 21 21:33:11 2012
From: report at bugs.python.org (Leon Matthews)
Date: Tue, 21 Feb 2012 20:33:11 +0000
Subject: [docs] [issue14006] Improve the documentation of
	xml.etree.ElementTree
In-Reply-To: <1329190125.69.0.69162565954.issue14006@psf.upfronthosting.co.za>
Message-ID: <1329856391.1.0.956791562549.issue14006@psf.upfronthosting.co.za>


Leon Matthews <leon at lost.co.nz> added the comment:

The ElementTree.py module has good JavaDoc-style function-level documentation, but as it's not in docstring format, it can't be seen from the interactive help.

I'd be willing to convert the current comments into docstrings, as long as I wouldn't be stepping on anybody's toes, and somebody could give me some guidance as to how to convert the @return and @param declarations, and how to handle the C version of the module.  

Any volunteers?

----------
nosy: +leonov

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

From report at bugs.python.org  Wed Feb 22 13:41:05 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 22 Feb 2012 12:41:05 +0000
Subject: [docs] [issue14034] Add argparse howto
In-Reply-To: <1329417262.26.0.419020263055.issue14034@psf.upfronthosting.co.za>
Message-ID: <1329914465.46.0.351586579567.issue14034@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> You might want to coordinate with Issue 13850 a bit - they want a quick reference table before
> the first example (which would therefore mean before this howto which is replacing the first example).

The howto discussed here would be a new file in Doc/howto, so no conflict.

----------

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

From report at bugs.python.org  Wed Feb 22 17:01:18 2012
From: report at bugs.python.org (Zbyszek Szmek)
Date: Wed, 22 Feb 2012 16:01:18 +0000
Subject: [docs] [issue13779] os.walk: bottom-up
In-Reply-To: <1326452589.73.0.0617213643117.issue13779@psf.upfronthosting.co.za>
Message-ID: <1329926477.96.0.0381681228891.issue13779@psf.upfronthosting.co.za>


Zbyszek Szmek <zbyszek at in.waw.pl> added the comment:

Maybe this could be closed? I'm attaching a small patch with a documentation clarification. (Adds "In either case the list of
subdirectories is retrieved before the tuples for the directory and
its subdirectories are generated.").

----------
keywords: +patch
Added file: http://bugs.python.org/file24603/issue13779.patch

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

From report at bugs.python.org  Wed Feb 22 17:22:05 2012
From: report at bugs.python.org (Steven Bethard)
Date: Wed, 22 Feb 2012 16:22:05 +0000
Subject: [docs] [issue14034] Add argparse howto
In-Reply-To: <1329417262.26.0.419020263055.issue14034@psf.upfronthosting.co.za>
Message-ID: <1329927725.28.0.78096261446.issue14034@psf.upfronthosting.co.za>


Steven Bethard <steven.bethard at gmail.com> added the comment:

Oh ok. Sounds good then!

----------

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

From bholladay at ucsd.edu  Wed Feb 22 22:09:59 2012
From: bholladay at ucsd.edu (Ben Holladay)
Date: Wed, 22 Feb 2012 13:09:59 -0800
Subject: [docs] Str Format: Default g precision
Message-ID: <6c2adafc7bed1b0a2bacea0210c80c77.squirrel@physics-mail.ucsd.edu>

In the docs for string format mini-specification, there is no mention of
the default precision for the 'g' presentation type. The precision is
mentioned for the 'none' type, 12 to match str(), but nothing is said for
the plain 'g' type. I did some experimenting and it appears to default to
6 but I could be wrong. I think this would be useful information and
should be added to the documentation.

ben h


From report at bugs.python.org  Thu Feb 23 02:27:02 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 23 Feb 2012 01:27:02 +0000
Subject: [docs] [issue14006] Improve the documentation of
	xml.etree.ElementTree
In-Reply-To: <1329190125.69.0.69162565954.issue14006@psf.upfronthosting.co.za>
Message-ID: <1329960422.72.0.602754063182.issue14006@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> The ElementTree.py module has good JavaDoc-style function-level documentation, but as it's not
> in docstring format, it can't be seen from the interactive help.
> 
> I'd be willing to convert the current comments into docstrings, as long as I wouldn't be
> stepping on anybody's toes,
Great, thanks!  I don?t know if the best approach here is to add lengthy docstrings or move the information from the comments into the reST docs.  Maybe this should be asked on the core-mentorship or python-dev mailing list.

> and somebody could give me some guidance as to how to convert the @return and @param declarations
In docstrings as well as in reST docs we just use English, with asterisks to mark up parameters, e.g. ?*path* is an instance of :class:`ElementPath`. ... Returns ``True`` if there is a match, ``False`` otherwise.?

> and how to handle the C version of the module.
Doctrings for C modules are not hard to find, just a little painful to write.  If we agree to turn comments into docstrings and you need help, I?ll be glad to guide you with that.

----------

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

From report at bugs.python.org  Thu Feb 23 04:36:34 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 23 Feb 2012 03:36:34 +0000
Subject: [docs] [issue14006] Improve the documentation of
	xml.etree.ElementTree
In-Reply-To: <1329190125.69.0.69162565954.issue14006@psf.upfronthosting.co.za>
Message-ID: <1329968193.97.0.794544535456.issue14006@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Converting sounds good to me, but it should be done carefully.

I think you can have two paragraphs in the docstrings: the first with the description of what it does and what it returns, and the second with the arguments.

For example Lib/xml/etree/ElementTree.py:355:
# Finds the first matching subelement, by tag name or path.
#
# @param path What element to look for.
# @keyparam namespaces Optional namespace prefix map.
# @return The first matching element, or None if no element was found.
# @defreturn Element or None

can become something like:
"""
Finds the first matching subelement, by tag name or path
and returns the first matching element, or None if no
 element was found.

*path* is the element to look for and *namespace* is an
optional namespace prefix map.
"""

----------

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

From report at bugs.python.org  Thu Feb 23 04:47:17 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Thu, 23 Feb 2012 03:47:17 +0000
Subject: [docs] [issue14006] Improve the documentation of
	xml.etree.ElementTree
In-Reply-To: <1329190125.69.0.69162565954.issue14006@psf.upfronthosting.co.za>
Message-ID: <1329968837.3.0.273301679104.issue14006@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

My general rule is that function/method docstrings are better short descriptions of what the function does and what the arguments are, a usage reminder for people who have already used the function.  Classes docstrings can tell a bit more about how the class is supposed to be used, e.g. what particular responsibility they have and what they work with.  Module docstrings should help you make sense of the public objects in the module, for example tell about the main classes and functions and briefly mentioning the less important ones.

This is a personal viewpoint; some people use dir and pydoc a lot to get the most info out of a new module, whereas I like separate documentation more.

ElementTree has no docstrings at all, which is IMO bad; I?d like the javadoc comments to be turned into docstrings, and if they are too big they can be reduced to their core and the extra help moved to reST docs (which are at this moment in what looks like a good shape: they have the same info as the javadoc comments from a quick glance).

I think some of the comments can just be deleted, like the @see lines.  Finally, a note about the comments for attributes: they should be documented in the reST docs, and for the Python code you have two possibilities: you can document them in the class docstring, or put string literals after them (see http://www.python.org/dev/peps/pep-0258/#attribute-docstrings ? they are discarded by Python, so not available to help/pydoc, but some tools can process them).

----------

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

From report at bugs.python.org  Thu Feb 23 06:37:53 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 23 Feb 2012 05:37:53 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
Message-ID: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>


New submission from Ezio Melotti <ezio.melotti at gmail.com>:

I was reading the "introduction" page of the tutorial [0], and noticed a few things that could be improved:
 1) the first paragraph is a bit confusing, showing a simple example and explaining what the >>> is would be better;
 2) comments can be introduced later too, they are not really necessary at the beginning;
 3) the first example is supposed to introduce numbers and basic operations, but it's still going on with the comments;
 4) the note about floating point issues is not so relevant anymore nowadays, so it could be (re)moved;
 5) "A value can be assigned to several variables simultaneously:" is not technically correct;
 6) "Variables must be ?defined? (assigned a value) before they can be used" this might be improved too;
 7) almost half of the section about numbers goes on explaining complex numbers.  This is totally unnecessary here, I think that mentioning them and maybe showing a simple example is more than enough.  Another option is to make a subsection with a note that says that the section can be skipped;
 8) the examples in this part lack some space (e.g. "a=3.0+4.0j");
 9) the print() function could get a better introduction and used in the first set of string examples;
 10) suggesting to use continuation lines with a trailing \ in string literals is not a good idea, it's better to use """...""" or implicit concatenation inside ();
 11) "Degenerate slice indices are handled gracefully" it might be better to show that it's not the same for "non-slice" indices;
 12) the "About Unicode" section could link to the Unicode HOWTO;
 13) while it's true that lists can contain different types of object, they usually shouldn't;
 14) while the "while" example is good (it first shows a piece of code and then explains what it does), I would introduce the "if" and the "for" first.  The "while" is arguably the most complex and less used of the three statements.

[0]: http://docs.python.org/py3k/tutorial/introduction.html

----------
assignee: docs at python
components: Documentation
messages: 154051
nosy: docs at python, eli.bendersky, eric.araujo, ezio.melotti, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Improve the "introduction" page of the tutorial
type: enhancement
versions: Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Thu Feb 23 09:00:41 2012
From: report at bugs.python.org (patrick vrijlandt)
Date: Thu, 23 Feb 2012 08:00:41 +0000
Subject: [docs] [issue13779] os.walk: bottom-up
In-Reply-To: <1329926477.96.0.0381681228891.issue13779@psf.upfronthosting.co.za>
Message-ID: <CAHRxO8is9ho9T_K4vFTk2BXFnEbzgkXRFjyjdO1J1_KhfsAidw@mail.gmail.com>


patrick vrijlandt <patrick.vrijlandt at gmail.com> added the comment:

Good solution. +1 for closing.

Patrick

----------

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

From tshepang at gmail.com  Thu Feb 23 09:42:57 2012
From: tshepang at gmail.com (Tshepang Lekhonkhobe)
Date: Thu, 23 Feb 2012 10:42:57 +0200
Subject: [docs] Which version of sphinx?
In-Reply-To: <CAPdtAj0npUjx1sBJqiOeT0jDgrercbYJ--06U6bopavbX4b-7Q@mail.gmail.com>
References: <1307058973.29551.2.camel@debian>
	<BANLkTimq78NVBdJzLg=3Jda_yzRUK-N6XQ@mail.gmail.com>
	<1307748473.4373.3.camel@debian>
	<CAPdtAj0npUjx1sBJqiOeT0jDgrercbYJ--06U6bopavbX4b-7Q@mail.gmail.com>
Message-ID: <CAA77j2AkG0O1vLdFAfGhb78hahgGcWKX8ENz9gws98haRHFmgQ@mail.gmail.com>

On Thu, Aug 18, 2011 at 14:45, Sandro Tosi <sandro.tosi at gmail.com> wrote:
> On Sat, Jun 11, 2011 at 01:27, Tshepang Lekhonkhobe <tshepang at gmail.com> wrote:
>> On Fri, 2011-06-10 at 20:40 +0000, Sandro Tosi wrote:
>>> Hello Tshepang,
>>>
>>> On Thu, Jun 2, 2011 at 23:56, Tshepang Lekhonkhobe <tshepang at gmail.com> wrote:
>>> > Hi,
>>> >
>>> > Is there any reason Sphinx version was specified here:
>>> > http://docs.python.org/dev/documenting/building.html?
>>>
>>> I don't have that clear your question. Are you asking why the version
>>> is explict in this command:
>>>
>>> svn co http://svn.python.org/projects/external/Sphinx-0.6.5/sphinx tools/sphinx
>>>
>>> or in some other place? can you please be a bit more specific (either
>>> in what you think is wrong and how you'd fix it)?
>>
>> Sorry for not being too clear. I meant, why is that specific version
>> required? Why doesn't the link just point to trunk (or tip, in Mercurial
>> speak)?
>
> I can think mainly two reason:
>
> - stability: if everyone is building the docs from sphinx tip (and all
> other third-party tool) you'll get a mess where for some people the
> change works and for others doesn't. Having "written in stone" what's
> the version to use, avoid this ambiguity.

Indeed. Version 1.0.8 (as packaged in Debian) actually breaks the
build. I prepared a whole patch to fix the issues, only to discover
that the version specified there (0.6.5) had no issues. I will attach
the patch here, one that makes the documentation to build with version
1.0.8, just in case.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-directive-errors.patch
Type: text/x-patch
Size: 4166 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/docs/attachments/20120223/21928df3/attachment.bin>

From tshepang at gmail.com  Thu Feb 23 15:48:11 2012
From: tshepang at gmail.com (Tshepang Lekhonkhobe)
Date: Thu, 23 Feb 2012 16:48:11 +0200
Subject: [docs] Which version of sphinx?
In-Reply-To: <CAA77j2AkG0O1vLdFAfGhb78hahgGcWKX8ENz9gws98haRHFmgQ@mail.gmail.com>
References: <1307058973.29551.2.camel@debian>
	<BANLkTimq78NVBdJzLg=3Jda_yzRUK-N6XQ@mail.gmail.com>
	<1307748473.4373.3.camel@debian>
	<CAPdtAj0npUjx1sBJqiOeT0jDgrercbYJ--06U6bopavbX4b-7Q@mail.gmail.com>
	<CAA77j2AkG0O1vLdFAfGhb78hahgGcWKX8ENz9gws98haRHFmgQ@mail.gmail.com>
Message-ID: <CAA77j2AJFj4ihknGJTDJ5rHUDTmtOuToJqGVGo=+xtG7x2u1PQ@mail.gmail.com>

On Thu, Feb 23, 2012 at 10:42, Tshepang Lekhonkhobe <tshepang at gmail.com> wrote:
> On Thu, Aug 18, 2011 at 14:45, Sandro Tosi <sandro.tosi at gmail.com> wrote:
>> On Sat, Jun 11, 2011 at 01:27, Tshepang Lekhonkhobe <tshepang at gmail.com> wrote:
>>> On Fri, 2011-06-10 at 20:40 +0000, Sandro Tosi wrote:
>>>> Hello Tshepang,
>>>>
>>>> On Thu, Jun 2, 2011 at 23:56, Tshepang Lekhonkhobe <tshepang at gmail.com> wrote:
>>>> > Hi,
>>>> >
>>>> > Is there any reason Sphinx version was specified here:
>>>> > http://docs.python.org/dev/documenting/building.html?
>>>>
>>>> I don't have that clear your question. Are you asking why the version
>>>> is explict in this command:
>>>>
>>>> svn co http://svn.python.org/projects/external/Sphinx-0.6.5/sphinx tools/sphinx
>>>>
>>>> or in some other place? can you please be a bit more specific (either
>>>> in what you think is wrong and how you'd fix it)?
>>>
>>> Sorry for not being too clear. I meant, why is that specific version
>>> required? Why doesn't the link just point to trunk (or tip, in Mercurial
>>> speak)?
>>
>> I can think mainly two reason:
>>
>> - stability: if everyone is building the docs from sphinx tip (and all
>> other third-party tool) you'll get a mess where for some people the
>> change works and for others doesn't. Having "written in stone" what's
>> the version to use, avoid this ambiguity.
>
> Indeed. Version 1.0.8 (as packaged in Debian) actually breaks the
> build. I prepared a whole patch to fix the issues, only to discover
> that the version specified there (0.6.5) had no issues. I will attach
> the patch here, one that makes the documentation to build with version
> 1.0.8, just in case.

Okay, the docs are outdated. Running "cd Doc && make html" pulls and
uses Sphinx 1.0.7.

From report at bugs.python.org  Thu Feb 23 15:58:10 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Thu, 23 Feb 2012 14:58:10 +0000
Subject: [docs] [issue14100] expose a note a hidden note
Message-ID: <1330009090.66.0.133471342458.issue14100@psf.upfronthosting.co.za>


New submission from Tshepang Lekhonkhobe <tshepang at gmail.com>:

I wonder if this note was hidden deliberately.

----------
assignee: docs at python
components: Documentation
files: make-note-visible.patch
keywords: patch
messages: 154065
nosy: docs at python, tshepang
priority: normal
severity: normal
status: open
title: expose a note a hidden note
versions: Python 3.3
Added file: http://bugs.python.org/file24612/make-note-visible.patch

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

From report at bugs.python.org  Thu Feb 23 16:01:37 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 23 Feb 2012 15:01:37 +0000
Subject: [docs] [issue14100] expose a note a hidden note
In-Reply-To: <1330009090.66.0.133471342458.issue14100@psf.upfronthosting.co.za>
Message-ID: <1330009297.77.0.330304087154.issue14100@psf.upfronthosting.co.za>


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


----------
nosy: +haypo, pitrou
stage:  -> patch review
type:  -> enhancement

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

From report at bugs.python.org  Thu Feb 23 16:30:23 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Thu, 23 Feb 2012 15:30:23 +0000
Subject: [docs] [issue14100] expose a hidden note
In-Reply-To: <1330009090.66.0.133471342458.issue14100@psf.upfronthosting.co.za>
Message-ID: <1330011023.29.0.777758761036.issue14100@psf.upfronthosting.co.za>


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


----------
title: expose a note a hidden note -> expose a hidden note

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

From report at bugs.python.org  Thu Feb 23 16:45:34 2012
From: report at bugs.python.org (Antoine Pitrou)
Date: Thu, 23 Feb 2012 15:45:34 +0000
Subject: [docs] [issue14100] expose a hidden note
In-Reply-To: <1330009090.66.0.133471342458.issue14100@psf.upfronthosting.co.za>
Message-ID: <1330011934.26.0.466334584886.issue14100@psf.upfronthosting.co.za>


Antoine Pitrou <pitrou at free.fr> added the comment:

Well, presumably the XXX tells you why it's hidden.

----------
nosy: +loewis

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

From report at bugs.python.org  Thu Feb 23 21:07:13 2012
From: report at bugs.python.org (Zbyszek Szmek)
Date: Thu, 23 Feb 2012 20:07:13 +0000
Subject: [docs] [issue14101] example function in tertools.count is
	misindented
Message-ID: <1330027633.46.0.670191761588.issue14101@psf.upfronthosting.co.za>


New submission from Zbyszek Szmek <zbyszek at in.waw.pl>:

Indentation is broken.

diff --git a/Modules/itertoolsmodule.c b/Modules/itertoolsmodule.c
--- a/Modules/itertoolsmodule.c
+++ b/Modules/itertoolsmodule.c
@@ -3221,10 +3221,10 @@
 Return a count object whose .__next__() method returns consecutive values.\n\
 Equivalent to:\n\n\
     def count(firstval=0, step=1):\n\
-    x = firstval\n\
-    while 1:\n\
-        yield x\n\
-        x += step\n");
+        x = firstval\n\
+        while 1:\n\
+            yield x\n\
+            x += step\n");

----------
assignee: docs at python
components: Documentation, Library (Lib)
files: itertools-count-indentation.diff
keywords: patch
messages: 154084
nosy: docs at python, zbysz
priority: normal
severity: normal
status: open
title: example function in tertools.count is misindented
type: enhancement
versions: Python 3.3
Added file: http://bugs.python.org/file24618/itertools-count-indentation.diff

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

From report at bugs.python.org  Thu Feb 23 22:29:33 2012
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 23 Feb 2012 21:29:33 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330032573.74.0.502519603795.issue14097@psf.upfronthosting.co.za>


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

some of theses are great suggestions.  I'll do an update shortly.

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

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

From report at bugs.python.org  Fri Feb 24 05:39:05 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 24 Feb 2012 04:39:05 +0000
Subject: [docs] [issue14100] Add a missing info to PEP 393 + link from
	whatsnew 3.3
In-Reply-To: <1330009090.66.0.133471342458.issue14100@psf.upfronthosting.co.za>
Message-ID: <1330058345.81.0.480736464064.issue14100@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Agreed with Antoine.  If you want, you can make a patch for the PEPs repo with the info requested by the XXX note, then a patch to replace that note by a link to the PEP, unless Martin wanted to do that himself.

----------
nosy: +eric.araujo
title: expose a hidden note -> Add a missing info to PEP 393 + link from whatsnew 3.3

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

From report at bugs.python.org  Fri Feb 24 05:43:26 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 24 Feb 2012 04:43:26 +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: <1330058606.81.0.779648873521.issue14101@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Patch LGTM.  Raymond, any objection?

----------
components: +Extension Modules -Documentation, Library (Lib)
nosy: +eric.araujo, rhettinger
stage:  -> patch review
title: example function in tertools.count is misindented -> example function in tertools.count docstring is misindented
versions: +Python 2.7, Python 3.2

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

From report at bugs.python.org  Fri Feb 24 08:00:46 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 24 Feb 2012 07:00:46 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330066846.32.0.484628336409.issue14097@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

The attached patch addresses 8) -- you might want to use it as a starting point (that's what I was going to fix before deciding to do a full review of the page).

----------
assignee: rhettinger -> docs at python
keywords: +patch
Added file: http://bugs.python.org/file24622/issue14097.diff

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

From report at bugs.python.org  Fri Feb 24 08:13:50 2012
From: report at bugs.python.org (Raymond Hettinger)
Date: Fri, 24 Feb 2012 07:13:50 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330067630.14.0.699634246853.issue14097@psf.upfronthosting.co.za>


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

Thanks.

----------

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

From report at bugs.python.org  Fri Feb 24 10:23:07 2012
From: report at bugs.python.org (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Fri, 24 Feb 2012 09:23:07 +0000
Subject: [docs] [issue14100] Add a missing info to PEP 393 + link from
	whatsnew 3.3
In-Reply-To: <1330009090.66.0.133471342458.issue14100@psf.upfronthosting.co.za>
Message-ID: <1330075387.21.0.0270703440277.issue14100@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

I'll look into this shortly.

----------

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

From report at bugs.python.org  Fri Feb 24 12:07:56 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 24 Feb 2012 11:07:56 +0000
Subject: [docs] [issue9056] Adding additional level of bookmarks and section
	numbers	in python pdf documents.
In-Reply-To: <1277175637.31.0.472126376822.issue9056@psf.upfronthosting.co.za>
Message-ID: <1330081676.41.0.878937631004.issue9056@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Feb 24 20:50:05 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Fri, 24 Feb 2012 19:50:05 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
	without	explanation
Message-ID: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>


New submission from Tshepang Lekhonkhobe <tshepang at gmail.com>:

Relevant line: http://hg.python.org/cpython/file/e2eccc906354/Doc/tutorial/introduction.rst#l487

When the concept is introduced, it appears like there's an assumption that the reader would know what it means. I'm curious if it's that common a term that it should be taken for granted, or if it deserves a definition.

----------
assignee: docs at python
components: Documentation
messages: 154151
nosy: docs at python, tshepang
priority: normal
severity: normal
status: open
title: tutorial intro talks of "shallow copy" concept without explanation
versions: Python 3.3

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

From report at bugs.python.org  Fri Feb 24 20:58:49 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Fri, 24 Feb 2012 19:58:49 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330113529.39.0.425752120405.issue14097@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/issue14097>
_______________________________________

From report at bugs.python.org  Fri Feb 24 21:30:09 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Fri, 24 Feb 2012 20:30:09 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330115409.43.0.974912214476.issue14097@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

Ezio, your fix for 8 is definitely good. Space makes it cleaner, as well as compliant to PEP 8, which explicitly recommends to surround operators with spaces.

Note, however, that this should be applied in other places as well, not only the complex number samples. For example:

2+2
(50-5*6)/4

etc.

There's quite a bit of inconsistency in the samples. Some surround operators with spaces and some don't. I think converging on a single consistent, PEP 8 compliant convention of surrounding with spaces always throughout the tutorial is a good idea.

----------

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

From report at bugs.python.org  Fri Feb 24 21:45:39 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Fri, 24 Feb 2012 20:45:39 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330116339.58.0.00811288041895.issue14097@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

Comments on some of the suggestions:

1) Agreed
2) Can be combined with (3), I think. Just show the number example with the explanatory comments. They speak for themselves. No need for the SPAM and STRING assignments.
5) Yep. Can be replaced by "A value can be assigned to several variables in a single statement"
6) There's the tradeoff of rigor vs. simplicity here, since this is still a tutorial for beginners, right? What alternative would you propose?
7) Totally agree. I don't think complex numbers deserve more than a single trivial example and one sentence dedicated to them in the tutorial, if that...
8) Yes. See my previous message in this issue
9) "It differs from just writing the expression you want to write" is definitely confusing
10) Agree
11) This is kind-of mentioned later in the negative index part. It may be worth mentioning that a single index must be within bounds, but the explanation on degenerate slices has its place too, since it's a friendly feature of Python many rely on.
12) Agree
13) This is probably too arguable to be included. With Python's duck typing there *is* sometimes place for placing different objects in the same list, with the understanding that they all have some common behavior (for example, callables).
14) Agree

----------

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

From report at bugs.python.org  Sat Feb 25 01:15:25 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 25 Feb 2012 00:15:25 +0000
Subject: [docs] [issue14049] execfile() fails on files that use global
	variables	inside functions
In-Reply-To: <1329569998.87.0.931536345344.issue14049@psf.upfronthosting.co.za>
Message-ID: <1330128925.46.0.887599529886.issue14049@psf.upfronthosting.co.za>


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

Searching on 'exec NameError' shows that this issue is a duplicate of (behavior issue) #1167300 which contained an essentially identical example"

>>> exec """\
... x = 3
... def f():
...     print x
... f()
... """ in {}, {}

#1167300 was closed as a duplicate of (behavior issue) #991196, which in turn was closed as 'won't fix' (ie, works as it must). Doc issue #4831, which resulted in some doc changes, seems related to this but is not the same. I believe this issue is a duplicate of #13557, which has a patch. I will add my proposed change there.

Anyway, my comments:

In 3.2.2, this runs

#prog='''\
x = 1
def weird():
    y = x + 1
    return y
print(weird())
#'''
#exec(prog)

The same uncommented does also, as does adding ',{}' to the call.
Adding ',{},{}' gives the NameError.
With one named {} arg passed twice, as follows, it runs.

d = {}
exec(prog, d, d)

The reasons for these results are:
1. assignments are *always* to the local namespace.
2. normally, for module code, the local and global namespaces are the same.
3. in the example, 'x=1' is the same as "values['x']=1", while within the function, 'y=x+1' looks up x in gvalues.

This is the same explanation as given in #1167300.

----------
nosy: +terry.reedy
resolution:  -> duplicate
status: open -> closed
superseder:  -> exec of list comprehension fails on NameError
versions: +Python 3.2, Python 3.3

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

From report at bugs.python.org  Sat Feb 25 01:18:07 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 25 Feb 2012 00:18:07 +0000
Subject: [docs] [issue13557] exec of list comprehension fails on NameError
In-Reply-To: <1323375954.63.0.637699438673.issue13557@psf.upfronthosting.co.za>
Message-ID: <1330129086.92.0.703470700926.issue13557@psf.upfronthosting.co.za>


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

Issues like this, about exec, have come up multiple times. I just closed #14049 as a duplicate of this, and listed there some other issues. So I think that the doc for exec (and execfile in 2.7) could be better still. I would like to see something like the following added, whether instead of or in addition to the current proposal -- perhaps after "If provided, locals can be any mapping object." (quote from the 3.2 exec entry)

"At module level, globals and locals are the same dictionary. If one passes two separate objects as globals and locals, the code will be executed as if it were embedded in a class definition."

To me, this is friendlier and less intimidating than 'free variable' and the Execution model doc chapter. It summarizes the essential problem with such exec calls.

To illustrate, the following gives the same NameError. and for the same reason, as exec(code,{},{}), where code is the quoted unindented version with the class line deleted.

class x:
    x = 1
    def incx():
        return x+1
    print(incx())

----------
nosy: +terry.reedy
versions: +Python 2.7, Python 3.2

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

From report at bugs.python.org  Sat Feb 25 06:30:19 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 25 Feb 2012 05:30:19 +0000
Subject: [docs] [issue13557] exec of list comprehension fails on NameError
In-Reply-To: <1323375954.63.0.637699438673.issue13557@psf.upfronthosting.co.za>
Message-ID: <1330147818.97.0.474019400685.issue13557@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Stefan: This fell off my radar, sorry I haven?t reviewed your patch yet.

Terry: +1

----------

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

From report at bugs.python.org  Sat Feb 25 07:59:45 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 25 Feb 2012 06:59:45 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330153185.28.0.026728652164.issue14097@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Be careful with whitespace changes.  Sometimes not putting whitespace around an operator helps to see the grouping of operations, for example.  The important thing is ?Readability counts?, not ?Always put whitespace around operators?.  A huge part of understanding PEP 8 is to know when not to follow PEP 8 (PEP 20 is not called a Zen for no reason :)

About 5)-6): I really wish the docs wouldn?t use the term ?variable?, which means something else in most other programming languages and always cause beginners to stumble upon unexpected-for-them binding behavior.

A remark that?s probably culture-dependent: ?degenerate? nearly sounds like a racist insult to me (see 11).

----------

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

From report at bugs.python.org  Sat Feb 25 08:04:20 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 25 Feb 2012 07:04:20 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <1330153460.02.0.793070993256.issue13491@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Here?s a patch for 2.7.  I haven?t changed the text_factory example.

The second patch is for 3.2 and contains a few additional changes that I did in my first patch.

----------
Added file: http://bugs.python.org/file24634/sqlite-doc-tweaks-2.7.diff

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

From report at bugs.python.org  Sat Feb 25 08:04:28 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 25 Feb 2012 07:04:28 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <1330153468.32.0.855282525845.issue13491@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


Added file: http://bugs.python.org/file24635/sqlite-doc-tweaks-3.2.diff

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

From report at bugs.python.org  Sat Feb 25 08:35:36 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 25 Feb 2012 07:35:36 +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: <1330155336.29.0.86229641689.issue14112@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I think it?s a common English term (i.e. ?shallow water? to describe a small lake-like thing where you can go without swimming), but non-native speakers may not know it (I don?t remember if I knew it before learning Python, for example).

What about this:

 All slice operations return a new list containing the requested elements.  This
-means that the following slice returns a shallow copy of the list *a*::
+means that the following slice returns a shallow copy (see the documentation of
+the :mod:`copy` module for a definition) of the list *a*::

(BTW, you can use syntax like Doc/tutorial/introduction.rst:487 to have links generated; see http://docs.python.org/devguide/triaging#generating-special-links-in-a-comment ?also linked from the ?Comment? label in the form, but it isn?t obvious that it?s a link).

----------
nosy: +eric.araujo, ezio.melotti, terry.reedy
versions: +Python 2.7, Python 3.2

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

From report at bugs.python.org  Sat Feb 25 09:00:18 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 25 Feb 2012 08:00:18 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330156818.65.0.362712962932.issue14097@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

> Be careful with whitespace changes.

Here I agree with you and disagree with the PEP 8 (specifically where it says that "hypot2 = x*x + y*y" and "c = (a+b) * (a-b)" are "wrong").

In
-   >>> 3+1j*3
+   >>> 3 + 1j * 3
I intentionally added spaces around all the operators to leave the expression ambiguous.  IIUC the point of that example is to show that even if 3+1j is a single entity, normal precedence rules still apply, so I didn't want the reader to make any assumptions about the precedence based on the whitespace (or even worse thing that the whitespace might define the precedence).

Additional comments and replies about the list:
 1) A user was confused about >>>, thought that was necessary to "define variables", that you had to always include it in your code.  The tutorial should make clear that this is used only in the interactive interpreter and not in regular code;
 2-3) what Eli said sounds good to me;
 5) "A value can be assigned to several variables simultaneously:" might lead to thing that "a = b = []" is the same as "a = []; b= []".  The term "variable" has a different meaning in other languages, but that doesn't mean we should refrain to use it -- we just have to specify what we mean with "variable" (this can be done later, saying that "both a and b will refer to the same list" should be enough here);
 6) here the idea is that is not the value to be assigned to the variable (like in C where the vars are like boxes and you can put values inside), but the variable that is used to refer to the object (so it's more like a label assigned to the object).  Again we can don't need to be too specific here yet, but we shouldn't say wrong things either.  See also http://python.net/crew/mwh/hacks/objectthink.html;
 11) presenting the error raised with the index first and the fact that slices are more "permissive" later sounds better to me;
 13) I'm not saying we should specifically tell users to put object of the same kind in a list, but just to avoid focusing on this aspect and use "realistic" examples.  Adding a note at the end saying that "lists can also contain objects of different types" should be enough;

----------

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

From report at bugs.python.org  Sat Feb 25 09:09:40 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 25 Feb 2012 08:09:40 +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: <1330157380.77.0.852681869193.issue14112@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Even if they know the meaning of "shallow" (which is not a really common word AFAICT), they might not know what it means in this context.

Adding an entry to glossary might be a better solution.

In this context I think the best solution would be to actually show the implication of having a shallow copy with another short example (hijacking the reader to some other page where they can find some in-depth description of what "shallow" might do more harm than good).

----------

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

From report at bugs.python.org  Sat Feb 25 10:18:30 2012
From: report at bugs.python.org (Tim Golden)
Date: Sat, 25 Feb 2012 09:18:30 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
	without	explanation
In-Reply-To: <1330157380.77.0.852681869193.issue14112@psf.upfronthosting.co.za>
Message-ID: <4F48A758.2010102@timgolden.me.uk>


Tim Golden <mail at timgolden.me.uk> added the comment:

On 25/02/2012 08:09, Ezio Melotti wrote:
> Even if they know the meaning of "shallow" (which is not a really common word AFAICT)

FWIW it's pretty much the only way of saying what it means.
I've no idea how many people used it last year or anything,
but if I needed to express the concept of the opposite of
deep I would struggle to find another word. Except, perhaps,
the doublespeak-like "not deep". Undeep? Double-plus undeep?

----------
nosy: +tim.golden

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

From report at bugs.python.org  Sat Feb 25 10:20:55 2012
From: report at bugs.python.org (Ramchandra Apte)
Date: Sat, 25 Feb 2012 09:20:55 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
	without	explanation
In-Reply-To: <1330113005.05.0.0872009811322.issue14112@psf.upfronthosting.co.za>
Message-ID: <1330161655.2.0.376542446905.issue14112@psf.upfronthosting.co.za>


Ramchandra Apte <maniandram01 at gmail.com> added the comment:

+1 for ?ric Araujo's idea.

----------
nosy: +ramchandra.apte

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

From report at bugs.python.org  Sat Feb 25 10:51:25 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Sat, 25 Feb 2012 09:51:25 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
	without	explanation
In-Reply-To: <1330155336.29.0.86229641689.issue14112@psf.upfronthosting.co.za>
Message-ID: <CAA77j2AE1ZMGuU3Bo_iVCL2R_puMrvq7-Z4gft7vza6zY7MYBA@mail.gmail.com>


Tshepang Lekhonkhobe <tshepang at gmail.com> added the comment:

On Sat, Feb 25, 2012 at 09:35, ?ric Araujo <report at bugs.python.org> wrote:
> What about this:
>
> ?All slice operations return a new list containing the requested elements. ?This
> -means that the following slice returns a shallow copy of the list *a*::
> +means that the following slice returns a shallow copy (see the documentation of
> +the :mod:`copy` module for a definition) of the list *a*::

That's kool, though I like Ezio's idea of putting it on a glossary
(and then linking to it) even more.

> (BTW, you can use syntax like Doc/tutorial/introduction.rst:487 to have links generated; see http://docs.python.org/devguide/triaging#generating-special-links-in-a-comment ?also linked from the ?Comment? label in the form, but it isn?t obvious that it?s a link).

Thanks for the pointer. Note however that I chose my approach because
it shows the info at a specific revision, in case the content changes
later on.

----------

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

From report at bugs.python.org  Sat Feb 25 10:54:36 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 25 Feb 2012 09:54:36 +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: <1330163676.52.0.0512165248649.issue14112@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

> FWIW it's pretty much the only way of saying what it means.

However, even using "not deep" here would still be ambiguous.  What's a deep copy?  What's a non-deep copy?
Using "shallow" might be a problem, but the real problem is that regardless of the wording, the reader might not know what this is all about.

----------

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

From pdemcenko at hotmail.com  Fri Feb 24 20:49:09 2012
From: pdemcenko at hotmail.com (Peter Demchenko)
Date: Fri, 24 Feb 2012 22:49:09 +0300
Subject: [docs] Bug?
Message-ID: <BLU144-W116FBE59DB7953B968D244BF6A0@phx.gbl>



Hi,May be I miss something, but look...Why the script:----------------x="ab"  'cde'print(len(x))----------------
 - responds with 2?Whitespaces after "ab" can be or no - result is the same: 2It's rather dangerous situation, since the next line 'cde' produces no compilation errors, so you'll get string x stripped!!!  An excerpt from manual: "2.4.2. String literal concatenationMultiple adjacent string literals (delimited by whitespace), possibly using different quoting conventions, are allowed, and their meaning is the same as their concatenation. Thus, "hello" 'world' is equivalent to "helloworld". This feature can be used to reduce the number of backslashes needed, to split long strings conveniently across long lines, ..."
Ok. Now look at another excerpt from the same man:!!  "string.whitespace A string containing all characters that are considered whitespace. On most systems this includes the characters space, tab, linefeed, return, formfeed, and vertical tab"As you see there are no other chars between <x="ab">  and  <'cde'> - whitespaces only!    I have Phyton 2.7.2 and WindowsXP host
Best regards,
Peter 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120224/ef8afc09/attachment.html>

From report at bugs.python.org  Sat Feb 25 13:59:51 2012
From: report at bugs.python.org (Petri Lehtinen)
Date: Sat, 25 Feb 2012 12:59:51 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <1330174791.0.0.52448599369.issue13491@psf.upfronthosting.co.za>


Petri Lehtinen <petri at digip.org> added the comment:

Both patches look good to me. The text_factory example is OK on 2.7 because the OptimizedUnicode flag works correctly there.

----------

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

From report at bugs.python.org  Sat Feb 25 15:41:07 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 25 Feb 2012 14:41:07 +0000
Subject: [docs] [issue13491] Fixes for sqlite3 doc
In-Reply-To: <1322390027.54.0.855055968281.issue13491@psf.upfronthosting.co.za>
Message-ID: <1330180867.42.0.261008915507.issue13491@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
assignee: docs at python -> petri.lehtinen

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

From report at bugs.python.org  Sat Feb 25 15:57:18 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sat, 25 Feb 2012 14:57:18 +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: <1330181838.48.0.151165691339.issue14112@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

A link to a glossary may be better than a link to the top of the copy module.  I wonder if we could use glossary markup in the copy module docs instead of adding terms to the global glossary.

Tim: I like ?undeep?, it?s used to describe a geographical feature of a river in The Lord of the Rings.

----------

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

From report at bugs.python.org  Sat Feb 25 18:29:07 2012
From: report at bugs.python.org (=?utf-8?q?F=C3=A9lix-Antoine_Fortin?=)
Date: Sat, 25 Feb 2012 17:29:07 +0000
Subject: [docs] [issue14122] operator: div() instead of truediv() in
	documention	since 3.1.2
Message-ID: <1330190947.0.0.577940760696.issue14122@psf.upfronthosting.co.za>


New submission from F?lix-Antoine Fortin <felixantoinefortin+python at gmail.com>:

A small regression was introduced by the changeset 57209 in the documentation of the operator module.

In the abstract operations table in section 9.3.1 the first of two lines
on Division, the associated function should be : truediv() instead of div(), since operator.div() no longer exists in Python 3. In changeset 57209, this corresponds to the line 408 of the file Doc/library/operator.rst.

I have included the patch for the changeset 57209.

----------
assignee: docs at python
components: Documentation
files: operator_div.patch
keywords: patch
messages: 154277
nosy: docs at python, felixantoinefortin
priority: normal
severity: normal
status: open
title: operator: div() instead of truediv() in documention since 3.1.2
versions: Python 3.1, Python 3.2, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file24639/operator_div.patch

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

From report at bugs.python.org  Sat Feb 25 18:51:41 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 25 Feb 2012 17:51:41 +0000
Subject: [docs] [issue14122] operator: div() instead of truediv() in
	documention	since 3.1.2
In-Reply-To: <1330190947.0.0.577940760696.issue14122@psf.upfronthosting.co.za>
Message-ID: <1330192301.9.0.941122675048.issue14122@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
stage:  -> patch review
type:  -> enhancement
versions:  -Python 3.1, Python 3.4

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

From report at bugs.python.org  Sat Feb 25 19:41:24 2012
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 25 Feb 2012 18:41:24 +0000
Subject: [docs] [issue13999] Queue references in multiprocessing doc points
	to Queue	module and not to self
In-Reply-To: <1329072364.23.0.444581618774.issue13999@psf.upfronthosting.co.za>
Message-ID: <E1S1MYb-0003RV-Ta@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 5d4f2f994f75 by Sandro Tosi in branch '2.7':
Issue #13999: refer to multiprocessing.Queue when needed
http://hg.python.org/cpython/rev/5d4f2f994f75

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

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

From report at bugs.python.org  Sat Feb 25 19:41:53 2012
From: report at bugs.python.org (Sandro Tosi)
Date: Sat, 25 Feb 2012 18:41:53 +0000
Subject: [docs] [issue13999] Queue references in multiprocessing doc points
	to Queue	module and not to self
In-Reply-To: <1329072364.23.0.444581618774.issue13999@psf.upfronthosting.co.za>
Message-ID: <1330195313.15.0.559634672128.issue13999@psf.upfronthosting.co.za>


Changes by Sandro Tosi <sandro.tosi at gmail.com>:


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

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

From report at bugs.python.org  Sat Feb 25 21:48:49 2012
From: report at bugs.python.org (Christine Jones)
Date: Sat, 25 Feb 2012 20:48:49 +0000
Subject: [docs] [issue14123] Doc change re old and new string formatting
Message-ID: <1330202928.96.0.727285588049.issue14123@psf.upfronthosting.co.za>


New submission from Christine Jones <silly.english.knights at gmail.com>:

Change to this http://docs.python.org/py3k/library/stdtypes.html as suggested by Nick Coghlan here http://www.gossamer-threads.com/lists/python/dev/969817

"The formatting operations described here are modelled on C's printf()
syntax. They only support formatting of certain builtin types, and the
use of a binary operator means that care may be needed in order to
format tuples and dictionaries correctly. As the new string formatting
syntax is more powerful, flexible, extensible and handles tuples and
dictionaries naturally, it is recommended for new code. However, there
are no current plans to deprecate printf-style formatting."

----------
assignee: docs at python
components: Documentation
messages: 154283
nosy: docs at python, telephonebook
priority: normal
severity: normal
status: open
title: Doc change re old and new string formatting

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

From report at bugs.python.org  Sat Feb 25 21:56:03 2012
From: report at bugs.python.org (Merlijn van Deen)
Date: Sat, 25 Feb 2012 20:56:03 +0000
Subject: [docs] [issue14124] _pickle.c comment/documentation improvement
Message-ID: <1330203362.98.0.289163571674.issue14124@psf.upfronthosting.co.za>


New submission from Merlijn van Deen <valhallasw at gmail.com>:

As suggested by loewis in msg154233, I created some documentation to help people get started with _pickle.c.

----------
assignee: docs at python
components: Documentation, Extension Modules
files: _pickle_c_doc.diff
keywords: patch
messages: 154284
nosy: docs at python, valhallasw
priority: normal
severity: normal
status: open
title: _pickle.c comment/documentation improvement
type: enhancement
versions: Python 3.3
Added file: http://bugs.python.org/file24641/_pickle_c_doc.diff

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

From report at bugs.python.org  Sat Feb 25 21:56:39 2012
From: report at bugs.python.org (Merlijn van Deen)
Date: Sat, 25 Feb 2012 20:56:39 +0000
Subject: [docs] [issue14124] _pickle.c comment/documentation improvement
In-Reply-To: <1330203362.98.0.289163571674.issue14124@psf.upfronthosting.co.za>
Message-ID: <1330203399.82.0.466698889478.issue14124@psf.upfronthosting.co.za>


Changes by Merlijn van Deen <valhallasw at gmail.com>:


----------
nosy: +loewis

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

From report at bugs.python.org  Sat Feb 25 22:04:24 2012
From: report at bugs.python.org (Eric V. Smith)
Date: Sat, 25 Feb 2012 21:04:24 +0000
Subject: [docs] [issue14123] Doc change re old and new string formatting
In-Reply-To: <1330202928.96.0.727285588049.issue14123@psf.upfronthosting.co.za>
Message-ID: <1330203864.92.0.529854188273.issue14123@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Feb 25 22:09:41 2012
From: report at bugs.python.org (Glenn Linderman)
Date: Sat, 25 Feb 2012 21:09:41 +0000
Subject: [docs] [issue14123] Doc change re old and new string formatting
In-Reply-To: <1330202928.96.0.727285588049.issue14123@psf.upfronthosting.co.za>
Message-ID: <1330204181.27.0.487875136643.issue14123@psf.upfronthosting.co.za>


Changes by Glenn Linderman <v+python at g.nevcal.com>:


----------
nosy: +v+python

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

From report at bugs.python.org  Sat Feb 25 23:11:24 2012
From: report at bugs.python.org (Ned Deily)
Date: Sat, 25 Feb 2012 22:11:24 +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: <1330207884.28.0.757357127524.issue14112@psf.upfronthosting.co.za>


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

"shallow copy" and "deep copy" are both standard computer science terms by no means unique to or invented by Python.  We should be cautious about documentation bloat and trying to redefine standard terms.

http://en.wikipedia.org/wiki/Object_copy#Shallow_copy

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

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

From report at bugs.python.org  Sun Feb 26 00:49:46 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Sat, 25 Feb 2012 23:49:46 +0000
Subject: [docs] [issue14123] Doc change re old and new string formatting
In-Reply-To: <1330202928.96.0.727285588049.issue14123@psf.upfronthosting.co.za>
Message-ID: <1330213786.1.0.988766597133.issue14123@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/issue14123>
_______________________________________

From report at bugs.python.org  Sun Feb 26 01:02:10 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Sun, 26 Feb 2012 00:02:10 +0000
Subject: [docs] [issue14112] tutorial intro talks of "shallow copy" concept
	without	explanation
In-Reply-To: <1330207884.28.0.757357127524.issue14112@psf.upfronthosting.co.za>
Message-ID: <CAA77j2CpdqJCfp3aDPpEB5f6tZ6h5w1ktGamTkMQHJ8qcOK-Dw@mail.gmail.com>


Tshepang Lekhonkhobe <tshepang at gmail.com> added the comment:

On Sun, Feb 26, 2012 at 00:11, Ned Deily <report at bugs.python.org> wrote:
> "shallow copy" and "deep copy" are both standard computer science terms by no means unique to or invented by Python. ?We should be cautious about documentation bloat and trying to redefine standard terms.
>
> http://en.wikipedia.org/wiki/Object_copy#Shallow_copy

Do they mean exactly the same thing in Python as what Wikipedia says?
In that case, are links to Wikipedia allowed?

Anyways, some explanation (or link) would be needed since many people
without a background in computer science are going to read the
tutorial. I think the term is not common enough that it can be taken
for granted that newbies to Python (readers of the tutorial) will know
it.

----------

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

From report at bugs.python.org  Sun Feb 26 01:03:53 2012
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Sun, 26 Feb 2012 00:03:53 +0000
Subject: [docs] [issue14123] Indicate that there are no current plans to
	deprecate	printf-style formatting
In-Reply-To: <1330202928.96.0.727285588049.issue14123@psf.upfronthosting.co.za>
Message-ID: <1330214633.6.0.227070475176.issue14123@psf.upfronthosting.co.za>


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


----------
title: Doc change re old and new string formatting -> Indicate that there are no current plans to deprecate printf-style formatting

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

From report at bugs.python.org  Sun Feb 26 01:12:04 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 26 Feb 2012 00:12:04 +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: <1330215124.9.0.232389966166.issue14112@psf.upfronthosting.co.za>


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

'Shallow' is a common English word: "Stay in shallow water until you learn to swim!" But that is not the issue here.

I think the underlying issue is that the first sentence "All slice operations return a new list containing the requested elements." is wrong. Python lists, like shopping lists, do not 'contain' objects. Both contain references to objects (copies of their identifieres) and thereby define an abstract collection. A shallow copy of a collection object copies references (ids). A deep copy also copies objects themselves. (The Wikipedia article says much the same, but to me much less clearly.) 

If we start with a true sentence "Slice operations return a new list containing references to a subsequence of the original elements." or "Slice operations return a new list that defines a subsequence of the original sequence of objects", then I do not think more *needs* to be said. We could optionally add "Since no objects are copied, slices are shallow copies." both to emphasize that no objects are copied and to introduced the notion of shallow copy.

----------

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

From report at bugs.python.org  Sun Feb 26 03:07:58 2012
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 26 Feb 2012 02:07:58 +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: <1330222078.03.0.703239054724.issue14112@psf.upfronthosting.co.za>


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

FWIW, the shallow/deep terminology is not unique to Python and is commonly used in computer science.

In my experience teaching Python, the terms are somewhat self-descriptive and only become perplexing when someone over-explains them.

That said, a glossary entry is appropriate.

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

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

From report at bugs.python.org  Sun Feb 26 03:34:48 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 26 Feb 2012 02:34:48 +0000
Subject: [docs] [issue14123] Indicate that there are no current plans to
	deprecate	printf-style formatting
In-Reply-To: <1330202928.96.0.727285588049.issue14123@psf.upfronthosting.co.za>
Message-ID: <1330223687.71.0.839921136201.issue14123@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

I?d like to make a patch with Nick?s text and a few examples.

----------
assignee: docs at python -> eric.araujo
nosy: +eric.araujo, ncoghlan
stage:  -> needs patch
versions: +Python 2.7, Python 3.2, Python 3.3

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

From report at bugs.python.org  Sun Feb 26 03:47:40 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 26 Feb 2012 02:47:40 +0000
Subject: [docs] [issue13770] python3 & json: add ensure_ascii documentation
In-Reply-To: <1326300131.17.0.750918490995.issue13770@psf.upfronthosting.co.za>
Message-ID: <1330224459.89.0.154590865656.issue13770@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

json in 2.7 works a bit differently; ensure_ascii is already documented there.  Closing, please reopen if the new doc is not to your satisfaction.

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

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

From report at bugs.python.org  Sun Feb 26 03:49:08 2012
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 26 Feb 2012 02:49:08 +0000
Subject: [docs] [issue13467] Typo in doc for library/sysconfig
In-Reply-To: <1322102306.14.0.426447482004.issue13467@psf.upfronthosting.co.za>
Message-ID: <E1S1UAc-0003kO-H7@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset c78b41fa5258 by ?ric Araujo in branch '2.7':
Fix typo (#13467)
http://hg.python.org/cpython/rev/c78b41fa5258

----------

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

From report at bugs.python.org  Sun Feb 26 03:49:09 2012
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 26 Feb 2012 02:49:09 +0000
Subject: [docs] [issue13716] distutils doc contains lots of XXX
In-Reply-To: <1325790136.17.0.881224521536.issue13716@psf.upfronthosting.co.za>
Message-ID: <E1S1UAc-0003kO-HE@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset e853ea9efc6e by ?ric Araujo in branch '2.7':
Hide or remove user-visible XXX notes from distutils doc (#13716).
http://hg.python.org/cpython/rev/e853ea9efc6e

----------

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

From report at bugs.python.org  Sun Feb 26 03:49:56 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 26 Feb 2012 02:49:56 +0000
Subject: [docs] [issue1040439] Missing documentation on how to link with
	libpython
Message-ID: <1330224596.07.0.137920948192.issue1040439@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Is there any reason not to backport to 2.7?  (Yes, I?m volunteering.)

----------

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

From report at bugs.python.org  Sun Feb 26 04:21:50 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Sun, 26 Feb 2012 03:21:50 +0000
Subject: [docs] [issue13716] distutils doc contains lots of XXX
In-Reply-To: <1325790136.17.0.881224521536.issue13716@psf.upfronthosting.co.za>
Message-ID: <1330226510.83.0.645283472171.issue13716@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Done.

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

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

From report at bugs.python.org  Sun Feb 26 09:49:49 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 26 Feb 2012 08:49:49 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330246189.45.0.173614555011.issue14097@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

Regarding the use of the name "variable", could it be replaced by just "name" ? That might make sense since the error for undefined "names" is usually NameError. However, note that the current documentation has a /huge/ amount of mentions for "variable", so we may be too late to the party.

?ric - the word "degenerate" is considered offensive in a couple of languages I speak, but the docs are written in English, so the important point is whether this word is offensive *in English*. If not, I see no reason to drop it.

----------

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

From report at bugs.python.org  Sun Feb 26 10:54:57 2012
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 26 Feb 2012 09:54:57 +0000
Subject: [docs] [issue14123] Indicate that there are no current plans to
	deprecate	printf-style formatting
In-Reply-To: <1330202928.96.0.727285588049.issue14123@psf.upfronthosting.co.za>
Message-ID: <E1S1aoh-0001gI-CA@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 80069bbae26d by Gregory P. Smith in branch '3.2':
Issue #14123: Explicitly mention that old style % string formatting has caveats
http://hg.python.org/cpython/rev/80069bbae26d

New changeset 98a1855ebfe1 by Gregory P. Smith in branch 'default':
Issue #14123: Explicitly mention that old style % string formatting has caveats but is not going away any time soon.
http://hg.python.org/cpython/rev/98a1855ebfe1

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

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

From yelinaung99 at gmail.com  Sun Feb 26 04:07:58 2012
From: yelinaung99 at gmail.com (Ye Aung)
Date: Sat, 25 Feb 2012 19:07:58 -0800
Subject: [docs] Help with Starting file
Message-ID: <CANOt3dzd07jfcvn548D2E=m81Q_6LSLzKRs+73+C5Zv5tp0ORg@mail.gmail.com>

I download the file here:  http://docs.python.org/download . I extract it
and I find a lot files in there and I have trouble figuring out which file
to start.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120225/a3bf53dc/attachment.html>

From sandro.tosi at gmail.com  Sun Feb 26 12:58:12 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sun, 26 Feb 2012 12:58:12 +0100
Subject: [docs] Help with Starting file
In-Reply-To: <CANOt3dzd07jfcvn548D2E=m81Q_6LSLzKRs+73+C5Zv5tp0ORg@mail.gmail.com>
References: <CANOt3dzd07jfcvn548D2E=m81Q_6LSLzKRs+73+C5Zv5tp0ORg@mail.gmail.com>
Message-ID: <CAPdtAj0LF0=UskM=ThaE9MDdWzzsAJR1HvMvSRdK_=AVb803jQ@mail.gmail.com>

On Sun, Feb 26, 2012 at 04:07, Ye Aung <yelinaung99 at gmail.com> wrote:
> I download the file here:? http://docs.python.org/download?. I extract it

I supposed you downloaded python-2.7.2-docs-html.tar.bz2 , if not,
please specify which one you took.

> and I find a lot files in there and I have trouble figuring out which file
> to start.

If it's the file above, then the start file is index.html.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Sun Feb 26 14:04:33 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Sun, 26 Feb 2012 14:04:33 +0100
Subject: [docs] Bug?
In-Reply-To: <BLU144-W116FBE59DB7953B968D244BF6A0@phx.gbl>
References: <BLU144-W116FBE59DB7953B968D244BF6A0@phx.gbl>
Message-ID: <CAPdtAj2J=yds4sY_MDYDX_e0oK_eJaCngJnzeZofmg=Noh_Fww@mail.gmail.com>

Hello Peter,

2012/2/24 Peter Demchenko <pdemcenko at hotmail.com>:
>
> Hi,
> May be I miss something, but look...
> Why the script:
> ----------------
> x="ab"
> 'cde'
> print(len(x))
> ----------------
>
> ?- responds with 2?

what else would you expect? 5 maybe? I'll try to explain below why 2 is correct

> Whitespaces after "ab" can be or no - result is the same: 2

do you mean "ab " or something else?

> It's rather dangerous situation, since the next line 'cde' produces no
> compilation errors

thecnically speaking, python is not compiled, just interpreted and a
bytecode version is generated for speed-up reasons. Also it's a valid
expression, a string, and it doesn't generate any warning/error. if
you typed it on an interactive prompt, it will just print back the
string.

> so you'll get string x stripped!

it's not stripped: you decided to terminate the x definition when you
press ENTER after "ab" so 'cde' is another line, another command,
*not* related to x

> !! ?An excerpt from manual:
> ?"2.4.2. String literal concatenation
> Multiple adjacent string literals (delimited by whitespace), possibly using
> different quoting conventions, are allowed, and their meaning is the same as
> their concatenation. Thus, "hello" 'world' is equivalent to "helloworld".
> This feature can be used to reduce the number of backslashes needed, to
> split long strings conveniently across long lines, ..."
>
> Ok. Now look at another excerpt from the same man:
> !! ?"string.whitespace
> A string containing all characters that are considered whitespace. On most
> systems this includes the characters space, tab, linefeed, return, formfeed,
> and vertical tab"

yes but it's also clear in the lexical description what a shortstring
is and that to use the literals concatenation the strings need to be
at the same syntax level.

To cut a long story short, it's simply not working as you expect :)
Either you use a multi-line string literal:

"""ab
cde"""

or a line continuation '\' and so on.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Sun Feb 26 14:09:12 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 26 Feb 2012 13:09:12 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330261752.13.0.726577230685.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

"A PyObject is not a very magnificent object - it just contains the refcount and a pointer to the object?s ?type object?."

Too chatty and should be replaced by a more pragmatic explanation, or shortened.

----------
nosy: +docs at python

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

From report at bugs.python.org  Sun Feb 26 14:12:15 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 26 Feb 2012 13:12:15 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330261935.34.0.978965894667.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

"in this case, nothing more than every Python object contains"

There's a grammar error lurking somewhere in there...

----------

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

From report at bugs.python.org  Sun Feb 26 14:26:31 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 26 Feb 2012 13:26:31 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330262791.47.0.293996851318.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

This is not strictly in the extending doc, but linked from it:

http://docs.python.org/dev/c-api/type.html#PyType_GenericNew

The PyType_GenericNew API function is not documented

----------

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

From report at bugs.python.org  Sun Feb 26 14:33:46 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 26 Feb 2012 13:33:46 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330263226.36.0.749330540116.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

"Let?s expend "

Typo

----------

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

From report at bugs.python.org  Sun Feb 26 14:44:29 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 26 Feb 2012 13:44:29 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330263869.5.0.679597461847.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

"The new method calls the tp_alloc slot to allocate memory"

tp_alloc needs formatting here, similarly to the way it's done in other places

----------

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

From report at bugs.python.org  Sun Feb 26 14:55:02 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 26 Feb 2012 13:55:02 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330264501.98.0.782182019666.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

"but in this cased"

Typo

[this and the past couple of comments refer to the newtypes.html doc]

----------

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

From report at bugs.python.org  Sun Feb 26 14:58:49 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 26 Feb 2012 13:58:49 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330264729.35.0.653620872893.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

Noddy_name in the full code listing (included from noddy2.c) is different from the Noddy_name that is actually explained later

----------

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

From report at bugs.python.org  Sun Feb 26 21:24:37 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 26 Feb 2012 20:24:37 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330287877.9.0.374022526566.issue14097@psf.upfronthosting.co.za>


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

In English, calling someone or something 'degenerate' is a major insult. In means that x is not really human or what it seems or what it was. I remember being initially startled or puzzled at the mathematical usage, but it actually is similar, just without the strong insult. A line is a degenerate parabola; a line segment is a degenerate ellipse; crossed lines constitute a degenerate hyperbola; a line segment and a point on the segment constitute a degenerate triangle. There are all limit cases, but they are simplified 'degenerated' limit cases that lack the curvature or dimensionality of the members of the sets that they are limits of. Note that straight lines are only degenerate as a limit of parabolas; they are fine figures in their only right.

0/0 as the limit of 0/x for small x is degenerate in that it looses the essential property of being a well defined real number.

'Degenerate' should not be casually applied to limits, edge cases, corner cases, or oddball cases in general. One could claim that empty counts and collections, including sequences, are 'degenerate' limits in that they loose the 'essential' property of somethingness. But if one means that, then they should be denied existence, as was done for 0 and empty sets, or put in separate classes. (For 0 and {}, there really is a sense of insult that does not apply to lines. We still see it with 'imaginary' numbers.) By including 0 and empty collections in their respective classes, Python denies that they are degenerate. So I do not think any slice should be called 'degenerate'. Certainly, the contrast between all slices working and only some indexes working has nothing to do with 'degeneracy'.

----------

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

From report at bugs.python.org  Sun Feb 26 21:32:37 2012
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 26 Feb 2012 20:32:37 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330288357.29.0.25460055156.issue14097@psf.upfronthosting.co.za>


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

I think we should feel free to change 'variable' to 'name', especially in the Intro, if it can be done gracefully in context. In my experience with python-list, the former seems a source of confusion for Python newbies. I try to avoid it when writing about Python.

----------

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

From report at bugs.python.org  Sun Feb 26 21:53:18 2012
From: report at bugs.python.org (Leon Matthews)
Date: Sun, 26 Feb 2012 20:53:18 +0000
Subject: [docs] [issue14006] Improve the documentation of
	xml.etree.ElementTree
In-Reply-To: <1329190125.69.0.69162565954.issue14006@psf.upfronthosting.co.za>
Message-ID: <1330289598.8.0.763916053671.issue14006@psf.upfronthosting.co.za>


Leon Matthews <python at lost.co.nz> added the comment:

Thank you ?ric and Ezio.  I'll produce a patch to convert the javadoc to docstrings this week, then submit it here.

----------

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

From report at bugs.python.org  Sun Feb 26 22:52:44 2012
From: report at bugs.python.org (Georg Brandl)
Date: Sun, 26 Feb 2012 21:52:44 +0000
Subject: [docs] [issue14097] Improve the "introduction" page of the tutorial
In-Reply-To: <1329975473.84.0.795852636525.issue14097@psf.upfronthosting.co.za>
Message-ID: <1330293164.42.0.772392509861.issue14097@psf.upfronthosting.co.za>


Georg Brandl <georg at python.org> added the comment:

Well, I guess some people will always be blind to the finer distinctions in the scientific meaning of words...  but that doesn't mean we should apply them where they don't.

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

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

From report at bugs.python.org  Sun Feb 26 23:08:30 2012
From: report at bugs.python.org (=?utf-8?q?Filip_Gruszczy=C5=84ski?=)
Date: Sun, 26 Feb 2012 22:08:30 +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: <1330294110.0.0.565314990291.issue11807@psf.upfronthosting.co.za>


Filip Gruszczy?ski <gruszczy at gmail.com> added the comment:

Bump! I would like to remind about this issue and patch.

----------

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

From report at bugs.python.org  Sun Feb 26 23:39:44 2012
From: report at bugs.python.org (Florent Xicluna)
Date: Sun, 26 Feb 2012 22:39:44 +0000
Subject: [docs] [issue14006] Improve the documentation of
	xml.etree.ElementTree
In-Reply-To: <1329190125.69.0.69162565954.issue14006@psf.upfronthosting.co.za>
Message-ID: <1330295984.63.0.409971307544.issue14006@psf.upfronthosting.co.za>


Florent Xicluna <florent.xicluna at gmail.com> added the comment:

FWIW, Fredrik, who is the creator of ElementTree, had a preference for JavaDoc conventions, as explained here: http://bugs.python.org/issue6488#msg102087

They are compatible with the tool PythonDoc, authored by Fredrik too:
http://www.effbot.org/zone/pythondoc.htm


However, I agree it makes sense to turn them into docstrings if the package is only maintained in the standard library.


BTW, the issue 6488 is still opened. I did not check if there's something left to do before to close it.
There's also a patch attached to issue 2864, which need some review.

----------
dependencies: +ElementTree documentation refers to "path" with no explanation, and inconsistently
nosy: +effbot

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

From report at bugs.python.org  Sun Feb 26 23:55:10 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Sun, 26 Feb 2012 22:55:10 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330296910.27.0.246958062442.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

There are some:

"
   XXX Need to ...
"

Paragraphs scattered across the doc. These have no place in the official documentation. For placeholders, an issue can be created that lists all the things that need to be done.

----------

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

From report at bugs.python.org  Mon Feb 27 07:15:06 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Mon, 27 Feb 2012 06:15:06 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330323305.82.0.376128216781.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

Adding the documentation experts. 

I plan to apply a fix for these soon. If you guys have any objections, let me know.

----------
nosy: +eric.araujo, ezio.melotti, georg.brandl

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

From report at bugs.python.org  Mon Feb 27 09:56:11 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 27 Feb 2012 08:56:11 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330332971.56.0.119150335259.issue14129@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

> "in this case, nothing more than every Python object contains"
> There's a grammar error lurking somewhere in there...

It could be: ?nothing more that what every Python object contains?.

Could you post a patch for review?

----------

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

From report at bugs.python.org  Mon Feb 27 10:06:05 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 27 Feb 2012 09:06:05 +0000
Subject: [docs] [issue14123] Indicate that there are no current plans to
	deprecate	printf-style formatting
In-Reply-To: <1330202928.96.0.727285588049.issue14123@psf.upfronthosting.co.za>
Message-ID: <1330333565.46.0.676642728229.issue14123@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Apparently this was too urgent too wait for my patch :)

Not closing yet, as there are still phrasing issues discussed on python-dev.

----------
assignee: eric.araujo -> 
nosy: +gregory.p.smith

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

From report at bugs.python.org  Mon Feb 27 10:40:55 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 27 Feb 2012 09:40:55 +0000
Subject: [docs] [issue14123] Indicate that there are no current plans to
	deprecate	printf-style formatting
In-Reply-To: <1330202928.96.0.727285588049.issue14123@psf.upfronthosting.co.za>
Message-ID: <1330335655.33.0.444470947339.issue14123@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Feb 27 13:24:22 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 27 Feb 2012 12:24:22 +0000
Subject: [docs] [issue10713] re module doesn't describe string boundaries
	for \b
In-Reply-To: <1292461535.35.0.85810781117.issue10713@psf.upfronthosting.co.za>
Message-ID: <1330345462.08.0.179742667043.issue10713@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

This is a new patch based on Martin work.
I don't think it's necessary to explain what happens while using r'\b' or r'\B' on an empty string in the doc -- that's not a common case and it might end up confusing users.  I think however that a couple of examples might help them figuring out what they are useful for.
Mentioning that they work with the beginning/end of the string too is a reasonable request, so I tweaked the doc to point that out.

----------
stage: needs patch -> patch review
type:  -> enhancement
versions:  -Python 3.1
Added file: http://bugs.python.org/file24661/issue10713.diff

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

From report at bugs.python.org  Mon Feb 27 14:28:44 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 27 Feb 2012 13:28:44 +0000
Subject: [docs] [issue10713] re module doesn't describe string boundaries
	for \b
In-Reply-To: <1292461535.35.0.85810781117.issue10713@psf.upfronthosting.co.za>
Message-ID: <1330349324.52.0.39118367177.issue10713@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Like it.

----------

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

From report at bugs.python.org  Mon Feb 27 15:02:54 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Mon, 27 Feb 2012 14:02:54 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330351373.33.0.200371297255.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

Patch attached

----------
keywords: +patch
stage:  -> patch review
Added file: http://bugs.python.org/file24663/issue_14129.1.patch

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

From report at bugs.python.org  Mon Feb 27 18:17:28 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Mon, 27 Feb 2012 17:17:28 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <1330363048.48.0.831578036977.issue14129@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

Thanks for the review. I'm going to do the commit now. Feel free to just fix it if any obvious mistakes remain.

----------

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

From report at bugs.python.org  Mon Feb 27 18:19:12 2012
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 27 Feb 2012 17:19:12 +0000
Subject: [docs] [issue14129] Corrections for the "extending" doc
In-Reply-To: <1330254538.51.0.802028199864.issue14129@psf.upfronthosting.co.za>
Message-ID: <E1S24Dx-0006Bg-UJ@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 6c737eb12c3e by Eli Bendersky in branch 'default':
Some corrections for the Doc/extending documentation. Closes #14129
http://hg.python.org/cpython/rev/6c737eb12c3e

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

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

From sandro.tosi at gmail.com  Tue Feb 28 22:42:13 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Tue, 28 Feb 2012 22:42:13 +0100
Subject: [docs] error Python 3.* - 9.3 operator, section 9.3.1, Division
In-Reply-To: <6DC1DA3F-51C4-4914-B99A-39EFF270D1F2@gmail.com>
References: <6DC1DA3F-51C4-4914-B99A-39EFF270D1F2@gmail.com>
Message-ID: <CAPdtAj2cRoOZkPSh6+vP-TABgqdRuuG28q0bBRm_+GidvTN74w@mail.gmail.com>

Hello F?lix-Antoine,

2012/2/19 F?lix-Antoine Fortin <felix.antoine.fortin at gmail.com>:
> In abstract operations table in section 9.3.1 the first of two lines
> on Division, the associated function should be : truediv() instead of div().

Nice catch! i've just fixed in 3.2 and 3.3 documentation.

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From hughperkins2 at gmail.com  Mon Feb 27 14:58:31 2012
From: hughperkins2 at gmail.com (Hugh Perkins)
Date: Mon, 27 Feb 2012 21:58:31 +0800
Subject: [docs] howto-advocacy
Message-ID: <52CC4668-D1EE-4902-8259-73FC23EA429F@gmail.com>

Hi

The howto-advocacy is interesting.

You might consider removing the following sentences, which I found personally gave me a negative impression:

"python hasn't had all the publicity" to my mind gives the impression that python is not popular.

"python is definitely not a toy language that only usable for small tasks". This gives to me the impression that you feel many people think it is.

Section "who's going to support it?" a company needs to be able to call someone, pay for support right now, within one hour, not on a maybe basis. I feel either remove this section or suggest links to three companies providing python support.

Section "python is freely available , how good can it be?" I felt what I wanted to see was not that Linux and apache are good, but why python is good.


From jepa1974 at hotmail.com  Tue Feb 28 16:37:22 2012
From: jepa1974 at hotmail.com (JOSE PERALTA)
Date: Tue, 28 Feb 2012 15:37:22 +0000
Subject: [docs] (no subject)
Message-ID: <SNT106-W25EFE6081B3D35723D1581DA6E0@phx.gbl>


NEED TO KNOW 
1) LOCATE IN SCREEN  (X,Y)   THE      RAW_INPUT("EJ.")  OR   THE  PRINT "EJ"


2) X=RAW_INPUT ("EJ:")    ONLY YOU LEAVE THE NUMBER OF CHARACTERS DIGITAR DESIRED
  		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120228/5d32a051/attachment.html>

From yelinaung99 at gmail.com  Mon Feb 27 03:10:34 2012
From: yelinaung99 at gmail.com (Ye Aung)
Date: Sun, 26 Feb 2012 18:10:34 -0800
Subject: [docs] Help with the files
Message-ID: <CANOt3dxj9GYFSNDKM_GGZuCthQ3rkdtbFamojxcSiPRsJbHuQA@mail.gmail.com>

I download the file here:  http://docs.python.org/download . I extract it
and I find a lot files in there and I have trouble figuring out which file
to start. I download the PDF (US-Letter paper size) for python 2.7.2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20120226/6f9be303/attachment.html>

From sandro.tosi at gmail.com  Tue Feb 28 22:53:11 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Tue, 28 Feb 2012 22:53:11 +0100
Subject: [docs] (no subject)
In-Reply-To: <SNT106-W25EFE6081B3D35723D1581DA6E0@phx.gbl>
References: <SNT106-W25EFE6081B3D35723D1581DA6E0@phx.gbl>
Message-ID: <CAPdtAj34YARtHEktv6XFLueweAtMMm3qtkRAMbF+kyqo7k0DSA@mail.gmail.com>

Hello Jose,
please have a look at http://tools.ietf.org/html/rfc1855 : writing in
upper case in mails is equals to screaming to people; probably
something you don't want to do if you're seeking for help.

On Tue, Feb 28, 2012 at 16:37, JOSE PERALTA <jepa1974 at hotmail.com> wrote:
> NEED TO KNOW
>
> 1) LOCATE IN SCREEN ?(X,Y) ? THE ? ? ?RAW_INPUT("EJ.") ?OR ? THE ?PRINT "EJ"
>
>
>
> 2) X=RAW_INPUT ("EJ:") ? ?ONLY?YOU?LEAVE?THE?NUMBER
> OF?CHARACTERS?DIGITAR?DESIRED

This request smells a lot like homeworks: can you please provide a bit
more context?

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From sandro.tosi at gmail.com  Tue Feb 28 22:59:17 2012
From: sandro.tosi at gmail.com (Sandro Tosi)
Date: Tue, 28 Feb 2012 22:59:17 +0100
Subject: [docs] Help with the files
In-Reply-To: <CANOt3dxj9GYFSNDKM_GGZuCthQ3rkdtbFamojxcSiPRsJbHuQA@mail.gmail.com>
References: <CANOt3dxj9GYFSNDKM_GGZuCthQ3rkdtbFamojxcSiPRsJbHuQA@mail.gmail.com>
Message-ID: <CAPdtAj0D6MJdDtKDHeh75Bk6-XhK6Ohjmop52cP=Cd93Z8_upQ@mail.gmail.com>

Hello Ye,

On Mon, Feb 27, 2012 at 03:10, Ye Aung <yelinaung99 at gmail.com> wrote:
> I download the file here:??http://docs.python.org/download?. I extract it
> and I find a lot files in there and I have trouble figuring out which file
> to start. I download the?PDF (US-Letter paper size) for python 2.7.2

It would have been better if you had replied to the other thread,
instead of starting a new one. To reply to your question, there is no
starting file for PDFs. They are the same docs linked at
http://docs.python.org/ but in a single file (and without an index).

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

From report at bugs.python.org  Wed Feb 29 03:12:20 2012
From: report at bugs.python.org (py.user)
Date: Wed, 29 Feb 2012 02:12:20 +0000
Subject: [docs] [issue14155] Deja vu in re's documentation
Message-ID: <1330481540.05.0.869825762197.issue14155@psf.upfronthosting.co.za>


New submission from py.user <port139 at yandex.ru>:

This paragraph is redundant
http://docs.python.org/py3k/library/re.html#matching-vs-searching

a duplicate
http://docs.python.org/py3k/library/re.html#search-vs-match


the part about match() behavior in multiline mode could be described in note here:
http://docs.python.org/py3k/library/re.html#re.regex.match

----------
assignee: docs at python
components: Documentation
messages: 154592
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: Deja vu in re's documentation
type: enhancement
versions: Python 3.2

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

From report at bugs.python.org  Wed Feb 29 05:17:56 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 29 Feb 2012 04:17:56 +0000
Subject: [docs] [issue14155] Deja vu in re's documentation
In-Reply-To: <1330481540.05.0.869825762197.issue14155@psf.upfronthosting.co.za>
Message-ID: <1330489076.77.0.519740449089.issue14155@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
nosy: +ezio.melotti, pitrou
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Wed Feb 29 10:50:10 2012
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 29 Feb 2012 09:50:10 +0000
Subject: [docs] [issue10713] re module doesn't describe string boundaries
	for \b
In-Reply-To: <1292461535.35.0.85810781117.issue10713@psf.upfronthosting.co.za>
Message-ID: <E1S2gAh-0001uW-Fb@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset fc89e09ca2fc by Ezio Melotti in branch '2.7':
#10713: Improve documentation for \b and \B and add a few tests.  Initial patch and tests by Martin Pool.
http://hg.python.org/cpython/rev/fc89e09ca2fc

New changeset cde7fa40b289 by Ezio Melotti in branch '3.2':
#10713: Improve documentation for \b and \B and add a few tests.  Initial patch and tests by Martin Pool.
http://hg.python.org/cpython/rev/cde7fa40b289

New changeset b78ca038e468 by Ezio Melotti in branch 'default':
#10713: merge with 3.2.
http://hg.python.org/cpython/rev/b78ca038e468

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

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

From report at bugs.python.org  Wed Feb 29 10:51:35 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 29 Feb 2012 09:51:35 +0000
Subject: [docs] [issue10713] re module doesn't describe string boundaries
	for \b
In-Reply-To: <1292461535.35.0.85810781117.issue10713@psf.upfronthosting.co.za>
Message-ID: <1330509095.47.0.368316035234.issue10713@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Fixed, thanks for the patch!

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

From report at bugs.python.org  Wed Feb 29 11:47:18 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 29 Feb 2012 10:47:18 +0000
Subject: [docs] [issue14155] Deja vu in re's documentation
In-Reply-To: <1330481540.05.0.869825762197.issue14155@psf.upfronthosting.co.za>
Message-ID: <1330512438.44.0.516283715632.issue14155@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Patch attached.

----------
assignee: docs at python -> ezio.melotti
components: +Regular Expressions
keywords: +patch
nosy: +mrabarnett
stage:  -> patch review
Added file: http://bugs.python.org/file24677/issue14155.diff

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

From report at bugs.python.org  Wed Feb 29 12:14:56 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 29 Feb 2012 11:14:56 +0000
Subject: [docs] [issue14149] argparse: Document how to use argument names
	that are	not Python identifiers
In-Reply-To: <1330431835.85.0.549489798388.issue14149@psf.upfronthosting.co.za>
Message-ID: <1330514096.1.0.422879271644.issue14149@psf.upfronthosting.co.za>


Changes by ?ric Araujo <merwok at netwok.org>:


----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
keywords: +easy
nosy: +docs at python
stage:  -> needs patch
title: argparse usage model requires argument names to be python identifiers -> argparse: Document how to use argument names that are not Python identifiers
versions: +Python 2.7, Python 3.2

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

From report at bugs.python.org  Wed Feb 29 12:17:35 2012
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Wed, 29 Feb 2012 11:17:35 +0000
Subject: [docs] [issue14155] Deja vu in re's documentation
In-Reply-To: <1330481540.05.0.869825762197.issue14155@psf.upfronthosting.co.za>
Message-ID: <1330514255.31.0.97503241025.issue14155@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Didn?t review all lines in detail but looks globally good.  I would not remove Fred?s name though, but move it to another section or the top-level of the file.

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

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

From report at bugs.python.org  Wed Feb 29 12:19:10 2012
From: report at bugs.python.org (Joseph Birr-Pixton)
Date: Wed, 29 Feb 2012 11:19:10 +0000
Subject: [docs] [issue14149] argparse: Document how to use argument names
	that are	not Python identifiers
In-Reply-To: <1330431835.85.0.549489798388.issue14149@psf.upfronthosting.co.za>
Message-ID: <1330514350.4.0.426847968677.issue14149@psf.upfronthosting.co.za>


Joseph Birr-Pixton <jpixton at gmail.com> added the comment:

> I don?t understand, can you rephrase?

Sorry, I mean making Namespace subscriptable.  eg:

>>> v = argparse.Namespace(abc = 123)
>>> v
Namespace(abc=123)
>>> v.abc
123
>>> v['abc']
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'Namespace' object is not subscriptable

> add_argument('foo_bar', metavar='foo-bar', ...)

This works. Thanks!

Cheers,
Joe

----------

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

From report at bugs.python.org  Wed Feb 29 12:40:33 2012
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 29 Feb 2012 11:40:33 +0000
Subject: [docs] [issue14155] Deja vu in re's documentation
In-Reply-To: <1330481540.05.0.869825762197.issue14155@psf.upfronthosting.co.za>
Message-ID: <E1S2htX-0003lt-Os@dinsdale.python.org>


Roundup Robot <devnull at psf.upfronthosting.co.za> added the comment:

New changeset 3958121a027f by Ezio Melotti in branch '2.7':
#14155: remove duplication about search vs match in re doc.
http://hg.python.org/cpython/rev/3958121a027f

New changeset 4114e816a71b by Ezio Melotti in branch '3.2':
#14155: remove duplication about search vs match in re doc.
http://hg.python.org/cpython/rev/4114e816a71b

New changeset 457c3c0cb0a0 by Ezio Melotti in branch 'default':
#14155: merge with 3.2.
http://hg.python.org/cpython/rev/457c3c0cb0a0

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

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

From report at bugs.python.org  Wed Feb 29 12:45:40 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 29 Feb 2012 11:45:40 +0000
Subject: [docs] [issue14155] Deja vu in re's documentation
In-Reply-To: <1330481540.05.0.869825762197.issue14155@psf.upfronthosting.co.za>
Message-ID: <1330515940.18.0.399563034871.issue14155@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Fixed.
I changed something, as suggested by ?ric.

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

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

From report at bugs.python.org  Wed Feb 29 13:34:34 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 29 Feb 2012 12:34:34 +0000
Subject: [docs] [issue13998] Lookbehind assertions go behind the start
	position for	the match
In-Reply-To: <1329036883.7.0.662970564139.issue13998@psf.upfronthosting.co.za>
Message-ID: <1330518874.89.0.278373520675.issue13998@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

IMHO the documentation is fine as is.  Using pos in combination with lookarounds that match on the beginning/end of the "slice" seems a rather uncommon corner case, and I don't think it's worth documenting it.  Even if it was documented, as a user, I would just try it from the interpreter anyway, rather than checking the docs for some prose to decipher.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
resolution:  -> wont fix
stage:  -> committed/rejected
status: open -> closed
versions: +Python 3.3 -Python 3.1

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

From report at bugs.python.org  Wed Feb 29 13:40:32 2012
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 29 Feb 2012 12:40:32 +0000
Subject: [docs] [issue11379] Remove "lightweight" from minidom description
In-Reply-To: <1299093908.17.0.828802315354.issue11379@psf.upfronthosting.co.za>
Message-ID: <1330519232.67.0.526311759186.issue11379@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Feb 29 16:25:32 2012
From: report at bugs.python.org (Steven Bethard)
Date: Wed, 29 Feb 2012 15:25:32 +0000
Subject: [docs] [issue14149] argparse: Document how to use argument names
	that are	not Python identifiers
In-Reply-To: <1330431835.85.0.549489798388.issue14149@psf.upfronthosting.co.za>
Message-ID: <1330529132.43.0.0764487826357.issue14149@psf.upfronthosting.co.za>


Steven Bethard <steven.bethard at gmail.com> added the comment:

> making Namespace subscriptable

This has been discussed before - see issue 11076. I prefer to keep Namespace as simple as possible. For subscripting, just use the standard Python idiom of vars as suggested in the docs:

http://docs.python.org/library/argparse.html#the-namespace-object

----------

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

From report at bugs.python.org  Wed Feb 29 17:37:49 2012
From: report at bugs.python.org (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 29 Feb 2012 16:37:49 +0000
Subject: [docs] [issue11379] Remove "lightweight" from minidom description
In-Reply-To: <1299093908.17.0.828802315354.issue11379@psf.upfronthosting.co.za>
Message-ID: <1330533468.82.0.275971200388.issue11379@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

The wording in msg152836 is fine with me, in particular as it doesn't make any performance claims.

----------

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

From report at bugs.python.org  Wed Feb 29 20:04:54 2012
From: report at bugs.python.org (Eli Bendersky)
Date: Wed, 29 Feb 2012 19:04:54 +0000
Subject: [docs] [issue11379] Remove "lightweight" from minidom description
In-Reply-To: <1299093908.17.0.828802315354.issue11379@psf.upfronthosting.co.za>
Message-ID: <1330542294.1.0.323337754649.issue11379@psf.upfronthosting.co.za>


Eli Bendersky <eliben at gmail.com> added the comment:

I'm attaching a patch for Doc/library/xml.dom.minidom.rst 

It adds the note as phrased by Stefan, with a tiny wording change to make the first sentence less ambiguous.

----------
keywords: +patch
Added file: http://bugs.python.org/file24686/issue_11379.1.patch

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

From report at bugs.python.org  Wed Feb 29 23:06:44 2012
From: report at bugs.python.org (py.user)
Date: Wed, 29 Feb 2012 22:06:44 +0000
Subject: [docs] [issue14155] Deja vu in re's documentation
In-Reply-To: <1330481540.05.0.869825762197.issue14155@psf.upfronthosting.co.za>
Message-ID: <1330553204.22.0.318967507999.issue14155@psf.upfronthosting.co.za>


py.user <port139 at yandex.ru> added the comment:

the multiline mode affects on regex.match()

>>> p = re.compile(r'^a')
>>> p.match('abc\nabc')
<_sre.SRE_Match object at 0xb749bf38>
>>> p.match('abc\nabc').span()
(0, 1)
>>> p.match('abc\nabc', 4)
>>> 
>>> p = re.compile(r'^a', re.M)
>>> p.match('abc\nabc', 4)
<_sre.SRE_Match object at 0xb749bf38>
>>> p.match('abc\nabc', 4).span()
(4, 5)
>>>

----------

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