From report at bugs.python.org  Mon Jul  1 02:25:49 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 01 Jul 2013 00:25:49 +0000
Subject: [docs] [issue18331] Document that runpy.run_path and run_module
	copy the	module globals
In-Reply-To: <1372602782.77.0.618152195123.issue18331@psf.upfronthosting.co.za>
Message-ID: <1372638349.5.0.394327629375.issue18331@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

As Richard said, the __globals__ attributes of the functions are pointing at the real module dictionary, which may have been cleared when the temporary module was destroyed.

However, I just checked the docs and they don't actually mention the fact that run_path and run_module currently return a copy of the globals - they say they "return the resulting module globals dictionary."

Since I would prefer it if the functions actually worked as advertised, I suggest we document the namespace copying as a CPython implementation detail, rather than as a guaranteed feature. That way we can eliminate these copy operations once the module namespace purging has been eliminated.

Some related references:
   Don't purge module dicts before shutdown: issue 18214
   Don't purge module dicts at all: issue 812369
   More robust finalisation semantics: PEP 442
   
We should also tidy up the headings in the data model reference (
http://docs.python.org/3/reference/datamodel.html#the-standard-type-hierarchy) so we can link directly to the section that mentions the CPython module clearing implementation detail this behaviour is designed to work around.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
stage:  -> needs patch
title: runpy.run_path gives functions with corrupted .__globals__ -> Document that runpy.run_path and run_module copy the module globals
type: behavior -> enhancement
versions: +Python 2.7, Python 3.4

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

From report at bugs.python.org  Mon Jul  1 02:28:51 2013
From: report at bugs.python.org (Nikolaus Rath)
Date: Mon, 01 Jul 2013 00:28:51 +0000
Subject: [docs] [issue17814] Popen.stdin/stdout/stderr documentation should
	mention	object type
In-Reply-To: <1366586086.38.0.427506521088.issue17814@psf.upfronthosting.co.za>
Message-ID: <1372638531.3.0.591954895586.issue17814@psf.upfronthosting.co.za>


Changes by Nikolaus Rath <Nikolaus at rath.org>:


----------
keywords: +patch
Added file: http://bugs.python.org/file30736/subprocess_rst.diff

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

From report at bugs.python.org  Mon Jul  1 02:29:54 2013
From: report at bugs.python.org (Nikolaus Rath)
Date: Mon, 01 Jul 2013 00:29:54 +0000
Subject: [docs] [issue17814] Popen.stdin/stdout/stderr documentation should
	mention	object type
In-Reply-To: <1366586086.38.0.427506521088.issue17814@psf.upfronthosting.co.za>
Message-ID: <1372638594.14.0.661738488077.issue17814@psf.upfronthosting.co.za>


Nikolaus Rath added the comment:

patch attached.

----------

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

From report at bugs.python.org  Mon Jul  1 03:50:32 2013
From: report at bugs.python.org (R. David Murray)
Date: Mon, 01 Jul 2013 01:50:32 +0000
Subject: [docs] [issue18334] type(name, bases,
	dict) does not call metaclass' __prepare__ attribute
In-Reply-To: <1372641138.46.0.644775856541.issue18334@psf.upfronthosting.co.za>
Message-ID: <1372643432.44.0.257740034634.issue18334@psf.upfronthosting.co.za>


R. David Murray added the comment:

"Intentional" is not perhaps the exactly right term, but it is working as expected.  There was a thread about this on python-dev ("PEP 3115 compliant dynamic type creation" and "adding types.build_class for 3.3"), that ultimately resulted in the addition of the 'new_class' function to the types module.  The documentation should probably just say that types doesn't handle metaclass __prepare__, and provide a link to the new_class function.

----------
assignee:  -> docs at python
components: +Documentation -Interpreter Core
nosy: +docs at python, ncoghlan, r.david.murray
versions: +Python 3.4

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

From report at bugs.python.org  Mon Jul  1 04:00:51 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 01 Jul 2013 02:00:51 +0000
Subject: [docs] [issue18334] type(name, bases,
	dict) does not call metaclass' __prepare__ attribute
In-Reply-To: <1372641138.46.0.644775856541.issue18334@psf.upfronthosting.co.za>
Message-ID: <1372644051.25.0.14734030915.issue18334@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

I think we should actually go further, and explicitly defer to http://docs.python.org/3/library/types#dynamic-type-creation for dynamic type creation.

Type shouldn't be called with arbitrary bases any more, precisely *because* doing so breaks __prepare__ handling. It's only safe to call a metaclass directly with arbitrary bases if you call types.prepare_class first:

    mcl, namespace, kwds = types.prepare_class(name, bases)
    cls = mcl(name, bases, namespace, **kwds)

You can only skip types.prepare_class if you *know* you already have the right metaclass (such as when there aren't any base classes defined).

----------

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

From report at bugs.python.org  Mon Jul  1 04:19:18 2013
From: report at bugs.python.org (Nikolaus Rath)
Date: Mon, 01 Jul 2013 02:19:18 +0000
Subject: [docs] [issue18334] type(name, bases,
	dict) does not call metaclass' __prepare__ attribute
In-Reply-To: <1372641138.46.0.644775856541.issue18334@psf.upfronthosting.co.za>
Message-ID: <1372645157.97.0.747655652828.issue18334@psf.upfronthosting.co.za>


Nikolaus Rath added the comment:

In that cases, maybe type(name, cls, clsdict) should actually raise an error if there's a metaclass with __prepare__ involved?

Presumably that would break only code that was already broken, but it would convert previously hidden behavioral bugs into an explicit expressions raised at the right point.

----------

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

From report at bugs.python.org  Mon Jul  1 09:19:51 2013
From: report at bugs.python.org (Thomas Guettler)
Date: Mon, 01 Jul 2013 07:19:51 +0000
Subject: [docs] [issue18336] codecs: Link to readline module (history)
	instead of	fd.readline()
Message-ID: <1372663191.71.0.440770388569.issue18336@psf.upfronthosting.co.za>


New submission from Thomas Guettler:

The documentation of codecs.readline() has a link to the readline module.

That the same word with a total different meaning!

http://docs.python.org/2/library/codecs.html?highlight=readline#codecs.StreamReader.readline

The GNU readline module is about the history like bash or interactive python.

----------
assignee: docs at python
components: Documentation
messages: 192111
nosy: docs at python, guettli
priority: normal
severity: normal
status: open
title: codecs: Link to readline module (history) instead of fd.readline()
versions: Python 2.7

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

From report at bugs.python.org  Mon Jul  1 09:30:57 2013
From: report at bugs.python.org (Thomas Guettler)
Date: Mon, 01 Jul 2013 07:30:57 +0000
Subject: [docs] [issue18337] codecs: StremReader readline() breaks on
	undocumented	characters
Message-ID: <1372663857.57.0.575592634078.issue18337@psf.upfronthosting.co.za>


New submission from Thomas Guettler:

The stream reader of codecs.open() breaks on undocumented characters:

http://docs.python.org/2/library/codecs.html?highlight=codecs%20readline#codecs.StreamReader.readline

import tempfile
temp=tempfile.mktemp()
fd=open(temp, 'wb')
fd.write('abc\ndef\x85ghi')
fd.close()

import codecs
fd=codecs.open(temp, 'rb', 'latin1')
while True:
    line=fd.readline()
    if not line:
        break
    print repr(line)

Result:
u'abc\n'
u'def\x85'
u'ghi'

Related: http://stackoverflow.com/questions/16227114/utf-8-files-read-in-python-will-line-break-at-character-x85

----------
assignee: docs at python
components: Documentation
messages: 192112
nosy: docs at python, guettli
priority: normal
severity: normal
status: open
title: codecs: StremReader readline() breaks on undocumented characters
versions: Python 2.7

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

From report at bugs.python.org  Mon Jul  1 09:35:31 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 01 Jul 2013 07:35:31 +0000
Subject: [docs] [issue18334] type(name, bases,
	dict) does not call metaclass' __prepare__ attribute
In-Reply-To: <1372641138.46.0.644775856541.issue18334@psf.upfronthosting.co.za>
Message-ID: <1372664131.9.0.919052520477.issue18334@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Unfortunately, it's not that simple, as calling type(name, bases, namespace) is *exactly* what a subclass will do as part of creating the type object.

>From inside the type implementation, we can't tell the difference between "properly called from the child type" and "improperly called without preparing the namespace first".

----------

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

From report at bugs.python.org  Mon Jul  1 11:12:54 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 01 Jul 2013 09:12:54 +0000
Subject: [docs] [issue18336] codecs: Link to readline module (history)
	instead of	fd.readline()
In-Reply-To: <1372663191.71.0.440770388569.issue18336@psf.upfronthosting.co.za>
Message-ID: <1372669974.23.0.233058358209.issue18336@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> serhiy.storchaka
keywords: +easy
nosy: +serhiy.storchaka
stage:  -> needs patch
versions: +Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Jul  1 11:36:06 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 01 Jul 2013 09:36:06 +0000
Subject: [docs] [issue18337] codecs: StremReader readline() breaks on
	undocumented	characters
In-Reply-To: <1372663857.57.0.575592634078.issue18337@psf.upfronthosting.co.za>
Message-ID: <1372671366.45.0.864165837714.issue18337@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Thank you for your report. This is a duplicate of issue18291.

----------
nosy: +serhiy.storchaka
resolution:  -> duplicate
stage:  -> committed/rejected
status: open -> closed
superseder:  -> codecs.open interprets space as line ends
versions: +Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Jul  1 18:27:29 2013
From: report at bugs.python.org (Martin Kysel)
Date: Mon, 01 Jul 2013 16:27:29 +0000
Subject: [docs] [issue16272] C-API documentation clarification for
	tp_dictoffset
In-Reply-To: <1350520063.61.0.687481658196.issue16272@psf.upfronthosting.co.za>
Message-ID: <1372696049.13.0.0692647972545.issue16272@psf.upfronthosting.co.za>


Changes by Martin Kysel <martin at martinkysel.com>:


----------
nosy: +mkysel

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

From report at bugs.python.org  Mon Jul  1 18:43:44 2013
From: report at bugs.python.org (Martin Kysel)
Date: Mon, 01 Jul 2013 16:43:44 +0000
Subject: [docs] [issue16665] doc for builtin hex() is poor
In-Reply-To: <1355257997.08.0.0348964643873.issue16665@psf.upfronthosting.co.za>
Message-ID: <1372697024.06.0.0676040115721.issue16665@psf.upfronthosting.co.za>


Changes by Martin Kysel <martin at martinkysel.com>:


----------
nosy: +mkysel

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

From report at bugs.python.org  Mon Jul  1 22:05:20 2013
From: report at bugs.python.org (paul j3)
Date: Mon, 01 Jul 2013 20:05:20 +0000
Subject: [docs] [issue9938] Documentation for argparse interactive use
In-Reply-To: <1285338690.84.0.283413950067.issue9938@psf.upfronthosting.co.za>
Message-ID: <1372709120.22.0.917495801817.issue9938@psf.upfronthosting.co.za>


paul j3 added the comment:

The exit and error methods are mentioned in the 3.4 documentation, but there are no examples of modifying them.

    16.4.5.9. Exiting methods
    ArgumentParser.exit(status=0, message=None)
    ArgumentParser.error(message)

test_argparse.py has a subclass that redefines these methods, though I think it is more complex than necessary.

    class ErrorRaisingArgumentParser(argparse.ArgumentParser):

In http://bugs.python.org/file30204/test_intermixed.py , part of http://bugs.python.org/issue14191 , which creates a parser mode that is closer to optparse in style, I simply use:

    def error(self, message):
        usage = self.format_usage()
        raise Exception('%s%s'%(usage, message))
    ArgumentParser.error = error

to catch errors.

https://github.com/nodeca/argparse a Javascript port of argparse, adds a 'debug' option to the ArgumentParser, that effectively redefines this error method.  They use that extensively in testing.

Another approach is to trap the sysexit.  Ipython does that when argparse is run interactively.

Even the simple try block works, though the SystemExit 2 has no information about the error.

    try:
        args = parser.parse_args('X'.split())
    except SystemExit as e:
        print(e)

Finally, plac ( https://pypi.python.org/pypi/plac ) is a pypi package that is built on argparse.  It has a well developed interactive mode, and integrates threads and multiprocessing.

----------
nosy: +paul.j3

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

From report at bugs.python.org  Tue Jul  2 13:42:32 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 02 Jul 2013 11:42:32 +0000
Subject: [docs] [issue17273] multiprocessing.pool.Pool task/worker handlers
	are not	fork safe
In-Reply-To: <1361514053.16.0.91883779216.issue17273@psf.upfronthosting.co.za>
Message-ID: <3bl3Tg5z3nz7Ljk@mail.python.org>


Roundup Robot added the comment:

New changeset 389788ba6bcb by Richard Oudkerk in branch '2.7':
Issue #17273: Clarify that pool methods can only be used by parent process.
http://hg.python.org/cpython/rev/389788ba6bcb

New changeset 57fe80fda9be by Richard Oudkerk in branch '3.3':
Issue #17273: Clarify that pool methods can only be used by parent process.
http://hg.python.org/cpython/rev/57fe80fda9be

New changeset 7ccf3d36ad13 by Richard Oudkerk in branch 'default':
Issue #17273: Clarify that pool methods can only be used by parent process.
http://hg.python.org/cpython/rev/7ccf3d36ad13

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

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

From report at bugs.python.org  Tue Jul  2 13:45:39 2013
From: report at bugs.python.org (Richard Oudkerk)
Date: Tue, 02 Jul 2013 11:45:39 +0000
Subject: [docs] [issue17273] Pool methods can only be used by parent process.
In-Reply-To: <1361514053.16.0.91883779216.issue17273@psf.upfronthosting.co.za>
Message-ID: <1372765539.16.0.127989810195.issue17273@psf.upfronthosting.co.za>


Changes by Richard Oudkerk <shibturn at gmail.com>:


----------
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
title: multiprocessing.pool.Pool task/worker handlers are not fork safe -> Pool methods can only be used by parent process.
type: behavior -> 
versions: +Python 2.7, Python 3.4

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

From report at bugs.python.org  Tue Jul  2 14:02:31 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 02 Jul 2013 12:02:31 +0000
Subject: [docs] [issue14206] multiprocessing.Queue documentation is lacking
	important	details
In-Reply-To: <1330993962.13.0.893864771053.issue14206@psf.upfronthosting.co.za>
Message-ID: <3bl3wl00MSz7LlQ@mail.python.org>


Roundup Robot added the comment:

New changeset f35401dba89f by Richard Oudkerk in branch '2.7':
Issue #14206: Clarify docs for Queue.join_cancel_thread().
http://hg.python.org/cpython/rev/f35401dba89f

New changeset 9746f217a270 by Richard Oudkerk in branch '3.3':
Issue #14206: Clarify docs for Queue.join_cancel_thread().
http://hg.python.org/cpython/rev/9746f217a270

New changeset d0b48efac9de by Richard Oudkerk in branch 'default':
Issue #14206: Clarify docs for Queue.join_cancel_thread().
http://hg.python.org/cpython/rev/d0b48efac9de

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

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

From report at bugs.python.org  Tue Jul  2 14:04:00 2013
From: report at bugs.python.org (Richard Oudkerk)
Date: Tue, 02 Jul 2013 12:04:00 +0000
Subject: [docs] [issue14206] multiprocessing.Queue documentation is lacking
	important	details
In-Reply-To: <1330993962.13.0.893864771053.issue14206@psf.upfronthosting.co.za>
Message-ID: <1372766640.22.0.275542983646.issue14206@psf.upfronthosting.co.za>


Changes by Richard Oudkerk <shibturn at gmail.com>:


----------
resolution:  -> fixed
stage:  -> committed/rejected

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

From report at bugs.python.org  Tue Jul  2 14:04:18 2013
From: report at bugs.python.org (Richard Oudkerk)
Date: Tue, 02 Jul 2013 12:04:18 +0000
Subject: [docs] [issue14206] multiprocessing.Queue documentation is lacking
	important	details
In-Reply-To: <1330993962.13.0.893864771053.issue14206@psf.upfronthosting.co.za>
Message-ID: <1372766658.49.0.824801387756.issue14206@psf.upfronthosting.co.za>


Changes by Richard Oudkerk <shibturn at gmail.com>:


----------
status: open -> closed

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

From report at bugs.python.org  Wed Jul  3 09:41:02 2013
From: report at bugs.python.org (py.user)
Date: Wed, 03 Jul 2013 07:41:02 +0000
Subject: [docs] [issue18206] license url in site.py should always use X.Y.Z
	form of	version number
In-Reply-To: <1371162560.09.0.685782864566.issue18206@psf.upfronthosting.co.za>
Message-ID: <1372837262.5.0.040380629394.issue18206@psf.upfronthosting.co.za>


Changes by py.user <bugzilla-mail-box at yandex.ru>:


Added file: http://bugs.python.org/file30755/issue18206_test.diff

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

From report at bugs.python.org  Wed Jul  3 19:24:13 2013
From: report at bugs.python.org (Olivier Hervieu)
Date: Wed, 03 Jul 2013 17:24:13 +0000
Subject: [docs] [issue18033] Example for Profile Module shows incorrect
	method
In-Reply-To: <1369235558.14.0.532987051887.issue18033@psf.upfronthosting.co.za>
Message-ID: <1372872253.22.0.486435776092.issue18033@psf.upfronthosting.co.za>


Olivier Hervieu added the comment:

Here is a fixed version for python2.7. Using StringIO instead of io module fixes the problem pointed by Ezio.
The print_stats method dumps the stats either on sys.stdout if `Stats` class is declared without a stream specification or in the given stream parameter (the name print_stats may be a bit misleading).

----------
nosy: +ohe
Added file: http://bugs.python.org/file30760/issue18033_py2.patch

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

From report at bugs.python.org  Wed Jul  3 19:43:07 2013
From: report at bugs.python.org (Wolf Ihlenfeldt)
Date: Wed, 03 Jul 2013 17:43:07 +0000
Subject: [docs] [issue18353] PyUnicode_WRITE_CHAR macro definition missing
Message-ID: <1372873387.67.0.379053408423.issue18353@psf.upfronthosting.co.za>


New submission from Wolf Ihlenfeldt:

Above macro is mentioned in the documentation (3.3.2), but does not appear in the header files. Associated function PyUnicode_WriteChar() is present and works as expected.

----------
assignee: docs at python
components: Documentation, Unicode
messages: 192247
nosy: Wolf.Ihlenfeldt, docs at python, ezio.melotti
priority: normal
severity: normal
status: open
title: PyUnicode_WRITE_CHAR macro definition missing
type: compile error
versions: Python 3.3

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

From report at bugs.python.org  Wed Jul  3 20:47:14 2013
From: report at bugs.python.org (Daniel Holth)
Date: Wed, 03 Jul 2013 18:47:14 +0000
Subject: [docs] [issue18354] http://www.python.org/doc/ has outdated note
Message-ID: <1372877234.32.0.505544665385.issue18354@psf.upfronthosting.co.za>


New submission from Daniel Holth:

Please remove the note.

Note

A new documentation project, which will be merged into the Python documentation soon, covers creating, installing and distributing Python packages:

    The Hitchhiker's Guide to Packaging (creating and distributing Python packages)

----------
assignee: docs at python
components: Documentation
messages: 192251
nosy: dholth, docs at python
priority: normal
severity: normal
status: open
title: http://www.python.org/doc/ has outdated note
type: enhancement

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

From report at bugs.python.org  Wed Jul  3 21:40:34 2013
From: report at bugs.python.org (paul j3)
Date: Wed, 03 Jul 2013 19:40:34 +0000
Subject: [docs] [issue16933] argparse: remove magic from examples
In-Reply-To: <1357911858.69.0.0703193383433.issue16933@psf.upfronthosting.co.za>
Message-ID: <1372880433.85.0.0356822980916.issue16933@psf.upfronthosting.co.za>


paul j3 added the comment:

There still is one "choices='XYZ'" example (16.4.5.1. Sub-commands) but the focus isn't on choices.

----------
nosy: +paul.j3

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

From report at bugs.python.org  Wed Jul  3 21:40:59 2013
From: report at bugs.python.org (Brian Curtin)
Date: Wed, 03 Jul 2013 19:40:59 +0000
Subject: [docs] [issue18354] http://www.python.org/doc/ has outdated note
In-Reply-To: <1372877234.32.0.505544665385.issue18354@psf.upfronthosting.co.za>
Message-ID: <1372880459.58.0.0787148162259.issue18354@psf.upfronthosting.co.za>


Brian Curtin added the comment:

Can you say why?

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

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

From report at bugs.python.org  Thu Jul  4 03:26:40 2013
From: report at bugs.python.org (Russkel)
Date: Thu, 04 Jul 2013 01:26:40 +0000
Subject: [docs] [issue18355] Merge super() guide into documentation
Message-ID: <1372901200.41.0.725969821731.issue18355@psf.upfronthosting.co.za>


New submission from Russkel:

When looking for documentation on the correct usage on super (http://docs.python.org/2/library/functions.html?highlight=super#super), the documentation links to this rather will written blog post http://rhettinger.wordpress.com/2011/05/26/super-considered-super/ by Mr. Hettinger.

I think there is value in merging that blog post into a HOWTO and including in the official documentation.

I'm more than willing to create a patch if this is considered a good idea.

----------
assignee: docs at python
components: Documentation
messages: 192262
nosy: Russkel, docs at python, rhettinger
priority: normal
severity: normal
status: open
title: Merge super() guide into documentation

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

From report at bugs.python.org  Thu Jul  4 09:55:20 2013
From: report at bugs.python.org (Michelle Arzul)
Date: Thu, 04 Jul 2013 07:55:20 +0000
Subject: [docs] [issue18356] help(numpy) causes segfault on exit
Message-ID: <1372924520.77.0.111539946992.issue18356@psf.upfronthosting.co.za>


New submission from Michelle Arzul:

As far as we could tell this bug is only consistently reproducible on Ubuntu 13.04.

A line in pydoc.py causes a segfault when help(numpy) (no other libraries that I know of) exits. The offending method is pipepager().

For a full trackdown and workaround of the problem see http://stackoverflow.com/questions/17344974/python-helpnumpy-causes-segfault-on-exit

----------
assignee: docs at python
components: Documentation
messages: 192276
nosy: Leeward, docs at python
priority: normal
severity: normal
status: open
title: help(numpy) causes segfault on exit
type: crash
versions: Python 2.7

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

From report at bugs.python.org  Thu Jul  4 10:07:29 2013
From: report at bugs.python.org (Christian Heimes)
Date: Thu, 04 Jul 2013 08:07:29 +0000
Subject: [docs] [issue18356] help(numpy) causes segfault on exit
In-Reply-To: <1372924520.77.0.111539946992.issue18356@psf.upfronthosting.co.za>
Message-ID: <1372925249.84.0.0575598692012.issue18356@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Please provide more information about your setup. Not everybody has access to a Ubuntu 13.04 box

* exact Python version
* NumPy version
* platform (X86, X86_64, ARM)
* Kernel, libc and compiler version are useful, too
* terminal application
* environment variables (output of ``export``, you may want to strip sensible values like DBus address). Especially TERM, PAGER and all LESS* variables are of interest.

----------
components: +Library (Lib) -Documentation
nosy: +christian.heimes
versions: +3rd party

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

From report at bugs.python.org  Thu Jul  4 10:33:28 2013
From: report at bugs.python.org (Michelle Arzul)
Date: Thu, 04 Jul 2013 08:33:28 +0000
Subject: [docs] [issue18356] help(numpy) causes segfault on exit
In-Reply-To: <1372924520.77.0.111539946992.issue18356@psf.upfronthosting.co.za>
Message-ID: <1372926808.36.0.949981821048.issue18356@psf.upfronthosting.co.za>


Michelle Arzul added the comment:

I'm no expert, I just found the bug... but I'll try my best.

* exact Python version: 2.7.4 (GCC 4.7.3)
* NumPy version: 1.7.1
* platform (X86, X86_64, ARM): i686
* Kernel: Linux 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:30 UTC 2013 i686 i686 i686 GNU/Linux
* libc: ldd (Ubuntu EGLIBC 2.17-0ubuntu5) 2.17
* compiler: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1)
* terminal application: not sure what you mean
* environment variables:
    TERM="xterm"
    (PAGER is not present)
    LESSCLOSE="/usr/bin/lesspipe %s %s"
    LESSOPEN="| /usr/bin/lesspipe %s"

If you need anything else please let me know.

----------
components: +Documentation -Library (Lib)
versions:  -3rd party

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

From report at bugs.python.org  Thu Jul  4 12:09:41 2013
From: report at bugs.python.org (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Thu, 04 Jul 2013 10:09:41 +0000
Subject: [docs] [issue18353] PyUnicode_WRITE_CHAR macro definition missing
In-Reply-To: <1372873387.67.0.379053408423.issue18353@psf.upfronthosting.co.za>
Message-ID: <1372932581.66.0.20572368358.issue18353@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I'll declare that the documentation is in error. I was pondering adding this macro, and the API changed forth and back several times (also after other people started contributing to the new Unicode API). The API is now what is implemented, and the documentation should follow.

----------
nosy: +loewis

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

From report at bugs.python.org  Thu Jul  4 16:22:52 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 04 Jul 2013 14:22:52 +0000
Subject: [docs] [issue18356] help(numpy) causes segfault on exit
In-Reply-To: <1372924520.77.0.111539946992.issue18356@psf.upfronthosting.co.za>
Message-ID: <1372947772.29.0.949175422059.issue18356@psf.upfronthosting.co.za>


R. David Murray added the comment:

pydoc doesn't do anything special other than import the module.  Well, there's some special code in linecache for getting docstrings from C modules, I think, so that could be something to check. 

Does Ubuntu have local patches to numpy?

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

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

From report at bugs.python.org  Thu Jul  4 16:50:40 2013
From: report at bugs.python.org (Michelle Arzul)
Date: Thu, 04 Jul 2013 14:50:40 +0000
Subject: [docs] [issue18356] help(numpy) causes segfault on exit
In-Reply-To: <1372924520.77.0.111539946992.issue18356@psf.upfronthosting.co.za>
Message-ID: <1372949440.03.0.895811536468.issue18356@psf.upfronthosting.co.za>


Michelle Arzul added the comment:

Apparently it only occurs with the Ubuntu packaged versions of Python and numpy. Somebody who was able to reproduce my problem had it with python-2.7.4-0ubuntu1-amd64 and python-numpy-1:1.7.1-1ubuntu1-amd64 which exhibited the same behaviour. Apparently python-dbg and python-numpy-dbg do not reproduce the error.

----------

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

From report at bugs.python.org  Fri Jul  5 09:45:11 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Fri, 05 Jul 2013 07:45:11 +0000
Subject: [docs] [issue18231] What's new in Python should explain what's new
	in UCD
In-Reply-To: <1371406253.35.0.589040711268.issue18231@psf.upfronthosting.co.za>
Message-ID: <1373010311.22.0.927041633844.issue18231@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

I agree with Martin, mentioning that the database has been updated should be enough.

----------

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

From report at bugs.python.org  Fri Jul  5 18:27:55 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Fri, 05 Jul 2013 16:27:55 +0000
Subject: [docs] [issue18354] http://www.python.org/doc/ has outdated note
In-Reply-To: <1372877234.32.0.505544665385.issue18354@psf.upfronthosting.co.za>
Message-ID: <1373041675.4.0.295589758999.issue18354@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/issue18354>
_______________________________________

From report at bugs.python.org  Fri Jul  5 18:50:02 2013
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 05 Jul 2013 16:50:02 +0000
Subject: [docs] [issue18353] PyUnicode_WRITE_CHAR macro definition missing
In-Reply-To: <1372873387.67.0.379053408423.issue18353@psf.upfronthosting.co.za>
Message-ID: <1373043002.66.0.260216033969.issue18353@psf.upfronthosting.co.za>


STINNER Victor added the comment:

I don't remember where this macro come from. 

It is mention in my review of the PEP (the text of the PEP, not the implementation):
http://mail.python.org/pipermail/python-dev/2011-September/113668.html

PyUnicode_WRITE_CHAR() was removed from the PEP by the following commit:
http://hg.python.org/peps/rev/5c69799e1a94

I'm not sure that the macro ever existed :-)

Anyway, it should be removed from the doc!

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

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

From report at bugs.python.org  Fri Jul  5 19:01:26 2013
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 05 Jul 2013 17:01:26 +0000
Subject: [docs] [issue18356] help(numpy) causes segfault on exit
In-Reply-To: <1372924520.77.0.111539946992.issue18356@psf.upfronthosting.co.za>
Message-ID: <1373043686.21.0.13665144592.issue18356@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Fri Jul  5 19:02:58 2013
From: report at bugs.python.org (STINNER Victor)
Date: Fri, 05 Jul 2013 17:02:58 +0000
Subject: [docs] [issue18356] help(numpy) causes segfault on exit
In-Reply-To: <1372924520.77.0.111539946992.issue18356@psf.upfronthosting.co.za>
Message-ID: <1373043778.89.0.186403416859.issue18356@psf.upfronthosting.co.za>


STINNER Victor added the comment:

> For a full trackdown and workaround of the problem see http://stackoverflow.com/questions/17344974/python-helpnumpy-causes-segfault-on-exit

The gdb trace is not interesting because it stopped at SIGPIPE, which is not an error. Please rerun your program in gdb and ignore SIGPIPE (type "handle SIGPIPE noprint nostop") or continue on PIPE (type "cont"). Then when you get the crash, please copy/paste the gdb traceback here.

----------

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

From report at bugs.python.org  Fri Jul  5 20:30:40 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 05 Jul 2013 18:30:40 +0000
Subject: [docs] [issue18326] Mention keywork only in list.sort docs
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1373049040.41.0.919647963168.issue18326@psf.upfronthosting.co.za>


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


----------
title: Not Clear Docs -> Mention keywork only in list.sort docs
type:  -> enhancement

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

From report at bugs.python.org  Fri Jul  5 20:55:22 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 05 Jul 2013 18:55:22 +0000
Subject: [docs] [issue18354] http://www.python.org/doc/ has outdated note
In-Reply-To: <1372877234.32.0.505544665385.issue18354@psf.upfronthosting.co.za>
Message-ID: <1373050522.43.0.504452274215.issue18354@psf.upfronthosting.co.za>


?ric Araujo added the comment:

The HHGP was an opinionated, distribute-centric user guide, which is now outdated and obsoleted by the upcoming Python packaging user documentation, which will cover more tools and be blessed by Nick Coghlan and the developers of packaging tools.

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

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

From report at bugs.python.org  Fri Jul  5 20:56:29 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 05 Jul 2013 18:56:29 +0000
Subject: [docs] [issue18354] http://www.python.org/doc/ has outdated note
In-Reply-To: <1372877234.32.0.505544665385.issue18354@psf.upfronthosting.co.za>
Message-ID: <1373050588.97.0.706189366088.issue18354@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Also I don?t think we?ll ever have documentation for non-stdlib libs/tools in the standard docs, so the HHGP or new packaging user doc won?t ?be merged into the Python documentation?.

----------

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

From report at bugs.python.org  Fri Jul  5 20:57:14 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 05 Jul 2013 18:57:14 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1373050634.92.0.748243178406.issue18326@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

'keyword argument' refers one to 'argument'. The entry for the latter says that there are only two types of arguments, keyword and positional. That is true as to how actual arguments are passed.

There are 3 possibilities for how a single argument for a parameter might be passed:
standard - positional or keyword
positional only (args for many C functions, not specifically indicated)
keyword only (follow '*' or '*args' after signature.

These are explained in the parameter entry. Keyword-only parameters have to be matched by keyword arguments.

I think it a bit misleading to say "There are two types of arguments". That actually means "There are two ways of passing an argument". Precede it by 'name=' or not. An object is the same whether passed by name or position.

Calling a name a keyword in this context is also misleading since 'keyword' otherwise means a reserved word that cannot be used as a name. Using an actual keyword to name an argument is illegal: 'for = 2' raises.

----------
nosy: +terry.reedy
title: Mention keywork only in list.sort docs -> Mention 'keyword only' for list.sort, improve  glossary.

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

From report at bugs.python.org  Fri Jul  5 21:06:10 2013
From: report at bugs.python.org (Brian Curtin)
Date: Fri, 05 Jul 2013 19:06:10 +0000
Subject: [docs] [issue18354] http://www.python.org/doc/ has outdated note
In-Reply-To: <1372877234.32.0.505544665385.issue18354@psf.upfronthosting.co.za>
Message-ID: <1373051170.7.0.63911431444.issue18354@psf.upfronthosting.co.za>


Brian Curtin added the comment:

Fixed in r14798 of the site.

----------
assignee: docs at python -> brian.curtin
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

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

From report at bugs.python.org  Fri Jul  5 21:58:46 2013
From: report at bugs.python.org (Zachary Ware)
Date: Fri, 05 Jul 2013 19:58:46 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1373054326.28.0.629456302269.issue18326@psf.upfronthosting.co.za>


Zachary Ware added the comment:

How about this patch?

I agree that "types of arguments/parameters" has great potential for confusion, so the glossary has been changed to "kinds of argument/parameter" (dropping the pluralization as well; it is unnecessary).  I think just taking the word "type" out of it makes the rest of each entry unambiguous.

To list.sort, I simply added a line: ":meth:`sort` accepts two arguments which can only be passed by keyword:".  I considered making each parameter's description an indented block after that, but that seems like more change than is really necessary, and the patched version doesn't look too bad to me.

----------
keywords: +patch
nosy: +zach.ware
Added file: http://bugs.python.org/file30781/issue18326.diff

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

From report at bugs.python.org  Fri Jul  5 22:38:43 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 05 Jul 2013 20:38:43 +0000
Subject: [docs] [issue18326] Mention 'keyword only' for list.sort,
	improve  glossary.
In-Reply-To: <1372511136.61.0.278425078947.issue18326@psf.upfronthosting.co.za>
Message-ID: <1373056723.43.0.0652590358315.issue18326@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

The new 'which' should be 'that'. Other than that, looks good to me.

----------

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

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


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


Added file: http://bugs.python.org/file30785/issue18326.that.diff

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

From report at bugs.python.org  Sat Jul  6 00:57:36 2013
From: report at bugs.python.org (Christian Heimes)
Date: Fri, 05 Jul 2013 22:57:36 +0000
Subject: [docs] [issue6128] Consequences of using Py_TPFLAGS_HAVE_GC are
	incompletely	explained
In-Reply-To: <1243457336.14.0.579311647458.issue6128@psf.upfronthosting.co.za>
Message-ID: <1373065056.05.0.604459919469.issue6128@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Python's extension modules aren't consistent. Some places deallocate the object with PyObject_Del(), other places are using PyObject_GC_Del() or simple Py_DECREF().

----------
nosy: +christian.heimes
priority: normal -> low
stage:  -> needs patch
type:  -> enhancement
versions: +Python 3.4

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

From report at bugs.python.org  Sat Jul  6 01:12:36 2013
From: report at bugs.python.org (Christian Heimes)
Date: Fri, 05 Jul 2013 23:12:36 +0000
Subject: [docs] [issue11366] xml.etree.ElementTree.Element: docs should
	mention	immediate subelement
In-Reply-To: <1299029422.8.0.159025283655.issue11366@psf.upfronthosting.co.za>
Message-ID: <1373065956.16.0.0506478786175.issue11366@psf.upfronthosting.co.za>


Christian Heimes added the comment:

The introduction [1] to etree explains it:

Element.findall() finds only elements with a tag which are direct children of the current element. 

IMHO it's also the obvious outcome for anybody familiar with XML and XPath.

[1] http://docs.python.org/3/library/xml.etree.elementtree.html#finding-interesting-elements

----------
nosy: +christian.heimes
resolution:  -> works for me
status: open -> closed

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

From report at bugs.python.org  Sat Jul  6 01:17:06 2013
From: report at bugs.python.org (Christian Heimes)
Date: Fri, 05 Jul 2013 23:17:06 +0000
Subject: [docs] [issue1703592] have a way to ignore nonexisting locales
	in	locale.setlocale
Message-ID: <1373066226.22.0.394474413717.issue1703592@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Jul  6 01:21:11 2013
From: report at bugs.python.org (Christian Heimes)
Date: Fri, 05 Jul 2013 23:21:11 +0000
Subject: [docs] [issue17221] Resort Misc/NEWS
In-Reply-To: <1361135741.75.0.253129131493.issue17221@psf.upfronthosting.co.za>
Message-ID: <1373066470.96.0.749116878268.issue17221@psf.upfronthosting.co.za>


Christian Heimes added the comment:

I think this issue can be closed. :)

----------
nosy: +christian.heimes
resolution:  -> fixed
status: open -> closed

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

From report at bugs.python.org  Sat Jul  6 10:00:10 2013
From: report at bugs.python.org (Senko Rasic)
Date: Sat, 06 Jul 2013 08:00:10 +0000
Subject: [docs] [issue18336] codecs: Link to readline module (history)
	instead of	fd.readline()
In-Reply-To: <1372663191.71.0.440770388569.issue18336@psf.upfronthosting.co.za>
Message-ID: <1373097609.99.0.210076800275.issue18336@psf.upfronthosting.co.za>


Senko Rasic added the comment:

Here's a patch just removing the reference.

Although potentially referencing io.IOBase.readline instead would be more correct, IMHO it'd be just more confusing to users reading the docs.

----------
keywords: +patch
nosy: +senko
Added file: http://bugs.python.org/file30789/codecs-readline-docstring-fix.diff

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

From report at bugs.python.org  Sat Jul  6 10:25:18 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 06 Jul 2013 08:25:18 +0000
Subject: [docs] [issue17860] subprocess docs lack info how to use output
	result
In-Reply-To: <1367159799.26.0.456231833917.issue17860@psf.upfronthosting.co.za>
Message-ID: <3bnQwF66ZZz7LjW@mail.python.org>


Roundup Robot added the comment:

New changeset a2c2ffa1a41c by Ronald Oussoren in branch '3.3':
Issue #17860: explicitly mention that std* streams are opened in binary mode by default.
http://hg.python.org/cpython/rev/a2c2ffa1a41c

New changeset ae8b054155c1 by Ronald Oussoren in branch 'default':
(3.3->default) Issue #17860: explicitly mention that std* streams are opened in binary mode by default.
http://hg.python.org/cpython/rev/ae8b054155c1

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

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

From report at bugs.python.org  Sat Jul  6 10:26:55 2013
From: report at bugs.python.org (Ronald Oussoren)
Date: Sat, 06 Jul 2013 08:26:55 +0000
Subject: [docs] [issue17860] subprocess docs lack info how to use output
	result
In-Reply-To: <1367159799.26.0.456231833917.issue17860@psf.upfronthosting.co.za>
Message-ID: <1373099215.33.0.139010830401.issue17860@psf.upfronthosting.co.za>


Ronald Oussoren added the comment:

The documentation for 3.3 and default now explicitly mentions that the std* streams are opened as binary streams when universal_newlines is false.

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

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

From report at bugs.python.org  Sat Jul  6 13:49:48 2013
From: report at bugs.python.org (Adam Collard)
Date: Sat, 06 Jul 2013 11:49:48 +0000
Subject: [docs] [issue12645] test.support. import_fresh_module - incorrect
	doc
In-Reply-To: <1311789815.76.0.639942891335.issue12645@psf.upfronthosting.co.za>
Message-ID: <1373111388.66.0.232401587959.issue12645@psf.upfronthosting.co.za>


Adam Collard added the comment:

The typo is no longer present, but the docs were still wrong.

----------
nosy: +adam-collard
Added file: http://bugs.python.org/file30803/issue-12645-test-docs

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

From report at bugs.python.org  Sat Jul  6 13:49:56 2013
From: report at bugs.python.org (Elena Oat)
Date: Sat, 06 Jul 2013 11:49:56 +0000
Subject: [docs] [issue16937] -u (unbuffered I/O) command line option
	documentation	mismatch for sys.stdin
In-Reply-To: <1357928522.67.0.838908652159.issue16937@psf.upfronthosting.co.za>
Message-ID: <1373111396.41.0.538400048471.issue16937@psf.upfronthosting.co.za>


Changes by Elena Oat <oat.elena at gmail.com>:


----------
keywords: +patch
Added file: http://bugs.python.org/file30804/issue16937.diff

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

From report at bugs.python.org  Sat Jul  6 18:07:53 2013
From: report at bugs.python.org (Balthazar Rouberol)
Date: Sat, 06 Jul 2013 16:07:53 +0000
Subject: [docs] [issue18384] Add devhelp build instructions to the
	documentation	makefile
Message-ID: <1373126872.99.0.196855788769.issue18384@psf.upfronthosting.co.za>


New submission from Balthazar Rouberol:

The documentation makefile is missing support for Devhelp.

The supplied patch fixes this for the Python 3 branch.
It also edits the ouput of the sphinx build to change the name of the devhelp project.

This is needed to be able to have both versions of documentation (py2 & py3) displayed in Devhelp. This is useful if developers need to access documentation for both versions, such as both maintaining a Python2 project and starting a new project in Python3.

This has been patched in some distributions downstream, but would be nice to have patched upstream. See: https://bugs.launchpad.net/ubuntu/+source/devhelp/+bug/787039

----------
assignee: docs at python
components: Documentation
files: devhelp-build-py3.patch
keywords: patch
messages: 192457
nosy: brouberol, docs at python
priority: normal
severity: normal
status: open
title: Add devhelp build instructions to the documentation makefile
type: enhancement
versions: Python 3.5
Added file: http://bugs.python.org/file30823/devhelp-build-py3.patch

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

From report at bugs.python.org  Sat Jul  6 18:08:46 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 06 Jul 2013 16:08:46 +0000
Subject: [docs] [issue18384] Add devhelp build instructions to the
	documentation	makefile
In-Reply-To: <1373126872.99.0.196855788769.issue18384@psf.upfronthosting.co.za>
Message-ID: <1373126926.09.0.951273344233.issue18384@psf.upfronthosting.co.za>


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


----------
nosy: +georg.brandl
stage:  -> patch review
versions: +Python 3.4 -Python 3.5

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

From report at bugs.python.org  Sat Jul  6 18:10:39 2013
From: report at bugs.python.org (Balthazar Rouberol)
Date: Sat, 06 Jul 2013 16:10:39 +0000
Subject: [docs] [issue18384] Add devhelp build instructions to the
	documentation	makefile
In-Reply-To: <1373126872.99.0.196855788769.issue18384@psf.upfronthosting.co.za>
Message-ID: <1373127039.22.0.844279915681.issue18384@psf.upfronthosting.co.za>


Changes by Balthazar Rouberol <brouberol at imap.cc>:


Removed file: http://bugs.python.org/file30823/devhelp-build-py3.patch

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

From report at bugs.python.org  Sat Jul  6 18:11:17 2013
From: report at bugs.python.org (Balthazar Rouberol)
Date: Sat, 06 Jul 2013 16:11:17 +0000
Subject: [docs] [issue18384] Add devhelp build instructions to the
	documentation	makefile
In-Reply-To: <1373126872.99.0.196855788769.issue18384@psf.upfronthosting.co.za>
Message-ID: <1373127077.8.0.18545738745.issue18384@psf.upfronthosting.co.za>


Changes by Balthazar Rouberol <brouberol at imap.cc>:


Added file: http://bugs.python.org/file30824/devhelp-build-py3.patch

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

From report at bugs.python.org  Sat Jul  6 18:12:52 2013
From: report at bugs.python.org (Balthazar Rouberol)
Date: Sat, 06 Jul 2013 16:12:52 +0000
Subject: [docs] [issue18384] Add devhelp build instructions to the
	documentation	makefile (Python3)
In-Reply-To: <1373126872.99.0.196855788769.issue18384@psf.upfronthosting.co.za>
Message-ID: <1373127172.3.0.61595840569.issue18384@psf.upfronthosting.co.za>


Changes by Balthazar Rouberol <brouberol at imap.cc>:


----------
title: Add devhelp build instructions to the documentation makefile -> Add devhelp build instructions to the documentation makefile (Python3)

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

From report at bugs.python.org  Sat Jul  6 18:14:41 2013
From: report at bugs.python.org (Balthazar Rouberol)
Date: Sat, 06 Jul 2013 16:14:41 +0000
Subject: [docs] [issue18385] Add devhelp build instructions to the
	documentation	makefile (Python2)
Message-ID: <1373127281.72.0.44183394667.issue18385@psf.upfronthosting.co.za>


New submission from Balthazar Rouberol:

The documentation makefile is missing support for Devhelp.

The supplied patch fixes this for the Python 2 branch.

----------
assignee: docs at python
components: Documentation
files: devhelp-build-py2.patch
keywords: patch
messages: 192458
nosy: brouberol, docs at python
priority: normal
severity: normal
status: open
title: Add devhelp build instructions to the documentation makefile (Python2)
type: enhancement
versions: Python 2.7
Added file: http://bugs.python.org/file30825/devhelp-build-py2.patch

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

From report at bugs.python.org  Sat Jul  6 18:23:20 2013
From: report at bugs.python.org (Balthazar Rouberol)
Date: Sat, 06 Jul 2013 16:23:20 +0000
Subject: [docs] [issue18384] Add devhelp build instructions to the
	documentation	makefile
In-Reply-To: <1373126872.99.0.196855788769.issue18384@psf.upfronthosting.co.za>
Message-ID: <1373127800.0.0.566793821487.issue18384@psf.upfronthosting.co.za>


Changes by Balthazar Rouberol <brouberol at imap.cc>:


----------
title: Add devhelp build instructions to the documentation makefile (Python3) -> Add devhelp build instructions to the documentation makefile
versions: +Python 2.7
Added file: http://bugs.python.org/file30826/devhelp-build-py2.patch

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

From report at bugs.python.org  Sat Jul  6 18:23:29 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 06 Jul 2013 16:23:29 +0000
Subject: [docs] [issue18385] Add devhelp build instructions to the
	documentation	makefile (Python2)
In-Reply-To: <1373127281.72.0.44183394667.issue18385@psf.upfronthosting.co.za>
Message-ID: <1373127809.63.0.718400403191.issue18385@psf.upfronthosting.co.za>


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


----------
resolution:  -> duplicate
stage:  -> committed/rejected
status: open -> closed
superseder:  -> Add devhelp build instructions to the documentation makefile

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

From report at bugs.python.org  Sat Jul  6 18:41:26 2013
From: report at bugs.python.org (Alexander Belopolsky)
Date: Sat, 06 Jul 2013 16:41:26 +0000
Subject: [docs] [issue18231] What's new in Python should explain what's new
	in UCD
In-Reply-To: <1371406253.35.0.589040711268.issue18231@psf.upfronthosting.co.za>
Message-ID: <1373128886.4.0.355186714778.issue18231@psf.upfronthosting.co.za>


Alexander Belopolsky added the comment:

It is not easy to figure out the consequences (if any) of UCD change for python grammar from unicode standard release notes.  I went through this exercise for a few releases and I thought it would be useful to share in release notes.  Since there does not seem to be interest, I am closing this issue.

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

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

From report at bugs.python.org  Sun Jul  7 02:26:56 2013
From: report at bugs.python.org (STINNER Victor)
Date: Sun, 07 Jul 2013 00:26:56 +0000
Subject: [docs] [issue18392] Doc: PyObject_Malloc() is not documented
Message-ID: <1373156816.39.0.0842066311974.issue18392@psf.upfronthosting.co.za>


New submission from STINNER Victor:

The implementation of the PEP 445 documents new memory allocator functions. But the old good PyObject_Malloc() is still not documentated!?

----------
assignee: docs at python
components: Documentation
messages: 192505
nosy: docs at python, haypo
priority: normal
severity: normal
status: open
title: Doc: PyObject_Malloc() is not documented
versions: Python 3.4

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

From report at bugs.python.org  Sun Jul  7 09:28:15 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 07 Jul 2013 07:28:15 +0000
Subject: [docs] [issue17860] subprocess docs lack info how to use output
	result
In-Reply-To: <1367159799.26.0.456231833917.issue17860@psf.upfronthosting.co.za>
Message-ID: <3bp1by5Jw7z7Ljk@mail.python.org>


Roundup Robot added the comment:

New changeset f4747e1ce2b1 by Ronald Oussoren in branch '3.3':
Cleanup of documentation change from #17860
http://hg.python.org/cpython/rev/f4747e1ce2b1

New changeset 83810f67d16b by Ronald Oussoren in branch 'default':
(3.3->default) Cleanup of documentation change from #17860
http://hg.python.org/cpython/rev/83810f67d16b

----------

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

From report at bugs.python.org  Sun Jul  7 10:05:06 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sun, 07 Jul 2013 08:05:06 +0000
Subject: [docs] [issue18231] What's new in Python should explain what's new
	in UCD
In-Reply-To: <1371406253.35.0.589040711268.issue18231@psf.upfronthosting.co.za>
Message-ID: <1373184306.43.0.205725518087.issue18231@psf.upfronthosting.co.za>


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


----------
stage: needs patch -> committed/rejected

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

From report at bugs.python.org  Sun Jul  7 17:02:47 2013
From: report at bugs.python.org (Christian Heimes)
Date: Sun, 07 Jul 2013 15:02:47 +0000
Subject: [docs] [issue9119] Python download page needs to mention crypto
	code	in	Windows installer
In-Reply-To: <1277836658.93.0.259031299275.issue9119@psf.upfronthosting.co.za>
Message-ID: <1373209367.92.0.431340924026.issue9119@psf.upfronthosting.co.za>


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


----------
nosy: +christian.heimes
versions: +Python 3.3, Python 3.4

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

From report at bugs.python.org  Sun Jul  7 20:31:55 2013
From: report at bugs.python.org (Christian Heimes)
Date: Sun, 07 Jul 2013 18:31:55 +0000
Subject: [docs] [issue12957] mmap.resize changes memory address of mmap'd
	region
In-Reply-To: <1315686259.57.0.0304440203891.issue12957@psf.upfronthosting.co.za>
Message-ID: <1373221915.89.0.450386683312.issue12957@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sun Jul  7 23:29:50 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sun, 07 Jul 2013 21:29:50 +0000
Subject: [docs] [issue11908] Weird `slice.stop or sys.maxint`
In-Reply-To: <1303493846.17.0.214651551769.issue11908@psf.upfronthosting.co.za>
Message-ID: <1373232590.66.0.115769360032.issue11908@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Jul  8 08:39:54 2013
From: report at bugs.python.org (Ben Finney)
Date: Mon, 08 Jul 2013 06:39:54 +0000
Subject: [docs] [issue12645] test.support. import_fresh_module - incorrect
	doc
In-Reply-To: <1311789815.76.0.639942891335.issue12645@psf.upfronthosting.co.za>
Message-ID: <1373265594.63.0.689293055688.issue12645@psf.upfronthosting.co.za>


Ben Finney added the comment:

I'm reading the existing `test.support.import_fresh_module` docstring, and have re-formatted it for PEP 257 compliance and for reading clarity.

----------
keywords: +patch
nosy: +bignose
Added file: http://bugs.python.org/file30857/issue12645.reformat_docstring.9d22bc60bd4f.patch

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

From report at bugs.python.org  Mon Jul  8 08:42:54 2013
From: report at bugs.python.org (Ben Finney)
Date: Mon, 08 Jul 2013 06:42:54 +0000
Subject: [docs] [issue12645] test.support. import_fresh_module - incorrect
	doc
In-Reply-To: <1311789815.76.0.639942891335.issue12645@psf.upfronthosting.co.za>
Message-ID: <1373265774.57.0.599232668188.issue12645@psf.upfronthosting.co.za>


Ben Finney added the comment:

> import_fresh_module raises an ImportError if *name* can't be imported, or returns None if the fresh module is not found.

The implementation doesn't seem to raise ImportError when a module import fails. Instead, from what I can tell, it captures any ImportError and returns None.

So should the documentation (user docs and docstring) reflect this? Or have I mis-read the implementation?

----------

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

From report at bugs.python.org  Mon Jul  8 09:17:25 2013
From: report at bugs.python.org (Grant)
Date: Mon, 08 Jul 2013 07:17:25 +0000
Subject: [docs] [issue17827] Document codecs.encode and codecs.decode
In-Reply-To: <1366811140.15.0.0983174574305.issue17827@psf.upfronthosting.co.za>
Message-ID: <1373267845.04.0.425234710425.issue17827@psf.upfronthosting.co.za>


Grant added the comment:

codecs module and 'whats new' doc patch for 3.4

----------
keywords: +patch
nosy: +Grant
versions:  -Python 2.7, Python 3.3
Added file: http://bugs.python.org/file30860/17827.diff

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

From report at bugs.python.org  Mon Jul  8 10:50:22 2013
From: report at bugs.python.org (Michelle Arzul)
Date: Mon, 08 Jul 2013 08:50:22 +0000
Subject: [docs] [issue18356] help(numpy) causes segfault on exit
In-Reply-To: <1372924520.77.0.111539946992.issue18356@psf.upfronthosting.co.za>
Message-ID: <1373273422.31.0.774989935684.issue18356@psf.upfronthosting.co.za>


Michelle Arzul added the comment:

This is what I get from gdb:

marzul at Leeward:~$ gdb --args python test.py
GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/python2.7...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/python2.7 test.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".

Program received signal SIGPIPE, Broken pipe.
0xb7fdd424 in __kernel_vsyscall ()
(gdb) cont
Continuing.

Program received signal SIGPIPE, Broken pipe.
0xb7fdd424 in __kernel_vsyscall ()
(gdb) cont
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0xb7e518fc in ?? () from /lib/i386-linux-gnu/libc.so.6
(gdb) cont
Continuing.

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) run
Starting program: /usr/bin/python2.7 test.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".

Program received signal SIGPIPE, Broken pipe.
0xb7fdd424 in __kernel_vsyscall ()
(gdb) cont
Continuing.

Program received signal SIGPIPE, Broken pipe.
0xb7fdd424 in __kernel_vsyscall ()
(gdb) cont
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0xb7e518fc in ?? () from /lib/i386-linux-gnu/libc.so.6
(gdb) where
#0  0xb7e518fc in ?? () from /lib/i386-linux-gnu/libc.so.6
#1  0xb7e45e7c in _IO_default_xsputn () from /lib/i386-linux-gnu/libc.so.6
#2  0xb7e443a1 in _IO_file_xsputn () from /lib/i386-linux-gnu/libc.so.6
#3  0xb7e39025 in fwrite () from /lib/i386-linux-gnu/libc.so.6
#4  0x080ac05b in ?? ()
#5  0x080b6bde in PyEval_EvalFrameEx ()
#6  0x080b71c0 in PyEval_EvalFrameEx ()
#7  0x0811f939 in PyEval_EvalCodeEx ()
#8  0x080b80d4 in PyEval_EvalFrameEx ()
#9  0x080b71c0 in PyEval_EvalFrameEx ()
#10 0x0811f939 in PyEval_EvalCodeEx ()
#11 0x080b7265 in PyEval_EvalFrameEx ()
#12 0x080b71c0 in PyEval_EvalFrameEx ()
#13 0x0811f939 in PyEval_EvalCodeEx ()
#14 0x081203ee in ?? ()
#15 0x080e11f9 in ?? ()
#16 0x080e3daf in PyObject_Call ()
#17 0x08129483 in ?? ()
#18 0x080b8a3e in PyEval_EvalFrameEx ()
#19 0x0811f939 in PyEval_EvalCodeEx ()
#20 0x0812029e in ?? ()
#21 0x080e11f9 in ?? ()
#22 0x080e3daf in PyObject_Call ()
---Type <return> to continue, or q <return> to quit---
#23 0x0816dd88 in ?? ()
#24 0x080b7615 in PyEval_EvalFrameEx ()
#25 0x0811f939 in PyEval_EvalCodeEx ()
#26 0x081836c7 in PyEval_EvalCode ()
#27 0x08183b7d in ?? ()
#28 0x080a6032 in PyRun_FileExFlags ()
#29 0x080a65f8 in PyRun_SimpleFileExFlags ()
#30 0x080a74af in Py_Main ()
#31 0x080a7581 in main ()
(gdb)

----------

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

From report at bugs.python.org  Mon Jul  8 12:36:52 2013
From: report at bugs.python.org (Xue Fuqiao)
Date: Mon, 08 Jul 2013 10:36:52 +0000
Subject: [docs] [issue18403] Minor bug in The Python Tutorial
Message-ID: <1373279812.84.0.20851379601.issue18403@psf.upfronthosting.co.za>


New submission from Xue Fuqiao:

In http://docs.python.org/3.3/tutorial/introduction.html#strings:

  In addition to indexing, slicing is also supported. While indexing is
  used to obtain individual characters, slicing allows you to obtain
  substring:
  >>> word[0:2]  # characters from position 0 (included) to 2 (excluded)
  'Py'
  >>> word[2:5]  # characters from position 2 (included) to 4 (excluded)
  'tho'

I think the second comment should be "from position 2 to 5", not "to 4".
I'm a Python newbie, sorry if it's not a bug.

----------
assignee: docs at python
components: Documentation
messages: 192632
nosy: docs at python, xfq
priority: normal
severity: normal
status: open
title: Minor bug in The Python Tutorial
versions: Python 3.3

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

From report at bugs.python.org  Mon Jul  8 14:26:40 2013
From: report at bugs.python.org (Madison May)
Date: Mon, 08 Jul 2013 12:26:40 +0000
Subject: [docs] [issue18403] Minor bug in The Python Tutorial
In-Reply-To: <1373279812.84.0.20851379601.issue18403@psf.upfronthosting.co.za>
Message-ID: <1373286400.27.0.514461531511.issue18403@psf.upfronthosting.co.za>


Madison May added the comment:

Nope, definitely an error!  Good catch, Xue.

----------
nosy: +madison.may

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

From report at bugs.python.org  Mon Jul  8 17:53:44 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 08 Jul 2013 15:53:44 +0000
Subject: [docs] [issue18403] Minor bug in The Python Tutorial
In-Reply-To: <1373279812.84.0.20851379601.issue18403@psf.upfronthosting.co.za>
Message-ID: <3bprml45LkzPCN@mail.python.org>


Roundup Robot added the comment:

New changeset 6f16fa5223cc by Ezio Melotti in branch '3.3':
#18403: fix an off-by-one typo noticed by Xue Fuqiao.
http://hg.python.org/cpython/rev/6f16fa5223cc

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

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

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

From report at bugs.python.org  Mon Jul  8 17:54:37 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 08 Jul 2013 15:54:37 +0000
Subject: [docs] [issue18403] Minor bug in The Python Tutorial
In-Reply-To: <1373279812.84.0.20851379601.issue18403@psf.upfronthosting.co.za>
Message-ID: <1373298877.86.0.809086038416.issue18403@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the report!

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

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

From report at bugs.python.org  Mon Jul  8 17:56:14 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 08 Jul 2013 15:56:14 +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: <1373298974.28.0.401830210513.issue14097@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

This still needs to be backported to 2.7.  There's also a typo reported in #18403 that should be fixed before the backport.

----------
assignee: docs at python -> ezio.melotti

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

From report at bugs.python.org  Tue Jul  9 05:13:26 2013
From: report at bugs.python.org (paul j3)
Date: Tue, 09 Jul 2013 03:13:26 +0000
Subject: [docs] [issue16418] argparse with many choices can generate
	absurdly long	usage message
In-Reply-To: <1352157111.52.0.432994430995.issue16418@psf.upfronthosting.co.za>
Message-ID: <1373339606.15.0.958633383957.issue16418@psf.upfronthosting.co.za>


paul j3 added the comment:

In the patch I just posted to http://bugs.python.org/issue16468 I address this long list issue in several ways:

In the Usage line, the metavar gives the user an alternative

In the expanded help line the user can just omit the '%(choices)s' 

In _check_value(), I implemented a numpy like summarize format for choice lists longer than 15   '{1,2,3,...,18,19}'.

----------

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

From report at bugs.python.org  Tue Jul  9 13:37:13 2013
From: report at bugs.python.org (Christian Heimes)
Date: Tue, 09 Jul 2013 11:37:13 +0000
Subject: [docs] [issue18412] Minor problem in PEP 8
In-Reply-To: <1373366713.85.0.45952908225.issue18412@psf.upfronthosting.co.za>
Message-ID: <1373369833.75.0.430844649449.issue18412@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
nosy: +docs at python
priority: normal -> low

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

From report at bugs.python.org  Tue Jul  9 15:21:46 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Tue, 09 Jul 2013 13:21:46 +0000
Subject: [docs] [issue12645] test.support. import_fresh_module - incorrect
	doc
In-Reply-To: <1311789815.76.0.639942891335.issue12645@psf.upfronthosting.co.za>
Message-ID: <1373376106.63.0.0334533337915.issue12645@psf.upfronthosting.co.za>


Eli Bendersky added the comment:

_save_and_remove module can also raise ImportError

----------

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

From report at bugs.python.org  Tue Jul  9 15:24:24 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Tue, 09 Jul 2013 13:24:24 +0000
Subject: [docs] [issue12645] test.support. import_fresh_module - incorrect
	doc
In-Reply-To: <1311789815.76.0.639942891335.issue12645@psf.upfronthosting.co.za>
Message-ID: <1373376263.93.0.756220938895.issue12645@psf.upfronthosting.co.za>


Eli Bendersky added the comment:

A single patch for both the ReST doc and docstring would be helpful. Except formatting, their contents can be the same.

----------

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

From report at bugs.python.org  Tue Jul  9 15:27:52 2013
From: report at bugs.python.org (Barry A. Warsaw)
Date: Tue, 09 Jul 2013 13:27:52 +0000
Subject: [docs] [issue18412] Minor problem in PEP 8
In-Reply-To: <1373366713.85.0.45952908225.issue18412@psf.upfronthosting.co.za>
Message-ID: <1373376471.96.0.906304253397.issue18412@psf.upfronthosting.co.za>


Barry A. Warsaw added the comment:

I clarified the wording.

----------
nosy: +barry
resolution:  -> fixed
status: open -> closed

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

From report at bugs.python.org  Tue Jul  9 16:00:06 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 09 Jul 2013 14:00:06 +0000
Subject: [docs] [issue18384] Add devhelp build instructions to the
	documentation	makefile
In-Reply-To: <1373126872.99.0.196855788769.issue18384@psf.upfronthosting.co.za>
Message-ID: <1373378406.52.0.78003187724.issue18384@psf.upfronthosting.co.za>


R. David Murray added the comment:

I'm not sure that this belongs in core, but I'll certainly defer to Georg on that :).  If it does go in, the help string should explain what 'devhelp' does, since it isn't obvious from the name (for a non-GNOME user...I had to google it).

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

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

From report at bugs.python.org  Tue Jul  9 18:15:20 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 09 Jul 2013 16:15:20 +0000
Subject: [docs] [issue18389] document that os.path.relpath does not
	interrogate the	file system
In-Reply-To: <1373141672.93.0.461698296017.issue18389@psf.upfronthosting.co.za>
Message-ID: <1373386520.19.0.667351390426.issue18389@psf.upfronthosting.co.za>


R. David Murray added the comment:

That's a good point.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
resolution: rejected -> 
stage: committed/rejected -> needs patch
status: closed -> open
title: os.path.relpath gives incorrect results if start parameters is not a directory -> document that os.path.relpath does not interrogate the file system
versions: +Python 3.3, Python 3.4

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

From report at bugs.python.org  Wed Jul 10 01:57:33 2013
From: report at bugs.python.org (Michael Dickens)
Date: Tue, 09 Jul 2013 23:57:33 +0000
Subject: [docs] [issue16665] doc for builtin hex() is poor
In-Reply-To: <1355257997.08.0.0348964643873.issue16665@psf.upfronthosting.co.za>
Message-ID: <1373414253.49.0.114017658558.issue16665@psf.upfronthosting.co.za>


Michael Dickens added the comment:

I used the wording suggested by rurpy with some changes. I also added a few examples.

----------
keywords: +patch
nosy: +MTGandP
Added file: http://bugs.python.org/file30882/issue16665.diff

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

From report at bugs.python.org  Wed Jul 10 03:03:23 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Wed, 10 Jul 2013 01:03:23 +0000
Subject: [docs] [issue16665] doc for builtin hex() is poor
In-Reply-To: <1355257997.08.0.0348964643873.issue16665@psf.upfronthosting.co.za>
Message-ID: <1373418203.52.0.398766207712.issue16665@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Personally, I think this is overkill.  Can you capture the essence of what you want to say in something short and sweet that gets to the point?  We're not looking for a complete spec.  You just need to say basically what the function does.

----------

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

From report at bugs.python.org  Wed Jul 10 14:58:32 2013
From: report at bugs.python.org (andrew cooke)
Date: Wed, 10 Jul 2013 12:58:32 +0000
Subject: [docs] [issue18423] Document limitations on -m
Message-ID: <1373461112.24.0.280779659137.issue18423@psf.upfronthosting.co.za>


New submission from andrew cooke:

Apparently the limited support for -m is standard behaviour - see http://bugs.python.org/issue18422 - but it's not documented at http://docs.python.org/3/using/cmdline.html#cmdoption-m

That should say, somewhere, that it only applies to leaf modules and packages.

----------
assignee: docs at python
components: Documentation
messages: 192804
nosy: acooke, docs at python
priority: normal
severity: normal
status: open
title: Document limitations on -m

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

From report at bugs.python.org  Wed Jul 10 15:11:34 2013
From: report at bugs.python.org (Marco Buttu)
Date: Wed, 10 Jul 2013 13:11:34 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
Message-ID: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>


New submission from Marco Buttu:

The documentaion of sum():

    Returns the sum of a sequence of numbers (NOT strings) plus the 
    value of parameter 'start' (which defaults to 0).  
    When the sequence is empty, returns start.

A. According to the PEP-8 it should be: "Return the sum...", and
   "When the sequence is empty, return start.", like the other docs. 
   For instance:

   >>> print(len.__doc__)
   len(object) -> integer

   Return the number of items of a sequence or mapping.

B. When the second argument is a tuple or a list, you can add sequences
   of sequences:

   >>> sum([['a', 'b', 'c'], [4]], [])
   ['a', 'b', 'c', 4]
   >>> sum(((1, 2, 3), (1,)), (1,))
   (1, 1, 2, 3, 1)

C. sum() takes not just sequences:

   >>> sum({1: 'one', 2: 'two'})
   3

Maybe it is not a good idea to give a complete description of sum() in the docstring, but perhaps something "good enough". In any case, I think the lack of the PEP-8 recommendation should be fixed.

----------
assignee: docs at python
components: Documentation
messages: 192805
nosy: docs at python, marco.buttu
priority: normal
severity: normal
status: open
title: sum() does not return only the sum of a sequence of numbers + PEP8 reccomandation
versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3

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

From report at bugs.python.org  Wed Jul 10 15:51:38 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 10 Jul 2013 13:51:38 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
In-Reply-To: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>
Message-ID: <1373464298.57.0.246847948522.issue18424@psf.upfronthosting.co.za>


R. David Murray added the comment:

Perhaps we could add something like "Also works, though possibly inefficiently, on any iterable whose elements support addition".  The biggest part of the sphinx docs for this are about what to use instead, and that doesn't really seem appropriate for a docstring.  So it may indeed be best to just not mention it in the docstring.

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

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

From report at bugs.python.org  Wed Jul 10 15:52:11 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 10 Jul 2013 13:52:11 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
In-Reply-To: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>
Message-ID: <1373464331.43.0.487963313152.issue18424@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.4 -Python 3.1, Python 3.2

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

From report at bugs.python.org  Wed Jul 10 16:04:42 2013
From: report at bugs.python.org (Ronald Oussoren)
Date: Wed, 10 Jul 2013 14:04:42 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
In-Reply-To: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>
Message-ID: <1373465082.73.0.180468151718.issue18424@psf.upfronthosting.co.za>


Ronald Oussoren added the comment:

There's an annoyingly long discussion about sum() on python-ideas.

IMHO the documentation should mention, as it does now, that sum is intended to be used with a sequence of numbers even it does work with most objects that support the + operator (such as by implementing __add__). In particular, using sum with a sequence of lists or tuples is extremely inefficient.

The fact that sum({1:'a', 2: 'b'}) works is a side effect of the how python works with sequences and IMHO doesn't have to be documented in every function that accepts a sequence as an argument.

----------
nosy: +ronaldoussoren

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

From report at bugs.python.org  Wed Jul 10 16:29:22 2013
From: report at bugs.python.org (Brett Cannon)
Date: Wed, 10 Jul 2013 14:29:22 +0000
Subject: [docs] [issue18423] Document limitations on -m
In-Reply-To: <1373461112.24.0.280779659137.issue18423@psf.upfronthosting.co.za>
Message-ID: <1373466562.11.0.788325445663.issue18423@psf.upfronthosting.co.za>


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


----------
keywords: +easy
stage:  -> needs patch
versions: +Python 3.3

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

From report at bugs.python.org  Wed Jul 10 16:44:41 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 10 Jul 2013 14:44:41 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
In-Reply-To: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>
Message-ID: <1373467481.24.0.747104617924.issue18424@psf.upfronthosting.co.za>


R. David Murray added the comment:

OK, so your vote is to leave the doc string alone (except for the PEP8 changes), right?

----------

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

From report at bugs.python.org  Wed Jul 10 16:50:08 2013
From: report at bugs.python.org (Ronald Oussoren)
Date: Wed, 10 Jul 2013 14:50:08 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
In-Reply-To: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>
Message-ID: <1373467808.62.0.217684828752.issue18424@psf.upfronthosting.co.za>


Ronald Oussoren added the comment:

Yes, the docstring isn't meant to be exhaustive documentation. The manual is more exhaustive and, as you noted, already contains links to alternatives.

----------

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

From report at bugs.python.org  Wed Jul 10 17:13:37 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Wed, 10 Jul 2013 15:13:37 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
In-Reply-To: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>
Message-ID: <1373469217.51.0.594992673902.issue18424@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Currently sum() is intended to work with numbers, explicitly forbids strings (as noted in the docstring), but also works with other types (even though it's inefficient).

If we want to document this, a possible wording might be:
    Returns the sum of a sequence of numbers plus the 
    value of parameter 'start' (which defaults to 0).  
    When the sequence is empty, returns start.
    Using sum() with a sequence of strings is not allowed,
    and might be inefficient with sequences of other types.

We should also consider that the implementation/behavior might change in future, but we can always update the docstring again.

+1 on the PEP 8 changes.

----------
nosy: +ezio.melotti

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

From report at bugs.python.org  Wed Jul 10 17:21:31 2013
From: report at bugs.python.org (Marco Buttu)
Date: Wed, 10 Jul 2013 15:21:31 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
In-Reply-To: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>
Message-ID: <1373469691.51.0.592655347063.issue18424@psf.upfronthosting.co.za>


Marco Buttu added the comment:

By reading the Ronald's comment, I realized it is better to keep it simple, so I agree with him.

The "extremely inefficient" reason seems to be less important (Python 3.3):

$ python -m timeit -s "a=['a']*10000; b=['b']*10000; a+b"
100000000 loops, best of 3: 0.00831 usec per loop
$ python -m timeit -s "a=['a']*10000; b=['b']*10000; sum([a, b], [])"
100000000 loops, best of 3: 0.0087 usec per loop

----------

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

From report at bugs.python.org  Wed Jul 10 17:33:08 2013
From: report at bugs.python.org (Ronald Oussoren)
Date: Wed, 10 Jul 2013 15:33:08 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
In-Reply-To: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>
Message-ID: <1373470388.55.0.429274407892.issue18424@psf.upfronthosting.co.za>


Ronald Oussoren added the comment:

Appending a sequence of lists with sum is inefficient because it (currently) does a lot of copying, and that gets noticable when you sum a larger number of lists

Note how using sum for add 200 lists is more than twice as long as adding 100 lists:

ronald at gondolin[0]$ python -m timeit -s "lists=[['a']*100 for i in range(100)]" "sum(lists, [])"
100 loops, best of 3: 2.04 msec per loop


ronald at gondolin[0]$ python -m timeit -s "lists=[['a']*100 for i in range(200)]" "sum(lists, [])"
100 loops, best of 3: 9.2 msec per loop


Also note how using itertools.chain is both a lot faster and behaves better:

ronald at gondolin[0]$ python -m timeit -s "import itertools; lists=[['a']*100 for i in range(100)]" "list(itertools.chain.from_iterable(lists))"
10000 loops, best of 3: 165 usec per loop


ronald at gondolin[0]$ python -m timeit -s "import itertools; lists=[['a']*100 for i in range(100)]" "list(itertools.chain.from_iterable(lists))"
10000 loops, best of 3: 155 usec per loop

(I used python2.7 for this, the same behavior can be seem with python 3).

See also #18305, which proposed a small change to how sum works which would fix the performance problems for summing a sequence of lists (before going too far and proposing to add special-case tuples and string)

----------

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

From report at bugs.python.org  Wed Jul 10 21:11:02 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 10 Jul 2013 19:11:02 +0000
Subject: [docs] [issue12731] python lib re uses obsolete sense of \w in
	full	violation of UTS#18 RL1.2a
In-Reply-To: <1313090311.62.0.0473644856742.issue12731@psf.upfronthosting.co.za>
Message-ID: <1373483462.61.0.731824332115.issue12731@psf.upfronthosting.co.za>


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


----------
versions: +Python 3.4 -Python 3.2

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

From report at bugs.python.org  Wed Jul 10 22:23:47 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 10 Jul 2013 20:23:47 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
In-Reply-To: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>
Message-ID: <3brBgQ2cF8z7Ljk@mail.python.org>


Roundup Robot added the comment:

New changeset 4b3b87719e2c by R David Murray in branch '3.3':
#18424: PEP8ify the tense of the sum docstring.
http://hg.python.org/cpython/rev/4b3b87719e2c

New changeset 38b42ffdf86b by R David Murray in branch 'default':
Merge: #18424: PEP8ify the tense of the sum docstring.
http://hg.python.org/cpython/rev/38b42ffdf86b

New changeset c5f5b5e89a94 by R David Murray in branch '2.7':
#18424: PEP8ify the tense of the sum docstring.
http://hg.python.org/cpython/rev/c5f5b5e89a94

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

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

From report at bugs.python.org  Wed Jul 10 22:24:50 2013
From: report at bugs.python.org (R. David Murray)
Date: Wed, 10 Jul 2013 20:24:50 +0000
Subject: [docs] [issue18424] sum() does not return only the sum of a
	sequence of	numbers + PEP8 reccomandation
In-Reply-To: <1373461894.57.0.746181395812.issue18424@psf.upfronthosting.co.za>
Message-ID: <1373487890.34.0.996063703265.issue18424@psf.upfronthosting.co.za>


R. David Murray added the comment:

Ok, pep8 changes committed.

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

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

From report at bugs.python.org  Thu Jul 11 09:24:27 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 11 Jul 2013 07:24:27 +0000
Subject: [docs] [issue11908] Weird `slice.stop or sys.maxint`
In-Reply-To: <1303493846.17.0.214651551769.issue11908@psf.upfronthosting.co.za>
Message-ID: <1373527467.67.0.292550329767.issue11908@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Closing for the reasons lists above.

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

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

From report at bugs.python.org  Thu Jul 11 09:52:21 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Thu, 11 Jul 2013 07:52:21 +0000
Subject: [docs] [issue11945] Adopt and document consistent semantics for
	handling NaN	values in containers
In-Reply-To: <1303962145.0.0.00759154980454.issue11945@psf.upfronthosting.co.za>
Message-ID: <1373529141.66.0.145414641669.issue11945@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

I think this should be closed.  AFAICT it is of interest to a very tiny subset of the human species and as near as I can tell that subset doesn't include people in the numeric and statistics community (the ones who actually use NaNs as placeholders for missing values).

So much code (and human reasoning) assumes that identity-implies-equality, that is would be easier to document the exception to expectation than to try to find every place in every module where the assumption is present (implicitly or explicitly).  Instead, it would be better to document that distinct float('NaN') objects are never equal to one another and that identical float('NaN') objects may or may not compare equal in various implementation dependent circumstances.

----------

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

From report at bugs.python.org  Thu Jul 11 17:33:26 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 11 Jul 2013 15:33:26 +0000
Subject: [docs] [issue18336] codecs: Link to readline module (history)
	instead of	fd.readline()
In-Reply-To: <1372663191.71.0.440770388569.issue18336@psf.upfronthosting.co.za>
Message-ID: <3brh9x6S8Jz7LjY@mail.python.org>


Roundup Robot added the comment:

New changeset 7e186bb1642c by Serhiy Storchaka in branch '2.7':
Issue #18336. Fix a link to StreamReader's read() method.
http://hg.python.org/cpython/rev/7e186bb1642c

New changeset 8dd67c20cab7 by Serhiy Storchaka in branch '3.3':
Issue #18336. Fix a link to StreamReader's read() method.
http://hg.python.org/cpython/rev/8dd67c20cab7

New changeset a53ac166fa58 by Serhiy Storchaka in branch 'default':
Issue #18336. Fix a link to StreamReader's read() method.
http://hg.python.org/cpython/rev/a53ac166fa58

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

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

From report at bugs.python.org  Thu Jul 11 17:34:56 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Thu, 11 Jul 2013 15:34:56 +0000
Subject: [docs] [issue18336] codecs: Link to readline module (history)
	instead of	fd.readline()
In-Reply-To: <1372663191.71.0.440770388569.issue18336@psf.upfronthosting.co.za>
Message-ID: <1373556896.91.0.520615025323.issue18336@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Actually it should be a link to the read() method.

----------
resolution:  -> fixed
stage: needs patch -> committed/rejected

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

From report at bugs.python.org  Thu Jul 11 18:30:10 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 11 Jul 2013 16:30:10 +0000
Subject: [docs] [issue17987] test.support.captured_stderr,
	captured_stdin not documented
In-Reply-To: <1368653423.88.0.898801742943.issue17987@psf.upfronthosting.co.za>
Message-ID: <3brjRP0Jh5z7Lk9@mail.python.org>


Roundup Robot added the comment:

New changeset af2416c2e27c by R David Murray in branch '3.3':
#17987: properly document support.captured_xxx.
http://hg.python.org/cpython/rev/af2416c2e27c

New changeset d0f7f1996001 by R David Murray in branch 'default':
Merge #17987: properly document support.captured_xxx.
http://hg.python.org/cpython/rev/d0f7f1996001

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

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

From report at bugs.python.org  Thu Jul 11 18:30:52 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 11 Jul 2013 16:30:52 +0000
Subject: [docs] [issue17987] test.support.captured_stderr,
	captured_stdin not documented
In-Reply-To: <1368653423.88.0.898801742943.issue17987@psf.upfronthosting.co.za>
Message-ID: <1373560252.68.0.725649349108.issue17987@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks, Dmi.

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

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

From report at bugs.python.org  Thu Jul 11 20:03:41 2013
From: report at bugs.python.org (Madison May)
Date: Thu, 11 Jul 2013 18:03:41 +0000
Subject: [docs] [issue18389] document that os.path.relpath does not
	interrogate the	file system
In-Reply-To: <1373141672.93.0.461698296017.issue18389@psf.upfronthosting.co.za>
Message-ID: <1373565821.25.0.694486104194.issue18389@psf.upfronthosting.co.za>


Madison May added the comment:

Patch for 3.4 added.  I tried to keep things short and sweet.

----------
Added file: http://bugs.python.org/file30892/Issue18389_3-4.patch

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

From report at bugs.python.org  Thu Jul 11 21:01:30 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 11 Jul 2013 19:01:30 +0000
Subject: [docs] [issue18085] Verifying refcounts.dat
In-Reply-To: <1369768958.38.0.697954786488.issue18085@psf.upfronthosting.co.za>
Message-ID: <3brmp159XQzRnB@mail.python.org>


Roundup Robot added the comment:

New changeset ffe24e3e7a2a by Serhiy Storchaka in branch '3.3':
Issue #18085: Add missed const modifier for some entries in refcounts.dat.
http://hg.python.org/cpython/rev/ffe24e3e7a2a

New changeset 6587fd3d89ae by Serhiy Storchaka in branch 'default':
Issue #18085: Add missed const modifier for some entries in refcounts.dat.
http://hg.python.org/cpython/rev/6587fd3d89ae

----------

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

From report at bugs.python.org  Thu Jul 11 21:59:04 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 11 Jul 2013 19:59:04 +0000
Subject: [docs] [issue18044] Email headers do not properly decode to unicode.
In-Reply-To: <1369310256.22.0.862828757307.issue18044@psf.upfronthosting.co.za>
Message-ID: <3brp4R3Jr9z7Ljj@mail.python.org>


Roundup Robot added the comment:

New changeset 4acb822f4c43 by R David Murray in branch '3.3':
#18044: Fix parsing of encoded words of the form =?utf8?q?=XX...?=
http://hg.python.org/cpython/rev/4acb822f4c43

New changeset 32c6cfffbddd by R David Murray in branch 'default':
Merge: #18044: Fix parsing of encoded words of the form =?utf8?q?=XX...?=
http://hg.python.org/cpython/rev/32c6cfffbddd

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

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

From report at bugs.python.org  Thu Jul 11 22:06:03 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 11 Jul 2013 20:06:03 +0000
Subject: [docs] [issue18044] Email headers do not properly decode to unicode.
In-Reply-To: <1369310256.22.0.862828757307.issue18044@psf.upfronthosting.co.za>
Message-ID: <1373573163.53.0.347259075375.issue18044@psf.upfronthosting.co.za>


R. David Murray added the comment:

This is actually two separate bugs, both a bit embarrassing.  The first one (that I just fixed) is that when parsing an encoded word I was only checking for decimal digits after an '=' (instead of the correct hex digits) when trying to do robust detection of encoded word limits.  

The second (the address one) is due to the fact that somewhere between stopping my full time work on the email project and actually committing the code, I lost track of the fact that I never implemented encoded word parsing for anything other than unstructured headers.  The infrastructure is there, I just need to write tests and hook it up.  

I'm going to open a separate issue for that.

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

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

From report at bugs.python.org  Thu Jul 11 22:11:20 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 11 Jul 2013 20:11:20 +0000
Subject: [docs] [issue18044] Email headers do not properly decode to unicode.
In-Reply-To: <1369310256.22.0.862828757307.issue18044@psf.upfronthosting.co.za>
Message-ID: <1373573480.88.0.110408449593.issue18044@psf.upfronthosting.co.za>


R. David Murray added the comment:

The issue for the second bug is issue 18431.

----------

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

From report at bugs.python.org  Thu Jul 11 22:48:41 2013
From: report at bugs.python.org (Dmi Baranov)
Date: Thu, 11 Jul 2013 20:48:41 +0000
Subject: [docs] [issue17987] test.support.captured_stderr,
	captured_stdin not documented
In-Reply-To: <1368653423.88.0.898801742943.issue17987@psf.upfronthosting.co.za>
Message-ID: <1373575721.44.0.266537540732.issue17987@psf.upfronthosting.co.za>


Dmi Baranov added the comment:

Yeah, my first patch applied :) thanks, David

----------

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

From report at bugs.python.org  Fri Jul 12 15:02:08 2013
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 12 Jul 2013 13:02:08 +0000
Subject: [docs] [issue18433] Clarify venv docs about which methods check
	for	pre-existing paths
Message-ID: <1373634128.21.0.571216700722.issue18433@psf.upfronthosting.co.za>


New submission from Brett Cannon:

E.g. setup_python and create_directories both check that the paths they will create pre-exist, but the docs don't mention this.

----------
assignee: docs at python
components: Documentation
messages: 192938
nosy: brett.cannon, carljm, docs at python
priority: normal
severity: normal
status: open
title: Clarify venv docs about which methods check for pre-existing paths
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Jul 12 15:03:54 2013
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 12 Jul 2013 13:03:54 +0000
Subject: [docs] [issue18434] Update venv example to use setuptools
Message-ID: <1373634234.22.0.916403882512.issue18434@psf.upfronthosting.co.za>


New submission from Brett Cannon:

Now that Distribute is just a shell for setuptools 0.8, the example in the venv docs for installing pip and setuptools in a venv should be updated to use setuptools (in case anyone uses that code as a script themselves).

----------
assignee: docs at python
components: Documentation
messages: 192939
nosy: brett.cannon, carljm, docs at python
priority: normal
severity: normal
status: open
title: Update venv example to use setuptools
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Fri Jul 12 19:55:08 2013
From: report at bugs.python.org (Corey Brune)
Date: Fri, 12 Jul 2013 17:55:08 +0000
Subject: [docs] [issue18353] PyUnicode_WRITE_CHAR macro definition missing
In-Reply-To: <1372873387.67.0.379053408423.issue18353@psf.upfronthosting.co.za>
Message-ID: <1373651708.71.0.617961147691.issue18353@psf.upfronthosting.co.za>


Corey Brune added the comment:

Hello all,
I removed the reference to PyUnicode_WRITE_CHAR macro in unicode.rst. 

Thanks,
Corey

----------
keywords: +patch
nosy: +cbrune
Added file: http://bugs.python.org/file30903/unicode.rst.patch

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

From report at bugs.python.org  Fri Jul 12 20:35:54 2013
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 12 Jul 2013 18:35:54 +0000
Subject: [docs] [issue18434] Update venv example to use setuptools
In-Reply-To: <1373634234.22.0.916403882512.issue18434@psf.upfronthosting.co.za>
Message-ID: <1373654154.77.0.838414205993.issue18434@psf.upfronthosting.co.za>


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


----------
nosy: +vinay.sajip

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

From report at bugs.python.org  Fri Jul 12 20:36:03 2013
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 12 Jul 2013 18:36:03 +0000
Subject: [docs] [issue18433] Clarify venv docs about which methods check
	for	pre-existing paths
In-Reply-To: <1373634128.21.0.571216700722.issue18433@psf.upfronthosting.co.za>
Message-ID: <1373654163.69.0.98892430489.issue18433@psf.upfronthosting.co.za>


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


----------
nosy: +vinay.sajip

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

From report at bugs.python.org  Fri Jul 12 21:42:56 2013
From: report at bugs.python.org (Vinay Sajip)
Date: Fri, 12 Jul 2013 19:42:56 +0000
Subject: [docs] [issue18433] Clarify venv docs about which methods check
	for	pre-existing paths
In-Reply-To: <1373634128.21.0.571216700722.issue18433@psf.upfronthosting.co.za>
Message-ID: <1373658176.32.0.34657632581.issue18433@psf.upfronthosting.co.za>


Vinay Sajip added the comment:

I noticed that create_directories is now ensure_directories in the code, but the docs don't reflect this. I've posted changes, do they cover your concerns or have I missed something?

----------
assignee: docs at python -> vinay.sajip
keywords: +patch
stage:  -> patch review
Added file: http://bugs.python.org/file30905/changes.diff

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

From report at bugs.python.org  Fri Jul 12 21:58:28 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 12 Jul 2013 19:58:28 +0000
Subject: [docs] [issue18434] Update venv example to use setuptools
In-Reply-To: <1373634234.22.0.916403882512.issue18434@psf.upfronthosting.co.za>
Message-ID: <3bsQ1H4bxjzPX7@mail.python.org>


Roundup Robot added the comment:

New changeset 1641a03dbe7b by Vinay Sajip in branch '3.3':
Issue #18434: Updated example script in venv docs to use setuptools rather than Distribute.
http://hg.python.org/cpython/rev/1641a03dbe7b

New changeset 24a55f04a571 by Vinay Sajip in branch 'default':
Closes #18434: Merged documentation update from 3.3.
http://hg.python.org/cpython/rev/24a55f04a571

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

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

From report at bugs.python.org  Fri Jul 12 22:12:00 2013
From: report at bugs.python.org (Brett Cannon)
Date: Fri, 12 Jul 2013 20:12:00 +0000
Subject: [docs] [issue18433] Clarify venv docs about which methods check
	for	pre-existing paths
In-Reply-To: <1373658176.32.0.34657632581.issue18433@psf.upfronthosting.co.za>
Message-ID: <CAP1=2W5sRaRspRZU0Sr5tS8w9YoVTNUz+UV4Sku5=aMHYhGvLw@mail.gmail.com>


Brett Cannon added the comment:

LGTM

On Fri, Jul 12, 2013 at 3:42 PM, Vinay Sajip <report at bugs.python.org> wrote:

>
> Vinay Sajip added the comment:
>
> I noticed that create_directories is now ensure_directories in the code,
> but the docs don't reflect this. I've posted changes, do they cover your
> concerns or have I missed something?
>
> ----------
> assignee: docs at python -> vinay.sajip
> keywords: +patch
> stage:  -> patch review
> Added file: http://bugs.python.org/file30905/changes.diff
>
> _______________________________________
> Python tracker <report at bugs.python.org>
> <http://bugs.python.org/issue18433>
> _______________________________________
>

----------

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

From report at bugs.python.org  Fri Jul 12 22:46:16 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 12 Jul 2013 20:46:16 +0000
Subject: [docs] [issue18434] Update venv example to use setuptools
In-Reply-To: <1373634234.22.0.916403882512.issue18434@psf.upfronthosting.co.za>
Message-ID: <3bsR4S21hRz7Ljl@mail.python.org>


Roundup Robot added the comment:

New changeset f8c3d05994e4 by Vinay Sajip in branch '3.3':
Issue #18434: Updated example script to tidy up resources.
http://hg.python.org/cpython/rev/f8c3d05994e4

----------

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

From report at bugs.python.org  Fri Jul 12 22:54:22 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 12 Jul 2013 20:54:22 +0000
Subject: [docs] [issue18433] Clarify venv docs about which methods check
	for	pre-existing paths
In-Reply-To: <1373634128.21.0.571216700722.issue18433@psf.upfronthosting.co.za>
Message-ID: <3bsRFn5q5pz7Ljv@mail.python.org>


Roundup Robot added the comment:

New changeset 0ca31c07e85e by Vinay Sajip in branch '3.3':
Issue #18433: Clarified venv documentation.
http://hg.python.org/cpython/rev/0ca31c07e85e

New changeset d292635314c9 by Vinay Sajip in branch 'default':
Closes #18433: Merged documentation update from 3.3.
http://hg.python.org/cpython/rev/d292635314c9

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

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

From report at bugs.python.org  Sat Jul 13 00:21:55 2013
From: report at bugs.python.org (Roundup Robot)
Date: Fri, 12 Jul 2013 22:21:55 +0000
Subject: [docs] [issue18389] document that os.path.relpath does not
	interrogate the	file system
In-Reply-To: <1373141672.93.0.461698296017.issue18389@psf.upfronthosting.co.za>
Message-ID: <3bsTBp0lmnzS77@mail.python.org>


Roundup Robot added the comment:

New changeset 70837970c5d8 by R David Murray in branch '3.3':
#18389: Clarify that relpath does not access the file system.
http://hg.python.org/cpython/rev/70837970c5d8

New changeset 7de05609e390 by R David Murray in branch 'default':
#18389: Clarify that relpath does not access the file system.
http://hg.python.org/cpython/rev/7de05609e390

New changeset 1345d8dbcb19 by R David Murray in branch '2.7':
#18389: Clarify that relpath does not access the file system.
http://hg.python.org/cpython/rev/1345d8dbcb19

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

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

From report at bugs.python.org  Sat Jul 13 00:23:06 2013
From: report at bugs.python.org (R. David Murray)
Date: Fri, 12 Jul 2013 22:23:06 +0000
Subject: [docs] [issue18389] document that os.path.relpath does not
	interrogate the	file system
In-Reply-To: <1373141672.93.0.461698296017.issue18389@psf.upfronthosting.co.za>
Message-ID: <1373667786.29.0.527078163547.issue18389@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks, Madison.  I tweaked the wording slightly, but the essence is the same :).

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

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

From report at bugs.python.org  Sat Jul 13 00:28:23 2013
From: report at bugs.python.org (Madison May)
Date: Fri, 12 Jul 2013 22:28:23 +0000
Subject: [docs] [issue18389] document that os.path.relpath does not
	interrogate the	file system
In-Reply-To: <1373141672.93.0.461698296017.issue18389@psf.upfronthosting.co.za>
Message-ID: <1373668103.41.0.626645346673.issue18389@psf.upfronthosting.co.za>


Madison May added the comment:

Thanks, David.  I like your changes -- sounds a lot cleaner and more explicit. :)

----------

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

From report at bugs.python.org  Sat Jul 13 04:42:24 2013
From: report at bugs.python.org (R. David Murray)
Date: Sat, 13 Jul 2013 02:42:24 +0000
Subject: [docs] [issue18430] gzip, bz2,
	lzma: peek advances file position of existing file object
In-Reply-To: <1373571241.88.0.314815867736.issue18430@psf.upfronthosting.co.za>
Message-ID: <1373683344.48.0.919593662389.issue18430@psf.upfronthosting.co.za>


R. David Murray added the comment:

I chose 'access position' because that's the terminology used in the 'seek' man page.  'file position' sounds odd to me, but since that is the term already used it does make sense to be consistent.

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
stage:  -> needs patch
versions: +Python 3.4

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

From report at bugs.python.org  Sat Jul 13 04:52:12 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sat, 13 Jul 2013 02:52:12 +0000
Subject: [docs] [issue18437] Typo in comment inside class Charset about
	output_charset
Message-ID: <1373683932.23.0.900604303434.issue18437@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

Python 3.4, line 197:

    output_charset: Some character sets must be converted before the can be

It is supposed to be:

    output_charset: Some character sets must be converted before they can be

----------
assignee: docs at python
components: Documentation
files: fix_typo_charset.txt
messages: 192990
nosy: docs at python, r.david.murray, vajrasky
priority: normal
severity: normal
status: open
title: Typo in comment inside class Charset about output_charset
versions: Python 3.4
Added file: http://bugs.python.org/file30908/fix_typo_charset.txt

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

From report at bugs.python.org  Sat Jul 13 04:57:25 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 13 Jul 2013 02:57:25 +0000
Subject: [docs] [issue18437] Typo in comment inside class Charset about
	output_charset
In-Reply-To: <1373683932.23.0.900604303434.issue18437@psf.upfronthosting.co.za>
Message-ID: <3bsbJj1xjXz7Ljl@mail.python.org>


Roundup Robot added the comment:

New changeset f91e6d0eb0f7 by R David Murray in branch '3.3':
#18437: fix comment typo.
http://hg.python.org/cpython/rev/f91e6d0eb0f7

New changeset da7d97ca1ef6 by R David Murray in branch 'default':
Merge: #18437: fix comment typo.
http://hg.python.org/cpython/rev/da7d97ca1ef6

New changeset 868010ed641c by R David Murray in branch '2.7':
#18437: fix comment typo.
http://hg.python.org/cpython/rev/868010ed641c

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

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

From report at bugs.python.org  Sat Jul 13 04:58:02 2013
From: report at bugs.python.org (R. David Murray)
Date: Sat, 13 Jul 2013 02:58:02 +0000
Subject: [docs] [issue18437] Typo in comment inside class Charset about
	output_charset
In-Reply-To: <1373683932.23.0.900604303434.issue18437@psf.upfronthosting.co.za>
Message-ID: <1373684282.48.0.86532074591.issue18437@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks.  Fixed.

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

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

From report at bugs.python.org  Sat Jul 13 05:41:51 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sat, 13 Jul 2013 03:41:51 +0000
Subject: [docs] [issue18438] Obsolete url in comment inside decimal module
Message-ID: <1373686911.48.0.750703855786.issue18438@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

Python 3.4, file Lib/decimal.py, line 24:

www.cs.berkeley.edu/~ejr/projects/754/private/drafts/854-1987/dir.html

If you go to the website, you'll encounter this error:

The server has encountered a problem because the resource was not found.

I could not find the replacement. The only thing that I could find is the paid material found here:

http://ieeexplore.ieee.org/xpl/mostRecentIssue.jsp?punumber=2502

That's not good.

----------
assignee: docs at python
components: Documentation
messages: 192994
nosy: docs at python, rhettinger, vajrasky
priority: normal
severity: normal
status: open
title: Obsolete url in comment inside decimal module
versions: Python 3.4

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

From report at bugs.python.org  Sat Jul 13 20:34:45 2013
From: report at bugs.python.org (Barry A. Warsaw)
Date: Sat, 13 Jul 2013 18:34:45 +0000
Subject: [docs] [issue18440] hash() and __hash__() do not document their
	size	constraints
Message-ID: <1373740485.69.0.943591579445.issue18440@psf.upfronthosting.co.za>


New submission from Barry A. Warsaw:

If you have a custom object that implements __hash__() and it returns a value wider than Py_ssize_t, built-in hash() on the object will truncate information.  This is because hash() takes the value returned by obj.__hash__() and coerces it through PyLong_FromSsize_t().  This can cause object hashes to have different values on 64bit and 32bit machines, e.g. on 64bit Linux where Py_ssize_t is 8 bytes wide vs. 32bit Linux where it is 4 bytes wide.

This may be perfectly reasonable from an implementation point of (ref: issue9778) but it is surprising since it is not documented.

This size constraint on object hashes should be documented.

from ctypes import *

class Foo:
    def __hash__(self):
        return 0x1332a6000000000

print(hash(Foo()), sizeof(c_ssize_t))

---64bit Ubuntu 13.10---
$ python3.3 hashex.py
86459409655398400 8

---32bit Ubuntu 13.10---
$ python3 hashex.py
40260800 4

----------
assignee: docs at python
components: Documentation
messages: 193014
nosy: barry, docs at python
priority: normal
severity: normal
status: open
title: hash() and __hash__() do not document their size constraints
type: behavior
versions: Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Sun Jul 14 14:36:00 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 14 Jul 2013 12:36:00 +0000
Subject: [docs] [issue18336] codecs: Link to readline module (history)
	instead of	fd.readline()
In-Reply-To: <1372663191.71.0.440770388569.issue18336@psf.upfronthosting.co.za>
Message-ID: <1373805360.01.0.563630408966.issue18336@psf.upfronthosting.co.za>


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


----------
status: open -> closed

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

From report at bugs.python.org  Sun Jul 14 15:29:26 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 14 Jul 2013 13:29:26 +0000
Subject: [docs] [issue18445] Tools/Script/Readme is outdated
In-Reply-To: <1373782620.19.0.347266346086.issue18445@psf.upfronthosting.co.za>
Message-ID: <1373808566.18.0.492906205791.issue18445@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> needs patch

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

From report at bugs.python.org  Sun Jul 14 17:43:07 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Sun, 14 Jul 2013 15:43:07 +0000
Subject: [docs] [issue18452] Typo in Doc/howto/argparse.rst
Message-ID: <1373816587.08.0.142397091694.issue18452@psf.upfronthosting.co.za>


New submission from F?vry Thibault:

'occurences' -> 'occurrences'

----------
assignee: docs at python
components: Documentation
messages: 193057
nosy: docs at python, iwontbecreative
priority: normal
severity: normal
status: open
title: Typo in Doc/howto/argparse.rst
type: enhancement
versions: Python 3.4

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

From report at bugs.python.org  Sun Jul 14 18:23:20 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Sun, 14 Jul 2013 16:23:20 +0000
Subject: [docs] [issue18452] Typo in Doc/howto/argparse.rst
In-Reply-To: <1373816587.08.0.142397091694.issue18452@psf.upfronthosting.co.za>
Message-ID: <1373819000.65.0.119000204388.issue18452@psf.upfronthosting.co.za>


F?vry Thibault added the comment:

This one typo should also be fixed on other files namely : 
- Doc/library/stdtypes.rst
- Doc/library/configparser.rst

----------

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

From report at bugs.python.org  Sun Jul 14 21:46:03 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sun, 14 Jul 2013 19:46:03 +0000
Subject: [docs] [issue18452] Typo in Doc/howto/argparse.rst
In-Reply-To: <1373816587.08.0.142397091694.issue18452@psf.upfronthosting.co.za>
Message-ID: <3btdf30v2tz7Ljm@mail.python.org>


Roundup Robot added the comment:

New changeset 8c935717fc8e by Ned Deily in branch '2.7':
Issue #18452: fix several "occurrence" typos (reported by F?vry Thibault).
http://hg.python.org/cpython/rev/8c935717fc8e

New changeset 1a93c624551f by Ned Deily in branch '3.3':
Issue #18452: fix several "occurrence" typos (reported by F?vry Thibault).
http://hg.python.org/cpython/rev/1a93c624551f

New changeset db9fe49069ed by Ned Deily in branch 'default':
Closes #18452: fix several "occurrence" typos (reported by F?vry Thibault).
http://hg.python.org/cpython/rev/db9fe49069ed

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

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

From report at bugs.python.org  Sun Jul 14 21:47:57 2013
From: report at bugs.python.org (Ned Deily)
Date: Sun, 14 Jul 2013 19:47:57 +0000
Subject: [docs] [issue18452] Typo in Doc/howto/argparse.rst
In-Reply-To: <1373816587.08.0.142397091694.issue18452@psf.upfronthosting.co.za>
Message-ID: <1373831277.46.0.784926853093.issue18452@psf.upfronthosting.co.za>


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


----------
type: enhancement -> 
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Mon Jul 15 04:11:12 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Mon, 15 Jul 2013 02:11:12 +0000
Subject: [docs] [issue18456] Documentation for PyDict_Update is incorrect
Message-ID: <1373854272.6.0.0142348360978.issue18456@psf.upfronthosting.co.za>


New submission from Nick Coghlan:

The docs from PyDict_Update (http://docs.python.org/3/c-api/dict.html#PyDict_Update) claim it is equivalent to the Python level dict.update (http://docs.python.org/3/library/stdtypes#dict.update)

This isn't accurate - unlike dict.update, PyDict_Update doesn't fall back to the iterating over a sequence of key value pairs if the second argument has no "keys" attribute.

----------
assignee: docs at python
components: Documentation
messages: 193070
nosy: docs at python, ncoghlan
priority: normal
severity: normal
stage: needs patch
status: open
title: Documentation for PyDict_Update is incorrect
type: enhancement
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Jul 15 07:38:44 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Mon, 15 Jul 2013 05:38:44 +0000
Subject: [docs] [issue17583] IDLE HOWTO
In-Reply-To: <1364685156.29.0.769214841654.issue17583@psf.upfronthosting.co.za>
Message-ID: <1373866724.88.0.513503683815.issue17583@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

(If someone else wants to take this before I get to it, feel free. But there seems to be enough support to add something eventually.)

It seems that Rietveld is able to ignore the binaries, but in the future, lets separate the text and images. If nothing else, the images should stay the same while the text gets updated patches.

Looking at http://docs.python.org/3/howto/index.html, I think the title should begin with Idle or IDLE, but if the latter, not include HOWTO as one SHOUT is enough. I think it should be in its alphabetical position after Functional Programming. I have no idea why argparse and ipaddress are out of order.

I think there should be a section on using the shell before using the editor.

>From a command line (at least on Windows, when not in the directory containing idle.py) 'python -m idlelib' is the easiest way to start. Within a Python program, 'import idlelib.idle' starts it. I plan to add a new section to the docs for this, but it might be worth repeating.

I will look more closely at the text another time.

----------
assignee: docs at python -> terry.reedy
nosy: +terry.reedy

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

From report at bugs.python.org  Mon Jul 15 11:15:59 2013
From: report at bugs.python.org (Torim)
Date: Mon, 15 Jul 2013 09:15:59 +0000
Subject: [docs] [issue18356] help(numpy) causes segfault on exit
In-Reply-To: <1372924520.77.0.111539946992.issue18356@psf.upfronthosting.co.za>
Message-ID: <1373879759.74.0.8878283099.issue18356@psf.upfronthosting.co.za>


Torim added the comment:

I would add even the linked solution from StackOverflow.com does not work reliably for me. Try to get at the end of numpy document - text vanishes and possibly lose chars displaying in terminal. Need to reset it.

Modified pydoc's pipepager method this way:
def pipepager(text, cmd):
    """Page through text by feeding it to another program."""
    #pipe = os.popen(cmd, 'w')
    import subprocess
    pipep = subprocess.Popen(cmd, stdin=subprocess.PIPE, shell=True)
    try:
        #pipe.write(text)
        #pipe.close()
	pipep.communicate(text)
    except IOError:
        pass # Ignore broken pipes caused by quitting the pager program.


Works for me so far, although the exact cause of issue with the stock/default pydoc is still not known.

----------
components: +Library (Lib)
nosy: +torim

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

From report at bugs.python.org  Mon Jul 15 14:01:25 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Mon, 15 Jul 2013 12:01:25 +0000
Subject: [docs] [issue18443] Misc/Readme still documents TextMate
In-Reply-To: <1373775366.01.0.177392157148.issue18443@psf.upfronthosting.co.za>
Message-ID: <1373889685.82.0.22832810313.issue18443@psf.upfronthosting.co.za>


F?vry Thibault added the comment:

The issue with Vim files has been fixed but not this one.
Adding a patch in case it is faster for anyone, as well as properly triaging the bug report. This also fixes the list to put in back in alphabetical order.

----------
assignee:  -> docs at python
components: +Documentation
keywords: +patch
nosy: +docs at python, eric.araujo, ezio.melotti, georg.brandl
type:  -> enhancement
versions: +Python 3.4
Added file: http://bugs.python.org/file30924/readme.patch

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

From report at bugs.python.org  Mon Jul 15 15:07:11 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Mon, 15 Jul 2013 13:07:11 +0000
Subject: [docs] [issue18460] .chm documentation files advertised in
	download.html but	not there.
Message-ID: <1373893631.43.0.158733965695.issue18460@psf.upfronthosting.co.za>


New submission from F?vry Thibault:

Just like it happenned with 2.7.3, the .chm help files are not present in the download pages.

The download page (e.g : http://docs.python.org/3/download.html) advertises the presence of .chm files but they are not there. 

I am unsure whether or not these files are still built, but as this as happend for all 3.* versions and there is no previous bug report, it might be worth looking at simply removing support for these files.

----------
assignee: docs at python
components: Documentation
messages: 193096
nosy: docs at python, iwontbecreative
priority: normal
severity: normal
status: open
title: .chm documentation files advertised in download.html but not there.
type: enhancement
versions: Python 3.1, Python 3.2, Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Jul 15 15:50:07 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Mon, 15 Jul 2013 13:50:07 +0000
Subject: [docs] [issue18462] Download > Other documentation page contains a
	link to a	french poker site
Message-ID: <1373896207.45.0.720927599345.issue18462@psf.upfronthosting.co.za>


New submission from F?vry Thibault:

The python for PSP (http://python-psp.net/trac) now redirects to python-psp.net which is a poker site.

----------
assignee: docs at python
components: Documentation
messages: 193101
nosy: docs at python, iwontbecreative
priority: normal
severity: normal
status: open
title: Download > Other documentation page contains a link to a french poker site
type: enhancement

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

From report at bugs.python.org  Mon Jul 15 15:58:48 2013
From: report at bugs.python.org (=?utf-8?q?F=C3=A9vry_Thibault?=)
Date: Mon, 15 Jul 2013 13:58:48 +0000
Subject: [docs] [issue18463] Download > Other documentation page
	outdated/dead links
Message-ID: <1373896728.41.0.823494848316.issue18463@psf.upfronthosting.co.za>


New submission from F?vry Thibault:

See issue 18462 and
The link to the series-60 nokia page directs to an empty page : http://www.developer.nokia.com/Community/Wiki/Nokia_Open_Source/ with comments in history : 
09:15, 24 April 2013 hamishwillee (Talk | contribs) deleted page Nokia Open Source/ (Stop creating htis page or you will be banned.)
04:20, 12 March 2013 hamishwillee (Talk | contribs) deleted page Nokia Open Source/ (There is no point to this topic. No content)
05:37, 4 March 2013 hamishwillee (Talk | contribs) deleted page Nokia Open Source/ (Appears to have been created by accident)

- The download are leak for python for VMS is dead : http://www.pi-net.dyndns.org/anonymous/kits/

----------
assignee: docs at python
components: Documentation
messages: 193102
nosy: docs at python, iwontbecreative
priority: normal
severity: normal
status: open
title: Download > Other documentation page outdated/dead links
type: enhancement

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

From report at bugs.python.org  Mon Jul 15 20:33:17 2013
From: report at bugs.python.org (Ned Deily)
Date: Mon, 15 Jul 2013 18:33:17 +0000
Subject: [docs] [issue18460] .chm documentation files advertised in
	download.html but	not there.
In-Reply-To: <1373893631.43.0.158733965695.issue18460@psf.upfronthosting.co.za>
Message-ID: <1373913197.45.0.307844028094.issue18460@psf.upfronthosting.co.za>


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


----------
nosy: +georg.brandl, loewis

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

From report at bugs.python.org  Mon Jul 15 20:37:18 2013
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 15 Jul 2013 18:37:18 +0000
Subject: [docs] [issue18440] hash() and __hash__() do not document their
	size	constraints
In-Reply-To: <1373740485.69.0.943591579445.issue18440@psf.upfronthosting.co.za>
Message-ID: <1373913438.14.0.28140925686.issue18440@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Mon Jul 15 21:22:36 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 15 Jul 2013 19:22:36 +0000
Subject: [docs] [issue18440] hash() and __hash__() do not document their
	size	constraints
In-Reply-To: <1373740485.69.0.943591579445.issue18440@psf.upfronthosting.co.za>
Message-ID: <3bvF4W2FMWzPns@mail.python.org>


Roundup Robot added the comment:

New changeset 8fe13940b033 by Barry Warsaw in branch '3.3':
- Issue #18440: Clarify that `hash()` can truncate the value returned from an
http://hg.python.org/cpython/rev/8fe13940b033

New changeset f01f0c9cbcc8 by Barry Warsaw in branch 'default':
- Issue #18440: Clarify that `hash()` can truncate the value returned from an
http://hg.python.org/cpython/rev/f01f0c9cbcc8

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

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

From report at bugs.python.org  Mon Jul 15 21:23:28 2013
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 15 Jul 2013 19:23:28 +0000
Subject: [docs] [issue18440] hash() and __hash__() do not document their
	size	constraints
In-Reply-To: <1373740485.69.0.943591579445.issue18440@psf.upfronthosting.co.za>
Message-ID: <1373916208.03.0.5005330388.issue18440@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Jul 16 00:22:11 2013
From: report at bugs.python.org (Ned Deily)
Date: Mon, 15 Jul 2013 22:22:11 +0000
Subject: [docs] [issue18462] Download > Other documentation page contains a
	link to a	french poker site
In-Reply-To: <1373896207.45.0.720927599345.issue18462@psf.upfronthosting.co.za>
Message-ID: <1373926931.01.0.010433222605.issue18462@psf.upfronthosting.co.za>


Ned Deily added the comment:

Thanks for the report. Since there doesn't seem to be an obvious replacement web page, I've removed the reference to this port.

----------
nosy: +ned.deily
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type: enhancement -> 

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

From report at bugs.python.org  Tue Jul 16 00:25:57 2013
From: report at bugs.python.org (Ned Deily)
Date: Mon, 15 Jul 2013 22:25:57 +0000
Subject: [docs] [issue18463] Download > Other documentation page
	outdated/dead links
In-Reply-To: <1373896728.41.0.823494848316.issue18463@psf.upfronthosting.co.za>
Message-ID: <1373927157.83.0.774841228772.issue18463@psf.upfronthosting.co.za>


Ned Deily added the comment:

Thanks for the report. The S60 section now links to a Wikipedia page which gives a better overview and to the Sourceforge download link for the original project.  I've removed the dead link to the other VMS project.

----------
nosy: +ned.deily
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed
type: enhancement -> 

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

From report at bugs.python.org  Tue Jul 16 03:52:16 2013
From: report at bugs.python.org (=?utf-8?q?Fran=C3=A7ois_Pinard?=)
Date: Tue, 16 Jul 2013 01:52:16 +0000
Subject: [docs] [issue18471] Typo in heapq documentation
Message-ID: <1373939536.64.0.4181851186.issue18471@psf.upfronthosting.co.za>


New submission from Fran?ois Pinard:

Within http://docs.python.org/3/library/heapq.html#theory, a sentence begins with "When an event schedule" while it should be spelled "When an event schedules".  The same may be observed in Python 2 documentation.

----------
assignee: docs at python
components: Documentation
messages: 193145
nosy: docs at python, icule
priority: normal
severity: normal
status: open
title: Typo in heapq documentation
versions: Python 3.3

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

From report at bugs.python.org  Tue Jul 16 04:09:55 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 16 Jul 2013 02:09:55 +0000
Subject: [docs] [issue18471] Typo in heapq documentation
In-Reply-To: <1373939536.64.0.4181851186.issue18471@psf.upfronthosting.co.za>
Message-ID: <3bvQ6V0H6mz7Ljt@mail.python.org>


Roundup Robot added the comment:

New changeset 236e6b995300 by Ned Deily in branch '2.7':
Issue #18471: Fix typo in heapq documentation (reported by Fran?ois Pinard).
http://hg.python.org/cpython/rev/236e6b995300

New changeset e22dd5fda5a8 by Ned Deily in branch '3.3':
Issue #18471: Fix typo in heapq documentation (reported by Fran?ois Pinard).
http://hg.python.org/cpython/rev/e22dd5fda5a8

New changeset 8a078bf3cf14 by Ned Deily in branch 'default':
Closes #18471: Fix typo in heapq documentation (reported by Fran?ois Pinard).
http://hg.python.org/cpython/rev/8a078bf3cf14

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

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

From report at bugs.python.org  Tue Jul 16 04:10:44 2013
From: report at bugs.python.org (Ned Deily)
Date: Tue, 16 Jul 2013 02:10:44 +0000
Subject: [docs] [issue18471] Typo in heapq documentation
In-Reply-To: <1373939536.64.0.4181851186.issue18471@psf.upfronthosting.co.za>
Message-ID: <1373940644.8.0.78287516236.issue18471@psf.upfronthosting.co.za>


Ned Deily added the comment:

Thanks for the report.

----------
nosy: +ned.deily
versions: +Python 2.7, Python 3.4

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

From report at bugs.python.org  Wed Jul 17 01:39:14 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Tue, 16 Jul 2013 23:39:14 +0000
Subject: [docs] [issue18478] Class bodies: when does a name become local?
Message-ID: <1374017954.45.0.193690883208.issue18478@psf.upfronthosting.co.za>


New submission from Terry J. Reedy:

http://docs.python.org/3/reference/executionmodel.html#naming-and-binding
says "The following are blocks: ... a class definition." and 

"If a name binding operation occurs anywhere within a code block, all uses of the name within the block are treated as references to the current block. This can lead to errors when a name is used within a block before it is bound. ..." 

This is definitely true for functions, but not for classes:

foo = 'bar'
class C:
    foo = foo

print(C().foo)
#
bar

This is the same for 3.3 and 2.7 with and without '(object)' added. Unless the code is considered to be buggy (probably since forever), the doc should be modified to change 'code block' to 'function code block' or maybe 'module or function code block'. (At near as I can think, the statement is true for modules, but only because globals() == locals(), so that part of the issue does not arise.)

----------
assignee: docs at python
components: Documentation
messages: 193205
nosy: docs at python, terry.reedy
priority: normal
severity: normal
stage: needs patch
status: open
title: Class bodies: when does a name become local?
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Wed Jul 17 01:59:44 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Tue, 16 Jul 2013 23:59:44 +0000
Subject: [docs] [issue18478] Class bodies: when does a name become local?
In-Reply-To: <1374017954.45.0.193690883208.issue18478@psf.upfronthosting.co.za>
Message-ID: <1374019184.43.0.885190095348.issue18478@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/issue18478>
_______________________________________

From report at bugs.python.org  Wed Jul 17 03:13:28 2013
From: report at bugs.python.org (Barry A. Warsaw)
Date: Wed, 17 Jul 2013 01:13:28 +0000
Subject: [docs] [issue10434] Document the rules for "public names"
In-Reply-To: <1289919338.9.0.394057770971.issue10434@psf.upfronthosting.co.za>
Message-ID: <1374023608.55.0.867211683686.issue10434@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Jul 17 09:36:13 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Wed, 17 Jul 2013 07:36:13 +0000
Subject: [docs] [issue18085] Verifying refcounts.dat
In-Reply-To: <1369768958.38.0.697954786488.issue18085@psf.upfronthosting.co.za>
Message-ID: <1374046573.64.0.382513918617.issue18085@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Wed Jul 17 17:30:37 2013
From: report at bugs.python.org (Yury V. Zaytsev)
Date: Wed, 17 Jul 2013 15:30:37 +0000
Subject: [docs] [issue9307] Py_TPFLAGS_LONG_SUBCLASS is not documented
In-Reply-To: <1279561825.23.0.120090245801.issue9307@psf.upfronthosting.co.za>
Message-ID: <1374075037.9.0.701817662083.issue9307@psf.upfronthosting.co.za>


Yury V. Zaytsev added the comment:

Hi,

I agree with Alexander, I've been recently investigating a related problem and I found the lack of documentation on the subject quite frustrating; I therefore propose the attached patch to the docs.

Hope that helps,
--Yury.

----------
keywords: +patch
nosy: +zaytsev
Added file: http://bugs.python.org/file30952/tpflags-doc.patch

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

From report at bugs.python.org  Thu Jul 18 21:10:54 2013
From: report at bugs.python.org (Wolf Ihlenfeldt)
Date: Thu, 18 Jul 2013 19:10:54 +0000
Subject: [docs] [issue18494] PyType_GenericSet/GetDict functions misnamed in
	docs?
Message-ID: <1374174654.87.0.00339141994483.issue18494@psf.upfronthosting.co.za>


New submission from Wolf Ihlenfeldt:

Are the names of functions PyType_GenericSetDict and -GetDict correctly documented (for 3.3.2), or should they be documented as PyObject_GenericGet/SetDict instead? The PyType-prefixed names are out of place in the section, and functions of these names not in the source. The PyObject_-variants are present.

----------
assignee: docs at python
components: Documentation
messages: 193315
nosy: Wolf.Ihlenfeldt, docs at python
priority: normal
severity: normal
status: open
title: PyType_GenericSet/GetDict functions misnamed in docs?
versions: Python 3.3

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

From report at bugs.python.org  Fri Jul 19 21:55:48 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 19 Jul 2013 19:55:48 +0000
Subject: [docs] [issue18438] Obsolete url in comment inside decimal module
In-Reply-To: <1373686911.48.0.750703855786.issue18438@psf.upfronthosting.co.za>
Message-ID: <1374263748.67.0.782072891926.issue18438@psf.upfronthosting.co.za>


?ric Araujo added the comment:

Praise the Wayback Machine: http://web.archive.org/web/20050309223101/http://www.cs.berkeley.edu/~ejr/projects/754/private/drafts/854-1987/dir.html

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

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

From report at bugs.python.org  Fri Jul 19 23:31:12 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 19 Jul 2013 21:31:12 +0000
Subject: [docs] [issue18460] .chm documentation files advertised in
	download.html but	not there.
In-Reply-To: <1373893631.43.0.158733965695.issue18460@psf.upfronthosting.co.za>
Message-ID: <1374269471.97.0.973370687583.issue18460@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

The files are built and included with the Windows installer. Perhaps they can be installed without installing anything else. In any case, unless they are (again?) made available as a separate download, 

"HTML Help (.chm) files are made available in the "Windows" section on the Python download page."

should be changed to something like

"Compiled HTML Help (.chm) files  are included with the Windows MSI Installer on the Python download page."

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

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

From report at bugs.python.org  Sat Jul 20 15:07:59 2013
From: report at bugs.python.org (R. David Murray)
Date: Sat, 20 Jul 2013 13:07:59 +0000
Subject: [docs] [issue18512] sys.stdout.write does not allow bytes in Python
	3.x
In-Reply-To: <1374287481.36.0.643885131326.issue18512@psf.upfronthosting.co.za>
Message-ID: <1374325679.81.0.914196706334.issue18512@psf.upfronthosting.co.za>


R. David Murray added the comment:

The fundamental behavior here is not going to change, as maintaining a bright line between bytes and strings is central to Python3's design.

The question is, does the method for achieving your goal need better documentation?

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python, r.david.murray
versions: +Python 3.4

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

From report at bugs.python.org  Sun Jul 21 04:57:34 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sun, 21 Jul 2013 02:57:34 +0000
Subject: [docs] [issue18516] Typos in Lib/email/generator.py
	and	Lib/email/architecture.rst
Message-ID: <1374375453.94.0.44126763837.issue18516@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

[sky at localhost cpython]$ grep -n boudary Lib/email/generator.py 
352:    #   _make_boudary = Generator._make_boundary
[sky at localhost cpython]$ grep -n fuzy Lib/email/architecture.rst 
27:This division is intentionally a bit fuzy; the API described by this documentation

In addition to that, I found inconsistency in plural form of tuple.

[sky at localhost cpython]$ grep -n "\-tuple" Lib/email/utils.py 
79:    """The inverse of parseaddr(), this takes a 2-tuple of the form
285:    params is a sequence of 2-tuples containing (param name, string value).
291:    # 3-tuple of the continuation number, the string value, and a flag

But I think this issue is very very trivial and we can ignore it.

----------
assignee: docs at python
components: Documentation
messages: 193425
nosy: docs at python, r.david.murray, vajrasky
priority: normal
severity: normal
status: open
title: Typos in Lib/email/generator.py and Lib/email/architecture.rst
versions: Python 3.4

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

From report at bugs.python.org  Sun Jul 21 06:09:50 2013
From: report at bugs.python.org (R. David Murray)
Date: Sun, 21 Jul 2013 04:09:50 +0000
Subject: [docs] [issue18516] Typos in Lib/email/generator.py
	and	Lib/email/architecture.rst
In-Reply-To: <1374375453.94.0.44126763837.issue18516@psf.upfronthosting.co.za>
Message-ID: <1374379790.03.0.64886207168.issue18516@psf.upfronthosting.co.za>


R. David Murray added the comment:

The tuple pluralization looks correct to me.

----------

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

From report at bugs.python.org  Sun Jul 21 09:32:05 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Sun, 21 Jul 2013 07:32:05 +0000
Subject: [docs] [issue18516] Typos in Lib/email/generator.py
	and	Lib/email/architecture.rst
In-Reply-To: <1374375453.94.0.44126763837.issue18516@psf.upfronthosting.co.za>
Message-ID: <1374391925.37.0.26297491493.issue18516@psf.upfronthosting.co.za>


Vajrasky Kok added the comment:

Sorry, my bad. The tuple pluralization is correct. I read it wrongly.

----------

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

From report at bugs.python.org  Sun Jul 21 11:55:34 2013
From: report at bugs.python.org (Mark Dickinson)
Date: Sun, 21 Jul 2013 09:55:34 +0000
Subject: [docs] [issue18438] Obsolete url in comment inside decimal module
In-Reply-To: <1373686911.48.0.750703855786.issue18438@psf.upfronthosting.co.za>
Message-ID: <1374400534.42.0.017779753608.issue18438@psf.upfronthosting.co.za>


Mark Dickinson added the comment:

Searching around a bit, I did find a link to what looks like the actual version of IEEE 854 online.  I don't think it would be appropriate to add such a link to the docs, though.  It looks as though we'll have to settle for a reasonably persistent link that goes to a page *about* IEEE 854, rather than a link to a draft.  The wikipedia page would seem reasonable:

http://en.wikipedia.org/wiki/IEEE_854-1987

----------
nosy: +mark.dickinson

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

From report at bugs.python.org  Sun Jul 21 19:16:19 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Sun, 21 Jul 2013 17:16:19 +0000
Subject: [docs] [issue18518] return-ing within code timed with timeit.timeit
	causes	wrong return value of timeit.timeit
In-Reply-To: <1374400020.0.0.45788018989.issue18518@psf.upfronthosting.co.za>
Message-ID: <1374426979.46.0.41494509686.issue18518@psf.upfronthosting.co.za>


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


----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python
type: behavior -> enhancement
versions: +Python 2.7, Python 3.4

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

From report at bugs.python.org  Mon Jul 22 01:31:48 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Sun, 21 Jul 2013 23:31:48 +0000
Subject: [docs] [issue18518] return-ing within code timed with timeit.timeit
	causes	wrong return value of timeit.timeit
In-Reply-To: <1374400020.0.0.45788018989.issue18518@psf.upfronthosting.co.za>
Message-ID: <1374449508.28.0.866964447383.issue18518@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Agreed this should be closed as "won't fix".

----------
nosy: +rhettinger
resolution:  -> wont fix
status: open -> closed

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

From report at bugs.python.org  Mon Jul 22 04:20:04 2013
From: report at bugs.python.org (R. David Murray)
Date: Mon, 22 Jul 2013 02:20:04 +0000
Subject: [docs] [issue18518] return-ing within code timed with timeit.timeit
	causes	wrong return value of timeit.timeit
In-Reply-To: <1374400020.0.0.45788018989.issue18518@psf.upfronthosting.co.za>
Message-ID: <1374459604.22.0.512815708377.issue18518@psf.upfronthosting.co.za>


R. David Murray added the comment:

Rather than closing it, we converted it to a documentation issue.  I think it is worth a footnote in the docs, since it is not obvious (without reading the source code) that a return statement will cause timeit to return an invalid result instead of raising a syntax error.

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

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

From report at bugs.python.org  Mon Jul 22 04:37:33 2013
From: report at bugs.python.org (Raymond Hettinger)
Date: Mon, 22 Jul 2013 02:37:33 +0000
Subject: [docs] [issue18518] return-ing within code timed with timeit.timeit
	causes	wrong return value of timeit.timeit
In-Reply-To: <1374400020.0.0.45788018989.issue18518@psf.upfronthosting.co.za>
Message-ID: <1374460653.92.0.796667788058.issue18518@psf.upfronthosting.co.za>


Raymond Hettinger added the comment:

Go ahead and add a footnote, but do consider that such footnotes are mostly just clutter.  It doesn't help someone at the moment there is an invalid return value -- instead it just makes it so that afterward someone can say that it is documented.

----------

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

From report at bugs.python.org  Mon Jul 22 15:29:18 2013
From: report at bugs.python.org (Serhiy Storchaka)
Date: Mon, 22 Jul 2013 13:29:18 +0000
Subject: [docs] [issue18529] Use long dash
In-Reply-To: <1374499433.16.0.583158051605.issue18529@psf.upfronthosting.co.za>
Message-ID: <1374499754.92.0.543682421426.issue18529@psf.upfronthosting.co.za>


Serhiy Storchaka added the comment:

Here is an alternative patch which replaces spaced hyphens and en-dashes and non-spaced em-dashes to em-dashes with spaces.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
stage:  -> patch review
type:  -> enhancement
versions: +Python 3.4
Added file: http://bugs.python.org/file31006/doc_mdashes_with_spaces.patch

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

From report at bugs.python.org  Mon Jul 22 20:51:43 2013
From: report at bugs.python.org (Barry A. Warsaw)
Date: Mon, 22 Jul 2013 18:51:43 +0000
Subject: [docs] [issue18531] Undocumented different between METH_KEYWORDS
	and **kws
Message-ID: <1374519103.74.0.277776306074.issue18531@psf.upfronthosting.co.za>


New submission from Barry A. Warsaw:

A colleague discovered an interesting implementation different between C-defined functions and Python-defined functions called with **kws arguments.  He tried to do this:

>>> from collections import defaultdict
>>> '{foo}{bar}'.format(**defaultdict(str))
''

He wondered how this could work, especially given:

>>> def what(**kws):
...   print(type(kws), repr(kws))
... 
>>> what(**defaultdict(str))
<class 'dict'> {}

The Language Reference clearly states that when what() is called, a new dictionary is create, which is populated by keyword arguments not consumed by positional args.

http://docs.python.org/3/reference/compound_stmts.html#function-definitions
http://docs.python.org/3/reference/expressions.html#calls

What isn't described is the behavior when the function is defined in C using METH_KEYWORDS.  In that case, the object passed through the ** argument is passed unscathed to the underlying methodobject defined to take METH_KEYWORDS.  str.format() is of the latter type so it gets the actual defaultdict.  what() of course gets the defined behavior.

It would be nice if the implementation details of the function did not leak into this behavior, but this is admittedly a corner case of the CPython implementation.  I haven't checked any of the alternative implementations to see what they do.  My guess is that CPython won't change for practical and backward compatibility reasons, thus I've opened this issue as a documentation bug.  At the very least, an implementation note in the Language Reference should be added.

----------
assignee: docs at python
components: Documentation
messages: 193559
nosy: barry, docs at python
priority: normal
severity: normal
status: open
title: Undocumented different between METH_KEYWORDS and **kws
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Jul 22 20:53:42 2013
From: report at bugs.python.org (Alex Gaynor)
Date: Mon, 22 Jul 2013 18:53:42 +0000
Subject: [docs] [issue18531] Undocumented different between METH_KEYWORDS
	and **kws
In-Reply-To: <1374519103.74.0.277776306074.issue18531@psf.upfronthosting.co.za>
Message-ID: <1374519222.66.0.18290438434.issue18531@psf.upfronthosting.co.za>


Alex Gaynor added the comment:

I'll confirm that PyPy raises a KeyError on the format() code.

----------
nosy: +alex

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

From report at bugs.python.org  Mon Jul 22 22:29:00 2013
From: report at bugs.python.org (Jason R. Coombs)
Date: Mon, 22 Jul 2013 20:29:00 +0000
Subject: [docs] [issue18532] hashlib.HASH objects should officially expose
	the hash	name
Message-ID: <1374524940.42.0.582552143445.issue18532@psf.upfronthosting.co.za>


New submission from Jason R. Coombs:

In hashlib, the HASH objects currently supply a 'name' attribute, reflecting the name used to initialize the hash object, and they have since Python 2.5. However, this interface is not published so isn't honored by other platforms (namely pypy).

I propose the '.name' attribute be formally added to the documentation to reflect the actual implementation.

I suggest this change be considered as a bugfix release if the original intention was for the '.name' attribute to be public (as it's a bug in the documentation if the intended and implemented interface isn't fully documented).

I plan to do some research to ascertain the intention of this attribute (as can be inferred from tests and the source). For now, I'll assume Python 3.4 only.

Any comments or suggestions welcome.

----------
assignee: docs at python
components: Documentation, Library (Lib)
messages: 193563
nosy: docs at python, jason.coombs
priority: normal
severity: normal
status: open
title: hashlib.HASH objects should officially expose the hash name
versions: Python 3.4

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

From report at bugs.python.org  Mon Jul 22 22:37:17 2013
From: report at bugs.python.org (Christian Heimes)
Date: Mon, 22 Jul 2013 20:37:17 +0000
Subject: [docs] [issue18532] hashlib.HASH objects should officially expose
	the hash	name
In-Reply-To: <1374524940.42.0.582552143445.issue18532@psf.upfronthosting.co.za>
Message-ID: <1374525437.63.0.617603482209.issue18532@psf.upfronthosting.co.za>


Christian Heimes added the comment:

Sounds like a good idea.

----------
nosy: +christian.heimes, gregory.p.smith
stage:  -> needs patch
type:  -> enhancement

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

From report at bugs.python.org  Tue Jul 23 00:05:40 2013
From: report at bugs.python.org (Daniel Holth)
Date: Mon, 22 Jul 2013 22:05:40 +0000
Subject: [docs] [issue18532] hashlib.HASH objects should officially expose
	the hash	name
In-Reply-To: <1374524940.42.0.582552143445.issue18532@psf.upfronthosting.co.za>
Message-ID: <1374530740.64.0.221392776186.issue18532@psf.upfronthosting.co.za>


Daniel Holth added the comment:

fwiw pypy 2 supports HASH.name but the older 1.9 (still part of some Linux distributions) did not.

----------
nosy: +dholth

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

From report at bugs.python.org  Tue Jul 23 16:57:32 2013
From: report at bugs.python.org (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 23 Jul 2013 14:57:32 +0000
Subject: [docs] [issue18512] sys.stdout.write does not allow bytes in Python
	3.x
In-Reply-To: <1374287481.36.0.643885131326.issue18512@psf.upfronthosting.co.za>
Message-ID: <1374591452.09.0.590701238913.issue18512@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Rephrasing R.David's question: 

ntrrgc: Did you consult any documentation (browsing or searching), and if so, where did you look?

----------
nosy: +loewis

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

From report at bugs.python.org  Tue Jul 23 17:42:34 2013
From: report at bugs.python.org (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 23 Jul 2013 15:42:34 +0000
Subject: [docs] [issue18460] .chm documentation files advertised in
	download.html but	not there.
In-Reply-To: <1373893631.43.0.158733965695.issue18460@psf.upfronthosting.co.za>
Message-ID: <1374594154.55.0.733222975001.issue18460@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

The CHM files for 2.7.x and 3.3.x are now there.

----------

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

From report at bugs.python.org  Tue Jul 23 17:43:37 2013
From: report at bugs.python.org (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Tue, 23 Jul 2013 15:43:37 +0000
Subject: [docs] [issue18460] .chm documentation files advertised in
	download.html but	not there.
In-Reply-To: <1373893631.43.0.158733965695.issue18460@psf.upfronthosting.co.za>
Message-ID: <1374594217.62.0.705039265278.issue18460@psf.upfronthosting.co.za>


Changes by Martin v. L?wis <martin at v.loewis.de>:


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

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

From report at bugs.python.org  Wed Jul 24 11:27:48 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 24 Jul 2013 09:27:48 +0000
Subject: [docs] [issue18541] LoggerAdapter example is counter-productive
Message-ID: <1374658068.88.0.794389656378.issue18541@psf.upfronthosting.co.za>


New submission from Antoine Pitrou:

The idiomatic way to use a LoggerAdapter is to override the process() method. However, the example in the cookbook (*) is some gobbledegook code overriding __getitem__ and __iter__ on a separate class. It's a pity that users are directed to use an insane and impractical idiom while the sane way is simple and powerful.

(*) http://docs.python.org/2/howto/logging-cookbook.html#context-info

----------
assignee: docs at python
components: Documentation
messages: 193633
nosy: docs at python, pitrou, vinay.sajip
priority: normal
severity: normal
status: open
title: LoggerAdapter example is counter-productive
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Wed Jul 24 15:08:33 2013
From: report at bugs.python.org (Ronald Oussoren)
Date: Wed, 24 Jul 2013 13:08:33 +0000
Subject: [docs] [issue6627] threading.local() does not work with C-created
	threads
In-Reply-To: <1249243364.61.0.822632396677.issue6627@psf.upfronthosting.co.za>
Message-ID: <1374671313.02.0.234737409766.issue6627@psf.upfronthosting.co.za>


Changes by Ronald Oussoren <ronaldoussoren at mac.com>:


----------
nosy: +ronaldoussoren

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

From report at bugs.python.org  Wed Jul 24 15:45:47 2013
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 24 Jul 2013 13:45:47 +0000
Subject: [docs] [issue18541] LoggerAdapter example is counter-productive
In-Reply-To: <1374658068.88.0.794389656378.issue18541@psf.upfronthosting.co.za>
Message-ID: <1374673547.79.0.153087683232.issue18541@psf.upfronthosting.co.za>


Vinay Sajip added the comment:

That's not quite right. The recommended way *is* to override the process() method. From the page you linked to:

"If you need a different method, e.g. if you want to prepend or append the contextual information to the message string, you just need to subclass LoggerAdapter and override process() to do what you need."

That does not have a specific example, as it seems simple enough to understand as stated.

The example you mention shows something else - how you would adapt an existing class (which might have information to go into the log) so that it could be passed (instead of a dict) to the LoggerAdapter initialiser. Possibly I could put this example into a separate section "Adapting an existing class to provide context information for logging" - this would make it clear that it's a separate use case and not the primary use case when using LoggerAdapter. The text seems clear enough,

"illustrates what dict-like behaviour is needed from an arbitrary ?dict-like? object for use in the constructor", but splitting it out into a separate section will make it easier for those who are speed-reading the docs.

----------

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

From report at bugs.python.org  Wed Jul 24 15:57:05 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 24 Jul 2013 13:57:05 +0000
Subject: [docs] [issue18541] LoggerAdapter example is counter-productive
In-Reply-To: <1374673547.79.0.153087683232.issue18541@psf.upfronthosting.co.za>
Message-ID: <260661816.18360175.1374674219341.JavaMail.root@zimbra10-e2.priv.proxad.net>


Antoine Pitrou added the comment:

> That does not have a specific example, as it seems simple enough to
> understand as stated.

I think we should acknowledge that people often have difficulties
with the rather simple functionalities of the logging module,
not only the advanced ones.

> The example you mention shows something else - how you would adapt an
> existing class (which might have information to go into the log) so
> that it could be passed (instead of a dict) to the LoggerAdapter
> initialiser.

But how is that necessary for the use case? Your LoggerAdapter-derived
class could take the "existing class" as a constructor parameter (*), then
inject the required info in its overriden process() method.

(*) either by overriding the constructor, or simply by passing the
"existing class" as an entry in the "extra" dict.

If I had trusted your doc blindly, I would have thought it necessary
to go through the "complicated scheme", while the simple scheme is 
actually sufficient to add per-connection info to log messages.

----------

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

From report at bugs.python.org  Wed Jul 24 16:33:27 2013
From: report at bugs.python.org (Vinay Sajip)
Date: Wed, 24 Jul 2013 14:33:27 +0000
Subject: [docs] [issue18541] LoggerAdapter example is counter-productive
In-Reply-To: <1374658068.88.0.794389656378.issue18541@psf.upfronthosting.co.za>
Message-ID: <1374676407.42.0.435809757838.issue18541@psf.upfronthosting.co.za>


Vinay Sajip added the comment:

> I think we should acknowledge that people often have difficulties
> with the rather simple functionalities of the logging module,
> not only the advanced ones.

Perhaps some people do have difficulties, but that's always going to be the case no matter what you do. A cookbook should explore different things, both simple and less simple.

> But how is that necessary for the use case? Your LoggerAdapter-
> derived class could take the "existing class" as a constructor
> parameter (*), then inject the required info in its overriden
> process() method.

If you can adapt an existing class to look sufficiently like a dict, that's all you need to do - there's no need to subclass LoggerAdapter and override process(). There might be cases where that's the easier option.

It's surprising how resistant people can be to subclassing and overriding. For example, for issue #18345 which you raised (which I haven't yet addressed as you said it was low-priority), one straightforward approach would be to subclass the relevant FileHandler classes.

> If I had trusted your doc blindly, I would have thought it necessary
> to go through the "complicated scheme"

It depends on how carefully you read it - I don't think it's *actually* misleading, and I quoted in my earlier response the sentence, which comes before the example, which says that overriding process() is what you'd normally do.

What about my suggestion about a separate section for the example, to make it clearer that it's just another approach which might be more suitable in some scenarios?

----------

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

From report at bugs.python.org  Wed Jul 24 16:49:52 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Wed, 24 Jul 2013 14:49:52 +0000
Subject: [docs] [issue18541] LoggerAdapter example is counter-productive
In-Reply-To: <1374676407.42.0.435809757838.issue18541@psf.upfronthosting.co.za>
Message-ID: <1838590296.18469092.1374677386057.JavaMail.root@zimbra10-e2.priv.proxad.net>


Antoine Pitrou added the comment:

> > But how is that necessary for the use case? Your LoggerAdapter-
> > derived class could take the "existing class" as a constructor
> > parameter (*), then inject the required info in its overriden
> > process() method.
> 
> If you can adapt an existing class to look sufficiently like a dict,
> that's all you need to do - there's no need to subclass
> LoggerAdapter and override process(). There might be cases where
> that's the easier option.

I am not talking about "adapting a class". I am taking about overriding
process() to do the adapting in a simpler way than in your example.

----------

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

From report at bugs.python.org  Wed Jul 24 18:53:16 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 24 Jul 2013 16:53:16 +0000
Subject: [docs] [issue18541] LoggerAdapter example is counter-productive
In-Reply-To: <1374658068.88.0.794389656378.issue18541@psf.upfronthosting.co.za>
Message-ID: <3c0jL357lHzQlq@mail.python.org>


Roundup Robot added the comment:

New changeset 16c15d7d4480 by Vinay Sajip in branch '2.7':
Issue #18541: simplified LoggerAdapter example.
http://hg.python.org/cpython/rev/16c15d7d4480

New changeset adaecee37745 by Vinay Sajip in branch '3.3':
Issue #18541: simplified LoggerAdapter example.
http://hg.python.org/cpython/rev/adaecee37745

New changeset f931ee89cc1c by Vinay Sajip in branch 'default':
Closes #18541: merged update from 3.3.
http://hg.python.org/cpython/rev/f931ee89cc1c

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

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

From report at bugs.python.org  Wed Jul 24 20:48:41 2013
From: report at bugs.python.org (py.user)
Date: Wed, 24 Jul 2013 18:48:41 +0000
Subject: [docs] [issue18548] In unittest doc change WidgetTestCase
	to	SimpleWidgetTestCase in suite()
Message-ID: <1374691721.34.0.862188774104.issue18548@psf.upfronthosting.co.za>


New submission from py.user:

http://docs.python.org/3/library/unittest.html#organizing-test-code
"""
def suite():
    suite = unittest.TestSuite()
    suite.addTest(WidgetTestCase('test_default_size'))
    suite.addTest(WidgetTestCase('test_resize'))
    return suite
"""

----------
assignee: docs at python
components: Documentation
files: issue.diff
keywords: patch
messages: 193667
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In unittest doc change WidgetTestCase to SimpleWidgetTestCase in suite()
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file31029/issue.diff

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

From report at bugs.python.org  Thu Jul 25 05:05:15 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 25 Jul 2013 03:05:15 +0000
Subject: [docs] [issue16937] -u (unbuffered I/O) command line option
	documentation	mismatch for sys.stdin
In-Reply-To: <1357928522.67.0.838908652159.issue16937@psf.upfronthosting.co.za>
Message-ID: <3c0ywB1mgfzQGZ@mail.python.org>


Roundup Robot added the comment:

New changeset 4b33f74ab0f1 by Ezio Melotti in branch '3.3':
#16937: document that stdin is always buffered, even when -u is used.  Patch by Elena Oat.
http://hg.python.org/cpython/rev/4b33f74ab0f1

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

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

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

From report at bugs.python.org  Thu Jul 25 05:06:29 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 25 Jul 2013 03:06:29 +0000
Subject: [docs] [issue16937] -u (unbuffered I/O) command line option
	documentation	mismatch for sys.stdin
In-Reply-To: <1357928522.67.0.838908652159.issue16937@psf.upfronthosting.co.za>
Message-ID: <1374721589.28.0.325887335867.issue16937@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

Fixed, thanks for the patch!

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

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

From report at bugs.python.org  Thu Jul 25 06:28:48 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Thu, 25 Jul 2013 04:28:48 +0000
Subject: [docs] [issue18529] Use long dash
In-Reply-To: <1374499433.16.0.583158051605.issue18529@psf.upfronthosting.co.za>
Message-ID: <1374726528.8.0.659463124045.issue18529@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/issue18529>
_______________________________________

From ezio.melotti at gmail.com  Thu Jul 25 06:58:46 2013
From: ezio.melotti at gmail.com (ezio.melotti at gmail.com)
Date: Thu, 25 Jul 2013 04:58:46 -0000
Subject: [docs] Use long dash (issue 18529)
Message-ID: <20130725045846.3581.87210@psf.upfronthosting.co.za>


http://bugs.python.org/review/18529/diff/8715/Doc/faq/extending.rst
File Doc/faq/extending.rst (right):

http://bugs.python.org/review/18529/diff/8715/Doc/faq/extending.rst#newcode319
Doc/faq/extending.rst:319: more input is required --- by extracting the
message string from the exception
This doesn't seem right to me, I think it should just be removed.

http://bugs.python.org/review/18529/diff/8715/Doc/howto/urllib2.rst
File Doc/howto/urllib2.rst (right):

http://bugs.python.org/review/18529/diff/8715/Doc/howto/urllib2.rst#newcode33
Doc/howto/urllib2.rst:33: handling common situations --- like basic
authentication, cookies, proxies and so
This could be dropped as well.

http://bugs.python.org/review/18529/diff/8715/Doc/library/argparse.rst
File Doc/library/argparse.rst (right):

http://bugs.python.org/review/18529/diff/8715/Doc/library/argparse.rst#newcode688
Doc/library/argparse.rst:688: * ``'store'`` --- This just stores the
argument's value.  This is the default
The single '-' seems to be used somewhat often to separate a list
element from its description.  I'm not sure if there's any convention
about this and if it's acceptable.  If it is it should be kept,
otherwise both a '---' or a ':' should work.

http://bugs.python.org/review/18529/diff/8715/Doc/library/codecs.rst
File Doc/library/codecs.rst (right):

http://bugs.python.org/review/18529/diff/8715/Doc/library/codecs.rst#newcode759
Doc/library/codecs.rst:759: The :class:`StreamRecoder` provide a
frontend --- backend view of encoding data
This is wrong.

http://bugs.python.org/review/18529/diff/8715/Doc/library/decimal.rst
File Doc/library/decimal.rst (right):

http://bugs.python.org/review/18529/diff/8715/Doc/library/decimal.rst#newcode73
Doc/library/decimal.rst:73: and rounded floating-point arithmetic."  ---
excerpt from the decimal
You could remove the double space while you are at it.

http://bugs.python.org/review/18529/diff/8715/Doc/library/logging.handlers.rst
File Doc/library/logging.handlers.rst (right):

http://bugs.python.org/review/18529/diff/8715/Doc/library/logging.handlers.rst#newcode533
Doc/library/logging.handlers.rst:533: versions of these daemons expected
a NUL terminated message --- even
You could add an hyphen between NUL and terminated too.

http://bugs.python.org/review/18529/diff/8715/Doc/library/unittest.mock.rst
File Doc/library/unittest.mock.rst (right):

http://bugs.python.org/review/18529/diff/8715/Doc/library/unittest.mock.rst#newcode2235
Doc/library/unittest.mock.rst:2235: just be ordinary mocks (well ---
`MagicMocks`):
Maybe here a comma is better?

http://bugs.python.org/review/18529/diff/8715/Doc/tutorial/whatnow.rst
File Doc/tutorial/whatnow.rst (right):

http://bugs.python.org/review/18529/diff/8715/Doc/tutorial/whatnow.rst#newcode69
Doc/tutorial/whatnow.rst:69: reported by www.egroups.com; Jan. 2000 ---
June 2000: 21272 msgs / 182
I think an en dash would be more appropriate here.

http://bugs.python.org/review/18529/

From report at bugs.python.org  Thu Jul 25 14:51:46 2013
From: report at bugs.python.org (anatoly techtonik)
Date: Thu, 25 Jul 2013 12:51:46 +0000
Subject: [docs] [issue18553] os.isatty() is not Unix only
In-Reply-To: <1374752779.81.0.230915084667.issue18553@psf.upfronthosting.co.za>
Message-ID: <1374756706.54.0.0959180922616.issue18553@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Thu Jul 25 15:02:03 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Thu, 25 Jul 2013 13:02:03 +0000
Subject: [docs] [issue18534] State clearly that open() 'file' param is
	"name" attr of	the result
In-Reply-To: <1374556018.34.0.468152457131.issue18534@psf.upfronthosting.co.za>
Message-ID: <1374757323.5.0.676167714782.issue18534@psf.upfronthosting.co.za>


Nick Coghlan added the comment:

Switching this to a docs bugs, since http://docs.python.org/3/library/functions.html#open doesn't mention this behaviour at all, and http://docs.python.org/3/library/io.html#io.FileIO.name only notes the fact it may be a file descriptor without mentioning the str/bytes discrepancy.

So, at a bare minimum, we need to clearly describe this behaviour in the docs. We may also want to explicitly point out that using os.fsdecode(name) before passing it to open() will ensure that the name attribute is set to a string rather than a bytes object.

----------
assignee:  -> docs at python
components: +Documentation
nosy: +docs at python
title: File "name" attribute should always be a text string -> State clearly that open() 'file' param is "name" attr of the result
versions: +Python 3.3, Python 3.4

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

From report at bugs.python.org  Thu Jul 25 19:33:52 2013
From: report at bugs.python.org (Roundup Robot)
Date: Thu, 25 Jul 2013 17:33:52 +0000
Subject: [docs] [issue15130] remove redundant paragraph in socket howto
In-Reply-To: <1340311752.3.0.940656841103.issue15130@psf.upfronthosting.co.za>
Message-ID: <3c1LBR6Jz3zQGZ@mail.python.org>


Roundup Robot added the comment:

New changeset 68fce7587f72 by R David Murray in branch '3.3':
#15130: remove repeat of abstract paragraph from socket howto body.
http://hg.python.org/cpython/rev/68fce7587f72

New changeset be4cc946b9df by R David Murray in branch 'default':
Merge #15130: remove repeat of abstract paragraph from socket howto body.
http://hg.python.org/cpython/rev/be4cc946b9df

New changeset a8d8bfb61874 by R David Murray in branch '2.7':
#15130: remove repeat of abstract paragraph from socket howto body.
http://hg.python.org/cpython/rev/a8d8bfb61874

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

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

From report at bugs.python.org  Thu Jul 25 19:35:16 2013
From: report at bugs.python.org (R. David Murray)
Date: Thu, 25 Jul 2013 17:35:16 +0000
Subject: [docs] [issue15130] remove redundant paragraph in socket howto
In-Reply-To: <1340311752.3.0.940656841103.issue15130@psf.upfronthosting.co.za>
Message-ID: <1374773716.4.0.0300856824222.issue15130@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks, Tshepang.

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

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

From report at bugs.python.org  Fri Jul 26 03:25:40 2013
From: report at bugs.python.org (R. David Murray)
Date: Fri, 26 Jul 2013 01:25:40 +0000
Subject: [docs] [issue18558] Iterable glossary entry needs clarification
In-Reply-To: <1374796651.89.0.668716719647.issue18558@psf.upfronthosting.co.za>
Message-ID: <1374801940.5.0.979589568485.issue18558@psf.upfronthosting.co.za>


R. David Murray added the comment:

The definition of an Iterable is a class that defines an __iter__  method.  Your class does not, so the behavior you site is correct.

The glossary entry for 'iterable' could use a little clarification.  A class that defines __getitem__ is an iterable if and only if it returns results when passed integers.  Since the documentation for Iterable references that glossary entry, it should probably also be explicit that defining __getitem__ does not (because of the forgoing limitation) cause isinstance(x, Iterable) to be True.  For a class that does not define __iter__, you must explicitly register it with Iterable.

To see why this must be so, consider this:

  >>> y = IsIterable({'a': 'b', 'c': 'd'})
  >>> [x for x in y]
  Traceback (most recent call last):
    File "<stdin>", line 1, in <module>
    File "<stdin>", line 1, in <listcomp>
    File "<stdin>", line 5, in __getitem__
  KeyError: 0

----------
assignee:  -> docs at python
components: +Documentation -Library (Lib)
nosy: +docs at python, r.david.murray
stage:  -> needs patch
title: Iterables not detected correctly -> Iterable glossary entry needs clarification
versions: +Python 3.4

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

From report at bugs.python.org  Fri Jul 26 18:07:36 2013
From: report at bugs.python.org (A.M. Kuchling)
Date: Fri, 26 Jul 2013 16:07:36 +0000
Subject: [docs] [issue18562] Regex howto: revision pass
Message-ID: <1374854855.56.0.787824851556.issue18562@psf.upfronthosting.co.za>


New submission from A.M. Kuchling:

I read through the 3.3 regex howto and have made various edits in the attached patch.

* describe how \w is different when used in bytes and Unicode patterns.

* describe re.ASCII flag to change that behaviour.

* remove a personal reference ('I generally prefer...')

* some small edits and re-wording.

----------
assignee: docs at python
components: Documentation
files: regex.diff
keywords: patch
messages: 193733
nosy: akuchling, docs at python
priority: normal
severity: normal
stage: patch review
status: open
title: Regex howto: revision pass
versions: Python 3.3
Added file: http://bugs.python.org/file31039/regex.diff

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

From report at bugs.python.org  Fri Jul 26 18:13:16 2013
From: report at bugs.python.org (Berker Peksag)
Date: Fri, 26 Jul 2013 16:13:16 +0000
Subject: [docs] [issue18562] Regex howto: revision pass
In-Reply-To: <1374854855.56.0.787824851556.issue18562@psf.upfronthosting.co.za>
Message-ID: <1374855196.12.0.5751167857.issue18562@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti
versions: +Python 3.4

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

From report at bugs.python.org  Fri Jul 26 23:47:38 2013
From: report at bugs.python.org (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 26 Jul 2013 21:47:38 +0000
Subject: [docs] [issue18529] Use long dash
In-Reply-To: <1374499433.16.0.583158051605.issue18529@psf.upfronthosting.co.za>
Message-ID: <1374875258.82.0.873352643394.issue18529@psf.upfronthosting.co.za>


?ric Araujo added the comment:

This looks like the kind of high-churn, low-benefit patches that we typically encourage new contributors not to do.  It?s fine to update dashes when modifying the surrounding text for another fix, and it may be useful to encourage using them in the markup docs, but not to do one big change.

----------
nosy: +eric.araujo, r.david.murray

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

From report at bugs.python.org  Sat Jul 27 01:06:11 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 26 Jul 2013 23:06:11 +0000
Subject: [docs] [issue18548] In unittest doc change WidgetTestCase
	to	SimpleWidgetTestCase in suite()
In-Reply-To: <1374691721.34.0.862188774104.issue18548@psf.upfronthosting.co.za>
Message-ID: <1374879971.22.0.852408159751.issue18548@psf.upfronthosting.co.za>


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


----------
nosy: +ezio.melotti, michael.foord
stage:  -> patch review
versions: +Python 3.3

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

From report at bugs.python.org  Sat Jul 27 01:28:20 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Fri, 26 Jul 2013 23:28:20 +0000
Subject: [docs] [issue18558] Iterable glossary entry needs clarification
In-Reply-To: <1374796651.89.0.668716719647.issue18558@psf.upfronthosting.co.za>
Message-ID: <1374881300.41.0.724065168772.issue18558@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

Stephen, your class, or rather instances thereof when initialized with a sequence, follow the old iteration protocol. You might call them iterators in the generic sense, though I cannot remember whether we used 'iterator' much before the introduction of the new and now dominant iteration protocol. I am sure 'iterable' was introduced with the new protocol for objects with .__iter__ methods that return iterators, which in this context means an object with a .__next__ method and excludes .__getitem__ objects.

It would have been less confusing is we had disabled the old protocol in 3.0, but aside from the predictable confusion, it seemed better to keep it.

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

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

From report at bugs.python.org  Sat Jul 27 03:19:53 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 27 Jul 2013 01:19:53 +0000
Subject: [docs] [issue18553] os.isatty() is not Unix only
In-Reply-To: <1374752779.81.0.230915084667.issue18553@psf.upfronthosting.co.za>
Message-ID: <1374887993.74.0.900036482463.issue18553@psf.upfronthosting.co.za>


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


----------
stage:  -> needs patch
type:  -> behavior
versions:  -Python 3.1, Python 3.2, Python 3.5

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

From report at bugs.python.org  Sat Jul 27 07:12:17 2013
From: report at bugs.python.org (py.user)
Date: Sat, 27 Jul 2013 05:12:17 +0000
Subject: [docs] [issue18566] In unittest.TestCase docs for setUp() and
	tearDown()	don't mention AssertionError
Message-ID: <1374901937.1.0.747872580847.issue18566@psf.upfronthosting.co.za>


New submission from py.user:

http://docs.python.org/3/library/unittest.html#unittest.TestCase.setUp
"any exception raised by this method will be considered an error rather than a test failure"

http://docs.python.org/3/library/unittest.html#unittest.TestCase.tearDown
"Any exception raised by this method will be considered an error rather than a test failure."


utest.py

#!/usr/bin/env python3

import unittest

class Test(unittest.TestCase):
    
    def setUp(self):
        raise AssertionError

    def tearDown(self):
        raise AssertionError
    
    def test_nothing(self):
        pass



[guest at localhost py]$ python3 -m unittest -v utest
test_nothing (utest.Test) ... FAIL

======================================================================
FAIL: test_nothing (utest.Test)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./utest.py", line 8, in setUp
    raise AssertionError
AssertionError

----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (failures=1)
[guest at localhost py]$


also raising unittest.SkipTest works properly

----------
assignee: docs at python
components: Documentation
messages: 193772
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In unittest.TestCase docs for setUp() and tearDown() don't mention AssertionError
type: enhancement
versions: Python 3.4

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

From report at bugs.python.org  Sat Jul 27 07:16:16 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Sat, 27 Jul 2013 05:16:16 +0000
Subject: [docs] [issue18566] In unittest.TestCase docs for setUp() and
	tearDown()	don't mention AssertionError
In-Reply-To: <1374901937.1.0.747872580847.issue18566@psf.upfronthosting.co.za>
Message-ID: <1374902176.87.0.553396643044.issue18566@psf.upfronthosting.co.za>


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


----------
keywords: +easy
nosy: +ezio.melotti, michael.foord
stage:  -> needs patch

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

From report at bugs.python.org  Sat Jul 27 18:12:13 2013
From: report at bugs.python.org (Steven D'Aprano)
Date: Sat, 27 Jul 2013 16:12:13 +0000
Subject: [docs] [issue18572] Remove redundant note about surrogates in
	string escape	doc
Message-ID: <1374941533.84.0.352957238503.issue18572@psf.upfronthosting.co.za>


New submission from Steven D'Aprano:

The documentation for string escapes suggests that \uxxxx escapes can be used to generate characters in the Supplementary Multilingual Planes by using surrogate pairs:

"Individual code units which form parts of a surrogate pair can be encoded using this escape sequence."

http://docs.python.org/3/reference/lexical_analysis.html#string-and-bytes-literals

E.g. in Python 3.2:

py> '\uD80C\uDC80' == '\U00013080'
True

but that is no longer the case in Python 3.3. I suggest the documentation should just remove that note.

----------
assignee: docs at python
components: Documentation
messages: 193787
nosy: docs at python, stevenjd
priority: normal
severity: normal
status: open
title: Remove redundant note about surrogates in string escape doc
versions: Python 3.3

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

From report at bugs.python.org  Sat Jul 27 20:20:02 2013
From: report at bugs.python.org (py.user)
Date: Sat, 27 Jul 2013 18:20:02 +0000
Subject: [docs] [issue18573] In unittest.TestCase.assertWarns doc there is
	some text	about assertRaises()
Message-ID: <1374949202.48.0.718203936991.issue18573@psf.upfronthosting.co.za>


New submission from py.user:

http://docs.python.org/3/library/unittest.html#unittest.TestCase.assertWarns
"When used as a context manager, assertRaises() accepts"
"... is to perform additional checks on the exception raised"

----------
assignee: docs at python
components: Documentation
files: issue.diff
keywords: patch
messages: 193788
nosy: docs at python, py.user
priority: normal
severity: normal
status: open
title: In unittest.TestCase.assertWarns doc there is some text about assertRaises()
type: enhancement
versions: Python 3.4
Added file: http://bugs.python.org/file31054/issue.diff

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

From report at bugs.python.org  Sat Jul 27 21:04:44 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 27 Jul 2013 19:04:44 +0000
Subject: [docs] [issue18573] In unittest.TestCase.assertWarns doc there is
	some text	about assertRaises()
In-Reply-To: <1374949202.48.0.718203936991.issue18573@psf.upfronthosting.co.za>
Message-ID: <1374951884.73.0.699541365468.issue18573@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Sat Jul 27 21:05:45 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 27 Jul 2013 19:05:45 +0000
Subject: [docs] [issue18572] Remove redundant note about surrogates in
	string escape	doc
In-Reply-To: <1374941533.84.0.352957238503.issue18572@psf.upfronthosting.co.za>
Message-ID: <1374951945.08.0.282019925913.issue18572@psf.upfronthosting.co.za>


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


----------
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.4

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

From report at bugs.python.org  Sat Jul 27 22:03:56 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 27 Jul 2013 20:03:56 +0000
Subject: [docs] [issue18572] Remove redundant note about surrogates in
	string escape	doc
In-Reply-To: <1374941533.84.0.352957238503.issue18572@psf.upfronthosting.co.za>
Message-ID: <1374955436.42.0.963253221776.issue18572@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

3.3.2:
>>> '\uD80C\uDC80' == '\U00013080'
False

The statement that surrogate code units can be encoded this way is still true. Indeed, it is now the only way to get such code units into a string. The suggestion that a pair will make an astral char is now false. The sentence could be changed to 

"Individual surrogate code units can be encoded using this escape sequence."

On the other hand, the same is true of *any* BMP char, including all the *other* non-graphic chars that can only be entered this way. So I think the sentence, if not deleted, should be replaced by what seems to me a more useful (complete) statement.

"Any Basic Multilingual  Plane (BMP) codepoint can be encoded using this escape sequence."

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

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

From report at bugs.python.org  Sat Jul 27 22:09:07 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 27 Jul 2013 20:09:07 +0000
Subject: [docs] [issue18573] In unittest.TestCase.assertWarns doc there is
	some text	about assertRaises()
In-Reply-To: <1374949202.48.0.718203936991.issue18573@psf.upfronthosting.co.za>
Message-ID: <1374955747.0.0.0562494697407.issue18573@psf.upfronthosting.co.za>


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


----------
assignee: docs at python -> terry.reedy
nosy: +terry.reedy

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

From report at bugs.python.org  Sat Jul 27 22:16:13 2013
From: report at bugs.python.org (Roundup Robot)
Date: Sat, 27 Jul 2013 20:16:13 +0000
Subject: [docs] [issue18573] In unittest.TestCase.assertWarns doc there is
	some text	about assertRaises()
In-Reply-To: <1374949202.48.0.718203936991.issue18573@psf.upfronthosting.co.za>
Message-ID: <3c2dhr5vxfz7Ljg@mail.python.org>


Roundup Robot added the comment:

New changeset 55dcf9e065be by Terry Jan Reedy in branch '3.3':
Issue #18573: Complete copy-paste from assertRaises entry to assertWarns entry.
http://hg.python.org/cpython/rev/55dcf9e065be

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

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

From report at bugs.python.org  Sat Jul 27 22:17:34 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 27 Jul 2013 20:17:34 +0000
Subject: [docs] [issue18573] In unittest.TestCase.assertWarns doc there is
	some text	about assertRaises()
In-Reply-To: <1374949202.48.0.718203936991.issue18573@psf.upfronthosting.co.za>
Message-ID: <1374956253.96.0.589410043353.issue18573@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

assertWarns is new in 3.2 and not in 2.7.
The sentence was copied from the assertRaises section but not changed.
Thanks for reporting.

----------
resolution:  -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
type: enhancement -> behavior
versions:  -Python 2.7

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

From report at bugs.python.org  Sat Jul 27 22:56:14 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Sat, 27 Jul 2013 20:56:14 +0000
Subject: [docs] [issue18566] In unittest.TestCase docs for setUp() and
	tearDown()	don't mention AssertionError
In-Reply-To: <1374901937.1.0.747872580847.issue18566@psf.upfronthosting.co.za>
Message-ID: <1374958574.55.0.744145892127.issue18566@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

I re-ran with setUp 'raise' changed to 'pass' to see the effect of raise AssertionError or unittest.SkipTest in tearDown and indeed the test fails or skips even then. I suggest adding ', other than AssertionError or SkipTest,' just after 'method'. The same is true of test_xxx methods.

A slight anomaly is that AssertionError in test_nothing and SkipTest in tearDown results in "FAILED (failures=1, skipped=1)", which is not really a skip.

For setUpClass and setUpModule, AssertionErrors *are* errors, not failures, while SkipTest works everywhere.

----------
nosy: +terry.reedy
versions: +Python 2.7, Python 3.3

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

From report at bugs.python.org  Sun Jul 28 14:32:44 2013
From: report at bugs.python.org (Nick Coghlan)
Date: Sun, 28 Jul 2013 12:32:44 +0000
Subject: [docs] [issue18576] Rename and document test.script_helper
	as	test.support.script_helper
Message-ID: <1375014764.64.0.152576599022.issue18576@psf.upfronthosting.co.za>


New submission from Nick Coghlan:

tests.script_helper provides various utilities for sensibly testing scripts in a subprocess. It isn't easy for CPython developers to discover, since it is isn't documented and the file is mixed in with actual tests in the main test directory.

As discussed in #15494, it should be:

1. Moved from Lib/test/ to Lib/test/support (and imports in tests adjusted accordingly)
2. Documented in Doc/library/test.rst

These changes should be made on both the 3.3 and default branches to avoid spurious merge conflicts.

----------
assignee: docs at python
components: Documentation, Tests
messages: 193819
nosy: docs at python, ncoghlan
priority: normal
severity: normal
status: open
title: Rename and document test.script_helper as test.support.script_helper
type: enhancement
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Jul 29 08:27:08 2013
From: report at bugs.python.org (rurpy)
Date: Mon, 29 Jul 2013 06:27:08 +0000
Subject: [docs] [issue18584] examples in email.policy doc are fu'd
Message-ID: <1375079228.82.0.247789886969.issue18584@psf.upfronthosting.co.za>


New submission from rurpy:

In the first example in the documentation for library module email.policy (http://docs.python.org/3/library/email.policy.html#module-email.policy):

  >>> from email import msg_from_binary_file
  >>> from email.generator import BytesGenerator
  >>> from subprocess import Popen, PIPE
  >>> with open('mymsg.txt', 'b') as f:
  ...     msg = msg_from_binary_file(f)

line 1: The module is "message_from_binary_file", not "msg_from_binary_file"
line 4: The mode must be "rb", not "b".
line 5: Same module (mis-)name problem as line 1.

Then in following example...

  >>> import os
  >>> with open('converted.txt', 'wb') as f:
  ...   f.write(msg.as_string (policy=msg.policy.clone (linesep=os.linesep))

line 3: Ubnbalanced parens, .as_string() has no "policy" keyword arg.

Please note I am trying to figure out how to use the email module for the first time and the above errors are glaring.  There may be (probably are) other errors in the examples and in the text that I am unaware of -- I've made  no attempt to find any others.  I suggest that someone familiar with email module review this page more carefully.

----------
assignee: docs at python
components: Documentation
messages: 193852
nosy: docs at python, rurpy2
priority: normal
severity: normal
status: open
title: examples in email.policy doc are fu'd
versions: Python 3.3

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

From report at bugs.python.org  Mon Jul 29 14:27:06 2013
From: report at bugs.python.org (R. David Murray)
Date: Mon, 29 Jul 2013 12:27:06 +0000
Subject: [docs] [issue18572] Remove redundant note about surrogates in
	string escape	doc
In-Reply-To: <1374941533.84.0.352957238503.issue18572@psf.upfronthosting.co.za>
Message-ID: <1375100826.53.0.690909771255.issue18572@psf.upfronthosting.co.za>


R. David Murray added the comment:

Python 3.2.3 (default, Jun 15 2013, 14:13:52) 
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> '\uD80C\uDC80'
'\ud80c\udc80'
>>> '\uD80C\uDC80' == '\U00013080'
False

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

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

From report at bugs.python.org  Mon Jul 29 17:03:29 2013
From: report at bugs.python.org (Steven D'Aprano)
Date: Mon, 29 Jul 2013 15:03:29 +0000
Subject: [docs] [issue18572] Remove redundant note about surrogates in
	string escape	doc
In-Reply-To: <1375100826.53.0.690909771255.issue18572@psf.upfronthosting.co.za>
Message-ID: <51F6843B.9070909@pearwood.info>


Steven D'Aprano added the comment:

On 29/07/13 22:27, R. David Murray wrote:

>>>> '\uD80C\uDC80' == '\U00013080'
> False

Are you running a wide build? In a narrow build, it returns True.

----------

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

From report at bugs.python.org  Mon Jul 29 17:51:55 2013
From: report at bugs.python.org (Ezio Melotti)
Date: Mon, 29 Jul 2013 15:51:55 +0000
Subject: [docs] [issue18548] In unittest doc change WidgetTestCase
	to	SimpleWidgetTestCase in suite()
In-Reply-To: <1374691721.34.0.862188774104.issue18548@psf.upfronthosting.co.za>
Message-ID: <1375113115.38.0.274711140306.issue18548@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

This is a leftover from 2.7.  In 2.7 the docs have a SimpleWidgetTestCase used as base class for two other classes, and then the same example is reimplemented by using a single WidgetTestCase class.
I think it would be better to make the two docs converge, by renaming the SimpleWidgetTestCase in 3.x to WidgetTestCase, and get rid of the SimpleWidgetTestCase example in 2.7.

----------

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

From report at bugs.python.org  Mon Jul 29 18:58:04 2013
From: report at bugs.python.org (R. David Murray)
Date: Mon, 29 Jul 2013 16:58:04 +0000
Subject: [docs] [issue18572] Remove redundant note about surrogates in
	string escape	doc
In-Reply-To: <1374941533.84.0.352957238503.issue18572@psf.upfronthosting.co.za>
Message-ID: <1375117084.81.0.613283294601.issue18572@psf.upfronthosting.co.za>


R. David Murray added the comment:

Probably.  I think the default build on Gentoo is wide.

That seems to make the existing text even more incorrect :)

----------

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

From report at bugs.python.org  Mon Jul 29 19:12:35 2013
From: report at bugs.python.org (R. David Murray)
Date: Mon, 29 Jul 2013 17:12:35 +0000
Subject: [docs] [issue18584] examples in email.policy doc are fu'd
In-Reply-To: <1375079228.82.0.247789886969.issue18584@psf.upfronthosting.co.za>
Message-ID: <1375117955.22.0.038468098206.issue18584@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thank you for the report.  We currently don't have automated testing of the doctest strings, and I must have neglected to hand test those examples before release.  I will fix (and test!) them ASAP.

----------
components: +email
nosy: +barry, r.david.murray
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.4

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

From report at bugs.python.org  Mon Jul 29 19:17:37 2013
From: report at bugs.python.org (Clay McClure)
Date: Mon, 29 Jul 2013 17:17:37 +0000
Subject: [docs] [issue18588] timeit examples should be consistent
Message-ID: <1375118257.92.0.412245719168.issue18588@psf.upfronthosting.co.za>


Changes by Clay McClure <clay at daemons.net>:


----------
assignee: docs at python
components: Documentation
nosy: claymation, docs at python
priority: normal
severity: normal
status: open
title: timeit examples should be consistent
type: enhancement
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5

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

From report at bugs.python.org  Mon Jul 29 19:20:38 2013
From: report at bugs.python.org (Clay McClure)
Date: Mon, 29 Jul 2013 17:20:38 +0000
Subject: [docs] [issue18588] timeit examples should be consistent
Message-ID: <1375118438.6.0.867422483387.issue18588@psf.upfronthosting.co.za>


New submission from Clay McClure:

The timeit module documentation includes examples of command-line and programmatic invocation, but the results between the two sets of examples don't agree.

This patch brings the results into agreement with each other.

----------
keywords: +patch
Added file: http://bugs.python.org/file31076/18588.patch

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

From report at bugs.python.org  Mon Jul 29 20:22:04 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 29 Jul 2013 18:22:04 +0000
Subject: [docs] [issue18589] cross-referencing doesn't work between the
	extending	guide and c-api
Message-ID: <1375122124.66.0.67649436332.issue18589@psf.upfronthosting.co.za>


New submission from Antoine Pitrou:

It doesn't seem possible to make reference links to e.g. the definition for tp_clear. Both :attr:`tp_clear` and :attr:`PyTypeObject.tp_clear` do not make any link. The extending guide is littered with such broken references.

----------
assignee: docs at python
components: Documentation
messages: 193887
nosy: docs at python, eric.araujo, ezio.melotti, georg.brandl, pitrou
priority: high
severity: normal
status: open
title: cross-referencing doesn't work between the extending guide and c-api
type: behavior
versions: Python 2.7, Python 3.3, Python 3.4

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

From report at bugs.python.org  Mon Jul 29 20:29:42 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 29 Jul 2013 18:29:42 +0000
Subject: [docs] [issue18589] cross-referencing doesn't work between the
	extending	guide and c-api
In-Reply-To: <1375122124.66.0.67649436332.issue18589@psf.upfronthosting.co.za>
Message-ID: <1375122582.85.0.368638162829.issue18589@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

Ahah, it seems the correct markup is :c:member:`~PyTypeObject.tp_clear`

Now all the existing references have to be fixed...

----------

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

From report at bugs.python.org  Mon Jul 29 20:35:23 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Mon, 29 Jul 2013 18:35:23 +0000
Subject: [docs] [issue18589] cross-referencing doesn't work between the
	extending	guide and c-api
In-Reply-To: <1375122124.66.0.67649436332.issue18589@psf.upfronthosting.co.za>
Message-ID: <1375122923.79.0.730406322401.issue18589@psf.upfronthosting.co.za>


Antoine Pitrou added the comment:

The following command does the trick:

sed -i "s/:attr:\`tp_/:c:member:\`~PyTypeObject.tp_/g" `find -name "*.rst"`

It does not fix word-wrapping, though. Is it ok to commit?

----------

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

From report at bugs.python.org  Mon Jul 29 22:02:12 2013
From: report at bugs.python.org (Roundup Robot)
Date: Mon, 29 Jul 2013 20:02:12 +0000
Subject: [docs] [issue18584] examples in email.policy doc are fu'd
In-Reply-To: <1375079228.82.0.247789886969.issue18584@psf.upfronthosting.co.za>
Message-ID: <3c3sHl6PPzzQq2@mail.python.org>


Roundup Robot added the comment:

New changeset ffc7ea3c04a5 by R David Murray in branch '3.3':
#18584: make doctest examples in email documentation pass.
http://hg.python.org/cpython/rev/ffc7ea3c04a5

New changeset 206685a4b19c by R David Murray in branch 'default':
Merge #18584: make doctest examples in email documentation pass.
http://hg.python.org/cpython/rev/206685a4b19c

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

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

From report at bugs.python.org  Mon Jul 29 22:06:01 2013
From: report at bugs.python.org (R. David Murray)
Date: Mon, 29 Jul 2013 20:06:01 +0000
Subject: [docs] [issue18584] examples in email.policy doc are fu'd
In-Reply-To: <1375079228.82.0.247789886969.issue18584@psf.upfronthosting.co.za>
Message-ID: <1375128361.15.0.231499648516.issue18584@psf.upfronthosting.co.za>


R. David Murray added the comment:

OK, this fixed.  The 'as_string' example will still fail, as I never added the policy argument to that method.  I'll deal with that in a separate issue.

Unfortunately it is quite possible there are other errors in the new docs, since they are new...I will review them in the coming month as I'll be working on adding some additional new features to the provisional policies.

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

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

From report at bugs.python.org  Tue Jul 30 06:44:29 2013
From: report at bugs.python.org (Vajrasky Kok)
Date: Tue, 30 Jul 2013 04:44:29 +0000
Subject: [docs] [issue18593] Typo in Lib/multiprocessing/heap.py
Message-ID: <1375159469.25.0.714853217909.issue18593@psf.upfronthosting.co.za>


New submission from Vajrasky Kok:

$ grep Inheirtable Lib/multiprocessing/*
Lib/multiprocessing/heap.py:# Inheirtable class which wraps an mmap, and from which blocks can be allocated

----------
assignee: docs at python
components: Documentation
messages: 193913
nosy: docs at python, vajrasky
priority: normal
severity: normal
status: open
title: Typo in Lib/multiprocessing/heap.py
versions: Python 3.4

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

From report at bugs.python.org  Tue Jul 30 07:52:55 2013
From: report at bugs.python.org (Antoine Pitrou)
Date: Tue, 30 Jul 2013 05:52:55 +0000
Subject: [docs] [issue18593] Typo in Lib/multiprocessing/heap.py
In-Reply-To: <1375159469.25.0.714853217909.issue18593@psf.upfronthosting.co.za>
Message-ID: <1375163575.19.0.0612979374353.issue18593@psf.upfronthosting.co.za>


Changes by Antoine Pitrou <pitrou at free.fr>:


----------
nosy: +sbt

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

From report at bugs.python.org  Tue Jul 30 15:13:08 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 30 Jul 2013 13:13:08 +0000
Subject: [docs] [issue18593] Typo in Lib/multiprocessing/heap.py
In-Reply-To: <1375159469.25.0.714853217909.issue18593@psf.upfronthosting.co.za>
Message-ID: <3c4J9J07FYz7LkS@mail.python.org>


Roundup Robot added the comment:

New changeset 634d6307730d by Eli Bendersky in branch '3.3':
Issue #18593: fix typo in comment
http://hg.python.org/cpython/rev/634d6307730d

New changeset b805bace07c5 by Eli Bendersky in branch 'default':
Issue #18593: fix typo in comment
http://hg.python.org/cpython/rev/b805bace07c5

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

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

From report at bugs.python.org  Tue Jul 30 15:13:44 2013
From: report at bugs.python.org (Eli Bendersky)
Date: Tue, 30 Jul 2013 13:13:44 +0000
Subject: [docs] [issue18593] Typo in Lib/multiprocessing/heap.py
In-Reply-To: <1375159469.25.0.714853217909.issue18593@psf.upfronthosting.co.za>
Message-ID: <1375190024.56.0.9235849409.issue18593@psf.upfronthosting.co.za>


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


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

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

From report at bugs.python.org  Tue Jul 30 17:19:21 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 30 Jul 2013 15:19:21 +0000
Subject: [docs] [issue18600] email.policy doc example passes 'policy' to
	as_string, but that doesn't work
Message-ID: <1375197560.98.0.336881142306.issue18600@psf.upfronthosting.co.za>


New submission from R. David Murray:

When I wrote those docs I intended to add a policy argument to as_string, but did not do it by the time 3.3 was released.  The docs for 3.3 need to be corrected, and I need to decide if I do want to add that keyword to as_string in 3.4 (the answer is probably yes, but I may check with the email-sig first).

----------
assignee: docs at python
components: Documentation, email
messages: 193937
nosy: barry, docs at python, r.david.murray
priority: normal
severity: normal
stage: needs patch
status: open
title: email.policy doc example passes 'policy' to as_string, but that doesn't work
type: behavior
versions: Python 3.3, Python 3.4

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

From report at bugs.python.org  Tue Jul 30 20:43:26 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 30 Jul 2013 18:43:26 +0000
Subject: [docs] [issue18584] examples in email.policy doc are fu'd
In-Reply-To: <1375079228.82.0.247789886969.issue18584@psf.upfronthosting.co.za>
Message-ID: <3c4RVP3sn6zQGr@mail.python.org>


Roundup Robot added the comment:

New changeset 7b86be4e822c by R David Murray in branch '3.3':
#18584: s/testcleanup/testsetup/ until we switch to Sphinx 1.1.
http://hg.python.org/cpython/rev/7b86be4e822c

New changeset 1901a04a3b4a by R David Murray in branch 'default':
Merge #18584: s/testcleanup/testsetup/ until we switch to Sphinx 1.1.
http://hg.python.org/cpython/rev/1901a04a3b4a

----------

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

From report at bugs.python.org  Tue Jul 30 21:07:26 2013
From: report at bugs.python.org (Stephen Paul Chappell)
Date: Tue, 30 Jul 2013 19:07:26 +0000
Subject: [docs] [issue18601] Example "command-line interface to difflib"
	has	typographical error
Message-ID: <1375211246.29.0.527231910426.issue18601@psf.upfronthosting.co.za>


New submission from Stephen Paul Chappell:

The example at the bottom is good but has a line with a bad variable it is name. It says:

    with open(fromlines) as fromf, open(tofile) as tof:
        fromlines, tolines = list(fromf), list(tof)

In the first line, fromlines does no even exist yet. should say:

    with open(fromlines) as fromf, open(tofile) as tof:
        from, tolines = list(fromf), list(tof)

----------
assignee: docs at python
components: Demos and Tools, Documentation
messages: 193948
nosy: Zero, docs at python
priority: normal
severity: normal
status: open
title: Example "command-line interface to difflib" has typographical error
versions: Python 3.3

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

From report at bugs.python.org  Tue Jul 30 21:38:02 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 30 Jul 2013 19:38:02 +0000
Subject: [docs] [issue18601] Example "command-line interface to difflib"
	has	typographical error
In-Reply-To: <1375211246.29.0.527231910426.issue18601@psf.upfronthosting.co.za>
Message-ID: <3c4SjP1nT1zR8P@mail.python.org>


Roundup Robot added the comment:

New changeset 0e1f0faacb0d by R David Murray in branch '3.3':
#18601: fix error made when difflib example was converted to use 'with'.
http://hg.python.org/cpython/rev/0e1f0faacb0d

New changeset c4f377d710da by R David Murray in branch 'default':
Merge: #18601: fix error made when difflib example was converted to use 'with'.
http://hg.python.org/cpython/rev/c4f377d710da

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

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

From report at bugs.python.org  Tue Jul 30 21:39:28 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 30 Jul 2013 19:39:28 +0000
Subject: [docs] [issue18601] Example "command-line interface to difflib"
	has	typographical error
In-Reply-To: <1375211246.29.0.527231910426.issue18601@psf.upfronthosting.co.za>
Message-ID: <1375213168.83.0.872948406302.issue18601@psf.upfronthosting.co.za>


R. David Murray added the comment:

Thanks for the report.  Actually that first 'fromlines' should be 'fromfile'.  Looks like someone made a typo when converting the example to use the 'with' statement.

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

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

From report at bugs.python.org  Tue Jul 30 21:53:45 2013
From: report at bugs.python.org (Roundup Robot)
Date: Tue, 30 Jul 2013 19:53:45 +0000
Subject: [docs] [issue16273] f.tell() returning negative number on Windows
	build
In-Reply-To: <1350526122.97.0.103530434711.issue16273@psf.upfronthosting.co.za>
Message-ID: <3c4T3X3bkFz7LjN@mail.python.org>


Roundup Robot added the comment:

New changeset 81bc2d64c006 by R David Murray in branch '3.3':
#16273: Fix tutorial discussion of seek/tell (opaque text-mode values).
http://hg.python.org/cpython/rev/81bc2d64c006

New changeset c7d9a2159c6c by R David Murray in branch 'default':
Merge: #16273: Fix tutorial discussion of seek/tell (opaque text-mode values).
http://hg.python.org/cpython/rev/c7d9a2159c6c

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

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

From report at bugs.python.org  Tue Jul 30 21:56:03 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 30 Jul 2013 19:56:03 +0000
Subject: [docs] [issue16273] f.tell() returning negative number on Windows
	build
In-Reply-To: <1350526122.97.0.103530434711.issue16273@psf.upfronthosting.co.za>
Message-ID: <1375214163.5.0.769237688862.issue16273@psf.upfronthosting.co.za>


R. David Murray added the comment:

Committed the doc patch.  Thanks Sijin.

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

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

From report at bugs.python.org  Tue Jul 30 22:29:30 2013
From: report at bugs.python.org (R. David Murray)
Date: Tue, 30 Jul 2013 20:29:30 +0000
Subject: [docs] [issue16355] inspect.getcomments() does not work in the
	interactive	shell
In-Reply-To: <1351511930.82.0.59071323276.issue16355@psf.upfronthosting.co.za>
Message-ID: <1375216170.71.0.110907964546.issue16355@psf.upfronthosting.co.za>


R. David Murray added the comment:

The patch looks good, but I would prefer that the test not use mock+knowledge of how get_comment is implemented, but instead test the public API by actually creating a module and deleting the source file.  test.script_helpers can be used to do this easily.

----------

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

From report at bugs.python.org  Wed Jul 31 03:22:37 2013
From: report at bugs.python.org (py.user)
Date: Wed, 31 Jul 2013 01:22:37 +0000
Subject: [docs] [issue18573] In unittest.TestCase.assertWarns doc there is
	some text	about assertRaises()
In-Reply-To: <1374949202.48.0.718203936991.issue18573@psf.upfronthosting.co.za>
Message-ID: <1375233757.49.0.730056275794.issue18573@psf.upfronthosting.co.za>


py.user added the comment:

What about the second line?
It doesn't catch any exception


utest.py

#!/usr/bin/env python3

import unittest

class Test(unittest.TestCase):

    def test_warning(self):
        import warnings

        with self.assertWarns(RuntimeWarning) as cm:
            raise ValueError('f')
            warnings.warn('f', RuntimeWarning)
        print(repr(cm.warning))


[guest at localhost py]$ python3 -m unittest utest
E
======================================================================
ERROR: test_warning (utest.Test)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./utest.py", line 11, in test_warning
    raise ValueError('f')
ValueError: f

----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (errors=1)
[guest at localhost py]$


with commented raise

[guest at localhost py]$ python3 -m unittest utest
RuntimeWarning('f',)
.
----------------------------------------------------------------------
Ran 1 test in 0.000s

OK
[guest at localhost py]$


in the patch I copied terms from the first sentence of the paragraph

----------

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

From report at bugs.python.org  Wed Jul 31 04:30:36 2013
From: report at bugs.python.org (Terry J. Reedy)
Date: Wed, 31 Jul 2013 02:30:36 +0000
Subject: [docs] [issue18573] In unittest.TestCase.assertWarns doc there is
	some text	about assertRaises()
In-Reply-To: <1374949202.48.0.718203936991.issue18573@psf.upfronthosting.co.za>
Message-ID: <1375237835.98.0.6954836576.issue18573@psf.upfronthosting.co.za>


Terry J. Reedy added the comment:

> What about the second line?
What second line?
> It doesn't catch any exception
It? I do not understand your point. Your example works as documented, including "any unexpected exception is an error".

Actually, that should be 'any exception' as none is expected.

Also, "additional checks on the exception raised:" should be 'warning caught'

----------

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

From report at bugs.python.org  Wed Jul 31 04:31:47 2013
From: report at bugs.python.org (Roundup Robot)
Date: Wed, 31 Jul 2013 02:31:47 +0000
Subject: [docs] [issue18573] In unittest.TestCase.assertWarns doc there is
	some text	about assertRaises()
In-Reply-To: <1374949202.48.0.718203936991.issue18573@psf.upfronthosting.co.za>
Message-ID: <3c4dtq0FcwzSyG@mail.python.org>


Roundup Robot added the comment:

New changeset 366beee880aa by Terry Jan Reedy in branch '3.3':
Issue #18573: More copy-paste fixes to assertWarns entry.
http://hg.python.org/cpython/rev/366beee880aa

----------

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

From report at bugs.python.org  Wed Jul 31 09:01:01 2013
From: report at bugs.python.org (py.user)
Date: Wed, 31 Jul 2013 07:01:01 +0000
Subject: [docs] [issue18573] In unittest.TestCase.assertWarns doc there is
	some text	about assertRaises()
In-Reply-To: <1374949202.48.0.718203936991.issue18573@psf.upfronthosting.co.za>
Message-ID: <1375254061.29.0.123016353814.issue18573@psf.upfronthosting.co.za>


py.user added the comment:

> What second line?
the second line patched in the diff file

----------

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

From report at bugs.python.org  Wed Jul 31 15:31:50 2013
From: report at bugs.python.org (Tshepang Lekhonkhobe)
Date: Wed, 31 Jul 2013 13:31:50 +0000
Subject: [docs] [issue7674] select.select() corner cases: duplicate fds,
	out-of-range fds
In-Reply-To: <1263192751.1.0.719382931138.issue7674@psf.upfronthosting.co.za>
Message-ID: <1375277510.32.0.562654169376.issue7674@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/issue7674>
_______________________________________

From blancalmancilla at gmail.com  Thu Jul  4 15:34:53 2013
From: blancalmancilla at gmail.com (Blanca Mancilla)
Date: Thu, 04 Jul 2013 13:34:53 -0000
Subject: [docs] Possible error
Message-ID: <CAALHx9R-ncGqUnO4fXcoZiEqA2RnWqoSrsHwo4Q=ttojSf07sQ@mail.gmail.com>

Hi,
I'm going through the documentation and came across the following error:

in http://docs.python.org/2.7/tutorial/interpreter.html, in the Source
Encoding Section, there is a program:

# -*- coding: iso-8859-15 -*-
currency = u"?"print ord(currency)

which presents a problem when running:


Traceback (most recent call last):
  File "encoding.py", line 6, in <module>
    print ord(currency)
TypeError: ord() expected a character, but string of length 3 found

but if I change the encoding to UTF-8 it works:

# -*- coding: UTF -*-

it give the desired results. Not sure if it is a real bug.


Regards,

bm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130704/272e7298/attachment-0001.html>

From blancalmancilla at gmail.com  Fri Jul  5 14:26:48 2013
From: blancalmancilla at gmail.com (Blanca Mancilla)
Date: Fri, 05 Jul 2013 12:26:48 -0000
Subject: [docs] About loops
Message-ID: <CAALHx9T+0BW_Rv-ixw4-w=kVm+rcShoh0ukhLq54h2Ud8Y5Hzw@mail.gmail.com>

Hi,
In section 4.4 break and continue Statements and else Clauses in loops, the
first program has an issue:
the second for: for x in range(2,n) is not entered in the first iteration
of the n for (for n in range(2,10))
as range (2,2) give an empty range:

>>> range(2,2)
[]

therefore 2 is never "declared" prime.

Also the break is in the wrong place.

bm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130705/63d31975/attachment-0001.html>

From blancalmancilla at gmail.com  Fri Jul  5 14:49:37 2013
From: blancalmancilla at gmail.com (Blanca Mancilla)
Date: Fri, 05 Jul 2013 12:49:37 -0000
Subject: [docs] About loops
In-Reply-To: <CAALHx9T+0BW_Rv-ixw4-w=kVm+rcShoh0ukhLq54h2Ud8Y5Hzw@mail.gmail.com>
References: <CAALHx9T+0BW_Rv-ixw4-w=kVm+rcShoh0ukhLq54h2Ud8Y5Hzw@mail.gmail.com>
Message-ID: <CAALHx9S8vz8JkmVmfxpJa5+rMN35EgHY-u+BMOn4gJRrcrnUNQ@mail.gmail.com>

and of course there are some test missing as whatever is not even is first
declared prime.
bm


On Fri, Jul 5, 2013 at 8:26 AM, Blanca Mancilla
<blancalmancilla at gmail.com>wrote:

> Hi,
> In section 4.4 break and continue Statements and else Clauses in loops,
> the first program has an issue:
> the second for: for x in range(2,n) is not entered in the first iteration
> of the n for (for n in range(2,10))
> as range (2,2) give an empty range:
>
> >>> range(2,2)
> []
>
> therefore 2 is never "declared" prime.
>
> Also the break is in the wrong place.
>
> bm
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130705/516cd809/attachment-0001.html>

From charles.merriam at gmail.com  Sun Jul  7 02:37:55 2013
From: charles.merriam at gmail.com (Charles Merriam)
Date: Sun, 07 Jul 2013 00:37:55 -0000
Subject: [docs] Bug in docs.python.org/2/sys.html
Message-ID: <5EA168F8-FD8A-417E-931D-36BEF09A3600@gmail.com>

This section should be first, before "argv":

.. data:: api_version 
?

as everything else is alphabetical.   It is currently between "version" and "version_info".

Thank you for your dedication,

Charles Merriam


From emmanuelackerman at earthlink.net  Sun Jul 14 02:52:45 2013
From: emmanuelackerman at earthlink.net (Emmanuel Ackerman)
Date: Sun, 14 Jul 2013 00:52:45 -0000
Subject: [docs] Python 2.7 Documentation
Message-ID: <51E1F5DF.4090502@earthlink.net>

Would it be ok to include the downloaded Python 2.7 documentation in 
Rachel from worldpossible.org <http://worldpossible.org/>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130714/9db09e8a/attachment.html>

From cocoatomo77 at gmail.com  Mon Jul 22 22:11:03 2013
From: cocoatomo77 at gmail.com (tomo cocoa)
Date: Mon, 22 Jul 2013 20:11:03 -0000
Subject: [docs] very miscellaneous doc bug
Message-ID: <CAN_7T0+ay0Avr9xU53i0pfgv-MSGnEsM+pvZEGNb69cnUAaBPw@mail.gmail.com>

Hello

I am a translator on Japanese Python documents.

A period was omitted after the word ":func:`distutils.util.execute`"

http://docs.python.org/3.3/distutils/apiref.html#distutils.ccompiler.CCompiler.execute

Excuse me for reporting a small mistake :p

Regards,

cocoatomo

-- 
class Cocoatomo:
    name = 'cocoatomo'
    email_address = 'cocoatomo77 at gmail.com'
    twitter_id = '@cocoatomo'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130722/3ff256a2/attachment.html>

From drekin at gmail.com  Mon Jul 29 15:47:05 2013
From: drekin at gmail.com (Draic Kin)
Date: Mon, 29 Jul 2013 13:47:05 -0000
Subject: [docs] Fwd: Order in Python documentation search results
In-Reply-To: <CAL6gwWVY0HMXD4ZWJeCUV4f3gh2EabK3jMJnaF04E2MRYq5Cpw@mail.gmail.com>
References: <CACvLUangzuQfrHZV9r=2eSpPreYWkBJ0H0AttZKfY9_HFV-udQ@mail.gmail.com>
 <CAL6gwWVY0HMXD4ZWJeCUV4f3gh2EabK3jMJnaF04E2MRYq5Cpw@mail.gmail.com>
Message-ID: <CACvLUamWcfYR97_ZLqvD4=G9z75XH1jAZ0PQEV4w_vmuhpv1-Q@mail.gmail.com>

Hello,
in January there was an attempt by Hernan Grecco to improve the order in
documentation search. Even a patch for Sphinx was accepted, however the
improvement wasn't implemented on docs.python.org. It would be nice to be
done. See forwarded message for details.

Thank you for reaction, Drekin


---------- Forwarded message ----------
From: Hernan Grecco <hernan.grecco at gmail.com>
Date: Mon, Jul 29, 2013 at 2:26 PM
Subject: Re: Order in Python documentation search results
To: Draic Kin <drekin at gmail.com>


Hi,

The patch was accepted into sphinx. What is missing is a new sphinx
release and that this release is installed in docs.python.org. It
would be really nice if this functionality is available in
docs.python.org (that was the original aim of the patch) but it is
outside my reach. Maybe you can e-mail the maintainer of the site.

cheers,

Hernan



On Mon, Jul 29, 2013 at 8:13 AM, Draic Kin <drekin at gmail.com> wrote:
> Hello,
> I have found your nice improvement of Python documentation search
> (http://mail.python.org/pipermail/python-ideas/2013-January/018500.html).
As
> I understand, you have finished the patch of sphinx
> (https://bitbucket.org/birkenfeld/sphinx/issue/1067/better-search-results
).
> However your improvement doesn't seem to be actually implemented on
> docs.python.org. Is there a chance it will be so? It would be very nice if
> search on docs.python.org worked like in your improvement
> (http://hgrecco.github.io/searchpydocs/).
>
> Thank you for information, Drekin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130729/90c55ead/attachment-0001.html>

From cjw at ncf.ca  Tue Jul 30 22:40:05 2013
From: cjw at ncf.ca (Colin J. Williams)
Date: Tue, 30 Jul 2013 20:40:05 -0000
Subject: [docs] Documentation for distutils - Python 2.7.5
Message-ID: <51F8229F.3080602@ncf.ca>

An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130730/7bea8c8d/attachment-0001.html>

From juergen.lindemeyer at gmx.net  Sat Jul  6 17:33:14 2013
From: juergen.lindemeyer at gmx.net (Juergen Novak)
Date: Sat, 06 Jul 2013 15:33:14 -0000
Subject: [docs] izip not documented in Py3
Message-ID: <51D83893.1080809@gmx.net>

Hi there,

today I was stumpling over a nice video of Raymond Hettinger. He also 
described izip, which I did not knew before. So I looked into the 
documentation and did not find it, because it was in 2.x in itertools 
and in 3.x it is a builtin.

But it is not documented as a builtin in 3.x -- either it is not 
documented in 3.x itertools (what is correct, since it can not be 
imported from there anymore, I guess).

I only did find it in 3.x documentation in a little doc about the 
conversion tool, stating that imports of izip are removed.

So essentially, izip is *not* documented at all in Py3.

There also might be missing some others that where moved from itertools 
to builtin, like imap. Did not check it.


Best Regards,

/juergen

From melottejoseph2 at gmail.com  Mon Jul 29 21:06:43 2013
From: melottejoseph2 at gmail.com (Joseph Melotte)
Date: Mon, 29 Jul 2013 19:06:43 -0000
Subject: [docs] Phyton tutorial als 1 file
Message-ID: <CAOfyMSR1q-5JF6V9eB7YpQXJv3_dGZH-TxsdoYSYzbjFfbuwKw@mail.gmail.com>

geachte,

website
http://www.coolpython.nl/tutorials/tut/tut.html

is deze tutorial ook te downloade als 1 file ?
indien ja, graag dan de website.

vriendelijke groeten,

Melotte Joseph
in B
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130729/624cd553/attachment-0001.html>

From mspalmer91 at gmail.com  Tue Jul  9 06:08:21 2013
From: mspalmer91 at gmail.com (Matthew Palmer)
Date: Tue, 09 Jul 2013 04:08:21 -0000
Subject: [docs] Bug Report: str() listed as 'Built in Function'
Message-ID: <CAC5aji1ydmrBWxN_j=RnfJLuEPn5+OccLD_P9-2vCJ-P+d7urA@mail.gmail.com>

http://docs.python.org/2/library/functions.html#non-essential-built-in-functions

"str()" is listed as a function although apperently, according to several
other people it's apparently a type, and not a function.

>>> str
<type 'str'>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130709/656496d5/attachment-0001.html>

From pydanny at gmail.com  Sat Jul 27 12:21:32 2013
From: pydanny at gmail.com (Daniel Greenfeld)
Date: Sat, 27 Jul 2013 10:21:32 -0000
Subject: [docs] Unittest documentation points to deprecated resource
Message-ID: <CAOoSJ_qwYnLskw055Mmc9OWwgqib_RvmaaQ31Sx4FD7x-94H_w@mail.gmail.com>

On http://docs.python.org/2/library/unittest.html

The "seealso" includes a link to "The Python Testing Tools Taxonomy",
which states that it is deprecated in favor of contents on the
official Python wiki:
http://wiki.python.org/moin/PythonTestingToolsTaxonomy

Regards,

Daniel Greenfeld

From obrien.hugh at gmail.com  Sat Jul 27 20:14:00 2013
From: obrien.hugh at gmail.com (Hugh O'Brien)
Date: Sat, 27 Jul 2013 18:14:00 -0000
Subject: [docs] Minor bug on
	http://docs.python.org/2/tutorial/interpreter.html
Message-ID: <CAOHKUnLoCc57y+BBCiXMA4u735_upA47vadX9EFtSMnEdNkxng@mail.gmail.com>

Section 2.2.5 shows the following demo code:

>>> import site
>>> site.getusersitepackages()
'/home/user/.local/lib/python3.2/site-packages'

The path provided is for python3, not 2.

Thanks for the docs,

Hugh

From obrien.hugh at gmail.com  Mon Jul 29 00:05:16 2013
From: obrien.hugh at gmail.com (Hugh O'Brien)
Date: Sun, 28 Jul 2013 22:05:16 -0000
Subject: [docs] minor bug in http://docs.python.org/3/tutorial/modules.html
Message-ID: <CAOHKUnKuK1i+Js9UPDfiGkU56uty0tuHrksxkmJB-ud0SoQX_Q@mail.gmail.com>

In section 6.4 the example file hierarchy seems to be affected by Python
syntax highlighting, resulting in the 'for' term appearing bold.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20130728/89879cf8/attachment-0001.html>

From techtonik at gmail.com  Tue Jul 23 20:31:52 2013
From: techtonik at gmail.com (anatoly techtonik)
Date: Tue, 23 Jul 2013 18:31:52 -0000
Subject: [docs] Problem with Python 3 docs usability and Google search
Message-ID: <CAPkN8xLqT014skGkvp0pbcDXxNAUB0mY72vuyQ3MYErmnnxxJA@mail.gmail.com>

Manual pages for Python 3 docs have two usability issues.

1. Page contents is too huge, makes manual unreadable. Compare:
http://docs.python.org/3/reference/datamodel.html?highlight=__getattr__#customizing-attribute-access
and
http://docs.python.org/release/2.5.2/ref/attribute-access.html

2. Searching by Google also leads to the second page, which most
likely means that people still link to the old content, unable to find
the latest stuff
https://www.google.com/search?q=attribute+access+python

Please, CC.
--
anatoly t.